GNSS measurement methods, terminals, and storage media for terminal equipment

Abstract

This application discloses a GNSS measurement method, terminal, and storage medium for a terminal device, belonging to the field of wireless communication. The GNSS measurement method provided in this application includes: triggering GNSS measurement if the Tracking Area Update (TAU) periodic timer times out or the device actively exits the power-saving mode (PSM); or, triggering GNSS measurement at a preset time before the TAU periodic timer times out. This method ensures that GNSS measurement is triggered at a specific time, avoiding the GNSS module remaining active for extended periods, saving power, and solving the problem of excessive power consumption when the terminal device is online for long-term GNSS measurement.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a GNSS measurement method, terminal, and storage medium for a terminal device. Background Technology

[0002] Narrow Band Internet of Things (NB-IoT) and / or LTE-enhanced MTO (eMTC) terminal equipment (TE) used in existing terrestrial mobile network applications typically do not have Global Navigation Satellite System (GNSS) measurement capabilities. However, in non-terrestrial network (NTN) scenarios, satellites move quickly and have wide coverage, resulting in large transmission delays and large Doppler frequency shifts in NTN scenarios. If the terminal equipment does not have GNSS positioning and ephemeris information acquisition capabilities, it cannot accurately estimate the distance from the terminal to the satellite and estimate the uplink Doppler frequency offset of the service link.

[0003] If the NTN IoT terminal device has GNSS positioning capabilities, the network side sends ephemeris information of relevant satellites through system information. The NTN IoT terminal device has the ability to calculate the distance / delay and Doppler shift between the satellite and the terminal device based on the position information and ephemeris information obtained from GNSS. However, if the GNSS measurement module remains active, it will cause excessive power consumption of the terminal. Summary of the Invention

[0004] This application proposes a GNSS measurement method, terminal, and storage medium for terminal devices to solve the problem of excessive power consumption during GNSS measurement in IoT terminal devices.

[0005] To achieve the above objectives, this application adopts the following solution:

[0006] This invention provides a GNSS measurement method for a terminal device, comprising:

[0007] If the tracking area update TAU period timer times out or the user actively exits the energy-saving mode PSM, GNSS measurements are triggered.

[0008] Alternatively, GNSS measurements can be triggered at a preset time before the TAU periodic timer expires.

[0009] Optionally, the method further includes:

[0010] If the tracking area update TAU period timer times out or the power saving mode PSM is actively exited, GNSS measurement is triggered and the GNSS timer is started. If the GNSS timer times out, the IoT communication activity state is entered.

[0011] Alternatively, after triggering GNSS measurements at a preset time before the TAU periodic timer expires, if the TAU periodic timer expires, the system enters the IoT communication activity state.

[0012] Optionally, the TAU periodic timer is related to the reporting cycle of the monitoring or measurement data of the terminal device.

[0013] Optionally, the duration of the GNSS timer is greater than or equal to the duration of the GNSS measurement.

[0014] Optionally, the GNSS measurement duration is estimated based on the GNSS receiver startup method of the terminal device.

[0015] Optionally, the preset time is related to the duration of the GNSS measurement.

[0016] Optionally, the preset time is greater than or equal to the GNSS measurement duration.

[0017] Optionally, the GNSS measurement method further includes:

[0018] Before the next GNSS measurement is triggered, the uplink data is pre-compensated multiple times based on the positioning information obtained from the GNSS measurement.

[0019] Optionally, the uplink transmitted data includes uplink transmitted data during at least one of the following periods:

[0020] During the initial uplink transmission of the random access preamble;

[0021] During repeated transmission of the random access preamble;

[0022] During the initial transmission of the physical uplink shared channel;

[0023] Repeated transmissions during the physical uplink shared channel period.

[0024] Optionally, the multiple pre-compensation steps for uplink transmitted data further include:

[0025] At the beginning of each consecutive uplink data transmission period, the timing advance and / or Doppler frequency offset are calculated once, and the timing advance and / or Doppler frequency offset are updated according to a preset period during the uplink data transmission period.

[0026] Optionally, the preset period is configured by the network side and carried in the system message.

[0027] This invention also provides a terminal device, including: a memory, a transceiver, and a processor, wherein: the memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; and the processor is used to read the computer program in the memory and perform the following operations:

[0028] If the tracking area update TAU period timer times out or the user actively exits the energy-saving mode PSM, GNSS measurements are triggered.

[0029] Alternatively, GNSS measurements can be triggered at a preset time before the TAU periodic timer expires.

[0030] Optionally, the processor is further configured to:

[0031] If the TAU period timer for the tracking area expires, GNSS measurement is triggered, and then the GNSS timer is started. If the GNSS timer expires, the system enters the IoT communication activity state.

[0032] Alternatively, after triggering GNSS measurements at a preset time before the TAU periodic timer expires, if the TAU periodic timer expires, the system enters the IoT communication activity state.

[0033] Optionally, the TAU periodic timer is related to the reporting cycle of the monitoring or measurement data of the terminal device.

[0034] Optionally, the duration of the GNSS timer is greater than or equal to the duration of the GNSS measurement.

[0035] Optionally, the GNSS measurement duration is estimated based on the GNSS receiver startup method of the terminal device.

[0036] Optionally, the preset time is related to the duration of the GNSS measurement.

[0037] Optionally, the preset time is greater than or equal to the GNSS measurement duration.

[0038] Optionally, the processor 710 is further configured to:

[0039] Before the next GNSS measurement is triggered, the uplink data is pre-compensated multiple times based on the positioning information obtained from the GNSS measurement.

[0040] Optionally, the uplink transmitted data includes uplink transmitted data during at least one of the following periods:

[0041] During the initial uplink transmission of the random access preamble;

[0042] During repeated transmission of the random access preamble;

[0043] During the initial transmission of the physical uplink shared channel;

[0044] Repeated transmissions during the physical uplink shared channel period.

[0045] Optionally, the processor 710 further includes performing multiple pre-compensations on the uplink transmitted data, including:

[0046] At the beginning of each consecutive uplink data transmission period, the timing advance and / or Doppler frequency offset are calculated once, and the timing advance and / or Doppler frequency offset are updated according to a preset period during the uplink data transmission period.

[0047] Optionally, the preset period is configured by the network side and carried in the system message.

[0048] This invention also provides a GNSS measurement device for a terminal device, comprising:

[0049] The control unit is used to trigger GNSS measurements if the tracking area update TAU period timer times out or if the user actively exits the energy-saving mode PSM.

[0050] Alternatively, GNSS measurements can be triggered at a preset time before the TAU periodic timer expires.

[0051] This application also provides a processor-readable storage medium storing a computer program for causing the processor to execute the GNSS measurement method for the terminal device provided in this embodiment of the invention.

[0052] In this embodiment, GNSS measurement is triggered if the tracking area update TAU period timer times out or the device actively exits the power-saving PSM mode; or, GNSS measurement is triggered at a preset time before the TAU period timer times out. This method enables GNSS measurement to be triggered at a specific time, avoiding the GNSS measurement module remaining active for extended periods, saving power, and solving the problem of excessive power consumption caused by long-term online GNSS measurement by terminal devices. Attached Figure Description

[0053] Figure 1 A flowchart illustrating a GNSS measurement method for a terminal device provided in this application embodiment;

[0054] Figure 2 A flowchart illustrating a GNSS measurement method for a terminal device provided in this application embodiment;

[0055] Figure 3 This is a schematic diagram of terminal device state switching provided in an embodiment of this application;

[0056] Figure 4 A schematic diagram of GNSS measurement using a terminal device provided in an embodiment of this application;

[0057] Figure 5 This is a schematic diagram of GNSS measurement using a terminal device, provided as an embodiment of this application.

[0058] Figure 6 A schematic diagram of an uplink compensation update cycle provided in an embodiment of this application;

[0059] Figure 7 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application;

[0060] Figure 8 This is a schematic diagram of the GNSS measurement device structure of a terminal device provided in an embodiment of this application. Detailed Implementation

[0061] To make the technical problems, technical solutions and advantages of the present invention clearer, a detailed description will be given below in conjunction with the accompanying drawings and specific embodiments.

[0062] In this embodiment of the invention, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0063] In this embodiment of the invention, the term "multiple" refers to two or more, and other quantifiers are similar.

[0064] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0065] This invention provides a GNSS measurement method, terminal, and storage medium for a terminal device to solve the problem of excessive power consumption of IoT terminals during GNSS measurement.

[0066] The method and apparatus are based on the same concept of the application. Since the methods and apparatus solve problems in similar ways, the implementation of the apparatus and methods can refer to each other, and the repeated parts will not be described again.

[0067] The network device involved in this application embodiment can be a base station, which may include multiple cells providing services to terminals. Depending on the specific application, a base station may also be called an access point, or a device in an access network that communicates with a wireless terminal device through one or more sectors on the air interface, or other names. The network device can be used to exchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network device can also coordinate the attribute management of the air interface. For example, the network equipment involved in the embodiments of this application can be a base transceiver station (BTS) in a Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), a NodeB in a Wide-band Code Division Multiple Access (WCDMA) system, an evolved Node B (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a next generation system, a Home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of this application. In some network structures, the network equipment may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and distributed unit may be geographically separated.

[0068] Network devices and terminals can each use one or more antennas for Multiple-Input Multiple-Output (MIMO) transmission. MIMO transmission can be Single-User MIMO (SU-MIMO) or Multiple-User MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, and can also be diversity transmission, precoding transmission, or beamforming transmission, etc.

[0069] refer to Figure 1 , Figure 2 A flowchart illustrating the GNSS measurement method for a terminal device provided in an embodiment of this application is shown, including:

[0070] Step 101: If the tracking area update TAU period timer times out or the user actively exits the energy-saving mode PSM, trigger GNSS measurement.

[0071] or,

[0072] Step 201: Trigger GNSS measurement at a preset time before the TAU periodic timer expires.

[0073] By using step 101 or step 201, the GNSS measurement module of the terminal device can be activated within a specific time period to trigger GNSS measurement, thus avoiding the GNSS measurement module being in a long-term running state and saving power.

[0074] Optionally, the method further includes:

[0075] If the tracking area update TAU period timer times out or the power saving mode PSM is actively exited, GNSS measurement is triggered and the GNSS timer is started. If the GNSS timer times out, the IoT communication activity state is entered.

[0076] Alternatively, after triggering GNSS measurements at a preset time before the TAU periodic timer expires, if the TAU periodic timer expires, the system enters the IoT communication activity state.

[0077] The terminal device provided in this embodiment of the invention is an NTN IoT terminal device in a non-terrestrial network (NTN) scenario. Specifically, the Tracking Area Update (TAU) is performed, and the duration of the TAU periodic timer is from the start of the Idle state to the end of the Power Saving Mode (PSM). This embodiment of the invention uses the TAU periodic timer-T3412 as an example.

[0078] It is worth noting that the terminal equipment in this application mainly refers to Internet of Things (IoT) terminal equipment, but it is not excluded that it can be applied to general terminal equipment (UE).

[0079] To reduce power consumption and extend battery life, NB-IoT / eMTC systems employ Power Saving Mode (PSM) and Extended Discontinuous Reception (eDRX), using extended periodic timers.

[0080] refer to Figure 3 NB-IoT / eMTC terminal devices typically operate in three states: Connected, Idle, and Power Saving Mode (PSM). The transition mechanisms between these states are as follows: Figure 3 As shown:

[0081] After the module registers and joins the network, it enters the connected state. In the connected state, the terminal device can send and receive data. After sending data, the terminal device will remain in the connected state and start an "inactive timer," which defaults to 20 seconds and can be configured from 1 second to 3600 seconds. When the "inactive timer" expires, the terminal device enters the idle state and starts an active timer (Active-Timer-T3324). The timeout of T3324 can be configured from 2 seconds to 186 minutes. In the idle state, the terminal device listens for paging information at regular intervals. When T3324 expires, the terminal device enters the power-saving mode. When the TAU cycle ends, the terminal device enters the connected state. The TAU cycle timer-T3412 can be configured from 54 minutes to 310 hours.

[0082] In eDRX mode, the network connection to the terminal device will intermittently drop. When the network is connected, the terminal device can receive data; when disconnected, it cannot receive data. The downtime ranges from tens of seconds to several hours, and can be configured according to needs. Entering power-saving mode (PSM) is equivalent to reducing the frequency of eDRX switching even further, as low as once every few days. Similarly, data can be received when the network is on, but not when it is off.

[0083] The principle of Power Saving Mode (PSM) is that it allows terminal devices to shut down signal transmission and reception and AS (Access Layer) related functions after entering an idle state for a period of time. This is equivalent to the terminal device partially shutting down after entering PSM, thereby reducing power consumption of antennas, radio frequency components, signaling processing, etc. During PSM, the terminal device does not accept any network paging; from the network side, the terminal device is unreachable at this time. Only when the TAU periodic timer (T3412) times out, or when the terminal device actively exits PSM to process uplink data, will the terminal device exit PSM mode, enter an idle state, and then enter a connected state to handle uplink and downlink services.

[0084] Figure 4 The following diagram illustrates the GNSS measurements performed in steps 101-102. Figure 5 The diagram illustrates the GNSS measurements performed in steps 201-202. Figure 4 When the TAU periodic timer (T3412) times out, GNSS measurement is triggered and the GNSS timer is started. Figure 5 The GNSS measurement is triggered at a preset time before the TAU periodic timer expires, and the GNSS timer is started.

[0085] Steps 101-102 enable the TAU periodic timer-T3412 to time out, or the terminal device to actively exit the power-saving mode PSM, triggering the terminal device to turn on the GNSS module to perform GNSS measurement and start the GNSS timer at the same time; when the GNSS timer times out, the GNSS measurement has ended and the GNSS module has been turned off, at which point the terminal device is allowed to enter the IoT communication activity state.

[0086] Steps 201-202 enable the terminal device to open the GNSS module and perform GNSS measurements at a preset time before the TAU periodic timer-T3412 expires, and at the same time start the GNSS timer; when the TAU periodic timer-T3412 expires, the GNSS measurement has ended and the GNSS module has been turned off, at which point the terminal device is allowed to enter the IoT communication activity state.

[0087] The steps 101-102 or 201-202 described above ensure that the GNSS measurement and IoT communication activity of the terminal device do not overlap, and the signals of the two do not interfere with each other. Furthermore, the terminal device will not perform GNSS measurement when it enters the IoT communication activity state, thus avoiding frequent startup of the GNSS module and greatly saving power.

[0088] Optionally, the TAU periodic timer is related to the reporting cycle of the monitoring or measurement data of the terminal device.

[0089] Specifically, for the application of Industrial Internet of Things (IIoT) in predictive maintenance, terminal devices need to report monitoring data periodically. Therefore, IIoT terminal devices are mostly in a sleep state, waking up periodically to report monitoring data. In this embodiment of the invention, a TAU periodic timer (T3412) is used to trigger the terminal device to perform GNSS measurements. The duration of the TAU periodic timer (T3412) is related to the monitoring data reporting cycle.

[0090] Optionally, the duration of the GNSS timer is greater than or equal to the duration of the GNSS measurement.

[0091] Specifically, the duration of the GNSS timer is greater than or equal to the duration of the GNSS measurement, which ensures that the terminal device can only enter the IoT communication activity state after the GNSS measurement is completed and the GNSS module is turned off.

[0092] Optionally, the GNSS measurement duration is estimated based on the GNSS receiver startup method of the terminal device.

[0093] Specifically, the GNSS Time To First Fix (TTFF) is a crucial indicator for evaluating GNSS receiver performance. Depending on the specific circumstances when the GNSS receiver is powered on, the initial positioning process can be categorized into three modes: cold start, warm start, and hot start. In cold start mode, there is virtually no usable information, and the startup process takes approximately 40 seconds. Warm start and hot start modes utilize satellite ephemeris and satellite almanacs, respectively, to determine the visible satellites at the user's current location for positioning. Currently, navigation products from well-known international companies such as Sirf and U-Blox achieve hot start times of 1-2 seconds and warm start times of approximately 5-9 seconds. Domestic receivers currently have a hot start time of around 9 seconds, indicating a significant gap in rapid positioning technology compared to international counterparts, and the technology is still immature. Therefore, based on the GNSS receiver startup method of the terminal device, the duration of GNSS measurements can be estimated, and the duration of the GNSS timer can be determined based on the duration of GNSS measurements.

[0094] Optionally, the preset time is related to the duration of the GNSS measurement.

[0095] Specifically, the preset time before the TAU periodic timer expires is determined based on the duration of the GNSS measurement. It is necessary to ensure that the GNSS measurement is completed and the GNSS module is in the off state when the terminal device enters the IoT communication activity state.

[0096] Optionally, the preset time is greater than or equal to the GNSS measurement duration.

[0097] Only when the preset time is greater than or equal to the GNSS measurement duration can it be ensured that the GNSS measurement is completed, the GNSS module is shut down, and the GNSS measurement does not overlap with the IoT communication activity state after the TAU periodic timer expires.

[0098] Optionally, the GNSS measurement method further includes:

[0099] Before the next GNSS measurement is triggered, the uplink data is pre-compensated multiple times based on the positioning information obtained from the GNSS measurement.

[0100] Specifically, because low-Earth orbit satellites move at a relatively high speed relative to the Earth, approximately 7.6 km / s, even if IoT terminal devices used for industrial monitoring are in motion, their movement speed is negligible within a short timeframe (at least within 2 hours). Therefore, the positioning information obtained by the terminal device through GNSS measurements can be used for compensation calculations in subsequent uplink data transmissions. In other words, the positioning information obtained from a single GNSS measurement can be reused in repeated uplink data transmissions.

[0101] Optionally, the uplink transmitted data includes uplink transmitted data during at least one of the following periods:

[0102] During the initial uplink transmission of the random access preamble;

[0103] During repeated transmission of the random access preamble;

[0104] During the initial transmission of the physical uplink shared channel;

[0105] Repeated transmissions during the physical uplink shared channel period.

[0106] Optionally, pre-compensation for uplink transmitted data may also include:

[0107] Based on the ephemeris information and positioning information obtained from GNSS measurements at the current moment, the timing advance is updated and calculated; based on the timing advance (TA), the uplink timing data is pre-compensated.

[0108] And / or, based on the ephemeris information and positioning information obtained from GNSS measurements at the current moment, update and calculate the Doppler frequency offset; based on the Doppler frequency offset, pre-compensate the uplink frequency data.

[0109] Optionally, the multiple pre-compensation steps for uplink transmitted data further include:

[0110] At the beginning of each consecutive uplink data transmission period, the timing advance and / or Doppler frequency offset are calculated once, and the timing advance and / or Doppler frequency offset are updated according to a preset period during the uplink data transmission period.

[0111] For example, refer to Figure 6 It shows that there is a gap between each consecutive uplink data transmission period. A calculation is performed at the beginning of each consecutive uplink data transmission period, and then the calculation is updated at a preset period in the middle of the consecutive uplink data transmission period. A calculation is performed at the beginning of the next consecutive uplink data transmission period, and then the calculation is updated at a preset period in the middle, and so on.

[0112] Optionally, the preset period is configured by the network side and carried in the system message.

[0113] Specifically, the terminal device extrapolates the ephemeris information of the new time from the ephemeris information obtained from SIBx, and updates the timing advance and Doppler frequency offset together with the positioning information obtained from GNSS. The preset update period for the calculation is configured by the network side and carried in the system message SIB.

[0114] Optionally, the GNSS timer and GNSS duration can be configured by the network side according to user service requirements.

[0115] refer to Figure 4 The GNSS measurement method for terminal equipment provided by the present invention will be further described below.

[0116] Figure 4 Taking NB-IoT terminal devices as an example, the TAU periodic timer (T3412 timer) triggers GNSS measurement upon timeout, and simultaneously triggers the GNSS timer. After GNSS measurement, when the GNSS timeout period is exceeded, the terminal device enters the IoT communication activity state.

[0117] At this time, the terminal device begins cell search, searching for downlink synchronization signals NPSS (Narrowband Primary Synchronization Signal) and / or NSSS (Narrowband Auxiliary Synchronization Signal). The terminal device synchronizes downlink frequency and symbols with the network, decodes NBCH (Narrowband Broadcast Channel) to obtain the Main System Information Block (MIB), decodes NPDSCH (Narrowband Physical Downlink Shared Channel) to obtain other system information carried on it, such as PRACH (Physical Random Access Channel) resource configuration information from SIB2-NB, and satellite ephemeris information from SIBx. Using the GNSS positioning information obtained from GNSS measurements during wake-up and the ephemeris information obtained from SIBx, the terminal device calculates the timing advance and Doppler frequency offset required for uplink timing and uplink frequency pre-compensation of subsequent uplink data transmissions, including the period during the first uplink transmission of the random access preamble, the period during repeated transmissions of the random access preamble, the period during the first transmission of the Physical Uplink Shared Channel (PUSCH), and / or the period during repeated transmissions of the Physical Uplink Shared Channel.

[0118] Therefore, a single GNSS measurement can be used to calculate the timing lead and Doppler frequency offset required for multiple pre-compensation operations. After a monitoring data report is completed, the terminal device enters eDRX state, then enters idle state, activates timer T3324 to time out, and then enters PSM state. A new GNSS measurement will be performed the next time the PSM state is activated.

[0119] refer to Figure 5 The GNSS measurement method for terminal equipment provided by the present invention will be further described below.

[0120] The GNSS measurement is triggered at a preset time before the TAU periodic timer (T3412) expires. The length of the preset time is longer than the duration of the GNSS measurement to ensure that the terminal device can enter the IoT communication active state only after the GNSS measurement is completed. Then, the terminal device enters the IoT communication active state when the TAU periodic timer (T3412) expires after the GNSS measurement. The terminal device begins cell search, searching for downlink synchronization signals (NPSS / NSSS). It synchronizes downlink frequency and symbols with the network, decodes the Narrowband Broadcast Channel (NBCH) to obtain the Master System Information Block (MIB), and decodes the Narrowband Physical Downlink Shared Channel (NPDSCH) to obtain other system information carried on it. For example, it obtains Physical Random Access Channel (PRACH) resource configuration information from Narrowband System Message 2 (SIB2-NB) and satellite ephemeris information from SIBx. Using the GNSS positioning information obtained during wake-up and the ephemeris information obtained from SIBx, it calculates the timing advance and Doppler frequency offset required for uplink timing and uplink frequency pre-compensation for subsequent uplink data transmissions, including during the initial uplink random access preamble transmission, the repeated random access preamble transmission, the initial physical uplink shared channel transmission, and / or the repeated physical uplink shared channel transmission.

[0121] After a monitoring data report is completed, the terminal device enters eDRX state, then enters idle state, timer T3324 times out, and the terminal device enters PSM state. It will then perform a new GNSS measurement upon waking up from PSM.

[0122] It is worth noting that, in addition to the TAU timer timeout period or the preset time before the TAU timer timeout, the terminal device can also wake up from the PSM to perform GNSS measurements based on an active reporting request.

[0123] In summary, the GNSS measurement method for terminal devices provided in this embodiment of the invention has the following beneficial effects:

[0124] This allows the terminal device to enter IoT communication activity state when the TAU periodic timer expires, triggering GNSS measurement and simultaneously GNSS timer. After GNSS measurement is completed and the GNSS timer expires, the terminal device enters IoT communication activity state. Alternatively, GNSS measurement can be triggered at a preset time before the TAU periodic timer expires, and the terminal device enters IoT communication activity state after GNSS measurement is completed and the TAU periodic timer expires. This ensures that the IoT is not in active communication state when the terminal device is performing GNSS measurement, and that the GNSS measurement and IoT active state of the terminal device do not overlap or interfere with each other, thus saving power.

[0125] Furthermore, a single GNSS measurement can be used to calculate the timing advance and Doppler frequency offset required for multiple uplink data pre-compensation calculations. The uplink pre-compensation update calculation cycle is configured by the network side and carried in the system information.

[0126] refer to Figure 7 This application provides a terminal device 70, including: a memory 720, a transceiver 700, and a processor 710, wherein:

[0127] Memory 720 is used to store computer programs;

[0128] Transceiver 700 is used to send and receive data under the control of the processor;

[0129] Processor 710 is configured to read the computer program in the memory and perform the following operations:

[0130] If the tracking area update TAU period timer times out or the user actively exits the energy-saving mode PSM, GNSS measurements are triggered.

[0131] Alternatively, GNSS measurements can be triggered at a preset time before the TAU periodic timer expires.

[0132] Optionally, the processor is further configured to:

[0133] If the TAU period timer for the tracking area expires, GNSS measurement is triggered, and then the GNSS timer is started. If the GNSS timer expires, the system enters the IoT communication activity state.

[0134] Alternatively, after triggering GNSS measurements at a preset time before the TAU periodic timer expires, if the TAU periodic timer expires, the system enters the IoT communication activity state.

[0135] Among them, Figure 7In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 710 and memory represented by memory 720 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 700 can be multiple components, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. For different user equipment, the user interface 730 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

[0136] Transceiver 700 is used to receive and send data under the control of processor 710.

[0137] The processor 710 is responsible for managing the bus architecture and general processing, while the memory 720 can store the data used by the processor 700 when performing operations.

[0138] Optionally, the processor 710 can be a CPU (Central Processing Unit), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), or CPLD (Complex Programmable Logic Device), and the processor can also adopt a multi-core architecture.

[0139] The processor executes any of the methods provided in the embodiments of the present invention according to the obtained executable instructions by calling a computer program stored in memory. The processor and memory may also be physically separated.

[0140] Optionally, the TAU periodic timer is related to the reporting cycle of the monitoring or measurement data of the terminal device.

[0141] Optionally, the duration of the GNSS timer is greater than or equal to the duration of the GNSS measurement.

[0142] Optionally, the GNSS measurement duration is estimated based on the GNSS receiver startup method of the terminal device.

[0143] Optionally, the preset time is related to the duration of the GNSS measurement.

[0144] Optionally, the preset time is greater than or equal to the GNSS measurement duration.

[0145] Optionally, the processor 710 is further configured to:

[0146] Before the next GNSS measurement is triggered, the uplink data is pre-compensated multiple times based on the positioning information obtained from the GNSS measurement.

[0147] Optionally, the uplink transmitted data includes uplink transmitted data during at least one of the following periods:

[0148] During the initial uplink transmission of the random access preamble;

[0149] During repeated transmission of the random access preamble;

[0150] During the initial transmission of the physical uplink shared channel;

[0151] Repeated transmissions during the physical uplink shared channel period.

[0152] Optionally, the processor 710 further includes pre-compensating for at least one uplink data transmission, including:

[0153] At the beginning of each consecutive uplink data transmission period, the timing advance and / or Doppler frequency offset are calculated once, and the timing advance and / or Doppler frequency offset are updated according to a preset period during the uplink data transmission period.

[0154] Optionally, the preset period is configured by the network side and carried in the system message.

[0155] Optionally, the GNSS timer and GNSS duration can be configured by the network side according to user service requirements.

[0156] It should be noted that the terminal device provided in this embodiment of the invention can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0157] refer to Figure 8 This application provides a GNSS measurement device 80 for a terminal device, comprising:

[0158] Control unit 81 is used to trigger GNSS measurements if the tracking area update TAU period timer times out or actively exits the energy-saving mode PSM.

[0159] Alternatively, GNSS measurements can be triggered at a preset time before the TAU periodic timer expires.

[0160] Optionally, the control unit 81 is further configured to:

[0161] If the TAU period timer for the tracking area expires, GNSS measurement is triggered, and then the GNSS timer is started. If the GNSS timer expires, the system enters the IoT communication activity state.

[0162] Alternatively, after triggering GNSS measurements at a preset time before the TAU periodic timer expires, if the TAU periodic timer expires, the system enters the IoT communication activity state.

[0163] Optionally, the TAU periodic timer is related to the reporting cycle of the monitoring or measurement data of the terminal device.

[0164] Optionally, the duration of the GNSS timer is greater than or equal to the duration of the GNSS measurement.

[0165] Optionally, the GNSS measurement duration is estimated based on the GNSS receiver startup method of the terminal device.

[0166] Optionally, the preset time is related to the duration of the GNSS measurement.

[0167] Optionally, the preset time is greater than or equal to the GNSS measurement duration.

[0168] Optionally, the GNSS measuring device 80 also includes a processing unit 82:

[0169] This is used to perform multiple pre-compensations on the uplink transmitted data based on the positioning information obtained from GNSS measurements before the next GNSS measurement is triggered.

[0170] Optionally, the uplink transmitted data includes uplink transmitted data during at least one of the following periods:

[0171] During the initial uplink transmission of the random access preamble;

[0172] During repeated transmission of the random access preamble;

[0173] During the initial transmission of the physical uplink shared channel;

[0174] Repeated transmissions during the physical uplink shared channel period.

[0175] Optionally, the processing unit 82 is further configured to pre-compensate at least one uplink data transmission, including:

[0176] At the beginning of each consecutive uplink data transmission period, the timing advance and / or Doppler frequency offset are calculated once, and the timing advance and / or Doppler frequency offset are updated according to a preset period during the uplink data transmission period.

[0177] Optionally, the preset period is configured by the network side and carried in the system message.

[0178] Optionally, the GNSS timer and GNSS duration can be configured by the network side according to user service requirements.

[0179] It should be noted that the GNSS measuring device 80 provided in this embodiment of the invention can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0180] It should be noted that the division of units in the embodiments of this invention is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0181] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0182] This invention also provides a processor-readable storage medium storing a computer program for causing the processor to execute the GNSS measurement method for the terminal device provided in this invention.

[0183] The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0184] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0185] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0186] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0187] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0188] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A GNSS measurement method of a terminal device, characterized by, The method comprises: triggering GNSS measurement if a tracking area update (TAU) periodic timer expires or the terminal device actively exits a power saving mode (PSM); or triggering GNSS measurement at a preset time before the TAU periodic timer expires. The method further comprises: starting a GNSS timer after triggering GNSS measurement if the TAU periodic timer expires or the terminal device actively exits the PSM, and entering an Internet of Things (IoT) communication active state if the GNSS timer expires; or entering the IoT communication active state if the TAU periodic timer expires after triggering GNSS measurement at the preset time before the TAU periodic timer expires.

2. The GNSS measurement method of a terminal device according to claim 1, characterized by, The TAU periodic timer is related to a reporting period of monitoring or measurement data of the terminal device.

3. The GNSS measurement method of a terminal device according to claim 1, characterized by, A duration of the GNSS timer is greater than or equal to a GNSS measurement duration.

4. The GNSS measurement method of a terminal device according to claim 3, characterized by, The GNSS measurement duration is estimated according to a GNSS receiver start mode of the terminal device.

5. The GNSS measurement method of a terminal device according to claim 1, characterized by, The preset time is related to the GNSS measurement duration.

6. The GNSS measurement method of a terminal device according to claim 5, characterized by, The preset time is greater than or equal to the GNSS measurement duration.

7. The GNSS measurement method of a terminal device according to claim 1, characterized by, The GNSS measurement method further comprises: performing multiple pre-compensations on uplink transmission data according to positioning information obtained through GNSS measurement before triggering GNSS measurement next time.

8. The GNSS measurement method of a terminal device according to claim 7, characterized by, The uplink transmission data includes uplink transmission data during at least one of the following: a first uplink transmission of a random access preamble; repeated transmission of the random access preamble; first transmission of a physical uplink shared channel; and repeated transmission of the physical uplink shared channel.

9. The GNSS measurement method of a terminal device according to claim 7, characterized by, The multiple pre-compensations on the uplink transmission data further comprise: calculating a timing advance and / or a Doppler frequency offset at the beginning of each continuous uplink data transmission period, and updating the calculation of the timing advance and / or the Doppler frequency offset at a preset period within the uplink data transmission period.

10. The GNSS measurement method of the terminal device according to claim 9, wherein the preset period is configured by a network side and carried in a system message.

11. A terminal device, comprising: The method comprises: a memory, a transceiver, and a processor, wherein the memory is configured to store a computer program, the transceiver is configured to transceive data under control of the processor, and the processor is configured to read the computer program in the memory and perform the following operations: triggering GNSS measurement if a tracking area update (TAU) periodic timer expires; or triggering GNSS measurement at a preset time before the TAU periodic timer expires or actively exiting a PSM mode. The processor is further configured to: start a GNSS timer after triggering GNSS measurement if the TAU periodic timer expires, and enter an Internet of Things (IoT) communication active state if the GNSS timer expires; or enter the IoT communication active state if the TAU periodic timer expires after triggering GNSS measurement at the preset time before the TAU periodic timer expires.

12. The terminal device according to claim 11, characterized by The TAU periodic timer is related to a reporting period of monitoring or measurement data of the terminal device.

13. The terminal device of claim 11, wherein, A duration of the GNSS timer is greater than or equal to a GNSS measurement duration.

14. The terminal device according to claim 13, characterized by The GNSS measurement duration is obtained according to a GNSS receiver start mode of the terminal device.

15. The terminal device of claim 11, wherein, The preset time is related to the GNSS measurement duration.

16. The terminal device according to claim 15, characterized by The preset time is greater than or equal to the GNSS measurement duration.

17. The terminal device of claim 11, wherein, The uplink transmission data is pre-compensated multiple times according to the positioning information obtained from the GNSS measurement before the next GNSS measurement is triggered.

18. The terminal device of claim 17, wherein, The uplink transmission data includes uplink transmission data during at least one of the following: During the first uplink transmission of a random access preamble; During the repeated transmission of a random access preamble; During the first transmission of a physical uplink shared channel; During the repeated transmission of a physical uplink shared channel.

19. The terminal device of claim 17, wherein, The multiple pre-compensations of the uplink transmission data further include: The timing advance and / or Doppler frequency offset are calculated once at the beginning of each continuous uplink data transmission period, and the timing advance and / or Doppler frequency offset are updated at a preset period within the uplink data transmission period.

20. The terminal device of claim 19, wherein, The preset period is configured by a network side and carried in a system message.

21. A GNSS measurement apparatus of a terminal device, characterized by comprising: The control unit is configured to: Trigger the GNSS measurement if a tracking area update (TAU) period timer expires or the terminal device actively exits a power saving mode (PSM); or Trigger the GNSS measurement at a preset time before the TAU period timer expires. The control unit is further configured to: Start a GNSS timer after the GNSS measurement is triggered if the TAU period timer expires or the terminal device actively exits the PSM, and enter an Internet of Things (IoT) communication active state if the GNSS timer expires; or Enter the IoT communication active state if the TAU period timer expires after the GNSS measurement is triggered at the preset time before the TAU period timer expires.

22. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, and the computer program is executed by the processor to implement the steps of the GNSS measurement method of the terminal device according to any one of claims 1 to 10.

Images