Using early data transmission for low-power periodicity and triggered positioning of mobile devices

Abstract

This article discusses techniques for low-power periodic and triggered location services for mobile devices using early data transmission (EDT). A location server (LS), such as in 5G LMF, sends a request to the UE for periodic or triggered location services, including a request for EDT and / or standardization. Upon confirmation of the request, the UE monitors for periodic or triggered events and, for each detected event, sends an event report to the LS, which may include location information. In an embodiment, the UE establishes a signaling connection with the RAN node but not with the core network to send the event report using EDT. The RAN node can then release the signaling connection immediately or after the LS returns a single response to the UE.

Description

[0001] This application is a divisional application of the invention patent application filed on June 3, 2019, with application number 201980041675.1 (international application number PCT / US2019 / 035225) and entitled "Low-power periodicity and triggered positioning of mobile devices using early data transmission".

[0002] Cross-references to related applications

[0003] This application claims U.S. Provisional Application No. 62 / 689,820, filed June 25, 2018, entitled “LOW POWER PERIODIC AND TRIGGERED LOCATION USING EARLY DATA TRANSMISSION”, and U.S. Provisional Application No. 62 / 732,558, filed September 17, 2018, entitled “LOW POWER PERIODIC AND TRIGGERED LOCATION USING EARLY DATA TRANSMISSION”, and U.S. Non-Provisional Application No. 16 / 368,204, filed March 28, 2019, entitled “LOW POWER PERIODIC AND TRIGGERED LOCATION USING EARLY DATA TRANSMISSION”, which have been assigned to the assignee and are expressly incorporated herein by reference in their entirety. Technical Field

[0004] This disclosure relates generally to communications, and more specifically to techniques for supporting periodic and triggered location services for user equipment (UE) under low power usage conditions. Background Technology

[0005] The 3rd Generation Partnership Project (3GPP) defines location solutions, known as control plane (CP) location solutions, for various radio access network (RAN) types, including GSM EDGE RAN (GERAN), Universal Terrestrial RAN (UTRAN), Evolved Universal Terrestrial RAN (E-UTRAN), and Next Generation RAN (NG-RAN). These location solutions are typically resource-intensive for both the radio network and the user equipment (UE). For example, for each location of the UE, the following are typically required: (a) assigning a signaling connection to both the RAN and the core network (CN) for the UE, and the UE entering a connected state (e.g., via paging through the RAN or via a service request from the UE); (b) allowing the UE to be authenticated and enabling encryption to begin; (c) generating internal network signaling to assign a Location Server (LS), such as an Enhanced Serving Mobility Center (E-SMLC) or a Location Management Function (LMF); (d) exchanging signaling between the UE and the LS, for example using the Long Term Evolution (LTE) Location Protocol (LPP), to coordinate and obtain location measurements; (e) the UE obtaining location measurements, using the location measurements to calculate its location, and sending the location measurements and / or the location to the LS; (f) the LS calculating the UE's location based on the received location measurements or verifying the received location; (g) the LS transmitting the UE's location to an external client via other network elements (e.g., a Gateway Mobility Center (GMLC)) or transmitting the UE's location to the UE; and (h) releasing the signaling connection and the LS assignment.

[0006] For UEs that are tracked periodically at intervals of five minutes or one hour (such as Internet of Things (IoT) UEs), the above process is typically battery-intensive. Furthermore, for networks supporting millions (or even billions) of UEs and / or IoT UEs, the process will consume network resources. Therefore, it may be desirable to develop positioning solutions that reduce network resource usage and UE battery consumption. Summary of the Invention

[0007] Early Data Transmission (EDT) is used to support periodic or triggered location services for User Equipment (UE). A Location Server (LS), such as 5GLMF, sends a request to the UE for periodic or triggered location services, including a request for EDT and / or a standard. After confirming the request, the UE monitors for periodic or triggered events and, for each detected event, sends an event report to the LS, which may include location information. In an embodiment, the UE establishes a signaling connection with the RAN node but not with the core network to send event reports using EDT. The RAN node can then release the signaling connection immediately or after the LS returns a single response to the UE.

[0008] In one implementation, a method performed by a user equipment (UE) to support periodic and triggered positioning for the UE includes: receiving a request for periodic or triggered positioning from a positioning server; sending a response to the positioning server confirming the periodic or triggered positioning; detecting periodic or triggered events; obtaining event information including at least one of location measurement, location estimation, a type of detected triggered event, or a combination thereof; obtaining a signaling connection to a radio access network (RAN) node, wherein the signaling connection does not include a signaling connection to a core network (CN) node; sending a first message to the RAN node, wherein the first message includes a non-access stratum (NAS) transport message, the NAS transport message including a routing identifier identifying the positioning server and an event report message containing the event information, wherein the RAN node forwards the NAS transport message to the CN node, and wherein the CN node forwards the event report message to the positioning server; and receiving a second message from the RAN node, wherein the second message releases the signaling connection to the RAN node.

[0009] In one embodiment, a user equipment (UE) capable of supporting periodic and triggered positioning includes: at least one wireless transceiver configured to wirelessly communicate with at least one wireless network; at least one memory; and at least one processor coupled to the at least one wireless transceiver and the at least one memory, and configured to receive a request for periodic or triggered positioning from a positioning server via the at least one wireless transceiver; send a response to the positioning server via the at least one wireless transceiver, the response confirming the periodic or triggered positioning; detect periodic or triggered events; and obtain event information including location measurements, location estimates, types of detected triggered events, or combinations thereof. The following steps are taken: obtaining a signaling connection to a Radio Access Network (RAN) node, wherein the signaling connection does not include a signaling connection to a Core Network (CN) node; sending a first message to the RAN node via the at least one radio transceiver, wherein the first message contains a Non-Access Stratum (NAS) transport message, the NAS transport message containing a routing identifier identifying the location server and an event report message containing the event information, wherein the RAN node forwards the NAS transport message to the CN node, wherein the CN node forwards the event report message to the location server; and receiving a second message from the RAN node via the at least one radio transceiver, wherein the second message releases the signaling connection to the RAN node.

[0010] In one implementation, a method performed by a positioning server to support periodic and triggered positioning of a user equipment (UE) includes: sending a request to the UE for periodic or triggered positioning, the request including an indication that the UE may report a detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both; receiving a response from the UE acknowledging the periodic or triggered positioning; receiving an event reporting message and a release assist indication (RAI) sent by the UE to a core network (CN) node, wherein the RAI includes a request for immediate connection release or a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the positioning server or an indication that the UE expects a response message from the positioning server, wherein the event reporting message contains an event message obtained by the UE after the UE detects a periodic or triggered event, wherein the event information includes at least one of location measurement, location estimation, a type of detected triggering event, or a combination thereof; determining location information of the UE based on the event information; and sending the location information of the UE to another entity.

[0011] In one embodiment, a location server for supporting periodic and triggered location of a user equipment (UE) includes: an external interface configured to communicate with a wireless network; and at least one processor coupled to the external interface and configured to: send a request for periodic or triggered location to the UE via the external interface, the request including indications that the UE may report a detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both; receive a response from the UE via the external interface confirming the periodic or triggered location; and receive, via the external interface, a request sent by the UE to the core network (CN) node. The CN node's event reporting message and release assist indication (RAI) include a request for immediate connection release or a request for early connection release. The request for early connection release includes an indication that the UE does not expect a response message from the location server or an indication that the UE expects a response message from the location server. The event reporting message contains an event message obtained by the UE after it detects a periodic or triggered event. The event information includes at least one of location measurement, location estimation, the type of detected triggered event, or a combination thereof. The event information is used to determine the UE's location information, and the UE's location information is sent to another entity via the external interface.

[0012] In one implementation, a method for supporting periodic and triggered location of a user equipment (UE) performed by a core network (CN) node includes: receiving a request for periodic or triggered location from a location server and sending the request for the periodic or triggered location to the UE, the request including an indication that the UE may report a detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both; receiving a response from the UE and sending the response to the location server, the response confirming the periodic or triggered location; and receiving a non-access stratum (NAS) transmission message and release assist sent by the UE to the RAN node from a radio access network (RAN) node. The NAS transmission message includes a routing identifier identifying the location server and an event report message, which contains an event message obtained by the UE after the UE detects a periodic or triggered event, wherein the event information includes at least one of location measurement, location estimation, the type of detected triggered event, or a combination thereof; and the transmission message includes the event report message and the RAI sent to the location server.

[0013] In one embodiment, a core network (CA) node for supporting periodic and triggered location of a user equipment (UE) includes: an external interface configured to communicate with a wireless network; and at least one processor coupled to the external interface and configured to: receive a request for periodic or triggered location from a location server via the external interface, and send the request for periodic or triggered location to the UE, the request including indications that the UE may report a detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both; receive a response from the UE via the external interface and send the response to the location server, the response confirming the periodic or triggered location; and receive data from a radio access network (RAN) node via the external interface. The system receives a Non-Access Stratum (NAS) transmission message and a Release Assist Indication (RAI) sent by the UE to the RAN node, wherein the RAI includes a request for immediate connection release or a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the location server or an indication that the UE expects a response message from the location server, wherein the NAS transmission message includes a routing identifier identifying the location server and an event report message, wherein the event report message contains an event message obtained by the UE after the UE detects a periodic or triggered event, wherein the event information includes at least one of location measurement, location estimation, the type of the detected trigger event, or a combination thereof; and the system sends the event report message and the RAI to the location server via the external interface.

[0014] In one implementation, a method for supporting periodic and triggered location of a user equipment (UE) performed by a radio access network (RAN) node includes: receiving a request for periodic or triggered location from a location server and sending the request for periodic or triggered location to the UE, the request including an indication that the UE may report a detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both; receiving a response from the UE and sending the response to the location server, the response confirming the periodic or triggered location; receiving a request for a signaling connection from the UE, wherein the signaling connection does not include a signaling connection to a core network (CN) node; providing the signaling connection to the UE; and from the... The UE receives a first message, wherein the first message includes a Release Assistance Indication (RAI), wherein the first message includes a Non-Access Stratum (NAS) transport message, the NAS transport message including a routing identifier identifying the location server and an event report message, the event report message including an event message obtained by the UE after detecting a periodic or triggered event, the event information including at least one of location measurement, location estimation, the type of the detected triggered event, or a combination thereof; sends the NAS transport message and the RAI to the CN node, wherein the CN node forwards the event report message and the RAI to the location server; and sends a second message to the UE, wherein the second message releases the signaling connection to the RAN node.

[0015] In one embodiment, a radio access network (RAN) node for supporting periodic and triggered location of a user equipment (UE) includes: an external interface configured to communicate with a radio network; and at least one processor coupled to the external interface and configured to: receive a request for periodic or triggered location from a location server via the external interface, and send the request for periodic or triggered location to the UE, the request including indications that the UE may report a detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both; receive a response from the UE via the external interface and send the response to the location server, the response confirming the periodic or triggered location; and receive a request for a signaling connection from the UE via the external interface, wherein the signaling connection does not include a core network (CN) node. The signaling connection to the RAN node is established via the external interface; the signaling connection is provided to the UE via the external interface; a first message is received from the UE via the external interface, wherein the first message includes a Release Assistance Indication (RAI), wherein the first message includes a Non-Access Stratum (NAS) transport message, the NAS transport message including a routing identifier identifying the location server and an event report message, the event report message including an event message obtained by the UE after detecting a periodic or triggered event, the event information including at least one of location measurement, location estimation, the type of detected triggered event, or a combination thereof; the NAS transport message and the RAI are sent to the CN node via the external interface, wherein the CN node forwards the event report message and the RAI to the location server; and a second message is sent to the UE via the external interface, wherein the second message releases the signaling connection to the RAN node. Attached Figure Description

[0016] The nature and advantages of the various embodiments can be understood by referring to the following figures.

[0017] Figure 1 This is a block diagram illustrating a non-roaming reference architecture for a control plane (CP) positioning solution in a 5G wireless network.

[0018] Figure 2 This is a block diagram illustrating a roaming reference architecture for a CP positioning solution in a 5G wireless network.

[0019] Figure 3 The signaling flow used to support UE-based positioning, UE-assisted positioning, and auxiliary data transmission is shown.

[0020] Figure 4The signaling flow used to support network-assisted and network-based positioning is shown.

[0021] Figure 5 The signaling flow used to support the positioning of one or more UEs is shown.

[0022] Figure 6-1 and Figure 6-2 A low-power MT-LR procedure for supporting periodicity and triggering positioning for roaming UEs is shown.

[0023] Figure 7 Another low-power MT-LR procedure for supporting periodicity and triggering positioning for roaming UEs is shown.

[0024] Figure 8-1 and Figure 8-2 Another low-power MT-LR procedure for supporting periodicity and triggering positioning for roaming UEs is shown.

[0025] Figure 9 It shows that for Figure 8-1 and Figure 8-2 The low-power MT-LR process shown is a procedure for changing the anchor LMF.

[0026] Figure 10 The process flow shown illustrates a method performed by a user equipment (UE) to support low-power periodicity and triggered positioning for the UE.

[0027] Figure 11 The process flow shown illustrates a method for supporting low-power periodicity and triggered positioning of user equipment, executed by a positioning server.

[0028] Figure 12 The process flow is shown, illustrating a method for supporting low-power periodicity and triggered location of user equipment, executed by the core network (CN) node.

[0029] Figure 13 The process flow is shown to illustrate a method for supporting low-power periodicity and triggered positioning of user equipment, performed by a radio access network (RAN) node.

[0030] Figure 14 This is a block diagram of an embodiment of LMF that can support the location service of the UE.

[0031] Figure 15 This is a block diagram of an embodiment that can support the Access and Mobility Management Function (AMF) of the UE's location services.

[0032] Figure 16 This is a block diagram of an embodiment of a RAN node capable of supporting the location services of a UE.

[0033] Figure 17 This is a block diagram of an embodiment of a UE that can support the UE's location services.

[0034] According to certain exemplary embodiments, the same reference numerals and symbols indicate the same elements in the various figures. Additionally, multiple instances of an element can be indicated by following a letter or hyphen after a first numeral and then a second numeral. For example, multiple instances of element 110 can be indicated as 110-1, 110-2, 110-3, etc. Similarly, multiple instances of element 150 can be indicated as 150S, 150V, 150H, etc. When only the first numeral is used to refer to this element, it should be understood that any instance of the element (e.g., element 110 in the previous examples will refer to any of elements 110-1, 110-2, and 110-3, while element 150 in the previous examples will refer to any of elements 150S, 150V, and 150H). Detailed Implementation

[0035] The 3rd Generation Partnership Project (3GPP) has defined and evaluated several solutions to support location services for user equipment (UEs) accessing fifth-generation (5G) wireless networks. One solution, referred to herein as the AMF-based location solution (also known as the AMF solution or AMF-based solution), is tightly integrated with the location solution for fourth-generation (4G) Long Term Evolution (LTE) radio access as defined in 3GPP Technical Specification (TS) 23.271, and requires all location requests to be processed and managed by the Serving Access and Mobility Management Function (AMF) for the target UE. Another solution, referred herein as the LMF-based location solution (also known as the LMF solution or LMF-based solution), requires all location requests to be processed and managed by the Location Management Function (LMF) in the serving 5G Core Network (5GCN) for the target UE, and has less impact on the location-specific aspects of the serving AMF. The third location solution, referred to herein as a combined AMF and LMF-based location solution (also known as a combined AMF and LMF solution or a combined AMF and LMF-based solution), combines aspects of both AMF-based and LMF-based location solutions by managing and coordinating the location of the target UE partly in the servicing AMF and partly in the LMF.

[0036] Periodic and triggered location services are location services in which event reports (typically each containing an estimate of the UE's location) for a target UE are sent to an external client at periodic intervals (e.g., fixed periodic intervals) and / or when certain triggered events occur. Triggered events may include the target UE moving into, out of, or remaining within a defined geographic area, or the target UE moving more than a minimum threshold straight-line distance from its previous location. Using periodic and triggered location services (e.g., over long periods of time such as an hour, day, or week), hundreds or even thousands of event reports for the UE can be sent to an external client, each typically containing an estimate of the UE's current location.

[0037] Traditionally, location services that support periodicity and triggering (e.g., as defined for LTE access in 3GPP TS 23.271) require the UE to report detected triggering events by establishing a signaling connection with the network and exchanging signaling with network nodes (e.g., MME or AMF) and / or location servers (LS) (e.g., E-SMLC or LMF) to report triggering events and achieve UE location. For low-power Internet of Things (IoT) devices, the use of signaling connections and the exchange of multiple signaling messages over a short period of time (e.g., 30 to 60 seconds) when sending a large number of event reports (e.g., hundreds or thousands of reports as mentioned above) can significantly reduce battery life. Furthermore, when used by many (e.g., millions) IoT devices, the network signaling and processing load can become excessive.

[0038] To reduce UE power consumption and network signaling and processing, the UE can report triggering events using connectionless messages, which are transmitted to the LS without any response from the LS. However, this may require new influences on the UE, RAN, and LS to support message delivery, message authentication, and message encryption, potentially increasing implementation costs and complexity. Another solution is to leverage Early Data Transmission (EDT), which enables Cellular IoT (CIoT) support for Small Data Transfer and Short Message Service (SMS) delivery via Narrowband IoT (NB-IoT) and LTE access. Through EDT, the UE can send an EDT request message (also known as an Early Data Request message) to the RAN node (e.g., eNB or gNB), containing a Non-Access Stratum (NAS) transport message. The NAS transport message may contain an embedded SMS message or a Data Protocol Data Unit (PDU) and a Release Assist Indication (RAI) (also known as a Release Assist Information), indicating whether the UE does not expect a response to the embedded SMS message or data PDU, or expects one. The RAN node can then forward the NAS transmission message and the indications for EDT and / or RAI to the core network (CN) node (e.g., MME or AMF). The CN node forwards the encapsulated data PDU or SMS message to its destination (e.g., via the Serving Gateway (SGW) and Packet Data Network Gateway (PDG) or Session Management Function (SMF) in the case of a data PDU, or via the MSC / VLR and SMS Gateway or SMS Function (SMSF) in the case of an SMS). If there is no pending downlink (DL) data or mobile terminal (MT) SMS known to the CN node, and if the RAI does not indicate that the UE expects a response, the CN node can send a release message to the RAN node to release the signaling connection to the UE. Otherwise, the CN node can wait for the response to be returned to the UE and / or can send any pending DL data or MT SMS messages to the UE before sending a release message to the RAN node. The EDT procedure can allow the UE to send uplink (UL) data or mobile originating (MO) SMS messages using a signaling connection with reduced duration without re-establishing any data bearer for the UE.

[0039] The EDT just described can be further enhanced to support periodic and triggered location-based event reporting for the UE, with the following enhancements labeled E1 to E4 for easy reference.

[0040] Enhanced E1: The NAS transport message included in the EDT request sent by the UE to the RAN node may include (i) an embedded UL positioning protocol (e.g., LPP) message and / or an embedded supplementary service message (e.g., the supplementary service message may contain a UL positioning protocol message), which contains measurement or location estimation; and (ii) a route ID indicating the destination LS (e.g., LMF). The CN node (e.g., AMF) then forwards the UL positioning protocol message and / or supplementary service message to the destination LS after receiving the NAS transport message from the RAN node.

[0041] Enhanced E2: Allows EDT requests sent by the UE to the RAN node to include an immediate release indication, which causes the RAN node to immediately release the signaling connection to the UE, thereby minimizing the duration of UE signaling and the signaling connection. The RAN node also indicates this immediate release to the CN node (e.g., AMF) when forwarding NAS transport messages to the CN node, which prevents the CN node from sending pending DL data or MT SMS to the UE and from returning a release message. In some embodiments, the immediate release indication may be indicated by a RAI (e.g., included therein).

[0042] Enhanced E3: When the LS initiates periodic and triggered location event reporting in the UE by sending a message (e.g., an LPP message or a supplemental service message) to the UE, the LS includes in that message a standard defining when the UE is allowed or required to use an EDT to send event reports and when the UE is allowed or required to use an EDT with immediate release to send event reports. For example, the standard may indicate that the UE uses an EDT with immediate release when it is idle and does not expect a response from the LS, uses an EDT without immediate release (also referred to as "early release") when it expects a single response from the LS, and otherwise, or after a certain threshold period or a threshold number of consecutive event reports using the EDT, the UE uses a regular NAS signaling connection instead of the EDT. In some embodiments, the standard may indicate a specific value of the RAI that the UE is allowed to include in the EDT request or NAS transport message (e.g., an RAI value indicating immediate release, an RAI value indicating early release where the UE does not expect a response from the LS, or an RAI value indicating early release where the UE expects a response from the LS).

[0043] Enhanced E4: The LS can use capability information supported by a positioning protocol (e.g., LPP) to determine the UE's capability to support the use of EDT for periodic and triggered positioning event reporting, where the LS requests and the UE returns UE positioning capabilities including whether the UE supports or does not support EDT.

[0044] As described above, as part of a positioning solution supporting LMF-based or a combined AMF and LMF-based positioning solution, the use of Early Data Transmission (EDT) from the UE can be employed to reduce the signaling load on both the UE and the serving wireless network (e.g., a 5G network) used for the UE. This document further describes the techniques used to support EDT for both LMF-based and combined AMF and LMF-based positioning solutions below.

[0045] Figure 1 This is a simplified block diagram illustrating a communication system 100 for non-roaming UE positioning using an AMF-based positioning solution, an LMF-based positioning solution, or a combined AMF and LMF positioning solution. The non-roaming communication system 100 includes a UE 105 and components of a fifth-generation (5G) network including a next-generation radio access network (NG-RAN) 112 and a 5G core network (5GCN) 150S. The NG-RAN 112 includes base stations (BSs) sometimes referred to as New Radio (NR) NodeBs or gNBs 110-1, 110-2, and 110-3 (collectively referred to herein as gNB 110), and the 5G core network (5GCN) 150S communicates with an external client 130 (also referred to as a Location Service (LCS) client). The combination of the 5GCN 150S and NG-RAN 112 can be referred to as a 5G system (5GS). 5GCN 150S is the serving 5GCN for UE 105 and is generally also the home 5GCN for UE 105 (e.g., to support non-roaming of UE 105). However, in some embodiments, 5GCN 150S may not be the home 5GCN when external client 130 is able to obtain the location of UE 105 from the access network for UE 105 while UE 105 is roaming (e.g., when external client 130 corresponds to a government agency or public safety agency). The 5G network may also be referred to as a New Radio (NR) network; NG-RAN 112 may be referred to as NR RAN or 5G RAN; and 5GCN 150S may be referred to as a Next Generation (NG) Core Network (NGC). Communication system 100 may also use information from satellite vehicle (SV) 190 for Global Navigation Satellite System (GNSS) such as GPS, GLONASS, Galileo, or BeiDou, or some other regional or regional satellite positioning system (SPS) such as IRNSS, EGNOS, or WAAS. The following describes the additional components of the communication system 100. The communication system 100 may include additional or alternative components.

[0046] It should be noted that Figure 1This is only a general illustration of the various components; any or all of these components may be used as appropriate, and each component may be repeated or omitted as needed. Specifically, although only one UE 105 is shown, it should be understood that many UEs (e.g., hundreds, thousands, millions of UEs, etc.) may utilize the communication system 100. Similarly, the communication system 100 may include more or fewer SV 190s, gNB 110s, external clients 130s, and / or other components. The connections shown linking the various components in the communication system 100 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. Furthermore, components may be rearranged, combined, separated, replaced, and / or omitted depending on the desired functionality.

[0047] although Figure 1 A 5G-based network is illustrated, but similar network implementations and configurations can be used for other communication technologies such as 3G, LTE, and IEEE 802.11 WiFi. For example, when using a wireless local area network (WLAN) (e.g., using an IEEE 802.11 radio interface), UE 105 can communicate with the access network (AN) instead of the NG-RAN, and therefore component 112 is sometimes referred to herein as AN or RAN, indicated by the terms "(R)AN", "(R)AN 112", or "RAN 112". In the case of an AN (e.g., IEEE 802.11AN), the AN can connect to a non-3GPP interoperability function (N3IWF) (…). Figure 1 (not shown in the image), while N3IWF is connected to AMF 154.

[0048] As used herein, UE 105 can be any electronic device and can be referred to as a device, mobile device, wireless device, mobile terminal, terminal, mobile station (MS), Secure User Plane Positioning (SUPL) Enabled Terminal (SET), or some other name. Furthermore, UE 105 can correspond to a smartwatch, digital glasses, fitness tracker, smart car, smart appliance, mobile phone, smartphone, laptop computer, tablet computer, PDA, tracking device, control device, or some other portable or mobile device. UE 105 may include a single entity or multiple entities, such as in a personal area network where users can employ audio, video, and / or data I / O devices and / or body sensors, as well as separate wired or wireless modems. Typically, although not required, UE 105 may use one or more Radio Access Technologies (RATs) to support wireless communication, such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), LTE, High Rate Packet Data (HRPD), IEEE 802.11 WiFi (also known as Wi-Fi). (BT), Global Microwave Access Interoperability (WiMAX), 5G New Radio (NR) (e.g., using NG-RAN 112 and 5GCN150S), etc. UE 105 can also support wireless communication using a wireless local area network (WLAN), which can be connected to other networks (e.g., the Internet) using, for example, Digital Subscriber Line (DSL) or packet cable. The use of one or more of these RATs can allow UE 105 to communicate with external clients 130 (e.g., via 5GCN 150S, not in use). Figure 1 The elements shown in the diagram, or may be transmitted via a gateway mobile location center (GMLC) 155) and / or allow an external client 130 to receive location information about the UE 105 (e.g., via GMLC 155).

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

[0050] In a particular implementation, UE 105 may have circuitry and processing resources capable of acquiring location-related measurements. Acquiring location-related measurements by UE 105 may include measurements of signals received from an SPS or Global Navigation Satellite System (GNSS) such as GPS, GLONASS, Galileo, or BeiDou, and / or may include measurements of signals received from a ground transmitter (e.g., GNB 110) fixed at a known location. UE 105, or a separate positioning server (e.g., LMF 152) to which UE 105 may send measurements, can then use any of several positioning methods based on these location-related measurements to obtain a location estimate for UE 105, such as, for example, GNSS, Auxiliary GNSS (A-GNSS), Advanced Forward Link Trilateral Measurement (AFLT), Observed Time Difference of Arrival (OTDOA), WLAN (also known as WiFi) positioning, or Enhanced Cell ID (ECID) or a combination thereof. In some of these technologies (e.g., A-GNSS, AFLT, and OTDOA), the pseudorange or timing difference can be measured at the UE 105 relative to three or more ground transmitters (e.g., gNB 110) fixed at known locations, or relative to four or more SV 190s or combinations thereof with accurately known orbit data, based at least in part on pilot, positioning reference (PRS) or other positioning-related signals transmitted by a transmitter or satellite and received at the UE 105.

[0051] A positioning server such as LMF 152 may be able to provide UE 105 with positioning assistance data, including, for example, information about the signal to be measured (e.g., expected signal timing, signal encoding, signal frequency, signal Doppler), the location and identification of a ground transmitter (e.g., gNB 110), and / or signal, timing, and orbit information for GNSS SV 190, to facilitate positioning technologies such as A-GNSS, AFLT, OTDOA, and ECID. This facilitation may include improving the signal acquisition and measurement accuracy of UE 105, and in some cases enabling UE 105 to calculate its estimated location based on location measurements. For example, the positioning server (e.g., LMF 152) may include a calendar indicating the location and identification of cellular transceivers and / or local transceivers in one or more specific areas (e.g., specific locations), and may provide UE 105 with information describing signals transmitted by cellular base stations or APs (e.g., gNB 110), such as transmission power and signal timing. UE 105 may obtain measurements of the signal strength of signals received from cellular transceivers and / or local transceivers (e.g., Received Signal Strength Indication (RSSI)), and / or may obtain signal-to-noise ratio (S / N), Reference Received Power (RSRP), Reference Received Quality (RSRQ), Time of Arrival (TOA), Receive Time-to-Transmit Time Difference (Rx-Tx), or Round-Trip Time of Transmission (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 transmit these measurements to a location server such as LMF 152 to determine the location of UE 105, or in some implementations, these measurements may be used in conjunction with auxiliary data (e.g., terrestrial calendar data or GNSS satellite data, such as GNSS calendar and / or GNSS ephemeris information) received from the location server (e.g., LMF 152) or broadcast by base stations in NG-RAN 112 (e.g., gNB 110) to determine the location of UE 105.

[0052] In the case of OTDOA, UE 105 can measure the reference signal time difference (RSTD) between signals such as a location reference signal (PRS), a cell-specific reference signal (CRS), or a tracking reference signal (TRS) transmitted by a pair of nearby transceivers and base stations (e.g., gNB 110). RSTD measurement can provide the time difference of arrival between signals (e.g., TRS, CRS, or PRS) received at UE 105 from two different transceivers. UE 105 can return the measured RSTD to a positioning server (e.g., LMF 152), which can calculate an estimated location for UE 105 based on the known location of the transceiver being measured and the known signal timing. In some implementations of OTDOA, the transceivers can accurately obtain a common universal time, such as GPS time or Coordinated Universal Time (UTC), for example using a GPS receiver at each transceiver, to accurately synchronize the signals used for RSTD measurement (e.g., PRS or CRS signals) to that common universal time.

[0053] The estimation of the location of UE 105 may be referred to as location, location estimation, location locking, location, position, location estimate, or location locking, and may be geodetic, thus providing location coordinates (e.g., latitude and longitude) for UE 105, which may or may not include an elevation component (e.g., altitude, surface height or surface depth, or above-ground height or below-ground height). Optionally, the location of UE 105 may be expressed as an urban location (e.g., expressed as a postal address or a designation of a point or small area (such as a specific room or floor) within a building). The location of UE 105 may also be expressed as an area or space in which UE 105 is expected to be located with a certain probability or confidence level (e.g., 67% or 95%, etc.) (defined geographically or in terms of urban morphology). The location of UE 105 can also be a relative location, which includes, for example, distance and direction defined relative to an origin at a known location or relative to a previous location of UE 105, or relative to X, Y (and Z) coordinates. This relative location can be defined geographically or in urban terms or by referring to a point, area, or space indicated on a map, floor plan, or building plan. In the description contained herein, unless otherwise indicated, the use of the term "location" can include any of these variations. When calculating the location of the UE, the local x, y, and z coordinates are typically solved first, and then the local coordinates are converted to absolute coordinates (e.g., latitude, longitude, and altitude above or below mean sea level) as needed.

[0054] like Figure 1 As shown, gNB 110 pairs in NG-RAN 112 can be connected to each other, for example, as Figure 1The connection is shown as either direct or indirect via another gNB 110. Access to the 5G network is provided to the UE 105 via wireless communication between the UE 105 and one or more of the gNBs 110. This can be achieved using 5G NR to provide wireless communication access to the 5GCN 150S on behalf of the UE 105. Figure 1 In this context, it is assumed that the serving gNB for UE 105 is gNB 110-1, but other gNBs (e.g., gNB 110-2 and / or gNB 110-3) may act as serving gNBs if UE 105 moves to another location, or other gNBs may act as auxiliary gNBs to provide additional coverage and bandwidth to UE 105. Figure 1 Some gNB 110s (e.g., gNB 110-2 or gNB 110-3) can be configured to act as location-only beacons, which can transmit signals (e.g., directional PRS) to assist the UE 105 in positioning, but may not be able to receive signals from the UE 105 or other UEs.

[0055] As mentioned, although Figure 1 Nodes configured to communicate according to 5G communication protocols are depicted, but nodes configured to communicate according to other communication protocols (such as, for example, LTE) can be used. Such nodes configured to communicate using different protocols can be controlled at least partially by the 5GCN 150S. Therefore, NG-RAN 112 can include any combination of gNBs, evolved Node Bs (eNBs), or other types of base stations or access points. As an example, NG-RAN 112 can include one or more next-generation eNBs (ng-eNBs) 114 that provide LTE radio access to UE 105 and can connect to entities in the 5GCN 150S, such as AMF 154.

[0056] The gNB 110 and / or ng-eNB 114 can communicate with the Access and Mobility Management Function (AMF) 154, which in turn communicates with the Location Management Function (LMF) 152 for location functionality. AMF 154 can support the network connectivity and mobility of UE 105, including cell changes and handovers, and can participate in supporting signaling connections to UE 105, and may assist in establishing and releasing Protocol Data Unit (PDU) sessions for UE 105. Other functions of AMF 154 may include: terminating the control plane (CP) interface from NG-RAN 112; terminating non-access stratum (NAS) signaling connections from UEs (such as UE 105), NAS encryption and integrity protection; registration management; connection management; reachability management; mobility management; access authentication and authorization.

[0057] When UE 105 accesses NG-RAN 112, LMF 152 can support UE 105's positioning and can support positioning procedures / methods such as Auxiliary 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 Transmission (AOD), WLAN positioning, RTT, and / or other positioning methods. LMF 152 can also process positioning service requests for UE 105 received, for example, from GMLC 155 or AMF 154. In some embodiments, the node / system implementing LMF 152 may additionally or alternatively implement other types of positioning support modules, such as Enhanced Serving Mobility Location Center (E-SMLC) or Secure User Plane Positioning (SUPL) positioning platform (SLP). Note that in some embodiments, at least a portion of the positioning functionality (including the derivation of the location of the UE 105) may be performed at the UE 105 (e.g., using signal measurements of signals transmitted by the wireless node and auxiliary data provided to the UE 105).

[0058] In the case of an AMF-based positioning solution or a positioning solution based on a combination of AMF and LMF, GMLC 155 can support positioning requests for UE 105 received from external client 130 and can forward such location requests to the serving AMF 154 of UE 105. AMF 154 can then forward the positioning request to LMF 152, which can (e.g., based on a request from external client 130) obtain one or more location estimates for UE 105 and can return the location estimates to AMF 154, which can then return the location estimates to external client 130 via GMLC 155. In an alternative LMF-based positioning solution, GMLC 155 can directly forward positioning requests received from external client 130 to LMF 152, thereby bypassing and not affecting the serving AMF 154. Then, similar to the AMF-based positioning solution, LMF 152 can obtain one or more location estimates from UE 105 and can return the location estimates directly to GMLC 155, which can then return the location estimates to external client 130 (for the AMF-based positioning solution).

[0059] For AMF-based positioning solutions, LMF-based positioning solutions, or positioning solutions based on a combination of AMF and LMF, GMLC 155 may include subscription information for external client 130 and may authenticate and authorize positioning requests for UE 105 from external client 130. GMLC 155 may further initiate a positioning session for UE 105 by sending a positioning request for UE 105 to AMF 154 or LMF 152 (e.g., depending on the type of positioning solution used), and may include the identity of UE 105 and the type of positioning requested (e.g., current positioning, or a sequence of periodic or triggered positioning) in the positioning request.

[0060] like Figure 1 As further shown, LMF 152 and gNB 110 can communicate using the New Radio Positioning Protocol A (NRPPa) defined in 3GPP TS 38.455, where NRPPa messages are transmitted between gNB 110 and LMF 152 via AMF154. Figure 1As further shown, LMF 152 and UE 105 can communicate using the LTE Positioning Protocol (LPP) defined in 3GPP TS 36.355, where LPP messages are transmitted between UE 105 and LMF 152 via serving AMF 154 and serving gNB 110-1 for UE 105. For example, LPP messages can be transmitted between LMF 152 and AMF 154 using a service operation based on Hypertext Transfer Protocol (HTTP), and LPP messages can be transmitted between AMF 154 and UE 105 using a 5G Non-Access Stratum (NAS) protocol. The LPP protocol can be used to support the positioning of UE 105 using UE-assisted 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), and / or Enhanced Cell Identity (ECID). The NRPPa protocol can be used to support the location of UE 105 using network-based location methods (such as ECID) (when used with measurements obtained by gNB 110), and / or the NRPPa protocol can be used by LMF 152 to obtain location-related information from gNB 110 to support OTDOA and ECID, such as parameters defining the location reference signal (PRS) transmission from gNB 110 and the location of gNB 110.

[0061] Using a UE-assisted positioning method, UE 105 can obtain location measurements (e.g., measurements of RSSI, RTT, RSTD, RSRP, and / or RSRQ for gNB 110, ng-eNB 114, or WLAN AP, or measurements of GNSS pseudorange, code phase, and / or carrier phase for SV 190) and send the measurements to a positioning server (e.g., LMF 152) to calculate a location estimate for UE 105. Using a UE-based positioning method, UE 105 can obtain location measurements (e.g., which may be the same as or similar to the location measurements for the UE-assisted positioning method) and can calculate the location of UE 105 (e.g., using auxiliary data received from a positioning server such as LMF 152 or broadcast by gNB 110, ng-eNB 114, or other base stations or APs). Using a network-based positioning method, one or more base stations (e.g., gNB 110 and / or ng-eNB 114) or APs can obtain location measurements (e.g., measurements of RSSI, RTT, RSRP, RSRQ, or TOA for signals transmitted by UE 105) and / or can receive measurements obtained by UE 105, and can send the measurements to a positioning server (e.g., LMF 152) to calculate a location estimate for UE 105.

[0062] The information provided to LMF 152 by gNB 110 using NRPPa may include timing and configuration information for PRS transmissions, as well as the location coordinates of gNB 110. LMF 152 may then provide some or all of this information to UE 105 as supplementary data in an LPP message via NG-RAN 112 and 5GCN 150S.

[0063] Depending on the desired functionality, the LPP message sent from LMF 152 to UE 105 can instruct UE 105 to perform any of a variety of operations. For example, the LPP message may contain instructions to enable UE 105 to obtain measurements for GNSS (or A-GNSS), WLAN, OTDOA, and / or ECID (or some other positioning method). In the case of OTDOA, the LPP message may instruct UE 105 to obtain one or more measurements (e.g., RSTD measurements) of PRS signals transmitted in a specific cell supported by a specific gNB 110 (or supported by one or more ng-eNBs 114 or eNBs). UE 105 may send the measurements back to LMF 152 via serving gNB 110-1 and AMF 154 in an LPP message (e.g., within a 5G NAS message).

[0064] In some embodiments, LPP can be enhanced by or replaced by an NR positioning protocol (NPP or NRPP) that supports positioning methods such as OTDOA and ECID for NR radio access. For example, an LPP message may contain an embedded NPP message, or may be replaced by an NPP message. In some other embodiments, LPP can be enhanced by an LPP extension (LPPe) protocol defined by the Open Mobile Alliance (OMA), where an LPP message may include an embedded LPPe message. The combined LPP and LPPe protocols can then be referred to as LPP / LPPe.

[0065] When NG-RAN 112 includes one or more ng-eNBs 114, the ng-eNBs 114 can communicate with the LMF 152 using NRPPa to support the positioning of UE 105 (e.g., using a network-based positioning method) and / or can transmit LPP and / or NPP messages between UE 105 and LMF 152 via ng-eNB 114 and AMF 154. The ng-eNBs 114 and / or gNBs 110 in NG-RAN 112 can also broadcast positioning assistance data to UEs (such as UE 105).

[0066] As shown in the figure, Unified Data Management (UDM) 156 can be connected to GMLC 155. UDM 156 is similar to a Home Subscriber Server (HSS) for LTE access, and UDM 156 can be combined with the HSS if needed. UDM 156 is a central database containing user-related and subscription-related information for UE 105, and can perform the following functions: UE authentication, UE identification, access authorization, registration and mobility management, subscription management, and SMS service management. Additionally, GMLC 155 is connected to Location Retrieval Function (LRF) 157, which handles the retrieval of location information for UE 105 and can be used, for example, to provide the location information of UE 105 to an external client 130 acting as a Public Safety Answering Point (PSAP) after an emergency call from UE 105 to the PSAP.

[0067] To support location services for Internet of Things (IoT) UEs, including those from external client 130, a Network Open Function (NEF) 159 may be included. For example, for UE 105 with LTE access to the Evolved Packet Core (EPC) instead of 5G NR radio access to the 5GCN 150S, the NEF may also be referred to as a Service Capability Open Function (SCEF). NEF 159 may be used, for example, to obtain the current or last known location of UE 105, an indication of changes in UE 105's location, or an indication of when UE 105 is available (or reachable). External client 130 may access a Service Capability Server (SCS). Figure 1 (Not shown in the image), the service capability server can access NEF 159 on behalf of external client 130 to provide location information for UE 105 to external client 130 via SCS. NEF 159 can connect to GMLC 155 to support UE 105's last known location, current location, and / or periodic and triggered location. If needed, NEF 159 may include or be combined with GMLC 155, and then the location information of UE 105 can be obtained directly from LMF 152 or AMF 154 (e.g., it may be connected to LMF 152 and / or AMF 154). For example, in combination later... Figure 6-1 In the procedure described in section 8, NEF 159 can replace HGMLC155H or can be combined with HGMLC 155H.

[0068] As described above, the AMF-based positioning solution uses the AMF as the primary anchor point for the target UE's positioning service. In the case of communication system 100, this would mean using the serving AMF 154 as the primary anchor point for obtaining one or more locations for UE 105. The AMF-based solution could then require all positioning requests from UE 105 to pass through and be managed and coordinated by AMF 154. Conversely, the LMF-based positioning solution could require all positioning requests to pass through and be managed and coordinated by the LMF in the target UE's serving 5GCN. In the case of communication system 100, this would mean using AMF152 as the primary anchor point for obtaining one or more locations for UE 105. Compared to the AMF-based solution, the LMF-based solution can have less positioning-specific impact on the serving AMF. However, the AMF-based solution can better match current EPC positioning solutions for LTE access as defined in 3GPP TS 23.271, which can reduce network impact when migrating from one solution to another or supporting both solutions.

[0069] From an efficiency perspective, for a single location request for the target UE, there may be little difference between an AMF-based solution and an LMF-based solution. However, for multiple location requests for the target UE 105 based on periodic or triggered events, the LMF-based solution can be more efficient than the AMF-based solution in terms of requiring less signaling and processing, and using fewer network entities and network interfaces. This can result in avoiding the transmission and support of location event reports for the UE 105 by the serving AMF 154, and avoiding the establishment and release of location sessions between AMF 154 and LMF 152 for each periodic or triggered location request required by the UE 105. Since location event reporting for periodic or triggered location requests can consume significant overall resource utilization, it may be necessary to optimize this part of the procedure using aspects of the LMF-based solution, while the part of the procedure related to initiating the location request and activating the location request in the target UE 105 (which executes only once) may require less optimization and can therefore retain aspects of the AMF-based solution. Therefore, in order to maintain consistency with the AMF-based positioning solution for a single positioning request for the target UE 105, a combined AMF and LMF-based solution can be used for periodic and triggered positioning. This solution uses elements from the AMF-based solution to initiate and establish delayed (e.g., periodic and triggered) positioning sessions and uses elements from the LMF-based solution to obtain and report individual positioning events.

[0070] Figure 2 It shows the relationship with Figure 1The communication system 100 shown is similar to, but supports, the positioning of roaming UE 105 in communication system 200. Similar to communication system 100, communication system 200 can provide roaming support for AMF-based positioning solutions, LMF-based positioning solutions, or positioning solutions based on a combination of AMF and LMF. In communication system 200, the core network 5GCN 150V, which communicates with UE 105 via NG-RAN 112, is an access network, also known as the Access Public Land Mobile Network (VPLMN), which communicates with the home network 5GCN 150H (also known as the Home Public Land Mobile Network (HPLMN)). In communication system 200, VPLMN 5GCN 150V includes a Positioning Management Function (LMF) 152. The LMF 152 in communication system 200 can perform functions related to positioning management functions (LMF) and positioning management functions (LMF) 152. Figure 1 The VPLMN 5GCN 150V also includes an Access Gateway Mobile Location Center (VGMLC) 155V, which is similar to... Figure 1 The GMLC 155 in the non-roaming communication system is designated as 155V to indicate that it is located in the access network of UE 105. Figure 2 As shown, in the case of an LMF-based positioning solution, the VGMLC 155V is connected to LMF 152 and LRF 157 in the VPLMN 5GCN 150V; in the case of an AMF-based positioning solution, it is connected to AMF 154 and LRF 157 in the VPLMN 5GCN 150V; or in the case of a positioning solution based on a combination of AMF and LMF, it is connected to AMF 154, LMF 152 and LRF 157 in the VPLMN 5GCN 150V.

[0071] As shown in the figure, the HPLMN 5GCN 150H may include a home GMLC (HGMLC) 155H, which can be connected (e.g., via the Internet) to a VGMLC 155V. Optionally (and as...) Figure 2 As shown by the dashed line in the diagram, in the case of an LMF-based positioning solution, the HGMLC 155H can be connected to the LMF 152; in the case of an AMF-based positioning solution, it can be connected to the AMF 154; or in the case of a positioning solution based on a combination of AMF and LMF, it can be connected to both LMF152 and AMF 154 (e.g., via the Internet), and in this case, it may not always be connected to the VGMLC 155V. The HGMLC 155H can be similar to... Figure 1The GMLC 155 is a non-roaming communication system and is designated as 155H to indicate that it is located in the home network of UE 105. VGMLC 155V and HGMLC 155H are sometimes collectively referred to as GMLC 155 herein. HGMLC 155H communicates with external client 130 and UDM 156 and LRF 147 in HPLMN 150H. LRF 147 can also communicate with external client 130 and can perform similar functions to LRF 157. HGMLC 155H can provide location access to UE 105 on behalf of external clients (such as external client 130). One or more of HGMLC 155H and LRF 147 can be connected to external client 130, for example, via another network such as the Internet. In some cases, located in another PLMN ( Figure 2 The request GMLC (RGMLC) in (not shown) can connect to the HGMLC 155H (e.g., via the Internet) to provide location access to UE 105 on behalf of an external client connected to the RGMLC. The RGMLC, HGMLC 155H, and VGMLC 155V can at least partially utilize the 3GPP CP solution defined in 3GPP TS 23.271 to support location access to UE 105. The HPLMN 5GCN 150H also includes a NEF 159, which may correspond to the NEF159 in communication system 100, and can connect to the HGMLC 155H.

[0072] To help reference the different interfaces and illustrate their correspondence with the EPC CP positioning solution defined in 3GPP TS 23.271, Figure 1 and Figure 2 Some interfaces (also known as reference points) are labeled with NLx corresponding to interface SLx for location support of LTE access by EPC (e.g., NLs corresponds to SL of EPC, NLg corresponds to SLg of EPC, and NLh corresponds to SLh of EPC). Figure 1 and Figure 2Interfaces designated Le, N2, NLg, NLg*, NLs, Lr, and NLh can be interfaces supporting control plane signaling and can be associated with control plane protocols used on one or more of these interfaces to support control plane signaling. In the case of NLg, NLg*, NLs, and NLh interfaces, the control plane protocol can support service-based operations and can be based on the Hypertext Transfer Protocol (HTTP). Additionally, the CP NG Application Protocol (NGAP) defined in 3GPP TS 38.413 can be used between AMF 154 and gNB 110 or ng-eNB114 via the N2 interface; the CP LPP or NPP protocol can be used between UE 105 and LMF 152; and CP supplementary service protocols (e.g., as defined in 3GPP TS 24.080) can be used between UE 105 and LMF 152 and / or between UE 105 and AMF 154.

[0073] As mentioned, although communication systems 100 and 200 are described regarding 5G technology, communication systems can be implemented to support other communication technologies, such as GSM, WCDMA, LTE, WiFi IEEE 802.11, etc., for supporting and interacting with mobile devices such as UE 105 (e.g., to implement voice, data, location, and other functionalities). For example, in some embodiments, non-3GPP interoperability functions (N3IWF, not included in 5GCN 150) can be used. Figure 1 and Figure 2 (As shown in the diagram) to connect the 5GCN 150S, 150V, and / or 150H to the WLAN. For example, the WLAN can support IEEE 802.11 WiFi access for UE105. Here, the N3IWF can connect to the WLAN as well as other elements in the 5GCN 150, such as the AMF 154. The positioning solution described herein can then operate in the same or similar manner as further described below, except that the LMF 152 no longer needs to interact with the NG-RAN 112 to obtain location-related information for UE105, but can instead interact with UE105 by sending and receiving LPP and / or NPP messages via the N3IWF and the WLAN.

[0074] In other embodiments, 5GCN 150S, 150V, and 150H (collectively referred to as 5GCN 150) can be configured to control different air interfaces, such as including one or more evolved NodeBs (eNBs) to replace the gNB 110 in an evolved Universal Terrestrial Radio Access Network (E-UTRAN). In some other embodiments, NG-RAN 112 and 5GCN 150S, 150V, and 150H can be replaced by other RANs and other core networks. For example, in an Evolved Packet System (EPS) supporting LTE access as defined by 3GPP: UE 105 can access EPS instead of NG-RAN 112 and 5GCN 150; NG-RAN 112 can be replaced by E-UTRAN containing eNBs instead of gNB 110; and 5GCN 150 can be replaced by an Evolved Packet Core (EPC) including a Mobility Management Entity (MME) replacing AMF 154, an Enhanced Serving Mobility Location Center (E-SMLC) replacing LMF 152, and a GMLC that can be similar to or the same as GMLC 155 (or VGMLC 155V or HGMLC 155H). In such an EPS, the E-SMLC can use the LPP A protocol (LPPa) defined in 3GPP TS 36.455 instead of NRPPa to send and receive location information from eNBs in the E-UTRAN, and LPP can be used to support the positioning of UE 105. Additionally, in some implementations, the base station (e.g., similar to or based on gNB 110 or ng-eNB 114) may be used as a location-only beacon and transmit signals (e.g., PRS) to assist the UE 105 in positioning, but does not receive signals.

[0075] Figure 3 The signaling flow of a positioning procedure is shown. This positioning procedure is applicable to communication systems 100 and 200 and is referred to herein as a UE-assisted and UE-based positioning procedure, which is used by LMF 152 to support UE-based positioning, UE-assisted positioning, and the transfer of auxiliary data. The procedure can be based on the LPP protocol used between LMF152 and UE 105, but it can also be applied to LPP / LPPe or NPP. The procedure can be applied to LMF-based positioning solutions, AMF-based positioning solutions, and / or positioning solutions based on a combination of AMF and LMF.

[0076] exist Figure 3In Phase 1, LMF 152 invokes the Namf_Communication_N1N2MessageTransfer service operation (e.g., as defined in 3GPP TS23.502) to AMF 154 to request the transmission of a downlink (DL) positioning (e.g., LPP) message to the UE. This service operation includes the DL positioning message and may include the UE 105 identifier (e.g., for an LMF-based positioning solution or a positioning solution based on a combination of AMF and LMF) or a location service (LCS) related identifier (e.g., for an AMF-based positioning solution). The downlink positioning message can request location information from the UE 105, provide auxiliary data to the UE 105, or query the UE 105's positioning capabilities.

[0077] At Phase 2, AMF 154 can identify UE 105 using the UE 105 identifier or LCS-related identifier received at Phase 1. If UE 105 is in an idle state, AMF 154 initiates a network-triggered service request procedure as defined in 3GPP TS 23.502 to establish a signaling connection with UE 105.

[0078] At phase 3, AMF 154 forwards the downlink location message to the UE in a DL NAS transport message. AMF 154 includes a routing identifier (e.g., the global or local address of LMF 152) in the DL NAS transport message.

[0079] At phase 4, UE 105 stores any auxiliary data provided in the downlink positioning message and performs any positioning measurements and location calculations requested by the downlink positioning message.

[0080] At phase 5, if UE 105 is in an idle state, UE 105 initiates a UE-triggered service request as defined in 3GPP TS23.502 in order to establish a signaling connection with AMF 154.

[0081] At phase 6, the UE returns any location information obtained in phase 4 or any location capabilities requested in phase 3 to AMF 154 in an uplink (UL) positioning (e.g., LPP) message included in the UL NAS transport message. The uplink positioning message may alternatively carry a request for further auxiliary data. The UE also includes the routing identifier received in phase 3 in the UL NAS transport message.

[0082] At phase 7, AMF 154 invokes the Namf_Communication_N1MessageNotify service operation (e.g., as defined in 3GPP TS 23.502) to LMF 152, indicated by the routing identifier received in phase 6. The service operation includes the uplink positioning message received in phase 6 and may include the UE 105 identifier (e.g., for an LMF-based positioning solution or a positioning solution based on a combination of AMF and LMF) or a positioning service (LCS) related identifier (e.g., for an AMF-based positioning solution). If UE 105 needs to send multiple messages in response to a request received in phase 3, phases 6 and 7 may be repeated. Phases 1 through 7 may be repeated to send new auxiliary data, as well as to request further location information and further UE 105 positioning capabilities.

[0083] Figure 4 The signaling flow of the procedure, applicable to communication systems 100 and 200 and referred to herein as a network-assisted positioning procedure, is shown. This procedure can be used by LMF 152 to support network-assisted and network-based positioning. The procedure can be based on the NRPPa protocol used between LMF 152 and (R)AN 112. The procedure can be applied to LMF-based positioning solutions, AMF-based positioning solutions, and / or positioning solutions based on a combination of AMF and LMF.

[0084] exist Figure 4 In Phase 1, LMF 152 invokes the Namf_Communication_N1N2MessageTransfer service operation (e.g., as defined in 3GPP TS23.502) to AMF 154 to request the transmission of a network location (e.g., NRPPa) message to the serving base station (e.g., gNB 110 or ng-eNB 114) of UE 105. The service operation includes the network location message and may include a UE 105 identifier (e.g., for an LMF-based positioning solution or a positioning solution based on a combination of AMF and LMF) or a location service (LCS) related identifier (e.g., for an AMF-based positioning solution). The network location message may request location information of UE 105 from (R)AN 112.

[0085] At Phase 2, AMF 154 can identify UE 105 using the UE 105 identifier or LCS-related identifier received at Phase 1. If UE 105 is in an idle state, AMF 154 initiates a network-triggered service request procedure as defined in 3GPP TS 23.502 to establish a signaling connection with UE 105.

[0086] At phase 3, AMF 154 forwards the network location message to the serving base station in the N2 transport message. AMF 154 includes a routing identifier (e.g., the global or local address of LMF 152) in the N2 transport message.

[0087] At phase 4, the serving base station obtains any location information of UE 105 requested in phase 3.

[0088] At phase 5, the serving base station returns any location information obtained in phase 4 to AMF 154 in the network location (e.g., NRPPa) message included in the N2 transport message. The serving base station also includes the routing identifier received in phase 3 in the N2 transport message.

[0089] At phase 6, AMF 154 invokes the Namf_Communication_N2InfoNotify service operation (e.g., as defined in 3GPP TS23.502) to LMF 152, indicated by the routing identifier received in phase 5. The service operation includes the network location message received in phase 5 and may include the UE 105 identifier (e.g., for an LMF-based location solution or a location solution based on a combination of AMF and LMF) or a location service (LCS) related identifier (e.g., for an AMF-based location solution). Phases 1 through 6 may be repeated to request further location information and further (R)AN112 capabilities.

[0090] Figure 5 Signaling flows are shown for a procedure applicable to communication systems 100 and 200 for obtaining network-assisted data associated with a non-UE, which can be used by LMF 152 to support network-assisted and network-based positioning. This procedure is not associated with a UE positioning session. It is used to obtain network-assisted data from a base station (e.g., gNB 110 or ng-eNB 114). The procedure can be based on NRPPa used between LMF 152 and (R)AN 112. The procedure can be applied to LMF-based positioning solutions, AMF-based positioning solutions, and / or positioning solutions based on a combination of AMF and LMF.

[0091] exist Figure 5In Phase 1, LMF 152 invokes the Namf_Communication_N1N2MessageTransfer service operation (e.g., as defined in 3GPP TS23.502) to AMF 154 to request the transmission of a network location (e.g., NRPPa) message to a target base station (e.g., gNB 110 or ng-eNB 114) in (R)AN 112. The service operation includes a network location message and a target base station identifier. The network location message can request location-related information from (R)AN 112.

[0092] At Phase 2, AMF 154 forwards the network location message to the target base station indicated in Phase 1 in the N2 transport message. AMF 154 includes a routing identifier (e.g., the global or local address of LMF 152) in the N2 transport message.

[0093] At phase 3, the target base station obtains any location-related information requested in phase 2.

[0094] At phase 4, the target base station returns any location-related information obtained in phase 3 to AMF 154 in the network location (e.g., NRPPa) message included in the N2 transport message. The target base station also includes the routing identifier received in phase 2 in the N2 transport message.

[0095] At phase 5, AMF 154 invokes the Namf_Communication_N2InfoNotify service operation (e.g., as defined in 3GPP TS23.502) to LMF 152, which is indicated by the routing identifier received in phase 4. The service operation includes the network location message received in phase 4 and may include the target base station identifier. Phases 1 through 5 may be repeated to request further location-related information from (R)AN 112.

[0096] Figure 6-1 and Figure 6-2 This paper summarizes periodic and triggered positioning procedures (which may be referred to as periodic and triggered 5GC-MT-LR) for roaming UE 105 in communication system 200, based on an LMF-based positioning solution. Periodic and triggered 5GC-MT-LR procedures for non-roaming UE 105 in communication system 100 may include... Figure 6-1 and Figure 6-2This is a subset of the procedure shown. The procedure enables periodic and triggered location of UE 105 with low resource utilization of UE 105 and VPLMN 150V. The procedure may not use EDT, but is based on a similar connectionless transmission of location event reports from UE 105 to LMF 152, where location determination and authentication of UE 105 can occur in real-time or non-real-time in LMF 152. (R)AN 112 allows location reports from multiple UEs to arrive at LMF 152 in batches to reduce signaling overhead, and prioritizes the transmission of location event reports according to Quality of Service (QoS) requirements.

[0097] Applicable to Figure 6-1 and Figure 6-2 The triggering events for the procedure can include any of the following: UE availability events, area events (e.g., UE 105 entering, leaving, or remaining in a defined geographic area), and motion events (e.g., UE 105 moving more than a threshold straight-line distance from a previous location). The LCS client 130 can request one or more of these events. For example, a UE availability event can be combined with a periodic event or another triggering event. When UE 105 is already available, a request for a UE availability event can be equivalent to requesting the current location of the target UE 105. This procedure allows the LMF 152 and VGMLC 155V to be combined to reduce signaling and enforcement impact. Privacy requirements can be configured in the HGMLC 155H or transmitted from the UDM 156 to the HGMLC 155H. The same LMF 152 can be used for each consecutive periodic or triggered location event, thereby avoiding the overhead of assigning and releasing the LMF 152 for each location event and enabling the information obtained by the LMF 152 to be used for previous location fixation.

[0098] exist Figure 6-1In Phase 1, the external LCS client 130 sends a location request for periodic and triggered location of the target UE 105 to the HGMLC155H in the HPLMN 150H of the UE 105. The location request provides the type of location report requested and associated parameters. For periodic location, the request may include the time interval between consecutive location reports and the total number of reports. For triggered reports of area events, the request includes details of the target area, whether the triggering event to be reported is within, entering or leaving the target area for the UE 105, and whether the event report should include a UE location estimate. For triggered reports of motion events, the request includes a threshold linear distance for the triggered location report and whether the event report should include a UE location estimate. For UE-available triggering events, additional parameters may not be required. The HGMLC 155H can verify the privacy requirements of the UE 105. Note that the external LCS client 130 may alternatively be located via NEF 159 (…). Figure 6-1 (Not shown) Access to the network function (NF) or application function (AF) of HGMLC 155H.

[0099] exist Figure 6-1 In phases 2 and 3, HGMLC 155H queries UDM 156 for the service AMF154 address, UE 105 privacy requirements, and possible VGMLC 155V and / or LMF 152 address.

[0100] At Phase 4, if no VGMLC 155V address is returned in Phase 3, the HGMLC 155H can use the Network Repository Function (NRF) service in the HPLMN150H to select an available VGMLC 155V from among the VPLMN 150Vs based on the VPLMN 150V address included in the AMF 154 address received in Phase 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., Subscription Permanent Identifier (SUPI) or General Public Subscription Identifier (GPSI)), any LMF 152 addresses received in Phase 3, and any privacy requirements of the UE 105. The HGMLC 155H also includes in the location request the type of location report requested and associated parameters, as well as a reference number to identify subsequent responses. For area event reporting, the HGMLC 155H, VGMLC 155V, or LMF 152 can convert the target area into a set of cells or tracking areas (TAs) equivalent to those in the VPLMN 150V.

[0101] At stage 5, the VGMLC 155V determines the LMF 152 in the VPLMN 150V and invokes the Nlmf_ProvideLocation Request service operation to forward the location request to the LMF 152. This stage can be omitted if the VGMLC 155V and LMF 152 functions are combined. Note that the VGMLC 155V can determine the LMF 152 using the following alternatives labeled A1 through A4.

[0102] Alternative A1: If the VGMLC, LMF, and AMF are fully interconnected in the VPLMN 5GCN 150V (e.g., via the carrier's IP intranet), then the VGMLC 155V can determine the LMF 152 based on any appropriate criteria (e.g., location QoS, LCS client type, VGMLC 155V identity). As an example, the VGMLC 155V can be configured with all LMFs in the VPLMN 150V, and the LMFs can be selected in a round-robin fashion.

[0103] Alternative A2: If AMFs are allowed to use some, but not all, of the LMFs in VPLMN 5GCN 150V, then VGMLC 155V can be configured with the LMFs allowed for each AMF, and then LMFs can be selected based on specific criteria (e.g., QoS) or randomly.

[0104] Alternative A3: VGMLC 155V can use the NRF service in VPLMN 5GCN 150V to request the set of available LMFs in VPLMN5GCN 150V, and then select an LMF 152 as in Alternative A1.

[0105] Alternative A4: When UE 105 registers with VPLMN 5GCN 150V, serving AMF 154 can (e.g., using NRF services) select LMF 152. Then, either AMF 154 or LMF 152 can provide the LMF 152 address along with the AMF 154 address to UDM 156. UDM 156 can then provide the LMF 152 address to HGMLC 155H in phase 3, which will then provide the address to VGMLC 155V in phase 4.

[0106] At stage 6, as an optional optimization and as an alternative to performing stages 4 and 5, if the HGMLC155H can determine or select the LMF 152 (e.g., based on the VPLMN 5GCN 150V identity or AMF154 address, using the NRF service or by receiving the NMF 152 from the UDM 156 in stage 3), the HMLC 155H can invoke the Nlmf_ProvideLocation Request service operation to forward the location request directly to the LMF 152.

[0107] At stages 7 to 10, if LMF 152 supports the requested periodicity and triggered location type, LMF 152 returns an acknowledgment to LCS client 130 via VGMLC 155V and / or HGMLC 155H, indicating that the request for periodicity or triggered location has been accepted.

[0108] At phase 11, LMF 152 invokes the Namf_MT_EnableUEReachabilityRequest service operation to serving AMF 154 to verify UE 105 reachability. Note that if serving AMF 154 is no longer available, LMF 152 can use the NRF service in VPLMN 5GCN 150V to select another AMF 154 from the same set of AMFs as the previous serving AMF 154.

[0109] At stage 12, if UE 105 is currently in a 3GPP connected state, this stage is skipped. Otherwise, if UE 105 is currently in an idle but reachable cellular (e.g., NR or LTE) access state, AMF 154 executes a 3GPP network-triggered service request (e.g., as defined in 3GPP TS 23.502) to place UE 105 in a connected state.

[0110] At stage 13, AMF 154 calls the Namf_MT_EnableUEReachability Response service operation to LMF 152 to confirm the reachability of UE 105.

[0111] At stages 14 and 15, if UE 105 is unreachable (e.g., using Extended Discontinuous Receive (eDRX) or Power Saving Mode (PSM)), LMF 152 calls the Namf_EventExposure_Subscribe service operation to AMF 154 so that AMF 154 can inform UE 105 when it becomes reachable again. At this point, and if UE 105 may not already be in a connected state, LMF 152 can execute stages 11 to 13 again. After UE 105 becomes reachable, LMF 152 can also execute stages 14 and 15 to obtain UE 105's current access type (i.e., cellular NR or LTE and / or WLAN) and any serving cell IDs from AMF 154. Note that if the serving AMF 154 for UE 105 changes within the same VPLMN 5GCN 150V when UE 105 becomes reachable, the old AMF 154 can notify LMF 152, and LMF 152 can execute phases 14 to 15 to obtain the current access type and any serving cell ID of UE 105 from the new AMF 154.

[0112] At phase 16, once UE 105 is reachable, LMF 152 can notify and verify UE 105's privacy requirements based on any privacy requests received from HGMLC 155H in phases 4 through 6. If this occurs, LMF 152 sends a supplemental service location notification call to UE 105 via service AMF 154 using the Namf_Communication_N1N2MessageTransfer service operation. Note that for phases 16 and 17, the transmission of supplemental service messages between LMF 152 and UE 105 can be based on any privacy requests received from HGMLC 155H in phases 4 through 6. Figure 3 The program described is used for exchanging location protocol messages.

[0113] At stage 17, if UE 105 privacy needs to be verified, UE 105 notifies its user of the location request and verifies user permission for the location request. UE 105 then returns a supplemental service location notification response to LMF 152, indicating whether the user grants or denies permission for the location request when verifying UE 105 privacy. The supplemental service response is transmitted via service AMF 154 and passed to LMF 152 using the Namf_Communication_N1MessageNotify service operation. Note that for IoT UE 105 (e.g., since there are typically no users of IoT UEs), stages 16 and 17 may be unnecessary (e.g., may be omitted).

[0114] At stage 18, if a triggered location for a UE-available event is requested, or if an initial UE 105 location is requested for another type of periodic or triggered location request, then LMF152 executes the following steps: Figures 3 to 5 One or more of the location procedures described herein shall perform the location of UE 105. LMF 152 then uses the information obtained in this stage and / or stage 15 to determine the location of UE 105. If no other triggered or periodic location report is requested, LMF 152 may skip stages 19 to 20 and 25 to 38 and execute stages 21 to 24 to return the location of UE 105 to LCS client 130, after which the procedure terminates.

[0115] exist Figure 6-2 In phase 19, LMF 152 uses the Namf_Communication_N1N2MessageTransfer service operation to send a message to UE 105 via service AMF 154. This message may be a supplemental service message, a location protocol (e.g., LPP or NPP) message, or may include both (e.g., a supplemental service message carrying an embedded LPP message). LMF 152 includes in the message a request for periodic or triggered location reporting from UE 105 (including the type of event to be reported) and the type of location measurement or location estimate to be provided by UE 105 for location reporting at phase 29. LMF 152 also includes a routing identifier identifying LMF 152 in the Namf_Communication_N1N2MessageTransfer service operation, which is transmitted to UE 105 by AMF 154 (e.g., in a DL NAS transport message carrying a message from LMF 152). Additionally, LMF 152 includes in the message a request for UE 105 to send an event report at phase 29 using connectionless transmission via (R)AN 112, and includes: (i) one or more UE IDs for connectionless reporting (e.g., locally assigned to UE 105 by LMF 152); (ii) encrypted information; (iii) priority indication; and (iv) a criterion for whether to use connectionless transmission or NAS signaling connection for reporting.

[0116] exist Figure 6-2In phase 20, if the request in phase 19 can be supported, UE 105 returns an acknowledgment to LMF 152 in a supplemental service and / or location protocol (e.g., LPP) message. This acknowledgment is transmitted via service AMF 154 and delivered to LMF 152 using the Namf_Communication_N1MessageNotify service operation. In this acknowledgment, UE 105 indicates whether connectionless transmission is also supported for sending event reports, in addition to transmission via NAS signaling connection.

[0117] At stages 21 to 24, LMF 152 sends a response to LCS client 130 via VGMLC 155V and / or HGMLC 155H, the response carrying any location estimates obtained at stage 18 and confirmation of the activation of event reporting for periodic or triggered positioning in UE 105. VGMLC 155V (if used) can then release status information for periodic and triggered 5GC-MT-LR requests.

[0118] At phase 25, UE 105 monitors for the occurrence of the periodic and / or triggering events requested at phase 19. This monitoring can be performed when UE 105 is idle and / or when UE 105 is unreachable from the network (e.g., using eDRX or PSM). If triggering events need to be detected, UE 105 can also (e.g., periodically) request auxiliary data from LMF 152 to help determine location. When a triggering event is detected, UE 105 proceeds to phase 26.

[0119] At phase 26, UE 105 determines, based on the criteria received in phase 19, whether to report the triggering event using connectionless delivery or NAS signaling connection. If UE 105 is already in a connected state or can only access 5GCN 150V via a type of (R)AN 112 node that does not support connectionless delivery, then UE 105 determines to use NAS signaling connection.

[0120] At phase 27, if UE 105 determines at phase 26 that it wants to use the NAS signaling connection, then UE 105 according to... Figure 3 Phases 5 through 7 are used to send supplemental service messages and / or location protocol messages (or a combination thereof) to the LMF 152. These messages may indicate the type of event detected at phase 25 and may include location estimation or location measurement (e.g., if requested at phase 19). The LMF 152 can use... Figures 3 to 5The procedure in the process requests additional location information from UE 105 and / or from (R)AN 112, and the location estimate of UE 105 can be determined, for example, based on such information (e.g., if requested at stages 4 to 6). UE 105 then skips stages 28 to 33.

[0121] At phase 28, if UE 105 determines at phase 26 that it will use connectionless transmission, then UE 105 obtains any location measurements or location estimates requested in phase 19. If UE 105 is using cellular (e.g., NR or LTE) access, then UE 105 determines a suitable temporary serving cell and requests and obtains a signaling channel or signaling connection with the associated RAN node in (R)AN 112. When (R)AN 112 is NG-RAN (e.g., NG-RAN 112 for communication systems 100 or 200), the RAN node can be gNB 110 or ng-eNB 114.

[0122] At phase 29, UE 105 sends a location message to the RAN node for cellular access, or to the N3IWF in 5GCN 150V for WLAN access. The location message includes the routing identifier of LMF 152 received in phase 19, the UE ID or one of multiple UE IDs received in phase 19, the authentication code for authenticating the UE ID received in phase 19, and a priority indication. The location message also includes location protocol (e.g., LPP) and / or supplementary service messages, which include any location measurements or location estimates obtained in phase 28 and may identify the type of reported event. The location protocol and / or supplementary service messages may be encrypted using encryption information received in phase 19. Other unencrypted content of the location message.

[0123] At stage 30, in the case of cellular access, UE 105 and RAN node release signaling channels or signaling connections.

[0124] At phase 31, for cellular access, the RAN node can obtain uplink location measurements of the UE signaling received at phases 28 and / or 29. For example, the RAN node can obtain measurements of RSSI, TOA, Rx-Tx, RTT, or AOA. The RAN node sends a network location message (e.g., an NRPPa message) included in the N2 transport message to the AMF 154 (e.g., this may differ from the AMF 154 in phases 11 through 20). The network location message includes any uplink location measurements obtained by the RAN node, as well as the location protocol and / or supplementary service messages received at phase 29, the UE ID, authentication code, and priority indication. The RAN node also includes the routing identifier of the LMF 152 received at phase 29 in the N2 transport message. The RAN node can use the priority indication to expedite the transmission of the network location message and / or include information about additional UEs associated with the same LMF 152 in the same network location message. The LMF 152 can handle and process any information about additional UEs independently.

[0125] At phase 32, AMF 154 invokes the Namf_Communication_N2InfoNotify service operation to LMF 152, which is indicated by the routing identifier received in phase 31. The service operation includes the network location message received in phase 31.

[0126] At phase 33, LMF 152 identifies UE 105 using the UE ID from the network location message and authenticates the UE ID using the authentication code from the network location message. Then, if the location protocol and / or supplementary service messages in the network location message are encrypted, LMF 152 decrypts them. If a request to include location estimation in the event report is made in phase 5 or phase 6, LMF 152 uses any uplink location measurements included in the network location message and any location measurements or location estimates included in the location protocol and / or supplementary service messages to determine or verify the location estimate of UE 105. LMF 152 may use priority indications from the network location message at phase 33 to expedite or delay the processing of the network location message.

[0127] At stage 34, LMF 152 selects VGMLC 155V (which may be different from the VGMLC 155V in stages 4 through 8) and invokes the Nlmf_EventNotify service operation on VGMLC 155V with the indication of the reported event type, reference number, H-GMLC155H address, and location estimate (if this location estimate was requested and obtained at stage 27 or stage 33). If LMF 152 and VGMLC 155V are combined, stage 34 can be omitted.

[0128] At stage 35, the VGMLC 155V will forward the information received in stage 34 to the HGMLC155H.

[0129] At stage 36, as an optional optimization, stages 34 and 35 are omitted, while LMF 152 sends the information directly to HGLMC 155H in stage 34.

[0130] At phase 37, the HGMLC 155H uses the reference number received in phase 35 or phase 36 to identify the periodic and triggered location request received in phase 1, and then sends the location estimate and the type of the reported trigger event to the external LCS client 130.

[0131] At phase 38, as in phase 25, UE 105 continues to monitor and detect further triggering events, and triggers phases 26 to 37 each time a triggering event is detected.

[0132] Figure 7 This paper summarizes another periodic and triggered positioning procedure (which may be referred to as periodic and triggered 5GC-MT-LR) for roaming UE 105 in communication system 200, based on an LMF-based positioning solution. A periodic and triggered 5GC-MT-LR procedure for non-roaming UE 105 in communication system 100 may include... Figure 7 This is a subset of the procedures shown. This procedure enables the periodicity and triggering of the UE 105 with low resource utilization of UE 105 and VPLMN 150V. This procedure has... Figure 6-1 and Figure 6-2 The procedures have the same characteristics, but use enhancements E1 to E4 previously described for EDT. For example: (i) enabling UE 105 to use EDT and RAI to report the occurrence of triggering events and provide associated location information; (ii) enabling UE to request immediate release of the signaling connection by RAN 112 after sending an event report using EDT, which minimizes the duration of the signaling connection; (iii) enabling UE 105 to indicate the expectation of receiving a single response from LMF 152, followed by release of the signaling connection by AMF 154, which reduces the duration of the signaling connection; and (iv) UE 105 can provide RAI at the Access Layer (AS) level or the NAS level.

[0133] exist Figure 7 Phases 1 to 18, execution Figure 6-1 Phases 1 to 18.

[0134] exist Figure 7In phase 19, LMF 152 uses the Namf_Communication_N1N2MessageTransfer service operation to send a message to UE 105 via service AMF 154. This message may be a supplemental service message, a location protocol (e.g., LPP or NPP) message, or may include both (e.g., a supplemental service message carrying an embedded LPP message). LMF 152 includes in the message a request for periodic or triggered location reporting by UE 105 (including the type of event to be reported) and the type of location measurement or location estimate to be provided by UE 105 for use in location reporting at phase 29. LMF 152 also includes a routing identifier identifying LMF 152 in the Namf_Communication_N1N2MessageTransfer service operation, which is transmitted to UE 105 by AMF 154 (e.g., in a DL NAS transport message carrying a message from LMF 152). Additionally, LMF 152 includes in the message an indication allowing UE 105 to send event reports using EDT. LMF 152 may also include criteria indicating when UE 105 can use EDT and which RAI values ​​(e.g., RAIs for immediate release and / or RAIs for early release) are allowed for UE 105 to include in EDT. Note that LMF 152 can determine UE 105's support for EDT for event reporting by obtaining UE 105's location (e.g., LPP) capabilities before Phase 19, including the RAI values ​​supported by UE 105. It should also be noted that the use of EDT and allowed RAI values ​​can be negotiated at the NAS level during UE 105's registration with 5GCN 150V. UE 105 can only utilize EDT and specific RAI values ​​for location event reporting in Phase 29 if UE 105 is agreed upon during registration and LMF 152 is permitted at Phase 19.

[0135] At phase 20, if the request in phase 19 can be supported, UE 105 returns an acknowledgment to LMF 152 in a positioning protocol (e.g., LPP) and / or supplementary service message, which is transmitted via service AMF 154 and delivered to LMF 152 using the Namf_Communication_N1MessageNotify service operation.

[0136] Execution at stages 21 to 24 Figure 6-2Phases 21 to 24 confirm that event reporting for periodic or triggered positioning is activated in UE 105, and if a UE-available event or initial location estimate is requested at phase 5 or phase 6, return any location estimate obtained at phase 18.

[0137] At phase 25, UE 105 monitors for the occurrence of the triggering event requested in phase 19. This monitoring can be performed when UE 105 is idle and / or when UE 105 is unreachable from 5GCN 150V (e.g., using eDRX or PSM). If a triggering event needs to be detected, UE 105 can also (e.g., periodically) request auxiliary data from LMF 152 to help determine location. When a triggering event is detected, UE 105 proceeds to phase 26.

[0138] In phase 26, UE 105 (e.g., based on any standard received in phase 19) determines whether to use NAS signaling connection or EDT to report the triggering event. If UE 105 is already connected or can only access RAN 112 nodes that do not support EDT, UE 105 determines to use NAS signaling connection.

[0139] At phase 27, if UE 105 determines at phase 26 that it wants to use the NAS signaling connection, then UE 105 executes... Figure 6-2 Phase 27 is used to report detected events and optionally, a NAS signaling connection is used to provide location information to LMF 152. UE105 then skips phases 28 through 37.

[0140] At phase 28, if UE 105 determines at phase 26 that it wants to use EDT, then UE 105 obtains any location measurement or location estimate requested in phase 19, determines a suitable serving cell if it accesses NG-RAN 112, and requests and obtains an RRC signaling connection with the RAN node in RAN 112 (e.g., gNB 110 or ng-eNB 114).

[0141] At phase 29, UE 105 sends a Radio Resource Control (RRC) EDT Request message to the RAN node. The EDT Request message may also be referred to as an RRC Early Data Request message or some other name, and in some implementations, it may be sent by UE 105 using the Common Control Channel (CCCH). The RRC EDT Request message may include an identifier of UE 105 (e.g., a 5G Globally Unique Temporary Identifier (5G-GUTI)) and a NAS transport message containing supplemental service messages and / or UL positioning protocol (e.g., LPP) messages, either of which may include any location measurements or location estimates obtained in phase 28 and may identify the type of reported event. As an example, at phase 29, UE 105 may send a supplemental service message containing an embedded UL positioning protocol message within the NAS transport message, or send only one of the UL positioning protocol message or the supplemental service message. In one embodiment, the UL positioning protocol message (if sent) may be an LPP location information provision message. The NAS transport message also includes a routing identifier received by the UE at phase 19. For example, as defined in 3GPP TS24.501, NAS transmission messages are encrypted and protected for integrity. The RRC EDT request may also include an Access Layer (AS) RAI. The AS RAI may indicate immediate or early release of the RRC signaling connection. For early release, the AS RAI may also indicate whether UE 105 expects to receive messages (e.g., DL positioning protocol messages) from LMF 152 in response. The AS RAI may be referred to as an EDT session indication and in some embodiments may be determined by the RAN node (e.g., if UE 105 does not include the ASRAI in the RRC EDT request message).

[0142] In some embodiments, the NAS transport message sent by UE 105 at phase 29 may include a NAS RAI, which may be similar to or the same as the AS RAI just described (e.g., it may indicate an immediate or early release of the RRC signaling connection, and for an early release, it may indicate whether UE 105 expects to receive a message from LMF 152 in response). In one embodiment, the AS RAI may be limited to indicating only an immediate release of the RRC signaling connection, while the NAS RAI may be limited to indicating only an early release of the RRC signaling connection and whether UE 105 expects to receive a message from LMF 152 in response. UE 105 may include the AS RAI at phase 29 when the RAN node (and possibly AMF 154) needs to take some action based on the AS RAI (e.g., as described below, such as releasing the RRC signaling connection at phase 30). UE 105 may include the NAS RAI at phase 29 when AMF 154, rather than the RAN node, needs to take some action based on the NAS RAI (e.g., as described below, such as sending a UE context release command at phase 36). Typically, at stage 29, UE 105 includes at least one of AS RAI and NAS RAI, but may not include either of these RAIs.

[0143] At phase 30, if an AS RAI is received at phase 29 and the AS RAI indicates immediate release, the RAN node sends an RRC message (e.g., an RRC EDT completion message, which may be referred to as an RRC early data completion message) to UE 105 to immediately release the RRC signaling connection.

[0144] At phase 31, the RAN node sends an N2 Initial UE Message to the serving AMF 154 of UE 105 (e.g., UE 105 identified by the RAN node using 5G-GUTI). The Initial UE Message includes the NAS transport message received at phase 29 and its contents, as well as an indication of the EDT. If an AS RAI is received at phase 29, the indication of the EDT may include that AS RAI.

[0145] At phase 32, AMF 154 performs integrity protection verification and decryption of the NAS transport message, for example, as defined in 3GPP TS 24.501. AMF 154 then invokes the Namf_Communication_N2InfoNotify service operation to LMF 152, as indicated by the routing identifier received in the NAS transport message in phase 31. The service operation includes supplementary service messages and / or UL positioning protocol messages included in the NAS transport message, and may include the NAS RAI and / or AS RAI if received in phase 31. If the NASRAI or AS RAI received at phase 31 indicates immediate release or indicates an early release from which UE 105 does not expect an LMF response, AMF 154 omits support for phases 34 through 35 because AMF 154 does not expect a response from LMF 152 at phase 34.

[0146] At phase 33, if a request to include a location estimate in the event report was made at phase 5 or phase 6, LMF152 uses any location measurements or location estimates included in the supplemental service and / or UL positioning protocol messages received at phase 32 to determine the location estimate of UE 105.

[0147] At stage 34, if the NAS RAI or AS RAI received at stage 32 indicates that UE 105 expects an early release of the response from LMF 152, then LMF 152 invokes the Namf_Communication_N1N2MessageTransfer service operation to AMF 154 to request the transmission of a supplementary service message and / or a DL positioning protocol message (e.g., an LPP message) to UE 105. As an example, at stage 34, LMF 152 may send a supplementary service message containing an embedded DL positioning protocol message, or only one of the DL positioning protocol message or the supplementary service message. In one embodiment, the DL positioning protocol message (if sent) may be an LPP acknowledgment message. The service operation includes the supplementary service message and / or the DL positioning protocol message.

[0148] At phase 35, if AMF 154 receives a supplemental service message and / or DL ​​positioning protocol message for UE 105 from LMF 152 at phase 34, AMF 154 forwards the supplemental service message and / or DL ​​positioning protocol message to RAN 112 (e.g., gNB 110 or ng-eNB 114) in a NAS transport message, which may be conveyed in an NGAP downlink NAS transport message. AMF 154 may also include a termination indication (e.g., in an NGAP downlink NAS transport message) indicating to RAN 112 that RAN 112 may release the signaling connection to UE 105.

[0149] At stage 36, unless AMF 154 receives a NAS RAI or AS RAI indicating immediate release at stage 31, or includes a termination indication at stage 35, AMF 154 sends a UE context release command to RAN 112 to release the RRC signaling connection to UE 105. Stage 36 can be executed after stage 35 if a NASRAI or AS RAI indicating that UE 105 expects a response from LMF 152 is received at step 31. Conversely, step 36 can be executed after stage 32 if stage 35 does not occur and a timeout occurs, or if AMF 154 receives a NAS RAI or ASRAI indicating that UE 105 does not expect a response from LMF 152. Note that AMF 154 can also send any pending MT small data or pending MT SMS messages to UE 105 after stage 31 and before stage 36, in which case AMF 154 can establish a complete signaling connection with UE 105 via RAN 112.

[0150] At phase 37, unless RAN 112 has previously performed phase 30 for immediate release of UE 105, RAN 112 (e.g., gNB 110 or ng-eNB 114 in RAN 112) sends an RRC message (e.g., an RRC EDT completion message or an RRC EDT early data completion message) to UE 105 to release the RRC signaling connection to UE 105, and if phase 35 occurs, any NAS transport messages received at phase 35 and their contents may be included. In some implementations, RAN 112 may use CCCH to send the RRC message for phase 37.

[0151] Execution will be carried out at stages 38 to 41. Figure 6-2 Phases 34 to 37 return an event report (containing an indication of the event that triggered it and a location estimate (if requested)) to the external client 130.

[0152] At phase 42, as in phase 25, UE 105 continues to monitor and detect further triggering events, and triggers phases 26 through 41 each time a triggering event is detected.

[0153] Figure 8-1 and Figure 8-2 Another example of a periodic and triggered positioning procedure (which may be referred to as periodic and triggered 5GC-MT-LR) for roaming UE 105 in communication system 200 is summarized based on a positioning solution based on a combination of AMF and LMF. Figure 8-1 and Figure 8-2 The procedure uses the EDT, which includes the previously described enhancements E1 through E4. Due to its length, it is divided into two graphs, as follows: Figure 8-1 and Figure 8-2 As shown. The periodic and triggered 5GC-MT-LR procedure in communication system 100 for non-roaming UE 105 and / or where external LCS client 130 accesses VGMLC 155V instead of HGMLC 155H may include Figure 8-1 and Figure 8-2 A subset of the programs shown. For example, in Figure 8-1 and Figure 8-2 In the subset of the program shown, H-GMLC 155H and V-GMLC 155V can be combined (e.g., they can be part of the same GMLC 155, which can function as a VGMLC, HGMLC, or both VGMLC and HGMLC), and the following applies to... Figure 8-1 and Figure 8-2 The described stages can be the same, the difference being that stages 4, 7, 19, and 39 may or may not be sent or received. Figure 8-1 and Figure 8-2 The procedure illustrated in the example supports UE 105 mobility within the VPLMN 5GCN 150V and from the 5GCN 150V to an EPC that also belongs to the VPLMN 150V. This procedure uses... Figure 1 and Figure 2 The NLg and NLg* reference points are shown and described. Using NLg* reference points when reporting periodic or triggered location events can enable reduced signaling and processing, which may result in lower latency and better scalability.

[0154] exist Figure 8-1 and Figure 8-2In Phase 1, the external LCS client 130 sends a delayed location request to the HGMLC 155H in the HPLMN 5GCN 150H of the target UE 105 for periodic, triggered, or UE-available location events. The location request provides the UE 105's identifier (e.g., GPSI or SUPI) and the type of location report requested and associated parameters. For periodic location, the request may include the time interval between consecutive location reports, the total number of reports, and location QoS. For triggered reports of area events, the request may include details of the target area, whether the triggered event to be reported is within, entering, or leaving the target area, whether the event report should include UE location estimation, and if so, location QoS and the duration of the report. For triggered reports of motion events, the request may include a threshold linear distance for triggering the location report, whether the event report should include UE location estimation, and if so, location QoS and the duration of the report. For UE-available location events, location QoS may be included. The HGMLC 155H can verify UE privacy requirements.

[0155] Note that in some embodiments, the external LCS client 130 may alternatively be located via NEF 159 (e.g., Figure 1 and Figure 2 (As shown) Access to the network function (NF) or application function (AF) of the HGMLC 155H. In some other embodiments, the external LCS client 130 (e.g., a public safety-enabled PSAP or other client) can access the LRF 147 or LRF 157, such as Figure 1 and Figure 2 As shown, then connect to an HGMLC 155H or VGMLC 155V. In these embodiments, the following applies to... Figure 8-1 and Figure 8-2 The signaling and message transmissions described in phases 1, 8, 20 and 40 (occurring between HGMLC 155H and external LCS client 130) can instead occur between HGMLC 155H (or VGMLC 155V) and external LCS client 130 via NEF 159, LRF 147 or LRF 157.

[0156] exist Figure 8-1 and Figure 8-2 At stage 2, HGMLC 155H can call the Nudm_UE_ContextManagement_Get service operation to the home UDM 156 of the target UE 105, and include the GPSI or SUPI of the UE 105.

[0157] At phase 3, if phase 2 has already occurred, UDM 156 returns the serving AMF 154 address and, optionally, the VGMLC 155V address, along with the current access type of UE 105 (such as NR, LTE, and / or WLAN). UDM 156 can also return the target UE 105's subscription privacy requirements—for example, those not stored in HGMLC 155H and not obtainable from the Privacy Profile Register (PPR) (…). Figure 8-1 and Figure 8-2 (Not shown in the image) In the case of access.

[0158] Note that, as described in 3GPP TS 23.271, the HGMLC 155H can also communicate with the Home Subscriber Server (HSS) of the target UE 105. Figure 8-1 and Figure 8-2 (Not shown in the image) Query the Service Mobility Management Entity (MME) address. Then, for example, if the HSS returns the MME address but the UDM 156 does not return the AMF address, then instead... Figure 8-1 and Figure 8-2 In stages 4 to 39, the EPC-MT-LR procedure for delayed positioning as described in 3GPP TS 23.271 for periodicity and triggering, or the EPC-MT-LR procedure for UE availability events as described in 3GPP TS 23.271, can be executed. Further note that if the HGMLC155H already knows the UE 105's serving AMF 154 address (and possibly the VGMLC 155V address and UE 105 privacy requirements), stages 2 and 3 can be omitted.

[0159] At Phase 4, if no VGMLC 155V address is returned in Phase 3, the HGMLC 155H can use the Network Repository Function (NRF) service in the HPLMN5GCN 150H to select an available VGMLC 155V from the VPLMN5GCN 150V based on the VPLMN 150V address included in the AMF 154 address received in Phase 3, for example, as described in 3GPP TSs 23.501 and 23.502. The HGMLC 155H forwards the location request to the VGMLC 155V (identified by the VGMLC 155V address obtained in Phase 3 or Phase 4) and includes the AMF 154 address, the target UE 105 identity (e.g., SUPI or GPSI), any access type received in Phase 3, and any privacy requirements for the UE 105. HGMLC 155H also includes the contact address of HGMLC 155H (e.g., Uniform Resource Identifier (URI)) and Location Delay Request (LDR) reference number (also known as Related Identifier (ID)), as well as some or all of the parameters received at Phase 1, such as location report type, location service quality (QoS), maximum duration, maximum number of event reports, and requests to include location estimates in location event reports for use in event reports at Phases 19 and 39.

[0160] At Phase 5, VGMLC 155V invokes the Namf_Location_ProvidePositioningInfo Request service operation to forward the location request, which includes all information received in Phase 4, to Service AMF 154. VGMLC 155V may optionally determine LMF 152 and then include the LMF 152 identity in the request sent to AMF 154. VGMLC 155V's determination of LMF 152 may be based on the UE 105's access type and / or on the type of location requested at Phase 1 (e.g., whether it is periodic, triggered, or for a UE availability event).

[0161] At stages 6 to 8, if the AMF 154 supports the type of location request received at stage 5, the AMF 154 returns an acknowledgment to the external LCS client 130 via the VGMLC 155V and HGMLC 155H, indicating that the location request has been accepted. The VGMLC 155V may then optionally release all resources used for the location request.

[0162] Note that, as an optional optimization, VGMLC 155V can be omitted. In this case, instead of executing stages 4 through 7, HGMLC 155H can invoke the Namf_Location_ProvidePositioningInfo Request service operation to forward the location request directly to AMF 154. AMF 154 then directly returns confirmation to HGMLC 155H.

[0163] At phase 9, if UE 105 is currently unreachable (e.g., if UE 105 is using Extended Discontinuous Receive (eDRX) or Power Saving Mode (PSM)), AMF 154 waits for UE 105 to become reachable.

[0164] Note that in the case of mobility from UE 105 to another AMF in 5GCN 150V or to EPC, when UE 105 becomes reachable, the old serving AMF 154 of UE 105 can return an event indication to HGMLC 155H as at stages 18 and 19, and can include the address of the new serving AMF or the new serving MME (if known). If the old AMF 154 does not know the address for the new serving AMF or MME, HGMLC 155H can repeat stages 2 and 3 to query the new AMF or MME address from UDM 156 and HSS. HGMLC 155H can then restart the procedure from stage 3.

[0165] At stage 10, once UE 105 is reachable, AMF 154 executes a network-triggered service request when necessary to move UE 105 to a connected state.

[0166] At phase 11, AMF 154 can notify UE 105 and verify any privacy requests received from HGMLC 155H in phases 4 and 5. If this occurs, AMF 154 can send a supplemental service location notification call to UE 105.

[0167] At stage 12, if UE 105 privacy needs to be verified, UE 105 can notify its user of the location request and can verify the user's permission for the location request. UE 105 can then return a Supplemental Service Location Notification response to AMF 154, indicating whether the user granted or denied permission for the location request when verifying UE 105 privacy. Note that for IoT UE 105 (e.g., since there are typically no users of IoT UEs), stages 11 and 12 may be unnecessary (e.g., may not be performed).

[0168] At phase 13, if VGMLC 155V does not include the LMF 152 identity at phase 5, then AMF 154 determines LMF 152, for example, based on the type of location request and the current UE access type. AMF 154 then invokes the Nlmf_Location_DetermineLocation Request service operation to LMF 152 to initiate a location request for the UE. For periodic or triggered location requests, AMF 154 may include all information received in phase 5, including the HGMLC 155H contact address and LDR reference number. For requests for UE-available location events, the HGMLC 155H contact address and LDR reference number may not be included. AMF 154 may also include certain positioning capabilities of UE 105 in the request sent at phase 13. These positioning capabilities may have already been obtained by AMF 154 from UE 105 during UE 105's registration or re-registration with AMF 154 at the NAS level (e.g., as described in 3GPP TS 24.501). Positioning capabilities may, for example, indicate whether UE 105 supports periodic and / or triggered positioning and / or whether UE 105 supports positioning event reporting using EDT.

[0169] At box 14, LMF 152 can be used as for... Figure 3 The described UE-assisted and UE-based positioning procedures, such as for Figure 4 The described network-assisted location procedures, and / or as for Figure 5 The described procedure for obtaining non-UE-associated network-assisted data to trigger the location of UE 105. During UE-assisted and UE-based location procedures (if executed), LMF 152 may request and obtain UE location capabilities (e.g., it may indicate the types of periodic and triggered location supported by UE 105, the access types supported by UE 105 for event reporting, and whether UE 105 supports EDT). For example, LMF 152 may also use one or more of these procedures to obtain UE 105 location in response to a request for a UE-available location event or when requesting initial location for periodic or triggered UE location. LMF 152 skips stages 15 and 16 only in response to a request for a UE-available location event, or if the UE 105 location capabilities obtained using the UE-assisted and UE-based location procedures or obtained from AMF 154 at stage 13 indicate that UE 105 does not support the requested types of periodic and / or triggered location.

[0170] At phase 15, as part of box 14, and if periodic or triggered location is requested, LMF 152 sends a periodic-triggered location request to UE 105 via serving AMF 154 by invoking the Namf_Communication_N1N2MessageTransfer service operation. The message carries the location request information received from AMF 154 at phase 13, but may omit the HGMLC 155H contact address and LDR reference number when procedural-to-EPC mobility is not supported and when LMF 152 acts as an anchor LMF (as described later herein). The message also indicates whether LMF 152 will act as an anchor LMF (which may also be referred to as a serving LMF), and includes the LMF 152 identifier if LMF 152 will act as an anchor LMF, otherwise includes the default LMF (or "any LMF") identifier. LMF 152 may indicate the permitted access types (e.g., NR, LTE connected to the 5GCN, LTE connected to the EPC, WLAN access connected to the 5GCN) for UE 105 to report events, and may (e.g., based on the UE 105's positioning capabilities and permitted access types obtained as part of Box 14) indicate certain permitted or required location measurements (or location estimates) for each positioning event reported by UE 105. As part of a periodically triggered positioning request NAS transmission from Serving AMF 154 to UE 105, Serving AMF 154 may include a routing identifier identifying LMF 152 in the NAS transmission message.

[0171] As part of phase 15, and when the request at phase 1 is for periodic or triggered positioning, LMF 152 may include a request in the periodic-triggered positioning request that UE 105 be allowed (or required) to send event reports using EDT. LMF 152 may also include criteria indicating when UE 105 may (or should) use EDT and which RAI values ​​(e.g., RAI for immediate release and / or RAI for early release) are allowed (or required) for EDT. For example, the criteria may indicate that UE 105 is allowed or required to use EDT (with immediate or early release) when UE 105 is idle, except after EDT has been used to report continuous event reports for a threshold time period or threshold number of periodic and triggered events (e.g., after which UE 105 may need to use NAS signaling connections).

[0172] Note that LMF 152 can determine UE 105's support for using EDT for event reporting, including the values ​​of RAIs supported by UE 105, by obtaining UE 105's positioning (e.g., LPP and / or NPP) capabilities as part of Box 14 and / or based on UE 105's positioning capabilities provided by AMF 154 at Phase 13. It should also be noted that the use of EDT and permitted RAI values ​​can be negotiated at the NAS level during UE 105's registration with 5GCN 150V. UE 105 can only use EDT and specific RAI values ​​if UE 105 is agreed to and permitted by LMF 152 during registration.

[0173] At stage 16, if UE 105 can support the request in stage 15, then as part of box 14, UE 105 returns an acknowledgment to LMF 152, which is transmitted via service AMF 154 and delivered to LMF 152 using the Namf_Communication_N1MessageNotify service operation.

[0174] Note that the periodic-triggered location request sent at stage 15 and its confirmation at stage 16 can be a location protocol (e.g., LPP or NPP) message, or it can be a message from a separate protocol (e.g., a supplemental service protocol). In the latter case, each message can carry an embedded location protocol message (e.g., an LPP or NPP message) to enable LMF152 to request or allow a specific location measurement from UE 105 at stage 22 and establish an initial location session (e.g., an LPP location session) for subsequent location reporting (e.g., at stages 25 and 29).

[0175] At phase 17, LMF 152 invokes the Nlmf_Location_DetermineLocationResponse service operation to AMF 154 in response to the request at phase 13. For a request for a location event available to the UE, the response may include any UE location obtained at box 14, and LMF 152 then releases all resources. For periodic or triggered location requests, the response may include any location obtained at box 14 and confirmation, according to phases 15 and 16, of whether periodic or triggered location was successfully activated in UE 105; if LMF 152 acts as the anchor LMF, LMF 152 also retains state information and resources for use in subsequent phases.

[0176] At stage 18, AMF 154 invokes the Namf_Location_EventNotify service operation to VGMLC 155V, including any location received at stage 17, and for periodic or triggered location requests, includes confirmation of whether periodic or triggered location requests were successfully activated in the target UE 105. VGMLC 155V can be the same VGMLC 155V used in stages 5 and 6, or it can be a different VGMLC 155V. In the case of a different VGMLC 155V, AMF 154 includes the HGMLC 155H contact address and LDR reference number. AMF 154 can then release all resources used for the location request.

[0177] At stage 19, the VGMLC 155V, using the HGMLC 155H contact address received at stage 18 (for different VGMLC 155Vs) or received and stored at stage 4 (for the same VGMLC 155V), forwards the response received at stage 18 to the HGMLC 155H, including the LDR reference number. The VGMLC 155V can then release all resources used for the location request.

[0178] Note that, as an optional optimization, instead of executing phases 18 and 19, AMF 154 can directly call the Namf_Location_EventNotify service operation to HGMLC155H (e.g., if VGMLC 155V is not used or if VGMLC 155V is no longer supported after phase 7).

[0179] At stage 20, HGMLC 155H forwards the response to external LCS client 130. If the location request at stage 1 is a location event available to the UE, the procedure terminates here and stages 21 to 41 are not executed.

[0180] At phase 21, for successful execution of periodic or triggered location requests in phases 15 and 16, UE 105 monitors for the occurrence of the triggered or periodic event requested in phase 15. When a triggered event is detected and if UE 105 is camped on or connected to (or can otherwise access) an access type permitted by LMF 152 at phase 15, UE 105 proceeds to phase 22. If UE 105 cannot access an permitted access type, UE 105 may skip reporting the triggered event or may report the triggered event at a later time when the permitted access type becomes available, depending on the configuration in UE 105 or the request received from LMF 152 at phase 15.

[0181] At phase 22, UE 105 obtains any location measurements or location estimates requested or permitted at phase 15. UE 105 can also record the type of triggering event detected at phase 21.

[0182] In phase 23, UE 105 (e.g., based on any standards received in phase 15) determines whether to use a NAS signaling connection or EDT to report the triggering event. If UE 105 is already connected or can only access a RAN node that does not support EDT, UE 105 determines to use a NAS signaling connection. Then, when UE 105 determines to use a NAS signaling connection, UE 105 executes phases 24 to 27 and skips phases 28 to 36. When UE 105 determines to use EDT, UE 105 skips phases 24 to 27 and executes phases 28 to 36.

[0183] At phase 24, if UE 105 determines at phase 23 that it wants to use the NAS signaling connection, then UE 105 performs a service request while in an idle state. The description here assumes that the cellular access type for 5GCN150V (e.g., NR or LTE) is used for phases 24 to 27, but similar phases can be applied to non-cellular access for 5GCN 150V (e.g., WLAN access).

[0184] At phase 25, UE 105 sends an event report message to LMF 152, which is transmitted via UE 105's current serving AMF 154 (which may be different from the original serving AMF 154 for box 14) and is delivered to LMF 152 using the Namf_Communication_N1MessageNotify service operation. UE 105 may send the event report message to AMF 154 within a NAS transport message, and then AMF 154 forwards the event report message to LMF 152. The event report may indicate the type of event being reported and include any location measurements or location estimates obtained by UE 105 at phase 22. When anchor LMF 152 is indicated at phase 15, UE 105 includes a routing identifier indicating anchor LMF 152 in the NAS transport message to ensure that the event report is forwarded to anchor LMF 152 by AMF 154. In this case, and unless the anchor LMF changes, as described later for... Figure 9As described, otherwise, LMF 152 for stage 25 is the same as LMF 152 for box 14. When LMF 152 at stage 15 is not the anchor LMF, UE 105 includes a routing identifier indicating the default LMF (or any LMF) in the NAS transport message, and AMF 154 forwards the event report to any suitable LMF 152 (e.g., which may be different from LMF 152 for box 14). In this case, UE 105 also includes the HGMLC155H contact address, LDR reference number, whether to report location estimation, and if so, location QoS in the event report.

[0185] At stage 26, LMF 52 can return confirmation of the event report to UE 105.

[0186] Note that the event reports and acknowledgments sent at stages 25 and 26 can be location protocol messages (e.g., LPP or NPP) or messages from a separate protocol (e.g., a supplemental service protocol). In the latter case, the event report at stage 25 can carry an embedded UL location protocol message (e.g., an LPP or NPP message) to enable UE 105 to include any location measurements or location estimates obtained at stage 22. For example, the UL location protocol message could be an LPP location information message.

[0187] At stage 27, LMF 152 can be used as for Figure 3 The described UE-assisted and UE-based positioning procedures, such as for Figure 4 The described network-assisted location procedures, and / or as for Figure 5 The described procedure for obtaining network-aided data associated with a non-UE is used to perform a UE positioning procedure to obtain a location measurement or location estimate for the UE 105.

[0188] At phase 28, if UE 105 determines in phase 23 that it wants to use EDT, then if it accesses NG-RAN 112, UE 105 determines the appropriate serving cell and requests and obtains an RRC signaling connection with a RAN node in RAN 112 (e.g., gNB 110 or ng-eNB 114). Note that the RRC signaling connection can simply be an association between UE 105 and the RAN node, which allows UE 105 and the RAN node to exchange RRC signaling messages.

[0189] At phase 29, UE 105 sends a Radio Resource Control (RRC) EDT Request message to the RAN node. The EDT Request message may also be referred to as an RRC Early Data Request message or some other name, and in some implementations, it may be sent by UE 105 using the Common Control Channel (CCCH). The RRC EDT Request message includes an identifier for UE 105, such as a 5G Globally Unique Temporary Identifier (5G-GUTI), and a NAS transport message containing an event reporting message. The event reporting message includes any location measurements or location estimates obtained in phase 22 and may identify the type of event being reported. When anchor LMF 152 was indicated at phase 15, UE 105 includes a routing identifier indicating anchor LMF 152 in the NAS transport message to ensure that the event report is forwarded to anchor LMF 152 by AMF 154 at phase 32. In this case, and unless the anchor LMF changes, as described later... Figure 9 As described, otherwise, LMF 152 for stages 28 through 36 is the same as LMF 152 for box 14. When LMF 152 at stage 15 is not the anchor LMF, UE 105 includes a routing identifier in the NAS transport message indicating the default LMF (or any LMF), and AMF 154 forwards the event report at stage 32 to any suitable LMF 152 (e.g., it may be different from or the same as LMF 152 for box 14). For non-anchor LMF 152, UE 105 also includes the HGMLC155H contact address, LDR reference number, whether to report location estimation, and if so, location QoS in the event report. For example, NAS transport messages are encrypted and protected for integrity as defined in 3GPP TS 24.501. RRC EDT requests may also include AS RAI. AS RAI may indicate immediate or early release of the RRC signaling connection. For early releases, AS RAI can also indicate whether UE 105 expects to receive a message from LMF 152 in response. AS RAI may be referred to as EDT Session Indication or some other name, and in some embodiments it may be determined by the RAN node (e.g., if UE 105 does not include AS RAI in the RRC EDT Request message at phase 29).

[0190] In some embodiments, the NAS transport message sent by UE 105 at phase 29 may include a NAS RAI, which may be similar to or the same as the AS RAI just described (e.g., it may indicate an immediate or early release of the RRC signaling connection, and for an early release, it may indicate whether UE 105 expects to receive a message from LMF 152 in response). In one embodiment, the AS RAI may be limited to indicating only an immediate release of the RRC signaling connection, while the NAS RAI may be limited to indicating only an early release of the RRC signaling connection and whether UE 105 expects to receive a message from LMF 152 in response. UE 105 may include the AS RAI at phase 29 when the RAN node (and possibly AMF 154) needs to take some action based on the AS RAI (e.g., as described below, such as releasing the RRC signaling connection at phase 30). UE 105 may include the NAS RAI at phase 29 when AMF 154, rather than the RAN node, needs to take some action based on the NAS RAI (e.g., as described below, such as sending a UE context release command at phase 35). Typically, at stage 29, UE 105 includes at least one of AS RAI and NAS RAI, but may not include either of these RAIs.

[0191] At phase 30, if an AS RAI is received at phase 29 and indicates immediate release, the RAN node sends an RRC EDT completion message (or some other RRC message, such as an RRC early data completion message) to UE105 to immediately release the RRC signaling connection (or release the signaling association between UE105 and the RAN node).

[0192] At phase 31, the RAN node sends an N2 initial UE message to the serving AMF 154 of UE 105 (e.g., identified by 5G-GUTI). The initial UE message includes the NAS transport message received at phase 29 and its contents, as well as an indication of the EDT. If an AS RAI is received at phase 29, the indication of the EDT may include that AS RAI. The AMF 154 for phase 31 may differ from the AMF 154 for box 14.

[0193] At phase 32, AMF 154 performs integrity protection verification and decryption of the NAS transport message, for example, as defined in 3GPP TS 24.501. AMF 154 then invokes the Namf_Communication_N2InfoNotify service operation on the LMF 152 indicated by the routing identifier received in the NAS transport message at phase 31 (e.g., the anchor LMF or any LMF as described for phase 29). The service operation includes the event reporting message received at phase 31, as well as the NAS RAI and / or AS RAI. If the NAS RAI and / or AS RAI received at phase 31 indicates immediate release or UE 105 does not expect an early release response from LMF 152, AMF 154 omits support for phases 33 and 34 because AMF 154 does not expect to receive a response at phase 33.

[0194] At phase 33, if the NAS RAI and / or AS RAI received at phase 31 indicate that UE 105 expects an early release of the response from LMF 152, then LMF 152 may invoke the Namf_Communication_N1N2MessageTransfer service operation to AMF 154 to request the transmission of an event report confirmation message to UE 105. The service operation includes the event report confirmation message.

[0195] Note that the event reports sent at stages 29, 31, and 32, and the report acknowledgments sent at stage 33, can be location protocol messages (e.g., LPP or NPP) or messages from a separate protocol (e.g., a supplemental service protocol). In the latter case, the event reports sent at stages 29, 31, and 32 can carry embedded UL location protocol messages (e.g., LPP or NPP messages) to enable UE 105 to include any location measurements or location estimates obtained at stage 22. For example, a location protocol message sent without a supplemental service protocol message or embedded in a supplemental service protocol message could be an LPP location information message. The event report acknowledgments can be LPP acknowledgments, supplemental service protocol messages, or LPP acknowledgments embedded in supplemental service protocol messages.

[0196] At stage 34, if AMF 154 receives an event report acknowledgment from LMF 152 of UE 105 at stage 33, AMF 154 forwards the event report acknowledgment to RAN 112 (e.g., gNB 110 or ng-eNB 114) in a NAS transport message, which may be conveyed in an NGAP downlink NAS transport message. AMF 154 may also include a termination indication (e.g., in an NGAP downlink NAS transport message) indicating to RAN 112 that RAN 112 may release the signaling connection to UE 105.

[0197] At stage 35, unless AMF 154 receives a NAS RAI and / or ASRAI indicating immediate release at stage 31, or includes a termination indication at stage 34, AMF 154 sends a UE context release command to RAN 112 to release the RRC signaling connection to UE 105. Stage 35 is executed after stage 34 if a NAS RAI or AS RAI indicating that UE 105 expects a response from LMF 152 is received at step 31. Conversely, step 35 is executed after stage 32 if a timeout occurs in the case where stage 34 does not occur, or if AMF 154 receives a NAS RAI or AS RAI indicating that UE 105 does not expect a response from LMF 152. Note that AMF 154 can also send any pending MT small data or pending MT SMS messages to UE 105 after phase 31 and before phase 35. In this case, AMF 154 can establish a full signaling connection with UE 105 via RAN 112.

[0198] At phase 36, unless RAN 112 has previously performed phase 30 for immediate release of UE 105, RAN 112 (e.g., gNB 110 or ng-eNB 114 in RAN 112) sends an RRC EDT completion message (or some other RRC message, such as an RRC Early Data Completion message) to UE 105 to release the RRC signaling connection to UE 105, and if phase 34 occurs, any NAS transport messages received at phase 34 may be included. In some implementations, RAN 112 may use CCCH to send the RRC EDT completion message at phase 36.

[0199] At phase 37, if the event report requires location estimation, LMF 152 uses the location measurements and / or location estimates obtained at phase 25 and / or phase 27 when UE 105 sends the event report using the NAS signaling connection, or at phase 32 when UE 105 sends the event report using the EDT, to determine the location of UE 105.

[0200] At phase 38, LMF 152 selects VGMLC 155V (which may be different from the VGMLC 155V used in phases 4 to 8 and phases 18 to 20) and invokes the Nlmf_EventNotify service operation to VGMLC 155V with the indication of the reported event type, the H-GMLC 155H contact address and LDR reference number, and any location estimates obtained at phase 37.

[0201] Note that at phase 38, the LMF 152 can select a VGMLC 155V in one of three different ways. In the first way, the LMF 152 can be configured with the addresses of one or more VGMLC 155s in the VPLMN 5GCN 150V and can randomly select a specific VGMLC 155V based on the current or expected load of the VGMLC 155 in the VPLMN 5GCN 150V, or based on the access type of the UE 105 and / or the type of reported location events. In the second way, the LMF 152 can use the NRF service in the VPLMN 5GCN 150V to select a VGMLC 155V, as described in 3GPP TS23.501 and 3GPP TS23.502. In the third approach, if LMF 152 is an anchor LMF, then LMF 152 may have already received the original VGMLC 155V address from AMF 154 at stage 13, and may have already stored the address. In this case, LMF 152 can select the original VGMLC 155V.

[0202] At stage 39, the VGMLC 155V will forward the information received in stage 38 to the HGMLC155H.

[0203] Note that, as an optional optimization, instead of execution phases 38 and 39, LMF 152 can directly call the Nlmf_EventNotify service operation to HGMLC155H.

[0204] At phase 40, the HGMLC 155H uses the LDR reference number received in phase 39 to identify the periodic and triggered location request received in phase 1, and then sends the reported event type and any location estimate to the external LCS client 130. The HGMLC 155H can also verify the UE 105 privacy requirements and then report the event and any location to the external LCS client 130.

[0205] At phase 41, UE 105 continues to monitor for further periodic or triggered events, and triggers phases 22 through 40 each time a triggered event is detected.

[0206] Note that if target UE 105 is unable to access 5GCN 150V in the VPLMN for repeated phases 22 to 40, but is permitted and can access LTE connected to the EPC for the same VPLMN 150V, then UE 105 can trigger 3GPP TS 23.271. Figure 9 In stages 13 to 24 of .19.1-1, location events are reported using delayed EPC-MT-LR event reporting for periodic and triggered location as described in 3GPP TS 23.271. In this case, when in 3GPP TS 23.271... Figure 9 When sending a Mobile Origin Location Request (MO-LR) call message at stage 14 of .19.1-1, UE 105 may include the HGMLC 155H contact address and LDR reference number, which allows the serving MME of UE 105 to use the 3GPP TS 23.271 Figure 9 Phases 19 to 21 of .19.1-1 report the location event to the HGMLC 155H. This is typically used in 3GPP TS 23.271. Figure 9 The E-SMLC in the program .1.19.1-1 will be with Figure 8-1 and Figure 8-2 The LMF 152 in box 14 is different and separate, but the VPLMN 150V can use proprietary procedures to enable the E-SMLC to access (e.g., read and / or modify) the status information of UE 105 in the LMF 152 (e.g., using the HGMLC 155H contact address and LDR reference number as keys to identify the status information of UE 105), which may help the E-SMLC and / or LMF 152 to locate UE 105 at a later time.

[0207] Figure 9 The following is an illustration of what is used when the anchor LMF 152 is used. Figure 8-1 and Figure 8-2The procedure shown is one in which the mobility of the target UE 105 causes a change in the serving AMF (and therefore the original anchor LMF 152 becomes unreachable or unsuitable). For example, the anchor LMF 152 may be located further away from AMF 154, resulting in higher resource utilization for signaling from AMF 154 to LMF 152, or LMF 152 may not have sufficient information for the current access network (e.g., serving and neighboring gNB 110, ng-eNB 114, and / or WLAN) to prevent UE 105 from achieving accurate and reliable positioning. In this case, the anchor LMF 152 may need to be changed. Figure 9 This illustrates the method used when UE 105 sends an event report (such as in...). Figure 8-1 and Figure 8-2 At stage 25 or stages 29 to 32, the current anchor LMF of UE 105 is Figure 9 The program that implements the change of anchor LMF 152 (when LMF1 152A is in the middle).

[0208] exist Figure 9 In stage 1, as for Figure 8-1 and Figure 8-2 In phase 24, if a NAS signaling connection is used, UE 105 executes a UE-triggered service request if necessary.

[0209] exist Figure 9 In Phase 2, UE 105 sends a NAS transport message containing an event report message to serving AMF 154. The NAS transport message includes a routing identifier indicating LMF1 152A. When UE 105 uses NAS signaling connections, Phase 2 can correspond to... Figure 8-1 and Figure 8-2 Phase 25, or when UE 105 uses EDT, Phase 2 can correspond to Figure 8-1 and Figure 8-2 Phases 29 to 31. When phase 2 corresponds to Figure 8-1 and Figure 8-2 During phases 29 to 31 of the EDT, UE 105 may send ASRAI together with the NAS transmission message, and / or the NAS transmission message may include NAS RAI as... Figure 9 As part of Phase 2, they are all forwarded by RAN 112 to AMF 154 (e.g., for...). Figure 8-1 and Figure 8-2 (As described in stages 29 to 31).

[0210] exist Figure 9At stage 3, AMF 154 can determine that LMF1 152A is unreachable or unsuitable for processing the event report. AMF 154 can then identify another anchor LMF: LMF2 152B. Stage 3 is optional and is not always executed.

[0211] At phase 4, AMF 154 invokes the Namf_Communication_N1MessageNotify service operation to LMF1 152A. The service operation includes the event report received in phase 2, NASSRAI and / or AS RAI received in phase 2 in the case of EDT, and, if AMF 154 determines LMF2 152B at phase 3, the identifier (ID) of LMF2 152B.

[0212] At stage 5, if the ID of LMF2 152B is not present at stage 4, then LMF1 152A can determine that LMF1 152A is not suitable for processing the event report (e.g., because LMF1 152A is not configured with information about the current access type or current access node for UE 105D). LMF1 152A can then determine another anchor LMF: LMF2 152B. Stage 5 may not be executed if stage 3 is performed, but it is likely to be executed in other cases (when the anchor LMF changes).

[0213] At stage 6, based on the identification of LMF2 152B received at stage 4 or based on the determination of LMF2 152B at stage 5, LMF1 152A invokes the Nlmf_LocationContextTransfer Request service operation to LMF2 152B to transmit the event report and any NAS RAI and / or AS RAI received at stage 4, as well as the current location context of UE 105, and indicates the change of anchor LMF. The location context of UE 105 may include the original (i) based on the location requests from LMF1 152A for periodic or triggered location requests for UE 105. Figure 8-1 and Figure 8-2 The program receives data from VGMLC 155V or HGMLC155H, or (ii) according to... Figure 9 The location context may include all information received by the program from an earlier anchor LMF. The location context may also include the current status of the event reports of UE 105 (e.g., the number of event reports received from UE 105 so far and / or the duration of the event reports so far), and may include location-related information of UE 105, such as previous location estimates or previous location measurements.

[0214] At phase 7, LMF2 152B sends an acknowledgment to LMF1 152A to confirm the delivery of the anchor LMF for UE 105. LMF1 152A then releases all resources used for the positioning of UE 105.

[0215] At phase 8, unless an event report is sent using EDT at phase 2, where the NARAI and / or AS RAI indications received at phase 6 do not allow a response from LMF2 152B, LMF2 152B invokes the Namf_Communication_N1N2MessageTransfer service operation to AMF 154 to request the transmission of an event report acknowledgment message to UE105. The event report acknowledgment may indicate a change in the anchor LMF and may include the LMF2 152B identifier or identifier. When UE105 uses NAS signaling connections, phase 8 may correspond to... Figure 8-1 and Figure 8-2 In stage 26, or when UE105 uses EDT, stage 8 can correspond to... Figure 8-1 and Figure 8-2 Stage 33.

[0216] Note that in VPLMN 5GCN 150V, where anchor LMF 152 may change, anchor LMF 152 may preferably not request or allow UE 105 to send event reports using EDT (which does not allow responses). This avoids... Figure 9 At stage 8, the new LMF2 152B identity cannot be returned to UE 105.

[0217] At phase 9, AMF 154 forwards the event report acknowledgment to UE105 in the NAS transport message. AMF 154 can also include a routing identifier indicating LMF2 152B in the NAS transport message, which avoids the need for LMF2 152B to include its identifier in the event report acknowledgment at phase 8. When UE105 uses NAS signaling connectivity, phase 9 can correspond to... Figure 8-1 and Figure 8-2 Phase 26 is part of the process, or when UE 105 uses EDT, Phase 9 may correspond to... Figure 8-1 and Figure 8-2 Stages 34 to 36.

[0218] At phase 10, when UE 105 uses NAS signaling connection, LMF2 152B can perform actions such as... Figure 8-1 and Figure 8-2 The UE positioning procedure at stage 27 in the process is used to obtain the location measurement or location estimate of UE 105.

[0219] At stage 11, if the event report requires location estimation, then LMF2 152B is as follows: Figure 8-1 and Figure 8-2 The position of UE 105 is determined as shown in stage 37. Then, Figure 8-1 and Figure 8-2 The remaining programs can be found in Figure 8-1 and Figure 8-2 Phase 38 continues, in which LMF2 152B retains state information to enable subsequent event reporting from UE 105.

[0220] Note that in Figure 9 In the variant of the program shown, AMF 154 can always be executed. Figure 9 Phase 3 of the process determines LMF2 152B when a change to anchor LMF 152 is required. In this variant, AMF 154 can... Figure 8-1 and Figure 8-2 In Phase 4, the Namf_Communication_N1MessageNotify service operation is invoked to LMF2 152B, not LMF1 152A. This service operation includes the event report received in Phase 2, the NASSRAI and / or AS RAI received in Phase 2 in the EDT case, and the identifier (ID) of LMF1 152A. LMF2 152B can then send a request for the location context of UE105 to LMF1 152A, and LMF1 152A can use the [resource name / feature] to request the location context of UE105. Figure 9 The program returns to the location context defined in stage 6 of the original program. Then, variations of the program can be made based on the above... Figure 9 The original program described continues from stages 8 to 11.

[0221] Figure 10 A process flow 1000 is shown illustrating a method for supporting periodic and triggered positioning of a user equipment (UE) (such as UE 105). As shown, at block 1002, the UE receives a request for periodic or triggered positioning from a positioning server such as an LMF (e.g., LMF 152), for example, as in... Figure 7 Phase 19 or Figure 8-1 and Figure 8-2 In stage 15, at box 1004, the UE sends a response to the location server confirming periodic or triggered location, for example, as in... Figure 7 Phase 20 or Figure 8-1 and Figure 8-2In stage 16, the request received in box 1002 and the response sent in box 1004 can be a location protocol (e.g., LPP or NPP) message, a supplemental service protocol message, or each can include two types of messages. In box 1006, the UE detects a periodic or triggered event, such as... Figure 7 Phase 25 or Figure 8-1 and Figure 8-2 In stage 21, within block 1008, the UE obtains event information, which may include at least one of location measurement, location estimation, the type of detected triggering event, or a combination thereof, for example, as in... Figure 7 Phase 28 or Figure 8-1 and Figure 8-2 In phase 22, within box 1010, the UE obtains a signaling connection to a radio access network (RAN) node, such as a new radio (NR) node B (e.g., gNB 110) or a next-generation evolution node B (e.g., ng-eNB 114), wherein this signaling connection initially does not include a signaling connection to a core network (CN) node such as the serving AMF (e.g., AMF 154), for example, as in Figure 7 Phase 28 or Figure 8-1 and Figure 8-2 In stage 28, at block 1012, the UE sends a first message to the RAN node. This first message contains a Non-Access Stratum (NAS) transport message, which includes a routing identifier identifying the location server and an event report message containing information about the event, for example, as in... Figure 7 Phase 29 or Figure 8-1 and Figure 8-2 At stage 29. Then, the RAN node forwards the NAS transmission message to the CN node (e.g., as shown in section 29). Figure 7 Phase 31 or Figure 8-1 and Figure 8-2 (At stage 31), and the CN node forwards the event report message to the location server (e.g., ...). Figure 7 Phase 32 or Figure 8-1 and Figure 8-2 (At stage 32 in the middle). At box 1014, the UE receives a second message from the RAN node, wherein the second message releases the signaling connection to the RAN node, for example, as in Figure 7 Stage 30 or 37 or Figure 8-1 and Figure 8-2 In stage 30 or 36. In one implementation, the first message may be a Radio Resource Control Early Data Transmission (EDT) request or an RRC Early Data Request, and the second message may be an RRC EDT completion message or an RRC Early Data Completion message.

[0222] In one implementation, the method further includes a release assist indication (RAI) in the first message sent at block 1012, wherein the RAN node forwards the NAS transmission message and the RAI to the CN node, and wherein the CN node forwards the event report message and the RAI to the location server.

[0223] The event reporting message sent in box 1012 may include a location protocol (e.g., LPP or NPP) message, a supplemental service protocol message, or both.

[0224] The RAI may include a request for immediate connection release or a request for early connection release, and a request for early connection release may include an indication that the UE does not expect a response message from the location server, or an indication that the UE expects a response message from the location server. The RAI may also, or alternatively, include an indication of early data transmission. The RAI may include an Access Stratum (AS) RAI or a NAS RAI, wherein the AS RAI is included in the first message but not in the NAS transmission message, and wherein the NAS RAI is included in the NAS transmission message. The RAI may include a request for immediate connection release, in which case the RAN node may send a second message to the UE in response to the request for immediate connection release, for example, as in... Figure 7 Phase 30 or Figure 8-1 and Figure 8-2 At stage 30. The RAI may include a request for early connection release, and this request may include an indication that the UE does not expect a response message from the location server. In this case, the RAN node may send this second message to the UE in response to receiving the connection release request from the CN node, for example, as in... Figure 7 Stages 36 to 37 or Figure 8-1 and Figure 8-2 Stages 35 to 36.

[0225] RAI may include a request for early connection release, and the request for early connection release may include an indication that the UE expects a response message from the positioning server. In this case, the process may further include the UE receiving a third request from the RAN node, wherein the third message contains a NAS transmission message, the NAS transmission message containing an event report confirmation message, wherein the event report confirmation message is sent by the positioning server in response to the event report message, for example, as in... Figure 7 Phase 37 or Figure 8-1 and Figure 8-2At stage 36. For example, the UE may receive the second message after the third message (e.g., if the third message is an RRC DL information transmission message), or the second message may include the third message. The event report confirmation message may include confirmation of the event report message. The request for the periodic or triggered location may include an indication that the UE may report the detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both, for example, as in Figure 7 Phase 19 or Figure 8-1 and Figure 8-2 There are 15 stages in the process.

[0226] The method for process flow 1000 may also include the UE receiving a request for the UE's positioning capabilities (e.g., an LPP request) from the positioning server, such as... Figure 8-1 and Figure 8-2 In box 14. Then, the UE may send a response (e.g., an LPP response) to the positioning server including the UE's positioning capabilities, wherein the positioning capabilities include an indication that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both, and wherein the positioning server may, in response to receiving the indication that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both, include an indication that the UE may use a request for early connection release or a request for immediate connection release, or both, to report detected periodic or triggered events.

[0227] The method for process flow 1000 may further include: the request for periodic or triggered positioning received at block 1002 includes criteria for reporting the detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both. The criteria may include at least one of the following: the UE uses a request for immediate connection release when the UE is idle and does not expect a response from the positioning server; the UE uses a request for early connection release when the UE is idle and expects a response from the positioning server; in other cases, or after a threshold time period or a threshold number of event reports have been used for either the request for early connection release or the request for immediate connection release (or both), the UE uses a non-access stratum (NAS) signaling connection; or a combination thereof.

[0228] Figure 11A process flow 1100 is shown illustrating a method for supporting periodic and triggered positioning of a user equipment (UE) (such as UE 105) performed by a positioning server (such as an LMF (e.g., LMF 152)). As shown, at block 1102, the positioning server sends a request to the UE for periodic or triggered positioning, wherein the request includes an indication that the UE may (or should) report detected periodic or triggered events using a request for early connection release, a request for immediate connection release, or both, for example, as in Figure 7 Phase 19 or Figure 8-1 and Figure 8-2 In stage 15, at box 1104, the location server receives a response from the UE, which confirms the periodic or triggered location, for example, as in... Figure 7 Phase 20 or Figure 8-1 and Figure 8-2 In stage 16 of the protocol, the request sent at box 1102 and the response received at box 1104 can be a location protocol (e.g., LPP or NPP) message, a supplemental service protocol message, or each can include two types of messages.

[0229] At box 1106, the location server receives an event reporting message and a release assist indication (RAI) sent by the UE to the core network (CN) node (such as the AMF (e.g., AMF 154)). The RAI includes a request for immediate connection release or a request for early connection release. The request for early connection release includes an indication that the UE does not expect a response message from the location server, or an indication that the UE expects a response message from the location server. The event reporting message contains an event message obtained by the UE after detecting a periodic or triggered event, and the event information includes at least one of location measurement, location estimation, the type of the detected triggering event, or a combination thereof. For example, box 1106 may correspond to... Figure 7 Phase 32 or Figure 8-1 and Figure 8-2 Phase 32.

[0230] At box 1108, the location server uses event information to determine the UE's location information, for example, as in Figure 7 Phase 33 or Figure 8-1 and Figure 8-2 In stage 37, at box 1110, the location server sends the UE's location information to another entity (such as a GMLC (e.g., GMLC 155V or GMLC 155H) or an LCS client (e.g., LCS client 130)). Figure 7 Stage 38 or 40 or Figure 8-1 and Figure 8-2 At stage 38. For example, location information may include a location estimate for the UE, the type of detected triggering event, or both.

[0231] The event report message received in box 1106 may include a location protocol (e.g., LPP or NPP) message, a supplemental service protocol message, or both.

[0232] The RAI received at block 1106 may include a request for immediate connection release or a request for early connection release. A request for early connection release may include an indication that the UE does not expect a response message from the location server. In this case, the procedure may further include avoiding sending a response message to the UE. The RAI may include a request for early connection release, and a request for early connection release may include an indication that the UE expects a response message from the location server. In this case, the procedure further includes sending an event report confirmation message to the CN node in response to the event report message, wherein the event report confirmation message is forwarded to the UE by the CN node. The event report confirmation message may include acknowledgment of the event report message.

[0233] The process may also include sending a request to the UE for the UE's positioning capabilities (e.g., an LPP request), for example, as... Figure 8-1 and Figure 8-2 In box 14. The positioning server can then receive from the UE a response (e.g., an LPP response) including the UE's positioning capabilities, wherein the positioning capabilities include an indication that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both. Then, in response to receiving the indication that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both, the positioning server can include in box 1102 an indication that the UE can use a request for early connection release or a request for immediate connection release, or both, to report detected periodic or triggered events.

[0234] The process may further include: the location server including a criterion in the location request for periodic or triggered location at box 1102, wherein the criterion includes a criterion for reporting detected periodic or triggered events using a request for early connection release, a request for immediate connection release, or both. The criterion may include at least one of the following: the UE uses a request for immediate connection release when the UE is idle and does not expect a response from the location server; the UE uses a request for early connection release when the UE is idle and expects a response from the location server; the UE uses a non-access stratum (NAS) signaling connection in other cases or after a threshold time period or a threshold number of event reports have been used for the request for early connection release or the request for immediate connection release (or both); or a combination thereof.

[0235] Figure 12 A process flow 1200 is shown illustrating a method for supporting periodic and triggered positioning of a user equipment (UE) (such as UE 105) performed by a core network (CN) node (such as an AMF (e.g., AMF 154)). As shown, at block 1202, the CN node receives a request for periodic or triggered positioning from a positioning server (such as an LMF (e.g., LMF 152)) and (e.g., in a NAS transmission message) sends the request for such periodic or triggered positioning to the UE, wherein the request includes an indication that the UE can report the detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both. For example, block 1202 may correspond to... Figure 7 Part of stage 19 or Figure 8-1 and Figure 8-2 This is part of phase 15. At box 1204, the CN node (e.g., in a NAS transmission message) receives a response from the UE and sends that response to the location server, where the response confirms the periodic or triggered location. For example, box 1204 could correspond to... Figure 7 Part of stage 20 or Figure 8-1 and Figure 8-2 This is part of phase 16. The request received at box 1202 and the response received at box 1204 may be a location protocol (e.g., LPP or NPP) message, a supplemental service protocol message, or may each include both types of messages.

[0236] In box 1206, the CN node receives, for example, a Non-Access Stratum (NAS) transport message and a Release Assist Indication (RAI) sent by the UE to the RAN node from a Radio Access Network (RAN) node (such as a New Radio (NR) Node B (e.g., gNB 110) or a Next Generation Evolution Node B (e.g., ng-eNB 114)). Figure 7 Phase 31 or Figure 8-1 and Figure 8-2 At stage 31. Here, the RAI may include a request for immediate connection release or a request for early connection release. A request for early connection release may include an indication that the UE does not expect a response message from the location server, or an indication that the UE expects a response message from the location server. The NAS transmission message may include a routing identifier identifying the location server and an event report message containing event information obtained by the UE after detecting a periodic or triggered event. For example, the event information may include at least one of location measurement, location estimation, the type of detected triggered event, or a combination thereof. At block 1208, the CN node sends the event report message and the RAI to the location server, for example, as in... Figure 7 Phase 32 or Figure 8-1 and Figure 8-2 There are 32 stages in the middle.

[0237] Event reporting messages may include location protocol messages (e.g., LPP or NPP), supplemental service protocol messages, or both.

[0238] In one embodiment of a method applicable to combining AMF and LMF positioning solutions, the CN node also receives a second request for periodic or triggered positioning from another entity (e.g., a gateway mobile positioning center), for example, as in... Figure 8-1 and Figure 8-2 In stage 5 of the process. Then, the CN node can send a second request to the location server for periodic or triggered location (e.g., as in...). Figure 8-1 and Figure 8-2 In stage 13), receiving a request for periodic or triggered location from the location server at box 1202 is in response to sending a second request for periodic or triggered location to the location server.

[0239] The RAI received at box 1206 may include a request for immediate connection release or a request for early connection release. A request for early connection release may include an indication that the UE does not expect a response message from the location server, in which case the CN node may not receive a response message for the UE from the location server. The RAI may include a request for early connection release, and a request for early connection release may include an indication that the UE expects a response message from the location server. In this case, the method may further include: receiving an event report acknowledgment message from the location server in response to an event report message (e.g., as in...). Figure 7 Phase 34 or Figure 8-1 and Figure 8-2(at stage 33); and sending a NAS transmission message to the UE containing the event report confirmation message (e.g., as in...). Figure 7 Stage 35 or Figure 8-1 and Figure 8-2 (Section 34 in the middle). The event report confirmation message may include confirmation of the event report message.

[0240] The method may further include: the CN node receiving the UE's positioning capabilities from the UE during the UE's registration with the CN node, and including the UE's positioning capabilities in a second request for periodic or triggered positioning sent to the positioning server (e.g., as in...). Figure 8-1 and Figure 8-2 (At stage 13 in the middle). For example, the positioning capability may include an indication that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both. Then, in response to receiving the indication that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both, the positioning server may include at box 1202 an indication that the UE can use a request for early connection release or a request for immediate connection release, or both, to report detected periodic or triggered events.

[0241] The method may further include: the request for periodic or triggered positioning received at block 1202 includes criteria for reporting the detected periodic or triggered event using a request for early connection release, or a request for immediate connection release, or both. The criteria may include at least one of the following: the UE uses a request for immediate connection release when the UE is idle and does not expect a response from the positioning server; the UE uses a request for early connection release when the UE is idle and expects a response from the positioning server; in other cases, or after a threshold time period or a threshold number of event reports have been used for either the request for early connection release or the request for immediate connection release (or both), the UE uses a non-access stratum (NAS) signaling connection; or a combination thereof.

[0242] Figure 13A process flow 1300 is shown illustrating a method for supporting periodic and triggered positioning of a user equipment (UE) (such as UE 105) performed by a radio access network (RAN) node (such as a new radio (NR) node B (e.g., gNB 110) or a next-generation evolution node B (e.g., ng-eNB 114)). As shown, at block 1302, the RAN node receives a request for periodic or triggered positioning (e.g., included in a NAS transport message) from a positioning server (such as an LMF (e.g., LMF 152)) and sends the request for periodic or triggered positioning to the UE. Here, the request includes an indication that the UE can report the detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both. For example, block 1302 may correspond to... Figure 7 Part of stage 19 or Figure 8-1 and Figure 8-2 This is part of phase 15. At box 1304, the RAN node receives a response from the UE (e.g., included in a NAS transport message) and sends that response to the positioning server, where the response confirms the periodic or triggered positioning, for example, as in... Figure 7 Phase 20 or Figure 8-1 and Figure 8-2 In stage 16 of the protocol, the request received at box 1302 and the response received at box 1304 can be a location protocol (e.g., LPP or NPP) message, a supplemental service protocol message, or each can include two types of messages.

[0243] At box 1306, the RAN node receives a request from the UE for a signaling connection, wherein the signaling connection initially does not include a signaling connection to a core network (CN) node (such as an AMF (e.g., AMF 154)), for example, as in Figure 7 Phase 28 or Figure 8-1 and Figure 8-2 In stage 28, at box 1308, the RAN node provides signaling connectivity to the UE, for example, as in... Figure 7 Phase 28 or Figure 8-1 and Figure 8-2At stage 28. In block 1310, the RAN node receives a first message from the UE via the signaling connection, wherein the first message includes a Release Assistance Indication (RAI), and wherein the first message also includes a Non-Access Stratum (NAS) transport message, which includes (i) a routing identifier identifying the location server and (ii) an event report message, which includes an event message obtained by the UE after a periodic or triggered event is detected, and wherein the event information includes at least one of location measurement, location estimation, the type of the detected triggering event, or a combination thereof. For example, block 1310 may correspond to Figure 7 Phase 29 or Figure 8-1 and Figure 8-2 Phase 29.

[0244] At box 1312, the RAN node sends a NAS transport message and a RAI (e.g., ...) to the CN node. Figure 7 Phase 31 or Figure 8-1 and Figure 8-2 (At stage 31), and the CN node forwards the event report message and RAI to the location server (e.g., ...). Figure 7 Phase 32 or Figure 8-1 and Figure 8-2 (At stage 32 in the middle). At box 1314, the RAN node sends a second message to the UE, in which the second message releases the signaling connection to the RAN node, for example, as in... Figure 7 Stage 30 or 37 or Figure 8-1 and Figure 8-2 In stage 30 or 36, the first message may be an Early Radio Resource Control (EDT) data transmission request or an Early Radio Resource Control (RRC) data transmission request, and the second message may be an RRC EDT completion message or an RRC data transmission completion message.

[0245] Event reporting messages may include location protocol messages (e.g., LPP or NPP), supplemental service protocol messages, or both.

[0246] The RAI may include a request for immediate connection release or a request for early connection release, and a request for early connection release may include an indication that the UE does not expect a response message from the location server or an indication that the UE expects a response message from the location server. The RAI may also, or alternatively, include an indication for early data transmission. The RAI may include an Access Stratum (AS) RAI or a NAS RAI, wherein the AS RAI is included in the first message but not in the NAS transmission message, and wherein the NAS RAI is included in the NAS transmission message. The RAI may include a request for immediate connection release, in which case the RAN node may send a second message to the UE in response to the request for immediate connection release, for example, as in... Figure 7 Phase 30 or Figure 8-1 and Figure 8-2 At stage 30, the RAI may include a request for early connection release, and this request may include an indication that the UE does not expect a response message from the location server. In this case, the RAN node may send a second message to the UE in response to receiving the connection release request from the CN node, for example, as in... Figure 7 Stages 36 and 37 or Figure 8-1 and Figure 8-2 Stages 35 and 36.

[0247] In one embodiment, the RAI may include a request for early connection release, and the request for early connection release may include an indication that the UE expects a response message from the location server. In this embodiment, the process may further include receiving a third message from the CN node, wherein the third message contains a NAS transmission message, the NAS transmission message containing an event report confirmation message, and wherein the event report confirmation message is sent by the location server to the CN node in response to the event report message, for example, as in... Figure 7 Stage 35 or Figure 8-1 and Figure 8-2 At stage 34. The process may then further include sending a fourth message to the UE, wherein the fourth message contains the NAS transmission message, for example, as in Figure 7 Phase 37 or Figure 8-1 and Figure 8-2 At stage 36. The RAN node can send the second message after the fourth message, or the second message can include the fourth message (e.g., as in...). Figure 7 Phase 37 or Figure 8-1 and Figure 8-2 (36 stages in the process). Event report confirmation can include acknowledgment of the event report message.

[0248] The method may further include the RAN node receiving a request for the UE's positioning capability from the positioning server via the CN node, and sending the request for positioning capability to the UE, for example, as for Figure 8-1 and Figure 8-2 As described in box 14. The RAN node can then receive a response from the UE including the UE's positioning capabilities and can send that response to the positioning server via the CN node (e.g., as for...). Figure 8-1 and Figure 8-2(as described in box 8), wherein the positioning capability includes the following indication: the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both, wherein the positioning server, in response to receiving the indication that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both, includes the following indication: the UE can use a request for early connection release or a request for immediate connection release, or both, to report detected periodic or triggered events.

[0249] The method may further include: the request for periodic or triggered positioning received at block 1302 includes criteria for reporting the detected periodic or triggered event using a request for early connection release or a request for immediate connection release, or both. The criteria may include at least one of the following: the UE uses a request for immediate connection release when the UE is idle and does not expect a response from the positioning server; the UE uses a request for early connection release when the UE is idle and expects a response from the positioning server; in other cases, or after a threshold time period or a threshold number of event reports have been used for the request for early connection release or the request for immediate connection release (or both), the UE uses a non-access stratum (NAS) signaling connection; or a combination thereof.

[0250] Figure 14 It shows things like Figures 1 to 9 The diagram illustrates an example hardware implementation of the location server 1400 for the LMF 152 shown. The location server 1400 may be part of, for example, a wireless network (such as a 5G core network (5GCN)). The location server 1400 includes, for example, hardware components such as an external interface 1402, which may be a wired or wireless interface capable of connecting to a GMLC (such as GMLC 155, VGMLC 155V, or HGMLC 155H) and an AMF (such as AMF 154). The location server 1400 includes one or more processors 1404 and a memory 1410, which may be coupled to a bus 1406. The memory 1410 may store data and may contain executable code or software (or firmware) instructions that, when executed by the one or more processors 1404, cause the one or more processors 1404 to act as a dedicated computer programmed to execute the programs and techniques disclosed herein.

[0251] like Figure 14 As shown, the memory 1410 includes one or more components or modules, which, when implemented by one or more processors 1404, are implemented, for example, according to Figures 2 to 9 and Figure 11The described method. Although components or modules are shown as software in memory 1410 that can be executed by one or more processors 1404, it should be understood that components or modules may be dedicated hardware in or outside of processor 1404. As shown, memory 1410 may include location information request unit 1414, which enables one or more processors 1404 to: communicate via external interface 1402 with at least one other entity, such as a UE (e.g., UE 105) that can be accessed via a CN node (e.g., AMF 154); send a request to the UE for periodic or triggered location, wherein the request includes an indication that the UE may report the detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both; and receive a response from the UE confirming the periodic or triggered location. The location information request unit 1414 may enable one or more processors 1404 to include a criterion in a request for periodic or triggered location, wherein the criterion includes a criterion for reporting detected periodic or triggered events using a request for early connection release or a request for immediate connection release, or both.

[0252] The memory 1410 may further include an event information response unit 1416, which enables one or more processors 1404 to receive, via an external interface 1402, an event report message and a release assist indication (RAI) sent by the UE to a core network (CN) node (e.g., AMF 154) from that CN node. The RAI includes a request for immediate connection release or a request for early connection release. The request for early connection release includes an indication that the UE does not expect a response message from the location server 1400 or an indication that the UE expects a response message from the location server 1400. The event report message contains an event message obtained by the UE after detecting a periodic or triggered event, and the event information includes at least one of location measurement, location estimation, the type of the detected triggering event, or a combination thereof. The event information response unit 1416 enables one or more processors 1404 to send an event report confirmation message to the CN node via the external interface 1402 in response to the event report message.

[0253] The memory 1410 may further include a location determination unit 1418 that enables one or more processors 1404 to determine the location information of the UE based at least in part on event information received by the event information response unit 1416. For example, the location determination unit 1418 may enable one or more processors 1404 to determine the estimated location of the UE 105 using one or more positioning methods such as, for example, GNSS, assisted GNSS (A-GNSS), advanced forward link trilateration (AFLT), observed time difference of arrival (OTDOA), WLAN, or enhanced cell ID (ECID), or combinations thereof, using the received event information.

[0254] In some implementations, memory 1410 may also include a location reporting unit 1420, which enables one or more processors 1404 to send location information determined by location determination unit 1418 to another entity (such as a GMLC or an external client) via external interface 1402.

[0255] In some embodiments, memory 1410 may further include a positioning capability unit 1415, which enables one or more processors 1404 to send a request for the positioning capability of the UE to the UE via external interface 1402 and receive a response from the UE containing the positioning capability of the UE. For example, the positioning capability may include an indication that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both. The location information request unit 1414 may enable one or more processors 1404 to respond to receiving an indication that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both, including an indication that the UE may use a request for early connection release or a request for immediate connection release, or both, to report detected periodic or triggered events.

[0256] Depending on the application, the methods described herein can be implemented in various ways. For example, these methods can be implemented in hardware, firmware, software, or any combination thereof. In a hardware implementation, one or more processors 1404 may be implemented within 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.

[0257] For implementations involving firmware and / or software, the methods can be implemented using modules (e.g., programs, functions, etc.) that perform the individual functions described herein. Any machine-readable medium that tangibly embodies the instructions can be used to implement the methods described herein. For example, software code can be stored in memory (e.g., memory 1410) and executed by one or more processor units (e.g., processor 1404), thereby enabling the processor unit to act as a dedicated computer programmed to execute the techniques and programs disclosed herein. Memory can be implemented within or outside the processor unit. As used herein, the term "memory" means any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type of memory or a particular number of memories, or the type of medium on which memory is stored.

[0258] When implemented in firmware and / or software, functionality can 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 includes physical computer storage media. The storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage media, semiconductor storage devices or other storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and is accessible by a computer; as used herein, disks and optical discs include compact optical discs (CDs), laser optical discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically reproduce data magnetically, while optical discs reproduce data optically by means of lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0259] In addition to being stored on a computer-readable storage medium, instructions and / or data may also be provided as signals on a transmission medium included in the communication apparatus. For example, the communication apparatus may include a transceiver having signals indicating instructions and data. The instructions and data are stored on a non-transitory computer-readable medium, such as memory 1410, and configured to cause one or more processors (e.g., processor 1404) to act as a dedicated computer programmed to execute the techniques and programs disclosed herein. That is, the communication apparatus includes a transmission medium having signals indicating information for performing the disclosed functions. At a first time, the transmission medium included in the communication apparatus may include a first portion of the information for performing the disclosed functions, and at a second time, the transmission medium included in the communication apparatus may include a second portion of the information for performing the disclosed functions.

[0260] Therefore, a location server 1400, such as LMF 152, may include components for sending a request to the UE for periodic or triggered location, the request including indications that the UE may report the detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both. This component may be, for example, an external interface 1402 and one or more processors 1404 having executable code or software instructions (such as location information request unit 1414) in dedicated hardware or implemented memory 1410. Components for receiving a response from the UE (which confirms the periodic or triggered location) may be, for example, an external interface 1402 and one or more processors 1404 having executable code or software instructions (such as location information request unit 1414) in dedicated hardware or implemented memory 1410. The component for receiving event reporting messages and release assist indications (RAIs) sent by the UE to the CN node from the core network (CN) node (where the RAI includes a request for immediate connection release or a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the location server or an indication that the UE expects a response message from the location server, wherein the event reporting message contains an event message obtained by the UE after the UE detects a periodic or triggered event, wherein the event information includes at least one of location measurement, location estimation, the type of the detected triggering event, or a combination thereof) may be, for example, an external interface 1402 and one or more processors 1404 having dedicated hardware or executable code or software instructions (such as event information response unit 1416) in memory 1410. The component for determining the UE's location information based on the event information may be, for example, one or more processors 1404 having dedicated hardware or executable code or software instructions (such as location determination unit 1418) in memory 1410. The component used to send the UE's location information to another entity may be, for example, an external interface 1402 and one or more processors 1404 having dedicated hardware or executable code or software instructions (such as a location reporting unit 1420) in a memory 1410.

[0261] The location server 1400 may also include a component for sending an event report confirmation message to the CN node in response to an event report message, wherein the event report confirmation message is forwarded by the CN node to the UE. This component may be, for example, an external interface 1402 and one or more processors 1404 having executable code or software instructions (such as an event information response unit 1416) in dedicated hardware or implementation memory 1410.

[0262] The location server 1400 may also include a component for including a standard in requests for periodic or triggered location, wherein the standard includes a standard for reporting detected periodic or triggered events using a request for early connection release, or a request for immediate connection release, or both. This component may be, for example, an external interface 1402 and one or more processors 1404 having executable code or software instructions (such as location information request unit 1414) in dedicated hardware or implementation memory 1410.

[0263] The positioning server 1400 may also include components for sending a request to the UE for the UE's positioning capabilities. These components may be, for example, an external interface 1402 and one or more processors 1404 having executable code or software instructions (such as positioning capability unit 1415) in dedicated hardware or implemented memory 1410. Components for receiving a response from the UE including the UE's positioning capabilities (wherein the positioning capabilities include indications such as: the UE supports reporting periodic and triggering events using a request for early connection release, or a request for immediate connection release, or both) may be, for example, an external interface 1402 and one or more processors 1404 having executable code or software instructions (such as positioning capability unit 1415) in dedicated hardware or implemented memory 1410. The component used to respond to receiving an indication that the UE supports reporting periodic and triggering events using a request for early connection release or a request for immediate connection release, or both, may include the UE being able to report detected periodic or triggering events using a request for early connection release or a request for immediate connection release, or both. This component may be, for example, an external interface 1402 and one or more processors 1404 having dedicated hardware or executable code or software instructions (such as location information request unit 1414) in implementation memory 1410.

[0264] Figure 15 It shows things like Figures 1 to 9 The diagram illustrates an example hardware implementation of a core network (CN) node 1500 of an AMF (e.g., AMF 154). The CN node 1500 includes, for example, hardware components such as an external interface 1502, which may be capable of connecting to a location server (such as...). Figures 1 to 9The LMF 152 shown herein and wired or wireless interfaces for RANs (such as RAN 112 (e.g., NG-RAN 112)) are also included. The CN node 1500 includes one or more processors 1504 and a memory 1510, which may be coupled to a bus 1506. The memory 1510 may store data and may contain executable code or software (or firmware) instructions that, when executed by the one or more processors 1504, cause the one or more processors 1504 to act as a dedicated computer programmed to execute the programs and techniques disclosed herein.

[0265] like Figure 15 As shown, memory 1510 includes one or more components or modules that, when implemented by one or more processors 1504, implement the methods described herein. Although the components or modules are shown as software in memory 1510 executable by one or more processors 1504, it should be understood that the components or modules may be dedicated hardware, either in-processor or out-of-processor. As shown, memory 1510 may include a forwarding request unit 1512 that enables one or more processors 1504 to receive a request for periodic or triggered location from a location server (e.g., LMF 152) via an external interface 1502 and to send the request to a UE (e.g., UE 105), wherein the request includes an indication that the UE may report the detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both. The forwarding request unit 1512 can also enable one or more processors 1504 to receive requests for periodic or triggered location from a gateway mobile location center (e.g., GMLC 155) via an external interface 1502 and send such requests to a location server. The periodic or triggered location requests sent to the location server may include location capabilities received from the UE.

[0266] Memory 1510 may include a forwarding response unit 1514 that enables one or more processors 1504 to receive a response from the UE via external interface 1502 and send the response to a location server, wherein the response confirms the periodic or triggered location. NAS transmission unit 1516 enables one or more processors 1504 to receive, via external interface 1502, a Non-Access Stratum (NAS) transmission message and a Release Assist Indication (RAI) sent by the UE to a Radio Access Network (RAN) node (e.g., gNB 110 or ng-eNB 114) from the RAN node, wherein the RAI includes a request for immediate connection release or a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the location server or an indication that the UE expects a response message from the location server, and wherein the NAS transmission message includes a routing identifier identifying the location server and an event report message, which contains an event message obtained by the UE after the UE detects a periodic or triggered event, and wherein the event information includes at least one of location measurement, location estimation, the type of the detected triggering event, or a combination thereof. The NAS transmission unit 1516 can also enable one or more processors 1504 to send a NAS transmission message containing a received event report confirmation message to the UE via an external interface 1502.

[0267] The event report transmission unit 1518 causes one or more processors 1504 to send an event report message and a RAI to the positioning server via the external interface 1502. The event report transmission unit 1518 can also cause one or more processors 1504 to receive an event report confirmation message from the positioning server via the external interface 1502 in response to the event report message.

[0268] The positioning capability unit 1520 enables one or more processors 1504 to receive the UE's positioning capability from the UE via an external interface 1502 during the UE's registration with the CN node. The positioning capability includes indications that the UE supports reporting periodic and triggering events using a request for early connection release or a request for immediate connection release, or both.

[0269] Depending on the application, the methods described herein can be implemented in various ways. For example, these methods can be implemented in hardware, firmware, software, or any combination thereof. In a hardware implementation, one or more processors 1504 may be implemented within 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.

[0270] For implementations involving firmware and / or software, the methods can be implemented using modules (e.g., programs, functions, etc.) that perform the individual functions described herein. Any machine-readable medium that tangibly embodies the instructions can be used to implement the methods described herein. For example, software code can be stored in memory and executed by one or more processor units, thereby enabling the processor units to act as dedicated computers programmed to execute the algorithms disclosed herein. Memory can be implemented within or outside the processor unit. As used herein, the term "memory" means any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type of memory or a particular number of memories, or the type of medium on which memory is stored.

[0271] When implemented in firmware and / or software, functionality can 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 includes physical computer storage media. The storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage media, semiconductor storage devices or other storage devices, or any other medium capable of storing desired program code in the form of instructions or data structures and accessible by a computer; as used herein, disks and optical discs include compact optical discs (CDs), laser discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically reproduce data magnetically, while optical discs reproduce data optically by means of lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0272] In addition to being stored on a computer-readable storage medium, instructions and / or data may also be provided as signals on a transmission medium included in the communication apparatus. For example, the communication apparatus may include a transceiver having signals indicating instructions and data. The instructions and data are stored on a non-transitory computer-readable medium, such as memory 1510, and configured to cause one or more processors to act as a dedicated computer programmed to execute the programs and techniques disclosed herein. That is, the communication apparatus includes a transmission medium having signals indicating information for performing the disclosed functions. At a first time, the transmission medium included in the communication apparatus may include a first portion of the information for performing the disclosed functions, and at a second time, the transmission medium included in the communication apparatus may include a second portion of the information for performing the disclosed functions.

[0273] Therefore, a CN node 1500 such as AMF 154 may include components for receiving a request for periodic or triggered location from a location server and sending the request for periodic or triggered location to a UE, the request including an indication that the UE may report the detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both. This component may be, for example, an external interface 1502 and one or more processors 1504 having executable code or software instructions (such as a forwarding request unit 1512) in dedicated hardware or implemented memory 1510. Components for receiving a response from the UE and sending the response (which confirms the periodic or triggered location) to the location server may be, for example, an external interface 1502 and one or more processors 1504 having executable code or software instructions (such as a forwarding response unit 1514) in dedicated hardware or implemented memory 1510. The component for receiving, from a Radio Access Network (RAN) node, a Non-Access Stratum (NAS) transmission message and a Release Assist Indication (RAI) sent by a UE to the RAN node (where the RAI includes a request for immediate connection release or a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the location server or an indication that the UE expects a response message from the location server, wherein the NAS transmission message includes a routing identifier identifying the location server and an event report message contained in an event message obtained by the UE after the UE detects a periodic or triggered event, wherein the event information includes at least one of location measurement, location estimation, the type of the detected trigger event, or a combination thereof) may be, for example, an external interface 1502 and one or more processors 1504 having dedicated hardware or executable code or software instructions (such as NAS transmission unit 1516) in implemented memory 1510. The component for sending the event report message and the RAI to the location server may be, for example, an external interface 1502 and one or more processors 1504 having dedicated hardware or executable code or software instructions (such as event report transmission unit 1518) in implemented memory 1510.

[0274] CN node 1500 may include components for receiving a second request for periodic or triggered location from a gateway mobile location center. This component may be, for example, an external interface 1502 and one or more processors 1504 having executable code or software instructions (such as forwarding request unit 1512) in dedicated hardware or implemented memory 1510. Components for sending the second request for periodic or triggered location to a location server (where receiving the request for periodic or triggered location from the location server is in response to sending the second request for periodic or triggered location to the location server) may be, for example, an external interface 1502 and one or more processors 1504 having executable code or software instructions (such as forwarding request unit 1512) in dedicated hardware or implemented memory 1510.

[0275] The CN node 1500 may also include components for receiving an event report confirmation message from the location server in response to an event report message. These components may be, for example, an external interface 1502 and one or more processors 1504 having executable code or software instructions (such as an event report transmission unit 1518) in dedicated hardware or implemented memory 1510. Components for sending a NAS transmission message containing the event report confirmation message to the UE may be, for example, an external interface 1502 and one or more processors 1504 having executable code or software instructions (such as a NAS transmission unit 1516) in dedicated hardware or implemented memory 1510.

[0276] CN node 1500 may further include components for receiving the UE's positioning capabilities from the UE during UE registration with the CN node (wherein the positioning capabilities include indications that the UE supports reporting periodic and triggered events using a request for early connection release, or a request for immediate connection release, or both). These components may be, for example, an external interface 1502 and one or more processors 1504 having dedicated hardware or executable code or software instructions (such as positioning capability unit 1520) in implemented memory 1510. Components for including the UE's positioning capabilities in a second request for periodic or triggered positioning sent to the positioning server (wherein the positioning server responds to receiving an indication that the UE supports reporting periodic and triggered events using a request for early connection release, or a request for immediate connection release, or both, and includes an indication that the UE can report detected periodic or triggered events using a request for early connection release, or a request for immediate connection release, or both) may be, for example, an external interface 1502 and one or more processors 1504 having dedicated hardware or executable code or software instructions (such as forwarding request unit 1512) in implemented memory 1510.

[0277] Figure 16It shows things like Figure 1 and Figure 2 As shown and referenced Figures 3 to 9 This is a diagram illustrating an example hardware implementation of the RAN node 1600 of a gNB 110 or ng-eNB 114. The RAN node 1600 may be part of, for example, a wireless network such as 5GS, and may be an element in, for example, RAN 112 (e.g., NG-RAN 112), which may be a New Radio (NR) Node B (gNB) or a Next Generation Evolution Node B (ng-eNB). The RAN node 1600 includes, for example, hardware components such as an external interface 1602, which may be a wired and / or wireless interface capable of connecting to a core network (CN) node such as AMF 154 and UEs (such as UE 105). The RAN node 1600 includes one or more processors 1604 and memories 1610, which may be coupled to a bus 1606. The memory 1610 may store data and may contain executable code or software (or firmware) instructions that, when executed by one or more processors 1604, cause one or more processors 1604 to act as a dedicated computer programmed to execute the programs and techniques disclosed herein.

[0278] like Figure 16 As shown, memory 1610 includes one or more components or modules that, when implemented by one or more processors 1604, implement the methods described herein. Although the components or modules are shown as software in memory 1610 executable by one or more processors 1604, it should be understood that the components or modules may be dedicated hardware in or outside the processor 1604. As shown, memory 1610 may include a forwarding request unit 1612 that enables one or more processors 1604 to receive a request for periodic or triggered location from a location server (e.g., via a CN node) via an external interface 1602 and to send the request for periodic or triggered location to the UE. A forwarding response unit 1614 enables one or more processors 1604 to receive a response from the UE via the external interface 1602 and (e.g., via a CN node) send the response to the location server, wherein the response acknowledges the periodic or triggered location.

[0279] The memory 1610 may include a signaling connection unit 1616, which enables one or more processors 1604 to receive a signaling connection request from the UE via an external interface 1602 and to provide a signaling connection with the UE via the external interface 1602.

[0280] The event information response unit 1618 enables one or more processors 1604 to receive a first message from the UE via an external interface 1602. This first message includes a request for early connection release. The first message also includes a Non-Access Stratum (NAS) transmission message containing a routing identifier identifying the location server and an event report message. This event report message includes an event message obtained by the UE after detecting a periodic or triggered event. The event information includes at least one of location measurement, location estimation, the type of the detected triggered event, or a combination thereof. The event information response unit 1618 also enables one or more processors 1604 to receive a message containing a NAS transmission message from the CN node via the external interface 1602. This NAS transmission message includes an event report confirmation message.

[0281] The NAS transmission unit 1620 enables one or more processors 1604 to send NAS transmission messages and requests for early connection release to a core network (CN) node (e.g., AMF 154) via an external interface 1602, wherein the CN node forwards event report messages to the location server. The NAS transmission unit 1620 can also enable one or more processors 1604 to send NAS transmission messages containing event report confirmation messages to the UE via the external interface 1602.

[0282] Release unit 1622 causes one or more processors 1604 to send a second message to the UE via external interface 1602, wherein the second message releases the signaling connection to the RAN node.

[0283] The positioning capability unit 1624 can enable one or more processors 1604 to receive a request for positioning capability from the positioning server via the external interface 1602 and through the CN node, and send the request for positioning capability to the UE. The positioning capability unit 1624 can also enable one or more processors 1604 to receive a response including the UE's positioning capability from the UE via the external interface 1602, and send the response to the positioning server via the CN node.

[0284] Depending on the application, the methods described herein can be implemented in various ways. For example, these methods can be implemented in hardware, firmware, software, or any combination thereof. In a hardware implementation, one or more processors 1604 may be implemented within 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.

[0285] For implementations involving firmware and / or software, the methods can be implemented using modules (e.g., programs, functions, etc.) that perform the individual functions described herein. Any machine-readable medium that tangibly embodies the instructions can be used to implement the methods described herein. For example, software code can be stored in memory and executed by one or more processor units, thereby enabling the processor units to act as dedicated computers programmed to execute the algorithms disclosed herein. Memory can be implemented within or outside the processor unit. As used herein, the term "memory" means any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type of memory or a particular number of memories, or the type of medium on which memory is stored.

[0286] When implemented in firmware and / or software, functionality can 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 includes physical computer storage media. The storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage media, semiconductor storage devices or other storage devices, or any other medium capable of storing desired program code in the form of instructions or data structures and accessible by a computer; as used herein, disks and optical discs include compact optical discs (CDs), laser discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically reproduce data magnetically, while optical discs reproduce data optically by means of lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0287] In addition to being stored on a computer-readable storage medium, instructions and / or data may also be provided as signals on a transmission medium included in the communication apparatus. For example, the communication apparatus may include a transceiver having signals indicating instructions and data. The instructions and data are stored on a non-transitory computer-readable medium, such as memory 1610, and configured to cause one or more processors 1604 to act as a dedicated computer programmed to execute the programs and techniques disclosed herein. That is, the communication apparatus includes a transmission medium having signals indicating information for performing the disclosed functions. At a first time, the transmission medium included in the communication apparatus may include a first portion of the information for performing the disclosed functions, and at a second time, the transmission medium included in the communication apparatus may include a second portion of the information for performing the disclosed functions.

[0288] Therefore, a RAN node 1600, such as gNB 110 or ng-eNB 114, may include components for receiving a request for periodic or triggered location from a location server and sending the request for periodic or triggered location to a UE. The request may include an indication that the UE can report the detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both. This component may be, for example, an external interface 1602 and one or more processors 1604 having executable code or software instructions (such as a forwarding request unit 1612) in dedicated hardware or implemented memory 1610. Components for receiving a response from the UE and sending that response (which confirms the periodic or triggered location) to the location server may be, for example, an external interface 1602 and one or more processors 1604 having executable code or software instructions (such as a forwarding response unit 1614) in dedicated hardware or implemented memory 1610. The components used to receive a request for a signaling connection from the UE (where the signaling connection does not include a signaling connection to a core network (CN) node) may be, for example, an external interface 1602 and one or more processors 1604 having executable code or software instructions (such as signaling connection unit 1616) in dedicated hardware or implemented memory 1610. The components used to provide a signaling connection to the UE may be, for example, an external interface 1602 and one or more processors 1604 having executable code or software instructions (such as signaling connection unit 1616) in dedicated hardware or implemented memory 1610. The component for receiving a first message from the UE (where the first message includes a Release Assist Instruction (RAI), wherein the first message contains a Non-Access Stratum (NAS) transport message, the NAS transport message containing a routing identifier identifying the location server, and an event report message, the event report message containing an event message obtained by the UE after detecting a periodic or triggered event, the event information including at least one of location measurement, location estimation, the type of the detected trigger event, or a combination thereof) may be, for example, an external interface 1602 and one or more processors 1604 having executable code or software instructions (such as an event information response unit 1618) in dedicated hardware or implemented memory 1610. The component for sending the NAS transport message and the RAI to the CN node (where the CN node forwards the event report message and the RAI to the location server) may be, for example, an external interface 1602 and one or more processors 1604 having executable code or software instructions (such as a NAS transport unit 1620) in dedicated hardware or implemented memory 1610. The component used to send a second message to the UE (where the second message releases the signaling connection to the RAN node) may be, for example, an external interface 1602 and one or more processors 1604 having dedicated hardware or executable code or software instructions (such as release unit 1622) in memory 1610.

[0289] RAN node 1600 may further include components for receiving a third message from CN node (the third message containing a NAS transmission message, the NAS transmission message containing an event report confirmation message, the event report confirmation message being sent to CN node by the positioning server in response to the event report message), such components may be, for example, an external interface 1602 and one or more processors 1604 having executable code or software instructions (such as event information response unit 1618) in dedicated hardware or implemented memory 1610. Components for sending a fourth message to UE (the fourth message containing the NAS transmission message) may be, for example, an external interface 1602 and one or more processors 1604 having executable code or software instructions (such as NAS transmission unit 1620) in dedicated hardware or implemented memory 1610.

[0290] RAN node 1600 may also include components for receiving a request for location capability from the location server via the CN node and sending the request for location capability to the UE. These components may be, for example, an external interface 1602 and one or more processors 1604 having executable code or software instructions (such as location capability unit 1624) in dedicated hardware or implementation memory 1610. The components used to receive a response from the UE including the UE's positioning capabilities and to send the response to the positioning server via the CN node (wherein the positioning capabilities include indications that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both, wherein the positioning server responds to receiving an indication that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both, and the indication that the UE can report detected periodic or triggered events using a request for early connection release or a request for immediate connection release, or both) may be, for example, an external interface 1602 and one or more processors 1604 having dedicated hardware or executable code or software instructions (such as positioning capability unit 1624) in implementation memory 1610.

[0291] Figure 17 This shows UE 1700 (such as Figures 1 to 9 The diagram illustrates an example hardware implementation of UE 105 shown. UE 1700 may include a radio transceiver 1702 to communicate with NG-RAN 112 (e.g., such as gNB 110 or ng-eNB 114). Figure 1 and Figure 2 The UE 1700 may also include additional transceivers (such as a wireless local area network (WLAN) transceiver 1706) and transceivers for communication from the SPS SV 190 (shown). Figure 1 and Figure 2 (Shown) An SPS receiver 1708 for receiving and measuring signals. UE 1700 may also include one or more sensors 1710, such as a camera, accelerometer, gyroscope, electronic compass, magnetometer, barometer, etc. UE 1700 may also include a user interface 1712, which may include, for example, a display, keypad, or other input device, such as a virtual keypad on the display, through which a user can interact with UE 1700. UE 1700 also includes one or more processors 1704 and memory 1720, which may be coupled to bus 1716. One or more processors 1704 and other components of UE 1700 may similarly be coupled to bus 1716, a separate bus, or may be directly connected together or coupled using a combination of the foregoing. Memory 1720 may store data and may contain executable code or software (or firmware) instructions that, when executed by one or more processors 1704, cause one or more processors 1704 to act as a dedicated computer programmed to execute the programs and techniques disclosed herein.

[0292] like Figure 17 As shown, memory 1720 may include one or more components or modules that may be implemented by one or more processors 1704 to perform the methods described herein. Although components or modules are shown as software in memory 1720 that may be executed by one or more processors 1704, it should be understood that components or modules may be dedicated hardware in or outside of one or more processors 1704. As shown, memory 1720 may include a location information request unit 1722 that enables one or more processors 1704 to receive a request for periodic or triggered location from a location server (e.g., LMF 152) via wireless transceiver 1702 or WLAN transceiver 1706 and send a response to the location server, wherein the response confirms the periodic or triggered location. Memory 1720 may include a periodic or triggered event detection unit 1723 that enables one or more processors 1704 to detect periodic or triggered events. When implemented by one or more processors 1704, the periodic or triggered event detection unit 1723 configures one or more processors 1704 to receive and monitor triggering events indicated by triggering parameters in a request for periodic or triggered positioning from a positioning server. Triggering parameters may include, for example, a trigger evaluation interval, a periodic maximum reporting interval, and one or more positioning triggers, such as location changes, entering or leaving a defined geographic area or remaining within it, moving more than a threshold linear distance from a previous location, etc.

[0293] Memory 1720 may include an event information measurement unit 1724 that enables one or more processors 1704 to acquire event information, such as location measurement, location estimation, the type of a detected triggering event, or a combination thereof. Memory 1720 may include a signaling connection unit 1726 that enables one or more processors 1704 to establish a signaling connection with a RAN node (such as gNB 110 or ng-eNB 114) via a radio transceiver 1702. Memory 1720 may further include an event information response unit 1728 that enables one or more processors 1704 to send a first message to the RAN node via the radio transceiver 1702, wherein the first message includes a Release Assistance Indication (RAI) and a Non-Access Stratum (NAS) transmission message, the NAS transmission message containing a routing identifier identifying the location server and an event report message containing event information, wherein the RAN node forwards the NAS transmission message and the RAI to a core network (CN) node (e.g., AMF 154), and wherein the CN node forwards the event report message and the RAI to the location server. The event information response unit 1728 can also enable one or more processors 1704 to receive a message containing a NAS transmission message from the RAN node via a wireless transceiver 1702 or a WLAN transceiver 1706, the NAS transmission message containing an event report confirmation message. The release unit 1730 enables one or more processors 1704 to receive a second message from the RAN node via the wireless transceiver 1702 and release the signaling connection to the RAN node based on the second message.

[0294] The memory 1720 may include a positioning capability unit 1732, which enables one or more processors 1704 to receive a request for positioning capability of the UE from a positioning server via a wireless transceiver 1702 or a WLAN transceiver 1706. The positioning capability unit 1732 may also enable one or more processors 1704 to send a response including the UE's positioning capability to the positioning server via the wireless transceiver 1702 or the WLAN transceiver 1706.

[0295] Depending on the application, the methods described herein can be implemented in various ways. For example, these methods can be implemented in hardware, firmware, software, or any combination thereof. In a hardware implementation, one or more processors 1704 may be implemented within 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.

[0296] For implementations of the UE 1700 involving firmware and / or software, the methods can be implemented using modules (e.g., programs, functions, etc.) that perform the individual functions described herein. Any machine-readable medium that tangibly embodies the instructions can be used to implement the methods described herein. For example, software code can be stored in memory (e.g., memory 1720) and executed by one or more processors 1704, thereby enabling one or more processors 1704 to act as a dedicated computer programmed to perform the techniques disclosed herein. Memory can be implemented within one or more processors 1704 or external to one or more processors 1704. As used herein, the term "memory" means any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type of memory or a particular number of memories, or the type of medium on which memory is stored.

[0297] When implemented in firmware and / or software, functions performed by UE 1700 may be stored as one or more instructions or codes on a non-transitory computer-readable storage medium (such as memory 1720). 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 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 disc storage, disk storage media, semiconductor storage devices or other storage devices, or any other medium capable of storing desired program code in the form of instructions or data structures and accessible by a computer; disks and optical discs as used herein include compact optical discs (CDs), laser optical discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically reproduce data magnetically, while optical discs reproduce data optically by means of lasers. The combination of the above should also be included within the scope of computer-readable media.

[0298] In addition to being stored on a computer-readable storage medium, instructions and / or data for UE 1700 may also be provided as signals on a transmission medium included in the communication apparatus. For example, a communication apparatus including part or all of UE 1700 may include a transceiver having signals indicating instructions and data. The instructions and data are stored on a non-transitory computer-readable medium, such as memory 1720, and configured to cause one or more processors 1704 to act as a dedicated computer programmed to perform the techniques disclosed herein. That is, the communication apparatus includes a transmission medium having signals indicating information for performing the disclosed functions. At a first time, the transmission medium included in the communication apparatus may include a first portion of the information for performing the disclosed functions, and at a second time, the transmission medium included in the communication apparatus may include a second portion of the information for performing the disclosed functions.

[0299] Therefore, UE 1700 may include components for receiving requests for periodic or triggered positioning from a positioning server. These components may be, for example, one of a wireless transceiver 1702 or a WLAN transceiver 1706, and one or more processors 1704 having executable code or software instructions (such as a location information request unit 1722) in dedicated hardware or implemented memory 1720. Components for sending a response to the positioning server (which confirms periodic or triggered positioning) may be, for example, one of a wireless transceiver 1702 or a WLAN transceiver 1706, and one or more processors 1704 having executable code or software instructions (such as a location information request unit 1722) in dedicated hardware or implemented memory 1720. The component for detecting periodic or triggered events may be, for example, one of a wireless transceiver 1702 or WLAN transceiver 1706, an SPS receiver 1708, a sensor 1710, and one or more processors 1704 having executable code or software instructions (such as a periodic or triggered event detection unit 1723) in dedicated hardware or implemented memory 1720. The component for obtaining event information (event information including at least one of location measurement, location estimation, type of detected triggered event, or a combination thereof) may be, for example, one of a wireless transceiver 1702, a WLAN transceiver 1706, an SPS receiver 1708, or a sensor 1710, and one or more processors 1704 having executable code or software instructions (such as an event information measurement unit 1724) in dedicated hardware or implemented memory 1720. The components for obtaining a signaling connection to a Radio Access Network (RAN) node (where the signaling connection does not include a signaling connection to a Core Network (CN) node) may be, for example, a radio transceiver 1702 and one or more processors 1704 having executable code or software instructions (such as a signaling connection unit 1726) in dedicated hardware or implemented memory 1720. The components for sending a first message to the RAN node (where the first message contains a Non-Access Stratum (NAS) transmission message containing a routing identifier identifying a location server and an event report message containing event information, wherein the RAN node forwards the NAS transmission message to the CN node, and the CN node forwards the event report message to the location server) may be, for example, a radio transceiver 1702 and one or more processors 1704 having executable code or software instructions (such as an event information response unit 1728) in dedicated hardware or implemented memory 1720. The component for receiving a second message from the RAN node (where the second message releases the signaling connection to the RAN node) may be, for example, a wireless transceiver 1702 and one or more processors 1704 having dedicated hardware or executable code or software instructions (such as release unit 1730) in memory 1720.

[0300] UE 1700 may also include components for including a release assist indication (RAI) in a first message (where the RAN node forwards the NAS transmission message and the RAI to the CN node, and the CN node forwards the event report message and the RAI to the location server). These components may be, for example, a radio transceiver 1702 and one or more processors 1704 having executable code or software instructions (such as an event information response unit 1728) in dedicated hardware or implementation memory 1720.

[0301] UE 1700 may also include components for receiving a third message from a RAN node (the third message containing a NAS transmission message containing an event report confirmation message sent by a positioning server in response to the event report message). This component may be, for example, a radio transceiver 1702 and one or more processors 1704 having executable code or software instructions (such as an event information response unit 1728) in dedicated hardware or implementation memory 1720.

[0302] UE 1700 may also include components for receiving requests for location capabilities from a location server. These components may be, for example, one of a wireless transceiver 1702 or a WLAN transceiver 1706, and one or more processors 1704 having executable code or software instructions (such as location capability unit 1732) in dedicated hardware or implementation memory 1720. The component used to send a response to the positioning server including the positioning capabilities of the UE (wherein the positioning capabilities include indications that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both), may be, for example, one of a wireless transceiver 1702 or a WLAN transceiver 1706 and one or more processors 1704 having dedicated hardware or executable code or software instructions (such as positioning capability unit 1732) in implementation memory 1720.

[0303] Throughout this specification, references to "an example," "example," "some examples," or "exemplary implementation" mean that a particular feature, structure, or characteristic described in conjunction with a feature and / or example may be included in at least one feature and / or example of the claimed subject matter. Therefore, the phrases "in one example," "example," "some examples," or "some implementations," or other similar phrases appearing throughout this specification do not necessarily all refer to the same feature, example, and / or limitation. Furthermore, a particular feature, structure, or characteristic may be combined in one or more examples and / or features.

[0304] Some portions of the detailed description included herein are presented based on algorithms or symbolic representations of operations on binary digital signals stored in the memory of a particular device or dedicated computing device or platform. In the context of this particular specification, the term "specific device," etc., includes general-purpose computers once it is programmed to perform a specific operation according to instructions from program software. Algorithm descriptions or symbolic representations are examples of techniques used by those skilled in the art of signal processing or related fields to convey the essence of their work to others skilled in the art. An algorithm herein and generally considered is a self-consistent sequence of operations or similar signal processing that leads to a desired result. In this context, an operation or processing involves the physical manipulation of physical quantities. Typically, although not strictly necessary, such quantities may take the form of electrical or magnetic signals capable of being stored, transmitted, combined, compared, or otherwise manipulated. It has been shown that it is sometimes convenient, in principle for general reasons, to refer to such signals as bits, data, values, elements, symbols, characters, items, numbers, etc. However, it should be understood that all such terms or similar terms will be associated with appropriate physical quantities and are merely convenient labels. Unless otherwise specified, it will be apparent from the discussion herein that the use of terms such as “processing,” “calculating,” “operating,” and “determining” throughout this specification refers to the actions or processes of a particular device (such as a dedicated computer, dedicated computing device, or similar dedicated electronic computing device). Therefore, in the context of this specification, a dedicated computer or similar dedicated electronic computing device is capable of manipulating or converting signals, which generally represent physical electronic or magnetic quantities in the memory, registers, or other information storage devices, transmitting devices, or display devices of the dedicated computer or similar dedicated electronic computing device.

[0305] In the foregoing detailed description, numerous specific details have been set forth to provide a thorough understanding of the claimed subject matter. However, those skilled in the art will understand that the claimed subject matter can be practiced without these specific details. In other instances, methods and apparatus known to those skilled in the art have not been described in detail to avoid obscuring the claimed subject matter.

[0306] As used herein, the terms “and,” “or,” and “and / or” can include, and are also contemplated, various meanings that depend at least in part on the context in which such terms are used. Generally, “or,” when used with a list of related terms (such as A, B, or C), is intended to mean A, B, and C (used herein in an inclusive sense) and A, B, or C (used herein in an exclusive sense). Additionally, the term “one or more,” as used herein, can be used to describe any feature, structure, or characteristic in the singular, or can be used to describe a plurality of features, structures, or characteristics, or some other combination of features, structures, or characteristics. However, it should be noted that this is merely an illustrative example, and the claimed subject matter is not limited to this example.

[0307] Although features currently considered exemplary have been shown and described, those skilled in the art will understand that various other modifications and equivalents may be made without departing from the claimed subject matter. Furthermore, numerous modifications may be made to adapt specific situations to the teachings of the claimed subject matter without departing from the central concepts described herein.

[0308] One implementation (1) can be a method performed by a location server to support periodic and triggered location for a user equipment (UE), the method comprising: sending a request to the UE for periodic or triggered location, the request including an indication that the UE may report a detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both; receiving a response from the UE acknowledging the periodic or triggered location; and receiving an event reporting message and a release assist indication (RAI) sent by the UE to the core network (CN) node, wherein the RAI... I includes a request for immediate connection release or a request for early connection release, wherein a request for early connection release includes an indication that the UE does not expect a response message from the location server or an indication that the UE expects a response message from the location server, wherein the event report message includes an event message obtained by the UE after the UE detects a periodic or triggered event, wherein the event information includes at least one of location measurement, location estimation, the type of the detected triggered event, or a combination thereof; determining the UE's location information based on the event information; and sending the UE's location information to another entity.

[0309] Some implementations (2) of the above method (1) may exist, wherein the event reporting message includes a location protocol message, a supplemental service protocol message, or both of these messages.

[0310] Some implementations (3) of the above method (1) may exist, wherein the CN node is an Access and Mobility Management Function (AMF) and the location server is a Location Management Function (LMF).

[0311] Some implementations (4) of the above method (1) may exist, wherein the RAI includes a request for immediate connection release or a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the location server, and the method further includes avoiding sending a response message to the UE.

[0312] Some implementations (5) of the above method (1) may exist, wherein the RAI includes a request for early connection release, wherein the request for early connection release includes an indication that the UE expects a response message from the positioning server, and further includes: sending an event report confirmation message to the CN node in response to the event report message, wherein the event report confirmation message is forwarded to the UE by the CN node.

[0313] Some implementations (6) of the above method (5) may exist, wherein the event report confirmation message includes confirmation of the event report message.

[0314] Some implementations (7) of the above method (1) may exist, further including criteria in the request for periodic or triggered location, wherein the criteria include criteria for reporting detected periodic or triggered events using a request for early connection release or a request for immediate connection release or both.

[0315] Some implementations (8) of the above method (1) may exist, further including: sending a request to the UE for the UE's positioning capabilities; receiving from the UE a response including the UE's positioning capabilities, wherein the positioning capabilities include an indication that the UE supports using a request for early connection release or a request for immediate connection release or both to report periodic and triggering events; and in response to receiving the indication that the UE supports using a request for early connection release or a request for immediate connection release or both to report periodic and triggering events, including an indication that the UE can use a request for early connection release or a request for immediate connection release or both to report detected periodic or triggering events.

[0316] Some implementations (9) of the above method (7) may exist, wherein the standard includes at least one of the following: using a request for immediate connection release when the UE is idle and the UE does not expect a response from the location server; using a request for early connection release when the UE is idle and the UE expects a response from the location server; using a non-access stratum (NAS) signaling connection in other cases or after a threshold time period or a threshold number of event reports have been used for the request for early connection release or the request for immediate connection release; or a combination of the above.

[0317] One implementation (10) may be a location server for supporting periodic and triggered location of a user equipment (UE), comprising: an external interface configured to communicate with a wireless network; and at least one processor coupled to the external interface and configured to: send a request for periodic or triggered location to the UE via the external interface, the request including indications that the UE may report detected periodic or triggered events using a request for early connection release, a request for immediate connection release, or both; receive a response from the UE via the external interface confirming the periodic or triggered location; and receive a request from a core network (CN) node via the external interface sent by the UE. The event reporting message and release assist indication (RAI) to the CN node, wherein the RAI includes a request for immediate connection release or a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the location server or an indication that the UE expects a response message from the location server, wherein the event reporting message contains an event message obtained by the UE after the UE detects a periodic or triggered event, wherein the event information includes at least one of location measurement, location estimation, the type of detected triggered event, or a combination thereof; determining the UE's location information based on the event information; and sending the UE's location information to another entity via the external interface.

[0318] Some implementations (11) of the above-mentioned location server (10) may exist, wherein the event reporting message includes a location protocol message, a supplemental service protocol message, or both of these messages.

[0319] Some implementations (12) of the above-mentioned location server (10) may exist, wherein the CN node is an access and mobility management function (AMF), and the location server is a location management function (LMF).

[0320] Some implementations (13) of the aforementioned location server (10) may exist, wherein the RAI includes a request for immediate connection release or a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the location server, and the at least one processor is further programmed to avoid sending a response message to the UE.

[0321] Some implementations (14) of the aforementioned location server (10) may exist, wherein the RAI includes a request for early connection release, wherein the request for early connection release includes an indication that the UE expects a response message from the location server, and wherein the at least one processor is further programmed to: in response to the event report message, send an event report confirmation message to the CN node via the external interface, wherein the event report confirmation message is forwarded to the UE by the CN node.

[0322] Some implementations (15) of the above-mentioned location server (14) may exist, wherein the event report confirmation message includes confirmation of the event report message.

[0323] Some implementations (16) of the above-described location server (10) may exist, wherein the at least one processor is further programmed to include criteria in the request for the periodic or triggered location, wherein the criteria include criteria for reporting the detected periodic or triggered events using a request for early connection release or a request for immediate connection release or both.

[0324] Some implementations (17) of the aforementioned positioning server (10) may exist, wherein the at least one processor is further programmed to: send a request for the positioning capabilities of the UE to the UE via the external interface; receive a response from the UE via the external interface including the positioning capabilities of the UE, wherein the positioning capabilities include an indication that the UE supports reporting periodic and triggering events using a request for early connection release or a request for immediate connection release or both; and, in response to receiving the indication that the UE supports reporting periodic and triggering events using a request for early connection release or a request for immediate connection release or both, via the external interface including an indication that the UE can report detected periodic or triggering events using a request for early connection release or a request for immediate connection release or both.

[0325] Some implementations (18) of the aforementioned location server (16) may exist, wherein the criteria include at least one of the following: using a request for immediate connection release when the UE is idle and the UE does not expect a response from the location server; using a request for early connection release when the UE is idle and the UE expects a response from the location server; using a non-access stratum (NAS) signaling connection in other cases or after a threshold time period or a threshold number of event reports have been used for the request for early connection release or the request for immediate connection release; or a combination of the above.

[0326] One implementation (19) may be a method performed by a core network (CN) node for supporting periodic and triggered location of a user equipment (UE), the method comprising: receiving a request for periodic or triggered location from a location server and sending the request for the periodic or triggered location to the UE, the request including an indication that the UE may report a detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both; receiving a response from the UE and sending the response to the location server, the response confirming the periodic or triggered location; and receiving a non-access stratum (NAS) transmission message sent by the UE to the RAN node from a radio access network (RAN) node. The NAS transmission message includes a release assist indication (RAI), wherein the RAI includes a request for immediate connection release or a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the location server or an indication that the UE expects a response message from the location server, wherein the NAS transmission message includes a routing identifier identifying the location server and an event report message, the event report message being an event message obtained by the UE after the UE detects a periodic or triggered event, wherein the event information includes at least one of location measurement, location estimation, the type of the detected trigger event, or a combination thereof; and sending the event report message and the RAI to the location server.

[0327] Some implementations (20) of the above method (19) may exist, wherein the event reporting message includes a location protocol message, a supplemental service protocol message, or both.

[0328] Some implementations (21) of the above method (19) may exist, further including: receiving a second request for periodic or triggered positioning from a gateway mobile positioning center; and sending the second request for periodic or triggered positioning to the positioning server, wherein receiving the request for periodic or triggered positioning from the positioning server is in response to sending the second request for periodic or triggered positioning to the positioning server.

[0329] Some implementations (22) of the above method (19) may exist, wherein the RAN node is a new radio (NR) node B (gNB) or a next-generation evolution node B (ng-eNB), wherein the CN node is an access and mobility management function (AMF), and wherein the location server is a location management function (LMF).

[0330] Some implementations (23) of the above method (19) may exist, wherein the RAI includes a request for immediate connection release or a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the location server, wherein no response message for the UE is received from the location server.

[0331] Some implementations (24) of the above method (19) may exist, wherein the RAI includes a request for early connection release, wherein the request for early connection release includes an indication that the UE expects a response message from the location server, and the method further includes: receiving an event report confirmation message from the location server in response to the event report message; and sending a NAS transmission message containing the event report confirmation message to the UE.

[0332] Some implementations (25) of the above method (24) may exist, wherein the event report confirmation message includes confirmation of the event report message.

[0333] Some implementations (26) of the above method (19) may exist, wherein the request for the periodic or triggered location includes criteria for reporting the detected periodic or triggered event using a request for early connection release or a request for immediate connection release or both.

[0334] Some implementations (27) of the above method (21) may exist, further comprising: during the registration of the UE to the CN node, receiving the UE's positioning capabilities from the UE, wherein the positioning capabilities include an indication that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release or both; the positioning capabilities of the UE are included in a second request for periodic or triggered positioning sent to the positioning server, wherein the positioning server, in response to receiving the indication that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release or both, includes an indication that the UE can report detected periodic or triggered events using a request for early connection release or a request for immediate connection release or both.

[0335] Some implementations (28) of the above method (26) may exist, wherein the standard includes at least one of the following: using a request for immediate connection release when the UE is idle and the UE does not expect a response from the location server; using a request for early connection release when the UE is idle and the UE expects a response from the location server; using a non-access stratum (NAS) signaling connection in other cases or after a threshold time period or a threshold number of event reports have been used for the request for early connection release or the request for immediate connection release; or a combination of the above.

[0336] One implementation (29) may be a core network (CN) node for supporting periodic and triggered location of a user equipment (UE), comprising: an external interface configured to communicate with a wireless network; and at least one processor coupled to the external interface and configured to: receive a request for periodic or triggered location from a location server via the external interface, and send the request for periodic or triggered location to the UE, the request including indications that the UE may report a detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both; receive a response from the UE via the external interface and send the response to the location server, the response confirming the periodic or triggered location; and receive a request from a radio access network (RAN) node via the external interface. The point receives a Non-Access Stratum (NAS) transmission message and a Release Assist Indication (RAI) sent by the UE to the RAN node, wherein the RAI includes a request for immediate connection release or a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the positioning server or an indication that the UE expects a response message from the positioning server, wherein the NAS transmission message includes a routing identifier identifying the positioning server and an event report message, wherein the event report message contains an event message obtained by the UE after the UE detects a periodic or triggered event, wherein the event information includes at least one of location measurement, location estimation, the type of detected triggering event, or a combination thereof; and sends the event report message and the RAI to the positioning server via the external interface.

[0337] Some implementations (30) of the aforementioned CN node (29) may exist, wherein the event reporting message includes a location protocol message, a supplemental service protocol message, or both.

[0338] Some implementations (31) of the aforementioned CN node (29) may exist, wherein the at least one processor is further configured to: receive a second request for periodic or triggered positioning from the gateway mobile positioning center via the external interface; and send the second request for periodic or triggered positioning to the positioning server via the external interface, wherein the at least one processor is further configured to receive the request for periodic or triggered positioning from the positioning server in response to sending the second request for periodic or triggered positioning to the positioning server.

[0339] Some implementations (32) of the above-mentioned CN node (29) may exist, wherein the RAN node is a new radio (NR) node B (gNB) or a next-generation evolution node B (ng-eNB), wherein the CN node is an access and mobility management function (AMF), and wherein the location server is a location management function (LMF).

[0340] Some implementations (33) of the aforementioned CN node (29) may exist, wherein the RAI includes a request for immediate connection release or a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the location server, wherein no response message for the UE has been received from the location server.

[0341] Some implementations (34) of the aforementioned CN node (29) may exist, wherein the RAI includes a request for early connection release, wherein the request for early connection release includes an indication that the UE expects a response message from the location server, wherein the at least one processor is further configured to: receive an event report confirmation message from the location server via the external interface in response to the event report message; and send a NAS transmission message containing the event report confirmation message to the UE via the external interface.

[0342] Some implementations (35) of the above-mentioned CN node (34) may exist, wherein the event report confirmation message includes confirmation of the event report message.

[0343] Some implementations (36) of the aforementioned CN node (29) may exist, wherein the request for periodic or triggered location includes a standard for reporting detected periodic or triggered events using a request for early connection release or a request for immediate connection release or both.

[0344] Some implementations (37) of the aforementioned CN node (31) may exist, wherein the at least one processor is further configured to: during the registration of the UE with the CN node, receive the UE's positioning capabilities from the UE via the external interface, wherein the positioning capabilities include an indication that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both; the positioning capabilities of the UE are included in a second request for periodic or triggered positioning sent to the positioning server, wherein the positioning server, in response to receiving the indication that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both, includes an indication that the UE can report detected periodic or triggered events using a request for early connection release or a request for immediate connection release, or both.

[0345] Some implementations (38) of the aforementioned CN node (36) may exist, wherein the standard includes at least one of the following: using a request for immediate connection release when the UE is idle and the UE does not expect a response from the location server; using a request for early connection release when the UE is idle and the UE expects a response from the location server; using a non-access stratum (NAS) signaling connection in other cases or after a threshold time period or a threshold number of event reports have been used for the request for early connection release or the request for immediate connection release; or a combination of the above.

[0346] One implementation (39) may be a method for supporting periodic and triggered location of a user equipment (UE) performed by a radio access network (RAN) node, the method comprising: receiving a request for periodic or triggered location from a location server and sending the request for the periodic or triggered location to the UE, the request including an indication that the UE may report a detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both; receiving a response from the UE and sending the response to the location server, the response confirming the periodic or triggered location; receiving a request for a signaling connection from the UE, wherein the signaling connection does not include a signaling connection to a core network (CN) node; and providing the signaling to the UE. The system connects to the UE and receives a first message, wherein the first message includes a Release Assistance Indication (RAI), wherein the first message includes a Non-Access Stratum (NAS) transport message, the NAS transport message including a routing identifier identifying the location server and an event report message, the event report message including an event message obtained by the UE after detecting a periodic or triggered event, the event information including at least one of location measurement, location estimation, the type of the detected triggered event, or a combination thereof; sends the NAS transport message and the RAI to the CN node, wherein the CN node forwards the event report message and the RAI to the location server; and sends a second message to the UE, wherein the second message releases the signaling connection to the RAN node.

[0347] Some implementations (40) of the above method (39) may exist, wherein the event reporting message includes a location protocol message, a supplemental service protocol message, or both.

[0348] Some implementations (41) of the above method (39) may exist, wherein the RAN node is a new radio (NR) node B (gNB) or a next-generation evolution node B (ng-eNB), wherein the CN node is an access and mobility management function (AMF), and wherein the location server is a location management function (LMF).

[0349] Some implementations (42) of the above method (41) may exist, wherein the first message is a Radio Resource Control Early Data Transmission (EDT) request or an RRC Early Data Request, and the second message is an RRC EDT completion message or an RRC Early Data Completion message.

[0350] Some implementations (43) of the above method (39) may exist, wherein the RAI includes a request for immediate connection release or a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the location server or an indication that the UE expects a response message from the location server.

[0351] Some implementations (44) of the above method (39) may exist, wherein the RAI includes an indication of early data transmission.

[0352] Some implementations (45) of the above method (39) may exist, wherein the RAI includes an access layer (AS) RAI or a NAS RAI, wherein the AS RAI is included in the first message but not in the NAS transport message, wherein the NAS RAI is included in the NAS transport message.

[0353] Some implementations (46) of the above method (43) may exist, wherein the RAI includes a request for immediate connection release, wherein the RAN node sends the second message to the UE in response to the request for immediate connection release.

[0354] Some implementations (47) of the above method (43) may exist, wherein the RAI includes a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the positioning server, wherein the RAN node sends the second message to the UE in response to receiving the request for connection release from the CN node.

[0355] Some implementations (48) of the above method (43) may exist, wherein the RAI includes a request for early connection release, wherein the request for early connection release includes an indication that the UE expects a response message from the positioning server, and the method further includes: receiving a third message from the CN node, the third message containing a NAS transmission message, the NAS transmission message containing an event report confirmation message, the event report confirmation message being sent by the positioning server to the CN node in response to the event report message; and sending a fourth message to the UE, the fourth message containing the NAS transmission message.

[0356] Some implementations (49) of the above method (48) may exist, wherein the RAN node sends the second message after the fourth message, or wherein the second message includes the fourth message.

[0357] Some implementations (50) of the above method (48) may exist, wherein the event report confirmation message includes confirmation of the event report message.

[0358] Some implementations (51) of the above method (39) may exist, wherein the request for periodic or triggered location includes a criterion for reporting the detected periodic or triggered event using a request for early connection release or a request for immediate connection release or both.

[0359] Some implementations (52) of the above method (39) may exist, further including: receiving a request for the positioning capability of the UE from the positioning server via the CN node, and sending the request for the positioning capability to the UE; and receiving a response from the UE including the positioning capability of the UE, and sending the response to the positioning server via the CN node, wherein the positioning capability includes an indication that the UE supports using a request for early connection release or a request for immediate connection release or both to report periodic and triggering events, wherein the positioning server, in response to receiving the indication that the UE supports using a request for early connection release or a request for immediate connection release or both to report periodic and triggering events, includes an indication that the UE can use a request for early connection release or a request for immediate connection release or both to report detected periodic or triggering events.

[0360] Some implementations (53) of the above method (51) may exist, wherein the standard includes at least one of the following: using a request for immediate connection release when the UE is idle and the UE does not expect a response from the location server; using a request for early connection release when the UE is idle and the UE expects a response from the location server; using a non-access stratum (NAS) signaling connection in other cases or after a threshold time period or a threshold number of event reports have been used for the request for early connection release or the request for immediate connection release; or a combination of the above.

[0361] One implementation (54) may be a radio access network (RAN) node for supporting periodic and triggered location of a user equipment (UE), comprising: an external interface configured to communicate with a wireless network; and at least one processor coupled to the external interface and configured to: receive a request for periodic or triggered location from a location server via the external interface, and send the request for periodic or triggered location to the UE, the request including indications that the UE may report a detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both; receive a response from the UE via the external interface and send the response to the location server, the response confirming the periodic or triggered location; and receive a request for a signaling connection from the UE via the external interface, wherein the signaling connection does not include access to the core network (C). The signaling connection to the RAN node is established via the external interface; the signaling connection is provided to the UE via the external interface; a first message is received from the UE via the external interface, wherein the first message includes a Release Assistance Indication (RAI), wherein the first message includes a Non-Access Stratum (NAS) transport message, the NAS transport message including a routing identifier identifying the location server and an event report message, the event report message including an event message obtained by the UE after detecting a periodic or triggered event, the event information including at least one of location measurement, location estimation, the type of detected triggered event, or a combination thereof; the NAS transport message and the RAI are sent to the CN node via the external interface, wherein the CN node forwards the event report message and the RAI to the location server; and a second message is sent to the UE via the external interface, wherein the second message releases the signaling connection to the RAN node.

[0362] Some implementations (55) of the aforementioned RAN node (54) may exist, wherein the event reporting message includes a location protocol message, a supplemental service protocol message, or both.

[0363] Some implementations (56) of the above-mentioned RAN node (54) may exist, wherein the RAN node is a new radio (NR) node B (gNB) or a next-generation evolution node B (ng-eNB), wherein the CN node is an access and mobility management function (AMF), and wherein the location server is a location management function (LMF).

[0364] Some implementations (57) of the above-mentioned RAN node (56) may exist, wherein the first message is a Radio Resource Control Early Data Transmission (EDT) request or an RRC Early Data Request, and wherein the second message is an RRC EDT completion message or an RRC Early Data Completion message.

[0365] Some implementations (58) of the aforementioned RAN node (54) may exist, wherein the RAI includes a request for immediate connection release or a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the location server or an indication that the UE expects a response message from the location server.

[0366] Some implementations (59) of the aforementioned RAN node (54) may exist, wherein the RAI includes an indication of early data transmission.

[0367] Some implementations (60) of the above-mentioned RAN node (54) may exist, wherein the RAI includes an access layer (AS) RAI or a NAS RAI, wherein the AS RAI is included in the first message but not in the NAS transport message, wherein the NAS RAI is included in the NAS transport message.

[0368] Some implementations (61) of the aforementioned RAN node (58) may exist, wherein the RAI includes a request for immediate connection release, wherein the RAN node sends the second message to the UE in response to the request for immediate connection release.

[0369] Some implementations (62) of the aforementioned RAN node (58) may exist, wherein the RAI includes a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the location server, wherein the RAN node sends the second message to the UE in response to receiving the request for connection release from the CN node.

[0370] Some implementations (63) of the aforementioned RAN node (58) may exist, wherein the RAI includes a request for early connection release, wherein the request for early connection release includes an indication that the UE expects a response message from the positioning server, wherein the at least one processor is further configured to: receive a third message from the CN node via the external interface, the third message containing a NAS transmission message, the NAS transmission message containing an event report confirmation message, the event report confirmation message being sent by the positioning server to the CN node in response to the event report message; and send a fourth message to the UE via the external interface, the fourth message containing the NAS transmission message.

[0371] Some implementations (64) of the above-mentioned RAN node (63) may exist, wherein the RAN node sends the second message after the fourth message, or wherein the second message includes the fourth message.

[0372] Some implementations (65) of the above-mentioned RAN node (63) may exist, wherein the event report confirmation message includes confirmation of the event report message.

[0373] Some implementations (66) of the aforementioned RAN node (54) may exist, wherein the request for periodic or triggered location includes a criterion for reporting detected periodic or triggered events using a request for early connection release or a request for immediate connection release or both.

[0374] Some implementations (67) of the aforementioned RAN node (54) may exist, wherein the at least one processor is further configured to: receive a request for the positioning capability of the UE from the positioning server via the CN node through the external interface, and send the request for the positioning capability to the UE; and receive a response including the positioning capability of the UE from the UE via the external interface, and send the response to the positioning server through the CN node, wherein the positioning capability includes an indication that the UE supports reporting periodic and triggering events using a request for early connection release or a request for immediate connection release or both, wherein the positioning server, in response to receiving the indication that the UE supports reporting periodic and triggering events using a request for early connection release or a request for immediate connection release or both, includes an indication that the UE can report detected periodic or triggering events using a request for early connection release or a request for immediate connection release or both.

[0375] Some implementations (68) of the RAN node (66) described above may exist, wherein the criteria include at least one of the following: using a request for immediate connection release when the UE is idle and the UE does not expect a response from the location server; using a request for early connection release when the UE is idle and the UE expects a response from the location server; using non-access stratum (NAS) signaling connection in other cases or after a threshold time period or a threshold number of event reports have been used for the request for early connection release or the request for immediate connection release; or a combination of the above.

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

Claims

1. A method for supporting periodicity and triggering positioning of a user equipment (UE), performed by the user equipment (UE), the method comprising: Receive requests for periodic or triggered location services from the location server; Send a response to the location server, the response confirming the periodic or triggered location; Detect periodic or triggered events; Obtain event information, which includes at least one of location measurement, location estimation, the type of detected triggering event, or a combination thereof; Obtaining a signaling connection to a Radio Access Network (RAN) node, wherein the signaling connection does not include a signaling connection to a Core Network (CN) node; and A first message is sent to the RAN node, wherein the first message contains a Non-Access Stratum (NAS) message, the NAS message containing a routing identifier that identifies the location server and an event report message containing the event information, wherein the RAN node forwards the NAS message to the CN node, and wherein the CN node forwards the event report message to the location server.

2. The method according to claim 1, further comprising: The first message includes a Release Assist Instruction (RAI), wherein the RAN node forwards the NAS message and the RAI to the CN node, and the CN node forwards the event report message and the RAI to the positioning server.

3. The method according to claim 1, wherein, The event reporting message may include a location protocol message, a supplemental service protocol message, or both.

4. The method according to claim 1, wherein, The RAN node is a New Radio (NR) Node B (gNB) or a Next Generation Evolution Node B (ng-eNB), wherein the CN node is an Access and Mobility Management Function (AMF), and wherein the Location Server is a Location Management Function (LMF).

5. The method according to claim 4, wherein, The first message is a Radio Resource Control (RRC) Early Data Transmission (EDT) Request or an RRC Early Data Request.

6. The method according to claim 2, wherein, The RAI includes a request for immediate connection release or a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the location server or an indication that the UE expects a response message from the location server.

7. The method according to claim 2, wherein, The RAI includes an indication of early data transmission.

8. The method according to claim 2, wherein, The RAI includes an Access Layer (AS) RAI or a NAS RAI, wherein the AS RAI is included in the first message but not in the NAS message, and the NAS RAI is included in the NAS message.

9. The method according to claim 6, wherein, The RAI includes a request for immediate connection release, wherein the RAN node sends a second message to the UE in response to the request for immediate connection release.

10. The method according to claim 6, wherein, The RAI includes a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the location server, wherein the RAN node sends a second message to the UE in response to receiving the connection release request from the CN node.

11. The method according to claim 9 or 10, wherein, The second message is a Radio Resource Control (RRC) Early Data Transmission (EDT) Completion Message or an RRC Early Data Completion Message.

12. The method according to claim 6, wherein, The RAI includes a request for early connection release, wherein the request for early connection release includes an indication that the UE expects a response message from the location server, and further includes: A second message is received from the RAN node. The second message contains a NAS message, which contains an event report confirmation message sent by the positioning server in response to the event report message.

13. The method according to claim 12, wherein, The event report confirmation message includes confirmation of the event report message.

14. The method according to claim 1, wherein, The request for periodic or triggered location includes an indication that the UE can report the detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both.

15. The method according to claim 14, wherein, The request for periodic or triggered location includes criteria for reporting detected periodic or triggered events, wherein the criteria include a threshold time period or a threshold number of consecutive event reports.

16. The method of claim 14, further comprising: Receive a request for the UE's positioning capabilities from the positioning server; as well as A response including the positioning capabilities of the UE is sent to the positioning server, wherein the positioning capabilities include an indication that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both, wherein the positioning server responds to receiving the indication that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both, and includes an indication that the UE can report detected periodic or triggered events using a request for early connection release or a request for immediate connection release, or both.

17. A user equipment (UE) capable of supporting periodic and triggered positioning, the UE comprising: At least one wireless transceiver is configured to communicate wirelessly with at least one wireless network; At least one memory; as well as At least one processor, coupled to the at least one wireless transceiver and the at least one memory, and configured to: Receive a request for periodic or triggered location from the location server via the at least one wireless transceiver; A response is sent to the location server via the at least one wireless transceiver, the response confirming the periodic or triggered location; Detect periodic or triggered events; Obtain event information, which includes at least one of location measurement, location estimation, the type of detected triggering event, or a combination thereof; Obtaining a signaling connection to a Radio Access Network (RAN) node, wherein the signaling connection does not include a signaling connection to a Core Network (CN) node; and A first message is sent to the RAN node via the at least one wireless transceiver, wherein the first message includes a Non-Access Stratum (NAS) message, the NAS message including a routing identifier identifying the location server and an event report message including the event information, wherein the RAN node forwards the NAS message to the CN node, and wherein the CN node forwards the event report message to the location server.

18. The UE according to claim 17, wherein, The at least one processor is further configured to include a Release Assist Indication (RAI) in the first message, wherein the RAN node forwards the NAS message and the RAI to the CN node, and wherein the CN node forwards the event report message and the RAI to the positioning server.

19. The UE according to claim 17, wherein, The event reporting message may include a location protocol message, a supplemental service protocol message, or both.

20. The UE according to claim 17, wherein, The RAN node is a New Radio (NR) Node B (gNB) or a Next Generation Evolution Node B (ng-eNB), wherein the CN node is an Access and Mobility Management Function (AMF), and wherein the Location Server is a Location Management Function (LMF).

21. The UE according to claim 20, wherein, The first message is a Radio Resource Control (RRC) Early Data Transmission (EDT) Request or an RRC Early Data Request.

22. The UE according to claim 18, wherein, The RAI includes a request for immediate connection release or a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the location server or an indication that the UE expects a response message from the location server.

23. The UE according to claim 18, wherein, The RAI includes an indication of early data transmission.

24. The UE according to claim 18, wherein, The RAI includes an Access Layer (AS) RAI or a NAS RAI, wherein the AS RAI is included in the first message but not in the NAS message, and the NAS RAI is included in the NAS message.

25. The UE according to claim 22, wherein, The RAI includes a request for immediate connection release, wherein the RAN node sends a second message to the UE in response to the request for immediate connection release.

26. The UE according to claim 22, wherein, The RAI includes a request for early connection release, wherein the request for early connection release includes an indication that the UE does not expect a response message from the location server, wherein the RAN node sends a second message to the UE in response to receiving the connection release request from the CN node.

27. The UE according to claim 22, wherein, The RAI includes a request for early connection release, wherein the request for early connection release includes an indication that the UE expects a response message from the location server, and wherein the at least one processor is further configured to: A second message is received from the RAN node via the at least one wireless transceiver. The second message contains a NAS message, which includes an event report confirmation message sent by the positioning server in response to the event report message.

28. The UE according to claim 27, wherein, The event report confirmation message includes confirmation of the event report message.

29. The UE according to claim 17, wherein, The request for periodic or triggered location includes an indication that the UE can report the detected periodic or triggered event using a request for early connection release, a request for immediate connection release, or both.

30. The UE according to claim 29, wherein, The request for periodic or triggered location includes criteria for reporting detected periodic or triggered events, wherein the criteria include a threshold time period or a threshold number of consecutive event reports.

31. The UE according to claim 29, wherein, The at least one processor is further configured to: The UE receives a request for location capability from the location server via the at least one wireless transceiver. as well as The location server sends a response via the at least one wireless transceiver to the location server, including the location capabilities of the UE, wherein the location capabilities include an indication that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both, wherein the location server responds to receiving the indication that the UE supports reporting periodic and triggered events using a request for early connection release or a request for immediate connection release, or both, and includes an indication that the UE can report detected periodic or triggered events using a request for early connection release or a request for immediate connection release, or both.

32. A user equipment (UE) capable of supporting periodic and triggered positioning, the UE comprising: A component used to receive requests for periodic or triggered location from a location server; A component for sending a response to the location server, the response confirming the periodic or triggered location; Components used to detect periodic or triggered events; A component for obtaining event information, the event information including at least one of location measurement, location estimation, type of detected triggering event, or a combination thereof; Components for obtaining a signaling connection to a Radio Access Network (RAN) node, wherein the signaling connection does not include a signaling connection to a Core Network (CN) node; and A component for sending a first message to the RAN node, wherein the first message includes a Non-Access Stratum (NAS) message, the NAS message including a routing identifier identifying the location server and an event report message including the event information, wherein the RAN node forwards the NAS message to the CN node, and wherein the CN node forwards the event report message to the location server.

33. A non-transitory computer-readable medium having program code stored thereon, the program code being operable to configure at least one processor in a user equipment (UE) capable of supporting periodic and triggered positioning, the program code comprising: Program code used to receive requests for periodic or triggered location from a location server; Program code used to send a response to the location server, the response confirming the periodic or triggered location; Program code used to detect periodic or triggered events; Program code for obtaining event information, the event information including at least one of location measurement, location estimation, type of detected triggering event, or a combination thereof; Program code for obtaining a signaling connection to a Radio Access Network (RAN) node, wherein the signaling connection does not include a signaling connection to a Core Network (CN) node; and Program code for sending a first message to the RAN node, wherein the first message includes a Non-Access Stratum (NAS) message, the NAS message including a routing identifier identifying the location server and an event report message including the event information, wherein the RAN node forwards the NAS message to the CN node, and wherein the CN node forwards the event report message to the location server.

Images