Method, apparatus, device, system and computer readable medium for location service enhancement based on user plane interface used by terminal device

Abstract

Embodiments of the present disclosure relate to devices, methods, apparatuses, and computer readable storage media for enhancing location services based on usage of a user plane interface of a terminal device. According to embodiments of the present disclosure, a terminal device can receive 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, 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; and establish a secure UP connection between the terminal device and the LCUP function instance using the LCUP assistance information in order to perform a UP positioning operation using the LCUP function instance.

Description

Technical Field

[0001] Embodiments of this disclosure generally relate to the telecommunications field, and more particularly to apparatus, methods, devices, and computer-readable media for enhancing location services based on a user plane interface with a terminal device. Background Technology

[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. Furthermore, user plane positioning has been proposed as a solution to enhance location services.

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

[0004] In general, exemplary embodiments of this disclosure provide devices, methods, apparatuses, and computer-readable media for location service enhancement based on user plane functionality.

[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, together with the at least one processor, to 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: 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 using the LCUP auxiliary information 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, together with the at least one processor, for the network device to: select a Location Management Function (LMF) to serve a terminal device in response to the initiation of a Control Plane (CP) positioning process; 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: 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 establish a secure UP connection between the terminal device and the LCUP function instance using information provided by the terminal device from the LCUP auxiliary information, 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., an 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, together with the at least one processor, to cause 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: 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, and wherein the LCUP function instance is associated with an LMF selected to serve the terminal device.

[0008] In a fourth aspect, a method is provided. The method includes: receiving Location Services User Plane (LCUP) auxiliary information in control plane (CP) positioning protocol signaling, wherein the LCUP auxiliary information includes at least one of the following: 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 using the LCUP auxiliary information to perform a positioning operation using the LCUP function instance.

[0009] In a fifth aspect, another method is provided. This method includes: in response to the initiation of a control plane (CP) positioning process, selecting a location management function (LMF) to serve a terminal device; transmitting 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: 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, wherein the LCUP function instance is associated with the LMF selected to serve the terminal device; and establishing a secure UP connection between the terminal device and the LCUP function instance using information provided by the terminal device from the LCUP auxiliary information, 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 includes: components for receiving Location Services User Plane (LCUP) auxiliary information in control plane (CP) positioning protocol signaling, wherein the LCUP auxiliary information includes 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 for establishing a secure UP connection between the terminal device and the LCUP function instance using the LCUP auxiliary information to perform a UP positioning operation using the LCUP function instance.

[0011] In a seventh aspect, another apparatus is provided. The apparatus includes: components for selecting a Location Management Function (LMF) to serve a terminal device in response to the initiation of a Control Plane (CP) positioning process; components for transmitting 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: 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 to serve the terminal device; and components 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 auxiliary information, so as to exchange positioning-related information with the terminal device using the LCUP function instance.

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

[0013] It should be understood that the summary section is not intended to identify key or essential features of embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0014] The above and other objects, features, and advantages of this disclosure will become more apparent from the more detailed description of some exemplary embodiments of the present disclosure in the accompanying drawings, wherein:

[0015] Figure 1 The illustration shows an example system in which exemplary embodiments of the present disclosure may be implemented;

[0016] Figure 2 The illustration shows a flowchart of an example method according to some example embodiments of the present disclosure;

[0017] Figure 3 The illustration shows a flowchart of an example method according to some example embodiments of the present disclosure;

[0018] Figure 4 The illustration shows a signaling diagram of an example process according to some example embodiments of the present disclosure;

[0019] Figure 5 A simplified block diagram of a device suitable for implementing embodiments of the present disclosure is illustrated; 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 accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0022] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are for illustrative purposes only and are intended to help those skilled in the art to understand and implement this disclosure, without implying any limitation on the scope of this disclosure. This disclosure described herein can be implemented in various ways other than those described below.

[0023] In the following description and claims, unless otherwise defined, 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 pertains.

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

[0025] It should be understood that although the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. 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 terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” also include the plural forms. It should also be understood that the terms “comprising,” “having,” and / or “including”, when used herein, specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

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

[0028] (a) Pure hardware circuit implementation (such as implementations only in analog and / or digital circuit systems) and

[0029] (b) A combination of hardware circuitry and software, such as (if applicable):

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

[0031] (ii) Any part of the (multiple) hardware processors having software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions) and

[0032] (c) Multiple hardware circuits and / or multiple processors, such as multiple microprocessors or a portion thereof, that require software (e.g., firmware) to operate, but which may be absent when operation does not require software.

[0033] This definition of "circuit system" applies to all uses of the term herein, including all uses in any claim. As a further example, as used herein, the term "circuit system" also covers the implementation of only hardware circuitry or a processor (or processors) or a portion thereof and its (or their) accompanying software and / or firmware. For example, and where applicable to a particular claim element, the term "circuit system" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0034] As used herein, the term "communication network" refers to a network that conforms to 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. Furthermore, communication within a communication network between User Equipment (UE) and network devices, or between network devices, can be performed according to any appropriate communication protocol, including but not limited to first-generation (1G) standards. st Generation 1G), Second Generation (2G) nd Generation (2G), 2.5G, 2.75G, third generation (3G) rd Generation 3G), fourth generation (4G) th Generation 4G, 4.5G, and 5G (5G) th Generation 6 (5G) communication protocols and / or any other currently known or future protocols, such as the future sixth generation (6G) th Generation (6G). Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, there will certainly be future communication technologies and systems that embody the future types of this disclosure. This should not be construed as limiting the scope of this disclosure to the systems described above.

[0035] As used herein, the term "network device" refers to a node in a communication network that a UE has access to and receives services from. A network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (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, or 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" are used interchangeably.

[0036] The term "UE" refers to any terminal device capable of wireless communication. By way of example and not limitation, a 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 can include, but is not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture devices (such as digital cameras), gaming devices, music storage and playback devices, in-vehicle wireless devices, wireless endpoints, mobile stations, laptop embedded equipment (LEE), laptop mounted equipment (LME), Universal Serial Bus (USB) dongles, smart devices, customer premises equipment (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (such as remote surgery), and UE-type riding side units (RodeSide). Units (RSUs), industrial equipment and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics, devices operating in commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal equipment," "communication equipment," "terminal," "user equipment," and "UE" are used interchangeably. 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. Furthermore, user plane positioning has been proposed as a location service enhancement solution. Therefore, architectural enhancements are needed 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 element proposed in this 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. A key objective of this architectural enhancement is to identify and improve the 3GPP Location Service (LCS) features and enhancements required for positioning by utilizing the user plane interface between the UE and the network, such as reducing 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 centralized or edge deployments, for example...

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

[0040] - Whether and how to enhance the existing 5GS LCS architecture or related processes to support Mobile Originating Location Request (MO-LR), Mobile Terminal-Location Request (MT-LR), delayed MT-LR, and regulatory-related location processes (when user plane location is involved).

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

[0042] - Requirements for the transmission protocol, such as the need for reliable transmission and in-order delivery.

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

[0044] -Possible enhancements to the user plane as the control plane.

[0045] The embodiments disclosed herein are enhancements to user plane discovery and control plane enhancements. The discovery of the user plane location interface termination is the process by which the UE uses the Domain Name System (DNS) to discover the IP addresses of (multiple) (Internet Protocol) servers (or Service Location Protocol, SLP in the Open Mobile Alliance (OMA) terminology) suitable for the user plane server.

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

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

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

[0049]

[0050]

[0051] The table above lists various positioning methods or protocols. A-GNSS indicates a positioning method based on the Assisted Global Navigation Satellite System; OTDOA indicates a positioning method based on observation time difference of arrival; E-CID indicates an enhanced cell ID; sensor indicates a sensor-based positioning method; WLAN indicates a positioning method based on wireless local area networks; 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 angle of departure; 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 angle of arrival. As can be seen from the table, SUPL can only provide partial measurements for the Multi-RTT method.

[0052] For the User Plane LCS, the SLP instance is defined by the Open Mobility Alliance (OMA) SLP FQDN specification, which can be referenced below.

[0053] - For emergency situations, it is located in Section 6.1.5.1 of OMA-TS-ULP-V2_0_6-20200804-A (most industry suppliers follow this approved specification).

[0054] - For non-emergency situations, it is not well defined in the approved OMA specifications, but the candidate specification 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 this disclosure present a hypothetical architecture in which the LMF can use a hybrid of CP (control plane) and UP (user plane) interactions for a single LCS request. The LMF uses CP interactions to interact with, for example, the NG RAN or the UE, such as requesting the NG RAN to send signals to the UE or to measure some signals from the UE, and uses UP interactions with the UE after a brief CP interaction to request the UE to send signals to the NG RAN or to report measurements of some signals from the NG RAN.

[0057] The embodiments disclosed herein are intended to provide enhancements to the traditional 3GPP control plane (CP) specification to integrate UP communication between the UE and LCS functionality in the network.

[0058] Example Environment

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

[0060] UE 101 is communicatively connected to the access network or radio access network RAN ​​102. RAN 102 may be, for example, a next-generation radio access network (NG-RAN), which is the access network for 3GPP 5G systems.

[0061] UE 101 is also communicatively connected to Access and Mobility Management Function (AMF) 105. AMF 105 is the gateway 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 via the Nanf interface. AMF 105 is also communicatively connected to RAN 102 via interface N2.

[0062] RAN 102 is also communicatively connected to User Plane Function (UPF) 103 via the N3 interface. As an important unit in the 3GPP 5G system core network, 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 via the N4 and N6 interfaces.

[0063] SMF 105 is a network element in the core network used for session management. Specifically, it is responsible for user plane interaction with UPF 103, creating, updating, and deleting sessions, and managing session contexts. SMF 105 can also communicate with other network elements via Nsmf.

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

[0065] Location Management Functions (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 for UE location management and provide location and velocity calculation and verification. LMF1 107a and LMF2 107b can receive location requests for UE or from AMF via the Nlmf interface, communicate with 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 and non-3GPP interoperability functions to obtain location information.

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

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

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

[0069] Unified Data Management (UDM) function 111 provides centralized management of network user data, particularly managing data used for access authorization, user registration, and data network profiles. UDM provides services to AMF, SMF, and other NFs via NUDM, such as Network Open Functions (NEF), which sits between the 5G core network and external third-party application functions and is responsible for managing external open network data. All external applications wishing to access data within the 5G core must go through the NEF.

[0070] The Edge Application Server Discovery Function (EASDF) 112 acts as the UE's Domain Name System (DNS) resolver and can supplement DNS queries with UE location-related information, enabling the DNS system to resolve to application servers located near the UE. EASDF can communicate with other NFs via the Neasdf interface.

[0071] In addition, the system includes other NFs, such as NEFs, Policy Charging Functions (PCFs), and Application Functions (AFs), all of which can communicate with other network elements in the core network through their respective interfaces. It should be noted that, for simplicity, these other NFs are not included in the main documentation. Figure 1 The description is in the middle.

[0072] Example embodiments of this disclosure relate to user plane communication between a UE located by LMFs 107a and 107b and LMFs 107a and 107b, which is conducted through an LCUP entity determined by the LMF to enhance CP positioning. One object of this disclosure is to enable the UE to contact the LCUP via the UP, which corresponds to the user plane terminal of the LMF of the serving terminal equipment.

[0073] To this end, embodiments of this disclosure propose providing LCUP instance assistance information from the network to the UE to enable the establishment of a secure UP connection between the UE and the appropriate LCUP. In this way, UP interactions can be performed between the UE and the appropriate LCUP to enhance the corresponding CP location process.

[0074] The embodiments of this disclosure can be implemented as follows: Figure 1 The system illustrated in the figure is implemented within 100; however, it should be understood that... Figure 1 The illustrations are for illustrative purposes only and do not imply any limitation on the scope of protection. Rather, embodiments of this 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 implementations are described in detail.

[0076] Example Method

[0077] Figure 2 The illustration shows a flowchart of an example method 200 for location service enhancement based on user plane functionality according to some example embodiments of the present disclosure. This method can be performed at a terminal device (such as a UE) or any other terminal device with CP location service enhancement requirements.

[0078] Method 200 can be initiated after the user plane participates in the CP positioning process (e.g., the MT-LR, MO-LR, or NI-LR process defined by 3GPP). Furthermore, the UP interface between the UE and the LMF can be direct or indirect (i.e., supporting proxy mode or non-proxy mode as defined by the OMASUPL specification). As mentioned, in response to a location request, the AMF can select an LMF instance as the serving LMF for the terminal device and use... Nlmf_Location_DetermineLocation The message requests the LMF to perform a location operation. The LMF may have an associated LCUP for the location operation, 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 the diagram, at block 210, the terminal device can receive Location Services User Plane (LCUP) assistance information from the network control plane (CP) positioning protocol signaling (e.g., LTE Positioning Protocol (LPP) signaling). The LCUP assistance information contains information used to assist in establishing a UP connection between the UE and the LCUP. The LCUP assistance information may include at least one of the following: addressing information of the LCUP function instance, relevance information of the ongoing CP positioning process, and security information used to establish a user plane (UP) session between the terminal device and the LCUP function instance. Specifically, the LCUP function instance is associated with a Location Management Function (LMF) selected to serve the terminal device.

[0080] LCUP assist information can be received in several different ways. In some example embodiments of this disclosure, LCUP assist information can be included in a capability request / indication message. This capability / indication request message is transmitted by the network (e.g., LMF) to indicate that the network supports user plane functions for location purposes, requesting the UE to report its capabilities. This capability / indication request message may contain LCUP assist information. In response to receiving the capability indication message, the terminal device can send a capability indication response message to the network to indicate that the terminal device supports user plane functions for location purposes. Additionally, the terminal can spontaneously send LPP signaling to indicate that the terminal device also supports user plane functions for location purposes.

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

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

[0083] In some embodiments of this disclosure, LCUP auxiliary information includes addressing information for an LCUP function instance. As mentioned above, when LCUP is used in the LCS procedure, it is necessary to ensure that the LCUP used by the UE matches the LMF already selected by the AMF. For this purpose, addressing information may 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 this disclosure, the addressing information may be, for example, a fully qualified domain name (FQDN) specific to an LCUP functional instance. This means that different LCUP functional instances have different FQDNs. For example, an FQDN can uniquely identify an LCUP functional instance.

[0085] In some embodiments of this application, the standard-defined FQDN range (such as...) .LMF.5gc.mnc <mnc>.mcc <mcc>.3gppnetwork.org can be used as an FQDN to reach ( <mcc> ., <mnc>Any LCUP defined in the PLMN. Wildcard parameter within the FQDN. "Different LCUP instances can have different values. For example, for an LCUP instance, the FQDN could 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 in conjunction with URSP rules to ensure that devices use PDU sessions to go to the correct DNN (Data Network Name) and network slice S-NSSAI to reach the LCUP associated with the LMF selected by the AMF.

[0087] In some embodiments of this disclosure, when LCUP is deployed in a network, an Operations Management and Maintenance (OAM) instance (e.g., acting as an AF) associated with the management of location capabilities in the network can provide guidance to the PCF on USRP rule settings for terminal devices (e.g., UEs as defined in TS 23.548, Section 6.6). The PCF instance can use this guidance to set USRP rules. USRP rules can map the FQDN of different LCUP instances to appropriate data networks and slices identified by the associated Data Network Name (DNN) and Single Network Slice Selection Auxiliary Information (S-NSSAI). Furthermore, the AF can further configure EAS Deployment Information (EDI) associated with the LCUP instance via the procedures defined in 3GPP 23.548, Section 6.2.3.4. EDI can be used for IP address lookup operations as described in 3GPP TS 23.548.

[0088] The PCF (e.g., in a Home Public Land Mobile Network (HPLMN)) can then send URSP rules to the UE. Thus, through the URSP rules, the UE is able to select the appropriate dnn+slice (and therefore the appropriate PDU session) to reach the LCUP in the HPLMMN and the LCUP in each visited public land mobile network (VPLMN) with which the HPLMMN has a roaming agreement. With the help of the URSP rules, the terminal device can map the FQDN range defined above to the relevant dnn+slice for use in the serving PLMN for UP communication between the UE and the LCUP. In roaming scenarios, the VPLMN will provide the appropriate dnn+slice to the HPLMMN as part of the roaming agreement. In this roaming case, this PDU session operates in LBO local breach mode. The existing PCF interface can be used to send URSP rules to the UE, and therefore no modification to the URSP structure is required.

[0089] In some embodiments of this disclosure, the LCUP instance auxiliary information may alternatively or additionally include security information for establishing a user plane (UP) session between the terminal device and the LCUP functional 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 this 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 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, such as when the UE wants to initiate a location protocol session by launching a session via a SUPL location initialization (POS INIT) message, the security information may also include a hash-based message authentication code field. However, if the UE launches the session via a SUPL START message as the initial message, such a field is not required.

[0090] In some embodiments of this disclosure, LCUP instance auxiliary information may alternatively or additionally include relevance information regarding the ongoing CP location process. The relevance information contains information used to associate the ongoing CP location process with the UP connection to further ensure the security of the UP connection. A network element such as an LMF may assign a relevance identifier as part of the location request, which may include, for example, an LMF address and a location request identifier. The LMF may provide the relevance identifier as part of the LCUP auxiliary information on the CP, for example, via LPP signaling to the terminal device. In subsequent operations establishing a UP connection between the terminal device and the LCUP, the relevance identifier may be used to associate the ongoing CP location process with the UP connection, as will be described below.

[0091] The LCUP auxiliary information also includes information about the ports of the LCUP functional instance, such as the TCP or UDP port of the LCUP. Additionally or alternatively, the LCUP auxiliary information may also include information about the positioning methods or protocols supported by the LCUP functional instance, such as those given in Table 1. With this information, a secure UP connection can be established, as described in reference 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 LCUP auxiliary information, so as to perform a location operation using the LCUP function instance.

[0093] In some embodiments of this disclosure, a terminal device can establish a secure connection with an LCUP instance by using at least one of relevance information and security information received in the LCUP assistance information, wherein the relevance information is used to identify the corresponding ongoing location process associated with the secure connection. The LMF maps LCS requests related to the UE to the UE's UP data path via the LCUP. Therefore, LCS operations can be performed using the LCUP for communication between the LMF and the UE.

[0094] When the security information includes transport layer security attribute information for establishing a secure UP connection, the terminal device can 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. When the security information includes a hash-based message authentication code field, the terminal device can use this authentication code field during UP connection establishment to initiate a location protocol session by sending a SUPL location initialization (POSINIT) message. However, as noted above, if the UE initiates the session using a SUPL START message as the initial message, such a field is not required.

[0095] In some embodiments of this disclosure, the IP address of the LCUP can be obtained through a DNS query. For example, the terminal device can transmit a Domain Name Server (DNS) request to translate the FQDN of the LCUP functional instance into one or more IP addresses used to reach the LCUP.

[0096] In some embodiments of this disclosure, at least one IP address of an LCUP function instance can be obtained through a Protocol Data Unit (PDU) session selected or established by means of a Protocol Data Unit (PDU) session based on the FQDN of the UP instance and UE Routing Policy (URSP) rules containing information about routing rules related to different FQDN ranges. It should be noted that the terminal device can receive more than one IP address, and the terminal device can randomly use one of them to establish a UP connection or use the address selection rules carried in the DNS response.

[0097] To enable DNS lookups, terminal devices can select or establish Protocol Data Unit (PDU) sessions to communicate with LCUP functional instances based on the FQDN of the UP instance and UE Routing Policy (URSP) rules containing routing rule information related to different FQDN ranges. For example, by mapping the FQDN range corresponding to the FQDN of the LCUP functional instance to data network names and network slices based on URSP rules, a PDU session can be selected or established.

[0098] In some embodiments of this application, on the network side, an Edge Application Server Discovery Function (EASDF) can be determined for a PDU session, and domain name server message processing rules can be configured for it based on EASDF deployment information associated with the FQDN range (which is associated with LCUP). If the SMF is 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 TS 23.548). The SMF can configure EASDF for the session using DNS message processing rules that reference the EDI configured by the AF, which is associated with the standard-defined FQDN range (…). .LMF.5gc.mncMNC>.mcc <mcc>It is associated with .3gppnetwork.org in order to trigger the unloading of related services.

[0099] In some embodiments of this disclosure, where there is no suitable ongoing PDU session between the terminal device and the network, the terminal device may transmit a PDU session establishment request to the network to determine PDU session parameters using the Fully Qualified Domain Name (FQDN) of the UP instance and the UE Routing Policy (URSP), thereby establishing a PDU session. For example, the terminal device may attempt to contact the LCUP using the FQDN contained in the LCUP instance auxiliary information received from the LMF and establish a relevant PDU session with the relevant dnn+slice determined by the URSP rules. The terminal device may receive a PDU session establishment complete message from the network as a response to the PDU session establishment request.

[0100] In some embodiments of this disclosure, EASDF is configured for the session. In this case, EASDF can be used to ensure that the local LCUP functional instance is used when determining the IP address of the LCUP functional 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>(e.g., .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 a trusted DNS can determine the correct local instance and trigger the SMF to insert the correct UPF for service offloading.

[0101] It should be noted that if SMF is configured to use a very local PSA (PDU session anchor) UPF for the dnn+slice being used, then EASDF may not be necessary.

[0102] It is important to note that alternative solutions exist for delivering the LCUP address to the UE. SUPL has defined OMA Push over SMS or UDP Push for this information. LCUP addresses can be delivered using this push mechanism; however, the delivery delay of the push mechanism is unpredictable.

[0103] Figure 3 The illustration shows 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. This method can be performed at a network system, such as the 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 the diagram, in block 310, the AMF can select the LMF to serve the terminal device in response to the initiation of the control plane (CP) positioning process.

[0105] As mentioned above, the CP positioning process can be initiated in several 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 data to the AMF via the Namf interface. Namf_Location_ProvidePositioningInfo The UE requests the AMF to provide CP location services. The AMF selects the LMF to provide CP location services to the UE and instructs the selected LMF to perform the location operation.

[0106] In block 320, the LMF can transmit Location Services User Plane (LCUP) auxiliary information in the Control Plane (CP) Positioning Protocol signaling. The LCUP auxiliary information includes at least one of the following: 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. Specifically, the LCUP function instance is associated with the selected LMF serving the terminal device.

[0107] For reference Figure 2 As described, LCUP assistance information can be provided to the terminal device in a variety of different ways. In some embodiments of this disclosure, LCUP assistance information may be included in a capability indication message. In some embodiments of this disclosure, LCUP assistance information may be included within an assistance provision message. In fact, any CP location-related signaling can be used by the LMF to deliver LCUP assistance information to the terminal device.

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

[0109] In some embodiments of this application, the standard-defined FQDN range (such as...) .LMF.5gc.mnc <mnc>.mcc <mcc>.3gppnetwork.org can be used as the UE's FQDN to reach ( <mcc> ., <mnc>Any LCUP defined in the PLMN. A specific FQDN can be used in conjunction with pre-configured URSP rules to route traffic exchanged with the selected LCUP instance to the appropriate data network (identified by the 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 according to guidance from the URSP settings provided by the AF. Furthermore, the AF can also configure EAS deployment information (EDI) associated with the LCUP instance via the procedures defined in Section 6.2.3.4 of 3GPP 23.548.

[0110] In some embodiments of this disclosure, the network (e.g., PCF) may transmit UE routing policy (URSP) rules to the terminal device, which contain information about routing rules related to different FQDN ranges in order to communicate with the LCUP function.

[0111] In some embodiments of this disclosure, the LCUP instance auxiliary information may alternatively or additionally include security information for establishing a user plane (UP) session between the terminal device and the LCUP functional instance. The security information may include, for example, transport layer security attribute information for establishing a secure UP connection, to facilitate the establishment of an SSL / TLS connection between the UE and the LCUP. In some embodiments, such as when the UE wants to initiate a location protocol session by launching a session via a SUPL location initialization (POSINIT) message, the security information may also include a hash-based message authentication code field.

[0112] In some embodiments of this disclosure, LCUP instance auxiliary information may alternatively or additionally include relevance information regarding the ongoing CP location process. The relevance information contains information used to associate the ongoing CP location process with the UP connection to further ensure the security of the UP connection. The relevance information may include a relevance identifier, which includes an LMF address and a location request identifier. The LMF may assign the relevance identifier as relevance information to the location request, which may, for example, include the LMF address and the location request identifier, and provide the relevance identifier as part of the LCUP auxiliary information on the CP, for example, via LPP signaling to the terminal device.

[0113] LCUP auxiliary information also includes information about ports on the LCUP functional instance, such as TCP or UDP ports on the LCUP. Additionally or alternatively, LCUP auxiliary information may also include information about the location methods or protocols supported by the LCUP functional instance, such as those given in Table 1.

[0114] In block 330, the LCPU can 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 location-related information with the terminal device using the LCUP function instance.

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

[0116] In some embodiments of this disclosure, the UE can contact the LCUP and use security information to establish a secure connection with the LCUP. The security information may include, for example, Transport Layer Security (TLS) attribute information used to establish a secure UP connection. The TLS attribute information may correspond, for example, to a key that is used as a pre-shared key to protect the TLS link between the UE and the LCUP, and which the LCF can use to establish an SSL / TLS connection between the UE and the LCUP. In some embodiments, such as when the UE wants to initiate a location protocol session by sending a SUPL POSI NIT message, the security information may also include a hash-based message authentication code field.

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

[0118] Using the LMF address contained in the relevance identifier, the LCUP can contact the appropriate LMF and provide it with a location request identifier. The LMF can then use the location request identifier to retrieve an ongoing location request for that device and map the LCS request for the UE to the UE's UP data path via the LCUP. Therefore, LCS operations can be performed using the LCUP for communication. This ensures further security because only the device that receives the relevance information (sent via a secure CP) can be associated with an 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. This IP address is selected or established by the terminal device by mapping the FQDN range corresponding to the FQDN of the LCUP functional instance to the data network name and network slice based on URSP rules.

[0120] When there is no appropriate ongoing PDU session between terminal devices, the network system can respond to a PDU session establishment request from a terminal device to establish a Protocol Data Unit (PDU) session and transmit a PDU session establishment completion message to the terminal device.

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

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

[0123] It should be noted that most operations on the network side essentially correspond to operations on the UE side, and therefore, network-side operations will not be elaborated upon further. Specific details can be found in [link to relevant documentation / references]. Figure 2 The described operation on the UE side is for reference.

[0124] Using embodiments of this disclosure, a UE can perform LCS user plane (UP) interaction with an LCUP (associated with an LMF serving the terminal device). In this way, CP positioning operations can be effectively and efficiently enhanced through UP interaction between the terminal device and the LCUP (associated with the LMF). Furthermore, in some embodiments of this disclosure, it can be ensured that the UE contacting the LCUP is the same UE undergoing the LCS procedure 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 CP location service enhancement based on LCUP is illustrated. It should be noted that signaling diagram 400 is provided for illustrative purposes only, and this disclosure is not limited thereto.

[0127] like Figure 4 As illustrated in the diagram, when LCUP is deployed in a network, the location-associated OAM (e.g., acting as an AF) can provide guidance (401) for setting URSP rules for (multiple) UEs as defined in Section 6.6 of TS23.548. The PCF in 102 can use this guidance to set URSP rules. The AF can also configure EAS deployment information related to LCUP via the procedures defined in Section 6.2.3.4 of TS23.548.

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

[0129] When a CP procedure occurs (such as the procedure defined for MT-LR in TS 23.273, or TS 23.273 ( Figure 6 .2-1): During the 5GC-MO-LR process, for example, GMLC can send a 403 to AMF. Namf_Location_ ProvidePositioningInfo ask.

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

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

[0132] LCUP assistance information can be provided in the Provide Assistance LPP message in response to the Request Assistance LPP message. Any CP location-related signaling from the network can actually be used by the LMF to deliver LCUP assistance information to the terminal device; therefore, the reference to the Provide Assistance and Request Capability LPP messages is primarily for illustrative purposes. In any case, LPP signaling passes through the AMF and NGRAN. It must be noted that even if the NGRAN is indicated as the access network between the UE and the core network (AMF, LMF, SMF, etc.), the procedures described in this invention can operate on any access network, including, for example, TNGF, W-AGF (defined in 3GPP TS 23.501 and TS23.316).

[0133] LCUP ancillary information may include at least one of the following: LCUP instance addressing information (e.g., FQDN), security material for UP connection establishment, and relevant information about the ongoing CP location process. LCUP ancillary information may also include the location method or protocol supported by the LCUP functional instance, and the possible TCP or UDP port at the LCUP. For more information on LCUP ancillary information, please refer to the reference. Figure 2 and Figure 3 The content described.

[0134] Upon receiving LCUP assistance information, the UE can attempt to contact the LCUP that received its addressing information (e.g., FQDN) from the LMF and establish a relevant PDU session using the URSP rules received in 402. For example, the UE can obtain the LCUP's FQDN from the LCUP assistance information and map it to the FQDN range of a pre-configured URSP rule to determine the relevant DNN+slice based on the mapping in the FQDN rule. Therefore, a PDU establishment request for the appropriate network slice associated with the LCUP instance can be routed to the AMF first in 406a and then to the SMF in 406b.

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

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

[0137] The UE attempts to obtain the LCUP's IP address by sending a 409 DNS query request. EASDF can be used in section 410 to ensure the use of a local UPF between the UE and the LCUP, as defined in 3GPP TS 23.548. The UE receives the LCUP's IP address in section 411 (it can receive more than one IP address).

[0138] The UE contacts the LCUP at 412a and establishes a secure connection with the LCUP using security materials and correlation information. The LCUP determines the proposed LMF based on the LMF address in the correlation and contacts the LMF at 412b. The LMF uses the location request identifier in the correlation information to retrieve the ongoing location request for this device and maps the LCS request for the UE to the UP data path of the UE via the LCUP. Therefore, the location determination procedure can be performed in 413 using the LCUP for communication between the UE and the LMF.

[0139] Example device

[0140] Figure 5 This 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 units (such as LMF, LCUP, SMF, AFM, AF, PCF, GLMC, EASDF, etc.) shown can be implemented by device 500. As shown, device 500 includes one or more processors 510, one or more memories 520 coupled to processor 510, and one or more communication modules 540 coupled to processor 510.

[0141] The communication module 540 is used for bidirectional communication. The communication module 540 has at least one antenna to facilitate communication. The communication interface can represent any interface required for communication with other network units.

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

[0143] 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 storage. 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 that are executed by the 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] Embodiments of this disclosure can be implemented using program 530, such that device 500 can perform as described in the reference. Figures 2-4 Any methods or processes discussed in this disclosure. Embodiments of this disclosure may also be implemented in hardware or a combination of software and hardware.

[0146] In some example embodiments, program 530 may be tangibly contained in a computer-readable medium, which 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 can leverage Network Functions Virtualization (NFV), a network architecture concept that proposes virtualizing network node functions as "building blocks" or entities that can be operatively connected or linked together to provide services. Virtualized network functions (VNFs) can include one or more virtual machines that use standard or general-purpose servers instead of custom hardware to run computer program code. Cloud computing or data storage can also be utilized. In wireless communications, this may mean that node operations are performed, at least partially, in a central / centralized unit (CU, such as a server, host, or node) operatively coupled to a distributed unit (DU, such as a radio head / node). Node operations may also be distributed across multiple servers, nodes, or hosts. It should also be understood that the allocation of labor between core network operations and base station operations may vary depending on the implementation.

[0148] In this embodiment, the server can generate a virtual network through which it communicates with the distributed units. Generally, a virtual network can 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 can provide flexible allocation of operations between the server and the wireless heads / nodes. In fact, any digital signal processing task can be performed in the CU or DU, and the boundaries of responsibility transferred between the CU and DU can be selected depending on the implementation.

[0149] Therefore, in this embodiment, a CU-DU architecture is implemented. In this case, device 500 may be included in a central unit (e.g., a control unit, an edge cloud server, a server) that is operatively coupled to distributed units (e.g., remote wireless heads / nodes) via a wireless or wired network. That is, the central unit (e.g., the 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 this embodiment, at least some of the processes may be performed by the central unit. In another embodiment, 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, at least some functional execution of device 500 can be shared between two physically separate devices (DU and CU) forming an operational entity. Therefore, the device can be considered as an operational entity comprising one or more physically separate devices for performing at least some of the processes. In an embodiment, this CU-DU architecture can provide flexible allocation of operations between the CU and DU. In practice, any digital signal processing task can be performed in either the CU or the DU, and the boundaries of responsibility transferred between the CU and DU can be selected depending on the implementation. In an embodiment, device 500 controls the execution of processes regardless of the device's location or where the process / function is performed.

[0151] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while others 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 this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0152] This 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 program modules, which are executed in a device targeting a real or virtual processor to perform the functions described above. Figures 2-4 Methods 200, 300, or procedures 400 are described. Typically, a program module includes 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 separated among program modules as desired. The machine-executable instructions of a program module can be executed on a local or distributed device. In a distributed device, program modules can reside on local and remote storage media.

[0153] Program code for performing the methods disclosed herein can be written in any combination of one or more programming languages. This program code can be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus such that, when the processor or controller executes the program code, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program code can be executed entirely on a machine, partially on a machine, as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

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

[0155] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination of the foregoing. More specific examples of computer-readable storage media include: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0156] Furthermore, although the operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or requiring that all illustrated operations be performed to achieve the desired result. In some scenarios, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of this disclosure, but rather as a description of features that may be specific to particular embodiments. Certain features described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, 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 this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary 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, enable the terminal device to: The device receives Location Services User Plane (LCUP) auxiliary information in the Control Plane (CP) Positioning Protocol signaling, wherein the LCUP auxiliary information includes at least one of the following: addressing information of the LCUP function instance 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 that the LCUP function instance can be used to perform a positioning operation.

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

3. The terminal device according to claim 2, wherein the terminal device is further configured to: A Protocol Data Unit (PDU) session is established based on the FQDN of the UP instance and the pre-configured UE Routing Policy (URSP) rules, which contain information on routing rules related to different FQDN ranges, in order to communicate with the LCUP functional 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 the data network name and network slice based on the URSP rules.

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

6. The terminal device according to any one of claims 1 to 4, wherein the CP positioning protocol signaling includes: Assistance provision messages transmitted from the LMF to the terminal device.

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

8. The terminal device according to any one of claims 1 to 4, wherein the LCUP auxiliary information further includes one or more of the following: 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 4, wherein the security information includes: 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 includes a hash-based message authentication code field.

11. The terminal device according to any one of claims 1 to 4, wherein the terminal device is further configured to: A PDU session establishment request is transmitted to the network to establish the PDU session using the Fully Qualified Domain Name (FQDN) of the UP instance and the pre-configured UE Routing Policy (URSP); and Receive a PDU session establishment complete message from the network.

12. The terminal device according to any one of claims 1 to 4, wherein the terminal device is further configured to: Transmit a Domain Name Server (DNS) request to translate the FQDN of the LCUP functional instance into an IP address.

13. The terminal device according to any one of claims 1 to 4, 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 the corresponding ongoing location process 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, together with the at least one processor, to enable the network device to: In response to the initiation of the control plane (CP) positioning process, select the location management function (LMF) to serve the terminal device. The LMF transmits Location Service User Plane (LCUP) auxiliary information in the Control Plane (CP) Positioning Protocol signaling, wherein the LCUP auxiliary information includes at least one of the following: addressing information of the LCUP function instance 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 auxiliary information, a secure UP connection is established between the terminal device and the LCUP function instance so that the LCUP function instance can exchange location-related information with the terminal device.

15. 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, together with the at least one processor, to make the network system: Location Services User Plane (LCUP) auxiliary information is transmitted in the control plane (CP) positioning protocol signaling. The LCUP auxiliary information includes at least one of the following: addressing information of the LCUP function instance 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; as well as Using information provided by the terminal device from the LCUP auxiliary information, a secure UP connection is established between the terminal device and the LCUP function instance so that the LCUP function instance can exchange location-related information with the terminal device.

16. A communication method, comprising: The terminal receives location service user plane (LCUP) auxiliary information in the control plane (CP) positioning protocol signaling, wherein the LCUP auxiliary information includes at least one of the following: addressing information of the LCUP function instance 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 that the LCUP function instance can be used to perform a positioning operation.

17. A communication method, comprising: In response to the initiation of the control plane (CP) positioning process, select the location management function (LMF) to serve the terminal device. The LMF transmits Location Service User Plane (LCUP) auxiliary information in the Control Plane (CP) Positioning Protocol signaling, wherein the LCUP auxiliary information includes at least one of the following: addressing information of the LCUP function instance 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 auxiliary information, a secure UP connection is established between the terminal device and the LCUP function instance so that the LCUP function instance can exchange location-related information with the terminal device.

18. A communication device, comprising: A component for receiving 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: addressing information of an LCUP function instance 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 that the LCUP function instance can be used to perform a positioning operation.

19. A communication device, comprising: Components for selecting a location management function (LMF) to serve a terminal device in response to the initiation of a control plane (CP) positioning process; A component for transmitting Location Services 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: addressing information of an LCUP function instance 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 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 auxiliary information, so as to exchange location-related information with the terminal device using the LCUP function instance.

20. A computer-readable medium comprising program instructions for causing a device to perform at least one method according to any one of claims 16 to 17.

Images