Location service enhancements based on use of user plane interfaces with terminal devices

By introducing the interaction between LCUP function and LMF in the 5G LCS architecture, the problems of high signaling load and insufficient security in user plane positioning are solved, efficient and secure user plane positioning services are realized, and mobile location request processing capabilities are improved.

CN118985152AActive Publication Date: 2024-11-19ALCATEL LUCENT SHANGHAI BELL CO LTD +1
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202280094389.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-03-28
Publication Date
2024-11-19
Estimated Expiration
2042-03-28

AI Technical Summary

Technical Problem

The existing 5G LCS architecture has problems such as excessive signaling load, low efficiency in handling mobile origin location requests and insufficient security in terms of user plane positioning. Especially in the changes in user plane interface architecture between UE and the network, it is difficult to be effective. Supports moving origin and terminating position requests and delayed position requests.

Method used

By introducing the interaction between the location management function (LMF) and the user plane location service (LCUP) function in terminal devices and network systems, using LCUP auxiliary information to establish a secure user plane connection, and enhancing user plane interaction in control plane positioning protocol signaling , supports hybrid interactive modes to improve positioning operation efficiency and safety.

Benefits of technology

It effectively reduces the signaling load introduced by the control plane positioning process, improves the efficiency and security of user plane positioning, supports efficient processing of mobile origin and termination position requests, and enhances the user plane capabilities of the 5G LCS architecture.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118985152A_ABST
    Figure CN118985152A_ABST
Patent Text Reader

Abstract

The embodiment of the invention relates to equipment, a method and a device for enhancing location service based on the use of a user plane interface with terminal equipment, and a computer readable storage medium. According to the embodiment of the invention, terminal equipment can receive location service user plane (LCUP) auxiliary information in control plane (CP) positioning protocol signaling, wherein the LCUP auxiliary information comprises at least one of addressing information of an LCUP function instance, correlation information of an ongoing CP positioning process, and security information for establishing a user plane (UP) session between the terminal device and the LCUP function instance, and the LCUP function instance is associated with a location management function (LMF) selected for serving the terminal device; and establishing a secure UP connection between the terminal device and the LCUP function instance by using the LCUP auxiliary information, so as to perform the UP positioning operation by using the LCUP function instance.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of telecommunications, and in particular to devices, methods, apparatuses, and computer-readable media for location service enhancement based on using a user plane interface with a terminal device. Background Art

[0002] Some communication systems such as New Radio (NR) support location services. Location services can be provided through control plane protocols such as the LTE positioning protocol. In addition, user plane positioning is proposed as a location service enhancement solution.

[0003] A key objective of the architecture enhancement is to identify the 3rd Generation Partnership Project (3GPP) Location Services (LCS) features and enhancements required to support user plane positioning. Summary of the invention

[0004] In general, example embodiments of the present disclosure provide devices, methods, apparatuses, and computer-readable media for location service enhancement based on user plane functions.

[0005] In a first aspect, a terminal device is provided. The terminal device includes at least one processor; and at least one memory including computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, enable the terminal device to: receive location service user plane (LCUP) auxiliary information in control plane (CP) positioning protocol signaling, wherein the LCUP auxiliary information includes at least one of the following items: addressing information of an LCUP function instance, correlation information of an ongoing CP positioning process, and security information for establishing a user plane (UP) session between the terminal device and the LCUP function instance, and wherein the LCUP function instance is associated with a location management function (LMF) selected for serving the terminal device; and establish a secure UP connection between the terminal device and the LCUP function instance by using the LCUP auxiliary information, so as to perform a UP positioning operation using the LCUP function instance.

[0006] In a second aspect, a network system is provided. The network system includes at least one processor; and at least one memory including computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, cause the network device to: in response to the initiation of a control plane (CP) positioning process, select a location management function (LMF) serving a terminal device; transmit location service user plane (LCUP) auxiliary information from the LMF in control plane (CP) positioning protocol signaling, wherein the LCUP auxiliary information includes at least one of the following items: addressing information of the LCUP function instance, correlation information of the ongoing CP positioning process, and security information for establishing a user plane (UP) session between the terminal device and the LCUP function instance, wherein the LCUP function instance is associated with the LMF selected to serve the terminal device; and use information provided by the terminal device from the LCUP auxiliary information to establish a secure UP connection between the terminal device and the LCUP function instance, so as to exchange positioning related information with the terminal device using the LCUP function instance.

[0007] In a third aspect, a network device is provided. The network device (e.g., LMF) includes at least one processor; and at least one memory including computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, enable the network system to: transmit location service user plane (LCUP) auxiliary information in control plane (CP) positioning protocol signaling, wherein the LCUP auxiliary information includes at least one of the following items: addressing information of the LCUP function instance, correlation information of the ongoing CP positioning process, and security information for establishing a user plane (UP) session between the terminal device and the LCUP function instance, and wherein the LCUP function instance is associated with the LMF selected for serving the terminal device.

[0008] In a fourth aspect, a method is provided. The method comprises: receiving location service user plane (LCUP) assistance information in control plane (CP) positioning protocol signaling, wherein the LCUP assistance information comprises at least one of the following items: addressing information of an LCUP function instance, correlation information of an ongoing CP positioning process, and security information for establishing a user plane (UP) session between a terminal device and the LCUP function instance, wherein the LCUP function instance is associated with a location management function (LMF) selected to serve the terminal device; and establishing a secure UP connection between the terminal device and the LCUP function instance by using the LCUP assistance information, so as to perform a positioning operation using the LCUP function instance.

[0009] In a fifth aspect, another method is provided. The method includes: in response to the initiation of a control plane (CP) positioning procedure, selecting a location management function (LMF) to serve a terminal device; transmitting location service user plane (LCUP) assistance information from the LMF in control plane (CP) positioning protocol signaling, wherein the LCUP assistance information includes at least one of the following items: addressing information of an LCUP function instance, correlation information of an ongoing CP positioning procedure, and security information for establishing a user plane (UP) session between the terminal device and the LCUP function instance, wherein the LCUP function instance is associated with the LMF selected to serve the terminal device; and using information provided by the terminal device from the LCUP assistance information, establishing a secure UP connection between the terminal device and the LCUP function instance so as to exchange positioning related information with the terminal device using the LCUP function instance.

[0010] In a sixth aspect, an apparatus is provided. The apparatus comprises: a component for receiving location service user plane (LCUP) assistance information in control plane (CP) positioning protocol signaling, wherein the LCUP assistance information comprises at least one of addressing information of an LCUP function instance, correlation information of an ongoing CP positioning process, and security information for establishing a user plane (UP) session between a terminal device and the LCUP function instance, wherein the LCUP function instance is associated with a location management function (LMF) selected for serving the terminal device; and establishing a secure UP connection between the terminal device and the LCUP function instance by using the LCUP assistance information, so as to perform a UP positioning operation using the LCUP function instance.

[0011] In a seventh aspect, another apparatus is provided. The apparatus comprises: a component for selecting a location management function (LMF) serving a terminal device in response to initiation of a control plane (CP) positioning procedure; a component for transmitting location service user plane (LCUP) assistance information from the LMF in control plane (CP) positioning protocol signaling, wherein the LCUP assistance information comprises at least one of the following items: addressing information of an LCUP function instance, correlation information of an ongoing CP positioning procedure, and security information for establishing a user plane (UP) session between the terminal device and the LCUP function instance, and wherein the LCUP function instance is associated with the LMF selected to serve the terminal device; and a component for establishing a secure UP connection between the terminal device and the LCUP function instance using information provided by the terminal device from the LCUP assistance information, so as to exchange positioning related information with the terminal device using the LCUP function instance.

[0012] In an eighth aspect, there is a computer-readable storage medium, which includes program instructions stored thereon. When a device executes the instructions, the instructions cause the device to perform the method according to the fourth, fifth or sixth aspect above.

[0013] It should be understood that the invention summary is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The above and other objects, features and advantages of the present disclosure will become more apparent through a more detailed description of some example embodiments of the present disclosure in the accompanying drawings, in which:

[0015] Figure 1 illustrates an example system in which example embodiments of the present disclosure may be implemented;

[0016] Figure 2 illustrates a flow chart of an example method according to some example embodiments of the present disclosure;

[0017] Figure 3 illustrates a flow chart of an example method according to some example embodiments of the present disclosure;

[0018] Figure 4 A signaling diagram illustrating an example process according to some example embodiments of the present disclosure;

[0019] Figure 5 illustrates a simplified block diagram of a device suitable for implementing embodiments of the present disclosure; and

[0020] Figure 6 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is illustrated.

[0021] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0022] The principle of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are only for illustrative purposes, and contribute to those skilled in the art to understand and implement the present disclosure, without implying any limitation on the scope of the present disclosure. The present disclosure described herein can be implemented in various ways except the way described below.

[0023] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0024] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an example embodiment, whether or not explicitly described, it should be understood that a person skilled in the art may affect the feature, structure, or characteristic in conjunction with other embodiments.

[0025] It should be understood that although the terms "first" and "second" etc. 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 element. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0026] The terms used herein are only used for the purpose of describing specific embodiments and are not intended to limit the exemplary embodiments. As used herein, unless the context clearly indicates otherwise, the singular forms "one", "an" and "the" also include plural forms. It should also be understood that the terms "including", "having" and / or "comprising" when used herein specify the existence of stated features, elements and / or components, etc., but do not exclude the existence or addition of one or more other features, elements, components and / or combinations thereof.

[0027] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0028] (a) pure hardware circuit implementation (such as implementation in analog and / or digital circuitry only) and

[0029] (b) a combination of hardware circuitry and software such as (where applicable):

[0030] (i) a combination of analog and / or digital hardware circuits and software / firmware, and

[0031] (ii) any portion of hardware processor(s) with software (including digital signal processor(s), software and memory(s) that work together to enable a device (such as a mobile phone or server) to perform various functions) and

[0032] (c) Hardware circuit(s) and / or processor(s) that require software (e.g., firmware) to operate, such as microprocessor(s) or portion(s) of microprocessor(s), but where the software is not required for operation, the software may not be present.

[0033] This definition of circuitry applies to all uses of the term herein, including in any claims. As a further example, as used in this application, the term "circuitry" also covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. By way of example and where applicable to a particular claim element, the term "circuitry" also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0034] As used herein, the term "communication network" refers to a network that complies with any appropriate communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrow Band Internet of Things (NB-IoT), New Radio (NR), etc. In addition, in the communication network, communication between user equipment (UE) and network devices or communication between network devices can be performed according to any appropriate communication protocol, including but not limited to first generation (1G), 2G, 3G, 4G, 5G, 6G, 7G, 8G, 9G, 10G, 11G, 12G, 13G, 14G, 15G, 16G, 17G, 18G, 19G, 20G, 21G, 22G, 23G, 24G, 25G, 26G, 27G, 28G, 29G, 30G, 31G, 32G, 33G, 34G, 36G, 37G, 38G, 39G, 40G, 41G, 42G, 43G, 44G, 45G, 46G, 47G, 48G, 49G, 50G, 51G, 52G, 53G, 54G, 55G, 56G, 57G, 58G, 59G, 60G, 61G, 62G, 63G, 64G, 65G, 66G, 67G, 68G, 79G, 80G, 81G, 81G st Generation, 1G), second generation (2 nd Generation, 2G), 2.5G, 2.75G, third generation (3 rd Generation, 3G), fourth generation (4 th Generation, 4G), 4.5G, fifth generation (5 th Generation (5G) communication protocols and / or any other currently known or future developed protocols, such as the future sixth generation (6 th The embodiments of the present disclosure may be applied to various communication systems. In view of the rapid development of communications, there will certainly be future types of communication technologies and systems that can embody the present disclosure. It should not be construed as limiting the scope of the present disclosure to only the above-mentioned systems.

[0035] As used herein, the term "network device" refers to a node in a communication network, and a UE has the node to access the network and receive services from it. A network device may refer to a base station (BS) or an access point (AP), such as a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low-power node (such as femto, pico, etc.), depending on the terminology and technology applied. In the following description, the terms "network device", "BS" and "node" can be used interchangeably.

[0036] The term "UE" refers to any terminal device capable of wireless communication. As an example and not limitation, UE may also be referred to as a communication device, terminal device, subscriber station (SS), portable subscriber station, mobile station (MS) or access terminal (AT). UE may include, but is not limited to, mobile phones, cellular phones, smart phones, Voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, Personal Digital Assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), game terminal devices, music storage and playback devices, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), Universal Serial Bus (USB) dongles, smart devices, wireless Customer Premises Equipment (CPE), Internet of Things (IoT) devices, watches or other wearable devices, Head Mounted Display (HMD), vehicles, drones, medical devices and applications (such as remote surgery), UE-type riding side units (RodeSide Unit, RSU), industrial equipment and applications (such as robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronic devices, devices operating in commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" can be used interchangeably. Some communication systems such as New Radio (NR) support location services. Location services can be provided through control plane protocols such as LTE positioning protocols. In addition, user plane positioning is also proposed as a location service enhancement solution. Therefore, architectural enhancements are required to support user plane positioning.

[0037] The term "network element" refers to a unit, function or device in a network system. For a 3GPP 5G system, the network may include, for example, an access network (AN), a radio access network (RAN), a next generation RAN (NG-RAN), an access and mobility management function (AMF), a session management function (SMF) 106, a user plane function (UPF), a location management function (LMF), a location service user plane (LCUP) function (a new unit proposed in the present disclosure), a unified data management (UDM) function, a network exposure function (NEF) and other network functions (NF) in the core network.

[0038] User plane positioning has been proposed as a location service enhancement solution. The key goal of the architectural enhancement is to identify the 3GPP Location Service (LCS) features and enhancements required to improve positioning using the user plane interface between the UE and the network, for example to reduce the signaling load introduced by the positioning process initiated by the CP. It aims to address architectural changes that allow the use of the user plane interface between the UE and the network, including central deployment or edge deployment, e.g.

[0039] - Discovery of user plane capabilities to be used for communications between the UE and the user plane location interface termination, and configuration and selection of PDU sessions (if required).

[0040] - Whether and how the existing 5GS LCS architecture or related procedures should be enhanced to support Mobile Originating Location Request (MO-LR), Mobile Terminal-Location Request (MT-LR), deferred MT-LR and regulatory related positioning procedures (when user plane positioning is involved).

[0041] -Interaction with legacy LCS call flow and security aspects

[0042] - Requirements on the delivery protocol, for example if reliable delivery and in-order delivery are required.

[0043] -Interaction between user plane and existing control plane solutions (if any).

[0044] - User plane as a possible enhancement of the control plane.

[0045] Embodiments of the present disclosure are directed to enhancements of user plane discovery and control plane enhancements. Discovery of the user plane location interface termination is the process by which the UE discovers the (multiple) (Internet Protocol) IP addresses of a suitable user plane server (or Service Location Protocol (SLP) in Open Mobile Alliance (OMA) terminology) using the Domain Name System (DNS).

[0046] 3GPP TS23.273 defines the current LCS architecture which involves the LMF (Location Management Function), which is the entity responsible for performing the necessary calculations to determine the UE location. For the purpose of UE location, it needs to obtain measurements from the New Generation (NG) Radio Access Network (RAN) and the UE.

[0047] According to Section 4.3.1 of 3GPP TS 38.305, the standard User Plane (UP) from OMA, Secure User Plane Location (SUPL) only supports some positioning methods, as shown in Table 1:

[0048] Table 1 Positioning methods or protocols supported by SUPL

[0049]

[0050]

[0051] In the above table, a variety of positioning methods or protocols are given, where A-GNSS indicates a positioning method based on assisted global navigation satellite system; OTDOA indicates a positioning method based on observed time difference of arrival; E-CID indicates enhanced cell ID; sensor indicates a positioning method based on sensor; WLAN indicates a positioning method based on wireless local area network; Bluetooth indicates a positioning method based on Bluetooth; DL-TDOA indicates a positioning method based on downlink time difference of arrival; DL-AoD indicates a positioning method based on downlink departure angle; Multi-RTT indicates a positioning method based on multi-cell round trip time; UL-TDOA indicates a positioning method based on uplink time difference of arrival; and UL-AoA indicates a positioning method based on uplink arrival angle. As can be seen from the above table, SUPL can only provide partial measurements for the Multi-RTT method.

[0052] For user plane LCS, the SLP instance is defined by the Open Mobile Alliance (OMA) SLP FQDN specification, which can be referenced as follows

[0053] - For emergency, it is in section 6.1.5.1 in OMA-TS-ULP-V2_0_6-20200804-A (Industry vendors mostly follow this approved specification)

[0054] - For non-emergency situations, it is not well defined in the approved OMA specs, but the candidate spec for 3.0 has section 6.4 of OMA-TS-ULP-V3_0-20181213-C

[0055] Both methods mentioned above use H-SLP (non-emergency) or E-SLP (emergency) FQDN to locate the SLP server.

[0056] The embodiments of the present disclosure propose a hypothetical architecture in which the LMF can use a mixture of CP (control plane) and UP (user plane) interactions for a single LCS request. The LMF uses CP interaction to interact with, for example, the NG RAN or the UE, for example, to request the NG RAN to send a signal to the UE or to measure some signals from the UE, and after a short CP interaction with the UE, uses UP interaction with the UE to request the UE to send a signal to the NG RAN or to report measurements of some signals from the NG RAN.

[0057] Embodiments of the present disclosure aim to provide enhancements to the legacy 3GPP Control Plane (CP) specifications to integrate UP communications between the UE and LCS functionality in the network.

[0058] Example Environment

[0059] Figure 1An example system 100 of the present disclosure is shown in which example embodiments may be implemented. Figure 1 As illustrated in , system 100 includes a terminal device, such as user equipment (UE) 101. UE 101 is an example of a terminal device, but the present disclosure is not limited thereto; rather, it may be any type of terminal device, such as a vehicle, etc., and system 100 may include any number of UEs.

[0060] The UE 101 is communicatively connected to an access network or radio access network RAN ​​102. The RAN 102 may be, for example, a Next Generation Radio Access Network (NG-RAN), which is an access network of a 3GPP 5G system.

[0061] UE 101 is also communicatively connected to access and mobility management function (AMF) 105. AMF 105 is the portal for RAN 102 to access the core network of the 3GPP 5G system. AMF can provide access control and mobility management functions and communicate with other network elements in the core network through the Nanf interface. AMF 105 is also communicatively connected to RAN 102 through interface N2.

[0062] RAN 102 is also communicatively connected to user plane function UPF 103 through N3 interface. As an important unit in the core network of 3GPP 5G system, user plane function (UPF) 103 is responsible for packet routing and forwarding on the user plane. UPF 102 is communicatively connected to session management function (SMF) 106 and data network (DN) 104 through N4 and N6 interfaces.

[0063] SMF 105 is a network element for session management in the core network, and is specifically responsible for user plane interaction with UPF 103, creating, updating, deleting sessions, and managing session contexts. At the same time, SMF 105 can communicate with other network elements through Nsmf.

[0064] DN 104 is a network used to provide network data services to UE, which may be, for example, an operator network, the Internet, a third-party service network, etc.

[0065] Location Management Function (LMF1) 107a and LMF2 107b are two location management functions on the control plane in the core network. They coordinate and schedule the resources required to manage the UE location and provide location and velocity calculation and verification. LMF1 107a and LMF2 107b can receive a location request for the UE or a location request from the AMF through the Nlmf interface, communicate with the UE on the control plane to exchange location information suitable for UE-assisted or UE-based positioning methods, and interact with other network elements such as NG-RAN, non-3GPP interworking functions to obtain location information.

[0066] Specifically, embodiments of the present disclosure propose to arrange one or more associated or matched LCS user plane (LCUP) functions for LMF; for example, LMF1 107a can be associated with LCUP1-0 108a and LCUP1-1 108c, and LMF2 107b can be associated with LCUP2 108b. The term "LCUP" used herein means a network element or network function for location services on the user plane, which can correspond to the user plane part of LMF or the OMA specification defined by the SUPL location platform, for example.

[0067] The LCUP function handles location operations on the user plane and can be used with the associated LMF, for example, to enhance location services on the control plane. The LMF and the associated LCUP can be located in the same area, for example, co-located with each other, or can communicate via an interface or implement specific behaviors. Additionally or alternatively, the LMF and the associated LCUP can also support similar positioning methods so that they can match each other. However, the embodiments of the present disclosure are not limited to this; it is also possible to associate with each other based on other factors. In addition, it should be noted that LMF1 107a and LMF2 107b are given only for illustrative purposes, and the system 100 may include a larger number of LMFs. In addition, the LMF can be associated with one LCUP and can be associated with multiple LCUPs. Alternatively, the LCUP can also be associated with more than one LMF, depending on the specific system implementation. In addition, each LCUP can be communicatively connected to the DN 104.

[0068] The system 100 also includes a Network Repository Function (NRF) 109, which acts as a centralized repository for all network functions (NFs) in the operator's network and provides records of all NFs and their configuration files and supported services.

[0069] The unified data management (UDM) function 111 provides data management of network user data in a centralized manner, especially managing data for access authorization, user registration and data network profiles. UDM provides services to AMF, SMF and other NFs through Nudm, such as the network open function (NEF), which is located between the 5G core network and external third-party application functions and is responsible for managing external open network data, and all external applications that want to access 5G core internal data must go through NEF.

[0070] The Edge Application Server Discovery Function (EASDF) 112 acts as a Domain Name System (DNS) resolver for the UE and can supplement DNS queries with information related to the UE location, which enables the DNS system to resolve to an application server close to the UE location. The EASDF can communicate with other NFs through the Neasdf interface.

[0071] In addition, the system also includes other NFs, such as NEF, Policy Charging Function (PCF), Application Function (AF), etc., and they can communicate with other network elements in the core network through their corresponding interfaces. It should be noted that these other NFs are not included in the core network for the purpose of simplicity. Figure 1 Described in.

[0072] Example embodiments of the present disclosure relate to user plane communication between a UE located by LMF 107a, 107b and LMF 107a, 107b, the communication being carried out via a LCUP entity determined by the LMF in order to enhance CP positioning. One of the objects of the present disclosure is to enable a UE to contact a LCUP via a UP, the LCUP corresponding to a user plane terminal of the LMF serving the terminal device.

[0073] To this end, the embodiments of the present disclosure propose to provide LCUP instance assistance information from the network to the UE so that a secure UP connection is established between the UE and the appropriate LCUP. In this way, UP interaction can be performed between the UE and the appropriate LUCP to enhance the corresponding CP positioning process.

[0074] The embodiments of the present disclosure may be Figure 1 ; however, it should be understood that Figure 1 It is illustrated only for the purpose of illustration and does not imply any limitation on the scope of protection. On the contrary, the embodiments of the present disclosure can be implemented in other communication systems with similar CP location service enhancement requirements.

[0075] The following will refer to Figures 2 to 6 Some example embodiments are described in detail.

[0076] Example Method

[0077] Figure 2 A flow chart of an example method 200 for location service enhancement based on user plane functionality according to some example embodiments of the present disclosure is illustrated. The method may be performed at a terminal device (such as a UE) or any other terminal device having a CP location service enhancement requirement.

[0078] Method 200 can be initiated after the user plane participates in a CP positioning process (e.g., the MT-LR process, the MO-LR process, or the NI-LR process defined by 3GPP). In addition, the UP interface between the UE and the LMF can be direct or indirect (i.e., supporting the proxy mode or the non-proxy mode defined by the OMA SUPL specification). As mentioned, in response to the location request, the AMF can select the LMF instance as the serving LMF for the terminal device and use the Nlmf_Location_DetermineLocation message to request the LMF to perform a positioning operation. The LMF can have an associated LCUP for positioning operations, but it should ensure that the terminal can connect to the associated LCUP on the UP. Therefore, method 200 can be implemented as follows.

[0079] like Figure 2 As illustrated in FIG. 2 , at block 210, the terminal device may receive location service user plane (LCUP) assistance information in control plane (CP) positioning protocol signaling (e.g., LTE positioning protocol (LPP) signaling) from the network. The LCUP assistance information contains information for assisting the establishment of a UP connection between the UE and the LCUP. The LCUP assistance information may include at least one of the following items: addressing information of an LCUP function instance, correlation information of an ongoing CP positioning procedure, and security information for establishing a user plane (UP) session between the terminal device and the LCUP function instance. In particular, the LCUP function instance is associated with a location management function (LMF) selected for serving the terminal device.

[0080] LCUP auxiliary information can be received in a variety of different ways. In some example embodiments of the present disclosure, the LCUP auxiliary information can be included in a capability request / indication message. The capability / indication request message is transmitted by the network (e.g., LMF) to indicate that the network supports user plane functions for positioning purposes to require the UE to report its capabilities. The capability / indication request message may include LCUP auxiliary information. In response to receiving the capability indication message, the terminal device may send a capability indication response message to the network to indicate that the terminal device supports user plane functions for positioning purposes. In addition, the terminal may spontaneously send LPP signaling to indicate that the terminal device also supports user plane functions for positioning purposes.

[0081] In some embodiments of the present disclosure, the LCUP assistance information may be included in the assistance provision message. In some embodiments of the present disclosure, the assistance provision message may be transmitted from the network (e.g., LMF) as a response to an assistance request message; the assistance request message is transmitted from the terminal device to inquire the network for positioning assistance data. In some embodiments of the present disclosure, the assistance provision message may also be transmitted from the network spontaneously, rather than in response to a request from the terminal device.

[0082] When the UE's Request Assistance LPP message has been sent as a payload in the Nlmf_Location_DeterminLocation request from the AMF, the LCUP assistance information can be provided in the reply Provide Assistance LPP message to be sent to the terminal device via the AMF and NG RAN.

[0083] In some embodiments of the present disclosure, the LCUP auxiliary information includes addressing information of the LCUP function instance. As mentioned above, when LCUP is used for the LCS process, it is necessary to ensure that the LCUP to be used by the UE can match the LMF already selected by the AMF. To this end, the addressing information can be provided, for example, by the LMF and used by the terminal device to contact the LCUP to establish a UP connection with the LCUP.

[0084] In some example embodiments of the present disclosure, the addressing information may be, for example, a fully qualified domain name (FQDN) specific to a LCUP function instance. This means that there are different FQDNs for different LUCP function instances. For example, the FQDN may uniquely identify a LUCP function instance.

[0085] In some embodiments of the present application, the standard defined FQDN range (such as *.LMF.5gc.mnc <mnc>.mcc <mcc>.3gppnetwork.org) can be used as the FQDN to reach the <mcc> ., <mnc>) in any LCUP in the PLMN defined in the FQDN. The wildcard parameter "*" in the FQDN can have different values ​​for different LCUP instances. For example, for an LCUP instance, the FQDN can be Beijing3.LMF.5gc.mnc <mnc>.mcc <mcc>.3gppnetwork.org; for another LCUP instance, it could be Shanghai2.LMF.5gc.mnc <mnc>.mcc <mcc>.3gppnetwork.org.

[0086] This specific FQDN can be used with URSP rules to ensure that the device uses the PDU session to go to the correct DNN (Data Network Name) and network slice S-NSSAI to reach the LUCP associated with the LMF selected by the AMF.

[0087] In some embodiments of the present disclosure, when LCUP is deployed in a network, an operations administration and maintenance (OAM) instance associated with the management of location capabilities in the network (e.g., acting as an AF) can provide guidance to the PCF for the setting of USRP rules for terminal devices (e.g., UE defined in Section 6.6 of TS23.548). The PCF instance can use this guidance to set up USRP rules. USRP rules can map the FQDNs of different LCUP instances to appropriate data networks and slices identified by the relevant data network names DNN and single network slice selection assistance information (S-NSSAI). In addition, the AF can further configure EAS deployment information (EDI) related to the LCUP instance via the process defined in Section 6.2.3.4 of 3GPP 23.548. EDI can be used for the following IP address query operations as described in 3GPP TS23.548.

[0088] The PCF (e.g. in the Home Public Land Mobile Network (HPLMN)) may then send the URSP rules to the UE. Thus, through the URSP rules, the UE is enabled to select the appropriate dnn+slice (and therefore the appropriate PDU session) to reach the LCUP in the HPLMN, and in each visited public land mobile network (VPLMN) with which the HPLMN has a roaming agreement. With the help of the URSP rules, the terminal device may map the FQDN ranges defined in the above standards to the relevant dnn+slices for use in the serving PLMN for UP communications between the UE and the LCUP. For roaming scenarios, the VPLMN will provide the HPLMN with appropriate dnn+slices as part of the roaming agreement. In this roaming case, this PDU session operates in LBO local breakout mode. The URSP rules may be sent to the UE using the existing PCF interface, and therefore there is no need to modify the URSP structure.

[0089] In some embodiments of the present disclosure, the LCUP instance auxiliary information may alternatively or additionally include: security information for establishing a user plane (UP) session between a terminal device and an LCUP function instance. The security information may include security materials that the UE can use to establish a user plane session between the UE and the LCUP. In some embodiments of the present disclosure, the security information may include transport layer security (TLS) attribute information for establishing a secure UP connection. The TLS attribute information may, for example, correspond to a key that is used as a pre-shared key to protect the TLS link between the UE and the LCUP. It can be used to establish an SSL / TLS connection between the UE and the LCUP. In some embodiments, for example, when the UE wants to start a session via a SUPL position initialization (POS INIT) message to initiate a positioning protocol session, the security information may also include a hash-based message authentication code field. However, if the UE starts a session via a SUPL START message as an initial message, such a field is not required.

[0090] In some embodiments of the present disclosure, the LCUP instance assistance information may alternatively or additionally include correlation information about the ongoing CP positioning process. The correlation information contains information used to correlate the ongoing CP positioning process with the UP connection to further ensure the security of the UP connection. A network unit such as an LMF may assign a correlation identifier as correlation information to a positioning request, which may include, for example, an LMF address and a positioning request identifier. The LMF may provide the correlation identifier to the terminal device as part of the LCUP assistance information on the CP, for example, via LPP signaling. In subsequent operations to establish a UP connection between the terminal device and the LUCP, the correlation identifier may be used to correlate the ongoing CP positioning process with the UP connection, which will be described below.

[0091] The LCUP assistance information also contains information about the port of the LCUP function instance, such as the TCP or UDP port of the LCUP. Additionally or alternatively, the LCUP assistance information may also include information about the positioning method or protocol supported by the LCUP function instance, such as those given in Table 1. With the help of this information, a secure UP connection can be established, as described with reference to block 220.

[0092] right Figure 2 For reference, in 220, the terminal device establishes a secure UP connection between the terminal device and the LCUP function instance by using the LCUP auxiliary information, so as to perform a positioning operation using the LCUP function instance.

[0093] In some embodiments of the present disclosure, the terminal device may establish a secure connection with the LCUP instance by using at least one of the correlation information and the security information received in the LCUP assistance information, wherein the correlation information is used to identify the corresponding ongoing positioning process associated with the secure connection. The LMF maps the LCS request of the UE with the UP data path of the UE via LCUP. Therefore, the LCS operation may be performed using LCUP for communication between the LMF and the UE.

[0094] In the case where the security information includes transport layer security attribute information for establishing a secure UP connection, the terminal device may use such security information to establish an SSL / TLS connection between the UE and the LCUP. The transport layer security attribute information may, for example, correspond to a key that is used as a pre-shared key to protect the TLS link between the UE and the LCUP. In the case where the security information includes a hash-based message authentication code field, the terminal device may use this authentication code field during establishment of the UP connection in order to initiate a positioning protocol session by sending a SUPL Position Initialization (POSINIT) message. However, as noted above, if the UE initiates a session via a SUPL START message as the initial message, such a field is not required.

[0095] In some embodiments of the present disclosure, the IP address of the LUCP may be obtained through a DNS query. For example, the terminal device may transmit a domain name server (DNS) request to convert the FQDN of the LCUP function instance into one or more IP addresses used to reach the LCUP.

[0096] In some embodiments of the present disclosure, at least one IP address of the LCUP functional instance may be obtained through a protocol data unit (PDU) session selected or established based on the FQDN of the UP instance and a UE routing selection policy (URSP) rule containing information about routing rules related to different FQDN ranges. It should be noted that the terminal device may receive more than one IP address, and the terminal device may randomly use one of them to establish a UP connection, or use the address selection rule carried in the DNS reply.

[0097] To implement the DNS query, the terminal device may select or establish a protocol data unit (PDU) session based on the FQDN of the UP instance and a UE routing selection policy (URSP) rule containing routing rule information related to different FQDN ranges to communicate with the LCUP function instance. For example, a PDU session may be selected or established by mapping an FQDN range corresponding to the FQDN of the LCUP function instance to a data network name and a network slice based on the URSP rule.

[0098] In some embodiments of the present application, on the network side, an edge application server discovery function (EASDF) can be determined for a PDU session, and a domain name server message processing rule can be configured for it based on the EASDF deployment information associated with the FQDN range (which is associated with the LCUP). If the SMF has been configured to use EASDF for PDU sessions (for dnn+ slicing), the SMF will select, insert and control the EASDF (as defined in Section 6.2 of 3GPP TS23.548). The SMF can configure the EASDF for the session with a DNS message processing rule that refers to the EDI configured by the AF, which is consistent with the standard defined FQDN range (*.LMF.5gc.mncMNC>.mcc <mcc>.3gppnetwork.org) to trigger the offloading of related services.

[0099] In some embodiments of the present disclosure, there is no suitable ongoing PDU session between the terminal device and the network, and the terminal device can transmit a PDU session establishment request to the network to determine the PDU session parameters using the fully qualified domain name (FQDN) of the UP instance and the UE routing policy (URSP) to establish the PDU session. For example, the terminal device can attempt to contact the LCUP with the FQDN included in the LCUP instance auxiliary information received from the LMF, and establish a related PDU session to the related dnn+slice determined by the URSP rule. The terminal device can receive a PDU session establishment completion message from the network as a response to the PDU session establishment request.

[0100] In some embodiments of the present disclosure, EASDF is configured for the session. In this case, EASDF can be used to ensure that the local LCUP function instance is used when determining the IP address of the LCUP function instance. The network can reuse R17 EASDF, where the EDI (EASDF deployment information) references the FQDN range defined by the standard (*.LMF.5gc.mnc <mnc>.mcc <mcc>.3gppnetwork.org) to trigger the offloading of this service. For example, the UE issues a DNS request, and the EASDF adds location information to this request so that the trusted DNS determines the correct local instance and triggers the SMF to insert the correct UPF for service offloading.

[0101] It is important to note that if the SMF is configured to use a very local PSA (PDU Session Anchor) UPF for the dnn+slice being used, then the use of EASDF may not be required.

[0102] It should be noted that there are alternative solutions for delivering the LCUP address to the UE. SUPL has defined OMA Push over SMS delivery or UDP Push for this information. The LCUP address can be delivered with the help of this push mechanism; however, the delay of the push mechanism delivery is unpredictable.

[0103] Figure 3 A flowchart of an example method 300 for establishing a UP connection to enhance CP location services according to some example embodiments of the present disclosure is illustrated. The method can be performed at a network system (such as a core network of a 3GPP 5G system, or any other network system with CP location service enhancement requirements).

[0104] like Figure 3 As illustrated in FIG. 3 , in block 310 , the AMF may select an LMF serving the terminal device in response to initiation of a control plane (CP) positioning procedure.

[0105] As mentioned above, the CP positioning process can be initiated in a variety of different ways. The CP positioning process can be, for example, the MT-LR process, MO-LR process, or NI-LR process defined by 3GPP. The GMLC can send Namf_Location_ProvidePositioningInfo to the AMF through the Namf interface to request the AMF to provide CP location service. The AMF selects the LMF to provide the CP location service for the UE and notifies the selected LMF to perform the positioning operation.

[0106] In block 320, the LMF may transmit location service user plane (LCUP) assistance information in control plane (CP) positioning protocol signaling. The LCUP assistance information includes at least one of the following items: addressing information of the LCUP function instance, relevance information of the ongoing CP positioning process, and security information for establishing a user plane (UP) session between the terminal device and the LCUP function instance. In particular, the LCUP function instance is associated with the selected LMF serving the terminal device.

[0107] As reference Figure 2 As described, LCUP auxiliary information can be provided to the terminal device in a variety of different ways. In some embodiments of the present disclosure, the LCUP auxiliary information can be included in a capability indication message. In some embodiments of the present disclosure, the LCUP auxiliary information can be included in an auxiliary provision message. In fact, any CP positioning related signaling can be used for LMF to deliver LCUP auxiliary information to the terminal device.

[0108] In some embodiments of the present disclosure, the LCUP auxiliary information includes addressing information of the LCUP function instance. The addressing information may be, for example, a fully qualified domain name (FQDN) specific to the LCUP function instance.

[0109] In some embodiments of the present application, the standard defined FQDN range (such as *.LMF.5gc.mnc <mnc>.mcc <mcc>.3gppnetwork.org) can be used as the FQDN of the UE to reach the <mcc> ., <mnc>) defined in the PLMN. A specific FQDN can be used together with pre-configured URSP rules to route the traffic exchanged with the selected LCUP instance to the appropriate data network (identified by DNN in 5G networks) and network slice (identified by S-NSSAI in 5G networks). The pre-configured URSP rules can be configured by the PCF based on the guidance of the URSP settings from the AF. In addition, the AF can also configure the EAS deployment information (EDI) related to the LCUP instance via the process defined in 3GPP 23.548 Section 6.2.3.4.

[0110] In some embodiments of the present disclosure, the network (eg, PCF) may transmit UE Routing Selection Policy (URSP) rules containing information about routing rules associated with different FQDN ranges to the terminal device in order to communicate with the LCUP function.

[0111] In some embodiments of the present disclosure, the LCUP instance assistance information may alternatively or additionally include: security information for establishing a user plane (UP) session between the terminal device and the LCUP function instance. The security information may include, for example, transport layer security attribute information for establishing a secure UP connection for establishing an SSL / TLS connection between the UE and the LCUP. In some embodiments, for example, when the UE wants to start a session via a SUPL Position Initialization (POSINIT) message to initiate a positioning protocol session, the security information may also include a hash-based message authentication code field.

[0112] In some embodiments of the present disclosure, the LCUP instance assistance information may alternatively or additionally include correlation information about the ongoing CP positioning process. The correlation information includes information used to correlate the ongoing CP positioning process with the UP connection to further ensure the security of the UP connection. The correlation information may include a correlation identifier, which includes the LMF address and the positioning request identifier. The LMF may assign the correlation identifier as correlation information to the positioning request, which may, for example, include the LMF address and the positioning request identifier, and provide the correlation identifier as part of the LCUP assistance information on the CP, for example, via LPP signaling to the terminal device.

[0113] The LCUP assistance information also contains information about ports on the LCUP function instance, such as TCP or UDP ports on the LCUP. Additionally or alternatively, the LCUP assistance information may also include information about positioning methods or protocols supported by the LCUP function instance, such as those given in Table 1.

[0114] In block 330, the LCPU may establish a secure UP connection between the terminal device and the LCUP function instance using information provided by the terminal device from the LCUP assistance information, so as to exchange positioning related information with the terminal device using the LCUP function instance.

[0115] In some embodiments of the present disclosure, a terminal device may establish a secure connection with a LCUP instance by using at least one of addressing information, correlation information, and security information received in LCUP auxiliary information, wherein the correlation information is used to identify a corresponding ongoing positioning process associated with the secure connection.

[0116] In some embodiments of the present disclosure, the UE may contact the LCUP and use the security information to establish a secure connection with the LCUP. The security information may include, for example, transport layer security (TLS) attribute information for establishing a secure UP connection. The TLS attribute information may, for example, correspond to a key that is used as a pre-shared key to protect the TLS link between the UE and the LCUP, and the LCF may use it to establish an SSL / TLS connection between the UE and the LCUP. In some embodiments, for example, when the UE wants to start a session via a SUPL POSI NIT message to initiate a positioning protocol session, the security information may also include a hash-based message authentication code field.

[0117] In some embodiments of the present disclosure, the network system may alternatively or additionally receive relevance information about an ongoing CP positioning procedure from a terminal device that contacts the LCUP to establish a UP connection. The relevance information may include a relevance identifier assigned by, for example, the LMF for a location request. The relevance identifier may include, for example, an LMF address and a positioning request identifier, or other information capable of relating the UP connection to an appropriate CP positioning procedure.

[0118] With the help of the LMF address contained in the correlation identifier, the LCUP can contact the appropriate LMF and provide the location request identifier to the LMF. The LMF can then use the location request identifier to retrieve the ongoing location request for the device and map the LCS request for the UE with the UE's UP data path via LCUP. Therefore, LCS operations can be performed using LCUP for communication. Therefore, further security can be ensured because only devices that receive the correlation information (sent via the secure CP) can be associated with the ongoing location request via UP signaling exchange.

[0119] The terminal device communicates with the network system to obtain the IP address of the LCUP instance on the PDU session, which is selected or established by the terminal device by mapping the FQDN range corresponding to the FQDN of the LCUP function instance to the data network name and network slice based on the URSP rules.

[0120] When there is no appropriate ongoing PDU session between terminal devices, the network system may establish a protocol data unit (PDU) session in response to a PDU session establishment request from the terminal device; and transmit a PDU session establishment completion message to the terminal device.

[0121] If the SMF has been configured to use EASDF for PDU sessions, the SMF can select, insert and control the EASDF. The SMF can configure the EASDF for the session with DNS message processing rules that refer to the EDI provided by the AF.

[0122] In some embodiments of the present disclosure, an EASDF is configured for the session and may be used to ensure that a local LCUP function instance is used when determining the IP address of the LCUP function instance.

[0123] It should be noted that most of the operations on the network side basically correspond to the operations on the UE side, and therefore the operations on the network side will not be described in detail. Figure 2 The operations on the UE side are described for reference.

[0124] With the aid of embodiments of the present disclosure, the UE can perform LCS user plane (UP) interaction with the LCUP (associated with the LMF serving the terminal device). In this way, the CP positioning operation can be effectively and efficiently enhanced through the UP interaction between the terminal device and the LUCP (which is associated with the LMF). In addition, in some embodiments of the present disclosure, it can also be ensured that the UE contacting the LCUP is the same as the UE undergoing the LCS process involving the corresponding LMF, thereby ensuring the security of the UP connection.

[0125] Example Process

[0126] Figure 4 An example signaling diagram 400 for implementing LUCP-based CP location service enhancement is illustrated. It should be noted that the signaling diagram 400 is provided for illustration purposes only, and the present disclosure is not limited thereto.

[0127] like Figure 4 As illustrated in , when LCUP is deployed in the network, the OAM associated with the location (e.g., acting as an AF) can provide 401 guidance for URSP rule setup for (multiple) UEs as defined in TS 23.548 Section 6.6. The PCF in 102 can use the guidance to set the URSP rules. The AF can also configure EAS deployment information related to LCUP via the process defined in 23.548 Section 6.2.3.4.

[0128] The PCF (in the HPLMN) sets the URSP rules based on the guidance in 401 and sends the URSP rules to the UE 402. The URSP rules define the rules for mapping the FQDN of the LCUP to the relevant dnn+slice (where the slice corresponds to the S-NSSAI) according to 3GPP TS23.502 Section 4.16.11 / 4 / 6 / 12 and 3GPP TS23.503.

[0129] When a CP procedure occurs (such as the procedure defined in TS23.273 for MT-LR, or TS23.273 ( Figure 6 .2-1): 5GC-MO-LR process), for example, GMLC can send a 403Namf_Location_ProvidePositioningInfo request to AMF.

[0130] As part of the process, the AMF selects 404a a serving LMF and requests 404b the LMF to perform a positioning operation using Nlmf_Location_DetermineLocation.

[0131] The LMF sends 405a LPP signaling to the UE (which is carried via NAS and AMF) in 405a to provide Figure 2 and Figure 3 LCUP assistance information described. For example, the LMF may provide LCUP assistance information (via LPP) to indicate to the UE that the network supports LCUP. The LPP signaling may be the first request capability message from the LMF to the UE. In this case, the UE may further indicate in the request capability response message in 405b whether it supports contacting LCUP for this LCS request.

[0132] The LCUP assistance information may be provided in a Provide Assistance LPP message in reply to a Request Assistance LPP message. Any CP positioning related signaling from the network may actually be used by the LMF to deliver the LCUP assistance information to the terminal device, so reference to the Provide Assistance and Request Capability LPP messages is mainly used for illustration purposes. In any case, the LPP signaling passes through the AMF and NGRAN. It must be noted that even though NG RAN is indicated as the access network between the UE and the core network (AMF, LMF, SMF, etc.), the procedures described in the present invention may also be run on any access network, including, for example, TNGF, W-AGF (defined in 3GPP TS23.501 and TS23.316)

[0133] The LCUP assistance information may include at least one of the addressing information of the LCUP instance (e.g., FQDN), security material for UP connection establishment, and relevance information for the ongoing CP positioning process. The LCUP assistance information may also include the positioning methods or protocols supported by the LCUP function instance, and possible TCP or UDP ports at the LCUP. For more information about the LCUP assistance information, see reference Figure 2 and Figure 3 The content described.

[0134] After receiving the LCUP assistance information, the UE may attempt to contact the LCUP whose addressing information (e.g., FQDN) is received from the LMF, and establish the relevant PDU session using the URSP rule received in 402. For example, the UE may obtain the FQDN of the LCUP in the LCUP assistance information and map it to the FQDN range of the preconfigured URSP rule to determine the relevant dnn+slice based on the mapping in the FQDN rule. Therefore, the PDU establishment request for the appropriate network slice associated with the LCUP instance may be first routed to the AMF in 406a and then to the SMF in 406b.

[0135] If the SMF has been configured in 401 to use EASDF for this PDU Session (for dnn+slice) as part of the establishment of this PDU Session, the SMF selects, inserts and controls the EASDF as defined in TS23.548 section 6.2. The SMF configures the EASDF for the session with DNS message processing rules that reference the FQDN range defined in the standard (e.g. *.LMF.5gc.mncMNC>.mcc <mcc>.3gppnetwork.org) associated EDI (configured in 401) to trigger the offloading of related services.

[0136] After the PDU session establishment is completed, the SMF sends 408a a PDU session establishment complete message to the AMF, and the AMF forwards 408b the message to the UE.

[0137] The UE attempts to get the IP address of the LCUP by sending 409 a DNS query request. EASDF may be used in 410 to ensure that a local UPF is used between the UE and the LCUP, as defined in 3GPP TS 23.548. The UE receives 411 the IP address of the LCUP (more than one IP address may be received).

[0138] The UE contacts 412a the LCUP and establishes a secure connection with the LCUP using the security material and the correlation information. The LCUP determines the suggested LMF based on the LMF address in the correlation and contacts 412b the LMF. The LMF retrieves the ongoing positioning request for this device using the positioning request identifier in the correlation information and maps the LCS request for the UE with the UP data path with the UE via the LCUP. Thus, a location determination procedure may be performed in 413 using the LCUP for communication between the UE and the LMF.

[0139] Example Device

[0140] Figure 5 is a simplified block diagram of a device 500 suitable for implementing embodiments of the present disclosure. For example, Figure 1 and Figure 4 The terminal device 101 and network elements (such as LMF, LUCP, SMF, AFM, AF, PCF, GLMC, EASDF, etc.) shown in the figure can be implemented by the device 500. As shown in the figure, the device 500 includes one or more processors 510, one or more memories 520 coupled to the processor 510, and one or more communication modules 540 coupled to the processor 510.

[0141] The communication module 540 is used for two-way communication. The communication module 540 has at least one antenna to facilitate communication. The communication interface may represent any interface required to communicate with other network elements.

[0142] Processor 510 may be of any type suitable for the local technology network, and may include, as non-limiting examples, one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 500 may have multiple processors, such as application specific integrated circuit chips, that are time-slaved to a clock synchronized with a main processor.

[0143] The memory 520 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 524, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital versatile disc (DVD), and other magnetic and / or optical memories. Examples of volatile memories include, but are not limited to, random access memory (RAM) 522 and other volatile memories that do not persist during power outages.

[0144] Computer program 530 includes computer executable instructions executed by associated processor 510. Program 530 may be stored in ROM 524. Processor 510 may perform any suitable actions and processes by loading program 530 into RAM 522.

[0145] The embodiments of the present disclosure can be implemented by means of a program 530, so that the device 500 can execute the Figure 2-Figure 4 Any method or process of the present disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0146] In some example embodiments, program 530 may be tangibly embodied in a computer-readable medium that may be included in device 500 (e.g., in memory 520) or in other storage devices accessible to device 500. Device 500 may load program 530 from the computer-readable medium into RAM 522 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 6 An example of a computer readable medium 800 in the form of a CD or DVD is shown. The computer readable medium has a program 530 stored thereon.

[0147] It should be understood that future networks may utilize network function virtualization (NFV), which is a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that can be operably connected or linked together to provide services. Virtualized network functions (VNFs) may include one or more virtual machines that use standard or general-purpose types of servers rather than customized hardware to run computer program code. Cloud computing or data storage may also be utilized. In wireless communications, this may mean that node operations are at least partially performed in a central / centralized unit CU (e.g., a server, host, or node) that is operably coupled to a distributed unit DU (e.g., a wireless head / node). Node operations may also be distributed among multiple servers, nodes, or hosts. It should also be understood that the distribution of labor between core network operations and base station operations may vary depending on the implementation.

[0148] In an embodiment, the server may generate a virtual network through which the server communicates with the distributed units. In general, a virtual network may involve the process of combining hardware and software network resources and network functionality into a single software-based management entity (virtual network). Such a virtual network may provide a flexible allocation of operations between the server and the wireless head / node. In fact, any digital signal processing task may be performed in the CU or DU, and the boundaries of transferring responsibilities between the CU and DU may be selected based on the implementation.

[0149] Therefore, in an embodiment, a CU-DU architecture is implemented. In this case, the device 500 may be included in a central unit (e.g., a control unit, an edge cloud server, a server), which is operably coupled to a distributed unit (e.g., a remote wireless head / node) (e.g., via a wireless or wired network). That is, the central unit (e.g., an edge cloud server) and the distributed units may be independent devices that communicate with each other via a wireless path or a wired connection. Alternatively, they may be in the same entity that communicates via a wired connection, etc. The edge cloud or edge cloud server may serve multiple distributed units or wireless access networks. In an embodiment, at least some of the processes may be performed by the central unit. In another embodiment, the device 500 may be included in a distributed unit, and at least some of the processes may be performed by the distributed unit.

[0150] In an embodiment, the execution of at least some functionality of the apparatus 500 may be shared between two physically separate devices (DU and CU) forming an operational entity. Therefore, the apparatus may be viewed as describing an operational entity comprising one or more physically separate devices for performing at least some of the processes. In an embodiment, such a CU-DU architecture may provide a flexible allocation of operations between the CU and the DU. In practice, any digital signal processing task may be performed in the CU or the DU, and the boundary for transferring responsibilities between the CU and the DU may be selected based on the implementation. In an embodiment, the apparatus 500 controls the execution of the process regardless of the location of the apparatus or where the process / function is performed.

[0151] Generally, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.

[0152] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer executable instructions, such as those included in a program module, which are executed in a device on a target real or virtual processor to perform the above-referenced Figure 2-Figure 4 Method 200, 300 or process 400 described herein. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or split between program modules as desired. The machine executable instructions of program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in local and remote storage media.

[0153] The program code for executing the disclosed method can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that when the processor or controller executes the program code, the functions / operations specified in the flow chart and / or block diagram are implemented. The program code can be executed completely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.

[0154] In the context of the present disclosure, computer program codes or related data may be carried by any appropriate carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.

[0155] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared or semiconductor system, device or apparatus, or any suitable combination of the foregoing. More specific examples of computer readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0156] In addition, although each operation is described in a specific order, this should not be understood as requiring such operations to be performed in the specific order shown or in sequence, or requiring the execution of all illustrated operations to achieve the desired result. In some scenarios, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of the present disclosure, but should be interpreted as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of separate embodiments may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination.

[0157] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.< / mcc> < / mnc> < / mcc> < / mcc> < / mnc> < / mcc> < / mnc> < / mcc> < / mcc> < / mnc> < / mcc> < / mnc> < / mnc> < / mcc> < / mcc> < / mnc>

Claims

1. A terminal device, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, cause the terminal device to: receiving location service user plane (LCUP) assistance information in control plane (CP) positioning protocol signaling, wherein the LCUP assistance information includes at least one of the following items: addressing information of an LCUP function instance, relevance information of an ongoing CP positioning procedure, and security information for establishing a user plane (UP) session between the terminal device and the LCUP function instance, and wherein the LCUP function instance is associated with a location management function (LMF) selected to serve the terminal device; as well as A secure UP connection is established between the terminal device and the LCUP function instance by using the LCUP auxiliary information, so as to perform a positioning operation using the LCUP function instance.

2. The terminal device according to claim 1, wherein the addressing information of the LCUP function instance comprises at least: The fully qualified domain name (FQDN) specific to this instance of the LCUP function.

3. The terminal device according to claim 2, wherein the terminal device is further configured to: A protocol data unit (PDU) session is selected or established based on the FQDN of the UP instance and a pre-configured UE routing policy (URSP) rule, wherein the pre-configured UE routing policy (URSP) rule contains information of routing rules associated with different FQDN ranges in order to communicate with the LCUP function instance.

4. The terminal device according to claim 3, wherein the PDU session is selected or established by mapping the FQDN range corresponding to the FQDN of the LCUP function instance to a data network name and a network slice based on the URSP rule.

5. The terminal device according to any one of claims 1 to 4, wherein the CP positioning protocol signaling includes a capability indication message, and the capability indication message indicates that the network supports a UP function for positioning purposes.

6. The terminal device according to any one of claims 1 to 5, wherein the CP positioning protocol signaling comprises: An assistance provision message is transmitted from the LMF to the terminal device.

7. The terminal device according to any one of claims 1 to 6, wherein the terminal device is further configured to: transmit the CP positioning protocol signaling to indicate that the terminal device supports UP functionality for positioning purposes.

8. The terminal device according to any one of claims 1 to 7, wherein the LCUP auxiliary information further includes one or more of the following items: information about the port of the LCUP function instance, and information about the positioning method or protocol supported by the LCUP function instance.

9. The terminal device according to any one of claims 1 to 8, wherein the security information comprises: Transport layer security attribute information used to establish the secure UP connection.

10. The terminal device according to claim 9, wherein the security information further comprises a hash-based message authentication code field.

11. The terminal device according to any one of claims 1 to 12, wherein the terminal device is further configured to: transmitting a PDU session establishment request to the network to establish the PDU session using the fully qualified domain name (FQDN) of the UP instance and the preconfigured UE routing policy (URSP); and A PDU session establishment complete message is received from the network.

12. The terminal device according to any one of claims 1 to 11, wherein the terminal device is further configured to: A domain name server (DNS) request is transmitted to convert the FQDN of the LCUP function instance into an IP address.

13. The terminal device according to any one of claims 1 to 12, wherein the terminal device is further configured to: The secure connection is established with the LCUP instance by using at least one of the correlation information and the security information received in the LCUP assistance information, wherein the correlation information is used to identify a corresponding ongoing positioning procedure associated with the secure connection.

14. A network system comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, with the at least one processor, cause the network device to: In response to initiation of a control plane (CP) positioning procedure, selecting a location management function (LMF) serving the terminal device; transmitting, from the LMF, location service user plane (LCUP) assistance information in control plane (CP) positioning protocol signaling, wherein the LCUP assistance information comprises at least one of the following: addressing information of an LCUP function instance, relevance information of an ongoing CP positioning procedure, and security information for establishing a user plane (UP) session between the terminal device and the LCUP function instance, and wherein the LCUP function instance is associated with the LMF selected to serve the terminal device; as well as Using information provided by the terminal device from the LCUP assistance information, a secure UP connection is established between the terminal device and the LCUP function instance, so as to exchange positioning related information with the terminal device using the LCUP function instance.

15. The network system according to claim 14, wherein the addressing information of the LCUP function instance comprises at least: The fully qualified domain name (FQDN) specific to this instance of the LCUP function.

16. The network system according to claim 15, wherein the network system is further configured to: UE routing policy (URSP) rules are transmitted to the terminal device, the UE routing policy (URSP) rules containing information about routing rules associated with different FQDN ranges for communication with the LCUP function.

17. A network system according to any one of claims 14 to 16, wherein the terminal device communicates with the network system to obtain the IP address of the LCUP instance on a PDU session, and the PDU session is selected or established by the terminal device by mapping the FQDN range corresponding to the FQDN of the LCUP function instance to a data network name and a network slice based on the URSP rule.

18. The network system according to any one of claims 14 to 17, wherein the CP positioning protocol signaling includes a capability indication message indicating that the network supports a UP function for positioning purposes.

19. The network system according to any one of claims 14 to 18, wherein the CP positioning protocol signaling comprises: An assistance provision message is transmitted from the LMF to the terminal device.

20. The network system according to any one of claims 14 to 19, wherein the network device is further configured to receive CP positioning protocol signaling, the CP positioning protocol signaling indicating that the terminal device supports a UP function for positioning purposes.

21. The network system according to any one of claims 14 to 20, wherein the LCUP assistance information further comprises one or more of the following items: information about ports at the UP function, and information about positioning methods or protocols supported by the LCUP function instance.

22. The network system according to any one of claims 14 to 21, wherein the security information comprises transport layer security attribute information for establishing a secure UP connection.

23. The network system according to claim 22, wherein the security information further comprises: Hash-based message authentication code field.

24. The network system according to any one of claims 14 to 23, wherein the network system is further configured to: A secure connection is established between the device and the LCUP instance using at least one of the security information and the correlation information received from the terminal device, wherein the correlation information is used to identify a corresponding ongoing positioning procedure associated with the secure connection.

25. The network system according to any one of claims 14 to 24, wherein the network system is further configured to: establishing a protocol data unit (PDU) session in response to a PDU session establishment request from the terminal device; and Transmit a PDU session establishment completion message to the terminal device.

26. The network system of claim 25, wherein establishing the PDU session comprises: An edge application server discovery function (EASDF) for the PDU session is determined and configured with domain name server message processing rules based on EASDF deployment information associated with an FQDN range associated with the LCUP.

27. The network system according to claim 26, wherein the network system is further configured to ensure the use of a local LCUP function instance by means of the EASDF in determining the IP address of the LCUP function instance.

28. A network device comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, cause the network system to: Transmitting Location Services User Plane (LCUP) assistance information in Control Plane (CP) Positioning Protocol signaling, wherein the LCUP assistance information includes at least one of the following items: addressing information of the LCUP function instance, correlation information of the ongoing CP positioning process, and security information for establishing a user plane (UP) session between the terminal device and the LCUP function instance; and The LCUP function instance is associated with the LMF selected to serve the terminal device.

29. The network device of claim 28, wherein the CP positioning protocol signaling includes a capability indication message indicating that the network supports a UP function for positioning purposes.

30. The network device of claim 28, wherein the CP positioning protocol signaling comprises: An assistance provision message transmitted to the terminal device.

31. The network device according to any one of claims 28 to 30, wherein the network device is further configured to: receiving correlation information from said LUCP function instance establishing a UP connection; and Based on the correlation information, the UP connection is correlated with a corresponding ongoing CP positioning procedure.

32. A method comprising: receiving location service user plane (LCUP) assistance information in control plane (CP) positioning protocol signaling, wherein the LCUP assistance information includes at least one of the following items: addressing information of an LCUP function instance, relevance information of an ongoing CP positioning procedure, and security information for establishing a user plane (UP) session between the terminal device and the LCUP function instance, wherein the LCUP function instance is associated with a location management function (LMF) selected to serve the terminal device; as well as A secure UP connection is established between the terminal device and the LCUP function instance by using the LCUP auxiliary information, so as to perform a positioning operation using the LCUP function instance.

33. A method comprising: In response to initiation of a control plane (CP) positioning procedure, selecting a location management function (LMF) serving the terminal device; transmitting, from the LMF, location service user plane (LCUP) assistance information in control plane (CP) positioning protocol signaling, wherein the LCUP assistance information comprises at least one of the following: addressing information of an LCUP function instance, relevance information of an ongoing CP positioning procedure, and security information for establishing a user plane (UP) session between the terminal device and the LCUP function instance, and wherein the LCUP function instance is associated with the LMF selected to serve the terminal device; as well as Using information provided by the terminal device from the LCUP assistance information, a secure UP connection is established between the terminal device and the LCUP function instance, so as to exchange positioning related information with the terminal device using the LCUP function instance.

34. An apparatus comprising: means for receiving location service user plane (LCUP) assistance information in control plane (CP) positioning protocol signaling, wherein the LCUP assistance information comprises at least one of the following: addressing information of an LCUP function instance, relevance information of an ongoing CP positioning procedure, and security information for establishing a user plane (UP) session between the terminal device and the LCUP function instance, and wherein the LCUP function instance is associated with a location management function (LMF) selected to serve the terminal device; as well as A secure UP connection is established between the terminal device and the LCUP function instance by using the LCUP auxiliary information, so as to perform a positioning operation using the LCUP function instance.

35. An apparatus comprising: means for selecting a location management function (LMF) serving a terminal device in response to initiation of a control plane (CP) positioning procedure; means for transmitting location service user plane (LCUP) assistance information from the LMF in control plane (CP) positioning protocol signaling, wherein the LCUP assistance information comprises at least one of the following: addressing information of an LCUP function instance, relevance information of an ongoing CP positioning procedure, and security information for establishing a user plane (UP) session between the terminal device and the LCUP function instance, and wherein the LCUP function instance is associated with the LMF selected to serve the terminal device; as well as means for establishing a secure UP connection between the terminal device and the LCUP function instance using information provided by the terminal device from the LCUP assistance information, so as to exchange positioning related information with the terminal device using the LCUP function instance.

36. A computer-readable medium comprising program instructions for causing an apparatus to perform at least one method according to any one of claims 28 to 29.

Citation Information

Patent Citations

  • Address information sending method, address information obtaining method, address information sending device, address information obtaining device, equipment and medium

    CN113115480A

  • Positioning measurement reporting in unlicensed spectrum

    CN114173371A

  • Supporting location services at a base station

    WO2020204961A1