Method, central unit and medium for location session
By introducing position management components (LMC) into the gNB of the 5G wireless communication system and using Xn, NG and F1 interfaces for position signaling transmission, the problems of large signaling volume and high delay in the prior art are solved, and mobile devices are improved Positioning accuracy and reliability.
Patent Information
- Application Number
- CN202411227090.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2020-08-13
- Filing Date
- 2020-08-14
- Publication Date
- 2024-11-01
AI Technical Summary
When the existing 5G wireless communication system acquires the location of the mobile device, the signaling volume is large, the delay is high, and the accuracy is low. Especially when the device is switched, the positioning architecture is difficult to effectively support, which affects the quality of the positioning service.
Introduce the location management component (LMC) in gNB, connect it to the gNB-CU, perform position-related signaling transmission through Xn, NG and F1 interfaces, reduce signaling delay of the core network, and perform UE's Location session switching ensures continuity of location services.
It reduces signaling delay and resource use, improves the accuracy and reliability of positioning, especially when switching devices, and improves the positioning service quality of 5G wireless communication systems.
Smart Images

Figure FT_1 
Figure FT_2 
Figure FT_3
Abstract
Description
[0001] This application is a divisional application of the invention patent application with the application date of August 14, 2020, application number 202080056987.2, and invention name “System and method for 5G location session switching for NG-RAN location management component”.
[0002] CROSS-REFERENCE TO RELATED APPLICATIONS
[0003] This application claims the benefit of U.S. Provisional Application No. 62 / 886,829, filed on August 14, 2019, entitled “HANDOVER OF 5G LOCATION SESSIONS FOR AN NG-RAN LOCATION MANAGEMENT COMPONENT,” and U.S. Non-Provisional Application No. 16 / 993,142, filed on August 13, 2020, entitled “SYSTEMS AND METHODS FOR HANDOVER OF 5G LOCATION SESSIONS FOR AN NG-RAN LOCATION MANAGEMENT COMPONENT,” both of which are assigned to the present assignee and are expressly incorporated herein by reference in their entireties. Technical Field
[0004] Aspects of the present disclosure relate to an architecture supporting UE positioning services in 5G NG-RAN. Background Art
[0005] Wireless communication systems have evolved through different generations, including first generation analog wireless phone service (1G), second generation (2G) digital wireless phone service (including temporary 2.5G and 2.75G networks), third generation (3G) high-speed data, Internet-enabled wireless service, and fourth generation (4G) service (e.g., LTE or WiMax). The fifth generation (5G) mobile standard calls for higher data transmission speeds, a greater number of connections, and better coverage, among other improvements. The 5G standard according to the Next Generation Mobile Networks Alliance is designed to provide data rates of tens of megabits per second to each of tens of thousands of users and 1 gigabit per second to dozens of employees in an office.
[0006] Obtaining the location of a mobile device that is accessing a wireless (e.g., 5G) network may be useful for many applications, including, for example, emergency calls, personal navigation, asset tracking, locating friends or family members, etc. However, the location of the mobile device may require the implementation of one or more positioning methods, which may require the support of multiple elements in the wireless network and the mobile device. This may result in a large amount of signaling caused by the interaction between multiple elements in the wireless network when obtaining the location of the wireless device, which may increase latency, reduce accuracy, and / or increase resource usage when obtaining the location of the mobile device. Therefore, it may be desirable to improve the architecture that supports different positioning methods to reduce the amount of signaling and other resource usage, thereby achieving lower latency and / or higher accuracy. If a handover of the mobile device occurs when locating the mobile device, and if certain elements in the wireless network cannot support the positioning of the mobile device after the handover, some architectural enhancements may be sensitive to the handover of the mobile device. In this case, additional enhancements may help to better achieve the positioning of the mobile device during and after the handover. Summary of the invention
[0007] A simplified summary related to one or more aspects disclosed herein is presented below. Therefore, the following summary should not be considered as a broad overview related to all expected aspects, nor should it be considered that the following summary is to determine the key or key elements related to all expected aspects, or to delineate the scope related to any particular aspect. Therefore, the sole purpose of the following summary is to present certain concepts related to one or more aspects of the mechanism disclosed herein in a simplified form before the detailed description presented below.
[0008] The RAN location server function, called the Location Management Component (LMC), may be included in the gNB and connected to the gNB Central Unit (gNB-CU). The gNB-CU may initiate a location session for the UE, including selecting a first LMC for the location session. The gNB-CU may handover the UE to a new serving gNB. The LMC with which the UE is conducting the location session may remain unchanged after the handover, or may change to a new LMC to suit the new serving gNB.
[0009] In one embodiment, a method for supporting a location session of a user equipment (UE) performed by a first central unit (CU) in a first new radio (NR) Node B (gNB) in a radio access network (RAN) includes: receiving a first positioning message for the UE from a first entity; determining a first location management component (LMC); storing first information for the location session, the first information for the location session including an identifier of the first LMC, an identifier of the UE, and a first identifier of the location session; forwarding the first positioning message to the first LMC; and performing a handover of the UE to a second gNB, whereby the second gNB supports continuation of the location session.
[0010] In one embodiment, a first central unit (CU) in a first new radio (NR) Node B (gNB) in a radio access network (RAN) is configured to support a location session of a user equipment (UE), the first CU comprising: an external interface configured to communicate with one or more of an access and mobility management function (AMF), other gNBs in the RAN, other CUs in other gNBs, and location management components (LMCs) in other gNBs; an internal interface configured to communicate with the LMC in the first gNB, a distributed unit (DU) in the first gNB, and a transmit receive point (TRP) in the first gNB One or more of the above may communicate with each other, the sending and receiving point may include a receiving point (RP) and a sending point (TP); at least one memory; at least one processor, coupled to the external interface, the internal interface and the at least one memory, wherein the at least one processor is configured to: receive a first positioning message of the UE from the first entity; determine a first location management component (LMC); store first information of the location session, the first information of the location session including an identifier of the first LMC, an identifier of the UE and a first identifier of the location session; forward the first positioning message to the first LMC; and perform switching of the UE to the second gNB, whereby the second gNB supports the continuation of the location session.
[0011] In one embodiment, a first central unit (CU) in a first new radio (NR) node B (gNB) in a radio access network (RAN), the first CU being configured to support a location session for a user equipment (UE), the first CU comprising: a component for receiving a first positioning message for the UE from a first entity; a component for determining a first location management component (LMC); a component for storing first information for the location session, the first information for the location session comprising an identifier of the first LMC, an identifier of the UE, and a first identifier for the location session; a component for forwarding the first positioning message to the first LMC; and a component for performing a handover of the UE to a second gNB, whereby the second gNB supports continuation of the location session.
[0012] In one embodiment, a non-transitory storage medium including program code stored thereon, the program code being operable to cause at least one processor in a first central unit (CU) in a first new radio (NR) node B (gNB) in a radio access network (RAN) to support a location session for a user equipment (UE), comprising: program code to receive a first positioning message for the UE from a first entity; program code to determine a first location management component (LMC); program code to store first information for the location session, the first information for the location session including an identifier of the first LMC, an identifier of the UE, and a first identifier for the location session; program code to forward the first positioning message to the first LMC; and program code to perform a handover of the UE to a second gNB, whereby the second gNB supports continuation of the location session.
[0013] In one embodiment, a method for continuing a location session of a user equipment (UE) performed by a first central unit (CU) in a first new radio (NR) node B (gNB) in a radio access network (RAN) includes: receiving a first handover request message of the UE from a second gNB, the first handover request message including first information of the location session, the first information of the location session including an identifier of a first location management component (LMC), an identifier of the UE, and a first identifier of the location session; storing second information of the location session, the second information of the location session including at least a portion of the first information of the location session; completing handover of the UE from the second gNB to the first gNB; determining a second LMC, wherein the second LMC is the first LMC or is different from the first LMC; when the second LMC is different from the first LMC, including the identifier of the second LMC in the second information of the location session; and sending a first location session update message to the first gNB, when the second LMC is different from the first LMC, the first location session update message including the identifier of the second gNB and the identifier of the second LMC.
[0014] In one embodiment, a first central unit (CU) in a first new radio (NR) node B (gNB) in a radio access network (RAN) is configured to continue a location session of a user equipment (UE), the first CU comprising: an external interface configured to communicate with one or more of an access and mobility management function (AMF), other gNBs in the RAN, other CUs in other gNBs, and location management components (LMCs) in other gNBs; an internal interface configured to communicate with one or more of the LMC in the first gNB, a distributed unit (DU) in the first gNB, and a transmit receive point (TRP) in the first gNB, the transmit receive point may include a receive point (RP) and a transmit point (TP); at least one memory; and at least one processor coupled to the external interface, the internal interface, and the at least one memory, wherein the at least one processor The device is configured to: receive a first handover request message of a UE from a second gNB via an external interface, the first handover request message including first information of a location session, the first information of the location session including an identifier of a first location management component (LMC), an identifier of the UE and a first identifier of the location session; store second information of the location session, the second information of the location session including at least a part of the first information of the location session; complete handover of the UE from the second gNB to the first gNB; determine a second LMC, wherein the second LMC is the first LMC or is different from the first LMC; when the second LMC is different from the first LMC, include the identifier of the second LMC in the second information of the location session; and send a first location session update message to the first gNB via an internal interface, when the second LMC is different from the first LMC, the first location session update message includes the identifier of the second gNB and the identifier of the second LMC.
[0015] In one embodiment, a first central unit (CU) in a first new radio (NR) node B (gNB) in a radio access network (RAN) is configured to continue a location session of a user equipment (UE), the first CU comprising: a component for receiving a first handover request message of the UE from a second gNB, the first handover request message comprising first information of the location session, the first information of the location session comprising an identifier of a first location management component (LMC), an identifier of the UE and a first identifier of the location session; a component for storing second information of the location session, the second information of the location session comprising at least a portion of the first information of the location session; a component for completing a handover of the UE from the second gNB to the first gNB; a component for determining a second LMC, wherein the second LMC is the first LMC or is different from the first LMC; a component for including the identifier of the second LMC in the second information of the location session when the second LMC is different from the first LMC; and a component for sending a first location session update message to the first gNB, wherein the first location session update message comprises the identifier of the second gNB and the identifier of the second LMC when the second LMC is different from the first LMC.
[0016] In one embodiment, a non-transitory storage medium including program code stored thereon, the program code being operable to cause at least one processor in a first central unit (CU) in a first new radio (NR) node B (gNB) in a radio access network (RAN) to be configured to continue a location session of a user equipment (UE), including: program code for receiving a first handover request message for the UE from a second gNB, the first handover request message including first information for the location session, the first information for the location session including an identifier of a first location management component (LMC), an identifier of the UE, and a first identifier for the location session; program code for storing second information for the location session, the second information for the location session including at least a portion of the first information for the location session; program code for completing handover of the UE from the second gNB to the first gNB; program code for determining a second LMC, wherein the second LMC is the first LMC or is different from the first LMC; program code for including the identifier of the second LMC in the second information for the location session when the second LMC is different from the first LMC; and program code for sending a first location session update message to the first gNB, wherein the first location session update message includes the identifier of the second gNB and the identifier of the second LMC when the second LMC is different from the first LMC.
[0017] In one embodiment, a method for supporting a location session of a user equipment (UE) performed by a first location management component (LMC) in a first new radio (NR) node B (gNB) in a radio access network (RAN), comprises: receiving a first positioning message for the UE from a first entity, the first positioning message being relayed by a central unit (CU) of the first gNB to a first LMC, the first positioning message initiating a location session for the UE in the first LMC, the first positioning message including an identifier of a source gNB, the source gNB serving the UE, and an identifier of the location session; sending at least one positioning message for the UE to a second entity; receiving a location session update message indicating a handover of the UE from the source gNB to a target gNB, the location session update message indicating whether a second LMC is allocated, the location session update message including an identifier of the second LMC when the second LMC is allocated; when the second LMC is not allocated, continuing to support the location session using the target gNB; and when the second LMC is allocated, sending a location session transfer message to the second LMC, the location session transfer message including a current state of the location session and the first positioning message.
[0018] In one embodiment, a first location management component (LMC) in a first new radio (NR) node B (gNB) in a radio access network (RAN) is configured to support a location session of a user equipment (UE), the first LMC comprising a communication interface, the communication interface comprising one or more of an external interface and an internal interface, the communication interface configured to communicate with a central unit (CU); at least one memory; at least one processor coupled to the communication interface and the at least one memory, wherein the at least one processor is configured to: receive a first positioning message of the UE from a first entity, the first positioning message being relayed by the central unit (CU) of the first gNB to the first LMC, the first positioning message being in the first LMC Initiate a location session of the UE, the first positioning message including the identifier of the source gNB, the source gNB serving the UE and the identifier of the location session; send at least one positioning message of the UE to the second entity; receive a location session update message, the location session update message indicates the switching of the UE from the source gNB to the target gNB, the location session update message indicates whether the second LMC is allocated, the location session update message includes the identifier of the second LMC when the second LMC is allocated; when the second LMC is not allocated, continue to support the location session using the target gNB; and when the second LMC is allocated, send a location session transfer message to the second LMC, the location session transfer message includes the current state of the location session and the first positioning message.
[0019] In one embodiment, a first location management component (LMC) in a first new radio (NR) node B (gNB) in a radio access network (RAN) is configured to support a location session for a user equipment (UE), the first LMC comprising a component for receiving a first positioning message for the UE from a first entity, the first positioning message being relayed by a central unit (CU) of the first gNB to the first LMC, the first positioning message initiating a location session for the UE in the first LMC, the first positioning message comprising an identifier of a source gNB, the source gNB serving the UE, and an identifier of the location session; a component for sending at least one positioning message for the UE to a second entity; a component for receiving a location session update message indicating a handover of the UE from the source gNB to a target gNB, the location session update message indicating whether a second LMC is allocated, the location session update message comprising an identifier of the second LMC when the second LMC is allocated; a component for continuing to support the location session using the target gNB when the second LMC is not allocated; and a component for sending a location session transfer message to the second LMC when the second LMC is allocated, the location session transfer message comprising a current state of the location session and the first positioning message.
[0020] In one embodiment, a non-transitory storage medium including program code stored thereon, the program code being operable to cause at least one processor in a first location management component (LMC) in a first new radio (NR) Node B (gNB) in a radio access network (RAN) to be configured to support a location session for a user equipment (UE), comprising: program code to receive a first positioning message for the UE from a first entity, the first positioning message being relayed by a central unit (CU) of the first gNB to the first LMC, the first positioning message initiating a location session for the UE in the first LMC, the first positioning message including an identity of a source gNB, a source gNB serving the UE, and a location session for the UE. and an identifier of the location session; program code for sending at least one positioning message of the UE to the second entity; program code for receiving a location session update message, the location session update message indicating the switching of the UE from the source gNB to the target gNB, the location session update message indicating whether a second LMC is allocated, the location session update message including the identifier of the second LMC when the second LMC is allocated; program code for continuing to support the location session using the target gNB when the second LMC is not allocated; and program code for sending a location session transfer message to the second LMC when the second LMC is allocated, the location session transfer message including the current state of the location session and the first positioning message.
[0021] Other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] The accompanying drawings are presented to aid in describing various aspects of the disclosure and are provided solely for illustration of these aspects and not limitation of these aspects.
[0023] Figure 1 A wireless communication system including a next generation (NG) radio access network is shown.
[0024] Figure 2 An extended architecture diagram of a NG-RAN node including a Location Management Component (LMC) is shown.
[0025] Figure 3 FIG. 2 is an enhanced location reporting procedure showing the signaling between the AMF and NG-RAN nodes.
[0026] Figure 4 is another enhanced position reporting process.
[0027] Figure 5 LPP signaling between the LMC in the gNB and the UE is shown.
[0028] Figure 6 Supplementary Service (SS) signaling between the LMC in the gNB and the UE is shown.
[0029] Figure 7 Various signaling between gNB / LMC and individual gNB / LMC are shown.
[0030] Figure 8 Various signaling between gNB-CU (Central Unit) and LMC are shown.
[0031] Fig. 9 Various signaling between gNB-CU and gNB-DU / TRP (Distributed Unit / Transmit Receiving Point) are shown.
[0032] Fig.10 A signaling example is shown when the LMC in the serving gNB for the target UE requests uplink (UL) position measurements from the gNB-DU / TRP in the neighboring gNB.
[0033] Fig.11 The MT-LR procedure for determining the UE location using the LMC in the NG-RAN is shown.
[0034] Fig.12 The NI-LR procedure for determining the UE location using the LMC in NG-RAN is shown.
[0035] Fig.13 The UE positioning process is shown.
[0036] Fig.14A RAN initiated location request (RI-LR) procedure for determining the UE location is shown.
[0037] Fig.15 The 5GCN MO-LR procedure with LMC in NG-RAN is shown.
[0038] Fig.16 Shown is the delayed MT-LR with periodic, triggered and UE available location events with LMC in NG-RAN.
[0039] Fig.17 The procedures for supporting the mobility of the UE are shown for MO-LR (Mobile Originated Location Request), MT-LR (Mobile Terminated Location Request) or NI-LR (Network Induced Location Request) procedures.
[0040] Figure 18 includes Fig.18A and Fig.18B , showing the process of supporting the mobility of UE 102 by periodic or triggered MT-LR.
[0041] Fig.19 A process is shown in which LMC and LMF coexist and AMF determines a suitable LMF or LMC for position estimation of the target UE or for providing assistance data to the target UE.
[0042] FIG20 shows a process flow illustrating a method for supporting a location session of a UE performed by a source CU.
[0043] FIG. 21 shows a process flow illustrating a method for supporting a location session of a UE performed by a target CU.
[0044] FIG. 22 shows a process flow illustrating a method for supporting a location session of a UE performed by a source or target LMC.
[0045] FIG. 23 is a diagram showing a hardware implementation of a source CU.
[0046] FIG. 24 is a diagram showing a hardware implementation of a target CU.
[0047] FIG. 25 is a diagram showing a hardware implementation of a source or target LMC.
[0048] Elements with the same reference numeral in different figures may correspond to each other (e.g., may be similar or identical to each other). In addition, some elements in the various figures are labeled using a numerical prefix followed by a letter or a numerical suffix. Elements with the same numerical prefix but different suffixes may be different instances of the same type of element. A numerical prefix without any suffix is used herein to refer to any element with the numerical prefix. For example, Figure 1Different instances of gNB 110-1 and 110-2 are shown in FIG. Reference to gNB 110 may then refer to either of gNBs 110-1 and 110-2. DETAILED DESCRIPTION
[0049] In the technical specification (TSS) of the 3rd Generation Partnership Project (3GPP), a location server (location management function (LMF) may be located in the 5G core network (5GCN) and connected to the access and mobility management function (AMF). Then, location-related signaling between the LMF and the target device (UE) includes core network and radio access network (RAN) signaling. For example, a Long Term Evolution Positioning Protocol (LPP) message sent between the LMF and the UE may be transmitted over multiple interfaces including an interface between the LMF and the AMF, an interface between the AMF and the NG-RAN (e.g., gNB), and an air interface between the NG-RAN (e.g., gNB) and the UE. These interfaces may be control plane interfaces, user plane interfaces, or both. Each interface and intermediate node typically adds additional delay to the transmission of the LPP message.
[0050] To reduce signaling latency between the location server and the UE, the location server functionality (at least part of it) can be moved from the core network to the RAN. The location server functionality in the RAN can also reduce resource utilization (by reducing signaling) and increase location capacity by offloading location support to the LMF in the core network.
[0051] According to one embodiment, the RAN location server function (referred to herein as the location management component (LMC)) may be a separate component in a new radio (NR) Node B (gNB) connected to a gNB central unit (CU) referred to as a gNB-CU. The gNB-CU may receive location-related messages from a UE via a gNB distributed unit (gNB-DU), from another gNB-CU in a different gNB via an Xn interface between two gNBs, or from a core network entity (e.g., AMF) via a next generation (NG) interface. The location-related signaling may be transmitted in a container message of a corresponding application protocol. For example, the transmission may use: (i) a radio resource control (RRC) container for LPP messages transmitted over an air interface; (ii) a next generation application protocol (NGAP) container for location-related messages transmitted over an NG interface between an AMF and a gNB (or other NG-RAN node); and (iii) an Xn application protocol (XnAP) container for location-related messages transmitted over an Xn interface between two NG-RAN nodes (e.g., 2 gNBs). The gNB-CU in the target gNB may then forward each of these containers to the LMC in the gNB using an F1 Application Protocol (F1-AP) container message. Similarly, for location-related messages sent from the LMC to a UE or another gNB or core network entity (e.g., AMF), the LMC may send the location-related message to the gNB-CU within the corresponding F1AP message container for distribution to UEs, other gNBs, gNB-DUs, or core network entities.
[0052] The architecture and other aspects disclosed in the following description and related drawings are directed to specific aspects of the present disclosure. Alternative aspects may be designed without departing from the scope of the present disclosure. In addition, well-known elements of the present disclosure are not described in detail or are omitted so as not to obscure the relevant details of the present disclosure.
[0053] The words "exemplary" and / or "example" are used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" and / or "example" is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term "aspects of the disclosure" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation.
[0054] In addition, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It should be appreciated that the various actions described herein may be performed by specific circuits (e.g., application specific integrated circuits (ASICs)), by program instructions executed by one or more processors, or by a combination of both. In addition, the (multiple) sequences of actions described herein may be considered to be fully embodied in any form of a non-transitory computer-readable storage medium having a corresponding set of computer instructions stored therein, which, when executed, will cause or instruct the associated processor of the device to perform the functions described herein. Therefore, various aspects of the present disclosure may be embodied in a variety of different forms, all of which are contemplated to be within the scope of the claimed subject matter. In addition, for each of the various aspects described herein, the corresponding form of any such aspect may be described herein as, for example, "logically configured to" perform the described actions.
[0055] A mobile device, also referred to herein as a UE, may be mobile or may be stationary (e.g., at certain moments) and may communicate with a radio access network (RAN). As used herein, the term "UE" may be interchangeably referred to as an "access terminal" or "AT," "client device," "wireless device," "subscriber equipment," "subscriber terminal," "subscriber station," "user terminal" or UT, "mobile terminal," "mobile device," "mobile station," or variations thereof. Typically, a UE may communicate with a core network via the RAN, and through the core network the UE may connect to external networks such as the Internet and other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through a wired access network, a WLAN network (e.g., based on IEEE 802.11, etc.), and the like. A UE may be embodied by any of a variety of types of devices including, but not limited to, a printed circuit (PC) card, a compact flash device, an external or internal modem, a wireless or wired phone, a smart phone, a tablet, a tracking device, an asset tag, and the like. The communication link through which a UE may send a signal to the RAN is referred to as an uplink channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, and the like). The communication link through which the RAN can send signals to the UE is called a downlink or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term traffic channel (TCH) can refer to an uplink / reverse or downlink / forward traffic channel.
[0056] Figure 1 A positioning architecture diagram of a communication system 100 including support for location management functions in NG-RAN is shown. The "location management function in NG-RAN" is referred to herein as the "location management component (LMC)" and is located in Figure 1 In one or more gNBs 110.
[0057] The communication system 100 may be configured to support positioning of a user equipment (UE) 102. Herein, the communication system 100 includes the UE 102, and components of a fifth generation (5G) network including a next generation (NG) radio access network (RAN) (NG-RAN) 135 and a 5G core network (5GCN) 140. The 5G network may also be referred to as a new radio (NR) network; the NG-RAN 135 may be referred to as a 5G RAN or NRRAN; and the 5GCN 140 may be referred to as an NG core network (NGC). The communication system 100 may further use information from a satellite vehicle (SV) 190 for a global navigation satellite system (GNSS) such as GPS, GLONASS, Galileo, or BeiDou, or some other local or regional satellite positioning system (SPS) such as IRNSS, EGNOS, or WAAS. Additional components of the communication system 100 are described below. The communication system 100 may include additional or alternative components.
[0058] It should be noted that Figure 1 Only a generalized illustration of the various components is provided, any or all of which may be utilized as appropriate, and each component may be repeated or omitted as desired. Specifically, although only one UE 102 is shown, it will be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the communication system 100. Similarly, the communication system 100 may include a greater (or smaller) number of SVs 190, gNBs 110, next generation evolved Node Bs (ng-eNBs) 114, AMFs 115, external clients 130, and / or other components. The illustrated connections connecting the various components in the communication system 100 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. In addition, components may be rearranged, combined, separated, replaced, and / or omitted, depending on the desired functionality.
[0059] Although Figure 1 A 5G-based network is shown, but similar network implementations and configurations may be used for other communication technologies, such as 3G, Long Term Evolution (LTE), etc. The implementations described herein, whether they are for 5G technology or for other communication technologies and protocols, may be used to configure, in response to receiving a request, an increased amount of location-related information or resources associated with a broadcast communication (e.g., a broadcast of assistance data) from a wireless node, the transmission of a positioning reference signal (PRS), or some other location-related function of the wireless node.
[0060] UE 102 may include and / or be referred to as a device, a mobile device, a wireless device, a mobile terminal, a terminal, a mobile station (MS), a terminal (SET) supporting secure user plane location (SUPL), or by some other name. In addition, UE 102 may correspond to a mobile phone, a smart phone, a laptop, a tablet, a PDA, a tracking device, a navigation device, an Internet of Things (IoT) device, or some other portable or portable device. Typically, although not necessarily, UE 102 may support wireless communications using one or more radio access technologies (RATs) such as using 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), Bluetooth® (BT), Worldwide Interoperability for Microwave Access (WiMAX), 5G New Radio (NR) (e.g., using NG-RAN 135 and 5GCN 140), etc. UE 102 may also support wireless communications using a wireless local area network (WLAN), which may be connected to other networks (e.g., the Internet) using, for example, a digital subscriber line (DSL) or packet cable. Using one or more of these RATs may allow UE 102 to communicate with external clients 130 (via Figure 1 Elements of the 5GCN 140 not shown in the figure, or possibly via a Gateway Mobile Location Center (GMLC) 125) and / or allowing external clients 130 to receive location information about the UE 102 (e.g., via the GMLC 125).
[0061] UE 102 may include a single entity, or may include multiple entities, such as in a personal area network where a user may use audio, video, and / or data I / O devices and / or body sensors and a separate wired or wireless modem. The estimate of the location of UE 102 may be referred to as a location, location estimate, location fix, fix, position fix, position estimate, or position fix, and may be geographic, providing location coordinates (e.g., latitude and longitude) for UE 102, which may or may not include an altitude component (e.g., height above sea level, height above the ground, floor, or basement, or depth below the ground, floor, or basement). Alternatively, the location of UE 102 may be expressed as a municipal location (e.g., as a postal address or a designation of a point or small area in a building such as a specific room or floor). The location of UE 102 may also be expressed as an area or volume (defined geographically or in municipal terms) in which UE 102 is expected to be located with a certain probability or confidence (e.g., 67%, 95%, etc.). The location of the UE 102 may also be a relative location including, for example, a distance and direction or relative X, Y (and Z) coordinates defined relative to some origin at a known location, which may be defined geographically, in municipal terms, or by reference to a point, area, or volume indicated on a map, floor plan, or building plan. In the description contained herein, the use of the term location may include any of these variations unless otherwise indicated. When calculating the location of the UE, local x, y, and possibly z coordinates are typically solved, and then the local coordinates are converted to absolute coordinates (e.g., for latitude, longitude, and altitude above or below mean sea level) if necessary.
[0062] Figure 1 The base stations (BSs) in the NG-RAN 135 shown include NR nodes, also referred to as gNBs, 110-1 and 110-2 (collectively and generically referred to herein as gNBs 110). The gNB 110 pairs in the NG-RAN 135 may be connected to each other—e.g., as Figure 1 As shown, the UE 102 is directly connected or indirectly connected via other gNBs 110. The UE 102 is provided with access to the 5G network via wireless communication between the UE 102 and one or more gNBs 110, which can represent the UE 102 using 5G NR providing wireless communication access to the 5GCN 140. 5G NR radio access may also be referred to as NR radio access or 5G radio access. Figure 1In the present invention, it is assumed that the serving gNB for UE 102 is gNB 110-1, although if UE 102 moves to another location, other gNBs (e.g., gNB 110-2) may serve as the serving gNB, or may serve as auxiliary gNBs to provide additional throughput and bandwidth to UE 102. As discussed herein, a location management component (LMC) 117 within a node in NG-RAN 135, such as in serving gNB 110-1, may perform location server functions. LMC 117 may be referred to by other names such as "location function", "location management function" (LMF), local LMF, RAN LMF, NG-RAN LMF, etc.
[0063] Figure 1 The base stations (BSs) in the illustrated NG-RAN 135 may also or alternatively include a next generation evolved Node B, also referred to as ng-eNB, 114. The ng-eNB 114 may be connected to one or more gNBs 110 in the NG-RAN 135—e.g., directly or indirectly via other gNBs 110 and / or other ng-eNBs. The ng-eNB 114 may provide LTE radio access and / or evolved LTE (eLTE) radio access to the UE 102. Figure 1 Some gNBs 110 (e.g., gNB 110-2) and / or ng-eNBs 114 in the UE 100 may be configured to function as positioning-only beacons, which may transmit signals (e.g., PRS signals) and / or may broadcast assistance data to assist in positioning of UE 102, but may not receive signals from UE 102 or other UEs. Figure 1 Only one ng-eNB 114 is shown, but some embodiments may include multiple ng-eNBs 114.
[0064] As mentioned above, although Figure 1 Nodes configured to communicate according to 5G NR and LTE communication protocols for NG-RAN 135 are depicted, but nodes configured to communicate according to other communication protocols may be used, such as the LTE protocol for an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN) or the IEEE 802.11x protocol for a WLAN. For example, in a 4G evolved packet system (EPS) that provides LTE wireless access to UE 102, the RAN may include an E-UTRAN, which may include base stations including evolved Node Bs (eNBs) that support LTE wireless access. The core network for the EPS may include an evolved packet core (EPC). The EPS may then include the E-UTRAN plus the EPC, where the E-UTRAN corresponds to Figure 1 In NG-RAN 135, EPC corresponds to Figure 1 5GCN 140 in.
[0065] The gNB 110 and ng-eNB 114 may communicate with an access and mobility management function (AMF) 115, which, for positioning functions, may communicate with a location management function (LMF) 120. The AMF 115 may support mobility of the UE 102, including cell changes and handovers, and may participate in supporting signaling connections to the UE 102, and may support data and voice bearers for the UE 102. When the UE accesses the NG-RAN 135, the LMF 120 (if present) may support positioning of the UE 102, and may support positioning procedures / methods such as Assisted GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA), Real-Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cell ID (ECID), Angle of Arrival (AOA), Angle of Departure (AOD), Multi-cell Round Trip Time (Multi-RTT), and / or other positioning methods. LMF 120 may also process location service requests for UE 102 received, for example, from AMF 115 or from GMLC 125. LMF 120 may be connected to AMF 115 and / or GMLC 125. In some embodiments, a node / system implementing LMF 120 may additionally or alternatively implement other types of location support modules, such as an enhanced serving mobile location center (E-SMLC). Note that in some embodiments, at least a portion of the positioning functionality (including derivation of the location of UE 102) may be performed at UE 102 (e.g., using signal measurements obtained by UE 102 for signals transmitted by wireless nodes such as gNB 110 and ng-eNB 114, and assistance data provided to UE 102 by LMF 120, for example).
[0066] The Gateway Mobile Location Center (GMLC) 125 may support location requests for UE 102 received from external clients 130 and may forward such location requests to AMF 115 for forwarding by AMF 115 to LMF 120 (or LMC 117). A location response (e.g., containing a location estimate for UE 102) from LMF 120 may similarly be returned to GMLC 125 directly or via AMF 115, and GMLC 125 may then return the location response (e.g., containing a location estimate) to the external client 130.
[0067] A network exposure function (NEF) 127 may be included in the 5GCN 140. The NEF 127 may support secure exposure of capabilities and events related to the 5GCN 150 and the UE 102 to the application function (AF) 131, and may enable secure provision of information from the AF 131 to the 5GCN 150. In the context of location services, the NEF 127 may be used to obtain the current or last known location of the UE 102, an indication of a change in the location of the UE 102, or an indication of when the UE 102 becomes available (or reachable). The NEF 127 may be connected to the AMF 115 and the GMLC 125 to support, for example, the last known location of the UE 102, the current location, and / or delayed periodic and triggered location.
[0068] LMF 120 may communicate with gNB 110 and / or ng-eNB 114 using New Radio Position Protocol A (NRPPa), which may be defined in 3GPP Technical Specification (TS) 38.455. NRPPa messages may be transmitted between gNB 110 and LMF 120, and / or between ng-eNB 114 and LMF 120 via AMF 115. LMF 120 and UE 102 may communicate using LTE Positioning Protocol (LPP), which may be defined in 3GPP TS 37.355. Herein, LPP messages may be transmitted between UE 102 and LMF 120 via AMF 115 and a serving gNB 110-1 or serving ng-eNB 114 for UE 102. For example, LPP messages may be transmitted between LMF 120 and AMF 115 using a service operation based on Hypertext Transfer Protocol (HTTP), and may be transmitted between AMF 115 and UE 102 using a 5G Non-Access Stratum (NAS) protocol. The LPP protocol may be used to support positioning of UE 102 using UE-assisted and / or UE-based positioning methods such as A-GNSS, RTK, OTDOA, multi-RTT, and / or ECID. The NRPPa protocol may be used to support positioning of UE 102 using network-based positioning methods, such as ECID (e.g., when used with measurements obtained by gNB 110 or ng-eNB 114), uplink AOA, and multi-RTT, and / or may be used by LMF 120 to obtain location-related information from gNB 110 and / or ng-eNB 114, such as parameters defining PRS transmissions from gNB 110 and / or ng-eNB 114.
[0069] Using UE-assisted positioning methods, UE 102 may obtain location measurements and send the measurements to a location server (e.g., LMF 120 or LMC 117 within a node in NG-RAN 135, such as in serving gNB 110-1) to calculate a location estimate for UE 102. For example, the location measurements may include one or more of: received signal strength indication (RSSI), round trip signal propagation time (RTT), reference signal time difference (RSTD), reference signal received power (RSRP), reference signal received quality (RSRQ), receive time-transmit time difference (Rx-Tx), AOA, and / or AOD for gNB 110, ng-eNB 114, and / or WLAN access point (AP). The location measurements may also or alternatively include measurements of GNSS pseudoranges, code phase, and / or carrier phase of SV 190. With a UE-based positioning method, UE 102 may obtain position measurements (e.g., which may be the same or similar to position measurements of a UE-assisted positioning method) and may calculate the position of UE 102 (e.g., with assistance data and / or uplink measurements received from a location server such as LMF 120 or LMC 117 or broadcast by gNB 110, ng-eNB 114, or other base stations or APs). With a network-based positioning method, one or more base stations (e.g., gNB 110 and / or ng-eNB 114) or APs may obtain position measurements of signals transmitted by UE 102 (e.g., measurements of RSSI, RTT, RSRP, RSRQ, AOA, Rx-Tx, or time of arrival (TOA)) and / or may receive measurements obtained by UE 102 and may send the measurements to a location server (e.g., LMF 120 or LMC 117) for use in calculating a position estimate of UE 102.
[0070] The information provided by the gNB 110 and / or ng-eNB 114 to the location server (e.g., LMF 120 using NRPPa) or the LMC 117 within a node in the NG-RAN 135 (e.g., in the serving gNB 110-1 using XnAP) may include timing and configuration information for PRS transmission and location coordinates. The location server may then provide some or all of this information to the UE 102 as assistance data in an LPP message via the NG-RAN 135 and 5GCN 140.
[0071] The LPP message sent from the location server to the UE 102 may instruct the UE 102 to perform any of a variety of things depending on the desired functionality. For example, the LPP message may contain instructions for the UE 102 to obtain measurements for GNSS (or A-GNSS), WLAN, and / or OTDOA (or some other positioning method such as multi-RTT). In the case of OTDOA, the LPP message may instruct the UE 102 to obtain one or more measurements (e.g., RSTD measurements) of PRS signals transmitted within a particular cell supported by a particular gNB 110 and / or ng-eNB 114 (or supported by some other type of base station such as an eNB or WiFi AP). The RSTD measurement may include the difference in the time of arrival of a signal (e.g., a PRS signal) transmitted or broadcast by one gNB 110 and a similar signal transmitted by another gNB 110 at the UE 102. The UE 102 may send the measurements back to a location server via the serving gNB 110-1 (or serving ng-eNB 114) and the AMF 115, for example in an LPP message (e.g., within a 5G NAS message) back to the LMF 120, or to the LMC 117 within a node in the NG-RAN 135 (e.g., in the serving gNB 110-1).
[0072] As noted, while the communication system 100 is described with respect to 5G technology, the communication system 100 may be implemented to support other communication technologies, such as GSM, WCDMA, LTE, etc., for supporting and interacting with mobile devices, such as UE 102 (e.g., for implementing voice, data, positioning, and other functions). In some such embodiments, the 5GCN 140 may be configured to control different air interfaces. For example, in some embodiments, the 5GCN 140 may control the non-3GPP interworking function (N3IWF, Figure 11140) is connected to the WLAN. For example, the WLAN may support IEEE 802.11 WiFi access for the UE 102 and may include one or more WiFi APs. In this article, the N3IWF may be connected to the WLAN and other elements in the 5GCN 140, such as the AMF 115. In some other embodiments, both the NG-RAN 135 and the 5GCN 140 may be replaced by other RANs and other core networks. For example, in the EPS, the NG-RAN 135 may be replaced by an E-UTRAN including an eNB, and the 5GCN 140 may be replaced by an EPC including a mobility management entity (MME) replacing the AMF 115, an E-SMLC replacing the LMF 120, and a GMLC that may be similar to the GMLC 125. In such an EPS, the E-SMLC may use the LPP A (LPPa) protocol defined by 3GPP TS36.455 instead of the NRPPa to send and receive location information to and from the eNB in the E-UTRAN, and the LPP may be used to support the positioning of the UE 102. In these other embodiments, on-demand resource allocation for UE 102 positioning may be supported in a manner similar to that described herein for 5G networks, except that the functionality and processes described herein for gNB 110, ng-eNB 114, AMF 115, and LMF 120 may in some cases be applied alternatively to other network elements such as eNBs, WiFi APs, MMEs, and E-SMLCs.
[0073] It should be noted that both gNB 110 and ng-eNB 114 may not always be present in NG-RAN 135. In addition, when both gNB 110 and ng-eNB 114 are present, the NG interface with AMF 115 may only be present for one of them.
[0074] like Figure 1As shown, the gNB 110 may be allowed to control one or more transmission points (TPs) 111, such as broadcasting only TPs, to improve support for DL positioning methods such as OTDOA or ECID. Additionally, the gNB 110 may be allowed to control one or more reception points (RPs) 113, such as internal location measurement units (LMUs), for UL measurements of positioning methods such as UTDOA or ECID. The TPs 111 and RPs 113 may be combined into or defined as part of a transmission reception point (TRP) 112 to support downlink (DL) and / or uplink (UL) positioning methods such as UL time difference of arrival (TDOA), DL TDOA (also known as OTDOA), and multi-RTT. Additionally, the gNB 110 may be allowed to include a location management component (LMC) 117 to support positioning of the target UE 102 by the serving gNB 110. LMC 117 may support some or all of the same functionality as LMF 120, except that LMC 117 is located in NG-RAN 135, whereas LMF 120 is located in 5GCN 140. Positioning of UE 102 by serving gNB 110 may be used to provide location services to UE 102, serving AMF 115, or LMF 120, and to improve NG-RAN operations—for example, by reducing latency in location determination and increasing the number of UEs 102 whose locations can be supported.
[0075] As shown, ng-eNB 114 may control one or more TPs 111a, which may use different protocols from TPs 111 in gNBs 110-1 and 110-2, e.g., TPs 111a may use protocols associated with LTE, while TPs 111 use protocols associated with 5G NR. TPs 111a may perform functions similar to those of TPs 111 in gNBs 110-1 and 110-2, and therefore, TPs 111 and 111a may be collectively referred to as TPs 111 herein.
[0076] The location management function (i.e., LMC 117) in NG-RAN 135 may have capabilities comparable to those of a 5GCN LMF (e.g., LMF 120). An operator may restrict LMC 117 to support, for example, NR radio access technology (RAT) related positioning if there is a 5GCN LMF 120 that supports other positioning methods, or may support most or all positioning methods in LMC 117 if there is no 5GCN LMF 120. LMC 117 may communicate with a gNB central unit (gNB-CU), as described later. LMC 117 may also manage one or more transmission points (TPs) 111 configured to transmit downlink (DL) reference signals (RSS) to be measured by UE 102 and one or more reception points (RPs) 113 configured to receive and measure uplink (UL) resource signals (RS) transmitted by UE 102. In some embodiments, LMC 117 may be a logical function in the gNB 110 CU, or may be external to the gNB 110 and connected to the gNB 110.
[0077] The LMC 117 in the gNB 110 may perform various functions. For example, the LMC 117 may request location measurements from the UE 102, for example using RRC or LPP, may manage UL location measurements by the gNB 110 or TRP 112 of the UE 102, and may manage static and dynamic scheduling of DL-PRS and broadcast of assistance data by the gNB 110. The LMC 117 may further interact with other gNBs 110 to coordinate location support (e.g., obtain UL location measurements for the UE 102 or request changes to DL-PRS broadcasts). The LMC 117 may determine a location estimate for the UE. The LMC 117 may provide location service capabilities to the serving AMF 115 (e.g., using NGAP), provide location service capabilities to other gNBs, and provide location service capabilities to the UE 102 (e.g., using RRC or LPP). The above functions are provided as examples only. Additional or different functions may be performed if desired. The LMC 117 may communicate with other gNBs 110 using XnAP or a location-specific protocol over XnAP to coordinate support for these functions.
[0078] Thus, the LMC 117 may support the NG-RAN 135 in determining the location of the UE 102, which may be requested by the UE 102 (e.g., using LPP), by the serving AMF 115 (e.g., using NGAP or a location specific protocol conveyed by NGAP), or by another gNB 110 / ng-eNB 114 (e.g., using XnAP or a location specific protocol conveyed by XnAP). Such a capability would allow location support without requiring the LMF 120 (or possibly the GMLC 125) in the 5GCN 140, and may also be used to reduce latency in location determination (because the NG-RAN 135 is closer to the UE 102 than the LMF 120), and to offload location support from the LMF.
[0079] Signaling between the AMF 115 and the NG-RAN 135 node may use protocol layering defined in 3GPP Technical Specifications (TS) 38.300 and 3GPP TS 23.501, and may use the Next Generation Application Protocol (NGAP) at the top level defined in 3GPP TS 38.413. The NG-RAN 135 location reporting procedure is defined in 3GPP TS 23.502 and 3GPP TS 38.413, and enables the serving AMF 115 to request the serving NG-RAN node to report the UE location only once, to report the UE location periodically when the serving cell changes, or to report the UE location periodically when the UE presence in the area of interest has changed. The location provided by the serving NG-RAN node may include an NR or LTE Cell Global Identity (CGI) and a Tracking Area Identity. This existing procedure may be enhanced to further include an optional Quality of Service (QoS) parameter in the Location Reporting Control message to enable the serving AMF 115 to request a more accurate location for the UE 102 than the location corresponding to the CGI. The procedure may be further enhanced to include an optional list of supported Geographic Area Description (GAD) shapes in the Location Reporting Control message. The procedure may also include allowing the serving NG-RAN node to obtain a more accurate UE location when QoS (e.g., using Enhanced Cell ID (ECID) positioning). The procedure may also allow the NG-RAN node (e.g., gNB 110) to return the UE location to the serving AMF 115 using the GAD shape when requested in the Location Reporting Control message.
[0080] Figure 2 1 shows an architecture diagram of an NG-RAN node 200 including an LMC 117. According to one embodiment, the NG-RAN node 200 may be a gNB 110. For example, Figure 2 The architecture shown can be applied to Figure 1 Any gNBs 110-1 and 110-2 in the NG-RAN 135 shown.
[0081] As shown, the gNB 110 includes a gNB central unit (gNB-CU) 202, and gNB distributed units (gNB-DU) 204 and 206, which may be physically co-located in the gNB 110 or may be physically separated. The gNB-CU 202 is a logical or physical node that carries support for the RRC, Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB used on the NR Uu air interface and controls the operation of one or more gNB-DUs. The gNB-CU terminates the F1 interface connected to the gNB-DU. As shown, the gNB-CU 202 may communicate with the AMF 115 via the NG interface. The gNB-CU 202 may also communicate with one or more other gNBs 110 via the Xn interface. The gNB-DUs 204 and 206 are logical or physical nodes that carry support for the radio link control (RLC), medium access control (MAC), and physical (PHY) protocol layers used over the NR Uu air interface of the gNB 110, and whose operation is controlled in part by the gNB-CU 202. The gNB-DU terminates the F1 interface with the gNB-CU. The gNB-CU 202 requests positioning measurements (e.g., E-CID) from the gNB-DUs 204 and 206. The gNB-DUs 204 and 206 report the measurements back to the gNB-CU 202. The gNB-DUs 204 and 206 may include positioning measurement functionality. It should be understood that a separate measurement node is not excluded.
[0082] The LMC 117 may be part of the gNB-CU 202 (e.g., a logical function or the gNB-CU 202). However, to offload positioning support from the gNB-CU 202 and allow a multi-vendor environment, a separate LMC 117 is allowed, which may be connected to the gNB-CU 202 via an F1 interface. The gNB-CU 202 may then forward all positioning related signaling to the LMC 117 and / or the gNB-DUs 204 and 206 or the TRP 112.
[0083] In addition, as shown in the figure, the gNB 110 may include TP 111 and RP 113 and LMC 117 combined into TRP 112, which may be physically or logically located in the gNB 110. The gNB-CU 202 may be configured to communicate with the TP 111, RP 113, and LMC 117, for example, via an F1 interface. Therefore, the gNB-CU 202 controls one or more TPs 111 and RP 113, and the LMC 117 may be accessed from the gNB-CU 202 via the F1 interface.
[0084] In some embodiments, the NG-RAN node 200 (or gNB 110) may include Figure 2 117. For example, NG-RAN node 200 may include gNB-CU 202 and LMC 117, but may not include one or more of gNB-DU 204 and 206, RP 113, or TP 111. Alternatively, NG-RAN node 200 may include one or more of gNB-DU 204 and 206, RP 113, or TP 111, but may not include LMC 117. In addition, Figure 2 The elements shown in the figure may be logically separated but physically co-located, or may be partially or completely physically separated. For example, the LMC 117 may be physically separated from the gNB-CU 202, or may be physically combined with the gNB-CU 202. Similarly, one or more of the gNB-DUs 204 and 206, the RP 113, or the TP 111 may be physically separated from the gNB-CU 202, or may be physically combined with the gNB-CU 202. In the case of physical separation, the F1 interface may define signaling over a physical link or connection between the two separated elements. In some embodiments, the gNB-CU 202 may be divided into a control plane portion (referred to as CU-CP or gNB-CU-CP) and a user plane portion (referred to as CU-UP or gNB-CU-UP). In this case, both the gNB-CU-CP and the gNB-CU-UP may interact with the gNB-DU 204 and 206 to support NRUu air interface signaling for the control plane (CP) and the user plane (UP), respectively. However, only the gNB-CU-CP may interact with the LMC 117, TP 111, and RP 113 to support and control location-related communications.
[0085] The protocol layering between the gNB-CU 202 and the TP 111, RP 113, and LMC 117 may be based on the F1 CP (F1 C) interface defined in 3GPP TS 38.470, which uses the top layer F1AP specified in 3GPP TS 38.473. New messages to support positioning may be added directly to the F1AP, or may be introduced in a new location-specific protocol that is transported using the F1AP.
[0086] The positioning procedure between the gNB-CU 202 and the LMC 117 may include all location-related procedures on the NG, Xn, and NR-Uu interfaces. For example, the positioning procedure between the AMF 115 and the NG-RAN node 200 may use NGAP. The positioning procedure between the NG-RAN node 200 and other NG-RAN nodes (e.g., gNB 110) may use XnAP or a protocol above XnAP, such as the Extended NR Positioning Protocol A (NRPPa) defined in 3GPP TS 39.455. The positioning procedure between the NG-RAN node 200 and the UE 102 may use RRC and / or LPP.
[0087] Corresponding messages supporting positioning can be carried in transparent F1AP message delivery containers. For example, the delivery of NGAP location reporting control and NAS transport messages can be carried out in UL / DL NGAP message delivery. The delivery of location-related XnAP messages can be carried out in UL / DL XnAP message delivery. The delivery of location-related RRC (LPP) messages can be carried out in UL / DL RRC (LPP) message delivery.
[0088] The above support may also be implemented via a single F1AP UL / DL LMC messaging container and / or a new location protocol using F1AP transport. Thus, the gNB-CU 202 may forward any location-related transport messages received on the NG, Xn, and Uu interfaces to the LMC 117 (or within the same gNB 110 (e.g., in the case where the gNB includes an LMC, such as Figure 2 as shown), or forwarded to another gNB (for example, in the case where the gNB does not have an LMC).
[0089] The positioning process between LMC 117 and gNB-DU 204 and 206, TP 111 and RP 113, which may be coordinated by gNB-CU 202, may include the transmission of UL / DL PRS configuration and the transmission of UL / DL PRS measurement information. The above functions may be similar to the functions of LTE LMU specified in 3GPP TS 36.305 and TS 36.459 (SLmAP), and also similar to the functions between LMF 120 and NG-RAN node 200. Therefore, NRPPa may be extended to support TRP location measurement / configuration messages that may be carried in F1AP transfer messages.
[0090] Therefore, the NG-RAN node 200 can support signaling and positioning procedures between the gNB-CU 202 and the LMC 117 based on F1AP to support the same positioning procedures supported on the NG, Xn and NR-Uu interfaces, and in addition, support the transmission of UL / DL PRS configuration and measurement information to / from the gNB-DU / TRP and from / to the LMC.
[0091] As can be seen, the NG-RAN positioning function (LMC) can be implemented using existing interfaces and protocols. However, given that there are common positioning procedures on Xn, NG and F1, it would be efficient to define a new common RAN positioning protocol that can be transported via Xn-C or F1-C (and possibly NG) messaging. Given that most of the functionality is also required between LMF and NG-RAN nodes (i.e., 5GCN LMF supports new Rel-16 positioning methods and features), NRPPa can also be extended to support additional RAN positioning messages.
[0092] For signaling between the AMF 115 and LMC 117 in the gNB 110, there may be two main options for reusing existing procedures / protocols, which will be described below and referred to as “Option 1” and “Option 2”.
[0093] Figure 3 "Option 1" is shown, with an enhanced position reporting process. Figure 3 The diagram illustrates signaling between the AMF 115 and a NG-RAN node, shown as the gNB 110 in an enhanced NG-RAN location reporting procedure. The serving AMF 115 may request the serving NG-RAN node 110 to report the UE location only once, periodically when the serving cell changes, or periodically when the UE presence in the area of interest has changed. However, the location provided by the serving NG-RAN node based on existing 3GPP procedures only includes the NR or E-UTRA Cell Global Identity (CGI) and the Tracking Area Identity (TAI). This procedure requires some minor additions as described below to enable the serving AMF to request a more accurate location from the NG RAN.
[0094] exist Figure 3 In Phase 1, the AMF 115 may send a Location Reporting Control message to the NG RAN node (e.g., gNB 110) to request the target device location. Optional QoS parameters may be added to the Location Reporting Control message to enable the serving AMF 115 to request a more accurate location than the one corresponding to the CGI. In addition, an optional list of supported GAD shapes in the Location Reporting Control message.
[0095] In Phase 2, the LMC 117 in the serving NG-RAN node (e.g., serving gNB 110) then determines the UE location. When providing QoS (using LMC), the serving NG-RAN node can obtain a more accurate UE location.
[0096] In Phase 3, the gNB 110 provides the location estimate back to the AMF 115 in a Location Report message. The UE location may be returned using the GAD shape when requested in a Location Report Control message.
[0097] Figure 3 The enhanced location reporting procedure in may be supported by the LMC 117 in the gNB 110. A gNB-CU 202 without an LMC 117 in the same gNB 110 may forward a location request (with QoS higher than the cell ID granularity) to another gNB 110 with an LMC 117 (by forwarding the Location Report Control message using an XnAP Transport message) and receive a later response from the LMC 117 (a Location Report message conveyed by an XnAP Transport message).
[0098] Figure 4 An "Option 2" is shown, in which the protocol defined in 3GPP TS 29.572 for the NL1 interface in 5GCN 140 is reused (eg Figure 1 as shown). Figure 4 Examples of location service support for Mobile Terminal Location Request (MT-LR) using 5GCN LMF based positioning (Stage 5) and using NG-RAN LMC based positioning (Stage 6) are shown.
[0099] exist Figure 4 In stage 1a of 3GPP TS 29.572, the GMLC 125 may send a Namf_Location_ProvidePositioningInfo request (as defined in 3GPP TS 29.572) to the AMF 115. Stages 1b and 1c are then skipped.
[0100] In phase 1b, if phase 1a is not performed, the NEF 127 may send a Namf_EventExposure Subscription Request (e.g., as defined in 3GPP TS 29.518) to the AMF 115.
[0101] In phase 1c, the AMF 115 may send a Namf_EventExposure Subscription Response to the NEF 127.
[0102] In Phase 2, if necessary, the UE 102, gNB 110 and AMF 115 initiate a network-triggered service request to put the UE 102 into a connected state.
[0103] In Phase 3, if necessary, UE 102, gNB 110 and AMF 115 initiate location notification verification to notify UE 102 of the location request and optionally allow UE 102 to allow or reject the location request.
[0104] In phase 4, the AMF 115 selects either LMF or LMC for positioning. Phase 5 is the process that will be performed if the AMF 115 selects LMF-based positioning; and if the AMF 115 selects RAN LMC-based positioning, phase 6 will be performed. From the AMF's perspective, the messages used for phases 5a and 5c in the case where LMF is selected can be the same as the messages used for phases 6a and 6c in the case where LMC is selected; only the transport (container) will be different. Therefore, the LMC will see the same "input / output" data as the LMF.
[0105] In phase 5a of LMF-based positioning, the AMF 115 sends a location request to the LMF 120, such as an Nlmf_Location_DetermineLocation request. Figure 1 The NL1 interface between the AMF 115 and the LMF 120 shown in supports a location request for the target UE 102 sent from the serving AMF 115 of the target UE 102 to the LMF 120 as specified in 3GPP TS 29.572. The request operation may include one or more of externalClientType, correlationID, amfId, occupationQoS, supportedGADShapes, supi, pei, gpsi, ecgi, ncgi, priority, and velocityRequested, where at least one of these parameters is present.
[0106] In phase 5b, UE 102, gNB 110, AMF 115 and / or LMF 120 initiate the UE positioning process.
[0107] In phase 5c, the LMF 120 sends a Nlmf_Location_DetermineLocation response to the AMF 115. The response operation includes locationEstimate and may further include one or more of accuracyFulfilmentIndicator, ageOfLocationEstimate, velocityEstimate, civicAddress, positioningDataList, gnssPositioningDataList, ecgi, ncgi, altitude, barometricPressure.
[0108] In phase 6a of LMC-based positioning, the AMF 115 sends a location request, such as Nlmf_Location_DetermineLocation, to the serving gNB 110. The Nlmf_Location_DetermineLocation request message for the target UE 102 may be transported between the serving gNB 110 and the serving AMF 115 in an NGAP transport container, which may be defined as a new NGAP DL transport message. The gNB-CU 202 without the collocated LMC 117 may then forward the Nlmf_Location_DetermineLocation request to another gNB 110 with the LMC 117 (by forwarding the Nlmf_Location_DetermineLocation request message using an XnAP transport message), and receive a later response from the other gNB.
[0109] In phase 6b, UE 102 and gNB 110 initiate a UE positioning process. UE 102 and / or gNB 110 may perform UL / DL signal measurements (e.g., UL-TDOA, DL-TDOA, multi-RTT, etc.) for location.
[0110] In phase 6c, the serving gNB 110 sends a location response, such as an Nlmf_Location_DetermineLocation response, to the AMF 115. The Nlmf_Location_DetermineLocation response message for the target UE 102 may be transported between the serving gNB 110 and the serving AMF 115 in an NGAP transport container, which may be defined as a new NGAP UL transport message.
[0111] In phase 7a, and if phase 1a is performed, the AMF 115 sends a Namf_Location_ProvidePositioningInfo response to the GMLC 125.
[0112] In phase 7b, and if phases 1b and 1c are executed, the AMF 115 sends a Namf_EventExposure notification message to the NEF 127.
[0113] and Figure 3 Compared to option 1 shown in Figure 4 Option 2 shown in may have several advantages. For example, AMF 115 may use the same messages / operations for LMF 120 and LMC 117. LMC 117 may be based on LMF 120 to reduce implementations of vendors supporting both LMC 117 and LMF 120. In addition, immediate and delayed positioning requests may be supported according to the 5GCN positioning procedures (e.g., MT-LR, Mobile Originated Positioning Request (MO-LR), Network Induced Positioning Request (NI-LR)) defined in 3GPP TS 23.273 and discussed below. Therefore, Figure 4 Option 2 shown in may be preferred and is assumed for the process described below.
[0114] The LPP protocol is used for the positioning procedure between the LMF 120 and the target UE 102, as specified in 3GPP TS 38.305 and 3GPP TS 37.355. For the LMF 120, the LPP messages are carried as transparent PDUs over the intermediate network interfaces using appropriate protocols (e.g., NAS / NGAP over the NG CP (NG-C) interface, NAS / RRC over the Uu interface).
[0115] The LPP may be reused for positioning signaling between the LMC 117 and the target UE 102 and transmitted in an RRC message container. The DL and UL information transfer messages may be extended to support non-NAS message containers, or new UL / DL RRC transfer container messages may be defined. The reuse of the LPP has the lowest overall impact, which also makes the UE positioning process unaware of the location of the LMF 120 (i.e., 5GCN LMF or NG-RAN LMC) (similar to the reuse of the NL1 message discussed above).
[0116] Figure 5 LPP signaling between LMC 117 in gNB 110 and UE 102 is shown. Figure 4 Stage 6b in can be expanded as shown.
[0117] exist Figure 5In phase 1, the LMC 117 in the gNB 110 sends an RRCDL transfer message to the target UE 102, for example in an LPP PDU.
[0118] In phase 2, the target UE 102 sends an RRC UL Transfer message to the LMC 117, for example in an LPP PDU.
[0119] The RRC signaling (e.g., location measurement indication) requesting measurement gaps may be reused, but may not be required when the LMC 117 is part of the serving gNB-CU 202. Since the gNB-CU 202 may now be aware of the location session, it may not be necessary for the UE 102 to request measurement gaps (i.e., the gaps may be configured by the serving gNB-CU 202 prior to any LPP location request). To indicate this to the UE 102, a flag (or similar small parameter) may be added to the LPP location request.
[0120] The LMC 117 may support the broadcast of assistance data in the same manner as the LMF 120 (e.g., as defined in 3GPP TS 38.305, 3GPP TS 38.455, 3GPP TS 38.331, and 3GPP TS 23.273). The LMC 117 will then perform any segmentation and encryption and provide a pre-coded positioning system information block (posSIB) for broadcast in a system information (SI) message. When the assistance data is broadcast in encrypted form, the encryption key may be provided by the LMC 117 to the AMF 115 for distribution to the appropriate subscribed UEs 102. The Nlmf_Broadcast_CipheringKeyData service operation specified in 3GPP TS 29.572 may be transmitted within an NGAP UL / DL transport message for this purpose (similar to Figure 4 In order to avoid that multiple LMCs provide the same encryption key to the AMF (e.g. for the same Tracking Area (TA)), only some LMCs may be configured to provide encryption keys to the AMF (e.g. only one LMC in each TA). The encryption keys may be configured in the LMC (e.g. by O&M) to ensure that gNBs in the same TA use the same encryption keys.
[0121] For location service operations, the Supplementary Services (SS) protocol (defined in 3GPP TS 24.080) can also be used for 5GCN location services as specified in 3GPP TS 23.273.
[0122] Figure 6 Supplementary service (SS) signaling between the LMC 117 in the gNB 110 and the UE 102 is shown.
[0123] exist Figure 6 In phase 1, the LMC 117 in the gNB 110 sends an RRC DL transfer message to the target UE 102, for example in an SS PDU.
[0124] In phase 2, the target UE 102 sends an RRC UL Transfer message to the LMC 117, for example in a SS PDU.
[0125] MT-LR and MO-LR service messages are exchanged between the AMF 115 and the UE 102 and may also be used in the same manner as currently defined for 5GCN LMF location services 3GPP TS 23.23. Supplementary service messages for supporting periodic and triggered location services are exchanged between the 5GCN LMF 120 and the UE 102. For the NG-RAN LMC 117, these messages may be transported in the same RRC container message as the LPP messages.
[0126] Figure 7 Various signaling between the first gNB1 / LMC1 1101 / 1171 and the second gNB2 / LMC2 1102 / 1172 are shown. The positioning process between the gNB / LMC pair needs to support one or more of the following functions: (a) requesting UL measurement of the target UE from another gNB (TRP) by one gNB (e.g., a serving gNB with LMC); (b) providing assistance data for the target UE to another gNB by one gNB (e.g., a serving gNB with LMC) to assist the UL measurement of the target UE by another gNB / TRP; (c) requesting a change in the scheduling and configuration of DL PRS broadcasting from one gNB to neighboring gNBs; (d) requesting a change in the scheduling and resources of broadcasting location information from one gNB to neighboring gNBs; (e) transmitting LPP containers from a serving gNB without LMC to a neighboring gNB with LMC; (f) transmitting SS containers from a serving gNB without LMC to a neighboring gNB with LMC; and (g) transmitting NGAP containers from a serving gNB without LMC to a neighboring gNB with LMC.
[0127] Items (a)-(d) are the same functions required between the 5GCN LMF and NG-RAN nodes, and it is expected that these functions will be supported using NRPPa in Rel-16 to support new NR positioning methods. Therefore, NRPPa can be reused for positioning procedures between gNBs. The XnAP transport container message can be defined in 3GPP TS 38.423, similar to Figure 7The XnAP Transport Container message can also be used to transport LPP and SS messages from a gNB without LMC to a gNB with LMC, and to forward the Nlmf_Location_DetermineLocation request / response to a neighboring gNB (in the case where the serving gNB does not have LMC), as shown in the RRC transport procedure. Figure 4 described.
[0128] Figure 8 Various signaling between the gNB-CU 202 and the LMC 117 are shown. The positioning procedures between the gNB-CU 202 and the LMC 117 include all location-related procedures on the NG, Xn and NR-Uu interfaces, including: Positioning procedures between the AMF 115 and the gNB / LMC 110 / 117 (using Nlmf_Location_DetermineLocation), such as Figure 4 The positioning process between gNB / LMC 110 / 117 and UE 102 (using LPP and SS) is as follows: Figure 5 As described; the positioning process between gNB / LMC 110 / 117 (using NRPPa), such as Figure 7 described.
[0129] The corresponding messages supporting positioning can be carried in the F1AP messaging container. In essence, the gNB-CU 202 will forward any location-related messages received on the NG, Xn and Uu interfaces to the LMC 117, such as Figure 8 (if gNB 110 has LMC 117; otherwise forwarded to another gNB 110 using XnAP, as shown Figure 7 described above).
[0130] Fig. 9 Various signaling between the gNB-CU 202 and the gNB-DU / TRP 204 / 112 is shown. The gNB-DU / TRP 204 / 112 may perform general functions such as: transmitting DL PRS according to a selected configuration (which may be configured on demand by the gNB-CU / LMC 202 / 117, e.g., based on the required QoS); performing UL PRS signal measurements such as RTOA, Rx-Tx, or AOA, where the UL PRS configuration needs to be provided to the RP 113 on demand by the gNB-CU / LMC 202 / 117; and reporting UL signal measurements (for a specific UE 102) to the gNB-CU / LMC 202 / 117.
[0131] The above functionality needs to be supported by signaling between the 5GCN LMF 120 and the gNB-DU / TRP 204 / 112, and will therefore be defined in NRPPa. The main options for signaling between the gNB-CU 202 and the gNB-DU / TRP 204 / 112 are referred to herein as "Option (a)" and "Option (b)". Option (a) uses separate procedures, messages, and parameters in F1AP that are consistent with NRPPa (but may not completely copy NRPPa). Option (b) uses F1AP container messages that carry NRPPa PDUs. The gNB-CU 202 can then forward the received NRPPa PDU to a specific gNB-DU / TRP 204 / 112.
[0132] For option (b), a common F1AP transfer message may be used for both gNB-CU 202 to gNB-DU / TRP 204 / 112 signaling and gNB-CU 202 to LMC 117 signaling (e.g. Figure 8 This will be similar to the RRC message transmission message carrying the RRC container in F1AP, and Fig. 9 These two situations are summarized in this paper.
[0133] The positioning transfer message may be opaque to the gNB-CU 202. For example, the gNB-CU 202 will need to interpret certain header portions of the transfer message to determine any subsequent actions, but will not need to interpret the included positioning PDU. For example, the gNB-CU 202 will need to decide whether the NRPPa PDU is intended for a gNB-DU / TRP 204 / 112 in the same gNB 110, or needs to be provided to a gNB-DU / TRP 204 / 112 of a neighboring gNB (which would require the NRPPa PDU to be transmitted using an XnAP transfer message).
[0134] For option (a), the NRPPa message will need to be converted to or from the corresponding F1AP message by the gNB-CU 202. This may result in significant overhead and additional processing by the gNB-CU 202.
[0135] Fig.10 An example of signaling for option (a) is shown, where the LMC 117 in the serving gNB 110-1 for the target UE 102 requests UL location measurements for the target UE 102 from the gNB-DU / TRP 204 / 112 in the neighboring gNB 110-2. In option (b), the NRPPa message is transmitted between the LMC 117 in the serving gNB 110-1 and the gNB-DU / TRP 204 / 112 in the neighboring gNB 110-2 without any conversion by the gNB-CU 202.
[0136] like Figure 3-Figure 10 As shown, existing positioning protocols can be reused for local NG-RAN positioning, including: Nlmf_Location_DetermineLocation and Nlmf_Broadcast_CipheringKeyData service operations defined in 3GPP TS29.572; LPP defined in 3GPP TS37.355; supplementary services defined in 3GPP TS 24.080; and NRPPa defined in 3GPP TS38.455.
[0137] The positioning messages of these positioning protocols can be transmitted in the transport container messages used for NGAP, RRC, XnAP and F1AP. Therefore, no new interface(s) may be required; the impact on existing protocols may be limited to the specification of new UL / DL transport message containers in NGAP, RRC, XnAP and F1AP protocols.
[0138] As specified in 3GPP TS 23.273, services related to UE positioning may be initiated from the 5GCN in the case of NI-LR or MT-LR location services, or from the UE 102 in the case of MO-LR location services. The same UE positioning services may also be supported using the LMC 117 in the NG-RAN, as described below.
[0139] Fig.11 The MT-LR procedure for determining the location of the UE 102 using the LMC 117 in the NG-RAN is shown. The 5GCN MT-LR and NI-LR procedures are specified in 3GPP TS 23.273. The signaling and procedures in the 5GCN using the LMC 117 may be the same as currently specified for the LMF 120. For the MT-LR procedure, the serving AMF 115 in the home or visited PLMN will at some point receive a Namf_Location_ProvidePositioningInfo request operation to request the current location of the UE 102, as shown above. Figure 4 shown in the following Fig.11 Further explanation in. Fig.11 MT-LR via GMLC 125 is shown. Similar to Fig.11 The message flow will be used by NEF for MT-LR. In particular, Fig.11 Stages 4-7 in may remain the same. For NI-LR, the serving AMF 115 determines the requirement to locate the UE 102, for example due to detecting the start of an emergency service call from the UE 102. For MT-LR, the serving AMF 115 performs Fig.11All stages in , while for NI-LR only stages 4-7 are performed.
[0140] exist Fig.11 In Phase 1, for MT-LR, the serving AMF 115 of the target UE 102 receives a Namf_Location_ProvidePositioningInfo request operation from the GMLC 125 (e.g., H-GMLC or V-GMLC). This service operation includes SUPI, client type and other information such as required QoS, supported GAD shapes, etc. The GMLC 125 verifies UE privacy before initiating Phase 1.
[0141] In Phase 2, for MT-LR, if the UE 102 is in CM IDLE state, the AMF 115 initiates a network triggered service request procedure as defined in clause 4.2.3.4 of 3GPP TS 23.502 to establish a signaling connection with the UE 102.
[0142] In phase 3, for MT-LR, if the UE 102 must be notified according to phase 1 or notified by privacy verification, and if the UE 102 supports LCS notification (according to the UE capability information), a notification call message is sent to the target UE 102, as specified in 3GPP TS 23.273. The target UE 102 notifies the UE user of the location request, and if privacy verification is requested, waits for the user to grant or deny permission. The UE 102 then returns a notification result to the AMF 115, indicating whether permission is granted or denied for the current LCS request if privacy verification is requested.
[0143] In stage 4, for MT-LR or NI-LR, the AMF 115 selects the LMF 120 or LMC 117. This can be based on the information currently defined in clause 5.1 of 3GPP TS 23.273 or based on AMF local configuration. The LMF / LMC selection takes into account the NG-RAN currently serving the UE. If LMC 117 is selected, stages 5-7 are performed. If LMF 120 is selected, similar steps are performed using the LMF 120 defined in clauses 6.1 and 6.10 of 3GPP TS 23.273.
[0144] In stage 5, as above Figure 4As described, the AMF 115 will send a Nlmf_Location_DetermineLocation request service operation within a NGAP DL Transfer message to the serving gNB-CU 202. The service operation may include an LCS-related identifier, an indication of whether the UE supports LPP, the required QoS, and the supported GAD shapes, as specified in 3GPP TS 29.572. In the case of "security issues", any UE / subscriber identity (e.g., SUPI or PEI) supported in the Nlmf_Location_DetermineLocation does not need to be provided to the LMC 117. The UE 102 can be identified by, for example, the NGAP-ID. The serving gNB-CU 202 can forward the Nlmf_Location_DetermineLocation request to a separate LMC 117 in the same gNB 110 in a F1AP Transfer message, as above Figure 8 The serving gNB-CU 202 may instead forward the Nlmf_Location_DetermineLocation request to an LMC in another gNB 110-2, in which case the Nlmf_Location_DetermineLocation request would initially be forwarded in an XnAP Transfer message to the gNB-CU in another gNB 110-2 with the gNB-CU, and then forwarded to the LMC in an F1AP Transfer message if the LMC is detached from the gNB-CU.
[0145] In stage 6, LMC 117 performs positioning procedures. This may include DL-PRS measurements performed at UE 102, and UL-PRS measurements performed at gNB-DU / TRP 204 / 112, as follows Fig.12 described.
[0146] In phase 7, the gNB-CU 202 returns the Nlmf_Location_DetermineLocation response message to the AMF 115 within the NGAP UL Transport message to return the current location of the UE 102, as shown above. Figure 4as described. The message includes an LCS-related identifier, a position estimate, its age and accuracy, and may include information about the positioning method, as specified in 3GPP TS 29.572. If the LMC 117 is not part of the serving gNB-CU 202, the LMC shall first return a Nlmf_Location_DetermineLocation response to the serving gNB-CU 202 in an F1AP Transfer message if the LMC is part of the serving gNB 110-1, a Nlmf_Location_DetermineLocation response in an XnAP Transfer message if the LMC is part of another gNB-CU 202, or a Nlmf_Location_DetermineLocation response in an F1AP Transfer message followed by an XnAP Transfer message if the LMC is in another gNB 110-2 and not part of a CU in this gNB. These operations, as well as positioning in Phase 3, require that the serving gNB-CU 202 maintains the identity of the LMC 117, and that the LMC 117 maintains the identity of the serving gNB-CU 202.
[0147] In phase 8, for MT-LR, AMF 115 returns a Namf_Location_ProvidePositioningInfo response to GMLC 125 to return the current location of UE 102, as specified in 3GPP TS 23.273. GMLC 125 may perform additional privacy verification before returning the current location to external client 130 or AF 131.
[0148] Fig.12 The NI-LR procedure for determining the UE location using the LMC 117 in the NG-RAN is shown.
[0149] exist Fig.12 In Phase 1, the serving AMF 115, UE 102 and gNB-CU 202 perform emergency registration or regulatory PDU session establishment.
[0150] Fig.12 Stages 2-4 in Fig.11 Phases 5-7 in the NSLMF_Location_DetermineLocation request are identical, differing only in some parameters of the Nlmf_Location_DetermineLocation service operation.
[0151] In stage 5, the AMF 115 provides the Namf_Location_EventNotify message to the GMLC / LRF 125.
[0152] Fig.13The UE positioning process is shown. Fig.11 Stage 6 and Fig.12 The UE positioning process in stage 3 may include LPP and NRPPa signaling, and Fig.13 Summarized in . Fig.13 It is assumed that the LMC 117 is part of the serving gNB 110-1 and is separate from the serving gNB-CU 202. If the LMC 117 is part of the serving gNB-CU 202, then stages 1a, 2a, 3a, 4a, 6c, and 7c will not occur. If the LMC 117 is part of the neighboring gNB 110-2, then each of stages 1a, 2a, 3a, 4a, 6c, and 7c will be replaced by a stage in which an LPP or NRPPa location message in each stage is transmitted between the serving gNB-CU and the gNB-CU in the neighboring gNB 110-2 in an XnAP Transfer message, and if the LMC 117 is not part of the neighboring gNB-CU, it will be replaced by an additional step in which a location message is further transmitted between the neighboring gNB-CU and the LMC 117 in an F1AP Transfer message.
[0153] exist Fig.13 In stage 1 of , illustrated as stages 1a, 1b, and 1c, for DL-PRS measurements, the LMC 117 may determine gNB-DUs / TRPs 204 / 112 (e.g., serving gNB-DUs) in the vicinity of the approximate location of the target device 102. If no or insufficient DL-PRS resources are configured on these gNB-DUs / TRPs, the LMC 117 may initiate an NRPPa procedure to configure (or reconfigure) DL PRS on the gNB-DUs / TRPs.
[0154] In phase 1a, LMC 117 sends the NRPPa DL-PRS configuration message to gNB-CU 202 within the F1AP transmit message, such as Figure 8 described.
[0155] In phases 1b and 1c, the gNB-CU 202 may forward the NRPPa DL-PRS configuration message to the gNBDU / TRP 204 / 112 using F1AP, as shown above. Fig. 9 or using XnAP to forward the NRPPa DL-PRS configuration message to the neighboring gNB 110-2, as described above Figure 7 described.
[0156] In stage 2, shown as stages 2a, 2b and 2c, for UL-PRS measurements, the LMC 117 provides the UL PRS configuration to the selected gNB-DU / TRP 204 / 112 in an NRPPa UL PRS Measurement Request message. The message includes all information required to enable the gNB-DU / TRP 204 / 112 to perform UL measurements.
[0157] In phase 2a, LMC 117 sends an NRPPa UL-PRS measurement request message to gNB-CU 202 within an F1AP transmit message, such as Figure 8 described.
[0158] In phases 2b and 2c, the gNB-CU 202 may forward the NRPPa UL-PRS measurement request message to the gNB DU / TRP 204 / 112 using F1AP, as shown above. Fig. 9 Alternatively, the NRPPa UL-PRS measurement request message may be forwarded to the neighboring gNB 110-2 using XnAP, as described above. Figure 7 described.
[0159] In stage 3 , shown as stages 3 a , 3 b , and 3 c , the LMC 117 may send an LPP Provide Assistance Data message to the target device 102 .
[0160] In phase 3a, LMC 117 sends the LPP Provide Assistance Data message to gNB-CU 202 in the F1AP Transmit message, such as Figure 4 described.
[0161] In phases 3b and 3c, gNB-CU 202 forwards the LPP Provide Assistance Data message to gNB-DU 204, as shown above. Fig. 9 As described above, it forwards the message to UE 102 within the RRC transmit message, as shown above Figure 5 and 6 described.
[0162] In stage 4 , illustrated as stages 4 a , 4 b , and 4 c , LMC 117 may send an LPP request location information message to target device 102 .
[0163] In phase 4a, LMC 117 sends an LPP request location information message to gNB-CU 202 in an F1AP transmit message, such as Figure 8 described.
[0164] In phases 4b and 4c, gNB-CU 202 forwards the LPP Request Location Information message to gNB-DU 204, as shown above. Fig. 9 As described above, it forwards the message to UE 102 within the RRC transmit message, as shown above Figure 5 and Figure 6 described.
[0165] In stage 5, shown as stages 5a, 5b, and 5c, the UE 102 and the configured gNB-DU / TRP 204 / 112, e.g., in the serving gNB 110-1 or the neighboring gNB 110-2, perform DL and UL PRS measurements.
[0166] In stage 6, shown as stages 6a, 6b and 6c, UE 102 sends an LPP Provide Location Information message to LMC 117.
[0167] In stage 6a, UE 102 sends an LPP Provide Location Information message to gNB-DU 204 in an RRC Transmit message, such as Figure 5 and Figure 6 described.
[0168] In phase 6b, gNB-DU 204 forwards the LPP Provide Location Information message to gNB-CU 202 within the F1AP Transmit message, such as Fig. 9 described.
[0169] In stage 6c, gNB-CU 202 forwards the LPP Provide Location Information message to LMC 117 in the F1AP Transmit message, such as Figure 8 described.
[0170] In stage 7, shown as stages 7a, 7b and 7c, each gNB-DU / TRP 204 / 112 reports UL PRS measurements to the LMC 117 in an NRPPa UL PRS Measurement Response message.
[0171] In stages 7a and 7b, the NRPPa UL-PRS Measurement Response message is sent to the serving gNB-CU 202 within an F1AP transmit message from the gNB-DU / TRP 204 / 112 in the serving gNB 110-1 or within an XnAP transmit message from the neighboring gNB 110-2.
[0172] In stage 7c, the serving gNB-CU 202 forwards the NRPPa UL-PRS Measurement Response message to the LMC 117 within the F1AP Transfer message.
[0173] Fig.14A RAN-initiated Location Request (RI-LR) procedure for determining the UE location is shown, which may be used when the NG-RAN (e.g., serving gNB 110-1) requires the location of the target UE 102; for example, for RRM purposes. Using this procedure, a separate / new procedure for "NG RAN acting as LCS client" may not be required. The procedure assumes that no location notification and / or verification of the UE 102 is required, for example, this may be indicated in the UDM privacy subscription for the UE 102 and signaled by the serving AMF 115 to the serving gNB 110-1 as part of the signaling connection establishment. Otherwise if the UE privacy subscription requires notification and / or verification, then this procedure does not apply.
[0174] Fig.14 It is assumed that LMC 117 is part of serving gNB 110-1 and is separate from serving gNB-CU 202. If LMC 117 is part of serving gNB-CU 202, then phases 1 and 3 will not occur. If LMC 117 is part of neighboring gNB 110-2, then each of phases 1 and 3 will be replaced by a phase in which a location message in each phase is transmitted between the serving gNB-CU and the gNB-CU in neighboring gNB 110-2 in an XnAP transmit message, and if LMC 117 is not part of the neighboring gNB-CU, then it will be replaced by an additional phase in which a location message is further transmitted between the neighboring gNB-CU and the LMC in an F1AP transmit message.
[0175] exist Fig.14 In stage 1, the serving gNB-CU 202 sends a Nlmf_Location_DetermineLocation request service operation within a F1AP Transport message to the LMC 117. The service operation may include the LCS related identifier, the required QoS, and the supported GAD shapes as specified in 3GPP TS 29.572.
[0176] In phase 2, LMC 117 performs the following Fig.13 The positioning of the target UE 102.
[0177] In Phase 3, the LMC 117 returns a Nlmf_Location_DetermineLocation Response message within the F1AP Transport message to the serving gNB-CU 202. The Location Response includes the LCS-related identifier, the location estimate, its age and accuracy, and may include information about the positioning method, as specified in 3GPP TS 29.572.
[0178] Fig.15The 5GCN MO-LR procedure with LMC 117 in NG-RAN is shown. The 5GCN MO-LR procedure is specified in 3GPP TS 23.273. The signaling and procedures in 5GCN may be the same as currently specified, such as Fig.15 shown.
[0179] exist Fig.15 In Phase 1, if UE 102 is in CM-IDLE state, UE 102 initiates a UE triggered service request as defined in Section 4.2.3.2 of 3GPP TS 23.502 to establish a signaling connection with AMF 115.
[0180] In phase 2, UE 102 sends an SS MO-LR request message included in a UL NAS transport message to AMF 115. The MO-LR request may include an LPP positioning message (e.g., LPP request assistance data). Different types of location services may be requested, including: a position estimate for UE 102, a position estimate for UE 102 to be sent to LCS Client 130 or AF 131, or position assistance data.
[0181] In stage 3, the AMF 115 selects either the LMF 120 or the LMC 117. This can be based on the information currently defined in clause 5.1 of 3GPP TS 23.273 or based on AMF local configuration. The LMF / LMC selection takes into account the NG-RAN currently serving the UE. If LMC 117 is selected, stages 4-6 are performed. If LMF 120 is selected, similar stages are performed using the LMF 120 defined in clause 6.2 of 3GPP TS 23.273.
[0182] In stage 4, as above Figure 4 As described, the AMF 115 sends a Nlmf_Location_DetermineLocation request service operation within a NGAP DL transport message to the serving gNB-CU 202. The service operation may include an LCS-related identifier, an indication of whether a location estimate or location assistance data is requested, and any embedded LPP messages in the MO-LR request as specified in 3GPP TS 23.273.
[0183] The serving gNB-CU 202 may forward the Nlmf_Location_DetermineLocation request NGAP container in the F1AP Transfer message to a separate LMC 117 in the same gNB as above. Figure 8The serving gNB-CU may instead forward the Nlmf_Location_DetermineLocation request to an LMC in another gNB 110-2, in which case the Nlmf_Location_DetermineLocation request would initially be forwarded in an XnAP Transfer message to the gNB-CU in another gNB 110-2 with the gNB-CU, and then forwarded to the LMC in an F1AP Transfer message if the LMC is detached from the gNB-CU.
[0184] In phase 5, the LMC 117 performs a positioning procedure (to obtain the UE position or transmit assistance data, as requested in phase 2).
[0185] In phase 6, when the location has been obtained or when the requested location assistance data has been delivered to the UE 102, the serving gNB-CU 202 returns a Nlmf_Location_DetermineLocation response message within the NGAP UL Transfer message to the AMF 115 to return the current location of the UE 102 or confirm the delivery of the assistance data. The message includes the LCS-related identifier and may include the location estimate, its age and accuracy, and information about the positioning method, as specified in 3GPP TS 29.572. If LMC 117 is not part of serving gNB-CU 202, LMC 117 will first return a Nlmf_Location_DetermineLocation response to serving gNB-CU 202 in a F1AP Transmit message if LMC 117 is part of serving gNB 110-1, in an XnAP Transmit message if LMC 117 is part of another gNB-CU, or in a F1AP Transmit message followed by an XnAP Transmit message if LMC 117 is in another gNB 110-2 and not part of a CU in that gNB. These operations, as well as positioning in Phase 5, require that serving gNB-CU 202 maintain the identity of LMC 117, and LMC 117 maintain the identity of serving gNB-CU 202.
[0186] In Phase 7, signaling with other 5GCN LCS entities 125 (e.g., GMLC 125) may occur, for example, to inform the GMLC 125 (e.g., for billing purposes) or to transmit the position estimate to a third party specified in 3GPP TS 23.273.
[0187] In phase 8, the AMF 115 sends a SS MO-LR Response message included in a DL NAS Transport message to the UE 102. The response carries any position estimate requested by the UE 102, or an indicator of whether a position estimate was successfully delivered to the identified LCS Client 130 or AF 131.
[0188] Fig.16 Delayed MT-LR with periodic, triggered and UE available location events in NG-RAN is shown. Delayed 5GCN MT-LR procedures using LMF are specified in 3GPP TS 23.273. The signaling and procedures in 5GCN can be the same as specified in 3GPP TS 23.273, as shown below Fig.16 shown.
[0189] exist Fig.16 In phase 1 of the target UE 102, the serving AMF 115 receives a Namf_Location_ProvidePositioningInfo request operation (or message) from the LCS entity 125 in the 5GCN (e.g., from the H-GMLC or V-GMLC 125). The service operation may include a location delay request (LDR) reference number, (H-)GMLC contact address, trigger location whether location estimation is required, QoS, supported GAD shapes, and other parameters defined in 3GPP TS 23.273. The GMLC 125 verifies UE privacy before initiating phase 1.
[0190] In phase 2, if the AMF 115 supports delayed location request, the AMF 115 returns an acknowledgement.
[0191] In Phase 3, if the UE 102 is currently unreachable (eg, using EDRX or PSM), the AMF 115 waits for the UE 102 to become reachable.
[0192] In Phase 4, once the UE 102 is reachable, if the UE 102 is then in CM IDLE state, the AMF 115 initiates a Network Triggered Service Request procedure as defined in clause 4.2.3.4 of 3GPP TS 23.502 to establish a signaling connection with the UE 102.
[0193] In phase 5, if the UE 102 must be notified according to phase 1 or notified by privacy verification, and if the UE 102 supports LCS notification (according to the UE capability information), a notification call message is sent to the target UE 102, as specified in 3GPP TS23.273. The target UE 102 notifies the UE user of the location request, and if privacy verification is requested, waits for the user to grant or deny permission. The UE 102 then returns a notification result to the AMF 115, indicating whether permission is granted or denied for the current LCS request if privacy verification is requested.
[0194] In stage 6, the AMF 115 selects either the LMF 120 or the LMC 117. If the LMC 117 is selected, stages 7-20 are performed. If the LMF 120 is selected, similar steps are performed using the LMF 120 defined in clause 6.3.1 of 3GPP TS 23.273. The AMF 115 may or may not select a specific LMC. If no specific LMC is selected, the serving gNB-CU 202 selects the LMC 117 (e.g., the LMC in the serving gNB 110-1).
[0195] In stage 7, as above Figure 4 As described, the AMF 115 will send a Nlmf_Location_DetermineLocation request service operation (or message) within a NGAP DL transfer message to the serving gNB-CU 202. The service operation includes an LCS related identifier, an indication of whether the UE supports LPP, and other parameters received in stage 1 and defined in 3GPP TS 29.572. In the case of "security issues", any UE / subscriber identity (e.g., SUPI or PEI) supported in Nlmf_Location_DetermineLocation does not need to be provided to the LMC 117. The UE 102 can be identified by, for example, NGAP-ID. If the LMC 117 is not part of the serving gNB-CU 202, the serving gNB-CU 202 can forward the Nlmf_Location_DetermineLocation request NGAP container to the LMC 117 in the F1AP DL transfer message, as described above. Figure 8If the LMC 117 is in another gNB, the Nlmf_Location_DetermineLocation request is forwarded to the other gNB-CU in the XnAP transfer message, and then the other gNB-CU forwards the request to the LMC 117. Only the serving gNB-CU 202 and the LMC 117 need to retain the status information of the location request (including the identity of the serving gNB-CU 202 in the case of the LMC 117, and the identity of the LMC 117 in the case of the serving gNB-CU 202).
[0196] In stage 8, LMC 117 may perform a positioning process (e.g., if an initial position estimate is required), such as Fig.13 During this phase, LMC 117 may request and obtain UE positioning capabilities (eg, which may indicate the type(s) of periodic and triggered location supported by UE 102 and the access types supported by UE 102 for event reporting).
[0197] For requests for UE available location events, the LMC 117 skips stages 9 and 10.
[0198] In stage 9, if periodic or triggered positioning is requested, LMC 117 sends a supplementary service LCS periodic triggered invocation request to UE 102, as shown above. Figure 5 and Figure 6 As described. The LCS periodically triggered location call carries the location request information received from AMF115 in stage 7. As specified in 3GPP TS 23.273, the LCS periodically triggered location call also includes a delay routing identifier, which can be the identity of LMC 117 when LMC 117 is to act as the serving LMC 117, otherwise it can be the default LMC identity. The LCS periodically triggered location call may also include an embedded LPP positioning message, which indicates certain allowed or required location measurements (or location estimates) for each location event reported in stage 14. The delay routing identifier can be global (e.g., an IP address, UUID, or URI), or it can be local. The delay routing identifier is used for routing by the gNB-CU 202 in stage 16.
[0199] In stage 10, if the request in stage 9 can be supported, UE 102 returns a supplementary service confirmation to LMC 117, which is transmitted in an RRL UL transfer message, as shown above. Figure 5 and Figure 6 described.
[0200] In stage 11, the LMC 117 sends an Nlmf_Location_DetermineLocation response message in an NGAP UL transport message over the NG interface to the AMF 115 in response to the request in stage 7. For a request for a UE available location event, the response includes any UE location obtained in stage 8, and then the LMC 117 releases all resources. For a periodic or triggered location request, the response includes any location obtained in stage 8, confirmation of whether periodic or triggered positioning was successfully activated in the UE 102 according to stages 9 and 10, and an identification of the LMC 117 in case of successful activation with the serving LMC. If the LMC 117 acts as a serving LMC, the LMC 117 also retains state information and resources for subsequent steps.
[0201] In phase 12, the AMF 115 invokes the Namf_Location_EventNotify service operation for V-GMLC for roaming or H GMLC for non-roaming and includes any location received in phase 11 and, for periodic or triggered positioning, confirms whether periodic or triggered positioning is successfully activated in the target UE 102. The AMF 115 also includes the LMC identity if received in phase 11. The AMF 115 may then release all resources used for location requests and cease support for the procedure.
[0202] In stage 13, for a periodic or triggered location request that successfully performed stages 9 and 10, UE 102 monitors for the occurrence of the triggered or periodic event requested in stage 9. For an area event or motion event, UE 102 monitors the requested event at an interval equal to or less than the maximum event sampling interval. UE 102 detects an event trigger when any of the following occurs: (I) the requested area event or motion event has been detected and the minimum reporting time interval has passed since the last report (if this is not the first event report); (ii) the requested periodic location event has occurred; or (III) the maximum reporting time for the area event or motion event has expired.
[0203] In stage 14 , UE 102 obtains any location measurements or location estimates requested or allowed in stage 9 .
[0204] In stage 15, if in RRC-IDLE state, UE 102 performs RRC connection establishment as defined in 3GPP TS 38.331.
[0205] At stage 16, UE 102 sends the LMC 117 (which may be different from the original serving LMC of stages 7-10) the datagram included in the above Figure 5 and Figure 6The event report may indicate the type of event being reported (e.g., whether it is a normal event or expiration of a maximum reporting interval) and may include an embedded LPP positioning message that includes any location measurements or location estimates obtained in stage 14. The event report also includes the (H-)GMLC contact address, the LDR reference number, whether the location estimate is to be reported, and the location QoS in the case where it is to be reported. The UE 102 also includes the delay routing identifier received in stage 9. The serving gNB-CU 202 then forwards the event report to the serving LMC 117 or any suitable LMC (e.g., an LMC in the same gNB if available) based on whether the delay routing identifier indicates a specific LMC or any (default) LMC. If the LMC 117 is part of the serving gNB-CU, no message transmission is required. If the LMC 117 is separate from the serving gNB-CU 202 but in the same gNB, the event report is forwarded using F1AP, such as Figure 8 If the LMC 117 is in a gNB different from the serving gNB, the event report is transmitted in the XnAP Transfer message as above Figure 7 described.
[0206] In phase 17, when LMC 117 receives the event report and if it is able to process the event report, LMC 117 returns a supplementary service confirmation for the event report to UE 102 (in an RRC DL transfer message, as shown above). Figure 5 and Figure 6 The confirmation optionally includes a new delay routing identifier indicating a new serving LMC or a default (any) LMC. Including the new delay routing identifier in the event report confirmation of stage 17 can be used to change the serving LMC (e.g., if UE 102 moves to an area better supported by a different LMC, or if the serving LMC is overloaded), or to make the default LMC the serving LMC.
[0207] In stage 18, if the event report requires a position estimate, the LMC 117 may perform the following steps: Fig.13 The positioning process described.
[0208] In phase 19, the LMC 117 sends an event report (e.g., position estimate) to the external client via the AMF 115 and includes the LDR reference number and the (H-)GMLC contact address to enable the AMF 115 to forward the event report to the correct (H-)GMLC for onward delivery to the external client or AF 131. The (H-)GMLC may perform additional privacy verification before returning the current position to the external client or AF.
[0209] In some embodiments of stage 19, the LMC 117 or gNB-CU 202 may send an event report to the external client 130 (or AF 131) at the user plane level and bypass other entities such as the AMF 115, GMLC 125, and NEF 127, which may achieve reduced latency. For example, the LMC 117 or gNB-CU 202 may transmit the event report in the form of data or data messages using one or more of the Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Transport Layer Security (TLS) protocols to send the event report directly to the external client 130 (or AF 131). In these embodiments, the messages sent in stages 1 and 7 may include additional information to enable user plane delivery. The additional information may include: (I) an IP address or fully qualified domain name of the external client 130 or AF 131; (II) a location reference (to help identify the event report); (III) information that enables encryption and / or authentication of the event report; and / or (IV) an address or indication of an intermediate routing function in 5GCN 140 to which the event report is sent by LMC 117 or gNB-CU 202 via the user plane, and which subsequently routes the event report (e.g., via the user plane) to the external client 130 or AF 131.
[0210] In stage 20, the UE 102 continues to monitor for further periodic or triggering events as in stage 13, and initiates stages 14-19 each time a triggering event is detected.
[0211] The handover of the UE 102 from the source to the target gNB 110 may occur during the positioning of the UE 102 with a single position estimate for NI-LR, MT-LR, MO-LR, or an initial (and possibly final) position estimate for delayed MT-LR. When this occurs, the UE's current (source) LMC 117 may change to the new (target) LMC 117 (alternative A) or may remain unchanged (alternative B). The network operator may configure a preference or requirement for either alternative A or alternative B, or the NG-RAN 135 may simply implement one alternative instead of both (to reduce implementation).
[0212] The advantage of not changing the source LMC (in alternative B) is that ongoing UL and DL measurements for UE 102 can continue without interference while measurements continue to be sent to the original source LMC for location determination. The advantage of changing the source LMC (in alternative A) would likely be the availability of more assistance data and / or access to more neighboring gNBs for a new serving cell for UE 102. As described below, the main principle for supporting UE mobility is that state information for the location session for UE 102 can only be maintained in the current LMC and the current serving gNB-CU of UE 102. In particular, the LMC is kept updated with the identity of the current serving gNB, and the serving gNB-CU remains aware of the current LMC.
[0213] Fig.17 A single generic procedure is shown that supports the mobility of UE 102 for MO-LR, MT-LR or NI-LR procedures, and includes support for alternatives A and B described above. Fig.17 In the example, it is assumed that the source LMC 117 S and target LMC 117 T At the source gNB 110 S and target gNB 110 T In the source LMC 117 S is the source gNB-CU 202 S Part or target of LMC 117 T is the target gNB-CU 202 T In the case of a part of S Heyuan LMC 117 S Between (for phases 3, 11, 13 and 17a) or between the target gNB-CU 202 T and target LMC 117 T Between (for stages 15 and 17b) Fig.17 News in. Source LMC 117 S Located at the same location as the source gNB 110 S In a different gNB (or outside the gNB 110) or in the target LMC 117 T Located at the target gNB 110 T In the case of different gNBs (or located outside gNB 110), Fig.17 The messages in the source gNB-CU 202 are respectively S Heyuan LMC 117 S Between (for phases 3, 11, 13 and 17a) or in the target gNB-CU 202 Tand target LMC 117 T XnAP transmission branches between gNB-CUs (for phases 15 and 17b) via gNB-CUs of different gNBs (or to / from the LMC when outside any gNB 110), and therefore include an additional XnAP transmission branch between two gNB-CUs (or between a gNB-CU and an external LMC).
[0214] exist Fig.17 A prerequisite may be that the AMF 115 receives an MT-LR, MO-LR or delayed MT-LR request for the location of the UE 102, or initiates NI-LR and selects an LMC to perform UE positioning.
[0215] exist Fig.17 In stage 1, the AMF 115 sends the Nlmf_Location_DetermineLocation request service operation to the serving / source gNB-CU 202 within the NGAP DL transfer message S , as above Figure 4 As described above, in the case of MT-LR, MO-LR or NI-LR for real-time positioning, or as above Fig.16 If the AMF 115 selects a specific source LMC 117 S , then AMF 115 includes the LMC identifier.
[0216] In phase 2, if the AMF 115 does not instruct the LMC (e.g., the source gNB 110 S LMC in the source gNB-CU 202 S Select source LMC 117 S , and store location session information including a unique location session identifier (given by the source gNB-CU 202 S 102, the source gNB 110, the association ID assigned by the AMF 115, the identity of the UE 102, the S Identification and source of LMC 117 S Source gNB-CU 202 S and LMC 117 SThe location session identifier may be used to associate subsequent messages with the location session. These subsequent messages may include positioning messages and messages related to handover of the UE 102 or termination of the location session. This will enable the current serving gNB-CU to route positioning messages between the UE 102 and the current LMC even after a change of LMC, and will enable both the current serving gNB-CU and the LMC to indicate or identify the location session affected by the handover. If the location session identifier will remain unique, or may be the location session identifier of the source gNB-CU 202, the location session identifier may be used to associate subsequent messages with the location session. These subsequent messages may include positioning messages and messages related to handover of the UE 102 or termination of the location session. This will enable the current serving gNB-CU to route positioning messages between the UE 102 and the current LMC even after a change of LMC, and will enable both the current serving gNB-CU and the LMC to indicate or identify the location session affected by the handover. S If a different identifier is assigned by AMF 115, the location session identifier can be a related ID assigned by AMF 115.
[0217] In Phase 3, gNB-CU 202 S Forward the Nlmf_Location_DetermineLocation request service operation to the source LMC 117 in the F1AP transmit message S , as above Figure 8 The F1AP transmission message includes the location session identifier and the serving gNB 110. S 's logo.
[0218] In stage 4, if Fig.13 Source: LMC 117 S The received information is stored and UL and / or DL measurements may be initiated for UE 102.
[0219] In stage 5, the source gNB-CU 202 S Deciding to handover UE 102 to a new target gNB 110 T (e.g., due to the S Then, a normal handover procedure is performed as specified in, for example, 3GPP TS 38.300, 3GPP TS 38.401, 3GPP TS 37.340 and in the additional items specified below.
[0220] In stage 6, from the source gNB-CU 202 S Sent to target gNB-CU 202 T The XnAP Handover Request message includes the location session information stored in stage 2. Source gNB-CU 202 S It may also include not changing the source LMC 117 S preferences or requirements.
[0221] In stage 7, the target gNB-CU 202 T Stores location session information.
[0222] In stage 8, the target gNB-CU 202 T Identify the source LMC 117 S Whether location sessions will continue to be supported, or whether a new target LMC will be used (target gNB 110 in this example). T This determination may be based on the information received from the source gNB-CU 202 in stage 6. S If the target gNB-CU 202 T Confirmed the use of new target LMC 117 T , then in stage 7 the new target LMC 117 T The identity of the target gNB-CU 202 is stored as part of the location session information, and then T Any LPP location responses received from UE 102 for this location session will be buffered and delivered to the target LMC 117 after stage 15. T In addition, the target gNB-CU 202 T A new unique location session identifier may be allocated to replace the source gNB-CU 202 S The assigned location session identifier. If the target gNB-CU 202 T Confirm to continue using source LMC 117 S , then any LPP location response received from UE 102 for the location session may be received by target gNB-CU 202 T Sent to source gNB-CU 202 S To forward to source LMC 117 S .
[0223] In phase 9, the rest of the normal handover procedure occurs as described in 3GPP TS 38.300, 3GPP TS 38.401, 3GPP TS 37.340.
[0224] In stage 10, the target gNB-CU 202 T Towards source gNB-CU 202 S Sending is intended for source LMC 117 S XnAP Location Session Update message (or some other XnAP message) and includes the target gNB 110 T The identification of whether the new target LMC 117 will be used T 、If the target LMC 117 is used T Identification and if the source LMC 117 S The session identifier will not be changed in case of any new location.
[0225] In stage 11, the source gNB-CU 202 S Forward the XnAP location session update message in the F1AP container message to the source LMC 117 S .
[0226] In stage 12, the source gNB-CU 202 S Delete (or discard) the location session information stored in phase 2. If the new target LMC is not used 117 T , then skip stages 13-15. Source gNB-CU 202 S SHOULD wait for Phases 10 and 11 to occur before deleting the location session information at Phase 12, in order to support the possibility that the source LMC 117 may delete the location session information before Phase 11. S Any LPP message sent to UE 102. Prior to stage 11, the source LMC 117 S See source gNB 110 S is the serving gNB for UE 102, so it will send the source gNB-CU 202 S Send any LPP message intended for UE 102 to be forwarded to UE 102, such as Fig.13 Between stages 6 and 9, the source gNB-CU 202 S Can buffer from source LMC 117 S However, after phase 9 (when handover completion is confirmed), the source gNB-CU 202 S The buffered LPP message or the source LMC 117 S The received LPP message is sent to the target gNB-CU 202 T , to be forwarded to UE 102. If the source gNB-CU 202 S This is not always possible if the location session information is to be deleted before phase 11. However, after phase 11, the source LMC 117 S Know that the new serving gNB is the target gNB 110 T , and if the new target LMC 117 will not be used T , the target gNB-CU 202 may be T Any LPP messages intended for UE 102 are sent.
[0227] In phase 13, if the new target LMC 117 is to be used T , then source LMC 117 S In the F1AP container message, send the following message to the source gNB-CU 202: S Sending is intended for target LMC 117 TThe XnAP location session transfer message (or some other XnAP message) includes the target LMC 117 T Identification, target gNB 110 T The source LMC 117 receives the original Nlmf_Location_DetermineLocation request service operation from phase 3 and the current state of the location session (including the positioning capabilities of the UE 102 if received in phase 4). S The source LMC 117 then receives details of any measurements received and any outstanding measurement requests sent in phase 4. S Releases all resources for the location request.
[0228] In stage 14, the source gNB-CU 202 S Forward the XnAP location session transfer message to the target gNB-CU 202 T .
[0229] In stage 15, the target gNB-CU 202 T Forward the XnAP location session transfer message to the target LMC 117 in the F1AP transfer message T As an alternative, the XnAP location session update message in phase 11 and the XnAP location session transfer messages in phases 13 and 15 may be mapped to corresponding F1AP messages, which are transferred in place of these XnAP messages in these phases.
[0230] In phase 16, the location session continues as Fig.13 as above, but using a new target gNB 110 T As serving gNB, and source LMC 117 S Or the new target LMC 117 T (depending on whether the LMC has changed) to obtain a position estimate for UE 102. In order to S Continue, target gNB-CU 202 T Should be transmitted via the source gNB-CU 202 S Forward any LPP messages received from UE 102 for this location session to the source LMC 117 S , and source LMC 117 S Should be transmitted via the source gNB-CU 202 S Send any LPP messages intended for UE 102 to target gNB-CU 202 T to be forwarded to UE 102. In order to be transmitted by the target LMC 117 TContinue to LMC 117 T Any gNB-DU / TRP 204 / 112 from which UL location measurements were requested in phase 4 but have not yet received UL location measurements shall be notified (via the target gNB-CU 202 T ) to target LMC 117 T Instead of source LMC 117 S Send a location response.
[0231] In stage 17a, in order to S Continue to locate, source LMC 117 S Via source gNB-CU 202 in Nlmf_Location_DetermineLocation Response message S To the target gNB-CU 202 T Returns a position estimate for UE 102 (e.g., obtained using measurements obtained in stage 4 and / or stage 16). Source LMC 117 S Including target gNB-CU202 T A visible indication that the location session has ended. Then, the source LMC 117 S Releases all resources of the location session.
[0232] In phase 17b, in order to be T Continue positioning, target LMC 117 T In the F1AP transmission message, the Nlmf_Location_DetermineLocation response message is sent to the target gNB-CU 202 T Returns a position estimate for UE 102 (e.g., as obtained using measurements obtained in stage 4 and / or stage 16). Target LMC 117 T Including the target gNB-CU 202 T A visible indication that the location session has ended. Then the target LMC 117 T Releases all resources of the location session.
[0233] In stage 18, the target gNB-CU 202 T The Nlmf_Location_DetermineLocation response message is forwarded to the AMF 115 within the NGAP UL Transport message. Then, the target gNB-CU 202 T Delete (or discard) the location session information stored in stage 7.
[0234] Fig.17The procedures in stages 4-16 in are also valid for further handovers from the initial (or nearest) target gNB to an additional target gNB. In this case, Fig.17 Source gNB-CU 202 in S Heyuan LMC 117 S Corresponding to the serving gNB-CU and LMC before switching, the target gNB-CU 202 T and target LMC 117 T (when LMC changes) correspond to the new serving gNB-CU and new LMC after handover, respectively. If the source LMC is located in a different gNB than the serving gNB before handover, then Fig.17 The messages for stages 11, 13 and 17a will be sent via gNB-CUs of different gNBs and will therefore include an additional XnAP transmission branch between the two gNB-CUs as described above for the initial handover.
[0235] Figure 18 includes Fig.18A 18b, two processes for supporting the mobility of UE 102, periodically or by triggering MT-LR, are shown. Fig.16 The periodic or triggered MT-LR, the mobility of UE 102 can be Fig.16 Before sending each incident report in stage 16 and / or during Fig.16 Stages 17-18 in 3GPP TS 23.273 occur when the event report is processed by the NG-RAN. The mobility of UE 102 before the event report can be supported by allowing the change of the serving LMC using a procedure similar to that described in 3GPP TS 23.273 for periodic or triggered changes of the serving LMF of MT_LR. Fig.17 The process for UE handover described in 100 is used to support the mobility of UE 102 during the processing of event reports. In some cases, both processes may occur and are shown together in FIG. 18. In FIG. 18, the serving gNB 110 SV is the gNB that originally served the target UE 102 when the event report was sent. When the delayed routing identifier indicates the serving LMC (in this case LMC 117 S ) when the source LMC 117 S is the initial serving LMC for UE 102, or the source LMC 117 when the delayed routing identifier indicates any LMC S The serving gNB 110 SV The LMC selected for UE 102. Source gNB 110 S Is with source LMC 117 S Associated gNB. Target LMC 117 TIs due to UE 102 switching to target gNB 110 T Or a new LMC for UE 102 selected due to selection of a new serving LMC. Target gNB 110 T Is with the target LMC 117 T The associated gNB or the gNB to which the UE 102 is switched.
[0236] for Fig.17 , the state information of the location session may be maintained only in the current LMC and the current serving gNB-CU of the target UE 102. S is the source gNB-CU 202 S Part or target of LMC 117 T is the target gNB-CU 202 T In the case of a part of S Heyuan LMC 117 S between (for stages 14, 16, 19a, 19d, 22a and 22d) or between the target gNB-CU 202 T and target LMC 117 T The F1AP in FIG. 18 transmits messages between (for phases 18, 19b, 19c, 22b and 22c). At the source LMC 117 S In serving gNB 110 SV In the case of , the XnAP transfer messages for phases 4, 19d and 22d are not sent. T Located at the target gNB-CU 202 T In different gNBs (where the transmission occurs to the target gNB 110 T In the case of switching) or outside the gNB 110, the target gNB-CU 202 is sent by the gNB-CU of different gNBs respectively. T and target LMC 117 T 18 between (or to / from the external LMC) and thus includes messages between two gNB-CUs (or between the target gNB-CU 202 T and external LMCs).
[0237] In FIG. 18 , the prerequisite is that periodic or triggered MR-LR has been activated in UE 102, for example, according to Fig.16 1-12 of , and UE 102 has detected the triggering event, obtained any required location measurements, and, if necessary, obtained an RRC connection, e.g., as Fig.16 Stages 13-15.
[0238] In stage 1 of FIG. 18 , UE 102 sends a supplementary service event report message included in an RRC UL transfer message, such as Fig.16 UE 102 includes a delayed routing identifier that indicates that a particular serving LMC (in this case, source LMC 117 in FIG. 18 ) is to be used. S ) or any LMC.
[0239] In phase 2, if the delayed route identifier indicates a specific serving LMC (herein assumed to be the source LMC 117 S ), the serving gNB-CU 202 SV A different target LMC may optionally be determined (herein, target LMC 117 is assumed). T ), which may better support the location of the current serving cell of UE 102. If the delayed routing identifier indicates any LMC, gNB-CU 202 SV Select LMC, this article assumes source LMC 117 S If the delayed routing identifier indicates that the serving gNB 110 cannot be reached due to lack of Xn connectivity SV If the specific service LMC is reached, the serving gNB 110 SV You can choose a source LMC that is different from the service LMC (this article assumes that the source LMC 117 S ). The event report may then be processed as described below. However, the serving LMC will be unaware of the event report and may continue to retain state information for periodic or triggered location requests and expect to receive event reports. To avoid this, the "Any LMC" option of the delayed routing identifier may be used for all event reports.
[0240] In stage 3, the serving gNB-CU 202 SV Store location session information including the identity of UE 102, a unique location session identifier (given by the serving gNB-CU 202 SV ), the identity of the final source or target LMC determined in stage 2, the serving gNB 110 SV The identification and indication of periodic or triggered positioning.
[0241] In stage 4, the serving gNB-CU 202 SV Forward the event report to the source gNB-CU 202 in the XnAP Transmit message S , as above Figure 7 as described above, and includes the source LMC 117 as the intended recipient of the event report when determining the new target LMC in stage 2S ID of serving gNB 110 SV Identifier, location session identifier and target LMC 117 T If the target LMC 117 is identified in phase 2 T , then the serving gNB-CU 202 SV Still heading to LMC 117 S Send an event report to allow source LMC 117 S In phases 16-18, the status information of the periodic or triggered positioning is transmitted to the target LMC 117 together with the event report. T .
[0242] In stage 5, as above Figure 8 As described above, the source gNB-CU 202 S In the F1AP transmission message, the source LMC 117 S Forwarding the incident report. After phases 1-5, there are four alternative possibilities, referred to below as Case A, Case B, Case C, and Case D:
[0243] Scenario A: No target identified in Phase 2 LMC 117 T , and no handover of UE 102 occurs during the processing of the event report. For this case, stages 6-18 are not executed, and stages 19d, 20b, 21, 22d and 23b are executed to return the event report AcK to UE 102, obtain the UE location if necessary and forward the event report to 5GCN.
[0244] Case B: The target LMC 117t is determined in stage 2, and no handover of the UE 102 occurs during the processing of the event report. For this case, stages 6-15 are not performed, stages 16-18 are performed to change from the source LMC 117s to the target LMC 117t, stages 19c, 20b, 21, 22c and 23b are performed to return an event report ACK to the UE 102, obtain the UE location if necessary and forward the event report to the 5GCN.
[0245] Case C: Target LMC 117 not identified in Phase 2 T , and a UE 102 to target gNB 110 occurs during the processing of the event report T For this case, stage 6-15 is performed to switch to the target gNB 110 T , if the source LMC117 S Also changed as part of the switch to target LMC 117 T, then execute stages 16-18, and execute stages 19a or 19b, 20a, 21, 22a or 22b and 23a to return an event report AcK to UE 102, if necessary, obtain the UE location and forward the event report to 5GCN.
[0246] Scenario D: Target LMC 117 identified in Phase 2 T , and a handover of UE 102 occurs during the processing of the event report. This case is not explicitly shown in FIG. 18 , but will include the steps for case B to transfer the source LMC 117 S Change to destination LMC 117 T , then applying stage 6-15 or stage 6-18 to the target gNB 110 T Instead of the source gNB 110 S to change to a new target gNB (not shown in Figure 18) and optionally a new target LMC. Phases similar to phases 21-23 will then be performed to return an event report AcK to UE 102, obtain the UE location if necessary, and forward the event report to 5GCN.
[0247] For case C, perform the following stages 6-15.
[0248] In stage 6, when the source LMC 117 S Upon receiving the event report and if it is able to process the event report, the source LMC 117 S By source gNB-CU 202 S and serving gNB-CU 202 SV Returns a supplementary service confirmation of the event report to UE 102, such as Fig.16 If the event report requires a position estimate, the source LMC 117 S You can start the positioning process, such as Fig.13 Part of the description.
[0249] In stage 7, the serving gNB-CU 202 SV Deciding to handover UE 102 to a new target gNB 110 T (e.g., due to the SV A normal handover procedure is performed as specified in, for example, 3GPP TS 38.300, 3GPP TS 38.401, 3GPP TS 37.340 and in the additional items specified below.
[0250] In stage 8, from the serving gNB-CU 202 SV Sent to target gNB-CU 202 TThe XnAP Handover Request message includes the location session information stored in stage 3. Serving gNB-CU 202 SV It may also include not changing the source LMC 117 S preferences or requirements.
[0251] In stage 9, the target gNB-CU 202 T Stores location session information.
[0252] In stage 10, the target gNB-CU 202 T Identify the source LMC 117 S Whether location sessions will continue to be supported, or whether a new target LMC will be used (target gNB 110 in this example). T When deciding whether to determine a new LMC, the target gNB-CU 202 T This can be considered as periodic or triggered positioning and from the serving gNB-CU 202 in stage 8 SV If the target gNB-CU 202 T Confirmed the use of new target LMC 117 T , then it is stored as part of the location session information in stage 9, and the target gNB-CU 202 T Any LPP location responses received from UE 102 for this location session will be buffered and delivered to the target LMC 117 after stage 18. T In addition, the target gNB-CU 202 T A new unique location session identifier may be allocated to replace the serving gNB-CU 202 SV If the target gNB-CU 202 T Confirm to continue using source LMC 117 S , then any LPP location response received from UE 102 for the location session may be received by target gNB-CU 202 T Sent to source gNB-CU 202 S To forward to source LMC 117 S .
[0253] In phase 11, the rest of the normal handover procedure occurs as described in 3GPP TS 38.300, 3GPP TS 38.401, 3GPP TS 37.340.
[0254] In stage 12, the target gNB-CU 202 T To the serving gNB-CU 202 SVSending is intended for source LMC 117 S XnAP Location Session Update message (or some other XnAP message) and includes the target gNB 110 T Identification of whether the new target LMC will be used and if so, the target LMC 117 T Identification and if the source LMC 117 S The session identifier will not be changed in case of any new location.
[0255] In stage 13, the serving gNB-CU 202 SV Forward the XnAP location session update message to the source gNB-CU 202 S (Based on the location session information still stored from stage 3).
[0256] In stage 14, the source gNB-CU 202 S Forward the XnAP location session update message to the source LMC 117 in the F1AP transfer message S .
[0257] In stage 15, the serving gNB-CU 202 SV Delete the location session information stored in stage 3. If a new target LMC is not used, skip stages 16-18. Occurs in stages 12-14 via the serving gNB-CU 202 SV Xiangyuan LMC 117 S Send XnAP Location Session Update message and delete serving gNB-CU 202 in stage 15 only after stage 13 SV The reason for the location session information in is similar to Fig.17 An explanation is provided in Stage 12.
[0258] For Case B and Case C the following stages 16-18 are performed.
[0259] In stage 16, if due to handover to the target gNB 110 T (Case C) or source LMC 117 S Change to target LMC117 T (Case B) and the new target LMC 117 will be used T , then source LMC 117 S In the F1AP container message to the source gNB-CU202 S Sending is intended for target LMC 117 T The XnAP location session transfer message (or some other XnAP message) includes the target LMC 117 TID, serving gNB ID for case B or target gNB ID for case C (indicating the latest serving gNB for the UE), from Fig.16 The source LMC 117 receives the original Nlmf_Location_DetermineLocation service request operation from stage 7 (if this is known), the LCS Event Report message received in stage 5, the positioning capabilities of the UE 102 (if known), and the current state of the location session and the event report including the state of any measurements used for case C. S All resources used for the location request can then be released. For case B (the serving LMC receives the location request from the source LMC 117 S Change to target LMC117 T ), the XnAP location session transfer message may include or be based on the Nlmf_LocationContextTransfer request service operation for the change of the serving LMF of the MT-LR for periodic or triggered, as described in 3GPP TS 23.273. In addition, for the procedure of the change of LMF in 3GPP TS 23.273, after stage 18, the target LMC 117 may receive the Nlmf_LocationContextTransfer request service operation. T Xiangyuan LMC 117 S Return confirmation.
[0260] In stage 17, the source gNB-CU 202 S Forward the XnAP location session transfer message to the target gNB-CU 202 T .
[0261] In stage 18, the target gNB-CU 202 T Forward the XnAP location session transfer message to the target LMC 117 in the F1AP transfer message T As an alternative, the XnAP location session update message in phase 14 and the XnAP location session transfer messages in phases 16 and 18 may be mapped to corresponding F1AP messages, which are transferred in place of these XnAP messages in these phases.
[0262] For Case A, Case B and Case C the following stages 19-23 are performed.
[0263] In stage 19-20, if the event report confirmation has not been returned to UE 102, the source LMC 117 S (Case A or C) or target LMC 117 T (Case B or Case C) Send event report confirmation to serving gNB-CU 202 SV (Case A or Case B) (at stage 20a or 20b) or target gNB-CU 202T (Case C) (at stage 20c or 20d) to be transmitted to UE 102 at step 20 (at stage 21a or 21b). The event report confirmation includes a new routing identifier indicating whether the current LMC will act as the serving LMC, or indicates the default (any) LMC. If the current LMC (source LMC 117 S or destination LMC 117 T ) will act as the serving LMC, then a change of LMC due to switching to the new gNB may occur after stage 20, but the serving LMC cannot be allowed to change because UE 102 will not be aware of the change of LMC after stage 20.
[0264] In stage 21, if Fig.13 As described above, using serving gNB 110 SV (Case A or B) or target gNB 110 T (Case C) and source LMC 117 S (Case A or C) or target LMC 117 T (Case B or C) Start or continue a location session to obtain a location estimate for UE 102. To S Continuation of location session after handover (Case C), target gNB-CU 202 T Should be transmitted via the source gNB-CU 202 S Forward any LPP messages received from UE 102 for this location session to the source LMC 117 S , and source LMC 117 S Should be transmitted via the source gNB-CU 202 S Send any LPP messages intended for UE 102 to the target gNB-CU 202 T to be forwarded to UE 102. In order to T Continue after switching, target LMC 117 T Any gNB-DU / TRP 204 / 112 from which UL location measurements were requested in phase 6 but have not yet received UL location measurements shall be notified (via the target gNB-CU 202 T ) to target LMC 117 T Instead of source LMC 117 S Send a location response.
[0265] At stage 22, the current LMC (source LMC 117 S or destination LMC 117 T ) to the current serving gNB-CU (target gNB-CU 202 in FIG. 18 ) T(in phase 23a or 23b) or serving gNB-CU 202 SV (at stage 23c or 23d)) sends an event report for UE 102. The current LMC includes an indication that the location session visible to the current serving gNB-CU has ended. If not acting as the serving LMC, the current LMC may release all resources for the location session.
[0266] In stage 23, the current serving gNB-CU (target gNB-CU 202 in FIG. 18 ) T or serving gNB-CU 202 SV ) forwards the event report to AMF 115 (at stage 24a or 24b) within the NGAP UL Transport message for onward delivery to the (H-)GMLC (e.g. GMLC 125) and external client (e.g. external client 130). The current serving gNB-CU then deletes the location session information stored at stage 3 or stage 9.
[0267] Note that the event reports sent in stages 22 and 23 will be forwarded by the AMF 115 to the external client 130 (or possibly the AF 131) via the (H-)GMLC (e.g. GMLC 125) and / or NEF (e.g. NEF 127) using control plane signalling. Fig.16 As described in Stage 19 of the current LMC (source LMC 117 S or destination LMC 117 T ) or a gNB-CU connected to the current LMC can send an event report to the external client 130 (or AF 131) at the user plane level and bypass other entities such as AMF 115, GMLC 125 and NEF 127, which can achieve reduced latency.
[0268] The procedures in stages 7-18 in FIG18 are also valid for further handovers from the initial (or nearest) target gNB to an additional target gNB. In this case, the serving gNB-CU 202 in FIG18 SV Heyuan LMC 117 S Corresponding to the serving gNB-CU and LMC before switching, the target gNB-CU 202 in FIG. 18 T and target LMC 117 T (When LMC changes) correspond to the new serving gNB-CU and new LMC after switching respectively.
[0269] By not changing the LMC of UE 102 after handover while a location session is ongoing, the Fig.17and 18. The location session typically takes less than 30 seconds (e.g., this is the maximum time allowed for locating an E911 call in the United States), and for low-latency user cases, only a few seconds or less than a second. This has two implications. First, handovers will be a rare event, and more than one handover is extremely rare. Second, the UE 102 will not move very far (e.g., at 100 km / h, the UE 102 will move 833 meters in 30 seconds and 56 meters in 2 seconds). Therefore, although the LMC may have to request additional UL or DL measurements of new serving cells applicable to the UE 102, it is unlikely that the LMC will not have connectivity to any new neighboring gNBs required to support these new measurements, or will not be configured with or able to access the associated assistance data to enable the UE to determine position from the new measurements.
[0270] If a change of LMC is not supported after handover of UE 102 during a location session, the process can be simplified by removing stages 7, 13, 14, and 17b. Fig.17 Similarly, the process in FIG. 18 can be simplified by removing stage 10, stages 16-18 for case C, and stages 19b and 22b.
[0271] Fig.17 The process described in FIG. 18 assumes that the UE handover is Xn-based and therefore occurs directly between gNBs 110, rather than via AMF 115. For N2-based handover of UE 102 via AMF 115 (e.g., as described in 3GPP TS 23.502), the source gNB 110 S The source gNB 110 may be configured with information indicating whether any location session can continue or needs to be aborted. S and new target gNB 110 T The location session may need to be aborted if there is no Xn connectivity (direct or indirect) between the LMC 117 and the NG-RAN, or if the current serving AMF 115 for the immediate location request (NI-LR, MT-LR or MO-LR) needs to change. When using the LMF 120, a change of the serving AMF 115 also results in abortion of the request for immediate location, so if there is extensive NG-RAN Xn interconnectivity, aborting the location session of the LMC 117 does not require degradation of service compared to using the LMF 120.
[0272] If the source gNB 110 S Decide to continue the location session (and assume that the source gNB 110 S and target gNB 110 T There is NG-RAN Xn interconnection between them), then Fig.17The process in Figure 18 can be continued, but there is one difference. The difference is that in Fig.17 18 or stage 8 is sent to the target gNB-CU 202 T The location session information may be included as part of the source to target transparent container in phase 1 of the N2 handover procedure in 3GPP TS 23.502.
[0273] If the source gNB 110 S If the LMC decides to terminate the location session, it may send a termination message to the current LMC, and the current LMC may then terminate the positioning and return to the source gNB 110. S Any location estimate of the target UE 102 may be forwarded to the currently serving AMF 115. If the source AMF 115 has not changed, the NI-LR, MT-LR or MO-LR request may be fulfilled by the AMF 115. If the source AMF 115 has changed as a result of a handover, the source AMF 115 itself may be forwarded to the target UE 102 from the source gNB 110. S The location request is aborted before receiving a location estimate, or the location estimate can be waited for if there is time (depending on how quickly the handover proceeds).
[0274] As described in 3GPP TS 23.273, support for location privacy of the target UE 102 is a 5GCN function supported by UE subscription data in the UDM, verification and enforcement of privacy by the NEF or GMLC and, when subscribed, notification and verification of privacy with the target UE 102 before returning location information to an external client or AF. These functions are not limited or affected by positioning the target UE 102 using the LMC 117 in the NG-RAN instead of using the LMF 120 in the 5GCN. For example, the process described herein for positioning the target UE 102 using the LMC 117 includes stages for supporting privacy as follows: MT-LR for immediate positioning, in Fig.11 Phases 1, 3, and 8 in MT-LR for delayed positioning, Fig.16 Stages 1, 5 and 19 in the.
[0275] When LMF 120 is used to support location of target UE 102, as defined in 3GPP TS 23.273, LPP and SS messages exchanged between target UE 102 and serving AMF 115 or LMF 120 to support the location shall be securely protected by encryption at the NAS level and possibly the AS level.
[0276] When the LMC 117 in the NG-RAN 135 is used to support the location of the target UE 102, as described herein, the LPP and SS messages exchanged between the target UE 102 and the LMC 117 to support the location will be securely protected by encryption at the AS level, provided that these messages are sent after the serving gNB 110-1 has activated AS security. For UEs transitioning from the CM-IDLE state to the CM-CONNECTED state, as described in 3GPP TS 38.300 and 38.413, AS security may be activated after the serving gNB 110-1 receives the NGAP INITIAL CONTEXT SETUP REQUEST message from the serving AMF 115. This occurs after the UE 102 has entered the RRC CONNECTED state and has sent a NAS SERVICE REQUEST to the serving AMF 115, as part of a UE-triggered service request or a network-triggered service request as defined in 3GPP TS 23.502. If the serving gNB 110-1 keeps the UE 102 in the RRC and CM CONNECTED states for the duration of the location session (e.g., due to knowledge of the start and end of the location session, such as Fig.17 and Figure 18), AS encryption can also remain active.
[0277] For this article Figure 11-13 and Fig.15 The MT-LR, NI-LR, and MO-LR processes described in Fig.16 The initial activation of the delayed MT-LR in stages 1-12, the signaling between the UE 102 and the LMC 117 occurs after a UE-triggered service request or a network-triggered service request has occurred, so AS security will be active. Fig.14 For RAN-initiated positioning as described in , the serving gNB 110-1 may also restrict usage to cases where AS security is already active (which should cover almost all cases where UE location is required). Fig.16 For sending a delayed MT-LR event report for periodic or triggered positioning and for the subsequent return of an event report confirmation and possible positioning of UE 102, if the UE was already in CM CONNECTED state before stages 16-18 (e.g., except in Fig.16AS security will be active if, in addition to establishing an RRC connection in stage 15 of 3GPP TS 23.273, UE-triggered service request is performed. As described in clause 6.3.1 of 3GPP TS 23.273, event reporting for triggered or periodic positioning using LMF 120 requires a UE-triggered service request, so using this request for LMC 117 does not introduce additional signaling overhead compared to using LMF 120. However, this may not be desirable because LMC 117 is intended to reduce signaling and associated delays.
[0278] One way to avoid the additional overhead of a full UE-triggered service request for event reporting for periodic or triggered positioning is to keep the UE 102 in the RRC INACTIVE state when not otherwise reporting events or engaging in other signaling or data transfer activities. This will allow for a more efficient transition to the RRC and CM CONNECTED states with AS security, as described in 3GPP TS 38.300. Upon initial knowledge of a periodic or triggered location session (e.g., as described in FIG. 18 ) or upon notification of this by the initial serving AMF 115, the serving gNB 110-1 may retain information indicating a preference for the target UE 102 to use the RRC INACTIVE state rather than the RRC IDLE state.
[0279] If UE 102 transitions to RRC IDLE state between consecutive event reports and does not perform a complete UE-triggered service request before sending the next event report, as described above, then Fig.16 The event reporting, event reporting confirmation, and any positioning messages sent during stages 16-18 of the present invention will not be protected by AS security. To provide security for this situation, when delayed periodic or triggered positioning is first activated, the messages transmitted between the target UE 102 and the LMC 117 may be encrypted based on security information stored in the UE 102 and the LMC 117. For example, the LMC 117 may be configured to provide a secure location service for the target UE 102 and the LMC 117. Fig.16 The LMC 117 may distribute the encryption key to itself or may transmit the encryption key to the UE 102 in stage 9 (while AS security is still active). Fig.16 The encryption key is received from AMF 115 in stage 7 of UE 102. Such encryption between UE 102 and LMC 117 will require LMC 117 to act as a serving LMC, where LMC 117 maintains state information for periodic or triggered positioning and provides a delayed routing identifier indicating the identifier of LMC 117 to UE 102.
[0280] Fig.191 shows a process in which the NG-RAN LMC 117 and the 5GCN LMF 120 coexist and the AMF 115 determines the appropriate 5GCN LMF 120 or NG-RAN LMC 117 for position estimation of the target UE 102 or for providing assistance data to the target UE 102. Figure 4 and Figure 11-16 As shown, 5GCN LMF 120 and NG-RAN LMC 117 can coexist in the network. The LMF 120 selection criteria defined in 3GPP TS 23.273 can take into account the availability of NG-RAN LMC.
[0281] exist Fig.19 In phase 1, the serving AMF 115 receives a Namf_Location_ProvidePositioningInfo request (in the case of MT-LR) from the LCS entity 125 (in phase 1a), receives an emergency registration for an IMS emergency call from the UE (in the case of NI-LR) (in phase 1c) or receives a SS MO-LR request (in the case of MO-LR) (in phase 1b). In response, the AMF 115 initiates the positioning procedure.
[0282] In stage 2, in all cases, the AMF 115 may determine a suitable 5GCN LMF 120 or NG-RAN LMC 117 for position estimation of the target UE 102 or for providing assistance data to the target UE 102.
[0283] In phase 3, the serving AMF 115 sends a Nlmf_Location_DetermineLocation request to the selected 5GCN LMF 120 (in phase 3a) or to the selected LMC 117 within a NGAP DL Transfer message.
[0284] The feasibility and specification implications of the location management functionality in NG RAN, referred to as the Location Management Component (LMC), are described above. Some key observations and conclusions can be summarized as follows.
[0285] 1.) The LMC 117 may be part of the gNB-CU 202 or may be a separate entity within the gNB 110 connected to the gNB-CU 202 via the F1 interface. 2.) Existing location protocols (developed by 3GPP for 5GCN location services and NR positioning support) may be reused for positioning using the LMC 117 in the NG-RAN 135 (i.e., 3GPP TS 29.572, 3GPP TS37.355, 3GPP TS 24.080, 3GPP TS 38.455). These enable the AMF 115 to treat the LMC 117 in a manner similar to that of the LMF 120 and enable the LMC 117 to function in a manner similar to that of the LMF 120. 3.) The impact of supporting LMC 117 in NG-RAN 135 on existing RAN protocols may be mainly limited to the specification of new UL / DL transport message containers in NGAP, RRC, XnAP and F1AP protocols, which can transport the various location protocol PDUs in item 2 above. 4.) Location service procedures for immediate MT-LR, NI-LR, MO-LR and delayed MT-LR can also be supported by the RAN LMC. Compared with the corresponding 5GCN location service procedures using LMF 120 specified in 3GPP TS23.273, the differences are mainly in the UE positioning procedures (LPP, NRPPa), which can remain functionally the same as those using LMF 120, but with higher signaling efficiency. 5.) UE mobility during immediate positioning or delayed positioning can be supported by two alternatives: (a) the source LMC for the UE can be changed to a new (target) LMC, or (b) it can remain unchanged. 6.) To support UE mobility, the state information of the location session may be maintained only in the current LMC and the current serving gNB-CU. The LMC may be updated with the identity of the current serving gNB, and the serving gNB-CU remains aware of the current LMC. 7.) To support the updating and transfer of the location session state information in accordance with item 6, the following XnAP changes may be introduced: (a) the location session information may be included in the XnAP Handover Request message, and (b) a new XnAP procedure may be defined to update and transfer the location session information between the source and target gNB-CU. 8.) Location privacy is a 5GCN feature as specified in 3GPP TS 23.273 and is not limited or affected by the use of the LMC in NG-RAN instead of the LMF in 5GCN to locate the target UE. 9.) The LPP and SS messages exchanged between the target UE and the LMC to support the location may be securely protected by encryption at the AS level, provided that these messages are sent after the serving gNB has activated AS security. 10.) By considering the availability of LMC in the LMF selection process performed by AMF, NG-RAN LMC and 5GCN LMF can co-exist in the network.
[0286] FIG. 20 shows a diagram illustrating a first new radio (NR) Node B (gNB) in a radio access network (RAN) such as NG-RAN 135, which is provided by a first central unit (CU) (e.g. Fig.17 Source gNB-CU 202 in S or the source gNB-CU 202 in FIG. 18 S or serving gNB-CU 202 SV ) is performed by a method for supporting a location session of a user equipment (UE) (e.g., UE 102).
[0287] Process flow 2000 may begin at block 2002, where the CU receives a first positioning message for a UE from a first entity, such as in Fig.17 In block 2004, the CU determines a first location management component (LMC), such as Fig.17 At block 2006, the CU stores first information of the location session, the first information of the location session including an identifier of the first LMC, an identifier of the UE, and a first identifier of the location session, for example, as described in Fig.17 In block 2008, the CU forwards the first positioning message to the first LMC, for example, as discussed in stage 2 of FIG. 18 or stage 3 of FIG. Fig.17 In block 2010, the CU performs a handover of the UE to a second gNB, whereby the second gNB supports continuation of the location session, e.g., as discussed in stage 3 of FIG. 18 or stage 4 of FIG. 18 . Fig.17 18 or stages 7-15 (or 7-18) discussed above.
[0288] In one embodiment, the first gNB (e.g., serving gNB 110 SV or source gNB 110 S ) is the serving gNB of the UE before the handover, and the second gNB (e.g., target gNB 110 T ) is the serving gNB of the UE after handover, such as Fig.17 As shown in Figure 18.
[0289] In one embodiment, the first LMC is part of the first CU, wherein the first positioning message is forwarded to the first LMC within the first CU, for example, Fig.17 and discussed in relation to FIG. 18 .
[0290] In one embodiment, the first LMC is part of the first gNB and is separate from the first CU, wherein forwarding the first positioning message to the first LMC includes sending the first positioning message to the first LMC in an F1 Application Protocol (F1AP) transmit message, such as Fig.17 and discussed in relation to FIG. 18 .
[0291] In one embodiment, the first LMC is a third gNB (e.g., gNB 110 in FIG. 18 ). S ), wherein forwarding the first positioning message to the first LMC includes sending the first positioning message to a third gNB in an Xn Application Protocol (XnAP) transmission message, for example, as discussed in FIG. 18 .
[0292] In one embodiment, forwarding the first positioning message to the first LMC further comprises forwarding at least some of the first information of the location session together with the first positioning message to the first LMC, for example, Fig.17 and Stage 4 of Figure 18 as discussed above.
[0293] In one embodiment, the process may further include the CU receiving a second positioning message from the first LMC, the second positioning message including the first identifier of the location session. The CU may send the second positioning message to the UE based on the first information of the location session.
[0294] In one embodiment, the process may further include the CU receiving a second positioning message from the UE, the second positioning message including the first identifier of the location session. The CU may send the second positioning message to the first LMC based on the first information of the location session.
[0295] In one embodiment, the CU performs the handover to the second gNB by: determining to handover the UE to the second gNB, sending a handover request message to the second gNB, the handover request message including the first information of the location session, and completing the handover of the UE to the second gNB, as in Figure 7 The CU also receives a location session update message from the second gNB, sends a location session update message to the first LMC, and deletes the first information of the location session, the location session update message including the identifier of the second gNB, for example, as in Fig.17 as discussed in stages 10, 11 and 12 of FIG. 18 or stages 12, 13 and 15 of FIG. 18 .
[0296] In one embodiment, a second CU in the second gNB (e.g., gNB-CU 202 T) receives a handover request message, wherein the second CU stores second information of the location session, the second information of the location session including at least a portion of the first information of the location session, wherein the second CU sends a location session update message to the first CU, for example, as in Fig.17 18 and stages 6, 7 and 10 and stages 8, 9 and 12 of FIG. 18 .
[0297] In one embodiment, wherein the second CU allocates a second identifier for the location session, the second identifier for the location session is different from the first identifier for the location session, the second information for the location session includes the second identifier for the location session, and the location session update message may include the second identifier for the location session, for example, as in Fig.17 8 and stage 10 of FIG. 18 .
[0298] In one embodiment, the second CU determines the second LMC, the second LMC is different from the first LMC, the second information of the location session includes the identifier of the second LMC, and the location session update message may include the identifier of the second LMC, for example, as in Fig.17 As discussed in stage 8 of FIG. 18 and stage 10 of FIG. 18 . In one embodiment, the second LMC obtains a position estimate of the UE.
[0299] In one embodiment, the first entity is an access and mobility management function (AMF), such as AMF 115, wherein the first positioning message is a Nlmf_Location_DetermineLocation request service operation, wherein the first positioning message is received within an NGAP DL transport message, such as Fig.16 Stage 7 and Fig.17 as discussed in Phase 1.
[0300] In one embodiment, the process may also include the CU receiving a Nlmf_Location_DetermineLocation response service operation from the first LMC, wherein the Nlmf_Location_DetermineLocation response service operation includes a location estimate of the UE, such as in Fig.14 The CU may send a Nlmf_Location_DetermineLocation response service operation to the AMF within a NGAP UL Transport message, for example, as described in Stage 3 of the NGAP UL Transport message. Fig.16 The CU may delete the first information of the location session, for example, as in Fig.17 as discussed in Stage 12 of this document.
[0301] In one embodiment, the first entity is a UE, wherein the first positioning message includes an event report for periodic or triggered positioning of the UE and a routing identifier, the routing identifier indicating any LMC or serving LMC, and the processing flow 2000 may further include determining the first LMC based at least in part on the routing identifier, for example, as discussed in stages 1 and 2 of Figure 18.
[0302] In one embodiment, the routing identifier indicates a serving LMC, wherein the first LMC is different from the serving LMC, and wherein forwarding the event report to the first LMC includes sending the event report and an indication of the first LMC to the serving LMC, for example, as discussed in stages 1 and 2 of FIG. 18 .
[0303] In one embodiment, the serving LMC sends a location session transfer message to the first LMC, the location session transfer message including the event report and the current status of periodic or triggered event reporting of the UE, for example, as discussed in stage 13 of FIG. 18 .
[0304] In one embodiment, location-related signaling may be transmitted in container messages of corresponding application protocols, including a radio resource control (RRC) container for LPP messages on the air interface, an NG-AP container for location-related messages on the NG interface, an Xn-AP container for location-related messages on the Xn interface, and an F1AP container for location-related messages on the F1 interface.
[0305] In one embodiment, the first LMC obtains a position estimate of the UE.
[0306] FIG. 21 shows a diagram illustrating a first new radio (NR) Node B (gNB) in a radio access network (RAN) such as NG-RAN 135, which is composed of a first central unit (CU) (e.g. Fig.17 and the target gNB-CU 202 in 18 T ) is performed by a method for continuing a location session of a user equipment (UE) (e.g., UE 102).
[0307] Process flow 2100 may begin at block 2102, where a CU receives a request from a second gNB (e.g., gNB 202 S or 202 SV ) receives a first handover request message from the UE, the first handover request message includes first information of the location session, the first information of the location session includes an identifier of a first location management component (LMC), an identifier of the UE, and a first identifier of the location session, for example, as in Fig.17In block 2104, the CU stores second information for the location session, the second information for the location session including at least a portion of the first information for the location session, for example, as discussed in step 6 of FIG. 18 or step 8 of FIG. 18. Fig.17 In block 2106, the CU completes handover of the UE from the second gNB to the first gNB, e.g., as discussed in stage 7 of FIG. 18 or stage 9 of FIG. 18. Fig.17 18 or stage 11. In block 2108, the CU determines a second LMC, wherein the second LMC is the first LMC or is different from the first LMC, for example, as in Fig.17 8 or stage 10 in FIG. 18. In block 2110, when the second LMC is different from the first LMC, the CU includes an identification of the second LMC in the second information of the location session, for example, as in Fig.17 In block 2112, the CU sends a first location session update message to the first gNB, and when the second LMC is different from the first LMC, the first location session update message includes an identifier of the second gNB and an identifier of the second LMC, for example, as in Fig.17 as discussed in stage 10 in FIG. 10 or stage 12 in FIG. 18 .
[0308] In one embodiment, the second gNB (e.g., serving gNB 110 SV or source gNB 110 S ) is the serving gNB of the UE before the handover, and the first gNB (e.g., target gNB 110 T ) is the serving gNB of the UE after handover, such as Fig.17 As shown in Figure 18.
[0309] In one embodiment, the process further includes the CU determining a second identifier for the location session, wherein the second identifier for the location session is the same as or different from the first identifier for the location session, for example, as in Fig.17 When the second identifier of the location session is different from the first identifier of the location session, the CU may include the second identifier of the location session in both the second information of the location session and the first location session update message sent to the second gNB, for example, as in Fig.17 8 and 10 of FIG. 18 and stages 10 and 12 of FIG. 18 are discussed above.
[0310] In one embodiment, a second CU in the second gNB receives a first location session update message sent by the first CU, wherein the second CU sends the first location session update message to the first LMC, for example, as in Fig.17 11 of FIG. 18 and stages 13 and 14 of FIG. 18 are discussed above.
[0311] In one embodiment, the process further includes the CU receiving a positioning message from the second LMC, the positioning message including a second identifier of the location session. The CU may send the positioning message to the UE based on the second information of the location session.
[0312] In one embodiment, the positioning message comprises an event report confirmation or LPP message for periodic or triggered positioning, for example, as discussed in stage 22b of Figure 18.
[0313] In one embodiment, the process further includes the CU receiving a positioning message from the UE, the positioning message including a second identifier of the location session, for example, as in Fig.16 The CU may send a positioning message to the second LMC based on the second information of the location session, for example, as in Fig.16 as discussed in Stage 16 of this document.
[0314] In one embodiment, the process further includes the CU determining to hand over the UE to a third gNB, such as Fig.17 As discussed in FIG. 18 . The CU may send a second handover request message to the third gNB, the second handover request message including the second information for the location session. The CU may complete the handover of the UE to the third gNB. The CU may receive a second location session update message from the third gNB, the second location session update message including the identifier of the third gNB. The CU may send a second location session update message to the second LMC. The CU may delete the second information of the location session.
[0315] In one embodiment, the process may also include the CU receiving from the second LMC a positioning message intended for the UE's service access and mobility management function (e.g., AMF 115) and an indication of location session termination, e.g., as in Fig.17 The CU may send a positioning message to the UE's serving AMF, for example, as discussed in stage 17b of FIG. 18 or stage 22b of FIG. 18. Fig.17 The CU may delete the second information of the location session, for example, as discussed in stage 18 of FIG. 18 or stage 23a of FIG. Fig.17 18 or stage 23a in FIG. 18 .
[0316] In one embodiment, the positioning message includes an event report or Nlmf_Location_DetermineLocation response service operation for periodic or triggered positioning, such as in Fig.17 as discussed in stages 1 and 6 of or stages 1 and 8 of FIG. 18 .
[0317] In one embodiment, location-related signaling may be transmitted in container messages of corresponding application protocols, including a radio resource control (RRC) container for LPP messages on the air interface, an NG-AP container for location-related messages on the NG interface, an Xn-AP container for location-related messages on the Xn interface, and an F1AP container for location-related messages on the F1 interface.
[0318] In one embodiment, the second LMC obtains a position estimate of the UE.
[0319] FIG. 22 shows a diagram of a first new radio (NR) Node B (gNB) in a radio access network (RAN) such as NG-RAN 135, wherein a first location management component (LMC) (e.g. Fig.17 and 18 in the source LMC 117 S or destination LMC 117 T ) is performed by a processing flow 2200 method for supporting a location session of a user equipment (UE) (e.g., UE 102).
[0320] Process flow 2200 may begin at block 2202, where a first LMC receives a first positioning message for a UE from a first entity, the first positioning message being relayed to the first LMC by a central unit (CU) of a first gNB, the first positioning message initiating a location session for the UE in the first LMC, the first positioning message including an identification of a source gNB, a source gNB serving the UE, and an identifier of a location session, e.g., as in Fig.17 In stage 2204, the first LMC sends at least one positioning message for the UE to the second entity, for example, as discussed in stages 3 and 15 of FIG. 18 or stages 5 and 18 of FIG. Fig.17 In an alternative embodiment, instead of sending at least one positioning message in stage 2204, the first LMC may receive at least one positioning message from the UE to the second entity, for example, as in Fig.17 In stage 2206, the first LMC receives a location session update message indicating a handover of the UE from the source gNB to the target gNB, the location session update message indicating whether a second LMC is assigned, the location session update message including an identifier of the second LMC when the second LMC is assigned, as in Fig.17 In stage 2208, when no second LMC is assigned, the first LMC continues to support the location session using the target gNB, as discussed in stage 11 of FIG. 18 or stage 14 of FIG. 18. Fig.17In stage 2210, when the second LMC is assigned, the first LMC sends a location session transfer message to the second LMC, the location session transfer message including the current state of the location session and the first positioning message, as discussed in stage 8 and 17a of FIG. 18 or stage 10 and 19d of FIG. 18. Fig.17 as discussed in stage 13 of FIG. 18 or stage 16 of FIG. 18 .
[0321] In one embodiment, when the first LMC is part of the CU, the relay is inside the CU, wherein when the LMC is not part of the CU, the relay transmits messages using the F1 Application Protocol (F1AP), e.g. Fig.17 and discussed in relation to FIG. 18 .
[0322] In one embodiment, when the first gNB is different from the source gNB, the first LMC receives a first positioning message from the first entity via the source gNB, for example, Fig.17 and discussed in relation to FIG. 18 .
[0323] In one embodiment, the first entity is an access and mobility management function (AMF), such as AMF 115, wherein the first positioning message includes an Nlmf_Location_DetermineLocation request service operation, such as Fig.17 as discussed in Phase 3.
[0324] In one embodiment, the first entity is a UE, wherein the first positioning message includes an event report for periodic or triggered positioning of the UE, for example, as in Fig.17 as discussed in Phase 5.
[0325] In one embodiment, the first entity is a third LMC, wherein the first positioning message comprises a location session transfer message, wherein the location session transfer message comprises the second positioning message, for example, as discussed in stage 18 of FIG. 18 .
[0326] In one embodiment, the second positioning message includes an event report for periodic or triggered positioning of the UE, wherein the source gNB receives the event report and an indication of a third LMC from the UE, wherein the source gNB determines the first LMC, and wherein the source gNB sends the event report together with the indication of the first LMC to the third LMC, for example, as discussed in stage 18 of Figure 18.
[0327] In one embodiment, in response to a handover of the UE from the second gNB to the source gNB, a location session transfer message is sent by the third LMC, wherein the source gNB determines the first LMC, wherein the source gNB sends a location session update message to the third LMC via the second gNB, the location session update message including an identifier of the first LMC, for example, as in Fig.17as discussed in stage 15 of FIG. 18 or stage 18 of FIG. 18 .
[0328] In one embodiment, the second positioning message includes an event report previously sent by the UE for periodic or triggered positioning, or an Nlmf_Location_DetermineLocation request service operation previously sent by a service access and mobility management function (AMF) for the UE, for example, as in Fig.17 as discussed in stage 15 of FIG. 18 or stage 18 of FIG. 18 .
[0329] In one embodiment, the second entity is a UE, wherein the first LMC sends at least one positioning message to the UE by sending a downlink positioning message to the UE via the first CU and the source gNB. For example, the first LMC may also receive an uplink positioning message from the UE via the first CU and the source gNB, such as Fig.13 discussed.
[0330] In one embodiment, the second entity is a UE, wherein the first LMC may receive at least one positioning message of the UE by receiving an uplink positioning message from the UE via the first CU and the source gNB, for example, Fig.13 As discussed. The first LMC may also send a downlink positioning message to the UE via the first CU and the source gNB.
[0331] In one embodiment, the downlink positioning message and the uplink positioning message each include an identifier of the location session, wherein the downlink positioning message is routed by the source gNB to the UE based on the identifier of the location session, wherein the uplink positioning message is routed by the source gNB to the first LMC based on the identifier of the location session, for example, as in Fig.17 or as discussed in Stage 2 of Figure 18.
[0332] In one embodiment, the downlink positioning message is a LCS periodically triggered location call message, a periodic or triggered positioning event report confirmation or an LPP message, for example, as in Fig.17 and discussed in relation to FIG. 18 .
[0333] In one embodiment, the uplink message is a location return result message or an LPP message periodically triggered by the LCS, for example, Fig.17 and 18 discussed.
[0334] In one embodiment, the second entity is a distributed unit (DU) in the gNB, wherein the first LMC sends at least one positioning message to the DU by sending a downlink network positioning message to the DU via the first CU. The first LMC may also receive an uplink network positioning message from the DU via the first CU, for example, Fig.13discussed.
[0335] In one embodiment, the second entity is a distributed unit (DU) in the gNB, wherein the first LMC may receive an uplink network positioning message from the DU via the first CU, for example, Fig.13 The first LMC may also send at least one positioning message to the DU by sending a downlink network positioning message to the DU via the first CU.
[0336] In one embodiment, the downlink network positioning message and the uplink network positioning message each include an NRPPa message or a F1AP message that can be mapped to the NRPPa message, for example, Fig.13 discussed.
[0337] In one embodiment, when the second LMC is not allocated, the first LMC continues to support the location session using the target gNB by at least one of: sending a downlink positioning message to the UE via the CU and the target gNB; receiving an uplink positioning message from the UE via the CU and the target gNB; sending a downlink network positioning message to a distributed unit (DU) in the gNB via the CU; receiving an uplink network positioning message from the DU via the CU; or sending a second positioning message to the first entity via the CU and the target gNB, for example, Fig.13 , Fig.17 and discussed in relation to FIG. 18 .
[0338] In one embodiment, the downlink positioning message and the uplink positioning message each include an LPP message, wherein the downlink network positioning message and the uplink network positioning message each include an NRPPa message or an F1AP message that can be mapped to the NRPPa message, wherein the second positioning message includes an event report confirmation or an Nlmf_Location_DetermineLocation request service operation for periodic or triggered positioning when the first entity includes a UE or an event report for periodic or triggered positioning when the first entity includes an AMF, for example. Fig.13 , Fig.17 and discussed in relation to FIG. 18 .
[0339] In one embodiment, when the second LMC is assigned, the second LMC uses the target gNB to continue supporting the location session, for example, as in Fig.17 Stages 15 and 16 and Fig.19 Stages 18 and 21 are discussed.
[0340] In one embodiment, location-related signaling may be transmitted in container messages of corresponding application protocols, including a radio resource control (RRC) container for LPP messages on the air interface, an NG-AP container for location-related messages on the NG interface, an Xn-AP container for location-related messages on the Xn interface, and an F1AP container for location-related messages on the F1 interface.
[0341] In one embodiment, when the second LMC is not assigned, the first LMC obtains a position estimate for the UE.
[0342] 23 is a diagram showing an example of a hardware implementation of a source central unit (CU) 2300 in a wireless network such as NG-RAN 135. The source CU 2300 may be provided by (or connected to) a serving or source NG-RAN node entity (e.g., serving gNB 110). SV or source gNB 110 S ) and may be, for example, part of a wireless network such as a 5G core network (5GCN) (e.g., 5GCN 140). The source CU 2300 may include hardware components, such as, for example, an external interface 2302, which may be a wired or wireless interface capable of connecting to the AMF 115 via an NG interface, or to other nodes within the RAN (e.g., neighboring gNBs 110-2 or 110-3) using an Xn Application Protocol (XnAP) or a location specific protocol (e.g., NR Positioning Protocol A (NRPPa)) transmitted over XnAP, and to other CUs or location management components (LMCs) within other gNBs. For example, if the source CU 2300 is within a gNB 110, the source CU 2300 may also include an internal interface 2304 that is capable of connecting to a location management component (LMC) such as LMC 117, a distributed unit (DU) such as gNB-DU 204, and a transmission reception point (TRP) via an F1 interface, which may include a reception point (RP) and a transmission point (TP), such as TRP 112, RP 113, and TP 111 within the same gNB 110. The source CU node 2300 also includes one or more processors 2308 and a memory 2310, which may be coupled together via a bus 2306. The memory 2310 may store data and may contain executable code or software instructions that, when executed by the one or more processors 2308, cause the one or more processors 2308 to operate as a special-purpose computer programmed to perform the processes and techniques disclosed herein (e.g., such as the process flow 2000 discussed in FIG. 20).
[0343] 23, memory 2310 includes one or more components or modules that, when implemented by one or more processors 2308, implement the methods described herein. Although the components or modules are illustrated as software in memory 2310 that can be executed by one or more processors 2308, it is understood that the components or modules can be dedicated hardware within or outside the processor 2308.
[0344] As shown, the memory 2310 may include a receive positioning message unit 2320, which, when implemented by the one or more processors 2308, configures the one or more processors 2308 to receive a positioning message for a UE (e.g., UE 102) from an entity such as AMF 115 or UE 102, for example, via the external interface 2302 and / or the internal interface 2304, for example, as in blocks 2002 and 2003 of FIG. Fig.17 18 or stage 1. For example, the one or more processors 2308 may be further configured to receive a second positioning message from the LMC or the UE, the second positioning message including the first identifier of the location session. When implemented by the one or more processors 2308, the determining LMC unit 2322 configures the one or more processors 2308 to determine a location management component (LMC), for example, as in blocks 2004, Fig.17 18 or stage 2. When implemented by one or more processors 2308, the storage location session information unit 2324 configures the one or more processors 2308 to store information of the location session, for example, in the memory 2310, the information including the identification of the LMC, the identification of the UE, and the identifier of the location session, for example, as in blocks 2006, Fig.17 18 or stage 3. The one or more processors 2308 may be further configured to delete the stored information. When implemented by the one or more processors 2308, the forwarding positioning message unit 2326 configures the one or more processors 2308 to forward the positioning message to the LMC, for example, via the external interface 2302 and / or the internal interface 2304, for example, as in blocks 2008, Fig.1718 or stage 4. For example, the one or more processors 2308 may be further configured to forward at least some of the information of the location session, such as the identifier of the first LMC, the identifier of the UE, and the first identifier for the location session, and the positioning message. The one or more processors 2308 may also be configured to send a second positioning message to the LMC based on the first information of the location session. When implemented by the one or more processors 2308, the switching unit 2328 configures the one or more processors 2308 to perform a handover of the UE to the second gNB, whereby the second gNB supports the continuation of the location session, for example, as in blocks 2010, Fig.17 18 or stages 5-12 or stages 7-15 (or 18) in FIG. 18 . For example, one or more processors 2308 may be configured to perform handover by determining to handover the UE to a second gNB, sending a handover request message to the second gNB, the handover request message including first information of the location session; completing the handover of the UE to the second gNB; receiving a location session update message from the second gNB, the location session update message including an identifier of the second gNB; sending a location session update message to the first LMC; and deleting the first information of the location session. When implemented by the one or more processors 2308, the location response unit 2330 configures the one or more processors 2308 to receive a location response, such as an Nlmf_Location_DetermineLocation response message, from the LMC, which may include a location estimate, and sends the location response message to the AMF within an NGAP UL transmission message, such as Fig.14 Phase 3 and Fig.16 As discussed in Stage 11 of this document.
[0345] The methods described herein can be implemented in various ways depending on the application. For example, the methods can be implemented in hardware, firmware, software, or any combination thereof. For hardware implementations, one or more processors can be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or a combination thereof.
[0346] For implementations involving firmware and / or software, the methods may be implemented using modules (e.g., procedures, functions, etc.) that perform the individual functions described herein. Any machine-readable medium that specifically embodies instructions may be used to implement the methods described herein. For example, software codes may be stored in a memory (e.g., memory 2310) and executed by one or more processor units (e.g., processor 2308), such that the processor units operate as special-purpose computers programmed to perform the techniques and processes disclosed herein. The memory may be implemented inside the processor unit or outside the processor unit. As used herein, the term "memory" refers to any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type of memory or amount of memory, or the type of medium in which the memory is stored.
[0347] If implemented in firmware and / or software, the functions may be stored as one or more instructions or codes on a non-transitory computer-readable storage medium. Examples include computer-readable media encoded with data structures and computer-readable media encoded with computer programs. Computer-readable media include physical computer storage media. The storage medium may be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, semiconductor memory or other storage device, or any other medium that can be used to store the required program code in the form of instructions or data structures and can be accessed by a computer; disks and optical disks used herein include compact disks (CDs), laser optical disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, where disks typically reproduce data magnetically, while optical disks reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.
[0348] In addition to storage on a computer-readable storage medium, instructions and / or data may be provided as signals on a transmission medium included in the communication device. For example, the communication device may include a transceiver with signals indicating instructions and data. Instructions and data are stored on a non-transitory computer-readable medium (e.g., memory 2310) and are configured to cause one or more processors (e.g., processor 2308) to operate as a special-purpose computer programmed to perform the techniques and processes disclosed herein. That is, the communication device includes a transmission medium with a signal indicating information for performing the disclosed functions. At a first time, the transmission medium included in the communication device may include a first portion of information for performing the disclosed functions, and at a second time, the transmission medium included in the communication device may include a second portion of information for performing the disclosed functions.
[0349] A central unit (CU) (e.g., source CU 2300) in a first new radio (NR) Node B (gNB) in a radio access network (RAN) may be configured to support a location session for a user equipment (UE) and include means for receiving a first positioning message for the UE from a first entity, which means may be, for example, an external interface 2302, an internal interface 2304, and one or more processors 2308 having dedicated hardware or implementing executable code or software instructions in a memory 2310, such as a receive positioning message unit 2320. Means for determining a first location management component (LMC) may be, for example, one or more processors 2308 having dedicated hardware or implementing executable code or software instructions in the memory 2310, such as a determine LMC unit 2322. Means for storing first information for a location session, the first information for the location session including an identification of the first LMC, an identification of the UE, and a first identifier for the location session, which means may be, for example, one or more processors 2308 having dedicated hardware or implementing executable code or software instructions in the memory 2310, such as a store location session information unit 2324. The means for forwarding the first positioning message to the first LMC may be, for example, the external interface 2302, the internal interface 2304, and one or more processors 2308 having dedicated hardware or implementing executable code or software instructions in the memory 2310, such as the forward positioning message unit 2326. The means for performing a handover of the UE to the second gNB, whereby the second gNB supports the continuation of the location session, may be, for example, the external interface 2302, the internal interface 2304, and one or more processors 2308 having dedicated hardware or implementing executable code or software instructions in the memory 2310, such as the handover unit 2328.
[0350] In some embodiments, the CU may also include a component for forwarding at least some of the first information of the location session together with the first positioning message to the first LMC, which component may be, for example, an external interface 2302, an internal interface 2304, and one or more processors 2308 having dedicated hardware or implementing executable code or software instructions in the memory 2310, such as a forwarding positioning message unit 2326.
[0351] In some embodiments, the CU may further include a component for receiving a second positioning message from the first LMC, the second positioning message including a first identifier of the location session, and the component may be, for example, an external interface 2302, an internal interface 2304, and one or more processors 2308 having dedicated hardware or implementing executable code or software instructions in the memory 2310, such as a receiving positioning message unit 2320. The component for sending a second positioning message to the UE based on the first information of the location session may be an external interface 2302, an internal interface 2304, and one or more processors 2308 having dedicated hardware or implementing executable code or software instructions in the memory 2310, such as a forwarding positioning message unit 2326.
[0352] In some embodiments, the CU may further include a component for receiving a second positioning message from the UE, the second positioning message including a first identifier of the location session, and the component may be, for example, an external interface 2302, an internal interface 2304, and one or more processors 2308 having dedicated hardware or implementing executable code or software instructions in the memory 2310, such as a receiving positioning message unit 2320. The component for sending a second positioning message to the first LMC based on the first information of the location session may be an external interface 2302, an internal interface 2304, and one or more processors 2308 having dedicated hardware or implementing executable code or software instructions in the memory 2310, such as a forwarding positioning message unit 2326.
[0353] In some embodiments, the CU may further include a component for receiving a Nlmf_Location_DetermineLocation response service operation from the first LMC, wherein the Nlmf_Location_DetermineLocation response service operation includes a location estimate of the UE, which component may be, for example, an external interface 2302, an internal interface 2304, and one or more processors 2308 having dedicated hardware or implementing executable code or software instructions in memory 2310, such as a location response unit 2330. The component for sending the Nlmf_Location_DetermineLocation response service operation to the AMF in an NGAP UL transfer message may be an external interface 2302, an internal interface 2304, and one or more processors 2308 having dedicated hardware or implementing executable code or software instructions in memory 2310, such as a location response unit 2330. The component for deleting the first information of the location session location may be, for example, one or more processors 2308 having dedicated hardware or implementing executable code or software instructions in memory 2310, such as a storage location session information unit 2324.
[0354] 24 is a diagram illustrating an example of a hardware implementation of a target central unit (CU) 2400 in a wireless network such as NG-RAN 135. The target CU 2400 may be performed or supported by (or connected to) an entity at a target NG-RAN node entity, such as the target gNB 110. T , and may be part of a wireless network such as, for example, a 5G core network (5GCN) (e.g., 5GCN 140). In some embodiments, the target CU 2400 and the source CU 2300 may be part of the same CU. The target CU 2400 may include hardware components, such as, for example, an external interface 2402, which may be a wired or wireless interface capable of connecting to the AMF 115 via an NG interface, or connecting to other nodes within the RAN (e.g., neighboring gNBs 110-2 or 110-3) using an Xn Application Protocol (XnAP) or a location-specific protocol (e.g., NR Positioning Protocol A (NRPPa)) transmitted over XnAP, and to other CUs or location management components (LMCs) within other gNBs. For example, if the target CU 2400 is within the gNB 110, the target CU 2400 may also include an internal interface 2404 that is capable of connecting to a location management component (LMC) such as the LMC 117, a distributed unit (DU) such as the gNB-DU 204, and a transmission reception point (TRP) via an F1 interface, which may include a reception point (RP) and a transmission point (TP), such as the TRP 112, RP 113, and TP 111 within the same gNB 110. The target CU 2400 also includes one or more processors 2408 and a memory 2410, which may be coupled together via a bus 2406. The memory 2410 may store data and may contain executable code or software instructions that, when executed by the one or more processors 2408, cause the one or more processors 2408 to operate as a special-purpose computer programmed to perform the processes and techniques disclosed herein (e.g., such as the process flow 2100 discussed in FIG. 21).
[0355] 24, memory 2410 includes one or more components or modules that, when implemented by one or more processors 2408, implement the methods described herein. Although the components or modules are illustrated as software in memory 2410 that can be executed by one or more processors 2408, it is understood that the components or modules can be dedicated hardware within or outside the processor 2408.
[0356] As shown, the memory 2410 may include a receiving handover request unit 2420, which, when implemented by the one or more processors 2408, configures the one or more processors 2408 to receive a handover request from a second gNB (e.g., gNB 202) via the external interface 2402, for example. S or 202 SV ) receiving a first handover request message of a UE (e.g., UE 102), wherein the handover request message includes first information of a location session, including an identifier of a location management component (LMC), an identifier of the UE, and an identifier of the location session, for example, as in block 2102 of FIG. 21, Fig.17 18 or stage 8. When implemented by one or more processors 2408, the storage location session information unit 2422 configures the one or more processors 2408 to store, for example, in the memory 2410, the second information of the location session, the second information of the location session including at least a portion of the first information of the location session, for example, as in blocks 2104, Fig.17 The one or more processors 2408 may be further configured to delete the stored information. When implemented by the one or more processors 2408, the complete handover unit 2424 configures the one or more processors 2408 to complete the handover of the UE from the second gNB, for example, as in blocks 2106, Fig.17 18 or stage 11 in FIG. 18 . For example, one or more processors 2408 may be configured to complete the handover of the UE by: determining to handover the UE to a third gNB, sending a second handover request message to the third gNB, the second handover request message including second information of the location session, completing the handover of the UE to the third gNB, receiving a second location session update message from the third gNB, the second location session update message including an identifier of the third gNB, sending a second location session update message to the second LMC, and deleting the second information of the location session. When implemented by the one or more processors 2408, the determine LMC unit 2426 configures the one or more processors 2408 to determine a second LMC to be used for the location session, the second LMC may be the first LMC or may be different from the first LMC, for example, as in block 2108 of FIG. 21 , Fig.17 18 or stage 10. When implemented by the one or more processors 2408, the stored location session information includes an ID unit 2428 that configures the one or more processors 2408 to include an identification of the second LMC in the stored second information if the second LMC is different from the first LMC, for example, as in blocks 2110, Fig.1718 or stage 10. When implemented by the one or more processors 2408, the sending location session update unit 2430 configures the one or more processors 2408 to send a location session update message to the first gNB, for example, via the external interface 2402, the location session update message including the identity of the second gNB and the identity of the second LMC when the second LMC is different from the first LMC, for example, as in blocks 2112, Fig.17 18 or stage 12. When implemented by one or more processors 2408, the location session determination ID unit 2432 configures the one or more processors 2408 to determine a second identifier of the location session, which second identifier of the location session may be the same as or different from the first identifier of the location session, wherein the second identifier may be included in the stored location session information and the location session update message. When implemented by one or more processors 2408, the positioning message unit 2434 configures the one or more processors 2408 to receive a positioning message from the LMC or the UE via the external interface 2402 or the internal interface 2404, the positioning message may include the second identifier of the location session, and send the positioning message to the UE or the LMC based on the information of the location session. The one or more processors 2408 may also be configured by the positioning message unit 2434 to receive a positioning message intended for the UE's serving AMF and an indication of location session termination from the LMC, and send a positioning message to the UE's serving AMF via the external interface 2402.
[0357] The methods described herein can be implemented in various ways depending on the application. For example, the methods can be implemented in hardware, firmware, software, or any combination thereof. For hardware implementations, one or more processors can be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or a combination thereof.
[0358] For implementations involving firmware and / or software, the methods may be implemented using modules (e.g., procedures, functions, etc.) that perform the individual functions described herein. Any machine-readable medium that specifically embodies instructions may be used to implement the methods described herein. For example, software codes may be stored in a memory (e.g., memory 2410) and executed by one or more processor units (e.g., processor 2408), such that the processor units operate as special-purpose computers programmed to perform the techniques and processes disclosed herein. The memory may be implemented inside the processor unit or outside the processor unit. As used herein, the term "memory" refers to any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type of memory or amount of memory, or the type of medium in which the memory is stored.
[0359] If implemented in firmware and / or software, the functions may be stored as one or more instructions or codes on a non-transitory computer-readable storage medium. Examples include computer-readable media encoded with data structures and computer-readable media encoded with computer programs. Computer-readable media include physical computer storage media. The storage medium may be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, semiconductor memory or other storage device, or any other medium that can be used to store the required program code in the form of instructions or data structures and can be accessed by a computer; disks and optical disks used herein include compact disks (CDs), laser optical disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, where disks typically reproduce data magnetically, while optical disks reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.
[0360] In addition to storage on a computer-readable storage medium, instructions and / or data may be provided as signals on a transmission medium included in the communication device. For example, the communication device may include a transceiver with signals indicating instructions and data. Instructions and data are stored on a non-transitory computer-readable medium (e.g., memory 2410) and are configured to cause one or more processors (e.g., processor 2408) to operate as a special-purpose computer programmed to perform the techniques and processes disclosed herein. That is, the communication device includes a transmission medium with a signal indicating information for performing the disclosed functions. At a first time, the transmission medium included in the communication device may include a first portion of information for performing the disclosed functions, and at a second time, the transmission medium included in the communication device may include a second portion of information for performing the disclosed functions.
[0361] A central unit (CU), such as a target CU 2400, in a first new radio (NR) Node B (gNB) in a radio access network (RAN) may be configured to continue a location session of a user equipment (UE) and include means for receiving a first handover request message of the UE from a second gNB, the first handover request message including first information of the location session, the first information of the location session including an identification of a first location management component (LMC), an identification of the UE and a first identifier of the location session, the means may be, for example, an external interface 2402, an internal interface 2404 and one or more processors 2408 having dedicated hardware or implementing executable code or software instructions in a memory 2410, such as a receiving handover request unit 2420. Means for storing second information of the location session, the second information of the location session including at least a portion of the first information of the location session, the means may be one or more processors 2408 having dedicated hardware or implementing executable code or software instructions in a memory 2410, such as a receiving storing location session information unit 2422. The means for completing the handover of the UE from the second gNB to the first gNB may be, for example, the external interface 2402, the internal interface 2404, and one or more processors 2408 having dedicated hardware or implementing executable code or software instructions in the memory 2410, such as the complete handover unit 2424. The means for determining the second LMC, where the second LMC is the first LMC or is different from the first LMC, may be, for example, the one or more processors 2408 having dedicated hardware or implementing executable code or software instructions in the memory 2410, such as the determine LMC unit 2426. The means for including an identification of the second LMC in the second information of the location session when the second LMC is different from the first LMC may be, for example, the one or more processors 2408 having dedicated hardware or implementing executable code or software instructions in the memory 2410, such as the include ID unit 2428 in the stored location session information. A component for sending a first location session update message to a first gNB, when the second LMC is different from the first LMC, the first location session update message includes an identifier of the second gNB and an identifier of the second LMC, the component may be, for example, an external interface 2402, an internal interface 2404, and one or more processors 2408 having dedicated hardware or implementing executable code or software instructions in a memory 2410, such as a sending location session update unit 2430.
[0362] In some embodiments, the CU may further include a component for determining a second identifier of the location session, wherein the second identifier of the location session is the same as or different from the first identifier of the location session, and the component may be, for example, one or more processors 2408 having dedicated hardware or implementing executable code or software instructions in the memory 2410, such as determining the ID in the determining location session ID unit 2432. The component for including the second identifier of the location session in both the second information of the location session and the first location session update message sent to the second gNB when the second identifier of the location session is different from the first identifier of the location session may be, for example, the external interface 2402, the internal interface 2404, and one or more processors 2408 having dedicated hardware or implementing executable code or software instructions in the memory 2410, such as including the ID unit 2428 in the stored location session information and sending the location session update unit 2430.
[0363] In one embodiment, the CU may further include a component for receiving a positioning message from a second LMC, the positioning message including a second identifier of the location session, and the component may be, for example, an external interface 2402, an internal interface 2404, and one or more processors 2408 having dedicated hardware or implementing executable code or software instructions in the memory 2410, such as a positioning message unit 2434. The component for sending a positioning message to the UE based on the second information of the location session may be an external interface 2402, an internal interface 2404, and one or more processors 2408 having dedicated hardware or implementing executable code or software instructions in the memory 2410, such as a positioning message unit 2434.
[0364] In one embodiment, the CU may further include a component for receiving a positioning message from the UE, the positioning message including a second identifier of the location session, and the component may be, for example, an external interface 2402, an internal interface 2404, and one or more processors 2408 having dedicated hardware or implementing executable code or software instructions in the memory 2410, such as a positioning message unit 2434. The component for sending a positioning message to the second LMC based on the second information of the location session may be, for example, an external interface 2402, an internal interface 2404, and one or more processors 2408 having dedicated hardware or implementing executable code or software instructions in the memory 2410, such as a positioning message unit 2434.
[0365] In one embodiment, the CU may also include a component for receiving a positioning message and an indication of location session termination intended for a serving access and mobility management function (AMF) of the UE from a second LMC, which component may be, for example, an external interface 2402, an internal interface 2404, and one or more processors 2408 having dedicated hardware or implementing executable code or software instructions in the memory 2410, such as a positioning message unit 2434. The component for sending a positioning message to the serving AMF of the UE may be an external interface 2402, an internal interface 2404, and one or more processors 2408 having dedicated hardware or implementing executable code or software instructions in the memory 2410, such as a positioning message unit 2434. The component for deleting the second information of the location session may be, for example, one or more processors 2408 having dedicated hardware or implementing executable code or software instructions in the memory 2410, such as a storage location session information unit 2422.
[0366] 25 is a diagram illustrating an example of a hardware implementation of a location management component (LMC) 2500 that may be similar to LMC 117 in a wireless network such as NG-RAN 135. LMC 2500 may be a source LMC, such as a node entity (e.g., serving gNB 110) that is connected to a serving or source NG-RAN node. SV or source gNB 110 S ) or may be a target LMC, for example, performed by (or connected to) a target NG-RAN node entity (e.g. target gNB 110 T ) and may be, for example, part of a wireless network such as a 5G core network (5GCN) (e.g., 5GCN 140). LMC 2500 may include hardware components, such as communication interfaces, which may include one or more of external interfaces 2502, such as, for example, if LMC 2500 is external to gNB 110, external interface 2502 may be a wired or wireless interface capable of connecting to other nodes within the RAN (e.g., a central unit (CU)), or internal interface 2504, such as, if LMC 2500 is within gNB 110, internal interface 2504 capable of connecting to the CU or other entities within gNB 110, such as, for example, via an F1 interface. LMC 2500 also includes one or more processors 2508 and memory 2510, which may be coupled together via bus 2506. The memory 2510 may store data and may contain executable code or software instructions that, when executed by the one or more processors 2508, cause the one or more processors 2508 to operate as a special-purpose computer programmed to perform the processes and techniques disclosed herein (e.g., such as the process flow 2200 discussed in FIG. 22 ).
[0367] 25, memory 2510 includes one or more components or modules that, when implemented by one or more processors 2508, implement the methods described herein. Although the components or modules are illustrated as software in memory 2510 that can be executed by one or more processors 2508, it is understood that the components or modules can be dedicated hardware within or outside the processor 2508.
[0368] As shown in the figure, the memory 2510 may include a receiving positioning message unit 2520. When implemented by one or more processors 2508, the receiving positioning message unit 2520 configures the one or more processors 2508 to receive a positioning message for a UE (e.g., UE 102) from a first entity, for example, through an external interface 2502 or an internal interface 2504. The first entity may be an access and mobility management function (AMF), such as AMF 115, or a UE. The positioning message is relayed by the CU of the gNB to the LMC and initiates a location session of the UE in the LMC, and includes an identifier of a source gNB, a source gNB serving the UE, and an identifier of the location session, for example, as in block 2202 of FIG. 22 , Fig.17 18 or stages 5 and 18 of FIG. 18. When implemented by one or more processors 2508, the exchange positioning message unit 2522 configures the one or more processors 2508 to send and / or receive at least one positioning message for the UE with a second entity, for example, using the external interface 2502 or the internal interface 2504, the second entity can be a UE or a distributed unit (DU) such as the gNB-DU 204, for example, as in blocks 2204, Fig.17 18 as discussed in stages 4 and 16 of FIG. 18 or stages 6 and 21 of FIG. 18 . For example, one or more processors 2508 may be configured to send a downlink positioning message to the UE via the first CU and the source gNB, or to receive an uplink positioning message from the UE via the first CU and the source gNB. In another example, one or more processors 2508 may be configured to send a downlink network positioning message to the DU via the first CU or to receive an uplink network positioning message from the DU via the first CU. When implemented by one or more processors 2508, the receiving update message indicates that the switching unit 2524 configures the one or more processors 2508 to receive a location session update message, for example, via the external interface 2502 or the internal interface 2504, the location session update message indicating a handover of the UE from the source gNB to the target gNB, and indicating whether a second LMC is allocated, and including an identifier of the second LMC when the second LMC is allocated, as in box 2206 of FIG. 22 , Fig.17When implemented by the one or more processors 2508, the continuing support location session unit 2526 configures the one or more processors 2508 to continue supporting the location session using the target gNB when the second LMC is not assigned, for example, as in blocks 2208, Fig.17 18 or stages 10 and 19d of FIG. 18 . For example, the one or more processors 2508 may be configured to, when the second LMC is not allocated, continue to support the location session using the target gNB by: sending a downlink positioning message to the UE via the CU and the target gNB, receiving an uplink positioning message from the UE via the CU and the target gNB, sending a downlink network positioning message to a distributed unit (DU) in the gNB via the CU, receiving an uplink network positioning message from the DU via the CU, or sending a second positioning message to the first entity via the CU and the target gNB. When implemented by the one or more processors 2508, sending a location session transfer message configures the one or more processors 2508 to send a location session transfer message to the second LMC via the external interface 2502 or the internal interface 2504 when the second LMC is allocated, the location session transfer message including the current state of the location session and the first positioning message, for example, as in block 2210 of FIG. 22 , Fig.17 as discussed in stage 13 of FIG. 18 or stage 16 of FIG. 18 .
[0369] The methods described herein can be implemented in various ways depending on the application. For example, the methods can be implemented in hardware, firmware, software, or any combination thereof. For hardware implementations, one or more processors can be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or a combination thereof.
[0370] For implementations involving firmware and / or software, the methods may be implemented using modules (e.g., procedures, functions, etc.) that perform the individual functions described herein. Any machine-readable medium that specifically embodies instructions may be used to implement the methods described herein. For example, software codes may be stored in a memory (e.g., memory 2510) and executed by one or more processor units (e.g., processor 2508), such that the processor units operate as special-purpose computers programmed to perform the techniques and processes disclosed herein. The memory may be implemented inside the processor unit or outside the processor unit. As used herein, the term "memory" refers to any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type of memory or amount of memory, or the type of medium in which the memory is stored.
[0371] If implemented in firmware and / or software, the functions may be stored as one or more instructions or codes on a non-transitory computer-readable storage medium. Examples include computer-readable media encoded with data structures and computer-readable media encoded with computer programs. Computer-readable media include physical computer storage media. The storage medium may be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, semiconductor memory or other storage device, or any other medium that can be used to store the required program code in the form of instructions or data structures and can be accessed by a computer; disks and optical disks used herein include compact disks (CDs), laser optical disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, where disks typically reproduce data magnetically, while optical disks reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.
[0372] In addition to storage on a computer-readable storage medium, instructions and / or data may be provided as signals on a transmission medium included in the communication device. For example, the communication device may include a transceiver with signals indicating instructions and data. Instructions and data are stored on a non-transitory computer-readable medium (e.g., memory 2510) and are configured to cause one or more processors (e.g., processor 2508) to operate as a special-purpose computer programmed to perform the techniques and processes disclosed herein. That is, the communication device includes a transmission medium with a signal indicating information for performing the disclosed functions. At a first time, the transmission medium included in the communication device may include a first portion of information for performing the disclosed functions, and at a second time, the transmission medium included in the communication device may include a second portion of information for performing the disclosed functions.
[0373] A location management component (LMC), such as LMC 2500, in a first new radio (NR) Node B (gNB) in a radio access network (RAN) is configured to support a location session for a user equipment (UE), the LMC may include a component for receiving a first positioning message for the UE from a first entity, the first positioning message being relayed by a central unit (CU) for the first gNB to the first LMC, the first positioning message initiating a location session for the UE in the first LMC, the first positioning message including an identification of a source gNB, the source gNB serving the UE, and an identifier of the location session, the component may be, for example, an external interface 2502, an internal interface 2504, and one or more processors 2508 having dedicated hardware or implementing executable code or software instructions in a memory 2510, such as a receiving positioning message unit 2520. A component for sending at least one positioning message for the UE to a second entity; may be, for example, an external interface 2502, an internal interface 2504, and one or more processors 2508 having dedicated hardware or implementing executable code or software instructions in a memory 2510, such as an exchanging positioning message unit 2522. The means for receiving a location session update message indicating a handover of the UE from the source gNB to the target gNB, the location session update message indicating whether a second LMC is assigned, the location session update message including an identification of the second LMC when the second LMC is assigned, the means may be, for example, the external interface 2502, the internal interface 2504, and one or more processors 2508 having dedicated hardware or implementing executable code or software instructions in the memory 2510, such as a receiving update message indicating a handover unit 2524. The means for continuing to support the location session using the target gNB when the second LMC is not assigned may be, for example, one or more processors 2508 having dedicated hardware or implementing executable code or software instructions in the memory 2510, such as a continuing to support the location session unit 2526. A component for sending a location session transfer message to a second LMC when the second LMC is assigned, the location session transfer message including the current status of the location session and the first positioning message, the component may be, for example, an external interface 2502, an internal interface 2504, and one or more processors 2508 having executable code or software instructions in dedicated hardware or implementing a memory 2510, such as a sending location session transfer message unit 2528.
[0374] References in this specification to "one example," "example," "some examples," or "exemplary embodiments" mean that a particular feature, structure, or characteristic described in conjunction with the features and / or examples may be included in at least one feature and / or example of the claimed subject matter. Thus, the appearances of the phrases "in one example," "example," "in some examples," or "in some embodiments," or other similar phrases in various places in this specification do not necessarily all refer to the same features, examples, and / or limitations. Furthermore, particular features, structures, or characteristics may be combined in one or more examples and / or features.
[0375] Some parts of the detailed description included herein are presented according to algorithms or symbolic representations of operations on binary digital signals stored in the memory of a specific device or a dedicated computing device or platform. In the context of this particular specification, the term specific device, etc. includes a general-purpose computer, once it is programmed to perform specific operations according to instructions from program software. Algorithmic descriptions or symbolic representations are examples of techniques used by ordinary technicians in signal processing or related fields to convey the essence of their work to other technicians in the field. The algorithm here is generally considered to be a self-consistent sequence of operations or similar signal processing sequences to obtain the desired results. In this case, the operation or processing involves physical operations of physical quantities. Typically, although not necessarily, these quantities can take the form of electrical or magnetic signals that can be stored, transmitted, combined, compared or otherwise manipulated. It turns out that sometimes, mainly for common reasons, it is convenient to refer to such signals as bits, data, values, elements, symbols, characters, terms, numbers, numbers, etc. However, it should be understood that all of these or similar terms are associated with appropriate physical quantities and are merely convenient labels. Unless otherwise expressly stated, it should be apparent from the discussion herein that, throughout the discussion of this specification, terms such as "processing," "computing," "calculating," "determining," etc., are used to refer to the actions or processes of a specific apparatus, such as a special purpose computer, a special purpose computing apparatus, or a similar special purpose electronic computing device. Thus, in the context of this specification, a special purpose computer or a similar special purpose electronic computing device is capable of manipulating or transforming signals, typically represented as physical electronic or magnetic quantities within a memory, register, or other information storage device, transmission device, or display device of a special purpose computer or a similar special purpose electronic computing device.
[0376] 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 appreciate that the claimed subject matter may be practiced without these specific details. In other cases, methods and devices known to those of ordinary skill have not been described in detail to avoid obscuring the claimed subject matter.
[0377] As used herein, the terms "and," "or," and "and / or" may include a variety of meanings, which are also expected to depend at least in part on the context in which the terms are used. In general, "or," if used in an associative list, such as A, B, or C, means A, B, and C, which are used herein in an inclusive sense, and A, B, or C, which are used herein in an exclusive sense. In addition, the term "one or more," as used herein, may be used to describe any feature, structure, or characteristic in the singular, or may be used to describe a plurality or some other combination of a feature, structure, or characteristic. However, it should be noted that this is merely an illustrative example, and the claimed subject matter is not limited to this example.
[0378] While what is presently considered to be exemplary features has been illustrated and described, it will be appreciated by those skilled in the art that various other modifications may be made, and equivalents may be substituted, without departing from the claimed subject matter. In addition, many modifications may be made to adapt a particular situation to the teachings of the claimed subject matter without departing from the central concepts described herein.
[0379] An implementation (1) may be a method for supporting a location session of a user equipment (UE) performed by a first central unit (CU) in a first new radio (NR) node B (gNB) in a radio access network (RAN), the method comprising: receiving a first positioning message for the UE from a first entity; determining a first location management component (LMC); storing first information for the location session, the first information for the location session comprising an identifier of the first LMC, an identifier of the UE, and a first identifier of the location session; forwarding the first positioning message to the first LMC; and performing a handover of the UE to a second gNB, whereby the second gNB supports continuation of the location session.
[0380] There may be some implementations (2) of the above method (1), wherein the first gNB is the serving gNB of the UE before the handover, and the second gNB is the serving gNB of the UE after the handover.
[0381] There may be some implementations (3) of the above method (1), wherein the first LMC is part of the first CU, and wherein forwarding the first positioning message to the first LMC is inside the first CU.
[0382] There may be some embodiments (4) of the above method (1), wherein the first LMC is part of the first gNB and is separate from the first CU, wherein forwarding the first positioning message to the first LMC includes sending the first positioning message to the first LMC in an F1 Application Protocol (F1AP) transmission message.
[0383] There may be some embodiments (5) of the above method (1), wherein the first LMC is part of a third gNB, and wherein forwarding the first positioning message to the first LMC includes sending the first positioning message to the third gNB in an Xn Application Protocol (XnAP) transmission message.
[0384] There may be some implementations (6) of the above method (1), wherein forwarding the first positioning message to the first LMC further comprises forwarding at least some of the first information of the location session and the first positioning message to the first LMC.
[0385] There may be some implementations (7) of the above method (1), further comprising: receiving a second positioning message from the first LMC, the second positioning message comprising a first identifier of the location session; and sending the second positioning message to the UE based on the first information of the location session.
[0386] There may be some implementations (8) of the above method (1), further comprising: receiving a second positioning message from the UE, the second positioning message comprising a first identifier of the location session; and sending the second positioning message to the first LMC based on the first information of the location session.
[0387] There may be some implementations (9) of the above method (1), wherein performing a handover to a second gNB includes: determining to handover the UE to the second gNB; sending a handover request message to the second gNB, the handover request message including first information of a location session; completing the handover of the UE to the second gNB; receiving a location session update message from the second gNB, the location session update message including an identifier of the second gNB; sending a location session update message to the first LMC; and deleting the first information of the location session to perform the handover.
[0388] There may be some embodiments (10) of the above method (9), wherein a second CU in the second gNB receives a handover request message, wherein the second CU stores second information of the location session, the second information of the location session including at least a portion of the first information of the location session, and wherein the second CU sends a location session update message to the first CU.
[0389] There may be some embodiments (11) of the above method (10), wherein the second CU allocates a second identifier for the location session, the second identifier for the location session is different from the first identifier for the location session, the second information for the location session includes the second identifier for the location session, and the location session update message includes the second identifier for the location session.
[0390] There may be some implementations (12) of the above method (10), wherein the second CU determines a second LMC, the second LMC is different from the first LMC, the second information of the location session includes an identifier of the second LMC, and the location session update message includes the identifier of the second LMC.
[0391] There may be some implementations (13) of the above method (1), wherein the first entity is an Access and Mobility Management Function (AMF), wherein the first positioning message is a Nlmf_Location_DetermineLocation request service operation, and wherein the first positioning message is received within a NGAP DL transport message.
[0392] There may be some implementations (14) of the above method (13), further comprising: receiving a Nlmf_Location_DetermineLocation response service operation from a first LMC, wherein the Nlmf_Location_DetermineLocation response service operation includes a location estimate of the UE; sending the Nlmf_Location_DetermineLocation response service operation to the AMF within an NGAP UL transfer message; and deleting first information of the location session.
[0393] There may be some embodiments (15) of the above method (1), wherein the first entity is a UE, wherein the first positioning message includes an event report for periodic or triggered positioning of the UE and a routing identifier, the routing identifier indicating any LMC or serving LMC, and further comprising determining the first LMC based at least in part on the routing identifier.
[0394] There may be some implementations (16) of the above method (15), wherein the routing identifier indicates a serving LMC, wherein the first LMC is different from the serving LMC, and wherein forwarding the event report to the first LMC includes sending the event report and an indication of the first LMC to the serving LMC.
[0395] There may be some implementations (17) of the above method (16), wherein the serving LMC sends a location session transfer message to the first LMC, the location session transfer message including the event report and the current status of the periodic or triggered event reporting of the UE.
[0396] An embodiment (18) may be a first central unit (CU) in a first new radio (NR) node B (gNB) in a radio access network (RAN), the first CU configured to support a location session of a user equipment (UE), the first CU comprising: an external interface configured to communicate with one or more of an access and mobility management function (AMF), other gNBs in the RAN, other CUs in other gNBs, and location management components (LMCs) in other gNBs; an internal interface configured to communicate with the LMC in the first gNB, a distributed unit (DU) in the first gNB, and a transmit / receive point (TRP) in the first gNB. The invention relates to a method for transmitting a positioning session of a UE to a first entity and a second gNB, wherein the at least one processor is coupled to an external interface, an internal interface and the at least one memory, wherein the at least one processor is configured to: receive a first positioning message of the UE from a first entity; determine a first location management component (LMC); store first information of the location session, wherein the first information of the location session includes an identifier of the first LMC, an identifier of the UE and a first identifier of the location session; forward the first positioning message to the first LMC; and perform a handover of the UE to a second gNB, whereby the second gNB supports the continuation of the location session.
[0397] There may be some implementations (19) of the first CU (18) described above, wherein the first gNB is a serving gNB for the UE before the handover, and the second gNB is a serving gNB for the UE after the handover.
[0398] There may be some embodiments (20) of the first CU (18) described above, wherein the first LMC is part of the first CU, wherein the first positioning message is forwarded to the first LMC via an internal interface.
[0399] There may be some embodiments (21) of the first CU (18) described above, wherein the first LMC is part of the first gNB and is separate from the first CU, wherein the at least one processor is configured to forward the first positioning message to the first LMC by being configured to send the first positioning message to the first LMC via an internal interface in an F1 Application Protocol (F1AP) transmission message.
[0400] There may be some embodiments (22) of the first CU (18) described above, wherein the first LMC is part of a third gNB, wherein the at least one processor is configured to forward the first positioning message to the first LMC by being configured to send the first positioning message to the third gNB via an external interface in an Xn Application Protocol (XnAP) transmission message.
[0401] There may be some embodiments (23) of the first CU (18) described above, wherein the at least one processor is configured to forward the first positioning message to the first LMC by being further configured to forward at least some of the first information of the location session together with the first positioning message to the first LMC.
[0402] There may be some embodiments (24) of the above-mentioned first CU (18), wherein the at least one processor is further configured to: receive a second positioning message from the first LMC, the second positioning message including a first identifier of the location session; and send the second positioning message to the UE based on the first information of the location session.
[0403] There may be some embodiments (25) of the above-mentioned first CU (18), wherein the at least one processor is further configured to: receive a second positioning message from the UE, the second positioning message including a first identifier of the location session; and send the second positioning message to the first LMC based on the first information of the location session.
[0404] There may be some embodiments (26) of the above-mentioned first CU (18), wherein the at least one processor is configured to perform a handover to the second gNB by being configured to perform the following operations: determine to handover the UE to the second gNB; send a handover request message to the second gNB, the handover request message including the first information of the location session; complete the handover of the UE to the second gNB; receive a location session update message from the second gNB, the location session update message including the identifier of the second gNB; send a location session update message to the first LMC; and delete the first information of the location session.
[0405] There may be some embodiments (27) of the above-mentioned first CU (26), wherein a second CU in the second gNB receives a handover request message, wherein the second CU stores second information of the location session, the second information of the location session includes at least a portion of the first information of the location session, and wherein the second CU sends a location session update message to the first CU.
[0406] There may be some embodiments (28) of the above-mentioned first CU (27), wherein the second CU allocates a second identifier for the location session, the second identifier for the location session is different from the first identifier for the location session, the second information for the location session includes the second identifier for the location session, and the location session update message includes the second identifier for the location session.
[0407] There may be some implementations (29) of the first CU (27) described above, wherein the second CU determines a second LMC, the second LMC is different from the first LMC, the second information of the location session includes an identifier of the second LMC, and the location session update message includes the identifier of the second LMC.
[0408] There may be some embodiments (30) of the first CU (18) described above, wherein the first entity is an AMF, wherein the first positioning message is a Nlmf_Location_DetermineLocation request service operation, wherein the first positioning message is received within a Next Generation Application Protocol (NGAP) downlink (DL) transmission message.
[0409] There may be some embodiments (31) of the above-mentioned first CU (30), further comprising: receiving a Nlmf_Location_DetermineLocation response service operation from a first LMC, wherein the Nlmf_Location_DetermineLocation response service operation includes a location estimate of the UE; sending the Nlmf_Location_DetermineLocation response service operation to the AMF within an NGAP uplink (UL) transmission message; and deleting first information of the location session.
[0410] There may be some embodiments (32) of the first CU (18) described above, wherein the first entity is a UE, wherein the first positioning message includes an event report for periodic or triggered positioning of the UE and a routing identifier, the routing identifier indicating any LMC or serving LMC, and wherein the at least one processor is further configured to determine the first LMC based at least in part on the routing identifier.
[0411] There may be some embodiments (33) of the first CU (32) described above, wherein the routing identifier indicates a serving LMC, wherein the first LMC is different from the serving LMC, and wherein the at least one processor is configured to forward the event report to the first LMC by being configured to send the event report and an indication of the first LMC to the serving LMC.
[0412] There may be some embodiments (34) of the first CU (33) above, wherein the serving LMC sends a location session transfer message to the first LMC, the location session transfer message including the event report and the current status of the periodic or triggered event reporting of the UE.
[0413] One embodiment (35) may be a first central unit (CU) in a first new radio (NR) node B (gNB) in a radio access network (RAN), the first CU being configured to support a location session of a user equipment (UE), the first CU comprising: a component for receiving a first positioning message of the UE from a first entity; a component for determining a first location management component (LMC); a component for storing first information for the location session, the first information for the location session comprising an identifier of the first LMC, an identifier of the UE and a first identifier of the location session; a component for forwarding the first positioning message to the first LMC; and a component for performing a handover of the UE to a second gNB, whereby the second gNB supports continuation of the location session.
[0414] One embodiment (36) may be a non-transitory storage medium including program code stored thereon, the program code being operable to cause at least one processor in a first central unit (CU) in a first new radio (NR) node B (gNB) in a radio access network (RAN) to support a location session for a user equipment (UE), including: program code for receiving a first positioning message for the UE from a first entity; program code for determining a first location management component (LMC); program code for storing first information for the location session, the first information for the location session including an identifier of the first LMC, an identifier of the UE, and a first identifier for the location session; program code for forwarding the first positioning message to the first LMC; and program code for performing a handover of the UE to a second gNB, whereby the second gNB supports continuation of the location session.
[0415] An embodiment (37) may be a method for continuing a location session of a user equipment (UE) performed by a first central unit (CU) in a first new radio (NR) node B (gNB) in a radio access network (RAN), the method comprising: receiving a first handover request message of the UE from a second gNB, the first handover request message comprising first information of the location session, the first information of the location session comprising an identifier of a first location management component (LMC), an identifier of the UE and a first identifier of the location session; storing second information of the location session, the second information of the location session comprising at least a portion of the first information of the location session; completing handover of the UE from the second gNB to the first gNB; determining a second LMC, wherein the second LMC is the first LMC or is different from the first LMC; when the second LMC is different from the first LMC, including the identifier of the second LMC in the second information of the location session; and sending a first location session update message to the first gNB, when the second LMC is different from the first LMC, the first location session update message comprising the identifier of the second gNB and the identifier of the second LMC.
[0416] There may be some implementations (38) of the above method (37), wherein the second gNB is the serving gNB of the UE before the handover, and the first gNB is the serving gNB of the UE after the handover.
[0417] There may be some embodiments (39) of the above method (37), which also include: determining a second identifier of the location session, wherein the second identifier of the location session is the same as or different from the first identifier of the location session; and when the second identifier of the location session is different from the first identifier of the location session, including the second identifier of the location session in both the second information of the location session and the first location session update message sent to the second gNB.
[0418] There may be some embodiments (40) of the above method (37), wherein a second CU in the second gNB receives a first location session update message sent by the first CU, wherein the second CU sends the first location session update message to the first LMC.
[0419] There may be some implementations (41) of the above method (39), further comprising: receiving a positioning message from a second LMC, the positioning message comprising a second identifier of the location session; and sending the positioning message to the UE based on second information of the location session.
[0420] There may be some embodiments (42) of the above method (41), wherein the positioning message comprises an event report confirmation or an LPP message for periodic or triggered positioning.
[0421] There may be some implementations (43) of the above method (39), further comprising: receiving a positioning message from the UE, the positioning message comprising a second identifier of the location session; and sending the positioning message to the second LMC based on the second information of the location session.
[0422] There may be some implementations (44) of the above method (37), which also include: determining to switch the UE to a third gNB; sending a second switching request message to the third gNB, the second switching request message including second information of the location session; completing the switching of the UE to the third gNB; receiving a second location session update message from the third gNB, the second location session update message including an identifier of the third gNB; sending a second location session update message to the second LMC; and deleting the second information of the location session to complete the switching of the UE.
[0423] There may be some embodiments (45) of the above method (39), further comprising: receiving a positioning message and an indication of location session termination intended for a serving access and mobility management function (AMF) of the UE from a second LMC; sending a positioning message to the serving AMF of the UE; and deleting second information of the location session.
[0424] There may be some embodiments (46) of the above method (45) wherein the positioning message comprises an event report or an Nlmf_Location_DetermineLocation response service operation for periodic or triggered positioning.
[0425] An embodiment (47) may be a first central unit (CU) in a first new radio (NR) node B (gNB) in a radio access network (RAN), the first CU being configured to continue a location session of a user equipment (UE), the first CU comprising: an external interface configured to communicate with one or more of an access and mobility management function (AMF), other gNBs in the RAN, other CUs in other gNBs, and location management components (LMCs) in other gNBs; an internal interface configured to communicate with one or more of the LMC in the first gNB, a distributed unit (DU) in the first gNB, and a transmit receive point (TRP) in the first gNB, the transmit receive point may include a receive point (RP) and a transmit point (TP); at least one memory; at least one processor coupled to the external interface, the internal interface, and the at least one memory, wherein the at least one processor is configured to communicate with the external interface, the internal interface, and the at least one memory, wherein the at least one processor is configured to communicate with the at least one LMC in the first gNB, the distributed unit (DU) in the first gNB, and the transmit receive point (TRP) in the first gNB. A processor is configured to: receive a first handover request message of the UE from the second gNB via an external interface, the first handover request message including first information of a location session, the first information of the location session including an identifier of a first location management component (LMC), an identifier of the UE and a first identifier of the location session; store second information of the location session, the second information of the location session including at least a part of the first information of the location session; complete handover of the UE from the second gNB to the first gNB; determine a second LMC, wherein the second LMC is the first LMC or is different from the first LMC; when the second LMC is different from the first LMC, include the identifier of the second LMC in the second information of the location session; and send a first location session update message to the first gNB via an internal interface, when the second LMC is different from the first LMC, the first location session update message includes the identifier of the second gNB and the identifier of the second LMC.
[0426] There may be some implementations (48) of the first CU (47) described above, wherein the second gNB is a serving gNB for the UE before switching, and the first gNB is a serving gNB for the UE after switching.
[0427] There may be some embodiments (49) of the above-mentioned first CU (47), wherein the at least one processor is further configured to: determine a second identifier of the location session, wherein the second identifier of the location session is the same as or different from the first identifier of the location session; and when the second identifier of the location session is different from the first identifier of the location session, the second identifier of the location session is included in both the second information of the location session and the first location session update message sent to the second gNB.
[0428] There may be some embodiments (50) of the above-mentioned first CU (47), wherein a second CU in the second gNB receives a first location session update message sent by the first CU, wherein the second CU sends the first location session update message to the first LMC.
[0429] There may be some embodiments (51) of the first CU (49) described above, wherein the at least one processor is further configured to: receive a positioning message from a second LMC, the positioning message including a second identifier of the location session; and send the positioning message to the UE based on the second information of the location session.
[0430] There may be some embodiments (52) of the first CU (51) above, wherein the positioning message includes an event report confirmation or an LPP message for periodic or triggered positioning.
[0431] There may be some embodiments (53) of the first CU (49) described above, wherein the at least one processor is further configured to: receive a positioning message from the UE, the positioning message including a second identifier of the location session; and send the positioning message to the second LMC based on the second information of the location session.
[0432] There may be some embodiments (54) of the above-mentioned first CU (47), wherein the at least one processor is further configured to: determine to switch the UE to a third gNB; send a second switching request message to the third gNB, the second switching request message including second information of the location session; complete the switching of the UE to the third gNB; receive a second location session update message from the third gNB, the second location session update message including an identifier of the third gNB; send a second location session update message to the second LMC; and delete the second information of the location session.
[0433] There may be some embodiments (55) of the above-mentioned first CU (49), which also include: receiving a positioning message and an indication of location session termination intended for a serving AMF of the UE from a second LMC; sending a positioning message to the serving AMF via an external interface of the UE; and deleting second information of the location session.
[0434] There may be some embodiments (56) of the first CU (55) described above, wherein the positioning message includes an event report or an Nlmf_Location_DetermineLocation response service operation for periodic or triggered positioning.
[0435] An embodiment (57) may be a first central unit (CU) in a first new radio (NR) node B (gNB) in a radio access network (RAN), the first CU being configured to continue a location session of a user equipment (UE), the first CU comprising: a component for receiving a first handover request message of the UE from a second gNB, the first handover request message comprising first information of the location session, the first information of the location session comprising an identifier of a first location management component (LMC), an identifier of the UE and a first identifier of the location session; a component for storing second information of the location session, the second information of the location session comprising at least a portion of the first information of the location session; a component for completing a handover of the UE from the second gNB to the first gNB; a component for determining a second LMC, wherein the second LMC is the first LMC or is different from the first LMC; a component for including the identifier of the second LMC in the second information of the location session when the second LMC is different from the first LMC; and a component for sending a first location session update message to the first gNB, wherein the first location session update message comprises the identifier of the second gNB and the identifier of the second LMC when the second LMC is different from the first LMC.
[0436] There may be some implementations (58) of the above-mentioned first CU (57), wherein the second gNB is the serving gNB of the UE before the handover, and the first gNB is the serving gNB of the UE after the handover.
[0437] Some embodiments (59) of the above-mentioned first CU (57) may also include: a component for determining a second identifier of the location session, wherein the second identifier of the location session is the same as or different from the first identifier of the location session; and a component for including the second identifier of the location session in both the second information of the location session and the first location session update message sent to the second gNB when the second identifier of the location session is different from the first identifier of the location session.
[0438] There may be some embodiments (60) of the above-mentioned first CU (57), wherein a second CU in the second gNB receives a first location session update message sent by the first CU, wherein the second CU sends the first location session update message to the first LMC.
[0439] Some embodiments (61) of the first CU (59) described above may further include: a component for receiving a positioning message from a second LMC, the positioning message including a second identifier of the location session; and a component for sending the positioning message to the UE based on the second information of the location session.
[0440] There may be some embodiments (62) of the first CU (61) described above, wherein the positioning message includes an event report confirmation or an LPP message for periodic or triggered positioning.
[0441] There may be some embodiments (63) of the first CU (59) described above, further comprising: a component for receiving a positioning message from the UE, the positioning message comprising a second identifier of the location session; and a component for sending the positioning message to the second LMC based on the second information of the location session.
[0442] There may be some embodiments (64) of the above-mentioned first CU (57), which also include: a component for determining to switch the UE to a third gNB; a component for sending a second switching request message to the third gNB, the second switching request message including second information of the location session; a component for completing the switching of the UE to the third gNB; a component for receiving a second location session update message from the third gNB, the second location session update message including an identifier of the third gNB; a component for sending a second location session update message to the second LMC; and a component for deleting the second information of the location session.
[0443] Some embodiments (65) of the above-mentioned first CU (59) may also include: a component for receiving a positioning message and an indication of location session termination intended for a serving access and mobility management function (AMF) of the UE from a second LMC; a component for sending a positioning message to the serving AMF of the UE; and a component for deleting the second information of the location session.
[0444] There may be some embodiments (66) of the first CU (65) described above, wherein the positioning message includes an event report or an Nlmf_Location_DetermineLocation response service operation for periodic or triggered positioning.
[0445] An embodiment (67) may be a non-transitory storage medium including program code stored thereon, the program code being operable to cause at least one processor in a first central unit (CU) in a first new radio (NR) node B (gNB) in a radio access network (RAN) to be configured to continue a location session of a user equipment (UE), including: program code for receiving a first handover request message for the UE from a second gNB, the first handover request message including first information for the location session, the first information for the location session including an identifier of a first location management component (LMC), an identifier of the UE, and a first identifier for the location session; program code for storing second information for the location session, the second information for the location session including at least a portion of the first information for the location session; program code for completing handover of the UE from the second gNB to the first gNB; program code for determining a second LMC, wherein the second LMC is the first LMC or is different from the first LMC; program code for including the identifier of the second LMC in the second information for the location session when the second LMC is different from the first LMC; and program code for sending a first location session update message to the first gNB, wherein the first location session update message includes the identifier of the second gNB and the identifier of the second LMC when the second LMC is different from the first LMC.
[0446] Therefore, it is intended that the claimed subject matter not be limited to the particular examples disclosed, but that the claimed subject matter may also include all aspects falling within the scope of the appended claims and their equivalents.
[0447] Although the foregoing disclosure shows illustrative aspects of the present disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps, and / or actions of the method claims according to the disclosed aspects described herein do not need to be performed in any particular order. In addition, although elements of the present disclosure may be described or claimed in the singular, the plural may be considered unless a limitation to the singular is explicitly stated.
Claims
1. A method for supporting a location session of a user equipment UE performed by a first central unit CU in a first New Radio NR Node B gNB in a Radio Access Network RAN, the method comprising: receiving a first positioning message for the UE from a first entity; Determining a first location management component LMC; storing first information for a location session, the first information for the location session comprising an identifier of the first LMC, an identifier of the UE, and a first identifier for the location session; Forwarding the first positioning message to the first LMC; as well as Perform handover of the UE to a second gNB, whereby the second gNB supports continuation of the location session.
2. The method according to claim 1, wherein: The first gNB is the serving gNB of the UE before the switching, and the second gNB is the serving gNB of the UE after the switching.
3. The method according to claim 1, wherein: The first LMC is part of the first CU, wherein forwarding the first positioning message to the first LMC is inside the first CU.
4. The method according to claim 1, wherein: The first LMC is part of the first gNB and is separate from the first CU, wherein forwarding the first positioning message to the first LMC includes sending the first positioning message to the first LMC in an F1 Application Protocol F1AP transmission message.
5. The method according to claim 1, wherein: The first LMC is part of a third gNB, wherein forwarding the first positioning message to the first LMC includes sending the first positioning message to the third gNB in an Xn application protocol XnAP transmission message.
6. The method according to claim 1, wherein: Forwarding the first positioning message to the first LMC further includes forwarding at least some of the first information for the location session to the first LMC along with the first positioning message.
7. The method according to claim 1, further comprising: receiving a second positioning message from the first LMC, the second positioning message including the first identifier for the location session; as well as Based on the first information for the location session, the second positioning message is sent to the UE.
8. The method according to claim 1, further comprising: receiving a second positioning message from the UE, the second positioning message including the first identifier for the location session; as well as Based on the first information for the location session, the second positioning message is sent to the first LMC.
9. The method according to claim 1, wherein: Performing handover to the second gNB includes: Determine to hand over the UE to the second gNB; Sending a handover request message to the second gNB, where the handover request message includes the first information for the location session; completing handover of the UE to the second gNB; receiving a location session update message from the second gNB, the location session update message including an identifier of the second gNB; sending the location session update message to the first LMC; and The first information for the location session is deleted.
10. The method according to claim 9, wherein: The second CU in the second gNB receives the switching request message, wherein the second CU stores second information for the location session, the second information for the location session includes at least a portion of the first information for the location session, and the second CU sends the location session update message to the first CU.
11. The method according to claim 1, wherein: The first entity is an Access and Mobility Management Function AMF, wherein the first positioning message is an Nlmf_Location_determine Location request service operation, wherein the first positioning message is received within a NGAP DLTransfer message.
12. The method according to claim 11, further comprising: receiving, from the first LMC, a Nlmf_Location_determineLocation response service operation, wherein the Nlmf_Location_determineLocation response service operation includes a location estimate of the UE; sending a Nlmf_Location_determineLocation response service operation in a NGAP ULTransfer message to the AMF; and The first information for the location session is deleted.
13. The method according to claim 1, wherein: The first entity is the UE, wherein the first positioning message includes an event report of a periodic or triggered location of the UE and a routing identifier indicating any LMC or serving LMC, and further includes determining the first LMC based at least in part on the routing identifier.
14. The method according to claim 13, wherein: The routing identifier indicates the serving LMC, wherein the first LMC is different from the serving LMC, wherein forwarding the event report to the first LMC comprises sending the event report and an indication of the first LMC to the serving LMC.
15. A first central unit CU in a first new radio NR Node B gNB in a radio access network RAN, the first CU being configured to support a location session of a user equipment UE, the first CU comprising: an external interface configured to communicate with one or more of an access and mobility management function AMF, other gNBs in the RAN, other CUs in other gNBs, and a location management component LMC in other gNBs; an internal interface configured to communicate with one or more of an LMC within the first gNB, a distributed unit DU within the first gNB, and a transmit-receive point TRP within the first gNB, wherein the TRP may include a receive point RP and a transmit point TP; at least one memory; at least one processor coupled to the external interface, the internal interface, and the at least one memory, wherein the at least one processor is configured to: receiving a first positioning message for the UE from a first entity; Determining a first location management component LMC; storing first information for a location session, the first information for the location session comprising an identifier of the first LMC, an identifier of the UE, and a first identifier for the location session; forwarding a first positioning message to the first LMC; and Perform handover of the UE to a second gNB, whereby the second gNB supports continuation of the location session.
16. The first CU according to claim 15, wherein: The first gNB is the serving gNB of the UE before the switching, and the second gNB is the serving gNB of the UE after the switching.
17. The first CU according to claim 15, wherein: The first LMC is part of the first CU, wherein the first positioning message is forwarded to the first LMC via the internal interface.
18. The first CU according to claim 15, wherein: The first LMC is part of the first gNB and is separate from the first CU, wherein the at least one processor is configured to forward the first positioning message to the first LMC by being configured to send the first positioning message to the first LMC via the internal interface in an F1 application protocol F1AP transmission message.
19. The first CU according to claim 15, wherein: The first LMC is part of a third gNB, wherein the at least one processor is configured to forward the first positioning message to the first LMC by being configured to send the first positioning message to the third gNB via the external interface in an Xn application protocol XnAP transmission message.
20. The first CU according to claim 15, wherein: The at least one processor is configured to forward the first positioning message to the first LMC by being further configured to forward at least some of the first information for the location session to the first LMC along with the first positioning message.
21. The first CU according to claim 15, wherein: The at least one processor is further configured to: receiving a second positioning message from the first LMC, the second positioning message including the first identifier for the location session; and Based on the first information for the location session, the second positioning message is sent to the UE.
22. The first CU according to claim 15, wherein: The at least one processor is further configured to: receiving a second positioning message from the UE, the second positioning message including the first identifier for the location session; and Based on the first information for the location session, the second positioning message is sent to the first LMC.
23. The first CU according to claim 15, wherein: The at least one processor is configured to perform handover to the second gNB by being configured to: Determine to hand over the UE to the second gNB; Sending a handover request message to the second gNB, where the handover request message includes the first information for the location session; completing handover of the UE to the second gNB; receiving a location session update message from the second gNB, the location session update message including an identifier of the second gNB; Sending the location session update message to the first LMC; as well as The first information for the location session is deleted.
24. The first CU according to claim 23, wherein: The second CU in the second gNB receives the switching request message, wherein the second CU stores second information for the location session, the second information for the location session includes at least a portion of the first information for the location session, and the second CU sends the location session update message to the first CU.
25. The first CU according to claim 15, wherein: The first entity is the AMF, wherein the first positioning message is a Nlmf_Location_determineLocation request service operation, wherein the first positioning message is received within a Next Generation Application Protocol NGAP downlink DL transmission message.
26. The first CU according to claim 25, further comprising: Receive a Nlmf_Location_determineLocation response service operation from the first LMC, wherein: The Nlmf_Location_determineLocation response service operation includes a location estimate of the UE; Sending a Nlmf_Location_determineLocation response service operation in a NGAP Uplink UL Transport message to the AMF; and The first information for the location session is deleted.
27. The first CU according to claim 15, wherein: The first entity is the UE, wherein the first positioning message includes an event report of a periodic or triggered location of the UE and a routing identifier, the routing identifier indicating any LMC or serving LMC, and wherein the at least one processor is further configured to determine the first LMC based at least in part on the routing identifier.
28. The first CU according to claim 27, wherein: The routing identifier indicates the serving LMC, wherein the first LMC is different from the serving LMC, wherein the at least one processor is configured to forward the event report to the first LMC by being configured to send the event report and an indication of the first LMC to the serving LMC.
29. A first central unit CU in a first new radio NR Node B gNB in a radio access network RAN, the first CU being configured to support a location session of a user equipment UE, the first CU comprising: means for receiving, from a first entity, a first positioning message for the UE; means for determining a first location management component LMC; A component for storing first information for a location session, wherein the first information for the location session includes an identifier of the first LMC, an identifier of the UE, and a first identifier for the location session; A component configured to forward a first positioning message to the first LMC; as well as Means for performing handover of the UE to a second gNB, whereby the second gNB supports continuation of the location session.
30. A non-transitory storage medium comprising program code stored thereon, the program code being operable to cause at least one processor in a first central unit CU in a first New Radio NR Node B gNB in a Radio Access Network RAN to support a location session for a User Equipment UE, comprising: program code for receiving, from a first entity, a first positioning message for the UE; Program code for determining a first location management component LMC; program code for storing first information for a location session, the first information for the location session comprising an identifier of the first LMC, an identifier of the UE, and a first identifier for the location session; program code for forwarding a first positioning message to a first LMC; as well as Program code for performing handover of the UE to a second gNB, whereby the second gNB supports continuation of the location session.
