Measurement method and terminal device

Abstract

The invention provides a measurement method and terminal equipment. The measurement method comprises the steps that the terminal equipment determines to execute a first GNSS operation according to a first condition, and the first condition is related to GNSS measurement. In the embodiment of the invention, the terminal equipment can determine the subsequent GNSS operation according to the condition (the first condition) related to the GNSS measurement. Thus, the terminal device can execute different GNSS operations according to the first condition to complete GNSS measurement, which is beneficial to formulating a reasonable GNSS measurement scheme, thereby being beneficial to saving signaling overhead or reducing service transmission delay.

Description

Measurement methods and terminal equipment Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a measurement method and terminal equipment. Background Art

[0002] In some communication systems (e.g., new radio (NR) systems), a terminal device connected to a non-terrestrial network (NTN) can perform global navigation satellite system (GNSS) measurements while in the radio resource control (RRC) connected state. However, it is currently unclear how the terminal device should perform GNSS measurements when the terminal device's GNSS position information is invalid or unavailable after the introduction of the solution for performing GNSS measurements in the RRC connected state.

[0003] Summary of the Invention

[0004] This application provides a measurement method and terminal device. The following introduces various aspects involved in this application.

[0005] In a first aspect, a measurement method is provided, including: a terminal device determines to perform a first GNSS operation according to a first condition, wherein the first condition is related to GNSS measurement.

[0006] In a second aspect, a terminal device is provided, including: a determination module, configured to determine to perform a first GNSS operation according to a first condition, wherein the first condition is related to GNSS measurement.

[0007] In a third aspect, a terminal device is provided, comprising a processor and a memory, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the terminal device executes part or all of the steps in the method of the first aspect.

[0008] In a fourth aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned terminal device. In another possible design, the system may also include other devices that interact with the terminal device in the solution provided in the embodiment of the present application.

[0009] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program enables a terminal device to execute part or all of the steps in the methods of the above aspects.

[0010] In a sixth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a terminal device to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.

[0011] In the seventh aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0012] In the embodiment of the present application, the terminal device can determine subsequent GNSS operations based on a condition related to GNSS measurement (a first condition). In this way, the terminal device can perform different GNSS operations based on the first condition to complete the GNSS measurement, which is conducive to formulating a reasonable GNSS measurement plan, thereby saving signaling overhead or reducing service transmission delay. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] FIG1 is a diagram illustrating an example of a system architecture of a wireless communication system to which an embodiment of the present application may be applied.

[0014] FIG2 is an example diagram of a transparent forwarding NTN network architecture.

[0015] FIG3 is an example diagram of a regeneration and forwarding NTN network architecture.

[0016] FIG4 is a flow chart of a measurement method according to an embodiment of the present application.

[0017] FIG5 is a flow chart of a measurement method provided in another embodiment of the present application.

[0018] FIG6 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application.

[0019] FIG7 is a schematic structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0020] Communication system architecture

[0021] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, advanced long term evolution (LTE-A) system, new radio (NR) system, evolution system of NR system, LTE-based access to unlicensed spectrum (LTE-U) system on unlicensed spectrum, NR-based access to unlicensed spectrum (NR-U) system on unlicensed spectrum, NTN system, universal mobile telecommunication system (UMTS), wireless local area networks (WLAN), wireless fidelity (WLAN), etc. fidelity, WiFi), fifth-generation communication (5G) systems or other communication systems, such as future communication systems, such as sixth-generation mobile communication systems, and satellite communication systems.

[0022] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, and the embodiments of the present application can also be applied to these communication systems.

[0023] The communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0024] The communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as a dedicated spectrum.

[0025] The embodiments of the present application can be applied to NTN systems as well as terrestrial networks (TN) systems. By way of example and not limitation, NTN systems include NR-based NTN systems and Internet of Things (IoT)-based NTN systems. For example, in scenarios where narrowband Internet of Things (NB-IoT) and enhanced machine type communications (eMTC) are connected to NTN, the system consisting of IoT terminal devices and NTN networks can be understood as an IoT-based NTN system.

[0026] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, where the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0027] In an embodiment of the present application, the terminal device may be a station (STATION, ST) in a WLAN, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a next-generation communication system such as a terminal device in an NR network, or a terminal device in a future-evolved public land mobile network (PLMN) network, etc.

[0028] In an embodiment of the present application, a terminal device may be a device that provides voice and / or data connectivity to a user and can be used to connect people, objects, and machines, such as a handheld device with wireless connection capabilities, an in-vehicle device, etc. The terminal device in the embodiment of the present application may be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the terminal device may be used to act as a base station. For example, the terminal device may act as a scheduling entity that provides sidelink signals between terminal devices in V2X or D2D, etc. For example, a cellular phone and a car communicate with each other using sidelink signals. Cellular phones and smart home devices communicate with each other without relaying the communication signal through a base station.

[0029] The network device in the embodiments of the present application may be a device for communicating with a terminal device, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. A base station may broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. The base station may also refer to a communication module, modem or chip provided in the aforementioned device or apparatus. The base station may also be a mobile switching center and a device-to-device D2D, vehicle-to-everything (V2X), machine-to-machine (M2M) communication device that performs the base station function, a network side device in a 6G network, a device that performs the base station function in a future communication system, etc. The base station may support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network equipment.

[0030] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0031] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device may include a CU and a DU. The gNB may also include an AAU.

[0032] The network equipment and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which the network equipment and terminal devices are located.

[0033] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. In some embodiments of the present application, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. In some embodiments of the present application, the network device may also be a base station set up in a location such as land or water.

[0034] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0035] For example, Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application. As shown in Figure 1, communication system 100 may include a network device 110 and a terminal device 120. Network device 110 may be a device that communicates with terminal device 120 (or referred to as a communication terminal or terminal). Network device 110 may provide communication coverage for a specific geographic area and may communicate with terminal devices within the coverage area. For example, the network device may be a satellite.

[0036] Figure 1 exemplarily shows a network device and two terminal devices. In some embodiments of the present application, the communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0037] It should be noted that Figure 1 only illustrates the system to which the present application is applicable in the form of an example. Of course, the method shown in the embodiment of the present application can also be applied to other systems, such as 5G communication systems, LTE communication systems, etc., and the embodiment of the present application does not make specific limitations on this.

[0038] In some embodiments of the present application, the wireless communication system shown in Figure 1 may also include other network entities such as a mobility management entity (MME) and an access and mobility management function (AMF), but the embodiments of the present application are not limited to this.

[0039] As previously mentioned, the technical solutions provided by the embodiments of this application can be applied to NTN systems. To facilitate understanding, some relevant technical knowledge involved in the embodiments of this application (e.g., the NTN network architecture) is first introduced. The following related technologies, as optional solutions, can be combined with the technical solutions of the embodiments of this application in any manner and fall within the scope of protection of the embodiments of this application. The embodiments of this application include at least some of the following:

[0040] NTN

[0041] The Third Generation Partnership Project (3GPP) is currently researching NTN technology. NTN typically uses satellite communications to provide communication services to terrestrial users. Compared to terrestrial communication networks (e.g., terrestrial cellular networks), satellite communications offer many unique advantages.

[0042] First, satellite communications are not restricted by user geography. For example, conventional terrestrial communication networks cannot cover areas where network equipment cannot be deployed, such as oceans, mountains, and deserts. Alternatively, terrestrial communication networks cannot cover certain areas due to sparse populations. However, satellite communications, because a single satellite can cover a large ground area and orbits the Earth, theoretically, every corner of the Earth can be covered by a satellite communication network.

[0043] Secondly, satellite communications have significant social value. They can provide low-cost coverage to remote, mountainous areas and impoverished countries and regions, enabling people in these areas to enjoy advanced voice communications and mobile internet technologies. From this perspective, satellite communications help narrow the digital divide with developed regions and promote their development.

[0044] Again, satellite communication has a long distance, and the communication cost does not increase significantly with the increase of communication distance.

[0045] Finally, satellite communications are highly stable and not affected by natural disasters.

[0046] Communication satellites can be divided into LEO satellites, MEO satellites, GEO satellites, HEO satellites, etc. according to the different orbital altitudes. At the current stage, the main research is on LEO satellites and GEO satellites.

[0047] LEO satellites typically operate at altitudes between 500 and 1500 km. Accordingly, their orbital period is approximately 1.5 to 2 hours. For LEO satellites, the signal propagation delay for single-hop communication between users is typically less than 20 milliseconds. The maximum satellite visibility time for LEO satellites is approximately 20 minutes. LEO satellites offer advantages such as short signal propagation distances, low link loss, and low transmit power requirements for terminal devices.

[0048] GEO satellites orbit at an altitude of approximately 35,786 km. They orbit the Earth every 24 hours. For GEO satellites, the signal propagation delay for single-hop communication between users is typically about 250 milliseconds.

[0049] To ensure satellite coverage and increase the capacity of the entire satellite communication system, satellites typically use multiple beams to cover the ground. Therefore, a single satellite can form dozens or even hundreds of beams to cover the ground. A single satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers.

[0050] Currently, NTN systems can include NR NTN systems and IoT NTN systems.

[0051] NTN Network Architecture

[0052] The NTN network architecture may include the following network elements: gateway, feeder link, service link and satellite.

[0053] The NTN network architecture may include one or more gateways, which may be used to connect satellites and terrestrial public networks.

[0054] A feeder link may refer to a link for communication between a gateway and a satellite.

[0055] The service link may refer to a link for communication between a terminal device and a satellite.

[0056] In terms of the functions provided by satellites, they can be categorized as those with transparent payloads or those with regenerative payloads. Transparent payload satellites provide only radio frequency filtering, frequency conversion, and amplification. In other words, transparent payload satellites transparently forward signals without altering the waveform of the transmitted signal. Regenerative payload satellites, in addition to providing radio frequency filtering, frequency conversion, and amplification, can also provide one or more of the following functions: demodulation, decoding, routing, conversion, encoding, and modulation. Regenerative payload satellites can have some or all of the functions of a base station. Depending on the functions provided by satellites in an NTN network, NTN network architectures can be categorized as either transparent or regenerative. Figures 2 and 3 provide example diagrams of transparent and regenerative payload NTN architectures, respectively.

[0057] In some embodiments, the NTN network architecture may further include inter-satellite links (ISLs). For example, ISLs may exist in a regenerative forwarding NTN network architecture.

[0058] Timing advance (TA) in TN

[0059] A key feature of uplink transmission is orthogonal multiple access (MA) across different devices in time and frequency. This means that uplink transmissions from different devices in the same cell do not interfere with each other. To ensure orthogonality in uplink transmissions and avoid intra-cell interference, network equipment requires that signals from different devices at the same time but using different frequency resources arrive at the network equipment at essentially aligned times. To ensure time synchronization on the network equipment side, communication systems (e.g., LTE / NR) can support an uplink TA mechanism.

[0060] In a communication system that supports uplink TA, the uplink and downlink clocks on the network device are identical, while those on the terminal device are offset, and different terminal devices have different uplink TA values. By appropriately controlling the offset for each terminal device, the network device can control the time it takes for uplink signals from different terminal devices to reach the network device. Terminal devices farther from the network device experience greater transmission delays and therefore need to send uplink data earlier than closer terminal devices.

[0061] The network device can determine the TA value of each terminal device by measuring the uplink transmission of the terminal device. The network device can send a TA command to the terminal device to notify the terminal device of its corresponding TA value. For example, the network device can send a TA command to the terminal device in two ways, as follows:

[0062] Method 1: Acquisition of initial TA: During the random access process, the network device can determine the TA value by measuring the received preamble and send it to the terminal device through the Timing Advance Command field of the random access response (RAR) message.

[0063] Method 2: Adjustment of TA in RRC connection state: Although the terminal device and the network device have achieved uplink synchronization during the random access process, the timing of the uplink signal reaching the network device may change over time. Therefore, the terminal device needs to continuously update its uplink TA amount to maintain uplink synchronization. If the TA of a terminal device needs to be corrected, the network device can send a TA command (Timing Advance Command) to the terminal device, requesting it to adjust the uplink timing. In some implementations, the TA command is sent by the network device to the terminal device through a media access control control element (MAC CE). This MAC CE can also be called a TA command MAC CE (i.e., a MAC CE carrying a TA command).

[0064] TA in NTN

[0065] From the above description, it can be seen that in the traditional TN network, the terminal device can perform TA maintenance based on the TA command issued by the network device. Like the TN system, in the NTN system (such as version 17 (release 17, R17)), the terminal device also needs to consider the impact of TA when performing uplink transmission. In the NTN system, the terminal device usually has GNSS positioning capability and TA pre-compensation capability. The terminal device can estimate the TA corresponding to the service link based on the location of the terminal device and the location of the service satellite. As an implementation method, a TA determination method combining open loop and closed loop is introduced in NTN. Based on the conclusions of the current standardization meeting, for terminal devices in RRC idle state (RRC_IDLE) / RRC inactive state (RRC_INACTIVE) and RRC connected state (RRC_CONNECTED), the TA of the terminal device connected to the NTN can be calculated by the following formula:

[0066] T TA =(N TA +N TA,UE-specific +N TA,common +N TA,offset )×T c

[0067] Among them, T TA Refers to the TA of the terminal equipment connected to NTN. TA It is the TA adjustment amount controlled by the network device. It is defined as 0 for the scenario sent by the physical random access channel (PRACH). It can be updated later through the TA command in message 2 (Msg2) or message B (MsgB) and the TA command MAC CE. TA,UE-specific The TA corresponding to the service link estimated by the terminal device itself (or service link TA) is used for TA pre-compensation. As an implementation method, the terminal device can obtain the satellite position based on its own GNSS position information combined with the satellite ephemeris information broadcast by the serving cell, thereby calculating the propagation delay of the service link from the terminal device to the satellite. TA,common The common TA controlled by network equipment includes any timing deviation that the network considers necessary, for example, it can be the TA corresponding to the feeder link, or it can be other values. TA,offset It is a preset offset value, for example, it can be a fixed offset value for calculating TA.

[0068] From the above formula, it can be seen that the terminal device connected to the NTN (for example, the NTN terminal device in the RRC connection state) needs to obtain the TA corresponding to the service link (i.e., N TA,UE-specifi c), on the one hand, it needs to know its own GNSS position information, and on the other hand, it needs to know the position of the serving satellite through the serving cell satellite ephemeris information. In addition, in order to calculate the TA of the terminal device, the UE also needs to obtain the public TA (i.e. N TA,common ).

[0069] GNSS Operations for IoT NTN

[0070] In IoT NTN (for example, scenarios where NB-IoT and eMTC terminal devices are connected to NTN), the GNSS measurement module and communication module of the IoT terminal device cannot operate simultaneously (Simultaneous GNSS and NTN NB-IoT / eMTC operation is not assumed). In R17IoT NTN, IoT terminal devices can only perform GNSS measurements in RRC idle state or RRC inactive state to obtain GNSS location information, and the GNSS module cannot be started in RRC connected state. To this end, the terminal device needs to obtain its own GNSS position through the GNSS module before entering the RRC connected state. The terminal device can then determine the validity period of the GNSS position based on its own situation (such as the mobility status of the terminal device) and report the remaining valid time corresponding to the GNSS position to the network when the RRC connection is established / RRC re-established / RRC restored. For a terminal device in the RRC connected state, when its GNSS position expires, since the terminal device cannot perform GNSS operations in the RRC connected state, the terminal device cannot perform certain subsequent operations based on the GNSS position information, such as being unable to calculate TA. In this case, the terminal device needs to return to the RRC idle state to perform GNSS operations.

[0071] Release 18 (R18) proposes to enhance the performance of IoT NTN to address the legacy issues of R17. When R18 enhances the performance of IoT NTN, it takes R17IoT-NTN as the baseline and builds on the results of R17NR-NTN. Further goals of IoT-NTN performance enhancement are as follows: (1) disabling of hybrid automatic repeat request (HARQ) feedback to mitigate the impact of HARQ stalling on UE data rates; (2) study and specify, if needed, improved GNSS operations for a new position fix for UE pre-compensation during long connection times and for reduced power consumption.

[0072] Based on the above research objectives, R18 discusses the ability of IoT terminal devices connected to the NTN to perform GNSS measurements (or, more accurately, obtain GNSS position information (GNSS position fix)) in the RRC connected state. Specifically, the conclusions reached after discussing GNSS enhancements for IoT terminal devices connected to the NTN in R18 may include the following aspects.

[0073] First, IoT NTN terminal devices may need to reacquire valid GNSS location information during a long RRC connection. In addition, in this case, it is also necessary to consider how the terminal device can update or reduce the need to update GNSS location information during the RRC connection state.

[0074] Secondly, how does the terminal device perform GNSS measurements when in the RRC connected state? For example, the following candidate solutions can be considered: Solution 1, the terminal device reacquires GNSS position information based on timer control; Solution 2, a new measurement gap is introduced, during which the terminal device reacquires GNSS position information.

[0075] Thirdly, how to trigger GNSS measurement when the terminal device is in RRC connected state. As one possible implementation, the GNSS measurement can be triggered by the network. As another possible implementation, the GNSS measurement can be triggered by the terminal device.

[0076] It can be seen that the terminal device can currently perform GNSS measurements in the RRC connected state. However, it is not clear how the terminal device should perform GNSS measurements when the GNSS location information of the terminal device is invalid or unavailable after the scheme for the terminal device to perform GNSS measurements in the RRC connected state is introduced. For example, if the current GNSS location information of the terminal device is invalid or unavailable, and the terminal device does not receive an instruction from the network device to trigger GNSS measurements, how should the terminal device perform GNSS measurements. For another example, assuming that the terminal device does not receive an instruction from the network device to trigger GNSS measurements, the terminal device can spontaneously perform GNSS measurements, but whether the terminal device can spontaneously perform GNSS measurements may depend on the configuration of the network device. In this case, if the network device does not configure the terminal device to enable the terminal device to autonomously initiate GNSS measurements, then when the current GNSS location information of the terminal device is invalid or unavailable, how should the terminal device perform GNSS measurements? There is currently no clear solution.

[0077] Therefore, when the current GNSS location information of the terminal device is invalid or unavailable, how the UE should perform GNSS measurement is a problem that needs to be solved.

[0078] To address the above issues, embodiments of the present application provide a measurement method and terminal device, enabling the terminal device to determine subsequent GNSS operations based on conditions related to GNSS measurements (i.e., the first condition described below). In this way, the terminal device can perform different GNSS operations based on the first condition to complete the GNSS measurement, which is beneficial for developing a reasonable GNSS measurement plan, thereby saving signaling overhead or reducing service transmission latency. The following describes an embodiment of the method of the present application in conjunction with Figures 4 and 5.

[0079] Figure 4 is a schematic flow chart of a measurement method provided in an embodiment of the present application. The method shown in Figure 4 can be executed by a terminal device, such as any of the terminal devices shown in Figures 1-3. In some embodiments, the terminal device can be a terminal device connected to an NTN. In some embodiments, the terminal device can be a terminal device in an RRC connected state.

[0080] The method shown in FIG4 may include step S410 , which is described below.

[0081] In step S410, the terminal device determines to perform a first GNSS operation according to a first condition, wherein the first condition is related to GNSS measurement.

[0082] In the embodiment of the present application, the first condition is a condition related to GNSS measurement, or in other words, the first condition is determined based on information associated with GNSS measurement.

[0083] In some embodiments, conditions related to GNSS measurement or information associated with GNSS measurement may include relevant information for indicating how the terminal device triggers GNSS measurement when in RRC connected state, such as relevant information of network-triggered GNSS measurement or terminal device-triggered GNSS measurement.

[0084] In some embodiments, conditions related to GNSS measurements or information associated with GNSS measurements may include relevant information on how the terminal device performs GNSS measurements when in an RRC connected state, for example, the terminal device can perform GNSS measurements based on a timer or the terminal device can perform GNSS measurements based on measurement gaps, etc.

[0085] In some embodiments, the conditions related to GNSS measurement or the information associated with GNSS measurement may include indication information for indicating whether the terminal device is allowed to perform GNSS measurement in the RRC connected state.

[0086] In the embodiments of the present application, in addition to the information listed above, the conditions related to GNSS measurements or the information associated with GNSS measurements may also include other GNSS-related information, such as resource information corresponding to the terminal device performing GNSS measurements, etc., which is not limited in the embodiments of the present application. The following exemplifies a preferred solution for the first condition mentioned in the embodiments of the present application.

[0087] In some embodiments, the first condition may be associated with one or more of the following information: information triggering the GNSS measurement, and time information for performing the GNSS measurement.

[0088] In some embodiments, the information triggering the GNSS measurement may include an instruction from the network to trigger the GNSS measurement. The terminal device may determine whether the network requires the terminal device to perform the GNSS measurement based on the information triggering the GNSS measurement.

[0089] In some embodiments, the information triggering the GNSS measurement may be sent by the network device to the terminal device.

[0090] In some embodiments, the terminal device may determine the time domain location for performing the GNSS measurement based on the time information for performing the GNSS measurement, so as to perform the GNSS measurement at the time domain location. In some embodiments, the time information for performing the GNSS measurement may include information about the GNSS measurement gap, so that the terminal device may perform the GNSS measurement in the measurement gap. However, the embodiments of the present application are not limited thereto. Exemplarily, the time information for performing the GNSS measurement may further include, for example, an indication information, which is used to indicate a time domain location (e.g., one or more time slots, one or more symbols, etc.), so that the terminal device performs the GNSS measurement at the corresponding time domain location.

[0091] In some embodiments, the time information for performing the GNSS measurement may be sent by the network device to the terminal device.

[0092] In some embodiments, the first condition may include one or more of the following: the terminal device receives information triggering GNSS measurement, and the terminal device receives information about a GNSS measurement gap.

[0093] In the embodiment of the present application, the terminal device may determine to perform the first GNSS operation based on the first condition. In other words, the terminal device may perform different GNSS operations based on whether the first condition and / or different first conditions are met, so as to determine a more optimal GNSS measurement solution for the terminal device in the current situation.

[0094] In some embodiments, the first GNSS operation may be used to indicate a manner in which the terminal device performs GNSS measurement, that is, the terminal device may determine a manner in which the GNSS measurement is performed according to the first condition, and perform the GNSS measurement based on the manner.

[0095] In some embodiments, the first GNSS operation may be used to instruct the terminal device to remain in the RRC connected state to perform GNSS measurements. In some embodiments, the first GNSS operation may be used to instruct the terminal device to leave the RRC connected state (e.g., enter the RRC idle state or the RRC inactive state) to perform GNSS measurements.

[0096] Exemplarily, the first GNSS operation may include one or more of the following: performing GNSS measurement based on time information of GNSS measurement; triggering RRC connection reestablishment and performing GNSS measurement before initiating RRC connection reestablishment request; and entering RRC idle state and performing GNSS measurement before the next RRC connection is established.

[0097] Depending on the first condition and the first GNSS operation, the terminal device may determine to perform the first GNSS operation according to the first condition, which may include multiple different possibilities. This is exemplarily introduced below with reference to FIG. 5 .

[0098] In some embodiments, the terminal device determining to perform the first operation according to the first condition may include: if the terminal device meets the first condition, the terminal device determining to perform GNSS measurement based on time information of the GNSS measurement.

[0099] For example, if the terminal device receives information about a GNSS measurement gap, the terminal device may determine to perform a GNSS measurement based on the received GNSS measurement gap. Alternatively, if the terminal device receives information triggering a GNSS measurement, the terminal device may perform a GNSS measurement based on the information triggering the GNSS measurement. Alternatively, if the terminal device receives information triggering a GNSS measurement and information about a GNSS measurement gap, the terminal device may perform a GNSS measurement in the corresponding GNSS measurement gap based on the information triggering the GNSS measurement.

[0100] In some embodiments, after the terminal device performs GNSS measurement based on the time information of the GNSS measurement, the terminal device may start or restart a first timer. During the operation of the first timer, the terminal device may consider the current GNSS location information to be valid or usable. For relevant information about the first timer, please refer to the description below and will not be repeated here.

[0101] In an embodiment of the present application, when the terminal device meets the first condition (for example, there is a GNSS measurement gap), the terminal device can be kept in the RRC connected state as much as possible, and GNSS measurement can be performed based on the information triggering the GNSS measurement and / or using the GNSS measurement gap, thereby saving signaling overhead and reducing service interruption.

[0102] In some embodiments, the terminal device determines to perform the first operation according to the first condition, which may include: if the terminal device does not meet the first condition, the terminal device determines to trigger RRC connection reconstruction, and performs GNSS measurement before initiating the RRC connection reconstruction request.

[0103] For example, if the terminal device receives neither information triggering GNSS measurement nor information about GNSS measurement gap, the terminal device may trigger RRC connection reestablishment and perform GNSS measurement before initiating an RRC connection reestablishment request.

[0104] In some embodiments, if the terminal device does not meet the first condition and the terminal device cannot autonomously initiate GNSS measurement, the terminal device determines to trigger RRC connection reestablishment and performs GNSS measurement before initiating the RRC connection reestablishment request. It should be understood that in this case, the first condition and the condition of whether the terminal device can autonomously initiate GNSS measurement can be considered as parallel conditions. If neither condition is met, RRC connection reestablishment can be triggered and GNSS measurement can be performed before initiating the RRC connection reestablishment request; if one or more of the two conditions are met, GNSS measurement can be performed based on the information triggering GNSS measurement / GNSS measurement gap, or GNSS measurement can be performed autonomously.

[0105] In some embodiments, the terminal device cannot autonomously start GNSS measurement, which may include: the network device does not configure the terminal device to automatically start GNSS measurement in the RRC connection state.

[0106] In some embodiments, triggering of RRC connection reestablishment by a terminal device is dependent on the configuration of a network device. That is, only when the network device has configured the terminal device to trigger RRC connection reestablishment while the terminal device is in an RRC connected state can the terminal device trigger RRC connection reestablishment even when the first condition is not met and perform GNSS measurements before initiating an RRC connection reestablishment request.

[0107] In some embodiments, the network device configures for the terminal device whether the terminal device can trigger RRC connection reconstruction when in the RRC connected state, which may mean that the network device configures for the terminal device whether the terminal device can trigger RRC connection reconstruction when in the RRC connected state when conditions related to GNSS measurement are not met.

[0108] In the embodiment of the present application, the terminal device performs GNSS measurement by triggering the RRC connection reestablishment process, which saves more high-level signaling and reduces service transmission delay than performing GNSS measurement by entering the RRC idle state.

[0109] In some embodiments, the terminal device determines to perform the first operation according to the first condition, which may include: if the terminal device does not meet the first condition, the terminal device determines to enter the RRC idle state and performs GNSS measurement before the next RRC connection is established.

[0110] For example, if the terminal device receives neither information triggering GNSS measurement nor information indicating a GNSS measurement gap, the terminal device may enter the RRC idle state and perform GNSS measurement before the next RRC connection is established.

[0111] In some embodiments, if the terminal device does not meet the first condition and the terminal device cannot autonomously initiate GNSS measurement, the terminal device determines to enter the RRC idle state and perform GNSS measurement before the next RRC connection is established. It should be understood that in this case, the first condition and the condition of whether the terminal device can autonomously initiate GNSS measurement can be considered as parallel conditions. If neither condition is met, the terminal device can enter the RRC idle state and perform GNSS measurement before the next RRC connection is established; if one or more of the two conditions are met, the terminal device can perform GNSS measurement based on the information triggering the GNSS measurement / GNSS measurement gap, or can autonomously perform GNSS measurement.

[0112] In the embodiment of the present application, the terminal device can enter the RRC idle state to perform GNSS measurement, and the implementation method is simpler.

[0113] In some embodiments, if the terminal device does not meet the first condition but the terminal device is capable of autonomously initiating GNSS measurement, the terminal device may choose to autonomously initiate GNSS measurement. For example, if the network device configures autonomous triggering of GNSS measurement for the terminal device, the terminal device may autonomously initiate GNSS measurement based on the configuration.

[0114] In summary, in the embodiments of the present application, depending on the difference of the first condition and the difference of the first GNSS operation, the terminal device can determine to perform different GNSS operations according to the first condition, for example, determine whether to remain in the RRC connected state and use the GNSS measurement gap to perform GNSS measurement, or trigger RRC connection reconstruction and complete GNSS measurement before initiating the reconstruction process, or return to the RRC idle state and complete GNSS measurement before a subsequent RRC connection is established, etc.

[0115] Continuing with FIG5 , in some embodiments, when a first event is triggered (occurs), the terminal device may determine to perform a first GNSS operation based on a first condition. In other words, the terminal device's determination to perform the first GNSS operation based on the first condition may be triggered by the first event. The first event may indicate that the current GNSS location information of the terminal device is invalid or unavailable.

[0116] In some embodiments, the first event may include one or more of the following: the terminal device determines (or judges) that the current GNSS position information of the terminal device is invalid or unavailable, and a timer times out.

[0117] The embodiments of the present application do not specifically limit the manner in which a terminal device determines whether the current GNSS location information of the terminal device is valid / available. For example, the terminal device may determine whether the current GNSS location information is valid / available based on whether a timer has expired, or the terminal device may determine whether the current GNSS location information is valid / available based on the terminal device's mobility and historically acquired GNSS location information.

[0118] In some embodiments, the timer may include a first timer, for example, a GNSS validity timer.

[0119] In some embodiments, during the running of the first timer, the terminal device may consider the current GNSS location information to be valid or usable. Alternatively, when the first timer expires, the terminal device may consider the current GNSS location information to be invalid or unusable.

[0120] In some embodiments, the first timer may be started or restarted each time the terminal device performs GNSS measurement or obtains GNSS location information.

[0121] The embodiment of the present application does not limit the timing duration of the first timer, and can be set according to actual conditions.

[0122] In some embodiments, the timing duration of the first timer may be determined by the terminal device. In some embodiments, the timing duration of the first timer may be configured by the network device. As an implementation, the network device may configure the timing duration of the first timer through system information (e.g., system information block (SIB)) or RRC dedicated signaling.

[0123] In some embodiments, the above-mentioned timer timeout may include a first timer timeout.

[0124] In some embodiments, the timer may include a second timer. In some embodiments, the second timer may be used to control the duration for which the terminal device considers the current GNSS position information to be valid or the duration for which the terminal device considers the uplink synchronization to be in progress.

[0125] In some embodiments, the second timer may be started or restarted each time the terminal device receives information about the TA adjustment and / or the frequency domain offset adjustment. In this case, it can be considered that the uplink time domain adjustment and the uplink frequency domain adjustment are controlled simultaneously by the network, for example, by the same signaling (such as MAC CE signaling), or in other words, in this case, it can be considered that the same timer (second timer) can be maintained for the uplink time domain adjustment and the uplink frequency domain adjustment.

[0126] In some embodiments, while the second timer is running, the terminal device may consider the current GNSS location information to be valid or available.

[0127] The embodiment of the present application does not limit the timing duration of the second timer, and can be set according to actual conditions.

[0128] In some embodiments, the timing duration of the second timer may be configured by the network device. As an implementation, the network device may configure the timing duration of the second timer through system information (eg, SIB) or RRC dedicated signaling.

[0129] In some embodiments, the above-mentioned timer expiration may include a second timer expiration.

[0130] In some embodiments, the timer may include a first timer and a second timer. In this case, the timer expiration may include both the first timer and the second timer expiration, or the timer expiration may include either one of the first timer and the second timer expiration.

[0131] In some embodiments, the timer may include a third timer and a fourth timer. In some embodiments, the third timer and the fourth timer may be used to control the duration for which the terminal device considers the current GNSS position information to be valid or the duration for which the terminal device considers uplink synchronization.

[0132] In some embodiments, the third timer may be started or restarted each time the terminal device receives information about the TA adjustment, and the fourth timer may be started or restarted each time the terminal device receives information about the uplink frequency domain adjustment. In this case, it can be considered that the uplink time domain adjustment and the uplink frequency domain adjustment are controlled separately by the network, for example, by different signaling (such as different MAC CE signaling), or in other words, in this case, it can be considered that a timer (a third timer and a fourth timer) can be maintained for each of the uplink time domain adjustment and the uplink frequency domain adjustment.

[0133] In some embodiments, when a third timer and a fourth timer can be maintained for uplink time domain adjustment and uplink frequency domain adjustment respectively, the third timer and the fourth timer can correspond to the same timing duration, or can correspond to different timing durations. This is not limited in the embodiments of the present application.

[0134] In some embodiments, when a third timer and a fourth timer can be maintained for uplink time domain adjustment and uplink frequency domain adjustment respectively, the above-mentioned timer timeout may include both the third timer and the fourth timer timing out, or any one of the third timer and the fourth timer timing out.

[0135] In some embodiments, while the third timer and / or the fourth timer are running, the terminal device may consider the current GNSS location information to be valid or available.

[0136] The embodiment of the present application does not limit the timing duration of the third timer and the fourth timer, and can be set according to actual conditions.

[0137] In some embodiments, the timing duration of the third timer or the fourth timer may be configured by the network device. As an implementation, the network device may configure the timing duration of the third timer or the fourth timer through system information (eg, SIB) or RRC dedicated signaling.

[0138] In some embodiments, the timer may include a first timer, a third timer, and a fourth timer. In this case, the timer expiration may include the timeout of the first timer, the third timer, and the fourth timer, or the timeout of any one or more of the first timer, the third timer, and the fourth timer.

[0139] In an embodiment of the present application, when the first event occurs, the terminal device can determine the subsequent behavior based on the first condition, such as whether to remain in the RRC connection state to perform GNSS measurement, or to leave the RRC connection state to perform GNSS measurement, etc., which is conducive to the terminal device to formulate a reasonable GNSS measurement plan according to the current situation.

[0140] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 5 . The device embodiment of the present application is described in detail below in conjunction with Figures 6 and 7 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

[0141] FIG6 is a schematic diagram of the structure of a terminal device according to an embodiment of the present application. The terminal device 600 shown in FIG6 may include a determination module 610.

[0142] The determining module 610 may be configured to determine to perform a first GNSS operation according to a first condition, wherein the first condition is related to GNSS measurement.

[0143] In some implementations, the first condition is associated with one or more of the following information: information triggering the GNSS measurement; and time information for performing the GNSS measurement.

[0144] In some implementations, the first condition includes one or more of the following: the terminal device receives information triggering the GNSS measurement; and the terminal device receives information of a GNSS measurement gap.

[0145] In some implementations, the first GNSS operation includes one or more of the following operations: performing the GNSS measurement based on the time information of the GNSS measurement; triggering radio resource control RRC connection reestablishment, performing the GNSS measurement before initiating an RRC connection reestablishment request; and entering the RRC idle state, performing the GNSS measurement before the next RRC connection is established.

[0146] In some implementations, the determination module 610 is further used to: if the terminal device meets the first condition, determine to perform the GNSS measurement based on the time information of the GNSS measurement; or if the terminal device does not meet the first condition, determine to trigger RRC connection reconstruction, and perform the GNSS measurement before initiating the RRC connection reconstruction request; or if the terminal device does not meet the first condition, determine to enter the RRC idle state, and perform the GNSS measurement before the next RRC connection is established.

[0147] In some implementations, if the terminal device does not meet the first condition, it is determined to trigger RRC connection reconstruction, and the GNSS measurement is performed before initiating the RRC connection reconstruction request, including: if the terminal device does not meet the first condition and the terminal device cannot autonomously start the GNSS measurement, it is determined to trigger RRC connection reconstruction, and the GNSS measurement is performed before initiating the RRC connection reconstruction request; if the terminal device does not meet the first condition, it is determined to enter the RRC idle state, and the GNSS measurement is performed before the next RRC connection is established, including: if the terminal device does not meet the first condition and the terminal device cannot autonomously start the GNSS measurement, it is determined to enter the RRC idle state, and the GNSS measurement is performed before the next RRC connection is established.

[0148] In some implementations, the determination module 610 is further used to: when a first event is triggered, determine to perform the first GNSS operation according to the first condition; wherein the first event is used to indicate that the current GNSS location information of the terminal device is invalid or unavailable.

[0149] In some implementations, the first event includes one or more of the following: the terminal device determining that current GNSS location information of the terminal device is invalid or unavailable; and a timer expiration.

[0150] In some implementations, the timer includes a first timer, wherein the first timer is started or restarted when the terminal device performs GNSS measurement or obtains GNSS location information.

[0151] In some implementations, the timer also includes a second timer, which is started or restarted when the terminal device receives information on timing advance adjustment and / or frequency domain offset adjustment, wherein the timer timeout includes both the first timer and the second timer timing out, or any one of the first timer and the second timer timing out; or the timer also includes a third timer and a fourth timer, which is started or restarted when the terminal device receives information on timing advance adjustment, and the fourth timer is started or restarted when the terminal device receives information on frequency domain offset adjustment, wherein the timer timeout includes all the first timer, the third timer, and the fourth timer timing out, or any one / multiple timers of the first timer, the third timer, and the fourth timer timing out.

[0152] In some implementations, the terminal device is a terminal device accessing a non-terrestrial communication network NTN, and the terminal device is in an RRC connected state.

[0153] In some implementations, the determining module 610 may be a processor 710. The terminal device 600 may further include a transceiver 730 and a memory 720, as specifically shown in FIG7 .

[0154] Figure 7 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 7 indicate that the unit or module is optional. The device 700 may be used to implement the method described in the above method embodiment. The device 700 may be a chip, a terminal device, or a network device.

[0155] The device 700 may include one or more processors 710. The processor 710 may support the device 700 to implement the method described in the method embodiment above. The processor 710 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another 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, a discrete gate or transistor logic device, a discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0156] The apparatus 700 may further include one or more memories 720. The memories 720 store programs that can be executed by the processor 710, causing the processor 710 to perform the methods described in the above method embodiments. The memories 720 may be independent of the processor 710 or integrated into the processor 710.

[0157] The apparatus 700 may further include a transceiver 730. The processor 710 may communicate with other devices or chips via the transceiver 730. For example, the processor 710 may transmit and receive data with other devices or chips via the transceiver 730.

[0158] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0159] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0160] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or network device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0161] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0162] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0163] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0164] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0165] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0166] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0167] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0168] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0169] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0170] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0171] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0172] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0173] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A measurement method, characterized in that, including: The terminal device determines to perform a first Global Navigation Satellite System (GNSS) operation according to a first condition, where the first condition is related to GNSS measurement.

2. The method according to claim 1, wherein The first condition is associated with one or more of the following information: information that triggers the GNSS measurement; and time information for performing the GNSS measurement.

3. The method according to claim 1 or 2, characterized in that, The first condition includes one or more of the following: the terminal device receives information that triggers the GNSS measurement; and the terminal device receives information about a GNSS measurement gap.

4. The method according to any one of claims 1 to 3, characterized in that, The first GNSS operation includes one or more of the following operations: performing the GNSS measurement based on the time information of the GNSS measurement; triggering Radio Resource Control (RRC) connection reestablishment and performing the GNSS measurement before initiating an RRC connection reestablishment request; and entering the RRC idle state and performing the GNSS measurement before the next RRC connection is established.

5. The method according to any one of claims 1-4, characterized in that, The terminal device determines to perform a first GNSS operation according to a first condition, including: if the terminal device meets the first condition, the terminal device determines to perform the GNSS measurement based on the time information of the GNSS measurement; or if the terminal device does not meet the first condition, the terminal device determines to trigger RRC connection reestablishment and perform the GNSS measurement before initiating an RRC connection reestablishment request; or if the terminal device does not meet the first condition, the terminal device determines to enter the RRC idle state and perform the GNSS measurement before the next RRC connection is established.

6. The method according to claim 5, wherein the if the terminal device does not meet the first condition, the terminal device determines to trigger RRC connection reestablishment and perform the GNSS measurement before initiating an RRC connection reestablishment request, includes: if the terminal device does not meet the first condition and the terminal device cannot independently initiate the GNSS measurement, the terminal device determines to trigger RRC connection reestablishment and perform the GNSS measurement before initiating an RRC connection reestablishment request; the if the terminal device does not meet the first condition, the terminal device determines to enter the RRC idle state and perform the GNSS measurement before the next RRC connection is established, includes: if the terminal device does not meet the first condition and the terminal device cannot independently initiate the GNSS measurement, the terminal device determines to enter the RRC idle state and perform the GNSS measurement before the next RRC connection is established.

7. The method according to any one of claims 1-6, characterized in that, The terminal device determines to perform a first GNSS operation according to a first condition, including: when a first event is triggered, the terminal device determines to perform the first GNSS operation according to the first condition; wherein the first event is used to indicate that the current GNSS position information of the terminal device is invalid or unavailable.

8. The method according to claim 7, wherein The first event includes one or more of the following: the terminal device determines that the current GNSS position information of the terminal device is invalid or unavailable; and a timer timeout.

9. The method according to claim 8, wherein The timer includes a first timer. When the terminal device performs GNSS measurement or obtains GNSS position information, the first timer is started or restarted.

10. The method according to claim 9, wherein the timer further includes a second timer. When the terminal device receives information on timing advance adjustment and / or information on frequency domain offset adjustment, the second timer is started or restarted. The timeout of the timer includes that both the first timer and the second timer time out, or any one of the first timer and the second timer times out; or the timer further includes a third timer and a fourth timer. When the terminal device receives information on timing advance adjustment, the third timer is started or restarted. When the terminal device receives information on frequency domain offset adjustment, the fourth timer is started or restarted. The timeout of the timer includes that the first timer, the third timer, and the fourth timer all time out, or any one or more of the first timer, the third timer, and the fourth timer times out.

11. The method according to any one of claims 1 to 10, characterized in that, The terminal device is a terminal device accessing a non-terrestrial communication network (NTN), and the terminal device is in the RRC connected state.

12. A terminal device, characterized in that, It includes: a determination module, configured to determine to perform a first Global Navigation Satellite System (GNSS) operation according to a first condition, where the first condition is related to GNSS measurement.

13. The terminal device according to claim 12, characterized in that, The first condition is associated with one or more of the following information: information triggering the GNSS measurement; and time information for performing the GNSS measurement.

14. The terminal device according to claim 12 or 13, characterized in that, The first condition includes one or more of the following: the terminal device receives information triggering the GNSS measurement; and the terminal device receives information on GNSS measurement gaps.

15. The terminal device according to any one of claims 12 - 14, characterized in that, The first GNSS operation includes one or more of the following operations: performing the GNSS measurement based on the time information of the GNSS measurement; triggering Radio Resource Control (RRC) connection reestablishment and performing the GNSS measurement before initiating an RRC connection reestablishment request; and entering the RRC idle state and performing the GNSS measurement before the next RRC connection is established.

16. The terminal device according to any one of claims 12-15, characterized in that, The determination module is further configured to: if the terminal device meets the first condition, determine to perform the GNSS measurement based on the time information of the GNSS measurement; or if the terminal device does not meet the first condition, determine to trigger RRC connection reestablishment and perform the GNSS measurement before initiating an RRC connection reestablishment request; or if the terminal device does not meet the first condition, determine to enter the RRC idle state and perform the GNSS measurement before the next RRC connection is established.

17. The terminal device according to claim 16, wherein the step of, if the terminal device does not meet the first condition, determining to trigger RRC connection reestablishment and performing the GNSS measurement before initiating an RRC connection reestablishment request, includes: If the terminal device does not meet the first condition and the terminal device cannot initiate GNSS measurement autonomously, it is determined to trigger RRC connection reconstruction, and the GNSS measurement is performed before initiating an RRC connection reconstruction request; If the terminal device does not meet the first condition, it is determined to enter the RRC idle state, and the GNSS measurement is performed before the next RRC connection is established, including: If the terminal device does not meet the first condition and the terminal device cannot initiate GNSS measurement autonomously, it is determined to enter the RRC idle state, and the GNSS measurement is performed before the next RRC connection is established.

18. The terminal device according to any one of claims 12-17, characterized in that, The determining module is further configured to: When a first event is triggered, determine to perform the first GNSS operation according to the first condition; Wherein, the first event is used to indicate that the current GNSS position information of the terminal device is invalid or unavailable.

19. The terminal device according to claim 18, characterized in that, The first event includes one or more of the following: The terminal device determines that the current GNSS position information of the terminal device is invalid or unavailable; and The timer expires.

20. The terminal device according to claim 19, wherein The timer includes a first timer, wherein when the terminal device performs GNSS measurement or obtains GNSS position information, the first timer is started or restarted.

21. The terminal device according to claim 20, wherein, The timer further includes a second timer, which is started or restarted when the terminal device receives information on timing advance adjustment and / or information on frequency domain offset adjustment, wherein the expiration of the timer includes that both the first timer and the second timer expire, or any one of the first timer and the second timer expires; or The timer further includes a third timer and a fourth timer, which are started or restarted when the terminal device receives information on timing advance adjustment and are started or restarted when the terminal device receives information on frequency domain offset adjustment, wherein the expiration of the timer includes that the first timer, the third timer, and the fourth timer all expire, or any one / more of the first timer, the third timer, and the fourth timer expires.

22. The terminal device according to any one of claims 12-21, characterized in that, The terminal device is a terminal device accessing a non-terrestrial communication network NTN, and the terminal device is in an RRC connected state.

23. A terminal device, characterized in that, It includes a memory and a processor, the memory is used to store a program, and the processor is used to call the program in the memory so that the terminal device executes the method according to any one of claims 1-11.

24. A device, characterized in that, It includes a processor, which is used to call a program from a memory so that the device executes the method according to any one of claims 1-11.

25. A chip, characterized in that, It includes a processor, which is used to call a program from a memory so that the device installed with the chip executes the method according to any one of claims 1-11.

26. A computer-readable storage medium, characterized in that, A program is stored thereon, and the program causes a computer to execute the method according to any one of claims 1-11.

27. A computer program product, characterized in that, It includes a program, and the program causes a computer to execute the method according to any one of claims 1-11.

28. A computer program, characterized in that, The computer program causes a computer to execute the method according to any one of claims 1-11.

Images