Position measurement method, timer maintenance method and equipment

Abstract

The invention relates to a position measurement method, terminal equipment and network equipment. The position measurement method comprises the following steps: the terminal equipment starts GNSS measurement and / or starts a timer related to the GNSS measurement under the condition that the position of a global navigation satellite system (GNSS) is invalid. In the embodiment of the invention, under the condition that the GNSS position is invalid, the terminal equipment can autonomously start GNSS measurement, so that the effective GNSS position can be obtained in time, and the state transition of the terminal equipment is reduced.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly, to a location measurement method, a timer maintenance method, and a device. Background Art

[0002] Currently, 3GPP (3rd Generation Partnership Project) is researching NTN (Non Terrestrial Network) technology. NTN generally uses satellite communication to provide communication services to terrestrial users. In NTN, the terminal location can be measured through GNSS (Global Navigation Satellite System). Summary of the Invention

[0003] An embodiment of this application provides a location measurement method, including:

[0004] When the GNSS location of the terminal device is invalid, the terminal device starts GNSS measurement and / or starts a timer related to GNSS measurement.

[0005] An embodiment of this application provides a timer maintenance method, including:

[0006] The terminal device obtains the duration of the GNSS valid timer, where the GNSS location of the terminal device is valid during the operation of the GNSS valid timer.

[0007] An embodiment of this application provides a timer maintenance method, including:

[0008] The network device obtains the duration of the GNSS valid timer of the terminal device, where the GNSS location of the terminal device is valid during the operation of the GNSS valid timer.

[0009] An embodiment of this application provides a terminal device, including:

[0010] A processing unit, configured to start GNSS measurement and / or start a timer related to GNSS measurement when the GNSS location is invalid.

[0011] An embodiment of this application provides a terminal device, including:

[0012] A processing unit, configured to obtain the duration of the GNSS valid timer, where the GNSS location of the terminal device is valid during the operation of the GNSS valid timer.

[0013] An embodiment of this application provides a network device, including:

[0014] A processing unit, configured to obtain the duration of the GNSS valid timer of the terminal device, where the GNSS position of the terminal device is valid during the operation of the GNSS valid timer.

[0015] An embodiment of the present application provides a terminal device, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the terminal device executes the above-mentioned position measurement method and / or timer maintenance method.

[0016] An embodiment of the present application provides a network device, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the network device executes the above-mentioned timer maintenance method.

[0017] An embodiment of the present application provides a chip for implementing the above-mentioned position measurement method and / or timer maintenance method.

[0018] Specifically, the chip includes: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the above-mentioned position measurement method and / or timer maintenance method.

[0019] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, which, when run by a device, causes the device to execute the above-mentioned position measurement method and / or timer maintenance method.

[0020] An embodiment of the present application provides a computer program product, including computer program instructions, which cause a computer to execute the above-mentioned position measurement method and / or timer maintenance method.

[0021] An embodiment of the present application provides a computer program, which, when running on a computer, causes the computer to execute the above-mentioned position measurement method and / or timer maintenance method.

[0022] In the embodiment of the present application, in the case where the GNSS position is invalid, the terminal device can independently start GNSS measurement so as to obtain an effective GNSS position in a timely manner, reducing the state transition of the terminal device. In the embodiment of the present application, in the case where the GNSS position is invalid, the terminal device can start a timer to extend the waiting time of the GNSS measurement command, reducing the state transition of the terminal device. Description of the Drawings

[0023] Figure 1 is a schematic diagram of an application scenario according to an embodiment of the present application.

[0024] Figure 2 It is a schematic diagram of an NTN network architecture based on transparent forwarding according to an embodiment of the present application.

[0025] Figure 3 It is a schematic diagram of an NTN network architecture based on regenerative forwarding according to an embodiment of the present application.

[0026] Figure 4A It is a schematic diagram without timing advance.

[0027] Figure 4B It is a schematic diagram with timing advance.

[0028] Figure 5 It is a schematic flowchart of a position measurement method according to an embodiment of the present application.

[0029] Figure 6 It is a schematic flowchart of a position measurement method according to another embodiment of the present application.

[0030] Figure 7 It is a schematic flowchart of a position measurement method according to another embodiment of the present application.

[0031] Figure 8 It is a schematic flowchart of a timer maintenance method according to an embodiment of the present application.

[0032] Figure 9 It is a schematic flowchart of a timer maintenance method according to another embodiment of the present application.

[0033] Figure 10 It is a schematic flowchart of a timer maintenance method according to an embodiment of the present application.

[0034] Figure 11 It is a schematic flowchart of a timer maintenance method according to another embodiment of the present application.

[0035] Figure 12 It is a schematic diagram of Example 1 according to an embodiment of the present application.

[0036] Figure 13 It is a schematic diagram of Example 2 according to an embodiment of the present application.

[0037] Figure 14 It is a schematic diagram of Example 3 according to an embodiment of the present application.

[0038] Figure 15 It is a schematic diagram of Example 4 according to an embodiment of the present application.

[0039] Figure 16 It is a schematic block diagram of a terminal device according to an embodiment of the present application.

[0040] Figure 17It is a schematic block diagram of a terminal device according to an embodiment of the present application.

[0041] Figure 18 It is a schematic block diagram of a terminal device according to another embodiment of the present application.

[0042] Figure 19 It is a schematic block diagram of a network device according to an embodiment of the present application.

[0043] Figure 20 It is a schematic block diagram of a network device according to another embodiment of the present application.

[0044] Figure 21 It is a schematic block diagram of a communication device according to an embodiment of the present application.

[0045] Figure 22 It is a schematic block diagram of a chip according to an embodiment of the present application.

[0046] Figure 23 It is a schematic block diagram of a communication system according to an embodiment of the present application. Detailed implementation manners

[0047] Next, the technical solutions in the embodiments of the present application will be described with reference to the accompanying drawings in the embodiments of the present application.

[0048] The technical solution of the embodiment 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, evolved system of the NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), 5th-Generation (5G) system or other communication systems, etc.

[0049] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technologies, mobile communication systems will not only support traditional communications, but 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, etc. The embodiment of the present application can also be applied to these communication systems.

[0050] In one embodiment, the communication system in the embodiments of the present application can be applied to a Carrier Aggregation (CA) scenario, a Dual Connectivity (DC) scenario, or a Standalone (SA) networking scenario.

[0051] In one embodiment, the communication system in the embodiments of the present application can be applied to unlicensed spectrum, where the unlicensed spectrum can also be considered as shared spectrum; alternatively, the communication system in the embodiments of the present application can also be applied to licensed spectrum, where the licensed spectrum can also be considered as non-shared spectrum.

[0052] The embodiments of the present application describe various embodiments in combination with network devices and terminal devices. Among them, the terminal device can also be referred to as a User Equipment (UE), access terminal, user unit, user station, mobile station, mobile device, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc.

[0053] The terminal device can be a station (STAION, 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 function, a computing device, or other processing devices connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0054] In the embodiments of the present application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as on a ship, etc.); it can also be deployed in the air (such as on an airplane, a balloon, a satellite, etc.).

[0055] In the embodiments of the present application, the terminal device may be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in smart grid, a wireless terminal device in transportation safety, a wireless terminal device in smart city, or a wireless terminal device in smart home, etc.

[0056] As an example rather than a limitation, in the embodiments of the present application, the terminal device may also be a wearable device. A wearable device, also known as a wearable intelligent device, is a general term for devices developed by applying wearable technology to the intelligent design of daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is either directly worn on the body or integrated into the user's clothes or accessories. A wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable intelligent devices include those with complete functions and large sizes that can achieve complete or partial functions without relying on a smart phone, such as smart watches or smart glasses, etc., and those that only focus on a certain type of application function and need to cooperate with other devices such as smart phones, such as various smart bracelets and smart jewelry for physical sign monitoring.

[0057] In the embodiments of the present application, the network device may be a device used to communicate with a mobile device. The network device may be an access point (AP) in a WLAN, a base transceiver station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network, or a network device in an NTN network, etc.

[0058] By way of example and not limitation, in the embodiments of the present application, the network device may have mobility characteristics. For example, the network device may be a mobile device. Optionally, 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. Optionally, the network device may also be a base station located on land, water, etc.

[0059] In the embodiments of the present application, the network device may 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 in other words, spectrum resources). The cell may be a cell corresponding to the network device (such as a base station). The cell may belong to a macro base station or a base station corresponding to a small cell. Here, the small cell may include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage range and low transmission power, and are suitable for providing high-rate data transmission services.

[0060] Figure 1 Exemplarily, a communication system 100 is shown. The communication system includes a network device 110 and two terminal devices 120. In one implementation, the communication system 100 may include multiple network devices 110, and the coverage range of each network device 110 may include other numbers of terminal devices 120. The embodiments of the present application do not limit this.

[0061] In one implementation, the communication system 100 may further include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF). The embodiments of the present application do not limit this.

[0062] Among them, the network device can further include an access network device and a core network device. That is, the wireless communication system further includes a plurality of core networks for communicating with the access network device. The access network device can be an evolved Node B (abbreviated as eNB or e-NodeB), macro base station, micro base station (also known as "small base station"), pico base station, access point (AP), transmission point (TP), or new generation Node B (gNodeB) in a Long-Term Evolution (LTE) system, a Next Radio (NR) system, or an Authorized Auxiliary Access Long-Term Evolution (LAA-LTE) system, etc.

[0063] It should be understood that in the embodiments of the present application, a device with communication functions in a network / system can be referred to as a communication device. Taking Figure 1 the shown communication system as an example, the communication device can include a network device and a terminal device with communication functions. The network device and the terminal device can be specific devices in the embodiments of the present application and will not be elaborated here; the communication device can also include other devices in the communication system, such as other network entities like a network controller and a mobility management entity, which are not limited in the embodiments of the present application.

[0064] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article merely describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this article generally represents an "or" relationship between the associated objects before and after.

[0065] It should be understood that the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or a representation of an association relationship. For example, A indicates B, which can mean that A directly indicates B. For example, B can be obtained through A; it can also mean that A indirectly indicates B. For example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

[0066] In the description of the embodiments of the present application, the term "corresponding" can represent a direct or indirect corresponding relationship between two entities, can also represent an association relationship between them, or can be relationships such as indication and being indicated, configuration and being configured, etc.

[0067] To facilitate the understanding of the technical solutions of the embodiments of the present application, the related technologies of the embodiments of the present application are described below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the protection scope of the embodiments of the present application.

[0068] Compared with terrestrial cellular network communication, satellite communication has many unique advantages. First, satellite communication is not restricted by the user's geographical location. For example, general terrestrial communication cannot cover areas such as the ocean, high mountains, and deserts where it is impossible to install communication equipment or where communication coverage is not provided due to sparse population. For satellite communication, since a single satellite can cover a large area of the ground and the satellite can orbit the Earth, theoretically every corner of the Earth can be covered by satellite communication. Second, satellite communication has great social value. Satellite communication can be covered at a relatively low cost in remote mountainous areas, poor and backward countries or regions, enabling people in these areas to enjoy advanced voice communication and mobile Internet technologies, which is conducive to narrowing the digital divide with developed regions and promoting the development of these regions. Third, satellite communication has a long communication distance, and the communication cost does not increase significantly as the communication distance increases; finally, satellite communication has high stability and is not restricted by natural disasters.

[0069] Communication satellites are classified into LEO (Low-Earth Orbit) satellites, MEO (Medium-Earth Orbit) satellites, GEO (Geostationary Earth Orbit) satellites, HEO (High Elliptical Orbit) satellites, etc. according to different orbital heights. At the current stage, the main research focuses on LEO and GEO.

[0070] The height range of LEO satellites is 500 km to 1500 km (kilometers), and the corresponding orbital period is about 1.5 hours to 2 hours. The signal propagation delay of single-hop communication between users is generally less than 20 ms (milliseconds). The maximum satellite visibility time is 20 minutes. The signal propagation distance is short, the link loss is small, and the requirement for the transmit power of user terminals is not high.

[0071] For GEO satellites, the orbital height is 35786 km, and the rotation period around the Earth is 24 hours. The signal propagation delay of single-hop communication between users is generally 250 ms.

[0072] To ensure the coverage of satellites and improve the system capacity of the entire satellite communication system, satellites use multi-beam coverage of the ground. A single satellite can form dozens or even hundreds of beams to cover the ground; a satellite beam can cover a ground area with a diameter of dozens to hundreds of kilometers.

[0073] Currently, the 3GPP NTN standardization mainly focuses on two NTN network architectures: transparent forwarding and regenerative forwarding. For example, Figure 2 shows the NTN network architecture based on transparent forwarding. For example, Figure 3 shows the NTN network architecture based on regenerative forwarding.

[0074] The NTN network consists of the following network elements:

[0075] One or more gateways, which are used to connect the satellite and the terrestrial public network.

[0076] Feeder link: The link used for communication between the gateway and the satellite.

[0077] Service link: The link used for communication between the terminal and the satellite.

[0078] Satellite: From the perspective of the functions it provides, it can be divided into two types: transparent forwarding and regenerative forwarding.

[0079] Transparent forwarding: It only provides functions such as radio frequency filtering, frequency conversion, and amplification. It only provides transparent forwarding of signals and does not change the waveform signals it forwards.

[0080] Regenerative forwarding: In addition to providing functions such as radio frequency filtering, frequency conversion, and amplification, it can also provide functions such as demodulation / decoding, routing / switching, and encoding / modulation. It has some or all of the functions of a base station.

[0081] Inter-satellite link: Exists in the regenerative forwarding network architecture.

[0082] Uplink Timing Advance for LTE / NR Terrestrial Networks

[0083] An important feature of uplink transmission is that different UEs perform orthogonal multiple access in time-frequency, that is, the uplink transmissions of different UEs from the same cell do not interfere with each other.

[0084] To ensure the orthogonality of uplink transmission and avoid intra-cell interference, the eNB / gNB requires that the signals of different UEs from different frequency domain resources at the same moment arrive at the eNB / gNB basically aligned in time. To ensure time synchronization on the eNB / gNB side, LTE / NR supports the mechanism of uplink timing advance.

[0085] In the scenario of time synchronization on the eNB / gNB side, for example, Figure 4A shows the schematic diagram without timing advance. For example, Figure 4B shows the schematic diagram with timing advance. T P1 and T P2Indicates the one-way transmission delay of the signal from the base station to the UE. The uplink (UL) clock and downlink (DL) clock on the eNB / gNB side are the same, while there is an offset between the uplink clock and downlink clock on the UE side, and different UEs have their own different uplink Timing Advance values. By appropriately controlling the offset of each UE, the eNB / gNB can control the arrival time of the uplink signals from different UEs at the eNB / gNB. For UEs farther away from the eNB / gNB, due to the larger transmission delay, they need to send uplink data earlier than UEs closer to the eNB / gNB.

[0086] The eNB / gNB determines the TA (Timing Advance) value of each UE based on measuring the UE's uplink transmission. The eNB / gNB sends TA commands to the UE in two ways.

[0087] 1. Acquisition of the initial TA: During the random access process, the eNB / gNB determines the TA value by measuring the received preamble and sends it to the UE through the Timing Advance Command field in the RAR (Random Access Response).

[0088] 2. Adjustment of the TA in the RRC (Radio Resource Control) connected state: Although the UE and the eNB / gNB achieve uplink synchronization during the random access process, the timing of the uplink signal arriving at the eNB / gNB may change over time. Therefore, the UE needs to continuously update its uplink Timing Advance value to maintain uplink synchronization. If the TA of a certain UE needs to be corrected, the eNB / gNB will send a Timing Advance Command to that UE, requiring it to adjust the uplink timing. This Timing Advance Command is sent to the UE through the Timing Advance Command MAC (Medium Access Control) CE (Control Element).

[0089] TA Maintenance in NTN

[0090] In traditional TN (Terrestrial Network), the UE performs TA maintenance based on the TA command sent by the network. For Rel-17 NTN, assuming that UEs all have GNSS (Global Navigation Satellite System) positioning capabilities and TA pre-compensation capabilities, the UE can estimate the service link TA by itself based on the UE's location and the location of the serving satellite. Therefore, an open-loop and closed-loop combined TA determination method is introduced in NTN. Based on the current R17 standard, for NTN UEs in the RRC_IDLE (idle) / INACTIVE (deactivated) and RRC_CONNECTED (connected) states, their timing advance (TA) can be determined by the following formula:

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

[0092] Where, N TA is defined as 0 for the scenario of PRACH (Physical Random Access Channel) transmission and can be updated later through the TA command in Msg2 / MsgB and the TA command MAC CE; N TA,UE―specific is the TA of the service link estimated by the UE itself and is used for TA pre-compensation. Specifically, the terminal will obtain the location of the satellite based on the GNSS location information it obtains and the satellite ephemeris information broadcast by the serving cell, so as to calculate the propagation delay of the service link from the UE to the satellite. N TA,common is the common TA controlled by the network and includes any timing deviation considered necessary by the network. N TA,offset is a fixed offset for calculating the TA.

[0093] It can be seen from the above TA calculation formula that for a UE in the RRC connected state to obtain the TA of the service link (i.e., N TA,UE―specific ), on the one hand, it needs to know its own GNSS location information, and on the other hand, it also needs to obtain the location of the serving satellite through the satellite ephemeris information of the serving cell. In addition, in order to calculate the TA of the UE, the UE also needs to obtain the common TA (i.e., N TA,common ).

[0094] R17 GNSS Operation of IoT (Internet of Things) NTN

[0095] In R17 IoT NTN (i.e., the scenario where NB-IoT (NarrowBand Internet of Things) and eMTC (enhanced Machine-Type Communication) access NTN), the GNSS measurement module and the communication module of the IoT terminal cannot operate simultaneously (Simultaneous GNSS and NTN NB-IoT / eMTC operation is not assumed). In R17 NTN, the IoT terminal can only perform GNSS measurements to obtain location information in the RRC IDLE or RRC INACTIVE state, and the GNSS module cannot be started in the RRC connected state. Therefore, before entering the RRC connected state, the UE needs to measure and obtain its GNSS location through the GNSS module first. The UE can determine the effective duration of the GNSS location according to its own situation (such as the UE's movement state), and report the remaining time of the valid GNSS location to the network when the RRC connection is established / RRC re-established / RRC connection resumed. For a UE in the RRC connected state, when its GNSS location expires, since the UE cannot perform GNSS operations in the RRC connected state, the UE cannot calculate the TA, so the UE needs to return to the RRC IDLE state.

[0096] GNSS Enhancement for R18 IoT NTN

[0097] In the R18 IoT NTN enhancement project, the following research objectives are included:

[0098] Disable HARQ (Hybrid Automatic Repeat-reQuest) feedback to reduce the impact of HARQ stalling on the terminal data rate (Disabling of HARQ feedback to mitigate impact of HARQ stalling on UE data rates[RAN1,RAN2])

[0099] If needed, study and specify improved GNSS operations for pre-compensating the UE during long connection times and reducing power consumption (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[RAN1])

[0100] Based on the above research objectives, IoT terminals accessing NTN in R18 will be able to perform GNSS operations in the RRC connected state.

[0101] In addition, GNSS enhancements for IoT terminals accessing NTN may also include:

[0102] 1. IoT NTN UEs may need to reacquire a valid GNSS position fix during a relatively long RRC connection. How UEs update or reduce the need to update GNSS position fix during the RRC connected state FFS.

[0103] 2. To reduce the need for RRC connected state UEs to perform GNSS measurements, a closed-loop time-frequency adjustment mechanism can be considered.

[0104] 3. For GNSS measurements in the connected state, at least the following candidate solutions can be considered:

[0105] (1) UE reacquisition of GNSS position fix controlled by a timer.

[0106] (2) Introduce a new gap during which the UE reacquires a GNSS position fix.

[0107] 4. For the triggering of GNSS measurements in the connected state, the following can be considered:

[0108] (1) UE-triggered GNSS measurements.

[0109] (2) Network-triggered GNSS measurements.

[0110] In addition, support for the base station to trigger the UE to perform GNSS measurements non-periodically using MAC CE. The UE can report at least the measurement time required for the GNSS position fix during initial access. UEs in the RRC connected state can report the GNSS effective duration using MAC CE.

[0111] For GNSS measurements in the RRC connected state, a method of non-periodically triggering the UE to perform GNSS measurements by the network can be adopted. Usually, the network can trigger the GNSS to perform GNSS measurements before the GNSS becomes invalid based on the GNSS effective time reported by the UE. In some cases, if the UE has not received a GNSS measurement command until the GNSS position becomes invalid, the behavior of the UE can refer to the specific solution in the embodiments of this application.

[0112] Figure 5FIG. 500 is a schematic flowchart of a position measurement method according to an embodiment of the present application. Optionally, this method can be applied to Figure 1 the system shown in FIG., but is not limited thereto. The method includes at least some of the following content.

[0113] S510. When the GNSS position of the terminal device is invalid, start GNSS measurement and / or start a timer related to GNSS measurement.

[0114] In an embodiment of the present application, the GNSS position of the terminal device may include a measurement result obtained by positioning the terminal device based on GNSS. When the GNSS position of the terminal device is invalid, the terminal device can independently or actively trigger the start of GNSS measurement. The terminal device can also start a timer related to GNSS measurement when the GNSS position of the terminal device is invalid. The terminal device can also independently or actively trigger the start of GNSS measurement and start a timer related to GNSS measurement when the GNSS position of the terminal device is invalid.

[0115] In one implementation, the conditions for starting the timer include at least one of the following:

[0116] The GNSS position is invalid;

[0117] The terminal device has not received a GNSS measurement command from the network device since the last GNSS measurement was completed;

[0118] Based on the closed-loop timing advance (TA) adjustment mechanism and / or the closed-loop frequency offset adjustment mechanism, it is determined that the terminal device is out of synchronization in the uplink.

[0119] For example, when the GNSS position of the terminal device is invalid and the terminal device has not received a GNSS measurement command from the network device since the last GNSS measurement was completed, the terminal device independently starts GNSS measurement and starts a first timer.

[0120] For another example, when the GNSS position of the terminal device is invalid, the terminal device has not received a GNSS measurement command from the network device since the last GNSS measurement was completed, and based on the closed-loop timing advance (TA) adjustment mechanism and / or the closed-loop frequency offset adjustment mechanism, it is determined that the terminal device is out of synchronization in the uplink, the terminal device independently starts GNSS measurement and starts a second timer.

[0121] For another example, when the GNSS position of the terminal device is invalid and the terminal device has not received a GNSS measurement command from the network device since the last GNSS measurement was completed, the terminal device starts a third timer.

[0122] For another example, when the GNSS position of the terminal device is invalid, and the terminal device has not received a GNSS measurement command from the network device since the last GNSS measurement was completed, and it is determined that the terminal device is out of synchronization in the uplink based on the closed-loop timing advance (TA) adjustment mechanism and / or the closed-loop frequency offset adjustment mechanism, the fourth timer is started.

[0123] In the embodiments of the present application, determining that the terminal device is out of synchronization in the uplink based on the closed-loop TA adjustment mechanism and / or the closed-loop frequency offset adjustment mechanism may include: determining that the terminal device is out of synchronization in the uplink based on the closed-loop TA adjustment mechanism, determining that the terminal device is out of synchronization in the uplink based on the closed-loop frequency offset adjustment mechanism, and determining that the terminal device is out of synchronization in the uplink based on the closed-loop TA adjustment mechanism and the closed-loop frequency offset adjustment mechanism. There may also be other ways to determine that the terminal device is out of synchronization in the uplink, which are not limited in the embodiments of the present application.

[0124] In one implementation, as Figure 6 shown, the method further includes:

[0125] S610: When the terminal device starts GNSS measurement and starts the timer, it performs GNSS measurement during the running of the timer.

[0126] For example, when the terminal device performs GNSS measurement during the running of the above first timer or second timer, the GNSS position of the terminal device can be obtained again based on the measurement result of GNSS.

[0127] In one implementation, as Figure 6 shown, the method further includes:

[0128] S620: When the timer times out and the terminal device has not completed GNSS measurement, the terminal device releases the RRC connection and returns to the RRC idle state, or the terminal device triggers a RLF (Radio Link Failure) process.

[0129] In the embodiments of the present application, the terminal device may be a terminal device in the RRC connected state, such as a UE in the RRC connected state in NTN.

[0130] For example, when the GNSS position of a terminal device in the RRC connected state is invalid and the terminal device has not received a GNSS measurement command from the network device since the last GNSS measurement was completed, it autonomously starts GNSS measurement and starts the first timer. When the first timer times out and the terminal device has not completed GNSS measurement, the terminal device releases the RRC connection and returns to the RRC idle state, or the terminal device triggers a RLF process.

[0131] For another example, when the GNSS position of the terminal device is invalid, and the terminal device has not received a GNSS measurement command from the network device since the last GNSS measurement was completed, and it is determined that the terminal device is out of uplink synchronization based on the closed-loop timing advance (TA) adjustment mechanism and / or the closed-loop frequency offset adjustment mechanism, the terminal device autonomously starts GNSS measurement and starts a second timer. When the second timer expires and the terminal device has not completed GNSS measurement, the terminal device releases the RRC connection and returns to the RRC idle state, or the terminal device triggers the RLF process.

[0132] In the embodiments of the present application, during the RLF process, the terminal device can reselect a cell, initiate RRC connection reconstruction, and may reconnect to the current cell or a new cell.

[0133] In one implementation, as Figure 6 shown, the method further includes:

[0134] S630: When the terminal device has completed at least one of GNSS measurement, uplink synchronization, and downlink synchronization, stop the timer.

[0135] In some examples, if the duration of the timer related to GNSS measurement includes the duration for completing GNSS measurement, the timer can be stopped after the terminal device completes GNSS measurement.

[0136] In some examples, if the duration of the timer related to GNSS measurement includes the duration for completing GNSS measurement and downlink synchronization, the timer can be stopped after the terminal device completes GNSS measurement and downlink synchronization.

[0137] In some examples, if the duration of the timer related to GNSS measurement includes the duration for completing GNSS measurement, downlink synchronization, and uplink synchronization, the timer can be stopped after the terminal device completes GNSS measurement, downlink synchronization, and uplink synchronization.

[0138] Specifically, the duration of the timer related to GNSS measurement can be set according to the requirements of the actual application scenario, and it is not limited in the embodiments of the present application.

[0139] In one implementation, when the terminal device has completed at least one of GNSS measurement, uplink synchronization, and downlink synchronization, the terminal device sends notification information for notifying the network device that the terminal device has completed at least one of GNSS measurement, uplink synchronization, and downlink synchronization.

[0140] For example, the UE can inform the network that it has completed at least one of GNSS measurement, uplink synchronization, and downlink synchronization by sending an uplink transmission (such as in the way of RACH, MAC CE, etc.).

[0141] In one embodiment, as Figure 7 shown, the method further includes:

[0142] S710. After the terminal device starts the timer when the GNSS position is invalid, it waits for a GNSS measurement command during the running of the timer. For example, after the terminal device starts the timer when the GNSS position is invalid and the terminal device has not received a GNSS measurement command from the network device since completing the last GNSS measurement, it waits for a GNSS measurement command during the running of the timer.

[0143] In the embodiments of the present application, when the GNSS position of the terminal device is invalid and the terminal device has not received a GNSS measurement command from the network device since completing the last GNSS measurement, it may not trigger the start of GNSS measurement autonomously or actively, but start a timer related to GNSS measurement. During the running of the timer, the terminal device can wait for a GNSS measurement command from the network device. If the GNSS measurement command is still not received after the timer times out, it can stop waiting for the GNSS measurement command.

[0144] In one embodiment, as Figure 7 shown, the method further includes:

[0145] S720. When the timer times out and the terminal device has not received a GNSS measurement command, the terminal device releases the RRC connection and returns to the RRC idle state, or the terminal device triggers an RLF process.

[0146] Again, a terminal device in the RRC connected state starts a third timer when the GNSS position is invalid and the terminal device has not received a GNSS measurement command from the network device since completing the last GNSS measurement. When the third timer times out and the terminal device has not received the GNSS measurement command, the terminal device releases the RRC connection and returns to the RRC idle state, or the terminal device triggers an RLF process.

[0147] Again, a terminal device in the RRC connected state starts a fourth timer when the GNSS position is invalid, the terminal device has not received a GNSS measurement command from the network device since completing the last GNSS measurement, and it is determined that the terminal device is out of synchronization in the uplink based on a closed-loop timing advance TA adjustment mechanism and / or a closed-loop frequency offset adjustment mechanism. When the fourth timer times out and the terminal device has not received the GNSS measurement command, the terminal device releases the RRC connection and returns to the RRC idle state, or the terminal device triggers an RLF process.

[0148] In one implementation, as Figure 7 shown, the method further includes:

[0149] S730. When the terminal device receives the GNSS measurement command from the network device, the timer is stopped. This step can be after S610 or after S710.

[0150] For example, during the operation of the above-mentioned third timer, if the terminal device receives the GNSS measurement command from the network device, the third timer is stopped. During the operation of the above-mentioned fourth timer, if the terminal device receives the GNSS measurement command from the network device, the fourth timer is stopped.

[0151] In one implementation, the duration of the timer is configured by the network device. For example, the terminal device receives timer configuration information from the network device, and the timer configuration information is used for the duration of at least one of the above-mentioned first timer, second timer, third timer, and fourth timer.

[0152] In one implementation, the duration of the timer reuses the duration of the measurement interval (gap).

[0153] In one implementation, the invalid GNSS position includes: the GNSS valid timer times out.

[0154] For example, when the GNSS valid timer of the terminal device times out and the terminal device has not received the GNSS measurement command from the network device since the last GNSS measurement was completed, the terminal device autonomously starts a GNSS measurement and starts the first timer.

[0155] For another example, when the GNSS valid timer of the terminal device times out, the terminal device has not received the GNSS measurement command from the network device since the last GNSS measurement was completed, and it is determined that the terminal device is out of synchronization in the uplink based on the closed-loop timing advance TA adjustment mechanism and / or the closed-loop frequency offset adjustment mechanism, the terminal device autonomously starts a GNSS measurement and starts the second timer.

[0156] For another example, when the GNSS valid timer of the terminal device times out and the terminal device has not received the GNSS measurement command from the network device since the last GNSS measurement was completed, the third timer is started.

[0157] For another example, when the GNSS valid timer of the terminal device times out, and the terminal device has not received a GNSS measurement command from the network device since it completed the most recent GNSS measurement, and it is determined that the terminal device is out of uplink synchronization based on the closed-loop timing advance (TA) adjustment mechanism and / or the closed-loop frequency offset adjustment mechanism, the fourth timer is started.

[0158] In an embodiment of the present application, the GNSS valid timer can be used to determine whether the GNSS measurement result of the terminal device, that is, the GNSS position, is valid. During the operation of the GNSS valid timer, the terminal device and the network device can consider the GNSS position of the terminal device to be valid. The GNSS valid timer can also have other names, such as the GNSS measurement result valid timer, the GNSS position valid timer, the GNSS result timer, etc. For the specific maintenance method of the GNSS valid timer, reference can be made to the relevant descriptions in the embodiments of the following timer maintenance method.

[0159] In an embodiment of the present application, when the GNSS position of the terminal device is invalid, the terminal device can independently initiate a GNSS measurement, so as to obtain a valid GNSS position in a timely manner and reduce the state transition of the terminal device. When the GNSS position of the terminal device is invalid, the terminal device can start a timer to extend the waiting time for the GNSS measurement command and reduce the state transition of the terminal device. For example, a terminal device in the RRC connected state can, as much as possible, restore or maintain uplink synchronization while keeping the RRC connection to improve the user experience.

[0160] Figure 8 is a schematic flowchart of a timer maintenance method 800 according to an embodiment of the present application. This method can optionally be applied to Figure 1 the system shown, but is not limited thereto. This embodiment can be implemented independently or in combination with the above-described embodiment of the position measurement method. The timer maintenance method includes at least some of the following content.

[0161] S810. The terminal device obtains the duration of the GNSS valid timer, where the GNSS position of the terminal device is valid during the operation of the GNSS valid timer.

[0162] In the embodiments of the present application, the terminal device can obtain the duration of the GNSS valid timer locally or from a network device. The terminal device can control the operation of the GNSS valid timer based on the duration of the GNSS valid timer. During the operation of the GNSS valid timer, the terminal device and / or the network device can consider the GNSS position of the terminal device to be valid. In the case where the GNSS valid timer times out, the terminal device and / or the network device can consider the GNSS position of the terminal device to be invalid or the GNSS position to have expired. In the embodiments of the present application, by maintaining the GNSS valid timer, for example, by obtaining the duration of the GNSS valid timer, the terminal device can timely know whether its current GNSS position is available. For example, when the GNSS position in front of the terminal device is available and when it is not available. Furthermore, the terminal device can use the valid GNSS position to determine the TA.

[0163] In one implementation, as Figure 9 shown, the timer maintenance method 900 further includes:

[0164] S910. The terminal device sends a first message, and the first message is used to report the duration of the GNSS valid timer, and the duration of the GNSS valid timer is determined by the terminal device.

[0165] In the embodiments of the present application, if the terminal device itself determines the duration of the GNSS valid timer, the terminal device can send a first message, such as an uplink signaling such as MAC CE or RRC signaling, to the network device, and the uplink signaling can include the duration of the GNSS valid timer.

[0166] In one implementation, as Figure 9 shown, the timer maintenance method further includes:

[0167] S920. When the terminal device sends the first message, it starts the GNSS valid timer.

[0168] In the embodiments of the present application, if the terminal device reports the duration of the GNSS valid timer to the network device through uplink signaling, it can start the GNSS valid timer when sending the uplink signaling.

[0169] In one implementation, as Figure 9 shown, the timer maintenance method further includes:

[0170] S930. The terminal device receives a second message, and the second message is used to configure the duration of the GNSS valid timer.

[0171] In the timer maintenance method according to an embodiment of the present application, it may only include S910 and S920, may only include S930, or include these three steps. For example, if the network device determines the duration of the GNSS valid timer, the method may include S930. If the terminal device determines the duration of the GNSS valid timer, the method may include S910 and S920. If both the terminal device and the network device can determine the duration of the GNSS valid timer, the method may include S910, S920, and S930, and the terminal device and the network device can use the duration of the GNSS valid timer received from each other to verify the local duration.

[0172] In an embodiment of the present application, if the network device determines the duration of the GNSS valid timer, the network device may send second information, such as downlink signaling like MAC CE or RRC signaling, to the terminal device. The downlink signaling may include the duration of the GNSS valid timer. After receiving the downlink signaling, the terminal device may configure the duration of the GNSS valid timer based on the downlink signaling.

[0173] In one implementation, the terminal device starts the GNSS valid timer based on the duration of the GNSS valid timer. The starting manner of the GNSS valid timer includes at least one of the following:

[0174] The terminal device starts the GNSS valid timer when receiving the second information;

[0175] The terminal device starts the GNSS valid timer at a specified time point based on the second information.

[0176] For example, if the terminal device receives downlink signaling for indicating the duration of the GNSS valid timer, it may start the GNSS valid timer when receiving the downlink signaling.

[0177] For example, if the terminal device receives downlink signaling for indicating the duration of the GNSS valid timer, it may start the GNSS valid timer at the specified time point indicated by the downlink signaling.

[0178] In an embodiment of the present application, the second information may explicitly indicate the specified time point or implicitly indicate the specified time point.

[0179] In one implementation, the specified time point includes at least one of the following:

[0180] The time point for starting the GNSS valid timer is included in the second information; this is an explicit indication method.

[0181] The effective time point of the second information; this is an implicit indication method.

[0182] In one embodiment, as Figure 9 shown, the timer maintenance method further includes:

[0183] S940. When the terminal device receives a GNSS measurement command, stop the GNSS valid timer; or, when the terminal device starts to perform GNSS measurement, stop the GNSS valid timer.

[0184] For example, if the terminal device has started the GNSS valid timer, when the terminal device receives a GNSS measurement command from the network device, the GNSS valid timer can be stopped.

[0185] Again, for example, if the terminal device has started the GNSS valid timer, when the terminal device starts to perform GNSS measurement based on the GNSS measurement command or autonomously, the GNSS valid timer can be stopped.

[0186] Figure 10 is a schematic flowchart of a timer maintenance method 1000 according to an embodiment of the present application. This method can optionally be applied to Figure 1 the system shown, but is not limited thereto. This embodiment can be implemented independently or in combination with the above-mentioned position measurement method embodiment. The timer maintenance method includes at least part of the following content.

[0187] S1010. The network device obtains the duration of the GNSS valid timer of the terminal device, where the GNSS position of the terminal device is valid during the operation of the GNSS valid timer.

[0188] In one embodiment, as Figure 11 shown, the timer maintenance method 1100 further includes:

[0189] S1110. The network device receives first information for reporting the duration of the GNSS valid timer, and the duration of the GNSS valid timer is determined by the terminal device.

[0190] In one embodiment, the GNSS valid timer is started by the terminal device when sending the first information.

[0191] In one embodiment, as Figure 11 shown, the timer maintenance method further includes: The network device configures the duration of the GNSS valid timer for the terminal device. The specific configuration method may include:

[0192] S1120. The network device sends second information for configuring the duration of the GNSS valid timer.

[0193] In the timer maintenance method according to the embodiments of the present application, it may only include S1110, may only include S1120, or include both of these two steps. For example, if the network device determines the duration of the GNSS valid timer, the method may include S1120. If the terminal device determines the duration of the GNSS valid timer, the method may include S1110. If both the terminal device and the network device can determine the duration of the GNSS valid timer, the method may include S1110 and S1120, and the terminal device and the network device can use the duration of the GNSS valid timer received from each other to verify the local duration.

[0194] In one implementation, the second information is used to indicate that the GNSS valid timer starts at a specified time point. In the embodiments of the present application, the second information may explicitly indicate the specified time point or implicitly indicate the specified time point.

[0195] In one implementation, the specified time point includes at least one of the following:

[0196] The time point for starting the GNSS valid timer included in the second information;

[0197] The effective time point of the second information.

[0198] In one implementation, as Figure 11 shown, the timer maintenance method further includes:

[0199] S1130, the network device sends a GNSS measurement command, and the GNSS measurement command is used to stop the GNSS valid timer.

[0200] For specific examples of the method executed by the network device in this embodiment, reference may be made to the relevant descriptions of the network device in the above methods 800 and 900. For the sake of brevity, details are not described herein again.

[0201] The position measurement method and / or the timer maintenance method according to the embodiments of the present application can be used in the scenario where the terminal in NTN maintains uplink synchronization. For example, a method for the terminal in NTN to maintain uplink synchronization may include the following methods:

[0202] Method 1. After the GNSS valid timer times out, the UE independently starts GNSS measurement and simultaneously starts the first timer. If the UE has not completed GNSS measurement when the first timer times out, the UE releases the RRC connection and returns to the RRC IDLE state or the UE triggers RLF.

[0203] Method 2. When the GNSS valid timer expires and the UE determines that the UE is uplink out-of-sync based on the closed-loop TA and / or frequency offset adjustment mechanism, the UE autonomously starts GNSS measurement and simultaneously starts a second timer. If the UE has not completed GNSS measurement when the second timer expires, the UE releases the RRC connection and returns to the RRC IDLE state or the UE triggers RLF.

[0204] Method 3. After the GNSS valid timer expires, the UE starts a third timer. If the UE has not received a GNSS measurement command from the network when the third timer expires, the UE releases the RRC connection and returns to the RRC IDLE state or the UE triggers RLF.

[0205] Method 4. When the GNSS valid timer expires and the UE determines that the UE is uplink out-of-sync based on the closed-loop TA and / or frequency offset adjustment mechanism, the UE starts a fourth timer. If the UE has not received a GNSS measurement command from the network when the fourth timer expires, the UE releases the RRC connection and returns to the RRC IDLE state or the UE triggers RLF.

[0206] Specific examples of the above methods are as follows:

[0207] Example 1:

[0208] After the GNSS valid timer expires, the UE autonomously starts GNSS measurement. Specifically, after the GNSS valid timer expires, the UE autonomously starts GNSS measurement and simultaneously starts a first timer. If the UE has not completed GNSS measurement when the first timer expires, the UE releases the RRC connection and returns to the RRC IDLE state or the UE triggers RLF.

[0209] As Figure 12 shown, the specific implementation process of this example is as follows:

[0210] 1. The UE in the RRC connected state maintains a GNSS valid timer. The determination and start conditions of the duration of the GNSS valid timer are as follows:

[0211] (1) The duration of the GNSS valid timer is determined by the UE and reported to the base station through uplink signaling (such as MAC CE, RRC signaling); the UE starts the GNSS valid timer when reporting the duration of the GNSS valid timer.

[0212] (2) The duration of the GNSS valid timer is configured to the UE by the base station through downlink signaling (such as MAC CE, RRC signaling). For example, the base station can configure the duration of the GNSS valid timer according to the GNSS valid time reported by the UE last time.

[0213] The time when the UE starts the GNSS valid timer can be one of the following ways:

[0214] a. When the UE receives the configuration of the GNSS valid timer duration, the UE starts the GNSS valid timer.

[0215] b. The UE starts the GNSS valid timer at a specified time point based on network indication. For example, when configuring the GNSS valid timer duration, the network explicitly indicates the time point for the UE to start the GNSS valid timer at the same time, or the UE uses the time point when the GNSS valid timer duration configuration takes effect (such as the time point when the downlink signaling carrying the GNSS valid timer duration configuration takes effect) as the time to start the GNSS valid timer.

[0216] 2. Optionally, if the UE receives a GNSS measurement command from the network, the UE stops the GNSS valid timer.

[0217] 3. When the UE meets the first condition, the UE starts the first timer, and the UE performs GNSS measurement during the running of the first timer. Among them,

[0218] (1) The first condition is that the GNSS valid timer expires and the UE has not received a GNSS measurement command from the network.

[0219] (2) The duration of the first timer is configured by the network. For example, reuse the duration of the measurement gap, or the network configures the duration of the first timer separately.

[0220] 4. If the UE completes GNSS measurement and / or uplink synchronization and / or downlink synchronization, the UE notifies the network that it has completed GNSS measurement and / or uplink synchronization and / or downlink synchronization by sending an uplink transmission (such as RACH (Random Access CHannel), MAC CE, etc.).

[0221] 5. If the UE completes GNSS measurement and / or uplink synchronization and / or downlink synchronization, the UE stops the first timer.

[0222] 6. If the first timer expires and the UE has not completed GNSS measurement when the first timer expires, the UE releases the RRC connection and returns to the RRC IDLE state or the UE triggers RLF.

[0223] A schematic diagram of this example is as follows:

[0224] Example 2:

[0225] When the GNSS valid timer expires and the UE determines that the UE is out-of-sync on the uplink based on the closed-loop TA and / or frequency offset adjustment mechanism, the UE autonomously initiates GNSS measurement. Specifically, when the GNSS valid timer expires and the UE determines that the UE is out-of-sync on the uplink based on the closed-loop TA and / or frequency offset adjustment mechanism, the UE autonomously initiates GNSS measurement and starts a second timer simultaneously. If the UE has not completed the GNSS measurement when the second timer expires, the UE releases the RRC connection and returns to the RRC IDLE state or the UE triggers an RLF.

[0226] As Figure 13 shown, the specific implementation process of this example is as follows:

[0227] 1. The UE in the RRC connected state maintains a GNSS valid timer. The determination and start conditions of the duration of the GNSS valid timer are the same as those in step 1 of Example 1.

[0228] 2. Optionally, if the UE receives a GNSS measurement command from the network, the UE stops the GNSS valid timer.

[0229] 3. The UE starts a second timer when the second condition is met. The UE performs GNSS measurement during the operation of the second timer. Among them,

[0230] (1) The second condition is that the GNSS valid timer expires, and the UE determines that the UE is out-of-sync on the uplink based on the closed-loop TA and / or frequency offset adjustment mechanism, for example, the time alignment timer expires, and the UE has not received a GNSS measurement command from the network.

[0231] (2) The duration of the second timer is configured by the network. For example, the duration of the measurement gap is reused, or the network configures the duration of the second timer separately.

[0232] 4. If the UE completes GNSS measurement and / or uplink synchronization and / or downlink synchronization, the UE notifies the network that it has completed GNSS measurement and / or uplink synchronization and / or downlink synchronization by sending an uplink transmission (such as RACH, MAC CE, etc.).

[0233] 5. If the UE completes GNSS measurement and / or uplink synchronization and / or downlink synchronization, the UE stops the second timer.

[0234] 6. If the second timer expires and the UE has not completed the GNSS measurement when the second timer expires, the UE releases the RRC connection and returns to the RRC IDLE state or the UE triggers an RLF.

[0235] A schematic diagram of this example is as follows:

[0236] Example 3:

[0237] After the GNSS valid timer expires, the UE continues to wait for the network to send a GNSS measurement command within a certain period of time. Specifically, after the GNSS valid timer expires, the UE starts a third timer. If the UE has not received a GNSS measurement command from the network when the third timer expires, the UE releases the RRC connection and returns to the RRC IDLE state or the UE triggers an RLF.

[0238] As Figure 14 shown, the specific implementation process of this example is as follows:

[0239] 1. The UE in the RRC connected state maintains a GNSS valid timer. The determination and start condition of the duration of the GNSS valid timer are the same as those in step 1 of Example 1.

[0240] 2. Optionally, if the UE receives a GNSS measurement command from the network, the UE stops the GNSS valid timer.

[0241] 3. The UE starts a third timer when the first condition is met. Among them, the first condition is the same as that in step 3 of Example 1. The duration of the third timer is configured by the network.

[0242] 4. If the UE receives a GNSS measurement command from the network, the UE stops the third timer.

[0243] 5. If the third timer expires and the UE has not received a GNSS measurement command from the network when the third timer expires, the UE releases the RRC connection and returns to the RRC IDLE state or the UE triggers an RLF.

[0244] A schematic diagram of this example is as follows:

[0245] Example 4:

[0246] When the GNSS valid timer expires and the UE determines that the UE is uplink out-of-sync based on the closed-loop TA and / or frequency offset adjustment mechanism, the UE continues to wait for the network to send a GNSS measurement command within a certain period of time. Specifically, when the GNSS valid timer expires and the UE determines that the UE is uplink out-of-sync based on the closed-loop TA and / or frequency offset adjustment mechanism, the UE starts a fourth timer. If the UE has not received a GNSS measurement command from the network when the fourth timer expires, the UE releases the RRC connection and returns to the RRC IDLE state or the UE triggers an RLF.

[0247] As Figure 15 shown, the specific implementation process of this example is as follows:

[0248] 1. A UE in the RRC connected state maintains a GNSS valid timer, and the determination and start condition of the duration of the GNSS valid timer are the same as step 1 of Example 1.

[0249] 2. Optionally, if the UE receives a GNSS measurement command from the network, the UE stops the GNSS valid timer.

[0250] 3. The UE starts a fourth timer when the second condition is met. Among them, the second condition is the same as step 3 of Example 2. The duration of the fourth timer is configured by the network.

[0251] 4. If the UE receives a GNSS measurement command from the network, the UE stops the fourth timer.

[0252] 5. If the fourth timer expires and the UE has not received a GNSS measurement command from the network when the fourth timer expires, the UE releases the RRC connection and returns to the RRC IDLE state or the UE triggers an RLF.

[0253] A schematic diagram of this example is as follows:

[0254] The embodiments of the present application provide a method for a terminal to measure GNSS in NTN, which clarifies the behavior of the UE when the GNSS position is invalid and the UE has not received a GNSS measurement command from the network. By introducing GNSS measurements triggered by the UE itself or waiting for a GNSS measurement command from the network for a period of time, the UE can recover or maintain uplink synchronization while keeping the RRC connection as much as possible, improving the user experience.

[0255] Figure 16 It is a schematic block diagram of a terminal device 1600 according to an embodiment of the present application. The terminal device 1600 may include:

[0256] A processing unit 1610, configured to start GNSS measurement and / or start a timer related to GNSS measurement when the GNSS position is invalid.

[0257] In one implementation, the processing unit is further configured to perform GNSS measurement during the running of the timer when starting GNSS measurement and starting the timer.

[0258] In one implementation, the processing unit is further configured to release the radio resource control RRC connection and return to the RRC idle state or the terminal device triggers a radio link failure RLF process when the timer expires and the terminal device has not completed GNSS measurement.

[0259] In one embodiment, the processing unit is further configured to stop the timer when the terminal device completes at least one of GNSS measurement, uplink synchronization, and downlink synchronization.

[0260] In one embodiment, the terminal device further includes a sending unit, configured to send notification information when the terminal device completes at least one of GNSS measurement, uplink synchronization, and downlink synchronization, where the notification information is used to notify the network device that the terminal device has completed at least one of GNSS measurement, uplink synchronization, and downlink synchronization.

[0261] In one embodiment, after the processing unit starts the timer when the GNSS position is invalid and the terminal device has not received a GNSS measurement command from the network device since completing the most recent GNSS measurement, it waits for a GNSS measurement command during the running of the timer.

[0262] In one embodiment, the processing unit is further configured to release the RRC connection back to the RRC idle state or the terminal device triggers an RLF process when the timer expires and the terminal device has not received the GNSS measurement command.

[0263] In one embodiment, the conditions for the processing unit to start the timer include at least one of the following:

[0264] The GNSS position is invalid;

[0265] The terminal device has not received a GNSS measurement command from the network device;

[0266] Based on a closed-loop timing advance TA adjustment mechanism and / or a closed-loop frequency offset adjustment mechanism, it is determined that the terminal device is out of uplink synchronization.

[0267] In one embodiment, the processing unit is further configured to stop the timer when receiving the GNSS measurement command from the network device.

[0268] In one embodiment, the duration of the timer is configured by the network device.

[0269] In one embodiment, the duration of the timer reuses the duration of the measurement interval.

[0270] In one embodiment, the GNSS position being invalid includes: the GNSS valid timer expires.

[0271] The terminal device 1600 in the embodiment of the present application can implement the corresponding functions of the terminal devices 500, 600, and 700 in the foregoing method embodiments. For the corresponding processes, functions, implementation manners, and beneficial effects of each module (sub-module, unit, or component, etc.) in the terminal device 1600, reference may be made to the corresponding descriptions in the foregoing method embodiments, which will not be elaborated herein. It should be noted that the functions described for each module (sub-module, unit, or component, etc.) in the terminal device 1500 in the embodiment of the application may be implemented by different modules (sub-modules, units, or components, etc.), or may be implemented by the same module (sub-module, unit, or component, etc.).

[0272] Figure 17 FIG. 4 is a schematic block diagram of a terminal device 1700 according to an embodiment of the present application. The terminal device 1700 may include:

[0273] A processing unit 1710, configured to obtain the duration of a GNSS valid timer, where the GNSS position of the terminal device is valid during the operation of the GNSS valid timer.

[0274] In one implementation manner, as shown in FIG. Figure 18 5, the terminal device 1800 further includes:

[0275] A sending unit 1810, configured to send first information for reporting the duration of the GNSS valid timer, where the duration of the GNSS valid timer is determined by the terminal device.

[0276] In one implementation manner, the terminal device further includes:

[0277] The processing unit is further configured to start the GNSS valid timer when the sending unit sends the first information.

[0278] In one implementation manner, as shown in FIG. Figure 18 6, the terminal device further includes:

[0279] A receiving unit 1820, configured to receive second information for configuring the duration of the GNSS valid timer.

[0280] In one implementation manner, the manner in which the processing unit starts the GNSS valid timer includes at least one of the following:

[0281] Starting the GNSS valid timer when receiving the second information;

[0282] Starting the GNSS valid timer at a specified time point based on the second information.

[0283] In one embodiment, the specified time point includes at least one of the following:

[0284] The time point for starting the GNSS valid timer included in the second information;

[0285] The effective time point of the second information.

[0286] In one embodiment, the processing unit 1710 is further configured to stop the GNSS valid timer when the terminal device receives a GNSS measurement command; or stop the GNSS valid timer when the terminal device starts to perform GNSS measurement.

[0287] The terminal devices 1700 and 1800 in the embodiments of the present application can implement the corresponding functions of the terminal devices in the foregoing method embodiments 800 and 900. For the corresponding processes, functions, implementation manners, and beneficial effects of each module (sub-module, unit, or component, etc.) in the terminal devices 1700 and 1800, reference may be made to the corresponding descriptions in the foregoing method embodiments, which will not be elaborated herein. It should be noted that the functions described for each module (sub-module, unit, or component, etc.) in the terminal devices 1700 and 1800 of the application embodiments may be implemented by different modules (sub-modules, units, or components, etc.), or may be implemented by the same module (sub-module, unit, or component, etc.).

[0288] Figure 19 It is a schematic block diagram of a network device 1900 according to an embodiment of the present application. The network device 1900 may include:

[0289] A processing unit 1910, configured to obtain the duration of the GNSS valid timer of the terminal device, where the GNSS position of the terminal device is valid during the operation of the GNSS valid timer.

[0290] In one embodiment, as Figure 20 shown, the network device 2000 further includes:

[0291] A receiving unit 2010, configured to receive first information for reporting the duration of the GNSS valid timer, where the duration of the GNSS valid timer is determined by the terminal device.

[0292] In one embodiment, the GNSS valid timer is started by the terminal device when sending the first information.

[0293] In one embodiment, the network device further includes: a first sending unit 2020, configured to send second information for configuring the duration of the GNSS valid timer.

[0294] In one embodiment, the second information is used to indicate that the GNSS valid timer starts at a specified time point.

[0295] In one embodiment, the specified time point includes at least one of the following:

[0296] The time point for starting the GNSS valid timer included in the second information;

[0297] The effective time point of the second information.

[0298] In one embodiment, as Figure 20 shown, the network device further includes:

[0299] A second sending unit 2030, configured to send a GNSS measurement command, where the GNSS measurement command is used to stop the GNSS valid timer.

[0300] The network devices 1900 and 2000 in the embodiments of the present application can implement the corresponding functions of the network devices 1000 and 1100 in the foregoing method embodiments. For the corresponding processes, functions, implementation manners, and beneficial effects of each module (sub-module, unit, or component, etc.) in the network devices 1900 and 2000, reference may be made to the corresponding descriptions in the foregoing method embodiments, which will not be elaborated herein. It should be noted that the functions described for each module (sub-module, unit, or component, etc.) in the network devices 1900 and 2000 in the embodiments of the application may be implemented by different modules (sub-modules, units, or components, etc.), or may be implemented by the same module (sub-module, unit, or component, etc.).

[0301] Figure 21 is a schematic structural diagram of a communication device 2100 according to an embodiment of the present application. The communication device 2100 includes a processor 2110, and the processor 2110 can call and run a computer program from a memory, so that the communication device 2100 implements the method in the embodiment of the present application.

[0302] In one embodiment, the communication device 2100 may further include a memory 2121. Among them, the processor 2110 can call and run a computer program from the memory 2121, so that the communication device 2100 implements the method in the embodiment of the present application.

[0303] Among them, the memory 2121 may be a separate device independent of the processor 2110, or may be integrated in the processor 2110.

[0304] In one embodiment, the communication device 2100 may further include a transceiver 2130. The processor 2110 may control the transceiver 2130 to communicate with other devices. Specifically, it may send information or data to other devices, or receive information or data sent by other devices.

[0305] Among them, the transceiver 2130 may include a transmitter and a receiver. The transceiver 2130 may further include an antenna, and the number of antennas may be one or more.

[0306] In one embodiment, the communication device 2100 may be the network device of the embodiment of the present application, and the communication device 2100 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, it will not be elaborated here.

[0307] In one embodiment, the communication device 2100 may be the terminal device of the embodiment of the present application, and the communication device 2100 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, it will not be elaborated here.

[0308] Figure 22 It is a schematic structural diagram of a chip 2200 according to an embodiment of the present application. The chip 2200 includes a processor 2210. The processor 2210 may call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0309] In one embodiment, the chip 2200 may further include a memory 2220. Among them, the processor 2210 may call and run a computer program from the memory 2220 to implement the method executed by the terminal device or the network device in the embodiment of the present application.

[0310] Among them, the memory 2220 may be a separate device independent of the processor 2210, or may be integrated in the processor 2210.

[0311] In one embodiment, the chip 2200 may further include an input interface 2230. Among them, the processor 2210 may control the input interface 2230 to communicate with other devices or chips. Specifically, it may obtain information or data sent by other devices or chips.

[0312] In one embodiment, the chip 2200 may further include an output interface 2240. Among them, the processor 2210 may control the output interface 2240 to communicate with other devices or chips. Specifically, it may output information or data to other devices or chips.

[0313] In one embodiment, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0314] In one embodiment, the chip can be applied to the terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0315] The chips applied to the network device and the terminal device can be the same chip or different chips.

[0316] It should be understood that the chip mentioned in the embodiments of the present application can also be referred to as a system-on-chip, system chip, chip system, or system-on-chip, etc.

[0317] The above-mentioned processor can be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the above-mentioned general-purpose processor can be a microprocessor or any conventional processor, etc.

[0318] The above-mentioned memory can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM).

[0319] It should be understood that the above memory is for illustrative but not restrictive purposes. For example, the memory in the embodiments of the present application may also be a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDR SDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synch link dynamic random access memory (SLDRAM), and a direct rambus random access memory (DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0320] Figure 23 FIG. 2300 is a schematic block diagram of a communication system 2300 according to an embodiment of the present application. The communication system 2300 includes a terminal device 2310 and a network device 2320.

[0321] In one embodiment, the terminal device 2310 is configured to start GNSS measurement and / or start a timer related to GNSS measurement when the GNSS position is invalid.

[0322] In one embodiment, the terminal device 2310 is configured to obtain the duration of the GNSS valid timer, where the GNSS position of the terminal device is valid during the running of the GNSS valid timer.

[0323] In one embodiment, the network device 2320 is configured to obtain the duration of the GNSS valid timer.

[0324] Wherein, the terminal device 2310 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 2320 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, details are not described herein again.

[0325] 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 instructions are loaded and executed on a computer, the processes or functions in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that the computer can access or a data storage device such as a server or data center that includes one or more integrated available media. The available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a Solid State Disk (SSD)), etc.

[0326] It should be understood that in various embodiments of the present application, the order numbers of the above processes do not indicate the order of execution. The order of execution of each process should be determined according to its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0327] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the above-described systems, devices, and units can refer to the corresponding processes in the foregoing method embodiments, and will not be described herein again.

[0328] The above is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present application, and all should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for measuring position, include: When the GNSS position is invalid, the terminal device starts GNSS measurement and / or starts a timer related to GNSS measurement.

2. The method according to claim 1, in, The method further comprises: When the terminal device starts the GNSS measurement and starts the timer, the terminal device performs the GNSS measurement during the operation of the timer.

3. The method according to claim 1, in, The method further comprises: When the timer times out and the terminal device has not completed the GNSS measurement, the terminal device releases the radio resource control RRC connection and returns to the RRC idle state.

4. The method according to claim 1, in, The method further comprises: When the terminal device completes the GNSS measurement, the terminal device sends a notification message, where the notification message is used to notify the network device that the terminal device has completed the GNSS measurement.

5. The method according to claim 1, in, The method further comprises: After the terminal device starts the timer when the GNSS position is invalid, it waits for a GNSS measurement command during the timer.

6. The method according to claim 5, in, The method further comprises: When the timer times out and the terminal device does not receive the GNSS measurement command, the terminal device releases the RRC connection and returns to the RRC idle state.

7. The method according to any one of claims 1 to 6, in, The conditions for starting the timer include at least one of the following: The GNSS position is invalid; The uplink desynchronization of the terminal device is determined based on a closed-loop timing advance TA adjustment mechanism and / or a closed-loop frequency offset adjustment mechanism.

8. The method according to any one of claims 1 to 6, in, The method further comprises: When the terminal device receives the GNSS measurement command from the network device, the terminal device stops the timer.

9. The method according to any one of claims 1 to 6, in, The duration of the timer is configured by the network device.

10. A method for measuring position, It is characterized in that include: The network device configures the duration of a timer associated with GNSS measurement to the terminal device, wherein the terminal device starts the timer when the GNSS position is invalid.

11. The position measurement method according to claim 10, in, The method further comprises: The network device sends a GNSS measurement command to the terminal device, wherein the terminal device stops the timer when receiving the GNSS measurement command.

12. The position measurement method according to claim 10 or 11, in, The method further comprises: The network device receives a notification message sent by the terminal device, wherein the notification message is used to notify the terminal device that the GNSS measurement has been completed.

13. A terminal device, include: The processing unit is configured to start GNSS measurement and / or start a timer related to GNSS measurement when the GNSS position is invalid.

14. The terminal device according to claim 13, in, The processing unit is further configured to, when the GNSS measurement is started and the timer is started, perform the GNSS measurement during the timer is running.

15. The terminal device according to claim 13, in, The processing unit is also used to release the radio resource control RRC connection and return to the RRC idle state when the timer times out and the terminal device has not completed the GNSS measurement.

16. The terminal device according to claim 13, in, The terminal device further includes: a sending unit, configured to send notification information when the terminal device completes the GNSS measurement, wherein the notification information is used to notify the network device that the terminal device has completed the GNSS measurement.

17. A network device, It is characterized in that include: A configuration module is used to configure the duration of a timer related to GNSS measurement for a terminal device, wherein the terminal device starts the timer when the GNSS position is invalid.

18. The network device according to claim 17, in, The network device also includes: A sending module is used to send a GNSS measurement command to the terminal device, wherein the terminal device stops the timer when receiving the GNSS measurement command.

19. The network device according to claim 17 or 18, in, The network device also includes: A receiving module is used to receive a notification message sent by the terminal device, wherein the notification message is used to notify the terminal device that the GNSS measurement has been completed.

Images