Methods and devices for managing location services in wireless communication

Abstract

A method for managing location services in a core network configured to provide wireless services to user equipment, UE, wherein the method is carried out in a location node and comprises: receiving (403, 404) a message, identifying a requesting entity, wherein the message is indicative of a request for positioning information related to at least one UE; retrieving (405), based on receiving the message, privacy information of the at least one UE, wherein the privacy information is stored in the core network; upon the retrieved privacy information comprising identification of the requesting entity as being allowed to obtain positioning information related to the at least one UE: obtaining (410) the position information, and transmitting (411) the obtained position information to the requesting entity.

Description

[0001] METHODS AND DEVICES FOR MANAGING LOCATION SERVICES IN

[0002] WIRELESS COMMUNICATION

[0003] Technical field

[0004] This disclosure is related to communication in wireless systems wherein wireless devices communicate with a radio network. Specifically, solutions are provided for managing location services to facilitate obtainment of positioning information related to wireless devices.

[0005] Background

[0006] Various protocols and technical requirements for wireless communication have been standardized under supervision of inter alia the 3rd Generation Partnership Project (3GPP). Improvement and further development are continuously carried out, and new or amended functions and features are thus implemented in successive releases of the technical specifications providing the framework for wireless communication.

[0007] Wireless communication may in various scenarios be carried out between a network and a wireless device. The network typically comprises a core network and an access network, also referred to as RAN (Radio Access Network), including a plurality of access nodes, which historically have been referred to as base stations. In a 5G radio access network such a base station may be referred to as a gNB. Each access node may be configured to serve one or more cells of a cellular wireless network. A variety of different types of wireless devices may be configured to communicate with the access network, and such wireless devices are generally referred to as User Equipment (UE).

[0008] A fundamental aspect of wireless communication is that it allows UEs to be mobile. For various purposes, it may thus be desirable to obtain positioning information related to UEs. For such purposes, a variety of location services have been developed. In this context, it may be noted that position / location are both used in the art, and may be considered to relate to the same or similar subjects. Examples of positioning information related to a UE may comprise an absolute (e.g., geographical) position, a relative position, such as distance or direction with respect to another entity (e.g., another UE), a heading, i.e., a direction of movement, or a velocity of movement. One example of a service used for obtaining positioning information is satellitebased services, such as GPS (Global Positioning Service). In addition, various types of services based on Radio Access Technology (RAT) have been suggested, such as Observed Time Difference of Arrival (OTDOA), which is based on measurement of the time it takes for signals to travel between the UE and multiple base stations.

[0009] In various scenarios, other entities than the UE itself may request or desire to obtain positioning information related to that UE. Such other entities may be other wireless device, network functions, applications, etc. In this context, the UE may be notified and requested to allow positioning, i.e., sharing of its positioning information to the requesting entity.

[0010] Summary

[0011] An overall objective of the proposed solution is to provide improvement in the field of managing and sharing positioning information related to a UE. The proposed solution is defined by the terms of the independent claims, whereas further aspects and details are set out in the dependent claims and in the description below.

[0012] According to one aspect, a method is provided for managing location services in a core network configured to provide wireless services to user equipment, UE, wherein the method is carried out in a location node and comprises: receiving a message, identifying a requesting entity, wherein the message is indicative of a request for positioning information related to at least one UE; retrieving, based on receiving the message, privacy information of the at least one UE, wherein the privacy information is stored in the core network; upon the retrieved privacy information comprising identification of the requesting entity as being allowed to obtain positioning information related to the at least one UE: obtaining the position information, and transmitting the obtained position information to the requesting entity.

[0013] Based on the proposed solution, occurrence of undue signaling to obtain consent to allow other entities to obtain positioning information related to a UE may be minimized. This improves resource efficiency in the wireless system and improves ability for UEs to conserve energy. Brief description the drawings

[0014] Fig. 1 schematically illustrates an implementation of a wireless communication system, in which a core network is configured to provide wireless services to UEs.

[0015] Fig. 2 schematically illustrates a UE configured to operate in the wireless system according to various examples of the proposed solution.

[0016] Fig. 3 schematically illustrates a general presentation of a core network node which may implement different functions in different examples of the proposed solution.

[0017] Fig. 4 shows a signaling diagram, illustrating various aspects and examples of the proposed solution.

[0018] Detailed description

[0019] In the following description, for the purposes of explanation and not limitation, details are set forth herein related to various examples. However, it will be apparent to those skilled in the art that the present invention may be practiced in other examples that depart from these specific details. In some instances, detailed descriptions of well- known devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail. The functions of the various elements including functional blocks, including but not limited to those labeled or described as “computer”, “processor” or “controller”, may be provided through the use of hardware such as circuit hardware and / or hardware capable of executing software in the form of coded instructions stored on computer readable medium. Thus, such functions and illustrated functional blocks are to be understood as being either hardware-implemented and / or computer-implemented and are thus machine-implemented. In terms of hardware implementation, the functional blocks may include or encompass, without limitation, digital signal processor (DSP) hardware, reduced instruction set processor, hardware (e.g., digital or analog) circuitry including but not limited to application specific integrated circuit(s) (ASIC), and (where appropriate) state machines capable of performing such functions. In terms of computer implementation, a computer is generally understood to comprise one or more processors or one or more controllers, and the terms computer and processor and controller may be employed interchangeably herein. When provided by a computer or processor or controller, the functions may be provided by a single dedicated computer or processor or controller, by a single shared computer or processor or controller, or by a plurality of individual computers or processors or controllers, some of which may be shared or distributed. Moreover, use of the term “processor” or “controller” shall also be construed to refer to other hardware capable of performing such functions and / or executing software, such as the example hardware recited above.

[0020] Before presenting aspects and examples of the proposed solution, context and devices for use of the proposed solution will be briefly described with reference to the drawings. The drawings are to be regarded as being schematic representations and elements illustrated in the drawings are not necessarily shown to scale. Rather, the various elements are represented such that their function and general purpose become apparent to a person skilled in the art. Any connection or coupling between functional blocks, devices, components, or other physical or functional units shown in the drawings or described herein may also be implemented by an indirect connection or coupling. A coupling between components may also be established over a wireless connection. Functional blocks may be implemented in hardware, firmware, software, or a combination thereof.

[0021] Fig. 1 illustrates a wireless system, in which UEs may communicate wirelessly by radio signaling with a wireless network 100. Fig. 1 is useful for context of the proposed solution and illustrates various entities and functions which cooperate in wireless system.

[0022] The wireless network 100 may be a radio communication network 100, configured to operate under the provisions of 5G as specified by 3GPP, according to various examples, or further generations.

[0023] The wireless network 100 may comprise a core network (CN) 110, connectable to an external network 130 such as the Internet. The core network may comprise a plurality of core network nodes, which realize logical functions. For the example of a 5G system, as illustrated, this may, inter alia, include respective nodes for Access and Mobility Management Function (AMF) 101, Gateway Mobile Location Center (GMLC) 102, Unified Data Management (UDM) 103, Unified Data Repository (UDR) 104, Network Exposure Function (NEF) 105, User Plane Function (UPF) 108, and Policy Control Function (PCF) 109. These nodes and their functions are as such legacy of the 5G system (5GS). It shall also be noted that the core network 110 may comprise further nodes configured to operate further functions, according to legacy procedures. One or more Application Functions (AF) 106 may be deployed outside of the 5G system i.e., as an application running on an application server (AS) 107 connected to the external network e.g., the Internet, which application server provides data for communication in the wireless system. Operators may deploy the AF 106 as trusted or non-trusted. A trusted AF 106 may have access to all interface with the CN 110 while an un-trusted must access anything inside the CN via the NEF 105.

[0024] The wireless network 100 further comprises an access network 120, comprising a plurality of access nodes (AN), configured for radio communication on a radio channel 141, 142, 143 with wireless devices, such as with the illustrated respective wireless devices UE1, UE2, and UE3. The wireless network 100 may further configure wireless devices for direct communication on a radio channel 144, such as UE1 between UE2 as illustrated. This may in various examples be referred to as Sidelink communication, which as such is a legacy 3GPP procedure.

[0025] In various scenarios, a certain entity of the wireless system, such as UE3 or the AF 106, may desire and request to obtain positioning information related to at least one UE. In this context, positioning information related to a UE may comprise measurement or estimate of an absolute or a relative position / location of the UE, e.g., as determined by a positioning procedure. Herein, the entity which desires to obtain the positioning information is referred to as a requesting entity. In this context, and by way of example with reference to Fig. 1, the desired positioning information may be an absolute position of UE1 and / or UE2, or relative positioning information such as a distance and / or direction between UE1 and UE2 or with respect to another position or object. In yet another example, the requesting entity may desire to obtain information of UEs present in a certain area, either specifically whether UE1 and / or UE2 are located within said area, or information of which UEs are present within the area, or simply information of presence of any UE within the area.

[0026] For context, various aspects relating to legacy procedure for obtaining positioning information related to a UE are briefly discussed below.

[0027] 3GPP has hitherto not specified a case when a UE (UE3) request location information of another UE (UE1 and / or UE2). Until Rel-18 only a 3rd party AF / LCS (Location Services) client could request such information. However, a new feature labelled Ranging / Sidelink (SL) Positioning is specified in 3GPP specification SA2 TS 23.586. This feature includes the possibility that a UE, e.g., UE3, can invoke the Ranging / Sidelink positioning service exposure to retrieve positioning information related to at least one other UE, such as absolute position or relative distance between two other UEs, such as UE1 and UE2. In a scenario where the third UE, UE3, is not in proximity of the at least one UE, i.e., UE1 and UE2, the UE3 needs to send a request to the network 100 and ask the network 100 to trigger the Ranging / Sidelink measurements. As the requesting entity, UE3 may thus act as SL Positioning Client UE. According to TS 23.586 the UE3 can either send the request via the control plane (clause 5.6.2.4) or via the user plane (clause 5.6.2.3). As location information is sensitive information it is important that such information is only shared if there is consent to do so.

[0028] In 5G, the control and user (data) planes are split. No security / privacy solution has been specified for Ranging / SL Positioning service exposure through 5GC U-plane (user) in 3GPP specification TS 33.533. For service exposure through 5GC C-plane (control), TS 33.533 provides that authorization for security and privacy specified for SL Positioning Client UE using Ranging / SL Positioning reuses the authorization for MO-LR (Mobile Originated Location Requests) as specified in 3GPP specification TS 23.273. MO-LR authorization is performed by the AMF by checking the subscriber information. Once the Client UE authorization is verified by the AMF, the AMF forwards the SL-MO-LR to the GMLC. TS 33.533 does not specify any privacy checking for this exposure service, i.e., checking of whether consent exists for positioning or location services, such as Ranging / SL Positioning. However, when the service is invoked by AF / 5G NF the GMLC interacts with the UDM to check the privacy profile of the UEs. The Content of legacy UE LCS Privacy Profile is specified in 3GPP specification TS 23.273 and is taken as baseline for Ranging / Sidelink Positioning according to TS 33.533.

[0029] In this context, it may be noted that the Privacy profile granularity is coarse, whether the LCS is allowed / not allowed / based on user interaction etc. It is not defined on UE / sub scription level, i.e., which UE / subscriber that is allowed to see / obtain other UEs location. Moreover, a specific UE / subscriber (Resource Owner) cannot provide consent or revoke consent for a specific Client UE, when exposure over control plane is used without explicit notification interaction between the wireless network and the UE / subscriber / user. As noted, there are two options for a third UE (UE3) to invoke the Ranging / SL Positioning service exposure according to TS 23.586, either through the control plane or through the user plan. In both cases the GMLC will be involved and according to legacy functionality the GMLC is the Network Function that performs the privacy check. For the control plan option, it has been suggested that the GLMC based privacy check can be reused. However, no method for privacy check when UE would use the user plane via the NEF has been specified.

[0030] According to the solutions outlined herein, it is proposed to enhance privacy information management and privacy check, to include privacy control on UE level. According to one aspect, this entails storing privacy information related to a UE (such as UE1 and / or UE2) in the core network 110, such that the privacy information comprises identities of entities, i.e., requesting entities, which are allowed to obtain positioning information related to the UE.

[0031] Various aspects relate to a location node of the core network 110, such as a GMLC in an embodiment set out in a 5G core network 110. Further aspects relate to a core network node configured to store privacy information, such as a UDM and / or a UDR. Further aspects relate to an entity configured to control privacy information of the UE1 and UE2, such as the UE1 and UE2 itself or an AF which owns or controls the UE(s) (UE1, UE2 and optionally UE3).

[0032] Before proceeding with details of the proposed solution, a brief description of various elements will be described, which may be configured to carry out the proposed solution.

[0033] Fig. 2 schematically illustrates an example of a UE 10 configured to communicate with the wireless network 100 as presented herein and configured for carrying out various method steps as outlined. The drawing shows some relevant elements or functions of the UE 10 are shown in the drawing. The UE 10 may however include other features and elements than those shown in the drawing or described herein, such as a power supply, a casing, a user interface, sensors, etc., but these are left out for the sake of simplicity. Any one of UE1, UE2, and UE3 may be realized in accordance with UE 10.

[0034] The UE 10 comprises a radio transceiver 213, also referred to herein as modem 213, for communicating in one or more frequency bands with other entities of the radio communication network 100, such as with the access node 121 or with another UE over an air interface, such as by Sidelink communication. The transceiver 213 may thus include a receiver chain (Rx) and a transmitter chain (Tx), for communicating through at least an air interface, referred to as Uu in 3GPP. The transceiver 213 may be or comprise a modem configured to encode, transmit, receive and decode data using radio waves.

[0035] The UE 10 may further comprise an antenna system 214, which may include one or more antennas, antenna ports or antenna arrays. The antenna system 214 is connected to the transceiver 213.

[0036] The UE 10 further comprises logic circuitry 210 configured to control data and signal communication via the radio transceiver on a physical channel, such as channel 141, 142, 143 to a serving access node of the wireless network 100. The logic circuitry is further configured to control the UE to carry out any of the steps associated with the proposed solution as outlined herein.

[0037] The logic circuitry 210 may include a processing device 211, including one or multiple processors, microprocessors, data processors, co-processors, and / or some other type of component that interprets and / or executes instructions and / or data. The processing device 211 may be implemented as hardware (e.g., a microprocessor, etc.) or a combination of hardware and software (e.g., a system-on-chip (SoC), an applicationspecific integrated circuit (ASIC), etc.). The processing device 211 may be configured to perform one or multiple operations based on an operating system and / or various applications or programs.

[0038] The logic circuitry 210 may further include memory storage 212, which may include one or multiple memories and / or one or multiple other types of storage mediums. For example, the memory storage 212 may include a random access memory (RAM), a dynamic random access memory (DRAM), a cache, a read only memory (ROM), a programmable read only memory (PROM), flash memory, and / or some other type of memory. The memory storage 212 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, a solid state disk, etc.). The memory storage 212 is configured for holding computer program code, which may be executed by the processing device 211, wherein the logic circuitry 210 is configured to control the UE 10 to carry out any of the method steps as provided herein. Software defined by said computer program code may include an application or a program that provides a function and / or a process. The software may include device firmware, an operating system (OS), or a variety of applications that may execute in the logic circuitry 210.

[0039] Fig. 3 schematically illustrates a core network node 300 of the core network 110, configured to carry out the method steps as outlined. In some embodiments, the core network node 300 may be configured to implement a location node, such as a GMLC. In other embodiments, the core network node 300 may implement a network node for managing privacy information of UEs, such as a UDM, a UDR, or a combination of UDM and UDR. It shall also be noted that although the core network node 300 is depicted as a unit in Fig. 3 for the sake of simplicity, the elements included in the core network node 300 may be distributed in different network elements, such as in different databases and data memories, and various functions may be carried out in the cloud, i.e., in computing and storing resources distributed in different networks and / or locations and which may cooperate and be accessed via e.g., the Internet.

[0040] The core network node 300 comprises logic circuitry 310 configured to implement at least one network function of the core network node 300.

[0041] The logic circuitry 310 may include a processing device 311, including one or multiple processors, microprocessors, data processors, co-processors, and / or some other type of component that interprets and / or executes instructions and / or data. Processing device 311 may be implemented as hardware (e.g., a microprocessor, etc.) or a combination of hardware and software (e.g., a system-on-chip (SoC), an applicationspecific integrated circuit (ASIC), etc.). The processing device 311 may be configured to perform one or multiple operations based on an operating system and / or various applications or programs.

[0042] The logic circuitry 310 may further include memory storage 312, which may include one or multiple memories and / or one or multiple other types of storage mediums. For example, memory storage 312 may include a random access memory (RAM), a dynamic random access memory (DRAM), a cache, a read only memory (ROM), a programmable read only memory (PROM), flash memory, and / or some other type of memory. Memory storage 312 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, a solid state disk, etc.). The memory storage 312 is configured for holding computer program code, which may be executed by the processing device 311, wherein the logic 310 is configured to control the core network node 300 to carry out any of the method steps as provided herein. Software defined by said computer program code may include an application or a program that provides a function and / or a process. The software may include device firmware, an operating system (OS), or a variety of applications that may execute in the logic 310.

[0043] The core network node 300 further comprise an interface 313, configured for communication with other entities of the core network 110. In this context, the interface 313 may comprise a plurality of interfaces which are setup for communication with different network entities. By way of example, various interfaces of the interface 313 may be configured in accordance with the Architectural Reference Model described in section 4.2.1 of 3GPP specification TS 23.273. ver. 18.3.0, which shows interfaces for, inter alia, both GMLC and UDM.

[0044] The core network node 300 may in various examples further comprise a data storage 314, configured for storing data related to UEs of the wireless system. In some examples, the core network node 300 may be configured to implement UDM and / or UDR, and is configured to be responsible for storing, in the data memory 314, and managing, by the logic circuitry 310 subscriber data, including user profiles, authentication information, service profiles, and other relevant user-related information, associated with UEs. The core network node 300 may further allows for updates of data associated with the UEs in the data memory 314, such as to subscriber profiles, service subscriptions, and other user-related information, ensuring that the network remains up to date with user preferences and entitlements. In the context of the proposed solution, this involves storing, updating, and retrieving data comprising privacy profiles which indicate consent, or allowance, to share position information for a UE.

[0045] Fig. 4 provides a signaling diagram, in which various steps and aspects of embodiments of the proposed solution are shown. It shall be noted that only certain nodes of the core network 110 are shown, although further core network nodes implementing other functions may also be involved in the signaling according to legacy procedures, such as AMF and PCF. It may also be noted that wireless devices UE1, UE2, UE3 communicate with the core network 110 via radio communication over RAN 120. Nodes and functions that do not affect or play a relevant part in the context of the proposed solution are left out of Fig. 4 for the sake of simplicity.

[0046] The proposed solution relates to management and checking of privacy information related to at least one UE, such as UE1 and / or UE2, for the purpose of allowing a requesting entity, such as UE3, to obtain positioning information related to the at least one UE. In legacy procedures under the 3GPP, privacy check is executed by the GMLC by retrieving the UE LCS Privacy Policy Information from the subscription information (from the UDM) of the UE, such as UE1, for which positioning information is requested. The current Privacy Policy has basically three options:

[0047] 1. positioning allowed without notifying the UE user;

[0048] 2. positioning allowed with notification to the UE user;

[0049] 3. positioning not allowed;

[0050] There are some more variants, but in general this is the options available for a UE to set in the profile. The UEs can further update their privacy policy.

[0051] Without any changes to the specification, the only way to provide UE level consent is to use the option (2) where the network contacts the UE1 and ask if the requesting entity (UE3) is allowed to get the positioning information. This is an inefficient mechanism that may cause extensive signaling in the network and increases the power consumption in the UE (UE1 / UE2) which needs to consent on UE level on each occasion.

[0052] To overcome this problem, and here specifically exemplified for UE1 unless where both UE1 and UE2 are mentioned, it is hereby proposed that the privacy profile related to the UE1 shall be expanded to also keep a list of other entities, such as other UEs, that are allowed to get the position information of the UEl / subscriber. In this context, it may be noted that UE1 and UE2 are configured with separate privacy profiles, which both may comprise a respective list of entities allowed to obtain positioning information of that UE.

[0053] According to one aspect, a further Privacy Policy option is proposed which in some form or shape provides the effect of: “Positioning allowed, without notification, by entities comprised in list of allowed entities”.

[0054] According to another aspect of the proposed solution, the UE1 or an AF 106 can update the profile to manage the list of entities (e.g., other UEs such as UE3) which are allowed (has consent by the UE1) to receive position information of the UEl / subscriber.

[0055] According to another aspect of the proposed solution, when a user / UE / Subscriber related to UE1 accepts the UE3, the UE3 is added to the list in the privacy profile, in privacy information stored in the core network 110. According to another aspect, the identity of an allowed requesting entity, such as UE3, which is stored in the privacy profile can be one or more of SUPI / GPSI / MSISDN / Application Layer ID.

[0056] According to another aspect, the identity of an allowed requesting entity may be indicative of a group of requesting entities, such as a group ID, or a type of requesting entity, such as a type ID. In this context, a UE (e.g., UE1) may be configured to provide consent, to be stored in the core network, to allow any of member of that group or type to obtain its positioning information.

[0057] According to another aspect, the consent stored in the core network may be conditional, based on e.g., location area (country, town, building etc.) or time (time of day or year, or duration of allowance).

[0058] According to another aspect, the identity of an allowed requesting entity may identify an allowed AF or LCS client. A further example to a LCS client is a network function in the 3GPP network. LCS client can be a NF or an AF.

[0059] Returning to Fig. 4, various steps and aspects of different examples of the proposed solution will now be described, with reference to the numerals given in the drawing. Reference is made to requests for, and obtainment of, positioning information related to at least one UE (UE1 and / or UE2). In various examples, this positioning information may comprise Ranging / SL positioning information, related to UE1 and / or UE2.

[0060] 401. At any given time, the UE1 and UE2 can independently update its privacy information, such as its LCS Privacy Profile, corresponding to what is stated in TS 23.273 clause 5.4. Specifically, in addition to what legacy procedures provide, it is here proposed that each UE can include in, and update, its privacy information with a list of requesting entities, such as other UEs, AFs, or LCS clients, that are allowed / have consent by that UE to retrieve location information. Such an update may involve (for the example of UE1) the UE1 sending a NAS (Non Access Stratum) message to the AMF, which will forward this to the PCF which updates the UE LCS Privacy Profile in the UDR.

[0061] 402. At any given time, the AF, via the NEF, can update the privacy information for e.g., UE1 or UE2, such as the respective UE LCS Privacy Profiles, corresponding to what is stated in TS 23.273 clause 5.4. Specifically, in addition to what legacy procedures provide, it is here proposed that the UE LCS privacy profile may be provided with or updated with a list of requesting entities, such as UEs, AFs, or LCS clients, that are allowed / have consent by the UE (UE1 / UE2) to retrieve location information.

[0062] In some examples, the update of the privacy information according to step 401 or 402 may be triggered by determining an update of identities of entities which are allowed to obtain positioning information related to the UE, such as by adding new entities to a group of trusted devices. In some examples, the update may be caused by user interaction with the UE. In other examples, the update may be automatically triggered, e.g., upon subscribing to an application service or responsive to the UE being added to a group of users (e.g., a private or corporate group) with a predetermined rule to allow positioning within the group.

[0063] 403. This step indicates receiving a message in a location node, such as the GMLC, identifying a requesting entity, wherein the message is indicative of a request for positioning information related to at least one UE, e.g., UE1 and / or UE2. In this example, the positioning request originates from an application, as identified by the AF. In some examples, the message is sent by the AF, and is indicative of a request to retrieve Ranging / SL positioning information related to UE1 and UE2. The request may go via the NEF to the GLMC. The request may identify the requesting entity, such as an ID uniquely identifying the AF or an LCS client. In some examples, the AF sending the request is also the requesting entity. An ID of the AF may be provided in the request by the AF or be added by the NEF.

[0064] 404. This step is alternative to step 403, and also indicates receiving a message in a location node, such as the GMLC, identifying a requesting entity, wherein the message is indicative of a request for positioning information related to at least one UE, e.g., UE1 and / or UE2. In this example, the positioning request originates from the UE3, and is indicative of a request to retrieve Ranging / SL positioning information related to UE1 and UE2. The request may go via the NEF to the GLMC (over the user plane) or go via the AMF to the GLMC (over the control plane). The request identifies the UE3 as the requesting entity. An ID of the UE3 may be provided in the request by the UE3 or be added by the NEF or the AMF.

[0065] 405. This step indicates that the location node retrieves privacy information of the at least one UE, responsive to receiving the message in step 403 or 404, wherein the privacy information is stored in the core network. The location node, such as GMLC, may use a service API (Application Programming Interface) to retrieve the privacy information, such as the UE LCS Privacy Profile, from storage. The privacy information may be stored in a network node of the core network, such as the UDR, or cashed in the UDM. The drawing shows the example of the GMLC retrieving the UE LCS Privacy Profile from the UDM, corresponding to what is specified in TS 29.503 clause 5.2.2.2.15, wherein the UDM fetches the stored profile from the UDR.

[0066] In an alternative example, the retrieving of privacy information in step 405 comprises a query, sent by the location node (GMLC) to the network node (e.g., the UDM) which is configured to manage the stored privacy information, wherein said query identifies the requesting entity (e.g., UE3), in addition to identifying the at least one UE (UE1 and / or UE2) for which positioning information is requested by the requesting entity (UE3). The query may e.g., comprise an ID of the requesting entity. In response to the query the location node receives a response message from the network node (UDM). The response message, which in this example constitutes the retrieved privacy information, may comprise an indication of positive outcome, such as an ACK or a flag or other data indicative of positive outcome, if the requesting entity is identified as an allowed entity in the stored privacy information of the at least one UE. The response may comprise an indication of negative outcome, such as a NACK or a flag or other data indicative of negative outcome, if the requesting entity is not identified as an allowed entity in the stored privacy information. In one example, a single query may be sent, identifying all of the at least one UE (UE1 and / or UE2) for which positioning information is requested. Alternatively, separate queries are transmitted, associated with each one of the at least one UE (UE1 and / or UE2) for which positioning information is requested. In any of these two examples, a single response or separate responses may be obtained in the location node.

[0067] 406. In this step the location node performs a check to determine whether the identification of the requesting entity is comprised in the stored privacy information. In one example, the GMLC may check the Privacy profile of all of the at least one UE identified in the request of step 403 or 404, i.e., UE1 and / or UE2, to check whether the requesting entity (AF, LCS client or UE3) is an allowed entity in the respective list.

[0068] With reference to the alternative example in step 405, the check may comprise determining whether the retrieved privacy information, i.e., the response message, is indicative of a positive outcome response. In other words, that a response message has been received from the network node (UDM), indicating that identification of the requesting entity is comprised in the stored privacy information for all of the at least one UE (UE1 and / or UE2).

[0069] In the context of the proposed solution as described herein, an allowed entity is an entity identified in the privacy information of a UE (such as UE1 or UE2) as being allowed to obtain positioning information related to that UE. The check may thus comprise determining whether an ID of the requesting entity (UE3) is comprised in the retrieved UE LCS Privacy Profile, such as in a list of IDs of entities allowed to obtain positioning information related to the UE.

[0070] If the determination has a positive outcome, i.e., that the ID of the requesting entity is listed in the privacy information for each of the at least one UE, the process moves to step 410.

[0071] If the determination has negative outcome, i.e., that the ID of the requesting entity is not listed in the privacy information for each of the at least one UE, the process may move to step 407 to obtain and store further consent. In an alternative example, e.g., where a UE (e.g., UE1) has not configured its UE LCS Privacy Profile to indicate that positioning may be allowed based on notification (see bullet 2 above), the process positioning may be terminated. This may include sending of a message identifying rejection of the request 403 / 404 in step 411 / 412 described below.

[0072] 407. This step indicates an example of further action taken if the check in step 406 has negative outcome, i.e., that the ID of the requesting entity is not listed in the privacy information for each of the at least one UE. In this scenario, the location node, e.g., GMLC, may trigger a notification to each of the at least one UE for which the requesting entity is not listed as an allowed entity. The notification may be sent via the AMF. The notification serves to check if the notified UE(s) can provide consent for the requesting entity. This may involve user interaction. The notification(s) sent in step 407 comprises an identification of the requesting entity, such as an ID of the UE3, a subscriber name, an application name, or other.

[0073] 408. This step indicates that the notified UE(s), UE1 and / or UE2, responds to the notification message of step 407 with a consent message. Here, the respective notified UE (UE1 or UE2) may provide consent to allow the requesting entity, i.e., to share positioning information with the requesting entity. If the consent message indicates no consent, or if a consent response is not received for all notified UE(s), or if consent is not given for all notified UE(s), the request for positioning information is rejected. In this scenario, a message indicating the rejection may be provided in step 411 and / or 412.

[0074] 409. This step indicates that consent was obtained in the location node from all at least one of the notified UE(s). The location node then stores the identification of the requesting entity in the privacy information for the consenting UE. In one example, this may involve the GMLC triggering update to the UE LCS Privacy Profile to add UE3 or the AF or LCS client to the list of allowed entities in the UE LCS Privacy Profile stored in UDM / UDR.

[0075] 410. This step indicates that the location node obtains the position information as requested in step 403 or 404. In the shown example, this may involve executing a positioning procedure to produce the positioning information. This is as such not specific to the proposed solution, and may include any legacy positioning mechanism, such as executing Ranging / Sidelink positioning procedures. In other examples, the requested positioning information may already be stored in a database accessible by the location node, such as in a location server. In such an example, obtaining the positioning information may comprise retrieving stored positioning information.

[0076] 411. This step indicates that the location node, e.g., GMLC, sends a positioning information message in response to the request message 404, i.e., to the requesting entity being the UE3. Where obtainment of location information is allowed and completed, the response message may comprise the obtained positioning information. Otherwise, the positioning information message may identify rejection of the request 404.

[0077] 412. This step indicates that the location node, e.g., GMLC, sends a positioning information message in response to the request message 403, i.e., to the requesting entity being the AF. Where obtainment of location information is allowed and completed, the response message may comprise the obtained positioning information. Otherwise, the positioning information message may identify rejection of the request 403.

[0078] One aspect of the proposed solution is related to operation of the location node 300 of a core network 110, which location node may be a GMLC 102. With reference to Fig. 3, and where the shown core network node 300 implements the location node, the location node comprises a communication interface 313 and logic circuitry 310. The location node is configured to carry out the following steps, by operation of the logic circuitry:

[0079] Receiving a message identifying a requesting entity, wherein the message is indicative of a request for positioning information related to at least one UE. This may involve some of the aspects outlined with respect to steps 403, 404 outlined above.

[0080] Retrieving, based on receiving the message, privacy information of the at least one UE, wherein the privacy information is stored in the core network. This may involve some of the aspects outlined with respect to steps 405 to 409 outlined above.

[0081] Upon the retrieved privacy information comprising identification of the requesting entity as being allowed to obtain positioning information related to the at least one UE, obtaining the position information, and transmitting the obtained position information to the requesting entity. This may involve some of the aspects outlined with respect to steps 410 to 412 outlined above. Upon the retrieved privacy information not comprising identification of the requesting entity as being allowed to obtain positioning information related to each of the at least one UE, the location node may reject the request for positioning information, and optionally notify the requesting entity of the rejection.

[0082] Another, related, aspect of the proposed solution is related to operation of a network node 300 of a core network 110, which network node may be a UDM 103 or a UDR 104 or comprise both functions. With reference to Fig. 3, and where the shown core network node 300 implements functions according to this aspect, the network node 300 comprises at least memory storage 314 configured to store privacy information of one or more UEs, wherein the stored privacy information is configured to comprises identity information of entities allowed to obtain positioning information related to the respective one or more UEs. Storing, including updating, of such identity information may be carried out as outlined above with reference to steps 401, 402, or 409. The network node further comprises an interface 313 for providing a network function access to retrieve the stored privacy information. Retrieving may be carried out in accordance with step 405 outlined above, wherein the retrieving network function may be implemented by the location node 102.

[0083] Another, related, aspect of the proposed solution is related to method carried out in a network node 300, which may be implementing UDM and / or UDR, for managing privacy information related to UEs. The method comprises storing privacy information of at least one UE, wherein the stored privacy information is configured to comprises identity information of entities (UE3, AF) allowed to obtain positioning information related to the respective at least one UE. The method further comprises providing access for a network function to retrieve the stored privacy information. The stored privacy information may, for each of the at least one UE, comprise a list of identities of entities (UE3, AF) allowed to obtain positioning information for that UE. The method may further receive an update instruction (401, 402, 409) to the identity information of entities (UE3, AF) allowed to obtain positioning information, such as addition, change, or cancellation of identification of one or more entities lowed to obtain positioning information for that UE, and to store the privacy information in accordance with the update instruction. The method may further comprise receiving a request to retrieve privacy information related to at least one UE, and outputting privacy information based on the request, e.g., as described with reference to step 405 above. In some examples, the output privacy information may comprise a list of identities of entities allowed to obtain positioning information for a UE identified in the request. In other examples, the output privacy information may comprise an indication of whether a UE identified in the request is comprised in a list of identities of entities allowed to obtain positioning information for that UE, in the stored privacy information. The network node 300 described in the preceding paragraph may be configured to carry out any of these method steps.

[0084] A further, related, aspect of the proposed solution is related to operation of an entity configured to operate in a wireless system, for managing access to privacy information for a UE. In this context, this entity may be the UE itself, or another entity such as an LCS client or an AF which owns or controls the privacy information related to the UE. The entity may comprise an interface, such as a transceiver 213 in the case of a UE, or a core network communication interface in the case of an LCS client or an AF. The entity is configured to transmit a message to a core network node of the core network, wherein said message comprises a request for storing, in the core network, identification of further entities being allowed to obtain positioning information related to the UE. This may be carried out in accordance with any of steps 401, 402 or 408 outlined above.

[0085] An effect of the mechanism in accordance with these aspects, by providing central storage of the privacy information comprising identity information of entities allowed to obtain positioning information, is that signaling to obtain consent for obtaining positioning information may be reduced, which improves resource efficiency (i.e., use of radio resources) in the wireless system and improves ability for UEs to conserve battery charge.

[0086] In one example of the proposed solution, an improved mechanism is set out in a 5G wireless system. This may include updated Procedure for Ranging / SL Positioning service exposure through 5GC network via control plane, as provided in TS 23.586 section 6.7.1.2.3. When a SL Positioning Client UE (UE3) performs the procedure and GMLC, in step 4 of that section, performs the Privacy check, it is proposed that the GMLC checks whether the ID of the SL Positioning Client UE is in the Privacy Profile of both UE1 and UE2. If so, the UE level privacy is confirmed. If the ID is not in the profile, then the GMLC could either notify each UE1 and UE2 and check if the Client UE (UE3) is allowed (UE1 and UE2 give their consent), or the GMLC could immediately reject the request based on the missing privacy consent in the profile.

[0087] Various aspects of the proposed solution have been outlined in the foregoing. The proposed solution may be embodied in accordance with any of those aspects and may comprise features of any of the items listed below.

[0088] Item 1. A method for managing location services in a core network configured to provide wireless services to user equipment, UE, wherein the method is carried out in a location node and comprises: receiving (403, 404) a message, identifying a requesting entity, wherein the message is indicative of a request for positioning information related to at least one UE; retrieving (405), based on receiving the message, privacy information of the at least one UE, wherein the privacy information is stored in the core network; upon the retrieved privacy information comprising identification of the requesting entity as being allowed to obtain positioning information related to the at least one UE: obtaining (410) the position information, and transmitting (411) the obtained position information to the requesting entity.

[0089] Item 2. The method of item 1, wherein the privacy information comprises, for each of the at least one UE, a list of one or more identities of entities allowed to obtain positioning information.

[0090] Item 3. The method of item 2, wherein each identity is indicative of at least one of: one requesting entity, a group of requesting entities, a type of requesting entity. Item 4. The method of any preceding item, wherein the requesting entity is an application function, AF.

[0091] Item 5. The method of any of items 1-4, wherein the requesting entity is a UE.

[0092] Item 6. The method of any of items 1-5, wherein the obtaining is carried out responsive to determining (406) that the identification of the requesting entity is comprised in the stored privacy information.

[0093] Item 7. The method of any of items 1-5, wherein the obtaining is carried out responsive to: obtaining (408) consent to allow the requesting entity, and storing (409) the identification of the requesting entity in the privacy information.

[0094] Item 8. The method of any preceding item, wherein the request for positioning information comprises a request for a relative position or an absolute position of the at least one UE.

[0095] Item 9. The method of any preceding item, wherein obtaining the positioning information comprises retrieving stored positioning information or executing a positioning procedure to produce the positioning information.

[0096] Item 10. A location node (GMLC) of a core network (110) which is configured to provide wireless services to user equipment, UE, wherein the location node comprises: a communication interface (313); and logic circuitry (310), configured to: receive, through the communication interface, a message identifying a requesting entity (UE3, AF), wherein the message is indicative of a request for positioning information related to at least one UE (UE1, UE2); retrieve, based on the received message, privacy information of the at least one UE, wherein the privacy information is stored in the core network; upon the retrieved privacy information comprising identification of the requesting entity as an entity being allowed to obtain positioning information related to the at least one UE: obtain the position information, and transmit the obtained position information to the requesting entity.

[0097] Item 11. The location node of item 10, wherein the logic circuitry is further configured to operate in accordance with any of items 2-9. Item 12. A network node (UDM / UDR) of a core network (110) which is configured to provide wireless services to user equipment, UE, wherein the network node comprises: memory storage (314) configured to store privacy information of at least one UE, wherein the stored privacy information is configured to comprises identity information of entities (UE3, AF) allowed to obtain positioning information related to the respective at least one UE; and an interface (313) for providing access for a network function to retrieve the stored privacy information.

[0098] Item 13. The network node of item 12, wherein the privacy information, for each of the at least one UE, comprises a list of one or more identities of entities allowed to obtain positioning information related to that UE.

[0099] Item 14. The network node of item 12 or 13, wherein at least one of said entities is a UE (UE3) or an application function, AF.

[0100] Item 15. The network node of any of items 12-14, wherein said interface further provides an input for receiving and storing said identity information.

[0101] Item 16. A method for managing access to privacy information for a user equipment, UE, configured for wireless communication with a core network, wherein the method comprises: transmitting (401, 402, 408), from an entity which controls privacy information of the UE, a message to a core network node of the core network; wherein said message comprises a request for storing, in the core network, identification of further entities being allowed to obtain positioning information related to the UE.

[0102] Item 17. The method of item 16, comprising: determining an update of identities of entities which are allowed to obtain positioning information related to the UE, wherein the message is transmitted based on said update.

[0103] Item 18. The method of item 16, comprising: receiving (407), from a location node of the core network node, a notification of a positioning request by at least one identified entity; wherein the message is transmitted (408) responsive to said notification and indicates whether the at least one identified entity is to allowed to obtain positioning information related to the UE.

[0104] Item 19. The method of any of items 16-18, wherein said entity is an application function, AF.

[0105] Item 20. The method of any of items 16-19, wherein said entity is said UE.

[0106] Item 21. The method of any of items 16-20, wherein the privacy information comprises a list of one or more identities of entities allowed to obtain positioning information.

[0107] Item 22. The method of item 21, wherein each identity is indicative of at least one of: one requesting entity, a group of requesting entities, a type of requesting entity.

[0108] Item 23. A method for managing privacy information related to UEs, wherein the method is carried out in a network node (UDM / UDR) of a core network, wherein said method comprises: storing privacy information of at least one UE, wherein the stored privacy information is configured to comprises identity information of entities (UE3, AF) allowed to obtain positioning information related to the respective at least one UE; and providing access for a network function (GMLC) to retrieve the stored privacy information.

[0109] Item 24. The method of item 23, wherein the stored privacy information comprises, for each of the at least one UE, a list of identities of entities (UE3, AF) allowed to obtain positioning information for that UE.

[0110] Item 25. The method of item 23 or 24, comprising: receiving an update instruction (401, 402, 409) to the identity information of entities (UE3, AF) allowed to obtain positioning information; and storing the privacy information in accordance with the update instruction.

[0111] Item 26. The method of any of items 23-25, comprising: receiving a request to retrieve privacy information related to at least one UE, and outputting privacy information based on the request,

[0112] Item 27. The method of item 26, wherein the output privacy information comprises a list of identities of entities allowed to obtain positioning information for a UE identified in the request. Item 28. The method of item 26, wherein the output privacy information comprises an indication of whether a UE identified in the request is comprised in a list of identities of entities allowed to obtain positioning information for that UE, in the stored privacy information.

Claims

CLAIMS1. A method for managing location services in a core network configured to provide wireless services to user equipment, UE, wherein the method is carried out in a location node and comprises: receiving (403, 404) a message, identifying a requesting entity, wherein the message is indicative of a request for positioning information related to at least one UE; retrieving (405), based on receiving the message, privacy information of the at least one UE, wherein the privacy information is stored in the core network; upon the retrieved privacy information comprising identification of the requesting entity as being allowed to obtain positioning information related to the at least one UE: obtaining (410) the position information, and transmitting (411) the obtained position information to the requesting entity.

2. The method of claim 1, wherein the privacy information comprises, for each of the at least one UE, a list of one or more identities of entities allowed to obtain positioning information.

3. The method of claim 2, wherein each identity is indicative of at least one of: one requesting entity, a group of requesting entities, a type of requesting entity.

4. The method of any preceding claim, wherein the requesting entity is an application function, AF.

5. The method of any of claims 1-4, wherein the requesting entity is a UE.

6. The method of any of claims 1-5, wherein the obtaining is carried out responsive to determining (406) that the identification of the requesting entity is comprised in the stored privacy information.

7. The method of any of claims 1-5, wherein the obtaining is carried out responsive to: obtaining (408) consent to allow the requesting entity, andstoring (409) the identification of the requesting entity in the privacy information.

8. The method of any preceding claim, wherein the request for positioning information comprises a request for a relative position or an absolute position of the at least one UE.

9. The method of any preceding claim, wherein obtaining the positioning information comprises retrieving stored positioning information or executing a positioning procedure to produce the positioning information.

10. A location node (GMLC) of a core network (110) which is configured to provide wireless services to user equipment, UE, wherein the location node comprises: a communication interface (313); and logic circuitry (310), configured to: receive, through the communication interface, a message identifying a requesting entity (UE3, AF), wherein the message is indicative of a request for positioning information related to at least one UE (UE1, UE2); retrieve, based on the received message, privacy information of the at least one UE, wherein the privacy information is stored in the core network; upon the retrieved privacy information comprising identification of the requesting entity as an entity being allowed to obtain positioning information related to the at least one UE: obtain the position information, and transmit the obtained position information to the requesting entity.

11. The location node of claim 10, wherein the logic circuitry is further configured to operate in accordance with any of claims 2-9.

12. A network node (UDM / UDR) of a core network (110) which is configured to provide wireless services to user equipment, UE, wherein the network node comprises: memory storage (314) configured to store privacy information of at least one UE, wherein the stored privacy information is configured to comprises identity informationof entities (UE3, AF) allowed to obtain positioning information related to the respective at least one UE; and an interface (313) for providing access for a network function to retrieve the stored privacy information.

13. The network node of claim 12, wherein the privacy information, for each of the at least one UE, comprises a list of one or more identities of entities allowed to obtain positioning information related to that UE.

14. The network node of claim 12 or 13, wherein at least one of said entities is a UE (UE3) or an application function, AF.

15. The network node of any of claims 12-14, wherein said interface further provides an input for receiving and storing said identity information.

16. A method for managing access to privacy information for a user equipment, UE, configured for wireless communication with a core network, wherein the method comprises: transmitting (401, 402, 408), from an entity which controls privacy information of the UE, a message to a core network node of the core network; wherein said message comprises a request for storing, in the core network, identification of further entities being allowed to obtain positioning information related to the UE.

17. The method of claim 16, comprising: determining an update of identities of entities which are allowed to obtain positioning information related to the UE, wherein the message is transmitted based on said update.

18. The method of claim 16, comprising: receiving (407), from a location node of the core network node, a notification of a positioning request by at least one identified entity;wherein the message is transmitted (408) responsive to said notification and indicates whether the at least one identified entity is to allowed to obtain positioning information related to the UE.

19. The method of any of claims 16-18, wherein said entity is an application function, AF.

20. The method of any of claims 16-19, wherein said entity is said UE.

21. The method of any of claims 16-20, wherein the privacy information comprises a list of one or more identities of entities allowed to obtain positioning information.

22. The method of claim 21, wherein each identity is indicative of at least one of: one requesting entity, a group of requesting entities, a type of requesting entity.

23. A method for managing privacy information related to UEs, wherein the method is carried out in a network node (UDM / UDR) of a core network, wherein said method comprises: storing privacy information of at least one UE, wherein the stored privacy information is configured to comprises identity information of entities (UE3, AF) allowed to obtain positioning information related to the respective at least one UE; and providing access for a network function (GMLC) to retrieve the stored privacy information.

24. The method of claim 23, wherein the stored privacy information comprises, for each of the at least one UE, a list of identities of entities (UE3, AF) allowed to obtain positioning information for that UE.

25. The method of claim 23 or 24, comprising: receiving an update instruction (401, 402, 409) to the identity information of entities (UE3, AF) allowed to obtain positioning information; and storing the privacy information in accordance with the update instruction.

26. The method of any of claims 23-25, comprising: receiving a request to retrieve privacy information related to at least one UE, and outputting privacy information based on the request,27. The method of claim 26, wherein the output privacy information comprises a list of identities of entities allowed to obtain positioning information for a UE identified in the request.

28. The method of claim 26, wherein the output privacy information comprises an indication of whether a UE identified in the request is comprised in a list of identities of entities allowed to obtain positioning information for that UE, in the stored privacy information.

Images