Communication method and communication apparatus
Patent Information
- Application Number
- MYPI2025005143
- Authority / Receiving Office
- MY · MY
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-03-02
- Filing Date
- 2024-02-28
- Publication Date
- 2024-09-02
AI Technical Summary
In the existing technology, a terminal device that fails in random access prolongs the time when determining that random access fails, resulting in the inability to start a new random access process in time and increasing power consumption and delay.
After the terminal equipment receives the PDCCH carrying downlink control information, it determines whether to continue the random access process or determines the random access failure based on the downlink control information, avoiding waiting for the contention resolution timer to expire, thereby shortening the delay of random access failure. and power consumption.
This effectively shortens the time for the terminal device to determine the random access failure, saves power consumption, and allows the terminal device to start a new random access process as soon as possible.
Smart Images

Figure PI2025005143_DRAWING_001 
Figure PI2025005143_DRAWING_002 
Figure PI2025005143_DRAWING_003
Abstract
Description
Communication method and communication device
[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on March 2, 2023, with application number 202310237163.0 and application name “Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Art
[0003] The network device configures multiple random access resources for the terminal device, allowing the terminal device to select a random access resource from the multiple random access resources for random access. If 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 the physical downlink shared channel (PDSCH), which carries information about the terminal device that successfully accessed the random access.
[0004] The terminal device that successfully accesses the random access can determine the success of the random access through the information carried by the PDSCH, and the terminal device that fails the random access can also determine the failure of the random access through the information carried by the PDSCH. However, the above process requires the terminal device that fails the random access to take longer to determine the failure of the random access.
[0005] Therefore, how to reduce the delay for a terminal device that fails random access to determine the failure of random access is a technical problem that needs to be solved urgently.
[0006] Summary of the Invention
[0007] The present application provides a communication method and a communication device, which can reduce the delay for a terminal device that fails random access to determine the failure of random access.
[0008] In a first aspect, a communication method is provided, which includes: a terminal device sends uplink information within a first resource; after sending the uplink information, the terminal device receives a PDCCH carrying downlink control information, the PDCCH is used to schedule downlink information, and the uplink information and the downlink information are information in a random access process; the terminal device decodes the PDCCH; if the terminal device successfully decodes the PDCCH, the terminal device determines whether to operate the downlink information according to the downlink control information; or, the terminal device determines whether to continue the current random access process according to the downlink control information; or, the terminal device receives the downlink information, and the terminal device determines the starting time of a physical uplink control channel that responds to the downlink information, and the end time of the downlink information and the starting time of the sending of the physical uplink control channel meet a minimum time interval.
[0009] Specifically, the terminal device can determine whether to continue processing downlink information based on the downlink control information in the PDCCH. When the terminal device determines based on the downlink control information that it does not need to continue processing the downlink information, the terminal device can determine that the terminal device's random access has failed, without having to wait for the contention resolution timer to expire before determining that the random access contention has failed. This can shorten the delay in the terminal device determining the failure of random access, allowing the terminal device to initiate a new random access as soon as possible, shortening the random access delay and saving power consumption of the terminal device.
[0010] In a possible implementation, the uplink information is the physical uplink shared channel in message A, and the downlink information is the random access response in message B; or, the uplink information is message 3, and the downlink information is message 4 or contention resolution information.
[0011] 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 process initiated by the terminal device has failed based on the downlink control information. In this way, the delay for the terminal device to determine that the random access process has failed can be shortened. 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 without having to wait for the contention resolution timer to expire before determining that the random access contention has failed. In this way, the delay for the terminal device to determine that the random access contention has failed can be shortened.
[0012] In one possible implementation, the downlink control information includes a frequency domain resource allocation FDRA field, which is used to allocate resource blocks for the downlink information transmission; 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 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 process; or, if the number of allocated resource blocks exceeds the first threshold, the terminal device does not continue the current random access process, and the first terminal device determines that the 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, and the first value is greater than 0.
[0013] In this way, the terminal device can determine whether random access has failed based on the number of resource blocks indicated in the downlink control information, without having to wait for the contention resolution timer to expire before determining that random access contention has failed. This can further shorten the delay for the terminal device to determine random access failure, saving power consumption of the terminal device.
[0014] In one possible implementation, the downlink control information includes an FDRA field, which is used to allocate resource blocks for the downlink information transmission; the number of allocated resource blocks does not exceed a first threshold, and the terminal device operates the downlink information; or, the number of allocated resource blocks does not exceed the first threshold, and the terminal device continues the current random access process; or, the number of allocated resource blocks does not exceed the first threshold, and the terminal device determines that the minimum time interval is equal to the first time interval.
[0015] In one possible implementation, the downlink control information includes time indication information, which is used to determine the time unit for sending the physical uplink control channel; the time interval between the end moment of the downlink information and the start moment of sending the physical uplink control channel is less than a second threshold, and the terminal device does not operate the downlink information; or, the time interval between the end moment of the downlink information and the start moment of sending the physical uplink control channel is less than the second threshold, the terminal device does not operate the downlink information, and the terminal device determines that this random access has failed; or, the time interval between the end moment of the downlink information and the start moment of sending the physical uplink control channel is less than the second threshold, and the terminal device does not continue the current random access process; or, the time interval between the end moment of the downlink information and the start moment of sending the physical uplink control channel is less than the second threshold, the terminal device does not continue the current random access process, and the terminal device determines that this random access has failed.
[0016] In this way, the terminal device can determine whether random access has failed based on the time interval between the end time of the downlink information indicated in the downlink control information and the start time of the physical uplink control channel transmission, without having to wait for the contention resolution timer to expire before determining that the random access contention has failed. This can further shorten the delay in the terminal device determining random access failure and save power consumption of the terminal device.
[0017] In one possible implementation, the downlink control information includes time indication information, which is used to determine the time unit for sending the physical uplink control channel; the time interval between the end moment of the downlink information and the start moment of sending the physical uplink control channel is not less than a second threshold, and the terminal device determines to operate the downlink information; or, the time interval between the end moment of the downlink information and the start moment of sending the physical uplink control channel is not less than the second threshold, and the terminal device determines to continue the current random access process.
[0018] In a possible implementation, the downlink control information includes first indication information, and the first indication information is used to instruct a terminal device having a first characteristic parameter to operate the downlink information.
[0019] 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. This can shorten the delay for the terminal device to determine that the random access has failed, saving power consumption of the terminal device.
[0020] In one possible implementation, the characteristic parameter of the terminal device is not the first characteristic parameter, and the terminal device does not operate the downlink information; or, the characteristic parameter of the terminal device is not the first characteristic parameter, and the terminal device does not operate the downlink information, and the terminal device determines that the random access has failed; or, the characteristic parameter of the terminal device is not the first characteristic parameter, and the terminal device does not continue the current random access process; or, the characteristic parameter of the terminal device is not the first characteristic parameter, and the terminal device does not continue the current random access process, and the terminal device determines that the random access has failed; or, the characteristic parameter of the terminal device is the first characteristic parameter, and the terminal device operates the downlink information.
[0021] In one possible implementation, the terminal device reports characteristic parameters through message 3; and / or the maximum bandwidth of unicast data transmission of the terminal device is not greater than 5 MHz, or the number of resource blocks used for unicast data transmission of the terminal device is not greater than M; and / or the maximum bandwidth of unicast data processing of the terminal device is not greater than 5 MHz, or the number of resource blocks used for unicast data processing of the terminal device is not greater than M; M is a positive integer, or the value of M corresponds to the subcarrier spacing.
[0022] In a second aspect, a communication method is provided, which includes: a network device receives uplink information, which is information in a random access process; the network device sends a PDCCH carrying downlink control information, which is used to schedule downlink information, which is information in a random access process; wherein, the PDCCH is used by a first terminal device to determine whether it is necessary to operate the downlink information, or the PDCCH is used by the first terminal device to determine whether to continue the current random access process.
[0023] In a possible implementation, the uplink information is the physical uplink shared channel in message A, and the downlink information is the random access response in message B; or, the uplink information is message 3, and the downlink information is message 4 or contention resolution information.
[0024] In a possible implementation, the downlink control information includes first indication information, and the first indication information is used to instruct a terminal device having a first characteristic parameter to operate the downlink information.
[0025] According to a third aspect, a communication method is provided, including: a first terminal device sends first information on a first resource, the first information being used for a random access process; the first terminal device receives a physical downlink control channel PDCCH, the PDCCH being used to carry a response to the first information; and the first terminal device determines that random access fails based on the PDCCH.
[0026] In a possible implementation, the PDCCH includes first indication information, and the first indication information is used to indicate random access failure. The first terminal device determines the random access failure according to the PDCCH, including: the first terminal device determines the random access failure according to the first indication information.
[0027] In one possible implementation, the PDCCH includes second indication information, and the second indication information is used to indicate the number of resources of the first physical downlink shared channel PDSCH. The first terminal device determines the random access failure based on the PDCCH, including: the first terminal device determines the random access failure based on the number of resources of the first PDSCH.
[0028] In one possible implementation, the PDCCH includes third indication information and fourth indication information, the third indication information is used to indicate the time domain resources of the second PDSCH, and the fourth indication information is used to indicate the time domain resources of the physical uplink control channel PUCCH that feeds back the second PDSCH. The first terminal device determines the random access failure based on the PDCCH, including: the first terminal device determines the random access failure based on the time interval between the time domain resources of the second PDSCH and the time domain resources of the PUCCH.
[0029] In one possible implementation, the PDCCH includes fifth indication information, which is used to indicate resource information of the third PDSCH; the third PDSCH includes sixth indication information, which is used to indicate resource information of the physical uplink shared channel PUSCH; the first terminal device determines the random access failure based on the PDCCH, including: the first terminal device determines the random access failure based on 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.
[0030] In one possible implementation, the method further includes: the lower layer of the first terminal device sends seventh indication information, and the seventh indication information is used to indicate that the first terminal device cannot process PDSCH, or the seventh indication information is used to indicate that the first terminal device fails to process PDSCH.
[0031] In a possible implementation, the method further includes: the first terminal device stopping a contention resolution timer.
[0032] In one possible implementation, the first information is used to indicate the type of the first terminal device; wherein, the first resource is also used for the second terminal device to send second information, the second information is used for a random access process, and the processing capability of the first terminal device is lower than that of the second terminal device.
[0033] In a fourth aspect, a communication method is provided, including: a network device receives first information on a first resource, the first information is used for a random access process; the network device sends a physical downlink control channel PDCCH, the PDCCH is used to carry a response to the first information, and the PDCCH is used by a first terminal device to determine that random access has failed.
[0034] In a possible implementation manner, the PDCCH includes first indication information, where the first indication information is used to indicate a random access failure.
[0035] In a possible implementation, the PDCCH includes second indication information, where the second indication information is used to indicate the number of resources of the 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 random access has failed.
[0036] In one possible implementation, the PDCCH includes third indication information and fourth indication information, the third indication information is used to indicate the time domain resources of the second PDSCH, and the fourth indication information is used to indicate the time domain resources of the physical uplink control channel PUCCH that feeds back the second PDSCH, and the time interval between the time domain resources of the second PDSCH and the time domain resources of the PUCCH is used by the first terminal device to determine that random access has failed.
[0037] In one possible implementation, the PDCCH includes fifth indication information, which is used to indicate resource information of the third PDSCH; the third PDSCH includes sixth indication information, which is used to indicate resource information of the physical uplink shared channel PUSCH; 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 random access has failed.
[0038] In one possible implementation, the first information is used to indicate the type of the first terminal device; wherein, the first resource is also used by the second terminal device to send second information to the network device, and the second information is used for a random access process, wherein the processing capability of the first terminal device is lower than the processing capability of the second terminal device.
[0039] In a fifth aspect, a communication device is provided, which can be used in the terminal device of the first aspect. The communication device can be a terminal device, or a device in the terminal device (for example, a chip, or a chip system, or a circuit), or a device that can be used in combination with the terminal device.
[0040] In one possible implementation, the communication device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the first aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuit and software.
[0041] In one possible implementation, the communication device includes: a transceiver unit, used to send uplink information within a first resource; the transceiver unit is also used to receive a PDCCH carrying downlink control information after sending the uplink information, the PDCCH is used to schedule downlink information, and the uplink information and the downlink information are information in a random access process; a processing unit, used to decode the PDCCH; if the PDCCH is successfully decoded, the processing unit is also used to determine whether to operate the downlink information based on the downlink control information; or, the processing unit is also used to determine whether to continue the current random access process based on the downlink control information; or, the transceiver unit is also used to receive the downlink information, and the processing unit is also used to determine the starting time of the physical uplink control channel for the downlink information response feedback, and the end time of the downlink information and the start time of the PUCCH transmission meet the minimum time interval.
[0042] In a possible implementation, the uplink information is the physical uplink shared channel in message A, and the downlink information is the random access response in message B; or, the uplink information is message 3, and the downlink information is message 4 or contention resolution information.
[0043] In one possible implementation, the downlink control information includes a frequency domain resource allocation FDRA field, which is used to allocate resource blocks for the downlink information transmission; if the number of allocated resource blocks exceeds a first threshold, the processing unit is further used 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 used to determine not to operate the downlink information, and the processing unit is further used to determine that this random access has failed; or, if the number of allocated resource blocks exceeds the first threshold, the processing unit is further used to determine not to continue the current random access process; or, if the number of allocated resource blocks exceeds the first threshold, the processing unit is further used to determine not to continue the current random access process, and the processing unit is further used to determine that this random access has failed; or, if the number of allocated resource blocks exceeds the first threshold, the processing unit is further used to determine to operate the downlink information, and the processing unit is further used to determine that the minimum time interval is equal to the sum of the first time interval and a first value, and the first value is greater than 0.
[0044] In one possible implementation, the downlink control information includes an FDRA field, which is used to allocate resource blocks for the downlink information transmission; the number of allocated resource blocks does not exceed a first threshold, and the processing unit is further used to determine the operation of the downlink information; or, the number of allocated resource blocks does not exceed the first threshold, and the processing unit is further used to determine to continue the current random access process; or, the number of allocated resource blocks does not exceed the first threshold, and the processing unit is further used to determine that the minimum time interval is equal to the first time interval.
[0045] In one possible implementation, the downlink control information includes time indication information, which is used to determine the time unit for sending the physical uplink control channel; the time interval between the end moment of the downlink information and the start moment of sending the physical uplink control channel is less than a second threshold, and the processing unit is further used to determine not to operate the downlink information; or, the time interval between the end moment of the downlink information and the start moment of sending the physical uplink control channel is less than the second threshold, and the processing unit is further used to determine not to operate the downlink information, and the processing unit is further used to determine that this random access has failed; or, the time interval between the end moment of the downlink information and the start moment of sending the physical uplink control channel is less than the second threshold, and the processing unit is further used to determine not to continue the current random access process; or, the time interval between the end moment of the downlink information and the start moment of sending the physical uplink control channel is less than the second threshold, and the processing unit is further used to determine not to continue the current random access process, and the processing unit is further used to determine that this random access has failed.
[0046] In one possible implementation, the downlink control information includes time indication information, which is used to determine the time unit for sending the physical uplink control channel; the time interval between the end time of the downlink information and the start time of sending the physical uplink control channel is not less than a second threshold, and the processing unit is also used to determine to operate the downlink information; or, the time interval between the end time of the downlink information and the start time of sending the physical uplink control channel is not less than the second threshold, and the processing unit is also used to determine to continue the current random access process.
[0047] In a possible implementation, the downlink control information includes first indication information, and the first indication information is used to instruct a terminal device having a first characteristic parameter to operate the downlink information.
[0048] In one possible implementation, the characteristic parameter of the communication device is not the first characteristic parameter, and the processing unit is further used to determine not to operate the downlink information; or, the characteristic parameter of the communication device is not the first characteristic parameter, and the processing unit is further used to determine not to operate the downlink information, and the processing unit is further used to determine that this random access has failed; or, the characteristic parameter of the communication device is not the first characteristic parameter, and the processing unit is further used to determine not to continue the current random access process; or, the characteristic parameter of the communication device is not the first characteristic parameter, and the processing unit is further used to determine not to continue the current random access process, and the processing unit is further used to determine that this random access has failed; or, the characteristic parameter of the communication device is the first characteristic parameter, and the processing unit is further used to determine to operate the downlink information.
[0049] In one possible implementation, the transceiver unit is further used to report characteristic parameters through message 3; and / or the maximum bandwidth of unicast data transmission of the communication device is not greater than 5 MHz, or the number of resource blocks used for unicast data transmission of the communication device is not greater than M; and / or the maximum bandwidth of unicast data processing of the communication device is not greater than 5 MHz, or the number of resource blocks used for unicast data processing of the communication device is not greater than M; M is a positive integer, or the value of M corresponds to the subcarrier spacing.
[0050] In the sixth aspect, a communication device is provided, which can be used in the network device of the second aspect. The communication device can be a network device, or a device in the network device (for example, a chip, or a chip system, or a circuit), or a device that can be used in combination with the network device.
[0051] In one possible implementation, the communication device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the second aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuit and software.
[0052] In one possible implementation, the communication device includes: a transceiver unit for receiving uplink information, which is information in a random access process; the transceiver unit is also used to send a PDCCH carrying downlink control information, which is used to schedule downlink information, which is information in a random access process; wherein, the PDCCH is used by the first terminal device to determine whether it is necessary to operate the downlink information, or the PDCCH is used by the first terminal device to determine whether to continue the current random access process.
[0053] In a possible implementation, the uplink information is the physical uplink shared channel in message A, and the downlink information is the random access response in message B; or, the uplink information is message 3, and the downlink information is message 4 or contention resolution information.
[0054] In a possible implementation, the downlink control information includes first indication information, and the first indication information is used to instruct a terminal device having a first characteristic parameter to operate the downlink information.
[0055] In the seventh aspect, a communication device is provided, which can be used in the terminal device of the third aspect. The communication device can be a terminal device, or a device in the terminal device (for example, a chip, or a chip system, or a circuit), or a device that can be used in combination with the terminal device.
[0056] In one possible implementation, the communication device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the third aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuit and software.
[0057] In one possible implementation, the communication device includes: a transceiver unit, used to send first information on a first resource, the first information being used for a random access process; the transceiver unit, further used to receive a PDCCH, the PDCCH being used to carry a response to the first information; and a processing unit, used to determine a random access failure based on the PDCCH.
[0058] In a possible implementation manner, the PDCCH includes first indication information, where the first indication information is used to indicate a random access failure. The processing unit is further configured to determine the random access failure according to the first indication information.
[0059] In a possible implementation, the PDCCH includes second indication information, where the second indication information is used to indicate the number of resources of the first PDSCH. The processing unit is further used to determine random access failure according to the number of resources of the first PDSCH.
[0060] In one possible implementation, the PDCCH includes third indication information and fourth indication information, the third indication information is used to indicate the time domain resources of the second PDSCH, and the fourth indication information is used to indicate the time domain resources of the PUCCH that feeds back the second PDSCH. The processing unit is also used to determine the random access failure based on the time interval between the time domain resources of the second PDSCH and the time domain resources of the PUCCH.
[0061] In one possible implementation, the PDCCH includes fifth indication information, which is used to indicate resource information of the third PDSCH; the third PDSCH includes sixth indication information, which is used to indicate resource information of the physical uplink shared channel PUSCH; the processing unit is also used to determine random access failure based on 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.
[0062] In a possible implementation, the transceiver unit is further configured to send seventh indication information, where the seventh indication information is used to indicate that the communication apparatus cannot process the PDSCH, or the seventh indication information is used to indicate that the communication apparatus fails to process the PDSCH.
[0063] In a possible implementation, the processing unit is further configured to stop a contention resolution timer.
[0064] In one possible implementation, the first information is used to indicate the type of the communication device; wherein, the first resource is also used for the second terminal device to send second information, the second information is used for a random access process, and the processing capability of the communication device is lower than the processing capability of the second terminal device.
[0065] In an eighth aspect, a communication device is provided, which can be used in the network device of the fourth aspect. The communication device can be a network device, or a device in the network device (for example, a chip, or a chip system, or a circuit), or a device that can be used in conjunction with the network device.
[0066] In one possible implementation, the communication device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the fourth aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuit and software.
[0067] In one possible implementation, the communication device includes: a transceiver unit, used to receive first information on a first resource, the first information is used for a random access process; the transceiver unit is also used to send a PDCCH, the PDCCH is used to carry a response to the first information, and the PDCCH is used by the first terminal device to determine that the random access has failed.
[0068] In a possible implementation manner, the PDCCH includes first indication information, where the first indication information is used to indicate a random access failure.
[0069] In a possible implementation, the PDCCH includes second indication information, where the second indication information is used to indicate the number of resources of the 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 random access has failed.
[0070] In one possible implementation, the PDCCH includes third indication information and fourth indication information, the third indication information is used to indicate the time domain resources of the second PDSCH, and the fourth indication information is used to indicate the time domain resources of the physical uplink control channel PUCCH that feeds back the second PDSCH, and the time interval between the time domain resources of the second PDSCH and the time domain resources of the PUCCH is used by the first terminal device to determine that random access has failed.
[0071] In one possible implementation, the PDCCH includes fifth indication information, which is used to indicate resource information of the third PDSCH; the third PDSCH includes sixth indication information, which is used to indicate resource information of the physical uplink shared channel PUSCH; 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 random access has failed.
[0072] In one possible implementation, the first information is used to indicate the type of the first terminal device; wherein, the first resource is also used by the second terminal device to send second information to the network device, and the second information is used for a random access process, wherein the processing capability of the first terminal device is lower than the processing capability of the second terminal device.
[0073] In the ninth aspect, a communication device is provided, comprising a processor, wherein the processor is used to, by executing a computer program or instruction, or by a logic circuit, enable the communication device to perform the method described in the first aspect and any possible embodiment of the first aspect; or enable the communication device to perform the method described in the second aspect and any possible embodiment of the second aspect; or enable the communication device to perform the method described in the third aspect and any possible embodiment of the third aspect; or enable the communication device to perform the method described in the fourth aspect and any possible embodiment of the fourth aspect.
[0074] In a possible implementation, the communication device further includes a memory for storing the computer program or instruction.
[0075] In a possible implementation, the communication device further includes a communication interface, which is used to input and / or output signals.
[0076] In the tenth aspect, a communication device is provided, comprising a logic circuit and an input / output interface, the input / output interface being used to input and / or output signals, the logic circuit being used to execute the method described in the first aspect and any possible embodiment of the first aspect; or the logic circuit being used to execute the method described in the second aspect and any possible embodiment of the second aspect; or the logic circuit being used to execute the method described in the third aspect and any possible embodiment of the third aspect; or the logic circuit being used to execute the method described in the fourth aspect and any possible embodiment of the fourth aspect.
[0077] In the eleventh aspect, a computer-readable storage medium is provided, on which a computer program or instruction is stored. When the computer program or the instruction is run on a computer, the method described in the first aspect and any possibility of the first aspect is executed; or, the method described in the second aspect and any possibility of the second aspect is executed; or, the method described in the third aspect and any possibility of the third aspect is executed; or, the method described in the fourth aspect and any possibility of the fourth aspect is executed.
[0078] In the twelfth aspect, a computer program product is provided, comprising instructions, which, when executed on a computer, cause the method described in the first aspect and any possible embodiment of the first aspect to be executed; or, cause the method described in the second aspect and any possible embodiment of the second aspect to be executed; or, cause the method described in the third aspect and any possible embodiment of the third aspect to be executed; or, cause the method described in the fourth aspect and any possible embodiment of the fourth aspect to be executed;.
[0079] In the thirteenth aspect, a communication system is provided, including: a terminal device and a network device; the terminal device is used to execute the method described in the first aspect and any possibility of the first aspect, and the network device is used to execute the method described in the first aspect and any possibility of the first aspect; or, the terminal device is used to execute the method described in the third aspect and any possibility of the third aspect, and the network device is used to execute the method described in the fourth aspect and any possibility of the fourth aspect.
[0080] The description of the beneficial effects of the second to thirteenth aspects may correspond to the description of the beneficial effects of the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0081] FIG1 is a schematic diagram of an application scenario 100 according to an embodiment of the present application.
[0082] FIG2 is a schematic diagram of a random access process 200 .
[0083] FIG3 is a schematic diagram of an interaction flow of a communication method 300 according to an embodiment of the present application.
[0084] FIG4 is a schematic diagram of the time interval between the time domain resources of downlink information 1 and the time domain resources of PUCCH1 according to an embodiment of the present application.
[0085] FIG5 is a schematic block diagram of the structure of a communication device 500 according to an embodiment of the present application.
[0086] FIG6 is a schematic block diagram of the structure of a communication device 600 according to an embodiment of the present application.
[0087] FIG7 is a schematic block diagram of the structure of a communication device 700 according to an embodiment of the present application.
[0088] FIG8 is a schematic block diagram of the structure of a communication device 800 according to an embodiment of the present application.
[0089] FIG9 is a schematic block diagram of the structure of a communication device 900 according to an embodiment of the present application. DETAILED DESCRIPTION
[0090] The technical solution in this application will be described below with reference to the accompanying drawings.
[0091] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, universal mobile telecommunication system (UMTS), fifth generation (5G) system, etc. th generation, 5G) system or new radio (NR), sixth generation (6 th These include systems evolving beyond 5G, such as 5G (near-future, 6G) systems, and NTN systems such as intersatellite and satellite communications. Satellite communication systems include satellite base stations and terminal devices. Satellite base stations provide communication services to terminal devices. Satellite base stations can also communicate with ground base stations. Satellites can function as both base stations and terminal devices. Satellites can also refer to non-ground base stations or devices, such as drones, hot air balloons, low-, medium-, and high-orbit satellites.
[0092] The technical solution of the embodiment of the present application is applicable to both homogeneous and heterogeneous network scenarios, and there is no restriction on the transmission point. It can be multi-point coordinated transmission between macro base stations, micro base stations, and macro base stations. It is applicable to FDD / TDD systems. The technical solution of the present application is not only applicable to low-frequency scenarios (sub 6G), but also to high-frequency scenarios (above 6GHz), terahertz, optical communications, etc. The technical solution of the present application can be applied not only to communications between network devices and terminals, but also to communications between network devices and network devices, between terminals, Internet of Vehicles, Internet of Things, Industrial Internet, etc.
[0093] The technical solutions of the embodiments of the present application can also be applied to scenarios where a terminal is connected to a single base station, wherein the base station to which the terminal is connected and the core network (CN) to which the base station is connected are of the same standard. For example, if the CN is 5G Core, the base station corresponds to a 5G base station, and the 5G base station is directly connected to the 5G Core; or if the CN is 6G Core, 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 dual connectivity (DC) scenarios where a terminal is connected to at least two base stations.
[0094] The technical solutions of the embodiments of the present application can also be used in macro and micro scenarios composed of base stations of different forms in the communication network. For example, the base stations can be satellites, aerial balloon stations, drone stations, etc. The technical solutions of the present application are also suitable for scenarios where both wide-coverage base stations and small-coverage base stations exist.
[0095] The technical solutions of the embodiments of the present application can be applied to scenarios where high reliability business needs exist, such as ports, industrial manufacturing, transportation, and coal mines.
[0096] The technical solutions of the embodiments of the present application can also be applied to 5.5G, 6G and later wireless communication systems, and applicable scenarios include but are not limited to terrestrial cellular communications, NTN, satellite communications, high altitude platform station (HAPS) communications, vehicle-to-everything (V2X), integrated access and backhaul (IAB), and reconfigurable intelligent surface (RIS) communications.
[0097] The terminal in the embodiment of the present application may be a device with wireless transceiver functions, and may refer to user equipment (UE), access terminal, subscriber unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent or user device. The terminal device may also be a satellite phone, a cellular phone, a smart phone, a wireless data card, a wireless modem, a machine type communication device, 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 communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a communication device carried on a high-altitude aircraft, a wearable device, a drone, a robot, a terminal in device-to-device (D2D) communication, a terminal in V2X, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in smart grid, a wireless terminal in transportation security ... This application does not limit the wireless terminals in the smart city, the wireless terminals in the smart home, or the terminal devices in the communication network evolved after 5G.
[0098] In the embodiments of the present application, the communication device used to implement the functions of the terminal device can be the terminal device; it can also be a device that can support the terminal device to implement the functions, such as a chip system. The device can be installed in the terminal device or used in conjunction with the terminal device. In the present application, the chip system can be composed of a chip or include a chip and other discrete devices.
[0099] The network device in the embodiment of the present application is a device with wireless transceiver functions, which is used to communicate with the terminal device. The access network device can be a node in the radio access network (RAN), which can also be called a base station, or a RAN node. It can be an evolved Node B (eNB or eNodeB) of LTE; or a base station of a 5G network such as gNodeB (gNB) or a base station in a public land mobile network (PLMN) evolved after 5G, a broadband network gateway (BNG), an aggregation switch or the 3GPP (the 3GPP) rd For example, the RAN may be configured as a RAN defined by the 3GPP protocol, an open radio access network (O-RAN), or a cloud radio access network (C-RAN).
[0100] The network devices in the embodiments of the present application may also include various forms of base stations, such as: macro base stations, micro base stations (also called small stations), relay stations, transmitting and receiving points (TRP), transmitting points (TP), mobile switching centers, and devices to devices (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications. Devices that perform base station functions, network devices in NTN communication systems, etc., are not specifically limited in this application.
[0101] The network device in the embodiment of the present application may also include network elements or modules that implement some functions of the base station, for example, one or more of the following: a centralized unit (CU), a distributed unit (DU), or a radio unit (RU). Optionally, the CU can be further separated into a CU-control plane (CP) and a CU-user plane (UP). The functions of the CU and DU can be implemented by different network elements, or simultaneously by the baseband unit (BBU) of the base station. The function of the RU can be implemented by the radio frequency equipment of the base station. For example, the radio frequency equipment of the base station may be a remote radio unit (RRU), a pico remote radio unit (pRRU), an active antenna unit (AAU), or other units, modules or devices with radio frequency processing functions. The communication interface protocol between the BBU and the radio frequency equipment can be a common public radio interface (CPRI) interface protocol, an enhanced common public radio interface (eCPRI) interface protocol, or a fronthaul interface protocol between the DU and RU in the O-RAN system, etc., without limitation.
[0102] In the embodiments of the present application, the device for implementing the functions of the network device can be a network device, or a device that can support the network device to implement the functions, such as a chip system. The device can be installed in the network device or used in conjunction with the network device. The chip system in the embodiments of the present application can be composed of a chip, or can include a chip and other discrete devices.
[0103] To facilitate understanding of the embodiments of the present application, the following briefly introduces the relevant concepts involved in the present application:
[0104] The UE in this application can be divided into a first type of terminal device and a second type of terminal device. For example, the first type of terminal device is, for example, a low-complexity UE, and the second type of terminal device may be a non-low-complexity UE. For example, the first type of terminal device is, for example, a low-complexity UE (reduced capability UE, REDCAP UE), and the second type of terminal device may be a legacy UE, such as an enhanced mobile broadband (eMBB) UE. For example, the first type of terminal device is, for example, an even lower-complexity UE (enhanced reduced capability UE, EREDCAP UE), and the second type of terminal device may be a low-complexity UE (reduced capability UE, REDCAP UE).
[0105] The first type of terminal device and the second type of terminal device have different characteristics, which include one or more of the following:
[0106] Bandwidth, number of supported or configured resources, number of transmit antenna ports and / or receive antenna ports, number of RF channels, number of hybrid automatic repeat request (HARQ) processes, supported peak rate, application scenarios, latency requirements, processing capability, protocol version, duplex mode, services, etc. The first feature is described in detail below.
[0107] The bandwidth, or channel bandwidth, or the maximum channel bandwidth supported or configured for a terminal device, may be different between the first type terminal device and the second type terminal device. For example, the bandwidth of the first type terminal device may be 20 MHz, 10 MHz, or 5 MHz, while the bandwidth of the second type terminal device may be 100 MHz. It is understood that with the advancement 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, such as 3 MHz, 25 MHz, or 50 MHz.
[0108] The number of resources supported or configured, the number of resources can be RBs, REs, subcarriers, RB groups, REG bundles, control channel elements, subframes, radio frames, time slots, mini-time slots and / or symbol numbers. The number of resources supported or configured by the first type of terminal device and the second type of terminal device is different. For example: the number of resources supported by the first type of terminal device is 48RBs, and the number of resources supported by the second type of terminal device is 96RBs.
[0109] The number of transmitting antenna ports and / or the number of receiving antenna ports, that is, the number of transmitting antenna ports and / or the number of receiving antenna ports of the first type of terminal device is different from that of the second type of terminal device. For example: the number of transmitting antenna ports of the first type of terminal device can be 1, and the number of receiving antenna ports can be 2; the number of transmitting antenna ports of the second type of terminal device can be 2, and the number of receiving antenna ports can be 4.
[0110] The number of RF channels, that is, the number of RF channels of the first type of terminal device is different from that of the second type of terminal device. For example: the number of RF channels of the first type of terminal device can be 1, and the number of RF channels of the second type of terminal device can be 2.
[0111] The number of hybrid automatic repeat request (HARQ) processes, that is, the number of HARQ processes supported by the first type of terminal device is different from that of the second type of terminal device. For example, the number of HARQ processes of the first type of terminal device can be 8, and the number of HARQ processes of the second type of terminal device can be 16.
[0112] The supported peak rate, that is, the maximum peak rate of the first type of terminal device and the second type of terminal device is different. For example, the maximum peak rate supported by the first type of terminal device may be 100Mbps, and the peak rate supported by the second type of terminal device may be 200Mbps.
[0113] Application scenarios, that is, the first type of terminal devices and the second type of terminal devices serve different application scenarios. For example, the first type of terminal devices are used in industrial wireless sensing, video surveillance, wearable devices, etc., and the second type of terminal devices are used in mobile communications, video surfing, etc.
[0114] Delay requirements, that is, the first type of terminal device and the second type of terminal device have different requirements for transmission delay. For example: the delay requirement of the first type of terminal device may be 500 milliseconds, and the delay requirement of the second type of terminal device may be 100 milliseconds.
[0115] The processing capability and the processing timing and processing speed of the first type of terminal device and the second type of terminal device for the channel or data under different subcarrier space (SCS) conditions are different. For example, the first type of terminal device does not support complex operations, and the complex operations may include: artificial intelligence (AI) and VR rendering. The second type of terminal device supports complex operations, or it can be understood that the processing capability of the first type of terminal device is lower than that of the second type of terminal device.
[0116] Protocol version, that is, the first type of terminal device and the second type of terminal device belong to terminal devices of different protocol versions. For example, the protocol version supported by the first type of terminal device is Release 17 and later, and the protocol version supported by the second type of terminal device is earlier than Release 17, such as Release 15 or Release 16. For example, the protocol version supported by the first type of terminal device is Release 18, and the protocol version supported by the second type of terminal device is earlier than Release 18, such as Release 15, Release 16, or Release 17.
[0117] Duplex mode, the duplex mode includes half-duplex and full-duplex, for example: the first type of terminal equipment operates in half-duplex mode, and the second type of terminal equipment operates in full-duplex mode.
[0118] Services include but are not limited to Internet of Things applications, such as video surveillance, mobile broadband (MBB), etc. For example, the first type of terminal device supports video surveillance, and the second type of terminal device supports mobile broadband (MBB). This embodiment of the present application does not limit this.
[0119] It should be understood that other types or future new types of terminal devices that also support the technical solution of this application are also within the scope of protection of this application.
[0120] The terminal device 120 in this application may be an example of a first type of terminal device, and the terminal device 130 may be an example of a second type of terminal device.
[0121] It should be understood that the features in this application can also be understood as characteristic parameters and can be used interchangeably in this application.
[0122] FIG1 is a schematic diagram of an application scenario 100 according to an embodiment of the present application. As shown in FIG1 , the communication devices in application scenario 100 include, but are not limited to, a network device 110, a terminal device 120, and a terminal device 130. Network device 110 and terminal device 120 may communicate uplink or downlink, and network device 110 and terminal device 130 may communicate uplink or downlink, respectively, without limitation. It is understood that application scenario 100 is intended only as an example and does not limit the scope of protection claimed by this application.
[0123] In application scenario 100, network device 110 configures multiple random access resources for terminal devices (without distinguishing between terminal devices 120 and terminal devices 130), and terminal devices 120 and 130 each randomly select a random access resource from the multiple random access resources to perform a random access process. When the random access resources randomly selected by terminal devices 120 and 130 are the same, this will cause a random access conflict between terminal devices 120 and 130. Network device 110 needs to resolve the random access conflict between terminal devices 120 and 130, that is, network device 110 needs to determine that one of terminal devices 120 and 130 is a terminal device that has successfully performed random access, and the other terminal device is a terminal device that has failed random access. For a description of the random access process, please refer to Figure 2.
[0124] FIG2 is a schematic diagram of a random access process 200. As shown in FIG2 , the random access process 200 includes:
[0125] S210 , the terminal device 120 sends random access request information 1 to the network device 110 through random access resource 1 , and the terminal device 130 sends random access request information 2 to the network device 110 through random access resource 1 .
[0126] Accordingly, network device 110 receives random access request information 1 sent by terminal device 120 and random access request information 2 sent by terminal device 130. When network device 110 simultaneously receives random access request information 1 and random access request information 2 through random access resource 1, network device 110 determines that a random access conflict occurs between terminal device 120 and terminal device 130.
[0127] S220 , the network device 110 sends a random access response (RAR) message 1 to the terminal device 120 , and the network device 110 sends a RAR message 2 to the terminal device 130 .
[0128] Accordingly, terminal device 120 receives RAR information 1 from network device 110, which is used to respond to random access request information 1, and determines, based on RAR information 1, that a random access conflict has occurred between terminal device 120 and terminal device 130. Terminal device 130 receives RAR information 2 from network device 110, which is used to respond to random access request information 2, and determines, based on RAR information 2, that a random access conflict has occurred between terminal device 130 and terminal device 120.
[0129] Specifically, RAR information 1 can be used to indicate to the terminal device 120 that a random access conflict has occurred, and RAR information 2 can be used to indicate to the terminal device 130 that a random access conflict has occurred. RAR information 1 may include resource information of a physical uplink shared channel (PUSCH) 1 for which the terminal device 120 sends random access conflict contention information 1 to the network device 110, and RAR information 2 may include resource information of a PUSCH 2 for which the terminal device 130 sends random access conflict contention information 2 to the network device 110.
[0130] S230 . The terminal device 120 sends random access conflict contention information 1 to the network device 110 via PUSCH1 , and the terminal device 130 sends random access conflict contention information 2 to the network device 110 via PUSCH2 .
[0131] Accordingly, the network device 110 receives the random access contention information 1 sent by the terminal device 120 and the random access conflict contention information 2 sent by the terminal device 130 .
[0132] Specifically, the network device 110 determines, based on the random access conflict contention information 1 and the random access conflict contention information 2, that one of the terminal devices 120 and 130 is a terminal device that has successfully performed random access, and the other is a terminal device that has failed random access.
[0133] S240 . The network device 110 broadcasts the PDCCH to the terminal device 120 and the terminal device 130 .
[0134] Accordingly, terminal device 120 and terminal device 130 receive the PDCCH from network device 110. Specifically, when network device 110 determines that terminal device 120 is a terminal device that has successfully random accessed, network device 110 broadcasts a PDCCH to terminal device 120 and terminal device 130. The PDCCH is used to schedule a PDSCH, which carries information about terminal device 120. Accordingly, terminal device 120 determines that terminal device 120 is a terminal device that has successfully random accessed based on the information about terminal device 120 carried in the PDSCH. Terminal device 120 determines that terminal device 130 is a terminal device that has failed random access based on the information about terminal device 120 carried in the PDSCH.
[0135] As can be seen from the above, whether a terminal device successfully accesses or fails random access, it needs to detect PDCCH and PDSCH. For a terminal device that fails random access, the above process will cause it to take a longer delay to determine the random access failure, and thus the terminal device that fails random access will not be able to start a new random access process in time.
[0136] In view of the above technical problems, the present application provides a communication method and a communication device, which can reduce the delay for a terminal device that fails random access to determine the failure of random access.
[0137] The communication method and communication device according to the embodiments of the present application will be described below with reference to the accompanying drawings.
[0138] FIG3 is a schematic diagram of the interaction process of the communication method 300 according to an embodiment of the present application. The method process in FIG3 can be executed by the terminal device 120 and the network device 110, or by modules and / or devices (e.g., chips or integrated circuits) with corresponding functions installed in the terminal device 120 and the network device 110, and this application does not limit this. The following description will be made using the terminal device 120 and the network device 110 as an example. As shown in FIG3, the method 300 includes:
[0139] S310 , the terminal device 120 sends uplink information 1 to the network device 110 in resource 1 , where the uplink information 1 is information in a random access process.
[0140] S320 , the network device 110 sends PDCCH1 carrying downlink control information 1 to the terminal device 120 . PDCCH1 is used to schedule downlink information 1 , which is information in a random access process.
[0141] Correspondingly, the terminal device 120 receives PDCCH1 carrying downlink control information 1 from the network device 110 .
[0142] Specifically, after sending uplink information 1 to the network device 110 , the terminal device 120 receives PDCCH1 from the network device 110 .
[0143] S330. The terminal device 120 decodes PDCCH1.
[0144] S340, the terminal device 120 determines whether it is necessary to operate the downlink information 1 according to the downlink control information 1; or, the terminal device 120 determines whether to continue the current random access process according to the downlink control information 1; or, the terminal device 120 receives the downlink information 1, and the terminal device 120 determines the starting time of the physical uplink control channel (PUCCH) 1 for the response feedback to the downlink information 1.
[0145] In S340 , after the terminal device 120 successfully completes decoding of the PDCCH 1 , the terminal device 120 obtains the downlink control information 1 carried in the PDCCH 1 and can determine a corresponding operation according to the downlink control information 1 .
[0146] In one example, the terminal device 120 determines whether to operate the downlink information 1 based on the downlink control information 1. For example, the downlink control information 1 is used to instruct the terminal device 120 to operate the downlink information, or the downlink control information 1 is used to instruct the terminal device 120 not to operate the downlink information. In this way, the downlink control information 1 can be used to indicate to the terminal device 120 whether to continue operating the downlink information.
[0147] Exemplarily, the operation may be any one of: receiving, processing, storing, demodulating, decoding, channel estimation, etc., without limitation. Alternatively, the above operation may be understood as the standard not specifying the behavior of the terminal device, or the processing is left to the terminal device to determine.
[0148] It can be understood that the decoding of PDCCH mentioned in this application can be at least one of the following: detecting (detecting) PDCCH, blind monitoring (blend monitoring) PDCCH, receiving PDCCH, demodulating PDCCH, decoding PDCCH, channel estimating PDCCH, parsing PDCCH, etc.
[0149] It is understood that when terminal device 120 determines based on downlink control information 1 that downlink information 1 operation is required, terminal device 120 determines to continue the current random access procedure. For example, if terminal device 120 has successfully completed random access, terminal device 120 determines based on downlink control information 1 that downlink information 1 operation is not required, terminal device 120 discontinues the current random access procedure. For example, if terminal device 120 has failed random access, terminal device 120 can reduce the delay in determining that random access has failed, and can also save power.
[0150] It can be understood that the random access failure in the present application can be understood as a failure in contention resolution during the random access process, or a failure in receiving RAR during the random access process, or a failure in sending preamble. For example, whether the above-mentioned random access fails can be: whether the random access process request fails. As described above, when the uplink information 1 is random access request information, the terminal device 120 determines whether the random access process request initiated by the terminal device 120 fails based on PDCCH1. That is, whether the network device 110 rejects the random access process request of the terminal device 120. Whether the above-mentioned random access fails can also be: a failure in contention resolution. As described above, when the uplink information 1 is contention resolution information during the random access process, the terminal device 120 determines whether the contention resolution of the terminal device 120 fails based on PDCCH1. In summary, no matter what the scenario is, the terminal device 120 can determine whether the random access fails based on PDCCH1.
[0151] In one possible implementation, the time interval between the end moment of the PDCCH and the start moment of the downlink information scheduled by the PDCCH exceeds the third threshold, and the terminal device does not receive the downlink information. The time interval between the end moment of the PDCCH and the start moment of the downlink information scheduled by the PDCCH does not exceed the third threshold, and the terminal device does not process the downlink information. For example, the third threshold is the length of time the terminal device processes the PDCCH. For example, the third threshold is N symbols, where N is a positive integer. For example, the value of the third threshold can be 3 symbols, or 2 symbols, or 1 symbol. For example, the third threshold is 0.5ms or 0.25ms. Exemplarily, the third threshold is different when the subcarrier spacing SCS is different. For example, the subcarrier spacing SCS is 15kHz, and the third threshold is 3 symbols. For example, the subcarrier spacing SCS is 30kHz, and the third threshold is 4 symbols.
[0152] Exemplarily, the index value of the last symbol of the PDCCH belongs to the first range, and the terminal device does not receive downlink information. The index value of the last symbol of the PDCCH does not belong to the first range, and the terminal device does not process downlink information. For example, the first range includes at least one of the following: 14, 13, 12, 11. For example, the first range includes at least one of the following: 14, 13, 12. Exemplarily, the first range is different when the subcarrier spacing SCS is different. For example, the subcarrier spacing SCS is 15kHz, and the first range includes at least one of the following: 14, 13, 12. For example, the subcarrier spacing SCS is 30kHz, and the first range includes at least one of the following: 14, 13, 12, 11, 10, 9.
[0153] Exemplarily, the interval between the time slot for transmitting the PDCCH and the time slot for transmitting the downlink information scheduled by the PDCCH is less than N time slots, and the terminal device does not receive the downlink information. The interval between the time slot for transmitting the PDCCH and the time slot for transmitting the downlink information scheduled by the PDCCH is greater than K time slots. For example, K is an integer. For example, K=0 or 1 or 2. For example, the time slot for transmitting the PDCCH and the time slot for transmitting the downlink information scheduled by the PDCCH are not adjacent time slots, and the terminal device processes the downlink information. The time slot for transmitting the PDCCH and the time slot for transmitting the downlink information scheduled by the PDCCH are adjacent time slots, and the terminal device does not process the downlink information. For example, the time slot for transmitting the PDCCH is time slot N, and the time slot for transmitting the downlink information scheduled by the PDCCH is time slot N+K, and the terminal device does not receive the downlink information. Wherein, K is an integer greater than 1. The time slot for transmitting the PDCCH is time slot N, and the time slot for transmitting the downlink information scheduled by the PDCCH is time slot N+1, and the terminal device does not process the downlink information. Exemplarily, the subcarrier spacing SCS is different, and K is different. For example, the subcarrier spacing SCS is 15 kHz, and K = 0. For example, the subcarrier spacing SCS is 30 kHz, and K = 1.
[0154] For example, not processed as reception, but not demodulation and / or not decoding.
[0155] In another example, the terminal device 120 determines whether to continue the current random access process based on the downlink control information 1. For example, the downlink control information 1 is used to indicate that the terminal device 120 can continue the current random access process; or, the downlink control information 1 is used to indicate that the terminal device 120 no longer continues the current random access process. In this way, the terminal device 120 can determine whether it is necessary to continue the current random access process based on the downlink control information 1. It can be understood that when the terminal device 120 determines that it is necessary to continue the current random access process, the terminal device 120 can determine that the terminal device 120 is a terminal device that has successfully accessed the random access. When the terminal device 120 determines that it is not necessary to continue the current random access process, the terminal device 120 can determine that the terminal device 120 is a terminal device that has failed random access.
[0156] In summary,
[0157] Through the above scheme, the terminal device can determine that the random access has failed based on the PDCCH, without further receiving the PDSCH scheduled by the PDCCH to determine whether the random access has failed. This can reduce the delay for the terminal device that has failed the random access to determine the random access failure, saving the power consumption of the terminal device. When the terminal device that has failed the random access determines that the random access has failed based on the PDCCH, it can start a new random access process as soon as possible, thus shortening the time it takes for the terminal device that has failed the random access to start a new random access process. For example, after this random access fails, the terminal device can initiate the next random access process in the current cell, or select another cell to initiate a new random access process.
[0158] Optionally, when the terminal device 120 receives downlink information 1 according to the scheduling information of the downlink control information 1 and determines the start time of PUCCH1 for response feedback of the downlink information 1, the end time of the downlink information 1 and the start time of PUCCH1 transmission meet the minimum time interval. That is, the time interval between the end time of the downlink information 1 and the start time of PUCCH1 transmission is within the processing capability of the terminal device 120.
[0159] In one possible implementation, uplink information 1 may be a PUSCH in message A of a two-step random access channel (RACH) process, and downlink information 1 may be a RAR in message B of a two-step RACH process. Alternatively, uplink information 1 may be message 3 of a four-step RACH process, and downlink information 1 may be message 4 of the four-step RACH process or contention resolution information.
[0160] Specifically, when the uplink information 1 is the PUSCH in message A and the downlink information 1 is the RAR in message B, the terminal device 120 can determine whether it is necessary to continue the current random access process based on the downlink control information 1 in the PDCCH1. For example, the terminal device 120 can determine whether the RAR reception has failed based on the downlink control information 1. In other words, when the terminal device 120 determines that it is not necessary to operate the RAR based on the downlink control information 1, the terminal device 120 determines that the random access process has failed. When 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 competition has failed based on the downlink control information 1. For example, when the downlink control information 1 indicates that the terminal device 120 does not need to operate message 4, the terminal device 120 determines that the random access competition has failed. It can be understood that when the downlink control information 1 instructs the terminal device 120 to operate message 4, the terminal device 120 determines that the random access competition is successful.
[0161] In one possible implementation, the downlink control information 1 includes a frequency domain resource allocation (FDRA) field, and the FDRA field is used to allocate resource blocks for the transmission of the downlink information 1.
[0162] Specifically, the above-mentioned resource block may refer to a resource unit. A resource unit may be a frequency domain resource unit and / or a time domain resource unit. For example, a frequency domain resource unit is a resource block (RB), bandwidth, channel bandwidth, bandwidth part (BWP), resource block group (RBG), resource element (RE), subcarrier, control channel element (CCE), resource element group (REG), and carrier. A time domain resource unit is a symbol, time slot, subslot, subframe, frame, and superframe.
[0163] In one example, when the number of resource blocks allocated for downlink information 1 transmission using the FDRA field exceeds a first threshold, the terminal device 120 does not perform downlink information 1 operations; or, when the number of resource blocks allocated for downlink information 1 transmission using the FDRA field exceeds the first threshold, the terminal device 120 does not perform downlink information 1 operations, and the terminal device 120 determines that the current random access has failed; or, when the number of resource blocks allocated for downlink information 1 transmission using the FDRA field exceeds the first threshold, the terminal device 120 does not continue the current random access process; or, when the number of resource blocks allocated for downlink information 1 transmission using the FDRA field exceeds the first threshold, the terminal device 120 does not continue the current random access process, and the terminal device 120 determines that the current random access has failed. For example, the first threshold can be understood as the processing capability of the terminal device 120. For example, the first threshold corresponds to the subcarrier spacing (SCS). For example, if the subcarrier spacing (SCS) is 15 kHz, the first threshold is 25 RBs. For example, if the subcarrier spacing (SCS) is 30 kHz, the first threshold is 12 RBs.
[0164] For example, the terminal device 120 determines that the 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 the TEMPORARY_C-RNTI, resending Msg1, notifying the upper layer of the terminal device 120 that the PDSCH cannot be processed, and notifying the upper layer of the terminal device 120 that the PDSCH or MAC protocol data unit (PDU) decoding has failed.
[0165] In summary, the terminal device 120 can determine that random access has failed based on the number of resource blocks indicated in the downlink control information 1. For example, when the number of resource blocks indicated in the downlink control information 1 exceeds a threshold, the terminal device 120 can determine that random access has failed. This can reduce the delay in the terminal device determining that random access has failed.
[0166] In one example, when the number of resource blocks allocated by the FDRA field for transmission of downlink information 1 exceeds a first threshold, terminal device 120 operates downlink information 1. At this point, terminal device 120 determines that the aforementioned minimum time interval is equal to the sum of the first time interval and a first value, and the first value is greater than 0. In other words, the aforementioned minimum time interval exceeds the processing capability of terminal device 120. That is, when the network device schedules downlink information 1 for the terminal device, the scheduling time is within the processing capability of terminal device 120, or the scheduling time exceeds the processing capability of terminal device 120.
[0167] Exemplarily, the processing capability of the terminal device 120 may be the bandwidth that the terminal device 120 can support, the channel bandwidth, the maximum channel bandwidth supported or configured, or the number of resource units that can be processed per unit time. For example, the unit time is one or more time domain resource units. For example, the subcarrier spacing is 15kHz, and the maximum number of resource scheduling supported by the terminal device 120 is 25 RBs. When the number of RBs included in resource 2 is greater than 25 RBs, it is considered that the number of resources 2 is greater than the processing capability of the terminal device 120. For example, the subcarrier spacing is 30kHz, and the maximum number of resource scheduling supported by the terminal device 120 is 12 RBs. When the number of RBs included in resource 2 is greater than 12 RBs, the terminal device 120 considers that the number of resources 2 is greater than the processing capability of the terminal device 120.
[0168] In addition, the processing capability of the terminal device 120 may also be the processing timing or processing speed of the channel or data.
[0169] In one example, when the number of resource blocks allocated for downlink information 1 transmission by the FDRA field does not exceed the first threshold, the terminal device 120 operates downlink information 1; or, when the number of resource blocks allocated for downlink information 1 transmission by the FDRA field does not exceed the first threshold, the terminal device 120 continues the current random access process; or, when the number of resource blocks allocated for downlink information 1 transmission by the FDRA field does not exceed the first threshold, the terminal device 120 determines that the aforementioned minimum time interval is equal to the first time interval. In this way, the terminal device 120 can determine that the random access is successful based on the number of resource blocks indicated by the downlink control information 1, and then proceed to the subsequent process. For example, the subsequent process can be to determine whether the random access is successful based on the downlink information 1.
[0170] In one possible implementation, the downlink control information includes a frequency domain resource allocation FDRA field, which is used to allocate resource blocks for downlink information transmission. When the number of allocated resource blocks exceeds a first threshold, the terminal device stops the contention resolution timer (e.g., ra-ContentionResolutionTimer), and / or the terminal device discards TEMPORARY_C-RNTI. In addition, the terminal device 120 can determine whether it is necessary to stop operations such as the contention resolution timer based on the relationship between the FDRA field and the first threshold. In other words, when 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, and / or discards TEMPORARY_C-RNTI, etc. It can be understood that this solution can be implemented independently of the aforementioned solution.
[0171] In one possible implementation, the downlink control information includes a frequency domain resource allocation FDRA field, which is used to allocate resource blocks for downlink information transmission. When the number of allocated resource blocks exceeds a first threshold, the terminal device sends a second indication message at a lower layer, which indicates that the terminal device cannot operate downlink information 1, or that the downlink information 1 operation fails, or that the MAC PDU operation fails. After receiving the second indication message, the terminal device stops the contention resolution timer (e.g., ra-ContentionResolutionTimer), and / or the terminal device discards the TEMPORARY_C-RNTI.
[0172] In one possible implementation, downlink control information 1 includes time indication information 1, which is used to determine the time unit for PUCCH 1 transmission. PUCCH 1 is used to carry feedback information of downlink information scheduled by 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 time of downlink information 1 and the start time of the time unit for PUCCH 1 transmission.
[0173] For example, the time unit is a symbol, a time slot, a sub-time slot, a sub-frame, a frame, and a superframe.
[0174] In one example, when the time interval between the end moment of the downlink information 1 and the start moment of the PUCCH1 transmission is less than the second threshold, the terminal device 120 does not operate the downlink information 1; or, the time interval between the end moment of the downlink information 1 and the start moment of the PUCCH1 transmission is less than the second threshold, the terminal device 120 does not operate the downlink information 1, and the terminal device 120 determines that this random access has failed; or, the time interval between the end moment of the downlink information 1 and the start moment of the PUCCH1 transmission is less than the second threshold, the terminal device 120 does not continue the current random access process; or, the time interval between the end moment of the downlink information 1 and the start moment of the PUCCH1 transmission is less than the second threshold, the terminal device 120 does not continue the current random access process, and the terminal device 120 determines that this random access has failed.
[0175] For example, the second threshold value can be understood as the processing capability of the terminal device 120. For example, the second threshold value is the capability of the terminal device 120 to process PDSCH. For example, the second threshold value is the capability of the terminal device 120 to process Msg4 PDSCH. For example, the second threshold value is the capability of the terminal device 120 to process Msg2 PDSCH. For example, the second threshold value corresponds to the subcarrier spacing SCS. For example, the subcarrier spacing SCS is 15kHz, the second threshold value is 13 symbols, or 14 symbols. For example, the subcarrier spacing SCS is 30kHz, and the second threshold value is 13 symbols.
[0176] In summary, the terminal device 120 can determine that random access has failed based on the time unit indicated in the downlink control information 1. For example, when the time interval between the end time of the downlink information 1 and the start time of the PUCCH 1 transmission is less than the second threshold, the terminal device 120 determines that the random access has failed. In this way, the delay in the terminal device determining that the random access has failed can be reduced.
[0177] In one example, if the time interval between the end time of downlink information 1 and the start time of PUCCH1 transmission is not less than the second threshold, the terminal device 120 determines to operate downlink information 1; or if the time interval between the end time of downlink information 1 and the start time of PUCCH1 transmission is not less than the second threshold, the terminal device 120 determines to continue the current random access procedure. In this way, the terminal device 120 can determine that the subsequent process can be carried out based on the time interval between the end time of downlink information 1 and the start time of PUCCH1 transmission being less than the second threshold.
[0178] FIG4 is a schematic diagram of the time interval between the time domain resources of downlink information 1 and the time domain resources of PUCCH 1 according to an embodiment of the present application. As shown in FIG4 , the time interval between the time domain resources of downlink information 1 and the time domain resources of PUCCH 1 can refer to the interval between the end position of the time domain resources of downlink information 1 and the start position of the time domain resources of PUCCH 1 (described using this as an example), or the interval between the start position of the time domain resources of downlink information 1 and the start position of the time domain resources of PUCCH 1 (not shown in FIG4 ), or the interval between the center position of the time domain resources of downlink information 1 and the center position of the time domain resources of PUCCH 1 (not shown in FIG4 ).
[0179] For example, the unit of the time interval can be any one of a symbol, a time slot, a transmission opportunity, a paging occasion (PO), a mini-slot, a sub-slot, a sub-frame, ms, or μs. In addition, the starting position, center position, and ending position of the time domain resource can be represented by any one of a symbol, a time slot, a transmission opportunity, PO, a mini-slot, a sub-slot, a sub-frame, ms, or μs. For example, the interval between the time domain resource of downlink information 1 and the time domain resource of PUCCH1 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 PUCCH1. For another example, the time interval between the time domain resource of downlink information 1 and the time domain resource of PUCCH1 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 PUCCH1.
[0180] In addition, the processing capability of the terminal device 120 can also be the processing timing or processing speed of the channel or data. The higher the processing capability of the terminal device 120, the shorter the processing time required; the lower the processing capability of the terminal device 120, the longer the processing time required. For example, the processing capability of the terminal device 120 is the time it takes for the terminal device 120 to process the PDSCH, or the sum of the time it takes for the terminal device 120 to process the downlink information 1 and to feed back the processing results through signaling. Therefore, the shortest time for the terminal device 120 to process the downlink information 1 and to feed back the processing results through PUCCH1 is T1. The time interval between the downlink information 1 scheduled by the network device 110 and its feedback of PUCCH1 is T2. When T2 < T1, it can be considered that the timing scheduled by the network device 110 is greater than or exceeds the processing capability of the terminal device 120.
[0181] In one possible implementation, the downlink control information 1 includes first indication information, and the first indication information is used to instruct the terminal device with the first characteristic parameter to operate the downlink information 1.
[0182] Specifically, the above-mentioned characteristic parameters may refer to the aforementioned parameters on how to distinguish terminal devices, for example, including but not limited to: bandwidth, number of supported or configured resources, number of transmitting antenna ports and / or number of receiving antenna ports, number of RF channels, number of hybrid automatic repeat request (HARQ) processes, supported peak rate, application scenarios, latency requirements, processing capability, protocol version, duplex mode, and service.
[0183] If the characteristic parameter of the terminal device 120 is not the first characteristic parameter, the terminal device 120 does not operate on downlink information 1; or if the characteristic parameter of the terminal device 120 is not the first characteristic parameter, the terminal device 120 does not operate on downlink information 1, and the terminal device 120 determines that the current random access has failed; or if the characteristic parameter of the terminal device 120 is not the first characteristic parameter, the terminal device 120 does not continue the current random access process; or if the characteristic parameter of the terminal device 120 is not the first characteristic parameter, the terminal device 120 does not continue the current random access process, and the terminal device 120 determines that the current random access has failed; or if the characteristic parameter of the terminal device 120 is the first characteristic parameter, the terminal device 120 operates on downlink information 1. This can also reduce the delay for the terminal device to determine that the random access has failed.
[0184] In one possible implementation, PDCCH1 includes first indication information, and the first indication information is used by the terminal device to determine that random access has failed. Specifically, the PDCCH1 sent by the network device 110 to the terminal device 120 includes the first indication information, which is used to indicate to the terminal device 120 that random access has failed. The following describes different scenarios.
[0185] Scenario 1:
[0186] Example 1 - Random access failure means that when the random access competition fails, the first indication information is used to indicate to the terminal device 120 that it should not operate the PDSCH1 scheduled by PDCCH1. The PDSCH1 carries information about the terminal device that has successfully performed random access. For example, when the network device 110 determines that the terminal device 130 is a terminal device that has successfully performed random access, PDSCH1 includes the identification information of the terminal device 130. Accordingly, 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 PDSCH1. Further, the terminal device 120 determines that the terminal device 120 is a terminal device that has failed random access based on the first indication information. Furthermore, the terminal device 120 does not need to continue to operate the PDSCH1 scheduled by PDCCH1.
[0187] Example 2 - Random access failure refers to when random access contention resolution fails, and the first indication information is used to indicate to the terminal device 120 that the PDSCH1 scheduled by the PDCCH1 does not include contention resolution information of the terminal device 120. Accordingly, the terminal device 120 determines that it is not necessary to continue operating the PDSCH1 based on the first indication information, and determines that the terminal device 120 is a terminal device that has failed random access.
[0188] Example 3 - Random access failure refers to a random access contention failure. The first indication information is used to indicate the random access contention failure to terminal device 120. Accordingly, terminal device 120 determines that terminal device 120 has failed random access based on the first indication information. Consequently, terminal device 120 does not need to continue operating PDSCH1 scheduled by PDCCH1.
[0189] Scenario 2:
[0190] Example 4 - Random access failure refers to a failure to receive a random access response message. The first indication information is used to instruct the terminal device 120 not to operate the PDSCH2 scheduled by the PDCCH1. The PDSCH2 includes resource information of the RAR information. Therefore, the terminal device 120 does not need to continue to operate the PDSCH2.
[0191] Example 5 - Random access failure refers to a failure to receive random access response information, and the first indication information is used to indicate to the terminal device 120 that PDSCH2 does not include resource information of the RAR information of the terminal device 120. Therefore, the terminal device 120 does not need to continue operating PDSCH2.
[0192] Example 6 - Random access failure refers to a failure to receive random access response information, and the first indication information is used to indicate the failure to receive RAR information to the terminal device 120. In this way, the terminal device 120 does not need to operate PDSCH2.
[0193] In one possible implementation, the first indication information is carried in the downlink assignment index (DAI) field. For example, PDCCH1 is the PDCCH that schedules Msg4. For example, the first terminal device parses PDCCH1 in a first manner, and the first manner is: PDCCH1 includes the first indication information, and PDCCH1 does not include the DAI domain. For example, the first terminal device parses PDCCH1 in a second manner, and the second manner is: PDCCH1 includes the first indication information, PDCCH1 includes the DAI domain, and the number of bits in the DAI domain is 1. For example, the second terminal device parses PDCCH1 in a third manner, and the third manner is: PDCCH1 does not include the first indication information, PDCCH1 includes the DAI domain, and the number of bits in the DAI domain is 2.
[0194] Optionally, the first indication information can be carried in the reserved domain. For example, PDCCH1 is the PDCCH that schedules Msg2. For example, the first terminal device parses PDCCH1 according to the first method, and the first method is: PDCCH1 includes the first indication information, and PDCCH1 does not include the reserved domain. For example, the first terminal device parses PDCCH1 according to the second method, and the second method is: PDCCH1 includes the first indication information, PDCCH1 includes the reserved domain, and the number of bits of the reserved domain is A1. For example, the second terminal device parses PDCCH1 according to the third method, and the third method is: PDCCH1 does not include the first indication information, PDCCH1 includes the reserved domain, and the number of bits of the reserved domain is A2. Among them, A1 is an integer, A2 is an integer, and A1 is less than A2.
[0195] 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.
[0196] For example, the network device distinguishes between RedCap and eMBB UE types in Msg1, and distinguishes between R17 RedCap and R18 RedCap UE types in Msg3. That is, different Msg1 resources are allocated to RedCap UE and eMBB, but the same Msg1 resources are allocated to R17 RedCap UE and R18 RedCap UE. R17 RedCap UE and R18 RedCap UE report the UE type in Msg3 to facilitate network device differentiation.
[0197] For example, the first indication information includes 1 bit.
[0198] For example, the first indication information is in a first bit state, and the first indication information indicates that the first terminal device operates downlink information. The first indication information is in a second bit state, and the first indication information indicates that the first terminal device does not operate downlink information. For example, the bit state of the first information is "1", indicating that the R18 RedCap UE receives Msg4 PDSCH. For example, the bit state of the first information is "0", indicating that the R18 RedCap UE does not receive Msg4 PDSCH.
[0199] For example, the first indication information is in a first bit state, and the first indication information indicates that the first terminal device operates downlink information. The first information is in a second bit state, and the first information indicates that the second terminal device operates downlink information. For example, the bit state of the first indication information is "1" to indicate that the R17 RedCap UE operates downlink information, and the bit state of the first indication information is "0" to indicate that the R18 RedCap UE operates downlink information. For example, the bit state of the first indication information is "1" to indicate that the downlink information is sent to the R17 RedCap UE, and the bit state of the first indication information is "0" to indicate that the downlink information is sent to the R18 RedCap UE.
[0200] For example, the network device does not distinguish between RedCap and eMBB UE types in Msg1. Instead, it distinguishes between eMBB, R17 RedCap, and R18 RedCap UE types in Msg3. This means that the same Msg1 resources are allocated to RedCap UEs and eMBB. eMBB, R17 RedCap UEs, and R18 RedCap UEs all report their UE types in Msg3, making it easier for the network device to distinguish them.
[0201] For example, the first indication information includes 2 bits.
[0202] For example, the first indication information is in a first bit state, indicating that the first terminal device is operating downlink information. The first indication information is in a second bit state, indicating that the second terminal device is receiving and operating downlink information. The first indication information is in a third bit state, indicating that the first indication information is in a third bit state, indicating that the third terminal device is operating downlink information. For example, the bit state of the first indication information is "00" to indicate that an R17 RedCap UE is operating downlink information, the bit state of the first indication information is "01" to indicate that an R18 RedCap UE is operating downlink information, and the bit state of the first indication information is "10" to indicate that an eMBB UE is operating downlink information. For example, the third terminal device is an eMBB UE. For example, the bit state of the first indication information is "00" to indicate that the downlink information is sent to an R17 RedCap UE, the bit state of the first indication information is "01" to indicate that the downlink information is sent to an R18 RedCap UE, and the bit state of the first indication information is "10" to indicate that the downlink information is sent to an eMBB UE.
[0203] For example, the network device distinguishes between R17 RedCap and R18 RedCap UE types in Msg1, that is, allocates different Msg1 resources to R17 RedCap UE and R18 RedCap UE.
[0204] 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.
[0205] For example, the first indication information includes at least one bit, the first bit of the first indication information corresponds to the RAR of preamble index 0, the first bit is in the first bit state, and the first indication information indicates that the first terminal device operates downlink information. The first bit is in the second bit state, and the first indication information indicates that the first terminal device does not operate downlink information.
[0206] In one possible implementation, the terminal device 120 reports characteristic parameters or characteristics via message 3 .
[0207] Optionally, the characteristic parameter may refer to the maximum bandwidth of unicast data transmission of the terminal device being no more than 5 MHz, or the number of resource blocks used for unicast data transmission of the terminal device being no more than M, where M is a positive integer and has a corresponding relationship with the SCS.
[0208] Optionally, the characteristic parameter may refer to a maximum bandwidth of unicast data processing by the terminal device being no greater than 5 MHz, or a number of resource blocks used for unicast data processing by the terminal device being no greater than M, where M is a positive integer and corresponds to 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.
[0209] It should be noted that the terminal device 120 can report the characteristic parameters of the terminal device 120 to the network device 110 through message 3.
[0210] In one possible implementation, when the terminal device 120 determines that random access fails, the method 300 may further include:
[0211] S350. The lower layer of the terminal device 120 sends a second indication message, where the second indication message is used to indicate that the downlink information 1 cannot be processed, or that the processing of the downlink information 1 fails.
[0212] Specifically, 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 a second indication information to the upper layer (for example, the media access control layer (MAC) or the radio resource control layer (RRC)), thereby assisting the upper layer of the terminal device 120 to adjust the random access process or re-initiate random access.
[0213] In one possible implementation, method 300 may further include:
[0214] S360: The terminal device 120 stops the contention resolution timer (eg, ra-ContentionResolutionTimer).
[0215] Specifically, when the terminal device 120 determines that the random access fails according to the downlink control information 1 in the PDCCH1, the terminal device 120 can stop the contention resolution timer, thereby reducing power consumption.
[0216] Optionally, the terminal device 120 may also choose to discard PDCCH1.
[0217] Optionally, when the terminal device 120 determines that the random access fails, the terminal device 120 may re-initiate a new random access.
[0218] It should be noted that, in the embodiment of the present application, the order of S310 to S360 is not fixed and can be adjusted according to specific circumstances. In addition, some steps in S310 to S360 are optional and may not be mandatory, and this is not limited.
[0219] It should be noted that the terminal device 120 can report the type of the terminal device 120 to the network device 110, that is, whether the terminal device 120 belongs to the first type of terminal device or the second type of terminal device. In one example, the terminal device 120 can report the type of the terminal device 120 to the network device 110 through information 1.
[0220] In one possible implementation, the processing capability of terminal device 120 is lower than that of terminal device 130. When network device 110 determines that terminal device 130 has successfully performed random access, network device 110 can use information such as the number of resources 1 and the time interval indicated by PDSCH1 on PDCCH1 to allow terminal device 120 to determine that terminal device 120 has failed random access. This can reduce the delay in terminal device 120 determining that random access has failed.
[0221] The communication method 300 will be further described below.
[0222] In one possible implementation, 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 greater than the processing capability of terminal device 120, and / or the time interval between the time domain resource of the first resource and the time domain resource of the second resource is less than the processing capability of terminal device 120, terminal device 120 deems the random access to have failed.
[0223] Exemplarily, the first control information is downlink control information or a physical downlink control channel (PDCCH). The first control information is TC-RNTI-scrambled DCI. The first control information is the PDCCH in message 4. The first information is the PDSCH or data information carried on the PDSCH. The first information is the PDSCH in message 4. The second information is uplink control information, or the PUCCH, or control information carried on the PUCCH. The second information is HARQ-ACK for feedback of the PDSCH in message 4.
[0224] The size of the first resource can be found in the above description and will not be repeated here.
[0225] In addition, the processing capability of the terminal device 120 is the bandwidth that the terminal device 120 can support, or the channel bandwidth, or the maximum channel bandwidth supported or configured by the terminal device, or the number of resource units that can be processed per unit time. For example, the unit time is one or more time domain resource units. The processing capability of the terminal device 120 can also be the processing timing and processing speed of the channel or data. It can be understood that the higher the processing capability of the terminal device 120, the shorter the processing time required; the lower the processing capability of the terminal device 120, the longer the processing time required. For example, the processing capability of the terminal device 120 is the time for the terminal device 120 to process PDSCH, or the sum of the time for the terminal device 120 to process PDSCH and feedback the processing results through signaling.
[0226] Exemplarily, the subcarrier spacing is 15 kHz, and the maximum number of resource scheduling supported by the terminal device 120 is 25 RBs. When the number of RBs included in the first resource is greater than 25 RBs, it is considered that the size of the first resource is greater than the processing capability of the terminal device 120. For example, the subcarrier spacing is 30 kHz, and the maximum number of resource scheduling supported by the terminal device 120 is 12 RBs. When the number of RBs included in the first resource is greater than 12 RBs, it is considered that the size of the first resource is greater than the processing capability of the terminal device 120.
[0227] The minimum time for terminal device 120 to process PDSCH and feedback the processing results through PUCCH is T1. The time interval between the PDSCH scheduled by network device 110 and its feedback PUCCH is T2. When T2 is less than T1, it is considered that the timing of network device 110 scheduling exceeds the processing capacity of terminal device 120.
[0228] Optionally, when it is determined that the contention resolution fails, the terminal device 120 will perform at least one of the following operations: the bottom layer notifies the upper layer that it cannot process PDSCH, the bottom layer notifies the upper layer that PDSCH or MAC PDU processing fails, stops the contention resolution timer, discards TC-RNTI, and re-initiates random access.
[0229] With 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. The contention failure can be determined after reading the PDCCH in message 4, avoiding the waste of power consumption caused by continuing blind detection, and can re-initiate the random access process as soon as possible, thereby shortening the random access delay.
[0230] In one possible implementation, the terminal device 120 receives a notification from the underlying layer that it cannot operate the PDSCH, or the PDSCH is not successfully decoded, or the MAC PDU is not successfully decoded, and the terminal device performs at least one of the following operations: stops the contention resolution timer, discards the TEMPORARY_C-RNTI, and considers that the contention resolution has failed.
[0231] Exemplarily, the process of the terminal device is as follows: if the PDSCH or MAC PDU is not successfully decoded; or if the bottom layer notifies that the PDSCH cannot be processed:
[0232] ■Stop the contention resolution timer;
[0233] ■Discard TEMPORARY_C-RNTI;
[0234] ■ Believe that this competition has failed
[0235] In one possible implementation, the terminal device 120 receives second control information, which is used to schedule the first data information; the second control information includes third information, which is used to instruct the terminal device 120 to receive the first data information or not to receive the first data information.
[0236] When the third information indicates that the terminal device 120 does not receive the first data information, the terminal device 120 may determine that the random access fails.
[0237] Optionally, the second control information is downlink control information. For example, the second control information is TC-RNTI scrambled DCI. The second control information is the PDCCH in message 4. For example, the second control information is RA-RNTI scrambled DCI. The second control information is the PDCCH in message 2 or the PDCCH of the RAR.
[0238] 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.
[0239] In a possible embodiment, the random access failure is a random contention resolution failure.
[0240] For example, the third information in the PDCCH in message 4 indicates that the terminal device 120 does not receive the PDSCH in message 4, or indicates that the PDSCH in message 4 does not include the contention resolution message of the terminal device 120, or indicates that the contention resolution of the terminal device 120 fails.
[0241] For example, the third information is carried in the downlink assignment index (DAI) 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 DAI. The terminal device 130 parses the second control information, and the second control information does not include the third information but includes DAI. For example, the terminal device 120 parses the second control information, and the second control information includes the third information, and the second control information includes the DAI field, and the number of bits of the DAI field is 1. The terminal device 130 parses the second control information, and the second control information does not include the third information, and the second control information includes the DAI field, and the number of bits of the DAI field is 2.
[0242] 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.
[0243] For example, network device 110 distinguishes between RedCap and eMBB UE types in Message 1, and distinguishes between R17 RedCap and R18 RedCap UE types in Message 3. That is, different Message 1 resources are allocated to RedCap UEs and eMBB, but the same Message 1 resources are allocated to R17 RedCap UEs and R18 RedCap UEs. R17 RedCap UEs and R18 RedCap UEs report their UE types in Message 3, making it easier for network device 110 to distinguish them.
[0244] Optionally, the third information includes 1 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" for the third information indicates that the first data information is sent to an R17 RedCap UE, and a bit state of "0" for the third information indicates that the first data information is sent to an R18 RedCap UE. For example, a bit state of "1" for the third information instructs the R17 RedCap UE to receive the first data information, and a bit state of "0" for the third information instructs the R18 RedCap UE to receive the first data information. For 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 a 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" for the third information instructs the R18 RedCap UE to receive the PDSCH in message 4. For example, a bit state of "0" for the third information instructs the R18 RedCap UE not to receive the PDSCH in message 4.
[0245] For example, network device 110 does not distinguish between RedCap and eMBB UE types in Message 1. Instead, network device 110 distinguishes between eMBB, R17 RedCap, and R18 RedCap UE types in Message 3. That is, the same Msg1 resources are allocated to RedCap UEs and eMBB. eMBB, R17 RedCap, and R18 RedCap UEs all report their UE types in Message 3, making it easier for network device 110 to distinguish them.
[0246] For example, the third information includes 2 bits. For example, when the third information is in the first bit state, the third information instructs the second terminal device to receive the first data information. When the third information is in the second bit state, the third information instructs the third terminal device to receive the first data information. When the third information is in the third bit state, the third information instructs the fourth terminal device to receive the first data information. For example, a bit state of "00" for the third information indicates that the first data information is sent to an R17 RedCap UE, a bit state of "01" for the third information indicates that the first data information is sent to an R18 RedCap UE, and a bit state of "10" for the third information indicates that the third information is sent to an eMBB UE. For example, a bit state of "00" for the third information indicates that an R17 RedCap UE receives the first data information, a bit state of "01" for the third information indicates that an R18 RedCap UE receives the first data information, and a bit state of "10" for the third information indicates that an eMBB UE receives the first data information. For example, the fourth terminal device is an eMBB UE.
[0247] In one embodiment, the random access failure is a RAR reception failure.
[0248] For example, the terminal device 120 does not receive the RAR in response to the preamble sent by the terminal device 120 .
[0249] For example, the third information in the PDCCH of message 2 indicates that the terminal device 120 does not receive the PDSCH of message 2, or indicates that the PDSCH of message 2 does not include the RAR of the terminal device 120, or indicates that the random access of the terminal device 120 fails.
[0250] For example, the third information is carried in the reserved field. For example, the terminal device 120 parses the second control information, the second control information includes the third information, and does not include the reserved field. The terminal device 130 parses the second control information, the second control information does not include the third information, and includes the reserved field. For example, the terminal device 120 parses the second control information, the second control information includes the third information, the second control information includes the reserved field, and the number of bits of the reserved field is A1. The terminal device 130 parses the second control information, the second control information does not include the third information, the second control information includes the reserved field, and the number of bits of the reserved field is A2. Wherein, A1 is an integer, A2 is an integer, and A1 is less than A2.
[0251] For example, the network device 110 distinguishes between R17 RedCap and R18 RedCap UE types in Message 1, that is, allocates different Message 1 resources to R17 RedCap UE and R18 RedCap UE.
[0252] 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 the UE type corresponding to one or more RARs.
[0253] For example, the bit state of the third information is "1" indicating that the first data information is sent to the R17 RedCap UE, and the bit state of the third information is "0" indicating that the first data information is sent to the R18 RedCap UE. For example, the bit state of the third information is "1" indicating that the R17 RedCap UE receives the first data information, and the bit state of the third information is "0" indicating that the R18 RedCap UE receives the first data information.
[0254] In summary, the terminal device 120 does not need to receive the PDSCH before determining that the random access contention has failed. Instead, it can determine that the contention has failed after reading the PDCCH in the message 4, thus avoiding wasting power by continuing to receive and process the PDSCH. The random access process can be re-initiated as soon as possible, thus shortening the random access delay.
[0255] The above describes the method embodiment of the embodiment of the present application, and the corresponding device embodiment is introduced below.
[0256] To implement the various functions of the methods provided herein, terminals and network devices may include hardware structures and / or software modules, and the aforementioned functions may be implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.
[0257] Figure 5 is a schematic block diagram of a communication device 500 according to an embodiment of the present application. The communication device 500 includes a processor 510 and a communication interface 520, which may be interconnected via a bus 530. The communication device 500 shown in Figure 5 may be a network device 110 or a terminal device 120.
[0258] Optionally, the communication device 500 further includes a memory 540 .
[0259] The memory 540 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), and is used for related instructions and data.
[0260] The processor 510 may be one or more central processing units (CPUs). In the case where the processor 510 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.
[0261] When the communication device 500 is a terminal device 120, exemplarily, the processor 510 is used to perform the following operations: sending uplink information 1 within resource 1; after sending the uplink information 1, receiving PDCCH1 carrying downlink control information 1, PDCCH1 is used to schedule downlink information 1, and uplink information 1 and downlink information 1 are information in the random access process; decoding PDCCH1; if PDCCH1 is successfully decoded, determining whether to operate downlink information 1 according to downlink control information 1; or, determining whether to continue the current random access process according to downlink control information 1; or, receiving downlink information 1, and determining the starting time of PUCCH1 for response feedback to downlink information 1, and the minimum time interval between the end time of downlink information 1 and the starting time of PUCCH1 transmission.
[0262] The above contents are merely exemplary descriptions. When the communication apparatus 500 is the terminal device 120, it will be responsible for executing the methods or steps related to the terminal device 120 in the above method embodiments.
[0263] When the communication device 500 is a network device 110, exemplarily, the processor 510 is used to perform the following operations: receive uplink information 1, which is information in a random access process; send PDCCH1 carrying downlink control information 1, which is used to schedule downlink information 1, which is information in a random access process; wherein PDCCH1 is used by the terminal device 120 to determine whether it is necessary to operate downlink information 1, or PDCCH1 is used by the terminal device 120 to determine whether to continue the current random access process, etc.
[0264] The above contents are merely exemplary descriptions. When the communication apparatus 500 is the network device 110, it will be responsible for executing the methods or steps related to the network device 110 in the above method embodiments.
[0265] The above description is merely exemplary. For details, please refer to the contents shown in the above method embodiment. In addition, the implementation of each operation in FIG5 may also correspond to the corresponding description of the method embodiment shown in FIG3 to FIG4.
[0266] Figure 6 is a schematic block diagram of a communication device 600 according to an embodiment of the present application. Communication device 600 may be the network device 110 or terminal device 120 described in the aforementioned embodiments, or may be a chip or module within network device 110 or terminal device 120, configured to implement the methods described in the aforementioned embodiments. Communication device 600 includes a transceiver unit 610 and a processing unit 620. The following provides an exemplary description of transceiver unit 610 and processing unit 620.
[0267] The transceiver unit 610 may include a sending unit and a receiving unit, which are respectively used to implement the sending or receiving functions in the above method embodiments; it may further include a processing unit, which is used to implement functions other than sending or receiving.
[0268] When the communication apparatus 600 is a terminal device 120, illustratively, the transceiver unit 610 is configured to transmit uplink information 1 within resource 1; after transmitting uplink information 1, receive PDCCH1 carrying downlink control information 1, PDCCH1 being used to schedule downlink information 1, and uplink information 1 and downlink information 1 being information in a random access process. The processing unit 620 is configured to decode PDCCH1; if PDCCH1 is successfully decoded, determine whether to operate downlink information 1 based on downlink control information 1; or, determine whether to continue the current random access process based on downlink control information 1; or, determine the start time of PUCCH1 for response feedback to downlink information 1, and the minimum time interval between the end time of downlink information 1 and the start time of PUCCH1 transmission.
[0269] Optionally, the processing unit 620 is further configured to execute the contents of steps involving processing and coordination of the terminal device 120 .
[0270] Optionally, the communication device 600 further includes a storage unit 630, and the storage unit 630 is used to store a program or code for executing the aforementioned method.
[0271] The above contents are merely exemplary descriptions. When the communication apparatus 600 is the terminal device 120, it will be responsible for executing the methods or steps related to the terminal device 120 in the above method embodiments.
[0272] When the communication device 600 is a network device 110, illustratively, the transceiver unit 610 is used to receive uplink information 1, which is information in a random access process; and to send PDCCH1 carrying downlink control information 1, which is used to schedule downlink information 1, which is information in a random access process; wherein PDCCH1 is used by the terminal device 120 to determine whether it is necessary to operate downlink information 1, or PDCCH1 is used by the terminal device 120 to determine whether to continue the current random access process, etc.
[0273] Optionally, the communication apparatus 600 may further include a processing unit 620 configured to execute steps related to processing and coordination of the network device 110 .
[0274] Optionally, the communication device 600 further includes a storage unit 630, which is used to store a program or code for executing the aforementioned method.
[0275] The above contents are merely exemplary descriptions. When the communication apparatus 600 is the network device 110, it will be responsible for executing the methods or steps related to the network device 110 in the above method embodiments.
[0276] In addition, the implementation of each operation in FIG6 may also refer to the corresponding description of the method shown in the above embodiment, which will not be repeated here.
[0277] The device embodiments shown in Figures 5 and 6 are used to implement the contents described in the aforementioned method embodiments in Figures 3 to 4. Therefore, the specific execution steps and methods of the devices shown in Figures 5 and 6 can refer to the contents described in the aforementioned method embodiments.
[0278] It should be understood that the aforementioned transceiver unit may include a transmitting unit and a receiving unit. The transmitting unit is used to perform the transmitting operation of the communication device, and the receiving unit is used to perform the receiving operation of the communication device. For ease of description, the embodiments of the present application combine the transmitting unit and the receiving unit into a single transceiver unit. This is described here as a unified description and will not be repeated later.
[0279] Figure 7 is a schematic block diagram of a communication device 700 according to an embodiment of the present application. The communication device 700 can be used to implement the functions of the network device 110 or the terminal device 120 in the above method. The communication device 700 can be a chip in the network device 110 or the terminal device 120.
[0280] 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, a chip, or other integrated circuit capable of implementing the method of the present application. The input / output interface 720 is used for inputting or outputting signals or data.
[0281] For example, when the communication device 700 is a terminal device 120, the input / output interface 720 is used to send uplink information 1 within resource 1; after sending uplink information 1, receive PDCCH1 carrying downlink control information 1, PDCCH1 is used to schedule downlink information 1, and uplink information 1 and downlink information 1 are information in the random access process. The processor 710 can be used to decode PDCCH1; if PDCCH1 is successfully decoded, determine whether to operate downlink information 1 based on downlink control information 1; or, determine whether to continue the current random access process based on downlink control information 1; or, receive downlink information 1, and determine the start time of PUCCH1 for response feedback to downlink information 1, and receive information 1 from the network device 110 with a minimum time interval between the end time of downlink information 1 and the start time of PUCCH1 transmission. The processor 710 is also used to perform some or all of the steps of any one of the methods provided in this application.
[0282] For example, when the communication device 700 is a network device 110, the input / output interface 720 is configured to receive uplink information 1, which is information during a random access process; and transmit PDCCH1 carrying downlink control information 1, which is used to schedule downlink information 1, which is information during a random access process. PDCCH1 is used by the terminal device 120 to determine whether to operate on downlink information 1, or to determine whether to continue the current random access process. The processor 710 is further configured to execute some or all of the steps of any one of the methods provided herein.
[0283] In one possible implementation, the processor 710 implements the functions implemented by the network device or the terminal device by executing instructions stored in the memory.
[0284] Optionally, the communication device 700 further includes a memory.
[0285] Optionally, the processor and memory are integrated together.
[0286] Optionally, the memory is outside the communication device 700 .
[0287] In one possible implementation, the processor 710 may be a logic circuit, which inputs / outputs messages or signals through the input / output interface 720. The logic circuit may be a signal processor, a chip, or other integrated circuit that can implement the method of the embodiment of the present application.
[0288] The above description of the device in FIG. 7 is merely an exemplary description. The device can be used to execute the method described in the above embodiment. For details, please refer to the description of the above method embodiment, which will not be repeated here.
[0289] FIG8 is a schematic block diagram of a communication device 800 according to an embodiment of the present application. The communication device 800 may be a network device 110 or a chip. The communication device 800 may be used to perform the operations performed by the network device 110 in the method embodiments shown in FIG5 to FIG11 .
[0290] When communication device 800 is network device 110, for example, it is a base station. Figure 8 shows a simplified schematic diagram of the base station structure. The base station includes sections 810, 820, and 830. Section 810 is primarily responsible for baseband processing and base station control. Section 810 is typically the base station's control center, often referred to as a processor, and is used to control the base station to execute network device-side processing operations in the above-described method embodiments. Section 820 is primarily responsible for storing computer program code and data. Section 830 is primarily responsible for transmitting and receiving radio frequency signals and converting radio frequency signals into baseband signals. Section 830 can often be referred to as a transceiver module, transceiver, transceiver circuit, or transceiver. The transceiver module in section 1730, also referred to as a transceiver or transceiver, includes an antenna 833 and radio frequency circuitry (not shown in Figure 8), with the radio frequency circuitry primarily responsible for radio frequency processing. Optionally, the components in section 830 that implement the receiving function can be considered a receiver, and the components that implement the transmitting function can be considered a transmitter. That is, section 830 includes a receiver 832 and a transmitter 831. A receiver may also be referred to as a receiving module, a receiver, or a receiving circuit, etc., and a transmitter may be referred to as a transmitting module, a transmitter, or a transmitting circuit, etc.
[0291] Sections 810 and 820 may include one or more boards, each of which may include one or more processors and one or more memories. The processor is used to read and execute programs in the memory to implement baseband processing functions and control the base station. If multiple boards are present, the boards may be interconnected to enhance processing capabilities. As an optional implementation, multiple boards may share one or more processors, multiple boards may share one or more memories, or multiple boards may simultaneously share one or more processors.
[0292] For example, in one implementation, the transceiver module in section 830 is used to execute the transceiver-related processes performed by the network device in the embodiments shown in Figures 3 and 4. The processor in section 810 is used to execute the processing-related processes performed by the network device in the embodiments shown in Figures 3 and 4.
[0293] In another implementation, the processor in part 810 is used to execute processes related to the processing performed by the communication device in the embodiments shown in Figures 3 and 4.
[0294] In another implementation, the transceiver module in part 830 is used to execute the transceiver-related processes performed by the communication device in the embodiments shown in Figures 3 to 4.
[0295] It should be understood that FIG8 is merely an example and not a limitation, and the network device including the processor, memory, and transceiver described above may not rely on the structures shown in FIG5 to FIG7.
[0296] When communication device 800 is a chip, the chip includes a transceiver, memory, and a processor. The transceiver can be an input / output circuit or a communication interface; the processor can be a processor, microprocessor, or integrated circuit integrated on the chip. The network device's sending operation in the above method embodiment can be understood as the chip's output, and the network device's receiving operation in the above method embodiment can be understood as the chip's input.
[0297] Figure 9 is a schematic 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, a processor of the terminal device 120, or a chip. The communication device 900 may be used to perform the operations performed by the terminal device 120 or the communication device in the above method embodiments.
[0298] When the communication device 900 is a terminal device 120, FIG9 shows a simplified schematic diagram of the terminal device structure. As shown in FIG9, the terminal device includes a processor, a memory, and a transceiver. The memory can store computer program code, and the transceiver includes a transmitter 931, a receiver 932, a radio frequency circuit (not shown in FIG9), an antenna 933, and input / output devices (not shown in FIG9).
[0299] The processor is primarily used to process communication protocols and communication data, control terminal devices, execute software programs, and process software program data. Memory is primarily used to store software programs and data. Radio frequency circuits are primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. Antennas are primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input / output devices. For example, touch screens, displays, and keyboards are primarily used to receive user input and output data to the user. It should be noted that some types of terminal devices may not have input / output devices.
[0300] When data needs to be sent, the processor performs baseband processing on the data to be sent, and then outputs the baseband signal to the RF circuit. The RF circuit performs RF processing on the baseband signal and then sends the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the terminal device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data. For ease of explanation, Figure 9 shows only one memory, processor, and transceiver. In an actual terminal device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device, etc. The memory may be set independently of the processor or integrated with the processor. This is not limited in the embodiments of the present application.
[0301] In the embodiment of the present application, the antenna and radio frequency circuit with transceiver functions can be regarded as the transceiver module of the terminal device, and the processor with processing function can be regarded as the processing module of the terminal device.
[0302] As shown in Figure 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., and the transceiver 930 may also be referred to as a transceiver unit, a transceiver, a transceiver device, etc.
[0303] Alternatively, the device implementing the receiving function in transceiver 930 may be considered a receiving module, and the device implementing the transmitting function in transceiver 930 may be considered a transmitting module. That is, transceiver 930 includes a receiver and a transmitter. A transceiver may also be sometimes referred to as a transceiver, a transceiver module, or a transceiver circuit. A receiver may also be sometimes referred to as a receiver, a receiving module, or a receiving circuit. A transmitter may also be sometimes referred to as a transmitter, a transmitting module, or a transmitting circuit.
[0304] For example, in one implementation, the processor 910 is used to perform the processing actions on the terminal device side in the embodiments shown in Figures 3 to 4, and the transceiver 930 is used to perform the transceiver actions on the terminal device side in Figures 3 to 4.
[0305] For example, in one implementation, the processor 910 is used to perform the processing actions on the terminal device side in the embodiments shown in Figures 3 to 4, and the transceiver 930 is used to perform the transceiver actions on the terminal device side in Figures 3 to 4.
[0306] It should be understood that FIG9 is merely an example and not a limitation, and the above-mentioned terminal device including the transceiver module and the processing module may not rely on the structures shown in FIG5 to FIG7.
[0307] When the communication device 900 is a chip, the chip includes a processor, memory, and a transceiver. The transceiver can be an input / output circuit or a communication interface; the processor can be a processing module, microprocessor, or integrated circuit integrated on the chip. The sending operation of the terminal device in the above method embodiment can be understood as the chip's output, and the receiving operation of the terminal device in the above method embodiment can be understood as the chip's input.
[0308] The present application also provides a chip, including a processor, for calling and executing instructions stored in a memory from the memory, so that a communication device equipped with the chip executes the methods in the above examples.
[0309] The present application also provides another chip, comprising: an input interface, an output interface, and a processor, wherein the input interface, the output interface, and the processor are connected via an internal connection path, and the processor is configured to execute code in a memory. When the code is executed, the processor is configured to execute the methods in the above examples. Optionally, the chip also includes a memory, which is configured to store computer programs or code.
[0310] The present application also provides a processor for coupling with a memory, and for executing the methods and functions involving a network device or a terminal device in any of the above embodiments.
[0311] In another embodiment of the present application, a computer program product including instructions is provided. When the computer program product is run on a computer, the method of the above embodiment is implemented.
[0312] The present application also provides a computer program. When the computer program is executed in a computer, the method of the aforementioned embodiment is implemented.
[0313] In another embodiment of the present application, a computer-readable storage medium is provided, which stores a computer program. When the computer program is executed by a computer, the method described in the above embodiment is implemented.
[0314] In the description of the embodiments of this application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or plural.
[0315] In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit differences. At the same time, in the embodiments of the present application, words such as "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations.
[0316] Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.
[0317] In the description of the embodiments of the present application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in the present application is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.
[0318] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0319] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0320] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0321] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of units is merely a logical functional division. In actual implementation, other division methods may be used, such as combining or integrating multiple units or components into another system, or ignoring or not implementing certain features.
[0322] On the other hand, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, which may be electrical, mechanical or other forms.
[0323] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0324] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist physically separately, or two or more units may be integrated into one unit.
[0325] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
[0326] The above is only a specific implementation of the embodiment of the present application, but the scope of protection of the embodiment of the present application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the embodiment of the present application, and they should be included in the scope of protection of the embodiment of the present application. Therefore, the scope of protection of the embodiment of the present application should be based on the scope of protection of the claims.
Claims
1. A communication method, characterized in that: include: The terminal device sends uplink information in the first resource; After sending the uplink information, the terminal device receives a physical downlink control channel PDCCH carrying downlink control information, the PDCCH is used to schedule downlink information, and the uplink information and the downlink information are information in a random access process; The terminal device decodes the PDCCH; If the terminal device successfully decodes the PDCCH, The terminal device determines whether to operate the downlink information according to the downlink control information; or, The terminal device determines whether to continue the current random access process according to the downlink control information; or, The terminal device receives the downlink information, and The terminal device determines the starting time of the physical uplink control channel PUCCH for the downlink information response feedback, and the end time of the downlink information and the starting time of the PUCCH sending meet the minimum time interval.
2. The method according to claim 1, characterized in that: The uplink information is a physical uplink shared channel PUSCH 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.
3. The method according to claim 1 or 2, characterized in that: The downlink control information includes a frequency domain resource allocation FDRA field, and the FDRA field is used to allocate resource blocks for the downlink information transmission; The number of the allocated resource blocks exceeds a first threshold, and the terminal device does not operate the downlink information; or, The number of the allocated resource blocks exceeds a first threshold, the terminal device does not operate the downlink information, and the first terminal device determines that the random access has failed; or, The number of the allocated resource blocks exceeds a first threshold, and the terminal device does not continue the current random access process; or, The number of the allocated resource blocks exceeds a first threshold, the terminal device does not continue the current random access process, and the first terminal device determines that the current random access has failed; or, The number of allocated resource blocks exceeds a 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 numerical value, and the first numerical value is greater than 0.
4. The method according to claim 1, characterized in that The downlink control information includes a FDRA field, and the FDRA field is used to allocate resource blocks for the downlink information transmission; The number of the allocated resource blocks does not exceed a first threshold, and the terminal device operates the downlink information; or, The number of the allocated resource blocks does not exceed the first threshold, and the terminal device continues the current random access process; or, The number of allocated resource blocks does not exceed a first threshold, and the terminal device determines that the minimum time interval is equal to a first time interval.
5. The method according to claim 1, characterized in that: The downlink control information includes time indication information, and the time indication information is used to determine the time unit for sending the PUCCH; The time interval between the end time of the downlink information and the start time of the PUCCH transmission is less than a second threshold, and the terminal device does not operate the downlink information; or, The time interval between the end time of the downlink information and the start time of the PUCCH transmission is less than the second threshold, the terminal device does not operate the downlink information, and the terminal device determines that this random access fails; or, The time interval between the end time of the downlink information and the start time of the PUCCH transmission is less than the second threshold, and the terminal device does not continue the current random access process; or, If the time interval between the end time of the downlink information and the start time of the PUCCH sending is less than a second threshold, the terminal device does not continue the current random access process, and the terminal device determines that this random access has failed.
6. The method according to claim 1, characterized in that The downlink control information includes time indication information, and the time indication information is used to determine the time unit for sending the PUCCH; The time interval between the end time of the downlink information and the start time of the PUCCH transmission is not less than a second threshold, and the terminal device determines to operate the downlink information; or, The time interval between the end time of the downlink information and the start time of the PUCCH sending is not less than a second threshold, and the terminal device determines to continue the current random access process.
7. The method according to claim 1, characterized in that The downlink control information includes first indication information, and the first indication information is used to instruct a terminal device having a first characteristic parameter to operate the downlink information.
8. The method according to claim 7, characterized in that The characteristic parameter of the terminal device is not the first characteristic parameter, and the terminal device does not operate the downlink information; or, 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 this random access fails; or, The characteristic parameter of the terminal device is not the first characteristic parameter, and the terminal device does not continue the current random access process; or, The characteristic parameter of the terminal device is not the first characteristic parameter, the terminal device does not continue the current random access process, and the terminal device determines that the current random access has failed; or, The characteristic parameter of the terminal device is the first characteristic parameter, and the terminal device operates the downlink information.
9. The method according to claim 1, characterized in that: The terminal device reports the characteristic parameter via message 3; and / or, The maximum bandwidth of the unicast data transmission of the terminal device is not greater than 5 MHz, or the number of resource blocks used for the unicast data transmission of the terminal device is not greater than M; and / or, The maximum bandwidth of the unicast data processing of the terminal device is not greater than 5 MHz, or the number of resource blocks used for the unicast data processing of the terminal device is not greater than M; The M is a positive integer, or the value of the M corresponds to the subcarrier spacing.
10. A communication method, characterized in that: include: The network device receives uplink information, where the uplink information is information in a random access process; The network device sends a physical downlink control channel PDCCH that carries downlink control information, where the PDCCH is used to schedule downlink information, and the downlink information is information in a random access process; The PDCCH is used by the first terminal device to determine whether the downlink information needs to be operated, or the PDCCH is used by the first terminal device to determine whether to continue the current random access process.
11. The method according to claim 10, characterized in that The uplink information is a physical uplink shared channel PUSCH 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.
12. The method according to claim 11, characterized in that The downlink control information includes first indication information, and the first indication information is used to instruct a terminal device having a first characteristic parameter to operate the downlink information.
13. A communication device, characterized in that: comprising a processor configured to, by executing a computer program or instructions, or, by means of a logic circuit, causing the communication device to perform the method according to any one of claims 1 to 9; or The communication device is enabled to execute the method according to any one of claims 10 to 12.
14. The communication device according to claim 13, characterized in that: The communication device further comprises a memory for storing the computer program or instructions.
15. The communication device according to claim 13 or 14, characterized in that: The communication device further comprises a communication interface, and the communication interface is used for inputting and / or outputting signals.
16. A communication device, characterized in that: It includes a logic circuit and an input / output interface, wherein the input / output interface is used to input and / or output signals. The logic circuit is used to execute the method according to any one of claims 1 to 9; or The logic circuit is configured to execute the method according to any one of claims 10 to 12.
17. A computer-readable storage medium, characterized in that: The computer readable storage medium stores a computer program or instruction. When the computer program or instruction is executed on a computer, so that the method of any one of claims 1 to 9 is performed; or, The method according to any one of claims 10 to 12 is performed.
18. A computer program product, characterized in that Contains instructions that, when executed on a computer, so that the method of any one of claims 1 to 9 is performed; or, The method according to any one of claims 10 to 12 is performed.
19. A communication system, characterized in that: include: A first terminal device and a network device; The first terminal device is used to execute the method according to any one of claims 1 to 9, The network device is used to execute the method according to any one of claims 10 to 12.
