Timer-based operation execution method and device, equipment, medium and product

Abstract

The invention discloses an operation execution method and device based on a timer, equipment, a medium and a product, and relates to the technical field of communication. The method comprises the following steps: executing a first operation on a first timer based on first time information; wherein the first time information is time information related to global navigation satellite system (GNSS) measurement and / or satellite switching. According to the method, the situation that the timer is overtime when communication is interrupted can be avoided for the terminal equipment, so that the terminal equipment can perform data transmission as soon as possible after completing GNSS measurement and / or satellite switching.

Description

Timer-based operation execution method, device, equipment, medium and product Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a timer-based operation execution method, device, equipment, medium and product. Background Art

[0002] Currently, the 3rd Generation Partnership Project (3GPP) is researching non-terrestrial network (NTN) technology.

[0003] Related technologies use satellite communications to provide communication services to users on the ground. During Global Navigation Satellite System (GNSS) measurements and satellite handovers, communication between a terminal device and the current cell is interrupted. Shortening data interruptions and reducing power consumption are pressing challenges.

[0004] Summary of the Invention

[0005] The present invention provides a method, apparatus, device, medium, and product for executing operations based on a timer. The technical solution is as follows:

[0006] According to one aspect of the present application, a timer-based operation execution method is provided, the method comprising:

[0007] Based on the first time information, perform a first operation on the first timer;

[0008] The first time information is time information related to GNSS measurement and / or satellite switching.

[0009] According to another aspect of the present application, a timer-based operation execution method is provided, the method comprising:

[0010] If the first timer times out within the first time period, the third operation is not performed;

[0011] or,

[0012] If the first timer times out outside the first time period, performing the third operation;

[0013] The first time period is a time period related to GNSS measurement and / or satellite switching.

[0014] According to another aspect of the present application, a timer-based operation execution device is provided, the device comprising:

[0015] an execution module, configured to execute a first operation on a first timer based on the first time information;

[0016] The first time information is time information related to GNSS measurement and / or satellite switching.

[0017] According to another aspect of the present application, a timer-based operation execution device is provided, the device comprising:

[0018] an execution module, configured to not execute the third operation if the first timer times out within the first time period; or

[0019] The execution module is configured to execute the third operation when the first timer times out of the first time period;

[0020] The first time period is a time period related to GNSS measurement and / or satellite switching.

[0021] According to another aspect of the present application, a chip is provided, which includes a programmable logic circuit and / or program instructions, and when a communication device equipped with the chip is running, is used to implement the timer-based operation execution method described above.

[0022] According to another aspect of the present application, a terminal device is provided, comprising: a processor; a transceiver connected to the processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the timer-based operation execution method as described above.

[0023] According to another aspect of the present application, a computer-readable storage medium is provided, in which at least one program is stored. The at least one program is loaded and executed by a processor to enable a communication device to implement the timer-based operation execution method as described above.

[0024] According to another aspect of the present application, a computer program product is provided, which includes at least one program segment, and the at least one program segment is stored in a computer-readable storage medium; a processor of a communication device reads the at least one program segment from the computer-readable storage medium, and the processor executes the at least one program segment, so that the communication device performs the timer-based operation execution method described above.

[0025] The beneficial effects of the technical solutions provided in the embodiments of the present application include at least:

[0026] Based on time information related to GNSS measurement and / or satellite switching, a first operation is performed on the first timer to prevent the terminal device from entering an idle state during the GNSS measurement and / or satellite switching, so that the terminal device can perform data transmission as soon as possible after completing the GNSS measurement and / or satellite switching. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0028] FIG1 is a schematic diagram of a communication system provided by an exemplary embodiment of the present application;

[0029] FIG2 is a flowchart of a timer-based operation execution method provided by another exemplary embodiment of the present application;

[0030] FIG3 is a flowchart of a timer-based operation execution method provided by another exemplary embodiment of the present application;

[0031] FIG4 is a flowchart of a timer-based operation execution method provided by another exemplary embodiment of the present application;

[0032] FIG5 is a flowchart of a timer-based operation execution method provided by another exemplary embodiment of the present application;

[0033] FIG6 is a block diagram of a timer-based operation execution device provided by another exemplary embodiment of the present application;

[0034] FIG7 is a block diagram of a timer-based operation execution device provided by another exemplary embodiment of the present application;

[0035] FIG8 is a schematic structural diagram of a terminal device provided by another exemplary embodiment of the present application. DETAILED DESCRIPTION

[0036] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0037] First, the relevant technologies involved in the embodiments of this application are introduced:

[0038] (1) GNSS operation

[0039] In Release 17 (R17) Internet of Things (IoT) NTNs, that is, in scenarios where narrowband IoT (NB-IoT) and enhanced Machine-Type Communication (eMTC) are connected to the NTN, the GNSS measurement module and communication module of an IoT terminal cannot operate simultaneously. In R17 NTNs, IoT terminals can only perform GNSS measurements to obtain location information in the Radio Resource Control (RRC) idle state or RRC inactive state, and the GNSS module cannot be activated in the RRC connected state. To this end, the user equipment (UE) must first obtain its own GNSS position using the GNSS module before entering the RRC connected state. The UE can determine the validity period of the GNSS position based on its own circumstances (such as the UE's mobility) and report the remaining validity period of the GNSS position to the network during RRC connection establishment, RRC re-establishment, or RRC connection recovery. 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 uplink timing maintenance (Time Alignment, TA). Therefore, the UE needs to return to the RRC idle state.

[0040] In Release 18 (R18) IoT NTN Enhanced WID (RP-213596), the following research objectives are clearly stated:

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

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

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

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

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

[0046] At the 3GPP Radio Access Network Work Group 1 (RAN1) meeting #109, RAN1 discussed GNSS enhancements for IoT terminals connected to NTN and reached the following conclusions:

[0047] 1. IoT NTN UE may need to reacquire a valid GNSS measurement position during an RRC connection with a long duration.

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

[0049] Method 1: The terminal device reacquires the GNSS measurement position based on timer control.

[0050] Method 2: A new gap is introduced, during which the terminal device reacquires the GNSS measurement position.

[0051] 3. For triggering connected GNSS measurements, consider:

[0052] GNSS measurements triggered by terminal devices;

[0053] GNSS measurements triggered by network devices.

[0054] (2) Satellite hard switching

[0055] For a semi-static (Quasi-Earth Fixed) cell, the ground coverage position of a low-orbit mobile satellite is fixed for a period of time. Terminal devices may need to face satellite handover scenarios while in the RRC connected state. For example, as the current satellite's elevation angle of ground coverage gradually decreases as it moves, at a certain moment the current satellite will no longer provide coverage for the current area. At this time, another new satellite may take over coverage of the current area, and the new satellite may be connected to the same ground gateway. From the terminal device's perspective, the two satellites have the same physical cell identifier (PCI) and frequency. To avoid co-frequency interference between the previous and next satellites, a hard handover between satellites is more practical. That is, the terminal device disconnects from the current satellite first and then establishes a connection with the new satellite.

[0056] (3) Radio Link Monitoring (RLM)

[0057] RLM is used to monitor the channel quality of the serving cell's downlink. The physical layer evaluates the radio link quality within a specified timeframe and compares it with the Qin and Qout thresholds. If the quality is below the Qout threshold, the physical layer reports an out-of-sync indication to higher layers; if it is above the Qin threshold, the physical layer reports an in-sync indication to higher layers. The Qin and Qout thresholds are determined by monitoring the Block Error Rate (BLER) of the Physical Downlink Control Channel (PDCCH) format 1-0. The BLER values ​​corresponding to Qin and Qout are configured through RRC signaling. The BLER value corresponding to the Qout threshold is 10%, and the BLER corresponding to the Qin threshold is 2%.

[0058] The network-side UE downlink desynchronization determination involves the following timers and constants: N310, T310, and N311. These timer and constant parameters can be configured to the UE via dedicated signaling. If not configured, the system broadcast parameters are used.

[0059] When the UE is in the RRC connected state and receives the maximum number of "out_of_Sync" times indicated by the first parameter N310, and the T310, T301, T304, and T311 timers are not running, the T310 timer is started. If the UE receives the maximum number of "in_Sync" times indicated by the second parameter N311, the T310 timer is stopped, indicating that the UE has recovered downlink synchronization. Otherwise, the UE is in the downlink out-of-sync state.

[0060] The Data Inactivity Timer is used to control the inactive operation of data. This parameter is configured in the RRC connected state in seconds (s). The start of the Data Inactivity Timer is controlled by the Media Access Control (MAC) layer. When the MAC sends or receives a dedicated traffic channel (DTCH), a dedicated control channel (DCCH), or a common control channel (CCCH), the Data Inactivity Timer will be started or restarted. If the Data Inactivity Timer times out, the MAC layer notifies the RRC layer that the Data Inactivity Timer has timed out, and the terminal device leaves the connected state and enters the idle state.

[0061] (4) Radio Resource Management (RRM) Measurements for Non-Connected UEs

[0062] A terminal device in a non-connected state needs to perform RRM measurements on the serving cell and other neighboring cells based on network configuration to support mobility operations, such as cell reselection.

[0063] The measurement of the serving cell by the UE in the non-connected state is carried out continuously. In Release 14 (R14) NB-IoT, a neighboring cell measurement relaxation mechanism for stationary terminal devices is introduced to further meet the power saving needs of the terminal devices. The measurement relaxation criteria are introduced for the relaxation of neighboring cell measurements. The network will configure the evaluation duration (T Search Delta P) of the narrowband reference signal received power (Narrowband Reference Signal Received Power, NRSRP) change and the reference signal received power (Reference Signal Received Power, RSRP) change value threshold (S Search Delta P). When the RSRP change of the UE on the serving cell within the evaluation duration is less than the change value threshold, the UE is considered to meet the measurement relaxation criteria. That is: within T Search Delta P, it meets:

[0064] (SrxlevRef–Srxlev)

[0065] Where Srxlev is the currently selected received level measurement value of the serving cell, and SrxlevRef is the reference Srxlev value of the serving cell.

[0066] ​When the UE selects or reselects a new cell, or (Srxlev-SrxlevRef)>0, or the UE does not meet (SrxlevRef–Srxlev) within T Search Delta P

[0067] After completing cell selection / reselection, the UE needs to perform normal RRM measurements for at least the evaluation duration. When the UE meets the measurement relaxation criteria, the UE's measurement interval for neighboring cells can be increased to 24 hours.

[0068] (5) RRM measurement of connected UE

[0069] In versions before R17, NB-IoT UE does not support RRM measurement in connected state. When the channel quality of the connected NB-IoT on the serving cell deteriorates, mobility management is performed through the Radio Link Failure (RLF) and RRC reconstruction process. After the UE triggers RLF, it is necessary to first select a suitable cell through search and measurement, and then initiate RRC connection reconstruction on the cell. In order to save the time of selecting the reconstructed cell after the UE triggers RLF, R17 introduces a neighboring cell measurement mechanism for connected UEs for NB-IoT UEs. For neighboring cell measurements of connected UEs, the network will configure the s-measure criterion through system messages, and the network can also configure the UE mobility status evaluation criterion. The UE determines whether to perform neighboring cell measurements based on the s-measure criterion and the UE mobility status evaluation criterion. The method is as follows:

[0070] When the UE enters the RRC connected state, if the network configures the UE mobility status assessment criteria, then:

[0071] Set NRSRP Ref to the most recently measured NRSRP of the serving cell used for cell selection or reselection;

[0072] If the UE does not meet the neighbor cell measurement relaxation criteria before entering the RRC connected state, the UE starts the T326 timer.

[0073] For a UE in a connected state, assuming that the measurement result of the UE on the measured carrier is NRSRP, if the network is configured with UE mobility status assessment criteria, then:

[0074] ​If (NRSRP Ref – (NRSRP – Power Offset Non Anchor)) > s-Measure Delta P, the UE sets NRSRP Ref = NRSRP - Power Offset Non Anchor, and at the same time the UE starts or restarts the T326 timer.

[0075] If the network does not configure the UE mobility state evaluation criterion, or T326 is running, then:

[0076] If (NRSRP - Power Offset Non Anchor) < s-Measure Intra, the UE performs measurements on the same-frequency neighboring cells.

[0077] If (NRSRP - Power Offset Non Anchor) < s-Measure Inter, the UE performs measurements on the different-frequency neighboring cells.

[0078] FIG. 1 shows a schematic diagram of a communication system provided by an exemplary embodiment of the present application. The communication system includes a communication satellite 101, a network device 102, and a terminal device 103.

[0079] The communication satellite 101 in the present application provides communication services to ground users (such as the network device 102 and the terminal device 103) through satellite communication. The communication satellite 101 is classified into low-Earth orbit (LEO) satellites, medium-Earth orbit (MEO) satellites, geostationary Earth orbit (GEO) satellites, high elliptical orbit (HEO) satellites, etc. according to different orbital heights. The communication satellites 101 considered in 3GPP include two types: one is a transparent repeater satellite, and the other is a regenerative repeater satellite.

[0080] The network device 102 in the present application provides wireless communication functions, and the network device 102 includes but is not limited to: Evolved Node B (eNB), Radio Network Controller (RNC), Node B (NB), Base Station Controller (BSC), Base Transceiver Station (BTS), Home Base Station (e.g., Home Evolved Node B, or Home Node B, HNB), Baseband Unit (BBU), Access Point (AP) in Wireless Fidelity (Wi-Fi) system, Wireless Relay Node, Wireless Backhaul Node, Transmission Point (TP) or Transmission and Reception Point (TRP), etc., and can also be the Next Generation Node B (NGNB) in the fifth generation (5G) mobile communication system. B, gNB) or transmission point (TRP or TP), or one or a group of (including multiple antenna panels) antenna panels of a base station in a 5G system, or it can also be a network node constituting a gNB or transmission point, such as a baseband unit (BBU) or a distributed unit (DU), or a base station in a Beyond Fifth Generation (B5G) or a Sixth Generation (6G) mobile communication system, or a core network (CN), fronthaul (Fronthaul), backhaul (Backhaul), radio access network (RAN), network slicing, or a serving cell, primary cell (PCell), primary secondary cell (PSCell), special cell (SpCell), secondary cell (SCell), neighboring cell, etc. of a terminal device.

[0081] The terminal device 103 in this application is also called UE, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, and user device. The terminal devices include, but are not limited to, handheld devices, wearable devices, vehicle-mounted devices, and Internet of Things devices, such as mobile phones, tablet computers, e-book readers, laptop computers, desktop computers, televisions, game consoles, mobile Internet devices (MIDs), augmented reality (AR) terminals, virtual reality (VR) terminals, and mixed reality (MR) terminals, wearable devices, handles, electronic tags, controllers, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, wireless terminals in remote medical surgery, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loops (WLANs), and wireless terminals in smart cities. Loop (WLL) stations, personal digital assistants (PDA), TV set-top boxes (STB), customer premises equipment (CPE), etc.

[0082] Network device 102 and terminal device 103 communicate with each other via an air interface technology, such as a Uu interface. For example, there are two communication scenarios between network device 102 and terminal device 103: uplink communication and downlink communication. Uplink communication refers to sending signals to network device 102; downlink communication refers to sending signals to terminal device 103.

[0083] The technical solutions provided in 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, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Advanced Long Term Evolution (LTE-A) system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, fifth generation (5G) mobile communication system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-based access to unlicensed spectrum). 5G NR system, ...The embodiments of the present application are described by taking the application in the NTN system as an example.

[0084] The technical solutions provided in the embodiments of the present application can also be applied to machine type communication (MTC), long term evolution technology for machine-to-machine communication (LTE-M), device-to-device (D2D) networks, machine-to-machine (M2M) networks, IoT networks or other networks. Among them, IoT networks can include, for example, the Internet of Vehicles. Among them, the communication methods in the Internet of Vehicles system are collectively referred to as vehicle to other devices (Vehicle to X, V2X, X can represent anything), for example, the V2X can include: vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian communication (V2P) or vehicle to network (V2N) communication, etc.

[0085] The communication system provided in this embodiment can be applied to, but is not limited to, at least one of the following communication scenarios: an uplink communication scenario, a downlink communication scenario, and a sidelink communication scenario.

[0086] In the related art, during GNSS measurement and / or satellite switching, the communication between the terminal device and the current cell is in an interrupted state. In one example, if the timer for judging RLF (e.g., T310 timer) times out during GNSS measurement and / or satellite switching, the terminal device deems that RLF occurs at this time and needs to perform RRC connection reestablishment according to the relevant protocol, which may cause the terminal device to still perform RRC connection reestablishment after completing GNSS measurement and / or completing satellite switching, thereby causing the terminal device to be unable to transmit data in a timely manner after completing GNSS measurement and / or completing satellite switching. In an example, if the timer for judging leaving the connected state and entering the idle state (e.g., data inactive state timer) times out during GNSS measurement and / or satellite switching, the terminal device must leave the connected state and return to the idle state according to the relevant protocol, and the terminal device must re-establish the RRC connection after completing GNSS measurement and / or completing satellite switching, which not only causes the terminal device to consume more power, but also makes the terminal device unable to transmit data in a timely manner after completing GNSS measurement and / or completing satellite switching. In one example, if the timer used to start connected state neighbor cell measurement (e.g., T326 timer) times out during GNSS measurement and / or satellite switching, then after completing the GNSS measurement and / or completing the satellite switching, the terminal device will not start the neighbor cell measurement because the T326 timer is not running. This may result in the inability to quickly discover the RRC reconstructed cell in the event of RLF, making it impossible for the terminal device to transmit data in a timely manner after completing the GNSS measurement and / or completing the satellite switching.

[0087] In response to the above problems, the present application proposes a timer-based operation execution method, which is described below.

[0088] FIG2 is a flow chart of a timer-based operation execution method provided by an exemplary embodiment of the present application. The method is executed by a terminal device and includes:

[0089] Step 120: Based on the first time information, perform a first operation on the first timer.

[0090] When the first time information is acquired, a first operation is performed on the first timer.

[0091] In some embodiments, the first time information is time information related to GNSS measurement and / or satellite handover. In some embodiments, the first time information is time information related to the start or initiation of GNSS measurement. In some embodiments, the first time information is time information related to the start or initiation of satellite handover. Optionally, the satellite handover includes at least one of a satellite soft handover and a satellite hard handover.

[0092] In one example, the satellite switching includes satellite hard switching. During the satellite hard switching, in order to avoid co-frequency interference between the two communication satellites before and after the switching, the terminal device needs to first disconnect from the current communication satellite and then establish a new connection with the new communication satellite during the satellite hard switching.

[0093] In some embodiments, the first time information includes at least one of the following first times:

[0094] The time when the GNSS measurement was performed;

[0095] The time when GNSS information expires;

[0096] The start time of the GNSS measurement gap;

[0097] The start time of satellite switching.

[0098] In some embodiments, the start time of the satellite switching is indicated by a network device (such as a base station or a core network device).

[0099] The network device indicates the start time of satellite switching in at least one of the following ways:

[0100] System message broadcast;

[0101] RRC dedicated signaling;

[0102] MAC Control Element (CE);

[0103] PDCCH.

[0104] It should be understood that the time when the terminal device performs the first operation is consistent with or synchronized with the first time. Generally, due to a certain time delay under objective conditions, the time when the first operation is performed may be slightly later than the first time.

[0105] In some embodiments, the first timer is a timer that triggers interruption of communication between the terminal device and the satellite when it times out.

[0106] In some embodiments, the first timer includes at least one of the following:

[0107] A timer for determining RLF;

[0108] A timer used to determine whether to leave the connected state and enter the idle state.

[0109] In some embodiments, the timer used to determine RLF includes: a T310 timer. Optionally, when the terminal device enters the radio link detection, when the number of consecutive downlink out-of-sync indications (out of sync) received is equal to the first parameter, the start of the T310 timer will be triggered. If the number of consecutive downlink synchronization indications (in sync) received is equal to the second parameter during the continuous operation of the T310 timer, the T310 timer is stopped, indicating that the link synchronization has been restored. In the case that the T310 timer times out, it is considered that a radio link failure is detected, and the RRC connection re-establishment process will be triggered. Optionally, the first parameter includes N310. Optionally, the second parameter includes N311.

[0110] In some embodiments, the timer used to determine whether to leave the connected state and enter the idle state includes a data inactivity timer. Optionally, when the terminal device is in the connected state after sending data, it starts the data inactivity timer. When the data inactivity timer expires, the terminal device leaves the connected state and enters the idle state.

[0111] In some embodiments, the first operation is an operation for preventing interruption of communication between the terminal device and the satellite. In some embodiments, the first operation is an operation for preventing the terminal device from continuing to run a first timer during a period related to GNSS measurement and / or satellite switching.

[0112] In some embodiments, the first operation includes:

[0113] Stop the first timer; or,

[0114] Pause the first timer.

[0115] In one example, based on the first time information, the T310 timer and / or the data inactivity timer are directly stopped. Optionally, "directly stopping" can be understood as canceling the first timer or setting the count value of the first timer to 0.

[0116] In one example, based on the first time information, the T310 timer and / or the data inactivity timer are paused. Optionally, "pause" can be understood as keeping the count value of the first timer unchanged and not increasing or decreasing the count value of the first timer.

[0117] In some embodiments, the timer for determining RLF is stopped at the moment the GNSS measurement is performed.

[0118] In some embodiments, at the moment of performing GNSS measurement, the timer for determining RLF is suspended.

[0119] In some embodiments, when the GNSS measurement is performed, the timer for deciding whether to leave the connected state and enter the idle state is stopped.

[0120] In some embodiments, when the GNSS measurement is performed, the timer for deciding whether to leave the connected state and enter the idle state is paused.

[0121] In some embodiments, when the GNSS information expires, the timer for determining RLF is stopped.

[0122] In some embodiments, when the GNSS information expires, the timer for determining RLF is suspended.

[0123] In some embodiments, when the GNSS information expires, the timer used to determine whether to leave the connected state and enter the idle state is stopped.

[0124] In some embodiments, when the GNSS information expires, the timer used to determine whether to leave the connected state and enter the idle state is suspended.

[0125] In some embodiments, at the start of a GNSS measurement gap, a timer for determining RLF is stopped.

[0126] In some embodiments, at the start of a GNSS measurement gap, a timer for determining RLF is paused.

[0127] In some embodiments, at the start time of the GNSS measurement gap, the timer for deciding to leave the connected state and enter the idle state is stopped.

[0128] In some embodiments, at the start of a GNSS measurement gap, a timer for determining whether to leave the connected state and enter the idle state is paused.

[0129] In some embodiments, at the start of satellite handover, the timer for determining RLF is stopped.

[0130] In some embodiments, at the start of satellite handover, the timer for determining RLF is paused.

[0131] In some embodiments, at the start of satellite handover, a timer for determining whether to leave the connected state and enter the idle state is stopped.

[0132] In some embodiments, at the start of satellite handover, a timer for determining whether to leave the connected state and enter the idle state is paused.

[0133] It is worth noting that the above embodiments can be further combined to form new embodiments.

[0134] In some embodiments, the T310 timer needs to count continuously until a threshold is reached before it starts and / or stops. In this case, it is recommended to stop the T310 timer immediately so that it can count continuously again after it is restarted. In this case, the working mechanism of the T310 timer is more in line with the original design of the T310 timer.

[0135] In some embodiments, the data inactive state timer is used to time the data transmission duration of the terminal device to determine whether it has entered the idle state from the connected state. Since stopping the data inactive state timer will clear the time that has been counted, it is recommended to pause the data inactive state timer as soon as possible to retain the time that has been counted.

[0136] In some embodiments, when the GNSS measurement is performed, the T310 timer is stopped; and when the GNSS measurement is performed, the data inactivity timer is paused.

[0137] In some embodiments, at the start of satellite switching, the T310 timer is stopped; and at the start of satellite switching, the data inactivity timer is paused.

[0138] In summary, the embodiment of the present application performs a first operation on the first timer based on time information related to GNSS measurement and / or satellite switching, so that the terminal device avoids entering an idle state during GNSS measurement and / or satellite switching. On the one hand, during GNSS measurement and / or satellite switching, the terminal device will not consider that RLF occurs at this time and will not trigger RRC connection reconstruction in accordance with the relevant protocol, thereby enabling the terminal device to directly perform data transmission after completing GNSS measurement and / or satellite switching, avoiding data transmission delay caused by performing RRC connection reconstruction; on the other hand, during GNSS measurement and / or satellite switching, the terminal device avoids entering an idle state in accordance with the relevant protocol, and the terminal device does not need to consume more power to reestablish the RRC connection after completing GNSS measurement and / or satellite switching, and can also avoid the situation where data transmission delay caused by performing RRC connection reconstruction, thereby enabling the terminal device to perform data transmission as soon as possible after completing GNSS measurement and / or satellite switching.

[0139] In the case where the first timer is a timer for determining RLF (e.g., a T310 timer), an embodiment of the present application enables the terminal device to not trigger RRC connection reconstruction during GNSS measurement and / or satellite switching, and the terminal device remains in the RRC connection state after completing the GNSS measurement and / or completing the satellite switching. Therefore, the terminal device can transmit data as soon as possible after completing the GNSS measurement and / or completing the satellite switching.

[0140] In the case where the first timer is a timer for determining whether to leave the connected state and enter the idle state (for example, a data inactive state timer), an embodiment of the present application enables the terminal device to not trigger the process of leaving the connected state and entering the idle state during GNSS measurement and / or satellite switching. The terminal device remains in the RRC connected state after completing the GNSS measurement and / or completing the satellite switching, so the terminal device can transmit data as soon as possible after completing the GNSS measurement and / or completing the satellite switching.

[0141] In some embodiments, based on the first operation performed by the terminal device on the first timer based on the first time information, the terminal device correspondingly performs a second operation on the second timer based on the second time information. In some embodiments, the second time information corresponds to the first time information. For example, the first time information corresponds to the start time of the GNSS measurement, and the second time information corresponds to the end time of the GNSS measurement. However, it should be noted that this embodiment can operate independently.

[0142] FIG3 is a flow chart of a timer-based operation execution method provided by an exemplary embodiment of the present application. The method is executed by a terminal device and includes:

[0143] Step 220: Based on the second time information, perform a second operation on the second timer.

[0144] When the second time information is acquired, a second operation is performed on the second timer.

[0145] In some embodiments, the second time information is time information related to GNSS measurement and / or satellite handover. In some embodiments, the second time information is time information related to the end or cessation of GNSS measurement. In some embodiments, the second time information is time information related to the end or cessation of satellite handover. Optionally, the satellite handover includes at least one of a satellite soft handover and a satellite hard handover.

[0146] In one example, the satellite switching includes satellite hard switching. During the satellite hard switching, in order to avoid co-frequency interference between the two communication satellites before and after the switching, the terminal device needs to first disconnect from the current communication satellite and then establish a new connection with the new communication satellite during the satellite hard switching.

[0147] In some embodiments, the second time information includes at least one of the following second times:

[0148] The time when the GNSS measurement is completed;

[0149] The time when the GNSS measurement results were obtained;

[0150] End time of the GNSS measurement gap;

[0151] The moment when satellite switching is completed.

[0152] In some embodiments, the second time information corresponds to the first time information. In one example, the time when the GNSS measurement is completed corresponds to the time when the GNSS measurement is performed. In one example, the time when the GNSS measurement result is obtained corresponds to the time when the GNSS information expires. In one example, the time when a GNSS measurement gap ends corresponds to the time when the GNSS measurement gap begins. In one example, the time when a satellite handoff is completed corresponds to the time when the satellite handoff begins.

[0153] In some embodiments, the start time of the satellite switching is indicated by a network device (such as a base station or a core network device).

[0154] The network device indicates the start time of satellite switching in at least one of the following ways:

[0155] System message broadcast;

[0156] RRC dedicated signaling;

[0157] MAC CE;

[0158] PDCCH.

[0159] It should be understood that the time when the terminal device performs the second operation is consistent with or synchronized with the second time. Generally, due to a certain time delay under objective conditions, the time when the second operation is performed may be slightly later than the second time.

[0160] In some embodiments, the second timer is a timer that triggers interruption of communication between the terminal device and the satellite when it times out.

[0161] In some embodiments, the second timer includes at least one of the following:

[0162] A timer for determining RLF;

[0163] A timer used to start connected neighbor cell measurements;

[0164] A timer used to determine whether to leave the connected state and enter the idle state.

[0165] In some embodiments, the timer used to determine RLF includes: a T310 timer. Optionally, when the terminal device enters the radio link detection, when the number of consecutive downlink out-of-sync indications (out of sync) received is equal to the first parameter, the start of the timer T310 will be triggered. If the number of consecutive downlink synchronization indications (in sync) received is equal to the second parameter during the continuous operation of the T310 timer, the T310 timer is stopped, indicating that the link synchronization has been restored. In the case that the T310 timer times out, it is considered that a radio link failure is detected, and the RRC connection re-establishment process will be triggered. Optionally, the first parameter includes N310. Optionally, the second parameter includes N311.

[0166] In some embodiments, the timer for starting the connected state neighbor cell measurement includes: a T326 timer. The terminal device will start the neighbor cell measurement only when the T326 timer is running.

[0167] In some embodiments, the timer used to determine whether to leave the connected state and enter the idle state includes a data inactivity timer. Optionally, when the terminal device is in the connected state after sending data, it starts the data inactivity timer. When the data inactivity timer expires, the terminal device leaves the connected state and enters the idle state.

[0168] In some embodiments, the second operation is used to restore the impact of the first operation on the normal operation of the timer. In some embodiments, the second operation is used to restore the impact of the first operation on the normal operation of the timer during a time period other than that related to GNSS measurement and / or satellite handover. In some embodiments, the second operation is used to trigger the terminal device to continue running the first timer during a time period other than that related to GNSS measurement and / or satellite handover.

[0169] In some embodiments, the second operation includes:

[0170] Start a second timer; or,

[0171] Resume the second timer.

[0172] In one example, the T310 timer is directly stopped based on the first time information, and then the T310 timer is restarted based on the second time information. Optionally, "directly stopping" can be understood as canceling the T310 timer or setting the count value of the T310 timer to 0. Optionally, "restarting" can be understood as re-running the T310 timer or re-increasing or decreasing the count value of the T310 timer.

[0173] In one example, the T310 timer is paused based on the first time information, and then resumed based on the second time information. Optionally, "pause" can be understood as leaving the count value of the T310 timer unchanged and not increasing or decreasing the count value of the T310 timer. Optionally, "resume" can be understood as increasing or decreasing the count value of the T310 timer from the original value.

[0174] In one example, the data inactivity timer is directly stopped based on the first time information, and then restarted based on the second time information. Alternatively, "directly stopping" can be understood as canceling the data inactivity timer or setting the count value of the data inactivity timer to 0. Alternatively, "restarting" can be understood as re-running the data inactivity timer or re-increasing or decrementing the count value of the data inactivity timer.

[0175] In one example, the data inactivity timer is paused based on the first time information, and then resumed based on the second time information. Alternatively, "pause" can be understood as leaving the count value of the data inactivity timer unchanged and not increasing or decreasing the count value of the data inactivity timer. Alternatively, "resume" can be understood as increasing or decreasing the count value of the data inactivity timer from its original value.

[0176] In one example, based on the second time information, the T326 timer is started. Optionally, "starting" can be understood as running the T326 timer, or re-increasing or reducing the count value of the T326 timer.

[0177] In some embodiments, a timer for determining RLF is started when the GNSS measurement is completed.

[0178] In some embodiments, the timer for determining RLF is resumed at the moment the GNSS measurement is completed.

[0179] In some embodiments, when the GNSS measurement is completed, a timer for starting the connected state neighbor cell measurement is started.

[0180] In some embodiments, when the GNSS measurement is completed, a timer for deciding whether to leave the connected state and enter the idle state is started.

[0181] In some embodiments, when the GNSS measurement is completed, the timer for deciding to leave the connected state and enter the idle state is resumed.

[0182] In some embodiments, a timer for determining RLF is started at the moment of acquiring the GNSS measurement result.

[0183] In some embodiments, the timer for determining RLF is resumed at the moment of acquiring the GNSS measurement result.

[0184] In some embodiments, at the moment of acquiring the GNSS measurement result, a timer for starting the connected state neighbor cell measurement is started.

[0185] In some embodiments, when the GNSS measurement result is obtained, a timer for determining whether to leave the connected state and enter the idle state is started.

[0186] In some embodiments, at the moment of acquiring the GNSS measurement result, the timer for deciding whether to leave the connected state and enter the idle state is resumed.

[0187] In some embodiments, at the end of the GNSS measurement gap, a timer for determining RLF is started.

[0188] In some embodiments, at the end of the GNSS measurement gap, the timer for determining RLF is resumed.

[0189] In some embodiments, at the end of the GNSS measurement gap, a timer for starting connected state neighbor cell measurement is started.

[0190] In some embodiments, at the end of the GNSS measurement gap, a timer for determining whether to leave the connected state and enter the idle state is started.

[0191] In some embodiments, at the end of the GNSS measurement gap, the timer for deciding to leave the connected state and enter the idle state is resumed.

[0192] In some embodiments, a timer for determining RLF is started at the moment when satellite switching is completed.

[0193] In some embodiments, at the completion moment of satellite handover, the timer for determining RLF is resumed.

[0194] In some embodiments, at the moment of completion of satellite handover, a timer for starting connected state neighbor measurement is started.

[0195] In some embodiments, when the satellite handover is completed, a timer for determining whether to leave the connected state and enter the idle state is started.

[0196] In some embodiments, at the moment when the satellite handover is completed, the timer for determining whether to leave the connected state and enter the idle state is restored.

[0197] It is worth noting that the above embodiments can be further combined to form new embodiments.

[0198] In some embodiments, the T310 timer needs to count continuously until a threshold is reached before it starts and / or stops. Therefore, it is recommended to stop the T310 timer immediately so that it can resume counting after it is restarted. In this case, the T310 timer's operating mechanism is more consistent with the original design intent of the T310 timer. If the T310 timer is stopped at the first time, it is started at the second time.

[0199] In some embodiments, the data inactivity timer is used to measure the duration of data transmission by the terminal device to determine whether the terminal device has entered the idle state from the connected state. Since stopping the data inactivity timer will reset the elapsed time, it is recommended to immediately pause the data inactivity timer to retain the elapsed time. If the data inactivity timer is paused at the first time, it should be resumed at the second time.

[0200] In some embodiments, when the GNSS measurement is completed, the T310 timer is started; and when the GNSS measurement is completed, the data inactivity timer is resumed.

[0201] In some embodiments, at the moment of completion of the satellite handover, the T310 timer is started; and at the moment of completion of the satellite handover, the data inactivity timer is resumed.

[0202] To sum up, the embodiment of the present application performs a second operation on the second timer based on time information related to GNSS measurement and / or satellite switching, so that the terminal device resumes the operation of the timer after completing the GNSS measurement and / or satellite switching, avoiding the situation where the timer cannot operate normally after communication is restored.

[0203] FIG4 is a flow chart of a timer-based operation execution method provided by an exemplary embodiment of the present application. The method is executed by a terminal device and includes:

[0204] Step 320: When the first timer times out within the first time period, the third operation is not performed.

[0205] In some embodiments, the first time period is a time period associated with GNSS measurement and / or satellite handover. In some embodiments, the first time period is a time period associated with the start and end of GNSS measurement, or a time period associated with the start and stop of GNSS measurement. In some embodiments, the first time period is a time period associated with the start and end of satellite handover, or a time period associated with the start and stop of satellite handover. Optionally, the satellite handover includes at least one of a satellite soft handover and a satellite hard handover.

[0206] In one example, the satellite switching includes satellite hard switching. During the satellite hard switching, in order to avoid co-frequency interference between the two communication satellites before and after the switching, the terminal device needs to first disconnect from the current communication satellite and then establish a new connection with the new communication satellite during the satellite hard switching.

[0207] In some embodiments, the first time period is a time period from the first time to the second time.

[0208] The first time includes at least one of the following:

[0209] The time when the GNSS measurement was performed;

[0210] The time when GNSS information expires;

[0211] The start time of the GNSS measurement gap;

[0212] The start time of satellite switching.

[0213] The second time includes at least one of the following:

[0214] The time when the GNSS measurement is completed;

[0215] The time when the GNSS measurement results were obtained;

[0216] End time of the GNSS measurement gap;

[0217] The moment when satellite switching is completed.

[0218] In some embodiments, there is a corresponding relationship between the first time and the second time.

[0219] In one example, the first time period is a time period from performing the GNSS measurement to completing the GNSS measurement.

[0220] In one example, the first time period is a time period from when the GNSS information expires to when the GNSS measurement result is acquired.

[0221] In one example, the first time period is a time period from the start of the GNSS measurement gap to the end of the GNSS measurement gap.

[0222] In one example, the first time period is a time period from the start of satellite switching to the completion of satellite switching.

[0223] In some embodiments, the start time of the satellite switching is indicated by a network device (such as a base station or a core network device).

[0224] The network device indicates the start time of satellite switching in at least one of the following ways:

[0225] System message broadcast;

[0226] RRC dedicated signaling;

[0227] MAC CE;

[0228] PDCCH.

[0229] In some embodiments, the third operation is an operation related to interruption of communication between the terminal device and the satellite.

[0230] In some embodiments, the first timer includes a timer for determining RLF. If the timer for determining RLF times out within the first time period, the third operation includes triggering RLF and / or performing RRC connection reestablishment. That is, if the timer for determining RLF times out within the first time period, RLF is not triggered and / or RRC connection reestablishment is not performed.

[0231] In some embodiments, the timer used to determine RLF includes: a T310 timer. Optionally, when the terminal device enters the radio link detection, when the number of consecutive downlink out-of-sync indications (out of sync) received is equal to the first parameter, the start of the timer T310 will be triggered. If the number of consecutive downlink synchronization indications (in sync) received is equal to the second parameter during the continuous operation of the T310 timer, the T310 timer is stopped, indicating that the link synchronization has been restored. In the case that the T310 timer times out, it is considered that a radio link failure is detected, and the RRC connection re-establishment process will be triggered. Optionally, the first parameter includes N310. Optionally, the second parameter includes N311.

[0232] In some embodiments, the first timer includes a timer for determining whether to leave the connected state and enter the idle state. If the timer for determining whether to leave the connected state and enter the idle state times out within a first time period, the third operation includes entering the idle state. That is, if the timer for determining whether to leave the connected state and enter the idle state times out within the first time period, the idle state is not entered.

[0233] In some embodiments, the timer used to determine whether to leave the connected state and enter the idle state includes a data inactivity timer. Optionally, when the terminal device is in the connected state after sending data, it starts the data inactivity timer. When the data inactivity timer expires, the terminal device leaves the connected state and enters the idle state.

[0234] In summary, the embodiment of the present application is based on a time period related to GNSS measurement and / or satellite switching, and when the first timer times out within the time period related to GNSS measurement and / or satellite switching, the third operation is not performed. On the one hand, during the GNSS measurement and / or satellite switching period, the terminal device does not perform RRC connection reestablishment, thereby enabling the terminal device to directly perform data transmission after completing the GNSS measurement and / or completing the satellite switching, avoiding data transmission delays caused by performing RRC connection reestablishment; on the other hand, during the GNSS measurement and / or satellite switching period, the terminal device avoids entering an idle state, thereby not consuming more power to reestablish the RRC connection after completing the GNSS measurement and / or completing the satellite switching, and can also avoid data transmission delays caused by performing RRC connection reestablishment, thereby enabling the terminal device to perform data transmission as soon as possible after completing the GNSS measurement and / or satellite switching.

[0235] In the case where the first timer is a timer for determining RLF (e.g., a T310 timer), an embodiment of the present application enables the terminal device to not trigger RRC connection reconstruction during GNSS measurement and / or satellite switching, and the terminal device remains in the RRC connection state after completing the GNSS measurement and / or completing the satellite switching. Therefore, the terminal device can transmit data as soon as possible after completing the GNSS measurement and / or completing the satellite switching.

[0236] In the case where the first timer is a timer for determining whether to leave the connected state and enter the idle state (for example, a data inactive state timer), an embodiment of the present application enables the terminal device to not trigger the process of leaving the connected state and entering the idle state during GNSS measurement and / or satellite switching. The terminal device remains in the RRC connected state after completing the GNSS measurement and / or completing the satellite switching, so the terminal device can transmit data as soon as possible after completing the GNSS measurement and / or completing the satellite switching.

[0237] In some embodiments, if the first timer times out outside the first time period, as shown in FIG5 , the method further includes:

[0238] Step 340: When the first timer times out outside the first time period, perform a third operation.

[0239] In some embodiments, the first time period is a time period associated with GNSS measurement and / or satellite handover. In some embodiments, the first time period is a time period associated with the start and end of GNSS measurement, or a time period associated with the start and stop of GNSS measurement. In some embodiments, the first time period is a time period associated with the start and end of satellite handover, or a time period associated with the start and stop of satellite handover. Optionally, the satellite handover includes at least one of a satellite soft handover and a satellite hard handover.

[0240] In one example, the satellite switching includes satellite hard switching. During the satellite hard switching, in order to avoid co-frequency interference between the two communication satellites before and after the switching, the terminal device needs to first disconnect from the current communication satellite and then establish a new connection with the new communication satellite during the satellite hard switching.

[0241] In some embodiments, the first time period is a time period from the first time to the second time.

[0242] The first time includes at least one of the following:

[0243] The time when the GNSS measurement was performed;

[0244] The time when GNSS information expires;

[0245] The start time of the GNSS measurement gap;

[0246] The start time of satellite switching.

[0247] The second time includes at least one of the following:

[0248] The time when the GNSS measurement is completed;

[0249] The time when the GNSS measurement results were obtained;

[0250] End time of the GNSS measurement gap;

[0251] The moment when satellite switching is completed.

[0252] In some embodiments, there is a corresponding relationship between the first time and the second time.

[0253] In one example, the first time period is a time period from performing the GNSS measurement to completing the GNSS measurement.

[0254] In one example, the first time period is a time period from when the GNSS information expires to when the GNSS measurement result is acquired.

[0255] In one example, the first time period is a time period from the start of the GNSS measurement gap to the end of the GNSS measurement gap.

[0256] In one example, the first time period is a time period from the start of satellite switching to the completion of satellite switching.

[0257] In some embodiments, the start time of the satellite switching is indicated by a network device (such as a base station or a core network device).

[0258] The network device indicates the start time of satellite switching in at least one of the following ways:

[0259] System message broadcast;

[0260] RRC dedicated signaling;

[0261] MAC CE;

[0262] PDCCH.

[0263] In some embodiments, the third operation is an operation related to interruption of communication between the terminal device and the satellite.

[0264] In some embodiments, the first timer includes a timer for determining RLF. If the timer for determining RLF times out outside the first time period, the third operation includes triggering RLF and / or performing RRC connection reestablishment. That is, if the timer for determining RLF times out outside the first time period, RLF is triggered and / or RRC connection reestablishment is performed.

[0265] In some embodiments, the timer used to determine RLF includes: a T310 timer. Optionally, when the terminal device enters the radio link detection, when the number of downlink out-of-sync indications (out of sync) received consecutively is equal to the first parameter, the start of the timer T310 timer is triggered. If, while the T310 timer is running continuously, the number of downlink synchronization indications (in sync) received consecutively is equal to the second parameter, the T310 timer is stopped, indicating that the link synchronization has been restored. In the case that the T310 timer times out, it is considered that a radio link failure is detected, and the RRC connection re-establishment process will be triggered. Optionally, the first parameter includes N310. Optionally, the second parameter includes N311.

[0266] In some embodiments, the first timer includes a timer for determining whether to leave the connected state and enter the idle state. If the timer for determining whether to leave the connected state and enter the idle state times out outside the first time period, the third operation includes entering the idle state. That is, if the timer for determining whether to leave the connected state and enter the idle state times out outside the first time period, the idle state is entered.

[0267] In some embodiments, the timer used to determine whether to leave the connected state and enter the idle state includes a data inactivity timer. Optionally, when the terminal device is in the connected state after sending data, it starts the data inactivity timer. When the data inactivity timer expires, the terminal device leaves the connected state and enters the idle state.

[0268] In summary, the embodiment of the present application is based on a time period related to GNSS measurement and / or satellite switching, and when the first timer does not time out within the time period related to GNSS measurement and / or satellite switching, the third operation is performed. On the one hand, the terminal device does not perform RRC connection reestablishment during the GNSS measurement period and / or satellite switching period, thereby enabling the terminal device to directly transmit data after completing the GNSS measurement and / or completing the satellite switching, thereby avoiding data transmission delays caused by performing RRC connection reestablishment; on the other hand, the terminal device does not enter an idle state during the GNSS measurement period and / or during the satellite switching period, thereby eliminating the need to consume more power to reestablish the RRC connection after completing the GNSS measurement and / or completing the satellite switching, and also avoiding data transmission delays caused by performing RRC connection reestablishment.

[0269] In the case where the first timer is a timer for determining RLF (e.g., a T310 timer), an embodiment of the present application enables the terminal device to not trigger RRC connection reconstruction during GNSS measurement and / or satellite switching, and the terminal device remains in the RRC connection state after completing the GNSS measurement and / or completing the satellite switching. Therefore, the terminal device can transmit data as soon as possible after completing the GNSS measurement and / or completing the satellite switching.

[0270] In the case where the first timer is a timer for determining whether to leave the connected state and enter the idle state (for example, a data inactive state timer), an embodiment of the present application enables the terminal device to not trigger the process of leaving the connected state and entering the idle state during the GNSS measurement and / or the satellite switching. The terminal device remains in the RRC connected state after completing the GNSS measurement and / or completing the satellite switching. Therefore, the terminal device can transmit data as soon as possible after completing the GNSS measurement and / or completing the satellite switching.

[0271] Exemplary embodiment 1:

[0272] In some embodiments, the terminal device performs a first operation on a running first timer according to the first time information.

[0273] In some embodiments, the first time information includes at least one of the following first times:

[0274] The time when the GNSS measurement starts;

[0275] The time when GNSS information starts to expire;

[0276] The start time of the GNSS measurement gap;

[0277] The start time of satellite hard handover, that is, the time when the terminal device is disconnected from the current satellite, can be indicated to the terminal device by the base station through system message broadcast, RRC dedicated signaling, MAC CE, PDCCH, etc.

[0278] In some embodiments, the first timer includes at least one of the following:

[0279] A timer for determining RLF;

[0280] A timer used to determine whether to leave the connected state and enter the idle state.

[0281] In some embodiments, the first operation includes:

[0282] Stop the first timer; or,

[0283] Pause the first timer.

[0284] Exemplary embodiment 2:

[0285] In some embodiments, the terminal device performs a second operation on the second timer according to the second time information.

[0286] In some embodiments, the second time information includes at least one of the following second times:

[0287] The time when the GNSS measurement is completed;

[0288] The time when the GNSS measurement results were obtained;

[0289] End time of the GNSS measurement gap;

[0290] The completion time of satellite hard handover, that is, the time when the terminal device is disconnected from the current satellite, can be indicated to the terminal device by the base station through system message broadcast, RRC dedicated signaling, MAC CE, PDCCH, etc.

[0291] In some embodiments, the second timer includes at least one of the following:

[0292] A timer used to start connected neighbor cell measurements;

[0293] A timer used to determine whether to leave the connected state and enter the idle state.

[0294] In some embodiments, the second operation includes:

[0295] Start / restart the second timer; or,

[0296] Resume the second timer.

[0297] Exemplary embodiment three:

[0298] In some embodiments, when the T310 timer times out during GNSS measurement and / or satellite hard switching, the terminal device does not trigger the RLF or RRC connection re-establishment process; alternatively, when the T310 timer times out, if the terminal device is not performing GNSS measurement and / or no satellite hard switching occurs, the terminal device triggers the RLF or RRC connection re-establishment process.

[0299] In some embodiments, during GNSS measurement and / or during satellite hard switching, the data inactivity timer expires, and the terminal device does not enter the idle state; alternatively, when the data inactivity timer expires, if the terminal device is not performing GNSS measurement and / or no satellite hard switching occurs, the terminal device enters the idle state.

[0300] In some embodiments, the timer-based operation execution method provided in the embodiments of the present application can prevent the terminal device from triggering RRC connection reestablishment or returning to the idle state during GNSS measurement and / or satellite hard handover, so that data transmission can be carried out as soon as possible after the GNSS measurement and / or satellite hard handover is completed. In addition, starting the T326 timer after completing the GNSS measurement and / or satellite hard handover can avoid the late initiation of neighboring cell measurement and the inability to achieve early reestablishment of cell measurement due to the expiration of the T326 timer.

[0301] FIG6 is a block diagram of a timer-based operation execution device provided by another exemplary embodiment of the present application. The device can be implemented as part of a terminal device. The device includes:

[0302] An execution module 610 is configured to execute a first operation on a first timer based on the first time information;

[0303] The first time information is time information related to GNSS measurement and / or satellite switching.

[0304] The first-time information includes at least one of the following:

[0305] The time when the GNSS measurement was performed;

[0306] The time when GNSS information expires;

[0307] The start time of the GNSS measurement gap;

[0308] The start time of satellite switching.

[0309] The first timer includes at least one of the following:

[0310] A timer for determining RLF;

[0311] A timer used to determine whether to leave the connected state and enter the idle state.

[0312] The timer used to determine RLF includes the T310 timer.

[0313] The timer used to determine whether to leave the connected state and enter the idle state includes a data inactive state timer.

[0314] The first operation includes:

[0315] Stop the first timer; or,

[0316] Pause the first timer.

[0317] The execution module 610 is further configured to execute a second operation on the second timer based on the second time information;

[0318] The second time information is time information related to GNSS measurement and / or satellite switching.

[0319] The second time information includes at least one of the following:

[0320] The moment when the GNSS measurement is completed;

[0321] The time when the GNSS measurement results are obtained;

[0322] End time of the GNSS measurement gap;

[0323] The moment when satellite switching is completed.

[0324] The second timer includes at least one of the following:

[0325] A timer for determining RLF;

[0326] A timer for starting neighbor cell measurements in connected state;

[0327] A timer used to determine whether to leave the connected state and enter the idle state.

[0328] The timer used to determine RLF includes a T310 timer.

[0329] The timer for starting the connected state neighbor cell measurement includes a T326 timer.

[0330] The timer used to determine whether to leave the connected state and enter the idle state includes a data inactive state timer.

[0331] The second operation includes:

[0332] Starting a second timer; or,

[0333] Resume the second timer.

[0334] FIG7 is a block diagram of a timer-based operation execution device provided by another exemplary embodiment of the present application. The device can be implemented as part of a terminal device. The device includes:

[0335] The execution module 710 is configured to not execute the third operation if the first timer times out within the first time period; or

[0336] An execution module 710 is configured to execute a third operation when the first timer times out outside the first time period;

[0337] The first time period is a time period related to GNSS measurement and / or satellite switching.

[0338] The first timer includes a timer for determining RLF; the third operation includes: triggering RLF and / or performing RRC connection reestablishment.

[0339] The timer used to determine RLF includes the T310 timer.

[0340] The first timer includes a timer for determining whether to leave the connected state and enter the idle state; the third operation includes: entering the idle state.

[0341] The timer used to determine whether to leave the connected state and enter the idle state includes a data inactive state timer.

[0342] FIG8 shows a schematic structural diagram of a terminal device provided by an exemplary embodiment of the present application. The terminal device 80 includes: a processor 81 , a receiver 82 , a transmitter 83 , a memory 84 and a bus 85 .

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

[0344] The receiver 82 and the transmitter 83 may be implemented as a communication component, which may be a communication chip.

[0345] The memory 84 is connected to the processor 81 via a bus 85 .

[0346] The memory 84 may be used to store at least one instruction, and the processor 81 may be used to execute the at least one instruction to implement each step in the above method embodiment.

[0347] In addition, the memory 84 can be implemented by any type of volatile or non-volatile storage device or a combination thereof. Volatile or non-volatile storage devices include but are not limited to: magnetic disks or optical disks, Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Static Random-Access Memory (SRAM), Read Only Memory (ROM), magnetic memory, flash memory, and Programmable Read Only Memory (PROM).

[0348] In some embodiments, a non-transitory readable storage medium including instructions is further provided, such as a memory including instructions, wherein the instructions can be executed by a processor of a terminal device to perform the above-mentioned timer-based operation execution method. For example, the non-transitory readable storage medium can be a ROM, a random-access memory (RAM), a compact disc read-only memory (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, etc.

[0349] The present application also provides a chip, which includes a programmable logic circuit and / or program instructions. When a communication device equipped with the chip is running, it is used to implement the timer-based operation execution method provided by the above-mentioned method embodiments.

[0350] The present application also provides a computer-readable storage medium, which stores at least one instruction, at least one program, code set or instruction set, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by a processor to enable the communication device to implement the timer-based operation execution method provided by the above-mentioned method embodiments.

[0351] The present application also provides a computer program product, which includes at least one program segment, and the at least one program segment is stored in a computer-readable storage medium; the processor of the communication device reads the at least one program segment from the computer-readable storage medium, and the processor executes the at least one program segment, so that the communication device executes the timer-based operation execution method provided by the above-mentioned method embodiments.

[0352] It should be understood that the term "plurality" used herein refers to two or more. "And / or" describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. The character " / " generally indicates an "or" relationship between the associated objects.

[0353] Those skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware, or by a program to instruct the relevant hardware, and the program may be stored in a computer-readable storage medium, which may be a read-only memory, a disk, or an optical disk, etc.

[0354] The above description is merely an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A timer-based operation execution method, characterized in that: The method is executed by a terminal device, and includes: Based on the first time information, perform a first operation on the first timer; The first time information is time information related to global navigation satellite system GNSS measurement and / or satellite switching.

2. The method according to claim 1, characterized in that The first time information includes at least one of the following: The time at which the GNSS measurement is performed; The time when the GNSS information expires; The start time of the GNSS measurement gap; The starting time of the satellite switching.

3. The method according to claim 1, characterized in that The first timer includes at least one of the following: A timer used to determine a radio link failure (RLF); A timer used to determine whether to leave the connected state and enter the idle state.

4. The method according to claim 3, characterized in that The timer used to determine RLF includes a T310 timer.

5. The method according to claim 3, characterized in that: The timer used to determine whether to leave the connected state and enter the idle state includes a data inactive state timer.

6. The method according to claim 1, characterized in that The first operation includes: Stop the first timer; or, The first timer is paused.

7. The method according to claim 1, characterized in that The method further comprises: Based on the second time information, performing a second operation on the second timer; The second time information is time information related to the GNSS measurement and / or the satellite switching.

8. The method according to claim 7, characterized in that The second time information includes at least one of the following: The time when the GNSS measurement is completed; The time at which the GNSS measurement result is obtained; End time of the GNSS measurement gap; The completion time of the satellite switching.

9. The method according to claim 7, characterized in that: The second timer includes at least one of the following: A timer for determining RLF; A timer for starting connected neighbor cell measurements; A timer for determining whether to leave the connected state and enter the idle state.

10. The method according to claim 9, characterized in that The timer used to determine RLF includes a T310 timer.

11. The method according to claim 9, characterized in that The timer used to start the connected state neighbor cell measurement includes a T326 timer.

12. The method according to claim 9, characterized in that The timer used to determine whether to leave the connected state and enter the idle state includes a data inactive state timer.

13. The method according to claim 7, characterized in that The second operation includes: starting the second timer; or, The second timer is resumed.

14. A timer-based operation execution method, characterized in that: The method is executed by a terminal device, and includes: When the first timer times out within the first time period, the third operation is not performed; or, When the first timer times out outside the first time period, performing the third operation; The first time period is a time period related to GNSS measurement and / or satellite switching.

15. The method according to claim 14, characterized in that The first timer includes a timer for determining RLF; The third operation includes: triggering RLF and / or performing RRC connection reconstruction.

16. The method according to claim 15, characterized in that The timer used to determine RLF includes a T310 timer.

17. The method according to claim 14, characterized in that The first timer includes a timer for judging whether to leave the connected state and enter the idle state; The third operation includes: entering the idle state.

18. The method according to claim 17, characterized in that The timer used to determine whether to leave the connected state and enter the idle state includes a data inactive state timer.

19. A timer-based operation execution device, characterized in that: The device comprises: An execution module, configured to execute a first operation on a first timer based on the first time information; The first time information is time information related to GNSS measurement and / or satellite switching.

20. A timer-based operation execution device, characterized in that: The device comprises: an execution module, configured to not execute the third operation when the first timer times out within the first time period; or The execution module is configured to execute the third operation when the first timer times out outside the first time period; The first time period is a time period related to GNSS measurement and / or satellite switching.

21. A chip, characterized in that: The chip includes a programmable logic circuit and / or program instructions, and when a communication device equipped with the chip is running, it is used to implement the timer-based operation execution method as described in any one of claims 1 to 13 and the timer-based operation execution method as described in any one of claims 14 to 18.

22. A terminal device, characterized in that: The terminal device comprises: processor; a transceiver connected to the processor; a memory for storing executable instructions for the processor; The processor is configured to load and execute the executable instructions to implement the timer-based operation execution method according to any one of claims 1 to 13 and the timer-based operation execution method according to any one of claims 14 to 18.

23. A computer-readable storage medium, characterized in that: The storage medium stores at least one program, and the at least one program is loaded and executed by the processor so that the communication device executes the timer-based operation execution method as described in any one of claims 1 to 13 and the timer-based operation execution method as described in any one of claims 14 to 18.

24. A computer program product, characterized in that The computer program product includes at least one program, which is stored in a computer-readable storage medium; the processor of the communication device reads the at least one program from the computer-readable storage medium, and the processor executes the at least one program, so that the communication device executes the timer-based operation execution method as described in any one of claims 1 to 13 and the timer-based operation execution method as described in any one of claims 14 to 18.

Images