Position measurement method, timer maintenance method and equipment

Abstract

A position measurement method (500, 600, 700), a terminal device (120, 1600, 1700, 1800, 231), and a network device (110, 1900, 2000, 232). The position measurement method (500, 600, 700) comprises: a terminal device (120, 1600, 1700, 1800, 231) starting a global navigation satellite system (GNSS) measurement and / or starting a timer associated with the GNSS measurement in the event that a GNSS position is ineffective (S510). According to the invention, the terminal device (120, 1600, 1700, 1800, 231) can autonomously initiate GNSS measurements in the event that the GNSS position is ineffective, so that the valid GNSS position can be obtained in time, and state transitions of the terminal device (120, 1600, 1700, 1800, 231) are reduced.

Description

Position measurement method, timer maintenance method and device Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a position measurement method, a timer maintenance method, and a device. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) is currently researching NTN (Non-Terrestrial Network) technology. NTN typically uses satellite communications to provide communication services to terrestrial users. In NTN, the Global Navigation Satellite System (GNSS) is used to measure terminal locations.

[0003] Summary of the Invention

[0004] The present invention provides a method for measuring a position, including:

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

[0006] The present invention provides a timer maintenance method, including:

[0007] The terminal device obtains the duration of the GNSS valid timer, wherein the GNSS position of the terminal device is valid during the running of the GNSS valid timer.

[0008] The present invention provides a timer maintenance method, including:

[0009] The network device obtains the duration of the GNSS valid timer of the terminal device, wherein the GNSS position of the terminal device is valid during the running of the GNSS valid timer.

[0010] An embodiment of the present application provides a terminal device, including:

[0011] The processing unit is configured to start GNSS measurement and / or start a timer related to GNSS measurement when the GNSS position is invalid.

[0012] An embodiment of the present application provides a terminal device, including:

[0013] A processing unit is used to obtain the duration of a GNSS valid timer, wherein the GNSS position of the terminal device is valid during the operation of the GNSS valid timer.

[0014] An embodiment of the present application provides a network device, including:

[0015] A processing unit is used to obtain the duration of a GNSS valid timer of a terminal device, wherein the GNSS position of the terminal device is valid during the operation of the GNSS valid timer.

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

[0017] An embodiment of the present application provides a network device, comprising a processor and a memory, wherein 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.

[0018] The embodiments of the present application provide a chip for implementing the above-mentioned position measurement method and / or timer maintenance method.

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

[0020] An embodiment of the present application provides a computer-readable storage medium for storing a computer program. When the computer program is executed by a device, the device executes the above-mentioned position measurement method and / or timer maintenance method.

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

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

[0023] In an embodiment of the present application, when the GNSS position is invalid, the terminal device can autonomously initiate GNSS measurement to obtain a valid GNSS position in a timely manner, reducing the state transitions of the terminal device. In an embodiment of the present application, when the GNSS position is invalid, the terminal device can start a timer to extend the waiting time for the GNSS measurement command, reducing the state transitions of the terminal device. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] FIG1 is a schematic diagram of an application scenario according to an embodiment of the present application.

[0025] FIG2 is a schematic diagram of an NTN network architecture based on transparent forwarding according to an embodiment of the present application.

[0026] FIG3 is a schematic diagram of an NTN network architecture based on regeneration and forwarding according to an embodiment of the present application.

[0027] FIG4A is a schematic diagram of a case without timing advance.

[0028] FIG4B is a schematic diagram of a timing advance.

[0029] FIG5 is a schematic flowchart of a position measurement method according to an embodiment of the present application.

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

[0031] FIG7 is a schematic flowchart of a position measurement method according to another embodiment of the present application.

[0032] FIG8 is a schematic flowchart of a timer maintenance method according to an embodiment of the present application.

[0033] FIG9 is a schematic flowchart of a timer maintenance method according to another embodiment of the present application.

[0034] FIG10 is a schematic flowchart of a timer maintenance method according to an embodiment of the present application.

[0035] FIG11 is a schematic flowchart of a timer maintenance method according to another embodiment of the present application.

[0036] FIG12 is a schematic diagram of Example 1 according to an embodiment of the present application.

[0037] FIG13 is a schematic diagram of Example 2 according to an embodiment of the present application.

[0038] FIG14 is a schematic diagram of Example 3 according to an embodiment of the present application.

[0039] FIG15 is a schematic diagram of Example 4 according to an embodiment of the present application.

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

[0041] FIG17 is a schematic block diagram of a terminal device according to an embodiment of the present application.

[0042] FIG18 is a schematic block diagram of a terminal device according to another embodiment of the present application.

[0043] FIG19 is a schematic block diagram of a network device according to an embodiment of the present application.

[0044] FIG20 is a schematic block diagram of a network device according to another embodiment of the present application.

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

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

[0047] Figure 23 is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0048] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0049] 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, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

[0050] 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, etc. The embodiments of the present application can also be applied to these communication systems.

[0051] In one embodiment, 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.

[0052] In one embodiment, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein 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, wherein the authorized spectrum can also be considered as an unshared spectrum.

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

[0054] 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 capabilities, a computing device or other processing device 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.

[0055] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

[0056] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, 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 a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0057] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0058] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (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.

[0059] 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. Alternatively, 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 set up in a location such as land or water.

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

[0061] FIG1 exemplarily illustrates a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include multiple network devices 110, and each network device 110 may include a different number of terminal devices 120 within its coverage area, which is not limited in this embodiment of the present application.

[0062] In one embodiment, 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), which is not limited in this embodiment of the present application.

[0063] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment can be an evolutionary base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), pico base station, access point (AP), transmission point (TP) or new generation base station (new generation Node B, gNodeB), etc. in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.

[0064] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system shown in Figure 1 as an example, the communication device may include a network device and a terminal device having a communication function. The network device and the terminal device may be specific devices in the embodiments of the present application and will not be described in detail here. The communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.

[0065] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0066] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" 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 between A and B.

[0067] In the description of 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 being indicated, configuration and being configured, etc.

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

[0069] Compared to terrestrial cellular communications, satellite communications offer many unique advantages. First, satellite communications are not restricted by user location. For example, conventional terrestrial communications cannot reach areas such as oceans, high mountains, and deserts where communication equipment is unavailable or where there is a sparse population. However, satellite communications, because a single satellite can cover a large area and orbits the Earth, theoretically every corner of the globe can be covered. Second, satellite communications have significant social value. Satellite communications can provide low-cost coverage in remote mountainous areas and impoverished countries and regions, enabling people in these areas to enjoy advanced voice communications and mobile internet technologies, helping to narrow the digital divide with developed regions and promoting their development. Third, satellite communications offer long range, and the cost of communications does not increase significantly with increasing distance. Finally, satellite communications are highly stable and unaffected by natural disasters.

[0070] Communication satellites are categorized by their orbital altitude into LEO (Low-Earth Orbit), MEO (Medium-Earth Orbit), GEO (Geostationary Earth Orbit), and HEO (High Elliptical Orbit). Currently, research focuses on LEO and GEO.

[0071] LEO satellites have an altitude range of 500 km to 1500 km (kilometers), corresponding to an orbital period of approximately 1.5 to 2 hours. Signal propagation delay for single-hop communication between users is typically less than 20 milliseconds (ms). The maximum satellite visibility time is 20 minutes. The short signal propagation distance and low link loss reduce the transmit power requirements of user terminals.

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

[0073] In order to ensure satellite coverage and improve the system capacity of the entire satellite communication system, satellites use multiple beams to cover the ground. A 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 tens to hundreds of kilometers.

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

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

[0076] One or more gateways used to connect satellites and terrestrial public networks.

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

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

[0079] Satellite: Based on the functions it provides, it can be divided into two types: transparent forwarding and regenerative forwarding.

[0080] Transparent forwarding: only provides wireless frequency filtering, frequency conversion and amplification functions. It only provides transparent forwarding of signals and will not change the waveform signal it forwards.

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

[0082] Intersatellite link: exists in the regenerative forwarding network architecture.

[0083] LTE / NR terrestrial network uplink timing advance

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

[0085] To ensure orthogonality in uplink transmissions and avoid intra-cell interference, the eNB / gNB requires that signals from different UEs arriving at the same time but on different frequency resources arrive at the eNB / gNB at roughly the same time. To ensure time synchronization on the eNB / gNB side, LTE / NR supports an uplink timing advance mechanism.

[0086] In the scenario of time synchronization on the eNB / gNB side, FIG4A is a schematic diagram without timing advance, and FIG4B is a schematic diagram with timing advance. P1 and T P2 This represents the one-way transmission delay of signals from the base station to the UE. The uplink (UL) and downlink (DL) clocks on the eNB / gNB are identical, while those on the UE are offset, and different UEs have different uplink timing advances. By appropriately controlling the offset for each UE, the eNB / gNB can control the arrival time of uplink signals from different UEs at the eNB / gNB. UEs farther from the eNB / gNB experience greater transmission delay and therefore need to send uplink data earlier than UEs closer to the eNB / gNB.

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

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

[0089] 2. Adjustment of TA in RRC (Radio Resource Control) Connected State: Although the UE and the eNB / gNB achieve uplink synchronization during random access, the timing of the uplink signal reaching the eNB / gNB may change over time. Therefore, the UE needs to continuously update its uplink timing advance to maintain uplink synchronization. If a UE's TA needs to be corrected, the eNB / gNB will send a Timing Advance Command to the UE, requesting it to adjust the uplink timing. This Timing Advance Command is sent to the UE via the Timing Advance Command MAC (Medium Access Control) CE (Control Element).

[0090] TA maintenance in NTN

[0091] In traditional TN (Terrestrial Network), UE performs TA maintenance based on TA commands issued by the network. For Rel-17 NTN, assuming that UEs have GNSS (Global Navigation Satellite System) positioning capabilities and TA pre-compensation capabilities, UEs can estimate the service link TA based on the UE position and the position of the serving satellite. Therefore, a TA determination method combining open-loop and closed-loop is introduced in NTN. Based on the current R17 standard, for NTN UEs in RRC_IDLE / INACTIVE and RRC_CONNECTED states, their timing advance (TA) can be determined by the following formula:

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

[0093] Among them, N TA The scenario for PRACH (Physical Random Access Channel) transmission is defined as 0 and can be updated later through the TA command in Msg2 / MsgB and the TA command MAC CE; N TA,UE-specificIt is the TA of the service link estimated by the UE itself and used for TA pre-compensation. Specifically, the terminal will obtain the satellite position based on its own GNSS position information combined with the satellite ephemeris information broadcast by the serving cell, and thus calculate the propagation delay of the service link from the UE to the satellite. TA,common It is a public TA controlled by the network and contains any timing deviation N that the network considers necessary. TA,offset is a fixed offset for calculating TA.

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

[0095] R17 IoT (Internet of Things) NTN GNSS Operations

[0096] In Release 17 IoT NTN (i.e., scenarios where NB-IoT (NarrowBand Internet of Things) and eMTC (enhanced Machine-Type Communication) are connected to the NTN), the GNSS measurement module and communication module of an IoT terminal cannot operate simultaneously (Simultaneous GNSS and NTN NB-IoT / eMTC operation is not assumed). In Release 17 NTN, IoT terminals can only perform GNSS measurements to obtain location information in RRC IDLE or RRC INACTIVE states. The GNSS module cannot be activated in the RRC CONNECTED state. Therefore, the UE must first obtain its own GNSS position using the GNSS module before entering the RRC CONNECTED state. The UE determines the GNSS position validity period based on its own circumstances (such as its mobility) and reports the remaining GNSS position validity period to the network during RRC connection establishment, reestablishment, or recovery. For a UE in the RRC CONNECTED state, if its GNSS position expires, the UE cannot perform GNSS operations in the RRC CONNECTED state and cannot calculate the TA. Therefore, the UE must return to the RRC IDLE state.

[0097] GNSS enhancements for R18 IoT NTN

[0098] The R18 IoT NTN Enhancement Project includes the following research objectives:

[0099] Disabling of HARQ feedback to mitigate impact of HARQ stalling on UE data rates[RAN1,RAN2]

[0100] 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]

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

[0102] In addition, GNSS enhancements for IoT terminals connected to NTN can also include:

[0103] 1. An IoT NTN UE may need to reacquire a valid GNSS position fix during a long RRC connection. How can the UE update or reduce the need to update the GNSS position fix during an RRC connection?

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

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

[0106] (1) The UE reacquires the GNSS position fix based on timer control.

[0107] (2) A new gap is introduced during which the UE reacquires the GNSS position fix.

[0108] 4. For triggering connected GNSS measurements, consider:

[0109] (1) UE-triggered GNSS measurement.

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

[0111] In addition, the base station can use MAC CE to aperiodically trigger the UE to perform GNSS measurements. The UE can report the measurement time required for GNSS position fix at least during initial access. UEs in RRC connected state can use MAC CE to report the GNSS validity period.

[0112] For GNSS measurements in the RRC connected state, the network can aperiodically trigger the UE to perform GNSS measurements. Typically, the network can trigger the GNSS to perform GNSS measurements before the GNSS becomes invalid based on the GNSS validity period reported by the UE. In some cases, if the UE does not receive a GNSS measurement command even after the GNSS position becomes invalid, the UE's behavior can be determined in detail in the embodiments of this application.

[0113] FIG5 is a schematic flow chart of a position measurement method 500 according to an embodiment of the present application. The method can optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents.

[0114] S510: When the GNSS position is invalid, the terminal device starts GNSS measurement and / or starts a timer related to GNSS measurement.

[0115] 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. The terminal device may autonomously or actively trigger the start of GNSS measurement when its own GNSS position is invalid. The terminal device may also start a timer related to GNSS measurement when its own GNSS position is invalid. The terminal device may also autonomously or actively trigger the start of GNSS measurement and start a timer related to GNSS measurement when its own GNSS position is invalid.

[0116] In one embodiment, the condition for starting the timer includes at least one of the following:

[0117] The GNSS position is invalid;

[0118] The terminal device has not received a GNSS measurement command from the network device since completing the most recent GNSS measurement;

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

[0120] For example, 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, the terminal device autonomously initiates the GNSS measurement and starts the first 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 completing the most recent GNSS measurement, and the terminal device is determined to be 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 the GNSS measurement and starts the second timer.

[0122] For another example, the terminal device starts the 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 most recent GNSS measurement.

[0123] 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 completing the most recent GNSS measurement, and the terminal device is determined to be 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.

[0124] In an embodiment of the present application, determining the uplink desynchronization of the terminal device based on a closed-loop TA adjustment mechanism and / or a closed-loop frequency offset adjustment mechanism may include: determining the uplink desynchronization of the terminal device based on a closed-loop TA adjustment mechanism, determining the uplink desynchronization of the terminal device based on a closed-loop frequency offset adjustment mechanism, and determining the uplink desynchronization of the terminal device based on a closed-loop TA adjustment mechanism and a closed-loop frequency offset adjustment mechanism. Other methods for determining the uplink desynchronization of the terminal device may also be used, which are not limited in the embodiments of the present application.

[0125] In one embodiment, as shown in FIG6 , the method further includes:

[0126] S610: When the terminal device starts the GNSS measurement and the timer, the terminal device performs the GNSS measurement while the timer is running.

[0127] For example, the terminal device may perform GNSS measurement during the operation of the first timer or the second timer to obtain the GNSS position of the terminal device based on the GNSS measurement result.

[0128] In one embodiment, as shown in FIG6 , the method further includes:

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

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

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

[0132] 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 completing the most recent GNSS measurement, and the terminal device is determined to be 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 initiates the GNSS measurement and starts a second timer. When the second timer times out and the terminal device has not completed the GNSS measurement, the terminal device releases the RRC connection and returns to the RRC idle state or the terminal device triggers the RLF process.

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

[0134] In one embodiment, as shown in FIG6 , the method further includes:

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

[0136] In some examples, if the duration of the timer associated with the GNSS measurement includes the duration for completing the GNSS measurement, the timer may be stopped after the terminal device completes the GNSS measurement.

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

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

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

[0140] In one embodiment, when the terminal device completes at least one of GNSS measurement, uplink synchronization and downlink synchronization, the terminal device sends a notification message, which is used to notify the network device that the terminal device has completed at least one of GNSS measurement, uplink synchronization and downlink synchronization.

[0141] For example, the UE may 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 RACH, MAC CE, etc.).

[0142] In one embodiment, as shown in FIG7 , the method further includes:

[0143] S710: After the terminal device starts the timer when the GNSS position is invalid, the terminal device waits for a GNSS measurement command during 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 most recent GNSS measurement, the terminal device waits for a GNSS measurement command during the timer.

[0144] In an embodiment of the present application, if a terminal device's GNSS position is invalid and the terminal device has not received a GNSS measurement command from a network device since completing the most recent GNSS measurement, the terminal device may not autonomously or proactively trigger the initiation of a GNSS measurement, but may instead start a timer associated with a GNSS measurement. While the timer is running, the terminal device may wait for a GNSS measurement command from the network device. If the GNSS measurement command has not been received after the timer expires, the terminal device may stop waiting for the GNSS measurement command.

[0145] In one embodiment, as shown in FIG7 , the method further includes:

[0146] S720: When the timer times out and the terminal device does not receive 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.

[0147] For another example, when the GNSS position of a terminal device in an RRC connected state is invalid and the terminal device has not received a GNSS measurement command from a network device since completing the most recent GNSS measurement, a third timer is started. 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.

[0148] For another example, when the GNSS position of a terminal device in an RRC connection state is invalid, and the terminal device has not received a GNSS measurement command from a network device since completing the most recent GNSS measurement, and the terminal device is determined to be out of uplink synchronization based on a closed-loop timing advance TA adjustment mechanism and / or a closed-loop frequency offset adjustment mechanism, a fourth timer is started. 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.

[0149] In one embodiment, as shown in FIG7 , the method further includes:

[0150] S730: When the terminal device receives the GNSS measurement command from the network device, the terminal device stops the timer. This step may be performed after S610 or after S710.

[0151] For example, during the operation of the 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 fourth timer, if the terminal device receives the GNSS measurement command from the network device, the fourth timer is stopped.

[0152] In one embodiment, 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 first timer, the second timer, the third timer, and the fourth timer.

[0153] In one embodiment, the duration of the timer reuses the duration of a measurement gap.

[0154] In one embodiment, the invalid GNSS position includes: a GNSS validity timer expires.

[0155] For example, when the GNSS valid timer times out and the terminal device has not received a GNSS measurement command from the network device since completing the most recent GNSS measurement, the terminal device autonomously starts the GNSS measurement and starts the first timer.

[0156] For another example, when the GNSS valid timer times out and the terminal device has not received a GNSS measurement command from the network device since completing the most recent GNSS measurement, and the terminal device is determined to be 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 the GNSS measurement and starts the second timer.

[0157] For another example, when the GNSS valid timer times out and the terminal device has not received a GNSS measurement command from the network device since completing the most recent GNSS measurement, the terminal device starts the third timer.

[0158] 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 completing the most recent GNSS measurement, and the terminal device is determined to be 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.

[0159] In embodiments of the present application, the GNSS validity timer can be used to determine whether the GNSS measurement result, i.e., the GNSS position, of a terminal device is valid. While the GNSS validity timer is running, the terminal device and network equipment can consider the GNSS position of the terminal device to be valid. The GNSS validity timer can also be referred to by other names, such as the GNSS measurement result validity timer, the GNSS position validity timer, or the GNSS result timer. For specific maintenance methods for the GNSS validity timer, please refer to the description of the following timer maintenance method embodiment.

[0160] In an embodiment of the present application, when the GNSS position is invalid, the terminal device can autonomously initiate GNSS measurement to obtain a valid GNSS position in a timely manner, reducing the state transitions of the terminal device. When the GNSS position is invalid, the terminal device can start a timer to extend the waiting time for the GNSS measurement command, reducing the state transitions of the terminal device. For example, a terminal device in an RRC connected state can restore or maintain uplink synchronization as much as possible while maintaining the RRC connection, thereby improving the user experience.

[0161] Figure 8 is a schematic flow chart of a timer maintenance method 800 according to one embodiment of the present application. This method may optionally be applied to the system shown in Figure 1, but is not limited thereto. This embodiment may be implemented independently or in combination with the aforementioned position measurement method embodiment. The timer maintenance method includes at least some of the following contents.

[0162] S810. The terminal device obtains the duration of the GNSS valid timer, wherein the GNSS position of the terminal device is valid during the running of the GNSS valid timer.

[0163] In an embodiment of the present application, the terminal device can obtain the duration of the GNSS valid timer locally, or obtain the duration of the GNSS valid timer 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 of a GNSS valid timer timeout, 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 be expired. In an embodiment of the present application, the terminal device can know whether its current GNSS position is available in a timely manner by maintaining the GNSS valid timer, such as obtaining the duration of the GNSS valid timer. 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 determine the TA using the valid GNSS position.

[0164] In one embodiment, as shown in FIG9 , the timer maintenance method 900 further includes:

[0165] S910. The terminal device sends first information, where the first information is used to report the duration of the GNSS valid timer. The duration of the GNSS valid timer is determined by the terminal device.

[0166] In an embodiment of the present application, if the terminal device itself determines the duration of the GNSS valid timer, the terminal device can send first information such as 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.

[0167] In one embodiment, as shown in FIG9 , the timer maintenance method further includes:

[0168] S920. When sending the first information, the terminal device starts the GNSS validity timer.

[0169] In an embodiment of the present application, if the terminal device reports the duration of the GNSS valid timer to the network device via uplink signaling, the GNSS valid timer can be started when the uplink signaling is sent.

[0170] In one embodiment, as shown in FIG9 , the timer maintenance method further includes:

[0171] S930. The terminal device receives second information, where the second information is used to configure the duration of the GNSS valid timer.

[0172] In the timer maintenance method of the embodiment of the present application, only S910 and S920 may be included, only S930 may be included, or all three steps may be included. For example, if the duration of the GNSS valid timer is determined by the network device, the method may include S930. If the duration of the GNSS valid timer is determined by the terminal device, the method may include S910 and S920. If both the terminal device and the network device are capable of determining the duration of the GNSS valid timer, the method may include S910, S920, and S930, and the terminal device and the network device may use the duration of the GNSS valid timer received from each other to verify the local duration.

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

[0174] In one embodiment, the terminal device starts the GNSS validity timer based on the duration of the GNSS validity timer. The GNSS validity timer is started in at least one of the following ways:

[0175] Upon receiving the second information, the terminal device starts the GNSS validity timer;

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

[0177] For example, if the terminal device receives downlink signaling for indicating the duration of the GNSS valid timer, the GNSS valid timer may be started upon receipt of the downlink signaling.

[0178] For example, if the terminal device receives downlink signaling indicating the duration of the GNSS valid timer, the GNSS valid timer may be started based on a specified time point indicated by the downlink signaling.

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

[0180] In one embodiment, the designated time point includes at least one of the following:

[0181] The second information includes the time point for starting the GNSS validity timer; this is an explicit indication method.

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

[0183] In one embodiment, as shown in FIG9 , the timer maintenance method further includes:

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

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

[0186] For another example, if the terminal device has started a GNSS valid timer, the GNSS valid timer may be stopped when the terminal device starts performing GNSS measurement based on a GNSS measurement command or autonomously.

[0187] Figure 10 is a schematic flow chart of a timer maintenance method 1000 according to one embodiment of the present application. This method may optionally be applied to the system shown in Figure 1 , but is not limited thereto. This embodiment may be implemented independently or in combination with the aforementioned position measurement method embodiment. The timer maintenance method includes at least some of the following contents.

[0188] S1010. The network device obtains the duration of the GNSS valid timer of the terminal device, wherein the GNSS position of the terminal device is valid during the running of the GNSS valid timer.

[0189] In one embodiment, as shown in FIG11 , the timer maintenance method 1100 further includes:

[0190] S1110. The network device receives first information, where the first information 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.

[0191] In one implementation, the GNSS validity timer is started by the terminal device when sending the first information.

[0192] In one embodiment, as shown in FIG11 , the timer maintenance method further includes: the network device configuring the duration of the GNSS valid timer for the terminal device. Specific configuration methods may include:

[0193] S1120: The network device sends second information, where the second information is used to configure the duration of the GNSS valid timer.

[0194] In the timer maintenance method of the embodiment of the present application, only S1110, only S1120, or both steps may be included. For example, if the duration of the GNSS valid timer is determined by the network device, the method may include S1120. If the duration of the GNSS valid timer is determined by the terminal device, the method may include S1110. If both the terminal device and the network device are capable of determining the duration of the GNSS valid timer, the method may include S1110 and S1120, and the terminal device and the network device may use the duration of the GNSS valid timer received from each other to verify the local duration.

[0195] In one embodiment, the second information is used to indicate that the GNSS validity timer is started at a specified time point. In the embodiment of the present application, the second information may explicitly indicate the specified time point or may implicitly indicate the specified time point.

[0196] In one embodiment, the designated time point includes at least one of the following:

[0197] The second information includes the time point of starting the GNSS validity timer;

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

[0199] In one embodiment, as shown in FIG11 , the timer maintenance method further includes:

[0200] S1130: The network device sends a GNSS measurement command, where the GNSS measurement command is used to stop the GNSS validity timer.

[0201] For specific examples of the network device executing methods 1000 and 1100 of this embodiment, reference can be made to the relevant descriptions of the network device in the above methods 800 and 900 , which will not be repeated here for the sake of brevity.

[0202] The location measurement method and / or timer maintenance method of the embodiments of the present application can be used in scenarios where a terminal in an NTN maintains uplink synchronization. For example, a method for maintaining uplink synchronization of a terminal in an NTN may include the following:

[0203] Method 1: After the GNSS valid timer expires, the UE autonomously starts GNSS measurement and starts a first timer. If the UE has not completed the 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.

[0204] Method 2: When the GNSS validity timer expires and the UE determines that the UE has lost uplink synchronization based on the closed-loop TA and / or frequency offset adjustment mechanism, the UE autonomously initiates GNSS measurement and starts a second timer. 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 RLF.

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

[0206] Method 4: When the GNSS validity timer expires and the UE determines that the UE has lost uplink synchronization 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 before the fourth timer expires, the UE releases the RRC connection and returns to the RRC IDLE state, or the UE triggers RLF.

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

[0208] Example 1:

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

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

[0211] 1. A UE in the RRC connected state maintains a GNSS validity timer. The duration of the GNSS validity timer and the conditions for starting the timer are as follows:

[0212] (1) The timer 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 timer duration of the GNSS valid timer.

[0213] (2) The timer length of the GNSS valid timer is configured by the base station to the UE through downlink signaling (such as MAC CE, RRC signaling). For example, the base station can configure the timer length of the GNSS valid timer based on the GNSS valid time most recently reported by the UE.

[0214] The time at which the UE starts the GNSS validity timer may be one of the following:

[0215] a. Upon receiving the GNSS valid timer duration configuration, the UE starts the GNSS valid timer.

[0216] b. The UE starts the GNSS validity timer at a specified time based on a network instruction. For example, the network explicitly instructs the UE to start the GNSS validity timer when configuring the GNSS validity timer duration, or the UE uses the time point at which the GNSS validity timer duration configuration takes effect (such as the time point at which the downlink signaling carrying the GNSS validity timer duration configuration takes effect) as the time to start the GNSS validity timer.

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

[0218] 3. The UE starts a first timer when a first condition is met, and the UE performs GNSS measurement during the running of the first timer.

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

[0220] (2) The duration of the first timer is configured by the network, for example, the duration of the reused measurement gap, or the network independently configures the duration of the first timer.

[0221] 4. If the UE completes GNSS measurement and / or uplink synchronization and / or downlink synchronization, the UE informs 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.).

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

[0223] 6. If the first timer times out and the UE has not completed the 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.

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

[0225] Example 2:

[0226] When the GNSS validity timer expires and the UE determines that the UE uplink is out of sync based on the closed-loop TA and / or frequency offset adjustment mechanism, the UE autonomously initiates GNSS measurement. Specifically, when the GNSS validity timer expires and the UE determines that the UE uplink is out of sync based on the closed-loop TA and / or frequency offset adjustment mechanism, the UE autonomously initiates GNSS measurement and simultaneously starts a second timer. 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 RLF.

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

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

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

[0230] 3. The UE starts a second timer when the second condition is met, and the UE performs GNSS measurement during the running of the second timer.

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

[0232] (2) The duration of the second timer is configured by the network, for example, the duration of the reused measurement gap, or the network independently configures the duration of the second timer.

[0233] 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.).

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

[0235] 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 RLF.

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

[0237] Example 3:

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

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

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

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

[0242] 3. The UE starts a third timer when the first condition is met. The first condition is the same as step 3 of Example 1. The duration of the third timer is configured by the network.

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

[0244] 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 RLF.

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

[0246] Example 4:

[0247] When the GNSS validity timer expires and the UE determines that the UE has lost uplink synchronization based on the closed-loop TA and / or frequency offset adjustment mechanism, the UE continues to wait for the network to issue a GNSS measurement command within a certain period of time. Specifically, when the GNSS validity timer expires and the UE determines that the UE has lost uplink synchronization 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.

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

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

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

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

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

[0253] 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 RLF.

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

[0255] The embodiments of the present application provide a method for measuring GNSS by a terminal in an NTN, which clarifies the behavior of the UE when the GNSS position is invalid and no GNSS measurement command has been received from the network. By introducing GNSS measurement triggered by the UE itself or continuing to wait for the GNSS measurement command from the network for a period of time, the UE can restore or maintain uplink synchronization as much as possible while maintaining the RRC connection, thereby improving the user experience.

[0256] FIG16 is a schematic block diagram of a terminal device 1600 according to an embodiment of the present application. The terminal device 1600 may include:

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

[0258] In one embodiment, 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.

[0259] In one embodiment, the processing unit is further configured to release the radio resource control (RRC) connection and return to the RRC idle state or trigger a radio link failure (RLF) process by the terminal device when the timer times out and the terminal device has not completed the GNSS measurement.

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

[0261] In one embodiment, the terminal device also includes a sending unit for sending notification information when the terminal device completes at least one of GNSS measurement, uplink synchronization and downlink synchronization. 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.

[0262] In one embodiment, the processing unit is further configured to start 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, and wait for a GNSS measurement command during the timer.

[0263] In one embodiment, the processing unit is further configured to release the RRC connection and return to the RRC idle state or trigger an RLF process for the terminal device when the timer times out and the terminal device does not receive the GNSS measurement command.

[0264] In one embodiment, the condition for the processing unit to start the timer includes at least one of the following:

[0265] The GNSS position is invalid;

[0266] The terminal device does not receive a GNSS measurement command from the network device;

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

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

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

[0270] In one implementation, the duration of the timer reuses the duration of the measurement interval.

[0271] In one embodiment, the invalid GNSS position includes: a GNSS validity timer expires.

[0272] The terminal device 1600 of the embodiment of the present application can implement the corresponding functions of the terminal devices 500, 600, and 700 in the aforementioned method embodiment. The processes, functions, implementation methods, and beneficial effects corresponding to the various modules (sub-modules, units, or components, etc.) in the terminal device 1600 can be found in the corresponding descriptions in the aforementioned method embodiment, and will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units, or components, etc.) in the terminal device 1500 of the embodiment of the application can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.).

[0273] FIG17 is a schematic block diagram of a terminal device 1700 according to an embodiment of the present application. The terminal device 1700 may include:

[0274] The processing unit 1710 is configured to obtain a duration of a GNSS valid timer, wherein the GNSS position of the terminal device is valid during the running of the GNSS valid timer.

[0275] In one embodiment, as shown in FIG18 , the terminal device 1800 further includes:

[0276] The sending unit 1810 is used to send first information, where the first information 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.

[0277] In one embodiment, the terminal device further includes:

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

[0279] In one embodiment, as shown in FIG18 , the terminal device further includes:

[0280] The receiving unit 1820 is configured to receive second information, where the second information is used to configure the duration of the GNSS valid timer.

[0281] In one embodiment, the processing unit starts the GNSS validity timer in at least one of the following ways:

[0282] Upon receiving the second information, starting the GNSS validity timer;

[0283] The GNSS validity timer is started at a specified time point based on the second information.

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

[0285] The time point for starting the GNSS validity timer included in the second information;

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

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

[0288] The terminal devices 1700 and 1800 of the embodiments of the present application can implement the corresponding functions of the terminal devices in the aforementioned methods 800 and 900. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the terminal devices 1700 and 1800 can be found in the corresponding descriptions in the above-mentioned method embodiments, which will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the terminal devices 1700 and 1800 of the embodiment of the application can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).

[0289] FIG19 is a schematic block diagram of a network device 1900 according to an embodiment of the present application. The network device 1900 may include:

[0290] The processing unit 1910 is configured to obtain a duration of a GNSS valid timer of a terminal device, wherein the GNSS position of the terminal device is valid during the running of the GNSS valid timer.

[0291] In one embodiment, as shown in FIG20 , the network device 2000 further includes:

[0292] The receiving unit 2010 is used to receive first information, where the first information 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.

[0293] In one implementation, the GNSS validity timer is started by the terminal device when sending the first information.

[0294] In one implementation, the network device further includes: a first sending unit 2020, configured to send second information, where the second information is used to configure the duration of the GNSS valid timer.

[0295] In one embodiment, the second information is used to instruct the GNSS validity timer to start at a specified time point.

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

[0297] The time point for starting the GNSS validity timer included in the second information;

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

[0299] In one embodiment, as shown in FIG20 , the network device further includes:

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

[0301] The network devices 1900 and 2000 of the embodiments of the present application can implement the corresponding functions of the network devices 1000 and 1100 in the aforementioned method embodiments. The processes, functions, implementation methods, and beneficial effects corresponding to the various modules (sub-modules, units, or components, etc.) in the network devices 1900 and 2000 can be found in the corresponding descriptions in the aforementioned method embodiments and will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units, or components, etc.) in the network devices 1900 and 2000 of the embodiments of the application can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.).

[0302] 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, which can call and execute a computer program from a memory to enable the communication device 2100 to implement the method in the embodiment of the present application.

[0303] In one embodiment, the communication device 2100 may further include a memory 2121. The processor 2110 may call and execute a computer program from the memory 2121 to enable the communication device 2100 to implement the method in the embodiment of the present application.

[0304] The memory 2121 may be a separate device independent of the processor 2110 , or may be integrated into the processor 2110 .

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

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

[0307] In one embodiment, the communication device 2100 may be a network device of an 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, they will not be repeated here.

[0308] In one embodiment, the communication device 2100 may be a terminal device of an 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, they will not be repeated here.

[0309] 22 is a schematic structural diagram of a chip 2200 according to an embodiment of the present application. The chip 2200 includes a processor 2210, which can call and execute a computer program from a memory to implement the method according to the embodiment of the present application.

[0310] In one embodiment, the chip 2200 may further include a memory 2220. The processor 2210 may call and execute 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.

[0311] The memory 2220 may be a separate device independent of the processor 2210 , or may be integrated into the processor 2210 .

[0312] In one embodiment, the chip 2200 may further include an input interface 2230. The processor 2210 may control the input interface 2230 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0313] In one embodiment, the chip 2200 may further include an output interface 2240. The processor 2210 may control the output interface 2240 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0314] 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 each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0315] 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 each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0316] The chips used in the network device and the terminal device may be the same chip or different chips.

[0317] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0318] The processor mentioned above may 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. The general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

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

[0320] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0321] FIG23 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 .

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

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

[0324] In one implementation, the network device 2320 is configured to obtain the duration of a GNSS valid timer.

[0325] 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, they are not described here in detail.

[0326] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, 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 in accordance with 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 devices. 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 a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0327] It should be understood that in the 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.

[0328] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0329] 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 modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included within the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A position measurement method, comprising: When the Global Navigation Satellite System (GNSS) position of the terminal device is invalid, the terminal device starts GNSS measurement and / or starts a timer related to GNSS measurement.

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

3. The method according to claim 1 or 2, wherein, The method further comprises: When the timer expires and the terminal device has not completed GNSS measurement, the terminal device releases the Radio Resource Control (RRC) connection to return to the RRC idle state or the terminal device triggers a Radio Link Failure (RLF) process.

4. The method according to any one of claims 1 to 3, wherein, The method further comprises: When the terminal device completes at least one of GNSS measurement, uplink synchronization, and downlink synchronization, the timer is stopped.

5. The method according to any one of claims 1 to 4, wherein The method further comprises: When the terminal device completes 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.

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

7. The method according to claim 6, wherein, The method further comprises: When the timer expires and the terminal device has not received the GNSS measurement command, the terminal device releases the RRC connection to return to the RRC idle state or the terminal device triggers an RLF process.

8. The method according to any one of claims 1 to 7, wherein The conditions for starting the timer include at least one of the following: The GNSS position is invalid; The terminal device has not received a GNSS measurement command from the network device since completing the most recent GNSS measurement; 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.

9. The method according to any one of claims 1 to 8, wherein, The method further comprises: When the terminal device receives the GNSS measurement command from the network device, the timer is stopped.

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

11. The method according to claim 10, wherein, The duration of the timer reuses the duration of the measurement interval.

12. The method according to any one of claims 1 to 10, wherein The invalid GNSS position includes: the expiration of the GNSS valid timer.

13. A timer maintenance method, comprising: The terminal device obtains 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.

14. The method according to claim 13, wherein, The method further comprises: The terminal device sends 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.

15. The method according to claim 14, wherein The method further comprises: When the terminal device sends the first information, the GNSS valid timer is started.

16. The method according to any one of claims 13 to 15, wherein, The method further comprises: The terminal device receives second information for configuring the duration of the GNSS valid timer.

17. The method according to claim 16, wherein, The starting methods of the GNSS valid timer include at least one of the following: When the terminal device receives the second information, it starts the GNSS valid timer; The terminal device starts the GNSS valid timer at a specified time point based on the second information.

18. The method according to claim 17, wherein, The specified time point includes at least one of the following: The second information includes the time point for starting the GNSS valid timer; The effective time point of the second information.

19. The method according to any one of claims 13 to 18, wherein, The method further includes: When the terminal device receives a GNSS measurement command, it stops the GNSS valid timer; or, when the terminal device starts to perform GNSS measurement, it stops the GNSS valid timer.

20. A timer maintenance method, including: 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.

21. The method according to claim 20, wherein, The method further includes: The network device receives the first information, which 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.

22. The method according to claim 21, wherein, The GNSS valid timer is started by the terminal device when sending the first information.

23. The method according to any one of claims 20 to 22, wherein The method further includes: The network device sends the second information, which is used to configure the duration of the GNSS valid timer.

24. The method according to claim 23, wherein, The second information is used to indicate that the GNSS valid timer starts at a specified time point.

25. The method according to claim 24, wherein, The specified time point includes at least one of the following: The second information includes the time point for starting the GNSS valid timer; The effective time point of the second information.

26. The method according to any one of claims 20 to 25, wherein, The method further includes: The network device sends a GNSS measurement command, which is used to stop the GNSS valid timer.

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

28. The terminal device according to claim 27, wherein, The processing unit is further used to perform GNSS measurement during the operation of the timer when starting GNSS measurement and starting the timer.

29. The terminal device according to claim 27 or 28, wherein The processing unit is further used to release the radio resource control (RRC) connection back to the RRC idle state or the terminal device triggers a radio link failure (RLF) process when the timer times out and the terminal device has not completed GNSS measurement.

30. The terminal device according to any one of claims 27 to 29, wherein, The processing unit is further used to stop the timer when the terminal device completes at least one of GNSS measurement, uplink synchronization, and downlink synchronization.

31. The terminal device according to any one of claims 27 to 30, wherein, The terminal device further includes a sending unit, which is used to send a notification message when the terminal device completes at least one of GNSS measurement, uplink synchronization, and downlink synchronization, and the notification message is used to notify the network device that the device has completed at least one of GNSS measurement, uplink synchronization, and downlink synchronization.

32. The terminal device according to claim 27, wherein, The processing unit is further used to wait for a GNSS measurement command during the operation of the timer after starting the timer when the GNSS position is invalid.

33. The terminal device according to claim 32, wherein, The processing unit is further configured to release the RRC connection and return to the RRC idle state or trigger an RLF process by the terminal device when the timer expires and the terminal device does not receive the GNSS measurement command.

34. The terminal device according to any one of claims 27 to 33, wherein, The conditions for the processing unit to start the timer include at least one of the following: The GNSS position is invalid; The terminal device has not received a GNSS measurement command from the network device since completing the most recent GNSS measurement; 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.

35. The terminal device according to any one of claims 27 to 34, wherein, The processing unit is further configured to stop the timer when receiving the GNSS measurement command from the network device.

36. The terminal device according to any one of claims 27 to 35, wherein, The duration of the timer is configured by the network device.

37. The terminal device according to claim 36, wherein, The duration of the timer reuses the duration of the measurement interval.

38. The terminal device according to any one of claims 27 to 37, wherein, The invalid GNSS position includes: the GNSS valid timer expires.

39. A terminal device, comprising: A processing unit, configured to obtain 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.

40. The terminal device according to claim 39, wherein, The terminal device further includes: A sending unit, 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.

41. The terminal device according to claim 40, wherein, The terminal device further includes: The processing unit is further configured to start the GNSS valid timer when the sending unit sends the first information.

42. The terminal device according to any one of claims 39 to 41, wherein, The terminal device further includes: A receiving unit, configured to receive second information for configuring the duration of the GNSS valid timer.

43. The terminal device according to claim 42, wherein, The ways for the processing unit to start the GNSS valid timer include at least one of the following: Start the GNSS valid timer when receiving the second information; Start the GNSS valid timer at a specified time point based on the second information.

44. The terminal device according to claim 43, wherein, The specified time point includes at least one of the following: The time point for starting the GNSS valid timer included in the second information; The effective time point of the second information.

45. The terminal device according to any one of claims 39 to 44, wherein, The processing unit 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.

46. A network device, including: 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.

47. The network device according to claim 46, wherein, The network device further includes: A receiving unit, 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.

48. The network device according to claim 47, wherein, The GNSS valid timer is started by the terminal device when sending the first information.

49. The network device according to any one of claims 46 to 47, wherein, The network device further includes: A first sending unit, configured to send second information for configuring the duration of the GNSS valid timer.

50. The network device according to claim 49, wherein, The second piece of information is used to indicate that the GNSS valid timer starts at a specified time point.

51. The network device according to claim 50, wherein, The specified time point includes at least one of the following: The time point for starting the GNSS valid timer included in the second piece of information; The effective time point of the second piece of information.

52. The network device according to any one of claims 46 to 51, wherein, The network device further includes: A second sending unit, configured to send a GNSS measurement command, where the GNSS measurement command is used to stop the GNSS valid timer.

53. A terminal device, comprising: A processor and a memory, where 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 method according to any one of claims 1 to 12 or 13 to 19.

54. A network device, comprising: A processor and a memory, where 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 method according to any one of claims 20 to 26.

55. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1 to 12 or 13 to 19.

56. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 20 to 26.

57. A computer-readable storage medium, configured to store a computer program, and when the computer program is run by a device, the device executes the method according to any one of claims 1 to 12 or 13 to 19.

58. A computer-readable storage medium, configured to store a computer program, and when the computer program is run by a device, the device executes the method according to any one of claims 20 to 26.

59. A computer program product, including computer program instructions, where the computer program instructions cause a computer to execute the method according to any one of claims 1 to 12 or 13 to 19.

60. A computer program product, including computer program instructions, where the computer program instructions cause a computer to execute the method according to any one of claims 20 to 26.

61. A computer program, where the computer program causes a computer to execute the method according to any one of claims 1 to 12 or 13 to 19.

62. A computer program, where the computer program causes a computer to execute the method according to any one of claims 20 to 26.

Images