WO2023123514A1 - Gnss有效性的处理方法、装置、设备及存储介质 - Google Patents

Gnss有效性的处理方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2023123514A1
WO2023123514A1 PCT/CN2021/144061 CN2021144061W WO2023123514A1 WO 2023123514 A1 WO2023123514 A1 WO 2023123514A1 CN 2021144061 W CN2021144061 W CN 2021144061W WO 2023123514 A1 WO2023123514 A1 WO 2023123514A1
Authority
WO
WIPO (PCT)
Prior art keywords
gnss
terminal device
validity period
times out
rlf
Prior art date
Application number
PCT/CN2021/144061
Other languages
English (en)
French (fr)
Inventor
江小威
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN202180004809.XA priority Critical patent/CN114503783A/zh
Priority to PCT/CN2021/144061 priority patent/WO2023123514A1/zh
Publication of WO2023123514A1 publication Critical patent/WO2023123514A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • Embodiments of the present disclosure relate to the field of communication technologies, and in particular, to a GNSS validity processing method, device, device, and storage medium.
  • the GNSS position fix (positioning) obtained by the terminal device has a validity period, and the validity of the GNSS position fix can only be maintained for a period of time. After the validity period is exceeded, the GNSS of the terminal device is outdated (timed out). The terminal device needs to reacquire GNSS.
  • IoT Internet of Things
  • GNSS Global Navigation Satellite System, Global Navigation Satellite System
  • LTE Long Term Evolution, Long Term Evolution
  • Embodiments of the present disclosure provide a GNSS validity processing method, device, device, and storage medium, which can provide a solution for the GNSS validity. Described technical scheme is as follows:
  • a method for processing GNSS validity is provided, the method is executed by a terminal device, and the method includes:
  • the target parameter of the radio link failure RLF is set.
  • a method for processing GNSS validity is provided, the method is executed by a terminal device, and the method includes:
  • GNSS Global Navigation Satellite System
  • an apparatus for processing GNSS validity is provided, the apparatus is used to implement a terminal device, and the apparatus includes:
  • the setting module is used to set the target parameter of the radio link failure RLF under the condition that the global navigation satellite system (GNSS) of the terminal device is overtime.
  • GNSS global navigation satellite system
  • an apparatus for processing GNSS validity is provided, the apparatus is used to implement a terminal device, and the apparatus includes:
  • the second sending module is configured to send the GNSS validity period to the network device.
  • a terminal device includes a processor
  • the processor is configured to set the target parameter of the radio link failure RLF when the global navigation satellite system (GNSS) of the terminal device times out.
  • GNSS global navigation satellite system
  • a terminal device includes a transceiver
  • the transceiver is used to send the validity period of the Global Navigation Satellite System (GNSS) to the network equipment.
  • GNSS Global Navigation Satellite System
  • a computer-readable storage medium is provided, and a computer program is stored in the storage medium, and the computer program is used for execution by a processor, so as to implement the above-mentioned method for processing GNSS validity.
  • a chip includes a programmable logic circuit and/or program instructions, and when the chip is running, it is used to implement the above-mentioned GNSS validity processing method.
  • a computer program product or computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium, and a processor reads from the The computer-readable storage medium reads and executes the computer instructions, so as to realize the above-mentioned processing method of GNSS validity.
  • GNSS timeout uses RLF (Radio Link Failure, wireless link failure) to record relevant information; after obtaining the validity period of GNSS, report the validity period of GNSS to the network equipment, and improve the processing mechanism related to GNSS validity.
  • RLF Radio Link Failure, wireless link failure
  • Fig. 1 is a schematic diagram of a communication system provided by an exemplary embodiment of the present disclosure
  • Fig. 2 is a schematic diagram of a communication system provided by an exemplary embodiment of the present disclosure
  • FIG. 3 is a flow chart of a method for processing GNSS validity provided by an exemplary embodiment of the present disclosure
  • FIG. 4 is a flow chart of a method for processing GNSS validity provided by an exemplary embodiment of the present disclosure
  • FIG. 5 is a flow chart of a GNSS validity processing method provided by an exemplary embodiment of the present disclosure
  • FIG. 6 is a flowchart of a method for processing GNSS validity provided by an exemplary embodiment of the present disclosure
  • Fig. 7 is a block diagram of a device for processing GNSS validity provided by an exemplary embodiment of the present disclosure
  • Fig. 8 is a block diagram of a device for processing GNSS validity provided by an exemplary embodiment of the present disclosure
  • Fig. 9 is a schematic structural diagram of a communication device provided by an exemplary embodiment of the present disclosure.
  • the network architecture and business scenarios described in the embodiments of the present disclosure are to illustrate the technical solutions of the embodiments of the present disclosure more clearly, and do not constitute a limitation to the technical solutions provided by the embodiments of the present disclosure.
  • the evolution of technology and the emergence of new business scenarios, the technical solutions provided by the embodiments of the present disclosure are also applicable to similar technical problems.
  • NTN Non-terrestrial Network
  • Satellite communication is not restricted by the user's region. For example, general land communication cannot cover areas such as oceans, mountains, deserts, etc. that cannot be equipped with communication equipment or are not covered by communication due to sparse population. For satellite communication, due to a Satellites can cover a large area of the ground, and satellites can orbit the earth, so theoretically every corner of the earth can be covered by satellite communications. Secondly, satellite communication has great social value.
  • Satellite communication can be covered at a lower cost in remote mountainous areas, poor and backward countries or regions, so that people in these regions can enjoy advanced voice communication and mobile Internet technology, which is conducive to narrowing the digital gap with developed regions and promoting development of these areas.
  • the distance of satellite communication is long, and the cost of communication does not increase significantly with the increase of communication distance; finally, the stability of satellite communication is high, and it is not limited by natural disasters.
  • LEO Low-Earth Orbit
  • MEO Medium-Earth Orbit
  • GEO Geostationary Earth Orbit
  • HEO High Elliptical Orbit
  • the altitude range of low-orbit satellites is 500km to 1500km, and the corresponding orbital period is about 1.5 hours to 2 hours.
  • the signal propagation delay of single-hop communication between users is generally less than 20ms.
  • the maximum satellite visible time is 20 minutes.
  • the signal propagation distance is short, the link loss is small, and the requirements for the transmission power of the user terminal equipment are not high.
  • Satellites in geosynchronous orbit have an orbital altitude of 35786km and a period of 24 hours around the earth.
  • the signal propagation delay of single-hop communication between users is generally 250ms.
  • satellites use multiple beams to cover the ground.
  • a satellite can form dozens or even hundreds of beams to cover the ground; a satellite beam can cover tens to hundreds of kilometers in diameter. ground area.
  • Table 1 shows the satellite altitude, orbit and satellite coverage of a typical NTN network:
  • the RTT (Round Trip Time, round-trip time) from the terminal device to the access network device includes two parts, one is the RTT from the terminal device to the satellite link, which is the UE specific TA (terminal device specific time synchronization) part, and the other part is The RTT of the link from the satellite to the access network equipment, this part is the common (public) TA (Time Alignment, time synchronization) part. Part of the common TA can be compensated by the access network equipment, and the other part can be compensated by the terminal equipment. The portion compensated by the terminal device will be sent to the terminal device through a system message.
  • the network device will also broadcast the ephemeris information of the satellite to help the terminal device obtain the position of the satellite so as to calculate the RTT from the terminal device to the satellite. Due to the mobility of the satellite, the common TA and ephemeris information will change, so the ephemeris information and common TA broadcast in the system message have a validity period, which is called UL synchronization validity duration (uplink synchronization validity period). The ephemeris information and common TA share a UL synchronization validity duration. The value of UL synchronization validity duration is broadcast by the network device to the terminal device through the SIB.
  • UL synchronization validity duration uplink synchronization validity period
  • the terminal device will start the UL synchronization validity timer according to the ephemeris information in the broadcast message and the epoch time (starting effective time) corresponding to the common TA.
  • epoch time has three indication methods:
  • System message express indication a system message clearly broadcasts a SFN (System Frame Number, system frame number) and subframe number (subframe number) to indicate the epoch time.
  • SFN System Frame Number, system frame number
  • subframe number subframe number
  • the system message implies an indication: the end position of the SI window (window) of the SI (System Information, system information) containing ephemeris information and common TA information is used as the epoch time.
  • the network device provides SFN and subframe number to the terminal device through dedicated signaling to indicate the epoch time.
  • IOT terminal equipment includes: BL UE (Bandwidth reduction and low complexity UE, bandwidth reduction and low complexity terminal equipment), UE in CE mode (UE in Coverage Enhancement mode, terminal equipment in coverage enhancement mode), NB-IOT UE (Narrow At least one of Band Internet of Things UE, narrowband IoT terminal equipment).
  • Embodiments of the present disclosure may be applied in an NTN system, as shown in FIG. 1 and FIG. 2 .
  • FIG. 1 shows a schematic diagram of an NTN system
  • the communication satellites in the NTN system are transparent payload satellites.
  • 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 .
  • Communication between the terminal device 10 and the access network device 40 can be performed through an air interface (such as a Uu interface).
  • the access network device 40 can be deployed on the ground, and the uplink and downlink communication between the terminal device 10 and the access network device 40 can be relayed and transmitted through the satellite 20 and the NTN gateway 30 (usually located on the ground).
  • the terminal device 10 sends the uplink signal to the satellite 20, and the satellite 20 forwards the above uplink signal to the NTN gateway 30, and then the NTN gateway 30 forwards the above uplink signal to the access network device 40, followed by the access
  • the network device 40 sends the above-mentioned uplink signal to the core network device 50 .
  • the downlink signal from the core network equipment 50 is sent to the access network equipment 40, and the access network equipment 40 sends the downlink signal to the NTN gateway 30, and the NTN gateway 30 forwards the above downlink signal to the satellite 20, and then the The satellite 20 forwards the above-mentioned downlink signal to the terminal device 10 .
  • the satellite 20 has the function 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 (relay station).
  • FIG. 2 shows a schematic diagram of another NTN system.
  • the communication satellites in the NTN system are satellites of regenerative payload.
  • the NTN system includes: a terminal device 10 , a satellite 20 , an NTN gateway 30 and a core network device 50 .
  • the functions of the access network device 40 are integrated on the satellite 20 , that is, the satellite 20 has the functions of the access network device 40 .
  • Communication between the terminal device 10 and the satellite 20 can be performed through an air interface (such as a Uu interface).
  • the satellite 20 and the NTN gateway 30 (usually located on the ground) can communicate through a satellite radio interface (Satellite Radio Interface, SRI).
  • SRI Satellite Radio Interface
  • the satellite receives the signal, demodulates and decodes it, re-encodes and modulates it, and sends the regenerated signal through the satellite frequency band.
  • the terminal device 10 sends the uplink signal to the satellite 20, and the satellite 20 forwards the above uplink signal to the NTN gateway 30, and then the NTN gateway 30 sends the above uplink signal to the core network device 50.
  • the downlink signal from the core network device 50 is sent 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 .
  • the access network device 40 is a device for providing wireless communication services for the terminal device 10 .
  • a connection may be established between the access network device 40 and the terminal device 10, so as to perform communication through the connection, including signaling and data interaction.
  • the number of access network devices 40 may be multiple, and two adjacent access network devices 40 may also communicate in a wired or wireless manner.
  • the terminal device 10 can switch between different access network devices 40 , that is, establish connections with different access network devices 40 .
  • the access network device 40 in the cellular communication network may be a base station.
  • a base station is a device deployed in an access network to provide wireless communication functions for terminal equipment 10 .
  • the base station may include various forms of macro base stations, micro base stations, relay stations, access points and so on.
  • the names of devices with base station functions may be different. For example, in 5G NR systems, they are called gNodeB or gNB.
  • the name "base station" may change as communication technology evolves.
  • the above-mentioned devices that provide the wireless communication function for the terminal device 10 are collectively referred to as base stations or access network devices.
  • the terminal device 10 involved in the embodiments of the present disclosure may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems, as well as various forms of user Equipment (User Equipment, UE), mobile station (Mobile Station, MS), terminal device (terminal device) and so on.
  • UE User Equipment
  • MS Mobile Station
  • terminal device terminal device
  • the above-mentioned devices are collectively referred to as terminal devices.
  • UE is used in some places to represent “terminal equipment”.
  • the "network device” may be an access network device (such as a base station) or a satellite.
  • the NTN system may include multiple satellites 20 .
  • One satellite 20 may cover a certain ground area, and provide wireless communication services for the terminal devices 10 on the ground area.
  • the satellite 20 can orbit the earth, and by arranging a plurality of satellites 20, communication coverage of different areas on the earth's surface can be achieved.
  • LTE Long Term Evolution
  • 5G 5th Generation
  • 5G 5th Generation
  • an embodiment of the present disclosure provides a processing manner of a terminal device after a GNSS timeout.
  • FIG. 3 shows a flowchart of a method for processing GNSS validity provided by an embodiment of the present disclosure. This embodiment is described by taking the method applied to a terminal device in the communication system shown in FIG. 1 or FIG. 2 as an example.
  • the method may include the steps of:
  • Step 201 When the GNSS of the terminal device times out, set the target parameter of RLF (Radio Link Failure, wireless link failure).
  • RLF Radio Link Failure, wireless link failure
  • the terminal device may acquire GNSS positioning, and the GNSS positioning has a validity period, and when the validity period of the GNSS positioning expires, determine GNSS outdated (GNSS timeout). That is, the GNSS timeout means that the GNSS positioning exceeds the validity period of the GNSS.
  • the validity period of the GNSS positioning may be pre-configured by the GNSS system or agreed upon in an agreement, which is not limited in the present disclosure.
  • the terminal device acquires the GNSS validity period from a GPS (Global Positioning System, Global Positioning System) module of the terminal device.
  • GPS Global Positioning System, Global Positioning System
  • the terminal device determines the RLF, executes the RLF processing flow, and records the relevant parameters (target parameters) of the RLF according to the GNSS timeout.
  • the terminal equipment can perform at least one of the following: declare MCG (Master Cell Group, main cell group) RLF, in the RLF variable report (VarRLF-Report) Record the target parameters.
  • the target parameter in the RLF variable report includes at least one of connection failure type (connectionFailureType) and RLF cause (rlf-Cause).
  • connectionFailureType connection failure type
  • RLF cause RLF cause
  • the terminal device sets the connection failure type as RLF, and/or sets the RLF cause as GNSS timeout.
  • the terminal device needs to acquire the GNSS positioning again.
  • the embodiment of the present disclosure provides a method. After the GNSS timeout, the terminal device declares RLF, and stops uplink transmission and downlink reception until it obtains a new GNSS positioning until.
  • the technical solution provided by this embodiment provides a solution for GNSS timeout. After GNSS timeout, use RLF (Radio Link Failure, wireless link failure) to record relevant information and improve the processing mechanism related to GNSS validity.
  • RLF Radio Link Failure, wireless link failure
  • the terminal device may return to the idle state.
  • FIG. 4 shows a flowchart of a method for processing GNSS validity provided by an embodiment of the present disclosure. This embodiment is described by taking the method applied to a terminal device in the communication system shown in FIG. 1 or FIG. 2 as an example.
  • the method may include the steps of:
  • Step 301 Declare MCG RLF in case of GNSS timeout of the terminal device.
  • the terminal device declares (declare) MCG RLF to trigger the MCG RLF processing flow.
  • Step 302 Record the target parameters in the RLF variable report.
  • the terminal equipment records RLF related information in VarRLF-Report (RLF variable report), for example, setting connectionFailureType (connection failure type) is RLF in the RLF variable report; rlf-Cause (RLF reason) is set in the RLF variable report ) is GNSS outdated.
  • VarRLF-Report for example, setting connectionFailureType (connection failure type) is RLF in the RLF variable report; rlf-Cause (RLF reason) is set in the RLF variable report ) is GNSS outdated.
  • Step 303 Return to the idle state.
  • AS Access Stratum, access layer
  • security security
  • the terminal device when the access layer security of the terminal device is not activated, the terminal device returns to the idle state; or, when the access layer security is activated, the terminal device returns to the idle state.
  • Step 304 Set the release reason of the RRC (Radio Resource Control, radio resource control) connection.
  • RRC Radio Resource Control, radio resource control
  • the terminal device sets the release cause (release reason) to other (other), or GNSS outdated, or RRC connection failure (RRC connection failure). That is, set the release reason of the radio resource control RRC connection to other; or, set the release reason of the RRC connection to GNSS timeout; or set the release reason of the RRC connection to RRC connection failure.
  • Step 301, Step 302, Step 303, and Step 304 may be arbitrary. That is, the terminal device can first declare RLF after the GNSS timeout, and then return to the idle state; the terminal device can also return to the idle state after the GNSS timeout, and then declare the RLF. Embodiments of the present disclosure do not limit this.
  • the terminal device declares the RLF, sets the target parameter of the RLF, and returns to the idle state. Or, after the GNSS timeout, the terminal device returns to the idle state; declares the RLF, and sets the target parameters of the RLF.
  • the technical solution provided by this embodiment after GNSS timeout, declares RLF (Radio Link Failure, wireless link failure) and records relevant information, controls the terminal device to return from the connected state to the idle state, and according to the GNSS timeout To set the release reason of RRC connection, improve the processing mechanism related to GNSS validity.
  • RLF Radio Link Failure, wireless link failure
  • the terminal device may remain connected.
  • FIG. 5 shows a flowchart of a method for processing GNSS validity provided by an embodiment of the present disclosure. This embodiment is described by taking the method applied to a terminal device in the communication system shown in FIG. 1 or FIG. 2 as an example.
  • the method may include the steps of:
  • Step 401 Send a first message to the network device, where the first message is used to indicate whether to support maintaining the connection state after the GNSS times out.
  • the first message is used to indicate that the terminal device supports maintaining the connected state in the case of GNSS timeout, or the first message is used to indicate that the terminal device does not support maintaining the connected state in the case of GNSS timeout. connected state.
  • the terminal device reports whether it has the ability to remain in the connected state after GNSS outdated.
  • the network device is an access network device.
  • Step 402 Receive a configuration message sent by the network device, the configuration message is used to indicate whether to keep the connection state after the GNSS times out.
  • the configuration message is used to configure the terminal device to return to the idle state when the GNSS times out, or the configuration message is used to configure the terminal device to remain in the connected state when the GNSS times out.
  • the network device can configure the terminal device to return to the idle state after GNSS outdated, or to remain in the connected state.
  • the network device configures the terminal device to remain in the connection state when the GNSS timeout occurs, or the network device configures the terminal device to fall back to idle state. In the case that the terminal device does not support maintaining the connection state after the GNSS timeout, the network device configures the terminal device to return to the idle state when the GNSS timeout occurs.
  • step 403 to step 405 are performed.
  • Step 403 When the GNSS of the terminal device times out, keep the connected state.
  • the network device configures the terminal device to remain in the connected state after the GNSS timeout, and in the case of the GNSS timeout, the terminal device remains in the connected state.
  • Step 404 Declare MCG RLF in case of GNSS timeout of the terminal device.
  • the terminal device declares (declare) MCG RLF to trigger the MCG RLF processing flow.
  • Step 405 Record the target parameters in the RLF variable report.
  • the terminal equipment records RLF related information in VarRLF-Report (RLF variable report), for example, setting connectionFailureType (connection failure type) is RLF in the RLF variable report; rlf-Cause (RLF reason) is set in the RLF variable report ) is GNSS outdated.
  • VarRLF-Report for example, setting connectionFailureType (connection failure type) is RLF in the RLF variable report; rlf-Cause (RLF reason) is set in the RLF variable report ) is GNSS outdated.
  • the sequence of declaring the RLF and maintaining the connected state may be arbitrary. That is, the terminal device can first declare RLF after the GNSS timeout, and then maintain the connection state; the terminal device can also maintain the connection state after the GNSS timeout, and then declare RLF. Embodiments of the present disclosure do not limit this.
  • the terminal device declares the RLF, sets the target parameter of the RLF, and maintains the connected state. Or, after the GNSS timeout, the terminal device remains connected; declare RLF, and set the target parameters of RLF.
  • the terminal device can report to the network device whether it supports maintaining the connected state after the GNSS timeout, if the terminal device supports maintaining the connected state, and the network device instructs the terminal device to maintain the connected state , after the GNSS timeout, the terminal device can remain in the connected state, declare RLF (Radio Link Failure, wireless link failure) and record relevant information, and improve the processing mechanism related to GNSS validity.
  • RLF Radio Link Failure, wireless link failure
  • the terminal device After the GNSS timeout, the terminal device declares the RLF and switches or maintains the state. Then, when the GNSS times out and the terminal device has not acquired the latest GNSS positioning, the terminal device is prohibited from performing uplink transmission. That is, when the GNSS of the terminal device times out, the terminal device forbids uplink transmission.
  • the terminal device does not perform downlink reception either, that is, the terminal device no longer monitors a PDCCH (Physical Downlink Control Channel, physical downlink control channel), and no longer performs downlink reception. That is, when the GNSS of the terminal device times out, the terminal device does not monitor the PDCCH; or, when the GNSS of the terminal device times out, no downlink reception is performed.
  • a PDCCH Physical Downlink Control Channel, physical downlink control channel
  • the embodiment of the present disclosure provides the following two processing methods:
  • Mode 1 The terminal device can perform subsequent processing according to the uplink out-of-synchronization.
  • Method 2 The network device can configure a time window for the terminal device, and the terminal device obtains a new GNSS positioning within the time window, and does not perform uplink transmission and downlink reception within the time window.
  • the terminal device prohibits uplink transmission before obtaining the latest GNSS position fix.
  • the terminal device no longer monitors the PDCCH, and no longer performs downlink reception.
  • the embodiment of the present disclosure provides the following three processing methods:
  • the MAC (Medium Access Control, Media Access Control) layer of the terminal device considers that the timeAlignmentTimer (time alignment) has timed out.
  • the behavior of the MAC layer is processed according to the process after the timeAlignmentTimer expires. In this way, the terminal device will not initiate random access until it obtains the latest GNSS position fix.
  • the terminal device includes a MAC layer.
  • the MAC layer determines the time alignment timeout; and executes the time alignment timeout processing flow.
  • the terminal device is prohibited from initiating random access.
  • timeAlignmentTimer timeout includes thinking that all timeAlignmentTimers (including pTAG (Primary Timing Advance Group, primary timing advance group) and sTAG (Secondary Timing Advance Group, auxiliary timing advance group) respective timeAlignmentTimers) are timeout, or that the timeAlignmentTimer of pTAG is timeout .
  • the MAC layer determines that both pTAG and sTAG time-alignment timeout; or, determines the pTAG time-alignment timeout.
  • the terminal device includes a MAC layer and a PHY (Physical layer, physical layer).
  • the MAC layer/PHY of the terminal device temporarily prohibits any uplink transmission.
  • the MAC layer or the PHY prohibits uplink transmission.
  • the terminal equipment includes an RRC layer and a MAC layer.
  • the behaviors of the RRC layer and the MAC layer are respectively defined as follows:
  • the RRC layer After GNSS outdated, the RRC layer optionally performs at least one of the following actions 1) to 3):
  • the RRC layer releases or disables PUCCH (Physical Uplink Control Channel, Physical Uplink Control Channel)/SPUCCH (Short PUCCH, short PUCCH) of all serving cells (serving cells).
  • PUCCH Physical Uplink Control Channel
  • SPUCCH Short PUCCH, short PUCCH
  • the RRC layer releases or disables at least one of the PUCCH and SPUCCH of the serving cell.
  • the RRC layer releases or disables SPS (Semi-Persistent Scheduling, semi-persistent scheduling) of all serving cells.
  • SPS Semi-Persistent Scheduling, semi-persistent scheduling
  • the RRC layer releases or disables the SPS of the serving cell.
  • the RRC layer releases or disables all dedicated SR (Scheduling Request, uplink scheduling request) resources.
  • the RRC layer releases or disables the dedicated SR resource.
  • the RRC layer After obtaining the latest GNSS position fix, the RRC layer optionally performs at least one of the following actions 4) to 6):
  • the RRC layer restores the PUCCH/SPUCCH of all disabled serving cells.
  • the RRC layer releases or disables at least one of the PUCCH and SPUCCH of the serving cell. Then, when the GNSS positioning is obtained, the RRC layer restores the PUCCH or SPUCCH of the disabled serving cell.
  • the RRC layer releases or disables the SPS of the serving cell. Then, when the GNSS positioning is obtained, the RRC layer restores the SPS of the disabled serving cell.
  • the RRC layer restores all disabled dedicated SR resources.
  • the RRC layer releases or disables the dedicated SR resource. Then, when the GNSS positioning is obtained and the terminal device is an NB-IOT device, the RRC layer restores the disabled dedicated SR resource.
  • the MAC layer After GNSS outdated, the MAC layer optionally performs at least one of the following actions 7) to 12):
  • the MAC layer clears the HARQ (Hybrid Automatic Repeat reQuest, Hybrid Automatic Repeat) buffer (buffer) of all serving cells.
  • HARQ Hybrid Automatic Repeat reQuest, Hybrid Automatic Repeat
  • the MAC layer clears the HARQ buffer of the server cell.
  • the MAC layer notifies the RRC layer to release/disable the PUCCH resources of all serving cells.
  • the MAC layer notifies the RRC layer to release or disable the PUCCH resource of the serving cell.
  • the MAC layer notifies the RRC layer to release/disable SRS (Sounding Reference Signal, channel sounding reference signal) resources of all serving cells.
  • SRS Sounding Reference Signal, channel sounding reference signal
  • the MAC layer notifies the RRC layer to release or disable the SRS resource of the serving cell.
  • the MAC layer clears or disables all configured downlink assignments and uplink grants (configured downlink assignments and uplink grants).
  • the MAC layer clears or disables the configured downlink tasks and uplink grants.
  • the MAC layer clears/disables the PUSCH (Physical Uplink Shared Channel, physical uplink shared channel) resource reported by the semi-persistent CSI (Channel State Information, channel state information).
  • PUSCH Physical Uplink Shared Channel
  • semi-persistent CSI Channel State Information, channel state information
  • the MAC layer clears or disables the PUSCH resource reported by the CSI.
  • the MAC layer prohibits uplink transmission.
  • the MAC layer restores the disabled configured downlink assignments and uplink grants.
  • the MAC layer clears or disables the configured downlink task and uplink authorization. Then, when the GNSS positioning is obtained, the MAC layer restores the disabled configured downlink tasks and uplink grants.
  • the terminal device resumes uplink transmission and downlink reception after acquiring the latest GNSS position fix.
  • the terminal device triggers reporting of GNSS validity duration, or triggers random access, or triggers connection reestablishment.
  • the terminal device optionally reports the MCG RLF.
  • the terminal device resumes uplink transmission after obtaining the GNSS positioning.
  • the terminal device resumes downlink reception after obtaining the GNSS positioning.
  • the terminal device if the terminal device returns to the idle state when the GNSS timeout occurs, the terminal device performs a random access procedure when the GNSS positioning is obtained.
  • the terminal device executes a connection reestablishment process after obtaining the GNSS positioning.
  • the terminal device when it obtains the GNSS positioning, it sends the GNSS validity period to the network device.
  • the terminal device reports the MAC RLF to the network device when the GNSS positioning is obtained.
  • the terminal device sends the RLF variable report to the network device.
  • the terminal device receives the configuration information of the time window sent by the network device, and in response to the configuration information, does not perform LTE/NR (New Radio, new air interface) uplink transmission or downlink reception within the time window.
  • LTE/NR New Radio, new air interface
  • the terminal device acquires GNSS positioning in the time window.
  • the network device can issue a time window such as a measurement gap (measurement gap), and the terminal device does not perform NR/LTE uplink transmission or downlink reception during the measurement gap period, and the terminal device can acquire GNSS during the measurement gap period position.
  • a measurement gap measurement gap
  • the network device configures a time window for the terminal device in advance according to the validity period of the GNSS.
  • the start time of the time window is earlier than the timeout time of the validity period of the GNSS.
  • the terminal device does not perform uplink transmission or downlink reception within the time window, and acquires GNSS positioning within the time window. Before the end of the time window, the terminal device obtains the latest GNSS positioning. Then outside the time window, the GNSS positioning of the terminal device is always within the validity period.
  • an embodiment of the present disclosure provides a method for a terminal device to report a GNSS validity period to a network device.
  • FIG. 6 shows a flowchart of a method for processing GNSS validity provided by an embodiment of the present disclosure. This embodiment is described by taking the method applied to a terminal device in the communication system shown in FIG. 1 or FIG. 2 as an example.
  • the method may include the steps of:
  • Step 501 Send the GNSS validity period to the network device.
  • the terminal device obtains the GNSS positioning and the GNSS validity period of the GNSS positioning.
  • the GNSS validity period is obtained by the terminal device according to the pre-configuration of the GNSS system.
  • the terminal device obtains the validity period of the GNSS from the GPS module of the terminal device.
  • the embodiments of the present disclosure respectively provide multiple trigger conditions, report content and report methods for the terminal device to report the validity period of the GNSS.
  • Various trigger conditions, reporting content and reporting methods can be combined arbitrarily.
  • the embodiment of the present disclosure provides the following two conditions:
  • the terminal device After the terminal device obtains the latest GNSS position fix, it triggers the GNSS validity duration report.
  • the terminal device when the terminal device acquires the GNSS positioning, it sends the GNSS validity period to the network device.
  • the network device instructs the terminal device whether to report GNSS validity duration through system messages and/or RRC dedicated messages.
  • the terminal device reports the validity period of the GNSS after receiving the instruction from the network device.
  • the terminal device receives the first indication sent by the network device through a system message; and/or, the terminal device receives the first indication sent by the network device through a radio resource control RRC dedicated message; where the first indication is used to instruct the terminal device Reporting the validity period of the GNSS, or, the first indication is used to instruct the terminal device not to report the validity period of the GNSS.
  • the terminal device sends the GNSS validity period to the network device in response to instructing the terminal device to report the GNSS validity period in the first indication.
  • the embodiment of the present disclosure provides the following two methods:
  • the terminal device reports in msg5 of random access.
  • the terminal device sends a random access message (msg5) to the network device, and the random access message includes the validity period of the GNSS.
  • msg5 a random access message
  • the random access message includes the validity period of the GNSS.
  • the GNSS validity duration can be carried in the connection establishment complete/connection recovery complete/connection reestablishment complete message.
  • the terminal device sends a connection establishment complete message/connection restoration complete message/connection reestablishment complete message to the network device, and the connection establishment complete message/connection restoration complete message/connection reestablishment complete message includes the GNSS validity period.
  • the terminal device may report the validity period of the GNSS through a terminal device auxiliary information message.
  • the terminal device reports the GNSS validity period through the terminal device information response message.
  • the terminal device sends a dedicated RRC message to the network device, and the dedicated RRC message includes the validity period of the GNSS.
  • the terminal device receives the terminal device information request sent by the network device, and the terminal device information request is used to request the terminal device to report the GNSS validity period; the terminal device sends a terminal device information response to the network device in response to the terminal device information request, and the terminal device information response Include GNSS validity period.
  • the embodiment of the present disclosure provides the following two content:
  • the validity duration of the ephemeris information/common TA refers to the remaining validity (effective) duration of the ephemeris information/common TA.
  • the terminal device sends the GNSS validity period to the network device when the GNSS validity period is shorter than the first validity period; wherein, the first validity period is the validity period of ephemeris information or public time synchronization. Exemplarily, the first validity period is the remaining valid duration of the validity period of ephemeris information or public time synchronization.
  • the terminal device reports the minimum of GNSS validity duration and ephemeris/common TA validity duration.
  • the terminal device sends the second validity period to the network device, and the second validity period is the smaller value of the GNSS validity period and the first validity period; wherein, the first validity period is the validity period of ephemeris information or public time synchronization. Exemplarily, the first validity period is the remaining valid duration of the validity period of ephemeris information or public time synchronization.
  • the technical solution provided by this embodiment provides a solution for GNSS validity period reporting.
  • a variety of trigger conditions, reporting methods, and reporting content for terminal equipment to report GNSS validity period are given, and the processing mechanism related to GNSS validity is improved.
  • FIG. 7 shows a block diagram of an apparatus for processing GNSS validity provided by an embodiment of the present disclosure.
  • the apparatus has the function of implementing the above example method on the terminal device side, and the function may be implemented by hardware, or may be implemented by executing corresponding software on the hardware.
  • the apparatus may be the terminal device described above, or may be set in the terminal device. As shown in Figure 7, the device may include:
  • a setting module 604 configured to set the target parameter of the radio link failure RLF when the GNSS of the terminal device times out.
  • the device also includes:
  • a declaration module 606, configured to declare the main cell group MCG RLF when the GNSS of the terminal equipment times out
  • the setting module 604 is configured to record target parameters in the RLF variable report.
  • the setting module 604 is configured to set the connection failure type connectionFailureType to RLF;
  • the setting module 604 is configured to set the RLF cause rlf-Cause as GNSS timeout.
  • the device also includes:
  • a state module 607 configured to return to the idle state when the security of the access layer is not activated
  • the state module 607 is configured to return to the idle state when the security of the access layer is activated.
  • the setting module 604 is configured to set the release cause of the radio resource control RRC connection to other;
  • the setting module 604 is configured to set the release reason of the RRC connection as GNSS timeout
  • the setting module 604 is configured to set the release cause of the RRC connection as RRC connection failure.
  • the device also includes:
  • the state module 607 is configured to maintain the connection state.
  • the device also includes:
  • the first receiving module 603 is configured to receive a configuration message sent by a network device;
  • the configuration message is used to configure the terminal device to fall back to an idle state when the GNSS times out;
  • the configuration message is used to configure the terminal device to remain in the connected state when the GNSS times out.
  • the device also includes:
  • the first sending module 605 is configured to send a first message to the network device, wherein
  • the first message is used to indicate that the terminal device supports maintaining a connected state in the case of GNSS timeout;
  • the first message is used to indicate that the terminal device does not support maintaining the connected state when the GNSS times out.
  • the device also includes:
  • the transmission module 601 is configured to prohibit uplink transmission when the GNSS of the terminal device times out.
  • the device also includes:
  • the transmission module 601 is configured to not monitor the physical downlink control channel PDCCH when the GNSS of the terminal device times out;
  • the transmission module 601 is configured to not perform downlink reception when the GNSS of the terminal device times out.
  • the terminal device includes a media access control MAC layer
  • the transmission module 601 is configured to determine time alignment timeout when the GNSS of the terminal device times out.
  • the transmission module 601 is configured to execute a time alignment timeout processing flow.
  • the transmission module 601 is configured to determine that both the primary timing advance group pTAG and the secondary timing advance group sTAG time-aligned timeout;
  • the transmission module 601 is configured to determine the pTAG time alignment timeout.
  • the device also includes:
  • the transmission module 601 is configured to prohibit initiation of random access when the GNSS of the terminal device times out.
  • the terminal device includes a media access control layer MAC layer and a physical layer PHY.
  • the terminal device includes a radio resource control RRC layer
  • the transmission module 601 is configured to release or disable at least one of the physical uplink control channel PUCCH and the short physical uplink control channel SPUCCH of the serving cell when the GNSS of the terminal device times out;
  • the transmission module 601 is configured to release or disable the semi-persistent scheduling SPS of the serving cell when the GNSS of the terminal device times out;
  • the transmission module 601 is configured to release or disable dedicated uplink scheduling request SR resources when the GNSS of the terminal device times out and the terminal device is a NB-IOT device.
  • the transmission module 601 is configured to restore the PUCCH or SPUCCH of the disabled serving cell when the GNSS positioning is obtained;
  • the transmission module 601 is configured to restore the SPS of the disabled serving cell when the GNSS positioning is obtained;
  • the transmission module 601 is configured to recover the disabled dedicated SR resource when the GNSS positioning is obtained and the terminal device is an NB-IOT device.
  • the terminal device includes a media access control MAC layer
  • the transmission module 601 is configured to clear the HARQ buffer of the server cell when the GNSS of the terminal device times out;
  • the transmission module 601 is configured to notify the radio resource control RRC layer to release or disable channel sounding reference signal SRS resources of the serving cell when the GNSS of the terminal device times out;
  • the transmission module 601 is configured to clear or disable configured downlink tasks and uplink authorizations when the GNSS of the terminal device times out;
  • the transmission module 601 is configured to clear or disable the physical uplink shared channel PUSCH resource reported by the semi-persistent channel state information CSI when the GNSS of the terminal device times out;
  • the transmission module 601 is configured to prohibit uplink transmission when the GNSS of the terminal device times out.
  • the transmission module 601 is configured to restore the disabled configured downlink task and uplink authorization when the GNSS positioning is obtained.
  • the transmission module 601 is configured to resume uplink transmission when the GNSS positioning is obtained.
  • the transmission module 601 is configured to resume downlink reception when the GNSS positioning is obtained.
  • the device also includes:
  • the first sending module 605 is configured to send the GNSS validity period to the network device when the GNSS positioning is obtained;
  • the first sending module 605 is configured to report the primary cell group MACRLF to the network device when the GNSS positioning is obtained.
  • the device also includes:
  • An execution module 602 configured to execute a random access procedure when the GNSS positioning is obtained
  • the execution module 602 is configured to execute a connection reestablishment process when the GNSS positioning is obtained.
  • the device also includes:
  • the first receiving module 603 is configured to obtain GNSS positioning within the time window.
  • the device also includes:
  • the transmission module 601 is configured to not perform uplink transmission or downlink reception within the time window.
  • the device also includes:
  • the first receiving module 603 is configured to receive configuration information of the time window sent by the network device.
  • FIG. 8 shows a block diagram of an apparatus for processing GNSS validity provided by an embodiment of the present disclosure.
  • the apparatus has the function of implementing the above example method on the terminal device side, and the function may be implemented by hardware, or may be implemented by executing corresponding software on the hardware.
  • the apparatus may be the terminal device described above, or may be set in the terminal device. As shown in Figure 8, the device may include:
  • the second sending module 701 is configured to send the GNSS validity period to the network device.
  • the second sending module 701 is configured to send a random access message to the network device, where the random access message includes the validity period of the GNSS.
  • the second sending module 701 is configured to send a dedicated radio resource control RRC message to the network device, where the dedicated RRC message includes the GNSS validity period.
  • the device also includes:
  • the second receiving module 702 is configured to receive a terminal device information request sent by the network device, and the terminal device information request is used to request the terminal device to report the validity period of the GNSS;
  • the second sending module 701 is configured to send a terminal device information response to the network device, where the terminal device information response includes the GNSS validity period.
  • the second sending module 701 is configured to send the GNSS validity period to the network device when the GNSS validity period is shorter than the first validity period;
  • the first validity period is the validity period of ephemeris information or public time synchronization.
  • the second sending module 701 is configured to send a second validity period to the network device, where the second validity period is the smaller value of the GNSS validity period and the first validity period;
  • the first validity period is the validity period of ephemeris information or public time synchronization.
  • the second sending module 701 is configured to send the GNSS validity period to the network device when the GNSS positioning is obtained.
  • the device also includes:
  • the second receiving module 702 is configured to receive the first indication sent by the network device through a system message
  • the second receiving module 702 is configured to receive the first indication sent by the network device through a radio resource control RRC dedicated message;
  • the first indication is used to instruct the terminal device to report the GNSS validity period, or, the first indication is used to instruct the terminal device not to report the GNSS validity period.
  • the device provided by the above embodiment realizes its functions, it only uses the division of the above-mentioned functional modules as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional modules according to actual needs. That is, the content structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • FIG. 9 shows a schematic structural diagram of a communication device (terminal device or network device) provided by an embodiment of the present disclosure.
  • the communication device may include: a processor 901 , a receiver 902 , a transmitter 903 , a memory 904 and a bus 905 .
  • the processor 901 includes one or more processing cores.
  • the processor 901 executes various functional applications and processes GNSS validity by running software programs and modules.
  • the receiver 902 and the transmitter 903 can be realized as a transceiver 906, and the transceiver 906 can be a communication chip.
  • the memory 904 is connected to the processor 901 through a bus 905 .
  • the memory 904 may be used to store a computer program, and the processor 901 is used to execute the computer program, so as to implement various steps performed by the communication device in the foregoing method embodiments.
  • the memory 904 can be implemented by any type of volatile or non-volatile storage device or their combination, and the volatile or non-volatile storage device includes but not limited to: random-access memory (Random-Access Memory, RAM) And read-only memory (Read-Only Memory, ROM), erasable programmable read-only memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), flash memory or other solid-state storage technologies, compact disc read-only memory (CD-ROM), high-density digital video disc (Digital Video Disc, DVD) or other optical storage, tape cartridges, tapes, disks storage or other magnetic storage devices.
  • RAM Random-Access Memory
  • ROM read-only memory
  • EPROM erasable programmable read-only memory
  • EPROM erasable programmable Read-Only Memory
  • EEPROM Electrically erasable programmable read-only memory
  • the processor 901 involved in the embodiment of the present disclosure may execute the steps performed by the terminal device in any of the methods shown in FIGS. 3 to 6 above, which are not repeated here. repeat.
  • the communication device when the communication device is implemented as a terminal device,
  • the processor is configured to set the target parameter of the radio link failure RLF when the global navigation satellite system (GNSS) of the terminal device times out.
  • GNSS global navigation satellite system
  • the communication device when the communication device is implemented as a terminal device,
  • the transceiver is used to send the validity period of the Global Navigation Satellite System (GNSS) to the network equipment.
  • GNSS Global Navigation Satellite System
  • An embodiment of the present disclosure also provides a computer-readable storage medium, where a computer program is stored in the storage medium, and the computer program is used to be executed by a processor of a core network device, so as to realize the above-mentioned GNSS validity on the terminal device side processing method.
  • the computer-readable storage medium may include: a read-only memory (Read-Only Memory, ROM), a random-access memory (Random-Access Memory, RAM), a solid-state hard drive (Solid State Drives, SSD) or an optical disc.
  • the random access memory may include resistive random access memory (Resistance Random Access Memory, ReRAM) and dynamic random access memory (Dynamic Random Access Memory, DRAM).
  • An embodiment of the present disclosure also provides a chip, the chip includes a programmable logic circuit and/or program instructions, and when the chip is run on a terminal device, it is used to implement the above-mentioned processing method for GNSS validity on the terminal device side .
  • An embodiment of the present disclosure also provides a computer program product or computer program, the computer program product or computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium, and the processor of the terminal device reads from the computer The readable storage medium reads and executes the computer instructions, so as to realize the above-mentioned method for processing GNSS validity at the terminal device side.
  • the "indication" mentioned in the embodiments of the present disclosure may be a direct indication, may also be an indirect indication, and may also mean that there is an association relationship.
  • a indicates B which can mean that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.
  • the term "corresponding" may mean that there is a direct correspondence or indirect correspondence between the two, or that there is an association between the two, or that it indicates and is indicated, configuration and being configuration etc.
  • the "plurality” mentioned herein means two or more.
  • “And/or” describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B may indicate: A exists alone, A and B exist simultaneously, and B exists independently.
  • the character “/” generally indicates that the contextual objects are an "or” relationship.
  • the numbering of the steps described herein only exemplarily shows a possible sequence of execution among the steps.
  • the above-mentioned steps may not be executed according to the order of the numbers, such as two different numbers
  • the steps are executed at the same time, or two steps with different numbers are executed in the reverse order as shown in the illustration, which is not limited in this embodiment of the present disclosure.
  • the functions described in the embodiments of the present disclosure may be implemented by hardware, software, firmware or any combination thereof.
  • the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Radio Relay Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开公开了一种GNSS有效性的处理方法、装置、设备及存储介质，涉及通信技术领域。所述方法由终端设备执行，所述方法包括：在所述终端设备的全球导航卫星系统GNSS超时的情况下，设置无线链路失败RLF的目标参数。该方法可以针对GNSS的有效性提供解决方案。

Description

GNSS有效性的处理方法、装置、设备及存储介质 技术领域
本公开实施例涉及通信技术领域，特别涉及一种GNSS有效性的处理方法、装置、设备及存储介质。
背景技术
终端设备获取的GNSS position fix(定位)具有有效期，GNSS position fix的有效性只能维持一段时间，超过有效期后，终端设备的GNSS outdated(超时)。终端设备需要重新获取GNSS。
而部分IoT(Internet of Things，物联网)终端设备无法支持同时进行GNSS(Global Navigation Satellite System，全球导航卫星系统)接收和LTE(Long Term Evolution，长期演进)收发。
在上述场景中针对GNSS的有效性问题如何进行处理是亟待解决的问题。
发明内容
本公开实施例提供了一种GNSS有效性的处理方法、装置、设备及存储介质，可以针对GNSS的有效性提供解决方案。所述技术方案如下：
根据本公开实施例的一个方面，提供了一种GNSS有效性的处理方法，所述方法由终端设备执行，所述方法包括：
在所述终端设备的全球导航卫星系统GNSS超时的情况下，设置无线链路失败RLF的目标参数。
根据本公开实施例的一个方面，提供了一种GNSS有效性的处理方法，所述方法由终端设备执行，所述方法包括：
向网络设备发送全球导航卫星系统GNSS有效期。
根据本公开实施例的一个方面，提供了一种GNSS有效性的处理装置，所述装置用于实现终端设备，所述装置包括：
设置模块，用于在所述终端设备的全球导航卫星系统GNSS超时的情况下，设置无线链路失败RLF的目标参数。
根据本公开实施例的一个方面，提供了一种GNSS有效性的处理装置，所述装置用于实现终端设备，所述装置包括：
第二发送模块，用于向网络设备发送全球导航卫星系统GNSS有效期。
根据本公开实施例的一个方面，提供了一种终端设备，所述终端设备包括处理器；
所述处理器，用于在所述终端设备的全球导航卫星系统GNSS超时的情况下，设置无线链路失败RLF的目标参数。
根据本公开实施例的一个方面，提供了一种终端设备，所述终端设备包括收发器；
所述收发器，用于向网络设备发送全球导航卫星系统GNSS有效期。
根据本公开实施例的一个方面，提供了一种计算机可读存储介质，所述存储介质中存储有计算机程序，所述计算机程序用于处理器执行，以实现上述GNSS有效性的处理方法。
根据本公开实施例的一个方面，提供了一种芯片，所述芯片包括可编程逻辑电路和/或程序指令，当所述芯片运行时，用于实现上述GNSS有效性的处理方法。
根据本公开实施例的一个方面，提供了一种计算机程序产品或计算机程序，所述计算机程序产品或计算机程序包括计算机指令，所述计算机指令存储在计算机可读存储介质中，处 理器从所述计算机可读存储介质读取并执行所述计算机指令，以实现上述GNSS有效性的处理方法。
本公开实施例提供的技术方案可以带来如下有益效果：
分别针对GNSS超时，以及，GNSS有效期上报，提供了解决方案。在GNSS超时后，采用RLF(Radio Link Failure，无线链路失败)记录相关信息；在获取到GNSS有效期后，向网络设备上报GNSS有效期，完善GNSS有效性相关的处理机制。
附图说明
为了更清楚地说明本公开实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本公开一个示例性实施例提供的通信系统的示意图；
图2是本公开一个示例性实施例提供的通信系统的示意图；
图3是本公开一个示例性实施例提供的GNSS有效性的处理方法的流程图；
图4是本公开一个示例性实施例提供的GNSS有效性的处理方法的流程图；
图5是本公开一个示例性实施例提供的GNSS有效性的处理方法的流程图；
图6是本公开一个示例性实施例提供的GNSS有效性的处理方法的流程图；
图7是本公开一个示例性实施例提供的GNSS有效性的处理装置的框图；
图8是本公开一个示例性实施例提供的GNSS有效性的处理装置的框图；
图9是本公开一个示例性实施例提供的通信设备的结构示意图。
具体实施方式
为使本公开的目的、技术方案和优点更加清楚，下面将结合附图对本公开实施方式作进一步地详细描述。
本公开实施例描述的网络架构以及业务场景是为了更加清楚地说明本公开实施例的技术方案，并不构成对本公开实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本公开实施例提供的技术方案对于类似的技术问题，同样适用。
在介绍本公开技术方案之前，先对本公开涉及的一些技术知识进行介绍说明。
非地面网络(Non-Terrestrial Network，NTN)技术
目前，相关标准组织正在研究NTN技术，NTN技术一般采用卫星通信的方式向地面用户提供通信服务。相比于地面的蜂窝通信网络，卫星通信具有很多独特的优点。首先，卫星通信不受用户地域的限制，例如一般的陆地通信不能覆盖海洋、高山、沙漠等无法搭设通信设备或由于人口稀少而不做通信覆盖的区域，而对于卫星通信来说，由于一颗卫星即可以覆盖较大的地面，加之卫星可以围绕地球做轨道运动，因此理论上地球上每一个角落都可以被卫星通信覆盖。其次，卫星通信有较大的社会价值。卫星通信在边远山区、贫穷落后的国家或地区都可以以较低的成本覆盖到，从而使这些地区的人们享受到先进的语音通信和移动互联网技术，有利于缩小与发达地区的数字鸿沟，促进这些地区的发展。再次，卫星通信距离远，且通信距离增大通讯的成本没有明显增加；最后，卫星通信的稳定性高，不受自然灾害的限制。
通信卫星按照轨道高度的不同分为低地球轨道(Low-Earth Orbit，LEO)卫星、中地球轨道(Medium-Earth Orbit，MEO)卫星、地球同步轨道(Geostationary Earth Orbit，GEO)卫星、高椭圆轨道(High Elliptical Orbit，HEO)卫星等等。目前阶段主要研究的是LEO和GEO。
1、LEO
低轨道卫星高度范围为500km～1500km，相应轨道周期约为1.5小时～2小时。用户间单跳通信的信号传播延迟一般小于20ms。最大卫星可视时间20分钟。信号传播距离短，链路损耗少，对用户终端设备的发射功率要求不高。
2、GEO
地球同步轨道卫星，轨道高度为35786km，围绕地球旋转周期为24小时。用户间单跳通信的信号传播延迟一般为250ms。
为了保证卫星的覆盖以及提升整个卫星通信系统的系统容量，卫星采用多波束覆盖地面，一颗卫星可以形成几十甚至数百个波束来覆盖地面；一个卫星波束可以覆盖直径几十至上百公里的地面区域。
表1中给出了典型的NTN网络的卫星高度、轨道、卫星覆盖范围：
表1
Figure PCTCN2021144061-appb-000001
终端设备到接入网设备的RTT(Round Trip Time，往返时间)包含两部分，一部分是终端设备到卫星链路的RTT，该部分为UE specific TA(终端设备特有时间同步)部分，另一部分是卫星到接入网设备链路的RTT，该部分为common(公共)TA(Time Alignment，时间同步)部分。common TA部分可以一部分由接入网设备来补偿，另一部分由终端设备来补偿。由终端设备补偿的部分会通过系统消息发送给终端设备。
网络设备除了广播需要终端设备补偿的common TA外，还会广播卫星的星历信息，来帮助终端设备获取卫星的位置以便计算终端设备到卫星的RTT。由于卫星的移动性，common TA和星历信息都会发生变化，所以系统消息中广播的星历信息和common TA具有有效期，称作UL synchronization validity duration(上行链路同步有效期)。星历信息和common TA共用一个UL synchronization validity duration。UL synchronization validity duration的值由网络设备通过SIB广播给终端设备。
终端设备会根据广播消息中星历信息和common TA对应的epoch time(起始生效时刻)来启动UL synchronization validity timer。
其中，epoch time有三种指示方式：
1、系统消息明示指示：系统消息中明确广播一个SFN(System Frame Number，系统帧号)和subframe number(子帧编号)来指示epoch time。
2、系统消息暗含指示：将包含星历信息和common TA信息的SI(System Information，系统信息)的SI window(窗口)的结束位置作为epoch time。
3、专用信令指示：网络设备通过专用信令向终端设备提供SFN和subframe number来指示epoch time。
IOT终端设备包括：BL UE(Bandwidth reduction and low complexity UE，带宽减少和低复杂性终端设备)、UE in CE mode(UE in Coverage Enhancement mode，覆盖增强模式的终端设备)、NB-IOT UE(Narrow Band Internet of Things UE，窄带物联网终端设备)中的至少一种。
本公开实施例可以应用于NTN系统中，如图1和图2所示。
请参考图1，其示出了一种NTN系统的示意图，该NTN系统中的通信卫星是透明转发(transparent payload)的卫星。如图1所示，该NTN系统包括：终端设备10、卫星20、NTN网关30、接入网设备40和核心网设备50。
终端设备10和接入网设备40之间可通过空口(如Uu接口)进行通信。在图1所示架构中，接入网设备40可以部署在地面，终端设备10和接入网设备40之间的上下行通信，可以通过卫星20和NTN网关30(通常位于地面)进行中转传输。以上行传输为例，终端设备10将上行信号发送给卫星20，卫星20将上述上行信号转发给NTN网关30，再由NTN网关30将上述上行信号转发给接入网设备40，后续由接入网设备40将上述上行信号发送给核心网设备50。以下行传输为例，来自核心网设备50的下行信号发送给接入网设备40，接入网设备40将下行信号发送给NTN网关30，NTN网关30将上述下行信号转发给卫星20，再由卫星20将上述下行信号转发给终端设备10。
在该NTN系统中卫星20具有频率转换与信号放大的作用，卫星20不对接入网设备40的信号进行解调，卫星20类似于repeater(中继站)。
请参考图2，其示出了另一种NTN系统的示意图，该NTN系统中的通信卫星是再生转发(regenerative payload)的卫星。如图2所示，该NTN系统包括：终端设备10、卫星20、NTN网关30和核心网设备50。
在图2所示架构中，接入网设备40的功能集成在卫星20上，也即卫星20具备接入网设备40的功能。终端设备10和卫星20之间可通过空口(如Uu接口)进行通信。卫星20和NTN网关30(通常位于地面)之间可通过卫星无线接口(Satellite Radio Interface，SRI)进行通信。在该NTN系统中，卫星接收信号并进行解调译码后再重新编码调制，并通过卫星频段发送再生的信号。
在图2所示架构中，以上行传输为例，终端设备10将上行信号发送给卫星20，卫星20将上述上行信号转发给NTN网关30，再由NTN网关30将上述上行信号发送给核心网设备50。以下行传输为例，来自核心网设备50的下行信号发送给NTN网关30，NTN网关30将上述下行信号转发给卫星20，再由卫星20将上述下行信号转发给终端设备10。
在上述图1和图2所示的网络架构中，接入网设备40是用于为终端设备10提供无线通信服务的设备。接入网设备40与终端设备10之间可以建立连接，从而通过该连接进行通信，包括信令和数据的交互。接入网设备40的数量可以有多个，两个邻近的接入网设备40之间也可以通过有线或者无线的方式进行通信。终端设备10可以在不同的接入网设备40之间进行切换，也即与不同的接入网设备40建立连接。
以蜂窝通信网络为例，蜂窝通信网络中的接入网设备40可以是基站。基站是一种部署在接入网中用以为终端设备10提供无线通信功能的装置。基站可以包括各种形式的宏基站，微基站，中继站，接入点等等。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同，例如在5G NR系统中，称为gNodeB或者gNB。随着通信技术的演进，“基站”这一名称可能会变化。为方便描述，本公开实施例中，上述为终端设备10提供无线通信功能的装置统称为基站或接入网设备。
另外，本公开实施例中涉及的终端设备10，可以包括各种具有无线通信功能的手持设备、 车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的用户设备(User Equipment，UE)，移动台(Mobile Station，MS)，终端设备(terminal device)等等。为方便描述，本公开实施例中，上面提到的设备统称为终端设备。在本公开实施例中，有些地方使用“UE”代表“终端设备”。在本公开实施例中，“网络设备”可以是接入网设备(如基站)或者卫星。
另外，以5G NTN系统为例，NTN系统中可以包括多颗卫星20。一颗卫星20可以覆盖一定范围的地面区域，为该地面区域上的终端设备10提供无线通信服务。另外，卫星20可以围绕地球做轨道运动，通过布设多个卫星20，可以实现对地球表面的不同区域的通信覆盖。
另外，在本公开实施例中，名词“网络”和“系统”通常混用，但本领域技术人员可以理解其含义。本公开实施例描述的技术方案可以适用于长期演进(Long Term Evolution，LTE)系统，也可以适用于5G系统，也可以适用于5G NR系统后续的演进系统或者其他通信系统，本公开对此不作限定。
示例性的，本公开实施例提供了一种在GNSS超时后，终端设备的处理方式。
请参考图3，其示出了本公开一个实施例提供的GNSS有效性的处理方法的流程图。本实施例以该方法应用于图1或图2所示的通信系统中的终端设备来举例说明。该方法可以包括如下步骤：
步骤201：在终端设备的GNSS超时的情况下，设置RLF(Radio Link Failure，无线链路失败)的目标参数。
示例性的，在步骤201之前，终端设备可以获取GNSS定位，GNSS定位具有有效期，在GNSS定位有效期结束的情况下，确定GNSS outdated(GNSS超时)。即，GNSS超时是指GNSS定位超出GNSS有效期。
应理解，GNSS定位的有效期，可以是GNSS系统预先配置的，也可以协议约定的，本公开对此不作限制。示例性的，终端设备从终端设备的GPS(Global Positioning System，全球定位系统)模块获取GNSS有效期。
在GNSS超时后，终端设备确定RLF，执行RLF的处理流程，根据GNSS超时记录RLF的相关参数(目标参数)。
示例性的，在所述终端设备的GNSS超时的情况下，终端设备可以执行以下中的至少一项：声明MCG(Master Cell Group，主小区组)RLF、在RLF变量报告(VarRLF-Report)中记录目标参数。
RLF变量报告中的目标参数包括连接故障类型(connectionFailureType)、RLF原因(rlf-Cause)中的至少一个。示例性的，终端设备将连接故障类型设置为RLF，和/或，将RLF原因设置为GNSS超时。
示例性的，在终端设备的GNSS超时后，终端设备需要重新获取GNSS定位。此时，由于部分终端设备不支持同时进行GNSS接收和LTE收发，本公开实施例提供了一种方法，在GNSS超时后，终端设备声明RLF，并停止上行传输和下行接收，直至获取到新的GNSS定位为止。
综上所述，本实施例提供的技术方案，针对GNSS超时，提供了解决方案。在GNSS超时后，采用RLF(Radio Link Failure，无线链路失败)记录相关信息，完善GNSS有效性相关的处理机制。
示例性的，在GNSS超时后，终端设备可以退回至空闲态。
请参考图4，其示出了本公开一个实施例提供的GNSS有效性的处理方法的流程图。本实施例以该方法应用于图1或图2所示的通信系统中的终端设备来举例说明。该方法可以包括如下步骤：
步骤301：在终端设备的GNSS超时的情况下，声明MCG RLF。
可选地，当终端设备的GNSS outdated后，终端设备声明(declare)MCG RLF，触发MCG RLF处理流程。
步骤302：在RLF变量报告中记录目标参数。
可选地，终端设备记录RLF相关信息在VarRLF-Report(RLF变量报告)中，例如，在RLF变量报告中设置connectionFailureType(连接故障类型)为RLF；在RLF变量报告中设置rlf-Cause(RLF原因)为GNSS outdated。
步骤303：退回至空闲态。
若AS(Access Stratum，接入层)security(安全)激活或未激活，终端设备执行离开连接态的流程，从连接态退回至空闲态。
即，在终端设备的接入层安全未激活的情况下，终端设备退回至空闲态；或，在接入层安全激活的情况下，终端设备退回至空闲态。
步骤304：设置RRC(Radio Resource Control，无线资源控制)连接的释放原因。
终端设备将release cause(释放原因)设置为other(其他)，或者GNSS outdated，或者RRC connection failure(RRC连接失败)。即，将无线资源控制RRC连接的释放原因设置为其他；或，将RRC连接的释放原因设置为GNSS超时；或，将RRC连接的释放原因设置为RRC连接失败。
示例性的，步骤301、步骤302与步骤303、步骤304的先后顺序可以是任意的。即，终端设备可以在GNSS超时后，先声明RLF，再退回至空闲态；终端设备也可以在GNSS超时后，先退回至空闲态，再声明RLF。本公开实施例对此不加以限制。
示例性的，在GNSS超时后，终端设备声明RLF、设置RLF的目标参数；退回空闲态。或，在GNSS超时后，终端设备退回空闲态；声明RLF、设置RLF的目标参数。
应理解，上述步骤可以在GNSS超时后单独实施，也可以与其他步骤组合实施，并且步骤执行的顺序可以根据需要进行调整。
综上所述，本实施例提供的技术方案，在GNSS超时后，声明RLF(Radio Link Failure，无线链路失败)并记录相关信息，控制终端设备从连接态退回至空闲态，并根据GNSS超时来设置RRC连接的释放原因，完善了GNSS有效性相关的处理机制。
示例性的，在GNSS超时后，终端设备可以保持连接态。
请参考图5，其示出了本公开一个实施例提供的GNSS有效性的处理方法的流程图。本实施例以该方法应用于图1或图2所示的通信系统中的终端设备来举例说明。该方法可以包括如下步骤：
步骤401：向网络设备发送第一消息，第一消息用于指示是否支持在GNSS超时后保持连接态。
示例性的，所述第一消息用于指示所述终端设备支持在GNSS超时的情况下保持连接态，或，所述第一消息用于指示所述终端设备不支持在GNSS超时的情况下保持连接态。
可选地，终端设备上报是否具有在GNSS outdated后保持在连接态的能力。
示例性的，网络设备为接入网设备。
步骤402：接收网络设备发送的配置消息，配置消息用于指示在GNSS超时后是否保持连接态。
示例性的，所述配置消息用于配置所述终端设备在GNSS超时的情况下退回至空闲态，或，所述配置消息用于配置所述终端设备在GNSS超时的情况下保持在连接态。
可选地，网络设备可以配置终端设备在GNSS outdated后回到idle态，或，保持在连接态。
示例性的，在终端设备支持在GNSS超时后保持连接态的情况下，网络设备配置终端设备在GNSS超时的情况下保持在连接态，或，网络设备配置终端设备在GNSS超时的情况下 退回至空闲态。在终端设备不支持在GNSS超时后保持连接态的情况下，网络设备配置终端设备在GNSS超时的情况下退回至空闲态。
在网络设备配置终端设备在GNSS超时后保持在连接态的情况下，执行步骤403至步骤405。在网络设备配置终端设备在GNSS超时后退回至空闲态的情况下，执行步骤301至步骤304。
步骤403：在终端设备的GNSS超时的情况下，保持连接态。
在网络设备配置终端设备在GNSS超时后保持连接态，且GNSS超时的情况下，终端设备保持在连接态。
步骤404：在终端设备的GNSS超时的情况下，声明MCG RLF。
可选地，当终端设备的GNSS outdated后，终端设备声明(declare)MCG RLF，触发MCG RLF处理流程。
步骤405：在RLF变量报告中记录目标参数。
可选地，终端设备记录RLF相关信息在VarRLF-Report(RLF变量报告)中，例如，在RLF变量报告中设置connectionFailureType(连接故障类型)为RLF；在RLF变量报告中设置rlf-Cause(RLF原因)为GNSS outdated。
示例性的，声明RLF以及保持连接态的先后顺序可以是任意的。即，终端设备可以在GNSS超时后，先声明RLF，再保持连接态；终端设备也可以在GNSS超时后，先保持连接态，再声明RLF。本公开实施例对此不加以限制。
示例性的，在GNSS超时后，终端设备声明RLF、设置RLF的目标参数；保持连接态。或，在GNSS超时后，终端设备保持连接态；声明RLF、设置RLF的目标参数。
应理解，上述步骤可以在GNSS超时后单独实施，也可以与其他步骤组合实施，并且步骤执行的顺序可以根据需要进行调整。
综上所述，本实施例提供的技术方案，终端设备可以向网络设备上报是否支持在GNSS超时后维持在连接态，若终端设备支持维持在连接态，且网络设备指示终端设备维持在连接态，则在GNSS超时后，终端设备可以维持在连接态，声明RLF(Radio Link Failure，无线链路失败)并记录相关信息，完善了GNSS有效性相关的处理机制。
示例性的，终端设备在GNSS超时后，声明RLF并进行状态的切换或保持。然后，在GNSS超时、且终端设备未获取到最新的GNSS定位的情况下，终端设备禁止进行上行传输。即，在终端设备GNSS超时的情况下，终端设备禁止上行传输。
可选的，终端设备也不进行下行接收，即，终端设备不再监听PDCCH(Physical Downlink Control Channel，物理下行控制信道)，不再进行下行接收。即，在终端设备GNSS超时的情况下，终端设备不监听PDCCH；或，在终端设备的GNSS超时的情况下，不进行下行接收。
则，本公开实施例提供了以下两种处理方式：
方式1：终端设备可以按照上行失步进行后续处理。
方式2：网络设备可以为终端设备配置时间窗口，在时间窗口内终端设备获取新的GNSS定位，时间窗口内不进行上行传输和下行接收。
针对上述的方式1，终端设备在获取最新的GNSS position fix前禁止上行传输。可选地，终端设备不再监听PDCCH，不再进行下行接收。
对于不再进行上行传输，本公开实施例提供了以下三种处理方式：
方式1)终端设备的MAC(Medium Access Control，媒体接入控制)层认为timeAlignmentTimer(时间对齐)超时。MAC层行为按照timeAlignmentTimer超时后的流程处理。此种方式下，终端设备在获取到最新的GNSS position fix前不会发起随机接入。
即，终端设备包括MAC层。在终端设备的GNSS超时的情况下，MAC层确定时间对齐超时；执行时间对齐超时处理流程。在终端设备的GNSS超时的情况下，终端设备禁止发起 随机接入。
其中，timeAlignmentTimer超时，包括认为所有的timeAlignmentTimer(包括pTAG(Primary Timing Advance Group，主定时提前组)和sTAG(Secondary Timing Advance Group，辅定时提前组)各自的timeAlignmentTimer)均超时，或认为pTAG的timeAlignmentTimer超时。
即，MAC层确定pTAG和sTAG均时间对齐超时；或，确定pTAG时间对齐超时。
方式2)终端设备包括MAC层和PHY(Physical layer，物理层)。终端设备的MAC层/PHY暂时禁止任何上行传输。
即，在终端设备的GNSS超时的情况下，MAC层或PHY禁止上行传输。
方式3)终端设备包括RRC层和MAC层。RRC层和MAC层的行为各自定义如下：
RRC层：
在GNSS outdated后，RRC层可选地执行以下行为1)至行为3)中的至少一个：
行为1)RRC层释放或禁用所有serving cell(服务小区)的PUCCH(Physical Uplink Control Channel，物理上行控制信道)/SPUCCH(Short PUCCH，短PUCCH)。
即，在终端设备的GNSS超时的情况下，RRC层释放或禁用服务小区的PUCCH、SPUCCH中的至少一个。
行为2)RRC层释放或禁用所有serving cell的SPS(Semi-Persistent Scheduling，半持续调度)。
即，在终端设备的GNSS超时的情况下，RRC层释放或禁用服务小区的SPS。
行为3)对于NB-IOT终端设备，RRC层释放或禁用所有专用SR(Scheduling Request，上行调度请求)资源。
即，在终端设备的GNSS超时，且终端设备为NB-IOT设备的情况下，RRC层释放或禁用专用SR资源。
在获取到最新的GNSS position fix后，RRC层可选地执行以下行为4)至行为6)中的至少一个：
行为4)RRC层恢复所有禁用的serving cell的PUCCH/SPUCCH。
示例性的，若在GNSS超时的情况下，RRC层释放或禁用服务小区的PUCCH、SPUCCH中的至少一个。则在获取到GNSS定位的情况下，RRC层恢复禁用的服务小区的PUCCH或SPUCCH。
行为5)RRC层恢复所有禁用的serving cell的SPS。
示例性的，若在终端设备的GNSS超时的情况下，RRC层释放或禁用服务小区的SPS。则在获取到GNSS定位的情况下，RRC层恢复禁用的服务小区的SPS。
行为6)对NB-IOT终端设备，RRC层恢复所有禁用的专用SR资源。
示例性的，若在终端设备的GNSS超时，且终端设备为NB-IOT设备的情况下，RRC层释放或禁用专用SR资源。则，在获取到GNSS定位，且终端设备为NB-IOT设备的情况下，RRC层恢复禁用的专用SR资源。
MAC层：
在GNSS outdated后，MAC层可选地执行以下行为7)至行为12)中的至少一个：
行为7)MAC层清空所有serving cell的HARQ(Hybrid Automatic Repeat reQuest，混合自动重传)buffer(缓冲器)。
即，在终端设备的GNSS超时的情况下，MAC层清空服务器小区的HARQ缓冲器。
行为8)MAC层通知RRC层释放/禁用所有serving cell的PUCCH资源。
即，在终端设备的GNSS超时的情况下，MAC层通知RRC层释放或禁用服务小区的PUCCH资源。
行为9)MAC层通知RRC层释放/禁用所有serving cell的SRS(Sounding Reference Signal，信道探测参考信号)资源。
即，在终端设备的GNSS超时的情况下，MAC层通知RRC层释放或禁用服务小区的SRS资源。
行为10)MAC层清空或禁用所有的configured downlink assignments and uplink grants(配置的下行链路任务和上行链路授权)。
即，在终端设备的GNSS超时的情况下，MAC层清空或禁用配置的下行链路任务和上行链路授权。
行为11)MAC层清空/禁用半持续CSI(Channel State Information，信道状态信息)报告的PUSCH(Physical Uplink Shared Channel，物理上行共享信道)资源。
即，在终端设备的GNSS超时的情况下，MAC层清空或禁用CSI报告的PUSCH资源。
行为12)UE MAC层暂时禁止任何上行传输。
即，在终端设备的GNSS超时的情况下，MAC层禁止上行传输。
在获取到最新的GNSS position fix后，MAC层恢复禁用的configured downlink assignments and uplink grants。
示例性的，若在终端设备的GNSS超时的情况下，MAC层清空或禁用配置的下行链路任务和上行链路授权。则，在获取到GNSS定位的情况下，MAC层恢复禁用的配置的下行链路任务和上行链路授权。
示例性的，终端设备在获取最新的GNSS position fix后，恢复上行传输和下行接收。可选地，终端设备在获取最新的GNSS position fix后，触发上报GNSS validity duration，或者触发随机接入，或者触发连接重建。在连接建立后，终端设备可选地进行MCG RLF上报。
可选的，终端设备在在获取到GNSS定位的情况下，恢复上行传输。
可选的，若终端设备在GNSS超时的情况下，停止下行接收，则终端设备在获取到GNSS定位的情况下，恢复下行接收。
可选的，若终端设备在GNSS超时的情况下，退回至空闲态，则终端设备在获取到GNSS定位的情况下，执行随机接入流程。
可选的，若终端设备在GNSS超时的情况下，退回至空闲态，则终端设备在获取到GNSS定位的情况下，执行连接重建流程。
可选的，终端设备在获取到GNSS定位的情况下，向网络设备发送GNSS有效期。
可选的，终端设备在获取到GNSS定位的情况下，向网络设备报告MAC RLF。示例性的，终端设备向网络设备发送RLF变量报告。
针对上述的方式2，终端设备接收网络设备发送的时间窗口的配置信息，并且响应于该配置信息，在时间窗口内不进行LTE/NR(New Radio，新空口)的上行传输，或下行接收。终端设备在时间窗口获取GNSS定位。
对于方式2，网络设备可以下发例如measurement gap(测量间隙)的时间窗口，终端设备在该measurement gap期间不进行NR/LTE的上行发送，或下行接收，终端设备可以在该measurement gap期间获取GNSS定位。
示例性的，网络设备根据GNSS有效期预先为终端设备配置好时间窗口。示例性的，时间窗口的起始时间早于GNSS有效期的超时时刻。终端设备在时间窗口内不进行上行传输或下行接收，在时间窗口内进行GNSS定位的获取，时间窗口结束前，终端设备获取到最新的GNSS定位。则在时间窗口外，终端设备的GNSS定位始终处于有效期内。
示例性的，本公开实施例提供了一种终端设备向网络设备上报GNSS有效期的方法。
请参考图6，其示出了本公开一个实施例提供的GNSS有效性的处理方法的流程图。本实施例以该方法应用于图1或图2所示的通信系统中的终端设备来举例说明。该方法可以包括如下步骤：
步骤501：向网络设备发送GNSS有效期。
示例性的，终端设备获取GNSS定位，和GNSS定位的GNSS有效期。GNSS有效期是终端设备根据GNSS系统预配置的方式获取的。示例性的，终端设备从终端设备的GPS模块获取GNSS有效期。
示例性的，本公开实施例分别提供了终端设备上报GNSS有效期的多种触发条件、上报内容和上报方式。多种触发条件、上报内容和上报方式之间可以任意组合。
示例性的，对于终端设备上报GNSS有效期的触发条件，本公开实施例提供了如下两种条件：
1)终端设备在获取最新的GNSS position fix后，触发GNSS validity duration上报。
示例性的，终端设备在获取到GNSS定位的情况下，向网络设备发送GNSS有效期。
2)网络设备通过系统消息和/或RRC专用消息指示终端设备是否上报GNSS validity duration。终端设备在接收到网络设备的指示后，上报GNSS有效期。
示例性的，终端设备接收网络设备通过系统消息发送的第一指示；和/或，终端设备接收网络设备通过无线资源控制RRC专用消息发送的第一指示；其中，第一指示用于指示终端设备上报GNSS有效期，或，第一指示用于指示终端设备不上报GNSS有效期。终端设备响应于第一指示中指示终端设备上报GNSS有效期，向网络设备发送GNSS有效期。
示例性的，对于终端设备上报GNSS有效期的上报方式，本公开实施例提供了如下两种方式：
1)终端设备在随机接入的msg5中上报。
示例性的，终端设备向网络设备发送随机接入消息(msg5)，随机接入消息中包括GNSS有效期。
具体地，GNSS validity duration可以携带在连接建立完成/连接恢复完成/连接重建完成消息中。
即，终端设备向网络设备发送连接建立完成消息/连接恢复完成消息/连接重建完成消息，连接建立完成消息/连接恢复完成消息/连接重建完成消息中包括GNSS有效期。
2)终端设备进入连接态后通过专用RRC消息上报。
具体地，终端设备可以通过终端设备辅助信息消息来上报GNSS有效期。或者，在网络设备在终端设备信息请求中请求终端设备上报GNSS validity duration后，终端设备通过终端设备信息响应消息上报GNSS有效期。
示例性的，终端设备向网络设备发送专用RRC消息，专用RRC消息中包括GNSS有效期。
例如，终端设备接收网络设备发送的终端设备信息请求，终端设备信息请求用于请求终端设备上报GNSS有效期；终端设备响应于终端设备信息请求，向网络设备发送终端设备信息响应，终端设备信息响应中包括GNSS有效期。
示例性的，对于终端设备上报GNSS有效期的上报内容，本公开实施例提供了如下两种内容：
1)若GNSS validity duration小于星历信息/common TA的validity duration(有效期)，则上报GNSS validity duration。其中，星历信息/common TA的validity duration指星历信息/common TA剩余的validity(有效)时长。
示例性的，终端设备在GNSS有效期小于第一有效期的情况下，向网络设备发送GNSS有效期；其中，第一有效期为星历信息或公共时间同步的有效期。示例性的，第一有效期为星历信息或公共时间同步的有效期的剩余有效时长。
2)终端设备上报GNSS validity duration和星历/common TA的validity duration中的最小者。
示例性的，终端设备向网络设备发送第二有效期，第二有效期为GNSS有效期和第一有效期中的较小值；其中，所述第一有效期为星历信息或公共时间同步的有效期。示例性的， 第一有效期为星历信息或公共时间同步的有效期的剩余有效时长。
综上所述，本实施例提供的技术方案，针对GNSS有效期上报，提供了解决方案。给出了终端设备上报GNSS有效期的多种触发条件、上报方式、上报内容，完善了GNSS有效性相关的处理机制。
应理解，响应于终端设备如上所述地向网络设备上报GNSS有效期，在有效期超时之后，终端设备的行为以及后续的处理方式已经在前述实施例中进行了详细描述，在此不再赘述。
下述为本公开装置实施例，可以用于执行本公开方法实施例。对于本公开装置实施例中未披露的细节，请参照本公开方法实施例。
请参考图7，其示出了本公开一个实施例提供的GNSS有效性的处理装置的框图。该装置具有实现上述终端设备侧的方法示例的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该装置可以是上文介绍的终端设备，也可以设置在终端设备中。如图7所示，该装置可以包括：
设置模块604，用于在所述终端设备的全球导航卫星系统GNSS超时的情况下，设置无线链路失败RLF的目标参数。
在一个可选的实施例中，所述装置还包括：
声明模块606，用于在所述终端设备的GNSS超时的情况下，声明主小区组MCG RLF；
所述设置模块604，用于在RLF变量报告中记录目标参数。
在一个可选的实施例中，所述设置模块604，用于将连接故障类型connectionFailureType设置为RLF；
和/或，
所述设置模块604，用于将RLF原因rlf-Cause设置为GNSS超时。
在一个可选的实施例中，所述装置还包括：
状态模块607，用于在接入层安全未激活的情况下，退回至空闲态；
或，
状态模块607，用于在接入层安全激活的情况下，退回至空闲态。
在一个可选的实施例中，所述设置模块604，用于将无线资源控制RRC连接的释放原因设置为其他；
或，
所述设置模块604，用于将所述RRC连接的释放原因设置为GNSS超时；
或，
所述设置模块604，用于将所述RRC连接的释放原因设置为RRC连接失败。
在一个可选的实施例中，所述装置还包括：
状态模块607，用于保持连接态。
在一个可选的实施例中，所述装置还包括：
第一接收模块603，用于接收网络设备发送的配置消息；其中
所述配置消息用于配置所述终端设备在GNSS超时的情况下退回至空闲态；或
所述配置消息用于配置所述终端设备在GNSS超时的情况下保持在连接态。
在一个可选的实施例中，所述装置还包括：
第一发送模块605，用于向网络设备发送第一消息，其中
所述第一消息用于指示所述终端设备支持在GNSS超时的情况下保持连接态；或
所述第一消息用于指示所述终端设备不支持在GNSS超时的情况下保持连接态。
在一个可选的实施例中，所述装置还包括：
传输模块601，用于在所述终端设备的GNSS超时的情况下，禁止上行传输。
在一个可选的实施例中，所述装置还包括：
传输模块601，用于在所述终端设备的GNSS超时的情况下，不监听物理下行控制信道 PDCCH；
传输模块601，用于在所述终端设备的GNSS超时的情况下，不进行下行接收。
在一个可选的实施例中，所述终端设备包括媒体介入控制MAC层；
所述传输模块601，用于在所述终端设备的GNSS超时的情况下，确定时间对齐超时；以及
所述传输模块601，用于执行时间对齐超时处理流程。
在一个可选的实施例中，所述传输模块601，用于确定主定时提前组pTAG和辅定时提前组sTAG均时间对齐超时；
所述传输模块601，用于确定所述pTAG时间对齐超时。
在一个可选的实施例中，所述装置还包括：
所述传输模块601，用于在所述终端设备的GNSS超时的情况下，禁止发起随机接入。
在一个可选的实施例中，所述终端设备包括媒体介入控制层MAC层和物理层PHY。
在一个可选的实施例中，所述终端设备包括无线资源控制RRC层；
所述传输模块601，用于在所述终端设备的GNSS超时的情况下，释放或禁用服务小区的物理上行控制信道PUCCH、短物理上行控制信道SPUCCH中的至少一个；
所述传输模块601，用于在所述终端设备的GNSS超时的情况下，释放或禁用服务小区的半持续调度SPS；
所述传输模块601，用于在所述终端设备的GNSS超时，且所述终端设备为窄带物联网NB-IOT设备的情况下，释放或禁用专用上行调度请求SR资源。
在一个可选的实施例中，所述传输模块601，用于在获取到GNSS定位的情况下，恢复禁用的服务小区的PUCCH或SPUCCH；
所述传输模块601，用于在获取到GNSS定位的情况下，恢复禁用的服务小区的SPS；
所述传输模块601，用于在获取到GNSS定位，且所述终端设备为NB-IOT设备的情况下，恢复禁用的专用SR资源。
在一个可选的实施例中，所述终端设备包括媒体接入控制MAC层；
所述传输模块601，用于在所述终端设备的GNSS超时的情况下，清空服务器小区的混合自动重传请求HARQ缓冲器；
所述传输模块601，用于在所述终端设备的GNSS超时的情况下，通知无线资源控制RRC层释放或禁用服务小区的信道探测参考信号SRS资源；
所述传输模块601，用于在所述终端设备的GNSS超时的情况下，清空或禁用配置的下行链路任务和上行链路授权；
所述传输模块601，用于在所述终端设备的GNSS超时的情况下，清空或禁用半持续信道状态信息CSI报告的物理上行共享信道PUSCH资源；
所述传输模块601，用于在所述终端设备的GNSS超时的情况下，禁止上行传输。
在一个可选的实施例中，所述传输模块601，用于在获取到GNSS定位的情况下，恢复禁用的配置的下行链路任务和上行链路授权。
在一个可选的实施例中，所述传输模块601，用于在获取到GNSS定位的情况下，恢复上行传输。
在一个可选的实施例中，所述传输模块601，用于在获取到GNSS定位的情况下，恢复下行接收。
在一个可选的实施例中，所述装置还包括：
第一发送模块605，用于在获取到GNSS定位的情况下，向网络设备发送GNSS有效期；
第一发送模块605，用于在获取到GNSS定位的情况下，向网络设备报告主小区组MACRLF。
在一个可选的实施例中，所述装置还包括：
执行模块602，用于在获取到GNSS定位的情况下，执行随机接入流程；
执行模块602，用于在获取到GNSS定位的情况下，执行连接重建流程。
在一个可选的实施例中，所述装置还包括：
第一接收模块603，用于在时间窗口内获取GNSS定位。
在一个可选的实施例中，所述装置还包括：
传输模块601，用于在所述时间窗口内，不进行上行传输或下行接收。
在一个可选的实施例中，所述装置还包括：
第一接收模块603，用于接收网络设备发送的所述时间窗口的配置信息。
请参考图8，其示出了本公开一个实施例提供的GNSS有效性的处理装置的框图。该装置具有实现上述终端设备侧的方法示例的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该装置可以是上文介绍的终端设备，也可以设置在终端设备中。如图8所示，该装置可以包括：
第二发送模块701，用于向网络设备发送全球导航卫星系统GNSS有效期。
在一个可选的实施例中，所述第二发送模块701，用于向所述网络设备发送随机接入消息，所述随机接入消息中包括所述GNSS有效期。
在一个可选的实施例中，所述第二发送模块701，用于向所述网络设备发送专用无线资源控制RRC消息，所述专用RRC消息中包括所述GNSS有效期。
在一个可选的实施例中，所述装置还包括：
第二接收模块702，用于接收网络设备发送的终端设备信息请求，所述终端设备信息请求用于请求终端设备上报GNSS有效期；
所述第二发送模块701，用于向所述网络设备发送终端设备信息响应，所述终端设备信息响应中包括所述GNSS有效期。
在一个可选的实施例中，所述第二发送模块701，用于在所述GNSS有效期小于第一有效期的情况下，向所述网络设备发送所述GNSS有效期；
其中，所述第一有效期为星历信息或公共时间同步的有效期。
在一个可选的实施例中，所述第二发送模块701，用于向所述网络设备发送第二有效期，所述第二有效期为所述GNSS有效期和第一有效期中的较小值；
其中，所述第一有效期为星历信息或公共时间同步的有效期。
在一个可选的实施例中，所述第二发送模块701，用于在获取到GNSS定位的情况下，向所述网络设备发送所述GNSS有效期。
在一个可选的实施例中，所述装置还包括：
第二接收模块702，用于接收所述网络设备通过系统消息发送的第一指示；
和/或，
第二接收模块702，用于接收所述网络设备通过无线资源控制RRC专用消息发送的所述第一指示；
其中，所述第一指示用于指示所述终端设备上报GNSS有效期，或，所述第一指示用于指示所述终端设备不上报所述GNSS有效期。
需要说明的一点是，上述实施例提供的装置在实现其功能时，仅以上述各个功能模块的划分进行举例说明，实际应用中，可以根据实际需要而将上述功能分配由不同的功能模块完成，即将设备的内容结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
请参考图9，其示出了本公开一个实施例提供的通信设备(终端设备或网络设备)的结 构示意图。该通信设备可以包括：处理器901、接收器902、发送器903、存储器904和总线905。
处理器901包括一个或者一个以上处理核心，处理器901通过运行软件程序以及模块，从而执行各种功能应用以及进行GNSS有效性的处理。
接收器902和发送器903可以实现为一个收发器906，该收发器906可以是一块通信芯片。
存储器904通过总线905与处理器901相连。
存储器904可用于存储计算机程序，处理器901用于执行该计算机程序，以实现上述方法实施例中通信设备执行的各个步骤。
此外，存储器904可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，易失性或非易失性存储设备包括但不限于：随机存储器(Random-Access Memory，RAM)和只读存储器(Read-Only Memory，ROM)、可擦写可编程只读存储器(Erasable Programmable Read-Only Memory，EPROM)、电可擦写可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、闪存或其他固态存储其技术，只读光盘(Compact Disc Read-Only Memory，CD-ROM)、高密度数字视频光盘(Digital Video Disc，DVD)或其他光学存储、磁带盒、磁带、磁盘存储或其他磁性存储设备。
其中，当通信设备实现为终端设备时，本公开实施例涉及的中的处理器901，可以执行上述图3至图6任一所示的方法中，由终端设备执行的步骤，此处不再赘述。
在一种可能的实现方式中，当通信设备实现为终端设备时，
所述处理器，用于在所述终端设备的全球导航卫星系统GNSS超时的情况下，设置无线链路失败RLF的目标参数。
在一种可能的实现方式中，当通信设备实现为终端设备时，
所述收发器，用于向网络设备发送全球导航卫星系统GNSS有效期。
本公开实施例还提供了一种计算机可读存储介质，所述存储介质中存储有计算机程序，所述计算机程序用于被核心网设备的处理器执行，以实现上述终端设备侧的GNSS有效性的处理方法。
可选地，该计算机可读存储介质可以包括：只读存储器(Read-Only Memory，ROM)、随机存储器(Random-Access Memory，RAM)、固态硬盘(Solid State Drives，SSD)或光盘等。其中，随机存取记忆体可以包括电阻式随机存取记忆体(Resistance Random Access Memory，ReRAM)和动态随机存取存储器(Dynamic Random Access Memory，DRAM)。
本公开实施例还提供了一种芯片，所述芯片包括可编程逻辑电路和/或程序指令，当所述芯片在终端设备上运行时，用于实现上述终端设备侧的GNSS有效性的处理方法。
本公开实施例还提供了一种计算机程序产品或计算机程序，所述计算机程序产品或计算机程序包括计算机指令，所述计算机指令存储在计算机可读存储介质中，终端设备的处理器从所述计算机可读存储介质读取并执行所述计算机指令，以实现上述终端设备侧的GNSS有效性的处理方法。
应理解，在本公开的实施例中提到的“指示”可以是直接指示，也可以是间接指示，还可以是表示具有关联关系。举例说明，A指示B，可以表示A直接指示B，例如B可以通过A获取；也可以表示A间接指示B，例如A指示C，B可以通过C获取；还可以表示A和B之间具有关联关系。
在本公开实施例的描述中，术语“对应”可表示两者之间具有直接对应或间接对应的关系，也可以表示两者之间具有关联关系，也可以是指示与被指示、配置与被配置等关系。
在本文中提及的“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在 B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
另外，本文中描述的步骤编号，仅示例性示出了步骤间的一种可能的执行先后顺序，在一些其它实施例中，上述步骤也可以不按照编号顺序来执行，如两个不同编号的步骤同时执行，或者两个不同编号的步骤按照与图示相反的顺序执行，本公开实施例对此不作限定。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本公开实施例所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述仅为本公开的示例性实施例，并不用以限制本公开，凡在本公开的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (40)

  1. 一种GNSS有效性的处理方法，其特征在于，所述方法由终端设备执行，所述方法包括：
    在所述终端设备的全球导航卫星系统GNSS超时的情况下，设置无线链路失败RLF的目标参数。
  2. 根据权利要求1所述的方法，其特征在于，所述在所述终端设备的全球导航卫星系统GNSS超时的情况下，设置无线链路失败RLF的目标参数，包括：
    在所述终端设备的GNSS超时的情况下，声明主小区组MCG RLF；以及
    在RLF变量报告中记录目标参数。
  3. 根据权利要求2所述的方法，其特征在于，所述在RLF变量报告中记录目标参数，包括以下中的至少一个：
    将连接故障类型connectionFailureType设置为RLF；
    将RLF原因rlf-Cause设置为GNSS超时。
  4. 根据权利要求1至3任一所述的方法，其特征在于，所述方法还包括：
    在接入层安全未激活的情况下，退回至空闲态；
    或，在接入层安全激活的情况下，退回至空闲态。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括以下中的一个：
    将无线资源控制RRC连接的释放原因设置为其他；
    将所述RRC连接的释放原因设置为GNSS超时；或
    将所述RRC连接的释放原因设置为RRC连接失败。
  6. 根据权利要求1至3任一所述的方法，其特征在于，所述方法还包括：
    保持连接态。
  7. 根据权利要求4至6任一所述的方法，其特征在于，所述方法还包括：
    接收网络设备发送的配置消息，其中
    所述配置消息用于配置所述终端设备在GNSS超时的情况下退回至空闲态；或
    所述配置消息用于配置所述终端设备在GNSS超时的情况下保持在连接态。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    向网络设备发送第一消息，其中
    所述第一消息用于指示所述终端设备支持在GNSS超时的情况下保持连接态；或
    所述第一消息用于指示所述终端设备不支持在GNSS超时的情况下保持连接态。
  9. 根据权利要求1至3任一所述的方法，其特征在于，所述方法还包括：
    在所述终端设备的GNSS超时的情况下，禁止上行传输。
  10. 根据权利要求1至3任一所述的方法，其特征在于，所述方法还包括以下中的至少一项：
    在所述终端设备的GNSS超时的情况下，不监听物理下行控制信道PDCCH；
    在所述终端设备的GNSS超时的情况下，不进行下行接收。
  11. 根据权利要求9所述的方法，其特征在于，所述终端设备包括媒体介入控制MAC层；
    所述在所述终端设备的GNSS超时的情况下，禁止上行传输，包括：
    在所述终端设备的GNSS超时的情况下，确定时间对齐超时；以及
    执行时间对齐超时处理流程。
  12. 根据权利要求11所述的方法，其特征在于，所述确定时间对齐超时，包括以下中的至少一项：
    确定主定时提前组pTAG和辅定时提前组sTAG均时间对齐超时；
    确定所述pTAG时间对齐超时。
  13. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    在所述终端设备的GNSS超时的情况下，禁止发起随机接入。
  14. 根据权利要求9所述的方法，其特征在于，所述禁止上行传输的步骤由所述终端设备的媒体介入控制层MAC层和物理层PHY执行。
  15. 根据权利要求9所述的方法，其特征在于，所述终端设备包括无线资源控制RRC层，并且所述在在所述终端设备的GNSS超时的情况下，禁止上行传输，包括以下中的至少一个：
    在所述终端设备的GNSS超时的情况下，释放或禁用服务小区的物理上行控制信道PUCCH、短物理上行控制信道SPUCCH中的至少一个；
    在所述终端设备的GNSS超时的情况下，释放或禁用服务小区的半持续调度SPS；
    在所述终端设备的GNSS超时，且所述终端设备为窄带物联网NB-IOT设备的情况下，释放或禁用专用上行调度请求SR资源。
  16. 根据权利要求15所述的方法，其特征在于，所述方法还包括以下中的至少一项：
    在获取到GNSS定位的情况下，恢复禁用的服务小区的PUCCH或SPUCCH；
    在获取到GNSS定位的情况下，恢复禁用的服务小区的SPS；
    在获取到GNSS定位，且所述终端设备为NB-IOT设备的情况下，恢复禁用的专用SR资源。
  17. 根据权利要求9所述的方法，其特征在于，所述终端设备包括媒体接入控制MAC层；
    所述在在所述终端设备的GNSS超时的情况下，禁止上行传输，包括以下中的至少一项：
    在所述终端设备的GNSS超时的情况下，清空服务器小区的混合自动重传请求HARQ缓冲器；
    在所述终端设备的GNSS超时的情况下，通知无线资源控制RRC层释放或禁用服务小区的物理上行控制信道PUCCH资源；
    在所述终端设备的GNSS超时的情况下，通知RRC层释放或禁用服务小区的信道探测参考信号SRS资源；
    在所述终端设备的GNSS超时的情况下，清空或禁用配置的下行链路任务和上行链路授权；
    在所述终端设备的GNSS超时的情况下，清空或禁用半持续信道状态信息CSI报告的物理上行共享信道PUSCH资源；
    在所述终端设备的GNSS超时的情况下，禁止上行传输。
  18. 根据权利要求17所述的方法，其特征在于，所述方法还包括：
    在获取到GNSS定位的情况下，恢复禁用的配置的下行链路任务和上行链路授权。
  19. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    在获取到GNSS定位的情况下，恢复上行传输。
  20. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    在获取到GNSS定位的情况下，恢复下行接收。
  21. 根据权利要求1至3任一所述的方法，其特征在于，所述方法还包括以下中的至少一项：
    在获取到GNSS定位的情况下，向网络设备发送GNSS有效期；
    在获取到GNSS定位的情况下，向网络设备报告主小区组MAC RLF。
  22. 根据权利要求4所述的方法，其特征在于，所述方法还包括以下中的至少一项：
    在获取到GNSS定位的情况下，执行随机接入流程；
    在获取到GNSS定位的情况下，执行连接重建流程。
  23. 根据权利要求1至3任一所述的方法，其特征在于，所述方法还包括：
    在时间窗口内获取GNSS定位。
  24. 根据权利要求23所述的方法，其特征在于，所述方法还包括：
    在所述时间窗口内，不进行上行传输或下行接收。
  25. 根据权利要求23所述的方法，其特征在于，所述方法还包括：
    接收网络设备发送的所述时间窗口的配置信息。
  26. 一种GNSS有效性的处理方法，其特征在于，所述方法由终端设备执行，所述方法包括：
    向网络设备发送全球导航卫星系统GNSS有效期。
  27. 根据权利要求26所述的方法，其特征在于，所述向网络设备发送全球导航卫星系统GNSS有效期，包括：
    向所述网络设备发送随机接入消息，所述随机接入消息中包括所述GNSS有效期。
  28. 根据权利要求26所述的方法，其特征在于，所述向网络设备发送全球导航卫星系统GNSS有效期，包括：
    向所述网络设备发送专用无线资源控制RRC消息，所述专用RRC消息中包括所述GNSS有效期。
  29. 根据权利要求28所述的方法，其特征在于，所述方法还包括：
    接收网络设备发送的终端设备信息请求，所述终端设备信息请求用于请求终端设备上报GNSS有效期；
    所述向所述网络设备发送专用无线资源控制RRC消息，包括：
    向所述网络设备发送终端设备信息响应，所述终端设备信息响应中包括所述GNSS有效期。
  30. 根据权利要求26至29任一所述的方法，其特征在于，所述向网络设备发送全球导航卫星系统GNSS有效期，包括：
    在所述GNSS有效期小于第一有效期的情况下，向所述网络设备发送所述GNSS有效期；
    其中，所述第一有效期为星历信息或公共时间同步的有效期。
  31. 根据权利要求26至29任一所述的方法，其特征在于，所述方法还包括：
    向所述网络设备发送第二有效期，所述第二有效期为所述GNSS有效期和第一有效期中的较小值；
    其中，所述第一有效期为星历信息或公共时间同步的有效期。
  32. 根据权利要求26至29任一所述的方法，其特征在于，所述向网络设备发送全球导航卫星系统GNSS有效期，包括：
    在获取到GNSS定位的情况下，向所述网络设备发送所述GNSS有效期。
  33. 根据权利要求26至29任一所述的方法，其特征在于，所述方法还包括：
    接收所述网络设备通过系统消息发送的第一指示；
    和/或，接收所述网络设备通过无线资源控制RRC专用消息发送的所述第一指示；
    其中，所述第一指示用于指示所述终端设备上报GNSS有效期，或，所述第一指示用于指示所述终端设备不上报所述GNSS有效期。
  34. 一种GNSS有效性的处理装置，其特征在于，所述装置用于实现终端设备，所述装置包括：
    设置模块，用于在所述终端设备的全球导航卫星系统GNSS超时的情况下，设置无线链路失败RLF的目标参数。
  35. 一种GNSS有效性的处理装置，其特征在于，所述装置用于实现终端设备，所述装置包括：
    第二发送模块，用于向网络设备发送全球导航卫星系统GNSS有效期。
  36. 一种终端设备，其特征在于，所述终端设备包括处理器；
    所述处理器，用于在所述终端设备的全球导航卫星系统GNSS超时的情况下，设置无线链路失败RLF的目标参数。
  37. 一种终端设备，其特征在于，所述终端设备包括收发器；
    所述收发器，用于向网络设备发送全球导航卫星系统GNSS有效期。
  38. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序，所述计算机程序用于被处理器执行，以实现如权利要求1至33任一项所述的GNSS有效性的处理方法。
  39. 一种芯片，其特征在于，所述芯片包括可编程逻辑电路和/或程序指令，当所述芯片运行时，用于实现如权利要求1至33任一项所述的GNSS有效性的处理方法。
  40. 一种计算机程序产品或计算机程序，其特征在于，所述计算机程序产品或计算机程序包括计算机指令，所述计算机指令存储在计算机可读存储介质中，处理器从所述计算机可读存储介质读取并执行所述计算机指令，以实现如权利要求1至33任一项所述的GNSS有效性的处理方法。
PCT/CN2021/144061 2021-12-31 2021-12-31 Gnss有效性的处理方法、装置、设备及存储介质 WO2023123514A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202180004809.XA CN114503783A (zh) 2021-12-31 2021-12-31 Gnss有效性的处理方法、装置、设备及存储介质
PCT/CN2021/144061 WO2023123514A1 (zh) 2021-12-31 2021-12-31 Gnss有效性的处理方法、装置、设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/144061 WO2023123514A1 (zh) 2021-12-31 2021-12-31 Gnss有效性的处理方法、装置、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2023123514A1 true WO2023123514A1 (zh) 2023-07-06

Family

ID=81510380

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/144061 WO2023123514A1 (zh) 2021-12-31 2021-12-31 Gnss有效性的处理方法、装置、设备及存储介质

Country Status (2)

Country Link
CN (1) CN114503783A (zh)
WO (1) WO2023123514A1 (zh)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023240615A1 (en) * 2022-06-17 2023-12-21 Mediatek Singapore Pte. Ltd. Schemes on epoch time indication in ntn
WO2024000229A1 (zh) * 2022-06-29 2024-01-04 Oppo广东移动通信有限公司 通信方法及通信装置
WO2024000466A1 (en) * 2022-06-30 2024-01-04 Mediatek Singapore Pte. Ltd. Schemes on gnss position fix in connected in iot ntn
WO2024000600A1 (en) * 2022-07-01 2024-01-04 Zte Corporation Wireless communication method and wireless terminal and wireless network node thereof
CN117528838A (zh) * 2022-07-29 2024-02-06 维沃移动通信有限公司 连接管理方法、用户设备及目标网络侧设备
US20240048227A1 (en) * 2022-08-05 2024-02-08 Samsung Electronics Co., Ltd. Triggering timing synchronization in non-terrestrial networks
WO2024031442A1 (en) * 2022-08-10 2024-02-15 Apple Inc. System and method for performing a global navigation satellite system (gnss) measurement in non-terrestrial network (ntn)
WO2024055152A1 (en) * 2022-09-13 2024-03-21 Mediatek Singapore Pte. Ltd. Conditions on triggering gnss position fix in ntn
CN115812328A (zh) * 2022-09-27 2023-03-17 北京小米移动软件有限公司 全球导航卫星系统gnss信息的生效时间确定方法及装置
CN117834070A (zh) * 2022-09-28 2024-04-05 大唐移动通信设备有限公司 定时信息的更新方法及装置
GB202214419D0 (en) * 2022-09-30 2022-11-16 Samsung Electronics Co Ltd Global Navigation Satellite System Measurement in Non-Terrestrial Networks
WO2024092649A1 (zh) * 2022-11-03 2024-05-10 Oppo广东移动通信有限公司 通信方法、装置、设备、存储介质、芯片、产品及程序
WO2024098358A1 (en) * 2022-11-11 2024-05-16 Zte Corporation Systems and methods for extending validation duration

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MODERATOR (MEDIATEK): "Summary #3 of AI 8.15.1 Enhancements to time and frequency synchronization", 3GPP DRAFT; R1-2112679, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20211111 - 20211119, 18 November 2021 (2021-11-18), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052077925 *

Also Published As

Publication number Publication date
CN114503783A (zh) 2022-05-13

Similar Documents

Publication Publication Date Title
WO2023123514A1 (zh) Gnss有效性的处理方法、装置、设备及存储介质
WO2021062726A1 (zh) 随机接入方法、终端设备、网络设备及存储介质
US20230208508A1 (en) Transmission control method and apparatus, device, and storage medium
WO2021016773A1 (zh) 监听随机接入响应的方法、终端设备、网络设备及存储介质
US20220124824A1 (en) Method for random access and communication device
WO2023130272A1 (zh) 信息处理方法、装置、设备及存储介质
WO2022205232A1 (zh) 覆盖增强等级的确定方法、配置方法、装置及存储介质
WO2022120747A1 (zh) 无线通信的方法和终端设备
WO2022077141A1 (zh) 随机接入响应接收窗的确定方法、装置、设备及介质
WO2021179139A1 (zh) 一种释放上行资源的方法、终端设备、网络设备
WO2022040867A1 (zh) 随机接入的方法、终端设备和网络设备
WO2023039809A1 (zh) Sr触发方法、随机接入方法、装置、设备及存储介质
WO2022151272A1 (zh) 定时器启动方法、装置、终端及存储介质
WO2023184286A1 (zh) 终端行为的确定方法、装置、设备及存储介质
WO2022160137A1 (zh) 无线通信方法、终端设备和网络设备
WO2022141414A1 (zh) 公共信息的广播方法、装置、设备及介质
WO2023097421A1 (zh) 信息上报方法、装置、设备、存储介质及程序产品
US20230422147A1 (en) Cell access control method, terminal device, and network device
US20230269686A1 (en) Method and apparatus for reporting timing advance in ntn, method and apparatus for receiving timing advance in ntn, and device
WO2023070682A1 (zh) 随机接入方法、装置、设备及存储介质
WO2022232991A1 (zh) Pdcch监听方法及drx上行重传定时器的控制方法
EP4319246A1 (en) Synchronization method and apparatus, and terminal device and network device
WO2022241793A1 (zh) 小区接入控制方法、装置、设备及存储介质
US20230403068A1 (en) Method for time-domain parameter determination, terminal device, and network device
US20240121762A1 (en) Wireless communication method, terminal device, and network device

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21969857

Country of ref document: EP

Kind code of ref document: A1