GNSS availability processing method, apparatus, device and storage medium

Abstract

The present disclosure discloses a method, apparatus, device and storage medium for processing GNSS availability in the field of communication technology. The method is executed by a terminal device, and the method includes setting a target parameter of Radio Link Failure (RLF) when a Global Navigation Satellite System (GNSS) of the terminal device expires. The method can provide a solution to GNSS availability.

Description

[Technical Field]

[0001] TECHNICAL FIELD Embodiments of the present disclosure relate to the field of communications technology, and in particular to a method, apparatus, device, and storage medium for processing GNSS availability. [Background technology]

[0002] The GNSS position fix acquired by the terminal device has a validity period, and the validity of the GNSS position fix can only be maintained for a certain period of time. After the validity period is exceeded, the terminal device's GNSS becomes outdated, and the terminal device must reacquire the GNSS.

[0003] Some IoT (Internet of Things) terminal devices cannot support GNSS (Global Navigation Satellite System) reception and LTE (Long Term Evolution) transmission and reception simultaneously.

[0004] How to deal with the GNSS availability issue in the above scenario is an issue that needs to be resolved urgently. Summary of the Invention [Problem to be solved by the invention]

[0005] The embodiments of the present disclosure provide a method, apparatus, device and storage medium for processing GNSS availability, and can provide a solution to the problem of GNSS availability. [Means for solving the problem]

[0006] According to one aspect of an embodiment of the present disclosure, there is provided a method for processing GNSS availability, the method being executed by a terminal device, the method comprising: The method includes setting a target parameter for radio link failure (RLF) when a global navigation satellite system (GNSS) of the terminal device expires.

[0007] According to one aspect of an embodiment of the present disclosure, there is provided a method for processing GNSS availability, the method being executed by a terminal device, the method comprising: Sending a global navigation satellite system (GNSS) validity period to a network device is included.

[0008] According to one aspect of an embodiment of the present disclosure, there is provided a processing device for GNSS availability, the device being used to realize a terminal device, the device comprising: A setting module is included for setting target parameters of a radio link failure (RLF) when a global navigation satellite system (GNSS) of the terminal device expires.

[0009] According to one aspect of an embodiment of the present disclosure, there is provided a processing device for GNSS availability, the device being used to realize a terminal device, the device comprising: and a second transmitting module for transmitting a Global Navigation Satellite System (GNSS) validity period to the network device.

[0010] According to one aspect of an embodiment of the present disclosure, there is provided a terminal device, the terminal device including a processor: The processor is used to set target parameters for radio link failure (RLF) when a global navigation satellite system (GNSS) of the terminal device expires.

[0011] According to one aspect of an embodiment of the present disclosure, there is provided a terminal device, the terminal device including a transceiver; The transceiver is used to transmit Global Navigation Satellite System (GNSS) validity periods to network devices.

[0012] According to one aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, and a computer program is stored in the storage medium, and when the computer program is executed by a processor, the above-mentioned GNSS availability processing method is realized.

[0013] According to one aspect of an embodiment of the present disclosure, a chip is provided, the chip including a programmable logic circuit and / or program instructions, which, when executed, realize the above-mentioned GNSS availability processing method.

[0014] According to one aspect of an embodiment of the present disclosure, there is provided a computer program product or a computer program, the computer program product or the computer program including computer instructions, the computer instructions being stored in a computer-readable storage medium, and a processor reading and executing the computer instructions from the computer-readable storage medium to realize the GNSS availability processing method. [Effects of the Invention]

[0015] The technical solutions provided by the embodiments of the present disclosure can have the following beneficial effects: Solutions are provided for GNSS expiration and GNSS validity reporting, respectively. After GNSS expiration, RLF (Radio Link Failure) is used to record the relevant information, and after obtaining the GNSS validity, the GNSS validity is reported to the network device, improving the processing mechanism related to GNSS validity. [Brief explanation of the drawings]

[0016] In order to more clearly describe the technical solutions in the embodiments of the present disclosure, the following briefly describes the drawings that need to be used in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present disclosure, and those skilled in the art can obtain other drawings based on these drawings without creative work. [Figure 1] 1 is a schematic diagram of a communication system provided by an exemplary embodiment of the present disclosure. [Figure 2] 1 is a schematic diagram of a communication system provided by an exemplary embodiment of the present disclosure. [Figure 3] 1 is a flowchart of a GNSS validity processing method provided by an exemplary embodiment of the present disclosure. [Figure 4] 1 is a flowchart of a GNSS validity processing method provided by an exemplary embodiment of the present disclosure. [Figure 5] 1 is a flowchart of a GNSS validity processing method provided by an exemplary embodiment of the present disclosure. [Figure 6] 1 is a flowchart of a GNSS validity processing method provided by an exemplary embodiment of the present disclosure. [Figure 7] FIG. 2 is a block diagram of a GNSS availability processing device provided by an exemplary embodiment of the present disclosure. [Figure 8] FIG. 2 is a block diagram of a GNSS availability processing device provided by an exemplary embodiment of the present disclosure. [Figure 9] 1 is a schematic structural diagram of a communication device provided by an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0017] To make the objectives, technical solutions and advantages of the present disclosure clearer, the following will further describe in detail the embodiments of the present disclosure with reference to the accompanying drawings.

[0018] The network architectures and business scenarios described in the embodiments of the present disclosure are intended to more clearly explain the technical solutions of the embodiments of the present disclosure, and do not constitute limitations on the technical solutions provided by the embodiments of the present disclosure. Those skilled in the art will understand that, with the evolution of network architectures and the emergence of new business scenarios, the technical solutions provided by the embodiments of the present disclosure can be similarly applied to similar technical problems.

[0019] Before describing the technical solution of the present disclosure, some technical knowledge related to the present disclosure will be explained.

[0020] Non-Terrestrial Network (NTN) technology Currently, relevant standards organizations are researching NTN technology, which typically uses satellite communications to provide communications services to terrestrial users. Satellite communications have many unique advantages over terrestrial cellular networks. First, satellite communications are not limited by user geography. For example, conventional terrestrial communications cannot cover areas such as oceans, high mountains, and deserts, where communications facilities are unavailable or where coverage is limited due to sparse populations. Satellite communications, however, can cover large areas of the globe with a single satellite, and because satellites orbit the Earth, theoretically every corner of the globe can be covered by satellite communications. Second, satellite communications have great social value. Satellite communications can reach remote mountainous areas and impoverished countries and regions at low cost, thereby providing advanced voice communications and mobile Internet technology to people in these regions, narrowing the digital divide with developed regions and promoting their development. Furthermore, satellite communications have long communication distances, and even as communication distances increase, communication costs do not increase significantly. Finally, satellite communications are highly reliable and are not limited by natural disasters.

[0021] Communication satellites are classified into low-earth orbit (LEO), medium-earth orbit (MEO), geostationary earth orbit (GEO), and high elliptical orbit (HEO) satellites depending on their orbital height. Currently, research is primarily focused on LEO and GEO.

[0022] 1. LEO The altitude range of low-orbit satellites is 500km to 1500km, with a corresponding orbital period of approximately 1.5 to 2 hours. The signal propagation delay for single-hop communication between users is generally less than 20ms. The maximum satellite visibility time is 20 minutes. The signal propagation distance is short, link loss is small, and the requirements for transmission power of user terminal devices are not high.

[0023] 2. GEO It is a geosynchronous satellite, orbiting at an altitude of 35,786 km and orbiting the Earth every 24 hours. The signal propagation delay for single-hop communication between users is typically 250 ms.

[0024] In order to ensure satellite coverage and improve the system capacity of the entire satellite communication system, satellites use multiple beams to cover the ground. One satellite can form tens or even hundreds of beams to cover the ground, and one satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers.

[0025] Table 1 shows the satellite altitude, orbit, and satellite coverage of a typical NTN network. [Table 1] The RTT (Round Trip Time) from the terminal device to the access network device includes two parts: one part is the RTT of the link from the terminal device to the satellite, which is a UE specific TA (Terminal Device Specific Time Alignment) part; and the other part is the RTT of the link from the satellite to the access network device, which is a common TA (Time Alignment) part. One part of the common TA part may be compensated by the access network device, and the other part may be compensated by the terminal device. The part compensated by the terminal device is transmitted to the terminal device via a system message.

[0026] Network devices broadcast common TAs that require terminal device compensation, as well as satellite ephemeris information to help terminal devices acquire satellite positions to calculate the RTT from the terminal device to the satellite. Because common TAs and ephemeris information all change due to satellite mobility, the ephemeris information and common TAs broadcast in system messages have a validity period called the UL synchronization validity duration. The ephemeris information and common TA share the UL synchronization validity duration. The value of the UL synchronization validity duration is broadcast by network devices to terminal devices via SIBs.

[0027] The terminal device starts a UL synchronization validity timer based on the ephemeris information in the broadcast message and the epoch time (start validity time) corresponding to the common TA.

[0028] There are three ways to indicate epoch time: 1. Explicit indication of system message: SFN (System Frame Number) and subframe number are explicitly broadcast in the system message to indicate the epoch time.

[0029] 2. System message implicitly includes: The end position of the SI window of the SI (System Information) including the ephemeris information and common TA information is set as the epoch time.

[0030] 3. Dedicated signaling indication: The network device provides the SFN and subframe number to the terminal device via dedicated signaling to indicate the epoch time.

[0031] The IOT terminal device includes at least one of a BL UE (Bandwidth reduction and low complexity UE), a UE in CE mode (UE in Coverage Enhancement mode), and a NB-IOT UE (Narrow Band Internet of Things UE).

[0032] The embodiments of the present disclosure can be applied to an NTN system, as shown in FIGS.

[0033] 1, a schematic diagram of an NTN system in which a communication satellite is a transparent payload satellite is shown. As shown in FIG. 1, the NTN system includes a terminal device 10, a satellite 20, an NTN gateway 30, an access network device 40, and a core network device 50.

[0034] The terminal device 10 and the access network device 40 may communicate via an air interface (such as a Uu interface). In the architecture shown in FIG. 1, the access network device 40 may be located on the ground, and uplink-downlink communication between the terminal device 10 and the access network device 40 may be relayed via a satellite 20 and an NTN gateway 30 (usually on the ground). Take uplink transmission as an example: the terminal device 10 transmits an uplink signal to the satellite 20, which forwards the uplink signal to the NTN gateway 30, which forwards the uplink signal to the access network device 40, which then transmits the uplink signal to the core network device 50. Take downlink transmission as an example: the downlink signal from the core network device 50 is transmitted to the access network device 40, which then transmits the downlink signal to the NTN gateway 30, which forwards the downlink signal to the satellite 20, which forwards the downlink signal to the terminal device 10.

[0035] In the NTN system, the satellite 20 has the role of frequency conversion and signal amplification, and the satellite 20 does not demodulate the signal of the access network device 40, and the satellite 20 is similar to a repeater.

[0036] 2, a schematic diagram of another NTN system in which the communications satellite is a regenerative payload satellite is shown. As shown in FIG. 2, the NTN system includes a terminal device 10, a satellite 20, an NTN gateway 30, and a core network device 50.

[0037] In the architecture shown in Figure 2, the functionality of the access network device 40 is integrated into the satellite 20, i.e., the satellite 20 comprises the functionality of the access network device 40. Communication between the terminal device 10 and the satellite 20 can be via an air interface (such as a Uu interface). Communication between the satellite 20 and the NTN gateway 30 (usually terrestrial) can be via a satellite radio interface (SRI). In the NTN system, the satellite receives a signal, demodulates and decodes it, then re-encodes the modulation, and transmits the recovered signal via the satellite frequency band.

[0038] 2, taking uplink transmission as an example, the terminal device 10 transmits an uplink signal to the satellite 20, the satellite 20 forwards the uplink signal to the NTN gateway 30, and the NTN gateway 30 transmits the uplink signal to the core network device 50. Taking downlink transmission as an example, the downlink signal from the core network device 50 is transmitted to the NTN gateway 30, the NTN gateway 30 forwards the downlink signal to the satellite 20, and the satellite 20 forwards the downlink signal to the terminal device 10.

[0039] 1 and 2, the access network device 40 is a device for providing wireless communication services to the terminal device 10. A connection for communication can be established between the access network device 40 and the terminal device 10 via a connection including signaling and data interaction. There may be multiple access network devices 40, and communication between two adjacent access network devices 40 may be in a wired or wireless manner. The terminal device 10 can switch between different access network devices 40, i.e., can establish a connection with different access network devices 40.

[0040] Taking a cellular communication network as an example, the access network device 40 in the cellular communication network may be a base station. A base station is a device located in an access network to provide wireless communication functions to a terminal device 10. Base stations may include various types of macro base stations, micro base stations, relay stations, access points, etc. In systems using different radio access technologies, devices with base station functions may have different names. For example, in a 5G NR system, they are called gNodeBs or gNBs. As communication technologies evolve, the name "base station" may change. For convenience of explanation, in the embodiments of the present disclosure, the above devices providing wireless communication functions to a terminal device 10 are collectively referred to as base stations or access network devices.

[0041] Furthermore, the terminal device 10 according to the embodiment of the present disclosure may include various handheld devices, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, each having a wireless communication function, as well as various forms of user equipment (UE), mobile stations (MS), terminal devices, etc. For ease of explanation, in the embodiment of the present disclosure, the above devices are collectively referred to as terminal devices. In the embodiment of the present disclosure, "UE" may be used to represent a "terminal device." In the embodiment of the present disclosure, a "network device" may be an access network device (such as a base station) or a satellite.

[0042] Also, taking the 5G NTN system as an example, the NTN system may include multiple satellites 20. One satellite 20 can cover a certain range of a terrestrial area and provide wireless communication services to terminal devices 10 in the terrestrial area. The satellites 20 can also orbit the Earth, and by deploying multiple satellites 20, communication coverage can be achieved for different areas of the Earth's surface.

[0043] In addition, in the embodiments of the present disclosure, the nouns "network" and "system" are usually used interchangeably, but those skilled in the art can understand their meaning. The technical solutions described in the embodiments of the present disclosure may be applied to a Long Term Evolution (LTE) system, a 5G system, an evolution system subsequent to the 5G NR system, or other communication systems, and the present disclosure is not limited thereto.

[0044] Illustratively, an embodiment of the present disclosure provides a processing method for a terminal device after a GNSS period expires.

[0045] 3, there is shown a flowchart of a GNSS availability processing method provided by an embodiment of the present disclosure. In this embodiment, the method is applied to a terminal device in the communication system shown in FIG. 1 or FIG. 2 as an example. The method may include the following steps: Step 201: When the GNSS of the terminal device expires, set a target parameter of RLF (Radio Link Failure).

[0046] Illustratively, before step 201, the terminal device can obtain a GNSS position, and the GNSS position has a validity period. When the GNSS position validity period ends, the terminal device determines that the GNSS position is outdated. That is, the GNSS expired period refers to the GNSS position exceeding the GNSS validity period.

[0047] The validity period of the GNSS position may be preset in the GNSS system or may be promised by a protocol, and the present disclosure is not limited thereto. For example, it can be understood that the terminal device obtains the GNSS validity period from a GPS (Global Positioning System) module of the terminal device.

[0048] After the GNSS period expires, the terminal device determines the RLF, performs the processing process of the RLF, and records the relevant parameters (target parameters) of the RLF based on the GNSS period expiration.

[0049] For example, when the GNSS of the terminal device expires, the terminal device may perform at least one of declaring a MCG (Master Cell Group) RLF and recording target parameters in an RLF variable report (VarRLF-Report).

[0050] The target parameters in the RLF variable report include at least one of a connection failure type and an RLF cause. Illustratively, the terminal device sets the connection failure type as RLF and / or sets the RLF cause as GNSS timeout.

[0051] For example, after a GNSS period of a terminal device expires, the terminal device needs to reacquire a GNSS position. At this time, because some terminal devices do not support simultaneous GNSS reception and LTE transmission and reception, an embodiment of the present disclosure provides a method for the terminal device to declare RLF after a GNSS period expires and stop uplink transmission and downlink reception until it acquires a new GNSS position.

[0052] As described above, the technical solution provided in this embodiment provides a solution to the GNSS timeout problem, which uses RLF (Radio Link Failure) to record relevant information after the GNSS timeout, and improves the processing mechanism related to the availability of the GNSS.

[0053] Illustratively, after the GNSS period expires, the terminal device may return to an idle state.

[0054] Referring to Figure 4, a flowchart of a GNSS availability processing method provided by an embodiment of the present disclosure is shown. In this embodiment, the method is described as being applied to a terminal device in the communication system shown in Figure 1 or Figure 2. The method may include the following steps: Step 301: If the GNSS of the terminal device expires, declare an MCG RLF.

[0055] Alternatively, after the terminal device is GNSS outdated, the terminal device declares an MCG RLF and triggers an MCG RLF processing process.

[0056] Step 302: Record the target parameters in the RLF variable report.

[0057] Optionally, the terminal device records RLF-related information in a VarRLF-Report, for example, by setting connection Failure Type to RLF in the RLF variable report and setting rlf-Cause to GNSS outdated in the RLF variable report.

[0058] Step 303: Return to idle state.

[0059] When AS (Access Stratum) security is active or inactive, the terminal device performs a process to leave the connected state and return from the connected state to the idle state.

[0060] That is, if the access stratum security of the terminal device has not been activated, the terminal device returns to the idle state, or if the access stratum security has been activated, the terminal device returns to the idle state.

[0061] Step 304: Set a release cause for the RRC (Radio Resource Control) connection.

[0062] The terminal device sets the release cause to other, or GNSS outdated, or RRC connection failure, i.e., sets the release cause of the Radio Resource Control (RRC) connection to other, or sets the release cause of the RRC connection to GNSS outdated, or sets the release cause of the RRC connection to RRC connection failure.

[0063] For example, the order of steps 301, 302, 303, and 304 may be arbitrary. That is, the terminal device may first declare RLF after the GNSS expires and then return to the idle state. The terminal device may also first return to the idle state after the GNSS expires and then declare RLF. The embodiments of the present disclosure are not limited thereto.

[0064] Illustratively, after the GNSS period expires, the terminal device declares RLF, sets target parameters for RLF, and returns to an idle state; alternatively, after the GNSS period expires, the terminal device returns to an idle state, declares RLF, and sets target parameters for RLF.

[0065] It can be understood that the above steps can be performed alone after the GNSS expires, or can be performed in combination with other steps, and the order in which the steps are performed can be adjusted as needed.

[0066] As described above, the technical solution provided in this embodiment declares RLF (Radio Link Failure) and records related information after the GNSS expires, controls the terminal device to return from the connected state to the idle state, and sets the cause for releasing the RRC connection based on the GNSS expires, thereby improving the processing mechanism related to the availability of the GNSS.

[0067] Illustratively, the terminal device may remain connected after the GNSS period expires.

[0068] 5, a flowchart of a GNSS availability processing method provided by an embodiment of the present disclosure is shown. In this embodiment, the method is applied to a terminal device in the communication system shown in FIG. 1 or FIG. 2 as an example. The method may include the following steps: Step 401: Send a first message to a network device, where the first message is used to indicate whether the network device supports maintaining a connection state after a GNSS timeout.

[0069] Exemplarily, the first message is used to indicate that the terminal device supports maintaining a connection state when GNSS expires, or the first message is used to indicate that the terminal device does not support maintaining a connection state when GNSS expires.

[0070] Optionally, the terminal device reports whether it has the ability to maintain a connection state after GNSS outdated.

[0071] Illustratively, the network device is an access network device.

[0072] Step 402: Receive a configuration message sent by a network device, where the configuration message is used to indicate whether to maintain a connection state after the GNSS expires.

[0073] Exemplarily, the configuration message is used to configure the terminal device to return to an idle state when a GNSS timeout occurs, or the configuration message is used to configure the terminal device to remain connected when a GNSS timeout occurs.

[0074] Alternatively, the network device may configure the terminal device to return to an idle state after GNSS outdated or to remain connected.

[0075] For example, in the case where the terminal device supports maintaining a connection state after the GNSS expires, the network device configures the terminal device to maintain a connection state when the GNSS expires, or configures the terminal device to return to an idle state when the GNSS expires. If the terminal device does not support maintaining a connection state after the GNSS expires, the network device configures the terminal device to return to an idle state when the GNSS expires.

[0076] If the terminal device is configured to maintain a connection state after the GNSS expires, the network device performs steps 403 to 405. If the terminal device is configured to return to an idle state after the GNSS expires, the network device performs steps 301 to 304.

[0077] Step 403: If the GNSS of the terminal device expires, maintain the connection state.

[0078] The network device is configured so that the terminal device maintains a connection state after the GNSS expires, and when the GNSS expires, the terminal device maintains a connection state.

[0079] Step 404: If the GNSS of the terminal device expires, declare an MCG RLF.

[0080] Alternatively, after the terminal device is GNSS outdated, the terminal device declares an MCG RLF and triggers an MCG RLF processing process.

[0081] Step 405: Record the target parameters in the RLF variable report.

[0082] Alternatively, the terminal device records RLF-related information in a VarRLF-Report, for example, by setting the connection Failure Type in the RLF variable report to be RLF and setting the rlf-Cause in the RLF variable report to be GNSS outdated.

[0083] For example, the order in which RLF is declared and the connection state is maintained may be arbitrary. That is, the terminal device may first declare RLF and maintain a reconnection state after the GNSS period expires, or the terminal device may first maintain a connection state after the GNSS period expires and then declare RLF. The embodiments of the present disclosure are not limited thereto.

[0084] For example, after the GNSS period expires, the terminal device declares RLF, sets target parameters for RLF, and maintains a connection state; or, after the GNSS period expires, the terminal device maintains a connection state, declares RLF, and sets target parameters for RLF.

[0085] It can be understood that the above steps can be performed alone after the GNSS expires, or can be performed in combination with other steps, and the order in which the steps are performed can be adjusted as needed.

[0086] As described above, the technical solution provided by this embodiment allows the terminal device to report to the network device whether it supports maintaining a connected state after the GNSS expires. If the terminal device supports maintaining a connected state and the network device instructs the terminal device to maintain a connected state, after the GNSS expires, the terminal device will maintain a connected state, declare RLF (Radio Link Failure), and record related information, thereby improving the processing mechanism related to the availability of the GNSS.

[0087] For example, after the terminal device GNSS expires, it declares RLF and switches or maintains the state. Next, if the GNSS expires and the terminal device has not acquired the latest GNSS position, the terminal device prohibits uplink transmission. That is, when the terminal device GNSS expires, the terminal device prohibits uplink transmission.

[0088] Alternatively, the terminal device may also not perform downlink reception, i.e., the terminal device may not monitor the PDCCH (Physical Downlink Control Channel) and may not perform downlink reception, i.e., the terminal device may not monitor the PDCCH when the GNSS of the terminal device expires, or may not perform downlink reception when the GNSS of the terminal device expires.

[0089] Then, the embodiment of the present disclosure provides the following two processing methods: Method 1: The terminal device can perform subsequent processing according to the uplink failure.

[0090] Method 2: The network device can set a time window for the terminal device, during which the terminal device acquires a new GNSS position, and does not perform uplink transmission and downlink reception within the time window.

[0091] In the above method 1, uplink transmission is prohibited before the terminal device acquires the latest GNSS position fix. Optionally, the terminal device does not monitor the PDCCH and does not perform downlink reception.

[0092] Regarding no uplink transmission, the embodiments of the present disclosure provide the following three processing methods: Method 1) The MAC (Medium Access Control) layer of the terminal device considers the timeAlignmentTimer to have expired. MAC layer actions are processed by the process after the timeAlignmentTimer has expired. In this method, the terminal device does not start random access before obtaining the latest GNSS position fix.

[0093] That is, the terminal device includes a MAC layer. When the GNSS of the terminal device expires, the MAC layer determines whether the time alignment period has expired and executes a time alignment period expiration processing process. When the GNSS of the terminal device expires, the terminal device prohibits the initiation of random access.

[0094] Among these, the expiration of a timeAlignmentTimer includes considering all timeAlignmentTimers (including the timeAlignmentTimers of each pTAG (Primary Timing Advance Group) and sTAG (Secondary Timing Advance Group)) to have expired, or considering the timeAlignmentTimer of a pTAG to have expired.

[0095] That is, the MAC layer determines that both the pTAG and the sTAG have expired their time alignment periods, or determines that the pTAG has expired their time alignment period.

[0096] Method 2) The terminal device includes a MAC layer and a PHY (Physical layer). The MAC layer / PHY of the terminal device temporarily prohibits any uplink transmission.

[0097] That is, if the GNSS of the terminal device expires, MAC layer or PHY uplink transmission is prohibited.

[0098] Method 3) The terminal device includes an RRC layer and a MAC layer. The actions of the RRC layer and the MAC layer are as follows: RRC layer: After the GNSS outdated, the RRC layer selectively performs at least one of the following actions 1) to 3): Action 1) The RRC layer releases or disables the PUCCH (Physical Uplink Control Channel) / SPUCCH (Short PUCCH) of all serving cells.

[0099] That is, when the GNSS of the terminal device expires, the RRC layer releases or disables at least one of the PUCCH and SPUCCH of the serving cell.

[0100] Action 2) The RRC layer releases or disables SPS (Semi-Persistent Scheduling) of all serving cells.

[0101] That is, when the GNSS of the terminal device expires, the RRC layer releases or disables the SPS of the serving cell.

[0102] Action 3) For NB-IOT terminal devices, the RRC layer releases or disables all dedicated SR (Scheduling Request, uplink scheduling request) resources.

[0103] That is, if the GNSS of the terminal device expires and the terminal device is an NB-IOT device, the RRC layer releases or disables the dedicated SR resource.

[0104] After obtaining the latest GNSS position fix, the RRC layer selectively performs at least one of the following actions 4) through 6): Action 4) The RRC layer restores all disabled PUCCH / SPUCCH of the serving cell.

[0105] For example, when the GNSS expires, the RRC layer releases or disables at least one of the PUCCH and SPUCCH of the serving cell, and when the GNSS position is acquired, the RRC layer restores the disabled PUCCH or SPUCCH of the serving cell.

[0106] Action 5) The RRC layer restores the SPS of all disabled serving cells.

[0107] For example, when the GNSS of the terminal device expires, the RRC layer releases or disables the SPS of the serving cell, and when the GNSS position is acquired, the RRC layer restores the disabled SPS of the serving cell.

[0108] Act 6) For NB-IOT terminal devices, the RRC layer restores all disabled dedicated SR resources.

[0109] For example, if the GNSS of the terminal device expires and the terminal device is an NB-IOT device, the RRC layer releases or disables the dedicated SR resource. If the GNSS position is acquired and the terminal device is an NB-IOT device, the RRC layer restores the disabled dedicated SR resource.

[0110] MAC layer: After the GNSS is outdated, the MAC layer selectively performs at least one of the following actions 7) to 12): Act 7) The MAC layer clears the HARQ (Hybrid Automatic Repeat reQuest) buffers of all serving cells.

[0111] That is, when the GNSS of the terminal device expires, the MAC layer clears the HARQ buffer of the serving cell.

[0112] Act 8) The MAC layer notifies the RRC layer to release / deactivate the PUCCH resources of all serving cells.

[0113] That is, when the GNSS of the terminal device expires, the MAC layer notifies the RRC layer to release or disable the PUCCH resources of the serving cell.

[0114] Act 9) The MAC layer notifies the RRC layer to release / disable SRS (Sounding Reference Signal) resources of all serving cells.

[0115] That is, when the GNSS of the terminal device expires, the MAC layer notifies the RRC layer to release or disable the SRS resources of the serving cell.

[0116] Act 10) The MAC layer clears or disables all configured downlink assignments and uplink grants.

[0117] That is, if the terminal device's GNSS expires, the MAC layer clears or invalidates the configured downlink tasks and uplink grants.

[0118] Act 11) The MAC layer clears / disables PUSCH (Physical Uplink Shared Channel) resources for semi-persistent CSI (Channel State Information) reporting.

[0119] That is, when the GNSS of the terminal device expires, the MAC layer clears or invalidates the PUSCH resource for the CSI report.

[0120] Act 12) The UE MAC layer temporarily prohibits any uplink transmission.

[0121] That is, if the terminal device's GNSS expires, the MAC layer prohibits uplink transmission.

[0122] After obtaining the latest GNSS position fix, the MAC layer restores any disabled configured downlink assignments and uplink grants.

[0123] For example, if the GNSS of the terminal device expires, the MAC layer clears or disables the configured downlink tasks and uplink grants, and if the GNSS position is acquired, the MAC layer restores the disabled configured downlink tasks and uplink grants.

[0124] For example, after the terminal device acquires the latest GNSS position fix, it restores uplink transmission and downlink reception. Optionally, after the terminal device acquires the latest GNSS position fix, it triggers and reports a GNSS validity duration, triggers random access, or triggers connection reestablishment. After establishing the connection, the terminal device optionally performs an MCG RLF report.

[0125] Optionally, the terminal device restores uplink transmission when the GNSS position is acquired.

[0126] Optionally, the terminal device stops downlink reception when the GNSS expires and restores downlink reception when the terminal device GNSS position is acquired.

[0127] Alternatively, the terminal device may return to an idle state when the GNSS position expires, and may perform a random access process when the terminal device GNSS position is acquired.

[0128] Optionally, the terminal device returns to an idle state when the GNSS expires and performs a connection re-establishment process when the terminal device GNSS position is acquired.

[0129] Optionally, when the terminal device GNSS position is obtained, it transmits the GNSS validity period to the network device.

[0130] Optionally, when the terminal device GNSS position is acquired, it reports the MAC RLF to the network device. Illustratively, the terminal device sends an RLF variable report to the network device.

[0131] In the above-mentioned method 2, the terminal device receives the time window setting information sent by the network device, and in response to the setting information, does not perform LTE / NR (New Radio) uplink transmission or downlink reception within the time window, and the terminal device acquires the GNSS position within the time window.

[0132] For method 2, the network device can transmit, for example, a measurement gap time window, during which the terminal device does not perform NR / LTE uplink transmission or downlink reception, and the terminal device can acquire a GNSS position during the measurement gap.

[0133] Illustratively, the network device pre-sets a time window for the terminal device based on the GNSS validity period. Illustratively, the start time of the time window is earlier than the expiration time of the GNSS validity period. The terminal device does not perform uplink transmission or downlink reception within the time window, and acquires a GNSS position within the time window, and before the time window ends, the terminal device acquires an updated GNSS position. Outside the time window, the GNSS position of the terminal device is always within the validity period.

[0134] Illustratively, an embodiment of the present disclosure provides a method for a terminal device to report a GNSS validity period to a network device.

[0135] 6, a flowchart of a GNSS availability processing method provided by an embodiment of the present disclosure is shown. In this embodiment, the method is applied to a terminal device in the communication system shown in FIG. 1 or FIG. 2 as an example. The method may include the following steps: Step 501: Send a GNSS validity period to a network device.

[0136] For example, the terminal device acquires a GNSS position and a GNSS validity period of the GNSS position. The terminal device acquires the GNSS validity period based on a method preset by the GNSS system. For example, the terminal device acquires the GNSS validity period from a GPS module of the terminal device.

[0137] For example, the embodiments of the present disclosure provide various trigger conditions, report contents, and report methods for a terminal device to report a GNSS validity period, and various trigger conditions, report contents, and report methods can be arbitrarily combined.

[0138] Illustratively, for the trigger conditions for the terminal device to report the GNSS validity period, the embodiment of the present disclosure provides the following two conditions: 1) After the terminal device acquires the latest GNSS position fix, it triggers a GNSS validity duration report.

[0139] Illustratively, when the terminal device GNSS position is acquired, it transmits the GNSS validity period to the network device.

[0140] 2) The network device instructs the terminal device whether to report the GNSS validity duration via a system message and / or an RRC dedicated message. After receiving the instruction from the network device, the terminal device reports the GNSS validity duration.

[0141] Exemplarily, the terminal device receives a first instruction sent by the network device via a system message, and / or the terminal device receives a first instruction sent by the network device via a radio resource control (RRC) dedicated message, in which the first instruction is used to instruct the terminal device to report GNSS valid periods, or the first instruction is used to instruct the terminal device not to report GNSS valid periods, and the terminal device transmits the GNSS valid periods to the network device in response to the first instruction instructing the terminal device to report the GNSS valid periods.

[0142] Illustratively, for the reporting method of the terminal device reporting the GNSS validity period, the embodiment of the present disclosure provides the following two methods: 1) Report in msg5 that the terminal device is in random access.

[0143] Illustratively, the terminal device sends a random access message (msg5) to the network device, and the random access message includes a GNSS validity period.

[0144] Specifically, the GNSS validity duration can be carried in the connection establishment complete / connection restoration complete / connection reestablishment complete message.

[0145] That is, the terminal device sends a connection establishment completion message / connection restoration completion message / connection reconfiguration completion message to the network device, and the connection establishment completion message / connection restoration completion message / connection reconfiguration completion message includes a GNSS validity period.

[0146] 2) The terminal device reports via a dedicated RRC message after entering the connected state.

[0147] Specifically, the terminal device can report the GNSS validity duration through a terminal device assistance information message, or the network device requests the terminal device to report the GNSS validity duration in a terminal device information request, and then the terminal device reports the GNSS validity duration through a terminal device information response message.

[0148] Illustratively, the terminal device sends a dedicated RRC message to the network device, where the dedicated RRC message includes a GNSS validity period.

[0149] For example, the terminal device receives a terminal device information request sent by the network device, the terminal device information request is used to request the terminal device to report a GNSS validity period, and the terminal device responds to the terminal device information request by sending a terminal device information response to the network device, where the terminal device information response includes the GNSS validity period.

[0150] Illustratively, for the reporting content of the terminal device reporting the GNSS validity period, the embodiment of the present disclosure provides the following two contents: 1) If the GNSS validity duration is shorter than the validity duration of the ephemeris information / common TA, the GNSS validity duration is reported, where the validity duration of the ephemeris information / common TA refers to the remaining validity period of the ephemeris information / common TA.

[0151] Illustratively, if the GNSS validity period is smaller than the first validity period, the terminal device transmits the GNSS validity period to the network device, where the first validity period is the validity period of the ephemeris information or the common time synchronization. Illustratively, the first validity period is the remaining validity period of the ephemeris information or the common time synchronization.

[0152] 2) The terminal device reports the minimum of the GNSS validity duration and the ephemeris / common TA validity duration.

[0153] Exemplarily, the terminal device sends a second validity period to the network device, where the second validity period is a smaller value of the GNSS validity period and the first validity period, and the first validity period is a validity period of the ephemeris information or the common time synchronization. Exemplarily, the first validity period is a remaining validity period of the validity period of the ephemeris information or the common time synchronization.

[0154] As described above, the technical solution provided in this embodiment provides a solution to the problem of GNSS validity period reporting, providing various trigger conditions, reporting methods, and reporting contents for terminal devices to report GNSS validity periods, and improving the processing mechanism related to GNSS validity.

[0155] It can be understood that in response to the terminal device reporting the GNSS validity period to the network device as described above, after the validity period expires, the actions of the terminal device and subsequent processing manners have already been described in detail in the above embodiments, and will not be described again here.

[0156] The following are examples of the disclosed apparatus, which can be used to implement the disclosed method examples. For details not disclosed in the disclosed apparatus examples, please refer to the disclosed method examples.

[0157] Referring to FIG. 7, a block diagram of a GNSS availability processing device provided by an embodiment of the present disclosure is shown. The device includes a function for implementing the exemplary terminal device-side method. The function can be implemented by hardware or by executing corresponding software in the hardware. The device can be the terminal device described above, or can be configured as a terminal device. As shown in FIG. 7, the device can include a configuration module 604, The setting module 604 is used to set target parameters for radio link failure (RLF) when a Global Navigation Satellite System (GNSS) of the terminal device expires.

[0158] In an optional embodiment, the apparatus further includes a declaration module 606; The declaration module 606 is used to declare a master cell group (MCG) RLF when the GNSS of the terminal device expires; The setting module 604 is used to record target parameters in the RLF variable report.

[0159] In an optional embodiment, the setting module 604 is used to set a connection failure type to RLF; and / or The setting module 604 is used to set the RLF cause (rlf-Cause) to GNSS expiration.

[0160] In an optional embodiment, the device further includes a status module 607; The state module 607 is used to return to an idle state if access stratum security is not activated; Or, The state module 607 is used to return to the idle state if access stratum security is activated.

[0161] In an alternative embodiment, the setting module 604 is used to set a release cause of a Radio Resource Control (RRC) connection to another; Or, The setting module 604 is used to set a release cause of the RRC connection to GNSS timeout; Or, The setting module 604 is used to set the release cause of the RRC connection to an RRC connection failure.

[0162] In an optional embodiment, the device further includes a status module 607; The state module 607 is used to maintain the connection state.

[0163] In an optional embodiment, the device further includes a first receiving module 603; The first receiving module 603 is used to receive a configuration message sent by a network device, wherein: The configuration message is used to configure the terminal device to return to an idle state when a GNSS timeout occurs; or The configuration message is used to configure the terminal device to remain connected if a GNSS timeout occurs.

[0164] In an optional embodiment, the device further includes a first transmitting module 605; The first sending module 605 is used to send a first message to the network device, wherein: The first message is used to indicate that the terminal device supports maintaining a connection state when GNSS expires; or The first message is used to indicate that the terminal device does not support maintaining a connection state when GNSS expires.

[0165] In an optional embodiment, the device further includes a transmission module 601; The transmission module 601 is used to prohibit uplink transmission when the GNSS of the terminal device expires.

[0166] In an optional embodiment, the device further includes a transmission module 601; The transmitting module 601 is used for not monitoring a physical downlink control channel (PDCCH) when the GNSS of the terminal device expires; The transmission module 601 is used to not perform downlink reception when the GNSS of the terminal device expires.

[0167] In an alternative embodiment, the terminal device includes a media access control (MAC) layer; The transmitting module 601 is used to determine the time alignment expiration when the GNSS of the terminal device expires; and The transmission module 601 is used to perform the time alignment expiration process.

[0168] In an alternative embodiment, the transmission module 601 is used to determine the time alignment expiration of both a primary timing early group (pTAG) and a secondary timing early group (sTAG); The transmission module 601 is used to determine the pTAG time alignment expiration.

[0169] In an optional embodiment, the device further includes the transmitting module 601; The transmitting module 601 is used to prohibit the initiation of random access when the GNSS of the terminal device expires.

[0170] In an alternative embodiment, the terminal device includes a media access control layer (MAC layer) and a physical layer (PHY).

[0171] In an alternative embodiment, the terminal device includes a radio resource control (RRC) layer; The transmitting module 601 is used to release or disable at least one of a physical uplink control channel (PUCCH) and a short physical uplink control channel (SPUCCH) of a serving cell when the GNSS of the terminal device expires; The transmitting module 601 is used for releasing or disabling semi-persistent scheduling (SPS) of a serving cell when a GNSS of the terminal device expires; The transmitting module 601 is used to release or disable dedicated uplink scheduling request (SR) resources when the GNSS of the terminal device expires and the terminal device is a Narrowband Internet of Things (NB-IOT) device.

[0172] In an alternative embodiment, the transmitting module 601 is used to restore the PUCCH or SPUCCH of the disabled serving cell when the GNSS position is acquired; The transmitting module 601 is used to restore the SPS of the disabled serving cell when the GNSS position is acquired; The transmitting module 601 is used to restore the disabled dedicated SR resources when the GNSS position is acquired and the terminal device is an NB-IOT device.

[0173] In an alternative embodiment, the terminal device includes a media access control (MAC) layer; The transmitting module 601 is used to clear a Hybrid Automatic Repeat Request (HARQ) buffer of a serving cell when a GNSS period of the terminal device expires; The transmitting module 601 is used to notify a radio resource control (RRC) layer to release or disable a channel sounding reference signal (SRS) resource of a serving cell when a GNSS of the terminal device expires; The transmitting module 601 is used to clear or disable the configured downlink task and uplink permission when the GNSS of the terminal device expires; The transmitting module 601 is used for clearing or invalidating a physical uplink shared channel (PUSCH) resource reported by semi-persistent channel state information (CSI) when a GNSS of the terminal device expires; The transmission module 601 is used to prohibit uplink transmission when the GNSS of the terminal device expires.

[0174] In an alternative embodiment, the transmission module 601 is used to restore configured downlink tasks and uplink grants that have been disabled when a GNSS position is acquired.

[0175] In an alternative embodiment, the transmission module 601 is used to restore uplink transmission when a GNSS position is acquired.

[0176] In an alternative embodiment, the transmission module 601 is used to restore downlink reception when a GNSS position is acquired.

[0177] In an optional embodiment, the device further includes a first transmitting module 605; The first transmitting module 605 is used to transmit the GNSS validity period to the network device when the GNSS position is obtained; The first transmitting module 605 transmits a master cell signal to the network device when the GNSS position is obtained. Group (MCG) Used to report RLF.

[0178] In an optional embodiment, the apparatus further includes an execution module 602; The execution module 602 is used to execute a random access process when the GNSS position is acquired; The execution module 602 is used to execute the connection reestablishment process when the GNSS position is acquired.

[0179] In an optional embodiment, the device further includes a first receiving module 603; The first receiving module 603 is used to acquire the GNSS position within a time window.

[0180] In an optional embodiment, the device further includes a transmission module 601; The transmission module 601 is used to not perform uplink transmission or downlink reception within the time window.

[0181] In an optional embodiment, the device further includes a first receiving module 603; The first receiving module 603 is used for receiving the setting information of the time window sent by the network device.

[0182] Referring to FIG. 8, a block diagram of a GNSS availability processing device provided by an embodiment of the present disclosure is shown. The device has a function for implementing the above-mentioned terminal device-side method example, and the function can be implemented by hardware or by executing corresponding software in hardware. The device can be the above-mentioned terminal device or can be configured as a terminal device. As shown in FIG. 8, the device can include a second transmitting module 701, The second transmitting module 701 is used for transmitting a Global Navigation Satellite System (GNSS) validity period to the network device.

[0183] In an optional embodiment, the second sending module 701 is used to send a random access message to the network device, where the random access message includes the GNSS validity period.

[0184] In an optional embodiment, the second transmitting module 701 is used to transmit a dedicated Radio Resource Control (RRC) message to the network device, where the dedicated RRC message includes the GNSS validity period.

[0185] In an optional embodiment, the device further includes a second receiving module 702; the second receiving module 702 is used to receive a terminal device information request sent by a network device, the terminal device information request being used to request the terminal device to report a GNSS validity period; The second sending module 701 is used for sending a terminal device information response including the GNSS validity period to the network device.

[0186] In an optional embodiment, the second sending module 701 is used to send the GNSS validity period to the network device if the GNSS validity period is smaller than a first validity period; Wherein, the first validity period is the validity period of the ephemeris information or the common time synchronization.

[0187] In an optional embodiment, the second sending module 701 is used to send a second validity period to the network device, the second validity period being a smaller value of the GNSS validity period and the first validity period; Wherein, the first validity period is the validity period of the ephemeris information or the common time synchronization.

[0188] In an alternative embodiment, the second transmitting module 701 is used to transmit the GNSS validity period to the network device when a GNSS position is obtained.

[0189] In an optional embodiment, the device further includes a second receiving module 702; a second receiving module 702 for receiving a first instruction sent by the network device through a system message; and / or a second receiving module 702, used by the network device to receive the first indication sent via a radio resource control (RRC) dedicated message; Wherein, the first instruction is used to instruct the terminal device to report a GNSS valid period, or the first instruction is used to instruct the terminal device not to report the GNSS valid period.

[0190] It should be noted that, when realizing its functions, the device provided in the above embodiments only takes the division of each of the above-mentioned functional modules as an example to describe it. In actual application, the distribution of the above functions can be completed by different functional modules according to actual needs to complete all or part of the above-mentioned functions, that is, the content structure of the device can be divided into different functional modules.

[0191] Regarding the apparatus in the above-described embodiment, the specific manner in which each module performs an operation has been described in detail in the embodiment relating to the present method, and detailed description thereof will be omitted here.

[0192] 9, a schematic block diagram of a communication device (terminal device or network device) provided by an embodiment of the present disclosure is shown. The communication device may include a processor 901, a receiver 902, a transmitter 903, a memory 904, and a bus 905.

[0193] The processor 901 includes one or more processing cores, and the processor 901 executes software programs and modules to perform processing for various functional applications and GNSS availability.

[0194] The receiver 902 and the transmitter 903 can be implemented as a single transceiver 906, which may be a single communications chip.

[0195] The memory 904 is connected to the processor 901 via a bus 905 .

[0196] The memory 904 can be used to store a computer program, and the processor 901 can execute the computer program to realize each step performed by the communication device in the above method embodiments.

[0197] Furthermore, the memory 904 may 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, Random-Access Memory (RAM) and Read-Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), flash memory or other solid-state storage technology, Compact Disc Read-Only Memory (CD-ROM), High-Density Digital Video Disc (DVD) or other optical storage devices, magnetic cassettes, magnetic tapes, magnetic disk storage devices or other magnetic storage devices.

[0198] When the communication device is implemented as a terminal device, the processor 901 according to an embodiment of the present disclosure can execute the steps performed by the terminal device among the methods shown in any of Figures 3 to 6 described above, and no further description will be given here.

[0199] In a possible implementation, when the communication device is implemented as a terminal device, The processor is used to set target parameters for radio link failure (RLF) when a global navigation satellite system (GNSS) of the terminal device expires.

[0200] In a possible implementation, when the communication device is implemented as a terminal device, The transceiver is used to transmit Global Navigation Satellite System (GNSS) validity periods to network devices.

[0201] An embodiment of the present disclosure further provides a computer-readable storage medium, wherein a computer program is stored in the storage medium, and the computer program can be executed by a processor of a core network device to realize the GNSS availability processing method on the terminal device side.

[0202] Alternatively, the computer-readable storage medium may include a read-only memory (ROM), a random-access memory (RAM), a solid-state drive (SSD), an optical disk, etc. The random-access memory may include a resistive random-access memory (ReRAM) and a dynamic random-access memory (DRAM).

[0203] An embodiment of the present disclosure further provides a chip, the chip including a programmable logic circuit and / or program instructions, which, when executed in a terminal device, realizes the method for processing GNSS availability on the terminal device side.

[0204] An embodiment of the present disclosure further provides a computer program product or a computer program, the computer program product or the computer program including computer instructions, the computer instructions being stored in a computer-readable storage medium, and a processor of a terminal device reading and executing the computer instructions from the computer-readable storage medium to realize the method for processing GNSS availability on the terminal device side.

[0205] It should be understood that the "indication" referred to in the embodiments of the present disclosure may be a direct indication, an indirect indication, or an indication that there is an association relationship. For example, A can indicate B, and A can directly indicate B, or B can be obtained by A, and A can indicate C, and B can be obtained via C, which can also indicate that there is a correlation between A and B.

[0206] In describing the embodiments of the present disclosure, the term "correspondence" may mean that there is a direct or indirect correspondence relationship between the two, or that there is an association relationship between the two, or a relationship such as instruction and being instructional, or configuration and being configured.

[0207] As referred to herein, "plurality" means two or more than two. "And / or" describes a relationship between related objects and indicates that three relationships can exist, for example, A and / or B can indicate three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the related objects before and after it are in an "or" relationship.

[0208] Furthermore, the step numbers described in this specification are merely examples of possible execution orders between steps, and in other embodiments, the steps may not be executed in numerical order, for example, two differently numbered steps may be executed simultaneously, or two differently numbered steps may be executed in the reverse order of that shown, and embodiments of the present disclosure are not limited thereto.

[0209] Those skilled in the art will recognize that the functions described in the embodiments of the present disclosure in one or more examples above can be implemented in hardware, software, firmware, or any combination thereof. If implemented using software, these functions may be stored on or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, and computer storage media are any media that facilitates transfer of a computer program from one place to another. Storage media may be any available medium accessible by a general-purpose or special-purpose computer.

[0210] The above are only illustrative examples of the present disclosure, and do not limit the present disclosure. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present disclosure should be included in the protection scope of the present disclosure.

Claims

1. A method for processing GNSS validity executed by a terminal device, comprising: sending a global navigation satellite system (GNSS) validity period to a network device, the GNSS validity period being carried in a connection establishment complete message, a connection restoration complete message, or a connection reestablishment complete message; returning to an idle state and setting a release cause of a radio resource control (RRC) connection to other when a global navigation satellite system (GNSS) of the terminal device expires; A method for processing GNSS validity, comprising:

2. The step of setting a target parameter for radio link failure (RLF) when a global navigation satellite system (GNSS) of the terminal device expires includes: declaring a Master Cell Group (MCG) RLF when the GNSS of the terminal device expires; and recording the target parameters in an RLF variable report. The method for processing GNSS validity according to claim 1 .

3. recording target parameters in the RLF variable report, setting a connection failure type to RLF; setting the RLF cause (rlf-Cause) to GNSS expiration; The method for processing GNSS validity according to claim 2 .

4. The method comprises: If access stratum security is not activated, returning to an idle state; or If access layer security is activated, returning to an idle state. The method for processing GNSS validity according to claim 1 .

5. The method comprises: setting a release cause of the Radio Resource Control (RRC) connection to other; setting the release cause of the RRC connection to GNSS expiration; or and setting a release cause of the RRC connection to RRC connection failure. The method for processing GNSS validity according to claim 4.

6. The method comprises: further comprising the step of maintaining a connection state; The method for processing GNSS validity according to claim 1 .

7. The method comprises: receiving a configuration message sent by the network device; The configuration message is used to configure the terminal device to return to an idle state when a GNSS period expires; or The configuration message is used to configure the terminal device to maintain a connection state when a GNSS period expires. The method for processing GNSS validity according to claim 4.

8. The method comprises: further comprising sending a first message to the network device; The first message is used to indicate that the terminal device supports maintaining a connection state when a GNSS expires; or The first message is used to indicate that the terminal device does not support maintaining a connection state when GNSS expires; The method for processing GNSS validity according to claim 7.

9. The method comprises: Further comprising the step of prohibiting uplink transmission when the GNSS of the terminal device expires. The method for processing GNSS validity according to claim 1 .

10. The method comprises: not monitoring a physical downlink control channel (PDCCH) when the GNSS of the terminal device expires; and not performing downlink reception if the GNSS of the terminal device expires. The method for processing GNSS validity according to claim 1 .

11. the terminal device includes a media access control (MAC) layer; The step of prohibiting uplink transmission when the GNSS of the terminal device expires includes: determining a time alignment expiration when the GNSS of the terminal device expires; and performing a time alignment expiration process. The method for processing GNSS validity according to claim 9 .

12. The step of determining a time alignment expiration comprises: determining time alignment expirations for both the primary timing early group (pTAG) and the secondary timing early group (sTAG); determining the pTAG time alignment expiration; The method for processing GNSS validity according to claim 11 .

13. The method comprises: Further comprising the step of prohibiting initiation of random access when the GNSS of the terminal device expires; The method for processing GNSS validity according to claim 11 .

14. The step of prohibiting uplink transmission is performed by a media access control layer (MAC layer) and a physical layer (PHY) of the terminal device. The method for processing GNSS validity according to claim 9 .

15. The terminal device includes a radio resource control (RRC) layer, and the step of prohibiting uplink transmission when a GNSS of the terminal device expires includes: Releasing or disabling at least one of a physical uplink control channel (PUCCH) and a short physical uplink control channel (SPUCCH) of a serving cell when the GNSS of the terminal device expires; Releasing or disabling semi-persistent scheduling (SPS) of a serving cell when the GNSS of the terminal device expires; Releasing or disabling a dedicated uplink scheduling request (SR) resource when the GNSS of the terminal device expires and the terminal device is a Narrowband Internet of Things (NB-IOT) device; The method for processing GNSS validity according to claim 9 .

16. The method comprises: If the GNSS position is acquired, restoring the PUCCH or SPUCCH of the disabled serving cell; If a GNSS position is acquired, restoring the SPS of the disabled serving cell; and if a GNSS position is acquired and the terminal device is an NB-IOT device, restoring the disabled dedicated SR resources. The method for processing GNSS validity according to claim 15.

17. the terminal device includes a media access control (MAC) layer; The step of prohibiting uplink transmission when the GNSS of the terminal device expires includes: clearing a hybrid automatic repeat request (HARQ) buffer of a serving cell when a GNSS of the terminal device expires; When the GNSS of the terminal device expires, notifying a Radio Resource Control (RRC) layer to release or disable a Physical Uplink Control Channel (PUCCH) resource of a serving cell; When the GNSS of the terminal device expires, notifying an RRC layer to release or disable a channel sounding reference signal (SRS) resource of a serving cell; clearing or disabling the configured downlink task and uplink permission when the GNSS of the terminal device expires; clearing or disabling physical uplink shared channel (PUSCH) resources reported by semi-persistent channel state information (CSI) when a GNSS of the terminal device expires; and prohibiting uplink transmission when the GNSS of the terminal device expires. The method for processing GNSS validity according to claim 9 .

18. The method comprises: If the GNSS position is acquired, restoring the disabled configured downlink tasks and uplink permissions.

18. The method for processing GNSS validity according to claim 17.

19. The method comprises: and if a GNSS position is acquired, further comprising the step of restoring the uplink transmission. The method for processing GNSS validity according to claim 9 .

20. The method comprises: and if a GNSS position is acquired, further comprising restoring downlink reception. The method for processing GNSS validity according to claim 10.

21. The method comprises: If the GNSS position is acquired, sending the GNSS validity period to the network device; and reporting a Master Cell Group (MCG) RLF to the network device if the GNSS position is acquired. The method for processing GNSS validity according to claim 1 .

22. The method comprises: if a GNSS position is acquired, performing a random access process; and if a GNSS position is acquired, performing a connection reestablishment process. The method for processing GNSS validity according to claim 4.

23. The method comprises: further comprising acquiring a GNSS position within the time window. The method for processing GNSS validity according to claim 1 .

24. The method comprises: and further comprising the step of not performing any uplink transmission or downlink reception within the time window.

24. The method of claim 23, wherein the GNSS validity processing method is

25. The method comprises: further comprising receiving setting information of the time window transmitted by a network device; 24. The method of claim 23, wherein the GNSS validity processing method is

26. transmitting a global navigation satellite system (GNSS) validity period to the network device, sending a random access message to the network device, the random access message including the GNSS validity period; The method for processing GNSS validity according to claim 1 .

27. transmitting a global navigation satellite system (GNSS) validity period to the network device, sending a dedicated radio resource control (RRC) message to the network device, the dedicated RRC message including the GNSS validity period; The method for processing GNSS validity according to claim 1 .

28. The method comprises: Further comprising receiving a terminal device information request sent by a network device, wherein the terminal device information request is used to request the terminal device to report a GNSS validity period; sending a dedicated Radio Resource Control (RRC) message to the network device; transmitting a terminal device information response including the GNSS validity period to the network device; 28. The method of claim 27, wherein the GNSS validity processing method is

29. transmitting a global navigation satellite system (GNSS) validity period to the network device, If the GNSS validity period is less than a first validity period, transmitting the GNSS validity period to the network device; the first validity period is a validity period of ephemeris information or common time synchronization; The method for processing GNSS validity according to claim 1 .

30. The method comprises: further comprising transmitting a second validity period to the network device, the second validity period being a smaller value of the GNSS validity period and the first validity period; the first validity period is a validity period of ephemeris information or common time synchronization; The method for processing GNSS validity according to claim 1 .

31. transmitting a global navigation satellite system (GNSS) validity period to the network device, If a GNSS position is acquired, transmitting the GNSS validity period to the network device. The method for processing GNSS validity according to claim 1 .

32. The method comprises: receiving, by the network device, a first indication sent via a system message; and the network device receiving the first indication sent via a Radio Resource Control (RRC) dedicated message; The first instruction is used to instruct the terminal device to report a GNSS validity period, or the first instruction is used to instruct the terminal device not to report the GNSS validity period. The method for processing GNSS validity according to claim 1 .

33. A GNSS availability processing device for implementing a terminal device, comprising: a second transmitting module for transmitting a global navigation satellite system (GNSS) validity period to a network device, wherein the GNSS validity period is carried in a connection establishment complete message, a connection restoration complete message, or a connection reconfiguration complete message; a setting module for returning to an idle state and setting a release cause of a radio resource control (RRC) connection to another when a global navigation satellite system (GNSS) of the terminal device expires; 1. A device for processing GNSS availability.

34. A terminal device, the terminal device includes a processor and a transceiver; The transceiver is used to transmit a global navigation satellite system (GNSS) validity period to the network device, and the GNSS validity period is carried in a connection establishment complete message, a connection restoration complete message, or a connection reconfiguration complete message; The processor is configured to return to an idle state when a Global Navigation Satellite System (GNSS) of the terminal device expires, and to set a release cause of a Radio Resource Control (RRC) connection to another. A terminal device characterized in that

35. A computer-readable storage medium, comprising: A computer program is stored in the storage medium, and when the computer program is executed by a processor, the method for processing GNSS validity according to any one of claims 1 to 32 is realized. A computer-readable storage medium comprising:

36. A chip, The chip includes programmable logic circuits and / or program instructions that, when executed, implement the GNSS availability processing method according to any one of claims 1 to 32. A chip characterized by:

37. A computer program comprising: The computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium, and a processor reads and executes the computer instructions from the computer-readable storage medium to realize the GNSS availability processing method according to any one of claims 1 to 32. A computer program characterized by:

Images