Method and device for user equipment timing advance reporting in wireless communication system
By introducing the UE's timing advance reporting mechanism in the wireless communication system, the problem of TA reporting management in the NTN environment is solved, and the performance of NR radio technology in non-terrestrial networks is improved, especially in high-altitude communication platforms and air-to-ground situations. Channel stability and coverage capability.
Patent Information
- Application Number
- CN202211379018.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2021-11-25
- Filing Date
- 2022-11-04
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2042-11-04
AI Technical Summary
In wireless communication systems, it is difficult for the prior art to effectively manage the timing advance (TA) reporting of user equipment (UE) in non-terrestrial network (NTN) environments, resulting in the inadequate resolution of key impacts in channel model definition and deployment situations. Impacts the performance of NR radio technology.
By introducing methods and devices for timing advance reporting of UEs in wireless communication systems, the UE is allowed to properly trigger TA reports based on system information and dedicated signaling configuration in a random access program and RRC connection mode, utilizing TA offset thresholds, using TA offsets and event triggering mechanism to ensure the accuracy and timeliness of TA reports.
Improve the timing relationship and UL time frequency synchronization capabilities of the NR NTN system in high-altitude communication platform and air-to-ground situation, enhance the processing capabilities of long propagation delays and Doppler effects, and improve the signal-to-noise ratio and network of mobile cells. cover.
Smart Images

Figure CN116170839B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to wireless communication networks, and more particularly, to methods and apparatus for User Equipment (UE) Timing Advance (TA) reporting 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 with Internet Protocol (IP) data packet communications. This IP data 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] Provided are a method, system, and device for user equipment (UE) timing advance (TA) reporting in a wireless communication system. The UE can appropriately trigger TA reporting in different configurations through system information (e.g., for random access (RA) procedure, for TA reporting during RA, etc.) and dedicated signaling (e.g., for radio resource control (RRC) connection mode, for event-triggered TA reporting, etc.).
[0005] In various embodiments, with respect to such and other concepts, systems and methods of the present invention, a method for a UE in a wireless communication system includes receiving a first configuration of a TA report, receiving a second configuration of the TA report, and determining whether to trigger a second TA report immediately after receiving the second configuration based on whether the first TA report has been transmitted to a serving cell. BRIEF DESCRIPTION OF THE DRAWINGS
[0006] Figure 1 The drawings show a wireless communication system according to an embodiment of the present invention.
[0007] 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.
[0008] Figure 3is a functional block diagram of a communication system according to an embodiment of the present invention.
[0009] Figure 4 According to an embodiment of the present invention Figure 3 Functional block diagram of the program code.
[0010] Figure 5 is an example case / scenario figure according to an embodiment of the present invention, wherein TA reporting at / during RA procedure is disabled and TA reporting (with first information and / or second information) in RRC connected mode is configured.
[0011] Figure 6 is an example case / scenario figure according to an embodiment of the present invention, wherein TA reporting at / during RA procedure is enabled and TA reporting (with first information or second information) in RRC connected mode is configured.
[0012] Figure 7 is an example situation / scenario illustration according to an embodiment of the present invention, wherein TA reporting at / during an RA procedure is disabled, TA reporting in RRC connected mode is not configured (or not configured), and then TA reporting in RRC connected mode is configured / reconfigured (with first information and / or second information).
[0013] Figure 8 is an example situation / scenario figure according to an embodiment of the present invention, wherein TA reporting at / during a RA procedure is deactivated, TA reporting in RRC connected mode (with second information) is configured, and then TA reporting in RRC connected mode (with first information) is configured / reconfigured.
[0014] Fig. 9 is an example situation / scenario figure according to an embodiment of the present invention, wherein TA reporting at / during an RA procedure is deactivated, TA reporting in RRC connected mode (having first information) is configured, and then TA reporting in RRC connected mode (having second information) is configured / reconfigured.
[0015] Fig.10 is an example case / scenario figure according to an embodiment of the present invention, wherein TA reporting at / during a RA procedure is enabled, TA reporting in RRC connected mode is not configured (or not configured), and then TA reporting in RRC connected mode is configured / reconfigured (with first information and / or second information).
[0016] Fig.11is an example situation / scenario figure according to an embodiment of the present invention, wherein TA reporting at / during a RA procedure is enabled, TA reporting in RRC connected mode (with second information) is configured, and then TA reporting in RRC connected mode (with first information) is configured / reconfigured.
[0017] Fig.12 is an example situation / scenario figure according to an embodiment of the present invention, wherein TA reporting at / during a RA procedure is enabled, TA reporting in RRC connected mode (having first information) is configured, and then TA reporting in RRC connected mode (having second information) is configured / reconfigured.
[0018] Fig.13 is an example case / scenario figure according to an embodiment of the present invention, wherein in the HO command, TA reporting at / during RA procedure is disabled and TA reporting in RRC connected mode (with first information and / or second information) is configured.
[0019] Fig.14 is an example case / scenario figure according to an embodiment of the present invention, wherein in the HO command, TA reporting at / during RA procedure is disabled and TA reporting in RRC connected mode is not configured (or not configured).
[0020] Fig.15 is a flowchart of a UE receiving a second configuration for configuring a TA report in an RRC connected mode according to an embodiment of the present invention.
[0021] Fig.16 is a flowchart of a UE receiving a second configuration for configuring a TA report in an RRC connected mode according to an embodiment of the present invention.
[0022] Fig.17 is a flowchart of a second configuration of a UE receiving a TA report according to an embodiment of the present invention.
[0023] Fig.18 is an example case / scenario figure of a second configuration of a UE receiving a TA report according to an embodiment of the present invention. DETAILED DESCRIPTION
[0024] 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.
[0025] 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.
[0026] 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] RP-201256, “Solution for NR Support of Non-Terrestrial Networks (NTN)”; [2] 3GPP TR 38.821 V16.0.0, “Solution for NR Support of Non-Terrestrial Networks (NTN)”; [3] R2-2111615, “Stage 3 Operational CR of TS 38.321 for Rel-17 NTN”; and [4] R2-2111221, “LS on UE TA Report”. The standards and documents listed above are hereby expressly and completely incorporated herein by reference in their entirety.
[0027] 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 1, 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 on forward link 120 and receive information from AT 116 on reverse link 118. AT 122 communicates with antennas 106 and 108, where antennas 106 and 108 transmit information to AT 122 on forward link 126 and receive information from AT 122 on 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.
[0028] Each group of antennas and / or the area in which they are designed to communicate is often referred to as a sector of the access network. In an embodiment, the antenna groups are each designed to communicate with access terminals in a sector of the area covered by the access network 100.
[0029] In communicating via forward links 120 and 126, the transmit antennas of access network 100 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 that transmits to access terminals randomly dispersed throughout its coverage area using beamforming causes less interference to access terminals in neighboring cells than an access network that transmits to all of its access terminals via a single antenna.
[0030] 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.
[0031] 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.
[0032] 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.
[0033] 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 the 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.
[0034] 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.
[0035] 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.
[0036] 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.
[0037] 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.
[0038] 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.
[0039] 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.
[0040] 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.
[0041] 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.
[0042] 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 (e.g., a keyboard or a keypad), and can output images and sounds through the output device 304 (e.g., 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.
[0043] 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.
[0044] 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.
[0045] 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.
[0046] 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.
[0047] In [1] RP-201256, “Solutions for NR to support Non-Terrestrial Networks (NTN)”, the description of the work items for Non-Terrestrial Networks (NTN) in NR is specified:
[0048] ****************************** Quote starts [1] *****************************
[0049] 3 reasons
[0050] Non-terrestrial networks refer to networks or network segments that use air or space vehicles for transmission:
[0051] ● Space launch vehicles: Satellites (including low earth orbit (LEO) satellites, medium earth orbit (MEO) satellites, geostationary orbit (GEO) satellites and highly elliptical orbit (HEO) satellites)
[0052] ●Aerial vehicles: High altitude platforms (HAPs), including unmanned aerial systems (UAS), including lighter-than-air UAS (LTA), heavier-than-air UAS (HTA), all operating at altitudes typically between 8km and 50km, quasi-stationary.
[0053] In 3GPP TS 22.261 approved by SA#82, use cases for 5G satellite integration and corresponding service requirements have been identified as a result of work item "5GSAT". This will address mobile broadband needs in unserved / underserved areas as well as public safety needs, maritime (3GPP TS 22.119 "Maritime communication services via 3GPP systems"), aircraft connectivity for satellite access, and orbital communication service requirements.
[0054] Since RAN#76, two activities have been carried out on NR to support non-terrestrial networks.
[0055] ● The first activity, FS_NR_nonterr_nw (see RP-171450), studied channel models for non-terrestrial networks to define deployment scenarios, parameters and identify key potential impacts on NR. The RAN-led work started in RAN#76 and was completed in RAN#80. The results are reflected in TR 38.811.
[0056] ● The second activity, FS_NR_NTN_solutions (see RP-190710), defines and evaluates solutions to the key impacts identified in the first activity. The work led by RAN3 started in RAN#80 and is scheduled to be completed in RAN#86. The results are reflected in TR38.821 (RP-193062).
[0057] Additionally, an email discussion was conducted between RAN #85 and #86 regarding the scoping of the Rel-17 WI on non-terrestrial networks. The report of this email discussion is available in RP-192500. It was concluded that the Rel-17 NR-NTN NWI should include two activities:
[0058] NR-NTN develops specifications to support normative activities in the following scenarios:
[0059] o The transparent payload based LEO scenarios address at least 3GPP Category 3 UEs with and without GNSS capabilities as well as geostationary and / or mobile cell scenarios (as per SI results).
[0060] ■ NOTE 1: Addressing LEO will provide flexibility to also support HAPS based scenarios based on transparent payloads.
[0061] ○ GEO context based on transparent payload addresses UEs with GNSS capabilities.
[0062] ■ NOTE 2: Addressing LEO and GEO scenarios will enable NR to support all NGSO scenarios with circular orbits at altitudes greater than or equal to 600 km.
[0063] ●Research activities on NTN context addressing
[0064] ○ HAPS scenario based on transparent payload: Study on the implementation of spectrum coexistence with cellular (additional control resource set, PCI confusion mitigation, etc.)
[0065] ○ Scenarios based on IoT-NTN
[0066] ○ UE’s location based on NTN network (for regulatory services): Identify possible solutions
[0067] Based on the above points, a new work item is proposed to carry the conclusions of the FS_NR_NTN_solutions study item and specify solutions to enable NR to support non-terrestrial networks.
[0068] Addressing LEO and GEO scenarios will be able to support all NGSO scenarios with circular orbits at altitudes greater than or equal to 600 km.
[0069] 4. Goals
[0070] 4.1 Objectives of SI or core WI or test WI
[0071] The work item aims to specify enhancements for NR NTN (Non-Terrestrial Network) identification, in particular LEO and GEO, with implicit compatibility to support High Altitude Platforms (HAPS) and Air-to-Ground (ATG) scenarios based on the following principles:
[0072] ●Adopt FDD for core specification work of NR-NTN.
[0073] ○ Note: This does not mean that TDD cannot be used in related contexts, such as HAPS, ATG
[0074] ● Use geo-fixed tracking areas and geo-fixed and mobile cells
[0075] ●Use UE with GNSS capability.
[0076] ●Use transparent payload
[0077] The detailed objectives are to specify enhancements to the NR radio interface and NG-RAN for Rel-15 and Rel-16 as follows:
[0078] 4.1.1RAN1
[0079] Enhanced features to address the problems identified due to long propagation delays, large Doppler effects and mobile cells in NTNs should specify the following (see TR 38.821):
[0080] ● Enhanced timing relationship [RAN1, RAN2]
[0081] ● Enhancement of UL time and frequency synchronization [RAN1, RAN2]
[0082] ******************************End of Quote*******************************
[0083] The UE-specific TA reporting for NR NTN is mentioned in the Operational MAC CR ([3] R2-2111615, "Stage 3 Operational CR of TS 38.321 for Rel-17 NTN"):
[0084] ****************************** Quote starts [3] *********************************
[0085] 5.1 Random Access Procedure
[0086] 5.1.1 Random Access Procedure Initialization
[0087] According to TS 38.300[2], the random access procedure described in this section is initiated by a PDCCH command, the MAC entity itself, or an RRC event. In the MAC entity, there is only one ongoing random access procedure at any point in time. […]
[0088] RRC configures the following parameters for the random access procedure:
[0089] […]
[0090] -enableTA-Report: Indicates whether UE-specific TA reporting during the random access procedure is enabled. […]
[0091] 5.1.3a MSGA Transfer
[0092] For each MSGA, the MAC entity shall:
[0093] […]
[0094] 1> If this is the first MSGA transmission within this random access procedure:
[0095] 2> If no transmission is performed for the CCCH logical channel, then:
[0096] 3> Indicate to the multiplexing and aggregation entity to include the C-RNTI MAC CE in subsequent uplink transmissions.
[0097] 2> If the random access procedure is initiated for SpCell beam failure recovery and spCell-BFR-CBRA with value true is configured:
[0098] 3> Indicate to the multiplexing and aggregation entity to include the BFR MAC CE or truncated BFR MAC CE in subsequent uplink transmissions.
[0099] 2> If the random access procedure is not initiated due to an SI request and enableTA-Report with an enabled value is configured, then:
[0100] 3> Indicate to the multiplexing and aggregation entity to include the UE-specific TA report MAC CE in subsequent uplink transmissions.
[0101] 2> Based on the HARQ information determined for the MSGA payload (see clause 5.1.2a), obtain the MAC PDU to be transmitted from the multiplexing and aggregation entity and store it in the MSGA buffer.
[0102] […]
[0103] 5.1.4 Random Access Response Reception
[0104] Once the random access preamble is transmitted, regardless of whether measurement gaps may occur, the MAC entity shall:
[0105] […]
[0106] 1> Otherwise, if a valid (as specified in TS 38.213 [6]) downlink assignment has been received on the PDCCH for the RA-RNTI and the received TB was successfully decoded:
[0107] […]
[0108] 4> Apply the following actions for the serving cell in which the random access preamble is transmitted:
[0109] 5> Process the received timing advance command (see clause 5.2);
[0110] 5> Indicate to the lower layer the preambleReceivedTargetPower and the amount of power ramp-up applied to the latest random access preamble transmission (i.e. (PREAMBLE_POWER_RAMPING_COUNTER-1)×PREAMBLE_POWER_RAMPING_STEP);
[0111] 5> If the random access procedure for SCell is performed on an uplink carrier in which pusch-Config is not configured:
[0112] 6> Ignore the received UL grant.
[0113] 5> Otherwise:
[0114] 6> Process the received UL grant value and indicate the value to the lower layers.
[0115] 4> If the MAC entity does not select a random access preamble among the contention-based random access preambles, then:
[0116] 5> The random access procedure is considered to be completed successfully.
[0117] 4> Otherwise:
[0118] 5> Set TEMPORARY_C-RNTI to the value received in the random access response;
[0119] 5> If this is the first successfully received random access response within this random access procedure:
[0120] 6> If no transmission is performed for the CCCH logical channel, then:
[0121] 7> Indicate to the multiplexing and aggregation entity to include the C-RNTI MAC CE in subsequent uplink transmissions.
[0122] 6> If the random access procedure is initiated for SpCell beam failure recovery and spCell-BFR-CBRA with value true is configured:
[0123] 7> Indicate to the multiplexing and aggregation entity to include the BFR MAC CE or truncated BFR MAC CE in subsequent uplink transmissions.
[0124] 6> If the random access procedure is not initiated due to an SI request and enableTA-Report with an enabled value is configured, then:
[0125] 7> Indicate to the multiplexing and aggregation entity to include the UE-specific TA report MAC CE in subsequent uplink transmissions.
[0126] 6> Get the MAC PDU for transmission from the multiplexing and aggregation entity and store it in the Msg3 buffer.
[0127] […]
[0128] 5.XX UE-specific TA report
[0129] The UE may be configured to report information about the UE specific timing advance during a random access procedure not due to an SI request and / or while in RRC_CONNECTED.
[0130] During a random access procedure not due to an SI request, the UE may be configured to report the UE-specific TA value using the UE-specific TA reporting MAC CE. The reporting of UE-specific TA is controlled by enableTA-Report contained in the system information.
[0131] Editor's note: Event triggering for reporting information about UE-specific TA in connected mode is supported and is based on TA value. TA offset threshold can be used for event triggered reporting, at least the offset threshold can be between the current information about UE-specific TA and the last successfully reported information about UE-specific TA.
[0132] Editor's note: The above requires confirmation from RAN1 and may be a pending RAN1 conclusion for re-discussion.
[0133] Editor's note: If the content of the information reported about the UE-specific TA is UE location information in connected mode, it is reported using RRC signaling.
[0134] Editor's note: Protocol: Under the working assumption "UE location information cannot be reported in connected mode", the content of the UE-specific TA reported in connected mode is the UE-specific TA pre-compensation (for the details of the TA value, confirmation from RAN1 is required).
[0135] Editor's note: Protocol: Under the working assumption "UE location information can be reported in connected mode", for TA reporting purposes in connected mode, the network may configure the UE to send UE-specific TA pre-compensation (for details of TA value, confirmation from RAN1 is required) or UE location information.
[0136] Editor's note: Protocol: If the content of the reported information about the UE-specific TA is the TA pre-compensation value in connected mode, then use MAC CE for reporting
[0137] Editor's note: Protocol: In cases where UE location information can be reported to the network, dedicated signaling is used to configure the UE to report UE location and / or UE specific TA information for TA reporting in connected mode. Whether both mechanisms are needed in parallel is for further study
[0138] […]
[0139] 6.1.3.XX UE-specific TA reporting MAC CE
[0140] The UE-specific TA reporting MAC CE is identified by a MAC subheader with an LCID as specified in Table 6.2.1-2.
[0141] It has a fixed size and consists of a single field defined as follows:
[0142] -UE Specific TA: This field contains the UE estimate of the UE specific TA. The length of the field is XX bits.
[0143] Editor's Note: The details and content of the UE-specific TA reporting MAC CE require confirmation from RAN1 and will be re-discussed pending RAN1 conclusion.
[0144] ******************************End of Quote*******************************
[0145] In the past RAN2 meeting, the following agreements were made:
[0146] (RAN2#113bis-e)
[0147] - At least for uplink scheduling adaptation, the UE may report information about UE-specific TA pre-compensation. The exact information and frequency of reporting depends on RAN1 results. When / how to report is for further study.
[0148] - UE reports UE-specific TA pre-compensation using MAC CE during RACH procedure (whether this needs to be configured is for further study). The actual content is for further study and also depends on further RAN1 input.
[0149] (RAN2#114-e)
[0150] - If enabled by the network, the UE reports information about UE-specific TA pre-compensation using MAC CE during the random access procedure (MSGA / MSG3 or MSG5).
[0151] (RAN2#115-e)
[0152] - UE-specific TA reporting during RACH procedure is enabled / disabled via System Information (SI) (for RACH in connected mode for further study)
[0153] - The content of the UE-specific TA pre-compensation reported using MAC CE in the RA procedure is the UE-specific TA (this can be revisited after receiving the RAN1 response).
[0154] - Support for reporting of UE-specific TA information in connected mode via RRC signaling or MAC CE for further study
[0155] -Support event triggering for reporting of UE-specific TA information in connected mode. Details for further study. Confirmation from RAN1 is also required
[0156] - If configured, the UE shall report information of UE-specific TA precompensation to the target cell during random access. Whether a new indication in RRC reconfiguration with synchronization is needed is for further study (except for the System Information Block (SIB) indication carried in the HO command on whether TA reporting is enabled / disabled in the target cell).
[0157] - Information about UE-specific TA pre-compensation is not reported in RA procedure triggered by "Request for additional SI"
[0158] - Event trigger for reporting information about UE specific TA is based on TA value (needs confirmation from RAN1)
[0159] -TA offset threshold can be used for event-triggered reporting, at least the offset threshold can be between the current information about the UE-specific TA and the last successfully reported information about the UE-specific TA
[0160] - Event triggering based on time threshold for reporting information about UE-specific TAs is not supported in NTN.
[0161] - No new indication in the synchronized RRC reconfiguration is required to configure the UE to report information about UE-specific TAs in the handover procedure (except for the SIB indication carried in the HO command about whether TA reporting is enabled / disabled in the target cell).
[0162] - If the content of the reported information about the UE-specific TA is UE location information in connected mode, it is reported using RRC signaling.
[0163] - Under the working assumption "UE location information may be reported in connected mode", for TA reporting purposes in connected mode, the network may configure the UE to send UE specific TA pre-compensation (needs confirmation from RAN1 for details of TA value) or UE location information
[0164] - (Working Assumption) If the content of the reported information about the UE-specific TA is the TA pre-compensation value in connected mode, then use MAC CE for reporting
[0165] (RAN2#116-e)
[0166] - It is not mandatory for Msg3 / MsgA or Msg5 to include TA report MAC CE, and whether it can be included depends on the TB size of Msg3 / MsgA or Msg5. No specific changes are required for this
[0167] - If the content of the reported information about the UE-specific TA is the TA pre-compensation value in connected mode, then report it using MAC CE
[0168] - In case UE location information can be reported to the network, use dedicated signaling to configure the UE to report UE location and / or UE specific TA information for TA reporting in connected mode. Whether both mechanisms are needed in parallel is for further study
[0169] In New Radio (NR), non-terrestrial networks (NTNs) will be introduced to use air / space vehicles as platforms for providing mobile services (e.g., [1] RP-201256, "Solutions for NR Support of Non-terrestrial Networks (NTNs)". UEs can be linked to, reside on, and / or connected to NTN networks involving air / space transmissions. NTNs may include various platforms, including low earth orbit (LEO) satellites, medium earth orbit (MEO) satellites, highly 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 geo-fixed beams (e.g., beams that are temporarily fixed at a location during a period of time) or geo-mobile beams (e.g., beams that continuously move together with the satellite). NTNs can provide wide area coverage and provide NW access in scenarios when terrestrial networks (TNs) are not feasible (e.g., deserts, polar regions, and / or on airplanes). More details on different NTN platforms can be found in TR 38.821 ([2]3GPP TR 38.821 V16.0.0).
[0170] To achieve UL synchronization in NTN, the UE shall pre-compensate the timing advance (TA) by taking into account the UE position, common TA and satellite ephemeris. Information about the UE TA may be reported by the UE to the network (NW) in NTN. Information about the UE TA may be reported in initial access and / or radio resource control (RRC) connected mode. If enabled by system information, e.g. for initial access, for the first event, the UE shall report the TA during the random access (RA) procedure. The UE shall report the TA based on a triggering event configured by dedicated signaling.
[0171] If enabled by the NW, information about the UE TA may be reported using a Media Access Control (MAC) Control Element (CE) during / at the RA procedure (e.g., in MSGA / Msg3 or Msg5). TA reporting during / at the RA procedure will be enabled / disabled by system information. TA reporting during / at the RA procedure may be controlled by a parameter (e.g., enableTA-Report) included in the system information. And TA reporting in RRC connected mode is event triggered (e.g., configured by the NW). The reporting event will be based on the TA offset (threshold) between the current information about the UE TA and the last successfully reported information about the UE TA. For example, if the TA value of the UE becomes higher than the TA offset threshold in the RRC connected mode (e.g., the difference between the current TA and the last successfully reported TA is higher than the offset), the UE will trigger a TA report. For the purpose of TA reporting in RRC connected mode, dedicated signaling (e.g., RRC configuration) is used to configure the UE to report UE location information and / or TA related information.
[0172] For example, if reporting is enabled through system information (e.g., enableTA-Report in system information is set to enabled, enableTA-Report exists in system information), the UE may report information about UE-specific TAs during / at the time of RA procedure (e.g., in initial access) using MAC CE. If reporting is disabled through system information (e.g., enableTA-Report in system information is not set to enabled, enableTA-Report does not exist in system information), the UE may not report information about UE-specific TAs during / at the time of RA procedure (e.g., in initial access).
[0173] If the reporting event is configured and (at least) implemented / triggered by dedicated signaling, the UE may report information related to a UE-specific TA in RRC connected mode. The UE may be configured to report information about a UE-specific TA in RRC connected mode, including content such as TA-related information and / or UE location information. The UE may be configured to report information about a UE-specific TA using MAC CE in RRC connected mode, including content such as TA-related information. The UE may be configured to report information about a UE-specific TA using RRC signaling in RRC connected mode, including content such as UE location information. TA reporting in RRC connected mode may be enabled / disabled by system information. TA reporting in RRC connected mode may not be enabled / disabled by system information. If reporting is enabled by system information (e.g., included in a handover (HO) command message), the UE may report information about a UE-specific TA in RRC connected mode using MAC CE during / at the time of a RA procedure (e.g., for RRC reconfiguration with synchronization and / or handover). If reporting is disabled through system information (eg, included in a HO Command message), the UE may not report information about UE-specific TAs during a RA procedure (eg, for RRC reconfiguration with synchronization and / or handover) in RRC connected mode.
[0174] Based on the current protocol, TA reporting during / at the time of RA procedure and TA reporting in RRC connected mode will be configured separately. TA reporting during / at the time of RA procedure will be configured through system information, and TA reporting in RRC connected mode will be configured through dedicated signaling (e.g., RRC message). In addition, TA reporting during / at the time of RA procedure will be reported once configured / enabled, and TA reporting in RRC connected mode will need to be triggered by a reporting event once configured. The reporting event for triggering TA reporting in RRC connected mode (e.g., event-triggered TA reporting) will be based on the TA offset between the current TA and the TA included in the last TA report. For example, if the TA offset is greater than a configured threshold, the TA report is triggered.
[0175] However, it is possible that when the UE is configured with TA reporting in RRC connected mode, there is no previous TA report. For example, the UE is in a cell in which TA reporting during / at the time of the RA procedure is not enabled (e.g., indicated by system information), and the UE receives dedicated signaling to configure TA reporting in RRC connected mode. In this case, the TA report cannot be triggered because the UE is unable to calculate the TA offset between the current TA and the TA included in the last TA report. In order to solve the problem, the TA report should be triggered by the UE in response to the configuration of the TA report in RRC connected mode. The UE may be configured with event-triggered TA reporting. A reporting event and / or event-triggered TA report is triggered when the TA offset between the current TA and the last reported TA is higher than a threshold. In order to prevent the absence of a previous TA report for comparison, the TA report may be triggered immediately after the configuration of the event-triggered TA report.
[0176] On the other hand, it is also possible that the TA report has been reported by the UE when the UE is configured with TA reporting in RRC connected mode. It is possible that the NW also configures TA reporting during RA. For example, the UE is in a cell where TA reporting during / at the time of RA procedure is enabled (e.g., indicated by system information), and the UE receives dedicated signaling to configure TA reporting in RRC connected mode. In this case, it may not be good to always trigger TA reporting (e.g., event-triggered TA reporting) in response to the configuration of TA reporting in RRC connected mode (or at this time) in view of the signaling overhead.
[0177] Considering that there may be different configurations for UE to trigger TA reporting and there may be different contents and / or triggers for TA reporting, methods for UE to determine whether and how to trigger and / or include information in TA reporting should be considered.
[0178] To solve the problem, the UE may determine whether to trigger a TA report in response to receiving a configuration for configuring a TA report in an RRC connection mode (e.g., having the content of the first information and / or the second information) (or at this time) based on satisfying at least one or more conditions. The first information may be TA-related information. The second information may be UE location information.
[0179] Conditions can be (or include) one or more of the following:
[0180] - If (or whether) TA reporting is enabled at / during the RA procedure;
[0181] - if (or whether) the content of the last reported TA is the second information (e.g., UE location information) or the first information (e.g., TA-related information);
[0182] - if (or whether) a configuration to configure TA reporting in RRC connected mode is received in a HO command (e.g., RRCReconfiguration including reconfigurationWithSync);
[0183] - If (or whether) there is a previous TA report (e.g., in the same cell);
[0184] - if (or whether) there is a previous TA report (e.g. in the same cell) with content as TA-related information;
[0185] - If (or whether) there is a previous TA report with content as UE location information (e.g. in the same cell);
[0186] - If (or whether) there is a previous TA report (e.g., in the same cell) with the same content as the TA report configured in RRC connected mode;
[0187] - if (or whether) the configured TA report content in the configuration used to configure the TA report in RRC connected mode is the same as the content of the previous TA report (e.g. in the same cell); and / or
[0188] - If (or whether) there was a previous TA report in the (current) RRC connected mode.
[0189] The UE may determine whether to trigger a TA report in response to receiving a configuration for configuring a TA report (e.g., a configuration for event-triggered TA reporting in RRC connected mode) (or at this time) based on, for example, whether there is a previous TA report in the same current serving cell in (current) RRC connected mode. For example, the UE may determine whether to trigger a second TA report in response to receiving a configuration for configuring a TA report (e.g., a configuration for event-triggered TA reporting in RRC connected mode) (or at this time) based on, for example, whether a first TA report is (or has been) triggered, generated, transmitted and / or reported in the same / current serving cell in (current) RRC connected mode. The UE may determine to trigger a TA report in response to receiving a configuration for event-triggered TA reporting based on whether the first TA report is (or has been) triggered, generated, transmitted and / or reported (e.g.) to the serving cell. In one example, if a first TA report has been triggered during RA (e.g., for initial access, for a first event), the UE does not trigger a second TA report after receiving the configuration for event-triggered TA reporting. If the first TA report is not triggered during RA (e.g., for initial access, for the first event), the UE triggers the second TA report after receiving the configuration of event-triggered TA report. The first TA report and the second TA report may be transmitted to the same cell (e.g., the (current) serving cell).
[0190] In some instances, the UE may determine whether to trigger TA reporting in response to (or at) receiving a configuration to configure TA reporting in RRC connected mode based on whether TA reporting at / during the RA procedure is enabled.
[0191] Case 1: TA reporting at / during the RA procedure is disabled, and TA reporting (with the first information and / or the second information) in RRC connected mode is configured.
[0192] If TA reporting at / during the RA procedure is not enabled (or disabled), the UE may (determine) trigger TA reporting in response to (or at this time of) receiving a configuration to configure TA reporting in RRC connected mode. Figure 5As shown in , the UE receives a first configuration (e.g., in system information) indicating that TA reporting is not enabled (or disabled) at / during an RA procedure. The UE receives a second configuration (e.g., in dedicated signaling) indicating / configuring a TA report with first information and / or second information in RRC connected mode. In response to receiving the second configuration (e.g., in dedicated signaling) (e.g., a configuration with TA reporting in RRC connected mode) (or at this time), the UE triggers a TA report. The UE may trigger a TA report when a reporting event is met / triggered in RRC connected mode. The UE may trigger a TA report regardless of the current TA value (e.g., regardless of whether the reporting event is met). The reporting event may be met (or triggered) when the change (or difference, or offset) of the UE TA between the current information about the UE TA and the last reported information about the UE TA is greater than (or not less than) a configured threshold. The UE may trigger a TA report when the change (or difference, or offset) of the UE TA between the current information about the UE TA and the last reported information about the UE TA is greater than (or not less than) a configured threshold.
[0193] Case 2: TA reporting at / during the RA procedure is enabled, and TA reporting (with the first information or the second information) in RRC connected mode is configured.
[0194] If TA reporting at / during the RA procedure is enabled (or not disabled), the UE may determine not to trigger TA reporting in response to receiving a configuration to configure TA reporting in RRC connected mode (or at this time). Figure 6 As shown in , the UE receives a first configuration (e.g., in system information) indicating that TA reporting is enabled at / during a RA procedure. The UE receives a second configuration (e.g., in dedicated signaling) indicating / configuring a TA report with first information and / or second information in RRC connected mode. In response to receiving the second configuration (e.g., in dedicated signaling) (e.g., a configuration with TA reporting in RRC connected mode) (or at this time), the UE does not trigger a TA report. Additionally and / or alternatively, the UE may trigger a TA report when a reporting event is met / triggered in RRC connected mode. The reporting event may be met (or triggered) when the change (or difference, or offset) of the UE TA between the current information about the UE TA and the last reported information about the UE TA is greater than (or not less than) a configured threshold. The UE may trigger a TA report when the change (or difference, or offset) of the UE TA between the current information about the UE TA and the last reported information about the UE TA is greater than (or not less than) a configured threshold.
[0195] If TA reporting at / during the RA procedure is enabled (or not disabled), the UE may determine whether to trigger TA reporting in response to receiving a configuration for configuring TA reporting in RRC connected mode (or at this time) based on whether a reporting event is met. For example, the UE receives a first configuration (e.g., in system information) indicating that TA reporting at / during the RA procedure is enabled. The UE receives a second configuration (e.g., in dedicated signaling) indicating / configuring TA reporting with first information and / or second information in RRC connected mode. In response to receiving the second configuration (e.g., in dedicated signaling) (e.g., a configuration with TA reporting in RRC connected mode) (or at this time), if the reporting event is met in RRC connected mode, the UE may trigger TA reporting. If the reporting event is not met in RRC connected mode, the UE may not trigger TA reporting. The reporting event may be met (or triggered) when the change (or difference, or offset) of the UE TA between the current information about the UE TA and the last reported information about the UE TA is greater than (or not less than) the configured threshold. When the change (or difference, or offset) of UE TA between the current information about UE TA and the last reported information about UE TA is greater than (or not less than) a configured threshold, the UE may trigger a TA report.
[0196] The UE may receive a first configuration of a TA report. The UE may determine (whether) to trigger a first TA report based on the first configuration. The UE may receive a second configuration of a TA report. The UE may determine (whether) to trigger a second TA report in response to receiving the second configuration (or at this time) based on the first configuration and / or the first TA report.
[0197] In one example, the UE may receive a first configuration (e.g., in system information) indicating that TA reporting at / during an RA procedure is enabled. The UE may receive system information containing the first configuration configured to be enabled. The UE may trigger a first TA report during or due to an RA procedure for initial access and / or for a first event. The UE may transmit the first TA report during the RA procedure or after the RA procedure (e.g., in a subsequent transmission of the RA procedure). The UE may transmit the first TA report using an uplink (UL) grant of Msg3 / MSGA. The UE may transmit the first TA report using an UL grant received after transmitting Msg3 / MSGA. The UE may receive a second configuration (e.g., in dedicated signaling) indicating / configuring / enabling TA reporting in RRC connected mode (e.g., event-triggered TA reporting). In response to receiving the second configuration (e.g., in dedicated signaling) (or at this time), the UE may not trigger a second TA report based on the first TA report having been transmitted (and / or triggered). When the change (or difference, or offset) of the UE TA between the current information about the UE TA and the last reported information about the UE TA (e.g., the TA reported in the first TA report) is greater than (or not less than) the configured threshold, the UE may trigger a third TA report, for example, based on the second configuration. The UE may transmit the third TA report using an available UL grant.
[0198] Additionally and / or alternatively, the UE may receive a first configuration (e.g., in system information) indicating that TA reporting during / at the time of an RA procedure is not enabled. The UE may not receive a first configuration (e.g., in system information) indicating that TA reporting during / at the time of an RA procedure is enabled. The first configuration may be omitted or absent in the system information. The UE may receive system information not including the first configuration. The UE may not trigger a first TA report during or due to an RA procedure for initial access and / or for a first event. The UE may not transmit a first TA report during or after the RA procedure (e.g., in a subsequent transmission of the RA procedure). The UE may receive a second configuration (e.g., in dedicated signaling) indicating / configuring / enabling a TA report in RRC connected mode (e.g., an event-triggered TA report). In response to receiving the second configuration (e.g., in dedicated signaling) (or at this time), the UE may not trigger a second TA report based on the first TA report having been transmitted (and / or triggered). The UE may transmit a second TA report using an available UL grant. When the change (or difference, or offset) of the UE TA between the current information about the UE TA and the last reported information about the UE TA (e.g., the TA reported in the first TA report) is greater than (or not less than) the configured threshold, the UE may trigger a third TA report, for example, based on the second configuration. The UE may transmit the third TA report using an available UL grant.
[0199] In some instances, based on whether TA reporting is enabled at / during the RA procedure and whether the content of the last reported TA (e.g., the last reported information about the UE TA) (e.g., in the UE's serving cell, in the UE's primary serving cell (PCell)) is UE location information or TA-related information, the UE can determine whether to trigger a TA report in response to receiving a configuration to configure TA reporting in RRC connected mode (or at this time).
[0200] Case 3: When TA reporting at / during the RA procedure is disabled, TA reporting in RRC connected mode is not configured (or not configured), then TA reporting in RRC connected mode (with the first information and / or the second information) is configured / reconfigured.
[0201] If there is no previous TA report (e.g., in the same cell), the UE may (determine) trigger a TA report in response to (or at this time of) receiving a configuration to configure TA reporting in RRC connected mode. Figure 7 As shown in , the UE receives a first configuration (e.g., in system information) indicating that TA reporting is not enabled (or disabled) at / during an RA procedure. The UE receives a second configuration (e.g., in first dedicated signaling) indicating / configuring that TA reporting is not configured in RRC connected mode. The UE then receives another second configuration (e.g., a third configuration) (e.g., in second dedicated signaling) indicating / configuring TA reporting with first information and / or second information in RRC connected mode. In response to receiving the (latter) second configuration (e.g., third configuration) (e.g., in second dedicated signaling) that configures TA reporting in RRC connected mode (or at this time), the UE triggers TA reporting. The UE may trigger TA reporting when a reporting event is met / triggered in RRC connected mode. The UE may trigger TA reporting regardless of the current TA value (e.g., regardless of whether the reporting event is met). The reporting event may be met / triggered when the change / difference / offset of the UE TA between the current information about the UE TA and the last reported information about the UE TA is greater than / not less than a configured threshold. When the change / difference / offset of UE TA between the current information about UE TA and the last reported information about UE TA is greater than / not less than a configured threshold, the UE may trigger a TA report.
[0202] Case 4-1: When TA reporting at / during the RA procedure is deactivated, TA reporting in RRC connected mode (with the second information) is configured, then TA reporting in RRC connected mode (with the first information) is configured / reconfigured.
[0203] If there is no previous TA report with the same information content (e.g. in the same cell) as indicated / configured by the configuration, the UE may (determine) trigger a TA report in response to (or at the time of) receiving a configuration to configure a TA report in RRC connected mode. Figure 8 As shown in , the UE receives a first configuration (e.g., in system information) indicating that TA reporting is not enabled (or disabled) at / during an RA procedure. The UE receives a second configuration (e.g., in first dedicated signaling) indicating / configuring a TA report with second information in RRC connected mode. The UE then receives another second configuration (e.g., a third configuration) (e.g., in second dedicated signaling) indicating / configuring a TA report with first information in RRC connected mode. In response to receiving the (later) second configuration (e.g., the third configuration) (e.g., in second dedicated signaling) (or at this time) that configures a TA report with first information in RRC connected mode, the UE may trigger a TA report. In response to receiving the (later) second configuration (e.g., the third configuration) (e.g., in second dedicated signaling) (or at this time) that configures a TA report with first information in RRC connected mode, the UE may not trigger a TA report. The UE may trigger a TA report when a reporting event is met / triggered in RRC connected mode. The UE may trigger a TA report regardless of the current TA value (e.g., regardless of whether the reporting event is met). When the change / difference / offset of UE TA between current information about UE TA (e.g., first information) and last reported information about UE TA (e.g., first and / or second information) is greater than / not less than a configured threshold, a reporting event may be satisfied / triggered. When the change / difference / offset of UE TA between current information about UE TA (e.g., first information) and last reported information about UE TA (e.g., first and / or second information) is greater than / not less than a configured threshold, the UE may trigger a TA report.
[0204] Case 4-2: When TA reporting at / during the RA procedure is deactivated, TA reporting in RRC connected mode (with the first information) is configured, then TA reporting in RRC connected mode (with the second information) is configured / reconfigured.
[0205] If there is no previous TA report with the same information content (e.g. in the same cell) as indicated / configured by the configuration, the UE may (determine) trigger a TA report in response to (or at the time of) receiving a configuration to configure a TA report in RRC connected mode. Fig. 9As shown in , the UE receives a first configuration (e.g., in system information) indicating that TA reporting is not enabled (or disabled) at / during an RA procedure. The UE receives a second configuration (e.g., in first dedicated signaling) indicating / configuring a TA report with first information in RRC connected mode. The UE then receives another second configuration (e.g., a third configuration) (e.g., in second dedicated signaling) indicating / configuring a TA report with second information in RRC connected mode. In response to receiving the (later) second configuration (e.g., the third configuration) (e.g., in second dedicated signaling) (or at this time) that configures a TA report with second information in RRC connected mode, the UE may trigger a TA report. In response to receiving the (later) second configuration (e.g., the third configuration) (e.g., in second dedicated signaling) (or at this time) that configures a TA report with second information in RRC connected mode, the UE may not trigger a TA report. The UE may trigger a TA report when a reporting event is met / triggered in RRC connected mode. The UE may trigger a TA report regardless of the current TA value (e.g., regardless of whether the reporting event is met). When the change / difference / offset of UE TA between current information about UE TA (e.g., second information) and last reported information about UE TA (e.g., first and / or second information) is greater than / not less than a configured threshold, a reporting event may be satisfied / triggered. When the change / difference / offset of UE TA between current information about UE TA (e.g., second information) and last reported information about UE TA (e.g., first and / or second information) is greater than / not less than a configured threshold, the UE may trigger a TA report.
[0206] Case 5: When TA reporting at / during the RA procedure is enabled, TA reporting in RRC connected mode is not configured (or not configured), then TA reporting in RRC connected mode (with the first information and / or the second information) is configured / reconfigured.
[0207] If there is no previous TA report with the same information content (e.g. in the same cell) as indicated / configured by the configuration, and / or if there is no previous TA report in the (current) RRC connected mode, the UE may (determine) trigger a TA report in response to (or at this time of) receiving a configuration to configure a TA report in RRC connected mode. Fig.10As shown in , the UE receives a first configuration indicating that TA reporting is enabled at / during a RA procedure (e.g., in system information). The UE receives a second configuration indicating / configuring that TA reporting is not configured in RRC connected mode (e.g., in a first dedicated signaling). The UE then receives another second configuration (e.g., a third configuration) indicating / configuring a TA report with the first information and / or the second information in RRC connected mode (e.g., in a second dedicated signaling). In response to receiving the (later) second configuration (e.g., the third configuration) (e.g., in the second dedicated signaling) (or at this time) of configuring a TA report in RRC connected mode, the UE may trigger a TA report. In response to receiving the (later) second configuration (e.g., the third configuration) (e.g., in the second dedicated signaling) (or at this time) of configuring a TA report in RRC connected mode, the UE may not trigger a TA report. The UE may trigger a TA report when a reporting event is met / triggered in RRC connected mode. The UE may trigger a TA report regardless of the current TA value (e.g., regardless of whether the reporting event is met). When the change / difference / offset of UE TA between current information about UE TA and last reported information about UE TA is greater than / not less than a configured threshold, the reporting event may be satisfied / triggered. When the change / difference / offset of UE TA between current information about UE TA and last reported information about UE TA is greater than / not less than a configured threshold, the UE may trigger a TA report. The last reported information about UE TA may be the first information and / or the second information reported in RRC connected mode. The last reported information about UE TA may be information reported in a TA report at / during an RA procedure.
[0208] Case 6-1: When TA reporting at / during the RA procedure is enabled, TA reporting in RRC connected mode (with the second information) is configured, then TA reporting in RRC connected mode (with the first information) is configured / reconfigured.
[0209] If there is no previous TA report with the same information content (e.g. in the same cell) as indicated / configured by the configuration, the UE may (determine) trigger a TA report in response to (or at the time of) receiving a configuration to configure a TA report in RRC connected mode. Fig.11As shown in , the UE receives a first configuration indicating that TA reporting is enabled at / during a RA procedure (e.g., in system information). The UE receives a second configuration indicating / configuring a TA report with second information in RRC connected mode (e.g., in a first dedicated signaling). The UE then receives another second configuration (e.g., a third configuration) indicating / configuring a TA report with first information in RRC connected mode (e.g., in a second dedicated signaling). In response to receiving a (later) second configuration (e.g., a third configuration) (e.g., in a second dedicated signaling) (or at this time) that configures a TA report with first information in RRC connected mode, the UE may trigger a TA report. In response to receiving a (later) second configuration (e.g., a third configuration) (e.g., in a second dedicated signaling) (or at this time) that configures a TA report with first information in RRC connected mode, the UE may not trigger a TA report. The UE may trigger a TA report when a reporting event is met / triggered in RRC connected mode. The UE may trigger a TA report regardless of the current TA value (e.g., regardless of whether the reporting event is met). When the change / difference / offset of UE TA between current information about UE TA (e.g., first information) and last reported information about UE TA (e.g., first and / or second information) is greater than / not less than a configured threshold, a reporting event may be satisfied / triggered. When the change / difference / offset of UE TA between current information about UE TA (e.g., first information) and last reported information about UE TA (e.g., first and / or second information) is greater than / not less than a configured threshold, the UE may trigger a TA report. The last reported information about UE TA may be information reported in RRC connected mode. The last reported information about UE TA may be information reported in a TA report at / during an RA procedure.
[0210] Case 6-2: When TA reporting at / during the RA procedure is enabled, TA reporting in RRC connected mode (with first information) is configured, then TA reporting in RRC connected mode (with second information) is configured / reconfigured.
[0211] If there is no previous TA report with the same information content (e.g. in the same cell) as indicated / configured by the configuration, the UE may (determine) trigger a TA report in response to (or at the time of) receiving a configuration to configure a TA report in RRC connected mode. Fig.12As shown in , the UE receives a first configuration (e.g., in system information) indicating that TA reporting is not enabled (or disabled) at / during an RA procedure. The UE receives a second configuration (e.g., in first dedicated signaling) indicating / configuring a TA report with first information in RRC connected mode. The UE then receives another second configuration (e.g., a third configuration) (e.g., in second dedicated signaling) indicating / configuring a TA report with second information in RRC connected mode. In response to receiving the (later) second configuration (e.g., the third configuration) (e.g., in second dedicated signaling) (or at this time) that configures a TA report with second information in RRC connected mode, the UE may trigger a TA report. In response to receiving the (later) second configuration (e.g., the third configuration) (e.g., in second dedicated signaling) (or at this time) that configures a TA report with second information in RRC connected mode, the UE may not trigger a TA report. The UE may trigger a TA report when a reporting event is met / triggered in RRC connected mode. The UE may trigger a TA report regardless of the current TA value (e.g., regardless of whether the reporting event is met). When the change / difference / offset of UE TA between current information about UE TA (e.g., second information) and last reported information about UE TA (e.g., first and / or second information) is greater than / not less than a configured threshold, a reporting event may be satisfied / triggered. When the change / difference / offset of UE TA between current information about UE TA (e.g., second information) and last reported information about UE TA (e.g., first and / or second information) is greater than / not less than a configured threshold, the UE may trigger a TA report.
[0212] In some instances, the UE may determine whether to trigger a TA report in response to receiving a configuration for configuring a TA report in RRC connected mode (or at this time) based on whether the configuration is received in the HO command. The HO command is an RRC message indicating a reconfiguration with synchronization and / or handover (e.g., an RRCReconfiguration including reconfigurationWithSync). The HO command includes a first configuration (e.g., for TA reporting at / during an RA procedure) and a second configuration (e.g., for TA reporting in RRC connected mode). The HO command includes the first configuration and the second configuration. The UE may trigger a TA report in response to receiving the first configuration and / or the second configuration in the HO command (or at this time). If the first configuration or the second configuration enables TA reporting, the UE may trigger a TA report in response to receiving the HO command (or at this time). If the first configuration enables TA reporting at / during an RA procedure, and / or if the second configuration indicates / configures / enables TA reporting in RRC connected mode, the UE may trigger a TA report in response to receiving the HO command (or at this time).
[0213] Case 7: In the HO command, TA reporting at / during the RA procedure is deactivated, and TA reporting (with the first information and / or the second information) in RRC connected mode is configured.
[0214] The UE may (determine) trigger TA reporting in response to (or at) receiving a HO command (e.g., RRCReconfiguration with reconfigurationWithSync) with a configuration to configure TA reporting in RRC connected mode (e.g., even if TA reporting at / during the RA procedure is disabled). For example, Fig.13 As shown in , a UE receives a HO command including a first configuration (e.g., in system information) and a second configuration (e.g., in dedicated signaling). The first configuration may indicate that TA reporting is not enabled (or disabled) at / during an RA procedure. The second configuration may indicate / configure a TA report with the first information and / or the second information in RRC connected mode. In response to receiving a HO command (e.g., with a configuration of TA reporting in RRC connected mode) (or at this time), the UE triggers a TA report. The UE may initiate an RA procedure in response to receiving the HO command and transmit a TA report during / at the RA procedure. The UE may trigger a TA report regardless of the current TA value (e.g., regardless of whether a reporting event is met). The UE may trigger a TA report when a reporting event is met / triggered in RRC connected mode (e.g., after an RA procedure for HO). The reporting event may be met / triggered when the change / difference / offset of the UE TA between the current information about the UE TA and the last reported information about the UE TA is greater than / not less than a configured threshold. When the change / difference / offset of UE TA between the current information about UE TA and the last reported information about UE TA is greater than / not less than a configured threshold, the UE may trigger a TA report.
[0215] Case 8: In the HO command, TA reporting at / during the RA procedure is disabled and TA reporting in RRC connected mode is not configured (or not configured).
[0216] The UE may determine not to trigger TA reporting in response to (or at the time of) receiving a HO command (e.g., RRCReconfiguration with reconfigurationWithSync) without having a configuration to configure TA reporting in RRC connected mode or having a configuration to deconfigure (or deactivate) TA reporting in RRC connected mode. Fig.14As shown in , the UE receives a HO command including a first configuration (e.g., in system information) and a second configuration (e.g., in dedicated signaling). The first configuration may indicate that TA reporting is not enabled (or disabled) at / during an RA procedure. The second configuration may deconfigure (or disable) TA reporting with the first information and / or the second information in RRC connection mode. In response to receiving the HO command (or at this time), the UE does not trigger TA reporting. The UE may initiate an RA procedure in response to receiving the HO command and may not transmit a TA report during / at the RA procedure.
[0217] In some instances, the UE may determine whether to trigger the TA report in response to (or at this time of) receiving a TA report (e.g., having the content of the first information and / or the second information) in the RRC connection mode based at least on whether the UE has transmitted and / or triggered the TA report (e.g., in the serving cell of the UE, in the PCell of the UE, after the last RRC connection procedure, and / or after the last handover). The RRC connection procedure may be triggered by initial access, RRC connection recovery, RRC connection reestablishment, and / or synchronization reconfiguration (e.g., handover).
[0218] For example, in response to the configuration of (event-triggered) TA report (in RRC connected mode) (or at this time), if the UE has not transmitted (or generated, or triggered) a TA report before (for example, in the same RRC connection, in the same cell), then the TA report is triggered (or generated). In response to the configuration of (event-triggered) TA report (in RRC connected mode) (or at this time), if the UE has transmitted (or generated, or triggered) a TA report before (for example, in the same RRC connection, in the same cell), then the TA report is not triggered (or generated).
[0219] For example, in response to the configuration of (event-triggered) TA report (in RRC connected mode) (or at this time), if the UE has transmitted (or generated) a TA report before (for example, in the same RRC connection, in the same cell), then whether to trigger (or generate) the TA report depends on whether the reporting event is met.
[0220] One or more examples / situations / situations disclosed herein may be combined in whole or in part to form another example.
[0221] The UE may receive, for example, via system information, a configuration (e.g., a first configuration) to indicate whether TA reporting during / at the time of an RA procedure is enabled (or disabled). If the configuration (e.g., the first configuration) indicates that TA reporting during / at the time of an RA procedure is enabled, the UE may be configured with TA reporting during / at the time of an RA procedure. If the UE is configured with TA reporting during / at the time of an RA procedure (or the UE receives a configuration, e.g., a first configuration, to enable TA reporting during / at the time of an RA procedure), the UE generates, triggers and / or transmits a TA report during (or at the time of) an RA procedure (and / or a subsequent transmission after the RA procedure, a procedure to trigger the RA procedure, a procedure of a first event related to the RA procedure). The TA report may be included in Msg3, Msg5 or MSGA of the RA procedure. If the UE is not configured with TA reporting during / at the time of an RA procedure (or the UE receives a configuration to disable TA reporting during the RA procedure), the UE does not trigger, generate and / or transmit a TA report during (or at the time of) an RA procedure. The TA report may not be included in Msg3, Msg5 or MSGA of the RA procedure (and / or subsequent transmissions after the RA procedure).
[0222] The UE may receive a configuration (e.g., a second configuration) for TA reporting in RRC connected mode, for example, via dedicated signaling. The configuration (e.g., the second configuration) may indicate whether event-triggered TA reporting in RRC connected mode is enabled. The configuration (e.g., the second configuration) may indicate whether the UE should report TA-related information or UE location information. The configuration may indicate a reporting event for TA reporting in RRC connected mode. If the UE is configured with event-triggered TA reporting in RRC connected mode (or the UE receives a configuration, e.g., a second configuration, to enable event-triggered TA reporting in RRC connected mode), the UE evaluates whether the TA offset between the current TA and the TA included in the last TA report is greater than (or not less than) the configured TA offset threshold. The TA offset threshold is configured, indicated and / or enabled by the second configuration. If the reporting event is met, the UE may trigger (or generate) a TA report. If the TA offset is greater than (or not less than) the configured TA offset threshold, the UE may trigger (or generate) a TA report. If the TA offset is not greater than (or less than) the configured TA offset threshold, the UE may not trigger (or generate) a TA report. The UE may have transmitted a TA report before (e.g., in the same cell, after completion of the last RRC connection procedure, and / or after the last handover). The last TA report may be reported at (or during) the RA procedure (e.g., in Msg3, Msg5, or MSGA). The last TA report may be reported in RRC connected mode. The last TA report may have content of TA related information and / or UE location information.
[0223] If the UE is not configured with event-triggered TA reporting in RRC connected mode (or the UE receives a configuration to deactivate / not configure event-triggered TA reporting in RRC connected mode), the UE does not evaluate the TA offset between the current TA and the TA included in the last TA report. The UE does not trigger (or generate) a TA report (e.g., in RRC connected mode) in response to receiving a configuration to deconfigure TA reporting in RRC connected mode.
[0224] To solve the problem, the UE may determine whether to use the first TA as the last reported TA for reporting an event, for example, in response to receiving a configuration to configure TA reporting in RRC connected mode (or at this time) based on satisfying at least one or more conditions. The UE may determine whether to evaluate the TA offset between the current TA and the first TA for reporting an event (or evaluate the TA offset between the current TA and the last reported TA (e.g., the TA included in the last TA report)) based on satisfying at least one or more conditions, for example, in response to receiving a configuration to configure TA reporting in RRC connected mode (or at this time).
[0225] If (at least) one or more conditions are met, the UE may (determine) to use the first TA as the last reported TA for the reported event. If (at least) one or more conditions are not met, the UE may determine not to use the first TA as the last reported TA for the reported event. If (at least) one or more conditions are met, the UE may evaluate the TA offset between the current TA and the first TA (in RRC connected mode). If (at least) one or more conditions are not met, the UE may evaluate the TA offset between the current TA and the TA included in the last TA report (in RRC connected mode). If the TA offset is greater than (or not less than) the configured TA offset threshold for TA reporting in RRC connected mode, the UE triggers a TA report.
[0226] Conditions can be (or include) one or more of the following:
[0227] - If (or whether) TA reporting is enabled at / during the RA procedure;
[0228] - if (or whether) the content of the last reported TA is the second information (e.g., UE location information) or the first information (e.g., TA-related information);
[0229] - if (or whether) a configuration to configure TA reporting in RRC connected mode is received in a HO command (e.g., RRCReconfiguration including reconfigurationWithSync);
[0230] - If (or whether) there is a previous TA report (e.g., in the same cell);
[0231] - if (or whether) there is a previous TA report (e.g. in the same cell) with content as TA-related information;
[0232] - If (or whether) there is a previous TA report with content as UE location information (e.g. in the same cell);
[0233] - If (or whether) there is a previous TA report (e.g., in the same cell) with the same content as the TA report configured in RRC connected mode;
[0234] - if (or whether) the configured TA report content in the configuration used to configure the TA report in RRC connected mode is the same as the content of the previous TA report (e.g. in the same cell); and / or
[0235] - If (or whether) there was a previous TA report in the (current) RRC connected mode.
[0236] In some instances, the UE may determine whether to use the first TA (or the last reported TA) for a reporting event (for TA reporting in RRC connected mode) based on whether TA reporting at / during the RA procedure is enabled.
[0237] Case 1: TA reporting at / during the RA procedure is disabled, and TA reporting (with the first information and / or the second information) in RRC connected mode is configured.
[0238] If TA reporting at / during the RA procedure is not enabled (or is disabled), the UE may use the first TA to calculate the TA offset in the reporting event (for TA reporting in RRC connected mode). Figure 5As shown in , the UE receives a first configuration (e.g., in system information) indicating that TA reporting is not enabled (or disabled) at / during a RA procedure. The UE receives a second configuration (e.g., in dedicated signaling) indicating / configuring a TA report having first information and / or second information in RRC connected mode. In response to receiving the second configuration (e.g., in dedicated signaling) (e.g., a configuration with TA reporting in RRC connected mode) (or thereafter), the UE may evaluate the difference between the current TA and the first TA used for the reporting event. The UE may trigger a TA report when the reporting event is met (e.g., the difference between the current TA and the first TA is higher than a configured threshold). The reporting event may be met / triggered when the change / difference / offset of the UE TA between the current information about the UE TA and the last reported information about the UE TA (or between the current information about the UE TA and the first TA) is greater than / not less than the configured threshold. When the change / difference / offset of UE TA between the current information about UE TA and the last reported information about UE TA (or between the current information about UE TA and the first TA) is greater than / not less than a configured threshold, the UE may trigger a TA report.
[0239] Case 2: TA reporting at / during the RA procedure is enabled, and TA reporting (with the first information or the second information) in RRC connected mode is configured.
[0240] If TA reporting at / during the RA procedure is enabled (or disabled), the UE may use the last reported TA to calculate the TA offset in the reporting event (for TA reporting in RRC connected mode). Figure 6As shown in , the UE receives a first configuration (e.g., in system information) indicating that TA reporting during / at a RA procedure is enabled. The UE receives a second configuration (e.g., in dedicated signaling) indicating / configuring a TA report having first information and / or second information in RRC connected mode. In response to receiving the second configuration (e.g., in dedicated signaling) (e.g., a configuration with TA reporting in RRC connected mode) (or thereafter), the UE may evaluate the difference between the current TA and the TA reported in the TA report during / at a RA procedure for a reporting event. The UE may trigger a TA report when the reporting event is met (e.g., the difference between the current TA and the last reported TA is higher than a configured threshold). The reporting event may be met / triggered when the change / difference / offset of the UE TA between the current information about the UE TA and the last reported information about the UE TA (or between the current information about the UE TA and the first TA) is greater than / not less than the configured threshold. When the change / difference / offset of UE TA between the current information about UE TA and the last reported information about UE TA (or between the current information about UE TA and the first TA) is greater than / not less than the configured threshold, the UE may trigger a TA report.
[0241] In some instances, the UE may determine whether to use the first TA (or the last reported TA) for a reporting event (for TA reporting in RRC connected mode) based on whether TA reporting at / during the RA procedure is enabled and whether the content of the last reported TA (e.g., the last reported information about the UE TA) (e.g., in the UE's serving cell, in the UE's PCell) is UE location information or TA-related information.
[0242] Case 3: When TA reporting at / during the RA procedure is disabled, TA reporting in RRC connected mode is not configured (or not configured), then TA reporting in RRC connected mode (with the first information and / or the second information) is configured / reconfigured.
[0243] If there is no previous TA report (e.g. in the same cell), the UE may (determine) use the first TA to calculate the TA offset in the reporting event (for TA reporting in RRC connected mode). Figure 7As shown in , the UE receives a first configuration (e.g., in system information) indicating that TA reporting is not enabled (or disabled) at / during the RA procedure. The UE receives a second configuration (e.g., in first dedicated signaling) indicating / configuring that TA reporting is not configured in RRC connected mode. The UE then receives another second configuration (e.g., a third configuration) (e.g., in second dedicated signaling) indicating / configuring TA reporting with first information and / or second information in RRC connected mode. In response to receiving the (latter) second configuration (e.g., third configuration) (e.g., in second dedicated signaling) (or thereafter) configuring TA reporting in RRC connected mode, the UE may evaluate the difference between the current TA and the first TA used for reporting events. The UE may trigger a TA report when a reporting event is met / triggered in RRC connected mode. The reporting event may be met / triggered when the change / difference / offset of the UE TA between the current information about the UE TA and the first TA is greater than / not less than a configured threshold. The UE may trigger a TA report when the change / difference / offset of the UE TA between the current information about the UE TA and the first TA is greater than / not less than a configured threshold.
[0244] Case 4-1: When TA reporting at / during the RA procedure is deactivated, TA reporting in RRC connected mode (with the second information) is configured, then TA reporting in RRC connected mode (with the first information) is configured / reconfigured.
[0245] If there is no previous TA report with the same information content (e.g. in the same cell) as indicated / configured by the configuration, the UE may (determine) use the first TA to calculate the TA offset in the reporting event (for TA reporting in RRC connected mode). Figure 8As shown in , the UE receives a first configuration (e.g., in system information) indicating that TA reporting is not enabled (or disabled) at / during a RA procedure. The UE receives a second configuration (e.g., in first dedicated signaling) indicating / configuring a TA report with second information in RRC connected mode. The UE then receives another second configuration (e.g., a third configuration) (e.g., in second dedicated signaling) indicating / configuring a TA report with first information in RRC connected mode. In response to receiving a (later) second configuration (e.g., a third configuration) (e.g., in second dedicated signaling) (or thereafter) configuring a TA report with first information in RRC connected mode, the UE may evaluate the difference between the current TA and the first TA used for reporting an event. In response to receiving a (later) second configuration (e.g., a third configuration) (e.g., in second dedicated signaling) (or thereafter) configuring a TA report with first information in RRC connected mode, the UE may evaluate the difference between the current TA and the last reported information about the UE used for reporting an event. The UE may trigger a TA report when a reporting event is met / triggered in RRC connected mode. When the change / difference / offset of UE TA between current information about UE TA (e.g., first information) and last reported information about UE TA (e.g., first and / or second information) is greater than / not less than a configured threshold, a reporting event may be satisfied / triggered. When the change / difference / offset of UE TA between current information about UE TA (e.g., first information) and last reported information about UE TA (e.g., first and / or second information) is greater than / not less than a configured threshold, the UE may trigger a TA report.
[0246] Case 4-2: When TA reporting at / during the RA procedure is deactivated, TA reporting in RRC connected mode (with the first information) is configured, then TA reporting in RRC connected mode (with the second information) is configured / reconfigured.
[0247] If there is no previous TA report with the same information content (e.g. in the same cell) as indicated / configured by the configuration, the UE may (determine) use the first TA to calculate the TA offset in the reporting event (for TA reporting in RRC connected mode). Fig. 9As shown in , the UE receives a first configuration (e.g., in system information) indicating that TA reporting is not enabled (or disabled) at / during a RA procedure. The UE receives a second configuration (e.g., in first dedicated signaling) indicating / configuring a TA report with first information in RRC connected mode. The UE then receives another second configuration (e.g., a third configuration) (e.g., in second dedicated signaling) indicating / configuring a TA report with second information in RRC connected mode. In response to receiving a (later) second configuration (e.g., a third configuration) (e.g., in second dedicated signaling) (or thereafter) configuring a TA report with second information in RRC connected mode, the UE may evaluate the difference between the current TA and the first TA used for reporting an event. In response to receiving a (later) second configuration (e.g., a third configuration) (e.g., in second dedicated signaling) (or thereafter) configuring a TA report with second information in RRC connected mode, the UE may evaluate the difference between the current TA and the last reported information about the UE TA for reporting an event. The UE may trigger a TA report when a reporting event is met / triggered in RRC connected mode. When the change / difference / offset of UE TA between current information about UE TA (e.g., second information) and last reported information about UE TA (e.g., first and / or second information) is greater than / not less than a configured threshold, a reporting event may be satisfied / triggered. When the change / difference / offset of UE TA between current information about UE TA (e.g., second information) and last reported information about UE TA (e.g., first and / or second information) is greater than / not less than a configured threshold, the UE may trigger a TA report.
[0248] Case 5: When TA reporting at / during the RA procedure is enabled, TA reporting in RRC connected mode is not configured (or not configured), then TA reporting in RRC connected mode (with the first information and / or the second information) is configured / reconfigured.
[0249] If there is no previous TA report with the same information content (e.g. in the same cell) as indicated / configured by the configuration, and / or if there is no previous TA report in the (current) RRC connected mode, the UE may (determine) use the first TA to calculate the TA offset in the reporting event (for TA reporting in RRC connected mode). For example, Fig.10As shown in , the UE receives a first configuration (e.g., in system information) indicating that TA reporting is enabled at / during an RA procedure. The UE receives a second configuration (e.g., in first dedicated signaling) indicating / configuring that TA reporting is not configured in RRC connected mode. The UE then receives another second configuration (e.g., a third configuration) (e.g., in second dedicated signaling) indicating / configuring TA reporting with first information and / or second information in RRC connected mode. In response to receiving the (later) second configuration (e.g., the third configuration) (e.g., in second dedicated signaling) (or thereafter) that configures TA reporting in RRC connected mode, the UE may evaluate the difference between the current TA and the first TA used for reporting events. In response to receiving the (later) second configuration (e.g., the third configuration) (e.g., in second dedicated signaling) (or thereafter) that configures TA reporting in RRC connected mode, the UE may evaluate the difference between the current TA and the reporting information about the UE TA at / during an RA procedure used for reporting events. The UE may trigger a TA report when / after a reporting event is met / triggered in RRC connected mode. When the change / difference / offset of UE TA between current information about UE TA and last reported information about UE TA is greater than / not less than a configured threshold, a reporting event may be satisfied / triggered. When the change / difference / offset of UE TA between current information about UE TA and last reported information about UE TA (and / or last TA) is greater than / not less than a configured threshold, the UE may trigger a TA report. The last reported information about UE TA may be the first information and / or the second information reported in RRC connected mode. The last reported information about UE TA may be information reported in a TA report at / during an RA procedure.
[0250] Case 6-1: When TA reporting at / during the RA procedure is enabled, TA reporting in RRC connected mode (with the second information) is configured, then TA reporting in RRC connected mode (with the first information) is configured / reconfigured.
[0251] If there is no previous TA report with the same information content (e.g. in the same cell) as indicated / configured by the configuration, the UE may (determine) use the first TA to calculate the TA offset in the reporting event (for TA reporting in RRC connected mode). Fig.11As shown in , the UE receives a first configuration (e.g., in system information) indicating that TA reporting is enabled at / during a RA procedure. The UE receives a second configuration (e.g., in first dedicated signaling) indicating / configuring a TA report with second information in RRC connected mode. The UE then receives another second configuration (e.g., a third configuration) (e.g., in second dedicated signaling) indicating / configuring a TA report with first information in RRC connected mode. In response to receiving (the next) second configuration (e.g., the third configuration) (e.g., in second dedicated signaling) (or thereafter) configuring a TA report with first information in RRC connected mode, the UE may evaluate the difference between the current TA and the first TA used for reporting an event. In response to receiving (the next) second configuration (e.g., the third configuration) (e.g., in second dedicated signaling) (or thereafter) configuring a TA report with first information in RRC connected mode, the UE may evaluate the difference between the current TA and the last reported information about the UE TA for reporting an event. The UE may trigger a TA report when / after a reporting event is met / triggered in RRC connected mode. When the change / difference / offset of UE TA between current information about UE TA (e.g., first information) and last reported information about UE TA (e.g., first and / or second information) is greater than / not less than a configured threshold, a reporting event may be satisfied / triggered. When the change / difference / offset of UE TA between current information about UE TA (e.g., first information) and last reported information about UE TA (e.g., first and / or second information) is greater than / not less than a configured threshold, the UE may trigger a TA report. The last reported information about UE TA may be information reported in RRC connected mode. The last reported information about UE TA may be information reported in a TA report at / during an RA procedure.
[0252] Case 6-2: When TA reporting at / during the RA procedure is enabled, TA reporting in RRC connected mode (with first information) is configured, then TA reporting in RRC connected mode (with second information) is configured / reconfigured.
[0253] If there is no previous TA report with the same information content (e.g. in the same cell) as indicated / configured by the configuration, the UE may (determine) use the first TA to calculate the TA offset in the reporting event (for TA reporting in RRC connected mode). Fig.12As shown in , the UE receives a first configuration (e.g., in system information) indicating that TA reporting is not enabled (or disabled) at / during a RA procedure. The UE receives a second configuration (e.g., in first dedicated signaling) indicating / configuring a TA report with first information in RRC connected mode. The UE then receives another second configuration (e.g., a third configuration) (e.g., in second dedicated signaling) indicating / configuring a TA report with second information in RRC connected mode. In response to receiving (a subsequent) second configuration (e.g., a third configuration) (e.g., in second dedicated signaling) (or thereafter) configuring a TA report with second information in RRC connected mode, the UE may evaluate the difference between the current TA and the first TA used for reporting an event. In response to receiving (a subsequent) second configuration (e.g., a third configuration) (e.g., in second dedicated signaling) (or thereafter) configuring a TA report with second information in RRC connected mode, the UE may evaluate the difference between the current TA and the last reported information about the UE TA for reporting an event. The UE may trigger a TA report when / after a reporting event is met / triggered in RRC connected mode. The UE may trigger a TA report regardless of the current TA value (e.g., regardless of whether a reporting event is met). The reporting event may be met / triggered when a change / difference / offset of the UE TA between the current information about the UE TA (e.g., the second information) and the last reported information about the UE TA (e.g., the first and / or the second information) is greater than / not less than a configured threshold. The UE may trigger a TA report when a change / difference / offset of the UE TA between the current information about the UE TA (e.g., the second information) and the last reported information about the UE TA (e.g., the first and / or the second information) is greater than / not less than a configured threshold.
[0254] In some instances, whether to use the first TA (or the last reported TA) for reporting events (for TA reporting in RRC connected mode) is based on whether a configuration is received in a HO command. The HO command is an RRC message indicating a reconfiguration with synchronization and / or handover (e.g., RRCReconfiguration including reconfigurationWithSync). The HO command includes a first configuration (e.g., for TA reporting at / during a RA procedure) and a second configuration (e.g., for TA reporting in RRC connected mode). The HO command includes the first configuration and the second configuration.
[0255] Case 7: The TA report (with the first information and / or the second information) in the RRC connected mode is configured in the HO command.
[0256] If TA reporting in RRC connected mode is configured in the HO command (e.g., RRCReconfiguration with reconfigurationWithSync), the UE may use the first TA to calculate the TA offset in the reporting event (for TA reporting in RRC connected mode). Fig.13 As shown in , a UE receives a HO command including a first configuration (e.g., in system information) and a second configuration (e.g., in dedicated signaling). The first configuration may indicate that TA reporting during / at the time of an RA procedure is not enabled (or disabled). The second configuration may indicate / configure a TA report in an RRC connected mode with the first information and / or the second information. In response to receiving the HO command (e.g., with a configuration of TA reporting in RRC connected mode) (or thereafter), the UE may evaluate the difference between the current TA and the first TA for reporting an event. The UE may initiate an RA procedure for HO in response to receiving the HO command. The UE may evaluate the difference between the current TA and the first TA for reporting an event after the RA procedure. The UE may trigger a TA report when a reporting event is met / triggered (e.g., the difference between the current TA and the first TA is higher than a configured threshold). The reporting event may be met / triggered when the change / difference / offset of the UE TA between the current information about the UE TA and the last reported information about the UE TA (or between the current information about the UE TA and the first TA) is greater than / not less than a configured threshold. When the change / difference / offset of UE TA between the current information about UE TA and the last reported information about UE TA (or between the current information about UE TA and the first TA) is greater than / not less than a configured threshold, the UE may trigger a TA report.
[0257] Alternatively and / or additionally, based at least on whether the UE has transmitted a TA report (e.g., in the UE's serving cell, in the UE's PCell, after the last RRC connection procedure, and / or after the last handover), the UE may use the first TA as the last reported TA for reporting events in the RRC connected mode. The RRC connection procedure may be triggered by initial access, RRC connection recovery, RRC connection reestablishment, and / or synchronization reconfiguration.
[0258] For example, if the UE has not transmitted (or generated) a TA report before (e.g., in the same RRC connection, in the same cell), the UE evaluates the TA offset between the current TA and the first TA. If the UE has transmitted (or generated) a TA report before (e.g., in the same RRC connection, in the same cell), the UE evaluates the TA offset between the current TA and the TA included in the last TA report.
[0259] The first TA may be derived / calculated by the UE at a specific (or reference) timing. The specific (or reference) timing may be (or include) the time when the UE receives a configuration (e.g., a second configuration) to configure a TA report in RRC connected mode. The specific (or reference) timing may be (or include) the last time when the UE receives a TA command (e.g., a timing advance command MAC CE, an absolute timing advance command MAC CE). The specific (or reference) timing may be (or include) the time when the UE receives a RAR and / or MSGB in a RA procedure. The first TA may be a TA derived / calculated by the UE when the UE receives a configuration (e.g., dedicated signaling) to configure a TA report in RRC connected mode. The first TA may be a TA received in a TA command (e.g., a timing advance command MAC CE, an absolute timing advance command MAC CE).
[0260] The first TA may be a common TA received from the NW. The common TA may be received in an NTN specific SIB from the NW. The common TA may be received and / or applied by the UE in the same NTN cell. The first TA may be a dedicated TA received from the NW. The first TA may be a full TA (e.g. used by the UE). The first TA may be a component or combination of components in the TA formula for the UE as specified in [4] R2-2111221 "LS regarding UE TA reporting" (i.e., T TA =(N TA +N TA,UE特定 +N TA,共同 +N TA,偏移 )×T C ) and K offset. K offset can be k_offset and / or k_mac.
[0261] Throughout the present disclosure, one, some and / or all instances of “TA” may correspond to “UE TA”, “UE specific TA”, “UE specific TA pre-compensation” and / or “information about UE TA”, may be supplemented and / or replaced by “UE TA”, “UE specific TA”, “UE specific TA pre-compensation” and / or “information about UE TA”. “Information about UE TA” may be “UE’s TA” or “UE TA” or be replaced by “UE’s TA” or “UE TA”. TA may be UE’s TA and / or TA calculated / estimated / used by UE. Throughout the present disclosure, one, some and / or all instances of “TA report” may correspond to “UE TA report”, “UE specific TA report” and / or “report”, may be supplemented and / or replaced by “UE TA report”, “UE specific TA report” and / or “report”. TA report may be TA report estimated / calculated and / or reported by UE. TA report may be used by NW for timing advance alignment, scheduling adaptation and / or timing related configuration (e.g., K offset).
[0262] The content of the TA report (e.g., information related to UE-specific TA reporting, information about UE TA, UE-specific TA pre-compensation, UE TA) will be TA-related information (e.g., first information) and / or UE position information (e.g., second information). The content of the TA report can be calculated using the UE position and the serving satellite ephemeris. The TA-related information can be the full TA (e.g., used by the UE), the UE-specific TA, the UE's serving link TA, and / or the difference between the full TA and the cell-specific K offset. The TA-related information can be a component or a combination of components in the UE's TA formula as specified in [4] R2-2111221 "LS regarding UE TA reporting" (i.e., T TA =(N TA +N TA,UE特定 +N TA,共同 +N TA,偏移 )×T C ) and K offset. K offset can be k_offset and / or k_mac. Full TA can be T TA and / or T TA +K offset.
[0263] As mentioned, the information about the UE TA, the UE-specific TA, the UE TA and / or the TA may be the TA value of the UE. As mentioned, the information about the UE TA, the UE-specific TA, the UE TA and / or the TA may be the full TA of the UE, e.g. TA Throughout this disclosure, a TA report may be a TA report MAC CE.
[0264] Throughout the present disclosure, a reporting event may correspond to a triggering event, may be supplemented by a triggering event and / or may be replaced by a triggering event. A reporting event and / or a triggering event may be an event to trigger a TA report (in RRC connected mode). The reporting event and / or the triggering event may be configured and / or enabled by a second configuration, for example via dedicated signaling. The second configuration may be or may configure a TA offset threshold, for example, for event-triggered TA reporting.
[0265] Throughout the present disclosure, a TA report at / during RA (procedure) may be a TA report due to (or triggered by) an RA procedure. A TA report at / during RA (procedure) may be configured and / or enabled by a first configuration, for example, via system information. A TA report at / during RA (procedure) may be a TA report enabled and / or triggered during an RA procedure associated with a first event. A TA report at / during RA (procedure) may be triggered during an RA procedure and / or a procedure that triggers an RA procedure (e.g., a procedure for a first event, a procedure for initial access, an RRC establishment procedure). A TA report at / during RA (procedure) may be transmitted during a subsequent transmission after the RA procedure and / or the RA procedure, for example, in Msg3 / MSGA or Msg5.
[0266] The UE location information may be coarse and / or finer location information. The UE location information may be GNSS coordinates and / or parts of GNSS coordinates. The UE location information may be reported based on user consent.
[0267] The UE may be configured by dedicated signaling to report UE location information and / or TA related information for TA reporting in RRC connected mode. The dedicated signaling may be an RRC configuration. The dedicated signaling may be an RRC message (e.g., RRCReestablishment, RRCReconfiguration, RRCConnectionReconfiguration, RRCResume, RRCSetup), a MAC CE, and / or a layer 1 indication. If the UE location information is reported in a TA report (e.g., in RRC connected mode), then RRC signaling is used for reporting. If the TA related information is reported in a TA report (e.g., during / at the time of a RA procedure and / or in RRC connected mode), then MAC CE is used for reporting.
[0268] The RRC signaling for TA reporting (e.g., with content of UE location information) may be an RRC message (e.g., MeasurementReport, RRCReconfigurationComplete). The MAC CE for TA reporting (e.g., with content of TA related information) may be a UE-specific TA reporting MAC CE as specified in the Operational MAC CR after RAN2#116 meeting (e.g., [2] 3GPP TR 38.821 V16.0.0). The UE-specific TA reporting MAC CE may have a fixed size and consist of a single field containing a UE estimate of a UE-specific TA (e.g., TA related information). The UE-specific TA reporting MAC CE may be transmitted during / at a time when the RA procedure (and / or subsequent transmission of the RA procedure) is not initiated for an SI request.
[0269] The TA report during / at the time of the RA procedure may relate to a TA report triggered because of (or in response to / due to) the initiation of the RA procedure or the reception of the first successfully received RAR (Random Access Response) within the RA procedure (or replaced by it).
[0270] TA reporting during / at the time of RA procedure may be configured by configuration in system information (e.g., by enableTA-report in system information). Configuration may apply to TA reporting in RRC connected mode. Configuration may not apply to TA reporting in RRC connected mode. The content of TA reporting during / at the time of RA procedure may be different from the content of TA reporting in RRC connected mode.
[0271] The TA report during / at the time of the RA procedure may be transmitted in a subsequent transmission after the RA procedure and / or after the RA procedure. The TA report during / at the time of the RA procedure may be transmitted in Msg3 / MsgA or Msg5. Depending on the TB size of Msg3, MsgA and / or Msg5, the MAC CE for TA reporting (e.g., UE-specific TA reporting MAC CE) will be transmitted in Msg3 / MsgA or Msg5. Msg5 may be a subsequent UL transmission after the RA procedure is completed. Msg5 may be an UL transmission of / with an RRC message (e.g., RRCSetupComplete, RRCResumeComplete).
[0272] For example, in a 2-step RA procedure, in response to initiating a RA, if TA reporting is enabled by system information, the UE instructs the multiplexing and aggregation entity to include a UE-specific TA report MAC CE in a subsequent UL transmission. The UE may transmit a UE-specific TA report MAC CE in a MSGA or an UL transmission after a MSGA transmission (e.g., scheduled by a NW).
[0273] For example, in a 4-step RA procedure, in response to receiving a RAR (e.g., a downlink (DL) assignment has been received on the PDCCH for the RA-RNTI and the received TB is successfully decoded), if TA reporting is enabled by system information, the UE instructs the multiplexing and aggregation entities to include a UE-specific TA report MAC CE in a subsequent UL transmission. The UE may transmit the UE-specific TA report MAC CE in a Msg3 or an UL transmission after the Msg3 transmission (e.g., scheduled by the NW).
[0274] Throughout the present disclosure, one, some and / or all "RA procedures" may be triggered / initiated for initial access and / or in RRC connected mode. Throughout the present disclosure, one, some and / or all "RA" and / or "RA procedures" may be triggered / initiated by a first event and / or a second event. A RA procedure may be triggered / initiated by a first event but not by a second event. Throughout the present disclosure, one, some and / or all "RA procedures" may be triggered / initiated for the purpose of a first event and / or a second event. A RA procedure may be triggered / initiated for the purpose of a first event but not for the purpose of a second event.
[0275] The first event can be one or more of the following:
[0276] - Initial access and / or RRC (connection) establishment (e.g. from RRC idle mode to RRC connected mode);
[0277] -RRC (connection) recovery (e.g. from RRC inactive mode to RRC connected mode);
[0278] -RRC (connection) re-establishment (e.g., in RRC connected mode); and / or
[0279] - Synchronous reconfiguration, reconfiguration with synchronization and / or handover (e.g., in RRC connected mode).
[0280] The second event can be one or more of the following:
[0281] -DL and / or UL data arrival (e.g. when UL is not synchronized in RRC connected mode);
[0282] -UL data arrival (e.g. when there are no available Physical Uplink Control Channel (PUCCH) resources for SR in RRC connected mode);
[0283] - Scheduling Request (SR) failure (e.g. in RRC connected mode);
[0284] - Establishing time alignment for secondary TAGs (e.g. in RRC connected mode);
[0285] - beam failure recovery (e.g., in RRC connected mode); and / or
[0286] - Listen before talk (LBT) failure on special cells (SpCells) (e.g., in RRC connected mode).
[0287] The system information may be a master information block (MIB) and / or a SIB. The system information may be a SIB specific to the NTN (e.g., SIB19). The system information may enable and / or disable TA reporting via a parameter (e.g., enableTA-Report) included in the RA configuration (e.g., RACH-ConfigCommon). The parameter (e.g., enableTA-Report) may be present or absent. The parameter (e.g., enableTA-Report) may be enabled or disabled.
[0288] TA reporting in RRC connected mode may relate to (or be replaced by) TA reporting triggered by a reporting event (e.g., based on a TA value, based on a TA change from a last TA report, based on a TA change compared to a configured threshold) when the UE is in RRC connected mode. TA reporting in RRC connected mode may relate to (or be replaced by) TA reporting triggered by an event in RRC connected mode.
[0289] TA reporting in RRC connected mode may be configured by dedicated signaling. Dedicated signaling may be applied to TA reporting during / at the time of RA procedure. Dedicated signaling may not be applied to TA reporting during / at the time of RA procedure. The content of TA reporting in RRC connected mode may be different from the content of TA reporting during / at the time of RA procedure.
[0290] TA reports in RRC connected mode may be transmitted in Msg3 / MsgA, Msg5 and / or RRC messages (e.g., MeasurementReport). TA reports in RRC connected mode may be transmitted in a RA procedure (and / or for a subsequent transmission after a RA procedure) triggered / initiated by one or more of the following events / purposes:
[0291] -RRC connection reestablishment;
[0292] - Synchronous reconfiguration and / or handover;
[0293] -DL data arrival (e.g. when UL is not synchronized);
[0294] -UL data arrival (e.g. when the UL is not synchronized, when there are no available PUCCH resources for SR);
[0295] -SR failure;
[0296] - Establish time alignment for secondary TAGs;
[0297] - beam failure recovery; and / or
[0298] -LBT failure on SpCell.
[0299] After receiving the configuration (e.g., the second configuration, in dedicated signaling) of the TA report (event-triggered TA report) in the RRC connection mode, the UE will trigger the TA report when the reporting event is met / triggered (or in response to it). The reporting event for the TA report with the content of the first information and the reporting event for the TA report with the content of the second information may be the same. The reporting event for the TA report with the content of the first information and the reporting event for the TA report with the content of the second information may be different. The reporting event may be based on the TA (e.g., TA difference, TA offset). The reporting event (condition) may be a TA offset threshold between the current information about the UE TA and the last successfully reported information about the UE TA. If the offset (or change) between the current information about the UE TA and the last reported information about the UE TA is greater than or equal to the TA offset threshold / when the offset (or change) between the current information about the UE TA and the last reported information about the UE TA is greater than or equal to the TA offset threshold, then the reporting event may be triggered or met. The TA offset may be the difference between the two TAs. The information about the UE TA may be the first information and / or the second information. The information about the UE TA may be content reported to the NW. The information about the UE TA may be a representation of the TA of the UE. The configuration of the reporting event and the TA report in the RRC connection mode may be configured in the same dedicated signaling. The configuration of the reporting event and the TA report in the RRC connection mode may be configured in different dedicated signaling. When the change (or difference, or offset) of the UE TA between the current information about the UE TA and the last reported information about the UE TA (or between the current information about the UE TA and the first TA) is greater than (or not less than) the configured threshold, the reporting event may be satisfied (or triggered). When the change (or difference, or offset) of the UE TA between the current information about the UE TA and the last reported information about the UE TA (or between the current information about the UE TA and the first TA) is greater than (or not less than) the configured threshold, the UE may trigger a TA report.
[0300] The UE may receive a configuration related to UE TA reporting. The UE may receive one or more first configurations (e.g., in system information, for TA reporting at / during an RA procedure) and / or a second (and / or third) configuration (e.g., in dedicated signaling, for TA reporting in RRC connected mode). The UE may receive a configuration to enable or disable TA reporting at / during an RA procedure. The UE may receive a configuration to enable or disable TA reporting in RRC connected mode. The UE may receive a configuration to indicate the content of a TA report in RRC connected mode (first information and / or second information). The UE may receive a configuration for reporting events for TA reporting in RRC connected mode.
[0301] The UE may be in a cell of the NTN. The UE may be connected to a cell of the NTN. The UE may be connected to a LEO, GEO, MEO, HEO and / or HAPS. Throughout this disclosure, a cell may be or refer to a NTN cell.
[0302] UE may refer to the UE or the MAC entity of the UE.
[0303] The UE may be a NR device. The UE may be a NR light device. The UE may be a device with insufficient capabilities. 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. The UE may be an LTE device. The UE may be a NB-IoT device. The UE may be an enhanced machine type communication (eMTC) device.
[0304] 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 eNB. The network may be a gNB. The network may be a gateway.
[0305] See also Fig.15 , with respect to such and other concepts, systems and methods of the present invention, a method 1000 for a UE in a wireless communication system includes receiving a second configuration for configuring a TA report in an RRC connected mode (step 1002), and determining to trigger a TA report in response to receiving the second configuration (or at this time) based on satisfying (at least) one or more conditions (step 1004).
[0306] In various embodiments, the condition may be whether TA reporting at / during the RA procedure is enabled.
[0307] In various embodiments, the condition may be whether there is a previous TA report (eg, in the same cell).
[0308] Return to reference Figure 3 and Figure 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 a second configuration for configuring a TA report in the RRC connected mode, and (ii) determine to trigger the TA report in response to receiving the second configuration (or at this time) based on satisfying (at least) one or more conditions. 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.
[0309] Return to Figure 3 and Figure 4In one or more embodiments from the perspective of the NW, 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) transmit a second configuration for configuring a TA report in the RRC connected mode, and (ii) determine at the UE that a TA report is triggered in response to receiving the second configuration (or at this time) based on satisfying (at least) one or more conditions. 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.
[0310] See also Fig.16 , with respect to such and other concepts, systems and methods of the present invention, a method 1010 for a UE in a wireless communication system includes receiving a second configuration for configuring a TA report in an RRC connected mode (step 1012), evaluating a TA offset for the TA report in the RRC connected mode (step 1014), and triggering a TA report in response to the TA offset being above a configured threshold (or at this time) (step 1016).
[0311] In various embodiments, the TA offset is an offset between a current TA and a first TA based on satisfying (at least) one or more conditions.
[0312] In various embodiments, the TA offset is an offset between a current TA and a last reported TA based on (at least) one or more conditions not being met.
[0313] In various embodiments, the condition may be whether TA reporting at / during the RA procedure is enabled.
[0314] In various embodiments, the condition may be whether there is a previous TA report (eg, in the same cell).
[0315] Return to reference Figure 3 and Figure 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 a second configuration for configuring a TA report in the RRC connected mode, (ii) evaluate a TA offset for the TA report in the RRC connected mode, and (iii) trigger a TA report in response to the TA offset being above a configured threshold (or at this time). 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.
[0316] Return to Figure 3 and Figure 4In one or more embodiments from the perspective of the NW, 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) transmit a second configuration for configuring TA reporting in RRC connected mode, (ii) evaluate a TA offset for TA reporting in RRC connected mode at the UE, and (iii) trigger a TA report at the UE in response to the TA offset being above a configured threshold (or at this time). 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.
[0317] See also Fig.17 , with respect to such and other concepts, systems and methods of the present invention, a method 1020 for a UE in a wireless communication system includes receiving a first configuration of a TA report (step 1022), receiving a second configuration of the TA report (step 1024), and determining whether to trigger a second TA report immediately after receiving the second configuration based on whether the first TA report has been transmitted to a serving cell (step 1026). Fig.18 An example is shown in FIG.
[0318] In various embodiments, the method further includes triggering a first TA report based on the first configuration being enabled, and not triggering a second TA report immediately after receiving the second configuration based on the first TA report having been transmitted to the serving cell. Fig.18 An example is shown in the upper part of .
[0319] In various embodiments, the method further includes not triggering the first TA report based on the first configuration not being enabled, and triggering the second TA report upon receiving the second configuration based on the first TA report not being transmitted to the serving cell. Fig.18 An example is shown in the lower part of .
[0320] In various embodiments, the first configuration is a configuration to enable TA reporting during RA for initial access, RRC connection resumption, RRC connection re-establishment, and / or handover.
[0321] In various embodiments, the second configuration is a configuration to enable event-triggered TA reporting.
[0322] In various embodiments, the first TA report is transmitted to the serving cell during the RA procedure or a subsequent transmission after the RA procedure.
[0323] In various embodiments, the RA procedure is associated with a procedure of initial access, RRC connection recovery, RRC connection re-establishment or handover, and / or wherein the second configuration is received after the RA procedure.
[0324] In various embodiments, the method further includes triggering a third TA report based on the second configuration if a TA offset between the current TA information and the TA information included in the first TA report is greater than or equal to a TA offset threshold.
[0325] In various embodiments, the TA report is a Timing Advance Report (TAR) MAC CE.
[0326] In various embodiments, the first configuration is received in system information (eg, SIB) and / or wherein the second configuration is received in dedicated signaling (eg, an RRCReconfiguration message or an RRCConnectionReconfiguration message).
[0327] Return to reference Figure 3 and Figure 4 In 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 configuration of a TA report, (ii) receive a second configuration of a TA report, and (iii) determine whether to trigger a second TA report upon receiving the second configuration based on whether the first TA report has been transmitted to the serving cell. 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.
[0328] Back again Figure 3 and Figure 4 In one or more embodiments from the perspective of the NW, 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) transmit a first configuration of a TA report, (ii) transmit a second configuration of a TA report, and (iii) determine at the UE whether to trigger a second TA report upon receiving the second configuration based on whether the first TA report has been transmitted to the serving cell. 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.
[0329] Any combination of the above concepts or teachings can be combined or formed into new embodiments. The disclosed details and embodiments can be used to at least (but not limited to) solve the problems mentioned above and herein.
[0330] 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.
[0331] 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.
[0332] 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.
[0333] 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 this 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.
[0334] 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.
[0335] 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 the specific order or hierarchy of steps in a process can be rearranged based on design preferences while remaining within the scope of the present disclosure. The attached method claims present the elements of the various steps in an exemplary order and are not meant to be limited to the specific order or hierarchy presented.
[0336] 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.
[0337] Although the present invention has been described in conjunction with various aspects and examples, it will be appreciated that the present invention is capable of further modifications. This application is intended to cover any changes, uses or adaptations of the present invention, which generally follow the principles of the present invention and include such deviations from the present disclosure, which are within the scope of known and customary practice in the technical field to which the present invention belongs.
Claims
1. A method for a user equipment UE, comprising: receiving a first configuration of a timing advance (TA) report in system information; A second configuration for receiving a TA report; as well as Determining whether to trigger a second TA report immediately after receiving the second configuration based on whether the first TA report has been transmitted to the serving cell includes: triggering the second TA report immediately after receiving the second configuration based on the first TA report not being transmitted to the serving cell.
2. The method according to claim 1, further comprising: triggering the first TA report based on the first configuration being enabled; as well as The second TA report is not triggered immediately after receiving the second configuration based on that the first TA report has been transmitted to the serving cell.
3. The method according to claim 1, further comprising: The first TA report is not triggered based on that the first configuration is not enabled.
4. The method of claim 1, wherein the first configuration is a configuration to enable TA reporting during random access (RA) for initial access, radio resource control (RRC) connection resumption, RRC connection reestablishment, and / or handover. The method of claim 1 , wherein the second configuration is a configuration to enable event-triggered TA reporting. 6 . The method of claim 1 , wherein the first TA report is transmitted to the serving cell during a RA procedure or a subsequent transmission after the RA procedure.
7. The method according to claim 6, wherein the RA procedure is related to a procedure of initial access, RRC connection recovery, RRC connection re-establishment or handover, and / or wherein the second configuration is received after the RA procedure.
8. The method according to claim 1, further comprising: If a TA offset between current TA information and TA information included in the first TA report is greater than or equal to a TA offset threshold, triggering a third TA report based on the second configuration.
9. The method of claim 1, wherein the TA report is a Timing Advance Report (TAR) Medium Access Control (MAC) Control Element (CE).
10. The method of claim 1, wherein the second configuration is received in dedicated signaling, wherein the dedicated signaling is an RRCReconfiguration message or an RRCConnectionReconfiguration message.
11. A user equipment UE, comprising: Memory; as well as a processor operatively coupled to the memory, wherein the processor is configured to execute program code to: receiving a first configuration of a timing advance (TA) report in system information; A second configuration for receiving a TA report; as well as Determining whether to trigger a second TA report immediately after receiving the second configuration based on whether the first TA report has been transmitted to the serving cell includes: triggering the second TA report immediately after receiving the second configuration based on the first TA report not being transmitted to the serving cell.
12. The UE of claim 11, wherein the processor is further configured to execute program code to: triggering the first TA report based on the first configuration being enabled; and The second TA report is not triggered immediately after receiving the second configuration based on that the first TA report has been transmitted to the serving cell.
13. The UE of claim 11, wherein the processor is further configured to execute program code to: The first TA report is not triggered based on that the first configuration is not enabled.
14. The UE of claim 11, wherein the first configuration is a configuration to enable TA reporting during random access (RA) for initial access, radio resource control (RRC) connection resumption, RRC connection reestablishment, and / or handover.
15. The UE of claim 11, wherein the second configuration is a configuration to enable event-triggered TA reporting. 16 . The UE of claim 11 , wherein the first TA report is transmitted to the serving cell during a RA procedure or a subsequent transmission after the RA procedure.
17. The UE according to claim 16, wherein the RA procedure is related to a procedure of initial access, RRC connection recovery, RRC connection re-establishment or handover, and / or wherein the second configuration is received after the RA procedure.
18. The UE of claim 11, wherein the processor is further configured to execute program code to: If a TA offset between current TA information and TA information included in the first TA report is greater than or equal to a TA offset threshold, triggering a third TA report based on the second configuration.
19. The UE of claim 11, wherein the TA report is a Timing Advance Report (TAR) Medium Access Control (MAC) Control Element (CE).
20. The UE of claim 11, wherein the second configuration is received in dedicated signaling, wherein the dedicated signaling is an RRCReconfiguration message or an RRCConnectionReconfiguration message.
Citation Information
Patent Citations
Method and apparatus in a wireless communication system for identifying uplink timing advance
CN108024387A
Timing advance for non-terrestrial network communication
CN112154707A
Methods for reporting timing advance in non-terrestrial network communications and communication apparatus utilizing the same
WO2021230815A1
