Communication method and communication device

Abstract

The present application provides a communication method and a communication device. The method includes the steps of: after transmitting uplink information to a network device, a terminal device receiving a physical downlink control channel (PDCCH) carrying downlink control information from the network device, where the PDCCH is used to schedule downlink information, and both the uplink information and the downlink information are information in a random access procedure; and the terminal device decoding the PDCCH. After successful decoding, the terminal device obtains the downlink control information and determines whether to continue operating the downlink information based on the downlink control information. If the terminal device determines not to continue operating the downlink information based on the downlink control information, the terminal device can further determine that the random access has failed. Because whether the random access has failed is determined based on the PDCCH, a delay in the terminal device determining that the random access has failed can be reduced.

Description

[Technical Field]

[0001] This application claims priority to Chinese Patent Application No. 202310237163.0, entitled "Communication Method and Communication Apparatus," filed with the State Intellectual Property Office of the People's Republic of China on March 2, 2023, which is incorporated herein by reference in its entirety.

[0002] The present application relates to the field of communications technology, and more particularly to communication methods and devices. [Background technology]

[0003] The network device configures multiple random access resources for the terminal device, so that the terminal device selects one random access resource from the multiple random access resources to perform the random access procedure. When multiple terminal devices select the same random access resource, resulting in a random access conflict, the network device broadcasts a physical downlink control channel (PDCCH) to the multiple terminal devices. The PDCCH is used to schedule a physical downlink shared channel (PDSCH), which carries information about terminal devices that have successfully performed random access.

[0004] A terminal device that has succeeded in random access can determine that the random access has been successful based on the information carried in the PDSCH, and a terminal device that has not succeeded in random access can determine that the random access has failed based on the information carried in the PDSCH. However, in the above procedure, a terminal device that has not succeeded in random access needs to take a longer time to determine that the random access has failed. Summary of the Invention

[0005] Therefore, how to reduce the delay when a terminal device that has not succeeded in random access determines that the random access has failed has become an urgent technical problem that needs to be solved at present. [Means for solving the problem]

[0006] The present application provides a communication method and a communication apparatus to reduce the delay when a terminal device that has not succeeded in random access determines that the random access has failed.

[0007] According to a first aspect, a communication method is provided, the method including: a terminal device transmitting uplink information on a first resource; after transmitting the uplink information, the terminal device receiving a PDCCH carrying downlink control information, where the PDCCH is used to schedule downlink information, and the uplink information and the downlink information are information in a random access procedure; the terminal device decoding the PDCCH; if the terminal device successfully decodes the PDCCH, the terminal device determining, based on the downlink control information, whether to operate the downlink information, or the terminal device determining, based on the downlink control information, whether to continue the current random access procedure, or the terminal device receiving the downlink information; and the terminal device determining, according to the downlink information, a start time of a physical uplink control channel fed back, where a time interval between an end time of the downlink information and a start time of transmitting the physical uplink control channel satisfies a minimum time interval.

[0008] Specifically, the terminal device can determine whether to continue operating the downlink information based on the downlink control information in the PDCCH. If the terminal device determines not to continue operating the downlink information based on the downlink control information, the terminal device can accordingly determine that the random access of the terminal device has failed, and does not need to wait for the contention resolution timer to expire before determining that the random access contention has failed. In this way, the delay when the terminal device determines that the random access has failed can be reduced, so that the terminal device can initiate a new random access as soon as possible, thereby reducing the random access delay and the power consumption of the terminal device.

[0009] In one possible implementation, the uplink information is a physical uplink shared channel in message A and the downlink information is a random access response in message B, or the uplink information is message 3 and the downlink information is message 4 or contention resolution information.

[0010] Specifically, when the uplink information is the physical uplink shared channel in message A and the downlink information is the random access response in message B, the terminal device can determine that the random access procedure initiated by the terminal device has failed based on the downlink control information. In this way, the delay when the terminal device determines that the random access procedure has failed can be reduced. When the uplink information is message 3 and the downlink information is message 4 or contention resolution information, the terminal device can determine that the random access contention has failed based on the downlink control information, and does not need to wait for the contention resolution timer to expire before determining that the random access contention has failed. In this way, the delay when the terminal device determines that the random access contention has failed can be reduced.

[0011] In one possible implementation, the downlink control information includes a frequency domain resource allocation (FDRA) field, and the FDRA field is used to allocate resource blocks for transmitting downlink information. If the number of allocated resource blocks exceeds a first threshold, the terminal device does not operate the downlink information; or if the number of allocated resource blocks exceeds the first threshold, the terminal device does not operate the downlink information; and the first terminal device determines that the current random access has failed; or if the number of allocated resource blocks exceeds the first threshold, the terminal device does not continue the current random access procedure; or if the number of allocated resource blocks exceeds the first threshold, the terminal device does not continue the current random access procedure; and the first terminal device determines that the current random access has failed; or if the number of allocated resource blocks exceeds the first threshold, the terminal device operates the downlink information; and the terminal device determines that the minimum time interval is equal to the sum of the first time interval and a first value, where the first value is greater than 0.

[0012] In this way, the terminal device can determine whether the random access has failed based on the number of resource blocks indicated in the downlink control information, and does not need to wait for the contention resolution timer to expire before determining that the random access contention has failed. Furthermore, the delay in the terminal device determining that the random access has failed can be reduced, and the power consumption of the terminal device can be reduced.

[0013] In one possible implementation, the downlink control information includes an FDRA field, and the FDRA field is used to allocate resource blocks for transmitting downlink information. If the number of allocated resource blocks does not exceed a first threshold, the terminal device operates the downlink information, or if the number of allocated resource blocks does not exceed the first threshold, the terminal device continues the current random access procedure, or if the number of allocated resource blocks does not exceed the first threshold, the terminal device determines that the minimum time interval is equal to the first time interval.

[0014] In one possible implementation, the downlink control information includes time indication information, and the time indication information is used to determine a time unit for transmitting the physical uplink control channel. If the time interval between the end of the downlink information and the start of transmitting the physical uplink control channel is less than a second threshold, the terminal device does not operate the downlink information, or if the time interval between the end of the downlink information and the start of transmitting the physical uplink control channel is less than the second threshold, the terminal device does not operate the downlink information and determines that the current random access has failed, or if the time interval between the end of the downlink information and the start of transmitting the physical uplink control channel is less than the second threshold, the terminal device does not continue the current random access procedure, or if the time interval between the end of the downlink information and the start of transmitting the physical uplink control channel is less than the second threshold, the terminal device does not continue the current random access procedure and determines that the current random access has failed.

[0015] In this way, the terminal device can determine whether the random access has failed based on the time interval between the end of the downlink control information and the start of transmitting the physical uplink control channel, which is indicated in the downlink control information, and does not need to wait for the contention resolution timer to expire before determining that the random access contention has failed. Furthermore, the delay when the terminal device determines that the random access has failed can be reduced, and the power consumption of the terminal device can be reduced.

[0016] In one possible implementation, the downlink control information includes time indication information, and the time indication information is used to determine a time unit for transmitting the physical uplink control channel. If the time interval between the end of the downlink information and the start of transmitting the physical uplink control channel is equal to or greater than a second threshold, the terminal device determines to operate the downlink information, or if the time interval between the end of the downlink information and the start of transmitting the physical uplink control channel is equal to or greater than a second threshold, the terminal device determines to continue the current random access procedure.

[0017] In one possible implementation, the downlink control information includes first instruction information, which instructs a terminal device having a first characteristic parameter to manipulate the downlink information.

[0018] In this way, there is no need to wait for the contention resolution timer to expire before determining that the random access contention has failed, so the delay when the terminal device determines that the random access has failed can be reduced, and the power consumption of the terminal device can be reduced.

[0019] In one possible implementation, if the feature parameter of the terminal device is not the first feature parameter, the terminal device does not operate the downlink information, or if the feature parameter of the terminal device is not the first feature parameter, the terminal device does not operate the downlink information and the terminal device determines that the current random access has failed, or if the feature parameter of the terminal device is not the first feature parameter, the terminal device does not continue the current random access procedure, or if the feature parameter of the terminal device is not the first feature parameter, the terminal device does not continue the current random access procedure and the terminal device determines that the current random access has failed, or if the feature parameter of the terminal device is the first feature parameter, the terminal device operates the downlink information.

[0020] In one possible implementation, the terminal device reports the characteristic parameters using message 3, and / or the maximum bandwidth for transmitting unicast data of the terminal device is less than or equal to 5 MHz, or the number of resource blocks used for transmitting unicast data of the terminal device is less than or equal to M, and / or the maximum bandwidth for processing unicast data of the terminal device is less than or equal to 5 MHz, or the number of resource blocks used for processing unicast data of the terminal device is less than or equal to M, where M is a positive integer, or there is a correspondence between the value of M and the subcarrier spacing.

[0021] According to a second aspect, a communication method is provided, the method including: a network device receiving uplink information, the uplink information being information in a random access procedure; and a network device transmitting a PDCCH carrying downlink control information, the PDCCH being used to schedule the downlink information, the downlink information being information in the random access procedure. The PDCCH is used by a first terminal device to determine whether to manipulate the downlink information, or the PDCCH is used by the first terminal device to determine whether to continue a current random access procedure.

[0022] In one possible implementation, the uplink information is a physical uplink shared channel in message A and the downlink information is a random access response in information B, or the uplink information is message 3 and the downlink information is information 4 or contention resolution information.

[0023] In one possible implementation, the downlink control information includes first instruction information, which instructs a terminal device having a first characteristic parameter to manipulate the downlink information.

[0024] According to a third aspect, there is provided a communication method including: a first terminal device transmitting first information on a first resource, the first information being used for a random access procedure; a first terminal device receiving a physical downlink control channel (PDCCH), the PDCCH being used to carry a response to the first information; and a first terminal device determining, based on the PDCCH, that the random access has failed.

[0025] In one possible implementation, the PDCCH includes first indication information, the first indication information indicating that random access has failed, and the first terminal device determining that the random access has failed based on the PDCCH includes the first terminal device determining that the random access has failed based on the first indication information.

[0026] In one possible implementation, the PDCCH includes second indication information, the second indication information indicating the number of resources of a first physical downlink shared channel (PDSCH), and determining by the first terminal device based on the PDCCH that the random access has failed includes the first terminal device determining that the random access has failed based on the number of resources of the first PDSCH.

[0027] In one possible implementation, the PDCCH includes third indication information and fourth indication information, the third indication information indicating a time domain resource of the second PDSCH, and the fourth indication information indicating a time domain resource of a physical uplink control channel (PUCCH) for feeding back the second PDSCH, and determining by the first terminal device that the random access has failed based on the PDCCH includes the first terminal device determining that the random access has failed based on a time interval between the time domain resource of the second PDSCH and the time domain resource of the PUCCH.

[0028] In one possible implementation, the PDCCH includes fifth indication information, the fifth indication information indicating resource information of a third PDSCH, the third PDSCH includes sixth indication information, the sixth indication information indicating resource information of a physical uplink shared channel (PUSCH), and determining by the first terminal device that the random access has failed based on the PDCCH includes the first terminal device determining that the random access has failed based on the number of resources of the third PDSCH and a time interval between the time domain resources of the third PDSCH and the time domain resources of the PUSCH.

[0029] In one possible implementation, the method further includes a step in which a lower layer of the first terminal device sends seventh indication information, wherein the seventh indication information indicates that the first terminal device cannot process the PDSCH, or the seventh indication information indicates that the first terminal device has failed to process the PDSCH.

[0030] In one possible implementation, the method further includes the first terminal device stopping a conflict resolution timer.

[0031] In one possible implementation, the first information indicates a type of the first terminal device, the first resource is further used by the second terminal device to transmit second information, the second information is used in a random access procedure, and the processing capability of the first terminal device is lower than the processing capability of the second terminal device.

[0032] According to a fourth aspect, there is provided a communication method, comprising: a step of a network device receiving first information on a first resource, the first information being used for a random access procedure; and a step of the network device transmitting a physical downlink control channel PDCCH, the PDCCH being used to carry a response to the first information, and the PDCCH being used by the first terminal device to determine that the random access has failed.

[0033] In one possible implementation, the PDCCH includes first indication information, and the first indication information indicates that the random access has failed.

[0034] In one possible implementation, the PDCCH includes second indication information, which indicates the number of resources of a first physical downlink shared channel (PDSCH), and the number of resources of the first PDSCH is used by the first terminal device to determine that the random access has failed.

[0035] In one possible implementation, the PDCCH includes third indication information and fourth indication information, where the third indication information indicates a time domain resource of a second PDSCH, and the fourth indication information indicates a time domain resource of a physical uplink control channel (PUCCH) for feeding back the second PDSCH, and a time interval between the time domain resource of the second PDSCH and the time domain resource of the PUCCH is used by the first terminal device to determine that the random access has failed.

[0036] In one possible implementation, the PDCCH includes fifth indication information, the fifth indication information indicating resource information of a third PDSCH, the third PDSCH includes sixth indication information, the sixth indication information indicating resource information of a physical uplink shared channel PUSCH, and the number of resources of the third PDSCH and the time interval between the time domain resources of the third PDSCH and the time domain resources of the PUSCH are used by the first terminal device to determine that the random access has failed.

[0037] In one possible implementation, the first information indicates a type of the first terminal device, the first resource is further used by the second terminal device to transmit second information to the network device, the second information is used in a random access procedure, and the processing capability of the first terminal device is lower than the processing capability of the second terminal device.

[0038] According to a fifth aspect, there is provided a communication device, which may be used in the terminal device of the first aspect. The communication device may be the terminal device, a device (e.g., a chip, a chip system, or a circuit) in the terminal device, or a device that may be used in conjunction with the terminal device.

[0039] In one possible implementation, the communication device may include modules or units that correspond one-to-one to the methods / operations / steps / actions described in the first aspect. The modules or units may be implemented by hardware circuits, software, or a combination of hardware circuits and software.

[0040] In one possible implementation, the communications apparatus includes: a transceiver unit configured to transmit uplink information on a first resource, the transceiver unit being further configured to receive a PDCCH carrying downlink control information after transmitting the uplink information, the PDCCH being used to schedule the downlink information, and the uplink information and the downlink information being information in a random access procedure; and a processing unit configured to decode the PDCCH. If the PDCCH is successfully decoded, the processing unit is further configured to determine whether to operate the downlink information based on the downlink control information, or the processing unit is further configured to determine whether to continue the current random access procedure based on the downlink control information, or the transceiver unit is further configured to receive the downlink information, the processing unit is further configured to determine a start time of a physical uplink control channel fed back in response to the downlink information, and the time interval between the end time of the downlink information and the start time of transmitting the PUCCH satisfies a minimum time interval.

[0041] In one possible implementation, the uplink information is a physical uplink shared channel in message A and the downlink information is a random access response in message B, or the uplink information is message 3 and the downlink information is message 4 or contention resolution information.

[0042] In one possible implementation, the downlink control information includes a frequency domain resource allocation (FDRA) field, which is used to allocate resource blocks for transmission of downlink information. If the number of allocated resource blocks exceeds a first threshold, the processing unit is further configured to determine not to operate the downlink information, or if the number of allocated resource blocks exceeds the first threshold, the processing unit is further configured to determine not to operate the downlink information, the processing unit is further configured to determine that a current random access has failed, or if the number of allocated resource blocks exceeds the first threshold, the processing unit is further configured to determine not to continue the current random access procedure, or if the number of allocated resource blocks exceeds the first threshold, the processing unit is further configured to determine not to continue the current random access procedure, the processing unit is further configured to determine that a current random access has failed, or if the number of allocated resource blocks exceeds the first threshold, the processing unit is further configured to operate the downlink information, and the processing unit is further configured to determine that the minimum time interval is equal to the sum of the first time interval and a first value, the first value being greater than 0.

[0043] In one possible implementation, the downlink control information includes an FDRA field, and the FDRA field is used to allocate resource blocks for transmission of the downlink information. If the number of allocated resource blocks does not exceed a first threshold, the processing unit is further configured to determine to operate the downlink information, or if the number of allocated resource blocks does not exceed the first threshold, the processing unit is further configured to determine to continue the current random access procedure, or if the number of allocated resource blocks does not exceed the first threshold, the processing unit is further configured to determine that the minimum time interval is equal to the first time interval.

[0044] In one possible implementation, the downlink control information includes time indication information, and the time indication information is used to determine a time unit for transmitting the physical uplink control channel. If a time interval between an end of the downlink information and a start of transmitting the physical uplink control channel is less than a second threshold, the processing unit is further configured to determine not to operate the downlink information, or if a time interval between an end of the downlink information and a start of transmitting the physical uplink control channel is less than the second threshold, the processing unit is further configured to determine not to operate the downlink information and the processing unit is further configured to determine that a current random access has failed, or if a time interval between an end of the downlink information and a start of transmitting the physical uplink control channel is less than the second threshold, the processing unit is further configured to determine not to continue the current random access procedure, or if a time interval between an end of the downlink information and a start of transmitting the physical uplink control channel is less than the second threshold, the processing unit is further configured to determine not to continue the current random access procedure and the processing unit is further configured to determine that a current random access has failed.

[0045] In one possible implementation, the downlink control information includes time indication information, and the time indication information is used to determine a time unit for transmitting the physical uplink control channel. If a time interval between an end point of the downlink information and a start point of transmitting the physical uplink control channel is equal to or greater than a second threshold, the processing unit is further configured to determine to operate the downlink information, or if a time interval between an end point of the downlink information and a start point of transmitting the physical uplink control channel is equal to or greater than a second threshold, the processing unit is further configured to determine to continue the current random access procedure.

[0046] In one possible implementation, the downlink control information includes first instruction information, which instructs a terminal device having a first characteristic parameter to manipulate the downlink information.

[0047] In one possible implementation, if the feature parameter of the communication device is not the first feature parameter, the processing unit is further configured to determine not to manipulate the downlink information, or if the feature parameter of the communication device is not the first feature parameter, the processing unit is further configured to determine not to manipulate the downlink information, and the processing unit is further configured to determine that the current random access has failed, or if the feature parameter of the communication device is not the first feature parameter, the processing unit is further configured to determine not to continue the current random access procedure, or if the feature parameter of the communication device is not the first feature parameter, the processing unit is further configured to determine not to continue the current random access procedure, and the processing unit is further configured to determine that the current random access has failed, or if the feature parameter of the communication device is the first feature parameter, the processing unit is further configured to determine to manipulate the downlink information.

[0048] In one possible implementation, the transceiver unit is further configured to report the characteristic parameters using message 3, and / or the maximum bandwidth for transmitting unicast data of the communication device is less than or equal to 5 MHz, or the number of resource blocks used for transmitting unicast data of the communication device is less than or equal to M, and / or the maximum bandwidth for processing unicast data of the communication device is less than or equal to 5 MHz, or the number of resource blocks used for processing unicast data of the communication device is less than or equal to M, where M is a positive integer, or there is a correspondence between the value of M and the subcarrier spacing.

[0049] According to a sixth aspect, there is provided a communication device, which may be used in the network device of the second aspect. The communication device may be the network device, a device (e.g., a chip, a chip system, or a circuit) in the network device, or a device that may be used in conjunction with the network device.

[0050] In one possible implementation, the communication device may include modules or units that correspond one-to-one to the methods / operations / steps / actions described in the second aspect. The modules or units may be implemented by hardware circuits, software, or a combination of hardware circuits and software.

[0051] In one possible implementation, the communication apparatus includes a transceiver unit configured to receive uplink information, where the uplink information is information in a random access procedure. The transceiver unit is further configured to transmit a PDCCH carrying downlink control information, where the PDCCH is used to schedule the downlink information, where the downlink information is information in the random access procedure. The PDCCH is used by the first terminal device to determine whether to manipulate the downlink information, or the PDCCH is used by the first terminal device to determine whether to continue a current random access procedure.

[0052] In one possible implementation, the uplink information is a physical uplink shared channel in message A and the downlink information is a random access response in information B, or the uplink information is message 3 and the downlink information is information 4 or contention resolution information.

[0053] In one possible implementation, the downlink control information includes first instruction information, which instructs a terminal device having a first characteristic parameter to manipulate the downlink information.

[0054] According to a seventh aspect, there is provided a communication device, which may be used in the terminal device of the third aspect. The communication device may be the terminal device, a device (e.g., a chip, a chip system, or a circuit) in the terminal device, or a device that may be used in conjunction with the terminal device.

[0055] In one possible implementation, the communication device may include modules or units that correspond one-to-one to the methods / operations / steps / actions described in the third aspect. The modules or units may be implemented by hardware circuits, software, or a combination of hardware circuits and software.

[0056] In one possible implementation, the communication device includes a transceiver unit configured to transmit first information on a first resource, where the first information is used for a random access procedure, the transceiver unit further configured to receive a PDCCH, where the PDCCH is used to carry a response to the first information, and a processing unit configured to determine that the random access has failed based on the PDCCH.

[0057] In one possible implementation, the PDCCH includes first indication information, the first indication information indicating that the random access has failed, and the processing unit is further configured to determine that the random access has failed based on the first indication information.

[0058] In one possible implementation, the PDCCH includes second indication information, the second indication information indicating the number of resources of the first PDSCH, and the processing unit is further configured to determine that the random access has failed based on the number of resources of the first PDSCH.

[0059] In one possible implementation, the PDCCH includes third indication information and fourth indication information, the third indication information indicating a time domain resource of the second PDSCH, and the fourth indication information indicating a time domain resource of the PUCCH for feeding back the second PDSCH, and the processing unit is further configured to determine that the random access has failed based on a time interval between the time domain resource of the second PDSCH and the time domain resource of the PUCCH.

[0060] In one possible implementation, the PDCCH includes fifth indication information, the fifth indication information indicating resource information of a third PDSCH, the third PDSCH includes sixth indication information, the sixth indication information indicating resource information of a physical uplink shared channel (PUSCH), and the processing unit is further configured to determine that the random access has failed based on the number of resources of the third PDSCH and a time interval between the time domain resources of the third PDSCH and the time domain resources of the PUSCH.

[0061] In one possible implementation, the transceiver unit is further configured to transmit seventh indication information, wherein the seventh indication information indicates that the communication device is unable to process the PDSCH, or the seventh indication information indicates that the communication device has failed to process the PDSCH.

[0062] In one possible implementation, the processing unit is further configured to stop the conflict resolution timer.

[0063] In one possible implementation, the first information indicates the type of the communication device, the first resource is further used by a second terminal device to transmit second information, the second information is used in a random access procedure, and the processing capability of the communication device is lower than the processing capability of the second terminal device.

[0064] According to an eighth aspect, there is provided a communication device, which may be used in the network device of the fourth aspect. The communication device may be the network device, a device (e.g., a chip, a chip system, or a circuit) in the network device, or a device that may be used in conjunction with the network device.

[0065] In one possible implementation, the communication device may include modules or units that correspond one-to-one to the methods / operations / steps / actions described in the fourth aspect. The modules or units may be implemented by hardware circuits, software, or a combination of hardware circuits and software.

[0066] In one possible implementation, the communications apparatus includes a transceiver unit configured to receive first information on a first resource, the first information being used for a random access procedure, the transceiver unit further configured to transmit a PDCCH, the PDCCH being used to carry a response to the first information, and the PDCCH being used by the first terminal device to determine that the random access has failed.

[0067] In one possible implementation, the PDCCH includes first indication information, and the first indication information indicates that the random access has failed.

[0068] In one possible implementation, the PDCCH includes second indication information, which indicates the number of resources of a first physical downlink shared channel (PDSCH), and the number of resources of the first PDSCH is used by the first terminal device to determine that the random access has failed.

[0069] In one possible implementation, the PDCCH includes third indication information and fourth indication information, where the third indication information indicates a time domain resource of a second PDSCH, and the fourth indication information indicates a time domain resource of a physical uplink control channel (PUCCH) for feeding back the second PDSCH, and a time interval between the time domain resource of the second PDSCH and the time domain resource of the PUCCH is used by the first terminal device to determine that the random access has failed.

[0070] In one possible implementation, the PDCCH includes fifth indication information, the fifth indication information indicating resource information of a third PDSCH, the third PDSCH includes sixth indication information, the sixth indication information indicating resource information of a physical uplink shared channel PUSCH, and the number of resources of the third PDSCH and the time interval between the time domain resources of the third PDSCH and the time domain resources of the PUSCH are used by the first terminal device to determine that the random access has failed.

[0071] In one possible implementation, the first information indicates a type of the first terminal device, the first resource is further used by the second terminal device to transmit second information to the network device, the second information is used in a random access procedure, and the processing capability of the first terminal device is lower than the processing capability of the second terminal device.

[0072] According to a ninth aspect, there is provided a communications device including a processor, the processor being configured to execute a computer program or instructions, or logic circuitry, to enable the communications device to perform a method according to the first aspect and any one of its possible implementations, or to enable the communications device to perform a method according to the second aspect and any one of its possible implementations, or to enable the communications device to perform a method according to the third aspect and any one of its possible implementations, or to enable the communications device to perform a method according to the fourth aspect and any one of its possible implementations.

[0073] In one possible implementation, the communications device further includes a memory configured to store computer programs or instructions.

[0074] In one possible implementation, the communication device further includes a communication interface configured to input and / or output signals.

[0075] According to a tenth aspect, there is provided a communication device including a logic circuit and an input / output interface, the input / output interface configured to input and / or output signals, and the logic circuit configured to perform a method according to the first aspect and any one of its possible implementations, or the logic circuit configured to perform a method according to the second aspect and any one of its possible implementations, or the logic circuit configured to perform a method according to the third aspect and any one of its possible implementations, or the logic circuit configured to perform a method according to the fourth aspect and any one of its possible implementations.

[0076] According to an eleventh aspect, there is provided a computer-readable storage medium storing a computer program or instructions that, when executed on a computer, performs a method according to the first aspect and any one of its possible implementations, or a method according to the second aspect and any one of its possible implementations, or a method according to the third aspect and any one of its possible implementations, or a method according to the fourth aspect and any one of its possible implementations.

[0077] According to a twelfth aspect, there is provided a computer program product comprising instructions which, when executed on a computer, cause a method according to the first aspect and any one of its possible implementations to be performed, or a method according to the second aspect and any one of its possible implementations, or a method according to the third aspect and any one of its possible implementations, or a method according to the fourth aspect and any one of its possible implementations.

[0078] According to a thirteenth aspect, there is provided a communication system including a terminal device and a network device, wherein the terminal device is configured to perform a method according to the first aspect and any one of its possible implementations, and the network device is configured to perform a method according to the first aspect and any one of its possible implementations, or the terminal device is configured to perform a method according to the third aspect and any one of its possible implementations, and the network device is configured to perform a method according to the fourth aspect or any one of its possible implementations.

[0079] For the description of the beneficial effects of the second to thirteenth aspects, please refer to the corresponding description of the beneficial effects of the first aspect, and the details will not be described again here. [Brief explanation of the drawings]

[0080] [Figure 1] 1 is a diagram of an application scenario 100 according to an embodiment of the present application. [Figure 2] FIG. 2 is a diagram of a random access procedure 200. [Figure 3] 3 is a schematic interaction flowchart of a communication method 300 according to an embodiment of the present application. [Figure 4] FIG. 2 is a diagram of a time interval between time domain resources of Downlink Information 1 and PUCCH 1 according to an embodiment of the present application; [Figure 5] 5 is a block diagram of the structure of a communication device 500 according to an embodiment of the present application. [Figure 6] 6 is a block diagram of the structure of a communication device 600 according to an embodiment of the present application. [Figure 7] 7 is a block diagram of the structure of a communication device 700 according to an embodiment of the present application. [Figure 8] 8 is a block diagram of the structure of a communication device 800 according to an embodiment of the present application. [Figure 9] 9 is a block diagram of the structure of a communication device 900 according to an embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0081] The technical solutions of the present application are described below with reference to the accompanying drawings.

[0082] The technical solutions of the embodiments of the present application are applicable to various communication systems, such as long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunication systems (UMTS), fifth generation (5G) systems, etc. th generation (5G) system or new radio (NR), sixth generation (6 thThe present invention may be applied to systems evolved after 5G, such as 6G (6th generation) systems, NTN systems, such as inter-satellite communication systems, and satellite communication systems. The satellite communication system includes a satellite base station and a terminal device. The satellite base station provides communication services to the terminal device. The satellite base station can also communicate with a terrestrial base station. The satellite may be used as a base station or as a terminal device. The satellite may be a non-terrestrial base station, a non-terrestrial device, or the like, such as an unmanned aerial vehicle, a hot air balloon, a low-earth orbit satellite, a medium-earth orbit satellite, or a high-earth orbit satellite.

[0083] The technical solutions of the embodiments of the present application are applicable to both homogeneous and heterogeneous network scenarios. In addition, the transmission points are not limited. Coordinated multi-point transmission can be performed between macro base stations, between micro base stations, and between macro and micro base stations. The technical solutions of the embodiments of the present application are applicable to FDD systems / TDD systems. The technical solutions of the present application are not only applicable to low-frequency scenarios (sub 6G), but also to high-frequency scenarios (above 6 GHz), terahertz, optical communications, etc. The technical solutions of the present application are not only applicable to communications between network devices and terminals, but also to communications between network devices, communications between terminals, communications for the Internet of Vehicles, the Internet of Things, and the Industrial Internet, etc.

[0084] The technical solutions of the embodiments of the present application can also be applied to a scenario in which a terminal is connected to a single base station. The base station connected to the terminal and the core network (CN) connected to the base station are of the same standard. For example, if the CN is a 5G Core, the corresponding base station is a 5G base station, and the 5G base station is directly connected to the 5G Core, or the CN is a 6G Core, and the base station is a 6G base station, and the 6G base station is directly connected to the 6G Core. The technical solutions of the present application can also be applied to a dual connectivity (DC) scenario in which a terminal is connected to at least two base stations.

[0085] The technical solutions of the embodiments of the present application can also be applied to macro and micro scenarios involving various forms of base stations in a communication network. For example, a base station can be a satellite, a balloon station, an unmanned aerial vehicle station, etc. The technical solutions of the present application can also be applied to scenarios in which both wide-coverage and small-coverage base stations exist.

[0086] The technical solutions of the embodiments of the present application can be applied to scenarios where services have high reliability requirements, such as port, industrial manufacturing, transportation, and coal mining scenarios.

[0087] The technical solutions of the embodiments of the present application can be further applied to 5.5G, 6G, and later wireless communication systems, including but not limited to terrestrial cellular communication, NTN, satellite communication, high altitude platform station (HAPS) communication, vehicle-to-everything (V2X), integrated access and backhaul (IAB), and reconfigurable intelligent surface (RIS) communication.

[0088] A terminal in an embodiment of the present application may be a device having a wireless transceiver function, and may be a user equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment. The terminal device may alternatively be a satellite phone, a cellular phone, a smartphone, a wireless data card, a wireless modem, or a machine-type communications device, or may be a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a customer-premises equipment (CPE), a smart point of sale (POS) machine, a handheld device with wireless communications capabilities, a computing device or another processing device connected to a wireless modem, an in-vehicle device, a communications device onboard a high-altitude aircraft, a wearable device, an unmanned aerial vehicle, a robot, a device-to-device (D2D) communications terminal, a V2X terminal, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, an industrial control wireless terminal, a self-driving wireless terminal, a remote medical wireless terminal, a smart grid (Smart Grid), a wireless communication device, a wireless modem, a wireless LAN (LAN), ... The wireless terminal may be a wireless terminal for a smart grid, a wireless terminal for transportation safety, a wireless terminal for a smart city, a wireless terminal for a smart home, a terminal device in a communication network evolved after 5G, etc. This is not limited in the present application.

[0089] In an embodiment of the present application, a communication device configured to perform the functions of a terminal device may be the terminal device itself, or may be a device capable of supporting the terminal device in performing the functions, such as a chip system. The device may be installed in the terminal device or used in conjunction with the terminal device. In the present application, a chip system may include a chip, or may include a chip and another discrete device.

[0090] The network device in the embodiment of the present application is a device having a radio transceiver function and configured to communicate with a terminal device. The access network device may be a node in a radio access network (RAN) and may be called a base station or a RAN node. The access network device may be an evolved Node B (eNB or eNodeB) of LTE, a base station of a 5G network such as a gNodeB (gNB), a base station of a public land mobile network (PLMN) evolved after 5G, a broadband network gateway (BNG), an aggregation switch, a 3rd Generation Partnership Project (3GPP) LTE (LTE-LTE ... rd generation partnership project (3GPP®) access device, etc. For example, the RAN may be configured as a RAN defined by 3GPP® protocols, an open radio access network (O-RAN), or a cloud radio access network (C-RAN).

[0091] The network devices in the embodiments of the present application may further include various forms of base stations, such as macro base stations, micro base stations (also called small cells), relay stations, transmitting and receiving points (TRPs), transmitting points (TPs), mobile switching centers, devices that function as base stations in device-to-device (D2D), vehicle-to-everything (V2X), or machine-to-machine (M2M) communications, and network devices in NTN communications systems, which are not specifically limited in the present application.

[0092] The network device in the embodiments of the present application may further include a network element or module that performs some functions of a base station, for example, one or more of the following: a central unit (CU), a distributed unit (DU), or a radio unit (RU). Optionally, the CU may be further divided into a CU control plane (CP) and a CU user plane (UP). The functions of the CU and DU may be performed by separate network elements, or both may be performed by a base station baseband unit (BBU). The functions of the RU may be performed by a radio frequency device of the base station. For example, the radio frequency device of the base station may be a remote radio unit (RRU), a pico remote radio unit (pRRU), an active antenna unit (AAU), or another unit, module, or device having radio frequency processing functionality. The communication interface protocol between the BBU and the radio frequency device may be, but is not limited to, a common public radio interface (CPRI) interface protocol, an enhanced common public radio interface (eCPRI) interface protocol, a fronthaul interface protocol between a DU and a RU in an O-RAN system, etc.

[0093] In embodiments of the present application, an apparatus configured to perform the functions of a network device may be a network device or may be an apparatus capable of supporting a network device in performing the functions, such as a chip system. The apparatus may be installed within a network device or used in conjunction with a network device. In embodiments of the present application, the chip system may include a chip or may include a chip and another discrete device.

[0094] To facilitate understanding of the embodiments of the present application, the following provides a brief description of relevant concepts of the present application.

[0095] UEs in the present application may be classified into a first type of terminal device and a second type of terminal device. For example, the first type of terminal device may be, for example, a reduced capability UE, and the second type of terminal device may be a non-reduced capability UE. For example, the first type of terminal device may be, for example, a reduced capability UE (REDCAP UE), and the second type of terminal device may be a legacy UE, for example, an enhanced mobile broadband (eMBB) UE. For example, the first type of terminal device may be, for example, an enhanced reduced capability UE (EREDCAP UE), and the second type of terminal device may be a reduced capability UE (REDCAP UE).

[0096] The first type terminal device and the second type terminal device have different characteristics, which are as follows: The first feature may include one or more of the following: bandwidth, number of supported or configured resources, number of transmit antenna ports and / or number of receive antenna ports, number of radio frequency channels, number of hybrid automatic repeat request (HARQ) processes, supported peak rate, application scenario, delay requirement, processing capability, protocol release, duplexing scheme, service, etc., and the first feature is described in detail below.

[0097] Bandwidth, channel bandwidth, or maximum channel bandwidth supported or configured by the terminal device: The bandwidth of the first type terminal device and the second type terminal device are different. For example, the bandwidth of the first type terminal device may be 20 MHz, 10 MHz, or 5 MHz, and the bandwidth of the second type terminal device may be 100 MHz. It should be understood that with the development of communication technology, the maximum channel bandwidth supported by the first type terminal device may no longer be 20 MHz, 10 MHz, or 5 MHz, but may evolve to a wider or narrower bandwidth, for example, 3 MHz, 25 MHz, or 50 MHz.

[0098] Number of supported or configured resources: The number of resources may be the number of RBs, REs, subcarriers, RB groups, REG bundles, control channel elements, subframes, radio frames, slots, minislots, and / or symbols. The number of resources supported or configured by a first type of terminal device is different from that of a second type of terminal device. For example, the number of resources supported by a first type of terminal device is 48 RBs, and the number of resources supported by a second type of terminal device is 96 RBs.

[0099] Number of transmitting antenna ports and / or number of receiving antenna ports: The number of transmitting antenna ports and / or the number of receiving antenna ports of the first type terminal device is different from that of the second type terminal device. For example, the number of transmitting antenna ports of the first type terminal device may be 1, the number of receiving antenna ports of the first type terminal device may be 2, the number of transmitting antenna ports of the second type terminal device may be 2, and the number of receiving antenna ports of the second type terminal device may be 4.

[0100] Number of radio frequency channels: The number of radio frequency channels of the first type terminal device is different from that of the second type terminal device. For example, the number of radio frequency channels of the first type terminal device may be 1, and the number of radio frequency channels of the second type terminal device may be 2.

[0101] Number of hybrid automatic repeat request (HARQ) processes: The number of HARQ processes supported by the first type terminal device is different from that of the second type terminal device. For example, the number of HARQ processes of the first type terminal device may be 8, and the number of HARQ processes of the second type terminal device may be 16.

[0102] Supported peak rate: The maximum peak rates of the first type terminal device and the second type terminal device are different. For example, the maximum peak rate supported by the first type terminal device may be 100 Mbps, and the peak rate supported by the second type terminal device may be 200 Mbps.

[0103] Application scenarios: The first type of terminal device and the second type of terminal device are suitable for different application scenarios, such as industrial wireless sensing, video surveillance, wearable devices, etc., and the second type of terminal device is suitable for mobile communications, video Internet access, etc.

[0104] Delay requirement: The first type terminal device and the second type terminal device have different requirements for transmission delay. For example, the delay requirement of the first type terminal device may be 500 milliseconds, and the delay requirement of the second type terminal device may be 100 milliseconds.

[0105] Processing capability: The first type terminal device and the second type terminal device have different processing speeds for channels or data processing time series under different subcarrier spacing (SCS) conditions. For example, the first type terminal device does not support composite operations, and the composite operations may include artificial intelligence (AI) and VR rendering, while the second type terminal device supports composite operations. Alternatively, this can be understood as the processing capability of the first type terminal device being lower than that of the second type terminal device.

[0106] Protocol Release: The first type of terminal device and the second type of terminal device are terminal devices of different protocol releases. For example, the protocol releases supported by the first type of terminal device are Release 17 and protocol releases later than Release 17, and the protocol releases supported by the second type of terminal device are protocol releases earlier than Release 17, such as Release 15 or Release 16. For example, the protocol release supported by the first type of terminal device is protocol release Release 18, and the protocol release supported by the second type of terminal device is a protocol release earlier than Release 18, such as Release 15, Release 16, or Release 17.

[0107] Duplex mode: The duplex mode includes half-duplex and full-duplex. For example, a first type of terminal device operates in half-duplex mode, and a second type of terminal device operates in full-duplex mode.

[0108] Service: The service includes, but is not limited to, Internet of Things applications such as video surveillance and mobile broadband MBB. For example, the service supported by the first type of terminal device is video surveillance, and the service supported by the second type of terminal device is mobile broadband MBB. This is not limited in the embodiments of the present application.

[0109] It should be understood that other types or future new types of terminal devices that support the technical solutions of the present application are also within the protection scope of the present application.

[0110] In this application, terminal device 120 may be an example of a first type of terminal device, and terminal device 130 may be an example of a second type of terminal device.

[0111] It should be understood that features in this application may also be understood as feature parameters, and the two may be used interchangeably in this application.

[0112] 1 is a diagram of an application scenario 100 according to an embodiment of the present application. As shown in FIG. 1, communication devices in the application scenario 100 include, but are not limited to, a network device 110, a terminal device 120, and a terminal device 130. Uplink or downlink communication may be performed between the network device 110 and the terminal device 120, and uplink or downlink communication may be performed between the network device 110 and the terminal device 130. This is not limited here. It should be understood that the application scenario 100 is used only as an example for understanding and cannot limit the scope of protection claimed in the present application.

[0113] In the application scenario 100, the network device 110 configures multiple random access resources for the terminal device (the terminal device 120 and the terminal device 130 are not distinguished), and the terminal device 120 and the terminal device 130 randomly select one random access resource from the multiple random access resources to perform a random access procedure. If the terminal device 120 and the terminal device 130 randomly select the same random access resource, a random access conflict exists between the terminal device 120 and the terminal device 130. The network device 110 needs to resolve the random access conflict between the terminal device 120 and the terminal device 130. In other words, the network device 110 needs to determine one of the terminal device 120 and the terminal device 130 as a terminal device that has successfully completed random access, and determine the other terminal device as a terminal device that has not successfully completed random access. Please refer to FIG. 2 for an explanation of the random access procedure.

[0114] 2 is a diagram of a random access procedure 200. As shown in FIG. 2, the random access procedure 200 includes the following steps:

[0115] S210: The terminal device 120 transmits random access request information 1 to the network device 110 on the random access resource 1, and the terminal device 130 transmits random access request information 2 to the network device 110 on the random access resource 1.

[0116] Correspondingly, the network device 110 receives the random access request information 1 sent by the terminal device 120 and the random access request information 2 sent by the terminal device 130. When the network device 110 receives both the random access request information 1 and the random access request information 2 on the random access resource 1, the network device 110 determines that a random access conflict has occurred between the terminal device 120 and the terminal device 130.

[0117] S220: The network device 110 transmits random access response (RAR) information 1 to the terminal device 120, and the network device 110 transmits RAR information 2 to the terminal device .

[0118] Correspondingly, the terminal device 120 receives RAR information 1 from the network device 110, which is used to respond to the random access request information 1, and determines, based on the RAR information 1, that a random access conflict has occurred between the terminal device 120 and the terminal device 130. The terminal device 130 receives RAR information 2 from the network device 110, which is used to respond to the random access request information 2, and determines, based on the RAR information 2, that a random access conflict has occurred between the terminal device 130 and the terminal device 120.

[0119] Specifically, the RAR information 1 may indicate to the terminal device 120 that a random access conflict has occurred, and the RAR information 2 may indicate to the terminal device 130 that a random access conflict has occurred. The RAR information 1 may include resource information of a physical uplink shared channel (PUSCH) 1 used by the terminal device 120 to transmit the random access conflict information 1 to the network device 110, and the RAR information 2 may include resource information of a PUSCH 2 used by the terminal device 130 to transmit the random access conflict information 2 to the network device 110.

[0120] S230: The terminal device 120 transmits random access conflict contention information 1 to the network device 110 through PUSCH 1, and the terminal device 130 transmits random access conflict contention information 2 to the network device 110 through PUSCH 2.

[0121] Correspondingly, network device 110 receives random access conflict information 1 sent by terminal device 120 and random access conflict information 2 sent by terminal device 130 .

[0122] Specifically, based on random access conflict conflict information 1 and random access conflict conflict information 2, network device 110 determines one of terminal device 120 and terminal device 130 as a terminal device that has succeeded in random access, and determines the other as a terminal device that has not succeeded in random access.

[0123] S240: The network device 110 broadcasts the PDCCH to the terminal device 120 and the terminal device 130.

[0124] Correspondingly, the terminal device 120 and the terminal device 130 receive a PDCCH from the network device 110. Specifically, when the network device 110 determines that the terminal device 120 is a terminal device that has successfully completed random access, the network device 110 broadcasts a PDCCH to the terminal device 120 and the terminal device 130. The PDCCH is used to schedule a PDSCH, and the PDSCH carries information about the terminal device 120. Correspondingly, the terminal device 120 determines that the terminal device 120 is a terminal device that has successfully completed random access based on the information about the terminal device 120 carried in the PDSCH, and the terminal device 120 determines that the terminal device 130 is a terminal device that has not successfully completed random access based on the actual information about the terminal device 120 carried in the PDSCH.

[0125] From the above, it can be seen that both the terminal device that has succeeded in random access and the terminal device that has not succeeded in random access need to detect the PDCCH and PDSCH. In the above procedure, the terminal device that has not succeeded in random access will experience a longer delay when determining that the random access has failed. As a result, the terminal device that has not succeeded in random access will not be able to start a new random access procedure in a timely manner.

[0126] In order to solve the above technical problems, the present application provides a communication method and a communication device for reducing the delay when a terminal device that has not succeeded in random access determines that the random access has failed.

[0127] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, a communication method and a communication device according to embodiments of the present application will be described with reference to the accompanying drawings.

[0128] Fig. 3 is a schematic interaction flowchart of a communication method 300 according to an embodiment of the present application. The method procedures in Fig. 3 may be performed by the terminal device 120 and the network device 110, or may be performed by modules and / or components (e.g., chips or integrated circuits) having corresponding functions installed in the terminal device 120 and the network device 110. This is not limited in the present application. In the following, the terminal device 120 and the network device 110 are used as examples for description. As shown in Fig. 3, the method 300 includes the following steps:

[0129] S310: The terminal device 120 sends uplink information 1 to the network device 110 on resource 1, where the uplink information 1 is information in a random access procedure.

[0130] S320: The network device 110 transmits a PDCCH 1 carrying downlink control information 1 to the terminal device 120, where the PDCCH 1 is used to schedule the downlink information 1, and the downlink information 1 is information in a random access procedure.

[0131] Correspondingly, terminal device 120 receives PDCCH 1 carrying downlink control information 1 from network device 110 .

[0132] Specifically, after sending uplink information 1 to the network device 110 , the terminal device 120 receives PDCCH 1 from the network device 110 .

[0133] S330: The terminal device 120 decodes the PDCCH 1.

[0134] S340: The terminal device 120 determines whether to operate the downlink information 1 based on the downlink control information 1, or the terminal device 120 determines whether to continue the current random access procedure based on the downlink control information 1, or the terminal device 120 receives the downlink information 1, and the terminal device 120 determines the start time of feeding back a physical uplink control channel (PUCCH) 1 according to the downlink information 1.

[0135] At S340, after the terminal device 120 successfully completes decoding of PDCCH 1, the terminal device 120 obtains the downlink control information 1 carried by PDCCH 1, and can determine corresponding operations according to the downlink control information 1.

[0136] In one example, the terminal device 120 determines whether to manipulate the downlink information 1 based on the downlink control information 1. For example, the downlink control information 1 instructs the terminal device 120 to manipulate the downlink information, or the downlink control information 1 instructs the terminal device 120 not to manipulate the downlink information. In this way, the downlink control information 1 can instruct the terminal device 120 whether to continue manipulating the downlink information.

[0137] For example, the operation may be any one of receiving, processing, storing, demodulating, decoding, channel estimation, etc. This is not limited here. Alternatively, the operation may be understood as a behavior of the terminal device not specified in the standard or a process determined by the terminal device.

[0138] It will be understood that decoding the PDCCH referred to in this application may be at least one of the following: detecting the PDCCH, performing blind monitoring on the PDCCH, receiving the PDCCH, demodulating the PDCCH, decoding the PDCCH, performing channel estimation on the PDCCH, analyzing the PDCCH, etc.

[0139] It should be understood that if the terminal device 120 determines to manipulate the downlink information 1 based on the downlink control information 1, the terminal device 120 determines to continue the current random access procedure. For example, the terminal device 120 is a terminal device that has successfully performed random access. If the terminal device 120 determines not to manipulate the downlink information 1 based on the downlink control information 1, the terminal device 120 does not continue the current random access procedure. For example, the terminal device 120 is a terminal device that has not successfully performed random access. In this way, the delay in the terminal device 120 determining that the random access has failed can be reduced, and power consumption can be further reduced.

[0140] It should be understood that a random access failure in this application may be understood as a contention resolution failure in the random access procedure, a RAR reception failure in the random access procedure, or a preamble transmission failure. For example, whether the random access has failed may be whether the random access procedure request has failed. As described above, if the uplink information 1 is random access request information, the terminal device 120 determines whether the random access procedure request initiated by the terminal device 120 has failed based on the PDCCH 1. In other words, whether the network device 110 rejects the random access procedure request of the terminal device 120. Alternatively, whether the random access has failed may be whether contention resolution has failed. As described above, if the uplink information 1 is contention resolution information in the random access procedure, the terminal device 120 determines whether contention resolution of the terminal device 120 has failed based on the PDCCH 1. In short, regardless of the scenario, the terminal device 120 can determine whether the random access has failed based on the PDCCH 1.

[0141] In one possible implementation, if the time interval between the end of the PDCCH and the start of the downlink information scheduled using the PDCCH exceeds a third threshold, the terminal device does not receive the downlink information. If the time interval between the end of the PDCCH and the start of the downlink information scheduled using the PDCCH does not exceed the third threshold, the terminal device does not process the downlink information. For example, the third threshold is the time length for processing the PDCCH by the terminal device. For example, the third threshold is N symbols, where N is a positive integer. For example, the value of the third threshold may be 3 symbols, 2 symbols, or 1 symbol. For example, the third threshold is 0.5 ms or 0.25 ms. For example, the third threshold varies depending on the subcarrier spacing (SCS). For example, if the subcarrier spacing (SCS) is 15 kHz, the third threshold is 3 symbols. For example, if the subcarrier spacing (SCS) is 30 kHz, the third threshold is 4 symbols.

[0142] For example, if the index value of the last symbol of the PDCCH is within the first range, the terminal device does not receive downlink information. If the index value of the last symbol of the PDCCH is not within the first range, the terminal device does not process downlink information. For example, the first range includes at least one of the following: 14, 13, 12, and 11. For example, the first range includes at least one of the following: 14, 13, and 12. For example, the first range varies depending on the subcarrier spacing SCS. For example, if the subcarrier spacing SCS is 15 kHz, the first range includes at least one of the following: 14, 13, and 12. For example, if the subcarrier spacing SCS is 30 kHz, the first range includes at least one of the following: 14, 13, 12, 11, 10, and 9.

[0143] For example, if the interval between the slot for transmitting the PDCCH and the slot for transmitting downlink information scheduled using the PDCCH is less than N slots, the terminal device does not receive downlink information. The interval between the slot for transmitting the PDCCH and the slot for transmitting downlink information scheduled using the PDCCH is greater than K slots. For example, K is an integer. For example, K=0, 1, or 2. For example, if the slot for transmitting the PDCCH and the slot for transmitting downlink information scheduled using the PDCCH are not adjacent slots, the terminal device processes the downlink information. If the slot for transmitting the PDCCH and the slot for transmitting downlink information scheduled using the PDCCH are adjacent slots, the terminal device does not process the downlink information. For example, if the slot for transmitting the PDCCH is slot N and the slot for transmitting downlink information scheduled using the PDCCH is slot (N+K), the terminal device does not receive downlink information. Here, K is an integer greater than 1. If the slot for transmitting the PDCCH is slot N and the slot for transmitting downlink information scheduled using the PDCCH is slot (N+1), the terminal device does not process the downlink information. For example, K depends on the subcarrier spacing SCS. For example, if the subcarrier spacing SCS is 15 kHz, K=0. For example, if the subcarrier spacing SCS is 30 kHz, K=1.

[0144] For example, no processing means that reception occurs but no demodulation and / or decoding occurs.

[0145] In another example, the terminal device 120 determines whether to continue the current random access procedure based on the downlink control information 1. For example, the downlink control information 1 indicates that the terminal device 120 may continue the current random access procedure, or the downlink control information 1 instructs the terminal device 120 not to continue the current random access procedure. In this manner, the terminal device 120 can determine whether to continue the current random access procedure based on the downlink control information 1. It will be understood that if the terminal device 120 determines to continue the current random access procedure, the terminal device 120 can determine that the terminal device 120 is a terminal device that has succeeded in random access. If the terminal device 120 determines not to continue the current random access procedure, the terminal device 120 can determine that the terminal device 120 is a terminal device that has not succeeded in random access.

[0146] in short, According to the above solution, the terminal device can determine that the random access has failed based on the PDCCH, and does not need to further receive the PDSCH scheduled using the PDCCH to determine whether the random access has failed. This reduces the delay when a terminal device that has not succeeded in random access determines that the random access has failed, and reduces the power consumption of the terminal device. If a terminal device that has not succeeded in random access determines that the random access has failed based on the PDCCH, the terminal device can initiate a new random access procedure as soon as possible. In this way, the period during which a terminal device that has not succeeded in random access can initiate a new random access procedure can be shortened. For example, after a current random access has failed, the terminal device can initiate a next random access procedure in the current cell, or can select another cell to initiate a new random access procedure.

[0147] Optionally, the terminal device 120 receives downlink information 1 based on the scheduling information of the downlink control information 1, and determines a start time for feeding back PUCCH 1 according to the downlink information 1. The time interval between the end time of the downlink information 1 and the start time for transmitting PUCCH 1 satisfies a minimum time interval. In other words, the time interval between the end time of the downlink information 1 and the start time for transmitting PUCCH 1 is within the processing capability of the terminal device 120.

[0148] In one possible implementation, uplink information 1 may be a PUSCH in message A in a two-step random access channel (RACH) procedure, and downlink information 1 may be an RAR in message B in a two-step RACH procedure. Alternatively, uplink information 1 may be message 3 in a four-step RACH procedure, and downlink information 1 is message 4 or contention resolution information in a four-step RACH procedure.

[0149] Specifically, if the uplink information 1 is a PUSCH in message A and the downlink information 1 is an RAR in message B, the terminal device 120 can determine whether to continue the current random access procedure based on the downlink control information 1 in PDCCH 1. For example, the terminal device 120 can determine whether reception of the RAR has failed based on the downlink control information 1. In other words, if the terminal device 120 determines not to operate the RAR based on the downlink control information 1, the terminal device 120 determines that the random access procedure has failed. If the uplink information 1 is message 3 and the downlink information 1 is message 4, the terminal device 120 can determine whether the random access contention has failed based on the downlink control information 1. For example, if the downlink control information 1 instructs the terminal device 120 not to operate message 4, the terminal device 120 determines that the random access contention has failed. It should be understood that if the downlink control information 1 instructs the terminal device 120 to operate message 4, the terminal device 120 determines that the random access contention has succeeded.

[0150] In one possible implementation, the downlink control information 1 includes a frequency domain resource allocation (FDRA) field, which is used to allocate resource blocks for the transmission of the downlink control information 1.

[0151] Specifically, a resource block may be a resource unit. The resource unit may be a frequency domain resource unit and / or a time domain resource unit. For example, the frequency domain resource unit may be a resource block (RB), a bandwidth, a channel bandwidth, a bandwidth part (BWP), a resource block group (RBG), a resource element (RE), a subcarrier, a control channel element (CCE), a resource element group (REG), or a carrier. The time domain resource unit may be a symbol, a slot, a subslot, a subframe, a frame, a superframe, etc.

[0152] In one example, if the number of resource blocks allocated using the FDRA field to transmit downlink information 1 exceeds a first threshold, the terminal device 120 does not operate on the downlink information 1; or if the number of resource blocks allocated using the FDRA field to transmit downlink information 1 exceeds the first threshold, the terminal device 120 does not operate on the downlink information 1 and determines that the current random access has failed; or if the number of resource blocks allocated using the FDRA field to transmit downlink information 1 exceeds the first threshold, the terminal device 120 does not continue the current random access procedure; or if the number of resource blocks allocated using the FDRA field to transmit downlink information 1 exceeds the first threshold, the terminal device 120 does not continue the current random access procedure and determines that the current random access has failed. For example, the first threshold may be understood as the processing capability of the terminal device 120. For example, there is a correspondence relationship between the first threshold and the subcarrier spacing SCS. For example, if the subcarrier spacing SCS is 15 kHz, the first threshold is 25 RB. For example, if the subcarrier spacing SCS is 30 kHz, the first threshold is 12 RB.

[0153] For example, the terminal device 120 determines that the current random access has failed, and the terminal device 120 performs at least one of the following operations: stopping the contention resolution timer (ra-ContentionResolutionTimer), discarding TEMPORARY_C-RNTI, retransmitting Msg1, notifying upper layers of the terminal device 120 that the PDSCH cannot be processed, and notifying upper layers of the terminal device 120 that decoding of the PDSCH or MAC protocol data unit (PDU) has failed.

[0154] In short, the terminal device 120 can determine that the random access has failed based on the number of resource blocks indicated in the downlink control information 1. For example, if the number of resource blocks indicated in the downlink control information 1 exceeds a threshold, the terminal device 120 can determine that the random access has failed. In this way, the delay when the terminal device determines that the random access has failed can be reduced.

[0155] In one example, if the number of resource blocks allocated using the FDRA field for transmitting downlink information 1 exceeds a first threshold, the terminal device 120 operates the downlink information 1. In this case, the terminal device 120 determines that the minimum time interval is equal to the sum of the first time interval and a first value, where the first value is greater than 0. In other words, the minimum time interval exceeds the processing capability range of the terminal device 120. In other words, when the network device schedules the downlink information 1 for the terminal device, the scheduling time is within the processing capability range of the terminal device 120 or is greater than the processing capability range of the terminal device 120.

[0156] For example, the processing capability of the terminal device 120 may be a bandwidth or channel bandwidth that can be supported by the terminal device 120, a maximum channel bandwidth supported or configured by the terminal device 120, or the number of resource units that can be processed by the terminal device 120 within a unit time. For example, a unit time is one or more time-domain resource units. For example, if the subcarrier spacing is 15 kHz, the maximum number of scheduled resources supported by the terminal device 120 is 25 RBs. If the number of RBs included in resource 2 is greater than 25 RBs, the number in resource 2 is considered to be greater than the processing capability of the terminal device 120. For example, if the subcarrier spacing is 30 kHz, the maximum number of scheduled resources supported by the terminal device 120 is 12 RBs. If the number of RBs included in resource 2 is greater than 12 RBs, the terminal device 120 considers the number in resource 2 to be greater than the processing capability of the terminal device 120.

[0157] Additionally, the processing capability of the terminal device 120 may alternatively be a channel or a data processing timeline or a processing speed.

[0158] In one example, if the number of resource blocks allocated using the FDRA field for transmitting downlink information 1 does not exceed a first threshold, the terminal device 120 operates the downlink information 1; or if the number of resource blocks allocated using the FDRA field for transmitting downlink information 1 does not exceed the first threshold, the terminal device 120 continues the current random access procedure; or if the number of resource blocks allocated using the FDRA field for transmitting downlink information 1 does not exceed the first threshold, the terminal device 120 determines that the minimum time interval is equal to the first time interval. In this manner, the terminal device 120 can determine that the random access is successful based on the number of resource blocks indicated in the downlink control information 1 and can perform a subsequent procedure. For example, the subsequent procedure may be to determine whether the random access is successful based on the downlink information 1.

[0159] In one possible implementation, the downlink control information includes a frequency domain resource allocation (FDRA) field, which is used to allocate resource blocks for transmitting downlink information. If the number of allocated resource blocks exceeds a first threshold, the terminal device stops a contention resolution timer (e.g., ra-ContentionResolutionTimer) and / or discards the TEMPORARY_C-RNTI. In addition, the terminal device 120 can determine whether an operation, such as stopping the contention resolution timer, is necessary based on the relationship between the FDRA field and the first threshold. In other words, if the terminal device 120 determines that the number of allocated resource blocks is greater than the first threshold, the terminal device 120 stops the contention resolution timer, discards the TEMPORARY_C-RNTI, and / or the like. It will be understood that this solution can be implemented independently of the above-mentioned solution.

[0160] In one possible implementation, the downlink control information includes a frequency domain resource allocation (FDRA) field, which is used to allocate resource blocks for transmitting downlink information. If the number of allocated resource blocks exceeds a first threshold, a lower layer of the terminal device sends second indication information, which indicates that the terminal device cannot operate on the downlink information 1, or that the operation on the downlink information 1 has failed, or that the operation on the MAC PDU has failed. After receiving the second indication information, the terminal device stops a contention resolution timer (e.g., ra-ContentionResolutionTimer) and / or discards the TEMPORARY_C-RNTI.

[0161] In one possible implementation, downlink control information 1 includes time indication information 1, which is used to determine the time unit for transmitting PUCCH 1. PUCCH 1 is used to carry feedback information of downlink information scheduled using downlink control information 1. In this way, terminal device 120 can determine whether random access has failed based on the time interval between the end of downlink information 1 and the start of the time unit for transmitting PUCCH 1.

[0162] For example, the time unit may be a symbol, a slot, a subslot, a subframe, a frame, or a superframe.

[0163] In one example, if the time interval between the end of downlink information 1 and the start of transmitting PUCCH 1 is less than a second threshold, the terminal device 120 does not operate downlink information 1; or if the time interval between the end of downlink information 1 and the start of transmitting PUCCH 1 is less than a second threshold, the terminal device 120 does not operate downlink information 1 and determines that the current random access has failed; or if the time interval between the end of downlink information 1 and the start of transmitting PUCCH 1 is less than the second threshold, the terminal device 120 does not continue the current random access procedure; or if the time interval between the end of downlink information 1 and the start of transmitting PUCCH 1 is less than the second threshold, the terminal device 120 does not continue the current random access procedure and determines that the current random access has failed.

[0164] For example, the second threshold may be understood as the processing capability of the terminal device 120. For example, the second threshold is the PDSCH processing capability of the terminal device 120. For example, the second threshold is the Msg4 PDSCH processing capability of the terminal device 120. For example, the second threshold is the Msg2 PDSCH processing capability of the terminal device 120. For example, there is a correspondence between the second threshold and the subcarrier spacing SCS. For example, if the subcarrier spacing SCS is 15 kHz, the second threshold is 13 symbols or 14 symbols. For example, if the subcarrier spacing SCS is 30 kHz, the second threshold is 13 symbols.

[0165] In short, the terminal device 120 can determine that the random access has failed based on the time unit indicated in the downlink control information 1. For example, if the time interval between the end of the downlink information 1 and the start of transmitting PUCCH 1 is less than the second threshold, the terminal device 120 determines that the random access has failed. In this way, the delay when the terminal device determines that the random access has failed can be reduced.

[0166] In one example, if the time interval between the end of downlink information 1 and the start of transmitting PUCCH 1 is greater than or equal to the second threshold, the terminal device 120 determines to operate on downlink information 1, or if the time interval between the end of downlink information 1 and the start of transmitting PUCCH 1 is greater than or equal to the second threshold, the terminal device 120 determines to continue the current random access procedure. In this way, the terminal device 120 can determine to perform a subsequent procedure based on the time interval between the end of downlink information 1 and the start of transmitting PUCCH 1 being less than the second threshold.

[0167] 4 is a diagram of a time interval between the time domain resource of downlink information 1 and the time domain resource of PUCCH 1 according to an embodiment of the present application. As shown in FIG. 4, the time interval between the time domain resource of downlink information 1 and the time domain resource of PUCCH 1 may be the interval between the end position of the time domain resource of downlink information 1 and the start position of the time domain resource of PUCCH 1 (this is used as an example for explanation), or may be the interval between the start position of the time domain resource of downlink information 1 and the start position of the time domain resource of PUCCH 1 (not shown in FIG. 4), or may be the interval between the center position of the time domain resource of downlink information 1 and the center position of the time domain resource of PUCCH 1 (not shown in FIG. 4).

[0168] For example, the unit of the time interval may be any one of a symbol, slot, transmission opportunity, paging occasion (PO), minislot, subslot, subframe, ms, or μs. In addition, the start position, center position, end position, etc. of the time domain resource may be represented by any one of a symbol, slot, transmission opportunity, PO, minislot, subslot, subframe, ms, μs, etc. For example, the interval between the time domain resource of downlink information 1 and the time domain resource of PUCCH 1 is the interval between the end symbol of the time domain resource of downlink information 1 and the start symbol of the time domain resource of PUCCH 1. As another example, the time interval between the time domain resource of downlink information 1 and the time domain resource of PUCCH 1 is the interval between the end slot of the time domain resource of downlink information 1 and the start slot of the time domain resource of PUCCH 1.

[0169] In addition, the processing capacity of the terminal device 120 may instead be the channel or data processing time series or processing speed. A higher processing capacity of the terminal device 120 means a shorter required processing time, and a lower processing capacity of the terminal device 120 means a longer required processing time. For example, the processing capacity of the terminal device 120 is the time for the terminal device 120 to process the PDSCH, or the sum of the time for the terminal device 120 to process the downlink information 1 and the time for the terminal device 120 to feedback the processing result by signaling. Therefore, the shortest time for the terminal device 120 to process the downlink information 1 and feedback the processing result by PUCCH 1 is T1. The time interval between the scheduling of the downlink information 1 by the network device 110 and the feedback of PUCCH 1 by the network device 110 is T2. When T2 < T1, the scheduling time series of the network device 110 can be regarded as greater than or exceeding the processing capacity of the terminal device 120.

[0170] In a possible implementation, the downlink control information 1 includes the first indication information, and the first indication information instructs a terminal device having the first characteristic parameter to operate the downlink information 1.

[0171] Specifically, the characteristic parameter may be, for example, parameters related to a method of distinguishing terminal devices, including but not limited to, bandwidth, the number of supported or configured resources, the number of transmission antenna ports and / or the number of reception antenna ports, the number of radio frequency channels, the number of hybrid automatic repeat request (HARQ) processes, the supported peak rate, the applicable scenario, the delay requirement, the processing capacity, the protocol release, the multiplexing method, and the service.

[0172] If the feature parameter of the terminal device 120 is not the first feature parameter, the terminal device 120 does not operate the downlink information 1, or if the feature parameter of the terminal device 120 is not the first feature parameter, the terminal device 120 does not operate the downlink information 1 and determines that the current random access has failed, or if the feature parameter of the terminal device 120 is not the first feature parameter, the terminal device 120 does not continue the current random access procedure, or if the feature parameter of the terminal device 120 is not the first feature parameter, the terminal device 120 does not continue the current random access procedure and determines that the current random access has failed, or if the feature parameter of the terminal device 120 is the first feature parameter, the terminal device 120 operates the downlink information 1. In this way, the delay in the terminal device determining that the random access has failed can also be reduced.

[0173] In one possible implementation, PDCCH 1 includes first indication information, which is used by the terminal device to determine that the random access has failed. Specifically, PDCCH 1 transmitted by the network device 110 to the terminal device 120 includes first indication information, which is used by the terminal device 120 to determine that the random access has failed. The following describes the first indication information in various scenarios.

[0174] Scenario 1: Example 1: If the random access failure is a random access contention failure, the first indication information instructs the terminal device 120 not to operate PDSCH 1 scheduled using PDCCH 1. PDSCH 1 carries information about the terminal device that has successfully performed random access. For example, if the network device 110 determines that the terminal device 130 is a terminal device that has successfully performed random access, PDSCH 1 includes identification information of the terminal device 130. Correspondingly, the terminal device 130 determines that the terminal device 130 is a terminal device that has successfully performed random access based on the identification information of the terminal device 130 carried in PDSCH 1. Furthermore, the terminal device 120 determines that the terminal device 120 is a terminal device that has not successfully performed random access based on the first indication information. Furthermore, the terminal device 120 does not need to continue operating PDSCH 1 scheduled using PDCCH 1.

[0175] Example 2: If the random access failure is a random access contention resolution failure, the first indication information indicates to the terminal device 120 that the PDSCH 1 scheduled using the PDCCH 1 does not include contention resolution information for the terminal device 120. Correspondingly, the terminal device 120 determines not to continue the operation of the PDSCH 1 based on the first indication information, and determines that the terminal device 120 is a terminal device that did not succeed in random access.

[0176] Example 3: If the random access failure is a random access contention failure, the first indication information indicates to the terminal device 120 that the random access contention has failed. Correspondingly, the terminal device 120 determines, based on the first indication information, that the terminal device 120 is a terminal device that has not succeeded in random access. Furthermore, the terminal device 120 does not need to continue the operation of PDSCH 1 scheduled using PDCCH 1.

[0177] Scenario 2: Example 4: If the random access failure means that the reception of the random access response information has failed, the first instruction information instructs the terminal device 120 not to operate the PDSCH 2 scheduled using the PDCCH 1, and the PDSCH 2 includes resource information of the RAR information. Furthermore, the terminal device 120 does not need to continue operating the PDSCH 2.

[0178] Example 5: If the random access failure means that the reception of random access response information has failed, the first indication information indicates to the terminal device 120 that the PDSCH 2 does not include resource information in the RAR information of the terminal device 120. Furthermore, the terminal device 120 does not need to continue operating the PDSCH 2.

[0179] Example 6: When the random access failure means that the reception of the random access response information has failed, the first indication information indicates to the terminal device 120 that the reception of the RAR information has failed. In this way, the terminal device 120 does not need to operate PDSCH 2.

[0180] In one possible implementation, the first indication information is carried in a downlink assignment index (DAI) field. For example, PDCCH 1 is a PDCCH for scheduling Msg4. For example, the first terminal device parses PDCCH 1 in a first manner. The first manner is that PDCCH 1 includes the first indication information and does not include a DAI field. For example, the first terminal device parses PDCCH 1 in a second manner. The second manner is that PDCCH 1 includes the first indication information, the PDCCH 1 includes a DAI field, and the number of bits in the DAI field is 1. For example, the second terminal device parses PDCCH 1 in a third manner. The third manner is that PDCCH 1 does not include the first indication information, the PDCCH 1 includes a DAI field, and the number of bits in the DAI field is 2.

[0181] Optionally, the first indication information may be carried in the reserved field. For example, PDCCH 1 is a PDCCH for scheduling Msg2. For example, the first terminal device parses PDCCH 1 in a first manner. The first manner is that PDCCH 1 includes the first indication information and does not include a reserved field. For example, the first terminal device parses PDCCH 1 in a second manner. The second manner is that PDCCH 1 includes the first indication information, PDCCH 1 includes a reserved field, and the number of bits in the reserved field is A1. For example, the second terminal device parses PDCCH 1 in a third manner. The third manner is that PDCCH 1 does not include the first indication information, PDCCH 1 includes a reserved field, and the number of bits in the reserved field is A2. A1 is an integer, A2 is an integer, and A1 is less than A2.

[0182] For example, the first terminal device is a first type terminal device, and the second terminal device is a second type terminal device, for example, the first terminal device is an R18 RedCap UE, and the second terminal device is an R17 RedCap UE.

[0183] For example, a network device may distinguish between RedCap UE types and eMBB UE types in Msg1, and between R17 RedCap UE types and R18 RedCap UE types in Msg3. In other words, RedCap UEs and eMBB UEs are assigned different Msg1 resources, but R17 RedCap UEs and R18 RedCap UEs are assigned the same Msg1 resources. R17 RedCap UEs and R18 RedCap UEs report their UE types in Msg3 for the network device to distinguish between them.

[0184] For example, the first indication information includes one bit.

[0185] For example, when the first indication information is in a first bit state, the first indication information instructs the first terminal device to manipulate downlink information. When the first indication information is in a second bit state, the first indication information instructs the first terminal device not to manipulate downlink information. For example, a bit state of "1" of the first information instructs the R18 RedCap UE to receive Msg4 PDSCH. For example, a bit state of "0" of the first information instructs the R18 RedCap UE not to receive Msg4 PDSCH.

[0186] For example, when the first indication information is in a first bit state, the first indication information instructs the first terminal device to manipulate downlink information. When the first information is in a second bit state, the first information instructs the second terminal device to manipulate downlink information. For example, a bit state of "1" of the first indication information instructs the R17 RedCap UE to manipulate downlink information, and a bit state of "0" of the first indication information instructs the R18 RedCap UE to manipulate downlink information. For example, a bit state of "1" of the first indication information instructs the R17 RedCap UE to transmit downlink information, and a bit state of "0" of the first indication information instructs the R18 RedCap UE to transmit downlink information.

[0187] For example, the network device does not distinguish between RedCap and eMBB UE types in Msg1. The network device distinguishes between eMBB, R17 RedCap, and R18 RedCap UE types in Msg3. In other words, RedCap UEs and eMBB UEs are allocated the same Msg1 resources. eMBB UEs, R17 RedCap UEs, and R18 RedCap UEs all report their UE type in Msg3 for the network device to distinguish between.

[0188] For example, the first indication information includes two bits.

[0189] For example, when the first indication information is in a first bit state, the first indication information instructs the first terminal device to manipulate downlink information. When the first indication information is in a second bit state, the first indication information instructs the second terminal device to manipulate downlink information. When the first indication information is in a third bit state, the first indication information instructs the third terminal device to manipulate downlink information. For example, a bit state "00" of the first indication information instructs an R17 RedCap UE to manipulate downlink information, a bit state "01" of the first indication information instructs an R18 RedCap UE to manipulate downlink information, and a bit state "10" of the first indication information instructs an eMBB UE to manipulate downlink information. For example, the third terminal device is an eMBB UE. For example, a bit state "00" of the first indication information indicates that downlink information is to be sent to an R17 RedCap UE, a bit state "01" of the first indication information indicates that downlink information is to be sent to an R18 RedCap UE, and a bit state "10" of the first indication information indicates that downlink information is to be sent to an eMBB UE.

[0190] For example, the network device distinguishes between R17 RedCap UE types and R18 RedCap UE types in Msg1, in other words, R17 RedCap UEs and R18 RedCap UEs are allocated different Msg1 resources.

[0191] For example, there is a correspondence between the bits included in the first indication information and one or more RARs, for example, each bit in the first indication information corresponds to one or more RARs of the preamble or indicates the UE type corresponding to one or more RARs.

[0192] For example, the first indication information includes at least one bit, and the first bit of the first indication information corresponds to the RAR of the preamble having an index of 0. When the first bit is in a first bit state, the first indication information instructs the first terminal device to manipulate the downlink information. When the first bit is in a second bit state, the first indication information instructs the first terminal device not to manipulate the downlink information.

[0193] In one possible implementation, terminal device 120 reports characteristic parameters or characteristics in message 3.

[0194] Optionally, the characteristic parameter may mean that the maximum bandwidth for transmitting unicast data of the terminal device is less than or equal to 5 MHz, or that the number of resource blocks used for transmitting unicast data of the terminal device is less than or equal to M, where M is a positive integer and has a corresponding relationship with the SCS.

[0195] Optionally, the characteristic parameter may mean that the maximum bandwidth for processing unicast data of the terminal device is less than or equal to 5 MHz, or that the number of resource blocks used to process unicast data of the terminal device is less than or equal to M, where M is a positive integer and has a corresponding relationship with the SCS. For example, if the SCS is 15 kHz, the value of M is 25. For example, if the SCS is 30 kHz, the value of M is 12.

[0196] It should be noted that the terminal device 120 may report characteristic parameters of the terminal device 120 to the network device 110 in message 3 .

[0197] In one possible implementation, if the terminal device 120 determines that the random access has failed, the method 300 may further include the following steps.

[0198] S350: The lower layer of the terminal device 120 sends second indication information, which indicates that the downlink information 1 cannot be processed or that the processing for the downlink information 1 has failed.

[0199] Specifically, in order to assist the upper layer of the terminal device 120 in adjusting the random access procedure or in initiating the random access again, after the terminal device 120 determines that the random access has failed, the lower layer (including the physical layer) of the terminal device 120 can send second indication information to the upper layer (e.g., the media access control (MAC) layer or the radio resource control (RRC) layer).

[0200] In one possible implementation, the method 300 may further include the following steps.

[0201] S360: The terminal device 120 stops the contention resolution timer (eg, ra-ContentionResolutionTimer).

[0202] Specifically, if the terminal device 120 determines that the random access has failed based on the downlink control information 1 in the PDCCH 1, the terminal device 120 may stop the contention resolution timer, thereby reducing power consumption.

[0203] Optionally, terminal device 120 may choose to discard PDCCH 1 instead.

[0204] Optionally, if the terminal device 120 determines that the random access has failed, the terminal device 120 may re-initiate a new random access.

[0205] It should be noted that in this embodiment of the present application, the order of S310 to S360 is not fixed and can be adjusted based on specific circumstances. In addition, some steps of S310 to S360 may be optional and not required, which is not limited here.

[0206] It should be noted that the terminal device 120 may report the type of the terminal device 120, i.e., whether the terminal device 120 is a first type of terminal device or a second type of terminal device, to the network device 110. In one example, the terminal device 120 may report the type of the terminal device 120 to the network device 110 in information 1.

[0207] In one possible implementation, the processing capability of the terminal device 120 is lower than the processing capability of the terminal device 130. When the network device 110 determines that the terminal device 130 is a terminal device that has successfully performed random access, the network device 110 can indicate information such as the number of resources 1 on PDSCH 1 and the time interval on PDCCH 1, thereby allowing the terminal device 120 to determine that the terminal device 120 is a terminal device that has not successfully performed random access. In this way, the delay when the terminal device 120 determines that the random access has failed can be reduced.

[0208] The communication method 300 is further described below.

[0209] In one possible implementation, the terminal device 120 receives first control information, the first control information including information about a first resource and information about a second resource, the first resource being used to carry the first information, the second resource being used to carry the second information, and the second information being used to respond to the first information. If the size of the first resource is larger than the processing capability of the terminal device 120 and / or if the time interval between the time domain resource of the first resource and the time domain resource of the second resource is smaller than the processing capability of the terminal device 120, the terminal device 120 considers the random access to have failed.

[0210] For example, the first control information is downlink control information or a physical downlink control channel (PDCCH). The first control information is DCI scrambled using the TC-RNTI. The first control information is a PDCCH in message 4. The first information is a PDSCH or data information carried on the PDSCH. The first information is a PDSCH in message 4. The second information is uplink control information, a PUCCH, or control information carried on the PUCCH. The second information is a HARQ-ACK used to feed back the PDSCH in message 4.

[0211] For the size of the first resource, please refer to the above description, and we will not repeat the details here.

[0212] In addition, the processing capability of the terminal device 120 is the bandwidth or channel bandwidth that can be supported by the terminal device 120, the maximum channel bandwidth supported or configured by the terminal device 120, or the number of resource units that can be processed by the terminal device 120 within a unit time. For example, the unit time is one or more time-domain resource units. The processing capability of the terminal device 120 may instead be a channel or data processing time series or processing speed. It should be understood that a higher processing capability of the terminal device 120 means a shorter required processing time, and a lower processing capability of the terminal device 120 means a longer required processing time. For example, the processing capability of the terminal device 120 is the time the terminal device 120 processes the PDSCH, or the sum of the time the terminal device 120 processes the PDSCH and the time the terminal device 120 feeds back the processing result by signaling.

[0213] For example, when the subcarrier spacing is 15 kHz, the maximum number of scheduled resources supported by the terminal device 120 is 25 RBs. If the number of RBs included in the first resource is greater than 25 RBs, the size of the first resource is considered to be greater than the processing capability of the terminal device 120. For example, when the subcarrier spacing is 30 kHz, the maximum number of scheduled resources supported by the terminal device 120 is 12 RBs. If the number of RBs included in the first resource is greater than 12 RBs, the size of the first resource is considered to be greater than the processing capability of the terminal device 120.

[0214] The shortest time for the terminal device 120 to process the PDSCH and feed back the processing result through the PUCCH is T1. The time interval between the scheduling of the PDSCH by the network device 110 and the feedback of the PUCCH by the network device 110 is T2. If T2 is less than T1, it is considered that the scheduling time series of the network device 110 is greater than the processing capability of the terminal device 120.

[0215] Optionally, if it determines that the contention resolution has failed, the terminal device 120 performs at least one of the following operations: the lower layer notifies the upper layer that it cannot process the PDSCH; the lower layer notifies the upper layer that processing on the PDSCH or MAC PDU has failed; the contention resolution timer is stopped; the TC-RNTI is discarded; and random access is restarted.

[0216] According to the above technical solution, the terminal device 120 does not need to receive the PDSCH or wait for the contention resolution timer to expire before determining that the random access contention has failed. To avoid the waste of power caused by further blind monitoring, the terminal device 120 can determine that the contention has failed after reading the PDCCH in message 4. In this way, the random access procedure can be restarted as soon as possible to shorten the random access delay.

[0217] In one possible implementation, the terminal device 120 receives notification from a lower layer that it cannot operate on the PDSCH, or that the PDSCH is not decoded successfully, or that the MAC PDU is not decoded successfully, and the terminal device performs at least one of the following operations: stopping the contention resolution timer, discarding the TEMPORARY_C-RNTI, and considering the current contention resolution to have failed.

[0218] For example, the procedure for a terminal device is as follows: if a PDSCH or MAC PDU is not successfully decoded, or if a notification received from a lower layer indicates that the PDSCH cannot be processed; ■ Stop the conflict resolution timer, ■ Destroy the TEMPORARY_C-RNTI, and ■ Consider the current conflict resolution to have failed.

[0219] In one possible implementation, the terminal device 120 receives second control information, where the second control information is used to schedule the first data information, and the second control information includes third information, where the third information instructs the terminal device 120 to receive the first data information or not to receive the first data information.

[0220] If the third information indicates to the terminal device 120 not to receive the first data information, the terminal device 120 may determine that the random access has failed.

[0221] Optionally, the second control information is downlink control information. For example, the second control information is DCI scrambled using TC-RNTI. The second control information is a PDCCH in message 4. For example, the second control information is DCI scrambled using RA-RNTI. The second control information is a PDCCH in message 2 or a PDCCH of RAR.

[0222] For example, the first data information is a PDSCH. The first data information is a PDSCH in message 4. The first data information is a PDSCH in message 2.

[0223] In one possible embodiment, the random access failure is a random contention resolution failure.

[0224] For example, the third information in the PDCCH in message 4 instructs the terminal device 120 not to receive the PDSCH in message 4, or indicates that the PDSCH in message 4 does not include a contention resolution message for the terminal device 120, or indicates that contention resolution for the terminal device 120 has failed.

[0225] For example, the third information is carried in a downlink assignment index (DAI) field. For example, the terminal device 120 parses the second control information, where the second control information includes the third information but does not include a DAI field. The terminal device 130 parses the second control information, where the second control information does not include the third information but does include a DAI field. For example, the terminal device 120 parses the second control information, where the second control information includes the third information, where the second control information includes a DAI field, and the number of bits in the DAI field is 1. The terminal device 130 parses the second control information, where the second control information does not include the third information, where the second control information includes a DAI field, and the number of bits in the DAI field is 2.

[0226] For example, the terminal device 120 is a first type terminal device, and the terminal device 130 is a second type terminal device. For example, the terminal device 120 is an R18 RedCap UE, and the terminal device 130 is an R17 RedCap UE.

[0227] For example, network device 110 distinguishes between RedCap UE types and eMBB UE types in message 1 and distinguishes between R17 RedCap UE types and R18 RedCap UE types in message 3. In other words, RedCap UEs and eMBB UEs are assigned different message 1 resources, but R17 RedCap UEs and R18 RedCap UEs are assigned the same message 1 resources. R17 RedCap UEs and R18 RedCap UEs report their UE types in message 3 for network device 110 to distinguish between them.

[0228] Optionally, the third information includes one bit. For example, when the third information is in a first bit state, the third information instructs the terminal device 120 to receive the first data information. When the third information is in a second bit state, the third information instructs the terminal device 130 to receive the first data information. For example, a bit state of "1" of the third information instructs the first data information to be transmitted to the R17 RedCap UE, and a bit state of "0" of the third information instructs the transmission to the R18 RedCap UE. For example, a bit state of "1" of the third information instructs the R17 RedCap UE to receive the first data information, and a bit state of "0" of the third information instructs the R18 RedCap UE to receive the first data information. As another example, when the third information is in a first bit state, the third information instructs the terminal device 120 to receive the first data information. When the third information is in the second bit state, the third information instructs the terminal device 120 not to receive the first data information. For example, a bit state of "1" of the third information instructs the R18 RedCap UE to receive the PDSCH in message 4. For example, a bit state of "0" of the third information instructs the R18 RedCap UE not to receive the PDSCH in message 4.

[0229] For example, network device 110 does not distinguish between RedCap and eMBB UE types in message 1. Network device 110 distinguishes between eMBB, R17 RedCap, and R18 RedCap UE types in message 3. In other words, RedCap UEs and eMBB UEs are assigned the same Msg1 resources. eMBB UEs, R17 RedCap UEs, and R18 RedCap UEs all report their UE type in message 3 for network device 110 to distinguish between.

[0230] For example, the third information includes two bits. For example, when the third information is in a first bit state, the third information instructs a second terminal device to receive the first data information. When the third information is in a second bit state, the third information instructs a third terminal device to receive the first data information. When the third information is in a third bit state, the third information instructs a fourth terminal device to receive the first data information. For example, a bit state "00" of the third information instructs that the first data information is to be transmitted to an R17 RedCap UE, a bit state "01" of the third information instructs that transmission is to be performed for an R18 RedCap UE, and a bit state "10" of the third information instructs that transmission is to be performed for an eMBB UE. For example, the bit state "00" of the third information indicates that the R17 RedCap UE receives the first data information, the bit state "01" of the third information indicates that the R18 RedCap UE receives the first data information, and the bit state "10" of the third information indicates that the eMBB UE receives the first data information. For example, the fourth terminal device is an eMBB UE.

[0231] In one embodiment, the random access failure is a failure to receive an RAR.

[0232] For example, the terminal device 120 does not receive an RAR in response to a preamble transmitted by the terminal device 120.

[0233] For example, the third information in the PDCCH in message 2 instructs the terminal device 120 not to receive the PDSCH in message 2, or indicates that the PDSCH in message 2 does not include the RAR of the terminal device 120, or indicates that the random access of the terminal device 120 has failed.

[0234] For example, the third information is carried in a reserved field. For example, the terminal device 120 parses the second control information, and the second control information includes the third information but does not include a reserved field. The terminal device 130 parses the second control information, and the second control information does not include the third information but does include a reserved field. For example, the terminal device 120 parses the second control information, and the second control information includes the third information, the second control information includes a reserved field, and the number of bits in the reserved field is A1. The terminal device 130 parses the second control information, and the second control information does not include the third information, the second control information includes a reserved field, and the number of bits in the reserved field is A2. A1 is an integer, A2 is an integer, and A1 is less than A2.

[0235] For example, the network device 110 distinguishes between R17 RedCap UE types and R18 RedCap UE types in Message 1. In other words, R17 RedCap UEs and R18 RedCap UEs are assigned different Message 1 resources.

[0236] For example, there is a correspondence between the bits included in the third information and one or more RARs, for example, each bit in the third information corresponds to one or more RARs of the preamble or indicates a UE type corresponding to one or more RARs.

[0237] For example, a bit state "1" of the third information indicates that the first data information is to be transmitted to the R17 RedCap UE, and a bit state "0" of the third information indicates that transmission is to be performed to the R18 RedCap UE. For example, a bit state "1" of the third information indicates that the R17 RedCap UE is to receive the first data information, and a bit state "0" of the third information indicates that the R18 RedCap UE is to receive the first data information.

[0238] In short, the terminal device 120 does not need to receive the PDSCH before determining that the random access contention has failed. To avoid wasting power by further receiving and processing the PDSCH, the terminal device 120 can determine that the contention has failed after reading the PDCCH in message 4. In this way, the random access procedure can be restarted as soon as possible to reduce the random access delay.

[0239] The above describes a method embodiment among the embodiments of the present application, and the following describes a corresponding apparatus embodiment.

[0240] To implement the functions in the methods provided in the present application, both the terminal and the network device may include hardware structures and / or software modules, and may implement the aforementioned functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether one of the aforementioned functions is implemented using a hardware structure, a software module, or a combination of a hardware structure and a software module depends on the specific application and design constraints of the technical solution.

[0241] 5 is a block diagram of a communication device 500 according to one embodiment of the present application. The communication device 500 includes a processor 510 and a communication interface 520. The processor 510 and the communication interface 520 may be connected to each other via a bus 530. The communication device 500 shown in FIG. 5 may be a network device 110 or a terminal device 120.

[0242] Optionally, the communication device 500 further comprises a memory 540 .

[0243] The memory 540 may include, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or portable read-only memory (compact disc read-only memory (CD-ROM). The memory 540 is configured to store associated instructions and data.

[0244] The processor 510 may be one or more central processing units (CPUs). If the processor 510 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0245] If the communication apparatus 500 is a terminal device 120, for example, the processor 510 is configured to perform the following operations: transmitting uplink information 1 on resource 1; after transmitting the uplink information 1, receiving a PDCCH 1 carrying downlink control information 1, where the PDCCH 1 is used to schedule the downlink information 1, and the uplink information 1 and the downlink information 1 are information in a random access procedure; decoding the PDCCH 1; and if the PDCCH 1 is successfully decoded, determining, based on the downlink control information 1, whether to operate the downlink information 1, or determining, based on the downlink control information 1, whether to continue the current random access procedure; or receiving the downlink information 1; and determining a start time of a PUCCH 1 fed back according to the downlink information 1, where a time interval between an end time of the downlink information 1 and a start time of transmitting the PUCCH 1 satisfies a minimum time interval.

[0246] The above content is only used as an example for explanation purposes. When it is a terminal device 120, the communication apparatus 500 is responsible for performing the methods or steps related to the terminal device 120 in the above method embodiments.

[0247] If the communication apparatus 500 is a network device 110, for example, the processor 510 is configured to perform the following operations: receive uplink information 1, where the uplink information 1 is information in a random access procedure; and transmit a PDCCH 1 carrying downlink control information 1, where the PDCCH 1 is used to schedule the downlink information 1 and the downlink information 1 is information in the random access procedure. The PDCCH 1 is used by the terminal device 120 to determine whether to operate on the downlink information 1, or the PDCCH 1 is used by the terminal device 120 to determine whether to continue the current random access procedure.

[0248] The above content is used as an example for explanation purposes only. When being a network device 110, the communication apparatus 500 is responsible for performing the methods or steps related to the network device 110 in the above method embodiments.

[0249] The above description is merely an example for explanation. For specific details, please refer to the details described in the above method embodiments. In addition, for the implementation of each operation in FIG. 5, please refer to the corresponding descriptions in the method embodiments shown in FIG. 3 and FIG. 4.

[0250] 6 is a block diagram of a communication device 600 according to an embodiment of the present application. The communication device 600 may be the network device 110 or the terminal device 120 of the aforementioned embodiments, or may be a chip or module within the network device 110 or the terminal device 120, and is configured to implement the method of the aforementioned embodiments. The communication device 600 includes a transceiver unit 610 and a processing unit 620. The transceiver unit 610 and the processing unit 620 will be described below using an example.

[0251] The transceiver unit 610 may include a transmitting unit and a receiving unit configured to perform the transmitting or receiving functions, respectively, in the above-described method embodiments. A processing unit may also be included and configured to perform functions other than transmitting or receiving.

[0252] If the communication apparatus 600 is a terminal device 120, for example, the transceiver unit 610 is configured to transmit uplink information 1 on resource 1, and receive PDCCH 1 carrying downlink control information 1 after transmitting the uplink information 1, where the PDCCH 1 is used to schedule the downlink information 1, and the uplink information 1 and the downlink information 1 are information in a random access procedure. The processing unit 620 is configured to decode the PDCCH 1, and if the PDCCH 1 is successfully decoded, determine based on the downlink control information 1 whether to operate the downlink information 1, or determine based on the downlink control information 1 whether to continue the current random access procedure, or determine a start time of PUCCH 1 fed back according to the downlink information 1, where the time interval between the end time of the downlink information 1 and the start time of transmitting PUCCH 1 satisfies a minimum time interval.

[0253] Optionally, the processing unit 620 is further configured to execute content related to steps such as processing and adjustment of the terminal device 120 .

[0254] Optionally, the communication device 600 further includes a storage unit 630. The storage unit 630 is configured to store programs or codes used to perform the methods described above.

[0255] The above content is only used as an example for explanation purposes. If it is a terminal device 120, the communication apparatus 600 is responsible for performing the methods or steps related to the terminal device 120 in the above method embodiments.

[0256] When the communication apparatus 600 is a network device 110, for example, the transceiver unit 610 is configured to receive uplink information 1, where the uplink information 1 is information in a random access procedure, and to transmit PDCCH 1 carrying downlink control information 1, where the PDCCH 1 is used to schedule the downlink information 1, where the downlink information 1 is information in a random access procedure. The PDCCH 1 is used by the terminal device 120 to determine whether to operate on the downlink information 1, or the PDCCH 1 is used by the terminal device 120 to determine whether to continue the current random access procedure.

[0257] Optionally, the communication apparatus 600 may further include a processing unit 620 configured to perform content related to steps such as processing and adjusting the network device 110 .

[0258] Optionally, the communication device 600 further includes a storage unit 630. The storage unit 630 is configured to store programs or codes used to perform the methods described above.

[0259] The foregoing is used as an example for illustrative purposes only. When the communication device 600 is the network device 110, the communication device 600 is responsible for performing the methods or steps associated with the network device 110 in the method embodiments described above.

[0260] In addition, for the implementation of each operation in Figure 6, please refer to the corresponding description of the method shown in the above embodiment, and the details will not be described again here.

[0261] The apparatus embodiments shown in Figures 5 and 6 are used to implement the contents described in the aforementioned method embodiments shown in Figures 3 and 4. Therefore, for specific implementation steps and methods of the apparatuses shown in Figures 5 and 6, please refer to the contents described in the aforementioned method embodiments.

[0262] It should be understood that the transceiver unit may include a transmitting unit and a receiving unit. The transmitting unit is configured to perform a transmitting operation of the communication device, and the receiving unit is configured to perform a receiving operation of the communication device. For ease of explanation, in this embodiment of the present application, the transmitting unit and the receiving unit are combined into one transceiver unit, which will be described here only once and will not be described in detail again below.

[0263] 7 is a block diagram of a communication device 700 according to one embodiment of the present application. The communication device 700 may be configured to implement the functions of the network device 110 or the terminal device 120 in the manner described above. The communication device 700 may be a chip in the network device 110 or the terminal device 120.

[0264] The communication device 700 includes an input / output interface 720 and a processor 710. The input / output interface 720 may be an input / output circuit. The processor 710 may be a signal processor, chip, or another integrated circuit capable of implementing the methods of the present application. The input / output interface 720 is configured to input or output signals or data.

[0265] For example, if the communications apparatus 700 is a terminal device 120, the input / output interface 720 is configured to transmit uplink information 1 on resource 1, and receive a PDCCH 1 carrying downlink control information 1 after transmitting the uplink information 1, where the PDCCH 1 is used to schedule the downlink information 1, and the uplink information 1 and the downlink information 1 are information in a random access procedure. The processor 710 may be configured to decode the PDCCH 1, and if the PDCCH 1 is successfully decoded, determine based on the downlink control information 1 whether to operate the downlink information 1, or determine based on the downlink control information 1 whether to continue the current random access procedure, or receive the downlink information 1, and determine a start time of a PUCCH 1 fed back according to the downlink information 1, where the time interval between the end time of the downlink information 1 and the start time of transmitting the PUCCH 1 satisfies a minimum time interval, and receive the information 1 from the network device 110. The processor 710 is further configured to perform some or all of the steps of any method provided in the present application.

[0266] For example, if the communications apparatus 700 is the network device 110, the input / output interface 720 is configured to receive uplink information 1, where the uplink information 1 is information in a random access procedure, and to transmit PDCCH 1 carrying downlink control information 1, where the PDCCH 1 is used to schedule the downlink information 1, where the downlink information 1 is information in the random access procedure. The PDCCH 1 is used by the terminal device 120 to determine whether to operate on the downlink information 1, or the PDCCH 1 is used by the terminal device 120 to determine whether to continue the current random access procedure. The processor 710 is further configured to perform some or all of the steps of any of the methods provided herein.

[0267] In one possible implementation, the processor 710 executes instructions stored in memory to perform functions performed by a network device or an end device.

[0268] Optionally, the communications device 700 further comprises a memory.

[0269] Optionally, the processor and memory are integrated together.

[0270] Optionally, the memory is external to the communication device 700 .

[0271] In one possible implementation, the processor 710 may be a logic circuit, and the processor 710 inputs / outputs messages or signaling through the input / output interface 720. The logic circuit may be a signal processor, a chip, or another integrated circuit capable of implementing the methods of the embodiments of the present application.

[0272] The above description of the device in Figure 7 is just an example for illustration purposes. The device may be configured to perform the method of the above embodiment. For specific content, please refer to the description of the above method embodiment. Details will not be described again here.

[0273] 8 is a block diagram of a communication device 800 according to one embodiment of the present application. The communication device 800 may be a network device 110 or a chip. The communication device 800 may be configured to perform the operations performed by the network device 110 in the method embodiments shown in FIGS. 5 to 11.

[0274] If the communication device 800 is a network device 110, such as a base station, FIG. 8 is a simplified diagram of the structure of the base station. The base station includes a portion 810, a portion 820, and a portion 830. The portion 810 is primarily configured to perform baseband processing and control the base station. The portion 810 is typically the control center of the base station and may be commonly referred to as a processor. The portion 810 is configured to control the base station to perform processing operations on the network device side in the above-described method embodiment. The portion 820 is primarily configured to store computer program code and data. The portion 830 is primarily configured to receive and transmit radio frequency signals and convert between radio frequency signals and baseband signals. The portion 830 may be commonly referred to as a transceiver module, transceiver machine, transceiver circuit, transceiver, etc. The transceiver module in the portion 1730 may be commonly referred to as a transceiver machine, transceiver, etc., and includes an antenna 833 and radio frequency circuitry (not shown in FIG. 8). The radio frequency circuitry is primarily configured to perform radio frequency processing. Optionally, in portion 830, a device configured to perform a receiving function may be considered a receiver, and a device configured to perform a transmitting function may be considered a transmitter. In other words, portion 830 includes a receiver 832 and a transmitter 831. A receiver may also be referred to as a receiving module, a receiver machine, a receiver circuit, etc., and a transmitter may also be referred to as a transmitting module, a transmitter machine, a transmitter circuit, etc.

[0275] Portion 810 and portion 820 may include one or more boards, each of which may include one or more processors and one or more memories. The processors are configured to read and execute programs in the memories to perform baseband processing functions and control the base station. When multiple boards are present, the boards may be interconnected to each other to increase processing power. In an optional implementation, multiple boards may share one or more processors, or multiple boards may share one or more memories, or multiple boards may simultaneously share one or more processors.

[0276] For example, in one implementation, the transceiver module in portion 830 is configured to perform the receive and transmit related processes performed by the network device in the embodiment shown in Figures 3 and 4. The processor in portion 810 is configured to perform the processing related processes performed by the network device in the embodiment shown in Figures 3 and 4.

[0277] In another implementation, the processor in portion 810 is configured to perform the processing-related processes performed by the communications device in the embodiments shown in FIGS.

[0278] In another implementation, the transceiver module in portion 830 is configured to perform the receive and transmit related processes performed by the communications device in the embodiments shown in FIGS.

[0279] It should be understood that Figure 8 is an example only and not a limitation, and a network device including a processor, memory, and transceiver need not rely on the structure shown in Figures 5 to 7.

[0280] When the communication device 800 is a chip, the chip includes a transceiver, a memory, and a processor. The transceiver may be an input / output circuit or a communication interface. The processor may be a processor, a microprocessor, or an integrated circuit integrated on a chip. A transmitting operation performed by the network device in the above-described method embodiments may be understood as an output of the chip, and a receiving operation performed by the network device in the above-described method embodiments may be understood as an input of the chip.

[0281] 9 is a block diagram of a communication device 900 according to an embodiment of the present application. The communication device 900 may be a terminal device 120 or a processor or chip within the terminal device 120. The communication device 900 may be configured to perform operations performed by the terminal device 120 or a communication device in the embodiments of the method described above.

[0282] When the communication apparatus 900 is a terminal device 120, FIG. 9 is a simplified structural diagram of the terminal device. As shown in FIG. 9, the terminal device includes a processor, a memory, and a transceiver. The memory can store computer program code. The transceiver includes a transmitter 931, a receiver 932, a radio frequency circuit (not shown in FIG. 9), an antenna 933, and an input / output device (not shown in FIG. 9).

[0283] The processor is primarily configured to process communication protocols and communication data, control the terminal device, execute software programs, process data of the software programs, etc. The memory is primarily configured to store software programs and data. The radio frequency circuit is primarily configured to perform conversion between baseband signals and radio frequency signals and process radio frequency signals. The antenna is primarily configured to receive and transmit radio frequency signals in the form of electromagnetic waves. The input / output device, such as a touch screen, display, or keyboard, is primarily configured to receive data entered by a user and output data to the user. It should be noted that some types of terminal devices may not have input / output devices.

[0284] When data needs to be transmitted, the processor performs baseband processing on the data to be transmitted and then outputs a baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal to the outside through an antenna in the form of electromagnetic waves. When data is transmitted to the terminal device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal to a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal to data and processes the data. For ease of explanation, FIG. 9 shows only one memory, one processor, and one transceiver. An actual terminal device product may have one or more processors and one or more memories. The memory may also be referred to as a storage medium, a storage device, or the like. The memory may be located independently of the processor or integrated with the processor. This is not a limitation of the embodiments of the present application.

[0285] In the embodiments of the present application, the antenna and the radio frequency circuit having the transceiver function may be regarded as a transceiver module of the terminal device, and the processor having the processing function may be regarded as a processing module of the terminal device.

[0286] 9, the terminal device includes a processor 910, a memory 920, and a transceiver 930. The processor 910 may also be referred to as a processing unit, a processing board, a processing module, a processing device, etc. The transceiver 930 may also be referred to as a transceiver unit, a transceiver machine, a transceiver device, etc.

[0287] Optionally, a device configured to perform a receiving function in the transceiver 930 may be considered a receiving module, and a device configured to perform a transmitting function in the transceiver 930 may be considered a transmitting module. In other words, the transceiver 930 includes a receiver and a transmitter. A transceiver may also be referred to as a transceiver machine, a transceiver module, a transceiver circuit, or the like. A receiver may also be referred to as a receiver machine, a receiving module, a receiver circuit, or the like. A transmitter may also be referred to as a transmitter machine, a transmitting module, a transmitter circuit, or the like.

[0288] For example, in one implementation, the processor 910 is configured to perform processing operations at the terminal device side in the embodiments shown in Figures 3 and 4, and the transceiver 930 is configured to perform receiving and transmitting operations at the terminal device side in Figures 3 and 4.

[0289] For example, in one implementation, the processor 910 is configured to perform processing operations at the terminal device side in the embodiments shown in Figures 3 and 4, and the transceiver 930 is configured to perform receiving and transmitting operations at the terminal device side in Figures 3 and 4.

[0290] It should be understood that Figure 9 is an example only and not a limitation, and the terminal device including the transceiver module and the processing module need not rely on the structures shown in Figures 5 to 7.

[0291] When the communication device 900 is a chip, the chip includes a processor, a memory, and a transceiver. The transceiver may be an input / output circuit or a communication interface. The processor may be a processing module, a microprocessor, or an integrated circuit integrated on the chip. A transmitting operation performed by a terminal device in the above-described method embodiments may be understood as an output of the chip, and a receiving operation performed by a terminal device in the above-described method embodiments may be understood as an input of the chip.

[0292] The present application further provides a chip including a processor configured to retrieve instructions from the memory and execute instructions stored in the memory, thereby enabling a communications device in which the chip is installed to perform the method of the aforementioned example.

[0293] The present application further provides another chip including an input interface, an output interface, and a processor. The input interface, the output interface, and the processor are connected through an internal connection path. The processor is configured to execute code in the memory, and when the code is executed, the processor is configured to perform the method of the above example. Optionally, the chip further includes a memory, and the memory is configured to store a computer program or code.

[0294] The present application further provides a processor configured to couple to the memory and configured to perform the methods and functions of the network device or terminal device in any one of the preceding embodiments.

[0295] Another embodiment of the present application provides a computer program product including instructions, which when executed on a computer, perform the methods of the aforementioned embodiments.

[0296] The present application further provides a computer program, which, when run on a computer, performs the methods of the above-described embodiments.

[0297] Another embodiment of the present application provides a computer-readable storage medium, which stores a computer program, which, when executed by a computer, performs the method of the aforementioned embodiment.

[0298] In the description of embodiments of the present application, unless otherwise specified, "plurality" means two or more. "At least one of the following items (moieties)" or similar expressions refers to any combination of these items, including any combination of a singular item (moiety) or multiple items (moieties). For example, at least one item (moiety) of a, b, or c may refer to a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c may be singular or plural.

[0299] In addition, in order to clearly describe the technical solutions of the embodiments of the present application, the embodiments of the present application use terms such as "first" and "second" to distinguish between the same or similar items that provide essentially the same function or purpose. Those skilled in the art can understand that terms such as "first" and "second" do not limit the number or execution order, and terms such as "first" and "second" are not necessarily limited to different items. In addition, the embodiments of the present application use terms such as "example" or "for example" to provide an example, illustration, or explanation.

[0300] Any embodiment or design style described in the embodiments of this application as an "example" or "for example" should not be described as being preferred or having more advantages than another embodiment or design style. Strictly speaking, the use of terms such as "example" or "for example" is intended to present the relevant concepts in a particular way to facilitate understanding.

[0301] In the description of the embodiments of the present application, unless otherwise specified, " / " represents an "or" relationship between related objects. For example, A / B can represent A or B. The term "and / or" in the present application is merely a relationship for describing related objects and represents that three relationships may exist. For example, A and / or B can represent the following three cases: when only A exists, when both A and B exist, and when only B exists, and A and B may each be singular or plural.

[0302] The sequence numbers of the above processes do not mean the execution order in the embodiments of the present application. The execution order of the processes should be determined based on the functions and internal logic of the processes, and should not be construed as any limitation on the implementation process of the embodiments of the present application.

[0303] Those skilled in the art can realize that, in combination with the examples described in the embodiments disclosed herein, the units and algorithm steps can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether a function is performed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can implement the described functions using various methods for each specific application, but this implementation should not be considered to exceed the scope of this application.

[0304] For ease of description, it is clearly understood by those skilled in the art that the detailed working processes of the aforementioned systems, devices and units should be referred to the corresponding processes in the method embodiments, and the details will not be described again here.

[0305] It should be understood that in some embodiments provided in the present application, the disclosed systems, devices, and methods may be implemented in other ways. For example, the described device embodiments are merely examples. For example, the division into units is merely a logical division of function, and actual implementation may involve other divisions. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implemented.

[0306] Additionally, the shown or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces. Indirect couplings or communication connections between devices or units may be implemented in electronic, mechanical, or other forms.

[0307] The units described as separate parts may or may not be physically separate, and the parts shown as units may or may not be physical units, in other words, they may be located in one place or distributed over multiple network units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions of the embodiments.

[0308] In addition, the functional units in the embodiments of the present application may be integrated into one processing unit, each of the units may exist physically alone, or two or more units may be integrated into one unit.

[0309] When functions are implemented in the form of software functional units and sold or used as independent products, the functions may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application may essentially be implemented in the form of a software product, or a portion of the technical solutions may be implemented in the form of a software product. The computer software product may be stored in a storage medium and include instructions that instruct a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the methods described in the embodiments of the present application. The storage medium may include any medium that can store program code, such as a USB flash drive, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0310] The above description is merely a specific implementation of the embodiments of the present application and is not intended to limit the scope of protection of the embodiments of the present application. Any modifications or replacements that can be easily conceived by those skilled in the art within the technical scope disclosed in the embodiments of the present application shall fall within the scope of protection of the embodiments of the present application. Therefore, the scope of protection of the embodiments of the present application shall be subject to the scope of protection of the claims. [Explanation of symbols]

[0311] 100 Application Scenarios 110 Network Devices 120 Terminal Devices 130 Terminal Devices 200 Random Access Procedure 300 Communication Methods 500 Communication Equipment 510 processor 520 Communication Interface 530 Bus 540 memory 600 Communication Equipment 610 Transceiver Unit 620 Processing Unit 630 Storage Unit 700 Communication Equipment 710 processor 720 Input / Output Interface 800 Communication Equipment 810 parts 820 parts 830 parts 831 Transmitter 832 receiver 833 Antenna 900 Communication Equipment 910 processor 920 memory 930 Transceiver 931 Transmitter 932 receiver 933 Antenna 1730 parts

Claims

1. transmitting, by the terminal device, uplink information on a first resource; receiving, by the terminal device, a physical downlink control channel (PDCCH) carrying downlink control information after transmitting the uplink information, wherein the PDCCH is used to schedule downlink information, and the uplink information and the downlink information are information in a random access procedure; decoding, by the terminal device, the PDCCH; If the terminal device successfully decodes the PDCCH, determining, by the terminal device, whether to manipulate the downlink information based on the downlink control information; or determining, by the terminal device, whether to continue the current random access procedure based on the downlink control information; or receiving, by the terminal device, the downlink information; determining, by the terminal device, a start time for feeding back a physical uplink control channel (PUCCH) according to the downlink information, wherein a time interval between an end time of the downlink information and the start time for transmitting the PUCCH satisfies a minimum time interval; A communication method, including:

2. The uplink information is a physical uplink shared channel (PUSCH) in a message A, and the downlink information is a random access response in a message B; or The uplink information is message 3, and the downlink information is message 4 or contention resolution information. The method of claim 1.

3. the downlink control information includes a frequency domain resource allocation (FDRA) field, the FDRA field being used to allocate resource blocks for transmission of the downlink information; If the number of allocated resource blocks exceeds a first threshold, the terminal device does not manipulate the downlink information; or If the number of allocated resource blocks exceeds a first threshold, the terminal device does not manipulate the downlink information, and the first terminal device determines that the current random access has failed; or If the number of allocated resource blocks exceeds a first threshold, the terminal device does not continue with the current random access procedure; or If the number of allocated resource blocks exceeds a first threshold, the terminal device does not continue the current random access procedure, and the first terminal device determines that the current random access has failed; or If the number of allocated resource blocks exceeds a first threshold, the terminal device manipulates the downlink information, and the terminal device determines that the minimum time interval is equal to the sum of a first time interval and a first value, and the first value is greater than 0; 3. The method according to claim 1 or 2.

4. the downlink control information includes an FDRA field, the FDRA field being used to allocate resource blocks for transmission of the downlink information; If the number of allocated resource blocks does not exceed a first threshold, the terminal device manipulates the downlink information; or If the number of allocated resource blocks does not exceed a first threshold, the terminal device continues the current random access procedure; or If the number of allocated resource blocks does not exceed a first threshold, the terminal device determines that the minimum time interval is equal to a first time interval. The method of claim 1.

5. the downlink control information includes time indication information, and the time indication information is used to determine a time unit for transmitting the PUCCH; If the time interval between the end time of the downlink information and the start time of transmitting the PUCCH is less than a second threshold, the terminal device does not manipulate the downlink information; or If the time interval between the end time of the downlink information and the start time of transmitting the PUCCH is less than a second threshold, the terminal device does not manipulate the downlink information, and the terminal device determines that the current random access has failed; or If the time interval between the end time of the downlink information and the start time of transmitting the PUCCH is less than a second threshold, the terminal device does not continue the current random access procedure; or If the time interval between the end time of the downlink information and the start time of transmitting the PUCCH is less than a second threshold, the terminal device does not continue the current random access procedure, and the terminal device determines that the current random access has failed. The method of claim 1.

6. the downlink control information includes time indication information, and the time indication information is used to determine a time unit for transmitting the PUCCH; If the time interval between the end time of the downlink information and the start time of transmitting the PUCCH is equal to or greater than a second threshold, the terminal device determines to manipulate the downlink information; or If the time interval between the end time of the downlink information and the start time of transmitting the PUCCH is equal to or greater than a second threshold, the terminal device determines to continue the current random access procedure. The method of claim 1.

7. The downlink control information includes first instruction information, and the first instruction information instructs a terminal device having a first characteristic parameter to manipulate the downlink information; The method of claim 1.

8. If the characteristic parameter of the terminal device is not the first characteristic parameter, the terminal device does not manipulate the downlink information; or If the characteristic parameter of the terminal device is not the first characteristic parameter, the terminal device does not operate the downlink information, and the terminal device determines that the current random access has failed; or If the characteristic parameter of the terminal device is not the first characteristic parameter, the terminal device does not continue with the current random access procedure; or If the characteristic parameter of the terminal device is not the first characteristic parameter, the terminal device does not continue the current random access procedure, and the terminal device determines that the current random access has failed; or When the characteristic parameter of the terminal device is the first characteristic parameter, the terminal device operates the downlink information. The method of claim 7.

9. the terminal device reports characteristic parameters in message 3; and / or the maximum bandwidth for transmitting unicast data of the terminal device is not more than 5 MHz, or the number of resource blocks used to transmit unicast data of the terminal device is not more than M; and / or The maximum bandwidth for processing the unicast data of the terminal device is not more than 5 MHz, or the number of resource blocks used to process the unicast data of the terminal device is not more than M; M is a positive integer, or there is a correspondence between the value of M and the subcarrier spacing. The method of claim 1.

10. receiving, by a network device, uplink information, the uplink information being information in a random access procedure; transmitting, by the network device, a physical downlink control channel (PDCCH) carrying downlink control information, the PDCCH being used to schedule downlink information, the downlink information being information in the random access procedure; The PDCCH is used by the first terminal device to determine whether to manipulate the downlink information, or the PDCCH is used by the first terminal device to determine whether to continue the current random access procedure; Communication method.

11. The uplink information is a physical uplink shared channel (PUSCH) in message A, and the downlink information is a random access response in information B; or The uplink information is message 3, and the downlink information is message 4 or contention resolution information. The method of claim 10.

12. The downlink control information includes first instruction information, and the first instruction information instructs a terminal device having a first characteristic parameter to manipulate the downlink information; The method of claim 11.

13. 1. A communication device comprising a processor, the processor being configured to: enabling the communication device to carry out the method according to any one of claims 1 to 9; or enabling the communication device to carry out the method according to any one of claims 10 to 12, A communication device configured to:

14. The communication device of claim 13 , further comprising a memory, the memory configured to store the computer program or the instructions.

15. 15. The communication device according to claim 13 or 14, further comprising a communication interface, the communication interface being configured to input and / or output signals.

16. 1. A communication device comprising a logic circuit and an input / output interface, the input / output interface configured to input and / or output signals; The logic circuit is configured to perform the method of any one of claims 1 to 9; or The logic circuit is configured to perform the method of any one of claims 10 to 12. Communication equipment.

17. A computer-readable storage medium, the computer-readable storage medium storing a computer program or instructions, the computer program or instructions being executable by a computer to: The method according to any one of claims 1 to 9 is carried out; or The method according to any one of claims 10 to 12 is carried out A computer-readable storage medium.

18. A computer program product comprising instructions that, when executed on a computer, The method according to any one of claims 1 to 9 is carried out; or The method according to any one of claims 10 to 12 is carried out Computer program products.

19. A communication system comprising a first terminal device and a network device, The first terminal device is configured to perform the method according to any one of claims 1 to 9, The network device is configured to perform the method of any one of claims 10 to 12. Communication system.

Images