Apparatus and method for UL transmission in multi-TRP scene

Abstract

The present disclosure provides an apparatus and method for UL transmission in a multi-TRP scenario. An apparatus for a UE may include an RF interface circuit configured to receive DCI from a TRP, the DCI to schedule PUCCH transmissions to a plurality of TRPs; and a processing circuit coupled with the RF interface circuit and configured to: encode and multiplex a plurality of PUCCH repetitions targeting a plurality of TRP on the one or more PUCCH resources based on PUCCH repetition related configuration information indicated by the DCI or higher layer signaling; and providing the encoded and multiplexed PUCCH repetition to an RF interface circuit for transmission over one or more PUCCH resources to a plurality of TRPs.

Description

[0001] This application is a divisional application of the invention patent application with the application date of June 18, 2021, the application number of 202110680163.9, and the title of “Apparatus and Method for UL Transmission in Multi-TRP Scenarios”. TECHNICAL FIELD

[0002] Embodiments of the present disclosure generally relate to wireless communications, and in particular, to apparatus and methods for physical uplink control channel (PUCCH) and physical uplink shared channel (PUSCH) transmission in multi-transmission reception point (TRP) scenarios with single downlink control information (DCI). BACKGROUND

[0003] In fifth generation (5G) or new radio (NR) mobile communications, it is important to allow dynamic switching between single-TRP and multi-TRP transmissions to make the coordinated multipoint (CoMP) scheme more useful. In 3GPP Technical Specification Release 16 for 5G / NR systems (hereinafter referred to as “5G / NR Rel-16”), multi-TRP related operations are mainly introduced for physical downlink shared channel (PDSCH) transmission. Depending on different backhaul assumptions (e.g., ideal backhaul assumption and non-ideal backhaul assumption), the multi-TRP related operations can include single-DCI operation and multi-DCI operation.

[0004] The multi-DCI operation can correspond to the non-ideal backhaul assumption. With multiple DCIs, each TRP can have one physical downlink control channel (PDCCH) for scheduling the corresponding PDSCH transmission. The single-DCI operation can correspond to the ideal backhaul assumption. With a single DCI, a single PDCCH can be used to schedule multiple PDSCH transmissions from multiple TRPs. SUMMARY

[0005] One aspect of the disclosure provides a method for wireless communication, comprising: receiving, at a user equipment (UE), a medium access control-control element (MAC-CE) for activation / deactivation of physical uplink control channel (PUCCH) spatial relations, the MAC-CE comprising: a first group of octets, wherein a first octet contains an identifier of a first PUCCH resource, a second octet contains a first spatial relation information identifier for the first PUCCH resource, and a third octet contains a second spatial relation information identifier for the first PUCCH resource; and a second group of octets comprising a fourth octet and a fifth octet, the fourth octet containing an identifier of a second PUCCH resource, the fifth octet containing a third spatial relation information identifier for the second PUCCH resource, and the second group of octets comprising an indication bit indicating whether one spatial relation or two spatial relations are to be activated for the second PUCCH resource; and causing, at the UE, spatial relations indicated by the first spatial relation information identifier and the second spatial relation information identifier to be activated for the first PUCCH resource, and a spatial relation indicated by the third spatial relation information identifier to be activated for the second PUCCH resource.

[0006] Another aspect of the disclosure provides an apparatus for a user equipment (UE), comprising radio frequency (RF) interface circuitry and processing circuitry coupled with the RF interface circuitry, wherein the RF interface circuitry is configured to receive a medium access control-control element (MAC-CE) for activation / deactivation of physical uplink control channel (PUCCH) spatial relations, the MAC-CE comprising: a first group of octets, wherein a first octet contains an identifier of a first PUCCH resource, a second octet contains a first spatial relation information identifier for the first PUCCH resource, and a third octet contains a second spatial relation information identifier for the first PUCCH resource, and a second group of octets comprising a fourth octet and a fifth octet, the fourth octet containing an identifier of a second PUCCH resource, the fifth octet containing a third spatial relation information identifier for the second PUCCH resource, and the second group of octets comprising an indication bit indicating whether one spatial relation or two spatial relations are to be activated for the second PUCCH resource; and wherein the processing circuitry is configured to cause spatial relations indicated by the first spatial relation information identifier and the second spatial relation information identifier to be activated for the first PUCCH resource, and a spatial relation indicated by the third spatial relation information identifier to be activated for the second PUCCH resource. BRIEF DESCRIPTION OF DRAWINGS

[0007] Embodiments of the present disclosure will be described herein below by way of example with reference to the attached drawings, wherein like reference numerals refer to similar elements throughout.

[0008] Figure 1 Exemplary multi-TRP related operations for downlink transmission according to some embodiments of the present disclosure are shown.

[0009] Figure 2 An example of an information element (IE) including PUCCH repetition related configuration information according to various embodiments of the present disclosure is shown. PUCCH-Resource

[0010] Figure 3 An example of a PUCCH spatial relation activation / deactivation medium access control-control element (MAC-CE) according to various embodiments of the present disclosure is shown.

[0011] Figure 4 An example of an enhanced PUCCH spatial relation activation / deactivation MAC-CE according to various embodiments of the present disclosure is shown.

[0012] Figure 5 An example of a PUCCH spatial relation activation / deactivation MAC-CE for a single PUCCH resource with multiple activated spatial relations according to various embodiments of the present disclosure is shown.

[0013] Figure 6 An example of a PUCCH spatial relation activation / deactivation MAC-CE for multiple PUCCH resources according to various embodiments of the present disclosure, where each PUCCH resource has multiple activated spatial relations.

[0014] Figure 7 An example of a PUCCH spatial relation activation / deactivation MAC-CE for multiple PUCCH resources with explicit group ID according to various embodiments of the present disclosure, where each PUCCH resource has a single activated spatial relation.

[0015] Figure 8 An example of a PUCCH spatial relation activation / deactivation MAC-CE for PUCCH resources with multiple activated spatial relations with explicit group ID according to various embodiments of the present disclosure is shown.

[0016] Figure 9 An example of a PUCCH spatial relation activation / deactivation MAC-CE for multiple PUCCH resources with explicit group ID according to various embodiments of the present disclosure, where each PUCCH resource has multiple activated spatial relations.

[0017] ​Figure 10 An example of a PUCCH spatial relation activation / deactivation MAC-CE for PUCCH resources with one or more activated spatial relations is shown in accordance with various embodiments of the present disclosure.

[0018] Figure 11 An example of a PUCCH spatial relation activation / deactivation MAC-CE for a mix of one or more PUCCH resources with a single activated spatial relation per PUCCH resource and one or more PUCCH resources with multiple activated spatial relations per PUCCH resource is shown in accordance with various embodiments of the present disclosure.

[0019] Figure 12 Another example of a PUCCH spatial relation activation / deactivation MAC-CE for a mix of one or more PUCCH resources with a single activated spatial relation per PUCCH resource and one or more PUCCH resources with multiple activated spatial relations per PUCCH resource is shown in accordance with various embodiments of the present disclosure.

[0020] Figure 13 An example of frequency division multiplexing (FDM) based PUCCH repetition with a single PUCCH resource is shown in accordance with various embodiments of the present disclosure.

[0021] Figure 14 An example of FDM based PUCCH repetition with multiple PUCCH resources is shown in accordance with various embodiments of the present disclosure.

[0022] Figure 15 An example of time division multiplexing (TDM) based PUCCH repetition with a single PUCCH resource is shown in accordance with various embodiments of the present disclosure.

[0023] Figure 16 An example of TDM based PUCCH repetition with multiple PUCCH resources is shown in accordance with various embodiments of the present disclosure.

[0024] Figure 17 An example of space division multiplexing (SDM) based PUCCH repetition with multiple PUCCH resources is shown in accordance with various embodiments of the present disclosure.

[0025] Figure 18 An example procedure at a user equipment (UE) associated with transmission of PUCCH repetition in a multi-TRP scenario with single DCI is shown in accordance with various embodiments of the present disclosure.

[0026] Figure 19An example procedure at a TRP associated with transmission of PUCCH repetition in a multi-TRP scenario with single DCI is shown in accordance with various embodiments of the present disclosure.

[0027] Figure 20 An example of inter-repetition frequency hopping for TDM-based PUSCH repetition with same frequency resource allocation size is shown in accordance with various embodiments of the present disclosure.

[0028] Figure 21 An example of inter-repetition frequency hopping for TDM-based PUSCH repetition with same frequency resource allocation size is shown in accordance with various embodiments of the present disclosure.

[0029] Figure 22 An example of inter-repetition frequency hopping for TDM-based PUSCH repetition with same frequency resource allocation size is shown in accordance with various embodiments of the present disclosure.

[0030] Figure 23 An example of inter-repetition frequency hopping for TDM-based PUSCH repetition with different frequency resource allocation size is shown in accordance with various embodiments of the present disclosure.

[0031] Figure 24 An example of inter-repetition frequency hopping for TDM-based PUSCH repetition with different frequency resource allocation size is shown in accordance with various embodiments of the present disclosure.

[0032] Figure 25 An example of inter-repetition frequency hopping for TDM-based PUSCH repetition with different frequency resource allocation size is shown in accordance with various embodiments of the present disclosure.

[0033] Figure 26 An example procedure at a UE associated with transmission of TDM-based PUSCH repetition in a multi-TRP scenario with single DCI is shown in accordance with various embodiments of the present disclosure.

[0034] Figure 27 An example network is shown in accordance with various embodiments of the present disclosure.

[0035] Figure 28 A wireless network is schematically illustrated in accordance with various embodiments of the present disclosure.

[0036] Figure 29 is a block diagram that shows a component that is capable of reading instructions from a machine- or computer- readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, in accordance with some example embodiments. DETAILED DESCRIPTION

[0037] Various aspects of the illustrative embodiments will be described using terminology commonly employed by those skilled in the art to convey the essence of this disclosure to others skilled in the art. However, it will be readily understood by those skilled in the art that many alternative embodiments can be practiced using portions of the described aspects. Specific figures, materials, and configurations are set forth for illustrative purposes to provide a thorough understanding of the illustrative embodiments. However, it will be readily understood by those skilled in the art that alternative embodiments can be practiced without these specific details. In other instances, well-known features may be omitted or simplified to avoid obscuring the illustrative embodiments.

[0038] Furthermore, the various operations will be described as multiple discrete operations in a manner most conducive to understanding the illustrative embodiments; however, the order of description should not be construed as implying that these operations must depend on the order. In particular, these operations do not need to be performed in the order presented.

[0039] The phrases “in an embodiment,” “in one embodiment,” and “in some embodiments” are used repeatedly throughout this document. These phrases do not typically refer to the same embodiment; however, they may refer to the same embodiment. Unless the context otherwise specifies, the terms “comprising,” “having,” and “including” are synonyms. The phrases “A or B” and “A / B” mean “(A), (B) or (A and B).”

[0040] In 5G / NR Rel-16, multi-TRP related operations were introduced primarily for PDSCH transmission. Depending on different backhaul assumptions (e.g., ideal backhaul assumption and non-ideal backhaul assumption), multi-TRP related operations can include single DCI operations and multi-DCI operations. Multi-DCI operations can correspond to the non-ideal backhaul assumption. Using multiple DCIs, each TRP can have one PDCCH for scheduling the corresponding PDSCH transmission. Single DCI operations can correspond to the ideal backhaul assumption. Using a single DCI, a single PDCCH can be used to schedule multiple PDSCH transmissions from multiple TRPs.

[0041] Figure 1 Exemplary multi-TRP related operations for downlink transmission according to some embodiments of this disclosure are illustrated. As an example, two TRPs (TRP #A and TRP #B) are provided to communicate with a UE having multiple antenna panels. Figure 1As shown, for the ideal backhaul assumption, a single PDCCH carrying a single DCI from TRP #A can schedule both a PDSCH transmission from TRP #A to the UE (PDSCH #1) and a PDSCH transmission from TRP #B to the UE (PDSCH #2); for the non-ideal backhaul assumption, TRP #A can have PDCCH #1 for scheduling the corresponding PDSCH transmission from TRP #A to the UE (PDSCH #1), while TRP #B can have PDCCH #2 for scheduling the corresponding PDSCH transmission from TRP #B to the UE (PDSCH #2).

[0042] As mentioned above, the multi-TRP related operations can include single-DCI operation and multi-DCI operation. On the other hand, the multi-TRP related operations can include multi-TRP related operations for downlink (e.g., PDSCH) and multi-TRP related operations for uplink (e.g., PUSCH). In 5G / NR Rel-16, the multi-TRP related operations are mainly introduced for PDSCH transmission, but the multi-TRP related operations for PUCCH and PUSCH transmission are not defined. In this application, the multi-TRP related operations for PUCCH and PUSCH transmission with single DCI will be discussed in detail.

[0043] Generally, for PUCCH transmission in multi-TRP scenario with single DCI, the PUCCH can be transmitted by repetition for different TRPs to improve communication reliability. The TRPs can be configured with the same cell identifier (ID) or different cell IDs. The type of PUSCH repetition can be frequency-division multiplexing (FDM) based PUSCH repetition, time-division multiplexing (TDM) based PUSCH repetition, or space-division multiplexing (SDM) based PUSCH repetition, which will be described in detail later. It should be noted that the UE can support a certain type of PUSCH repetition, so the UE can need to report the UE's capability on supporting which type of PUSCH repetition to the TRP or higher layer.

[0044] According to some embodiments of the present disclosure, the UE can encode and multiplex PUCCH repetitions targeting multiple TRPs on one or more PUCCH resources based on PUCCH repetition related configuration information indicated by DCI or higher layer signaling. The PUCCH repetition related configuration information can include an indication on whether to enable PUCCH repetition, the type of PUCCH repetition when PUCCH repetition is enabled, and the number of PUCCH repetitions. The type of PUCCH repetition can include FDM based PUCCH repetition, TDM based PUCCH repetition, or SDM based PUCCH repetition.

[0045] In one example, the higher layer signaling can be radio resource control (RRC) signaling, and at least one or more components of the PUCCH repetition related configuration information can be set in a RRC information element (IE) PUCCH-Config In one example, the PUCCH repetition related configuration information can be configured on a PUCCH resource set level, or on a PUCCH resource level, or on a PUCCH format level.

[0046] Figure 2 An example of an information element (IE) including PUCCH repetition related configuration information according to various embodiments of the disclosure is shown. PUCCH-Resource As shown in the IE Figure 2 , the type of PUCCH repetition is set in the IE PUCCH-Resource . Note that other components of the PUCCH repetition related configuration information can also be provided in the IE PUCCH-Resource

[0047] Based on the PUCCH repetition related configuration information and one or more PUCCH resources allocated for transmission of the PUCCH repetition, the UE can multiplex the PUCCH repetition on the allocated PUCCH resources and transmit the PUCCH repetition to multiple TRPs. The PUCCH repetition can be configured to transmit uplink control information (UCI), including one or more of a hybrid automatic repeat request acknowledgement (HARQ-ACK), channel state information (CSI), and a scheduling request (SR).

[0048] In addition, according to some embodiments of the disclosure, when the UE is operating in frequency range 2 (FR2), the UE can be configured to perform multi-beam operation, and thus different spatial relations corresponding to individual UE transmit (Tx) beams can be used for transmission of the PUCCH repetition targeting different TRPs. Accordingly, the PUCCH can be configured with spatial relation information indicating which Tx beam the UE should use for the PUCCH transmission.

[0049] In 3GPP Technical Specification Release 15 (hereinafter “Rel-15”), a PUCCH spatial relation activation / deactivation medium access control-control element (MAC-CE) is defined to activate the spatial relation of a PUCCH resource.

[0050] Figure 3 An example of such a MAC-CE for activating one spatial relation for a single PUCCH resource is shown. As shown in the MAC-CE Figure 3 ​As shown, the MAC-CE includes: a Serving Cell ID field, used to indicate the identifier of the Serving Cell to which the MAC-CE is applied; and a Bandwidth Part (BWP) ID field, used to indicate the uplink (UL) BWP to which the MAC-CE is applied, as a DCI bandwidth part indicator as specified in 3GPP Technical Specification (TS) 38.212. bandwidth part indicator The code point for the ) field; the PUCCH Resource ID field, containing the information as specified in 3GPP TS 38.331. PUCCH-ResourceId The identifier of the PUCCH resource ID.

[0051] MAC-CE also includes S i Field. If the PUCCH resource ID is configured... PUCCH-Config In this context, there exist standards that meet the requirements specified in 3GPP TS 38.331. PUCCH-SpatialRelationInfoId The spatial relationship information of PUCCH, then S i instruct PUCCH-SpatialRelationInfoId This field indicates the activation status of the PUCCH spatial relationship information equal to i+1; otherwise, the MAC entity will ignore this field. i The field is set to 1 to indicate PUCCH-SpatialRelationInfoId The PUCCH spatial relationship information equal to i+1 will be activated. i The field is set to 0 to indicate PUCCH-SpatialRelationInfoId The PUCCH spatial relationship information equal to i+1 will be deactivated. Only one PUCCH spatial relationship information can be activated for a PUCCH resource at a time.

[0052] In 5G / NR Rel-16, an enhanced MAC-CE is defined, which can update the spatial relationships of a set of PUCCH resources. PUCCH resources can be divided into multiple groups. If the MAC-CE updates the spatial relationship of a specific PUCCH resource, it can simultaneously update the spatial relationships of the groups to which that specific PUCCH resource belongs. Therefore, the enhanced MAC-CE can also be referred to as group-based MAC-CE in this paper.

[0053] Figure 4 This enhanced MAC-CE is shown. For example... Figure 4 As shown, similar to Figure 3 The MAC-CE in the standard MAC-CE, and the enhanced MAC-CE also include the serving cell ID field and the BWP ID field. The difference is that the enhanced MAC-CE includes the PUCCH resource ID field, which contains information from... PUCCH-ResourceIdan identifier of the indicated PUCCH resource that will be activated with the spatial relation indicated by the Spatial Relation Info ID field. If the indicated PUCCH resource ID is contained in the PUCCH resource group of the indicated UL BWP (as specified in 3GPP TS 38.331 resourceGroupToAddModList-r16 Configurations), other PUCCH resources within the same PUCCH resource group are not indicated in the MAC-CE and the MAC-CE applies to all PUCCH resources in the PUCCH resource group. The enhanced MAC-CE also includes a spatial relation info ID field containing PUCCH-SpatialRelationInfoId -1, where PUCCH- SpatialRelationInfoId is the identifier of the PUCCH spatial relation info in PUCCH-Config as specified in TS 38.331.

[0054] As shown in Figure 3 and Figure 4 , in both MAC-CEs, only one spatial relation can still be activated for one PUCCH resource. As mentioned above, one or more PUCCH resources can be assigned for the transmission of PUCCH repetition. In the case where only a single PUCCH resource is assigned for the transmission of PUCCH repetition, the single PUCCH resource is used for PUCCH repetition, and thus it can be necessary to configure more than one activated spatial relation for one PUCCH resource to allow the transmission of PUCCH repetition to multiple TRPs in FR2.

[0055] According to some embodiments of the disclosure, a new MAC-CE can be introduced to activate or deactivate one or more spatial relations for one or more PUCCH resources within the same or different groups. Figure 5 Examples of PUCCH spatial relation activation / deactivation MAC-CE for a single PUCCH resource with multiple activated spatial relations are shown, according to various embodiments of the disclosure. Figure 6 Examples of PUCCH spatial relation activation / deactivation MAC-CE for multiple PUCCH resources, where each PUCCH resource has multiple activated spatial relations, are shown, according to various embodiments of the disclosure. As shown in Figure 5 Multiple (two) spatial relations can be activated for one PUCCH resource by one MAC-CE. As shown in Figure 6 Multiple (two) spatial relations can be activated for multiple PUCCH resources by one MAC-CE.

[0056] According to some embodiments of the disclosure, some PUCCH resources can be configured with multiple activated spatial relations, while other PUCCH resources can still be configured with only one activated spatial relation. If one PUCCH resource is configured with multiple activated spatial relations, then there can be some conflicts if the UE also receives a group-based MAC-CE for updating the spatial relation of the PUCCH resource (as shown in Figure 4 For example, for one PUCCH resource #A, the resource is activated with two spatial relations #X and #Y. If the UE also receives a group-based MAC-CE to update the spatial relation of PUCCH resource #A with a single spatial relation #Z, there can be confusion on how to update the spatial relation of PUCCH resource #A. To solve this problem, some optional solutions are proposed in this application, which will be described in detail below. Figure 7 to Figure 12

[0057] In some embodiments of the disclosure, if one particular PUCCH resource (e.g., PUCCH resource #A) is activated with multiple spatial relations, then for this PUCCH resource #A, the spatial relation update by a group-based MAC-CE as shown in Figure 4 may be ignored. In other words, if the UE receives a group-based MAC-CE configured to activate only one spatial relation for one PUCCH resource, the UE can ignore the update of the activated spatial relation based on this MAC-CE.

[0058] In some embodiments of the disclosure, multiple PUCCH resources for PUCCH repetition transmission can be divided into separate PUCCH resource groups based on the number of activated spatial relations of the PUCCH resources, and the MAC-CE can include separate groups containing PUCCH resource ID fields and spatial relation information ID fields for indicating separate groups of PUCCH resources with different numbers of activated spatial relations. Thus, the UE can update one or more activated spatial relations of all PUCCH resources with the same number of activated spatial relations as the indicated PUCCH resources in the PUCCH resource group configured by resourceGroupToAddModList and including the PUCCH resources indicated in the MAC-CE based on one or more activated spatial relations of the indicated PUCCH resources. For example, for the MAC-CE as shown in Figure 4 the spatial relation update can only apply to those PUCCH resources with a single activated spatial relation for each PUCCH resource; for the MAC-CE as shown in Figure 5 or Figure 6 ​The MAC-CE shown, the spatial relation update can be applied to those PUCCH resources that have two activated spatial relations per PUCCH resource.

[0059] In some embodiments of the disclosure, an explicit group ID can be included in the MAC-CE for PUCCH spatial relation update. Figure 7 to Figure 9 Some examples of MAC-CE with explicit group ID according to various embodiments of the disclosure are shown. Specifically, for each indicated PUCCH resource and each activated spatial relation for the indicated PUCCH resource, the MAC-CE can further include a Group ID field for identifying a PUCCH resource group that is identified by resourceGroupToAddModList configured and includes an indicated PUCCH resource with activated spatial relation. In Figure 7 In the MAC-CE includes multiple PUCCH resources, each PUCCH resource has one activated spatial relation, and is configured with a Group ID field for each PUCCH resource; in Figure 8 In the MAC-CE includes one PUCCH resource with multiple activated spatial relations, a Group ID 1 field is configured for the PUCCH resource whose spatial relation is identified by spatial relation information ID 1, a Group ID 2 field is configured for the PUCCH resource whose spatial relation is identified by spatial relation information ID 2; in Figure 9 In the MAC-CE includes multiple PUCCH resources, each PUCCH resource has multiple activated spatial relations, a Group ID 1 field is configured for each PUCCH resource whose spatial relation is identified by spatial relation information ID 1, a Group ID 2 field is configured for each PUCCH resource whose spatial relation is identified by spatial relation information ID 2. By using the MAC-CE including explicit group ID field, the UE can update the activated spatial relations by all PUCCH resources in the PUCCH resource group that is identified by resourceGroupToAddModList configured and identified by the Group ID field corresponding to the indicated PUCCH resource with activated spatial relation.

[0060] In some embodiments of the disclosure, for each indicated PUCCH resource and each activated spatial relation for the indicated PUCCH resource, the MAC-CE can further include a reserved field 'R' including a present indication bit 'P' to indicate whether the activated spatial relation exists in the MAC-CE. Figure 10Such a MAC-CE is shown that includes one PUCCH resource with one or more activated spatial relations. For example, if the ‘P’ bit is set to 0, it indicates that the MAC-CE does not activate the spatial relation identified by spatial relation information ID1; if the ‘P’ bit is set to 1, it indicates that the MAC-CE will activate the spatial relation identified by spatial relation information ID1.

[0061] In some embodiments of the disclosure, for grouping of PUCCH resources, PUCCH resources without repetition for the same TRP or from the same UE panel can be grouped into one group. For example, PUCCH resources without repetition can be grouped into Group #A and Group #B. PUCCH resources with repetition plus PUCCH resources without repetition form one super group, for example, Group #C. Group #C = Group #A + Group #B + PUCCH resources with repetition. In other words, Group #A and Group #B are subgroups of Group #C. The MAC-CE can also include a Sub-Group ID field for identifying a subgroup of PUCCH resources including the indicated PUCCH resource with activated spatial relation for each indicated PUCCH resource and each activated spatial relation of the indicated PUCCH resource. By using the MAC-CE including the explicit Sub-Group ID field, the UE can update the activated spatial relation of all PUCCH resources in the subgroup of PUCCH resources identified by the Sub-Group ID field corresponding to the indicated PUCCH resource with activated spatial relation based on the activated spatial relation of the indicated PUCCH resource.

[0062] In some embodiments of the disclosure, the MAC-CE can include multiple PUCCH resources. If a particular PUCCH resource is only configured with one spatial relation by RRC signaling, only one spatial relation can be indicated for the PUCCH resource in the MAC-CE. If multiple spatial relations are configured for a PUCCH resource by RRC signaling, multiple spatial relations can be indicated for the PUCCH resource in the MAC-CE. Figure 11 An example of a PUCCH spatial relation activation / deactivation MAC-CE for a mix of one or more PUCCH resources with a single activated spatial relation per PUCCH resource and one or more PUCCH resources with multiple activated spatial relations per PUCCH resource is shown in accordance with various embodiments of the disclosure.

[0063] Figure 12Another example of a mixed PUCCH spatial relation activation / deactivation MAC-CE for one or more PUCCH resources with a single activated spatial relation per PUCCH resource and one or more PUCCH resources with multiple activated spatial relations per PUCCH resource is shown in accordance with various embodiments of the present disclosure. In the MAC-CE as shown in Figure 12 In the MAC-CE as shown, a ‘P’ bit is included to indicate whether a single spatial relation or multiple spatial relations are activated for one PUCCH resource. If the ‘P’ bit is set to 0, only one activated spatial relation is indicated for a PUCCH resource; otherwise, multiple activated spatial relations can be indicated for a PUCCH resource.

[0064] According to some embodiments, different PUCCH resources can be allocated for PUCCH repetition transmission. In these embodiments, one PUCCH resource can be configured with only one activated spatial relation. It can not be necessary to introduce a new MAC-CE to activate multiple spatial relations for one PUCCH resource.

[0065] In these embodiments, one or more dedicated PUCCH resource subsets in a PUCCH resource set can be configured for PUCCH repetition by higher layers (e.g., RRC layer). In a PUCCH resource subset, multiple PUCCH resources dedicated for PUCCH repetition transmission can be included. Each PUCCH resource can be configured with one activated spatial relation. In one PUCCH resource subset, all PUCCH resources can be configured with the same PUCCH format.

[0066] In some embodiments, a new field can be added in DCI to trigger a PUCCH resource subset. If a PUCCH resource subset is triggered, the PUCCH resources in the PUCCH resource subset can be allocated for transmission of PUCCH repetition. The PUCCH resources can be mapped to PUCCH repetition sequentially.

[0067] In some alternative embodiments, a PUCCH resource set for PUCCH repetition transmission can be implicitly triggered by a PUCCH resource indicator (PRI) in DCI. If the PRI corresponds to a PUCCH resource dedicated for PUCCH repetition transmission, the corresponding PUCCH resource subset including the PUCCH resource can be triggered. The PUCCH resource indicated by the PRI can be mapped to the first PUCCH repetition, and the remaining resources in the PUCCH resource subset can be mapped to PUCCH repetition sequentially with wrapping around.

[0068] In some embodiments, a group of multiple spatial relations can be indicated to a UE by higher layer signaling (e.g., RRC signaling) or DCI, and a spatial relation can be activated for each PUCCH resource in a PUCCH resource subset.k one PUCCH repetition using different spatial relations N one PUCCH repetition using different spatial relations, where 1 ≤ k ≤ N , and k may be configured by higher layers, or indicated by DCI, or implicitly determined based on specification, e.g., as a function of one or more of the following parameters: the number of PUCCH repetitions N and the number of spatial relations associated with PUCCH configuration, which are provided by PUCCH-Config . The spatial relations for different PUCCH repetitions can be sequentially determined by the index in a set of multiple spatial relations with proper “wrap-around”, the starting spatial relation indicated by MAC-CE is used to activate the spatial relations for one or more PUCCH resources.

[0069] As described above, the type of PUCCH repetition can include FDM-based PUCCH repetition, TDM-based PUCCH repetition, or SDM-based PUCCH repetition. In other words, the PUCCH repetition can be transmitted in an FDM-based manner, a TDM-based manner, or an SDM-based manner.

[0070] When the PUCCH repetition is transmitted in an FDM-based manner, the PUCCH repetition targeting different TRPs can be transmitted through different spatial relations, and the UE should support simultaneous transmission through multiple spatial relations or UE antenna panels.

[0071] Figure 13 An example of FDM-based PUCCH repetition with a single PUCCH resource according to various embodiments of the disclosure is illustrated. When a single PUCCH resource is used for FDM-based PUCCH repetition, the PUCCH format of the PUCCH resource should support multiple consecutive physical resource blocks (PRBs). As Figure 13 shown, the PRBs can be equally divided into multiple parts corresponding to multiple PUCCH repetitions, which can be transmitted to different TRPs through different spatial relations. Figure 14 An example of FDM-based PUCCH repetition with multiple PUCCH resources according to various embodiments of the disclosure is illustrated. When multiple PUCCH resources are used for FDM-based PUCCH repetition, the multiple PUCCH resources can occupy consecutive or non-consecutive PRBs.

[0072] When the PUCCH repetition is transmitted in a TDM-based manner, the PUCCH repetition targeting different TRPs can be transmitted through different spatial relations, and the UE does not need to support simultaneous transmission through multiple spatial relations or UE antenna panels.

[0073] Figure 15 Examples of TDM-based PUCCH repetition with a single PUCCH resource according to various embodiments of the present disclosure are shown. When a single PUCCH resource is used for TDM-based repetition, the PUCCH format of the PUCCH resource should support multiple consecutive orthogonal frequency-division multiplexing (OFDM) symbols or slots. As shown, the OFDM symbols or slots can be equally divided into multiple parts corresponding to multiple repetitions, and multiple PUCCH repetitions can be transmitted to different TRPs through different spatial relations. Figure 15 Examples of TDM-based PUCCH repetition with multiple PUCCH resources according to various embodiments of the present disclosure are shown. When multiple PUCCH resources are used for TDM-based repetition, the multiple PUCCH resources can occupy consecutive or non-consecutive OFDM symbols or slots. Figure 16 Examples of TDM-based PUCCH repetition with multiple PUCCH resources according to various embodiments of the present disclosure are shown. When multiple PUCCH resources are used for TDM-based repetition, the multiple PUCCH resources can occupy consecutive or non-consecutive OFDM symbols or slots.

[0074] In some embodiments, TDM-based PUCCH repetition can be implemented at a slot level or a sub-slot level. For example, the length of one slot can be 14 symbols (normal cyclic prefix (CP)) or 12 symbols (extended cyclic prefix (CP)), and the length of one sub-slot can be one or more of the following: 2, 4, or 7 / 6 symbols (for normal CP / extended CP, respectively). Accordingly, when a UE is configured with a slot-based or sub-slot-based PUCCH resource configuration, the PUCCH resource can be contained within a slot or sub-slot duration, and when the UE is configured with PUCCH repetition, the UE can be further indicated whether the repetition is mapped at a slot level or a sub-slot level through higher layer configuration or through 1stlayer signaling of DCI. For PUCCH carrying HARQ-ACK feedback, the first PUCCH repetition can be mapped to the PUCCH resource indicated by PRI in the DCI, and the subsequent PUCCH repetitions can be mapped to consecutive available sub-slots or slots. In addition, each PUCCH repetition can be transmitted using a spatial relation, which can be uniquely identified for each PUCCH resource used for PUCCH repetition.

[0075] When transmitting PUCCH repetition in an SDM-based manner, PUCCH repetitions targeting different TRPs can be transmitted through different spatial relations, and the UE should support simultaneous transmission through multiple spatial relations or UE antenna panels. The PUCCH repetitions can occupy the same resources in the time and frequency domains. Figure 17 Examples of spatial division multiplexing (SDM)-based PUCCH repetition with multiple PUCCH resources according to various embodiments of the present disclosure are shown.

[0076] In the above embodiments, various schemes for transmitting PUCCH repetitions targeting multiple TRPs have been described in detail. For the purpose of illustration, the following will describe operations associated with transmission of PUSCH repetitions to be performed at a UE and a TRP, respectively. Figure 18 and 19

[0077] Figure 18 An example procedure 1800 at a UE in a multi-TRP scenario with single DCI associated with transmission of PUCCH repetitions according to various embodiments of the present disclosure is shown. The example procedure 1800 can include operations 1810 to 1830.

[0078] At operation 1810, the UE can receive, from a TRP, a DCI for scheduling PUCCH transmission to multiple TRPs. The multiple TRPs can be configured with a same cell ID or different cell IDs.

[0079] At operation 1820, the UE can encode and multiplex multiple PUCCH repetitions targeting multiple TRPs on one or more PUCCH resources based on PUCCH repetition related configuration information indicated by the DCI or higher layer signaling.

[0080] According to some embodiments of the present disclosure, the PUCCH repetition related configuration information can include an indication on whether PUCCH repetition is enabled or not, and a type of PUCCH repetition and a number of PUCCH repetitions when PUCCH repetition is enabled. The type of PUCCH repetition can include FDM based PUCCH repetition, TDM based PUCCH repetition, or SDM based PUCCH repetition. The higher layer signaling can be RRC signaling, and at least one or more components of the PUCCH repetition related configuration information can be set in an RRC IE PUCCH-Config The PUCCH repetition related configuration information can be configured on a PUCCH resource set level, a PUCCH resource level, or a PUCCH format level. The PUCCH repetition can be configured for conveying UCI including one or more of HARQ-ACK, CSI, and SR.

[0081] According to some embodiments of the present disclosure, the UE can further determine a capability of the UE on which type of PUCCH repetition to support, encode an indication on the capability of the UE, and report the indication on the capability of the UE to the TRP or a higher layer.

[0082] At operation 1830, the UE can transmit the encoded and multiplexed PUCCH repetitions to the multiple TRPs through the one or more PUCCH resources.

[0083] ​According to some embodiments of the disclosure, when a UE operates in FR2, the UE can activate / deactivate MAC-CEs based on PUCCH spatial relation from TRPs, determine multiple spatial relations activated for one or more PUCCH resources, map PUCCH repetitions targeting multiple TRPs to respective spatial relations in the activated multiple spatial relations, and transmit the PUCCH repetitions through one or more resources and the respective spatial relations to the multiple TRPs.

[0084] In some embodiments, the MAC-CE can be a group-based MAC-CE including a PUCCH resource ID field for indicating an ID of a PUCCH resource, and a spatial relation information ID field for indicating an ID of a spatial relation to be activated for the PUCCH resource. The UE can update, based on the indicated activated spatial relation of the PUCCH resource, activated spatial relations of all PUCCH resources in a PUCCH resource group that is configured and includes the PUCCH resource indicated in the MAC-CE. resourceGroupToAddModList configured and includes the PUCCH resource indicated in the MAC-CE.

[0085] In some embodiments, the one or more PUCCH resources can include only a single PUCCH resource, and the single PUCCH resource is configured with activated multiple spatial relations based on the MAC-CE. The MAC-CE can include a PUCCH resource ID field, and multiple spatial relation information ID fields for indicating IDs of the multiple spatial relations to be activated for the PUCCH resource. The MAC-CE can include multiple PUCCH resource ID fields for indicating IDs of multiple PUCCH resources, and one or more spatial relation information ID fields for indicating IDs of one or more spatial relations to be activated for each of the multiple PUCCH resources.

[0086] In some embodiments, when the MAC-CE is configured to activate only one spatial relation for a PUCCH resource, the UE can ignore the update of activated multiple spatial relations based on the MAC-CE.

[0087] In some embodiments, the UE can update, based on the indicated activated spatial relation of the PUCCH resource, activated spatial relations of all PUCCH resources in a PUCCH resource group that has the same number of activated spatial relations as the indicated PUCCH resource, the PUCCH resource group being configured and including the PUCCH resource indicated in the MAC-CE. resourceGroupToAddModList configured and includes the PUCCH resource indicated in the MAC-CE.

[0088] In some embodiments, the plurality of PUCCH resources can be divided into separate PUCCH resource groups based on the number of activated spatial relations of the PUCCH resources, and the MAC-CE can include separate groups of PUCCH resource ID fields and spatial relation information ID fields for indicating separate PUCCH resource groups with different numbers of activated spatial relations. The UE can update one or more activated spatial relations of all PUCCH resources in a PUCCH resource group with the same number of activated spatial relations as the indicated PUCCH resource based on the indicated one or more activated spatial relations of the PUCCH resource, the PUCCH resource group being identified by resourceGroupToAddModList configured and including the indicated PUCCH resource in the MAC-CE.

[0089] In some embodiments, for each indicated PUCCH resource and each activated spatial relation of the indicated PUCCH resource, the MAC-CE can further include a group ID field for identifying a PUCCH resource group being configured and including the indicated PUCCH resource with the activated spatial relation. The UE can update the activated spatial relation of all PUCCH resources in a PUCCH resource group based on the activated spatial relation of the indicated PUCCH resource, the PUCCH resource group being identified by resourceGroupToAddModList configured and including the indicated PUCCH resource with the activated spatial relation. The UE can update the activated spatial relation of all PUCCH resources in a PUCCH resource group based on the activated spatial relation of the indicated PUCCH resource, the PUCCH resource group being identified by resourceGroupToAddModList configured and identified by a group ID field corresponding to the indicated PUCCH resource with the activated spatial relation.

[0090] In some embodiments, for each indicated PUCCH resource and each activated spatial relation of the indicated PUCCH resource, the MAC-CE can further include a reserved field ‘R’ including a present indication bit ‘P’ to indicate whether the activated spatial relation is present in the MAC-CE.

[0091] According to some embodiments of this disclosure, one or more PUCCH resources may include multiple PUCCH resources, and each PUCCH resource is configured with an activation space relationship based on MAC-CE. One or more dedicated PUCCH resource subsets in the PUCCH resource set may be configured for PUCCH repeat transmission, and all PUCCH resources in a PUCCH resource subset may be configured with the same PUCCH format. The UE may determine the PUCCH resource subset for PUCCH repeat transmission based on the dedicated field in the DCI, and sequentially map the PUCCH resources in the PUCCH resource subset to the PUCCH repeats. Alternatively, the UE may determine the PUCCH resource subset for PUCCH repeat transmission based on the PRI in the DCI, map the PUCCH resources indicated by the PRI to the first PUCCH repeat in the PUCCH repeat, and map the remaining resources in the PUCCH resource subset to subsequent PUCCH repeats in the PUCCH repeat.

[0092] In some embodiments, the UE can determine multiple spatial relationships for PUCCH repetition based on DCI or higher-layer signaling; through each k Each repetition is assigned a different spatial relation, mapping the PUCCH repetition to multiple spatial relations, where... k It is the number of repetitions from 1 to PUCCH. N The integer between the specified values, configured by a higher layer or indicated by the DCI; and the encoded and multiplexed PUCCH is repeatedly transmitted to multiple TRPs through one or more PUCCH resources and multiple spatial relationships.

[0093] Figure 19 Example process 1900 is illustrated in various embodiments of this disclosure, relating to the transmission of PUCCH repetition at a TRP in a multi-TRP scenario utilizing a single DCI. Example process 1900 may include operations 1910 to 1920.

[0094] At operation 1910, the TRP can encode DCI or higher-level signaling, which is used to instruct the UE on PUCCH repetition related configuration information and allocate one or more PUCCH resources for the transmission of PUCCH repetition from the UE to multiple TRPs.

[0095] At Operation 1920, the TRP can send encoded DCI or higher-layer signaling to the UE.

[0096] According to some embodiments of the disclosure, when the UE operates in FR2, a TRP can encode a PUCCH spatial relation activation / deactivation MAC-CE for indicating a plurality of spatial relations activated for one or more PUCCH resources; and transmit the encoded PUCCH spatial relation activation / deactivation MAC-CE to the UE. The MAC-CE can be a group-based MAC-CE including: a PUCCH resource ID field for indicating an ID of a PUCCH resource, and a spatial relation information ID field for indicating an ID of a spatial relation to be activated for the PUCCH resource.

[0097] In some embodiments, the one or more PUCCH resources can include only a single PUCCH resource, and the single PUCCH resource is configured with a plurality of activated spatial relations based on the MAC-CE. The MAC-CE can include: a PUCCH resource ID field, and a plurality of spatial relation information ID fields for indicating IDs of the plurality of spatial relations to be activated for the PUCCH resource. The MAC-CE can include: a plurality of PUCCH resource ID fields for indicating IDs of a plurality of PUCCH resources; and one or more spatial relation information ID fields for indicating IDs of one or more spatial relations to be activated for each of the plurality of PUCCH resources.

[0098] In some embodiments, the plurality of PUCCH resources can be divided into separate PUCCH resource groups based on a number of activated spatial relations of the PUCCH resources, and the MAC-CE can include separate groups of PUCCH resource ID fields and spatial relation information ID fields for indicating separate PUCCH resource groups with different numbers of activated spatial relations.

[0099] In some embodiments, for each indicated PUCCH resource and each activated spatial relation of the indicated PUCCH resource, the MAC-CE can further include a group ID field for identifying a PUCCH resource group that is configured and includes the indicated PUCCH resource with the activated spatial relation. resourceGroupToAddModList configured and includes the indicated PUCCH resource with the activated spatial relation.

[0100] In some embodiments, for each indicated PUCCH resource and each activated spatial relation of the indicated PUCCH resource, the MAC-CE can further include a reserved field ‘R’ including a present indication bit ‘P’ to indicate whether the activated spatial relation is present in the MAC-CE.

[0101] According to some embodiments of the disclosure, the one or more PUCCH resources can comprise a plurality of PUCCH resources, and each PUCCH resource is configured with one active spatial relation based on a MAC-CE. One or more dedicated subsets of PUCCH resources in the set of PUCCH resources can be configured for transmission of PUCCH repetition, and all PUCCH resources in one subset of PUCCH resources can be configured with the same PUCCH format.

[0102] In some embodiments, the DCI can include a PRI, and a subset of PUCCH resources including the PUCCH resource indicated by the PRI can be configured for transmission of PUCCH repetition. The PUCCH resource indicated by the PRI can be allocated for transmission of a first PUCCH repetition in the PUCCH repetition, and the remaining resources in the subset of PUCCH resources can be allocated for transmission of subsequent PUCCH repetitions in the PUCCH repetition.

[0103] The above part of the disclosure is provided to describe possible schemes for transmission of PUCCH repetition in a multi-TRP scenario with single DCI. In the following part, schemes for PUSCH repetition transmission in a multi-TRP scenario will be described, in particular for TDM-based PUSCH repetition transmission.

[0104] For PUSCH transmission with single DCI operation, PUSCH can be transmitted with repetition for different TRPs to improve reliability. The type of PUSCH repetition can be FDM-based PUSCH repetition, TDM-based PUSCH repetition, or SDM-based PUSCH repetition. In 5G / NR Rel-16, inter-repetition frequency hopping is supported for TDM-based PUSCH repetition for ultra-reliable and low-latency communication (URLLC). However, the PUSCH repetition is for the same cell. With inter-repetition frequency hopping, the starting RB for PUSCH repetition with index n is defined as follows. n

[0105] Here, is the starting RB for PUSCH repetition n , is the starting RB within the uplink BWP, is the frequency offset in RBs between the frequency hops, and is the number of PRBs of the uplink active BWP size.

[0106] ​​When PUSCH repetition is applied to a multi-TRP scenario, multiple TRPs need to be considered to enhance inter-repetition frequency hopping. For TDM-based PUSCH repetition in a multi-TRP scenario with single DCI, the same frequency allocation size can be applied for all TDM-based PUSCH repetitions, or different frequency allocation sizes are applied for TDM-based PUSCH repetitions targeting different TRPs and the same frequency allocation size is applied for TDM-based PUSCH repetitions targeting the same TRP. Depending on the frequency allocation size to be applied to TDM-based PUSCH repetitions, inter-repetition frequency hopping patterns can be predefined in different ways to enable a UE to map individual PUSCH repetitions targeting the same TRP to different frequency domain resources respectively corresponding to the individual PUSCH repetitions.

[0107] According to some embodiments of the present disclosure, the same frequency allocation size is applied for all TDM-based PUSCH repetitions. In an embodiment, for TDM-based PUSCH repetition transmission in a multi-TRP scenario operating with single DCI, frequency hopping can be applied between PUSCH repetitions. For those repetitions targeting the same TRP, frequency hopping can be applied to achieve frequency diversity.

[0108] Assume that TRPs are indexed by k Index k = 0, 1,..., K -1, K is the total number of TRPs), for PUSCH repetition n Index n = 0, 1, 2,..., N -1, N is the total number of TDM-based PUSCH repetitions), for example, if the index of the target TRP of PUSCH repetition n is given by k = 0, 1, 2,..., k = n mod K then the inter-repetition frequency hopping pattern can be predefined by the following equation (1).

[0109] (1) Figure 20 An example of inter-repetition frequency hopping for TDM-based PUSCH repetitions with the same frequency resource allocation size according to various embodiments of the present disclosure is shown. In this example, two TRPs are indexed by 0 and 1 respectively, there are 4 TDM-based PUSCH repetitions indexed by 0, 1, 2, 3, and the inter-repetition frequency hopping pattern is predefined by the above equation (1). As shown in the example, the inter-repetition frequency hopping pattern is defined as Figure 20As shown, the same frequency allocation size is applied to all four TDM-based PUSCH repetitions, and the four TDM-based PUSCH repetitions occupy different time-domain resources, which can have zero gap between them. In addition, PUSCH repetition #0 and PUSCH repetition #2 targeting the same TRP #0 are mapped to different frequency-domain resources, and PUSCH repetition #1 and PUSCH repetition #3 targeting the same TRP #1 are also mapped to different frequency-domain resources, but PUSCH repetition #0 and PUSCH repetition #1 (or PUSCH repetition #2 and PUSCH repetition #3) targeting different TRPs can be mapped to the same frequency-domain resources.

[0110] In some embodiments where the same frequency allocation size is applied to all TDM-based PUSCH repetitions, the index of the target TRP k is given by It is given that the inter-repetition frequency hopping pattern can be predefined by the following equation (2).

[0111] (2) Figure 21 An example of inter-repetition frequency hopping for TDM-based PUSCH repetitions with the same frequency resource allocation size according to various embodiments of the present disclosure is shown. In this example, two TRPs are indexed by 0 and 1 respectively, there are 4 TDM-based PUSCH repetitions indexed by 0, 1, 2, 3, and the inter-repetition frequency hopping pattern is predefined by the above equation (2). As shown, the same frequency allocation size is applied to all four TDM-based PUSCH repetitions, and the four TDM-based PUSCH repetitions occupy different time-domain resources, which can have zero gap between them. In addition, PUSCH repetition #0 and PUSCH repetition #2 targeting the same TRP #0 are mapped to different frequency-domain resources, and PUSCH repetition #1 and PUSCH repetition #3 targeting the same TRP #1 are also mapped to different frequency-domain resources, but PUSCH repetition #0 and PUSCH repetition #2 (or PUSCH repetition #1 and PUSCH repetition #3) targeting different TRPs can be mapped to the same frequency-domain resources. Figure 21

[0112] In some embodiments where the same frequency allocation size is applied to all TDM-based PUSCH repetitions, the index of the target TRP k is given by It is given that the inter-repetition frequency hopping pattern can be predefined by the following equation (3).

[0113] (3)​ Figure 22 Examples of inter-repetition frequency hopping for TDM-based PUSCH repetitions with the same frequency resource allocation size, according to various embodiments of this disclosure, are shown. In this example, two TRPs are indexed 0 and 1 respectively, and there are four TDM-based PUSCH repetitions indexed 0, 1, 2, and 3. The inter-repetition frequency hopping pattern is predefined by equation (3) above. Figure 22 As shown, the same frequency allocation size is applied to all four TDM-based PUSCH repetitions, and the four TDM-based PUSCH repetitions occupy different time-domain resources, with the interval between these time-domain resources potentially being zero. Furthermore, PUSCH repetitions #0 and #1, targeting the same TRP #0, are mapped to different frequency-domain resources, as are PUSCH repetitions #2 and #3, also targeting the same TRP #1. However, PUSCH repetitions #0 and #3 (or PUSCH repetitions #1 and #2) targeting different TRPs can be mapped to the same frequency-domain resource.

[0114] According to some embodiments of this disclosure, for TDM-based PUSCH repetitions, the frequency resource allocation sizes between PUSCH repetitions targeting different TRPs can be different, while the frequency resource allocation sizes for PUSCH repetitions targeting the same TRP should be the same. In this case, the parameters... and It should be specific to TRP.

[0115] In some embodiments where different frequency allocation sizes are applied to TDM-based PUSCH repetitions targeting different TRPs, the index of the target TRP... k It can be by k = n mod K Given, and the frequency hopping mode between repetitions can be predefined by the following equation (4).

[0116] (4) in, Is the index as n The PUSCH repeats the starting RB, This is for indexes. k The starting RB within the uplink BWP of the TRP, This is for indexes. k The frequency offset between TRP frequency hopping intervals, in RB units, and It is the number of PRBs of the uplink activated BWP size.

[0117] Figure 23An example of inter-repetition frequency hopping for TDM-based PUSCH repetition with different frequency resource allocation sizes is shown according to various embodiments of the present disclosure. In this example, two TRPs are indexed by 0 and 1 respectively, and there are 4 TDM-based PUSCH repetitions indexed by 0, 1, 2, 3, the inter-repetition frequency hopping pattern is predefined by the above equation (4). As shown in Figure 23 different frequency allocation sizes are applied to TDM-based PUSCH repetitions targeting different TRPs (e.g., PUSCH repetition #0 and PUSCH repetition #1), and the four TDM-based PUSCH repetitions occupy different time domain resources, the interval between these time domain resources can be zero. In addition, PUSCH repetition #0 and PUSCH repetition #2 targeting the same TRP #0 are mapped to different frequency domain resources, and PUSCH repetition #1 and PUSCH repetition #3 targeting the same TRP #1 are also mapped to different frequency domain resources, but the frequency domain resources allocated to PUSCH repetition #0 and PUSCH repetition #1 (or PUSCH repetition #2 and PUSCH repetition #3) targeting different TRPs can overlap.

[0118] In some embodiments where different frequency allocation sizes are applied to TDM-based PUSCH repetitions targeting different TRPs, the index of the target TRP k is given by The inter-repetition frequency hopping pattern can be predefined by the following equation (5).

[0119] (5) Figure 24 An example of inter-repetition frequency hopping for TDM-based PUSCH repetition with different frequency resource allocation sizes is shown according to various embodiments of the present disclosure. In this example, two TRPs are indexed by 0 and 1 respectively, and there are 4 TDM-based PUSCH repetitions indexed by 0, 1, 2, 3, the inter-repetition frequency hopping pattern is predefined by the above equation (5). As shown in Figure 24 different frequency allocation sizes are applied to TDM-based PUSCH repetitions targeting different TRPs (e.g., PUSCH repetition #0 and PUSCH repetition #2), and the four TDM-based PUSCH repetitions occupy different time domain resources, the interval between these time domain resources can be zero. In addition, PUSCH repetition #0 and PUSCH repetition #1 targeting the same TRP #0 are mapped to different frequency domain resources, and PUSCH repetition #2 and PUSCH repetition #3 targeting the same TRP #1 are also mapped to different frequency domain resources, but the frequency domain resources allocated to PUSCH repetition #0 and PUSCH repetition #2 (or PUSCH repetition #1 and PUSCH repetition #3) targeting different TRPs can overlap.

[0120] In some embodiments where different frequency allocation sizes are applied to TDM-based PUSCH repetitions targeting different TRPs, an index of the target TRP k is given by The inter-repetition frequency hopping pattern can be predefined by the following equation (6).

[0121] (6) Figure 25 An example of inter-repetition frequency hopping for TDM-based PUSCH repetitions with different frequency resource allocation sizes is shown according to various embodiments of the present disclosure. In this example, two TRPs are indexed by 0 and 1 respectively, there are 4 TDM-based PUSCH repetitions indexed by 0, 1, 2, 3, and the inter-repetition frequency hopping pattern is predefined by the above equation (6). As shown, different frequency allocation sizes are applied to TDM-based PUSCH repetitions targeting different TRPs (e.g., PUSCH repetition #0 and PUSCH repetition #2), and the four TDM-based PUSCH repetitions occupy different time domain resources, the interval length between which can be zero. In addition, PUSCH repetition #0 and PUSCH repetition #1 targeting the same TRP #0 are mapped to different frequency domain resources, and PUSCH repetition #2 and PUSCH repetition #3 targeting the same TRP #1 are also mapped to different frequency domain resources, but the frequency domain resources allocated to PUSCH repetition #0 and PUSCH repetition #3 (or PUSCH repetition #1 and PUSCH repetition #2) targeting different TRPs can overlap. Figure 25

[0122] It should be noted that the above embodiments related to transmission of TDM-based PUSCH repetitions can be applied to UEs operating in frequency range 1 and frequency range 2. Furthermore, depending on the capability of the UE, the UE can or can not need a certain time to retune RF when the UE needs to switch frequency hopping between different frequency parts.

[0123] Figure 26 An example procedure 2600 associated with transmission of TDM-based PUSCH repetitions at a UE in a multi-TRP scenario with single DCI is shown according to various embodiments of the present disclosure. The example procedure 2600 can include operations 2610 to 2630.

[0124] At operation 2610, the UE can receive a DCI from a TRP, the DCI scheduling transmission of TDM-based PUSCH repetitions to multiple TRPs. ​

[0125] At operation 2620, the UE can encode and reuse TDM-based PUSCH repetitions by mapping each PUSCH repetition targeting the same TRP among multiple TRPs to different frequency domain resources, the different frequency domain resources corresponding to each PUSCH repetition and determined by a predefined inter-repetition frequency hopping pattern.

[0126] At operation 2630, the UE can repeatedly send encoded and multiplexed TDM-based PUSCH to multiple TRPs.

[0127] According to some embodiments of this disclosure, the inter-repetition frequency hopping mode is based on the frequency allocation size for TDM-based PUSCH repetition and the index of the PUSCH repetition. n Index of target TRP k The relationships between them are predefined.

[0128] In some embodiments, TDM-based PUSCH repetitions can be configured with the same frequency allocation size and target TRP index. k It can be by k = n mod K Given, and the frequency hopping pattern between repetitions can be predefined by the following formula: .

[0129] In some embodiments, TDM-based PUSCH repetitions can be configured with the same frequency allocation size and target TRP index. k It can be by Given, and the frequency hopping pattern between repetitions can be predefined by the following formula: .

[0130] In some embodiments, TDM-based PUSCH repetitions can be configured with the same frequency allocation size and target TRP index. k It can be by Given, and the frequency hopping pattern between repetitions can be predefined by the following formula: .

[0131] In some embodiments, TDM-based PUSCH repetition can be configured with different frequency allocation sizes and target TRP indexes. k It can be by k = n mod K Given, and the frequency hopping pattern between repetitions can be predefined by the following formula: .

[0132] In some embodiments, TDM-based PUSCH repetition can be configured with different frequency allocation sizes and target TRP indexes. k It can be by Given, and the frequency hopping pattern between repetitions can be predefined by the following formula: .

[0133] In some embodiments, TDM-based PUSCH repetition can be configured with different frequency allocation sizes and target TRP indexes. k It can be by Given, and the frequency hopping pattern between repetitions can be predefined by the following formula: .

[0134] In the above embodiments, it should be noted that TDM-based PUSCH repetitions targeting different TRPs can be configured with different frequency allocation sizes, but TDM-based PUSCH repetitions targeting the same TRP should be configured with the same frequency allocation size.

[0135] Figure 27 and Figure 28 Various systems, devices, and components are shown that can implement aspects of the disclosed embodiments.

[0136] Figure 27 Illustrations of a network 2700 according to various embodiments of the present disclosure are shown. The network 2700 can operate in a manner consistent with the 3GPP technical specifications of LTE or 5G / NR systems. However, the exemplary embodiments are not limited in this respect, and the described embodiments can be applied to other networks that benefit from the principles described herein, such as future 3GPP systems, etc.

[0137] Network 2700 may include UE 2702, which may include any mobile or non-mobile computing device designed to communicate with RAN 2704 via an over-the-air connection. UE 2702 may be, but is not limited to, smartphones, tablets, wearable computing devices, desktop computers, laptops, in-vehicle infotainment devices, in-vehicle entertainment devices, instrument clusters, head-up displays, in-vehicle diagnostic devices, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, networked appliances, machine-type communication devices, M2M or D2D devices, IoT devices, etc.

[0138] In some embodiments, network 2700 may include multiple UEs that are directly coupled to each other via sidelink interfaces. The UEs may be M2M / D2D devices that communicate using physical sidelink channels (e.g., but not limited to, physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH), physical sidelink basic channel (PSFCH), etc.).

[0139] In some embodiments, UE 2702 can also communicate with AP 2706 via an over-the-air connection. AP 2706 manages WLAN connections and can be used to offload some / all network traffic from RAN 2704. The connection between UE 2702 and AP 2706 can be consistent with any IEEE 802.13 protocol, where AP 2706 can be a Wi-Fi® router. In some embodiments, UE 2702, RAN 2704, and AP 2706 can utilize cellular WLAN aggregation (e.g., LTE-WLAN aggregation (LWA) / Lightweight IP (LWIP)). Cellular WLAN aggregation may involve UE 2702, configured by RAN 2704, utilizing both cellular radio resources and WLAN resources.

[0140] RAN 2704 may include one or more Access Nodes (ANs), such as AN 2708. AN 2708 can terminate the air interface protocol of UE 2702 by providing access layer protocols including RRC, Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Media Access Control (MAC), and L1 protocol. In this way, AN 2708 enables data / voice connectivity between CN 2720 and UE 2702. In some embodiments, AN 2708 may be implemented in a discrete device or as one or more software entities running on a server computer as part of, for example, a virtual network, which may be referred to as CRAN or a virtual baseband unit pool. AN 2708 may be referred to as a Base Station (BS), gNB, RAN node, evolved Node B (eNB), next-generation eNB (ng-eNB), Node B (NodeB), Roadside Unit (RSU), TRxP, TRP, etc. AN2708 can be a macro cell base station or a low-power base station, used to provide microcells, picocells, or other similar cells with smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

[0141] In embodiments where RAN 2704 includes multiple ANs, they can be coupled to each other via an X2 interface (in the case of RAN 2704 being an LTE RAN) or an Xn interface (in the case of RAN 2704 being a 5G RAN). In some embodiments, the X2 / Xn interfaces, which can be separated into a control plane interface and a user plane interface, can allow ANs to transmit and handover, data / context transfer, mobility, load management, interference coordination, and other related information.

[0142] The AN of RAN 2704 can manage one or more cells, cell groups, component carriers, etc., to provide an air interface for network access to UE 2702. UE 2702 can simultaneously connect to multiple cells provided by the same or different ANs of RAN 2704. For example, UE 2702 and RAN 2704 can use carrier aggregation to allow UE 2702 to connect to multiple component carriers, each component carrier corresponding to a primary cell (Pcell) or a secondary cell (Scell). In dual connectivity scenarios, the first AN can be the primary node providing the primary cell group (MCG), and the second AN can be the secondary node providing the secondary cell group (SCG). The first / second AN can be any combination of eNB, gNB, ng-eNB, etc.

[0143] RAN 2704 can provide an air interface on either licensed or unlicensed spectrum. For operation in unlicensed spectrum, nodes can use Licensed Assisted Access (LAA), Enhanced LAA (eLAA), and / or further enhanced LAA (feLAA) mechanisms based on carrier aggregation (CA) technology with PCell / Scell. Before accessing unlicensed spectrum, nodes can perform medium / carrier sensing operations based on, for example, a Listen-Before-Speak (LBT) protocol.

[0144] In a vehicle-to-everything (V2X) scenario, UE 2702 or AN 2708 can be or act as a roadside unit (RSU), which can refer to any transportation infrastructure entity used for V2X communication. An RSU can be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by a UE can be referred to as a "UE-type RSU"; an RSU implemented in or by an eNB can be referred to as an "eNB-type RSU"; an RSU implemented in or by a next-generation NodeB (gNB) can be referred to as a "gNB-type RSU"; and so on. In one example, the RSU is a computing device coupled to radio frequency circuitry located on the roadside, providing connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU can provide very low-latency communication required for high-speed events, such as collision avoidance, traffic warnings, etc. Alternatively or additionally, the RSU can provide other cellular / WLAN communication services. RSU components can be enclosed in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide wired connectivity (e.g., Ethernet) to traffic signal controllers or backhaul networks.

[0145] In some embodiments, RAN 2704 may be LTE RAN 2710, which includes an evolved Node B (eNB), such as eNB 2712. LTE RAN 2710 can provide an LTE air interface with the following characteristics: 15 kHz SCS; CP-OFDM waveforms for DL ​​and SC-FDMA waveforms for UL; turbo codes for data and TBCC for control, etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; rely on PDSCH / PDCCH demodulation reference signals (DMRS) for PDSCH / PDCCH demodulation; and rely on CRS for cell search and initial acquisition, channel quality measurement, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface can operate in the sub-6 GHz band.

[0146] In some embodiments, RAN 2704 may be a next-generation (NG) RAN 2714 with a gNB (e.g., gNB 2716) or a gn-eNB (e.g., ng-eNB 2718). gNB 2716 can connect to a 5G-enabled UE using a 5G NR interface. gNB 2716 can connect to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. Ng-eNB 2718 can also connect to the 5G core via an NG interface, but can connect to the UE via an LTE air interface. gNB 2716 and ng-eNB 2718 can connect to each other via an Xn interface.

[0147] In some embodiments, the NG interface can be divided into two parts: the NG user plane (NG-U) interface and the NG control plane (NG-C) interface. The former carries traffic data between the nodes of NG-RAN 2714 and UPF 2748, while the latter is the signaling interface (e.g., the N2 interface) between NG-RAN 2714 and the nodes of Access and Mobility Management Function (AMF) 2744.

[0148] NG-RAN 2714 can provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polarity, repetition, simplex, and Reed-Muller codes for control, and LDPC for data. The 5G-NR air interface can rely on CSI-RS, PDSCH / PDCCH DMRS similar to those of the LTE air interface. The 5G-NR air interface may not use CRS, but can use PBCH DMRS for PBCH demodulation; PTRS for PDSCH phase tracking; and a tracking reference signal for time tracking. The 5G-NR air interface can operate on the FR1 band, including the sub-6 GHz band, or the FR2 band, including the 24.25 GHz to 52.6 GHz band. The 5G-NR air interface may include an SSB, which is an area of ​​the downlink resource grid including PSS / SSS / PBCH.

[0149] In some embodiments, the 5G-NR air interface can use BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of SCS. For instance, UE 2702 can be configured with multiple BWPs, each configured with a different SCS. When UE 2702 is instructed to change a BWP, the transmitted SCS also changes. Another use case for BWPs relates to power saving. Specifically, multiple BWPs with different numbers of frequency resources (e.g., PRBs) can be configured for UE 2702 to support data transmission under different traffic load scenarios. A BWP containing fewer PRBs can be used for data transmission with lower traffic loads, while allowing power saving at UE 2702 and, in some cases, at gNB 2716. A BWP containing more PRBs can be used for scenarios with higher traffic loads.

[0150] RAN 2704 is communicatively coupled to CN 2720, which includes network elements, to provide various functions supporting data and telecommunications services to customers / subscribers (e.g., users of UE 2702). Components of CN 2720 may be implemented in a single physical node or in different physical nodes. In some embodiments, NFV may be used to virtualize any or all of the functionality provided by the network elements of CN 2720 onto physical compute / storage resources such as servers, switches, etc. A logical instance of CN 2720 may be referred to as a network slice, and a logical instantiation of a portion of CN 2720 may be referred to as a network subslice.

[0151] In some embodiments, CN 2720 may be LTE CN 2722, which may also be referred to as the Evolved Packet Core (EPC). LTE CN 2722 may include a Mobility Management Entity (MME) 2724, a Serving Gateway (SGW) 2726, a Serving GPRS Support Node (SGSN) 2728, a Home Subscriber Server (HSS) 2730, a Proxy Gateway (PGW) 2732, and a Policy Control and Charging Rules Function (PCRF) 2734, as shown in the figure. These components are coupled to each other through interfaces (or "reference points"). The functions of the elements of LTE CN 2722 can be briefly described below.

[0152] The MME 2724 enables mobility management functions to track the current location of the UE 2702, thereby facilitating patrol, bearer activation / deactivation, handover, gateway selection, authentication, and other functions.

[0153] The SGW 2726 can terminate the S1 interface toward the RAN and route data packets between the RAN and the LTE CN 2722. The SGW 2726 can serve as a local mobility anchor for handover between RAN nodes and can also provide anchoring for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0154] The SGSN 2728 can track the location of UE 2702 and perform security functions and access control. Additionally, the SGSN 2728 can perform EPC inter-node signaling for mobility between different RAT networks; PDN and S-GW selection specified by the MME 2724; MME selection for handover, etc. The S3 reference point between the MME 2724 and SGSN 2728 enables the exchange of user and bearer information for 3GPP indirect access network mobility in idle / active states.

[0155] The HSS 2730 may include a database for network users, containing subscription-related information that supports network entities in handling communication sessions. The HSS 2730 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc. An S6a reference point between the HSS 2730 and the MME 2724 enables the transmission of subscription and authentication data to authenticate / authorize user access to the LTE CN 2720.

[0156] The PGW 2732 can terminate the SGi interface toward a data network (DN) 2736, which may include an application / content server 2738. The PGW 2732 can route data packets between the LTE CN 2722 and the data network 2736. The PGW 2732 can be coupled to the SGW 2726 via an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 2732 may also include nodes for policy enforcement and charging data collection (e.g., PCEF). Additionally, the SGi reference point between the PGW 2732 and the data network 2736 can be, for example, an external public or private PDN or an internal packet data network for providing IMS services. The PGW 2732 can be coupled to the PCRF 2734 via a Gx reference point.

[0157] PCRF 2734 is the policy and charging control element of LTE CN 2722. PCRF 2734 can be communicatively coupled to application / content server 2738 to determine appropriate QoS and charging parameters for service flows. PCRF 2732 can provide associated rules to PCEF (via Gx reference point) with appropriate TFT and QCI.

[0158] In some embodiments, CN 2720 may be a 5G core network (5GC) 2740. 5GC 2740 may include Authentication Server Function (AUSF) 2742, Access and Mobility Management Function (AMF) 2744, Session Management Function (SMF) 2746, User Plane Function (UPF) 2748, Network Slice Selection Function (NSSF) 2750, Network Open Function (NEF) 2752, NF Storage Function (NRF) 2754, Policy Control Function (PCF) 2756, Unified Data Management (UDM) 2758, and Application Function (AF) 2760, as shown in the figure. These functions are coupled to each other through interfaces (or "reference points"). The functions of the components of 5GC 2740 can be briefly described below.

[0159] The AUSF 2742 can store data for UE 2702 authentication and handle authentication-related functions. The AUSF 2742 facilitates a common authentication framework for various access types. In addition to communicating with other components of the 5GC 2740 via a reference point, as shown in the figure, the AUSF 2742 can also demonstrate an interface based on Nausf services.

[0160] The AMF 2744 allows the 5GC 2740 to communicate with UE 2702 and RAN 2704, and subscribe to notifications regarding mobility events for UE 2702. The AMF 2744 can handle registration management (e.g., registering UE 2702), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 2744 can provide the transmission of Session Management (SM) messages between UE 2702 and SMF 2746, and acts as a transparent broker for routing SM messages. The AMF 2744 can also provide the transmission of SMS messages between UE 2702 and the SMSF. The AMF 2744 can interact with AMF 2742 and UE 2702 to perform various security anchoring and context management functions. Furthermore, the AMF 2744 can be the termination point of the RANCP interface, which may include or be the N2 reference point between RAN 2704 and AMF 2744; the AMF 2744 can serve as the termination point for NAS (N1) signaling and perform NAS encryption and integrity protection. The AMF 2744 can also support NAS signaling with UE 2702 via the N3 IWF interface.

[0161] SMF 2746 can be responsible for SM (e.g., session establishment, tunnel management between UPF 2748 and AN 2708); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring flow control at UPF 2748 to route traffic to appropriate destinations; termination of interfaces to policy control functions; control of policy enforcement, charging, and QoS as a part; lawful interception (for SM events and interfaces to the LI system); termination of the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information (sent to AN 2708 on N2 via AMF 2744); and determining the SSC mode of the session. SM can refer to the management of PDU sessions, and a PDU session or "session" can refer to the PDU connectivity service that provides or enables PDU exchange between UE 2702 and data network 2736.

[0162] The UPF 2748 can be used as an anchor point for mobility within and between RATs, an external PDU session point for interconnection with the data network 2736, and a branch point supporting multi-homed PDU sessions. The UPF 2748 can also perform packet routing and forwarding, packet inspection, user plane portion of policy rules, lawful packet interception (UP collection), traffic usage reporting, QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic authentication (e.g., SDF-to-QoS flow mapping), transport-level packet marking in uplink and downlink, and downlink packet buffering and downlink data notification triggering. The UPF 2748 may include an uplink classifier to support traffic flow routing to the data network.

[0163] The NSSF 2750 can select a set of network slice instances to serve UE 2702. If needed, the NSSF 2750 can also determine the allowed network slice selection assistance information (NSSAI) and the mapping to the subscribed individual NSSAI (S-NSSAI). The NSSF 2750 can also determine the set of AMFs to be used to serve UE 2702 based on appropriate configuration and possibly by querying the NRF 2754, or determine a list of candidate AMFs. The selection of a set of network slice instances for UE 2702 can be triggered by the AMF 2744 (which UE 2702 registers with by interacting with the NSSF 2750), resulting in a change of AMF. The NSSF 2750 can interact with the AMF 2744 via the N22 reference point; and can communicate with another NSSF in the visited network via the N31 reference point (not shown). Furthermore, the NSSF 2750 can expose an interface based on NNSSF services.

[0164] The NEF 2752 can securely disclose services and capabilities provided by 3GPP network functions for third parties, internal disclosure / redisclosure, AFs (e.g., AF 2760), edge computing, or fog computing systems. In these embodiments, the NEF 2752 can authenticate, authorize, or suppress AFs. The NEF 2752 can also translate information exchanged with AF 2760 and information exchanged with internal network functions. For example, the NEF 2752 can convert between AF service identifiers and internal 5GC information. The NEF 2752 can also receive information from other NFs based on their public capabilities. This information can be stored as structured data at the NEF 2752 or stored at a data storage NF using a standardized interface. The NEF 2752 can then redistribute the stored information to other NFs and AFs, or use it for other purposes such as analytics. Additionally, the NEF 2752 can expose interfaces based on Nnef services.

[0165] NRF 2754 supports service discovery, receiving NF discovery requests from NF instances and providing information about discovered NF instances to those instances. NRF 2754 also maintains information about available NF instances and the services they support. As used herein, the terms "instantiation," "instance," etc., can refer to the creation of an instance, and an "instance" can refer to the concrete occurrence of an object, such as during program code execution. Furthermore, NRF 2754 can demonstrate interfaces based on NRF services.

[0166] PCF 2756 can provide policy rules to control plane functions to enforce them, and can also support a unified policy framework to manage network behavior. PCF 2756 can also implement a frontend to access subscription information related to policy decisions in the UDR of UDM 2758. In addition to communicating with functions via reference points as shown in the figure, PCF 2756 also demonstrates an interface based on Npcf services.

[0167] UDM 2758 can process subscription-related information to support network entities in handling communication sessions and can store subscription data for UE 2702. For example, subscription data can be transmitted via the N8 reference point between UDM 2758 and AMF 2744. UDM 2758 may include two parts: an application front-end and a UDR. The UDR may store policy data and subscription data for UDM 2758 and PCF 2756, and / or structured data and application data for disclosure (including PFD for application detection and application request information for multiple UEs 2702) for NEF 2752. UDR 221 may expose a Nudr service-based interface to allow UDM 2758, PCF 2756, and NEF 2752 to access specific sets of stored data, as well as to read, update (e.g., add, modify), delete, and receive notifications of relevant data changes in the subscription UDR. UDM may include UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. Several different front-ends can provide services to the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via reference points as shown in the figure, the UDM 2758 can also demonstrate interfaces based on Nudm services.

[0168] The AF 2760 can provide application impact on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

[0169] In some embodiments, 5GC 2740 can enable edge computing by selecting an operator / third-party service that is geographically close to the point to which UE 2702 attaches to the network. This can reduce latency and load on the network. To provide edge computing implementation, 5GC 2740 can select a UPF 2748 close to UE 2702 and perform traffic routing from UPF 2748 to data network 2736 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF 2760. In this way, AF 2760 can influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 2760 is considered a trusted entity, the network operator can permit AF 2760 to interact directly with the relevant NF. Additionally, AF 2760 can expose interfaces based on Naf services.

[0170] Data network 2736 can represent various network operator services, Internet access, or third-party services that can be provided by one or more servers (including, for example, application / content server 2738).

[0171] Figure 28 A wireless network 2800 according to various embodiments is schematically illustrated. The wireless network 2800 may include a UE 2802 that communicates wirelessly with an AN 2804. The UE 2802 and the AN 2804 may be similar to and substantially interchangeable with equivalent components described elsewhere herein.

[0172] UE 2802 can be communicatively coupled to AN 2804 via connection 2806. Connection 2806 is shown as an air interface to enable communication coupling and can be consistent with cellular communication protocols operating at millimeter wave (mmWave) or sub-6 GHz frequencies, such as LTE or 5G NR protocols.

[0173] UE 2802 may include a host platform 2808 coupled to a modem platform 2810. Host platform 2808 may include application processing circuitry 2812, which may be coupled to protocol processing circuitry 2814 of modem platform 2810. Application processing circuitry 2812 may run various applications for UE 2802 to process source / receive application data. Application processing circuitry 2812 may also implement one or more layer operations to send / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.

[0174] Protocol processing circuitry 2814 can implement one or more layer operations to facilitate the transmission or reception of data via connection 2806. Layer operations implemented by protocol processing circuitry 2814 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0175] The modem platform 2810 may further include digital baseband circuitry 2816, which can implement one or more layer operations of "below" layer operations performed by protocol processing circuitry 2814 in the network protocol stack. These operations may include, for example, one or more of the following PHY operations: HARQ-ACK function, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, and multi-antenna port precoding / decoding. These functions may include one or more of the following: space-time, space-frequency, or spatial coding; reference signal generation / detection; preamble sequence generation and / or decoding; synchronization sequence generation / detection; blind decoding of control channel signals; and other related functions.

[0176] The modem platform 2810 may further include transmitting circuitry 2818, receiving circuitry 2820, RF circuitry 2822, and RF front-end (RFFE) circuitry 2824, which may include or be connected to one or more antenna panels 2826. In short, transmitting circuitry 2818 may include a digital-to-analog converter, mixer, intermediate frequency (IF) component, etc.; receiving circuitry 2820 may include an analog-to-digital converter, mixer, IF component, etc.; RF circuitry 2822 may include a low-noise amplifier, power amplifier, power tracking component, etc.; RFFE circuitry 2824 may include filters (e.g., surface acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of components of transmitting circuitry 2818, receiving circuitry 2820, RF circuitry 2822, RFFE circuitry 2824, and antenna panels 2826 (collectively, the "transmit / receive components") may be specific to the details of a particular implementation, such as whether the communication is TDM or FDM, at mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmitting / receiving components may be arranged in multiple parallel transmitting / receiving chains, and may be arranged in the same or different chips / modules, etc.

[0177] In some embodiments, the protocol processing circuitry 2814 may include one or more instances of control circuitry (not shown) to provide control functions for the transmitting / receiving components.

[0178] UE reception can be established via and through antenna panel 2826, RFFE circuit 2824, RF circuit 2822, receiving circuit 2820, digital baseband circuit 2816, and protocol processing circuit 2814. In some embodiments, antenna panel 2826 can receive transmissions from AN 2804 by receiving beamforming signals received by a plurality of antennas / antenna elements of one or more antenna panels 2826.

[0179] UE transmission can be established via and through protocol processing circuitry 2814, digital baseband circuitry 2816, transmission circuitry 2818, RF circuitry 2822, RFFE circuitry 2824, and antenna panel 2826. In some embodiments, the transmission components of UE 2804 can apply a spatial filter to the data to be transmitted to form a transmission beam emitted by the antenna elements of antenna panel 2826.

[0180] Similar to UE 2802, AN 2804 may include a host platform 2828 coupled to modem platform 2830. Host platform 2828 may include application processing circuitry 2832 coupled to protocol processing circuitry 2834 of modem platform 2830. Modem platform may also include digital baseband circuitry 2836, transmitting circuitry 2838, receiving circuitry 2840, RF circuitry 2842, RFFE circuitry 2844, and antenna panel 2846. Components of AN 2804 may be similar to their namesake components in UE 2802 and are substantially interchangeable with those in UE 2802. In addition to performing data transmission / reception as described above, components of AN 2808 may also perform various logical functions, including, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0181] Figure 29 This is a block diagram illustrating components, according to some example embodiments, capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more methods discussed herein. Specifically, Figure 29 A schematic representation of hardware resource 2900 is shown, which includes one or more processors (or processor cores) 2910, one or more memory / storage devices 2920, and one or more communication resources 2930, each of which can be communicatively coupled via bus 2940. Hardware resource 2900 may be part of a UE, AN, or LMF. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor 2902 may be executed to provide an execution environment for one or more network slices / subslices to utilize hardware resource 2900.

[0182] Processor 2910 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application-specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 2912 and processor 2914.

[0183] The memory / storage device 2920 may include main memory, disk storage devices, or any suitable combination thereof. The memory / storage device 2920 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage devices, etc.

[0184] Communication resource 2930 may include interconnect or network interface components or other suitable devices for communicating with one or more peripheral devices 2904 or one or more databases 2906 via network 2908. For example, communication resource 2930 may include wired communication components (e.g., for coupling via Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth (Bluetooth®) components (e.g., Bluetooth Low Energy), Wi-Fi components, and other communication components.

[0185] Instructions 2950 may include software, programs, applications, applets, or other executable code for causing at least any processor 2910 to perform any one or more of the methods discussed herein. Instructions 2950 may reside wholly or partially in at least one of the following: processor 2910 (e.g., within the processor's buffer memory), memory / storage device 2920, or any suitable combination thereof. Furthermore, any portion of instructions 2950 may be transferred to hardware resource 2900 from any combination of peripheral device 2904 or database 2906. Therefore, the memories of processor 2910, memory / storage device 2920, peripheral device 2904, and database 2906 are examples of computer-readable and machine-readable media.

[0186] The following paragraphs describe examples of various embodiments.

[0187] Example 1 includes an apparatus for a user equipment (UE), comprising: a radio frequency (RF) interface circuit configured to receive downlink control information (DCI) from a transmit / receive point (TRP), the DCI being used to schedule physical uplink control channel (PUCCH) transmissions to multiple TRPs; and a processing circuit coupled to the RF interface circuit and configured to: encode and multiplex multiple PUCCH repetitions targeting the multiple TRPs on one or more PUCCH resources based on PUCCH repetition-related configuration information indicated by the DCI or higher-level signaling; and provide the encoded and multiplexed PUCCH repetitions to the RF interface circuit for transmission to the multiple TRPs via the one or more PUCCH resources.

[0188] Example 2 includes the apparatus according to Example 1, wherein the PUCCH repeating related configuration information includes: an indication of whether the PUCCH repeating is enabled, and the type and number of PUCCH repeats when the PUCCH repeating is enabled.

[0189] Example 3 includes the apparatus according to Example 2, wherein the type of PUCCH repetition includes: frequency division multiplexing (FDM) based PUCCH repetition, time division multiplexing (TDM) based PUCCH repetition, or space division multiplexing (SDM) based PUCCH repetition.

[0190] Example 4 includes an apparatus according to any one of Examples 1 to 3, wherein the higher-layer signaling is Radio Resource Control (RRC) signaling, and at least one or more components of the PUCCH repeat-related configuration information are set in the RRC information element IE. PUCCH-Config middle.

[0191] Example 5 includes an apparatus according to any one of Examples 1 to 4, wherein the PUCCH repeat-related configuration information is configured at the PUCCH resource set level, the PUCCH resource level, or the PUCCH format level.

[0192] Example 6 includes an apparatus according to any one of Examples 1 to 5, wherein the plurality of TRPs are configured with the same cell identifier or different cell identifiers.

[0193] Example 7 includes an apparatus according to any one of Examples 1 to 6, wherein the processing circuitry is further configured to: determine the UE's capability regarding which type of PUCCH repetition it supports; encode an indication of the UE's capability; and provide the indication of the UE's capability to the RF interface circuitry for reporting to the TRP or a higher layer.

[0194] Example 8 includes an apparatus according to any one of Examples 1 to 7, wherein the PUCCH repeat is configured to transmit uplink control information, including one or more of Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK), Channel State Information (CSI), and Scheduling Request (SR).

[0195] Example 9 includes an apparatus according to any one of Examples 1 to 8, wherein, when the UE operates in frequency range 2, the processing circuitry is further configured to: determine a plurality of spatial relationships activated for the one or more PUCCH resources based on the PUCCH spatial relationship activation / deactivation medium access control-control element MAC-CE from the TRP; repeatedly map the PUCCH targeting the plurality of TRPs to the corresponding spatial relationships among the activated plurality of spatial relationships; and repeatedly provide the PUCCH to the RF interface circuitry for transmission to the plurality of TRPs via the one or more resources and the corresponding spatial relationships.

[0196] Example 10 includes the apparatus according to Example 9, wherein the MAC-CE is a group-based MAC-CE, comprising: a PUCCH Resource ID field for indicating an identifier ID of a PUCCH resource, and a spatial relationship information ID field for indicating an ID of a spatial relationship to be activated for the PUCCH resource.

[0197] Example 11 includes the apparatus according to Example 10, wherein the processing circuitry is further configured to update the activation space relationship of all PUCCH resources in the following PUCCH resource group based on the indicated activation space relationship of the PUCCH resources. resourceGroupToAddModList Configure and include the PUCCH resources indicated in the MAC-CE.

[0198] Example 12 includes the apparatus according to Example 10, wherein the one or more PUCCH resources comprise only a single PUCCH resource, and the single PUCCH resource is configured with the activated multiple spatial relationships based on the MAC-CE.

[0199] Example 13 includes the apparatus according to Example 12, wherein the MAC-CE includes: the PUCCH resource ID field, and a plurality of spatial relationship information ID fields for indicating the IDs of a plurality of spatial relationships to be activated for the PUCCH resource.

[0200] Example 14 includes the apparatus according to Example 12, wherein the MAC-CE includes: a plurality of PUCCH resource ID fields for indicating IDs of a plurality of PUCCH resources; and one or more spatial relationship information ID fields for indicating IDs of one or more spatial relationships to be activated for each of the plurality of PUCCH resources.

[0201] Example 15 includes the apparatus according to Example 12, wherein when the MAC-CE is configured to activate only one spatial relationship for a PUCCH resource, the processing circuitry is configured to ignore updates to the multiple activated spatial relationships based on the MAC-CE.

[0202] Example 16 includes the apparatus according to Example 13, wherein the processing circuitry is configured to update the activation space relationships of all PUCCH resources in a PUCCH resource group that have the same number of activation space relationships as the indicated PUCCH resource, based on the activation space relationships of the indicated PUCCH resource, wherein the PUCCH resource group is composed of... resourceGroupToAddModList Configure and include the PUCCH resource indicated in the MAC-CE.

[0203] Example 17 includes the apparatus according to Example 14, wherein the plurality of PUCCH resources are divided into separate PUCCH resource groups based on the number of active spatial relationships of the PUCCH resources, and the MAC-CE includes separate groups of PUCCH resource ID fields and spatial relationship information ID fields for indicating the separate PUCCH resource groups having different numbers of active spatial relationships.

[0204] Example 18 includes the apparatus according to Example 16, wherein the processing circuitry is further configured to update one or more activation space relationships of all PUCCH resources in a PUCCH resource group that have the same number of activation space relationships as the indicated PUCCH resource, based on one or more activation space relationships of the indicated PUCCH resource, wherein the PUCCH resource group is composed of... resourceGroupToAddModList Configure and include the PUCCH resources indicated in the MAC-CE.

[0205] Example 19 includes an apparatus according to any one of Examples 10 to 18, wherein, for each indicated PUCCH resource and each active space relationship of the indicated PUCCH resource, the MAC-CE further includes a group ID field for identifying a group of PUCCH resources, the PUCCH resource group being composed of... resourceGroupToAddModList Configure and include the indicated PUCCH resource with the said active spatial relationship.

[0206] Example 20 includes the apparatus according to Example 19, wherein the processing circuitry is further configured to update the activation space relationship of all PUCCH resources in the following PUCCH resource group based on the activation space relationship of the indicated PUCCH resources, the PUCCH resource group being composed of resourceGroupToAddModList Configured and identified by the group ID field corresponding to the indicated PUCCH resource having the said activation space relationship.

[0207] Example 21 includes an apparatus according to any one of Examples 10 to 18, wherein for each indicated PUCCH resource and each active spatial relationship of the indicated PUCCH resource, the MAC-CE further includes a reserved field 'R', the reserved field 'R' including an presence indication bit 'P' to indicate whether the active spatial relationship exists in the MAC-CE.

[0208] Example 22 includes an apparatus according to any one of Examples 10 to 21, wherein the MAC-CE further includes: a serving cell ID field for indicating the ID of the serving cell to which the MAC-CE is applied; and a bandwidth portion BWP ID field for indicating the ID of the uplink BWP to which the MAC-CE is applied.

[0209] Example 23 includes an apparatus according to any one of Examples 10 to 11, wherein the one or more PUCCH resources comprise a plurality of PUCCH resources, and each PUCCH resource is configured with an activation space relationship based on the MAC-CE.

[0210] Example 24 includes the apparatus according to Example 23, wherein one or more dedicated subsets of PUCCH resources in a PUCCH resource set are configured for the transmission of repeated PUCCHs, and all PUCCH resources in a subset of PUCCH resources are configured with the same PUCCH format.

[0211] Example 25 includes the apparatus according to Example 24, wherein the processing circuitry is configured to encode and multiplex the PUCCH repeat by: determining a subset of PUCCH resources for transmission of the PUCCH repeat based on a dedicated field in the DCI, and sequentially mapping the PUCCH resources in the subset of PUCCH resources to the PUCCH repeat.

[0212] Example 26 includes the apparatus according to Example 24, wherein the processing circuitry is configured to encode and multiplex the PUCCH repeat by: determining a subset of PUCCH resources for transmission of the PUCCH repeat based on a PUCCH resource indicator PRI in the DCI, mapping the PUCCH resources indicated by the PRI to a first PUCCH repeat in the PUCCH repeat, and mapping the remaining resources in the subset of PUCCH resources to subsequent PUCCH repeats in the PUCCH repeat.

[0213] Example 27 includes the apparatus according to Example 23, wherein the processing circuitry is further configured to: determine multiple spatial relationships for transmission of the PUCCH repetition based on the DCI or the higher-layer signaling; and through each k Each PUCCH is repeatedly assigned a different spatial relationship, mapping the PUCCH repeat to the multiple spatial relationships, wherein... k It is the number of times the PUCCH is repeated from 1. NThe integers between, and configured by a higher layer or indicated by the DCI; and the encoded and multiplexed PUCCHs are repeatedly provided to the RF interface circuitry for transmission to the multiple TRPs via the one or more PUCCH resources and the multiple spatial relationships.

[0214] Example 28 includes the apparatus according to Example 12, wherein when the type of PUCCH repetition is an FDM-based PUCCH repetition, the PUCCH format of the single PUCCH resource supports multiple consecutive Physical Resource Blocks (PRBs), and the multiple PRBs are equally divided into multiple portions respectively corresponding to the PUCCH repetition.

[0215] Example 29 includes the apparatus according to Example 12, wherein when the type of PUCCH repetition is TDM-based PUCCH repetition, the PUCCH format of the single PUCCH resource supports multiple consecutive orthogonal frequency division multiplexing OFDM symbols or time slots, and the multiple OFDM symbols or time slots are equally divided into multiple parts respectively corresponding to the PUCCH repetition.

[0216] Example 30 includes the apparatus according to Example 23, wherein when the type of PUCCH repetition is TDM-based PUCCH repetition, the plurality of PUCCH resources occupy continuous or discontinuous orthogonal frequency division multiplexing (OFDM) symbols or time slots, and the processing circuitry is configured to encode and multiplex the PUCCH repetition by mapping the PUCCH repetition to the plurality of PUCCH resources at the time slot level or sub-time slot level.

[0217] Example 31 includes the apparatus according to Example 12 or 23, wherein when the type of PUCCH repetition is SDM-based PUCCH repetition, the same frequency domain resources and the same time domain resources are configured for the transmission of the PUCCH repetition.

[0218] Example 32 includes a method performed at a user equipment (UE), comprising: receiving downlink control information (DCI) from a transmit / receive point (TRP), the DCI being used to schedule physical uplink control channel (PUCCH) transmissions to multiple TRPs; encoding and multiplexing multiple PUCCH repetitions targeting the multiple TRPs on one or more PUCCH resources based on PUCCH repetition-related configuration information indicated by the DCI or higher-level signaling; and transmitting the encoded and multiplexed PUCCH repetitions to the multiple TRPs via the one or more PUCCH resources.

[0219] Example 33 includes the method according to Example 32, wherein the PUCCH repeating related configuration information includes: an indication of whether the PUCCH repeating is enabled, and the type and number of PUCCH repeats when the PUCCH repeating is enabled.

[0220] Example 34 includes the method according to Example 33, wherein the type of PUCCH repetition includes: frequency division multiplexing (FDM) based PUCCH repetition, time division multiplexing (TDM) based PUCCH repetition, or space division multiplexing (SDM) based PUCCH repetition.

[0221] Example 35 includes the method according to any one of Examples 32 to 34, wherein the higher-layer signaling is Radio Resource Control (RRC) signaling, and at least one or more components of the PUCCH repeat-related configuration information are set in the RRC information element IE. PUCCH-Config middle.

[0222] Example 36 includes the method according to any one of Examples 32 to 34, wherein the PUCCH repeat-related configuration information is configured at the PUCCH resource set level, the PUCCH resource level, or the PUCCH format level.

[0223] Example 37 includes the method according to any one of Examples 32 to 36, wherein the plurality of TRPs are configured with the same cell identifier or different cell identifiers.

[0224] Example 38 includes the method according to any one of Examples 32 to 37, further comprising: determining the UE's capability to support which type of PUCCH repetition; encoding an indication of the UE's capability; and reporting the indication of the UE's capability to the TRP or a higher layer.

[0225] Example 39 includes a method according to any one of Examples 32 to 38, wherein the PUCCH repeat is configured to transmit uplink control information, including one or more of Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK), Channel State Information (CSI), and Scheduling Request (SR).

[0226] Example 40 includes the method according to any one of Examples 32 to 39, wherein, when the UE operates in frequency range 2, the method further includes: determining a plurality of spatial relationships activated for the one or more PUCCH resources based on the activation / deactivation of the medium access control-control element MAC-CE from the TRP; mapping the PUCCH repeats targeting the plurality of TRPs to the corresponding spatial relationships among the activated plurality of spatial relationships; and transmitting the PUCCH repeats through the one or more resources and the corresponding spatial relationships to the plurality of TRPs.

[0227] Example 41 includes the method according to Example 40, wherein the MAC-CE is a group-based MAC-CE, comprising: a PUCCH Resource ID field for indicating an identifier ID of a PUCCH resource, and a spatial relationship information ID field for indicating an ID of a spatial relationship to be activated for the PUCCH resource.

[0228] Example 42 includes the method according to Example 41, further comprising: updating the activation space relationship of all PUCCH resources in the following PUCCH resource group based on the activation space relationship of the indicated PUCCH resources, wherein the PUCCH resource group is composed of... resourceGroupToAddModList Configure and include the PUCCH resources indicated in the MAC-CE.

[0229] Example 43 includes the method according to Example 41, wherein the one or more PUCCH resources comprise only a single PUCCH resource, and the single PUCCH resource is configured with the activated multiple spatial relationships based on the MAC-CE.

[0230] Example 44 includes the method according to Example 43, wherein the MAC-CE includes: the PUCCH resource ID field, and a plurality of spatial relationship information ID fields for indicating the IDs of a plurality of spatial relationships to be activated for the PUCCH resource.

[0231] Example 45 includes the method according to Example 43, wherein the MAC-CE includes: a plurality of PUCCH resource ID fields for indicating IDs of a plurality of PUCCH resources; and one or more spatial relationship information ID fields for indicating IDs of one or more spatial relationships to be activated for each of the plurality of PUCCH resources.

[0232] Example 46 includes the method according to Example 43, wherein when the MAC-CE is configured to activate only one spatial relationship for a PUCCH resource, the method further includes ignoring updates to the activated multiple spatial relationships based on the MAC-CE.

[0233] Example 47 includes the method according to Example 44, further comprising: updating the activation space relationships of all PUCCH resources in a PUCCH resource group that have the same number of activation space relationships as the indicated PUCCH resource, based on the activation space relationships of the indicated PUCCH resource, wherein the PUCCH resource group is composed of... resourceGroupToAddModList Configure and include the PUCCH resource indicated in the MAC-CE.

[0234] Example 48 includes the method according to Example 45, wherein the plurality of PUCCH resources are divided into separate PUCCH resource groups based on the number of active spatial relationships of the PUCCH resources, and the MAC-CE includes separate groups of PUCCH resource ID fields and spatial relationship information ID fields for indicating the separate PUCCH resource groups having different numbers of active spatial relationships.

[0235] Example 49 includes the method according to Example 48, further comprising: updating one or more activation space relationships of all PUCCH resources in a PUCCH resource group that have the same number of activation space relationships as the indicated PUCCH resource, based on one or more activation space relationships of the indicated PUCCH resource, wherein the PUCCH resource group is composed of... resourceGroupToAddModList Configure and include the PUCCH resources indicated in the MAC-CE.

[0236] Example 50 includes the method according to any one of Examples 41 to 49, wherein, for each indicated PUCCH resource and each activation space relationship of the indicated PUCCH resource, the MAC-CE further includes a group ID field for identifying a PUCCH resource group composed of... resourceGroupToAddModList Configure and include the indicated PUCCH resource with the said active spatial relationship.

[0237] Example 51 includes the method according to Example 50, further comprising: updating the activation space relationship of all PUCCH resources in the following PUCCH resource group based on the activation space relationship of the indicated PUCCH resources, wherein the PUCCH resource group is composed of resourceGroupToAddModList Configured and identified by the group ID field corresponding to the indicated PUCCH resource having the said activation space relationship.

[0238] Example 52 includes the method according to any one of Examples 41 to 49, wherein for each indicated PUCCH resource and each active spatial relationship of the indicated PUCCH resource, the MAC-CE further includes a reserved field 'R', the reserved field 'R' including an presence indication bit 'P' to indicate whether the active spatial relationship exists in the MAC-CE.

[0239] Example 53 includes the method according to any one of Examples 41 to 52, wherein the MAC-CE further includes: a serving cell ID field for indicating the ID of the serving cell to which the MAC-CE is applied; and a bandwidth portion BWP ID field for indicating the ID of the uplink BWP to which the MAC-CE is applied.

[0240] Example 54 includes the method according to any one of Examples 41 to 42, wherein the one or more PUCCH resources comprise a plurality of PUCCH resources, and each PUCCH resource is configured with an activation space relationship based on the MAC-CE.

[0241] Example 55 includes the method according to Example 54, wherein one or more dedicated subsets of PUCCH resources in a PUCCH resource set are configured for the transmission of PUCCH repetitions, and all PUCCH resources in a subset of PUCCH resources are configured with the same PUCCH format.

[0242] Example 56 includes the method according to Example 55, wherein encoding and multiplexing the PUCCH repeat comprises: determining a subset of PUCCH resources for transmission of the PUCCH repeat based on a dedicated field in the DCI, and sequentially mapping the PUCCH resources in the subset of PUCCH resources to the PUCCH repeat.

[0243] Example 57 includes the method according to Example 55, wherein encoding and multiplexing the PUCCH repeat comprises: determining a subset of PUCCH resources for transmission of the PUCCH repeat based on a PUCCH resource indicator PRI in the DCI, mapping the PUCCH resources indicated by the PRI to a first PUCCH repeat in the PUCCH repeat, and mapping the remaining resources in the subset of PUCCH resources to subsequent PUCCH repeats in the PUCCH repeat.

[0244] Example 58 includes the method according to Example 54, further comprising: determining multiple spatial relationships for transmissions used in the PUCCH repetition based on the DCI or the higher-layer signaling; and through each kEach PUCCH is repeatedly assigned a different spatial relationship, mapping the PUCCH repeat to the multiple spatial relationships, wherein... k It is the number of times the PUCCH is repeated from 1. N The integers between, and configured by a higher layer or indicated by the DCI; and the encoded and multiplexed PUCCHs are repeatedly provided to the RF interface circuitry for transmission to the multiple TRPs via the one or more PUCCH resources and the multiple spatial relationships.

[0245] Example 59 includes the method according to Example 43, wherein when the type of PUCCH repetition is an FDM-based PUCCH repetition, the PUCCH format of the single PUCCH resource supports multiple consecutive Physical Resource Blocks (PRBs), and the multiple PRBs are equally divided into multiple parts respectively corresponding to the PUCCH repetition.

[0246] Example 60 includes the method according to Example 43, wherein when the type of PUCCH repetition is TDM-based PUCCH repetition, the PUCCH format of the single PUCCH resource supports multiple consecutive orthogonal frequency division multiplexing OFDM symbols or time slots, and the multiple OFDM symbols or time slots are equally divided into multiple parts respectively corresponding to the PUCCH repetition.

[0247] Example 61 includes the method according to Example 54, wherein when the type of PUCCH repetition is TDM-based PUCCH repetition, the plurality of PUCCH resources occupy continuous or discontinuous orthogonal frequency division multiplexing (OFDM) symbols or time slots, and the encoding and multiplexing of the PUCCH repetition includes: mapping the PUCCH repetition to the plurality of PUCCH resources at the time slot level or sub-time slot level.

[0248] Example 62 includes the method according to Example 43 or 54, wherein when the type of PUCCH repetition is SDM-based PUCCH repetition, the same frequency domain resources and the same time domain resources are configured for the transmission of the PUCCH repetition.

[0249] Example 63 includes an apparatus for transmitting a receive point (TRP), comprising: a radio frequency (RF) interface circuit; and processing circuitry coupled to the RF interface circuitry and configured to: encode downlink control information (DCI) or higher-level signaling for instructing a UE on PUCCH repetition-related configuration information and allocating one or more PUCCH resources for PUCCH repetition transmission from the UE to multiple TRPs; and provide the encoded DCI or higher-level signaling to the RF interface circuitry for transmission to the UE.

[0250] Example 64 includes the apparatus according to Example 63, wherein the PUCCH repeat-related configuration information includes: an indication of whether the PUCCH repeat is enabled, and the type and number of PUCCH repeats when the PUCCH repeat is enabled.

[0251] Example 65 includes the apparatus according to Example 64, wherein the type of PUCCH repetition includes: frequency division multiplexing (FDM) based PUCCH repetition, time division multiplexing (TDM) based PUCCH repetition, or space division multiplexing (SDM) based PUCCH repetition.

[0252] Example 66 includes an apparatus according to any one of Examples 63 to 65, wherein the higher-layer signaling is Radio Resource Control (RRC) signaling, and at least one or more components of the PUCCH repeat-related configuration information are set in the RRC information element IE. PUCCH-Config middle.

[0253] Example 67 includes an apparatus according to any one of Examples 63 to 65, wherein the PUCCH repeat-related configuration information is configured at the PUCCH resource set level, the PUCCH resource level, or the PUCCH format level.

[0254] Example 68 includes an apparatus according to any one of Examples 63 to 67, wherein the plurality of TRPs are configured with the same cell identifier or different cell identifiers.

[0255] Example 69 includes an apparatus according to any one of Examples 63 to 68, wherein, when the UE operates in frequency range 2, the processing circuitry is further configured to: encode a PUCCH spatial relation activation / deactivation medium access control-control element MAC-CE, the MAC-CE indicating a plurality of spatial relations activated for the one or more PUCCH resources; and provide the encoded PUCCH spatial relation activation / deactivation MAC-CE to the RF interface circuitry for transmission to the UE.

[0256] Example 70 includes the apparatus according to Example 69, wherein the MAC-CE is a group-based MAC-CE, comprising: a PUCCH Resource ID field for indicating an identifier ID of a PUCCH resource, and a spatial relationship information ID field for indicating an ID of a spatial relationship to be activated for the PUCCH resource.

[0257] Example 71 includes the apparatus according to Example 70, wherein the one or more PUCCH resources comprise only a single PUCCH resource, and the single PUCCH resource is configured with the activated multiple spatial relationships based on the MAC-CE.

[0258] Example 72 includes the apparatus according to Example 71, wherein the MAC-CE includes: the PUCCH resource ID field, and a plurality of spatial relationship information ID fields for indicating the IDs of a plurality of spatial relationships to be activated for the PUCCH resource.

[0259] Example 73 includes the apparatus according to Example 71, wherein the MAC-CE includes: a plurality of PUCCH resource ID fields for indicating IDs of a plurality of PUCCH resources; and one or more spatial relationship information ID fields for indicating IDs of one or more spatial relationships to be activated for each of the plurality of PUCCH resources.

[0260] Example 74 includes the apparatus according to Example 73, wherein the plurality of PUCCH resources are divided into separate PUCCH resource groups based on the number of active spatial relationships of the PUCCH resources, and the MAC-CE includes separate groups of PUCCH resource ID fields and spatial relationship information ID fields for indicating the separate PUCCH resource groups having different numbers of active spatial relationships.

[0261] Example 75 includes an apparatus according to any one of Examples 70 to 74, wherein, for each indicated PUCCH resource and each active space relationship of the indicated PUCCH resource, the MAC-CE further includes a group ID field for identifying a group of PUCCH resources, the PUCCH resource group being composed of... resourceGroupToAddModList Configure and include the indicated PUCCH resource with the said active spatial relationship.

[0262] Example 76 includes an apparatus according to any one of Examples 70 to 74, wherein, for each indicated PUCCH resource and each active spatial relationship of the indicated PUCCH resource, the MAC-CE further includes a reserved field 'R', the reserved field 'R' including an presence indication bit 'P' to indicate whether the active spatial relationship exists in the MAC-CE.

[0263] Example 77 includes an apparatus according to any one of Examples 70 to 76, wherein the MAC-CE further includes: a serving cell ID field for indicating the ID of the serving cell to which the MAC-CE is applied; and a bandwidth portion BWP ID field for indicating the ID of the uplink BWP to which the MAC-CE is applied.

[0264] Example 78 includes the apparatus according to Example 70, wherein the one or more PUCCH resources include a plurality of PUCCH resources, and each PUCCH resource is configured with an activation space relationship based on the MAC-CE.

[0265] Example 79 includes the apparatus according to Example 78, wherein, based on the DCI or the higher-layer signaling, one or more dedicated subsets of PUCCH resources in a PUCCH resource set are configured for the transmission of PUCCH repetitions, and all PUCCH resources in a subset of PUCCH resources are configured with the same PUCCH format.

[0266] Example 80 includes the apparatus according to Example 79, wherein the DCI includes a PUCCH resource indicator PRI, and a subset of PUCCH resources including the PUCCH resources indicated by the PRI is configured to transmit the PUCCH repeat.

[0267] Example 81 includes an apparatus according to Example 80, wherein the PUCCH resources indicated by the PRI are allocated for transmitting a first PUCCH repeat in the PUCCH repeat, and the remaining resources in the subset of the PUCCH resources are allocated for transmitting subsequent PUCCH repeats in the PUCCH repeat.

[0268] Example 82 includes the apparatus according to Example 71, wherein when the type of PUCCH repetition is FDM-based PUCCH repetition, the PUCCH format of the single PUCCH resource supports multiple consecutive Physical Resource Blocks (PRBs), and the multiple PRBs are equally divided into multiple portions respectively corresponding to the PUCCH repetition.

[0269] Example 83 includes the apparatus according to Example 71, wherein when the type of PUCCH repetition is TDM-based PUCCH repetition, the PUCCH format of the single PUCCH resource supports multiple consecutive orthogonal frequency division multiplexing OFDM symbols or time slots, and the multiple OFDM symbols or time slots are equally divided into multiple parts respectively corresponding to the PUCCH repetition.

[0270] Example 84 includes the apparatus according to Example 71 or 78, wherein when the type of PUCCH repetition is SDM-based PUCCH repetition, the same frequency domain resources and the same time domain resources are configured for the transmission of the PUCCH repetition.

[0271] Example 85 includes a method performed at a Transmitting and Receiving Point (TRP) comprising: encoding downlink control information (DCI) or higher-level signaling for instructing a UE on PUCCH repetition-related configuration information and allocating one or more PUCCH resources for PUCCH repetition transmission from the UE to multiple TRPs; and transmitting the encoded DCI or higher-level signaling to the UE.

[0272] Example 86 includes the method according to Example 85, wherein the PUCCH repeat-related configuration information includes: an indication of whether the PUCCH repeat is enabled, and the type and number of PUCCH repeats when the PUCCH repeat is enabled.

[0273] Example 87 includes the method according to Example 86, wherein the type of PUCCH repetition includes: frequency division multiplexing (FDM) based PUCCH repetition, time division multiplexing (TDM) based PUCCH repetition, or space division multiplexing (SDM) based PUCCH repetition.

[0274] Example 88 includes the method according to any one of Examples 85 to 87, wherein the higher-layer signaling is Radio Resource Control (RRC) signaling, and at least one or more components of the PUCCH repeat-related configuration information are set in the RRC information element IE. PUCCH-Config middle.

[0275] Example 89 includes the method according to any one of Examples 85 to 87, wherein the PUCCH repeat-related configuration information is configured at the PUCCH resource set level, the PUCCH resource level, or the PUCCH format level.

[0276] Example 90 includes the method according to any one of Examples 85 to 89, wherein the plurality of TRPs are configured with the same cell identifier or different cell identifiers.

[0277] Example 91 includes the method according to any one of Examples 85 to 90, wherein, when the UE is operating in frequency range 2, the method further includes: encoding a PUCCH spatial relation activation / deactivation medium access control-control element MAC-CE, the MAC-CE being used to indicate a plurality of spatial relations activated for the one or more PUCCH resources; and transmitting the encoded PUCCH spatial relation activation / deactivation MAC-CE to the UE.

[0278] Example 92 includes the method according to Example 91, wherein the MAC-CE is a group-based MAC-CE, comprising: a PUCCH Resource ID field for indicating an identifier ID of a PUCCH resource, and a spatial relationship information ID field for indicating an ID of a spatial relationship to be activated for the PUCCH resource.

[0279] Example 93 includes the method according to Example 92, wherein the one or more PUCCH resources comprise only a single PUCCH resource, and the single PUCCH resource is configured with the activated multiple spatial relationships based on the MAC-CE.

[0280] Example 94 includes the method according to Example 93, wherein the MAC-CE includes: the PUCCH resource ID field, and a plurality of spatial relationship information ID fields for indicating the IDs of a plurality of spatial relationships to be activated for the PUCCH resource.

[0281] Example 95 includes the method according to Example 93, wherein the MAC-CE includes: a plurality of PUCCH resource ID fields for indicating IDs of a plurality of PUCCH resources; and one or more spatial relationship information ID fields for indicating IDs of one or more spatial relationships to be activated for each of the plurality of PUCCH resources.

[0282] Example 96 includes the method according to Example 95, wherein the plurality of PUCCH resources are divided into separate PUCCH resource groups based on the number of active spatial relationships of the PUCCH resources, and the MAC-CE includes separate groups of PUCCH resource ID fields and spatial relationship information ID fields for indicating the separate PUCCH resource groups having different numbers of active spatial relationships.

[0283] Example 97 includes the method according to any one of Examples 92 to 96, wherein, for each indicated PUCCH resource and each activation space relationship of the indicated PUCCH resource, the MAC-CE further includes a group ID field for identifying a PUCCH resource group composed of... resourceGroupToAddModList Configure and include the indicated PUCCH resource with the said active spatial relationship.

[0284] Example 98 includes the method according to any one of Examples 92 to 96, wherein, for each indicated PUCCH resource and each active spatial relationship of the indicated PUCCH resource, the MAC-CE further includes a reserved field 'R', the reserved field 'R' including an presence indication bit 'P' to indicate whether the active spatial relationship exists in the MAC-CE.

[0285] Example 99 includes the method according to any one of Examples 92 to 98, wherein the MAC-CE further includes: a serving cell ID field for indicating the ID of the serving cell to which the MAC-CE is applied; and a bandwidth portion BWP ID field for indicating the ID of the uplink BWP to which the MAC-CE is applied.

[0286] Example 100 includes the method according to Example 92, wherein the one or more PUCCH resources include a plurality of PUCCH resources, and each PUCCH resource is configured with an activation space relationship based on the MAC-CE.

[0287] Example 101 includes the method according to Example 100, wherein, based on the DCI or the higher-layer signaling, one or more dedicated PUCCH resource subsets in a PUCCH resource set are configured for the transmission of PUCCH repetitions, and all PUCCH resources in a PUCCH resource subset are configured with the same PUCCH format.

[0288] Example 102 includes the method according to Example 101, wherein the DCI includes a PUCCH resource indicator PRI, and a subset of PUCCH resources including the PUCCH resources indicated by the PRI is configured to transmit the PUCCH repeat.

[0289] Example 103 includes the method according to Example 102, wherein the PUCCH resources indicated by the PRI are allocated for transmitting a first PUCCH repeat in the PUCCH repeat, and the remaining resources in the subset of the PUCCH resources are allocated for transmitting subsequent PUCCH repeats in the PUCCH repeat.

[0290] Example 104 includes the method according to Example 93, wherein when the type of PUCCH repetition is an FDM-based PUCCH repetition, the PUCCH format of the single PUCCH resource supports multiple consecutive Physical Resource Blocks (PRBs), and the multiple PRBs are equally divided into multiple parts respectively corresponding to the PUCCH repetition.

[0291] Example 105 includes the method according to Example 93, wherein when the type of PUCCH repetition is TDM-based PUCCH repetition, the PUCCH format of the single PUCCH resource supports multiple consecutive orthogonal frequency division multiplexing OFDM symbols or time slots, and the multiple OFDM symbols or time slots are equally divided into multiple parts respectively corresponding to the PUCCH repetition.

[0292] Example 106 includes the method according to Example 93 or 100, wherein when the type of PUCCH repetition is SDM-based PUCCH repetition, the same frequency domain resources and the same time domain resources are configured for the transmission of the PUCCH repetition.

[0293] Example 107 includes a computer-readable medium having instructions stored thereon, wherein the instructions, when executed by a processing circuit of a user equipment (UE), cause the processing circuit to perform a method as described in any one of Examples 32 to 62.

[0294] Example 108 includes a computer-readable medium having instructions stored thereon, wherein the instructions, when executed by processing circuitry of a transmit-receive point (TRP), cause the processing circuitry to perform the method as described in any one of Examples 85 to 106.

[0295] Example 109 includes an apparatus for a user equipment (UE) including means for performing the method as described in any one of Examples 32 to 62.

[0296] Example 110 includes an apparatus for transmitting a receiving point TRP, including means for performing the method as described in any one of Examples 85 to 106.

[0297] Example 111 includes an apparatus for a user equipment (UE), comprising: a radio frequency (RF) interface circuit configured to receive downlink control information (DCI) from a transmit / receive point (TRP) for scheduling transmission of physical uplink shared channel (PUSCH) repetitions to multiple TRPs based on time division multiplexing (TDM); and processing circuitry coupled to the RF interface circuitry and configured to: encode and multiplex the TDM-based PUSCH repetitions by mapping each PUSCH repetition targeting the same TRP among the multiple TRPs to different frequency domain resources, the different frequency domain resources corresponding to each PUSCH repetition and determined by a predefined inter-repetition frequency hopping pattern; and providing the encoded and multiplexed TDM-based PUSCH repetitions to the RF interface circuitry for transmission to the multiple TRPs.

[0298] Example 112 includes the apparatus according to Example 111, wherein the inter-repetition frequency hopping mode is based on the frequency allocation size for the TDM-based PUSCH repetition and the index of the PUSCH repetition. n Index of target TRP k The relationship between them is predefined, where n From 0 to N Integers in the range of -1 k From 0 to K Integers in the range of -1K The total number of the multiple TRPs, N The total number of PUSCH repetitions based on TDM.

[0299] Example 113 includes the apparatus according to Example 112, wherein the TDM-based PUSCH repetitions are configured with the same frequency allocation size, and the index of the target TRP... k Depend on k = n mod K Given, and the frequency hopping pattern between repetitions is predefined by the following formula: , in, Is the index as n The PUSCH repeats the starting resource block RB. It is the starting RB within the uplink bandwidth portion of the BWP. It is the frequency offset between frequency hops, measured in RBs, and It is the number of Physical Resource Blocks (PRBs) of size BWP activated on the uplink.

[0300] Example 114 includes the apparatus according to Example 112, wherein the TDM-based PUSCH repetitions are configured with the same frequency allocation size, and the index of the target TRP... k Depend on Given, and the frequency hopping pattern between repetitions is predefined by the following formula: , in, Is the index as n The PUSCH repeats the starting resource block RB. It is the starting RB within the uplink bandwidth portion of the BWP. It is the frequency offset between frequency hops, measured in RBs, and It is the number of Physical Resource Blocks (PRBs) of size BWP activated on the uplink.

[0301] Example 115 includes the apparatus according to Example 112, wherein the TDM-based PUSCH repetitions are configured with the same frequency allocation size, and the index of the target TRP... k Depend on Given, and the frequency hopping pattern between repetitions is predefined by the following formula: , in, Is the index as n The PUSCH repeats the starting resource block RB. It is the starting RB within the uplink bandwidth portion of the BWP. It is the frequency offset between frequency hops, measured in RBs, and It is the number of Physical Resource Blocks (PRBs) of size BWP activated on the uplink.

[0302] Example 116 includes the apparatus according to Example 112, wherein the TDM-based PUSCH repetitions targeting different TRPs are configured with different frequency allocation sizes, the index of the target TRP... k Depend on k = n mod K Given, and the frequency hopping pattern between repetitions is predefined by the following formula: , in, Is the index as n The PUSCH repeats the starting resource block RB. This is for indexes. k The uplink bandwidth portion of the TRP within the starting RB of the BWP, This is for indexes. k The frequency offset between TRP frequency hopping intervals, in RB units, and It is the number of Physical Resource Blocks (PRBs) of size BWP activated on the uplink.

[0303] Example 117 includes the apparatus according to Example 112, wherein the TDM-based PUSCH repetitions targeting different TRPs are configured with different frequency allocation sizes, the index of the target TRP... k Depend on Given, and the frequency hopping pattern between repetitions is predefined by the following formula: , in, Is the index as n The PUSCH repeats the starting resource block RB. This is for indexes. k The uplink bandwidth portion of the TRP within the starting RB of the BWP, This is for indexes. k The frequency offset between TRP frequency hopping intervals, in RB units, and It is the number of Physical Resource Blocks (PRBs) of size BWP activated on the uplink.

[0304] Example 118 includes the apparatus according to Example 112, wherein the TDM-based PUSCH repetitions targeting different TRPs are configured with different frequency allocation sizes, the index of the target TRP being... k Depend on Given, and the frequency hopping pattern between repetitions is predefined by the following formula: , in, Is the index as n The PUSCH repeats the starting resource block RB. This is for indexes. k The uplink bandwidth portion of the TRP within the starting RB of the BWP, This is for indexes. k The frequency offset between TRP frequency hopping intervals, in RB units, and It is the number of Physical Resource Blocks (PRBs) of size BWP activated on the uplink.

[0305] Example 119 includes an apparatus according to any one of Examples 116 to 118, wherein the TDM-based PUSCH repeats targeting the same TRP are configured with the same frequency allocation size.

[0306] Example 120 includes a method performed at a user equipment (UE), comprising: receiving downlink control information (DCI) from a transmit / receive point (TRP) for scheduling transmissions of physical uplink shared channel (PUSCH) repetitions to multiple TRPs based on time division multiplexing (TDM); encoding and multiplexing the TDM-based PUSCH repetitions by mapping each PUSCH repetition targeting the same TRP among the multiple TRPs to different frequency domain resources, the different frequency domain resources corresponding to each PUSCH repetition and determined by a predefined inter-repetition frequency hopping pattern; and transmitting the encoded and multiplexed TDM-based PUSCH repetitions to the multiple TRPs.

[0307] Example 121 includes the method according to Example 120, wherein the inter-repetition frequency hopping mode is based on the frequency allocation size for the TDM-based PUSCH repetition and the index of the PUSCH repetition. n Index of target TRP k The relationship between them is predefined, where n From 0 to N Integers in the range of -1 k From 0 to K Integers in the range of -1 K The total number of the multiple TRPs, N The total number of PUSCH repetitions based on TDM.

[0308] Example 122 includes the method according to Example 121, wherein the TDM-based PUSCH repeats are configured with the same frequency allocation size, and the index of the target TRP... k Depend on k = n mod K Given, and the frequency hopping pattern between repetitions is predefined by the following formula: , in, Is the index as n The PUSCH repeats the starting resource block RB. It is the starting RB within the uplink bandwidth portion of the BWP. It is the frequency offset between frequency hops, measured in RBs, and It is the number of Physical Resource Blocks (PRBs) of size BWP activated on the uplink.

[0309] Example 123 includes the method according to Example 121, wherein the TDM-based PUSCH repetitions are configured with the same frequency allocation size, and the index of the target TRP... k Depend on Given, and the frequency hopping pattern between repetitions is predefined by the following formula: , in, Is the index as n The PUSCH repeats the starting resource block RB. It is the starting RB within the uplink bandwidth portion of the BWP. It is the frequency offset between frequency hops, measured in RBs, and It is the number of Physical Resource Blocks (PRBs) of size BWP activated on the uplink.

[0310] Example 124 includes the method according to Example 121, wherein the TDM-based PUSCH repeats are configured with the same frequency allocation size, and the index of the target TRP... k Depend on Given, and the frequency hopping pattern between repetitions is predefined by the following formula: , in, Is the index as n The PUSCH repeats the starting resource block RB. It is the starting RB within the uplink bandwidth portion of the BWP. It is the frequency offset between frequency hops, measured in RBs, and It is the number of Physical Resource Blocks (PRBs) of size BWP activated on the uplink.

[0311] Example 125 includes the method according to Example 121, wherein the TDM-based PUSCH repetitions targeting different TRPs are configured with different frequency allocation sizes, the index of the target TRP... k Depend on k = n mod K Given, and the frequency hopping pattern between repetitions is predefined by the following formula: , in, Is the index as n The PUSCH repeats the starting resource block RB. This is for indexes. k The uplink bandwidth portion of the TRP within the starting RB of the BWP, This is for indexes. k The frequency offset between TRP frequency hopping intervals, in RB units, and It is the number of Physical Resource Blocks (PRBs) of size BWP activated on the uplink.

[0312] Example 126 includes the method according to Example 121, wherein the TDM-based PUSCH repetitions targeting different TRPs are configured with different frequency allocation sizes, the index of the target TRP... k Depend on Given, and the frequency hopping pattern between repetitions is predefined by the following formula: , in, Is the index as n The PUSCH repeats the starting resource block RB. This is for indexes. k The uplink bandwidth portion of the TRP within the starting RB of the BWP, This is for indexes. k The frequency offset between TRP frequency hopping intervals, in RB units, and It is the number of Physical Resource Blocks (PRBs) of size BWP activated on the uplink.

[0313] Example 127 includes the method according to Example 121, wherein the TDM-based PUSCH repetitions targeting different TRPs are configured with different frequency allocation sizes, the index of the target TRP... k Depend on Given, and the frequency hopping pattern between repetitions is predefined by the following formula: , in, Is the index as n The PUSCH repeats the starting resource block RB. This is for indexes. k The uplink bandwidth portion of the TRP within the starting RB of the BWP, This is for indexes. k The frequency offset between TRP frequency hopping intervals, in RB units, and It is the number of Physical Resource Blocks (PRBs) of size BWP activated on the uplink.

[0314] Example 128 includes the method according to any one of Examples 125 to 127, wherein the TDM-based PUSCH repeats targeting the same TRP are configured with the same frequency allocation size.

[0315] Example 129 includes a computer-readable medium having instructions stored thereon, wherein the instructions, when executed by processing circuitry of a user equipment (UE), cause the processing circuitry to perform the method as described in any one of Examples 120 to 128.

[0316] Example 130 includes an apparatus for a user equipment (UE) including means for performing the method as described in any one of Examples 120 to 128.

[0317] While certain embodiments have been illustrated and described herein for purposes of description, various alternative and / or equivalent embodiments or implementations devised to achieve the same purpose may replace the illustrated and described embodiments without departing from the scope of this disclosure. This application is intended to cover any adaptations or variations of the embodiments discussed herein. Therefore, it is readily understood that the embodiments described herein are limited only by the appended claims and their equivalents.

Claims

1. A method for wireless communication, comprising: At the user equipment (UE), a Media Access Control-Control Element (MAC-CE) is received. This MAC-CE is used to activate / deactivate the spatial relationships of the Physical Uplink Control Channel (PUCCH). The MAC-CE includes: The first group of eight bytes includes an identifier for the first PUCCH resource, a first spatial relationship information identifier for the first PUCCH resource, and a third spatial relationship information identifier for the first PUCCH resource; and The second set of eight bytes includes a fourth and a fifth eight-byte group. The fourth eight-byte group contains an identifier for the second PUCCH resource, and the fifth eight-byte group contains a third spatial relationship information identifier for the second PUCCH resource. The second set of eight bytes also includes an indicator bit to indicate whether one or two spatial relationships should be activated for the second PUCCH resource. At the UE, the spatial relationships indicated by the first spatial relationship information identifier and the second spatial relationship information identifier are activated for the first PUCCH resource, and the spatial relationships indicated by the third spatial relationship information identifier are activated for the second PUCCH resource.

2. The method according to claim 1, wherein, The second group of eight bytes also includes a sixth eight-byte, which contains the fourth spatial relation information identifier of the second PUCCH resource.

3. The method according to claim 1, wherein, If the indicator bit indicates that a spatial relationship will be activated for the second PUCCH resource, then the second set of eight bytes, apart from the fifth eight-bit byte, does not include any other eight-bit bytes containing the spatial relationship information identifier of the second PUCCH resource.

4. The method according to claim 1, wherein, The identifier of the first PUCCH resource is 7 bits long, and the identifiers of the first spatial relationship information and the second spatial relationship information are both 6 bits long.

5. The method according to claim 1, wherein, The MAC-CE further includes: a field indicating the identity of the serving cell to which the MAC-CE is applied, and a field indicating the uplink (UL) bandwidth portion to which the MAC-CE is applied.

6. An apparatus for a user equipment (UE), comprising a radio frequency (RF) interface circuit and processing circuitry coupled to said RF interface circuitry. in, The RF interface circuit is configured to receive a Medium Access Control-Control Element (MAC-CE) for activating / deactivating the spatial relationships of the Physical Uplink Control Channel (PUCCH). The MAC-CE includes: The first group of eight bytes contains an identifier for the first PUCCH resource, a first spatial relationship information identifier for the first PUCCH resource, and a third spatial relationship information identifier for the first PUCCH resource. The second set of eight bytes includes a fourth and a fifth eight-byte group. The fourth eight-byte group contains an identifier for the second PUCCH resource, and the fifth eight-byte group contains a third spatial relationship information identifier for the second PUCCH resource. The second set of eight bytes also includes an indicator bit to indicate whether one or two spatial relationships should be activated for the second PUCCH resource. The processing circuit is configured to activate the spatial relationships indicated by the first spatial relationship information identifier and the second spatial relationship information identifier for the first PUCCH resource, and to activate the spatial relationships indicated by the third spatial relationship information identifier for the second PUCCH resource.

7. The apparatus according to claim 6, wherein, The second group of eight bytes also includes a sixth eight-byte, which contains the fourth spatial relation information identifier of the second PUCCH resource.

8. The apparatus according to claim 6, wherein, If the indicator bit indicates that a spatial relationship will be activated for the second PUCCH resource, then the second set of eight bytes, apart from the fifth eight-bit byte, does not include any other eight-bit bytes containing the spatial relationship information identifier of the second PUCCH resource.

9. The apparatus according to claim 6, wherein, The identifier of the first PUCCH resource is 7 bits long, and the identifiers of the first spatial relationship information and the second spatial relationship information are both 6 bits long.

10. The apparatus according to claim 6, wherein, The MAC-CE further includes: a field indicating the identity of the serving cell to which the MAC-CE is applied, and a field indicating the uplink (UL) bandwidth portion to which the MAC-CE is applied.

11. A non-transitory machine-readable storage medium having instructions stored thereon, the instructions causing the user equipment (UE) to perform the method according to any one of claims 1 to 5 when executed by a processing circuitry.

Images