Method and apparatus for processing contention resolution in a wireless communication system

By introducing a timing offset mechanism in the wireless communication system, delaying the start of the contention resolution timer, the problem of power consumption and delay in the random access contention resolution process in NTN is solved, and the efficiency and flexibility of the system are improved.

CN115209561BActive Publication Date: 2024-12-03ASUSTEK COMPUTER INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202210319033.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2021-11-17
Filing Date
2022-03-29
Publication Date
2024-12-03
Estimated Expiration
2042-03-29

AI Technical Summary

Technical Problem

In wireless communication systems, during random access (RA) contention resolution in non-terrestrial networks (NTNs), traditional timer mechanisms lead to increased power consumption and contention resolution delays, especially over longer round trip times (RTTs) ) In the case of ) , the traditional timer length is not enough to cover the response time of the NTN platform, limiting network scheduling flexibility.

Method used

Introducing a timing offset mechanism, suitable for user equipment (UE) in NTN environments, delaying startup or restarting of contention resolution timer after Msg3 transmission and retransmission, ensuring that UE can effectively monitor PDCCH in NTN and reduce unnecessary Power consumption.

Benefits of technology

By delaying the startup timer, the power consumption of wireless devices in the NTN environment is reduced, and the success rate of contention resolution and network scheduling flexibility are improved, adapting to the longer RTT characteristics of the NTN platform.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115209561B_ABST
    Figure CN115209561B_ABST
Patent Text Reader

Abstract

A method and apparatus for a user equipment is provided to appropriately monitor a physical downlink control channel in order to perform contention resolution for a random access procedure in a non-terrestrial network. The user equipment may perform a Msg3 transmission during an RA procedure in an NTN and start a random access contention resolution timer in the first symbol after the end of the Msg3 transmission plus a timing offset. In response to the expiration of the RA contention resolution timer, the UE determines whether to consider contention resolution as unsuccessful based on at least whether the RA contention resolution timer expires during the duration of the timing offset after the retransmission of the Msg3.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates generally to wireless communication networks, and more particularly, to methods and apparatus for handling contention resolution in wireless communication systems. Background Art

[0002] With the rapid growth of the demand for transmitting large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks with Internet Protocol (IP) data packet communications, which can provide IP-bearing voice, multimedia, multicast and on-demand communication services to users of mobile communication devices.

[0003] An exemplary network structure is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The E-UTRAN system can provide high data throughput to enable the above-mentioned IP-borne voice and multimedia services. Currently, the 3GPP standards organization is discussing new next-generation (e.g., 5G) radio technologies. Therefore, changes to the current body of 3GPP standards are currently being submitted and considered to evolve and complete the 3GPP standards. Summary of the invention

[0004] A method and apparatus for a user equipment (UE) are provided to appropriately monitor a physical downlink control channel (PDCCH) in order to reduce power consumption and perform contention resolution of a random access (RA) procedure in a non-terrestrial network (NTN). The UE may perform a Msg3 transmission and start a RA contention resolution timer, receive an uplink (UL) grant for Msg3 retransmission on the PDCCH while the timer is running, and perform Msg3 retransmission using the UL grant. The UE may stop the timer in response to receiving the UL grant, and if the Msg3 transmission is in the NTN, then start the timer in the first symbol after the Msg3 retransmission ends plus a timing offset, and if the Msg3 transmission is in the terrestrial network (TN), then the UE may restart the timer in the first symbol after the Msg3 retransmission ends.

[0005] In various embodiments, the UE initiates an RA procedure, transmits Msg3 in the RA procedure, starts a first timer with a first value at a first timing, and receives an UL grant for Msg3 retransmission on a PDCCH while the first timer is running. The UE retransmits the Msg3 using the UL grant, and restarts the first timer with a second value at a second timing.

[0006] In various embodiments, the UE performs a Msg3 transmission and starts a RA contention resolution timer, receives a UL grant for Msg3 retransmission on a PDCCH while the RA contention resolution timer is running, and performs Msg3 retransmission using the UL grant. The UE further stops the RA contention resolution timer in response to receiving the UL grant, and starts the RA contention resolution timer in the first symbol after the end of the Msg3 retransmission plus a timing offset if the Msg3 transmission is in NTN, and restarts the RA contention resolution timer in the first symbol after the end of the Msg3 retransmission if the Msg3 transmission is in TN.

[0007] In various embodiments, the UE performs a Msg3 transmission during an RA procedure in the NTN and starts an RA contention resolution timer in a first symbol after the end of the Msg3 transmission plus a timing offset. In response to the RA contention resolution timer expiring, the UE determines whether to consider contention resolution as unsuccessful based at least on whether the RA contention resolution timer expires during a duration of the timing offset after the Msg3 retransmission.

[0008] In various embodiments, the UE performs a Msg3 transmission during a RA procedure in the NTN and starts a RA contention resolution timer in the first symbol after the end of the Msg3 transmission plus a timing offset, where if the RA contention resolution timer expires for the duration of the time offset after the Msg3 retransmission, contention resolution is not considered unsuccessful. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 A diagram showing a wireless communication system according to an embodiment of the present invention;

[0010] Figure 2 is a block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) according to an embodiment of the present invention;

[0011] Figure 3 is a functional block diagram of a communication system according to an embodiment of the present invention;

[0012] Figure 4 According to an embodiment of the present invention Figure 3 Functional block diagram of the program code;

[0013] Figure 5 An example of a problem when a Msg4 timer is restarted with a timing offset according to an embodiment of the present invention is shown, wherein the Msg4 timer may be a contention resolution timer in an RA procedure, and wherein the RTT offset refers to the timing offset;

[0014] Figure 6 An example of a problem when a Msg4 timer is restarted without a timing offset according to an embodiment of the present invention is shown, wherein the Msg4 timer may be a contention resolution timer in an RA procedure, and wherein the RTT offset refers to the timing offset;

[0015] Figure 7 An example of a first solution according to an embodiment of the present invention is shown, wherein the Msg4 timer may be a contention resolution timer in a RA procedure, and wherein the RTT offset refers to the timing offset;

[0016] Figure 8 An example of a second solution according to an embodiment of the present invention is shown, wherein the Msg4 timer may be a contention resolution timer in the RA procedure, and wherein the RTT offset refers to the timing offset;

[0017] Fig. 9 An example of PDCCH monitoring for Msg3 transmission according to an embodiment of the present invention is shown, wherein the Msg4 timer (eg, the first timer) may be a contention resolution timer in the RA procedure;

[0018] Fig.10 An example of a third solution according to an embodiment of the present invention is shown, wherein the Msg4 timer may be a contention resolution timer in a RA procedure, and wherein the RTT offset refers to a timing offset;

[0019] Fig.11 An example of a fourth solution according to an embodiment of the present invention is shown, wherein the Msg4 timer may be a contention resolution timer in the RA procedure, wherein the RTT timer refers to the timing offset;

[0020] Fig.12 is a flow chart according to an embodiment of the present invention, illustrating a method for processing contention resolution in a wireless communication system, comprising starting a first timer with a first value at a first time, and restarting the first timer with a second value at a second time;

[0021] Fig.13 is a flow chart according to an embodiment of the present invention, illustrating a method for processing contention resolution in a wireless communication system, comprising starting a first timer at a first timing, and restarting the first timer at a second timing and a third timing;

[0022] Fig.14 is a flow chart according to an embodiment of the present invention, illustrating a method for processing contention resolution in a wireless communication system, comprising starting a first timer at a first timing, stopping the first timer at a fourth timing, and starting the first timer at a third timing;

[0023] Fig.15 is a flow chart according to an embodiment of the present invention, illustrating a method for processing contention resolution in a wireless communication system, comprising starting a first timer with a first value at a first time, and starting the first timer at a fourth timing;

[0024] Fig.16 is a flow chart according to an embodiment of the present invention, illustrating a method for processing contention resolution in a wireless communication system, comprising stopping an RA contention resolution timer, and starting the RA timer in the first symbol after the end of Msg3 transmission plus a timing offset when Msg3 is in NTN, and restarting the RA contention resolution timer in the first symbol after the end of Msg3 retransmission when Msg3 is transmitted in TN;

[0025] Fig.17 is a flow chart according to an embodiment of the present invention, illustrating a method for processing contention resolution in a wireless communication system, comprising performing Msg3 transmission during an RA procedure in an NTN, starting an RA contention resolution timer in a first symbol after the end of Msg3 transmission plus a timing offset, and determining whether to regard content resolution as unsuccessful based on at least whether a condition is satisfied;

[0026] Fig.18 The present invention is a flow chart showing a method for processing contention resolution in a wireless communication system according to an embodiment of the present invention, which includes performing Msg3 transmission during an RA process in an NTN, starting an RA contention resolution timer in the first symbol after the end of Msg3 transmission plus a timing offset, and if the RA contention resolution timer expires within the duration of the time offset after Msg3 retransmission, the contention resolution is not considered unsuccessful. DETAILED DESCRIPTION

[0027] The present invention described herein may be applied to or implemented in the exemplary wireless communication systems and devices described below. In addition, the present invention is primarily described in the context of the 3GPP architecture reference model. However, it should be understood that with the disclosed information, those skilled in the art can easily make adjustments to use and implement aspects of the present invention in the 3GPP2 network architecture as well as other network architectures.

[0028] The exemplary wireless communication systems and devices described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communications, such as voice, data, etc. These systems can be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP Long Term Evolution (LTE) wireless access, 3GPP Long Term Evolution Advanced (LTE-A) wireless access, 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR), or some other modulation technology.

[0029] Specifically, the exemplary wireless communication system apparatus described below may be designed to support one or more standards, such as those provided by an association named “3rd Generation Partnership Project” (referred to herein as 3GPP), including: [1] RP-201256, “Solution for NR Supporting Non-Terrestrial Networks (NTN)”; [2] 3GPP TS 38.321 V16.3.0, “NR, MAC Protocol Specification”; and [3] 3GPP TR 38.821 V16.0.0, “Solution for NR Supporting Non-Terrestrial Networks (NTN)”; [4] 3GPP TS 38.331 V16.3.1, “NR, RRC Protocol Specification”. The standards and documents listed above are expressly and completely incorporated herein by reference in their entirety.

[0030] Figure 1 A multiple access wireless communication system according to an embodiment of the present invention is shown. An access network 100 (AN) includes multiple antenna groups, one antenna group includes 104 and 106, another antenna group includes 108 and 110, and another antenna group includes 112 and 114. Figure 1, only two antennas are shown for each antenna group, but each antenna group may utilize more or fewer antennas. Access terminal (AT) 116 communicates with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 via forward link 120 and receive information from AT 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, where antennas 106 and 108 transmit information to AT 122 via forward link 126 and receive information from AT 122 via reverse link 124. In an FDD system, communication links 118, 120, 124, and 126 may use different frequencies for communication. For example, forward link 120 may use a different frequency than the frequency used by reverse link 118.

[0031] Each antenna group and / or the area in which they are designed to communicate is often referred to as a sector of the access network. In an embodiment, the antenna groups are each designed to communicate with access terminals in a sector of the area covered by the access network 100.

[0032] In communicating via forward links 120 and 126, the transmit antennas of access network 100 may utilize beamforming in order to improve the signal-to-noise ratio of the forward links for the different access terminals 116 and 122. Also, an access network that uses beamforming to transmit to access terminals that are randomly dispersed throughout the coverage area of ​​the access network will generally cause less interference to access terminals in neighboring cells than an access network that transmits to all of its access terminals via a single antenna.

[0033] AN can be a fixed station or base station for communicating with a terminal, and can also be referred to as an access point, Node B, base station, enhanced base station, eNodeB, or some other term. AT can also be referred to as user equipment (UE), a wireless communication device, a terminal, an access terminal, or some other term.

[0034] Figure 2 2 is a simplified block diagram of an embodiment of a transmitter system 210 (also referred to as an access network) and a receiver system 250 (also referred to as an access terminal (AT) or user equipment (UE)) in a MIMO system 200. At the transmitter system 210, traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214.

[0035] In one embodiment, each data stream is transmitted via a respective transmit antenna.TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

[0036] The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream is then modulated (e.g., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for that data stream to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions executed by processor 230.

[0037] The modulation symbols for all data streams are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then converts the N T The modulation symbol stream is provided to N T transmitters (TMTR) 222a through 222t. In certain embodiments, TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

[0038] Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (eg, amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission via the MIMO channel. T The antennas 224a to 224t transmit the N signals from the transmitters 222a to 222t. T a modulated signal.

[0039] At the receiver system 250, N R The transmitted modulated signals are received by each antenna 252a through 252r and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254a through 254r. Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding "received" symbol stream.

[0040] RX data processor 260 then extracts the N R The receiver 254 receives and processes N R receive symbol streams to provide N TThe RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing by the RX processor 260 is complementary to that performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

[0041] Processor 270 periodically determines which pre-coding matrix to use (discussed below). Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.

[0042] The reverse link message may include various types of information related to the communication link and / or the received data stream. The reverse link message is then processed by the TX data processor 238 (which also receives traffic data for a number of data streams from the data source 236), modulated by the modulator 280, conditioned by the transmitters 254a to 254r, and transmitted back to the transmitter system 210.

[0043] At the transmitter system 210, the modulated signal from the receiver system 250 is received by the antenna 224, conditioned by the receiver 222, demodulated by the demodulator 240, and processed by the RX data processor 242 to extract the reverse link message transmitted by the receiver system 250. The processor 230 then determines which precoding matrix to use to determine the beamforming weights and then processes the extracted message.

[0044] The memory 232 may be used to temporarily store some buffer / calculated data from 240 or 242 through the processor 230, store some buffer data from 212, or store some specific program codes. Also, the memory 272 may be used to temporarily store some buffer / calculated data from 260 through the processor 270, store some buffer data from 236, or store some specific program codes.

[0045] Steering Figure 3 , this figure shows an alternative simplified functional block diagram of a communication device according to one embodiment of the present invention. Figure 3 As shown in FIG. , the communication device 300 in the wireless communication system can be used to implement Figure 1UE (or AT) 116 and 122 in, and the wireless communication system is preferably an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, a program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 through the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive a signal input by a user through the input device 302 (for example, a keyboard or a keypad), and can output images and sounds through the output device 304 (for example, a display or a speaker). The transceiver 314 is used to receive and transmit wireless signals to pass the received signal to the control circuit 306 and wirelessly output the signal generated by the control circuit 306.

[0046] Figure 4 According to one embodiment of the present invention, Figure 3 4. In this embodiment, program code 312 includes application layer 400, layer 3 portion 402, and layer 2 portion 404, and is coupled to layer 1 portion 406. Layer 3 portion 402 generally performs radio resource control. Layer 2 portion 404 generally performs link control. Layer 1 portion 406 generally performs physical connectivity.

[0047] For LTE, LTE-A or NR systems, the layer 2 portion 404 may include a radio link control (RLC) layer and a medium access control (MAC) layer. The layer 3 portion 402 may include a radio resource control (RRC) layer.

[0048] Any two or more of the following paragraphs, (sub)bullets, points, actions or claims described in each invention may be logically, reasonably and appropriately combined to form a specific method.

[0049] Any sentence, paragraph, (sub) bullet point, key point, action or claim described in each of the following inventions can be implemented independently and individually to form a specific method. The dependency in the following inventions (e.g., "based on", "more specifically", etc.) is only a possible embodiment that does not limit a specific method.

[0050] The work item for Non-Terrestrial Networks (NTN) in NR has been agreed at the RAN#88 plenary meeting. The description of this work item is specified in [1] RP-201256 "Solutions for NR to support Non-Terrestrial Networks (NTN):

[0051] *************************Quote starts [1]************************************

[0052] 3 valid reasons

[0053] Non-terrestrial networks refer to networks or network segments that use air or space vehicles for transmission:

[0054] ● Space launch vehicles: Satellites (including low earth orbit (LEO) satellites, medium earth orbit (MEO) satellites, geostationary orbit (GEO) satellites and highly elliptical orbit (HEO) satellites)

[0055] ●Aerial vehicles: High altitude platforms (HAPs), including unmanned aerial systems (UAS), including lighter-than-air UAS (LTA), heavier-than-air UAS (HTA), all operating at altitudes typically between 8km and 50km, quasi-stationary.

[0056] In 3GPP TS 22.261 adopted by SA#82, use cases and corresponding service requirements for 5G satellite integration have been identified as a result of work item "5GSAT". This will meet mobile broadband needs in unserved / underserved areas, as well as public safety needs, maritime (3GPP TS 22.119 "Maritime communication services over 3GPP systems"), aircraft connectivity and railway communication service requirements applicable to satellite access.

[0057] Since RAN#76, two activities have been carried out on NR to support non-terrestrial networks.

[0058] ●The first activity, FS_NR_nonterr_nw (see RP-171450), studies channel models for non-terrestrial networks to define deployment scenarios, parameters and identify key potential impacts on NR. The RAN-led work started in RAN#76 and was completed in RAN#80. The results are reflected in TR 38.811.

[0059] ● The second activity, FS_NR_NTN_solutions (see RP-190710), defines and evaluates solutions to the key impacts identified in the first activity. The work led by RAN3 started in RAN#80 and is scheduled to be completed in RAN#86. The results are reflected in TR38.821 (RP-193062).

[0060] Additionally, an email discussion took place between RAN #85 and #86 on the scope of Rel-17 WI on non-terrestrial networks. A report of this email discussion is available in RP-192500. It was concluded that Rel-17 NR-NTN NWI should include two activities:

[0061] NR-NTN develops specifications to support normative activities in the following scenarios:

[0062] o The transparent payload based LEO scenarios address at least 3GPP Category 3 UEs with and without GNSS capabilities as well as geostationary and / or mobile cell scenarios (as per SI results).

[0063] ■ NOTE 1: Addressing LEO will provide flexibility to also support HAPS based scenarios based on transparent payloads.

[0064] ○ GEO context based on transparent payload addresses UEs with GNSS capabilities.

[0065] ■ NOTE 2: Addressing LEO and GEO scenarios will enable NR to support all NGSO scenarios with circular orbits at altitudes greater than or equal to 600 km.

[0066] ●Research activities on NTN context addressing

[0067] ○ HAPS scenario based on transparent payload: study of implementation methods for spectrum coexistence with cellular (additional coresets, PCI confusion mitigation, ...)

[0068] ○ Scenarios based on IoT-NTN

[0069] ○ UE’s location based on NTN network (for regulatory services): Identify possible solutions

[0070] Based on the above points, a new work item is proposed to carry the conclusions of the FS_NR_NTN_solutions study item and specify solutions to enable NR to support non-terrestrial networks.

[0071] Addressing LEO and GEO scenarios will be able to support all NGSO scenarios with circular orbits at altitudes greater than or equal to 600 km.

[0072] 4. Goals

[0073] 4.1 Objectives of SI or core WI or test WI

[0074] The work item aims to specify enhancements for NR NTN (Non-Terrestrial Network) identification, in particular LEO and GEO, with implicit compatibility to support High Altitude Communications Platforms (HAPS) and Air-to-Ground (ATG) scenarios based on the following principles:

[0075] ●Adopt FDD for core specification work of NR-NTN.

[0076] ○ Note: This does not mean that TDD cannot be used in related contexts, such as HAPS, ATG

[0077] ● Use geo-fixed tracking areas and geo-fixed and mobile cells

[0078] ●Use UE with GNSS capability.

[0079] ●Use transparent payload

[0080] The detailed objectives are to specify enhancements to the NR radio interface and NG-RAN for Rel-15 and Rel-16 as follows:

[0081] 4.1.1 RAN1

[0082] Enhanced features to address the problems identified due to long propagation delays, large Doppler effects and mobile cells in NTNs should specify the following (see TR 38.821):

[0083] ●Timing relationship enhancement [RAN1, RAN2]

[0084] ● Enhancement of UL time and frequency synchronization [RAN1, RAN2]

[0085] HARQ

[0086] ○Number of HARQ processes [RAN1]

[0087] ○ Activation / deactivation of HARQ feedback as described in TR 38.821 [RAN1&2]

[0088] In addition, if helpful and necessary, the following topics should be specified:

[0089] ● Enhancement of PRACH sequence and / or format, and extension of RA-ResponseWindow duration (if UE has GNSS capability but without pre-compensation for timing and frequency offset capability) [RAN1 / 2].

[0090] ●Feeder link switch [RAN2, RAN1]

[0091] ● Beam management and bandwidth part (BWP) operation of NTN with frequency reuse [RAN1 / 2]

[0092] ○ Includes polarization mode signaling

[0093] 4.1.2 RAN2

[0094] Note: An offset-based timer adaptive solution is used.

[0095] The following user plane procedure enhancements shall be specified (see TR 38.821)

[0096] MAC

[0097] ○ Random access:

[0098] ■ Defines the offset where the ra-ResponseWindow of NTN starts.

[0099] ■ Introduce an offset to the start of ra-ContentionResolutionTimer to resolve random access contention

[0100] ■Solutions to resolve preamble ambiguity and RAR window extension.

[0101] ■Msg-3 scheduling adaptation

[0102] ● Only applicable when pre-compensation of timing and frequency offset is performed on the UE side

[0103] ○ Enhancements to UL scheduling to reduce scheduling latency.

[0104] ○DRX:

[0105] ■ If HARQ feedback is enabled, an offset for drx-HARQ-RTT-TimerDL and drx-HARQ-RTT-TimerUL is introduced.

[0106] ■ If HARQ is switched off per HARQ process, then there is adaptation in the HARQ process

[0107] ○ Scheduling Request: Extension of the value range of sr-ProhibitTimer

[0108] ●RLC

[0109] ○ Status reporting: Extension of the value range of t-Reassembly

[0110] ○ Sequence number: Extension of SN space for GEO context only

[0111] PDCP

[0112] ○SDU discard: Extension of the value range of discardTimer.

[0113] ○ Sequence Number: An extension of the SN space for GEO context.

[0114] The following control plane procedural enhancements should be specified (see TR 38.821)

[0115] ●Idle mode:

[0116] ○ Define additional assistance information for cell selection / reselection (e.g. using UE location information, satellite almanac information)

[0117] ○Define NTN (satellite / HAPS) cell-specific information in SIB

[0118] Connection mode

[0119] o Enhancements needed to consider location information (UE and satellite / HAPS) and / or almanac when determining when to perform a handover, to allow for a high degree of handover control for handover robustness and coverage management.

[0120] o Enhancements to existing measurement configurations to account for absolute propagation delay differences between satellites (e.g., SMTC measurement gap adaptation for SSB / CSI-RS measurement windows) [RAN2 / 4].

[0121] ● Service continuity for mobility from TN to NTN and from NTN to TN systems (to be addressed when connected mode mobility is fully developed)

[0122] ● Identify potential issues associated with positioning UEs in the context of NTNs using existing Location Services (LCS) application protocols and specify any adaptations, if any [RAN2 / 3]

[0123] ******************************End of Quote*******************************

[0124] The procedures for random access (RA) contention resolution and completion are specified in TS 38.321 [2] (3GPP TS 38.321 V16.3.0, “NR, MAC Protocol Specification”) as follows:

[0125] ***************************** Quote starts [2]********************************

[0126] 5.1.5 Contention Resolution

[0127] Once Msg3 is transmitted, the MAC entity shall:

[0128] 1> For each HARQ retransmission in the first symbol after the end of Msg3 transmission, start ra-ContentionResolutionTimer and restart ra-ContentionResolutionTimer;

[0129] 1> Regardless of whether measurement gaps may occur, PDCCH is monitored when ra-ContentionResolutionTimer is running;

[0130] 1> If a notification of receiving a PDCCH transmission from SpCell is received from the lower layer:

[0131] 2> If C-RNTI MAC CE is included in Msg3, then:

[0132] 3> If a random access procedure is initiated for SpCell beam failure recovery (as specified in Section 5.17) and the PDCCH transmission is addressed to the C-RNTI; or

[0133] 3> If the random access procedure is initiated by a PDCCH command and the PDCCH transmission is addressed to the C-RNTI; or

[0134] 3> If the random access procedure is initiated by the MAC sublayer itself or by the RRC sublayer and the PDCCH transmission is addressed to the C-RNTI and contains an UL grant for a new transmission:

[0135] 4> Consider this contention resolution as a success;

[0136] 4>Stop ra-ContentionResolutionTimer;

[0137] 4>Discard TEMPORARY_C-RNTI;

[0138] 4> Consider this random access procedure to have been completed successfully.

[0139] 2> Otherwise, if the CCCH SDU is contained in Msg3 and the PDCCH transmission is addressed to its TEMPORARY_C-RNTI:

[0140] 3> If the MAC PDU is decoded successfully:

[0141] 4>Stop ra-ContentionResolutionTimer;

[0142] 4> If the MAC PDU contains the UE contention resolution identifier MAC CE; and

[0143] 4> If the UE contention resolution identifier in the MAC CE matches the CCCH SDU transmitted in Msg3:

[0144] 5> Consider this contention resolution as successful and end the decomposition and demultiplexing of MAC PDU;

[0145] 5> If this random access procedure is initiated for SI request:

[0146] 6>Indicate to the upper layer that confirmation of SI request has been received.

[0147] 5> Otherwise:

[0148] 6> Set C-RNTI to the value of TEMPORARY_C-RNTI;

[0149] 5>Discard TEMPORARY_C-RNTI;

[0150] 5> Consider this random access procedure to have been completed successfully.

[0151] 4> Otherwise:

[0152] 5>Discard TEMPORARY_C-RNTI;

[0153] 5> Consider this contention resolution as unsuccessful and discard the successfully decoded MAC PDU.

[0154] 1> If ra-ContentionResolutionTimer expires:

[0155] 2>Discard TEMPORARY_C-RNTI;

[0156] 2>Consider contention resolution as unsuccessful.

[0157] 1> If contention resolution is deemed unsuccessful:

[0158] 2> Clear the HARQ buffer in the Msg3 buffer used to transmit MAC PDU;

[0159] 2>Increase PREAMBLE_TRANSMISSION_COUNTER by 1;

[0160] 2>If PREAMBLE_TRANSMISSION_COUNTER=preambleTransMax+1:

[0161] 3>Indicate random access problems to upper layers.

[0162] 3> If this random access procedure is triggered for an SI request:

[0163] 4> The random access procedure is considered to have been completed unsuccessfully.

[0164] 2> If the random access procedure is not completed:

[0165] 3>If RA_TYPE is set to 4-stepRA:

[0166] 4> Select a random backoff time based on a uniform distribution between 0 and PREAMBLE_BACKOFF;

[0167] 4> If the criteria for selecting a contention-free random access resource (as defined in section 5.1.2) are met during the backoff time:

[0168] 5>Perform the random access resource selection procedure (see Section 5.1.2);

[0169] 4> Otherwise:

[0170] 5> Perform the random access resource selection procedure after the backoff time (see section 5.1.2).

[0171] 3> Otherwise (i.e., RA_TYPE is set to 2-stepRA):

[0172] 4> If msgA-TransMax is applied (see Section 5.1.1a) and PREAMBLE_TRANSMISSION_COUNTER = msgA-TransMax+1:

[0173] 5> Set RA_TYPE to 4-stepRA;

[0174] 5> Perform initialization of variables specific to the random access type as specified in Section 5.1.1a;

[0175] 5> Clear the HARQ buffer in the MSGA buffer used to transmit MAC PDU;

[0176] 5> Abandon the explicitly transmitted contention-free 2-step RA type random access resources (if any);

[0177] 5> Perform random access resource selection as specified in section 5.1.2.

[0178] 4> Otherwise:

[0179] 5> Select a random backoff time based on a uniform distribution between 0 and PREAMBLE_BACKOFF;

[0180] 5> If the criteria for selecting a contention-free random access resource (as defined in section 5.1.2a) are met during the backoff time:

[0181] 6> Perform the random access resource selection procedure for 2-step RA type as specified in section 5.1.2a.

[0182] 5> Otherwise:

[0183] 6> Perform random access resource selection for 2-step RA type procedure after backoff time (see section 5.1.2a)

[0184] 5.1.6 Completion of random access procedure

[0185] After completing the random access procedure, the MAC entity shall:

[0186] 1> Abandon any explicitly transmitted contention-free random access resources for 2-step RA type and 4-step RA type, except for 4-step RA type contention-free random access resources for beam failure recovery request (if any);

[0187] 1> Clear the HARQ buffer in the Msg3 buffer and MSGA buffer used to transmit MAC PDU.

[0188] Upon successful completion of the Random Access procedure initiated for a DAPS handover, the target MAC entity shall:

[0189] 1> Indicates to the upper layer the successful completion of the random access procedure.

[0190] ******************************End of Quote*******************************

[0191] DRX operation is specified in TS 38.321 [2] (3GPP TS 38.321 V16.3.0, “NR, MAC Protocol Specification”) as follows:

[0192] ****************************** Quote starts [2] ******************************

[0193] 5.7 Discontinuous Reception (DRX)

[0194] The MAC entity may be configured by RRC with DRX functionality that controls the PDCCH of the UE, which monitors the activity of the MAC entity's C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI and AI-RNTI. When using DRX operation, the MAC entity shall also monitor the PDCCH in accordance with the requirements present in other sections of this specification. When in RRC_CONNECTED, if DRX is configured, then for all activated serving cells, the MAC entity may monitor the PDCCH discontinuously using the DRX operation specified in this section; otherwise the MAC entity shall monitor the PDCCH as specified in TS 38.213 [6].

[0195] NOTE 1: If sidelink resource allocation mode 1 is configured by RRC, then DRX functionality is not configured.

[0196] RRC controls DRX operation by configuring the following parameters:

[0197] -drx-onDurationTimer: duration when the DRX cycle starts;

[0198] -drx-SlotOffset: Delay before starting drx-onDurationTimer;

[0199] -drx-InactivityTimer: duration after the PDCCH opportunity where the PDCCH indicates a new UL or DL ​​transmission by the MAC entity;

[0200] -drx-RetransmissionTimerDL (per DL HARQ process, except the broadcast process): maximum duration until a DL retransmission is received;

[0201] -drx-RetransmissionTimerUL (per UL HARQ process): maximum duration until a grant for UL retransmission is received;

[0202] -drx-LongCycleStartOffset: the long DRX cycle and the drx-StartOffset of the subframe that defines the start of the long and short DRX cycles;

[0203] -drx-ShortCycle (optional): short DRX cycle;

[0204] -drx-ShortCycleTimer (optional): duration that the UE will follow the short DRX cycle;

[0205] -drx-HARQ-RTT-TimerDL (per DL HARQ process, except broadcast process): minimum duration before the MAC entity expects a DL assignment of a HARQ retransmission;

[0206] -drx-HARQ-RTT-TimerUL (per UL HARQ process): minimum duration before the MAC entity expects a UL HARQ retransmission grant;

[0207] -ps-Wakeup (optional): Start the configuration of the associated drx-onDurationTimer when listening but no DCP is detected;

[0208] -ps-TransmitOtherPeriodicCSI (optional): configuration to report periodic CSI other than L1-RSRP on PUCCH during the duration indicated by drx-onDurationTimer if DCP is configured but the associated drx-onDurationTimer is not started;

[0209] -ps-TransmitPeriodicL1-RSRP (optional): configuration to transmit periodic CSI for L1-RSRP on PUCCH during the duration indicated by drx-onDurationTimer if DCP is configured but the associated drx-onDurationTimer is not started;

[0210] The service cells of the MAC entity can be configured by RRC in two DRX groups with separate DRX parameters. When RRC does not configure a secondary DRX group, there is only one DRX group and all service cells belong to the one DRX group. When two DRX groups are configured, each service cell is uniquely assigned to either of the two groups. The DRX parameters configured separately for each DRX group are: drx-onDurationTimer, drx-InactivityTimer. The DRX parameters common to the DRX groups are: drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL and drx-HARQ-RTT-TimerUL.

[0211] When a DRX cycle is configured, the action time for the serving cells in the DRX group includes the following times:

[0212] - the drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or

[0213] -drx-RetransmissionTimerDL or drx-RetransmissionTimerUL is running on any serving cell in the DRX group; or

[0214] -ra-ContentionResolutionTimer (as described in Section 5.1.5) or msgB-ResponseWindow (as described in Section 5.1.4a) is running; or

[0215] - A scheduling request is sent on the PUCCH and is pending (as described in section 5.4.4); or

[0216] - Not receiving a newly transmitted PDCCH indicating a C-RNTI addressed to the MAC entity after successfully receiving a random access response for a random access preamble that was not selected by the MAC entity among contention-based random access preambles (as described in sections 5.1.4 and 5.1.4a).

[0217] When DRX is configured, the MAC entity shall:

[0218] 1> If a MAC PDU is received in a configured downlink assignment:

[0219] 2> Start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback ends;

[0220] 2>Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0221] 1> If a MAC PDU is transmitted in a configured uplink grant and no LBT failure indication is received from lower layers:

[0222] 2> Start the drx-HARQ-RTT-TimerUL of the corresponding HARQ process in the first symbol after the end of the first transmission (within the cluster) of the corresponding PUSCH transmission;

[0223] 2> Stop the drx-RetransmissionTimerUL of the corresponding HARQ process at the first transmission (within the cluster) corresponding to the PUSCH transmission.

[0224] 1> If drx-HARQ-RTT-TimerDL expires:

[0225] 2> If the data corresponding to the HARQ process is not successfully decoded:

[0226] 3> Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the expiration of the drx-HARQ-RTT-TimerDL.

[0227] 1> If drx-HARQ-RTT-TimerUL expires:

[0228] 2> Start the drx-RetransmissionTimerUL of the corresponding HARQ process in the first symbol after the expiration of drx-HARQ-RTT-TimerUL.

[0229] 1> If a DRX command MAC CE or a long DRX command MAC CE is received:

[0230] 2> Stop drx-onDurationTimer for each DRX group;

[0231] 2> Stop the drx-InactivityTimer for each DRX group.

[0232] 1> If the drx-InactivityTimer for the DRX group expires:

[0233] 2> If short DRX cycle is configured:

[0234] 3> Start or restart the drx-ShortCycleTimer for this DRX group in the first symbol after the expiration of the drx-InactivityTimer;

[0235] 3> Use short DRX cycle for this DRX group.

[0236] 2> Otherwise:

[0237] 3> Use long DRX cycle for this DRX group.

[0238] 1> If DRX command MAC CE is received:

[0239] 2> If short DRX cycle is configured:

[0240] 3> Start or restart the drx-ShortCycleTimer for each DRX group in the first symbol after the DRX command MAC CE reception ends;

[0241] 3> Use a short DRX cycle for each DRX group.

[0242] 2> Otherwise:

[0243] 3> Use a long DRX cycle for each DRX group.

[0244] 1> If the drx-ShortCycleTimer for the DRX group expires:

[0245] 2> Use the long DRX cycle for this DRX group.

[0246] 1> If a long DRX command MAC CE is received:

[0247] 2> Stop the drx-ShortCycleTimer for each DRX group;

[0248] 2> Use a long DRX cycle for each DRX group.

[0249] 1> If a short DRX cycle is used for the DRX group, and [(SFN×10)+subframe number] modulo (drx-ShortCycle)=(drx-StartOffset) modulo (drx-ShortCycle):

[0250] 2> Start the drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the subframe.

[0251] 1> If the long DRX cycle is used for the DRX group, and [(SFN×10)+subframe number] modulo (drx-LongCycle)=drx-StartOffset:

[0252] 2> If DCP monitoring is configured for the active DL BWP as specified in TS 38.213 [6] section 10.3:

[0253] 3> if a DCP indication is received from lower layers indicating the start of the drx-onDurationTimer associated with the current DRX cycle, as specified in TS 38.213 [6]; or

[0254] 3> If all DCP opportunities in the time domain associated with the current DRX cycle occur in the active time as specified in TS 38.213 [6], consider the Grant / Assignment / DRX Command MAC CE / Long DRX Command MAC CE received and the Scheduling Request sent 4 ms before the start of the last DCP opportunity, or during a Measurement Gap, or when the MAC entity monitors PDCCH transmissions on the search space indicated by recoverySearchSpaceId of the SpCell identified by the C-RNTI while the ra-ResponseWindow is in operation (as specified in section 5.1.4); or

[0255] 3> If ps-Wakeup is configured to use the value true and no DCP indication associated with the current DRX cycle is received from lower layers:

[0256] 4> Start drx-onDurationTimer after drx-SlotOffset from the beginning of the subframe.

[0257] 2> Otherwise:

[0258] 3> Start drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the subframe.

[0259] NOTE 2: In case of unaligned SFN across carriers in a cell group, the SFN of the SpCell is used to calculate the DRX duration.

[0260] 1> If the DRX group is in the active time:

[0261] 2> monitor the PDCCH on the serving cells in this DRX group as specified in TS 38.213 [6];

[0262] 2> If PDCCH indicates DL transmission:

[0263] 3> Start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback ends;

[0264] NOTE 3: When HARQ feedback is deferred by PDSCH to HARQ feedback timing indicating a non-numeric k1 value, as specified in TS 38.213 [6], the corresponding transmit opportunity for sending DL HARQ feedback is indicated in the subsequent PDCCH requesting HARQ-ACK feedback.

[0265] 3>Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0266] 3> If the PDSCH-HARQ_feedback timing indicates a non-numeric k1 value, as specified in TS 38.213 [6]:

[0267] 4> Start drx-RetransmissionTimerDL in the first symbol after PDSCH transmission for the corresponding HARQ process.

[0268] 2> If PDCCH indicates UL transmission:

[0269] 3> Start the drx-HARQ-RTT-TimerUL of the corresponding HARQ process in the first symbol after the end of the first transmission (in the cluster) of the corresponding PUSCH transmission;

[0270] 3>Stop the drx-RetransmissionTimerUL corresponding to the HARQ process.

[0271] 2> If PDCCH indicates a new transmission (DL or UL) on a serving cell in this DRX group:

[0272] 3> Start or restart the drx-InactivityTimer for this DRX group in the first symbol after the end of PDCCH reception.

[0273] 2> If the HARQ process receives downlink feedback information and indicates confirmation:

[0274] 3>Stop the drx-RetransmissionTimerUL corresponding to the HARQ process.

[0275] 1> if DCP monitoring is configured for the active DL BWP as specified in TS 38.213 [6] section 10.3; and

[0276] 1> If the current symbol n appears within the duration of drx-onDurationTimer; and

[0277] 1> If the drx-onDurationTimer associated with the current DRX cycle is not started as specified in this section:

[0278] 2> If, when evaluating all DRX active time conditions specified in this section, the MAC entity will not be in active time considering the grant / assignment / DRX command MAC CE / long DRX command MAC CE received 4 ms before symbol n and the scheduling request sent, then:

[0279] 3> Periodic SRS and semi-static SRS are not transmitted, as defined in TS 38.214 [7];

[0280] 3> Do not report the semi-static CSI configured on PUSCH;

[0281] 3> If ps-TransmitPeriodicL1-RSRP is not configured to use the value true:

[0282] 4> Periodic CSI as L1-RSRP on PUCCH is not reported.

[0283] 3> If ps-TransmitOtherPeriodicCSI is not configured to use the value true:

[0284] 4> Do not report periodic CSI other than L1-RSRP on PUCCH.

[0285] 1> Otherwise:

[0286] 2> In the current symbol n, if, when evaluating all DRX action time conditions specified in this section, the DRX group will not be in action time, taking into account the grant / assignment and DRX command MAC CE / long DRX command MAC CE scheduled on the serving cell in this DRX group received 4 ms before symbol n and the scheduling request sent, then:

[0287] 3> Periodic SRS and semi-static SRS defined in TS 38.214 [7] are not transmitted in this DRX group;

[0288] 3> Do not report CSI on PUCCH and semi-static CSI configured on PUSCH in this DRX group.

[0289] 2> If CSI mask (csi-Mask) is set by the upper layer:

[0290] 3> In the current symbol n, if, when evaluating all DRX action time conditions specified in this section, the grant / assignment and DRX command MAC CE / long DRX command MAC CE scheduled on the serving cell in this DRX group received 4 ms before symbol n are taken into account, the drx-onDurationTimer of the DRX group shall not be running; and

[0291] 4> CSI on PUCCH is not reported in this DRX group.

[0292] NOTE 4: If the UE multiplexes CSI configured on PUCCH with other overlapping UCI according to the procedure specified in TS 38.213 [6] section 9.2.5, and this CSI multiplexed with other UCI is to be reported on PUCCH resources outside the DRX active time of the DRX group in which this PUCCH is configured, then it is up to the UE implementation whether to report this CSI multiplexed with other UCI.

[0293] Regardless of whether the MAC entity monitors the PDCCH on the serving cells in the DRX group, the MAC entity transmits HARQ feedback, aperiodic CSI on the PUSCH, and aperiodic SRS as defined in TS 38.214 [7] on the serving cells in the DRX group when anticipating this situation.

[0294] If the PDCCH opportunity is incomplete (eg, the active time starts or ends in the middle of a PDCCH opportunity), then the MAC entity does not need to monitor the PDCCH.

[0295] ******************************End of Quote*******************************

[0296] In the current NR MAC specification, such as 3GPP TS 38.321 V16.3.0 “NR, MAC Protocol Specification”, a user equipment (UE) can perform a random access (RA) procedure using a 4-step and / or 2-step RA. In the 4-step RA procedure, the UE sends a RA preamble (Msg1) and receives a RAR (Msg2) from the network (NW). In response to receiving Msg2, the UE sends Msg3 using the UL grant in Msg2 and starts a contention resolution timer (e.g., ra-ContentionResolutionTimer) in the first symbol after the end of Msg3 transmission. In response to receiving Msg3, the NW sends Msg4 to notify the UE of the completion of the RA procedure. If the NW fails to receive Msg3 after sending Msg2, the NW sends a dynamic grant (DG) for retransmission to the UE. The dynamic UL grant for Msg3 retransmission is addressed to the temporary cell radio network temporary identifier (C-RNTI) of the UE on the physical downlink control channel (PDCCH). In response to receiving the DG, the UE retransmits Msg3 and restarts the contention resolution timer (eg, ra-ContentionResolutionTimer) in the first symbol after the Msg3 retransmission ends.

[0297] In the 2-step RA procedure, the UE sends an MSGA containing an RA preamble and a physical uplink shared channel (PUSCH) payload. In response to receiving the MSGA, the NW sends an MSGB to notify the UE to complete the RA procedure. If the NW receives the RA preamble but fails to receive the PUSCH payload in the MSGA, the NW sends an MSGB (e.g., with fallbackRAR) to notify the UE to fall back to Msg3. The UE transmits Msg3 using the uplink (UL) grant in the MSGB (e.g., with fallbackRAR) and starts a contention resolution timer (e.g., ra-ContentionResolutionTimer) in the first symbol after the end of the Msg3 transmission. In response to receiving Msg3, the NW sends an Msg4 to notify the UE to complete the RA procedure. If the NW fails to receive Msg3 after sending the MSGB (e.g., with fallbackRAR), the NW sends a DG for retransmission to the UE. In response to receiving the DG, the UE retransmits Msg3 and restarts the contention resolution timer (eg, ra-ContentionResolutionTimer) in the first symbol after the Msg3 retransmission ends.

[0298] When the contention resolution timer (e.g., ra-ContentionResolutionTimer) is running, the UE monitors the PDCCH to resolve possible RA contention. The contention resolution timer (e.g., ra-ContentionResolutionTimer) is used to receive Msg4 and / or DG after Msg3 transmission / retransmission. The contention resolution timer (e.g., ra-ContentionResolutionTimer) is used for contention resolution in the RA procedure. The contention resolution timer (e.g., ra-ContentionResolutionTimer) is configured by the NW in the RA configuration (e.g., RACH-ConfigCommon, RACH-ConfigCommonTwoStepRA), such as 3GPP TS 38.331 V16.3.1 "NR, RRC Protocol Specification". And, the initial value (e.g., length) of the contention resolution timer (e.g., ra-ContentionResolutionTimer) can be configured to 8, 16, 24, 32, 40, 48, 56 and / or 64 subframes. When the UE receives Msg4, the UE stops the contention resolution timer (e.g., ra-ContentionResolutionTimer) and regards the RA procedure as successfully completed. When the UE receives a DG for retransmission of Msg3 (e.g., an UL grant addressed to the temporary C-RNTI of the UE and / or when the contention resolution timer is running), the UE restarts the contention resolution timer (e.g., ra-ContentionResolutionTimer) and retransmits Msg3.

[0299] The above processing of contention resolution timers (e.g., ra-ContentionResolutionTimer) may generally be applicable (e.g., in terrestrial network (TN) cells). On the other hand, New Radio (NR) introduces non-terrestrial networks (NTN) to use air / space vehicles as platforms for providing mobile services, such as RP-201256 "Solutions for NR to support non-terrestrial networks (NTN)". The UE may link, camp on and / or connect to a control / space-related NTN network for transmission. NTN includes various platforms, including low earth orbit (LEO) satellites, medium earth orbit (MEO) satellites, high elliptical orbit (HEO) satellites, geostationary orbit (GEO) satellites, non-geostationary orbit (NGSO) satellites and / or high altitude platform stations (HAPs). For more detailed information on different NTN platforms, see 3GPP TR 38.821V16.0.0 "Solutions for NR to support non-terrestrial networks (NTN)". NTN can provide wide area coverage and provide NW access when terrestrial networks (TN) are not feasible (e.g., in deserts, polar regions, and / or on airplanes).

[0300] However, for long distances from the UE to the platform, transmission between the UE and the NW in the NTN requires a longer round-trip time (RTT) than transmission between the UE and the NW in the TN. That is, there is a round-trip delay (RTD) between the UE and the NW in the NTN. After the transmission / retransmission of Msg3, the UE may need more time to receive the Msg4 and / or DG for retransmission. And, the UE may unnecessarily listen to the PDCCH during the RTT, which results in power consumption. According to the work item (WI) description (e.g., RP-201256, "Solutions for NR to support non-terrestrial networks (NTN)" and TR 38.821), a timing offset for the start of a contention resolution timer (e.g., ra-ContentionResolutionTimer) may be introduced in the NTN. When the UE is located in and / or connected to an NTN cell, the UE may apply and / or use a timing offset. The timing offset may be a time delay between the UE and the NW in the NTN.

[0301] like Figure 5As shown, the UE may transmit Msg3 using the UL grant received in Msg2 and / or MSGB (e.g., with fallbackRAR). In certain cases (e.g., in NTN cells), the UE may start a contention resolution timer (e.g., ra-ContentionResolutionTimer) after a timing offset after Msg3 transmission (e.g., at the time when Msg3 transmission ends + timing offset). While the contention resolution timer (e.g., ra-ContentionResolutionTimer) is running, the UE may monitor a PDCCH addressed to a temporary C-RNTI. If the UE receives a DG for Msg3 retransmission (e.g., an UL grant addressed to the temporary C-RNTI of the UE), the UE may retransmit Msg3 using the DG. In certain cases (e.g., in NTN cells), the UE may restart a contention resolution timer (e.g., ra-ContentionResolutionTimer) after a timing offset after Msg3 retransmission (e.g., at the time when Msg3 retransmission ends + timing offset). However, the contention resolution timer (e.g., ra-ContentionResolutionTimer) may expire during the timing offset after Msg3 retransmission (e.g., after Msg3 retransmission but before the contention resolution timer is restarted). The contention resolution timer (e.g., ra-ContentionResolutionTimer) may expire before it is restarted. Once the contention resolution timer (e.g., ra-ContentionResolutionTimer) expires, the UE may consider contention resolution to be unsuccessful. The UE may retransmit another Msg1 after contention resolution is considered to be unsuccessful.

[0302] To avoid this problem, the UE may apply a timing offset to the start of a contention resolution timer (e.g., ra-ContentionResolutionTimer) after Msg3 transmission, and may not apply a timing offset to the restart of a contention resolution timer (e.g., ra-ContentionResolutionTimer) after Msg3 retransmission. The UE may start a contention resolution timer (e.g., ra-ContentionResolutionTimer) after the timing offset after Msg3 transmission (e.g., at the time of Msg3 transmission end+timing offset). Furthermore, the UE may restart the contention resolution timer (e.g., ra-ContentionResolutionTimer) after Msg3 retransmission (e.g., at the end of Msg3 transmission).

[0303] like Figure 6As shown, considering the large RTD in NTN, the length of the contention resolution timer (e.g., ra-ContentionResolutionTimer) without timing offset may not be enough to receive the NW response (e.g., Msg4) of some NTN platforms (e.g., GEO). In NTN, the maximum RTD of GEO is 541.46ms, and the maximum RTD of LEO is 25.77ms, such as 3GPP TR38.821V16.0.0 "Solution for NR Support of Non-Terrestrial Networks (NTN)". And, in the current NR Radio Resource Control (RRC) specification, such as 3GPP TS 38.331V16.3.1 "NR, RRC Protocol Specification", the maximum length of the contention resolution timer (e.g., ra-ContentionResolutionTimer) is 64 subframes (i.e., 64ms), which is much shorter than 541.46ms. Furthermore, even if the length of the contention resolution timer (e.g., ra-ContentionResolutionTimer) can be long enough to cover a large RTT to receive a NW response (e.g., Msg4, DG) in the NTN, since the UE can only receive the NW response after the RTT, the actual duration left for the NW to schedule the response (e.g., Msg4, DG) to the UE during the contention resolution timer is reduced. A contention resolution timer (e.g., ra-ContentionResolutionTimer) without a timing offset may limit the scheduling flexibility of the NW.

[0304] In order to solve one or more of the above problems, the UE may apply different values / lengths to the first timer when the UE starts the first timer and the UE restarts the first timer. The UE may start the first timer with a first value / length and restart the first timer with a second value / length. The second value / length may be different from the first value / length (e.g., greater than / longer than the first value / length). The second value / length may be the first value / length plus a timing offset. The first value / length and the second value / length may be received from the NW in the same configuration. The first value / length and the second value / length may be received from the NW in different configurations. The configuration may be an RA configuration and / or an NTN configuration. The first timer may be a contention resolution timer (e.g., ra-ContentionResolutionTimer). The first timer may be a timer for contention resolution in an RA procedure. The first timer with a first value / length may be started after Msg3 is transmitted (e.g., at the time when Msg3 transmission ends + timing offset). The first timer with a first value / length may be started in symbol n+x. Symbol n is the first symbol after the end of Msg3 transmission. x is the length of the timing offset. The first timer with the second value / length may be restarted after Msg3 retransmission (e.g., at the end of Msg3 retransmission). The first timer with the second value / length may be restarted in the first symbol after the end of Msg3 retransmission. The first timer with the first value / length and the first timer with the second value / length may be configured in the same configuration. The first timer with the first value / length and the first timer with the second value / length may be configured in different configurations. The configuration may be an RA configuration and / or an NTN configuration. The first timer with the first value / length and the first timer with the second value / length may be the same timer with different values ​​in the configuration. The first timer with the first value / length and the first timer with the second value / length may be two different timers in the configuration.

[0305] For example, Figure 7As shown in , the UE may transmit Msg3 using the UL grant received in Msg2 and / or MSGB (e.g., with fallbackRAR). The UE may start a first timer after a timing offset after the transmission of Msg3 (e.g., at the time when the Msg3 transmission ends + the timing offset). While the first timer is running, the UE may monitor the PDCCH addressed to the temporary C-RNTI (and possibly receive a DG for retransmission). The UE may retransmit Msg3 using the DG. The UE may restart the first timer after the Msg3 retransmission ends (at the end of the Msg3 retransmission), with the length of the first timer extending the timing offset. While the first timer is running, the UE may monitor the PDCCH addressed to the temporary C-RNTI (and possibly receive Msg4). The UE may regard the RA procedure as successfully completed after receiving Msg4.

[0306] In order to solve one or more of the above problems, the UE may restart the first timer after Msg3 retransmission (for example, at the end of Msg3 retransmission). Additionally or alternatively, when the first timer expires after Msg3 retransmission, the UE may restart the first timer. Additionally or alternatively, the UE may restart the first timer after the timing offset after Msg3 retransmission (for example, at the time of Msg3 retransmission end+timing offset). The first timer may be a contention resolution timer (for example, ra-ContentionResolutionTimer). The first timer may be a timer for contention resolution in the RA procedure. The first timer may be started after Msg3 transmission (for example, at the time of Msg3 transmission end+timing offset). The first timer may be started in symbol n+x. Symbol n is the first symbol after the end of Msg3 transmission. x is the length of the timing offset. The first timer may be restarted after Msg3 retransmission (for example, at the end of Msg3 retransmission). The first timer may not be restarted after Msg3 retransmission (for example, at the end of Msg3 retransmission). Based on whether at least one condition is satisfied, when the first timer expires / after the first timer expires / after the first timer expires / in response to the first timer expiring, the first timer may be restarted. If an UL grant for Msg3 retransmission has been received, when the first timer expires / after the first timer expires / after the first timer expires / in response to the first timer expiring, the first timer may be restarted. If Msg3 has been retransmitted, when the first timer expires / after the first timer expires / after the first timer expires / in response to the first timer expiring, the first timer may be restarted. When the first timer expires during a duration within a timing offset after Msg3 retransmission / after the first timer expires during a duration within a timing offset after Msg3 retransmission / after the first timer expires during a duration within a timing offset after Msg3 retransmission / in response to the first timer expiring during a duration within a timing offset after Msg3 retransmission, the first timer may be restarted. The first timer may be restarted after the timing offset after Msg3 retransmission (e.g., at the time of Msg3 retransmission end+timing offset). The first timer may be restarted in the first symbol after the Msg3 retransmission ends. The first timer may be restarted in symbol m+x. Symbol m is the first symbol after the end of Msg3 retransmission. x is the length of the timing offset. The first timer may not be restarted after the timing offset after Msg3 retransmission (e.g., at the time of Msg3 retransmission end+timing offset). The first timer may be configured in the RA configuration and / or the NTN configuration.

[0307] For example, Figure 8 As shown in , the UE may transmit Msg3 using the UL grant received in Msg2 and / or MSGB (e.g., with fallbackRAR). The UE may start a first timer after a timing offset after the transmission of Msg3 (e.g., at the time when the Msg3 transmission ends + the timing offset). While the first timer is running, the UE may monitor the PDCCH addressed to the temporary C-RNTI (and possibly receive a DG for retransmission). The UE may retransmit Msg3 using the DG. The UE may restart the first timer after the retransmission of Msg3 (e.g., at the end of the retransmission of Msg3). The UE may restart the first timer after the timing offset after the retransmission of Msg3 (e.g., at the time when the Msg3 retransmission ends + the timing offset). While the first timer is running, the UE may monitor the PDCCH addressed to the temporary C-RNTI (and possibly receive Msg4). The UE may regard the RA procedure as successfully completed after receiving Msg4.

[0308] For example, the UE may transmit Msg3 using the UL grant received in Msg2 and / or MSGB (e.g., with fallbackRAR). The UE may start a first timer after a timing offset after the transmission of Msg3 (e.g., at a time when the transmission of Msg3 ends + the timing offset). While the first timer is running, the UE may monitor a PDCCH addressed to the temporary C-RNTI (and possibly receive a DG for retransmission). The UE may retransmit Msg3 using the DG. When the first timer expires during the timing offset after the retransmission of Msg3 (or in response to the first timer expiring during the timing offset after the retransmission of Msg3), the UE may restart the first timer. The UE may restart the first timer after a timing offset after the retransmission of Msg3 (e.g., at a time when the retransmission of Msg3 ends + the timing offset). While the first timer is running, the UE may monitor a PDCCH addressed to the temporary C-RNTI (and possibly receive Msg4). The UE may regard the RA procedure as successfully completed after receiving Msg4.

[0309] The UE may monitor the PDCCH after Msg3 transmission. The UE may monitor the PDCCH after the timing offset after Msg3 transmission (e.g., at the time of Msg3 transmission end + timing offset) until Msg4 is received. The UE may monitor the PDCCH until contention resolution is deemed successful. The UE may monitor the PDCCH until contention resolution is deemed unsuccessful. The UE may monitor the PDCCH during a specific period after Msg3 retransmission.

[0310] For example, Fig. 9As shown, the UE may transmit Msg3 using the UL grant received in Msg2 and / or MSGB (e.g., with fallbackRAR). In response to the Msg3 transmission, the UE may receive a dynamic UL grant for Msg3 retransmission. The UE may retransmit Msg3 using the dynamic UL grant. The UE may receive Msg4 in response to the Msg3 retransmission.

[0311] In the above case, the UE may monitor the PDCCH during the first period. The UE may not monitor the PDCCH during the first period. The first period may start after the Msg3 retransmission (eg, at the end of the Msg3 retransmission), for example Fig. 9 The first period may end after the timing offset after Msg3 retransmission (e.g., at the time when Msg3 retransmission ends + the timing offset), for example Fig. 9 The time point t3 in .

[0312] Also in the above case, the UE may monitor the PDCCH during the second period. The UE may not monitor the PDCCH during the second period. The second period may start after the Msg3 retransmission (eg, at the end of the Msg3 retransmission), for example Fig. 9 The second period may end after the first timer expires (eg, at the time when Msg3 transmission ends + timing offset + length of the first timer), for example Fig. 9 The time point t2 in .

[0313] Also in the above case, the UE may monitor the PDCCH during the third period. The UE may not monitor the PDCCH during the third period. The third period may start after the first timer expires (e.g., at the time when Msg3 transmission ends + timing offset + length of the first timer), for example Fig. 9 The third period may end after the timing offset after Msg3 retransmission (eg, at the time of Msg3 retransmission end + timing offset), for example Fig. 9 The time point t3 in .

[0314] A restart mechanism (e.g., the restart mechanism mentioned above) can prevent the contention resolution timer (e.g., ra-ContentionResolutionTimer) from expiring unexpectedly; and the UE may need to monitor the PDCCH all the time. Considering that the UE is unlikely to receive a NW response (e.g., Msg4, DG) during the timing offset after Msg3 transmission and / or retransmission, it may not be necessary to monitor the PDCCH all the time. In order to reduce power consumption, some other solutions can be considered.

[0315] In order to solve one or more of the above problems, when receiving an UL grant for Msg3 retransmission (or in response to the reception), the UE may stop the first timer. Alternatively or additionally, at the time of Msg3 retransmission / after Msg3 retransmission / after Msg3 retransmission (or in response to Msg3 retransmission), the UE may stop the first timer. The UL grant may be a dynamic grant addressed to the temporary C-RNTI. The UL grant may be received by the UE from the NW when the first timer is in operation. The first timer may be a contention resolution timer (e.g., ra-ContentionResolutionTimer). The first timer may be a timer for contention resolution in the RA procedure. The first timer may be started after Msg3 transmission and / or retransmission (e.g., at the time when Msg3 transmission and / or retransmission ends + timing offset). The first timer may be started in symbol n+x. Symbol n is the first symbol after the end of Msg3 transmission and / or retransmission. x is the length of the timing offset. The first timer may be started in the first symbol after the end of Msg3 transmission and / or retransmission plus the timing offset. The first timer may be started after receiving an UL grant for Msg3 retransmission (or in response to the reception). The first timer may be started in symbol m+x. Symbol m is the first symbol after receiving the end of UL grant for Msg3 retransmission and / or the first symbol after the end of Msg3 retransmission. x is the length of the timing offset. When the first timer stops, the UE may not regard contention resolution as unsuccessful. When the first timer stops, the UE may continue the RA procedure. When the first timer expires, the UE may regard contention resolution as unsuccessful. The first timer may be configured in the RA configuration and / or the NTN configuration.

[0316] When receiving (or in response to) an UL grant for Msg3 retransmission and / or after performing (or in response to) performing an Msg3 retransmission, the processing of the first timer may be different when the UE is in the TN and in the NTN. When receiving (or in response to) an UL grant for Msg3 retransmission, the UE may determine whether to stop the first timer (e.g., based on whether the UE is in the TN or in the NTN, and / or whether the Msg3 transmission (retransmission) is performed in the TN or in the NTN). When receiving (or in response to) an UL grant for Msg3 retransmission, if the Msg3 transmission and / or retransmission is in the NTN (or if the UE is in the NTN), the UE may determine to stop the first timer. Then, the UE may start the first timer after the Msg3 retransmission plus the timing offset (e.g., at the time when the Msg3 retransmission ends plus the timing offset). When receiving an UL grant for Msg3 retransmission (or in response to the reception), if the Msg3 transmission and / or retransmission is in the NTN (or if the UE is in the NTN), the UE may determine to start the first timer after the Msg3 retransmission plus the timing offset (e.g., at the time when the Msg3 retransmission ends plus the timing offset). When receiving an UL grant for Msg3 retransmission (or in response to the reception), if the Msg3 transmission and / or retransmission is not in the NTN (or if the UE is not in the NTN), the UE may determine not to stop the first timer. When receiving an UL grant for Msg3 retransmission (or in response to the reception), if the Msg3 transmission and / or retransmission is in the TN (or if the UE is in the TN), the UE may determine not to stop the first timer. When receiving an UL grant for Msg3 retransmission (or in response to the reception), if the Msg3 transmission and / or retransmission is not in the NTN (or if the UE is not in the NTN), the UE may determine to restart the first timer. When receiving an UL grant for Msg3 retransmission (or in response to the reception), if the Msg3 transmission and / or retransmission is in the TN (or if the UE is in the TN), the UE may determine to restart the first timer. After performing Msg3 retransmission (or in response to the performance), if the Msg3 transmission and / or retransmission is in the NTN (or if the UE is in the NTN), the UE may determine to start the first timer after the Msg3 retransmission plus the timing offset (e.g., at the time when the Msg3 retransmission ends plus the timing offset). After performing Msg3 retransmission (or in response to the performance), if the Msg3 transmission and / or retransmission is not in the NTN (or if the UE is not in the NTN), the UE may determine to restart the first timer.After performing the Msg3 retransmission (or in response to the performance), if the Msg3 transmission and / or retransmission is in the TN (or if the UE is in the TN), the UE may determine to restart the first timer.

[0317] For example, Fig.10 As shown, the UE may transmit Msg3 in the NTN using the UL grant received in Msg2 (e.g., random access response RAR) and / or MSGB (e.g., with fallback RAR). The UE in the NTN may be in and / or connected to the NTN cell. The UE may start a first timer after a timing offset after the transmission of Msg3 (e.g., at the time when the Msg3 transmission ends + the timing offset). While the first timer is running, the UE may monitor the PDCCH addressed to the temporary C-RNTI (and may receive a DG for retransmission). When the DG for retransmission is received (or in response to the reception) (e.g., based on the transmission of Msg3 in the NTN), the UE may stop the first timer. The UE may retransmit Msg3 using the DG. The UE may start the first timer after a timing offset after the retransmission of Msg3 (e.g., at the time when the Msg3 retransmission ends + the timing offset) (e.g., based on the transmission of Msg3 in the NTN). While the first timer is running, the UE may monitor the PDCCH addressed to the temporary C-RNTI (and possibly receive Msg4). After receiving Msg4, the UE may consider the RA procedure to be successfully completed and / or stop the first timer. If the first timer expires, the UE may consider the contention resolution (e.g., of the RA procedure) to be unsuccessful.

[0318] For example, the UE may transmit Msg3 in the TN using an UL grant received in Msg2 (e.g., a random access response (RAR)) and / or MSGB (e.g., with fallbackRAR). The UE in the TN may be in and / or connected to a TN cell. The UE may start a first timer after the transmission of Msg3 (e.g., at the end of the transmission of Msg3). While the first timer is running, the UE may monitor a PDCCH addressed to a temporary C-RNTI (and possibly receive a DG for retransmission). The UE may retransmit Msg3 using the DG. The UE may restart the first timer after the retransmission of Msg3 (e.g., at the end of the retransmission of Msg3) (e.g., based on the transmission of Msg3 in the TN). While the first timer is running, the UE may monitor a PDCCH addressed to a temporary C-RNTI (and possibly receive Msg4). After receiving Msg4, the UE may regard the RA procedure as successfully completed and / or stop the first timer. If the first timer expires, the UE may consider the contention resolution (eg, of the RA procedure) as unsuccessful.

[0319] According to various embodiments of the present invention, when Msg3 transmission and / or retransmission is performed in NTN, the UE may be in and / or connected to the NTN cell. When the UE transmits and / or retransmits Msg3 in NTN, the UE may be in and / or connected to the NTN cell. When Msg3 transmission and / or retransmission is performed in TN, the UE may be in and / or connected to the TN cell. When the UE transmits and / or retransmits Msg3 in TN, the UE may be in and / or connected to the TN cell.

[0320] According to various embodiments of the present invention, the UL grant may be a dynamic grant and / or a dynamic UL grant (eg, addressed to a temporary C-RNTI). A dynamic UL grant may be replaced with and / or referred to as a dynamic grant.

[0321] According to various embodiments of the present invention, the timing offset may be a period / length (e.g., RTT, RTD) of a time delay between a UE and a NW in the NTN. According to various embodiments of the present invention, the "timing offset after the end of Msg3 transmission" may be a certain period / duration after the end of Msg3 transmission. According to various embodiments of the present invention, the "timing offset after the end of Msg3 retransmission" may be a certain period / duration after the end of Msg3 retransmission.

[0322] According to various embodiments of the present invention, there may be a second timer used as a timing offset. The second timer may be configured by the NW in the RA and / or NTN configuration. The length / value of the second timer may be a timing offset. The length / value of the second timer may be x symbols. The second timer may be started after (or in response to) the transmission and / or retransmission of Msg3. The second timer may be started in the first symbol after the end of the transmission and / or retransmission of Msg3. The second timer may be started after (or in response to the UL grant reception). The second timer may be started in the first symbol after the end of the UL grant reception. According to various embodiments of the present invention, the "timing offset after the end of the Msg3 transmission" may be the time when the second timer expires after the Msg3 transmission. According to various embodiments of the present invention, the "timing offset after the end of the Msg3 retransmission" may be the time when the second timer expires after the Msg3 retransmission. The first timer may be started and / or restarted when the second timer expires.

[0323] According to various embodiments of the present invention, the timing offset may be RTT, RTD and / or propagation delay (twice thereof) between the UE and the NW (e.g., gNB). The timing offset may include feeder link delay, UE-gNB delay and / or UE-platform delay. The UE may receive the timing offset from the NW and / or be configured by the NW to use the timing offset. The UE may calculate a UE-specific value as the timing offset. The UE may receive UE-specific and / or common values ​​from the NW and / or be configured by the NW to use UE-specific and / or common values, and use the values ​​to calculate the timing offset. The timing offset may be a common value (e.g., broadcast by the NW). The timing offset may be a UE-specific value (e.g., K_offset). The timing offset may be a common value (e.g., received from the NW) plus a UE-specific value (e.g., calculated by the UE). The timing offset may be a TA value calculated by the UE. The timing offset may be a TA value received from the NW. The timing offset may be estimated via Msg1 / MSGA transmission. The timing offset may be the TA received in Msg2 / MSGB (i.e., for Msg3 transmission) plus a common value. The value of the timing offset may be based on the GNSS / position of the UE. The timing offset may be common to UEs in the same serving cell / beam. The timing offset may be a delay value corresponding to a common reference point (e.g., cell center) experienced by all UEs served within the cell / beam. The timing offset may be UE specific. The timing offset may be a delay value corresponding to the total delay between the UE and the reference point (e.g., cell center) and / or NW (e.g., gNB), where this value is specific to each UE within the cell / beam.

[0324] In some cases (e.g., the contention resolution timer is restarted after the timing offset after Msg3 retransmission), the contention resolution timer (e.g., ra-ContentionResolutionTimer) may expire during the timing offset after Msg3 retransmission (e.g., after Msg3 retransmission but before Msg3 retransmission + timing offset). Once the contention resolution timer (e.g., ra-ContentionResolutionTimer) expires, the UE may consider contention resolution as unsuccessful. It may be assumed that when the contention resolution timer (e.g., ra-ContentionResolutionTimer) is started and / or restarted, the UE may apply the timing offset to the start (restart) of the contention resolution timer (e.g., ra-ContentionResolutionTimer). Based on this assumption, other modifications may need to be considered.

[0325] In order to solve one or more of the above problems, when the first timer expires, the UE may determine whether to regard contention resolution as unsuccessful based on at least whether a condition is satisfied. For example, the condition may be that the first timer expires during a duration within a timing offset after the transmission and / or retransmission of Msg3. For example, the condition may be that no UL grant (e.g., a dynamic UL grant addressed to a temporary C-RNTI on a PDCCH) for Msg3 retransmission is received when the first timer is in operation (and / or after the first timer is last started / restarted). For example, the condition may be that the PDCCH does not indicate / schedule Msg3 retransmission when the first timer is in operation (and / or after the first timer is last started / restarted). For example, the condition may be that Msg3 has not been retransmitted when the first timer is in operation (and / or after the first timer is last started / restarted). For example, the condition may be that the first timer will not be started / restarted subsequently (e.g., after the timing offset after the transmission / retransmission of Msg3). For example, the condition may be that the first timer will not be started / restarted after the timing offset (e.g., first timer expiration+timing offset).

[0326] In various embodiments, when the first timer expires, if the first timer does not expire (and / or expire) during the timing offset after the Msg3 transmission and / or retransmission, then the UE considers the contention resolution to be unsuccessful. Alternatively or additionally, when the first timer expires, if the first timer expires (and / or expires) during the timing offset after the Msg3 transmission and / or retransmission, then the UE does not consider the contention resolution to be unsuccessful.

[0327] In various embodiments, when the first timer expires, if no UL grant for retransmitting Msg3 is received when the first timer is running (and / or after the first timer is last started / restarted), then the UE considers contention resolution to be unsuccessful. Alternatively or additionally, when the first timer expires, if an UL grant for retransmitting Msg3 is received when the first timer is running (and / or after the first timer is last started / restarted), then the UE does not consider contention resolution to be unsuccessful.

[0328] In various embodiments, when the first timer expires, if the PDCCH did not indicate / schedule Msg3 retransmission when the first timer was running (and / or after the first timer was last started / restarted), then the UE considers contention resolution to be unsuccessful. Alternatively or additionally, when the first timer expires, if the PDCCH indicates / schedules Msg3 retransmission when the first timer was running (and / or after the first timer was last started / restarted), then the UE does not consider contention resolution to be unsuccessful.

[0329] In various embodiments, when the first timer expires, if Msg3 has not been retransmitted when the first timer is running (and / or after the first timer was last started / restarted), the UE considers contention resolution to be unsuccessful. Alternatively or additionally, when the first timer expires, if Msg3 has been retransmitted when the first timer is running (and / or after the first timer was last started / restarted), the UE does not consider contention resolution to be unsuccessful.

[0330] In various embodiments, when the first timer expires, if the first timer is not subsequently started (restarted) (e.g., due to Msg3 retransmission), the UE regards contention resolution as unsuccessful. Alternatively or additionally, when the first timer expires, if the first timer is subsequently started (restarted) (e.g., due to Msg3 retransmission), the UE does not regard contention resolution as unsuccessful.

[0331] When the first timer expires, if the first timer will not start (restart) after the timing offset (e.g., first timer expiration + timing offset), then the UE may regard contention resolution as unsuccessful. After the timing offset (e.g., first timer expiration + timing offset) after the first timer expires, the UE may regard contention resolution as unsuccessful. When the first timer expires, the UE may delay the timing offset as unsuccessful. Alternatively or additionally, when the first timer expires, if the first timer is started (restarted) during the timing offset after the first timer expires, then the UE may not regard contention resolution as unsuccessful.

[0332] In another example, when the first timer expires, if the first timer does not expire during the timing offset after the Msg3 transmission and / or retransmission, the UE regards the RA procedure as unsuccessfully completed. When the first timer expires, if the first timer expires during the timing offset after the Msg3 transmission and / or retransmission, the UE does not regard the RA procedure as unsuccessfully completed.

[0333] The first timer may be a contention resolution timer (e.g., ra-ContentionResolutionTimer). The first timer may be a timer for contention resolution in the RA procedure. The first timer may be started after Msg3 transmission and / or retransmission (e.g., at the time of Msg3 transmission / retransmission end+timing offset). The first timer may be started in symbol n+x. Symbol n is the first symbol after the end of Msg3 transmission and / or retransmission. x is the length of the timing offset. The timing offset after Msg3 transmission and / or retransmission may be the time when the second timer is in operation. The first timer and / or the second timer may be configured in the RA configuration and / or the NTN configuration.

[0334] For example, Fig.11 As shown in , the UE may transmit Msg3 using the UL grant received in Msg2 and / or MSGB (e.g., with fallbackRAR). The UE may start a second timer after the transmission of Msg3 (e.g., at the end of the transmission of Msg3). The UE may start a first timer after the expiration of the second timer (or in response to the expiration of the second timer). While the first timer is running, the UE may monitor the PDCCH addressed to the temporary C-RNTI (and may receive a DG for retransmission). The UE may retransmit Msg3 using the DG. The UE may start a second timer after the retransmission of Msg3 (e.g., at the end of the retransmission of Msg3). When the first timer expires, the UE checks whether the second timer is running. If the second timer is running, the UE may not regard contention resolution as unsuccessful. The UE may start the first timer after the expiration of the second timer. When the first timer is running, the UE may monitor the PDCCH addressed to the temporary C-RNTI (and may receive Msg4). After receiving Msg4, the UE may regard the RA procedure as completed successfully.

[0335] For example, the UE may transmit Msg3 using the UL grant received in Msg2 and / or MSGB (e.g., with fallbackRAR). The UE may start a second timer after the transmission of Msg3 (e.g., at the end of the transmission of Msg3). The UE may start a first timer after the expiration of the second timer (or in response to the expiration of the second timer). While the first timer is running, the UE may monitor the PDCCH addressed to the temporary C-RNTI. When the first timer expires, the UE checks whether the second timer is running. If the second timer is not running, the UE may consider the contention resolution as unsuccessful and fall back to retransmitting Msg1.

[0336] In view of and applying the above and aspects of the disclosure provided herein, Figure 12-Figure 17Various exemplary embodiments according to the present invention provide methods, acts, processes and / or steps.

[0337] refer to Fig.12 According to this and other concepts and methods of the present invention, the method 1000 of the UE includes: at step 1002, initiating an RA procedure; at step 1004, transmitting Msg3 in the RA procedure; at step 1006, starting a first timer with a first value at a first timing; at step 1008, when the first timer is running, receiving an UL grant for Msg3 retransmission on the PDCCH; at step 1010, retransmitting Msg3 using the UL grant; and at step 1012, restarting the first timer with a second value at a second timing.

[0338] In various embodiments, the second value is the first value plus a timing offset.

[0339] In various embodiments, the first timing is the first symbol after the end of Msg3 transmission plus a timing offset.

[0340] In various embodiments, the second timing is the first symbol after the Msg3 retransmission ends.

[0341] Return to reference Figure 3 and Figure 4 In one or more embodiments, the UE / device 300 includes a program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to perform the following operations: (i) initiate an RA procedure; (ii) transmit Msg3 in the RA procedure; (iii) start a first timer with a first value at a first timing; (iv) receive an UL grant for Msg3 retransmission on the PDCCH when the first timer is running; (v) retransmit Msg3 using the UL grant; and (vi) restart the first timer with a second value at a second timing. In addition, the CPU 308 can execute the program code 312 to perform all of the actions, steps, and methods described above, below, or otherwise herein.

[0342] refer to Fig.13 According to this and other concepts and methods of the present invention, the UE method 1020 includes: at step 1022, initiating an RA procedure; at step 1024, transmitting Msg3 in the RA procedure; at step 1026, starting a first timer at a first timing; at step 1028, receiving an UL grant for Msg3 retransmission on the PDCCH when the first timer is running; at step 1030, retransmitting Msg3 using the UL grant; and at step 1032, restarting the first timer at a second timing and a third timing.

[0343] In various embodiments, the first timing is the first symbol after the end of Msg3 transmission plus a timing offset.

[0344] In various embodiments, the second timing is the first symbol after expiration of the first timer.

[0345] In various embodiments, the second timing is the first symbol after the Msg3 retransmission ends.

[0346] In various embodiments, the third timing is the first symbol after the end of Msg3 retransmission plus the timing offset.

[0347] Return to reference Figure 3 and Figure 4 In one or more embodiments, the UE / device 300 includes a program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to perform the following operations: (i) initiate an RA procedure; (ii) transmit Msg3 in the RA procedure; (iii) start a first timer at a first timing; (iv) receive an UL grant for Msg3 retransmission on the PDCCH when the first timer is running; (v) retransmit Msg3 using the UL grant; and (vi) restart the first timer at a second timing and a third timing. In addition, the CPU 308 can execute the program code 312 to perform all of the actions, steps, and methods described above, below, or otherwise herein.

[0348] refer to Fig.14 According to this and other concepts and methods of the present invention, method 1040 of the UE includes: at step 1042, initiating an RA procedure; at step 1044, transmitting Msg3 in the RA procedure; at step 1046, starting a first timer at a first timing; at step 1048, receiving an UL grant for Msg3 retransmission on the PDCCH when the first timer is running; at step 1050, stopping the first timer at a fourth timing; and at step 1052, retransmitting Msg3 using the UL grant and starting the first timer at a third timing.

[0349] In various embodiments, the first timing is the first symbol after the end of Msg3 transmission plus a timing offset.

[0350] In various embodiments, the fourth timing is the first symbol after the end of UL grant reception.

[0351] In various embodiments, the third timing is the first symbol after the end of Msg3 retransmission plus the timing offset.

[0352] In various embodiments, while the first timer is running, the UE additionally monitors the PDCCH.

[0353] In various embodiments, the first timer is used for contention resolution.

[0354] In various embodiments, the first timer is a contention resolution timer (eg, ra-ContentionResolutionTimer).

[0355] In various embodiments, the RA procedure is a 2-step RA and / or a 4-step RA in NTN.

[0356] In various embodiments, the timing offset is the time delay (eg, RTT, RTD, TA) between the UE and the NW in the NTN.

[0357] In various embodiments, the timing offset is provided by the NW and / or calculated by the UE.

[0358] Return to reference Figure 3 and Figure 4 In one or more embodiments, the UE / device 300 includes a program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to perform the following operations: (i) initiate an RA procedure; (ii) transmit Msg3 in the RA procedure; (iii) start a first timer at a first timing; (iv) when the first timer is running, receive an UL grant for retransmission of Msg3 on the PDCCH; (v) stop the first timer at a fourth timing; (vi) retransmit Msg3 using the UL grant; and (vii) start the first timer at a third timing. In addition, the CPU 308 can execute the program code 312 to perform all of the actions, steps, and methods described above, below, or otherwise herein.

[0359] refer to Fig.15 According to this and other concepts and methods of the present invention, the UE method 1060 includes: at step 1062, initiating an RA procedure; at step 1064, transmitting Msg3 in the RA procedure; at step 1066, starting a first timer at a first timing; at step 1068, when the first timer is running, receiving an UL grant for retransmission of Msg3 on the PDCCH; at step 1070, retransmitting Msg3 using the UL grant; and at step 1072, starting the first timer at a fourth timing.

[0360] In various embodiments, the first timing is the first symbol after the end of Msg3 transmission plus a timing offset.

[0361] In various embodiments, the fourth timing is the first symbol after the end of Msg3 retransmission plus the timing offset.

[0362] In various embodiments, the first timer expires before the fourth timer.

[0363] In various embodiments, when the first timer expires, the UE does not consider the contention resolution as unsuccessful.

[0364] In various embodiments, while the first timer is running, the UE additionally monitors the PDCCH.

[0365] In various embodiments, the first timer is used for contention resolution.

[0366] In various embodiments, the first timer is a contention resolution timer (eg, ra-ContentionResolutionTimer).

[0367] In various embodiments, the RA procedure is a 2-step RA and / or a 4-step RA in NTN.

[0368] In various embodiments, the timing offset is the time delay (eg, RTT, RTD, TA) between the UE and the NW in the NTN.

[0369] In various embodiments, the timing offset is provided by the NW and / or calculated by the UE.

[0370] Return to reference Figure 3 and Figure 4 In one or more embodiments, the UE / device 300 includes a program code 312 stored in the memory 310. The CPU 308 may execute the program code 312 to perform the following operations: (i) initiate an RA procedure; (ii) transmit Msg3 in the RA procedure; (iii) start a first timer at a first timing; (iv) receive an UL grant for Msg3 retransmission on the PDCCH while the first timer is running; (v) retransmit Msg3 using the UL grant; and (vi) start the first timer at a fourth timing. In addition, the CPU 308 may execute the program code 312 to perform all of the actions, steps, and methods described above, below, or otherwise herein.

[0371] refer to Fig.16According to this and other concepts and methods of the present invention, the method 1080 of the UE includes: at step 1082, performing Msg3 transmission and starting an RA contention resolution timer; at step 1084, when the RA contention resolution timer is running, receiving an UL grant for Msg3 retransmission on the PDCCH; at step 1086, performing Msg3 retransmission using the UL grant; stopping the RA contention resolution timer in response to receiving the UL grant (at step 1088); if the Msg3 transmission is in NTN, then starting the RA contention resolution timer in the first symbol after the end of the Msg3 retransmission plus the timing offset (at step 1090); and at step 1092, if the Msg3 transmission is in TN, then restarting the RA contention resolution timer in the first symbol after the end of the Msg3 retransmission.

[0372] In various embodiments, if Msg3 is transmitted in NTN, then the RA contention resolution timer is started in the first symbol after the end of Msg3 transmission plus the timing offset.

[0373] In various embodiments, if Msg3 is transmitted in TN, the RA contention resolution timer is started in the first symbol after the end of Msg3 transmission.

[0374] In various embodiments, further comprising, in response to expiration of the RA contention resolution timer, deeming the contention resolution unsuccessful.

[0375] In various embodiments, the timing offset is the time delay between the UE and the network in the NTN.

[0376] In various embodiments, the time delay is a round trip time.

[0377] Return to reference Figure 3 and Figure 4In one or more embodiments, the UE / device 300 includes program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to perform the following operations: (i) perform Msg3 transmission and start the RA contention resolution timer; (ii) when the RA contention resolution timer is running, receive an UL grant for Msg3 retransmission on the PDCCH; (iii) perform Msg3 retransmission using the UL grant, (iv) in response to receiving the UL grant, stop the RA contention resolution timer, (v) if the Msg3 transmission is in the NTN, then start the RA contention resolution timer in the first symbol after the end of the Msg3 retransmission plus the timing offset; and (vi) if the Msg3 transmission is in the TN, then restart the RA contention resolution timer in the first symbol after the end of the Msg3 retransmission. In addition, the CPU 308 can execute the program code 312 to perform all of the actions, steps and methods described above, below or otherwise herein.

[0378] refer to Fig.17 According to this and other concepts and methods of the present invention, the method 1100 of the UE includes: at step 1102, performing Msg3 transmission during the RA procedure in the NTN; at step 1104, starting the RA contention resolution timer in the first symbol after the end of the Msg3 transmission plus the timing offset; and at step 1106, in response to the RA contention resolution timer expiring, determining whether to regard the contention resolution as unsuccessful based on at least whether the RA contention resolution timer expires during the duration of the timing offset after the Msg3 retransmission.

[0379] In various embodiments, the method further includes deeming contention resolution unsuccessful based at least on the RA contention resolution timer not expiring during the duration of the timing offset following the Msg3 retransmission.

[0380] In various embodiments, the UE does not consider contention resolution to be unsuccessful based at least on the RA contention resolution timer expiring during the duration of the timing offset following the Msg3 retransmission.

[0381] In various embodiments, the timing offset is the time delay between the UE and the network in the NTN.

[0382] In various embodiments, the time delay is a round trip time.

[0383] In various embodiments, the method further includes: receiving a UL grant for Msg3 retransmission on the PDCCH while the RA contention resolution timer is running; performing the Msg3 retransmission using the UL grant; and restarting or starting the RA contention resolution timer in the first symbol after the end of the Msg3 retransmission plus the timing offset.

[0384] Return to reference Figure 3 and Figure 4 In one or more embodiments, the UE / device 300 includes program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to perform the following operations: (i) perform Msg3 transmission during the RA procedure in the NTN; (ii) start the RA contention resolution timer in the first symbol after the end of the Msg3 transmission plus the timing offset; and (iii) in response to the RA contention resolution timer expiring, determine whether to consider the contention resolution as unsuccessful based on at least whether the RA contention resolution timer expires during the duration of the timing offset after the Msg3 retransmission. In addition, the CPU 308 can execute the program code 312 to perform all of the actions, steps and methods described above, below or otherwise herein.

[0385] refer to Fig.18 According to this and other concepts and methods of the present invention, the method 1110 of the UE includes: at step 1112, performing Msg3 transmission during the RA procedure in the NTN; at step 1114, starting the RA contention resolution timer in the first symbol after the end of the Msg3 transmission plus the timing offset; and at step 1116, if the random access contention resolution timer expires within the duration of the timing offset after the Msg3 retransmission, the contention resolution is not considered unsuccessful.

[0386] In various embodiments, the UE, in response to expiration of the random access contention resolution timer, does not consider contention resolution unsuccessful based at least on the random access contention resolution timer expiring during the duration of the timing offset after the Msg3 retransmission.

[0387] In various embodiments, the method further includes: if no uplink grant for retransmitting Msg3 is received while the random access contention resolution timer is running, responsive to expiration of the random access contention resolution timer, considering the contention resolution to be unsuccessful.

[0388] In various embodiments, the method further comprises: considering contention resolution unsuccessful in response to expiration of the random access contention resolution timer based at least on not receiving a physical downlink control channel indicating Msg3 retransmission while the random access contention resolution timer is running.

[0389] In various embodiments, the method further includes: if the UE performs Msg3 transmission in the terrestrial network, in response to expiration of the random access contention resolution timer, considering the contention resolution as unsuccessful.

[0390] In various embodiments, the method further includes: when the random access contention resolution timer is running, receiving an uplink grant for Msg3 retransmission on a physical downlink control channel, performing Msg3 retransmission using the uplink grant, and starting or restarting the random access contention resolution timer in the first symbol after the end of the Msg3 retransmission plus the timing offset.

[0391] In various embodiments, the timing offset is the time delay between the UE and the network in the non-terrestrial network.

[0392] In various embodiments, the time delay is a round trip time or a round trip delay.

[0393] In various embodiments, when the UE receives Msg4, the random access contention resolution timer is stopped.

[0394] In various embodiments, when the UE receives Msg4, the UE considers the contention resolution successful.

[0395] Return to reference Figure 3 and Figure 4 In one or more embodiments, the UE / device 300 includes program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to perform the following operations: (i) perform Msg3 transmission during the RA procedure in the NTN; (ii) start the RA contention resolution timer in the first symbol after the end of the Msg3 transmission plus the timing offset; and (iii) if the random access contention resolution timer expires within the duration of the timing offset after the Msg3 retransmission, then the contention resolution is not considered unsuccessful. In addition, the CPU 308 can execute the program code 312 to perform all of the actions, steps and methods described above, below or otherwise herein.

[0396] According to various embodiments of the present invention, when the first timer is running, the UE may monitor the PDCCH. When the second timer is running, the UE may not monitor the PDCCH. When both the first and second timers are running, the UE may not monitor the PDCCH. The UE may not monitor the PDCCH during the timing offset. When the first timer is running, the UE is in DRX action time, for example, 3GPP TS 38.321 V16.3.0, "NR, MAC Protocol Specification". When the second timer is running, the UE is not in DRX action time. When both the first and second timers are running, the UE is not in DRX action time.

[0397] The UE may be in a cell of the NTN. The UE may be connected to a cell of the NTN. The UE may be connected to LEO, GEO, MEO, HEO and / or HAPS.

[0398] The UE may receive a configuration related to the NTN and / or the RA. The configuration may include a first timer, a second timer, and / or a timing offset. The value / length of the first timer (e.g., used in the NTN) may be the same as the contention resolution timer (e.g., ra-ContentionResolutionTimer) used in the TN. The value / length of the first timer (e.g., used in the NTN) may be different from the contention resolution timer (e.g., ra-ContentionResolutionTimer) used in the TN.

[0399] UE may be referred to as UE, a MAC entity of UE, or an RRC entity of UE.

[0400] The UE may be a NR device, a NR-light device, a reduced capability device, a mobile phone or device, a wearable device, a sensor, or a fixed device.

[0401] A network can be a network node, base station, access point, eNB, gNB or gateway.

[0402] Any combination of the above concepts or teachings can be combined or formed into new embodiments. The disclosed details and embodiments can be used to solve at least (but not limited to) the problems mentioned above and herein.

[0403] It should be noted that any of the methods, alternatives, steps, examples and embodiments presented herein may be applied independently, individually and / or in combination with multiple methods, alternatives, steps, examples and embodiments.

[0404] Various aspects of the present disclosure have been described above. It should be clear that the teachings herein can be implemented in a wide variety of forms, and any specific structure, function, or both disclosed herein are only representative. Based on the teachings herein, it should be understood by those skilled in the art that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, by using other structures, functionality, or structures and functionality other than one or more aspects of the aspects set forth herein or different from one or more aspects of the aspects set forth herein, this device can be implemented or this method can be practiced. As an example of some of the above concepts, in some aspects, parallel channels can be established based on pulse repetition frequency. In some aspects, parallel channels can be established based on pulse position or offset. In some aspects, parallel channels can be established based on time hopping sequences. In some aspects, parallel channels can be established based on pulse repetition frequency, pulse position or offset, and time hopping sequences.

[0405] Those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0406] Those of ordinary skill in the art will further appreciate that the various illustrative logical blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the various aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two, which may be designed using source decoding or some other technique), and various forms of programs or design code with instructions (which may be referred to herein as "software" or "software modules" for convenience), or a combination of the two. To clearly illustrate this interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those of ordinary skill in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0407] In addition, the various illustrative logical blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented within or performed by an integrated circuit ("IC"), an access terminal, or an access point. An IC may include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute code or instructions residing within the IC, outside the IC, or both. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration.

[0408] It should be understood that any specific order or hierarchy of steps in any disclosed process is an example of an exemplary method. It should be understood that based on design preferences, the specific order or hierarchy of steps in a process can be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in an exemplary order, but are not meant to be limited to the specific order or hierarchy presented.

[0409] The steps of the method or algorithm described in conjunction with the various aspects disclosed herein can be implemented directly with hardware, with a software module executed by a processor, or with a combination of the two. Software modules (e.g., including executable instructions and related data) and other data may reside in a data memory, such as a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art. An example storage medium may be coupled to a machine such as a computer / processor (for convenience, the machine may be referred to as a "processor" in this article) so that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. An example storage medium may be integrated with the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user device. In an alternative, the processor and the storage medium may reside in a user device as discrete components. In addition, in some aspects, any suitable computer program product may include a computer-readable medium, and the computer-readable medium includes a code related to one or more aspects of the present disclosure. In some aspects, a computer program product may include packaging materials.

[0410] Although the present invention has been described in conjunction with various aspects and examples, it will be appreciated that the present invention is capable of further modifications. This application is intended to cover any changes, uses or adaptations of the present invention, which generally follow the principles of the present invention and include such deviations from the present disclosure, which are within the scope of known and customary practice in the technical field to which the present invention belongs.

Claims

1. A method for a user device, It is characterized in that include: Msg3 transmission is performed during the random access procedure in non-terrestrial networks; as well as Starting a random access contention resolution timer in the first symbol after the end of the Msg3 transmission plus the timing offset, If the random access contention resolution timer expires within the duration of the timing offset after Msg3 retransmission, contention resolution is not considered unsuccessful.

2. The method according to claim 1, It is characterized in that The user equipment, in response to expiration of the random access contention resolution timer, does not regard the contention resolution as unsuccessful based at least on the expiration of the random access contention resolution timer during the duration of the timing offset after the Msg3 retransmission.

3. The method according to claim 1, It is characterized in that Also includes: If no uplink grant for retransmitting Msg3 is received while the random access contention resolution timer is running, the contention resolution is regarded as unsuccessful in response to expiration of the random access contention resolution timer.

4. The method according to claim 1, It is characterized in that Also includes: The contention resolution is deemed unsuccessful in response to expiration of the random access contention resolution timer based at least on not receiving a physical downlink control channel indicating the Msg3 retransmission while the random access contention resolution timer is running.

5. The method according to claim 1, It is characterized in that Also includes: If the user equipment performs the Msg3 transmission in a terrestrial network, the contention resolution is regarded as unsuccessful in response to expiration of the random access contention resolution timer.

6. The method according to claim 1, It is characterized in that Also includes: receiving an uplink grant for the Msg3 retransmission on a physical downlink control channel while the random access contention resolution timer is running; performing the Msg3 retransmission using the uplink grant; as well as The random access contention resolution timer is started or restarted in the first symbol after the end of the Msg3 retransmission plus the timing offset.

7. The method according to claim 1, It is characterized in that The timing offset is a time delay between the user equipment and a network in the non-terrestrial network.

8. The method according to claim 7, It is characterized in that The time delay is the round trip time or round trip delay.

9. The method according to claim 1, It is characterized in that When the user equipment receives Msg4, it stops the random access contention resolution timer.

10. The method according to claim 9, It is characterized in that When the user equipment receives the Msg4, the user equipment regards the contention resolution as successful.

11. A user device, It is characterized in that include: Memory; as well as a processor operatively coupled to the memory, wherein the processor is configured to execute program code to: perform Msg3 transmission during a random access procedure in a non-terrestrial network; as well as Starting a random access contention resolution timer in the first symbol after the end of the Msg3 transmission plus the timing offset, If the random access contention resolution timer expires within the duration of the timing offset after Msg3 retransmission, contention resolution is not considered unsuccessful.

12. The user equipment according to claim 11, It is characterized in that The processor is further configured to execute the program code to: in response to expiration of the random access contention resolution timer, not consider the contention resolution as unsuccessful based at least on the random access contention resolution timer expiring during the duration of the timing offset after the Msg3 retransmission.

13. The user equipment according to claim 11, It is characterized in that The processor is further configured to execute the program code to: if no uplink grant for retransmitting Msg3 is received while the random access contention resolution timer is running, deem the contention resolution unsuccessful in response to expiration of the random access contention resolution timer.

14. The user equipment according to claim 11, It is characterized in that The processor is also configured to execute the program code to: deem the contention resolution unsuccessful in response to expiration of the random access contention resolution timer based at least on not receiving a physical downlink control channel indicating the Msg3 retransmission while the random access contention resolution timer is running.

15. The user equipment according to claim 11, It is characterized in that The processor is further configured to execute the program code to: if the user equipment performs the Msg3 transmission in a terrestrial network, in response to expiration of the random access contention resolution timer, regard the contention resolution as unsuccessful.

16. The user equipment according to claim 11, It is characterized in that The processor is further configured to execute the program code to: receiving an uplink grant for the Msg3 retransmission on a physical downlink control channel while the random access contention resolution timer is running; performing the Msg3 retransmission using the uplink grant; as well as The random access contention resolution timer is started or restarted in the first symbol after the end of the Msg3 retransmission plus the timing offset.

17. The user equipment according to claim 11, It is characterized in that The timing offset is a time delay between the user equipment and a network in the non-terrestrial network.

18. The user equipment according to claim 17, It is characterized in that The time delay is the round trip time or round trip delay.

19. The user equipment according to claim 11, It is characterized in that When the user equipment receives Msg4, it stops the random access contention resolution timer.

20. The user equipment according to claim 19, It is characterized in that When the user equipment receives the Msg4, the user equipment regards the contention resolution as successful.