Transmission method, terminal and network side device

Abstract

This application relates to the field of communication technology and discloses a transmission method, terminal, and network-side equipment to solve the problem of PUCCH transmission reliability in multi-TRP joint transmission scenarios. The method includes: sending N repeatedly transmitted Physical Uplink Control Channels (PUCCHs); where N is an integer greater than or equal to 2. In this way, the terminal can send multiple repeatedly transmitted PUCCHs to multiple TRPs, which can reduce information delays caused by some TRPs in poor transmission environments and improve the reliability of repeated transmissions.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of communication, and particularly relates to a transmission method, a terminal and a network side device. BACKGROUND

[0002] With the rapid development of wireless communication technology, the fifth generation (5th Generation, 5G) wireless communication technology has gradually been applied in various fields. The 5G wireless communication technology supports higher speed, larger bandwidth access capability, lower latency and high reliability information interaction, etc.

[0003] High reliability and low latency communication is an important communication type in 5G. URLLC is a communication service with high requirements for latency and reliability. In order to support URLLC service, Multi-TRP (Multi-Transmission Reception Point) joint transmission is gradually rising as a new information transmission method. In the above joint transmission scenario, the terminal can connect with multiple TRPs at the same time, so as to transmit data through multiple TRPs at the same time, and when the terminal receives data sent by different TRPs, the terminal can combine the obtained data to obtain the final data.

[0004] However, how to improve the reliability of data transmission in the multi-TRP joint scenario has become a problem to be solved. SUMMARY

[0005] The embodiments of the present application provide a transmission method, a terminal and a network side device, which improve the transmission reliability of PUCCH in the multi-TRP joint transmission scenario by repeatedly transmitting PUCCH (Physical Uplink Control Channel).

[0006] In order to achieve the above purpose, the present application is implemented as follows:

[0007] In a first aspect, the embodiments of the present application provide a transmission method for a terminal, which comprises the following steps:

[0008] transmitting N physical uplink control channels (PUCCH) for repeated transmission; N is an integer greater than or equal to 2.

[0009] Optionally, before transmitting the N PUCCHs for repeated transmission, the method further comprises the following steps:

[0010] Receiving M downlink control information DCIs, each of the M downlink control information DCIs including first configuration information corresponding to part of the N physical uplink control channels PUCCHs, and a control resource set CORESET pool index configured by a control resource set CORESET carrying the M downlink control information DCIs being different, the M being an integer greater than or equal to 2.

[0011] Optionally, before transmitting the N physical uplink control channels PUCCHs in the repetition transmission, the method further includes:

[0012] Receiving M downlink control information DCIs, each of the M downlink control information DCIs including first configuration information corresponding to part of the N physical uplink control channels PUCCHs, the part of the N physical uplink control channels PUCCHs corresponding to a same reception transmission reception point TRP, the M being an integer greater than or equal to 2.

[0013] Optionally, the first configuration information includes time domain configuration information, and the N physical uplink control channels PUCCHs are configured to be transmitted continuously in a time domain corresponding to a same index parameter, or adjacent physical uplink control channels PUCCHs in the time domain correspond to different index parameters, the index parameter being a control resource set CORESET pool index configured by a control resource set CORESET in which downlink control information DCI scheduling the physical uplink control channel PUCCH is located.

[0014] Optionally, according to the control resource set CORESET pool index parameter configured by the control resource set CORESET in which the downlink control information DCI scheduling the physical uplink control channel PUCCH is located, a spatial relation of the physical uplink control channel PUCCH is predefined as being determined according to a quasi co-location QCL assumption or a configured quasi co-location type D (QCL-TypeD) of one control resource set CORESET of the control resource sets CORESET configured with the same index parameter.

[0015] Or

[0016] According to the control resource set CORESET pool index parameter configured by the control resource set CORESET in which the downlink control information DCI scheduling the physical uplink control channel PUCCH is located, a path loss reference signal of the physical uplink control channel PUCCH is predefined as being determined according to a reference signal corresponding to a quasi co-location QCL assumption or a configured quasi co-location type D (QCL-TypeD) of one control resource set CORESET of the control resource sets CORESET configured with the same index parameter.

[0017] Optionally, one of the control resource sets CORESETs configured with the same index parameter is identified as the minimum control resource set CORESET among the control resource sets CORESETs configured with the same index parameter.

[0018] Optionally, the first configuration information includes a TPC command, used to determine a transmission power of a physical uplink control channel PUCCH scheduled by the downlink control information DCI.

[0019] Optionally, before the transmitting the N physical uplink control channels PUCCHs, the method further includes:

[0020] receiving 1 medium access control control element MAC CE; the medium access control control element MAC CE carries L second configuration information, each second configuration information is used to indicate a spatial relation parameter of a part of the N physical uplink control channels PUCCHs, and L is an integer greater than or equal to 2.

[0021] Optionally, the N physical uplink control channels PUCCHs are configured to be transmitted continuously in the time domain corresponding to the same second configuration information, or the second configuration information corresponding to adjacent physical uplink control channels PUCCHs is different in the time domain.

[0022] In a second aspect, an embodiment of the present application also provides another transmission method, applied to a network side device, the transmission method comprising:

[0023] receiving a part of the N physical uplink control channels PUCCHs; and N is an integer greater than or equal to 2.

[0024] Optionally, before receiving the part of the N physical uplink control channels PUCCHs, the method further includes:

[0025] transmitting downlink control information DCI, the DCI including first configuration information corresponding to a part of the N PUCCHs, and control resource set CORESET pool indexes of M control resource sets CORESETs carrying the M DCIs are different, each of the M DCIs corresponding to a part of the N PUCCHs, and M is an integer greater than or equal to 2.

[0026] Optionally, before receiving the part of the N physical uplink control channels PUCCHs, the method further includes:

[0027] transmitting downlink control information DCI, the DCI including first configuration information corresponding to part of the N PUCCHs, the part of the PUCCHs corresponding to the same receiving transmission receiving point TRP, each of the M DCIs corresponding to part of the N PUCCHs, the M being an integer greater than or equal to 2.

[0028] Optionally, the first configuration information includes time domain configuration information, the M DCIs being used to configure the N PUCCHs to: continuously transmit PUCCHs corresponding to the same index parameter in the time domain, or PUCCHs corresponding to different index parameters being adjacent in the time domain, the index parameter being a CORESET pool index configured by a control resource set CORESET in which the DCI scheduling the PUCCH is located.

[0029] Optionally, according to a control resource set CORESET pool index parameter configured by a control resource set CORESET in which downlink control information DCI scheduling the physical uplink control channel PUCCH is located, a spatial relationship of the physical uplink control channel PUCCH is predefined as: being determined according to a quasi-co-location QCL assumption or a quasi-co-location type D (QCL-TypeD) configured by one of the control resource sets CORESETs configured with the same index parameter.

[0030] Or

[0031] According to a control resource set CORESET pool index parameter configured by a control resource set CORESET in which downlink control information DCI scheduling the physical uplink control channel PUCCH is located, a path loss reference signal of the physical uplink control channel PUCCH is predefined as: being determined according to a reference signal corresponding to a quasi-co-location QCL assumption or a reference signal corresponding to a quasi-co-location type D (QCL-TypeD) configured by one of the control resource sets CORESETs configured with the same index parameter.

[0032] Optionally, the one of the control resource sets CORESETs configured with the same index parameter is the control resource set CORESET identified as the smallest among the control resource sets CORESETs configured with the same index parameter.

[0033] Optionally, the first configuration information includes a TPC command used to configure a transmission power of the physical uplink control channel PUCCH scheduled by the downlink control information DCI.

[0034] Optionally, before receiving the N physical uplink control channels PUCCHs repeatedly transmitted, the method further includes:

[0035] transmitting 1 medium access control control element (MAC CE); the MAC CE carries L second configuration information, each of which is used to configure a spatial relation parameter of part of the N physical uplink control channels (PUCCHs), and L is an integer greater than or equal to 2.

[0036] Optionally, the MAC CE is used to configure the N PUCCHs to be transmitted consecutively in the time domain corresponding to the same second configuration information, or the second configuration information corresponding to adjacent PUCCHs is different in the time domain.

[0037] In a third aspect, an embodiment of the present application also provides a terminal, which comprises a first transceiver, configured to:

[0038] transmit N PUCCHs in repeated transmission; N is an integer greater than or equal to 2.

[0039] Optionally, before transmitting the N PUCCHs in repeated transmission, the first transceiver is further configured to:

[0040] receive M DCIs, each of which includes first configuration information corresponding to part of the N PUCCHs, and the control resource set (CORESET) pool index configured by the CORESET carrying the M DCIs is different, and M is an integer greater than or equal to 2.

[0041] Optionally, according to the control resource set (CORESET) pool index parameter of the CORESET in which the DCI scheduling the PUCCH is located, the spatial relation of the PUCCH is predefined as being determined according to the quasi co-location (QCL) assumption or the configured QCL-TypeD of one of the CORESETs configured with the same index parameter.

[0042] or

[0043] According to a control resource set CORESET pool index parameter configured by a downlink control information DCI scheduling the physical uplink control channel PUCCH, a path loss reference signal of the physical uplink control channel PUCCH is predefined as a reference signal corresponding to a quasi co-location QCL assumption of one of the control resource sets CORESET configured with the same index parameter or a reference signal corresponding to a configured QCL-TypeD.

[0044] Optionally, the first configuration information includes a TPC command, used to determine a transmission power of the physical uplink control channel PUCCH scheduled by the downlink control information DCI.

[0045] Optionally, before the first transceiver transmits the N physical uplink control channels PUCCH in repeated transmission, the first transceiver is further configured to:

[0046] receive 1 medium access control control element MAC CE; the medium access control control element MAC CE carries L second configuration information, each second configuration information is used to indicate a spatial relationship parameter of part of the N physical uplink control channels PUCCH, and L is an integer greater than or equal to 2.

[0047] In a fourth aspect, the embodiments of the present application further provide a network side device, comprising a second transceiver, the second transceiver is configured to:

[0048] receive part of the N physical uplink control channels PUCCH in repeated transmission; N is an integer greater than or equal to 2.

[0049] Optionally, the second transceiver is further configured to:

[0050] transmit downlink control information DCI, the DCI includes first configuration information corresponding to part of the N PUCCH, and control resource sets CORESETs configured by control resource sets CORESETs carrying M DCIs are different, each of the M DCIs corresponds to part of the N PUCCH, and M is an integer greater than or equal to 2.

[0051] Optionally, according to a control resource set (CORESET) pool index parameter configured by a control resource set (CORESET) in which downlink control information (DCI) scheduling the physical uplink control channel (PUCCH) is located, a spatial relation of the physical uplink control channel (PUCCH) is predefined as being determined according to a quasi co-location (QCL) assumption or a configured quasi co-location type D (QCL-TypeD) of one control resource set (CORESET) of the control resource sets (CORESETs) configured with the same index parameter.

[0052] Or

[0053] According to a control resource set (CORESET) pool index parameter configured by a control resource set (CORESET) in which downlink control information (DCI) scheduling the physical uplink control channel (PUCCH) is located, a path loss reference signal of the physical uplink control channel (PUCCH) is predefined as being determined according to a reference signal corresponding to a quasi co-location (QCL) assumption or a configured quasi co-location type D (QCL-TypeD) of one control resource set (CORESET) of the control resource sets (CORESETs) configured with the same index parameter.

[0054] Optionally, the first configuration information includes a TPC command, used to configure a transmission power of the physical uplink control channel (PUCCH) scheduled by the downlink control information (DCI).

[0055] Optionally, the second transceiver is further configured to:

[0056] transmit 1 medium access control (MAC) control element (CE); the medium access control (MAC) control element (CE) carries L second configuration information, each second configuration information being used to configure a spatial relation parameter of part of the N physical uplink control channels (PUCCHs), and L is an integer greater than or equal to 2.

[0057] In a fifth aspect, an embodiment of the present application provides a terminal, which comprises a memory, a processor, and a computer program stored in the memory and executable on the processor; when the processor executes the program, the steps of the transmission method in the first aspect are implemented.

[0058] In a sixth aspect, an embodiment of the present application provides a network side device, which comprises a memory, a processor, and a computer program stored in the memory and executable on the processor; when the processor executes the program, the steps of the transmission method in the second aspect are implemented.

[0059] In a seventh aspect, the embodiments of the present application provide a computer readable storage medium, which stores a computer program. The computer program is executed by a processor to implement the steps of the transmission method according to the first aspect or the second aspect.

[0060] The above technical solutions of the present application have at least the following beneficial effects:

[0061] The terminal can send multiple PUCCHs with repeated transmissions to multiple TRPs, which can reduce the information delay caused by poor transmission environment of some TRPs, and improve the reliability of transmission. BRIEF DESCRIPTION OF DRAWINGS

[0062] Figure 1 is a flowchart of the transmission method provided by the embodiments of the present application on the terminal side;

[0063] Figure 2 is a schematic diagram of information transmission provided by the embodiments of the present application;

[0064] Figures 3-4 is a schematic diagram of the configuration mode of PUCCH in the time domain provided by the embodiments of the present application;

[0065] Figure 5 is a diagram of information contained in the control unit of the medium access control provided by the embodiments of the present application;

[0066] Figure 6 is a schematic diagram of the configuration mode of PUCCH in the time domain provided by the embodiments of the present application;

[0067] Figure 7 is a combination diagram of the DCI and spatial relationship corresponding to the PUCCH provided by the embodiments of the present application;

[0068] Figure 8 is one of the structural diagrams of the terminal provided by the embodiments of the present application;

[0069] Figure 9 is one of the structural diagrams of the network side device provided by the embodiments of the present application;

[0070] Figure 10 is the second structural diagram of the terminal provided by the embodiments of the present application;

[0071] Figure 11 is the second structural diagram of the network side device provided by the embodiments of the present application. DETAILED DESCRIPTION

[0072] In order to make the technical problems, technical solutions and advantages of the present application clearer, specific embodiments will be described in detail below with reference to the accompanying drawings.

[0073] Reference Figure 1 , Figure 1This is a schematic flowchart illustrating a transmission method provided in an embodiment of the present invention. Figure 1 As shown, a transmission method applied to a terminal includes the following steps:

[0074] Step 101: Send N PUCCHs that are transmitted repeatedly; where N is an integer greater than or equal to 2.

[0075] In this embodiment, the terminal can send multiple repeatedly transmitted PUCCHs to multiple TRPs (Transmission Reception Points) involved in joint transmission. The N repeatedly transmitted PUCCHs can be understood as N PUCCHs carrying the same UCI (Uplink Control Information). Depending on the format, the UCI information may include HARQ-ACK (Hybrid Automatic Repeat Request Acknowledgement), CSI (Channel State Information), SR (Scheduling Request), etc.

[0076] like Figure 2 As shown, the terminal establishes connections with two TRPs involved in the joint transmission. The terminal can receive downlink control information from TRP11 and TRP12 respectively. The terminal can also simultaneously send PUCCHs to both TRPs based on the received downlink control information, and the UCI carried in both PUCCHs is identical. Both TRPs can receive the PUCCHs sent by the terminal. The two TRPs shown in the figure are merely an example; in practical applications, the number of TRPs can be greater than two.

[0077] The reliability of repeated transmissions can be improved by repeatedly transmitting PUCCH to multiple TRPs in a joint transmission.

[0078] From the perspective of network-side devices, the method of this embodiment includes:

[0079] Receive a portion of N repeatedly transmitted PUCCHs; where N is an integer greater than or equal to 2.

[0080] In practical applications, the channel environment and spatial relationship parameters of multiple TRPs undergoing repeated transmissions often differ. In such cases, if the terminal uses the same configuration for PUCCHs sent to different TRPs during repeated transmissions, a satisfactory transmission effect cannot be achieved. To further improve the reliability of repeated PUCCH transmissions, this invention proposes the following methods.

[0081] The first way is to improve the reliability of transmission from the DCI (Downlink Control Information) scheduling PUCCH. The description is as follows.

[0082] Before transmitting the N PUCCHs of repeated transmission, the method further comprises:

[0083] Receiving M DCIs, each DCI including first configuration information corresponding to part of the N PUCCHs, the CORESET pool index configured by the CORESET carrying the M DCIs being different, and the M being an integer greater than or equal to 2.

[0084] For the network side device, such as the TRP, the method of the embodiment of the application further comprises, before receiving the N PUCCHs of repeated transmission:

[0085] Before receiving part of the N PUCCHs of repeated transmission, the method further comprises:

[0086] Transmitting DCIs, each DCI including first configuration information corresponding to part of the N PUCCHs, the CORESET pool index configured by the CORESET carrying the M DCIs being different, each of the M DCIs corresponding to part of the N PUCCHs, and the M being an integer greater than or equal to 2.

[0087] That is, in the embodiment of the application, the PUCCHs corresponding to different TRPs are scheduled by different DCIs, and the PUCCHs corresponding to the same TRP can be scheduled by the same DCI. The M DCIs can be transmitted by one of the TRPs, or by one of the TRPs or multiple TRPs of joint transmission.

[0088] In this embodiment, the CORESET pool index configured by the CORESET of the DCI can be used to determine the TRP corresponding to the DCI. For example, TRP0 is associated with coresetPoolIndex-r16=0, and TRP1 is associated with coresetPoolIndex-r16=1. Based on the above-mentioned associated resource pool index information, the TRP corresponding to the DCI can be determined. Each DCI can schedule at least one PUCCH in time sequence, and the TRP corresponding to the PUCCH, i.e., the sender of the DCI, can be determined in the above-mentioned manner.

[0089] Since the CORESET pool index configured for each DCI is different, the corresponding TRP determined by the CORESET pool index is also different. Each DCI is used to indicate the first configuration information of the PUCCH sent to the corresponding TRP.

[0090] by Figure 2 The example shown illustrates information transmission between a terminal and two TRPs in a joint transmission. The terminal receives two DCIs from TRP11 and TRP12. The two DCIs have different CORESET pool indices configured for their CORESETs. Based on these CORESET pool indices, the two DCIs can be identified as corresponding to TRP11 and TRP12, respectively. During information transmission, the terminal can obtain the TRP11 corresponding to the DCI and use it to schedule the PUCCH sent to TRP11; it can also obtain the TRP12 corresponding to the DCI and use it to schedule the PUCCH sent to TRP12.

[0091] Since PUCCHs on different TRPs are scheduled by different DCIs, transmission resources corresponding to the TRP can be configured for the DCI based on the TRP's characteristics, such as the network environment. For example, PUCCHs on TRPs with better channel quality can be allocated relatively fewer resources, while PUCCHs on TRPs with poorer channel quality can be allocated relatively more resources. This allows for more rational scheduling of PUCCHs on TRPs, improving scheduling flexibility and further enhancing the reliability of PUCCH transmission.

[0092] Optionally, the first configuration information includes time-domain configuration information, which is used to configure the N PUCCHs in the following two ways:

[0093] The first type is continuous transmission of PUCCH corresponding to the same index parameters in the time domain.

[0094] This method, also known as sequential mapping, determines the time-domain position of the first PUCCH transmission and the number of PUCCH retransmissions in the DCI-scheduled PUCCH based on the PDSCH-to-HARQ (Hybrid Automatic Repeat reQuest) feedback timing indicator (PDSCH to HARQ timer). During time-domain allocation, if multiple PUCCHs correspond to the same index parameter, the corresponding TRPs can be determined based on this index parameter, allowing multiple PUCCHs with the same TRP to be transmitted consecutively in the time domain.

[0095] The index parameter is the CORESET pool index configured in the CORESET where the DCI that schedules the PUCCH is located.

[0096] The second type is where adjacent PUCCHs in the time domain have different index parameters.

[0097] This method can also be called cyclic mapping. That is, the time slot for the first PUCCH transmission is determined based on the PDSCH-to-HARQ_feedbacktiming indicator in the DCI, and a PUCCH transmission is performed every other time slot, repeating the transmission according to the number of time slots. When allocating in the time domain, if multiple PUCCHs correspond to different index parameters, then the TRP determined by those index parameters will also be different. Therefore, multiple PUCCHs corresponding to different TRPs can be distributed in the time domain according to the time slot interval.

[0098] From the perspective of the network-side device, the first configuration information includes time-domain configuration information, and the M DCIs are used to configure the N PUCCHs in the following two ways:

[0099] The first type is continuous transmission of PUCCH corresponding to the same index parameters in the time domain;

[0100] The second type is where adjacent PUCCHs in the time domain have different index parameters;

[0101] The index parameter is the CORESET pool index configured in the control resource set CORESET where the DCI that schedules the PUCCH is located.

[0102] In this embodiment, the time-domain location of PUCCH transmission can be determined by counting the PDSCH (Physical downlink shared channel) scheduled by DCI. The number of PUCCH repetitions (nrofSlots) depends on the RRC (Radio Resource Control) configuration. Figure 3 As shown, during the four repeated transmissions by the terminal, the parameters of the PUCCH are the same for each repeated transmission, and the RRC is configured to specify the number of times the PUCCH repeats.

[0103] To further understand the two configuration methods mentioned above, examples are provided below.

[0104] For example, such as Figure 4As shown, the base station sends downlink control information to the terminal. The PDSCH scheduled by the downlink control information can include the PDSCH time slot and the interval k1 between the uplink control channel and the downlink control channel. After configuring the time-domain configuration information according to DCI-0 and DCI-1, if the TRP corresponding to PUCCH R0 and PUCCH R2 is different from the TRP corresponding to PUCCH R1 and PUCCH R3, then PUCCH R0 and PUCCH R2 can be distributed alternately in the time domain, and PUCCH R1 and PUCCH R3 can be distributed alternately in the time domain. If the TRP corresponding to PUCCH R0 and PUCCH R1 is the same, and the TRP corresponding to PUCCH R2 and PUCCH R3 is the same, then PUCCH R0 and PUCCH R1 can be distributed continuously in the time domain, and PUCCH R2 and PUCCH R3 can be distributed continuously in the time domain.

[0105] Both configuration methods described above enable the orderly scheduling of PUCCHs on different TRPs, thereby improving the reliability of repeated transmissions.

[0106] In practical applications, before sending the N repetitive PUCCH transmissions, the following steps are also included:

[0107] Receive M DCIs, each DCI including first configuration information corresponding to a portion of the N PUCCHs, wherein the TRPs corresponding to the portion of the PUCCHs are the same, M is an integer greater than or equal to 2, and N is an integer greater than or equal to 2.

[0108] For network-side devices, such as TRP, the method of this embodiment further includes, before receiving a portion of the N repeatedly transmitted Physical Uplink Control Channels (PUCCHs), the following:

[0109] Send a DCI, wherein the DCI includes first configuration information corresponding to a portion of the N PUCCHs, the TRPs corresponding to the portion of the PUCCHs are the same, and each of the M DCIs corresponds to a portion of the N PUCCHs, wherein M is an integer greater than or equal to 2.

[0110] In this implementation, N PUCCHs can be grouped into M PUCCH groups, with each PUCCH group having the same receiving TRP. This allows the same DCI to be used to schedule the corresponding PUCCH group for each TRP, improving information transmission efficiency. Furthermore, for multiple TRPs transmitting repeatedly, since PUCCHs can contain different resources, different DCIs can be used to schedule the PUCCHs of different TRPs, ensuring that different TRPs acquire different resources and improving the flexibility of resource scheduling.

[0111] Furthermore, the first configuration information includes time-domain configuration information, used to configure the N PUCCHs to be distributed sequentially in the time domain as PUCCH groups, or to configure the N PUCCHs such that adjacent PUCCHs in the time domain belong to different groups. That is, the PUCCH groups are distributed sequentially in the time domain, or the PUCCH groups are distributed at intervals in the time domain.

[0112] Method 2 improves the reliability of repeated transmissions from the perspective of PUCCH spatial relationship configuration, as explained below.

[0113] Before sending the N PUCCHs that are repeatedly transmitted, the method further includes:

[0114] Receive one MAC CE (Media Access Control Control Element); the MAC CE carries L second configuration information, each second configuration information is used to indicate the spatial relationship parameters of some PUCCHs among the N PUCCHs, where L is an integer greater than or equal to 2.

[0115] For network-side devices, such as TRP, the method of this embodiment of the invention further includes, before sending the N repeatedly transmitted Physical Uplink Control Channels (PUCCHs):

[0116] Send one MAC CE; the MAC CE carries L second configuration information, each second configuration information is used to configure the spatial relationship parameters of some PUCCHs in the N PUCCHs, where L is an integer greater than or equal to 2.

[0117] In this embodiment, a MAC CE can be used to activate multiple spatial relationship parameters of PUCCH, wherein the spatial relationship parameters may include parameters for controlling beam direction and power control parameters for power control, etc.

[0118] Furthermore, the N PUCCHs activated by MAC CE can also be configured in the time domain in the following two ways:

[0119] The first type is continuous transmission of PUCCH in the time domain, corresponding to the same second configuration information.

[0120] This method can also be called sequential mapping, which means that the spatial relationship parameters that are activated first and the spatial relationship parameters that are activated later are configured in sequence according to the order. Specifically, the spatial relationship parameters that are activated first and the spatial relationship parameters that are activated later can be determined based on the number of times PUCCH is repeated in the RRC or DCI configuration.

[0121] The second type is in the time domain, where adjacent PUCCHs have different second configuration information.

[0122] This method can also be called cyclic mapping, which means that the spatial relationship parameters that are activated sequentially can be configured at intervals. For example, the spatial relationship parameters activated by odd-numbered MAC CE mappings can be configured alternately with those activated by even-numbered MAC CE mappings.

[0123] From the perspective of the network-side device, the MAC CE is used to configure the N PUCCHs as follows: in the time domain, PUCCHs corresponding to the same second configuration information are transmitted continuously; or, in the time domain, adjacent PUCCHs correspond to different second configuration information.

[0124] In specific embodiments of the present invention, PUCCHs corresponding to different TRPs correspond to different spatial relationship configurations, while PUCCHs corresponding to the same TRP correspond to the same spatial relationship configuration, thereby improving the reliability of information transmission.

[0125] To facilitate understanding of the above embodiments, examples are provided below in conjunction with the accompanying drawings.

[0126] See Figure 5 , Figure 5 This represents the field information table contained in a MAC CE that schedules a PUCCH. This MAC CE is used to schedule PUCCHs for two TRPs (using two TRPs as an example). The field information table includes four rows of fields, each with eight bits. The first row includes a reserved bit R, the Serving Cell ID, and the Bandwidth ID (BWP ID). The second row includes the Physical Uplink Control Channel Resource ID (PUCCH resource ID), with each PUCCH resource ID corresponding to two spatial relationship information IDs for a set of PUCCHs. The third row includes a field for carrying the Spatial Relation Info ID, as well as a reserved bit R and a field C. The fourth row includes two reserved bits R and a field for carrying the spatial relationship information ID.

[0127] Using the spatial relationship information carried by the MAC CE mentioned above, the spatial relationship information of the PUCCH can be configured. See also Figure 6 , Figure 6 This indicates the configuration method of PUCCH in the time domain.

[0128] As shown in the time slot diagram corresponding to the first row of PUCCH, when the spatial relationship parameters of the PUCCH corresponding to slot 0 R0 and slot 1 R1 are the same, the PUCCH corresponding to slot 0 R0 and slot 1 R1 can be transmitted continuously in the time domain; similarly, when the spatial relationship parameters of the PUCCH corresponding to slot 2 R2 and slot 3 R3 are the same, the PUCCH corresponding to slot 2 R2 and slot 3 R3 can also be transmitted continuously in the time domain. After configuration using the above method, the PUCCH corresponding to slot 0 R0 and slot 1 R1 can be configured with the same set of spatial relationship parameters and correspond to TRP11; the PUCCH corresponding to slot 2 R2 and slot 3 R3 can be configured with another set of spatial relationship parameters and correspond to TRP12.

[0129] As shown in the time slot diagram corresponding to the second row of PUCCH, when the spatial relationship parameters of the PUCCH corresponding to slot 0 R0 and slot 1 R1 are different, the PUCCH corresponding to slot 0 R0 and slot 1 R1 can be transmitted intermittently; when the spatial relationship parameters of the PUCCH corresponding to slot 2 R2 and slot 3 R3 are different, the PUCCH corresponding to slot 2 R2 and slot 3 R3 can also be transmitted intermittently in the time domain. After configuration using the above method, the PUCCH corresponding to slot 0 R0 and slot 2 R2 can be configured with the same set of spatial relationship parameters and can correspond to TRP11; the PUCCH corresponding to slot 1 R1 and slot 3 R3 can be configured with another set of spatial relationship parameters and correspond to TRP12.

[0130] When considering both the DCI and spatial relation parameters corresponding to a PUCCH, different PUCCHs can correspond to different DCIs and spatial relation parameters. Taking the scheduling of four repeated transmissions of PUCCHs using two DCIs (DCI0 and DCI1) and two sets of spatial relation parameters (spatial relation 0 and spatial relation 1) as an example, the DCIs and spatial relation parameters corresponding to PUCCH0, PUCCH1, PUCCH2, and PUCCH3 can be arranged as follows: Figure 7 The method shown yields multiple combinations.Figure 7 The examples provided are just a few of the possible combinations. Many more combinations can be obtained by following the above method, but they will not be listed in detail here.

[0131] In combination one, PUCCH0 and PUCCH2 have the same DCI and spatial relationship, as do PUCCH1 and PUCCH3. This combination method allows for time-interval transmission of PUCCHs. In combination four, PUCCH0 and PUCCH1 have the same DCI and spatial relationship, as do PUCCH2 and PUCCH3. This combination method allows for continuous time-domain transmission of PUCCHs. Specific transmission methods can be found in the descriptions of the above embodiments and will not be repeated here.

[0132] In practical applications, this implementation method may further include:

[0133] Before sending the N repetitive PUCCHs to the N TRPs of the joint transmission, the method further includes:

[0134] Receive one MAC CE; the MAC CE carries L sets of second configuration information, each set of second configuration information corresponds to a PUCCH group composed of some PUCCHs among the N PUCCHs, and each set of second configuration information includes at least one of spatial configuration information and power control parameters, where L is an integer greater than or equal to 2.

[0135] Furthermore, the PUCCH group can also be configured in the following ways:

[0136] The first type: In the time domain, adjacent PUCCHs belong to different PUCCH groups;

[0137] The second type: In the time domain, the N PUCCHs are distributed sequentially in groups;

[0138] The third type: L is equal to N, and the receiving TRP of PUCCH in each PUCCH group is the same.

[0139] In this embodiment of the invention, the spatial relationship parameters of the PUCCH are determined by the configuration information carried by the MAC CE. The terminal can flexibly configure the spatial relationship parameters according to the TRP corresponding to the PUCCH. This allows PUCCHs sent to the same TRP to use the same set of configuration information, while PUCCHs sent to different TRPs can use different configuration information. The information can be flexibly configured according to parameters such as the transmission environment of the TRP, thereby improving the reliability of repeated transmissions.

[0140] When not using MAC CE configuration, the terminal can configure the default space relationship for PUCCH in the following two ways:

[0141] The first method is based on the CORESET pool index parameters configured in the CORESET where the DCI of the PUCCH is located. The spatial relationship of the PUCCH is predefined as follows: it is determined based on the QCL (Quasi Co-Location) assumption of one of the CORESETs with the same index parameters or the configured quasi-co-location type D (QCL-Type D).

[0142] The second method is based on the CORESET pool index parameters configured in the CORESET where the DCI of the PUCCH is located. The path loss reference signal of the PUCCH is predefined as: the reference signal corresponding to the QCL assumption of one of the CORESETs with the same index parameters or the reference signal corresponding to the configured QCL-TypeD.

[0143] Among them, one of the CORESETs configured with the same index parameters is the CORESET with the smallest identifier among the CORESETs configured with the same index parameters.

[0144] From the perspective of network-side devices, the default spatial relationship can be configured for PUCCH in the following ways:

[0145] The first method is to predefine the spatial relationship of the Physical Uplink Control Channel (PUCCH) based on the control resource set CORESET pool index parameters configured in the control resource set CORESET where the downlink control information DCI of the Physical Uplink Control Channel (PUCCH) is located: based on the quasi-co-location QCL assumption of one of the control resource sets CORESET with the same index parameters or the configured quasi-co-location type D (QCL-Type D) configuration.

[0146] The second method is to predefine the path loss reference signal of the Physical Uplink Control Channel (PUCCH) based on the control resource set CORESET pool index parameters configured in the control resource set CORESET where the downlink control information DCI of the Physical Uplink Control Channel (PUCCH) is located: the reference signal corresponding to the quasi-co-location QCL assumption of one of the control resource sets CORESET with the same index parameters or the reference signal corresponding to the configured quasi-co-location type D (QCL-Type D).

[0147] Wherein, one of the control resource sets CORESET configured with the same index parameters is the control resource set CORESET with the smallest identifier among the control resource sets CORESET configured with the same index parameters.

[0148] In this embodiment, the parameters can be configured sequentially or cyclically according to the TRP corresponding to the PUCCH. For example, in the earlier transmitted PUCCHs, the predefined spatial relationship and predefined path loss reference signal of the PUCCH are associated with the reference signal of the QCL-TypeD or QCL assumption of the smallest CORESET identified in coreset Pool Index-r16=0. In the later transmitted PUCCHs, the predefined spatial relationship and predefined path loss reference signal of the PUCCH are associated with the reference signal of the QCL-TypeD or QCL assumption of the smallest CORESET identified in coreset Pool Index-r16=1. Alternatively, for the predefined spatial relationship and predefined path loss reference signal of the PUCCH, the PUCCHs transmitted in odd-numbered transmissions are mapped to the reference signal of the QCL-TypeD or QCL assumption of the smallest CORESET identified in coresetPoolIndex-r16=0, and the PUCCHs transmitted in even-numbered transmissions are mapped to the reference signal of the QCL-TypeD or QCL assumption of the smallest CORESET identified in coresetPoolIndex-r16=1.

[0149] In a specific implementation, the terminal can also configure the default spatial relationship for the PUCCH in the following ways:

[0150] The N PUCCHs form M PUCCH groups. The PUCCHs in each PUCCH group have the same receive TRP. The first configuration information includes time-domain configuration information, which is used to configure the N PUCCHs to be distributed sequentially in the time domain in units of PUCCH groups. The spatial relationship of the PUCCH groups is configured to be determined according to the QCL-TypeD of the first CORESET of the corresponding receive TRP.

[0151] or

[0152] The N PUCCHs form M PUCCH groups. The PUCCHs in each PUCCH group have the same receive TRP. The first configuration information includes time-domain configuration information, which is used to configure the N PUCCHs to be distributed sequentially in the time domain in units of PUCCH groups. The reference signal for path loss calculation of the PUCCH group is configured as the reference signal of the QCL assumption of the corresponding receive TRP.

[0153] or

[0154] The N PUCCHs form M PUCCH groups. The PUCCHs in each PUCCH group have the same receive TRP. The first configuration information includes time-domain configuration information, which is used to configure the N PUCCHs such that adjacent PUCCHs in the time domain belong to different groups. The spatial relationship of the PUCCH groups is configured to be determined based on the QCL-TypeD of the first CORESET of the corresponding receive TRP.

[0155] or

[0156] The N PUCCHs form M PUCCH groups, and the PUCCHs in each PUCCH group have the same receive TRP. The first configuration information includes time-domain configuration information, which is used to configure the N PUCCHs such that adjacent PUCCHs in the time domain belong to different groups. The reference signal for path loss calculation corresponding to the PUCCH group is configured as the reference signal of the QCL assumption of the receive TRP.

[0157] This implementation can predefine spatial relationships and path loss reference signals according to various principles, which can improve the flexibility of information configuration and the reliability of repeated transmissions.

[0158] Method 3 improves transmission reliability by determining the transmission power of the PUCCH, as explained below:

[0159] The first configuration information includes a TPC command used to determine the transmission power of the PUCCH scheduled by the DCI.

[0160] In this embodiment, the transmission power of the PUCCH can be controlled using the TPC command indicated in the DCI that schedules the PUCCH. For example, the PUCCH scheduled by the DCI associated with coresetPoolIndex-r16=0 is controlled using the TPC command indicated in the DCI with coresetPoolIndex-r16=0.

[0161] From the perspective of the network-side device, this method can also be understood as follows: the first configuration information includes TPC commands, which are used to configure the transmission power of the PUCCH scheduled by the DCI.

[0162] In specific embodiments of the present invention, PUCCHs corresponding to different TRPs correspond to different TPC commands, while PUCCHs corresponding to the same TRP correspond to the same TPC command.

[0163] By determining the transmission power of the PUCCH using the TPC command indicated in the DCI that schedules the PUCCH, the transmission power can be controlled more accurately, and the reliability of repeated transmissions can be improved.

[0164] By combining one or more of the above three methods, the reliability of PUCCH transmission can be further improved.

[0165] See Figure 8 This invention provides a terminal. For example... Figure 8 As shown, the terminal 800 includes a first transceiver 801, which is used for:

[0166] Send N Physical Uplink Control Channels (PUCCHs) that are repeatedly transmitted; where N is an integer greater than or equal to 2.

[0167] Optionally, before transmitting the N repetitive Physical Uplink Control Channels (PUCCH), the first transceiver 801 is further configured to:

[0168] Receive M downlink control information (DCIs), each DCI including first configuration information of a portion of the N physical uplink control channels (PUCCHs). The control resource set (CORESET) carrying the M DCIs has a different pool index, where M is an integer greater than or equal to 2.

[0169] Optionally, before transmitting the N repetitive Physical Uplink Control Channels (PUCCH), the first transceiver 801 is further configured to:

[0170] Receive M downlink control information (DCIs), each DCI including first configuration information of a portion of the N physical uplink control channels (PUCCHs), wherein the receive transmission receiver points (TRPs) corresponding to the portion of the physical uplink control channels (PUCCHs) are the same, and M is an integer greater than or equal to 2.

[0171] Optionally, the first configuration information includes time-domain configuration information, used to configure the N physical uplink control channels (PUCCHs) as follows: physical uplink control channels (PUCCHs) corresponding to the same index parameters in the time domain are transmitted continuously, or, adjacent physical uplink control channels (PUCCHs) in the time domain have different index parameters, wherein the index parameter is the control resource set (CORESET) pool index configured by the control resource set (CORESET) where the downlink control information (DCI) that schedules the physical uplink control channel (PUCCH) is located.

[0172] Optionally, based on the control resource set CORESET pool index parameters configured in the control resource set CORESET where the downlink control information DCI of the physical uplink control channel PUCCH is located, the spatial relationship of the physical uplink control channel PUCCH is predefined as: determined based on the quasi-co-location QCL assumption of one of the control resource sets CORESET with the same index parameters or the configured quasi-co-location type D (QCL-Type D);

[0173] or

[0174] Based on the control resource set CORESET pool index parameters configured in the control resource set CORESET where the downlink control information DCI of the physical uplink control channel PUCCH is located, the path loss reference signal of the physical uplink control channel PUCCH is predefined as: the reference signal corresponding to the quasi-co-address QCL assumption of one of the control resource sets CORESET with the same index parameters or the reference signal corresponding to the configured QCL-TypeD.

[0175] Optionally, one of the control resource sets CORESET configured with the same index parameters is the control resource set CORESET with the smallest identifier among the control resource sets CORESET configured with the same index parameters.

[0176] Optionally, the first configuration information includes a TPC command used to determine the transmission power of the physical uplink control channel (PUCCH) scheduled by the downlink control information (DCI).

[0177] Optionally, before the first transceiver 801 transmits the N repeatedly transmitted Physical Uplink Control Channels (PUCCH), it is further configured to:

[0178] The system receives one Media Access Control (MAC) CE; the MAC CE carries L second configuration information, each second configuration information being used to indicate the spatial relationship parameters of a portion of the N Physical Uplink Control Channels (PUCCHs), where L is an integer greater than or equal to 2.

[0179] Optionally, the N physical uplink control channels (PUCCHs) are configured such that, in the time domain, physical uplink control channels (PUCCHs) corresponding to the same second configuration information are transmitted continuously; or, in the time domain, adjacent physical uplink control channels (PUCCHs) correspond to different second configuration information.

[0180] It should be noted that, in this embodiment of the invention, the terminal 800 described above can be... Figure 1The terminal in any of the corresponding embodiments of the invention, Figure 1 Any implementation method in the corresponding invention embodiment can be implemented by the terminal 800 in this embodiment and achieve the same beneficial effect, which will not be elaborated here.

[0181] See Figure 9 This invention provides a network-side device. For example... Figure 9 As shown, the network-side device 900 includes a second transceiver 901, which is used for:

[0182] Receive a portion of the N Physical Uplink Control Channels (PUCCHs) that are repeatedly transmitted; where N is an integer greater than or equal to 2.

[0183] Optionally, before receiving a portion of the PUCCH from the N repeatedly transmitted Physical Uplink Control Channels (PUCCHs), the second transceiver 901 is further configured to:

[0184] Send downlink control information (DCI), the DCI includes first configuration information corresponding to a portion of the N PUCCHs, the control resource set CORESET carrying the M DCIs has a different control resource set CORESET pool index, each of the M DCIs corresponds to a portion of the N PUCCHs, and M is an integer greater than or equal to 2.

[0185] Optionally, before receiving a portion of the PUCCH from the N repeatedly transmitted Physical Uplink Control Channels (PUCCHs), the second transceiver 901 is further configured to:

[0186] Send downlink control information (DCI), the DCI including first configuration information corresponding to a portion of the N PUCCHs, the portion of the PUCCHs having the same receive transmit receive point (TRP), each of the M DCIs corresponding to a portion of the N PUCCHs, where M is an integer greater than or equal to 2.

[0187] Optionally, the first configuration information includes time-domain configuration information, wherein the M DCIs are used to configure the N PUCCHs as follows: PUCCHs corresponding to the same index parameters in the time domain are transmitted continuously, or adjacent PUCCHs in the time domain have different index parameters, wherein the index parameter is the CORESET pool index configured by the control resource set CORESET where the DCI scheduling the PUCCH is located.

[0188] Optionally, based on the control resource set CORESET pool index parameters configured in the control resource set CORESET where the downlink control information DCI of the physical uplink control channel PUCCH is located, the spatial relationship of the physical uplink control channel PUCCH is predefined as: based on the quasi-co-location QCL assumption of a control resource set CORESET with the same index parameters or the configured quasi-co-location type D configuration;

[0189] or

[0190] Based on the control resource set CORESET pool index parameters configured in the control resource set CORESET where the downlink control information DCI of the physical uplink control channel PUCCH is located, the path loss reference signal of the physical uplink control channel PUCCH is predefined as: the reference signal corresponding to the quasi-co-address QCL assumption of one of the control resource sets CORESET with the same index parameters or the reference signal corresponding to the configured quasi-co-address type D.

[0191] Optionally, one of the control resource sets CORESET configured with the same index parameters is the control resource set CORESET with the smallest identifier among the control resource sets CORESET configured with the same index parameters.

[0192] Optionally, the first configuration information includes a TPC command for configuring the transmission power of the Physical Uplink Control Channel (PUCCH) scheduled by the Downlink Control Information (DCI).

[0193] Optionally, before receiving the N repeatedly transmitted Physical Uplink Control Channels (PUCCH), the second transceiver 901 is further configured to:

[0194] Send one Media Access Control (MAC) CE; the MAC CE carries L second configuration information, each second configuration information is used to configure the spatial relationship parameters of some of the N Physical Uplink Control Channels (PUCCHs), where L is an integer greater than or equal to 2.

[0195] Optionally, the MAC CE is used to configure the N physical uplink control channels (PUCCHs) as follows: in the time domain, physical uplink control channels (PUCCHs) corresponding to the same second configuration information are transmitted continuously; or, in the time domain, adjacent physical uplink control channels (PUCCHs) correspond to different second configuration information.

[0196] It should be noted that the network-side device 900 in the embodiments of the present invention can be the network-side device in the method embodiments described above. Any implementation of the network-side device in the method embodiments described above can be implemented by the network-side device 900 in this embodiment and achieve the same beneficial effects, which will not be elaborated here.

[0197] See Figure 10 Another terminal provided in this embodiment of the invention, such as Figure 10 As shown, the terminal 1000 includes a first memory 1001, a first processor 1002, and a computer program stored in the first memory 1001 and executable on the first processor 1002; when the first processor 1002 executes the program, it implements:

[0198] Send N Physical Uplink Control Channels (PUCCHs) that are repeatedly transmitted; where N is an integer greater than or equal to 2.

[0199] Optionally, before transmitting the N repeatedly transmitted Physical Uplink Control Channels (PUCCH), the first processor 1002 is also used to:

[0200] Receive M downlink control information (DCIs), each DCI including first configuration information of a portion of the N physical uplink control channels (PUCCHs). The control resource set (CORESET) carrying the M DCIs has a different pool index, where M is an integer greater than or equal to 2.

[0201] Optionally, before transmitting the N repeatedly transmitted Physical Uplink Control Channels (PUCCH), the first processor 1002 is also used to:

[0202] Receive M downlink control information (DCIs), each DCI including first configuration information of a portion of the N physical uplink control channels (PUCCHs), wherein the receive transmission receiver points (TRPs) corresponding to the portion of the physical uplink control channels (PUCCHs) are the same, and M is an integer greater than or equal to 2.

[0203] Optionally, the first configuration information includes time-domain configuration information, used to configure the N physical uplink control channels (PUCCHs) as follows: physical uplink control channels (PUCCHs) corresponding to the same index parameters in the time domain are transmitted continuously, or, adjacent physical uplink control channels (PUCCHs) in the time domain have different index parameters, wherein the index parameter is the control resource set (CORESET) pool index configured by the control resource set (CORESET) where the downlink control information (DCI) that schedules the physical uplink control channel (PUCCH) is located.

[0204] Optionally, based on the control resource set CORESET pool index parameters configured in the control resource set CORESET where the downlink control information DCI of the physical uplink control channel PUCCH is located, the spatial relationship of the physical uplink control channel PUCCH is predefined as: determined based on the quasi-co-location QCL assumption of one of the control resource sets CORESET with the same index parameters or the configured quasi-co-location type D (QCL-Type D);

[0205] or

[0206] Based on the control resource set CORESET pool index parameters configured in the control resource set CORESET where the downlink control information DCI of the physical uplink control channel PUCCH is located, the path loss reference signal of the physical uplink control channel PUCCH is predefined as: the reference signal corresponding to the quasi-co-location QCL assumption of one of the control resource sets CORESET with the same index parameters, or the reference signal corresponding to the configured quasi-co-location type D (QCL-Type D).

[0207] Optionally, one of the control resource sets CORESET configured with the same index parameters is the control resource set CORESET with the smallest identifier among the control resource sets CORESET configured with the same index parameters.

[0208] Optionally, the first configuration information includes a TPC command used to determine the transmission power of the physical uplink control channel (PUCCH) scheduled by the downlink control information (DCI).

[0209] Optionally, before sending the N repeatedly transmitted Physical Uplink Control Channels (PUCCH), the first processor 1002 is further configured to:

[0210] The system receives one Media Access Control (MAC) CE; the MAC CE carries L second configuration information, each second configuration information being used to indicate the spatial relationship parameters of a portion of the N Physical Uplink Control Channels (PUCCHs), where L is an integer greater than or equal to 2.

[0211] Optionally, the N physical uplink control channels (PUCCHs) are configured such that, in the time domain, physical uplink control channels (PUCCHs) corresponding to the same second configuration information are transmitted continuously; or, in the time domain, adjacent physical uplink control channels (PUCCHs) correspond to different second configuration information.

[0212] exist Figure 10In this context, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more first processors represented by first processor 1002 and memory represented by first memory 1001. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. A bus interface provides the interface. First processor 1002 is responsible for managing the bus architecture and general processing, and first memory 1001 may store data used by first processor 1002 during operation.

[0213] It should be noted that, in this embodiment of the invention, the terminal 1000 can be... Figure 1 The terminal in any of the corresponding embodiments of the invention, Figure 1 Any implementation method in the corresponding embodiment of the invention can be implemented by the terminal 1000 in this embodiment and achieve the same beneficial effect, which will not be elaborated here.

[0214] See Figure 11 Another network-side device provided in this embodiment of the invention, such as Figure 11 As shown, the network-side device 1100 includes a second memory 1101, a second processor 1102, and a computer program stored in the second memory 1101 and executable on the second processor 1102; when the second processor 1102 executes the program, it implements:

[0215] Receive a portion of the N Physical Uplink Control Channels (PUCCHs) that are repeatedly transmitted; where N is an integer greater than or equal to 2.

[0216] Optionally, before executing a portion of the PUCCH in the N Physical Uplink Control Channel (PUCCH) that are repeatedly transmitted, the second processor 1102 is further configured to:

[0217] Send downlink control information (DCI), the DCI includes first configuration information corresponding to a portion of the N PUCCHs, the control resource set CORESET carrying the M DCIs has a different control resource set CORESET pool index, each of the M DCIs corresponds to a portion of the N PUCCHs, and M is an integer greater than or equal to 2.

[0218] Optionally, before executing a portion of the PUCCH in the N Physical Uplink Control Channel (PUCCH) that are repeatedly transmitted, the second processor 1102 is further configured to:

[0219] Send downlink control information (DCI), the DCI including first configuration information corresponding to a portion of the N PUCCHs, the portion of the PUCCHs having the same receive transmit receive point (TRP), each of the M DCIs corresponding to a portion of the N PUCCHs, where M is an integer greater than or equal to 2.

[0220] Optionally, the first configuration information includes time-domain configuration information, wherein the M DCIs are used to configure the N PUCCHs as follows: PUCCHs corresponding to the same index parameters in the time domain are transmitted continuously, or adjacent PUCCHs in the time domain have different index parameters, wherein the index parameter is the CORESET pool index configured by the control resource set CORESET where the DCI scheduling the PUCCH is located.

[0221] Optionally, the second processor 1102 is also used for:

[0222] Based on the control resource set CORESET pool index parameters configured in the control resource set CORESET where the downlink control information DCI of the physical uplink control channel PUCCH is located, the spatial relationship of the physical uplink control channel PUCCH is predefined as follows: based on the quasi-co-location QCL assumption of a control resource set CORESET with the same index parameters or the configured quasi-co-location type D (QCL-Type D) configuration.

[0223] or

[0224] Based on the control resource set CORESET pool index parameters configured in the control resource set CORESET where the downlink control information DCI of the physical uplink control channel PUCCH is located, the path loss reference signal of the physical uplink control channel PUCCH is predefined as: the reference signal corresponding to the quasi-co-location QCL assumption of one of the control resource sets CORESET with the same index parameters, or the reference signal corresponding to the configured quasi-co-location type D (QCL-Type D).

[0225] Optionally, one of the control resource sets CORESET configured with the same index parameters is the control resource set CORESET with the smallest identifier among the control resource sets CORESET configured with the same index parameters.

[0226] Optionally, the first configuration information includes a TPC command for configuring the transmission power of the Physical Uplink Control Channel (PUCCH) scheduled by the Downlink Control Information (DCI).

[0227] Optionally, before receiving the N repeatedly transmitted Physical Uplink Control Channels (PUCCH), the second processor 1102 is also used to:

[0228] Send one Media Access Control (MAC) CE; the MAC CE carries L second configuration information, each second configuration information is used to configure the spatial relationship parameters of some of the N Physical Uplink Control Channels (PUCCHs), where L is an integer greater than or equal to 2.

[0229] Optionally, the MAC CE is used to configure the N physical uplink control channels (PUCCHs) as follows: in the time domain, physical uplink control channels (PUCCHs) corresponding to the same second configuration information are transmitted continuously; or, in the time domain, adjacent physical uplink control channels (PUCCHs) correspond to different second configuration information.

[0230] It should be noted that the network-side device 1100 in the embodiments of the present invention can be any implementation of the network-side device in the above method embodiments. Any implementation of the network-side device in the above method embodiments can be implemented by the network-side device 1100 in this embodiment and achieve the same beneficial effects, which will not be elaborated here.

[0231] This invention also provides a computer-readable storage medium storing a computer program. When executed by a processor, this computer program implements the various processes of the network-side device and terminal-side in the above-described transmission method embodiments, achieving the same technical effects. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0232] In the several embodiments provided in this application, it should be understood that the disclosed methods and apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0233] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can be physically comprised separately, or two or more units can be integrated into one unit. The integrated unit described above can be implemented in hardware or in the form of hardware plus software functional units.

[0234] The integrated units implemented as software functional units described above can be stored in a computer-readable storage medium. These software functional units, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute some steps of the transmission and reception methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0235] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A transmission method for a terminal, characterized by, The method comprises: transmitting N physical uplink control channels (PUCCHs) in repetition transmission; N is an integer greater than or equal to 2; The method further comprises: receiving 1 media access control (MAC) control element (CE) carrying L second configuration information, each second configuration information being used to indicate a spatial relation parameter of part of the N PUCCHs, L being an integer greater than or equal to 2; The N PUCCHs are configured to be transmitted consecutively in the time domain corresponding to the same second configuration information, or adjacent PUCCHs correspond to different second configuration information in the time domain; The method further comprises: receiving M downlink control information (DCI), each DCI including first configuration information corresponding to part of the N PUCCHs, the first configuration information including time domain configuration information used to configure the N PUCCHs to be transmitted consecutively in the time domain corresponding to the same index parameter, or adjacent PUCCHs correspond to different index parameters in the time domain, the index parameter being a control resource set (CORESET) pool index configured by a CORESET in which the DCI scheduling the PUCCH is located.

2. The transmission method of claim 1, wherein, Before transmitting the N PUCCHs in repetition transmission, the method further comprises: The M downlink control information (DCI) is carried in different control resource set (CORESET) pool indexes configured by CORESETs, M being an integer greater than or equal to 2.

3. The transmission method of claim 1, wherein, Before transmitting the N PUCCHs in repetition transmission, the method further comprises: receiving M downlink control information (DCI), each DCI including first configuration information corresponding to part of the N PUCCHs, the part of the PUCCHs corresponding to the same transmission reception point (TRP), M being an integer greater than or equal to 2.

4. The transmission method of claim 2, wherein According to the control resource set (CORESET) pool index parameter configured by a CORESET in which the downlink control information (DCI) scheduling the PUCCH is located, the spatial relation of the PUCCH is predefined as being determined according to quasi co-location (QCL) assumption or configured QCL type D of one of the CORESETs configured with the same index parameter; or ​ According to a control resource set CORESET pool index parameter configured by a control resource set CORESET in which downlink control information DCI scheduling the physical uplink control channel PUCCH is located, a path loss reference signal of the physical uplink control channel PUCCH is predefined as: a reference signal corresponding to a quasi co-location QCL assumption of one of the control resource sets CORESET configured with the same index parameter or a reference signal corresponding to a configured quasi co-location type D.

5. The transmission method of claim 4, wherein, The one of the control resource sets CORESET configured with the same index parameter is a control resource set CORESET identified as the smallest among the control resource sets CORESET configured with the same index parameter.

6. The transmission method of claim 2, wherein, The first configuration information includes a TPC command used to determine a transmission power of the physical uplink control channel PUCCH scheduled by the downlink control information DCI.

7. A transmission method for a network-side device, comprising: Comprise: Receiving part of the N physical uplink control channels PUCCH in repeated transmission; The N is an integer greater than or equal to 2; The method further comprises: Sending 1 media access control control element MAC CE; The media access control control element MAC CE carries L second configuration information, each second configuration information is used for configuring a spatial relationship parameter of part of the N physical uplink control channels PUCCH, and the L is an integer greater than or equal to 2; The MAC CE is used to configure the N physical uplink control channels PUCCH as: in the time domain, the physical uplink control channels PUCCH corresponding to the same second configuration information are continuously transmitted; Or, in the time domain, the second configuration information corresponding to adjacent physical uplink control channels PUCCH is different; The method further comprises: Sending downlink control information DCI, the DCI includes first configuration information corresponding to part of the N PUCCH, the first configuration information includes time domain configuration information, and the M DCI is used to configure the N PUCCH as: in the time domain, the PUCCH corresponding to the same index parameter is continuously transmitted, or in the time domain, the index parameters corresponding to adjacent PUCCH are different, and the index parameter is a CORESET pool index configured by a control resource set CORESET in which DCI scheduling the PUCCH is located.

8. The transmission method of claim 7, wherein, Before receiving part of the N physical uplink control channels PUCCH in repeated transmission, further comprising: The control resource set CORESET pool index configured by the control resource set CORESET carrying the M DCIs is different, each of the M DCIs corresponds to part of the N PUCCH, and the M is an integer greater than or equal to 2.

9. The transmission method of claim 7, wherein, Before receiving part of the N physical uplink control channels PUCCH in repeated transmission, further comprising: The control resource set CORESET pool index configured by the control resource set CORESET carrying the M DCIs is different, each of the M DCIs corresponds to part of the N PUCCH, and the M is an integer greater than or equal to 2. transmitting downlink control information DCI, the DCI including first configuration information corresponding to part of the N PUCCHs, the part of the N PUCCHs corresponding to the same receiving transmission receiving point TRP, each of the M DCIs corresponding to part of the N PUCCHs, the M being an integer greater than or equal to 2.

10. The transmission method of claim 8, wherein the spatial relation of the physical uplink control channel PUCCH is predefined according to a control resource set CORESET pool index parameter configured by a control resource set CORESET in which the downlink control information DCI scheduling the physical uplink control channel PUCCH is located, as a quasi co-location QCL assumption or a configured quasi co-location type D configuration of one of the control resource sets CORESETs configured with the same index parameter. Or the path loss reference signal of the physical uplink control channel PUCCH is predefined according to a control resource set CORESET pool index parameter configured by a control resource set CORESET in which the downlink control information DCI scheduling the physical uplink control channel PUCCH is located, as a reference signal corresponding to a quasi co-location QCL assumption or a configured quasi co-location type D configuration of one of the control resource sets CORESETs configured with the same index parameter.

11. The transmission method of claim 10, wherein, The one of the control resource sets CORESETs configured with the same index parameter is the control resource set CORESET with the smallest identifier among the control resource sets CORESETs configured with the same index parameter.

12. The transmission method of claim 8, wherein, The first configuration information includes a TPC command for configuring the transmission power of the physical uplink control channel PUCCH scheduled by the downlink control information DCI.

13. A terminal, characterized by The terminal includes a first transceiver, the first transceiver being configured to: transmit N physical uplink control channels PUCCHs in repeated transmission, the N being an integer greater than or equal to 2; The first transceiver is further configured to: receive 1 medium access control control element MAC CE, the medium access control control element MAC CE carrying L second configuration information, each second configuration information being used to indicate a spatial relation parameter of part of the N physical uplink control channels PUCCHs, the L being an integer greater than or equal to 2; The N physical uplink control channels PUCCHs are configured such that, in the time domain, the physical uplink control channels PUCCHs corresponding to the same second configuration information are transmitted consecutively, or in the time domain, the second configuration information corresponding to adjacent physical uplink control channels PUCCHs is different. The first transceiver is further configured to:

14. The terminal according to claim 13, characterized by The control resource set CORESET pool index configured by the control resource set CORESET carrying the M downlink control information DCIs is different, and the M is an integer greater than or equal to 2.

15. The terminal according to claim 14, wherein According to the control resource set CORESET pool index parameter configured by the control resource set CORESET in which the downlink control information DCI scheduling the physical uplink control channel PUCCH is located, the spatial relationship of the physical uplink control channel PUCCH is predefined as being determined according to the quasi co-location QCL assumption or the configured quasi co-location type D of one of the control resource sets CORESET configured with the same index parameter; Or According to the control resource set CORESET pool index parameter configured by the control resource set CORESET in which the downlink control information DCI scheduling the physical uplink control channel PUCCH is located, the path loss reference signal of the physical uplink control channel PUCCH is predefined as being determined according to the reference signal corresponding to the quasi co-location QCL assumption or the reference signal corresponding to the configured quasi co-location type D of one of the control resource sets CORESET configured with the same index parameter. The first configuration information includes a TPC command for determining the transmission power of the physical uplink control channel PUCCH scheduled by the downlink control information DCI.

16. The terminal according to claim 14, characterized by The first transceiver is further configured to:

17. A network-side device, comprising: Receive part of the N physical uplink control channels PUCCH in repeated transmission; the N is an integer greater than or equal to 2; Send 1 medium access control control element MAC CE; the medium access control control element MAC CE carries L second configuration information, each second configuration information is used for configuring the spatial relationship parameter of part of the N physical uplink control channels PUCCH; the L is an integer greater than or equal to 2; The MAC CE is used to configure the N physical uplink control channels PUCCH as: in the time domain, the physical uplink control channels PUCCH corresponding to the same second configuration information are continuously transmitted; or in the time domain, the second configuration information corresponding to adjacent physical uplink control channels PUCCH is different; ​ transmitting a downlink control information DCI, the DCI including first configuration information corresponding to part of the N PUCCHs, the first configuration information including time domain configuration information, the M DCIs being used to configure the N PUCCHs to be: continuously transmitted in time domain corresponding to the same index parameter, or, the index parameters corresponding to the adjacent PUCCHs in time domain being different, the index parameter being a control resource set CORESET pool index configured by a CORESET in which the DCI scheduling the PUCCH is located.

18. The network-side device of claim 17, wherein, The second transceiver is further configured to: The control resource set CORESET pool index configured by a control resource set CORESET carrying the M DCIs is different, each of the M DCIs corresponding to part of the N PUCCHs, the M being an integer greater than or equal to 2.

19. The network-side device of claim 18, wherein, According to an index parameter of a control resource set CORESET pool configured by a control resource set CORESET in which a downlink control information DCI scheduling the physical uplink control channel PUCCH is located, a spatial relation of the physical uplink control channel PUCCH is predefined to be determined according to a quasi co-location QCL assumption or a configured quasi co-location type D of one of the control resource sets CORESETs configured with the same index parameter. According to an index parameter of a control resource set CORESET pool configured by a control resource set CORESET in which a downlink control information DCI scheduling the physical uplink control channel PUCCH is located, a path loss reference signal of the physical uplink control channel PUCCH is predefined to be a reference signal corresponding to a quasi co-location QCL assumption or a configured quasi co-location type D of one of the control resource sets CORESETs configured with the same index parameter.

20. The network-side device of claim 18, wherein, The first configuration information includes a TPC command used to configure a transmission power of the physical uplink control channel PUCCH scheduled by the downlink control information DCI.

21. A terminal, characterized by The computer program product comprises a memory, a processor and a computer program stored in the memory and executable on the processor; when the processor executes the program, the transmission method of any one of claims 1 to 6 is implemented.

22. A network-side device, comprising: The computer program product comprises a memory, a processor and a computer program stored in the memory and executable on the processor; when the processor executes the program, the transmission method of any one of claims 7 to 12 is implemented.

23. A computer readable storage medium having stored thereon a computer program, characterized in that, The program is executed by the processor to implement the transmission method of any one of claims 1 to 6, or to implement the transmission method of any one of claims 7 to 12.

Images