RU2839000C2 - Method and device for processing accuracy of fixing global navigation satellite system - Google Patents

Abstract

FIELD: communication.

SUBSTANCE: method of determining reliability of fixing a global navigation satellite system (GLONASS), performed by a terminal device, includes: transmission of GLONASS fixation validity period to network device, wherein the GLONASS fixation validity period is carried in the connection establishment completion message/connection recovery completion message/connection reestablishment completion message; and returning to the idle state when the GLONASS location is outdated, and setting the reason for resetting the radio resource control (RRC) connection as “other”.

EFFECT: possibility of supporting simultaneous reception of a global navigation satellite system (GLONASS) signal and transmission and reception of data according to a long-term evolution (LTE) standard.

19 cl, 9 dwg

Description

Field of technology

[1] This application is a national phase application of international application PCT/CN2021/144061, filed on December 31, 2021, the contents of which are incorporated in their entirety into this description.

[2] The present invention relates to the field of communication technologies, namely, to a method and device for processing the reliability of the fixation of the global navigation satellite system (GLONASS).

Prerequisites for the creation of an invention

[3] The fixed GLONASS location received by the terminal device has a validity period (relevance), and the validity of the GLONASS location fixation can only be maintained for a finite period of time. After the validity period expires, the GLONASS fixation of the terminal device becomes obsolete. The terminal device must receive the GLONASS fixation again.

[4] However, some Internet of Things (IoT) terminal devices are unable to support simultaneous reception of the global navigation satellite system (GLONASS) signal and transmission and reception of data using the long term evolution (LTE) standard.

[5] Determining the reliability of GLONASS data in the scenario described above is an urgent problem that requires a solution.

The essence of the invention

[6] In embodiments of the present invention, a method, an installation and a device for processing the reliability of GLONASS fixation, as well as a data carrier, are proposed, which represent a solution for determining the reliability of GLONASS data. The proposed technical solution is described below.

[7] According to one aspect of the embodiments of the present invention, a method for processing the reliability of GLONASS fixation is proposed. The proposed method is performed using a terminal device, wherein the method includes:

[8] setting the target parameter for radio link failure (RLF) in the case where the global navigation satellite system (GLONASS) fix of the terminal device is outdated.

[9] According to one aspect of the embodiments of the present invention, a method for processing the reliability of a GLONASS fixation is proposed. The proposed method is performed using a terminal device, wherein the method includes:

[10] transfer of the validity period of the global navigation satellite system (GLONASS) fix to the network device.

[11] According to a third aspect of the embodiments of the present invention, a terminal device is provided. The proposed terminal device includes a processor.

[12] The processor is configured to perform the method according to the first aspect or the second aspect.

Brief description of the drawings

[13] Below, drawings will be briefly described to provide a more detailed explanation of the technical solutions in the embodiments of the present invention.

[14] Fig. 1 is a block diagram of a communication system proposed in one embodiment of the present invention.

[15] Fig. 2 is a block diagram of a communication system proposed in one embodiment of the present invention.

[16] Fig. 3 is a flow chart of an algorithm for a method for processing the reliability of a GLONASS fixation proposed in one embodiment of the present invention.

[17] Fig. 4 is a flow chart of an algorithm for a method for processing the reliability of a GLONASS fixation proposed in one embodiment of the present invention.

[18] Fig. 5 is a flow chart of an algorithm for a method for processing the reliability of a GLONASS fixation proposed in one embodiment of the present invention.

[19] Fig. 6 is a flow chart of an algorithm for a method for processing the reliability of a GLONASS fixation proposed in one embodiment of the present invention.

[20] Fig. 7 is a block diagram of a device for processing the reliability of GLONASS fixation, proposed in one of the embodiments of the present invention.

[21] Fig. 8 is a block diagram of a device for processing the reliability of a GLONASS fixation, proposed in one embodiment of the present invention.

[22] Fig. 9 is a structural block diagram of a communication device proposed in one embodiment of the present invention.

Detailed description of the invention

[23] For a more detailed explanation of the objectives, technical solutions and advantages of the present invention, various implementations thereof are described in detail below using examples of the accompanying drawings.

[24] The network architecture and service scenarios illustrated in the embodiments of the present invention are intended to explain in more detail the technical solutions proposed in the present invention and do not impose any limitations on the proposed technical solutions. Those skilled in the art should understand that the technical solutions proposed in the embodiments of the present invention are applicable to solving similar technical problems that may arise with the development of system architectures and the emergence of new service scenarios.

[25] First, technical information related to the present invention will be provided, and then the proposed technical solutions will be described.

[26] Non-Terrestrial Network (NTN) Technology

[27] The relevant standardization organizations are currently studying NTN technology, which mainly uses satellite communications to provide communication services to terrestrial users. Compared with terrestrial cellular networks, satellite communications have many unique advantages. Firstly, satellite communications are not limited to the subscriber’s geographical area. For example, conventional terrestrial communications are unable to cover areas such as oceans, mountains, deserts and the like, where communication devices cannot be installed or communication coverage cannot be provided due to insufficiently dense population. Satellite communications, on the other hand, can cover vast terrestrial areas, with satellites moving in orbit around the Earth, which means that, theoretically, all corners of the planet can be covered by satellite communications. Secondly, satellite communications have great social significance. It can cover remote mountainous areas, poor or underdeveloped countries and regions at a lower cost, allowing people in these regions to enjoy modern voice communication and mobile Internet technology, reducing the digital gap with developed regions and accelerating development. Third, satellite communication has a long range, and the cost of communication does not increase significantly with the increase in communication distance. Finally, satellite communication is highly stable and is not affected by natural disasters.

[28] Communication satellites are classified according to the altitude of their orbits as follows: low-earth orbit (LEO) satellites, medium-earth orbit (MEO) satellites, geostationary earth orbit (GEO) satellites, elliptical orbit (HEO) satellites, etc. Currently, the main developments are focused on LEO and GEO satellites.

[29] 1. LEO

[30] The altitude range of low-Earth orbit satellites is from 500 to 1500 km, and the corresponding orbital period is about 1.5-2 hours. The signal propagation delay for single-hop communication between subscribers generally does not exceed 20 ms. The maximum visibility time of the satellite is 20 minutes. The signal propagation range is short, the losses in the communication line are small, and the requirements for the transmission power of subscriber terminal devices are low.

[31] 2. GEO

[32] Geostationary Earth orbit satellites have an orbital altitude of 35,786 km and a rotation period around the earth of 24 hours. The propagation delay of a signal in a single-hop connection between subscribers is typically 250 ms.

[33] To provide satellite communications coverage and increase the capacity of the satellite communications system as a whole, satellites use multi-beam communications for ground coverage. A satellite can form tens or even hundreds of beams to cover ground areas, and the coverage of one satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers.

[34] Table 1 shows the satellite altitudes, orbits, and satellite coverage for a typical NTN network.

Table 1

Platform Altitude Range Orbit Beam Coverage Area

LEO satellite 300 - 1500 km Circular around the Earth 100 - 1000 km

MEO satellite 7000 - 25000 km 100 - 1000 km

GEO satellite 35786 km The corresponding station maintains a fixed position in altitude and azimuth relative to a given point on the earth's surface 200 - 3500 km

UAS platform (including HAPS) 8-50 km (20 km for HAPS) 5 - 200 km

HEO satellite 400 - 50000 km Elliptical around the Earth 200 - 3500 km

[35] The round trip time (RTT) from the terminal device to the network access device consists of two parts: one part is the RTT of the communication link from the terminal device to the satellite, which is a user equipment (UE)-specific part of the time alignment (TA), and the second part is the RTT of the communication link from the satellite to the network access device, which is a part of the general time alignment (TA). A part of the general TA can be compensated by the network access device, while the other part can be compensated by the terminal device. The part compensated by the terminal device is transmitted to the terminal device using a system message.

[36] In addition to broadcasting the TA which needs to be compensated by the terminal device, the network device also broadcasts the ephemeris information of the satellite to help the terminal device obtain the satellite position and calculate the RTT from the terminal device to the satellite. Due to the movement of the satellite, the overall TA and the ephemeris information change, so the ephemeris information and the overall TA broadcast in the system message have a validity period which is called the uplink (UL) synchronization validity period. The ephemeris information and the overall TA have the same uplink synchronization validity period. The uplink synchronization validity period value is broadcast from the network device to the terminal device using the System Information Block (SIB).

[37] The terminal device starts the uplink synchronization validity timer using the reference time (action start time) corresponding to the ephemeris information and the common TA in the broadcast message.

[38] The reference time can be specified in three ways:

[39] 1. Explicit indication in the system message: The system frame number (SFN) and subframe number are explicitly broadcast in the system message, indicating the reference time.

[40] 2. Implicit indication in the system message: the final position of the system information (SI) window containing ephemeris information and information on the general TA is used as the reference time.

[41] 3. Indication by special signaling: To indicate the reference time, the network device transmits the SFN number and the subframe number to the terminal device by special signaling.

[42] The IOT terminal devices include at least one of the following: a Bandwidth Reduction and Low Complexity UE (BL UE), a Coverage Enhancement UE (CE), or a Narrow Band Internet of Things UE (NB-IOT UE).

[43] Embodiments of the present invention may be applied to the NTN system shown in Fig. 1 and Fig. 2.

[44] Referring to Fig. 1, which shows a block diagram of the NTN system, and where the communication satellite is a transparent data relay satellite. According to Fig. 1, the NTN system includes: a terminal device 10, a satellite 20, an NTN gateway 30, a network access device 40, and a core network device 50.

[45] Communication between the terminal device 10 and the network access device 40 may be performed via a radio interface (e.g., a Uu interface). In the architecture shown in Fig. 1, the network access device 40 may be located on the ground, and the uplink and downlink communication between the terminal device 10 and the network access device 40 may be relayed via a satellite 20 and an NTN gateway 30 (typically located on the ground). Considering 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 then the NTN gateway 30 forwards the uplink signal to the network access device 40, which forwards the uplink signal to the core network device 50. Let us consider the downlink transmission as an example: a downlink signal from the core network device 50 is transmitted to the network access device 40, the network access device 40 transmits the downlink signal to the NTN gateway 30, the NTN gateway 30 forwards the downlink signal to the satellite 20, and then the satellite 20 forwards the downlink signal to the terminal device 10.

[46] In the NTN system, satellite 20 performs the functions of frequency conversion and signal amplification, while satellite 20 does not demodulate the signal of network access device 40, that is, satellite 20 is similar to a repeater.

[47] Referring to Fig. 2, a block diagram of another NTN system is shown, where the communication satellite in the NTN system is a satellite with signal regeneration. According to the illustration of Fig. 2, the NTN system includes: a terminal device 10, a satellite 20, an NTN gateway 30 and a core network device 50.

[48] In the architecture shown in Fig. 2, the functions of the network access device 40 are integrated into the satellite 20, that is, the satellite 20 performs the functions of the network access device 40. Communication between the terminal device 10 and the satellite 20 may be carried out via a radio interface (for example, a Uu interface). The satellite 20 and the NTN gateway 30 (usually located on the ground) may communicate via a satellite radio interface (SRI). In such an NTN system, the satellite receives a signal, demodulates and decodes it, then re-encodes and modulates it, and transmits the regenerated signal in the satellite frequency band.

[49] In the architecture shown in Fig. 2, taking the uplink transmission as an example, the terminal device 10 transmits the uplink signal to the satellite 20, and the satellite 20 forwards the uplink signal to the NTN gateway 30, and then the NTN gateway 30 to the core network device 50. Taking the 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 then the satellite 20 forwards the downlink signal to the terminal device 10.

[50] In the above-described architectures, shown in Fig. 1 and 2, the network access device 40 is a device for providing wireless communication services to the terminal device 10. A connection can be established between the network access device 40 and the terminal device 10 for communicating over this connection, which includes exchanging signals and data. Several network access devices 40 can be present, and two adjacent network access devices 40 can also perform wired or wireless communication with each other. The terminal device 10 can switch between different network access devices 40, that is, establish connections with different network access devices 40.

[51] Taking a cellular communication network as an example, the network access device 40 in the cellular communication network may be a base station. A base station is a device that is deployed in an access network to provide wireless communication functions to the terminal device 10. The base station may have various forms: macro base stations, micro base stations, relay stations, access daughter stations, etc. In systems that use different radio access technologies, the name of the devices with base station functions may be different, for example, in the 5G New Radio (NR) system, they are called gNodeB or gNB. With the development of communication technologies, the name "base station" may also change. For simplicity, in the embodiments of the present invention, the above-described devices that provide wireless communication functions to the terminal device 10 are collectively called base stations or network access devices.

[52] In this case, the terminal device 10 used in the embodiments of the present invention may include various portable devices, devices installed on vehicles, wearable devices, computing devices or other data processing devices associated with wireless modems, as well as various types of user equipment (UE), mobile stations (MS), terminal devices and the like. For ease of description, in the embodiments of the present invention, such devices are collectively called terminal devices. In the embodiments of the present invention, the term "user equipment, UE" is sometimes used instead of "terminal device". In the embodiments of the present invention, the "network device" may be a network access device (e.g., a base station) or a satellite.

[53] In this case, taking the NTN 5G system as an example, the NTN system may include a plurality of satellites 20. Each satellite 20 may provide coverage of a given terrestrial area and provide wireless communication services to the terminal device 10 in this area. In this case, the satellite 20 may move in orbit around the earth, and by arranging a plurality of satellites 20, communication coverage of various areas of the earth's surface may be provided.

[54] In the embodiments of the present invention, the terms “system” and “network” are often used interchangeably, but those skilled in the art should understand their meanings. The technical solution described in the embodiments of the present invention can be applied to a long term evolution (LTE) system, a 5G system, and subsequent evolution stages of 5G NR systems, or other communication systems, without limiting the present invention in this regard.

[55] As an example, in one embodiment of the present invention, a method for processing for a terminal device after GLONASS fix deprecation is provided.

[56] Let us consider Fig. 3, which is a block diagram of an algorithm for a method for processing the reliability of a GLONASS fixation, proposed in one of the examples of implementing the present invention. This embodiment of the present invention is described using the example of a method used in a terminal device of the communication system shown in Fig. 1 or 2. The method may include the steps described below.

[57] Step 201: In case the GLONASS fix of the terminal device is outdated, setting the target radio link failure (RLF) parameter.

[58] In one implementation, prior to step 201, the terminal device may obtain a GLONASS location fix, wherein the GLONASS location fix may have a validity period. When the validity period of the GLONASS location fix expires, it is determined that the GLONASS fix is out of date. The GLONASS fix being out of date means that the validity period of the GLONASS fix for the GLONASS location fix has expired.

[59] It should be understood that the validity period of the GLONASS location fixation may be pre-configured in the GLONASS system or specified in the protocol, without limiting the present invention in this regard. As an example, the terminal device may receive the validity period of the GLONASS fixation from the global positioning system (GPS) module of the terminal device.

[60] After the GLONASS fix has become obsolete, the terminal device detects the RLF, executes the RLF processing procedure, and records the corresponding parameter (target parameter) of the RLF corresponding to the GLONASS fix becoming obsolete.

[61] In one implementation, when the GLONASS fix of the terminal device is out of date, the terminal device may perform at least one of the following: declaring a master cell group (MCG) RLF or writing a target parameter to a VarRLF-Report.

[62] The target parameter in the RLF variable report includes the link failure type and/or the RLF reason. In one implementation, the terminal device may specify the link failure type as "RLF" and/or specify the RLF reason as "GLONASS fix aging".

[63] In one embodiment, after a GLONASS fix of a terminal device ages out, the terminal device must re-acquire a GLONASS location fix. For this case, since some terminal devices do not support simultaneous GLONASS reception and LTE transmission/reception, embodiments of the present invention provide a method in which, after a GLONASS fix ages out, the terminal device declares an RLF and stops uplink transmission and downlink reception until it obtains a new GLONASS location fix.

[64] Thus, the technical solution proposed in the embodiments of the present invention is a solution for the situation of GLONASS fixation aging. After the GLONASS fixation aging, RLF is used to record the relevant information, which can improve the data processing mechanism related to the reliability of the GLONASS fixation.

[65] In one implementation, after the GLONASS fix has expired, the terminal device may return to an idle state.

[66] Let us consider Fig. 4, which is a flow chart of an algorithm for a method for processing the reliability of a GLONASS fixation, proposed in one of the examples of implementing the present invention. This embodiment of the present invention is described using the example of a method used in a terminal device of the communication system shown in Fig. 1 or 2. The method may include the steps described below.

[67] Step 301: Declare RLF MCG if the terminal device's GLONASS fix is out of date.

[68] In one implementation, after the terminal device's GLONASS fix has aged, the terminal device declares an RLF MCG to initiate an RLF MCG processing procedure.

[69] Step 302: The target parameter is written to the RLF variable report.

[70] In one implementation, the terminal device records information related to RLF in a RLF variable report (VarRLF-Report), such as setting the link failure type as "RLF" in the RLF variable report; and setting the RLF cause as "GLONASS fix aging" in the RLF variable report.

[71] Step 303: Return to Idle State.

[72] When access stratum (AS) security is enabled or not enabled, the terminal device performs a connected state exit procedure and returns from the connected state to the idle state.

[73] That is, if the access layer security of the terminal device is not activated, the terminal device returns to the idle state; or, if the access layer security is activated, the terminal device returns to the idle state.

[74] Step 304: Specify the reason for resetting the Radio Resource Control (RRC) connection.

[75] The terminal device sets the reset reason to "other", "GLONASS fix aging", or "RRC connection failure". That is, the RRC connection reset reason is set to "other"; or the RRC connection reset reason is set to "GLONASS fix aging"; or the RRC connection reset reason is set to "RRC connection failure".

[76] In one embodiment, the sequence of steps 301, 302, 303 and 304 may be arbitrary. That is, after the GLONASS fix ages, the terminal device may first declare RLF and then return to the idle state; or after the GLONASS fix ages, the terminal device may return to the idle state and then declare RLF. The present invention is not limited in this regard.

[77] As an example, after a GLONASS fix has aged, a terminal device may declare an RLF and specify an RLF target; and return to the idle state. Alternatively, after a GLONASS fix has aged, a terminal device may return to the idle state; and declare an RLF and specify an RLF target.

[78] It should be understood that the steps described above after the GLONASS fixation becomes obsolete can be performed separately, or can be performed in combination with other steps, and the sequence of steps can be adjusted as necessary.

[79] Thus, in the technical solution proposed in this embodiment of the present invention, after the GLONASS fixation becomes obsolete, the RLF is declared and the corresponding information is recorded, the terminal device is ensured to return from the connected state to the idle state, and the reason for resetting the RRC connection is set to “GLONASS fixation becomes obsolete”, which makes it possible to improve the data processing mechanism related to the reliability of the GLONASS fixation.

[80] In one implementation, after the GLONASS fix has expired, the terminal device remains connected.

[81] Let us consider Fig. 5, which is a block diagram of an algorithm for a method for processing the reliability of a GLONASS fixation, proposed in one of the embodiments of the present invention. This embodiment of the present invention is described using the example of a method used in a terminal device of the communication system shown in Fig. 1 or 2. The method may include the steps described below.

[82] Step 401: a first message is transmitted to the network device, wherein the first message is configured to indicate whether to maintain a connected state after the GLONASS fix has expired.

[83] In one embodiment, the first message may be configured to indicate that the terminal device maintains a connected state when the GLONASS fix is out of date, or the first message may be configured to indicate that the terminal device does not maintain a connected state when the GLONASS fix is out of date.

[84] In one implementation, the terminal device may report its ability to remain connected after the GLONASS fix has expired.

[85] In one embodiment, said network device may be a network access device.

[86] Step 402: receiving a configuration message transmitted by the network device, wherein the configuration message is configured to indicate whether to remain in a connected state after the GLONASS fix expires.

[87] In one embodiment, the configuration message may be configured to configure the terminal device to return to the IDLE state when the GLONASS fix is expired, or the configuration message may be configured to configure the terminal device to continue to be connected when the GLONASS fix is expired.

[88] In one implementation, the network device may configure the terminal device to return to an idle state or to remain in a connected state after the GLONASS fix has expired.

[89] In one embodiment, if the terminal device maintains a connected state after the GLONASS fix has aged out, the network device configures the terminal device to continue to be connected when the GLONASS fix has aged out, or the network device configures the terminal device to return to the idle state when the GLONASS fix has aged out. If the terminal device does not maintain a connected state after the GLONASS fix has aged out, the network device configures the terminal device to return to the idle state when the GLONASS fix has aged out.

[90] If the network device configures the terminal device to remain in the connected state after the GLONASS fix ages out, perform steps 403-405. If the network device configures the terminal device to return to the idle state after the GLONASS fix ages out, perform steps 301-304.

[91] Step 403: If the terminal device's GLONASS fix is out of date, remain in the connected state.

[92] If a network device configures a terminal device to remain in a connected state when the GLONASS fix is expired, the terminal device remains in a connected state.

[93] Step 404: Declare RLF MCG if the terminal device's GLONASS fix is out of date.

[94] In one implementation, after the terminal device's GLONASS fix has aged, the terminal device declares an RLF MCG to initiate an RLF MCG processing procedure.

[95] Step 405: The target parameter is written to the RLF variable report.

[96] In one implementation, the terminal device records information related to RLF in a RLF variable report (VarRLF-Report), such as setting the link failure type as "RLF" in the RLF variable report; and setting the RLF cause as "GLONASS fix aging" in the RLF variable report.

[97] In one embodiment, the sequence of declaring RLF and remaining in the connected state may be arbitrary. That is, after the GLONASS fix ages, the terminal device may first declare RLF and then remain in the connected state; or after the GLONASS fix ages, the terminal device may remain in the connected state and then declare RLF. The present invention is not limited in this regard.

[98] In one implementation, after the GLONASS fix has aged out, the terminal device may declare an RLF and specify an RLF target parameter; and remain in the connected state. Alternatively, after the GLONASS fix has aged out, the terminal device may remain in the connected state; and declare an RLF and specify an RLF target parameter.

[99] It should be understood that the steps described above after the GLONASS fixation becomes obsolete can be performed separately, or can be performed in combination with other steps, and the sequence of steps can be adjusted as necessary.

[100] Thus, in the technical solution proposed in this embodiment of the present invention, the terminal device may report to the network device whether it maintains being in the connected state after the aging of the GLONASS fix, and when the terminal device maintains being in the connected state and the network device instructs the terminal device to remain in the connected state, then after the aging of the GLONASS fix, the terminal device may remain in the connected state, declare RLF and record the relevant information, which can improve the data processing mechanism related to the reliability of the GLONASS fix.

[101] In one implementation, after a GLONASS fix has aged, the terminal device may declare an RLF and switch state or maintain state. Then, if the GLONASS fix has aged and the terminal device does not receive a recent GLONASS location fix, the terminal device is prohibited from performing uplink transmissions. That is, if the GLONASS fix of the terminal device has aged, the terminal device is prohibited from performing uplink transmissions.

[102] In one embodiment, the terminal device also does not perform downlink reception, that is, the terminal device no longer monitors the physical downlink control channel (PDCCH) and no longer performs downlink reception. That is, when the GLONASS fix of the terminal device is aged, the terminal device does not monitor the PDCCH; or, when the GLONASS fix of the terminal device is aged, it does not perform downlink reception.

[103] In this case, in this embodiment of the present invention, two processing methods are provided as described below.

[104] Method 1: The terminal device may perform further processing according to the uplink desynchronization.

[105] Method 2: The network device may configure a time window for the terminal device, the terminal device obtains a new GLONASS location fix within this time window, and does not perform uplink transmissions or downlink receptions within this time window.

[106] In the case of method 1 described above, the terminal device inhibits uplink transmission until a new GLONASS position fix is received. In one implementation, the terminal device no longer monitors the PDCCH and no longer receives downlink.

[107] In the case of failure to perform uplink transmissions, this embodiment of the present invention provides three processing modes described below.

[108] Mode 1) The media access control (MAC) layer of the terminal device takes into account that the time synchronization timer has expired. The MAC layer actions are processed according to the procedure after the time synchronization timer has expired. Thus, the terminal device will not initiate random access until it receives the latest GLONASS location fix.

[109] That is, the terminal device enables the MAC layer. When the GLONASS fix of the terminal device is expired, the MAC layer determines that the time alignment timer has expired; and executes the processing procedure for the expiration of the time alignment timer. When the GLONASS fix of the terminal device is expired, the terminal device is prohibited from initiating random access.

[110] The expiration of a timing advance timer includes the recognition that all timing advance timers, including the expiration of the corresponding timing advance timers of the primary timing advance group (pTAG) and secondary timing advance group (sTAG), or the recognition that the timing advance timer of the pTAG has expired.

[111] That is, the MAC layer determines that both the pTAG and sTAG timing timers have expired; or determines that the pTAG timing timer has expired.

[112] Mode 2) The terminal device enables the MAC layer and the physical layer (PHY). The MAC/PHY layers of the terminal device temporarily disable any uplink transmissions.

[113] That is, when the terminal device's GLONASS fix is out of date, the MAC or PHY layer prohibits uplink transmissions.

[114] Mode 3) The terminal device includes the RRC layer and the MAC layer. The actions at the RRC layer and the MAC layer are described below respectively.

[115] RRC Level:

[116] After the GLONASS fix has become obsolete, the RRC layer performs at least one of the actions 1)-3) described below.

[117] Action 1): The RRC layer resets or deactivates the physical uplink control channel (PUCCH) / short PUCCH (SPUCCH) of all serving cells.

[118] That is, when the GLONASS fix of the terminal device is obsolete, the RRC layer resets or deactivates the PUCCH and/or SPUCCH of the serving cell.

[119] Action 2): The RRC layer resets or deactivates semi-persistent scheduling (SPS) of all serving cells.

[120] That is, when the GLONASS fix of the terminal device is outdated, the RRC layer resets or deactivates the SPS of the serving cell.

[121] Action 3): For the NB-IOT terminal device, the RRC layer discards or deactivates all allocated scheduling request (SR) resources.

[122] That is, when the GLONASS fix of the terminal device is outdated and the terminal device is an NB-IOT device, the RRC layer resets or deactivates the allocated SR resources.

[123] Upon receiving the latest GLONASS position fix, the RRC layer performs at least one of the actions 4)-6) described below.

[124] Action 4): The RRC layer restores the PUCCH/SPUCCH of all deactivated serving cells.

[125] In one implementation, when a GLONASS fix is old, the RRC layer resets or deactivates the PUCCH and/or SPUCCH of the serving cell. Then, when a GLONASS location fix is received, the RRC layer restores the PUCCH or SPUCCH of the deactivated serving cell.

[126] Action 5): The RRC layer restores the SPS of all deactivated serving cells.

[127] In one implementation, when the GLONASS fix of the terminal device is old, the RRC layer resets or deactivates the SPS of the serving cell. Then, when the GLONASS location fix is received, the RRC layer restores the SPS of the deactivated serving cell.

[128] Action 6): For the NB-IOT terminal device, the RRC layer restores all deactivated allocated Scheduling Request (SR) resources.

[129] In one implementation, when a GLONASS fix of a terminal device is old and the terminal device is an NB-IOT device, the RRC layer resets or deactivates the dedicated SR resources. As an example, when a GLONASS location fix is received and the terminal device is an NB-IOT device, the RRC layer restores all deactivated dedicated SR resources.

[130] MAC Level:

[131] After the GLONASS fixation has become obsolete, the MAC layer performs at least one of the actions 7)-12) described below.

[132] Action 7): The MAC layer clears the hybrid automatic repeat request (HARQ) buffer of all serving cells.

[133] That is, when the GLONASS fix of the terminal device is outdated, the MAC layer clears the HARQ buffer of the serving cell.

[134] Step 8): The MAC layer notifies the RRC layer about the reset/deactivation of the PUCCH resource of all serving cells.

[135] That is, when the GLONASS fix of the terminal device becomes obsolete, the MAC layer notifies the RRC layer about the reset or deactivation of the PUCCH resource of the serving cell.

[136] Step 9): The MAC layer notifies the RRC layer of the reset/deactivation of the sounding reference signal (SRS) resource of all serving cells.

[137] That is, when the GLONASS fix of the terminal device becomes obsolete, the MAC layer notifies the RRC layer about the reset or deactivation of the SRS resource of the serving cell.

[138] Action 10): The MAC layer clears or deactivates all configured downlink assignments and uplink grants.

[139] That is, when the end device's GLONASS binding is expired, the MAC layer clears or deactivates the configured downlink and uplink enable tasks.

[140] Action 11): The MAC layer clears/deactivates the physical uplink shared channel (PUSCH) resource signaled using semi-persistent channel state information (CSI).

[141] That is, when the GLONASS fix of the terminal device is expired, the MAC layer clears or deactivates the PUSCH resource reported using CSI.

[142] Action 12): The subscriber equipment MAC layers temporarily prohibit any uplink transmissions.

[143] That is, when the terminal device's GLONASS fix is out of date, the MAC layer prohibits uplink transmissions.

[144] Upon receiving a new GLONASS position fix, the MAC layer restores the disabled downlink assignments and uplink grants.

[145] In one implementation, when the terminal device's GLONASS fix is stale, the MAC layer clears or deactivates the configured downlink assignments and uplink grants. Then, upon receipt of a new GLONASS location fix, the MAC layer restores the deactivated downlink assignments and uplink grants.

[146] In one embodiment, the terminal device, after receiving a new GLONASS position fix, restores uplink transmissions and downlink reception. In one embodiment, after receiving a new GLONASS position fix, the terminal device initiates a GLONASS fix validity age report, or initiates random access, or initiates connection reestablishment. After connection establishment, the terminal device may transmit an RLF MCG report.

[147] In one implementation, the terminal device, after receiving the latest GLONASS position fix, restores the uplink transmissions.

[148] In one embodiment, if the terminal device stops receiving the downlink in the event of a GLONASS fix becoming obsolete, the terminal device restores receiving the downlink in the event of a GLONASS location fix being received.

[149] In one implementation, if the terminal device returns to the idle state in the event of a GLONASS fix becoming obsolete, the terminal device performs a random access procedure in the event of a GLONASS location fix being obtained.

[150] In one implementation, if the terminal device returns to the idle state in the event of a GLONASS fix becoming obsolete, the terminal device performs a procedure to re-establish a communication connection in the event of receiving a GLONASS location fix.

[151] In one implementation, when a terminal device receives a GLONASS location fix, it transmits a GLONASS fix validity period to the network device.

[152] In one implementation, the terminal device transmits a RLF MCG report to the network device upon receipt of a new GLONASS position fix. In one implementation, the terminal device may transmit a report with RLF variables to the network device.

[153] For the above-described method 2: the terminal device receives the configuration information of the time window transmitted by the network device and, in response to this configuration information, does not perform uplink transmissions or downlink receptions of LTE/New Radio (NR) within this time window. The terminal device obtains a GLONASS location fix within said time window.

[154] For method 2, the network device may issue a time window, such as a measurement time interval, and the terminal device does not perform NR/LTE uplink transmissions or downlink receptions within the measurement time interval, while the terminal device may receive a GLONASS location fix during the measurement time interval.

[155] In one embodiment, the network device may pre-configure a time window for the terminal device in accordance with the validity period of the GLONASS fix. In one embodiment, the start time of the time window may precede the expiration time of the validity period of the GLONASS fix. The terminal device does not transmit on the uplink or receive on the downlink within the time window and receives a GLONASS location fix within the time window. Before the end of the time window, the terminal device receives the latest GLONASS location fix. Then, except for the time window, the GLONASS location fix is always within the validity period.

[156] In one embodiment of the present invention, a method is proposed for transmitting a report, by a terminal device, on the validity period of a GLONASS fixation to a network device.

[157] Let us consider Fig. 6, which is a flow chart of an algorithm for a method for processing the reliability of a GLONASS fixation, proposed in one of the examples of implementing the present invention. This embodiment of the present invention is described using the example of a method used in a terminal device of the communication system shown in Fig. 1 or 2. The method may include the steps described below.

[158] Step 501: The GLONASS fix validity period is transmitted to the network device.

[159] In one embodiment, the terminal device may receive a GLONASS location fix and a validity period of the GLONASS location fix. The terminal device receives the validity period of the GLONASS fix in a manner pre-configured in the GLONASS system. As an example, the terminal device may receive the validity period of the GLONASS fix from the GPS module of the terminal device.

[160] In this embodiment of the present invention, a plurality of trigger conditions, report contents and methods for transmitting a report for a terminal device on the validity period of a GLONASS fixation are accordingly proposed. The mentioned multiple trigger conditions, report contents and report methods can be combined arbitrarily.

[161] In one embodiment, this embodiment of the present invention provides two trigger conditions for transmitting a GLONASS fix validity period report by a terminal device, as described below.

[162] 1) After the terminal device receives the latest GLONASS location fix, it initiates a report on the validity period of the GLONASS fix.

[163] When a terminal device receives a GLONASS location fix, it transmits the GLONASS fix validity period to the network device.

[164] 2) The network device instructs the terminal device whether to transmit a GLONASS fix reliability period report using a system message and/or a special RRC message. The terminal device transmits a GLONASS fix reliability period report upon receiving the instruction from the network device.

[165] The terminal device may receive a first instruction transmitted by the network device using a system message; and/or the terminal device may receive a first instruction transmitted by the network device using a dedicated radio resource control (RRC) message; wherein the first instruction is configured to instruct the terminal device to transmit a GLONASS fix validity period report, or the first instruction is configured to instruct the terminal device not to transmit a GLONASS fix validity period report. The terminal device transmits the GLONASS fix validity period to the network device in response to the first instruction instructing the terminal device to transmit a GLONASS fix validity period report.

[166] In one embodiment, this embodiment of the present invention provides two methods for transmitting a report by a terminal device on the validity period (fixation) of GLONASS, described below.

[167] 1) The terminal device transmits a report in a random access message (msg5).

[168] The terminal device may transmit a random access message (msg5) to the network device, where the random access message contains the validity period of the GLONASS fix.

[169] Namely, the validity period of the GLONASS fix may be postponed in the connection establishment completion message/connection restoration completion message/connection re-establishment completion message.

[170] That is, the terminal device transmits a message about the completion of the connection establishment / a message about the completion of the connection restoration / a message about the completion of the re-establishment of the connection to the network device, wherein the message about the completion of the connection establishment / a message about the completion of the connection restoration / a message about the completion of the re-establishment of the connection contains the validity period of the GLONASS fixation.

[171] 2) After the terminal device enters the connected state, it transmits a report using a special RRC message.

[172] The terminal device may transmit a GLONASS fix validity period report using a terminal device auxiliary information message. Alternatively, after the network device requests a GLONASS fix validity period report from the terminal device in a terminal device information request, the terminal device transmits a GLONASS fix validity period report using a terminal device information response message.

[173] The terminal device may transmit a special RRC message to the network device, wherein the special RRC message contains the validity period of the GLONASS fix.

[174] For example, the terminal may receive a terminal device information request transmitted by a network device, wherein the terminal device information request is configured to request from the terminal device a report on the validity period of a GLONASS fix; the terminal device transmits a terminal device information response to the network device in response to the terminal device information request, wherein the terminal device information response contains the validity period of a GLONASS fix.

[175] In one embodiment, this embodiment of the present invention provides two report contents, described below, by the terminal device, on the validity period of the GLONASS fixation.

[176] 1) If the validity period of the GLONASS fix is less than the validity period of the ephemeris information/general TA, then a report on the validity period of the GLONASS fix is transmitted. The validity period of the ephemeris information/general TA is the remaining validity period of the ephemeris information/general TA.

[177] The terminal device may transmit the validity period of the GLONASS fix to the network device in the case where the validity period of the GLONASS fix is less than the first validity period; in this case, the first validity period is the validity period of the ephemeris information/total time synchronization (TA). Alternatively, the first validity period may be the remaining validity period of the ephemeris information or total time synchronization.

[178] 2) the terminal device transmits in the report the minimum of the following: the GLONASS fixation reliability period or the ephemeris information/total TA reliability period.

[179] The terminal device may transmit a second validity period to the network device, wherein the second validity period is a value that is less than the validity period of the GLONASS fix and the first validity period; wherein the first validity period is the validity period of the ephemeris information or the general time synchronization. Alternatively, the first validity period may be the remaining validity period of the ephemeris information or the general time synchronization.

[180] Thus, the technical solution proposed in this embodiment of the present invention makes it possible to obtain a solution for transmitting a report on the reliability period of GLONASS fixation. A plurality of trigger conditions, reporting methods and report contents are proposed for transmitting by a terminal device on the reliability period of GLONASS fixation, which makes it possible to improve the data processing mechanism associated with the reliability of GLONASS fixation.

[181] It should be understood that in response to the transmission by the terminal device of a report on the validity period of the GLONASS fixation to the network device in accordance with the above description, after the validity period has expired, the actions of the terminal device and subsequent processing methods have been described in detail above and will not be repeated further.

[182] Embodiments of the device according to the present invention that can be configured to perform embodiments of the proposed method are discussed below. For details not described in the embodiments of the device according to the present invention, reference should be made to the embodiments of the proposed method.

[183] Let us consider Fig. 7, which shows a block diagram of a device for processing the reliability of GLONASS fixation, proposed in one of the embodiments of the present invention. The proposed device has functions for implementing the above-described examples of the method on the side of the terminal device, and its functions can be implemented using hardware or by executing appropriate software on hardware. The proposed device can be a terminal device described above, or can be located inside a terminal device. According to the illustration of Fig. 7, the device can include:

[184] a 604 assignment module configured to set a target radio link failure (RLF) parameter in the event that the GLONASS fix of the terminal device is out of date.

[185] In one embodiment of the present invention, the device further comprises:

[186] a declaration module 606 configured to declare the RLF of a main cell group (MCG) in the event that the GLONASS (fixation) of the terminal device is obsolete.

[187] The assignment module 604 is configured to write the target parameters to the RLF variable report.

[188] In one embodiment of the present invention, the assignment module 604 is configured to set the connection failure type to “RLF”;

[189] and/or,

[190] Assignment module 604 is configured to set the RLF reason to "GLONASS fix aging".

[191] In one embodiment of the present invention, the device further comprises:

[192] a state module 607 configured to return to an idle state in the event that access layer security is not activated;

[193] or,

[194] a state module 607 configured to return to an idle state in the event that access layer security is activated.

[195] In one embodiment of the present invention, the assignment module 604 is configured to set the radio resource control (RRC) connection reset reason to “other”;

[196] or,

[197] the assignment module 604 is configured to set the RRC connection reset reason to "GLONASS fix aging";

[198] or,

[199] The assignment module 604 is configured to set the RRC connection reset reason to “RRC connection failure”.

[200] In one embodiment of the present invention, the device further comprises:

[201] a state module 607 configured to continue to remain in a connected state.

[202] In one embodiment of the present invention, the device further comprises:

[203] a first receiving module 603 configured to receive a configuration message transmitted by a network device; wherein

[204] a configuration message is configured to configure the terminal device to return to the idle state in the event that the GLONASS fix is expired; or

[205] Configuration message configured to configure the terminal device to remain in a connected state in case the GLONASS fix is out of date.

[206] In one embodiment of the present invention, the device further comprises:

[207] a first transmission module 605 configured to transmit a first message to a network device, wherein

[208] the first message is configured to indicate that the terminal device maintains a connected state in the event that the GLONASS fix is out of date; or

[209] The first message is configured to indicate that the terminal device does not support staying in a connected state in the case where the GLONASS fix is out of date.

[210] In one embodiment of the present invention, the device further comprises:

[211] a transmission module 601 configured to prohibit uplink transmission in the event that the GLONASS fix of the terminal device is outdated.

[212] In one embodiment of the present invention, the device further comprises:

[213] a transmission module 601 configured to not monitor the physical downlink control channel (PDCCH) in the event that the GLONASS fix of the terminal device is stale; or

[214] a transmission module 601 configured to not perform downlink reception in the event that the GLONASS fix of the terminal device is out of date.

[215] In one embodiment of the present invention, the terminal device includes a medium access control (MAC) layer;

[216] the transmission module 601 is configured to determine that the time synchronization timer has expired in the event that the GLONASS fix of the terminal device has become stale; and

[217] the transmission module 601 is configured to perform a processing procedure associated with the expiration of the time synchronization timer.

[218] In one embodiment of the present invention, the transmission module 601 is configured to determine that both the timing synchronization timers of the primary timing advance group (pTAG) and the secondary timing advance group (sTAG) have expired; or

[219] the transmission module 601 is configured to determine that the pTAG time alignment timer has expired.

[220] In one embodiment of the present invention, the device further comprises:

[221] a transmission module 601 configured to prohibit initiation of random access in the event that the GLONASS fix of the terminal device is out of date.

[222] In one embodiment of the present invention, the terminal device includes a medium access control (MAC) layer and a physical layer (PHY).

[223] In one embodiment of the present invention, the terminal device includes a radio resource control (RRC) layer;

[224] the transmission module 601 is configured to reset or deactivate the physical uplink control channel (PUCCH) and/or the short physical uplink control channel (SPUCCH) of the serving cell in the event that the GLONASS fix of the terminal device is outdated;

[225] the transmission module 601 is configured to reset or deactivate the semi-persistent scheduling (SPS) of the serving cell in the event that the GLONASS fix of the terminal device is outdated; or

[226] the transmission module 601 is configured to reset or deactivate the dedicated scheduling request (SR) resource of the serving cell in the case where the GLONASS fix of the terminal device is outdated and the terminal device is a narrowband Internet of Things (NB-IOT) device.

[227] In one embodiment of the present invention, the transmission module 601 is configured to restore the PUCCH or SPUCCH of the deactivated serving cell in case of receiving a GLONASS location fix;

[228] the transmission module 601 is configured to restore the SPS of the deactivated serving cell in the event of receiving a GLONASS position fix; or

[229] the transmission module 601 is configured to restore the allocated SR resource of the deactivated serving cell in the case where a GLONASS location fix is received and when the terminal device is an NB-IOT device.

[230] In one embodiment of the present invention, the terminal device includes a medium access control (MAC) layer;

[231] the transmission module 601 is configured to clear the HARQ buffer of the serving cell in the event that the GLONASS fix of the terminal device is out of date;

[232] module 601 is configured to notify the radio resource control (RRC) layer of the reset or deactivation of the sounding reference signal (SRS) resources of the serving cell in the event that the GLONASS fix of the terminal device is outdated;

[233] the transmission module 601 is configured to clear or deactivate the configured downlink assignments and uplink grants in the event that the GLONASS fix of the terminal device is out of date;

[234] the transmission module 601 is configured to clear or deactivate the physical uplink shared communication channel (PUSCH) resource signaled by the semi-persistent channel state information (CSI) in the event that the GLONASS fix of the terminal device is stale; or

[235] The transmission module 601 is configured to prohibit uplink transmission in the event that the GLONASS fix of the terminal device is out of date.

[236] In one embodiment of the present invention, the transmission module 601 is configured to make downlink assignments and uplink grants in the event of receiving a GLONASS position fix.

[237] In one embodiment of the present invention, the transmission module 601 is configured to recover uplink transmissions in the event of receiving a GLONASS location fix.

[238] In one embodiment of the present invention, the transmitting module 601 is configured to restore downlink reception in the event of receiving a GLONASS position fix.

[239] In one embodiment of the present invention, the device further comprises:

[240] a first transmission module 605 configured to transmit a GLONASS fix validity period to a network device in the event of receiving a GLONASS location fix; or

[241] a first transmitting module 605 configured to transmit a master cell group (MCG) RLF to a network device in the event of receiving a GLONASS location fix.

[242] In one embodiment of the present invention, the device further comprises:

[243] an execution module 602 configured to execute a random access procedure in the event of receiving a GLONASS location fix;

[244] an execution module 602 configured to perform a connection re-establishment procedure in the event of receiving a GLONASS location fix.

[245] In one embodiment of the present invention, the device further comprises:

[246] a first receiving module 603 configured to receive a GLONASS location fix within a time window.

[247] In one embodiment of the present invention, the device further comprises:

[248] a transmission module 601 configured to not perform uplink transmissions or downlink receptions within said time window.

[249] In one embodiment of the present invention, the device further comprises:

[250] a first receiving module 603 configured to receive time window configuration information transmitted by a network device.

[251] Let us consider Fig. 8, which shows a block diagram of a device for processing the reliability of GLONASS fixation, proposed in one of the embodiments of the present invention. The proposed device has functions for implementing the above-described examples of the method on the side of the terminal device, and its functions can be implemented using hardware or by executing appropriate software on hardware. The proposed device can be a terminal device described above, or can be located inside a terminal device. According to the illustration of Fig. 8, the device can include:

[252] a second transmission module 701 configured to transmit the GLONASS fixation validity period to the network device;

[253] In one embodiment of the present invention, the second transmitting module 701 is configured to transmit a random access message to the network device, wherein the random access message comprises a validity period of the GLONASS fix.

[254] In one embodiment of the present invention, the second transmitting module 701 is configured to transmit a special radio resource control (RRC) message to the network device, wherein the special RRC message contains a validity period of the GLONASS fix.

[255] In one embodiment of the present invention, the device further comprises:

[256] a second receiving module 702 configured to receive a request for terminal device information transmitted by a network device, wherein the request for terminal device information is configured to request from the terminal device a report on the validity period of the GLONASS fixation;

[257] the second transmission module 701 is configured to transmit a response of the terminal device information to the network device, wherein the response of the terminal device information contains a validity period of the GLONASS fixation.

[258] In one embodiment of the present invention, the second transmitting module 701 is configured to transmit the GLONASS fix validity period to the network device in a case where the GLONASS fix validity period is less than the first validity period;

[259] The first period of reliability is the period of reliability of ephemeris information or general time synchronization.

[260] In one embodiment of the present invention, the second transmitting module 701 is configured to transmit a second validity period to the network device, wherein the second validity period is a value less than the validity period of the GLONASS fix and the first validity period;

[261] The first period of reliability is the period of reliability of ephemeris information or general time synchronization.

[262] In one embodiment of the present invention, the second transmitting module 701 is configured to transmit a GLONASS fix validity period to the network device in the event of receiving a GLONASS location fix.

[263] In one embodiment of the present invention, the device further comprises:

[264] a second receiving module 702 configured to receive a first instruction transmitted by the network device via a system message;

[265] and/or,

[266] a second receiving module 702 configured to receive a first instruction transmitted by a network device using a dedicated radio resource control (RRC) message;

[267] wherein the first instruction is configured to instruct the terminal device to transmit a report on the validity period of the GLONASS fix, or the first instruction is configured to instruct the terminal device not to transmit a report on the validity period of the GLONASS fix.

[268] It should be noted that in the case where the device proposed in the above embodiments of the present invention performs its functions, its division into the described functional modules is carried out solely as an example. In practice, the above-described distribution of functions can be achieved by other functional modules, depending on actual needs. That is, the internal structure of the device, in order to perform all or part of the functions described above, can be divided into other functional modules.

[269] For a detailed description of the operations of each of the modules of the device described above, reference should be made to the previously given embodiments of the present invention related to the method. Their description will not be repeated here.

[270] Referring to Fig. 9, a block diagram of a communication device (terminal device or network device) proposed in one embodiment of the present invention is shown. The communication device may include: a processor 901, a receiver 902, a transmitter 903, a memory 904, and a bus 905.

[271] The processor 901 includes one or more processor cores. The processor 901 executes various functional applications and processes the reliability of GLONASS fixation by executing computer programs and modules.

[272] The receiver 902 and the transmitter 903 may be implemented as a transceiver 906, wherein the transceiver 906 may be a communication chip.

[273] Memory 904 is connected to processor 901 via bus 905.

[274] Memory 904 may be configured to store a computer program, and processor 901 may be configured to execute the computer program, which causes the communication device to perform the various steps of the above-described embodiments of the present invention related to the method.

[275] The memory 904 may be implemented using any type of volatile or nonvolatile memory device or combination thereof, including, but not limited to, random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other semiconductor storage technologies, compact disc read-only memory (CD-ROM), high-density digital video disc (DVD) or other optical storage device, tape cassette, tape, disk storage device, or other magnetic storage device.

[276] When the communication device is in the form of a terminal device, the processor 901 used in the embodiments of the present invention may perform the steps performed by the terminal device in any of the methods illustrated in Figs. 3-6 above, which will not be described again here.

[277] In one possible implementation, when the communication device is implemented in the form of a terminal device,

[278] The processor is configured to set a target radio link failure (RLF) parameter in the event that the global navigation satellite system (GLONASS) fix of the terminal device is out of date.

[279] In one possible implementation, when the communication device is implemented in the form of a terminal device,

[280] The transceiver is configured to transmit a global navigation satellite system (GLONASS) fix validity period to a network device.

[281] In one embodiment of the present invention, a machine-readable data carrier is further provided. A computer program is stored on the machine-readable data carrier, wherein the computer program is used for execution by the processor of the core network device for the purpose of performing the above-described method for processing the reliability of GLONASS fixation by the terminal device.

[282] The computer-readable storage medium may include, but is not limited to, read-only memory (ROM), random access memory (RAM), a solid-state drive (SSD), or an optical disk. RAM may include resistive random access memory (ReRAM) and dynamic random access memory (DRAM).

[283] In one embodiment of the present invention, a microcircuit is also proposed. The proposed microcircuit includes a programmable logic circuit and/or program instructions, and in the case where the microcircuit operates in a terminal device, it is used to implement the above-described method for processing the reliability of GLONASS fixation by a terminal device.

[284] In one embodiment of the present invention, a computer program product or a computer program is also proposed. The computer program product or the computer program includes computer instructions, wherein the computer instructions are stored on a machine-readable data carrier. The processor of the terminal device reads the computer instructions from the machine-readable data carrier and executes the computer instructions for the purpose of performing the above-described method for processing the reliability of GLONASS fixation by the terminal device.

[285] It should be understood that “indication” in embodiments of the present invention may be either a direct indication or an indirect indication, and may also mean that there is a correspondence relationship. As an example, “A indicates B” may mean that A directly indicates B, for example, B can be obtained through A; it may also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it may also mean that there is a correspondence relationship between A and B.

[286] In describing embodiments of the present invention, the term “corresponding” may mean that there is a direct correspondence or an indirect correspondence between two elements, or that there is an associative relationship between them, or a relationship of indicating and indicated, configuring and configured, and the like.

[287] "Plurality" in this document means two or more. "And/or" describes the relationship of connection between the corresponding objects and indicates that three types of relationships are possible, for example, "A and/or B" can mean: only A is present, A and B are present at the same time, or only B is present. The symbol "/" generally indicates that the corresponding objects are related by an "or" relationship.

[288] In this case, the numbering of the steps described in this document shows only an example of a possible sequence of execution of these steps. In other embodiments of the present invention, these steps do not necessarily have to be executed according to the numbering order, for example, steps with two different numbers can be executed simultaneously, or steps with two different numbers can be executed in the reverse order shown in the drawings, without limiting the present invention in this regard.

[289] Those skilled in the art will understand that in the one or more examples discussed above, the functions described in the embodiments of the present invention may be implemented using hardware, software, firmware, or any combination thereof. If implemented as software, the functions may be stored on or transmitted over as one or more instructions or codes on a computer-readable storage medium. A computer-readable storage medium may include both a computer storage medium and a communication medium, where the communication medium may include any media that enables transfer of a computer program from one place to another. The storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[290] The description above is merely a description of preferred options.

Claims (98)

1. A method for determining the reliability of the fixation of the global navigation satellite system (GLONASS), performed by a terminal device and including: transmission of the GLONASS fixation reliability period to the network device, wherein the GLONASS fixation reliability period is transferred in the connection establishment completion message/connection restoration completion message/reconnection re-establishment completion message; and return to idle state when GLONASS location is out of date and set RRC connection reset reason to "other". 2. The method according to item 1, in which the setting of the target parameter RLF, in the case when the fixation of the GLONASS location of the terminal device is outdated, includes: declaration of the RLF of the main cell group (MCG) in case the GLONASS location fix of the terminal device is outdated; and Write the target parameter to the RLF variable report. 3. The method of claim 2, wherein recording the target parameter in the RLF variable report includes at least one of the following: setting the connection failure type to "RLF"; or assigning the RLF reason as "GLONASS fixation obsolescence". 4. The method according to paragraph 1, also including: return to idle state when access layer security is not enabled; or return to idle state when access layer security is activated, or also including: continued stay in a connected state. 5. The method according to paragraph 4, also including one of the following: Set the Radio Resource Control (RRC) connection reset reason to "other"; setting the RRC connection reset reason to "GLONASS fix expiration"; or Set the RRC connection reset reason to "RRC connection failure". 6. The method according to paragraph 4, also including: receiving a configuration message transmitted by a network device, while the configuration message is configured to configure the terminal device to return to the idle state in the event that the GLONASS position fix is out of date; or the configuration message is configured to configure the terminal device to continue to stay in the connected state in the case where the GLONASS location fix is out of date, the method also includes: transmitting the first message to the network device, while the first message is configured to indicate that the terminal device supports continuing to be in a connected state in the event that the GLONASS location fix is out of date; or The first message is configured to indicate that the terminal device does not support remaining in a connected state in the event that the GLONASS location fix is out of date. 7. The method according to paragraph 1, also including: prohibition of transmission on the uplink in the case when the GLONASS location fixation of the terminal device is outdated, the method also includes: restoration of uplink transmission in case of receiving GLONASS location fix. 8. The method according to claim 1, further comprising at least one of the following: failure to monitor the physical downlink control channel (PDCCH) when the terminal device's GLONASS location fix is out of date; or failure to receive downlink communication when the GLONASS location fix of the terminal device is outdated, the method also includes: restoration of downlink reception in the event of receiving a GLONASS location fix. 9. The method of claim 7, wherein the terminal device includes a medium access control (MAC) layer; and prohibition of transmission on the uplink in the case when the GLONASS location fixation of the terminal device is outdated, includes: determining that the time synchronization timer has expired in the event that the GLONASS location fix of the terminal device is out of date; and execution of the processing procedure associated with the expiration of the time synchronization timer, wherein determining that the time synchronization timer has expired includes at least one of the following: determining that both the primary timing advance group (pTAG) and secondary timing advance group (sTAG) timing timers have expired; or determining that the pTAG time synchronization timer has expired, the method also includes: prohibition of initiation of random access in the case when the GLONASS location fixation of the terminal device is outdated. 10. The method according to claim 7, wherein the terminal device includes a radio resource control (RRC) layer, and prohibiting transmission on the uplink in the case when the GLONASS location fix of the terminal device is outdated, includes at least one of the following: resetting or deactivating the physical uplink control channel (PUCCH) and/or the short physical uplink control channel (SPUCCH) of the serving cell in the event that the GLONASS location fix of the terminal device is outdated; resetting or deactivating the semi-persistent scheduling (SPS) of the serving cell in the event that the GLONASS location fix of the terminal device is outdated; or resetting or deactivating the dedicated scheduling request (SR) resource of the serving cell in the case where the GLONASS location fix of the terminal device is outdated and the terminal device is a narrowband Internet of Things (NB-IOT) device, wherein the method also includes at least one of the following: restoration of PUCCH or SPUCCH of a deactivated serving cell in case of receiving a GLONASS location fix; restoration of SPS of a deactivated serving cell in case of receiving a GLONASS location fix; or restoration of a deactivated dedicated SR resource in the case where a GLONASS location fix is received and when the terminal device is an NB-IOT device. 11. The method of claim 7, wherein the terminal device includes a MAC layer; and prohibiting uplink transmission in the case where the GLONASS location fix of the terminal device is out of date includes at least one of the following: clearing the hybrid automatic repeat request (HARQ) buffer of the serving cell in the event that the GLONASS location fix of the terminal device is outdated; notification to the radio resource control (RRC) layer of the reset or deactivation of the resource of the physical uplink control channel (PUCCH) of the serving cell in the event that the GLONASS location fix of the terminal device is outdated; notification to the radio resource control (RRC) layer of the reset or deactivation of the sounding reference signal (SRS) resources of the serving cell in the event that the GLONASS location fix of the terminal device is outdated; clearing or deactivating configured downlink assignments and uplink permissions when the terminal device's GLONASS location fix is out of date; clearing or deactivating the physical uplink shared communication channel (PUSCH) resource signaled by means of semi-persistent channel state information (CSI) when the GLONASS location fix of the terminal device is out of date; or prohibition of transmission on the uplink in the case when the GLONASS location fixation of the terminal device is outdated, the method also includes: restore deactivated downlink assignments and uplink clearances in the event of receiving a GLONASS position fix. 12. The method according to claim 1, further comprising at least one of the following: transmission of the GLONASS fixation reliability period to the network device, whereby the GLONASS fixation reliability period is carried over in the connection establishment message; or transmitting MCG RLF to a network device in the event of receiving a GLONASS location fix, or also including: obtaining GLONASS location fixation within a time window, the method also includes: failure to transmit on the uplink or receive on the downlink within the said time window, or receiving time window configuration information transmitted by a network device. 13. The method of claim 4, further comprising at least one of the following: performing a random access procedure in the event of obtaining a GLONASS location fix; or performing the procedure for re-establishing a connection in the event of receiving a GLONASS location fix. 14. The method according to paragraph 1, wherein the transmission of the GLONASS fixation reliability period to the network device includes: transmission of a random access message to a network device, wherein the random access message contains the validity period of the GLONASS fixation, or transmission of a special radio resource control (RRC) message to a network device, wherein the special RRC message contains the validity period of the GLONASS fixation, the method also includes: receiving a request for information from a terminal device transmitted by a network device, wherein the request for information from a terminal device is configured to request a report from the terminal device on the validity period of the GLONASS fixation; wherein the transmission of a special radio resource control (RRC) message to the network device includes: transmission of the response information of the terminal device to the network device, wherein the response information of the terminal device includes the period of reliability of the GLONASS fixation. 15. The method according to paragraph 1, wherein the transmission of the GLONASS fixation reliability period to the network device includes: transmission of the GLONASS fixation reliability period to the network device in the event that the GLONASS fixation reliability period is less than the first reliability period; In this case, the first period of reliability is the period of reliability of ephemeris information or general time synchronization. 16. The method according to paragraph 1, also including: transmission of the second reliability period to the network device, where the second reliability period is the lesser of the GLONASS fixation reliability period and the first reliability period; In this case, the first period of reliability is the period of reliability of ephemeris information or general time synchronization. 17. The method according to paragraph 1, wherein the transmission of the GLONASS fixation reliability period to the network device includes: transmission of the validity period of the GLONASS fixation to the network device in the event of receiving a GLONASS location fixation. 18. The method of claim 1, further comprising at least one of the following: receiving the first instruction transmitted by a network device using a system message; or receiving the first instruction transmitted by a network device using a special radio resource control (RRC) message; wherein the first instruction is configured to instruct the terminal device to transmit a report on the validity period of the GLONASS fix, or the first instruction is configured to instruct the terminal device not to transmit a report on the validity period of the GLONASS fix. 19. A terminal device (UE), comprising: memory; and CPU; wherein the processor, when executing the computer program stored in the memory, is configured to perform a method for determining the reliability of the fixation of the global navigation satellite system (GLONASS) according to any of paragraphs 1-18.

Images