WO2023245451A1 - 随机接入方法和装置 - Google Patents

随机接入方法和装置 Download PDF

Info

Publication number
WO2023245451A1
WO2023245451A1 PCT/CN2022/100244 CN2022100244W WO2023245451A1 WO 2023245451 A1 WO2023245451 A1 WO 2023245451A1 CN 2022100244 W CN2022100244 W CN 2022100244W WO 2023245451 A1 WO2023245451 A1 WO 2023245451A1
Authority
WO
WIPO (PCT)
Prior art keywords
msg3
contention resolution
terminal device
resolution timer
timer
Prior art date
Application number
PCT/CN2022/100244
Other languages
English (en)
French (fr)
Inventor
江小威
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN202280002093.4A priority Critical patent/CN115299167A/zh
Priority to PCT/CN2022/100244 priority patent/WO2023245451A1/zh
Publication of WO2023245451A1 publication Critical patent/WO2023245451A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/004—Transmission of channel access control information in the uplink, i.e. towards network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal

Definitions

  • the present disclosure relates to the field of communication technology, and in particular, to a random access method and device.
  • the contention resolution timer will be started. During the running of the contention resolution timer, the terminal device will monitor the PDCCH (physical downlink control channel, Msg3 retransmission scheduling based on TC-RNTI (temporary cell radio network temporary identifier, temporary cell radio network temporary identifier) addressing on the physical downlink control channel. After the contention resolution timer times out, the terminal device will consider that the contention has not been resolved. success.
  • PDCCH physical downlink control channel
  • Msg3 retransmission scheduling based on TC-RNTI temporary cell radio network temporary identifier, temporary cell radio network temporary identifier
  • the contention resolution timer will be restarted multiple times due to multiple receipts of Msg3 retransmission schedules. Before the contention resolution timer is restarted, the previously started contention resolution timer may have expired. At this time, the terminal device will think that Contention failed. However, since the contention resolution timer will be restarted after receiving the retransmission schedule of Msg3, the terminal device should not think that the contention has failed at this time. This is an issue that needs to be solved urgently.
  • Embodiments of the present disclosure provide a random access method and device, which can avoid a terminal device from being mistakenly determined to be a contention resolution failure.
  • embodiments of the present disclosure provide a random access method, which is executed by a terminal device.
  • the method includes: in response to a contention resolution timer timeout in contention-based random access, and the first condition is met, Contention resolution is determined to be unsuccessful or is not considered successful.
  • the terminal device responds to the contention-based random access, the contention resolution timer times out, and the first condition is met, and determines that the contention resolution was unsuccessful or does not consider that the contention resolution was unsuccessful.
  • the terminal device responds to the contention-based random access, the contention resolution timer times out, and the first condition is met, and determines that the contention resolution was unsuccessful or does not consider that the contention resolution was unsuccessful.
  • embodiments of the present disclosure provide another random access method, which is executed by a terminal device.
  • the method includes: initiating random access, sending a random access message Msg3 to the network side device; responding to the Msg3 Transmitted in the NTN network, the listening timer is started after the initial transmission of Msg3.
  • embodiments of the present disclosure provide a communication device that has some or all of the functions of the terminal device for implementing the method described in the first aspect.
  • the functions of the communication device may have some or all of the functions of the present disclosure.
  • the functions in the embodiments may also be used to independently implement any of the embodiments of the present disclosure.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform corresponding functions in the above method.
  • the transceiver module is used to support communication between the communication device and other devices.
  • the communication device may further include a storage module coupled to the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.
  • the communication device includes: a processing module configured to determine that the contention resolution is not successful or fails in response to the contention resolution timer timing out and the first condition being met in contention-based random access. Contention resolution is considered unsuccessful.
  • embodiments of the present disclosure provide another communication device that has some or all of the functions of the terminal device in the method example described in the second aspect.
  • the functions of the communication device may have some of the functions in the present disclosure.
  • the functions in all the embodiments may also be provided to implement the functions of any one embodiment in the present disclosure independently.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform corresponding functions in the above method.
  • the transceiver module is used to support communication between the communication device and other devices.
  • the communication device may further include a storage module coupled to the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.
  • the communication device includes: a transceiver module configured to initiate random access and send a random access message Msg3 to the network side device; a processing module configured to respond to Msg3 on the NTN network During transmission, the listening timer is started after the initial transmission of Msg3.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor.
  • the processor calls a computer program in a memory, it executes the method described in the first aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor.
  • the processor calls a computer program in a memory, it executes the method described in the second aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the second aspect above.
  • an embodiment of the present disclosure provides a communication device.
  • the device includes a processor and an interface circuit.
  • the interface circuit is used to receive code instructions and transmit them to the processor.
  • the processor is used to run the code instructions to cause the The device performs the method described in the first aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the device includes a processor and an interface circuit.
  • the interface circuit is used to receive code instructions and transmit them to the processor.
  • the processor is used to run the code instructions to cause the The device performs the method described in the second aspect above.
  • embodiments of the present disclosure provide a random access system, which includes the communication device described in the third aspect and the communication device described in the fourth aspect, or the system includes the communication device described in the fifth aspect.
  • the device and the communication device according to the sixth aspect, or the system includes the communication device according to the seventh aspect and the communication device according to the eighth aspect, or the system includes the communication device according to the ninth aspect and the communication device according to the tenth aspect.
  • embodiments of the present invention provide a computer-readable storage medium for storing instructions used by the above-mentioned terminal equipment. When the instructions are executed, the terminal equipment is caused to execute the above-mentioned first aspect. method.
  • embodiments of the present invention provide a readable storage medium for storing instructions used by the terminal device. When the instructions are executed, the terminal device is caused to execute the method described in the second aspect. .
  • the present disclosure also provides a computer program product including a computer program, which when run on a computer causes the computer to execute the method described in the first aspect.
  • the present disclosure also provides a computer program product including a computer program, which, when run on a computer, causes the computer to execute the method described in the second aspect.
  • the present disclosure provides a chip system, which includes at least one processor and an interface for supporting a terminal device to implement the functions involved in the first aspect, for example, determining or processing data involved in the above method. and information.
  • the chip system further includes a memory, and the memory is used to store necessary computer programs and data for the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present disclosure provides a chip system, which includes at least one processor and an interface for supporting the terminal device to implement the functions involved in the second aspect, for example, determining or processing the data involved in the above method. and information.
  • the chip system further includes a memory, and the memory is used to store necessary computer programs and data for the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present disclosure provides a computer program that, when run on a computer, causes the computer to execute the method described in the first aspect.
  • the present disclosure provides a computer program that, when run on a computer, causes the computer to perform the method described in the second aspect.
  • Figure 1 is a schematic diagram of an NTN communication method provided by an embodiment of the present disclosure
  • Figure 2 is a schematic diagram of another NTN communication method provided by an embodiment of the present disclosure.
  • Figure 3 is a schematic diagram of another NTN communication method provided by an embodiment of the present disclosure.
  • Figure 4 is an architectural diagram of a communication system provided by an embodiment of the present disclosure.
  • Figure 5 is a flow chart of a random access method provided by an embodiment of the present disclosure.
  • Figure 6 is a flow chart of another random access method provided by an embodiment of the present disclosure.
  • Figure 7 is a flow chart of yet another random access method provided by an embodiment of the present disclosure.
  • Figure 8 is a flow chart of yet another random access method provided by an embodiment of the present disclosure.
  • Figure 9 is a structural diagram of a communication device provided by an embodiment of the present disclosure.
  • Figure 10 is a structural diagram of another communication device provided by an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of a chip provided by an embodiment of the present disclosure.
  • the random access process refers to the process from when the user (terminal device) sends a random access preamble and tries to access the network (network side device) to when a basic signaling connection is established with the network. Random access is a very critical step in the mobile communication system, and it is also the last step in establishing a communication link between the terminal device and the network side device. Terminal devices can interact with network-side devices through random access.
  • the random access process may include two-step random access and four-step random access.
  • the four-step random access process includes: the terminal device sends a random access preamble through the first message msg1; the network side device sends a random access response message (Random AccessResponse, RAR) through the second message msg2; the terminal The device sends a radio resource control (RRC) connection request through the third message msg3; the terminal device receives the RRC connection establishment through the fourth message msg4 (this process is also the contention resolution process)
  • RRC radio resource control
  • the two-step 2-step random access process includes: the terminal device sends an A message msgA to the network side device, and the network side device sends a B message msgB to the terminal device.
  • msgA contains content equivalent to msg1 and msg3 in four-step random access
  • msgB contains content equivalent to msg2 and msg4 in four-step random access.
  • the third message in the 4-step random access process is called Msg3.
  • Msg3 The third message in the 4-step random access process is called Msg3.
  • the content of the Msg3 message may also be different.
  • Msg3 needs to contain an important piece of information: the unique identifier of each terminal device, which will be used for the fourth step of contention resolution in four-step random access.
  • the terminal device will start the contention resolution timer after sending msg3. During the running of the timer, the terminal device will monitor the msg3 re-addressed by TC-RNTI on the PDCCH. Pass scheduling, or msg4 scheduling. After the contention resolution timer expires, the end device considers contention resolution unsuccessful.
  • NTN non-terrestrialnetworks, non-terrestrial networks
  • NTN communications can be divided into transparent transmission mode and regeneration mode.
  • the transparent transmission mode is shown in Figure 2.
  • the NTN ground station sends the base station signal to the satellite.
  • the satellite converts the signal to the satellite frequency band and then sends it to the terminal (terminal equipment) through the satellite frequency band.
  • the satellite Does not demodulate base station signals.
  • the regeneration mode is shown in Figure 3. 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 sends the regenerated signal through the satellite frequency band.
  • Table 1 below gives the satellite altitude, orbit, and satellite coverage of a typical NTN network:
  • the contention resolution timer is started after the RTT (Round-Trip Time, round trip time) time passes after msg3 is sent.
  • Scrambling is a digital signal processing method that uses the scrambling code to XOR the original signal to obtain a new signal.
  • uplink physical channel scrambling is to distinguish different terminal devices, and downlink scrambling can distinguish cells and channels.
  • scrambling codes can be used to scramble and descramble the original signal.
  • the scrambling code can scramble downlink control information (DCI), or it can also be called scrambling PDCCH.
  • Scrambling DCI may specifically refer to scrambling the cyclic redundancy check (CRC) field of DCI.
  • the terminal device descrambles the received DCI, which specifically means that the terminal device uses a corresponding type of scrambling code to descramble the CRC field of the DCI to determine the format or type of the DCI.
  • 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 wireless network temporary Identifier (random accessradionetwork temporary identifier, RA-RNTI), system information radio network temporary identifier (SI-RNTI), and paging radio network temporary identifier (P-RNTI).
  • C-RNTI cell radio network temporary identifier
  • TC-RNTI temporary cell radio network temporary identifier
  • random access wireless network temporary Identifier random access wireless network temporary Identifier (random accessradionetwork temporary identifier, RA-RNTI), system information radio network temporary identifier (SI-RNTI), and paging radio network temporary identifier (P-RNTI).
  • the terminal device 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.
  • the terminal device needs to carry the C-RNTI when it initiates a random access request to the network side device. . If the terminal device is in the RRC idle state or the RRC inactive state, it means that the terminal device has not 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 message, recorded as TC-RNTI. After the terminal device is randomly accessed successfully, the TC-RNTI can be converted for C-RNTI.
  • RRC-connected radio resource control connected
  • 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 equipment A and terminal equipment B initiate random access using the same random access channel time-frequency resource, the corresponding RA-RNTIs are the same.
  • PUSCH includes two mapping types: Type A and Type B.
  • Mapping type can be understood as the resource allocation type.
  • both Type A and Type B indicate the starting symbol (identified as S), symbol length (identified as L), and the possible value range of S+L, for example, third-generation partners Table 6.1.2.1-1 (referred to as Table 2 in this disclosure) in Chapter 6.1.2.1 of Tchnology Standard (TS) 38.214 of the 3rd generation partnership project (3GPP) shows that the valid The combination of S and L (Valid Sand L combinations).
  • the parameters in the Type A row are only applicable to the repeated sending of Type A (repetition Type Aonly).
  • " ⁇ 1,...,14 ⁇ ” and “ ⁇ 1,...,12 ⁇ ” in the S+L column of the Type B row are suitable for repeated sending of Type A (for repetition Type A)
  • the S+L of the Type B row “ ⁇ 1,...,27 ⁇ ” and “ ⁇ 1,...,23 ⁇ ” in a column are suitable for repeated sending of Type B (for repetition TypeB).
  • Repeated transmission of PUSCH refers to sending multiple PUSCHs, and multiple PUSCHs are multiple copies of the same uplink data.
  • the transmission of a PUSCH ie, a piece of uplink data
  • Multiple copies of the same uplink data refer to multiple copies of the same or different RVs (redundancy versions) obtained by channel coding the same system bits.
  • the communication standard introduces the parameter "number of repetitions (numberOfRepetitions-r16)" to configure the number of repetitions.
  • numberOfRepetitions-r16 has a total of 8 configurable values, indicated by 3 bits. The various values of these 3 bits correspond to ⁇ n1, n2, n3, n4,n7,n8,n12,n16 ⁇ , the value after n indicates the number of repetitions, for example, n1 indicates sending once, n16 indicates sending 16 times.
  • the network device can configure one of the above eight configurable values for the terminal device through high-layer signaling, such as RRC signaling, thereby indicating the number of repetitions to the terminal device.
  • L*numberOfRepetitions-r16 available symbols are all used for repeated transmission of PUSCH. "*" in this application means "multiplied by".
  • S+L is less than or equal to 14.
  • the terminal device When the terminal device is configured with the number of repetitions (assumed to be R1), the terminal device will detect each time slot in R1 time slots (R1 consecutive time slots starting from the starting time slot). When a certain time slot If the L symbols starting from the starting symbol S in the slot are all available symbols, PUSCH will be sent on this time slot. Otherwise, PUSCH will be sent on this time slot and continue to see if other time slots meet the conditions.
  • FIG. 4 is a schematic architectural diagram of a communication system provided by an embodiment of the present disclosure.
  • the communication system may include but is not limited to one network side device and one terminal device.
  • the number and form of devices shown in Figure 4 are only for examples and do not constitute a limitation on the embodiments of the present disclosure. In actual applications, two or more devices may be included.
  • the communication system 10 shown in Figure 4 includes a network side device 101 and a terminal device 102 as an example.
  • LTE long term evolution
  • 5th generation 5th generation
  • NR 5th generation new radio
  • side link in the embodiment of the present disclosure may also be called a side link or a through link.
  • the network side device 101 in the embodiment of the present disclosure is an entity on the network side that is used to transmit or receive signals.
  • the network side device 101 can be an evolved base station (evolved NodeB, eNB), a transmission point (transmission reception point, TRP), a next generation base station (next generation NodeB, gNB) in an NR system, or other future mobile communication systems.
  • eNB evolved NodeB
  • TRP transmission reception point
  • gNB next generation base station
  • WiFi wireless fidelity
  • the embodiments of the present disclosure do not limit the specific technology and specific equipment form used by the base station.
  • the base station may be composed of a centralized unit (central unit, CU) and a distributed unit (DU), where the CU may also be called a control unit (control unit), and CU-DU is used.
  • the structure can separate the protocol layer of the base station, such as the base station. Some protocol layer functions are centralized controlled by the CU, and the remaining part or all protocol layer functions are distributed in the DU, and the CU centrally controls the DU.
  • the terminal device 102 in the embodiment of the present disclosure is an entity on the user side that is used to receive or transmit signals, such as a mobile phone.
  • Terminal equipment can also be called terminal equipment (terminal), user equipment (user equipment, UE), mobile station (mobile station, MS), mobile terminal equipment (mobile terminal, MT), etc.
  • the terminal device can be a car with communication functions, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (augmented reality (AR) terminal equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical surgery, smart grid ( Wireless terminal equipment in smart grid, wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, wireless terminal equipment in smart home, etc.
  • the embodiments of the present disclosure do not limit the specific technology and specific equipment form used by the terminal equipment.
  • Figure 5 is a flow chart of a random access method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • the terminal device performs a contention-based random access process and sends a contention-based random access request to the network side device, where the random access request includes message Msg3.
  • the terminal device performs a contention-based random access process.
  • the contention resolution timer (ra-ContentionResolutionTimer) will be started.
  • the terminal equipment will monitor the Msg3 retransmission scheduling based on TC-RNTI (temporary cell radio network temporary identifier, temporary cell radio network temporary identifier) addressing on PDCCH (physical downlink control channel, physical downlink control channel), or the scheduling of message Msg4, After the contention resolution timer times out, and if the first condition is met, it is determined that the contention resolution was not successful, or it is determined that the contention resolution is not considered to be unsuccessful.
  • TC-RNTI temporary cell radio network temporary identifier, temporary cell radio network temporary identifier
  • PDCCH physical downlink control channel, physical downlink control channel
  • the first condition may be a condition for determining that the contention resolution is not successful, or the first condition may be a condition for determining that the contention resolution is not considered to be unsuccessful. Therefore, whether the contention resolution is successful can be determined based on the first condition, and the terminal device can be prevented from mistakenly determining that the contention resolution has failed.
  • the first condition includes at least one of the following:
  • Msg3 is transmitted in a non-terrestrial network NTN network, and the Msg3 retransmission scheduled based on the temporary cell radio network temporary identifier TC-RNTI is not received on the physical downlink control channel PDCCH at the last start before the contention resolution timer expires;
  • Msg3 is transmitted in the NTN network, and the contention resolution timer is started after the round-trip time delay RTT after Msg3 is sent, and the last time before the contention resolution timer times out, no TC-RNTI is received on the PDCCH Scheduled Msg3 retransmission;
  • Msg3 is transmitted in the NTN network, and the contention resolution timer is started after the RTT delay after Msg3 is sent, and after the contention resolution timer is started, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH;
  • the contention resolution timer When Msg3 is transmitted in the NTN network, the contention resolution timer will not be started, and the Msg3 retransmission based on TC-RNTI scheduling is not received on the PDCCH at the last start before the contention resolution timer expires;
  • the contention resolution timer 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.
  • the first condition may be that Msg3 is transmitted in the non-terrestrial network NTN network, and the Msg3 re-scheduling based on TC-RNTI is not received on the PDCCH at the last start before the contention resolution timer expires. pass.
  • the terminal device determines that the contention resolution was unsuccessful or does not consider that the contention resolution was unsuccessful, which can avoid the terminal device making an incorrect determination. Contention resolution failed.
  • the first condition may be that Msg3 is transmitted in the NTN network, and the contention resolution timer is started after the round-trip time RTT is delayed after Msg3 is sent, and the last time before the contention resolution timer times out Started, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH; the terminal device determines contention resolution when the contention resolution timer times out in contention-based random access and the first condition above is met. Not being successful or not considering contention resolution as unsuccessful can avoid the terminal device from incorrectly determining that contention resolution failed.
  • the first condition may be that Msg3 is transmitted in the NTN network, and the contention resolution timer is started after the RTT is delayed after Msg3 is sent, and after the contention resolution timer is started, the contention resolution timer is not started on the PDCCH.
  • the terminal device After receiving the Msg3 retransmission scheduled based on TC-RNTI; in the contention-based random access, the terminal device determines that the contention resolution has not been successful or does not consider the contention resolution timer to be successful if the contention resolution timer times out and the first condition above is met.
  • Resolution Unsuccessful you can avoid end devices from being incorrectly determined to have failed contention resolution.
  • the first condition may be that Msg3 is transmitted in the NTN network, the contention resolution timer will not be started, and the contention resolution timer will not be started for the last time before the contention resolution timer expires, and the contention resolution timer based on Msg3 retransmission scheduled by TC-RNTI; in contention-based random access, if the contention resolution timer times out and the first condition above is met, the terminal device determines that the contention resolution has not been successful or does not consider that the contention resolution has not been successful. Success prevents the end device from incorrectly determining contention resolution failure.
  • the first condition may 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 TC-RNTI-based scheduling is received on the PDCCH. Msg3 retransmission.
  • the terminal device determines that the contention resolution was unsuccessful or does not consider that the contention resolution was unsuccessful, which can avoid the terminal device making an incorrect determination. Contention resolution failed.
  • the contention resolution timer can be started after the terminal device sends Msg3. After receiving at least one retransmission of Msg3 based on TC-RNTI scheduling on the PDCCH, after receiving the retransmission schedule of Msg3, the terminal device will send Msg3 again, and then start the contention resolution timer. This time, contention resolution is started. When the timer is set, the previously started contention resolution timer may not have expired. Based on this, the last start before the contention resolution timer expires can be determined.
  • the contention resolution timer will not be started because the terminal equipment does not receive the Msg3 retransmission based on the TC-RNTI schedule on the PDCCH. In the case of not receiving the Msg3 retransmission schedule, the contention resolution can be determined. The timer will not be started.
  • the first condition includes at least one of the following:
  • the terminal device is in the NTN network, and the contention resolution timer times out before the first symbol Symbol plus RTT time after the initial transmission of Msg3;
  • the terminal device is in the NTN network, and the contention resolution timer times out before the first Symbol plus RTT time after the scheduled Msg3 retransmission ends;
  • the terminal device is in the NTN network, and the contention resolution timer times out before the first Symbol plus RTT time after all repeated transmissions of Msg3 initial transmission are completed, in which Type A physical uplink shared channel PUSCH is used to repeatedly schedule Msg3;
  • the terminal device is in the NTN network, and the contention resolution timer times out before the first Symbol plus RTT time after all repeated transmissions of the scheduled Msg3 retransmission, in which Type A PUSCH repetition is used to schedule Msg3;
  • 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;
  • 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 Msg3 retransmission ends.
  • the first condition may be that the terminal device is in the NTN network, and the contention resolution timer times out before the first symbol Symbol plus RTT time after the initial transmission of Msg3 ends.
  • the terminal device determines that the contention resolution was unsuccessful or does not consider that the contention resolution was unsuccessful, which can avoid the terminal device making an incorrect determination. Contention resolution failed.
  • the first condition may be that the terminal device is in the NTN network, and the contention resolution timer times out before the first Symbol plus RTT time after the scheduled Msg3 retransmission ends; the terminal device is based on contention.
  • the contention resolution timer times out and the first condition above is met, it is determined that the contention resolution was unsuccessful or does not consider the contention resolution to be unsuccessful, which can avoid the terminal device being mistakenly determined to be a contention resolution failure. .
  • the first condition may be that the terminal device is in the NTN network, and the contention resolution timer times out before the first Symbol plus RTT time after all repeated transmissions of Msg3 initial transmission are completed, where, use Type A Physical Uplink Shared Channel PUSCH Repeated Scheduling Msg3;
  • contention-based random access if the contention resolution timer times out and the first condition above is met, the terminal device determines that the contention resolution has not been successful or does not consider the contention to be resolved.
  • Resolution Unsuccessful you can avoid end devices from being incorrectly determined to have failed contention resolution.
  • the first condition may be that the terminal device is in the NTN network, and the contention resolution timer times out before the first Symbol plus RTT time after all repeated transmissions of the scheduled Msg3 retransmission end, where , Type A PUSCH repetition is used to schedule Msg3; when the contention resolution timer times out in contention-based random access, and the first condition above is met, the terminal device determines that the contention resolution has not been successful or does not consider that the contention resolution has not been successful. Success prevents the end device from incorrectly determining contention resolution failure.
  • the first condition may be that 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 is the first Symbol after the initial transmission of Msg3 ends. Plus the timeout before the RTT moment; when the contention resolution timer of the terminal device times out in contention-based random access and the first condition above is met, it determines that the contention resolution was unsuccessful or does not consider that the contention resolution was unsuccessful. It is possible to avoid incorrect identification of end devices as contention resolution failures.
  • the first condition may be that the terminal device is in the NTN network, and the terminal device receives the Msg3 retransmission schedule on the PDCCH, and the contention resolution timer is the first Symbol after the Msg3 retransmission ends. Add a timeout before the RTT moment.
  • the terminal device determines that the contention resolution was unsuccessful or does not consider that the contention resolution was unsuccessful, which can avoid the terminal device making an incorrect determination. Contention resolution failed.
  • the terminal device determines that the contention resolution is unsuccessful or does not consider the contention resolution to be unsuccessful in response to the contention resolution timer expiring in contention-based random access and meeting the first condition. Thus, it is possible to avoid the terminal device from being mistakenly determined as a contention resolution failure.
  • Figure 6 is a flow chart of another random access method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • S61 Initiate random access and send the random access message Msg3 to the network side device.
  • S62 In response to Msg3 being transmitted in the NTN network, start the listening timer after the initial transmission of Msg3.
  • the terminal device initiates random access and sends the random access message Msg3 to the network side device.
  • Msg3 is transmitted in the NTN network
  • the terminal device starts the listening timer after the initial transmission of Msg.
  • the terminal device can start the listening timer after the initial transmission of Msg3, so as to realize the blind retransmission scheduling of the terminal device supporting the initial transmission of Msg3.
  • the listening timer is a separate timer, and the listening timer and the contention resolution timer are different timers.
  • the terminal device initiates random access and sends the random access message Msg3 to the network side device.
  • Msg3 is transmitted in the NTN network
  • the terminal device starts a contention resolution timer after the initial transmission of Msg. separate listening timer. Therefore, the terminal device can support the blind retransmission scheduling of the initial transmission of Msg3.
  • the PDCCH is listened to while the listening timer is running.
  • the terminal device initiates random access and sends the random access message Msg3 to the network side device.
  • Msg3 is transmitted in the NTN network
  • the terminal device starts a contention resolution timer after the initial transmission of Msg. separate listening timer. While the listening timer is running, the terminal device can listen to the PDCCH.
  • the terminal device is in the discontinuous reception DRX active state.
  • the terminal device initiates random access and sends the random access message Msg3 to the network side device.
  • Msg3 is transmitted in the NTN network
  • the terminal device starts a contention resolution timer after the initial transmission of Msg. separate listening timer. While the listening timer is running, the terminal device is in the discontinuous reception DRX (discontinuous reception) active state.
  • the terminal device can also listen to the PDCCH while the listening timer is running.
  • monitoring the PDCCH includes: monitoring the TC-RNTI-based scheduling on the PDCCH or only monitoring the retransmission scheduling of Msg3 based on the TC-RNTI.
  • the terminal device initiates random access and sends the random access message Msg3 to the network side device.
  • Msg3 is transmitted in the NTN network
  • the terminal device starts a contention resolution timer after the initial transmission of Msg. separate listening timer. While the listening timer is running, the terminal device can listen to the PDCCH.
  • the terminal device may monitor the TC-RNTI-based scheduling on the PDCCH, or may only monitor the TC-RNTI-based Msg3 retransmission scheduling.
  • the method provided by the embodiment of the present disclosure further includes: determining the duration of the listening timer based on the first system message or the first radio resource control RRC message sent by the network side device.
  • the terminal device can receive the first system message or the first RRC (radio resource control, radio resource control) message sent by the network side device, and then determine the timing length of the listening timer.
  • RRC radio resource control, radio resource control
  • the first system message of the network side device in LTE may be SIB31 (System Information Block), SIB1, or SIB2, etc.
  • the first system message of the network side device in NR can also be SIB19 or SIB1.
  • the first RRC message may be a connection reconfiguration message (including a handover command), a connection establishment message, a connection reestablishment message, a connection recovery message, or a connection release message, etc.
  • the terminal device initiates random access and sends the random access message Msg3 to the network side device.
  • Msg3 is transmitted in the NTN network
  • the terminal device starts monitoring after the initial transmission of Msg. timer.
  • the terminal device determines that the contention resolution was unsuccessful or does not consider that the contention resolution was unsuccessful, It is possible to avoid incorrect identification of end devices as contention resolution failures.
  • the listening timer may be a contention resolution timer.
  • the terminal device sends the random access message Msg3 to the network side device and performs the initial transmission of Msg3, it starts the contention resolution timer.
  • the contention resolution timer monitors the TC-RNTI-based scheduling on the PDCCH or only Monitor the retransmission schedule of Msg3 based on TC-RNTI.
  • the terminal device After the terminal device performs the initial transmission of Msg3, it starts the contention resolution timer. This may be to start the contention resolution timer immediately after the initial transmission of Msg3. That is, there is no need to delay the RTT time before starting the contention resolution timer.
  • the terminal device starts a contention resolution timer after the initial transmission of Msg, and then delays the RTT time after the initial transmission of Msg3, and then starts a contention resolution timer, and then the contention resolution timer runs. time, listen to the TC-RNTI-based scheduling or only listen to the TC-RNTI-based Msg3 retransmission scheduling on the PDCCH.
  • S61 and S62 can be implemented alone or in combination with any other step in the embodiment of the present disclosure.
  • they can be implemented in combination with S51 in the embodiment of the present disclosure.
  • the disclosed embodiments do not limit this.
  • the terminal device initiates random access and sends the random access message Msg3 to the network side device.
  • Msg3 is transmitted in the NTN network
  • the terminal device starts monitoring after the initial transmission of Msg. timer.
  • the terminal device determines that the contention resolution was unsuccessful or does not consider that the contention resolution was unsuccessful, It is possible to avoid incorrect identification of end devices as contention resolution failures.
  • Figure 7 is a flow chart of yet another random access method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • S71 In response to receiving the configuration information sent by the network side device, start the listening timer after the initial transmission of Msg3, where the configuration information is used to instruct the terminal device to perform blind retransmission scheduling of the initial transmission of Msg3.
  • the terminal equipment needs to additionally monitor the PDCCH, which will increase the power consumption of the terminal equipment.
  • the terminal device responds to receiving the configuration information sent by the network side device and starts the listening timer after the initial transmission of Msg3, where the configuration information is used to instruct the terminal device to perform blind retransmission of Msg3 initial transmission. Scheduling.
  • the terminal device when the terminal device receives the 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 the listening timer after the initial transmission of Msg. While the listening timer is running, the PDCCH is monitored to support the blind retransmission scheduling of Msg3 initial transmission.
  • the terminal device does not receive the configuration information of the network side device, after the initial transmission of Msg3, it is not necessary to start the listening timer and not to listen to the PDCCH, thereby saving the power consumption of the terminal device.
  • the terminal device when the terminal device receives the configuration information sent by the network side device, it may be receiving a second system message or a second radio resource control RRC message sent by the network side device.
  • the second system message of the network side device in LTE may be SIB31 (System Information Block), SIB1, or SIB2, etc.
  • the second system message of the network side device in NR can also be SIB19 or SIB1.
  • the second RRC message may be a connection reconfiguration message (including a handover command), a connection establishment message, a connection reestablishment message, a connection recovery message, or a connection release message, etc.
  • the terminal device if the terminal device supports blind retransmission scheduling for the initial transmission of Msg3, the terminal device starts the listening timer only after the initial transmission of Msg3, where the terminal device is in an idle state, a connected state, or an inactive state.
  • the terminal device can be in an idle state, an inactive state, or a connected state.
  • S72 Report capability information to the network side device, where the capability information is used to indicate that the terminal device supports blind retransmission scheduling for receiving Msg3 initial transmission.
  • the terminal device supports reporting capability information to the network side device, and the capability information is used to indicate that the terminal device supports blind retransmission scheduling for receiving Msg3 initial transmission.
  • the network side device can send the configuration information to enable blind retransmission scheduling of Msg3 initial transmission to the terminal device.
  • the capability information reported by the terminal device can be reported through Msg3/Msg5, or reported through the terminal device capability information RRC message.
  • the listening timer is started after Msg3 is initially transmitted, including at least one of the following:
  • the first Symbol After the initial transmission of Msg3, the first Symbol starts the listening timer, and Type A PUSCH repetition is not used to schedule Msg3.
  • the terminal device initiates random access and sends the random access message Msg3 to the network side device.
  • Msg3 is transmitted in the NTN network
  • the terminal device starts the listening timer after the initial transmission of Msg.
  • the terminal device can start the listening timer on the first Symbol after all repeated transmissions after the initial transmission of Msg3, in which Type A PUSCH repetition is used to schedule Msg3.
  • the terminal device initiates random access and sends the random access message Msg3 to the network side device.
  • Msg3 is transmitted in the NTN network
  • the terminal device starts the listening timer after the initial transmission of Msg.
  • the terminal device can start the listening timer on the first Symbol after Msg3 is initially transmitted.
  • Type A PUSCH repetition is not used to schedule Msg3.
  • S71 and S72 can be implemented alone, or can be implemented in combination with any other step in the embodiment of the present disclosure, for example, in combination with S51 and/or S61 in the embodiment of the present disclosure.
  • S62 is implemented together, and the embodiment of the present disclosure does not limit this.
  • Figure 8 is a flow chart of yet another random access method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • S81 Initiate random access and send the random access message Msg3 to the network side device.
  • S82 In response to Msg3 being transmitted in the NTN network, start a listening timer after the initial transmission of Msg3, where the listening timer is a contention resolution timer.
  • the contention resolution timer will be started.
  • the terminal device will monitor the PDCCH (physical Msg3 retransmission scheduling based on TC-RNTI (temporary cell radio network temporary identifier, temporary cell radio network temporary identifier) addressing on downlink control channel, physical downlink control channel, after the contention resolution timer times out, the terminal device will think Contention resolution was not successful.
  • PDCCH physical Msg3 retransmission scheduling based on TC-RNTI (temporary cell radio network temporary identifier, temporary cell radio network temporary identifier)
  • the terminal device sends the random access message Msg3 to the network side device and immediately starts (without delaying the RTT time) the contention resolution timer after the initial transmission of Msg3.
  • the terminal device does not receive the retransmission schedule of msg3 on the PDCCH during the running of the contention resolution timer, it cannot be considered that the contention resolution has failed.
  • the terminal equipment will also monitor the retransmission schedule of Msg3 on the PDCCH during the running of the contention resolution timer started by delaying the RTT after the initial transmission of Msg3.
  • the condition for judging contention resolution failure in the related art considers this situation as contention resolution failure.
  • the terminal device determines that the contention resolution is unsuccessful or does not consider that the contention resolution is unsuccessful in response to the timeout of the contention resolution timer and the second condition is met.
  • the terminal device initiates random access and sends the random access message Msg3 to the network side device; in response to Msg3 being transmitted in the NTN network, the listening timer is started after the initial transmission of Msg3, and the listening timer is contention Solve the timer.
  • the terminal device only determines that the contention resolution is unsuccessful or does not consider that the contention resolution is unsuccessful only when the contention resolution timer times out and the second condition is met.
  • the second condition may be a condition for determining that the contention resolution is not successful, or the second condition may be a condition for determining that the contention resolution is not considered to be unsuccessful. Therefore, whether the contention resolution is successful can be determined based on the second condition, and the terminal device can be prevented from mistakenly determining that the contention resolution has failed.
  • the second condition includes at least one of the following:
  • Msg3 retransmission scheduled based on the temporary cell radio network temporary identity TC-RNTI is not received on the physical downlink control channel PDCCH;
  • the contention resolution timer is started after the round-trip time RTT is delayed after Msg3 is sent, and the last time it is started before the contention resolution timer expires, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH;
  • the contention resolution timer is started after the RTT is delayed after Msg3 is sent, and after the contention resolution timer is started, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH;
  • the contention resolution timer will not be started, and no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH at the last start before the contention resolution timer expires;
  • the contention resolution timer will not be started, and no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH after the contention resolution timer is started.
  • the second condition may be that Msg3 retransmission scheduled based on the temporary cell radio network temporary identity TC-RNTI is not received on the physical downlink control channel PDCCH at the last start before the contention resolution timer expires. ;
  • 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. The terminal device times out when the contention resolution timer expires, and the above clause is satisfied.
  • determining that the contention resolution was unsuccessful or not considering that the contention resolution was unsuccessful can avoid the terminal device from mistakenly determining that the contention resolution has failed.
  • the second condition may be that the contention resolution timer is started after the round-trip time RTT is delayed after Msg3 is sent, and the last time it is started before the contention resolution timer times out, no message is received on the PDCCH Msg3 retransmission based on TC-RNTI scheduling; the terminal device initiates random access, sends the random access message Msg3 to the network side device in the NTN network, starts the contention resolution timer after the initial transmission of Msg3, and the terminal device is in contention
  • the resolution timer times out and the above second condition is met, determining that the contention resolution was unsuccessful or not considering the contention resolution as unsuccessful can avoid the terminal device from mistakenly determining that the contention resolution failed.
  • the second condition may be that the contention resolution timer is started after the RTT is delayed after the Msg3 is sent, and after the contention resolution timer is started, no TC-RNTI scheduled content is received on the PDCCH.
  • the second condition may be that the contention resolution timer will not be started, and the Msg3 reload based on TC-RNTI scheduling is not received on the PDCCH at the last start before the contention resolution timer times out. transmission; 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. The terminal device times out when the contention resolution timer expires, and the above conditions are met. In the case of the second condition, determining that the contention resolution is unsuccessful or not considering that the contention resolution is unsuccessful can avoid the terminal device from mistakenly determining that the contention resolution has failed.
  • 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 Initiate random access, send the random access message Msg3 to the network side device in the NTN network, start the contention resolution timer after the initial transmission of Msg3, and the terminal device times out when the contention resolution timer expires, and meets the second condition above In this case, determining that the contention resolution was unsuccessful or not considering the contention resolution to be unsuccessful can avoid the terminal device from incorrectly determining that the contention resolution failed.
  • the contention resolution timer can be started after the terminal device sends Msg3. After receiving at least one retransmission of Msg3 based on TC-RNTI scheduling on the PDCCH, after receiving the retransmission schedule of Msg3, the terminal device will send Msg3 again, and then start the contention resolution timer. This time, contention resolution is started. When the timer is set, the previously started contention resolution timer may not have expired. Based on this, the last start before the contention resolution timer expires can be determined.
  • the contention resolution timer will not be started because the terminal equipment does not receive the Msg3 retransmission based on the TC-RNTI schedule on the PDCCH. In the case of not receiving the Msg3 retransmission schedule, the contention resolution can be determined. The timer will not be started.
  • the second condition includes at least one of the following:
  • contention resolution timer times out before the first symbol Symbol plus RTT time after the initial transmission of Msg3;
  • the contention resolution timer times out before the first Symbol plus RTT time after the scheduled Msg3 retransmission ends;
  • the contention resolution timer times out before the first Symbol plus RTT time after all repeated transmissions of Msg3 initial transmission are completed, in which Type A physical uplink shared channel PUSCH is used to repeatedly schedule Msg3;
  • the contention resolution timer times out before the first Symbol plus RTT time after all repeated transmissions of the scheduled Msg3 retransmission, in which Type A PUSCH repetition is used to schedule Msg3;
  • the terminal equipment receives the retransmission schedule of Msg3 on the PDCCH, and the contention resolution timer times out before the first Symbol plus RTT time after the initial transmission of Msg3;
  • the terminal device receives the Msg3 retransmission schedule on the PDCCH, and the contention resolution timer times out before the first Symbol plus the RTT time after the Msg3 retransmission ends.
  • the second condition may be that the contention resolution timer times out before the first symbol Symbol plus RTT after the initial transmission of Msg3; the terminal device initiates random access and sends a request to the network side in the NTN network. The device sends the random access message Msg3 and starts the contention resolution timer after the initial transmission of Msg3.
  • the terminal device determines that the contention resolution has not been successful or does not consider it Unsuccessful contention resolution avoids the end device being incorrectly determined to have failed contention resolution.
  • the second condition may be that the contention resolution timer times out before the first Symbol plus RTT time after the scheduled Msg3 retransmission is completed; the terminal device initiates random access and sends a request to the network in the NTN network.
  • the side device sends the random access message Msg3 and starts the contention resolution timer after the initial transmission of Msg3.
  • the terminal device determines that the contention resolution has not been successful or failed. By considering contention resolution as unsuccessful, the terminal device may be prevented from incorrectly determining that contention resolution failed.
  • the second condition may be that the contention resolution timer times out before the first Symbol plus RTT time after all repeated transmissions of Msg3 initial transmission are completed, where Type A physical uplink shared channel PUSCH is used Repeatedly schedule Msg3; the terminal device initiates random access, sends the random access message Msg3 to the network side device in the NTN network, starts the contention resolution timer after the initial transmission of Msg3, and the terminal device times out during the contention resolution timer, and
  • the above second condition is met, determining that the contention resolution is unsuccessful or not considering that the contention resolution is unsuccessful can avoid the terminal device from mistakenly determining that the contention resolution has failed.
  • the second condition may be that the contention resolution timer times out before the first Symbol plus RTT time after all repeated transmissions of the scheduled Msg3 retransmission are completed, where Type A PUSCH repetition is used to 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. The terminal device times out when the contention resolution timer expires, and the above clause is satisfied.
  • determining that the contention resolution was unsuccessful or not considering that the contention resolution was unsuccessful can avoid the terminal device from mistakenly determining that the contention resolution has failed.
  • the second condition may 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 RTT time after the initial transmission of Msg3 ends; the terminal device The 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. The terminal device times out when the contention resolution timer expires and meets the second condition above. In this case, determining that the contention resolution was unsuccessful or not considering the contention resolution to be unsuccessful can avoid the terminal device from incorrectly determining that the contention resolution failed.
  • the second condition may 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 The 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. The terminal device times out when the contention resolution timer expires and meets the second condition above. In this case, determining that the contention resolution was unsuccessful or not considering the contention resolution to be unsuccessful can avoid the terminal device from incorrectly determining that the contention resolution failed.
  • the terminal device determines that the contention resolution is unsuccessful or does not consider the contention resolution to be unsuccessful in response to the contention resolution timer expiring in contention-based random access and meeting the first condition. Thus, it is possible to avoid the terminal device from being mistakenly determined as a contention resolution failure.
  • S81 to S83 can be implemented alone or in combination with any other step in the embodiment of the present disclosure, for example, in combination with S51 and/or S61 in the embodiment of the present disclosure.
  • S62 and/or S71 are implemented together with S72, and the embodiment of the present disclosure does not limit this.
  • the method provided by the embodiments of the present disclosure is introduced from the perspective of a terminal device.
  • the terminal device may include a hardware structure and a software module to implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • a certain function among the above functions can be executed by a hardware structure, a software module, or a hardware structure plus a software module.
  • FIG. 9 is a schematic structural diagram of a communication device 1 provided by an embodiment of the present disclosure.
  • the communication device 1 shown in FIG. 9 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
  • the receiving module is used to implement the receiving function.
  • the transceiving module may implement the sending function and/or the receiving function.
  • the communication device 1 may be a terminal device, a device in the terminal device, or a device that can be used in conjunction with the terminal device.
  • the communication device 1 is a terminal device:
  • the device includes: a processing module 12.
  • the processing module 12 is configured to determine that the contention resolution is unsuccessful or does not consider that the contention resolution is unsuccessful in response to the contention resolution timer expiring and the first condition being met in the contention-based random access.
  • the communication device 1 further includes: a transceiver module 11 .
  • the transceiver module 11 is configured to send a contention-based random access request to the network side device, where the random access request includes message Msg3.
  • the first condition includes at least one of the following:
  • Msg3 is transmitted in a non-terrestrial network NTN network, and the Msg3 retransmission scheduled based on the temporary cell radio network temporary identifier TC-RNTI is not received on the physical downlink control channel PDCCH at the last start before the contention resolution timer expires;
  • Msg3 is transmitted in the NTN network, and the contention resolution timer is started after the round-trip time delay RTT after Msg3 is sent, and the last time before the contention resolution timer times out, no TC-RNTI is received on the PDCCH Scheduled Msg3 retransmission;
  • Msg3 is transmitted in the NTN network, and the contention resolution timer is started after the RTT delay after Msg3 is sent, and after the contention resolution timer is started, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH;
  • the contention resolution timer When Msg3 is transmitted in the NTN network, the contention resolution timer will not be started, and the Msg3 retransmission based on TC-RNTI scheduling is not received on the PDCCH at the last start before the contention resolution timer expires;
  • the contention resolution timer 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.
  • the first condition includes at least one of the following:
  • the terminal device is in the NTN network, and the contention resolution timer times out before the first symbol Symbol plus RTT time after the initial transmission of Msg3;
  • the terminal device is in the NTN network, and the contention resolution timer times out before the first Symbol plus RTT time after the scheduled Msg3 retransmission ends;
  • the terminal device is in the NTN network, and the contention resolution timer times out before the first Symbol plus RTT time after all repeated transmissions of Msg3 initial transmission are completed, in which Type A physical uplink shared channel PUSCH is used to repeatedly schedule Msg3;
  • the terminal device is in the NTN network, and the contention resolution timer times out before the first Symbol plus RTT time after all repeated transmissions of the scheduled Msg3 retransmission, in which Type A PUSCH repetition is used to schedule Msg3;
  • 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;
  • 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 Msg3 retransmission ends.
  • the communication device 1 is a terminal device:
  • the device includes: a transceiver module 11 and a processing module 12.
  • the transceiver module 11 is configured to initiate random access and send a random access message Msg3 to the network side device.
  • the processing module 12 is configured to, in response to the Msg3 being transmitted in the NTN network, start a listening timer after the Msg3 is initially transmitted.
  • the listening timer is a separate timer, and the listening timer and the contention resolution timer are different timers.
  • the processing module 12 is also configured to listen to the PDCCH during the running of the listening timer.
  • the terminal device is in the discontinuous reception DRX active state.
  • the processing module 12 is also configured to monitor the TC-RNTI-based scheduling on the PDCCH or only monitor the retransmission scheduling of Msg3 based on the TC-RNTI.
  • the transceiver module 11 is further configured to determine the duration of the listening timer based on the first system message or the first radio resource control RRC message sent by the network side device.
  • the listening timer is a contention resolution timer, wherein the processing module 12 is also configured to listen to TC-RNTI-based scheduling or only listen to TC-RNTI-based scheduling on the PDCCH during the operation of the listening timer. Msg3 retransmission scheduling.
  • the processing module 12 is also configured to start a listening timer after the initial transmission of Msg3 in response to receiving the configuration information sent by the network side device, where the configuration information is used to instruct the terminal device to perform the initial transmission of Msg3. Blind retransmission scheduling.
  • the transceiver module 11 is further configured to receive a second system message or a second radio resource control RRC message sent by the network side device.
  • 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 the blind retransmission schedule of Msg3 initial transmission, wherein the terminal device is in an idle state or a connected state or is not. Activated state.
  • the transceiver module 11 is also configured to report capability information to the network side device, where the capability information is used to indicate that the terminal device supports blind retransmission scheduling for receiving Msg3 initial transmission.
  • the processing module 12 is also configured to start a listening timer after the initial transmission of Msg3, including at least one of the following:
  • the first Symbol After the initial transmission of Msg3, the first Symbol starts the listening timer, and Type A PUSCH repetition is not used to schedule Msg3.
  • the processing module 12 is further configured to, in response to the contention resolution timer expiration and the second condition being met, determine that the contention resolution was unsuccessful or not consider that the contention resolution was unsuccessful.
  • the second condition includes at least one of the following:
  • Msg3 retransmission scheduled based on the temporary cell radio network temporary identity TC-RNTI is not received on the physical downlink control channel PDCCH;
  • the contention resolution timer is started after the round-trip time RTT is delayed after Msg3 is sent, and the last time it is started before the contention resolution timer expires, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH;
  • the contention resolution timer is started after the RTT is delayed after Msg3 is sent, and after the contention resolution timer is started, no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH;
  • the contention resolution timer will not be started, and no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH at the last start before the contention resolution timer expires;
  • the contention resolution timer will not be started, and no Msg3 retransmission based on TC-RNTI scheduling is received on the PDCCH after the contention resolution timer is started.
  • the second condition includes at least one of the following:
  • contention resolution timer times out before the first symbol Symbol plus RTT time after the initial transmission of Msg3;
  • the contention resolution timer times out before the first Symbol plus RTT time after the scheduled Msg3 retransmission ends;
  • the contention resolution timer times out before the first Symbol plus RTT time after all repeated transmissions of Msg3 initial transmission are completed, in which Type A physical uplink shared channel PUSCH is used to repeatedly schedule Msg3;
  • the contention resolution timer times out before the first Symbol plus RTT time after all repeated transmissions of the scheduled Msg3 retransmission, in which Type A PUSCH repetition is used to schedule Msg3;
  • the terminal equipment receives the retransmission schedule of Msg3 on the PDCCH, and the contention resolution timer times out before the first Symbol plus RTT time after the initial transmission of Msg3;
  • the terminal device receives the Msg3 retransmission schedule on the PDCCH, and the contention resolution timer times out before the first Symbol plus the RTT time after the Msg3 retransmission ends.
  • the communication device 1 provided in the above embodiments of the present disclosure achieves the same or similar beneficial effects as the random access method provided in some of the above embodiments, and will not be described again here.
  • FIG. 10 is a schematic structural diagram of another communication device 1000 provided by an embodiment of the present disclosure.
  • the communication device 1000 may be a terminal device, or may be a chip, chip system, or processor that supports the terminal device to implement the above method.
  • the communication device 1000 can be used to implement the method described in the above method embodiment. For details, please refer to the description in the above method embodiment.
  • Communication device 1000 may include one or more processors 1001.
  • the processor 1001 may be a general-purpose processor or a special-purpose processor, or the like.
  • it can be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data
  • the central processor can be used to control and execute communication devices (such as network side equipment, baseband chips, terminal equipment, terminal equipment chips, DU or CU, etc.)
  • a computer program processes data for a computer program.
  • the communication device 1000 may also include one or more memories 1002, on which a computer program 1004 may be stored.
  • the memory 1002 executes the computer program 1004, so that the communication device 1000 performs the method described in the above method embodiment.
  • the memory 1002 may also store data.
  • the communication device 1000 and the memory 1002 can be provided separately or integrated together.
  • the communication device 1000 may also include a transceiver 1005 and an antenna 1006.
  • the transceiver 1005 may be called a transceiver unit, a transceiver, a transceiver circuit, etc., and is used to implement transceiver functions.
  • the transceiver 1005 may include a receiver and a transmitter.
  • the receiver may be called a receiver or a receiving circuit, etc., used to implement the receiving function;
  • the transmitter may be called a transmitter, a transmitting circuit, etc., used to implement the transmitting function.
  • the communication device 1000 may also 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 embodiment.
  • the communication device 1000 is a terminal device: the processor 1001 is used to execute S51 in Figure 5; S62 in Figure 6; S71 in Figure 7; S82 and S83 in Figure 8; and the transceiver 1005 is used to execute S61 in Figure 6 ; S71 in Figure 7; S81 in Figure 8.
  • the processor 1001 may include a transceiver for implementing receiving and transmitting functions.
  • the transceiver may be a transceiver circuit, an interface, or an interface circuit.
  • the transceiver circuits, interfaces or interface circuits used to implement the receiving and transmitting functions can be separate or integrated together.
  • the above-mentioned transceiver circuit, interface or interface circuit can be used for reading and writing codes/data, or the above-mentioned transceiver circuit, interface or interface circuit can be used for signal transmission or transfer.
  • the processor 1001 may store a computer program 1003, and the computer program 1003 runs on the processor 1001, causing the communication device 1000 to perform the method described in the above method embodiment.
  • the computer program 1003 may be solidified in the processor 1001, in which case the processor 1001 may be implemented by hardware.
  • the communication device 1000 may include a circuit, and the circuit may implement the functions of sending or receiving or communicating in the foregoing method embodiments.
  • the processors and transceivers described in this disclosure may be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed signal ICs, application specific integrated circuits (ASICs), printed circuit boards ( printed circuit board (PCB), electronic equipment, etc.
  • the processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), n-type metal oxide-semiconductor (NMOS), P-type Metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS n-type metal oxide-semiconductor
  • PMOS P-type Metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the communication device in the description of the above embodiments may be a terminal device, but the scope of the communication device described in the present disclosure is not limited thereto, and the structure of the communication device may not be limited by FIG. 10 .
  • the communication device may be a stand-alone device or may be part of a larger device.
  • the communication device may be:
  • the IC collection may also include storage components for storing data and computer programs;
  • FIG. 11 is a structural diagram of a chip provided in an embodiment of the present disclosure.
  • Chip 1100 includes processor 1101 and interface 1103.
  • the number of processors 1101 may be one or more, and the number of interfaces 1103 may be multiple.
  • Interface 1103, used to receive code instructions and transmit them to the processor.
  • the processor 1101 is configured to run code instructions to perform the random access method as described in some of the above embodiments.
  • the chip 1100 also includes a memory 1102, which is used to store necessary computer programs and data.
  • Embodiments of the present disclosure also provide a random access system.
  • the system includes a communication device as a terminal device in the aforementioned embodiment of FIG. 9 and a communication device as a network side device.
  • the system includes a communication device as a terminal device in the aforementioned embodiment of FIG. 10.
  • the communication device of the device and the communication device as the network side device.
  • the present disclosure also provides a readable storage medium on which instructions are stored, and when the instructions are executed by a computer, the functions of any of the above method embodiments are implemented.
  • the present disclosure also provides a computer program product, which, when executed by a computer, implements the functions of any of the above method embodiments.
  • the computer program product includes one or more computer programs.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer program may be stored in or transferred from one computer-readable storage medium to another, for example, the computer program may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more available media integrated therein.
  • the available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVD)), or semiconductor media (e.g., solid state disks, SSD)) etc.
  • magnetic media e.g., floppy disks, hard disks, magnetic tapes
  • optical media e.g., high-density digital video discs (DVD)
  • DVD digital video discs
  • semiconductor media e.g., solid state disks, SSD
  • At least one in the present disclosure can also be described as one or more, and the plurality can be two, three, four or more, and the present disclosure is not limited.
  • the technical feature is distinguished by “first”, “second”, “third”, “A”, “B”, “C” and “D” etc.
  • the technical features described in “first”, “second”, “third”, “A”, “B”, “C” and “D” are in no particular order or order.
  • each table in this disclosure can be configured or predefined.
  • the values of the information in each table are only examples and can be configured as other values, which is not limited by this disclosure.
  • it is not necessarily required to configure all the correspondences shown in each table.
  • the corresponding relationships shown in some rows may not be configured.
  • appropriate deformation adjustments can be made based on the above table, such as splitting, merging, etc.
  • the names of the parameters shown in the titles of the above tables may also be other names understandable by the communication device, and the values or expressions of the parameters may also be other values or expressions understandable by the communication device.
  • 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. wait.
  • Predefinition in this disclosure may be understood as definition, pre-definition, storage, pre-storage, pre-negotiation, pre-configuration, solidification, or pre-burning.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例公开了一种随机接入方法和装置，可应用于通信技术领域，其中，由终端设备执行的方法包括：终端设备响应于基于竞争的随机接入中，争用解决定时器超时，且满足第一条件，确定争用解决未成功或不认为争用解决未成功。由此，可以避免终端设备错误的确定为争用解决失败。

Description

随机接入方法和装置 技术领域
本公开涉及通信技术领域，尤其涉及一种随机接入方法和装置。
背景技术
在基于竞争的随机接入过程中，终端设备发送消息Msg3至网络侧设备后，会启动争用解决定时器，在该争用解决定时器运行期间，终端设备会监听PDCCH(physical downlink control channel，物理下行控制信道)上基于TC-RNTI(temporary cell radio network temporary identifier，临时小区无线网络临时标识)寻址的Msg3重传调度，在争用解决定时器超时后，终端设备会认为争用解决未成功。
然而，争用解决定时会因为多次收到Msg3的重传调度而被多次重启，在争用解决定时器重启之前，可能之前启动的争用解决定时器已经超时，此时终端设备会认为争用失败。但是，由于争用解决定时器还会在收到Msg3的重传调度进行重启，此时终端设备不应认为争用失败，这是亟需解决的问题。
发明内容
本公开实施例提供一种随机接入方法和装置，可以避免终端设备错误的确定为争用解决失败。
第一方面，本公开实施例提供一种随机接入方法，该方法由终端设备执行，该方法包括：响应于基于竞争的随机接入中，争用解决定时器超时，且满足第一条件，确定争用解决未成功或不认为争用解决未成功。
在该技术方案中，终端设备响应于基于竞争的随机接入中，争用解决定时器超时，且满足第一条件，确定争用解决未成功或不认为争用解决未成功。由此，可以避免终端设备错误的确定为争用解决失败。
第二方面，本公开实施例提供另一种随机接入方法，该方法由终端设备执行，该方法包括：发起随机接入，向网络侧设备发送随机接入的消息Msg3；响应于所述Msg3在NTN网络中传输，在Msg3初传后启动监听定时器。
第三方面，本公开实施例提供一种通信装置，该通信装置具有实现上述第一方面所述的方法中终端设备的部分或全部功能，比如通信装置的功能可具备本公开中的部分或全部实施例中的功能，也可以具备单独实施本公开中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该通信装置的结构中可包括收发模块和处理模块，所述处理模块被配置为支持通信装置执行上述方法中相应的功能。所述收发模块用于支持通信装置与其他设备之间的通信。所述通信装置还可以包括存储模块，所述存储模块用于与收发模块和处理模块耦合，其保存通信装置必要的计算机程序和数据。
在一种实现方式中，所述通信装置包括：处理模块，被配置为响应于基于竞争的随机接入中，争用解决定时器超时，且满足第一条件，确定争用解决未成功或不认为争用解决未成功。
第四方面，本公开实施例提供另一种通信装置，该通信装置具有实现上述第二方面所述的方法示例中终端设备的部分或全部功能，比如通信装置的功能可具备本公开中的部分或全部实施例中的功能，也可以具备单独实施本公开中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该通信装置的结构中可包括收发模块和处理模块，该处理模块被配置为支持通信装置执行上述方法中相应的功能。收发模块用于支持通信装置与其他设备之间的通信。所述通信装置还可以包括存储模块，所述存储模块用于与收发模块和处理模块耦合，其保存通信装置必要的计算机程序和数据。
在一种实现方式中，所述通信装置包括：收发模块，被配置为发起随机接入，向网络侧设备发送随机接入的消息Msg3；处理模块，被配置为响应于所述Msg3在NTN网络中传输，在Msg3初传后启动监听定时器。
第五方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第一方面所述的方法。
第六方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第二方面所述的方法。
第七方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第一方面所述的方法。
第八方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第二方面所述的方法。
第九方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第一方面所述的方法。
第十方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第二方面所述的方法。
第十一方面，本公开实施例提供一种随机接入系统，该系统包括第三方面所述的通信装置以及第四方面所述的通信装置，或者，该系统包括第五方面所述的通信装置以及第六方面所述的通信装置，或者，该系统包括第七方面所述的通信装置以及第八方面所述的通信装置，或者，该系统包括第九方面所述的通信装置以及第十方面所述的通信装置。
第十二方面，本发明实施例提供一种计算机可读存储介质，用于储存为上述终端设备所用的指令，当所述指令被执行时，使所述终端设备执行上述第一方面所述的方法。
第十三方面，本发明实施例提供一种可读存储介质，用于储存为上述终端设备所用的指令，当所述指令被执行时，使所述终端设备执行上述第二方面所述的方法。
第十四方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第十五方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
第十六方面，本公开提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持终端设备实现第一方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存终端设备必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十七方面，本公开提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持终端设备实现第二方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存终端设备必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十八方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第十九方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
附图说明
为了更清楚地说明本公开实施例或背景技术中的技术方案，下面将对本公开实施例或背景技术中所需要使用的附图进行说明。
图1是本公开实施例提供的一种NTN通信方式示意图；
图2是本公开实施例提供的另一种NTN通信方式示意图；
图3是本公开实施例提供的又一种NTN通信方式示意图；
图4是本公开实施例提供的一种通信系统的架构图；
图5是本公开实施例提供的一种随机接入方法的流程图；
图6是本公开实施例提供的另一种随机接入方法的流程图；
图7是本公开实施例提供的又一种随机接入方法的流程图；
图8是本公开实施例提供的又一种随机接入方法的流程图；
图9是本公开实施例提供的一种通信装置的结构图；
图10是本公开实施例提供的另一种通信装置的结构图；
图11是本公开实施例提供的一种芯片的结构示意图。
具体实施方式
为了便于理解本公开，此处对本公开实施例涉及到的部分概念作简单介绍。
1、随机接入(Random Access，RA)
随机接入过程是指从用户(终端设备)发送随机接入前导码开始尝试接入网络(网络侧设备)到与网络间建立起基本的信令连接之前的过程。随机接入是移动通信系统中非常关键的步骤，也是终端设备与网络侧设备建立通信链路的最后一步。终端设备可以通过随机接入与网络侧设备进行信息交互。其中，随机接入过程可以包括两步随机接入和四步随机接入。
其中，四步4step随机接入过程包括：终端设备通过第一条消息msg1发送随机接入前导码preamble；网络侧设备通过第二条消息msg2发送随机接入响应消息(Random AccessResponse，RAR)；终端设备通过第三条消息msg3发送无线资源控制(radio resourcecontrol，RRC)连接请求；终端设备通过第四条消息msg4接收RRC连接建立(此过程也即为竞争解决contention resolution过程)
两步2step随机接入过程包括：终端设备向网络侧设备发送的A消息msgA，网络侧设备向终端设备发送B消息msgB。其中，msgA中包含与四步随机接入中msg1及msg3等效的内容；msgB中包含与四步随机接入中msg2及msg4等效的内容。
其中，第三条消息(msg3)
4step随机接入过程中的第三条消息被称为Msg3，根据终端设备状态的不同和应用场景的不同，Msg3消息的内容也可能不同。Msg3中需要包含一个重要信息：每个终端设备唯一的标识，该标识将用于四步随机接入中的第四步竞争解决。
其中，在基于竞争的随机接入的过程中，终端设备在发送完msg3后，会启动争用解决定时器，在该定时器运行期间，终端设备会监听PDCCH上TC-RNTI寻址的msg3重传调度，或msg4的调度。在争用解决定时器超时后，终端设备认为争用解决未成功。
2、NTN(non-terrestrialnetworks，非地面网络)通信方式例如图1所示。
依据卫星处理信号的方式的不同，NTN通信可以分为透传模式和再生模式。
其中，透传模式如图2所示，NTN地面站将基站信号发送给卫星，卫星将信号转换到卫星频段后再通过卫星频段下发给终端(终端设备)，除了频率转换与信号放大，卫星不对基站信号解调。
再生模式如图3所示，NTN地面站将基站信号发送给卫星后，卫星先将信号进行解调译码后再重新编码调制，并通过卫星频段发送再生的信号。
下表1给出了典型NTN网络的卫星高度，轨道，卫星覆盖范围：
Figure PCTCN2022100244-appb-000001
表1
对于NTN，争用解决定时器是在msg3发送后再经过RTT(Round-Trip Time，往返时间)时间后启动的。
3、加扰
加扰，是数字信号的加工处理方法，用扰码与原始信号异或运算，从而得到新的信号。通常上行链路物理信道加扰的作用是区分不同的终端设备，下行链路加扰可以区分小区和信道。其中，扰码可用于对原始信号加扰和解扰。例如，扰码可以对下行控制信息(downlink control information，DCI)加扰，或者也可称为对PDCCH加扰。对DCI加扰具体可以指对DCI的循环冗余校验(cyclic redundancy check，CRC)字段进行加扰。相应地，终端设备对接收到的DCI进行解扰，具体是指终端设备对DCI的CRC字段使用相应类型的扰码进行解扰，以确定DCI的格式或者类型等。
扰码可以包括但不限于：小区无线网络临时标识(cell radio network temporary identifier，C-RNTI)、临时小区无线网络临时标识(temporary cell radio network temporary identifier，TC-RNTI)、随机接入无线网络临时标识(random accessradionetwork temporary identifier，RA-RNTI)、系统消息无线网络临时标识(system information radio network temporary identifier，SI-RNTI)和寻呼无线网络临时标识(paging radio network temporary identifier，P-RNTI)。
a)C-RNTI和TC-RNTI
若终端设备处于无线资源控制连接(radio resource control connected，RRC-connected)态，说明该 终端设备已经被分配到了C-RNTI，终端设备向网络侧设备发起随机接入请求时需要携带该C-RNTI。若终端设备处于RRC空闲(RRC idle)态或者RRC非活跃(RRC inactive)态，说明该终端设备还未被分配到C-RNTI。若终端设备请求RRC连接，网络侧设备在后续的响应信息里可能会给该终端设备分配一个临时C-RNTI，记为TC-RNTI，待该终端设备随机接入成功后，TC-RNTI可转化为C-RNTI。
b)RA-RNTI
在随机接入流程中，RA-RNTI的生成与终端设备发送前导码所用的时频资源相关。例如，当终端设备A和终端设备B使用同一个随机接入信道时频资源发起随机接入时，对应的RA-RNTI相同。
4、PUSCH(physical uplink share channel，物理上行共享信道)的映射类型(mapping type)
PUSCH包括两种mapping type，分别为：类型Type A和类型Type B。mapping type可以理解为资源分配类型。在NR的通信标准中，Type A和Type B都指示了起始符号(标识为S)，符号长度(标识为L)，以及S+L的可能值范围，示例性的，第三代合作伙伴计划(3rd generationpartnership project，3GPP)技术规范(Tchnology Standard，TS)38.214中6.1.2.1章节中的表6.1.2.1-1(本公开中记为表2)示出了Type A和Type B下，有效的S和L的组合(Valid Sand L conbinations)。
下表2：有效的S和L的组合
Figure PCTCN2022100244-appb-000002
表2
其中，Type A一行的参数仅适用于Type A的重复发送(repetition Type Aonly)。Type B一行的S+L一列中的“{1,…,14}”和“{1,…,12}”适用于Type A的重复发送(for repetition Type A)，Type B一行的S+L一列中的“{1,…,27}”和“{1,…,23}”适用于Type B的重复发送(for repetition TypeB)。
5、PUSCH的重复发送
PUSCH的重复发送是指发送多个PUSCH，多个PUSCH为多份相同的上行数据。一个PUSCH(即一份上行数据)的发送可以称为PUSCH的一次重复发送。多份相同的上行数据是指同一份系统比特经过信道编码之后所得到的多份相同或不同的RV(redundancy version，冗余版本)。
针对Type B，通信标准引入参数“重复次数(numberOfRepetitions-r16)”配置重复次数，numberOfRepetitions-r16共有8个可配置值，由3bit指示，这3bit的各种值依次对应{n1,n2,n3,n4,n7,n8,n12,n16}，n之后的数值表示重复次数，例如，n1表明发送1次，n16表明发送16次。网络设备可以通过高层信令，例如，RRC信令，为终端设备配置上述8个可配置值中的一个值，从而为终端设备指示重复次数。针对Type B，从重复发送PUSCH的起始时隙中的起始符号S开始，L*numberOfRepetitions-r16个可用符号，均用于PUSCH的重复发送。本申请中的“*”是指“乘以”。
针对Type A，S+L是小于或等于14的。当终端设备被配置了重复次数(假设为R1)时，终端设备会在R1个时隙(从起始时隙开始的连续R1个时隙)中的每个时隙进行检测，当某个时隙内从起始符号S开始的L个符号均为可用符号，则在该时隙上发送PUSCH，否则放弃在该时隙上发送PUSCH，继续看其他时隙是否满足条件。
为了更好的理解本公开实施例公开的一种随机接入方法和装置，下面首先对本公开实施例适用的通信系统进行描述。
请参见图4，图4为本公开实施例提供的一种通信系统的架构示意图。该通信系统可包括但不限于一个网络侧设备和一个终端设备，图4所示的设备数量和形态仅用于举例并不构成对本公开实施例的限定，实际应用中可以包括两个或两个以上的网络侧设备，两个或两个以上的终端设备。图4所示的通信系统10以包括一个网络侧设备101和一个终端设备102为例。
需要说明的是，本公开实施例的技术方案可以应用于各种通信系统。例如：长期演进(long term evolution，LTE)系统、第五代(5th generation，5G)移动通信系统、5G新空口(new radio，NR)系统，或者其他未来的新型移动通信系统等。还需要说明的是，本公开实施例中的侧链路还可以称为侧行链路或直通链路。
本公开实施例中的网络侧设备101是网络侧的一种用于发射或接收信号的实体。例如，网络侧设备101可以为演进型基站(evolved NodeB，eNB)、传输点(transmission reception point，TRP)、NR系统中的下一代基站(next generation NodeB，gNB)、其他未来移动通信系统中的基站或无线保真(wireless fidelity，WiFi)系统中的接入节点等。本公开的实施例对基站所采用的具体技术和具体设备形态不做限定。本公开实施例提供的基站可以是由集中单元(central unit，CU)与分布式单元(distributed unit，DU)组成的，其中，CU也可以称为控制单元(control unit)，采用CU-DU的结构可以将基站，例如基站的协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU。
本公开实施例中的终端设备102是用户侧的一种用于接收或发射信号的实体，如手机。终端设备也可以称为终端设备(terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端设备(mobile terminal，MT)等。终端设备可以是具备通信功能的汽车、智能汽车、手机(mobile phone)、穿戴式设备、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self-driving)中的无线终端设备、远程手术(remote medical surgery)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smart home)中的无线终端设备等等。本公开的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
可以理解的是，本公开实施例描述的通信系统是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提供的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本公开实施例提供的技术方案对于类似的技术问题，同样适用。
下面结合附图对本公开所提供的一种随机接入方法和装置进行详细地介绍。
请参见图5，图5是本公开实施例提供的一种随机接入方法的流程图。
如图5所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S51：响应于基于竞争的随机接入中，争用解决定时器超时，且满足第一条件，确定争用解决未成功或不认为争用解决未成功。
在一些实施例中，终端设备进行基于竞争的随机接入过程，向网络侧设备发送基于竞争的随机接入 请求，其中，随机接入请求中包括消息Msg3。
本公开实施例中，终端设备进行基于竞争的随机接入过程，终端设备向网络侧设备发送消息Msg3后，会启动争用解决定时器(ra-ContentionResolutionTimer)在该争用解决定时器运行期间，终端设备会监听PDCCH(physical downlink control channel，物理下行控制信道)上基于TC-RNTI(temporary cell radio network temporary identifier，临时小区无线网络临时标识)寻址的Msg3重传调度，或消息Msg4的调度，在争用解决定时器超时后，并且在满足第一条件的情况下，确定争用解决未成功，或者，确定不认为争用解决未成功。
其中，第一条件可以为确定争用解决未成功的条件，或者，第一条件还可以为确定不认为争用解决未成功的条件。从而，可以根据第一条件确定争用解决是否成功，可以避免终端设备错误的确定为争用解决失败。
在一些实施例中，第一条件，包括以下至少一个：
Msg3在非陆地网络NTN网络中传输，且在争用解决定时器超时前的最后一次启动，未在物理下行控制信道PDCCH上接收到基于临时小区无线网络临时标识TC-RNTI调度的Msg3重传；
Msg3在NTN网络中传输，且争用解决定时器是在Msg3发送后延迟往返时间RTT后启动的，且在争用解决定时器超时前的最后一次启动，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；
Msg3在NTN网络中传输，且争用解决定时器是在Msg3发送后延迟RTT后启动的，且在争用解决定时器启动后，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；
Msg3在NTN网络中传输，争用解决定时器不将被启动，且在争用解决定时器超时前的最后一次启动，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；
Msg3在NTN网络中传输，争用解决定时器不将被启动，且在争用解决定时器启动后，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传。
本公开实施例中，第一条件可以为，Msg3在非陆地网络NTN网络中传输，且在争用解决定时器超时前的最后一次启动，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传。终端设备在基于竞争的随机接入中，争用解决定时器超时，且满足上述第一条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
本公开实施例中，第一条件可以为，Msg3在NTN网络中传输，且争用解决定时器是在Msg3发送后延迟往返时间RTT后启动的，且在争用解决定时器超时前的最后一次启动，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；终端设备在基于竞争的随机接入中，争用解决定时器超时，且满足上述第一条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
本公开实施例中，第一条件可以为，Msg3在NTN网络中传输，且争用解决定时器是在Msg3发送后延迟RTT后启动的，且在争用解决定时器启动后，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；终端设备在基于竞争的随机接入中，争用解决定时器超时，且满足上述第一条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
本公开实施例中，第一条件可以为，Msg3在NTN网络中传输，争用解决定时器不将被启动，且在争用解决定时器超时前的最后一次启动，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；终端设备在基于竞争的随机接入中，争用解决定时器超时，且满足上述第一条件的情况下，确定争用解 决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
本公开实施例中，第一条件可以为，Msg3在NTN网络中传输，争用解决定时器不将被启动，且在争用解决定时器启动后，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传。终端设备在基于竞争的随机接入中，争用解决定时器超时，且满足上述第一条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
其中，争用解决定时器超时前的最后一次启动，可以为终端设备发送Msg3后，启动争用解决定时器。在PDCCH上接收到基于TC-RNTI调度的至少一次Msg3重传之后，在接收到Msg3的重传调度之后，终端设备会再次发送Msg3，之后再启动争用解决定时器，此次启动争用解决定时器时，之前启动的争用解决定时器可能还未超时，基于此，可以确定争用解决定时器超时前的最后一次启动。
其中，争用解决定时器不将被启动，可以为终端设备未在PDCCH上接收到基于TC-RNTI调度的Msg3重传，在未接收到Msg3的重传调度的情况下，可以确定争用解决定时器不将被启动。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在一些实施例中，第一条件，包括以下至少一个：
终端设备在NTN网络中，且争用解决定时器在Msg3初传结束后的第一个符号Symbol加上RTT时刻之前超时；
终端设备在NTN网络中，且争用解决定时器在调度的Msg3重传结束后的第一个Symbol加上RTT时刻之前超时；
终端设备在NTN网络中，且争用解决定时器在Msg3初传的所有重复传输结束后的第一个Symbol加上RTT时刻之前超时，其中，采用类型Type A物理上行共享信道PUSCH重复调度Msg3；
终端设备在NTN网络中，且争用解决定时器在调度的Msg3重传的所有重复传输结束后的第一个Symbol加上RTT时刻之前超时，其中，采用Type A PUSCH repetition调度Msg3；
终端设备在NTN网络中，且终端设备在PDCCH上收到Msg3的重传调度，且争用解决定时器在Msg3初传结束后的第一个Symbol加上RTT时刻之前超时；
终端设备在NTN网络中，且终端设备在PDCCH上收到Msg3的重传调度，且争用解决定时器在Msg3重传结束后的第一个Symbol加上RTT时刻之前超时。
本公开实施例中，第一条件可以为，终端设备在NTN网络中，且争用解决定时器在Msg3初传结束后的第一个符号Symbol加上RTT时刻之前超时。终端设备在基于竞争的随机接入中，争用解决定时器超时，且满足上述第一条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
本公开实施例中，第一条件可以为，终端设备在NTN网络中，且争用解决定时器在调度的Msg3重传结束后的第一个Symbol加上RTT时刻之前超时；终端设备在基于竞争的随机接入中，争用解决定时器超时，且满足上述第一条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
本公开实施例中，第一条件可以为，终端设备在NTN网络中，且争用解决定时器在Msg3初传的所有重复传输结束后的第一个Symbol加上RTT时刻之前超时，其中，采用类型Type A物理上行共享信道PUSCH重复调度Msg3；终端设备在基于竞争的随机接入中，争用解决定时器超时，且满足上述 第一条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
本公开实施例中，第一条件可以为，终端设备在NTN网络中，且争用解决定时器在调度的Msg3重传的所有重复传输结束后的第一个Symbol加上RTT时刻之前超时，其中，采用Type A PUSCH repetition调度Msg3；终端设备在基于竞争的随机接入中，争用解决定时器超时，且满足上述第一条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
本公开实施例中，第一条件可以为，终端设备在NTN网络中，且终端设备在PDCCH上收到Msg3的重传调度，且争用解决定时器在Msg3初传结束后的第一个Symbol加上RTT时刻之前超时；终端设备在基于竞争的随机接入中，争用解决定时器超时，且满足上述第一条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
本公开实施例中，第一条件可以为，终端设备在NTN网络中，且终端设备在PDCCH上收到Msg3的重传调度，且争用解决定时器在Msg3重传结束后的第一个Symbol加上RTT时刻之前超时。终端设备在基于竞争的随机接入中，争用解决定时器超时，且满足上述第一条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
通过实施本公开实施例，终端设备响应于基于竞争的随机接入中，争用解决定时器超时，且满足第一条件，确定争用解决未成功或不认为争用解决未成功。由此，可以避免终端设备错误的确定为争用解决失败。
请参见图6，图6是本公开实施例提供的另一种随机接入方法的流程图。
如图6所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S61：发起随机接入，向网络侧设备发送随机接入的消息Msg3。
S62：响应于Msg3在NTN网络中传输，在Msg3初传后启动监听定时器。
本公开实施例中，终端设备发起随机接入，向网络侧设备发送随机接入的消息Msg3，在Msg3在NTN网络中传输的情况下，终端设备在Msg初传后启动监听定时器。
其中，终端设备可以在Msg3初传后启动监听定时器，以实现终端设备支持Msg3的初传的盲重传调度。
在一些实施例中，本公开实施例中，监听定时器为一个单独的定时器，该监听定时器与争用解决定时器为不同的定时器。
本公开实施例中，终端设备发起随机接入，向网络侧设备发送随机接入的消息Msg3，在Msg3在NTN网络中传输的情况下，终端设备在Msg初传后启动一个争用解决定时器以外的单独的监听定时器。从而终端设备能够支持Msg3的初传的盲重传调度。
在一些实施例中，在监听定时器运行期间，监听PDCCH。
本公开实施例中，终端设备发起随机接入，向网络侧设备发送随机接入的消息Msg3，在Msg3在NTN网络中传输的情况下，终端设备在Msg初传后启动一个争用解决定时器以外的单独的监听定时器。在监听定时器运行期间，终端设备可以监听PDCCH。
在一些实施例中，终端设备处于非连续接收DRX激活active状态。
本公开实施例中，终端设备发起随机接入，向网络侧设备发送随机接入的消息Msg3，在Msg3在NTN网络中传输的情况下，终端设备在Msg初传后启动一个争用解决定时器以外的单独的监听定时器。在监听定时器运行期间，终端设备处于非连续接收DRX(discontinuous reception，非连续接收)激活active状态，终端设备在监听定时器运行期间，还可以监听PDCCH。
在一些实施例中，监听PDCCH，包括：在PDCCH上监听基于TC-RNTI的调度或仅监听基于TC-RNTI的Msg3的重传调度。
本公开实施例中，终端设备发起随机接入，向网络侧设备发送随机接入的消息Msg3，在Msg3在NTN网络中传输的情况下，终端设备在Msg初传后启动一个争用解决定时器以外的单独的监听定时器。在监听定时器运行期间，终端设备可以监听PDCCH。其中，终端设备可以在PDCCH上监听基于TC-RNTI的调度，或者还可以仅监听基于TC-RNTI的Msg3的重传调度。
在一些实施例中，本公开实施例提供的方法，还包括：基于网络侧设备发送的第一系统消息或第一无线资源控制RRC消息，确定监听定时器的定时时长。
本公开实施例中，终端设备可以接收网络侧设备发送的第一系统消息或第一RRC(radio resource control，无线资源控制)消息，进而确定监听定时器的定时时长。
其中，LTE(long term evolution，长期演进)中的网络侧设备的第一系统消息可以为SIB31(System Information Block，系统信息块)、SIB1、或SIB2等。NR(new radio，新无线)中的网络侧设备的第一系统消息还可以为SIB19或SIB1。第一RRC消息可以为连接重配消息(包括切换命令)，或连接建立消息，或连接重建消息，或连接恢复消息，或连接释放消息等。
需要说明的是，本公开实施例中，终端设备发起随机接入，向网络侧设备发送随机接入的消息Msg3，在Msg3在NTN网络中传输的情况下，终端设备在Msg初传后启动监听定时器。并且，终端设备在基于竞争的随机接入中，争用解决定时器超时，且满足上面一些实施例中的第一条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
在一些实施例中，监听定时器可以为争用解决定时器。终端设备在向网络侧设备发送随机接入的消息Msg3，进行Msg3初传后，启动争用解决定时器，在该争用解决定时器运行时间，在PDCCH上监听基于TC-RNTI的调度或仅监听基于TC-RNTI的Msg3的重传调度。
其中，终端设备进行Msg3初传后，启动争用解决定时器，可以为在Msg3初传后立即启动争用解决定时器，也即，不必延迟RTT时间后再启动。
可以理解的是，终端设备在进行Msg初传后，启动一个争用解决定时器，之后在Msg3初传后延迟RTT时间后，再启动一个争用解决定时器，在该争用解决定时器运行时间，在PDCCH上监听基于TC-RNTI的调度或仅监听基于TC-RNTI的Msg3的重传调度。
需要说明的是，本公开实施例中，S61和S62可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S51一起被实施，本公开实施例并不对此做出限定。
需要说明的是，本公开实施例中，终端设备发起随机接入，向网络侧设备发送随机接入的消息Msg3，在Msg3在NTN网络中传输的情况下，终端设备在Msg初传后启动监听定时器。并且，终端设备在基于竞争的随机接入中，争用解决定时器超时，且满足上面一些实施例中的第一条件的情况下，确定争用 解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
请参见图7，图7是本公开实施例提供的又一种随机接入方法的流程图。
如图7所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S71：响应于接收到网络侧设备发送的配置信息，在Msg3初传后启动监听定时器，其中，配置信息用于指示终端设备进行Msg3初传的盲重传调度。
可以想到的是，终端设备支持Msg3初传的盲重传调度，终端需要额外监听PDCCH，会增加终端设备的功耗。
基于此，本公开实施例中，终端设备响应于接收到网络侧设备发送的配置信息，在Msg3初传后启动监听定时器，其中，配置信息用于指示终端设备进行Msg3初传的盲重传调度。
本公开实施例中，终端设备在接收到网络侧设备发送的配置信息，配置信息指示终端设备进行Msg3初传的盲重传调度的情况下，终端设备在Msg初传后启动监听定时器，在监听定时器运行期间，监听PDCCH，以支持Msg3初传的盲重传调度。
其中，终端设备在未接收到网络侧设备的配置信息的情况下，在Msg3初传后，可以不启动监听定时器，可以不监听PDCCH，从而节省终端设备的功耗。
在一些实施例中，终端设备接收到网络侧设备发送的配置信息，可以为接收到网络侧设备发送的第二系统消息或第二无线资源控制RRC消息。
其中，LTE(long term evolution，长期演进)中的网络侧设备的第二系统消息可以为SIB31(System Information Block，系统信息块)、SIB1、或SIB2等。NR(new radio，新无线)中的网络侧设备的第二系统消息还可以为SIB19或SIB1。第二RRC消息可以为连接重配消息(包括切换命令)，或连接建立消息，或连接重建消息，或连接恢复消息，或连接释放消息等。
在一些实施例中，终端设备支持Msg3初传的盲重传调度的情况下，终端设备才在Msg3初传后启动监听计时器，其中，终端设备处于空闲态或连接态或非激活态。
本公开实施例中，终端设备可以在空闲态idle/非激活态inactive/连接态connected状态。
S72：向网络侧设备上报能力信息，其中，能力信息用于指示终端设备支持接收Msg3初传的盲重传调度。
本公开实施例中，终端设备支持向网络侧设备上报能力信息，能力信息用于指示终端设备支持接收Msg3初传的盲重传调度。
基于此，网络侧设备在收到终端设备上报的能力信息后，可以向终端设备发送使能Msg3初传的盲重传调度的配置信息。终端设备上报能力信息可以通过Msg3/Msg5携带进行上报，或者通过终端设备能力信息RRC消息来上报。
在一些实施例中，在Msg3初传后启动监听定时器，包括以下至少一个：
在Msg3初传后的所有重复传输结束后的第一个Symbol启动监听定时器，其中，采用Type A PUSCH repetition调度Msg3；
在Msg3初传后第一个Symbol启动监听定时器，其中，未采用Type A PUSCH repetition调度Msg3。
本公开实施例中，终端设备发起随机接入，向网络侧设备发送随机接入的消息Msg3，在Msg3在NTN网络中传输的情况下，终端设备在Msg初传后启动监听定时器。其中，终端设备可以在Msg3初 传后的所有重复传输结束后的第一个Symbol启动监听定时器，其中，采用Type A PUSCH repetition调度Msg3。
本公开实施例中，终端设备发起随机接入，向网络侧设备发送随机接入的消息Msg3，在Msg3在NTN网络中传输的情况下，终端设备在Msg初传后启动监听定时器。其中，终端设备可以在Msg3初传后第一个Symbol启动监听定时器，其中，未采用Type A PUSCH repetition调度Msg3。
需要说明的是，本公开实施例中，S71与S72可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S51和/或S61与S62一起被实施，本公开实施例并不对此做出限定。
请参见图8，图8是本公开实施例提供的又一种随机接入方法的流程图。
如图8所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S81：发起随机接入，向网络侧设备发送随机接入的消息Msg3。
S82：响应于Msg3在NTN网络中传输，在Msg3初传后启动监听定时器，其中，监听定时器为争用解决定时器。
S83：响应于争用解决定时器超时，且满足第二条件，确定争用解决未成功或不认为争用解决未成功。
相关技术中，在基于竞争的随机接入过程中，终端设备发送消息Msg3至网络侧设备后，会启动争用解决定时器，在该争用解决定时器运行期间，终端设备会监听PDCCH(physical downlink control channel，物理下行控制信道)上基于TC-RNTI(temporary cell radio network temporary identifier，临时小区无线网络临时标识)寻址的Msg3重传调度，在争用解决定时器超时后，终端设备会认为争用解决未成功。
然而，在监听定时器为争用解决定时器的情况下，终端设备在向网络侧设备发送随机接入的消息Msg3，进行Msg3初传后，立即启动(不延迟RTT时间)争用解决定时器，如果终端设备在该争用解决定时器运行期间未收到PDCCH上的msg3的重传调度的话，是不能认为争用解决失败的。因为终端设备还会在Msg3初传后延迟RTT而启动的争用解决定时器运行期间监听PDCCH上的Msg3的重传调度。但是，相关技术中的判断争用解决未成功的条件会将该情况认为争用解决失败。
基于此，本公开实施例中，终端设备响应于争用解决定时器超时，且满足第二条件，确定争用解决未成功或不认为争用解决未成功。
本公开实施例中，终端设备发起随机接入，向网络侧设备发送随机接入的消息Msg3；响应于Msg3在NTN网络中传输，在Msg3初传后启动监听定时器，监听定时器为争用解决定时器。其中，终端设备在争用解决定时器超时，且满足第二条件的情况下，才确定争用解决未成功或不认为争用解决未成功。
其中，第二条件可以为确定争用解决未成功的条件，或者，第二条件还可以为确定不认为争用解决未成功的条件。从而，可以根据第二条件确定争用解决是否成功，可以避免终端设备错误的确定为争用解决失败。
在一些实施例中，第二条件，包括以下至少一个：
在争用解决定时器超时前的最后一次启动，未在物理下行控制信道PDCCH上接收到基于临时小区无线网络临时标识TC-RNTI调度的Msg3重传；
争用解决定时器是在Msg3发送后延迟往返时间RTT后启动的，且在争用解决定时器超时前的最后一次启动，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；
争用解决定时器是在Msg3发送后延迟RTT后启动的，且在争用解决定时器启动后，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；
争用解决定时器不将被启动，且在争用解决定时器超时前的最后一次启动，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；
争用解决定时器不将被启动，且在争用解决定时器启动后，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传。
本公开实施例中，第二条件可以为，在争用解决定时器超时前的最后一次启动，未在物理下行控制信道PDCCH上接收到基于临时小区无线网络临时标识TC-RNTI调度的Msg3重传；终端设备发起随机接入，在NTN网络中向网络侧设备发送随机接入的消息Msg3，在Msg3初传后启动争用解决定时器，终端设备在争用解决定时器超时，且满足上述第二条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
本公开实施例中，第二条件可以为，争用解决定时器是在Msg3发送后延迟往返时间RTT后启动的，且在争用解决定时器超时前的最后一次启动，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；终端设备发起随机接入，在NTN网络中向网络侧设备发送随机接入的消息Msg3，在Msg3初传后启动争用解决定时器，终端设备在争用解决定时器超时，且满足上述第二条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
本公开实施例中，第二条件可以为，争用解决定时器是在Msg3发送后延迟RTT后启动的，且在争用解决定时器启动后，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；终端设备发起随机接入，在NTN网络中向网络侧设备发送随机接入的消息Msg3，在Msg3初传后启动争用解决定时器，终端设备在争用解决定时器超时，且满足上述第二条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
本公开实施例中，第二条件可以为，争用解决定时器不将被启动，且在争用解决定时器超时前的最后一次启动，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；终端设备发起随机接入，在NTN网络中向网络侧设备发送随机接入的消息Msg3，在Msg3初传后启动争用解决定时器，终端设备在争用解决定时器超时，且满足上述第二条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
本公开实施例中，第二条件可以为，争用解决定时器不将被启动，且在争用解决定时器启动后，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；终端设备发起随机接入，在NTN网络中向网络侧设备发送随机接入的消息Msg3，在Msg3初传后启动争用解决定时器，终端设备在争用解决定时器超时，且满足上述第二条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
其中，争用解决定时器超时前的最后一次启动，可以为终端设备发送Msg3后，启动争用解决定时器。在PDCCH上接收到基于TC-RNTI调度的至少一次Msg3重传之后，在接收到Msg3的重传调度之后，终端设备会再次发送Msg3，之后再启动争用解决定时器，此次启动争用解决定时器时，之前启动的争用解决定时器可能还未超时，基于此，可以确定争用解决定时器超时前的最后一次启动。
其中，争用解决定时器不将被启动，可以为终端设备未在PDCCH上接收到基于TC-RNTI调度的Msg3重传，在未接收到Msg3的重传调度的情况下，可以确定争用解决定时器不将被启动。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在一些实施例中，第二条件，包括以下至少一个：
争用解决定时器在Msg3初传结束后的第一个符号Symbol加上RTT时刻之前超时；
争用解决定时器在调度的Msg3重传结束后的第一个Symbol加上RTT时刻之前超时；
争用解决定时器在Msg3初传的所有重复传输结束后的第一个Symbol加上RTT时刻之前超时，其中，采用类型Type A物理上行共享信道PUSCH重复调度Msg3；
争用解决定时器在调度的Msg3重传的所有重复传输结束后的第一个Symbol加上RTT时刻之前超时，其中，采用Type A PUSCH repetition调度Msg3；
终端设备在PDCCH上收到Msg3的重传调度，且争用解决定时器在Msg3初传结束后的第一个Symbol加上RTT时刻之前超时；
终端设备在PDCCH上收到Msg3的重传调度，且争用解决定时器在Msg3重传结束后的第一个Symbol加上RTT时刻之前超时。
本公开实施例中，第二条件可以为，争用解决定时器在Msg3初传结束后的第一个符号Symbol加上RTT时刻之前超时；终端设备发起随机接入，在NTN网络中向网络侧设备发送随机接入的消息Msg3，在Msg3初传后启动争用解决定时器，终端设备在争用解决定时器超时，且满足上述第二条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
本公开实施例中，第二条件可以为，争用解决定时器在调度的Msg3重传结束后的第一个Symbol加上RTT时刻之前超时；终端设备发起随机接入，在NTN网络中向网络侧设备发送随机接入的消息Msg3，在Msg3初传后启动争用解决定时器，终端设备在争用解决定时器超时，且满足上述第二条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
本公开实施例中，第二条件可以为，争用解决定时器在Msg3初传的所有重复传输结束后的第一个Symbol加上RTT时刻之前超时，其中，采用类型Type A物理上行共享信道PUSCH重复调度Msg3；终端设备发起随机接入，在NTN网络中向网络侧设备发送随机接入的消息Msg3，在Msg3初传后启动争用解决定时器，终端设备在争用解决定时器超时，且满足上述第二条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
本公开实施例中，第二条件可以为，争用解决定时器在调度的Msg3重传的所有重复传输结束后的第一个Symbol加上RTT时刻之前超时，其中，采用Type A PUSCH repetition调度Msg3；终端设备发起随机接入，在NTN网络中向网络侧设备发送随机接入的消息Msg3，在Msg3初传后启动争用解决定时器，终端设备在争用解决定时器超时，且满足上述第二条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
本公开实施例中，第二条件可以为，终端设备在PDCCH上收到Msg3的重传调度，且争用解决定时器在Msg3初传结束后的第一个Symbol加上RTT时刻之前超时；终端设备发起随机接入，在NTN网络中向网络侧设备发送随机接入的消息Msg3，在Msg3初传后启动争用解决定时器，终端设备在争 用解决定时器超时，且满足上述第二条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
本公开实施例中，第二条件可以为，终端设备在PDCCH上收到Msg3的重传调度，且争用解决定时器在Msg3重传结束后的第一个Symbol加上RTT时刻之前超时；终端设备发起随机接入，在NTN网络中向网络侧设备发送随机接入的消息Msg3，在Msg3初传后启动争用解决定时器，终端设备在争用解决定时器超时，且满足上述第二条件的情况下，确定争用解决未成功或不认为争用解决未成功，可以避免终端设备错误的确定为争用解决失败。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
通过实施本公开实施例，终端设备响应于基于竞争的随机接入中，争用解决定时器超时，且满足第一条件，确定争用解决未成功或不认为争用解决未成功。由此，可以避免终端设备错误的确定为争用解决失败。
需要说明的是，本公开实施例中，S81至S83可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S51和/或S61与S62和/或S71与S72一起被实施，本公开实施例并不对此做出限定。
上述本公开提供的实施例中，从终端设备的角度对本公开实施例提供的方法进行了介绍。为了实现上述本公开实施例提供的方法中的各功能，终端设备可以包括硬件结构、软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能可以以硬件结构、软件模块、或者硬件结构加软件模块的方式来执行。
请参见图9，为本公开实施例提供的一种通信装置1的结构示意图。图9所示的通信装置1可包括收发模块11和处理模块12。收发模块可包括发送模块和/或接收模块，发送模块用于实现发送功能，接收模块用于实现接收功能，收发模块可以实现发送功能和/或接收功能。
通信装置1可以是终端设备，也可以是终端设备中的装置，还可以是能够与终端设备匹配使用的装置。
在一些实施例中，通信装置1为终端设备：
该装置，包括：处理模块12。
处理模块12，被配置为响应于基于竞争的随机接入中，争用解决定时器超时，且满足第一条件，确定争用解决未成功或不认为争用解决未成功。
在一些实施例中，通信装置1，还包括：收发模块11。
收发模块11，被配置为向网络侧设备发送基于竞争的随机接入请求，其中，随机接入请求包括消息Msg3。
在一些实施例中，第一条件，包括以下至少一个：
Msg3在非陆地网络NTN网络中传输，且在争用解决定时器超时前的最后一次启动，未在物理下行控制信道PDCCH上接收到基于临时小区无线网络临时标识TC-RNTI调度的Msg3重传；
Msg3在NTN网络中传输，且争用解决定时器是在Msg3发送后延迟往返时间RTT后启动的，且在争用解决定时器超时前的最后一次启动，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；
Msg3在NTN网络中传输，且争用解决定时器是在Msg3发送后延迟RTT后启动的，且在争用解 决定时器启动后，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；
Msg3在NTN网络中传输，争用解决定时器不将被启动，且在争用解决定时器超时前的最后一次启动，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；
Msg3在NTN网络中传输，争用解决定时器不将被启动，且在争用解决定时器启动后，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传。
在一些实施例中，第一条件，包括以下至少一个：
终端设备在NTN网络中，且争用解决定时器在Msg3初传结束后的第一个符号Symbol加上RTT时刻之前超时；
终端设备在NTN网络中，且争用解决定时器在调度的Msg3重传结束后的第一个Symbol加上RTT时刻之前超时；
终端设备在NTN网络中，且争用解决定时器在Msg3初传的所有重复传输结束后的第一个Symbol加上RTT时刻之前超时，其中，采用类型Type A物理上行共享信道PUSCH重复调度Msg3；
终端设备在NTN网络中，且争用解决定时器在调度的Msg3重传的所有重复传输结束后的第一个Symbol加上RTT时刻之前超时，其中，采用Type A PUSCH repetition调度Msg3；
终端设备在NTN网络中，且终端设备在PDCCH上收到Msg3的重传调度，且争用解决定时器在Msg3初传结束后的第一个Symbol加上RTT时刻之前超时；
终端设备在NTN网络中，且终端设备在PDCCH上收到Msg3的重传调度，且争用解决定时器在Msg3重传结束后的第一个Symbol加上RTT时刻之前超时。
在一些实施例中，通信装置1为终端设备：
该装置，包括：收发模块11和处理模块12。
收发模块11，被配置为发起随机接入，向网络侧设备发送随机接入的消息Msg3。
处理模块12，被配置为响应于所述Msg3在NTN网络中传输，在Msg3初传后启动监听定时器。
在一些实施例中，监听定时器为一个单独的定时器，该监听定时器与争用解决定时器为不同的定时器。
在一些实施例中，处理模块12，还被配置为在监听定时器运行期间，监听PDCCH。
在一些实施例中，终端设备处于非连续接收DRX激活active状态。
在一些实施例中，处理模块12，还被配置为在PDCCH上监听基于TC-RNTI的调度或仅监听基于TC-RNTI的Msg3的重传调度。
在一些实施例中，收发模块11，还被配置为基于网络侧设备发送的第一系统消息或第一无线资源控制RRC消息，确定监听定时器的定时时长。
在一些实施例中，监听定时器为争用解决定时器，其中，处理模块12，还被配置为在监听定时器运行期间，在PDCCH上监听基于TC-RNTI的调度或仅监听基于TC-RNTI的Msg3的重传调度。
在一些实施例中，处理模块12，还被配置为响应于接收到网络侧设备发送的配置信息，在Msg3初传后启动监听定时器，其中，配置信息用于指示终端设备进行Msg3初传的盲重传调度。
在一些实施例中，收发模块11，还被配置为接收到网络侧设备发送的第二系统消息或第二无线资源控制RRC消息。
在一些实施例中，处理模块12，还被配置为响应于终端设备支持Msg3初传的盲重传调度，在Msg3 初传后启动监听计时器，其中，终端设备处于空闲态或连接态或非激活态。
在一些实施例中，收发模块11，还被配置为向网络侧设备上报能力信息，其中，能力信息用于指示终端设备支持接收Msg3初传的盲重传调度。
在一些实施例中，处理模块12，还被配置为在Msg3初传后启动监听定时器，包括以下至少一个：
在Msg3初传后的所有重复传输结束后的第一个Symbol启动监听定时器，其中，采用Type A PUSCH repetition调度Msg3；
在Msg3初传后第一个Symbol启动监听定时器，其中，未采用Type A PUSCH repetition调度Msg3。
在一些实施例中，处理模块12，还被配置为响应于争用解决定时器超时，且满足第二条件，确定争用解决未成功或不认为争用解决未成功。
在一些实施例中，第二条件，包括以下至少一个：
在争用解决定时器超时前的最后一次启动，未在物理下行控制信道PDCCH上接收到基于临时小区无线网络临时标识TC-RNTI调度的Msg3重传；
争用解决定时器是在Msg3发送后延迟往返时间RTT后启动的，且在争用解决定时器超时前的最后一次启动，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；
争用解决定时器是在Msg3发送后延迟RTT后启动的，且在争用解决定时器启动后，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；
争用解决定时器不将被启动，且在争用解决定时器超时前的最后一次启动，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；
争用解决定时器不将被启动，且在争用解决定时器启动后，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传。
在一些实施例中，第二条件，包括以下至少一个：
争用解决定时器在Msg3初传结束后的第一个符号Symbol加上RTT时刻之前超时；
争用解决定时器在调度的Msg3重传结束后的第一个Symbol加上RTT时刻之前超时；
争用解决定时器在Msg3初传的所有重复传输结束后的第一个Symbol加上RTT时刻之前超时，其中，采用类型Type A物理上行共享信道PUSCH重复调度Msg3；
争用解决定时器在调度的Msg3重传的所有重复传输结束后的第一个Symbol加上RTT时刻之前超时，其中，采用Type A PUSCH repetition调度Msg3；
终端设备在PDCCH上收到Msg3的重传调度，且争用解决定时器在Msg3初传结束后的第一个Symbol加上RTT时刻之前超时；
终端设备在PDCCH上收到Msg3的重传调度，且争用解决定时器在Msg3重传结束后的第一个Symbol加上RTT时刻之前超时。
关于上述实施例中的通信装置1，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
本公开上述实施例中提供的通信装置1，与上面一些实施例中提供的随机接入方法取得相同或相似的有益效果，此处不再赘述。
请参见图10，图10是本公开实施例提供的另一种通信装置1000的结构示意图。通信装置1000可以是终端设备，也可以是支持终端设备实现上述方法的芯片、芯片系统、或处理器等。该通信装置1000 可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置1000可以包括一个或多个处理器1001。处理器1001可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，网络侧设备、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行计算机程序，处理计算机程序的数据。
可选的，通信装置1000中还可以包括一个或多个存储器1002，其上可以存有计算机程序1004，存储器1002执行所述计算机程序1004，以使得通信装置1000执行上述方法实施例中描述的方法。可选的，所述存储器1002中还可以存储有数据。通信装置1000和存储器1002可以单独设置，也可以集成在一起。
可选的，通信装置1000还可以包括收发器1005、天线1006。收发器1005可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1005可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。
可选的，通信装置1000中还可以包括一个或多个接口电路1007。接口电路1007用于接收代码指令并传输至处理器1001。处理器1001运行所述代码指令以使通信装置1000执行上述方法实施例中描述的方法。
通信装置1000为终端设备：处理器1001用于执行图5中的S51；图6中的S62；图7中的S71；图8中的S82和S83；收发器1005用于执行图6中的S61；图7中的S71；图8中的S81。
在一种实现方式中，处理器1001中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，处理器1001可以存有计算机程序1003，计算机程序1003在处理器1001上运行，可使得通信装置1000执行上述方法实施例中描述的方法。计算机程序1003可能固化在处理器1001中，该种情况下，处理器1001可能由硬件实现。
在一种实现方式中，通信装置1000可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。本公开中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的通信装置可以是终端设备，但本公开中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图10的限制。通信装置可以是独立的设备或者可以是较大设备的一部分。例如所述通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存 储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片系统的情况，请参见图11，为本公开实施例中提供的一种芯片的结构图。
芯片1100包括处理器1101和接口1103。其中，处理器1101的数量可以是一个或多个，接口1103的数量可以是多个。
对于芯片用于实现本公开实施例中终端设备的功能的情况：
接口1103，用于接收代码指令并传输至所述处理器。
处理器1101，用于运行代码指令以执行如上面一些实施例所述的随机接入方法。
可选的，芯片1100还包括存储器1102，存储器1102用于存储必要的计算机程序和数据。
本领域技术人员还可以了解到本公开实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本公开实施例保护的范围。
本公开实施例还提供一种随机接入系统，该系统包括前述图9实施例中作为终端设备的通信装置和作为网络侧设备的通信装置，或者，该系统包括前述图10实施例中作为终端设备的通信装置和作为网络侧设备的通信装置。
本公开还提供一种可读存储介质，其上存储有指令，该指令被计算机执行时实现上述任一方法实施例的功能。
本公开还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行所述计算机程序时，全部或部分地产生按照本公开实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解：本公开中涉及的第一、第二等各种数字编号仅为描述方便进行的区 分，并不用来限制本公开实施例的范围，也表示先后顺序。
本公开中的至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本公开不做限制。在本公开实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
本公开中各表所示的对应关系可以被配置，也可以是预定义的。各表中的信息的取值仅仅是举例，可以配置为其他值，本公开并不限定。在配置信息与各参数的对应关系时，并不一定要求必须配置各表中示意出的所有对应关系。例如，本公开中的表格中，某些行示出的对应关系也可以不配置。又例如，可以基于上述表格做适当的变形调整，例如，拆分，合并等等。上述各表中标题示出参数的名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以通信装置可理解的其他取值或表示方式。上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。
本公开中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以所述权利要求的保护范围为准。

Claims (24)

  1. 一种随机接入方法，其特征在于，所述方法由终端设备执行，包括：
    响应于基于竞争的随机接入中，争用解决定时器超时，且满足第一条件，确定争用解决未成功或不认为争用解决未成功。
  2. 如权利要求1所述的方法，其特征在于，还包括：
    向网络侧设备发送基于竞争的随机接入请求，其中，所述随机接入请求包括消息Msg3。
  3. 如权利要求2所述的方法，其特征在于，所述第一条件，包括以下至少一个：
    所述Msg3在非陆地网络NTN网络中传输，且在所述争用解决定时器超时前的最后一次启动，未在物理下行控制信道PDCCH上接收到基于临时小区无线网络临时标识TC-RNTI调度的Msg3重传；
    所述Msg3在NTN网络中传输，且所述争用解决定时器是在所述Msg3发送后延迟往返时间RTT后启动的，且在所述争用解决定时器超时前的最后一次启动，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；
    所述Msg3在NTN网络中传输，且所述争用解决定时器是在所述Msg3发送后延迟RTT后启动的，且在所述争用解决定时器启动后，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；
    所述Msg3在NTN网络中传输，所述争用解决定时器不将被启动，且在所述争用解决定时器超时前的最后一次启动，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；
    所述Msg3在NTN网络中传输，所述争用解决定时器不将被启动，且在所述争用解决定时器启动后，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传。
  4. 如权利要求2所述的方法，其特征在于，所述第一条件，包括以下至少一个：
    所述终端设备在NTN网络中，且所述争用解决定时器在Msg3初传结束后的第一个符号Symbol加上RTT时刻之前超时；
    所述终端设备在NTN网络中，且所述争用解决定时器在调度的Msg3重传结束后的第一个Symbol加上RTT时刻之前超时；
    所述终端设备在NTN网络中，且所述争用解决定时器在Msg3初传的所有重复传输结束后的第一个Symbol加上RTT时刻之前超时，其中，采用类型Type A物理上行共享信道PUSCH重复调度所述Msg3；
    所述终端设备在NTN网络中，且所述争用解决定时器在调度的Msg3重传的所有重复传输结束后的第一个Symbol加上RTT时刻之前超时，其中，采用Type A PUSCH repetition调度所述Msg3；
    所述终端设备在NTN网络中，且所述终端设备在PDCCH上收到Msg3的重传调度，且所述争用解决定时器在Msg3初传结束后的第一个Symbol加上RTT时刻之前超时；
    所述终端设备在NTN网络中，且所述终端设备在PDCCH上收到Msg3的重传调度，且所述争用解决定时器在Msg3重传结束后的第一个Symbol加上RTT时刻之前超时。
  5. 一种随机接入方法，其特征在于，所述方法由终端设备执行，包括：
    发起随机接入，向网络侧设备发送随机接入的消息Msg3；
    响应于所述Msg3在NTN网络中传输，在Msg3初传后启动监听定时器。
  6. 如权利要求5所述的方法，其特征在于，所述监听定时器为一个单独的定时器，该监听定时器 与争用解决定时器为不同的定时器。
  7. 如权利要求5或6所述的方法，其特征在于，还包括：
    在所述监听定时器运行期间，监听PDCCH。
  8. 如权利要求7所述的方法，其特征在于，所述终端设备处于非连续接收DRX激活active状态。
  9. 如权利要求7或8所述的方法，其特征在于，所述监听PDCCH，包括：
    在所述PDCCH上监听基于TC-RNTI的调度或仅监听基于TC-RNTI的所述Msg3的重传调度。
  10. 如权利要求5至9中任一项所述的方法，其特征在于，还包括：
    基于所述网络侧设备发送的第一系统消息或第一无线资源控制RRC消息，确定所述监听定时器的定时时长。
  11. 如权利要求9所述的方法，其特征在于，所述监听定时器为争用解决定时器，其中，还包括：
    在所述监听定时器运行期间，在所述PDCCH上监听基于TC-RNTI的调度或仅监听基于TC-RNTI的所述Msg3的重传调度。
  12. 如权利要求9至11中任一项所述的方法，其特征在于，所述在Msg3初传后启动监听定时器，包括：
    响应于接收到所述网络侧设备发送的配置信息，在Msg3初传后启动所述监听定时器，其中，所述配置信息用于指示所述终端设备进行Msg3初传的盲重传调度。
  13. 如权利要求12所述的方法，其特征在于，所述接收到所述网络侧设备发送的配置信息，包括：
    接收到所述网络侧设备发送的第二系统消息或第二无线资源控制RRC消息。
  14. 如权利要求12或13所述的方法，其特征在于，还包括：
    响应于所述终端设备支持Msg3初传的盲重传调度，在Msg3初传后启动所述监听计时器，其中，所述终端设备处于空闲态或连接态或非激活态。
  15. 如权利要求12至14中任一项所述的方法，其特征在于，还包括：
    向所述网络侧设备上报能力信息，其中，所述能力信息用于指示所述终端设备支持接收Msg3初传的盲重传调度。
  16. 如权利要求5至15中任一项所述的方法，其特征在于，所述在Msg3初传后启动监听定时器，包括以下至少一个：
    在Msg3初传后的所有重复传输结束后的第一个Symbol启动所述监听定时器，其中，采用Type A PUSCH repetition调度所述Msg3；
    在所述Msg3初传后第一个Symbol启动所述监听定时器，其中，未采用Type A PUSCH repetition调度所述Msg3。
  17. 如权利要求5至16中任一项所述的方法，其特征在于，还包括：
    响应于争用解决定时器超时，且满足第二条件，确定争用解决未成功或不认为争用解决未成功。
  18. 如权利要求17所述的方法，其特征在于，所述第二条件，包括以下至少一个：
    在所述争用解决定时器超时前的最后一次启动，未在物理下行控制信道PDCCH上接收到基于临时小区无线网络临时标识TC-RNTI调度的Msg3重传；
    所述争用解决定时器是在所述Msg3发送后延迟往返时间RTT后启动的，且在所述争用解决定时器超时前的最后一次启动，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；
    所述争用解决定时器是在所述Msg3发送后延迟RTT后启动的，且在所述争用解决定时器启动后，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；
    所述争用解决定时器不将被启动，且在所述争用解决定时器超时前的最后一次启动，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传；
    所述争用解决定时器不将被启动，且在所述争用解决定时器启动后，未在PDCCH上接收到基于TC-RNTI调度的Msg3重传。
  19. 如权利要求17所述的方法，其特征在于，所述第二条件，包括以下至少一个：
    所述争用解决定时器在Msg3初传结束后的第一个符号Symbol加上RTT时刻之前超时；
    所述争用解决定时器在调度的Msg3重传结束后的第一个Symbol加上RTT时刻之前超时；
    所述争用解决定时器在Msg3初传的所有重复传输结束后的第一个Symbol加上RTT时刻之前超时，其中，采用类型Type A物理上行共享信道PUSCH重复调度所述Msg3；
    所述争用解决定时器在调度的Msg3重传的所有重复传输结束后的第一个Symbol加上RTT时刻之前超时，其中，采用Type A PUSCH repetition调度所述Msg3；
    所述终端设备在PDCCH上收到Msg3的重传调度，且所述争用解决定时器在Msg3初传结束后的第一个Symbol加上RTT时刻之前超时；
    所述终端设备在PDCCH上收到Msg3的重传调度，且所述争用解决定时器在Msg3重传结束后的第一个Symbol加上RTT时刻之前超时。
  20. 一种通信装置，其特征在于，所述装置包括：
    处理模块，被配置为响应于基于竞争的随机接入中，争用解决定时器超时，且满足第一条件，确定争用解决未成功或不认为争用解决未成功。
  21. 一种通信装置，其特征在于，所述装置包括：
    收发模块，被配置为发起随机接入，向网络侧设备发送随机接入的消息Msg3；
    处理模块，被配置为响应于所述Msg3在NTN网络中传输，在Msg3初传后启动监听定时器。
  22. 一种通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求1至19中任一项所述的方法。
  23. 一种通信装置，其特征在于，包括：处理器和接口电路；
    所述接口电路，用于接收代码指令并传输至所述处理器；
    所述处理器，用于运行所述代码指令以执行如权利要求1至19中任一项所述的方法。
  24. 一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使如权利要求1至19中任一项所述的方法被实现。
PCT/CN2022/100244 2022-06-21 2022-06-21 随机接入方法和装置 WO2023245451A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280002093.4A CN115299167A (zh) 2022-06-21 2022-06-21 随机接入方法和装置
PCT/CN2022/100244 WO2023245451A1 (zh) 2022-06-21 2022-06-21 随机接入方法和装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/100244 WO2023245451A1 (zh) 2022-06-21 2022-06-21 随机接入方法和装置

Publications (1)

Publication Number Publication Date
WO2023245451A1 true WO2023245451A1 (zh) 2023-12-28

Family

ID=83819326

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/100244 WO2023245451A1 (zh) 2022-06-21 2022-06-21 随机接入方法和装置

Country Status (2)

Country Link
CN (1) CN115299167A (zh)
WO (1) WO2023245451A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107211462A (zh) * 2015-01-23 2017-09-26 联发科技股份有限公司 Lte rach过程增强
WO2022081074A1 (en) * 2020-10-16 2022-04-21 Telefonaktiebolaget Lm Ericsson (Publ) Enhancing random access channel report content with message3 information

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107211462A (zh) * 2015-01-23 2017-09-26 联发科技股份有限公司 Lte rach过程增强
WO2022081074A1 (en) * 2020-10-16 2022-04-21 Telefonaktiebolaget Lm Ericsson (Publ) Enhancing random access channel report content with message3 information

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ASUSTEK: "Consideration on random access for further MTC enhancement", 3GPP TSG RAN WG2 MEETING #91, R2-153486, 14 August 2015 (2015-08-14), XP050993016 *
HUAWEI, HISILICON: "Discussion on the timers for 2-step RACH", 3GPP TSG RAN WG2 MEETING 107, R2-1910678, 16 August 2019 (2019-08-16), XP051768449 *
NOKIA, NOKIA SHANGHAI BELL: "Correction on mac-ContentionResolutionTimer for FeMTC and eNB-IoT", 3GPP TSG RAN WG2 #100, R2-1713979, 2 December 2017 (2017-12-02), XP051372638 *
OPPO: "Stage 3 issues on contention resolution for 2-step RACH", 3GPP TSG RAN WG2 MEETING #107BIS, R2-1912087, 3 October 2019 (2019-10-03), XP051790140 *

Also Published As

Publication number Publication date
CN115299167A (zh) 2022-11-04

Similar Documents

Publication Publication Date Title
WO2018157298A1 (zh) 随机接入的方法、终端设备和网络设备
WO2023279302A1 (zh) 用于非地面网络的sdt处理方法、通信装置和存储介质
CN114071750A (zh) 频域资源的确定方法、设备及存储介质
CN116508367A (zh) 用于小数据传输或接收的方法及装置
US11778681B2 (en) Data transmission method and apparatus
WO2023245451A1 (zh) 随机接入方法和装置
WO2023019410A1 (zh) 一种传输下行控制信息dci的方法及其装置
WO2022120519A1 (zh) 部分带宽处理方法及装置
CN113573401B (zh) 通信方法、装置及系统
US20200170048A1 (en) Data transmission method, base station, and user equipment
WO2023230971A1 (zh) 一种多prach传输方法及其装置
WO2020252633A1 (zh) 随机接入前导码退避的方法、装置和系统
WO2023225876A1 (zh) 波束确定方法和装置
CN115004809A (zh) 一种确定侧链路时长的方法及其装置
WO2023206033A1 (zh) 混合自动重传请求harq反馈的处理方法及其装置
CN114287166B (zh) 一种基于四步随机接入的第三条消息重复的覆盖增强方法
WO2024000208A1 (zh) 一种定时提前报告tar的触发方法、装置、设备及存储介质
WO2023201529A1 (zh) 资源配置方法及装置
WO2024020902A1 (zh) 一种随机接入控制方法及装置
WO2024060143A1 (zh) 一种上报方法/装置/设备及存储介质
WO2024031373A1 (zh) 一种确定触发连续lbt失败的方法及装置
WO2023245453A1 (zh) 一种消息传输方法/装置/设备及存储介质
WO2023122988A1 (zh) 一种定时器同步方法及其装置
WO2024020753A1 (zh) 数据传输方法和装置
WO2024065095A1 (zh) 指示方法、装置、设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22947231

Country of ref document: EP

Kind code of ref document: A1