Patent Description:
As an example, it may be useful or necessary to locate a UE that has access to a Fifth Generation (<NUM>) New Radio (NR) network. However, there may be problems or limitations when a UE or SUPL Location Platform (SLP) does not support location of the UE according to a standard SUPL solution for <NUM> wireless access. Means to overcome such problems or limitations may thus be useful. Attention is drawn to document <NPL>. Further attention is drawn to document <NPL>. Attention is also drawn to document "UserPlane Location Protocol"; <NPL>.

Further embodiments of the invention are defined in the appended dependent claims. Parts of the description and drawings referring to embodiments which are not covered by the claims are not present as embodiments of the invention but as background examples useful for understanding the invention. Techniques described herein address these and other issues by providing means by which usable cell information may be conveyed over a <NUM> NR data connection using a SUPL message with a Long-Term Evolution (LTE) cell ID data field. In some embodiments, for example, the UE may include the Cell ID of an LTE neighbor cell or information regarding the <NUM> NR serving cell, such as a portion of the <NUM> NR Cell ID or a reserved value or sequence identifying the <NUM> NR serving cell. An example method at a UE of supporting location of the UE using a SUPL session over a <NUM> NR data connection, according to the description, comprises establishing the <NUM> NR data connection between the UE and a SUPL Location Platform (SLP), determining cell data, wherein the cell data comprises information regarding a <NUM> NR serving cell of the UE, or a Long-Term Evolution (LTE) neighbor cell, or a combination thereof. The method further comprises sending a SUPL message to the SLP as part of the SUPL session, wherein the SUPL message comprises a Location ID (LID) parameter having a Long-Term Evolution (LTE) Cell Information data field, and wherein the cell data is included in the LTE Cell Information data field.

An example method at an SLP of supporting location of a UE using a SUPL session over a <NUM> NR data connection, according to the description, comprises establishing the <NUM> NR data connection between the SLP and the UE, and receiving a SUPL message from the UE as part of the SUPL session, wherein the SUPL message comprises a Location ID (LID) parameter having a Long-Term Evolution (LTE) Cell Information data field, wherein the cell data is included in the LTE Cell Information data field, and the cell data comprises information regarding a <NUM> NR serving cell of the UE, or an LTE neighbor cell, or a combination thereof. The method further comprises determining a location of the UE based at least in part on the cell data.

An example UE, according to the description, comprises a communication interface, a memory, and one or more processing units communicatively coupled with the memory and the communication interface. The one or more processing units are further configured to establish, using the communication interface, a <NUM> NR data connection between the UE and an SLP, and determine cell data, wherein the cell data comprises information regarding a <NUM> NR serving cell of the UE, or a Long-Term Evolution (LTE) neighbor cell, or a combination thereof. The one or more processing units are further configured to send, using the communication interface, a SUPL message to the SLP as part of a SUPL session, wherein the SUPL message comprising a Location ID (LID) parameter having a Long-Term Evolution (LTE) Cell Information data field, wherein the cell data is included in the LTE Cell Information data field.

An example SLP, according to the description, comprises a communication interface, a memory, and one or more processing units communicatively coupled with the communication interface and the memory. The one or more processing units are configured to establish, using the communication interface, a <NUM> NR data connection between the SLP and a UE, and receive, using the communication interface, a SUPL message from the UE as part of a SUPL session, the SUPL message comprising a Location ID (LID) parameter having an LTE Cell Information data field, wherein cell data is included in the LTE Cell Information data field, and the cell data comprises information regarding a <NUM> NR serving cell of the UE, or an LTE neighbor cell, or a combination thereof. The one or more processing units are further configured to determine a location of the UE based at least in.

An example mobile device, according to the description, comprises means for establishing a <NUM> NR data connection between the mobile device and an SLP, and means for determining cell data, wherein the cell data comprises information regarding a <NUM> NR serving cell of the mobile device, or a Long-Term Evolution (LTE) neighbor cell, or a combination thereof. The mobile device further comprises means for sending a SUPL message to the SLP as part of the SUPL session, wherein the SUPL message comprises a Location ID (LID) parameter having a Long-Term Evolution (LTE) Cell Information data field, wherein the cell data is included in the LTE Cell Information data field.

An example computer server, according to the description, comprises means for establishing a <NUM> NR data connection between the computer server and a UE, and means for receiving a Secure User Plane Location (SUPL) message from the UE as part of a SUPL session, wherein the SUPL message comprises a Location ID (LID) parameter having a LTE Cell Information data field, wherein cell data is included in the LTE Cell Information data field, and the cell data comprises information regarding a <NUM> NR serving cell of the UE or an LTE neighbor cell. The computer server further comprises means for determining a location of the UE based at least in part on the cell data.

An example non-transitory computer-readable medium, according to the description, has instructions embedded thereon for supporting location of a UE using a SUPL session over a <NUM> NR data connection. The instructions, when executed by one or more processing units of the UE, cause the UE to establish the <NUM> NR data connection between the UE and a SLP, and determine cell data, wherein the cell data comprises information regarding a <NUM> NR serving cell of the UE, or a Long-Term Evolution (LTE) neighbor cell, or a combination thereof. The instructions, when executed by one or more processing units of the UE, further cause the UE to send a SUPL message to the SLP as part of the SUPL session, the SUPL message comprising a Location ID (LID) parameter having an LTE Cell Information data field, wherein the cell data is included in the LTE Cell Information data field.

Another example non-transitory computer-readable medium, according to the description, has instructions embedded thereon for supporting location of a UE using a SUPL session over a <NUM> NR data connection. The instructions, when executed by one or more processing units of an SLP, cause the SLP to establish the <NUM> NR data connection between the SLP and the UE, and receive a SUPL message from the UE as part of the SUPL session, wherein the SUPL message comprises a Location ID (LID) parameter having a Long-Term Evolution (LTE) Cell Information data field. The cell data is included in the LTE Cell Information data field, and the cell data comprises information regarding a <NUM> NR serving cell of the UE or an LTE neighbor cell. The instructions, when executed by the one or more processing units of an SLP, further cause the SLP to determine a location of the UE based at least in part on the cell data.

Several illustrative embodiments are described with respect to the accompanying drawings, which form a part hereof. While particular embodiments, in which one or more aspects of the disclosure may be implemented, are described below, other embodiments may be used and various modifications may be made without departing from the scope of the disclosure.

When a <NUM> NR network is used to support a SUPL location session between a UE and an SLP, problems may arise in the case that standards-based SUPL support for <NUM> location (e.g. according to a latest standard for SUPL <NUM> published by the Open Mobile Alliance (OMA)) is not implemented by the UE or SLP. As an example, a UE may not be able to send information to an SLP identifying a current <NUM> serving cell for the UE or providing location measurements for the <NUM> serving cell or neighboring <NUM> cells. This may prevent an SLP from obtaining a coarse location estimate for the UE, which may in turn make a more accurate location estimate difficult or impossible to obtain. Techniques provided herein can overcome these issues by providing means by which usable cell information for <NUM> NR may be conveyed over a <NUM> NR data connection using a SUPL message with a cell ID data field applicable to Fourth Generation (<NUM>) Long Term Evolution (LTE).

As referred to herein, the terms "New Radio," "Fifth Generation New Radio," "<NUM> NR," and derivatives thereof refer to <NUM> technology as implemented in specifications for the Third Generation Partnership Project (3GPP). As a person of ordinary skill in the art would appreciate, various <NUM> technology standards are defined and revised by 3GPP.

<FIG> shows a diagram of an embodiment of a communication system <NUM> that may implement the techniques described herein for supporting a SUPL session (also referred to herein as a SUPL location session) over a <NUM> NR data connection. Here, the communication system <NUM> comprises a UE <NUM> and components of a <NUM> network, comprising a Next Generation (NG) Radio Access Network (RAN), or NG-RAN <NUM>, a <NUM> Core Network (5GCN) <NUM> and a home network 5GCN <NUM>. When home network 5GCN <NUM> is different to 5GCN <NUM>, 5GCN <NUM> and NG-RAN <NUM> may belong to a visited network for UE <NUM>. The home network 5GCN <NUM> is for a Home Public Land Mobile Network (HPLMN) for the UE <NUM> and communicates with the 5GCN <NUM> which may be for a Visited Public Land Mobile Network (VPLMN) that communicates with the UE <NUM>. A <NUM> network may also be referred to as a New Radio (NR) network or as a <NUM> System (5GS); NG-RAN <NUM> may be referred to as an NR RAN or a <NUM> RAN; and 5GCN <NUM> and <NUM> may be referred to as an NG Core network (NGC). The communication system <NUM> may further utilize information from satellite vehicles (SVs) <NUM> for a Global Navigation Satellite System (GNSS) like the Global Positioning System (GPS), GLONASS, Galileo, Beidou or some other local or regional Satellite Positioning System (SPS) such as Indian Regional Navigation Satellite System (IRNSS), European Geostationary Navigation Overlay Service (EGNOS), or Wide Area Augmentation System (WAAS). Additional components of the communication system <NUM> are described below. The communication system <NUM> may include additional or alternative components.

It should be noted that <FIG> provides a generalized illustration of various components, any or all of which may be utilized as appropriate, and each of which may be duplicated or omitted as necessary. Specifically, although one UE <NUM> is illustrated, it will be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the communication system <NUM>. Similarly, the communication system <NUM> may include a larger or smaller number of SVs <NUM>, gNBs <NUM>, external clients <NUM>, and/or other components. The illustrated connections that connect the various components in the communication system <NUM> include data and signaling connections which may include additional (intermediary) components, direct or indirect physical and/or wireless connections, and/or additional networks. Furthermore, components may be rearranged, combined, separated, substituted, and/or omitted, depending on desired functionality.

The UE <NUM>, as used herein, may be an electronic device and may be referred to as a device, a mobile device, a wireless device, a mobile terminal, a terminal, a wireless terminal, a mobile station (MS), a Secure User Plane Location (SUPL) Enabled Terminal (SET), or by some other name. Moreover, UE <NUM> may correspond to a cellphone, smartphone, laptop, tablet, personal data assistant (PDA), tracking device or some other portable or moveable device. In some cases, a UE <NUM> may be part of some other entity - e.g. may be a chipset supporting a modem that is integrated into some larger mobile entity such as a vehicle, drone, package, shipment, robotic device etc. Typically, though not necessarily, the UE <NUM> may support wireless communication using one or more Radio Access Technologies (RATs) such as Global System for Mobile communication (GSM), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), Long Term Evolution (LTE), High Rate Packet Data (HRPD), IEEE <NUM> WiFi, Bluetooth® (BT), Worldwide Interoperability for Microwave Access (WiMAX), <NUM> NR (e.g., using the NG-RAN <NUM> and 5GCN <NUM>, <NUM>), etc. The UE <NUM> may also support wireless communication using a Wireless Local Area Network (WLAN) which may connect to other networks (e.g. the Internet) using a Digital Subscriber Line (DSL) or packet cable for example.

The UE <NUM> may include a single entity or may include multiple entities such as in a personal area network where a user may employ audio, video and/or data I/O devices and/or body sensors and a separate wireline or wireless modem. An estimate of a location of the UE <NUM> may be referred to as a location, location estimate, location fix, fix, position, position estimate or position fix, and may be geodetic, thus providing location coordinates for the UE <NUM> (e.g., latitude and longitude) which may or may not include an altitude component (e.g., height above sea level, height above or depth below ground level, floor level or basement level). Alternatively, a location of the UE <NUM> may be expressed as a civic location (e.g., as a postal address or the designation of some point or small area in a building such as a particular room or floor). A location of the UE <NUM> may also be expressed as an area or volume (defined either geodetically or in civic form) within which the UE <NUM> is expected to be located with some probability or confidence level (e.g., <NUM>%, <NUM>%, etc.) A location of the UE <NUM> may further be a relative location comprising, for example, a distance and direction or relative X, Y (and Z) coordinates defined relative to some origin at a known location which may be defined geodetically, in civic terms, or by reference to a point, area, or volume indicated on a map, floor plan or building plan. In the description contained herein, the use of the term location may comprise any of these variants unless indicated otherwise. When computing the location of a UE, it is common to solve for local x, y, and possibly z coordinates and then, if needed, convert the local coordinates into absolute ones (e.g. for latitude, longitude and altitude above or below mean sea level).

Base stations (BSs) in the NG-RAN <NUM> shown in <FIG> comprise NR NodeBs, also referred to as gNBs, <NUM>-<NUM>, <NUM>-<NUM> and <NUM>-<NUM> (collectively and generically referred to herein as gNBs <NUM>). Pairs of gNBs <NUM> in NG-RAN <NUM> may be connected to one another - e.g. directly as shown in <FIG> or indirectly via other gNBs <NUM>. Access to the <NUM> network is provided to UE <NUM> via wireless communication between the UE <NUM> and one or more of the gNBs <NUM>, which may provide wireless communication access to the 5GCN <NUM> on behalf of the UE <NUM> using <NUM> (e.g., NR). In <FIG>, the serving gNB for UE <NUM> is assumed to be gNB <NUM>-<NUM>, although other gNBs (e.g. gNB <NUM>-<NUM> and/or gNB <NUM>-<NUM>) may act as a serving gNB if UE <NUM> moves to another location or may act as a secondary gNB to provide additional throughout and bandwidth to UE <NUM>. Some gNBs <NUM> in <FIG> (e.g. gNB <NUM>-<NUM> or gNB <NUM>-<NUM>) may be configured to function as positioning-only beacons which may transmit signals (e.g. a Positioning Reference Signal (PRS)) to assist positioning of UE <NUM> but may not receive signals from UE <NUM> or from other UEs.

As noted, while <FIG> depicts nodes configured to communicate according to <NUM> communication protocols, nodes configured to communicate according to other communication protocols, such as, for example, the LTE protocol, may be used. Such nodes, configured to communicate using different protocols, may be controlled, at least in part, by the 5GCN <NUM>. Thus, the NG-RAN <NUM> may include any combination of gNBs, evolved Node Bs (eNBs) supporting LTE access, or other types of base stations or access points. As an example, NG-RAN <NUM> may include one or more next generation eNBs (ng-eNBs) which provide LTE wireless access to UE <NUM> and which may connect to gNBs <NUM> in NG-RAN <NUM> and/or to entities in 5GCN <NUM> such as an Access and Mobility Management Function (AMF) <NUM> and a User Plane Function (UPF) <NUM>.

The gNBs <NUM> can communicate with the AMF <NUM>. The AMF <NUM> may support mobility of the UE <NUM>, including cell change and handover and may participate in supporting a signaling connection to the UE <NUM> and possibly helping establish and release Protocol Data Unit (PDU) sessions for UE <NUM>. Other functions of AMF <NUM> may include: termination of a control plane (CP) interface from NG-RAN <NUM>; termination of Non-Access Stratum (NAS) signaling connections from UEs such as UE <NUM>, NAS ciphering and integrity protection; registration management; connection management; reachability management; mobility management; access authentication and authorization.

As illustrated, HPLMN <NUM> includes a Unified Data Management (UDM) <NUM> and a Home Session Management Function (SMF), H-SMF <NUM>, that may be connected to a Visited SMF (V-SMF) <NUM> in the VPLMN <NUM> (e.g., via the Internet), as well as a User Plane Function (UPF) <NUM> that may be connected to a UPF <NUM> in the VPLMN 5GCN <NUM>. The UDM <NUM> is analogous to a Home Subscriber Server (HSS) for LTE access, and if desired, the UDM <NUM> may be combined with an HSS. The UDM <NUM> is a central database that contains user-related and subscription related information for UE <NUM> and may perform the following functions: UE authentication, UE identification, access authorization, registration and mobility management, subscription management and Short Message Service (SMS) management. The UPF <NUM> and UPF <NUM> may each support voice and data bearers for UE <NUM> and may enable UE <NUM> voice and data access to other networks such as the Internet. UPF <NUM> and/or UPF <NUM> functions may include: external PDU session point of interconnect to a Data Network, packet (e.g. Internet Protocol (IP)) routing and forwarding, packet inspection and user plane part of policy rule enforcement, Quality of Service (QoS) handling for user plane, downlink packet buffering and downlink data notification triggering.

The UPF <NUM> may be communicatively connected to a location server (LS), such as a home SLP (H-SLP) <NUM> for UE <NUM>. The H-SLP <NUM> may support the SUPL user plane (UP) location solution defined by the Open Mobile Alliance (OMA) and may support location services for UE <NUM> based on subscription information for UE <NUM> stored in H-SLP <NUM>. In some embodiments of communication system <NUM>, a Discovered SLP (D-SLP) or Emergency SLP (E-SLP) (not shown in <FIG>), in or accessible from VPLMN 5GCN <NUM> (e.g. connected to UPF <NUM>), may be additionally or alternatively used to locate UE <NUM> using the SUPL UP location solution.

In a UP location solution such as SUPL, signaling (e.g. such as SUPL messages carrying embedded LTE Positioning Protocol (LPP) and/or New Radio Positioning Protocol (NPP) messages) to support location of UE <NUM> may be transferred between participating entities (e.g. UE <NUM> and H-SLP <NUM>) using data bearers (e.g. using the Internet Protocol (IP)).

The H-SMF <NUM> is responsible for session management and may allocate an IP address to UE <NUM>. The H-SMF <NUM> can also select and control the UPF <NUM> for data transfer. The H-SMF <NUM> may be connected to UDM <NUM> for UE <NUM>. The V-SMF <NUM> may similarly control UPF <NUM> and may help establish voice and data sessions for UE <NUM> in coordination with H-SMF <NUM>. UPF <NUM> and/or H-SLP <NUM> may be connected to external client <NUM>, e.g., through another network, such as the Internet.

It should be understood that while a VPLMN <NUM> and a separate HPLMN <NUM> are illustrated in <FIG>, both PLMNs (networks) may be the same PLMN. In that case, (i) H-SLP <NUM>, H-SMF <NUM> and UDM <NUM> may be in the same 5GCN as AMF <NUM>, (ii) 5GCN <NUM> and 5GCN <NUM> may be the same 5GCN, (iii) V-SMF <NUM> and H-SMF <NUM> may be the same SMF, and (v) UPF <NUM> and UPF <NUM> may be the same UPF.

The H-SLP <NUM> may support positioning of the UE <NUM> when UE <NUM> accesses the NG-RAN <NUM> and may support position procedures / methods such as Assisted GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA), Real Time Kinematic (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cell ID (ECID), angle of arrival (AOA), angle of departure (AOD), WLAN positioning and/or other position methods. The H-SLP <NUM> may also process location services requests for the UE <NUM>, e.g., received from external client <NUM>. It is noted that in some embodiments, at least part of the positioning functionality (including derivation of the location of UE <NUM>) may be performed at the UE <NUM> (e.g., using signal measurements obtained by UE <NUM> for signals transmitted by wireless nodes such as gNBs <NUM>, and assistance data provided to the UE <NUM>, e.g. by H-SLP <NUM>).

As further illustrated in <FIG>, H-SLP <NUM> and UE <NUM> may communicate (e.g. using a data connection <NUM>) which may support the transfer of SUPL messages containing positioning protocol messages for the LTE Positioning Protocol (LPP) defined in 3GPP TS <NUM> (or 3GPP TS <NUM>). The LPP protocol may be used to support positioning of UE <NUM> using UE assisted and/or UE based position methods such as A-GNSS, RTK, OTDOA, ECID and/or WLAN positioning. An LPP message sent from the H-SLP <NUM> to the UE <NUM> (e.g. inside a SUPL POS message) may instruct the UE <NUM> to do any of a variety of things, depending on desired functionality. For example, the LPP message could contain an instruction for the UE <NUM> to obtain measurements for GNSS (or A-GNSS), WLAN, and/or OTDOA (or some other position method). In the case of OTDOA, the LPP message may instruct the UE <NUM> to obtain one or more measurements (e.g. Reference Signal Time Difference (RSTD) measurements) of PRS or other signals transmitted within particular cells supported by particular gNBs <NUM> (or supported by one or more ng-eNBs or eNBs). The UE <NUM> may send the measurements back to the H-SLP <NUM> in an LPP message (e.g. transported inside a SUPL POS message).

In some embodiments, LPP may be augmented by or replaced by an NR positioning protocol (NPP or NRPP) which supports position methods such as OTDOA and ECID for NR radio access. For example, an LPP message may contain an embedded NPP message or may be replaced by an NPP message.

As previously noted, a SUPL location session between the UE <NUM> and the H-SLP <NUM> may be utilized to obtain a location estimate for the UE <NUM>, which may involve the transfer of assistance data and positioning measurements between the UE <NUM> and H-SLP <NUM> via a TCP/IP data connection, to aid in the determination of the location of the UE <NUM>. An example data connection <NUM> for a SUPL session between UE <NUM> and H-SLP <NUM> is shown in <FIG> and passes through H-SLP <NUM>, UPF <NUM>, UPF <NUM>, gNB <NUM>-<NUM> and UE <NUM>, with SUPL messages potentially being transferred through each of these entities between UE <NUM> and H-SLP <NUM>. The portion of data connection <NUM> that passes between UE <NUM> and gNB <NUM>-<NUM> may be supported by data transfer and signaling using <NUM> NR.

SUPL sessions may be network initiated (e.g., by the H-SLP <NUM>, which may be in response to receiving a location request for UE <NUM> from an external client <NUM>) or may be UE initiated (e.g. by UE <NUM>). In either case, the UE <NUM> may need to send information related to a <NUM> NR serving cell for UE <NUM> to H-SLP <NUM>, which may be included in a SUPL Location ID (LID) parameter in a SUPL message such as a SUPL POS INIT message. As noted in Table <NUM> below, the LID parameter can define the current serving cell, current serving WLAN AP or current serving WiMAX BS information of UE <NUM> (which is referred to in Table <NUM> as a SET).

The location ID parameter is defined by OMA in a Technical Specification (TS) for the SUPL UserPlane Location Protocol (ULP). The LID definition for ULP may be as shown in Table <NUM> below.

As indicated in Table <NUM>, the Location ID can include information, including information for a serving cell (also referred to as "Cell Info"). For LTE access by a UE <NUM>, the Cell Info in a LID parameter can include LTE Cell Information (also referred to as LTE Cell Info, or as an LTE Cell Information data field), which may be as shown in Table <NUM>.

The LID parameter defined as shown in Tables <NUM> and <NUM> supports location of a UE <NUM> with LTE wireless access and with wireless access according to certain other technologies such as WCDMA, GSM, WLAN (IEEE <NUM>) and HRPD but does not support location of a UE <NUM> with <NUM> NR wireless access such as in communication system <NUM>. A later version of SUPL may support location of a UE <NUM> with <NUM> NR wireless access - e.g. by extending the LID parameter shown in Tables <NUM> and <NUM> with additional information applicable to a <NUM> NR serving cell for a UE <NUM>. However, implementation of such a later version of SUPL may add complexity to a UE <NUM> and H-SLP <NUM> and may not occur for some interim period of a few years or more. In addition, a UE <NUM> that is not implemented according to this later version of SUPL may still support wireless communication using <NUM> NR and may need to be located when accessing <NUM> NR - e.g. as in communication system <NUM>. It may therefore be desirable to support SUPL location for <NUM> NR wireless access using a simpler method than that standardized by OMA in a later version of SUPL. Embodiments of such a simplified method are described herein and involve using LTE Cell Information as shown in Table <NUM> to convey information related to <NUM> NR wireless access. These embodiments may not require any formal change to a LID parameter (e.g. as shown in Table <NUM>) or to the LTE Cell Information defined for SUPL and shown in Table <NUM> and may be forward compatible with any later changes to the LID parameter and LTE cell Information defined by OMA.

As one example, referred to here as example E1, of the method, a UE <NUM> may be accessing <NUM> NR as in communication system <NUM>. In this case, a SUPL session may be established between the UE <NUM> and H-SLP <NUM> using the data connection <NUM> with the purpose of obtaining a location estimate for the UE <NUM>. During the SUPL session, the UE <NUM> may transfer a LID parameter to H-SLP <NUM> - e.g. by sending a SUPL POS INIT message containing the LID parameter to the H-SLP <NUM>. The H-SLP may use the LID parameter to obtain or help obtain a location estimate for the UE <NUM>. The LID parameter may contain "<NUM> information" related to the <NUM> NR wireless access for UE <NUM> including information which may be related to the <NUM> NR serving cell for the UE <NUM>. The <NUM> information may be included in the LTE Cell Information data field of the LID parameter, which may be encoded the same as or similarly to that shown in Table <NUM>. The <NUM> information may comprise information for a <NUM> NR serving cell for UE <NUM> or information for an LTE neighbor cell for UE <NUM>. The LTE neighbor cell may have a coverage area that includes the location of UE <NUM> and overlaps with the coverage area of the NR serving cell for UE <NUM> and may thus enable an approximate location estimate for the UE <NUM>. The information for the LTE neighbor cell may include a cell global identification for the LTE neighbor cel1. The information for the <NUM> NR serving cell for the UE <NUM> may include an indication in the LTE Cell Information data field (e.g. a flag or reserved bit value in one of the data fields for the LTE Cell Info shown in Table <NUM>) indicating the presence of the information for the <NUM> NR serving cell for the UE <NUM>. The information for the <NUM> NR serving cell for the UE <NUM> may comprise a <NUM> NR Physical Cell ID (PCI), a <NUM> NR cell global ID (CGI), a <NUM> NR Tracking Area code (TAC) or some combination of these. The information for the <NUM> NR serving cell may be encoded using one or more data fields in the LTE Cell Information data field. At least some of the information for the <NUM> NR serving cell may be truncated. For example, since an LTE Cell ID comprises <NUM> bits whereas a <NUM> NR Cell ID comprises <NUM> bits, a <NUM> NR serving cell identity (ID) might be truncated to <NUM> bits by removing the high order <NUM> bits or low order <NUM> bits. Such a truncated cell ID may still be useful for locating a UE <NUM> by an H-SLP <NUM> - e.g. if a network does not use the <NUM> high order bits of an NR cell ID or arranges for NR cells sharing the same <NUM> low order bits to be in the same local area. The indication of the presence of the information for the <NUM> NR serving cell for the UE <NUM> may comprise a reserved value or a reserved bit sequence for a data field in the LTE Cell Information data field (e.g. such as the TA data field in Table <NUM>). In some embodiments, both the UE <NUM> and H-SLP <NUM> support the method and are each aware of this support by the other entity. The knowledge of the support by the other entity may be configured in the UE <NUM> and H-SLP <NUM> by the operator of HPLMN <NUM> and may be applicable to location of all subscribed UEs <NUM> by H-SLP <NUM>. In a variant of Example E1, the information related to a <NUM> NR serving cell for a UE <NUM> may be encoded in one or more other fields of a LID parameter, such as a cell information field for WCDMA or information for a WLAN access point.

Further embodiments are described in detail below in relation to <FIG> and <FIG>. Furthermore, although embodiments described herein are directed toward the use of an H-SLP <NUM>, the techniques disclosed herein may be used with other types of SLP servers (e.g., a Visited SLP (V-SLP), D-SLP and/or E-SLP) and/or other location server types.

<FIG> is a message-flow diagram illustrating an example of how a network-initiated SUPL session between an H-SLP <NUM> and a UE <NUM> may be conducted. Here, an external client <NUM> acting as a SUPL agent may begin the messaging illustrated in <FIG> by sending, at action <NUM>, a Mobile Location Protocol (MLP) Standard Location Immediate Request (SLIR) message to the H-SLP <NUM>, with which external client <NUM> is associated. The MLP SLIR message may request a location of UE <NUM>. The H-SLP <NUM> may then authenticate the external client <NUM> and check if the external client <NUM> is authorized for the service it requests, based on a client-id received. Further, based on a received ms-id parameter identifying UE <NUM>, the H-SLP <NUM> may apply subscriber privacy for UE <NUM> against the client-id.

If notification and verification or notification only is required, the H-SLP <NUM> may perform functionality at block <NUM>, in which the H-SLP <NUM> may verify that the UE <NUM> is currently not SUPL roaming, and may further verify that the UE <NUM> supports SUPL.

At action <NUM>, H-SLP <NUM> initiates a SUPL session with the UE <NUM> by sending a SUPL INIT message to the UE <NUM> - e.g. using the User Datagram Protocol (USP) and the Internet Protocol (IP) or using SMS. As partly indicated in <FIG>, the SUPL INIT message may comprise a session-id, proxy/non-proxy mode indicator and an intended positioning method. If the result of the privacy check made by the H-SLP <NUM> after receiving the MLP SLIR message at action <NUM> indicates that notification or verification to the target subscriber for UE <NUM> is needed, the H-SLP <NUM> may also include a Notification element in the SUPL INIT message. Before the SUPL INIT message is sent, the H-SLP <NUM> may also compute and store a hash of the message.

At block <NUM>, the UE <NUM> may analyze the received SUPL INIT. If found to be non-authentic the UE <NUM> may then take no further action. Otherwise the UE <NUM> can take needed action preparing for establishment or resumption of a secure connection.

The UE <NUM> may also evaluate Notification rules and may follow appropriate actions. The UE <NUM> also checks the proxy/non-proxy mode indicator to determine if the H-SLP <NUM> uses proxy or non-proxy mode. In the embodiment illustrated in <FIG>, proxy mode is used and the UE <NUM> may establish a secure connection as part of block <NUM>, such as the data connection <NUM> in <FIG>, to the H-SLP <NUM> using the H-SLP <NUM> address that has been provisioned by the Home Network in the UE <NUM>. Establishment of a secure connection as part of block <NUM> may include: (i) establishing a TCP/IP connection from UE <NUM> to H-SLP <NUM>; (ii) establishing a Transport Layer Security (TLS) session between UE <NUM> and H-SLP <NUM>; (iii) authenticating security credentials for UE <NUM> by H-SLP <NUM>; (iv) authenticating security credentials for H-SLP <NUM> by UE <NUM>; and/or (v) establishing two-way ciphering of data (e.g. SUPL messages) that are transferred between UE <NUM> and H-SLP <NUM> using the established TCP/IP connection and TLS session. Establishment of a secure connection as part of block <NUM> may involve active support by both UE <NUM> and H-SLP <NUM>, though may be initiated only by UE <NUM>.

The UE <NUM> then sends a SUPL POS INIT message to the H-SLP <NUM> using the secure connection, at action <NUM>, to continue the SUPL location session with the H-SLP <NUM>. The UE <NUM> can send the SUPL POS INIT message even if the UE <NUM> supports positioning technologies that do not include the intended positioning method indicated in the SUPL INIT message. The SUPL POS INIT message may comprise the session-id, SET capabilities, a hash of the received SUPL INIT message (ver) and a Location ID corresponding to the LID (or lid) described herein in Tables <NUM> and <NUM>. The UE <NUM>'s SET capabilities may include the positioning methods supported by UE <NUM> (e.g., Assisted GPS (A-GPS), such as SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., Radio Resource Location Services (LCS) Protocol (RRLP), Radio Resource Control (RRC), TIA-<NUM> or LPP/LPP Extensions (LPPe)). The UE <NUM> may additionally provide a Network Measurement Report (NMR) specific for the radio technology being used (e.g., for GSM: Timing Advance (TA), received signal levels (RXLEV)). The UE <NUM> may additionally or alternatively provide its position, if this is supported. The UE <NUM> may include and set a Requested Assistance Data element in the SUPL POS INIT.

According to embodiments, to help ensure the UE <NUM> provides usable cell related information in the LID parameter of the SUPL POS INIT message sent at action <NUM>, in the case that UE <NUM> is using <NUM> NR wireless access, the UE <NUM> can take one of the following steps.

In some embodiments, the UE <NUM> may decide on taking one of the Steps A-D above based on a predetermined priority. In some embodiments, for example, the UE <NUM> may prioritize Steps A-D in the order they are listed above (Step A having the highest priority). Other embodiments may have a different order of priority (prioritizing, for example, Step D over Step C. ) The UE <NUM> may then perform a lower-priority step if unable to perform a higher-priority step, in order to ultimately provide usable NR cell information in the LID parameter of the SUPL POS INIT message sent at action <NUM>.

If a position retrieved from or calculated based on information received in the SUPL POS INIT message is available that meets a required Quality of Positioning (QoP), the H-SLP <NUM> may skip to action <NUM>, sending an SUPL END message and not engaging in a SUPL POS session.

At block <NUM>, the H-SLP <NUM> may check that the hash of the SUPL INIT received at action <NUM> matches the one it has computed for this particular SUPL session. Based on the SUPL POS INIT message including positioning method(s) (or "posmethod(s)") supported by the UE <NUM>, the H-SLP <NUM> may then determine the posmethod. If required for the posmethod, the H-SLP <NUM> may use a supported positioning protocol (e.g., RRLP, RRC, TIA-<NUM> or LPP/LPPe) from the SUPL POS INIT message sent at action <NUM>.

Additionally, at block <NUM>, the UE <NUM> and the H-SLP <NUM> may exchange several successive positioning messages, each comprising a SUPL POS message which includes one or more positioning protocol messages (e.g. for LPP or RRLP). The H-SLP <NUM> may then calculate a position estimate for the UE <NUM> based on the received positioning measurements (UE-Assisted) from the UE <NUM> or the UE <NUM> may calculate the position estimate based on positioning measurements obtained by the UE <NUM> and on assistance data received from the H-SLP <NUM> (UE-Based).

Once the position calculation is complete the H-SLP <NUM> may send a SUPL END message to the UE <NUM> at action <NUM>, informing the UE <NUM> that no further positioning procedure will be started and that the SUPL location session is finished. The UE <NUM> may then release the secure connection to the H-SLP <NUM> (e.g. data connection <NUM>) and release all resources related to this session.

The H-SLP <NUM> may send the position estimate back to the external client <NUM> in an MLP Standard Location Immediate Answer (SLIA) message at action <NUM>, and the H-SLP <NUM> may release all resources related to this SUPL session.

<FIG> is a message-flow diagram illustrating an example of how a UE-initiated (SET-initiated) SUPL session between an H-SLP <NUM> and a UE <NUM> may be conducted, according to an embodiment. The utilization of a LID in the SUPL session can be similar to the utilization of the LID described above with regard to <FIG>.

At block <NUM>, the UE <NUM> may (e.g. via a SUPL Agent on the UE <NUM>) receive a request for a location of UE <NUM> from an application running on the UE <NUM>. The UE <NUM> can then take appropriate action to establish or resume a secure data connection to the H-SLP <NUM> which may correspond to the data connection <NUM> in <FIG>. Establishment of a secure data connection to the H-SLP <NUM> at block <NUM> may be as described for block <NUM> for <FIG>.

The SUPL Agent on the UE <NUM> may use a default address of H-SLP <NUM> provisioned by the Home Network of UE <NUM> to establish or resume a secure connection to the H-SLP <NUM> at block <NUM> and may then send a SUPL START message to the H-SLP <NUM> at action <NUM> to start a SUPL session with the H-SLP <NUM>. The SUPL START message may contain a session-id, SET capabilities of UE <NUM> and a LID parameter. Similar to the embodiment illustrated in <FIG>, the UE <NUM> may take any of a variety of steps (e.g., Steps A-D previously described) to include information related to a <NUM> NR serving cell or a nearby (e.g. neighbor) LTE cell for the UE <NUM> in the LID parameter of the SUPL START message sent at action <NUM> when UE <NUM> is accessing <NUM> NR.

If the H-SLP <NUM> is able to determine a location for the UE <NUM> using the LID received for action <NUM>, where the location meets QoP requirements, the H-SLP <NUM> may directly proceed to action <NUM>, in which a SUPL END message including a location estimate for UE <NUM> may be sent to the UE <NUM>.

At block <NUM>, H-SLP <NUM> may verify that the UE <NUM> is currently not SUPL roaming.

Consistent with the SUPL START message sent at action <NUM>, including posmethod(s) supported by the UE <NUM>, the H-SLP <NUM> may determine a preferred posmethod. If required for the posmethod, the H-SLP <NUM> may use a positioning protocol supported by UE <NUM> (e.g., RRLP, RRC, TIA-<NUM> or LPP/LPPe) as indicated in the SUPL START message. The H-SLP <NUM> may respond by sending a SUPL RESPONSE message at action <NUM> to the UE <NUM>. The SUPL RESPONSE may contain the session-id but no H-SLP address, to indicate to the UE <NUM> that a new connection should not be established. The SUPL RESPONSE may also contain the posmethod, and may also contain location information, not meeting the QoP, but giving a coarse approximation of the position, based on information received in the SUPL START message at action <NUM>.

After the UE <NUM> receives the SUPL RESPONSE from the H-SLP <NUM>, the UE <NUM> may send a SUPL POS INIT message to H-SLP <NUM> at action <NUM>. The SUPL POS INIT message may contain at least the session-id, SET capabilities and a LID parameter. Again, the LID parameter may include information related to a <NUM> NR serving cell in the manner described herein, and may comprise the same information (e.g. the same LID parameter) as was included in the SUPL START message sent at action <NUM>. The UE <NUM> may provide its position, if this is supported, and/or may include a first SUPL POS message within the SUPL POS INIT message, and/or may set the Requested Assistance Data element in the SUPL POS INIT sent at action <NUM>. If a position retrieved or calculated based on information (e.g. the LID) received in the SUPL POS INIT message is available which meets a required QoP, the H-SLP <NUM> may directly proceed to action <NUM>, in which the H-SLP <NUM> sends a SUPL END message and does not engage in a SUPL POS session.

Similar to block <NUM> of <FIG>, at block <NUM> of <FIG> the UE <NUM> and the H-SLP <NUM> may exchange several successive positioning (e.g. SUPL POS) messages. The H-SLP <NUM> may calculate a position estimate for UE <NUM> based on the received positioning measurements (UE-Assisted) or the UE may calculate the position estimate based on assistance data obtained from the H-SLP <NUM> and measurements obtained by the UE <NUM> (UE-Based).

Once the position calculation is complete the H-SLP <NUM> can send a SUPL END message at action <NUM> to the UE <NUM> informing UE <NUM> that no further positioning procedure will be started and that the SUPL location session is finished. Depending on positioning method and used positioning protocol, the H-SLP <NUM> may add the determined position estimate to the SUPL END message. The UE <NUM> may then release the secure connection (e.g. the data connection <NUM>) and may release all resources related to this SUPL session, and the H-SLP <NUM> may release all resources related to this SUPL session.

<FIG> is a flow diagram of a method <NUM> of supporting location of a UE using a SUPL session over a <NUM> NR data connection, according to an embodiment. The method <NUM> may be performed by the UE (e.g. the UE <NUM>). As with other figures provided herein, <FIG> is provided as a non-limiting example. Alternative embodiments may vary in function by combining, separating, or otherwise varying the functionality described in the blocks illustrated in <FIG>. Means for performing the functionality of one or more of the blocks illustrated in <FIG> may comprise hardware and/or software components of a UE, such as the UE <NUM> illustrated in <FIG> and described in more detail below. Additionally, it can be noted that the functions illustrated in <FIG> may be performed by a UE for both network-initiated and UE-initiated SUPL sessions.

At block <NUM>, a <NUM> NR data connection (e.g. the data connection <NUM> in <FIG>) is established between the UE and an SLP (e.g. the H-SLP <NUM>). As indicated in <FIG>, a communication system may include several intervening devices through which communications between the UE and SLP (e.g., H-SLP <NUM>) may be relayed, including a base station supporting a <NUM> NR serving cell (e.g., a serving gNB <NUM>). Means for performing the functionality at block <NUM> may include one or more software and/or hardware components of a UE, such as a bus <NUM>, processing unit(s) <NUM>, memory <NUM>, wireless communication interface <NUM>, and/or other software and/or hardware components of a UE <NUM> as illustrated in <FIG> and described in more detail below. Block <NUM> may correspond to block <NUM> in <FIG> or block <NUM> in <FIG>.

At block <NUM>, the functionality comprises determining cell data, where the cell data comprises information regarding: a <NUM> NR serving cell of the UE, or an LTE neighbor cell for the UE, or a combination thereof. As discussed in embodiments herein, a UE may determine information related to a <NUM> NR serving cell or LTE neighbor cell for the UE to include in an LID parameter by following any of Steps A-D described above or as described for example E1, which include determining information regarding a <NUM> NR serving cell or an LTE neighbor cell. Means for performing the functionality at block <NUM> may include one or more software and/or hardware components of a UE, such as, bus <NUM>, processing unit(s) <NUM>, memory <NUM>, and/or other software and/or hardware components of a UE <NUM> as illustrated in <FIG> and described in more detail below.

At block <NUM>, the functionality comprises sending a SUPL message to the SLP as part of the SUPL session, where the SUPL message comprises a LID parameter having an LTE Cell Information data field. The cell data is included in the LTE Cell Information data field (e.g. as described for steps A-D and example E1 above). According to some embodiments, the location of the UE can then be obtained at least in part by the SLP using the cell data. Means for performing the functionality at block <NUM> may include one or more software and/or hardware components of a UE, such as, bus <NUM>, processing unit(s) <NUM>, memory <NUM>, wireless communication interface <NUM>, and/or other software and/or hardware components of a UE <NUM> as illustrated in <FIG> and described in more detail below. Block <NUM> may correspond to action <NUM> for <FIG> or either of actions <NUM> and <NUM> for <FIG>.

As indicated in the previously-described embodiments, the method <NUM> may include any of a variety of additional features, depending on desired functionality. In some embodiments, for example, the cell data comprises the information regarding the LTE neighbor cell, and the information regarding the LTE neighbor cell includes a cell global identification of the LTE neighbor cell. In some embodiments, the cell data comprises the information regarding the <NUM> NR serving cell of the UE, and the method further comprises including an indication in the LTE Cell Information data field indicating a presence of the information regarding the <NUM> NR serving cell of the UE. As previously indicated, the indication of the presence of the information regarding the <NUM> NR serving cell of the UE may comprise a flag, which may comprise a reserved value or a reserved bit sequence for a data field in the LTE Cell Information data field.

The information regarding the <NUM> NR serving cell of the UE may also vary, depending on desired functionality. In some embodiments, this information may comprise a <NUM> NR Physical Cell ID, <NUM> NR cell global ID, or a <NUM> NR Tracking Area code, or any combination thereof. This information may be encoded using one or more data fields in the LTE Cell Information data field and/or in some other field(s) in the LID parameter, as discussed in the embodiments above. The data fields may include, for example, the LTE Cell ID, as well as the TAC and/or PCI data fields. At least some of the information regarding the <NUM> NR serving cell of the UE may additionally or alternatively be truncated.

The SUPL message sent by the UE may also vary, depending on the scenario. In instances in which the UE initiates the SUPL session, for example, the SUPL message may comprise a SUPL START or SUPL POS INIT message. In instances in which the SLP initiates the SUPL session, the SUPL message may comprise a SUPL POS INIT message. In this latter case, the UE may receive a SUPL INIT message from the SLP, and establishing the <NUM> NR data connection between the UE and the SLP may be in response to receiving the SUPL INIT message.

<FIG> is a flow diagram of a method <NUM> at an SLP (e.g. the H-SLP <NUM>) of supporting location of a UE (e.g. the UE <NUM>) using a SUPL session over a <NUM> NR data connection, according to an embodiment. Alternative embodiments may vary in function by combining, separating, or otherwise varying the functionality described in the blocks illustrated in <FIG>. Means for performing the functionality of one or more of the blocks illustrated in <FIG> may comprise hardware and/or software components of a computer system, such as the computer system <NUM> illustrated in <FIG> and described in more detail below. Additionally, it can be noted that the functions illustrated in <FIG> may be performed by an SLP for both network-initiated and UE-initiated SUPL sessions. According to some embodiments, the SLP may comprise an H-SLP, as illustrated in embodiments described above.

At block <NUM>, a <NUM> NR data connection (e.g., the data connection <NUM> in <FIG>) is established between the SLP and the UE. Again, a communication system may include several intervening devices through which communications between the UE and SLP may be relayed. Means for performing the functionality at block <NUM> may include one or more software and/or hardware components of a computer system, such as a bus <NUM>, processing unit(s) <NUM>, memory <NUM>, communication subsystem <NUM>, and/or other software and/or hardware components of a computer system <NUM> as illustrated in <FIG> and described in more detail below. Block <NUM> may correspond to block <NUM> in <FIG> or block <NUM> in <FIG>.

At block <NUM>, the functionality comprises receiving a SUPL message from the UE as part of the SUPL session. For example, the SUPL message may start the SUPL session or may continue the SUPL session. The SUPL message comprises a LID parameter having an LTE Cell Information data field. Cell data is included in the LTE Cell Information data field, and the cell data comprises information regarding a <NUM> NR serving cell of the UE or an LTE neighbor cell. Means for performing the functionality at block <NUM> may include one or more software and/or hardware components of a computer system, such as a bus <NUM>, processing unit(s) <NUM>, memory <NUM>, communication subsystem <NUM>, and/or other software and/or hardware components of a computer system <NUM> as illustrated in <FIG> and described in more detail below. Block <NUM> may correspond to action <NUM> for <FIG> or either of actions <NUM> and <NUM> for <FIG>.

At block <NUM>, a location of the UE is determined based at least in part on the cell data. Means for performing the functionality at block <NUM> may include one or more software and/or hardware components of a computer system, such as a bus <NUM>, processing unit(s) <NUM>, memory <NUM>, communication subsystem <NUM>, and/or other software and/or hardware components of a computer system <NUM> as illustrated in <FIG> and described in more detail below.

As indicated in the previously-described embodiments, the method <NUM> may include any of a variety of additional features, depending on desired functionality. For example, in some embodiments where the cell data comprises information regarding the LTE neighbor cell, the information regarding the LTE neighbor cell may include a cell global identification of the LTE neighbor cell. In some embodiments where the cell data comprises the information regarding the <NUM> NR serving cell of the UE, the method may further comprise identifying an indication in the LTE Cell Information data field indicating the presence of the information regarding the <NUM> NR serving cell of the UE. As previously indicated, the indication of the presence of the information regarding the <NUM> NR serving cell of the UE may comprise a flag, which may comprise a reserved value or a reserved bit sequence for a data field in the LTE Cell Information data field.

The information regarding the <NUM> NR serving cell of the UE may also vary, depending on desired functionality. In some embodiments, this information may comprise a <NUM> NR Physical Cell ID, <NUM> NR cell global ID, or a <NUM> NR Tracking Area code, or any combination thereof. This information may be encoded using one or more data fields in the LTE Cell Information data field and/or in some other field(s) in the LID parameter, as discussed in the embodiments above. The data fields may include, for example, the LTE Cell ID, as well as the TAC and/or PCI data fields. The information regarding the <NUM> NR serving cell may additionally or alternatively be truncated.

The SUPL message sent by the UE may also vary, depending on the scenario. In instances in which the UE initiates the SUPL session, for example, the SUPL message may comprise a SUPL START or SUPL POS INIT message. In instances in which the SLP initiates the SUPL session, the SUPL message may comprise a SUPL POS INIT message. In this latter case, the SLP may send a SUPL INIT message to the UE, and establishing the <NUM> NR data connection between the SLP and the UE may be in response to the UE receiving the SUPL INIT message.

According to embodiments, SLPs may vary in design and function, depending on desired functionality. For example, an embodiment of an SLP, according to this description, comprises a communication interface, a memory, and one or more processing units communicatively coupled with the communication interface and the memory. The one or more processing units are configured to establish, using the communication interface, a <NUM> NR data connection between the SLP and a UE, and receive, using the communication interface, a SUPL message from the UE as part of a SUPL session, the SUPL message comprising a LID parameter having a LTE Cell Information data field. Cell data is included in the LTE Cell Information data field, and the cell data comprises information regarding a <NUM> NR serving cell of the UE, or an LTE neighbor cell, or a combination thereof. The one or more processing units are also configured to determine a location of the UE based at least in part on the cell data.

Alternative embodiments of the example SLP may include one or more of the following features. The one or more processing units may be further configured to identify an indication in the LTE Cell Information data field indicating the presence of the information regarding the <NUM> NR serving cell of the UE. The one or more processing units may be further configured to receive, using the communication interface, a SUPL START message at the SLP after establishing the <NUM> NR data connection between the SLP and the UE. The one or more processing units may be further configured to send, using the communication interface a SUPL INIT message to the UE, wherein the one or more processing units are further configured to establish the <NUM> NR data connection between the UE and the SLP is in response to the UE receiving the SUPL INIT message.

An example method at an SLP of supporting location of a UE using a SUPL session over a <NUM> NR data connection, according to this description, comprises establishing the <NUM> NR data connection between the SLP and the UE, and receiving a SUPL message from the UE as part of the SUPL session, the SUPL message comprising a Location ID (LID) parameter having a Long-Term Evolution (LTE) Cell Information data field. The cell data is included in the LTE Cell Information data field, and the cell data comprises information regarding a <NUM> NR serving cell of the UE, or an LTE neighbor cell, or a combination thereof. The method further comprises determining a location of the UE based at least in part on the cell data.

Alternative embodiments of the example method may include one or more of the following features. The cell data may comprise the information regarding the LTE neighbor cell, and the information regarding the LTE neighbor cell may include a cell global identification of the LTE neighbor cell. The cell data may comprise the information regarding the <NUM> NR serving cell of the UE, and the method may further comprise identifying an indication in the LTE Cell Information data field indicating the presence of the information regarding the <NUM> NR serving cell of the UE. The information regarding the <NUM> NR serving cell of the UE may comprise a <NUM> NR Physical Cell ID, a <NUM> NR cell global ID, or a <NUM> NR Tracking Area code, or any combination. The information regarding the <NUM> NR serving cell of the UE may be encoded using one or more data fields in the LTE Cell Information data field. At least some of the information regarding the <NUM> NR serving cell of the UE may be truncated. The indication of the presence of the information regarding the <NUM> NR serving cell of the UE may comprise a reserved value or a reserved bit sequence for a data field in the LTE Cell Information data field. The UE may initiate the SUPL session, and the method may further comprise receiving a SUPL START message at the SLP after establishing the <NUM> NR data connection between the SLP and the UE. The SLP may initiate the SUPL session, and the method may further comprise sending a SUPL INIT message to the UE, wherein establishing the <NUM> NR data connection between the UE and the SLP is in response to the UE receiving the SUPL INIT message. The SUPL message may comprise a SUPL POS INIT message.

According to another embodiment, an example computer server comprises means for establishing a <NUM> NR data connection between the computer server and a UE, and means for receiving a SUPL message from the UE as part of a SUPL session, the SUPL message comprising a LID parameter having an LTE Cell Information data field. Cell data is included in the LTE Cell Information data field, and the cell data comprises information regarding a <NUM> NR serving cell of the UE or an LTE neighbor cell. The computer server further comprises means for determining a location of the UE based at least in part on the cell data.

Alternative embodiments of the computer server may comprise one or more the following features. The computer server may further comprise means for identifying an indication in the LTE Cell Information data field indicating the presence of the information regarding the <NUM> NR serving cell of the UE. The computer server may further comprise means for receiving a SUPL START message at the computer server after establishing the <NUM> NR data connection between the computer server and the UE. The computer server may further comprise means for sending a SUPL INIT message to the UE, and wherein the means for establishing the <NUM> NR data connection between the UE and the computer server is configured to do so in response to the UE receiving the SUPL INIT message.

An example non-transitory computer-readable medium, according to this description, includes instructions embedded thereon for supporting location of a UE using a SUPL session over a <NUM> NR data connection. The instructions, when executed by one or more processing units of an SLP, cause the SLP to: establish the <NUM> NR data connection between the SLP and the UE and receive a SUPL message from the UE as part of the SUPL session, the SUPL message comprising a LID parameter having a Long-Term Evolution (LTE) Cell Information data field. Cell data is included in the LTE Cell Information data field, and the cell data comprises information regarding a <NUM> NR serving cell of the UE or an LTE neighbor cell. The instructions, when executed by one or more processing units of an SLP, further cause the SLP to determine a location of the UE based at least in part on the cell data.

Alternative embodiments of the non-transitory computer-readable medium may include one or more the following features. The instructions, when executed by the one or more processing units of the SLP, may further cause the SLP to identify an indication in the LTE Cell Information data field indicating the presence of the information regarding the <NUM> NR serving cell of the UE. The instructions, when executed by the one or more processing units of the SLP, then further cause the SLP to send a SUPL INIT message to the UE, and establishing the <NUM> NR data connection between the UE and the SLP may be in response to the UE receiving the SUPL INIT message.

<FIG> illustrates an embodiment of a UE <NUM>, which can be utilized as described herein above (e.g. in association with <FIG>). For example, the UE <NUM> can perform one or more of the functions of method <NUM> of <FIG>. It should be noted that <FIG> is meant to provide a generalized illustration of various components, any or all of which may be utilized as appropriate. It can be noted that, in some instances, components illustrated by <FIG> can be localized to a single physical device and/or distributed among various networked devices, which may be disposed at different physical locations (e.g., located at different parts of a user's body, in which case the components may be communicatively connected via a Personal Area Network (PAN) and/or other means).

The UE <NUM> is shown comprising hardware elements that can be electrically coupled via a bus <NUM> (or may otherwise be in communication, as appropriate). The hardware elements may include a processing unit(s) <NUM> which can include without limitation one or more general-purpose processors, one or more special-purpose processors (such as digital signal processing (DSP) chips, graphics acceleration processors, application specific integrated circuits (ASICs), and/or the like), and/or other processing structure or means. As shown in <FIG>, some embodiments may have a separate Digital Signal Processor (DSP) <NUM>, depending on desired functionality. Location determination and/or other determinations based on wireless communication may be provided in the processing unit(s) <NUM> and/or wireless communication interface <NUM> (discussed below). The UE <NUM> also can include one or more input devices <NUM>, which can include without limitation a keyboard, touch screen, a touch pad, microphone, button(s), dial(s), switch(es), and/or the like; and one or more output devices <NUM>, which can include without limitation a display, light emitting diode (LED), speakers, and/or the like.

The UE <NUM> may also include a wireless communication interface <NUM>, which may comprise without limitation a modem, a network card, an infrared communication device, a wireless communication device, and/or a chipset (such as a Bluetooth® device, an IEEE <NUM> device, an IEEE <NUM>. <NUM> device, a WiFi device, a WiMax device, a WAN device and/or various cellular devices, etc.), and/or the like, which may enable the UE <NUM> to communicate via the networks described above with regard to <FIG>. The wireless communication interface <NUM> may permit data and signaling to be communicated (e.g. transmitted and received) with a <NUM> LTE and/or <NUM> NR network as described herein, for example, via eNBs, gNBs, ng-eNBs, access points, various base stations and/or other access node types, and/or other network components, computer systems, and/or any other electronic devices described herein. The communication can be carried out via one or more wireless communication antenna(s) <NUM> that send and/or receive wireless signals <NUM>.

Depending on desired functionality, the wireless communication interface <NUM> may comprise separate transceivers to communicate with base stations (e.g., ng-eNBs and gNBs) and other terrestrial transceivers, such as wireless devices and access points. The UE <NUM> may communicate with different data networks that may comprise various network types. For example, a Wireless Wide Area Network (WWAN) may be a Code Division Multiple Access (CDMA) network, a Time Division Multiple Access (TDMA) network, a Frequency Division Multiple Access (FDMA) network, an Orthogonal Frequency Division Multiple Access (OFDMA) network, a Single-Carrier Frequency Division Multiple Access (SC-FDMA) network, a WiMax (IEEE <NUM>) network, and so on. A CDMA network may implement one or more radio access technologies (RATs) such as CDMA2000, Wideband CDMA (WCDMA), and so on. Cdma2000 includes IS-<NUM>, IS-<NUM>, and/or IS-<NUM> standards. A TDMA network may implement GSM, Digital Advanced Mobile Phone System (D-AMPS), or some other RAT. An OFDMA network may employ LTE, LTE Advanced, <NUM> NR, and so on. <NUM> NR, LTE, LTE Advanced, GSM, and WCDMA are described in documents from 3GPP. Cdma2000 is described in documents from a consortium named "3rd Generation Partnership Project <NUM>" (3GPP2). 3GPP and 3GPP2 documents are publicly available. A wireless local area network (WLAN) may also be an IEEE <NUM>. 11x network, and a wireless personal area network (WPAN) may be a Bluetooth network, an IEEE <NUM>. 15x, or some other type of network. The techniques described herein may also be used for any combination of WWAN, WLAN and/or WPAN.

The UE <NUM> can further include sensor(s) <NUM>. Sensors <NUM> may comprise, without limitation, one or more inertial sensors and/or other sensors (e.g., accelerometer(s), gyroscope(s), camera(s), magnetometer(s), altimeter(s), microphone(s), proximity sensor(s), light sensor(s), barometer(s), and the like), some of which may be used to complement and/or facilitate the position determination described herein, in some instances.

Embodiments of the UE <NUM> may also include a GNSS receiver <NUM> capable of receiving signals <NUM> from one or more GNSS satellites (e.g., SVs <NUM>) using an antenna <NUM> (which could be the same as antenna <NUM>). Positioning based on GNSS signal measurement can be utilized to complement and/or incorporate the techniques described herein. The GNSS receiver <NUM> can determine or help determine a position of the UE <NUM>, using conventional techniques, from GNSS SVs of a GNSS system (e.g., SVs <NUM> of <FIG>), such as Global Positioning System (GPS), Galileo, Glonass, Quasi-Zenith Satellite System (QZSS) over Japan, IRNSS over India, Beidou over China, and/or the like. Moreover, the GNSS receiver <NUM> can be used with various augmentation systems (e.g., a Satellite Based Augmentation System (SBAS)) that may be associated with or otherwise enabled for use with one or more global and/or regional navigation satellite systems, such as, e.g., WAAS, EGNOS, Multi-functional Satellite Augmentation System (MSAS), and Geo Augmented Navigation system (GAGAN), and/or the like.

The UE <NUM> may further include and/or be in communication with a memory <NUM>. The memory <NUM> can include, without limitation, local and/or network accessible storage, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random access memory ("RAM"), and/or a read-only memory ("ROM"), which can be programmable, flash-updateable, and/or the like. Such storage devices may be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and/or the like.

The memory <NUM> of the UE <NUM> also can comprise software elements (not shown in <FIG>), including an operating system, device drivers, executable libraries, and/or other code, such as one or more application programs, which may comprise computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein. Merely by way of example, one or more procedures described with respect to the method(s) discussed above may be implemented as code and/or instructions in memory <NUM> that are executable by the UE <NUM> (and/or processing unit(s) <NUM> or DSP <NUM> within UE <NUM>). In an aspect, then, such code and/or instructions can be used to configure and/or adapt a general purpose computer (or other device) to perform one or more operations in accordance with the described methods.

<FIG> illustrates an embodiment of a computer system <NUM>, which may be utilized and/or incorporated into one or more components of a communication system (e.g., communication system <NUM> of <FIG>), including various components of a <NUM> network, such as the NG-RAN <NUM>, 5GCN <NUM> or <NUM>, and/or similar components of other network types. <FIG> provides a schematic illustration of one embodiment of a computer system <NUM> that can perform the methods provided by various other embodiments, such as the methods described in relation to <FIG>. It should be noted that <FIG> is meant to provide a generalized illustration of various components, any or all of which may be utilized as appropriate. <FIG>, therefore, broadly illustrates how individual system elements may be implemented in a relatively separated or relatively more integrated manner. In addition, it can be noted that components illustrated by <FIG> can be localized to a single device and/or distributed among various networked devices, which may be disposed at different physical or geographical locations. In some embodiments, the computer system <NUM> may correspond to an H-SLP (e.g. H-SLP <NUM>) or another SLP (e.g. such as a V-SLP, D-SLP or E-SLP), a gNB <NUM> (e.g. gNB <NUM>-<NUM>), another cellular or non-cellular access node, a UDM <NUM>, and H-SMF <NUM>, and/or some other type of location-capable device.

The computer system <NUM> is shown comprising hardware elements that can be electrically coupled via a bus <NUM> (or may otherwise be in communication, as appropriate). The hardware elements may include processing unit(s) <NUM>, which can include without limitation one or more general-purpose processors, one or more special-purpose processors (such as digital signal processing chips, graphics acceleration processors, and/or the like), and/or other processing structure, which can be configured to perform one or more of the methods described herein, including the method described in relation to <FIG>. The computer system <NUM> also can include one or more input devices <NUM>, which can include without limitation a mouse, a keyboard, a camera, a microphone, and/or the like; and one or more output devices <NUM>, which can include without limitation a display device, a printer, and/or the like.

The computer system <NUM> may further include (and/or be in communication with) one or more non-transitory storage devices <NUM>, which can comprise, without limitation, local and/or network accessible storage, and/or can include, without limitation, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random access memory ("RAM"), and/or a read-only memory ("ROM"), which can be programmable, flash-updateable, and/or the like. Such storage devices may be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and/or the like.

The computer system <NUM> may also include a communications subsystem <NUM>, which can include support of wireline communication technologies and/or wireless communication technologies (in some embodiments) managed and controlled by a wireless communication interface <NUM>. The communications subsystem <NUM> may include a modem, a network card (wireless or wired), an infrared communication device, a wireless communication device, and/or a chipset, and/or the like. The communications subsystem <NUM> may include one or more input and/or output communication interfaces, such as the wireless communication interface <NUM>, to permit data and signaling to be exchanged with a network, mobile devices, other computer systems, and/or any other electronic devices described herein. Note that the terms "mobile device" and "UE" are used interchangeably herein to refer to any mobile communications device such as, but not limited to, mobile phones, smartphones, wearable devices, mobile computing devices (e.g., laptops, PDAs, tablets), embedded modems, and automotive and other vehicular computing devices.

In many embodiments, the computer system <NUM> will further comprise a working memory <NUM>, which can include a RAM and/or or ROM device. Software elements, shown as being located within the working memory <NUM>, can include an operating system <NUM>, device drivers, executable libraries, and/or other code, such as application(s) <NUM>, which may comprise computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein. Merely by way of example, one or more procedures described with respect to the method(s) discussed above, such as the method described in relation to <FIG>, may be implemented as code and/or instructions that are stored (e.g. temporarily) in working memory <NUM> and are executable by a computer (and/or a processing unit within a computer such as processing unit(s) <NUM>); in an aspect, then, such code and/or instructions can be used to configure and/or adapt a general purpose computer (or other device) to perform one or more operations in accordance with the described methods.

A set of these instructions and/or code might be stored on a non-transitory computer-readable storage medium, such as the storage device(s) <NUM> described above. In some cases, the storage medium might be incorporated within a computer system, such as computer system <NUM>. In other embodiments, the storage medium might be separate from a computer system (e.g., a removable medium, such as an optical disc), and/or provided in an installation package, such that the storage medium can be used to program, configure, and/or adapt a general purpose computer with the instructions/code stored thereon. These instructions might take the form of executable code, which is executable by the computer system <NUM> and/or might take the form of source and/or installable code, which, upon compilation and/or installation on the computer system <NUM> (e.g., using any of a variety of generally available compilers, installation programs, compression/decompression utilities, etc.), then takes the form of executable code.

With reference to the appended figures, components that can include memory can include non-transitory machine-readable media. The term "machine-readable medium" and "computer-readable medium" as used herein, refer to any storage medium that participates in providing data that causes a machine to operate in a specific fashion. In embodiments provided hereinabove, various machine-readable media might be involved in providing instructions/code to processing units and/or other device(s) for execution. Additionally or alternatively, the machine-readable media might be used to store and/or carry such instructions/code. In many implementations, a computer-readable medium is a physical and/or tangible storage medium. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Common forms of computer-readable media include, for example, magnetic and/or optical media, any other physical medium with patterns of holes, a Random Access Memory (RAM), a Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read instructions and/or code.

The methods, systems, and devices discussed herein are examples. Various embodiments may omit, substitute, or add various procedures or components as appropriate. For instance, features described with respect to certain embodiments may be combined in various other embodiments. Different aspects and elements of the embodiments may be combined in a similar manner. The various components of the figures provided herein can be embodied in hardware and/or software. Also, technology evolves and, thus, many of the elements are examples that do not limit the scope of the disclosure to those specific examples.

Claim 1:
A method (<NUM>) at a Secure User Plane Location platform, SLP, of supporting location of a user equipment, UE, using a Secure User Plane Location, SUPL session over a Fifth Generation, <NUM>, New Radio, NR, data connection, the method comprising:
establishing (<NUM>) the <NUM> NR data connection between the UE and the SLP;
receiving (<NUM>) a SUPL message from the UE as part of the SUPL session, the SUPL message comprising a Location ID, LID, parameter having a Long-Term Evolution, LTE, Cell Information data field, wherein cell data is included in the LTE Cell Information data field, and wherein the cell data comprises information regarding a <NUM> NR serving cell of the UE; and
determining (<NUM>) a location of the UE based at least in part on the cell data.