Communication method, communication device, communication system, and storage medium

Abstract

Disclosed in the embodiments of the present disclosure are a communication method, a communication device, a communication system, and a storage medium. The method comprises: sending a message Msg3, wherein Msg3 carries first information, and the first information is used for indicating one or more of the following: requesting Msg4 physical downlink shared channel (PDSCH) repetition, and a terminal supporting the Msg4 PDSCH repetition. Therefore, conditions are provided to some extent for implementing Msg4 PDSCH repetition.

Description

Communication methods, communication equipment, communication systems and storage media Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication device, communication system and storage medium. Background Technology

[0002] Random access refers to the process from when a terminal device sends a random access preamble to attempt to access the network until a basic signaling connection is established with the network. Terminal devices typically use a four-step random access process, with the final step being the network device sending a random access message 4 (Msg4) to the successfully accessed terminal device. Summary of the Invention

[0003] Random access message (Message, Msg)4 is a downlink message in the random access process. How to achieve repeated transmission of Msg4 in downlink coverage enhancement.

[0004] This disclosure provides a communication method, communication device, communication system, and storage medium.

[0005] A first aspect of this disclosure provides a communication method, which is executed by a terminal, and the method includes:

[0006] Send message Msg3, in which Msg3 carries first information, the first information being used to indicate one or more of the following: requesting Msg4 Physical Downlink Shared Channel (PDSCH) retransmission; the terminal supports Msg4 PDSCH retransmission.

[0007] A second aspect of this disclosure provides a communication method, which is executed by a network device, and the method includes:

[0008] Receive message Msg3, wherein Msg3 carries first information, the first information being used to indicate one or more of the following: requesting Msg4 Physical Downlink Shared Channel (PDSCH) retransmission; the terminal supports Msg4 PDSCH retransmission.

[0009] A third aspect of this disclosure provides a terminal, the terminal comprising:

[0010] A transceiver module is used to send message Msg3, wherein Msg3 carries first information, the first information being used to indicate one or more of the following: requesting repeated transmission of the Physical Downlink Shared Channel (PDSCH) for Msg4; and the terminal supporting repeated transmission of Msg4 PDSCH. A fourth aspect of this disclosure provides a network device, the network device comprising:

[0011] The transceiver module is used to receive message Msg3, wherein Msg3 carries first information, which indicates one or more of the following: requesting repeated transmission of the Physical Downlink Shared Channel (PDSCH) for Msg4; and the terminal supports repeated transmission of Msg4 PDSCH.

[0012] A fifth aspect of this disclosure provides a communication device, which includes one or more processors;

[0013] The processor is configured to perform the method as described in the first aspect above, or to perform the method as described in the second aspect above.

[0014] A sixth aspect of this disclosure provides a communication system including a terminal and a network device, wherein the terminal is configured to perform the method described in the first aspect above, and the network device is configured to perform the method described in the second aspect above.

[0015] A seventh aspect of this disclosure provides a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect above, or to perform the method described in the second aspect above.

[0016] An eighth aspect of this disclosure provides a computer program product including a computer program that, when executed by a processor, implements the method described in the first aspect above, or implements the method described in the second aspect above.

[0017] In the above embodiments, the terminal requests Msg4 PDSCH retransmission via Msg3 or instructs itself to support Msg4 PDSCH retransmission, thereby providing conditions for realizing Msg4 PDSCH retransmission and downlink coverage enhancement, and improving the performance and reliability of the communication system. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments or background art of this disclosure, the accompanying drawings used in the embodiments or background art of this disclosure will be described below.

[0019] Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this disclosure;

[0020] Figures 2A-2B are interactive schematic diagrams of the communication method provided in the embodiments of this disclosure;

[0021] Figure 3 is a schematic diagram of the structure of a terminal provided in an embodiment of this disclosure;

[0022] Figure 4A is a schematic diagram of the structure of a communication device provided in an embodiment of this disclosure;

[0023] Figure 4B is a schematic diagram of the structure of a chip provided in an embodiment of this disclosure. Detailed Implementation

[0024] This disclosure provides communication methods, communication devices, communication systems, and storage media.

[0025] In a first aspect, embodiments of this disclosure propose a communication method, the method comprising: sending a message Msg3, wherein the Msg3 carries first information, the first information being used to indicate one or more of the following: requesting Msg4 Physical Downlink Shared Channel (PDSCH) retransmission; and the terminal supporting Msg4 PDSCH retransmission.

[0026] In the above embodiments, the terminal requests Msg4 PDSCH retransmission via Msg3 or instructs itself to support Msg4 PDSCH retransmission, thereby providing conditions for realizing Msg4 PDSCH retransmission and downlink coverage enhancement, and improving the performance and reliability of the communication system.

[0027] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes:

[0028] If the downlink reference signal received power RSRP is less than a first threshold, it is determined that the first information is carried in Msg3.

[0029] In the above embodiments, the terminal can carry the first information in Msg3 when the downlink reference signal received power RSRP is less than the first threshold value, thereby avoiding the meaningless first information occupying transmission resources when the network state does not support the repeated transmission of Msg4 PDSCH.

[0030] In conjunction with some embodiments of the first aspect, in some embodiments, the aforementioned first information is also used to indicate one or more of the following:

[0031] The limited-capability RedCap terminal repeatedly transmits Msg4 PDSCH using the 48-bit common control channel CCCH.

[0032] RedCap terminals repeatedly transmit Msg4 PDSCH, using 64-bit CCCH.

[0033] Enhanced Msg4 PDSCH retransmission of RedCap terminals, using 48-bit CCCH;

[0034] Enhance the Msg4PDSCH retransmission of RedCap terminals, using 64-bit CCCH;

[0035] For repeated transmissions of Msg4 PDSCH except for RedCap or Enhanced RedCap terminals, use 48-bit CCCH;

[0036] Except for RedCap or Enhanced RedCap terminals, repeated transmissions of Msg4 PDSCH use 64-bit CCCH;

[0037] Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission and Msg4 PDSCH retransmission use 48-bit CCCH respectively.

[0038] Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively;

[0039] RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0040] RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0041] Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively;

[0042] Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

[0043] In the above embodiments, the terminal can reuse one or more of the various indication information to indicate that it supports (or requests) repeated transmission of Msg4PDSCH, thereby reducing the resources occupied by the transmission of indication information.

[0044] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes:

[0045] The terminal supports Msg4 PDSCH retransmission and confirms support for Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission.

[0046] In the above embodiments, the terminal simultaneously supports Msg4 PDSCH retransmission and Msg4 HARQ-ACK PUCCH retransmission, thereby further providing conditions for improving the success rate of downlink coverage enhancement.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes:

[0048] Configuration parameters for receiving repeated transmissions of Msg4 PDSCH, wherein the configuration parameters satisfy one or more of the following:

[0049] At the same time, Msg4 PDSCH retransmission and Msg4 HARQ-ACK physical uplink control channel PUCCH retransmission function are enabled.

[0050] The Msg4 PDSCH repeat transmission function is enabled, but the first threshold value and the second threshold value are not configured. The first threshold value is used to trigger Msg4 PDSCH repeat transmission, and the second threshold value is used to trigger Msg4 HARQ-ACK PUCCH repeat transmission.

[0051] The first threshold value that triggers repeated transmission of Msg4 PDSCH is less than the second threshold value that triggers repeated transmission of Msg4 HARQ-ACK PUCCH.

[0052] In the above embodiments, the network device can configure the configuration parameters for repeated transmission of Msg4 PDSCH to the terminal, further providing conditions for realizing repeated transmission of Msg4 PDSCH.

[0053] In conjunction with some embodiments of the first aspect, in some embodiments, the above Msg3 further includes second information, the second information being used to indicate one or more of the following: supporting repeated transmission of Msg4 HARQ-ACK physical uplink control channel PUCCH; requesting repeated transmission of Msg4 HARQ-ACK PUCCH.

[0054] In conjunction with some embodiments of the first aspect, in some embodiments, the second information described above may be the same as or different from the first information.

[0055] In conjunction with some embodiments of the first aspect, in some embodiments, the second indication information described above is also used to indicate one or more of the following:

[0056] Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission and Msg4 PDSCH retransmission use 48-bit CCCH respectively.

[0057] Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively;

[0058] RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0059] RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0060] Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively;

[0061] Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

[0062] In the above embodiments, the terminal can use second information, which is the same as or different from the first information, in Msg3 to indicate that it supports (or requests) Msg4 HARQ-ACK PUCCH repeated transmission, thereby further ensuring the reliability of Msg4 PDSCH repeated transmission and downlink coverage enhancement.

[0063] Secondly, embodiments of this disclosure provide a communication method, which is executed by a network device, the method comprising:

[0064] Receive message Msg3, wherein Msg3 carries first information, the first information being used to indicate one or more of the following: requesting Msg4 Physical Downlink Shared Channel (PDSCH) retransmission; the terminal supports Msg4 PDSCH retransmission.

[0065] In conjunction with some embodiments of the second aspect, in some embodiments the above method further includes:

[0066] Msg3 contains the first information, which determines that the downlink reference signal received power RSRP is less than a first threshold value.

[0067] In conjunction with some embodiments of the second aspect, in some embodiments, the aforementioned first information is also used to indicate one or more of the following:

[0068] The limited-capability RedCap terminal repeatedly transmits Msg4 PDSCH using the 48-bit common control channel CCCH.

[0069] RedCap terminals repeatedly transmit Msg4 PDSCH, using 64-bit CCCH.

[0070] Enhanced Msg4 PDSCH retransmission of RedCap terminals, using 48-bit CCCH;

[0071] Enhance the Msg4PDSCH retransmission of RedCap terminals, using 64-bit CCCH;

[0072] For repeated transmissions of Msg4 PDSCH except for RedCap or Enhanced RedCap terminals, use 48-bit CCCH;

[0073] Except for RedCap or Enhanced RedCap terminals, repeated transmissions of Msg4 PDSCH use 64-bit CCCH;

[0074] Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission and Msg4 PDSCH retransmission use 48-bit CCCH respectively.

[0075] Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively;

[0076] RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0077] RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0078] Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively;

[0079] Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

[0080] In conjunction with some embodiments of the second aspect, in some embodiments the above method further includes:

[0081] The first information indicates that the terminal supports repeated transmission of Msg4 PDSCH, and confirms that the terminal supports repeated transmission of Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH).

[0082] In conjunction with some embodiments of the second aspect, in some embodiments the above method further includes:

[0083] Configuration parameters for sending repeated Msg4 PDSCH transmissions, wherein the configuration parameters satisfy one or more of the following:

[0084] The Msg4 PDSCH retransmission function and the Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission function are enabled.

[0085] The Msg4 PDSCH repeat transmission function is enabled, but the first threshold value and the second threshold value are not configured. The first threshold value is used to trigger Msg4 PDSCH repeat transmission, and the second threshold value is used to trigger Msg4 HARQ-ACK PUCCH repeat transmission.

[0086] The first threshold value that triggers repeated transmission of Msg4 PDSCH is less than the second threshold value that triggers repeated transmission of Msg4 HARQ-ACK PUCCH.

[0087] In conjunction with some embodiments of the second aspect, in some embodiments, the above Msg3 further includes second information, the second information being used to indicate one or more of the following: supporting repeated transmission of Msg4 HARQ-ACK physical uplink control channel PUCCH; requesting repeated transmission of Msg4 HARQ-ACK PUCCH.

[0088] In conjunction with some embodiments of the second aspect, in some embodiments, the second information described above may be the same as or different from the first information.

[0089] In conjunction with some embodiments of the second aspect, in some embodiments, the aforementioned second indication information is also used to indicate one or more of the following:

[0090] Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission and Msg4 PDSCH retransmission use 48-bit CCCH respectively.

[0091] Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively;

[0092] RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0093] RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0094] Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively;

[0095] Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

[0096] Thirdly, embodiments of this disclosure provide a terminal, the terminal comprising:

[0097] The transceiver module is used to send message Msg3, wherein Msg3 carries first information, which indicates one or more of the following: requesting repeated transmission of the Physical Downlink Shared Channel (PDSCH) for Msg4; and the terminal supports repeated transmission of Msg4 PDSCH.

[0098] In conjunction with some embodiments of the third aspect, in some embodiments, the above-described processing module is used for:

[0099] If the downlink reference signal received power RSRP is less than the first threshold, it is determined that Msg3 carries the first information.

[0100] In conjunction with some embodiments of the third aspect, in some embodiments, the aforementioned first information is also used to indicate one or more of the following:

[0101] The limited-capability RedCap terminal repeatedly transmits Msg4 PDSCH using the 48-bit common control channel CCCH.

[0102] RedCap terminals repeatedly transmit Msg4 PDSCH, using 64-bit CCCH.

[0103] Enhanced Msg4 PDSCH retransmission of RedCap terminals, using 48-bit CCCH;

[0104] Enhance the Msg4PDSCH retransmission of RedCap terminals, using 64-bit CCCH;

[0105] For repeated transmissions of Msg4 PDSCH except for RedCap or Enhanced RedCap terminals, use 48-bit CCCH;

[0106] Except for RedCap or Enhanced RedCap terminals, repeated transmissions of Msg4 PDSCH use 64-bit CCCH;

[0107] Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission and Msg4 PDSCH retransmission use 48-bit CCCH respectively.

[0108] Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively;

[0109] RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0110] RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0111] Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively;

[0112] Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

[0113] In conjunction with some embodiments of the third aspect, in some embodiments, the above-described processing module is further configured to:

[0114] The terminal supports Msg4 PDSCH retransmission and confirms support for Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission.

[0115] In conjunction with some embodiments of the third aspect, in some embodiments, the above-described transceiver module can also be used for:

[0116] Configuration parameters for receiving repeated transmissions of Msg4 PDSCH, wherein the configuration parameters satisfy one or more of the following:

[0117] At the same time, Msg4 PDSCH retransmission and Msg4 HARQ-ACK physical uplink control channel PUCCH retransmission function are enabled.

[0118] The Msg4 PDSCH repeat transmission function is enabled, but the first threshold value and the second threshold value are not configured. The first threshold value is used to trigger Msg4 PDSCH repeat transmission, and the second threshold value is used to trigger Msg4 HARQ-ACK PUCCH repeat transmission.

[0119] The first threshold value that triggers repeated transmission of Msg4 PDSCH is less than the second threshold value that triggers repeated transmission of Msg4 HARQ-ACK PUCCH.

[0120] In conjunction with some embodiments of the third aspect, in some embodiments, the above Msg3 further includes second information, which is used to indicate one or more of the following: supporting repeated transmission of Msg4 HARQ-ACK physical uplink control channel PUCCH; requesting repeated transmission of Msg4 HARQ-ACK PUCCH.

[0121] In conjunction with some embodiments of the third aspect, in some embodiments, the second information described above may be the same as or different from the first information.

[0122] In conjunction with some embodiments of the third aspect, in some embodiments, the aforementioned second indication information is also used to indicate one or more of the following:

[0123] Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission and Msg4 PDSCH retransmission use 48-bit CCCH respectively.

[0124] Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively;

[0125] RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0126] RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0127] Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively;

[0128] Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

[0129] Fourthly, embodiments of this disclosure provide a network device, the network device comprising:

[0130] The transceiver module is used to receive message Msg3, wherein Msg3 carries first information, which indicates one or more of the following: requesting repeated transmission of the Physical Downlink Shared Channel (PDSCH) for Msg4; and the terminal supports repeated transmission of Msg4 PDSCH.

[0131] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-described processing module is used for:

[0132] Msg3 contains the first information, which determines that the downlink reference signal received power RSRP is less than a first threshold value.

[0133] In conjunction with some embodiments of the fourth aspect, in some embodiments, the aforementioned first information is also used to indicate one or more of the following:

[0134] The limited-capability RedCap terminal repeatedly transmits Msg4 PDSCH using the 48-bit common control channel CCCH.

[0135] RedCap terminals repeatedly transmit Msg4 PDSCH, using 64-bit CCCH.

[0136] Enhanced Msg4 PDSCH retransmission of RedCap terminals, using 48-bit CCCH;

[0137] Enhance the Msg4PDSCH retransmission of RedCap terminals, using 64-bit CCCH;

[0138] For repeated transmissions of Msg4 PDSCH except for RedCap or Enhanced RedCap terminals, use 48-bit CCCH;

[0139] Except for RedCap or Enhanced RedCap terminals, repeated transmissions of Msg4 PDSCH use 64-bit CCCH;

[0140] Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission and Msg4 PDSCH retransmission use 48-bit CCCH respectively.

[0141] Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively;

[0142] RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0143] RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0144] Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively;

[0145] Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

[0146] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-described processing module is further configured to:

[0147] The first information indicates that the terminal supports repeated transmission of Msg4 PDSCH, and confirms that the terminal supports repeated transmission of Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH).

[0148] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-described transceiver module can also be used for:

[0149] Configuration parameters for sending repeated Msg4 PDSCH transmissions, wherein the configuration parameters satisfy one or more of the following:

[0150] At the same time, Msg4 PDSCH retransmission and Msg4 HARQ-ACK physical uplink control channel PUCCH retransmission function are enabled.

[0151] The Msg4 PDSCH repeat transmission function is enabled, but the first threshold value and the second threshold value are not configured. The first threshold value is used to trigger Msg4 PDSCH repeat transmission, and the second threshold value is used to trigger Msg4 HARQ-ACK PUCCH repeat transmission.

[0152] The first threshold value that triggers repeated transmission of Msg4 PDSCH is less than the second threshold value that triggers repeated transmission of Msg4 HARQ-ACK PUCCH.

[0153] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above Msg3 further includes second information, which is used to indicate one or more of the following: supporting repeated transmission of Msg4 HARQ-ACK physical uplink control channel PUCCH; requesting repeated transmission of Msg4 HARQ-ACK PUCCH.

[0154] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second information described above may be the same as or different from the first information.

[0155] In conjunction with some embodiments of the fourth aspect, in some embodiments, the aforementioned second indication information is also used to indicate one or more of the following:

[0156] Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission and Msg4 PDSCH retransmission use 48-bit CCCH respectively.

[0157] Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively;

[0158] RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0159] RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0160] Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively;

[0161] Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

[0162] Fifthly, embodiments of this disclosure provide a communication device, which includes one or more processors; wherein the communication device is used to execute the first aspect and optional implementations of the first aspect, or to execute the second aspect and optional implementations of the second aspect.

[0163] In a sixth aspect, embodiments of this disclosure provide a communication system comprising: a terminal and a network device; wherein the terminal is configured to perform the method described in the first aspect and optional implementations thereof, and the network device is configured to perform the method described in the second aspect and optional implementations thereof.

[0164] In a seventh aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect and its optional implementations, or to perform the method described in the second aspect and its optional implementations.

[0165] Eighthly, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method described in the first aspect and its optional implementations, or to perform the method described in the second aspect and its optional implementations.

[0166] In a ninth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the method as described in the first aspect and optional implementations of the first aspect, or to perform the method as described in the second aspect and optional implementations of the second aspect.

[0167] In a tenth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the method described according to the first aspect and optional implementations thereof, or configured to perform the method described according to the second aspect and optional implementations thereof.

[0168] It is understood that the aforementioned terminals, network devices, communication devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0169] This disclosure provides a communication method, a communication device, a communication system, and a storage medium. In some embodiments, the terms "communication method" and "information processing method" can be used interchangeably; the terms "communication method apparatus" and "information processing apparatus" can be used interchangeably; and the terms "message transmission system" and "information processing system" can be used interchangeably.

[0170] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular 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 particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0171] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0172] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0173] In this disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the aforementioned," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular or a plural expression.

[0174] In the embodiments disclosed herein, "multiple" refers to two or more.

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

[0176] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.

[0177] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0178] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0179] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0180] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0181] In some embodiments, the terms “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 lower than,” and “above” can be used interchangeably, as can the terms “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”.

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

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

[0184] 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," or "fixed station." In some embodiments, it may also be understood as "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / 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," or "bandwidth part (BWP)."

[0185] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)," "user terminal," "Narrow Band-Internet of Things (NB-IoT) device," "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.

[0186] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0187] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0188] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

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

[0190] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0191] As shown in Figure 1, the communication system 100 includes a terminal 101 and a network device 102.

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

[0193] In some embodiments, network device 102 may include at least one of access network device and core network device.

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

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

[0196] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0197] In some embodiments, a core network device may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of the aforementioned one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Protocol Core (EPC), a 5G Core Network (5GCN), or a Next Generation Core (NGC).

[0198] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0199] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0200] The embodiments disclosed herein 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), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a 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, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0201] Research in the field of communications focuses on how to enhance downlink coverage, including improving the performance of the random access message (Msg) 4 on the Physical Downlink Shared Channel (PDSCH). One approach is to perform multiple repetitions of the Msg 4 PDSCH transmission.

[0202] This disclosure addresses the need for the network to know whether the terminal supports or requests Msg4 PDSCH repetition before scheduling Msg4 PDSCH repetition. Therefore, the terminal can indicate to the network whether it supports or requests Msg4 PDSCH repetition before receiving Msg4.

[0203] Alternatively, one indication method is for the terminal to explicitly indicate support for Msg4 PDSCH repetition (or PDSCH repetition for msg4) or request Msg4 PDSCH repetition in Msg3.

[0204] Optionally, the indication in Msg3 that indicates repeated transmission of the Hybrid Automatic Repeat reQuest-Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) can be reused.

[0205] This disclosure proposes an instruction method in which a terminal requests Msg4 to be retransmitted on the PDSCH via Msg3, or instructs the terminal to support Msg4 being retransmitted on the PDSCH, thereby providing conditions and basis for network devices to perform Msg4 PDSCH repetition and achieve downlink coverage enhancement.

[0206] The communication methods, communication devices, communication systems, and storage media provided in this disclosure will be described in detail below with reference to the accompanying drawings.

[0207] Figure 2A is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 2A, the communication method involved in this embodiment is executed by a communication system, which may include a terminal and network devices. The method described below, as shown in Figure 2A, includes:

[0208] Step S2101: Send the configuration parameters for repeated transmission of Msg4 PDSCH.

[0209] In some embodiments, Msg4 is a random access completion confirmation message sent by the network device to the terminal during the four-step random access process, used to indicate to the terminal that it has successfully accessed the network.

[0210] In some embodiments, during the Contention Based Random Access (CBRA) process, Msg4 may also include a contention resolution identifier (ID). All terminals receiving the Msg4 message can compare the contention resolution ID in Msg4 with the contention resolution ID in their own Msg3 message. If they match, the contention resolution is considered successful, and the random access procedure is completed; otherwise, the contention has failed, and the terminal needs to re-initiate the random access procedure.

[0211] In some embodiments, Msg3 is a random access completion message sent by the terminal to the network device during the four-step random access process. It may contain the terminal's identity information, so that the network device can identify and verify the terminal requesting access based on the terminal's identity information.

[0212] In some embodiments, Msg3 may also include a temporary identifier for encrypted communication and an identifier for identifying the system type. This information provides the necessary preparation for establishing encrypted communication between the network and the terminal.

[0213] In some embodiments, Msg3 may also carry other critical information, such as the reason for initiating Contention-Based Random Access (CBRA) and possible system message requests. This information helps network devices understand the access needs and status of mobile terminals.

[0214] In some embodiments, the network device sends the configuration parameters for Msg4 PDSCH repetition to the terminal.

[0215] In some embodiments, the network device may send configuration parameters for repeated transmission of Msg4 PDSCH via system messages or broadcast messages.

[0216] In some embodiments, terms such as "Msg4 PDSCH repeated transmission", "Msg4 sent multiple times on PDSCH", "Msg4 repeatedly transmitted on PDSCH", and "Msg4 sent multiple times on PDSCH" can all be used to describe Msg4 being repeatedly transmitted (or sent) on PDSCH. In some scenarios, the above terms can be used interchangeably.

[0217] In some embodiments, the configuration parameters for repeated transmission of Msg4 PDSCH may include one or more of the following: an enable parameter, the number of Msg4PDSCH repetitions, the time-frequency domain resources corresponding to the Msg4 PDSCH repetition, and a first threshold value for triggering the Msg4 PDSCH repetition.

[0218] In some embodiments, an enable parameter is used to enable (or activate) and / or deactivate (or deactivate) Msg4 PDSCH repetitive transmissions.

[0219] In some embodiments, the configuration parameters include parameters for enabling Msg4 PDSCH retransmission, which determines that the network device simultaneously enables Msg4 Hybrid Automatic Repeat reQuest-Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission.

[0220] In some embodiments, terms such as "Msg4 HARQ-ACK PUCCH repeated transmission", "Msg4 HARQ-ACK repeated transmission on PUCCH", "Msg4 HARQ-ACK repeated transmission on PUCCH", "Msg4 HARQ-ACK repeated transmission on PUCCH", and "Msg4 HARQ-ACK repeated transmission on PUCCH" can all be used to describe that Msg4 HARQ-ACK is repeatedly transmitted (or transmitted) on PUCCH. In some scenarios, the above terms can be used interchangeably.

[0221] In some embodiments, the configuration parameters can simultaneously enable Msg4 PDSCH repeat transmission and Msg4 HARQ-ACK PUCCH repeat transmission.

[0222] In some embodiments, the configuration parameters can enable both Msg4 PDSCH repeat transmission and Msg4HARQ-ACK PUCCH repeat transmission functions simultaneously through one enable parameter; or enable both Msg4 PDSCH repeat transmission and Msg4 HARQ-ACK PUCCH repeat transmission functions separately through two different enable parameters.

[0223] In some embodiments, the configuration parameters may also include the number of times Msg4 HARQ-ACK PUCCH is repeatedly transmitted, the time-frequency domain resources corresponding to the repeated transmission of Msg4 HARQ-ACK PUCCH, and so on.

[0224] In some embodiments, the first threshold value for triggering Msg4 PDSCH repetition can be the Reference Signal Received Power (RSRP).

[0225] In some embodiments, the configuration parameters may also include a second threshold value for triggering repeated transmission of Msg4 HARQ-ACK PUCCH.

[0226] In some embodiments, the first threshold value for triggering repeated transmission of Msg4 PDSCH is less than the second threshold value for triggering repeated transmission of Msg4 HARQ-ACK PUCCH.

[0227] In some embodiments, since the channel PUCCH used to transmit Msg4 HARQ-ACK is always worse than the channel PDSCH used to transmit Msg4, the first threshold value can be set to be less than the second threshold value.

[0228] In some embodiments, the configuration parameters may enable only the Msg4 PDSCH repeat transmission function, but without configuring the first RSRP threshold value and the second RSRP threshold value. The first RSRP threshold value is used to trigger the Msg4 PDSCH repeat transmission, and the second RSRP threshold value is used to trigger the Msg4 HARQ-ACK PUCCH repeat transmission.

[0229] In other words, the configuration parameters can enable only Msg4 PDSCH repeat transmission and Msg4 HARQ-ACK PUCCH repeat transmission, but without configuring the first threshold value for triggering Msg4 PDSCH repeat transmission and the second threshold value for triggering Msg4 HARQ-ACK PUCCH repeat transmission.

[0230] In some embodiments, the terminal receives configuration parameters for repeated transmission of Msg4 PDSCH.

[0231] Step S2102: If the downlink reference signal received power RSRP is less than the first threshold, it is determined that Msg3 carries the first information.

[0232] In some embodiments, the terminal can determine that Msg3 carries the first information if the downlink RSRP is less than a first threshold value.

[0233] In some embodiments, the terminal can determine that Msg3 carries the first information if the RSRP of the downlink path loss reference point is less than a first threshold value.

[0234] In some embodiments, the first information is used to indicate one or more of the following: requesting repeated transmission of the Msg4 Physical Downlink Shared Channel (PDSCH); the terminal supports repeated transmission of the Msg4 PDSCH.

[0235] In some embodiments, the UE can only indicate PDSCH repetition for msg4 in Msg3 if the network device has enabled the PDSCH repetition for msg4 function.

[0236] In some embodiments, the network device does not enable the PDSCH repetition for msg4 function, and the terminal can also request PDSCH repetition for msg4 in Msg3.

[0237] Step S2103: Send Msg3.

[0238] Msg3 contains the first piece of information.

[0239] In some embodiments, if the terminal enables the Msg PDSCH repeat transmission function in the received Msg PDSCH repeat transmission configuration parameters and the terminal supports the Msg PDSCH repeat transmission function, it can directly send Msg3 containing the first information.

[0240] In some embodiments, the terminal may also send Msg3 containing the first information if the RSRP of the downlink path loss reference point is less than a first threshold value.

[0241] In some embodiments, the first threshold value may be indicated by the network device through repeated transmission of configuration parameters via Msg PDSCH.

[0242] In some embodiments, the first threshold value may also be determined by the terminal based on the protocol agreement, and this disclosure does not limit it.

[0243] In some embodiments, the first information may also be used to indicate repeated transmission of Msg4PDSCH for Reduced Capability (RedCap) terminals, and a 48-bit Common Control Channel (CCCH) may be used.

[0244] In some embodiments, a capability-limited terminal is used to describe a terminal that is processed by reducing terminal bandwidth, the number of transceiver antennas, and the modulation order in order to reduce cost and power consumption.

[0245] In some embodiments, the Enhanced Reduced Capabilities (eRedCap) terminal is an enhanced version of the RedCap UE, which further improves performance and functionality on top of RedCap. While meeting the requirements of low power consumption and low cost, the eRedCap UE can also adapt to some specific application scenarios.

[0246] In some embodiments, terms such as "RedCap terminal uses 48-bit CCCH for repeated transmission of Msg4 PDSCH" and "uses 48-bit CCCH to repeatedly transmit Msg4 PDSCH" can be used to describe the repeated transmission of Msg4 PDSCH in RedCap terminal. A 48-bit CCCH can be used. In some scenarios, the above terms can be used interchangeably.

[0247] In other words, information indicating the CCCH size used for Msg4 PDSCH repetition by a RedCap terminal can be reused to instruct the terminal to support or request Msg4 PDSCH repetition. If Msg3 contains the information field "CCCH of size 48 bits for Msg4 PDSCH repetition of a RedCap UE", then the network device can determine that the terminal has indicated its support for or request for Msg4 PDSCH repetition. This reduces the transmission overhead of the terminal indicating its support for or request for Msg4 PDSCH repetition.

[0248] In some embodiments, the first information can also be used to indicate that, except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) and Msg4 PDSCH are repeatedly transmitted, each using 48 bits of CCCH.

[0249] In other words, the system can reuse both the Msg4 HARQ-ACK PUCCH repetition and Msg4 PDSCH repetition indication information, using 48 bits of CCCH indication information, to indicate whether the terminal supports or requests Msg4 PDSCH repetition. If Msg3 contains the information field "CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK & Msg4 PDSCH repetition, except for an(e)RedCap UE", then the network device can determine that the terminal has indicated its support for or request for Msg4 PDSCH repetition. This reduces the transmission overhead of the terminal indicating its support for or request for Msg4 PDSCH repetition.

[0250] In some embodiments, the first information may also be used to indicate one or more of the following: repeated transmission of Msg4 PDSCH for RedCap terminals using 64-bit CCCH; repeated transmission of Msg4 PDSCH for enhanced RedCap terminals using 48-bit CCCH; repeated transmission of Msg4 PDSCH for enhanced RedCap terminals using 64-bit CCCH; repeated transmission of Msg4 PDSCH for terminals other than RedCap or enhanced Reduced Capabilities (eRedCap) terminals using 48-bit CCCH; repeated transmission of Msg4 PDSCH for terminals other than RedCap or enhanced RedCap terminals using 64-bit CCCH; repeated transmission of Msg4 HARQ-ACK PUCCH and repeated transmission of Msg4 PDSCH for terminals other than RedCap or enhanced RedCap terminals using 64-bit CCCH respectively; repeated transmission of Msg4 HARQ-ACK PUCCH and repeated transmission of Msg4 PDSCH for RedCap terminals using 48-bit CCCH respectively; repeated transmission of Msg4 HARQ-ACK for RedCap terminals. PUCCH and Msg4 PDSCH repeat transmissions each use 64-bit CCCH; Msg4HARQ-ACK PUCCH and Msg4 PDSCH repeat transmissions of the enhanced RedCap terminal each use 48-bit CCCH; Msg4HARQ-ACK PUCCH and Msg4 PDSCH repeat transmissions of the enhanced RedCap terminal each use 64-bit CCCH.

[0251] In some embodiments, the indication information corresponding to any of the above items can be the first information. That is, if Msg3 contains the indication information corresponding to any of the above items, it can be determined that Msg3 contains the first information.

[0252] In some embodiments, Msg3 may contain different Logical Channel Identifiers (LCIDs) to identify which type of terminal (e.g., RedCap terminal or other terminals) Msg4 PDSCH is being repeatedly transmitted, and the size of the CCCH used.

[0253] In some embodiments, Msg3 contains multiple corresponding indication messages from the above items, thus confirming that it includes the first information. For example, the indication messages "RedCap terminal's Msg4 PDSCH is repeatedly transmitted using 48-bit CCCH" and "Except for RedCap or enhanced RedCap terminals, Msg4 PDSCH is repeatedly transmitted using 64-bit CCCH" can be reused to implicitly indicate that the terminal requests (or supports) Msg4 PDSCH repeated transmission.

[0254] In this embodiment of the disclosure, by reusing one or more of the various indication information, the terminal is instructed to support (or request) repeated transmission of Msg4PDSCH, thereby improving the flexibility of the first information indication and reducing the transmission overhead of the indication.

[0255] In some embodiments, the terminal supports repeated transmission of Msg4 PDSCH and confirms that repeated transmission of Msg4 HARQ-ACK PUCCH is supported.

[0256] In the disclosed embodiments, if the terminal supports repeated transmission of Msg4 PDSCH, in order to ensure that the network device can determine in a timely and accurate manner whether the terminal has reliably received Msg4, the terminal needs to send Msg4 HARQ-ACK to the network device for each Msg4 PDSCH transmission. That is, if Msg3 indicates that the terminal supports repeated transmission of Msg4 PDSCH, then it can be determined that the terminal also supports repeated transmission of Msg4 HARQ-ACK PUCCH.

[0257] In some embodiments, Msg3 also includes second information, which indicates one or more of the following: supporting repeated transmission of Msg4 HARQ-ACK physical uplink control channel PUCCH; requesting repeated transmission of Msg4 HARQ-ACK PUCCH.

[0258] In other words, the terminal can also indicate via Msg3 whether it supports repeated transmission of Msg4 HARQ-ACK PUCCH, or whether it requests repeated transmission of Msg4HARQ-ACK PUCCH.

[0259] In some embodiments, the terminal can implicitly indicate whether it supports repeated transmission of Msg4 HARQ-ACK PUCCH through the first information. That is, if Msg3 indicates support for repeated transmission of Msg4 PDSCH, it also implicitly indicates that it supports repeated transmission of Msg4 HARQ-ACK PUCCH.

[0260] In some embodiments, the second information and the first information can be the same information, that is, the second information is identical to the first information. This minimizes the transmission resources occupied by Msg3. For example, both the first and second information can multiplex indication information indicating any one or more of the following channels: Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH and Msg4 PDSCH retransmissions use 48-bit CCCH; except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH and Msg4 PDSCH retransmissions use 64-bit CCCH; RedCap terminals use 48-bit CCCH for Msg4 HARQ-ACK PUCCH and Msg4 PDSCH retransmissions; RedCap terminals use 64-bit CCCH for Msg4 HARQ-ACK PUCCH and Msg4 PDSCH retransmissions; Enhanced RedCap terminals use 48-bit CCCH for Msg4 HARQ-ACK PUCCH and Msg4 PDSCH retransmissions; Enhanced RedCap terminals use 48-bit CCCH for Msg4 HARQ-ACK PUCCH and Msg4 PDSCH retransmissions. PDSCH is repeatedly transmitted, using 64-bit CCCH.

[0261] In other words, if Msg3 includes any one or more of the above indication information, it can be considered that the terminal simultaneously indicates that it supports (or requests) repeated transmission of Msg4 PDSCH and supports (or requests) repeated transmission of Msg4 HARQ-ACK PUCCH.

[0262] In some embodiments, the second information and the first information can be different; that is, the second information is different from the first information. This allows the terminal to separately indicate support (or request) for repeated transmission of Msg4 PDSCH and support (or request) for repeated transmission of Msg4 HARQ-ACK PUCCH, improving the flexibility of the indication.

[0263] In some embodiments, the second information differs from the first information. The first indication information can be multiplexed from one or more of the following indication information: repeated transmission of Msg4 PDSCH by the RedCap terminal using 48-bit CCCH; repeated transmission of Msg4 PDSCH by the RedCap terminal using 64-bit CCCH; repeated transmission of Msg4 PDSCH by the enhanced RedCap terminal using 48-bit CCCH; repeated transmission of Msg4 PDSCH by the enhanced RedCap terminal using 64-bit CCCH; repeated transmission of Msg4 PDSCH by terminals other than RedCap or enhanced RedCap terminals using 48-bit CCCH; repeated transmission of Msg4 PDSCH by terminals other than RedCap or enhanced RedCap terminals using 64-bit CCCH. That is, when Msg3 includes any one or more of the above indication information, it can be considered that the terminal simultaneously indicates its support (or request) for repeated transmission of Msg4 PDSCH.

[0264] In some embodiments, the second information differs from the first information. The second information may reuse one or more of the following indication information: Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH and Msg4 PDSCH repetitions each use 48-bit CCCH; except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH and Msg4 PDSCH repetitions each use 64-bit CCCH; RedCap terminals use 48-bit CCCH for Msg4 HARQ-ACK PUCCH and Msg4 PDSCH repetitions; RedCap terminals use 64-bit CCCH for Msg4 HARQ-ACK PUCCH and Msg4 PDSCH repetitions; Enhanced RedCap terminals use 48-bit CCCH for Msg4 HARQ-ACK PUCCH and Msg4 PDSCH repetitions; Enhanced RedCap terminals use 48-bit CCCH for Msg4 HARQ-ACK PUCCH and Msg4 PDSCH repetitions. PDSCH is repeatedly transmitted, each using a 64-bit CCCH. That is, if Msg3 includes any one or more of the above indication information, it can be considered that the terminal simultaneously indicates its support for (or request) Msg4 HARQ-ACK PUCCH repeated transmission.

[0265] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2103. For example, step S2101 may be implemented as a standalone embodiment, step S2102 may be implemented as a standalone embodiment, step S2103 may be implemented as a standalone embodiment, step S2102+S2103 may be implemented as a standalone embodiment, etc., but is not limited thereto.

[0266] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.

[0267] In the embodiments disclosed herein, each step and its optional implementation can also be carried out independently.

[0268] In this embodiment, the terminal indicates to the network device via Msg3 whether it supports (or requests) Msg4 PDSCH retransmission, thereby providing conditions for realizing Msg4 PDSCH retransmission and downlink coverage enhancement, and improving the performance and reliability of the communication system.

[0269] Figure 2B is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 2B, the communication method in this embodiment is executed by a communication system, which may include a terminal and network devices. As shown in Figure 2B, the method includes:

[0270] Step S2201: The terminal sends message Msg3.

[0271] Msg3 carries first information, which indicates one or more of the following: requesting Msg4 PDSCH to be retransmitted; the terminal supports Msg4 PDSCH retransmission.

[0272] In some embodiments, the network device receives Msg3 containing first information.

[0273] In some embodiments, the terminal can determine that Msg3 carries the first information when the downlink reference signal received power RSRP is less than a first threshold value.

[0274] In some embodiments, when the network device receives Msg3 carrying first information, it can determine that the downlink reference signal received power RSRP is less than a first threshold value.

[0275] In some embodiments, the first information described above is also used to indicate one or more of the following:

[0276] The limited-capability RedCap terminal repeatedly transmits Msg4 PDSCH using the 48-bit common control channel CCCH.

[0277] RedCap terminals repeatedly transmit Msg4 PDSCH, using 64-bit CCCH.

[0278] Enhanced Msg4 PDSCH retransmission of RedCap terminals, using 48-bit CCCH;

[0279] Enhance the Msg4PDSCH retransmission of RedCap terminals, using 64-bit CCCH;

[0280] For repeated transmissions of Msg4 PDSCH except for RedCap or Enhanced RedCap terminals, use 48-bit CCCH;

[0281] Except for RedCap or Enhanced RedCap terminals, repeated transmissions of Msg4 PDSCH use 64-bit CCCH;

[0282] Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission and Msg4 PDSCH retransmission use 48-bit CCCH respectively.

[0283] Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively;

[0284] RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0285] RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0286] Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively;

[0287] Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

[0288] In some embodiments, the terminal and network device may also determine that the terminal supports repeated transmission of Msg4 PDSCH when it is determined that the terminal supports repeated transmission of Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH).

[0289] In some embodiments, the terminal may also receive configuration parameters for repeated transmission of Msg4 PDSCH, wherein the configuration parameters satisfy one or more of the following:

[0290] At the same time, Msg4 PDSCH retransmission and Msg4 HARQ-ACK physical uplink control channel PUCCH retransmission function are enabled.

[0291] The Msg4 PDSCH repeat transmission function is enabled, but the first threshold value and the second threshold value are not configured. The first threshold value is used to trigger Msg4 PDSCH repeat transmission, and the second threshold value is used to trigger Msg4 HARQ-ACK PUCCH repeat transmission.

[0292] The first threshold value that triggers repeated transmission of Msg4 PDSCH is less than the second threshold value that triggers repeated transmission of Msg4 HARQ-ACK PUCCH.

[0293] In some embodiments, the network device may send configuration parameters for repeated transmission of Msg4 PDSCH to the terminal.

[0294] In some embodiments, Msg3 further includes second information, which indicates one or more of the following: supporting repeated transmission of Msg4 HARQ-ACK physical uplink control channel PUCCH; requesting repeated transmission of Msg4 HARQ-ACK PUCCH.

[0295] In some embodiments, the second information described above may be the same as or different from the first information.

[0296] In some embodiments, the second indication information described above is also used to indicate one or more of the following:

[0297] Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission and Msg4 PDSCH retransmission use 48-bit CCCH respectively.

[0298] Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively;

[0299] RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0300] RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0301] Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively;

[0302] Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

[0303] In this embodiment, the terminal indicates to the network device via Msg3 whether it supports (or requests) Msg4 PDSCH retransmission, thereby providing conditions for realizing Msg4 PDSCH retransmission and downlink coverage enhancement, and improving the performance and reliability of the communication system.

[0304] The communication method provided in this disclosure will be further described below with reference to the following embodiments.

[0305] The UE carries indication information in msg3 to indicate PDSCH repetition for msg4.

[0306] In some embodiments, instructing PDSCH repetition for msg4 is used to tell the network device that the terminal supports PDSCH repetition for msg4, or to tell the network device that the terminal requests PDSCH repetition for msg4. For the latter, the network configures an RSRP threshold; if the RSRP of the downlink path loss reference point is less than this threshold, the UE triggers a request for PDSCH repetition for msg4.

[0307] In some embodiments, network devices can enable the PDSCH repetition for msg4 function via system messages. This can be done explicitly or implicitly. Implicit enabling includes, for example, broadcasting PDSCH repetition for msg4 related parameters in the system message, such as the list of PDSCH repetition counts for Msg4, RSRP threshold configuration, etc. Only when the network has enabled the PDSCH repetition for msg4 function can the UE indicate PDSCH repetition for msg4 in Msg3.

[0308] Optionally, the above indication information is used to indicate one or more of the following:

[0309] For RedCap UEs with limited capabilities, Msg4 PDSCH repetition is performed using a 48-bit Common Control Channel (CCCH).

[0310] The Msg4 PDSCH repetition of a RedCap UE uses a 64-bit CCCH.

[0311] Enhanced Msg4 PDSCH repetition for RedCap UEs by using a 48-bit CCCH (CCCH of size 48 bits for Msg4 PDSCH repetition for an eRedCap UE);

[0312] Enhance the Msg4PDSCH repetition transmission of RedCap terminals by using a 64-bit CCCH (CCCH of size 64 bits for Msg4 PDSCH repetition for an eRedCap UE);

[0313] For Msg4 PDSCH repetitions except for RedCap or Enhanced RedCap UEs, a 48-bit CCCH is used.

[0314] Except for RedCap or Enhanced RedCap terminals, Msg4 PDSCH repetition uses a 64-bit CCCH (CCCH of size 64 bits for Msg4 PDSCH repetition, except for an(e)RedCap UE);

[0315] Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) repetition and Msg4 PDSCH repetition use 48-bit CCCH (CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK & Msg4 PDSCH repetition, except for an(e)RedCap UE);

[0316] Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH repetition and Msg4 PDSCH repetition use 64-bit CCCH (CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK & Msg4 PDSCH repetition, except for an(e)RedCap UE);

[0317] The Msg4 HARQ-ACK PUCCH repetition and Msg4 PDSCH repetition of a RedCap UE use 48-bit CCCH (CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK & Msg4 PDSCH repetition of a RedCap UE);

[0318] The Msg4 HARQ-ACK PUCCH repetition and Msg4 PDSCH repetition of a RedCap UE use 64-bit CCCH (CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK & Msg4 PDSCH repetition of a RedCap UE);

[0319] Enhance the Msg4 HARQ-ACK PUCCH repetition and Msg4 PDSCH repetition of RedCap terminals, using 48-bit CCCH (CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK & Msg4 PDSCH repetition of an eRedCap UE);

[0320] Enhance the Msg4 HARQ-ACK PUCCH repetition and Msg4 PDSCH repetition of RedCap terminals by using 64-bit CCCH (CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK & Msg4 PDSCH repetition of an eRedCap UE).

[0321] Optionally, if the terminal supports Msg4 repetition, it must also support PUCCH repetition of Msg4 HARQ-ACK.

[0322] Optionally, the PDSCH repetition for msg4 parameter configured on the network device must meet at least one of the following conditions:

[0323] If the network has enabled the Msg4 PDSCH repetition function, then the PUCCH repetition of Msg4 HARQ-ACK function must also be enabled.

[0324] If the network enables the Msg4 PDSCH repetition function but does not configure the RSRP threshold for Msg4 PDSCH repetition, then the RSRP threshold for PUCCH repetition of Msg4 HARQ-ACK will not be configured.

[0325] The RSRP threshold for triggering Msg4 PDSCH repetition in the network configuration must be less than the RSRP threshold for triggering PUCCH repetition of Msg4 HARQ-ACK in the network configuration.

[0326] In some embodiments, the RSRP threshold for PUCCH repetition of Msg4 HARQ-ACK is: rsrp-ThresholdMsg4. RSRP is the RSRP of the downlink path loss reference point. Because the channel for PUCCH for Msg4 HARQ-ACK is always worse than Msg4 PDSCH, the RSRP threshold of the downlink path loss reference point that triggers PUCCH repetition is greater than the RSRP threshold that triggers Msg4 PDSCH repetition.

[0327] In some embodiments, if the network enables Msg4 PDSCH repetition and PUCCH repetition of Msg4 HARQ-ACK via system messages, but does not configure the RSRP threshold for Msg4 PDSCH repetition, then the RSRP threshold for PUCCH repetition of Msg4 HARQ-ACK is also not configured.

[0328] Optionally, if the terminal indicates Msg4 PDSCH repetition via Msg3, then it must also indicate PUCCH repetition of Msg4 HARQ-ACK.

[0329] In some embodiments, the indication of PUCCH repetition of Msg4 HARQ-ACK can be either explicit or implicit. For implicit indications, such as if the terminal indicates Msg4 PDSCH repetition, the network considers that the terminal has simultaneously indicated PUCCH repetition of Msg4 HARQ-ACK.

[0330] In some embodiments, the network enables the Msg4 PDSCH repetition function but does not configure an RSRP threshold. The UE triggers the reporting of the Msg4 PDSCH repetition capability via msg3. If the network configures an RSRP threshold, and the RSRP value of the downlink path loss reference point is less than the RSRP threshold configured for Msg4 PDSCH repetition, the UE triggers the reporting of the Msg4 PDSCH repetition capability via msg3. When the terminal determines that it needs to report Msg4 PDSCH repetition, regardless of whether the network enables PUCCH repetition of Msg4 HARQ-ACK, whether it configures the RSRP threshold for the downlink path loss reference point of PUCCH repetition, or whether the RSRP of the downlink path loss reference point is less than the RSRP threshold for the downlink path loss reference point of PUCCH repetition, it simultaneously indicates PUCCH repetition of Msg4 HARQ-ACK. For explicit indications, one of the following can be indicated simultaneously:

[0331] Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission and Msg4 PDSCH retransmission use 48-bit CCCH respectively.

[0332] Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively;

[0333] RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0334] RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0335] Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively;

[0336] Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

[0337] Optionally, if the terminal indicates PUCCH repetition of Msg4 HARQ-ACK via Msg3, it is not necessary to indicate Msg4PDSCH repetition indication at the same time.

[0338] This disclosure also provides an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0339] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0340] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0341] Figure 3 is a schematic diagram of the structure of the communication device proposed in an embodiment of this disclosure. As shown in Figure 3, the communication device 3100 may include at least one of a transceiver module 3101, a processing module 3102, etc.

[0342] In some embodiments, the communication device 3100 is a terminal, and the transceiver module is used to send message Msg3, wherein Msg3 carries first information, the first information being used to indicate one or more of the following: requesting Msg4 to be retransmitted on the Physical Downlink Shared Channel (PDSCH); the terminal supports Msg4 PDSCH retransmission.

[0343] In some embodiments, the above processing module is used to:

[0344] If the downlink reference signal received power RSRP is less than the first threshold, it is determined that Msg3 carries the first information.

[0345] In some embodiments, the first information described above is also used to indicate one or more of the following:

[0346] The limited-capability RedCap terminal repeatedly transmits Msg4 PDSCH using the 48-bit common control channel CCCH.

[0347] RedCap terminals repeatedly transmit Msg4 PDSCH, using 64-bit CCCH.

[0348] Enhanced Msg4 PDSCH retransmission of RedCap terminals, using 48-bit CCCH;

[0349] Enhance the Msg4PDSCH retransmission of RedCap terminals, using 64-bit CCCH;

[0350] For repeated transmissions of Msg4 PDSCH except for RedCap or Enhanced RedCap terminals, use 48-bit CCCH;

[0351] Except for RedCap or Enhanced RedCap terminals, repeated transmissions of Msg4 PDSCH use 64-bit CCCH;

[0352] Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission and Msg4 PDSCH retransmission use 48-bit CCCH respectively.

[0353] Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively;

[0354] RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0355] RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0356] Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively;

[0357] Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

[0358] In some embodiments, the above-described processing module is further configured to:

[0359] The terminal supports Msg4 PDSCH retransmission and confirms support for Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission.

[0360] In some embodiments, the transceiver module described above can also be used for:

[0361] Configuration parameters for receiving repeated transmissions of Msg4 PDSCH, wherein the configuration parameters satisfy one or more of the following:

[0362] At the same time, Msg4 PDSCH retransmission and Msg4 HARQ-ACK physical uplink control channel PUCCH retransmission function are enabled.

[0363] The Msg4 PDSCH repeat transmission function is enabled, but the first threshold value and the second threshold value are not configured. The first threshold value is used to trigger Msg4 PDSCH repeat transmission, and the second threshold value is used to trigger Msg4 HARQ-ACK PUCCH repeat transmission.

[0364] The first threshold value that triggers repeated transmission of Msg4 PDSCH is less than the second threshold value that triggers repeated transmission of Msg4 HARQ-ACK PUCCH.

[0365] In some embodiments, Msg3 may further include second information, which indicates one or more of the following: supporting repeated transmission of Msg4 HARQ-ACK physical uplink control channel PUCCH, and requesting repeated transmission of Msg4 HARQ-ACK PUCCH.

[0366] In some embodiments, the second information described above may be the same as or different from the first information.

[0367] In some embodiments, the second indication information described above is also used to indicate one or more of the following:

[0368] Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission and Msg4 PDSCH retransmission use 48-bit CCCH respectively.

[0369] Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively;

[0370] RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0371] RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0372] Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively;

[0373] Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

[0374] Optionally, the transceiver module described above is used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal in any of the above methods, which will not be elaborated here.

[0375] Optionally, the above processing module is used to perform at least one of the other steps executed by the terminal in any of the above methods, which will not be elaborated here.

[0376] In some embodiments, the communication device 3100 is a network device, and the transceiver module is used to receive message Msg3, wherein Msg3 carries first information, the first information being used to indicate one or more of the following: requesting Msg4 to be retransmitted on the Physical Downlink Shared Channel (PDSCH), and the terminal supporting Msg4 PDSCH retransmission.

[0377] In some embodiments, the above processing module is used to:

[0378] Msg3 contains the first information, which determines that the reference signal received power RSRP of the downlink path loss reference point is less than a first threshold value.

[0379] In some embodiments, the first information described above is also used to indicate one or more of the following:

[0380] The limited-capability RedCap terminal repeatedly transmits Msg4 PDSCH using the 48-bit common control channel CCCH.

[0381] RedCap terminals repeatedly transmit Msg4 PDSCH, using 64-bit CCCH.

[0382] Enhanced Msg4 PDSCH retransmission of RedCap terminals, using 48-bit CCCH;

[0383] Enhance the Msg4PDSCH retransmission of RedCap terminals, using 64-bit CCCH;

[0384] For repeated transmissions of Msg4 PDSCH except for RedCap or Enhanced RedCap terminals, use 48-bit CCCH;

[0385] Except for RedCap or Enhanced RedCap terminals, repeated transmissions of Msg4 PDSCH use 64-bit CCCH;

[0386] Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission and Msg4 PDSCH retransmission use 48-bit CCCH respectively.

[0387] Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively;

[0388] RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0389] RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0390] Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively;

[0391] Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

[0392] In some embodiments, the above-described processing module is further configured to:

[0393] The first information indicates that the terminal supports repeated transmission of Msg4 PDSCH, and confirms that the terminal supports repeated transmission of Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH).

[0394] In some embodiments, the transceiver module described above can also be used for:

[0395] Configuration parameters for sending repeated Msg4 PDSCH transmissions, wherein the configuration parameters satisfy one or more of the following:

[0396] At the same time, Msg4 PDSCH retransmission and Msg4 HARQ-ACK physical uplink control channel PUCCH retransmission function are enabled.

[0397] The Msg4 PDSCH repeat transmission function is enabled, but the first threshold value and the second threshold value are not configured. The first threshold value is used to trigger Msg4 PDSCH repeat transmission, and the second threshold value is used to trigger Msg4 HARQ-ACK PUCCH repeat transmission.

[0398] The first threshold value that triggers repeated transmission of Msg4 PDSCH is less than the second threshold value that triggers repeated transmission of Msg4 HARQ-ACK PUCCH.

[0399] In some embodiments, Msg3 may further include second information, which indicates one or more of the following: supporting repeated transmission of Msg4 HARQ-ACK physical uplink control channel PUCCH, and requesting repeated transmission of Msg4 HARQ-ACK PUCCH.

[0400] In some embodiments, the second information described above may be the same as or different from the first information.

[0401] In some embodiments, the second indication information described above is also used to indicate one or more of the following:

[0402] Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission and Msg4 PDSCH retransmission use 48-bit CCCH respectively.

[0403] Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively;

[0404] RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0405] RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH.

[0406] Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively;

[0407] Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

[0408] Optionally, the transceiver module described above is used to perform at least one of the communication steps such as sending and / or receiving performed by the network device in any of the above methods, which will not be elaborated here.

[0409] Optionally, the above processing module is used to perform at least one of the other steps performed by the network device in any of the above methods, which will not be elaborated here.

[0410] Figure 4A is a schematic diagram of the structure of the communication device 4100 proposed in an embodiment of this disclosure. The communication device 4100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 4100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0411] As shown in Figure 4A, the communication device 4100 includes one or more processors 4101. The processor 4101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. The communication device 4100 is used to execute any of the above methods.

[0412] In some embodiments, the communication device 4100 further includes one or more memories 4102 for storing instructions. Optionally, all or part of the memories 4102 may also be located outside the communication device 4100.

[0413] In some embodiments, the communication device 4100 further includes one or more transceivers 4103. When the communication device 4100 includes one or more transceivers 4103, the transceivers 4103 perform at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2103, S2103), and the processor 4101 performs other steps, such as step S2102.

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

[0415] In some embodiments, the communication device 4100 may include one or more interface circuits 4104. Optionally, the interface circuit 4104 is connected to the memory 4102, and the interface circuit 4104 can be used to receive signals from the memory 4102 or other devices, and can be used to send signals to the memory 4102 or other devices. For example, the interface circuit 4104 can read instructions stored in the memory 4102 and send the instructions to the processor 4101.

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

[0417] Figure 4B is a schematic diagram of the structure of chip 4200 according to an embodiment of this disclosure. For cases where the communication device 4100 can be a chip or a chip system, please refer to the schematic diagram of chip 4200 shown in Figure 4B, but it is not limited thereto.

[0418] Chip 4200 includes one or more processors 4201, which are used to perform any of the above methods.

[0419] In some embodiments, chip 4200 further includes one or more interface circuits 4202. Optionally, the interface circuit 4202 is connected to memory 4203, and the interface circuit 4202 can be used to receive signals from memory 4203 or other devices, and the interface circuit 4202 can be used to send signals to memory 4203 or other devices. For example, the interface circuit 4202 can read instructions stored in memory 4203 and send the instructions to processor 4201.

[0420] In some embodiments, the interface circuit 4202 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 4201 performs at least one of the other steps.

[0421] In some embodiments, the terms interface circuit, interface, transceiver pin, transceiver, etc., can be used interchangeably.

[0422] In some embodiments, chip 4200 further includes one or more memories 4203 for storing instructions. Optionally, all or part of the memories 4203 may be located outside of chip 4200.

[0423] This disclosure also proposes a storage medium storing instructions that, when executed on the communication device 4100, cause the communication device 4100 to perform 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 not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0424] This disclosure also provides a program product that, when executed by the communication device 4100, causes the communication device 4100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0425] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

[0426] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0427] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0428] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0429] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A communication method characterized by comprising: include: Send message Msg3, wherein Msg3 carries first information, the first information being used to indicate one or more of the following: Request Msg4 Physical Downlink Shared Channel (PDSCH) retransmission; Terminal supports Msg4 PDSCH retransmission.

2. The method of claim 1, wherein, The method further includes: If the downlink reference signal received power RSRP is less than a first threshold, it is determined that the first information is carried in Msg3.

3. The method of claim 1 or 2, wherein, The first information is also used to indicate one or more of the following: The limited-capability RedCap terminal repeatedly transmits Msg4 PDSCH using the 48-bit common control channel CCCH. RedCap terminals repeatedly transmit Msg4 PDSCH, using 64-bit CCCH. Enhanced Msg4 PDSCH retransmission of RedCap terminals, using 48-bit CCCH; Enhanced Msg4 PDSCH retransmission of RedCap terminals, using 64-bit CCCH; Except for RedCap or Enhanced RedCap terminals, repeated transmissions of Msg4 PDSCH use 48-bit CCCH; Except for RedCap or Enhanced RedCap terminals, repeated transmissions of Msg4 PDSCH use 64-bit CCCH; Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission and Msg4 PDSCH retransmission use 48-bit CCCH respectively. Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively; RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH. RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH. Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively; Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The terminal supports Msg4 PDSCH retransmission and confirms support for Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Configuration parameters for receiving repeated transmissions of Msg4 PDSCH, wherein the configuration parameters satisfy one or more of the following: At the same time, Msg4 PDSCH retransmission and Msg4 HARQ-ACK physical uplink control channel PUCCH retransmission function are enabled. The Msg4 PDSCH repeat transmission function is enabled, but the first threshold value and the second threshold value are not configured. The first threshold value is used to trigger Msg4 PDSCH repeat transmission, and the second threshold value is used to trigger Msg4 HARQ-ACK PUCCH repeat transmission. The first threshold value that triggers repeated transmission of Msg4 PDSCH is less than the second threshold value that triggers repeated transmission of Msg4 HARQ-ACK PUCCH.

6. The method of any one of claims 1-5, wherein, The Msg3 also includes second information, which indicates one or more of the following: Supports repeated transmission of Msg4 hybrid automatic repeat request acknowledgment (HARQ-ACK) on the physical uplink control channel (PUCCH); Request Msg4 HARQ-ACK PUCCH to be transmitted again.

7. The method of claim 6, wherein, The second information may be the same as or different from the first information.

8. The method of claim 6 or 7, wherein, The second indication information is also used to indicate one or more of the following: Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission and Msg4 PDSCH retransmission use 48-bit CCCH respectively. Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively; RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH. RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH. Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively; Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

9. A communication method characterized by comprising: include: Receive message Msg3, wherein Msg3 carries first information, the first information being used to indicate one or more of the following: Request Msg4 Physical Downlink Shared Channel (PDSCH) retransmission; Terminal supports Msg4 PDSCH retransmission.

10. The method of claim 9, wherein, The method further includes: Msg3 contains the first information, which determines that the downlink reference signal received power RSRP is less than a first threshold value.

11. The method of claim 9 or 10, wherein, The first information is also used to indicate one or more of the following: The limited-capability RedCap terminal repeatedly transmits Msg4 PDSCH using the 48-bit common control channel CCCH. RedCap terminals repeatedly transmit Msg4 PDSCH, using 64-bit CCCH. Enhanced Msg4 PDSCH retransmission of RedCap terminals, using 48-bit CCCH; Enhanced Msg4 PDSCH retransmission of RedCap terminals, using 64-bit CCCH; For repeated transmissions of Msg4 PDSCH except for RedCap or Enhanced RedCap terminals, use 48-bit CCCH; Except for RedCap or Enhanced RedCap terminals, repeated transmissions of Msg4 PDSCH use 64-bit CCCH; Except for RedCap or Enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission and Msg4 PDSCH retransmission use 48-bit CCCH respectively. Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively; RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH. RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH. Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively; Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

12. The method of any one of claims 9-11, wherein, The method further includes: The first information indicates that the terminal supports repeated transmission of Msg4 PDSCH, and confirms that the terminal supports repeated transmission of Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH).

13. The method of any one of claims 9-12, wherein, The method further includes: Configuration parameters for sending repeated Msg4 PDSCH transmissions, wherein the configuration parameters satisfy one or more of the following: The Msg4 PDSCH retransmission function and the Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) retransmission function are enabled. The Msg4 PDSCH repeat transmission function is enabled, but the first threshold value and the second threshold value are not configured. The first threshold value is used to trigger Msg4 PDSCH repeat transmission, and the second threshold value is used to trigger Msg4 HARQ-ACK PUCCH repeat transmission. The first threshold value that triggers repeated transmission of Msg4 PDSCH is less than the second threshold value that triggers repeated transmission of Msg4 HARQ-ACK PUCCH.

14. The method of any one of claims 9-13, wherein, The Msg3 also includes second information, which indicates one or more of the following: Supports repeated transmission of Msg4 hybrid automatic repeat request acknowledgment (HARQ-ACK) on the physical uplink control channel (PUCCH); Request Msg4 HARQ-ACK PUCCH to be transmitted again.

15. The method of claim 14, wherein, The second information may be the same as or different from the first information.

16. The method of claim 14 or 15, wherein, The second indication information is also used to indicate one or more of the following: except for RedCap or enhanced RedCap terminals, Msg4 Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) Physical Uplink Control Channel (PUCCH) and Msg4 PDSCH are repeatedly transmitted, each using 48 bits of CCCH. Except for RedCap or Enhanced RedCap terminals, Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission use 64-bit CCCH respectively; RedCap terminals use 48-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH. RedCap terminals use 64-bit CCCH for repeated transmission of Msg4 HARQ-ACK PUCCH and Msg4 PDSCH. Enhance the Msg4 HARQ-ACK PUCCH retransmission and Msg4 PDSCH retransmission of the RedCap terminal, using 48-bit CCCH respectively; Enhance the Msg4 HARQ-ACK PUCCH repetitive transmission and Msg4 PDSCH repetitive transmission of RedCap terminals, using 64-bit CCCH respectively.

17. A communication device, characterized by The communication device is used to perform the method as described in any one of claims 1-8, 9-16.

18. A communication system, characterized by The device includes a terminal and a network device, wherein the terminal is used to perform the method as described in any one of claims 1-8, and the network device is used to perform the method as described in any one of claims 9-16.

19. A storage medium, the storage medium storing instructions, wherein, When the instruction is executed on the communication device, the communication device performs the known method as described in any one of claims 1-16.

20. A computer program product, characterised in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1-16.

Images