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: sending first information to a network device, wherein the first information is used for indicating, to the network device, that a terminal expects to perform repeated transmission on a dedicated physical uplink control channel (PUCCH). The present disclosure can improve the transmission performance of a PUCCH.

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] Due to the different nodes using PUCCH, 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, which is executed by a terminal. The method includes: sending first information to a network device, wherein the first information is used to indicate to the network device that the terminal expects a dedicated physical uplink control channel (PUCCH) to perform repeated transmission.

[0007] According to a second aspect of an embodiment of the present disclosure, a communication method is proposed, which is executed by a network device, and the method includes: receiving first information sent by a terminal, wherein the first information is used to indicate to the network device that the terminal expects a dedicated physical uplink control channel dedicated PUCCH to perform repeated transmission.

[0008] According to a third aspect of an embodiment of the present disclosure, a communication method is proposed, including: a terminal sends first information to a network device, wherein the first information is used to indicate to the network device that the terminal expects a dedicated physical uplink control channel dedicated PUCCH to perform repeated transmission; and the network device receives the first information.

[0009] According to a fourth aspect of an embodiment of the present disclosure, a terminal is proposed, comprising: a transceiver module, configured to send first information to a network device, wherein the first information is configured to indicate to the network device that the terminal expects a dedicated physical uplink control channel (PUCCH) to perform repeated transmission.

[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 first information sent by a terminal, wherein the first information is configured to indicate to the network device that the terminal expects a dedicated physical uplink control channel (PUCCH) to perform repeated transmission.

[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 an 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 second aspects.

[0015] The present disclosure sends first information to a network device through a terminal, so that the network device can configure and schedule repeated transmission of a dedicated PUCCH to the terminal, thereby improving the transmission performance of the PUCCH. 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 is a schematic diagram showing an interaction of a communication method according to an embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

[0030] In a first aspect, an embodiment of the present disclosure proposes a communication method, which is executed by a terminal, and includes: sending first information to a network device, wherein the first information is used to indicate to the network device that the terminal expects a dedicated physical uplink control channel dedicated PUCCH to perform repetition transmission.

[0031] In the above embodiment, the terminal sends the first information to the network device to inform the network device in advance that the terminal expects repeated transmission of dedicated PUCCH, so that the network device can configure and schedule repeated transmission of dedicated PUCCH to the terminal in advance, thereby improving PUCCH transmission performance.

[0032] In combination with some embodiments of the first aspect, in some embodiments, the dedicated PUCCH is transmitted using PUCCH parameters configured by radio resource control RRC signaling, and the RRC signaling is carried based on a random access message Msg4.

[0033] In the above embodiment, the transmission performance is improved for the dedicated PUCCH configured by the RRC signaling carried by Msg4.

[0034] In combination with some embodiments of the first aspect, in some embodiments, the transmission of the dedicated PUCCH is located after the Msg4 hybrid automatic repeat request confirmation HARQ-ACK, and / or, the transmission of the dedicated 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.

[0035] In the above embodiment, the dedicated PUCCH is transmitted after the Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) of Msg4 and / or before the terminal sends the first signaling, so as to improve the transmission performance of the PUCCH in this time period.

[0036] In combination with some embodiments of the first aspect, in some embodiments, the first information includes at least one of the following: repeat transmission capability; repeat transmission request.

[0037] In the above embodiment, the first information reported by the terminal may be at least one of the retransmission capability and the retransmission request, which can adapt to various situations where the network device is configured or not configured with the RSRP threshold, thereby improving the transmission performance of the PUCCH.

[0038] In combination with some embodiments of the first aspect, in some embodiments, the first information is second information, and the second information is used to indicate to the network device the capability of the terminal to repeatedly transmit the common PUCCH.

[0039] In the above embodiment, by indicating the common PUCCH retransmission capability of the terminal, the dedicated PUCCH retransmission capability can be indirectly indicated, thereby saving signaling.

[0040] 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: a service data unit SDU in the random access information Msg3; a media access control unit subheader.

[0041] In the above embodiment, the capability of common PUCCH repeated transmission may be carried out through at least one signaling, so that more efficient transmission can be performed in different situations.

[0042] In combination with some embodiments of the first aspect, in some embodiments, the first information is third information, and the third information is used to separately indicate to the network device the capability of the terminal to repeatedly transmit dedicated PUCCH.

[0043] In the above embodiment, the third information may be used to separately indicate the capability of repeated transmission of the dedicated PUCCH, so as to more quickly inform the network device that the terminal expects repeated transmission of the dedicated PUCCH.

[0044] In combination with some embodiments of the first aspect, in some embodiments, the third information is carried based on at least one of the following: Msg1; Msg A; Msg3; Msg5.

[0045] In the above embodiment, the capability of repeated transmission of dedicated PUCCH can be carried out through at least one signaling, so as to enable more efficient transmission in different situations.

[0046] In combination with some embodiments of the first aspect, in some embodiments, the third information is based on an independent random access channel PRACH carried in the Msg1 and / or the Msg A, and the independent PRACH is configured by a network device and has different time-frequency domain resources from the traditional PRACH; and / or, the independent PRACH resource is configured by a network device and uses a different preamble sequence from the traditional PRACH.

[0047] In the above embodiment, the capability of indicating repeated transmission of dedicated PUCCH more quickly may be achieved based on the independent random access channel PRACH bearer in the Msg1 and / or the Msg A.

[0048] In combination with some embodiments of the first aspect, in some embodiments, the third information is based on at least one of the following carrying items of the Msg3 and / or the Msg A physical uplink shared channel PUSCH: an independent demodulation reference signal DMRS, and the independent DMRS corresponds to at least one of the following differences from the traditional DMRS: time domain, code domain and frequency domain; a newly added logical channel identifier LCID; a reserved bit in the media access control subheader; an existing MAC CE; a newly added MAC CE; a reserved bit in the RRCsetupRequest message; a newly added bit in the RRCsetupRequest message; a reserved bit in the RRC recovery request message; a newly added bit in the RRC recovery request message; a reserved bit in the RRC reconstruction request message; a newly added bit in the RRC reconstruction request message; a newly added RRC capability signaling carried in the packet data unit MAC PDU; and a newly added physical layer bit in the payload.

[0049] In the above embodiment, the capability of repeated transmission of the dedicated PUCCH may be indicated based on at least one method, so as to enable more efficient transmission in different situations.

[0050] In combination with some embodiments of the first aspect, in some embodiments, the third information is carried based on at least one of the following items in the Msg5: an independent demodulation reference signal DMRS, and the independent DMRS is different from the traditional DMRS in corresponding to at least one of the following items: time domain, code domain and frequency domain; a newly added logical channel identifier; a reserved bit in the media access control subheader; an existing MAC CE; a newly added MAC CE; a reserved bit in the RRCsetupComplete message of the RRC setup completion; a newly added bit in the RRCsetupComplete message; a reserved bit in the RRC recovery complete message; a newly added bit in the RRC recovery complete message; a reserved bit in the RRC reconstruction complete message; a newly added bit in the RRC reconstruction complete message; a newly added RRC capability signaling in the packet data unit MAC PDU; and a newly added physical layer bit in the payload.

[0051] In the above embodiment, the capability of repeated transmission of the dedicated PUCCH may be indicated based on at least one method, so as to enable more efficient transmission in different situations.

[0052] In combination with some embodiments of the first aspect, in some embodiments, in response to receiving fourth information sent by the network device, the first information is sent to the network device, and the fourth information is used to explicitly instruct the terminal to send the first information.

[0053] In the above embodiment, the fourth information sent by the network device can be received to facilitate reporting the dedicated PUCCH repeated transmission capability upon receiving the fourth information. This avoids the terminal's meaningless reporting of the dedicated PUCCH repeated transmission capability and waste of resources when the network device does not support the configuration of repeated transmission. Furthermore, the display indication method can more quickly determine whether to send the first information, thereby improving efficiency.

[0054] In combination with some embodiments of the first aspect, in some embodiments, in response to receiving fourth information sent by the network device, the first information is sent to the network device, and the fourth information is used to implicitly instruct the terminal to send the first information.

[0055] In the above embodiment, the fourth information sent by the network device can be received so that the dedicated PUCCH repeated transmission capability can be reported upon receiving the fourth information. This avoids the terminal's meaningless reporting of the dedicated PUCCH repeated transmission capability when the network device does not support the configuration of repeated transmission, which wastes resources. Furthermore, the implicit indication method can save signaling.

[0056] In combination with some embodiments of the first aspect, in some embodiments, the fourth information includes at least one of the following: the number of repeated transmissions; the set of repeated transmission times; the threshold value of the reference information received power RSRP.

[0057] In the above embodiment, the fourth information may include at least one item, so that the terminal can determine whether to report the first information more flexibly and accurately.

[0058] In combination with some embodiments of the first aspect, in some embodiments, in response to the network device configuring the threshold value of the reference signal received power RSRP corresponding to the dedicated PUCCH repetition, the terminal supports the dedicated PUCCH repetition, and the RSRP measurement value of the terminal is lower than the threshold value, and the retransmission request is sent; in response to the network device not configuring the threshold value, the terminal supports the dedicated PUCCH repetition, and the terminal sends the retransmission capability.

[0059] In the above embodiment, the terminal sends different information to inform the network device that the terminal expects dedicated PUCCH to be repeatedly transmitted in different situations where the network device is configured with an RSRP threshold or the network device is not configured with an RSRP threshold.

[0060] In combination with some embodiments of the first aspect, in some embodiments, the threshold value of the RSRP corresponding to the dedicated PUCCH repetition is determined by at least one of the following methods: determining the threshold value of the RSRP corresponding to the dedicated PUCCH, which is the same as the threshold value of the RSRP corresponding to the common PUCCH; receiving the fifth information sent by the network device, and the fourth information is used to configure the threshold value of the RSRP corresponding to the dedicated PUCCH.

[0061] In the above embodiment, the RSRP threshold corresponding to the dedicated PUCCH can be configured according to different situations to save resources or improve efficiency.

[0062] In combination with some embodiments of the first aspect, in some embodiments, the fifth information is carried by at least one of the following: SIB1; other system messages OSI; Msg4.

[0063] In the above embodiment, the fifth information may be carried in at least one manner to improve efficiency.

[0064] According to a second aspect of an embodiment of the present disclosure, a communication method is provided, which is executed by a network device, and the method includes: receiving first information sent by a terminal, wherein the first information is used to indicate to the network device that the terminal expects a dedicated physical uplink control channel dedicated PUCCH to perform repeated transmission.

[0065] In combination with some embodiments of the second aspect, in some embodiments, the dedicated PUCCH is transmitted using PUCCH parameters configured by radio resource control RRC signaling, and the RRC signaling is carried based on the random access message Msg4.

[0066] In combination with some embodiments of the second aspect, in some embodiments, the transmission of the dedicated PUCCH is located after the Msg4 hybrid automatic repeat request confirmation HARQ-ACK; and / or, the transmission of the dedicated 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.

[0067] In combination with some embodiments of the second aspect, in some embodiments, the first information includes at least one of the following: repeat transmission capability; repeat transmission request.

[0068] In combination with some embodiments of the second aspect, in some embodiments, the first information is second information, and the second information is used to indicate to the network device the capability of the terminal to repeat transmission of the common PUCCH.

[0069] 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: a service data unit SDU in the random access information Msg3; a media access control unit subheader.

[0070] In combination with some embodiments of the second aspect, in some embodiments, the first information is third information, and the third information is used to separately indicate to the network device the capability of the terminal to repeatedly transmit dedicated PUCCH.

[0071] In combination with some embodiments of the second aspect, in some embodiments, the third information is carried based on at least one of the following: Msg1; Msg A; Msg3; Msg5.

[0072] In combination with some embodiments of the second aspect, in some embodiments, the third information is based on an independent random access channel PRACH carried in the Msg1 and / or the Msg A, and the independent PRACH is configured by a network device and has different time-frequency domain resources from the traditional PRACH; and / or, the independent PRACH resource is configured by a network device and uses a different preamble sequence from the traditional PRACH.

[0073] In combination with some embodiments of the second aspect, in some embodiments, the third information is based on at least one of the following carrying items of the Msg3 and / or the Msg A physical uplink shared channel PUSCH: an independent demodulation reference signal DMRS, and the independent DMRS corresponds to at least one of the following differences from the traditional DMRS: time domain, code domain and frequency domain; a newly added logical channel identifier LCID; a reserved bit in the media access control subheader; an existing MAC CE; a newly added MAC CE; a reserved bit in the RRCsetupRequest message; a newly added bit in the RRCsetupRequest message; a reserved bit in the RRC recovery request message; a newly added bit in the RRC recovery request message; a reserved bit in the RRC reconstruction request message; a newly added bit in the RRC reconstruction request message; a newly added RRC capability signaling carried in the packet data unit MAC PDU; and a newly added physical layer bit in the payload.

[0074] In combination with some embodiments of the second aspect, in some embodiments, the third information is carried based on at least one of the following items in the Msg5: an independent demodulation reference signal DMRS, and the independent DMRS is different from the traditional DMRS in corresponding to at least one of the following items: time domain, code domain and frequency domain; a newly added logical channel identifier; a reserved bit in the media access control subheader; an existing MAC CE; a newly added MAC CE; a reserved bit in the RRCsetupComplete message of the RRC setup completion; a newly added bit in the RRCsetupComplete message; a reserved bit in the RRC recovery complete message; a newly added bit in the RRC recovery complete message; a reserved bit in the RRC reconstruction complete message; a newly added bit in the RRC reconstruction complete message; a newly added RRC capability signaling in the packet data unit MAC PDU; and a newly added physical layer bit in the payload.

[0075] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending fourth information to the terminal, where the fourth information is used to explicitly instruct the terminal to send the first information.

[0076] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending fourth information to the terminal, where the fourth information is used to implicitly instruct the terminal to send the first information.

[0077] In combination with some embodiments of the second aspect, in some embodiments, the fourth information includes at least one of the following: the number of repeated transmissions; the set of repeated transmission times; the threshold value of the reference information receiving power RSRP.

[0078] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending fifth information to the terminal, where the fifth information is used to configure a threshold value of RSRP corresponding to the dedicated PUCCH.

[0079] In combination with some embodiments of the second aspect, in some embodiments, the fifth information is carried by at least one of the following: SIB1; other system messages OSI; Msg4.

[0080] According to a third aspect of an embodiment of the present disclosure, a communication method is provided, comprising: a terminal sending first information to a network device, wherein the first information is used to indicate to the network device that the terminal expects a dedicated physical uplink control channel dedicated PUCCH to perform repeated transmission; and the network device receives the first information.

[0081] According to a fourth aspect of an embodiment of the present disclosure, a terminal is provided, comprising: a transceiver module, configured to send first information to a network device, wherein the first information is configured to indicate to the network device that the terminal expects a dedicated physical uplink control channel (PUCCH) to perform repeated transmission.

[0082] In combination with some embodiments of the fourth aspect, in some embodiments, the dedicated PUCCHMsg is transmitted using PUCCH parameters configured by radio resource control RRC signaling, and the RRC signaling is based on the random access message Msg4 carried

[0083] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transmission of the dedicated PUCCH is located after the Msg4 hybrid automatic repeat request confirmation HARQ-ACK, and / or the transmission of the dedicated 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.

[0084] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information includes at least one of the following: a repeat transmission capability and a repeat transmission request.

[0085] In combination with some embodiments of the fourth aspect, in some embodiments, the first information is the second information, and the second information is used to indicate to the network device the capability of the terminal to repeat transmission of the common PUCCH.

[0086] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second information is carried based on at least one of the following: a service data unit SDU in the random access information Msg3, or a media access control unit subheader.

[0087] In combination with some embodiments of the fourth aspect, in some embodiments, the first information is third information, and the third information is used to separately indicate to the network device the capability of the terminal to repeatedly transmit the dedicated PUCCH.

[0088] In conjunction with some embodiments of the fourth aspect, in some embodiments, the third information is carried based on at least one of the following: Msg1, Msg A, Msg3, and Msg5.

[0089] In conjunction with some embodiments of the fourth aspect, in some embodiments, the third information is carried based on an independent random access channel PRACH in Msg1 and / or Msg A. The independent PRACH is configured by a network device and has different time-frequency domain resources from the traditional PRACH. And / or, the independent PRACH resource is configured by the network device and uses a different preamble sequence than the traditional PRACH.

[0090] In combination with some embodiments of the fourth aspect, in some embodiments, the third information is based on at least one of the following carried by Msg3 and / or Msg A physical uplink shared channel PUSCH: an independent demodulation reference signal DMRS, the independent DMRS and the traditional DMRS corresponding to at least one of the following different: time domain, code domain and frequency domain. A newly added logical channel identifier LCID. Reserved bits in the media access control subheader. Existing MAC CE. A newly added MAC CE. Reserved bits in the RRC setup request RRCsetupRequest message. A newly added bit in the RRCsetupRequest message. Reserved bits in the RRC recovery request message. A newly added bit in the RRC recovery request message. Reserved bits in the RRC reconstruction request message. A newly added bit in the RRC reconstruction request message. Newly added RRC capability signaling carried in the packet data unit MAC PDU. Newly added physical layer bits in the payload.

[0091] In combination with some embodiments of the fourth aspect, in some embodiments, the third information is carried based on at least one of the following items in Msg5: an independent demodulation reference signal DMRS, and the independent DMRS is different from the traditional DMRS in corresponding to at least one of the following items: time domain, code domain and frequency domain. Newly added LCID. Reserved bit in the media access control subheader. Existing MAC CE. Newly added MAC CE. Reserved bit in the RRCsetupComplete message of RRC setup completion. Newly added bit in the RRCsetupComplete message. Reserved bit in the RRC recovery complete message. Newly added bit in the RRC recovery complete message. Reserved bit in the RRC reconstruction complete message. Newly added bit in the RRC reconstruction complete message. Newly added RRC capability signaling in the packet data unit MAC PDU. Newly added physical layer bit in the payload.

[0092] In combination with some embodiments of the fourth aspect, in some embodiments, the transceiver module 6101 is also used to: in response to receiving fourth information sent by the network device, send first information to the network device, and the fourth information is used to explicitly instruct the terminal to send the first information.

[0093] In combination with some embodiments of the fourth aspect, in some embodiments, the transceiver module 6101 is also used to: in response to receiving fourth information sent by the network device, send first information to the network device, and the fourth information is used to implicitly instruct the terminal to send the first information.

[0094] In conjunction with some embodiments of the fourth aspect, in some embodiments, the fourth information includes at least one of the following: a number of repeated transmissions, a set of repeated transmission numbers, and a threshold value of reference signal received power (RSRP).

[0095] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module 6101 is further configured to: in response to the network device configuring a threshold value for the reference signal received power (RSRP) corresponding to dedicated PUCCH repetition, the terminal supports dedicated PUCCH repetition, and the RSRP measurement value of the terminal is lower than the threshold value, send a repeat transmission request. In response to the network device not configuring the threshold value, the terminal supports dedicated PUCCH repetition, and the terminal sends a repeat transmission capability.

[0096] In conjunction with some embodiments of the fourth aspect, in some embodiments, the terminal 6100 further includes a processing module 6102, configured to determine a threshold value of RSRP corresponding to the dedicated PUCCH repetition in at least one of the following ways: determining a threshold value of RSRP corresponding to the dedicated PUCCH, which is the same as a threshold value of RSRP corresponding to the common PUCCH; and receiving fifth information sent by a network device, where the fourth information is used to configure the threshold value of RSRP corresponding to the dedicated PUCCH.

[0097] In conjunction with some embodiments of the fourth aspect, in some embodiments, the fifth information is carried by at least one of the following: SIB1, other system message OSI, Msg4.

[0098] According to a fifth aspect of an embodiment of the present disclosure, a network device is provided, including: a transceiver module, configured to receive first information sent by a terminal, wherein the first information is configured to indicate to the network device that the terminal expects a dedicated physical uplink control channel (PUCCH) to perform repeated transmission.

[0099] In combination with some embodiments of the fifth aspect, in some embodiments, the dedicated PUCCHMsg is transmitted using PUCCH parameters configured by radio resource control RRC signaling, and the RRC signaling is carried based on the random access message Msg4.

[0100] In conjunction with some embodiments of the fifth aspect, in some embodiments, dedicated PUCCH transmission occurs after Msg4 Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK). And / or, dedicated PUCCH transmission occurs before the terminal sends first signaling, where the first signaling includes at least one of the following: terminal capability information or terminal reconfiguration completion information.

[0101] With reference to some embodiments of the fifth aspect, in some embodiments, the first information includes at least one of the following: a repeat transmission capability and a repeat transmission request.

[0102] In combination with some embodiments of the fifth aspect, in some embodiments, the first information is the second information, and the second information is used to indicate to the network device the capability of the terminal to repeatedly transmit the common PUCCH.

[0103] In conjunction with some embodiments of the fifth aspect, in some embodiments, the second information is carried based on at least one of the following: a service data unit SDU in the random access information Msg3, and a media access control unit subheader.

[0104] In combination with some embodiments of the fifth aspect, in some embodiments, the first information is third information, and the third information is used to separately indicate to the network device the capability of the terminal to repeatedly transmit the dedicated PUCCH.

[0105] In conjunction with some embodiments of the fifth aspect, in some embodiments, the third information is carried based on at least one of the following: Msg1, Msg A, Msg3, and Msg5.

[0106] In conjunction with some embodiments of the fifth aspect, in some embodiments, the third information is carried based on an independent random access channel PRACH in Msg1 and / or Msg A, where the independent PRACH is configured by a network device and has different time-frequency domain resources from the traditional PRACH. And / or, the independent PRACH resource is configured by the network device and uses a different preamble sequence from the traditional PRACH.

[0107] In combination with some embodiments of the fifth aspect, in some embodiments, the third information is based on at least one of the following carrying items of the physical uplink shared channel PUSCH of Msg3 and / or Msg A: an independent demodulation reference signal DMRS, and the independent DMRS is different from the traditional DMRS in corresponding to at least one of the following items: time domain, code domain and frequency domain. A newly added logical channel identifier LCID. Reserved bits in the media access control subheader. Existing MAC CE. A newly added MAC CE. Reserved bits in the RRC setup request RRCsetupRequest message. A newly added bit in the RRCsetupRequest message. Reserved bits in the RRC recovery request message. A newly added bit in the RRC recovery request message. Reserved bits in the RRC reconstruction request message. A newly added bit in the RRC reconstruction request message. Newly added RRC capability signaling carried in the packet data unit MAC PDU. Newly added physical layer bits in the payload.

[0108] In combination with some embodiments of the fifth aspect, in some embodiments, the third information is carried based on at least one of the following items in Msg5: an independent demodulation reference signal DMRS, and the independent DMRS is different from the traditional DMRS in corresponding to at least one of the following items: time domain, code domain and frequency domain. Newly added logical channel identifier. Reserved bit in the media access control subheader. Existing MAC CE. Newly added MAC CE. Reserved bit in the RRCsetupComplete message of RRC setup completion. Newly added bit in the RRCsetupComplete message. Reserved bit in the RRC recovery complete message. Newly added bit in the RRC recovery complete message. Reserved bit in the RRC reconstruction complete message. Newly added bit in the RRC reconstruction complete message. Newly added RRC capability signaling in the packet data unit MAC PDU. Newly added physical layer bit in the payload.

[0109] In combination with some embodiments of the fifth aspect, in some embodiments, the transceiver module 6201 is further used to: send fourth information to the terminal, where the fourth information is used to explicitly instruct the terminal to send the first information.

[0110] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module 6201 is further used to: send fourth information to the terminal, and the fourth information is used to implicitly instruct the terminal to send the first information

[0111] In conjunction with some embodiments of the fifth aspect, in some embodiments, the fourth information includes at least one of the following: a number of repeated transmissions, a set of repeated transmission numbers, and a threshold value of reference signal received power (RSRP).

[0112] In combination with some embodiments of the fifth aspect, in some embodiments, the method further includes: sending fifth information to the terminal, where the fifth information is used to configure a threshold value of RSRP corresponding to the dedicated PUCCH.

[0113] In conjunction with some embodiments of the fifth aspect, in some embodiments, the fifth information is carried by at least one of the following: SIB1, other system message OSI, Msg4.

[0114] 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.

[0115] 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.

[0116] 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.

[0117] 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.

[0118] 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.

[0119] 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.

[0120] 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.

[0121] 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.

[0122] 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.

[0123] 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.

[0124] 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.

[0125] 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.

[0126] 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.

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

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

[0129] 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.

[0130] 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.

[0131] 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.

[0132] 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.

[0133] 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.

[0134] 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.

[0135] 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.

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

[0137] 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.

[0138] 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.

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

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

[0141] 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.

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

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

[0144] 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.

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

[0146] 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.

[0147] 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 the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0148] 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.

[0149] 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).

[0150] 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.

[0151] 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.

[0152] 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).

[0153] 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.

[0154] 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.

[0155] 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,

[0156] Table 1

[0157] 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.

[0158] In some embodiments, a network device may configure a dedicated PUCCH resource via Msg4 for transmission of uplink control information (UCI) such as HARQ-ACK after the terminal establishes an RRC connection and before the terminal capability message is reported and the RRC reconfiguration message is sent. 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).

[0159] 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.

[0160] 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.

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

[0162] Step S2101 , the network device 102 sends fourth information to the terminal 101 .

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

[0164] In some embodiments, the fourth information is used to instruct the terminal to transmit the first information. For example, the fourth information is used to explicitly instruct the terminal to transmit the first information. The first information is used to indicate to the network device that the terminal expects repeated transmissions on the dedicated PUCCH. The explicit instruction can be understood as the network device directly instructing the terminal to transmit the first information. For example, the fourth information can be a 1-bit enable signaling signal specifically used to instruct the terminal to transmit the first information.

[0165] In some embodiments, the fourth information is used to implicitly instruct the terminal to send the first information. Implicit instruction can be understood as the network device indirectly notifying the terminal that it can send the first information through the fourth information, although it does not explicitly instruct the terminal to send the first information.

[0166] In some embodiments, when the fourth information is used to implicitly instruct the terminal to send the first information, the fourth information includes at least one of the following: the number of repeated transmissions; the set of repeated transmission numbers; and the threshold value of RSRP.

[0167] In some embodiments, when the fourth information includes the number of repeated transmissions, it can be determined that the network device supports repeated transmission by the terminal, that is, implicitly indicates that the terminal can send the first information to the network device.

[0168] In some embodiments, when the fourth information includes a set of repeated transmission times, the set of repeated transmission times includes at least two repeated transmission times. The terminal may determine the repeated transmission times from the set of repeated transmission times. The network device may also dynamically instruct the terminal to use a certain repeated transmission time from the set of repeated transmission times. In other words, it may be determined that the network device supports repeated transmissions by the terminal, implicitly instructing the terminal to send the first information to the network device.

[0169] In some embodiments, when the fourth information includes an RSRP threshold, the RSRP threshold is used for repeated transmission. For example, when the RSRP value measured by the terminal is lower than the RSRP threshold, the terminal may send a repeated transmission request to the network device. In other words, it may be determined that the network device supports repeated transmission by the terminal, implicitly indicating that the terminal may send the first information to the network device.

[0170] In some embodiments, the fourth information may include the number of repeated transmissions and the RSRP threshold value. When the fourth information includes the number of repeated transmissions and the RSRP threshold value, it can be more certain that the network device supports repeated transmission by the terminal, that is, the first information can be sent to the network device.

[0171] In some embodiments, the fourth information may include a set of repeated transmission times and a threshold value of RSRP. When the fourth information includes a set of repeated transmission times and a threshold value of RSRP, it can be more certain that the network device supports repeated transmission by the terminal, that is, the first information can be sent to the network device.

[0172] In some embodiments, the fourth information may include a number of repeated transmissions and a set of repeated transmission numbers. When the fourth information includes the number of repeated transmissions and the set of repeated transmission numbers, the terminal may perform repeated transmissions based on the number of repeated transmissions, based on the set of repeated transmission numbers, or based on an instruction from the network device to perform repeated transmissions using either method. In other words, it may be determined that the network device supports repeated transmissions by the terminal, and the first information may be sent to the network device.

[0173] In some embodiments, the fourth information may include the number of repeated transmissions, a set of repeated transmission numbers, and a threshold value of RSRP.

[0174] In some embodiments, the terminal sends first information to the network device. Since the first information indicates that the terminal expects repeated transmission of dedicated PUCCH, the network device can configure relevant resources for repeated transmission of dedicated PUCCH for the terminal, thereby achieving coverage enhancement for dedicated PUCCH of the terminal.

[0175] In some embodiments, the fourth information may be carried based on at least one of the following: system information block 1 (SIB1); Msg 4. For example, the fourth information is carried by RRC signaling carried by Msg 4.

[0176] In some implementations, the name of the fourth information is not limited, and it can be, for example, "instruction information", "configuration information", etc.

[0177] Step S2102 , the network device 102 sends fifth information to the terminal 101 .

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

[0179] In some embodiments, the fifth information is used to configure a threshold value of RSRP corresponding to the dedicated PUCCH.

[0180] In some embodiments, the fifth information may be specifically used to configure the RSRP threshold value corresponding to the dedicated PUCCH, and may also be used to configure the RSRP threshold value corresponding to the common PUCCH and the RSRP threshold value corresponding to the dedicated PUCCH. When the fifth information is used to configure the RSRP threshold value corresponding to the common PUCCH and the RSRP threshold value corresponding to the dedicated PUCCH, the RSRP threshold value corresponding to the common PUCCH and the RSRP threshold value corresponding to the dedicated PUCCH may be the same or different. For example, the fifth information may indicate only one RSRP threshold value, and both the common PUCCH and the dedicated PUCCH use this RSRP threshold value, that is, the RSRP threshold value corresponding to the common PUCCH and the RSRP threshold value corresponding to the dedicated PUCCH are the same. For another example, the fifth information may indicate the RSRP threshold value corresponding to the common PUCCH and the RSRP threshold value corresponding to the dedicated PUCCH, respectively. In this case, the RSRP threshold value corresponding to the common PUCCH and the RSRP threshold value corresponding to the dedicated PUCCH may be the same or different. It will be understood that the above situation is for example only and is not limited in this disclosure. In this disclosure, the RSRP threshold value and the RSRP threshold value have the same meaning and can be used interchangeably.

[0181] In some embodiments, the network device may also configure the RSRP threshold value corresponding to the common PUCCH to the terminal using other information. The terminal may determine that the RSRP threshold value corresponding to the dedicated PUCCH is the same as the RSRP threshold value corresponding to the common PUCCH. In other words, the network device does not need to separately configure the RSRP threshold value corresponding to the dedicated PUCCH for the terminal.

[0182] In some embodiments, the fifth information is carried based on at least one of the following: SIB1; other system information (OSI); Msg4.

[0183] In some embodiments, after receiving the fifth information, the terminal may send a repeat transmission request to the network device when the RSRP value measured by the terminal is lower than the RSRP threshold value.

[0184] In some embodiments, the fourth information and the fifth information may be the same or different. For example, when the fourth information and the fifth information are the same, the fourth information may include the RSRP threshold corresponding to the dedicated PUCCH, configure the RSRP threshold corresponding to the dedicated PUCCH for the terminal, and implicitly instruct the terminal to send the first information. For another example, when the fourth information and the fifth information are different, the fourth information may include at least one of a 1-bit enable signaling, a number of repeated transmissions, and a set of repeated transmission numbers. The fourth information is used to instruct the terminal to send the first information, and the fifth information is used to configure the RSRP threshold corresponding to the dedicated PUCCH.

[0185] In some implementations, the name of the fifth information is not limited, and it can be, for example, "configuration information" or the like.

[0186] Step S2103 , the terminal 101 sends first information to the network device 102 .

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

[0188] In some embodiments, the first information is used to indicate to the network device that the terminal expects the dedicated PUCCH to be repeatedly transmitted.

[0189] In some embodiments, dedicated PUCCH is transmitted using PUCCH parameters configured by RRC signaling, where the RRC signaling is carried over Msg4.

[0190] In some embodiments, the network device may configure PUCCH parameters to the terminal through RRC signaling carried by Msg4, and the dedicated PUCCH uses the PUCCH parameters for transmission.

[0191] In some embodiments, the transmission of dedicated PUCCH is located after Msg4 HARQ-ACK. Or, the transmission of dedicated PUCCH is located before the terminal sends the first signaling. Or, the transmission of dedicated PUCCH is located after Msg4 HARQ-ACK and before the terminal sends the first signaling. The transmission of dedicated PUCCH is located after Msg4 HARQ-ACK, which means that the terminal sends dedicated PUCCH for uplink transmission after sending the Msg4 HARQ-ACK message. For example, dedicated PUCCH can be used to transmit at least one of the following: HARQ-ACK message, SR, channel state information CSI. The Msg4 HARQ-ACK message can represent the terminal's feedback on the Msg4 sent by the network device, and the HARQ-ACK message transmitted by the dedicated PUCCH can 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. The first signaling includes at least one of the following: terminal capability information; terminal reconfiguration completion information. That is, the transmission of the dedicated 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 dedicated 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 dedicated PUCCH can be at all times before the terminal sends the UE capability signaling. For another example, the transmission of the dedicated PUCCH can be at all times before the terminal sends the RRCReconfigurationComplete. For another example, the transmission of the dedicated PUCCH can 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 transmission of the dedicated PUCCH can be after the terminal sends the Msg4 HARQ-ACK message to the network device and before the terminal sends the RRCReconfigurationComplete.

[0192] In some embodiments, before the terminal sends the UE capability signaling, the terminal sends the repetition transmission capability of the dedicated PUCCH. It is understandable that the repetition transmission capability of the dedicated PUCCH does not belong to the UE capability signaling.

[0193] In some embodiments, the first information includes at least one of the following: repetition capability reporting; and repetition request.

[0194] In some embodiments, if the network device configures an RSRP threshold for the terminal, a repeat transmission request may be sent when the RSRP value measured by the terminal is lower than the RSRP threshold and the terminal supports dedicated PUCCH repetition. That is, the first information may include a repeat transmission request. In this disclosure, the RSRP value measured by the terminal may be referred to as the RSRP measurement value.

[0195] In some embodiments, if the network device does not configure the RSRP threshold for the terminal and the terminal supports dedicated PUCCH repetition, the retransmission capability is sent to the network device. That is, the first information may include the retransmission capability.

[0196] In some embodiments, the terminal may send a retransmission capability and a retransmission request to the network device, that is, the first information may include the retransmission capability and the retransmission request.

[0197] In some embodiments, when the network device configures an RSRP threshold value for the terminal and the RSRP measurement value is higher than the RSRP threshold value, the terminal may temporarily not send the first information. Alternatively, the RSRP measurement value may be monitored and the first information may be sent when the RSRP value is lower than the RSRP threshold value.

[0198] In some embodiments, the first information may be second information, where the second information is used to indicate the terminal's common PUCCH retransmission capability to the network device, thereby indirectly reporting the dedicated PUCCH retransmission capability. That is, the network device may determine that the dedicated PUCCH retransmission capability is the same as the common PUCCH retransmission capability. When the first information is second information, the dedicated PUCCH retransmission capability is sent to the network device along with the common PUCCH retransmission capability via the first information.

[0199] In some embodiments, the second information may be carried based on at least one of the following: a service data unit (SDU) in Msg3; or a medium access control element (MAC CE) subheader. For example, the second information may be carried based on a reserved bit in a Msg3 SDU. For another example, the second information may be carried based on a reserved bit in a MAC CE subheader. Of course, this disclosure is merely an example and is not intended to be limiting.

[0200] In some embodiments, the first information may be third information. The third information is used to separately indicate to the network device the terminal's dedicated PUCCH retransmission capability. That is, the common PUCCH retransmission capability can be reported to the network device via other means. The dedicated PUCCH retransmission capability and the common dedicated PUCCH retransmission capability can be the same or different. Alternatively, the common PUCCH retransmission capability may not be reported to the network device, and this disclosure is not limited to this.

[0201] In some embodiments, the third information is carried based on at least one of the following: Msg1; Msg A; Msg3; Msg5.

[0202] In some embodiments, the third information may be carried based on Msg1 and / or Msg A. For example, a field may be added to the feature combination. When the third information is carried based on Msg1 and / or Msg A, the third information may be carried based on an independent random access channel (separate PRACH) in Msg1 and / or Msg A. Separate PRACH is a channel configured by a network device and has different time-frequency domain resources from traditional PRACH. Or, separate PRACH is a channel configured by a network device and uses a different preamble sequence from traditional PRACH. Time-frequency domain resources include time domain resources and frequency domain resources. Traditional PRACH can be understood as an existing PRACH. For example, traditional PRACH can represent a PRACH already existing in the protocol, or a PRACH in a traditional terminal. It can also be understood as a PRACH that supports dedicated PUCCH.

[0203] In some embodiments, the network device may configure separate PRACH resources for the terminal.

[0204] In some embodiments, when the third information is carried based on Msg3 and / or Msg A, the third information can be carried based on at least one of the following in the physical uplink shared channel (PUSCH) of Msg3 and / or Msg A: a separate demodulation reference signal (separate DMRS), the independent DMRS and the traditional DMRS corresponding to at least one of the following differences: time domain, code domain and frequency domain; a newly added logical channel identification (LCID); a reserved bit in the MAC subheader; an existing MAC CE; a newly added (new) MAC CE; a reserved bit in the RRC setup request (RRCsetupRequest) message; a newly added bit in the RRCsetupRequest message; a reserved bit in the RRC recovery request message; a newly added bit in the RRC recovery request message; a reserved bit in the RRC reconstruction request message; a newly added bit in the RRC reconstruction request message; a MAC packet data unit (packet data unit); The newly added RRC capability signaling is carried in the data unit (PDU); the newly added physical layer bit is in the payload.

[0205] In some embodiments, the third information can be carried by an independent DMRS, where the independent DMRS is a DMRS that differs from a conventional DMRS in at least one of the time domain, code domain, and frequency domain. A conventional DMRS can be understood as an existing DMRS. For example, the independent DMRS can be a DMRS that differs from a conventional DMRS in the time domain. Another example is a DMRS that differs from a conventional DMRS in the code domain. Another example is a DMRS that differs from a conventional DMRS in the frequency domain.

[0206] In some embodiments, the network device may configure independent DMRS resources for the terminal.

[0207] In some embodiments, the third information can be carried by the newly added LCID. The newly added LCID can be used alone to carry the third information.

[0208] In some embodiments, the third information may be carried in a reserved bit in a MAC subheader. For example, the MAC subheader may be at least one of a MAC SDU subheader or a MAC CE subheader.

[0209] In some embodiments, the third information may be carried by an existing MAC CE (legacy MAC CE). The existing MAC CE may be, for example, a buffer status report (BSR) or a timing advance command (TAC). However, it should be understood that this disclosure is merely an example and not a limitation.

[0210] In some embodiments, the third information may be carried by a newly added MAC CE. The newly added MAC CE may be, for example, a MAC CE dedicated to carrying the third information.

[0211] In some embodiments, the third information may be carried by a reserved bit in the RRCsetupRequest message, that is, when the RRCsetupRequest message is sent, the retransmission capability of the dedicated PUCCH of the terminal is reported to the network device.

[0212] In some embodiments, the third information can be carried by adding bits to the RRCsetupRequest message. Specifically, one or more bits are added to the RRCsetupRequest message to carry the third information. The terminal's dedicated PUCCH retransmission capability can also be reported to the network device when the RRCReestablishment message is sent.

[0213] In some embodiments, the third information may be carried by a reserved bit in the RRC recovery request (RRCResumeRequest) message, that is, when the RRCResumeRequest message is sent, the retransmission capability of the terminal dedicated PUCCH is reported to the network device.

[0214] In some embodiments, the third information can be carried by adding bits to the RRCResumeRequest message. That is, one or more bits are added to the RRCResumeRequest message to carry the third information. The terminal's dedicated PUCCH retransmission capability can be reported to the network device when the RRCReestablishment message is sent.

[0215] In some embodiments, the third information may be carried via a reserved bit in an RRC reestablishment request (RRCReestablishment) message, that is, when the RRCReestablishment message is sent, the retransmission capability of the dedicated PUCCH of the terminal is reported to the network device.

[0216] In some embodiments, the third information can be carried by adding bits to the RRCReestablishment message. Specifically, one or more bits are added to the RRCReestablishment message to carry the third information. When the RRCReestablishment message is sent, the terminal's dedicated PUCCH retransmission capability can also be reported to the network device.

[0217] In some embodiments, the third information may be carried by adding RRC capability signaling to the MAC PDU. For example, RRC capability signaling may be added to Msg3 and carried in the MAC PDU for reporting.

[0218] In some embodiments, the third information may be carried by a newly added physical layer bit in the payload. For example, after the MAC PDU is delivered to the physical layer, a physical layer bit is added to the payload to indicate the third information.

[0219] In some embodiments, when the third information is carried based on Msg5, the third information can be carried based on at least one of the following items in Msg5: an independent DMRS, which is different from the traditional DMRS in at least one of the time domain, code domain, and frequency domain; a newly added LCID; a reserved bit in the MAC subheader; an existing MAC CE; a newly added MAC CE; a reserved bit in the RRC setup complete (RRCsetupComplete) message; a newly added bit in the RRCsetupComplete message; a reserved bit in the RRC recovery complete (RRCResumeComplete) message; a newly added bit in the RRCResumeComplete message; a reserved bit in the RRC reestablishment complete (RRCReestablishmentComplete) message; a newly added bit in the RRCReestablishmentComplete message; newly added RRC capability signaling carried in a MAC packet data unit (PDU); and a newly added physical layer bit in the payload. For specific implementation methods, reference may be made to the above-mentioned embodiments related to Msg3 and / or MsgA, and this disclosure will not be repeated here.

[0220] In some embodiments, when the third information is carried based on a separate PRACH in Msg1 and / or Msg A, the network can be configured with a separate PRACH resource to determine that the network supports dedicated PUCCH repetition, and the third information can be sent to the network device. When the third information is carried based on Msg1 and / or Msg A, or carried based on Msg5, the third information can be sent to the network device after receiving the fourth information, i.e., the first information is sent to the network device.

[0221] In some embodiments, after receiving the first information, the network device may configure and / or indicate the number of repeated transmissions of the dedicated PUCCH to the terminal, so that the terminal can perform repeated transmissions and improve the transmission performance of the PUCCH.

[0222] In some embodiments, after receiving the first information, the network device may indicate to the terminal that the number of repeated transmissions is 1, or may not indicate it. If the network device indicates to the terminal that the number of repeated transmissions is 1, it means that the transmission is performed once, that is, no repeated transmission is performed.

[0223] In some embodiments, the network device may directly indicate the number of repetitions via a PUCCH resource indicator (PRI). For example, each PUCCH corresponds to a number of repetitions, and the number of repetitions may be indirectly indicated by indicating the PUCCH resource.

[0224] In some embodiments, the names of the first information, the second information, and the third information are not limited. For example, the first information, the second information, or the third information may be "indication information," "capability information," or the like.

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

[0226] 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.

[0227] 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.

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

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

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

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

[0232] 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:

[0233] Step S3101, obtain the fourth information.

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

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

[0236] In some embodiments, terminal 101 obtains fourth information specified by the protocol.

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

[0238] In some embodiments, the terminal 101 performs processing to obtain the fourth information.

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

[0240] Step S3102, obtain the fifth information.

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

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

[0243] In some embodiments, terminal 101 obtains fifth information specified by the protocol.

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

[0245] In some embodiments, the terminal 101 performs processing to obtain the fifth information.

[0246] In some embodiments, step S3102 is omitted, and the terminal 101 autonomously implements the function indicated by the fifth information, or the above function is default or by default.

[0247] Step S3103, sending the first information.

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

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

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

[0251] In some embodiments, step S3101 and step S3102 may be executed in an interchanged order or simultaneously.

[0252] In some embodiments, step S3101 and step S3102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0254] 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:

[0255] Step S3201, sending the first information.

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

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

[0258] In some embodiments, the dedicated PUCCH is transmitted using PUCCH parameters configured by radio resource control RRC signaling, and the RRC signaling is carried based on the random access message Msg4.

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

[0260] In some embodiments, the first information includes at least one of the following: a repeat transmission capability and a repeat transmission request.

[0261] In some embodiments, the first information is the second information, and the second information is used to indicate to the network device the capability of the terminal to repeat common PUCCH transmission.

[0262] In some embodiments, the second information is carried based on at least one of the following: a service data unit SDU in the random access message Msg3, and a media access control unit subheader.

[0263] In some embodiments, the first information is third information, and the third information is used to separately indicate to the network device the capability of the terminal to repeatedly transmit the dedicated PUCCH.

[0264] In some embodiments, the third message is carried based on at least one of the following: Msg1, Msg A, Msg3, or Msg5.

[0265] In some embodiments, the third information is carried on an independent random access channel (PRACH) in Msg1 and / or Msg A. The independent PRACH is configured by a network device and has different time-frequency domain resources than a traditional PRACH. And / or, the independent PRACH resources are configured by a network device and use a different preamble sequence than a traditional PRACH.

[0266] In some embodiments, the third information is based on at least one of the following items carried by the physical uplink shared channel PUSCH of Msg3 and / or Msg A: an independent demodulation reference signal DMRS, the independent DMRS being different from at least one of the time domain, code domain, and frequency domain of the traditional DMRS. A newly added logical channel identifier LCID. A reserved bit in the media access control subheader. An existing MAC CE. A newly added MAC CE. A reserved bit in the RRC setup request RRCsetupRequest message. A newly added bit in the RRCsetupRequest message. A reserved bit in the RRC recovery request message. A newly added bit in the RRC recovery request message. A reserved bit in the RRC reconstruction request message. A newly added bit in the RRC reconstruction request message. A newly added RRC capability signaling carried in the packet data unit MAC PDU. A newly added physical layer bit in the payload.

[0267] In some embodiments, the third information is carried based on at least one of the following items in Msg5: an independent demodulation reference signal DMRS, which is different from at least one of the time domain, code domain, and frequency domain of the traditional DMRS. A newly added logical channel identifier. A reserved bit in the media access control subheader. An existing MAC CE. A newly added MAC CE. The reserved bit in the RRCsetupComplete message of the RRC setup completion. A newly added bit in the RRCsetupComplete message. The reserved bit in the RRC recovery complete message. The newly added bit in the RRC recovery complete message. The reserved bit in the RRC reconstruction complete message. The newly added bit in the RRC reconstruction complete message. The newly added RRC capability signaling in the packet data unit MAC PDU. The newly added physical layer bit in the payload.

[0268] In some embodiments, in response to receiving fourth information sent by the network device, the first information is sent to the network device, and the fourth information is used to explicitly instruct the terminal to send the first information.

[0269] In some embodiments, in response to receiving the fourth information sent by the network device, the first information is sent to the network device, and the fourth information is used to implicitly instruct the terminal to send the first information.

[0270] In some embodiments, the fourth information includes at least one of the following: a number of repeated transmissions, a set of repeated transmission numbers, and a threshold value of reference signal received power (RSRP).

[0271] In some embodiments, in response to the network device configuring a threshold value for reference signal received power (RSRP) corresponding to dedicated PUCCH repetition, the terminal supports dedicated PUCCH repetition, and the RSRP measurement value of the terminal is lower than the threshold value, the terminal sends a retransmission request. In response to the network device not configuring the threshold value, the terminal supports dedicated PUCCH repetition, and the terminal sends a retransmission capability.

[0272] In some embodiments, the RSRP threshold corresponding to the dedicated PUCCH repetition is determined using at least one of the following methods: determining the RSRP threshold corresponding to the dedicated PUCCH to be the same as the RSRP threshold corresponding to the common PUCCH; and receiving fifth information sent by the network device, wherein the fourth information is used to configure the RSRP threshold corresponding to the dedicated PUCCH.

[0273] In some embodiments, the fifth information is carried by at least one of the following: SIB1, other system message OSI, Msg4.

[0274] 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:

[0275] Step S4101, sending the fourth information.

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

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

[0278] Step S4102, sending the fifth information.

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

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

[0281] Step S4103, obtaining first information.

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

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

[0284] In some embodiments, the network device 102 obtains first information specified by the protocol.

[0285] In some embodiments, the network device 102 obtains the first information from an upper layer(s).

[0286] In some embodiments, the network device 102 performs processing to obtain the first information.

[0287] In some embodiments, step S4103 is omitted, and the network device 102 autonomously implements the function indicated by the first information, or the above function is default or by default.

[0288] 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:

[0289] Step S4201, obtain first information.

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

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

[0292] In some embodiments, the network device 102 obtains first information specified by the protocol.

[0293] In some embodiments, the network device 102 obtains the first information from an upper layer(s).

[0294] In some embodiments, the network device 102 performs processing to obtain the first information.

[0295] In some embodiments, step S4201 is omitted, and the network device 102 autonomously implements the function indicated by the first information, or the above function is default or by default.

[0296] 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:

[0297] Step S5101: Terminal 101 sends first information to network device 102.

[0298] Optional implementations of step S5101 may refer to S2103 in FIG. 2 , step S3103 in FIG. 3 a , and other related parts in the embodiments involved in FIG. 2 and FIG. 3 a , which will not be described in detail here.

[0299] 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.

[0300] Step S5102: The network device 102 receives first information.

[0301] Optional implementations of step S5102 can be found in S2103 of FIG. 2 , step S3103 of FIG. 3 a , and other related parts in the embodiments involved in FIG. 2 and FIG. 3 a , which will not be described in detail here.

[0302] 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.

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

[0304] In some embodiments, the terminal may report dedicated PUCCH repetition-related capabilities in advance, and the network device may obtain the dedicated PUCCH repetition-related capabilities of the terminal and perform reasonable configuration or scheduling of dedicated PUCCH repetition.

[0305] In some embodiments, terminal capabilities may be reported in at least one of the following ways:

[0306] 1) Bundle the dedicated PUCCH repetition capability with the common PUCCH repetition capability and indicate them together through the spare bit in the subheader of the Msg3SDU or MAC CE.

[0307] In some embodiments, if an RSRP threshold is configured, a terminal supporting PUCCH repetition makes a PUCCH repetition request only when the RSRP measurement value is lower than the threshold.

[0308] In some embodiments, the RSRP threshold may be a threshold value of RSRP, which have the same meaning and can be used interchangeably.

[0309] In some embodiments, if the RSRP threshold is not configured, a terminal supporting PUCCH repetition performs PUCCH repetition capability reporting.

[0310] 2) The terminal reports the first information to the gNB separately. Specifically, the dedicated PUCCH repetition capability indication can be provided via Msg1 / A / 3 / 5.

[0311] In some embodiments, the terminal capability indication is performed based on the Msg1 / A PRACH resource, for example, a field is added to the feature combination.

[0312] In some embodiments, the base station may configure a set of separate PRACH resources for dedicated PUCCH repetition capability reporting. For example, the separate PRACH resource may have the same random access opportunity as the traditional PRACH, but with separate preambles (shared RO with separate preambles). Alternatively, the separate PRACH resource may be a separate random access channel configuration (separate PRACH configuration).

[0313] In some embodiments, terminal capability indication may be performed based on Msg3 / A PUSCH.

[0314] In some embodiments, the indication may be based on the Msg3separate DMRS resource. For example, the Msg3separate DMRS resource is different from the traditional DMRS in at least one of the time domain, code domain, and frequency domain.

[0315] In some embodiments, a new LCID can be introduced, or the spare bit in the subheader of the MAC SDU or MAC CE can be used, or the legacy MAC CE or new MAC CE can be used, or the spare bit or a newly added bit in RRCsetupRequest, RRCResumeRequest, or RRCReestablishment can be used. Alternatively, a new RRC capability signaling bearer can be designed and reported in the Msg3 MAC PDU. Alternatively, after the MAC PDU is handed over to the physical layer, a physical layer bit can be added to the payload to indicate the capability.

[0316] In some embodiments, the terminal capability indication may be performed based on Msg5 to enhance the uplink coverage of the subsequent dedicated PUCCH.

[0317] In some embodiments, the indication may be based on Msg5 separate DMRS resource.

[0318] In some embodiments, a new LCID can be used, or the spare bit in the MAC subheader can be used, or the legacy or new MAC CE can be used, or the reserved bit or newly added field in RRCResumeComplete, RRCsetupComplete, or RRCReestablishmentComplete can be used, or a new RRC capability signaling bearer can be designed to be reported in the Msg5 MAC PDU. Alternatively, after the MAC PDU is handed over to the physical layer, a physical layer bit can be added to the payload to indicate the capability.

[0319] In some embodiments, for terminal capability indication based on Msg3 / A PUSCH or based on a separate DMRS resource in Msg5, SIB1 or Msg4 RRC signaling may optionally indicate whether the terminal reports dedicated PUCCH repetition capability. For example, only if SIB1 or Msg4 RRC carries configuration parameters related to dedicated PUCCH repetition, or if dedicated PUCCH repetition is enabled as indicated by the first field of SIB1 or Msg4 RRC, can the terminal indicate terminal capability based on Msg3 / A PUSCH or based on a separate DMRS resource in Msg5. For terminal capability indication based on Msg1 / A PUSCH, whether the gNB is configured with a separate PRACH resource can be used to directly determine whether the current network device supports subsequent dedicated PUCCH repetition.

[0320] In some embodiments, if the network side configures an RSRP threshold, the terminal makes a dedicated PUCCH repetition request only when the RSRP measurement value is lower than the threshold; if the network side does not configure an RSRP threshold, the terminal supporting dedicated PUCCH repetition performs dedicated PUCCH repetition capability reporting.

[0321] In some embodiments, the RSRP threshold may share the threshold of the common PUCCH repetition, or may be a separate RSRP threshold configured by the network device and different from the common PUCCH repetition.

[0322] In some embodiments, the RSRP threshold may be configured based on RRC signaling carried by SIB1, OSI, or Msg4.

[0323] In some embodiments, the terminal reports a dedicated PUCCH repetition request, and the gNB configures and / or instructs the terminal on the number of subsequent dedicated PUCCH repetitions.

[0324] In some embodiments, even if the terminal reports the terminal capability and / or repetition request, the gNB may indicate to the terminal that the number of repetitions is 1, or not configure or indicate repetition.

[0325] In some embodiments, the repetition number indication may be performed directly through the PRI.

[0326] Figure 6a is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure. As shown in Figure 6a, terminal 6100 may include a transceiver module 6101. Transceiver module 6101 is configured to send first information to a network device, indicating to the network device that the terminal expects repeated transmission of a dedicated physical uplink control channel (PUCCH). Dedicated PUCCHMsg is transmitted using PUCCH parameters configured by radio resource control (RRC) signaling, which is carried over random access message Msg4.

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

[0328] In some embodiments, the first information includes at least one of the following: a repeat transmission capability and a repeat transmission request.

[0329] In some embodiments, the first information is the second information, and the second information is used to indicate to the network device the capability of the terminal to repeat common PUCCH transmission.

[0330] In some embodiments, the second information is carried based on at least one of the following: a reserved bit in a service data unit SDU in the random access message Msg3, or a reserved bit in a media access control unit subheader.

[0331] In some embodiments, the first information is third information, and the third information is used to separately indicate to the network device the capability of the terminal to repeatedly transmit the dedicated PUCCH.

[0332] In some embodiments, the third message is carried based on at least one of the following: Msg1, Msg A, Msg3, or Msg5.

[0333] In some embodiments, the third information is carried on an independent random access channel (PRACH) in Msg1 and / or Msg A. The independent PRACH is configured by a network device and has different time-frequency domain resources than a traditional PRACH. And / or, the independent PRACH resources are configured by a network device and use a different preamble sequence than a traditional PRACH.

[0334] In some embodiments, the third information is based on at least one of the following carried by the physical uplink shared channel PUSCH of Msg3 and / or Msg A: an independent demodulation reference signal DMRS, the independent DMRS and the traditional DMRS corresponding to at least one of the following different: time domain, code domain and frequency domain. A newly added logical channel identifier LCID. A reserved bit in the media access control subheader. An existing MAC CE. A newly added MAC CE. A reserved bit in the RRC setup request RRCsetupRequest message. A newly added bit in the RRCsetupRequest message. A reserved bit in the RRC recovery request message. A newly added bit in the RRC recovery request message. A reserved bit in the RRC reconstruction request message. A newly added bit in the RRC reconstruction request message. A newly added RRC capability signaling carried in the packet data unit MAC PDU. A newly added physical layer bit in the payload.

[0335] In some embodiments, the third information is carried based on at least one of the following items in Msg5: an independent demodulation reference signal DMRS, the independent DMRS and the traditional DMRS correspond to at least one of the following different items: time domain, code domain and frequency domain. A newly added logical channel identifier. A reserved bit in the media access control subheader. An existing MAC CE. A newly added MAC CE. The reserved bit in the RRCsetupComplete message of RRC setup completion. A newly added bit in the RRCsetupComplete message. The reserved bit in the RRC recovery complete message. The newly added bit in the RRC recovery complete message. The reserved bit in the RRC reconstruction complete message. The newly added bit in the RRC reconstruction complete message. The newly added RRC capability signaling in the packet data unit MAC PDU. The newly added physical layer bit in the payload.

[0336] In some embodiments, the transceiver module 6101 is also used to: send first information to the network device in response to receiving fourth information sent by the network device, the fourth information is used to explicitly instruct the terminal to send the first information, or the fourth information is used to implicitly instruct the terminal to send the first information.

[0337] In some embodiments, the fourth information is used to implicitly instruct the terminal to send the first information, and the second information includes at least one of the following: a number of repeated transmissions, a set of repeated transmissions, and a threshold value of reference signal received power (RSRP).

[0338] In some embodiments, the transceiver module 6101 is further configured to: in response to the network device configuring a threshold value for reference signal received power (RSRP) corresponding to dedicated PUCCH repetition, the terminal supporting dedicated PUCCH repetition, and the RSRP measurement value of the terminal being lower than the threshold value, send a repeat transmission request; and in response to the network device not configuring the threshold value, the terminal supporting dedicated PUCCH repetition, the terminal sending a repeat transmission capability.

[0339] In some embodiments, the terminal 6100 further includes a processing module 6102 configured to determine a threshold value of RSRP corresponding to the dedicated PUCCH repetition in at least one of the following ways: determining a threshold value of RSRP corresponding to the dedicated PUCCH that is the same as a threshold value of RSRP corresponding to the common PUCCH; and receiving fifth information sent by the network device, wherein the fourth information is used to configure the threshold value of RSRP corresponding to the dedicated PUCCH.

[0340] In some embodiments, the fifth information is carried by at least one of the following: SIB1, other system message OSI, Msg4.

[0341] In some embodiments, the fourth information is the same as or different from the fifth information.

[0342] Figure 6b is a schematic diagram of the structure of a network device according to an embodiment of the present disclosure. As shown in Figure 6b, network device 6200 may include a transceiver module 6201. Transceiver module 6201 is configured to receive first information sent by a terminal. The first information indicates to the network device that the terminal expects a dedicated physical uplink control channel (PUCCH) to perform repetition transmission. Dedicated PUCCHMsg is transmitted using PUCCH parameters configured by radio resource control (RRC) signaling. The RRC signaling is carried over random access message Msg4.

[0343] In some embodiments, the dedicated PUCCH is transmitted using PUCCH parameters configured by radio resource control RRC signaling, and the RRC signaling is carried based on the random access message Msg4.

[0344] In some embodiments, the dedicated PUCCH is transmitted after the Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) message in Msg4. And / or, the dedicated 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 or terminal reconfiguration completion information.

[0345] In some embodiments, the first information includes at least one of the following: a repeat transmission capability and a repeat transmission request.

[0346] In some embodiments, the first information is the second information, and the second information is used to indicate to the network device the capability of the terminal to repeat common PUCCH transmission.

[0347] In some embodiments, the second information is carried based on at least one of the following: a service data unit SDU in the random access message Msg3, and a media access control unit subheader.

[0348] In some embodiments, the first information is third information, and the third information is used to separately indicate to the network device the capability of the terminal to repeatedly transmit the dedicated PUCCH.

[0349] In some embodiments, the third message is carried based on at least one of the following: Msg1, Msg A, Msg3, or Msg5.

[0350] In some embodiments, the third information is carried on an independent random access channel (PRACH) in Msg1 and / or Msg A. The independent PRACH is configured by a network device and has different time-frequency domain resources than a traditional PRACH. And / or, the independent PRACH resources are configured by a network device and use a different preamble sequence than a traditional PRACH.

[0351] In some embodiments, the third information is based on at least one of the following carried by the physical uplink shared channel PUSCH of Msg3 and / or Msg A: an independent demodulation reference signal DMRS, the independent DMRS and the traditional DMRS corresponding to at least one of the following different: time domain, code domain and frequency domain. A newly added logical channel identifier LCID. A reserved bit in the media access control subheader. An existing MAC CE. A newly added MAC CE. A reserved bit in the RRC setup request RRCsetupRequest message. A newly added bit in the RRCsetupRequest message. A reserved bit in the RRC recovery request message. A newly added bit in the RRC recovery request message. A reserved bit in the RRC reconstruction request message. A newly added bit in the RRC reconstruction request message. A newly added RRC capability signaling carried in the packet data unit MAC PDU. A newly added physical layer bit in the payload.

[0352] In some embodiments, the third information is carried based on at least one of the following items in Msg5: an independent demodulation reference signal DMRS, the independent DMRS and the traditional DMRS correspond to at least one of the following different items: time domain, code domain and frequency domain. A newly added logical channel identifier. A reserved bit in the media access control subheader. An existing MAC CE. A newly added MAC CE. The reserved bit in the RRCsetupComplete message of RRC setup completion. A newly added bit in the RRCsetupComplete message. The reserved bit in the RRC recovery complete message. The newly added bit in the RRC recovery complete message. The reserved bit in the RRC reconstruction complete message. The newly added bit in the RRC reconstruction complete message. The newly added RRC capability signaling in the packet data unit MAC PDU. The newly added physical layer bit in the payload.

[0353] In some embodiments, the transceiver module 6201 is further used to: send fourth information to the terminal, where the fourth information is used to explicitly instruct the terminal to send the first information.

[0354] In some embodiments, the transceiver module 6201 is further used to: send fourth information to the terminal, where the fourth information is used to implicitly instruct the terminal to send the first information.

[0355] In some embodiments, the fourth information includes at least one of the following: a number of repeated transmissions, a set of repeated transmission numbers, and a threshold value of reference signal received power (RSRP).

[0356] In some embodiments, the method further includes: sending fifth information to the terminal, where the fifth information is used to configure a threshold value of RSRP corresponding to the dedicated PUCCH.

[0357] In some embodiments, the fifth information is carried by at least one of the following: SIB1, other system message OSI, Msg4.

[0358] 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.

[0359] 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.

[0360] 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.

[0361] 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.

[0362] 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.

[0363] 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.

[0364] 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.

[0365] 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.

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

[0367] 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.

[0368] 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.

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

[0370] 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.

[0371] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 7100, the communication device 7100 executes 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.

[0372] 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.

[0373] 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: First information is sent to a network device, where the first information is used to indicate to the network device that the terminal expects a dedicated physical uplink control channel dedicated PUCCH to perform repetition transmission.

2. The method according to claim 1, characterized in that: The dedicated PUCCH is transmitted using PUCCH parameters configured by radio resource control RRC signaling, and the RRC signaling is carried based on a random access message Msg4.

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

4. The method according to any one of claims 1 to 3, characterized in that: The first information includes at least one of the following: Repeat transmission capability; Repeat the transfer request.

5. The method according to any one of claims 1 to 4, characterized in that: The first information is the second information, and the second information is used to indicate to the network device the capability of the terminal common PUCCH repeated transmission.

6. The method according to claim 5, characterized in that The second information is carried based on at least one of the following: Service data unit SDU in random access information Msg3; The media access control unit is in the subheader.

7. The method according to any one of claims 1 to 4, characterized in that: The first information is third information, and the third information is used to separately indicate to the network device the capability of the terminal to repeatedly transmit dedicated PUCCH.

8. The method according to claim 7, characterized in that The third information is carried based on at least one of the following: Msg1; Msg A; Msg3; Msg5.

9. The method according to claim 8, characterized in that The third information is based on the independent random access channel PRACH carried by the Msg1 and / or the Msg A, the independent PRACH is configured by the network device and has different time and frequency domain resources from the traditional PRACH; and / or the independent PRACH resources are configured by the network device and use a different preamble sequence from the traditional PRACH.

10. The method according to any one of claims 8 to 9, characterized in that: The third information is carried based on at least one of the following items of the Msg3 and / or the Msg A physical uplink shared channel PUSCH: An independent demodulation reference signal DMRS, wherein the independent DMRS is different from a conventional DMRS in at least one of the following: time domain, code domain, and frequency domain; Newly added logical channel identifier LCID; Reserved bits in the media access control subheader; Existing MAC CE; Newly added MAC CE; The reserved bit in the RRC setup request RRCsetupRequest message; A newly added bit in the RRCsetupRequest message; Reserved bits in the RRC recovery request message; A newly added bit in the RRC recovery request message; Reserved bits in the RRC Reestablishment Request message; A newly added bit in the RRC reestablishment request message; The packet data unit MAC PDU carries the newly added RRC capability signaling; New physical layer bits added to the payload.

11. The method according to any one of claims 8 to 10, characterized in that: The third information is carried based on at least one of the following items in the Msg5: An independent demodulation reference signal DMRS, wherein the independent DMRS is different from a conventional DMRS in at least one of the following: time domain, code domain, and frequency domain; Newly added logical channel identifier; Reserved bits in the media access control subheader; Existing MAC CE; Newly added MAC CE; The reserved bit in the RRCsetupComplete message of RRC setup completion; A newly added bit in the RRCsetupComplete message; Reserved bits in the RRC recovery complete message; A newly added bit in the RRC recovery complete message; Reserved bits in the RRC Reestablishment Complete message; A newly added bit in the RRC reestablishment complete message; New RRC capability signaling in the packet data unit MAC PDU; New physical layer bits added to the payload.

12. The method according to any one of claims 1, characterized in that: In response to receiving fourth information sent by the network device, the first information is sent to the network device, wherein the fourth information is used to explicitly instruct the terminal to send the first information.

13. The method according to claim 1, characterized in that In response to receiving fourth information sent by the network device, the first information is sent to the network device, wherein the fourth information is used to implicitly instruct the terminal to send the first information.

14. The method according to claim 12, characterized in that The fourth information includes at least one of the following: Number of retransmissions; A set of repetition transmission times; The threshold value of the reference information received power RSRP.

15. The method according to any one of claims 3, characterized in that: In response to the network device configuring a threshold value of a reference signal received power RSRP corresponding to the dedicated PUCCH repetition, the terminal supports the dedicated PUCCH repetition, and the RSRP measurement value of the terminal is lower than the threshold value, sending the repeated transmission request; In response to the network device not configuring the threshold value, the terminal supports the dedicated PUCCH repetition, and the terminal sends the retransmission capability.

16. The method according to claim 15, characterized in that The RSRP threshold corresponding to the dedicated PUCCH repetition is determined by at least one of the following methods: Determine a threshold value of RSRP corresponding to the dedicated PUCCH, which is the same as the threshold value of RSRP corresponding to the common PUCCH; Fifth information sent by a network device is received, where the fifth information is used to configure a threshold value of RSRP corresponding to the dedicated PUCCH.

17. The method according to claim 16, characterized in that The fifth information is carried by at least one of the following: SIB1; Other system messages OSI; Msg4.

18. A communication method, characterized in that: The method is performed by a network device, and the method includes: A first information sent by a terminal is received, where the first information is used to indicate to a network device that the terminal expects a dedicated physical uplink control channel dedicated PUCCH to perform repetition transmission.

19. The method according to claim 18, characterized in that The dedicated PUCCH is transmitted using PUCCH parameters configured by radio resource control RRC signaling, and the RRC signaling is carried based on a random access message Msg4.

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

21. The method according to any one of claims 18 to 20, characterized in that: The first information includes at least one of the following: Repeat transmission capability; Repeat the transfer request.

22. The method according to any one of claims 18 to 21, characterized in that: The first information is the second information, and the second information is used to indicate to the network device the capability of the terminal common PUCCH repeated transmission.

23. The method according to claim 22, characterized in that The second information is carried based on at least one of the following: Service data unit SDU in random access information Msg3; The media access control unit is in the subheader.

24. The method according to any one of claims 18 to 22, characterized in that: The first information is third information, and the third information is used to separately indicate to the network device the capability of the terminal to repeatedly transmit dedicated PUCCH.

25. The method according to claim 24, characterized in that The third information is carried based on at least one of the following: Msg1; Msg A; Msg3; Msg5.

26. The method according to claim 25, characterized in that The third information is based on an independent random access channel PRACH carried in the Msg1 and / or the Msg A, the independent PRACH is configured by a network device and has different time-frequency domain resources from the traditional PRACH; and / or the independent PRACH resources are configured by a network device and use a different preamble sequence from the traditional PRACH.

27. The method according to any one of claims 25-26, characterized in that The third information is carried based on at least one of the following items of the Msg3 and / or the Msg A physical uplink shared channel PUSCH: An independent demodulation reference signal DMRS, wherein the independent DMRS is different from a conventional DMRS in at least one of the following: time domain, code domain, and frequency domain; Newly added logical channel identifier LCID; Reserved bits in the media access control subheader; Existing MAC CE; Newly added MAC CE; The reserved bit in the RRC setup request RRCsetupRequest message; A newly added bit in the RRCsetupRequest message; Reserved bits in the RRC recovery request message; A newly added bit in the RRC recovery request message; Reserved bits in the RRC Reestablishment Request message; A newly added bit in the RRC reestablishment request message; The packet data unit MAC PDU carries the newly added RRC capability signaling; New physical layer bits added to the payload.

28. The method according to any one of claims 25 to 27, characterized in that: The third information is carried based on at least one of the following items in the Msg5: An independent demodulation reference signal DMRS, wherein the independent DMRS is different from a conventional DMRS in at least one of the following: time domain, code domain, and frequency domain; Newly added LCIDs; Reserved bits in the media access control subheader; Existing MAC CE; Newly added MAC CE; The reserved bit in the RRCsetupComplete message of RRC setup completion; A newly added bit in the RRCsetupComplete message; Reserved bits in the RRC recovery complete message; A newly added bit in the RRC recovery complete message; Reserved bits in the RRC Reestablishment Complete message; A newly added bit in the RRC reestablishment complete message; New RRC capability signaling in the packet data unit MAC PDU; New physical layer bits added to the payload.

29. The method according to claim 18, characterized in that The method further comprises: Sending fourth information to the terminal, where the fourth information is used to explicitly instruct the terminal to send the first information.

30. The method according to claim 18, characterized in that The method further comprises: Sending fourth information to the terminal, where the fourth information is used to implicitly instruct the terminal to send the first information.

31. The method according to claim 30, characterized in that The fourth information includes at least one of the following: Number of retransmissions; A set of repetition transmission times; The threshold value of the reference information received power RSRP.

32. The method according to any one of claims 21, characterized in that The method further comprises: Sending fifth information to the terminal, where the fifth information is used to configure a threshold value of RSRP corresponding to the dedicated PUCCH.

33. The method according to claim 32, characterized in that The fifth information is carried by at least one of the following: SIB1; Other system messages OSI; Msg4.

34. A communication method, characterized in that: The method comprises: The terminal sends first information to the network device, where the first information is used to indicate to the network device that the terminal expects a dedicated physical uplink control channel dedicated PUCCH to perform repetition transmission; The network device receives first information.

35. A terminal, characterized in that: include: The transceiver module is used to send first information to the network device, where the first information is used to indicate to the network device that the terminal expects a dedicated physical uplink control channel dedicated PUCCH to perform repeated transmission repetition.

36. A network device, characterized in that: include: The transceiver module is used to receive first information sent by the terminal, where the first information is used to indicate to the network device that the terminal expects a dedicated physical uplink control channel dedicated PUCCH to perform repeated transmission repetition.

37. 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 to 17.

38. 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 18-33.

39. 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 17, and the network device is configured to implement the communication method according to any one of claims 18 to 33.

40. 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 according to any one of claims 1-17 or 18-33.

Images