Communication method, terminal, network device and storage medium

Abstract

The present disclosure relates to a communication method, a terminal, a network device and a storage medium. The communication method comprises: determining transmission parameters of a first physical uplink control channel (PUCCH); and sending the first PUCCH on the basis of the transmission parameters of the first PUCCH. The present disclosure can improve the transmission performance.

Description

Communication method, terminal, network device and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a communication method, a terminal, a network device, and a storage medium. Background Art

[0002] Currently, the terminal can use the common physical uplink control channel (PUCCH) parameters configured by the network device to send a random access message (Msg) 4 hybrid automatic repeat request (HARQ-ACK).

[0003] Summary of the Invention

[0004] The PUCCH transmission nodes are different, so the transmission performance of some PUCCHs needs to be improved.

[0005] The embodiments of the present disclosure provide a communication method, a terminal, a network device, and a storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, a communication method is proposed. The method is executed by a terminal, and the method includes: determining a transmission parameter of a first physical uplink control channel PUCCH; and sending the first PUCCH based on the transmission parameter of the first PUCCH.

[0007] According to a second aspect of an embodiment of the present disclosure, a communication method is proposed. The method is executed by a network device, and the method includes: receiving a first physical uplink control channel PUCCH, where a transmission parameter of the first PUCCH is determined by a terminal.

[0008] According to the third aspect of an embodiment of the present disclosure, a communication method is proposed, including: a terminal determines a transmission parameter of a first physical uplink control channel PUCCH; the terminal sends the first PUCCH based on the transmission parameter of the first PUCCH; and a network device receives the first physical uplink control channel PUCCH.

[0009] According to a fourth aspect of an embodiment of the present disclosure, a terminal is proposed, including: a processing module for determining transmission parameters of a first physical uplink control channel PUCCH; and a transceiver module for sending the first PUCCH based on the transmission parameters of the first PUCCH.

[0010] According to a fifth aspect of an embodiment of the present disclosure, a network device is proposed, including: a transceiver module, configured to receive a first physical uplink control channel PUCCH, wherein a transmission parameter of the first PUCCH is determined by a terminal.

[0011] According to a sixth aspect of an embodiment of the present disclosure, a terminal is proposed, comprising: one or more processors; wherein the terminal is configured to execute the first aspect and any one of the communication methods in the first aspect.

[0012] According to a seventh aspect of an embodiment of the present disclosure, a network device is proposed, comprising: one or more processors; wherein the network device is used to execute the second aspect and any one of the communication methods in the second aspect.

[0013] According to the eighth aspect of an embodiment of the present disclosure, a communication system is proposed, comprising a terminal and a network device, wherein the terminal is configured to implement the first aspect and any one of the communication methods in the first aspect, and the network device is configured to implement the second aspect and any one of the communication methods in the second aspect.

[0014] According to the ninth aspect of the embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes a communication method such as the first aspect and any one of the first aspects or the second aspect and any one of the third aspects.

[0015] The present disclosure determines the transmission parameters of the first PUCCH by receiving the first information sent by the network device, so that the determined first PUCCH is a PUCCH capable of repeated transmission, thereby improving transmission performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0017] FIG1a is a schematic diagram showing a communication system architecture according to an embodiment of the present disclosure.

[0018] Fig. 1b is a schematic diagram showing interaction between a terminal and a network device according to an exemplary embodiment.

[0019] FIG2 a is a schematic diagram showing interaction of a communication method according to an embodiment of the present disclosure.

[0020] FIG2 b is a schematic diagram showing interaction of a communication method according to an embodiment of the present disclosure.

[0021] FIG3 a is a flow chart showing a communication method according to an embodiment of the present disclosure.

[0022] FIG3 b is a flow chart showing a communication method according to an embodiment of the present disclosure.

[0023] FIG3 c is a flow chart showing a communication method according to an embodiment of the present disclosure.

[0024] FIG4 a is a flow chart showing a communication method according to an embodiment of the present disclosure.

[0025] FIG4 b is a flow chart showing a communication method according to an embodiment of the present disclosure.

[0026] FIG4 c is a flow chart showing a communication method according to an embodiment of the present disclosure.

[0027] FIG5 is a flow chart showing a communication method according to an embodiment of the present disclosure.

[0028] FIG6 a is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.

[0029] FIG6 b is a schematic structural diagram of a network device according to an embodiment of the present disclosure.

[0030] Fig. 7a is a schematic structural diagram of a communication device according to an exemplary embodiment.

[0031] FIG7 b is a schematic diagram showing a chip structure according to an exemplary embodiment. DETAILED DESCRIPTION

[0032] The embodiments of the present disclosure provide a communication method, a terminal, a network device, and a storage medium.

[0033] In a first aspect, an embodiment of the present disclosure proposes a communication method, which is executed by a terminal and includes: determining a transmission parameter of a first physical uplink control channel PUCCH; and sending the first PUCCH based on the transmission parameter of the first PUCCH.

[0034] In the above embodiment, the transmission parameters of the first PUCCH may be determined, and the first PUCCH may be sent based on the parameters, so that the PUCCH capable of repeated transmission is used, thereby improving transmission performance.

[0035] In combination with some embodiments of the first aspect, in some embodiments, at least one of the following methods is used to determine the transmission parameters of the first PUCCH: determining the transmission parameters of the first PUCCH based on the provisions in the protocol; receiving first information, where the first information is used by the terminal to determine the transmission parameters of the first PUCCH.

[0036] In the above implementation, the transmission parameters of the first PUCCH are determined by receiving the first information sent by the network device and / or in a manner specified in the protocol, and the PUCCH capable of repeated transmission is used to improve transmission performance.

[0037] In combination with some embodiments of the first aspect, in some embodiments, the transmission of the first PUCCH is located after Msg4 hybrid automatic repeat request confirmation HARQ-ACK; and / or, the transmission of the first PUCCH is located before the terminal sends the first signaling, and the first signaling includes at least one of the following: terminal capability information; terminal reconfiguration completion information.

[0038] In the above embodiment, it is possible to implement the use of a PUCCH capable of repeated transmission after Msg4 hybrid automatic repeat request confirmation HARQ-ACK and / or before the terminal sends the first signaling, thereby improving transmission performance.

[0039] In combination with some embodiments of the first aspect, in some embodiments, the first PUCCH is used to carry at least one of the following: a hybrid automatic repeat request confirmation HARQ-ACK message; a scheduling request SR message; and a channel state information CSI.

[0040] In the above embodiment, the first PUCCH may be used to carry at least one of the above items, so as to improve transmission performance when carrying the above messages.

[0041] In combination with some embodiments of the first aspect, in some embodiments, the terminal does not expect the network device to configure transmission parameters of a dedicated physical uplink control channel dedicated PUCCH to the terminal through Msg4, and the first PUCCH is a public PUCCH.

[0042] In the above embodiment, the terminal may not expect the network device to configure the transmission parameters of the dedicated PUCCH through Msg4. In this case, the first PUCCH may be a public PUCCH, and the terminal may subsequently use the transmission parameters of the public PUCCH for transmission to improve transmission performance.

[0043] In combination with some embodiments of the first aspect, in some embodiments, the first PUCCH is a dedicated physical uplink control channel dedicated PUCCH, and transmission parameters of the dedicated PUCCH are carried based on the random access message Msg4.

[0044] In the above embodiment, if the network device configures the transmission parameters of the dedicated physical uplink control channel dedicated PUCCH to the terminal through Msg4, and the first PUCCH is the dedicated PUCCH, the terminal can subsequently use the transmission parameters of the dedicated PUCCH to improve transmission performance.

[0045] In combination with some embodiments of the first aspect, in some embodiments, a repetition transmission parameter of the first PUCCH is determined, and the first PUCCH is repetitively transmitted according to the repetition transmission parameter.

[0046] In the above embodiment, the repetition transmission parameter of the first PUCCH may be determined to facilitate repetition transmission and improve transmission performance.

[0047] In combination with some embodiments of the first aspect, in some embodiments, the repetition transmission parameter of the dedicated PUCCH is determined in the following manner: the repetition transmission parameter of the dedicated PUCCH is determined to be the same as the repetition transmission parameter used by the terminal to send the Msg4 HARQ-ACK message.

[0048] In the above embodiment, it may be determined that the repetition transmission parameter of the dedicated PUCCH is the same as the repetition transmission parameter used by the terminal to send the Msg4 HARQ-ACK message, so as to save signaling resources.

[0049] In combination with some embodiments of the first aspect, in some embodiments, the repetition transmission parameters of the dedicated PUCCH are determined in the following manner: based on the second information sent by the network device, the repetition transmission parameters of the dedicated PUCCH are determined, and the second information is used to semi-statically configure the repetition transmission parameters of the dedicated PUCCH.

[0050] In the above embodiment, the repetition transmission parameter of the dedicated PUCCH may be determined based on the second information of the network device to improve efficiency.

[0051] In combination with some embodiments of the first aspect, in some embodiments, the second information is carried based on at least one of the following: system message SIB; Msg4.

[0052] In the above embodiment, the second information may be carried based on at least one of the above items to adapt to different situations and improve efficiency.

[0053] In combination with some embodiments of the first aspect, in some embodiments, the determination of the repetition transmission parameter of the dedicated PUCCH satisfies at least one of the following priority relationships: determining the repetition transmission parameter of the dedicated PUCCH based on the Msg4 takes precedence over determining the repetition transmission parameter of the dedicated PUCCH based on the SIB; determining the repetition transmission parameter of the dedicated PUCCH based on the SIB takes precedence over determining that the repetition transmission parameter of the dedicated PUCCH is the same as the repetition transmission parameter used by the terminal to send the Msg4 HARQ-ACK message.

[0054] In the above embodiment, the repetition transmission parameter may be determined based on the priority relationship, so that the determined repetition transmission parameter is more accurate.

[0055] In combination with some embodiments of the first aspect, in some embodiments, if at least one of the following conditions is met, the terminal performs repeated transmission based on the repeated transmission parameter: the terminal sends a repeated transmission capability indication to the network device; the terminal sends a repeated transmission request to the network device.

[0056] In the above embodiment, after determining the retransmission parameter, the terminal may use the retransmission parameter to perform retransmission after sending a retransmission capability to the network device or a retransmission request to the network, so as to improve transmission performance.

[0057] In combination with some embodiments of the first aspect, in some embodiments, the repetition transmission parameters of the dedicated PUCCH scheduled by the downlink control information DCI in the fallback format and the repetition transmission parameters of the dedicated PUCCH scheduled by the DCI in the non-fallback format are determined based on the same or different methods; the repetition transmission parameters corresponding to the dedicated PUCCH scheduled by the DCI in the fallback format are the same as or different from the repetition transmission parameters corresponding to the dedicated PUCCH scheduled by the DCI in the non-fallback format.

[0058] In the above embodiment, DCI of different formats can use the same or different methods to determine the repetition transmission parameters, and the determined repetition transmission parameters can also be the same or different, so as to achieve more targeted use of the repetition transmission parameters for repetition transmission, or save signaling consumption.

[0059] In combination with some embodiments of the first aspect, in some embodiments, repeated transmission is not performed if at least one of the following items is met: the terminal does not perform repeated transmission when sending the Msg4 HARQ-ACK message; the second information is not received.

[0060] In the above embodiment, when the terminal does not perform repeated transmission when sending the Msg4 HARQ-ACK message and / or does not receive the second information, repeated transmission may not be performed, and there is no need to determine whether to perform repeated transmission, thereby improving efficiency.

[0061] In combination with some embodiments of the first aspect, in some embodiments, the repetition transmission parameters of the dedicated PUCCH are determined in the following manner: based on the downlink DCI sent by the network device, the repetition transmission parameters of the dedicated PUCCH are determined, the downlink DCI is used to schedule the dedicated PUCCH, and the downlink DCI carries the repetition transmission parameters corresponding to the dedicated PUCCH.

[0062] In the above embodiment, the repeated transmission parameters can be dynamically configured through the downlink DCI to improve transmission performance and efficiency.

[0063] In combination with some embodiments of the first aspect, in some embodiments, in response to the cyclic redundancy check CRC of the downlink DCI being scrambled by the cell radio network temporary identifier C-RNTI, and / or the downlink DCI being a fallback format DCI, at least one of the following methods is used to determine the repetition transmission parameters of the dedicated PUCCH based on the downlink DCI sent by the network device: determining the repetition transmission parameters of the dedicated PUCCH based on the first field in the downlink DCI, the first field being the downlink allocation indication field DAI; determining the repetition transmission parameters of the dedicated PUCCH based on at least part of the bits of the second field in the downlink DCI, the second field including at least one of the following: modulation and coding scheme MCS field; transmit power control TPC field; PUCCH resource indication field PRI.

[0064] In the above embodiment, the repeated transmission parameters can be dynamically configured through different fields in the downlink DCI to improve transmission performance and efficiency.

[0065] In combination with some embodiments of the first aspect, in some embodiments, in response to the CRC of the downlink DCI being scrambled by the C-RNTI, and / or the downlink DCI being a non-fallback format DCI, the repetition transmission parameters of the dedicated PUCCH are determined based on the downlink DCI sent by the network device in at least one of the following ways: determining the repetition transmission parameters of the dedicated PUCCH based on the third field in the downlink DCI, the third field being a newly added field in the downlink DCI; determining the repetition transmission parameters of the dedicated PUCCH based on at least part of the bits of the second field in the downlink DCI, the second field including at least one of the following: modulation and coding scheme MCS field; transmission power control TPC field; PUCCH resource indication PRI field.

[0066] In the above embodiment, the repeated transmission parameters can be dynamically configured through different fields in the downlink DCI to improve transmission performance and efficiency.

[0067] In combination with some embodiments of the first aspect, in some embodiments, the second field includes a PRI field, where the PRI field is used to indicate a dedicated PUCCH resource, and each dedicated PUCCH resource corresponds to a repetition transmission parameter.

[0068] In the above embodiment, for the PRI field, each dedicated PUCCH resource may correspond to a repetition transmission parameter, so as to more efficiently determine the repetition transmission parameter.

[0069] In combination with some embodiments of the first aspect, in some embodiments, the first field or the second field indicates a repetition transmission parameter by means of a codepoint; or, the first field or the second field indicates the number of repetition transmissions of the dedicated PUCCH by indicating a numerical set index, and the numerical set index is determined based on the repetition parameter set carried by the second information.

[0070] In the above embodiment, the first field or the second field may indicate the repetition transmission parameter in different ways to improve efficiency.

[0071] In combination with some embodiments of the first aspect, in some embodiments, at least one of the following conditions is met, and the retransmission parameter of the dedicated PUCCH is determined based on the first field or the second field in the downlink DCI: sending a retransmission capability indication to the network device; sending a retransmission request to the network device; receiving second information sent by the network device, the second information including a bit for explicitly instructing the terminal to perform retransmission; receiving second information sent by the network device, the second information including the retransmission parameter.

[0072] In the above embodiment, when at least one condition is met, the first field and the second field may be used to determine the repetition transmission parameter of the dedicated PUCCH to improve efficiency.

[0073] In combination with some embodiments of the first aspect, in some embodiments, the repetition transmission parameter includes at least one of the following: the number of repetition transmissions; the set of repetition transmission numbers; the threshold value of the reference information receiving power RSRP, and the RSRP threshold value is used by the terminal to determine whether to perform repetition transmission.

[0074] In the above embodiment, the repeated transmission parameter may include at least one of the above items to achieve more flexible repeated transmission and improve transmission performance.

[0075] According to a second aspect of an embodiment of the present disclosure, a communication method is provided, including: receiving a first physical uplink control channel PUCCH, where a transmission parameter of the first PUCCH is determined by a terminal.

[0076] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending first information to the terminal, where the first information is used by the terminal to determine transmission parameters of the first PUCCH.

[0077] In combination with some embodiments of the second aspect, in some embodiments, the transmission of the first PUCCH is located after the Msg4 hybrid automatic repeat request confirmation HARQ-ACK, and / or, the transmission of the first PUCCH is located before the terminal sends the first signaling, and the first signaling includes at least one of the following: terminal capability information; terminal reconfiguration completion information.

[0078] In combination with some embodiments of the second aspect, in some embodiments, the first PUCCH is used to carry at least one of the following: a hybrid automatic repeat request confirmation HARQ-ACK message; a scheduling request SR message; and a channel state information CSI.

[0079] In combination with some embodiments of the second aspect, in some embodiments, the terminal does not expect the network device to configure the transmission parameters of the dedicated physical uplink control channel dedicated PUCCH to the terminal through Msg4, and the first PUCCH is a public PUCCH.

[0080] In combination with some embodiments of the second aspect, in some embodiments, the first PUCCH is a dedicated physical uplink control channel dedicated PUCCH, and the transmission parameters of the dedicated PUCCH are carried based on the random access message Msg4.

[0081] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending second information to the network, where the second information is used to semi-statically configure the repetition transmission parameters of the dedicated PUCCH.

[0082] In combination with some embodiments of the second aspect, in some embodiments, the second information is carried based on at least one of the following: system message SIB; Msg4.

[0083] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending a downlink DCI to the terminal, where the downlink DCI is used to schedule the dedicated PUCCH, and the downlink DCI carries a repetition transmission parameter corresponding to the dedicated PUCCH.

[0084] In combination with some embodiments of the second aspect, in some embodiments, the cyclic redundancy check CRC of the downlink DCI is encrypted by the cell radio network temporary identifier C-RNTI, and / or the downlink DCI is a fallback format DCI, and the downlink DCI includes at least one of the following: a first field, the first field is used to determine the repetition transmission parameters of the dedicated PUCCH, and the first field is the downlink allocation indication field DAI; a second field, the second field is used to determine the repetition transmission parameters of the dedicated PUCCH, and the second field includes at least one of the following: a modulation and coding scheme MCS field; a transmit power control TPC field; and a PUCCH resource indication field PRI.

[0085] In combination with some embodiments of the second aspect, in some embodiments, the CRC of the downlink DCI is encrypted by C-RNTI, and / or the downlink DCI is a non-fallback format DCI, and the downlink DCI includes at least one of the following: a third field, the third field is used to determine the repetition transmission parameters of the dedicated PUCCH, and the third field is a newly added field in the downlink DCI; a second field, the second field is used to determine the repetition transmission parameters of the dedicated PUCCH, and the second field includes at least one of the following: a modulation and coding scheme MCS field; a transmit power control TPC field; and a PUCCH resource indication field PRI.

[0086] In combination with some embodiments of the second aspect, in some embodiments, the second field includes a PRI field, where the PRI field is used to indicate a dedicated PUCCH resource, and each dedicated PUCCH resource corresponds to a repetition transmission parameter.

[0087] In combination with some embodiments of the second aspect, in some embodiments, the first field or the second field indicates a repetition transmission parameter by means of a codepoint; or, the first field or the second field indicates the number of repetition transmissions of the dedicated PUCCH by indicating a numerical set index, and the numerical set index is determined based on the repetition parameter set carried by the second information.

[0088] In combination with some embodiments of the second aspect, in some embodiments, at least one of the following conditions is met, and the downlink DCI is used to determine the repeated transmission parameters of the dedicated PUCCH: receiving a repeated transmission capability indication sent by the terminal; receiving a repeated transmission request sent by the terminal; sending a second information to the terminal, wherein the second information includes a bit for explicitly instructing the terminal to perform repeated transmission; sending a second information to the terminal, wherein the second information includes the repeated transmission parameters.

[0089] In combination with some embodiments of the second aspect, in some embodiments, the repetition transmission parameter includes at least one of the following: the number of repetition transmissions; the set of repetition transmission numbers; the threshold value of the reference information receiving power RSRP, and the RSRP threshold value is used by the terminal to determine whether to perform repetition transmission.

[0090] According to a third aspect of an embodiment of the present disclosure, a communication method is provided, including: a terminal determines a transmission parameter of a first physical uplink control channel PUCCH; the terminal sends the first PUCCH based on the transmission parameter of the first PUCCH; and a network device receives the first physical uplink control channel PUCCH.

[0091] According to a fourth aspect of an embodiment of the present disclosure, a terminal is provided, including: a processing module for determining transmission parameters of a first physical uplink control channel PUCCH; and a transceiver module for sending the first PUCCH based on the transmission parameters of the first PUCCH.

[0092] In combination with some embodiments of the fourth aspect, in some embodiments, the processing module adopts at least one of the following methods to determine the transmission parameters of the first PUCCH: determining the transmission parameters of the first PUCCH based on the provisions in the protocol; receiving first information, and the first information is used by the terminal to determine the transmission parameters of the first PUCCH.

[0093] In combination with some embodiments of the fourth aspect, in some embodiments, the transmission of the first PUCCH is located after Msg4 hybrid automatic repeat request confirmation HARQ-ACK; and / or, the transmission of the first PUCCH is located before the terminal sends the first signaling, and the first signaling includes at least one of the following: terminal capability information; terminal reconfiguration completion information.

[0094] In combination with some embodiments of the fourth aspect, in some embodiments, the first PUCCH is used to carry at least one of the following: a hybrid automatic repeat request confirmation HARQ-ACK message; a scheduling request SR message; and a channel state information CSI.

[0095] In combination with some embodiments of the fourth aspect, in some embodiments, the terminal does not expect the network device to configure the transmission parameters of the dedicated physical uplink control channel dedicated PUCCH to the terminal through Msg4, and the first PUCCH is a public PUCCH.

[0096] In combination with some embodiments of the fourth aspect, in some embodiments, the first PUCCH is a dedicated physical uplink control channel dedicated PUCCH, and the transmission parameters of the dedicated PUCCH are carried based on the random access message Msg4.

[0097] In combination with some embodiments of the fourth aspect, in some embodiments, the terminal further includes a processing module, configured to determine a repetition transmission parameter of the first PUCCH, and perform repetition transmission of the first PUCCH according to the repetition transmission parameter.

[0098] In combination with some embodiments of the fourth aspect, in some embodiments, the processing module determines the repetition transmission parameter of the dedicated PUCCH in the following manner: determining that the repetition transmission parameter of the dedicated PUCCH is the same as the repetition transmission parameter used by the terminal to send the Msg4 HARQ-ACK message.

[0099] In combination with some embodiments of the fourth aspect, in some embodiments, the processing module determines the repetition transmission parameters of the dedicated PUCCH in the following manner: based on the second information sent by the network device, the repetition transmission parameters of the dedicated PUCCH are determined, and the second information is used to semi-statically configure the repetition transmission parameters of the dedicated PUCCH.

[0100] In combination with some embodiments of the fourth aspect, in some embodiments, the second information is carried based on at least one of the following: system message SIB; Msg4.

[0101] In combination with some embodiments of the fourth aspect, in some embodiments, the processing module determines that the repetition transmission parameters of the dedicated PUCCH satisfy at least one of the following priority relationships: determining the repetition transmission parameters of the dedicated PUCCH based on the Msg4 takes precedence over determining the repetition transmission parameters of the dedicated PUCCH based on the SIB; determining the repetition transmission parameters of the dedicated PUCCH based on the SIB takes precedence over determining that the repetition transmission parameters of the dedicated PUCCH are the same as the repetition transmission parameters used by the terminal to send the Msg4 HARQ-ACK message.

[0102] In combination with some embodiments of the fourth aspect, in some embodiments, the processing module is used to meet at least one of the following conditions and perform repeated transmission based on the repeated transmission parameters: the terminal sends a repeated transmission capability indication to the network device; the terminal sends a repeated transmission request to the network device.

[0103] In combination with some embodiments of the fourth aspect, in some embodiments, the processing module determines the repetition transmission parameters of the dedicated PUCCH scheduled by the downlink control information DCI in the fallback format and the repetition transmission parameters of the dedicated PUCCH scheduled by the DCI in the non-fallback format based on the same or different methods; the repetition transmission parameters corresponding to the dedicated PUCCH scheduled by the DCI in the fallback format are the same or different from the repetition transmission parameters corresponding to the dedicated PUCCH scheduled by the DCI in the non-fallback format.

[0104] In combination with some embodiments of the fourth aspect, in some embodiments, the processing module is used to satisfy at least one of the following and no repeated transmission is performed: the terminal does not perform repeated transmission when sending the Msg4 HARQ-ACK message; the second information is not received.

[0105] In combination with some embodiments of the fourth aspect, in some embodiments, the processing module determines the repetition transmission parameters of the dedicated PUCCH in the following manner: based on the downlink DCI sent by the network device, the repetition transmission parameters of the dedicated PUCCH are determined, the downlink DCI is used to schedule the dedicated PUCCH, and the downlink DCI carries the repetition transmission parameters corresponding to the dedicated PUCCH.

[0106] In combination with some embodiments of the fourth aspect, in some embodiments, the processing module is scrambled by the cell radio network temporary identifier C-RNTI in response to the cyclic redundancy check CRC of the downlink DCI, and / or the downlink DCI is a fallback format DCI, and at least one of the following methods is used to determine the repetition transmission parameters of the dedicated PUCCH based on the downlink DCI sent by the network device: based on the first field in the downlink DCI, the repetition transmission parameters of the dedicated PUCCH are determined, and the first field is the downlink allocation indication field DAI; based on the second field in the downlink DCI, the repetition transmission parameters of the dedicated PUCCH are determined, and the second field includes at least one of the following: modulation and coding scheme MCS field; transmit power control TPC field; PUCCH resource indication field PRI.

[0107] In combination with some embodiments of the fourth aspect, in some embodiments, the processing module is scrambled by C-RNTI in response to the CRC of the downlink DCI, and / or the downlink DCI is a non-fallback format DCI, and determines the repetition transmission parameters of the dedicated PUCCH based on the downlink DCI sent by the network device in at least one of the following ways: determining the repetition transmission parameters of the dedicated PUCCH based on the third field in the downlink DCI, the third field being a newly added field in the downlink DCI; determining the repetition transmission parameters of the dedicated PUCCH based on at least part of the bits of the second field in the downlink DCI, the second field including at least one of the following: modulation and coding scheme MCS field; transmission power control TPC field; PUCCH resource indication PRI field.

[0108] In combination with some embodiments of the fourth aspect, in some embodiments, the second field includes a PRI field, and the PRI field is used to indicate a dedicated PUCCH resource, and each dedicated PUCCH resource corresponds to a repetition transmission parameter.

[0109] In combination with some embodiments of the fourth aspect, in some embodiments, the first field or the second field indicates the repetition transmission parameter by means of a codepoint; or, the first field or the second field indicates the number of repetition transmissions of the dedicated PUCCH by indicating a numerical set index, and the numerical set index is determined based on the repetition parameter set carried by the second information.

[0110] In combination with some embodiments of the fourth aspect, in some embodiments, the processing module satisfies at least one of the following conditions and determines the repeated transmission parameters of the dedicated PUCCH based on the first field or the second field in the downlink DCI: sending a repeated transmission capability indication to the network device; sending a repeated transmission request to the network device; receiving second information sent by the network device, the second information including a bit for explicitly instructing the terminal to perform repeated transmission; receiving second information sent by the network device, the second information including the repeated transmission parameters.

[0111] In combination with some embodiments of the fourth aspect, in some embodiments, the repetition transmission parameter includes at least one of the following: the number of repetition transmissions; the set of repetition transmission numbers; the threshold value of the reference information receiving power RSRP, and the RSRP threshold value is used by the terminal to determine whether to perform repetition transmission.

[0112] According to a fifth aspect of an embodiment of the present disclosure, a network device is provided, including: a transceiver module, configured to receive a first physical uplink control channel PUCCH, wherein a transmission parameter of the first PUCCH is determined by a terminal.

[0113] In combination with some embodiments of the fifth aspect, in some embodiments, the transceiver module is further used to: send first information to the terminal, where the first information is used by the terminal to determine the transmission parameters of the first physical uplink control channel PUCCH.

[0114] In combination with some embodiments of the fifth aspect, in some embodiments, the transmission of the first PUCCH is located after Msg4 hybrid automatic repeat request confirmation HARQ-ACK; and / or, the transmission of the first PUCCH is located before the terminal sends the first signaling, and the first signaling includes at least one of the following: terminal capability information; terminal reconfiguration completion information.

[0115] In combination with some embodiments of the fifth aspect, in some embodiments, the first PUCCH is used to carry at least one of the following: a hybrid automatic repeat request confirmation HARQ-ACK message; a scheduling request SR message; and a channel state information CSI.

[0116] In combination with some embodiments of the fifth aspect, in some embodiments, the terminal does not expect the network device to configure the transmission parameters of the dedicated physical uplink control channel dedicated PUCCH to the terminal through Msg4, and the first PUCCH is a public PUCCH.

[0117] In combination with some embodiments of the fifth aspect, in some embodiments, the first PUCCH is a dedicated physical uplink control channel dedicated PUCCH, and the transmission parameters of the dedicated PUCCH are carried based on the random access message Msg4.

[0118] In combination with some embodiments of the fifth aspect, in some embodiments, the transceiver module is further used to: send second information to the network, where the second information is used to semi-statically configure the repeated transmission parameters of the dedicated PUCCH.

[0119] In combination with some embodiments of the fifth aspect, in some embodiments, the second information is carried based on at least one of the following: system message SIB; Msg4.

[0120] In combination with some embodiments of the fifth aspect, in some embodiments, the transceiver module is further used to: send a downlink DCI to the terminal, the downlink DCI is used to schedule the dedicated PUCCH, and the downlink DCI carries the repetition transmission parameters corresponding to the dedicated PUCCH.

[0121] In combination with some embodiments of the fifth aspect, in some embodiments, the cyclic redundancy check CRC of the downlink DCI is encrypted by the cell radio network temporary identifier C-RNTI, and / or the downlink DCI is a fallback format DCI, and the downlink DCI includes at least one of the following: a first field, the first field is used to determine the repetition transmission parameters of the dedicated PUCCH, and the first field is the downlink allocation indication field DAI; a second field, the second field is used to determine the repetition transmission parameters of the dedicated PUCCH, and the second field includes at least one of the following: a modulation and coding scheme MCS field; a transmit power control TPC field; and a PUCCH resource indication field PRI.

[0122] In combination with some embodiments of the fifth aspect, in some embodiments, the CRC of the downlink DCI is encrypted by C-RNTI, and / or the downlink DCI is a non-fallback format DCI, and the downlink DCI includes at least one of the following: a third field, the third field is used to determine the repetition transmission parameters of the dedicated PUCCH, and the third field is a newly added field in the downlink DCI; a second field, the second field is used to determine the repetition transmission parameters of the dedicated PUCCH, and the second field includes at least one of the following: a modulation and coding scheme MCS field; a transmit power control TPC field; and a PUCCH resource indication field PRI.

[0123] In combination with some embodiments of the fifth aspect, in some embodiments, the second field includes a PRI field, and the PRI field is used to indicate a dedicated PUCCH resource, and each dedicated PUCCH resource corresponds to a repetition transmission parameter.

[0124] In combination with some embodiments of the fifth aspect, in some embodiments, the first field or the second field indicates the repetition transmission parameter by means of a codepoint; or, the first field or the second field indicates the number of repetition transmissions of the dedicated PUCCH by indicating a numerical set index, and the numerical set index is determined based on the repetition parameter set carried by the second information.

[0125] In combination with some embodiments of the fifth aspect, in some embodiments, at least one of the following conditions is met, and the downlink DCI is used to determine the repeated transmission parameters of the dedicated PUCCH: receiving a repeated transmission capability indication sent by the terminal; receiving a repeated transmission request sent by the terminal; sending a second information to the terminal, wherein the second information includes a bit for explicitly instructing the terminal to perform repeated transmission; sending a second information to the terminal, wherein the second information includes the repeated transmission parameters.

[0126] In combination with some embodiments of the fifth aspect, in some embodiments, the repetition transmission parameter includes at least one of the following: the number of repetition transmissions; the set of repetition transmission numbers; the threshold value of the reference information receiving power RSRP, and the RSRP threshold value is used by the terminal to determine whether to perform repetition transmission.

[0127] According to a sixth aspect of an embodiment of the present disclosure, a terminal is provided, comprising: one or more processors; wherein the terminal is configured to execute the first aspect and any one of the communication methods in the first aspect.

[0128] According to a seventh aspect of an embodiment of the present disclosure, a network device is provided, comprising: one or more processors; wherein the network device is configured to execute the second aspect and any one of the communication methods in the second aspect.

[0129] According to the eighth aspect of an embodiment of the present disclosure, a communication system is provided, including a terminal and a network device, wherein the terminal is configured to implement the first aspect and any one of the communication methods in the first aspect, and the network device is configured to implement the second aspect and any one of the communication methods in the second aspect.

[0130] According to the ninth aspect of an embodiment of the present disclosure, a storage medium is provided, which stores instructions. When the instructions are executed on a communication device, the communication device executes a communication method such as the first aspect and any one of the first aspects or the second aspect and any one of the second aspects.

[0131] According to a tenth aspect of an embodiment of the present disclosure, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation manner of the first aspect or the second aspect.

[0132] According to an eleventh aspect of the embodiments of the present disclosure, the embodiments of the present disclosure propose a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first aspect or the second aspect.

[0133] According to a twelfth aspect of the embodiments of the present disclosure, the embodiments of the present disclosure provide a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first or second aspect.

[0134] It is understandable that the terminal, access network device, first network element, other network elements, core network device, communication system, storage medium, program product, computer program, chip, or chip system involved in each embodiment of the present disclosure are all used to perform the method proposed in the embodiment of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding method and will not be repeated here.

[0135] The present disclosure provides communication methods, devices, equipment, and storage media. In some embodiments, the terms "communication method," "information processing method," and "communication method" are interchangeable; the terms "communication device," "information processing device," and "communication device" are interchangeable; and the terms "information processing system," "communication system," and "communication system" are interchangeable.

[0136] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0137] In each embodiment of the present disclosure, unless otherwise specified or provided for, the terms and / or descriptions between the embodiments are consistent and may be referenced by each other. The technical environments in different embodiments may be combined to form new embodiments based on their inherent logical relationships.

[0138] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0139] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0140] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0141] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0142] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0143] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0144] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for example, if the description object is "information", then the "first information" and "the performance of each AI model" can be the same information or different information, and their contents can be the same or different.

[0145] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0146] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0147] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0148] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0149] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0150] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0151] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.

[0152] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0153] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0154] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0155] FIG1a is a schematic diagram showing a communication system architecture according to an embodiment of the present disclosure.

[0156] As shown in FIG. 1 a , a communication system 100 includes a terminal 101 and a network device 102 .

[0157] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0158] In some embodiments, the network device 102 may include at least one of an access network device and a core network device.

[0159] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0160] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0161] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0162] In some embodiments, a core network device may be a device including one or more network elements, or may be multiple devices or device groups, each including all or part of the one or more network elements. The network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0163] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0164] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1a, or a portion thereof, but are not limited thereto. The entities shown in FIG1a are illustrative only. The communication system may include all or part of the entities shown in FIG1a, or may include other entities other than those shown in FIG1a. The number and form of the entities may be arbitrary, and the entities may be physical or virtual. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0165] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0166] In some embodiments, when the network device configures a reference signal received power (RSRP) threshold for the terminal, and the measured RSRP is lower than the configured RSRP, the terminal supporting common PUCCH repeated transmission can report the capability of common PUCCH repeated transmission to the network device. For example, the capability can be reported through the reserved bit in the medium access control (MAC) subheader in Msg3. If the network device does not configure the RSRP threshold for the terminal, the terminal supporting common PUCCH repeated transmission can directly report the capability of common PUCCH repeated transmission to the network device. For example, the capability can be reported through the spare bit in the medium access control (MAC) subheader in Msg3.

[0167] In some embodiments, the network device can configure the number of retransmissions to the terminal via a system information block (SIB). For example, candidate values ​​for the number of retransmissions can include {2, 4, 8}. If the terminal reports its UE capability to the network device, or sends a PUCCH retransmission request to the network device, the retransmissions configured by the network device can be performed subsequently.

[0168] In some embodiments, the network device may configure a set of transmission times to the terminal through the SIB. For example, the set of transmission times may be at least two values ​​among the candidate values ​​{2, 4, 8}. The index of the set of transmission times may be configured using the downlink assignment index (DAI) field in the downlink control information (DCI) in the fallback format, wherein the DCI is scrambled by the cyclic redundancy check (CRC) using a temporary cell-radio network temporary identifier (TC-RNTI). Table 1 is an exemplary table of DAI indicating the number of repeated transmissions. As shown in Table 1,

[0169] Table 1

[0170] In some embodiments, the subsequent common PUCCH after the terminal sends the Msg4 HARQ-ACK to the network device may share the same repetition transmission number indicated by the DAI field of the Msg4 DCI.

[0171] In some embodiments, a network device may configure dedicated PUCCH resources via Msg4 for transmission of uplink control information (UCI) such as HARQ-ACK after the terminal establishes an RRC connection and before the terminal reports the terminal capability message and sends the RRC reconfiguration message. For example, the dedicated PUCCH resource may be configured via a signaling in Msg4. For example, the signaling may be a masterCellGroup OCTET STRING (CONTAINING CellGroupConfig).

[0172] In some embodiments, FIG1b is a schematic diagram illustrating the interaction between a terminal and a network device according to an exemplary embodiment. The network device includes a gNB and an access and mobility management function (AMF). In step 1 of FIG1b , the terminal sends an RRC establishment request to the network device. For example, the RRC establishment request may include a cause value, and the terminal identifier may be a random value or a temporary mobile subscription identifier (TMSI). In step 2, the network device may configure the terminal for RRC establishment using Msg4. For example, the RRC establishment message may include signaling radio bearer (SRB) 1 related configuration. In step 3, the terminal sends an RRC establishment complete message to the network device. For example, the RRC establishment complete message may carry a non-access stratum (NAS) registration request. Between steps 2 and 3, or after step 3, the terminal may send a Msg4 HARQ-ACK message to the network device. Since Msg4 may include the dedicated PUCCH resource configured by the network device for the terminal, after the terminal sends the Msg4 HARQ-ACK message, until the terminal sends the RRC reconfiguration complete message to the network device in step 13 of Figure 1b, the dedicated PUCCH resource configured by the network device for transmission can be used. In Figure 1b, step 4 shows the gNB sending an initial UE message to the AMF. For example, the initial UE message may include the gNB identifier, the UE identifier, and the next generation application protocol (NGAP) identifier. Step 5 shows the sending and receiving of non-access stratum transport (downlink NAS transport) messages between the AMF and the terminal, such as the downlink NAS transport sent by the AMF to the terminal and the uplink NAS transport sent by the terminal to the AMF. Step 6 shows the AMF sending an initial context setup request message to the terminal. For example, this may include receiving a registration message.Step 7 indicates that the gNB sends an Initial Context Setup Request (SSC) command to the terminal. Step 8 indicates that the terminal sends a Security Mode Complete (SSC) message to the gNB. Step 9 indicates that the gNB sends a UE Capability Enquiry (UE Capability Enquiry) message to the terminal. Step 10 indicates that the terminal sends UE Capability Information (UE Capability Information) to the gNB. Step 11 indicates that the gNB sends a UE Radio Capability Info Indication (UE Radio Capability Info Indication) message to the AMF. Step 12 indicates that the gNB sends an RRC Reconfiguration (RRC Reconfiguration) message to the terminal, such as configuring an even-even SRB2 or receiving a registration message. Step 13 indicates that the terminal sends an RRC Reconfiguration Complete (RRC Reconfiguration Complete) message to the gNB. Step 14 indicates that the gNB sends an Initial Context Setup Response (Initial Context Setup Response) to the AMF. Step 15 indicates that the AMF sends a Packet Data Unit Session Resource Setup Request (PDU Session Resource Setup Request) to the gNB. For example, this may include a Packet Data Unit (PDU) Session Establishment Accept (SES). Step 16 indicates that the gNB sends an RRC reconfiguration message to the terminal. For example, this may include data radio bearer (DRB) configuration and NAS message transparent transmission. Step 17 indicates that the terminal sends an RRC reconfiguration complete message to the gNB. Step 18 indicates that the gNB sends a PDU session resource setup response to the AMF.

[0173] In some embodiments, PUCCH formats include PUCCH format 0 and PUCCH format 1, which are used to carry HARQ-ACK and scheduling requests (SRs), and cannot be used for channel state information (CSI) feedback. CSI feedback can only be carried via PUCCH format 2, PUCCH format 3, or PUCCH format 4. PUCCH format 2, PUCCH format 3, or PUCCH format 4 are mandatory capabilities for terminal capability signaling. For example, the gNB cannot configure the relevant features of mandatory capability signaling before the terminal capabilities are reported.

[0174] FIG2a is a schematic diagram illustrating an interaction of a communication method according to an embodiment of the present disclosure. As shown in FIG2a , the present disclosure embodiment relates to a communication method for use in a communication system 100, the method comprising:

[0175] Step S2101 , the network device 102 sends first information to the terminal 101 .

[0176] In some embodiments, the terminal 101 receives first information sent by the network device 102 .

[0177] In some embodiments, the first information is used by the terminal to determine the transmission parameters of the first physical uplink control channel (PUCCH). The transmission of the first PUCCH is located after the Msg4 hybrid automatic repeat request confirmation HARQ-ACK, and / or the transmission of the first PUCCH is located before the terminal sends the first signaling, and the first signaling includes at least one of the following: terminal capability information (UE capability signaling); terminal reconfiguration completion information (RRCReconfigurationComplete). That is, the transmission of the first PUCCH before the terminal sends the first signaling can be before the terminal sends the terminal capability information (UE capability signaling) or before the terminal sends the reconfiguration completion information (RRCReconfigurationComplete). For example, the transmission of the first PUCCH can be at all times after the terminal sends the Msg4 HARQ-ACK message to the network device. For another example, the transmission of the first PUCCH can be at all times before the terminal sends the UE capability signaling. For another example, the transmission of the first PUCCH can be at all times before the terminal sends the RRCReconfigurationComplete. For another example, the first PUCCH transmission may be after the terminal sends the Msg4 HARQ-ACK message to the network device and before the terminal sends the UE capability signaling. For another example, the first PUCCH transmission may be after the terminal sends the Msg4 HARQ-ACK message to the network device and before the terminal sends the RRCReconfigurationComplete message.

[0178] In some embodiments, the transmission of the first PUCCH is located after the Msg4 HARQ-ACK, which means that the terminal sends the first PUCCH for uplink transmission after sending the Msg4 HARQ-ACK message.

[0179] In some embodiments, the first PUCCH may be used to carry at least one of the following: a HARQ-ACK message; a scheduling request (SR) message; or channel state information (CSI). The Msg4 HARQ-ACK message may indicate feedback from the terminal to Msg4 sent by the network device. The HARQ-ACK message transmitted by the first PUCCH may indicate that after the terminal sends the Msg4 HARQ-ACK message, the network device sends other downlink messages to the terminal, and the terminal provides feedback on the other downlink messages.

[0180] In some embodiments, the terminal does not expect the network device to configure dedicated PUCCH transmission parameters to the terminal via Msg4. When the terminal does not expect the network device to configure dedicated PUCCH transmission parameters to the terminal via Msg4, the network device can configure dedicated PUCCH transmission parameters for the terminal. The terminal can transmit based on the transmission parameters of the common PUCCH, that is, the first PUCCH is the common PUCCH.

[0181] In some embodiments, the first PUCCH is a dedicated PUCCH.

[0182] In some embodiments, the name of the first information is not limited, and it can be, for example, "instruction information", "configuration information", etc.

[0183] Step S2102: Terminal 101 determines the transmission parameters of the first PUCCH.

[0184] In some embodiments, the terminal may determine the transmission parameters of the first PUCCH in at least one of the following ways: determining the transmission parameters of the first PUCCH based on provisions in the protocol; receiving first information, the first information being used by the terminal to determine the transmission parameters of the first PUCCH.

[0185] In some embodiments, the terminal may receive the first information and determine the transmission parameters of the first PUCCH according to the first information.

[0186] In some embodiments, the terminal may determine the transmission parameters of the first PUCCH based on the provisions of the protocol. For example, the terminal may not receive the first information, or when the terminal does not receive the first information, the terminal may determine the transmission parameters of the first PUCCH based on the provisions of the protocol. For another example, even if the terminal receives the first information, the terminal may still determine the transmission parameters of the first PUCCH based on the provisions of the protocol.

[0187] Step S2103 , the network device 102 sends second information to the terminal 101 .

[0188] In some embodiments, the terminal 101 may receive second information sent by the network device 102 .

[0189] In some embodiments, the second information is used to semi-statically configure repetition transmission parameters of a dedicated PUCCH.

[0190] In some embodiments, the terminal may determine the repetition transmission parameter of the dedicated PUCCH after receiving the second information sent by the network device.

[0191] In some embodiments, the second information may be carried based on at least one of the following: a system message SIB; Msg4.

[0192] In some embodiments, the second information may be carried based on a SIB, and the terminal may determine the repetition transmission parameter of the dedicated PUCCH based on the SIB.

[0193] In some embodiments, the second information may be carried based on Msg4, and the terminal may determine the repetition transmission parameter of the dedicated PUCCH based on Msg4.

[0194] In some embodiments, the second information may be carried based on the SIB and Msg4. That is, the SIB and Msg4 respectively carry the second information, and the terminal may determine the repetition transmission parameter of the dedicated PUCCH based on the SIB or Msg4. For example, the repetition transmission parameter of the dedicated PUCCH may be determined preferentially based on Msg4.

[0195] In some embodiments, the name of the second information is not limited, and it can be, for example, "configuration information", "instruction information", etc.

[0196] In step S2104, the terminal 101 determines the repetition transmission parameter of the first PUCCH.

[0197] In some embodiments, when the first PUCCH is a common PUCCH, the repetition transmission parameter of the common PUCCH may be configured by sending a Msg4 HARQ-ACK message to the network device at the end, and then there is no need to configure the repetition transmission parameter for the first PUCCH. The repetition transmission parameter of the common PUCCH may also be not configured by sending a Msg4 HARQ-ACK message to the network device at the end, and the terminal can determine the repetition transmission parameter of the first PUCCH.

[0198] In some embodiments, the first PUCCH is a dedicated PUCCH.

[0199] In some embodiments, when the first PUCCH is a dedicated PUCCH, the terminal may determine a repetition transmission parameter of the first PUCCH.

[0200] In some embodiments, the repetition transmission parameter may include at least one of the following: the number of repetition transmissions; a set of repetition transmission numbers; an RSRP threshold value, where the RSRP threshold value is used by the terminal to determine whether to perform repetition transmission.

[0201] In some embodiments, when the repetition transmission parameter includes a repetition transmission count, the terminal may perform repetition transmission based on the repetition transmission count. When the repetition transmission parameter is a repetition transmission parameter set, the terminal may determine any repetition transmission count from the repetition transmission parameter set for repetition transmission. Alternatively, the terminal may receive an instruction from a network device and, based on the instruction, determine to use a repetition transmission parameter from the repetition transmission set.

[0202] In some embodiments, an RSRP threshold value is used by a terminal to determine whether to perform repeated transmissions. For example, when a network device configures an RSRP value for a terminal, the terminal determines to perform repeated transmissions when the RSRP measured value is lower than the RSRP threshold value. When the RSRP measured value is higher than the RSRP threshold value, the terminal determines not to perform repeated transmissions. The RSRP measured value represents the RSRP value measured by the terminal.

[0203] In some embodiments, when the first PUCCH is a dedicated PUCCH, the terminal may determine that the repetition transmission parameter of the dedicated PUCCH is the same as the repetition transmission parameter used by the terminal to send the Msg4 HARQ-ACK message.

[0204] In some embodiments, the repetition transmission parameter used by the terminal to send the Msg4 HARQ-ACK message can be, for example, indicated by the gNB through the DAI field in the DCI, or it can be a separate value configured by system information block 1 (SIB1).

[0205] In some embodiments, the terminal may determine the repetition transmission parameter of the dedicated PUCCH based on second information sent by the network device, where the second information is used to semi-statically configure the repetition transmission parameter of the dedicated PUCCH.

[0206] In some embodiments, determining the repetition transmission parameters of the dedicated PUCCH satisfies at least one of the following priority relationships: determining the repetition transmission parameters of the dedicated PUCCH based on Msg4 takes precedence over determining the repetition transmission parameters of the dedicated PUCCH based on SIB; determining the repetition transmission parameters of the dedicated PUCCH based on SIB takes precedence over determining that the repetition transmission parameters of the dedicated PUCCH are the same as the repetition transmission parameters used by the terminal to send the Msg4 HARQ-ACK message.

[0207] In some embodiments, when the network device does not send the second information to the terminal, the terminal may determine that the repetition transmission parameter of the dedicated PUCCH is the same as the repetition transmission parameter used by the terminal to send the Msg4 HARQ-ACK message. When the network device sends the second information to the terminal, and the second information is carried based on Msg4, the repetition transmission parameter of the dedicated PUCCH may be determined based on Msg4. When the network device sends the second information to the terminal, and the second information is carried based on SIB, the repetition transmission parameter of the dedicated PUCCH may be determined based on SIB. When the network device sends the second information to the terminal, and both Msg4 and SIB carry the second information, the terminal may preferentially determine the repetition transmission parameter of the dedicated PUCCH based on Msg4.

[0208] In some embodiments, when the network device sends the second information to the terminal, and the second information is carried based on the SIB, it can also be determined that the repetition transmission parameter of the dedicated PUCCH is the same as the repetition transmission parameter used by the terminal to send the Msg4 HARQ-ACK message.

[0209] In some embodiments, repeated transmission is performed based on the repeated transmission parameter when at least one of the following conditions is met: the terminal sends a repeated transmission capability indication to the network device; the terminal sends a repeated transmission request to the network device.

[0210] In some embodiments, when a terminal sends a retransmission capability indication to a network device, that is, notifies the network device that the terminal has the capability to perform retransmission, the terminal may perform retransmission based on the determined retransmission parameters. For example, retransmission may be performed based on the common PUCCH. In another example, retransmission may be performed based on the dedicated PUCCH.

[0211] In some embodiments, when a terminal sends a repeat transmission request to a network device, it implicitly indicates that the terminal has the capability to perform repeat transmission and requests repeat transmission. The terminal may perform repeat transmission based on the determined repeat transmission parameters. For example, repeat transmission may be performed based on the common PUCCH. In another example, repeat transmission may be performed based on the dedicated PUCCH.

[0212] In some embodiments, based on the same or different methods, the repetition transmission parameters of the dedicated PUCCH scheduled by the downlink control information DCI in the fallback format and the repetition transmission parameters of the dedicated PUCCH scheduled by the DCI in the non-fallback format are determined; the repetition transmission parameters corresponding to the dedicated PUCCH scheduled by the DCI in the fallback format are the same as or different from the repetition transmission parameters corresponding to the dedicated PUCCH scheduled by the DCI in the non-fallback format.

[0213] For example, for the dedicated PUCCH scheduled by the DCI in the fallback format and the dedicated PUCCH scheduled by the DCI in the non-fallback format, it can be determined that the repetition transmission parameters of the two dedicated PUCCHs are the same as the repetition transmission parameters used by the terminal to send the Msg4 HARQ-ACK message. Or the repetition transmission parameters of the two dedicated PUCCHs can be determined based on Msg4, or the repetition transmission parameters of the two dedicated PUCCHs can be determined based on SIB. For another example, for the DCI in the non-fallback format, the repetition transmission parameters of the dedicated PUCCH can be determined based on Msg4. The repetition transmission parameters determined by the two methods can be the same or different. For another example, the repetition transmission parameters for the dedicated PUCCH scheduled by the DCI in the fallback format can be determined based on Msg4, and the repetition transmission parameters for the dedicated PUCCH scheduled by the DCI in the non-fallback format can be determined based on SIB. This disclosure does not list them one by one, but it is understandable that the dedicated PUCCH scheduled by the fallback format DCI and the dedicated PUCCH scheduled by the non-fallback format DCI can determine the dedicated PUCCH retransmission parameters based on any same or different methods, and this disclosure does not limit them.

[0214] In some embodiments, repeated transmission is not performed if at least one of the following is satisfied: the terminal does not perform repeated transmission when sending the Msg4 HARQ-ACK message; the second information is not received.

[0215] In some embodiments, when a terminal does not perform repeated transmission when sending a Msg4 HARQ-ACK message, the terminal determines not to perform repeated transmission. The case where the terminal does not perform repeated transmission when sending a Msg4 HARQ-ACK message may be, for example, when the terminal uses a common PUCCH to send the Msg4 HARQ-ACK message and the terminal does not support repeated transmission of the common PUCCH. Alternatively, when the terminal supports repeated transmission of the common PUCCH but the RSRP measurement value is greater than the RSRP threshold corresponding to the common PUCCH, the terminal does not perform repeated transmission when sending the Msg4 HARQ-ACK message.

[0216] In some embodiments, when the terminal does not perform repeated transmission when sending the Msg4 HARQ-ACK message, but the network device configures the common PUCCH repeated transmission parameters for the terminal, the terminal can determine the dedicated PUCCH repeated transmission parameters based on the common PUCCH repeated transmission parameters configured by the network device, and perform repeated transmission based on the repeated transmission parameters.

[0217] In some embodiments, when the terminal does not receive the second information, retransmission is not performed.

[0218] In some embodiments, when the terminal sends a Msg4 HARQ-ACK message, no retransmission is performed and no second information is received, no retransmission is performed. Alternatively, when the terminal does not receive a common PUCCH retransmission parameter configured by the network device and does not receive the second information, no retransmission is performed.

[0219] Step S2105: Send the first PUCCH based on the transmission parameters of the first PUCCH.

[0220] In some embodiments, when the first PUCCH is a common PUCCH, transmission may be performed based on the transmission parameters of the commom PUCCH; when the first PUCCH is a dedicated PUCCH, transmission may be performed based on the transmission parameters of the dedicated PUCCH.

[0221] In some embodiments, a repetition transmission parameter of the first PUCCH may be determined. For detailed implementation, reference may be made to the implementation of step S2103 and step S2104, which will not be described in detail herein.

[0222] In some embodiments, repeated transmission can be performed based on the determined transmission parameters of the first PUCCH and the determined repeated transmission parameters of the first PUCCH. The transmission parameters of the first PUCCH can be understood as various parameters used to send the first PUCCH, including but not limited to the frequency domain and time domain for sending the first PUCCH. The transmission parameters of the first PUCCH can also be understood as the resources for the network device to configure the first PUCCH to the terminal. The repeated transmission parameters of the first PUCCH are used for repeated transmission to achieve coverage enhancement. For example, the repeated transmission parameters of the first PUCCH may include the number of repeated transmissions, the set of repeated transmission times, the threshold value of RSRP, etc.

[0223] The communication method involved in the embodiment of the present disclosure may include at least one of steps S2101 to S2105. For example, steps S2102 and S2105 may be implemented as independent embodiments, and step S2104 may be implemented as an independent embodiment, but is not limited thereto.

[0224] In some embodiments, step S2101 and step S2103 may be executed in an interchanged order or simultaneously.

[0225] In some embodiments, step S2101 and step S2103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0226] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 a .

[0227] FIG2b is a schematic diagram illustrating an interaction of a communication method according to an embodiment of the present disclosure. As shown in FIG2b , the present disclosure embodiment relates to a communication method for use in a communication system 100, the method comprising:

[0228] Step S2201: The network device 102 sends first information to the terminal 101.

[0229] In some embodiments, the terminal 101 receives first information sent by the network device 102 .

[0230] In some embodiments, the first information is used by the terminal to determine transmission parameters of a first physical uplink control channel (PUCCH). The first PUCCH is transmitted after a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) message (Mg4), and / or the first PUCCH is transmitted before the terminal sends a first signaling message, the first signaling message including at least one of the following: UE capability signaling; and RRCReconfigurationComplete message.

[0231] The specific implementation of step S2201 can refer to the implementation of step S2101, and this disclosure will not go into details here.

[0232] Step S2202: Terminal 101 determines the transmission parameters of the first PUCCH.

[0233] In some embodiments, the terminal may determine the transmission parameters of the first PUCCH in at least one of the following ways: determining the transmission parameters of the first PUCCH based on provisions in the protocol; receiving first information, the first information being used by the terminal to determine the transmission parameters of the first PUCCH.

[0234] In some embodiments, the terminal may receive the first information and determine the transmission parameters of the first PUCCH according to the first information.

[0235] In some embodiments, the terminal may determine the transmission parameters of the first PUCCH based on the provisions of the protocol. For example, the terminal may not receive the first information, or when the terminal does not receive the first information, the terminal may determine the transmission parameters of the first PUCCH based on the provisions of the protocol. For another example, even if the terminal receives the first information, the terminal may still determine the transmission parameters of the first PUCCH based on the provisions of the protocol.

[0236] Step S2203 , the network device 102 sends a downlink DCI to the terminal 101 .

[0237] In some embodiments, the terminal 101 receives a downlink DCI sent by a network device. The downlink DCI is used to schedule a dedicated PUCCH, and the downlink DCI carries a repetition transmission parameter corresponding to the dedicated PUCCH.

[0238] In some embodiments, the terminal receives a downlink DCI and may determine a repetition transmission parameter based on the downlink DCI.

[0239] In step S2204, the terminal 101 determines the repetition transmission parameter of the first PUCCH.

[0240] In some embodiments, a terminal receives a downlink DCI and may determine a repetition parameter based on the downlink DCI, for example, by indicating the number of repetitions through the downlink DCI, or determining the number of repetitions in a set of repetition times configured by the terminal through the downlink DCI.

[0241] In some embodiments, the terminal receives a downlink DCI and, in response to the CRC of the downlink DCI being scrambled using a cell radio network temporary identifier (C-RNTI), and / or the downlink DCI being a fallback format DCI, determines the repetition transmission parameter of the dedicated PUCCH based on the downlink DCI sent by the network device in at least one of the following ways: determining the repetition transmission parameter of the dedicated PUCCH based on a first field in the downlink DCI, where the first field is a downlink allocation indication field DAI; determining the repetition transmission parameter of the dedicated PUCCH based on a second field in the downlink DCI, where the second field includes at least one of the following: a modulation and coding scheme (MCS) field; a transmit power control (TPC) field; and a PUCCH resource indicator (PRI) field.

[0242] In some embodiments, the repetition transmission parameter may be indicated based on the DAI field in the DCI.

[0243] In some embodiments, the repetition parameter of the dedicated PUCCH may be determined based on one or more bits in the MCS field in the DCI. The repetition parameter of the dedicated PUCCH may be determined based on one or more bits in the TPC field in the DCI. The repetition parameter of the dedicated PUCCH may also be determined by one or more bits in the MCS field and one or more bits in the TPC field. The repetition parameter of the dedicated PUCCH may also be determined based on one or more bits in the PRI field.

[0244] In some embodiments, the terminal receives a downlink DCI and, in response to the CRC of the downlink DCI being scrambled through the C-RNTI, and / or the downlink DCI being a non-fallback format DCI, determines the repetition transmission parameters of the dedicated PUCCH based on the downlink DCI sent by the network device in at least one of the following ways: determining the repetition transmission parameters of the dedicated PUCCH based on the third field in the downlink DCI, where the third field is a newly added field in the downlink DCI; determining the repetition transmission parameters of the dedicated PUCCH based on at least part of the bits of the second field in the downlink DCI, where the second field includes at least one of the following: an MCS field; a TPC field; or a PRI field.

[0245] In some embodiments, a new field may be added to the downlink DCI, and the repetition transmission parameter of the dedicated PUCCH may be determined based on the new field. For example, the new field may be specifically used to determine the repetition transmission parameter of the dedicated PUCCH.

[0246] In some embodiments, the repetition parameter of the dedicated PUCCH may be determined based on one or more bits in the MCS field in the DCI. The repetition parameter of the dedicated PUCCH may be determined based on one or more bits in the TPC field in the DCI. The repetition parameter of the dedicated PUCCH may also be determined by one or more bits in the MCS field and one or more bits in the TPC field. The repetition parameter of the dedicated PUCCH may also be determined based on one or more bits in the PRI field.

[0247] In some embodiments, in response to the CRC of the downlink DCI being encrypted by the C-RNTI, and / or the downlink DCI being a fallback format DCI, and / or the downlink DCI being a non-fallback format DCI, the second field includes a PRI field, and the PRI field is used to indicate a dedicated PUCCH resource, and each dedicated PUCCH resource corresponds to a repetition transmission parameter.

[0248] In some embodiments, the PRI field may be used to indicate dedicated PUCCH resources, and each dedicated PUCCH resource corresponds to a repetition transmission parameter, so as to indirectly indicate that the dedicated PUCCH resource corresponds to the repetition transmission parameter by indicating the dedicated PUCCH resource.

[0249] In some embodiments, the first field or the second field indicates a repetition transmission parameter by means of a codepoint; or, the first field or the second field indicates the number of repetition transmissions of a dedicated PUCCH by indicating a numerical set index, and the numerical set index is determined based on a repetition parameter set carried by a third information carrier.

[0250] In some embodiments, the first field or the second field may indicate a repetition parameter through a codepoint. For example, the number of repetition transmissions may be indicated through a codepoint.

[0251] In some embodiments, the first field or the second field indicates the number of repeated transmissions of the dedicated PUCCH by indicating a numerical set index. The numerical set index is determined based on a repetition parameter set carried by third information. That is, the network device can configure a set of repeated transmission times for the terminal via the third information, and can indicate the numerical set index via the first field or the second field in the downlink DCI. The numerical set index is used by the terminal to determine the number of repeated transmissions in the set of repeated transmission times, and the terminal can perform repeated transmissions based on the determined number of repeated transmissions.

[0252] In some embodiments, at least one of the following conditions is met, and the retransmission parameters of the dedicated PUCCH are determined based on the first field or the second field in the downlink DCI: sending a retransmission capability indication to the network device; sending a retransmission request to the network device; receiving third information sent by the network device, the third information including a bit for explicitly instructing the terminal to perform retransmission; receiving third information sent by the network device, the third information including a retransmission parameter.

[0253] In some embodiments, the first or second field in the DCI may or may not be used to indicate the number of dedicated PUCCH retransmissions. Taking the PRI field as an example, the PRI field may be used only to indicate PUCCH resources and not to indicate the number of dedicated PUCCH retransmissions. Alternatively, the PRI field may be used to indicate both PUCCH resources and the number of dedicated PUCCH retransmissions. Therefore, when conditions are met, the dedicated PUCCH retransmission parameter may be determined based on the first or second field in the downlink DCI.

[0254] For example, after sending a retransmission capability indication to the network device, the retransmission parameters of the dedicated PUCCH can be determined based on the first field or the second field in the downlink DCI. After receiving the retransmission capability indication sent by the terminal, the network device uses the first field or the second field in the downlink DCI to indicate the retransmission parameters of the dedicated PUCCH. For another example, after sending a retransmission request to the network device, the retransmission parameters of the dedicated PUCCH can be determined based on the first field or the second field in the downlink DCI. After receiving the retransmission request sent by the terminal, the network device uses the first field or the second field in the downlink DCI to indicate the retransmission parameters of the dedicated PUCCH. For another example, when receiving third information sent by the network device and the third information includes a bit for explicitly instructing the terminal to perform retransmission, the retransmission parameters of the dedicated PUCCH can be determined based on the first field or the second field in the downlink DCI. When the third information includes a bit for explicitly instructing the terminal to perform repeated transmission, it can be determined that the network device supports repeated transmission of the terminal's dedicated PUCCH. Then, when a downlink DCI is subsequently received, the repeated transmission parameters of the dedicated PUCCH can be determined based on the first field or the second field in the downlink DCI. For another example, the third information sent by the network device can be received, and the third information includes repeated transmission parameters, and it can be determined that the network device supports repeated transmission of the terminal's dedicated PUCCH. Then, when a downlink DCI is subsequently received, the repeated transmission parameters of the dedicated PUCCH can be determined based on the first field or the second field in the downlink DCI.

[0255] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0256] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0257] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", etc. can be used interchangeably.

[0258] Step S2205: Send the first PUCCH based on the transmission parameters of the first PUCCH.

[0259] In some embodiments, when the first PUCCH is a common PUCCH, transmission may be performed based on the transmission parameters of the commom PUCCH; when the first PUCCH is a dedicated PUCCH, transmission may be performed based on the transmission parameters of the dedicated PUCCH.

[0260] The specific implementation of step S2205 can refer to the implementation of step S2105, and this disclosure will not go into details here.

[0261] The communication method involved in the embodiment of the present disclosure may include at least one of steps S2201 to S2205. For example, steps S2102 and S2205 may be implemented as independent embodiments, and step S2104 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0262] In some embodiments, step S2201 and step S2203 may be executed in an interchangeable order or simultaneously.

[0263] In some embodiments, step S2201 and step S2203 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0264] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 b .

[0265] FIG3a is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3a, the embodiment of the present disclosure relates to a communication method, which is executed by terminal 101 and includes:

[0266] Step S3101, obtain first information.

[0267] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0268] In some embodiments, the terminal 101 receives the first information sent by the network device 102, but is not limited thereto and may also receive the first information sent by other entities.

[0269] In some embodiments, terminal 101 obtains first information specified by a protocol.

[0270] In some embodiments, terminal 101 obtains the first information from upper layer(s).

[0271] In some embodiments, the terminal 101 performs processing to obtain the first information.

[0272] In some embodiments, step S3101 is omitted, and the terminal 101 autonomously implements the function indicated by the first information, or the above function is default or by default.

[0273] Step S3102: Determine the transmission parameters of the first PUCCH.

[0274] The optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0275] Step S3103, obtain the second information.

[0276] The optional implementation of step S3103 can refer to the optional implementation of step S2103 in Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0277] In some embodiments, the terminal 101 receives the second information sent by the network device 102, but is not limited thereto and may also receive the second information sent by other entities.

[0278] In some embodiments, terminal 101 obtains second information specified by the protocol.

[0279] In some embodiments, terminal 101 obtains the second information from upper layer(s).

[0280] In some embodiments, terminal 101 performs processing to obtain the second information.

[0281] In some embodiments, step S3103 is omitted, and the terminal 101 autonomously implements the function indicated by the second information, or the above function is default or by default.

[0282] Step S3104: determine the repetition transmission parameter of the first PUCCH.

[0283] The optional implementation of step S3104 can refer to the optional implementation of step S2104 in Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0284] Step S3105: Send the first PUCCH based on the transmission parameters of the first PUCCH.

[0285] The optional implementation of step S3105 can refer to the optional implementation of step S2105 in Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0286] In some embodiments, the terminal 101 sends the first PUCCH to the network device 102, but is not limited thereto and may also send the first PUCCH to other entities.

[0287] The communication method involved in the embodiment of the present disclosure may include at least one of steps S3101 to S3105. For example, steps S3102 and S3105 may be implemented as independent embodiments, and step S3104 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0288] In some embodiments, step S3101 and step S3103 may be executed in an interchangeable order or simultaneously. In some embodiments, step S3101 and step S3103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0289] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 3 a .

[0290] FIG3b is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3b, the present disclosure embodiment relates to a communication method, which is executed by terminal 101 and includes:

[0291] Step S3201, obtain first information.

[0292] The optional implementation of step S3201 can refer to the optional implementation of step S2201 in Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0293] In some embodiments, the terminal 101 receives the first information sent by the network device 102, but is not limited thereto and may also receive the first information sent by other entities.

[0294] In some embodiments, terminal 101 obtains first information specified by a protocol.

[0295] In some embodiments, terminal 101 obtains the first information from upper layer(s).

[0296] In some embodiments, the terminal 101 performs processing to obtain the first information.

[0297] In some embodiments, step S3201 is omitted, and the terminal 101 autonomously implements the function indicated by the first information, or the above function is default or by default.

[0298] Step S3202: Determine the transmission parameters of the first PUCCH.

[0299] The optional implementation of step S3202 can refer to the optional implementation of step S2202 in Figure 2b and other related parts in the embodiment involved in Figure 2b, which will not be repeated here.

[0300] Step S3203: Obtain downlink DCI.

[0301] The optional implementation of step S3203 can refer to the optional implementation of step S2203 in Figure 2b and other related parts in the embodiment involved in Figure 2b, which will not be repeated here.

[0302] In some embodiments, the terminal 101 receives downlink DCI sent by the network device 102, but is not limited thereto and may also receive downlink DCI sent by other entities.

[0303] In some embodiments, the terminal 101 obtains the downlink DCI specified by the protocol.

[0304] In some embodiments, the terminal 101 obtains downlink DCI from upper layer(s).

[0305] In some embodiments, the terminal 101 performs processing to obtain downlink DCI.

[0306] In some embodiments, step S3202 is omitted, and the terminal 101 autonomously implements the function indicated by the downlink DCI, or the above function is default or by default.

[0307] Step S3204: determine the repetition transmission parameter of the first PUCCH.

[0308] The optional implementation of step S3204 can refer to the optional implementation of step S2204 in Figure 2b and other related parts in the embodiment involved in Figure 2b, which will not be repeated here.

[0309] Step S3205: Send the first PUCCH based on the transmission parameters of the first PUCCH.

[0310] The optional implementation of step S3205 can refer to the optional implementation of step S2105 in Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0311] In some embodiments, the terminal 101 sends the first PUCCH to the network device 102, but is not limited thereto and may also send the first PUCCH to other entities.

[0312] The communication method involved in the embodiment of the present disclosure may include at least one of steps S3201 to S3205. For example, steps S3202 and S3205 may be implemented as independent embodiments, and step S3204 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0313] In some embodiments, step S3201 and step S3203 may be executed in an interchanged order or simultaneously.

[0314] In some embodiments, step S3201 and step S3203 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0315] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 3 b .

[0316] FIG3c is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3c, the embodiment of the present disclosure relates to a communication method, which is executed by terminal 101 and includes:

[0317] Step S3301: Determine the transmission parameters of the first PUCCH.

[0318] The optional implementation of step S3301 can refer to the optional implementation of step S2102 in Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0319] Step S3302: Send the first PUCCH based on the transmission parameters of the first PUCCH.

[0320] The optional implementation of step S3302 can refer to the optional implementation of step S2105 in Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0321] In some embodiments, the terminal 101 sends the first PUCCH to the network device 102, but is not limited thereto and may also send the first PUCCH to other entities.

[0322] In some embodiments, the transmission parameters of the first PUCCH are determined by at least one of the following methods: determining the transmission parameters of the first PUCCH based on provisions in the protocol; receiving first information, where the first information is used by the terminal to determine the transmission parameters of the first PUCCH.

[0323] In some embodiments, the transmission of the first PUCCH is located after Msg4 hybrid automatic repeat request confirmation HARQ-ACK; and / or, the transmission of the first PUCCH is located before the terminal sends the first signaling, and the first signaling includes at least one of the following: terminal capability information; terminal reconfiguration completion information.

[0324] In some embodiments, the first PUCCH is used to carry at least one of the following: a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, a scheduling request (SR) message, and channel state information (CSI).

[0325] In some embodiments, the terminal does not expect the network device to configure transmission parameters of the dedicated physical uplink control channel dedicated PUCCH to the terminal through Msg4, and the first PUCCH is a common PUCCH.

[0326] In some embodiments, the first PUCCH is a dedicated physical uplink control channel (PUCCH), and transmission parameters of the dedicated PUCCH are carried based on the random access message Msg4.

[0327] In some embodiments, a repetition transmission parameter of the first PUCCH is determined, and the first PUCCH is repetitively transmitted according to the repetition transmission parameter.

[0328] In some embodiments, the repetition transmission parameter of the dedicated PUCCH is determined in the following manner: the repetition transmission parameter of the dedicated PUCCH is determined to be the same as the repetition transmission parameter used by the terminal to send the Msg4 HARQ-ACK message.

[0329] In some embodiments, the repetition transmission parameter of the dedicated PUCCH is determined in the following manner: the repetition transmission parameter of the dedicated PUCCH is determined based on second information sent by the network device, where the second information is used to semi-statically configure the repetition transmission parameter of the dedicated PUCCH.

[0330] In some embodiments, the second information is carried based on at least one of the following: a system message SIB. Msg4.

[0331] In some embodiments, determining a repetition parameter for a dedicated PUCCH satisfies at least one of the following priority relationships: determining the repetition parameter for the dedicated PUCCH based on Msg4 takes precedence over determining the repetition parameter for the dedicated PUCCH based on the SIB. Determining the repetition parameter for the dedicated PUCCH based on the SIB takes precedence over determining that the repetition parameter for the dedicated PUCCH is the same as the repetition parameter used by the terminal to send the Msg4 HARQ-ACK message.

[0332] In some embodiments, if at least one of the following conditions is met, the terminal performs repeated transmission based on the repeated transmission parameter: the terminal sends a repeated transmission capability indication to the network device; the terminal sends a repeated transmission request to the network device.

[0333] In some embodiments, repetition parameters for a dedicated PUCCH scheduled by downlink control information DCI in a fallback format and repetition parameters for a dedicated PUCCH scheduled by DCI in a non-fallback format are determined based on the same or different methods. The repetition parameters corresponding to the dedicated PUCCH scheduled by the DCI in the fallback format are the same as or different from the repetition parameters corresponding to the dedicated PUCCH scheduled by the DCI in the non-fallback format.

[0334] In some embodiments, repeated transmission is not performed if at least one of the following is satisfied: the terminal does not perform repeated transmission when sending the Msg4 HARQ-ACK message; the second information is not received.

[0335] In some embodiments, the repetition transmission parameters of the dedicated PUCCH are determined as follows: the repetition transmission parameters of the dedicated PUCCH are determined based on the downlink DCI sent by the network device, the downlink DCI is used to schedule the dedicated PUCCH, and the downlink DCI carries the repetition transmission parameters corresponding to the dedicated PUCCH.

[0336] In some embodiments, in response to a cyclic redundancy check (CRC) of a downlink DCI being scrambled by a cell radio network temporary identifier (C-RNTI), and / or the downlink DCI being a fallback format DCI, at least one of the following methods is used to determine a repetition transmission parameter of a dedicated PUCCH based on the downlink DCI sent by a network device: determining the repetition transmission parameter of the dedicated PUCCH based on a first field in the downlink DCI, where the first field is a downlink allocation indication field (DAI). determining the repetition transmission parameter of the dedicated PUCCH based on at least part of the bits of a second field in the downlink DCI, where the second field includes at least one of the following: a modulation and coding scheme (MCS) field, a transmit power control (TPC) field, and a PUCCH resource indication field (PRI).

[0337] In some embodiments, in response to the CRC of the downlink DCI being scrambled by the C-RNTI, and / or the downlink DCI being a non-fallback format DCI, at least one of the following methods is used to determine the repetition transmission parameter of the dedicated PUCCH based on the downlink DCI sent by the network device: determining the repetition transmission parameter of the dedicated PUCCH based on a third field in the downlink DCI, where the third field is a newly added field in the downlink DCI. Determining the repetition transmission parameter of the dedicated PUCCH based on at least a portion of the bits of the second field in the downlink DCI, where the second field includes at least one of the following: a modulation and coding scheme MCS field; a transmission power control TPC field; and a PUCCH resource indication PRI field.

[0338] In some embodiments, the second field includes a PRI field, the PRI field is used to indicate a dedicated PUCCH resource, and each dedicated PUCCH resource corresponds to a repetition transmission parameter.

[0339] In some embodiments, the first field or the second field indicates the repetition parameter by means of a codepoint. Alternatively, the first field or the second field indicates the number of repetitions of the dedicated PUCCH by indicating a value set index, where the value set index is determined based on a repetition parameter set carried by the second information carrier.

[0340] In some embodiments, a retransmission parameter for a dedicated PUCCH is determined based on a first field or a second field in a downlink DCI, when at least one of the following conditions is met: sending a retransmission capability indication to a network device; sending a retransmission request to the network device; receiving second information sent by the network device, the second information including a bit for explicitly instructing a terminal to perform retransmission; or receiving second information sent by the network device, the second information including a retransmission parameter.

[0341] In some embodiments, the repetition transmission parameter includes at least one of the following: the number of repetition transmissions, the set of repetition transmissions, the threshold value of the reference signal received power (RSRP), and the threshold value of the RSRP used by the terminal to determine whether to perform repetition transmission.

[0342] FIG4a is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG4a, the embodiment of the present disclosure relates to a communication method, and the method includes:

[0343] Step S4101, sending the first information.

[0344] The optional implementation of step S4101 can refer to the optional implementation of step S2101 in Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0345] In some embodiments, the network device 102 sends the first information to the terminal 101, but is not limited thereto and may also send the first information to other entities.

[0346] Step S4102, sending the second information.

[0347] The optional implementation of step S4102 can refer to the optional implementation of step S2102 in Figure 2a and other related parts in the embodiment involved in Figure a2, which will not be repeated here.

[0348] In some embodiments, the network device 102 sends the second information to the terminal 101, but is not limited thereto and may also send the second information to other entities.

[0349] Step S4103, receiving the first PUCCH.

[0350] The optional implementation of step S4103 can refer to the optional implementation of step S2105 in Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0351] In some embodiments, the network device 102 receives the first PUCCH sent by the terminal 101, but is not limited thereto and may also receive the first PUCCH sent by other entities.

[0352] FIG4b is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG4b, the embodiment of the present disclosure relates to a communication method, and the method includes:

[0353] Step S4201, sending the first information.

[0354] The optional implementation of step S4201 can refer to the optional implementation of step S2201 in Figure 2b and other related parts in the embodiment involved in Figure 2b, which will not be repeated here.

[0355] In some embodiments, the network device 102 sends the first information to the terminal 101, but is not limited thereto and may also send the first information to other entities.

[0356] Step S4202: Send downlink DCI.

[0357] The optional implementation of step S4202 can refer to the optional implementation of step S2202 in Figure 2b and other related parts in the embodiment involved in Figure 2b, which will not be repeated here.

[0358] In some embodiments, the network device 102 sends downlink DCI to the terminal 101, but is not limited thereto and may also send downlink DCI to other entities.

[0359] Step S4203, receiving the first PUCCH.

[0360] The optional implementation of step S4203 can refer to the optional implementation of step S2105 in Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0361] In some embodiments, the network device 102 receives the first PUCCH sent by the terminal 101, but is not limited thereto and may also receive the first PUCCH sent by other entities.

[0362] Figure 4c is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 4c, the embodiment of the present disclosure relates to a communication method, which includes:

[0363] Step S4301, receiving the first PUCCH.

[0364] The optional implementation of step S4301 can refer to the optional implementation of step S2105 in Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0365] In some embodiments, the network device 102 receives the first PUCCH sent by the terminal 101, but is not limited thereto and may also receive the first PUCCH sent by other entities.

[0366] FIG5 is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG5 , the embodiment of the present disclosure relates to a communication method, and the method includes:

[0367] Step S5101: Terminal 101 determines the transmission parameters of the first PUCCH.

[0368] The optional implementation of step S5101 can be found in S2102 of FIG. 2 a and other related parts of the embodiment involved in FIG. 2 a , which will not be described in detail here.

[0369] In some embodiments, the above method may include the method of the above embodiments related to the communication system 100, the terminal 101, the network device 102, etc., which will not be repeated here.

[0370] Step S5102: Terminal 101 sends the first PUCCH based on the transmission parameters of the first PUCCH.

[0371] The optional implementation of step S5102 can be found in S2105 of FIG. 2 a and other related parts of the embodiment involved in FIG. 2 a , which will not be described in detail here.

[0372] In some embodiments, the above method may include the method of the above embodiments related to the communication system 100, the terminal 101, the network device 102, etc., which will not be repeated here.

[0373] Step S5103 , the network device 102 receives a first PUCCH.

[0374] The optional implementation of step S5103 can be found in S2105 of FIG. 2 a and other related parts of the embodiment involved in FIG. 2 a , which will not be described in detail here.

[0375] In some embodiments, the above method may include the method of the above embodiments related to the communication system 100, the terminal 101, the network device 102, etc., which will not be repeated here.

[0376] The present disclosure also provides a communication method as follows:

[0377] In some embodiments, the terminal does not expect the network side to configure the UE dedicated PUCCH resource through the RRC signaling carried by Msg4.

[0378] In some embodiments, at least one of the following repetition number determination methods is considered for determining the number of dedicated PUCCH repetitions:

[0379] 1) Use the same value as the Msg4 HARQ-ACK PUCCH repetition transmission parameter determined by the UE, which is configured by SIB1 or indicated by the DAI field in the Msg4 DCI.

[0380] 2) The individual repetition transmission parameters may be configured by at least one of the following signaling: SIB, RRC signaling carried by Msg4.

[0381] In some embodiments, if Msg4RRC configures a single repetition transmission parameter for a dedicated PUCCH, then when the terminal sends a dedicated PUCCH repetition request or a dedicated PUCCH repetition-related capability indication, that repetition transmission parameter is used. Otherwise, if the SIB configures a single repetition transmission parameter for a dedicated PUCCH repetition, then when the terminal sends a dedicated PUCCH repetition request or a dedicated PUCCH repetition-related capability indication, that repetition transmission parameter is used. Otherwise, if a single repetition transmission parameter is configured for a common PUCCH, or if the terminal determines the repetition transmission parameter via the DAI field in the Msg4 DCI, then when the terminal sends a dedicated PUCCH repetition request or a dedicated PUCCH repetition-related capability indication, that repetition transmission parameter is used. Otherwise, the terminal disables PUCCH repetition transmission.

[0382] In some embodiments, the PUCCHs scheduled by DCI format 1-0 and DCI format 1-1 may use the same or different repetition transmission parameters, and the same or different configuration methods.

[0383] In some embodiments, DCI format 1-0 may be a fallback format DCI. DCI format 1-1 may be a non-fallback format DCI.

[0384] 3) The PUCCH repetition transmission parameters are dynamically indicated by the gNB.

[0385] In some embodiments, for DCI formats 1-0 in which the C-RNTI scrambles the CRC, the PUCCH repetition transmission parameter is indicated by the DAI field. When the terminal sends a dedicated PUCCH repetition request or a dedicated PUCCH repetition-related capability indication, and / or configures dedicated PUCCH repetition transmission parameters, the DAI field in the DCI is used to indicate the repetition transmission parameters.

[0386] In some embodiments, for DCI format 1-0 in which the C-RNTI scrambles the CRC or DCI format 1-1 in which the C-RNTI scrambles the CRC, the PUCCH repetition transmission parameter may be represented by at least one of the following fields: A new field is introduced in non-fallback DCI to represent the dedicated PUCCH repetition transmission parameter. Existing fields are reused in DCI format 1-1, for example, at least some bits are used in the MCS field, or at least some bits are used in the TPC field, or at least some bits are used in the PRI field.

[0387] In some embodiments, when a dedicated PUCCH repetition transmission parameter set is configured, and / or when PUCCH dedicated PUCCH repetition is configured as available, and / or when the terminal sends a dedicated PUCCH repetition request or a dedicated PUCCH repetition-related capability indication, and / or when dedicated PUCCH repetition transmission parameters are configured, at least one of the above methods is used. The priority is the same as in the above embodiment 2).

[0388] In some embodiments, the repetition transmission parameter may be included in the TPC table, for example, by replacing certain rows in the TPC table, or configured together with the PUCCH resources through RRC signaling via Msg4.

[0389] In some embodiments, for PRI dynamic indication, if a PUCCH repetition request or PUCCH repetition-related UE capabilities are reported, the following method can also be optionally configured as dedicated PUCCH repetition: the number of PUCCH repetitions reconfigured by RRC, each PUCCH resource can be configured with a PUCCH repetition number, and the gNB dynamically indicates the PUCCH repetition number by dynamically indicating the PUCCH resource. The dynamic indication can be through DCI format 1-0 or DCI format 1-1.

[0390] In some embodiments, if the gNB is configured with UE capability reporting or PUCCH retransmission request or dedicated PUCCH repetition related parameters, at least one of the above methods is used. Otherwise, there is no new field in the DCI, or the existing fields in the DCI are interpreted as having existing uses.

[0391] FIG6a is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure. As shown in FIG6a, the terminal 6100 may include: a processing module 6101 for determining transmission parameters of a first physical uplink control channel (PUCCH); and a transceiver module 6102 for transmitting the first PUCCH based on the transmission parameters of the first PUCCH.

[0392] In some embodiments, the processing module 6101 determines the transmission parameters of the first PUCCH in at least one of the following ways: determining the transmission parameters of the first PUCCH based on provisions in a protocol; and receiving first information, where the first information is used by the terminal to determine the transmission parameters of the first PUCCH.

[0393] In some embodiments, the first PUCCH is transmitted after the Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) message 4. And / or, the first PUCCH is transmitted before the terminal sends a first signaling message, where the first signaling message includes at least one of the following: terminal capability information, and terminal reconfiguration completion information.

[0394] In some embodiments, the first PUCCH is used to carry at least one of the following: a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, a scheduling request (SR) message, and channel state information (CSI).

[0395] In some embodiments, the terminal does not expect the network device to configure transmission parameters of the dedicated physical uplink control channel dedicated PUCCH to the terminal through Msg4, and the first PUCCH is a common PUCCH.

[0396] In some embodiments, the first PUCCH is a dedicated physical uplink control channel (PUCCH), and transmission parameters of the dedicated PUCCH are carried based on the random access message Msg4.

[0397] In some embodiments, the terminal further includes a processing module 6101, configured to determine a repetition transmission parameter of the first PUCCH, and perform repetition transmission of the first PUCCH according to the repetition transmission parameter.

[0398] In some embodiments, the processing module 6101 determines the repetition transmission parameter of the dedicated PUCCH in the following manner: determining that the repetition transmission parameter of the dedicated PUCCH is the same as the repetition transmission parameter used by the terminal to send the Msg4 HARQ-ACK message.

[0399] In some embodiments, the processing module 6101 determines the dedicated PUCCH repetition transmission parameter in the following manner: determining the dedicated PUCCH repetition transmission parameter based on second information sent by the network device, where the second information is used to semi-statically configure the dedicated PUCCH repetition transmission parameter.

[0400] In some embodiments, the second information is carried based on at least one of the following: a system message SIB. Msg4.

[0401] In some embodiments, the processing module 6101 determines that the repetition transmission parameter of the dedicated PUCCH satisfies at least one of the following priority relationships: determining the repetition transmission parameter of the dedicated PUCCH based on Msg4 takes precedence over determining the repetition transmission parameter of the dedicated PUCCH based on the SIB. Determining the repetition transmission parameter of the dedicated PUCCH based on the SIB takes precedence over determining that the repetition transmission parameter of the dedicated PUCCH is the same as the repetition transmission parameter used by the terminal to send the Msg4 HARQ-ACK message.

[0402] In some embodiments, the processing module 6101 is configured to perform repeated transmission based on the repeated transmission parameter when at least one of the following conditions is met: the terminal sends a repeated transmission capability indication to the network device; the terminal sends a repeated transmission request to the network device.

[0403] In some embodiments, the processing module 6101 determines, based on the same or different methods, a repetition transmission parameter of a dedicated PUCCH scheduled by downlink control information DCI in a fallback format and a repetition transmission parameter of a dedicated PUCCH scheduled by DCI in a non-fallback format. The repetition transmission parameter corresponding to the dedicated PUCCH scheduled by the DCI in the fallback format is the same as or different from the repetition transmission parameter corresponding to the dedicated PUCCH scheduled by the DCI in the non-fallback format.

[0404] In some embodiments, the processing module 6101 is configured to satisfy at least one of the following conditions: the terminal does not perform repeated transmission when sending the Msg4 HARQ-ACK message; and the second information is not received.

[0405] In some embodiments, the processing module 6101 determines the repetition transmission parameters of the dedicated PUCCH in the following manner: based on the downlink DCI sent by the network device, the repetition transmission parameters of the dedicated PUCCH are determined, the downlink DCI is used to schedule the dedicated PUCCH, and the downlink DCI carries the repetition transmission parameters corresponding to the dedicated PUCCH.

[0406] In some embodiments, the processing module 6101 determines the repetition transmission parameters of the dedicated PUCCH based on the downlink DCI sent by the network device in response to the cyclic redundancy check CRC of the downlink DCI being scrambled by the cell radio network temporary identifier C-RNTI, and / or the downlink DCI being a fallback format DCI, using at least one of the following methods: determining the repetition transmission parameters of the dedicated PUCCH based on a first field in the downlink DCI, where the first field is the downlink allocation indication field DAI. Determining the repetition transmission parameters of the dedicated PUCCH based on a second field in the downlink DCI, where the second field includes at least one of the following: a modulation and coding scheme MCS field. A transmit power control TPC field. A PUCCH resource indication field PRI.

[0407] In some embodiments, the processing module 6101 determines the repetition transmission parameter of the dedicated PUCCH based on the downlink DCI sent by the network device in response to the CRC of the downlink DCI being scrambled by the C-RNTI, and / or the downlink DCI being a non-fallback format DCI, using at least one of the following methods: determining the repetition transmission parameter of the dedicated PUCCH based on a third field in the downlink DCI, where the third field is a newly added field in the downlink DCI. Determining the repetition transmission parameter of the dedicated PUCCH based on at least part of the bits of the second field in the downlink DCI, where the second field includes at least one of the following: a modulation and coding scheme MCS field. A transmission power control TPC field. A PUCCH resource indication PRI field.

[0408] In some embodiments, the second field includes a PRI field, the PRI field is used to indicate a dedicated PUCCH resource, and each dedicated PUCCH resource corresponds to a repetition transmission parameter.

[0409] In some embodiments, the first field or the second field indicates the repetition parameter by means of a codepoint. Alternatively, the first field or the second field indicates the number of repetitions of the dedicated PUCCH by indicating a value set index, where the value set index is determined based on a repetition parameter set carried by the second information carrier.

[0410] In some embodiments, the processing module 6101 determines a retransmission parameter for a dedicated PUCCH based on the first field or the second field in the downlink DCI, if at least one of the following conditions is met: sending a retransmission capability indication to a network device; sending a retransmission request to the network device; receiving second information sent by the network device, the second information including a bit for explicitly instructing the terminal to perform retransmission; and receiving second information sent by the network device, the second information including a retransmission parameter.

[0411] In some embodiments, the repetition transmission parameter includes at least one of the following: a repetition transmission number, a repetition transmission number set, and a reference signal received power (RSRP) threshold value, where the RSRP threshold value is used by the terminal to determine whether to perform repetition transmission.

[0412] FIG6b is a schematic diagram of the structure of a network device according to an embodiment of the present disclosure. As shown in FIG6b , the network device 6200 may include a transceiver module 6201. The transceiver module 6201 is configured to receive a first physical uplink control channel (PUCCH), wherein the transmission parameters of the first PUCCH are determined by the terminal.

[0413] In some embodiments, the transceiver module 6201 is further used to: send first information to the terminal, where the first information is used by the terminal to determine transmission parameters of the first physical uplink control channel PUCCH.

[0414] In some embodiments, the first PUCCH is transmitted after the Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) message 4. And / or, the first PUCCH is transmitted before the terminal sends a first signaling message, where the first signaling message includes at least one of the following: terminal capability information, and terminal reconfiguration completion information.

[0415] In some embodiments, the first PUCCH is used to carry at least one of the following: a hybrid automatic repeat request acknowledgement (HARQ-ACK) message, a scheduling request (SR) message, and channel state information (CSI).

[0416] In some embodiments, the terminal does not expect the network device to configure transmission parameters of the dedicated physical uplink control channel dedicated PUCCH to the terminal through Msg4, and the first PUCCH is a common PUCCH.

[0417] In some embodiments, the first PUCCH is a dedicated physical uplink control channel (PUCCH), and transmission parameters of the dedicated PUCCH are carried based on the random access message Msg4.

[0418] In some embodiments, the transceiver module 6201 is further used to: send second information to the network, where the second information is used to semi-statically configure the repetition transmission parameters of the dedicated PUCCH.

[0419] In some embodiments, the second information is carried based on at least one of the following: a system message SIB. Msg4.

[0420] In some embodiments, the transceiver module 6201 is further configured to: send downlink DCI to the terminal, where the downlink DCI is used to schedule a dedicated PUCCH, and the downlink DCI carries a repetition transmission parameter corresponding to the dedicated PUCCH.

[0421] In some embodiments, the cyclic redundancy check (CRC) of the downlink DCI is scrambled using the cell radio network temporary identifier (C-RNTI), and / or the downlink DCI is a fallback format DCI. The downlink DCI includes at least one of the following: a first field, the first field is used to determine the repetition transmission parameter of the dedicated PUCCH, and the first field is the downlink allocation indication field (DAI). A second field, the second field is used to determine the repetition transmission parameter of the dedicated PUCCH, and the second field includes at least one of the following: a modulation and coding scheme (MCS) field; a transmit power control (TPC) field; and a PUCCH resource indication field (PRI).

[0422] In some embodiments, the CRC of the downlink DCI is scrambled using the C-RNTI, and / or the downlink DCI is a non-fallback format DCI. The downlink DCI includes at least one of the following: a third field, which is used to determine the repetition transmission parameter of the dedicated PUCCH. The third field is a newly added field in the downlink DCI. A second field, which is used to determine the repetition transmission parameter of the dedicated PUCCH. The second field includes at least one of the following: a modulation and coding scheme (MCS) field; a transmit power control (TPC) field; and a PUCCH resource indicator (PRI) field.

[0423] In some embodiments, the second field includes a PRI field, the PRI field is used to indicate a dedicated PUCCH resource, and each dedicated PUCCH resource corresponds to a repetition transmission parameter.

[0424] In some embodiments, the first field or the second field indicates the repetition parameter by means of a codepoint. Alternatively, the first field or the second field indicates the number of repetitions of the dedicated PUCCH by indicating a value set index, where the value set index is determined based on a repetition parameter set carried by the second information carrier.

[0425] In some embodiments, the downlink DCI is used to determine a retransmission parameter for a dedicated PUCCH when at least one of the following conditions is met: receiving a retransmission capability indication sent by a terminal; receiving a retransmission request sent by a terminal; sending second information to the terminal, the second information including a bit for explicitly instructing the terminal to perform retransmission; and sending second information to the terminal, the second information including a retransmission parameter.

[0426] In some embodiments, the repetition transmission parameter includes at least one of the following: a repetition transmission number, a repetition transmission number set, and a reference signal received power (RSRP) threshold value, where the RSRP threshold value is used by the terminal to determine whether to perform repetition transmission.

[0427] Figure 7a is a schematic diagram of the structure of a communication device 7100 proposed in an embodiment of the present disclosure. Communication device 7100 can be a network device, a terminal, a chip, a chip system, or a processor that supports a network device in implementing any of the above methods, or a chip, a chip system, or a processor that supports a terminal in implementing any of the above methods. Optionally, the network device can be an access network device, a core network device, or the like. Optionally, the terminal can be a user equipment, or the like. Communication device 7100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0428] As shown in Figure 7a, communication device 7100 includes one or more processors 7101. Processor 7101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device, execute programs, and process program data. Communication device 7100 is used to perform any of the above methods. Optionally, the communication device can be a base station, a baseband chip, a terminal device, a terminal device chip, a DU or CU, etc.

[0429] In some embodiments, the communication device 7100 further includes one or more memories 7102 for storing instructions. Optionally, all or part of the memories 7102 may be located outside the communication device 7100.

[0430] In some embodiments, the communication device 7100 further includes one or more transceivers 7103. When the communication device 7100 includes one or more transceivers 7103, the transceiver 7103 performs the communication step S2101 such as sending and / or receiving in the above method, and the processor 7101 performs other steps.

[0431] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0432] In some embodiments, the communication device 7100 may include one or more interface circuits 7104. Optionally, the interface circuit 7104 is connected to the memory 7102. The interface circuit 7104 may be configured to receive signals from the memory 7102 or other devices, and may be configured to send signals to the memory 7102 or other devices. For example, the interface circuit 7104 may read instructions stored in the memory 7102 and send the instructions to the processor 7101.

[0433] The communication device 7100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 7100 described in the present disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 7a. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0434] FIG7 b is a schematic diagram of the structure of a chip 7200 according to an embodiment of the present disclosure. If the communication device 7100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 7200 shown in FIG7 b , but the present disclosure is not limited thereto.

[0435] The chip 7200 includes one or more processors 7201 , and the chip 7200 is configured to execute any of the above methods.

[0436] In some embodiments, the chip 7200 further includes one or more interface circuits 7202. Optionally, the interface circuit 7202 is connected to the memory 7203. The interface circuit 7202 can be used to receive signals from the memory 7203 or other devices, and can be used to send signals to the memory 7203 or other devices. For example, the interface circuit 7202 can read instructions stored in the memory 7203 and send the instructions to the processor 7201.

[0437] In some embodiments, the interface circuit 7202 executes the communication step S2101 of sending and / or receiving in the above method, and the processor 7201 executes other steps.

[0438] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0439] In some embodiments, the chip 7200 further includes one or more memories 7203 for storing instructions. Alternatively, all or part of the memories 7203 may be located outside the chip 7200.

[0440] The present disclosure also provides a storage medium having instructions stored thereon. When the instructions are executed on the communication device 7100, the communication device 7100 is caused to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

[0441] The present disclosure also provides a program product, which, when executed by the communication device 7100, enables the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0442] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A communication method, characterized in that: The method is executed by a terminal, and includes: Determining a transmission parameter of a first physical uplink control channel PUCCH; The first PUCCH is sent based on the transmission parameters of the first PUCCH.

2. The method according to claim 1, characterized in that The transmission parameter of the first PUCCH is determined by at least one of the following methods: Determine a transmission parameter of the first PUCCH based on the provisions in the protocol; First information is received, where the first information is used by the terminal to determine a transmission parameter of a first PUCCH.

3. The method according to any one of claims 1 to 2, characterized in that: The transmission of the first PUCCH is after the Msg4 hybrid automatic repeat request confirmation HARQ-ACK; and / or, The transmission of the first PUCCH is before the terminal sends a first signaling, and the first signaling includes at least one of the following: terminal capability information; terminal reconfiguration completion information.

4. The method according to any one of claims 1 to 2, characterized in that: The first PUCCH is used to carry at least one of the following: Hybrid automatic repeat request confirmation HARQ-ACK message; Scheduling request SR message; Channel state information CSI.

5. The method according to any one of claims 1 to 4, characterized in that: The terminal does not expect the network device to configure the transmission parameters of the dedicated physical uplink control channel dedicated PUCCH to the terminal through Msg4, and the first PUCCH is a public PUCCH.

6. The method according to any one of claims 1 to 4, characterized in that: The first PUCCH is a dedicated physical uplink control channel dedicated PUCCH, and the transmission parameters of the dedicated PUCCH are carried based on the random access message Msg4.

7. The method according to claim 6, characterized in that The method further comprises: Determine a repetition transmission parameter of the first PUCCH, and perform repetition transmission of the first PUCCH according to the repetition transmission parameter.

8. The method according to claim 7, characterized in that The repetition transmission parameter of the dedicated PUCCH is determined in the following manner: Determine that the repetition transmission parameter of the dedicated PUCCH is the same as the repetition transmission parameter used by the terminal to send the Msg4 HARQ-ACK message.

9. The method according to claim 7, characterized in that: The repetition transmission parameter of the dedicated PUCCH is determined in the following manner: Based on second information sent by a network device, a repetition transmission parameter of the dedicated PUCCH is determined, where the second information is used to semi-statically configure the repetition transmission parameter of the dedicated PUCCH.

10. The method according to claim 9, characterized in that The second information is carried based on at least one of the following: System message SIB; Msg4.

11. The method according to claim 10, characterized in that The determining of the repetition transmission parameter of the dedicated PUCCH satisfies at least one of the following priority relationships: Determining the repetition transmission parameter of the dedicated PUCCH based on the Msg4 takes precedence over determining the repetition transmission parameter of the dedicated PUCCH based on the SIB; Determining the repetition transmission parameter of the dedicated PUCCH based on the SIB takes precedence over determining that the repetition transmission parameter of the dedicated PUCCH is the same as the repetition transmission parameter used by the terminal to send the Msg4 HARQ-ACK message.

12. The method according to any one of claims 8 to 11, characterized in that: At least one of the following conditions is met, and repeated transmission is performed based on the repeated transmission parameter: The terminal sends a repeat transmission capability indication to the network device; The terminal sends a repeated transmission request to the network device.

13. The method according to any one of claims 8 to 12, characterized in that: Determine, based on the same or different methods, a repetition transmission parameter of the dedicated PUCCH scheduled by the downlink control information DCI in a fallback format and a repetition transmission parameter of the dedicated PUCCH scheduled by the DCI in a non-fallback format; The repetition transmission parameter corresponding to the dedicated PUCCH scheduled by the DCI in the fallback format is the same as or different from the repetition transmission parameter corresponding to the dedicated PUCCH scheduled by the DCI in the non-fallback format.

14. The method according to any one of claims 8 to 13, characterized in that: If at least one of the following conditions is met, duplicate transmission will not be performed: The terminal does not perform repeated transmission when sending the Msg4 HARQ-ACK message; The second information was not received.

15. The method according to claim 8, characterized in that The repetition transmission parameter of the dedicated PUCCH is determined in the following manner: based on a downlink DCI sent by a network device, the repetition transmission parameter of the dedicated PUCCH is determined, the downlink DCI is used to schedule the dedicated PUCCH, and the downlink DCI carries the repetition transmission parameter corresponding to the dedicated PUCCH.

16. The method according to claim 15, characterized in that In response to the cyclic redundancy check CRC of the downlink DCI being scrambled by the cell radio network temporary identifier C-RNTI, and / or the downlink DCI being a fallback format DCI, the repetition transmission parameter of the dedicated PUCCH is determined based on the downlink DCI sent by the network device in at least one of the following ways: Determine a repetition transmission parameter of the dedicated PUCCH based on a first field in the downlink DCI, where the first field is a downlink allocation indication field DAI; Determine a repetition transmission parameter of the dedicated PUCCH based on at least part of bits of a second field in the downlink DCI, where the second field includes at least one of the following: Modulation and Coding Scheme MCS field; Transmit power control TPC field; PUCCH resource indication field PRI.

17. The method according to any one of claims 16, characterized in that In response to the CRC of the downlink DCI being scrambled by the C-RNTI, and / or the downlink DCI being a non-fallback format DCI, determining the repetition transmission parameter of the dedicated PUCCH based on the downlink DCI sent by the network device in at least one of the following ways: Determine a repetition transmission parameter of the dedicated PUCCH based on a third field in the downlink DCI, where the third field is a newly added field in the downlink DCI; Based on at least part of the bits of the second field in the downlink DCI, the repetition transmission parameter of the dedicated PUCCH is determined, and the second field includes at least one of the following: a modulation and coding scheme MCS field; a transmission power control TPC field; a PUCCH resource indication PRI field.

18. The method according to any one of claims 16-17, characterized in that: The second field includes a PRI field, where the PRI field is used to indicate dedicated PUCCH resources, and each dedicated PUCCH resource corresponds to a repetition transmission parameter.

19. The method according to any one of claims 16 to 18, characterized in that: The first field or the second field indicates a repetition transmission parameter by means of a codepoint; or, the first field or the second field indicates the number of repetition transmissions of the dedicated PUCCH by indicating a numerical set index, and the numerical set index is determined based on a repetition parameter set carried by the second information.

20. The method according to any one of claims 16 to 19, characterized in that: At least one of the following conditions is met, and based on the first field or the second field in the downlink DCI, a repetition transmission parameter of the dedicated PUCCH is determined: sending a repeat transmission capability indication to a network device; Sending repeated transmission requests to the network device; receiving second information sent by the network device, wherein the second information includes a bit for explicitly instructing the terminal to perform repeated transmission; Second information sent by the network device is received, where the second information includes the repeated transmission parameter.

21. The method according to any one of claims 1 to 20, characterized in that The repetition transmission parameter includes at least one of the following: Number of retransmissions; A set of repetition transmission times; A threshold value of reference information received power RSRP is used by the terminal to determine whether to perform repeated transmission.

22. A communication method, characterized in that: The method is performed by a network device, and the method includes: A first physical uplink control channel PUCCH is received, where a transmission parameter of the first PUCCH is determined by the terminal.

23. The method according to claim 22, characterized in that The method further comprises: Sending first information to a terminal, where the first information is used by the terminal to determine a transmission parameter of the first PUCCH.

24. The method according to any one of claims 22-23, characterized in that The transmission of the first PUCCH is located after Msg4 hybrid automatic repeat request confirmation HARQ-ACK, and / or, the transmission of the first PUCCH is located before the terminal sends a first signaling, and the first signaling includes at least one of the following: terminal capability information; terminal reconfiguration completion information.

25. The method according to claim 24, characterized in that The first PUCCH is used to carry at least one of the following: Hybrid automatic repeat request confirmation HARQ-ACK message; Scheduling request SR message; Channel state information CSI.

26. The method according to any one of claims 24-25, characterized in that The terminal does not expect the network device to configure the transmission parameters of the dedicated physical uplink control channel dedicated PUCCH to the terminal through Msg4, and the first PUCCH is a public PUCCH.

27. The method according to any one of claims 24-25, characterized in that The first PUCCH is a dedicated physical uplink control channel dedicated PUCCH, and the transmission parameters of the dedicated PUCCH are carried based on the random access message Msg4.

28. The method according to claim 27, characterized in that The method further comprises: Sending second information to the network, where the second information is used to semi-statically configure the repetition transmission parameters of the dedicated PUCCH.

29. The method according to claim 28, characterized in that The second information is carried based on at least one of the following: System message SIB; Msg4.

30. The method according to claim 27, characterized in that The method further comprises: A downlink DCI is sent to the terminal, where the downlink DCI is used to schedule the dedicated PUCCH, and the downlink DCI carries a repetition transmission parameter corresponding to the dedicated PUCCH.

31. The method according to claim 30, characterized in that The cyclic redundancy check CRC of the downlink DCI is scrambled by a cell radio network temporary identifier C-RNTI, and / or the downlink DCI is a fallback format DCI, and the downlink DCI includes at least one of the following; A first field, where the first field is used to determine a repetition transmission parameter of the dedicated PUCCH, and the first field is a downlink allocation indication field DAI; The second field is used to determine the repeated transmission parameter of the dedicated PUCCH, and the second field includes at least one of the following: a modulation and coding scheme MCS field; a transmit power control TPC field; and a PUCCH resource indication field PRI.

32. The method according to claim 30, characterized in that The CRC of the downlink DCI is scrambled by C-RNTI, and / or the downlink DCI is a non-fallback format DCI, and the downlink DCI includes at least one of the following; A third field, the third field is used to determine the repetition transmission parameter of the dedicated PUCCH, and the third field is a newly added field in the downlink DCI; The second field is used to determine the repeated transmission parameter of the dedicated PUCCH, and the second field includes at least one of the following: a modulation and coding scheme MCS field; a transmit power control TPC field; and a PUCCH resource indication field PRI.

33. The method according to any one of claims 31-32, characterized in that The second field includes a PRI field, where the PRI field is used to indicate dedicated PUCCH resources, and each dedicated PUCCH resource corresponds to a repetition transmission parameter.

34. The method according to any one of claims 31 to 33, characterized in that: The first field or the second field indicates a repetition transmission parameter by means of a codepoint; or, the first field or the second field indicates the number of repetition transmissions of the dedicated PUCCH by indicating a numerical set index, and the numerical set index is determined based on a repetition parameter set carried by the second information.

35. The method according to any one of claims 31 to 34, characterized in that The downlink DCI is used to determine the repetition transmission parameter of the dedicated PUCCH if at least one of the following conditions is met: receiving a repeat transmission capability indication sent by a terminal; receiving a repeated transmission request sent by a terminal; Sending second information to the terminal, where the second information includes a bit used to explicitly instruct the terminal to perform repeated transmission; Sending second information to the terminal, where the second information includes the repeated transmission parameter.

36. The method according to any one of claims 1 to 35, characterized in that The repetition transmission parameter includes at least one of the following: Number of retransmissions; A set of repetition transmission times; A threshold value of reference information received power RSRP is used by the terminal to determine whether to perform repeated transmission.

37. A communication method, characterized in that: The method comprises: The terminal determines a transmission parameter of a first physical uplink control channel PUCCH; The terminal sends the first PUCCH based on the transmission parameters of the first PUCCH; The network device receives a first physical uplink control channel PUCCH.

38. A terminal, characterized in that it comprises: A processing module, used to determine a transmission parameter of a first physical uplink control channel PUCCH; The transceiver module is used to send the first PUCCH based on the transmission parameters of the first PUCCH.

39. A network device, characterized in that: include: The transceiver module is used to receive a first physical uplink control channel PUCCH, where the transmission parameters of the first PUCCH are determined by the terminal.

40. A terminal, characterized in that: include: one or more processors; The processor is used to execute the communication method described in any one of claims 1-21.

41. A network device, characterized in that: include: one or more processors; Wherein, the processor is used to execute the communication method described in any one of claims 22-36.

42. A communication system, characterized in that: It comprises a terminal and a network device, wherein the terminal is configured to implement the communication method according to any one of claims 1 to 21, and the network device is configured to implement the communication method according to any one of claims 22 to 36.

43. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the communication method as described in any one of claims 1-21 or 22-36.

Images