Method and apparatus for managing user plane connections

Abstract

According to an aspect, there is provided a method for execution by a first network node (e.g. AMF node). The method involves enabling a first user plane connection for a communication device (e.g. UE) to a first location management node (e.g. first LMF node), and enabling a second user plane connection for the communication device to a second location management node (e.g. second LMF node). In accordance with an embodiment of the disclosure, the first user plane connection and the second user plane connection co-exist in time (i.e. can be used at the same time). Furthermore, some embodiments introduce a mechanism to indicate to the communication device which user plane connection is to be moved to a target location management node in a relocation scenario when the multiple user plane connections exist for the communication device.

Description

[0001] METHOD AND APPARATUS FOR

[0002] MANAGING USER PLANE CONNECTIONS

[0003] Related Applications

[0004] [1] This patent application claims priority from US provisional patent application no. US 63 / 744,923 filed on January 14, 2025 and PCT provisional patent application no. PCT / CN2025 / 088171 filed on April 9, 2025, which are both incorporated by reference in their entirety.

[0005] Field of the Disclosure

[0006] [2] This disclosure relates to mobile communication systems, and more particularly to managing user plane connections.

[0007] Background

[0008] [3] None of the material in the background section should be interpreted to be Applicant’s admitted prior art.

[0009] [4] Location Services User Plane Protocol (LCS-UPP) was introduced in Release 18 of Third Generation Partnership Project (3GPP) Technical Specification (TS) to provide transport of LTE Positioning Protocol (LPP) messages and LCS supplementary services messages via a user plane connection.

[0010] [5] To utilize the user plane positioning via LCS-UPP, a User Equipment (UE) and a Location Management Function (LMF) shall establish an LCS secured user plane connection. The LCS secured user plane connection is achieved by a Transport Layer Security (TLS) connection over a TCP connection, which is established between the UE and the LMF.

[0011] [6] 3GPP TS 23.273 entitled “5G System (5GS) Location Services (LCS); Stage 2” version 19.1.0 dated 2024-12-20 (hereinafter “TS 23.273 V19.1.0”) does not explicitly state how many LCS secured user plane connections per UE is allowed. However, 3GPP TS 23.273 V19.1.0 teaches the following in subclause 6.18.3:2. [Conditional] Steps 3-10 of figure 6.18.2-1 are performed between AMF (or Target AMF), UE, and Target LMF with addition that UE also terminate connection to Source LMF.

[0012] 3. The AMF sends an Nlmf_Location_UPConfig Request towards the source LMF. The message may include a request for the Source LMF to terminate a specific user plane connection to the UE and the Target LMF identification. Alternatively, it may include information about AMF reallocation.

[0013] NOTE 2: AMF relocation does not necessarily always cause LMF reselection, the AMF relocation information can keep the LMF informed.

[0014] 4-5. [Conditional] The source LMF may invoke an Nlmf_Location_LocationContextTransfer Request service operation towards the target LMF to provide the current location context(s) of the UE, if there is user plane based periodic and triggered UE location events report context(s). The target LMF informs source LMF of the location context transfer operation results.

[0015] 6. [Conditional] If the user plane connection to source LMF is still active, the source LMF terminates the connection to the UE.

[0016] The underline text has a hint that there might be multiple user plane connections connect to the same UE at the same time (i.e. the multiple user plane connections coexist in time and thus can be used at the same time).

[0017] [7] According to 3GPP TS 29.518 entitled “5G System; Access and Mobility Management Services; Stage 3” version 19.1.0 dated 2025-01-07 (hereinafter “TS 29.518”, an AMF can have only one LcsUPContext for the UE:

[0018] Table 6.1.6.2.84-1: Definition of type LcsUpContext

[0019]

[0020] The bold text indicates that the AMF can store only one LcsUpContext.Summary of the Disclosure

[0021] [8] If AMF selects an LMF which does not have LCS-UPP, but based on UE context there is an LMF which has LCS-UPP connection to the UE, then the selected LMF may initiate LCS-UPP towards the UE which shall be rejected by the UE since UE has already LCS-UPP with the other LMF. This can cause extra delay in the positioning service.

[0022] [9] A workaround is possible if one LMF registered in NRF with LCS-UPP capability, but operators might deploy multiple LMFs for different positioning requests, and there is no reason to limit only one LMF can have the LCS-UPP connection to the UE. Selected LMF which capable of LCS-UPP is not aware that UE has already LCS-UPP connection with other LMF then it may try initiate LCS-UPP which can cause delay in positioning service.

[0023]

[0010] According to an embodiment, it is proposed to allow multiple user plane connections per UE (e.g. multiple user plane connections to different LMFs for a UE). Note that UE can have multiple UP connections to different LMFs, e.g. triggered by different positioning requests, and those UP connections can be used at the same time.

[0024]

[0011] For the scenario of Modification of User Plane Connection between UE and LMF as specified in subclause 6.18.3 of TS 23.273 V19.1.0, when the target LMF move the existing user plane connection in step 2, since there might more than one user plane connections toward the UE, the target LMF shall indicate to the UE which user plane connection is to be moved. This enables the UE to know which user plane connection is to be moved during an LMF relocation.

[0025]

[0012] For example, when an LMF relocation happens and UE has two UP connections (i.e. UPC1: UE to LMF1, and UPC2: UE to LMF2), when LMF1 needs to be changed to LMF3, UE has to know if it’s UPC1 or UPC2 to be changed to a UP connection. If it’s UPC1, then the UE should stop sending the positioning information to LMF1 , and move the UPC1 to a new UP connection.

[0026]

[0013] Therefore, some embodiments introduce a mechanism to indicate to the UE which user plane connection is to be moved to the target LMF in the scenario of LMF relocation when multiple user plane connections exist between the UE and LMFs.In some implementations, the AMF indicates original / source LMF information (e.g, the original LMF LCS-UP address) to the Target LMF during the LMF relocation. In some implementations, the original LMF LCS-UP address is sent from the target LMF to the UE in the USER PLANE CONNECTION ESTABLISHMENT COMMAND message which triggers the UE to establish the LCS secured user plane connection towards the target LMF. It might happen that more than one user plane connection is to be moved to the same LMF, so more than one original LMF LCS-UP address can be included in the USER PLANE CONNECTION ESTABLISHMENT COMMAND message.

[0027]

[0014] According to an aspect, there is provided a method for execution by a first network node (e.g. AMF node). The method involves enabling a first user plane connection for a communication device (e.g. UE) to a first location management node (e.g. first LMF node), and enabling a second user plane connection for the communication device to a second location management node (e.g. second LMF node). In accordance with an embodiment of the disclosure, the first user plane connection and the second user plane connection co-exist in time.

[0028]

[0015] In some implementations, the method also involves, upon an event triggering movement of the first user plane connection or the second user plane connection, sending source user plane information (e.g. original LMF LCS-UP address) of a source location management node to a target location management node (e.g. target / third LMF node) involved in the movement, such that the source user plane information of the source location management node can identify which user plane connection is to be moved. Note that the source location management node is the first location management node when the first user plane connection is being moved or the second location management node when the second user plane connection is being moved.

[0029]

[0016] According to another aspect, there is provided a non-transitory computer readable medium (CRM) having recorded thereon statements and instructions that, when executed by a processor of a first network node (e.g. AMF node), configure the first network node to implement a method as summarized above.

[0030]

[0017] According to another aspect, there is provided a first network node (e.g. AMF node). The first network node has a network interface configured to communicatewith other network nodes and control circuitry coupled to the network interface. The control circuitry is configured to enable a first user plane connection for a communication device (e.g. UE) to a first location management node (e.g. first LMF node), and to enable a second user plane connection for the communication device to a second location management node (e.g. second LMF node). In accordance with an embodiment of the disclosure, the first user plane connection and the second user plane connection co-exist in time.

[0031]

[0018] In some implementations, the control circuitry is also configured to implement a method as summarized above.

[0032]

[0019] According to another aspect, there is provided a method for execution by a target location management node (e.g. target / third LMF node). The method involves receiving, from a first network node (e.g. AMF node), source user plane information (e.g. original LMF LCS-UP address) of a source location management node. The method also involves identifying, based on the source user plane information of the source location management node, a user plane connection for a communication device (e.g. UE) that is to be moved. The method also involves facilitating movement of the user plane connection including sending to the communication device an indication of the user plane connection of the source location management node and the target location management node.

[0033]

[0020] In some implementations, the target location management node sends the indication via a user plane connection establishment command message which triggers the communication device to establish a new user plane connection towards the target location management node.

[0034]

[0021] According to another aspect, there is provided a non-transitory computer readable medium (CRM) having recorded thereon statements and instructions that, when executed by a processor of a target location management node (e.g. target / third LMF node), configure the target location management node to implement a method as summarized above.

[0035]

[0022] According to another aspect, there is provided a target location management node (e.g. target / third LMF node). The target location management nodehas a network interface configured to communicate with other network nodes, and control circuitry coupled to the network interface. The control circuitry is configured to receive, from a first network node (e.g. AMF node) via the network interface, source user plane information (e.g. original LMF LCS-UP address) of a source location management node. The control circuitry is also configured to identify, based on the source user plane information of the source location management node, a user plane connection for a communication device (e.g. UE) that is to be moved. The control circuitry is configured to facilitate movement of the user plane connection including sending, to the communication device via the network interface, an indication of the user plane connection of the source location management node and the target location management node.

[0036]

[0023] In some implementations, the control circuitry is also configured to implement a method as summarized above.

[0037]

[0024] According to another aspect, there is provided a method for execution by a communication device (e.g. UE). The method involves establishing a first user plane connection with a first location management node (e.g. first LMF node), and establishing a second user plane connection with a second location management node (e.g. second LMF node). The method also involves receiving an indication that the second user plane connection is to be moved from the second location management node to a target location management node (e.g. target / third LMF node), and halting communication (e.g. stop sending positioning information) with the second location management node and instead move the second user plane connection to a new user plane connection involving the target location management node.

[0038]

[0025] In some implementations, the communication device receives the indication via a user plane connection establishment command message which triggers the communication device to establish the new user plane connection towards the target location management node.

[0039]

[0026] According to another aspect, there is provided a non-transitory computer readable medium (CRM) having recorded thereon statements and instructions that, when executed by a processor of a communication device (e.g. UE), configure the communication device to implement a method as summarized above.

[0027] According to another aspect, there is provided a communication device (e.g. UE). The communication device has a wireless access radio configured to communicate with a wireless network, and control circuitry coupled to the wireless access radio. The control circuitry is configured to establish a first user plane connection with a first location management node (e.g. first LMF node), and establish a second user plane connection with a second location management node (e.g. second LMF node). The control circuitry is also configured to receive an indication that the second user plane connection is to be moved from the second location management node to a target location management node (e.g. target / third LMF node), and halt communication (e.g. stop sending positioning information) with the second location management node and instead move the second user plane connection to a new user plane connection involving the target location management node.

[0040]

[0028] In some implementations, the control circuitry is also configured to implement a method as summarized above.

[0041]

[0029] One of the objects of the disclosure is to provide an improved solution for location management. In particular, one of the problems to be solved by the disclosure is that the existing solution for establishing user plane connection between UE and LMF may not work properly in multiple user plane connections per UE scenario.

[0042]

[0030] According to a first aspect of the disclosure, a method at a first location management node is provided. The method may comprise obtaining location management node information of the first location management node. Location management node information of a location management node is for establishing a user plane connection between a terminal device and the location management node. The method may further comprise sending the location management node information of the first location management node to a first terminal device.

[0043]

[0031] According to a second aspect of the disclosure, a method at an access and mobility management node is provided. The method may comprise obtaining location management node information of the first location management node. Location management node information of a location management node is for establishing a user plane connection between a terminal device and the location management node. Themethod may further comprise sending the location management node information of the first location management node to a first terminal device.

[0044]

[0032] According to a third aspect of the disclosure, a method at a first terminal device is provided. The method may comprise receiving, from a network node, location management node information of a first location management node. Location management node information of a location management node is for establishing a user plane connection between a terminal device and the location management node. The method may further comprise establishing a first user plane connection between the first terminal device and the first location management node based on the location management node information of the first location management node.

[0045]

[0033] According to a fourth aspect of the disclosure, a first location management node is provided. The first location management node may comprise processing circuitry and a memory. The processing circuitry may be configured to obtain location management node information of the first location management node. Location management node information of a location management node is for establishing mapping a user plane connection between a terminal device and the location management node. The processing circuitry may be further configured to send the location management node information of the first location management node to a first terminal device.

[0046]

[0034] According to a fifth aspect of the disclosure, an access and mobility management node is provided. The access and mobility management node may comprise processing circuitry and a memory. The processing circuitry may be configured to obtain location management node information of the first location management node. Location management node information of a location management node is for establishing a user plane connection between a terminal device and the location management node. The processing circuitry may be further configured to send the location management node information of the first location management node to a first terminal device.

[0047]

[0035] According to a sixth aspect of the disclosure, a first terminal device is provided. The first terminal device may comprise processing circuitry and a memory. The processing circuitry may be configured to receive, from a network node, locationmanagement node information of a first location management node. Location management node information of a location management node is for establishing a user plane connection between a terminal device and the location management node. The processing circuitry may be further configured to establish a first user plane connection between the first terminal device and the first location management node based on the location management node information of the first location management node.

[0048]

[0036] According to a seventh aspect of the disclosure, a computer program is provided. The computer program may comprise instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method according to any of the above first to third aspects.

[0049]

[0037] According to an eighth aspect of the disclosure, a computer program product is provided. The computer program product may comprise instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method according to any of the above first to third aspects.

[0050]

[0038] According to a ninth aspect of the disclosure, a computer-readable medium is provided. The computer-readable medium may comprise instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method according to any of the above first to third aspects.

[0051]

[0039] According to a tenth aspect of the disclosure, a carrier is provided. The carrier may contain the computer program according to the above seventh aspect. The carrier may be one of an electronic signal, optical signal, radio signal, or computer-readable medium.

[0052]

[0040] According to an eleventh aspect of the disclosure, a method implemented in a communication system is provided. The communication system may include two or more of: a first location management node, an access and mobility management node and a first terminal device. The method may comprise two or more of: steps of the method according to the above first aspect, steps of the method according to the above second aspect and steps of the method according to the above third aspect.

[0053]

[0041] According to a twelfth aspect of the disclosure, a communication system is provided. The communication system may include two or more of: a first locationmanagement node according to the above fourth aspect, an access and mobility management node according to the above fifth aspect and a first terminal device according to the above sixth aspect.

[0054]

[0042] With any one of the above first to twelfth aspects, the first terminal device and / or the network (e.g. the first location management node or the access and mobility management node) can be allowed to know which user plane connection is mapped to which location management node information. In particular, when location management node relocation occurs, the first terminal device can know which user plane connection should be replaced.

[0055]

[0043] Other aspects and features of the present disclosure will become apparent, to those ordinarily skilled in the art, upon review of the following description of the various embodiments of the disclosure.

[0056] Brief Description of the Drawings

[0057]

[0044] Embodiments will now be described with reference to the attached drawings in which:

[0058] Figure 1 is a diagram illustrating an exemplary communication system into which an embodiment of the disclosure is applicable;

[0059] Figure 2 is a flowchart illustrating a method performed by a first location management node according to an embodiment of the disclosure;

[0060] Figures 3A to 3C are flowcharts each illustrating a method performed by a first location management node according to an embodiment of the disclosure;

[0061] Figure 4 is a flowchart illustrating a method performed by an access and mobility management node according to an embodiment of the disclosure;

[0062] Figure 5A to 5C are flowcharts each illustrating a method performed by an access and mobility management node according to an embodiment of the disclosure;

[0063] Figure 6 is a flowchart illustrating a method performed by a first terminal device according to an embodiment of the disclosure;Figure 7 is a flowchart illustrating the existing process for positioning via a User Plane Connection between UE and LMF;

[0064] Figures 8 and 9 are flowcharts each illustrating an exemplary process according to an embodiment of the disclosure;

[0065] Figure 10 is a block diagram illustrating an apparatus suitable for use in practicing some embodiments of the disclosure;

[0066] Figure 11 is a diagram showing an example of a communication system in accordance with some embodiments;

[0067] Figure 12 is a diagram showing a UE in accordance with some embodiments;

[0068] Figure 13 is a diagram showing a network node in accordance with some embodiments; and

[0069] Figure 14 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized;

[0070] Figure 15 is a block diagram of a communication system, in accordance with an embodiment of the disclosure;

[0071] Figure 16 is a flowchart of a method of managing user plane connections, in accordance with an embodiment of the disclosure;

[0072] Figure 17 is a sequence drawing of a procedure for how a secure user plane connection between UE and LMF can be modified; and

[0073] Figure 18 is a sequence drawing of a procedure triggered by UE to support positioning over the user plane connection between UE and LMF.

[0074] Detailed Description of Embodiments

[0075]

[0045] It should be understood at the outset that although illustrative implementations of one or more embodiments of the present disclosure are provided below, the disclosed systems and / or methods may be implemented using any number of techniques. The disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary designs and implementations illustrated and described herein, but may be modified within the scope of the appended embodiment along with their full scope of equivalents.Introduction

[0076]

[0046] Referring now to Figure 15, shown is a block diagram of a communication system 1500, in accordance with an embodiment of the disclosure. The communication system 1500 has a communication device 1510 (e.g. UE) capable of accessing a network 1502, which might for example include a 5G network, a 6G network, and / or some other network. Note that there can be numerous other communication devices 151 Oa-c. The network 1502 has several network nodes including a first network node 1520, first and second location management nodes 1530 and 1540, a target location management node 1550, and may have other network nodes 1560 as well.

[0077]

[0047] The communication device 1510 has a wireless access radio 1515 configured to access the network 1502, a CRM 1519, and control circuitry 1516 coupled to the wireless access radio 1515 and the CRM 1519. In some implementations, the control circuitry 1516 includes a processor 1517 that executes software, which can stem from a memory 1518. However, other implementations are possible and are within the scope of this disclosure. The communication device 1510 can have additional components, but these are not shown for simplicity. In some implementations, the communication device 1510 is a UE. Other implementations are possible.

[0078]

[0048] The first network node 1520 has a network interface 1525 configured to communicate with other nodes of the communication system 1500, a CRM 1529, and control circuitry 1526 coupled to the network interface 1525 and the CRM 1529. In some implementations, the control circuitry 1526 includes a processor 1527 that executes software, which can stem from a memory 1528. However, other implementations are possible and are within the scope of this disclosure. The first network node 1520 can have additional components, but these are not shown for simplicity. In some implementations, the first network node 1520 is an AMF node. Other implementations are possible.

[0079]

[0049] Details of the first and second location management nodes 1530 and 1540 are omitted for simplicity. In some implementations, the first and second location management nodes 1530 and 1540 are LMF nodes. Other implementations are possible.

[0050] The target location management node 1550 has a network interface 1555 configured to communicate with other nodes of the communication system 1500, a CRM 1559, and control circuitry 1556 coupled to the network interface 1555 and the CRM 1559. In some implementations, the control circuitry 1556 includes a processor 1557 that executes software, which can stem from a memory 1558. However, other implementations are possible and are within the scope of this disclosure. The target location management node 1550 can have additional components, but these are not shown for simplicity. In some implementations, the target location management node 1550 is a target LMF node. Other implementations are possible.

[0080]

[0051] In accordance with an embodiment of the disclosure, the communication system 1500 enables the communication device 1510 to simultaneously establish and use a first user plane connection with the first location management node 1530 and a second user plane connection with the second location management node 1540. However, in the event that one of the user plane connections is to be moved to the target location management node 1550, a problem is how to inform the communication device 1510 about which user plane connection is to be moved, given that there are multiple user plane connections toward the communication device 1510.

[0081]

[0052] The control circuitry 1516 of the communication device 1510, the control circuitry 1526 of the first network node 1520, and the control circuitry 1556 of the target location management node 1550, implement a method of managing user plane connections. Such operation by the control circuitries 1516, 1526 and 1556 will be described below with reference to Figure 16. Although the method of Figure 16 is described below with reference to the communication system 1500 shown in Figure 15, it is to be understood that the method of Figure 16 is applicable to other communication systems. In general, the method of Figure 16 is applicable to any appropriately configured communication system.

[0082]

[0053] At step 1601 , there is established or enabled a first user plane connection for the communication device 1510 to the first location management node 1530. At step 1602, there is established or enabled a second user plane connection for the communication device 1510 to the second location management node 1540. In accordance with an embodiment of the disclosure, the first user plane connection andthe second user plane connection co-exist in time. Therefore, the first user plane connection and the second user plane connection can be used at the same time.

[0083]

[0054] At step 1603, upon an event triggering movement of the first user plane connection or the second user plane connection, the first network node 1520 sends source user plane information of a source location management node to the target location management node 1550. The source user plane information (e.g. original / source LMF LCS-UP address) of the source location management node can identify which user plane connection is to be moved. The source location management node is the first location management node 1530 when the first user plane connection is being moved or the second location management node 1540 when the second user plane connection is being moved.

[0084]

[0055] It is noted that the source user plane information might not be sent directly to the target location management node 1550 at step 1603. Instead, the source user plane information might be sent to an intermediate node (e.g. a source LMF node which is the second LMF node 1540 in this example) which in turn conveys the source user plane information to the target location management node 1550. In another embodiment, the first network node 1520 sends, to the source LMF node (e.g. the second LMF node 1540), a message indicating the target LMF node 1550 for the movement, such that the source LMF node can then send the source user plane information to the target LMF node 1550. In this way, the message sent from the first network node 1520 to the source LMF node might not actually include the source user plane information. Other implementations are possible.

[0085]

[0056] There are many possibilities for the source user plane information. In some implementations, the source user plane information includes an original / source LMF address as already suggested above. However, other routing information is possible. In another implementation, location management node information is used as described later with reference to Figure 2. More generally, any suitable original / source user plane information from which the user plane connection to be moved can be identified can be used.

[0086]

[0057] At step 1604, the target location management node 1550 sends an indication of the user plane connection (e.g. original LMF LCS-UP address) to be movedfrom the second location management node to the target location management node 1550. In this example, it is assumed that the second user plane connection is to be moved, and hence the target location management node 1550 identifies the second user plane connection. This enables the communication device 1510 to know which user plane connection is to be moved.

[0087]

[0058] In some implementations, the indication is sent at step 1604 via a user plane connection establishment command message which triggers the communication device to establish a new user plane connection towards the target location management node. Other implementations are possible.

[0088]

[0059] At step 1605, the communication device 1510 halts communication (e.g. stop sending positioning information) with the second location management node 1540 and instead moves the second user plane connection to a new user plane connection involving the target location management node 1550. At step 1606, the new user plane connection is in use instead of the second user plane connection.

[0089]

[0060] It might happen that more than one user plane connection is to be moved to the same target location management node 1550. In that case, more than one indication (e.g. multiple original LMF LCS-UP addresses) can be included in the user plane connection establishment command message at step 1604.

[0090]

[0061] It is noted that the AMF node 1520 can be informed of the change I move by a source LMF node. For example, in some implementations, the second LMF node 1540 notifies the AMF node 1520, and then the AMF node 1520 can send source LMF routing information to the target LMF node 1550, and then the target LMF node 1550 can include it in a UPP-CM message sent to the UE 1510. Other implementations are possible.

[0091]

[0062] According to another embodiment of the disclosure, there is provided a non-transitory CRM having recorded thereon statements and instructions that, when executed by the processor 1517 of the communication device 1510, implement a method as described herein. The non-transitory computer readable medium can be the memory 1518 and / or the CRM 1519 of the communication device 1510 shown in Figure 15, or some other non-transitory CRM.

[0063] According to another embodiment of the disclosure, there is provided a non-transitory CRM having recorded thereon statements and instructions that, when executed by the processor 1527 of the first network node 1520, implement a method as described herein. The non-transitory computer readable medium can be the memory 1528 and / or the CRM 1529 of the first network node 1520 shown in Figure 15, or some other non-transitory CRM.

[0092]

[0064] According to another embodiment of the disclosure, there is provided a non-transitory CRM having recorded thereon statements and instructions that, when executed by the processor 1557 of the target location management node 1550, implement a method as described herein. The non-transitory computer readable medium can be the memory 1558 and / or the CRM 1559 of the target location management node 1550 shown in Figure 15, or some other non-transitory CRM.

[0093]

[0065] Examples of a non-transitory CRM include memory, an SSD (Solid State Drive), a hard disk drive, a CD (Compact Disc), a DVD (Digital Video Disc), a BD (Blu-ray Disc), a memory stick, etc. Other non-transitory CRMs are also possible.

[0094]

[0066] The illustrated examples described herein focus on software implementations. However, other implementations are possible and are within the scope of this disclosure. Other implementations can include additional or alternative hardware components, such as any appropriately configured FPGA (Field-Programmable Gate Array), ASIC (Application-Specific Integrated Circuit), and / or microcontroller, for example. Thus, the control circuitry 1516 of the communication device 1510, the control circuitry 1526 of the first network node 1520, and the control circuitry 1556 of the target location management node 1550 can instead be implemented with any suitable combination of hardware, software and / or firmware.

[0095]

[0067] Further example details are provided in the following sections. It is to be understood that the following sections are very specific and are provided merely for exemplary purposes, such that other implementations are possible and within the scope of the disclosure.Modification of User Plane Connection between UE and LMF

[0096]

[0068] A problem with one LCS-UPP connection per UE is that if AMF needs to select an LMF and if we want to leverage the user plane connection then AMF needs to select that LMF which has LCS-UPP based on UE context. In this case other selection criteria like slice information, tracking area, etc. cannot be used if those selection criteria are mutual exclusive. If operator wants to deploy LMFs for different positioning purposes and uses cases, then allowing only one LCS-UPP per UE limits the possibilities of user plane positioning solution.

[0097]

[0069] Referring now to Figure 17, shown is a sequence drawing of a procedure for how a secure user plane connection between UE and LMF can be modified. The flow describes change of LMF but applies also when source and target LMF is the same. The procedure can also be used to terminate the user plane connection to Source LMF not selecting any Target LMF. Steps 1701 through 1707 are described below.

[0098]

[0070] At step 1701a [Conditional], the LMF discovers a need to change LMF or re-establish the user plane connection between UE and LMF or terminate the user plane connection, e.g. after receiving an event report via user plane from UE or after receiving an AMF relocation information from a target AMF (target AMF obtains from source AMF the UE LCS-UP context which indicates UE has maintained LCS-UP connection with the source LMF, the target AMF may inform the source LMF about the AMF change using the Nlmf_Locatoion_UPConfig request). The LMF sends an Nlmf_Location_UPNotify message that includes connection move (termination and establishment) or termination is required and if connection move is requested then message may include target LMF identification. The address of the AMF was provided to LMF as a "Notification Target Address" in latest Nlmf_Location_UPConfig message or Nlmf_Location_UP Subscribe message. If the LMF is going to terminate the user plane connection, step 1701a, step 1703, step 1706 and step 1707 are performed and other steps are skipped.

[0099] If the request is to terminate the user plane connection, the AMF releases the LCS-UP context.NOTE 1: The LMF change procedure is independent from the SSC mode of the PDU Session with dedicated DNN used for positioning. For SSC mode 2 / 3, PSA UPF connection with the LMF can be relocated with UE movement and LMF can discover the need to change LMF to reduce the user plane path latency.

[0100]

[0071] At step 1701b [Conditional], AMF based on target LMF identification received from source LMF for user plane positioning, or AMF may perform LMF reselection if UE moves to a new location (which may be out of serving area of source LMF and in serving area of target LMF) and select the target LMF for the current UE location based on LMF service area, LMF user plane positioning capability information and other information listed in clause 5.1. LMF needs to be capable to establish a user plane session for positioning with the UE. After AMF relocation, the target AMF may trigger the LMF reselection and LCS-UP connection modification procedure, e.g. if the source LMF does not perform LMF reselection.

[0101]

[0072] At step 1702 [Conditional], steps 1803 to 18010 of Figure 18 described below are performed between AMF (or Target AMF), UE, and Target LMF if Target LMF and the UE does not have already the user plane connection. UE also terminate connection to Source LMF.

[0102]

[0073] At step 1703, the AMF sends an Nlmf_Location_UPConfig Request towards the source LMF. The message may include a request for the Source LMF to terminate a specific user plane connection to the UE and the Target LMF identification. Alternatively, it may include information about AMF reallocation.

[0103] NOTE 2: AMF relocation does not necessarily always cause LMF reselection, the AMF relocation information can keep the LMF informed.

[0104]

[0074] At steps 1704 and 1705 [Conditional], the source LMF may invoke an Nlmf_Location_LocationContextTransfer Request service operation towards the target LMF to provide the current location context(s) of the UE, if there is user plane based periodic and triggered UE location events report context(s). The target LMF informs source LMF of the location context transfer operation refappfsults.

[0105]

[0075] At step 1706 [Conditional], if the user plane connection to source LMF is still active, the source LMF terminates the connection to the UE.

[0076] At step 1707, the LMF sends Nlmf_Location_UPConfig Response message to AMF to confirm connection termination or acknowledge change of AMF. If this procedure is used for termination, the AMF will release the LCS-UP context after receiving the response message.

[0106] UE initiated User Plane Connection

[0107]

[0077] UE may trigger the user plane connection establishment if the UE does not have user plane connection with LMF. Referring now to Figure 18, shown is a sequence drawing of a procedure triggered by UE to support positioning over the user plane connection between UE and LMF. Steps 1801 through 1811 are described below.

[0108]

[0078] At step 1801, the UE sends a user plane connection establishment request to AMF via Non-Access Stratum (NAS) Message, if there is no established secure user plane connection between the UE and LMF and UE decides to request a user plane connection for upcoming positioning requests.

[0109]

[0079] At step 1802 [Conditional], if the UE is authorized based on UE Subscription to use the user plane positioning, AMF selects an LMF which is capable to establish a user plane session for positioning with the UE. AMF may either query the NRF or based on local configuration to discover and select a proper LMF.

[0110]

[0080] At step 1803 [Conditional], the AMF sends a Nlmf_Location_UPConfig Request towards LMF to request set up of an LCS-UP connection. The AMF shall include the target UE identity (see 3GPP TS 29.572 entitled “5G System; Location Management Services; Stage 3” version 19.1.0 dated 2025-01-07, hereinafter “TS 29.572) (SUPI and / or GPSI) in the request.

[0111]

[0081] At step 1804 [Conditional], if LMF accepts to utilize user plane for positioning and there is no established secure user plane connection between the UE and LMF, LMF sends a user plane information to AMF to indicate UE to accept and utilize user plane for positioning. The user plane information includes the user plane positioning address of the LMF. The LMF allocates a LCS-UP binding ID to associate the user plane connection to be established with the target UE and includes the LCS-UP binding ID in the user plane information. The LMF associates the target UE identity (SUPI and / or GPSI) with the LCS-UP binding ID.

[0082] At step 1805 [Conditional], when AMF receives the user plane information from LMF in step 1804, AMF forwards it to UE via a DL NAS TRANSPORT message.

[0112]

[0083] At step 1806 [Conditional], if there is no established secure user plane connection, UE establishes a secured user plane connection with LMF. UE uses the user plane positioning address of the LMF, together with the information in the URSP, to determine the PDU session parameters including DNN+S-NSSAI. UE uses the PDU session parameter to establish PDU session. When SMF receives the request, it selects a proper UPF based on the DNN+S-NSSAI, and establishes the connection between the UPF and LMF.

[0113]

[0084] After the secured user plane connection has been established successfully, the UE sends the LCS-UP binding ID received in step 1804 to LMF via the secured user plane connection to enable LMF to perform the correlation of the UE with this secured user plane connection. The LCS-UP binding ID will be released once the correlation is complete.

[0114]

[0085] At step 1807 [Conditional], UE sends an acknowledgement to LMF through AMF to indicate a success of user plane connection establishment for positioning service or a failure to utilize the user plane connection as defined in 3GPP TS 24.572 entitled “5G System (5GS); User plane Location Services (LCS) protocols and procedures; Stage 3” version 19.1.0 dated 2025-01-10 ‘hereinafter “TS 24.572 V19.1.0”.

[0115]

[0086] At step 1808 [Conditional], AMF sends the acknowledgement received in step 1807 to the LMF via Namf_N1messageNotify service.

[0116]

[0087] At step 1809 [Conditional], LMF responds to AMF that user plane connection between the UE and LMF has been established.

[0117]

[0088] At step 1810 [Conditional], the AMF stores the LCS-UP connection context as part of UE context.

[0118]

[0089] At step 1811 [Conditional], after the secure user plane connection is established, if LMF determines to utilize the user plane connection for positioning after receiving a positioning request from AMF, or UE determines to utilize the user planeconnection for positioning, LPP messages are transferred between UE and LMF for UE based positioning, UE assisted positioning and delivery of assistance data. Supplementary services messages including event report messages, periodic triggered invoke messages and MS cancel deferred location messages may also be transferred between LMF and UE via the established user plane connection.

[0119]

[0090] In TS 29.572: AMF to include the original / source LMF information(e.g. the original LMF LCS-UP address, or the original LMF LCS-UP identification) to the Target LMF for the LMF relocation:

[0120] Table 6.1.6.2.52-1: Definition of type UpConfig

[0121]

[0122]

[0091] In TS 24.572 V19.1.0, a new IE for the original / source LMF information, e.g LMF LCS-UP address(s) are added in the USER PLANE CONNECTION ESTABLISHMENT COMMAND:Table 10.3.1.1.1: USER PLANE CONNECTION ESTABLISHMENT COMMAND message content

[0123]

[0124]

[0092] This invention may impact TS 24.572 V19.1.0 and TS 29.572.

[0125]

[0093] The following sections provide non-limiting examples of how certain aspects of the proposed solutions could be implemented within the framework of a specific communication standard. The changes described in these sections are merely intended to illustrate how certain aspects of the proposed solutions could be implemented in a particular standard. However, the proposed solutions could also be implemented in other suitable manners, both in the 3GPP Specification and in other specifications or standards.

[0126] Discussion on Number of LCS-UPP Connections

[0127]

[0094] Introduction: In SA2#165 SA2 meeting CR has been postponed defining the number of LCS-UPP connections per UE. Now this discussion paper analyses the situation and proposes the possible way forward.

[0128]

[0095] Background: LCS-UPP defined in rel18 to use user plane connection between UE and LMF to transfer Ipp and supplementary services instead of using control plane. Based on stage 3 work and specification it is possible to maintain only one LCS-UPP, but it was never a stage 2 intention to limit number of connections to one. The problem with one LCS-UPP connection per UE is that if AMF needs to select an LMF and if we want to leverage the user plane connection then AMF needs to selectthat LMF which has LCS-UPP based on UE context. In this case other selection criteria like slice information, tracking area, etc. cannot be used if those selection criteria are mutual exclusive. If operator wants to deploy LMFs for different positioning purposes and uses cases, then allowing only one LCS-UPP per UE limits the possibilities of user plane positioning solution.

[0129] Observation #1 : Based on the existing solutions if we want to leverage user plane connection for positioning AMF shall select LMF which has LCS-UPP based on UE context.

[0130]

[0096] Discussion: Based on CT4 TS 29.518 AMF can have only one LcsUPContext for the UE:

[0131] Table 6.1.6.2.84-1: Definition of type LcslIpContext

[0132]

[0133] Observation #2: AMF can store only one LcsUpContext.

[0134]

[0097] If AMF selects that LMF which does not have LCS-UPP - but based on UE context there is an LMF which has LCS-UPP connection to the UE - then the selected LMF may initiate LCS-UPP towards the UE which shall be rejected by the UE since UE has already LCS-UPP with other LMF. This can cause extra delay in the positioning service.

[0135]

[0098] Workaround could work if one LMF registered in NRF with LCS-UPP capability, but operators might deploy multiple LMFs for different positioning requests, and there is no reason to limit only 1 LMF can have the LCS-UPP connection to the UE.

[0136] Observation #3: Selected LMF which capable of LCS-UPP is not aware that UE has already LCS-UPP connection with other LMF then it may try initiate LCS-UPP which can cause delay in positioning service.

[0099] Rel-18 has been frozen. Stage 3 does not extend functionalities in cell 8. Therefore, the proposal is to keep this behaviour in rel-18 and accept only one LCS-UPP connection per UE. Stage 3 for rel-19 is not frozen yet therefore the proposal is to allow one LCS-UPP connections per UE towards each LMFs in rel-19.

[0137] Proposal #1 : Specify that in rel-18 the number of LCS-UPP connection pert UE can be one.

[0138] Proposal #2: Define in rel-19 UE can have one LCS-UPP connection towards each LMFs.

[0139] Proposals:

[0140] Proposal #1: Specify that in rel-18 the number of LCS-UPP connection pert UE to one.

[0141] Proposal #2: Define in rel-19 or rel-20 that UE can have one LCS-UPP connection towards each LMFs.

[0142] Number of User Plane Connections for User Plane (3GPP TS 23.273 V19.1.0)

[0143]

[0100] Reason for change: As it described in DP SA2-25xxxxx the problem with one LCS-UPP connection per UE is that if AMF needs to select an LMF and if we want to leverage the user plane connection then AMF needs to select that LMF which has LCS-UPP based on UE context. In this case other selection criteria like slice information, tracking area, etc. cannot be used if those selection criteria are mutual exclusive. If operator wants to deploy LMFs for different positioning purposes and uses cases, then allowing only one LCS-UPP per UE limits the possibilities of user plane positioning solution.

[0144]

[0101] Summary of change: Adding that UE shall have maximum one LCS-UPP connection towards each LMFs.

[0145]

[0102] Consequences if not approved: When AMF needs to select an LMF and we want to leverage the user plane connection then AMF needs to select that LMF which has LCS-UPP based on UE context if only one LCS-UPP possible per UE. In this case other selection criteria like slice information cannot be used if those selectioncriteria are mutual exclusive. If operator wants to deploy LMFs for different positioning purposes and uses cases, then allowing only one LCS-UPP per UE limits the possibilities of user plane positioning solution.

[0146]

[0147] 6.18.0 General

[0148] Clause 6.18 describes the management of the user plane connection between UE and LMF. LMF or UE may trigger the establishment of the user plane connection.

[0149] UE and LMF may maintain the established user plane connection. LMF may modify or terminate the established user plane connection between UE and LMF. UE may have more LCS-UPP connection, UE shall have maximum one LCS-UPP connection towards each LMFs.

[0150] Precondition:

[0151] The LMF can send its user plane information (i.e. IP address or FQDN) to the UE via a DL NAS TRANSPORT message of the AMF. If LMF sends its FQDN to the UE, a DNS server / resolver is used to resolve the IP address of LMF (e.g. EASDF or local DNS for local LMF address resolution). UE uses URSP which includes user plane positioning related PDU session parameters (e.g. a dedicated DNN and S-NSSAI) to establish a PDU session used for user plane positioning. SMF should select a PSA UPF (located in central site or local site) connecting with the LMF for this PDU session, based on S-NSSAI, DNN and UE location information, etc.

[0152] Session break out for local LMF service for user plane positioning can be supported by preconfiguring SMF with local LMF(s) IP address(es) / network prefix(es) and their DNAIs for positioning dedicated PDU session in certain service area(s) for local PSA and UL CL / BP insertion.

[0153] NOTE 1: Based on preconfigured local LMF information, SMF can subscribe to UE location information from AMF and perform additional local PSA and UL CL / BP insertion and corresponding forwarding rules configuration if UE moves to a location where it can be served by local LMF(s).

[0154] NOTE 2: In this Release, to avoid LMF selection conflicts, the LMFs use their dedicated FQDNs which are different from each other, but their FQDNs can have common parts in support of usage as Traffic descriptor in URSP.

[0155] NOTE 3: It is up to operator to determine appropriate QoS parameters for user plane connection between UE and LMF.Other Embodiments

[0156]

[0103] For the purpose of explanation, details are set forth in the following description in order to provide a thorough understanding of the embodiments disclosed. It is apparent, however, to those skilled in the art that the embodiments may be implemented without these specific details or with an equivalent arrangement.

[0157]

[0104] SA2 agreed to support multiple user plane connections per user equipment (UE) in Rel-19 and now is discussing how to support it.

[0158]

[0105] According to the perspective of the inventors of the present disclosure, for the multiple user plane connections per UE scenario, there are more than one user plane connections between UE and several location management functions (LMFs). It would be advantageous for UE to know which user plane connection is for which LMF. So there should be a mapping in UE and network (NW) side on LMF information (e.g. LMF ID) and user plane connection.

[0159]

[0106] The present disclosure proposes an improved solution for location management. Hereinafter, the solution will be described in detail with reference to FIG. 1 to FIG. 14.

[0160]

[0107] FIG. 1 is a diagram illustrating an exemplary communication system into which an embodiment of the disclosure is applicable. As shown, the communication system comprises a user equipment (UE) 101, a (radio) access network ((R)AN) 102, a user plane function (UPF) 103, a data network (DN) 104, a network slice-specific and SNPN authentication and authorization function (NSSAAF) 105, an authentication server function (AUSF) 106, an access and mobility management function (AMF) 107, a session management function (SMF) 108, a service communication proxy (SCP) 109, a network slice admission control function (NSACF) 110, a network slice selection function (NSSF) 111, a network exposure function (NEF) 112, a network repository function (NRF) 113, a policy control function (PCF) 114, a unified data management (UDM) 115, an application function (AF) 116, and a location management function (LMF) 117. The term SNPN refers to standalone non-public network. The functional description of the above entities can be found from clause 6 of 3GPP TS 23.501 entitled“System architecture for the 5G System (5GS)” version 19.2.0 dated 2024-12-20 (hereinafter “TS 23.501”).

[0161]

[0108] As used herein, the term “communication system” refers to a system following any suitable communication standards, such as the first generation (1G), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G, 6G communication protocols, and / or any other protocols either currently known or to be developed in the future. The specific terms used herein do not limit the present disclosure only to the communication system related to the specific terms, which however can be more generally applied to other communication systems. Note that the network node (or network function) mentioned in this document may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g. on a cloud infrastructure.

[0162]

[0109] The term terminal device may also be referred to as, for example, device, access terminal, user equipment (UE), mobile station, mobile unit, subscriber station, or the like. It may refer to any end device that can access a wireless communication network and receive services therefrom. By way of example and not limitation, the terminal device may include a portable computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and playback appliance, a mobile phone, a cellular phone, a smart phone, a tablet, a wearable device, a personal digital assistant (PDA), or the like.

[0163]

[0110] In an Internet of things (loT) scenario (e.g. a narrow-band loT (NB-loT) scenario), the terminal device may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another terminal device and / or a network equipment. As an example, the terminal device may be a machine-to-machine (M2M) device, which may, in a 3GPP context, be referred to as a machine-type communication (MTC) device. Particular examples of such machines or devices may include sensors, metering devices such as power meters, industrial machineries, bikes, vehicles, or home or personal appliances, e.g. refrigerators, televisions, personal wearables such as watches, and so on.

[0164]

[0111] FIG. 2 is a flowchart illustrating a method performed by a first location management node according to an embodiment of the disclosure. The locationmanagement node may be a network node implementing LMF or any other network node having similar functionality. At block 202, the first location management node obtains location management node information of the first location management node. Location management node information (e.g. LMF information) of a location management node is for establishing a user plane connection between a terminal device and the location management node (e.g. for mapping the location management node to the corresponding user plane connection). For example, the location management node information of a location management node may comprise a location management node identifier (ID) of the location management node. Examples of the location management node ID of the location management node may comprise but not limited to: a network address (e.g. an Internet protocol (IP) address, or a location services (LCS) user plane (UP) address) of the location management node; and a fully qualified domain name (FQDN) of the location management node.

[0165]

[0112] As a first option, block 202 may be implemented as block 306 of FIG. 3. At block 306, the first location management node determines the location management node information of the first location management node. For example, the determined location management node information may be globally unique per operator / public land mobile network (PLMN). In this way, the location management node information may be determined by the first location management node independently to skip any interaction with other network nodes (e.g. an AMF).

[0166]

[0113] As a second option, block 202 may be implemented as blocks 308 and 310 of FIG. 3. The second option corresponds to a case where the first location management node is a location management node that initially triggers establishment of user plane connection. At block 308, the first location management node sends, to an access and mobility management node, a first indication for indicating that a new user plane connection is to be established. The access and mobility management node may be a network node implementing an AMF or any other network node having similar functionality. At block 310, the first location management node receives, from the access and mobility management node, the location management node information of the first location management node.

[0167]

[0114] As a third option, block 202 may be implemented as blocks 314 and 310 of FIG. 3. The third option corresponds to a case where the first location managementnode is a target location management node in location management node relocation. A source location management node in the location management node relocation is a second location management node. At block 314, the first location management node sends, to the access and mobility management node, a second indication for indicating that the first user plane connection to be established between the first terminal device and the first location management node is to replace a second user plane connection between the first terminal device and the second location management node. At block 310, the first location management node receives, from the access and mobility management node, the location management node information of the first location management node. For the second and third options, the location management node information is determined by the access and mobility management node.

[0168]

[0115] At block 204, the first location management node sends the location management node information of the first location management node to a first terminal device. For example, the location management node information of the first location management node may be sent to the first terminal device via an access and mobility management node. Thus, block 204 may comprise block 212. At block 212, the first location management node sends, to the access and mobility management node, user plane information of a first user plane connection to be established between the first terminal device and the first location management node. The user plane information of the first user plane connection comprises the location management node information of the first location management node. For example, the user plane information of the first user plane connection may be contained in a first message for establishing the first user plane connection between the first terminal device and the first location management node. As an exemplary example, the first message may be a User Plane Connection Establishment Command message. In response to the user plane information or the first message, the access and mobility management node may send, to the first terminal device, a second message (e.g. a downlink (DL) non-access stratum (NAS) Transport message) containing the user plane information or the first message.

[0169]

[0116] With the method of FIG. 2, the first terminal device and / or the network (e.g. the first location management node or the access and mobility management node) can be allowed to know which user plane connection is mapped to which location management node information. In particular, when location management noderelocation occurs, the first terminal device can know which user plane connection should be replaced.

[0170]

[0117] FIG. 4 is a flowchart illustrating a method performed by an access and mobility management node according to an embodiment of the disclosure. At block 402, the access and mobility management node obtains location management node information of the first location management node. Location management node information of a location management node is for establishing a user plane connection between a terminal device and the location management node. For example, the location management node information of a location management node may comprise a location management node ID (e.g. LMF ID) of the location management node. Examples of the location management node ID of the location management node may comprise but not limited to: a network address (e.g. an IP address, or a LCS-UP address) of the location management node; and a FQDN of the location management node.

[0171]

[0118] As a first option, block 402 may be implemented as block 506 of FIG. 5. At block 506, the access and mobility management node receives, from the first location management node, the location management node information of the first location management node. For the first option, the location management node information is determined by the first location management node. For example, the location management node information of the first location management node may be received in user plane information of a first user plane connection to be established between the first terminal device and the first location management node. For example, the user plane information of the first user plane connection may be contained in a first message for establishing the first user plane connection. As an exemplary example, the first message may be a User Plane Connection Establishment Command message.

[0172]

[0119] As a second option, block 402 may be implemented as blocks 508 and 510 of FIG. 5. The second option corresponds to a case where the first location management node is a location management node that initially triggers establishment of user plane connection. At block 508, the access and mobility management node receives, from the first location management node, a first indication for indicating that a new user plane connection is to be established. At block 510, the access and mobilitymanagement node determines the location management node information of the first location management node.

[0173]

[0120] For the second option, the method at the access and mobility management node may further comprise block 512 of FIG. 5. At block 512, the access and mobility management node may send, to the first location management node, the location management node information of the first location management node. In this way, the first location management node may trigger establishment of the first user plane connection by using the location management node information of the first location management node.

[0174]

[0121] For the second option, the method at the access and mobility management node may further comprise block 514 of FIG. 5. At block 514, the access and mobility management node may receive, from the first location management node, user plane information of a first user plane connection to be established between the first terminal device and the first location management node. The user plane information of the first user plane connection comprises the location management node information of the first location management node. For example, the user plane information of the first user plane connection may be contained in a first message for establishing the first user plane connection. As an exemplary example, the first message may be a User Plane Connection Establishment Command message.

[0175]

[0122] As a third option, block 402 may be implemented as blocks 516 and 510 of FIG. 5. The second option corresponds to a case where the first location management node is a target location management node in location management node relocation. A source location management node in the location management node relocation is a second location management node. At block 516, the access and mobility management node receives, from the first location management node, a second indication for indicating that the first user plane connection to be established between the first terminal device and the first location management node is to replace a second user plane connection between the first terminal device and the second location management node. At block 510, the access and mobility management node determines the location management node information of the first location management node. Similarly to the second option, for the third option, the method at the access and mobility management node may further comprise block 512 and / or 514.

[0123] At block 404, the access and mobility management node sends the location management node information of the first location management node to a first terminal device. As an example, the location management node information of the first location management node may be sent in response to the user plane information or the first message received from the first location management node. The location management node information of the first location management node may be sent in a second message (e.g. a DL NAS Transport message) containing the user plane information or the first message. Alternatively, the location management node information of the first location management node is separate from the user plane information of the first user plane connection and both the location management node information and the user plane information are contained in the second message. It is also possible that the location management node information of the first location management node may be sent in response to the first indication or the second indication. In this case, block 514 may be optional. With the method of FIG. 4, the same effect as the method of FIG. 2 can be achieved.

[0176]

[0124] FIG. 6 is a flowchart illustrating a method performed by a first terminal device according to an embodiment of the disclosure. At block 602, the first terminal device receives, from a network node, location management node information of a first location management node. Location management node information of a location management node is for establishing a user plane connection between a terminal device and the location management node. For example, the network node may be the first location management node or an access and mobility management node. At block 604, the first terminal device establishes a first user plane connection between the first terminal device and the first location management node based on the location management node information of the first location management node. With the method of FIG. 6, the same effect as the method of FIG. 2 can be achieved.

[0177]

[0125] To facilitate the explanation of the enhancements proposed by the present disclosure, FIG. 7 is Figure 6.18.1-1 of 3GPP TS 23.273 entitled “5G System (5GS) Location Services (LCS); Stage 2” version 19.2.0 dated 2025-01-07 (hereinafter TS 23.273 V19.2.0”) and illustrates the existing process for positioning via a User Plane Connection between UE and LMF initiated by LMF. Details about the process can befound from section 6.18.1 of 3GPP TS 23.273 V19.2.0. FIG. 8 and FIG. 9 each illustrate an exemplary process according to an embodiment of the disclosure.

[0178]

[0126] The process of each of FIG. 8 and FIG. 9 are based on the considerations that for multiple location services (LCS) secured user plane connections per UE scenario, UE should have the mapping information about which LMF is for which LCS secured user plane connection. For this end, LMF ID assigned by AMF is used when establishing the LCS secured user plane connection. So in 3GPP TS 24.572 entitled “5G System (5GS); User plane Location Services (LCS) protocols and procedures; Stage 3” version 19.2.0 dated 2025-03-20 (hereinafter “TS 24.572 V19.2.0”), LMF includes LMF information (e.g. LMF ID including e.g. LMF LCS-UP address) to UE in USER PLANE CONNECTION ESTABLISHMENT COMMAND message.

[0179]

[0127] In the NW side, AMF assigns the LMF ID each time when establishing the user plane connection. There may be 2 cases. In Case 1 , the LMF initiates User Plane Connection. The existing process is illustrated in FIG. 7. The exemplary process of the present disclosure shown in FIG. 8 corresponds to Case 1. In the process, it is the LMF triggers establishment, for establishing a new user plane connection scenario. At step 2, one new indication is introduced. It indicates the request of establishing a new user plane connection. Then, AMF allocates the LMF ID, between step 2 and 3. A new step 2a is added with a message from AMF to LMF to send the LMF ID to LMF. At a new step 2b, LMF includes the LMF ID in the USER PLANE CONNECTION ESTABLISHMENT COMMAND. The Nlmf_Location_UPNotify at step 2b is normally used for notification, and another embodiment could be Namf_communication_N1N2MessageTransfer (user plane info(LMF ID)).

[0180]

[0128] The exemplary process of the present disclosure shown in FIG. 9 corresponds to Case 2 (i.e. LMF relocation scenario). In the process, when target LMF triggers establishing the user plane connection, it sends, at step 2, a new indication to AMF on replacing an existing user plane connection, the LMF ID (or IP address) of the LMF to be replaced. Then AMF deletes the LMF ID for the old LMF and allocates a LMF ID for the new LMF, and sends them to the new LMF at a new step 2a. The new LMF includes its LMF ID and the LMF ID of original (or old) LMF in the USER PLANE CONNECTION ESTABLISHMENT COMMAND to the UE at a new step 2b. At step 3, both source LMF ID and target LMF ID are included in the USER PLANE CONNECTIONESTABLISHMENT COMMAND message. Note it is possible that the messages used at step 2a and step 2b may be same as the message used at step 2.

[0181]

[0129] Therefore, with respect to AMF allocated LMF ID, as a first option, AMF may send LMF ID to LMF, then LMF send LMF ID inside “user plane info” to UE via AMF (AMF transparently relays user plane info). As a second option, AMF may send LMF ID to UE in DL NAS Transport message (user plane info, LMF ID).

[0182]

[0130] It is also possible that LMF allocates LMF ID. As long as LMF make sure the ID is globally unique per operator / PLMN, then the flow can skip interaction with AMF for LMF ID allocation. LMF may send the LMF ID in “user plane info” to UE via AMF: Namf_communication_N1N2MessageTransfer (user plane info(LMF ID)); DL NAS Transport message (user plane info(LMF ID)).

[0183]

[0131] Therefore, the present disclosure introduces a mechanism to provide the UE a LMF ID for an user plane connection during user plane connections establishment procedure, so UE and NW can use the LMF ID to map to a specific LCS secured user plane connection.

[0184]

[0132] The NW assigns and sends the LMF ID to the UE in the USER PLANE CONNECTION ESTABLISHMENT COMMAND message when establishing the LCS secured user plane connection towards the target LMF.

[0185]

[0133] And two new indicators are introduced from LMF to AMF to indicate if the LCS secured user plane connection to be established is a new LCS secured user plane connection, or a replacement of an existing LCS secured user plane connection. AMF allocates / deletes the LMF ID for it accordingly, and sent the LMF ID of the LMF establishing the LCS secured user plane connection to the UE.

[0186]

[0134] With the introduced mechanism, it enables the UE and NW to know which user plane connection is mapped to which LMF ID. So when the LMF relocation occurs, the UE knows which LCS secured user plane connection should be replaced.

[0187]

[0135] Based on the above description, the following changes may be proposed to be made to TS 24.572 V19.2.0, where the proposed changes are highlighted with underlines.Table 10.3.1.1.1: USER PLANE CONNECTION ESTABLISHMENT COMMAND message content

[0188]

[0189]

[0136] In addition, there may be a change request (CR) proposed for 3GPP TS 23.273 V19.2.0. Note that the added content proposed by the CR relative to 3GPP TS 23.273 V19.2.0 will be highlighted with underlines, and deleted content will be represented

[0190]

[0191]

[0137] The title of the CR for 3GPP TS 23.273 V19.2.0 is “Supporting multiple LCS-UPP connections per UE”. The reason for change is described as below. As it is described in DP S2-2501607 in SA2#167 the problem with one LCS-UPP connection per UE is that if AMF needs to select an LMF and if we want to leverage the user plane connection then AMF needs to select that LMF which has LCS-UPP based on UE context. In this case other selection criteria like slice information, tracking area, etc. cannot be used if those selection criteria are mutual exclusive.

[0192]

[0138] The summary of change is as below: adding that UE shall support several LCS-UPP connection, each towards different LMF; updating UE and AMF functionality with multiple LCS-UPP support; updating user plane modification procedure.

[0193]

[0139] The consequences if the CR is not approved are as below. When AMF needs to select an LMF and we want to leverage the user plane connection then AMF needs to select that LMF which has LCS-UPP based on UE context if only one LCS-UPP possible per UE. In this case other selection criteria like slice information cannotbe used if those selection criteria are mutual exclusive. If operator wants to deploy LMFs for different positioning purposes and uses cases, then allowing only one LCS-UPP per UE limits the possibilities of user plane positioning solution.

[0194]

[0140] The first change is as shown below.

[0195] 4.3.5 UE

[0196] A target UE may support positioning according to four different modes :

[0197] - -UE assisted mode (the UE obtains location measurements and sends the measurements to another entity (e . g. an LMF) to compute a location) ;

[0198] - -UE based mode (the UE obtains location measurements and computes a location estimate making use of assistance data provided by serving PLMN) ;

[0199] - -standalone mode (the UE obtains location measurements and computes a location estimate without making use of assistance data provided by serving PLMN) ;

[0200] - -network based mode (a serving PLMN obtains location measurements of signals transmitted by a target UE and computes a location estimate) .

[0201] NOTE : The transmission of UE signals for network based mode may or may not be transparent to the UE .

[0202] Positioning procedures used by a UE for NG-RAN access are described in TS 38.305

[0009] .

[0203] A limited set of UE positioning capabilities and UE user plane positioning capabilities including multiple LCS-UPP connections capability can be transferred to the 5GCN in the 5GMM capability during registration of the UE as described in

[0204] TS 24.501

[0011] . Some of these positioning capabilities may be transferred subsequently to an LMF as described inTS 29.572

[0012] . UE positioning capabilities may also be transferred directly to a location server (e . g. LMF) .

[0205] Additional functions which may be supported by a UE to support location services include the following.

[0206] - -Support location requests received from a network for 5GC- MT-LR, 5GC-NI-LR or a deferred 5GC-MT-LR for periodic or triggered location.

[0207] - -Support location requests to a network for a 5GC-MO-LR.

[0208] - -Support privacy notification and verification for a 5GC- MT-LR or deferred 5GC-MT-LR for periodic or triggered location .

[0209] - -Send updated privacy requirements to a serving AMF ( for transfer to a UDR via UDM) .

[0210] - -Support periodic or triggered location reporting to an LMF.

[0211] - -Support change of a serving LMF for periodic or triggered location reporting.

[0212] - -Support cancelation of periodic or triggered location reporting .

[0213] - -Support multiple simultaneous location sessions .

[0214] - -Support the reception of unciphered and / or ciphered assistance data broadcast by NG-RAN.

[0215] - -Support the reception of ciphering keys for the assistance data from the AMF.

[0216] - -Support handling of 5GC-MT-LR, 5GC-NI-LR, 5GC-MO-LR and deferred 5GC-MT-LR for periodic or triggered location over a user plane connection between UE and LMF.- -Support multiple LCS-UPP connections, each to a different LMF.

[0217] - -Support reporting of location events for a periodic or triggered 5GC-MT-LR over a user plane connection to an LCS Client or AF with periodic cumulative event reports being sent over control plane to the LMF, H-GMLC and LCS Client or AF.

[0218]

[0141] The next change is as shown below.

[0219] 4.3.7 Access and Mobility Management Function, AMF

[0220] The AMF contains functionality responsible for managing positioning for a target UE for all types of location request . The AMF is accessible to the GMLC and NEF via the Namf interface, to the RAN via the N2 reference point and to the UE via the N1 reference point .

[0221] Functions which may be performed by an AMF to support location services include the following.

[0222] - -Initiate an NI-LR location request for a UE with an IMS emergency call or to know a UE geographical area with NR satellite access for PLMN selection verification.

[0223] - -Receive and manage location requests from a GMLC for a 5GC-MT-LR and deferred 5GC-MT-LR for periodic, triggered and UE available location events .

[0224] - -Receive and manage location requests from a UE for a 5GC- MO-LR.

[0225] - -Receive and manage Event Exposure request for location information from an NEF.

[0226] - -Select an LMF.

[0227] - -Receive updated privacy requirements from a UE and transfer to a UDR via UDM.- -Support cancelation of periodic or triggered location reporting for a target UE .

[0228] - -Support cancelation of a 5GC-MT-LR or 5GC-M0-LR during UE mobility from 5GS to EPS with N26 interface .

[0229] - -Support change of a serving LMF for periodic or triggered location reporting for a target UE .

[0230] - -When assistance data is broadcast by 5GS in ciphered form, the AMF receives ciphering keys from the LMF and forwards to suitably subscribed UEs using mobility management procedures .

[0231] - -Store UE Positioning Capability received from an LMF and send the UE Positioning Capability along with the received location request to an LMF.

[0232] - -Receive and store UE user plane positioning capabilities (the user plane positioning using LCS-UPP and / or the user plane positioning using SUPL

[0049] ) as part of the "5GMM capability" from UE .

[0233] - -Receive UL NAS Transport including a PRU Association, Association Update, or Disassociation Request (contained in an LCS supplementary service message) from a UE .

[0234] - -AMF may verify whether a UE can serve as a PRU based on UE subscription data after receiving the PRU Association Request, Association Update, or Disassociation. AMF may also use local policy to determine if UEs are allowed to serve as a PRU. AMF may verify based on subscription information or local policy if PRU can work as stationary PRU.

[0235] - -Sends the PRU Association Request or PRU Disassociation Request to LMF and may include a UE verification indication indicating whether this UE is authorized to serve as a PRU.- -Support verifying whether UE is subscribed with user plane positioning between UE and LMF and triggering LMF to establish a User Plane Connection to UE if UE requested that .

[0236] - -Support subscribing from LMF status of LCS user plane connection between a UE and the LMF.

[0237] - -Store in UE context that UE has [a] multiple

[0238] [maintained] User Plane connections with certain LMFs .

[0239] NOTE : Details of UE Positioning Capability is defined in

[0240] TS 37 . 355

[0020] .

[0241] - -Support of local configuration of a mapping table of UE identifier ranges and LMF identifier ( s ) or querying the UDM the LMF identifier for a UE for a 5GC-MO-LR.

[0242] - -Support the 5G to EPS Handover by providing the target MME ID to GMLC as part of the LCS Service response .

[0243] - -Support interaction with NWDAF to obtain UE related analytics to assist with UE location verification for NR satellite access .

[0244]

[0142] The next change is as shown below.

[0245] 5.10 Support of Positioning over user plane connection between UE and LMF for non-regulatory service

[0246] LMF and UE may utilize a user plane connection to transfer supplementary services messages and LPP messages . User Plane protocol (LCS-UPP) to support supplementary services messages and LPP messages transport between the UE and the LMF is defined in TS 24.572

[0048] .

[0247] If LMF decides to use user plane the LMF should indicate the UE to use user plane for positioning with the information to establish a secure connection, and via this secure connection,position messages can be transferred between UE and the LMF. The URSP defined in TS 23.503

[0041] is used by UE to determine how to route the position messages . The operator may provide LMF (s) address information and connection capability for LCS use in traffic descriptors and LCS user plane positioning dedicated PDU session parameters (e . g. , DNN and S-NSSAI ) in Route Selection Descriptors to the UE as part of the URSP rule . The position messages can be routed to an established PDU Session or can trigger the establishment of a new PDU Session. The LMF and UE may maintain the established user plane connection and the established user plane connection may be reused for subsequent user plane position messages transmission trigged by UE or LMF. If the LMF detects the user plane connection is not used for an implementation specific time, the LMF terminates the user plane connection. The supplementary services messages transferred over user plane only support event report messages, periodic triggered invoke messages and MS cancel deferred location messages . If a deferred location session initiated by sending periodic triggered invoke message to the UE on a user plane connection, then UE associates this deferred location session to the user plane connection, i . e . UE uses the user plane connection if exists to send event-report for this deferred location session.

[0248] NOTE 1 : In this Release, the user plane connection between UE and LMF can not be used for regulatory positioning service .

[0249] NOTE 2 : For one positioning procedure, the LMF selects either control plane or user plane to transfer the associated supplementary services messages and LPP messages .

[0250] During the positioning procedure, the LMF and UE should avoid switching between control plane and user plane to transfer the messages above .

[0143] The next change is as shown below.

[0251] 6.18.0 General

[0252] Clause 6.18 describes the management of the user plane connection between UE and LMF. LMF or UE may trigger the establishment of the user plane connection.

[0253] UE and LMF may maintain the established user plane connection. LMF may modify or terminate the established user plane connection between UE and LMF. UE may have multiple LCS-UPP connections, UE shall have maximum one LCS-UPP connection towards each LMF.

[0254] Precondition :

[0255] The LMF can send its user plane information (i . e . IP address or FQDN) to the UE via a DL NAS TRANSPORT message of the AMF. If LMF sends its FQDN to the UE, a DNS server / resolver is used to resolve the IP address of LMF (e . g. EASDF or local DNS for local LMF address resolution) . UE uses URSP which includes user plane positioning related PDU session parameters (e . g. a dedicated DNN and S-NSSAI ) to establish a PDU session used for user plane positioning. SMF should select a PSA UPF (located in central site or local site) connecting with the LMF for this PDU session, based on S-NSSAI, DNN and UE location information, etc .

[0256] Session break out for local LMF service for user plane positioning can be supported by preconfiguring SMF with local LMF (s) IP address ( es ) / network prefix (es) and their DNAIs for positioning dedicated PDU session in certain service area (s) for local PSA and UL CL / BP insertion.NOTE 1 : Based on preconfigured local LMF information, SMF can subscribe to UE location information from AMF and perform additional local PSA and UL CL / BP insertion and corresponding forwarding rules configuration if UE moves to a location where it can be served by local LMF (s) .

[0257] NOTE 2 : In this Release, to avoid LMF selection conflicts, the LMFs use their dedicated FQDNs which are different from each other, but their FQDNs can have common parts in support of usage as Traffic descriptor in URSP .

[0258] NOTE 3 : It is up to operator to determine appropriate QoS parameters for user plane connection between UE and LMF.

[0259]

[0144] The next change is as shown below.

[0260] 6.18.1 LMF initiated User Plane Connection

[0261] LMF may trigger the user plane connection establishment after receiving a location request from AMF if target UE does not have user plane connection with this LMF. AMF may subscribe from LMF the status of LOS user plane connection for the target UE, using a Nlmf_Location_UP Subscribe message if the UE supports user plane positioning. Figure 6.18.1-1 shows a procedure triggered by LMF to support positioning over the user plane connection between UE and LMF.

[0262] Figure 6.18.1-1: Positioning via a User Plane Connection between UE and LMF initiated by LMF

[0263] NOTE 1 : User Plane protocol (LCS-UPP) to support generic transport between the UE and the LMF is defined in TS 24 . 572

[0048] .

[0264] - 1. Based on UE user plane positioning capability, control plane congestion status (e . g. AMF load status) and other implementation factors, LMF decides whether to usethe positioning procedure via a user plane connection between UE and LMF.

[0265] LMF may invoke Nnrf_NFDiscovery service operation to retrieve control plane congestion status (e . g. AMF load information) . LMF may also invoke Nnrf_NFManagement_NFStatusSubscribe service to subscribe specific AMF load information. Based on AMF load information, LMF may determine to use user plane positioning, if there is available user plane connection between UE and LMF.

[0266] Steps 2-8 are skipped if there is already a user plane connection context of the target UE in LMF and LMF determines to utilize the user plane connection for positioning .

[0267] NOTE 2 : LMF can select user plane positioning for specific positioning methods (e . g. motion sensor-based method) and it is based on implementation and local configuration to determine which positioning method requires user plane transport .

[0268] NOTE 3 : The procedure can also be triggered when LMF receives a location request from AMF via control plane signalling as defined in clause 6.1 and clause 6.3.

[0269] - 2. [Conditional] If LMF decides to utilize user plane for positioning and there is no established secure user plane connection between the UE and the LMF, LMF invokes Namf_communication_NlN2MessageTransf er service operation to send the user plane information to AMF in a NAS container to indicate UE to utilize user plane over TLS for positioning. The user plane information includes the user plane positioning address of the LMF. The LMF allocates LCS-UP binding ID to be used to associate the user planeconnection to be established with the target UE and includes this LCS-UP binding ID in the user plane information. The LMF associates the target UE identity (SUPI and / or GPSI ) with this LCS-UP binding ID.

[0270] - If the UE supports the user plane positioning capability and AMF has not subscribed the status of LCS user plane connection, the AMF may subscribe from LMF the status of LCS user plane connection.

[0271] - If user plane connection context exists for this UE and UE does not support multiple LCS-UPP connections, then AMF rej ects the request .

[0272] NOTE 4 : Security mechanism to support user plane positioning is defined in Annex Q.2 of TS 33.501

[0050] .

[0273] - 3. [Conditional] When AMF receives the user plane information from LMF in step 2, AMF sends it to UE via a DL NAS TRANSPORT message .

[0274] - 4. [Conditional] If there is no established applicable PDU session for the user plane positioning, the UE uses the URSP as defined in TS 23.503

[0041] which includes user plane positioning related PDU session parameters, e . g. a dedicated DNN and S-NSSAI, to establish the PDU session for user plane positioning. UE establishes a secured user plane connection with LMF if there is no established secure user plane connection towards the LMF. If LMF send its FQDN to the UE, a DNS server / resolver is used to resolve the IP address of LMF (e . g. EASDF or local DNS for local LMF address resolution) . After the secured user plane connection been established successfully, the UE sends the LCS-UP binding ID received in step 3 to LMF via the secured user plane connection to enable LMF to perform the correlation of the UE with the secured user planeconnection. The LCS-UP binding ID will be released once the correlation is complete .

[0275] - 5. [Conditional] UE sends an acknowledgement to LMF through AMF to indicate a success of user plane connection establishment for positioning service or a failure to utilize the user plane connection as defined in

[0276] TS 24 . 572

[0048] .

[0277] - 6 [Conditional ] AMF sends the acknowledgement received in step 5 to the LMF via Namf_NlmessageNotif y service .

[0278] - 7. [Conditional] LMF indicates AMF in the Nlmf_Location_UPNotif y message that user plane connection between the UE and LMF has been established and provides LMF user plane address .

[0279] Editor ' s note : If LMF user plane address or other ID is used to identify LMF user plane connection will be decided in CT1 WG.

[0280] - 8. [Conditional] The AMF stores the LCS-UP connection context as part of UE context .

[0281] - 9. If LMF or UE determines to utilize the user plane connection for positioning and the secure user plane connection is established, LPP messages are transferred between UE and LMF for UE based positioning, UE assisted positioning and delivery of assistance data . Supplementary services messages including event report messages, periodic triggered invoke messages and MS cancel deferred location messages may also be transferred between LMF and UE via the established user plane connection.

[0282]

[0145] The next change is as shown below.

[0283] 6.18.2 UE initiated User Plane Connection

[0284] UE may trigger the user plane connection establishment if the UEdoes not have user plane connection with a specific LMF. Figure 6.18.2-1 shows a procedure triggered by UE to support positioning over the user plane connection between UE and LMF.

[0285] Figure 6.18.2-1: Positioning via a User Plane Connection between UE and LMF, initiated by UE

[0286] - 1. UE sends a user plane connection establishment request to AMF via NAS Message, if there is no established secure user plane connection between the UE and the LMF and UE decides to request a user plane connection for upcoming positioning requests .

[0287] - 2. [Conditional] If the UE is authorized based on UE Subscription to use the user plane positioning, AMF selects an LMF which capable to establish a user plane session for positioning with the UE and which does not have already user plane connection. AMF may either query the NRF or based on local configuration to discover and select a proper LMF.

[0288] - 3. [Conditional] The AMF sends a Nlmf_Location_UPConf ig Request towards LMF to request set up of an LCS-UP connection. The AMF shall include the target UE identity (see TS 29.572

[0012] ) (SUPI and / or GPSI ) in the request .

[0289] - 4. [Conditional] If LMF accepts to utilize user plane for positioning and there is no established secure user plane connection between the UE and LMF, LMF sends a user plane information to AMF to indicate UE to accept and utilize user plane for positioning. The user plane information includes the user plane positioning address of the LMF. The LMF allocates a LCS-UP binding ID to associate the user plane connection to be established with the target UE and includes the LCS-UP binding ID in the user plane information. The LMF associates the target UE identity (SUPI and / or GPSI ) with the LCS-UP binding ID.- 5. [Conditional] When AMF receives the user plane information from LMF in step 4, AMF forwards it to UE via a DL NAS TRANSPORT message .

[0290] - 6. [Conditional] If there is no established secure user plane connection towards the LMF, UE establishes a secured user plane connection with LMF. UE uses the user plane positioning address of the LMF, together with the information in the URSP, to determine the PDU session parameters including DNN+S-NSSAI . UE uses the PDU session parameter to establish PDU session. When SME receives the request, it selects a proper UPF based on the DNN+S-NSSAI, and establishes the connection between the UPF and LMF.

[0291] After the secured user plane connection has been established successfully, the UE sends the LCS-UP binding ID received in step 4 to LMF via the secured user plane connection to enable LMF to perform the correlation of the UE with this secured user plane connection. The LCS-UP binding ID will be released once the correlation is complete .

[0292] - 7. [Conditional] UE sends an acknowledgement to LMF through AMF to indicate a success of user plane connection establishment for positioning service or a failure to utilize the user plane connection as defined in

[0293] TS 24 . 572

[0048] .

[0294] - 8. [Conditional] AMF sends the acknowledgement received in step 7 to the LMF via Namf_NlmessageNotif y service .

[0295] - 9. [Conditional] LMF responds to AMF that user plane connection between the UE and LMF has been established and provides LMF user plane address .Editor ' s note : If LMF user plane address or other ID is used to identify LMF user plane connection will be decided in CT1 WG.

[0296] - 10. [Conditional] The AMF stores the LCS-UP connection context as part of UE context

[0297] - 11. [Conditional] After the secure user plane connection is established, if LMF determines to utilize the user plane connection for positioning after receiving a positioning request from AMF, or UE determines to utilize the user plane connection for positioning, LPP messages are transferred between UE and LMF for UE based positioning, UE assisted positioning and delivery of assistance data . Supplementary services messages including event report messages, periodic triggered invoke messages and MS cancel deferred location messages may also be transferred between LMF and UE via the established user plane connection.

[0298]

[0146] The next change is as shown below.

[0299] 6.18.3 Modification of User Plane Connection between UE and LMF The figure 6.18.3-1 shows how a secure user plane connection between UE and LMF is modified. The flow describes change of LMF but applies also when source and target LMF is the same . The procedure can also be used to terminate the user plane connection to Source LMF not selecting any Target LMF.

[0300] Figure 6.18.3-1: Connection modification between UE and LMFs

[0301] - la . [Conditional] The LMF discovers a need to change LMF or re-establish the user plane connection between UE and LMF or terminate the user plane connection, e . g. after receiving an event report via user plane from UE or after receiving an AMF relocation information from a target AMF (target AMF obtains from source AMF the UE LCS-UP context which indicates UE has maintained LCS-UP connection withthe source LMF, the target AMF may inform the source LMF about the AMF change using the Nlmf_Locatoion_UPConf ig request) . The LMF sends an Nlmf_Location_UPNotif y message that includes connection move (termination and establishment) or termination is required and if connection move is requested then message may include target LMF identification. The address of the AMF was provided to LMF as a "Notification Target Address" in latest Nlmf_Location_UPConf ig message or Nlmf_Location_UP Subscribe message . If the LMF is going to terminate the user plane connection, step la, step 3, step 6 and step 7 are performed and other steps are skipped.

[0302] If the request is to terminate the user plane connection, the AMF releases the LCS-UP context .

[0303] NOTE 1 : The LMF change procedure is independent from the SSC mode of the PDU Session with dedicated DNN used for positioning. For SSC mode 2 / 3, PSA UPF connection with the LMF can be relocated with UE movement and LMF can discover the need to change LMF to reduce the user plane path latency.

[0304] - lb . [Conditional] AMF should perform LMF reselection if a target LMF identification received from source LMF for user plane positioning, or AMF may perform LMF reselection if a UE established a LCS UP connection with the source LMF to a new location (which may be out of serving area of source LMF and in serving area of target LMF) and select the target LMF for the current UE location based on LMF service area, LMF user plane positioning capability information and other information listed in clause 5.1. LMF needs to be capable to establish a user plane session for positioning with the UE . After AMF relocation, the target AMF may trigger the LMF reselection and LCS-UP connectionmodification procedure, e . g. if the source LMF does not perform LMF reselection.

[0305] - 2. [Conditional ] Steps 3-10 of figure 6.18.2-1 are performed between AMF (or Target AMF) , UE, and Target LMF with following modifications : [with addition that UE also terminate connection to Source LMF] .

[0306] If UE supports multiple LCS-UPP connection:

[0307] - in step 3. , AMF needs to provide Source LMF user plane address to target LMF

[0308] - in step 4. , if Target LMF does not have user plane connection with the UE, user plane information also needs to include Source LMF user plane address; if Target LMF already has user plane connection with the UE, step 4 to step 8 are skipped. Instead, the Target LMF needs to send Source LMF user plane address via User Plane Information message on the user plane connection and the UE sends back the acknowledge on the user plane connection.

[0309] - after step 6. , UE identifies old user plane connection using the source LMF user plane address . The UE assosiates all deferred location sessions associated with old user plane connection to the new user plane connection and terminates old user plane connection. Editor ' s note : If LMF user plane address or other ID is used to identify Source and Target LMF user plane connection will be decided in CT1 WG.

[0310] If UE does not support multiple LCS-UPP connection:

[0311] in step 5. , even though AMF has LCS-UP connection in context, AMF forwards user plane connection establishment request to UE AMF identifies thatconnection establishmert request received from target LMF.

[0312] in step 6. , UE terminates connection to Source LMF before UE establishes the user plane connection to Target LMF.

[0313] In step 10. , AMF updates LCS-UP connection context with the new LMF ID.

[0314] - 3. The AMF sends an Nlmf_Location_UPConf ig Request towards the source LMF. The message may include a request for the Source LMF to terminate a specific user plane connection to the UE and indication that location context (s) have been assigned to user plane connection and the Target LMF identification. Alternatively, it may include information about AMF reallocation.

[0315] NOTE 2 : AMF relocation does not necessarily always cause LMF reselection, the AMF relocation information can keep the LMF informed.

[0316] - 4-5. [Conditional] The source LMF may invoke an Nlmf_Location_LocationContextTransf er Request service operation towards the target LMF to provide the current location context (s) of the UE, if there is user plane based periodic and triggered UE location events report

[0317] context (s) . The target LMF informs source LMF of the location context transfer operation results .

[0318] - 6. [Conditional] If the user plane connection to source LMF is still active or purpose of procedure is user plane connection termination, the source LMF terminates the connection to the UE .

[0319] - 7. The LMF sends Nlmf_Location_UPConf ig Response message to AMF to confirm connection termination or acknowledge change of AMF. If this procedure is used for termination, theAMF will release the LCS-UP context after receiving the response message .

[0320]

[0147] FIG. 10 is a block diagram illustrating an apparatus suitable for use in practicing some embodiments of the disclosure. For example, any one of the first location management node, the access and mobility management node and the first terminal device described above may be implemented through the apparatus 1000. As shown, the apparatus 1000 may include processing circuitry 1010 and a memory 1020. The processing circuitry 1010 may be configured to operate in accordance with the embodiments of the present disclosure, as discussed above. The processing circuitry 1010 may include a processor and / or integrated circuitry for processing and / or control. The processor may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multi-core processor architectures, as non-limiting examples. The integrated circuitry may include, but not limited to, field programmable gate array (FPGA), application specific integrated circuitry (ASIC), etc.

[0321]

[0148] The memory 1020 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memories, magnetic memory devices and systems, optical memory devices and systems, fixed memories and removable memories. The memory 1020 may be configured to store data, instructions and / or other information described herein. In some embodiments, the instructions are executable by the processor, whereby the apparatus 1000 is operative to or configured to operate in accordance with the embodiments of the present disclosure, as discussed above. That is, the embodiments of the present disclosure may be implemented at least in part by computer program executable by the processor, or by hardware, or by a combination of computer program and hardware.

[0322]

[0149] FIG. 11 shows an example of a communication system 3100 in accordance with some embodiments.

[0323]

[0150] In the example, the communication system 3100 includes a telecommunication network 3102 that includes an access network 3104, such as a radioaccess network (RAN), and a core network 3106, which includes one or more core network nodes 3108. The access network 3104 includes one or more access network nodes, such as network nodes 3110a and 3110b (one or more of which may be generally referred to as network nodes 3110), or any other similar 3GPP access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 3102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 3102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 3102, including one or more network nodes 3110 and / or core network nodes 3108.

[0324]

[0151] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1 , E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 3110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 3112a, 3112b, 3112c, and 3112d (one ormore of which may be generally referred to as UEs 3112) to the core network 3106 over one or more wireless connections.

[0325]

[0152] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 3100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 3100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0326]

[0153] The UEs 3112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 3110 and other communication devices. Similarly, the network nodes 3110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 3112 and / or with other network nodes or equipment in the telecommunication network 3102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 3102.

[0327]

[0154] In the depicted example, the core network 3106 connects the network nodes 3110 to one or more host computing systems, such as host 3116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 3106 includes one more core network nodes (e.g., core network node 3108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 3108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), AuthenticationServer Function (ALISF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0328]

[0155] The host 3116 may be under the ownership or control of a service provider other than an operator or provider of the access network 3104 and / or the telecommunication network 3102. The host 3116 may host a variety of applications to provide one or more service. Examples of such applications include live and prerecorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0329]

[0156] As a whole, the communication system 3100 of FIG. 11 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0330]

[0157] In some examples, the telecommunication network 3102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 3102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 3102. For example, the telecommunications network 3102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

[0158] In some examples, the UEs 3112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 3104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 3104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0331]

[0159] In the example, the hub 3114 communicates with the access network 3104 to facilitate indirect communication between one or more UEs (e.g., UE 3112c and / or 3112d) and network nodes (e.g., network node 3110b). In some examples, the hub 3114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 3114 may be a broadband router enabling access to the core network 3106 for the UEs. As another example, the hub 3114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 3110, or by executable code, script, process, or other instructions in the hub 3114. As another example, the hub 3114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 3114 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 3114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 3114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 3114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0332]

[0160] The hub 3114 may have a constant / persistent or intermittent connection to the network node 3110b. The hub 3114 may also allow for a different communication scheme and / or schedule between the hub 3114 and UEs (e.g., UE 3112c and / or 3112d), and between the hub 3114 and the core network 3106. In other examples, thehub 3114 is connected to the core network 3106 and / or one or more UEs via a wired connection. Moreover, the hub 3114 may be configured to connect to an M2M service provider over the access network 3104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 3110 while still connected via the hub 3114 via a wired or wireless connection. In some embodiments, the hub 3114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 3110b. In other embodiments, the hub 3114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 3110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0333]

[0161] FIG. 12 shows a UE 3200 in accordance with some embodiments. The UE 3200 presents additional details of some embodiments of the UE 3112 of FIG. 11. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3GPP, including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0334]

[0162] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user(e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0335]

[0163] The UE 3200 includes processing circuitry 3202 that is operatively coupled via a bus 3204 to an input / output interface 3206, a power source 3208, a memory 3210, a communication interface 3212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIG. 12. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0336]

[0164] The processing circuitry 3202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 3210. The processing circuitry 3202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 3202 may include multiple central processing units (CPUs).

[0337]

[0165] In the example, the input / output interface 3206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 3200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or anycombination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0338]

[0166] In some embodiments, the power source 3208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 3208 may further include power circuitry for delivering power from the power source 3208 itself, and / or an external power source, to the various parts of the UE 3200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 3208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 3208 to make the power suitable for the respective components of the UE 3200 to which power is supplied.

[0339]

[0167] The memory 3210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 3210 includes one or more application programs 3214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 3216. The memory 3210 may store, for use by the UE 3200, any of a variety of various operating systems or combinations of operating systems.

[0340]

[0168] The memory 3210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embeddedIIICC (elllCC), integrated IIICC (illlCC) or a removable IIICC commonly known as ‘SIM card.’ The memory 3210 may allow the UE 3200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 3210, which may be or comprise a device-readable storage medium.

[0341]

[0169] The processing circuitry 3202 may be configured to communicate with an access network or other network using the communication interface 3212. The communication interface 3212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 3222. The communication interface 3212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 3218 and / or a receiver 3220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 3218 and receiver 3220 may be coupled to one or more antennas (e.g., antenna 3222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0342]

[0170] In the illustrated embodiment, communication functions of the communication interface 3212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0171] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 3212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0343]

[0172] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0344]

[0173] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 3200 shown in FIG. 12.

[0174] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0345]

[0175] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0346]

[0176] FIG. 13 shows a network node 3300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0347]

[0177] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units,distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0348]

[0178] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0349]

[0179] The network node 3300 includes a processing circuitry 3302, a memory 3304, a communication interface 3306, and a power source 3308. The network node 3300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 3300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 3300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 3304 for different RATs) and some components may be reused (e.g., a same antenna 3310 may be shared by different RATs). The network node 3300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 3300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 3300.

[0180] The processing circuitry 3302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 3300 components, such as the memory 3304, to provide network node 3300 functionality.

[0350]

[0181] In some embodiments, the processing circuitry 3302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 3302 includes one or more of radio frequency (RF) transceiver circuitry 3312 and baseband processing circuitry 3314. In some embodiments, the radio frequency (RF) transceiver circuitry 3312 and the baseband processing circuitry 3314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 3312 and baseband processing circuitry 3314 may be on the same chip or set of chips, boards, or units.

[0351]

[0182] The memory 3304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 3302. The memory 3304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 3302 and utilized by the network node 3300. The memory 3304 may be used to store any calculations made by the processing circuitry 3302 and / or any data received via the communication interface 3306. In some embodiments, the processing circuitry 3302 and memory 3304 is integrated.

[0352]

[0183] The communication interface 3306 is used in wired or wireless communication of signaling and / or data between a network node, access network,and / or UE. As illustrated, the communication interface 3306 comprises port(s) / terminal(s) 3316 to send and receive data, for example to and from a network over a wired connection. The communication interface 3306 also includes radio frontend circuitry 3318 that may be coupled to, or in certain embodiments a part of, the antenna 3310. Radio front-end circuitry 3318 comprises filters 3320 and amplifiers 3322. The radio front-end circuitry 3318 may be connected to an antenna 3310 and processing circuitry 3302. The radio front-end circuitry may be configured to condition signals communicated between antenna 3310 and processing circuitry 3302. The radio front-end circuitry 3318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 3318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 3320 and / or amplifiers 3322. The radio signal may then be transmitted via the antenna 3310. Similarly, when receiving data, the antenna 3310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 3318. The digital data may be passed to the processing circuitry 3302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0353]

[0184] In certain alternative embodiments, the network node 3300 does not include separate radio front-end circuitry 3318, instead, the processing circuitry 3302 includes radio front-end circuitry and is connected to the antenna 3310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 3312 is part of the communication interface 3306. In still other embodiments, the communication interface 3306 includes one or more ports or terminals 3316, the radio front-end circuitry 3318, and the RF transceiver circuitry 3312, as part of a radio unit (not shown), and the communication interface 3306 communicates with the baseband processing circuitry 3314, which is part of a digital unit (not shown).

[0354]

[0185] The antenna 3310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 3310 may be coupled to the radio front-end circuitry 3318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 3310 is separate from the network node 3300 and connectable to the network node 3300 through an interface or port.

[0186] The antenna 3310, communication interface 3306, and / or the processing circuitry 3302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 3310, the communication interface 3306, and / or the processing circuitry 3302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0355]

[0187] The power source 3308 provides power to the various components of network node 3300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 3308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 3300 with power for performing the functionality described herein. For example, the network node 3300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 3308. As a further example, the power source 3308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0356]

[0188] Embodiments of the network node 3300 may include additional components beyond those shown in FIG. 13 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 3300 may include user interface equipment to allow input of information into the network node 3300 and to allow output of information from the network node 3300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 3300. In some embodiments providing a core network node, such as core network node 108 of FIG. 11 , some components, such as the radio front-end circuitry 3318 and the RF transceiver circuitry 3312 may be omitted.

[0189] FIG. 14 is a block diagram illustrating a virtualization environment 3400 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 3400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 3400 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

[0357]

[0190] Applications 3402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 3400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0358]

[0191] Hardware 3404 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 3406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 3408a and 3408b (one or more of which may be generally referred to as VMs 3408), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 3406 may present a virtual operating platform that appears like networking hardware to the VMs 3408.

[0192] The VMs 3408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 3406. Different embodiments of the instance of a virtual appliance 3402 may be implemented on one or more of VMs 3408, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0359]

[0193] In the context of NFV, a VM 3408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, nonvirtualized machine. Each of the VMs 3408, and that part of hardware 3404 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 3408 on top of the hardware 3404 and corresponds to the application 3402.

[0360]

[0194] Hardware 3404 may be implemented in a standalone network node with generic or specific components. Hardware 3404 may implement some functions via virtualization. Alternatively, hardware 3404 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 3410, which, among others, oversees lifecycle management of applications 3402. In some embodiments, hardware 3404 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 3412 which may alternatively be used for communication between hardware nodes and radio units.

[0195] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0361]

[0196] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0197] As such, it should be appreciated that at least some aspects of the exemplary embodiments of the disclosure may be practiced in various components such as integrated circuit chips and modules. It should thus be appreciated that the exemplary embodiments of this disclosure may be realized in an apparatus that is embodied as an integrated circuit, where the integrated circuit may comprise circuitry (as well as possibly firmware) for embodying at least one or more of a data processor, a digital signal processor, baseband circuitry and radio frequency circuitry that are configurable so as to operate in accordance with the exemplary embodiments of this disclosure.

[0362]

[0198] It should be appreciated that at least some aspects of the exemplary embodiments of the disclosure may be embodied in computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other device. The computer executable instructions may be stored on a computer readable medium such as a hard disk, optical disk, removable storage media, solid state memory, RAM, etc. As will be appreciated by one skilled in the art, the function of the program modules may be combined or distributed as desired in various embodiments. In addition, the function may be embodied in whole or in part in firmware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGA), and the like.

[0363] Clauses

[0364] Clause 1. A method at a first location management node, the method comprising:

[0365] obtaining (202) location management node information of the first location management node, wherein location management node information of a location management node is for establishing a user plane connection between a terminal device and the location management node; and

[0366] sending (204) the location management node information of the first location management node to a first terminal device.Clause 2. The method according to clause 1 , wherein the location management node information of the first location management node is sent in user plane information of a first user plane connection to be established between the first terminal device and the first location management node; and / or

[0367] wherein the location management node information of the first location management node is sent in a first message for establishing the first user plane connection between the first terminal device and the first location management node.

[0368] Clause 3. The method according to clause 1 or 2, wherein obtaining (202) the location management node information of the first location management node comprises:

[0369] determining (306) the location management node information of the first location management node.

[0370] Clause 4. The method according to clause 1 or 2, wherein obtaining (202) the location management node information of the first location management node comprises:

[0371] receiving (310), from an access and mobility management node, the location management node information of the first location management node.

[0372] Clause 5. The method according to clause 4, wherein the first location management node is a location management node that initially triggers establishment of user plane connection; and

[0373] wherein obtaining (202) the location management node information of the first location management node comprises: sending (308), to the access and mobility management node, a first indication for indicating that a new user plane connection is to be established.

[0374] Clause 6. The method according to clause 4, wherein the first location management node is a target location management node in location management node relocation, wherein a source location management node in the location management node relocation is a second location management node; andwherein obtaining (202) the location management node information of the first location management node comprises: sending (314), to the access and mobility management node, a second indication for indicating that the first user plane connection to be established between the first terminal device and the first location management node is to replace a second user plane connection between the first terminal device and the second location management node.

[0375] Clause 7. The method according to any of clauses 4 to 6, wherein sending (204) the location management node information of the first location management node to the first terminal device comprises:

[0376] sending (212), to the access and mobility management node, user plane information of the first user plane connection, wherein the user plane information of the first user plane connection comprises the location management node information of the first location management node.

[0377] Clause 8. The method according to any of clauses 1 to 7, wherein the location management node information of a location management node comprises:

[0378] a location management node identifier, ID, of the location management node.

[0379] Clause 9. The method according to clause 8, wherein the location management node ID of the location management node comprises one or more of:

[0380] a network address of the location management node; and

[0381] a fully qualified domain name, FQDN, of the location management node.

[0382] Clause 10. The method according to any of clauses 2 to 9, wherein the first message is a User Plane Connection Establishment Command message.

[0383] Clause 11. The method according to any of clauses 1 to 10, wherein the first location management node implements a location management function, LMF; and / or

[0384] wherein the access and mobility management node implements an access and mobility management function, AMF.Clause 12. A method at an access and mobility management node, the method comprising:

[0385] obtaining (402) location management node information of the first location management node, wherein location management node information of a location management node is for establishing a user plane connection between a terminal device and the location management node; and

[0386] sending (404) the location management node information of the first location management node to a first terminal device.

[0387] Clause 13. The method according to clause 12, wherein the location management node information of the first location management node is sent in user plane information of a first user plane connection to be established between the first terminal device and the first location management node; and / or

[0388] wherein the location management node information of the first location management node is sent in a downlink, DL, non-access stratum, NAS, Transport message.

[0389] Clause 14. The method according to clause 13, wherein the location management node information of the first location management node is separate from the user plane information of the first user plane connection.

[0390] Clause 15. The method according to any of clauses 12 to 14, wherein obtaining (402) the location management node information of the first location management node comprises:

[0391] receiving (506), from the first location management node, the location management node information of the first location management node.

[0392] Clause 16. The method according to any of clauses 12 to 14, wherein obtaining (402) the location management node information of the first location management node comprises:

[0393] determining (510) the location management node information of the first location management node.Clause 17. The method according to clause 16, further comprising:

[0394] sending (512), to the first location management node, the location management node information of the first location management node.

[0395] Clause 18. The method according to clause 16 or 17, wherein the first location management node is a location management node that initially triggers establishment of user plane connection; and

[0396] wherein the method further comprises: receiving (508), from the first location management node, a first indication for indicating that a new user plane connection is to be established.

[0397] Clause 19. The method according to clause 16 or 17, wherein the first location management node is a target location management node in location management node relocation, wherein a source location management node in the location management node relocation is a second location management node; and

[0398] wherein the method further comprises: receiving (516), from the first location management node, a second indication for indicating that the first user plane connection to be established between the first terminal device and the first location management node is to replace a second user plane connection between the first terminal device and the second location management node.

[0399] Clause 20. The method according to any of clauses 17 to 19, further comprising:

[0400] receiving (514), from the first location management node, user plane information of a first user plane connection to be established between the first terminal device and the first location management node, wherein the user plane information of the first user plane connection comprises the location management node information of the first location management node.

[0401] Clause 21. The method according to any of clauses 12 to 20, wherein the location management node information of a location management node comprises:

[0402] a location management node identifier, ID, of the location management node.Clause 22. The method according to clause 21, wherein the location management node ID of the location management node comprises one or more of:

[0403] a network address of the location management node; and

[0404] a fully qualified domain name, FQDN, of the location management node. Clause 23. The method according to any of clauses 12 to 22, wherein the first location management node implements a location management function, LMF; and / or

[0405] wherein the access and mobility management node implements an access and mobility management function, AMF.

[0406] Clause 24. A method at a first terminal device, the method comprising:

[0407] receiving (602), from a network node, location management node information of a first location management node, wherein location management node information of a location management node is for establishing a user plane connection between a terminal device and the location management node; and

[0408] establishing (604) a first user plane connection between the first terminal device and the first location management node based on the location management node information of the first location management node.

[0409] Clause 25. The method according to clause 24, wherein the network node is one of:

[0410] the first location management node; and

[0411] an access and mobility management node.

[0412] Clause 26. The method according to clause 24 or 25, wherein the location management node information of a location management node comprises:

[0413] a location management node identifier, ID, of the location management node.

[0414] Clause 27. The method according to clause 26, wherein the location management node ID of the location management node comprises one or more of:a network address of the location management node; and a fully qualified domain name, FQDN, of the location management node. Clause 28. The method according to any of clauses 24 to 27, wherein the first location management node implements a location management function, LMF; and / or wherein the access and mobility management node implements an access and mobility management function, AMF.

[0415] Clause 29. A first location management node (1000) comprising processing circuitry (1010) and a memory (1020), the processing circuitry (1010) being configured to:

[0416] obtain location management node information of the first location management node, wherein location management node information of a location management node is for establishing mapping a user plane connection between a terminal device and the location management node; and

[0417] send the location management node information of the first location management node to a first terminal device.

[0418] Clause 30. The first location management node (1000) according to clause 29, wherein the processing circuitry (1010) is configured to perform the method according to any of clauses 2 to 11.

[0419] Clause 31. An access and mobility management node (1000) comprising processing circuitry (1010) and a memory (1020), the processing circuitry (1010) being configured to:

[0420] obtain location management node information of the first location management node, wherein location management node information of a location management node is for establishing a user plane connection between a terminal device and the location management node; and

[0421] send the location management node information of the first location management node to a first terminal device.Clause 32. The access and mobility management node (1000) according to clause 31, wherein the processing circuitry (1010) is configured to perform the method according to any of clauses 13 to 23.

[0422] Clause 33. A first terminal device (1000) comprising processing circuitry (1010) and a memory (1020), the processing circuitry (1010) being configured to:

[0423] receive, from a network node, location management node information of a first location management node, wherein location management node information of a location management node is for establishing a user plane connection between a terminal device and the location management node; and

[0424] establish a first user plane connection between the first terminal device and the first location management node based on the location management node information of the first location management node.

[0425] Clause 34. The first terminal device (1000) according to clause 33, wherein the processing circuitry (1010) is configured to perform the method according to any of clauses 25 to 28.

[0426] Clause 35. A computer program comprising instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method according to any of clauses 1 to 28.

[0427] Clause 36. A computer program product comprising instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method according to any of clauses 1 to 28.

[0428] Clause 37. A computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method according to any of clauses 1 to 28.

[0429] Clause 38. A carrier containing the computer program according to clause 35, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer-readable medium.

[0199] While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

[0430]

[0200] References in the present disclosure to “one embodiment”, “an embodiment” and so on, indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0431]

[0201] It should be understood that, although the terms “first”, “second” and so on may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of the disclosure. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed terms.

[0432]

[0202] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the present disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and / or “including”, when used herein, specify the presence of stated features, elements, and / or components, but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof. The terms “connect”, “connects”, “connecting” and / or “connected” used herein cover the direct and / or indirect connection between two elements. It should be noted that two blocks shown in succession in the above figures may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.

[0203] The present disclosure includes any novel feature or combination of features disclosed herein either explicitly or any generalization thereof. Various modifications and adaptations to the foregoing exemplary embodiments of this disclosure may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings. However, any and all modifications will still fall within the scope of the non-Limiting and exemplary embodiments of this disclosure.

[0433]

[0204] Numerous modifications and variations of the present disclosure are possible in light of the above teachings. It is therefore to be understood that within the scope of the appended claims, the disclosure may be practised otherwise than as specifically described herein.

Claims

Claims:

1. A method for execution by a first network node, comprising:enabling a first user plane connection for a communication device to a first location management node; andenabling a second user plane connection for the communication device to a second location management node;wherein the first user plane connection and the second user plane connection co-exist in time.

2. The method of claim 1 , further comprising:upon an event triggering movement of the first user plane connection or the second user plane connection, sending source user plane information of a source location management node to a target location management node involved in the movement, such that the source user plane information of the source location management node can identify which user plane connection is to be moved;wherein the source location management node is the first location management node when the first user plane connection is being moved or the second location management node when the second user plane connection is being moved.

3. The method of claim 1 or claim 2, wherein the first network node comprises an AMF (Access and Mobility Management Function) node, the communication device comprises a UE (User Equipment), the first location management node comprises a first LMF (Location Management Function) node, and the second location management node comprises a second LMF node, and the target location management node comprises a third LMF node.

4. A non-transitory computer readable medium having recorded thereon statements and instructions that, when executed by a processor of a first network node, configure the first network node to implement a method according to any one of claims 1 to 3.

5. A first network node, comprising:a network interface configured to communicate with other network nodes;control circuitry coupled to the network interface and configured to:enable a first user plane connection for a communication device to a first location management node; andenable a second user plane connection for the communication device to a second location management node;wherein the first user plane connection and the second user plane connection co-exist in time.

6. The first network node of claim 5, wherein the control circuitry is further configured to implement a method according to claim 2 or claim 3.

7. A method for execution by a target location management node, comprising:receiving, from a first network node, source user plane information of a source location management node;identifying, based on the source user plane information of the source location management node, a user plane connection for a communication device that is to be moved;facilitating movement of the user plane connection including sending to the communication device an indication of the user plane connection of the source location management node and the target location management node.

8. The method of claim 7, wherein sending the indication comprises sending the indication via a user plane connection establishment command message whichtriggers the communication device to establish a new user plane connection towards the target location management node.

9. The method of claim 7 or claim 8, wherein the target location management node comprises a target LMF (Location Management Function) node, the first network node comprises an AMF (Access and Mobility Management Function) node, and the communication device comprises a UE (User Equipment).

10. A non-transitory computer readable medium having recorded thereon statements and instructions that, when executed by a processor of a target location management node, configure the target location management node to implement a method according to any one of claims 7 to 9.

11. A target location management node, comprising:a network interface configured to communicate with other network nodes;control circuitry coupled to the network interface and configured to:receive, from a first network node via the network interface, source user plane information of a source location management node;identify, based on the source user plane information of the source location management node, a user plane connection for a communication device that is to be moved;facilitate movement of the user plane connection including sending, to the communication device via the network interface, an indication of the user plane connection of the source location management node and the target location management node.

12. The target location management node of claim 11, wherein the control circuitry is further configured to implement a method according to claim 8 or claim 9.

13. A method for execution by a communication device, comprising:establishing a first user plane connection with a first location management node; andestablishing a second user plane connection with a second location management node;receiving an indication that the second user plane connection is to be moved from the second location management node to a target location management node; andhalting communication with the second location management node and instead moving the second user plane connection to a new user plane connection involving the target location management node.

14. The method of claim 13, wherein receiving the indication comprises receiving the indication via a user plane connection establishment command message which triggers the communication device to establish the new user plane connection towards the target location management node.

15. The method of claim 13 or claim 14, wherein the communication device comprises a UE (User Equipment), the first location management node comprises a first LMF (Location Management Function) node, the second location management node comprises a second LMF node, and the target location management node comprises a target LMF node.

16. A non-transitory computer readable medium having recorded thereon statements and instructions that, when executed by a processor of a communication device, configure the communication device to implement a method according to claim 13 or claim 14.

17. A communication device, comprising:a wireless access radio configured to communicate with a wireless network;control circuitry coupled to the wireless access radio and configured to: establish a first user plane connection with a first location management node; andestablish a second user plane connection with a second location management node;receive an indication that the second user plane connection is to be moved from the second location management node to a target location management node; andhalt communication with the second location management node and instead move the second user plane connection to a new user plane connection involving the target location management node.

18. The communication device of claim 17, wherein the control circuitry is further configured to implement a method according to claim 14 or claim 15.

Images