User plane protocol for location services control based on PS data off

Abstract

Methods and apparatus are provided to handle PS Data off for Location services provided over User plane connection (i.e., provided as a PS service) of packet data connection at the UE and location management function. The method performed by the UE comprises receiving from a network node (location management function), a request to setup User Plane (UP) connection for UP Protocol for location services (LCS-UPP) with LCS-UPP being a packet switched service and sending in response to the request a failure message comprising a failure cause when a Packet Switched (PS) Data off status in the wireless device is activated, wherein the PS Data off status activated indicates that transmission of data packets is prevented.

Description

User Plane Protocol for Location services control based on PS data offRelated Applications

[0001] This application claims the benefit of provisional patent application serial number 63 / 681922, filed on 8 / 12 / 2024, the disclosure of which is hereby incorporated herein by reference in its entirety.Technical Field

[0002] The present disclosure relates to a cellular communications system and, more particularly, to management of location services and packet services data off.Background

[0003] The 3rd Generation Partnership Project (3GPP) specifications define a Packet Switched (PS) Data Off feature for cellular networks. When configured by the Home Public Land Mobile Network (HPLMN) and activated by the user, this feature prevents the transport of all data packets via Packet Data Network (PDN) connections or Protocol Data Unit (PDU) sessions in 3GPP access networks, except for Internet Protocol (IP) packets required by 3GPP PS Data Off Exempt Services.

[0004] The 3GPP PS Data Off Exempt Services are configured in the User Equipment (UE) by the HPLMN. These exempt services may include various operator services such as MMTel Voice, SMS over IMS, and device management over PS, among others. When 3GPP PS Data Off is activated, the UE informs the network of this status. Subsequently, both the UE and the network cease sending uplink and downlink IP packets for services that are not exempt.

[0005] The 3GPP Location Services (LCS)-User Plane Protocol (UPP) utilizes IP packets to transfer location supplementary services messages and Long Term Evolution (LTE) Positioning Protocol (LPP) messages. These messages are transmitted via a user plane connection between a UE and a Location Management Function (LMF). The LCS-UPP supports the transport of LPP messages and specific location supplementary services messages.

[0006] Currently, the 3GPP specifications do not provide a mechanism for the LMF to be aware of the user's 3GPP PS Data Off status. This lack of awareness can lead to situations where the LMF may attempt to set up LCS secured user planeconnections for UEs with activated 3GPP PS Data Off, potentially resulting in unsuccessful connection attempts or inconsistencies in service delivery.

[0007] The interaction between the 3GPP PS Data Off feature and location services, particularly those utilizing the user plane protocol, presents challenges in ensuring consistent and efficient service delivery while respecting the user's data preferences and network configurations.***** START EXCERPT FROM 3GPP TS 22.011 *****10 3GPP PS Data Off10.1 Description3 GPP PS Data Off is a feature which, when configured by the HPLMN and activated by the user, prevents transport via PDN connections in 3 GPP access networks of all data packets except IP packets required by 3 GPP PS Data Off Exempt Services.10.2 RequirementsThe 3 GPP system shall provide a mechanism by which an operator can configure which operator services are defined as 3 GPP PS Data Off Exempt Services for their own subscribers.When 3 GPP PS Data Off is activated in the UE, in order to preserve charging consistency:- the UE shall inform the network that 3 GPP PS Data Off is activated,- the UE shall cease the sending of uplink IP Packets of all services that are not 3 GPP PS Data Off Exempt Services via PDN connections in 3 GPP access networks,- the network shall cease the sending of downlink IP Packets to the UE for all services that are not 3 GPP PS Data Off Exempt Services via PDN connections in 3 GPP access networks,- the UE shall cease the sending of uplink traffic over non- IP PDN types via PDN connections in 3 GPP access networks, and- the network shall cease the sending of downlink traffic over non-IP PDN types via PDN connections in 3 GPP access networks.NOTE 1 : Disabling of traffic on both the uplink and downlink is needed in order to provide consistency of charging between HPLMN and VPLMN, as well as consistency between what the user expects and what the user may be billed for.Each of the following operator services shall be configurable by the HPLMN operator to be part of the 3 GPP PS Data Off Exempt Services:- MMTel Voice;- SMS over IMS;- USSD over IMS (USSI);- MMTel Video;- Particular IMS services not defined by 3 GPP, where each such IMS service is identified by an IMS communication service identifier;- Device Management over PS- Management of USIM files over PS (e.g. via Bearer Independent Protocol); and- IMS Supplementary Service configuration via the Ut interface using XCAP.3 GPP PS Data Off may be activated based on roaming status, and the HPLMN may configure up to two sets of 3GPP PS Data Off Exempt Services for its subscribers: one is used when in HPLMN and another when roaming.NOTE 2: The updating to the sets of configured 3 GPP Data Off Exempt Services in the VPLMNs and HPLMN is not guaranteed to take effect in real time. The updating to the sets of configured 3 GPP Data Off Exempt Services in the UEs is not guaranteed take effect in real time.The user should be made aware of the operator services that are 3 GPP PS Data Off Exempt Services.NOTE 3 : The system can support falling back to operate over the CS domain in case an operator service is not configured to be a 3 GPP PS Data Off Exempt Service and an equivalent CS domain operator service exists for the operator service.*****EN DEXCERPT FROM 3GPP TS 22.011 *****

[0008] According to some embodiments described in the context of 5G Service Based Architecture, a method performed by a wireless communication device (112) is provided. The method comprises the step of receiving, from a network node (e.g., Location Management Function (LMF), a request to setup User Plane (UP) connection for UP Protocol for location services (LCS-UPP) and the step of sending in response to the request a failure message comprising a failure cause when the UE determined that a Packet Switched (PS) Data off status in the wireless device is activated, wherein PS Data off status activated indicates that transmission of data packets is prevented.

[0009] For example, the method further comprises the step of determining by the wireless communication device that LCS-UPP service is not included in PS Data off list of exempted services when sending the failure message, hence LCS-UPP service is not an exempted service.

[0010] According to another embodiment, a method performed by the wireless communication device is provided. The method comprises the step of upon determining that a Packet Switched (PS) Data off status is activated and a User Plane (UP) connection for location services is setup with a network node, the wireless device performs the step of sending a release message to the network node(LMF) to release the UP connection and wherein the release message includes a corresponding failure cause as a result of PS data off being now activated.

[0011] According to an embodiment, a wireless communication device adapted to perform any of the wireless communication devices embodiments herein.

[0012] According to other embodiments, a wireless communication device comprising one or more transmitters, one or more receivers and processing circuity associated with one or more transmitters and the one or more receivers, the processing circuitry configured to cause the wireless communication device to perform any of the wireless communication device embodiments herein.

[0013] According to some embodiments, a method performed by a network node implementing a Location Management Function in a wireless communication system such as 5G or 6G or other similar systems), the method comprising the step of receiving information indicative that PS DATA off status for a User Equipment (UE) is activated from either a network function within the system (for e.g., Session Management Function (SMF) associated to a Packet Data Session established by the UE with the SMF) or from the UE, and performing one or more actions which include determining whether to refrain from using user plane protocol for location services (LCS-UPP) procedures with the UE while Packet Switched (PS) DATA OFF status is activated for the UE and use control plane location procedures instead with the UE when required.

[0014] For example, the information is obtained from the UE in response to sending a User Plane (UP) Connection establishment request by the Location Management Function to the UE, and the LMF obtains in a response from the UE a failure cause due to failure to establish the UP connection when PS DATA off status is activated at the UE.

[0015] For example, the information is a release cause obtained from the UE in a UP connection release message, initiated by the UE in response to the PS DATA off status change at the UE from deactivated to activated to release an existing UP connection with the Location Management Function.

[0016] For example, determining whether to refrain from using user plane protocol for location services (LCS-UPP) procedures with the UE while PS DATA OFF status is activated for the UE further comprises one of the following steps: refrainingfrom using LCS-UPP procedures with the UE when LMF determines that LCS-UPP is not included in a PS DATA off exempt list of services, or using LCS-UPP procedures with the UE when LMF determines that LCS-UPP is included in a PS DATA off exempt list of services.

[0017] For example, the one or more actions described above further comprises releasing a UP connection with the UE if one exists or not establishing a UP connection with the UE for LCS-UPP.

[0018] According to some embodiments, a network node in a wireless communication system is provided, wherein the network device is adapted to perform any one of the embodiments described herein.

[0019] According to some embodiments, a network node in a wireless communication system is provided, wherein the network node comprises processing circuitry configured to cause the network node to perform any one of the embodiments described herein.Brief Description of the DrawingsThe accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0020] Figure 1 illustrates one example of a cellular communications system 100 in which embodiments of the present disclosure may be implemented;

[0021] Figures 2 and 3 illustrate example embodiments of the cellular communication system of Figure 1;

[0022] Figure 4 (prior art) illustrate example of LCS-UPP procedure between LMF and UE;

[0023] Figures 5A to 5H illustrates different examples of embodiments of notifying PS DATA off status for using or not using LCS UPP in accordance with few embodiments;

[0024] Figure 6 is a flow chart of a method in a network node implementing an LMF in accordance with the embodiments herein;

[0025] Figure 7 is a flow chart of a method in a wireless device / UE in accordance with the embodiments herein;

[0026] Figures 8, 9 and 10 are schematic block diagrams of example embodiments of a network node.

[0027] Figures 11, 12 are schematic block diagrams of example embodiments of a wireless device.Detailed Description

[0028] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0029] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0030] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

[0031] Radio Node: As used herein, a "radio node" is either a radio access node or a wireless communication device.

[0032] Radio Access Node: As used herein, a "radio access node" or "radio network node" or "radio access network node" is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and / or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station (e.g., a network node that implements a gNB Central Unit (gNB-CU) or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node.

[0033] Core Network Node: As used herein, a "core network node" is any type of node in a core network or any node that implements a core network function. The node can be a server or system of distributed servers. Some examples of a core network node include, e.g., an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Short message service function (SMSF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), a Network slice Admission Control function (NSACF) or the like. The Core network functions may be virtualized / containerized on a node, server, distributed servers, or implemented as a dedicated function on a dedicated physical node (compute, memory, and network). Other future core network functions in future core networks such as 6G and beyond are also applicable for this invention.

[0034] Communication Device: As used herein, a "communication device" is any type of device that has access to an access network. Some examples of a communication device include, but are not limited to: mobile phone, smart phone,sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC). The communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and / or data via a wireless or wireline connection.

[0035] Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of a wireless communication device include, but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (loT) device. Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC. The wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and / or data via a wireless connection. In this document, wireless communication device and UE are interchangeable.

[0036] Network Node: As used herein, a "network node" is any node that is either part of the RAN or the core network of a cellular communications network / system.

[0037] Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.

[0038] Note that, in the description herein, reference may be made to the term "cell"; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.

[0039] Figure 1 illustrates one example of a cellular communications system 100 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communications system 100 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC); however, the present disclosure is not limited thereto. In this example, the RAN includes base stations 102-1 and 102-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC), controlling corresponding (macro) cells 104-1 and 104-2. The base stations 102-1 and 102-2 are generally referred to herein collectively as base stations 102 and individually as base station 102. Likewise, the (macro) cells 104-1 and 104-2 are generally referred to herein collectively as (macro) cells 104 and individually as (macro) cell 104. The RAN may also include a number of low power nodes 106-1 through 106-4 controlling corresponding small cells 108-1 through 108-4. The low power nodes 106-1 through 106-4 can be small base stations (such as pico or femto base stations) or RRHs, or the like. Notably, while not illustrated, one or more of the small cells 108-1 through 108-4 may alternatively be provided by the base stations 102. The low power nodes 106-1 through 106-4 are generally referred to herein collectively as low power nodes 106 and individually as low power node 106. Likewise, the small cells 108-1 through 108-4 are generally referred to herein collectively as small cells 108 and individually as small cell 108.

[0040] In particular when the NG-RAN consists of gNBs (5G or beyond) connected to the 5GC through the NG interface, a gNB may further consist of a gNB-control unit (CU) and one or more gNB-Distribution Unit(s) (DU(s)). A gNB-CU and a gNB-DU is connected via Fl interface as illustrated in Figure 1A.

[0041] The cellular communications system 100 also includes a core network 110, which in the 5G System (5GS) is referred to as the 5GC. The base stations 102 (and optionally the low power nodes 106) are connected to the core network 110.

[0042] The base stations 102 and the low power nodes 106 provide service to wireless communication devices 112-1 through 112-5 in the corresponding cells 104 and 108. The wireless communication devices 112-1 through 112-5 are generally referred to herein collectively as wireless communication devices 112 and individually as wireless communication device 112. In the following description, the wirelesscommunication devices 112 are oftentimes UEs and as such sometimes referred to herein as UEs 112, but the present disclosure is not limited thereto.

[0043] Figure 2 illustrates a wireless communication system represented as a 5G network architecture composed of core Network Functions (NFs), where interaction between any two NFs is represented by a point-to-point reference point / interface. Figure 2 can be viewed as one particular implementation of the system 100 of Figure 1. The embodiments in the reminder of these document are described within the context of 5G network architecture using the 5G terminology, but the embodiments are also applicable to other systems / networks using network slicing, admission control of network slicing and on-demand network slicing can. Example of those systems / networks may be 6G systems / networks and beyond.

[0044] Seen from the access side the 5G network architecture shown in Figure 2 comprises a plurality of UEs 112 connected to either a RAN 102 or an Access Network (AN) as well as an AMF 200. Typically, the R(AN) 102 comprises base stations, e.g. such as eNBs or gNBs or similar. Seen from the core network side, the 5GC NFs shown in Figure 2 includes but not limited to a NSSF 202, an AUSF 204, a UDM 206, the AMF 200, a LMF 220, a SMF 208, a PCF 210, and an Application Function (AF) 212.

[0045] Reference point representations of the 5G network architecture are used to develop detailed call flows in the normative standardization. The N1 reference point is defined to carry signaling between the UE 112 and AMF 200. The reference points for connecting between the AN 102 and AMF 200 and between the AN 102 and UPF 214 are defined as N2 and N3, respectively. There is a reference point, Nil, between the AMF 200 and SMF 208, which implies that the SMF 208 is at least partly controlled by the AMF 200. N4 is used by the SMF 208 and UPF 214 so that the UPF 214 can be set using the control signal generated by the SMF 208, and the UPF 214 can report its state to the SMF 208. The SMSF 220 communicates with the AMF 200 over the N20 reference point, and with UDM 206 over the N21 reference point, and AMF 200 communicates with UDM 206 over the N8 reference point as illustrated in Figure 2. N9 is the reference point for the connection between different UPFs 214, and N14 is the reference point connecting between different AMFs 200, respectively. N15 and N7 are defined since the PCF 210 applies policy to the AMF200 and SMF 208, respectively. N12 is required for the AMF 200 to perform authentication of the UE 112. N8 and N10 are defined because the subscription data of the UE 112 is required for the AMF 200 and SMF 208. NL1 is the reference point between AMF 200 and LMF 220.

[0046] The 5GC network aims at separating UP and CP. The UP carries user traffic while the CP carries signaling in the network. In Figure 2, the UPF 214 is in the UP and all other NFs, i.e., the AMF 200, SMF 208, PCF 210, AF 212, NSSF 202, AUSF 204, and UDM 206, are in the CP. It also allows UPFs to be deployed separately from CP functions in a distributed fashion. In this architecture, UPFs may be deployed very close to UEs to shorten the Round Trip Time (RTT) between UEs and data network for some applications requiring low latency. LMF 220 can be characterized as handling UP and CP that supports CP positioning as well as UP plane positioning. Separating the UP and CP guarantees each plane resource to be scaled independently.

[0047] The 5G core network architecture is composed of modularized functions. For example, the AMF 200, SMF 208 and for example LMF 220 are independent functions in the CP. Separated AMF 200 and SMF 208 allow independent evolution and scaling. Other CP functions like the PCF 210 and AUSF 204 can be separated as shown in Figure 2. Modularized function design enables the 5GC network to support various services flexibly.

[0048] Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF. In the CP, a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity. The UP supports interactions such as forwarding operations between different UPFs.

[0049] Figure 3 illustrates a 5G network architecture using service-based interfaces between the NFs in the CP, instead of the point-to-point reference points / interfaces used in the 5G network architecture of Figure 2. However, the NFs described above with reference to Figure 2 correspond to the NFs shown in Figure 3. The service(s) etc. that a NF provides to other authorized NFs can be exposed to the authorized NFs through the service-based interface. In Figure 3 the service based interfaces are indicated by the letter "N" followed by the name of the NF, e.g. Namffor the service based interface of the AMF 200 and Nsmf for the service based interface of the SMF 208, Nsmsf for service based interface exposing services of SMSF 220, etc. Any NFs depicted in Figure 2 can interact with the NEF 216 and / or NRF 218 of Figure 3 as necessary, though not explicitly indicated in Figure 2.

[0050] Some properties of the NFs shown in Figures 2 and 3 may be described in the following manner. The AMF 200 provides UE-based authentication, authorization, mobility management, etc. A UE 112 even using multiple access technologies is basically connected to a single AMF 200 because the AMF 200 is independent of the access technologies. The SMF 208 is responsible for session management and allocates Internet Protocol (IP) addresses to UEs. It also selects and controls the UPF 214 for data transfer. If a UE 112 has multiple sessions, different SMFs 208 may be allocated to each session to manage them individually and possibly provide different functionalities per session. The AUSF 204 supports authentication function for UEs or similar and thus stores data for authentication of UEs or similar while the UDM 206 stores subscription data of the UE 112. The LMF 220 manages the overall co-ordination and scheduling of resources required for the location of a UE 112 that is registered with or accessing the core network (e.g., 5G CN or 6G CN or any appropriate or applicable CN). It also calculates or verifies a final location and any velocity estimate and may estimate the achieved accuracy. The LMF 220 receives location requests for a target UE 112 from the serving AMF 200 using the Nlmf interface. The LMF 220 interacts with the UE 112 in order to exchange location information applicable to UE assisted and UE based position methods and interacts with the NG-RAN, and other access Network functions (e.g., N3IWF or TNAN specified for 5G CN in TS 23.501) in order to obtain location information. Many NFs including AMF 200, SMF 208 communicate with UDM 206 to obtain subscription data and / or notification of UE availability for reachability or SMS availability. The Data Network (DN), not part of the 5GC network, provides Internet access or operator services and similar.

[0051] An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.

[0052] Figure 4 illustrates the Positioning Procedure over User Plane between LMF 220 and UE 112 in accordance with the prior art. Optional steps are represented by dashed lines / boxes.

[0053] As illustrated, the seps are described below as per TS 23.273 version 18.2.0.1. [Optional] The UE or LMF use the Secure UP transfer one or multiple LPP message(s). If LMF starts the procedure the LMF may request location information and / or measurements from the UE, and / or provide assistance data to / from the UE and / or query for the capabilities; if UE starts procedure, UE may request assistance data from LMF and / or providing location data and / or capability information to LMF.2. [Optional] The UE or LMF processes capabilities information, assistance data, and / or location measurements / calculations.3. [Optional] The UE or LMF may send one or multiple LPP message(s) using the Secure UP transfer.

[0054] NOTE: Step 1, step 2 and step 3 can occur in any order, sequentially or concurrently.

[0055] Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. Embodiments of the solutions described herein are described within the context of 5G CN as described in 3GPP, but can be applicable to any generation of core network with similar or equivalent functionality. The embodiments enable an LMF 220 to obtain relevant information related to PS DATA off status of the UE 112. A number of solution to achieve the purpose are summarized below:Currently there is no interface between SMF 208 and LMF 220, they don’t communicate with each other. 2 solutions / embodiments are described for LMF 220 to get the 3GPP PS DATA off status of the UE:

[0056] Solution 1: The SMF 208 notifies the LMF 220 about the UE's 3GPP PS DATA off UE status.- Solution 1 proposes to add 1 new message from the SMF 208 to LMF 220, once the SMF 208 receives the UE’s 3GPP PS DATA off UE status in for example a PDU session establishment request message within for example the Protocol Configuration Option (PCO) Information element (PCO IE) as described in 3GPP TS 23.502 , the SMF 208 indicates the UE’s 3GPP PS DATA off UE status to the LMF 220 via the new message. For the UEs with 3GPP PS Data Off UE status set to "activated", the LMF 220 doesn’t requestto setup the LCS secured user plane connection according to the 3GPP PS Data Off UE status and the 3GPP PS DATA off exempt service list. If the 3GPP PS data UE status is changed, the SMF 208 shall notify the LMF 220 as well.

[0057] Solution 2: UE 112 notifies the LMF 220 about the UE's 3GPP PS DATA off UE status also referred to as 3GP PS DATA off status.- Solution 2 proposes to add 1 new message from UE 112 to LMF 220 to inform the LMF 220 about the 3GPP PS DATA off status in the UE 112, e.g, USER PLANE CONNECTION UPDATE or USER PLANE CONNECTION NOTIFY message, the message would additionally include the 3GPP PS DATA off status. When the 3GPP PS DATA off UE status is changed, the UE 112 notifies the LMF 220.

[0058] Solution 3: Add a new failure cause code to indicate failure due to the 3GPP PS DATA off status being activated.If the 3GPP PS DATA off UE status is "activated" in the UE and LCS-UPP is not configured in the UE as a 3GPP PS DATA off exempt service in the UE, then when the LMF 220 initiates the network initiated user plane connection establishment procedure with the UE as specified in TS 23.273 clause 6.18.1, then the UE rejects the network initiated user plane connection establishment procedure with the USER PLANE CONNECTION ESTABLISHMENT FAILURE message with the new failure cause.If the 3GPP PS DATA off UE status changes from "deactivated" to "activated", LCS- UPP is not configured in the UE as a 3GPP PS DATA off exempt service, and LCS secured user plane connection already exists, the UE shall initiate UE requested user plane connection release and send the USER PLANE CONNECTION RELEASE REQUEST message with the new failure cause.Once the LMF 220 receives such new failure cause code (either in the USER PLANE CONNECTION ESTABLISHMENT FAILURE message or the USER PLANE CONNECTION RELEASE REQUEST message), LMF 220 shall not request to establish the LCSsecured user plane connection for the UE, and LMF 220 should choose other positioning solutions, e.g control plane positioning solution.When the 3GPP PS DATA off status is changed in the UE, and no LCS secured user plane connection is already available, the LMF 220 can get the 3GPP PS DATA off status information when requesting to establish the LCS secured user plane connection for the UE 112 once the positioning service is needed.

[0059] Solution 4: Combination of solution 3 and solution 2, where in solution 2 the UE informs the LMF 220 only when the 3GPP PS DATA off UE status changes from "activated" to "deactivated", if the UE previously sent the USER PLANE CONNECTION ESTABLISHMENT FAILURE message or the USER PLANE CONNECTION RELEASE REQUEST message, with the new failure cause code of solution 3.Using solution 3, the LMF 220 becomes aware that the LCS-UPP cannot be used due to the 3GPP PS DATA off and LMF shall not request to establish the LCS secured user plane connection for the UE 112 again.Using the part of the solution 2 above, the LMF 220 becomes aware that the LCS- UPP can be used again and LMF 220 can request to establish the LCS secured user plane connection for the UE 112 again.

[0060] Therefore, any of the solution above in essence introduces a mechanism for LMF 220 to become aware that LCS-UPP cannot be used due to the 3GPP PS Data Off and / or to ensure that the LCS secured user plane connection is not established or is released, and the LMF 220 is informed that the reason for not- establishment or release is the 3GPP PS DATA off. Based on this information then LMF 220 shall not request to establish the LCS secured user plane connection for such UE 112 again unless the status of PS DATA off is changed to allowing user plane data to be transmitted for the service.

[0061] Any of the solution / embodiments described above prevents the LMF 220 to request to setup the LCS secured user plane connection which would be rejected by the UE, this mechanism saves the resource of the whole system.

[0062] Now more details of the solutions / embodiments are described herein.

[0063] As stated above, at the time of filing this document, there is a discussion in 3GPP about whether to add the LCS-UPP to a list of operator services configurableby the HPLMN operator to be part of the 3GPP PS DATA off exempt service list.However, no conclusion was reached.If the 3GPP PS DATA off UE status is "activated" then:1 ) If LCS-UPP is not specified by 3GPP to be one of operator services configurable by the HPLMN operator to be part of the 3GPP PS DATA off exempt service list then according to 3GPP TS 22.011 , TS 23.501 and TS 24.501 , the UE cannot send IP packets for LCS-UPP, and the LCS-UPP can’t be used. Any attempt to establish LCS secured user plane connection for such UE needs to be rejected and existing LCS secured user plane connection needs to be released;2) If LCS-UPP is however specified by 3GPP to be one of operator services configurable by the HPLMN operator to be part of the 3GPP PS DATA off exempt service list but the HPLMN does not configure LCS-UPP to be 3GPP PS DATA off exempt service, then again according to 3GPP TS 22.011 , TS 23.501 and TS 24.501 , the UE cannot send IP packets for LCS-UPP, and the LCS-UPP can’t be used. Any attempt to establish LCS secured user plane connection still needs to be rejected and existing LCS secured user plane connection still needs to be released.

[0064] The embodiments herein are described to support the option where 3GPP doesn't agree to add LCS-UPP in the 3GPP PS DATA off exempt service and the option

[0065] Figure 5A illustrates a procedure illustrating solution 1 according to an embodiment.

[0066] In Figure 5A, a new interface between SMF 208 and LMF 220 is proposed, and a new message (e.g, Nlmf_EventNotify or any appropriate message) is used by the SMF 208 to indicate the UE's 3GPP PS DATA off status to LMF 220.

[0067] When the UE indicates the status of PS DATA off to the SMF 208 in for example a PDU session establishment or modification request message to setup or modify a PDU session as per current 3GPP procedure defined in TS 23.502, the PS DATA off status may be included in for e.g., a PCO IE within the message. The SMF 208 at step la uses the new message to inform the LMF 220 about the PS DATA OFF status as obtained from the UE. In some embodiments, the SMF 208 knows theLMF 220 either via a prior subscription to the notification by the LMF 220 in the SMF 208 in which case the LMF 220 may subscribe with all the SMF instances it may discover or the SMF instance is provided by the AMF to the LMF 220. Alternatively, instead of an explicit subscription by the LMF 220, the SMF 208 could be configured with a default notification to the LMF 220 for the event notification (i.e., the event of receiving the PS DATA off status from the UE or changes to PS DATA off status). The identity of the LMF 220 can be provided by the AMF 200 to the SMF 208 during the PDU session establishment procedure in one of the message exchanged between the AMF 200 and the SMF 208.

[0068] When the LMF 220 receives the notification that the 3GPP PS Data Off status is set to "activated" for the UE, the LMF 220 does not request to setup the LCS secured user plane connection with the UE or refrain from using LCS UPP positioning procedures with the UE or may release the UP connection for LCS UPP if one is already established with the UE. The LMF 220 may revert to using control plane positioning procedure with the UE 112. If the 3GPP PS DATA off status is changed to deactivated as indicated by the UE 112 to the SMF 208, the SMF 208 shall notify the LMF 220 as well at step lb, at which point if the LMF 220 needs to perform positioning procedure with the UE 112, the LMF 220 can use LCS UPP procedure instead of control plane positioning procedure.

[0069] If the UE 112 at step 1c changes the PS DATA off status to activated again, it informs the SMF 208, which notifies the LMF 220. If the user plane is established for LCS UPP with the LMF 220 for the UE 112, the LMF 220 can release the UP connection or would refrain from using LCS user plane procedures.

[0070] Figure 5B illustrates a procedure for solution 1 where LCS-UPP is a service that can be exempted as part of PS DATA off exempt services according to an embodiment.

[0071] In Figure 5B, the new interface between SMF 208 and LMF 220 is also used, and the new message (e.g, Nlmf_EventNotify or any appropriate message) is used by the SMF 208 to indicate the UE's 3GPP PS DATA off status to LMF 220. In 5B, the LMF is also configured with the 3GPP PS DATA off exempt service list.

[0072] When the UE indicates the status of PS DATA off to the SMF 208 in for example a PDU session establishment or modification request message to setup ormodify a PDU session as per current 3GPP procedure defined in TS 23.502, the PS DATA off status may be included in for e.g., a PCO IE within the message. The SMF 208 at step la uses the new message to inform the LMF 220 about the PS DATA OFF status as obtained from the UE. In some embodiments, the SMF 208 knows the LMF 220 either via a prior subscription to the notification by the LMF 220 in the SMF 208 in which case the LMF 220 may subscribe with all the SMF instances it may discover or the SMF instance is provided by the AMF to the LMF 220. Alternatively, instead of an explicit subscription by the LMF 220, the SMF 208 could be configured with a default notification to the LMF 220 for the event notification (i.e., the event of receiving the PS DATA off status from the UE or changes to PS DATA off status). The identity of the LMF 220 can be provided by the AMF 200 to the SMF 208 during the PDU session establishment procedure in one of the message exchanged between the AMF 200 and the SMF 208.

[0073] When LMF 220 receives the notification that the 3GPP PS Data Off status is set to "activated", the LMF 220 checks if LCS-UPP is part of the 3GPP PS DATA off exempt service list based on the Home PLMN configuration. If LCS-UPP is not included in the 3GPP PS DATA off exempt service list, then the LMF 220 based on the notification from the SMF 208 will not request to setup the LCS secured user plane connection with the UE or refrain from using LCS UPP positioning procedures with the UE if a UP connection is established or may release the UP connection for LCS UPP if one is established with the UE. The LMF 220 may then revert to using control plane positioning procedure. If LCS-UPP is included in the 3GPP PS DATA off exempt service list, then the LMF 220 based on the notification from the SMF 208 indicating PS DATA off status is activated, the LMF 220 can use the LCS UPP procedure with the UE if it needs to.

[0074] If the 3GPP PS DATA off status is changed to "deactivated", the SMF 208 shall notify the LMF 220 as well at step lb, at which point if the LMF needs to perform positioning procedure with the UE 112, the LMF 220 can use LCS UPP procedure (e.g., establishing a UP connection or performing positioning over UP) instead of using control plane positioning procedure regardless of whether the LCS- UPP is included or not in the 3GPP PS DATA off exempt service list

[0075] If the UE 112 at step 1c changes the PS DATA off status to activated again, the LMF 220 obtains the notification from the SMF 208 (or AMF 200). The LMF 220 checks if LCS-UPP is part of the 3GPP PS DATA off exempt service list based on the Home PLMN configuration. If LCS-UPP is not included in the 3GPP PS DATA off exempt service list, then the LMF 220 based on the notification from the SMF 208 will not request to setup the LCS secured user plane connection with the UE or refrain from using LCS UPP positioning procedures with the UE if a UP connection is setup or may release the UP connection for LCS UPP if one is established with the UE. The LMF 220 may then revert to using control plane positioning procedure. If LCS-UPP is included in the 3GPP PS DATA off exempt service list, then the LMF 220 based on the notification from the SMF 208 indicating PS DATA off status is activated, the LMF 220 can continue to use the LCS UPP procedure with the UE if it needs to.

[0076] Figure 5C illustrates a procedure for solution 2 where LCS-UPP is not added as a 3GPP PS DATA off exempt service and where the UE 112 (instead of the SMF 208) notifies the LMF 220 about the UE's 3GPP PS DATA off UE status also referred to as 3GP PS DATA off status according to an embodiment.

[0077] In Figure 5C, a new message (or existing message) is used by the UE 112 to inform the LMF 220 about the 3GPP PS DATA off status in the UE 112, e.g, USER PLANE CONNECTION UPDATE or USER PLANE CONNECTION NOTIFY message may be used by the UE 112 to indicate to the LMF 220 the UE's 3GPP PS DATA off status and any changes to 3GPP PS DATA off status.

[0078] When the PS DATA off status is activated in the UE 112, and the UE have a UP connection with the LMF 220, the UE 112 in step la sends a message to the LMF 220 to notify the LMF 220 of the 3GPP PS DATA off status as being "activated". In some embodiments, the message is a USER PLANE CONNECTION UPDATE or USER PLANE CONNECTION NOTIFY message, or it may be an existing UP message updated to include the PS DATA Off status of the UE.

[0079] When the LMF 220 receives from the UE 112 over any of the aforementioned messages the notification that the 3GPP PS Data Off status is set to "activated" for the UE, the LMF 220 does not use LCS UPP positioning procedures with the UE or may release the UP connection for LCS UPP. The LMF 220 may revertto using control plane positioning procedure with the UE 112. If the 3GPP PS DATA off status is changed to deactivated in the UE 112, the UE 112 informs the LMF 220 in a similar way at step lb, at which point if the LMF 220 needs to perform positioning procedure with the UE 112, the LMF 220 can use LCS UPP procedure instead of control plane positioning procedure.

[0080] If the UE 112 at step 1c changes the PS DATA off status to activated again, it informs the LMF 220 using any of the aforementioned messages. If the user plane is established for LCS UPP with the LMF 220 for the UE 112, the LMF 220 can release the UP connection or refrain from using LCS user plane procedures.

[0081] Figure 5D illustrates a procedure for solution 2 where the LCS-UPP can be added as a service in the 3GPP PS DATA off exempt service and where the UE 112 (instead of the SMF 208) notifies the LMF 220 about the UE's 3GPP PS DATA off UE status also referred to as 3GP PS DATA off status according to an embodiment.

[0082] In Figure 5D, a new message (or existing message) is used by the UE 112 to inform the LMF 220 about the 3GPP PS DATA off status in the UE 112, e.g, USER PLANE CONNECTION UPDATE or USER PLANE CONNECTION NOTIFY message may be used by the UE 112 to indicate to the LMF 220 the UE's 3GPP PS DATA off status and any changes to 3GPP PS DATA off status. In Figure 5D, the LMF 220 is also configured with the 3GPP PS DATA off exempt service list, but the LCS-UPP is not exempted, i.e., LCS-UPP is not included or configured in the 3GPP PS DATA off exempt service list.

[0083] At step la, the 3GPP PS DATA off status is activated in the UE 112, the UE 112 indicates the status of PS DATA off to the LMF 220 using any of the aforementioned messages in Fig. 5C.

[0084] When LMF 220 receives the notification from the UE 112 that the 3GPP PS Data Off status is set to "activated", the LMF 220 checks if LCS-UPP is part of the 3GPP PS DATA off exempt service list based on the Home PLMN configuration. If LCS-UPP is not included in the 3GPP PS DATA off exempt service list, then the LMF 220 based on the notification from the UE 112 will not use LCS UPP positioning procedures with the UE or may release the UP connection for LCS UPP. The LMF 220 may then revert to using control plane positioning procedure.

[0085] If LCS-UPP is included in the 3GPP PS DATA off exempt service list, then the LMF 220 based on the notification from the UE 112 indicating PS DATA off status is activated, the LMF 220 can use the LCS UPP procedure with the UE if it needs to.

[0086] If the 3GPP PS DATA off status is changed to "deactivated", the UE 112 shall notify the LMF 220 as well at step lb, at which point if the LMF 220 needs to perform positioning procedure with the UE 112, the LMF 220 can use LCS UPP procedure with the UE 112 instead of using control plane positioning procedure regardless of whether the LCS-UPP is included or not in the 3GPP PS DATA off exempt service listIf the UE 112 at step 1c changes the PS DATA off status to activated again, the LMF 220 obtains the notification from the UE 112. The LMF 220 again checks if LCS-UPP is part of the 3GPP PS DATA off exempt service list based on the Home PLMN configuration. If LCS-UPP is not included in the 3GPP PS DATA off exempt service list, then the LMF 220 based on the notification from the UE 112 will not use LCS UPP positioning procedures with the UE over the UP connection or may release the UP connection for LCS UPP. The LMF 220 may then revert to using control plane positioning procedure. If LCS-UPP is included in the 3GPP PS DATA off exempt service list, then the LMF 220 based on the notification from the UE 112 indicating PS DATA off status is activated, the LMF 220 can continue to use the LCS UPP procedure with the UE if it needs to.

[0087] Figure 5E, 5F, 5G and 5H illustrates a procedure for solution 3 where the 3GPP standard does not support configuring LCS-UPP as a 3GPP PS DATA off exempt service (Fig. 5E) or supports configuring LCS-UPP as an exempted service, but the service is not configured in the exempted list of services (Fig. 5F). In either option illustrated in both Figures (5E and 5F) the UE 112 rejects a request from the LMF 220 to setup a UP connection for LCS with the rejection message from the UE 112 to the LMF 220 including a failure cause indicating as 3GPP PS DATA off UE status activated or releases the UP connection if one was established including the appropriate cause.

[0088] More specifically, if the 3GPP PS DATA off UE status is "activated" in the UE (Fig. 5E) or the 3GPP PS DATA off UE status is "activated" in the UE and the LCS-UPP service is not configured to be exempted (5F) then when the LMF 220initiates the network initiated user plane connection establishment procedure with the UE by sending at step 1 a USER PLANE CONNECTION ESTABLISHMENT REQUEST to the UE 112 as specified in TS 23.273 clause 6.18.1, then the UE, at step 2, rejects the network initiated user plane connection establishment procedure with the USER PLANE CONNECTION ESTABLISHMENT FAILURE message with the new failure cause (e.g., 3GPP PS DATA off activated).

[0089] In some embodiment, illustrated in Figure 5G and 5H if the 3GPP PS DATA off UE status changes from "deactivated" to "activated", and the UE either does not support LCS-UPP service being exempted (5G) or support it but may not include LCS-UPP in the 3GPP PS DATA off exempt service (5H), and LCS secured user plane connection already exists, the UE shall initiate UE requested user plane connection release and send the USER PLANE CONNECTION RELEASE REQUEST message with the new failure cause (Activated 3GPP PS DATA off or 3GPP PS DATA off activated.

[0090] Once the LMF 220 receives such new failure cause code (either in the USER PLANE CONNECTION ESTABLISHMENT FAILURE message or the USER PLANE CONNECTION RELEASE REQUEST message), LMF 220 shall not request to establish the LCS secured user plane connection for the UE, and LMF 220 should choose other positioning solutions, e.g., control plane positioning solution.

[0091] When the 3GPP PS DATA off status is changed in the UE, and no LCS secured user plane connection is already available, the LMF 220 can get the 3GPP PS DATA off status information when requesting to establish the LCS secured user plane connection for the UE 112 once the positioning service is needed.

[0092] The following describes solution 3 if and when implemented in the 3GPP standard TS 24.572 by proposing changes to procedure "Network initiated user plane connection establishment procedure not accepted by the UE" in clause 6.2.1.1.5 of the standard and changes to procedure "UE requested user plane connection release procedure initiation by the UE" in clause 6.2.2.2.2 of the standard and "UE requested user plane connection release procedure initiation by the UE" procedure in clause 6.2.2.2.3 and finally changes to clause 11.3.3 for failure causes. The changes are illustrated below as underlined new text to be added to the existing procedure or in italics text added to the table in clause 11.3.3.***** prOpOsec| change to TS 24.572 version 18.1 .1 *****6.2.1.1.5 Network initiated user plane connection establishment procedure not accepted by the UEIf the USER PLANE CONNECTION ESTABLISHMENT COMMAND cannot be accepted, the UE shall send a USER PLANE CONNECTION ESTABLISHMENT FAILURE message to the LMF and shall consider the LCS secured user plane connection between the UE and the LMF as not established. The USER PLANE CONNECTION ESTABLISHMENT FAILURE message contains a Failure cause IE set to for example one of the following cause values or other appropriate values may be used:#1 PDU session failure;#2TLS connection failure;#3LCS-UP connection binding failure;#X Activated 3GPP PS DATA off; or#111 Protocol error, unspecified.If the UE failed to use an established PDU session for LCS-UP or failed to establish a PDU session for LCS-UP, the UE shall send a USER PLANE CONNECTION ESTABLISHMENT FAILURE message containing cause value #1 "PDU session failure".If the UE failed to establish a TLS connection for LCS-UP, the UE shall send a USER PLANE CONNECTION ESTABLISHMENT FAILURE message containing cause value #2 "TLS connection failure".Upon reception of a LCS-UP CONNECTION BINDING REJECT message from the LMF, the UE shall send a USER PLANE CONNECTION ESTABLISHMENT FAILURE message containing cause value #3 "LCS-UP connection binding failure" to acknowledge the binding failure received from LMF.If the 3GPP PS DATA off UE status (see 3GPP TS 24.501 [4]) is "activated", the UE shall send a USER PLANE CONNECTION ESTABLISHMENT FAILURE message containing cause value #X "Activated 3GPP PS DATA off".Upon reception of a USER PLANE CONNECTION ESTABLISHMENT FAILURE message from the UE, the LMF shall stop the timer T5012, release the allocated LCS-UP binding ID value and the association of the TLS connection with the UE, ifany, abort the user plane connection establishment procedure, and consider the LCS secured user plane connection between the UE and the LMF as not established.After that, except if cause value #X 'Activated 3GPP PS DATA off" is included in theUSER PLANE CONNECTION ESTABLISHMENT FAILURE , the LMF may perform the network initiated user plane connection establishment procedure as specified in clause 6.2.1 .1 .2. If cause value #X "Activated 3GPP PS DATA off" is included in the USER PLANE CONNECTION ESTABLISHMENT FAILURE the LMF shall not initiate the network initiated userconnection establishmentas specified in clause 6.2.1 .1 until the UE initiates the UE userconnection establishmentas specified in clause 6.2.2.1.NOTE: After the release of the LCS-UP binding ID value and its association with the UE, the LMF ensures not to assign the LCS-UP binding ID value to any UE for implementation specific time.***** change *****6.2.2.2.2 UE requested user plane connection release procedure initiation by the UEThe UE initiates the UE requested user plane connection release procedure by sending the USER PLANE CONNECTION RELEASE REQUEST message to the LMF, as shown in figure 6.2.2.2.2.1 , the UE: a) shall generate the USER PLANE CONNECTION RELEASE REQUEST message according to subclause 10.3.8, b) shall send the USER PLANE CONNECTION RELEASE REQUEST message to the LMF; c) shall start a timer T5013 upon sending the USER PLANE CONNECTION RELEASE REQUEST message; and d) may include the Failure cause IE with the cause value set to:1 ) #1"PDU session failure" if the UE requested user plane connection release procedure is initiated due to PDU session for the user plane positioning is released;2) #2 "TLS connection failure" if the UE requested user plane connection release procedure is initiated because the TLS connection with the LMF has failed and cannot be maintained by the UE; or y) #X "Activated 3GPP PS DATA off" if the 3GPP PS DATA off UE status (see 3GPP TS 24.501 [4]) changes from "deactivated" to "activated".[Insert Figure 5G or 5H]Figure 6.2.2.2.2.1 : UE requested user plane connection release procedure***** change *****6.2.2.2.3 UE requested user plane connection release procedure accepted by theLMFUpon reception of a USER PLANE CONNECTION RELEASE REQUEST message from the UE, the LMF shall perform the network initiated user plane connection release procedure as specified in subclause 6.2.1.2.If the Failure cause IE is included in the USER PLANE CONNECTION RELEASE REQUEST message with the cause value set to #1 "PDU session failure" or #2 "TLS connection failure", and the location services are still needed, the LMF may consider to use other available positioning solutions after the completion of the user plane connection release procedure.If the Failure cause IE is included in the USER PLANE CONNECTION RELEASE REQUEST message with the cause value set to #X "Activated 3GPP PS DATA off", and the location services are still needed, the LMF shall not initiate the network initiated user plane connection establishmentas specified in clause 6.2.1 .1 until the UE initiates the UEuser plane connection establishmentas specified in clause 6.2.2.1 , and may consider to use other available positioning solutions after the completion of the userconnection release***** change *****11.3.3 Failure causeThe purpose of the Failure cause information element is to indicate the reason of the failure of a UPP-CM procedure.The Failure cause is a type 3 information element with a length of 2 octets.The Failure cause information element is coded as shown in figure 11 .3.3.1 and table 11.3.3.1.8 7 6 5 4 3 2 1 octet 1octet 2Figure 11.3.3.1 : Failure cause information elementTable 11.3.3.1 : Failure cause information element

[0093] Figure 6 illustrates operation or method of a network node implementing for example an LMF that supports user plane (UP) positioning procedure over a UP connection in accordance with the embodiments and steps described herein in figures 5A to 5H.

[0094] The method comprises the step of receiving information indicating that PS DATA off status for a UE is activated and the step of performing one or more an actions including determining whether to refrain from using user plane protocol for location services (LCS-UPP) procedures with the UE while PS DATA OFF status is activated for the UE.

[0095] In one example, the information is obtained from a Session Management Function (SMF) associated to a Packet Data Session established by the UE with the SMF.

[0096] In another example, the information is obtained from the UE in response to sending a User Plane (UP) Connection establishment request by the Location Management Function to the UE. The information may be a failure cause indicating PS DATA off status is activated included in a response message (e.g., USER PLANE CONNECTION ESTABLISHMENT FAILURE) indicating rejection of the request from the Location Management Function.

[0097] The information may also be obtained from the UE in a UP connection release message ( e.g., USER PLANE CONNECTION RELEASE REQUEST) initiated by the UE to the Location Management Function in response to the PS DATA off status change from deactivated to activated in the UE and a UP connection already exists with the Location Management Function. The information in the release message is a failure cause or a release cause indicating PS DATA off status is activated.

[0098] In one example, determining whether to refrain from using user plane protocol for location services (LCS-UPP) procedures with the UE while PS DATA OFF status is activated for the UE comprises either upon determining that LCS-UPP is not included in a PS DATA off exempt list of services, the LMF refrains from using LCS- UPP procedures with the UE or upon determining that LCS-UPP is included in a PS DATA off exempt list of services, the LMF is not blocked from using LCS-UPP with the UE and can use the LCS-UPP procedures with the UE.

[0099] In some example, the one or more actions further comprises releasing a UP connection with the UE if one exists when PS DATA off status is received or when received and the LMF further checks that LCS-UPP is not exempt from PS DATA off. Another action may be not establishing a UP connection with the UE for LCS-UPP if for example the LMF received the PS DATA off status set to activated from the UE.

[0100] Figure 7 illustrates operation or flowchart illustrating steps of a method performed by a wireless communication device (e.g., a UE). The method comprises the step of upon receiving, from a network node implementing a LMF, a request to setup User Plane (UP) connection for UP Protocol for location services (LCS-UPP) sending a failure message comprising a failure cause indicating PS DATA off status in the wireless device is activated. Example of messages are described In Figure 5C to 5H. The method may alternatively include the step of upon determining the 3GPP PS DATA off status is changed from deactivated to activated and UP connection for location services is setup with the network node, sending a release message to the network to release the UP connection and including in the release message a failure cause indicating PS DATA off status is activated. The method may alternatively include the step of notifying the network node implementing the LMF of the 3GPP PS DATA off status and changes to the 3GPP PS DATA off status in the UE.

[0101] In one example, the method further comprises determining that LCS-UPP is not included in PS DATA off list of exempted services when releasing the the UP connection or when sending a failure to setup a UP connection.

[0102] Figure 8 is a schematic block diagram of a network node 800 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The network node 800 may be, for example, a base station 102 or 106 or a network node that implements all or part of the functionality of the basestation 102, or a core network node (or a network node that implements a NF of a core network, e.g., LMF 220, SMF 208). The network node 800 may operate in accordance with, e.g., the process of Figure 7 described above. As illustrated, the network node 800 includes a control system 802 that includes one or more processors 804 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and / or the like), memory 806, and a network interface 808. The one or more processors 804 are also referred to herein as processing circuitry. In addition, if the network node 800 is a radio access node (e.g., a base station 102, or network node that implements at least some of the functionality of the base station 102), the network node 800 may include one or more radio units 810 that each includes one or more transmitters 812 and one or more receivers 814 coupled to one or more antennas 816. The radio units 810 may be referred to or be part of radio interface circuitry. In some embodiments, the radio unit(s) 810 is external to the control system 802 and connected to the control system 802 via, e.g., a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s) 810 and potentially the antenna(s) 816 are integrated together with the control system 802. The one or more processors 804 operate to provide one or more functions of the network node 800 as described herein. In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 806 and executed by the one or more processors 804.

[0103] Figure 9 is a schematic block diagram that illustrates a virtualized embodiment of the network node 800 according to some embodiments of the present disclosure. Again, optional features are represented by dashed boxes. As used herein, a "virtualized" network node is an implementation of the network node 800 in which at least a portion of the functionality of the network node 800 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, if the network node 800 is a radio access node, the network node 800 may include the control system 802 and / or the one or more radio units 810, as described above. The control system 802 may be connected to the radio unit(s) 810 via, for example, an optical cable or the like. The network node 800 includes one or more processingnodes 900 coupled to or included as part of a network(s) 902. If present, the control system 802 or the radio unit(s) are connected to the processing node(s) 900 via the network 902. Each processing node 900 includes one or more processors 904 (e.g., CPUs, ASICs, FPGAs, and / or the like), memory 906, and a network interface 908.

[0104] In this example, functions 910 of the network node 800 described herein are implemented at the one or more processing nodes 900 or distributed across the one or more processing nodes 900 and the control system 802 and / or the radio unit(s) 810 in any desired manner. In some particular embodiments, some or all of the functions 910 of the network node 800 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 900. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 900 and the control system 802 is used in order to carry out at least some of the desired functions 910. Notably, in some embodiments, the control system 802 may not be included, in which case the radio unit(s) 810 communicate directly with the processing node(s) 900 via an appropriate network interface(s).

[0105] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the network node 800 or a node (e.g., a processing node 900) implementing one or more of the functions 910 of the network node 800 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0106] Figure 10 is a schematic block diagram of the network node 800 according to some other embodiments of the present disclosure. The network node 800 includes one or more modules 1000, each of which is implemented in software. The module(s) 1000 provides the functionality of the network node 800 described herein. This discussion is equally applicable to the processing node 900 of Figure 9 where the modules 1000 may be implemented at one of the processing nodes 900 ordistributed across multiple processing nodes 900 and / or distributed across the processing node(s) 900 and the control system 802.

[0107] Figure 11 is a schematic block diagram of a wireless communication device 112 (e.g., a UE) according to some embodiments of the present disclosure. As illustrated, the wireless communication device 112 includes one or more processors 1102 (e.g., CPUs, ASICs, FPGAs, and / or the like), memory 1104, and one or more transceivers 1106 each including one or more transmitters 1108 and one or more receivers 1110 coupled to one or more antennas 1112. The transceiver(s) 1106 includes radio-front end circuitry connected to the antenna(s) 1112 that is configured to condition signals communicated between the antenna(s) 1112 and the processor(s) 1102, as will be appreciated by on of ordinary skill in the art. The processors 1102 are also referred to herein as processing circuitry. The transceivers 1106 are also referred to herein as radio circuitry. In some embodiments, the functionality of the wireless communication device 112 (or UE) described above may be fully or partially implemented in software that is, e.g., stored in the memory 1104 and executed by the processor(s) 1102. Note that the wireless communication device 112 may include additional components not illustrated in Figure 11 such as, e.g., one or more user interface components (e.g., an input / output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and / or the like and / or any other components for allowing input of information into the wireless communication device 112 and / or allowing output of information from the wireless communication device 112), a power supply (e.g., a battery and associated power circuitry), etc.

[0108] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the wireless communication device 112 according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0109] Figure 12 is a schematic block diagram of the wireless communication device 112 according to some other embodiments of the present disclosure. The wireless communication device 112 includes one or more modules 1200, each of which is implemented in software. The module(s) 1200 provides the functionality of the wireless communication device 112 (or UE) described herein.

[0110] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according to one or more embodiments of the present disclosure.

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

Claims

Claims1. A method performed by a wireless communication device (112), the method comprising: receiving from a network node, a request to setup User Plane (UP) connection for UP Protocol for location services (LCS-UPP) with LCS-UPP being a packet switched service; and sending in response to the request a failure message comprising a failure cause when a Packet Switched (PS) Data off status in the wireless device is activated; wherein the PS Data off status activated indicates that transmission of data packets is prevented.

2. The method of claim 1, wherein the method further comprises determining that LCS-UPP service is not included in PS Data off list of exempted services when sending the failure message.

3. The method of claim 1 wherein the network node is a Location Management Function.

4. A method performed by a wireless communication device (112), the method comprising: upon determining that a Packet Switched (PS) Data off status is activated and a User Plane (UP) connection for location services is setup with a network node, sending a release message to the network node to release the UP connection; wherein the release message includes a corresponding failure cause.

5. A wireless communication device (112) adapted to perform the method of any one of claims 1 to 4.

6. A wireless communication device (112) comprising: one or more transmitters (1108); one or more receivers (1110); andprocessing circuity (1102) associated with the one or more transmitters (1108) and the one or more receivers (1110), the processing circuitry (1102) configured to cause the wireless communication device to perform the method of any one of claims 1 to 4.

7. A computer program comprising instructions which, when executed on at least one processor, cause the processor to carry out the method according to any one of claims 1 to 4.

8. A carrier containing the computer program of claim 7, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium.

9. A non-transitory computer-readable medium comprising instructions executable by processing circuitry of a User Equipment (UE) whereby the UE is operable to perform the method of any one of claims 1 to 4.

10. A method performed by a network node implementing a Location Management Function in a wireless communication system, the method comprising: receiving information indicative that PS Data off status for a User Equipment (UE) is activated; and performing one or more actions including determining whether to refrain from using user plane protocol for location services (LCS-UPP) procedures with the UE while Packet Switched (PS) Data OFF status is activated for the UE.

11. The method of claim 10, wherein the information is obtained from a Session Management Function (SMF) associated to a Packet Data Session established by the UE with the SMF.

12. The method of claim 10, wherein the information is obtained from the UE in response to sending a User Plane (UP) Connection establishment request by the Location Management Function to the UE.

13. The method according to claim 12 wherein the information is a failure cause included in failure to establish the UP connection when PS DATA off status is activated at the UE.

14. The method of claim 10, wherein the information is a release cause obtained from the UE in a UP connection release message initiated by the UE to release an existing UP connection with the Location Management Function, in response to the PS DATA off status change at the UE from deactivated to activated.

15. The method of claim 10 wherein determining whether to refrain from using user plane protocol for location services (LCS-UPP) procedures with the UE while PS DATA OFF status is activated for the UE comprises one of:- refraining from using LCS-UPP procedures with the UE upon determining that LCS-UPP is not included in a PS DATA off exempt list of services, or- using LCS-UPP procedures with the UE upon determining that LCS-UPP is included in a PS DATA off exempt list of services.

16. The method of claim 10 wherein the one or more actions further comprises releasing a UP connection with the UE if one exists or not establishing a UP connection with the UE for LCS-UPP.

17. A network node in a wireless communication system, the network node adapted to perform the method of any one of claims 10 to 16.

18. A network node in a wireless communication system, the network node comprising processing circuitry configured to cause the network node to perform the method of any one of claims 10 to 16.

19. A computer program comprising instructions which, when executed on at least one processor, cause the processor to carry out the method according to any one of claims 10 to 16.

20. A carrier containing the computer program of claim 19, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium.

21. A non-transitory computer-readable medium comprising instructions executable by processing circuitry of a network node for a wireless communication system, whereby the network node is operable to perform the method of any one of claims 10 to 16.

Images