Method and apparatus for handling random access in non-terrestrial network in communications

Abstract

Methods, systems, and devices are provided for handling random access in a non-terrestrial network in a wireless communication system, wherein the method of a user equipment comprises: initiating a random access procedure in a first cell; determining whether a second type of random access resource is available in response to initiating the random access procedure; and in response to determining that the global navigation satellite system state of the user equipment is disqualified during the random access procedure: selecting a second type of random access resource for the random access procedure if the second type of random access resource is available, or performing cell selection or reselection if the second type of random access resource is not available.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communication networks, and more particularly, to methods and apparatus for handling random access in a NTN in a wireless communication system. 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 that communicate using Internet Protocol (IP) packets. This IP packet communication can provide IP-bearing voice, multimedia, multicast and on-demand communication services for 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-bearing 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 enable the 3GPP standards to evolve and complete. Summary of the invention

[0004] A method, system and device for handling random access (RA) in a non-terrestrial network (NTN) in a wireless communication system are provided, so that a user equipment (UE) with global navigation satellite system (GNSS) capability can perform RA procedures and / or fallback actions under certain conditions, such as based on the validity of GNSS. The UE can handle inconsistent knowledge of GNSS capabilities between the UE and the network (NW). Coexistence between UEs with and without GNSS can be supported in the NTN. The UE can access a cell based on GNSS capabilities. Non-GNSS UEs can be supported resource-efficiently in the NTN. RA resource usage between GNSS UEs and non-GNSS UEs can be properly handled. The UE can maintain a timing advance (TA) value in the absence of GNSS operation. A UE without GNSS can know its location, obtain TA parameters (for example, ), maintaining its full TA value (e.g., T TA ), and / or performing UL transmission in the NTN.

[0005] A method, system and apparatus for handling random access in an NTN in a wireless communication system are provided, wherein the method of a UE includes: initiating an RA procedure in a first cell; determining whether a second type RA resource is available in response to initiating the RA procedure; and during the RA procedure, in response to determining that the GNSS status of the UE is unqualified: if the second type RA resource is available, selecting the second type RA resource for the RA procedure, or if the second type RA resource is not available, performing cell selection or reselection.

[0006] In various embodiments, a method of a UE includes: receiving a first type of RA resource and a second type of RA resource from a network; initiating an RA procedure; in response to initiating the RA procedure, selecting the first type of RA resource based on that the UE's GNSS status is qualified; determining during the RA procedure that the UE's GNSS status becomes unqualified; and in response to the determination that the UE's GNSS status becomes unqualified: stopping the RA procedure, initiating or re-initiating the RA procedure, and / or selecting or reselecting the second type of RA resource. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 The drawings show a wireless communication system according to an embodiment of the present invention.

[0008] 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.

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

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

[0011] Figure 5 This is a reproduction of Figure 16.14.2.1-1: Illustration of timing relationships (for collocated gNB and NTN Gateway) from 3GPP TS 38.300 V17.5.0 “NR, NR and NG-RAN overall description, Stage 2”.

[0012] Figure 6 It is from 3GPP TS 38.331V17.5.0, "NR, RRC protocol specification" Figure 5 .3.7.1-1: Reproduction of successful RRC connection re-establishment.

[0013] Figure 7 It is from 3GPP TS 38.331V17.5.0 Figure 5.3.7.1-2: RRC re-establishment falls back to the re-establishment of successful RRC establishment.

[0014] Figure 8 It is from 3GPP TS 38.211V17.5.0 "NR, physical channels and modulation" Figure 4 .3.1-1: Reproduction of uplink-downlink timing relationship.

[0015] Fig. 9 It is a flowchart of a method of a UE according to an embodiment of the present invention, the method comprising: receiving an RRC message including a first type of RA resource from a network, and in response to receiving the RRC message, determining to use the first type of RA resource based on not satisfying a first condition, and determining to perform a fallback action based on satisfying the first condition.

[0016] Fig.10 is a flowchart of a method for a UE according to an embodiment of the present invention, the method comprising: initiating an RA procedure in a first cell; determining whether a second type of RA resource is available in response to initiating the RA procedure; and during the RA procedure, in response to determining that the GNSS status of the UE is unqualified.

[0017] Fig.11 It is a flowchart of a method of a UE according to an embodiment of the present invention, the method comprising: receiving a first type RA resource and a second type RA resource from a network; initiating an RA procedure; in response to initiating the RA procedure, selecting the first type RA resource based on the qualified GNSS status of the UE; determining that the GNSS status of the UE becomes unqualified during the RA procedure; and in response to the determination that the GNSS status of the UE becomes unqualified: stopping the RA procedure, initiating or re-initiating the RA procedure, and / or selecting or reselecting the second type RA resource. DETAILED DESCRIPTION

[0018] 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 mainly described in the context of the 3GPP architecture reference model. However, it should be understood that with the help of the disclosed information, those skilled in the art can easily adapt and use and implement aspects of the present invention in the 3GPP2 network architecture as well as other network architectures.

[0019] 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) radio access, 3GPP Long Term Evolution Advanced (LTE-A) radio access, 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR), or some other modulation technology.

[0020] In particular, the exemplary wireless communication systems and devices described below may be designed to support one or more standards, such as those provided by a consortium named “3rd Generation Partnership Project”, referred to herein as 3GPP, including: [1] 3GPP TR 38.821 V16.1.0, “Solution for NR Support of Non-Terrestrial Networks (NTN)”; [2] 3GPP TS 38.300 V17.5.0, “NR, NR and NG-RAN Overall Description, Stage 2”; [3] 3GPP TS 38.321 V17.5.0, “NR, MAC Protocol Specification”; [4] 3GPP TS 38.331 V17.5.0, “NR, RRC Protocol Specification”; [5] R2-2306951, “Operational CR for R18 IoT NTN”; [6] R2-2306962, “TS for Rel-18 IoT-NTN”. [7] R2-2306954, "Operational CR - Introduction of IoT NTN enhancements"; [8] 3GPP TS 38.304 V17.5.0, "NR, UE procedures in idle mode and RRC inactive state"; [9] 3GPP TS 38.213 V17.5.0, "NR, Physical layer procedures for control";

[10] 3GPP TS 38.211 V17.5.0, "NR, Physical channels and modulation";

[11] 3GPP TS 38.305 V17.5.0, "NG-RAN, Stage 2 functional specification for UE positioning in NG-RAN"; and

[12] 3GPP TS 36.331 V17.5.0, "E-UTRA, RRC protocol specification". The standards and documents listed above are hereby expressly and completely incorporated herein by reference in their entirety.

[0021] Figure 1 1 shows a multiple access wireless communication system according to an embodiment of the present invention. An access network 100 (AN) includes multiple antenna groups, one including 104 and 106, another including 108 and 110, and another including 112 and 114. Figure 11, only two antennas are shown for each antenna group, however, 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.

[0022] Each antenna group and / or the area in which these antennas 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.

[0023] 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. Additionally, an access network transmitting to access terminals randomly dispersed throughout its coverage area using beamforming may cause less interference to access terminals in neighboring cells than if the access network transmitted to all of its access terminals via a single antenna.

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

[0025] 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.

[0026] In one embodiment, each data stream is transmitted through 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.

[0027] 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 are 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. Instructions executed by processor 230 may determine the data rate, coding, and modulation for each data stream. Memory 232 is coupled to processor 230.

[0028] 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.

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

[0030] 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.

[0031] RX data processor 260 then extracts the N R The receiver 254 receives and processes N R received 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 data processor 260 is complementary to the processing performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

[0032] 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.

[0033] The reverse link message may include various types of information about 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.

[0034] 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.

[0035] The memory 232 may be used to temporarily store some buffer / calculated data from 240 or 242 via 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 via the processor 270, store some buffer data from 236, or store some specific program codes.

[0036] Go to 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, 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 monitor or a speaker). The transceiver 314 is used to receive and transmit wireless signals, pass the received signal to the control circuit 306, and wirelessly output the signal generated by the control circuit 306.

[0037] 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 typically performs radio resource control. Layer 2 portion 404 typically performs link control. Layer 1 portion 406 typically performs physical connectivity.

[0038] 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.

[0039] 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.

[0040] Any sentence, paragraph, (sub) bullet, key point, action or claim described in each of the following invention paragraphs or sections can be implemented independently and individually to form a specific method or device. The following disclosure of the present invention, such as "based on", "more specifically", "example", etc., is only a possible embodiment that does not limit a specific method or device.

[0041] The general description of NR non-terrestrial networks (NTN) in 3GPP Release 17 is specified in TS 38.300 ([2] 3GPP TS 38.300 V17.5.0, “NR, NR and NG-RAN general description, Stage 2”) as follows:

[0042] ***************** Quote starts [2]****************

[0043] 16.14 Non-terrestrial Networks

[0044] 16.14.1 Overview

[0045] …

[0046] Three types of service links are supported:

[0047] - Geofixed: provided by a beam that constantly covers the same geographical area (e.g. the case of GSO satellites);

[0048] - Quasi-geo-fixed: provided by a beam covering one geographical area during a limited period and a different geographical area during another period (e.g. the case of NGSO satellites producing steerable beams);

[0049] - Geomobile: provided by a beam whose coverage area slides over the surface of the Earth (e.g. the case of NGSO satellites producing fixed or non-steerable beams).

[0050] For NGSO satellites, gNBs can provide quasi-geofixed service links or geomobile service links, while gNBs operating with GSO satellites can provide geofixed service links.

[0051] In this release, UEs supporting NTN have GNSS functionality.

[0052] 16.14.2 Timing and Synchronization

[0053] 16.14.2.1 Scheduling and Timing

[0054] DL and UL are aligned at the uplink timing synchronization reference point (RP) with N TA，偏移 Given offset (see clause 4.2 of TS 38.213).

[0055] In order to accommodate the propagation delay in NTN, the Common Timing Advance (CommonTA) and two offsets K 偏移 and k mac To enforce several timing relationships:

[0056] - Common TA is the configured timing offset equal to the RTT between RP and NTN payload.

[0057] -K 偏移 is the configured scheduling offset that needs to be greater than or equal to the sum of the serving link RTT and the common TA.

[0058] -k mac is the configured offset which is approximately equal to the RTT between the RP and the gNB.

[0059] Scheduling offset K 偏移 To allow the UE sufficient processing time between downlink reception and uplink transmission, see TS 38.213.

[0060] Offset k mac Used to delay the application of the downlink configuration indicated by the MAC CE command on PDSCH (see TS 38.213) and in the estimation of UE-gNB RTT (see TS 38.321). It can be provided by the network when the downlink and uplink frame timing are not aligned at the gNB. mac It is also used in the random access procedure to determine the start time of the RAR window / MsgB window after the transmission of Msg1 / MsgA (see TS 38.213).

[0061] Service link RTT, feeder link RTT, RP, common TA, k mac and T TA (See Clause 16.14.2.2) shown in Figure 16.14.2.1-1.

[0062] Figure 5 This is a reproduction of Figure 16.14.2.1-1: Illustration of timing relationships (for collocated gNB and NTN Gateway) from 3GPP TS 38.300 V17.5.0 “NR, NR and NG-RAN overall description, Stage 2”.

[0063] …

[0064] 16.14.2.2 Timing Advance and Frequency Precompensation

[0065] For the serving cell, the network broadcasts valid ephemeris information and common TA parameters. The UE shall have a valid GNSS position as well as ephemeris and common TA before connecting to the NTN cell. To achieve synchronization, before and during connection to the NTN cell, the UE shall calculate the RTT between the UE and the RP based on the GNSS position, ephemeris and common TA parameters (see clause 4.2 in TS 38.213), and autonomously pre-compensate T for the RTT between the UE and the RP as shown in Figure 16.14.2.1-1. TA(See clause 4.3 of TS 38.211).

[0066] The UE shall calculate the Doppler shift of the serving link by taking into account the UE position and ephemeris and autonomously pre-compensate for it in uplink transmissions.If the UE does not have a valid GNSS position and / or valid ephemeris and a common TA, the UE shall not transmit until both are reacquired.

[0067] In connected mode, the UE should be able to continuously update the timing advance and frequency pre-compensation.

[0068] The UE may be configured to report the timing advance during the random access procedure or in connected mode. In connected mode, event-triggered reporting of the timing advance is supported.

[0069] ****************END OF QUOTE*****************

[0070] In NTN, the NW may provide NTN information and / or NTN configuration to the UE as specified in TS 38.331 ([4] 3GPP TS 38.331 V17.5.0, “NR, RRC Protocol Specification”):

[0071] ***************** Quote starts [4]****************

[0072] -NTN-ConfigIENTN-Config provides the parameters required by the UE to access NR via NTN access. NTN-Config information element

[0073]

[0074]

[0075]

[0076]

[0077]

[0078] ****************END OF QUOTE*****************

[0079] In Release 18 IoT NTN, if the GNSS position is invalid, the UE does not initiate an RRC connection. Enhancements to GNSS operations are introduced for IoT NTN, as described in the Operation CR of TS 36.300 ([5] R2-2306951, "Operation CR for R18 IoT NTN"), the Operation CR of TS 36.321 ([6] R2-2306962, "Stage 3 Operation CR of TS 36.321 for Rel-18 IoT-NTN") and the Operation CR of TS 36.331 ([7] R2-2306954, "Introduction of Operation CR-IoT NTN enhancements"):

[0080] ***************** Quote starts [5]****************

[0081] 23.21.2.2 Timing Advance and Frequency Precompensation

[0082] …

[0083] In connected mode, the UE shall continuously update timing advance and frequency pre-compensation, and the UE may be configured to perform GNSS acquisition. RLM is suspended while the UE performs GNSS acquisition. In connected mode, the UE shall acquire the broadcasted parameters in view of outdated ephemeris and common timing advance, and in view of outdated GNSS position, the UE shall move to idle mode. After completing GNSS acquisition, the UE shall trigger a remaining validity duration report.

[0084] Editor's Note: AS operations other than RLM SHOULD be suspended and MAY be logged in Phase 2 unless adequately logged in Phase 3 (MAC and / or RRC).

[0085] ****************END OF QUOTE*****************

[0086] ***************** Quote starts [6]****************

[0087] 5.xx GNSS measurement

[0088] The network may request a NB-IoT UE, BL UE or UE in enhanced coverage in a non-terrestrial network to perform GNSS measurements by sending a GNSS Measurement Command MAC CE described in clause 6.1.3.xx.

[0089] The MAC entity will:

[0090] - If the MAC entity receives a GNSS measurement command MAC CE on the serving cell:

[0091] - Indicates to upper layers that the UE is required to perform GNSS measurements.

[0092] Editor's note: When the UE performs GNSS measurements during GNSS measurement gaps, some AS operations (e.g., DataInactivityTimer, Random Access, SR, BSR) are suspended.

[0093] 5.yy Remaining GNSS measurement validity duration report

[0094] The MAC entity of an NB-IoT UE, BL UE or UE in enhanced coverage in a non-terrestrial network may be triggered by upper layers to report the remaining GNSS measurement validity duration after completing the GNSS measurement.

[0095] If the remaining GNSS measurement validity duration reporting procedure has been triggered:

[0096] - If the MAC entity has UL resources allocated for new transmissions for this TTI, and;

[0097] - If due to logical channel prioritization, the allocated UL resources can accommodate the remaining GNSS Validity Duration Report MAC control element plus its subheaders:

[0098] - Instructs the Multiplexing and Assembly procedure to generate the Remaining GNSS Validity Duration Report MAC control element as defined in clause 6.1.3.yy.

[0099] ****************END OF QUOTE*****************

[0100] ***************** Quote starts [7]****************

[0101] 5.3.3.4UE receives RRCConnectionSetup

[0102] …

[0103] 1> Set the content of the RRCConnectionSetupComplete message as follows:

[0104] …

[0105] 2> If the UE is connected to NTN:

[0106] 3>Contains gnss-validityDuration according to the remaining time of GNSS validity duration;

[0107] 3>Contains gnss-PositionFixDuration according to the duration required for UE to obtain GNSS position;

[0108] ****************Next Quote*****************

[0109] 5.3.3.21 UE actions following indication of stale GNSS position

[0110] Following an indication that the GNSS position has become out-of-date while in RRC_CONNECTED, the UE shall:

[0111] 1> If the UE does not support GNSS positioning in GNSS measurement gaps:

[0112] 2> Perform actions immediately after leaving RRC_CONNECTED as specified in 5.3.12, where the release reason is 'other'.

[0113] Editor's Note: Protocol: If the UE enters a GNSS measurement gap, the UE may remain in the RRC_CONNECTED state when the current GNSS position becomes stale.

[0114] ****************Next Quote*****************

[0115] 5.3.7.5 UE receives RRCConnectionReestablishment

[0116] …

[0117] 1>Except for NB-IoT UEs where AS security has not been activated:

[0118] …

[0119] 2> If the UE is connected to NTN:

[0120] 3>Contains gnss-validityDuration according to the remaining time of GNSS validity duration;

[0121] 3>Contains gnss-PositionFixDuration according to the duration required for UE to obtain GNSS position;

[0122] …

[0123] 1> For NB-IoT UEs where AS security has not been activated:

[0124] …

[0125] 2> If the UE is connected to NTN:

[0126] 3>Contains gnss-validityDuration according to the remaining time of GNSS validity duration;

[0127] ****************END OF QUOTE*****************

[0128] The description related to the enhancements for GNSS standalone (or GNSS-free, non-GNSS) operation is specified in TR 38.821 ([1] 3GPP TR 38.821 V16.1.0, “Solutions for NR support of non-terrestrial networks (NTN)”) as follows:

[0129] ***************** Quote starts [1]****************

[0130] 6.3.3 Random Access

[0131] Based on the simulation assumptions in Table 6.1.2-2, the performance of the Rel-15 PRACH design is verified in several typical scenarios for NTN as listed in Table 6.1.2-3.

[0132] …

[0133] However, in case the UE side does not perform pre-compensation of timing and frequency offset for UL transmission, the enhanced PRACH format and / or preamble sequence shall be supported by the following options:

[0134] - Option-1: Single Zadoff-Chu sequence based on larger SCS, repeat number, additional usage of CP and Ncs may be further determined in normative work.

[0135] • Option-2: Solution based on multiple Zadoff-Chu sequences with different roots.

[0136] • Option-3: Gold / m-sequence as preamble sequence with additional processes, e.g., modulation and transform precoding.

[0137] • Option-4: Single Zadoff-Chu sequence with combination of scrambling sequences.

[0138] ****************Next Quote*****************

[0139] 7.2.1.1.4 Coexistence with different random access capabilities

[0140] Problem Statement

[0141] If there are both GNSS capable and non-GNSS capable UEs and assuming that the random access schemes for these UEs may be different, it should be possible for the network to separate resources and control access to the network under the condition that the random access procedures and resources may look very different.

[0142] Possible solutions

[0143] One possible solution is for the network to be able to configure separate resources and differentiate these resources based on GNSS capabilities.

[0144] ****************END OF QUOTE*****************

[0145] In addition, the RA configuration is specified in TS 38.331 ([4] 3GPP TS 38.331 V17.5.0, “NR, RRC Protocol Specification”) as follows:

[0146] ***************** Quote starts [4]****************

[0147] -BWP-UplinkCommon

[0148] IE BWP-UplinkCommon is used to configure the common parameters of the uplink BWP. It is "cell-specific" and the network ensures the necessary alignment with the corresponding parameters of other UEs. The common parameters of the initial bandwidth part of the PCell are also provided via system information. For all other serving cells, the network provides common parameters via dedicated signaling.

[0149] BWP-UplinkCommon Information Element

[0150]

[0151]

[0152]

[0153]

[0154] ****************Next Quote*****************

[0155] -CellGroupConfig

[0156] CellGroupConfig IE is used to configure the master cell group (MCG) or secondary cell group (SCG). …

[0157] CellGroupConfig Information Element

[0158]

[0159]

[0160]

[0161] ****************Next Quote*****************

[0162] -MsgA-ConfigCommon

[0163] The IE MsgA-ConfigCommon is used to configure PRACH and PUSCH resources for transmission of MsgA in a 2-step random access type procedure.

[0164] MsgA-ConfigCommon Information Element

[0165]

[0166]

[0167]

[0168] ****************Next Quote*****************

[0169] -RACH-ConfigCommonIERACH-ConfigCommon is used to specify cell-specific random access parameters.

[0170]

[0171]

[0172]

[0173]

[0174]

[0175] …

[0176] -RACH-ConfigCommonTwoStepRAIERACH-ConfigCommonTwoStepRA is used to specify the cell-specific 2-step random access type parameters.

[0177] RACH-ConfigCommonTwoStepRA Information Element

[0178]

[0179]

[0180]

[0181]

[0182]

[0183]

[0184] …

[0185] -RACH-ConfigDedicatedIERACH-ConfigDedicated is used to specify dedicated random access parameters. RACH-ConfigDedicated information element

[0186]

[0187]

[0188]

[0189]

[0190]

[0191]

[0192]

[0193]

[0194]

[0195]

[0196] …

[0197] -RACH-ConfigGeneric

[0198] IERACH-ConfigGeneric is used to specify random access parameters both for regular random access and for beam failure recovery.

[0199] RACH-ConfigGeneric Information Element

[0200]

[0201]

[0202]

[0203]

[0204] -RACH-ConfigGenericTwoStepRAIERACH-ConfigGenericTwoStepRA is used to specify the 2-step random access type parameters. RACH-ConfigGenericTwoStepRA information element

[0205]

[0206]

[0207]

[0208]

[0209]

[0210] *****************END OF QUOTE****************

[0211] The cell selection and reselection procedures are specified in TS 38.304 ([8] 3GPP TS 38.304 V17.5.0, "NR, UE procedures in idle mode and RRC inactive state"):

[0212] ***************** Quote starts [8]****************

[0213] 5.3.1 Cell Status and Cell Reservation

[0214] The cell status and cell reservation are indicated in the MIB or SIB1 message as specified in TS 38.331 by means of the following fields:

[0215] -cellBarred (IE type: "barred" or "not barred")

[0216] Indicated in MIB messages. In case of multiple PLMNs or NPNs indicated in SIB1, this field is common to all PLMNs and NPNs. When cellBarredNTN is included in SIB1, UEs supporting NTN ignore this field.

[0217] -cellBarredNTN (IE type: "barred" or "not barred")

[0218] Indicated in SIB1 message. In case of multiple PLMNs indicated in SIB1, this field is common for all PLMNs. If the UE does not support NTN connectivity, this field is ignored.

[0219] -cellBarredRedCap1Rx (IE type: "prohibit" or "don't prohibit")

[0220] Indicated in SIB1 message. In case of multiple PLMNs or NPNs indicated in SIB1, this field is common to all PLMNs and NPNs. This field is applicable only to RedCap UEs.

[0221] -cellBarredRedCap2Rx (IE type: "barred" or "not barred")

[0222] Indicated in SIB1 message. In case of multiple PLMNs or NPNs indicated in SIB1, this field is common to all PLMNs and NPNs. This field is applicable only to RedCap UEs.

[0223] -cellReservedForOperatorUse (IE type: "reserved" or "not reserved")

[0224] Indicated in the SIB1 message. In case of multiple PLMNs or NPNs indicated in SIB1, this field is specified per PLMN or per SNPN.

[0225] -cellReservedForOtherUse (IE type: "true")

[0226] Indicated in SIB1 message. In case of multiple PLMNs indicated in SIB1, this field is common to all PLMNs.

[0227] -cellReservedForFutureUse (IE type: "true")

[0228] Indicated in SIB1 message. In case of multiple PLMNs or NPNs indicated in SIB1, this field is common to all PLMNs and NPNs.

[0229] …

[0230] -halfDuplexRedCapAllowed (IE type: "true")

[0231] Indicated in SIB1 message. In case of multiple PLMNs or NPNs indicated in SIB1, this field is common to all PLMNs and NPNs. This field is applicable only to RedCap UEs.

[0232] -iab-Support(IE type: "true")

[0233] Indicated in the SIB1 message. In case of multiple PLMNs or NPNs indicated in SIB1, this field is specified per PLMN or per SNPN.

[0234] When the cell status is indicated as "not prohibited" and "not reserved" for operator use and not "true" for other uses and not "true" for future use,

[0235] - The UE shall consider this cell as a candidate during cell selection and cell reselection procedures.

[0236] ...when cellBarredNTN is not broadcast in this cell,

[0237] - For NTN access, the UE shall treat this cell as if the cell status is "barred".

[0238] When halfDuplexRedCapAllowed is not broadcast in this cell,

[0239] - RedCap UEs capable of operating only in half-duplex in FDD shall treat this cell as if the cell status is "barred".

[0240] When the cell status is indicated as "not prohibited" and "reserved" for operator use of any PLMN / SNPN and not "true" for other uses and not "true" for future uses,

[0241] - A UE assigned to access identity 11 or 15 operating in its HPLMN / EHPLMN shall consider this cell as a candidate during cell selection and reselection procedures if the field cellReservedForOperatorUse for that PLMN is set to "reserved".

[0242] - A UE assigned to access identity 11 or 15 shall consider this cell as a candidate during cell selection and reselection procedures if the field cellReservedForOperatorUse for the selected / registered SNPN is set to "reserved".

[0243] - In case the cell is "reserved for operator use" for the registered PLMN / SNPN or selected PLMN / SNPN, UEs assigned to access identities 0, 1, 2 and 12 to 14 shall behave as if the cell status is "barred".

[0244] - In case the cell is "reserved for operator use" for the registered PLMN or selected PLMN, a UE assigned to Access Identity 3 shall behave as if the cell status is "barred".

[0245] …

[0246] When indicating a cell status of "barred" or treated as if the cell status is "barred",

[0247] - The UE is not allowed to select / reselect this cell, even for emergency calls.

[0248] - The UE shall select another cell according to the following rules:

[0249] - If the cell is treated as if the cell status is "barred" due to failure to obtain the MIB:

[0250] - The UE may exclude barred cells as candidates for cell selection / reselection for up to 300 seconds.

[0251] - If the selection criteria are met, the UE may select another cell on the same frequency.

[0252] -otherwise:

[0253] …

[0254] - If the UE is not a RedCap UE, or if the UE is a RedCap UE and intraFreqReselectionRedCap is available in SIB1:

[0255] - If the field intraFreqReselection in the MIB message is set to "allow":

[0256] - If the reselection criteria are met, the UE may select another cell on the same frequency;

[0257] - If the cell is treated as if the cell status is "barred" due to failure to acquire SIB1:

[0258] - The UE may exclude the barred cell as a candidate for cell selection / reselection for up to 300 seconds;

[0259] -otherwise:

[0260] - The UE shall exclude barred cells as candidates for cell selection / reselection for 300 seconds.

[0261] - If the field intraFreqReselection in the MIB message is set to "Not Allowed":

[0262] - If the cell is treated as if the cell status is "barred" due to failure to acquire SIB1:

[0263] - The UE may exclude the barred cell as a candidate for cell selection / reselection for up to 300 seconds;

[0264] - If the cell operates in licensed spectrum:

[0265] - The UE shall not reselect to another cell on the same frequency as the barred cell and exclude such cells as candidates for cell selection / reselection for 300 seconds;

[0266] -otherwise:

[0267] - If the reselection criteria are met, the UE may select to another cell on the same frequency.

[0268] -otherwise:

[0269] - If the cell operates in licensed spectrum, or if this cell belongs to a PLMN indicated as equivalent to the UE's registered PLMN or selected PLMN, or if this cell belongs to the UE's registered SNPN or selected SNPN:

[0270] - The UE shall not reselect to another cell on the same frequency as the barred cell and exclude such cells as candidates for cell selection / reselection for 300 seconds;

[0271] -otherwise:

[0272] - If the reselection criteria are met, the UE may select to another cell on the same frequency.

[0273] - The UE shall exclude barred cells as candidates for cell selection / reselection for 300 seconds.

[0274] The cell selection of another cell may also include a change of RAT.

[0275] ****************END OF QUOTE*****************

[0276] Some procedures for RRC connection control (e.g., reconfiguration with synchronization, reestablishment) are specified in TS 38.331 ([4] 3GPP TS 38.331 V17.5.0, “NR, RRC Protocol Specification”) as follows:

[0277] ***************** Quote starts [4]****************

[0278] 5.3.5.8.3 T304 expires (reconfiguration due to synchronization failure) or T420 expires (path switching failure)

[0279] The UE shall:

[0280] 1> If the T304 of MCG expires; or

[0281] 1> If the T420 expires; or

[0282] 1> If the target L2 U2N relay UE (i.e. the UE indicated by targetRelayUE-Identity in the received RRCReconfiguration message containing reconfigurationWithSync indicating a path switch as specified in 5.3.5.5.2) changes its serving PCell before the path switch:

[0283] 2> Release the dedicated preamble provided in rach-ConfigDedicated (if configured);

[0284] 2> Release the dedicated msgA PUSCH resources provided in rach-ConfigDedicated (if configured);

[0285] …

[0286] 3> Restore back to the UE configuration used in the source PCell;

[0287] 3> If the associated T304 is not initialized after performing cell selection while timer T311 is running, as defined in clause 5.3.7.3:

[0288] 4>Store the handover failure information in VarRLF-Report as described in clause 5.3.10.5;

[0289] 3> Initiate connection re-establishment procedures as specified in clause 5.3.7.

[0290] NOTE 1: In the above context, "UE configuration" includes state variables and parameters for each radio bearer.

[0291] …

[0292] 1> Otherwise, if T304 expires when RRCReconfiguration is received via other RAT (handover to NR fails):

[0293] 2>Reset MAC;

[0294] 2> Perform the actions defined for this failure condition as defined in the specification applicable to the other RAT.

[0295] NOTE 2: In this clause, the term 'handover failure' has been used to refer to 'reconfiguration with synchronization failure'.

[0296] ****************Next Quote*****************

[0297] 5.3.7RRC Connection Reestablishment

[0298] 5.3.7.1 General

[0299] Figure 6 It is from 3GPP TS 38.331V17.5.0, "NR, RRC protocol specification" Figure 5 .3.7.1-1: Reproduction of successful RRC connection re-establishment.

[0300] Figure 7 It is from 3GPP TS 38.331V17.5.0 Figure 5 .3.7.1-2: RRC re-establishment falls back to the re-establishment of successful RRC establishment.

[0301] The purpose of this procedure is to re-establish the RRC connection. A UE in RRC_CONNECTED for which AS security has been activated in case of SRB2 and at least one DRB / Multicast MRB setup or for which the IAB is SRB2 may initiate the procedure in order to continue the RRC connection. The connection re-establishment is successful if the network is able to find and verify a valid UE context, or if the UE context cannot be retrieved and the network responds with RRCSetup according to clause 5.3.3.4.

[0302] For example, the network uses the following program:

[0303] - When AS security is activated and the network retrieves or verifies the UE context:

[0304] - Reactivate AS security without changing the algorithm;

[0305] - Re-establish and restore SRB1;

[0306] - When the UE is re-establishing an RRC connection and the network is unable to retrieve or verify the UE context:

[0307] - discard the stored AS context and release all RBs as well as BH RLC channels and Uu relay RLC channels;

[0308] - Fall back to establish a new RRC connection.

[0309] ****************Next Quote*****************

[0310] 5.3.10.3 Detection of radio link failure

[0311] The UE shall:

[0312] …

[0313] 2>When T310 in PCell expires; or

[0314] 2>When T312 in PCell expires; or

[0315] 2> upon a Random Access Problem indication from the MCG MAC while none of T300, T301, T304, T311 or T319 is running and the SDT procedure is not in progress; or

[0316] 2> upon an indication from the MCG RLC that the maximum number of retransmissions has been reached while the SDT procedure is not in progress; or

[0317] …

[0318] 2> On consistent uplink LBT failure indication from MCG MAC while T304 is not in operation:

[0319] …

[0320] 4> Consider that a radio link failure will be detected for MCG, i.e., MCG RLF;

[0321] 4> discard any fragments of the segmented RRC message stored according to 5.7.6.3;

[0322] 4> If AS security has not been activated:

[0323] 5> Perform actions after transitioning to RRC_IDLE as specified in 5.3.11, where the release reason is 'other'; -

[0324] 4> Else if AS security is activated but SRB2 and at least one DRB or multicast MRB or SRB2 for IAB are not set up:

[0325] 5>Store the radio link failure information in VarRLF-Report as described in clause 5.3.10.5;

[0326] 5> Perform actions after transitioning to RRC_IDLE as specified in 5.3.11, where the release reason is 'RRC connection failure';

[0327] 4> Otherwise:

[0328] 5>Store the radio link failure information in VarRLF-Report as described in clause 5.3.10.5;

[0329] 5> If T316 is configured; and

[0330] 5> If SCG transmission is not paused; and

[0331] 5> If SCG has not deactivated; and

[0332] 5> If neither PSCell change nor PSCell addition is in progress (i.e., timer T304 of the NR PSCell is not running in case of NR-DC, or timer T307 of the E-UTRA PSCell is not running in NE-DC, as specified in TS 36.331 clause 5.3.10.10):

[0333] 6> Initiate MCG Failure Information procedure as specified in 5.7.3b to report MCG radio link failure.

[0334] 5> Otherwise:

[0335] 6> Initiate the connection re-establishment procedure as specified in 5.3.7.

[0336] ****************Next Quote*****************

[0337] 5.3.11 UE actions after transitioning to RRC_IDLE

[0338] The UE shall:

[0339] 1>Reset MAC;

[0340] …

[0341] 1> If the transition to RRC_IDLE is triggered by receiving a RRCRelease message containing waitTime:

[0342] 2> If T302 is running:

[0343] 3> Stop timer T302;

[0344] 2>Start timer T302, where the value is set to waitTime;

[0345] 2> Notify upper layers that access barring is applicable for all access categories except categories '0' and '2'.

[0346] 1> Otherwise:

[0347] 2> If T302 is running:

[0348] 3> Stop timer T302;

[0349] 3> Perform actions as specified in 5.3.14.4;

[0350] 1> If the T390 is in operation:

[0351] 2> For all access categories, stop timer T390;

[0352] 2> Perform actions as specified in 5.3.14.4;

[0353] 1> If the UE leaves RRC_INACTIVE:

[0354] 2> If it is not triggered by receiving the RRCRelease message to go to RRC_IDLE:

[0355] 3> If it has been stored, discard the cell reselection priority information provided by cellReselectionPriorities;

[0356] 3> If it is running, stop timer T320;

[0357] 2> If T319a is in operation:

[0358] 3> Stop timer T319a;

[0359] 3> Consider that the SDT procedure is not in progress;

[0360] 1> Stop all running timers, except T302, T320, T325, T330, T331, T400 and T430;

[0361] 1>Discard the UE inactive AS context (if any);

[0362] 1> Release suspendConfig (if configured);

[0363] 1>Remove all entries in MCG and SCG VarConditionalReconfig (if they exist);

[0364] 1>For each measId, if the associated reportConfig has reportType set to condTriggerConfig, then:

[0365] 2>For the associated reportConfigId:

[0366] 3> Remove the entry with matching reportConfigId from reportConfigList in VarMeasConfig;

[0367] 2> If the associated measObjectId is associated only with a reportConfig with reportType set to condTriggerConfig, then:

[0368] 3> Remove the entry with matching measObjectId from measObjectList in VarMeasConfig;

[0369] 2> Remove the entry with matching measId from measIdList in VarMeasConfig;

[0370] 1>Discard K gNB Key, SK gNB Key, SK eNB Key, K RRCenc Key, K RRCint Key, K UPint Key and K UPenc The key (if it exists);

[0371] 1> Release all radio resources, including RLC entities, BAP entities, MAC configurations and associated PDCP entities and SDAPs for all established RBs (except broadcast MRBs), BH RLC channels, Uu relay RLC channels, PC5 relay RLC channels and SRAP entities;

[0372] 1> Indicate the release of the RRC connection to the upper layer together with the release cause;

[0373] 1> Notify the upper layer of the release of all application layer measurement configurations;

[0374] 1> discard any application layer measurement reports that have not been submitted to the lower layers for transmission;

[0375] 1> discard any fragments of the segmented RRC message stored according to 5.7.6.3;

[0376] 1> Except for going to RRC_IDLE triggered by inter-RAT cell reselection when the UE is in RRC_INACTIVE or RRC_IDLE or when an inter-RAT cell is selected while T311 is running or when an E-UTRA cell is selected for EPS fallback for IMS voice as specified in 5.4.3.5:

[0377] …

[0378] 3> Enter RRC_IDLE and perform cell selection as specified in TS 38.304;

[0379] ****************END OF QUOTE*****************

[0380] The RA procedure including power control is specified in TS 38.321 ([3] 3GPP TS 38.321 V17.5.0 “NR MAC Protocol Specification”) as follows:

[0381] ***************** Quote starts [3]****************

[0382] 5.1.1 Random Access Procedure Initialization

[0383] The random access procedure described in this clause is initiated by a PDCCH command, by the MAC entity itself or by RRC for events according to TS 38.300. In the MAC entity, at any point in time, there is only one ongoing random access procedure. The random access procedure on the SCell shall only be initiated by a PDCCH command where the ra-PreambleIndex is different from 0b000000.

[0384] …

[0385] When initiating a random access procedure, the UE selects a set of random access resources as specified in clause 5.1.1b and initializes the following parameters for the random access procedure according to the values ​​configured by the RRC for the selected set of random access resources:

[0386] -prach-ConfigurationIndex: A set of PRACH opportunities that can be used for random access preamble transmission of Msg1. If PRACH opportunities are shared between 2-step and 4-step RA types, then these also apply to MSGA PRACH;

[0387] …

[0388] -msgA-PRACH-ConfigurationIndex: A set of available PRACH opportunities for transmitting the random access preamble of MSGA in a 2-step RA type.

[0389] -preambleReceivedTargetPower: initial random access preamble power for 4-step RA type;

[0390] -msgA-PreambleReceivedTargetPower: initial random access preamble power for 2-step RA type;

[0391] -rsrp-ThresholdSSB: RSRP threshold used to select SSB for 4-step RA type. If the random access procedure is initiated for beam failure recovery, the rsrp-ThresholdSSB used to select SSB in candidateBeamRSList refers to the rsrp-ThresholdSSB in BeamFailureRecoveryConfig IE;

[0392] -rsrp-ThresholdCSI-RS: RSRP threshold used to select CSI-RS for RA type order 4. If the random access procedure is initiated for beam failure recovery, rsrp-ThresholdCSI-RS is equal to rsrp-ThresholdSSB in the BeamFailureRecoveryConfig IE;

[0393] -msgA-RSRP-ThresholdSSB: RSRP threshold used to select SSB for 2-step RA type.

[0394] -rsrp-ThresholdSSB-SUL: RSRP threshold for selecting between NUL carrier and SUL carrier;

[0395] -msgA-RSRP-Threshold: RSRP threshold used to select between 2-step RA type and 4-step RA type when both 2-step and 4-step RA type random access resources are configured in the UL BWP;

[0396] -rsrp-ThresholdMsg3: RSRP threshold for Msg3 repetition (see clause 5.1.1b);

[0397] -FeatureCombination: a feature or feature combination associated with a set of random access resources;

[0398] …

[0399] - candidateBeamRSList: a list of reference signals (CSI-RS and / or SSB) identifying candidate beams and associated random access parameters for recovery;

[0400] -recoverySearchSpaceId: Search space identity used to monitor responses to beam failure recovery requests;

[0401] -powerRampingStep: power ramping factor;

[0402] -msgA-PreamblePowerRampingStep: power ramp factor for MSGA preamble;

[0403] -powerRampingStepHighPriority: power ramping factor in case of prioritized random access procedure;

[0404] -scalingFactorBI: scaling factor for the prioritized random access procedure;

[0405] -ra-PreambleIndex: random access preamble;

[0406] -ra-ssb-OccasionMaskIndex: defines the PRACH occasions associated with the SSB where the MAC entity may transmit the random access preamble (see clause 7.4);

[0407] -msgA-SSB-SharedRO-MaskIndex: indicates the subset of 4-step RA type PRACH opportunities shared with 2-step RA type PRACH opportunities for each SSB. If 2-step RA type PRACH opportunities are shared with 4-step RA type PRACH opportunities and msgA-SSB-SharedRO-MaskIndex is not configured, all 4-step RA type PRACH opportunities can be used for 2-step RA type (see clause 7.4);

[0408] -ssb-SharedRO-MaskIndex: defines the PRACH occasions associated with the SSB in which the MAC entity may transmit a random access preamble (see clause 7.4) on which the preamble is allocated for a feature or feature combination;

[0409] -ra-OccasionList: defines the PRACH opportunities associated with the CSI-RS where the MAC entity can transmit the random access preamble;

[0410] -ra-PreambleStartIndex: the starting index of the random access preamble for on-demand SI request;

[0411] -startPreambleForThisPartition: the first preamble associated with a set of random access resources applicable for a random access procedure;

[0412] -preambleTransMax: Maximum number of random access preamble transmissions;

[0413] -ssb-perRACH-OccasionAndCB-PreamblesPerSSB: defines the number of SSBs mapped to each PRACH opportunity of 4-step RA type and the number of contention-based random access preambles mapped to each SSB;

[0414] -msgA-CB-PreamblesPerSSB-PerSharedRO: defines the number of contention-based random access preambles of 2-step RA type mapped to each SSB when PRACH opportunities are shared between 2-step and 4-step RA types;

[0415] -msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB: defines the number of SSBs mapped to each PRACH occasion of 2-step RA type and the number of contention-based random access preambles mapped to each SSB;

[0416] …

[0417] - If random access preamble group B is configured for 4-step RA type, then:

[0418] -ra-Msg3SizeGroupA: threshold for determining the group of random access preambles of 4-step RA type;

[0419] -msg3-DeltaPreamble: Delta in TS 38.213 PREAMBLE_Msg3 ;

[0420] -messagePowerOffsetGroupB: the power offset for preamble selection contained in groupBconfigured;

[0421] -numberOfRA-PreamblesGroupA: defines the number of random access preambles in random access preamble group A for each SSB included in groupBconfigured.

[0422] - If random access preamble group B is configured for 2-step RA type, then:

[0423] -msgA-DeltaPreamble: Delta in TS 38.213 MsgA_PUSCH ;

[0424] -messagePowerOffsetGroupB: The power offset for preamble selection contained in GroupB-ConfiguredTwoStepRA;

[0425] -numberOfRA-PreamblesGroupA: defines the number of random access preambles in random access preamble group A used for each SSB included in GroupB-ConfiguredTwoStepRA;

[0426] -ra-MsgA-SizeGroupA: The threshold used to determine the group of random access preambles of the 2-step RA type.

[0427] - The set of random access preambles and / or PRACH opportunities used for SI request (if any);

[0428] - The set of random access preambles and / or PRACH opportunities for beam failure recovery request (if any);

[0429] - The set of random access preambles and / or PRACH opportunities for reconfiguration with synchronization (if any);

[0430] -ra-ResponseWindow: time window for monitoring RA response (SpCell only);

[0431] -ra-ContentionResolutionTimer: Contention resolution timer (SpCell only);

[0432] -msgB-ResponseWindow: Time window for monitoring RA responses of 2-step RA type (SpCell only).

[0433] …

[0434] When the random access procedure is initiated on the serving cell, the MAC entity shall:

[0435] 1> Clear the Msg3 buffer;

[0436] 1> Clear the MSGA buffer;

[0437] 1> Set PREAMBLE_TRANSMISSION_COUNTER to 1;

[0438] 1> Set PREAMBLE_POWER_RAMPING_COUNTER to 1;

[0439] 1> Set PREAMBLE_BACKOFF to 0ms;

[0440] 1> Set POWER_OFFSET_2STEP_RA to 0dB;

[0441] …

[0442] 1> According to clause 5.1.1b, select a random access resource set applicable to the current random access procedure;

[0443] …

[0444] 1> If RA_TYPE is set to 2-stepRA:

[0445] 2> Perform the random access resource selection procedure for 2-step RA type (see clause 5.1.2a).

[0446] 1> Otherwise:

[0447] 2> Perform random access resource selection procedure (see clause 5.1.2).

[0448] 5.1.1a Initialization of variables specific to random access types

[0449] The MAC entity will:

[0450] 1> If RA_TYPE is set to 2-stepRA:

[0451] 2> Set PREAMBLE_POWER_RAMPING_STEP to msgA-PreamblePowerRampingStep;

[0452] …

[0453] 2> else if ra-PrioritizationForSlicingTwoStep for NSAG-ID is configured for the selected carrier; and

[0454] 2> If the MAC entity is provided with this NSAG-ID by upper layers:

[0455] 3> If powerRampingStepHighPriority is configured in ra-PrioritizationForSlicingTwoStep for this NSAG-ID:

[0456] 4> Set PREAMBLE_POWER_RAMPING_STEP to powerRampingStepHighPriority.

[0457] …

[0458] 1> Otherwise (i.e., RA_TYPE is set to 4-stepRA):

[0459] 2> Set PREAMBLE_POWER_RAMPING_STEP to powerRampingStep;

[0460] …

[0461] 2> Set preambleTransMax to the preambleTransMax contained in RACH-ConfigGeneric;

[0462] 2> If a random access procedure is initiated for SpCell beam failure recovery (as specified in clause 5.17); and

[0463] 2> If beamFailureRecoveryConfig is configured for the active UL BWP of the selected carrier:

[0464] 3> Start beamFailureRecoveryTimer (if configured);

[0465] 3> Apply the parameters powerRampingStep, preambleReceivedTargetPower, and preambleTransMax configured in beamFailureRecoveryConfig.

[0466] 2> if a random access procedure is initiated for beam failure recovery (as specified in clause 5.17); and

[0467] 2> if beamFailureRecoveryConfig is configured for the active UL BWP of the selected carrier; and

[0468] 2> If ra-Prioritization is configured in beamFailureRecoveryConfig:

[0469] 3> Set PREAMBLE_POWER_RAMPING_STEP to powerRampingStepHighPriority in ra-Prioritization contained in beamFailureRecoveryConfig;

[0470] …

[0471] 2> If RA_TYPE switches from 2-stepRA to 4-stepRA during this random access procedure:

[0472] 3>Set POWER_OFFSET_2STEP_RA to (PREAMBLE_POWER_RAMPING_COUNTER-1)×(MSGA_PREAMBLE_POWER_RAMPING_STEP-PREAMBLE_POWER_RAMPING_STEP).

[0473] …

[0474] 5.1.1b Selection of random access resource set for random access procedure

[0475] The MAC entity will:

[0476] 1> if the BWP selected for the random access procedure is configured with a random access resource set with msg3-Repetitions set to true and a random access resource set without msg3-Repetitions set to true, and the RSRP referenced by the downlink path loss is less than rsrp-ThresholdMsg3; or

[0477] 1> If the BWP selected for the random access procedure is configured only with random access resource sets with msg3-Repetitions set to true:

[0478] 2> Assume that Msg3 repetition is applicable to the current random access procedure.

[0479] 1> Otherwise:

[0480] 2> Assume that Msg3 repetition is not applicable to the current random access procedure.

[0481] …

[0482] 1> If no contention-free random access resources and random access resources for SI request are provided for this random access procedure, and one or more of the features including RedCap and / or slicing and / or SDT and / or MSG3 repetition are applicable to this random access procedure:

[0483] NOTE 2: The applicability of SDT is determined by the MAC entity according to clause 5.27. The applicability of NSAG-ID is determined by upper layers when a random access procedure is initiated. The applicability of RedCap is also determined by upper layers when a random access procedure is initiated and is applicable to random access procedures initiated by a PDCCH order and any random access procedure initiated by the MAC entity.

[0484] 2> If no random access resource set is available for any feature applicable to the current random access procedure (as specified in clause 5.1.1c):

[0485] 3> Select a set of random access resources that is not associated with any feature indication (as specified in clause 5.1.1c) for this random access procedure.

[0486] 2> Otherwise if there is a random access resource set available that can be used to indicate all features that trigger this random access procedure:

[0487] 3> Select this random access resource set for this random access procedure.

[0488] 2> Otherwise (i.e., there are one or more sets of random access resources available that are configured with an indication of a subset of all features for triggering this random access procedure):

[0489] 3> Select a set of random access resources from the available sets of random access resources based on the priority order indicated by upper layers as specified in clause 5.1.1d for this random access procedure.

[0490] 1> Otherwise, if a contention-free random access resource has been provided for this random access procedure and RedCap is applicable to the current random access procedure and there is a random access resource set available that is only configured with RedCap indication:

[0491] 2> Select this random access resource set for this random access procedure.

[0492] 1> Otherwise:

[0493] 2> Select a set of random access resources that is not associated with any feature indication (as specified in clause 5.1.1c) for the current random access procedure.

[0494] …

[0495] 5.1.3 Random Access Preamble Transmission

[0496] For each random access preamble, the MAC entity shall:

[0497] 1> If PREAMBLE_TRANSMISSION_COUNTER is greater than one; and

[0498] 1> If a notification to suspend the power ramp counter has not been received from the lower layer; and

[0499] 1> If no LBT failure indication is received from the lower layers for the last random access preamble transmission; and

[0500] 1> If the selected SSB or CSI-RS has not changed since the selection in the last random access preamble transmission:

[0501] 2>Increment PREAMBLE_POWER_RAMPING_COUNTER by 1.

[0502] 1> Select the value of DELTA_PREAMBLE according to clause 7.3;

[0503] 1>Set PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower+DELTA_PREAMBLE+(PREAMBLE_POWER_RAMPING_COUNTER-1)×PREAMBLE_POWER_RAMPING_STEP+POWER_OFFSET_2STEP_RA;

[0504] 1> Calculate the RA-RNTI associated with the PRACH opportunity in which the random access preamble is transmitted, except for the contention-free random access preamble used for beam failure recovery request;

[0505] 1> Instruct the physical layer to transmit a random access preamble using the selected PRACH opportunity, the corresponding RA-RNTI (if available), PREAMBLE_INDEX and PREAMBLE_RECEIVED_TARGET_POWER.

[0506] …

[0507] 5.1.3a MSGA Transfer

[0508] For each MSGA, the MAC entity shall:

[0509] 1> If PREAMBLE_TRANSMISSION_COUNTER is greater than one; and

[0510] 1> If a notification to suspend the power ramp counter has not been received from the lower layer; and

[0511] 1> If no LBT failure indication is received from lower layers for the last MSGA random access preamble transmission; and

[0512] 1> If the selected SSB has not changed since the selection in the last random access preamble transmission:

[0513] 2>Increment PREAMBLE_POWER_RAMPING_COUNTER by 1.

[0514] 1> Select the value of DELTA_PREAMBLE according to clause 7.3;

[0515] 1>Set PREAMBLE_RECEIVED_TARGET_POWER to msgA-PreambleReceivedTargetPower+DELTA_PREAMBLE+(PREAMBLE_POWER_RAMPING_COUNTER-1)×PREAMBLE_POWER_RAMPING_STEP;

[0516] …

[0517] 1> Calculate the MSGB-RNTI associated with the PRACH opportunity in which the random access preamble is transmitted;

[0518] 1> Instruct the physical layer to transmit MSGA using the associated PUSCH resources of the selected PRACH opportunity and MSGA (if the selected preamble and PRACH opportunity are mapped to valid PUSCH opportunities), using the corresponding RA-RNTI, MSGB-RNTI, PREAMBLE_INDEX, PREAMBLE_RECEIVED_TARGET_POWER, msgA-PreambleReceivedTargetPower and the power ramp variable applied to the latest MSGA preamble transmission (i.e., (PREAMBLE_POWER_RAMPING_COUNTER-1)×PREAMBLE_POWER_RAMPING_STEP);

[0519] …

[0520] 5.1.4 Random Access Response Reception

[0521] Once the random access preamble is transmitted, regardless of whether measurement gaps may occur, the MAC entity shall:

[0522] …

[0523] 1> if the ra-ResponseWindow configured in BeamFailureRecoveryConfig expires and if a PDCCH transmission on the search space indicated by recoverySearchSpaceId addressed to the C-RNTI has not been received on the serving cell that transmitted the preamble; or

[0524] 1> If the ra-ResponseWindow configured in RACH-ConfigCommon expires and if a Random Access Response containing a Random Access Preamble identifier matching the transmitted PREAMBLE_INDEX has not been received:

[0525] 2> The random access response reception is considered unsuccessful;

[0526] 2>Increment PREAMBLE_TRANSMISSION_COUNTER by 1;

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

[0528] 3> If the random access preamble is transmitted on SpCell:

[0529] 4>Indicate random access problem to upper layer;

[0530] 4> If this random access procedure is triggered for an SI request:

[0531] 5> The random access procedure is considered to have not been completed successfully.

[0532] 3> Otherwise if the random access preamble is transmitted on the SCell:

[0533] 4> The random access procedure is considered to have not been completed successfully.

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

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

[0536] 3> If the criteria for selecting contention-free random access resources (as defined in clause 5.1.2) are met during the backoff time:

[0537] 4> Perform random access resource selection procedure (see clause 5.1.2).

[0538] …

[0539] 4> Perform the random access resource selection procedure after the backoff time (see clause 5.1.2).

[0540] …

[0541] 5.1.4a 2-step RA type MSGB reception and contention resolution

[0542] Once the MSGA preamble is transmitted, whether or not a measurement gap may occur, the MAC entity shall:

[0543] 1> Start msgB-ResponseWindow at PDCCH opportunity as specified in TS 38.213, clause 8.2A;

[0544] 1>While msgB-ResponseWindow is running, monitor whether the PDCCH of SpCell has a random access response identified by MSGB-RNTI;

[0545] 1> If the C-RNTI MAC CE is included in the MSGA:

[0546] 2> While msgB-ResponseWindow is running, monitor the PDCCH of SpCell to see if there is a random access response identified by C-RNTI.

[0547] …

[0548] 1> If msgB-ResponseWindow expires and random access response reception has not been considered successful based on the above description:

[0549] 2>Increment PREAMBLE_TRANSMISSION_COUNTER by 1;

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

[0551] 3>Indicate random access problems to upper layers;

[0552] …

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

[0554] 3> If msgA-TransMax applies (see clause 5.1.1a) and PREAMBLE_TRANSMISSION_COUNTER = msgA-TransMax+1:

[0555] 4> Set RA_TYPE to 4-stepRA;

[0556] 4> Perform initialization of variables specific to the random access type as specified in clause 5.1.1a;

[0557] 4> If the Msg3 buffer is empty:

[0558] 5> Get the MAC PDU to be transmitted from the MSGA buffer and store it in the Msg3 buffer;

[0559] 4> Clear the HARQ buffer in the MSGA buffer used to transmit MAC PDU;

[0560] 4> discard the explicitly transmitted contention-free 2-step RA type random access resources (if any);

[0561] 4> Perform the random access resource selection procedure as specified in clause 5.1.2.

[0562] 3> Otherwise:

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

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

[0565] 5> Perform the random access resource selection procedure for 2-step RA type random access (see clause 5.1.2a).

[0566] 4> Otherwise:

[0567] 5> Perform the random access resource selection procedure for 2-step RA type random access after the backoff time (see clause 5.1.2a).

[0568] ****************END OF QUOTE*****************

[0569] The definition, calculation and use of TA information / values ​​are specified in TS 38.211 (

[10] 3GPP TS 38.211 V17.5.0, "NR, Physical channels and modulation") and TS 38.213 ([9] 3GPP TS 38.213 V17.5.0, "NR, Physical layer procedures for control") as follows:

[0570] **************** Quote starts

[10] ****************

[0571] 4.3 Frame Structure

[0572] 4.3.1 Frame and Subframe

[0573] …

[0574] On a carrier, there is a set of frames in the uplink and a set of frames in the downlink.

[0575] The uplink frame number i for transmission from the UE will precede the start of the corresponding downlink frame at the UE Start, where

[0576] ●N TA and N TA，偏移 As given in clause 4.2 of [TS 38.213], except for msgA transmission on PUSCH, where N TA =0;

[0577] ● Given by clause 4.2 of [TS 38.213] is derived from the higher-level parameters ta-Common, ta-CommonDrift, and ta-CommonDriftVariant (if configured), otherwise

[0578] ● Given by clause 4.2 of [TS 38.213] is calculated by the UE based on higher layer parameters related to the UE position and the serving satellite ephemeris (if configured), otherwise

[0579] Figure 8 It is from 3GPP TS 38.211V17.5.0 "NR, physical channels and modulation" Figure 4 .3.1-1: Reproduction of uplink-downlink timing relationship.

[0580] ****************END OF QUOTE*****************

[0581] ***************** Quote starts [9]****************

[0582] 4.2 Transmission Timing Adjustment

[0583] The UE may be provided with the value of the timing advance offset for the serving cell via n-TimingAdvanceOffset for the serving cell. TA，偏移 If the UE is not provided with n-TimingAdvanceOffset for the serving cell, the UE determines the default value N of the timing advance offset for the serving cell as described in [TS38.133]. TA，偏移 .

[0584] If the UE is configured with two UL carriers for the serving cell, the same timing advance offset value N TA，偏移 Applicable to both carriers.

[0585] After receiving the timing advance command for a TAG, the UE calculates the timing advance command based on the value N that the UE expects to be the same for all serving cells in the TAG. TA，偏移 And adjust the uplink timing of PUSCH / SRS / PUCCH transmission on all serving cells in the TAG based on the received timing advance command, wherein the uplink timing of PUSCH / SRS / PUCCH transmission is the same for all serving cells in the TAG.

[0586] …

[0587] For 2 μ 15kHz SCS, used for the TAG timing advance command to indicate the uplink timing relative to the TAG's current uplink timing in 16·64·T c / 2 μ The start timing of the random access preamble is described in [TS38.211].

[0588] In case of random access response or in case of absolute timing advance command MAC CET in TAG A , the timing advance command in [TS 38.321] is transmitted through T A =0, 1, 2, ..., 3846 indicates the index value N TA Values, which have 2 μ The time alignment amount of the TAG of the 15kHz SCS is N TA =T A ·16·64 / 2 μ . N TA Defined in [TS 38.211] and is relative to the SCS transmitted for the first uplink from the UE after receiving a Random Access Response or Absolute Timing Advance Command MAC CE.

[0589] In other cases, the timing advance command of the TAG [TS 38.321]T A By T A =0, 1, 2, ..., 63 indicates the current N TA Value N TA_old To New N TA Value N TA_new The adjustment of μ 15kHz SCS, N TA_new =N TA_old +(T A-31)·16·64 / 2 μ .

[0590] …

[0591] By positive or negative quantity TA The adjustment of the value indicates that the uplink transmission timing for the TAG is advanced or delayed by a corresponding amount, respectively.

[0592] For a timing advance command received on uplink timeslot n, and for a transmission other than a PUSCH scheduled by a RAR UL grant or a fallbackRAR UL grant as described in clause 8.2A or 8.3, or a PUCCH with HARQ-ACK information in response to a successRAR as described in clause 8.2A, the corresponding adjustment of the uplink transmit timing is from uplink timeslot n+k+1+2 μ ·K 偏移 is applied at the beginning of N T，1 is the duration in milliseconds of N1 symbols corresponding to the PDSCH processing time of UE processing capability 1 when additional PDSCH DM-RS is configured, N T，2 is the duration in milliseconds of N2 symbols corresponding to the PUSCH preparation time [TS 38.214] of UE processing capability 1, N TZ，max is the maximum timing advance value in milliseconds that can be provided by the 12-bit TA common field, is the number of time slots per subframe, T sf is the subframe duration of 1 ms, and K 偏移 =K 小区，偏移 -K UE，偏移 , where K 小区，偏移 Provided by cellSpecificKoffset and K UE，偏移 Provided by the differential Koffset MAC CE command [11, TS 38.321]; otherwise, if not provided separately, K 小区，偏移 =0 or K UE，偏移 =0. N1 and N2 are determined relative to the minimum SCS among the SCSs of all configured UL BWPs of all uplink carriers in the TAG and all configured DL BWPs of the corresponding downlink carriers. For μ=0, the UE assumes that N 1，0 = 14[6, TS 38.214]. Time slot n and is determined relative to the minimum SCS among the SCSs of all configured UL BWPs of all uplink carriers in a TAG. TA，maxis determined relative to the minimum SCS among all configured UL BWPs of all uplink carriers in the TAG and the SCSs of all configured initial ULBWPs provided by initialUplinkBWP. The uplink timeslot n is determined with respect to the minimum SCS among all configured UL BWPs of all uplink carriers in the TAG and the SCSs of all configured initial ULBWPs provided by initialUplinkBWP. TA = 0, where PDSCH provides a timing advance command and T TA Defined in [TS 38.211].

[0593] …

[0594] If, in the absence of a timing advance command, the received downlink timing changes and is not compensated for or is only partially compensated for by the uplink timing adjustment as described in [TS 38.133], the UE changes N accordingly. TA .

[0595] If two adjacent time slots overlap due to a TA command, the latter time slot is reduced in duration relative to the previous time slot. During the actual transmission time window for PUSCH or PUCCH transmission [TS 38.214], the UE does not change N TA .

[0596] Using the higher layer ephemeris parameters for the serving satellite (if provided), the UE determines the To pre-compensate the two-way propagation delay between the uplink time synchronization reference point and the serving satellite, the UE determines the one-way propagation delay Delay based on the UE's 共同 (t) [TS 38.211]:

[0597]

[0598] Among them, TA 共同 TA 共同漂移 and TA 共同漂移变化 Provided by ta-Common, ta-CommonDrift, and ta-CommonDriftVariant, respectively, and t 纪元 It's TA 共同 TA 共同漂移 and TA 共同漂移变化 epoch time [TS 38.331]. 共同 (t) provides the distance between the serving satellite and the uplink time synchronization reference point at time t divided by the speed of light. The uplink time synchronization reference point is located on a satellite with N TA，偏移 The point at which DL and UL framing are aligned at a given offset.

[0599] ****************Next Quote*****************

[0600] 8.2 Random Access Response - Type 1 Random Access Procedure

[0601] In response to a PRACH transmission, the UE attempts to detect a DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI during a window controlled by higher layers [TS 38.321]. The window starts at the first symbol of the earliest CORESET for which the UE is configured to receive a PDCCH for a Type 1-PDCCH CSS set as defined in clause 10.1, i.e., at least one symbol after the last symbol of a PRACH opportunity corresponding to a PRACH transmission, wherein the symbol duration corresponds to the SCS for a Type 1-PDCCH CSS set as defined in clause 10.1. If as defined in [TS 38.211] or is not zero, the window is extended by an additional T TA +k mac milliseconds after the start, where T TA Defined in [TS 38.211] and k mac Provided by kmacs, or if kmacs is not provided, k mac = 0. Based on the SCS for the Type 1-PDCCH CSS set, the length of the window in number of slots is provided by ra-ResponseWindow.

[0602] …

[0603] 8.2A Random Access Response - Type 2 Random Access Procedure

[0604] In response to a transmission of PRACH and PUSCH, or in response to a transmission of only PRACH in case the PRACH preamble is mapped to a valid PUSCH opportunity, the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding MsgB-RNTI during a window controlled by higher layers [TS 38.321]. The window starts at the first symbol of the earliest CORESET for which the UE is configured to receive a PDCCH for a Type1-PDCCH CSS set as defined in clause 10.1, i.e., at least one symbol after the last symbol of a PUSCH opportunity corresponding to a PRACH transmission, with the symbol duration corresponding to the SCS for a Type1-PDCCH CSS set. If as defined in [TS 38.211] or is not zero, the window is extended by an additional T TA+k mac milliseconds after the start, where T TA Defined in [TS 38.211] and k mac Provided by kmacs, or if kmacs is not provided, k mac = 0. Based on the SCS for the Type1-PDCCH CSS set, the length of the window in number of slots is provided by msgB-ResponseWindow.

[0605] ****************END OF QUOTE*****************

[0606] TA maintenance in MAC entity (for N TA ) and the application for UE-gNB RTT are specified in TS 38.321 ([3] 3GPP TS 38.321 V17.5.0, “NR, MAC protocol specification”) as follows:

[0607] ***************** Quote starts [3]****************

[0608] 3.1 Definition

[0609] …

[0610] Non-terrestrial network: NG-RAN consisting of gNBs that provide non-terrestrial NR access to UEs with the help of NTN payload starting from onboard or off-board NTN vehicles and NTN gateways.

[0611] …

[0612] Serving cell: PCell, PSCell or SCell in TS 38.331.

[0613] …

[0614] Timing Advance Group: A group of serving cells configured by RRC for cells with configured UL using the same timing reference cell and the same timing advance value. The timing advance group of the SpCell containing the MAC entity is called the Primary Timing Advance Group (PTAG), while the term Secondary Timing Advance Group (STAG) refers to other TAGs.

[0615] UE-gNB RTT: For non-terrestrial networks, the sum of the UE’s timing advance value (see TS 38.211 clause 4.3.1) and kmac.

[0616] ****************Next Quote*****************

[0617] 5.1.5 Contention Resolution

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

[0619] 1> If Msg3 transmission (i.e., initial transmission or HARQ retransmission) is scheduled with PUSCH repetition type A:

[0620] 2> If Msg3 is sent on a non-terrestrial network:

[0621] 3> Start or restart ra-ContentionResolutionTimer in the first symbol after all repetitions of Msg3 transmission end plus UE-gNB RTT.

[0622] …

[0623] 1> Otherwise, if the Msg3 transmission (i.e., initial transmission or HARQ retransmission) is transmitted on a non-terrestrial network:

[0624] 2> Start or restart ra-ContentionResolutionTimer in the first symbol after the end of Msg3 transmission plus UE-gNB RTT.

[0625] …

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

[0627] 1> If a notification of receipt of a PDCCH transmission of SpCell is received from a lower layer:

[0628] 2> If C-RNTI MAC CE is included in Msg3:

[0629] 3> If a random access procedure is initiated for SpCell beam failure recovery or for both SpCell's BFD-RS set beam failure recovery (as specified in clause 5.17) and the PDCCH transmission is addressed to the C-RNTI; or

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

[0631] 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:

[0632] 4> Consider this competition resolved successfully;

[0633] 4>Stop ra-ContentionResolutionTimer;

[0634] 4> discard TEMPORARY_C-RNTI;

[0635] 4> This random access procedure is considered to be completed successfully.

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

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

[0638] 4>Stop ra-ContentionResolutionTimer;

[0639] 4> If the MAC PDU contains the UE contention resolution identity MAC CE; and

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

[0641] 5> The contention resolution is considered successful and the decomposition and demultiplexing of MAC PDU is terminated;

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

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

[0644] 5> Otherwise:

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

[0646] 5> discard TEMPORARY_C-RNTI;

[0647] 5> This random access procedure is considered to be completed successfully.

[0648] 4> Otherwise:

[0649] 5> discard TEMPORARY_C-RNTI;

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

[0651] 1> If ra-ContentionResolutionTimer expires:

[0652] 2> If Msg3 is sent on a non-terrestrial network:

[0653] 3> If a PDCCH addressed to the TC-RNTI indicating an uplink grant for Msg3 retransmission is not received after the start of ra-ContentionResolutionTimer:

[0654] 4> discard TEMPORARY_C-RNTI;

[0655] 4> Believe that the competition solution was unsuccessful.

[0656] 2> Otherwise:

[0657] 3> discard TEMPORARY_C-RNTI;

[0658] 3> Consider the competition resolution to be unsuccessful.

[0659] 1> If the contest resolution is deemed unsuccessful:

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

[0661] 2>Increment PREAMBLE_TRANSMISSION_COUNTER by 1;

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

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

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

[0665] 4> The random access procedure is considered to have not been completed successfully.

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

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

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

[0669] 4> If the criteria for selecting contention-free random access resources (as defined in clause 5.1.2) are met during the backoff time:

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

[0671] 4> Otherwise:

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

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

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

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

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

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

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

[0679] 5> Perform random access resource selection as specified in clause 5.1.2.

[0680] 4> Otherwise:

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

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

[0683] 6> Perform the Random Access Resource Selection procedure for the 2-step RA type as specified in clause 5.1.2a.

[0684] 5> Otherwise:

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

[0686] ****************Next Quote*****************

[0687] 5.2 Maintenance of uplink time alignment

[0688] RRC configures the following parameters to maintain UL time alignment:

[0689] - timeAlignmentTimer (per TAG), which controls how long the MAC entity considers the uplink time alignment of the serving cells belonging to the associated TAG;

[0690] …

[0691] The MAC entity will:

[0692] 1> When a timing advance command MAC CE is received, and if N has been maintained with the indicated TAG TA (as defined in TS 38.211):

[0693] 2> Apply timing advance command for the indicated TAG;

[0694] …

[0695] 3> Start or restart the timeAlignmentTimer associated with the indicated TAG.

[0696] 1> When a timing advance command is received in a random access response message for a serving cell belonging to a TAG or in a MSGB for a SpCell:

[0697] 2> If the MAC entity does not select a random access preamble among the contention-based random access preambles:

[0698] 3> Apply timing advance command for this TAG;

[0699] 3> Start or restart the timeAlignmentTimer associated with this TAG.

[0700] 2> Otherwise, if the timeAlignmentTimer associated with this TAG is not running:

[0701] 3> Apply timing advance command for this TAG;

[0702] 3>Start the timeAlignmentTimer associated with this TAG;

[0703] 3> when the contest resolution is deemed unsuccessful as described in clause 5.1.5; or

[0704] …

[0705] 4> Stop the timeAlignmentTimer associated with this TAG.

[0706] …

[0707] 2> Otherwise:

[0708] 3> Ignore the received timing advance command.

[0709] 1> When an Absolute Timing Advance Command is received in response to an MSGA transmission containing a C-RNTI MAC CE as specified in clause 5.1.4a:

[0710] 2> Apply timing advance command for PTAG;

[0711] …

[0712] 3> Start or restart the timeAlignmentTimer associated with PTAG.

[0713] …

[0714] 1> When an instruction to start the timeAlignmentTimer associated with PTAG has been received from the upper layer:

[0715] 2>Start the timeAlignmentTimer associated with PTAG.

[0716] 1>When timeAlignmentTimer expires:

[0717] 2> If timeAlignmentTimer is associated with PTAG:

[0718] 3> Clear all HARQ buffers for all serving cells;

[0719] 3> Notify RRC to release PUCCH for all serving cells (if configured);

[0720] 3> Notify RRC to release SRS for all serving cells (if configured);

[0721] 3> Clear any configured downlink assignments and configured uplink grants;

[0722] 3> Clear any PUSCH resources used for semi-persistent CSI reporting;

[0723] 3> All running timeAlignmentTimers are considered expired;

[0724] 3> Maintain N of all tags TA (Defined in TS 38.211).

[0725] …

[0726] When the timeAlignmentTimer associated with the TAG to which the serving cell belongs is not running, the CG-SDT procedure is not in progress, or the SRS transmission in RRC_INACTIVE as in clause 5.26 is not in progress, the MAC entity shall not perform any uplink transmission on this serving cell except for the random access preamble and MSGA transmission. In addition, when the timeAlignmentTimer associated with the PTAG is not running, the CG-SDT procedure is not in progress, and the SRS transmission in RRC_INACTIVE as in clause 5.26 is not in progress, the MAC entity shall not perform any uplink transmission on any serving cell except for the random access preamble and MSGA transmission on the SpCell. When the cg-SDT-TimeAlignmentTimer is not running and the inactivePosSRS-TimeAlignmentTimer is not running during the ongoing CG-SDT procedure triggered as in clause 5.27, the MAC entity shall not perform any uplink transmission except for the random access preamble and MSGA transmission.

[0727] ****************END OF QUOTE*****************

[0728] In LTE, the NW may instruct the NW via a handover command as specified in TS 36.331 (

[12] 3GPP TS 36.331 V17.5.0, “E-UTRA, RRC Protocol Specification”). TA :

[0729] **************** Quote starts

[12] ****************

[0730]

[0731] ****************Next Quote*****************

[0732]

[0733]

[0734]

[0735]

[0736] ****************END OF QUOTE*****************

[0737] The general description of location services (LCS) and / or UE positioning in TN is specified in TS 38.305 (

[11] 3GPP TS 38.305 V17.5.0, "NG-RAN, Stage 2 Functional Specification for UE Positioning in NG-RAN") as follows:

[0738] **************** Quote starts

[11] ****************

[0739] 4.1 Assumptions and generality

[0740] …

[0741] Positioning functionality provides a way to determine the geographic location and / or velocity of a UE based on measuring radio signals. Location information may be requested by and reported to a client (e.g., an application) associated with the UE, or by a client within or attached to the core network. Location information should be reported in a standard format, such as those based on cell-based or geographic coordinates, along with an estimated error (uncertainty) in the UE's position and velocity and, if available, the positioning method (or list of methods) used to obtain the position estimate.

[0742] 4.2 The role of UE positioning method

[0743] The NG-RAN may utilize one or more positioning methods in order to determine the location of the UE.

[0744] Locating a UE involves two main steps:

[0745] -Signal measurement; and

[0746] - Position estimation and optional velocity calculation based on measurements.

[0747] Signal measurements can be made by the UE or by the serving ng-eNB or gNB. The basic signals measured for terrestrial positioning methods are typically LTE or NR radio transmissions; however, other methods may utilize other transmissions, such as general radio navigation signals including those from the Global Navigation Satellite System (GNSS).

[0748] …

[0749] The position estimate calculation can be made by the UE or by the LMF.

[0750] ****************END OF QUOTE*****************

[0751] A non-terrestrial network (NTN) in 3GPP can provide non-terrestrial access to user equipment (UE) by means of an NTN payload on an airborne or satellite-borne NTN vehicle and an NTN gateway. NTN can provide wide-area coverage and provide network (NW) access in scenarios when terrestrial networks are not feasible (e.g., deserts, polar regions, and / or on airplanes). UEs can connect to NTNs involving airborne / satellite-borne for transmission and / or reception. NTNs may include various platforms, including low earth orbit (LEO) satellites, medium earth orbit (MEO) satellites, high elliptical orbit (HEO) satellites, geostationary orbit (GEO) satellites, geostationary synchronous orbit (GSO) satellites, non-geostationary synchronous orbit (NGSO) satellites, and / or high altitude communication platforms (HAPS). LEO satellites may have earth-fixed beams (e.g., beams temporarily fixed at one location during a period of time) or earth-mobile beams (e.g., beams continuously move together with the satellite). LEO satellites may serve / provide Earth mobile cells (eg, with Earth fixed beams) and / or (quasi) Earth fixed cells (eg, with Earth mobile beams).

[0752] Currently (in 3GPP Release 18 and earlier), it is assumed that a UE supporting NTN has Global Navigation Satellite System (GNSS) capability. The UE may compensate uplink (UL) timing and frequency based on the UE position obtained via GNSS. The UE may have a valid position via GNSS and receive some NTN information (e.g., ephemeris, common timing advance (TA), parameters configured in NTN-Config in TS 38.331 ([4] 3GPP TS 38.331 V17.5.0)) to pre-compensate for TA values ​​and / or frequency shifts. The assumption limits the applicability of 3GPP NTN. For example, some UEs may not have GNSS capability. And some UEs may not always receive GNSS signals or acquire GNSS positions, for example due to the radio environment. It has been observed that it is possible that GNSS may not be available in some cases. In addition, GNSS handling may cause delays to UE operation due to positioning acquisition time and additional energy consumption. For improvement, GNSS-independent mechanisms may be introduced to improve energy efficiency and reduce dependence on GNSS service availability. GNSS independent mechanisms have been discussed in RAN meetings to improve UL robustness and reduce dependency on GNSS service availability. UEs without GNSS (capability) will be able to access NTN in future releases. Throughout this disclosure, the following may be interchangeable: GNSS independent, no GNSS, non-GNSS.

[0753] In order to support GNSS independent operation, some enhancements to the physical random access channel (PRACH) resources and / or random access (RA) scheme may be required for UEs without GNSS capabilities. According to TR 38.821 ([1] 3GPP TR38.821 V16.1.0), it will be possible for the network to configure separate RA resources based on GNSS capabilities. It is assumed that the random access channel (RACH) resources or configuration are separated between UEs with and without GNSS.

[0754] Throughout the present disclosure, a UE with GNSS may be a UE with GNSS capability. A UE with GNSS may be a first UE having or configured / equipped with a GNSS device / receiver. A UE with GNSS may be (referred to as) a GNSS-based UE, a GNSS UE, or a GNSS-dependent UE. A UE with GNSS may mean that the UE is capable of GNSS operation. A UE with GNSS may mean that the UE provides capability information indicating that the UE is capable of GNSS operation. A UE with GNSS may mean that the UE (currently) has UE location information. A UE with GNSS may mean that the UE (currently) has (sufficient / valid) GNSS information. The GNSS information may be UE location information derived (or obtained) via GNSS. The GNSS information may be a GNSS signal received by the UE. The GNSS information may be satellite information provided by the NW. A UE with GNSS may be a first type UE (e.g., as specified below). GNSS operation may be or include at least receiving a GNSS signal and / or obtaining location information via GNSS.

[0755] Throughout the present disclosure, a UE without GNSS may be a UE without GNSS capability. A UE without GNSS may be a UE (with or without GNSS capability) that does not acquire GNSS information. A UE without GNSS may be a second UE that does not have or is not configured / equipped with a GNSS device / receiver. A UE without GNSS may be a third UE that has or is configured / equipped with a GNSS device / receiver. The third UE may not receive / acquire / derive / have (enough) GNSS signals or information. The third UE may not access GNSS satellites. The third UE may be in the duration of a GNSS measurement gap. The GNSS measurement validity duration may not be long enough for the third UE to acquire GNSS. The received GNSS signal may not be strong enough for the third UE to acquire a GNSS position. The third UE may be in an indoor scenario. The third UE may disconnect its GNSS operator, for example, for saving power. The third UE may be a first UE that satisfies the first condition (e.g., as specified below). A UE without GNSS may be (referred to as) a UE without GNSS, a non-GNSS UE, or a GNSS independent UE. A UE without GNSS may mean that the UE is not capable of GNSS operation. A UE without GNSS may mean that the UE provides capability information indicating that the UE is not capable of GNSS operation. A UE without GNSS may mean that the UE does not (currently) have UE location information. A UE without GNSS may mean that the UE does not (currently) have (sufficient / valid) GNSS information. The GNSS information may be UE location information derived (or obtained) via GNSS. The GNSS information may be GNSS signals received by the UE. The GNSS information may be satellite information provided by the NW. A UE without GNSS may be a second type UE (e.g., as specified below).

[0756] Throughout the present disclosure, a first type UE may be a UE with GNSS (capability). A first type UE may be a UE that knows its location. A first type UE may be configured / equipped with a GNSS device / receiver. A first type UE may be able to receive GNSS signals or information. A first type UE may be able to obtain / have / know its location and / or GNSS location. A first type UE may have the capability for pre-compensation of timing and frequency offsets. A first type UE may (can) pre-compensate TA and / or frequency shift via UE location and NTN information. A first type UE may (can) maintain UL synchronization based on UE location and NTN information. A first type UE may not know its location (at least at a certain moment, for example, after RA resource selection). A first type UE may not obtain a GNSS location (at least at a certain moment, for example, after RA resource selection). A first type UE may not (can) pre-compensate TA and / or frequency shift (at least at a certain moment, for example, after RA resource selection). A first type UE may not (can) maintain UL synchronization (at least at a certain moment, for example, after RA resource selection). The first type UE may (or may not) satisfy a first condition (e.g., as specified below). The GNSS position, GNSS information, and / or NTN information of the first type UE may be valid. The GNSS signal of the first type UE may be qualified (e.g., the strength of the received GNSS signal is equal to or above a threshold). The GNSS signal of the first type UE may be available.

[0757] Throughout the present disclosure, the second type UE may be a UE without GNSS (capability). The second type UE may be a UE that does not know its position. The second type UE may be configured / equipped with a GNSS device / receiver. The second type UE may not be configured / equipped with a GNSS device / receiver. The second type UE may not be able to receive GNSS signals or information. The second type UE may not be able to obtain / have / know its position and / or GNSS position. The second type UE may have the capability for pre-compensation of timing and frequency offsets. The second type UE may not have the capability for pre-compensation of timing and frequency offsets. The second type UE may not (can) pre-compensate TA and / or frequency shift via UE position and NTN information. The second type UE may not (can) maintain UL synchronization based on UE position and NTN information. The second type UE may know its position (at least at a certain moment, for example, after RA resource selection). The second type UE may (can) pre-compensate TA and / or frequency shift (at least at a certain moment, for example, after RA resource selection). The second type UE may (can) maintain UL synchronization (at least at a certain moment, for example, after RA resource selection). The second type UE may (or may not) satisfy the first condition (e.g., as specified below). The GNSS position, GNSS information, and / or NTN information of the second type UE may be outdated and / or not valid. The GNSS signal of the second type UE may be unqualified (e.g., the strength of the received GNSS signal is equal to or below a threshold). The GNSS signal of the second type UE may be unavailable.

[0758] Throughout this disclosure, a UE with or without GNSS may be based on a GNSS status (eg, strength / availability of GNSS signals and / or validity of GNSS information) and / or a first condition (eg, as specified below).

[0759] The NW may configure the first type RA (resource) and / or the second type RA (resource) to the UE. The NW may indicate (or provide configuration) that the cell allows (or is capable of) the first type RA (resource) and / or the second type RA (resource). The UE may access the cell via the first type RA (resource) or the second type RA (resource). The first type RA (resource) may be different from the second type RA (resource). The first type RA (resource) may be (designed / configured) for a UE with GNSS (e.g., a first type UE). The second type RA (resource) may be (designed / configured) for a UE without GNSS (e.g., a second type UE).

[0760] Throughout the present disclosure, RA (resource) may be, be referred to as and / or include RA resources, RA configuration, RA format and / or RA scheme. RA resources may be or may include (part of) parameters of RACH-ConfigGeneric and / or RACH-ConfigGenericTwoStepRA in TS 38.331 ([4] 3GPP TS 38.331 V17.5.0). Throughout the present disclosure, the following may be interchangeable: RA, RACH and PRACH. "RA" may be, be referred to as, correspond to, be supplemented with and / or be replaced by "RACH" and / or "PRACH".

[0761] The first type RA (resource) and the second type RA (resource) may be configured as or may correspond to RA mode A and RA mode B, respectively. The first type RA (resource) and the second type RA (resource) may be configured as or may correspond to RA type 1 and RA type 2, respectively. The first type RA (resource) may be a current (or legacy) RA resource configured for NTN as specified in TS 38.331 ([4] 3GPP TS 38.331 V17.5.0). The second type RA (resource) may be an additional (e.g., new type, extended) RA (resource) in addition to the first type RA (resource). For example, the NW may configure the second type RA (resource) in the first type RA (resource) (e.g., RACH-ConfigGeneric, RACH-ConfigGenericTwoStepRA). For example, the NW may configure the second type RA (resource) and / or the first type RA (resource) in a common RA configuration (e.g., RACH-ConfigCommon, RACH-ConfigCommonTwoStepRA). The first type RA (resource) and the second type RA (resource) may be configured for NTN. The first type RA (resource) may be designed for UEs with GNSS. The second type RA (resource) may be designed for UEs without GNSS.

[0762] The first type RA (resource) and the second type RA (resource) may include 4-step RA and / or 2-step RA (RA resources). The first type RA (resource) and the second type RA (resource) may include contention-based random access (CBRA) and / or contention-free random access (CFRA) (RA resources). The second type RA (resource) may not include 4-step RA, 2-step RA, CBRA and / or CFRA. The first type RA (resource) and / or the second type RA (resource) may be a common RA resource (for a cell). The first type RA (resource) and / or the second type RA (resource) may be a dedicated RA resource (for a UE). The NW may indicate the first type RA (resource) and / or the second type RA (resource) (or provide its configuration) via broadcast signaling (e.g., system information).

[0763] The first type RA (resource) and the second type RA (resource) may be configured on the same cell. The first type RA (resource) and the second type RA (resource) may be configured on different cells. The cell may allow / configure / be able to have both the first type RA (resource) and the second type RA (resource). The cell may allow / configure / be able to have the first type RA (resource) but not the second type RA (resource). The cell may allow / configure / be able to have the second type RA (resource) but not the first type RA (resource). A cell that provides a configuration (or indication) related to the first type RA (resource) may allow (or be able to) access via the UE of the first type RA (resource). A cell that provides a configuration (or indication) related to the second type RA (resource) may allow (or be able to) access via the UE of the second type RA (resource). A cell that does not provide a configuration (or indication) related to the first type RA (resource) may not allow (or be unable to) access via the UE of the first type RA (resource). A cell that does not provide a configuration (or indication) related to the second type RA (resource) may not allow (or be unable to) access via the UE of the second type RA (resource).

[0764] The UE may (determine) to access the cell via the first type RA (resource) and / or the second type RA (resource) based on (at least) the NW indication (or configuration). For example, if (at least) the NW allows the first type RA (resource) (or has the capability of the first type RA (resource)), the UE is allowed to access the cell via the first type RA (resource). If (at least) the NW allows the second type RA (resource) (or has the capability of the second type RA (resource)), the UE is allowed to access the cell via the second type RA (resource). If (at least) the NW does not allow the first type RA (resource) (or does not have the capability of the first type RA (resource)), the UE is not allowed to access the cell via the first type RA (resource). If (at least) the NW does not allow the second type RA (resource) (or does not have the capability of the second type RA (resource)), the UE is not allowed to access the cell via the second type RA (resource).

[0765] The first type RA (resource) and the second type RA (resource) may be distinguished by a PRACH sequence (e.g., a Zadoff-Chu (ZC) sequence, an m-sequence, a gold sequence), a PRACH format, a repetition scheme, a subcarrier spacing (SCS), a time (adjustment) offset / indication, a frequency (adjustment) offset / indication, and / or an RA response window. The first type RA (resource) and the second type RA (resource) may have (or be configured with) different PRACH sequences (e.g., a ZC sequence, an m-sequence, a gold sequence) and / or PRACH formats. The first type RA (resource) and the second type RA (resource) may have (or be configured with) different repetition schemes, for example, for PRACH. The first type RA (resource) may not have (or be configured with) a repetition scheme. The second type RA (resource) may have (or be configured with) a repetition scheme. The second type RA (resource) may have (or be configured with) more repetitions than the first type RA (resource). The first type RA (resource) and the second type RA (resource) may have (or be configured with) different SCSs, for example, for PRACH. The second type of RA (resource) may have (or be configured with) a larger SCS than the first type of RA (resource). The first type of RA (resource) and the second type of RA (resource) may have (or be configured with) different TAs and / or frequency (adjustment) offsets / indications, for example, for PRACH opportunities, for physical downlink control channel (PDCCH) opportunities, for RA timers (e.g., ra-ResponseWindow, msgB-ResponseWindow, ra-ContentionResolutionTimer). The first type of RA (resource) may not have (or be configured with) a TA and / or frequency (adjustment) offset / indication. The second type of RA (resource) may have (or be configured with) (additional / specific) TA and / or frequency (adjustment) offset / indication. The first type of RA (resource) and the second type of RA (resource) may have (or be configured with) different RA response windows (e.g., ra-ResponseWindow, msgB-ResponseWindow). The second type of RA (resource) may have (or be configured with) a longer RA response window (e.g., ra-ResponseWindow, msgB-ResponseWindow) than the first type of RA (resource). The RA response window (eg, ra-ResponseWindow, msgB-ResponseWindow) is used to receive RA responses (eg, Msg2, random access response (RAR), MSGB), for example, for RA preambles.

[0766] Throughout this disclosure, the first condition may be based on, related to, or include (at least) one or more of the following items (e.g., headings):

[0767] GNSS Operation

[0768] In one example, the first condition may be (based on) whether the UE can complete the (triggered) GNSS measurement or GNSS positioning operation. If the UE is unable to complete the (triggered) GNSS measurement or GNSS positioning operation, the first condition may be met. If the UE completes the (triggered) GNSS measurement or GNSS positioning operation, the first condition may not be met. The GNSS measurement or GNSS positioning operation is triggered by the NW or the UE.

[0769] In one example, the first condition may be (based on / related to) whether the GNSS position of the UE becomes outdated. If the GNSS position becomes (or has become) outdated, the first condition may be satisfied. If the GNSS position does not become outdated, the first condition may not be satisfied. If the GNSS position is valid, the first condition may not be satisfied.

[0770] In one example, the first condition may be (based on / related to) whether the GNSS position fix (or UE position based on GNSS) is available / acquired by the UE. The first condition may be met if the GNSS position fix (or UE position based on GNSS) is / becomes unavailable to the UE. The first condition may be met if the UE does not have / acquire / obtain / maintain a (valid) GNSS position fix (or UE position based on GNSS). The first condition may be met if the UE loses the (valid) GNSS position fix (or UE position based on GNSS). The first condition may not be met if the GNSS position fix (or UE position based on GNSS) is / becomes available to the UE. The first condition may not be met if the UE has / acquires / obtains / maintains a (valid) GNSS position fix (or UE position based on GNSS).

[0771] In one example, the first condition may be (based on / related to) whether the UE has operation with GNSS. If the UE does not have operation with GNSS, the first condition may be satisfied. If the UE has operation with GNSS, the first condition may not be satisfied.

[0772] GNSS validity duration

[0773] In one example, the first condition may be (based on / related to) whether the length of (the remaining time of) the GNSS validity duration is equal to or higher than a threshold value (e.g., a time threshold value). If the length of (the remaining time of) the GNSS validity duration is equal to or lower than the threshold value (e.g., a time threshold value), the first condition may be satisfied. If the length of (the remaining time of) the GNSS validity duration is equal to or higher than the threshold value (e.g., a time threshold value), the first condition may not be satisfied.

[0774] In one example, the first condition may be (based on / related to) whether the GNSS validity duration has expired. If the GNSS validity duration has expired, the first condition may be satisfied. The first condition may be satisfied in response to the GNSS validity duration expiring / expiring. If the GNSS validity duration is in progress, the first condition may not be satisfied.

[0775] GNSS signal strength

[0776] In one example, the first condition may be (based on / related to) whether the received GNSS signal is qualified / sufficient / strong enough. For example, the first condition may be (based on / related to) whether the strength of the received GNSS signal is equal to or higher than a threshold (e.g., a GNSS threshold, a reference signal received power (RSRP) threshold, a threshold related to radio conditions). If the strength of the received GNSS signal is not qualified / sufficient / not strong enough, for example, equal to or lower than a threshold (e.g., a GNSS threshold, an RSRP threshold, a threshold related to radio conditions), the first condition may be met. If the strength of the received GNSS signal is qualified / sufficient / strong enough, for example, equal to or higher than a threshold (e.g., a GNSS threshold, an RSRP threshold, a threshold related to radio conditions), the first condition may not be met.

[0777] In one example, the first condition may be (based on / related to) whether a GNSS signal can be detected or available. If a GNSS signal cannot be detected or is not available, the first condition may be satisfied. If a GNSS signal can be detected or is available, the first condition may not be satisfied.

[0778] GNSS signals may be received / derived / detected from one or more GNSS satellites.

[0779] RA resources, RA formats and / or RA configurations

[0780] In one example, the first condition may be (based on / related to) whether a type of RA resource is configured or indicated to the UE, for example, on the cell. The first condition may be met if the first type of RA resource is not configured or indicated (on the cell and / or to the UE). The first condition may be met if the second type of RA resource is configured or indicated (on the cell and / or to the UE). The first condition may be met if the first type of RA resource is not available (on the cell and / or to the UE). The first condition may not be met if the first type of RA resource is configured or indicated (on the cell and / or to the UE). The first condition may not be met if the second type of RA resource is not configured or indicated (on the cell and / or to the UE). The first condition may not be met if the first type of RA resource is available (on the cell and / or to the UE).

[0781] In one example, the first condition may be (based on / related to) which type of RA resource can be used earlier (e.g., based on a next PRACH opportunity). The first condition may be satisfied if the second type RA resource can be used earlier than the first type RA resource. The first condition may be satisfied if the next PRACH opportunity of the second type RA resource is earlier than the next PRACH opportunity of the first type RA resource. The first condition may be satisfied if the second type RA resource is / becomes available earlier than the first type RA resource. The first condition may not be satisfied if the first type RA resource can be used earlier than the second type RA resource. The first condition may not be satisfied if the next PRACH opportunity of the first type RA resource is earlier than the next PRACH opportunity of the second type RA resource. The first condition may not be satisfied if the first type RA resource is / becomes available earlier than the second type RA resource.

[0782] The above description about RA resources may refer to RA resources, RA formats and / or RA configurations.

[0783] NW Indication

[0784] In one example, the first condition may be (based on / related to) whether the network indicates the availability of GNSS for UEs (e.g., a group of UEs) in the cell. If the network indicates that GNSS is not available, the first condition may be met. If the network indicates that GNSS is available, the first condition may not be met.

[0785] In one example, the first condition may be (based on / related to) whether the GNSS satellite is accessible. If the network indicates that (at least one of) the GNSS satellite is not accessible, the first condition may be met. If the network indicates that (at least one of) the GNSS satellite is accessible, the first condition may not be met.

[0786] In one example, the first condition may be (based on / related to) whether GNSS measurement is triggered / configured. If the network indicates that GNSS measurement is not triggered / configured for the UE, the first condition may be met. If the network indicates that GNSS measurement is triggered / configured for the UE, the first condition may not be met.

[0787] In one example, the first condition may be (based on / related to) whether the indication (or parameter) is configured. If the indication (or parameter) is not configured, the first condition may be satisfied. If the indication (or parameter) is configured, the first condition may not be satisfied.

[0788] The indication (or parameter) may be a timer or a duration. The timer may be started at the length of the duration. The timer may be started at a specific time indicated by the NW. The UE may start or restart the timer in response to receiving the indication (or parameter). When the timer is in operation, the UE may consider the GNSS, GNSS signal, GNSS position, UE position, TA value and / or the first type of RA resources to be valid. When the timer expires or is not in operation, the UE may consider the GNSS, GNSS signal, GNSS position, UE position, TA value and / or the first type of RA resources to be invalid. If the timer is not in operation or expires, the first condition may be met. If the timer is in operation, the first condition may not be met.

[0789] The indication (or parameter) may be an indication of GNSS. The indication (or parameter) may be configured when, for example, the indication (or parameter) is present in the NTN configuration. The indication (or parameter) may not be configured when, for example, the indication (or parameter) is not present in the NTN configuration. The indication (or parameter) may be configured when, for example, the indication (or parameter) is set to true, enabled or available in the NTN configuration. The indication (or parameter) may not be configured when, for example, the indication (or parameter) is set to false, not enabled or not available in the NTN configuration.

[0790] The indication (or parameter) may be provided in a dedicated signal and / or a common signal. The indication (or parameter) may be provided for a UE, a group of UEs, or all UEs in the same cell. The indication (or parameter) may be provided for a cell or a group of cells. The indication (or parameter) may be provided in system information, a radio resource control (RRC) message, a media access control (MAC) control element (CE), and / or downlink control information (DCI). The indication (or parameter) may be provided or associated with RA resources, GNSS information, and / or NTN information.

[0791] Power Mode

[0792] In one example, the first condition may be (based on / related to) whether the UE is in a power saving mode. If the UE is in a power saving mode, the first condition may be satisfied. If the UE is not in a power saving mode, the first condition may not be satisfied.

[0793] Availability / recognition of UE location / GNSS location / TA values

[0794] In one example, the first condition may be (based on) user consent for positioning. If the UE does not have user consent for positioning, the first condition may be satisfied. If the UE has user consent for positioning, the first condition may not be satisfied.

[0795] In one example, the first condition may be (based on / related to) a positioning mechanism. If the UE cannot perform positioning, the first condition may be satisfied. If the UE can perform positioning, the first condition may not be satisfied.

[0796] In one example, the first condition may be (based on / related to) the availability of the UE location / position. The first condition may be satisfied if the UE does not have / acquire / know its location / position. The first condition may not be satisfied if the UE has / acquires / knows its location / position. The first condition may be satisfied if the UE cannot use the serving satellite position and / or its own position, e.g., to pre-compensate for transmission delays. The first condition may not be satisfied if the UE can use the serving satellite position and / or its own position, e.g., to pre-compensate for transmission delays.

[0797] In one example, the first condition may be (based on / related to) the availability of a GNSS position. If the UE does not have / acquire / know its GNSS position, the first condition may be satisfied. If the UE has / acquires / knows its GNSS position, the first condition may not be satisfied.

[0798] In one example, the first condition may be (based on / related to) the availability of a TA value. The first condition may be satisfied if the UE does not have / obtain / know its TA value. The first condition may not be satisfied if the UE has / obtains / knows its TA value. For example, the TA value may be a timing advance to be pre-compensated by the UE due to a UE-next generation Node B (gNB) round trip time (RTT) in an NTN.

[0799] Validity of NTN information and / or GNSS information

[0800] In one example, the first condition may be (based on / related to) the validity of the NTN information and / or the GNSS information. If the NTN information and / or the GNSS information becomes / is invalid, the first condition may be satisfied. If the NTN information and / or the GNSS information becomes / is valid, the first condition may not be satisfied.

[0801] The validity of the NTN information and / or GNSS information may be maintained by a timer (e.g., T430). The NTN information and / or GNSS information may become invalid when the timer is not in operation or expires. The timer may be started, for example, for the length of the duration indicated by the NW. The timer may be started, for example, at a specific time indicated by the NW. The UE may start or restart the timer in response to receiving the timer or being configured with the timer.

[0802] Pre-compensation for TA value, UE-gNB RTT and / or frequency shift (ability)

[0803] In one example, the first condition may be (based on / related to) a capability of the UE. The first condition may be (based on / related to) a capability for (or whether the UE is able to) pre-compensate for a TA value. The first condition may be (based on / related to) a capability for (or whether the UE is able to) pre-compensate for or calculate a UE-gNB RTT. The first condition may be (based on / related to) a capability for (or whether the UE is able to) maintain UL synchronization. The first condition may be (based on / related to) a capability for (or whether the UE is able to) pre-compensate for frequency shift. If the UE does not have the capability, the first condition may be satisfied. If the UE has the capability, the first condition may not be satisfied.

[0804] In one example, the first condition may be (based on / related to) whether the UE can pre-compensate for, for example, a transmission delay on the serving link. The transmission delay may be a (two-way) transmission delay between an uplink time synchronization reference point and a serving satellite. The uplink time synchronization reference point is where the downlink (DL) and UL are in a state with N TA，偏移 The point at which the frame is aligned given an offset. The first condition may be met if the UE cannot pre-compensate for, for example, a transmission delay on the serving link. The first condition may not be met if the UE can pre-compensate for, for example, a transmission delay on the serving link.

[0805] Causes / Purpose / Trigger of RA

[0806] In one instance, the first condition may be (based on / related to) the triggering of the RA procedure. The first condition may be (based on) the purpose / reason / reason / purpose of the RA procedure. If the RA procedure is triggered by the first cause, the first condition may be met. If the RA procedure is triggered by the second cause (or not triggered by the first cause), the first condition may not be met. The first cause and / or the second cause may (at least) be (or include): initial access, synchronous reconfiguration, UL synchronization, request for UL resources, beam failure recovery (BFR), and / or system information (SI) request. The initial access may be or include RRC connection establishment, RRC connection recovery and / or RRC connection reconstruction. The synchronous reconfiguration may be or include handover (HO), conditional handover (CHO), primary cell (PCell) / primary secondary cell (PSCell) change and / or secondary cell (SCell) / secondary cell group (SCG) addition.

[0807] RRC Status

[0808] In one example, the first condition may be (based on / related to) the current RRC state. If the UE is in the first RRC state, the first condition may be satisfied. If the UE is in the second RRC state (or not in the first RRC state), the first condition may not be satisfied. The RRC state may be or include an RRC idle state / mode, an RRC inactive state / mode, and / or an RRC connected state / mode.

[0809] Availability of parameters (e.g., TA-related parameters)

[0810] In one example, the first condition may be (based on / related to) whether the UE can receive, acquire, calculate, derive and / or determine a parameter. The parameter may be an ephemeris parameter for a serving satellite. The parameter may be The parameters can be The parameter can be Delay 共同 (t). The parameter can be TA 共同 TA 共同漂移 ,t 纪元 and / or TA 共同漂移变化 The parameter can be ta-Common, ta-CommonDrift and / or ta-CommonDriftVariant and / or t 纪元. The parameter may be a parameter specified and / or used in section 4.2 of TS38.213 ([9] 3GPP TS 38.213 V17.5.0). The parameter may be a common TA value. The parameter may be a cell-specific TA value. The parameter may be a UE-specific TA value (which is calculated by the UE). The parameter may be a parameter received in NTN-Config as specified in TS38.331 ([4] 3GPP TS 38.331 V17.5.0). The first condition may be met if the UE cannot receive, obtain, calculate, derive and / or determine the parameter. The first condition may not be met if the UE can receive, obtain, calculate, derive and / or determine the parameter.

[0811] The current design of RA may not be feasible for non-GNSS UEs. For example, the current design of RA assumes that the UE can pre-compensate the TA and / or frequency shift based on the UE position obtained via GNSS, which cannot be achieved by the non-GNSS UE. In order to support non-GNSS UEs (e.g., second type UEs) in the NTN, a new type of RA (e.g., second type RA) different from the current design of RA (e.g., first type RA) will be required to consider different characteristics between the second type UE and the first type UE, such as the ability to pre-compensate timing and frequency offsets.

[0812] In general, the NW may provide appropriate RA resources (or configurations) to the UE, for example, based on information provided by the UE (e.g., capability information). For example, when the NW detects that the UE is a first type UE and / or a UE with GNSS capability, the NW will provide the UE with first type RA resources. For example, after initial access, the UE enters the RRC connected state and connects to the first cell. The UE may indicate its capabilities for GNSS to the NW. The NW will then provide RA resources based on the capabilities. For UEs with GNSS capability, the NW will provide the UE with (dedicated) first type RA resources, for example, for reconfiguration with synchronization, CHO, BFR.

[0813] However, it is also possible that the applicability of RA resources depends on a certain UE state that may change from time to time. For example, the UE may move to an indoor area. The UE may lose connection to a GNSS satellite. The UE may turn off GNSS operation for power saving. After receiving the RA resources, the UE will not or may not receive GNSS signals and / or perform GNSS operations, for example before / after / during the RA procedure. The UE may not know its own position and / or may not pre-compensate the TA value / transmission delay, for example before / after / during the RA procedure. For example, before / after / during the RA procedure, the UE will meet the first condition. For the case where the NW configures a dedicated RA resource (e.g., a first type RA) to the UE (e.g., for CHO, for BFR), the UE state may change so that the UE will become unable to perform RA (e.g., switching, CHO, BFR) using the first type RA resource because the configured RA resource is (or becomes) not applicable to the UE. The UE may be a first type UE at a first timing and become a second type UE at a second timing.

[0814] To support GNSS-independent mechanisms in NTN, some enhancements to PRACH transmissions will be introduced for UL pre-compensation in case of reduced GNSS availability or accuracy. New types of RAs may be defined for non-GNSS UEs (in addition to the traditional types of RAs for GNSS UEs). It is assumed that a first type of RA resources (for UEs with GNSS) and a second type of RA resources (for UEs without GNSS) will be defined for NTN. In addition, even for UEs with GNSS capabilities, the UE location may not always be available because the GNSS status may change from time to time.

[0815] In one example, after initiation of the RA procedure, if the UE has obtained the UE position by GNSS, it may select the first type of RA resources for the RA procedure. During the RA procedure, if the GNSS state of the UE is lost, the RA procedure may fail if the UE continues to use the first type of RA resources without GNSS.

[0816] To solve the problem, the UE may perform a first action in response to a first condition. If the first condition is met, the UE may perform the first action. If the first condition is not met, the UE may not perform the first action. If the first condition is not met, the UE may perform a second action. The UE may check the first condition and / or determine whether to perform the first action and / or the second action in response to a first event. When / if the first event occurs / after the first event occurs, the UE may check the first condition, perform the first action, and / or perform the second action. The first action may be a fallback action. The second action may be a traditional action in response to the first event.

[0817] The first event can be one or more of the following:

[0818] -UE receives an RRC message (e.g., RRCReconfiguration);

[0819] -UE receives PDCCH command;

[0820] - The UE receives a handover command or indication triggering a handover or CHO;

[0821] -UE receives dedicated RA resources (e.g., RACH-ConfigDedicated);

[0822] -UE triggers / initiates RRC connection procedure;

[0823] -UE triggers / initiates RA procedure;

[0824] -UE performs handover or CHO;

[0825] -UE performs reconfiguration with synchronization;

[0826] -UE performs conditional reconfiguration evaluation;

[0827] -UE requests system information;

[0828] -UE detects beam failure;

[0829] -UE performs BFR;

[0830] -UE selects (a set of) RA resources;

[0831] -UE transmits Msg1 or MSGA;

[0832] - Expiration of a timer (e.g., ra-ResponseWindow, msgB-ResponseWindow, ra-ContentionResolutionTimer, T430, T304).

[0833] The first action can be one or more of the following:

[0834] -UE does not initiate the RRC connection procedure;

[0835] -UE does not initiate RA procedure;

[0836] -UE considers the failure of RRC connection;

[0837] -UE considers the RA procedure to have failed;

[0838] -UE considers failure of reconfiguration with synchronization;

[0839] -UE considers radio link failure;

[0840] -UE stops / aborts the ongoing RRC connection procedure;

[0841] -UE stops / aborts the ongoing RA procedure;

[0842] - The UE performs a fallback during an ongoing RA procedure;

[0843] - The UE initiates an RRC connection procedure, e.g. without using the RA resources provided in the first event;

[0844] -UE initiates contention-based (CB) RA procedure;

[0845] -UEs use common RA resources;

[0846] - The UE does not use dedicated RA resources;

[0847] - The UE does not use the RA resources provided in the first event;

[0848] -UE releases / discards the first type RA resources;

[0849] -UE releases / discards dedicated RA resources;

[0850] -UE obtains the second type of RA resources;

[0851] - UE (re)acquires system information (e.g., System Information Blocks (SIBs) related to NTN or GNSS);

[0852] -UE transmits the indication to NW;

[0853] -UE performs GNSS positioning operations and / or GNSS measurements;

[0854] -UE requires GNSS signal / information;

[0855] -UE suspends UL / DL transmission;

[0856] -UE considers UL synchronization loss;

[0857] -UE initiates RRC connection re-establishment procedure;

[0858] -UE performs cell reselection;

[0859] -UE releases radio resources;

[0860] -UE discards the measurement report;

[0861] -UE resets the MAC entity;

[0862] -UE clears the Hybrid Automatic Repeat Request (HARQ) buffer;

[0863] -UE suspends radio bearers;

[0864] -UE enters RRC idle state;

[0865] -UE stops timers (e.g., validity timer, RA timer); and / or

[0866] - The UE (re)starts a timer (eg, RRC timer, failure timer).

[0867] The common RA resource may be a cell-specific RA resource. The common RA resource may be provided (or configured) by system information. The common RA resource may be contention-based. The common RA resource may not be dedicated to the UE. The common RA resource may be a first type RA. The common RA resource may be a second type RA.

[0868] The UE may transmit an indication to the NW to indicate that the first condition is met or occurs. The UE may transmit an indication to the NW to indicate that a failure occurs during an RA procedure or an RRC connection procedure. The UE may transmit an indication to the NW to indicate that the GNSS information becomes invalid. The UE may transmit an indication to the NW to indicate that the first type of RA resources becomes unavailable. The UE may transmit an indication to the NW to indicate that the UE becomes, switches to, or is considered to be a second type of UE. The UE may transmit an indication to the NW to request a second type of RA resources. The indication may be an RRC message, a MAC CE, and / or UE assistance information.

[0869] The second action can be one or more of the following:

[0870] - The UE initiates an RRC connection procedure, e.g. using the RA resources provided in the first event;

[0871] - The UE initiates the RA procedure, e.g. using the RA resources provided in the first event;

[0872] - The UE initiates the CFRA procedure, e.g. using the RA resources provided in the first event;

[0873] -UE stops a timer (e.g. a failure timer); and / or

[0874] - The UE (re)starts a timer (eg, a validity timer).

[0875] For example, if the GNSS state is lost during the RA procedure, the UE may determine to reselect another cell based on the inability to select the second type of RA resource. For example, if the GNSS state is lost during the RA procedure, the UE may determine to perform RA resource reselection (e.g., select the second type of RA) and / or re-initiate the RA procedure.

[0876] In the following four examples, the UE may initiate a first RA procedure in the first cell. The first RA procedure may be triggered for handover, initial access, RRC reconfiguration (with synchronization), RRC connection establishment, RRC connection recovery UL / DL data arrival, request for UL resources and / or UL synchronization. In response to initiating the first RA procedure, when initiating the first RA procedure and / or after, the UE may determine (e.g., evaluate, measure) whether the GNSS state of the UE is qualified. The UE may determine (e.g., evaluate, measure) the GNSS state of the UE after initiation of the first RA procedure or RA resource (set) selection. The UE may determine (e.g., evaluate, measure) the GNSS state of the UE during the RA procedure. The UE may determine (e.g., evaluate, measure) the GNSS state of the UE before RA resource (set) selection and / or RA preamble transmission (e.g., Msg1, MSGA transmission). If the strength of the GNSS signal is lower than or equal to a threshold, the GNSS signal is unavailable and / or the GNSS information is invalid, the GNSS state of the UE may be unqualified. If the strength of the GNSS signal is higher than or equal to a threshold, the GNSS signal is available and / or the GNSS information is valid, the GNSS state of the UE may be qualified. The determination of the GNSS state of the UE may include evaluating, measuring, deriving, calculating, monitoring and / or comparing, for example, the GNSS signal (strength) and / or GNSS information received by the UE. In response to initiating a first RA procedure, when initiating the first RA procedure and / or after, the UE may determine whether the second type of RA resources are available. The UE may determine the second type of RA resources after the initiation of the first RA procedure or the RA resource (set) selection. If the first cell is configured with the second type of RA resources (for the UE), the second type of RA resources may be available. If the first cell is not configured with the second type of RA resources (for the UE), the second type of RA resources may not be available. If the UE is provided with the second type of RA resources (in the first cell), the second type of RA resources may be available. If the UE is not provided with the second type of RA resources (in the first cell), the second type of RA resources may not be available.

[0877] In a first instance, the UE may determine that the GNSS state of the UE is qualified. The first cell may be configured with a first type of RA resource. The first cell may not be configured with a second type of RA resource. The UE may continue the first RA procedure (e.g., perform RA resource selection). The UE may select the first type of RA resource based on the GNSS state of the UE being qualified.

[0878] In a second example, the UE may determine that the GNSS state of the UE is qualified. The first cell may be configured with a first type of RA resource. The first cell may be configured with a second type of RA resource. The UE may continue the first RA procedure (e.g., perform RA resource selection). The UE may select the first type of RA resource, for example, based on the GNSS state of the UE being qualified. The UE may select the second type of RA resource based on the second type of RA resource being usable earlier than the first type of RA resource.

[0879] In a third instance, the UE may determine that the GNSS state of the UE is unqualified. The first cell may be configured with the first type of RA resources. The first cell may not be configured with the second type of RA resources. If the UE determines that the GNSS state of the UE is unqualified, the UE may determine whether the second type of RA resources are available. If the UE determines that the second type of RA resources are unavailable, the UE may not continue the first RA procedure. The UE may perform (at least) the following actions based on (at least) the GNSS state of the UE is unqualified and / or the second type of RA resources are unavailable: stop the first RA procedure, initiate an RRC re-establishment procedure, reselect the second cell, select the second cell, and / or initiate a second RA procedure on the second cell. The second cell is configured with the second type of RA resources.

[0880] In a fourth example, the UE may determine that the GNSS state of the UE is unqualified. The first cell may be configured with a first type of RA resource. The first cell may be configured with a second type of RA resource. If the UE determines that the GNSS state of the UE is unqualified, the UE may determine whether the second type of RA resource is available. If the UE determines that the second type of RA resource is available, the UE may continue the first RA procedure (e.g., perform RA resource selection). The UE may select the second type of RA resource based on the UE's GNSS state being unqualified and / or the second type of RA resource being available.

[0881] The above examples may be combined in whole or in part. In the above examples, the first type RA resource is different from the second type RA resource. The first type RA resource and the second type RA resource may include different time and / or frequency resources for the UE to perform RA and / or transmit RA preambles. The first type RA resource may be designed for a UE with GNSS. The second type RA resource may be designed for a UE without GNSS.

[0882] Additionally and / or alternatively, the UE may initiate a first RA procedure on the first cell. The first RA procedure may be triggered for handover, initial access, RRC reconfiguration (with synchronization), RRC connection establishment, RRC connection recovery UL / DL data arrival, request for UL resources and / or UL synchronization. In response to initiating the first RA procedure, when initiating the first RA procedure and / or after, the UE may determine that the GNSS state of the UE is qualified. The UE may determine the GNSS state of the UE after initiation of the first RA procedure or RA resource (set) selection. The UE may determine the GNSS state of the UE before RA resource (set) selection and / or RA preamble transmission (e.g., Msg1, MSGA transmission). If the strength of the GNSS signal is higher than or equal to a threshold, the GNSS signal is available and / or the GNSS information is valid, then the GNSS state of the UE may be qualified. The determination of the GNSS state of the UE may include evaluating, measuring, deriving, calculating, monitoring and / or comparing, for example, GNSS signals (strength) and / or GNSS information received by the UE. The first cell may be configured with a first type of RA resource. The first cell may be configured with a second type of RA resource. The UE may continue the first RA procedure (e.g., perform RA resource selection). The UE may select the first type of RA resource, for example, based on the UE's GNSS state being qualified. The UE may select RA resources (e.g., RA resource sets, RA preamble groups, RA preambles, PRACH opportunities, and / or physical uplink shared channel (PUSCH) opportunities) based on the first type of RA resources. The UE may transmit Msg1 or MSGA after RA resource selection. In response to transmitting Msg1 or MSGA, the UE may monitor whether the PDCCH has a NW response. The UE may determine that the UE's GNSS state becomes unqualified during the first RA procedure. The UE may determine that the UE's GNSS state becomes unqualified after, at, at, and / or in response to RA resource selection, Msg1 transmission, MSGA transmission, receiving a NW response, and / or not receiving a NW response (e.g., after expiration of a RA timer). In response to (determining) that the UE's GNSS state becomes / becomes unqualified, the UE may perform (at least) the following actions. The UE may perform (at least) the following actions based on (at least) the UE's GNSS status being unqualified (during the first RA procedure) and / or the second type of RA resources being available. The UE may stop the first RA procedure. The UE may initiate the second RA procedure. The UE may not stop the first RA procedure. The UE may perform (and / or fall back / fall back to) RA resource selection in the first RA procedure or the second RA procedure. The UE may (re)select the second type of RA resources, for example, in the first RA procedure or the second RA procedure. The first type of RA resources are different from the second type of RA resources. The first type of RA resources and the second type of RA resources may include different time and / or frequency resources for the UE to perform RA and / or transmit RA preambles.The first type RA resources may be designed for UEs with GNSS. The second type RA resources may be designed for UEs without GNSS.

[0883] Additionally and / or alternatively, the UE may reuse the power ramp counter when the UE performs the first action. In the following description and / or throughout the present disclosure, the power ramp counter may be PREAMBLE_POWER_RAMPING_COUNTER. The UE may not (re)set the power ramp counter to 1 when the UE performs the first action. The UE may set the power ramp counter to the stored value when the UE performs the first action.

[0884] Additionally and / or alternatively, the NW may (always) provide two types of RA resources, e.g., for the first type UE, for BFR. The NW may provide both the first type RA resources and the second type RA resources to the UE if (at least) one or more of the following second conditions are met:

[0885] - the UE is a first UE;

[0886] -NW triggers handover or CHO procedure for UE;

[0887] -NW provides a handover command or indication to change the serving cell of the UE;

[0888] -NW provides dedicated RA resources to UE;

[0889] -NW provides RA resources for BFR to UE;

[0890] - The NW detects a first condition of the UE; and / or

[0891] - The NW receives indication or assistance information from the UE.

[0892] The UE may determine which type of RA resource to use based on the applicability of the RA resource. The applicability may depend on a certain UE state (and / or capability), for example, a first condition. For example, if a first type RA (and a second type RA) is configured to the UE and the first type RA is (or becomes) not applicable to the UE, the UE may use the second type RA (if the second type RA is applicable to the UE). If a second type RA (and a first type RA) is configured to the UE and the second type RA is (or becomes) not applicable to the UE, the UE may use the first type RA (if the first type RA is applicable to the UE). If all configured RA resources are not applicable, the UE may perform the first action (specified above).

[0893] Additionally and / or alternatively, when the first type UE uses the second type RA resources, the first type UE may or may not perform (some of) the first procedure. When the first type UE camps / selects / reselects a cell that does not have the first type RA resources, the first type UE may or may not perform (some of) the first procedure. As in the current specifications ([2] 3GPP TS 38.300 V17.5.0, [3] 3GPP TS 38.321 V17.5.0, [4] 3GPP TS 38.331 V17.5.0), the first procedure may be performed by a UE with GNSS. The first procedure may be related to GNSS, UE position and / or TA pre-compensation. The first procedure may be performed for initial access. The first procedure may be or include TA reporting, TA pre-compensation and / or UE-gNB RTT estimation.

[0894] The first type UE may determine whether to execute the first procedure based on whether the NW (or cell) provides the first type RA resources. If the NW (or cell) provides the first type RA resources, the first type UE may execute the first procedure. If the NW (or cell) does not provide the first type RA resources, the first type UE may not execute the first procedure.

[0895] The first type UE may determine whether to execute the first procedure based on whether the first type UE selects / uses the second type RA resource. If the first type UE selects / uses the first type RA resource, the first type UE may execute the first procedure. If the first type UE selects / uses the second type RA resource, the first type UE may not execute the first procedure.

[0896] The first type UE may determine whether to execute the first procedure based on whether the first type UE camps / selects / reselects a cell with the first type RA resources. If the first type UE camps / selects / reselects a cell with the first type RA resources, the first type UE may execute the first procedure. If the first type UE camps / selects / reselects a cell without the first type RA resources, the first type UE may not execute the first procedure.

[0897] In addition and / or alternatively, the first type UE may or may not indicate to the NW whether it will use the first type RA resources, for example after initial access. If the first condition is met, the first type UE may indicate to the NW that it will not use the first type RA resources. The first type UE may indicate to the NW that the first condition is met. The first type UE may provide auxiliary information related to the first condition and / or the purpose of the RA resources to the NW. The auxiliary information may be a UE state related to the first condition. The auxiliary information may be (or include): selection of RA resources, GNSS state of the UE, perception of the UE location, and / or the like (e.g., preference for RA resources). The first type UE may report auxiliary information in the event of a change in UE state, a change in the serving cell, initial access, triggering / completing the RA procedure / when this time / at this moment / in response thereto. The first type UE may report auxiliary information via an RRC message and / or a MAC CE.

[0898] One or more of the embodiments, concepts, methods, aspects and / or examples described above and herein may be combined in whole or in part.

[0899] The UE may receive configurations related to NTN and / or GNSS, for example, via system information and / or RRC messages. The UE may receive NTN information via SIB3, SIB19, SIB31 and / or SIBxx as in [7]R2-2306954. The UE may receive RA configurations and / or RA resources via system information (e.g., SIB1) and / or RRC messages (e.g., RRCReconfiguration, RRCResume, RRCSetup). The UE may receive configurations related to cell (re)selection, for example, via system information and / or RRC messages. The UE may receive parameters and / or indications for cell (re)selection via MIB, SIB1, SIB2, SIB3, SIB4, SIB5, SIB19, SIB31 and / or new SIBs related to NTN.

[0900] Throughout the present disclosure, "handover / CHO" may correspond to, may be supplemented with and / or may be replaced by "reconfiguration with synchronization". The handover / CHO procedure may correspond to, may be supplemented with and / or may be replaced by an RRC reconfiguration procedure and / or a reconfiguration procedure with synchronization. The handover / CHO procedure may be triggered after the UE receives an RRC reconfiguration message (e.g., RRCReconfiguration). In response to the RRC reconfiguration message (e.g., RRCReconfiguration), the handover / CHO procedure may be completed after the UE transmits an RRC message (e.g., RRCReconfigurationComplete). The handover / CHO procedure may be completed after the UE camps on / links to the target cell. The handover / CHO procedure may be completed after a handover failure occurs (e.g., a reconfiguration failure with synchronization occurs, T304 expires).

[0901] The UE may be in a cell of the NTN. The UE may be connected to a cell of the NTN. The UE may pre-occupy a cell of the NTN. The UE may be connected to a LEO, GEO, MEO, HEO and / or HAPS. Throughout this disclosure, a cell may be / may refer to an NTN cell. A cell may be a serving cell. A cell may be a non-serving cell. A cell may be a neighboring cell and / or a target cell.

[0902] UE may be referred to as UE, RRC layer of UE, or MAC entity of UE.

[0903] The UE may be a New Radio (NR) device. The UE may be a NR Light device. The UE may be a Long Term Evolution (LTE) device. The UE may be a Narrowband Internet of Things (NB-IoT) device. The UE may be an enhanced Machine Type Communication (eMTC) device. The UE may be an under-capable device. The UE may be a mobile phone. The UE may be a wearable device. The UE may be a sensor. The UE may be a fixed device.

[0904] The network may be a network node. The network may be a base station. The network may be an access point. The network may be an evolved Node B (eNB). The network node may be a gNB. The network may be a gateway.

[0905] Embodiments, concepts, methods, aspects and / or examples of the invention are described below.

[0906] See also Fig. 9 , with respect to such and other concepts, systems and methods of the present invention, a method 1000 for a UE includes receiving an RRC message including a first type of RA resources from a network (step 1002), and in response to receiving the RRC message, determining to use the first type of RA resources based on not satisfying a first condition and determining to perform a fallback action based on satisfying the first condition (step 1004).

[0907] In various embodiments, the UE is a GNSS capable UE.

[0908] In various embodiments, the first type of RA resources is for GNSS capable UEs.

[0909] In various embodiments, the first condition is that GNSS (signal) is unavailable.

[0910] In various embodiments, the first condition is that the UE location is not available.

[0911] In various embodiments, the first condition is that the GNSS position is not available or valid.

[0912] In various embodiments, the first condition is that the validity time timer is not running.

[0913] In various embodiments, the fallback action is that the UE does not initiate the RA procedure using the first type RA.

[0914] In various embodiments, the fallback action is the UE releasing the first type RA resources.

[0915] In various embodiments, the fallback action is the UE transmitting an indication to the NW.

[0916] Return to reference Figure 3 and 4 In one or more embodiments from the perspective of the UE, the apparatus 300 includes a program code 312 stored in a memory 310 of the transmitter. The CPU 308 may execute the program code 312 to: (i) receive an RRC message including a first type of RA resource from the network; and (ii) in response to receiving the RRC message, determine to use the first type of resource based on not satisfying the first condition and determine to perform a fallback action based on satisfying the first condition. In addition, the CPU 308 may execute the program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

[0917] The first type RA resources and the second type RA resources may be provided in different NTN cells. Coexistence between the first type UE (e.g., UE with GNSS) and the second type UE (e.g., UE without GNSS) in a cell or between cells should be considered. The first type RA resources may be provided on the first cell. The second type RA resources may be provided on the second cell. The first type RA resources may or may not be provided on the second cell. The second type RA resources may or may not be provided on the first cell. If a UE (e.g., a second type UE) is unable to use a specific type of RA (e.g., the first type RA) for example for initial access, although the UE may pre-occupy a cell that only provides a specific type of RA (and / or does not provide a type of RA that the UE can use), it cannot perform RA access to the cell.

[0918] To solve the problem, the UE may (determine whether to) access, camp on and / or (re)select to the NTN cell (in the RRC idle state and / or the RRC inactive state) based on (at least) GNSS capability, the first condition (as described above) and / or whether a specific type of RA (resource) is supported / provided / configured in the NTN cell. For example, if the UE is a specific type of UE (e.g., a first type UE, a second type UE), the UE may (determine or not) access / camp on / select / reselect the cell based on (whether) the cell supports / provides / configures at least a type of RA that the UE can use, (whether) at least a specific type of RA is supported / provided / configured in the cell, and / or, for example, whether the UE (or a specific type of UE) is prohibited (or allowed to access) NW indication.

[0919] A first type UE may access / pre-occupy / select / reselect a cell with a first type RA (resource). A first type UE may access / pre-occupy / select / reselect a cell with a second type RA (resource). A first type UE may access / pre-occupy / select / reselect a cell without a first type RA (resource). A first type UE may use a first type RA (resource) or a second type RA (resource). If the UE is a first type UE, the UE may use a first type RA. If the UE is a first type UE, the UE may or may not use a second type RA. If the UE is a first type UE, the UE may access / pre-occupy / select / reselect a cell with a first type RA (resource). If the UE is a first type UE, the UE may access / pre-occupy / select / reselect a cell with a second type RA (resource). If the UE is a first type UE, the UE may access / pre-occupy / select / reselect a cell without a first type RA (resource). The UE may perform a determination (e.g., checking whether one or more of the above conditions are met) based on one or more of the above items.

[0920] A second type UE may access / pre-occupy / select / reselect a cell with a second type RA (resource). A second type UE may not access / pre-occupy / select / reselect a cell without a second type RA (resource). A second type UE may use a second type RA (resource). A second type UE may not use a first type RA (resource). If the UE is a second type UE, the UE may use a second type RA. If the UE is a second type UE, the UE may or may not use a first type RA. If the UE is a second type UE, the UE may access / pre-occupy / select / reselect a cell with a first type RA (resource). If the UE is a second type UE, the UE may access / pre-occupy / select / reselect a cell with a second type RA (resource). If the UE is a second type UE, the UE may not access / pre-occupy / select / reselect a cell without a second type RA (resource). The UE may perform a determination based on one or more of the above items (e.g., checking whether one or more of the above conditions are met).

[0921] A cell with a first type of RA (resource) may be a cell configured with a first type of RA (resource). A cell with a first type of RA (resource) may be a cell configured with a second type of RA (resource). A cell with a first type of RA (resource) may be a cell not configured with a second type of RA (resource). A cell with a first type of RA (resource) may not be a cell not configured with a first type of RA (resource). A cell with a first type of RA (resource) may be a cell configured for a first type of UE. A cell with a first type of RA (resource) may be a cell indicated for a first type of UE.

[0922] The cell with the second type of RA (resource) may be a cell configured with the second type of RA (resource). The cell with the second type of RA (resource) may be a cell configured with the first type of RA (resource). The cell with the second type of RA (resource) may be a cell not configured with the first type of RA (resource). The cell with the second type of RA (resource) may not be a cell not configured with the second type of RA (resource). The cell with the second type of RA (resource) may be a cell configured for the second type of UE. The cell with the second type of RA (resource) may be a cell indicated for the second type of UE.

[0923] The first type of cell may be a cell having a first type of RA (resource). The first type of cell may be a cell indicated to have GNSS (capability). The first type of cell may be a cell indicated to prioritize a first type of UE.

[0924] The second type of cell may be a cell having a second type of RA (resource). The second type of cell may be a cell indicated as not having GNSS (capability). The second type of cell may be a cell indicated as prioritizing a second type of UE.

[0925] The first type cell or the second type cell may be determined, configured or indicated by the NW via system information or an RRC message. The UE may detect and / or determine whether the cell is a first type cell or a second type cell based on RA resources. The UE may detect and / or determine whether the cell is a first type cell or a second type cell based on an NW indication (e.g., a prohibition bit).

[0926] Alternatively and / or in addition, the cell type distinction may be based on (at least) a first condition. The first type UE and the second type UE may be distinguished by (at least) the first condition. For example, the first type cell may be associated to (or correspond to) the first type UE. The second type cell may be associated to (or correspond to) the second type UE. The association (or correspondence) may be based on the first condition. The first type UE may be a UE that does not satisfy the first condition. The second type UE may be a UE that satisfies the first condition. If the UE is a first type UE, the UE may use a first type RA. If the UE is a second type UE, the UE may use a second type RA. If the UE is a first type UE, the UE may or may not use a second type RA. If the UE is a second type UE, the UE may or may not use a first type RA.

[0927] Additionally and / or alternatively, the first type UE may determine to pre-occupy / select / reselect the second type cell based on (at least) the first condition. If the first condition is met / when the first condition is met / in response to meeting the first condition, the first type UE may pre-occupy / select / reselect the second type cell. The first type UE may be deemed to be, is and / or becomes a second type UE based on (at least) the first condition. The first type UE may determine to pre-occupy / select / reselect the second type cell based on other criteria and / or parameters for cell selection and / or reselection, as specified in TS 38.304 ([8] 3GPP TS38.304 V17.5.0). The first type UE may determine to prioritize the first type cell (or the second type cell) based on (at least) the first condition. If the first condition is not met / when the first condition is not met / in response to not meeting the first condition, the first type UE may prioritize the second type cell. If the first condition is met / when the first condition is met / in response to meeting the first condition, the first type UE may prioritize the second type cell. The first type UE may check the first condition before, after, or in response to performing a cell (re)selection. The first type UE may check the first condition before, after, or in response to entering an RRC idle state.

[0928] For example, if GNSS signals are not available, e.g. based on measured radio conditions, network indication, the first type UE may camp on / select / reselect a second type cell. If GNSS is not available when the first type UE performs measurements on a neighboring cell, the first type UE camps on / selects / reselects a second type cell. If GNSS is not available when the first type UE performs cell (re)selection, the first type UE camps on / selects / reselects a second type cell.

[0929] For example, if the first type cell is not detected and / or available, the first type UE may camp on / select / reselect a second type cell. If the first type cell is not detected when the first type UE performs measurements on neighboring cells, the first type UE camps on / selects / reselects a second type cell. If the first type cell is not detected when the first type UE performs cell (re) selection, the first type UE camps on / selects / reselects a second type cell.

[0930] For example, if the first type UE has not yet acquired (or derived) a valid TA value, UE position and / or GNSS position / when the first type UE has not yet acquired (or derived) a valid TA value, UE position and / or GNSS position / in response to the first type UE not having acquired (or derived) a valid TA value, UE position and / or GNSS position, the first type UE may camp on / select / reselect a second type cell. The first type UE may receive NTN information from the NW (e.g., via system information, via an RRC reconfiguration message). The first type UE may acquire (or derive) the UE position via GNSS. The first type UE may pre-compensate the TA value based on the NTN information and the UE position. The first type UE may fail to receive the NTN information, acquire (or derive) the UE position and / or pre-compensate the TA value. If the first type UE fails to receive NTN information, obtain (or derive) UE position and / or pre-compensated TA value / when the first type UE fails to receive NTN information, obtain (or derive) UE position and / or pre-compensated TA value / in response to the first type UE failing to receive NTN information, obtain (or derive) UE position and / or pre-compensated TA value, the first type UE camps / selects / reselects the second type cell when the first type UE is in RRC idle / inactive state. If the first type UE fails to receive NTN information, obtain (or derive) UE position and / or pre-compensated TA value / when the first type UE fails to receive NTN information, obtain (or derive) UE position and / or pre-compensated TA value / in response to the first type UE failing to receive NTN information, obtain (or derive) UE position and / or pre-compensated TA value, the first type UE camps / selects / reselects the second type cell when the first type UE performs measurements on neighboring cells. If the first type UE fails to receive NTN information, obtain (or derive) the UE position and / or pre-compensated TA value / when the first type UE fails to receive NTN information, obtain (or derive) the UE position and / or pre-compensated TA value / in response to the first type UE failing to receive NTN information, obtain (or derive) the UE position and / or pre-compensated TA value, the first type UE pre-occupies / selects / reselects a second type of cell when the first type UE performs cell (re)selection.

[0931] For example, if the first type UE has acquired (or derived) a valid TA value, UE position and / or GNSS position / when the first type UE has acquired (or derived) a valid TA value, UE position and / or GNSS position / in response to the first type UE having acquired (or derived) a valid TA value, UE position and / or GNSS position, the first type UE may prioritize the first type cell (for cell reselection). The first type UE may receive NTN information from the NW (e.g., via system information, via an RRC reconfiguration message). The first type UE may acquire (or derive) the UE position via GNSS. The first type UE may pre-compensate the TA value based on the NTN information and the UE position. If the first type UE has valid NTN information, UE position and / or TA value / when the first type UE has valid NTN information, UE position and / or TA value / in response to the first type UE having valid NTN information, UE position and / or TA value, the first type UE prioritizes the first type cell (for cell reselection) when the first type UE is in an RRC idle / inactive state. If the first type UE has valid NTN information, UE location and / or TA value / when the first type UE has valid NTN information, UE location and / or TA value / in response to the first type UE having valid NTN information, UE location and / or TA value, the first type UE prioritizes the first type cell when the first type UE performs cell (re)selection.

[0932] Additionally and / or alternatively, a UE (e.g., a specific type of UE, a first type of UE, a second type of UE) may be prevented from accessing / camping / selecting / reselecting a first type of cell based on one or more of the following examples. A cell may provide a (NW) indication to indicate whether a UE (e.g., a specific type of UE, a first type of UE, a second type of UE) is allowed to camp / select / reselect a cell. The (NW) indication may be a prohibition bit. The (NW) indication may indicate whether the UE is prohibited by the cell.

[0933] For example, based on the cell ranking criteria, offset and / or priority, the second type UE may be prevented from camping / selecting / reselecting the first type cell. The UE may receive one or more parameters related to cell (re)selection and / or the first type cell. The UE may apply the parameters for cell reselection criteria and / or measurement rules. The UE may apply the parameters for access restriction.

[0934] For example, based on a (NW) indication, such as a prohibition bit, the second type UE may be prevented from camping / selecting / reselecting the first type cell. The (NW) indication (e.g., prohibition bit) may be configured or provided in system information (e.g., MIB, SIB1). The (NW) indication (e.g., prohibition bit) may be one of the current prohibition bits specified in TS 38.304 ([8] 3GPP TS 38.304 V17.5.0). The (NW) indication (e.g., prohibition bit) may be a prohibition bit different from the current prohibition bits specified in TS 38.304 ([8] 3GPP TS 38.304 V17.5.0). The (NW) indication (e.g., prohibition bit) may be a specific prohibition bit for GNSS and / or NTN. The (NW) indication (e.g., prohibition bit) may be applied to or used by the second type UE. The (NW) indication (e.g., prohibition bit) may not be applied to or used by the first type UE. The (NW) indication (eg, a prohibition bit) may be applied to or used by NTN UEs. The (NW) indication (eg, a prohibition bit) may not be applied to or used by non-NTN UEs.

[0935] Based on the (NW) indication (e.g., the prohibition bit), when the cell state is indicated as "not prohibited", "not reserved" for operator use, not "true" for other uses, and / or not "true" for future use, the second type UE considers this cell as a candidate during the cell selection and / or cell reselection procedure. Based on the (NW) indication (e.g., the prohibition bit), when the cell state is indicated as "prohibited", "reserved" for operator use, "true" for other uses, and / or "true" for future use, the second type UE does not consider this cell as a candidate during the cell selection and / or cell reselection procedure. If the (NW) indication (e.g., the prohibition bit) is omitted or not configured, the second type UE considers this cell as a candidate during the cell selection and / or cell reselection procedure. If the (NW) indication (e.g., the prohibition bit) exists or is configured, the second type UE does not consider this cell as a candidate during the cell selection and / or cell reselection procedure. If the (NW) indication (e.g., a barred bit) is present or configured, the second type UE treats this cell as if the cell state is "barred". When the cell state is indicated as "barred" or treated as if the cell state is "barred", the second type UE may not select / reselect this cell.

[0936] For the second type of cell, the (NW) indication (e.g., the prohibition bit) may be indicated as "not prohibited", "not reserved", not "true" for other uses, and / or not "true" for future use for the operator. For the first type of cell, the (NW) indication (e.g., the prohibition bit) may be indicated as "prohibited", "reserved", "true" for other uses, and / or "true" for future use for the operator. For the second type of cell, the (NW) indication (e.g., the prohibition bit) may not be configured. For the first type of cell, the (NW) indication (e.g., the prohibition bit) may be configured. The second type UE may consider the second type of cell as a candidate during the cell selection and / or cell reselection procedure. The second type UE may not consider the first type of cell as a candidate during the cell selection and / or cell reselection procedure. The second type UE may exclude the first type of cell as a candidate during the cell selection and / or cell reselection procedure. The second type UE may exclude the first type of cell from the candidate list.

[0937] Additionally and / or alternatively, if the second type UE does not camp on, select, reselect, access and / or connect to the second type cell / when the second type UE does not camp on, select, reselect, access and / or connect to the second type cell / in response to the second type UE not camping on, selecting, reselecting, accessing and / or connecting to the second type cell, the second type UE may perform the first action (as described above). If the second type UE may not camp on, select, reselect, access and / or connect to the second type cell / when the second type UE may not camp on, select, reselect, access and / or connect to the second type cell / in response to the second type UE may not camp on, select, reselect, access and / or connect to the second type cell (e.g., if the UE regards the cell as barred / when the UE regards the cell as barred / in response to the UE regarding the cell as barred), the second type UE may perform the first action. If the second type UE camps on, selects, reselects, accesses and / or connects to the first type cell / when the second type UE camps on, selects, reselects, accesses and / or connects to the first type cell / in response to the second type UE camping on, selecting, reselecting, accessing and / or connecting to the first type cell, the second type UE may perform a first action. If the second type UE does not have available second type RA resources / when the second type UE does not have available second type RA resources / in response to the second type UE not having available second type RA resources, the second type UE may perform a first action. If the second type UE is not receiving the second type RA resources / when the second type UE is not receiving the second type RA resources / in response to the second type UE not receiving the second type RA resources, the second type UE may perform the first action. The first action may be a fallback action and / or a fault handling.

[0938] For example, the UE may receive RA resources and / or RA configuration from system information of the first cell. The UE may initiate an RA procedure for initial access to the first cell. The UE may initiate an RRC connection establishment procedure to the first cell. The RA procedure may be triggered by the RRC connection establishment procedure. In response to the triggering of the RA procedure and / or the RRC connection establishment procedure, the UE may check / detect / determine whether the first cell is a second type cell. In response to the triggering of the RA procedure and / or the RRC connection establishment procedure, the UE may check / detect / determine whether the second type RA resources are available. The UE may check / detect / determine that the first cell is not a second type cell. The RA resources and / or RA configuration may not be or include the second type RA resources. The UE may then perform cell reselection. The UE may not trigger the RA procedure. The UE may stop the RA procedure. The UE may stop the RRC connection establishment procedure. The UE may regard the RRC connection establishment procedure as a failure. The UE may be a second type UE. The UE may be in an RRC idle state.

[0939] For example, the UE may receive a dedicated RA resource from an RRC reconfiguration message in a first cell. The UE may initiate an RA procedure for handover to a second cell. The UE may initiate an RRC reconfiguration procedure to the second cell. The RA procedure may be triggered by / for an RRC reconfiguration procedure. In response to the triggering of the RA procedure and / or the RRC reconfiguration procedure, the UE may check / determine whether the dedicated RA resource is appropriate. If the UE is a second type UE and the dedicated RA resource is a second type RA resource, the dedicated RA resource is deemed appropriate. If the UE is a second type UE and the dedicated RA resource is a first type RA resource, the dedicated RA resource is deemed inappropriate. If the RA resource is inappropriate (for performing handover), the UE may not perform the RRC reconfiguration procedure and / or the RA procedure. The UE may stop the RRC reconfiguration procedure and / or the RA procedure. The UE may perform cell reselection. The UE may consider the RRC reconfiguration procedure as a failure. If the RA resource is inappropriate (for performing handover), the UE may use a common RA resource other than the dedicated RA resource provided in the RRC reconfiguration message. The UE may perform the RA procedure and / or the RRC reconfiguration procedure using the common RA resource. The UE may be in an RRC connected state.

[0940] For example, the UE may initiate an RRC connection reestablishment procedure in the RRC connected state. The UE may perform cell selection during the RRC connection reestablishment procedure. The UE may not select or detect the second type of cell. The UE may enter the RRC idle state in response to not selecting or detecting the second type of cell. The UE may be a second type UE.

[0941] The RA design for non-GNSS UEs (e.g., second type UEs) may not be backward compatible. In order to provide access for both the first type UE (e.g., GNSS UE) and the second type UE (e.g., non-GNSS UE), two types of RA resources need to be provided (separately). According to TR 38.821 ([1] 3GPP TR 38.821 V16.1.0), RA resources may be separated based on the GNSS capabilities of the UE. The conventional design of RA (e.g., first type RA) provides access for UEs with GNSS capabilities. The new type of RA (e.g., second type RA) provides access for UEs without GNSS capabilities. If the UE has GNSS capabilities, it may only use the conventional design of RA (e.g., first type RA). If the UE does not have GNSS capabilities, it may only use the new type of RA (e.g., second type RA). However, such RA differentiation based on GNSS capabilities results in resource inefficiency because the UE may only use part of the RACH resources (e.g., a UE with GNSS capabilities cannot utilize the new type of RA (e.g., second type RA)).

[0942] To solve the problem, RA (resource) differentiation should not be (at least) (only) based on the GNSS capability of the UE. UEs with GNSS capability should be allowed to use new types of RA (resources) (e.g., second type RA). For example, a UE with GNSS capability but unable to obtain its position and / or unable to pre-compensate TA and / or frequency shift (e.g., based on its UE position) can use the second type RA and / or not use the first type RA. Alternatively and / or in addition, a UE without GNSS capability but able to obtain its position and / or able to pre-compensate TA and / or frequency shift (e.g., based on its UE position) can use the first type RA and / or not use the second type RA.

[0943] The first type UE may use the second type RA (resource). The first type UE may use the first type RA (resource) or the second type RA (resource). The second type UE may use the second type RA (resource). The second type UE may not use the first type RA (resource). The second type RA (resource) may be shared by the first type UE and the second type UE.

[0944] The first type UE may use / determine to use / determine whether to use the second type RA (resource) based on the first condition. For example, based on the first condition, the UE with GNSS capability may use the RA resources (or RA scheme (second type RA resources)) for UEs without GNSS capability. If the first condition is met / when the first condition is met / in response to satisfying the first condition, the first type UE may (determine) to use the second type RA (resource). If the first condition is not met / when the first condition is not met / in response to not satisfying the first condition, the first type UE may not (or determine not to) use the second type RA (resource). If the first condition is not met / when the first condition is not met / in response to not satisfying the first condition, the first type UE may (determine) to use the second type RA (resource). If the first condition is not met / when the first condition is not met / in response to not satisfying the first condition, the first type UE may (determine) to use the second type RA (resource). If the first condition is met / when the first condition is not met / in response to satisfying the first condition , the first type UE may not (or determine not to) use the second type RA (resource). If the first condition is not met / when the first condition is not met / in response to the first condition not being met, the first type UE may (determine) to use the first type RA (resource). Regardless of the first condition, the first type UE may use the first type RA (resource). The first type UE may prioritize the first type RA (resource) over the second type RA (resource). The first type UE may check the first condition before or after triggering the RA procedure. The first type UE may check the first condition during the RA procedure. The first type RA (resource) may be provided on the cell. The first type RA (resource) may not be provided on the cell. The second type RA (resource) may be provided on the cell.

[0945] Alternatively and / or in addition, RA (resource) distinction may be based on (at least) a first condition. A first type UE and a second type UE may be distinguished by (at least) a first condition. For example, a first type RA may be associated with (or correspond to) a first type UE. A second type RA may be associated with (or correspond to) a second type UE. The association (or correspondence) may be based on a first condition. A first type UE may be a UE that satisfies the first condition. A second type UE may be a UE that does not satisfy the first condition. A first type UE may be a UE that does not satisfy the first condition. A second type UE may be a UE that satisfies the first condition. If the UE is a first type UE, the UE may use a first type RA. If the UE is a second type UE, the UE may use a second type RA. If the UE is a first type UE, the UE may or may not use a second type RA. If the UE is a second type UE, the UE may or may not use a first type RA.

[0946] For example, regardless of the first condition, the second type UE may not (be allowed to) use the first type RA. Alternatively and / or in addition, the second type UE may determine to use the first type RA (resource) based on the first condition. If the first condition is met / when the first condition is met / in response to meeting the first condition, the second type UE may (determine) to use the first type RA (resource). If the first condition is not met / when the first condition is not met / in response to not meeting the first condition, the second type UE may not (or determine not) use the first type RA (resource). If the first condition is not met / when the first condition is not met / in response to not meeting the first condition, the second type UE may (determine) use the first type RA (resource). If the first condition is met / when the first condition is met / in response to meeting the first condition, the second type UE may not (or determine not) use the first type RA (resource). Regardless of the first condition, the second type UE may use the second type RA (resource). The second type UE may check the first condition before or after triggering the RA procedure. The second type UE may check the first condition during the RA procedure. The second type RA (resource) may be provided on the cell. The second type RA (resource) may not be provided on the cell. The first type RA (resource) may be provided on the cell.

[0947] In one example, if GNSS signals are not available, the first type UE may use the second type RA (resources). GNSS signals being unavailable (for the UE) may be that the UE is unable to receive GNSS signals, cannot detect GNSS signals, the GNSS signals received by the UE are not qualified / sufficient / strong enough (e.g., to obtain a GNSS position), and / or the UE is unable to perform GNSS operations (e.g., GNSS measurements). The first type UE may trigger an RA procedure and / or an RRC connection procedure. For example, based on measuring radio conditions, network indications, the first type UE may check whether GNSS is available. If GNSS is not available before / after triggering the RA procedure and / or the RRC connection procedure, the first type UE uses the second type RA (resources). If GNSS is not available after or in response to triggering the RA procedure and / or the RRC connection procedure (for a duration), the first type UE uses the second type RA (resources). If GNSS is available before / after triggering the RA procedure and / or the RRC connection procedure, the first type UE uses the first type RA (resources). If GNSS is available after or in response to triggering a RA procedure and / or an RRC connection procedure (within a duration), the first type UE uses the first type RA (resource).

[0948] In one example, if the first type RA (resources / format / configuration) is not provided and / or available, for example, for initial access, the first type UE may use the second type RA (resources). The first type UE may trigger an RA procedure and / or an RRC connection procedure. The first type UE may check whether the first type RA (resources) is configured and / or available. If the first type RA (resources) is not configured or unavailable before / after triggering the RA procedure and / or the RRC connection procedure, the first type UE uses the second type RA (resources). If the next PRACH opportunity is too far away, for example, exceeding the duration, the first type RA (resources) may not be available. If the first type RA (resources) is configured (and available) before / after triggering the RA procedure and / or the RRC connection procedure, the first type UE uses the first type RA (resources).

[0949] In one instance, if the first type UE has not yet acquired (or derived) a valid TA value, UE position and / or GNSS position, the first type UE may use a second type RA (resource). The first type UE may receive NTN information from the NW (e.g., via system information, via an RRC reconfiguration message). The first type UE may acquire (or derive) the UE position via GNSS. The first type UE may pre-compensate the TA value based on the NTN information and the UE position. The first type UE may fail to receive NTN information, acquire (or derive) the UE position, and / or pre-compensate the TA value. The first type UE may trigger an RA procedure and / or an RRC connection procedure. If the first type UE fails to receive NTN information, acquire (or derive) the UE position and / or pre-compensate the TA value, the first type UE uses a second type RA (resource) in response to triggering the RA procedure and / or the RRC connection procedure.

[0950] In one example, the first type UE may use the second type RA (resources) based on the RA trigger and / or the RRC state. The first type UE may trigger the RA procedure and / or the RRC connection procedure. If the RA procedure and / or the RRC connection procedure are used for initial access, the first type UE uses the second type RA (resources). If the RA procedure and / or the RRC connection procedure are not used for initial access, the first type UE uses the first type RA (resources). If the RA procedure and / or the RRC connection procedure are used for handover, the first type UE uses the second type RA (resources). If the RA procedure and / or the RRC connection procedure are not used for handover, the first type UE uses the first type RA (resources).

[0951] If the UE is a second type UE, the UE may use the second type RA (resource). If the UE is a second type UE, the UE may not use the first type RA (resource). If the UE is a first type UE, the UE may use the second type RA (resource). If the UE is a first type UE, the UE may use the first type RA (resource).

[0952] In one example, the second type UE may not use RA (resources). The second type UE has GNSS capability. The second type UE is configured / equipped with a GNSS device / receiver. The second type UE does not receive / acquire / derive / have (sufficient) GNSS signals or information. The second type UE satisfies the first condition. The second type UE is not able to pre-compensate the TA value.

[0953] In one example, the second type UE may use the second type RA (resource). The second type UE has GNSS capability. The second type UE is configured / equipped with a GNSS device / receiver. The second type UE does not receive / acquire / derive / have (sufficient) GNSS signals or information. The second type UE satisfies the first condition. The second type UE is not able to pre-compensate the TA value.

[0954] In one example, for operation with GNSS, the UE may use the first type of RA (resources). For operation with GNSS, the UE may use the second type of RA (resources). For operation without GNSS, the UE may use the second type of RA (resources). For operation without GNSS, the UE may not use the first type of RA (resources).

[0955] For some situations (e.g., handover, reconfiguration with synchronization, BFR), the NW may provide dedicated RA resources for the UE. If the RA resource distinction between the first type RA and the second type RA is based on (at least) a first condition that may change from time to time (e.g., GNSS state, knowledge of UE location, GNSS signal strength) and which may not be known to the NW (at least not synchronized), the NW may not know how to provide dedicated RA resources to the UE, e.g., whether to provide the first type RA or the second type RA.

[0956] To solve the problem, the NW may, for example, provide (dedicated) second type RA resources to the first type UE (always) on the NTN cell. For initial access, since the NW does not know whether the UE has its own location (for example, whether the UE is a first type UE or a second type UE), the NW may provide the UE (always) with second type RA resources. The NW may not provide (common) first type RA resources on the NTN cell. The NW may provide (common) second type RA resources on the NTN cell. The NW may provide (common) first type RA resources on the NTN cell. The NW may provide (dedicated) second type RA resources on the NTN cell. The NW may provide (dedicated) second type RA resources to the UE. The NW may not provide (common) second type RA resources on the NTN cell. The NW may not provide (common) first type RA resources on the NTN cell.

[0957] To solve the problem, the UE may provide assistance information related to the first condition to the NW. The assistance information may be a UE state related to the first condition. The assistance information may be (or include): GNSS state of the UE, perception of the UE location, and / or the like (e.g., preference for RA resources). The UE may report assistance information in case of / when / at this moment / in response to a change in UE state, a change in serving cell, initial access, triggering / completing an RA procedure. The UE may be a first type UE.

[0958] The NW shall provide the NTN assistance information to the UE via system information (e.g., SIB19 in NR, SIB31 in LTE) or a dedicated RRC message (e.g., RRCReconfiguration). The system information may be NTN specific system information. A dedicated RRC message (e.g., RRCReconfiguration) may be provided in a handover procedure. The NW may broadcast the NTN assistance information to the UE in the serving cell. The NW may provide the NTN assistance information to the UE when handing over the UE from the serving cell to the target cell.

[0959] The NTN assistance information may be satellite information of a serving cell and / or a neighboring cell. The NTN assistance information and / or satellite information may be or include an NTN configuration (e.g., NTN-Config). The NTN configuration (e.g., NTN-Config) may include (at least) ephemeris information (e.g., ephemerisInfo), common TA information (e.g., ta-Info), K offset (e.g., cellSpecificKoffset), k mac (e.g., kmac), epoch time (e.g., epochTime), validity duration (e.g., ntn-UlSyncValidityDuration), and / or cell reference location (e.g., referenceLocation). The UE may use the NTN configuration (e.g., NTN-Config) to access a serving cell, adjust / compensate for TA (e.g., for a serving cell), and / or perform measurements (e.g., on a serving cell, on a neighboring cell).

[0960] The ephemeris information may be ephemeris information of a (serving) satellite. The ephemeris information may include / indicate a position, velocity and / or orbit of a (serving) satellite. The common TA information may be, include and / or be referred to as a common TA value (e.g., ta-Common), a drift rate of the common TA (e.g., ta-CommonDrift), and / or a drift rate variation of the common TA (e.g., ta-CommonDriftVariant). The common TA information may be a parameter used to derive the common TA, for example, the TA between the satellite and a reference point. The K offset may be K_offset, ... 小区，偏移 or K 偏移 The K offset may be a cell-specific scheduling offset. The K offset may be used to derive K 小区，偏移 The parameter kmac can be kmac or kmac. mac k mac may be the satellite specific scheduling offset. kmac may be the TA between the reference point and the gNB. k mac may be the number of nodes used to derive k mac Parameters.

[0961] In addition, the NW may provide RA resources and / or configurations to the UE. The NW may provide common RA resources and / or dedicated RA resources. Common RA resources may be cell-specific RA resources. Common RA resources may be provided (or configured) by system information. Common RA resources may be contention-based. Common RA resources may not be dedicated to the UE. Common RA resources may be 2-step RA or 4-step RA. Common RA resources and / or configurations may be RACH-ConfigCommon, RACH-ConfigCommonTwoStepRA. Dedicated RA resources may be provided (or configured) by an RRC reconfiguration message or a PDCCH command. Dedicated RA resources may be contention-free. Common RA resources may be dedicated to the UE. Dedicated RA resources may be 2-step RA or 4-step RA. Dedicated RA resources and / or configurations may be RACH-ConfigDedicated.

[0962] The UE shall maintain the TA value used for UL / DL transmissions. The (full) TA value is the T as specified in TS 38.211 (

[10] 3GPP TS 38.211). TA . T TA NW-based configuration is done by N TA 、N TA，偏移 , and / or Composition. TA，偏移 Configured by NW, for example via n-TimingAdvanceOffset or a default value. TA Indicated or adjusted by TA command. In the terrestrial network (TN), the UE uses N TA and N TA，偏移 Calculate T TA The UE will receive N via RA response (e.g. RAR, MSGB) during the RA procedure. TA The UE will receive N from the timing advance command MAC CE in RRC connected mode TA For RACH-free handover, N may be indicated to the UE via an RRC reconfiguration message (eg, RRCConnectionReconfiguration). TA Zero or the same as the primary timing advance group (PTAG).

[0963] In NTN, in addition to N TA and N TA，偏移 In addition, UE calculates / derives the TA of and is derived from the common TA information for the satellite (serving the cell). And The UE performs pre-compensation based on the ephemeris information using the UE position and satellite position. It is a common TA value, a satellite-specific TA value and / or a cell-specific TA value. is a UE specific TA value. The UE will receive the NTN configuration and pre-compensated TA value (e.g., T TA ). The UE may calculate the UE-gNB RTT as the TA value (e.g., T TA ) and kmac. The UE shall delay the start of the RA timer and / or DRX timer by the UE-gNB RTT. The UE shall report the TA value (e.g., T TA ) and / or UE location.

[0964] For non-GNSS UEs in NTN, the UE will not be able to obtain / derive its position via GNSS. And without GNSS and the UE's position, the UE cannot calculate the UE-specific TA value in NTN (e.g. ) and / or pre-compensated TA value (e.g., T TA ). As a result, the UE may lose UL synchronization and may not be able to perform any transmission to the NW.

[0965] To solve the problem, the UE may use the first information provided by the NW to calculate the TA parameter in the NTN and / or the UE-specific TA value (e.g., ). The UE may pre-compensate the TA value (eg, T TA ). The UE may not calculate the UE-specific TA value based on the GNSS position (obtained by the UE itself) (e.g. ) and / or pre-compensated TA value (e.g., T TA ). The UE may not have a (valid) GNSS position. The NW may provide the first information to the UE. The first information may be related to the UE position and / or the UE-specific TA. The first information may be specific to the UE. The first information may be the UE position. Throughout the present disclosure, the following may be interchangeable: UE positioning, UE position, UE position, GNSS position, GNSS positioning. The first information may be a UE-specific TA value and / or a TA parameter. The UE-specific TA value may be, consist of, include or correspond to The transmission delay on the service link, T TA, UE-gNB RTT, extended common TA and / or new TA value. The TA parameter may be used to derive and / or calculate a UE-specific TA value. The first information may be derived, calculated, estimated and / or obtained by the NW. The first information may be provided / transmitted / updated via an RRC message, a MAC CE and / or a DCI. The first information may be provided / transmitted / updated during a handover procedure. The first information may be provided / transmitted / updated in an RRC connected state.

[0966] To solve the problem, the UE may receive the UE position, UE-specific TA value and / or TA parameters from the NW. The UE may not have GNSS. The UE may be a second type UE. The UE without GNSS may receive the UE position and / or TA value from the NW.

[0967] For example, the UE may provide a location measurement value to the NW. The UE may perform an UL transmission to the NW before (or after) receiving the first information from the NW, for example, for positioning measurements. The NW may perform measurements for UE positioning, for example, via reception of the UL transmission. The UE and / or the NW may perform positioning operations, for example, DL-Time Difference of Arrival (TDOA), UL-TDOA, multi-RTT, as specified in TS 38.305 (

[11] 3GPP TS 38.305 V17.5.0). The NW may determine, derive, calculate and / or estimate the UE location, for example, based on a UE positioning mechanism (e.g., in TS 38.305 (

[11] 3GPP TS 38.305 V17.5.0)) and / or NW verification for UE location (e.g., in Rel-18 NTN). The positioning operation may be triggered by the UE and / or the NW. The NW may, for example, calculate a UE-specific TA value based on the UE location. If the UE is a second type UE, the NW may determine, derive, calculate and / or estimate the UE location. If a UE request and / or configuration is received, the NW may determine, derive, calculate and / or estimate the UE location. The NW may provide the first information to the UE based on (at least) UL transmission, positioning measurement, positioning operation / mechanism, UE location and / or UE-specific TA value.

[0968] For example, if the UE is a second type UE, the NW may provide the first information. If the UE is not a first type UE, the NW may provide the first information. If the UE is a first type UE, the NW may not provide the first information. If the UE is not a second type UE, the NW may not provide the first information. If, for example, a UE request for the first information is received, the NW may provide the first information. If, for example, a UE configuration / capability indicating no GNSS is received, the NW may provide the first information.

[0969] For example, the NW may provide the first information to the UE for performing the RA procedure. The UE may receive the first information during (or before) the RA procedure. The UE may perform the RA procedure using the first information. The first information may be configured with / equipped with (dedicated) RA resources.

[0970] For example, the UE may receive the first information during a handover procedure. The first information may be configured / provided in a handover command. The first information may be configured / provided in system information (e.g., NTN-specific system information). The first information may be configured / provided with an NTN configuration (e.g., NTN-Config). The first information may be configured / provided with a cell configuration.

[0971] For example, the UE may receive the first information in RRC connection mode. The first information may be configured / provided in a MAC CE (e.g., a timing advance command MAC CE). The first information may be associated with a timer. The UE may start or restart the timer in response to receiving the first information. The NW may start or restart the timer in response to transmitting the first information. The timer may be a valid time timer (e.g., T430). The timer may be a TA timer (e.g., timeAlignmentTimer). The timer may be associated with each UE. The timer may be associated with each TAG.

[0972] If the first information is valid or has been received, the UE may start or restart the TA timer (e.g., timeAlignmentTimer) when receiving the timing advance command MAC CE. For example, when receiving the timing advance command MAC CE, if the UE does not have the (valid) first information, the UE may not start or restart the TA timer (e.g., timeAlignmentTimer). For example, when receiving the timing advance command MAC CE, if the UE does not have the (valid) first information, the UE may stop the TA timer (e.g., timeAlignmentTimer). For example, when receiving the timing advance command MAC CE, if the UE does not have the (valid) first information, the UE may regard the TA timer (e.g., timeAlignmentTimer) as expired.

[0973] For example, the UE may use the first information to derive, calculate and / or estimate The transmission delay on the service link, T TAand / or UE-gNB RTT. The UE may use the first information to pre-compensate the TA. The UE may use the first information to perform UL transmission and / or measurement. The UE may use the first information on the serving cell, the target cell and / or the neighboring cell. The UE may use the first information to adjust the start or length of the timer (e.g., ra-ResponseWindow, msgB-ResponseWindow, ra-ContentionResolutionTimer, HARQ-RTT-TimerDL-NTN, HARQ-RTT-TimerUL-NTN). The UE may use the first information to perform UL synchronization. The UE may use the first information to maintain the TA value. The UE may calculate T based on the current formula in TS 38.211 (

[10] 3GPP TS 38.211 V17.5.0) and / or TS 38.213 ([9] 3GPP TS38.213 V17.5.0) TA The UE may calculate T based on, for example, a new formula specific to the second type of UE. TA .

[0974] For example, when the last provided first information becomes invalid, the NW can update the first information. The NW can update the first information based on a timer (specified above). The NW can update the first information in response to the expiration of the timer, when the timer expires, or before the timer expires. The NW can update the first information based on a UE request. The UE can transmit a request and / or an indication in response to the expiration of the timer, when the timer expires, or before the timer expires. The UE can transmit a request and / or an indication in response to an event and / or a threshold (e.g., a distance threshold). The event can be based on the motion and / or speed mode of the UE. The request and / or indication can be transmitted in an RRC message and / or a MAC CE. When the UE enters, pre-occupies, and / or links to a new cell / if the UE enters, pre-occupies, and / or links to a new cell, the NW can update the first information. When the UE enters and / or changes / transitions to the RRC connected state / if the UE enters and / or changes / transitions to the RRC connected state, the NW can update the first information.

[0975] The UE may indicate (to the NW) that it needs to calculate (or derive) TA parameters (e.g. ), transmission delay and / or UE-gNB RTT. The UE may request the NW to provide the first information (e.g., when the UE moves or in response to the UE moving). For example, in response to receiving the request (or indication), the NW may initiate a positioning mechanism (or operation) for the UE. For example, if the NW has received the request (or indication), and / or the NW has derived the (current) UE location and / or the first information for the UE, the NW may provide the first information to the UE.

[0976] For example, if the UE does not receive the first information, the UE may calculate (or derive) the TA parameter (eg, ), transmission delay and / or UE-gNB RTT. If the UE is able to calculate (or derive) the TA parameters (e.g., ), transmission delay and / or UE-gNB RTT, the NW may not provide the first information to the UE. If the UE is capable of calculating (or deriving) the TA parameters (e.g., ), transmission delay and / or UE-gNB RTT, the UE may calculate (or derive) the TA parameter (e.g., ), transmission delay and / or UE-gNB RTT.

[0977] If the UE does not receive the first information, the UE may assume (or consider) a TA parameter (eg, ), transmission delay and / or UE-gNB RTT is 0. If the UE does not receive the first information, the UE may not perform pre-compensation of the TA. If the UE does not receive the first information, the UE may not use RA resources and / or configuration requiring pre-compensation of the TA.

[0978] For example, for the same serving cell, for the same RRC connection, the NW may not update the first information. When the UE links to a new cell and / or enters an RRC connected state, thereafter or in response thereto, the NW may provide the first information to the UE. When the UE is in the same cell and / or the same RRC connected state, the NW may not provide another first information. The UE may receive the first information and derive T TA The NW may provide the NW via a MAC CE and / or RA response after providing the first information. TA UE can receive N TA And adjust T TA .

[0979] The UE may (or may not) receive a TA command (eg, a timing advance command MAC CE). The UE may use the TA command to derive the first TA parameter (eg, N TA ). The UE may use the first information to derive a second TA parameter (e.g., The first TA parameter and the second TA parameter may be different parameters. The UE may calculate a TA value (eg, T TA The UE may calculate a TA value (eg, T TA ).

[0980] The NW may provide the first information to the UE for handover (or CHO) to the target cell. The UE may use the first information to calculate (or derive) the TA parameters of the target cell (e.g., ), transmission delay and / or UE-gNB RTT. The handover may not be a HO without RACH. The handover may be a CHO. The UE may perform a RA procedure for the handover. The UE may use the first information for a RA procedure to the target cell.

[0981] For example, when changing / transitioning to the RRC inactive / idle state, thereafter and / or in response thereto, the UE may retain the first information. When changing / transitioning to the RRC inactive / idle state, thereafter and / or in response thereto, the UE may not release or discard the first information. When changing / transitioning to the RRC inactive / idle state, thereafter and / or in response thereto, the UE may release or discard the first information.

[0982] See also Fig.10 , with respect to such and other concepts, systems and methods of the present invention, a method 1010 for a UE includes initiating an RA procedure in a first cell (step 1012), determining whether second type RA resources are available in response to initiating the RA procedure (step 1014), and during the RA procedure, in response to determining that the GNSS status of the UE is unqualified: if the second type RA resources are available, select the second type RA resources, or if the second type RA resources are not available, perform cell selection or reselection (step 1016).

[0983] In various embodiments, a first cell is provided with a first type of RA resources.

[0984] In various embodiments, if the strength of the GNSS signal is less than or equal to a threshold, the GNSS signal is not available and / or the GNSS information is invalid, then the GNSS status of the UE is unqualified.

[0985] In various embodiments, the cell selection or reselection is performed by at least one or more of: stopping the RA procedure, initiating an RRC re-establishment procedure, selecting a second cell, and / or initiating another RA procedure on the second cell using the second type of RA resources.

[0986] In various embodiments, the method further includes selecting the first type RA resource or the second type RA resource in response to determining that the GNSS status of the UE is qualified.

[0987] Return to reference Figure 3 and 4In one or more embodiments from the perspective of the UE, the apparatus 300 includes program code 312 stored in a memory 310 of the transmitter. The CPU 308 may execute the program code 312 to: (i) initiate an RA procedure in a first cell; (ii) determine whether a second type of RA resource is available in response to initiating the RA procedure; and (iii) during the RA procedure, in response to determining that the GNSS status of the UE is unqualified: if the second type of RA resource is available, select the second type of RA resource, or if the second type of RA resource is not available, perform cell selection or reselection. In addition, the CPU 308 may execute the program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

[0988] See also Fig.11 , with respect to such and other concepts, systems and methods of the present invention, a method 1020 for a UE includes receiving a first type of RA resource and a second type of RA resource from a network (step 1022), initiating an RA procedure (step 1024), in response to initiating the RA procedure, selecting the first type of RA resource based on a GNSS status of the UE being qualified (step 1026), determining during the RA procedure that the GNSS status of the UE becomes unqualified (step 1028), and in response to the determination that the GNSS status of the UE becomes unqualified: stopping the RA procedure, initiating or re-initiating the RA procedure, and / or selecting or reselecting a second type of RA resource (step 1030).

[0989] In various embodiments, if the strength of the GNSS signal is less than or equal to a threshold, the GNSS signal is not available and / or the GNSS information is invalid, then the GNSS status of the UE is unqualified.

[0990] In various embodiments, the determination is performed in response to transmitting Msg1 or MSGA.

[0991] In various embodiments, the first type of RA resources is used for UEs with GNSS.

[0992] In various embodiments, the second type of RA resources are used for UEs without GNSS.

[0993] Return to reference Figure 3 and 4In one or more embodiments from the perspective of the UE, the apparatus 300 includes program code 312 stored in a memory 310 of the transmitter. The CPU 308 may execute the program code 312 to: (i) receive a first type of RA resource and a second type of RA resource from a network; (ii) initiate an RA procedure; (iii) in response to initiating the RA procedure, select the first type of RA resource based on the UE's GNSS status being qualified; (iv) determine during the RA procedure that the UE's GNSS status becomes unqualified; and (v) in response to the determination that the UE's GNSS status becomes unqualified: stop the RA procedure, initiate or re-initiate the RA procedure, and / or select or re-select the second type of RA resource. In addition, the CPU 308 may execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or otherwise herein.

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

[0995] 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.

[0996] 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 different 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 frequencies. In some aspects, parallel channels can be established based on pulse positions or offsets. 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 frequencies, pulse positions or offsets, and time hopping sequences.

[0997] Those skilled in the art will appreciate 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.

[0998] 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, for convenience, may be referred to herein as "software" or "software modules"), or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled 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.

[0999] 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. The 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. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[1000] 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 a sample order and are not intended to be limited to the specific order or hierarchy presented.

[1001] 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 can 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 a computer-readable storage medium known in the art. An example storage medium can be coupled to a machine such as a computer / processor (for convenience, the machine can 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 can be integrated with a processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user device. In an alternative, the processor and the storage medium can 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 of the various aspects of the present disclosure. In some aspects, a computer program product may include packaging materials.

[1002] 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.

[1003] CROSS-REFERENCE TO RELATED APPLICATIONS

[1004] This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 525,561 filed on July 7, 2023, U.S. Provisional Patent Application No. 63 / 525,564 filed on July 7, 2023, U.S. Provisional Patent Application No. 63 / 525,566 filed on July 7, 2023, and U.S. Provisional Patent Application No. 63 / 527,507 filed on July 18, 2023, each of which is incorporated herein by reference in its entirety.

Claims

1. A method for a user device, characterized in that: include: Initiating a random access procedure in the first cell; determining whether a second type of random access resource is available in response to initiating the random access procedure; During the random access procedure, in response to determining that a global navigation satellite system status of the user equipment is unqualified: If the second type of random access resources are available, selecting the second type of random access resources for the random access procedure; or If the second type of random access resources is not available, cell selection or reselection is performed.

2. The method according to claim 1, characterized in that The first cell is provided with a first type of random access resource.

3. The method according to claim 1, characterized in that The GNSS status of the user equipment is unqualified if the strength of the GNSS signal is lower than or equal to a threshold, the GNSS signal is unavailable and / or the GNSS information is invalid.

4. The method according to claim 1, characterized in that: The cell selection or reselection is performed by at least one or more of the following: Stopping the random access procedure; Initiate a radio resource control re-establishment procedure; Selecting a second cell; and / or Another random access procedure is initiated on the second cell using the second type of random access resources.

5. The method according to claim 1, characterized in that Also includes: In response to determining that the global navigation satellite system status of the user equipment is qualified, selecting a first type of random access resource or the second type of random access resource for the random access procedure.

6. A method for a user device, characterized in that: include: receiving a first type of random access resource and a second type of random access resource from a network; Initiate a random access procedure; In response to initiating the random access procedure, selecting the first type of random access resource based on a global navigation satellite system status of the user equipment being qualified; determining, during the random access procedure, that the global navigation satellite system status of the user equipment becomes unqualified; as well as In response to the determination that the global navigation satellite system status of the user equipment becomes unqualified: Stopping the random access procedure; Initiate or re-initiate the random access procedure; and / or Select or reselect the second type of random access resource.

7. The method according to claim 6, characterized in that The GNSS status of the user equipment is unqualified if the strength of the GNSS signal is lower than or equal to a threshold, the GNSS signal is unavailable and / or the GNSS information is invalid.

8. The method according to claim 6, characterized in that The determination is performed in response to transmitting Msg1 or MSGA.

9. The method according to claim 6, characterized in that The first type of random access resource is used for the user equipment having a global navigation satellite system.

10. The method according to claim 6, characterized in that The second type of random access resource is used for the user equipment not having a global navigation satellite system.

11. A user equipment, 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: Initiating a random access procedure in the first cell; determining whether a second type of random access resource is available in response to initiating the random access procedure; During the random access procedure, in response to determining that a global navigation satellite system status of the user equipment is unqualified: If the second type of random access resources are available, selecting the second type of random access resources for the random access procedure; or If the second type of random access resources is not available, cell selection or reselection is performed.

12. The user equipment according to claim 11, characterized in that The first cell is provided with a first type of random access resource.

13. The user equipment according to claim 11, characterized in that The GNSS status of the user equipment is unqualified if the strength of the GNSS signal is lower than or equal to a threshold, the GNSS signal is unavailable and / or the GNSS information is invalid.

14. The user equipment according to claim 11, characterized in that The cell selection or reselection is performed by at least one or more of the following: Stopping the random access procedure; Initiate a radio resource control re-establishment procedure; Selecting a second cell; and / or Another random access procedure is initiated on the second cell using the second type of random access resources.

15. The user equipment according to claim 11, characterized in that The processor is further configured to execute the program code to: In response to determining that the global navigation satellite system status of the user equipment is qualified, selecting a first type of random access resource or the second type of random access resource for the random access procedure.

Images