Method and device for solving conflict between measurement and communication of terminal equipment

Abstract

The invention provides a method and a device for solving conflicts between measurement and communication of terminal equipment. Specifically, the method describes that under the condition that a first timer is overtime, the terminal device determines whether to start a second timer according to whether the terminal device is in a GNSS measurement period, and the second timer is used for the terminal device to acquire system information within effective time of the second timer. According to the method and the device, the RLF risk caused by the fact that the SIB31 cannot be read in the GNSS measurement period can be effectively reduced.

Description

Conflict resolution and device for measurement and communication of terminal equipment Technical Field

[0001] The present application relates to the field of communications, and in particular to a method and apparatus for resolving conflicts between measurement and communication of a terminal device. Background Art

[0002] Currently, IoT NTN has enhanced the capabilities of IoT terminals, allowing UEs to perform GNSS position fix operations in the RRC connected state. Based on current understanding, IoT terminals need to stop related operations of the communication module during the GNSS position fix operation.

[0003] Therefore, if the UE is performing GNSS measurements at a certain moment and T317 times out, the UE needs to simultaneously start the T318 timer to obtain SIB31. If SIB31 is obtained within the validity period of T318, the UE will enter RLF. Since the UE needs to perform GNSS positioning operations during GNSS measurements, it cannot read SIB31 during GNSS measurements. Obviously, the existing mechanism will shorten the time the UE can actually read SIB31 in this situation, increasing the risk of the UE experiencing RLF.

[0004] In addition, if the UE is in T318 at a certain moment and triggers GNSS measurement, since SIB31 reading and GNSS positioning operations cannot be performed at the same time, the existing mechanism obviously has a problem in which the UE needs to continue reading SIB31 or perform GNSS measurement first, which is an urgent problem to be solved.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a method and apparatus for conflict resolution between measurement and communication of a terminal device, so as to at least resolve the conflict problem existing in the related art between the SIB31 reading process and the GNSS position positioning operation process of the IOT terminal.

[0007] According to one embodiment of the present application, a conflict resolution method for measurement and communication of a terminal device is provided, including: when a first timer times out, the terminal device determines whether to start a second timer based on whether the terminal device is in a global navigation satellite system GNSS measurement period, wherein the second timer is used for the terminal device to obtain system information within the effective time of the second timer.

[0008] According to one embodiment of the present application, a device for resolving conflicts between measurement and communication of a terminal device is provided, including: a first determination module, for determining whether to start a second timer according to whether the terminal device is in a global navigation satellite system GNSS measurement period when a first timer times out, wherein the second timer is used by the terminal device to obtain system information within the effective time of the second timer.

[0009] According to another embodiment of the present application, a conflict resolution method for measurement and communication of a terminal device is provided, including: when the terminal device starts GNSS measurement, when a first timer times out, the terminal device determines the start time of a second timer and / or the duration of the second timer, wherein the second timer is used by the terminal device to obtain system information within the effective time of the second timer.

[0010] According to another embodiment of the present application, a device for resolving conflicts between measurement and communication of a terminal device is provided, which is located in the terminal device and includes: a second determination module for determining the start time and / or the duration of a second timer when a first timer times out when GNSS measurement is started, wherein the second timer is used to obtain system information within the effective time of the second timer.

[0011] This application determines whether to start the second timer for acquiring system information within the valid time based on whether the terminal device is currently in a GNSS measurement period. This effectively mitigates the risk of RLF caused by the inability to read SIB31 during GNSS measurement. Furthermore, during GNSS measurement, the UE determines the start time of T318 rather than directly determining the SIB31 reading time, thereby avoiding conflicts between GNSS measurement and SIB31 reading. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0013] FIG1 is a schematic structural diagram of an NTN network architecture based on transparent forwarding according to an embodiment of the present application;

[0014] FIG2 is a schematic structural diagram of an NTN network architecture based on regeneration and forwarding according to an embodiment of the present application;

[0015] FIG3 is a schematic diagram of time synchronization on an eNB or gNB side according to an embodiment of the present application;

[0016] 4 is a flow chart of a method for resolving conflicts between measurement and communication of a terminal device according to an embodiment of the present invention;

[0017] FIG5 is a structural block diagram of an apparatus for resolving conflicts between measurement and communication of a terminal device according to an embodiment of the present application;

[0018] FIG6 is a timing diagram of the operation of a terminal device based on scenario 1 according to an embodiment of the present application;

[0019] FIG7 is a timing diagram of the operation of a terminal device based on scenario 2 according to an embodiment of the present application;

[0020] 8 is a flow chart of a method for resolving conflicts between measurement and communication of a terminal device according to an embodiment of the present invention;

[0021] FIG9 is a structural block diagram of an apparatus for resolving conflicts between measurement and communication of a terminal device according to an embodiment of the present application;

[0022] FIG10 is a timing diagram of the operation of a terminal device based on scenario 3 according to an embodiment of the present application;

[0023] FIG11 is a timing diagram of the operation of a terminal device based on scenario 4 according to an embodiment of the present application;

[0024] FIG12 is a timing diagram 1 of the start-up and effective time of the T318 timer according to an embodiment of the present application;

[0025] FIG13 is a second timing diagram of the start and effective time of the T318 timer according to an embodiment of the present application;

[0026] FIG14 is a third timing diagram of the start-up and effective time of the T318 timer according to an embodiment of the present application;

[0027] FIG15 is a fourth timing diagram of the start and effective time of the T318 timer according to an embodiment of the present application;

[0028] FIG16 is a fifth timing diagram of the start and effective time of the T318 timer according to an embodiment of the present application;

[0029] FIG17 is a sixth timing diagram of the start-up and effective time of the T318 timer according to an embodiment of the present application;

[0030] FIG18 is a seventh timing diagram of the start and effective time of the T318 timer according to an embodiment of the present application;

[0031] FIG19 is a timing diagram showing the start and effective time of the T318 timer according to an embodiment of the present application;

[0032] FIG20 is a timing diagram 9 of the start and effective time of the T318 timer according to an embodiment of the present application;

[0033] FIG21 is a timing diagram showing the start-up and effective time of the T318 timer according to an embodiment of the present application;

[0034] FIG22 is a schematic structural diagram of a terminal device according to an embodiment of the present application;

[0035] Figure 23 is a structural diagram of another terminal device according to an embodiment of the present application. DETAILED DESCRIPTION

[0036] The present application will be described in detail below with reference to the accompanying drawings and in combination with embodiments. It should be noted that, unless there is a conflict, the embodiments and features in the embodiments of the present application can be combined with each other.

[0037] It should be noted that the terms "first", "second", etc. in the description and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

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

[0039] 3GPP is currently researching Non-Terrestrial Network (NTN) technology. NTN generally uses satellite communications to provide communication services to terrestrial users. Compared to terrestrial cellular networks, satellite communications offer many unique advantages. First, satellite communications are not restricted by user location. For example, conventional terrestrial communications cannot cover areas such as oceans, high mountains, and deserts where communication equipment cannot be deployed 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 poor, underdeveloped 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.

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

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

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

[0043] LEO: Low-orbit satellites have an altitude range of 500 km to 1500 km, with an orbital period of approximately 1.5 to 2 hours. Signal propagation delay for single-hop communication between users is typically less than 20 ms. The maximum satellite visibility time is 20 minutes. Signal propagation distances are short, link loss is minimal, and the transmit power requirements for user terminals are low.

[0044] GEO: Geosynchronous Earth Orbit (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.

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

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

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

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

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

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

[0051] Transparent forwarding: It only provides the functions of wireless frequency filtering, frequency conversion and amplification, and only provides transparent forwarding of signals without changing the waveform signal it forwards.

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

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

[0054] LTE / NR terrestrial network uplink timing advance

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

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

[0057] The uplink and downlink clocks on the eNB / gNB are identical, but there is an offset between the uplink and downlink clocks on the UE side, and different UEs have different uplink timing advances. By appropriately controlling the offset for each UE, the eNB / gNB can control the time it takes for uplink signals from different UEs to arrive at the eNB / gNB. UEs farther from the eNB / gNB experience greater transmission latency and therefore need to send uplink data earlier than UEs closer to the eNB / gNB.

[0058] Figure 3 is a schematic diagram of time synchronization on the eNB or gNB side according to an embodiment of the present application.

[0059] As shown in Figure 3, the eNB / gNB determines the TA 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.

[0060] Acquisition of initial TA: During the random access process, the eNB / gNB determines the TA value by measuring the received preamble and sends it to the UE through the Timing Advance Command field of the RAR.

[0061] Adjustment of TA in RRC Connected State: Although the UE and the eNB / gNB achieve uplink synchronization during random access, the timing of uplink signals reaching the eNB / gNB may vary 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 sends a Timing Advance Command to the UE, requesting it to adjust its uplink timing. This Timing Advance Command is sent to the UE via the Timing Advance Command MAC CE.

[0062] TA maintenance in NTN

[0063] In traditional TN networks, UEs maintain their TA based on TA commands issued by the network. For Rel-17 NTN, assuming UEs have GNSS positioning capabilities and TA pre-compensation capabilities, UEs can estimate the service link TA based on their location and the location of the serving satellite. Therefore, NTN introduces a TA determination method that combines open-loop and closed-loop methods. Based on the conclusions of current standardization meetings, for NTN UEs in RRC_IDLE / INACTIVE and RRC_CONNECTED states, their timing advance (TA) is determined by the following formula:

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

[0065] Among them, N TA The PRACH transmission scenario is defined as 0 and can be updated later through the TA command in Msg2 / MsgB and the TAcommand MAC CE.

[0066] N TA,UE-specific This is the UE's estimated serving link TA, used for TA precompensation. Specifically, the terminal uses its own GNSS position information combined with the satellite ephemeris information broadcast by the serving cell to determine the satellite position, thereby calculating the propagation delay of the serving link from the UE to the satellite.

[0067] N TA,common It is a public TA controlled by the network and contains any timing deviation that the network deems necessary.

[0068] N TA,offset is a fixed offset for calculating TA.

[0069] 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, to calculate the UE's TA, the UE also needs to obtain the common TA (i.e., N_(TA,common)).

[0070] GNSS Operations for R17 IoT NTN

[0071] In R17 IoT NTN (i.e., scenarios where NB-IoT and eMTC are connected to NTN), the GNSS measurement module and communication module of the IoT terminal cannot operate simultaneously (Simultaneous GNSS and NTN NB-IoT / eMTC operation is not assumed). In R17 NTN, the IoT terminal can only perform GNSS measurements to obtain location information in RRC IDLE or RRC INACTIVE, and the GNSS module cannot be started in the RRC connected state. To this end, the UE needs to obtain its own GNSS position through the GNSS module before entering the RRC connected state. The UE can determine the validity period of the GNSS position based on its own situation (such as the UE's mobility status) and report the remaining validity period of the GNSS position to the network when the RRC connection is established / reestablished / restored. For a UE in the RRC connected state, when its GNSS position expires, the UE cannot perform GNSS operations in the RRC connected state and cannot calculate the TA. Therefore, the UE needs to return to the RRC IDLE state.

[0072] R17 IoT NTN ephemeris information / public TA acquisition mechanism

[0073] In NTNs, the ephemeris information and public TA-related parameters of the serving cell satellite are notified to the UE via system broadcast. For IoT NTNs, the ephemeris information of the serving satellite is carried in SIB31. Because ephemeris information and public TA-related parameters require frequent updates, the concept of ephemeris information / public TA validity period is introduced. When the ephemeris information and / or public TA-related parameters previously obtained by the UE expire, the UE needs to reread SIB31. Specifically, the network configures the durations of timers T317 and T318, where T317 is the validity period of the ephemeris information / public TA, and T318 is the maximum time the UE is allowed to reread SIB31 after the ephemeris information / public TA maintained by the UE expires.

[0074] For a UE in RRC connected state, after reading SIB31, the UE starts T317 at the epoch time indicated by the SIB31. During T317, the ephemeris information and public TA maintained by the UE are considered valid. The UE can calculate its own TA according to the TA formula and perform TA compensation.

[0075] When T317 is exceeded, the previously acquired ephemeris information and common TA parameters are expired, and the UE is considered to be out of uplink synchronization. The UE RRC layer needs to notify the MAC layer to stop all UL transmissions, start T318, and re-read SIB31.

[0076] If the UE reads SIB31 again, the UE stops T318 and starts T317 at the epoch time indicated by the SIB31, and notifies the MAC layer to resume uplink transmission.

[0077] If T318 times out, the UE triggers RLF.

[0078] GNSS enhancements for R18 IoT NTN

[0079] In the R18 IoT NTN enhancement, the following research objectives are clearly stated:

[0080] 4.1.1IoT-NTN Performance Enhancements in Rel-18 to address remaining issues from Rel-17

[0081] This work considers Rel-17 IoT-NTN as baseline as well as Rel-17 NR-NTN outcome and the further IoT-NTN performance enhancements objectives are listed below:

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

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

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

[0085] At the 3GPP RAN1#109 meeting, RAN1 discussed GNSS enhancements for IoT terminals connected to NTN and reached the following conclusions:

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

[0087] For connected GNSS measurements, at least the following options can be considered:

[0088] Method 1: The UE reacquires the GNSS position fix based on timer control.

[0089] Method 2: Introduce a new gap, and the UE re-acquires the GNSS position fix during the gap.

[0090] For triggering connected GNSS measurements, consider:

[0091] UE-triggered GNSS measurements.

[0092] Network-triggered GNSS measurements

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

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

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

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

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

[0098] Example 1

[0099] FIG4 is a flow chart of a method for resolving a conflict between measurement and communication of a terminal device according to an embodiment of the present invention. As shown in FIG4 , the process includes the following steps:

[0100] Step 402: When the first timer times out, the terminal device determines whether to start a second timer based on whether the terminal device is in a global navigation satellite system GNSS measurement period or whether it is performing a GNSS position fix operation, wherein the second timer is used for the terminal device to obtain system information within the effective time of the second timer.

[0101] It should be noted that in this application, the terminal device needs to perform a GNSS positioning (position fix) operation during the GNSS measurement.

[0102] The system information described in this application includes at least System Information Block (SIB) 31. Of course, considering the continuity of the technology, any information that can be used to provide ephemeris information of the serving satellite to the terminal device is within the scope of protection of this embodiment. Furthermore, also considering the continuity of the technology, any information that transmits ephemeris information of the serving satellite via broadcast, multicast, or unicast is within the scope of protection of this embodiment.

[0103] The first timer described in this embodiment includes at least the T317 timer. The second timer includes at least the T318 timer. Of course, considering the continuity of technology, any timer that can be used to maintain ephemeris information and public TA validity of the terminal device, as well as any timer that can be used to obtain SIB31, is within the scope of protection of this application, and is not limited to the T317 timer and the T318 timer.

[0104] The terminal device determines whether to start the second timer according to whether the terminal device is in the GNSS measurement period, including: when the first timer times out and the terminal device determines that the terminal device is not in the GNSS measurement period, the terminal device starts the second timer.

[0105] The terminal device determines whether to start the second timer according to whether the terminal device is in the GNSS measurement period, including: when the first timer times out and the terminal device is not in the GNSS measurement period, the terminal device starts the second timer.

[0106] After the terminal device starts the second timer, when the terminal determines that the terminal device triggers GNSS measurement, the method also includes: the terminal device maintains the second timer and obtains system information within the remaining valid time; when the terminal device obtains the system information within the remaining valid time, the terminal device starts GNSS measurement.

[0107] After the terminal device starts the second timer, when the terminal determines that the terminal device triggers GNSS measurement, the method further includes: the terminal device stops the second timer and starts GNSS measurement.

[0108] After the terminal device starts GNSS measurement, the terminal device performs GNSS measurement within the GNSS measurement time.

[0109] The GNSS measurement time includes one of the following: the effective time of the GNSS measurement timer; and the GNSS measurement interval.

[0110] It should be noted that the terminal device performs GNSS measurement within the GNSS measurement time, including: when the GNSS position positioning is completed within the GNSS measurement time, the terminal device completes downlink synchronization with the network device.

[0111] It should be noted that the terminal device performs GNSS measurement within the GNSS measurement time, including: when the GNSS position positioning is not completed within the GNSS measurement time, the terminal device enters the idle state or triggers the radio link failure RLF; the terminal device continues to perform GNSS position positioning.

[0112] It should be noted that after the terminal device stops the second timer and starts GNSS measurement, the method also includes: when the terminal device completes GNSS positioning within the GNSS measurement time, the terminal device restarts the second timer, or, when the terminal device completes GNSS positioning within the GNSS measurement time, the terminal device restores the second timer and obtains system information within the remaining valid time.

[0113] It should be noted that after the terminal device stops the second timer and starts GNSS measurement, the method also includes: after the terminal device completes downlink synchronization, the terminal device restarts the second timer, or, after the terminal device completes downlink synchronization, the terminal device restores the second timer and obtains system information within the remaining valid time.

[0114] It should be noted that, after the terminal device obtains the system information within the valid time of the second timer and the GNSS position of the terminal device is valid, the terminal device resumes uplink synchronization with the network device.

[0115] It should be noted that, when the terminal device fails to obtain system information within the valid time of the second timer, the method further includes: the terminal device triggers RLF.

[0116] It should be noted that the terminal device receives configuration information sent by the network device, wherein the configuration information includes first timer information for running the first timer and second timer information for running the second timer.

[0117] Example 2

[0118] FIG5 is a structural block diagram of an apparatus for resolving conflicts between measurement and communication of a terminal device according to an embodiment of the present application. The apparatus is located in the terminal device. As shown in FIG5 , the apparatus includes:

[0119] The first determination module 52 is used to determine whether to start a second timer according to whether the terminal device is in a global navigation satellite system GNSS measurement period when the first timer times out, wherein the second timer is used for the terminal device to obtain system information within the effective time of the second timer.

[0120] The apparatus further includes: a first starting module, configured to start a second timer when the first timer times out and the terminal device determines that the terminal device is not in a GNSS measurement period.

[0121] When the determination module determines that the terminal device triggers GNSS measurement (for example, the GNSS position of the terminal device is invalid), the device is also used to: maintain a second timer and obtain system information within the remaining valid time; when the system information is obtained within the remaining valid time, start GNSS measurement.

[0122] The apparatus further includes: a first stopping module, configured to stop the second timer and start the GNSS measurement when the determining module determines that the terminal device triggers the GNSS measurement.

[0123] The device further includes: a first measurement module, configured to perform GNSS measurement within a GNSS measurement time after starting the GNSS measurement.

[0124] The GNSS measurement time includes one of the following: the effective time of the GNSS measurement timer; and the GNSS measurement interval.

[0125] The device also includes: a first downlink synchronization module, which is used to complete downlink synchronization with the network device after completing GNSS position positioning within the GNSS measurement time.

[0126] The device also includes: a first trigger module, which is used to enter an idle state or trigger a radio link failure RLF when the GNSS position positioning is not completed within the GNSS measurement time; and a first positioning module, which is used to continue the GNSS position positioning.

[0127] The device also includes: a first restart module, which is used to restart the second timer when the GNSS position positioning is completed within the GNSS measurement time, or a first recovery module, which is used to restore the second timer when the GNSS position positioning is completed within the GNSS measurement time, and obtain system information within the remaining valid time.

[0128] The device also includes: a second restart module, which is used to restart the second timer after completing the downlink synchronization, or a second restart module, which is used to restore the second timer after completing the downlink synchronization and obtain the system information within the remaining valid time.

[0129] The device also includes: a third recovery module, which is used to recover uplink synchronization with the network device after acquiring the system information within the effective time of the second timer.

[0130] The device also includes: a second triggering module, configured to trigger RLF when the system information is not acquired within the valid time of the second timer.

[0131] The apparatus further includes: a first receiving module, configured to receive configuration information sent by the network device, wherein the configuration information includes first timer information for running the first timer and second timer information for running the second timer.

[0132] Specifically, the present application further provides the following scenarios for Example 1 and Example 2 to better understand the solutions described in the above embodiments.

[0133] Scenario 1:

[0134] If the terminal device determines that the T317 timer has expired during the GNSS validity period, the ephemeris information of the serving satellite and the public TA-related parameters maintained by the terminal device have become invalid. The UE needs to start the T318 timer to obtain the ephemeris information of the serving satellite and the public TA-related parameters carried in SIB31.

[0135] FIG6 is a timing diagram of the operation of a terminal device based on scenario 1 according to an embodiment of the present application. As shown in FIG6 , the specific scenario is as follows:

[0136] The terminal device in the connected state receives the configuration information sent by the network device, including the configuration information for the T317 timer and the configuration information for the T318 timer.

[0137] According to the configuration information of the T317 timer, the terminal device runs the T317 timer to maintain the ephemeris information and public TA parameters of the serving satellite. At the same time, the terminal device is maintaining the GNSS position.

[0138] At time T1, the T317 timer times out. Since the previously obtained ephemeris information and public TA parameters have expired, it is determined that uplink desynchronization has occurred. Therefore, the terminal device starts the T318 timer and re-reads SIB31 within the valid time of the T318 timer.

[0139] At time T2, the terminal device triggers GNSS measurement and re-reads SIB31 within the valid time of T318 timer.

[0140] At time T3, the terminal device obtains SIB31, stops the T318 timer, and restarts the T317 timer based on the obtained SIB31 to maintain the ephemeris information and public TA parameters of the service satellite. At the same time, the terminal device starts GNSS measurement.

[0141] The terminal device performs GNSS measurement within the valid time of the GNSS measurement timer or the GNSS measurement interval. When the GNSS position is completed, the terminal device re-maintains the GNSS position and completes downlink synchronization with the network device.

[0142] It should be noted that, in order to reduce the operating burden of the terminal device, the terminal device may not start the GNSS measurement immediately at time T3, but may start the GNSS measurement after a time length t1 after time T3.

[0143] It should be noted that, upon determining that uplink desynchronization occurs in the terminal, the RRC layer of the terminal will notify the MAC layer to stop all uplink transmissions.

[0144] It should be noted that the configuration information of the T317 timer and the configuration information of the T318 timer may be sent through the same signaling or message, or may be sent through different signaling or messages.

[0145] Scenario 2:

[0146] During the GNSS validity period, the terminal device determines that the T317 timer has expired. At this time, the maintained ephemeris information and public TA-related parameters of the serving satellite have become invalid. The UE obtains SIB31 within the valid time after starting the T318 timer. However, at time T2, if the terminal device has not yet obtained SIB31, the terminal device determines that the GNSS position is invalid and needs to perform GNSS measurement again to obtain the GNSS position.

[0147] FIG7 is a timing diagram of the operation of a terminal device based on scenario 2 according to an embodiment of the present application. As shown in FIG7 , the specific scenario is as follows:

[0148] According to the configuration information of the T317 timer, the terminal device runs the T317 timer to maintain the ephemeris information and public TA parameters of the serving satellite. At the same time, the terminal device is maintaining the GNSS position.

[0149] At time T1, the T317 timer times out. Since the previously obtained ephemeris information and public TA parameters have expired, it is determined that uplink desynchronization has occurred. Therefore, the terminal device starts the T318 timer and re-reads SIB31 within the valid time of the T318 timer.

[0150] At time T2, the terminal device triggers GNSS measurement. At this time, the terminal device has not yet obtained SIB31. The terminal device stops the T318 timer and starts GNSS measurement.

[0151] At time T3, the terminal device completes GNSS positioning and re-maintains its GNSS position. At the same time, the terminal device can resume the T318 timer and continue to obtain SIB31 within the remaining validity period of the T318 timer, or the terminal device can restart the T318 timer and obtain SIB31 within the validity period of a complete T318 timer.

[0152] At time T4, the terminal device obtains SIB31, stops the T318 timer, and restarts the T317 timer based on the obtained SIB31, maintaining the ephemeris information and public TA parameters of the service satellite to restore uplink synchronization with the network device. The terminal device then completes downlink synchronization with the network device.

[0153] It should be noted that, in order to reduce the operating burden of the terminal device, the terminal device may not start the T318 timer immediately at time T3, but may start the T318 timer after a time length t2 after time T3.

[0154] It should be noted that, upon determining that uplink desynchronization occurs in the terminal, the RRC layer of the terminal will notify the MAC layer to stop all uplink transmissions.

[0155] It should be noted that the configuration information of the T317 timer and the configuration information of the T318 timer may be sent through the same signaling or message, or may be sent through different signaling or messages.

[0156] Example 3

[0157] FIG8 is a flow chart of a method for resolving a conflict between measurement and communication of a terminal device according to an embodiment of the present invention. As shown in FIG8 , the process includes the following steps:

[0158] Step 802: When the terminal device starts GNSS measurement, when the first timer times out, the terminal device determines the start time of the second timer and / or the duration of the second timer, wherein the second timer is used by the terminal device to obtain system information within the effective time of the second timer.

[0159] The system information described in this application includes at least System Information Block (SIB) 31. Of course, considering the continuity of the technology, any information that can be used to provide ephemeris information of the serving satellite to the terminal device is within the scope of protection of this embodiment. Furthermore, also considering the continuity of the technology, any information that transmits ephemeris information of the serving satellite via broadcast, multicast, or unicast is within the scope of protection of this embodiment.

[0160] The first timer described in this embodiment includes at least the T317 timer. The second timer includes at least the T318 timer. Of course, considering the continuity of technology, any timer that can be used to maintain ephemeris information and public TA validity of the terminal device, as well as any timer that can be used to obtain SIB31, is within the scope of protection of this application, and is not limited to the T317 timer and the T318 timer.

[0161] After the terminal device starts GNSS measurement, the terminal device performs GNSS measurement within the GNSS measurement time.

[0162] The GNSS measurement time includes one of the following: the effective time of the GNSS measurement timer; and the GNSS measurement interval.

[0163] The terminal device performs GNSS measurement within the GNSS measurement time, including: when the GNSS position positioning is completed within the GNSS measurement time, the terminal device completes downlink synchronization with the network device.

[0164] The terminal device performs GNSS measurement within the GNSS measurement time, including: when the GNSS position positioning is not completed within the GNSS measurement time, the terminal device enters the idle state or triggers the radio link failure RLF; the terminal device continues to perform GNSS position positioning.

[0165] The method also includes one of the following: the terminal device starts the second timer when the first timer times out; the terminal device starts the second timer when the GNSS position positioning is completed; the terminal device starts the second timer when the GNSS position positioning is completed and the downlink synchronization is completed; the terminal device starts the second timer after the first timer times out and before the GNSS position positioning; the terminal device starts the second timer after completing the GNSS position positioning and before completing the downlink synchronization; the terminal device starts the second timer after completing the downlink synchronization.

[0166] When the terminal device starts the second timer when the first timer expires, the effective time includes one of the following: a first effective time with the first moment of completing GNSS position positioning as the starting time; a second effective time with the second moment after completing GNSS position positioning and before completing downlink synchronization as the starting time; a third effective time with the third moment of completing downlink synchronization as the starting time; and a fourth effective time with the fourth moment after completing downlink synchronization and before the second timer expires as the starting time.

[0167] When the terminal device starts the second timer when completing GNSS position positioning, the valid time includes one of the following: a first valid time with the first moment of completing GNSS position positioning as the starting time; a second valid time with the second moment after completing GNSS position positioning and before completing downlink synchronization as the starting time; a third valid time with the third moment of completing downlink synchronization as the starting time; and a fourth valid time with the fourth moment after completing downlink synchronization and before the second timer expires as the starting time.

[0168] When the terminal device starts the second timer when completing downlink synchronization, the valid time includes one of the following: a third valid time with the third moment of completing downlink synchronization as the starting time; a fourth valid time with the fourth moment after completing downlink synchronization and before the second timer expires as the starting time.

[0169] When the terminal device starts the second timer after the first timer expires and before the GNSS position positioning, the effective time includes one of the following: a first effective time with the first moment of completing the GNSS position positioning as the starting time; a second effective time with the second moment after completing the GNSS position positioning and before completing the downlink synchronization as the starting time; a third effective time with the third moment of completing the downlink synchronization as the starting time; and a fourth effective time with the fourth moment after completing the downlink synchronization and before the second timer expires as the starting time.

[0170] In the case where the terminal device starts the second timer after completing GNSS position positioning and before completing downlink synchronization, the valid time includes one of the following: a second valid time with the second moment after completing GNSS position positioning and before completing downlink synchronization as the starting time; a third valid time with the third moment after completing downlink synchronization as the starting time; a fourth valid time with the fourth moment after completing downlink synchronization and before the second timer expires as the starting time.

[0171] When the terminal device starts the second timer after completing downlink synchronization, the valid time includes one of the following: a fourth valid time with a fourth moment after completing downlink synchronization and before the second timer expires as the starting time.

[0172] After the terminal device starts the second timer, when the terminal determines that the terminal device triggers GNSS measurement, the method also includes: the terminal device maintains the second timer and obtains system information within the remaining valid time; when the terminal device obtains the system information within the remaining valid time, the terminal device starts GNSS measurement.

[0173] After the terminal device starts the second timer, when the terminal determines that the terminal device triggers GNSS measurement, the method further includes: the terminal device stops the second timer and starts GNSS measurement.

[0174] When the terminal device obtains the system information within the valid time of the second timer and the condition that the UE's GNSS position is valid is met, the terminal device resumes uplink synchronization with the network device.

[0175] When the terminal device fails to obtain the system information within the valid time of the second timer, the method further includes: the terminal device triggers RLF.

[0176] The method further includes: the terminal device receives configuration information sent by the network device, wherein the configuration information includes first timer information for running the first timer and second timer information for running the second timer.

[0177] The terminal determines the length of the second timer according to the configuration information and the remaining time during GNSS measurement, or the terminal determines the length of the second timer according to the configuration information, the remaining time during GNSS measurement and the downlink synchronization time.

[0178] FIG9 is a structural block diagram of an apparatus for resolving conflicts between measurement and communication of a terminal device according to an embodiment of the present application. The apparatus is located in the terminal device. As shown in FIG9 , the apparatus includes:

[0179] The second determination module 92 is configured to determine the start time and / or duration of a second timer when the first timer times out in the case of starting GNSS measurement, wherein the second timer is configured to obtain system information within the effective time of the second timer.

[0180] The device further includes: a second measurement module, configured to perform GNSS measurement within a GNSS measurement time after starting the GNSS measurement.

[0181] The GNSS measurement time includes one of the following: the effective time of the GNSS measurement timer; and the GNSS measurement interval.

[0182] The device also includes: a second downlink synchronization module, which is used to complete downlink synchronization with the network device when the GNSS position positioning is completed within the GNSS measurement time.

[0183] The device also includes: a third trigger module, which is used to enter an idle state or trigger a radio link failure RLF when the GNSS position positioning is not completed within the GNSS measurement time; and a second positioning module, which is used to continue the GNSS position positioning.

[0184] The device also includes: a second starting module, which is used to perform one of the following operations: starting the second timer when the first timer times out; starting the second timer when the GNSS position positioning is completed; starting the second timer when the GNSS position positioning is completed and the downlink synchronization is completed; starting the second timer after the first timer times out and before the GNSS position positioning is completed; starting the second timer after the GNSS position positioning is completed and before the downlink synchronization is completed; starting the second timer after the downlink synchronization is completed.

[0185] The device also includes: an acquisition module, which is used to acquire system information within a valid time.

[0186] When the second timer is started when the first timer times out, the valid time includes one of the following: a first valid time with the first moment of completing GNSS position positioning as the starting time; a second valid time with the second moment after completing GNSS position positioning and before completing downlink synchronization as the starting time; a third valid time with the third moment of completing downlink synchronization as the starting time; a fourth valid time with the fourth moment after completing downlink synchronization and before the second timer times out as the starting time.

[0187] When the second timer is started when the GNSS position positioning is completed, the valid time includes one of the following: a first valid time with the first moment of completing the GNSS position positioning as the starting time; a second valid time with the second moment after completing the GNSS position positioning and before completing the downlink synchronization as the starting time; a third valid time with the third moment of completing the downlink synchronization as the starting time; and a fourth valid time with the fourth moment after completing the downlink synchronization and before the second timer expires as the starting time.

[0188] When the second timer is started when the downlink synchronization is completed, the valid time includes one of the following: a third valid time with the third moment of completion of the downlink synchronization as the starting time; a fourth valid time with the fourth moment after the downlink synchronization is completed and before the second timer expires as the starting time.

[0189] When the second timer is started after the first timer expires and before GNSS position positioning, the valid time includes one of the following: a first valid time with the first moment of completing GNSS position positioning as the starting time; a second valid time with the second moment after completing GNSS position positioning and before completing downlink synchronization as the starting time; a third valid time with the third moment of completing downlink synchronization as the starting time; and a fourth valid time with the fourth moment after completing downlink synchronization and before the second timer expires as the starting time.

[0190] In the case where the second timer is started after the GNSS position positioning is completed and before the downlink synchronization is completed, the valid time includes one of the following: a second valid time with the second moment after the GNSS position positioning is completed and before the downlink synchronization is completed as the starting time; a third valid time with the third moment after the downlink synchronization is completed as the starting time; a fourth valid time with the fourth moment after the downlink synchronization is completed and before the second timer times out as the starting time.

[0191] In the case where the second timer is started after the downlink synchronization is completed, the valid time includes one of the following: a fourth valid time starting at a fourth moment after the downlink synchronization is completed and before the second timer expires.

[0192] The device also includes: a maintenance module, which is used to maintain the second timer and obtain system information within the remaining valid time when it is determined that the GNSS measurement is triggered after the second timer is started (for example, the GNSS position is invalid); a third restart module, which is used to restart the GNSS measurement when the terminal device obtains the system information within the remaining valid time.

[0193] The apparatus further includes: a second stopping module, configured to stop the second timer and restart the GNSS measurement when it is determined that the GNSS measurement is triggered (for example, the GNSS position is invalid) after the second timer is started.

[0194] The apparatus further includes: a third recovery module, configured to recover uplink synchronization with the network device after acquiring the system information within the valid time of the second timer and when the GNSS position of the terminal is valid.

[0195] The device also includes: a fourth triggering module, configured to trigger RLF when the system information is not acquired within the valid time of the second timer.

[0196] The apparatus further includes: a second receiving module, configured to receive configuration information sent by the network device, wherein the configuration information includes first timer information for running the first timer and second timer information for running the second timer.

[0197] The device is also used to determine the length of the second timer based on the configuration information and the remaining time during GNSS measurement, or to determine the length of the second timer based on the configuration information, the remaining time during GNSS measurement and the downlink synchronization time.

[0198] Scenario 3:

[0199] When the terminal device starts the GNSS positioning function and the GNSS is valid, it is determined that the T317 timer has timed out. The UE needs to start the T318 timer to obtain SIB31 within the valid time.

[0200] FIG10 is a timing diagram of the operation of a terminal device based on scenario 3 according to an embodiment of the present application. As shown in FIG10 , the specific scenario is as follows:

[0201] The terminal device in the connected state receives the configuration information sent by the network device, including the configuration information for the T317 timer and the configuration information for the T318 timer.

[0202] According to the configuration information of the T317 timer, the terminal device runs the T317 timer to maintain the ephemeris information and public TA parameters of the serving satellite. At the same time, the terminal device is maintaining the GNSS position.

[0203] At time T1, the T317 timer times out, and the previously acquired ephemeris information and public TA parameters have expired.

[0204] At time T2, the terminal device triggers a GNSS measurement (for example, because the GNSS position maintained by the terminal device has expired). The terminal device performs GNSS measurement within the valid time of the GNSS measurement timer or the GNSS measurement interval. When the GNSS position positioning is completed, the terminal device re-maintains the GNSS position.

[0205] At time T3, the terminal device starts the T318 timer and re-reads SIB31 within the valid time of the T318 timer.

[0206] At time T4, the terminal device obtains SIB31, stops the T318 timer, and restarts the T317 timer based on the obtained SIB31, maintaining the ephemeris information and public TA parameters of the service satellite to restore uplink synchronization with the network device. Then, downlink synchronization with the network device is completed.

[0207] It should be noted that, upon determining that uplink desynchronization occurs in the terminal, the RRC layer of the terminal will notify the MAC layer to stop all uplink transmissions.

[0208] It should be noted that the configuration information of the T317 timer and the configuration information of the T318 timer may be sent through the same signaling or message, or may be sent through different signaling or messages.

[0209] Scenario 4:

[0210] When the terminal device starts the GNSS positioning function, after starting the GNSS measurement, it is determined that the T317 timer has timed out. The UE needs to start the T318 timer to obtain SIB31 within the valid time.

[0211] FIG11 is a timing diagram of the operation of a terminal device based on scenario 4 according to an embodiment of the present application. As shown in FIG11 , the specific scenarios are as follows:

[0212] The terminal device in the connected state receives the configuration information sent by the network device, including the configuration information for the T317 timer and the configuration information for the T318 timer.

[0213] According to the configuration information of the T317 timer, the terminal device runs the T317 timer to maintain the ephemeris information and public TA parameters of the serving satellite. At the same time, the terminal device is maintaining the GNSS position.

[0214] At time T1, the terminal device triggers GNSS measurement, for example, when the GNSS position maintained by the terminal device expires. The terminal device performs GNSS measurement within the valid time of the GNSS measurement timer or the GNSS measurement interval.

[0215] At time T2, the T317 timer times out, and the previously acquired ephemeris information and public TA parameters have expired.

[0216] At time T3, when the terminal device completes GNSS positioning, it re-maintains the GNSS position and starts the T318 timer, and re-reads SIB31 within the valid time of the T318 timer.

[0217] At time T4, the terminal device obtains SIB31, stops the T318 timer, and restarts the T317 timer based on the obtained SIB31, maintaining the ephemeris information and public TA parameters of the service satellite to restore uplink synchronization with the network device. Then, downlink synchronization with the network device is completed.

[0218] It should be noted that, upon determining that uplink desynchronization occurs in the terminal, the RRC layer of the terminal will notify the MAC layer to stop all uplink transmissions.

[0219] It should be noted that the configuration information of the T317 timer and the configuration information of the T318 timer may be sent through the same signaling or message, or may be sent through different signaling or messages.

[0220] Scenario 5:

[0221] Scenario 5 flexibly adjusts the start time and validity period of T318 in scenarios 3 and 4. In scenario 5, when the T317 timer expires, the terminal device starts or is performing GNSS measurement.

[0222] 12 to 15 are timing diagrams of the start-up and effective time of the T318 timer according to different embodiments of the present application.

[0223] In Figure 12, the start position of the T318 timer is the same as the timeout position of the T317 timer. At the same time, the terminal device can start acquiring SIB31 within the T318 timer validity period 1 after the GNSS position is completed, or it can start acquiring SIB31 within the T318 timer validity period 2 after the GNSS position is completed.

[0224] In Figure 12, the duration of the T318 timer is determined by the sum of the GNSS measurement time from the time when the T317 timer times out to the time when the GNSS position positioning is completed and the configured T318 timer duration (the duration between the time when the GNSS position positioning is completed and the time when T318 times out).

[0225] In Figure 13, the T318 timer is started after the T317 timer expires, during the GNSS measurement. The terminal device can also start acquiring SIB31 after the GNSS position fix is ​​completed and within the T318 timer validity period 1. Alternatively, the terminal device can start acquiring SIB31 after the GNSS position fix is ​​completed and within the T318 timer validity period 2.

[0226] In Figure 13, the duration of the T318 timer is determined by the sum of the GNSS measurement time from the time the T318 timer times out to the time the GNSS position is completed and the configured T318 timer duration (the duration between the time the GNSS position is completed and the time T318 times out). In Figure 14, the start position of the T318 timer is after the T317 timer times out. At the same time as the GNSS measurement and positioning is completed, the terminal device can start when the GNSS position is completed and obtain SIB31 within the T318 timer valid time 1. It can also start after the GNSS position is completed and obtain SIB31 within the T318 timer valid time 2.

[0227] In FIG. 14 , the configured T318 timer duration is determined according to the configured T318 timer duration.

[0228] In Figure 15, the T318 timer is started after the T317 timer expires. When the GNSS measurement and positioning is completed, the terminal device can start when the GNSS positioning is completed and obtain SIB31 within the T318 timer valid time 1. It can also start after the GNSS positioning is completed and obtain SIB31 within the T318 timer valid time 2.

[0229] In FIG15 , the T318 timer duration is determined based on the configured T318 timer duration (the duration between the moment when GNSS positioning is completed and the moment when T318 times out) and the difference between the GNSS effective time from the completion of GNSS positioning to the start of the T318 timer.

[0230] 16 to 21 are timing diagrams of the start-up and effective time of the T318 timer according to different embodiments of the present application.

[0231] In Figure 16, the T317 timer times out during GNSS measurement, and the T318 timer starts when the T317 timer times out. The terminal device can start acquiring SIB31 within T318 timer validity period 1 after GNSS positioning is completed. Alternatively, the terminal device can start acquiring SIB31 within T318 timer validity period 2 after GNSS positioning is completed.

[0232] In Figure 16, the duration of the T318 timer is determined by the sum of the effective time from the time when the T317 timer times out to the time when the GNSS measurement is started, the GNSS measurement time from the time when the T317 timer times out to the time when the GNSS position positioning is completed, and the configured T318 timer duration (the duration between the time when the GNSS position positioning is completed and the time when T318 times out).

[0233] In Figure 17, the T317 timer times out while maintaining the GNSS position. The T318 timer starts after the T317 timer times out during the GNSS measurement. The terminal device can start acquiring SIB31 within the T318 timer validity period 1 after the GNSS position is completed. Alternatively, the terminal device can start acquiring SIB31 within the T318 timer validity period 2 after the GNSS position is completed.

[0234] Figure 17 is similar to Figure 16. The duration of the T318 timer is determined by the sum of the effective duration from the time when the T317 timer times out to the time when the GNSS measurement is started, the GNSS measurement time from the time when the T317 timer times out to the time when the GNSS position positioning is completed, and the configured T318 timer duration (the duration between the time when the GNSS position positioning is completed and the time when T318 times out).

[0235] In Figure 18, the T317 timer times out during a GNSS measurement, and the T318 timer starts when the GNSS measurement is initiated. The terminal device can obtain SIB31 within T318 timer validity period 1, starting when GNSS positioning is completed. Alternatively, the terminal device can obtain SIB31 within T318 timer validity period 2, starting after GNSS positioning is completed.

[0236] In Figure 18, the duration of the T318 timer is the sum of the GNSS measurement time from the start time of the T318 timer to the completion of the GNSS position positioning and the configured T318 timer duration (the duration between the time when the GNSS position positioning is completed and the time when T318 times out).

[0237] In Figure 19, the T317 timer times out during a GNSS measurement, and the T318 timer starts when the GNSS measurement is initiated. The terminal device can obtain SIB31 within T318 timer validity period 1, starting when GNSS positioning is completed. Alternatively, the terminal device can obtain SIB31 within T318 timer validity period 2, starting after GNSS positioning is completed.

[0238] Figure 19 is similar to Figure 17. In Figure 19, the duration of the T318 timer is the sum of the GNSS measurement time from the start time of the T318 timer to the completion of the GNSS position positioning and the configured T318 timer duration (the duration from the time when the GNSS position positioning is completed to the time when T318 times out). In Figure 20, the T317 timer times out during the GNSS measurement, and the T318 timer starts when the GNSS position positioning is completed. The terminal device can start when the GNSS position positioning is completed and obtain SIB31 within the effective time 1 of the T318 timer. It can also start after the GNSS position positioning is completed and obtain SIB31 within the effective time 2 of the T318 timer.

[0239] Similar to Figure 14, in Figure 14, the configured T318 timer duration is determined based on the configured T318 timer duration. In Figure 21, the T317 timer times out during GNSS measurement, and the T318 timer is started after the GNSS position fix is ​​completed. The terminal device can start acquiring SIB31 when the T318 timer is started and within the T318 timer validity period 1. Alternatively, the terminal device can start acquiring SIB31 after the T318 timer is started and within the T318 timer validity period 2.

[0240] Similar to Figure 15, in Figure 21, the T318 timer duration is determined based on the configured T318 timer duration (the duration is the time between the moment when GNSS positioning is completed and the moment when T318 times out) and the difference between the GNSS valid time from the completion of GNSS positioning to the start of the T318 timer.

[0241] It should be noted that, although not shown in the figure, in the embodiment of this solution, based on Figures 12-14, 16-20, on the basis of the T318 timer duration, the downlink synchronization time after the GNSS measurement is increased. Figure 22 is a structural diagram of a terminal device according to an embodiment of the present application. As shown in Figure 21, the terminal device can be used to execute the above-mentioned paging method based on enhanced discontinuous reception on the terminal device side. Specifically: The terminal device 220 may include: a processor 2201, a receiver 2202, a transmitter 2203, a memory 2204 and a bus 2205.

[0242] The processor 2201 includes one or more processing cores. The processor 2201 executes various functional applications and information processing by running software programs and modules.

[0243] The receiver 2202 and the transmitter 2203 may be implemented as a transceiver 2206 , which may be a communication chip.

[0244] The memory 2204 is connected to the processor 2201 via a bus 2205 .

[0245] The memory 2204 may be used to store a computer program, and the processor 2204 may be used to execute the computer program to implement the various steps performed by the terminal device in the above method embodiment.

[0246] Furthermore, the memory 2204 may be implemented by any type of volatile or non-volatile memory device or a combination thereof, including but not limited to: RAM (Random-Access Memory) and ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other solid-state storage technology, CD-ROM (Compact Disc Read-Only Memory), DVD (Digital Video Disc) or other optical storage, tape cassettes, magnetic tape, disk storage or other magnetic storage devices. Among them:

[0247] Processor 2201, configured to:

[0248] When the first timer times out, it is determined whether to start a second timer based on the validity of the global navigation satellite system GNSS position of the terminal device, wherein the second timer is used to obtain system information within the validity time of the second timer.

[0249] FIG23 is a schematic diagram of the structure of another terminal device according to an embodiment of the present application. As shown in FIG23 , the terminal device can be used to perform the above-mentioned terminal device-side paging method based on enhanced discontinuous reception. Specifically, the terminal device 230 may include: a processor 2301, a receiver 2302, a transmitter 2303, a memory 2304, and a bus 2305.

[0250] The processor 2301 includes one or more processing cores. The processor 2301 executes various functional applications and information processing by running software programs and modules.

[0251] The receiver 2302 and the transmitter 2303 may be implemented as a transceiver 2306 , which may be a communication chip.

[0252] The memory 2304 is connected to the processor 2301 via a bus 2305 .

[0253] The memory 2304 may be used to store a computer program, and the processor 2304 may be used to execute the computer program to implement the various steps performed by the terminal device in the above method embodiment.

[0254] Furthermore, the memory 2304 may be implemented by any type of volatile or non-volatile memory device or a combination thereof, including but not limited to: RAM (Random-Access Memory) and ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other solid-state storage technology, CD-ROM (Compact Disc Read-Only Memory), DVD (Digital Video Disc) or other optical storage, tape cassettes, magnetic tape, disk storage or other magnetic storage devices. Among them:

[0255] Processor 2301 is configured to:

[0256] In the case where the terminal device starts GNSS measurement, when the first timer times out, the start time of the second timer is determined, wherein the second timer is used by the terminal device to obtain system information within the valid time of the second timer.

[0257] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0258] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, 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), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as 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 bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

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

[0260] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0261] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0262] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0263] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0264] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0265] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0266] The embodiment of the present application also provides a computer program.

[0267] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here.

[0268] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0269] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

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

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

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

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

[0274] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0275] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in 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 method for resolving conflicts between measurement and communication of a terminal device, the method comprising: When a first timer expires, the terminal device determines whether to start a second timer according to whether the terminal device is in a Global Navigation Satellite System (GNSS) measurement period, where the second timer is used for the terminal device to obtain system information within the effective time of the second timer.

2. The method according to claim 1, wherein the terminal device determines whether to start the second timer according to whether the terminal is in the GNSS measurement period, comprising: When the first timer expires and the terminal device is not in the GNSS measurement period, the terminal device starts the second timer.

3. The method according to claim 2, after the terminal device starts the second timer, when the terminal determines to trigger GNSS measurement, the method further comprises: The terminal device maintains the second timer and obtains the system information within the remaining effective time; When the terminal device obtains the system information within the remaining effective time, the terminal device starts the GNSS measurement.

4. The method according to claim 2, after the terminal device starts the second timer, when the terminal determines to trigger GNSS measurement, the method further comprises: The terminal device stops the second timer and starts the GNSS measurement.

5. The method according to claim 3 or 4, after the terminal device starts the GNSS measurement, the terminal device performs the GNSS measurement within the GNSS measurement time.

6. The method according to claim 5, the GNSS measurement time includes one of the following: The effective time of the GNSS measurement timer; The GNSS measurement interval.

7. The method according to claim 5 or 6, the terminal device performs the GNSS measurement within the GNSS measurement time, comprising: When the GNSS position positioning is completed within the GNSS measurement time, the terminal device completes the downlink synchronization with the network device.

8. The method according to claim 5 or 6, the terminal device performs the GNSS measurement within the GNSS measurement time, comprising: When the GNSS position positioning is not completed within the GNSS measurement time, the terminal device enters the idle state or triggers a Radio Link Failure (RLF); The terminal device continues to perform the GNSS position positioning.

9. The method according to any one of claims 4 to 8, after the terminal device stops the second timer and starts the GNSS measurement, the method further comprises: When the terminal device completes the GNSS position positioning within the GNSS measurement time, the terminal device restarts the second timer, or, When the terminal device completes the GNSS position positioning within the GNSS measurement time, the terminal device resumes the second timer and obtains the system information within the remaining effective time.

10. The method according to claim 7, after the terminal device stops the second timer and starts the GNSS measurement, the method further comprises: After the terminal device completes the downlink synchronization, the terminal device restarts the second timer, or, After the terminal device completes the downlink synchronization, the terminal device resumes the second timer and obtains the system information within the remaining valid time.

11. The method according to any one of claims 1 to 10, when the terminal device obtains the system information within the valid time of the second timer and the GNSS position of the terminal is valid, the terminal device resumes the uplink synchronization with the network device.

12. The method according to any one of claims 1 to 10, when the terminal device fails to obtain the system information within the valid time of the second timer, the method further includes: The terminal device triggers an RLF.

13. The method according to any one of claims 1 to 12, the method further includes: The terminal device receives configuration information sent by the network device, where the configuration information includes first timer information for running the first timer and second timer information for running the second timer.

14. According to the method according to any one of claims 1 to 13, the first timer includes: T317 timer; The second timer includes: T318 timer.

15. The method according to any one of claims 1 to 13, wherein the system information at least includes: System Information Block SIB31.

16. A method for resolving conflicts between measurement and communication of a terminal device, the method includes: When the terminal device starts GNSS measurement, when the first timer expires, the terminal device determines the start time and / or duration of the second timer, where the second timer is used for the terminal device to obtain system information within the valid time of the second timer.

17. The method according to claim 1, after the terminal device starts the GNSS measurement, the terminal device performs GNSS measurement during the GNSS measurement time.

18. The method according to claim 17, the GNSS measurement time includes one of the following: The valid time of the GNSS measurement timer; The GNSS measurement interval.

19. The method according to claim 17 or 18, the terminal device performs GNSS measurement during the GNSS measurement time, including: When the GNSS position is located within the GNSS measurement time, the terminal device completes the downlink synchronization with the network device.

20. The method according to claim 17 or 18, the terminal device performs GNSS measurement during the GNSS measurement time, including: When the GNSS position is not located within the GNSS measurement time, the terminal device enters the idle state or triggers a Radio Link Failure (RLF); The terminal device continues to perform GNSS position location.

21. The method according to claim 19, the method further includes one of the following: The terminal device starts the second timer when the first timer expires; The terminal device starts the second timer when the GNSS position is located; The terminal device starts the second timer when the GNSS position is located and the downlink synchronization is completed; The terminal device starts the second timer after the first timer times out and before completing GNSS position positioning; The terminal device starts the second timer before starting when it has completed GNSS position positioning and completed downlink synchronization; The terminal device starts the second timer after completing downlink synchronization.

22. According to the method described in claim 19 or 20, when the terminal device starts the second timer when the first timer times out, the valid time includes one of the following: The first valid time starting from the first moment when GNSS position positioning is completed; The second valid time starting from the second moment after completing GNSS position positioning and before completing downlink synchronization; The third valid time starting from the third moment when downlink synchronization is completed; The fourth valid time starting from the fourth moment after completing downlink synchronization and before the second timer times out.

23. According to the method described in claim 19 or 20, when the terminal device starts the second timer when it has completed GNSS position positioning, the valid time includes one of the following: The first valid time starting from the first moment when GNSS position positioning is completed; The second valid time starting from the second moment after completing GNSS position positioning and before completing downlink synchronization; The third valid time starting from the third moment when downlink synchronization is completed; The fourth valid time starting from the fourth moment after completing downlink synchronization and before the second timer times out.

24. According to the method described in claim 19 or 20, when the terminal device starts the second timer when it has completed downlink synchronization, the valid time includes one of the following: The third valid time starting from the third moment when downlink synchronization is completed; The fourth valid time starting from the fourth moment after completing downlink synchronization and before the second timer times out.

25. According to the method described in claim 19 or 20, when the terminal device starts the second timer after the first timer times out and before GNSS position positioning, the valid time includes one of the following: The first valid time starting from the first moment when GNSS position positioning is completed; The second valid time starting from the second moment after completing GNSS position positioning and before completing downlink synchronization; The third valid time starting from the third moment when downlink synchronization is completed; The fourth valid time starting from the fourth moment after completing downlink synchronization and before the second timer times out.

26. According to the method described in claim 19 or 20, when the terminal device starts the second timer before starting when it has completed GNSS position positioning and completed downlink synchronization, the valid time includes one of the following: The second valid time starting from the second moment after completing GNSS position positioning and before completing downlink synchronization; The third valid time starting from the third moment when downlink synchronization is completed; A fourth valid time starting at a fourth moment after downlink synchronization is completed and before the second timer expires.

27. The method according to claim 19 or 20, where, when the terminal device starts the second timer after completing downlink synchronization, the valid time includes one of the following: A fourth valid time starting at a fourth moment after downlink synchronization is completed and before the second timer expires.

28. The method according to any one of claims 21 to 27, after the terminal device starts the second timer and the terminal determines to trigger GNSS measurement, the method further includes: The terminal device maintains the second timer and obtains the system information within the remaining valid time; When the terminal device obtains the system information within the remaining valid time, the terminal device starts the GNSS measurement.

29. The method according to any one of claims 21 to 27, after the terminal device starts the second timer and the terminal determines to trigger GNSS measurement, the method further includes: The terminal device stops the second timer and starts the GNSS measurement.

30. The method according to any one of claims 21 to 29, when the terminal device obtains the system information within the valid time of the second timer and meets the condition that the GNSS position of the terminal is valid, the terminal device resumes uplink synchronization with the network device.

31. The method according to any one of claims 21 to 29, when the terminal device does not obtain the system information within the valid time of the second timer, the method further includes: The terminal device triggers RLF.

32. The method according to any one of claims 21 to 31, the method further includes: The terminal device receives configuration information sent by the network device, where the configuration information includes first timer information for the operation of the first timer and second timer information for the operation of the second timer.

33. The method according to claim 32, The terminal determines the duration of the second timer according to the configuration information and the remaining time during GNSS measurement, or, The terminal determines the duration of the second timer according to the configuration information, the remaining time during GNSS measurement, and the downlink synchronization time.

34. The method according to any one of claims 21 to 31, wherein the first timer comprises: T317 timer; The second timer includes: T318 timer.

35. The method according to any one of claims 21 to 31, wherein the system information at least includes: System Information Block SIB31.

36. A device for resolving conflicts between measurement and communication of a terminal device, located in the terminal device, the device includes: A first determination module, configured to determine whether to start a second timer according to whether the terminal device is in a Global Navigation Satellite System (GNSS) measurement period when a first timer expires, where the second timer is used for the terminal device to obtain system information within the valid time of the second timer.

37. The device according to claim 36, the device further includes: The first startup module is used to start a second timer when the first timer times out and the terminal device determines that the terminal device is not in the GNSS measurement period.

38. The apparatus according to claim 37, when the determination module determines that the terminal device triggers GNSS measurement, the apparatus is further used for: Maintaining the second timer and acquiring the system information within the remaining valid time; When the system information is acquired within the remaining valid time, starting the GNSS measurement.

39. The apparatus according to claim 37, the apparatus further includes: The first stop module is used to stop the second timer and start the GNSS measurement when the determination module determines that the terminal device triggers GNSS measurement.

40. The apparatus according to claim 38 or 39, the apparatus further includes: The first measurement module is used to perform the GNSS measurement within the GNSS measurement time after starting the GNSS measurement.

41. The apparatus according to claim 40, the GNSS measurement time includes one of the following: The valid time of the GNSS measurement timer; The GNSS measurement interval.

42. The apparatus according to claim 40 or 41, the apparatus further includes: The first downlink synchronization module is used to complete the downlink synchronization with the network device when the GNSS position positioning is completed within the GNSS measurement time.

43. The apparatus according to claim 40 or 41, the apparatus further includes: The first trigger module is used to enter the idle state or trigger a radio link failure (RLF) when the GNSS position positioning is not completed within the GNSS measurement time; The first positioning module is used to continue the GNSS position positioning.

44. The apparatus according to any one of claims 39 to 43, the apparatus further includes: The first restart module is used to restart the second timer when the GNSS position positioning is completed within the GNSS measurement time, or The first recovery module is used to recover the second timer and acquire the system information within the remaining valid time when the GNSS position positioning is completed within the GNSS measurement time.

45. The apparatus according to claim 42, the apparatus further includes: The second restart module is used to restart the second timer after completing the downlink synchronization, or The second restart module is used to recover the second timer and acquire the system information within the remaining valid time after completing the downlink synchronization.

46. The apparatus according to any one of claims 36 to 45, the apparatus further includes: The second recovery module is used to recover the uplink synchronization with the network device after acquiring the system information within the valid time of the second timer.

47. The apparatus according to any one of claims 36 to 45, the apparatus further includes: The second trigger module is used to trigger an RLF when the system information is not acquired within the valid time of the second timer.

48. The apparatus according to any one of claims 36 to 47, the apparatus further includes: A first receiving module, configured to receive configuration information sent by a network device, where the configuration information includes first timer information for running a first timer and second timer information for running a second timer.

49. The apparatus according to any one of claims 36 to 48, wherein the first timer comprises: Timer T317; The second timer includes: Timer T318.

50. The apparatus according to any one of claims 36 to 48, wherein the system information at least includes: System Information Block SIB31.

51. A device for resolving conflicts between measurement and communication of a terminal device, located in the terminal device, the device includes: A second determining module, configured to, when starting GNSS measurement and when a first timer expires, determine a start time and / or a duration of a second timer, where the second timer is used to obtain system information within a valid time of the second timer.

52. The device according to claim 51, the device further includes: A second measurement module, configured to perform the GNSS measurement within a GNSS measurement time after starting the GNSS measurement.

53. The device according to claim 52, the GNSS measurement time includes one of the following: The valid time of a GNSS measurement timer; A GNSS measurement interval.

54. The device according to claim 52 or 53, the device further includes: A second downlink synchronization module, configured to complete downlink synchronization with the network device when completing GNSS position positioning within the GNSS measurement time.

55. The device according to claim 52 or 53, the device further includes: A third triggering module, configured to enter an idle state or trigger a Radio Link Failure (RLF) when GNSS position positioning is not completed within the GNSS measurement time; A second positioning module, configured to continue performing GNSS position positioning.

56. The device according to claim 53, wherein the device further comprises: A second starting module, configured to perform one of the following operations: Start the second timer when the first timer expires; Start the second timer when completing GNSS position positioning; Start the second timer when completing GNSS position positioning and completing downlink synchronization; Start the second timer after the first timer expires and before GNSS position positioning; Start the second timer before starting after completing GNSS position positioning and completing downlink synchronization; Start the second timer after completing downlink synchronization.

57. The device according to claim 53, the device further includes: An obtaining module, configured to obtain the system information within a valid time.

58. The device according to claim 56, in the case of starting the second timer when the first timer expires, the valid time includes one of the following: A first valid time starting from a first moment when completing GNSS position positioning; A second valid time starting from a second moment after completing GNSS position positioning and before completing downlink synchronization; A third valid time starting from a third moment when completing downlink synchronization; A fourth valid time starting from a fourth moment after completing downlink synchronization and before the second timer expires.

59. The apparatus according to claim 56, when starting the second timer upon completion of GNSS position positioning, the effective time includes one of the following: A first effective time starting from the first moment when GNSS position positioning is completed; A second effective time starting from the second moment after completion of GNSS position positioning and before completion of downlink synchronization; A third effective time starting from the third moment when downlink synchronization is completed; A fourth effective time starting from the fourth moment after completion of downlink synchronization and before the second timer times out.

60. The apparatus according to claim 56, when starting the second timer upon completion of downlink synchronization, the effective time includes one of the following: A third effective time starting from the third moment when downlink synchronization is completed; A fourth effective time starting from the fourth moment after completion of downlink synchronization and before the second timer times out.

61. The apparatus according to claim 56, when starting the second timer after the first timer times out and before GNSS position positioning, the effective time includes one of the following: A first effective time starting from the first moment when GNSS position positioning is completed; A second effective time starting from the second moment after completion of GNSS position positioning and before completion of downlink synchronization; A third effective time starting from the third moment when downlink synchronization is completed; A fourth effective time starting from the fourth moment after completion of downlink synchronization and before the second timer times out.

62. The apparatus according to claim 56, when starting the second timer after completion of GNSS position positioning and before completion of downlink synchronization, the effective time includes one of the following: A second effective time starting from the second moment after completion of GNSS position positioning and before completion of downlink synchronization; A third effective time starting from the third moment when downlink synchronization is completed; A fourth effective time starting from the fourth moment after completion of downlink synchronization and before the second timer times out.

63. The apparatus according to claim 56, when starting the second timer after completion of downlink synchronization, the effective time includes one of the following: A fourth effective time starting from the fourth moment after completion of downlink synchronization and before the second timer times out.

64. The apparatus according to any one of claims 51 to 63, the apparatus further includes: A maintenance module, configured to maintain the second timer and obtain the system information within the remaining effective time when it is determined that the GNSS position is invalid after starting the second timer; A third restart module, configured to restart the GNSS measurement when the terminal device obtains the system information within the remaining effective time.

65. The apparatus according to any one of claims 51 to 63, the apparatus further includes: A second stop module, configured to stop the second timer and restart the GNSS measurement when it is determined that the GNSS position is invalid after starting the second timer.

66. The apparatus according to any one of claims 51 to 63, A third recovery module, configured to recover uplink synchronization with a network device after obtaining the system information within the effective time of the second timer.

67. The apparatus according to any one of claims 51 to 63, the apparatus further comprising: A fourth trigger module, configured to trigger RLF when the system information is not obtained within the effective time of the second timer.

68. The apparatus according to any one of claims 50 to 63, the apparatus further comprising: A second receiving module, configured to receive configuration information sent by a network device, where the configuration information includes first timer information for running the first timer and second timer information for running the second timer.

69. The apparatus according to claim 68, the apparatus is further configured to Determine the duration of the second timer according to the remaining time during GNSS measurement in the configuration information, or Determine the duration of the second timer according to the remaining time during GNSS measurement and the downlink synchronization time in the configuration information.

70. The apparatus according to any one of claims 51 to 68, wherein the first timer comprises: Timer T317; The second timer includes: Timer T318.

71. The apparatus according to any one of claims 51 to 68, wherein the system information at least includes: System Information Block SIB31.

Images