System and method for periodic and triggered event reporting via user plane

By using user plane signaling to directly transmit location reports from user equipment to external clients, the solution addresses high latency issues in existing wireless networks, enhancing location accuracy and reducing end-to-end latency.

CN119096618APending Publication Date: 2024-12-06QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380036517.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-03
Filing Date
2023-05-04
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

Current location solutions in wireless networks suffer from high latency, with most solutions taking 1-10 seconds to provide location estimates, and no existing solution achieves latency below 1 second without using mobile device-based positioning, which is inadequate for applications requiring low latency and high accuracy.

Method used

Implementing user plane (UP) connections to pass event reports from the UE directly to the LCS client or AF (1 hop). The solution includes a defined protocol layer on the user plane (IP), Transmission Control Protocol (TCP), Transport Layer Security (TLS), supplementary services. Support for UP connections is provided through LMF or GMLC, wherein the use of LMF allows the use of more positioning methods, and the use of GMLC allows event reporting to have better security and monitoring. The solution also allows the UE to report the status of UP event reporting to the LMF and GMLC via the CP.

Benefits of technology

Reduces latency and improves signaling efficiency by minimizing the number of intermediate entities involved in location report delivery, achieving low latency and high accuracy location reporting.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096618A_ABST
    Figure CN119096618A_ABST
Patent Text Reader

Abstract

Methods and apparatus for reducing end-to-end latency for location determination of a user equipment (UE) are described. Control plane signaling may be used to support location requests for UEs from external clients. User plane signaling may be utilized to support location reporting to the external client to minimize latency. Event reports with location information may be transmitted to the external client (or application function) using user plane signaling either directly or via a location management function (LMF) or a gateway mobile location center (GMLC) or via both the LMF and GMLC. In the event that the LMF or GMLC receives an event report from the UE, the LMF or GMLC may transmit the event report to the external client using user plane signaling. A periodic or triggered cumulative event report may be transmitted to the LMF, GMLC, or external client using control plane signaling to confirm that the periodic or triggered location request remains operational.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Related Applications

[0002] This application claims the benefit of U.S. Application No. 18 / 311,877, filed on May 3, 2023, entitled “SYSTEMS AND METHODS FOR PERIODIC AND TRIGGERED EVENT REPORTING VIA USER PLANE,” which claims the benefit of U.S. Provisional Application No. 63 / 382,207, filed on November 3, 2022, entitled “SYSTEMS AND METHODS FOR PERIODIC AND TRIGGERED EVENT REPORTING VIA USERPLANE,” and U.S. Provisional Application No. 63 / 382,207, filed on May 5, 2022, entitled “SYSTEMS AND METHODS FOR PERIODIC AND TRIGGERED EVENT REPORTING VIA USER PLANE,” which claims the benefit of U.S. Provisional Application No. 63 / 382,207, filed on November 3, 2022, entitled “SYSTEMS AND METHODS FOR PERIODIC AND TRIGGERED EVENT REPORTING VIA USER PLANE,” and U.S. Provisional Application No. 63 / 382,207, filed on November 3, 2022, entitled “SYSTEMS AND METHODS FOR PERIODIC AND TRIGGERED EVENT REPORTING VIA USER 63 / 338,877 to "PLANE" both of which are assigned to the assignee of the present application and are incorporated herein by reference in their entirety. Background Art Technical Field

[0003] The present disclosure relates generally to communications, and more particularly to techniques for supporting location services for user equipment (UE).

[0004] Related Background

[0005] Certain location use cases require very low latency when providing the location of a mobile device to external clients. Examples include: smart (automated) factories, where the location of tools and objects being manufactured may need to be known with an accuracy of 1 cm to 10 cm (or less) and with a latency of less than 100 milliseconds (ms); drones, where the location may need to be known to within a second or less with an accuracy of 1 meter; public safety first responders in hazardous locations (e.g., inside a burning or partially collapsed building); and use cases associated with locating vehicles and / or pedestrians (referred to as V2X). Other use cases associated with high location accuracy may also have low latency requirements, as the location accuracy of moving objects degrades rapidly. For example, even at only 4 mph (normal walking speed), an object moves 1.79 meters in 1 second, so after less than 1 second, the advantage of 1 meter location accuracy is no longer valid.

[0006] Current location solutions defined for wireless networks can have latencies of 1 second to 10 seconds or more, and no location solution defined for wireless networks is known to have a latency that is consistently less than 1 second, except for solutions that use mobile device-based positioning (where the mobile device or an application in the mobile device is also a client for determining location). Summary of the invention

[0007] Methods and apparatus for reducing end-to-end latency in location determination of a user equipment (UE) are described. Control plane signaling may be used to support location requests for the UE from an external client. User plane signaling may be used to support location reports to the external client to minimize latency. User plane signaling may be used to transmit event reports with location information to the external client (or application function) directly or via a location management function (LMF) or a gateway mobile location center (GMLC), or via both the LMF and GMLC. In the event that the LMF or GMLC receives an event report from the UE, the LMF or GMLC may transmit the event report to the external client using user plane signaling. Control plane signaling may be used to transmit periodic or triggered cumulative event reports to the LMF, GMLC, or external client to confirm that the periodic or triggered location requests remain operational.

[0008] According to the present disclosure, an example method performed by a user equipment (UE) for locating the UE in a wireless network may include: receiving a request for locating the UE, wherein the request for locating the UE includes a periodic or triggered location request based on a location request initiated by an external client or application function (AF), including one or more criteria for providing a cumulative event report, and is received by the UE using control plane signaling. The method may also include: performing the following operations in response to detecting a periodic or triggered event, the periodic or triggered event occurring at multiple different times: obtaining first location information of the UE, and reporting the first location information of the UE to the external client or AF using user plane signaling. The method may also include: in response to determining that at least one of the one or more criteria for providing the cumulative event report has been met, transmitting the cumulative event report to the external client or AF using control plane signaling.

[0009] An example user equipment (UE) may include: one or more transceivers, one or more memories, one or more processors, the one or more processors being communicatively coupled to the one or more transceivers and the one or more memories, wherein the one or more processors are configured to receive a request for locating the UE via the one or more transceivers, wherein the request for locating the UE: comprises a periodic or triggered location request based on a location request initiated by an external client or application function (AF), comprises one or more criteria for providing a cumulative event report, and is received by the UE using control plane signaling. The one or more processors may be further configured to: in response to detecting a periodic or triggered event, perform the following operations, the periodic or triggered event occurring at multiple different times: obtain first location information of the UE, and report the first location information of the UE to the external client or AF using user plane signaling. The one or more processors may be further configured to: in response to determining that at least one of the one or more criteria for providing the cumulative event report has been met, transmit the cumulative event report to the external client or AF via the one or more transceivers using control plane signaling.

[0010] According to the present disclosure, an example device for locating a user equipment (UE) in a wireless network may include a component for receiving a request for locating the UE, wherein the request for locating the UE includes a periodic or triggered location request based on a location request initiated by an external client or application function (AF), includes one or more criteria for providing a cumulative event report, and is received by the UE using control plane signaling. The device may also include a component for performing the following operations in response to detecting a periodic or triggered event, which occurs at multiple different times: obtaining first location information of the UE, and reporting the first location information of the UE to the external client or AF using user plane signaling. The device may also include a component for transmitting the cumulative event report to the external client or AF using control plane signaling in response to determining that at least one of the one or more criteria for providing the cumulative event report has been met.

[0011] According to the present disclosure, an example non-transitory computer-readable medium stores instructions for locating a user equipment (UE) in a wireless network, the instructions including code for receiving a request for locating the UE, wherein the request for locating the UE includes a periodic or triggered location request based on a location request initiated by an external client or application function (AF), includes one or more criteria for providing a cumulative event report, and is received by the UE using control plane signaling. The instructions may also include code for performing the following operations in response to detecting a periodic or triggered event, the periodic or triggered event occurring at multiple different times: obtaining first location information of the UE, and reporting the first location information of the UE to the external client or AF using user plane signaling. The instructions may also include code for performing the following operations: in response to determining that at least one of the one or more criteria for providing the cumulative event report has been met, transmitting the cumulative event report to the external client or AF using control plane signaling. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] An understanding of the nature and advantages of the various embodiments may be achieved by reference to the following drawings.

[0013] Figure 1A and Figure 1B is a simplified block diagram illustrating a network architecture supporting Very Low Latency Location Services (VLLLS) for non-roaming UEs.

[0014] Figure 2 is a simplified block diagram illustrating a network architecture supporting VLLLS for roaming UEs.

[0015] Figure 3A It is a representation of the protocol layer that can be used when the target UE communicates the location report for the target UE to the external client.

[0016] Figure 3B It is a representation of the protocol layers that may be used when a target UE delivers a location report for the target UE using user plane signaling directly to an external client or via a Location Management Function (LMF) or Gateway Mobile Location Centre (GMLC).

[0017] Figure 4A A location session establishment and reporting procedure for supporting VLLLS for a target UE supporting location reporting is shown.

[0018] Figure 4B A location reporting procedure applicable to a target UE supporting location reporting to an external client or Application Function (AF) is shown.

[0019] Figure 4CA location reporting procedure applicable to a target UE supporting location reporting to an external client or Application Function (AF) via GMLC is shown.

[0020] Figure 4D A location reporting procedure suitable for a target UE supporting location reporting to an external client or Application Function (AF) via a location server is shown.

[0021] Figure 4E A location reporting procedure is shown which may be used by a UE to report via a user facing LCS client or AF.

[0022] Figure 5 is an illustration of a process flow illustrating a method performed by a user equipment (UE) for locating the UE in a wireless network according to one embodiment.

[0023] Figure 6 is a block diagram of an implementation of a network entity such as a GMLC or NEF supporting VLLLS.

[0024] Figure 7 is a block diagram of an implementation of a network entity such as an AMF or LMF supporting VLLLS.

[0025] Figure 8 is a block diagram of an implementation of a user equipment supporting VLLLS.

[0026] Similar reference numerals and symbols in the various drawings are specifically implemented to indicate similar elements according to certain examples. In addition, multiple instances of the element can be indicated by adding a letter or a hyphen and a second numeral after the first numeral of the element. For example, multiple instances of element 110 can be indicated as 110-1, 110-2, 110-3, etc. Similarly, multiple instances of element 155 can be indicated as 155A, 155B, 155C, etc. When only the first numeral is used to refer to such an element, it should be understood that any instance of the element (for example, the element 110 in the previous example will refer to elements 110-1, 110-2 and 110-3, and the element 155 in the previous example will refer to elements 155A, 155B and 155C). DETAILED DESCRIPTION

[0027] Obtaining the location of a user equipment (UE) (sometimes referred to as a "target UE") in a wireless network may be useful for many application scenarios, including, for example, emergency calls, personal navigation, asset tracking, locating friends or family members, etc. However, certain types of use cases require low latency or very low latency (e.g., less than 1 second, and in some cases less than 100 milliseconds (ms)). The end-to-end latency in providing a location estimate of the target UE to an external client may include the following components: A) delay in transmitting a location request from the external client to a control entity (e.g., a location server) in the wireless network; B) delay in requesting location measurements or location estimates from other entities in the wireless network and / or from the target UE by the control entity; C) delay in obtaining location measurements; D) delay in delivering location measurements to a location calculation entity (e.g., a control entity); E) delay in calculating a location estimate from the location measurements; and F) delay in delivering the calculated location estimate to the external client.

[0028] To minimize these components, one or more of the following approaches may be taken. Components (A) and (B) may be performed only once or infrequently to establish a series of continuous position measurements for the target UE (e.g., via periodic or triggered location). Component (C) may be reduced by tracking, where the position measurement entity (e.g., the target UE or a base station in the wireless network) relies on previous measurements to establish a small window within which any new measurements can be expected to be obtained. For example, when the measuring entity already knows the time of arrival (TOA) (and any Doppler) quite accurately, the TOA measurement that requires the correlation of the received signal with the previously known signal content can be obtained much faster. Component (C) may also be reduced by obtaining measurements in parallel from multiple entities (such as from multiple base stations) rather than serially from only one entity. Component (D) may be reduced by specifying a position calculation entity close to the source of the position measurements, such as specifying the target UE for position calculation when the UE provides at least some measurements, or specifying a position calculation entity in the radio access network (RAN) rather than in the core network (CN) when the UE and / or a base station in the RAN provides measurements. Component (E) can be reduced by using a faster processor for position calculation (e.g., as in a location server or higher-end target UE). Component (F) can be reduced by employing user plane delivery of the position estimate directly from the position calculation entity to the external client, which can avoid additional delays caused by intermediate (e.g., control plane) entities and can use high bandwidth.

[0029] One difference between the above approach and conventional location solutions is the reduction in latency of components (A), (B) and (F). Since the establishment of a series of continuous location measurements for the target UE only needs to be performed once or infrequently, conventional control plane procedures and signaling can be used to support the establishment. However, since the delivery of location reports to external clients increases the latency of each location report, user plane signaling and procedures that can minimize latency can be used to support the delivery. As part of the solution, when the control entity is part of a radio access network (RAN) (e.g., to reduce the latency of component (D)), efficient means for periodically changing the control entity and reconfiguring location measurements when the target UE moves to a new serving cell or a new serving base station can be supported.

[0030] Solutions are needed for reducing latency and improving signaling efficiency when providing location to external clients. Currently, no solution has been identified to achieve the desired latency reduction and signaling efficiency improvement. For example, for existing control plane (CP) location in 5G networks, location results or event reports (for triggered and periodic location) are passed (via network exposure function (NEF)) successively from user equipment (UE) to gNB, from gNB to application management function (AMF), from AMF to location management function (LMF), from LMF to gateway mobile location center (GMLC) and from GMLC to location service (LCS) client or application function (AF). Four or five intermediate entities with five or six interfaces increase both latency and signaling.

[0031] A solution discussed in this article is applied to event reporting for periodic and triggered locations, and a user plane (UP) connection is used to pass event reports from the UE directly to the LCS client or AF (1 hop). The solution in this article also allows event reporting via LMF or GMLC (2 hops) or via LMF and GMLC (3 hops) through a user plane connection. The solution discussed in this article includes a defined protocol layer on the user plane (Internet Protocol (IP), Transmission Control Protocol (TCP), Transport Layer Security (TLS), supplementary services). Support for UP connections is provided through LMF or GMLC, wherein the use of LMF allows the use of more positioning methods, and the use of GMLC allows event reporting to have better security and monitoring. The solution also allows the UE to report the status of UP event reporting to the LMF and GMLC via the CP. In addition, a process for event reporting is defined, and the process is suitable for existing CP processes. In addition, cancellation of event reporting and LMF changes are supported via the CP.

[0032] Figure 1A and Figure 1BA network architecture supporting very low latency location services (VLLLS) for non-roaming UEs is shown, and Figure 2 The corresponding network architecture for roaming UE is shown. Figure 1A , Figure 1B and Figure 2 It may be consistent or partially consistent with the location solution defined by the 3rd Generation Partnership Project (3GPP). It may be noted that references to specific 3GPP technical specifications are referred to as "3GPP TS" or simply "TS" followed by the number of the corresponding technical specification.

[0033] Figure 1A The communication system 100 is illustrated as including a UE 105, which is referred to herein as a "target UE" because the UE 105 may be the target of a location request. Figure 1A Also shown are components of a fifth generation (5G) network (which may also be referred to as a 5G system (5GS)) including a next generation RAN (NG-RAN) 112 including base stations (BSs) sometimes referred to as new radio (NR) Node Bs or gNBs 110-1, 110-2, 110-3, and 110-4 (collectively and generally referred to herein as gNB 110) and a 5G core network (5GCN) 150 that communicates with external clients 130. Figure 1A As shown in box 133 in (where the dashed line shows an optional feature), communication between the external client 130 and the 5GCN 150 may optionally be carried out via the Internet. 5G networks may also be referred to as new radio (NR) networks; NG-RAN 112 may be referred to as NR RAN or 5GRAN; and 5GCN150 may be referred to as the next generation (NG) core network (NGC). The communication system 100 may further utilize information from a space vehicle (SV) 190 of a global navigation satellite system (GNSS) such as GPS, GLONASS, Galileo, or BeiDou, or some other local or regional satellite positioning system (SPS) such as IRNSS, EGNOS, or WAAS. Additional components of the communication system 100 are described below. The communication system 100 may include additional or alternative components.

[0034] Figure 1A Also shown are a serving gNB (gNB) 110-1 for the target UE 105 and some neighbor gNBs (gNB) 110-2, 110-3, and 110-4. The gNB 110 may be any gNB 110 capable of receiving and measuring uplink (UL) signals sent by the target UE 105 and / or capable of sending downlink (DL) reference signals (RS) that may be received and measured by the target UE 105.

[0035] The entity in NG-RAN 112 that transmits DL reference signals (RS) to be measured by target UE 105 for a particular location session is generally referred to as a "transmission point" (TP), and may include one or more of gNB 110-1, gNB 110-2 (if different from gNB 110-1), and gNBs 110-3, 110-4. In some cases, gNB 110-1, gNB 110-2, gNB 110-3, 110-4 may each include multiple TPs (e.g., where each TP is associated with a different cell and / or uses a different antenna or a different set of antenna elements).

[0036] The entity in the NG-RAN that receives and measures the UL signals (e.g., RS) sent by the target UE 105 for a specific location session is generally referred to as a "reception point" (RP), and may include one or more of gNB 110-1, gNB 110-2 (if different from gNB 110-1), and gNBs 110-3, 110-4. In some cases, gNB 110-1, gNB 110-2, gNB 110-3, 110-4 may each include multiple RPs (e.g., where each RP is associated with a different cell and / or uses a different antenna or a different set of antenna elements).

[0037] It should be noted that Figure 1A Only generalized illustrations of various components are provided, any or all of which may be utilized as appropriate, and each component may be repeated or omitted as desired. Specifically, although only one UE 105 is illustrated, it should be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the communication system 100. Similarly, the communication system 100 may include a greater or lesser number of SVs 190, gNBs 110, external clients 130, and / or other components. The illustrated connections connecting 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. In addition, the components may be rearranged, combined, separated, replaced, and / or omitted depending on the desired functionality.

[0038] Although Figure 1AA 5G-based network is illustrated, but similar network implementations and configurations may be used for other communication technologies, such as 3G, Long Term Evolution (LTE), and IEEE 802.11 WiFi, etc. For example, in the case of using a wireless local area network (WLAN) (e.g., an IEEE 802.11 radio interface), the UE 105 may communicate with an access network (AN) (rather than an NG-RAN), and accordingly, the component 112 is sometimes referred to herein as an AN or a radio access network (RAN), and is denoted 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 may be connected to a non-3GPP interworking function (N3IWF) (e.g., in the 5GCN 150) ( Figure 1A ), where N3IWF is connected to AMF 154.

[0039] As used herein, target UE 105 can be any electronic device and can be referred to as equipment, mobile device, wireless device, mobile terminal, terminal, mobile station (MS), terminal (SET) enabling secure user plane location (SUPL) or some other name. Target UE 105 can be a stand-alone device or can be embedded in another device (e.g., factory tool or vehicle) to be monitored or tracked. In addition, UE 105 can correspond to smart watches, digital glasses, fitness monitors, smart cars, smart home appliances, cellular phones, smart phones, laptop computers, tablet devices, PDAs, tracking devices, control devices or some other portable or removable devices. UE 105 may include a single entity or may include multiple entities, such as in a personal area network where a user can adopt audio, video, and / or data I / O devices, and / or body sensors and separate wired or wireless modems. Typically, although not necessarily, the UE 105 may utilize one or more radio access technologies (RATs) 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), Wireless communications may be supported using BT, WiMAX, 5G New Radio (NR) (e.g., using NG-RAN 112 and 5GCN 150), etc. UE 105 may also support wireless communications using a wireless local area network (WLAN), which may be connected to other networks (e.g., the Internet) using, for example, a digital subscriber line (DSL) or packet cable. Using one or more of these RATs may allow UE 105 (e.g., via Figure 1AElements of the 5GCN 150 not shown in the figure, or possibly via a Gateway Mobile Location Center (GMLC) 155) communicate with the external client 130 and / or allow the external client 130 (e.g., via the GMLC 155) to receive location information about the UE 105.

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

[0041] In certain implementations, UE 105 may have circuitry and processing resources capable of obtaining location-related measurements. Location-related measurements obtained by UE 105 may include measurements of signals received from 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-based transmitter fixed at a known location (e.g., such as gNB 110). Subsequently, UE105, gNB 110-2, or a separate location server (e.g., LMF 152) to which UE 105 may transmit measurements may use any of a number of positioning methods (e.g., such as GNSS, Assisted GNSS (A-GNSS), Advanced Forward Link Trilateration (AFLT), Observed Time Difference of Arrival (OTDOA), WLAN (also known as WiFi) positioning, Angle of Departure (AOD), Angle of Arrival (AOA), multi-cell round-trip signal propagation time (multi-RTT), or enhanced cell ID (ECID), or a combination thereof) to obtain a position estimate for UE 105 based on these location-related measurements. In some of these techniques (e.g., A-GNSS, AFLT, and OTDOA), pseudoranges or timing differences may be measured at a UE 105 relative to three or more ground-based transmitters (e.g., gNB 110) fixed at known locations or relative to four or more SVs 190 with accurately known orbit data, or a combination thereof, based at least in part on pilots, positioning reference signals (PRS), or other positioning-related signals transmitted by these transmitters or satellites and received at the UE 105.

[0042] A location server (such as LMF 152) may be capable of providing positioning assistance data to UE 105, for example, including information about signals to be measured (e.g., expected signal timing, signal decoding, signal frequency, signal Doppler), the location and identity of ground transmitters (e.g., gNB 110), and / or signal, timing, and orbit information for GNSS SV 190 to facilitate positioning techniques such as A-GNSS, AFLT, OTDOA, AOD, multi-RTT, and ECID. This facilitation may include improving the accuracy of signal acquisition and measurements made by UE 105, and in some cases, enabling UE 105 to calculate its estimated position based on the position measurements. For example, LMF 152 may include an almanac (also referred to as a base station almanac (BSA)) that indicates the location and identity of cellular transceivers and / or local transceivers in one or more specific areas (such as a specific venue), and may provide information describing signals transmitted by cellular base stations or APs (e.g., gNB 110), such as transmit power and signal timing. UE 105 can obtain signal strength measurements (e.g., received signal strength indication (RSSI)) for signals received from a cellular transceiver and / or a local transceiver, and / or can obtain a signal-to-noise ratio (S / N), a reference signal received power (RSRP), a reference signal received quality (RSRQ), a time of arrival (TOA), an angle of arrival (AOA), an angle of departure (AOD), a receive time-transmit time difference (Rx-Tx), or a round-trip signal propagation time (RTT) between UE 105 and a cellular transceiver (e.g., gNB 110) or a local transceiver (e.g., a WiFi access point (AP)). UE 105 may communicate these measurements to a location server (such as LMF 152) to determine the location of UE 105; or in some embodiments, the UE may use these measurements together with assistance data (e.g., terrestrial almanac data or GNSS satellite data (such as GNSS almanac and / or GNSS ephemeris information)) received from LMF 152 or broadcast by a base station (e.g., gNB 110) in NG-RAN 112 to determine the location of UE 105.

[0043] In the case of OTDOA, the UE 105 may measure a reference signal time difference (RSTD) between signals (such as a positioning reference signal (PRS), a cell-specific reference signal (CRS), or a tracking reference signal (TRS)) transmitted by a neighboring paired transceiver and a base station (e.g., gNB 110). The RSTD measurement may provide an arrival time difference between signals (e.g., TRS, CRS, or PRS) received from two different transceivers at the UE 105. The UE 105 may return the measured RSTD to the LMF 152, which may calculate an estimated position of the UE 105 based on the known position of the measured transceiver and the known signal timing. In some implementations of OTDOA, the signals (e.g., PRS signals or CRS signals) used for RSTD measurements may be accurately synchronized by the transceivers to a universal time (such as GPS time or coordinated universal time (UTC)), for example, using a GPS or GNSS receiver at each transceiver to accurately obtain the universal time.

[0044] In some implementations, network-based positioning methods may be used to locate the target UE 105. Using these methods, entities in the network (such as gNB 110) may measure UL signals transmitted by the UE 105. These UL signals may contain or include UL reference signals, such as UL positioning reference signals (PRS). The entity (e.g., gNB 110) that obtains the position measurement may then pass the position measurement to a location server (e.g., LMF 152), which may calculate the location of the target UE 105. Examples of UL position measurements may include RSSI, RSRP, RSRQ, TOA, Rx-Tx, AOA, and RTT. An example of a network-based positioning method may be an uplink time difference of arrival (UTDOA) method, which may utilize TOA measurements obtained by the gNB 110, the timing of which is accurately synchronized or consistent with a universal absolute time, such as GPS time. Another example of a network-based positioning method may be ECID, which may utilize any of RSSI, RSRP, RSRQ, TOA, Rx-Tx, AOA, and RTT measurements.

[0045] Using the UE-assisted positioning method, the UE 105 may obtain location measurements (e.g., measurements of RSSI, Rx-Tx, RTT, RSTD, RSRP, and / or RSRQ for the gNB 110, or measurements of GNSS pseudorange, code phase, and / or carrier phase for the SV 190) and transmit these measurements to an entity performing location server functions (such as LMF 152) to calculate a position estimate for the UE 105. Using the UE-based positioning method, the UE 105 may obtain location measurements (e.g., which may be the same or similar to the location measurements of the UE-assisted positioning method), and the position of the UE 105 may be additionally calculated (e.g., with the aid of assistance data received in a point-to-point manner from a location server (such as LMF 152) or broadcast by the gNB 110).

[0046] The estimate of the location of the UE 105 may be referred to as location, location estimate, location fix, fix, position, position estimate, or position fix, and may be geographic, thereby providing location coordinates (e.g., latitude and longitude) about the UE 105, 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, the location of the UE 105 may be expressed as a municipal location (e.g., a postal address or a designation of a point or smaller area in a building, such as a particular room or floor). The location of the UE 105 may also be expressed as an area or volume (geographically or municipally defined) within which the UE 105 is expected to be located with a certain probability or confidence level (e.g., 67%, 95%, etc.). The location of UE 105 may also be a relative location, including, for example, a distance and direction defined relative to a certain origin at a known location or relative X, Y (and Z) coordinates, which may be defined geographically, in municipal form, or with reference to a point, area, or volume indicated on a map, floor plan, or building plan. The location may be expressed as an absolute location estimate of UE 105 (such as location coordinates or address) or a relative location estimate of UE 105 (such as a distance and direction relative to a previous location estimate or relative to a known absolute location). The location of UE 105 may include a linear velocity, angular velocity, linear acceleration, angular acceleration, angular orientation (e.g., orientation of UE 105 relative to a fixed global or local coordinate system), an identifier of a triggering event for locating UE 105, or some combination thereof. For example, a triggering event may include an area event, a motion event, or a speed event. For example, an area event may be that UE 105 moves to a defined area, moves out of the area, and / or stays in the area. For example, a motion event may include that the UE 105 moves a threshold straight-line distance or a threshold distance along the UE trajectory. For example, a speed event may include that the UE 105 reaches a minimum or maximum speed, a threshold increase and / or decrease in speed, and / or a threshold change in direction. In the description contained herein, the use of the term "position" may include any of these variants, unless otherwise noted. When calculating the position of the UE 105, local x, y, and (possibly) z coordinates are typically solved, and then the local coordinates are converted to absolute coordinates (e.g., with respect to latitude, longitude, and altitude above or below mean sea level) where necessary.

[0047] like Figure 1A As shown, pairs of gNBs 110 in the NG-RAN 112 may be connected to each other, e.g. Figure 1AThe gNBs 110 are shown as being connected to each other directly or indirectly via other gNBs 110. Access to the 5G network is provided to the UE 105 via wireless communications between the UE 105 and one or more of the gNBs 110, which may provide wireless communications access to the 5GCN 150 on behalf of the UE 105 using 5G (e.g., NR). Figure 1A , it is assumed that the serving gNB (gNB) for UE 105 is gNB 110-1, although other gNBs (e.g., gNB 110-2 and / or gNB 110-3) may serve as serving gNBs if UE 105 moves to another location, or may serve as secondary gNBs to provide additional throughput and bandwidth to UE 105. Figure 1A Some of the gNBs 110 (e.g., gNB 110-3 or gNB 110-4) may be configured to function as positioning-only beacons, which may send signals (e.g., directional PRS) to assist in positioning of UE 105, but may not receive signals from UE 105 or from other UEs.

[0048] As mentioned, although Figure 1A Nodes configured to communicate according to a 5G communication protocol are depicted, but nodes configured to communicate according to other communication protocols (e.g., such as an LTE protocol) may also be used. Such nodes configured to communicate using different protocols may be controlled, at least in part, by the 5GCN 150. Thus, the NG-RAN 112 may include any combination of gNBs, evolved Node Bs (eNBs), or other types of base stations or access points. For example, the NG-RAN 112 may include one or more next generation eNBs (ng-eNBs) (not shown) that provide LTE wireless access to the UE 105 and may be connected to entities in the 5GCN 150 (such as the AMF 154).

[0049] The gNB 110 and / or ng-eNB may communicate with an access and mobility management function (AMF) 154, which may communicate with a location management function (LMF) 152 for positioning functionality. The AMF 154 may support the mobility of the UE 105, including cell changes and handovers, and may participate in supporting signaling connections to the UE 105 and may help establish and release protocol data unit (PDU) sessions for the UE 105 supported by the UPF 151. Other functions of the AMF 154 may include: termination of control plane (CP) interfaces from the NG-RAN 112; termination of non-access stratum (NAS) signaling connections from a UE such as the UE 105, NAS ciphering and integrity protection; registration management; connection management; reachability management; mobility management; access authentication and authorization.

[0050] The LMF 152 may support positioning of the UE 105 when the UE 105 accesses the NG-RAN 112, and may support various positioning procedures / methods, such as Assisted GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA), Real-Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cell ID (ECID), Angle of Arrival (AOA), Angle of Departure (AOD), Multi-RTT, WLAN Positioning, UTDOA, and / or other positioning methods. The LMF 152 may also process location service requests for the UE 105, for example, received directly or indirectly from the GMLC 155 or the NEF 159. In some embodiments, the node / system implementing the LMF 152 may additionally or alternatively implement other types of location support modules, such as an Enhanced Serving Mobile Location Center (E-SMLC) or a Secure User Plane Location (SUPL) Location Platform (SLP). It will be noted that in some embodiments, at least a portion of the positioning functionality (including deriving the position of the UE 105) may be performed at the UE 105 (e.g., using signal measurements of signals sent by wireless nodes and assistance data provided to the UE 105).

[0051] The GMLC 155 may support location requests for the UE 105 received from the external client 130, and may forward such location requests to the serving AMF 154 of the UE 105. The AMF 154 may then forward the location request to the LMF 152, which may obtain one or more location estimates for the UE 105 (e.g., according to the request from the external client 130) and may return the location estimates to the AMF 154, which may return the location estimates to the external client 130 via the GMLC 155. The GMLC 155 may contain subscription information for the external client 130, and may authenticate and authorize the location request for the UE 105 from the external client 130. The GMLC 155 may further initiate a location session for the UE 105 by transmitting a location request for the UE 105 to the AMF 154, and may include in the location request the identity of the UE 105 and the type of location requested (e.g., such as a current location or a sequence of periodic or triggered locations).

[0052] AMF 154 and gNB 110 may communicate using New Radio Positioning Protocol A (NRPPa). NRPPa may be defined in 3GPP TS 38.455 and may be the same, similar, or an extension of LTE Positioning Protocol A (LPPa) defined in 3GPP TS 36.455, where NRPPa messages are passed between gNB 110 and AMF 154. Additionally, AMF 154 and UE 105 may communicate using LTE Positioning Protocol (LPP) defined in 3GPP Technical Specification (TS) 37.355, where LPP messages are passed between UE 105 and serving AMF 154 via serving gNB 110-1 of UE 105. For example, LPP messages may be passed between AMF 154 and UE 105 using a 5G non-access stratum (NAS) protocol. The LPP protocol may be used to support positioning of UE 105 using UE-assisted positioning methods and / or UE-based positioning methods such as Assisted GNSS (A-GNSS), Real-Time Kinematics (RTK), Wireless Local Area Network (WLAN), Observed Time Difference of Arrival (OTDOA), AOD, AOA, Multi-RTT, and / or Enhanced Cell Identity (ECID). The NRPPa protocol may be used to support positioning of UE 105 using network-based and network-assisted positioning methods such as ECID and Multi-RTT (e.g., when used with measurements obtained by gNB 110 or received from gNB 110 of UE 105) and / or may be used by LMF 152 to obtain location-related information from gNB 110, such as parameters defining positioning reference signal (PRS) transmissions from gNB 110 to support OTDOA, AOD, and Multi-RTT.

[0053] The gNB 110 may use the Next Generation Application Protocol (NGAP) (e.g., as defined in 3GPP TS 38.413) to communicate with the AMF 154. The NGAP may enable the AMF 154 to request the location of the target UE 105 from the gNB 110-1 of the target UE 105, and may enable the gNB 110-1 to return the location of the UE 105 to the AMF 154.

[0054] The gNBs 110 may communicate with each other using an Xn Application Protocol (XnAP) (e.g., as defined in 3GPP TS 38.423). The XnAP may allow one gNB 110 to request another gNB 110 to obtain UL location measurements for a target UE 105 and return these UL location measurements. The XnAP may also enable a gNB 110 to request another gNB 110 to send a downlink (DL) RS or PRS to enable the target UE 105 to obtain a DL location measurement of the sent DL RS or PRS. In some implementations, the XnAP may be used to transmit location-related messages belonging to a higher protocol level (e.g., NRPPa) between gNBs 110 to request UL location measurements and / or the transmission of DL RS or PRS signals, in which case the XnAP may be used only as a transmission protocol between paired gNBs 110.

[0055] The gNB (e.g., gNB 110-1) may communicate with the target UE 105 using a radio resource control (RRC) protocol (e.g., as defined in 3GPP TS 38.331). RRC may allow the gNB 110 (e.g., gNB 110-1) to request location measurements of DL RS or DL ​​PRS transmitted by the gNB 110 and / or by other gNBs 110 from the target UE 105 and return these location measurements. RRC may also enable the gNB 110 (e.g., gNB 110-1) to request the target UE 105 to transmit UL RS or PRS so that the gNB 110 or other gNB 110 can obtain UL location measurements of the transmitted UL RS or PRS. The gNB (e.g., gNB 110-1) may also communicate with the target UE 105 using lower protocol levels (e.g., layer 1 (L1) and / or layer 2 (L2) protocol levels), which may be used by the UE 105 to return location measurements. RRC may also be used to transmit one or more LPP messages between UE 105 and gNB 110-1, wherein the one or more LPP messages, rather than RRC, are used to request location measurement to the target UE 105 and / or request the target UE 105 to send a UL RS or PRS.

[0056] The information provided by gNB 110 to LMF 152 using NRPPa may include timing and configuration information for PRS transmissions of gNB 110 and the location coordinates of the gNB. LMF 152 may then provide some or all of this information to UE 105 as assistance data in an LPP message.

[0057] The RRC and / or LPP messages transmitted from the LMF 152 to the UE 105 may instruct the UE 105 to do any of a variety of things, depending on the desired functionality. For example, the LPP and / or RRC messages may include instructions for the UE 105 to obtain measurements for GNSS (or A-GNSS), WLAN, AOD, multi-RTT, and / or OTDOA (or some other positioning method). In the case of OTDOA, the LPP or RRC message may instruct the UE 105 to obtain one or more measurements (e.g., RSTD measurements) of PRS signals transmitted within a particular cell supported by a particular gNB 110 (or supported by one or more ng-eNBs or eNBs). The UE 105 may transmit the measurements back to the LMF 152 in the LPP message.

[0058] In some embodiments, LPP may be augmented or replaced by a NR or NG positioning protocol (NPP or NRPP) that supports positioning methods such as OTDOA, multi-RTT, 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.

[0059] The gNB 110 in the NG-RAN 112 may also broadcast positioning assistance data to each UE (such as UE 105).

[0060] like Figure 1A As illustrated, a unified data management (UDM) 156 may be connected to the GMLC 155. The UDM 156 is similar to a Home Subscriber Server (HSS) for LTE access, and if desired, the UDM 156 may be combined with the HSS. The UDM 156 is a central database that contains user-related and subscription-related information for the UE 105 and may perform the following functions: UE authentication, UE identification, access authorization, registration and mobility management, subscription management, and short message service management.

[0061] To support services including location services for Internet of Things (IoT) UEs from external clients 130, a network exposure function (NEF) 159 may be included in the 5GCN 150. The NEF may also be referred to as a service capability exposure function (SCEF), for example for a UE 105 having LTE access to the EPC instead of 5G NR radio access to the 5GCN 150. The NEF 159 may support secure exposure of capabilities and events about the 5GCN 150 and the UE 105 to the external clients 130 (these capabilities and events may therefore be referred to as application functions (AFs)), and may enable secure provision of information from the external clients 130 to the 5GCN 150. In the context of location services, the NEF 159 may be used to obtain the current or last known location of the UE 105, to obtain an indication of a change in the location of the UE 105, or to obtain an indication of when the UE 105 becomes available (or reachable). The external client 130 may access the NEF 159 directly or may access a service capability server (SCS, Figure 1A 155), the service capability server (SCS) may access the NEF 159 on behalf of the external client 130 to provide location information to the external client 130 of the UE 105 via the SCS. The NEF 159 may be connected to the GMLC 155 to support the last known location, current location, and / or deferred periodic and triggered location of the UE 105. If desired, the NEF 159 may include the GMLC 155, or may be combined with the GMLC.

[0062] User plane function (UPF) 151 may support voice and data bearers for UE 105 and may enable voice and data access to other networks (such as the Internet) for UE 105. The functions of UPF 151 may include: external PDU session interconnection points to data networks, packet (e.g., Internet Protocol (IP)) routing and forwarding, user plane portion of packet inspection and policy rule enforcement, quality of service (QoS) handling of the user plane, downlink packet buffering, and downlink data notification triggering.

[0063] Figure 1A One example of a user plane signaling path that may be used to report the UE location to the external client 130 or the AF 132 is illustrated by thick arrow 162 .

[0064] Figure 1B Illustrated Figure 1A164, the user plane signaling path may be used to report the UE location to the external client 130 or AF 132 via the LMF 152 or, as shown by the dashed line 164, via the LMF 152 and the GMLC 155. For example, the LMF 152 may determine a location estimate for the UE 105 based on location information provided to the LMF 152 by the UE 105 (e.g., using a UE-assisted positioning method). The LMF 152 may then transmit the location estimate to the external client 130 or AF 132 directly (on path 163) or via the GMLC 155 (on path 164). In some implementations, the user plane signaling path may only pass through the GMLC 155 ( Figure 1B not shown).

[0065] Figure 2 Illustrated with Figure 1A 100, but the communication system supports the location of roaming UE 105. In the communication system 200, the core network 5GCN 150V that communicates with the UE 105 via the NG-RAN 112 is part of a visited network (i.e., a visited public land mobile network (VPLMN)), which communicates with a home network 5GCN 150H that is part of a home public land mobile network (HPLMN). In the communication system 200, the VPLMN 5GCN150V includes an AMF 154 that communicates with the LMF 152. The AMF 154 also communicates with a UDM 156 located, for example, in the HPLMN 5GCN 150H. The VPLMN 5GCN 150V also includes a visited gateway mobile location center (VGMLC) 155V, which is similar to the visited gateway mobile location center. Figure 1A The GMLC 155 in the non-roaming communication system 100 is designated as 155V to indicate that it is located in the visited network of the UE 105. Figure 2 As illustrated, the VGMLC 155V is connected to the AMF 154 in the VPLMN 5GCN 150V.

[0066] As illustrated, the HPLMN 5GCN 150H may include a home GMLC (HGMLC) 155H, which may be connected to a VGMLC 155V (e.g., via the Internet). The HGMLC 155H may be similar to Figure 1A150H and is designated as 155H to indicate that it is located in the home network of the UE 105. The VGMLC 155V and the HGMLC 155H may sometimes be collectively referred to herein and generally referred to as the GMLC 155. The HGMLC 155H communicates with the external client 130 and the UDM 156 in the HPLMN 150H. The HGMLC 155H may provide location access to the UE 105 on behalf of the external client, such as the external client 130.

[0067] HPLMN 5GCN 150H may also include NEF 159 that may be connected to HGMLC 155H. One or more of HGMLC 155H and NEF 159 may be connected to external client 130, for example, via another network such as the Internet. In some cases, a client located in another PLMN ( Figure 2 A requesting GMLC (RGMLC) in FIG. 150 (not shown) may connect to the HGMLC 155H (eg, via the Internet) to provide location access to the UE 105 on behalf of an external client connected to the RGMLC.

[0068] As further illustrated, the HPLMN 5GCN 150H may include a home UPF 151H that may be connected (e.g., via the Internet) to a visited UPF 151V in the VPLMN 5GCN 150V. The UPFs 151H and 151V may be similar to Figure 1A The UPF 151 in the non-roaming communication system is designated as 151H and 151V to indicate the location of the UE 105 in the home network and the visited network, respectively.

[0069] Low latency location can be supported via user plane positioning, which can be applied to event reporting such as periodic or triggered deferred 5G core mobile terminated location request (5GC-MT-LR). The target UE 105 can use the user plane connection to report events to the LCS client 130 or AF 132 directly or via LMF 152 or GMLC 155 (or H-GMLC 155H). When reporting directly to the LCS client 130 or AF 132 or reporting via GMLC 155 or H-GMLC 155H, the UE 105 can transmit a supplementary service event report including a location estimate via the user plane connection. This can significantly reduce end-to-end latency because the event report does not need to be delivered via the control plane connection through NG-RAN 112, AMF 154, LMF 152, GMLC 155 and (possibly) NEF 159. This also improves signaling efficiency. When reporting via LMF 152, UE 105 transmits a supplementary service event report to LMF 152 via a user plane connection, which includes one or more LPP messages. LMF 152 then verifies or determines the position estimate and transmits the event report with the position estimate to LCS client 130 or AF 132 via a second user plane connection. This still reduces latency and improves signaling efficiency. Control plane associations between UE 105 and LMF 152, between LMF 152 and GMLC 155 (V-GMLC 155V / H-GMLC 155H), and between GMLC 155 (H-GMLC 155H) and LCS client 130 or between NEF 159 and AF 132 are retained to allow the status of the event report to be delivered to GMLC 155 (H-GMLC 155H) (and NEF 159, if used) and to support cancellation of event reports using existing control plane procedures.

[0070] Figure 1A , Figure 1B and Figure 2How a location session may be established and how location reporting may be supported is also illustrated at a high level by the thick arrows. To establish (or cancel) a location session for the target UE 105, a control plane signaling path may be used, as indicated by the thick arrows 161 and 261. Using the control plane (CP) path, a control plane procedure is used in which the external client 130 transmits a location request to the GMLC 155 (or to the HGMLC 155H when roaming) or to the NEF 159, which forwards the location request to the serving AMF 154 of the target UE 105 (e.g., via the VGMLC 155V in the case of a roaming target UE 105). The serving AMF 154 then forwards the location request to the LMF 152, which is returned to the AMF 154 and transmitted to the gNB 110-1 of the target UE 105, which acts as the gNB for the location session or forwards the location request to a separate gNB 110-2. Figure 1A , Figure 1B and Figure 2 Only the position establishment via GMLC 155 or HGMLC 155H and VGMLC 155V rather than via NEF 159 is shown.

[0071] For location reporting, UE 105 may use a user plane connection to report events to LCS client 130 or AF 132, or as Figure 1A and Figure 2 Direct reporting as indicated by thick arrows 162 and 262 in FIG. 1 , or as indicated by thick arrows 162 and 262 in FIG. Figure 1B The target UE 105 is reported via LMF 152 and / or GMLC 155 as shown by the thick arrows 163 and 164 in FIG. Figure 2 1) and possibly roaming via Internet 133, UE 105 may access the network via gNB 110-1, UPF 151 (as shown in FIG. Figure 1A and Figure 1B The illustrated) or UPF 151V and UPF 151H transmit the location report to the external client 130 or AF 132. When the two endpoints are not in the same trust domain, the user plane connection can use encryption and mutual authentication.

[0072] like Figure 1B As illustrated by UP paths 163 and 164, UP connectivity may be provided by LMF 152 and / or GMLC 155, wherein the use of LMF 152 allows for more positioning methods and the use of GMLC 155 allows for better security and monitoring of incident reporting. Figure 2 The LMF 152 and / or H-GMLC 155H in provide a similar UP connection for the roaming UE 105.

[0073] For location reporting from UE 105 via the user plane, no restriction on the target UE 105 mobility state may be required.

[0074] Figure 3A A protocol layer 300 is shown that may be used when a target UE 105 delivers a location report to an external client 130 or AF 132 via user plane signaling. The UE 105 may deliver the location report to the external client 130 or AF 132 using IP, TCP, optionally using Transport Layer Security (TLS) and (possibly) Hypertext Transfer Protocol (HTTP) (e.g., HTTP / 2), or SUPL ULP. To deliver the location report to the UPF 151, the UE 105 may use a PDU session between the UE 105 and the UPF 151 that uses protocols defined by 3GPP for this purpose, including the NR physical layer (PHY), the medium access control (MAC) protocol, the radio link control (RLC) protocol, the packet data convergence protocol (PDCP), the service data protocol (SDAP), GTP-U, and UDP / IP. Figure 3A An advantage of the ULP in the gNB 110 may be the widespread support for the ULP in many UEs 105 to support the OMA SUPL location solution. Adapting the ULP support in the UE 105 to enable a combined control plane and user plane location solution as described herein may thus have low UE 105 specific implementation impact. Information referred to herein as "location context information" may be required in the participating entities (e.g., the UE 105 and the gNB 110) to support sending UL RS and DL RS, obtaining UL location measurements and DL location measurements, communicating location measurements to the gNB 110, and / or delivering location reports to the external clients 130.

[0075] Figure 3B 350 is shown as a protocol layer that can be used when the target UE 105 delivers a location report to the external client 130 or AF 132 using user plane signaling directly or optionally via the LMF 152 and / or H-GMLC 155. The protocol layer is similar to Figure 3A1. The present invention relates to a protocol layering in which the UE 105 transmits location reports to the external client 130 or AF 132 using IP, TCP, optionally TLS, and one of HTTP, SUPL ULP, or a supplementary service protocol. The location event reports are delivered from the UE 105 to the LCS client 130 or AF 132 using data transmission through the UPF 151. The delivery can be direct or can be made via the LMF 152 and / or H-GMLC 155 (shown in dashed lines). The delivery via the LMF 152 allows the LMF 152 to determine or verify the location estimate and, if necessary, to exchange LPP messages with the target UE 105 via the user plane to perform positioning of the target UE 105. The delivery via the H-GMLC 155 enables the H-GMLC 155 to monitor the event reports made by the target UE 105 and avoids the UE 105 directly interacting with the LCS client 130 or AF 132 data, which may pose a security risk to either entity. A version of TLS (eg, TLS 1.2) may be used to enable secure data connections. Figure 3B The LMF 152 and / or H-GMLC 155 shown only exist when event reports are delivered to the LCS client 130 or AF 132 via the LMF 152 and / or H-GMLC 155 instead of being delivered directly to the LCS client 130 or AF 132. The event reports may each include the type of event indication, the location estimate of the UE 105, and the time of the event or the time of the location. When delivering the event report via the LMF 152, the UE 105 may transmit an event report formatted according to a supplementary service protocol (e.g., a protocol defined in 3GPP TS 24.080), where the LMF 152 may convert the event report into an event report formatted according to HTTP or SUPL ULP for delivery to the H-GMLC 155 (if present on the user plane path) and the LCS client 130 or AF 132.

[0076] Figure 4A An example process of the target UE 105 performing location reporting using the user plane is shown. Figure 4A Applied to Figure 2 The roaming target UE 105 in the communication system 200 in FIG. Figure 1A The process of the non-roaming target UE 105 in the communication system 100 may include Figure 4A A subset of the process shown in . The operations in this process are Figure 4A The phases are shown with numbers in the figure and are referred to as phases in this document. This convention is also used for the other figures described below.

[0077] exist Figure 4AAt stage 1 in the , the external location service (LCS) client 130 transmits a location request for a periodic or triggered location event of the target UE 105 to the HGMLC 155H in the HPLMN 5GCN150H of the target UE 105. The location request provides the type of location report requested and the associated parameters. For periodic location, the request includes the time interval between consecutive location reports, the total number of reports, and the location QoS. For triggered reports for area events, the request includes detailed information of the target area, whether the triggering event to be reported is the target UE 105 within the target area, entering the target area, or leaving the target area, whether the event report should include a UE location estimate, and if so, including the location QoS and the duration of the report. For triggered reports for motion events, the request includes a threshold linear distance for triggering a location report, whether the event report should include a UE location estimate, and if so, including the location QoS and the duration of the report. More than one type of location report may be requested at stage 1 (e.g., the external client 130 may request periodic location reports and triggered location reports for area events or motion events). The location request may also include user plane information. The user plane information may include a request to transmit a location report via the user plane and an address (e.g., an IP address, FQDN, or URI) to which the location report should be transmitted via the user plane, as well as security information. The security information may include encryption and / or authentication keys (including public or private keys) and an identification of the external client 130 that may be used to establish a TCP connection and / or a TLS session between the target UE 105 and the external client 130. The location request transmitted at stage 1 may also include a location session reference to identify the location report transmitted later at stage 25.

[0078] It is noted that the external LCS client 130 may alternatively be a network function (NF) or an application function (AF) accessing the HGMLC 155H via the NEF 159 .

[0079] exist Figure 4A At stage 2 in , HGMLC 155H may verify the target UE 105 privacy requirements by querying UDM 156 for the privacy subscription information of UE 105 and then verifying whether external client 130 is allowed to receive location information of UE 105. In case positioning of target UE 105 is not allowed, subsequent stages are skipped.

[0080] At stage 3, the HGMLC 155H invokes the Nudm_UECM_Get service operation towards the home UDM 156 of the target UE 105 using the GPSI or SUPI of the target UE 105 to obtain the serving AMF 154 address of the target UE 105 and optionally the VGMLC 155V address and the current access type.

[0081] It should be noted that the HGMLC 155H may also send a message to the HSS ( Figure 4A The address of the serving mobility management entity (MME) is queried (not shown) as described in 3GPP TS23.271. Then, the deferred EPC-MT-LR procedure for periodic and triggered location described in 3GPP TS23.271 may be performed instead of Figure 4A 4 to 35 in, for example, if the HSS returns the MME address, but the UDM 156 does not return the AMF address. In this case, postponing the EPC-MT-LR procedure may also invoke location reporting by the UE 105 via the user plane, which may be similar to the following for Figure 4A As described.

[0082] At stage 4, if no VGMLC 155V address was returned in stage 3, the HGMLC 155H may use the Network Repository Function (NRF) service in the HPLMN 5GCN 150H to select an available VGMLC 155V in the VPLMN 5GCN 150V based on the VPLMN identity contained in the AMF 154 address received in stage 3. The HGMLC 155H forwards the location request to the VGMLC 155V and includes the AMF 154 address, the target UE 105 identity (e.g., SUPI), any access type received at stage 3, and any privacy requirements of the target UE 105. The HGMLC 155H also includes the contact address of the HGMLC 155H (also referred to as the notification target address, such as a URI) and the location deferral request (LDR) reference number (also referred to as the notification correlation ID), which will be used for event and location reporting at stages 19 and 30. The HGMLC 155H also includes any user plane information received at stage 1, and may include other information received at stage 1, such as the location session reference and the type of periodic and / or triggered location reported requested.

[0083] At stage 5, the VGMLC 155V calls the Namf_Location_ProvidePositioningInfo request service operation to forward the location request including all the information received at stage 4 to the serving AMF 154. The VGMLC 155V may optionally determine the LMF 152 and then include the LMF 152 identity in the request transmitted to the AMF 154.

[0084] At stages 6 to 8, if AMF 154 supports deferred location requests for periodic or triggered location, AMF 154 returns an acknowledgement to the external LCS client 130 via VGMLC 155V and HGMLC 155H, indicating that the request for location is accepted. At this point, VGMLC 155V may optionally release resources used for the location request.

[0085] Note that as an optional optimization, VGMLC 155V may not be used. In this case, instead of performing stages 4 to 7, HGMLC 155H calls the Namf_Location_ProvidePositioningInfo request service operation to forward the location request directly to AMF 154. AMF 154 then returns an acknowledgement directly to HGMLC 155H.

[0086] At stage 9, if the target UE 105 is currently unreachable (e.g., using DRX or PSM), the AMF 154 waits for the target UE 105 to become reachable.

[0087] Note that, in the case where the target UE 105 moves to another AMF or moves to an enhanced packet core (EPC) supporting LTE access, when the target UE 105 becomes reachable, the old AMF 154 may return an event indication to the HGMLC 155H (as at stages 18 and 19) and may include the address of the new serving AMF or new serving MME (if known). If the new serving AMF or MME is unknown, the HGMLC 155H may repeat stages 2 and 3 to query the UDM 156 and HSS for the new AMF or new MME address. The HGMLC 155H may then restart the process from stage 3.

[0088] At stage 10, if the target UE 105 needs to be moved to the CM connected state, the AMF 154 performs a network triggered service request once the target UE 105 is reachable.

[0089] At stage 11, the AMF 154 may notify the target UE 105 and verify the UE privacy requirements based on any privacy requirements received from the HGMLC 155H in stages 4 to 5. If this occurs, the AMF 154 transmits a supplementary service location notification call to the target UE 105.

[0090] At stage 12, if stage 11 is performed for UE privacy verification, the target UE 105 notifies the user of the UE 105 (if there is a user) of the location request, and verifies the user permission if UE privacy is to be verified. The target UE 105 then returns a supplementary service location notification response to the AMF 154, indicating whether the user (or UE 105, if there is no user) grants or denies permission for the location request.

[0091] At stage 13, AMF 154 determines LMF 152, for example, based on the LMF 152 identity provided by VGMLC 155V in stage 5, the type of location request (e.g., QoS), and / or the current UE access type. AMF 154 then invokes the Nlmf_Location_DetermineLocation request service operation towards LMF 152 to initiate a request for the deferred UE location. AMF 154 includes all the information received in stage 5, including the HGMLC 155H contact address, LDR reference number, and user plane information. The request also includes the LCS-related identifier, the serving cell identity of UE 105, the external client 130 type, and may include the required QoS and GAD shape supported by the external client 130.

[0092] At stage 14, LMF 152 initiates a UE positioning procedure (e.g., using UE-assisted and UE-based positioning procedures described in 3GPP TS 23.273 and / or network-assisted positioning procedures described in 3GPP TS 23.273). During this process, LMF 152 may request and obtain the target UE 105 positioning capabilities (e.g., which may indicate the types of periodic and triggered location supported by the target UE 105, the access types supported by the target UE 105 for event reporting, and whether the target UE 105 supports location reporting via the user plane). LMF 152 may also obtain the target UE 105 location, for example, in the case where the initial UE 105 location is requested by the external client 130 at stage 1.

[0093] At stage 15, and as part of stage 14, LMF 152 transmits a periodic triggered location request to the target UE 105 via the serving AMF 154 by invoking the Namf_Communication_N1N2MessageTransfer service operation. The periodic triggered location request carries the location request information received from AMF 154 at stage 13, including the HGMLC 155H contact address, LDR reference number and user plane information. The periodic triggered location request may indicate the allowed access type (e.g., one or more of NR, LTE access to 5GCN 150V, LTE access to EPC of VPLMN, WLAN (e.g., IEEE 802.11 WiFi) access to 5GCN 150V) for location reporting at stage 25, and may (e.g., based on the positioning capabilities of the target UE 105 obtained as part of stage 14 and the allowed access types) indicate certain allowed or required location measurements (or location estimates) for each location event reported at stage 22.

[0094] At stage 16, if the request in stage 15 can be supported, as part of stage 14, the target UE 105 returns an acknowledgment to the LMF 152, which is passed via the serving AMF 154 and delivered to the LMF 152 using the Namf_Communication_N1MessageNotify service operation. The target UE 105 may indicate in the acknowledgment whether user plane location reporting can be supported. The remaining stages in this document assume that location reporting via the user plane can be supported. When location reporting via the user plane cannot be supported, the process may continue according to periodic and triggered 5GC-MT-LR procedures, where the location report is returned to the external client 130 via control plane signaling.

[0095] Note that the periodic triggered location request transmitted at stage 15 and its acknowledgement at stage 16 may be a message for a positioning protocol (e.g., LPP) or may be a message for a separate protocol (e.g., Supplementary Service Protocol). In the latter case, each message may carry an embedded positioning protocol message to enable the LMF 152 to request or allow specific location measurements from the target UE 105 and / or for a specific positioning method based on the UE's location.

[0096] At stage 17, the LMF 152 invokes the Nlmf_Location_DetermineLocation response service operation towards the AMF 154 in response to the request at stage 13. The response includes any location obtained at stage 14, confirmation of whether periodic or triggered location was successfully activated in the target UE 105 according to stages 15 and 16, and an indication that user plane location reporting will be used. The LMF 152 may then release all resources used for the location request and cease support for the procedure.

[0097] At stage 18, the AMF 154 invokes the Namf_Location_EventNotify service operation towards the VGMLC 155V and includes any location received at stage 17, confirmation of whether periodic or triggered location has been successfully activated in the target UE 105, and an indication of user plane location reporting. The VGMLC 155V may be the same VGMLC 155V used in stages 5 and 6, or may be a different VGMLC 155V. In the case of a different VGMLC 155V, the AMF 154 includes the HGMLC 155H contact address and the LDR reference number. The AMF 154 may then release all resources used for the location request and cease support for the procedure.

[0098] At stage 19, the VGMLC 155V forwards the response received at stage 18 to the HGMLC 155H and includes the LDR reference number using the HGMLC 155H contact address received at stage 18 (for a different VGMLC 155V) or received and stored at stage 4 (for the same VGMLC 155V). The VGMLC 155V may then release all resources used for the location request and cease support for the process.

[0099] Note that as an optional optimization, instead of performing phases 18 and 19, the AMF 154 may directly invoke the Namf_Location_EventNotify service operation towards the HGMLC 155H (e.g., if VGMLC 155V is not used or if VGMLC 155V is no longer supported after phase 7).

[0100] At stage 20 , the HGMLC 155H forwards the response to the external LCS client 130 .

[0101] At stage 21, the target UE 105 monitors for the occurrence of the trigger or periodic event requested in stage 15. When a trigger event is detected at stage 15 and if the target UE 105 is camped on or connected to (or can otherwise access) an access type allowed by the LMF 152, the target UE 105 proceeds to stage 22. If the target UE 105 cannot access the allowed access type, then according to the requirements received from the LMF 152 at stage 15, the target UE 105 may skip reporting the trigger event or may report the trigger event at a later time when the allowed access type becomes available.

[0102] At stage 22, the target UE 105 obtains position measurements and determines a position estimate and (possibly) other position information (e.g., target UE velocity and / or orientation) from these position measurements, as requested at stage 15. The UE 105 may obtain position measurements of DL signals (e.g., PRS signals or TRS signals) sent by one or more gNBs 110 in the NG-RAN 112 according to the control plane. The UE 105 may also obtain position measurements of signals from other sources (e.g., GNSS SV 190 and / or WLAN AP) and / or from sensors in the UE 105. The UE 105 may then determine a position estimate for the UE 105 from these position measurements and possibly using assistance data broadcasted by and received from the NG-RAN 112 or received from the LMF 152 in the 5GCN 150 using control plane signaling (e.g., at an earlier time).

[0103] At stage 23, the target UE 105 performs a service request if in the CM idle state, or performs a resume request if in the RRC inactive state.

[0104] At stage 24, if a TCP connection and / or TLS session does not currently exist between the target UE 105 and the external client 130, the target UE 105 establishes a TCP connection and optional TLS session with the external client 130. This typically only occurs once, at any time after stage 15. For position reporting directly to the external client 130, the target UE 105 may use the address of the external client 130 received at stage 15 to establish a TCP connection, and may use any encryption and authentication keys received at stage 15 to establish a TLS session.

[0105] In a variation of Phase 24, when ULP is used instead of HTTP to transmit the location report, if a SUPL session does not currently exist, the UE 105 may establish a SUPL session with the external client 130, which may include establishing a TCP connection and an optional TLS session as described above. In this variation, the UE 105 may indicate at Phase 1 (e.g., at the ULP level and optionally in a SUPL START or SUPL TRIGGERED START message transmitted to the external client 130 as part of Phase 24) that the SUPL session is associated with the location request. For example, as part of Phase 24, the UE 105 may include a location session reference transmitted by the external client 130 at Phase 1 in a SUPL START or SUPL TRIGGERED START message transmitted to the external client 130.

[0106] At stage 25, the target UE 105 transmits a location report (also referred to as an event report) to the external client 130. The location report may include some or all of the location information determined at stage 22 as well as the target UE 105 identity (e.g., GPSI or SUPI), a location session reference, an address or indication of the external client 130, and / or the type of triggered or periodic event detected at stage 21. Figure 3A According to the protocol layering described above, the location report may be transmitted as a user plane message. If HTTP is used to transmit the location report at stage 25, the location report may include an HTTP POST message. If ULP is used to transmit the location report at stage 25, the location report may include a ULP message, such as a SUPL POS message, a SUPL POS INIT message, or a SUPL REPORT message.

[0107] At stage 26, the external client 130 may optionally return an acknowledgment to the target UE 105. If acknowledgments at the TCP level are deemed sufficient, acknowledgments may not be required. In some variants, the acknowledgment at stage 26 or a separate message from the external client 130 to the UE 105 may request some changes to the location reporting, such as a higher or lower location reporting periodicity, a higher or lower location QoS, or cancellation of location reporting. If HTTP is used to transmit the location report at stage 25, the acknowledgment at stage 26 may include an HTTP status 204 (no content) message or an HTTP status 200 OK message.

[0108] At stage 27, the target UE 105 continues to monitor for further periodic or triggering events and initiates stages 22 to 26 whenever a periodic or triggering event is detected.

[0109] At stage 28, to cancel the location request (e.g., if the target UE 105 is powered off or if the user wishes to cancel the location), the target UE 105 performs stage 23 if necessary and then transmits a Cancel Location Request message to the serving AMF 154 using non-access stratum (NAS) control plane signaling to indicate that the periodic or triggered location is canceled. The target UE 105 includes the HGMLC 155H contact address and the LDR reference number.

[0110] At stages 29 to 31 , the AMF 154 forwards the cancel request to the VGMLC 155V, the HGMLC 155H and the external LCS client 130 .

[0111] At stage 32, if the external LCS client 130 wishes to cancel a periodic or triggered location, the external LCS client 130 transmits a request to the HGMLC 155H.

[0112] At stages 33 to 34, the HGMLC 155H determines the serving AMF 154 address as in stage 3 and forwards the cancel request to the AMF 154 directly or via the VGMLC 155V. The HGMLC 155H includes the HGMLC 155H contact address and the LDR reference number.

[0113] At stage 35, once the target UE 105 becomes reachable, the AMF 154 transmits a cancel request to the target UE 105 and includes the HGMLC 155H contact address and the LDR reference number. The target UE 105 then releases all resources used for the location request.

[0114] It is noted that the cancellation request transmitted to the target UE 105 at stage 35 may be a message for a supplementary service or a NAS message.

[0115] In another variation of the techniques described herein, a periodic or triggered location of the target UE 105 may be requested by the external LCS client 130 and activated in the target UE 105 using control plane signaling (e.g., based on a request with Figure 4A1 to 20 in ). In this variant, the LMF 152 in the 5GCN 150 of the serving PLMN for the target UE 105 may be used to support periodic or triggered location of the target UE 105. Whenever the UE 105 detects a periodic or triggered event, the LMF 152 may receive a location event report from the UE 105. The LMF 152 may then optionally use control plane signaling to determine the location of the UE 105, and (when the location is obtained) may transmit a location event report containing the location to the external client 130 via the user plane (e.g., using a TCP connection and an optional TLS session between the LMF 152 and the external client 130) and possibly using HTTP or ULP. With this variant, the latency of transmitting the location event report from the LMF 152 to the external client 130 may be reduced compared to using control plane signaling to transmit the location event report from the LMF 152 to the external client 130.

[0116] Figure 4B An example process of the target UE 105 performing location reporting using the user plane is shown. Figure 4B Applied to Figure 1A The non-roaming target UE 105 in the communication system 100 in FIG. Figure 2 The process of roaming target UE 105 in the communication system 200 may be based on Figure 4B The process shown in Figure 4B In the example, position reporting is performed using event reporting that includes a position estimate. Figure 4B The process in shows event reporting from UE 105 directly to LCS client 130 or AF 132 when a user plane connection is established directly from UE 105 to LCS client 130 or AF 132 without an intermediate LMF 152 or H-GMLC 155H.

[0117] At stage 1, you can execute Figure 4A or perform steps 1 to 21 of the deferred 5GC-MT-LR procedure for periodic or triggered location events in clause 6.3.1 of 3GPP TS 23.273, but with the following differences.

[0118] In step 1 of 3GPP TS 23.273 clause 6.3.1, the LCS client or AF includes a request for a user plane report in a location request and includes an IP address or FQDN for a user plane connection and security information for enabling a secure connection.

[0119] In steps 4, 5, 14 and 16 of clause 6.3.1 of 3GPP TS 23.273, the request for user plane reporting and the IP address or FQDN and security information are forwarded to the V-GMLC (if used), AMF, LMF and target UE in that order. The type of user plane connection (directly to LCS client or AF) and the type of user plane connection used in Figure 4B The criteria for transmitting the cumulative event report at stage 9 of the process shown in FIG. 1 is also conveyed from the H-GMLC to the target UE. The criteria may include periodic time intervals or at Figure 4B A certain number of event reports are transmitted via the user plane at stage 6 of the process shown in FIG.

[0120] In steps 17 to 21 of clause 6.3.1 of 3GPP TS23.273, the target UE indicates to the LMF, H-GMLC and LCS client or AF whether the target UE can support event reporting via the user plane. If event reporting via the user plane cannot be supported, the target UE transmits event reports via the control plane using the procedure in clause 6.3.1 of 3GPP TS23.273.

[0121] At stage 2, the UE 105 establishes a secure TCP / IP connection to the LCS client 130 or AF 132 using the IP address or FQDN and security information received at stage 1.

[0122] At stage 3, if the UE 105 requires assistance data to help determine the location later at stage 5, the UE 105 may transmit a positioning LPP request to the LMF 152 via the control plane using the deferred routing ID received in step 16 of the process in clause 6.3.1 in 3GPP TS 23.273 to identify the request and route the request to the correct LMF 152. The LMF 152 then provides the requested assistance data to the UE 105 by returning an LPP positioning message via the control plane. Preferably, the UE 105 requests the assistance data some time before a location determination is required to avoid increasing latency. If the current LMF cannot provide assistance data for the current UE location (e.g., the current UE Tracking Area Identity (TAI) or Cell Global Identity (CGI)), the LMF 152 may use the LMF change procedure to forward the request for assistance data to a more appropriate LMF. In this case, the new LMF may return assistance data to the UE 105 via the original LMF 152 to avoid changing the LMF association in the UE 105 and the H-GMLC 155H or V-GMLC.

[0123] At stage 4, UE 105 monitors and detects the occurrence of triggering or periodic events, such as Figure 4AStage 21 or step 22 of the procedure in clause 6.3.1 of 3GPP TS 23.273.

[0124] At stage 5, the UE 105 obtains a position measurement and may use the assistance data obtained at stage 3 to determine the current position. Obtaining position at stage 5 limits the UE 105 to using either UE-based or independent positioning methods. If a UE-assisted positioning method is required, the LMF 152 may use Figure 4D Instead of the process described in Figure 4B process.

[0125] At stage 6, UE 105 transmits a supplementary service event report to LCS client 130 or AF 132 over the secure TCP / IP connection established at stage 2. The event report indicates the type of event reported and includes the location determined at stage 5.

[0126] At stage 7 , the LCS client 130 or AF 132 returns a supplementary service event report acknowledgement to the UE 105 over the secure TCP / IP connection established at stage 2 .

[0127] At stage 8, the UE 105 continues to monitor and detect further triggers or periodic events as in stage 4, and repeats stages 5 to 7 for each detected trigger or periodic event.

[0128] At stage 9, based on the criteria received by UE 105 for transmitting cumulative event reports (e.g., expiration of a periodic timer or Figure 4B 6 of the procedure shown in 3GPP TS 23.273), the UE 105 transmits a cumulative event report to the LMF 152, the H-GMLC 155H and the LCS client 130 or AF 132 by periodically or triggeredly deferring the control plane part of the 5GC-MT-LR. The cumulative event report indicates to the LMF 152, the H-GMLC 155H and the external LCS client 130 or AF 132 that the control plane part of the periodic or triggered deferral 5GC-MT-LR is still operational, the UE 105 is still reporting events (e.g., still powered on and within network coverage), and may include statistical information about the events reported since the last cumulative event report was transmitted (e.g., the number of event reports).

[0129] Figure 4C An example process of the target UE 105 performing location reporting using the user plane is shown. Figure 4C Applied to Figure 1AThe non-roaming target UE 105 in the communication system 100 in FIG. Figure 2 The process of roaming target UE 105 in the communication system 200 may be based on Figure 4C The process shown in Figure 4C In the example, position reporting is performed using event reporting that includes a position estimate. Figure 4C The process in shows event reporting from the UE 105 to the LCS client 130 or AF 132 when a user plane connection to the LCS client 130 or AF 132 is established via the H-GMLC 155H.

[0130] At stage 1, you can execute Figure 4A or perform steps 1 to 21 of the deferred 5GC-MT-LR procedure for periodic or triggered location events in clause 6.3.1 of 3GPP TS 23.273, but with the following differences.

[0131] In step 1 of 3GPP TS 23.273 clause 6.3.1, the LCS client or AF includes a request for a user plane report in a location request and includes an IP address or FQDN for a user plane connection and security information for enabling a secure connection.

[0132] In steps 4, 5, 14 and 16 of clause 6.3.1 of 3GPP TS23.273, the request for user plane reporting and the IP address or FQDN and security information of the H-GMLC are forwarded to the VGMLC (if used), AMF, LMF and target UE in sequence. The H-GMLC also retains the IP address or FQDN and security information of the LCS client or AF received at step 1. The type of user plane connection (via the H-GMLC) is also conveyed from the H-GMLC to the target UE.

[0133] In steps 17 to 21 of clause 6.3.1 of 3GPP TS23.273, the target UE indicates to the LMF, H-GMLC and LCS client or AF whether the target UE can support event reporting via the user plane. If event reporting via the user plane cannot be supported, the target UE transmits event reports via the control plane using the procedure in clause 6.3.1 of 3GPP TS23.273.

[0134] exist Figure 4C At stage 2, the UE 105 establishes a secure TCP / IP connection to the H-GMLC 155H using the IP address or FQDN and security information received by the UE 105 at stage 1.

[0135] At Stage 3, the H-GMLC 155H establishes a secure TCP / IP connection to the LCS Client 130 or AF 132 using the IP address or FQDN and security information received by the H-GMLC 155H at Stage 1.

[0136] At stage 4, if the UE 105 requires assistance data to help determine the position later at stage 6, the UE 105 performs Figure 4B Stage 3 in the protocol may be used to obtain assistance data from the LMF 152 using the control plane.

[0137] At stage 5, UE 105 monitors and detects the occurrence of triggering or periodic events, such as Figure 4A Stage 21 or step 22 of the procedure in clause 6.3.1 of 3GPP TS 23.273.

[0138] At stage 6, the UE 105 obtains a position measurement and may use the assistance data obtained at stage 3 to determine the current position. Obtaining the position at stage 6 limits the UE 105 to using either UE-based or independent positioning methods. If a UE-assisted positioning method is required, the LMF 152 may use Figure 4C The process Figure 4D The process described in .

[0139] At stage 7, the UE 105 transmits a supplementary service, HTTP or SUPL ULP event report to the H-GMLC 155H over the secure TCP / IP connection established at stage 2. The event report indicates the type of event reported and includes the location determined at stage 6.

[0140] At stage 8 , the H-GMLC 155H forwards the supplementary service, HTTP or SUPL ULP event report to the LCS client 130 or AF 132 over the secure TCP / IP connection established at stage 3 .

[0141] At stage 9 , the LCS client 130 or AF 132 returns a supplementary service, HTTP or SUPL ULP event report acknowledgement to the H-GMLC 155H over the secure TCP / IP connection established at stage 3 .

[0142] At stage 10 , the H-GMLC 155H returns a supplementary service, HTTP or SUPL ULP event report acknowledgement to the UE 105 over the secure TCP / IP connection established at stage 2 .

[0143] At stage 11, the UE 105 continues to monitor and detect further triggers or periodic events as in stage 5, and repeats stages 6 to 10 for each detected trigger or periodic event.

[0144] As in Figure 4B At stage 9 in the process shown in , no cumulative event reports from the UE 105 may be needed when transmitting event reports via the H-GMLC 155H, because the H-GMLC 155H already knows the status of the event reports and will know if the UE 105 has stopped reporting events.

[0145] Figure 4D An example process of the target UE 105 performing location reporting using the user plane is shown. Figure 4D Applied to Figure 1A The non-roaming target UE 105 in the communication system 100 in FIG. Figure 2 The process of roaming target UE 105 in the communication system 200 may be based on Figure 4D The process shown in Figure 4D In the example, position reporting is performed using event reporting that includes a position estimate. Figure 4D The process in FIG. 1 shows event reporting from a UE 105 to an LCS Client 130 or AF 132 when a user plane connection to the LCS Client 130 or AF 132 is established via an LMF 152. The process does not support the delivery of event reports to a new LMF. Although such support could be added, this could significantly increase latency and add more impact to the target UE 105, LMF 152, and LCS Client 130 or AF 132. Environments that require very low latency may include factories, warehouses, and industrial plants, where a single LMF may support the entire UE coverage area, so there is no need to change the LMF 152. In other environments where a change in LMF may be required, a new LMF may be used instead. Figure 4B and Figure 4C process.

[0146] At stage 1, you can execute Figure 4A or perform steps 1 to 21 of the deferred 5GC-MT-LR procedure for periodic or triggered location events in clause 6.3.1 of 3GPP TS 23.273, but with the following differences.

[0147] In step 1 of 3GPP TS 23.273 clause 6.3.1, the LCS client or AF includes a request for a user plane report in a location request and includes an IP address or FQDN for a user plane connection and security information for enabling a secure connection.

[0148] In steps 4, 5 and 14 of clause 6.3.1 of 3GPP TS23.273, the request for user plane reporting and the IP address or FQDN and security information are forwarded to V-GMLC (if used), AMF and LMF in sequence. The criteria for transmitting cumulative event reports at step 14 are also conveyed to LMF. The criteria may include periodic time intervals or a specific number of event reports transmitted via the user plane at steps 7 and 11.

[0149] In step 16 of 3GPP TS 23.273 clause 6.3.1, the request for user plane reporting and the IP address or FQDN and security information of the LMF are transmitted to the target UE. The LMF also retains the IP address or FQDN and security information of the LCS client or AF received at step 14. At step 16, the type of user plane connection (via the LMF) is also conveyed to the target UE.

[0150] In steps 17 to 21 of clause 6.3.1 of 3GPP TS23.273, the target UE indicates to the LMF, H-GMLC and LCS client or AF whether the target UE can support event reporting via the user plane. If event reporting via the user plane cannot be supported, the target UE transmits event reports via the control plane using the procedure in clause 6.3.1 of 3GPP TS23.273.

[0151] exist Figure 4D At stage 2, UE 105 establishes a secure TCP / IP connection to LMF 152 using the IP address or FQDN and security information received by UE 105 at stage 1.

[0152] At stage 3, the LMF 152 establishes a secure TCP / IP connection to the LCS client 130 or AF 132 using the IP address or FQDN and security information received by the LMF 152 at stage 1.

[0153] At stage 4, if the UE 105 requires assistance data to help obtain a position measurement later at stage 6, the UE 105 performs Figure 4B Stage 3 in the protocol may be used to obtain assistance data from the LMF 152 using the control plane.

[0154] At stage 5, UE 105 monitors and detects the occurrence of triggering or periodic events, such as Figure 4A Stage 21 or step 22 of the procedure in clause 6.3.1 of 3GPP TS 23.273.

[0155] At stage 6 , the UE 105 obtains location measurements and possibly determines the location, possibly using the assistance data obtained at stage 4 .

[0156] At stage 7, UE 105 transmits a supplementary service event report to LMF 152 over the secure TCP / IP connection established at stage 2. The event report indicates the type of event reported and includes an embedded LPP message with the location measurement or location estimate obtained at stage 6.

[0157] At stage 8 , LMF 152 returns a supplementary service event report acknowledgement to UE 105 over the secure TCP / IP connection established at stage 2 .

[0158] At stage 9, if LMF 152 requires additional location measurements or location estimates from UE 105, LMF 152 exchanges LPP messages with UE 105 over the secure TCP / IP connection established at stage 2 to request and receive additional location measurements or location estimates from UE 105.

[0159] At stage 10 , LMF 152 determines or verifies a position estimate for UE 105 based on the position measurements or position estimates received from UE 105 at stage 7 and / or stage 9 .

[0160] At stage 11 , LMF 152 transmits a supplementary service, HTTP or SUPL ULP event report to LCS client 130 or AF 132 over the secure TCP / IP connection established at stage 3 , and includes the type of event report and the location estimate determined or verified at stage 10 .

[0161] At stage 12 , the LCS client 130 or AF 132 returns a supplementary service, HTTP or SUPL ULP event report acknowledgement to the LMF 152 over the secure TCP / IP connection established at stage 3 .

[0162] At stage 13, the UE 105 continues to monitor and detect further triggers or periodic events as in stage 5, and repeats stages 6 to 12 for each detected trigger or periodic event.

[0163] At stage 14, based on the criteria for transmitting the cumulative event report received by the LMF 152 (e.g., expiration of a periodic timer or transmission of a specific number of event reports), the LMF 152 transmits the cumulative event report to the H-GMLC 155H and the LCS client 130 or AF 132 by periodically or triggeredly deferring the control plane part of the 5GC-MT-LR using steps 28 to 30 of the procedure in clause 6.3.1 of 3GPP TS 23.273. The cumulative event report indicates to the H-GMLC 155H and the external LCS client 130 or AF 132 that the control plane part of the periodically or triggeredly deferring 5GC-MT-LR is still operational, that the UE 105 is still reporting events (e.g., still powered on and within network coverage), and may include statistical information about the events reported since the last cumulative event report was transmitted (e.g., the number of event reports).

[0164] The cancellation of event reporting may be initiated by the UE 105, H-GMLC 155H or LCS client 130 or AF 132 using the control plane procedures defined in clauses 6.3.2 and 6.3.3 of 3GPP TS 23.273. Changes to these procedures may be Figure 4B , Figure 4C and Figure 4D The user plane connection established by the process in is also released. Once the control plane level cancellation occurs, the user plane connection can be released by either end.

[0165] Figure 4E The process of event reporting from the UE 105 to the LCS client 130 or AF 132 is shown when a user plane connection is established directly from the UE 105 to the LCS client 130 or AF 132. This process is applicable when the target UE 105 is able to determine its location.

[0166] In phase 1, execute Figure 4A or steps 1 to 21 of clause 6.3.1 of 3GPP TS 23.273 for the deferred 5GC-MT-LR procedure for periodic or triggered location, where Figure 4A The following actions occur at those stages of, or the following additional actions occur at those steps of clause 6.3.1 of 3GPP TS 23.273.

[0167] At stage 1 or step 1, the LCS client 130 or AF 132 can include a request for a user plane report in an LCS service request and can include a user plane address of the LCS client 130 or AF 132 (e.g., which can be an IP address, a universal resource locator (URL), a uniform resource identifier (URI), or a fully qualified domain name (FQDN))

[0168] and security information for enabling a secure connection (e.g., a public security key and / or a private security key of a private key-public key pair). The H-GMLC 155H may verify whether both the target UE 105 and the LCS client 130 or AF 132 have subscribed to user plane reporting. If the LCS client 130 or AF 132 does not include a user plane address or security information, the H-GMLC

[0169] 155H may obtain a default user plane address and / or default security information from subscription data of the LCS client 130 or the AF 132. The H-GMLC 155H may determine a criterion for transmitting cumulative event reports via the control plane. The criterion may include a maximum number of cumulative event report timers and / or user plane event report counters.

[0170] ·exist Figure 4A At stages 4, 5 and 13 of 3GPP TS 23.273 or steps 4, 5 and 14 of clause 6.3.1 of 3GPP TS 23.273, the request for user plane reporting, the user plane address, security information and the criteria for transmitting the cumulative event report via the control plane may be forwarded to V-

[0171] GMLC 155V (if used), service AMF 154 and LMF 152.

[0172] ·exist Figure 4A At stage 14 in or step 15 in clause 6.3.1 of 3GPP TS 23.273, LMF 152 may verify whether UE 105 is capable of supporting a positioning method (eg, a UE-based positioning method) that allows UE 105 to determine its own position.

[0173] ·exist Figure 4A At stage 15 in or step 16 in clause 6.3.1 of 3GPP TS23.273, LMF 152 may include a request for user plane reporting, a user plane address, security information and criteria for transmitting cumulative event reports in a supplementary service LCS periodic triggered invocation request transmitted to the target UE 105.

[0174] ·exist Figure 4A At stage 16 of 3GPP TS 23.273 or step 17 of clause 6.3.1 of 3GPP TS 23.273, the target UE 105 may indicate to the LMF 152 whether the target UE 105 is capable of supporting event reporting via the user plane. If the target UE 105 is not capable of supporting event reporting via the user plane, then Figure 4AAt stages 17 to 20 in 3GPP TS 23.273 or steps 18 to 21 in clause 6.3.1 of 3GPP TS 23.273, a failure response may be returned to the LCS client 130 or the AF 132.

[0175] Back to Figure 4E In the process of FIG. 1 , at stage 2, UE 105 may use the user plane address and security information received at stage 1 to establish a secure user plane connection to LCS client 130 or AF 132. The secure user plane connection and its protocol may be as described for Figure 3A or Figure 3B Described and may not pass through LMF 152 or HGMLC 155H.

[0176] At stage 3, UE 105 may monitor and detect the occurrence of triggering or periodic events, such as for Figure 4A The process is described in stage 21 or step 22 of clause 6.3.1 of 3GPP TS 23.273.

[0177] At stage 4a, UE 105 may obtain location measurements and determine the current location of UE 105.

[0178] At stage 4b, if UE 105 is unable to determine its own location at stage 4a, UE 105 may transmit an event report that does not include a location estimate to LCS client 130 or AF 132 via the secure user plane connection established at stage 2 or via the control plane, as described for steps 24 to 30 in clause 6.3.1 of 3GPP TS 23.273.

[0179] At stage 5, if the UE 105 is able to determine its position at stage 4a, the UE 105 may transmit an event report to the LCS client 130 or AF 132 via the secure user plane connection established at stage 2. The event report may indicate the type of event reported (e.g., a periodic event, an area-related event, or a motion-related event) and may include the location determined at stage 4a and (possibly) the time or timestamp of the event detection performed at step 3 or the location determination performed at step 4a.

[0180] At stage 6 , the LCS client 130 or the AF 132 may return an event report acknowledgment to the UE 105 over the secure user plane connection established at stage 2 .

[0181] It may be noted that event reporting and event reporting confirmation may reuse existing supplementary service messages as defined in 3GPP TS 24.080, or may use messages as defined for Figure 3A and Figure 3B Messages described for HTTP or SUPL ULP.

[0182] At stage 7, the UE 105 may continue to monitor and detect further triggers or periodic events as in stage 3, and may repeat stages 4 to 6 for each detected trigger or periodic event.

[0183] At stage 8, UE 105 may monitor the criteria for transmitting cumulative event reports received at stage 1. If a cumulative event report timer is received at stage 1, UE 105 may start the timer after stage 1 and after each cumulative event report is transmitted. If a maximum number of user plane event report counters are received at stage 1, UE 105 may maintain a count of the number of user plane event reports transmitted at stage 5. When the cumulative event report timer expires or when the count of user plane event reports transmitted at stage 5 reaches the maximum number of user plane event report counters, UE 105 may transmit the cumulative event report and restart the timer and the count of user plane event reports. UE 105 transmits the cumulative event report to LMF 152, H-GMLC 155H and LCS client 130 or AF 132 by periodically or triggeringly deferring the control plane portion of 5GC-MT-LR, for example using steps 24 to 30 in clause 6.3.1 of 3GPP TS 23.273. The cumulative event report may indicate to the LMF 152, H-GMLC 155H and external LCS client 130 or AF 132 that the control plane portion of the periodic or triggered deferral 5GC-MT-LR is still active, that the UE 105 is reporting events via the user plane, and may include statistical information about the events reported since the last cumulative event report was transmitted (e.g., the number of event reports transmitted). The cumulative event report may be an event report message as defined in 3GPP TS 24.080, which also indicates the event type as a "cumulative event report" type event.

[0184] The target UE 105 may also transmit a cumulative event report at stage 8 to obtain assistance data from the LMF 152 for assisting positioning at stage 4a. In this case, the target UE 105 may include a positioning LPP request for assistance data (e.g., as defined in 3GPP TS 37.355) in the cumulative event report transmitted to the LMF 152 at step 25 of 3GPP TS 23.273, and the LMF 152 may return the requested assistance data to the target UE 105 using step 27 of clause 6.3.1 of 3GPP TS 23.273. In this case, the cumulative event report timer and the count of user plane event reports may be restarted, and the cumulative event report (but not including an embedded positioning LPP request for assistance data) may be transmitted by the LMF 152 to the H-GMLC 155H and the LCS client 130 or AF 132.

[0185] exist Figure 4E During the event reporting shown, for example, if the location (e.g., tracking area) of the UE 105 changes and is no longer in the service area of ​​the current LMF 152 but in the service area of ​​another new LMF 152, the current LMF 152 used for event reporting via the control plane of the UE 105 may need to be replaced with another new LMF 152. In this case, when the UE 105 transmits the cumulative event report at stage 8, the serving AMF 154 or the current LMF 152 may detect that the UE 105 is no longer in the service area of ​​the current LMF 152 (e.g., not in the tracking area supported by the current LMF 152), and then the LMF change procedure in clause 6.4 of 3GPP TS 23.273 may be invoked to forward the cumulative event report (and any request for assistance data) to another new LMF 152. In this case, the new LMF 152 may return any assistance data to the UE 105 (if requested) and may forward the cumulative event report to the H-GMLC 155H and the LCS Client 130 or AF 132.

[0186] It may be noted that when stage 8 is used to request assistance data, the UE 105 may perform stage 8 before performing stage 4a for user plane event reports in order to avoid additional delays in transmitting user plane event reports.

[0187] Figure 5 5 is an illustration of a process flow 500 illustrating a method for performing by a user equipment (UE) (such as target UE 105) to locate the UE in a wireless network according to some embodiments. For example, the UE may be UE 105 or Figure 8 UE 800 shown in .

[0188] At block 512, functionality includes: receiving a request for locating the UE, wherein the request for locating the UE: includes a periodic or triggered location request based on a location request initiated by an external client or an application function (AF); includes one or more criteria for providing cumulative event reports; and is received by the UE using control plane signaling, such as Figure 4E Phase 1 and Figure 4A The request may come from or be via an LMF (e.g., LMF 152). The components and / or structures for performing this functionality may include, for example, a wireless transceiver 802 and one or more processors 804 having dedicated hardware or implementing executable code or software instructions in a memory 820, such as Figure 8 The location request receiving unit 822 in the UE 800 illustrated in FIG.

[0189] At block 514, functionality includes: responding to detecting a periodic or triggered event (e.g., Figure 4E At stage 3), the following operations are performed, where the periodic or triggered event occurs at multiple different times: obtaining the first location information of the UE (for example, as in Figure 4E ), and using user plane signaling to report the first location information of the UE to the external client or AF (for example, as in Figure 4E 5). The components and / or structures for performing this functionality may include, for example, a wireless transceiver 802 and one or more processors 804 having dedicated hardware or implementing executable code or software instructions in a memory 820, such as Figure 8 The location information obtaining unit 828 in the UE 800 illustrated in FIG.

[0190] At block 516, functionality includes: in response to determining that at least one of the one or more criteria for providing the cumulative event report has been met (e.g., as in Figure 4E 8), transmit the accumulated event report to the external client or AF using control plane signaling (e.g., as in Figure 4E 8). The components and / or structures for performing this functionality may include, for example, a wireless transceiver 802 and one or more processors 804 having dedicated hardware or implementing executable code or software instructions in a memory 820, such as Figure 8 The location information obtaining unit 828 in the UE 800 illustrated in FIG.

[0191] In a specific implementation, reporting the first location information of the UE to the external client or AF using user plane signaling includes: (1) reporting the first location information of the UE directly to the external client or AF, or (2) reporting the first location information of the UE via a location management function (LMF) or a home gateway mobile location center (H-GMLC) or both, for example, as in Figure 4C Stage 7 and 8 of Figure 4D As discussed herein, according to some embodiments, directly reporting the first location information of the UE to the external client or AF may include: transmitting an event report message to the external client or AF using user plane signaling, wherein the first location information is included in the event report message, for example, as for Figure 4E In such embodiments, the event report message may include an HTTP message or a SUPL ULP message.

[0192] In a specific implementation, reporting the first location information of the UE to the external client or AF via the LMF includes: transmitting a first event report message to the LMF using user plane signaling, wherein the first location information is included in the first event report message, for example, as in Figure 4D . In some embodiments, the first event report message may include a supplementary service message. According to some embodiments, reporting the first location information of the UE to the external client or AF via the LMF may also include: after or when reporting the first location information, exchanging Long Term Evolution (LTE) Positioning Protocol (LPP) messages with the LMF using user plane signaling to provide positioning measurements to the LMF, thereby enabling the UE or the LMF to determine a position estimate of the UE (e.g., using a UE-based or UE-assisted positioning method), for example, as in Figure 4D The LMF may then transmit a second event report message including the position estimate to the external client or AF using user plane signaling, for example, Figure 4D as described at stage 11.

[0193] In a specific implementation, reporting the first location information of the UE to the external client or AF via the H-GMLC may include: using user plane signaling to transmit a first event report message having the first location information to the H-GMLC, for example, Figure 4C The H-GMLC may then transmit a second event report message including the position estimate to the external client or AF using user plane signaling, for example, Figure 4CIn some embodiments, the first event report message may include a supplementary service message, an HTTP message, or a SUPL ULP message.

[0194] In one specific implementation, the request for locating the UE includes at least one of: an indication to use user plane signaling to report the first location information, a type of user plane connection, and an address to which the first location information is to be reported, for example, as described herein with respect to Figure 4E Phase 1 and Figure 4A In such a specific implementation, the UE may establish a first user plane connection to at least one of the external client or the AF or to another entity based on the address, wherein the other entity establishes a second user plane connection towards the external client or the AF, and wherein the first user plane connection or the first user plane connection and the second user plane connection are used to report the first location information. The first user plane connection and the second user plane connection may each be based on at least one of the following: Internet Protocol (IP) or Transmission Control Protocol (TCP) or both, for example, as for Figure 3A and Figure 3B The first user plane connection, the second user plane connection, or both may be secure and established based on the received security information. Some embodiments may also include transmitting or receiving a cancellation of locating the UE using control plane signaling, wherein the first user plane connection is released after the control plane connection is canceled.

[0195] In a specific implementation, obtaining the first location information of the UE includes: transmitting a request for assistance data to a location server using control plane signaling; and receiving assistance data from the location server using control plane signaling, for example, as described herein with respect to Figure 4D Additionally or alternatively, transmitting the cumulative event report (e.g., as in Figure 4E Stage 8) may include: transmitting the accumulated event report to the external client or AF, location server, home gateway mobile location center (H-GMLC) or some combination thereof, for example, as for Figure 4E as described in Stage 8.

[0196] Figure 6 is an example network entity 600 (such as Figure 1A , Figure 1B and Figure 2150, VGMLC 155V, HGMLC 155H or NEF 159) shown in . The network entity 600 can be, for example, part of a wireless network such as a 5G core network (5GCN) 150, 150V or 150H. The network entity 600 includes, for example, hardware components such as an external interface 602, which can be a wired interface or a wireless interface capable of connecting to an external client 130, NEF 159 (if the network entity 600 is GMLC155), GMLC 155 (if the network entity 600 is NEF 159 or another GMLC 155), UDM 156, AMF 154. The network entity 600 includes one or more processors 604 and a memory 610, which can be coupled together using a bus 606. Memory 610 may contain executable code or software instructions that, when executed by the processor(s) 604, cause the processor(s) to operate as a special-purpose computer programmed to perform the processes and techniques disclosed herein.

[0197] like Figure 6As illustrated, the memory 610 includes one or more components or modules that, when implemented by one or more processors 604, implement the methodologies as described herein. Although the components or modules are illustrated as software in the memory 610 that can be executed by the one or more processors 604, it should be understood that the components or modules can be dedicated hardware in or outside the processor 604. As illustrated, the memory 610 may include a location request receiving unit 612 that enables the one or more processors 604 to receive and process a request for locating a UE from an external client via the external interface 602. The memory 610 may include a location request transmitting unit 616 that enables the one or more processors 604 to communicate a request for locating a UE to another entity (such as the AMF 154) in the wireless network via the external interface 602 using control plane signaling, wherein the request for locating the UE includes a request to report location information using user plane signaling (or control plane signaling) and an address to which the location information is to be reported. The memory 610 may include an acknowledgement receiving unit 616 that enables the one or more processors 604 to receive and process a response from another entity via the external interface 602 using control plane signaling, wherein the response indicates acceptance of the request for locating the UE. An acknowledgement transmitting unit 618 enables the one or more processors 604 to transmit the response to the external client via the external interface 602. The memory 610 may also include a querying unit 620 that enables the one or more processors 604 to query another entity in the wireless network (e.g., UDM 156) for an address of the other entity via the external interface 602. The memory 610 may also include a querying response unit 622 that enables the one or more processors 604 to receive a response to the query with the address of the other entity from another entity in the wireless network (e.g., UDM 156) via the external interface 602. The memory 610 may also include an activation response unit 624 that enables the one or more processors 604 to receive a second response from a second entity via the external interface 602 using control plane signaling, wherein the second response indicates activation of a request for locating the UE in a radio access network (RAN), wherein the RAN provides wireless access to the UE. The memory 610 may also include an activation transmission unit 626 that enables the one or more processors 604 to forward the second response to an external client via the external interface 602.

[0198] The one or more processors 604 may be configured by the reporting unit 628 to receive a report with location information, such as an event report, from the UE or LMF via the external interface 602 using user plane signaling. The one or more processors 604 may also be configured by the reporting unit 628 to transmit a report with location information, such as an event report, to an external client or AF via the external interface 602 using user plane signaling. The one or more processors 604 may also be configured by the reporting unit 628 to receive a periodic or triggered cumulative event report to an external client, AF or GMLC via the external interface 602 using control plane signaling, the periodic or triggered cumulative event report indicating that the periodic or triggered location request remains operational, that the UE is still reporting events (e.g., still powered on and within network coverage) and may include statistical information about events reported since the last cumulative event report was transmitted (e.g., the number of event reports).

[0199] The one or more processors 604 may be configured by the control plane / user plane unit 630 to establish and cancel user plane connections and control plane connections. The one or more processors 604 may be configured by the control plane / user plane unit 630 to, for example, establish a user plane connection using IP, TCP, or both, and to establish a secure user plane connection based on security information such as a private authentication key or token.

[0200] The methodologies described herein may be implemented by various means depending on the application. For example, these methodologies may be implemented in hardware, firmware, software, or any combination thereof. For hardware implementation, the one or more processors may be implemented in 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.

[0201] For specific implementations involving firmware and / or software, these methodologies can be implemented with modules (e.g., procedures, functions, etc.) that perform the individual functions described herein. Any machine-readable medium that tangibly embodies instructions can be used to implement the methodologies described herein. For example, software codes can be stored in a memory and executed by one or more processor units so that these processor units operate as special-purpose computers programmed to perform the algorithms disclosed herein. The memory can be implemented within a processor unit or outside a processor unit. As used herein, the term "memory" refers to any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type of memory or any particular amount of memory, or the type of medium on which the memory is stored.

[0202] If implemented in firmware and / or software, each function may be stored as one or more instructions or codes on a non-transitory computer-readable storage medium. Examples include computer-readable media encoded with data structures and computer-readable media encoded with computer programs. Computer-readable media include physical computer storage media. The storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices, semiconductor storage devices or other storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer; as used herein, disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, where disks typically reproduce data magnetically, while optical disks reproduce data optically using lasers. The above combinations should also be included within the scope of computer-readable media.

[0203] In addition to being stored on a computer-readable storage medium, instructions and / or data may also be provided as a signal on a transmission medium included in a communication device. For example, a communication device may include a transceiver having a signal indicating instructions and data. These instructions and data are stored on a non-transitory computer-readable medium (e.g., memory 610) and are configured to cause one or more processors 604 to operate as a special-purpose computer programmed to perform the processes and techniques disclosed herein. That is, the communication device includes a transmission medium having a signal indicating information for performing the disclosed functions. At a first time, the transmission medium included in the communication device may include a first portion of information for performing the disclosed functions, and at a second time, the transmission medium included in the communication device may include a second portion of information for performing the disclosed functions.

[0204] A first entity in a wireless network configured to support location determination of a user equipment (UE), such as a network entity 600, may include means for receiving a request for locating a UE from an external client, which means may be, for example, an external interface 602 and one or more processors 604 having dedicated hardware or implementing executable code or software instructions in a memory 610, such as a location request receiving unit 612. Means for transmitting a request for locating the UE to a second entity in the wireless network using control plane signaling, wherein the request for locating the UE includes a request to report location information using user plane signaling and an address to which the location information is to be reported, may be, for example, the external interface 602 and one or more processors 604 having dedicated hardware or implementing executable code or software instructions in a memory 610, such as a location request transmitting unit 614. Means for receiving a first response from the second entity using control plane signaling, wherein the first response indicates acceptance of the request for locating the UE, may be, for example, the external interface 602 and one or more processors 604 having dedicated hardware or implementing executable code or software instructions in a memory 610, such as an acknowledgement receiving unit 616. The means for forwarding the first response to the external client may be, for example, the external interface 602 and one or more processors 604 having dedicated hardware or implementing executable code or software instructions in the memory 610 , such as the confirmation transmission unit 618 .

[0205] In one specific implementation, the first entity may include means for transmitting a query for the address of the second entity to the third entity before passing the request for locating the UE to the second entity, which means may be, for example, the external interface 602 and one or more processors 604 having dedicated hardware or implementing executable code or software instructions in the memory 610, such as the query unit 620. The means for receiving the address of the second entity from the third entity may be, for example, the external interface 602 and one or more processors 604 having dedicated hardware or implementing executable code or software instructions in the memory 610, such as the query response unit 622.

[0206] In one specific implementation, the first entity may include means for receiving a second response from the second entity using control plane signaling, wherein the second response indicates activation of a request for locating the UE in a radio access network (RAN), wherein the RAN provides wireless access to the UE, the means may be, for example, the external interface 602 and one or more processors 604 having dedicated hardware or implementing executable code or software instructions in the memory 610, such as the activation response unit 624. The means for forwarding the second response to the external client may be, for example, the external interface 602 and one or more processors 604 having dedicated hardware or implementing executable code or software instructions in the memory 610, such as the activation transmission unit 626.

[0207] Figure 7 is an example network entity 700 (such as Figure 1A , Figure 1B and Figure 2 154 or LMF 152) shown in . The network entity 700 can be, for example, part of a wireless network such as a 5G core network (5GCN) 150, 150V, or 150H. The network entity 700 includes, for example, hardware components such as an external interface 702, which can be a wired interface or a wireless interface capable of connecting to the GMLC 155, NEF 159, LMF 152 (if the network entity 700 is AMF 154), AMF 154 (if the network entity is LMF 152), UDM 156, and a serving base station 110-1. The network entity 700 includes one or more processors 704 and a memory 710, which can be coupled together using a bus 706. The memory 710 can contain executable code or software instructions that, when executed by one or more processors 704, cause the one or more processors to operate as a special-purpose computer programmed to perform the processes and techniques disclosed herein.

[0208] like Figure 7As illustrated, the memory 710 includes one or more components or modules that, when implemented by the one or more processors 704, implement the methodologies as described herein. Although the components or modules are illustrated as software in the memory 710 that can be executed by the one or more processors 704, it should be understood that the components or modules can be dedicated hardware in or outside the processor 704. As illustrated, the memory 710 may include a location request receiving unit 712 that enables the one or more processors 704 to receive and process a request for locating a UE from a second entity (such as the GMLC 155 or the NEF 159) in the wireless network via the external interface 702, wherein the request for locating the UE is based on a location request initiated by an external client and is received using control plane signaling. The memory 710 may include a location request transmitting unit 716 that enables the one or more processors 704 to transmit information of a request for locating the UE to a third entity in the wireless network via the external interface 702 using control plane signaling, wherein the third entity may be a serving base station, such as gNB 110-1 or UE 105, wherein the request for locating the UE and the information of the request for locating the UE each include a request to report location information using user plane signaling and an address to which the location information is to be reported, wherein the information of the request for locating the UE enables the third entity to obtain the location information of the UE using control plane signaling and report the location information of the UE to an external client using user plane signaling. The memory 710 may include a confirmation receiving unit 716 that enables the one or more processors 704 to receive and process a response from the third entity via the external interface 702 using control plane signaling, wherein the response indicates activation or confirmation of the request for locating the UE in the third entity. The confirmation transmitting unit 718 enables the one or more processors 704 to transmit the response to the second entity via the external interface 702.

[0209] The one or more processors 704 may be configured by the reporting unit 720 to receive a report with location information, such as an event report, from the UE via the external interface 702 using user plane signaling. The one or more processors 704 may also be configured by the reporting unit 720 to transmit a report with location information, such as an event report, to the GMLC, an external client, or an AF via the external interface 702 using user plane signaling. The one or more processors 704 may also be configured by the reporting unit 720 to transmit a periodic or triggered cumulative event report to the external client, AF, or GMLC via the external interface 702 using control plane signaling, the periodic or triggered cumulative event report indicating that the periodic or triggered location request remains operational, that the UE is still reporting events (e.g., still powered on and within network coverage) and may include statistical information about events reported since the last cumulative event report was transmitted (e.g., the number of event reports).

[0210] The one or more processors 704 may be configured by the positioning determination unit 722 to determine or verify a position estimate for the UE based on location information received from the UE and from the gNB, for example, using a UE-assisted positioning method as discussed herein. The one or more processors 704 may be configured by the positioning determination unit 722 to, for example, exchange LPP messages with the UE using user plane signaling to obtain positioning measurements and optionally provide assistance data. The one or more processors 704 may be configured by the positioning determination unit 722 to receive a request for assistance data from the UE and transmit the assistance data to the UE using control plane signaling or user plane signaling.

[0211] The one or more processors 704 may be configured by the control plane / user plane unit 724 to establish and cancel user plane connections and control plane connections. The one or more processors 704 may be configured by the control plane / user plane unit 724 to, for example, establish a user plane connection using IP, TCP, or both, and to establish a secure user plane connection based on security information such as a private authentication key or token.

[0212] The methodologies described herein may be implemented by various means depending on the application. For example, these methodologies may be implemented in hardware, firmware, software, or any combination thereof. For hardware implementation, one or more processors 704 may be implemented in 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.

[0213] For specific implementations involving firmware and / or software, these methodologies can be implemented with modules (e.g., procedures, functions, etc.) that perform the individual functions described herein. Any machine-readable medium that tangibly embodies instructions can be used to implement the methodologies described herein. For example, software codes can be stored in a memory and executed by one or more processor units so that the one or more processor units operate as a special-purpose computer programmed to perform the technology disclosed herein. The memory can be implemented within the processor unit or outside the processor unit. As used herein, the term "memory" refers to any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type of memory or any particular amount of memory, or the type of medium on which the memory is stored.

[0214] If implemented in firmware and / or software, the functions may be stored as one or more instructions or codes on a non-transitory computer-readable storage medium (such as memory 710). Examples of storage media include computer-readable media encoded with data structures and computer-readable media encoded with computer programs. Computer-readable media include physical computer storage media. The storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices, semiconductor storage devices or other storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer; as used herein, disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, where disks typically reproduce data magnetically, while optical disks reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0215] In addition to being stored on a computer-readable storage medium, instructions and / or data may also be provided as a signal on a transmission medium included in a communication device. For example, a communication device may include a transceiver having a signal indicating instructions and data. These instructions and data are stored on a non-transient computer-readable medium (e.g., memory 710) and are configured to cause one or more processors 704 to operate as a special-purpose computer programmed to perform the technology disclosed herein. That is, the communication device includes a transmission medium having a signal indicating information for performing the disclosed functions. At a first time, the transmission medium included in the communication device may include a first part of the information for performing the disclosed functions, and at a second time, the transmission medium included in the communication device may include a second part of the information for performing the disclosed functions.

[0216] A first entity in a wireless network configured to support location determination of a user equipment (UE), such as a network entity 700, may include means for receiving a request for locating a UE from a second entity in the wireless network, wherein the request for locating the UE is based on a location request initiated by an external client and received by the first entity from the second entity using control plane signaling, the means may be, for example, an external interface 702 and one or more processors 704 having dedicated hardware or implementing executable code or software instructions in a memory 710, such as a location request receiving unit 712. Means for transmitting information of a request for locating the UE to a third entity in the wireless network using control plane signaling, wherein the request for locating the UE and the information of the request for locating the UE each include a request to report location information using user plane signaling and an address to which the location information is to be reported, wherein the information of the request for locating the UE enables the third entity to obtain the location information of the UE using control plane signaling and report the location information of the UE to the external client using user plane signaling, may be, for example, an external interface 702 and one or more processors 704 having dedicated hardware or implementing executable code or software instructions in a memory 710, such as a location request transmitting unit 714.

[0217] In one specific implementation, the first entity may include means for receiving a response from the third entity using control plane signaling, wherein the response indicates activation or confirmation of the request for positioning the UE in the third entity, and the means may be, for example, the external interface 702 and one or more processors 704 having dedicated hardware or implementing executable code or software instructions in the memory 710, such as the confirmation receiving unit 716. The means for forwarding the response to the second entity may be, for example, the external interface 702 and one or more processors 704 having dedicated hardware or implementing executable code or software instructions in the memory 710, such as the confirmation transmitting unit 718.

[0218] Figure 8 is an example UE 800 (such as Figure 1A , Figure 1B and Figure 2 1 is a diagram of an example of a hardware implementation of a UE 105 as shown in FIG. 1 . UE 800 may include an external interface (such as a wireless transceiver 802) to wirelessly communicate with a base station in a radio access network (such as gNB 110-1). UE 800 may also use wireless transceiver 802 to communicate with elements in 5GCN (such as AMF 154 or LMF 152), as discussed herein and as described in detail in the accompanying drawings. Figure 4A UE 800 may also include additional transceivers, such as a wireless local area network (WLAN) transceiver 806 and a cellular phone for receiving and measuring signals from SPS SV 190 ( Figure 1A , Figure 1B and Figure 2 800 may also include one or more sensors 810, such as a camera, an accelerometer, a gyroscope, an electronic compass, a magnetometer, a barometer, etc. The UE 800 may also include a user interface 812 through which a user can interface with the UE 800, which may include, for example, a display, a keypad, or other input device (such as a virtual keypad on a display). The UE 800 also includes one or more processors 804 and a memory 820, which may be coupled together using a bus 816. The one or more processors 804 and other components of the UE 800 may similarly be coupled together using the bus 816, a separate bus, or may be directly connected together, or coupled using a combination of the foregoing. The memory 820 may contain executable code or software instructions that, when executed by one or more processors 804, cause the one or more processors to operate as a special-purpose computer programmed to execute the algorithms disclosed herein.

[0219] like Figure 8 As illustrated, the memory 820 may include one or more components or modules that may be implemented by one or more processors 804 to perform the methodologies described herein. Although each component or module is illustrated as software in the memory 820 that can be executed by one or more processors 804, it should be understood that each component or module may be dedicated hardware in or outside the one or more processors 804. As illustrated, the memory 820 may include a location request receiving unit 822 that enables the one or more processors 804 to receive a request for locating a UE from an entity in the wireless network (such as AMF 154, LMF 152, gNB 110-1, or gNB 110-2) via the wireless transceiver 802, wherein the request for locating the UE is based on a location request initiated by an external client and is received using control plane signaling.

[0220] The memory 820 may also include a confirmation unit 824 that enables the one or more processors 804 to return a confirmation of the request for locating the UE to the second entity via the wireless transceiver 802 using control plane signaling.

[0221] Memory 820 may also include a location information obtaining unit 828 that enables the one or more processors 804 to receive location information of the UE via the wireless transceiver 802 using control plane signaling.

[0222] In some implementations, the memory 820 may also include a location determination unit 830 that enables the one or more processors 804 to determine a location estimate for the UE using the obtained measurements, where the location estimate may be the received location information.

[0223] The memory 820 may also include a location information reporting unit 832 that enables one or more processors 804 to transmit the location information of the UE to an external client via the wireless transceiver 802 using user plane signaling, and the user plane signaling may be based on at least one of the Internet Protocol (IP), the Transmission Control Protocol (TCP), the Transport Layer Security (TLS), or some combination thereof. In some specific implementations, the location information reporting unit 832 may report the location information using user plane signaling. For example, the first location information may be reported using a protocol data unit (PDU) session of the UE. The one or more processors 804 may be configured by the location information reporting unit 832 to transmit an event report including location information (including location measurement and / or location estimation) directly to an external client or AF via the wireless transceiver 802, or via the LMF or GMLC, or via both the LMF and the GMLC using user plane signaling. The one or more processors 804 may also be configured by the location information reporting unit 832 to transmit a periodic or triggered cumulative event report to an external client, AF, LMF or GMLC via the wireless transceiver 802 using control plane signaling, the periodic or triggered cumulative event report indicating that the periodic or triggered location request remains operational, the UE is still reporting events (e.g., still powered on and within network coverage) and may include statistical information about the events reported since the last cumulative event report was transmitted (e.g., the number of event reports).

[0224] The memory 820 may also include a monitoring unit 834 that enables the one or more processors 804 to monitor the occurrence of one or more times, which may be, for example, periodic times or times of triggering events, wherein, for example, a location information obtaining unit 828 is used to obtain a location measurement at each time for signals received from multiple transmission points (TPs), signals received from entities outside the 5GS, or at least one of an inertial sensor of the UE; for example, at each time, at least some information in the first location information is determined by the location determination unit 830 based on the location measurement obtained at each first time; and at least some information in the first location information is transmitted to an external client after each time using user plane signaling, for example, using the location information reporting unit 832. The one or more processors 804 can be configured by the location information unit 828 to exchange LPP messages with the LMF to obtain and report positioning measurements, including, for example, requesting and receiving assistance data using user plane signaling or control plane signaling.

[0225] The one or more processors 804 may be configured by the control plane / user plane unit 836 to establish and cancel user plane connections and control plane connections. The one or more processors 804 may be configured by the control plane / user plane unit 836 to, for example, establish a user plane connection using IP, TCP, or both, and to establish a secure user plane connection based on security information such as a private authentication key or token.

[0226] The methodologies described herein may be implemented by various means depending on the application. For example, these methodologies may be implemented in hardware, firmware, software, or any combination thereof. For hardware implementation, one or more processors 804 may be implemented in 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.

[0227] For specific implementations of UE 800 involving firmware and / or software, these methodologies can be implemented with modules (e.g., procedures, functions, etc.) that perform the individual functions described herein. Any machine-readable medium that tangibly embodies instructions can be used to implement the methodologies described herein. For example, software codes can be stored in a memory (e.g., memory 820) and executed by one or more processors 804, so that one or more processors 804 operate as a special-purpose computer programmed to perform the techniques disclosed herein. The memory can be implemented within one or more processors 804 or external to one or more processors 804. As used herein, the term "memory" refers to any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type of memory or any particular amount of memory, or the type of medium on which the memory is stored.

[0228] If implemented in firmware and / or software, the functions performed by the UE 800 may be stored as one or more instructions or codes on a non-transitory computer-readable storage medium (such as memory 820). Examples of storage media include computer-readable media encoded with data structures and computer-readable media encoded with computer programs. Computer-readable media include physical computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices, semiconductor storage devices or other storage devices, or any other medium that can be used to store desired program codes in the form of instructions or data structures and can be accessed by a computer; as used herein, disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, where disks typically reproduce data magnetically, while optical disks reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0229] In addition to being stored on a computer-readable storage medium, instructions and / or data for UE 800 may also be provided as a signal on a transmission medium included in a communication device. For example, a communication device including part or all of UE 800 may include a transceiver having a signal indicating instructions and data. These instructions and data are stored on a non-transitory computer-readable medium (e.g., memory 820) and are configured to cause one or more processors 804 to operate as a special-purpose computer programmed to perform the technology disclosed herein. That is, the communication device includes a transmission medium having a signal indicating information for performing the disclosed functions. At a first time, the transmission medium included in the communication device may include a first part of information for performing the disclosed functions, and at a second time, the transmission medium included in the communication device may include a second part of information for performing the disclosed functions.

[0230] A first entity in a wireless network configured to support location determination of a user equipment (UE), such as a UE 800, may include means for receiving a request for locating the UE from a second entity in the wireless network, wherein the request for locating the UE is based on a location request initiated by an external client and received by the first entity from the second entity using control plane signaling, the means may be, for example, a wireless transceiver 802 and one or more processors 804 having dedicated hardware or implementing executable code or software instructions in a memory 820, such as a location request receiving unit 822. The means for obtaining first location information of the UE using control plane signaling may be, for example, a wireless transceiver 802 and one or more processors 804 having dedicated hardware or implementing executable code or software instructions in a memory 820, such as a location information obtaining unit 828. The means for reporting the first location information of the UE to the external client using user plane signaling may be, for example, a wireless transceiver 802 and one or more processors 804 having dedicated hardware or implementing executable code or software instructions in a memory 820, such as a location information reporting unit 832.

[0231] In one specific implementation, the first entity may include a component for returning an acknowledgment of the request for locating the UE to the second entity using control plane signaling, which component may be, for example, a wireless transceiver 802 and one or more processors 804 having dedicated hardware or implementing executable code or software instructions in a memory 820, such as a confirmation unit 824.

[0232] In one specific implementation, the first entity may include a component for monitoring the occurrence of each first time, which may be, for example, a wireless transceiver 802 and one or more processors 804 having dedicated hardware or implementing executable code or software instructions in memory 820, such as a monitoring unit 834. The component for obtaining a position measurement at each first time for at least one of a signal received from a plurality of transmission points (TPs), a signal received from an entity outside the 5GS, or an inertial sensor of the UE may be, for example, a wireless transceiver 802 and one or more processors 804 having dedicated hardware or implementing executable code or software instructions in memory 820, such as a position information obtaining unit 828. The component for determining at least some of the first position information at each first time based on the position measurement obtained at each first time may be, for example, a wireless transceiver 802 and one or more processors 804 having dedicated hardware or implementing executable code or software instructions in memory 820, such as a position determination unit 830. The means for transmitting at least some of the first location information to the external client after each first time using user plane signaling may be, for example, a wireless transceiver 802 and one or more processors 804 having dedicated hardware or implementing executable code or software instructions in memory 820, such as a location information reporting unit 832.

[0233] A specific implementation can be described as follows:

[0234] Clause 1: A method for locating a user equipment (UE) in a wireless network, the method comprising: receiving a request for locating the UE, wherein the request for locating the UE: comprises a periodic or triggered location request based on a location request initiated by an external client or an application function (AF), comprises one or more criteria for providing a cumulative event report, and is received by the UE using control plane signaling; in response to detecting a periodic or triggered event, performing the following operations, wherein the periodic or triggered event occurs at multiple different times: obtaining first location information of the UE, and reporting the first location information of the UE to the external client or AF using user plane signaling; and in response to determining that at least one of the one or more criteria for providing the cumulative event report has been met, transmitting the cumulative event report to the external client or AF using control plane signaling.

[0235] Clause 2: A method according to clause 1, wherein reporting the first location information of the UE to the external client or AF using user plane signaling includes: (1) reporting the first location information of the UE directly to the external client or AF, or (2) reporting the first location information of the UE via a location management function (LMF) or a home gateway mobile location center (H-GMLC) or both.

[0236] Clause 3: The method according to clause 2, wherein directly reporting the first location information of the UE to the external client or AF comprises: transmitting an event report message to the external client or AF using user plane signaling, wherein the first location information is included in the event report message.

[0237] Clause 4: A method as described in any of clauses 2 to 3, wherein the event report message comprises a supplementary service message, an HTTP message or a SUPL ULP message.

[0238] Clause 5: A method according to clause 2, wherein reporting the first location information of the UE to the external client or AF via the LMF comprises: transmitting a first event report message to the LMF using user plane signaling, wherein the first location information is included in the first event report message.

[0239] Clause 6: The method of clause 5, wherein the first event report message comprises a supplementary service message, an HTTP message, or a SUPL ULP message.

[0240] Clause 7: A method according to any one of clauses 5 to 6, wherein reporting the first location information of the UE to the external client or AF via the LMF further includes: after or when reporting the first location information, exchanging Long Term Evolution (LTE) Positioning Protocol (LPP) messages with the LMF using user plane signaling to provide positioning measurements to the LMF, thereby enabling the UE or the LMF to determine a location estimate of the UE, wherein the LMF uses user plane signaling to transmit a second event report message including the location estimate to the external client or AF.

[0241] Clause 8a: A method according to Clause 2, wherein reporting the first location information of the UE to the external client or AF via the H-GMLC includes: using user plane signaling to transmit a first event report message with the first location information to the H-GMLC, wherein the H-GMLC uses user plane signaling to transmit a second event report message including the location estimate to the external client or AF.

[0242] Clause 8b: The method of clause 8a, wherein the first event report message comprises a supplementary service message, an HTTP message, or a SUPL ULP message.

[0243] Clause 9: A method according to any one of clauses 1 to 8b, wherein the request for locating the UE includes at least one of: an indication to use user plane signaling to report the first location information, the type of user plane connection, or an address to which the first location information is to be reported.

[0244] Clause 10: A method according to clause 9, wherein the UE establishes a first user plane connection to at least one of the external client or AF or to another entity based on the address, wherein the other entity establishes a second user plane connection towards the external client or AF, wherein the first location information is reported using (1) the first user plane connection or (2) the first user plane connection and the second user plane connection.

[0245] Clause 11: The method of clause 10, wherein the first user plane connection and the second user plane connection are each based on at least one or both of Internet Protocol (IP) or Transmission Control Protocol (TCP).

[0246] Clause 12: A method as described in clause 11, wherein the first user plane connection, the second user plane connection, or both are secure and are established based on the received security information.

[0247] Clause 13: A method as described in any of clauses 11 to 12, the method further comprising: transmitting or receiving a cancellation of locating the UE using control plane signaling, wherein the first user plane connection is released after canceling the control plane connection.

[0248] Clause 14: A method according to any of clauses 1 to 13, wherein obtaining the first location information of the UE comprises: transmitting a request for assistance data to a location server using control plane signaling; and receiving assistance data from the location server using control plane signaling.

[0249] Clause 15: The method of any of clauses 1 to 14, wherein transmitting the cumulative event report to the external client or AF may further comprise transmitting the cumulative event report to a location server, a Home Gateway Mobile Location Center (H-GMLC), or both.

[0250] Clause 16: A user equipment (UE), the user equipment (UE) comprising: one or more transceivers; one or more memories; and one or more processors, the one or more processors being communicatively coupled to the one or more transceivers and the one or more memories, wherein the one or more processors are configured to: receive, via the one or more transceivers, a request for locating the UE, wherein the request for locating the UE: comprises a periodic or triggered location request based on a location request initiated by an external client or application function (AF), comprises one or more criteria for providing a cumulative event report, and is received by the UE using control plane signaling; in response to detecting a periodic or triggered event, perform the following operations, the periodic or triggered event occurring at multiple different times: obtain first location information of the UE, and report the first location information of the UE to the external client or AF using user plane signaling; and in response to determining that at least one of the one or more criteria for providing the cumulative event report has been met, transmit the cumulative event report to the external client or AF via the one or more transceivers using control plane signaling.

[0251] Clause 17: A UE according to Clause 16, wherein, in order to report the first location information of the UE to the external client or AF using user plane signaling, the one or more processors are configured to: (1) report the first location information of the UE directly to the external client or AF, or (2) report the first location information of the UE via a location management function (LMF) or a home gateway mobile location center (H-GMLC) or both.

[0252] Clause 18: A UE according to Clause 17, wherein, in order to report the first location information of the UE directly to the external client or AF, the one or more processors are configured to transmit an event report message to the external client or AF using user plane signaling, wherein the first location information is included in the event report message.

[0253] Clause 19: A UE according to any one of clauses 17 to 18, wherein, in order to report the first location information of the UE to the external client or AF via the LMF, the one or more processors are configured to transmit a first event report message to the LMF using user plane signaling, wherein the first location information is included in the first event report message.

[0254] Clause 20: A UE according to clause 19, wherein, in order to report the first location information of the UE to the external client or AF via the LMF, the one or more processors are further configured to: after or when reporting the first location information, exchange Long Term Evolution (LTE) Positioning Protocol (LPP) messages with the LMF using user plane signaling to provide positioning measurements to the LMF so as to determine the position estimate of the UE using a UE-assisted positioning method, wherein the LPP message includes a second event report message from the LMF, and the second event report message includes the position estimate sent to the external client or AF using user plane signaling.

[0255] Clause 21a: A UE according to clause 17, wherein, in order to report the first location information of the UE to the external client or AF via the H-GMLC, the one or more processors are configured to transmit a first event report message with the first location information to the H-GMLC using user plane signaling.

[0256] Clause 21b: The UE of clause 21a, wherein, for the first event report message, the one or more processors are configured to transmit a supplementary service message, an HTTP message, or a SUPL ULP message.

[0257] Clause 22: A UE according to any one of clauses 16 to 21b, wherein, in order to receive the request for locating the UE, the one or more processors are configured to receive at least one of: an indication to use user plane signaling to report the first location information, the type of user plane connection, or an address to which the first location information is to be reported.

[0258] Clause 23: A UE according to clause 22, wherein the one or more processors are configured to establish a first user plane connection to at least one of the external client or the AF or to another entity based on the address, wherein the one or more processors are configured to report the first location information using (1) the first user plane connection or (2) for a second user plane connection established by the other entity, the first user plane connection is a second user plane connection.

[0259] Clause 24: A UE according to any one of clauses 16 to 23, wherein, in order to obtain the first location information of the UE, the one or more processors are configured to: transmit a request for auxiliary data to a location server using control plane signaling; and receive auxiliary data from the location server using control plane signaling.

[0260] Clause 25: A UE according to any one of clauses 16 to 24, wherein, in order to transmit the cumulative event report to the external client or AF, the one or more processors are configured to transmit the cumulative event report to a location server, a home gateway mobile location center (H-GMLC), or both.

[0261] Clause 26: An apparatus for locating a user equipment (UE) in a wireless network, the apparatus comprising: a component for receiving a request for locating the UE, wherein the request for locating the UE: comprises a periodic or triggered location request based on a location request initiated by an external client or application function (AF), comprises one or more criteria for providing a cumulative event report, and is received by the UE using control plane signaling; a component for performing the following operations in response to detecting a periodic or triggered event, the periodic or triggered event occurring at multiple different times: obtaining first location information of the UE, and reporting the first location information of the UE to the external client or AF using user plane signaling; and a component for transmitting the cumulative event report to the external client or AF using control plane signaling in response to determining that at least one of the one or more criteria for providing the cumulative event report has been met.

[0262] Clause 27: An apparatus according to clause 25, wherein the component for reporting the first location information of the UE to the external client or AF using user plane signaling includes: a component for (1) reporting the first location information of the UE directly to the external client or AF, or (2) reporting the first location information of the UE via a location management function (LMF) or a home gateway mobile location center (H-GMLC) or both.

[0263] Clause 28: An apparatus according to clause 27, wherein the component for reporting the first location information of the UE directly to the external client or AF includes: a component for transmitting an event report message to the external client or AF using user plane signaling, wherein the first location information is included in the event report message.

[0264] Clause 29: An apparatus according to any one of clauses 27 to 28, wherein the component for reporting the first location information of the UE to the external client or AF via the LMF includes: a component for transmitting a first event report message to the LMF using user plane signaling, wherein the first location information is included in the first event report message.

[0265] Clause 30: A non-transitory computer-readable medium storing instructions for locating a user equipment (UE) in a wireless network, the instructions comprising code for performing the following operations: receiving a request for locating the UE, wherein the request for locating the UE: comprises a periodic or triggered location request based on a location request initiated by an external client or application function (AF), comprises one or more criteria for providing a cumulative event report, and is received by the UE using control plane signaling; in response to detecting a periodic or triggered event, performing the following operations, the periodic or triggered event occurring at multiple different times: obtaining first location information of the UE, and reporting the first location information of the UE to the external client or AF using user plane signaling; and in response to determining that at least one of the one or more criteria for providing the cumulative event report has been met, transmitting the cumulative event report to the external client or AF using control plane signaling.

[0266] A device having means for carrying out the method according to any one of clauses 1 to 15.

[0267] A non-transitory computer-readable medium storing instructions comprising code for performing the method according to any one of clauses 1 to 15.

[0268] References throughout this specification to "one example," "an example," "some examples," or "exemplary implementations" mean that the particular features, structures, or characteristics described in conjunction with the features and / or examples may be included in at least one feature and / or example of the claimed subject matter. Thus, phrases appearing throughout the specification in "one example," "an example," "some examples," or "in some implementations," or other similar phrases, do not necessarily all refer to the same features, examples, and / or limitations. Furthermore, these particular features, structures, or characteristics may be combined in one or more examples and / or features.

[0269] Some parts of the specific embodiments included herein are presented in the form of algorithms or symbolic representations of operations on binary digital signals stored in the memory of a specific device or a special computing device or platform. In the context of this specific specification, the term specific device, etc. includes a general-purpose computer that performs specific operations according to instructions from program software once programmed. Algorithmic descriptions or symbolic representations are examples of techniques used by ordinary technicians in signal processing or related fields to convey the essence of their work to other technicians in the field. The algorithm here is generally considered to be a self-consistent sequence of operations or similar signal processing that leads to a desired result. In this context, operations or processing involve physical manipulation of physical quantities. Typically, but not necessarily, such quantities can take the form of electrical or magnetic signals that can be stored, transferred, combined, compared or otherwise manipulated. Mainly for reasons of common use, it has been proven that it is sometimes convenient to refer to such signals as bits, data, values, elements, symbols, characters, items, numbers, numerical values, etc. However, it should be understood that all of these or similar terms should be associated with appropriate physical quantities and are merely convenient labels. Unless specifically stated otherwise, as is apparent from the discussion herein, it should be appreciated that throughout this specification, discussions utilizing terms such as "processing," "computing," "calculating," "determining," etc. refer to actions or processes of a specific apparatus such as a special purpose computer, a special purpose computing apparatus, or a similar special purpose electronic computing device. Thus, in the context of this specification, a special purpose computer or similar special purpose electronic computing device is capable of manipulating or transforming signals that are typically represented as physical electronic or magnetic quantities within a memory, register, or other information storage device, transmission device, or display device of the special purpose computer or similar special purpose electronic computing device.

[0270] In the above detailed description, numerous specific details are set forth to provide a thorough understanding of the claimed subject matter. However, those skilled in the art will appreciate that the claimed subject matter may be practiced without these specific details. In other instances, methods and devices known to those of ordinary skill in the art are not described in detail to avoid obscuring the claimed subject matter.

[0271] As used herein, the terms "and," "or," and "and / or" may include various meanings that are also intended to depend, at least in part, on the context in which such terms are used. Generally, "or," if used in connection with a list, such as A, B, or C, is intended to mean A, B, and C (where used in an inclusive sense) as well as A, B, or C (where used in an exclusive sense). Additionally, the terms "one or more," as used herein, may be used to describe any feature, structure, or characteristic in the singular, or may be used to describe a plurality of features, structures, or characteristics, or some other combination thereof. It should be noted, however, that this is merely an illustrative example, and claimed subject matter is not limited to this example.

[0272] While there has been illustrated and described what are presently considered to be example features, it will be appreciated by those skilled in the art that various other modifications may be made, and equivalents may be substituted, without departing from the claimed subject matter. Additionally, many modifications may be made to adapt a particular scenario to the teachings of the claimed subject matter without departing from the central concepts described herein.

[0273] Therefore, it is intended that the claimed subject matter not be limited to the particular examples disclosed, but that the claimed subject matter may also include all aspects falling within the scope of the appended claims and their equivalents.

Claims

1. A method performed by a user equipment (UE) for locating the UE in a wireless network, the method comprising: receiving a request for locating the UE, wherein the request for locating the UE: including periodic or triggered location requests based on location requests initiated by external clients or application functions (AFs), Include one or more criteria for providing cumulative incident reporting, and received by the UE using control plane signaling; In response to detecting a periodic or triggered event, the following operations are performed, the periodic or triggered event occurring at a plurality of different times: obtaining first location information of the UE, and Report the first location information of the UE to the external client or AF using user plane signaling; as well as In response to determining that at least one of the one or more criteria for providing the cumulative event report has been met, the cumulative event report is transmitted to the external client or the AF using control plane signaling.

2. The method according to claim 1, wherein reporting the first location information of the UE to the external client or AF using user plane signaling comprises: (1) reporting the first location information of the UE directly to the external client or AF, or (2) reporting the first location information of the UE via a Location Management Function (LMF) or a Home Gateway Mobile Location Center (H-GMLC) or both.

3. The method according to claim 2, wherein directly reporting the first location information of the UE to the external client or AF comprises: An event report message is transmitted to the external client or AF using user plane signaling, wherein the first location information is included in the event report message. 4 . The method of claim 3 , wherein the event report message comprises a supplementary service message, an HTTP message, or a SUPL ULP message.

5. The method according to claim 2, wherein reporting the first location information of the UE to the external client or AF via the LMF comprises: A first event report message is transmitted to the LMF using user plane signaling, wherein the first location information is included in the first event report message. 6 . The method of claim 5 , wherein the first event report message comprises a supplementary service message, an HTTP message, or a SUPL ULP message.

7. The method according to claim 5, wherein reporting the first location information of the UE to the external client or AF via the LMF further comprises: After or when reporting the first location information, long term evolution (LTE) positioning protocol (LPP) messages are exchanged with the LMF using user plane signaling to provide positioning measurements to the LMF, thereby enabling the UE or the LMF to determine a location estimate of the UE, wherein the LMF uses user plane signaling to transmit a second event report message including the location estimate to the external client or AF.

8. The method according to claim 2, wherein reporting the first location information of the UE to the external client or AF via the H-GMLC comprises: A first event report message with the first location information is transmitted to the H-GMLC using user plane signaling, wherein the H-GMLC transmits a second event report message including the location estimate to the external client or AF using user plane signaling.

9. The method of claim 1 , wherein the request for locating the UE comprises at least one of: an instruction to use user plane signaling to report the first location information, The type of user plane connection, or The address to which the first location information is to be reported.

10. The method of claim 9, wherein the UE establishes a first user plane connection to at least one of the external client or AF or to another entity based on the address, wherein the other entity establishes a second user plane connection toward the external client or AF, wherein the first location information is reported using (1) the first user plane connection or (2) the first user plane connection and the second user plane connection.

11. The method of claim 10, wherein the first user plane connection and the second user plane connection are each based on at least one or both of Internet Protocol (IP) or Transmission Control Protocol (TCP).

12. The method of claim 11, wherein the first user plane connection, the second user plane connection, or both are secure and established based on the received security information.

13. The method according to claim 11, further comprising: A cancellation of locating the UE is transmitted or received using control plane signaling, wherein the first user plane connection is released after canceling the control plane connection.

14. The method according to claim 1, wherein obtaining the first location information of the UE comprises: transmitting a request for assistance data to a location server using control plane signaling; as well as Assistance data is received from the location server using control plane signaling.

15. The method according to claim 1, wherein transmitting the accumulated event report to the external client or AF further comprises: The accumulated event report is transmitted to a location server, a Home Gateway Mobile Location Center (H-GMLC), or both.

16. A user equipment (UE), the user equipment (UE) comprising: one or more transceivers; one or more memories; and one or more processors communicatively coupled to the one or more transceivers and the one or more memories, wherein the one or more processors are configured to: receiving, via the one or more transceivers, a request for locating the UE, wherein the request for locating the UE: including periodic or triggered location requests based on location requests initiated by external clients or application functions (AFs), Include one or more criteria for providing cumulative incident reporting, and received by the UE using control plane signaling; In response to detecting a periodic or triggered event, the following operations are performed, the periodic or triggered event occurring at a plurality of different times: obtaining first location information of the UE, and Report the first location information of the UE to the external client or AF using user plane signaling; as well as In response to determining that at least one of the one or more criteria for providing the cumulative event report has been met, the cumulative event report is transmitted to the external client or the AF via the one or more transceivers using control plane signaling.

17. The UE according to claim 16, wherein: In order to report the first location information of the UE to the external client or AF using user plane signaling, the one or more processors are configured to: (1) report the first location information of the UE directly to the external client or AF, or (2) report the first location information of the UE via a location management function (LMF) or a home gateway mobile location center (H-GMLC) or both.

18. The UE according to claim 17, wherein: In order to report the first location information of the UE directly to the external client or AF, the one or more processors are configured to transmit an event report message to the external client or AF using user plane signaling, wherein the first location information is included in the event report message.

19. The UE according to claim 17, wherein: In order to report the first location information of the UE to the external client or AF via the LMF, the one or more processors are configured to transmit a first event report message to the LMF using user plane signaling, wherein the first location information is included in the first event report message.

20. The UE according to claim 19, wherein: In order to report the first location information of the UE to the external client or AF via the LMF, the one or more processors are further configured to: after or when reporting the first location information, exchange Long Term Evolution (LTE) Positioning Protocol (LPP) messages with the LMF using user plane signaling to provide positioning measurements to the LMF so as to determine the location estimate of the UE using a UE-assisted positioning method, wherein the LPP message includes a second event report message from the LMF, and the second event report message includes the location estimate sent to the external client or AF using user plane signaling.

21. The UE according to claim 17, wherein: To report the first location information of the UE to the external client or AF via the H-GMLC, the one or more processors are configured to transmit a first event report message having the first location information to the H-GMLC using user plane signaling.

22. The UE according to claim 16, wherein: To receive the request for locating the UE, the one or more processors are configured to receive at least one of: an instruction to use user plane signaling to report the first location information, The type of user plane connection, or The address to which the first location information is to be reported.

23. The UE of claim 22, wherein the one or more processors are configured to establish a first user plane connection to at least one of the external client or the AF or to another entity based on the address, wherein the one or more processors are configured to report the first location information using (1) the first user plane connection or (2) for a second user plane connection established by the other entity, the first user plane connection being a second user plane connection.

24. The UE according to claim 16, wherein: To obtain the first location information of the UE, the one or more processors are configured to: transmitting a request for assistance data to a location server using control plane signaling; and Assistance data is received from the location server using control plane signaling.

25. The UE according to claim 16, wherein: To transmit the cumulative event report to the external client or AF, the one or more processors are configured to transmit the cumulative event report to a location server, a Home Gateway Mobile Location Center (H-GMLC), or both.

26. An apparatus for locating a user equipment (UE) in a wireless network, the apparatus comprising: means for receiving a request for locating the UE, wherein the request for locating the UE: including periodic or triggered location requests based on location requests initiated by external clients or application functions (AFs), Include one or more criteria for providing cumulative incident reporting, and received by the UE using control plane signaling; Means for performing the following operations in response to detecting a periodic or triggered event, the periodic or triggered event occurring at a plurality of different times: obtaining first location information of the UE, and Report the first location information of the UE to the external client or AF using user plane signaling; and Means for transmitting the cumulative event report to the external client or the AF using control plane signaling in response to determining that at least one of the one or more criteria for providing the cumulative event report has been met.

27. The apparatus of claim 26, wherein the means for reporting the first location information of the UE to the external client or AF using user plane signaling comprises: A means for reporting the first location information of the UE (1) directly to the external client or AF, or (2) via a Location Management Function (LMF) or a Home Gateway Mobile Location Center (H-GMLC) or both.

28. The apparatus of claim 27, wherein the means for reporting the first location information of the UE directly to the external client or AF comprises: means for transmitting an event report message to the external client or AF using user plane signaling, wherein the first location information is included in the event report message.

29. The apparatus of claim 27, wherein the means for reporting the first location information of the UE to the external client or AF via the LMF comprises: means for transmitting a first event report message to the LMF using user plane signaling, wherein the first location information is included in the first event report message.

30. A non-transitory computer-readable medium storing instructions for locating a user equipment (UE) in a wireless network, the instructions comprising code for: receiving a request for locating the UE, wherein the request for locating the UE: including periodic or triggered location requests based on location requests initiated by external clients or application functions (AFs), Include one or more criteria for providing cumulative incident reporting, and received by the UE using control plane signaling; In response to detecting a periodic or triggered event, the following operations are performed, the periodic or triggered event occurring at a plurality of different times: obtaining first location information of the UE, and Reporting the first location information of the UE to the external client or AF using user plane signaling; and In response to determining that at least one of the one or more criteria for providing the cumulative event report has been met, the cumulative event report is transmitted to the external client or the AF using control plane signaling.