System and method for power efficient positioning of mobile devices

Abstract

During a positioning session between a user equipment (UE) and a location server, the location server can send a request to a base station to suspend a radio resource control (RRC) connection with the UE. For example, the location server can send a request to the base station suggesting a connection suspension, or can provide an indication of an amount of time during which location-related messages between the UE and the location server are not expected. The base station can determine whether to suspend the connection with the UE, thereby placing the UE in an inactive state based on the provided information. The base station can also determine whether to suspend the connection based on data activity of the UE. While in the inactive state, the UE and the base station store a UE connection context, which can be used to quickly resume the connection.

Description

[0001] Priority claim under 35.119 of the United States Code

[0002] Pursuant to 35.119 of the United States Code, this application claims the interests and priority of U.S. Provisional Application No. 63 / 085,045, filed September 29, 2020, entitled “SYSTEM AND METHODS FOR POWER EFFICIENT POSITIONING,” and U.S. Non-Provisional Application No. 17 / 477,228, filed September 16, 2021, entitled “SYSTEM AND METHODS FOR POWER EFFICIENT POSITIONING OF A MOBILE DEVICE,” both of which have been assigned to their assigns and are incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure relates generally to communications, and more specifically to technologies for supporting location services for user equipment (UE). Background Technology

[0004] Wireless communication systems have evolved through multiple generations, including first-generation analog wireless telephony (1G), second-generation (2G) digital wireless telephony (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data and internet-enabled wireless services, and fourth-generation (4G) services (e.g., LTE or WiMax). The fifth-generation (5G) New Radio (NR) standard demands even higher data transmission speeds, a greater number of connections, and better coverage, among other improvements. According to the Next Generation Mobile Networks Alliance, 5G NR is designed to provide tens of megabits per second of data per second for each of tens of thousands of users, with 1 gigabit per second provided to dozens of employees on an office floor.

[0005] For some applications, obtaining the location of a mobile device via wireless communication systems can be useful or essential in the absence of Global Navigation Satellite Systems (GNSS) support (such as GPS, GLONASS, or Galileo). For example, this can be applied when applications such as navigation assistance, public safety support, or the management of moving objects in factories or warehouses require tracking mobile devices indoors or in dense urban canyons. In such cases, a reliable and rapid GNSS-free method for locating the mobile device can be valuable. Power efficiency during the location service is also desirable. Summary of the Invention

[0006] During a location session between a user equipment (UE) and a location server, the location server may send a request to the base station to suspend the radio resource control (RRC) connection with the UE. For example, the location server may send a request to the base station suggesting a connection suspension, or it may provide an indication of a duration during which no location-related messages between the UE and the location server are expected. The base station may determine whether to suspend the connection with the UE, thereby placing the UE in an inactive state based on the provided information. The base station may also determine whether to suspend the connection based on the UE's data activity. Placing the UE in an inactive state during a location session provides power savings when messaging is not required. In the inactive state, the UE and the base station store the UE connection context, which can be used to quickly and efficiently restore the connection, and this also provides power savings compared to when the location session requires releasing and establishing a new connection. In some implementations, the base station may release the connection with the UE, for example, if the UE is in a high mobility state, which can be indicated in a request to the base station.

[0007] In one implementation, a method performed by a user equipment (UE) to support location services for the UE includes: sending a message to a base station to establish a radio resource control (RRC) connection with the base station; receiving a message for a location session from a location server; receiving a connection suspension message from the base station to place the UE into an inactive state, wherein the connection suspension message is initiated by the location server; performing location measurements to obtain location information while in an inactive state; and sending location information to the location server while in a connected state.

[0008] In one implementation, a user equipment (UE) configured to support location services for a UE includes: a radio transceiver configured to wirelessly communicate with entities in a wireless network; at least one memory; and at least one processor coupled to the radio transceiver and the memory, wherein the at least one processor is configured to: send messages to a base station via the radio transceiver to establish a radio resource control (RRC) connection with the base station; receive messages for a location session from a location server; receive a connection suspension message from the base station to place the UE in an inactive state, wherein the connection suspension message is initiated by the location server; perform location measurements to obtain location information when in an inactive state; and send location information to the location server when in a connected state.

[0009] In one implementation, a user equipment (UE) configured to support location services for a UE includes: components for sending messages to a base station to establish a radio resource control (RRC) connection with the base station; components for receiving messages for a location session from a location server; components for receiving a connection suspension message from the base station to place the UE in an inactive state, wherein the connection suspension message is initiated by the location server; components for performing location measurements to obtain location information when in an inactive state; and components for sending location information to the location server when in a connected state.

[0010] In one implementation, a non-transitory storage medium includes program code stored thereon, the program code being operable to configure at least one processor in a user equipment (UE) to support location services for the UE, the program code including instructions for: sending a message to a base station to establish a radio resource control (RRC) connection with the base station; receiving a message from a location server for a location session; receiving a connection suspension message from the base station to place the UE in an inactive state, wherein the connection suspension message is initiated by the location server; performing location measurements to obtain location information while in an inactive state; and sending location information to the location server while in a connected state.

[0011] In one implementation, a method performed by a location server to support location services for a user equipment (UE) includes: sending a message to the UE for a location session; sending a message to a base station with which the UE has established a radio resource control (RRC) connection, the message requesting the UE to suspend its connection to place the UE in an inactive state, wherein the base station suspends the RRC connection between the base station and the UE in response to the message; and receiving location information from the UE after the UE performs location measurements to obtain location information and restores the RRC connection with the base station.

[0012] In one implementation, a location server configured to support location services for a user equipment (UE) includes: an external interface configured to communicate with one or more base stations and one or more UEs; at least one memory; and at least one processor coupled to the external interface and the memory, wherein the at least one processor is configured to: send a message for a location session to the UE via the external interface; send a message via the external interface to a base station with which the UE has established a radio resource control (RRC) connection, the message requesting the UE to suspend its connection to place the UE in an inactive state, wherein the base station suspends the RRC connection between the base station and the UE in response to the message; and receive location information from the UE via the external interface after the UE performs location measurements to obtain location information and restores its RRC connection with the base station.

[0013] In one implementation, a location server configured to support location services for a user equipment (UE) includes: components for sending messages to the UE for a location session; components for sending messages to a base station with which the UE has established a radio resource control (RRC) connection, the messages requesting the UE to suspend the connection to place the UE into an inactive state, wherein the base station suspends the RRC connection between the base station and the UE in response to the messages; and components for receiving location information from the UE after the UE performs location measurements to obtain location information and restores the RRC connection with the base station.

[0014] In one implementation, a non-transitory storage medium includes program code stored thereon, the program code being operable to configure at least one processor in a location server to support location services for a user equipment (UE), the program code including instructions for: sending a message to the UE for a location session; sending a message to a base station with which the UE has established a radio resource control (RRC) connection, the message requesting the UE to suspend its connection to place the UE in an inactive state, wherein the base station suspends the RRC connection between the base station and the UE in response to the message; and receiving location information from the UE after the UE performs location measurements to obtain location information and restores the RRC connection with the base station.

[0015] In one implementation, a method performed by a base station to support location services for a user equipment (UE) includes: sending a message to the UE to establish a radio resource control (RRC) connection with the UE; receiving a message from the location server while the UE is in a location session with the location server, the message requesting a suspension of the RRC connection between the base station and the UE; determining whether to release the RRC connection based at least in part on the message requesting the suspension of the connection from the location server; and sending a suspension of connection message to the UE to place the UE into an inactive state, wherein the UE performs location measurements to obtain location information while in an inactive state and sends the location information to the location server while in a connected state.

[0016] In one implementation, a base station configured to support location services for a user equipment (UE) includes: an external interface configured to communicate with a location server in a wireless network and one or more UEs; at least one memory; and at least one processor coupled to the external interface and the memory, wherein the at least one processor is configured to: send a message to the UE via the external interface to establish a radio resource control (RRC) connection with the UE; receive a message from the location server via the external interface when the UE is in a location session with the location server, the message requesting a connection suspension of the RRC connection between the base station and the UE; determine whether to release the RRC connection based at least in part on the request for connection suspension message from the location server; and send a connection suspension message to the UE via the external interface to place the UE into an inactive state, wherein the UE performs location measurements to obtain location information when in an inactive state and sends location information to the location server when in a connected state.

[0017] In one implementation, a base station for supporting location services for a user equipment (UE) includes: components for sending a message to the UE to establish a radio resource control (RRC) connection with the UE; components for receiving a message from a location server when the UE is in a location session with the location server, the message requesting a connection suspension of the RRC connection between the base station and the UE; components for determining whether to release the RRC connection based at least in part on the message requesting connection suspension from the location server; and components for sending a connection suspension message to the UE to place the UE in an inactive state, wherein the UE performs location measurements to obtain location information when in an inactive state and sends location information to the location server when in a connected state.

[0018] In one implementation, a non-transitory storage medium includes program code stored thereon, the program code being operable to configure at least one processor in a base station to support location services for a user equipment (UE), the program code including instructions for: sending a message to the UE to establish a radio resource control (RRC) connection with the UE; receiving a message from a location server while the UE is in a location session with a location server, the message requesting a suspension of the RRC connection between the base station and the UE; determining whether to release the RRC connection based at least in part on the message requesting a suspension of the connection from the location server; and sending a suspension of connection message to place the UE into an inactive state, wherein the UE performs location measurements to obtain location information while in an inactive state and sends location information to the location server while in a connected state.

[0019] Other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description. Attached Figure Description

[0020] The accompanying drawings are provided to help describe various aspects of this disclosure and are intended to illustrate these aspects only and not to limit them.

[0021] Figure 1 A high-level system architecture for a wireless communication system according to aspects of this disclosure is shown.

[0022] Figure 2 The Radio Resource Control (RRC) connection state machine and state transitions are shown.

[0023] Figure 3 The diagram illustrates the signaling flow of various messages sent between components of the communication system during a location session in which the location server requests a pause in the RRC connection.

[0024] Figure 4 The diagram illustrates the signaling flow of various messages sent between components of the communication system during a location session in which a user equipment (UE) requests an RRC connection suspension.

[0025] Figure 5 A schematic block diagram illustrating certain exemplary features of a UE configured to request a suspension of its RRC connection with a base station during a location session is shown.

[0026] Figure 6 A schematic block diagram illustrating certain exemplary features of a location server configured to request the suspension of the RRC connection between the UE and the base station during a location session is shown.

[0027] Figure 7 A schematic block diagram illustrating certain exemplary features of a base station configured to request a suspension of the RRC connection with the UE during a positioning session is shown.

[0028] Figure 8 A flowchart is shown of an exemplary method performed by the UE to support the UE's location services, wherein the RRC connection is suspended during the location session.

[0029] Figure 9 A flowchart is shown of an exemplary method for supporting location services for a UE, performed by a location server, wherein the RRC connection is suspended during a location session.

[0030] Figure 10 A flowchart is shown of an exemplary method performed by a base station to support location services for a UE, wherein the RRC connection is suspended during a location session.

[0031] Elements, stages, steps, and / or actions with the same reference markers in different diagrams may correspond to each other (e.g., they may be similar or identical). Furthermore, some elements in various diagrams are labeled with numeric prefixes followed by alphanumeric suffixes. Elements with the same numeric prefix but different suffixes may be different instances of the same type of element. In this document, a numeric prefix without any suffix will be used to represent any element with that numeric prefix. For example, Figure 1 Different examples of base stations, 110-1, 110-2, and 110-3, are shown. Reference to base station 110 refers to any one of base stations 110-1, 110-2, and 110-3. Detailed Implementation

[0032] Aspects of this disclosure are provided in the following description and in the related figures for the various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of this disclosure. Furthermore, well-known elements of this disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of this disclosure.

[0033] The terms “exemplary” and / or “example” are used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” and / or “example” is not necessarily to be construed as superior or advantageous over other aspects. Similarly, the term “aspects of this disclosure” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed.

[0034] Those skilled in the art will understand that any of a variety of different techniques and skills can be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the following description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof, depending in part on the specific application, in part on the required design, in part on the corresponding technology, etc.

[0035] Furthermore, many aspects are described with respect to the sequence of actions to be performed by elements of a computing device, for example. It will be understood that the various actions described herein can be performed by a particular circuit (e.g., an application-specific integrated circuit (ASIC)), program instructions executed by one or more processors, or a combination of both. Moreover, the sequence of actions described herein can be considered entirely embodied in any form of computer-readable storage medium storing a corresponding set of computer instructions that, when executed, will cause or instruct the associated processor of the device to perform the functionalities described herein. Therefore, various aspects of this disclosure can be embodied in many different forms, all of which are contemplated within the scope of the claimed subject matter. Additionally, for each aspect described herein, any corresponding form of such aspect can be described herein as, for example, "logic configured to perform the described actions."

[0036] As used herein, unless otherwise stated, the terms “User Equipment” (UE) and “Base Station” are not intended to be specific or otherwise limited to any particular Radio Access Technology (RAT). Generally, a UE can be any wireless communication device used by a user to communicate via a wireless communication network (e.g., mobile phone, router, tablet computer, laptop computer, consumer tracking device for tracking consumer items, packaging, assets, or entities such as individuals and pets, wearable devices (e.g., smartwatches, glasses, augmented reality (AR) / virtual reality (VR) headsets, etc.), vehicles (e.g., cars, motorcycles, bicycles, etc.), Internet of Things (IoT) devices, etc.). A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term “UE” can be interchangeably referred to as “Access Terminal” or “AT”, “Client Equipment”, “Wireless Equipment”, “Subscriber Equipment”, “Subscriber Terminal”, “Subscriber Station”, “User Terminal” or “UT”, “Mobile Terminal”, “Mobile Station”, “Mobile Equipment”, or variations thereof. Typically, a UE can communicate with the core network via the RAN, and through the core network, the UE can connect to external networks (such as the Internet) and other UEs. Of course, other mechanisms for the UE to connect to the core network and / or the Internet are also possible, such as via wired access networks, wireless local area network (WLAN) networks (e.g., based on IEEE 802.11, etc.).

[0037] A base station may operate under one of several RATs (Regional Access Points) communicating with the UE, depending on the network deployed within it, and may be alternatively referred to as an Access Point (AP), Network Node, NodeB, Evolved NodeB (eNB), New Radio (NR) NodeB (also known as gNB), etc. Additionally, in some systems, the base station may provide purely edge node signaling functions, while in others it may provide additional control and / or network management functions. The communication link through which the UE transmits signals to the base station is referred to as an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the base station transmits signals to the UE is referred to as a downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term Traffic Channel (TCH) may refer to either a UL / reverse or DL / forward traffic channel.

[0038] The term "base station" can refer to a single physical transmission point or multiple physical transmission points, which may or may not be co-located. For example, when the term "base station" refers to a single physical transmission point, the physical transmission point can be an antenna of the base station, corresponding to a cell of the base station. When the term "base station" refers to multiple co-located physical transmission points, the physical transmission points can be an antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). When the term "base station" refers to multiple non-co-located physical transmission points, the physical transmission points can be a distributed antenna system (DAS) (a spatially separated network of antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, a non-co-located physical transmission point can be a serving base station that receives measurement reports from the UE and neighboring base stations where the UE is measuring its reference RF signal.

[0039] To support UE positioning, two main categories of positioning solutions have been defined: control plane and user plane. For control plane (CP) positioning, signaling related to positioning and positioning support can be carried over the existing network (and UE) interface using existing protocols dedicated to signaling transmission. For user plane (UP) positioning, signaling related to positioning and positioning support can be carried as part of other data using protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP).

[0040] The 3rd Generation Partnership Project (3GPP) has defined control plane location solutions for UEs using radio access based on GSM (2G), UMTS (3G), LTE (4G), and New Radio (NR) for 5G. These solutions are defined in 3GPP Technical Specifications (TS) 23.271 and 23.273 (common parts), 43.059 (GSM access), 25.305 (UMTS access), 36.305 (LTE access), and 38.305 (NR access). The Open Mobility Alliance (OMA) has similarly defined an up-plane location solution called Secure User Plane Location (SUPL), which can be used to locate UEs accessing any of multiple radio interfaces supporting IP packet access, such as GPRS in the GSM case, GPRS in the UMTS case, or IP access in the LTE or NR case.

[0041] Both CP and UP location solutions can employ a Location Server (LS) to support positioning. The LS can be part of or accessible from the UE's serving or home network, or simply accessible via the Internet or a local intranet. If positioning of the UE is required, the LS can initiate a session with the UE (e.g., a location session or a SUPL session) and coordinate the UE's location measurements and determine the UE's estimated location. During a location session, the location server can request positioning capabilities from the UE (or the UE can provide them without request), can provide auxiliary data to the UE (e.g., if requested by the UE or without request), and can request location estimates or measurements from the UE (e.g., for GNSS, TDOA, AOD, multi-RTT, and / or enhanced cell ID (ECID) positioning methods). The UE can use the auxiliary data to acquire and measure GNSS and / or PRS signals (e.g., by providing expected characteristics of these signals, such as frequency, expected time of arrival, signal decoding, and signal Doppler).

[0042] In UE-based operating modes, the UE may also or alternatively use auxiliary data to help determine the location estimate from the obtained location measurement (e.g., if the auxiliary data provides satellite ephemeris data in the case of GNSS positioning or base station location and other base station characteristics (such as PRS timing) in the case of terrestrial positioning using, for example, TDOA, AOD, multi-RTT, etc).

[0043] In UE-assisted operation mode, the UE can return location measurements to the LS, which can determine the estimated location of the UE based on these measurements and possibly also on other known or configured data (e.g., satellite ephemeris data for GNSS location or base station characteristics (including base station location and possible PRS timing) in the case of terrestrial positioning such as TDOA, AOD, multi-RTT, etc.).

[0044] In another standalone operating mode, the UE can perform position-related measurements without any positioning assistance data from the LS, and can also calculate position or position changes without any positioning assistance data from the LS. Positioning methods that can be used in standalone mode include GPS and GNSS (e.g., if the UE obtains satellite orbit data from data broadcast by the GPS and GNSS satellites themselves) and sensors.

[0045] In the case of a 3GPP CP location, the LS can be an Enhanced Serving Mobile Location Center (E-SMLC) for LTE access, a Standalone SMLC (SAS) for UMTS access, a Serving Mobile Location Center (SMLC) for GSM access, or a Location Management Function (LMF) for 5G NR access. In the case of an OMA SUPL location, the LS can be a SUPL Location Platform (SLP), which can act as any of the following: (i) a Home SLP (H-SLP), if in or associated with the UE's home network, or if a permanent subscription for location services is provided to the UE; (ii) a Discovered SLP (D-SLP), if in or associated with another (non-home) network, or if not associated with any network; (iii) an Emergency SLP (E-SLP), if it supports the location for emergency calls initiated by the UE; or (iv) a Visited SLP (V-SLP), if in or associated with the UE's serving network or current local area.

[0046] During a location session, the LS and UE can exchange messages defined according to a location protocol to coordinate the determination of estimated location. Possible location protocols may include, for example, the LTE Location Protocol (LPP) defined by 3GPP in 3GPP TS 37.355 and the LPP Extensions (LPPe) protocol defined by OMA in OMA TS OMA-TS-LPPe-V1_0, OMA-TS-LPPe-V1_1, and OMA-TS-LPPe-V2_0. The LPP and LPPe protocols can be used in combination, where an LPP message contains an embedded LPPe message. This combination of LPP and LPPe protocols can be referred to as LPP / LPPe. LPP and LPP / LPPe can be used to help support 3GPP control plane solutions for LTE or NR access, in which case LPP or LPP / LPPe messages are exchanged between the UE and the E-SMLC or between the UE and the LMF. LPP or LPPe messages can be exchanged between the UE and the E-SMLC via the Serving Mobility Management Entity (MME) for the UE and the serving eNodeB. LPP or LPP / LPPe messages can also be exchanged between the UE and the LMF via the Serving Access and Mobility Management Function (AMF) for the UE and the Serving NR Node B (gNB). LPP and LPP / LPPe can also be used to help support OMA SUPL solutions for many types of radio access (such as LTE, NR, and WiFi) that support IP messaging, where LPP or LPP / LPPe messages are exchanged between the SUPL Enabled Terminal (SET) (which is the term for a UE with SUPL) and the SLP, and can be transmitted within SUPL messages (such as SUPL POS or SUPL POSINIT messages).

[0047] The LS and the base station (e.g., an eNodeB for LTE access or a gNodeB for NR access) can exchange messages enabling the LS to: (i) obtain location measurements for a specific UE from the base station, or (ii) obtain location information not related to a specific UE from the base station, such as the location coordinates of the base station's antennas, the cell supported by the base station (e.g., cell identifier), cell timing for the base station, and / or parameters for signals transmitted by the base station (such as PRS signals). In the case of LTE access, the LPP A (LPPa) protocol can be used to transmit such messages between the base station as an eNodeB and the LS as an E-SMLC. In the case of NR access, the New Radio Positioning Protocol A (NRPPa) protocol can be used to transmit such messages between the base station as a gNodeB and the LS as an LMF.

[0048] During a location session, the UE may infrequently send location measurements to the location server. For example, the location server may not request frequent location measurements; periodic triggers for location measurements may have long periods. In another example, there may be a relatively long time interval between receiving auxiliary data or requesting a location measurement and sending location information. The base station (e.g., gNB) may not know the timing of the location measurement instructions from the location server to the UE and / or when the UE prepares or sends the location measurement, because location-related messages between the location server and the UE can be transparently transmitted through the base station as LPP messages.

[0049] The connection between the UE and the base station (e.g., an RRC connection) can be released solely by the base station. Without information related to the timing of the location measurement, the base station may not release the connection with the UE, and therefore the UE can maintain a connected state with the base station throughout the entire location measurement session, potentially resulting in additional resource and power consumption by the UE. Furthermore, even if the base station releases the connection with the UE, a new connection needs to be initiated if the location measurement is sent immediately after the connection is released, which will consume additional power and time.

[0050] For example, for the E911 or other location tracking applications, GNSS positioning may take more than 15 seconds. Maintaining a connection with the base station for such an extended period can result in additional power consumption.

[0051] In one implementation, as discussed herein, the base station may receive a message from the UE or a location server to suspend the RRC connection between the UE and the base station. For example, in some implementations, the location server or the UE may send a request to the base station suggesting the suspension of the RRC connection or providing an indication of a duration during which no location-related messages between the UE and the location server are expected to be transmitted. The base station may determine whether to suspend the connection with the UE based on the request or the information provided in the request. The base station may also determine whether to suspend the RRC connection based on the UE's data activity. For example, the base station may determine to suspend the RRC connection with the UE and may send an RRC release message (also referred to herein as a suspension message) to the UE, indicating that the RRC connection is suspended to place the UE in an RRC inactive state (also referred to herein as inactive mode or inactive state). When in inactive mode, the UE and the base station store the UE connection context, allowing for rapid connection recovery based on the stored UE connection context with minimal power consumption compared to regular connection releases and re-establishments. In some implementations, the UE or the location server may determine that the UE is moving and that a RAN update (e.g., handover to another base station) may occur before the expected next location message. The location server or UE may include indications of UE movement in the request and may request the release of the UE to place it in an idle state during the location session. The base station may determine whether to release the RRC connection with the UE based on the request or the information provided in the request, as well as additional information such as the UE's data activity.

[0052] Figure 1 An architecture based on a non-roaming 5G NR network is shown to support UE positioning via a pause of RRC connection requested per UE or location server as discussed herein. Figure 1 A communication system 100 including UE 102 is shown. UE 102 is sometimes referred to herein as the “target UE” because UE 102 may be the target of a location request. Figure 1Components of a fifth-generation (5G) network, including a next-generation radio access network (NG-RAN) 112, are also shown. NG-RAN 112 includes base stations (BS) sometimes referred to as new radio (NR) NodeBs, or gNBs 110-1, 110-2, 110-3, and a next-generation evolved NodeB (ng-eNB) 114, as well as a 5G core network (5GCN) 150 that communicates with external clients 130. The architecture of gNB 110 can be divided into functional parts, such as one or more gNB central units (gNB-CU), one or more gNB distributed units (gNB-DU), and one or more gNB remote units (gNB-RU), any of which can be physically co-located with or physically separated from the other parts of gNB 110. 5G networks can also be referred to as New Radio (NR) networks; NG-RAN 112 can be referred to as NR RAN or 5G RAN; and 5GC 150 can be referred to as Next Generation (NG) Core Network (NGC). Communication system 100 can also use information from spacecraft (SV) 190 for Global Navigation Satellite Systems (GNSS) (such as GPS, GLONASS, Galileo, or BeiDou) or some other local or regional satellite positioning systems (SPS), such as IRNSS, EGNOS, or WAAS. Additional components of communication system 100 are described below. Communication system 100 may include additional or alternative components.

[0053] Figure 1 The serving gNB 110-1 and neighboring gNBs 110-2, 110-3 and ng-eNB 114 for target UE 102 are shown. The neighboring gNB can be any gNB capable of receiving and measuring uplink (UL) signals transmitted by target UE 102 and / or capable of transmitting downlink (DL) reference signals (RS) (e.g., location reference signals (PRS)) that can be received and measured by target UE 102.

[0054] The entity in NG-RAN 112 that transmits the DL reference signal (RS) to be measured by the target UE 102 for a location-specific session is generally referred to as the “transmission point (TP)” and may include one or more of the serving gNB 110-1 and neighboring gNBs 110-2, 110-3 and ng-eNB 114.

[0055] The entity in NG-RAN 112 that receives and measures UL signals (e.g., RS) transmitted by target UE 102 for a location-specific session is generally referred to as a “receiving point (RP)” and may include one or more of the serving gNB 110-1 and neighboring gNBs 110-2, 110-3 and ng-eNB 114.

[0056] It should be noted that Figure 1 Only a generalized description of the various components is provided; any or all of them may be used appropriately, and each may be copied or omitted if necessary. Specifically, although only one UE 102 is shown, it will be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the communication system 100. Similarly, the communication system 100 may include more or fewer SV 190s, gNB 110-1, gNB 110-2, external clients 130, and / or other components. The connections shown linking the various components in the communication system 100 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. Furthermore, components may be rearranged, combined, separated, replaced, and / or omitted depending on the desired functionality.

[0057] although Figure 1 A 5G-based network is illustrated, but similar network implementations and configurations can be used for other communication technologies such as 3G, Long Term Evolution (LTE) (also known as 4G), and IEEE 802.11 WiFi. For example, when using a Wireless Local Area Network (WLAN) (e.g., an IEEE 802.11 radio interface), UE 102 can communicate with the Access Network (AN) instead of the NG-RAN, and accordingly, component 112 is sometimes referred to herein as AN or RAN, indicated by the terms "RAN", "(R)AN", or "(R)AN 112". In the case of an AN (e.g., an IEEE 802.11 AN), the AN can connect to a non-3GPP Interoperability Function (N3IWF) (e.g., in 5GCN 150)). Figure 1 (not shown in the image), where N3IWF is connected to AMF 154.

[0058] As used herein, the target UE 102 can be any electronic device and may be referred to as a device, mobile device, wireless device, mobile terminal, terminal, mobile station (MS), Secure User Plane Location (SUPL) enabled terminal (SET), or some other name. The target UE 102 can be a standalone device or can be embedded in another device to be monitored or tracked (e.g., a factory tool). Furthermore, UE 102 can correspond to a smartwatch, digital glasses, fitness monitor, smart car, smart appliance, mobile phone, smartphone, laptop, tablet, PDA, consumer tracking device for tracking consumer items, packages, assets, or entities (such as individuals and pets), control device, or some other portable or mobile device. UE 102 may include a single entity or may include multiple entities such as in a personal area network (PAN), such as a PAN where users can employ audio, video, and / or data I / O devices and / or body sensors, as well as separate wired or wireless modems. Typically, although not mandatory, UE 102 may use one or more Radio Access Technologies (RATs) to support wireless communication, such as GSM, Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), LTE, High Rate Packet Data (HRPD), IEEE 802.11 WiFi (also known as Wi-Fi). (BT), Global Microwave Access Interoperability (WiMAX), 5G New Radio (NR) (e.g., using NG-RAN 112 and 5GCN 150), etc. UE 102 can also support wireless communication using a wireless local area network (WLAN), which can be connected to other networks (e.g., the Internet) using, for example, digital subscriber line (DSL) or packet cable. The use of one or more of these RATs can allow UE 102 to communicate with external client 130 (e.g., via...). Figure 1 The 5GCN 150 components not shown may be used, or may be used via a gateway mobile location center (GMLC 160) and / or allow an external client 130 to receive location information about UE 102 (e.g., via GMLC 160).

[0059] UE 102 can enter a connected state with a wireless communication network that may include NG-RAN 112. In one example, UE 102 can communicate with the cellular communication network by transmitting or receiving radio signals from a cellular transceiver (such as gNB 110-1) in NG-RAN 112. The transceiver provides user and control plane protocol terminals to UE 102 and may be referred to as a base station, base transceiver, radio base station, radio transceiver, radio network controller, transceiver function, base station subsystem (BSS), extended service set (ESS), or some other suitable terminology.

[0060] In a particular implementation, UE 102 may have circuitry and processing resources capable of acquiring location-related measurements. The location-related measurements acquired by UE 102 may include measurements of signals received from a satellite spacecraft (SV) 190 belonging to a Satellite Positioning System (SPS) or Global Navigation Satellite System (GNSS) (such as GPS, GLONASS, Galileo, or BeiDou), and / or may include measurements of signals received from a ground transmitter (e.g., gNB 110) fixed at a known location. UE 102 or UE 102 may send the measured gNB 110-1 to it, and then UE 102 may use any of several positioning methods, such as GNSS, Auxiliary GNSS (A-GNSS), Advanced Forward Link Trilateral Measurement (AFLT), Angle of Departure (AoD), Time Difference of Arrival (TDOA), Round Trip Time (RTT), Multiple RTT, WLAN (also known as WiFi) positioning, or Enhanced Cell ID (ECID), or combinations thereof, to obtain a location estimate for UE 102 based on these location-related measurements. In some of these technologies (e.g., A-GNSS, AFLT, AOD, RTT, and TDOA), pseudorange or timing difference can be measured at the UE 102 at least in part based on pilot signals, positioning reference signals (PRS), or other positioning-related signals transmitted by a transmitter or satellite and received at the UE 102, relative to three or more ground transmitters (e.g., gNBs) fixed at known locations, or relative to four or more SV 190s with accurate known orbit data, or relative to a combination thereof.

[0061] Figure 1The location server in the UE 102 may correspond to, for example, a Location Management Function (LMF) 152 or a Secure User Plane Positioning (SUPL) Location Platform (SLP) 162, and may be able to provide the UE 102 with positioning assistance data, including, for example, information about the signal to be measured (e.g., expected signal timing, signal decoding, signal frequency, signal Doppler), the location and identification of the ground transmitter (e.g., gNB), and / or signal, timing, and orbit information for GNSS SV, to facilitate positioning technologies such as A-GNSS, AFLT, AoD, TDOA, RTT, and ECID. This facilitation may include improving the signal acquisition and measurement accuracy of the UE 102, and in some cases, enabling the UE 102 to calculate its estimated location based on location measurements. For example, a location server (e.g., LMF 152 or SLP 162) may include ephemeris, also known as base station ephemeris (BSA), which indicates the location and identification of cellular transceivers and / or local transceivers in a specific area or such area as a specific location, and may provide information describing signals transmitted by a cellular base station or AP (e.g., gNB), such as transmission power and signal timing. UE 102 may obtain signal strength measurements (e.g., Received Signal Strength Indication (RSSI)) for signals received from cellular transceivers and / or local transceivers, and / or may obtain signal-to-noise ratio (S / N), reference signal received power (RSRP), reference signal received quality (RSRQ), time of arrival (TOA), angle of arrival (AoA), angle of departure (AOD), receive time-transmission time difference (Rx-Tx), or round-trip time of propagation (RTT) between UE 102 and a cellular transceiver (e.g., gNB) or local transceiver (e.g., WiFi access point (AP)). UE 102 can use these measurements, along with auxiliary data (e.g., ground almanac data or GNSS satellite data such as GNSS ephemeris and / or GNSS ephemeris table information) received from a location server (e.g., LMF 152 or SLP 162) or broadcast by base stations in NG-RAN 112 (e.g., gNB 110-1, 110-2), to determine the location of UE 102.

[0062] In some implementations, network entities are used to assist in the localization of the target UE 102. For example, entities in the network (such as gNB 110-1, 110-2) can measure the UL signal transmitted by the UE 102. The UL signal may include or contain UL reference signals, such as a UL Position Reference Signal (PRS) or a UL Detection Reference Signal (SRS). The entity that obtains the location measurement (e.g., gNB 110-1, 110-2) can then transmit the location measurement to the UE 102 or LMF 152, which can use the measurement to determine the real-time differential of multiple transceiver pairs. Examples of location measurements that can use UL signals include RSSI, RSRP, RSRQ, TOA, Rx-Tx, AOA, and RTT.

[0063] The estimation of the location of UE 102 may be referred to as location, location estimate, location fixed, fixed, position, or location fixed, and it may be geographical, thus providing location coordinates (e.g., latitude and longitude) for UE 102, which may or may not include an altitude component (e.g., altitude above ground or depth below ground, number of floors above ground or number of floors below ground). Alternatively, the location of UE 102 may be represented as a city location (e.g., as a postal address or designation of a point or small area (such as a specific room or floor) within a building). The location of UE 102 may also be represented as an area or volume in which UE 102 is expected to be located with a certain probability or confidence level (e.g., 67% or 95%, etc.) (defined geographically or in city terms). The location of UE 102 can also be a relative location, including, for example, distance and direction defined relative to an origin at a known location, or relative to X, Y (and Z) coordinates, which can be defined geographically, in urban terms, or as a point, area, or volume indicated on a reference map, floor plan, or building plan. The location can be represented as an absolute position estimate of the UE, such as location coordinates or an address, or as a relative position estimate of the UE, such as distance and direction from a previous position estimate or a known absolute location. The UE's location can include the UE's linear velocity, angular velocity, linear acceleration, angular acceleration, angular orientation, such as the UE's orientation relative to a fixed global or local coordinate system, an identifier of a triggering event used to locate the UE, or some combination thereof. For example, a triggering event can include a region event, a motion event, or a speed event. For example, a region event can be the UE moving into a defined region, moving out of the region, and / or remaining in the region. For example, a motion event can include the UE moving a threshold straight-line distance or moving a threshold distance along a UE trajectory. For example, a speed event can include the UE reaching a minimum or maximum speed, a speed threshold increase and / or decrease, and / or a direction threshold change. In the description contained herein, the use of the term location may include any of these variations unless otherwise indicated. When calculating the location of a UE, local x, y, and possibly z coordinates are typically solved, and then the local coordinates are converted to absolute coordinates (e.g., latitude, longitude, and altitude above or below mean sea level) as needed.

[0064] like Figure 1 As shown, gNB pairs in NG-RAN 112 can be connected to each other, for example, as Figure 1The access to the 5G network is provided to UE 102 directly or indirectly via other gNBs 110-1 and 110-2, as shown. gNBs 110-1 and 110-2 may use 5G (e.g., NR) to provide wireless communication access to the 5GCN150 on behalf of UE 102. Figure 1 In this example, assuming that the serving gNB for UE 102 is gNB 110-1, if UE 102 moves to another location, other gNBs (e.g., gNB 110-2, 110-3, or ng-eNB 114) can also act as serving gNBs or as secondary gNBs to provide additional throughput and bandwidth to UE 102. Figure 1 Some gNBs (e.g., gNB 110-2, 110-3, or ng-eNB 114) can be configured to act as location-only beacons, which can send signals (e.g., directional PRS) to assist the UE 102 in positioning, but may not receive signals from the UE 102 or from other UEs.

[0065] As noted, although Figure 1 A node configured to communicate according to a 5G communication protocol is shown, but nodes configured to communicate according to other communication protocols (such as, for example, LTE) may also be used. Such nodes configured to communicate using different protocols can be controlled at least partially by the 5GCN 150. Therefore, the NG-RAN 112 may include any combination of gNBs, LTE-enabled evolved Node Bs (eNBs), or other types of base stations or access points. As an example, the NG-RAN 112 may include one or more ng-eNBs 114 that provide LTE radio access to the UE 102 and can connect to entities in the 5GCN 150, such as AMF 154.

[0066] gNB 110-1, 110-2, 110-3 and ng-eNB 114 can communicate with Access and Mobility Management Function (AMF) 154, which, for location functionality, can communicate with Location Management Function (LMF) 152. AMF 154 can support UE 102's mobility, including cell changes and handovers, and can participate in signaling connections supporting UE 102, and may assist in establishing and releasing Protocol Data Unit (PDU) sessions for UE 102 supported by UPF 158. Other functions of AMF 154 may include: terminating the control plane (CP) interface from NG-RAN 112; terminating non-access stratum (NAS) signaling connections from UEs (such as UE 102), NAS encryption and integrity protection; registration management; connection management; reachability management; mobility management; access authentication and authorization.

[0067] When UE 102 accesses NG-RAN 112, gNB 110-1 can support the location of UE 102. gNB 110-1 can also process location service requests for UE 102 received, for example, directly or indirectly from GMLC 160. In some embodiments, the node / system implementing gNB 110-1 may additionally or alternatively implement other types of location support modules, such as an Enhanced Serving Mobility Location Center (E-SMLC) or a Secure User Plane Location (SUPL) Positioning Platform (SLP) 162. It should be noted that in some embodiments, at least a portion of the location functionality (including the derivation of UE 102's location) can be performed at UE 102 (e.g., signal measurement using signals transmitted by the radio node and auxiliary data provided to UE 102).

[0068] GMLC 160 can support location requests for UE 102 received from external client 130 and can forward such requests to the serving AMF 154 for UE 102. AMF 154 can then forward the location request to gNB 110-1 or LMF 152, which can obtain one or more location estimates for UE 102 (e.g., based on the request from external client 130) and can return the location estimates to AMF 154, which can then return the location estimates to external client 130 via GMLC 160. GMLC 160 can contain subscription information for external client 130 and can authenticate and authorize location requests for UE 102 from external client 130. GMLC 160 can also initiate a location session for UE 102 by sending a location request for UE 102 to AMF154, and can include the identifier of UE 102 and the type of location requested (e.g., current location, or a sequence of periodic or triggered locations) in the location request.

[0069] As shown, the Unified Data Management (UDM) 161 can be connected to the GMLC 160. The UDM 161 is similar to a Home Subscriber Server (HSS) for LTE access, and can be combined with the HSS when necessary. The UDM 161 is a central database containing user-related and subscription-related information for the UE 102, and can perform the following functions: UE authentication, UE identification, access authorization, registration and mobility management, subscription management, and short message service management.

[0070] like Figure 1 As further shown, external client 130 can connect to core network 150 via GMLC 160 and / or SLP 162. External client 130 can optionally connect to core network 150 and / or connect to SLP 164 outside 5GCN 150 via Internet 175. External client 130 can be a server, web server, or user equipment (such as a personal computer, UE, etc.).

[0071] Network Open Function (NEF) 163 can connect to GMLC 160 and AMF 154. In some implementations, NEF 163 can be connected to communicate directly with external client 130 or Application Function (AF) 132. NEF 163 can support the secure exposure of capabilities and events related to 5GCN 150 and UE 102 to external client 130 or AF 132, and can allow information to be securely provided from external client 130 or AF 132 to 5GCN 150. For example, NEF 163 can be used to obtain the current or last known location of UE 102, an indication of a change in the location of UE 102, or an indication of when UE 102 becomes available (or reachable). External client 130 or AF 132 can access NEF 163 to obtain the location information of UE 102.

[0072] LMF 152 and gNB 110-1 can communicate using the New Radio Location Protocol A (NRPPa). NRPPa is defined in 3GPP TS 38.455, where NRPPa messages are transmitted between gNB 110-1 and LMF 152. Furthermore, LMF 152 and UE 102 can communicate using the LTE Location Protocol (LPP) defined in 3GPP TS 37.355, where LPP messages are transmitted between UE 102 and LMF 152 via serving AMF 154 and serving gNB 110-1 for UE 102. The LPP protocol can be used to support UE 102's location using UE-assisted and / or UE-based location methods such as assisted GNSS (A-GNSS), Real-time Kinematics (RTK), Wireless Local Area Network (WLAN), Time Difference of Arrival (TDOA), Round-Trip Time (RTT), and / or Enhanced Cell Identification (ECID)). The NRPPa protocol can be used to support the positioning of UE 102 using network-based positioning methods (such as ECID) (when used with measurements obtained or received from gNB 110-1, 110-2, 110-3 or ng-eNB 114), and / or can be used by LMF 152 to obtain location-related information from gNB, such as defining parameters of the Positioning Reference Signal (PRS) transmitted from gNB for supporting TDOA.

[0073] GNB 110-1, 110-2, 110-3, or ng-eNB 114 can communicate with AMF 154 using, for example, the Next Generation Application Protocol (NGAP) as defined in 3GPP Technical Specification (TS) 38.413. NGAP enables AMF 154 to request the location of target UE 102 from the serving gNB 110-1 for target UE 102, and enables gNB 110-1 to return the location of UE 102 to AMF 154.

[0074] GNBs 110-1, 110-2, 110-3, or ng-eNB 114 can communicate with each other using, for example, the Xn Application Protocol (XnAP) as defined in 3GPP TS 38.423. XnAP allows one gNB 110 to request and return UL location measurements from another gNB 110 for the target UE 102. XnAP also enables a gNB 110 to request another gNB 110 to send a downlink (DL) RS or PRS, allowing the target UE 102 to obtain DL location measurements from the sent DL RS or PRS.

[0075] A gNB (e.g., gNB 110-1) can communicate with a target UE 102 using, for example, a Radio Resource Control (RRC) protocol defined in 3GPP TS 38.331. The RRC can allow a gNB (e.g., gNB 110-1) to request location measurements of a DL RS or DL ​​PRS transmitted by gNB 110-1 and / or other gNBs 110-2, 110-3, or ng eNB 114 from the target UE 102, and return some or all of the location measurements. The RRC can also enable a gNB (e.g., gNB 110-1) to request the target UE 102 to transmit a UL RS or PRS so that gNB 1101 or other gNBs 110-2, 110-3, or ng eNB 114 can obtain the UL location measurements of the transmitted UL RS or PRS.

[0076] Using a UE-assisted positioning method, UE 102 can obtain location measurements (e.g., measurements of RSSI, Rx-Tx, RTT, multiple RTT, AOA, RSTD, RSRP, and / or RSRQ for gNB 110-1, 110-2, 110-3 or ng-eNB 114 or WLAN AP, or measurements of GNSS pseudorange, code phase, and / or carrier phase for SV 190), and can send the measurements to an entity performing location server functions (e.g., LMF 152 or SLP 162) for calculating the location estimate of UE 102. Using a UE-based positioning method, UE 102 can obtain location measurements (e.g., which may be the same as or similar to the location measurements used in a UE-assisted positioning method), and can calculate the location of UE 102 (e.g., using auxiliary data received from a location server such as LMF 152 or SLP 162). Using a network-based positioning method, one or more base stations (e.g., gNB 110-1 to 110-2) or APs can obtain location measurements (e.g., measurements of RSSI, RTT, AOD, RSRP, RSRQ, Rx-Tx, or TOA for signals transmitted by UE 102), and / or can receive measurements obtained by UE 102, and can send these measurements to a location server (e.g., LMF 152) for calculating the location estimate of UE 102.

[0077] Information provided by gNB 110-2, 110-3, or ng eNB 114 to gNB 110-1 using XnAP may include timing and configuration information for PRS transmission, as well as the location coordinates of gNB 110-2, 110-3, or ng eNB 114. gNB 110-1 may then provide some or all of this information to UE 102 as auxiliary data in an RRC message. In some implementations, the RRC message sent from gNB 110-1 to UE 102 may include an embedded LPP message.

[0078] RRC messages sent from gNB 110-1 to UE 102 can instruct UE 102 to do anything among various desired functions. For example, an RRC message may contain instructions for UE 102 to acquire measurements of GNSS (or A-GNSS), WLAN, and / or OTDOA (or some other positioning method) or to transmit uplink (UL) signals (such as positioning reference signals, probe reference signals, or both). In the case of OTDOA, the RRC message may instruct UE 102 to acquire one or more measurements (e.g., RSTD measurements) of PRS signals transmitted within a specific cell supported by a specific gNB. UE 102 can use these measurements to determine its location, for example, using OTDOA.

[0079] The gNB in ​​NG-RAN 112 can also broadcast positioning assistance data to UEs such as UE 102.

[0080] As shown, Session Management Function (SMF) 156 connects AMF 154 and UPF 158. SMF 156 can manage the establishment, modification, and release of PDU sessions for UE 102, perform IP address allocation and management for UE 102, act as a Dynamic Host Configuration Protocol (DHCP) server for UE 102, and select and control UPF 158 on behalf of UE 102.

[0081] User plane function (UPF) 158 supports voice and data bearers for UE 102 and enables UE 102 to access other networks, such as the Internet 175, for voice and data. UPF 158 functions may include: external PDU session points interconnected to data networks, packet (e.g., Internet Protocol (IP)) routing and forwarding, user plane portions of packet inspection and policy rule enforcement, user plane Quality of Service (QoS) processing, downlink packet buffering, and downlink data notification triggering. UPF 158 can connect to SLP 162 to enable location support for UE 102 using the SUPL location solution defined by the Open Mobility Alliance (OMA). SLP 162 can also connect to or be accessible from external client 130.

[0082] It should be understood that, despite Figure 1 The network architecture for non-roaming UEs is shown, but with appropriate well-known modifications, a corresponding network architecture can be provided for roaming UEs.

[0083] During a location session, in certain situations, such as during emergency calls or mission-critical scenarios, it is expected that the location server (e.g., LMF 152 or SLP 162) will receive a response to location-related requests from UE 102 as quickly as possible. One source of latency found in conventional location processes is the delay in UE 102 obtaining UL clearance from the base station, which is necessary to send the requested location information to location servers 152 / 162. For example, if UE 102 does not yet have UL clearance from the base station, UE 102 will send a request for clearance using a scheduling request (SR), and the base station will respond with the UL clearance. The process of obtaining the necessary UL clearance from the base station can take up to several seconds, which is a significant delay, especially in emergency situations.

[0084] To reduce latency when responding to location servers 152 / 162 with requested location-related information, location servers 152 / 162 provide the serving base station with an indication that the location session has high priority and that a UL license should be provided to UE 102 in order to respond to the request. For example, location servers 152 / 162 may send an indication to the base station, such as when location servers 152 / 162 send a request to UE 102. The base station can process the license and send the UL license to the UE before the UE is ready to respond to the request. Therefore, when the UE is ready to respond to the request, the UE can use the already received UL license to send information. Thus, the UE does not need to request and wait for the UL license.

[0085] In the NR network, UE 102 can be in an RRC connected state, an RRC idle state, or an RRC inactive state. The gNB 110 in the NR network can move UE 102 to an inactive state (from the connected state or the idle state), where the UE connection context (all configurations) is saved by both the gNB 110 and UE 102. The functionality of UE 102 in the inactive state is largely the same as in the idle state, where UE 102 will monitor paging during the Discontinuous Paging Receive (DRX) cycle. However, while in the inactive state, UE 102 can also, for example, periodically perform RAN-based notification area updates, and when moved outside the configured RAN-based notification area, can obtain system information and can send system information (SI) requests (if configured). When the RRC connection is restored, data activity recovery is faster than establishing an RRC connection from the idle state after releasing the RRC connection, because the UE connection context has been saved by both the gNB 110 and UE 102. Therefore, by using the inactive state, UE 102 will not remain idle in the connected state for extended periods, which would require additional power consumption. Furthermore, resuming the connection from the inactive state will be fast and therefore incur almost no delay. Only gNB 110 can suspend the RRC connection to move UE 102 to the inactive state, but resumption can be triggered by either the UE or gNB 110.

[0086] Figure 2 The example illustrates a simple UE RRC state machine 200 and state transitions in the NR, for example, as described in 3GPP TS38.331. UE 102 can have only one RRC state at a time in the NR. As shown, UE 102 can have the NR RRC_CONNECTED state 202, the NR RRC_INACTIVE state 204, or the NR RRC_IDLE state 206. When an RRC connection is established, UE 102 can be in the RRC_CONNECTED state 202 or the RRC_INACTIVE state 204. If not, i.e., no RRC connection is established, UE 102 is in the RRC_IDLE state 206.

[0087] In RRC_IDLE state 206, UE-specific DRX can be configured by the upper layer, and UE-controlled mobility can be configured based on the network. When in RRC_IDLE state 206, UE 102 can monitor short messages sent via downlink control information (DCI) using the Paging Radio Network Temporary Identifier (P-RNTI), monitor the paging channel for core network (CN) paging using the 5G Service Temporary Mobile Subscriber Identifier (S-TMSI), perform neighboring cell measurements and cell selection (reselection), obtain system information and send SI requests (if configured), and perform available measurements and record the location and time of the UE.

[0088] In RRC_INACTIVE state 204, UE-specific DRX can be configured by the upper layer or by the RRC layer, and UE mobility control can be configured based on the network. Furthermore, UE 102 stores the UE inactive access stratum (AS) context, and the RAN-based notification area is configured by the RRC layer. When in RRC_INACTIVE state 204, UE 102 can monitor short messages sent via DCI along with P-RNTI, monitor paging channels using CN paging with 5G-S-TMSI and RAN paging using fully inactive RNTI (I-RNTI), and perform neighbor cell measurements and cell selection (reselection). Additionally, UE 102 can periodically perform RAN-based notification area updates and when moving out of the configured RAN-based notification area, obtain system information and send SI requests (if configured), and perform recording of available measurements and recording the location and time of the UE.

[0089] In RRC_CONNECTED state 202, UE 102 stores the AS context and is configured to pass unicast data to / from the UE. At lower layers, UE 102 can be configured with UE-specific DRX. UEs configured to support carrier aggregation (CA) can use one or more SCells aggregated with SpCell to increase bandwidth. UEs configured to support dual connectivity (DC) use a secondary cell group (SCG) aggregated with the primary cell group (MCG) to increase bandwidth. Furthermore, RRC_Connected state 202 includes network-controlled mobility within the NR and to / from E-UTRA. When in RRC_CONNECTED state 202, if configured, UE 102 can monitor short messages sent via DCI using P-RNTI, monitor control channels associated with shared data channels to determine whether to schedule data for them, provide channel quality and feedback information, perform neighbor cell measurements and measurement reports, and acquire system information.

[0090] like Figure 2As shown, from NR RRC_CONNECTED state 202, UE 102 can transition to NR RRC_IDLE state 206 by being released by gNB 110. By establishing a connection, UE 102 can transition from NR RRC_IDLE state 206 to NR RRC_CONNECTED state 202.

[0091] Furthermore, from NR RRC_CONNECTED state 202, UE 102 can be released by gNB 110 and transition to NR RRC_INACTIVE state 204. From NR RRC_INACTIVE state 204, UE 102 can transition back to NR RRC CONNECTED state 202 by resuming the connection. Since both gNB 110 and UE 102 store the UE connection context (including AS context), resuming NR RRC_CONNECTED state 202 from NR RRC_INACTIVE state 204 is faster and requires fewer message passes than establishing NR RRC_CONNECTED state 202 from NR RRC_IDLE state 206. Additionally, as shown, when in NR RRC_INACTIVE state 204, UE 102 can be released by gNB 110 and transition to NR RRC_IDLE state 206.

[0092] As discussed above, only gNB 110 can suspend the RRC connection and transition UE 102 to an inactive state, for example, from NR RRC_CONNECTED state 202 to NR RRC_INACTIVE state 204. However, during a positioning session between the location server (e.g., LMF 152) and UE 102, LPP is used to send messages, which are then passed through gNB 110 and gNB 110 is unaware of the message details. Therefore, during the positioning session, gNB 110 is unaware of the timing instructions from the location server to UE 102, such as the frequency of positioning measurements, or if the location server has even requested positioning measurements from the UE. Consequently, gNB 110 lacks the timing information necessary for positioning to determine whether the RRC connection with UE 102 should be suspended and whether UE 102 should be placed in an inactive mode.

[0093] Therefore, in one implementation, the location server (e.g., LMF 152) can communicate with the base station (e.g., gNB 110) to suspend the RRC connection with UE 102. For example, when the location server determines that UE 102 does not need to send location information to the location server during an extended period, it will switch UE 102 to an inactive state. For example, the location server will not request measurements during the extended period, or location measurements from UE 102 will not be reported frequently. For example, the location server can provide the base station with an indication of the time until a connection with UE 102 will be needed, such as the time until the location server will request location measurements, or the time until a periodic trigger for reporting location measurements occurs. For example, the base station can determine whether to suspend the RRC connection of UE 102 and put UE 102 into an inactive mode, for example, based on UE 102's data activity and network congestion.

[0094] After base station 110 suspends the RRC connection with UE 102 and transitions UE 102 to an inactive state, the UE connection context is stored by UE 102 and base station 110. UE 102 can resume the connection, for example, when ready to send location measurements. For example, when UE 102 is in an inactive state, the location server can page UE 102 to request location measurements, or UE 102 can be configured to perform periodic location measurements. When in inactive mode, UE 102 can perform location measurements, such as GNSS measurements or cellular-based positioning, for example, using DL PRS signals received from the base station. When UE 102 is ready to send location measurements to the location server, UE 102 can send a request to base station 110 to resume the RRC connection. Because UE 102 and the base station store the UE connection context while the UE is in an inactive state, the resumption of the RRC connection can be fast and consume less power compared to the conventional connection release / establishment between idle and connected states. If UE 102 determines that the location session has ended, UE 102 can request base station 110 to release the connection and switch UE 102 to an idle state.

[0095] Figure 3 Signaling flow 300 is shown, illustrating the process during a location session between UE 102 and location server 152. Figure 1 The various messages sent between components of the communication system 100 depicted herein, where the location server requests a pause of the RRC connection of UE 102 during a location session, are discussed herein. While flowcharts relating to 5G NR radio access using gNB 110 are discussed for ease of illustration, similar scenarios involving ng-eNB 114 or eNBs instead of gNB 110 are also discussed. Figure 3The signaling flow will be obvious to those skilled in the art. Furthermore, it should be understood that messages provided in signaling flow 300 are used to describe the process of establishing an RRC connection and the location server requesting a pause in the RRC connection during a positioning session, and it should be understood that additional messages and actions may be included in the positioning session. In signaling flow 300, it is assumed that UE 102 and location server 152 communicate using the previously referenced LPP positioning protocol, although the use of NPP or a combination of LPP and NPP is also possible. Signaling flow 300 can be executed in the control plane or the user plane.

[0096] In phase 1, UE 102 may send a message (e.g., an RRC message) to base station 110 to request the establishment of an RRC connection. This may be in response to receiving a paging message from base station 110. Figure 3 (not shown in the diagram), messages are sent via UE 102, which can occur, for example, if AMF 154 needs to establish a connection to UE 102 to support the location of UE 102 (e.g., as described below for phases 3 to 12).

[0097] In phase 2, base station 110 can send a message to UE 102 to establish an RRC connection. Although phases 1 and 2 describe only two messages, additional messages can be sent to establish an RRC connection, for example, if UE 102 is initially in an RRC IDLE state.

[0098] In phase 3, location server 152 may send one or more messages to UE 102 for a positioning session. For example, the message may be a request for the ability to respond to UE 102. In another example, the message may be a provision of auxiliary data message to UE 102 (which provides auxiliary data via base station 110), the provision of auxiliary data message including auxiliary data for UE measurements. The auxiliary data may be used for ECID, AOD, RTT, TDOA, A-GNSS, and / or other positioning methods supported by UE 102. In some embodiments, location server 152 may have already made a request and UE 102 may have already provided positioning capabilities, and the auxiliary data may be consistent with UE capabilities. Furthermore, in some embodiments, UE 102 may send an LPP request for auxiliary data message to location server 152 prior to phase 3.

[0099] In phase 4, location server 152 may send an LPP request location information message to UE 102 via base station 110. This LPP request location information message includes a request for location measurement, for example, for AOD, RTT, TDOA, A-GNSS, ECID, etc. The LPP request location information message sent in phase 4 may indicate a long response time (e.g., greater than 20 seconds) or may indicate periodic or triggered positioning with a long response period (e.g., a period of 1 to 30 minutes).

[0100] In phase 5, location server 152 may send a message (e.g., an NRPPa message) to base station 110 requesting the suspension of the RRC connection between UE 102 and base station 110. For example, the message could be a suggestion to suspend the RRC connection. Alternatively, the message may include an indication of a duration during which message transmission between UE 102 and location server 152 is not expected. For example, the duration could be based on the expected time until UE 102 performs location measurements. For example, location information requests from location server 152 to UE 102 may not occur for a period of time, or the location session may be a periodic or triggered location session, and UE 102 may not need to obtain and report location measurements for a period of time. For example, the duration could be based on the time until a location information message is expected from UE 102. In another implementation, the duration could be based on the time until a location-related request from UE 102 is expected. For example, phase 5 may occur before phase 4, and the duration could be the time until a location information request is expected to be sent by location server 152. Similarly, phase 5 can occur earlier, and its duration can be until the expected time when a capability request or any other location request is expected to be sent by location server 152. In some implementations, location server 152 may determine that UE 102 is moving, and a RAN update (e.g., a switch to another base station) may occur before the expected next location message. Therefore, location server 152 may include an indication of UE 102's movement and request the release of the connection to place UE 102 into an idle state.

[0101] In phase 6, base station 110 may, at least in part, respond to the message from location server 152 in phase 5 to determine that the RRC connection with UE 102 should be suspended, and may send a connection suspension message (e.g., an RRC release message with a suspension indication) to UE 102 to place UE 102 into the RRC INACTIVE state. In some implementations, base station 110 may determine the data activity of UE 102 using the connection with base station 110, and the determination of connection suspension may also be based on data activity, for example, if scheduled activity is minimal, e.g., no activity or less than a threshold. In response to the suspension message, UE 102 transitions from the RRC connected state to the inactive state. Base station 110 and UE 102 store UE connection contexts (such as AS contexts) to enable rapid restoration of the RRC connection with minimal signaling between UE 102 and base station 110. In some implementations, UE 102 can determine its mobility state, such as high mobility, medium mobility, or low mobility. The phase 6 message includes an indication of UE 102's mobility state, and if UE 102 is in a high mobility state, it can request connection release to place UE 102 in an idle state; and if UE 102 is in a low mobility state, it can request connection suspension to place UE 102 in an inactive state. Base station 110 can determine to release the connection, for example, if the UE is in a high mobility state, and can send a release message to place UE 102 in an idle state.

[0102] In optional phase 7A, UE 102 can detect event-triggered location measurements of a location session, such as periodic events, for example, if the location session is periodic or triggered.

[0103] In optional phase 7B, location server 152 may send a paging message to UE 102 that includes a measurement request. For example, when UE 102 is in an inactive state, UE 102 continues to monitor the paging channel to perform CN paging using 5G-S-TMSI and RAN paging using Fully Inactive-RNTI (I-RNTI), which can be used to instruct UE 102 to perform location measurements.

[0104] In phase 8, UE 102 can obtain location measurements, such as AOD, RTT, TDOA, A-GNSS, ECID, etc., while still being in an inactive state. In some implementations, UE 102 can further estimate the UE's location based on the location measurements.

[0105] In phase 9, UE 102 may send a connection restoration request message to base station 110, requesting the restoration of the RRC connection. For example, the connection restoration request may include stored UE connection context (such as AS context) stored by the UE to help restore the RRC connection.

[0106] In phase 10, base station 110 may send a connection restoration response message to UE 102 to restore the RRC connection between UE 102 and base station 110. For example, when UE 102 is inactive, base station 110 may restore the connection based on the UE context information received from UE 102 in the phase 9 message and the UE context stored by base station 110.

[0107] In phase 11, after UE 102 has restored its RRC connection with base station 110, UE 102 sends an LPP location information message to location server 152 via base station 110. The LPP location information message includes UE location measurements and / or location estimates obtained in phase 8.

[0108] In phase 12, location server 152 may use the measurements and / or location estimates received in phase 11 to determine (e.g., calculate) or verify the location of UE 102.

[0109] Figure 4 Signaling flow 400 is shown, illustrating the process during a location session between UE 102 and location server 404. Figure 1 The various messages sent between components of the communication system 100 depicted herein, whereby UE 102 requests a pause of the RRC connection during a positioning session, as discussed herein. While flowcharts relating to 5G NR radio access using gNB 110 are discussed for ease of illustration, similar scenarios involving ng-eNB 114 or eNBs instead of gNB 110 are also discussed. Figure 3 The signaling flow will be obvious to those skilled in the art. Furthermore, it should be understood that messages provided in signaling flow 400 are used to describe the process of establishing an RRC connection and UE 102 requesting an RRC connection pause during a positioning session, and it should be understood that additional messages and actions may be included in the positioning session. In signaling flow 400, it is assumed that UE 102 and location server 404 communicate using the aforementioned LPP positioning protocol. Signaling flow 400 can be executed in either the control plane or the user plane. When signaling flow 400 is executed in the control plane, location server 404 may be an LMF 152. When signaling flow 400 is executed in the user plane, location server 404 may be an SLP 162, and... Figure 4The LPP messages shown at points 4, 5, and 12 in the middle stages can each be transmitted within a SUPL message (e.g., a SUPL POS message).

[0110] In Phase 1, client 402 (which may be inside UE 102 (e.g., an application within UE 102) or outside UE 102 (e.g., a web server)) sends a request to location server 404 to request the location of UE 102. If location server 404 is SLP 162, the request can be sent directly to location server 404. If location server 404 is LMF 152, the request can be sent indirectly to location server 404 through other intermediate entities, for example, via GMLC 160 and AMF 154.

[0111] In Phase 1A, UE 102 can receive a location request or location indication from client 402. The request or indication may include an indication of the duration of a measurement report, for example, for periodic or triggered location.

[0112] In phase 2, UE 102 can send a message to base station 110 to request an RRC connection.

[0113] In phase 3, base station 110 can send a message to UE 102 to establish an RRC connection.

[0114] In phase 4, location server 404 may send one or more messages to UE 102 for a positioning session. For example, the message may be a request for the ability to respond to UE 102. In another example, the message may be a provision of auxiliary data message to UE 102 (which provides auxiliary data via base station 110), the provision of auxiliary data message including auxiliary data for UE measurements. The auxiliary data may be used for ECID, AOD, RTT, TDOA, A-GNSS, and / or other positioning methods supported by UE 102. In some embodiments, location server 404 may have already made the request and UE 102 may have already provided positioning capabilities, and the auxiliary data may be consistent with UE capabilities. Furthermore, in some embodiments, UE 102 may send an LPP request for auxiliary data message to location server 404 prior to phase 4.

[0115] In phase 5, location server 404 may send an LPP request location information message to UE 102 via base station 110. This LPP request location information message includes a request for location measurement, for example, for AOD, RTT, TDOA, a-GNSS, ECID, etc. The LPP request location information message sent in phase 5 may indicate a long response time or may indicate periodic or triggered positioning with a long response period.

[0116] In phase 6, UE 102 may send a message to base station 110 requesting the suspension of the RRC connection between UE 102 and base station 110. For example, the message could be a suggestion to suspend the RRC connection. Alternatively, the message may include an indication of a duration during which message transmission between UE 102 and location server 404 is not expected. For example, the duration could be based on the expected time until UE 102 performs location measurements. For example, location information requests from location server 404 to UE 102 may not occur for a period of time, or the location session may be a periodic or triggered location session, and UE 102 may not need to obtain and report location measurements for a period of time. For example, the duration could be based on the time until a location information message is expected from UE 102. In another implementation, the duration could be based on the time until a location-related request is expected from location server 404. For example, phase 6 may occur before phase 5, and the duration could be the time until a location information request is expected to be sent by location server 404. Similarly, phase 6 can occur before phase 4, and its duration can be until the expected capability request or any other location request is sent by location server 404. In some implementations, UE 102 can use its connection with base station 110 to determine data activity, and can send a message to base station 110 if scheduled activity is minimal, e.g., no activity or less than a threshold. In some implementations, UE 102 can determine that UE 102 is moving, and a RAN update (e.g., handover to another base station) can occur before the expected next location message. Therefore, UE 102 can include an indication of UE 102's movement and request to release the connection to place UE 102 into an idle state.

[0117] In phase 7, base station 110 may, at least in part, respond to the message from UE 102 in phase 6 to determine that the RRC connection with UE 102 should be suspended, and may send a connection suspension message to UE 102. In some implementations, base station 110 may determine the data activity of UE 102 using the connection with base station 110, and the determination of connection suspension may also be based on data activity, for example, if scheduled activity is minimal, e.g., no activity or less than a threshold. In response to the suspension message, UE 102 transitions from an RRC connected state to an inactive state. Base station 110 and UE 102 store UE connection contexts (such as AS contexts) to enable rapid restoration of the RRC connection with minimal signaling between UE 102 and base station 110. In some implementations, if the message in phase 6 includes an indication of UE 102's movement and a request to release the connection, base station 110 may determine to release the connection and send a release message to place UE 102 into an idle state.

[0118] In phase 8, client 402 can detect event triggering of the location session, such as periodic events or timers, for example, if the location session is periodic or triggered. Client 402 can indicate to UE 102 that the timer has ended and will perform location measurement and / or provide a location information message to location server 404.

[0119] In phase 9, UE 102 can obtain location measurements, such as AOD, RTT, TDOA, A-GNSS, ECID, etc., while still being in an inactive state. In some implementations, UE 102 can further estimate its position based on the location measurements.

[0120] In phase 10, UE 102 may send a connection restoration request message to base station 110 to request the restoration of the RRC connection. For example, the connection restoration request may include stored UE connection context (such as AS context) stored by UE 102 to help restore the RRC connection.

[0121] In phase 11, base station 110 may send a connection restoration response message to UE 102 to restore the RRC connection between UE 102 and base station 110. For example, when UE 102 is inactive, base station 110 may restore the connection based on the UE context information received from UE 102 in the phase 10 message and the UE context stored by base station 110.

[0122] In phase 12, after UE 102 has restored its RRC connection with base station 110, UE 102 sends an LPP location information message to location server 404 via base station 110. The LPP location information message includes UE location measurements and / or location estimates obtained in phase 9.

[0123] In phase 13, location server 404 may use the measurements and / or location estimates received in phase 12 to determine (e.g., calculate) or verify the location of UE 102.

[0124] In phase 14, location server 404 may send the location of UE 102 to client 402 (e.g., via UE 102 if client 402 is inside UE 102).

[0125] Figure 5 A schematic block diagram illustrating certain exemplary features of UE 500 is shown. For example, UE 500 may be... Figure 1 The UE 102 shown is configured to support positioning and to request the suspension and resumption of RRC connections with the base station during a positioning session, as discussed herein. For example, UE 500 can perform... Figure 8 The process flow and the algorithms disclosed herein are illustrated. For example, UE 500 may include one or more processors 502, memory 504, external interfaces such as at least one wireless transceiver 510 (e.g., a wireless network interface), SPS receiver 515, and one or more sensors 513 operably coupled to one or more connections 506 (e.g., bus, line, fiber optic, link, etc.) to a non-transitory computer-readable medium 520 and memory 504. For example, SPS receiver 515 may receive and process data from... Figure 1 The SPS signal of SV 190 is shown. For example, one or more sensors 513 may be inertial measurement units (IMUs), which may include one or more accelerometers, one or more gyroscopes, magnetometers, etc. UE 500 may also include additional items not shown, such as a user interface (e.g., a virtual keypad on the display) that may include a display, keypad, or other input device through which a user can interact with the UE. In some example implementations, all or part of UE 500 may take the form of a chipset, etc.

[0126] At least one wireless transceiver 510 may be a transceiver for both WWAN and WLAN communication systems, or may include separate transceivers for both WWAN and WLAN. The wireless transceiver 510 may include a transmitter 512 and a receiver 514 coupled to one or more antennas 511 for transmitting (e.g., on one or more uplink channels and / or one or more sidelink channels) and / or receiving (e.g., on one or more downlink channels and / or one or more sidelink channels) wireless signals and converting signals from wireless signals to wired (e.g., electrical and / or optical) signals and from wired (e.g., electrical and / or optical) signals to wireless signals. Therefore, the transmitter 512 may include multiple transmitters, which may be discrete components or combined / integrated components, and / or the receiver 514 may include multiple receivers, which may be discrete components or combined / integrated components. The wireless transceiver 510 can be configured to support various standards such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Telephone System), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), WiFi, and WiFi Direct (WiFi-D). Various radio access technologies (RATs) such as Zigbee are used to transmit signals (e.g., with base stations and access points and / or one or more other devices). The new radio can use millimeter-wave frequencies and / or frequencies below 6 GHz (sub-6 GHz). The wireless transceiver 510 can be communicatively coupled to a transceiver interface (e.g., via optical and / or electrical connections), which can be at least partially integrated with the wireless transceiver 510.

[0127] In some embodiments, UE 500 may include an antenna 511, which may be internal or external. The UE antenna 511 may be used to transmit and / or receive signals processed by the wireless transceiver 510. In some embodiments, the UE antenna 511 may be coupled to the wireless transceiver 510. In some embodiments, measurements of signals received (transmitted) by UE 500 may be performed at the connection point between the UE antenna 511 and the wireless transceiver 510. For example, the measurement reference point for measuring the received (transmitted) RF signal may be the input (output) terminal of receiver 514 (transmitter 512) and the output (input) terminal of UE antenna 511. In a UE 500 having multiple UE antennas 511 or an antenna array, the antenna connector may be considered as a virtual point representing the aggregated output (input) of multiple UE antennas. In some embodiments, UE 500 may measure received signals, including signal strength and TOA measurements, and the raw measurements may be processed by one or more processors 502.

[0128] One or more processors 502 may be implemented using a combination of hardware, firmware, and software. For example, one or more processors 502 may be configured to perform the functions discussed herein by implementing one or more instructions or program code 508 on a non-transitory computer-readable medium such as medium 520 and / or memory 504. In some embodiments, one or more processors 502 may represent one or more circuits that are configurable to perform at least a portion of a data signal calculation program or process related to the operation of UE 500.

[0129] Medium 520 and / or memory 504 may store instructions or program code 508 containing executable code or software instructions that, when executed by one or more processors 502, cause one or more processors 502 to operate as a dedicated computer programmed to perform the techniques disclosed herein. As shown in UE 500, medium 520 and / or memory 504 may include one or more components or modules that may be implemented by one or more processors 502 to perform the methods described herein. Although components or modules are shown as software in memory 520 executable by one or more processors 502, it should be understood that components or modules may be stored in memory 504 or may be dedicated hardware in or outside one or more processors 502.

[0130] Multiple software modules and data tables may reside in medium 520 and / or memory 504 and be used by one or more processors 502 to manage both the communications and functions described herein. It should be understood that the organization of the contents of medium 520 and / or memory 504 as shown in UE 500 is merely exemplary, and therefore the functionality of modules and / or data structures may be combined, separated, and / or constructed in different ways, depending on the implementation of UE 500.

[0131] The medium 520 and / or memory 504 may include a connection module 522, which, when implemented by one or more processors 502, configures one or more processors 502 to send and receive messages via radio transceiver 510 to establish an RRC connection with the serving base station. One or more processors 502 may also be configured, for example, to send a request to the base station via the radio transceiver to suspend the connection between the base station and the UE, thereby placing the UE in an inactive state. One or more processors 502 may be configured to request connection suspension during a location session, for example, based at least in part on the time until location measurements are performed or location information is sent to a location server. One or more processors 502 may also be configured to determine data activity scheduled for the UE during the location session, wherein the request for connection suspension may also be based on data activity. One or more processors 502 may include a request that the duration of location-related messages between the UE and the location server is not expected to be the time during which the UE performs location measurements. When in an inactive state, one or more processors 502 may be configured to store the UE connection context (e.g., AS context) in memory 504, which can be used to resume the connection. One or more processors 502 may be configured to, for example, send a request to a base station via radio transceiver 510 to restore a connection, such as when a location measurement is to be performed or when location information is to be sent to a location server, and to be configured to receive messages from the base station for use in restoring a connection using the UE connection context. In some implementations, one or more processors 502 may be configured to, for example, determine UE movement based on location measurements or sensor data that may indicate that UE 102 is moving, and that a RAN update (e.g., a handover to another base station) may occur before the expected next location message. One or more processors 502 may be configured to, for example, send a request to a base station via radio transceiver 510 to release a connection based on movement, and may include an indication of movement of the base station.

[0132] The medium 520 and / or memory 504 may include a positioning session module 524, which, when implemented by one or more processors 502, configures the one or more processors 502 to participate in a positioning session with a serving base station and a location server via a radio transceiver 510, including receiving location service requests (such as requests for positioning capabilities) and requests for location information (such as positioning measurements, e.g., for UE-assisted positioning procedures, or location estimation, e.g., for UE-based positioning procedures). The one or more processors 502 are configured to send a response to a location service request, for example, by providing positioning capabilities and the requested location information. The one or more processors 502 may also be configured to receive auxiliary data. The one or more processors 502 are further configured to perform the requested positioning measurements (which may be, for example, RxTx, AOA, TOA, RSRP, etc.), or other types of measurements, such as measurements using WiFi or SPS. The one or more processors 502 may be configured to receive periodic location requests. The one or more processors 502 may also be configured to determine a location estimation based on the positioning measurements and auxiliary data.

[0133] Depending on the application, the methods described herein can be implemented using various components. For example, these methods can be implemented in hardware, firmware, software, or any combination thereof. In a hardware implementation, one or more processors 502 may be one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or combinations thereof.

[0134] For firmware and / or software implementations, the method can be implemented using modules (e.g., programs, functions, etc.) that perform the functions described herein. In implementing the methods described herein, any machine-readable medium that tangibly embodies the instructions can be used. For example, software code can be stored in a non-transitory computer-readable medium 520 or memory 504 connected to and executed by one or more processors 502. Memory can be implemented within one or more processors or outside one or more processors. As used herein, the term "memory" refers to any type of long-term, short-term, volatile, non-volatile, or other memory, and should not be limited to any particular type of memory or any particular number of memories or the type of medium on which memory is stored.

[0135] If implemented in firmware and / or software, the functionality may be stored as one or more instructions or program code 508 on a non-transitory computer-readable medium, such as medium 520 and / or memory 504. Examples include computer-readable media encoding data structures and computer-readable media encoding computer program code 508. For example, a non-transitory computer-readable medium including program code 508 stored thereon may include program code 508 for supporting the suspension of the RRC connection between the UE and the base station during a positioning session in a manner consistent with the disclosed embodiments. The non-transitory computer-readable medium 520 includes a physical computer storage medium. The storage medium may be any available medium accessible by a computer. By way of example and not limitation, such non-transitory computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that may be used to store desired program code 508 in the form of instructions or data structures and accessible by a computer; as used herein, disks and optical discs include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0136] In addition to being stored on computer-readable medium 520, instructions and / or data may be provided as signals on a transmission medium included in a communication device. For example, the communication device may include a wireless transceiver 510 having signals indicating instructions and data. The instructions and data are configured to cause one or more processors to perform the functions outlined in the claims. That is, the communication device includes a transmission medium having signals indicating the performance of the disclosed functions.

[0137] Memory 504 can represent any data storage mechanism. Memory 504 may include, for example, main memory and / or secondary memory. Main memory may include, for example, random access memory, read-only memory, etc. Although shown in this example as separate from one or more processors 1202, it should be understood that all or part of the main memory may be provided within or otherwise co-located / coupled with one or more processors 502. Secondary memory may include, for example, memory of the same or similar type as the main memory and / or one or more data storage devices or systems, such as, for example, disk drives, optical disk drives, tape drives, solid-state drives, etc.

[0138] In some implementations, the secondary storage may be operatively receiving or otherwise configured to be coupled to the non-transitory computer-readable medium 520. Therefore, in some example implementations, the methods and / or apparatus presented herein may take the form, in whole or in part, of the computer-readable medium 520, which may include computer-implementable program code 508 stored thereon, which, if executed by one or more processors 502, may be operable to enable the performance of all or part of the example operations as described herein. The computer-readable medium 520 may be part of the memory 504.

[0139] Figure 6 A schematic block diagram illustrating certain exemplary features of location server 600, such as LMF 152 or SLP 162, is shown. Figure 1 and Figure 2 As shown, it is configured to support UE positioning and, during a positioning session, to request the suspension and resumption of the RRC connection between the UE and the base station, as discussed herein. The location server 600 can perform, for example... Figure 9 The process flow and the algorithms disclosed herein are illustrated. For example, location server 600 may include one or more processors 602, memory 604, and external interfaces 616 (e.g., wired or wireless network interfaces to entities in a base station and / or core network) operably coupled to one or more connections 606 (e.g., buses, lines, optical fibers, links, etc.) to non-transitory computer-readable medium 620 and memory 604. In some example implementations, all or part of location server 600 may take the form of a chipset, etc.

[0140] One or more processors 602 may be implemented using a combination of hardware, firmware, and software. For example, one or more processors 602 may be configured to perform the functions discussed herein by implementing one or more instructions or program code 608 on a non-transitory computer-readable medium such as medium 620 and / or memory 604. In some embodiments, one or more processors 602 may represent one or more circuits that are configurable to perform at least a portion of a data signal calculation program or process related to the operation of location server 600.

[0141] Medium 620 and / or memory 604 may store instructions or program code 608 containing executable code or software instructions that, when executed by one or more processors 602, cause one or more processors 602 to operate as a dedicated computer programmed to perform the techniques disclosed herein. As shown in location server 600, medium 620 and / or memory 604 may include one or more components or modules that may be implemented by one or more processors 602 to perform the methods as described herein. Although components or modules are shown as software in memory 620 executable by one or more processors 602, it should be understood that components or modules may be stored in memory 604 or may be dedicated hardware in or outside one or more processors 602.

[0142] Multiple software modules and data tables may reside in medium 620 and / or memory 604 and be used by one or more processors 602 to manage both the communications and functions described herein. It should be understood that the organization of the contents of medium 620 and / or memory 604 as shown in location server 600 is merely exemplary, and therefore the functionality of modules and / or data structures may be combined, separated, and / or constructed in different ways depending on the implementation of location server 600.

[0143] Medium 620 and / or memory 604 may include a positioning session module 622, which, when implemented by one or more processors 602, configures the one or more processors 602 to participate in a positioning session with the UE via a serving base station through an external interface 616, including sending location service requests (such as requests for positioning capabilities) and requests for location information (such as positioning measurements, e.g., for UE-assisted positioning procedures, or location estimation, e.g., for UE-based positioning procedures). The one or more processors 602 are configured to receive responses to location service requests, including, for example, receiving positioning capabilities and the requested location information from the UE. The one or more processors 602 may be configured to send and receive messages for periodic positioning sessions. The one or more processors 602 may also be configured to send auxiliary data. The one or more processors 602 may also be configured to determine the UE's location estimation based on received positioning measurements (e.g., RxTx, AOA, TOA, RSRP, etc.) or other types of measurements (such as measurements using WiFi or SPS).

[0144] The medium 620 and / or memory 604 may include a connection module 624, which, when implemented by one or more processors 602, configures one or more processors 602 to send a request to the base station, for example via an external interface 616, to suspend the connection between the base station and the UE, thereby placing the UE in an inactive state. One or more processors 602 may be configured to request connection suspension during a location session, for example, based at least in part on the time until a location measurement is performed or location information is sent to a location server. One or more processors 602 may also be configured to determine data activity scheduled for the UE during the location session, wherein the request for connection suspension may also be based on data activity. One or more processors 602 may include a request that does not anticipate the duration of location-related messages between the UE and the location server may be the time during which the UE performs location measurements. One or more processors 602 may be configured to page the UE when the UE is in an inactive state, for example, instructing the UE when a location measurement is to be performed or when location information is to be sent to a location server. In some implementations, one or more processors 602 may be configured to determine the movement of the UE, for example, based on location measurements that may indicate that the UE is moving, and RAN updates (e.g., handover to another base station) may occur before the expected next location message. One or more processors 602 may be configured to, for example, send a request to the base station via an external interface 616 to release the connection based on movement, and may include an indication of the movement of the base station.

[0145] Depending on the application, the methods described herein can be implemented using various components. For example, these methods can be implemented in hardware, firmware, software, or any combination thereof. In a hardware implementation, one or more processors 602 may be one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or combinations thereof.

[0146] For firmware and / or software implementations, the method can be implemented using modules (e.g., programs, functions, etc.) that perform the functions described herein. In implementing the methods described herein, any machine-readable medium that tangibly embodies the instructions can be used. For example, software code can be stored in a non-transitory computer-readable medium 620 or memory 604 connected to and executed by one or more processors 602. Memory can be implemented within one or more processors or outside one or more processors. As used herein, the term "memory" refers to any type of long-term, short-term, volatile, non-volatile, or other memory, and should not be limited to any particular type of memory or any particular number of memories or the type of medium on which memory is stored.

[0147] If implemented in firmware and / or software, the functionality may be stored as one or more instructions or program code 608 on a non-transitory computer-readable medium, such as medium 620 and / or memory 604. Examples include computer-readable media encoding data structures and computer-readable media encoding computer program code 608. For example, a non-transitory computer-readable medium including program code 608 stored thereon may include program code 608 for supporting the suspension of the RRC connection between the UE and the base station during a positioning session in a manner consistent with the disclosed embodiments. Non-transitory computer-readable medium 620 includes physical computer storage media. The storage medium may be any available medium accessible by a computer. By way of example and not limitation, such non-transitory computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that may be used to store desired program code 608 in the form of instructions or data structures and is accessible by a computer; as used herein, disks and optical discs include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0148] In addition to being stored on computer-readable medium 620, instructions and / or data may be provided as signals on a transmission medium included in a communication device. For example, the communication device may include an external interface 616 having signals indicating instructions and data. The instructions and data are configured to cause one or more processors to perform the functions outlined in the claims. That is, the communication device includes a transmission medium having signals indicating information indicating the performance of the disclosed functions.

[0149] Memory 604 can represent any data storage mechanism. Memory 604 may include, for example, main memory and / or secondary memory. Main memory may include, for example, random access memory, read-only memory, etc. Although shown in this example as separate from one or more processors 1202, it should be understood that all or part of the main memory may be provided within or otherwise co-located / coupled with one or more processors 602. Secondary memory may include, for example, memory of the same or similar type as the main memory and / or one or more data storage devices or systems, such as, for example, disk drives, optical disk drives, tape drives, solid-state drives, etc.

[0150] In some implementations, the secondary storage may be operatively receiving or otherwise configured to be coupled to the non-transitory computer-readable medium 620. Thus, in some example implementations, the methods and / or apparatus presented herein may take the form, in whole or in part, of the computer-readable medium 620, which may include computer-implementable program code 608 stored thereon, which, if executed by one or more processors 602, may be operable to enable the performance of all or part of the example operations as described herein. The computer-readable medium 620 may be part of the memory 604.

[0151] Figure 7 A schematic block diagram illustrating certain exemplary features of base station 700 is shown, for example, Figure 1 The base station 110 shown is capable of supporting UE positioning and requesting the suspension and resumption of RRC connections between the UE and the base station during a positioning session, as discussed herein. Base station 700 can be an eNB or a gNB. Base station 700 can perform, for example... Figure 10The process flow and algorithms disclosed herein are illustrated. For example, base station 700 may include one or more processors 702, memory 704, and external interfaces that may include a wireless transceiver 710 (e.g., a wireless network interface) and a communication interface 716 (e.g., a wired or wireless network interface directly or via one or more intermediate entities connected to other base stations and / or entities in the core network, such as location servers), operably coupled to a non-transitory computer-readable medium 720 and memory 704 via one or more connections 706 (e.g., bus, line, fiber optic, link, etc.). Base station 700 may also include additional items not shown, such as a user interface that may include, for example, a display, keyboard, or other input device, such as a virtual keyboard on a display, through which a user can interact with the base station. In some example implementations, all or part of base station 700 may take the form of a chipset, etc. For example, wireless transceiver 710 may include a transmitter 712 and a receiver 714, the transmitter 712 being capable of transmitting one or more signals via one or more types of wireless communication networks and the receiver 714 receiving one or more signals transmitted via one or more types of communication networks. The communication interface 716 can be a wired or wireless interface, capable of connecting to other base stations or network entities in the RAN, such as location servers, for example, LMF 152 or SLP 162, via various entities such as AMF 154 or UPF 158. Figure 1 As shown.

[0152] In some embodiments, base station 700 may include antenna 711, which may be internal or external. Antenna 711 may be used to transmit and / or receive signals processed by wireless transceiver 710. In some embodiments, antenna 711 may be coupled to wireless transceiver 710. In some embodiments, measurements of signals received (transmitted) by base station 700 may be performed at the connection point between antenna 711 and wireless transceiver 710. For example, the measurement reference point for measuring the received (transmitted) RF signal may be the input (output) terminal of receiver 714 (transmitter 712) and the output (input) terminal of antenna 711. In base station 700 having multiple antennas 711 or antenna arrays, antenna connectors may be considered as virtual points representing the aggregated output (input) of multiple antennas. In some embodiments, base station 700 may measure received signals, including signal strength and TOA measurements, and the raw measurements may be processed by one or more processors 702.

[0153] One or more processors 702 may be implemented using a combination of hardware, firmware, and software. For example, one or more processors 702 may be configured to perform the functions discussed herein by implementing one or more instructions or program code 708 on a non-transitory computer-readable medium such as medium 720 and / or memory 704. In some embodiments, one or more processors 702 may represent one or more circuits that are configurable to perform at least a portion of a data signal calculation program or process related to the operation of base station 700.

[0154] Medium 720 and / or memory 704 may store instructions or program code 708 containing executable code or software instructions that, when executed by one or more processors 702, cause one or more processors 702 to operate as a dedicated computer programmed to perform the techniques disclosed herein. As shown in base station 700, medium 720 and / or memory 704 may include one or more components or modules that may be implemented by one or more processors 702 to perform the methods described herein. Although components or modules are shown as software in memory 720 executable by one or more processors 702, it should be understood that components or modules may be stored in memory 704 or may be dedicated hardware in or outside of one or more processors 702. Multiple software modules and data tables may reside in medium 720 and / or memory 704 and be used by one or more processors 702 to manage both the communications and functions described herein. It should be understood that the organization of the contents of the medium 720 and / or memory 704 as shown in base station 700 is merely exemplary, and therefore the functionality of the modules and / or data structures can be combined, separated and / or constructed in different ways, depending on the implementation of base station 700.

[0155] The medium 720 and / or memory 704 may include a connection module 722, which, when implemented by one or more processors 702, configures one or more processors 702 to send and receive messages via radio transceiver 710 to establish an RRC connection with the UE. The one or more processors 702 may also be configured to receive a request, for example, from an entity (such as a location server) via communication interface 716 or from the UE via the radio transceiver, to suspend the connection between the base station and the UE, thereby placing the UE in an inactive state. For example, the request may include a duration during which location-related messages between the UE and the location server are not expected, the duration of which may be the time during which the UE performs location measurements. The one or more processors 702 may be configured to determine, for example, to suspend the connection with the UE based at least in part on the time until location measurements are performed or location information is sent to the location server. The one or more processors 702 may also be configured to determine data activity scheduled for the UE during a location session, wherein the determination of suspending the connection may also be based on data activity. When inactive, one or more processors 702 can be configured to store the UE connection context (e.g., AS context) in memory 704, which can be used to restore the connection. One or more processors 702 can be configured to receive a request from the UE to restore the connection, for example via radio transceiver 710, such as when a location measurement is to be performed or when location information is to be sent to a location server, and to send a message to the UE for restoring the connection using the UE connection context. In some implementations, the request may include a request to release the connection with the UE, for example, if the UE is moving and a RAN update (e.g., a switch to another base station) may occur before the expected next location message. The request may include, for example, an indication of UE movement. One or more processors 702 can be configured to determine whether to release the connection with the UE.

[0156] The medium 720 and / or memory 704 may include a location session module 724, which, when implemented by one or more processors 702, configures one or more processors 702 to participate in a location session with the UE and the location server via an external interface (wireless transceiver 710 and communication interface 716). For example, one or more processors 702 may be configured to receive a location service request message from the location server and forward the location service request message to the UE, for example, in an LPP message or a SUPL message. One or more processors 702 are also configured to receive a location service response message from the UE and forward the location service response message to the location server, for example, in an LPP message or a SUPL message.

[0157] Depending on the application, the methods described herein can be implemented using various components. For example, these methods can be implemented in hardware, firmware, software, or any combination thereof. In a hardware implementation, one or more processors 702 may be one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or combinations thereof.

[0158] For firmware and / or software implementations, the method can be implemented using modules (e.g., programs, functions, etc.) that perform the functions described herein. In implementing the methods described herein, any machine-readable medium that tangibly embodies the instructions can be used. For example, software code can be stored in a non-transitory computer-readable medium 720 or memory 704 connected to and executed by one or more processors 702. Memory can be implemented within one or more processors or outside one or more processors. As used herein, the term "memory" refers to any type of long-term, short-term, volatile, non-volatile, or other memory, and should not be limited to any particular type of memory or any particular number of memories or the type of medium on which memory is stored.

[0159] If implemented in firmware and / or software, the functionality may be stored as one or more instructions or program code 708 on a non-transitory computer-readable medium, such as medium 720 and / or memory 704. Examples include computer-readable media encoding data structures and computer-readable media encoding computer program code 708. For example, a non-transitory computer-readable medium including program code 708 stored thereon may include program code 708 for supporting the suspension of the RRC connection between the UE and the base station during a positioning session in a manner consistent with the disclosed embodiments. The non-transitory computer-readable medium 720 includes a physical computer storage medium. The storage medium may be any available medium accessible by a computer. By way of example and not limitation, such non-transitory computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that may be used to store desired program code 708 in the form of instructions or data structures and is accessible by a computer; as used herein, disks and optical discs include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0160] In addition to being stored on the computer-readable medium 720, instructions and / or data may be provided as signals on a transmission medium included in a communication device. For example, the communication device may include a wireless transceiver 710 having signals indicating instructions and data. The instructions and data are configured to cause one or more processors to perform the functions outlined in the claims. That is, the communication device includes a transmission medium having signals indicating the performance of the disclosed functions.

[0161] Memory 704 can represent any data storage mechanism. Memory 704 may include, for example, main memory and / or secondary memory. Main memory may include, for example, random access memory, read-only memory, etc. Although shown in this example as separate from one or more processors 1202, it should be understood that all or part of the main memory may be provided within or otherwise co-located / coupled with one or more processors 702. Secondary memory may include, for example, memory of the same or similar type as the main memory and / or one or more data storage devices or systems, such as, for example, disk drives, optical disk drives, tape drives, solid-state drives, etc.

[0162] In some implementations, the secondary storage may be operatively receiving or otherwise configured to be coupled to the non-transitory computer-readable medium 720. Therefore, in some example implementations, the methods and / or apparatus presented herein may take the form, in whole or in part, of the computer-readable medium 720, which may include computer-implementable program code 708 stored thereon, which, if executed by one or more processors 702, may be operatively capable of performing all or part of the example operations as described herein. The computer-readable medium 720 may be part of the memory 704.

[0163] Figure 8 This illustrates a method performed by the UE in a manner consistent with the disclosed implementation for supporting user equipment (UE) (such as...). Figure 1 The flowchart shows an exemplary method 800 for location services of UE 102.

[0164] In box 802, the UE sends a message to the base station to establish a Radio Resource Control (RRC) connection with the base station, for example, as... Figure 3 The components discussed in Phase 1, used to send messages to a base station to establish a Radio Resource Control (RRC) connection with the base station, may include, for example, a radio transceiver 510 and one or more processors 502, which have dedicated hardware or implement executable code or software instructions in memory 504 and / or media 520 in the UE 500, such as a connection module 522, etc. Figure 5 As shown.

[0165] In box 804, the UE receives messages from the location server for the location session, such as... Figure 3 The components discussed in stages 3 and 4. For receiving messages for a location session from a location server, the components may include, for example, a wireless transceiver 510 and one or more processors 502, which have dedicated hardware or implement executable code or software instructions in memory 504 and / or media 520 in the UE 500, such as a location session module 524, etc. Figure 5 As shown.

[0166] In box 806, the UE receives a connection suspension message from the base station to place the UE into an inactive state, wherein the connection suspension message is initiated by a location server, for example, as... Figure 3 The components discussed in stages 5 and 6, used to receive a connection suspension message from the base station to place the UE in an inactive state (where the connection suspension is initiated by a location server), may include, for example, a wireless transceiver 510 and one or more processors 502, which have dedicated hardware or implement executable code or software instructions in memory 504 and / or media 520 in the UE 500, such as connection module 522, etc. Figure 5 As shown.

[0167] In box 808, the UE performs positioning measurements to obtain location information when it is inactive, for example, such as... Figure 3 The components discussed in phase 8, used to perform positioning measurements to obtain location information when inactive, may include, for example, a wireless transceiver 510 and one or more processors 502, which have dedicated hardware or executable code or software instructions in memory 504 and / or media 520 in the UE 500, such as a positioning session module 524, etc. Figure 5 As shown.

[0168] In box 810, the UE sends location information to the location server when it is in a connected state, for example, such as... Figure 3 The components discussed in phase 11, used to send location information to a location server while in a connected state, may include, for example, a wireless transceiver 510 and one or more processors 502, which have dedicated hardware or implement executable code or software instructions in memory 504 and / or media 520 in the UE 500, such as a location session module 524, etc. Figure 5 As shown.

[0169] In some implementations, the UE transitions from a connected state to an inactive state in response to a connection pause message, for example, as... Figure 3The components discussed in phase 6. The components used to transition from a connected state to an inactive state in response to a connection pause message may include, for example, a wireless transceiver 510 and one or more processors 502, which have dedicated hardware or implement executable code or software instructions in memory 504 and / or media 520 in the UE 500, such as connection module 522, etc. Figure 5 As shown.

[0170] In some implementations, the UE can restore its connection with the base station to transition from an inactive state to a connected state. For example, in one implementation, when location information is to be sent to a location server, the UE can send a connection restoration request message to the base station, such as... Figure 3 This is discussed in stage 9. The UE can respond to a connection restoration request message by receiving a connection restoration response message from the base station to transition from an inactive state to a connected state, for example, as... Figure 3 The components discussed in phase 10, including those for sending a connection restoration request message to the base station when location information is to be sent to the location server, and those for receiving a connection restoration response message from the base station in response to the connection restoration request message to transition from an inactive state to a connected state, may include, for example, a wireless transceiver 510 and one or more processors 502, which have dedicated hardware or implement executable code or software instructions in memory 504 and / or media 520 in the UE 500, such as a connection module 522, etc. Figure 5 As shown.

[0171] In one implementation, the location server can determine the time when the location measurement is performed and initiate a connection pause message based at least in part on the time when the location measurement is performed, for example, as... Figure 3 The components discussed in phase 5, used to determine the time to perform positioning measurements after receiving a request for location information from a location server, may include, for example, a wireless transceiver 510 and one or more processors 502, which have dedicated hardware or implement executable code or software instructions in memory 504 and / or media 520 in the UE 500, such as a connectivity module 522 and a positioning session module 524, as... Figure 5 As shown.

[0172] In one implementation, the location server initiates a connection suspension message by providing the base station with an indication of the duration during which location-related messages between the UE and the location server are not expected, for example, ... Figure 3This is discussed in Phase 5. For example, the duration of unexpected location-related messages between the UE and the location server could be the time during which the UE performs location measurements. For example, the duration of unexpected location-related messages between the UE and the location server could be based on a measurement period. For example, location-related messages between the UE and the location server that are not expected during the duration include location measurement messages to the location server. In one implementation, the base station sends a connection suspension message based on an indication of the duration, for example, as... Figure 3 The sixth stage is discussed.

[0173] In one implementation, the UE can store the UE connection context when it is inactive. The base station stores the UE connection context when the UE is inactive and can restore the RRC connection with the base station based on the UE connection context, for example... Figure 3 The components discussed in stages 6, 9, and 10. Components for storing the UE connection context when inactive (where the base station stores the UE connection context when the UE is inactive) and components for resuming connection with the base station based on the UE connection context may include, for example, a wireless transceiver 510 and one or more processors 502 having dedicated hardware or implementing executable code or software instructions in memory 504 and / or media 520 in the UE 500, such as connection module 522, etc. Figure 5 As shown.

[0174] Figure 9 This demonstrates a method consistent with the disclosed implementation, where a location server (such as...) is used... Figure 1 The LMF152 or SLP 162 shown herein performs functions to support user equipment (UE) such as Figure 1 The flowchart shows an exemplary method 900 for location services of UE 102.

[0175] In box 902, the location server sends messages to the UE for the location session, such as... Figure 3 The components discussed in stages 3 and 4. Components for sending messages for a location session to the UE may include, for example, an external interface 616 and one or more processors 602, which have dedicated hardware or implement executable code or software instructions in memory 604 and / or media 620 in the location server 600, such as a location session module 622, etc. Figure 6 As shown.

[0176] In box 904, the location server sends a message to a base station that has established a radio resource control (RRC) connection with the UE, requesting that the UE's connection be suspended to place the UE into an inactive state. The base station, in response to the message, suspends the RRC connection between the base station and the UE, for example, as... Figure 3The components discussed in Phase 5, used to send a message to a base station that has established a Radio Resource Control (RRC) connection with the UE (the message requests the UE to suspend the connection to place the UE into an inactive state, wherein the base station suspends the RRC connection between the base station and the UE in response to the message), may include, for example, an external interface 616 and one or more processors 602, which have dedicated hardware or implement executable code or software instructions in memory 604 and / or media 620 in location server 600, such as connection module 624, etc. Figure 6 As shown.

[0177] In box 906, after the UE performs location measurements to obtain location information and restores its RRC connection with the base station, the location server receives location information from the UE, for example, such as... Figure 3 The components discussed in phase 11. For receiving location information from the UE after the UE performs location measurements to obtain location information and restores the RRC connection with the base station, the components may include, for example, an external interface 616 and one or more processors 602, which have dedicated hardware or implement executable code or software instructions in memory 604 and / or media 620 in the location server 600, such as a location session module 622, etc. Figure 6 As shown.

[0178] In one implementation, the message to the base station requesting connection suspension may include a suggestion to suspend the RRC connection with the UE, for example, such as Figure 3 This is discussed in stage 5. In one implementation, the message to the base station requesting a connection suspension includes an indication of the duration during which location-related messages between the UE and the location server are not expected, for example, such as... Figure 3 This is discussed in Phase 5. For example, the duration of unexpected location-related messages between the UE and the location server could be the time during which the UE performs location measurements. For example, the duration of unexpected location-related messages between the UE and the location server could be based on a measurement period. For example, location-related messages between the UE and the location server that are not expected during the duration could include location measurement messages from the UE. In one example, location-related messages between the UE and the location server that are not expected during the duration could be location-related requests to the UE. In one implementation, the base station suspends the RRC connection between the base station and the UE based on an indication of the duration, for example, as... Figure 3 The sixth stage is discussed.

[0179] In one implementation, the UE transitions from a connected state to an inactive state in response to the base station suspending the RRC connection between the base station and the UE. While in the inactive state, the UE stores a UE connection context, and the base station also stores a UE connection context. Furthermore, the UE connection context is used to restore the RRC connection between the UE and the base station, for example, as... Figure 3 The sixth stage is discussed.

[0180] Figure 10 This demonstrates a method consistent with the disclosed implementation, whereby the base station (such as...) Figure 1 The gNB 110 shown performs functions to support user equipment (UE) (such as...) Figure 1 The flowchart shows an exemplary method 1000 for location services of UE 102.

[0181] In box 1002, the base station sends a message to the UE to establish a Radio Resource Control (RRC) connection with the UE, for example, as Figure 3 The components discussed in Phase 2 may include, for example, a radio transceiver 710 or a communication interface 716 and one or more processors 702, which have dedicated hardware or implement executable code or software instructions in the memory 704 and / or medium 720 in the base station 700, such as a connection module 722. Figure 7 As shown.

[0182] In box 1004, the base station receives a message from the location server while the UE is in a location session with the location server. This message requests a suspension of the RRC connection between the base station and the UE, for example, as... Figure 3 The components discussed in Phase 5, used to receive messages from a location server while the UE is in a location session with the location server (the messages requesting a connection suspension between the base station and the UE), may include, for example, a wireless transceiver 710 or a communication interface 716 and one or more processors 702, which have dedicated hardware or implement executable code or software instructions in the memory 704 and / or medium 720 in the base station 700, such as a connection module 722, etc. Figure 7 As shown.

[0183] In box 1006, the base station determines to release the RRC connection based at least in part on a message requesting connection suspension from the location server, for example, as... Figure 3The components discussed in stage 6, used to determine the release of an RRC connection based at least in part on a message requesting connection suspension from a location server, may include, for example, a wireless transceiver 710 or a communication interface 716 and one or more processors 702, which have dedicated hardware or implement executable code or software instructions in memory 704 and / or media 720 in base station 700, such as connection module 722, etc. Figure 7 As shown.

[0184] In box 1008, the base station sends a connection suspension message to the UE to put the UE into an inactive state. While in an inactive state, the UE performs location measurements to obtain location information and sends location information to a location server while in a connected state, for example... Figure 3 The components discussed in stages 6, 8, and 11, for sending a connection suspension message to the UE to place the UE into an inactive state (wherein the UE performs location measurements to obtain location information when inactive and sends location information to a location server when connected), may include, for example, a wireless transceiver 710 or a communication interface 716 and one or more processors 702 having dedicated hardware or implementing executable code or software instructions in memory 704 and / or media 720 in base station 700, such as connection module 722, etc. Figure 7 As shown.

[0185] In one implementation, the base station determines the data activity scheduled by the UE when the UE performs location measurements, wherein determining to release the RRC connection also responds to the data activity, for example, such as Figure 3 The components discussed in Phase 6. Components used to determine data activities scheduled for the UE during location measurements (where determining to release the RRC connection also responds to the data activity) may include, for example, a radio transceiver 710 or communication interface 716 and one or more processors 702 having dedicated hardware or implementing executable code or software instructions in memory 704 and / or media 720 in base station 700, such as connection module 722, etc. Figure 7 As shown.

[0186] In one implementation, the message requesting connection suspension from the location server includes a suggestion to suspend the RRC connection with the UE, for example, such as Figure 3 This is discussed in Phase 5. For example, a message requesting connection suspension from the location server may include an indication of the duration during which location-related messages between the UE and the location server are not expected, such as... Figure 3This is discussed in Phase 5. For example, the duration of unexpected location-related messages between the UE and the location server could be the time during which the UE performs location measurements. For example, the duration of unexpected location-related messages between the UE and the location server could be based on a measurement period. In one implementation, unexpected location-related messages between the UE and the location server during the duration could include location measurement messages from the UE. For example, unexpected location-related messages between the UE and the location server during the duration could be location-related requests from the location server. In one implementation, the base station could determine to release the RRC connection at least in part based on an indication of the duration, for example, as... Figure 3 The sixth stage is discussed.

[0187] In one implementation, when the UE is ready to send location information to the location server, the base station can receive a connection resumption request message from the UE, for example, such as... Figure 3 The components discussed in stage 9, used to receive a connection restoration request message from the UE when the UE is ready to send location information to the location server, may include, for example, a wireless transceiver 710 or a communication interface 716 and one or more processors 702, which have dedicated hardware or implement executable code or software instructions in the memory 704 and / or medium 720 in the base station 700, such as a connection module 722, etc. Figure 7 As shown. The base station can respond to a connection restoration request message by sending a connection restoration response message to the UE, wherein the UE transitions from an inactive state to a connected state and sends location information to a location server, for example, as... Figure 3 The components discussed in phase 10, for sending a connection restoration response message to the UE in response to a connection restoration request message (where the UE transitions from an inactive state to a connected state and sends location information to a location server), may include, for example, a wireless transceiver 710 or a communication interface 716 and one or more processors 702, which have dedicated hardware or implement executable code or software instructions in the memory 704 and / or medium 720 in the base station 700, such as a connection module 722, etc. Figure 7 As shown.

[0188] In one implementation, the base station can store the UE connection context when the UE is inactive, wherein the UE stores the UE connection context when the UE is inactive; and restore the RRC connection with the UE based on the UE connection context, for example, as... Figure 3The components discussed in stages 6, 9, and 10, for storing the UE connection context when the UE is inactive and for restoring the RRC connection with the UE based on the UE connection context, may include, for example, a wireless transceiver 710 or a communication interface 716 and one or more processors 702, which have dedicated hardware or implement executable code or software instructions in the memory 704 and / or medium 720 in the base station 700, such as a connection module 722, etc. Figure 7 As shown.

[0189] In one implementation, when the UE is in a high mobility state, the base station releases the RRC connection between the base station and the UE to put the UE into an idle state, and when the UE is in a low mobility state, the RRC connection between the base station and the UE is suspended to put the UE into an inactive state, for example, as... Figure 3 The stages discussed in phases 5 and 6.

[0190] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout this specification can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0191] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, circuits, and algorithmic steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally according to their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art may implement the described functionality in different ways for each specific application; however, such implementation decisions should not be construed as departing from the scope of this disclosure.

[0192] The various illustrative logic blocks, modules, and circuits disclosed herein can be implemented or executed using a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0193] The methods, sequences, and / or algorithms described in conjunction with the aspects disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or a combination of both. The software module can reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor such that the processor can read information from and write information to the storage medium. Alternatively, the storage medium can be a component of the processor. The processor and storage medium can reside in an ASIC. The ASIC can reside in a user terminal (e.g., a UE). Alternatively, the processor and storage medium can reside as discrete components in the user terminal.

[0194] In one or more exemplary aspects, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored as one or more instructions or code on or transmitted thereon on a computer-readable medium. A computer-readable medium includes computer storage media and communication media, which includes any medium that facilitates the transfer of a computer program from one place to another. A storage medium may be any available medium accessible to a computer. By way of example and not limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, disk storage devices or other magnetic storage devices, or any other medium that may be used to carry or store the required program code in the form of instructions or data structures, and is accessible to a computer. Furthermore, any connection is appropriately referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used in this article, disks and optical discs include compact discs (CDs), laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs, where disks typically copy data magnetically, while optical discs copy data optically using lasers. The combinations described above should also be included within the scope of computer-readable media.

[0195] Based on this description, embodiments may include different combinations of features. Examples of implementations are described in the following numbered clauses:

[0196] Clause 1. A method performed by a user equipment (UE) to support location services for the UE, comprising: sending a message to a base station to establish a radio resource control (RRC) connection with the base station; receiving a message for a location session from a location server; receiving a connection suspension message from the base station to place the UE into an inactive state, wherein the connection suspension message is initiated by the location server; performing location measurements to obtain location information while in an inactive state; and sending the location information to the location server while in a connected state.

[0197] Clause 2. The method according to Clause 1 further includes: sending a connection restoration request message to the base station when location information is to be sent to the location server; and receiving a connection restoration response message from the base station in response to the connection restoration request message to transition from an inactive state to a connected state.

[0198] Clause 3. The method according to any one of Clauses 1 to 2, wherein the location server determines the time for performing the location measurement and initiates a connection pause message based at least in part on the time for performing the location measurement.

[0199] Clause 4. The method according to any one of Clauses 1 to 3, wherein the location server initiates a connection suspension message by providing an indication of duration to the base station, during which no location-related messages between the UE and the location server are expected.

[0200] Clause 5. The method described in Clause 4, wherein the duration of location-related messages between the UE and the location server is not expected to include the time during which the UE performs location measurements.

[0201] Clause 6. The method according to any one of Clauses 4 to 5, wherein the duration of location-related messages between the UE and the location server is not expected to be based on a measurement period.

[0202] Clause 7. The method according to any one of Clauses 4 to 6, wherein location-related messages between the UE and the location server that are not expected during the duration include location measurement messages to the location server.

[0203] Clause 8. The method according to any one of Clauses 4 to 7, wherein the base station sends a connection suspension message based on an indication of duration.

[0204] Clause 9. The method according to any one of Clauses 1 to 8 further includes: storing the UE connection context when inactive, wherein the base station stores the UE connection context when the UE is inactive; and restoring the RRC connection with the base station based on the UE connection context.

[0205] Clause 10. A user equipment (UE) configured to support location services for a UE, comprising: a radio transceiver configured to wirelessly communicate with an entity in a wireless network; at least one memory; and at least one processor coupled to the radio transceiver and the memory, wherein the at least one processor is configured to: transmit a message to a base station via the radio transceiver to establish a radio resource control (RRC) connection with the base station; receive a message for a location session from a location server via the radio transceiver; receive a connection suspension message from the base station via the radio transceiver to place the UE into an inactive state, wherein the connection suspension message is initiated by the location server; perform location measurements to obtain location information when in an inactive state; and transmit location information to the location server when in a connected state.

[0206] Clause 11. The UE according to Clause 10, wherein at least one processor is further configured to: send a connection restoration request message to a base station via a radio transceiver when location information is to be sent to a location server; and receive a connection restoration response message from the base station via a radio transceiver in response to the connection restoration request message to transition from an inactive state to a connected state.

[0207] Clause 12. The UE according to any one of Clauses 10 to 11, wherein the location server determines the time for performing the location measurement and initiates a connection suspension message based at least in part on the time for performing the location measurement.

[0208] Clause 13. The UE pursuant to any one of Clauses 10 to 12, wherein the location server initiates a connection suspension message by providing an indication of duration to the base station, during which no location-related messages between the UE and the location server are expected.

[0209] Clause 14. The UE as described in Clause 13, wherein the duration of location-related messages between the UE and the location server is not expected to include the time during which the UE performs location measurements.

[0210] Clause 15. The UE pursuant to any one of Clauses 13 to 14, wherein the duration of location-related messages between the UE and the location server is not expected to be based on a measurement period.

[0211] Clause 16. The UE according to any one of Clauses 13 to 15, wherein location-related messages between the UE and the location server that are not expected during the duration include location measurement messages to the location server.

[0212] Clause 17. The UE pursuant to any one of Clauses 13 to 16, wherein the base station sends a connection suspension message based on an indication of duration.

[0213] Clause 18. The UE according to any one of Clauses 10 to 17, wherein at least one processor is further configured to: store the UE connection context when inactive, wherein the base station stores the UE connection context when the UE is inactive; and restore the RRC connection with the base station based on the UE connection context.

[0214] Clause 19. A user equipment (UE) configured to support location services for a UE, comprising: means for sending a message to a base station to establish a radio resource control (RRC) connection with the base station; means for receiving a message for a location session from a location server; means for receiving a connection suspension message from the base station to place the UE in an inactive state, wherein the connection suspension message is initiated by the location server; means for performing location measurements to obtain location information when in an inactive state; and means for sending location information to the location server when in a connected state.

[0215] Clause 20. The UE as described in Clause 19 further includes: a component for sending a connection restoration request message to a base station when location information is to be sent to a location server; and a component for receiving a connection restoration response message from the base station in response to the connection restoration request message to transition from an inactive state to a connected state.

[0216] Clause 21. The UE according to any one of Clauses 19 to 20, wherein the location server determines the time for performing the location measurement and initiates a connection suspension message based at least in part on the time for performing the location measurement.

[0217] Clause 22. The UE pursuant to any one of Clauses 19 to 21, wherein the location server initiates a connection suspension message by providing an indication of duration to the base station, during which no location-related messages between the UE and the location server are expected.

[0218] Clause 23. The UE as described in Clause 22, wherein the duration of location-related messages between the UE and the location server is not expected to include the time during which the UE performs location measurements.

[0219] Clause 24. The UE pursuant to any one of Clauses 22 to 23, wherein the duration of location-related messages between the UE and the location server is not expected to be based on a measurement period.

[0220] Clause 25. The UE according to any one of Clauses 22 to 24, wherein location-related messages between the UE and the location server that are not expected during the duration include location measurement messages to the location server.

[0221] Clause 26. The UE pursuant to any one of Clauses 22 to 25, wherein the base station sends a connection suspension message based on an indication of duration.

[0222] Clause 27. The UE according to any one of Clauses 19 to 26 further includes: a component for storing the UE connection context when in an inactive state, wherein the base station stores the UE connection context when the UE is inactive; and a component for resuming the RRC connection with the base station based on the UE connection context.

[0223] Clause 28. A non-transitory storage medium including program code stored thereon, the program code being operable for configuring at least one processor in a user equipment (UE) to support location services for the UE, the program code including instructions for: sending a message to a base station to establish a radio resource control (RRC) connection with the base station; receiving a message from a location server for a location session; receiving a connection suspension message from the base station to place the UE in an inactive state, wherein the connection suspension message is initiated by the location server; performing location measurements to obtain location information while in an inactive state; and sending location information to the location server while in a connected state.

[0224] Clause 29. The non-transitory storage medium as described in Clause 28, wherein the program code further includes instructions for: sending a connection restoration request message to a base station when location information is to be sent to a location server; and receiving a connection restoration response message from the base station in response to the connection restoration request message to transition from an inactive state to a connected state.

[0225] Clause 30. The non-transitory storage medium according to any one of Clauses 28 to 29, wherein the location server determines the time for performing the location measurement and initiates a connection suspension message based at least in part on the time for performing the location measurement.

[0226] Clause 31. The non-transitory storage medium according to any one of Clauses 28 to 30, wherein the location server initiates a connection suspension message by providing an indication of duration to the base station, during which no location-related messages between the UE and the location server are expected.

[0227] Clause 32. The non-transitory storage medium as described in Clause 31, wherein the duration of location-related messages between the UE and the location server is not expected to include the time during which the UE performs location measurements.

[0228] Clause 33. The non-transitory storage medium according to any one of Clauses 31 to 32, wherein the duration of location-related messages between the UE and the location server is not expected to be based on a measurement period.

[0229] Clause 34. The non-transitory storage medium according to any one of Clauses 31 to 33, wherein location-related messages between the UE and the location server that are not expected during the duration include location measurement messages to the location server.

[0230] Clause 35. A non-transitory storage medium pursuant to any one of Clauses 31 to 34, wherein the base station sends a connection suspension message based on an indication of duration.

[0231] Clause 36. The non-transitory storage medium according to any one of Clauses 28 to 35, wherein the program code further includes instructions for: storing the UE connection context when inactive, wherein the base station stores the UE connection context when the UE is inactive; and restoring the RRC connection with the base station based on the UE connection context.

[0232] Clause 37. A method performed by a location server to support location services for a user equipment (UE), comprising: sending a message to the UE for a location session; sending a message to a base station with which the UE has established a radio resource control (RRC) connection, the message requesting the UE to suspend the connection to place the UE into an inactive state, wherein the base station suspends the RRC connection between the base station and the UE in response to the message; and receiving the location information from the UE after the UE performs location measurements to obtain location information and restores the RRC connection with the base station.

[0233] Clause 38. The method according to Clause 37, wherein the message to the base station for requesting connection suspension includes a proposal to suspend the RRC connection with the UE.

[0234] Clause 39. The method according to any one of Clauses 37 to 38, wherein the message to the base station for requesting connection suspension includes an indication of duration during which location-related messages between the UE and the location server are not expected.

[0235] Clause 40. The method according to Clause 39, wherein the duration of the location-related messages between the UE and the location server is not expected to include the time during which the UE performs location measurements.

[0236] Clause 41. The method according to any one of Clauses 39 to 40, wherein the duration of location-related messages between the UE and the location server is not expected to be based on a measurement period.

[0237] Clause 42. The method according to any one of Clauses 39 to 41, wherein location-related messages between the UE and the location server that are not expected during the duration include location measurement messages from the UE.

[0238] Clause 43. The method according to any one of Clauses 39 to 42, wherein location-related messages between the UE and the location server that are not expected during the duration include location-related requests to the UE.

[0239] Clause 44. The method according to any one of Clauses 39 to 43, wherein the base station suspends the RRC connection between the base station and the UE based on a duration indication.

[0240] Clause 45. The method according to any one of Clauses 37 to 44, wherein the UE transitions from a connected state to an inactive state in response to the base station suspending the RRC connection between the base station and the UE, wherein the UE stores a UE connection context while in the inactive state, and the base station stores the UE connection context, and wherein the UE connection context is used to restore the RRC connection between the UE and the base station.

[0241] Clause 46. A location server configured to support location services for a user equipment (UE), comprising: an external interface configured to communicate with one or more base stations and one or more UEs; at least one memory; and at least one processor coupled to the external interface and the memory, wherein the at least one processor is configured to: send a message for a location session to the UE via the external interface; send a message via the external interface to a base station with which the UE has established a radio resource control (RRC) connection, the message requesting the UE to suspend its connection to place the UE in an inactive state, wherein the base station suspends the RRC connection between the base station and the UE in response to the message; and receive location information from the UE via the external interface after the UE performs location measurements to obtain location information and restores its RRC connection with the base station.

[0242] Clause 47. The location server as described in Clause 46, wherein the message to the base station for requesting connection suspension includes a suggestion to suspend the RRC connection with the UE.

[0243] Clause 48. A location server according to any one of Clauses 46 to 47, wherein the message to the base station for requesting a connection suspension includes an indication of a duration during which location-related messages between the UE and the location server are not expected.

[0244] Clause 49. The location server as described in Clause 48, wherein the duration of location-related messages between the UE and the location server is not expected to include the time during which the UE performs location measurements.

[0245] Clause 50. A location server pursuant to any one of Clauses 48 to 49, wherein the duration of location-related messages between the UE and the location server is not expected to be based on a measurement period.

[0246] Clause 51. A location server according to any one of Clauses 48 to 50, wherein location-related messages between the UE and the location server that are not expected during the duration include location measurement messages from the UE.

[0247] Clause 52. A location server according to any one of Clauses 48 to 51, wherein location-related messages between the UE and the location server that are not expected during the duration include location-related requests to the UE.

[0248] Clause 53. A location server pursuant to any one of Clauses 48 to 52, wherein the base station suspends the RRC connection between the base station and the UE based on a duration indication.

[0249] Clause 54. A location server according to any one of Clauses 46 to 53, wherein the UE transitions from a connected state to an inactive state in response to the base station suspending the RRC connection between the base station and the UE, wherein the UE stores a UE connection context while in the inactive state, and the base station stores the UE connection context, and wherein the UE connection context is used to restore the RRC connection between the UE and the base station.

[0250] Clause 55. A location server configured to support location services for a user equipment (UE), comprising: components for sending a message to the UE for a location session; components for sending a message to a base station with which the UE has established a radio resource control (RRC) connection, the message requesting the UE to suspend the connection to place the UE into an inactive state, wherein the base station suspends the RRC connection between the base station and the UE in response to the message; and components for receiving location information from the UE after the UE performs location measurements to obtain location information and resumes the RRC connection with the base station.

[0251] Clause 56. The location server as described in Clause 55, wherein the message to the base station for requesting connection suspension includes a suggestion to suspend the RRC connection with the UE.

[0252] Clause 57. A location server according to any one of Clauses 55 to 56, wherein the message to the base station for requesting a connection suspension includes an indication of a duration during which location-related messages between the UE and the location server are not expected.

[0253] Clause 58. The location server as described in Clause 57, wherein the duration of location-related messages between the UE and the location server is not expected to include the time during which the UE performs location measurements.

[0254] Clause 59. A location server pursuant to any one of Clauses 57 to 58, wherein the duration of location-related messages between the UE and the location server is not expected to be based on a measurement period.

[0255] Clause 60. A location server according to any one of Clauses 57 to 59, wherein location-related messages between the UE and the location server that are not expected during the duration include location measurement messages from the UE.

[0256] Clause 61. A location server according to any one of Clauses 57 to 60, wherein location-related messages between the UE and the location server that are not expected during the duration include location-related requests to the UE.

[0257] Clause 62. A location server pursuant to any one of Clauses 57 to 61, wherein the base station suspends the RRC connection between the base station and the UE based on a duration indication.

[0258] Clause 63. A location server according to any one of Clauses 55 to 62, wherein the UE transitions from a connected state to an inactive state in response to the base station suspending the RRC connection between the base station and the UE, wherein the UE stores a UE connection context while in the inactive state, and the base station stores the UE connection context, and wherein the UE connection context is used to restore the RRC connection between the UE and the base station.

[0259] Clause 64. A non-transitory storage medium including program code stored thereon, the program code being operable for configuring at least one processor in a location server to support location services for a user equipment (UE), the program code including instructions for: sending a message to the UE for a location session; sending a message to a base station with which the UE has established a radio resource control (RRC) connection, the message requesting the UE to suspend the connection to place the UE into an inactive state, wherein the base station suspends the RRC connection between the base station and the UE in response to the message; and receiving location information from the UE after the UE performs location measurements to obtain location information and restores the RRC connection with the base station.

[0260] Clause 65. The non-transitory storage medium as described in Clause 64, wherein the message to the base station for requesting connection suspension includes a proposal to suspend the RRC connection with the UE.

[0261] Clause 66. The non-transitory storage medium according to any one of Clauses 64 to 65, wherein the message to the base station for requesting a connection suspension includes an indication of a duration during which location-related messages between the UE and the location server are not expected.

[0262] Clause 67. The non-transitory storage medium as described in Clause 66, wherein the duration of location-related messages between the UE and the location server is not expected to include the time during which the UE performs location measurements.

[0263] Clause 68. The non-transitory storage medium pursuant to any one of Clauses 66 to 67, wherein the duration of location-related messages between the UE and the location server is not expected to be based on a measurement period.

[0264] Clause 69. The non-transitory storage medium according to any one of Clauses 66 to 68, wherein location-related messages between the UE and the location server that are not expected during the duration include location measurement messages from the UE.

[0265] Clause 70. The non-transitory storage medium according to any one of Clauses 66 to 69, wherein location-related messages between the UE and the location server that are not expected during the duration include location-related requests to the UE.

[0266] Clause 71. A non-transitory storage medium pursuant to any one of Clauses 66 to 70, wherein the base station suspends the RRC connection between the base station and the UE based on a duration indication.

[0267] Clause 72. The non-transitory storage medium according to any one of Clauses 64 to 71, wherein the UE transitions from a connected state to an inactive state in response to the base station suspending the RRC connection between the base station and the UE, wherein the UE stores the UE connection context while in the inactive state, and the base station stores the UE connection context, and wherein the UE connection context is used to restore the RRC connection between the UE and the base station.

[0268] Clause 73. A method performed by a base station to support location services for a user equipment (UE), comprising: sending a message to the UE to establish a radio resource control (RRC) connection with the UE; receiving a message from a location server while the UE is in a location session with a location server, the message requesting a connection suspension of the RRC connection between the base station and the UE; determining whether to release the RRC connection based at least in part on the request for connection suspension message from the location server; and sending a connection suspension message to the UE to place the UE into an inactive state, wherein the UE performs location measurements to obtain location information while in an inactive state and sends the location information to the location server while in a connected state.

[0269] Clause 74. The method according to Clause 73 further includes determining data activity scheduled by the UE when the UE performs location measurements, wherein determining to release the RRC connection also responds to the data activity.

[0270] Clause 75. The method according to any one of Clauses 73 to 74, wherein the message requesting connection suspension from the location server includes a proposal to suspend the RRC connection with the UE.

[0271] Clause 76. The method according to any one of Clauses 73 to 75, wherein the message requesting connection suspension from the location server includes an indication of a duration during which no location-related messages between the UE and the location server are expected.

[0272] Clause 77. The method according to Clause 76, wherein the duration of the location-related messages between the UE and the location server is not expected to include the time during which the UE performs location measurements.

[0273] Clause 78. The method according to any one of Clauses 76 to 77, wherein the duration of location-related messages between the UE and the location server is not expected to be based on a measurement period.

[0274] Clause 79. The method according to any one of Clauses 76 to 78, wherein location-related messages between the UE and the location server that are not expected during the duration include location measurement messages from the UE.

[0275] Clause 80. The method according to any one of Clauses 76 to 79, wherein location-related messages between the UE and the location server that are not expected during the duration include location-related requests from the location server.

[0276] Clause 81. The method according to any one of Clauses 76 to 80, wherein determining the release of the RRC connection is based at least in part on an indication of duration.

[0277] Clause 82. The method according to any one of Clauses 73 to 81 further includes: receiving a connection restoration request message from the UE when the UE is ready to send location information to the location server; and sending a connection restoration response message to the UE in response to the connection restoration request message, wherein the UE transitions from an inactive state to a connected state and sends location information to the location server.

[0278] Clause 83. The method according to any one of Clauses 73 to 82 further includes: storing a UE connection context when the UE is inactive, wherein the UE stores the UE connection context when the UE is inactive; and restoring an RRC connection with the UE based on the UE connection context.

[0279] Clause 84. The method according to any one of Clauses 73 to 83, wherein the message requesting connection suspension from the location server further includes a suggestion to release the RRC connection based on the UE's mobility state to place the UE in an idle state.

[0280] Clause 85. The method according to Clause 84, wherein when the UE is in a high mobility state, the base station releases the RRC connection between the base station and the UE to place the UE in an idle state, and when the UE is in a low mobility state, the base station suspends the RRC connection between the base station and the UE to place the UE in an inactive state.

[0281] Clause 86. A base station configured to support location services for a user equipment (UE), comprising: an external interface configured to communicate with a location server in a wireless network and one or more UEs; at least one memory; and at least one processor coupled to the external interface and the memory, wherein the at least one processor is configured to: send a message to the UE via the external interface to establish a radio resource control (RRC) connection with the UE; receive a message from the location server via the external interface when the UE is in a location session with the location server, the message requesting a connection suspension of the RRC connection between the base station and the UE; determine, at least in part, to release the RRC connection based on the request for connection suspension message from the location server; and send a connection suspension message via the external interface to place the UE into an inactive state, wherein the UE performs location measurements to obtain location information when in an inactive state and sends location information to the location server when in a connected state.

[0282] Clause 87. The base station according to Clause 86, wherein at least one processor is further configured to determine data activity scheduled by the UE when the UE performs location measurements, wherein at least one processor is configured to further determine to release the RRC connection in response to the data activity.

[0283] Clause 88. A base station pursuant to any one of Clauses 86 to 87, wherein the message requesting connection suspension from the location server includes a suggestion to suspend the RRC connection with the UE.

[0284] Clause 89. A base station pursuant to any one of Clauses 86 to 88, wherein the message requesting connection suspension from the location server includes an indication of a duration during which no location-related messages between the UE and the location server are expected.

[0285] Clause 90. The base station as described in Clause 89, wherein the duration of location-related messages between the UE and the location server is not expected to include the time during which the UE performs location measurements.

[0286] Clause 91. A base station pursuant to any one of Clauses 89 to 90, wherein the duration of location-related messages between the UE and the location server is not expected to be based on a measurement period.

[0287] Clause 92. A base station according to any one of Clauses 89 to 91, wherein location-related messages between the UE and the location server that are not expected during the duration include location measurement messages from the UE.

[0288] Clause 93. A base station pursuant to any one of Clauses 89 to 92, wherein location-related messages between the UE and the location server that are not expected during the duration include location-related requests from the location server.

[0289] Clause 94. A base station pursuant to any one of Clauses 89 to 93, wherein determining the release of an RRC connection is based at least in part on an indication of duration.

[0290] Clause 95. A base station according to any one of Clauses 86 to 94, wherein at least one processor is further configured to: receive a connection restoration request message from the UE via an external interface when the UE is ready to send location information to the location server; and, in response to the connection restoration request message, send a connection restoration response message to the UE via the external interface, wherein the UE transitions from an inactive state to a connected state and sends location information to the location server.

[0291] Clause 96. A base station according to any one of Clauses 86 to 95, wherein at least one processor is further configured to: store a UE connection context when the UE is inactive, wherein the UE stores the UE connection context when the UE is inactive; and restore an RRC connection with the UE based on the UE connection context.

[0292] Clause 97. A base station pursuant to any one of Clauses 86 to 96, wherein the message requesting connection suspension from the location server further includes a suggestion to release the RRC connection based on the UE's mobility state to place the UE in an idle state.

[0293] Clause 98. The base station as described in Clause 97, wherein when the UE is in a high mobility state, the base station releases the RRC connection between the base station and the UE to place the UE in an idle state, and when the UE is in a low mobility state, the base station suspends the RRC connection between the base station and the UE to place the UE in an inactive state.

[0294] Clause 99. A base station for supporting location services for a user equipment (UE), comprising: means for sending a message to the UE to establish a radio resource control (RRC) connection with the UE; means for receiving a message from a location server when the UE is in a location session with a location server, the message requesting a connection suspension of the RRC connection between the base station and the UE; means for determining whether to release the RRC connection based at least in part on the message requesting connection suspension from the location server; and means for sending a connection suspension message to the UE to place the UE in an inactive state, wherein the UE performs location measurements to obtain location information when in an inactive state and sends location information to the location server when in a connected state.

[0295] Clause 100. The base station according to Clause 99 further includes components for determining data activity scheduled for the UE when the UE performs location measurements, wherein the components for determining the release of the RRC connection also determine the release of the RRC connection in response to the data activity.

[0296] Clause 101. A base station pursuant to any one of Clauses 99 to 100, wherein the message requesting connection suspension from the location server includes a suggestion to suspend the RRC connection with the UE.

[0297] Clause 102. A base station pursuant to any one of Clauses 99 to 101, wherein the message requesting connection suspension from the location server includes an indication of a duration during which no location-related messages between the UE and the location server are expected.

[0298] Clause 103. The base station as described in Clause 102, wherein the duration of location-related messages between the UE and the location server is not expected to include the time during which the UE performs location measurements.

[0299] Clause 104. A base station pursuant to any one of Clauses 102 to 103, wherein the duration of location-related messages between the UE and the location server is not expected to be based on a measurement period.

[0300] Clause 105. A base station according to any one of Clauses 102 to 104, wherein location-related messages between the UE and the location server that are not expected during the duration include location measurement messages from the UE.

[0301] Clause 106. A base station according to any one of Clauses 102 to 105, wherein location-related messages between the UE and the location server that are not expected during the duration include location-related requests from the location server.

[0302] Clause 107. A base station according to any one of Clauses 102 to 106, wherein the component for determining the release of the RRC connection determines the release of the RRC connection based at least in part on an indication of duration.

[0303] Clause 108. The base station according to any one of Clauses 99 to 107 further includes: a component for receiving a connection restoration request message from the UE when the UE is ready to send location information to the location server; and a component for sending a connection restoration response message to the UE in response to the connection restoration request message, wherein the UE transitions from an inactive state to a connected state and sends location information to the location server.

[0304] Clause 109. The base station according to any one of Clauses 99 to 108 further includes: a component for storing a UE connection context when the UE is inactive, wherein the UE stores the UE connection context when the UE is inactive; and a component for resuming an RRC connection with the UE based on the UE connection context.

[0305] Clause 110. A base station pursuant to any one of Clauses 99 to 109, wherein the message requesting connection suspension from the location server further includes a suggestion to release the RRC connection based on the UE's mobility state to place the UE in an idle state.

[0306] Clause 111. The base station as described in Clause 110, wherein when the UE is in a high mobility state, the base station releases the RRC connection between the base station and the UE to place the UE in an idle state, and when the UE is in a low mobility state, the base station suspends the RRC connection between the base station and the UE to place the UE in an inactive state.

[0307] Clause 112. A non-transitory storage medium including program code stored thereon, the program code being operable to configure at least one processor in a base station to support location services for a user equipment (UE), the program code including instructions for: sending a message to the UE to establish a radio resource control (RRC) connection with the UE; receiving a message from a location server while the UE is in a location session with a location server, the message requesting a connection suspension of the RRC connection between the base station and the UE; determining whether to release the RRC connection based at least in part on the message requesting connection suspension from the location server; and sending a connection suspension message to place the UE into an inactive state, wherein the UE performs location measurements to obtain location information while in an inactive state and sends the location information to the location server while in a connected state.

[0308] Clause 113. The base station as described in Clause 112, wherein the program code further includes instructions for determining data activity scheduled by the UE when the UE performs location measurements, wherein the program code further includes instructions for further determining to release the RRC connection in response to the data activity.

[0309] Clause 114. A base station pursuant to any one of Clauses 112 to 113, wherein the message requesting connection suspension from the location server includes a suggestion to suspend the RRC connection with the UE.

[0310] Clause 115. A base station pursuant to any one of Clauses 112 to 114, wherein the message requesting connection suspension from the location server includes an indication of a duration during which location-related messages between the UE and the location server are not expected.

[0311] Clause 116. The base station as described in Clause 115, wherein the duration of location-related messages between the UE and the location server is not expected to include the time during which the UE performs location measurements.

[0312] Clause 117. A base station pursuant to any one of Clauses 115 to 116, wherein the duration of location-related messages between the UE and the location server is not expected to be based on a measurement period.

[0313] Clause 118. A base station according to any one of Clauses 115 to 117, wherein location-related messages between the UE and the location server that are not expected during the duration include location measurement messages from the UE.

[0314] Clause 119. A base station pursuant to any one of Clauses 115 to 118, wherein location-related messages between the UE and the location server that are not expected during the duration include location-related requests from the location server.

[0315] Clause 120. A base station pursuant to any one of Clauses 115 to 119, wherein determining the release of an RRC connection is based at least in part on an indication of duration.

[0316] Clause 121. A base station according to any one of Clauses 112 to 120, wherein the program code further includes instructions for: receiving a connection restoration request message from the UE when the UE is ready to send location information to the location server; and sending a connection restoration response message to the UE in response to the connection restoration request message, wherein the UE transitions from an inactive state to a connected state and sends location information to the location server.

[0317] Clause 122. A base station according to any one of Clauses 112 to 121, wherein the program code further includes instructions for: storing a UE connection context when the UE is inactive, wherein the UE stores the UE connection context when the UE is inactive; and restoring an RRC connection with the UE based on the UE connection context.

[0318] Clause 123. A base station pursuant to any one of Clauses 112 to 122, wherein the message requesting connection suspension from the location server further includes a suggestion to release the RRC connection based on the UE's mobility state to place the UE in an idle state.

[0319] Clause 124. The base station as described in Clause 123, wherein when the UE is in a high mobility state, the base station releases the RRC connection between the base station and the UE to place the UE in an idle state, and when the UE is in a low mobility state, the base station suspends the RRC connection between the base station and the UE to place the UE in an inactive state.

[0320] While the foregoing disclosure illustrates illustrative aspects of this disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of this disclosure as defined by the appended claims. The functions, steps, and / or actions of the method claims according to the aspects of the disclosure described herein do not need to be performed in any particular order. Furthermore, although elements of this disclosure may be described or claimed in the singular, the plural form is contemplated unless expressly stated to be limited to the singular.

Claims

1. A method performed by a user equipment (UE) to support location services of the UE, comprising: The connection suspension message is received from the base station to place the UE in an inactive state while the UE is in a location session with a location server, wherein the base station has an established radio resource control (RRC) connection with the UE, and wherein the connection suspension message is initiated by the location server. Perform positioning measurements to obtain location information while in the inactive state; and When in a connected state, the location information is sent to the location server. The location server initiates the connection suspension message by providing the base station with an indication of the duration, during which no location-related messages between the UE and the location server are expected.

2. The method according to claim 1, further comprising: When the location information is to be sent to the location server, a connection restoration request message is sent to the base station; as well as In response to the connection restoration request message, a connection restoration response message is received from the base station to transition from the inactive state to the connected state.

3. The method according to claim 1, wherein, The location server determines the time to perform the location measurement and initiates the connection pause message based at least in part on the time of performing the location measurement.

4. The method according to claim 1, wherein, The duration of the location-related messages between the UE and the location server is not expected to include the time during which the UE performs the location measurement.

5. The method according to claim 1, wherein, The duration of the location-related messages between the UE and the location server is not expected to be based on a measurement period.

6. The method according to claim 1, wherein, The location-related messages between the UE and the location server that are not expected during the said duration include location measurement messages to the location server.

7. The method according to claim 1, wherein, The base station sends the connection pause message based on the indication of the duration.

8. The method according to claim 1, further comprising: The base station stores the UE connection context when the UE is in the inactive state; and The RRC connection with the base station is restored based on the UE connection context.

9. A user equipment (UE) configured to support location services of the UE, comprising: A wireless transceiver, configured to communicate wirelessly with entities in a wireless network; At least one memory; At least one processor coupled to the wireless transceiver and the at least one memory, wherein the at least one processor is configured to: The wireless transceiver sends a message to the base station to establish a radio resource control (RRC) connection with the base station; Receive messages for a location session from the location server via the wireless transceiver; The UE is placed in an inactive state by receiving a connection suspension message from the base station via the wireless transceiver, wherein the connection suspension message is initiated by the location server; Perform positioning measurements to obtain location information while in the inactive state; and When in a connected state, the location information is sent to the location server. The location server initiates the connection suspension message by providing the base station with an indication of the duration, during which no location-related messages between the UE and the location server are expected.

10. The UE according to claim 9, wherein, The at least one processor is further configured to: When the location information is to be sent to the location server, a connection restoration request message is sent to the base station via the wireless transceiver; and In response to the connection restoration request message, a connection restoration response message is received from the base station via the wireless transceiver to transition from the inactive state to the connected state.

11. The UE according to claim 9, wherein, The location server determines the time to perform the location measurement and initiates the connection pause message based at least in part on the time of performing the location measurement.

12. The UE according to claim 9, wherein, The duration of the location-related messages between the UE and the location server is not expected to include the time during which the UE performs the location measurement.

13. The UE according to claim 9, wherein, The duration of the location-related messages between the UE and the location server is not expected to be based on a measurement period.

14. The UE according to claim 9, wherein, The location-related messages between the UE and the location server that are not expected during the said duration include location measurement messages to the location server.

15. The UE according to claim 9, wherein, The base station sends the connection pause message based on the indication of the duration.

16. The UE according to claim 9, wherein, The at least one processor is further configured to: The base station stores the UE connection context when the UE is in the inactive state; and The RRC connection with the base station is restored based on the UE connection context.

17. A user equipment (UE) configured to support location services of the UE, comprising: Components used to send messages to a base station to establish a radio resource control (RRC) connection with the base station; A component used to receive messages for a location session from a location server; A component for receiving a connection suspension message from the base station to place the UE in an inactive state, wherein the connection suspension message is initiated by the location server; Components for performing positioning measurements to obtain location information when in the inactive state; and A component for sending the location information to the location server when in a connected state. The message to the base station requesting the connection to be suspended includes an indication of the duration during which location-related messages between the UE and the location server are not expected.

18. A method performed by a location server to support location services for a user equipment (UE), comprising: A message is sent to a base station that has established a Radio Resource Control (RRC) connection with the UE, the message requesting that the UE's connection be suspended to place the UE in an inactive state while the location server is in a location session with the UE, wherein the base station suspends the RRC connection between the base station and the UE in response to the message; and After the UE performs positioning measurements to obtain the location information and restores the RRC connection with the base station, the location information is received from the UE. The message to the base station requesting the connection to be suspended includes an indication of the duration during which location-related messages between the UE and the location server are not expected.

19. The method according to claim 18, wherein, The message to the base station requesting the connection suspension includes a suggestion to suspend the RRC connection with the UE.

20. The method according to claim 18, wherein, The duration of the location-related messages between the UE and the location server is not expected to include the time during which the UE performs the location measurement.

21. The method according to claim 18, wherein, The duration of the location-related messages between the UE and the location server is not expected to be based on a measurement period.

22. The method according to claim 18, wherein, The location-related messages between the UE and the location server that are not expected during the said duration include location measurement messages from the UE.

23. The method according to claim 18, wherein, Location-related messages between the UE and the location server that are not expected during the said duration include location-related requests to the UE.

24. The method according to claim 18, wherein, The base station suspends the RRC connection between the base station and the UE based on the indication of the duration.

25. The method according to claim 18, wherein, The UE transitions from a connected state to an inactive state in response to the base station suspending the RRC connection between the base station and the UE. The UE stores a UE connection context while in the inactive state, and the base station stores the UE connection context. The UE connection context is used to restore the RRC connection between the UE and the base station.

26. A method performed by a base station to support location services for a user equipment (UE), comprising: When the UE is in a location session with the location server, it receives a message from the location server requesting the suspension of the radio resource control (RRC) connection between the base station and the UE. Whether to release the RRC connection is determined at least in part based on the message from the location server requesting the connection to be suspended; as well as In response to determining that the RRC connection is to be released, a connection pause message is sent to the UE to place the UE into an inactive state, wherein the UE performs location measurements to obtain location information while in the inactive state and sends the location information to the location server while in a connected state. The message from the location server requesting the connection to be suspended includes an indication of the duration during which location-related messages between the UE and the location server are not expected.

27. The method of claim 26, further comprising data activities determined to be scheduled by the UE when the UE performs positioning measurements, wherein, Determining to release the RRC connection also responds to the data activity.

28. The method according to claim 26, wherein, The message from the location server requesting the connection to be suspended includes a suggestion to suspend the RRC connection with the UE.

29. The method according to claim 26, wherein, The duration of the location-related messages between the UE and the location server is not expected to include the time during which the UE performs the location measurement.

30. The method according to claim 26, wherein, The duration of the location-related messages between the UE and the location server is not expected to be based on a measurement period.

31. The method according to claim 26, wherein, The location-related messages between the UE and the location server that are not expected during the said duration include location measurement messages from the UE.

32. The method according to claim 26, wherein, Location-related messages between the UE and the location server that are not expected during the said duration include location-related requests from the location server.

33. The method according to claim 26, wherein, The decision to release the RRC connection is based at least in part on the indication of the duration.

34. The method of claim 26, further comprising: When the UE is ready to send the location information to the location server, a connection restoration request message is received from the UE. as well as In response to the connection restoration request message, a connection restoration response message is sent to the UE, wherein the UE transitions from the inactive state to the connected state and sends the location information to the location server.

35. The method of claim 26, further comprising: The UE connection context is stored when the UE is in the inactive state, wherein the UE stores the UE connection context when the UE is in the inactive state; and The RRC connection with the UE is restored based on the UE connection context.

36. The method according to claim 26, wherein, The message from the location server requesting the connection to be suspended also includes a suggestion to release the RRC connection based on the UE's mobility state to put the UE into an idle state.

37. The method of claim 36, wherein, When the UE is in a high mobility state, the base station releases the RRC connection between the base station and the UE to place the UE in the idle state, and when the UE is in a low mobility state, the base station suspends the RRC connection between the base station and the UE to place the UE in the inactive state.

Images