CN117997491A

CN117997491A - Retransmission method and equipment for Msg4 hybrid automatic repeat request acknowledgement

Info

Publication number: CN117997491A
Application number: CN202211380061.6A
Authority: CN
Inventors: 丁勇; 云翔; 肖昌文; 张博广; 孙立新
Original assignee: Baicells Technologies Co Ltd
Current assignee: Baicells Technologies Co Ltd
Priority date: 2022-11-04
Filing date: 2022-11-04
Publication date: 2024-05-07
Also published as: WO2024093048A1

Abstract

The application provides a retransmission method and equipment for Msg4 hybrid automatic repeat request confirmation, and relates to the technical field of wireless communication, wherein the method comprises the following steps: acquiring the repeated transmission times of the PUCCH corresponding to the user terminal according to the user request signaling and/or the network indication signaling; and after the Msg4 is sent, repeatedly receiving the Msg4 hybrid automatic repeat request acknowledgement fed back by the user terminal according to the repeated transmission times. The application realizes the repeated transmission of the Msg4 hybrid automatic repeat request acknowledgement by determining the repeated transmission times of the Msg4 hybrid automatic repeat request acknowledgement, thereby effectively avoiding the influence of the path loss and the limit of the transmitting power of the user terminal on the transmission of the Msg4 hybrid automatic repeat request acknowledgement, being beneficial to completing the random access process and improving the service quality of the communication network.

Description

Retransmission method and equipment for Msg4 hybrid automatic repeat request acknowledgement

Technical Field

The application relates to the technical field of wireless communication, in particular to a retransmission method and equipment for Msg4 hybrid automatic repeat request confirmation.

Background

Coverage is one of the key factors of a communication network, which directly affects the quality of service and the operating costs of the communication network. Among them, how to enhance the physical uplink control channel (Physical Uplink Control Channel, abbreviated PUCCH) is an important research direction. In the 5G New air interface (New Radio abbreviated NR) technology, PUCCH is required for carrying a hybrid automatic repeat request ACKnowledgement (HARQ-ACK) of Msg 4. In the current 5G NR standard, repeated transmission of PUCCH carrying Msg4 HARQ-ACK is not supported, so in the case where path loss is large and the transmit power of a User Equipment (UE) is limited, especially for a 5G NR Non-terrestrial network (Non-TERRESTRIAL NETWORK, NTN for short), or a 5G-based satellite access system, the base station side may not correctly detect the PUCCH, and cannot complete the response of the random access procedure Msg4, and thus cannot complete the random access procedure.

Disclosure of Invention

The technical purpose to be achieved by the embodiment of the application is to provide a retransmission method and equipment for Msg4 hybrid automatic repeat request confirmation, which are used for solving the problem that the random access process cannot be completed in the current 5G NR technology without supporting the retransmission of the PUCCH of Msg4 hybrid automatic repeat request confirmation.

In order to solve the above technical problems, an embodiment of the present application provides a retransmission method for Msg4 hybrid automatic repeat request acknowledgement, which is applied to a network side device, and includes:

acquiring the repeated transmission times of a Physical Uplink Control Channel (PUCCH) corresponding to a user terminal according to user request signaling and/or network indication signaling, wherein the user request signaling comprises the following steps: msg1 request and/or Msg3 request, the network indication signaling comprising: public signaling and/or user-specific signaling;

And repeatedly receiving the Msg4 hybrid automatic repeat request acknowledgement fed back by the user terminal according to the repeat transmission times after the Msg4 is sent.

Specifically, the repeated transmission method as described above, according to the user request signaling, obtains the repeated transmission times, including:

acquiring first information of whether the user terminal supports the repeated transmission of the PUCCH from the Msg1 request or the Msg3 request;

And when the first information indicates that the user terminal supports the repeated transmission of the PUCCH, acquiring the repeated transmission times from the Msg1 request or the Msg3 request.

Specifically, according to the repeated transmission method described above, according to the user request signaling and the network indication signaling, the obtaining the repeated transmission times includes:

and acquiring first information of whether the user terminal supports the repeated transmission of the PUCCH from the Msg1 request or the Msg3 request, and acquiring the repeated transmission times according to the network indication signaling.

Specifically, the repeated transmission method as described above, according to the common signaling in the network indication signaling, obtains the repeated transmission times, including:

According to a first field or a first mixed field of a first signaling of the common signaling, acquiring the repeated transmission times from a first configuration list, wherein the first mixed field comprises at least two first fields, and the first signaling comprises: at least one of radio resource control (Radio Resource Control, abbreviated RRC) signaling, system information block (System Information Block, abbreviated SIB) signaling, master information block (Main Information Block, abbreviated MIB) signaling, and common downlink control information (Downlink Control Information, abbreviated DCI);

Or obtaining a second configuration list about the number of repeated transmissions from a second signaling of the common signaling, or obtaining a first configuration set in the first configuration list from the second signaling, and obtaining the number of repeated transmissions from the second configuration list or the first configuration set according to a third signaling of the common signaling, where the second signaling includes: the RRC signaling and/or the SIB signaling, and the third signaling includes: the MIB signaling and/or the common DCI;

Or the second configuration list is obtained from the second signaling, a second configuration set in the second configuration list is obtained from the first signaling, and the repeated transmission times are obtained from the second configuration set according to the third signaling.

Specifically, the repeated transmission method as described above, according to the user-specific signaling in the network indication signaling, obtains the repeated transmission times, including:

Acquiring the number of repeated transmissions from a first configuration list about the number of repeated transmissions according to a second field or a second mixed field in a fourth signaling of the user-specific signaling, wherein the second mixed field comprises at least two second fields, and the fourth signaling comprises: at least one of DCI scheduling Msg2, DCI scheduling Msg3, DCI scheduling Msg4, msg2 and Msg 4;

Or obtaining a second configuration list about the number of repeated transmissions from a fifth signaling of the user specific signaling, or obtaining a first configuration set in the first configuration list from the fifth signaling, and obtaining the number of repeated transmissions from the second configuration list or the first configuration set according to a sixth signaling of the user specific signaling, where the fifth signaling includes: the raf information of MSg2 and/or the Msg4, the sixth signaling comprising: at least one of DCI of the scheduling Msg2, DCI of the scheduling Msg3, DCI of the scheduling Msg4, and RAR UL GRANT information of MSg;

Or the second configuration list is obtained from the fifth signaling, the second configuration set in the second configuration list is obtained from the fourth signaling, and the repeated transmission times are obtained from the second configuration set according to the sixth signaling.

Specifically, the repeated transmission method as described above, according to the common signaling and the user-specific signaling in the network indication signaling, obtains the repeated transmission times, including:

Acquiring a first configuration set in a first configuration list about the number of repeated transmissions or a second configuration list about the number of repeated transmissions from the common signaling, and acquiring the number of repeated transmissions from the first configuration set or the first configuration list according to the user-specific signaling, wherein the common signaling comprises: at least one of RRC signaling, SIB signaling, MIB signaling, and common DCI, the user-specific signaling including: at least one of DCI scheduling Msg2, DCI scheduling Msg3, DCI scheduling Msg4, msg2 and Msg 4;

or the second configuration list is obtained from the public signaling, a second configuration set of the second configuration list is obtained from the public signaling or the user special signaling, and the repeated transmission times are obtained from the second configuration set according to the user special signaling.

Another embodiment of the present application further provides a retransmission method for Msg4 hybrid automatic repeat request acknowledgement, which is applied to a user terminal, and includes:

Transmitting a user request signaling to a network side device, wherein the user request signaling carries at least one of first information and repeated transmission times of whether the user terminal supports repeated transmission of a Physical Uplink Control Channel (PUCCH), and the user request signaling comprises: msg1 request and/or Msg3 request;

And repeatedly sending Msg4 hybrid automatic repeat request acknowledgement to the network side equipment according to the repeat transmission times after receiving Msg4 sent by the network side equipment under the condition that the user terminal supports the repeat transmission of the PUCCH.

Another embodiment of the present application further provides a network side device, including:

The first processing module is configured to obtain, from a user request signaling and/or a network indication signaling, a number of repeated transmissions of a PUCCH corresponding to a user terminal, where the user request signaling includes: msg1 request and/or Msg3 request, the network indication signaling comprising: public signaling and/or user-specific signaling;

And the second processing module is used for repeatedly receiving the Msg4 hybrid automatic repeat request acknowledgement fed back by the user terminal according to the repeat transmission times after the Msg4 is sent.

Another embodiment of the present application also provides a user terminal, including:

A third processing module, configured to send a user request signaling to a network side device, where the user request signaling carries first information and/or a number of repeated transmissions of whether the user terminal supports repeated transmission of a PUCCH, and the user request signaling includes: msg1 request and/or Msg3 request;

And the fourth processing module is used for repeatedly sending the Msg4 hybrid automatic repeat request acknowledgement to the network side equipment according to the repeat transmission times after receiving the Msg4 sent by the network side equipment under the condition that the user terminal supports the repeat transmission of the PUCCH.

Another embodiment of the present application further provides an electronic device, including a processor, a memory, and a computer program stored on the memory and executable on the processor, where the computer program when executed by the processor implements the steps of the retransmission method for Msg4 hybrid automatic repeat request acknowledgement applied to a network side device as described above, or implements the steps of the retransmission method for Msg4 hybrid automatic repeat request acknowledgement applied to a user terminal as described above.

Another embodiment of the present application also provides a computer readable storage medium having a computer program stored thereon, which when executed by a processor, implements the steps of the retransmission method for Msg4 hybrid automatic repeat request acknowledgement applied to a network side device as described above, or implements the steps of the retransmission method for Msg4 hybrid automatic repeat request acknowledgement applied to a user terminal as described above.

Compared with the prior art, the retransmission method and the device for the Msg4 hybrid automatic repeat request acknowledgement have the following advantages:

In the random access process of the user terminal and the network side equipment, the application firstly determines the repeated transmission times for transmitting the Msg4 hybrid automatic repeat request acknowledgement, and then carries out the repeated transmission of the Msg4 hybrid automatic repeat request acknowledgement according to the repeated transmission times, thereby realizing the repeated transmission of the Msg4 hybrid automatic repeat request acknowledgement, effectively avoiding the influence of the limitation of path loss and transmitting power of the user terminal on the transmission of the Msg4 hybrid automatic repeat request acknowledgement, being beneficial to completing the random access process and further improving the service quality of the communication network.

Drawings

Fig. 1 is a flowchart of a retransmission method of Msg4 hybrid automatic repeat request acknowledgement applied to a network side device;

Fig. 2 is a flow chart of a retransmission method of Msg4 h-arq acknowledgement applied to a ue;

fig. 3 is a schematic structural diagram of a network side device;

Fig. 4 is a schematic structural diagram of a user terminal.

Detailed Description

In order to make the technical problems, technical solutions and advantages to be solved more apparent, the following detailed description will be given with reference to the accompanying drawings and specific embodiments. In the following description, specific details such as specific configurations and components are provided merely to facilitate a thorough understanding of embodiments of the application. It will therefore be apparent to those skilled in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the application. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness.

It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

In various embodiments of the present application, it should be understood that the sequence numbers of the following processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

It should be understood that the term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

In the embodiments provided herein, it should be understood that "B corresponding to a" means that B is associated with a from which B may be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may also determine B from a and/or other information.

It should be noted that, the network side device in the present application includes, but is not limited to, a base station.

Referring to fig. 1, an embodiment of the present application provides a retransmission method for Msg4 hybrid automatic repeat request acknowledgement, which is applied to a network side device and includes:

Step S101, according to user request signaling and/or network indication signaling, obtaining the repeated transmission times of a Physical Uplink Control Channel (PUCCH) corresponding to a user terminal, wherein the user request signaling comprises: msg1 request and/or Msg3 request, the network indication signaling comprising: public signaling and/or user-specific signaling;

Step S102, after sending the Msg4, repeatedly receiving the Msg4 hybrid automatic repeat request acknowledgement fed back by the user terminal according to the repeat transmission times.

In the random access process, after receiving the Msg4 sent by the network side device, the terminal sends an Msg4 hybrid automatic repeat request acknowledgement to the network side device side, so that the network side device can accurately receive the Msg4 hybrid automatic repeat request acknowledgement, and the user terminal preferably adopts a repeat transmission mode, so that the network side device and the user terminal are ensured to be in butt joint. The method solves the problem that the prior 5G NR technology does not support the repeated transmission of the Msg4 hybrid automatic repeat request acknowledgement. When the number of repeated transmissions of the PUCCH is acquired, the number of repeated transmissions may be acquired from the user request signaling or the network indication signaling, or the number of repeated transmissions may be acquired by combining the user request signaling and the network indication signaling. Preferably, the user request signaling includes: the Msg1 request and/or Msg3 request, the network indication signaling includes: public signaling and/or user-specific signaling.

In summary, in the random access process of the user terminal and the network side device, the method and the device of the application firstly determine the number of times of repeated transmission for transmitting the Msg4 hybrid automatic repeat request acknowledgement, and then perform repeated transmission of the Msg4 hybrid automatic repeat request acknowledgement according to the number of times of repeated transmission, thereby realizing repeated transmission of the Msg4 hybrid automatic repeat request acknowledgement, effectively avoiding the influence of the path loss and the transmitting power limitation of the user terminal on the transmission of the Msg4 hybrid automatic repeat request acknowledgement, and being beneficial to completing the random access process, thereby improving the service quality of the communication network.

In an embodiment of the present application, when the network side device only obtains the number of repeated transmissions from the user request signaling, preferably, first information about whether the corresponding user terminal supports PUCCH repeated transmission is obtained from the Msg1 request or the Msg3 request, if the first information indicates that the user terminal does not support repeated transmission, it may be determined that the user terminal cannot repeatedly send the Msg4 hybrid automatic repeat request acknowledgement, so that the network side device does not need to repeatedly receive the Msg4 hybrid automatic repeat request acknowledgement when performing random access;

When the first information indicates that the user terminal supports PUCCH retransmission, it may be determined that the user terminal can retransmit the Msg4 hybrid automatic repeat request acknowledgement, where the network side device needs to repeatedly receive the Msg4 hybrid automatic repeat request acknowledgement to ensure that the Msg4 hybrid automatic repeat request acknowledgement can be correctly received, and at this time, the retransmission times may be obtained from the Msg1 request or the Msg3 request.

In an embodiment, when the first information and the number of retransmissions are requested to be carried by Msg1, the first information and the number of retransmissions may be carried in a Physical Random Access Channel (PRACH) preamble index, i.e. PRACH preamble index.

In another embodiment, when the first information and the number of retransmissions are both requested to be carried by the Msg3, the first information and the number of retransmissions may be carried in a signaling requested by the Msg3, for example: the signaling carrying the first information is: msg4-PUCCH-repetitioncapabilityindicator ENUMERATED { Enable, disable }, wherein Enable indicates support for PUCCH retransmission and Disable indicates no support for PUCCH retransmission; the signaling carrying the number of repeated transmissions is: msg4-Pucch-RepetitionNrofSlots ENUMERATED { n ₁,n₂, …, m }, where n ₁,n₂, …, m indicate the specific number of repeated transmissions.

In another embodiment, the first information and the number of repeated transmissions may be respectively requested by the Msg1 and the Msg3, preferably, the first information is requested by the Msg1, for example: the number of retransmissions is requested to be carried by Msg3 in a predetermined PRACH preamble index, for example: carried in signaling Msg4-Pucch-RepetitionNrofSlots ENUMERATED { n ₁,n₂, …, m }.

It should be noted that, the first information described herein includes, but is not limited to, a specific information, or a conventional information that can be identified by the network side device, and the network side device can determine whether the ue supports PUCCH retransmission according to the conventional information.

In an embodiment of the present application, when the network side device needs to acquire the number of repeated transmissions according to the user request signaling and the network indication signaling, preferably, first information about whether the corresponding user terminal supports PUCCH repeated transmission is acquired from the Msg1 request or the Msg3 request, if the first information indicates that the user terminal does not support repeated transmission, it may be determined that the user terminal cannot repeat transmission of the Msg4 hybrid automatic repeat request acknowledgement, and when random access is performed, the network side device does not need to repeatedly receive the Msg4 hybrid automatic repeat request acknowledgement, and at this time, the network side device may no longer acquire the number of repeated transmissions according to the network indication signaling, or fix the number of repeated transmissions acquired according to the network indication signaling to 1, or send the network indication signaling carrying the number of repeated transmissions to the user terminal.

If the first information indicates that the user terminal supports PUCCH retransmission, it may be determined that the user terminal can retransmit the Msg4 hybrid automatic repeat request acknowledgement, where the network side device needs to repeatedly receive the Msg4 hybrid automatic repeat request acknowledgement to ensure that the Msg4 hybrid automatic repeat request acknowledgement can be correctly received, and at this time, the specific retransmission times may be obtained according to the network indication signaling, and optionally, the retransmission times may be carried in the network indication signaling and sent to the user terminal.

In a specific embodiment, the first information is carried in PRACH preamble index of the Msg1 request, or in Msg4-Pucch-RepetitionNrofSlots ENUMERATED { n ₁,n₂, …, m } of the Msg3 request.

In an embodiment of the present application, when the network side device needs to acquire the number of repeated transmissions according to the network indication signaling (including acquiring the number of repeated transmissions according to the network indication signaling only and acquiring the first information from the Msg1 request or the Msg3 request, and acquiring the number of repeated transmissions according to the network indication signaling), the network side device may specifically acquire the number of repeated transmissions according to the common signaling and/or the user-specific signaling in the network indication signaling, and the following discussion will be made according to the acquisition of the common signaling, the acquisition of the user-specific signaling, and the acquisition of 3 cases according to the common signaling and the user-specific signaling, respectively.

According to a first field or a first mixed field of a first signaling of the common signaling, acquiring the repeated transmission times from a first configuration list, wherein the first mixed field comprises at least two first fields, and the first signaling comprises: at least one of radio resource control RRC signaling, system information block SIB signaling, master information block MIB signaling, and common downlink control information DCI;

In the case where the number of repeated transmissions is acquired based only on common signaling, since the common signaling may include a plurality of sub-signaling, for example: RRC signaling, SIB signaling, MIB signaling, and common DCI; the number of retransmissions may be carried in one sub-signaling or in multiple sub-signaling.

In an embodiment, when the number of retransmissions is carried in one sub-signaling, the number of retransmissions may be obtained from the first configuration list according to a first field or a first mixed field of a first signaling of the common signaling, where the first mixed field includes at least two first fields, preferably at least part of bits in the at least two first fields, and the first signaling includes: at least one of RRC signaling, SIB signaling, MIB signaling, and common DCI, the first configuration list is a configuration list predetermined according to a protocol with respect to the number of repeated transmissions.

In a specific embodiment, when the first signaling is RRC signaling or SIB signaling, the first field is: msg4-Pucch-RepetitionNrofSlots ENUMERATED { n ₁,n₂, …, m }, where n ₁,n₂, …, m indicate a specific number of retransmissions in the first configuration list, and the first configuration list corresponds to at least one ue.

In a specific embodiment, when the first signaling is MIB signaling or common DCI, the first field may be a field that does not exist in the original protocol, i.e. a new field, for example: msg4-Pucch-RepetitionNrofSlots indicator-n bit (n is more than or equal to 0); the value {0 … 0,0 … 1, …,1 … 1} of this field may indicate the specific number of retransmissions in the first configuration list;

The first field may also be a part of bits of an existing field in the original protocol, where the value {0 … 0,0 … 1, …,1 … } of the part of bits may indicate a specific number of repeated transmissions in the first configuration list.

In a specific embodiment, when the first signaling is MIB signaling or common DCI, the first mixed field may be a combination of at least two fields in the above existing field, where the existing field includes, but is not limited to, a preset number of most significant bits (Most Significant Bit, MSB for short) and least significant bits (LEAST SIGNIFICANT bit, LSB for short). At this time, the value {0 … 0,0 … 1, …,1 … } of the first mixed field is used to indicate the specific retransmission times in the first configuration list;

Or the first mixed field may be a combination of at least one of the above-mentioned existing fields including, but not limited to, a preset number of MSB bits and LSB bits and a newly added field. At this time, the values {0 …,0 … 1, …,1 … } of the first mixed field are used to indicate the specific number of retransmissions in the first configuration list.

It should be noted that the existing fields in MIB signaling include, but are not limited to: systemFrameNumber fields, subCarrierSpacingCommon fields, ssb-SubcarrierOffset fields, dmrs-TypeA-Position fields, pdcch-ConfigSIB1 fields, celbarred fields, intraFreqReselection fields, spark fields.

Existing fields in common DCI include, but are not limited to: frequency domain resource assignment fields, time domain resource assignment fields, VRB-to-PRB mapping fields, modulation and coding scheme fields, reserved bits fields, short Messages Indicator fields, short Messages fields, TB scaling fields, and TRS availability indication fields.

In another embodiment, when the number of retransmissions is carried in a plurality of sub-signaling, a second configuration list about the number of retransmissions may be obtained from a second signaling of the common signaling, or a first configuration set in the first configuration list may be obtained from the second signaling, and the number of retransmissions may be obtained from the second configuration list or the first configuration set according to a third signaling of the common signaling. Wherein the second signaling comprises: RRC signaling and/or SIB signaling, the third signaling including: MIB signaling and/or common DCI.

Specifically, the signaling or field carrying the second configuration list in the second signaling is denoted by ：numberOfMsg4-PUCCH-RepetitionsList SEQUENCE{n₁,n₂,n₃,n₄,n₅,n₆,n₇,n₈,n₉,n₁₀,n₁₁,n₁₂,n₁₃,n₁₄,n₁₅,n₁₆,…,n_m};, and the signaling or field carrying and repeating the transmission times in the third signaling is denoted by: msg4-Pucch-RepetitionNrofSlots indicator-n bit (n is more than or equal to 0); the value {0 … 0,0 … 1, …,1 … 1} of this field may indicate a specific number of retransmissions, corresponding to a specific value of the second configuration list.

Specifically, the signaling or field in the second signaling that carries the first configuration set is expressed as: numberOfMsg4-PUCCH-RepetitionsList SEQUENCE (SIZE (2 ⁿ (n is 0 or more))) OF NumberOfMsg4-PUCCH-Repetitions; the signaling or field carrying and repeating the number of transmissions in the third signaling is expressed as: msg4-Pucch-RepetitionNrofSlots indicator-n bit (n is more than or equal to 0); the value {0 … 0,0 … 1, …,1 … 1} of this field may indicate a specific number of retransmissions, corresponding to a specific value of the first configuration set.

In another embodiment, when the number of retransmissions is carried in the plurality of sub-signaling, a second configuration list related to the number of retransmissions may be further obtained from a second signaling of the common signaling, a second configuration set in the second configuration list may be obtained from the second signaling, and the number of retransmissions may be obtained from the second configuration set according to a third signaling of the common signaling. Wherein, the signaling or field carrying the second configuration list in the second signaling is denoted by ：numberOfMsg4-PUCCH-RepetitionsList SEQUENCE{n₁,n₂,n₃,n₄,n₅,n₆,n₇,n₈,n₉,n₁₀,n₁₁,n₁₂,n₁₃,n₁₄,n₁₅,n₁₆,…,n_m};, and the signaling or field carrying the second configuration set in the second signaling is denoted by: numberOfMsg4-PUCCH-RepetitionsList SEQUENCE (SIZE (2 ⁿ (n is 0 or more))) OF NumberOfMsg4-PUCCH-Repetitions; the signaling or field carrying the number of repeated transmissions in the third signaling is expressed as: msg4-Pucch-RepetitionNrofSlots indicator-n bit (n is more than or equal to 0); the value {0 … 0,0 … 1, …,1 … 1} of this field may indicate a specific number of retransmissions, corresponding to a specific value of the second configuration set of the second configuration list.

In another embodiment, when the number of retransmissions is carried in the plurality of sub-signaling, a second configuration list related to the number of retransmissions may be further obtained from a second signaling of the common signaling, a second configuration set in the second configuration list may be obtained from the third signaling, and the number of retransmissions may be obtained from the second configuration set according to the third signaling of the common signaling.

Wherein, the signaling or field carrying the second configuration list in the second signaling is denoted by ：numberOfMsg4-PUCCH-RepetitionsList SEQUENCE{n₁,n₂,n₃,n₄,n₅,n₆,n₇,n₈,n₉,n₁₀,n₁₁,n₁₂,n₁₃,n₁₄,n₁₅,n₁₆,…,n_m};, and the signaling or field carrying the second configuration set in the third signaling is denoted by: msg4-Pucch-RepetitionNrofSlots Set indicator-n ₁ bit(n₁ equal to or greater than 0), it should be noted that when n ₁ is equal to 0, it means that the second configuration set is not needed, and it can be directly determined from the second configuration list; the field includes n ₁ MSB bits corresponding to a second configuration set of a second configuration list of a second signaling bearer; the signaling or field carrying the number of repetitions in the third signaling is expressed as: msg4-Pucch-RepetitionNrofSlots indicator-n ₂ bit(n₂ is 0 or more); this field includes n ₂ LSB bits, which together with the n ₁ MSB bits of Msg4-Pucch-RepetitionNrofSlots Set indicator indicate a specific value; the value {0 … 0,0 … 1, …,1 … 1} of this field may indicate a specific number of retransmissions, corresponding to a specific value of the second configuration set of the second configuration list of PUCCH retransmission numbers.

In the case where the number of repeated transmissions is obtained from only common signaling, since the user-specific signaling may include a plurality of sub-signaling, for example: DCI scheduling Msg2, DCI scheduling Msg3, DCI scheduling Msg4, msg2 and Msg4; the number of retransmissions may be carried in one sub-signaling or in multiple sub-signaling.

In an embodiment, when the number of retransmissions is carried in one sub-signaling, the number of retransmissions may be obtained from the first configuration list according to a second field or a second mixed field of a fourth signaling of the user specific signaling, where the second mixed field comprises at least two second fields, preferably at least part of bits in the at least two second fields, and the fourth signaling comprises: at least one of DCI scheduling Msg2, DCI scheduling Msg3, DCI scheduling Msg4, msg2 and Msg4, the first configuration list is a configuration list about the number of repeated transmissions predetermined according to a protocol.

In a specific embodiment, when the fourth signaling is DCI for scheduling Msg2, DCI for scheduling Msg3, DCI for scheduling Msg4, or MSg's RAR UL GRANT information, the second field is: msg4-Pucch-RepetitionNrofSlots ENUMERATED { n ₁,n₂, …, m }, where n ₁,n₂, …, m indicate a specific number of retransmissions in the first configuration list.

In a specific embodiment, when the fourth signaling is DCI for scheduling Msg2, DCI for scheduling Msg3, DCI for scheduling Msg4, or RAR UL GRANT information of MSg2, the second field may be a field that is not existing in the original protocol, i.e. a new field, for example: msg4-Pucch-RepetitionNrofSlots indicator-n bit (n is more than or equal to 0); the value {0 … 0,0 … 1, …,1 … 1} of this field may indicate the specific number of retransmissions in the first configuration list;

The second field may also be a part of bits of an existing field in the original protocol, where the value {0 … 0,0 … 1, …,1 … } of the part of bits may indicate a specific number of repeated transmissions in the first configuration list.

In a specific embodiment, when the fourth signaling is DCI for scheduling Msg2, DCI for scheduling Msg3, DCI for scheduling Msg4, or MSg r UL GRANT information of RAR UL GRANT, the first mixed field may be a combination of at least two fields of the above existing fields. At this time, the values {0 … 0,0 … 1, …,1 … } of the second mixed field are used to indicate the specific retransmission times in the first configuration list;

Or the second mixed field may be a combination of at least one of the existing fields and the newly added field as described above. At this time, the values {0 …,0 … 1, …,1 … } of the second mixed field are used to indicate the specific number of repeated transmissions in the first configuration list.

Note that existing fields in DCI of scheduling Msg2 include, but are not limited to: a TB scaling field, a LSBs of SFN field and a Reserved bits field.

The DCI for scheduling Msg3 is preferably DCI 0_0 of scrambling cyclic redundancy check (Cyclic Redundancy Check, abbreviated CRC) by a temporary cell-radio network temporary identifier (Temporary Cell Radio Network Temporary Identifier, abbreviated TC-RNTI), wherein existing fields include, but are not limited to, HARQ process number field, new data indicator field, downlink assignment index field and TPC command for scheduled PUSCH field.

The DCI for scheduling Msg4 is preferably DCI 1_0 with TC-RNTI scrambling CRC, and existing fields include, but are not limited to HARQ process number fields, downlink assignment index fields, TPC command for scheduled PUSCH fields, PUCCH resource indicator, new data indicator fields and Reserved bit Reserved bits fields.

Existing fields in the RAR information for Msg2 include, but are not limited to: CSI request field, frequency hopping flag field, PUSCH frequency resource allocation field, PUSCH time resource allocation field, MCS field and TPC command for PUSCH field.

In another embodiment, when the number of retransmissions is carried in a plurality of sub-signaling, the second configuration list about the number of retransmissions may be obtained from the fifth signaling of the user-specific signaling, or the first configuration set in the first configuration list may be obtained from the fifth signaling, and the number of retransmissions may be obtained from the second configuration list or the first configuration set according to the sixth signaling of the user-specific signaling. Wherein the fifth signaling comprises: MSg2 and/or the Msg4, the sixth signaling comprises: DCI of scheduling Msg2, DCI of the scheduling Msg3, DCI of the scheduling Msg4 and RAR UL GRANT information of MSg.

Specifically, the signaling or field carrying the second configuration list in the fifth signaling is denoted by ：numberOfMsg4-PUCCH-Repetitions ENUMERATED{n₁,n₂,n₃,n₄,n₅,n₆,n₇,n₈,n₉,n₁₀,n₁₁,n₁₂,n₁₃,n₁₄,n₁₅,n₁₆,…,n_m};, and the signaling or field carrying the number of repeated transmissions in the sixth signaling is denoted by: msg4-Pucch-RepetitionNrofSlots indicator-n bit (n is more than or equal to 0); the value {0 … 0,0 … 1, …,1 … 1} of this field may indicate a specific number of retransmissions, corresponding to a specific value of the second configuration list.

Specifically, the signaling or field in the fifth signaling that carries the first configuration set is expressed as: numberOfMsg4-PUCCH-RepetitionsList SEQUENCE (SIZE (2 ⁿ (n is 0 or more))) OF NumberOfMsg4-PUCCH-Repetitions; the signaling or field carrying and repeating the number of transmissions in the sixth signaling is expressed as: msg4-Pucch-RepetitionNrofSlots indicator-n bit (n is more than or equal to 0); the value {0 … 0,0 … 1, …,1 … 1} of this field may indicate a specific number of retransmissions, corresponding to a specific value of the first configuration set.

In another embodiment, when the number of repeated transmissions is carried in the plurality of sub-signaling, a second configuration list related to the number of repeated transmissions may be further obtained from the fifth signaling, a second configuration set in the second configuration list may be obtained from the fifth signaling, and the number of repeated transmissions may be obtained from the second configuration set according to the sixth signaling. Wherein, the signaling or field carrying the second configuration list in the fifth signaling is denoted by ：numberOfMsg4-PUCCH-Repetitions ENUMERATED{n₁,n₂,n₃,n₄,n₅,n₆,n₇,n₈,n₉,n₁₀,n₁₁,n₁₂,n₁₃,n₁₄,n₁₅,n₁₆,…,n_m};, and the signaling or field carrying the second configuration set in the fifth signaling is denoted by: numberOfMsg4-PUCCH-RepetitionsList SEQUENCE (SIZE (2 ⁿ (n is 0 or more))) OF NumberOfMsg4-PUCCH-Repetitions; the signaling or field carrying the number of repeated transmissions in the sixth signaling is expressed as: msg4-Pucch-RepetitionNrofSlots indicator-n bit (n is more than or equal to 0); the value {0 … 0,0 … 1, …,1 … 1} of this field may indicate a specific number of retransmissions, corresponding to a specific value of the second configuration set of the second configuration list.

In another embodiment, when the number of retransmissions is carried in the plurality of sub-signaling, a second configuration list related to the number of retransmissions may be further obtained from the fifth signaling, a second configuration set in the second configuration list may be obtained from the sixth signaling, and the number of retransmissions may be obtained from the second configuration set according to the sixth signaling of the common signaling. Wherein, the signaling or field carrying the second configuration list in the fifth signaling is denoted by ：numberOfMsg4-PUCCH-Repetitions ENUMERATED{n₁,n₂,n₃,n₄,n₅,n₆,n₇,n₈,n₉,n₁₀,n₁₁,n₁₂,n₁₃,n₁₄,n₁₅,n₁₆,…,n_m};, and the signaling or field carrying the second configuration set in the sixth signaling is denoted by: msg4-Pucch-RepetitionNrofSlots Set indicator-n ₁ bit(n₁ is equal to or greater than 0), it should be noted that when n ₁ is equal to 0, it means that the second configuration set is not needed, and it can be directly determined from the second configuration list; the field includes n ₁ MSB bits corresponding to a second configuration set of a second configuration list of a fifth signaling bearer; the signaling or field carrying the number of repetitions in the sixth signaling is expressed as: msg4-Pucch-RepetitionNrofSlots indicator-n ₂ bit(n₂ is 0 or more); this field includes n ₂ LSB bits, which together with the n ₁ MSB bits of Msg4-Pucch-RepetitionNrofSlots Set indicator indicate a specific value; the value {0 … 0,0 … 1, …,1 … 1} of this field may indicate a specific number of retransmissions, corresponding to a specific value of the second configuration set of the second configuration list.

Optionally, the number of repeated transmissions may also be obtained according to common signaling and user-specific signaling.

In a specific embodiment, the first configuration set in the first configuration list may be acquired from the common signaling, or the second configuration list in the number of repeated transmissions may be acquired from the common signaling, and the number of repeated transmissions may be acquired from the second configuration list or the first configuration set according to the user-specific signaling. Wherein the first configuration list is a configuration list predetermined according to a protocol with respect to the number of repeated transmissions.

In an embodiment, the first configuration set is carried in RRC signaling or SIB signaling in common signaling, and the number of repeated transmissions is carried in at least one of DCI scheduling Msg2, DCI scheduling Msg3, DCI scheduling Msg4, and RAR UL GRANT information of MSg2 in user-specific signaling.

Wherein the signaling or field carrying the first configuration set may be indicative of: numberOfMsg4-PUCCH-RepetitionsList SEQUENCE (SIZE (2 ⁿ (n is 0 or more))) OF NumberOfMsg4-PUCCH-Repetitions;

the field carrying the number of repeated transmissions may be a third field or a third mixed field, where the third field may be a new field or a part of bits of an existing field of the sub-signaling related to the user-specific signaling in the original protocol, and the third mixed field is a combination of a plurality of third fields belonging to the same sub-signaling, and the existing field includes, but is not limited to, a preset number of MSB bits and LSB bits.

Wherein the new field is expressed as: msg4-Pucch-RepetitionNrofSlots indicator-n bit (n is more than or equal to 0); the value {0 … 0,0 … 1, …,1 … 1} of this field may indicate a specific number of retransmissions.

The existing fields include, but are not limited to:

a TB scaling field, a LSBs of SFN field, and Reserved bits field of DCI belonging to the scheduling Msg 2;

HARQ process number field, new data indicator field, downlink assignment index field and TPC command for scheduled PUSCH field of DCI belonging to schedule Msg 3;

HARQ process number field, downlink assignment index field, TPC command for scheduled PUSCH field, PUCCH resource indicator, new data indicator field and Reserved bits field of DCI belonging to schedule Msg 4;

CSI request field, frequency hopping flag field, PUSCH frequency resource allocation field, PUSCH time resource allocation field, MCS field and TPC command for PUSCH field of RAR UL GRANT information belonging to Msg 2.

In another embodiment, the second configuration list is carried in RRC signaling or SIB signaling in common signaling, and the number of repeated transmissions is carried in at least one of DCI scheduling Msg2, DCI scheduling Msg3, DCI scheduling Msg4, and RAR UL GRANT information of MSg2 in user-specific signaling.

Wherein the signaling or field carrying the second configuration list may be expressed as ：numberOfMsg4-PUCCH-RepetitionsList SEQUENCE{n₁,n₂,n₃,n₄,n₅,n₆,n₇,n₈,n₉,n₁₀,n₁₁,n₁₂,n₁₃,n₁₄,n₁₅,n₁₆,…,n_m}.

The field carrying the number of repeated transmissions in the user specific signaling may be the third field or the third mixed field, which is not described herein.

In another embodiment, the first configuration set is carried with MIB or common DCI in common signaling, and the number of repeated transmissions is carried with at least one of DCI scheduling Msg2, DCI scheduling Msg3, DCI scheduling Msg4, and RAR UL GRANT information of MSg in user-specific signaling;

The field carrying the first configuration set may be a fourth field or a fourth mixed field, where the fourth field may be a new field, or may be a part of bits of an existing field of a sub-signaling related to user-specific signaling in an original protocol, and the fourth mixed field is a combination of a plurality of fourth fields belonging to the same sub-signaling.

Wherein, the newly added field can be expressed as: msg4-Pucch-RepetitionNrofSlots Set indicator-n ₁ bit(n₁ is equal to or greater than 0), it should be noted that when n ₁ is equal to 0, it means that the first configuration set is not needed, and it can be directly determined from the first configuration list; this field comprises n ₁ MSB bits corresponding to the first configuration set of the first configuration list.

The existing fields include, but are not limited to:

systemFrameNumber fields, subCarrierSpacingCommon fields, ssb-SubcarrierOffset fields, dmrs-TypeA-Position fields, pdcch-ConfigSIB1 fields, cellBarred fields, intraFreqReselection fields, and spark fields, which are all subordinate to MIB.

Frequency domain resource assignment fields, time domain resource assignment fields, VRB-to-PRB mapping fields, modulation and coding scheme fields, reserved bits fields, short Messages Indicator fields, short Messages fields, TB scaling fields, and TRS availability indication fields, which belong to the common DCI.

The field carrying the number of repeated transmissions in the user-specific signaling may be a fifth field or a fifth mixed field, where the fifth field may be a newly added field, or may be part of bits of an existing field of a sub-signaling related to the user-specific signaling in an original protocol, and the fifth mixed field is a combination of a plurality of fifth fields belonging to the same sub-signaling;

Wherein, the newly added field can be expressed as: msg4-Pucch-RepetitionNrofSlots indicator-n ₂bit(n₂ is 0 or more); this field includes n ₂ LSB bits, which together with the n ₁ MSB bits of Msg4-Pucch-RepetitionNrofSlots Set indicator indicate a specific value; the value {0 … 0,0 … 1, …,1 … 1} of this field may indicate a specific number of retransmissions, corresponding to a specific value of the configuration set.

The existing fields include, but are not limited to:

HARQ process number field, downlink assignment index field, TPC command for scheduled PUSCH field, PUCCH resource indicator field, new data indicator field and Reserved bits field of DCI belonging to schedule Msg 4;

In a specific embodiment, the second configuration list is further obtained from the common signaling, a second configuration set of the second configuration list is obtained from the common signaling or the user-specific signaling, and the retransmission times are obtained from the second configuration set according to the user-specific signaling.

In an embodiment, the second configuration list is carried by RRC signaling or SIB signaling in the common signaling, the second configuration set of the second configuration list is carried by RRC signaling or SIB signaling in the common signaling, and the number of repeated transmissions is carried by at least one of DCI scheduling Msg2, DCI scheduling Msg3, DCI scheduling Msg4, and RAR UL GRANT information of MSg in the user-specific signaling;

The signaling or field carrying the second set of configurations may be indicative of: numberOfMsg4-PUCCH-RepetitionsList SEQUENCE (SIZE (2 ⁿ (n is 0 or more))) OF NumberOfMsg4-PUCCH-Repetitions;

The signaling or fields of the first configuration set carried by RRC signaling or SIB signaling in the common signaling may be represented as: numberOfMsg4-PUCCH-RepetitionsList SEQUENCE (SIZE (2 ⁿ (n is 0 or more))) OF NumberOfMsg4-PUCCH-Repetitions;

the field carrying the number of retransmissions may be the third field or the third mixed field, which is not described herein.

In another embodiment, the second configuration list is carried by RRC signaling or SIB signaling in common signaling, the second configuration set of the second configuration list is carried by MIB signaling or common DCI in common signaling, and the number of repeated transmissions is carried by at least one of DCI scheduling Msg2, DCI scheduling Msg3, DCI scheduling Msg4, and RAR UL GRANT information of MSg in user-specific signaling;

The field carrying the second configuration set may be a sixth field or a sixth mixed field, where the sixth field may be a new field, or may be a part of bits of an existing field of the sub-signaling related to the user-specific signaling in the original protocol, and the sixth mixed field is a combination of a plurality of sixth fields belonging to the same sub-signaling.

Wherein, the newly added field can be expressed as: msg4-Pucch-RepetitionNrofSlots Set indicator-n ₁ bit(n₁ is equal to or greater than 0), it should be noted that when n ₁ is equal to 0, it means that the second configuration set is not needed, and it can be directly determined from the first configuration list; this field comprises n ₁ MSB bits corresponding to the second configuration set of the second configuration list.

The existing fields include, but are not limited to:

The field carrying the number of repeated transmissions in the user specific signaling may be a fifth field or a fifth mixed field, which is not described herein.

In another embodiment, the second configuration list is carried in RRC signaling or SIB signaling in common signaling, the second configuration set of the second configuration list is carried in RAR or Msg4 of MSg in user-specific signaling, and the number of retransmissions is carried in at least one of DCI scheduling Msg2, DCI scheduling Msg3, DCI scheduling Msg4, and RAR UL GRANT information of MSg in user-specific signaling;

The signaling or fields carrying the second set of configurations may be expressed as: numberOfMsg4-PUCCH-RepetitionsList SEQUENCE (SIZE (2 ⁿ (n is 0 or more))) OF NumberOfMsg4-PUCCH-Repetitions;

In another embodiment, the second configuration list is carried in RRC signaling or SIB signaling in common signaling, the second configuration set of the second configuration list is carried in at least one of DCI scheduling Msg2, DCI scheduling Msg3, DCI scheduling Msg4 and RAR UL GRANT information of MSg in user-specific signaling, and the number of repeated transmissions is carried in at least one of DCI scheduling Msg2, DCI scheduling Msg3, DCI scheduling Msg4 and RAR UL GRANT information of MSg in user-specific signaling;

The signaling or field carrying the second configuration set may be the sixth field or the sixth mixed field, which are not described herein;

the field carrying the number of retransmissions may be a fifth field or a fifth mixed field, which is not described herein.

Referring to fig. 2, another embodiment of the present application further provides a retransmission method for Msg4 hybrid automatic repeat request acknowledgement, which is applied to a user terminal and includes:

Step S201, a user request signaling is sent to a network side device, where the user request signaling carries at least one of first information and a number of repeated transmissions of whether the user terminal supports repeated transmission of a PUCCH, and the user request signaling includes: msg1 request and/or Msg3 request;

Step S202, when the ue supports the retransmission of PUCCH, after receiving the Msg4 sent by the network side device, repeatedly sending an Msg4 hybrid automatic repeat request acknowledgement to the network side device according to the number of repeated transmissions.

In another embodiment of the present application, a retransmission method for a Msg4 hybrid automatic repeat request acknowledgement applied to a user terminal is provided, where when the user terminal sends a user request signaling, the user terminal may carry, in the user request signaling, at least one of first information and a number of repeated transmissions of whether the user terminal supports repeated transmission of a PUCCH, where the first information is convenient for a network side device to timely learn whether the user terminal supports repeated transmission of the PUCCH, and perform repeated reception or single reception of the Msg4 hybrid automatic repeat request acknowledgement according to a specific situation, so as to ensure that the network side device can receive the Msg4 hybrid automatic repeat request acknowledgement fed back by the user terminal under the condition that the user terminal repeatedly sends the Msg4 hybrid automatic repeat request acknowledgement, ensure smooth completion of a random access procedure, and improve service quality of a communication network.

It should be noted that, when the ue supports the repeated transmission of PUCCH, the number of repeated transmissions may be carried in the ue request signaling; if the number of repeated transmissions of the Msg4 hybrid automatic repeat request acknowledgement in the network indication signaling received by the user terminal is greater than 1, the user terminal only performs transmission of the Msg4 hybrid automatic repeat request acknowledgement once after receiving the Msg4, or gives up transmission of the Msg4 hybrid automatic repeat request acknowledgement.

Referring to fig. 3, another embodiment of the present application further provides a network side device, including:

A first processing module 301, configured to obtain, from a user request signaling and/or a network indication signaling, a number of repeated transmissions of a PUCCH corresponding to a user terminal, where the user request signaling includes: msg1 request and/or Msg3 request, the network indication signaling comprising: public signaling and/or user-specific signaling;

And the second processing module 302 is configured to repeatedly receive, after the Msg4 is sent, an Msg4 hybrid automatic repeat request acknowledgement fed back by the user terminal according to the number of repeated transmissions.

Specifically, as described above, the network side device, the first processing module includes:

A first processing unit, configured to obtain, from the Msg1 request or the Msg3 request, first information whether the user terminal supports repeated transmission of a PUCCH;

And the second processing unit is used for acquiring the repeated transmission times from the Msg1 request or the Msg3 request when the first information indicates that the user terminal supports the repeated transmission of the PUCCH.

And the third processing unit is used for acquiring the first information whether the user terminal supports the repeated transmission of the PUCCH from the Msg1 request or the Msg3 request, and acquiring the repeated transmission times according to the network indication signaling.

A fourth processing unit, configured to obtain the number of repeated transmissions from a first configuration list according to a first field or a first mixed field of a first signaling of the common signaling, where the first mixed field includes at least two first fields, and the first signaling includes: at least one of radio resource control RRC signaling, system information block SIB signaling, master information block MIB signaling, and common downlink control information DCI;

Or a fifth processing unit, configured to obtain a second configuration list about the number of repeated transmissions from a second signaling of the common signaling, or obtain a first configuration set in the first configuration list from the second signaling, and obtain the number of repeated transmissions from the second configuration list or the first configuration set according to a third signaling of the common signaling, where the second signaling includes: the RRC signaling and/or the SIB signaling, and the third signaling includes: the MIB signaling and/or the common DCI;

Or a sixth processing unit, configured to obtain the second configuration list from the second signaling, obtain a second configuration set in the second configuration list from the first signaling, and obtain the retransmission times from the second configuration set according to the third signaling.

A seventh processing unit, configured to obtain the number of repeated transmissions from a first configuration list related to the number of repeated transmissions according to a second field or a second mixed field in a fourth signaling of the user-specific signaling, where the second mixed field includes at least two of the second fields, and the fourth signaling includes: at least one of DCI scheduling Msg2, DCI scheduling Msg3, DCI scheduling Msg4, msg2 and Msg 4;

Or an eighth processing unit, configured to obtain a second configuration list related to the number of repeated transmissions from a fifth signaling of the user specific signaling, or obtain a first configuration set in the first configuration list from the fifth signaling, and obtain the number of repeated transmissions from the second configuration list or the first configuration set according to a sixth signaling of the user specific signaling, where the fifth signaling includes: the raf information of MSg2 and/or the Msg4, the sixth signaling comprising: at least one of DCI of the scheduling Msg2, DCI of the scheduling Msg3, DCI of the scheduling Msg4, and RAR UL GRANT information of MSg;

Or a ninth processing unit, configured to obtain the second configuration list from the fifth signaling, obtain a second configuration set in the second configuration list from the fourth signaling, and obtain the retransmission times from the second configuration set according to the sixth signaling.

a tenth processing unit, configured to obtain, from the common signaling, a first configuration set in a first configuration list related to the number of repeated transmissions or a second configuration list related to the number of repeated transmissions, and obtain, from the first configuration set or the first configuration list, the number of repeated transmissions according to the user-specific signaling, where the common signaling includes: at least one of RRC signaling, SIB signaling, MIB signaling, and common DCI, the user-specific signaling including: at least one of DCI scheduling Msg2, DCI scheduling Msg3, DCI scheduling Msg4, msg2 and Msg 4;

Or an eleventh processing unit, configured to obtain the second configuration list from the common signaling, obtain a second configuration set of the second configuration list from the common signaling or the user-specific signaling, and obtain the number of repeated transmissions from the second configuration set according to the user-specific signaling.

The embodiment of the network side equipment of the application is equipment corresponding to the embodiment of the retransmission method for Msg4 hybrid automatic repeat request confirmation applied to the network side equipment, and all the implementation means in the embodiment of the method are applicable to the embodiment of the equipment, so that the same technical effect can be achieved.

Referring to fig. 4, another embodiment of the present application further provides a user terminal, including:

A third processing module 401, configured to send a user request signaling to a network side device, where the user request signaling carries first information about whether the user terminal supports repeated transmission of a PUCCH and/or a number of repeated transmissions, and the user request signaling includes: msg1 request and/or Msg3 request;

a fourth processing module 402, configured to repeatedly send an Msg4 hybrid automatic repeat request acknowledgement to the network side device according to the number of repeated transmissions after receiving the Msg4 sent by the network side device when the user terminal supports the repeated transmission of the PUCCH.

The embodiment of the user terminal of the application is the user terminal corresponding to the embodiment of the retransmission method for Msg4 hybrid automatic repeat request confirmation applied to the user terminal, and all the implementation means in the embodiment of the method are applicable to the embodiment of the user terminal, so that the same technical effect can be achieved.

Furthermore, the present application may repeat reference numerals and/or letters in the various examples. This repetition is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed.

It is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprise," "include," or any other variation thereof, are intended to cover a non-exclusive inclusion.

While the foregoing is directed to the preferred embodiments of the present application, it will be appreciated by those skilled in the art that various modifications and adaptations can be made without departing from the principles of the present application, and such modifications and adaptations are intended to be comprehended within the scope of the present application.

Claims

1. The retransmission method of the Msg4 hybrid automatic repeat request acknowledgement is applied to network side equipment and is characterized by comprising the following steps:

2. The retransmission method according to claim 1, wherein obtaining the number of retransmission times according to the user request signaling comprises:

3. The retransmission method according to claim 1, wherein obtaining the number of retransmission times according to the user request signaling and the network indication signaling comprises:

4. A retransmission method according to claim 1 or 3, characterized in that the acquisition of the number of retransmissions from the common signaling in the network indication signaling comprises:

5. A retransmission method according to claim 1 or 3, characterized in that the acquisition of the number of retransmissions from the user specific signalling in the network indication signalling comprises:

6. A retransmission method according to claim 1 or 3, characterized in that the acquisition of the number of retransmissions from the common signaling and the user-specific signaling in the network indication signaling comprises:

7. A retransmission method for Msg4 hybrid automatic repeat request acknowledgement, applied to a user terminal, comprising:

8. A network side device, comprising:

9. A user terminal, comprising:

10. An electronic device, comprising a processor, a memory, and a computer program stored on the memory and executable on the processor, the computer program implementing the steps of the retransmission method for Msg4 hybrid automatic repeat request acknowledgement applied to a network side device according to any of claims 1 to 6 or the steps of the retransmission method for Msg4 hybrid automatic repeat request acknowledgement applied to a user terminal according to claim 7 when executed by the processor.

11. A computer-readable storage medium, on which a computer program is stored, which when executed by a processor implements the steps of the retransmission method for Msg4 hybrid automatic repeat request acknowledgement applied to a network-side device according to any one of claims 1 to 6, or the steps of the retransmission method for Msg4 hybrid automatic repeat request acknowledgement applied to a user terminal according to claim 7.