Random access method and apparatus

Abstract

The embodiment of the disclosure discloses a random access method and device, which can be applied to the technical field of communication. The method executed by a terminal device comprises: in response to that a contention resolution timer expires and a first condition is met in a contention-based random access, the terminal device determines that contention resolution is unsuccessful or is not considered to be unsuccessful. Thus, the terminal device can be prevented from determining that contention resolution is unsuccessful in error.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a random access method and apparatus. Background Technology

[0002] In a contention-based random access process, after the terminal device sends message Msg3 to the network-side device, it starts a contention resolution timer. During the execution of this contention resolution timer, the terminal device listens for Msg3 retransmission scheduling on the PDCCH (physical downlink control channel) based on TC-RNTI (temporary cell radionetwork temporary identifier) ​​addressing. After the contention resolution timer expires, the terminal device considers the contention resolution unsuccessful.

[0003] However, the contention resolution timer is restarted multiple times due to repeated retransmissions of Msg3. Before the contention resolution timer restarts, a previously started contention resolution timer may have already expired, at which point the terminal device will consider the contention to have failed. However, since the contention resolution timer is restarted upon receiving a retransmission of Msg3, the terminal device should not consider the contention to have failed in this case. This is a problem that urgently needs to be solved. Summary of the Invention

[0004] This disclosure provides a random access method and apparatus that can prevent terminal devices from mistakenly determining that the contention resolution has failed.

[0005] In a first aspect, embodiments of this disclosure provide a random access method, which is executed by a terminal device. The method includes: in response to a contention-based random access event, if a contention resolution timer times out and a first condition is met, determining that the contention resolution was unsuccessful or not considering the contention resolution as unsuccessful.

[0006] In this technical solution, in contention-based random access, if the contention resolution timer times out and the first condition is met, the terminal device determines that the contention resolution was unsuccessful or does not consider the contention resolution to have failed. This avoids the terminal device mistakenly determining that the contention resolution has failed.

[0007] Secondly, this disclosure provides another random access method, which is executed by a terminal device. The method includes: initiating random access by sending a random access message Msg3 to a network-side device; and, in response to the transmission of Msg3 in the NTN network, starting a listening timer after the initial transmission of Msg3.

[0008] Thirdly, embodiments of this disclosure provide a communication device that implements some or all of the functions of the terminal device described in the first aspect above. For example, the communication device may have the functions of some or all of the embodiments in this disclosure, or it may have the functions of any one embodiment in this disclosure implemented individually. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0009] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions described in the above method. The transceiver module supports communication between the communication device and other devices. The communication device may also include a storage module, coupled to the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.

[0010] In one implementation, the communication device includes a processing module configured to, in response to a contention-based random access event, if a contention resolution timer times out and a first condition is met, determine that the contention resolution was unsuccessful or not consider the contention resolution to have been unsuccessful.

[0011] Fourthly, embodiments of this disclosure provide another communication device that has some or all of the functions of the terminal device described in the method example of the second aspect above. For example, the communication device may have the functions of some or all of the embodiments in this disclosure, or it may have the functions of any one embodiment in this disclosure implemented individually. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0012] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions described in the above method. The transceiver module is used to support communication between the communication device and other devices. The communication device may also include a storage module, which is coupled to the transceiver module and the processing module, and stores the necessary computer programs and data of the communication device.

[0013] In one implementation, the communication device includes: a transceiver module configured to initiate random access and send a random access message Msg3 to a network-side device; and a processing module configured to start a listening timer after the initial transmission of Msg3 in response to the transmission of Msg3 in the NTN network.

[0014] Fifthly, embodiments of this disclosure provide a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the first aspect.

[0015] In a sixth aspect, embodiments of this disclosure provide a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the second aspect above.

[0016] In a seventh aspect, embodiments of this disclosure provide a communication device including a processor and a memory, the memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the first aspect above.

[0017] Eighthly, embodiments of this disclosure provide a communication device including a processor and a memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the second aspect above.

[0018] Ninthly, embodiments of this disclosure provide a communication device including a processor and an interface circuit. The interface circuit is configured to receive code instructions and transmit them to the processor, which is configured to execute the code instructions to cause the device to perform the method described in the first aspect above.

[0019] In a tenth aspect, embodiments of this disclosure provide a communication device including a processor and an interface circuit. The interface circuit is configured to receive code instructions and transmit them to the processor, which is configured to execute the code instructions to cause the device to perform the method described in the second aspect above.

[0020] Eleventhly, embodiments of this disclosure provide a random access system, the system including the communication device described in the third aspect and the communication device described in the fourth aspect, or the system including the communication device described in the fifth aspect and the communication device described in the sixth aspect, or the system including the communication device described in the seventh aspect and the communication device described in the eighth aspect, or the system including the communication device described in the ninth aspect and the communication device described in the tenth aspect.

[0021] In a twelfth aspect, embodiments of the present invention provide a computer-readable storage medium for storing instructions for use by the aforementioned terminal device, which, when executed, cause the terminal device to perform the method described in the first aspect.

[0022] In a thirteenth aspect, embodiments of the present invention provide a readable storage medium for storing instructions for use by the aforementioned terminal device, which, when executed, cause the terminal device to perform the method described in the second aspect.

[0023] In a fourteenth aspect, this disclosure also provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect above.

[0024] In a fifteenth aspect, this disclosure also provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the method described in the second aspect above.

[0025] In a sixteenth aspect, this disclosure provides a chip system including at least one processor and an interface for supporting a terminal device in implementing the functions involved in the first aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the terminal device. The chip system may be composed of chips or may include chips and other discrete devices.

[0026] In a seventeenth aspect, this disclosure provides a chip system including at least one processor and an interface for supporting a terminal device in implementing the functions involved in the second aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the terminal device. The chip system may be composed of chips or may include chips and other discrete devices.

[0027] In an eighteenth aspect, this disclosure provides a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect above.

[0028] In a nineteenth aspect, this disclosure provides a computer program that, when run on a computer, causes the computer to perform the method described in the second aspect above. Attached Figure Description

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

[0030] Figure 1 This is a schematic diagram of an NTN communication method provided in an embodiment of this disclosure;

[0031] Figure 2 This is a schematic diagram of another NTN communication method provided in an embodiment of this disclosure;

[0032] Figure 3 This is a schematic diagram of another NTN communication method provided in the embodiments of this disclosure;

[0033] Figure 4 This is an architecture diagram of a communication system provided in an embodiment of this disclosure;

[0034] Figure 5 This is a flowchart of a random access method provided in an embodiment of this disclosure;

[0035] Figure 6 This is a flowchart of another random access method provided in this disclosure embodiment;

[0036] Figure 7 This is a flowchart of yet another random access method provided in this disclosure embodiment;

[0037] Figure 8 This is a flowchart of yet another random access method provided in this disclosure embodiment;

[0038] Figure 9 This is a structural diagram of a communication device provided in an embodiment of this disclosure;

[0039] Figure 10 This is a structural diagram of another communication device provided in an embodiment of this disclosure;

[0040] Figure 11 This is a schematic diagram of the structure of a chip provided in an embodiment of this disclosure. Detailed Implementation

[0041] To facilitate understanding of this disclosure, some concepts involved in the embodiments of this disclosure are briefly introduced herein.

[0042] 1. Random Access (RA)

[0043] The random access procedure refers to the process from when the user (terminal device) sends a random access preamble to attempt to access the network (network-side equipment) until a basic signaling connection is established with the network. Random access is a crucial step in mobile communication systems and the final step in establishing a communication link between the terminal device and the network-side equipment. The terminal device can exchange information with the network-side equipment through random access. The random access procedure can include two-step random access and four-step random access.

[0044] The four-step random access process includes: the terminal device sending a preamble via message msg1; the network device sending a Random Access Response (RAR) via message msg2; the terminal device sending a Radio Resource Control (RRC) connection request via message msg3; and the terminal device receiving the RRC connection establishment via message msg4 (this process is also known as the contention resolution process).

[0045] The two-step random access process includes: the terminal device sending message A (msgA) to the network device, and the network device sending message B (msgB) to the terminal device. msgA contains content equivalent to msg1 and msg3 in the four-step random access process; msgB contains content equivalent to msg2 and msg4 in the four-step random access process.

[0046] The third message (msg3)

[0047] The third message in the 4-step random access process is called Msg3. The content of Msg3 may vary depending on the terminal device's status and the application scenario. Msg3 must contain an important piece of information: a unique identifier for each terminal device, which will be used to resolve the contention in the fourth step of the 4-step random access process.

[0048] In contention-based random access, after sending msg3, the terminal device starts a contention resolution timer. During this timer's operation, the terminal device listens for msg3 retransmission scheduling or msg4 scheduling via TC-RNTI addressing on the PDCCH. If the contention resolution timer expires, the terminal device considers the contention resolution unsuccessful.

[0049] 2. NTN (non-terrestrial networks) communication methods, for example Figure 1 As shown.

[0050] Depending on how the satellite processes the signal, NTN communication can be divided into transparent transmission mode and regeneration mode.

[0051] Among them, the pass-through mode is as follows Figure 2 As shown, the NTN ground station sends the base station signal to the satellite, which then converts the signal to the satellite frequency band and transmits it to the terminal (terminal equipment) via the satellite frequency band. Apart from frequency conversion and signal amplification, the satellite does not demodulate the base station signal.

[0052] Regeneration mode such as Figure 3As shown, after the NTN ground station sends the base station signal to the satellite, the satellite first demodulates and decodes the signal, then re-encodes and modulates it, and then transmits the regenerated signal through the satellite frequency band.

[0053] Table 1 below shows the satellite altitude, orbit, and coverage area of ​​a typical NTN network:

[0054]

[0055] Table 1

[0056] For NTN, the contention resolution timer is started after msg3 is sent and then after the RTT (Round-Trip Time).

[0057] 3. Scrambling

[0058] Scrambling is a digital signal processing method that uses a scrambling code to perform an XOR operation with the original signal to obtain a new signal. Typically, uplink physical channel scrambling distinguishes different terminal devices, while downlink scrambling distinguishes cells and channels. Scrambling codes can be used to scramble and descramble the original signal. For example, scrambling codes can scramble downlink control information (DCI), also known as PDCCH scrambling. Specifically, DCI scrambling refers to scrambling the cyclic redundancy check (CRC) field of the DCI. Correspondingly, the terminal device descrambles the received DCI, specifically by using an appropriate type of scrambling code to descramble the CRC field of the DCI to determine its format or type.

[0059] Scrambling codes may include, but are not limited to: cell radio network temporary identifier (C-RNTI), temporary cell radio network temporary identifier (TC-RNTI), random access radio network temporary identifier (RA-RNTI), system information radio network temporary identifier (SI-RNTI), and paging radio network temporary identifier (P-RNTI).

[0060] a) C-RNTI and TC-RNTI

[0061] If the terminal device is in the radio resource control connected (RRC-connected) state, it means that the terminal device has been assigned a C-RNTI, and the terminal device needs to include this C-RNTI when initiating a random access request to the network-side device. If the terminal device is in the RRC idle or RRC inactive state, it means that the terminal device has not yet been assigned a C-RNTI. If the terminal device requests an RRC connection, the network-side device may assign a temporary C-RNTI to the terminal device in the subsequent response information, denoted as TC-RNTI. After the terminal device successfully accesses the network, the TC-RNTI can be converted into a C-RNTI.

[0062] b)RA-RNTI

[0063] In the random access procedure, the generation of RA-RNTI is related to the time-frequency resources used by the terminal device to send the preamble. For example, when terminal device A and terminal device B initiate random access using the same random access channel time-frequency resources, their corresponding RA-RNTIs are the same.

[0064] 4. PUSCH (physical uplink share channel) mapping type

[0065] PUSCH includes two mapping types: Type A and Type B. A mapping type can be understood as a resource allocation type. In NR communication standards, both Type A and Type B indicate the start symbol (identified as S), the symbol length (identified as L), and the possible range of values ​​for S+L. For example, Table 6.1.2.1-1 (referred to as Table 2 in this disclosure) in section 6.1.2.1 of the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.214 shows valid S and L conbinations under Type A and Type B.

[0066] Table 2 below: Valid combinations of S and L

[0067]

[0068] Table 2

[0069] Specifically, the parameters in the Type A row only apply to repetitions of Type A. The "{1,…,14}" and "{1,…,12}" in the S+L column of the Type B row apply to repetitions of Type A, while the "{1,…,27}" and "{1,…,23}" in the S+L column of the Type B row apply to repetitions of Type B.

[0070] 5. Repeated transmission of PUSCH

[0071] Repeated transmission of a PUSCH refers to transmitting multiple PUSCHs, each representing multiple identical uplink data. Transmitting a single PUSCH (i.e., one piece of uplink data) can be considered a single repeated transmission of the PUSCH. Multiple identical uplink data refers to multiple identical or different RVs (redundancy versions) obtained after channel coding of the same set of system bits.

[0072] For Type B, the communication standard introduces the parameter "numberOfRepetitions-r16" to configure the number of repetitions. numberOfRepetitions-r16 has eight configurable values, indicated by 3 bits. These 3 bits correspond to {n1, n2, n3, n4, n7, n8, n12, n16}, where the value after n indicates the number of repetitions. For example, n1 indicates one transmission, and n16 indicates 16 transmissions. Network devices can configure one of these eight configurable values ​​for terminal devices via higher-layer signaling, such as RRC signaling, thereby indicating the number of repetitions to the terminal device. For Type B, starting from the start symbol S in the initial time slot of the repetitive PUSCH transmission, L*numberOfRepetitions-r16 available symbols are all used for the repetitive transmission of PUSCH. In this application, "*" means "multiplied".

[0073] For Type A, S+L is less than or equal to 14. When the terminal device is configured with a repetition count (let's say R1), the terminal device will perform a check in each of the R1 time slots (R1 consecutive time slots starting from the start time slot). If all L symbols starting from the start symbol S in a certain time slot are available symbols, then PUSCH will be sent in that time slot; otherwise, PUSCH will not be sent in that time slot, and the device will continue to check if other time slots meet the conditions.

[0074] To better understand the random access method and apparatus disclosed in this disclosure, the communication system to which this disclosure applies will be described first.

[0075] Please see Figure 4 , Figure 4 This is a schematic diagram of the architecture of a communication system provided in an embodiment of the present disclosure. The communication system may include, but is not limited to, a network-side device and a terminal device. Figure 4 The number and form of devices shown are for illustrative purposes only and do not constitute a limitation on the embodiments of this disclosure. In actual applications, there may be two or more network-side devices and two or more terminal devices. Figure 4 The communication system 10 shown is exemplified by including a network-side device 101 and a terminal device 102.

[0076] It should be noted that the technical solutions of this disclosure can be applied to various communication systems. For example, Long Term Evolution (LTE) systems, 5th Generation (5G) mobile communication systems, 5G New Radio (NR) systems, or other future new mobile communication systems. It should also be noted that the side link in this disclosure can also be referred to as a side link or a direct link.

[0077] The network-side device 101 in this embodiment is a network-side entity used for transmitting or receiving signals. For example, the network-side device 101 can be an evolved NodeB (eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. This disclosure does not limit the specific technology or device form used in the base station. The base station provided in this disclosure can be composed of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. Using a CU-DU structure, the base station, for example, can have its protocol layer separated. Some protocol layer functions are centrally controlled by the CU, while the remaining or all protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0078] The terminal device 102 in this disclosure is a user-side entity used to receive or transmit signals, such as a mobile phone. The terminal device can also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device can be a car with communication capabilities, a smart car, a mobile phone, a wearable device, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, etc. This disclosure does not limit the specific technology or device form used in the terminal device.

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

[0080] The random access method and apparatus provided in this disclosure will now be described in detail with reference to the accompanying drawings.

[0081] Please see Figure 5 , Figure 5 This is a flowchart of a random access method provided in an embodiment of this disclosure.

[0082] like Figure 5 As shown, this method is executed by a terminal device, and the method may include, but is not limited to, the following steps:

[0083] S51: In response to a contention-based random access event, if the contention resolution timer times out and the first condition is met, determine that the contention resolution was unsuccessful or do not consider the contention resolution to have failed.

[0084] In some embodiments, the terminal device performs a contention-based random access procedure by sending a contention-based random access request to the network-side device, wherein the random access request includes the message Msg3.

[0085] In this embodiment of the disclosure, the terminal device performs a contention-based random access procedure. After the terminal device sends message Msg3 to the network-side device, it starts a contention resolution timer (ra-ContentionResolutionTimer). During the operation of the contention resolution timer, the terminal device listens to the retransmission scheduling of Msg3 or message Msg4 on the PDCCH (physical downlink control channel) based on TC-RNTI (temporary cell radio network temporary identifier). After the contention resolution timer expires, and if the first condition is met, it is determined that the contention resolution was unsuccessful, or it is determined that the contention resolution was not considered unsuccessful.

[0086] The first condition can be either a condition determining that the contention resolution failed, or a condition determining that the contention resolution was not considered unsuccessful. Therefore, determining whether the contention resolution was successful based on the first condition can prevent the terminal device from mistakenly determining that the contention resolution failed.

[0087] In some embodiments, the first condition includes at least one of the following:

[0088] Msg3 was transmitted in the non-terrestrial network NTN network, and in the last start before the contention resolution timer expired, no Msg3 retransmission scheduled based on the temporary cell radio network temporary identifier TC-RNTI was received on the physical downlink control channel PDCCH.

[0089] Msg3 is transmitted in the NTN network, and the contention resolution timer is started after the round-trip time (RTT) after Msg3 is sent. In the last start before the contention resolution timer expires, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH.

[0090] Msg3 is transmitted in the NTN network, and the contention resolution timer is started after the RTT following the transmission of Msg3. After the contention resolution timer is started, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH.

[0091] When Msg3 is transmitted in the NTN network, the contention resolution timer will not be started, and in the last start before the contention resolution timer expires, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH.

[0092] When Msg3 is transmitted in the NTN network, the contention resolution timer will not be started, and after the contention resolution timer is started, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH.

[0093] In this embodiment of the disclosure, the first condition can be that Msg3 is transmitted in a non-terrestrial network (NTN), and in the last startup before the contention resolution timer expires, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH. In contention-based random access, if the contention resolution timer expires and the above first condition is met, the terminal device determines that the contention resolution was unsuccessful or does not consider the contention resolution to have failed, thus avoiding the terminal device's erroneous determination that the contention resolution has failed.

[0094] In this embodiment of the disclosure, the first condition can be that Msg3 is transmitted in the NTN network, and the contention resolution timer is started after the round-trip time (RTT) following the transmission of Msg3, and the last start before the contention resolution timer expires does not receive a Msg3 retransmission based on TC-RNTI scheduling on the PDCCH; if the contention resolution timer expires in contention-based random access and the above first condition is met, the terminal device determines that the contention resolution was unsuccessful or does not consider the contention resolution to be unsuccessful, which can avoid the terminal device mistakenly determining that the contention resolution has failed.

[0095] In this embodiment of the disclosure, the first condition can be that Msg3 is transmitted in the NTN network, and the contention resolution timer is started after the RTT following the transmission of Msg3, and after the contention resolution timer is started, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH; if the contention resolution timer times out in contention-based random access and the above first condition is met, the terminal device determines that the contention resolution was unsuccessful or does not consider the contention resolution to be unsuccessful, which can avoid the terminal device mistakenly determining that the contention resolution has failed.

[0096] In this embodiment of the disclosure, the first condition can be that Msg3 is transmitted in the NTN network, the contention resolution timer will not be started, and the last start before the contention resolution timer expires does not receive a Msg3 retransmission based on TC-RNTI scheduling on the PDCCH; if the contention resolution timer expires in contention-based random access and the above first condition is met, the terminal device determines that the contention resolution has failed or does not consider the contention resolution to have failed, which can avoid the terminal device mistakenly determining that the contention resolution has failed.

[0097] In this embodiment of the disclosure, the first condition can be that Msg3 is transmitted in the NTN network, the contention resolution timer will not be started, and after the contention resolution timer is started, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH. In contention-based random access, if the contention resolution timer times out and the above first condition is met, the terminal device determines that the contention resolution was unsuccessful or does not consider the contention resolution to be unsuccessful, thus avoiding the terminal device's erroneous determination that the contention resolution has failed.

[0098] The last start before the contention resolution timer expires can be initiated after the terminal device sends Msg3. After receiving at least one Msg3 retransmission based on TC-RNTI scheduling on the PDCCH, the terminal device will send Msg3 again after receiving the Msg3 retransmission schedule, and then start the contention resolution timer again. When the contention resolution timer is started this time, the previously started contention resolution timer may not have expired yet. Based on this, the last start before the contention resolution timer expires can be determined.

[0099] The contention resolution timer will not be started if the terminal device does not receive the Msg3 retransmission based on TC-RNTI scheduling on the PDCCH. In the case of not receiving the Msg3 retransmission schedule, it can be determined that the contention resolution timer will not be started.

[0100] It should be noted that the above embodiments are not exhaustive, but only illustrative of some embodiments. Furthermore, the above embodiments can be implemented individually or in combination. The above embodiments are only illustrative and are not intended to limit the scope of protection of the embodiments disclosed herein.

[0101] In some embodiments, the first condition includes at least one of the following:

[0102] The terminal device is in the NTN network, and the contention resolution timer times out before the first symbol after the initial transmission of Msg3 is completed, plus the RTT time.

[0103] The terminal device is in the NTN network, and the contention resolution timer times out before the first Symbol plus the RTT time after the scheduled Msg3 retransmission ends;

[0104] The terminal device is in the NTN network, and the contention resolution timer times out before the first Symbol plus the RTT time after all repeated transmissions of the initial Msg3 transmission are completed. In this case, the Type A Physical Uplink Shared Channel (PUSCH) is used to repeatedly schedule Msg3.

[0105] The terminal device is in the NTN network, and the contention resolution timer times out before the first Symbol plus the RTT time after all repeated transmissions of the scheduled Msg3 retransmission have ended. The Msg3 is scheduled using Type A PUSCH repetition.

[0106] The terminal device is in the NTN network, and the terminal device receives the retransmission schedule of Msg3 on the PDCCH, and the contention resolution timer times out before the first Symbol plus the RTT time after the initial transmission of Msg3 ends.

[0107] The terminal device is in the NTN network, and the terminal device receives the retransmission schedule of Msg3 on the PDCCH, and the contention resolution timer times out before the first Symbol plus the RTT after the Msg3 retransmission ends.

[0108] In this embodiment of the disclosure, the first condition can be that the terminal device is in an NTN network, and the contention resolution timer times out before the first symbol plus the RTT time after the initial transmission of Msg3. In contention-based random access, if the contention resolution timer times out and the above first condition is met, the terminal device determines that the contention resolution was unsuccessful or does not consider the contention resolution unsuccessful, thus avoiding the terminal device's erroneous determination that the contention resolution has failed.

[0109] In this embodiment of the disclosure, the first condition may be that the terminal device is in an NTN network and the contention resolution timer expires before the first Symbol plus the RTT time after the scheduled Msg3 retransmission ends; if the terminal device is in contention-based random access and the contention resolution timer expires, and the above first condition is met, it is determined that the contention resolution was unsuccessful or is not considered to have failed, which can avoid the terminal device mistakenly determining that the contention resolution has failed.

[0110] In this embodiment of the disclosure, the first condition can be that the terminal device is in an NTN network, and the contention resolution timer times out before the first Symbol plus the RTT time after all repeated transmissions of the initial Msg3 transmission are completed, wherein Msg3 is repeatedly scheduled using a Type A Physical Uplink Shared Channel (PUSCH). In contention-based random access, if the contention resolution timer times out and the above first condition is met, the terminal device determines that the contention resolution was unsuccessful or does not consider the contention resolution to be unsuccessful, which can avoid the terminal device mistakenly determining that the contention resolution has failed.

[0111] In this embodiment of the disclosure, the first condition can be that the terminal device is in an NTN network, and the contention resolution timer times out before the first Symbol plus the RTT time after all repeated transmissions of the scheduled Msg3 retransmission have ended, wherein Type A PUSCH repetition is used to schedule Msg3; if the terminal device is in contention-based random access, and the contention resolution timer times out, and the above first condition is met, it can determine that the contention resolution was unsuccessful or not consider the contention resolution to be unsuccessful, which can avoid the terminal device mistakenly determining that the contention resolution has failed.

[0112] In this embodiment of the disclosure, the first condition may be that the terminal device is in an NTN network, and the terminal device receives the retransmission schedule of Msg3 on the PDCCH, and the contention resolution timer expires before the first Symbol plus the RTT time after the initial transmission of Msg3 ends; in contention-based random access, if the contention resolution timer expires and the above first condition is met, the terminal device determines that the contention resolution was unsuccessful or does not consider the contention resolution to be unsuccessful, which can avoid the terminal device mistakenly determining that the contention resolution has failed.

[0113] In this embodiment of the disclosure, the first condition can be that the terminal device is in an NTN network, and the terminal device receives the retransmission schedule for Msg3 on the PDCCH, and the contention resolution timer times out before the first Symbol plus the RTT time after the Msg3 retransmission ends. In contention-based random access, if the contention resolution timer times out and the above first condition is met, the terminal device determines that the contention resolution was unsuccessful or does not consider the contention resolution to be unsuccessful, thus avoiding the terminal device erroneously determining that the contention resolution has failed.

[0114] It should be noted that the above embodiments are not exhaustive, but only illustrative of some embodiments. Furthermore, the above embodiments can be implemented individually or in combination. The above embodiments are only illustrative and are not intended to limit the scope of protection of the embodiments disclosed herein.

[0115] By implementing the embodiments of this disclosure, in a contention-based random access scenario, if the contention resolution timer times out and a first condition is met, the terminal device determines that the contention resolution was unsuccessful or does not consider the contention resolution to have failed. This avoids the terminal device erroneously determining that the contention resolution has failed.

[0116] Please see Figure 6 , Figure 6 This is a flowchart of another random access method provided in an embodiment of this disclosure.

[0117] like Figure 6 As shown, this method is executed by a terminal device, and the method may include, but is not limited to, the following steps:

[0118] S61: Initiate random access by sending a random access message Msg3 to the network-side device.

[0119] S62: In response to Msg3 being transmitted in the NTN network, start a listening timer after the initial transmission of Msg3.

[0120] In this embodiment of the disclosure, the terminal device initiates random access by sending a random access message Msg3 to the network-side device. When Msg3 is transmitted in the NTN network, the terminal device starts a listening timer after the initial transmission of Msg.

[0121] Among them, the terminal device can start a listening timer after the initial transmission of Msg3 to enable the terminal device to support blind retransmission scheduling of the initial transmission of Msg3.

[0122] In some embodiments of this disclosure, the listener timer is a separate timer, which is different from the contention resolution timer.

[0123] In this embodiment, the terminal device initiates random access by sending a random access message Msg3 to the network-side device. When Msg3 is transmitted in the NTN network, the terminal device starts a separate listener timer after the initial transmission of Msg3, in addition to a contention resolution timer. This enables the terminal device to support blind retransmission scheduling for the initial transmission of Msg3.

[0124] In some embodiments, the PDCCH is listened to during the execution of the listener timer.

[0125] In this embodiment of the disclosure, the terminal device initiates random access by sending a random access message Msg3 to the network-side device. If Msg3 is transmitted in the NTN network, the terminal device starts a separate listener timer, in addition to a contention resolution timer, after the initial transmission of Msg. During the listener timer's operation, the terminal device can listen to the PDCCH.

[0126] In some embodiments, the terminal device is in a discontinuous reception DRX active state.

[0127] In this embodiment, the terminal device initiates random access by sending a random access message Msg3 to the network-side device. When Msg3 is transmitted in the NTN network, the terminal device starts a separate listener timer after the initial transmission of Msg, in addition to a contention resolution timer. During the listener timer's operation, the terminal device is in a discontinuous reception (DRX) active state. The terminal device can also listen to the PDCCH during the listener timer's operation.

[0128] In some embodiments, listening to the PDCCH includes: listening to TC-RNTI-based scheduling or listening only to TC-RNTI-based Msg3 retransmission scheduling on the PDCCH.

[0129] In this embodiment, the terminal device initiates random access by sending a random access message Msg3 to the network-side device. If Msg3 is transmitted in the NTN network, the terminal device starts a separate listener timer after the initial transmission of Msg3, in addition to a contention resolution timer. During the listener timer's operation, the terminal device can listen to the PDCCH. Specifically, the terminal device can listen to TC-RNTI-based scheduling on the PDCCH, or it can listen only to TC-RNTI-based retransmission scheduling of Msg3.

[0130] In some embodiments, the method provided in this disclosure further includes: determining the duration of a listening timer based on a first system message or a first radio resource control (RRC) message sent by a network-side device.

[0131] In this embodiment of the disclosure, the terminal device can receive a first system message or a first RRC (radio resource control) message sent by the network-side device, and then determine the duration of the listening timer.

[0132] In LTE (long term evolution), the first system message from network-side equipment can be SIB31 (System Information Block), SIB1, or SIB2, etc. In NR (new radio), the first system message from network-side equipment can also be SIB19 or SIB1. The first RRC message can be a connection reconfiguration message (including a handover command), a connection establishment message, a connection reconstruction message, a connection restoration message, or a connection release message, etc.

[0133] It should be noted that in this embodiment, when the terminal device initiates random access and sends a random access message Msg3 to the network-side device, and Msg3 is transmitted in the NTN network, the terminal device starts a listening timer after the initial transmission of Msg. Furthermore, in contention-based random access, if the contention resolution timer times out and the first conditions in some of the embodiments above are met, the terminal device determines that the contention resolution was unsuccessful or does not consider the contention resolution to have failed, thus avoiding the terminal device erroneously determining that the contention resolution has failed.

[0134] In some embodiments, the listening timer can be a contention resolution timer. After the terminal device sends a random access message Msg3 to the network-side device and performs the initial transmission of Msg3, it starts the contention resolution timer. During the runtime of the contention resolution timer, it listens on the PDCCH for scheduling based on TC-RNTI or only listens for retransmission scheduling of Msg3 based on TC-RNTI.

[0135] Among them, after the terminal device performs the initial transmission of Msg3, it starts the contention resolution timer. This means that the contention resolution timer can be started immediately after the initial transmission of Msg3, that is, it is not necessary to delay the RTT time before starting it.

[0136] It is understandable that after the terminal device performs the initial transmission of Msg, it starts a contention resolution timer. Then, after the initial transmission of Msg3 and a delay of the RTT time, it starts another contention resolution timer. During the running time of the contention resolution timer, it listens on the PDCCH for scheduling based on TC-RNTI or only listens for retransmission scheduling of Msg3 based on TC-RNTI.

[0137] It should be noted that in the embodiments of this disclosure, S61 and S62 can be implemented individually or in combination with any other step in the embodiments of this disclosure, such as in combination with S51 in the embodiments of this disclosure. The embodiments of this disclosure do not limit this.

[0138] It should be noted that in this embodiment, when the terminal device initiates random access and sends a random access message Msg3 to the network-side device, and Msg3 is transmitted in the NTN network, the terminal device starts a listening timer after the initial transmission of Msg. Furthermore, in contention-based random access, if the contention resolution timer times out and the first conditions in some of the embodiments above are met, the terminal device determines that the contention resolution was unsuccessful or does not consider the contention resolution to have failed, thus avoiding the terminal device erroneously determining that the contention resolution has failed.

[0139] Please see Figure 7 , Figure 7 This is a flowchart of another random access method provided in this embodiment.

[0140] like Figure 7 As shown, this method is executed by a terminal device, and the method may include, but is not limited to, the following steps:

[0141] S71: In response to receiving configuration information sent by the network-side device, start a listening timer after the initial transmission of Msg3. The configuration information is used to instruct the terminal device to perform blind retransmission scheduling for the initial transmission of Msg3.

[0142] It is conceivable that if the terminal device supports blind retransmission scheduling for the initial Msg3 transmission, the terminal needs to additionally listen to the PDCCH, which will increase the power consumption of the terminal device.

[0143] Based on this, in this embodiment of the present disclosure, the terminal device, in response to receiving the configuration information sent by the network-side device, starts a listening timer after the initial transmission of Msg3, wherein the configuration information is used to instruct the terminal device to perform blind retransmission scheduling for the initial transmission of Msg3.

[0144] In this embodiment of the disclosure, when the terminal device receives configuration information sent by the network-side device, and the configuration information instructs the terminal device to perform blind retransmission scheduling for the initial transmission of Msg3, the terminal device starts a listening timer after the initial transmission of Msg3. During the operation of the listening timer, it listens to the PDCCH to support the blind retransmission scheduling for the initial transmission of Msg3.

[0145] In this case, if the terminal device does not receive configuration information from the network-side device, it can choose not to start the listening timer or listen to the PDCCH after the initial transmission of Msg3, thereby saving power consumption of the terminal device.

[0146] In some embodiments, the configuration information received by the terminal device from the network-side device may be a second system message or a second radio resource control (RRC) message sent by the network-side device.

[0147] In LTE (long term evolution), the second system message of network-side equipment can be SIB31 (System Information Block), SIB1, or SIB2, etc. In NR (new radio), the second system message of network-side equipment can also be SIB19 or SIB1. The second RRC message can be a connection reconfiguration message (including handover command), a connection establishment message, a connection reconstruction message, a connection restoration message, or a connection release message, etc.

[0148] In some embodiments, if the terminal device supports blind retransmission scheduling for the initial Msg3 transmission, the terminal device will start the listening timer after the initial Msg3 transmission, wherein the terminal device is in an idle state, a connected state, or an inactive state.

[0149] In this embodiment of the disclosure, the terminal device can be in an idle state, an inactive state, or a connected state.

[0150] S72: Report capability information to the network-side device, wherein the capability information is used to indicate that the terminal device supports blind retransmission scheduling for receiving the initial Msg3 transmission.

[0151] In this embodiment of the disclosure, the terminal device supports reporting capability information to the network-side device. The capability information is used to indicate that the terminal device supports blind retransmission scheduling for receiving the initial transmission of Msg3.

[0152] Based on this, after receiving the capability information reported by the terminal device, the network-side device can send configuration information to the terminal device to enable blind retransmission scheduling for the initial Msg3 transmission. The capability information reported by the terminal device can be carried on Msg3 / Msg5 or reported through the terminal device capability information RRC message.

[0153] In some embodiments, a listening timer is started after the initial transmission of Msg3, including at least one of the following:

[0154] After all repeated transmissions following the initial transmission of Msg3 are completed, the first Symbol starts a listening timer, where the Type A PUSCH repetition scheduler is used to schedule Msg3.

[0155] After the initial transmission of Msg3, the first Symbol starts a listening timer, but the Type A PUSCH repetition is not used to schedule Msg3.

[0156] In this embodiment, the terminal device initiates random access by sending a random access message Msg3 to the network-side device. When Msg3 is transmitted in the NTN network, the terminal device starts a listening timer after the initial transmission of Msg3. Specifically, the terminal device can start the listening timer on the first Symbol after all repeated transmissions following the initial transmission of Msg3 have ended. The Msg3 is scheduled using Type A PUSCH repetition.

[0157] In this embodiment, the terminal device initiates random access by sending a random access message Msg3 to the network-side device. When Msg3 is transmitted in the NTN network, the terminal device starts a listening timer after the initial transmission of Msg3. Specifically, the terminal device can start the listening timer on the first Symbol after the initial transmission of Msg3, and the Type A PUSCH repetition scheduling of Msg3 is not used.

[0158] It should be noted that in the embodiments of this disclosure, S71 and S72 can be implemented individually or in combination with any other step in the embodiments of this disclosure, such as in combination with S51 and / or S61 and S62 in the embodiments of this disclosure. The embodiments of this disclosure do not limit this.

[0159] Please see Figure 8 , Figure 8 This is a flowchart of another random access method provided in this embodiment.

[0160] like Figure 8 As shown, this method is executed by a terminal device, and the method may include, but is not limited to, the following steps:

[0161] S81: Initiate random access by sending a random access message Msg3 to the network-side device.

[0162] S82: In response to the transmission of Msg3 in the NTN network, a listening timer is started after the initial transmission of Msg3. The listening timer is a contention resolution timer.

[0163] S83: In response to the contention resolution timer timeout and the second condition being met, determine that the contention resolution was unsuccessful or do not consider the contention resolution to be unsuccessful.

[0164] In related technologies, during contention-based random access, after the terminal device sends message Msg3 to the network-side device, it starts a contention resolution timer. During the execution of this contention resolution timer, the terminal device listens for Msg3 retransmission scheduling on the PDCCH (physical downlink control channel) based on TC-RNTI (temporary cell radio network temporary identifier). After the contention resolution timer expires, the terminal device considers the contention resolution unsuccessful.

[0165] However, when the listener timer is a contention resolution timer, after the terminal device sends a random access message Msg3 to the network-side device and performs the initial transmission of Msg3, it immediately starts the contention resolution timer (without delaying the RTT). If the terminal device does not receive a retransmission schedule for msg3 on the PDCCH during the execution of this contention resolution timer, it cannot be considered that the contention resolution has failed. This is because the terminal device will also listen for retransmission schedules for Msg3 on the PDCCH during the execution of the contention resolution timer started after the initial transmission of Msg3 and the RTT delay. However, the conditions for judging unsuccessful contention resolution in related technologies would consider this situation as a failure of contention resolution.

[0166] Based on this, in this embodiment of the disclosure, the terminal device, in response to the contention resolution timer timeout and the second condition being met, determines that the contention resolution was unsuccessful or does not consider the contention resolution to be unsuccessful.

[0167] In this embodiment of the disclosure, the terminal device initiates random access by sending a random access message Msg3 to the network-side device. In response to the transmission of Msg3 in the NTN network, a listening timer is started after the initial transmission of Msg3. This listening timer is a contention resolution timer. The terminal device determines that the contention resolution was unsuccessful or does not consider the contention resolution unsuccessful only if the contention resolution timer expires and a second condition is met.

[0168] The second condition can be either a condition determining that the contention resolution failed, or a condition determining that the contention resolution was not considered unsuccessful. Therefore, the success or failure of contention resolution can be determined based on the second condition, preventing the terminal device from mistakenly determining that the contention resolution failed.

[0169] In some embodiments, the second condition includes at least one of the following:

[0170] During the last startup before the contention resolution timer expired, no Msg3 retransmission scheduled based on the Temporary Cell Radio Network Temporary Identifier TC-RNTI was received on the Physical Downlink Control Channel (PDCCH).

[0171] The contention resolution timer is started after the round-trip time (RTT) following the transmission of Msg3, and the last start before the contention resolution timer expires does not receive a Msg3 retransmission based on TC-RNTI scheduling on the PDCCH.

[0172] The contention resolution timer is started after the RTT following the transmission of Msg3, and no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH after the contention resolution timer starts.

[0173] The contention resolution timer will not be started, and in the last start before the contention resolution timer expires, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH;

[0174] The contention resolution timer will not be started, and after the contention resolution timer is started, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH.

[0175] In this embodiment of the disclosure, the second condition may be that, in the last startup before the contention resolution timer expires, no Msg3 retransmission scheduled based on the Temporary Cell Radio Network Temporary Identifier (TC-RNTI) is received on the Physical Downlink Control Channel (PDCCH); the terminal device initiates random access and sends the random access message Msg3 to the network-side device in the NTN network; after the initial transmission of Msg3, the contention resolution timer is started; if the contention resolution timer expires and the above second condition is met, the terminal device determines that the contention resolution has failed or does not consider the contention resolution to have failed, which can avoid the terminal device mistakenly determining that the contention resolution has failed.

[0176] In this embodiment of the disclosure, the second condition can be that the contention resolution timer is started after the round-trip time (RTT) following the transmission of Msg3, and the last start before the contention resolution timer expires does not receive a Msg3 retransmission based on TC-RNTI scheduling on the PDCCH; the terminal device initiates random access, sends a random access message Msg3 to the network-side device in the NTN network, and starts the contention resolution timer after the initial transmission of Msg3. If the contention resolution timer expires and the above second condition is met, the terminal device determines that the contention resolution was unsuccessful or does not consider the contention resolution to be unsuccessful, which can avoid the terminal device mistakenly determining that the contention resolution has failed.

[0177] In this embodiment of the disclosure, the second condition can be that the contention resolution timer is started after the RTT following the transmission of Msg3, and after the contention resolution timer is started, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH; the terminal device initiates random access and sends the random access message Msg3 to the network-side device in the NTN network, and starts the contention resolution timer after the initial transmission of Msg3. If the contention resolution timer expires and the above second condition is met, the terminal device determines that the contention resolution has failed or does not consider the contention resolution to have failed, which can avoid the terminal device mistakenly determining that the contention resolution has failed.

[0178] In this embodiment of the disclosure, the second condition may be that the contention resolution timer will not be started, and in the last start before the contention resolution timer expires, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH; the terminal device initiates random access, sends the random access message Msg3 to the network-side device in the NTN network, and starts the contention resolution timer after the initial transmission of Msg3. If the contention resolution timer expires and the above second condition is met, the terminal device determines that the contention resolution has failed or does not consider the contention resolution to have failed, which can avoid the terminal device mistakenly determining that the contention resolution has failed.

[0179] In this embodiment of the disclosure, the second condition may be that the contention resolution timer will not be started, and after the contention resolution timer is started, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH; the terminal device initiates random access, sends a random access message Msg3 to the network-side device in the NTN network, and starts the contention resolution timer after the initial transmission of Msg3. If the contention resolution timer expires and the above second condition is met, the terminal device determines that the contention resolution has failed or does not consider the contention resolution to have failed, which can avoid the terminal device mistakenly determining that the contention resolution has failed.

[0180] The last start before the contention resolution timer expires can be initiated after the terminal device sends Msg3. After receiving at least one Msg3 retransmission based on TC-RNTI scheduling on the PDCCH, the terminal device will send Msg3 again after receiving the Msg3 retransmission schedule, and then start the contention resolution timer again. When the contention resolution timer is started this time, the previously started contention resolution timer may not have expired yet. Based on this, the last start before the contention resolution timer expires can be determined.

[0181] The contention resolution timer will not be started if the terminal device does not receive the Msg3 retransmission based on TC-RNTI scheduling on the PDCCH. In the case of not receiving the Msg3 retransmission schedule, it can be determined that the contention resolution timer will not be started.

[0182] It should be noted that the above embodiments are not exhaustive, but only illustrative of some embodiments. Furthermore, the above embodiments can be implemented individually or in combination. The above embodiments are only illustrative and are not intended to limit the scope of protection of the embodiments disclosed herein.

[0183] In some embodiments, the second condition includes at least one of the following:

[0184] The contention resolution timer times out before the first Symbol after the initial Msg3 transmission ends, plus the RTT time.

[0185] The contention is resolved so that the timer times out before the first Symbol plus the RTT after the scheduled Msg3 retransmission ends;

[0186] The contention resolution timer times out before the first Symbol plus the RTT time after all repeated transmissions of Msg3 initial transmission are completed. Among them, the Type A Physical Uplink Shared Channel (PUSCH) is used to repeatedly schedule Msg3.

[0187] The contention is resolved so that the timer times out before the first Symbol plus the RTT after all repeated transmissions of the scheduled Msg3 retransmission have ended. The Msg3 is scheduled using Type A PUSCH repetition.

[0188] The terminal device receives the retransmission schedule for Msg3 on the PDCCH, and the contention resolution timer times out before the first Symbol plus the RTT time after the initial transmission of Msg3 ends.

[0189] The terminal device receives the retransmission schedule for Msg3 on the PDCCH, and the contention resolution timer times out before the first Symbol plus the RTT after the Msg3 retransmission ends.

[0190] In this embodiment, the second condition can be that the contention resolution timer times out before the first Symbol plus the RTT time after the initial transmission of Msg3; the terminal device initiates random access and sends the random access message Msg3 to the network-side device in the NTN network. After the initial transmission of Msg3, the contention resolution timer is started. If the contention resolution timer times out and the above second condition is met, the terminal device determines that the contention resolution was unsuccessful or does not consider the contention resolution to be unsuccessful, which can avoid the terminal device mistakenly determining that the contention resolution has failed.

[0191] In this embodiment of the disclosure, the second condition can be that the contention resolution timer times out before the first Symbol plus the RTT time after the scheduled Msg3 retransmission ends; the terminal device initiates random access and sends a random access message Msg3 to the network-side device in the NTN network. After the initial transmission of Msg3, the contention resolution timer is started. If the contention resolution timer times out and the above second condition is met, the terminal device determines that the contention resolution has failed or does not consider the contention resolution to have failed, which can avoid the terminal device mistakenly determining that the contention resolution has failed.

[0192] In this embodiment of the disclosure, the second condition can be that the contention resolution timer times out before the first Symbol plus the RTT time after all repeated transmissions of the initial Msg3 transmission are completed. Here, the Type A Physical Uplink Shared Channel (PUSCH) is used to repeatedly schedule Msg3. The terminal device initiates random access and sends the random access message Msg3 to the network-side device in the NTN network. After the initial transmission of Msg3, the contention resolution timer is started. If the contention resolution timer times out and the above second condition is met, the terminal device determines that the contention resolution has failed or does not consider the contention resolution to have failed, which can avoid the terminal device mistakenly determining that the contention resolution has failed.

[0193] In this embodiment of the disclosure, the second condition can be that the contention resolution timer times out before the first Symbol plus the RTT time after all repeated transmissions of the scheduled Msg3 retransmission are completed. Here, the Type A PUSCH repetition scheduling of Msg3 is adopted. The terminal device initiates random access and sends the random access message Msg3 to the network-side device in the NTN network. After the initial transmission of Msg3, the contention resolution timer is started. If the contention resolution timer times out and the above second condition is met, the terminal device determines that the contention resolution has failed or does not consider the contention resolution to have failed, which can avoid the terminal device erroneously determining that the contention resolution has failed.

[0194] In this embodiment of the disclosure, the second condition can be that the terminal device receives the retransmission schedule of Msg3 on the PDCCH, and the contention resolution timer expires before the first Symbol plus the RTT time after the initial transmission of Msg3 ends; the terminal device initiates random access, sends the random access message Msg3 to the network-side device in the NTN network, and starts the contention resolution timer after the initial transmission of Msg3. If the contention resolution timer expires and the above second condition is met, the terminal device determines that the contention resolution was unsuccessful or does not consider the contention resolution to be unsuccessful, which can avoid the terminal device mistakenly determining that the contention resolution has failed.

[0195] In this embodiment of the disclosure, the second condition can be that the terminal device receives the retransmission schedule of Msg3 on the PDCCH, and the contention resolution timer times out before the first Symbol plus the RTT time after the Msg3 retransmission ends; the terminal device initiates random access, sends the random access message Msg3 to the network-side device in the NTN network, and starts the contention resolution timer after the initial transmission of Msg3. If the contention resolution timer times out and the above second condition is met, the terminal device determines that the contention resolution has failed or does not consider the contention resolution to have failed, which can avoid the terminal device mistakenly determining that the contention resolution has failed.

[0196] It should be noted that the above embodiments are not exhaustive, but only illustrative of some embodiments. Furthermore, the above embodiments can be implemented individually or in combination. The above embodiments are only illustrative and are not intended to limit the scope of protection of the embodiments disclosed herein.

[0197] By implementing the embodiments of this disclosure, in a contention-based random access scenario, if the contention resolution timer times out and a first condition is met, the terminal device determines that the contention resolution was unsuccessful or does not consider the contention resolution to have failed. This avoids the terminal device erroneously determining that the contention resolution has failed.

[0198] It should be noted that in the embodiments of this disclosure, S81 to S83 can be implemented individually or in combination with any other step in the embodiments of this disclosure, such as in combination with S51 and / or S61 and S62 and / or S71 and S72 in the embodiments of this disclosure. The embodiments of this disclosure do not limit this.

[0199] The methods provided in the embodiments of this disclosure above are described from the perspective of a terminal device. To implement the functions of the methods provided in the embodiments of this disclosure above, the terminal device may include hardware structures and software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. One of the above functions may be executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules.

[0200] Please see Figure 9 This is a schematic diagram of the structure of a communication device 1 provided in an embodiment of the present disclosure. Figure 9 The communication device 1 shown may include a transceiver module 11 and a processing module 12. The transceiver module may include a sending module and / or a receiving module. The sending module is used to implement the sending function, and the receiving module is used to implement the receiving function. The transceiver module can implement both sending and / or receiving functions.

[0201] The communication device 1 can be a terminal device, a device within a terminal device, or a device that can be used in conjunction with a terminal device.

[0202] In some embodiments, the communication device 1 is a terminal device:

[0203] The device includes: a processing module 12.

[0204] Processing module 12 is configured to, in response to a contention-based random access event, if the contention resolution timer times out and a first condition is met, determine that the contention resolution was unsuccessful or not consider the contention resolution to be unsuccessful.

[0205] In some embodiments, the communication device 1 further includes a transceiver module 11.

[0206] The transceiver module 11 is configured to send a contention-based random access request to the network-side device, wherein the random access request includes a message Msg3.

[0207] In some embodiments, the first condition includes at least one of the following:

[0208] Msg3 was transmitted in the non-terrestrial network NTN network, and in the last start before the contention resolution timer expired, no Msg3 retransmission scheduled based on the temporary cell radio network temporary identifier TC-RNTI was received on the physical downlink control channel PDCCH.

[0209] Msg3 is transmitted in the NTN network, and the contention resolution timer is started after the round-trip time (RTT) after Msg3 is sent. In the last start before the contention resolution timer expires, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH.

[0210] Msg3 is transmitted in the NTN network, and the contention resolution timer is started after the RTT following the transmission of Msg3. After the contention resolution timer is started, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH.

[0211] When Msg3 is transmitted in the NTN network, the contention resolution timer will not be started, and in the last start before the contention resolution timer expires, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH.

[0212] When Msg3 is transmitted in the NTN network, the contention resolution timer will not be started, and after the contention resolution timer is started, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH.

[0213] In some embodiments, the first condition includes at least one of the following:

[0214] The terminal device is in the NTN network, and the contention resolution timer times out before the first symbol after the initial transmission of Msg3 is completed, plus the RTT time.

[0215] The terminal device is in the NTN network, and the contention resolution timer times out before the first Symbol plus the RTT time after the scheduled Msg3 retransmission ends;

[0216] The terminal device is in the NTN network, and the contention resolution timer times out before the first Symbol plus the RTT time after all repeated transmissions of the initial Msg3 transmission are completed. In this case, the Type A Physical Uplink Shared Channel (PUSCH) is used to repeatedly schedule Msg3.

[0217] The terminal device is in the NTN network, and the contention resolution timer times out before the first Symbol plus the RTT time after all repeated transmissions of the scheduled Msg3 retransmission have ended. The Msg3 is scheduled using Type A PUSCH repetition.

[0218] The terminal device is in the NTN network, and the terminal device receives the retransmission schedule of Msg3 on the PDCCH, and the contention resolution timer times out before the first Symbol plus the RTT time after the initial transmission of Msg3 ends.

[0219] The terminal device is in the NTN network, and the terminal device receives the retransmission schedule of Msg3 on the PDCCH, and the contention resolution timer times out before the first Symbol plus the RTT after the Msg3 retransmission ends.

[0220] In some embodiments, the communication device 1 is a terminal device:

[0221] The device includes a transceiver module 11 and a processing module 12.

[0222] The transceiver module 11 is configured to initiate random access and send a random access message Msg3 to the network-side device.

[0223] Processing module 12 is configured to start a listening timer after the initial transmission of Msg3 in response to the transmission of Msg3 in the NTN network.

[0224] In some embodiments, the listen timer is a separate timer, which is different from the contention resolution timer.

[0225] In some embodiments, the processing module 12 is also configured to listen to the PDCCH during the operation of the listening timer.

[0226] In some embodiments, the terminal device is in a discontinuous reception DRX active state.

[0227] In some embodiments, the processing module 12 is further configured to listen on the PDCCH for TC-RNTI-based scheduling or to listen only for TC-RNTI-based Msg3 retransmission scheduling.

[0228] In some embodiments, the transceiver module 11 is further configured to determine the duration of the listening timer based on a first system message or a first radio resource control (RRC) message sent by the network-side device.

[0229] In some embodiments, the listener timer is a contention resolution timer, wherein the processing module 12 is further configured to listen on the PDCCH for TC-RNTI-based scheduling or only listen for TC-RNTI-based Msg3 retransmission scheduling during the operation of the listener timer.

[0230] In some embodiments, the processing module 12 is further configured to start a listening timer after the initial transmission of Msg3 in response to receiving configuration information sent by the network-side device, wherein the configuration information is used to instruct the terminal device to perform blind retransmission scheduling for the initial transmission of Msg3.

[0231] In some embodiments, the transceiver module 11 is further configured to receive a second system message or a second radio resource control (RRC) message sent by a network-side device.

[0232] In some embodiments, the processing module 12 is further configured to start a listening timer after the initial transmission of Msg3 in response to the terminal device supporting blind retransmission scheduling of the initial transmission of Msg3, wherein the terminal device is in an idle state, a connected state, or an inactive state.

[0233] In some embodiments, the transceiver module 11 is further configured to report capability information to the network-side device, wherein the capability information is used to indicate that the terminal device supports blind retransmission scheduling for receiving the initial Msg3 transmission.

[0234] In some embodiments, the processing module 12 is further configured to start a listening timer after the initial transmission of Msg3, including at least one of the following:

[0235] After all repeated transmissions following the initial transmission of Msg3 are completed, the first Symbol starts a listening timer, where the Type A PUSCH repetition scheduler is used to schedule Msg3.

[0236] After the initial transmission of Msg3, the first Symbol starts a listening timer, but the Type A PUSCH repetition is not used to schedule Msg3.

[0237] In some embodiments, the processing module 12 is further configured to determine that the contention resolution was unsuccessful or not consider the contention resolution to be unsuccessful in response to a contention resolution timer timeout and a second condition being met.

[0238] In some embodiments, the second condition includes at least one of the following:

[0239] During the last startup before the contention resolution timer expired, no Msg3 retransmission scheduled based on the Temporary Cell Radio Network Temporary Identifier TC-RNTI was received on the Physical Downlink Control Channel (PDCCH).

[0240] The contention resolution timer is started after the round-trip time (RTT) following the transmission of Msg3, and the last start before the contention resolution timer expires does not receive a Msg3 retransmission based on TC-RNTI scheduling on the PDCCH.

[0241] The contention resolution timer is started after the RTT following the transmission of Msg3, and no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH after the contention resolution timer starts.

[0242] The contention resolution timer will not be started, and in the last start before the contention resolution timer expires, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH;

[0243] The contention resolution timer will not be started, and after the contention resolution timer is started, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH.

[0244] In some embodiments, the second condition includes at least one of the following:

[0245] The contention resolution timer times out before the first Symbol after the initial Msg3 transmission ends, plus the RTT time.

[0246] The contention is resolved so that the timer times out before the first Symbol plus the RTT after the scheduled Msg3 retransmission ends;

[0247] The contention resolution timer times out before the first Symbol plus the RTT time after all repeated transmissions of Msg3 initial transmission are completed. Among them, the Type A Physical Uplink Shared Channel (PUSCH) is used to repeatedly schedule Msg3.

[0248] The contention is resolved so that the timer times out before the first Symbol plus the RTT after all repeated transmissions of the scheduled Msg3 retransmission have ended. The Msg3 is scheduled using Type A PUSCH repetition.

[0249] The terminal device receives the retransmission schedule for Msg3 on the PDCCH, and the contention resolution timer times out before the first Symbol plus the RTT time after the initial transmission of Msg3 ends.

[0250] The terminal device receives the retransmission schedule for Msg3 on the PDCCH, and the contention resolution timer times out before the first Symbol plus the RTT after the Msg3 retransmission ends.

[0251] Regarding the communication device 1 in the above embodiments, the specific methods by which each module performs operations have been described in detail in the embodiments related to the method, and will not be elaborated here.

[0252] The communication device 1 provided in the above embodiments of this disclosure achieves the same or similar beneficial effects as the random access method provided in some of the above embodiments, and will not be repeated here.

[0253] Please see Figure 10 , Figure 10 This is a schematic diagram of another communication device 1000 provided in an embodiment of this disclosure. The communication device 1000 can be a terminal device, or a chip, chip system, or processor that supports the terminal device in implementing the above methods. The communication device 1000 can be used to implement the methods described in the above method embodiments, and for details, please refer to the description in the above method embodiments.

[0254] The communication device 1000 may include one or more processors 1001. The processor 1001 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., network-side equipment, baseband chip, terminal equipment, terminal equipment chip, DU or CU, etc.), execute computer programs, and process data from the computer programs.

[0255] Optionally, the communication device 1000 may further include one or more memories 1002, which may store a computer program 1004. The memories 1002 execute the computer program 1004 to cause the communication device 1000 to perform the methods described in the above method embodiments. Optionally, the memories 1002 may also store data. The communication device 1000 and the memories 1002 may be provided separately or integrated together.

[0256] Optionally, the communication device 1000 may further include a transceiver 1005 and an antenna 1006. The transceiver 1005 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 1005 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0257] Optionally, the communication device 1000 may further include one or more interface circuits 1007. The interface circuit 1007 is used to receive code instructions and transmit them to the processor 1001. The processor 1001 executes the code instructions to cause the communication device 1000 to perform the method described in the above method embodiments.

[0258] Communication device 1000 is a terminal device: processor 1001 is used to execute... Figure 5 S51 in; Figure 6 S62 in the middle; Figure 7 S71 in the middle; Figure 8 S82 and S83 in the transceiver 1005 are used to execute Figure 6 S61 in; Figure 7 S71 in the middle; Figure 8 S81 in the middle.

[0259] In one implementation, the processor 1001 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0260] In one implementation, processor 1001 may store computer program 1003, which runs on processor 1001 and causes communication device 1000 to execute the methods described in the above method embodiments. Computer program 1003 may be embedded in processor 1001, in which case processor 1001 may be implemented in hardware.

[0261] In one implementation, the communication device 1000 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this disclosure can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal-oxide-semiconductor (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal-oxide-semiconductor (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0262] The communication device described in the above embodiments may be a terminal device, but the scope of the communication device described in this disclosure is not limited thereto, and the structure of the communication device may vary. Figure 10 The communication device may be a standalone device or part of a larger device. For example, the communication device may be:

[0263] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0264] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

[0265] (3) ASIC, such as modem;

[0266] (4) Modules that can be embedded in other devices;

[0267] (5) Receivers, terminal equipment, smart terminal equipment, cellular phones, wireless equipment, handheld devices, mobile units, vehicle-mounted equipment, network equipment, cloud equipment, artificial intelligence equipment, etc.

[0268] (6) Others, etc.

[0269] For cases where the communication device can be a chip or a chip system, please refer to [link / reference]. Figure 11 This is a structural diagram of a chip provided in an embodiment of this disclosure.

[0270] Chip 1100 includes processor 1101 and interface 1103. The number of processors 1101 can be one or more, and the number of interfaces 1103 can be multiple.

[0271] Regarding the case where the chip is used to implement the functions of the terminal device in the embodiments of this disclosure:

[0272] Interface 1103 is used to receive code instructions and transmit them to the processor.

[0273] Processor 1101 is configured to run code instructions to perform the random access method as described in some of the embodiments above.

[0274] Optionally, chip 1100 may also include memory 1102, which is used to store necessary computer programs and data.

[0275] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this disclosure can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented in hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this disclosure.

[0276] This disclosure also provides a random access system, which includes the aforementioned... Figure 9In the embodiments, the communication device serves as a terminal device and the communication device serves as a network-side device; alternatively, the system includes the aforementioned components. Figure 10 The embodiments include a communication device as a terminal device and a communication device as a network-side device.

[0277] This disclosure also provides a readable storage medium having instructions stored thereon that, when executed by a computer, implement the functions of any of the above method embodiments.

[0278] This disclosure also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

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

[0280] Those skilled in the art will understand that the various numerical designations such as "first," "second," etc., used in this disclosure are merely for the convenience of description and are not intended to limit the scope of the embodiments of this disclosure, nor do they indicate the order of events.

[0281] At least one of the features described in this disclosure can also be described as one or more, and multiple features can be two, three, four or more, and this disclosure does not impose any limitations. In the embodiments of this disclosure, for a technical feature, the technical features in that technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", etc., and there is no sequential order or size order among the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0282] The correspondences shown in the tables of this disclosure can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values; this disclosure is not limiting. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this disclosure may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headers of the above tables can also use other names that the communication device can understand, and the values ​​or representations of the parameters can also be other values ​​or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

[0283] The predefined terms in this disclosure can be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

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

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

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

Claims

1. A random access method, characterized by, The method is performed by a terminal device, comprising: In a contention-based random access, a contention-based random access request is sent to a network side device, wherein the random access request includes a message Msg3, the terminal device is in a non-terrestrial network NTN network, and the Msg3 is transmitted in the NTN network; It is determined that the contention resolution timer is timed out and the first condition is met, it is determined that the contention resolution is not successful or it is not considered that the contention resolution is not successful, the contention resolution timer is started after a round trip time RTT after the Msg3 is sent by the terminal device, and the contention resolution timer is restarted after the RTT time after the Msg3 is retransmitted after the Msg3 retransmission scheduling based on the TC-RNTI is received on the PDCCH during the running time of the contention resolution timer; The first condition includes at least one of the following: The contention resolution timer is timed out before the first symbol Symbol plus the RTT time after the end of the initial transmission of the Msg3; The contention resolution timer is timed out before the first Symbol plus the RTT time after the end of the scheduled Msg3 retransmission; The contention resolution timer is timed out before the first Symbol plus the RTT time after the end of all repeated transmissions of the Msg3 initial transmission, wherein the Msg3 is scheduled by Type A physical uplink shared channel PUSCH repetition; The contention resolution timer is timed out before the first Symbol plus the RTT time after the end of all repeated transmissions of the scheduled Msg3 retransmission, wherein the Msg3 is scheduled by Type A PUSCH repetition; The terminal device receives the Msg3 retransmission scheduling on the PDCCH, and the contention resolution timer is timed out before the first Symbol plus the RTT time after the end of the Msg3 initial transmission; The terminal device receives the Msg3 retransmission scheduling on the PDCCH, and the contention resolution timer is timed out before the first Symbol plus the RTT time after the end of the Msg3 retransmission.

2. The method of claim 1, wherein, The first condition includes at least one of the following: No Msg3 retransmission scheduling based on the temporary cell radio network temporary identifier TC-RNTI is received on the physical downlink control channel PDCCH during the last start before the contention resolution timer is timed out; The contention resolution timer is started after a delay round trip time RTT after the Msg3 is sent, and no Msg3 retransmission scheduling based on the TC-RNTI is received on the PDCCH during the last start before the contention resolution timer is timed out; The contention resolution timer is started after a delay RTT after the Msg3 is sent, and no Msg3 retransmission scheduling based on the TC-RNTI is received on the PDCCH after the contention resolution timer is started; The contention resolution timer will not be started, and no Msg3 retransmission scheduling based on the TC-RNTI is received on the PDCCH during the last start before the contention resolution timer is timed out; The contention resolution timer is not started, and after the contention resolution timer is started, a Msg3 retransmission scheduling based on a TC-RNTI is not received on a PDCCH.

3. A random access method, comprising: The method is performed by a terminal device, and includes: initiating random access, and sending a message Msg3 of the random access to a network side device; starting a listening timer after initial transmission of the Msg3 in response to transmission of the Msg3 in an NTN network; in a case where the listening timer is a contention resolution timer, determining that the contention resolution timer times out and a second condition is met, and determining that contention resolution is not successful or is not considered to be not successful; the contention resolution timer is started after a round trip time RTT after the Msg3 is sent by the terminal device, and the contention resolution timer is restarted after a RTT time after the Msg3 is retransmitted in a case where a Msg3 retransmission scheduling based on a TC-RNTI is received on a PDCCH during a running time of the contention resolution timer; in a case where the listening timer is a separate timer different from the contention resolution timer, the listening timer is started after initial transmission of the Msg3, including at least one of the following: starting the listening timer at a first symbol after all repeated transmissions of the initial transmission of the Msg3 end, wherein the Msg3 is scheduled using Type A PUSCH repetition; starting the listening timer at a first symbol after the initial transmission of the Msg3, wherein the Msg3 is not scheduled using Type A PUSCH repetition; the second condition includes at least one of the following: the contention resolution timer times out before a first symbol after the initial transmission of the Msg3 plus a RTT time; the contention resolution timer times out before a first symbol after the scheduled Msg3 retransmission plus a RTT time; the contention resolution timer times out before a first symbol after all repeated transmissions of the initial transmission of the Msg3 plus a RTT time, wherein the Msg3 is scheduled using Type A PUSCH repetition; the contention resolution timer times out before a first symbol after all repeated transmissions of the scheduled Msg3 retransmission plus a RTT time, wherein the Msg3 is scheduled using Type A PUSCH repetition; the terminal device receives the Msg3 retransmission scheduling on the PDCCH, and the contention resolution timer times out before a first symbol after the initial transmission of the Msg3 plus a RTT time; the terminal device receives the Msg3 retransmission scheduling on the PDCCH, and the contention resolution timer times out before a first symbol after the Msg3 retransmission plus a RTT time.

4. The method of claim 3, wherein, further comprising: listening to a PDCCH during a running time of the listening timer.

5. The method of claim 4, wherein, the terminal device is in a discontinuous reception DRX active state.

6. The method of claim 4, wherein, the listening to the PDCCH includes: monitoring, on the PDCCH, for scheduling based on a TC-RNTI or only for retransmission scheduling of the Msg3 based on the TC-RNTI.

7. The method of any one of claims 3 to 6, wherein, Further comprising: determining a timing duration of the monitoring timer based on a first system message or a first radio resource control (RRC) message sent by the network-side device.

8. The method of claim 3, wherein, The monitoring timer is a contention resolution timer, and the method further comprises: monitoring, on the PDCCH, for scheduling based on a TC-RNTI or only for retransmission scheduling of the Msg3 based on the TC-RNTI during running of the monitoring timer.

9. The method of any one of claims 3 to 6, wherein, The starting of the monitoring timer after initial transmission of the Msg3 comprises: starting the monitoring timer after initial transmission of the Msg3 in response to receiving configuration information sent by the network-side device, wherein the configuration information is used to instruct the terminal device to perform blind retransmission scheduling of the initial transmission of the Msg3.

10. The method of claim 9, wherein, The receiving of the configuration information sent by the network-side device comprises: receiving a second system message or a second RRC message sent by the network-side device.

11. The method of claim 9, wherein, Further comprising: starting the monitoring timer after initial transmission of the Msg3 in response to the terminal device supporting blind retransmission scheduling of the initial transmission of the Msg3, wherein the terminal device is in an idle state or a connected state or an inactive state.

12. The method of any one of claims 3 to 6, wherein, Further comprising: reporting capability information to the network-side device, wherein the capability information is used to indicate that the terminal device supports receiving blind retransmission scheduling of the initial transmission of the Msg3.

13. The method of claim 3, wherein, The second condition comprises at least one of: in the last start before the contention resolution timer expires, no Msg3 retransmission scheduling based on a temporary cell radio network temporary identifier (TC-RNTI) is received on a PDCCH; the contention resolution timer is started after a delay round-trip time (RTT) after the Msg3 is sent, and in the last start before the contention resolution timer expires, no Msg3 retransmission scheduling based on the TC-RNTI is received on the PDCCH; the contention resolution timer is started after a delay RTT after the Msg3 is sent, and after the contention resolution timer is started, no Msg3 retransmission scheduling based on the TC-RNTI is received on the PDCCH; the contention resolution timer will not be started, and in the last start before the contention resolution timer expires, no Msg3 retransmission scheduling based on the TC-RNTI is received on the PDCCH; the contention resolution timer will not be started, and after the contention resolution timer is started, no Msg3 retransmission scheduling based on the TC-RNTI is received on the PDCCH.

14. A communications device, characterized by The apparatus comprises: a transceiver configured to send, to a network-side device, a contention-based random access request in a contention-based random access, wherein the random access request comprises a message (Msg3), and the Msg3 is transmitted in an NTN network by a terminal device; The processing module is configured to determine that a contention resolution timer is expired and a first condition is met, determine that contention resolution is not successful or is not considered to be not successful, the contention resolution timer is started after a round trip time (RTT) after the Msg3 is sent by the terminal device, and is restarted after an RTT time after the Msg3 is retransmitted based on a TC-RNTI scheduling on a PDCCH is received during a running time of the contention resolution timer. The first condition includes at least one of the following: The contention resolution timer is expired before a first symbol plus an RTT time after the Msg3 initial transmission ends. The contention resolution timer is expired before a first symbol plus an RTT time after the scheduled Msg3 retransmission ends. The contention resolution timer is expired before a first symbol plus an RTT time after all repeated transmissions of the Msg3 initial transmission ends, wherein the Msg3 is scheduled by Type A physical uplink shared channel (PUSCH) repetition. The contention resolution timer is expired before a first symbol plus an RTT time after all repeated transmissions of the scheduled Msg3 retransmission ends, wherein the Msg3 is scheduled by Type A PUSCH repetition. The terminal device receives the Msg3 retransmission scheduling on the PDCCH, and the contention resolution timer is expired before a first symbol plus an RTT time after the Msg3 initial transmission ends. The terminal device receives the Msg3 retransmission scheduling on the PDCCH, and the contention resolution timer is expired before a first symbol plus an RTT time after the Msg3 retransmission ends.

15. A communications device, characterized by The apparatus includes: A transceiver module configured to initiate random access, and send a message Msg3 of random access to a network side device; A processing module configured to start a listening timer after the Msg3 initial transmission in response to the Msg3 being transmitted in an NTN network; In a case where the listening timer is a contention resolution timer, the processing module is further configured to determine that the contention resolution timer is expired and a second condition is met, and determine that contention resolution is not successful or is not considered to be not successful, the contention resolution timer is started after an RTT after the Msg3 is sent by the terminal device, and is restarted after an RTT time after the Msg3 is retransmitted based on a TC-RNTI scheduling on a PDCCH is received during a running time of the contention resolution timer; In a case where the listening timer is a separate timer different from the contention resolution timer, the processing module is configured to perform at least one of the following: Start the listening timer at a first symbol after all repeated transmissions of the Msg3 initial transmission end, wherein the Msg3 is scheduled by Type A PUSCH repetition. start the listening timer at the first symbol after the initial transmission of the Msg3, wherein the Msg3 is not scheduled with Type A PUSCH repetition; the second condition comprises at least one of: the contention resolution timer expires before the first symbol after the end of the initial transmission of the Msg3 plus the RTT time instant; the contention resolution timer expires before the first symbol after the end of the scheduled retransmission of the Msg3 plus the RTT time instant; the contention resolution timer expires before the first symbol after the end of all repetitions of the initial transmission of the Msg3 plus the RTT time instant, wherein the Msg3 is scheduled with Type A PUSCH repetition; the contention resolution timer expires before the first symbol after the end of all repetitions of the scheduled retransmission of the Msg3 plus the RTT time instant, wherein the Msg3 is scheduled with Type A PUSCH repetition; the terminal device receives the scheduling of the retransmission of the Msg3 on the PDCCH, and the contention resolution timer expires before the first symbol after the end of the initial transmission of the Msg3 plus the RTT time instant; the terminal device receives the scheduling of the retransmission of the Msg3 on the PDCCH, and the contention resolution timer expires before the first symbol after the end of the retransmission of the Msg3 plus the RTT time instant.

16. A communications device, characterized by The apparatus comprises a processor and a memory, the memory stores a computer program, and the processor executes the computer program stored in the memory to enable the apparatus to perform the method of any one of claims 1-2, 3-13.

17. A communications device, characterized by comprise: a processor and an interface circuit; the interface circuit is configured to receive code instructions and transmit the code instructions to the processor; the processor is configured to execute the code instructions to perform the method of any one of claims 1-2, 3-13.

18. A computer readable storage medium storing instructions that, when executed, cause the method of any one of claims 1-2, 3-13 to be implemented.

Images