ENHANCED GNSS OPERATION OF IoT NTN

Abstract

A method and apparatus for enabling enhanced global navigation satellite system (GNSS) operation of an Internet of Things non-terrestrial network (IoT NTN) in a communication network is disclosed. In particular, enhancements are provided to address issues related to providing: a mechanism in which a user equipment (UE) reports a GNSS position positioning duration; a mechanism for the UE to report GNSS validity duration; a network (NW) triggered GNSS measurement mechanism; and a GNSS measurement mechanism triggered by the UE.

Description

Technical Field

[0001] The present invention generally relates to the field of wireless communications, and more particularly to methods and apparatus for enabling enhanced Global Navigation Satellite System (GNSS) operations for Internet of Things Non-Terrestrial Networks (IoT NTNs) in communication networks. Background Art

[0002] In a wireless communication network, a user equipment (UE) can communicate with a base station of the network by establishing a radio link between the UE and the base station. In 5G (New Radio or NR) or 4G (LTE) wireless networks, the UE can receive signaling and data from a serving base station in the downlink transmission direction or send signaling and data to the serving base station in the uplink transmission direction. In addition, satellite narrowband Internet of Things (NB-IoT) or enhanced machine type communication (eMTC) is also being used in a complementary manner for terrestrial deployments.

[0003] IoT operation in remote areas with low or no cellular connectivity is crucial for many different industries, including: transportation (e.g., maritime, road, rail, air) and logistics; solar energy, oil and gas harvesting; utilities; agriculture; environmental monitoring; mining; and many others. NB-IoT's capabilities are well suited to these types of IoT implementations, but satellite connectivity is needed to provide coverage beyond terrestrial deployments, where IoT connectivity is required. Given the solutions already available, a standardized solution that allows for global IoT operation anywhere on Earth is urgently needed. Importantly, satellite NB-IoT and eMTC are defined in a way that complements terrestrial deployments.

[0004] Work items in Release 17 (R17) IoT NTN have been identified to specify support for NB-IoT and eMTC on non-terrestrial networks. Enhancements should assume the following assumptions: priority will be given to standalone deployments of NB-IoT / eMTC supported within the Rel.17 timeframe (i.e., operating in carriers used only for NB-IoT NTN (and accordingly, eMTC NTN)); GNSS capability in the UE is considered a working assumption for both NB-IoT and eMTC devices. With this assumption, the UE can estimate and pre-compensate timing and frequency offsets for uplink (UL) transmissions with sufficient accuracy. Simultaneous GNSS and NTN NB-IoT / eMTC operation is not assumed, and the NB-IoT / eMTC design for terrestrial networks should be reused as much as possible; and transparent payload.

[0005] For GNSS operation for IoT NTN in Release 17, it is not expected that the UE will be in a connected state for an extended period of time. In GNSS operation for IoT NTN in Release 17, a Radio Resource Control (RRC) connection is initiated only when the UE has a valid GNSS position. Connected UEs are not expected to perform GNSS acquisitions. If the GNSS position becomes outdated, the connected UE will enter an idle state.

[0006] As part of Release 18 (R18), new work items were proposed to define further enhancements to NB-IoT NTN and eMTC NTN to optimize GNSS operation and power efficiency for long-term connections in situations where GNSS usage is sparse (compared to Release 17). In Release 18, IoT-NTN performance enhancements were introduced to address remaining issues in Release 17. Release 18 considers Release 17 IoT NTN as a baseline. Specifically, Release 18 aims to investigate and specify improved GNSS operation and reduced power consumption required for UE pre-compensated new position fixes during long connection times. Simultaneous GNSS and NTN NB-IoT / eMTC operation is not assumed.

[0007] In Release 18, IoT NTN needs to support the following scenarios: the UE can remain in connected mode for a long time; the UE can reacquire GNSS position in the connected state; and the UE does not need to perform GNSS positioning operations and IoT NTN transmissions simultaneously. Therefore, enhancements are required to address the following open issues from Release 18: Issue 1: Mechanism for UE to report GNSS position fix duration; Issue 2: Mechanism for UE to report GNSS validity duration; Issue 3: GNSS measurement mechanism triggered by NW; and Issue 4: GNSS measurement mechanism triggered by UE. Summary of the Invention

[0008] Disclosed are methods and apparatus for enabling enhanced Global Navigation Satellite System (GNSS) operations for Internet of Things Non-Terrestrial Networks (IoT NTNs) in communication networks. Specifically, enhancements are provided to address issues related to providing: a mechanism for user equipment (UE) to report GNSS position fix duration; a mechanism for UE to report GNSS validity duration; a network (NW)-triggered GNSS measurement mechanism; and a UE-triggered GNSS measurement mechanism.

[0009] In one example embodiment, a method for user equipment (UE) to interact with a network and a global navigation satellite system (GNSS) is disclosed, the method comprising: reporting a GNSS positioning duration or a GNSS validity duration when initiating access to a new cell of the network; wherein the UE initiates the access via a radio resource control (RRC) operation or a medium access control (MAC) control element (CE), and the UE reports at least one GNSS positioning duration or a GNSS validity duration. In one embodiment, the GNSS positioning duration is reported to the network in an RRC operation along with a remaining GNSS validity duration. In one embodiment, the GNSS positioning duration is reported in a predefined message in a MAC CE. In one embodiment, the GNSS positioning duration is reported via radio access UE capabilities. In one embodiment, if the GNSS positioning duration changes, the method further comprises reporting the updated GNSS positioning duration to the network via an RRC operation or a MAC CE. The RRC operation includes an uplink (UL) dedicated RRC message. In one embodiment, when reporting the GNSS positioning duration, an inhibit timer is utilized. The inhibit timer can be used to limit the reporting frequency.

[0010] In another embodiment, the GNSS validity duration may be reported using MAC CE. In one embodiment, the GNSS validity duration is reported using MAC CE after each GNSS measurement is completed. In one embodiment, when the GNSS validity duration is reported, a GNSS report periodicity timer is started, and when the GNSS report periodicity timer expires, the updated validity duration is reported using MAC CE. In one embodiment, the updated validity duration is reported using MAC CE when the UE mobility state changes or when the UE speed changes. In one embodiment, the updated validity duration is reported using MAC CE when the change in the remaining GNSS validity duration exceeds a threshold. In one embodiment, the updated validity duration is reported using MAC CE when the GNSS information is invalid for a period of time.

[0011] In another embodiment, a user equipment (UE) for interacting with a network and a global navigation satellite system (GNSS) is disclosed, the user equipment comprising: at least one antenna; at least one radio configured to communicate with the network using the at least one antenna; and at least one processor coupled to the at least one radio, wherein the at least one processor is configured to perform operations including: reporting a GNSS positioning duration or a GNSS validity duration upon initiating access to a new cell of the network, wherein the access is initiated via a radio resource control (RRC) operation or a medium access control (MAC) control element (CE) to report the at least one GNSS positioning duration or the GNSS validity duration. In one embodiment, the GNSS positioning duration is reported to the network in an RRC operation along with a remaining GNSS validity duration. In one embodiment, the GNSS positioning duration is reported in a predefined message in a MAC CE. In one embodiment, the GNSS positioning duration is reported via radio access UE capabilities. In one embodiment, if the GNSS positioning duration changes, the report further includes reporting the updated GNSS positioning duration to the network via an RRC operation or a MAC CE. The RRC operation includes an uplink (UL) dedicated RRC message. In one embodiment, an inhibit timer is utilized when reporting GNSS position fix durations. The inhibit timer can be used to limit the reporting frequency.

[0012] In another embodiment, the GNSS validity duration may be reported using MAC CE. In one embodiment, the GNSS validity duration is reported using MAC CE after each GNSS measurement is completed. In one embodiment, when the GNSS validity duration is reported, a GNSS report periodicity timer is started, and when the GNSS report periodicity timer expires, the updated validity duration is reported using MAC CE. In one embodiment, the updated validity duration is reported using MAC CE when the UE mobility state changes or when the UE speed changes. In one embodiment, the updated validity duration is reported using MAC CE when the change in the remaining GNSS validity duration exceeds a threshold. In one embodiment, the updated validity duration is reported using MAC CE when the GNSS information is invalid for a period of time.

[0013] In another example embodiment, a user equipment (UE) interacting with a network and a global navigation satellite system (GNSS) is disclosed, the user equipment comprising: at least one antenna; at least one radio configured to communicate with the network using the at least one antenna; and at least one processor coupled to the at least one radio, wherein the at least one processor is configured to perform operations including: receiving a GNSS measurement command in a medium access control (MAC) control element (CE) from the network when the UE GNSS is about to become obsolete; and determining whether to perform GNSS measurements. In one embodiment, upon receiving the GNSS measurement command, the UE further comprises always performing GNSS measurements. In one embodiment, upon receiving the GNSS measurement command, the UE further comprises determining whether to perform GNSS measurements based on whether valid GNSS information exists. In one embodiment, upon receiving the GNSS measurement command, the UE further comprises determining whether to perform GNSS measurements based on a selection determination made by the UE or when a remaining GNSS validity condition set by the network is satisfied. In one embodiment, upon determining not to perform GNSS measurements, the UE further transmits a determination not to perform GNSS measurements to the network in a GNSS validity duration MAC CE.

[0014] In one embodiment, when it is determined that GNSS measurements are to be performed, GNSS measurements are performed in a specified measurement gap configuration, and when the GNSS measurements are completed, a GNSS valid duration MAC CE is transmitted to the network. In one embodiment, the specified measurement gap configuration includes a gap duration provided to the UE by radio resource control (RRC) signaling and is enabled by a GNSS measurement command MAC CE. In one embodiment, if only one gap is configured by RRC signaling, the RRC-configured gap for GNSS measurements is applied, and if more than one gap is configured by RRC, a gap configuration index is enabled for GNSS measurements. In one embodiment, the specified measurement gap configuration includes a GNSS gap duration, offset, and period provided to the UE in a GNSS measurement command MAC CE. In one embodiment, a start time point for performing GNSS measurements after receiving a GNSS measurement command MAC CE associated with a gap pattern configured in the RRC occurs at the latest measurement opportunity configured by the RRC. In one embodiment, a start time point for performing GNSS measurements after receiving a GNSS measurement command MAC CE occurs at a predefined delay time after receiving the GNSS measurement command MAC CE. In one embodiment, a start time point of performing GNSS measurement after receiving the GNSS measurement command MAC CE is defined in the GNSS measurement command MAC CE.

[0015] In another embodiment, a user equipment (UE) for interacting with a network and a global navigation satellite system (GNSS) is disclosed, the user equipment comprising: at least one antenna; at least one radio, wherein the at least one radio is configured to communicate with the network using the at least one antenna; and at least one processor coupled to the at least one radio, wherein the at least one processor is configured to perform operations including: determining whether to perform GNSS measurements based on GNSS information becoming invalid. In one embodiment, based on the GNSS information becoming invalid, a timer is restarted, and when the timer expires, GNSS measurements are performed. In one embodiment, based on the GNSS information becoming invalid, GNSS measurements are automatically and autonomously performed. In one embodiment, if the GNSS measurements cannot be performed within a predetermined time period, a radio link failure (RLF) is declared and idle mode is resumed. In one embodiment, based on the GNSS information becoming invalid and the UE having uplink data to transmit, the UE resumes idle mode. In one embodiment, based on the GNSS information becoming invalid and the UE having uplink data to transmit, GNSS measurements are automatically and autonomously performed. In one embodiment, based on GNSS information becoming invalid and the UE having uplink data to transmit and GNSS being unable to acquire within a predetermined amount of time, the UE declares RLF and returns to idle mode. In one embodiment, based on detecting the RLF, GNSS measurements are automatically and autonomously performed. In one embodiment, based on detecting the RLF, GNSS measurements are performed if the RLF is due to an UL transmission failure. In one embodiment, if the GNSS measurements fail, the UE declares GNSS failure and returns to idle mode.

[0016] Other methods and apparatus are also described. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The present invention is illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate similar elements.

[0018] Figure 1 An example wireless communication system according to one embodiment of the present disclosure is illustrated.

[0019] Figure 2 A user equipment directly communicating with a base station (BS) according to one embodiment of the present disclosure is illustrated.

[0020] Figure 3 An example block diagram of a UE according to one embodiment of the present disclosure is illustrated.

[0021] Figure 4An example block diagram of a BS according to one embodiment of the present disclosure is illustrated.

[0022] Figure 5 An example block diagram of a cellular communication circuit according to one embodiment of the present disclosure is illustrated.

[0023] Figure 6 A process for a UE to report a GNSS position fix duration to a network according to one embodiment of the present disclosure is illustrated.

[0024] Figure 7 A process for a UE to report a GNSS validity duration to a network according to one embodiment of the present disclosure is illustrated.

[0025] Figure 8A A process for a UE to receive a trigger from a NW to perform UE GNSS measurements according to one embodiment of the present disclosure is illustrated.

[0026] Figure 8B A process for a UE to receive a trigger from a NW to perform UE GNSS measurements that can be skipped by the UE according to one embodiment of the present disclosure is illustrated.

[0027] Figure 9A and Figure 9B is a diagram of an example of interstitial opportunities for GNSS measurements triggered by a NW according to one embodiment of the present disclosure.

[0028] Figure 10 is a block diagram of components for different use cases of UE-triggered GNSS measurements according to one embodiment of the present disclosure. DETAILED DESCRIPTION

[0029] In the following description, numerous specific details are set forth to provide a thorough explanation of the embodiments of the present invention. However, it will be apparent to those skilled in the art that the embodiments of the present invention may be practiced without these specific details. In other instances, well-known components, structures, and techniques have not been shown in detail in order to avoid obscuring the understanding of this description.

[0030] Reference in this specification to "some embodiments" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the present invention. The appearance of the phrase "in some embodiments" in various places in this specification does not necessarily refer to the same embodiment.

[0031] In the following description and claims, the terms "coupled" and "connected," and their derivatives, may be used. It should be understood that these terms are not intended to be synonymous with each other. "Coupled" is used to indicate that two or more elements, which may or may not be in direct physical or electrical contact with each other, cooperate or interact with each other. "Connected" is used to indicate the establishment of communication between two or more elements that are coupled to each other.

[0032] The processes shown in the following figures are performed by processing logic that includes hardware (e.g., circuitry, dedicated logic, etc.), software (such as software running on a general-purpose computer system or a dedicated machine), or a combination of both. Although the processes are described below as operating in certain sequential order, it should be understood that some of the operations described may be performed in a different order. In addition, some operations may be performed in parallel rather than sequentially.

[0033] The terms "server," "client," and "device" are intended to refer generally to data processing systems and not specifically to specific form factors of a server, client, and / or device.

[0034] Figure 1 A simplified example wireless communication system according to one aspect of the present disclosure is illustrated. Note that Figure 1 The system is only one example of a possible system, and features of the present disclosure may be implemented in any of a variety of systems as desired.

[0035] As shown, the example wireless communication system includes a base station 102A that communicates with one or more user devices 106A, 106B, 106N, etc. via a transmission medium. Each of the user devices may be referred to herein as a "user equipment" (UE). Therefore, user device 106 is referred to as a UE or UE device.

[0036] Base station (BS) 102A may be a base transceiver station (BTS) or a cell site ("cellular base station") and may include hardware that enables wireless communications with UEs 106A through 106N.

[0037] The communication area (or coverage area) of a base station may be referred to as a "cell". The base station 102A and the UE 106 may be configured to communicate over a transmission medium using any of a variety of radio access technologies (RATs), also known as wireless communication technologies or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-Advanced (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if the base station 102A is implemented in the context of LTE, it may alternatively be referred to as an "eNodeB" or "eNB". Note that if the base station 102A is implemented in the context of 5G NR, it may alternatively be referred to as a "gNodeB" or "gNB".

[0038] As shown, base station 102A may also be configured to communicate with network 100 (e.g., a cellular service provider's core network, a telecommunications network such as the Public Switched Telephone Network (PSTN), and / or the Internet, among other possibilities). Thus, base station 102A may facilitate communications between user devices and / or between user devices and network 100. Specifically, cellular base station 102A may provide UE 106 with various telecommunications capabilities, such as voice, SMS, and / or data services.

[0039] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore provide a network of cells that can provide continuous or nearly continuous overlapping service to UEs 106A-N and similar devices over a geographic area via one or more cellular communication standards.

[0040] Thus, although base station 102A may function as Figure 1 106A-N, each UE 106 may also be capable of receiving signals from (and possibly within communication range of) one or more other cells (which may be provided by base stations 102B-N and / or any other base stations), which may be referred to as "neighboring cells." Such cells may also be capable of facilitating communications between user devices and / or between user devices and network 100. Such cells may include "macro" cells, "micro" cells, "pico" cells, and / or cells of any other variety of granularity of service area size. For example, in Figure 1 The base stations 102A-B illustrated in FIG may be macro cells, while the base station 102N may be a micro cell. Other configurations are also possible.

[0041] In some embodiments, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or "gNB." In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, a gNB cell may include one or more transmit and receive points (TRPs). Furthermore, UEs capable of operating in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

[0042] It is noted that the UE 106 may be capable of communicating using multiple wireless communication standards. For example, the UE 106 may be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.). If desired, the UE 106 may also or alternatively be configured to communicate using one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcast standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocols. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0043] Figure 2 A UE 106 is illustrated that directly communicates with a base station 102 through uplink and downlink communications according to one aspect of the present disclosure. The UE 106 can be a device with cellular communication capabilities, such as a mobile phone, a handheld device, a computer or a tablet computer, or in fact any type of wireless device. The UE 106 may include a processor configured to execute program instructions stored in a memory. The UE 106 can perform any of the method embodiments described herein by executing such stored instructions. Alternatively or in addition, the UE 106 may include programmable hardware elements, such as a field programmable gate array (FPGA) configured to perform any of the method embodiments described herein or any part of any of the method embodiments described herein.

[0044] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT, 1xEV-DO, HRPD, eHRPD) or LTE using a single shared radio and / or GSM or LTE using a single shared radio. The shared radio may be coupled to a single antenna, or may be coupled to multiple antennas (e.g., for MIMO) for performing wireless communications. Generally speaking, the radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio may implement one or more receive chains and transmit chains using the aforementioned hardware. For example, UE 106 may share one or more portions of a receive chain and / or transmit chain between multiple wireless communication technologies (such as those discussed above).

[0045] In some embodiments, the UE 106 may include a separate transmit chain and / or receive chain (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As another possibility, the UE 106 may include one or more radio components shared between multiple wireless communication protocols, and one or more radio components used uniquely by a single wireless communication protocol. For example, the UE 106 may include a shared radio component for communicating using either LTE or 5GNR (or LTE or 1xRTT, or LTE or GSM), and a separate radio component for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0046] Figure 3 An example simplified block diagram of a communication device 106 according to one aspect of the present disclosure is illustrated. Note that Figure 3The block diagram of the communication device is only an example of a possible communication device. According to the embodiment, the communication device 106 can be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (such as a laptop computer, a notebook or a portable computing device), a tablet computer and / or a combination of devices, in addition to other devices. As shown, the communication device 106 may include a group of components 300 configured to perform core functions. For example, the group of components can be implemented as a system on a chip (SOC), which can include parts for various purposes. Alternatively, the group of components 300 can be implemented as a separate component or group of components for various purposes. The group of components 300 can be coupled to various other circuits of the communication device 106 (e.g., communicatively; directly or indirectly).

[0047] For example, the communication device 106 may include various types of memory (e.g., including NAND flash memory 310), input / output interfaces such as a connector I / F 320 (e.g., for connecting to a computer system; a docking station; a charging station; input devices such as a microphone, a camera, a keyboard; output devices such as a speaker; etc.), a display 360 that may be integrated with the communication device 106 or external to the communication device, and cellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc., and short-range to medium-range wireless communication circuitry 329 (e.g., Bluetooth TM and WLAN circuitry). In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0048] Cellular communication circuitry 330 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 335 and 336, as shown. Short-range to medium-range wireless communication circuitry 329 may also be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 337 and 338, as shown. Alternatively, short-range to medium-range wireless communication circuitry 329 may be (e.g., communicatively; directly or indirectly) coupled to antennas 335 and 336 in addition to or in lieu of being (e.g., communicatively; directly or indirectly) coupled to antennas 337 and 338. Short-range to medium-range wireless communication circuitry 329 and / or cellular communication circuitry 330 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input, multiple-output (MIMO) configuration.

[0049] In some embodiments, as further described below, the cellular communication circuitry 330 can include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radios) for multiple radio access technologies (RATs) (e.g., a first receive chain for LTE and a second receive chain for 5G NR). Furthermore, in some embodiments, the cellular communication circuitry 330 can include a single transmit chain that can switch between radios dedicated to specific RATs. For example, a first radio can be dedicated to a first RAT, such as LTE, and can communicate with a dedicated receive chain and a transmit chain shared with an additional radio, such as a second radio that can be dedicated to a second RAT (e.g., 5G NR) and can communicate with both the dedicated receive chain and the shared transmit chain.

[0050] The communication device 106 may also include and / or be configured for use with one or more user interface elements. The user interface elements may include any of a variety of elements, such as a display 360 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of a touch screen display), a mouse, a microphone and / or speakers, one or more cameras, one or more buttons, and / or any of a variety of other elements capable of providing information to a user and / or receiving or interpreting user input.

[0051] The communication device 106 may also include one or more smart cards 345 , such as one or more UICCs (Universal Integrated Circuit Cards) 345 , having SIM (Subscriber Identity Module) functionality.

[0052] As shown, the SOC 300 may include a processor 302 that may execute program instructions for the communication device 106 and a display circuit 304 that may perform graphics processing and provide display signals to a display 360. The processor 302 may also be coupled to a memory management unit (MMU) 340 (the MMU may be configured to receive addresses from the processor 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310)) and / or to other circuits or devices (such as the display circuit 304, the short-range wireless communication circuit 229, the cellular communication circuit 330, the connector I / F 320, and / or the display 360). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of the processor 302.

[0053] As described above, the communication device 106 can be configured to communicate using wireless and / or wired communication circuits. The communication device 106 can also be configured to determine physical downlink shared channel scheduling resources for the user equipment device and the base station. In addition, the communication device 106 can be configured to select and group CCs (component carriers) from the wireless link and determine virtual CCs from the selected CC group. The wireless device can also be configured to perform physical downlink resource mapping based on the aggregate resource matching pattern of the CC group.

[0054] As described herein, the communication device 106 may include hardware and software components for implementing the above-described features for determining physical downlink shared channel scheduling resources for the communication device 106 and the base station. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 302 of the communication device 106 may be configured to implement some or all of the features described herein. Alternatively (or in addition), the processor 302 may be configured as a programmable hardware element, such as an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360, the processor 302 of the communication device 106 may be configured to implement some or all of the features described herein.

[0055] Furthermore, as described herein, processor 302 may include one or more processing elements. Thus, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform one or more functions of processor 302.

[0056] Furthermore, as described herein, both the cellular communication circuitry 330 and the short-range wireless communication circuitry 329 may include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuitry 330, and similarly, one or more processing elements may be included in the short-range wireless communication circuitry 329. Thus, the cellular communication circuitry 330 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuitry 330. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuitry 230. Similarly, the short-range wireless communication circuitry 329 may include one or more ICs configured to perform the functions of the short-range wireless communication circuitry 329. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-range wireless communication circuitry 329.

[0057] Figure 4 An example block diagram of a base station 102 according to one aspect of the present disclosure is illustrated. Figure 4 The base station 102 is only one example of a possible base station. As shown, the base station 102 may include a processor 404 that may execute program instructions for the base station 102. The processor 404 may also be coupled to a memory management unit (MMU) 440 that may be configured to receive addresses from the processor 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450) or to other circuits or devices.

[0058] The base station 102 may include at least one network port 470. The network port 470 may be configured to couple to a telephone network and provide access to the telephone network as described above. Figure 1 and Figure 2 Multiple devices such as UE 106 of the telephone network described in.

[0059] The network port 470 (or an additional network port) may also or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as the UE 106. In some cases, the network port 470 may be coupled to a telephony network via the core network, and / or the core network may provide a telephony network (e.g., in other UEs served by the cellular service provider).

[0060] In some embodiments, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or "gNB." In such embodiments, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) (5GC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transmit and receive points (TRPs). Furthermore, UEs capable of operating in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

[0061] Base station 102 may include at least one antenna 434, and may include multiple antennas. The at least one antenna 434 may be configured to function as a wireless transceiver and may be further configured to communicate with UE 106 via radio 430. Antenna 434 communicates with radio 430 via communication chain 432. Communication chain 432 may be a receive chain, a transmit chain, or both. Radio 430 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, and the like.

[0062] The base station 102 may be configured to perform wireless communications using multiple wireless communication standards. In some instances, the base station 102 may include multiple radio components that enable the base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station 102 may include an LTE radio component for performing communications according to LTE and a 5G NR radio component for performing communications according to 5G NR. In this case, the base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, the base station 102 may include a multimode radio component capable of performing communications according to any one of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0063] As further described later herein, BS 102 may include hardware and software components for implementing or supporting a specific implementation of the features described herein. The processor 404 of the base station 102 may be configured to implement or support implementation of part or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 404 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit) or a combination thereof. Alternatively (or in addition), in combination with one or more of the other components 430, 432, 434, 440, 450, 460, 470, the processor 404 of the BS 102 may be configured to implement or support a specific implementation of part or all of the features described herein.

[0064] Furthermore, as described herein, processor 404 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor 404. Thus, processor 404 may include one or more integrated circuits (ICs) configured to perform the functions of processor 404. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 404.

[0065] Furthermore, as described herein, radio 430 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio 430. Thus, radio 430 may include one or more integrated circuits (ICs) configured to perform the functions of radio 430. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio 430.

[0066] Figure 5 An example simplified block diagram of a cellular communication circuit according to one aspect of the present disclosure is illustrated. Note that Figure 5 The block diagram of the cellular communication circuitry is only one example of possible cellular communication circuitry. Depending on the embodiment, the cellular communication circuitry 330 may be included in a communication device such as the communication device 106 described above. As described above, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of devices, among other devices.

[0067] Cellular communication circuitry 330 may be coupled (eg, communicatively; directly or indirectly) to one or more antennas, such as ( Figure 3 In some embodiments, the cellular communication circuit 330 may include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, Figure 5 As shown, the cellular communication circuitry 330 may include a modem 510 and a modem 520. The modem 510 may be configured for communication according to a first RAT (e.g., such as LTE or LTE-A), and the modem 520 may be configured for communication according to a second RAT (e.g., such as 5G NR).

[0068] As shown, the modem 510 may include one or more processors 512 and a memory 516 in communication with the processor 512. The modem 510 may communicate with a radio frequency (RF) front end 530. The RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 530 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534. In some embodiments, the receive circuitry 532 may communicate with a downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0069] Similarly, the modem 520 may include one or more processors 522 and a memory 526 in communication with the processors 522. The modem 520 may communicate with an RF front end 540. The RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 540 may include receive circuitry 542 and transmit circuitry 544. In some embodiments, the receive circuitry 542 may communicate with a DL front end 560, which may include circuitry for receiving radio signals via the antenna 335b.

[0070] In some embodiments, the switch 570 can couple the transmit circuitry 534 to an uplink (UL) front end 572. Additionally, the switch 570 can couple the transmit circuitry 544 to the UL front end 572. The UL front end 572 can include circuitry for transmitting radio signals via the antenna 336. Thus, when the cellular communication circuitry 330 receives an instruction to transmit according to a first RAT (e.g., via a transmit chain including the transmit circuitry 534 and the UL front end 572), the switch 570 can be switched to a first state that allows the modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain including the transmit circuitry 534 and the UL front end 572). Similarly, when the cellular communication circuitry 330 receives an instruction to transmit according to a second RAT (e.g., via a transmit chain including the transmit circuitry 544 and the UL front end 572), the switch 570 can be switched to a second state that allows the modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain including the transmit circuitry 544 and the UL front end 572).

[0071] As described herein, the modem 510 may include hardware and software components for implementing the above-mentioned features or for selecting periodic resource portions for user equipment devices and base stations and for various other technologies described herein. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 512 may be configured to implement part or all of the feature parts described herein. Alternatively (or in addition thereto), the processor 512 may be configured as a programmable hardware element, such as an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). Alternatively (or additionally), in combination with one or more of the other components 530, 532, 534, 550, 570, 572, 335, and 336, the processor 512 may be configured to implement part or all of the feature parts described herein.

[0072] Furthermore, as described herein, processor 512 may include one or more processing elements. Thus, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0073] As described herein, the modem 520 may include hardware and software components for implementing the above-mentioned features or for selecting a periodic resource portion on a wireless link between a UE and a base station, as well as for various other technologies described herein. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 522 may be configured to implement part or all of the feature parts described herein. Alternatively (or in addition thereto), the processor 522 may be configured as a programmable hardware element, such as an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). Alternatively (or additionally), in combination with one or more of the other components 540, 542, 544, 550, 570, 572, 335, and 336, the processor 522 may be configured to implement part or all of the feature parts described herein.

[0074] Furthermore, as described herein, processor 522 may include one or more processing elements. Thus, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0075] Figure 6 The following illustrates a process for UE 106 to report a GNSS position fix duration to network 100. It should be understood that the network 100 discussed below may also refer to a non-terrestrial network (NTN) that delivers telecommunication connectivity from space and the stratosphere (e.g., via satellite and other NTN technology types). For example, if desired, UE 106 may be configured to communicate using one or more Global Navigation Satellite Systems (GNSS, such as GPS or GLONASS) and / or any other wireless communication protocol. A GNSS position fix duration may be the duration required for a GNSS receiver to acquire signals from satellites, perform triangulation, and obtain a position solution, sometimes referred to as the GNSS position fix duration. This duration depends on how the GNSS receiver is started. Different UEs may have different GNSS position fix durations in different GNSS start states (e.g., 30 seconds for cold start, 5-10 seconds for warm start, and 1-2 seconds for hot start). Based on knowledge of the GNSS position fix duration, network 100 may determine the GNSS measurement gap configuration. Furthermore, it should be understood that UE 106 may typically be an Internet of Things (IoT) device.

[0076] like Figure 6As can be seen in FIG, a mechanism for UE 106 to report GNSS position fix duration to network 100 is described. As an example, when UE 106 initiates access to a new cell, UE 106 will report GNSS position fix duration 610 during initial access to network 100. UE 106 may initiate access via a radio resource control (RRC) operation or a medium access control (MAC) control element (CE). As an example, UE 106 initiates RRC connection establishment / resumption / reestablishment or UE first access in a target cell via handover. UE 106 may report one or more values ​​(one value per GNSS start state) to NW 100. Specifically, UE 106 may report this information to NW 100 via RRC signaling or via MAC CE.

[0077] In one implementation option, the GNSS positioning duration is reported together with the remaining GNSS valid duration in an RRC operation or message to the NW 100. Examples of such messages may include: RCConnectionSetupComplete, RRCConnectionReestablishmentComplete, RRCConnectionResumeComplete, RRCConnectionReconfigurationComplete for handover cases.

[0078] In one implementation option, the GNSS positioning duration is reported in a predefined message in a MAC CE. As an example, the UE 106 reports the GNSS positioning duration to the network 100 via a MAC CE (eg, in Msg3, Msg 5, etc.).

[0079] In one implementation option, the UE 100 may report the GNSS positioning duration per GNSS state via the radio access UE capabilities.

[0080] During the RRC connection, if the UE GNSS start state or positioning duration changes, the UE 106 may report the updated GNSS positioning duration and / or GNSS start state 620 to the NW 100. The report may be sent via UE-specific RRC signaling or MAC CE. In one embodiment option, the UE 106 reports the updated GNSS positioning duration / start state to the NW 100 via a UE-specific uplink (UL) RRC message. In one embodiment option, the UE 106 reports the updated GNSS positioning duration / start state to the NW 100 via a MAC CE. In one embodiment option, a prohibit timer may be utilized to limit the reporting frequency. As an example, the UE 106 starts a prohibit timer when reporting the GNSS positioning duration to the NW 100 and is not allowed to transmit this information before the timer expires.

[0081] Figure 7 This section illustrates a process for UE 106 to report the GNSS validity duration to network 100. By reporting from UE 106, NW 100 can determine how long the UE's GNSS location information is valid for data transmission in a connected state and can trigger UE 106 to perform GNSS positioning operations (i.e., GNSS measurements) before the GNSS information expires. During initial access, UE 106 reports the remaining time / validity duration to NW 100 via RRC signaling (similar to legacy R17). This can occur in: RRCConnectionSetupComplete, RRCConnectionReestablishmentComplete, RRCConnectionResumeComplete, and RRCConnectionReconfigurationComplete.

[0082] Furthermore, during the RRC connection, UE 106 may report an updated GNSS validity duration to network 100 via MAC CE 710 in various ways. In one embodiment, the GNSS validity duration is reported to network 100 using MAC CE 715 after each GNSS measurement is completed. Periodic reporting 720 from UE 106 to network 100 may also be used. As an example embodiment, when reporting the GNSS validity duration to network 100, UE 106 starts a GNSS reporting periodicity timer and, when the GNSS reporting periodicity timer expires, reports the updated validity duration to network 100 using MAC CE. In one embodiment, the updated validity duration is reported to network 100 using MAC CE when the UE mobility state changes or when the UE speed changes 725. Examples of mobility state changes may include: static, low mobility, medium mobility, high mobility, etc. A speed change may be associated with exceeding a threshold (>threshold). In one embodiment, when the estimated change in the remaining GNSS validity duration exceeds a threshold 730, an updated validity duration is reported using a MAC CE. In one embodiment, when the GNSS information is invalid for a period of time 735 (e.g., invalid for an X period of time in the future), an updated validity duration is reported using a MAC CE. Furthermore, to limit the frequency of MAC CE reporting, a prohibit timer can be introduced for control. Furthermore, the MAC CEs for the GNSS validity duration and the GNSS positioning duration can be designed in the same or separate MAC CEs.

[0083] Figure 8A This document illustrates a process in which UE 106 receives a trigger from NW 100 to perform UE GNSS measurements. It also describes a use case in which NW 100 triggers UE GNSS measurements. For example, NW 100 can trigger UE 106 to perform GNSS measurements when UE GNSS information is about to become outdated. Furthermore, NW 100 can trigger UE 106 to perform GNSS measurements when the gNB cannot correctly decode the UE's data due to an inaccurate UL TA.

[0084] like Figure 8A As can be seen in FIG, NW 100 can trigger the GNSS measurement mechanism. UE 106 is in a connected state. NW 100 can pre-configure the GNSS measurement gap configuration via RRC (RRCConnectionReconfig (GNSS measurement gap configuration)) 810. Next, NW 100 sends a GNSS trigger measurement command MAC CE 815 to UE 100.

[0085] Based on this, the UE 100 may perform various operations based on receiving the command MAC CE. In one embodiment, the UE 100 always performs GNSS measurements according to the NW command. In one embodiment, the UE 100 may decide whether to perform GNSS measurements based on whether it has valid GNSS information. The UE 100 may make the decision to skip GNSS measurements in the following ways: 1) depending on the UE implementation or 2) when the remaining GNSS validity condition > T (e.g., configured by the NW). Brief reference Figure 8B It should be noted that, in one embodiment, after receiving the GNSS measurement command (MAC CE) 815, the UE 106 may decide to skip the GNSS measurement if the remaining GNSS valid duration is (>T).

[0086] If the UE 106 needs to perform GNSS measurements, the UE 106 starts the GNSS measurements in the indicated measurement gap when necessary. When the GNSS measurements are completed, the UE 106 sends a response message (e.g., GNSS valid duration MAC CE) 806 to the NW 100. If the UE 106 does not need to perform GNSS measurements, the UE 106 sends a response message (e.g., GNSS valid duration MAC CE) 806 to the NW 100.

[0087] It should be noted that when UE 106 transmits a response message to NW 100, UE 106 may perform a RACH or SR (depending on the TATimer status) to the NW to request an UL grant. Furthermore, when NW 100 transmits a GNSS measurement command to the UE, the NW may simultaneously provide the UE with an uplink transmission grant to report the GNSS validity duration MAC CE (as a response). Furthermore, the UE can perform an UL transmission after the GNSS measurement is completed without waiting for the end of the interstitial opportunity.

[0088] A method for determining the gap timing for performing GNSS measurements will now be described. Various options are available for gap configuration. In one example option, only the gap duration is included in the gap configuration. In one example option, the gap configuration includes the GNSS gap duration, offset, and periodicity. The gap configuration is enabled for triggered GNSS measurements in various optional ways. In one optional way, the gap configuration is provided to UE 106 via RRC signaling and enabled by a GNSS trigger command MAC CE. As an example, if RRC configures only one gap, when UE 106 receives the trigger command, UE 106 may apply the RRC configured gap to GNSS measurements. Alternatively, if RRC configures more than one gap, NW 100 may indicate which gap configuration (i.e., index) is enabled for GNSS measurements. In another optional way, the gap configuration is provided directly to UE 106 in the GNSS trigger command MAC CE.

[0089] In one embodiment, a start time point for performing GNSS measurements when a GNSS trigger command is received is defined. In one example, this is related to the gap pattern configured in the RRC. When the UE 106 receives the GNSS trigger command, the UE 106 starts the GNSS measurement in the nearest measurement opportunity according to the RRC configuration. In one example, this is related to the time point when the UE 106 receives the GNSS trigger command. When the UE 106 receives the GNSS trigger command at T, the UE starts the GNSS measurement at T+K_delay. It should be noted that K_delay can be predefined in the specification or explicitly indicated in the MAC CE. In another optional example, the start time point is directly indicated in the MAC CE, which is independent of the time T when the UE receives the GNSS trigger command.

[0090] refer to Figure 9A and Figure 9B , describes an example of intermittent opportunities for GNSS measurements triggered by NW. For example, refer to Figure 9A The start time of the gap opportunity is determined by the RRC configuration, where the gap configuration includes: offset = 0; duration = 2 seconds; periodicity = 10 seconds. Figure 9A This can be seen in the following example: Figure 9A Visible in the figure is the GNSS trigger command MAC CE and the GNSS response MAC CE (eg, validity duration MC CE)

[0091] For example, reference Figure 9BThe start time of the intermittent opportunity for GNSS measurement is determined by the GNSS trigger command MAC CE. As can be seen, a GNSS trigger command MAC CE with a duration of 1 second and a delay of T is issued. After time T, a GNSS response MAC CE (e.g., validity duration MAC CE) occurs from the UE.

[0092] refer to Figure 10 In this article, we will describe some use cases for UE-triggered GNSS measurements. UE-triggered GNSS measurements may occur when the UE has UL data arriving but the GNSS information is invalid, or when the UE GNSS information is about to become invalid but it has not yet received a GNSS trigger command from the NW side.

[0093] Various UE-triggered GNSS measurement mechanisms will be described. In one example solution, a mechanism based on timer 1010 may be used. The UE starts or restarts timer 1010 upon receiving a GNSS trigger command MAC CE or upon GNSS measurement completion. When the timer expires, the UE will autonomously perform GNSS measurements.

[0094] In another example solution, the UE autonomously starts GNSS measurements when GNSS becomes unavailable 1020. If the UE cannot successfully acquire GNSS information within X period of time, the UE may declare a radio link failure (RLF) 1030 and the UE returns to idle.

[0095] In another example solution, when GNSS becomes invalid 1020 and the UE has uplink data to send, the UE does not need to return to idle when the GNSS information becomes invalid, and if the UE has uplink data to send, the UE autonomously starts GNSS measurements. If the UE cannot successfully acquire GNSS information within an X period of time, the UE may declare RLF 1030 and return to idle.

[0096] In another example solution, the UE may take action upon detecting an RLF. In one example, when the UE detects an RLF 1030, the UE autonomously starts GNSS measurements. In another example, when the UE detects an RLF 1030, if the RLF cause is due to an UL transmission failure (e.g., RACH failure, RLC failure), the UE starts GNSS measurements. For both examples, if the UE fails to perform a GNSS measurement or does not locate a GNSS position within an X period of time, the UE may declare a GNSS failure and move back to idle. Generally speaking, when a GNSS measurement / position fix failure occurs, the UE may return to idle or trigger a UE reestablishment procedure.

[0097] It should be understood that the methods and apparatus described above implement these processes by processors and circuit components of UEs and network devices to implement these methods and processes. Portions of the content described above can be implemented using logic circuits such as dedicated logic circuits or using microcontrollers or other forms of processing cores that execute program code instructions. Thus, the processes taught in the above discussion can be performed using program code such as machine-executable instructions, which cause a machine to execute these instructions to perform certain functions. In this context, a "machine" can be a machine that converts intermediate form (or "abstract") instructions into processor-specific instructions (e.g., an abstract execution environment such as a "virtual machine" (e.g., a Java virtual machine), an interpreter, a common language runtime, a high-level language virtual machine, etc.), and / or an electronic circuit provided on a semiconductor chip (e.g., a "logic circuit" implemented using transistors), which is designed to execute instructions, the processor being a general-purpose processor and / or a dedicated processor. The processes taught in the above discussion can also be performed by (as an alternative to or in combination with a machine) an electronic circuit that is designed to execute a process (or a portion thereof) without executing program code. For example, the described operations may be stored as instructions on a non-transitory computer-readable medium for execution by a computer.

[0098] The present invention also relates to an apparatus for performing the operations described herein. The apparatus may be specially constructed for the required purpose, or may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored on a computer-readable storage medium, such as, but not limited to, any type of disk, including floppy disks, optical disks, CD-ROMs and magneto-optical disks, read-only memory (ROM), RAM, EPROM, EEPROM, magnetic or optical cards, or any type of medium suitable for storing electronic instructions, and each coupled to a computer system bus.

[0099] A machine-readable medium includes any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer). For example, machine-readable media include read-only memory ("ROM"); random access memory ("RAM"); magnetic disk storage media; optical storage media; flash memory devices; and the like.

[0100] Articles of manufacture can be used to store program code. Articles of manufacture storing program code can be implemented as, but not limited to, one or more memories (e.g., one or more flash memories, random access memories (static, dynamic, or other)), optical disks, CD-ROMs, DVD ROMs, EPROMs, EEPROMs, magnetic or optical cards, or other types of machine-readable media suitable for storing electronic instructions. Program code can also be downloaded from a remote computer (e.g., a server) to a requesting computer (e.g., a client) via a data signal contained in a propagation medium (e.g., via a communication link (e.g., a network connection)).

[0101] The foregoing detailed description has been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the tools used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm, as used here and generally, refers to a self-consistent sequence of operations leading to a desired result. These operations are those requiring physical manipulation of physical quantities. Typically, but not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient, primarily for common sense, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

[0102] It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless otherwise specifically stated, it will be apparent from the foregoing discussion that discussions throughout this specification using terms such as "select," "determine," "receive," "form," "group," "aggregate," "generate," "remove," and the like will be understood to refer to actions and processes on a computer system or similar electronic computing device that manipulates data represented as physical (electronic) quantities in the computer system's registers and memories and converts it into other data similarly represented as physical quantities in the computer system's memories or registers or other such information storage, transmission, or display devices.

[0103] The process presented herein and display are not inherently relevant to any particular computer or other device. According to the teaching content of this paper, various general-purpose systems can be used together with program, or can prove that it is convenient to construct the more special-purpose device for carrying out described operation. According to the description below, the required structure for various these systems will be apparent. In addition, the present invention is not described with reference to any specific programming language. Should be understood that multiple programming languages ​​can be used for realizing the teaching content of the present invention as described herein.

[0104] The foregoing discussion describes only some exemplary embodiments of the present invention. Those skilled in the art will readily recognize from these discussions, drawings and claims that various modifications can be made without departing from the spirit and scope of the present invention.

Claims

1. A method for user equipment (UE) to interact with a network and a global navigation satellite system (GNSS), the method comprising: When initiating access to a new cell of the network, reporting the GNSS positioning duration or the GNSS valid duration; and The UE initiates the access via a radio resource control (RRC) operation or a medium access control (MAC) control element (CE), and the UE reports at least one GNSS positioning duration or a GNSS valid duration. 2 . The method according to claim 1 , wherein the GNSS positioning duration is reported to the network together with a remaining GNSS valid duration in the RRC operation. 3 . The method according to claim 1 , wherein the GNSS positioning duration is reported in a predefined message of the MAC CE. The method of claim 1 , wherein the GNSS positioning duration is reported via radio access UE capabilities. 5 . The method according to claim 1 , wherein in a case where the GNSS positioning duration changes, the method further comprises reporting an updated GNSS positioning duration to the network via the RRC operation or the MAC CE.

6. The method of claim 5, wherein the RRC operation comprises an uplink (UL) dedicated RRC message. The method of claim 1 , wherein an inhibit timer is utilized when reporting the GNSS position fix duration. The method of claim 7 , wherein the inhibit timer is used to limit a reporting frequency. 9 . The method of claim 1 , further comprising reporting the GNSS validity duration using a MAC CE. 10 . The method of claim 9 , wherein the GNSS validity duration is reported using the MAC CE after each GNSS measurement is completed.

11. The method according to claim 9, wherein When the GNSS validity duration is reported, a GNSS reporting periodicity timer is started, and when the GNSS reporting periodicity timer expires, the updated validity duration is reported using the MAC CE.

12. The method according to claim 9, wherein When the UE mobility state changes or when the UE speed changes, the updated validity duration is reported using the MAC CE.

13. The method according to claim 9, wherein: When the change in the remaining GNSS validity duration exceeds a threshold, the updated validity duration is reported using the MAC CE.

14. The method according to claim 9, wherein When the GNSS information is invalid for a period of time, the MAC CE is used to report the validity duration of the update.

15. A user equipment (UE) for interacting with a network and a global navigation satellite system (GNSS), the user equipment (UE) comprising: at least one antenna; at least one radio, wherein the at least one radio is configured to communicate with the network using the at least one antenna; and at least one processor coupled to the at least one radio, wherein the at least one processor is configured to perform operations comprising: When initiating access to a new cell of the network, reporting a GNSS positioning duration or a GNSS valid duration, wherein the access is initiated via a radio resource control (RRC) operation or a medium access control (MAC) control element (CE) to report the at least one GNSS positioning duration or the GNSS valid duration. 16 . The UE according to claim 15 , wherein the GNSS positioning duration is reported to the network together with a remaining GNSS valid duration in the RRC operation. 17 . The UE according to claim 15 , wherein the GNSS positioning duration is reported in a predefined message of the MAC CE.

18. The UE of claim 15, wherein the GNSS positioning duration is reported via radio access UE capabilities. 19 . The UE according to claim 15 , wherein in a case where the GNSS positioning duration changes, the method further comprises reporting the updated GNSS positioning duration to the network via the RRC operation or the MAC CE.

20. The UE of claim 19, wherein the RRC operation comprises an uplink (UL) dedicated RRC message.

21. The UE of claim 15, wherein when reporting the GNSS positioning duration, a prohibit timer is utilized to limit a reporting frequency.

22. The UE of claim 15, further comprising utilizing a MAC CE to report a GNSS validity duration. 23 . The UE according to claim 22 , wherein the GNSS validity duration is reported using the MAC CE after each GNSS measurement is completed.

24. The UE according to claim 22, wherein: When the GNSS validity duration is reported, a GNSS reporting periodicity timer is started, and when the GNSS reporting periodicity timer expires, the updated validity duration is reported using the MAC CE.

25. The UE according to claim 22, wherein When the UE mobility state changes or when the UE speed changes, the updated validity duration is reported using the MAC CE.

26. The UE according to claim 22, wherein: When the change in the remaining GNSS validity duration exceeds a threshold, the updated validity duration is reported using the MAC CE.

27. The UE according to claim 22, wherein: When the change in the remaining GNSS validity duration exceeds a threshold, the updated validity duration is reported using the MAC CE.

28. The UE according to claim 22, wherein: When the GNSS information is invalid for a period of time, the MAC CE is used to report the validity duration of the update.

29. A user equipment (UE) for interacting with a network and a global navigation satellite system (GNSS), the user equipment (UE) comprising: at least one antenna; at least one radio, wherein the at least one radio is configured to communicate with the network using the at least one antenna; and at least one processor coupled to the at least one radio, wherein the at least one processor is configured to perform operations comprising: When the UE GNSS is about to become obsolete, receiving a GNSS measurement command in a medium access control (MAC) control element (CE) from the network; as well as Determines whether to perform GNSS measurement.

30. The UE according to claim 29, wherein: Upon receiving the GNSS measurement command, the operations further include always performing the GNSS measurement.

31. The UE according to claim 29, wherein Upon receiving the GNSS measurement command, the operation further includes determining whether to perform the GNSS measurement based on whether valid GNSS information exists.

32. The UE according to claim 29, wherein Upon receiving the GNSS measurement command, the operations further include determining whether to perform the GNSS measurement based on: a selection determination made by the UE, or when a remaining GNSS validity condition set by the network is satisfied.

33. The UE according to claim 29, wherein When it is determined not to perform the GNSS measurement, the determination not to perform the GNSS measurement is sent to the network in a GNSS valid duration MAC CE.

34. The UE according to claim 29, wherein When it is determined that a GNSS measurement is to be performed, the GNSS measurement is performed in a specified measurement gap configuration, and when the GNSS measurement is completed, a GNSS valid duration MAC CE is transmitted to the network.

35. The UE according to claim 29, wherein The designated measurement gap configuration includes a gap duration provided to the UE by radio resource control (RRC) signaling and is enabled by the GNSS measurement command MAC CE.

36. The UE according to claim 35, wherein In case that the RRC signaling configures only one gap, the RRC configured gap for GNSS measurement is applied, and in case that the RRC configures more than one gap, a gap configuration index is enabled for the GNSS measurement.

37. The UE according to claim 29, wherein The specified measurement gap configuration includes a GNSS gap duration, an offset, and a periodicity provided to the UE in the GNSS measurement command MAC CE.

38. The UE according to claim 29, wherein A start time point of performing GNSS measurement after receiving the GNSS measurement command MAC CE associated with the gap pattern configured in the RRC occurs in a latest measurement opportunity configured according to the RRC.

39. The UE according to claim 29, wherein A start time point of performing GNSS measurement after receiving the GNSS measurement command MAC CE occurs at a predefined delay time after receiving the GNSS measurement command MAC CE.

40. The UE according to claim 29, wherein: A start time point of performing GNSS measurement after receiving the GNSS measurement command MAC CE is defined in the GNSS measurement command MAC CE.

41. A user equipment (UE) for interacting with a network and a global navigation satellite system (GNSS), the user equipment (UE) comprising: at least one antenna; at least one radio, wherein the at least one radio is configured to communicate with the network using the at least one antenna; and at least one processor coupled to the at least one radio, wherein the at least one processor is configured to perform operations comprising: Whether to perform GNSS measurement is determined based on the GNSS information becoming invalid.

42. The UE according to claim 41, wherein Based on the GNSS information becoming invalid, a timer is restarted, and when the timer expires, the GNSS measurement is performed.

43. The UE according to claim 41, wherein Based on the GNSS information becoming invalid, the GNSS measurement is automatically and autonomously performed.

44. The UE according to claim 41, wherein In the event that the GNSS measurements cannot be performed within a predetermined time period, a radio link failure (RLF) is declared and idle mode is restored.

45. The UE according to claim 41, wherein Based on the GNSS information becoming invalid and the UE having uplink data to send, the UE resumes idle mode.

46. ​​The UE according to claim 41, wherein Based on the GNSS information becoming invalid and the UE having uplink data to send, the GNSS measurements are automatically and autonomously performed.

47. The UE according to claim 41, wherein Based on the GNSS information becoming invalid, and the UE having uplink data to transmit, and the GNSS cannot be acquired within a predetermined amount of time, the UE declares RLF and resumes idle mode.

48. The UE according to claim 41, wherein Based on detecting the RLF, the GNSS measurements are automatically and autonomously performed.

49. The UE according to claim 48, wherein Based on detecting the RLF, the GNSS measurement is performed if the RLF is caused by a UL transmission failure.

50. The UE according to claim 49, wherein In case the GNSS measurement fails, the UE declares GNSS failure and returns to idle.

Images