Method for implementing simultaneous multi-panel physical uplink shared channel transmissions

Abstract

A user equipment (UE) includes a transceiver and a processor configured to receive a plurality of DCIs for simultaneous multi-panel physical uplink shared channel (PUSCH) transmissions (STxMP). The processor is configured to determine that the UE is scheduled with the STxMP overlapping in the time domain and the frequency domain through a plurality of physical downlink control channels (PDCCHs) having different associated control resource set pool index values. Based on the determination, the processor is configured to schedule each PUSCH transmission of the STxMP based on an associated downlink modulation reference symbol according to UE capability; multiplexing two or more hybrid automatic repeat request acknowledgements (HARQ-ACKs) according to a total number of HARQ-ACKs described in a total downlink allocation index bit field of each of the plurality of DCIs; and determining a transmission of each PUSCH of the STxMP based on a respective data priority or schedule for the PUSCH.

Description

Technical Field

[0001] The present application generally relates to wireless communication systems, including methods and systems for implementing simultaneous multi-panel (MP) physical uplink shared channel (PUSCH) transmissions. Background Art

[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between base stations and wireless communication devices. Wireless communication system standards and protocols may include, for example, the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the IEEE 802.11 standard for wireless local area networks (WLANs) (commonly referred to as Wi-Fi within industry organizations). ® ).

[0003] As envisioned by 3GPP, different wireless communication system standards and protocols may use various radio access networks (RANs) to communicate between base stations of the RAN (which may also sometimes be referred to as RAN nodes, network nodes, or simply nodes) and wireless communication devices called user equipment (UE). The 3GPP RAN may include, for example, Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next Generation Radio Access Network (NG-RAN).

[0004] Each RAN may use one or more radio access technologies (RATs) to perform communications between base stations and UEs. For example, GERAN implements GSM and / or EDGE RAT, UTRAN implements Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, E-UTRAN implements LTE RAT (sometimes referred to as LTE), and NG-RAN implements NR RAT (sometimes referred to as 5G RAT, 5G NR RAT, or NR in this document). In some deployments, E-UTRAN may also implement NR RAT. In some deployments, NG-RAN may also implement LTE RAT.

[0005] A base station used by a RAN may correspond to the RAN. An example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as an evolved Node B, enhanced Node B, eNodeB, or eNB). An example of an NG-RAN base station is a Next Generation Node B (sometimes also referred to as a g-Node B or gNB).

[0006] The RAN provides its communication services with external entities through its connection to the Core Network (CN). For example, E-UTRAN may utilize the Evolved Packet Core (EPC), while NG-RAN may utilize the 5G Core Network (5GC). BRIEF DESCRIPTION OF THE DRAWINGS

[0007] To easily identify the discussion of any particular element or action, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.

[0008] Figure 1 An example wireless communication system is shown in accordance with embodiments described herein.

[0009] Figure 2A-2C An example of two physical uplink shared channels (PUSCHs) overlapping when spatial division multiplexed (SDMed) or frequency division multiplexed (FDMed) is shown in accordance with embodiments described herein.

[0010] Figure 3A-3B Example multiplexing of a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) is shown in accordance with embodiments described herein.

[0011] Figure 4 An example flow diagram of operations that may be performed by a UE according to the embodiments described herein is shown.

[0012] Figure 5 An example flow diagram of operations that may be performed by a base station according to embodiments described herein is shown.

[0013] Figure 6 An example flow diagram of operations that may be performed by a UE according to the embodiments described herein is shown.

[0014] Figure 7 An example architecture of a wireless communication system according to embodiments described herein is shown.

[0015] Figure 8 A system for performing signaling between a wireless device and a network device according to embodiments described herein is shown. DETAILED DESCRIPTION

[0016] In the present disclosure, various embodiments relate to methods and systems for implementing simultaneous multi-panel (MP) physical uplink shared channel (PUSCH) transmissions. As used herein, "simultaneous" transmissions may include transmissions that are transmitted in a substantially simultaneous manner. In particular, the embodiments described herein relate to methods and systems for indicating simultaneous multi-panel PUSCH transmissions (or uplink (UL) transmissions) using UL precoding indications for PUSCH transmissions and / or UL beam indications for physical uplink control channels (PUCCH) and / or PUSCH. The UL precoding indications and / or UL beam indications are transmitted in a single downlink control information (S-DCI) or in a multi-DCI based multi-transmission reception point (multi-TRP or m-TRP) operation.

[0017] In addition, for the case of multi-TRP operation based on multi-DCI, two PUSCHs or two PUCCHs may be transmitted to two different TRPs in the same CC. As described herein, a TRP may refer to a user equipment (UE), a base station, an access point, a Wi-Fi router, and the like. Two or more PUSCHs may be transmitted in the UL direction using one or more antenna panels of the UE. In some embodiments, the total number of layers and the total number of codewords across all antenna panels may be, for example, four and two, respectively.

[0018] In the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.214 Release 16, simultaneous physical downlink shared channel (PDSCH) reception for m-TRP is mentioned using S-DCI or m-DCI. If simultaneous PDSCH reception is scheduled by S-DCI, the PDSCH resources associated with different downlink (DL) beams (or spatial Rx filters) are frequency domain multiplexed (FDMed) or spatial domain multiplexed (SDMed). In Section 5.1 of TS 38.214, it is described that the UE is indicated using two transmission configuration indication (TCI) states in the code point of the DCI field "TCI" and a demodulation reference signal (DM-RS) port within one code division multiplexing (CDM) group in the DCI field "antenna port". In Section 5.1.6.2 of TS 38.214, it is described that when the UE does not indicate an entry containing repetitionNumber in PDSCH-TDRA using DCI, the DCI field "Time Domain Resource Allocation" (TDRA) indicates that the UE is not configured with sfnSchemePdsch, and it is indicated by two TCI states in the code point of the DCI field "TCI" and DM-RS ports within two CDM groups in the DCU field "Antenna Port". In this case, the first TCI state corresponds to the CDM group of the first antenna port indicated by the antenna port table, and the second TCI state corresponds to another CDM group.

[0019] If simultaneous PDSCH receptions are scheduled by m-DCI, the two PDSCH receptions may overlap completely or partially, or not at all, in the time and frequency domains.The Physical Data Control Channel (PDCCH) scheduling the two PDSCHs is associated with different ControlResourceSets with different coresetPoolIndex values.

[0020] In Release 17, the UE may also transmit multiple repetitions of the same transport block (TB) on different UL beams, where the repetitions are in time division multiplexing (TDM) mode. In this case, beam indication is performed by extending the sounding reference signal (SRS) resource indicator (SRI) bit field when two SRS resource sets used as codebook or non-codebook are configured. However, in Release 17, simultaneous PUSCH transmission is not supported using frequency division multiplexing (FDM) or space division multiplexing (SDM). Various embodiments in the present disclosure may describe methods and systems for simultaneous PUSCH transmission in m-TRP scenarios.

[0021] Reference will now be made specifically to the representative embodiments / aspects illustrated in the accompanying drawings. The following description is not intended to limit the embodiments to a preferred embodiment. On the contrary, it is intended to cover alternatives, combinations, modifications and equivalents that may be included within the spirit and scope of the embodiments defined by the appended claims.

[0022] Figure 1 An example wireless communication system according to the embodiments described herein is shown. Figure 1 As shown, the wireless communication system 100 may include base stations 102, 104, and 106 and a UE 108. In some embodiments, the base stations 102, 104, and 106 may be eNb, eNodeB, gNodeB, or access point (AP) in a radio access network (RAN), and may support one or more radio access technologies, such as 4G, 5G, 5G New Radio (5G NR), etc. The UE 108 may be a phone, a smart phone, a tablet, a smart watch, an Internet of Things (IoT), etc. As a non-limiting example, each of the base stations 102, 104, and 106 may be used as a TRP for communicating with the UE 108 in a UL direction and a DL direction. The UE 108 may use one or more antenna panels to send UL transmission of data and / or control information (such as PUCCH, PUSCH, SRS) to one or more TRPs and DL reception of data and / or control information (such as PDCCH, PDSCH, etc.) alternately, simultaneously, or contemporaneously.

[0023] Figure 2A , Figure 2B and Figure 2CExamples of complete overlap in the frequency domain, non-overlap in the frequency domain, and partial overlap in the frequency domain are shown respectively. For example, in Figure 200a, two PUSCHs 202 and 204 are space-division multiplexed and transmitted via multiple TRPs. As shown in Figure 200a, PUSCHs 202 and 204 can completely overlap each other in the frequency domain and in the time domain. In Figure 200b, two PUSCHs 206 and 208 that are frequency-division multiplexed do not overlap in the frequency domain, and as shown in Figure 200c, two PUSCHs 210 and 212 that are frequency-division multiplexed partially overlap in the frequency domain.

[0024] Various embodiments as described herein may address potential issues associated with simultaneous multi-panel PUSCH transmissions (STxMP) using S-DCI or m-DCI. For example, for STxMP using m-DCI, potential issues may be associated with DM-RS configuration, such as whether the DM-RS symbol positions for two PUSCH transmissions can be aligned. Another potential issue may be associated with frequency hopping (FH), such as when intra-slot FH or inter-slot FH is utilized to indicate one of two PUSCHs instead of the other of the two PUSCHs. In some embodiments, FH may also affect DM-RS alignment or misalignment. Another issue that needs to be addressed is, for example, Figure 2A , Figure 2B and / or Figure 2C When the two PUSCHs overlap as shown in , are scheduled by different DCIs with different values ​​of Total Downlink Assignment Index (TDAI), what should be the value of each TDAI. Other issues may be associated with the priority indicator value of each PUSCH of STxMP with different priority values ​​and the UE behavior when the total number of layers across two STxMP PUSCHs scheduled by m-DCI exceeds four.

[0025] Various embodiments as described herein may use s-DCI to address potential issues related to STxMP, which may be related to TDAI indication for a dynamic hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook and how to use a multiple grant PUSCH procedure to indicate STxMP PUSCH. An issue related to TDAI indication for a dynamic HARQ-ACK codebook may be overlapping PUSCHs scheduled by S-DCI (e.g., Figure 2A , Figure 2B and / or Figure 2C ) has its own TDAI indication (where the second TDAI is reused) and what each TDAI should indicate.

[0026] Use below Figure 4 , Figure 5 and Figure 6Various solutions to the above problems related to STxMP using m-DCI or S-DCI are described in detail. Figure 3A and Figure 3B , Figure 4 An example flow chart of operations that may be performed by a UE according to an embodiment described herein is shown. As shown in flow chart 400, at 402, the UE may receive m-DCI for STxMP. As described herein, in Release 16, simultaneous reception of PDSCH is supported, and when two PDSCHs are scheduled via multiple TRPs with two different coresetPoolIndex values ​​in ControlResourceSet, as described in Section 5.1.6.2 of 3GPP TS38.213, the UE cannot assume different DM-RS configurations with respect to the actual number of pre-loaded DM-RS symbols, the actual number of additional DM-RS symbols, the actual DM-RS symbol positions, and the DM-RS configuration type. The UE also cannot assume that the DM-RS ports in a CDM group are indicated by two TCI states.

[0027] At 404, the UE may determine whether the m-DCI received by the UE at 402 indicates that the UE is utilizing a PUSCH that is completely or partially overlapped in the time domain and the frequency domain (such as, for example, Figure 2A and / or Figure 2C Based on determining at 404 that the m-DCI received by the UE at 402 indicates that the UE is using a PUSCH (such as, for example, a PUSCH that is completely or partially overlapped in the time domain and the frequency domain) through multiple physical downlink control channels (PDCCHs) (or at least two PDCCHs) with different coresetPoolIndex values. Figure 2A and / or Figure 2C ), the UE may use 406, 408 and / or 410 to perform the operations described herein.

[0028] At 406, based on determining at 404 that the m-DCI received by the UE at 402 indicates that the UE is utilizing a PUSCH that is completely or partially overlapping in the time domain and the frequency domain (such as, for example, Figure 2A and / or Figure 2C), the UE may schedule each PUSCH transmission of the STxMP based on the associated DM-RS according to the UE capabilities. In some embodiments, and as a non-limiting example, at 404, the scheduler of the UE may need to verify that the DM-RS indication associated with each PUSCH of the STxMP has DM-RS symbols that are aligned in time. In other words, except for the total number of DMRS symbols including the additional DMRS symbols, the symbol positions of the DM-RS symbols for each PUSCH of the STxMP must be the same.

[0029] Additionally or alternatively, the scheduler of the UE may also verify that the DMRS configuration type associated with each DMRS indication is also the same at 404. In other words, the DMRS configuration type for all DMRS indications needs to be DMRS configuration type-1 or DMRS configuration type-2.

[0030] In some implementations, at 404, the scheduler of the UE may also verify that the DM-RS ports of the two PUSCHs used for STxMP belong to different CDM groups indicated by the two TCI states.

[0031] In some embodiments, based on specific UE capabilities, the UE's scheduler may ignore verifying the time alignment of DMRS symbols, the configuration type corresponding to each DMRS indication, and / or the CDM groups associated with the DM-RS ports.

[0032] In some embodiments, at 404, the scheduler of the UE may also verify that each PUSCH of the STxMP is scheduled by the intra-slot FH, or that the PUSCH without the STxMP is scheduled by the intra-slot FH. A single bit in the DCI may indicate whether the FH is enabled, and the UE may be configured with inter-slot FH or intra-slot FH. When the UE is configured with intra-slot FH, the number of DMRS symbols and / or the position corresponding to the DMRS symbols may change. Therefore, when each PUSCH of the STxMP is scheduled by the intra-slot FH, the DM-RS symbols are still aligned in time. Additionally or alternatively, the scheduler of the UE may also verify whether the inter-slot FH is used to schedule at least one PUSCH of the STxMP, and no FH is mentioned for the other remaining PUSCHs of the STxMP.

[0033] In some embodiments, at 408, the UE may multiplex two or more HARQ-ACKs based on the total number of HARQ-ACKs for multiplexing (as described in the TDAI bit field of each DCI of the m-DCI received at 402). As a non-limiting example, the TDAI bit field of each DCI in the multiple DCIs may correspond to an associated TRP in the multiple TRPs. When there are overlapping PUSCHs and PUCCHs, instead of multiplexing the PUSCH only when the UL TDAI is not equal to 4, the UE may multiplex the HARQ-ACK to each PUSCH of the STxMP independently. In other words, the UE may multiplex the HARQ-ACK for each TRP based on the TDAI bit field value of the DCI to which it corresponds.

[0034] For example, Figure 3A As shown in diagram 300a, UE 302 may have two TRPs, and the UE may perform UL transmissions to both TRPs using, for example, panel 1 304 and panel 2 306. UE 302 may receive DCI DCI1 308 corresponding to a first TRP associated with panel 1 304, and DCI DCI2 310 corresponding to a second TRP associated with panel 2 306. As shown in diagram 300a, the UE may be scheduled for UL transmission 312 including PUCCH1 316 and PUSCH1 318 that overlap in time via panel 1 304. In addition, UE 302 may be scheduled for UL transmission 314 including PUSCH1 320 via panel 2 306. UL transmissions 312 and 314 overlap in time. As a non-limiting example, the TDAI in DCI2 310 may indicate no HARQ-ACK multiplexing, while the TDAI in DCI1 308 may indicate HARQ-ACK multiplexing. Therefore, as described herein, the UE may multiplex HARQ-ACK independently to each PUSCH, as specified in the TDAI field of each DCI of the TRP.

[0035] In another example, if Figure 3BAs shown in diagram 300b, UE 322 may have two TRPs, and the UE may perform UL transmissions to both TRPs using, for example, panel 1 324 and panel 2 326. UE 302 may receive DCI DCI1 328 corresponding to a first TRP associated with panel 1 324, and DCI DCI2 330 corresponding to a second TRP associated with panel 2 326. As shown in diagram 300b, the UE may be scheduled via panel 1 324 for UL transmission 332 including PUCCH1 336 and PUSCH1 338 that do not overlap in time. Additionally, UE 322 may be scheduled via panel 2 326 for UL transmission 334 including PUSCH1 340. UL transmissions 332 and 334 overlap in time. As a non-limiting example, the TDAI in DCI2 330 may indicate HARQ-ACK multiplexing, while the TDAI in DCI1 328 may indicate no HARQ-ACK multiplexing. Thus, as described herein, the UE may multiplex HARQ-ACK to each PUSCH independently, as specified in the TDAI field of each DCI of the TRP.

[0036] In some embodiments, at 408, at least when simultaneous transmission of PUSCH and PUCCH is not allowed, the TDAI bit field of the DCI on the first panel (or first TRP) of the m-TRP may indicate the total number of HARQ-ACK bits from the first panel (or first TRP) and the second panel (or second TRP) to be multiplexed on the PUSCH on the first panel of the m-TRP. For example, as shown in Figure 300b, PUCCH1 336 and PUSCH1 340 are transmitted by different TRPs. PUCCH1 336 and PUSCH1 340 overlap in time. Therefore, since the TDAI in DCI2 330 indicates the multiplexing of HARQ-ACK on PUSCH, HARQ-ACK for PUCCH1 336 and PUSCH1 340 can be multiplexed.

[0037] In some embodiments, additionally or alternatively, when the channel state information (CSI) carried by the physical uplink control channel resources on the second panel (or second TRP) overlaps with the PUSCH on the first panel (or first TRP), if the CSI type of the channel state information (CSI) carried by the PUCCH resources on the second panel (or second TRP) is the same as the CSI type of the PUCCH resources on the first panel (or first TRP), the UE may discard the CSI carried by the PUCCH resources on the second panel (or second TRP). In some embodiments, additionally or alternatively, the CSI carried by the PUCCH resources may be discarded, and only HARQ-ACK may be multiplexed by the UE.

[0038] In some embodiments, at 410, the UE may determine the transmission of the PUSCH based on the corresponding data priority or scheduling of each PUSCH of the STxMP. For example, for a direct grant (DG) or a configured grant (CG) of the PUSCH, the priority flag may indicate the data priority of the PUSCH. The priority indication may be used for cancellation within the UE. In other words, a low priority UL transmission may be canceled and replaced by a high priority UL transmission. As a non-limiting example, in some embodiments, the UE may transmit two PUSCHs of the same or different priorities of the STxMP based on the UE capabilities. The UE capabilities may indicate the behavior of the UE with respect to the simultaneous transmission of PUSCHs of the same or different priorities.

[0039] In some embodiments, alternatively or additionally, the UE may transmit only a high priority PUSCH and discard or cancel the low priority PUSCH used for transmission. In addition, the cancellation of the low priority PUSCH used for transmission may be based on a cancellation timeline, which may be further based on partial or complete cancellation according to UE capabilities. As a non-limiting example, the complete cancellation and / or partial cancellation of the low priority PUSCH may be based on the last symbol of the DCI scheduling of the high priority PUSCH and the first symbol of the low priority PUSCH, and / or the start time of the first symbol of the high priority PUSCH and the low priority PUSCH. Additionally or alternatively, the partial cancellation of the low priority PUSCH may be further based on additional symbols based on UE capabilities. In some embodiments, the UE capabilities may include or describe the simultaneous transmission of a low priority PUSCH or the cancellation of a low priority PUSCH.

[0040] In some embodiments, the total number of layers across the overlapping PUSCHs may not exceed a predetermined threshold number of layers, for example, four layers. Thus, the UE may transmit the PUSCH that is scheduled first. Additionally or alternatively, the UE may transmit a PUSCH whose associated DCI ends earlier than the DCI of other PUSCHs.

[0041] In some embodiments, the UE may implement actions with respect to the above-mentioned problems and various solutions to these problems according to a mutual agreement between the UE and a network (such as a core network or a radio access network), as discussed herein.

[0042] Figure 5 An example flow chart of operations that may be performed by a UE according to embodiments described herein is shown. As shown in flow chart 500, at 502, the UE may receive an s-DCI for STxMP. The s-DCI may schedule two simultaneous multi-panel PUSCHs. The s-DCI may include one or more TDAI bit fields.

[0043] At 504, the UE may transmit two or more HARQ-ACKs based on the total number of TDAI bits (bit fields) in the s-DCI. As a non-limiting example, a single TDAI bit field may indicate the total number of HARQ-ACKs that may be multiplexed on the PUSCH. Additionally or alternatively, for PUSCH repetitions, the HARQ-ACK may be multiplexed at each repetition. In some embodiments, when two or more TDAI bit fields in the s-DCI are used, the first TDAI bit field may be associated with the first PUSCH, and the second TDAI bit field may be associated with the second PUSCH. In addition, each TDAI bit field may indicate a HARQ-ACK bit associated with a PUCCH resource that overlaps in time with a corresponding PUSCH of the same TRP.

[0044] In some implementations, the UE may avoid PUCCH overlap with PUSCH scheduled by the s-DCI received at 502, and / or ignore the TDAI indication.

[0045] In some embodiments, at 506, the UE may transmit STxMP over multiple time slots according to a specific start and length indicator value (SLIV) for time domain multiplexing of the PUSCH. As described in Section 6.1.2 of 3GPP TS 38.214, the SLIV may be indicated in a time domain resource allocation (TDRA) bit field that refers to a row with multiple SLIVs. As a non-limiting example, the first two SLIVs within the indicated TDRA row may be used for STxMP, and the next two SLIVs may be used for STxMP in the next time slot (or time slots), and so on. Additionally or alternatively, the first SLIV and the third SLIV within the indicated TDRA row may be used for STxMP, and the second SLIV and the fourth SLIV may be used for STxMP in the next time slot (or time slots), and so on.

[0046] In some embodiments, the association between SLIVs and beams / TRPs may be indicated separately, for example using an SRS resource indicator (SRI) bit. For example, a first SLIV may be associated with a first beam / TRP and a second SLIV may be associated with a second beam / TRP, or vice versa. In some embodiments, the scheduler may also verify that the total number of SLIVs within the indicated TDRA row is an even number. Additionally or alternatively, the remaining SLIVs may be considered to be associated with the first indicated beam.

[0047] In some embodiments, the UE may implement actions with respect to the above-mentioned problems and various solutions to these problems according to a mutual agreement between the UE and a network (such as a core network or a radio access network), as discussed herein.

[0048] Figure 6An example flow chart of operations that may be performed by a base station according to the embodiments described herein is shown. As shown in flowchart 600, at 602, the base station may transmit m-DCI for STxMP to the UE. As a non-limiting example, the base station may transmit s-DCI for STxMP to the UE. STxMP may include multiple PUSCHs overlapping in the time domain and / or frequency domain. STxMP including multiple PUSCHs may be scheduled by multiple PDCCHs with different corresponding CORESET pool index values. At 604, the base station may schedule each PUSCH transmission of the STxMP based on the associated DM-RS symbol according to the UE capability information received from the UE.

[0049] At 606, the base station may schedule each PUSCH transmission of the STxMP by intra-slot frequency hopping (FH), or not schedule the PUSCH transmission of the STxMP by intra-slot FH, or schedule at least the PUSCH transmission of the STxMP by inter-slot FH and schedule the remaining one or more PUSCH transmissions of the STxMP without intra-slot FH or inter-slot FH. At 608, the base station may configure transmission of two or more HARQ-ACKs in a total downlink allocation indication (TDAI) bit field of each of the multiple DCIs.

[0050] As a non-limiting example, the base station may also configure the transmission of two or more HARQ-ACKs in the total number of total downlink allocation index (TDAI) bits in a single DCI. As described herein, according to some embodiments, a single TDAI bit may indicate multiplexing of two or more HARQ-ACKs, and multiple TDAI bits may indicate transmission of a HARQ-ACK associated with a physical uplink control channel (PUCCH) resource that overlaps in time with a corresponding PUSCH of the same TRP.

[0051] In some embodiments, the base station may configure transmission of STxMP over multiple slots according to a specific start and length indicator value (SLIV) for time domain multiplexing of PUSCH.

[0052] Embodiments contemplated herein include an apparatus having one or more elements for performing methods 400, 500, or 600. In the context of methods 400 or 500, the apparatus may be, for example, an apparatus of a UE (such as wireless device 802 as a UE, as described herein). In the context of method 600, the apparatus may be, for example, an apparatus of a base station (such as network device 820 as a base station, as described herein).

[0053] Embodiments contemplated herein include one or more non-transitory computer-readable media storing instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of methods 400, 500, or 600. In the context of methods 400 or 500, the non-transitory computer-readable medium may be, for example, a memory of a UE (such as memory 806 of wireless device 802 as a UE, as described herein). In the context of method 600, the non-transitory computer-readable medium may be, for example, a memory of a base station (such as memory 824 of network device 820 as a base station, as described herein).

[0054] Embodiments contemplated herein include an apparatus having logic, modules, or circuits for performing one or more elements of method 400, 500, or 600. In the context of method 400 or 500, the apparatus may be, for example, an apparatus of a UE (such as wireless device 802 as a UE, as described herein). In the context of method 600, the apparatus may be, for example, an apparatus of a base station (such as network device 820 as a base station, as described herein).

[0055] Embodiments contemplated herein include an apparatus having one or more processors and one or more computer-readable media using or storing instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of methods 400, 500, or 600. In the context of methods 400 or 500, the apparatus may be, for example, an apparatus of a UE (such as wireless device 802 as a UE, as described herein). In the context of method 600, the apparatus may be, for example, an apparatus of a base station (such as network device 820 as a base station, as described herein).

[0056] Embodiments contemplated herein include a signal described in or associated with one or more elements of methods 400 , 500 , or 600 .

[0057] Embodiments contemplated herein include a computer program or computer program product having instructions, wherein when the program is executed by a processor, the processor is caused to perform one or more elements of the method 400, 500, or 600. In the context of the method 400 or 500, the processor may be a processor of a UE (such as the processor 804 of the wireless device 802 as a UE, as described herein), and the instructions may be located, for example, in the processor and / or on a memory of the UE (such as the memory 806 of the wireless device 802 as a UE, as described herein). In the context of the method 600, the processor may be a processor of a base station (such as the processor 822 of the network device 820 as a base station, as described herein), and the instructions may be located, for example, in the processor and / or on a memory of the base station (such as the memory 824 of the network device 820 as a base station, as described herein).

[0058] Figure 7 An example architecture of a wireless communication system according to the embodiments described herein is shown. The following description is provided for an example wireless communication system 700 operating in conjunction with the LTE system standard and / or the 5G or NR system standard provided in the 3GPP technical specifications.

[0059] like Figure 7 As shown, wireless communication system 700 includes UE 702 and UE 704 (although any number of UEs may be used). In this example, UE 702 and UE 704 are illustrated as smartphones (e.g., handheld touch screen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device configured for wireless communication.

[0060] UE 702 and UE 704 may be configured to be communicatively coupled to RAN 706. In an embodiment, RAN 706 may be NG-RAN, E-UTRAN, etc. UE 702 and UE 704 utilize connections (or channels) (shown as connection 708 and connection 710, respectively) with RAN 706, where each connection (or channel) includes a physical communication interface. RAN 706 may include one or more base stations, such as base station 712 and base station 714, to implement connection 708 and connection 710.

[0061] In this example, connection 708 and connection 710 are air interfaces that enable such communicative coupling and may conform to the RAT used by the RAN 706 , such as, for example, LTE and / or NR.

[0062] In some embodiments, UE 702 and UE 704 may also directly exchange communication data via side link interface 716. UE 704 is shown as being configured to access an access point (shown as AP 718) via connection 720. As an example, connection 720 may include a local wireless connection, such as any connection conforming to the IEEE 802.11 protocol, wherein AP 718 may include a Wi-Fi ® In this example, AP 718 may not be connected to another network (eg, the Internet) through CN 724.

[0063] In an embodiment, UE 702 and UE 704 may be configured to communicate with each other or with base station 712 and / or base station 714 over a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals in accordance with various communication techniques, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication techniques (e.g., for downlink communications) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0064] In some embodiments, all or part of the base station 712 or the base station 714 may be implemented as one or more software entities running on a server computer as part of a virtual network. In addition, or in other embodiments, the base station 712 or the base station 714 may be configured to communicate with each other via the interface 722. In an embodiment where the wireless communication system 700 is an LTE system (e.g., when the CN 724 is an EPC), the interface 722 may be an X2 interface. The X2 interface may be defined between two or more base stations (e.g., two or more eNBs, etc.) connected to the EPC and / or between two eNBs connected to the EPC. In an embodiment where the wireless communication system 700 is an NR system (e.g., when the CN 724 is a 5GC), the interface 722 may be an Xn interface. The Xn interface is defined between two or more base stations (e.g., two or more gNBs, etc.) connected to the 5GC, between the base station 712 (e.g., gNB) and the eNB connected to the 5GC, and / or between two eNBs connected to the 5GC (e.g., CN 724).

[0065] RAN 706 is shown as being communicatively coupled to CN 724. CN 724 may include one or more network elements 726 configured to provide various data and telecommunication services to customers / subscribers (e.g., UE 702 and users of UE 704) connected to CN 724 via RAN 706. The components of CN 724 may be implemented in one physical device or separate physical devices, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).

[0066] In an embodiment, CN 724 may be an EPC, and RAN 706 may be connected to CN 724 via an S1 interface 728. In an embodiment, S1 interface 728 may be divided into two parts: an S1 user plane (S1-U) interface, which carries traffic data between base station 712 or base station 714 and a serving gateway (S-GW); and an S1-MME interface, which is a signaling interface between base station 712 or base station 714 and a mobility management entity (MME).

[0067] In an embodiment, CN 724 may be a 5GC, and RAN 706 may be connected to CN 724 via an NG interface 728. In an embodiment, NG interface 728 may be divided into two parts: an NG user plane (NG-U) interface, which carries traffic data between base station 712 or base station 714 and a user plane function (UPF); and an S1 control plane (NG-C) interface, which is a signaling interface between base station 712 or base station 714 and an access and mobility management function (AMF).

[0068] Generally speaking, the application server 730 may be an element that provides applications that use Internet Protocol (IP) bearer resources with the CN 724 (e.g., packet-switched data services). The application server 730 may also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE 702 and the UE 704 via the CN 724. The application server 730 may communicate with the CN 724 via an IP communication interface 732.

[0069] Figure 8 A system 800 for performing signaling 838 between a wireless device 802 and a network device 820 according to embodiments described herein is shown. The system 800 may be part of a wireless communication system as described herein. For example, the wireless device 802 may be a UE of the wireless communication system. The network device 820 may be, for example, a base station (e.g., an eNB or a gNB) of the wireless communication system.

[0070] The wireless device 802 may include one or more processors 804. The processor 804 may execute instructions to perform various operations of the wireless device 802, as described herein. The processor 804 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0071] The wireless device 802 may include a memory 806. The memory 806 may be a non-transitory computer-readable storage medium that stores instructions 808 (which may include, for example, instructions executed by the processor 804). The instructions 808 may also be referred to as program code or a computer program. The memory 806 may also store data used by the processor 804 and results computed by the processor.

[0072] The wireless device 802 may include one or more transceivers 810, which may include radio frequency (RF) transmitter and / or receiver circuitry that uses an antenna 812 of the wireless device 802 to facilitate signaling (e.g., signaling 838) transmitted and / or received by the wireless device 802 with other devices (e.g., network device 820) according to a corresponding RAT.

[0073] The wireless device 802 may include one or more antennas 812 (e.g., one, two, four, or more). For implementations with multiple antennas 812, the wireless device 802 may take advantage of the spatial diversity of these multiple antennas 812 to send and / or receive multiple different data streams on the same time-frequency resources. This behavior may be referred to as, for example, multiple-input multiple-output (MIMO) behavior (referring to the multiple antennas used at each of the transmitting device and the receiving device to implement this aspect). MIMO transmissions by the wireless device 802 may be implemented based on precoding (or digital beamforming) applied to the wireless device 802, which multiplexes the data streams between the antennas 812 based on known or assumed channel characteristics so that each data stream is received at an appropriate signal strength relative to the other streams and at a desired location in the spatial domain (e.g., the location of the receiver associated with the data stream). Some implementations may use a single-user MIMO (SU-MIMO) approach (in which the data streams are all directed to a single receiver) and / or a multi-user MIMO (MU-MIMO) approach (in which separate data streams may be directed to separate (different) receivers in different locations in the spatial domain).

[0074] In some embodiments with multiple antennas, the wireless device 802 may implement analog beamforming techniques whereby the phases of signals transmitted by the antennas 812 are relatively adjusted so that the (joint) transmissions of the antennas 812 may be directional (this is sometimes referred to as beam steering).

[0075] The wireless device 802 may include one or more interfaces 814. The interface 814 may be used to provide input to the wireless device 802 or output from the wireless device. For example, a wireless device 802 that is a UE may include an interface 814, such as a microphone, a speaker, a touch screen, buttons, etc., to allow a user of the UE to input and / or output to the UE. Other interfaces of such a UE may be composed of transmitters, receivers, and other circuits (for example, in addition to the transceiver 810 / antenna 812 described above), which allow the UE to communicate with other devices and may communicate according to known protocols (for example, Wi-Fi ® ,Bluetooth ® etc.) work.

[0076] The wireless device 802 may include an STxMP module 816. The STxMP module 816 may be implemented via hardware, software, or a combination thereof. For example, the STxMP module 816 may be implemented as a processor, circuit, and / or instructions 808 stored in the memory 806 and executed by the processor 804. In some examples, the STxMP module 816 may be integrated within the processor 804 and / or the transceiver 810. For example, the STxMP module 816 may be implemented by a combination of software components (e.g., executed by a DSP or general purpose processor) and hardware components (e.g., logic gates and circuits) within the processor 804 or the transceiver 810.

[0077] From the perspective of the UE, the STxMP module 816 may be used in various aspects of the present disclosure, for example, Figure 4-Figure 6 all aspects.

[0078] The network device 820 may include one or more processors 822. The processor 822 may execute instructions to perform various operations as described herein for the network device 820. The processor 822 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0079] The network device 820 may include a memory 824. The memory 824 may be a non-transitory computer-readable storage medium that stores instructions 826 (which may include, for example, instructions executed by the processor 822). The instructions 826 may also be referred to as program code or a computer program. The memory 824 may also store data used by the processor 822 and results calculated by the processor.

[0080] The network device 820 may include one or more transceivers 828, which may include RF transmitter and / or receiver circuitry that uses an antenna 830 of the network device 820 to facilitate signaling (e.g., signaling 838) transmitted or received by the network device 820 with other devices (e.g., wireless device 802) according to a corresponding RAT.

[0081] The network device 820 may include one or more antennas 830 (eg, one, two, four, or more). In embodiments with multiple antennas 830, the network device 820 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc. as described above.

[0082] The network device 820 may include one or more interfaces 832. The interface 832 may be used to provide input to or output from the network device 820. For example, the network device 820 as a base station may include an interface 832 composed of a transmitter, a receiver, and other circuits (e.g., in addition to the transceiver 828 / antenna 830 described above), which enables the base station to communicate with other equipment in the core network and / or enables the base station to communicate with an external network, computer, database, etc., in order to achieve the purpose of performing operations, management, and maintenance of the base station or other equipment operably connected to the base station.

[0083] The network device 820 may include an STxMP module 834. The STxMP module 834 may be implemented via hardware, software, or a combination thereof. For example, the STxMP module 834 may be implemented as a processor, circuit, and / or instructions 826 stored in the memory 824 and executed by the processor 822. In some examples, the STxMP module 834 may be integrated within the processor 822 and / or the transceiver 828. For example, the STxMP module 834 may be implemented by a combination of software components (e.g., executed by a DSP or general purpose processor) and hardware components (e.g., logic gates and circuits) within the processor 822 or the transceiver 828.

[0084] From the perspective of the base station, the STxMP module 834 may be used in various aspects of the present disclosure, for example, Figure 4-Figure 6 all aspects.

[0085] For one or more embodiments, at least one of the components set forth in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as described herein. For example, a baseband processor as described herein in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples set forth herein. For another example, circuits associated with a UE, a base station, a network element, etc. as described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples set forth herein.

[0086] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in view of the above teachings or may be obtained from the practice of the various embodiments.

[0087] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine executable instructions to be executed by a computer system. A computer system may include one or more general or special purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic components for performing operations; or may include a combination of hardware, software, and / or firmware.

[0088] The systems described herein relate to specific embodiments, but are provided as examples. These embodiments may be combined into a single system, partially combined into other systems, divided into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of another embodiment may be used in one embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in one or more embodiments, and it should be recognized that unless explicitly stated herein, these parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment.

[0089] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0090] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and the apparatus described herein. Therefore, the embodiments of the present invention should be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: Transceiver; as well as A processor, the processor being configured to: receiving, via the transceiver, a plurality of DCIs for simultaneous multi-panel physical uplink shared channel (PUSCH) transmissions (STxMP); determining that the UE is scheduled via a plurality of physical downlink control channels (PDCCHs) having different associated control resource set (CORSET) pool index values ​​using the STxMPs overlapping in time and frequency domains; as well as In response to the determination: Scheduling each PUSCH transmission of the STxMP based on an associated downlink modulation reference symbol (DMRS) according to UE capabilities; multiplexing two or more Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) according to a total number of HARQ-ACKs described in a Total Downlink Assignment Index (TDAI) bit field of each DCI in the plurality of DCIs; and The transmission of PUSCH is determined based on the corresponding data priority or scheduling of each PUSCH of the STxMP. 2 . The UE according to claim 1 , wherein the STxMP partially or completely overlaps in the time domain and the frequency domain.

3. The UE of claim 1, wherein the processor is configured to verify that the associated DMRS of each PUSCH transmission is aligned in time so as to schedule each PUSCH transmission of the STxMP according to the UE capabilities. 4 . The UE of claim 3 , wherein a total number of DMRSs and corresponding positions of the DMRSs are the same for each PUSCH transmission of the STxMP.

5. The UE of claim 1, wherein the processor is configured to verify that a DMRS configuration type of the associated DMRS for each PUSCH transmission is the same for each PUSCH transmission for scheduling the STxMP according to the UE capability.

6. The UE according to claim 1, wherein the processor is configured to: It is verified that a first DMRS port for a first PUSCH transmission belongs to a first CDM group and a second DMRS port for a second PUSCH transmission belongs to a second CDM group, the first CDM group being different from the second CDM group. 7 . The UE of claim 1 , wherein the processor is configured to verify that each PUSCH transmission of the STxMP is scheduled for transmission by intra-slot frequency hopping (FH) or that no PUSCH transmission of the STxMP is scheduled for transmission by intra-slot FH.

8. The UE of claim 1, wherein the processor is configured to verify that at least one PUSCH transmission of the STxMP is scheduled for transmission via inter-slot frequency hopping (FH), and no FH is indicated for remaining one or more PUSCH transmissions of the STxMP.

9. The UE of claim 1, wherein in order to multiplex the two or more HARQ-ACKs according to the total number of HARQ-ACKs described in the total downlink assignment index (TDAI) bit field of each DCI in the multiple DCIs, the processor is configured to independently multiplex the HARQ-ACKs corresponding to each PUSCH.

10. The UE of claim 1, wherein the TDAI bit field of each of the plurality of DCIs corresponds to an associated TRP of a plurality of transmission reception points (TRPs).

11. The UE according to claim 1, wherein: The TDAI bit field of a DCI in the plurality of DCIs corresponds to a Transmission Reception Point (TRP) in a plurality of TRPs; and The TDAI bit field indicates a total number of HARQ-ACK bits from two or more TRPs among the multiple TRPs, and the processor is configured to independently multiplex the HARQ-ACK corresponding to each PUSCH.

12. The UE according to claim 11, wherein: The processor is configured to multiplex the HARQ-ACK from the first TRP and the second TRP based on that simultaneous transmission of a PUSCH on a first TRP among the multiple TRPs and a physical uplink control channel (PUCCH) on a second TRP among the multiple TRPs is not allowed.

13. The UE according to claim 12, wherein the processor is configured to: According to channel state information (CSI) carried by a physical uplink control channel (PUCCH) on a first TRP of the plurality of TRPs that overlaps with the PUSCH on the second TRP of the plurality of TRPs: Dropping the PUCCH when another PUCCH on the second TRP has the same CSI type as the CSI type of the PUCCH on the first TRP; or The PUCCH on the first TRP is multiplexed with the PUSCH on the second TRP.

14. The UE according to claim 1, wherein: The transmission of the PUSCH is based on the corresponding data priority of each PUSCH in the PUSCH or the scheduling is based on the UE capability corresponding to the STxMP with different data priorities, and the UE capability includes simultaneous transmission of the PUSCH, or cancellation of the transmission of the PUSCH with lower data priority in the PUSCH based on a cancellation timeline according to partial cancellation or complete cancellation.

15. The UE of claim 1, wherein transmission of a PUSCH is further based on a start time of a DCI associated with the PUSCH. 16 . The UE according to claim 1 , wherein a total number of data layers overlapped in the time domain and the frequency domain of the STxMP does not exceed four.

17. A user equipment (UE), the user equipment (UE) comprising: Transceiver; as well as A processor, the processor being configured to: receiving, via the transceiver, a single downlink control information (DCI) for a simultaneous multi-panel physical uplink shared channel (PUSCH) transmission (STxMP); transmitting two or more HARQ-ACKs according to a total number of total downlink allocation index (TDAI) bits in the single DCI, the single TDAI bit indicating multiplexing of the two or more HARQ-ACKs, and the plurality of TDAI bits indicating transmitting the HARQ-ACKs associated with physical uplink control channel (PUCCH) resources that temporally overlap with corresponding PUSCHs of the same transmission reception point (TRP); and The STxMP is transmitted over multiple slots according to a specific start and length indicator value (SLIV) for time domain multiplexing of the PUSCH. The UE according to claim 17 , wherein the PUCCH does not overlap with the PUSCH.

19. A base station, comprising: Transceiver; as well as A processor, the processor being configured to: transmitting, via the transceiver, a plurality of DCIs for simultaneous multi-panel physical uplink shared channel (PUSCH) transmissions (STxMP) to a user equipment (UE); and In response to the UE being scheduled via a plurality of physical downlink control channels (PDCCHs) having different associated control resource set (CORSET) pool index values ​​with the STxMPs overlapping in time and frequency domains: scheduling each PUSCH transmission of the STxMP based on an associated downlink modulation reference symbol (DMRS) according to UE capability information received from the UE; scheduling each PUSCH transmission of the STxMP by intra-slot frequency hopping (FH), or scheduling the PUSCH transmission of the STxMP without intra-slot FH, or scheduling at least the PUSCH transmission of the STxMP by inter-slot FH and scheduling the remaining one or more PUSCH transmissions of the STxMP without intra-slot FH or inter-slot FH; and Transmission of two or more HARQ-ACKs is configured in a total downlink assignment index (TDAI) bit field of each DCI in the plurality of DCIs.

20. The base station according to claim 19, wherein: The processor is configured to: transmitting, via the transceiver, to the UE a single downlink control information (DCI) for simultaneous STxMPs; and configuring the transmission of the two or more HARQ-ACKs in a total number of total downlink allocation index (TDAI) bits in the single DCI, a single TDAI bit indicating multiplexing of the two or more HARQ-ACKs, and a plurality of TDAI bits indicating that the transmission of the HARQ-ACKs is associated with a physical uplink control channel (PUCCH) resource that temporally overlaps with a corresponding PUSCH of the same transmission reception point (TRP); and Transmission of the STxMP over multiple time slots is configured according to a specific start and length indicator value (SLIV) for time domain multiplexing of the PUSCH.

Images