EP4620205A1 - Methods to indicate positioning integrity entity - Google Patents

Methods to indicate positioning integrity entity

Info

Publication number
EP4620205A1
EP4620205A1 EP23808765.4A EP23808765A EP4620205A1 EP 4620205 A1 EP4620205 A1 EP 4620205A1 EP 23808765 A EP23808765 A EP 23808765A EP 4620205 A1 EP4620205 A1 EP 4620205A1
Authority
EP
European Patent Office
Prior art keywords
integrity
wireless device
positioning
location
entity
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP23808765.4A
Other languages
German (de)
French (fr)
Inventor
Ritesh SHREEVASTAV
Xiaolin JIANG
Richárd BÁTORFI
Fredrik Gunnarsson
Yunjie Lu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP4620205A1 publication Critical patent/EP4620205A1/en
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity
    • H04W12/104—Location integrity, e.g. secure geotagging
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/029—Location-based management or tracking services

Definitions

  • the present disclosure relates to wireless communications, and in particular, to methods for indicating a positioning integrity entity to a client for radio access technology (RAT) dependent positioning.
  • RAT radio access technology
  • 3GPP Third Generation Partnership Project
  • 4G also referred to as Long Term Evolution (LTE)
  • 5G also referred to as New Radio (NR)
  • Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices or user equipment (UE), as well as communication between network nodes and between wireless devices.
  • the 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.
  • Positioning has been a topic of LTE standardization since 3GPP Technical Release 9 (3GPP Rel-9). An objective is to fulfill regulatory requirements for emergency call positioning. Positioning in NR is proposed to be supported by the architecture shown in FIG.1.
  • the location management function (LMF) is the location node in NR.
  • LMF location management function
  • NRPPa NR positioning protocol A
  • RRC Radio Resource Control
  • the gNB and ng-eNB may not always both be present.
  • Note 2 When both the gNB and ng-eNB are present, the NG-C interface is only present for one of them.
  • Enhanced Cell ID Essentially cell ID information to associate the device to the serving area of a serving cell, and then additional information to determine a finer granularity position
  • • Assisted GNSS GNSS information retrieved by the device, supported by assistance information provided to the device from E-SMLC
  • OTDOA Observed Time Difference of Arrival
  • the device estimates the time difference of reference signals from different base stations and sends to the E-SMLC for multilateration
  • UTDOA Uplink TDOA
  • the device is requested to transmit a specific waveform that is detected by multiple location measurement units (e.g. an eNB) at known positions.
  • multiple location measurement units e.g. an eNB
  • the positioning modes may be categorized in the following three areas: • UE-Assisted: The UE performs measurements with or without assistance from the network and sends these measurements to the E-SMLC where the position calculation may take place; • UE-Based: The UE performs measurements and calculates its own position with assistance from the network; and • Standalone: The UE performs measurements and calculates its own without network assistance.
  • a new study item (SI) on “New SID on Study on expanded and improved NR positioning” has been approved in which one task is to study solutions for Integrity for RAT dependent positioning techniques; identify the error sources; study methodologies, procedures, signaling, etc., for determination of positioning integrity for both UE-based and UE-assisted positioning; and focus on reuse of concepts and principles being developed for RAT-Independent global navigation satellite system (GNSS) positioning integrity, where possible.
  • Integrity Integrity is the measure of trust that may be placed in the correctness of information supplied by a navigation/location system. For example, integrity includes the ability of a system to provide timely warnings to user receivers in case of a failure.
  • a failure may be taken from a radio access technology (RAT) independent positioning method such as assisted GNSS. If a satellite is malfunctioning, it should be detected by the system and the user should be informed not to use this satellite.
  • RAT radio access technology
  • FIG.2 illustrates a definition of accuracy, precision, validity, reliability and integrity.
  • Integrity key performance indicators KPIs
  • TTA Time to Alert
  • IR Integrity Risk
  • PL Protection Level
  • PL is the statistical error bound computed to guarantee that the probability of the absolute position error exceeding the said number is smaller than or equal to the target integrity risk
  • Target Integrity Risk TIR
  • FIG.3 shows an example with the Stanford plot in which all the possible integrity operation and events may be explained in its different regions: Nominal Operation is when PE ⁇ PL ⁇ AL; System unavailable is when AL ⁇ PL; Misleading Operation is when PL ⁇ PE; Hazardously Operation is when PL ⁇ AL ⁇ PE; Integrity Failure is an integrity event that lasts for longer than the TTA and with no alarm raised within the TTA; Misleading Information (MI) is an integrity event occurring when, being the system declared available, the position error exceeds the protection level but not the alert limit; and/or Hazardously Misleading Information (HMI) is an integrity event occurring when, being the system declared available, the position error exceeds the alert limit.
  • MI Misleading Information
  • HMI Hazardously Misleading Information
  • Integrity result reporting modes In 3GPP Technical Report (TR) 38.857 V17.0.0, two modes of integrity result reporting are also identified below for consideration in the work item (WI): • Mode 1 of Integrity Result Reporting : PL Reporting
  • the integrity computing entity calculates the PL based on the measurement assistance information and TIR. Then, the calculated PL is directly reported to where the location services (LCS) client resides (Network or UE). Hence, the integrity computing entity does not judge whether the positioning system is still available. It simply provides whatever PL value it has obtained. It is left to the LCS client itself to determine if the positioning system is still available based on the reported PL.
  • LCS location services
  • the integrity computing entity calculates the PL based on the measurement assistance information and TIR. Then, the integrity computing entity further compares the calculated PL with the given AL to determine if the positioning system is still available to offer trustable position estimation. Thus, the integrity computing entity may only have to report a binary flag (0 and 1) to indicate whether the positioning system is available. Thus, in this case, the LCS client may be directly informed about the system availability, without conducting further evaluation by itself.
  • the location services may be categorized into: - 5GC-MT-LR that is applicable to a request from a location services (LCS) client for a current location of the target UE, and assuming that the LCS client is authorized to use the location service and no privacy verification is required; - 5GC-MO-LR that is applicable to a request by the UEto the serving public land mobile network (PLMN) for obtaining the location related information of itself or just assistance data; and - Deferred 5GC-MT-LR for Periodic, Triggered and UE Available Location Events.
  • FIG.4 illustrates the 5GC-MT-LR procedure for the commercial location service.
  • This procedure is applicable to a request from an LCS client or application function (AF) for a current location of the target UE, and it is assumed that: - Privacy verification may be required for the location service request; - The LCS client or the AF needs to be authorized to use the location service.
  • the LCS Client or the AF (via a network exposure function (NEF)) sends a request to the (H) gateway mobile location center (GMLC) for a location and optionally a velocity for the target UE which may be identified by a general public subscription identifier (GPSI) or a subscription permanent identifier (SUPI).
  • the request may include the required quality of service (QoS), supported geographical area description (GAD) shapes and other attributes.
  • step 2-23 are skipped and (H)GMLC (for 1a) or NEF (for 1b) responds to the LCS Client or the AF the failure of the service authorization in step 24.
  • the (H)GMLC derives the GPSI or SUPI of the target UE and possibly the QoS from either subscription data or other data supplied by the LCS Client or AF.
  • the LCS request may also carry the Service Identity (see 3GPP TS 22.071) and the codeword and the service coverage information.
  • the (H)GMLC may verify that the Service Identity received in the LCS request matches one of the service identities allowed for the LCS client or AF. If the service identity does not match one of the service identities for the LCS client or AF, the (H)GMLC shall reject the LCS request. Otherwise, the (H)GMLC may map the received service identity in a corresponding service type.
  • the LCS service request may include a scheduled location time if a current location of the UE is required at a specific time in the future.
  • the LCS service request may include integrity requirements. NOTE 1: In this release of 3GPP specifications, integrity requirements are only for GNSS integrity.
  • the (H)GMLC itself determines the verinym (GPSI or SUPI) of the target UE. If the (H)GMLC may resolve the address of PMD from the pseudonym, the HGMLC requests the verinym from its associated PMD. If (H)GMLC is not able to obtain the verinym of the target UE, the (H)GMLC shall cancel the location request.
  • PMD pseudonym mediation device
  • the (H)GMLC verifies whether it stores the previously obtained location estimate of the target UE. If the HGMLC stores the location estimate and timestamp of the location estimate (if available) and the location estimate satisfies the requested accuracy and the requested maximum age of location, the (H)GMLC checks the result of the privacy check at step 2. If the result of the privacy check for call/session unrelated class is "Location allowed without notification” then steps 3-23 may be skipped. 1b-1 AF sends the Nnef_EventExposure_Subscribe to the NEF.
  • the NEF identifies based on the QoS attribute received from the location request that higher than cell-ID level location accuracy is required and invokes the Ngmlc_Location_ProvideLocation_Request service operation to the (H)GMLC, which contains the attributes received from the AF request.
  • the NEF may also invoke the Ngmlc_Location_ProvideLocation_Request service operation to the (H)GMLC for lower than cell-ID location accuracy as an implementation option or if a scheduled location time is included.
  • the NEF or HGMLC receiving location request shall verify whether the number of Target UEs in the Nnef_EventExposure_Subscribe or LCS request is equal to or less than the Maximum Target UE Number of the LCS client. If Maximum Target UE Number is exceeded, the NEF or HGMLC shall reject the Nnef_EventExposure_Subscribe or LCS request, the steps 2-23 are skipped, and then the GMLC respond to the client with proper error cause in the step 24.
  • the NEF may invoke an Namf_EventExposure_Subscribe service operation to subscribe location event reporting from the access and mobility management function (AMF) for the target UE as further described in clause 6.5 of the relevant 3GPP technical standard.
  • the (H)GMLC invokes a Nudm_SDM_Get service operation towards the unified data manager (UDM) of the target UE to get the privacy settings of the UE identified by its GPSI or SUPI.
  • the UDM returns the target UE Privacy setting of the UE.
  • the (H)GMLC checks the UE LCS privacy profile. If the target UE is not allowed to be located, steps 3-23 are skipped. 3.
  • the (H)GMLC invokes a Nudm_UECM_Get service operation towards the UDM of the target UE with GPSI or SUPI of this UE.
  • the UDM returns the network addresses of the current serving AMF and additionally the address of a VGMLC (for the roaming case). If the location request is an immediate location request, the (H)GMLC checks the country codes of the serving node addresses. If the (H)GMLC finds the current AMF is out of the service coverage of the (H)GMLC, the (H)GMLC returns an appropriate error message to the LCS client or AF (via NEF).
  • NOTE 3 The UDM is aware of the serving AMF address at UE registration on an AMF as defined in clause 4.2.2.2.2 of 3GPP TS 23.502 [19].
  • the UDM is aware of a serving VGMLC address at UE registration on an AMF as defined in clause 4.2.2.2.2 of 3GPP TS 23.502 [19].
  • the HGMLC may also query the HSS of the target UE for a serving mobile management entity (MME) address as described in clause 9.1.1 of 3GPP TS 23.271 [4].
  • MME serving mobile management entity
  • the EPC-MT-LR procedure described in clause 9.1.15 of 3GPP TS 23.271 [4], excluding the UE availability event, may then be performed instead of steps 4-23, e.g. if the home subscriber server (HSS) returns an MME address but the UDM does not return an AMF address. 4. For a non-roaming case, this step is skipped.
  • the HGMLC may receive an address of a VGMLC (together with the network address of the current serving AMF) from the UDM in step 3, otherwise, the HGMLC may use the NRF service in the HPLMN to select an available VGMLC in the VPLMN, based on the VPLMN identification contained in the AMF address received in step 3.
  • the HGMLC then sends the location request to the VGMLC by invoking the Ngmlc_Location_ProvideLocation service operation towards the VGMLC.
  • the HGMLC sends the location service request message to the serving AMF. In this case, step 4 is skipped. If the result of privacy check indicates that the verification based on current location is needed, the HGMLC shall send a location request to the VGMLC (in the case of roaming) or to the AMF (in the case of non-roaming) indicating "positioning allowed without notification" and VGMLC shall invoke an Namf_Location_ProvidePositioningInfo Request service operation towards the AMF at step 5.
  • H-GMLC also provides the LCS client type of AF, if received in step 41b-2, or LCS client type of LCS client and other attributes to be sent to AMF in step 5. 5.
  • the VGMLC first authorizes that the location request is allowed from this HGMLC, PLMN or from this country. If not, an error response is returned.
  • the (H)GMLC or VGMLC invokes the Namf_Location_ProvidePositioningInfo service operation towards the AMF to request the current location of the UE.
  • the service operation includes the SUPI, the client type and may include the required LCS QoS, supported GAD shapes, scheduled location time, service type and other attributes as received or determined in step 1.
  • the location request forwarded at step 4 and step 5 may also carry the result of the privacy check in step 2 which may include a codeword provided by the LCS Client or AF and an indication of a privacy related action as described in clause 5.4. 6.
  • the AMF initiates a network triggered Service Request procedure as defined in clause 4.2.3.3 of 3GPP TS 23.502 to establish a signalling connection with the UE. If signalling connection establishment fails, steps 7-13 are skipped and the AMF answers to the GMLC in step 14 with the last known location of the UE (i.e. Cell ID) together with the age of this location. 7.
  • the AMF shall return an error response in step 14 and if roaming VGMLC in step 15 to the HGMLC if privacy verification was requested and either the UE user denies permission or there is no response with the indication received from the (H)GMLC indicating barring of the location request and steps 10 ⁇ 13 are skipped.
  • the notification result may also indicate the Location Privacy Indication setting for subsequent LCS requests; i.e. whether subsequent LCS requests, if generated, will be allowed or disallowed by the UE.
  • the Location Privacy Indication may also indicate a time for disallowing the subsequent LCS requests.
  • the AMF invokes the Nudm_ParameterProvision_Update (LCS privacy) service operation to store in the UDM the Location Privacy Indication information received from the UE.
  • the UDM may then store the updated UE privacy setting information into the UDR as the “LCS privacy” Data Subset of the Subscription Data. 10-13.
  • Steps 10-13 are the same as steps 6-9 defined in clause 6.1.1 of the relevant 3GPP technical standard with the addition that service type may be indicated towards the LMF and the exception that the LMF may determine the UE location in local coordinates or geographical co-ordinates or both. If the supported GAD shapes is not received in step 11 or Local Co-ordinates is not included in the supported GAD shapes, the LMF shall determine a geographical location. If a scheduled location time is provided at step 5, steps 11 and 12 include the following additional differences. 11.
  • the AMF returns the Namf_Location_ProvidePositioningInfo Response towards the (V)GMLC (or HGMLC for roaming when the NL3 reference point is not supported) to return the current location of the UE.
  • the service operation includes the location estimate, its age and accuracy and may include information about the positioning method and the timestamp of the location estimate. 15.
  • the VGMLC forwards the location estimation of the target UE, its age, its accuracy and optionally the information about the positioning method received at step 14 to the HGMLC. For non-roaming scenario, this step is skipped. 16.
  • the (H)GMLC shall perform an additional privacy check in order to decide whether the (H)GMLC may forward the location information to the LCS client or AF or send a notification if the result of the privacy check requires the notification and verification based on current location.
  • This additional privacy check is needed is when the target UE user has defined different privacy settings for different geographical locations.
  • the (H)GMLC skips steps 17-23. 17. If the result of privacy checks in step 16 indicates that the notification (and verification) based on current location is needed, and in the case of roaming, the (H)GMLC shall send a location request to the VGMLC with location type indicating “notification only”. 18.
  • Step 21 is the same as step 8. 22.
  • the AMF returns the Namf_Location_ProvidePositioningInfo Response towards the (V)GMLC (or HGMLC for roaming when the NL3 reference point is not supported) with an indication of the result of notification and verification procedure performed in steps 20-21.
  • the VGMLC forwards an indication of the result of notification and verification procedure to the HGMLC. For non-roaming scenario, this step is skipped.
  • the (H)GMLC sends the location service response to the LCS Client or AF (via the NEF) if the target UE is allowed to be located by the LCS Client or AF.
  • the location service response from the (H)GMLC to the LCS Client or AF may contain the information about the positioning method used and the indication indicating whether the obtained location estimate satisfies the requested accuracy. If in step 2, step 15, step 16 or step 23, the (H)GMLC identifies that the target UE is not allowed to be located by the LCS Client or AF, it rejects the LCS service request, and optionally indicates in the response, the reason of the rejection, i.e., the target UE is not allowed to be located. If the LCS QoS Class is Assured and (H)GMLC detects that requested accuracy is not achieved, the (H)GMLC sends error response including failure cause.
  • Some embodiments advantageously provide methods, systems, and apparatuses for indicating a positioning integrity entity to a client for radio access technology (RAT) dependent positioning. Some embodiments may provide methods for: • indicating which entity (wireless device, location management function ) performed the integrity result calculation to the external location services (LCS) client; and/or • how the external LCS client may use the integrity entity information to calibrate the positioning integrity results.
  • a tag indicating the positioning integrity entity for each positioning session may be sent by the location management function to the access and mobility management function (AMF) and further to the external LCS client. Having knowledge of which entity performed the positioning integrity calculation, the external LCS client may further utilize other knowledge about that entity available to calibrate and refine the integrity results.
  • AMF access and mobility management function
  • the location management function sends positioning integrity entity information in the location service response to the AMF and the AMF may forward this information all the way to the external LCS client.
  • the external LCS client may use the positioning integrity entity information to calibrate and refine the integrity results.
  • Some embodiments include a flag which will inform the LCS client whether the integrity and safety computations were done by the wireless device side or by the location management function. There may be some unknown errors while computing integrity such as any residual error, wireless device hardware impairments or hardware fault. Similarly, at the location management function there may be unknown or unaccounted-for error; hence the LCS client may compensate for and take the necessary safety margins into account, and accordingly, whether they were computed by the location management function or the wireless device.
  • a network node configured to communicate with a wireless device, the network node configured to: receive an integrity result from one of a wireless device and a location management function, the one of the wireless device and the location management function being a positioning integrity entity; and send to a location services (LCS) client an indication of which of the wireless device and the location management function is the positioning integrity entity for each of a plurality of positioning sessions.
  • the indication of positioning integrity entity includes integrity results determined by the positioning integrity entity.
  • the indication of positioning integrity entity includes integrity results verified by the one of the wireless device and the location management function that is not the positioning integrity entity.
  • an indication of positioning integrity from the wireless device includes an indication of a radio access technology (RAT)-dependent positioning integrity.
  • the network node is configured to receive a global navigation satellite system (GNSS) integrity.
  • the integrity result includes a protection level, PL, and an entity that determined the PL.
  • the method includes: receiving an integrity result from one of a wireless device and a location management function , the one of the wireless device and the location management function being a positioning integrity entity; and sending to a location services (LCS) client an indication of which of the wireless device and the location management function is the positioning integrity entity for each of a plurality of positioning sessions.
  • the indication of positioning integrity entity includes integrity results determined by the positioning integrity entity.
  • the indication of positioning integrity entity includes integrity results verified by the one of the wireless device and the location management function that is not the positioning integrity entity.
  • an indication of positioning integrity from the wireless device includes an indication of a radio access technology (RAT)-dependent positioning integrity.
  • RAT radio access technology
  • the method includes receiving a global navigation satellite system (GNSS) integrity.
  • the integrity result includes a protection level, PL, and an entity that determined the PL.
  • a core network node configured to communicate with a wireless device. The core network node is configured to: receive from a second network node an indication indicating which of at least one of a first wireless device and a location management function is a position integrity entity; and determine via an access and mobility function a positioning integrity result based at least in part on the indication of the position integrity entity.
  • the core network node is configured to transmit to a second wireless device an indication of the position integrity result.
  • the core network node is configured to transmit to a second wireless device an indication of an identity of the position integrity entity. In some embodiments, determining the positioning integrity result further includes determining an age and accuracy of the position integrity result. In some embodiments, the integrity result includes a protection level, PL, and an entity that determined the PL.
  • a method implemented in a core network node configured to communicate with a wireless device and a second network node includes receiving from the second network node an indication indicating which of at least one of a first wireless device and a location management function is a position integrity entity; and determining via an access and mobility function, a positioning integrity result based at least in part on the indication of the position integrity entity.
  • the method includes transmitting to a second wireless device an indication of the position integrity result. In some embodiments, the method includes transmitting to a second wireless device an indication of an identity of the position integrity entity. In some embodiments, determining the positioning integrity result further includes determining an age and accuracy of the position integrity result. In some embodiments, the integrity result includes a protection level, PL, and an entity that determined the PL.
  • a wireless device configured to communicate with a network node is provided. The wireless device is configured to: transmit radio access technology (RAT)-dependent positioning integrity result to the network node, the positioning integrity result including at least one of a location request, a quality of service request and an identity of a location management function to receive the positioning integrity result.
  • RAT radio access technology
  • the positioning integrity result includes a request for one of a position and location assistance data.
  • the wireless device is configured to receive from the location management function, a scheduled location time for determining the positioning integrity result.
  • the wireless device is configured to perform an integrity computation and include the integrity computation in the positioning integrity result.
  • the integrity result includes a protection level, PL, and an entity that determined the PL.
  • the method includes transmitting radio access technology (RAT)-dependent positioning integrity result to the network node, the positioning integrity result including at least one of a location request, a quality of service request and an identity of a location management function to receive the positioning integrity result.
  • RAT radio access technology
  • the positioning integrity result includes a request for one of a position and location assistance data.
  • the method includes receiving from the location management function, a scheduled location time for determining the positioning integrity result.
  • the method includes performing an integrity computation and including the integrity computation in the positioning integrity result.
  • the integrity result includes a protection level, PL, and an entity that determined the PL.
  • FIG.1 illustrates NG-RAN 3GPP Rel-15 LCS protocols
  • FIG.2 illustrates differences between accuracy, precision, validity, reliability, integrity and certainty
  • FIG.3 is a Stanford plot
  • FIGS.4 and 4A depict a timing diagram of a procedure for a commercial location service
  • FIG.5 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure
  • FIG.6 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure
  • FIG.7 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to
  • relational terms such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements.
  • the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein.
  • the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the joining term, “in communication with” and the like may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • electrical or data communication which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.
  • the term “network node” used herein may be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi- standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node,
  • the network node may also comprise test equipment.
  • radio node used herein may be used to also denote a wireless device such as a wireless device or a radio network node.
  • wireless device such as a wireless device or a radio network node.
  • UE user equipment
  • the wireless device herein may be any type of wireless device capable of communicating with a network node or another wireless device over radio signals, such as wireless device.
  • the wireless device may also be a radio communication device, target device, device to device (D2D) wireless device, machine type wireless device or wireless device capable of machine to machine communication (M2M), low-cost and/or low-complexity wireless device, a sensor equipped with wireless device, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (IoT) device, or a Narrowband IoT (NB-IOT) device, etc.
  • D2D device to device
  • M2M machine to machine communication
  • M2M machine to machine communication
  • M2M machine to machine communication
  • Low-cost and/or low-complexity wireless device a sensor equipped with wireless device
  • Tablet mobile terminals
  • smart phone laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles
  • CPE Customer Premises Equipment
  • IoT Internet of Things
  • NB-IOT Narrowband IoT
  • Radio network node may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).
  • RNC evolved Node B
  • MCE Multi-cell/multicast Coordination Entity
  • IAB node Multi-cell/multicast Coordination Entity
  • RRU Remote Radio Unit
  • RRH Remote Radio Head
  • WCDMA Wide Band Code Division Multiple Access
  • WiMax Worldwide Interoperability for Microwave Access
  • UMB Ultra Mobile Broadband
  • GSM Global System for Mobile Communications
  • functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes.
  • the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, may be distributed among several physical devices.
  • all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.
  • Some embodiments provide for indicating a positioning integrity entity to a client for radio access technology (RAT) dependent positioning.
  • RAT radio access technology
  • FIG.5 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14.
  • the access and mobility function and location management function may be provided by one or more network nodes in the core network 14.
  • the access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18).
  • Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20.
  • a first wireless device wireless device22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a.
  • a second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b.
  • wireless devices 22 While a plurality of wireless devices 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole wireless device is in the coverage area or where a sole wireless device is connecting to the corresponding network node 16. Note that although only two wireless devices 22 and three network nodes 16 are shown for convenience, the communication system may include many more wireless devices 22 and network nodes 16. Also, it is contemplated that a wireless device 22 may be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a wireless device 22 may have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR.
  • wireless device 22 may be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.
  • the communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • the connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30.
  • the intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network.
  • the intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).
  • the communication system of FIG.5 as a whole enables connectivity between one of the connected wireless devices 22a, 22b and the host computer 24.
  • the connectivity may be described as an over-the-top (OTT) connection.
  • the host computer 24 and the connected wireless devices 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications.
  • a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected wireless device 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the wireless device 22a towards the host computer 24.
  • a network node 16 is configured to include an integrity unit 32 which is configured to send to a location services (LCS) client an indication of which of the wireless device and the location management function is the positioning integrity entity for each of a plurality of positioning sessions.
  • LCS location services
  • a wireless device 22 is configured to include an integrity results unit 34 which is configured to transmit radio access technology (RAT)-dependent positioning integrity result to the network node, the positioning integrity result including at least one of a location request, a quality of service request and an identity of a location management function to receive the positioning integrity result.
  • RAT radio access technology
  • Within the core network 14 is a core network node 36 configured to perform location management functionsand access and mobility functions, as described below. Example implementations, in accordance with an embodiment, of the wireless device 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG.6.
  • a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10.
  • the host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities.
  • the processing circuitry 42 may include a processor 44 and memory 46.
  • the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • the processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 46 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24.
  • Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein.
  • the host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24.
  • the instructions may be software associated with the host computer 24.
  • the software 48 may be executable by the processing circuitry 42.
  • the software 48 includes a host application 50.
  • the host application 50 may be operable to provide a service to a remote user, such as a wireless device 22 connecting via an OTT connection 52 terminating at the wireless device 22 and the host computer 24.
  • the host application 50 may provide user data which is transmitted using the OTT connection 52.
  • the “user data” may be data and information described herein as implementing the described functionality.
  • the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider.
  • the processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22.
  • the communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the wireless device 22.
  • the hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a wireless device 22 located in a coverage area 18 served by the network node 16.
  • the radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • the communication interface 60 may be configured to facilitate a connection 66 to the host computer 24.
  • the connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.
  • the hardware 58 of the network node 16 further includes processing circuitry 68.
  • the processing circuitry 68 may include a processor 70 and a memory 72.
  • the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection.
  • the software 74 may be executable by the processing circuitry 68.
  • the processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16.
  • Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein.
  • the memory 72 is configured to store data, programmatic software code and/or other information described herein.
  • the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16.
  • processing circuitry 68 of the network node 16 may include an integrity unit 32 which is configured to send to a location services (LCS) client an indication of which of the wireless device and the location management function is the positioning integrity entity for each of a plurality of positioning sessions.
  • the communication system 10 further includes the wireless device 22 already referred to.
  • the wireless device 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the wireless device 22 is currently located.
  • the radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • the hardware 80 of the wireless device 22 further includes processing circuitry 84.
  • the processing circuitry 84 may include a processor 86 and memory 88.
  • the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • processors and/or processor cores and/or FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 88 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the wireless device 22 may further comprise software 90, which is stored in, for example, memory 88 at the wireless device 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the wireless device 22.
  • the software 90 may be executable by the processing circuitry 84.
  • the client application 92 may be operable to provide a service to a human or non-human user via the wireless device 22, with the support of the host computer 24.
  • an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the wireless device 22 and the host computer 24.
  • the client application 92 may receive request data from the host application 50 and provide user data in response to the request data.
  • the OTT connection 52 may transfer both the request data and the user data.
  • the client application 92 may interact with the user to generate the user data that it provides.
  • the processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by wireless device 22.
  • the processor 86 corresponds to one or more processors 86 for performing wireless device 22 functions described herein.
  • the wireless device 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to wireless device 22.
  • the processing circuitry 84 of the wireless device 22 may include an integrity results unit 34 which is configured to transmit radio access technology (RAT)-dependent positioning integrity result to the network node, the positioning integrity result including at least one of a location request, a quality of service request and an identity of a location management function to receive the positioning integrity result.
  • the communication system 10 also includes the core network node 36 which includes processing circuitry 94 configured to perform access and mobility functions 96 and location management functions 98 within an integrity determination unit 100.
  • the processing circuitry 94 is configured to control the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed by theaccess and mobility function96 and 98.
  • the processing circuitry 94 may be implemented as processor operating according to computer instructions stored in a memory of the core network node 36.
  • the memory is configured to store data, programmatic software code and/or other information described herein.
  • the processing circuitry 94 may include a processor, such as a central processing unit, and memory.
  • the processing circuitry 94 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 88 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • RAM Random Access Memory
  • ROM Read-Only Memory
  • EPROM Erasable Programmable Read-Only Memory
  • the radio interface 102 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • RF radio frequency
  • the inner workings of the network node 16, wireless device 22, and host computer 24 may be as shown in FIG.6 and independently, the surrounding network topology may be that of FIG.5.
  • the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the wireless device 22 or from the service provider operating the host computer 24, or both.
  • the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 64 between the wireless device 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the wireless device 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the wireless device 22, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary wireless device signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.
  • the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the wireless device 22.
  • the cellular network also includes the network node 16 with a radio interface 62.
  • the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/ supporting/ending a transmission to the wireless device 22, and/or preparing/terminating/ maintaining/supporting/ending in receipt of a transmission from the wireless device 22.
  • the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a wireless device 22 to a network node 16.
  • the wireless device 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/ supporting/ending a transmission to the network node 16, and/or preparing/ terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.
  • FIGS.5 and 6 show various “units” such as integrity unit 32, and integrity results unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.
  • FIG.7 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIGS.5 and 6, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a wireless device 22, which may be those described with reference to FIG.6.
  • the host computer 24 provides user data (Block S100).
  • the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block S102).
  • a host application such as, for example, the host application 50
  • the host computer 24 initiates a transmission carrying the user data to the wireless device 22 (Block S104).
  • the network node 16 transmits to the wireless device 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block S106).
  • the wireless device 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block S108).
  • FIG.8 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG.5, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a wireless device 22, which may be those described with reference to FIGS.5 and 6.
  • the host computer 24 provides user data (Block S110).
  • the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50.
  • the host computer 24 initiates a transmission carrying the user data to the wireless device 22 (Block S112).
  • the transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIG.9 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG.5, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a wireless device 22, which may be those described with reference to FIGS.5 and 6.
  • the wireless device 22 receives input data provided by the host computer 24 (Block S116).
  • the wireless device 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block S118).
  • the wireless device 22 provides user data (Block S120).
  • the wireless device provides the user data by executing a client application, such as, for example, client application 92 (Block S122).
  • the executed client application 92 may further consider user input received from the user.
  • the wireless device 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124).
  • the host computer 24 receives the user data transmitted from the wireless device 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).
  • FIG.10 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG.5, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a wireless device 22, which may be those described with reference to FIGS.5 and 6.
  • the network node 16 receives user data from the wireless device 22 (Block S128).
  • the network node 16 initiates transmission of the received user data to the host computer 24 (Block S130).
  • the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block S132).
  • FIG.11 is a flowchart of an example process in a network node 16 for indicating a positioning integrity entity to a client for radio access technology (RAT) dependent positioning.
  • One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the integrity unit 32), processor 70, radio interface 62 and/or communication interface 60.
  • Network node 16 such as via processing circuitry 68 and/or processor 70 and/or radio interface 62 and/or communication interface 60 is configured to receive an integrity result from one of a wireless device and a location management function, the one of the wireless device and the location management function being a positioning integrity entity (Block S134).
  • the process also includes sending to a location services (LCS) client an indication of which of the wireless device and the location management function is the positioning integrity entity for each of a plurality of positioning sessions (Block S136).
  • the indication of positioning integrity entity includes integrity results determined by the positioning integrity entity.
  • the indication of positioning integrity entity includes integrity results verified by the one of the wireless device and the location management function that is not the positioning integrity entity.
  • an indication of positioning integrity from the wireless device includes an indication of a radio access technology (RAT)-dependent positioning integrity.
  • the method also includes receiving a global navigation satellite system (GNSS) integrity.
  • the integrity result includes a protection level, PL, and an entity that determined the PL.
  • FIG.12 is a flowchart of an example process in a core network node 36 for indicating a positioning integrity entity to a client for radio access technology (RAT) dependent positioning.
  • One or more blocks described herein may be performed by one or more elements of core network node 36 such as by one or more of processing circuitry 94 (including the integrity determination unit 102) and/or the radio interface 100.
  • the core network node 36 such as via processing circuitry 94 and/or radio interface 100 is configured to receive from the second network node an indication indicating which of at least one of a first wireless device and a location management function is a position integrity entity (Block S138).
  • the process also includes determining via an access and mobility function a positioning integrity result based at least in part on the indication of the position integrity entity (Block S140).
  • the method includes transmitting to a second wireless device an indication of the position integrity result. In some embodiments, the method includes transmitting to a second wireless device an indication of an identity of the position integrity entity. In some embodiments, determining the positioning integrity result further includes determining an age and accuracy of the position integrity result. In some embodiments, the integrity result includes a protection level, PL, and an entity that determined the PL.
  • FIG.13 is a flowchart of an example process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the integrity results unit 34), processor 86, radio interface 82 and/or communication interface 60.
  • Wireless device 22 such as via processing circuitry 84 and/or processor 86 and/or radio interface 82 is configured to transmitting radio access technology (RAT)-dependent positioning integrity result to the network node, the positioning integrity result including at least one of a location request, a quality of service request and an identity of a location management function to receive the positioning integrity result (Block S142).
  • the positioning integrity result includes a request for one of a position and location assistance data.
  • the method includes receiving from the location management function 98 a scheduled location time for determining the positioning integrity result.
  • the method includes performing an integrity computation and including the integrity computation in the positioning integrity result.
  • the integrity result includes a protection level, PL, and an entity that determined the PL.
  • Step 1 The external client sends an LCS service request, and when a integrity performance request is included it may also request integrity entity information and/or request desired integrity entity.
  • Step 2. the wireless device 22 positioning and integrity performance calculation. The detailed procedures are not shown.
  • the external entity is clear about the responsible party in case of failure due to wrong integrity results being provided.
  • the external client may also utilize other information such as knowledge about the integrity entity as indicated (whether there is bias in the integrity performance result considering the algorithm and/or its hardware and computing capability).
  • the external client may compute the bias by comparing the positioning and integrity results from other RAT-independent positioning methods to calibrate the integrity results.
  • the LCS client may decide the integrity entity that provides a best integrity performance and may request that entity as the desired integrity entity for later sessions.
  • Step 3a The concept is also applicable when the client is in the wireless device 22.
  • the LMF 98 may inform the wireless device LCS layer that Integrity has been computed by either the LMF 98 or the wireless device 22.
  • UE Capability to support RAT-dependent positioning Integrity Inside Step 2 wireless device or UE Capability regarding RAT-dependent positioning Integrity is sent from the wireless device 22 to the LMF 98.
  • the RAT-dependent positioning Integrity may have two modes: UE-based mode and UE-assisted (LMF-based) modes.
  • wireless device 22 may indicate its capability of RAT-dependent positioning to the LMF 98 in LTE positioning protocol (LPP) ProvideCapabilityMessage.
  • LPF LTE positioning protocol
  • the wireless device’s RAT-dependent positioning capability may be characterized by extending the PositioningModes information element (IE) in LPP.
  • IE PositioningModes information element
  • the LCS Client or the AF sends a request to the (H)GMLC for a location and optionally, a velocity for the target wireless device 22 which may be identified by an GPSI or an SUPI.
  • the request may include the required QoS, supported GAD shapes and other attributes.
  • (H)GMLC (for 1a) or NEF (for 1b) authorizes the LCS Client or the AF for the usage of the LCS service. If the authorization fails, steps 2-23 are skipped and (H)GMLC (for 1a) or NEF (for 1b) responds to the LCS Client or the AF the failure of the service authorization in step 24.
  • the (H)GMLC derives the GPSI or SUPI of the target wireless device 22 and possibly the QoS from either subscription data or other data supplied by the LCS Client or AF.
  • the LCS request may also carry the Service Identity (see 3GPP TS 22.071) and the Codeword and the service coverage information.
  • the (H)GMLC may verify that the Service Identity received in the LCS request matches one of the service identities allowed for the LCS client or AF. If the service identity does not match one of the service identities for the LCS client or AF, the (H)GMLC may reject the LCS request. Otherwise, the (H)GMLC may map the received service identity in a corresponding service type.
  • the LCS service request may include a scheduled location time if a current location of the wireless device 22 is required at a specific time in the future.
  • the LCS service request may include integrity requirements.
  • Integrity requirements may include GNSS integrity and/or RAT- dependent integrity.
  • 10-13 Steps 10-13 are the same as steps 6-9 defined in clause 6.1.1 of the relevant 3GPP Technical Standard with the addition that service type may be indicated towards the LMF 98 and the exception that the LMF 98 may determine the wireless device location in local coordinates or geographical co-ordinates or both. Either the wireless device 22 or LMF 98 may perform the integrity computation. If the supported GAD shapes is not received in step 11 or Local Co-ordinates is not included in the supported GAD shapes, the LMF 98 may determine a geographical location.
  • steps 11 and 12 may include the following additional differences.
  • the AMF 96 may include the scheduled location time in the Nlmf_Location_DetermineLocation service operation sent towards the LMF 98. 12.
  • the LMF 98 may include the scheduled location time.
  • LMF 98 may determine to use GNSS positioning method and/or RAT-dependent positioning method.
  • LMF 98 may not deliver the scheduled location time to NG-RAN as part of step 12.
  • the wireless device 22 sends an MO-LR Request message included in a UL NAS TRANSPORT message.
  • the MO-LR Request may optionally include up to three LPP positioning message(s).
  • Different types of location services may be requested: location estimate of the wireless device 22, location estimate of the wireless device 22 to be sent to an LCS client or AF, or location assistance data. If the wireless device 22 is requesting its own location or that its own location be sent to an LCS client or AF, this message carries LCS requested QoS information (e.g. accuracy, response time, LCS QoS Class), the requested maximum age of location, the requested type of location (e.g.
  • LCS requested QoS information e.g. accuracy, response time, LCS QoS Class
  • the requested maximum age of location e.g.
  • the message may include the identity of the LCS client or the AF, and may include the address of the GMLC through which the LCS client or AF (via NEF) should be accessed.
  • a Service Type indicating which MO-LR service of the LCS Client is requested by the wireless device 22 may be included.
  • the message also may include a pseudonym indicator to indicate that a pseudonym should be assigned by the network and transferred to the LCS Client as the wireless device's identity.
  • the message may also include integrity requirements. NOTE 1: Integrity requirements may include GNSS integrity and/or RAT- dependent integrity.
  • Step 5 If the wireless device 22 is requesting its own location, the actions described in clause 6.11 may be performed together with the actions described for step 12 in clause 6.1.2 if a scheduled location time is present. If the wireless device 22 is instead requesting location assistance data, the LMF 98 may transfer this data to the wireless device 22 as described in clause 6.11.1. The LMF 98 may determine the exact location assistance data to transfer according to the type of data specified by the wireless device 22, the wireless device location capabilities, the MO-LR subscribed assistance data and the current cell. NOTE 3: If integrity requirements are received in step 4, LMF 98 may determine to use GNSS positioning method and/or RAT-dependent positioning method. For RAT-dependent positioning method, either the wireless device 22 or LMF 98 may perform the Integrity computation. Step 6.
  • the service operation may also include the UE Positioning Capability if the UE Positioning Capability is received in step 5, including an indication that the capabilities are non-variable and not received from AMF 96 in step 4. If the wireless device 22 is requesting location assistance data, steps 7 to 12 are skipped. Step 7. If the location estimate was successfully obtained, the AMF 96 invokes the Ngmlc_Location_LocationUpdate service operation towards to the VGMLC assigned in the step 2.
  • the service operation may carry the identity of the wireless device 22, the event causing the location estimate (5GC-MO-LR) and the location estimate, its age, obtained accuracy indication and the LCS QoS Class requested by the target wireless device 22.
  • the service operation may include the pseudonym indicator, the identity of the LCS Client, AF ID, the GMLC address, the timestamp of the location estimate and the Service Type specified by the wireless device 22, if available.
  • Integrity results reporting to client Similar to the integrity result reporting modes described above, the integrity results to the client may be reported in one or more of the following formats: • In one format, the integrity results to the client include the PL, and the entity that computed the PL (e.g., LMF, UE or both): • In another format, the integrity results to the client include a boolean variable to indicate if Integrity requirements are met or not, additionally: o When the boolean variable is set to true, indicating that the integrity requirement is met (no Integrity Event is flagged), then the integrity entity that determined the Boolean variable result (e.g., LMF, UE or both) is also sent.
  • the integrity results to the client include the PL, and the entity that computed the PL (e.g., LMF
  • the target TIR and/or achievable TIR are optional sent, and the integrity entity (e.g., LMF, UE or both) that calculate the achievable TIR is also sent.
  • the integrity entity e.g., LMF, UE or both
  • 3GPP contributions may be drafted in the following manners: Draft CR to TS 29.515 V17.8.0 Reason for Change:
  • the NF consumer may provide the integrity requirements for the positioning request and network/UE will take the integrity requirement into account when handling the positioning request. However, when reporting the UE location to the NF consumer, the integrity result is not provided, e.g. whether the integrity requirement is fulfilled or not, the actual integrity value for the positioning measurement.
  • the integrity result will include the following information: - The integrity computing entities who calculated (and determined) the integrity result. - The calculated PL value, the LCS client use this information to determine by itself whether the system is available or not. - The indication whether the integrity requirements met or not. o when the integrity requirements are not met, the achieved TIR. Summary of change: 1/ Specify the new data types for Integrity Result. 2/ Add the integrity Result in Location Data and Event Notify Data. 3/ Update OpenAPI accordingly.
  • the service operation is used during the procedures: - 5GC-MT-LR Procedure for the commercial location service (see 3GPP TS 23.273 [4], clause 6.1.2) - Deferred 5GC-MT-LR Procedure for Periodic, Triggered and UE Available Location Events (see 3GPP TS 23.273 [4], clause 6.3.1)
  • the ProvideLocation service operation is invoked by a NF Service Consumer, e.g. a NEF or GMLC, towards the GMLC to request to provide the location information (geodetic location and, optionally local and/or civic location) for a target UE or to subscribe to periodic or triggered deferred location for a target UE.
  • a NF Service Consumer e.g. a NEF or GMLC
  • the response body shall contain the parameters related to the determined position of the UE if any (geodetic position, local position, civic location, positioning methods, integrity result, ). If geographic area(s) are received in the request for area event, the GMLC (or V- GMLC when roaming) shall convert the received geographic area(s) into a corresponding list of cell and/or tracking area identities when invoking AMF location services.
  • EventNotify for a single UE The service operation is used during the procedure: - Deferred 5GC-MT-LR Procedure for Periodic, Triggered and UE Available Location Events (see 3GPP TS 23.273 [4], clause 6.3.1 or clause 6.3.2)
  • the EventNotify for a single UE enables the consumer NF (e.g. (H)GMLC, NEF) to get notified about the geodetic and optionally local and/or civic location, the completion or activation of deferred location, mobility to a different AMF/MME of a UE with deferred location for a target UE when some certain events are detected. See Figure 5.2.2.5.2-1. (FIG.18 in the present document) 1.
  • H consumer NF
  • the GMLC shall send an HTTP POST to the locationNotificationUri to send a notification.
  • the input parameters for the notification (Notification Correlation ID, UE (SUPI and if available GPSI), Type of location related event (e.g. deferred location for the UE available event, activation of location for periodic or triggered location, mobility of a target UE to a new AMF or MME for a deferred location, Geodetic Location, Local Location, 2030 Location, Position Methods Used, serving LMF identification, integrity result, etc.) should be included in the HTTP POST request body.
  • 6.1.5.1 This clause specifies the application data model supported by the API.
  • Table 6.1.5.1-1 specifies the data types defined for the Ngmlc_Location service based interface protocol.
  • Table 6.1.5.1-1 Ngmlc_Location specific Data Types 6.1.5.2.3 Type: LocationData Table 6.1.5.2.3-1: Definition of type LocationData ype: EventNotifyData Table 6.1.5.2.6-1: Definition of type EventNotifyData ype: IntegrityProtectionLevel Table 6.1.5.2.xx-1: Definition of type IntegrityProtectionLevel 6.1.5.2.yy Type: IntegrityResult Table 6.1.5.2.yy-1: Definition of type IntegrityResult 6.1.5.3.x
  • Enumeration IntegrityComputingEntity The enumeration IntegrityDeterminingEntity represents the entity who calculated (and determined) the integrity result. It shall comply with the provisions defined in table 6.1.5.3.x-1.
  • the integrity result is not provided, e.g. whether the integrity requirement is fulfilled or not, the actual integrity value for the positioning measurement. Without such information, the NF consumer cannot aware the quality of the positioning measurement and may misuse the UE location with certain business logic.
  • the integrity result will include the following information: - The integrity computing entities who calculated (and determined) the integrity result. - The calculated PL value, the LCS client use this information to determine by itself whether the system is available or not. - The indication whether the integrity requirements met or not. o when the integrity requirements are not met, the achieved TIR Summary of Change: 1/ Add the integrity Result in Location Data and Event Notify Data. 2/ Update OpenAPI accordingly.
  • the integrity result is not provided, e.g. whether the integrity requirement is fulfilled or not, the actual integrity value for the positioning measurement. Without such information, the NF consumer cannot aware the quality of the positioning measurement and may misuse the UE location with certain business logic.
  • the integrity result will include the following information: - The integrity computing entities who calculated (and determined) the integrity result. - The calculated PL value, the LCS client use this information to determine by itself whether the system is available or not. - The indication whether the integrity requirements met or not. o when the integrity requirements are not met, the achieved TIR Summary of Change: 1/ Add the integrity Result in Location Data and Event Notify Data. 2/ Update OpenAPI accordingly.
  • Consequence if not approved The NF consumer cannot be aware of the system availability and may misuse the UE location when the integrity requirements are not met. 5.2.2.2.2 Retrieve UE Location This procedure allows a consumer NF to request the location information (geodetic location and, optionally, local and/or civic location) for a target UE or to activate periodic or triggered deferred location for a target UE. See Figure 5.2.2.2.2-1 (FIG.19 in the present document). 2a. On success, "200 OK" shall be returned.
  • the response body shall contain the parameters related to the determined position of the UE if any (geodetic position, local location, civic location, positioning methods, integrity result, ...); 5.2.2.3.2 Periodic or Triggered Event Notification This procedure notifies the NF Service Consumer (i.e. GMLC) about event information related to periodic or triggered location of a target UE.
  • GMLC NF Service Consumer
  • the LMF shall send a POST request to the GMLC callback URI determined as described above.
  • the request body shall include a notification correlation ID (LDR reference), the UE identification (SUPI and if available GPSI), the type of event and may include a geodetic location, local location, civic location, position methods used, and other available parameters related to the position if any (e.g. Velocity, Altitude etc.), H-GMLC callback URI (if the NF consumer is a V-GMLC) , integrity result, and serving LMF identification.
  • LDR reference notification correlation ID
  • SUPI UE identification
  • GPSI GPSI
  • H-GMLC callback URI if the NF consumer is a V-GMLC
  • integrity result e.g.
  • serving LMF identification e.g.
  • 6.1.6.1 General This clause specifies the application data model supported by the API.
  • Example A4. The network node of any of Examples A1-A3, wherein an indication of positioning integrity from the wireless device includes an indication of a radio access technology (RAT)-dependent positioning integrity.
  • Example A5. The network node of any of Examples A1-A4, wherein the network node, radio interface and/or processing circuitry are further configured to receive a global navigation satellite system (GNSS) integrity.
  • GNSS global navigation satellite system
  • Example A6 The network node of any of Examples A1-A5, wherein the integrity result includes a protection level, PL, and an entity that determined the PL.
  • a method implemented in a network node configured to communicate with a wireless device comprising: receiving an integrity result from one of a wireless device and a location management function, the one of the wireless device and the location management function being a positioning integrity entity; and sending to a location services (LCS) client an indication of which of the wireless device and the location management function is the positioning integrity entity for each of a plurality of positioning sessions.
  • Example B2 The method of Example B1, wherein the indication of positioning integrity entity includes integrity results determined by the positioning integrity entity.
  • Example B3. The method of any of Examples B1 and B2, wherein the indication of positioning integrity entity includes integrity results verified by the one of the wireless device and the location management function that is not the positioning integrity entity.
  • Example B3 The method of any of Examples B1-B3, wherein an indication of positioning integrity from the wireless device includes an indication of a radio access technology (RAT)-dependent positioning integrity.
  • Example B5. The method of any of Examples B1-B4, further comprising receiving a global navigation satellite system (GNSS) integrity.
  • Example B6. The method of any of Examples B1-B5, wherein the integrity result includes a protection level, PL, and an entity that determined the PL.
  • Example C1 The method of any of Examples B1-B3, wherein an indication of positioning integrity from the wireless device includes an indication of a radio access technology (RAT)-dependent positioning integrity.
  • RAT radio access technology
  • Example B6 The method of any of Examples B1-B5, wherein the integrity result includes a protection level, PL, and an entity that determined the PL.
  • a core network node configured to communicate with a wireless device, the core network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: receive from a second network node an indication indicating which of at least one of a first wireless device and a location management function is a position integrity entity; and determine via an access and mobility function (AMF) a positioning integrity result based at least in part on the indication of the position integrity entity.
  • AMF access and mobility function
  • Example C1 The core network node of Example C1, wherein the core network node, radio interface and/or processing circuitry are configured to transmit to a second wireless device an indication of an identity of the position integrity entity.
  • Example C4 The core network node of any of Examples C1-C3, wherein determining the positioning integrity result further includes determining an age and accuracy of the position integrity result.
  • Example C5. The core network node of any of Examples C1-C5, wherein the integrity result includes a protection level, PL, and an entity that determined the PL.
  • Example D1 The core network node of Example C1-C3, wherein the integrity result includes a protection level, PL, and an entity that determined the PL.
  • a method implemented in a core network node configured to communicate with a wireless device and a second network node comprising: receiving from the second network node an indication indicating which of at least one of a first wireless device and a location management function is a position integrity entity; and determining via an access and mobility function a positioning integrity result based at least in part on the indication of the position integrity entity.
  • Example D2 The method of Example D1, further comprising transmitting to a second wireless device an indication of the position integrity result.
  • Example D3 The method of Example D1, further comprising transmitting to a second wireless device an indication of an identity of the position integrity entity.
  • Example D4 The method of any of Examples D1-D3, wherein determining the positioning integrity result further includes determining an age and accuracy of the position integrity result.
  • Example D5. The method of any of Examples D1-D5, wherein the integrity result includes a protection level, PL, and an entity that determined the PL.
  • Example E1. A wireless device configured to communicate with a network node, the wireless device configured to, and/or comprising a radio interface and/or processing circuitry configured to: transmit radio access technology (RAT)-dependent positioning integrity result to the network node, the positioning integrity result including at least one of a location request, a quality of service request and an identity of a location management function to receive the positioning integrity result.
  • RAT radio access technology
  • Example E2 The wireless device of Example E1, wherein the positioning integrity result includes a request for one of a position and location assistance data.
  • Example E1 and E2 wherein the wireless device, radio interface and/or processing circuitry are further configured to receive from a location management function a scheduled location time for determining the positioning integrity result.
  • Example E4 The wireless device of any of Example E1-E3, wherein the wireless device, radio interface and/or processing circuitry are further configured to perform an integrity computation and include the integrity computation in the positioning integrity result.
  • Example E5. The wireless device of any of Examples E1-E5, wherein the integrity result includes a protection level, PL, and an entity that determined the PL.
  • Example F1 protection level
  • a method implemented in a wireless device comprising: transmitting radio access technology (RAT)-dependent positioning integrity result to the network node, the positioning integrity result including at least one of a location request, a quality of service request and an identity of a location management function to receive the positioning integrity result.
  • RAT radio access technology
  • Example F2 The method of Example F1, wherein the positioning integrity result includes a request for one of a position and location assistance data.
  • Example F3 The method of any of Examples F1 and F2, further comprising receiving from a location management function a scheduled location time for determining the positioning integrity result.
  • Example F4 The method of any of Example F1-F3, further comprising performing an integrity computation and including the integrity computation in the positioning integrity result.
  • the integrity result includes a protection level, PL, and an entity that determined the PL.
  • the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware.
  • the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that may be executed by a computer.
  • Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.
  • These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • These computer program instructions may also be stored in a computer readable memory or storage medium that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
  • Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer.
  • the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider an Internet Service Provider

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

A method, system and apparatus for indicating a positioning integrity entity to a client for radio access technology, RAT, dependent positioning are disclosed. According to one aspect, a method in a network node (16) includes receiving (134) an integrity result from one of a wireless device (22) and a location management function (98), the one of the wireless device (22) and the location management function (98) being a positioning integrity entity. The method also includes sending (136) to a location services client an indication of which of the wireless device (22) and the location management function (98) is the positioning integrity entity for each of a plurality of positioning sessions.

Description

METHODS TO INDICATE POSITIONING INTEGRITY ENTITY TECHNICAL FIELD The present disclosure relates to wireless communications, and in particular, to methods for indicating a positioning integrity entity to a client for radio access technology (RAT) dependent positioning. BACKGROUND The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices or user equipment (UE), as well as communication between network nodes and between wireless devices. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks. Positioning has been a topic of LTE standardization since 3GPP Technical Release 9 (3GPP Rel-9). An objective is to fulfill regulatory requirements for emergency call positioning. Positioning in NR is proposed to be supported by the architecture shown in FIG.1. The location management function (LMF) is the location node in NR. There are also interactions between the location node and the gNodeB (hereinafter referred to as a network node) via the NR positioning protocol A (NRPPa). The interactions between the network node and the device is supported via the Radio Resource Control (RRC) protocol. Note 1: The gNB and ng-eNB may not always both be present. Note 2: When both the gNB and ng-eNB are present, the NG-C interface is only present for one of them. In the legacy, i.e., existing, LTE standards, the following techniques are supported: • Enhanced Cell ID. Essentially cell ID information to associate the device to the serving area of a serving cell, and then additional information to determine a finer granularity position; • Assisted GNSS. GNSS information retrieved by the device, supported by assistance information provided to the device from E-SMLC; • OTDOA (Observed Time Difference of Arrival). The device estimates the time difference of reference signals from different base stations and sends to the E-SMLC for multilateration; • UTDOA (Uplink TDOA). The device is requested to transmit a specific waveform that is detected by multiple location measurement units (e.g. an eNB) at known positions. These measurements are forwarded to E-SMLC for multilateration; and • Sensor methods such as Biometric pressure sensor which provides vertical position of the device and Inertial Motion Unit (IMU) which provides displacement. All of these methods are also being standardized for NR in 3GPP Rel-15 (limited functionality) and 3GPP Rel-16, and planned to be enhanced in 3GPP Rel-17. The positioning modes may be categorized in the following three areas: • UE-Assisted: The UE performs measurements with or without assistance from the network and sends these measurements to the E-SMLC where the position calculation may take place; • UE-Based: The UE performs measurements and calculates its own position with assistance from the network; and • Standalone: The UE performs measurements and calculates its own without network assistance. Until now, accuracy has been the main positioning performance metrics which have been discussed and supported by the requirements in 3GPP. Emerging applications relying on high-precision positioning technology in autonomous applications (e.g., automotive), have created a need for high integrity and reliability in addition to high accuracy. The 5G service requirements specified in 3GPP Technical Standard (TS) 22.261 include the need to determine the reliability, and the uncertainty or confidence level, of the position-related data. In 3GPP RP-213561, a new study item (SI) on “New SID on Study on expanded and improved NR positioning” has been approved in which one task is to study solutions for Integrity for RAT dependent positioning techniques; identify the error sources; study methodologies, procedures, signaling, etc., for determination of positioning integrity for both UE-based and UE-assisted positioning; and focus on reuse of concepts and principles being developed for RAT-Independent global navigation satellite system (GNSS) positioning integrity, where possible. Integrity Integrity is the measure of trust that may be placed in the correctness of information supplied by a navigation/location system. For example, integrity includes the ability of a system to provide timely warnings to user receivers in case of a failure. An example of a failure may be taken from a radio access technology (RAT) independent positioning method such as assisted GNSS. If a satellite is malfunctioning, it should be detected by the system and the user should be informed not to use this satellite. Example use cases and scenarios: Any use-case related to positioning in Ultra Reliable and Low Latency Communication (URLLC) naturally requires high integrity performance. Some use-cases include V2X, autonomous driving, UAV (drones), eHealth, rail and maritime, emergency and mission critical uses. In use-cases in which large errors may lead to serious consequences such as health-related impacts, wrong legal decisions or wrong charge computation, etc., the integrity reporting becomes crucial. FIG.2 illustrates a definition of accuracy, precision, validity, reliability and integrity. Basically, it may be concluded that accuracy is the same term as validity in positioning. Also, terms such as reliability, precision, uncertainty and confidence level may in some cases be used interchangeably. However, integrity requires the evaluation of both accuracy and reliability. Integrity key performance indicators (KPIs) and events A few example Integrity KPIs are defined that may help in identifying different integrity events: Alert Limit (AL): is the largest error allowable for safe operation; Time to Alert (TTA): is the maximum allowable elapsed time from the onset of a positioning failure until the equipment announces the alert; Integrity Risk (IR): is the maximum probability of providing a signal that is out of tolerance without warning the user in a given period of time; Protection Level (PL): is the statistical error bound computed to guarantee that the probability of the absolute position error exceeding the said number is smaller than or equal to the target integrity risk; Target Integrity Risk (TIR): The probability that the positioning error exceeds the Alert Limit (AL) without warning the user within the required Time-to-Alert (TTA). FIG.3 shows an example with the Stanford plot in which all the possible integrity operation and events may be explained in its different regions: Nominal Operation is when PE < PL < AL; System unavailable is when AL < PL; Misleading Operation is when PL < PE; Hazardously Operation is when PL < AL < PE; Integrity Failure is an integrity event that lasts for longer than the TTA and with no alarm raised within the TTA; Misleading Information (MI) is an integrity event occurring when, being the system declared available, the position error exceeds the protection level but not the alert limit; and/or Hazardously Misleading Information (HMI) is an integrity event occurring when, being the system declared available, the position error exceeds the alert limit. Integrity result reporting modes In 3GPP Technical Report (TR) 38.857 V17.0.0, two modes of integrity result reporting are also identified below for consideration in the work item (WI): • Mode 1 of Integrity Result Reporting : PL Reporting The integrity computing entity calculates the PL based on the measurement assistance information and TIR. Then, the calculated PL is directly reported to where the location services (LCS) client resides (Network or UE). Hence, the integrity computing entity does not judge whether the positioning system is still available. It simply provides whatever PL value it has obtained. It is left to the LCS client itself to determine if the positioning system is still available based on the reported PL. • Mode 2 of Integrity Result Reporting : Integrity Event Flagging The integrity computing entity calculates the PL based on the measurement assistance information and TIR. Then, the integrity computing entity further compares the calculated PL with the given AL to determine if the positioning system is still available to offer trustable position estimation. Thus, the integrity computing entity may only have to report a binary flag (0 and 1) to indicate whether the positioning system is available. Thus, in this case, the LCS client may be directly informed about the system availability, without conducting further evaluation by itself. Location Service Procedures The location services may be categorized into: - 5GC-MT-LR that is applicable to a request from a location services (LCS) client for a current location of the target UE, and assuming that the LCS client is authorized to use the location service and no privacy verification is required; - 5GC-MO-LR that is applicable to a request by the UEto the serving public land mobile network (PLMN) for obtaining the location related information of itself or just assistance data; and - Deferred 5GC-MT-LR for Periodic, Triggered and UE Available Location Events. FIG.4 illustrates the 5GC-MT-LR procedure for the commercial location service. This procedure is applicable to a request from an LCS client or application function (AF) for a current location of the target UE, and it is assumed that: - Privacy verification may be required for the location service request; - The LCS client or the AF needs to be authorized to use the location service. 1. The LCS Client or the AF (via a network exposure function (NEF)) sends a request to the (H) gateway mobile location center (GMLC) for a location and optionally a velocity for the target UE which may be identified by a general public subscription identifier (GPSI) or a subscription permanent identifier (SUPI). The request may include the required quality of service (QoS), supported geographical area description (GAD) shapes and other attributes. (H)GMLC (for 1a) or NEF (for 1b) authorizes the LCS Client or the AF for the usage of the LCS service. If the authorization fails, step 2-23 are skipped and (H)GMLC (for 1a) or NEF (for 1b) responds to the LCS Client or the AF the failure of the service authorization in step 24. In some cases, the (H)GMLC derives the GPSI or SUPI of the target UE and possibly the QoS from either subscription data or other data supplied by the LCS Client or AF. The LCS request may also carry the Service Identity (see 3GPP TS 22.071) and the codeword and the service coverage information. The (H)GMLC may verify that the Service Identity received in the LCS request matches one of the service identities allowed for the LCS client or AF. If the service identity does not match one of the service identities for the LCS client or AF, the (H)GMLC shall reject the LCS request. Otherwise, the (H)GMLC may map the received service identity in a corresponding service type. The LCS service request may include a scheduled location time if a current location of the UE is required at a specific time in the future. The LCS service request may include integrity requirements. NOTE 1: In this release of 3GPP specifications, integrity requirements are only for GNSS integrity. If the LCS service request contains the pseudonym of the target UE and the (H)GMLC cannot resolve the pseudonym mediation device (PMD) address from the pseudonym, the (H)GMLC itself determines the verinym (GPSI or SUPI) of the target UE. If the (H)GMLC may resolve the address of PMD from the pseudonym, the HGMLC requests the verinym from its associated PMD. If (H)GMLC is not able to obtain the verinym of the target UE, the (H)GMLC shall cancel the location request. If a scheduled location time is not included and the requested type of location is "current or last known location" and the requested maximum age of location information is available, the (H)GMLC verifies whether it stores the previously obtained location estimate of the target UE. If the HGMLC stores the location estimate and timestamp of the location estimate (if available) and the location estimate satisfies the requested accuracy and the requested maximum age of location, the (H)GMLC checks the result of the privacy check at step 2. If the result of the privacy check for call/session unrelated class is "Location allowed without notification" then steps 3-23 may be skipped. 1b-1 AF sends the Nnef_EventExposure_Subscribe to the NEF. 1b-2 The NEF identifies based on the QoS attribute received from the location request that higher than cell-ID level location accuracy is required and invokes the Ngmlc_Location_ProvideLocation_Request service operation to the (H)GMLC, which contains the attributes received from the AF request. The NEF may also invoke the Ngmlc_Location_ProvideLocation_Request service operation to the (H)GMLC for lower than cell-ID location accuracy as an implementation option or if a scheduled location time is included. If a location is required for more than one UE, the steps below may be repeated and in that case, the NEF or HGMLC receiving location request shall verify whether the number of Target UEs in the Nnef_EventExposure_Subscribe or LCS request is equal to or less than the Maximum Target UE Number of the LCS client. If Maximum Target UE Number is exceeded, the NEF or HGMLC shall reject the Nnef_EventExposure_Subscribe or LCS request, the steps 2-23 are skipped, and then the GMLC respond to the client with proper error cause in the step 24. NOTE 2: If cell-ID level or lower than cell-ID level location accuracy is required in the location request, the NEF may invoke an Namf_EventExposure_Subscribe service operation to subscribe location event reporting from the access and mobility management function (AMF) for the target UE as further described in clause 6.5 of the relevant 3GPP technical standard. 2. The (H)GMLC invokes a Nudm_SDM_Get service operation towards the unified data manager (UDM) of the target UE to get the privacy settings of the UE identified by its GPSI or SUPI. The UDM returns the target UE Privacy setting of the UE. The (H)GMLC checks the UE LCS privacy profile. If the target UE is not allowed to be located, steps 3-23 are skipped. 3. The (H)GMLC invokes a Nudm_UECM_Get service operation towards the UDM of the target UE with GPSI or SUPI of this UE. The UDM returns the network addresses of the current serving AMF and additionally the address of a VGMLC (for the roaming case). If the location request is an immediate location request, the (H)GMLC checks the country codes of the serving node addresses. If the (H)GMLC finds the current AMF is out of the service coverage of the (H)GMLC, the (H)GMLC returns an appropriate error message to the LCS client or AF (via NEF). NOTE 3: The UDM is aware of the serving AMF address at UE registration on an AMF as defined in clause 4.2.2.2.2 of 3GPP TS 23.502 [19]. The UDM is aware of a serving VGMLC address at UE registration on an AMF as defined in clause 4.2.2.2.2 of 3GPP TS 23.502 [19]. NOTE 4: The HGMLC may also query the HSS of the target UE for a serving mobile management entity (MME) address as described in clause 9.1.1 of 3GPP TS 23.271 [4]. The EPC-MT-LR procedure described in clause 9.1.15 of 3GPP TS 23.271 [4], excluding the UE availability event, may then be performed instead of steps 4-23, e.g. if the home subscriber server (HSS) returns an MME address but the UDM does not return an AMF address. 4. For a non-roaming case, this step is skipped. In the case of roaming, the HGMLC may receive an address of a VGMLC (together with the network address of the current serving AMF) from the UDM in step 3, otherwise, the HGMLC may use the NRF service in the HPLMN to select an available VGMLC in the VPLMN, based on the VPLMN identification contained in the AMF address received in step 3. The HGMLC then sends the location request to the VGMLC by invoking the Ngmlc_Location_ProvideLocation service operation towards the VGMLC. In the cases when the HGMLC did not receive the address of the VGMLC, or when the VGMLC address is the same as the HGMLC address, or when both PLMN operators agree, the HGMLC sends the location service request message to the serving AMF. In this case, step 4 is skipped. If the result of privacy check indicates that the verification based on current location is needed, the HGMLC shall send a location request to the VGMLC (in the case of roaming) or to the AMF (in the case of non-roaming) indicating "positioning allowed without notification" and VGMLC shall invoke an Namf_Location_ProvidePositioningInfo Request service operation towards the AMF at step 5. H-GMLC also provides the LCS client type of AF, if received in step 41b-2, or LCS client type of LCS client and other attributes to be sent to AMF in step 5. 5. In cases of roaming, the VGMLC first authorizes that the location request is allowed from this HGMLC, PLMN or from this country. If not, an error response is returned. The (H)GMLC or VGMLC invokes the Namf_Location_ProvidePositioningInfo service operation towards the AMF to request the current location of the UE. The service operation includes the SUPI, the client type and may include the required LCS QoS, supported GAD shapes, scheduled location time, service type and other attributes as received or determined in step 1. NOTE 5: The location request forwarded at step 4 and step 5 may also carry the result of the privacy check in step 2 which may include a codeword provided by the LCS Client or AF and an indication of a privacy related action as described in clause 5.4. 6. If the UE is in connection management (CM) IDLE state, the AMF initiates a network triggered Service Request procedure as defined in clause 4.2.3.3 of 3GPP TS 23.502 to establish a signalling connection with the UE. If signalling connection establishment fails, steps 7-13 are skipped and the AMF answers to the GMLC in step 14 with the last known location of the UE (i.e. Cell ID) together with the age of this location. 7. If the indicator of privacy check related action indicates that the UE must either be notified or notified with privacy verification and if the UE supports LCS notification (according to the UE capability information), a notification invoke message is sent to the target UE, indicating the identity of the LCS client and the service type (if that is both supported and available) and whether privacy verification is required. 8. The target UE notifies the UE user of the location request and, if privacy verification was requested, waits for the user to grant or withhold permission. The UE then returns a notification result to the AMF indicating, if privacy verification was requested, whether permission is granted or denied for the current LCS request. If the UE user does not respond after a predetermined time period, the AMF shall infer a “no response” condition. The AMF shall return an error response in step 14 and if roaming VGMLC in step 15 to the HGMLC if privacy verification was requested and either the UE user denies permission or there is no response with the indication received from the (H)GMLC indicating barring of the location request and steps 10~13 are skipped. The notification result may also indicate the Location Privacy Indication setting for subsequent LCS requests; i.e. whether subsequent LCS requests, if generated, will be allowed or disallowed by the UE. The Location Privacy Indication may also indicate a time for disallowing the subsequent LCS requests. 9. The AMF invokes the Nudm_ParameterProvision_Update (LCS privacy) service operation to store in the UDM the Location Privacy Indication information received from the UE. The UDM may then store the updated UE privacy setting information into the UDR as the “LCS privacy” Data Subset of the Subscription Data. 10-13. Steps 10-13 are the same as steps 6-9 defined in clause 6.1.1 of the relevant 3GPP technical standard with the addition that service type may be indicated towards the LMF and the exception that the LMF may determine the UE location in local coordinates or geographical co-ordinates or both. If the supported GAD shapes is not received in step 11 or Local Co-ordinates is not included in the supported GAD shapes, the LMF shall determine a geographical location. If a scheduled location time is provided at step 5, steps 11 and 12 include the following additional differences. 11. The AMF includes the scheduled location time in the Nlmf_Location_DetermineLocation service operation sent towards the LMF. 12. When sending a location request to the UE, the LMF may include the scheduled location time. NOTE 6: If integrity requirements are received in step 11, LMF may determine to use GNSS positioning method. NOTE 7: LMF does not deliver the scheduled location time to NG-RAN as part of step 12. NOTE 8: The LMF may send a location request to the UE at step 12 containing the scheduled location time sometime before the scheduled location time to allow the UE to enter CM Connected state shortly before the scheduled location time. 14. The AMF returns the Namf_Location_ProvidePositioningInfo Response towards the (V)GMLC (or HGMLC for roaming when the NL3 reference point is not supported) to return the current location of the UE. The service operation includes the location estimate, its age and accuracy and may include information about the positioning method and the timestamp of the location estimate. 15. In the case of roaming, the VGMLC forwards the location estimation of the target UE, its age, its accuracy and optionally the information about the positioning method received at step 14 to the HGMLC. For non-roaming scenario, this step is skipped. 16. If the privacy check in step 2 indicates that further privacy checks are needed, the (H)GMLC shall perform an additional privacy check in order to decide whether the (H)GMLC may forward the location information to the LCS client or AF or send a notification if the result of the privacy check requires the notification and verification based on current location. One example when this additional privacy check is needed is when the target UE user has defined different privacy settings for different geographical locations. When an additional privacy check is not needed, the (H)GMLC skips steps 17-23. 17. If the result of privacy checks in step 16 indicates that the notification (and verification) based on current location is needed, and in the case of roaming, the (H)GMLC shall send a location request to the VGMLC with location type indicating “notification only”. 18. The (H)GMLC or VGMLC invokes the Namf_Location_ProvidePositioningInfo service operation towards the AMF to request notification (and verification) based on current location. 19. If the UE is in CM IDLE state, the AMF initiates a network triggered Service Request procedure as defined in clause 4.2.3.3 of 3GPP TS 23.502 to establish a signalling connection with the UE. 20. If the indicator of privacy check related action indicates that the UE must either be notified or notified with privacy verification and if the UE supports LCS notification, the AMF sends a notification invoke message to the target UE, indicating the identity of the LCS client and the service type (if that is both supported and available) and whether privacy verification is required. 21. Step 21 is the same as step 8. 22. The AMF returns the Namf_Location_ProvidePositioningInfo Response towards the (V)GMLC (or HGMLC for roaming when the NL3 reference point is not supported) with an indication of the result of notification and verification procedure performed in steps 20-21. 23. In the case of roaming, the VGMLC forwards an indication of the result of notification and verification procedure to the HGMLC. For non-roaming scenario, this step is skipped. 24. The (H)GMLC sends the location service response to the LCS Client or AF (via the NEF) if the target UE is allowed to be located by the LCS Client or AF. Accordingly, NEF invokes Nnef_EventExposure_Notify or sends Nnef_EventExposure_Subscribe Response to the AF. If the location request from the LCS Client contained the pseudonym and the (H)GMLC resolved the verinym from the pseudonym in step 1, the (H)GMLC shall use the pseudonym of the target UE in the location response to the external LCS client. If the external LCS client or AF requires it, the (H)GMLC may first transform the universal location co-ordinates provided by the AMF into some local geographic reference system. The (H)GMLC may record charging information for both the LCS Client or AF and inter-network revenue charges from the AMF's network. The location service response from the (H)GMLC to the LCS Client or AF may contain the information about the positioning method used and the indication indicating whether the obtained location estimate satisfies the requested accuracy. If in step 2, step 15, step 16 or step 23, the (H)GMLC identifies that the target UE is not allowed to be located by the LCS Client or AF, it rejects the LCS service request, and optionally indicates in the response, the reason of the rejection, i.e., the target UE is not allowed to be located. If the LCS QoS Class is Assured and (H)GMLC detects that requested accuracy is not achieved, the (H)GMLC sends error response including failure cause. SUMMARY Some embodiments advantageously provide methods, systems, and apparatuses for indicating a positioning integrity entity to a client for radio access technology (RAT) dependent positioning. Some embodiments may provide methods for: • indicating which entity (wireless device, location management function ) performed the integrity result calculation to the external location services (LCS) client; and/or • how the external LCS client may use the integrity entity information to calibrate the positioning integrity results. A tag indicating the positioning integrity entity for each positioning session may be sent by the location management function to the access and mobility management function (AMF) and further to the external LCS client. Having knowledge of which entity performed the positioning integrity calculation, the external LCS client may further utilize other knowledge about that entity available to calibrate and refine the integrity results. The location management function sends positioning integrity entity information in the location service response to the AMF and the AMF may forward this information all the way to the external LCS client. The external LCS client may use the positioning integrity entity information to calibrate and refine the integrity results. Some embodiments include a flag which will inform the LCS client whether the integrity and safety computations were done by the wireless device side or by the location management function. There may be some unknown errors while computing integrity such as any residual error, wireless device hardware impairments or hardware fault. Similarly, at the location management function there may be unknown or unaccounted-for error; hence the LCS client may compensate for and take the necessary safety margins into account, and accordingly, whether they were computed by the location management function or the wireless device. External LCS clients have the possibility to use the positioning integrity entity information to calibrate and refine the integrity results. In case of failure due to wrong integrity results being provided, the responsible party for the integrity results is clear. According to one aspect, a network node configured to communicate with a wireless device, the network node configured to: receive an integrity result from one of a wireless device and a location management function, the one of the wireless device and the location management function being a positioning integrity entity; and send to a location services (LCS) client an indication of which of the wireless device and the location management function is the positioning integrity entity for each of a plurality of positioning sessions. According to this aspect, in some embodiments, the indication of positioning integrity entity includes integrity results determined by the positioning integrity entity. In some embodiments, the indication of positioning integrity entity includes integrity results verified by the one of the wireless device and the location management function that is not the positioning integrity entity. In some embodiments, an indication of positioning integrity from the wireless device includes an indication of a radio access technology (RAT)-dependent positioning integrity. In some embodiments, the network node is configured to receive a global navigation satellite system (GNSS) integrity. In some embodiments, the integrity result includes a protection level, PL, and an entity that determined the PL. According to another aspect, a method implemented in a network node configured to communicate with a wireless device is provided. The method includes: receiving an integrity result from one of a wireless device and a location management function , the one of the wireless device and the location management function being a positioning integrity entity; and sending to a location services (LCS) client an indication of which of the wireless device and the location management function is the positioning integrity entity for each of a plurality of positioning sessions. According to this aspect, in some embodiments, the indication of positioning integrity entity includes integrity results determined by the positioning integrity entity. In some embodiments, the indication of positioning integrity entity includes integrity results verified by the one of the wireless device and the location management function that is not the positioning integrity entity. In some embodiments, an indication of positioning integrity from the wireless device includes an indication of a radio access technology (RAT)-dependent positioning integrity. In some embodiments, the method includes receiving a global navigation satellite system (GNSS) integrity. In some embodiments, the integrity result includes a protection level, PL, and an entity that determined the PL. According to yet another aspect, a core network node configured to communicate with a wireless device is provided. The core network node is configured to: receive from a second network node an indication indicating which of at least one of a first wireless device and a location management function is a position integrity entity; and determine via an access and mobility function a positioning integrity result based at least in part on the indication of the position integrity entity. According to this aspect, in some embodiments, the core network node is configured to transmit to a second wireless device an indication of the position integrity result. In some embodiments, the core network node is configured to transmit to a second wireless device an indication of an identity of the position integrity entity. In some embodiments, determining the positioning integrity result further includes determining an age and accuracy of the position integrity result. In some embodiments, the integrity result includes a protection level, PL, and an entity that determined the PL. According to another aspect, a method implemented in a core network node configured to communicate with a wireless device and a second network node is provided. The method includes receiving from the second network node an indication indicating which of at least one of a first wireless device and a location management function is a position integrity entity; and determining via an access and mobility function, a positioning integrity result based at least in part on the indication of the position integrity entity. According to this aspect, in some embodiments, the method includes transmitting to a second wireless device an indication of the position integrity result. In some embodiments, the method includes transmitting to a second wireless device an indication of an identity of the position integrity entity. In some embodiments, determining the positioning integrity result further includes determining an age and accuracy of the position integrity result. In some embodiments, the integrity result includes a protection level, PL, and an entity that determined the PL. According to another aspect, a wireless device configured to communicate with a network node is provided. The wireless device is configured to: transmit radio access technology (RAT)-dependent positioning integrity result to the network node, the positioning integrity result including at least one of a location request, a quality of service request and an identity of a location management function to receive the positioning integrity result. According to this aspect, in some embodiments, the positioning integrity result includes a request for one of a position and location assistance data. In some embodiments, the wireless device is configured to receive from the location management function, a scheduled location time for determining the positioning integrity result. In some embodiments, the wireless device is configured to perform an integrity computation and include the integrity computation in the positioning integrity result. In some embodiments, the integrity result includes a protection level, PL, and an entity that determined the PL. According to yet another aspect, a method implemented in a wireless device configured to communicate with network node is provided. The method includes transmitting radio access technology (RAT)-dependent positioning integrity result to the network node, the positioning integrity result including at least one of a location request, a quality of service request and an identity of a location management function to receive the positioning integrity result. According to this aspect, in some embodiments, the positioning integrity result includes a request for one of a position and location assistance data. In some embodiments, the method includes receiving from the location management function, a scheduled location time for determining the positioning integrity result. In some embodiments, the method includes performing an integrity computation and including the integrity computation in the positioning integrity result. In some embodiments, the integrity result includes a protection level, PL, and an entity that determined the PL. BRIEF DESCRIPTION OF THE DRAWINGS A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein: FIG.1 illustrates NG-RAN 3GPP Rel-15 LCS protocols; FIG.2 illustrates differences between accuracy, precision, validity, reliability, integrity and certainty; FIG.3 is a Stanford plot; FIGS.4 and 4A depict a timing diagram of a procedure for a commercial location service; FIG.5 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure; FIG.6 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure; FIG.7 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure; FIG.8 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure; FIG.9 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure; FIG.10 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure; FIG.11 is a flowchart of an example process in a network node for indicating a positioning integrity entity to a client for radio access technology (RAT) dependent positioning; FIG.12 is a flowchart of an example process in a core network node for indicating positioning integrity results; FIG.13 is a flowchart of an example process in a wireless device for indicating a positioning integrity entity to a client for radio access technology (RAT) dependent positioning; FIG.14 is a timing diagram of RAT-dependent positioning and integrity calculation and integrity entity indication procedures according to principles set forth herein; FIGS.15 and 15A depict a timing diagram of a commercial location service procedure modified according to principles disclosed herein; FIG.16 is another timing diagram of a commercial location service procedure modified according to principles set forth herein; FIG.17 “Figure 5.2.2.2.2-1: ProvideLocation Request/Response for a target UE” from 3GPP TS 29.515 V17.8.0; FIG.18 ” Figure 5.2.2.5.2-1: EventNotify Notification for a single UE” from 3GPP TS 29.515 V17.8.0; FIG.19 “Figure 5.2.2.2.2-1: DetermineLocation Request” from 3GPP TS 29.572 V17.9.0; and FIG.20 “Figure 5.2.2.3.2-1: EventNotify Request” from 3GPP TS 29.572 V17.9.0. DETAILED DESCRIPTION Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to for indicating a positioning integrity entity to a client for radio access technology (RAT) dependent positioning. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description. As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication. In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections. The term “network node” used herein may be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi- standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device such as a wireless device or a radio network node. In some embodiments, the non-limiting terms wireless device or a user equipment (UE) are used interchangeably. The wireless device herein may be any type of wireless device capable of communicating with a network node or another wireless device over radio signals, such as wireless device. The wireless device may also be a radio communication device, target device, device to device (D2D) wireless device, machine type wireless device or wireless device capable of machine to machine communication (M2M), low-cost and/or low-complexity wireless device, a sensor equipped with wireless device, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (IoT) device, or a Narrowband IoT (NB-IOT) device, etc. Also, in some embodiments the generic term “radio network node” is used. It may be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH). Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure. Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, may be distributed among several physical devices. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein. Some embodiments provide for indicating a positioning integrity entity to a client for radio access technology (RAT) dependent positioning. In the current positioning support of LTE and NR systems, if the location result is supposed to be sent to the external location services client, the exact entity that calculates the position results and the integrity results are not known to the location services client. This prohibits the location services client from further calibrating the received integrity results by, e.g., prior knowledge of the entity or prior results by the same entity. Moreover, the responsible party for the integrity results is not clear in case of failure due to the provision of wrong integrity results. Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG.5 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access and mobility function and location management function may be provided by one or more network nodes in the core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device wireless device22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of wireless devices 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole wireless device is in the coverage area or where a sole wireless device is connecting to the corresponding network node 16. Note that although only two wireless devices 22 and three network nodes 16 are shown for convenience, the communication system may include many more wireless devices 22 and network nodes 16. Also, it is contemplated that a wireless device 22 may be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a wireless device 22 may have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, wireless device 22 may be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN. The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown). The communication system of FIG.5 as a whole enables connectivity between one of the connected wireless devices 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected wireless devices 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected wireless device 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the wireless device 22a towards the host computer 24. A network node 16 is configured to include an integrity unit 32 which is configured to send to a location services (LCS) client an indication of which of the wireless device and the location management function is the positioning integrity entity for each of a plurality of positioning sessions. A wireless device 22 is configured to include an integrity results unit 34 which is configured to transmit radio access technology (RAT)-dependent positioning integrity result to the network node, the positioning integrity result including at least one of a location request, a quality of service request and an identity of a location management function to receive the positioning integrity result. Within the core network 14 is a core network node 36 configured to perform location management functionsand access and mobility functions, as described below. Example implementations, in accordance with an embodiment, of the wireless device 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG.6. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory). Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24. The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a wireless device 22 connecting via an OTT connection 52 terminating at the wireless device 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In some embodiments, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22. The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the wireless device 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a wireless device 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10. In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory). Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include an integrity unit 32 which is configured to send to a location services (LCS) client an indication of which of the wireless device and the location management function is the positioning integrity entity for each of a plurality of positioning sessions. The communication system 10 further includes the wireless device 22 already referred to. The wireless device 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the wireless device 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The hardware 80 of the wireless device 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory). Thus, the wireless device 22 may further comprise software 90, which is stored in, for example, memory 88 at the wireless device 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the wireless device 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the wireless device 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the wireless device 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides. The processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by wireless device 22. The processor 86 corresponds to one or more processors 86 for performing wireless device 22 functions described herein. The wireless device 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to wireless device 22. For example, the processing circuitry 84 of the wireless device 22 may include an integrity results unit 34 which is configured to transmit radio access technology (RAT)-dependent positioning integrity result to the network node, the positioning integrity result including at least one of a location request, a quality of service request and an identity of a location management function to receive the positioning integrity result. The communication system 10 also includes the core network node 36 which includes processing circuitry 94 configured to perform access and mobility functions 96 and location management functions 98 within an integrity determination unit 100. The processing circuitry 94 is configured to control the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed by theaccess and mobility function96 and 98. The processing circuitry 94 may be implemented as processor operating according to computer instructions stored in a memory of the core network node 36. The memory is configured to store data, programmatic software code and/or other information described herein. The processing circuitry 94 may include a processor, such as a central processing unit, and memory. The processing circuitry 94 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory). Note that the functions attributed to the network node 16 and to the core network node 36 may be distributed between them or included in one or the other. The core network node 36 also includes a radio interface 100 which is configured to communication wirelessly to the network node 16 and/or a wireless device 22. The radio interface 102 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers. In some embodiments, the inner workings of the network node 16, wireless device 22, and host computer 24 may be as shown in FIG.6 and independently, the surrounding network topology may be that of FIG.5. In FIG.6, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the wireless device 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network). The wireless connection 64 between the wireless device 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the wireless device 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and wireless device 22, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the wireless device 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary wireless device signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc. Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the wireless device 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/ supporting/ending a transmission to the wireless device 22, and/or preparing/terminating/ maintaining/supporting/ending in receipt of a transmission from the wireless device 22. In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a wireless device 22 to a network node 16. In some embodiments, the wireless device 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/ supporting/ending a transmission to the network node 16, and/or preparing/ terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16. Although FIGS.5 and 6 show various “units” such as integrity unit 32, and integrity results unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry. FIG.7 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIGS.5 and 6, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a wireless device 22, which may be those described with reference to FIG.6. In a first step of the method, the host computer 24 provides user data (Block S100). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block S102). In a second step, the host computer 24 initiates a transmission carrying the user data to the wireless device 22 (Block S104). In an optional third step, the network node 16 transmits to the wireless device 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block S106). In an optional fourth step, the wireless device 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block S108). FIG.8 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG.5, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a wireless device 22, which may be those described with reference to FIGS.5 and 6. In a first step of the method, the host computer 24 provides user data (Block S110). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the wireless device 22 (Block S112). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the wireless device 22 receives the user data carried in the transmission (Block S114). FIG.9 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG.5, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a wireless device 22, which may be those described with reference to FIGS.5 and 6. In an optional first step of the method, the wireless device 22 receives input data provided by the host computer 24 (Block S116). In an optional substep of the first step, the wireless device 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block S118). Additionally or alternatively, in an optional second step, the wireless device 22 provides user data (Block S120). In an optional substep of the second step, the wireless device provides the user data by executing a client application, such as, for example, client application 92 (Block S122). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the wireless device 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the wireless device 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126). FIG.10 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG.5, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a wireless device 22, which may be those described with reference to FIGS.5 and 6. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the wireless device 22 (Block S128). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (Block S130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block S132). FIG.11 is a flowchart of an example process in a network node 16 for indicating a positioning integrity entity to a client for radio access technology (RAT) dependent positioning. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the integrity unit 32), processor 70, radio interface 62 and/or communication interface 60. Network node 16 such as via processing circuitry 68 and/or processor 70 and/or radio interface 62 and/or communication interface 60 is configured to receive an integrity result from one of a wireless device and a location management function, the one of the wireless device and the location management function being a positioning integrity entity (Block S134). The process also includes sending to a location services (LCS) client an indication of which of the wireless device and the location management function is the positioning integrity entity for each of a plurality of positioning sessions (Block S136). In some embodiments, the indication of positioning integrity entity includes integrity results determined by the positioning integrity entity. In some embodiments, the indication of positioning integrity entity includes integrity results verified by the one of the wireless device and the location management function that is not the positioning integrity entity. In some embodiments, an indication of positioning integrity from the wireless device includes an indication of a radio access technology (RAT)-dependent positioning integrity. In some embodiments, the method also includes receiving a global navigation satellite system (GNSS) integrity. In some embodiments, the integrity result includes a protection level, PL, and an entity that determined the PL. FIG.12 is a flowchart of an example process in a core network node 36 for indicating a positioning integrity entity to a client for radio access technology (RAT) dependent positioning. One or more blocks described herein may be performed by one or more elements of core network node 36 such as by one or more of processing circuitry 94 (including the integrity determination unit 102) and/or the radio interface 100. The core network node 36 such as via processing circuitry 94 and/or radio interface 100 is configured to receive from the second network node an indication indicating which of at least one of a first wireless device and a location management function is a position integrity entity (Block S138). The process also includes determining via an access and mobility function a positioning integrity result based at least in part on the indication of the position integrity entity (Block S140). In some embodiments, the method includes transmitting to a second wireless device an indication of the position integrity result. In some embodiments, the method includes transmitting to a second wireless device an indication of an identity of the position integrity entity. In some embodiments, determining the positioning integrity result further includes determining an age and accuracy of the position integrity result. In some embodiments, the integrity result includes a protection level, PL, and an entity that determined the PL. FIG.13 is a flowchart of an example process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the integrity results unit 34), processor 86, radio interface 82 and/or communication interface 60. Wireless device 22 such as via processing circuitry 84 and/or processor 86 and/or radio interface 82 is configured to transmitting radio access technology (RAT)-dependent positioning integrity result to the network node, the positioning integrity result including at least one of a location request, a quality of service request and an identity of a location management function to receive the positioning integrity result (Block S142). In some embodiments, the positioning integrity result includes a request for one of a position and location assistance data. In some embodiments, the method includes receiving from the location management function 98 a scheduled location time for determining the positioning integrity result. In some embodiments, the method includes performing an integrity computation and including the integrity computation in the positioning integrity result. In some embodiments, the integrity result includes a protection level, PL, and an entity that determined the PL. Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for indicating a positioning integrity entity to a client for radio access technology (RAT) dependent positioning. Referring to FIG.14, one or more of the following steps may be performed in some embodiments: Step 1. The external client sends an LCS service request, and when a integrity performance request is included it may also request integrity entity information and/or request desired integrity entity. Step 2. the wireless device 22 positioning and integrity performance calculation. The detailed procedures are not shown. Step 3. the LMF 98, which knows the integrity entity for the positioning session, may indicate the integrity entity together with the location response upon request as in Step 1 or it may decide by itself whether to send this integrity entity information to AMF 96 and external wireless device 22. In some embodiments, the integrity entity may have different combinations: • wireless device 22 as the only integrity entity; • LMF 98 as the only integrity entity; or • wireless device 22 and LMF 98 both act as the integrity entity: o wireless device 22 and LMF 98 work independently and return two integrity results; o Integrity results calculated by wireless device 22, and verified by LMF 98; and/or o Integrity results calculated by LMF 98, and verified by wireless device 22. In some embodiments, with integrity entity indication, the external entity is clear about the responsible party in case of failure due to wrong integrity results being provided. The external client may also utilize other information such as knowledge about the integrity entity as indicated (whether there is bias in the integrity performance result considering the algorithm and/or its hardware and computing capability). The external client may compute the bias by comparing the positioning and integrity results from other RAT-independent positioning methods to calibrate the integrity results. Moreover, by comparing the integrity results from different integrity entities, the LCS client may decide the integrity entity that provides a best integrity performance and may request that entity as the desired integrity entity for later sessions. Step 3a: The concept is also applicable when the client is in the wireless device 22. In that case, the LMF 98 may inform the wireless device LCS layer that Integrity has been computed by either the LMF 98 or the wireless device 22. UE Capability to support RAT-dependent positioning Integrity Inside Step 2, wireless device or UE Capability regarding RAT-dependent positioning Integrity is sent from the wireless device 22 to the LMF 98. The RAT-dependent positioning Integrity may have two modes: UE-based mode and UE-assisted (LMF-based) modes. wireless device 22 may indicate its capability of RAT-dependent positioning to the LMF 98 in LTE positioning protocol (LPP) ProvideCapabilityMessage. The wireless device’s RAT-dependent positioning capability may be characterized by extending the PositioningModes information element (IE) in LPP. PositioningModes The IE PositioningModes may be used to indicate several positioning modes using a bit map: -- ASN1START PositioningModes ::= SEQUENCE { posModes BIT STRING { standalone (0) ue-based (1), ue-assisted (2) ue-assistedIntegrity (3), ue-basedIntegrity (4) } (SIZE (1..8)), ... } -- ASN1STOP Configuration and Signaling Procedures The following steps are shown in FIG.15 and may be based on 3GPP TS 23.273. 1. The LCS Client or the AF (via NEF) sends a request to the (H)GMLC for a location and optionally, a velocity for the target wireless device 22 which may be identified by an GPSI or an SUPI. The request may include the required QoS, supported GAD shapes and other attributes. (H)GMLC (for 1a) or NEF (for 1b) authorizes the LCS Client or the AF for the usage of the LCS service. If the authorization fails, steps 2-23 are skipped and (H)GMLC (for 1a) or NEF (for 1b) responds to the LCS Client or the AF the failure of the service authorization in step 24. In some cases, the (H)GMLC derives the GPSI or SUPI of the target wireless device 22 and possibly the QoS from either subscription data or other data supplied by the LCS Client or AF. The LCS request may also carry the Service Identity (see 3GPP TS 22.071) and the Codeword and the service coverage information. The (H)GMLC may verify that the Service Identity received in the LCS request matches one of the service identities allowed for the LCS client or AF. If the service identity does not match one of the service identities for the LCS client or AF, the (H)GMLC may reject the LCS request. Otherwise, the (H)GMLC may map the received service identity in a corresponding service type. The LCS service request may include a scheduled location time if a current location of the wireless device 22 is required at a specific time in the future. The LCS service request may include integrity requirements. NOTE 1: Integrity requirements may include GNSS integrity and/or RAT- dependent integrity. 10-13. Steps 10-13 are the same as steps 6-9 defined in clause 6.1.1 of the relevant 3GPP Technical Standard with the addition that service type may be indicated towards the LMF 98 and the exception that the LMF 98 may determine the wireless device location in local coordinates or geographical co-ordinates or both. Either the wireless device 22 or LMF 98 may perform the integrity computation. If the supported GAD shapes is not received in step 11 or Local Co-ordinates is not included in the supported GAD shapes, the LMF 98 may determine a geographical location. If a scheduled location time is provided at step 5, steps 11 and 12 may include the following additional differences. 11. The AMF 96 may include the scheduled location time in the Nlmf_Location_DetermineLocation service operation sent towards the LMF 98. 12. When sending a location request to the wireless device 22, the LMF 98 may include the scheduled location time. NOTE 6: If integrity requirements are received in step 11, LMF 98 may determine to use GNSS positioning method and/or RAT-dependent positioning method. NOTE 7: LMF 98 may not deliver the scheduled location time to NG-RAN as part of step 12. NOTE 8: The LMF 98 may send a location request to the wireless device 22 at step 12 containing the scheduled location time sometime before the scheduled location time to allow the wireless device 22 to enter CM Connected state shortly before the scheduled location time. 14. The AMF 96 may return the Namf_Location_ProvidePositioningInfo Response towards the (V)GMLC (or HGMLC for roaming when the NL3 reference point is not supported) to return the current location of the wireless device 22 along with Integrity results and whether integrity was performed by the wireless device 22 or the LMF 98. The service operation includes the location estimate, its age and accuracy and may include information about the positioning method and the timestamp of the location estimate. Referring now to FIG.16, a number of steps are discussed in detail below. Of note, only the impacted steps are described below. Step 2. The wireless device 22 sends an MO-LR Request message included in a UL NAS TRANSPORT message. The MO-LR Request may optionally include up to three LPP positioning message(s). Different types of location services may be requested: location estimate of the wireless device 22, location estimate of the wireless device 22 to be sent to an LCS client or AF, or location assistance data. If the wireless device 22 is requesting its own location or that its own location be sent to an LCS client or AF, this message carries LCS requested QoS information (e.g. accuracy, response time, LCS QoS Class), the requested maximum age of location, the requested type of location (e.g. "current location", "current or last known location") and optionally for a current location, a scheduled location time. If the wireless device 22 is requesting that its location be sent to an LCS client, the message may include the identity of the LCS client or the AF, and may include the address of the GMLC through which the LCS client or AF (via NEF) should be accessed. In addition, a Service Type indicating which MO-LR service of the LCS Client is requested by the wireless device 22 may be included. The message also may include a pseudonym indicator to indicate that a pseudonym should be assigned by the network and transferred to the LCS Client as the wireless device's identity. The message may also include integrity requirements. NOTE 1: Integrity requirements may include GNSS integrity and/or RAT- dependent integrity. Step 5. If the wireless device 22 is requesting its own location, the actions described in clause 6.11 may be performed together with the actions described for step 12 in clause 6.1.2 if a scheduled location time is present. If the wireless device 22 is instead requesting location assistance data, the LMF 98 may transfer this data to the wireless device 22 as described in clause 6.11.1. The LMF 98 may determine the exact location assistance data to transfer according to the type of data specified by the wireless device 22, the wireless device location capabilities, the MO-LR subscribed assistance data and the current cell. NOTE 3: If integrity requirements are received in step 4, LMF 98 may determine to use GNSS positioning method and/or RAT-dependent positioning method. For RAT-dependent positioning method, either the wireless device 22 or LMF 98 may perform the Integrity computation. Step 6. When a location estimate best satisfying the requested QoS has been obtained or when the requested location assistance data has been transferred to the wireless device 22, the LMF 98 returns the Nlmf_Location_DetermineLocation Response towards the AMF 96 along with Integrity results and whether integrity was performed by the wireless device 22 or the LMF 98. The service operation may include the LCS correlation identifier, the location estimate, if this was obtained, its age and accuracy and may include information about the positioning method. If a location estimate was not successfully obtained, or if the requested location assistance data could not be transferred successfully to the wireless device 22, a failure cause may be included in the service operation. The service operation may also include the UE Positioning Capability if the UE Positioning Capability is received in step 5, including an indication that the capabilities are non-variable and not received from AMF 96 in step 4. If the wireless device 22 is requesting location assistance data, steps 7 to 12 are skipped. Step 7. If the location estimate was successfully obtained, the AMF 96 invokes the Ngmlc_Location_LocationUpdate service operation towards to the VGMLC assigned in the step 2. The service operation may carry the identity of the wireless device 22, the event causing the location estimate (5GC-MO-LR) and the location estimate, its age, obtained accuracy indication and the LCS QoS Class requested by the target wireless device 22. In addition, the service operation may include the pseudonym indicator, the identity of the LCS Client, AF ID, the GMLC address, the timestamp of the location estimate and the Service Type specified by the wireless device 22, if available. Integrity results reporting to client Similar to the integrity result reporting modes described above, the integrity results to the client may be reported in one or more of the following formats: • In one format, the integrity results to the client include the PL, and the entity that computed the PL (e.g., LMF, UE or both): • In another format, the integrity results to the client include a boolean variable to indicate if Integrity requirements are met or not, additionally: o When the boolean variable is set to true, indicating that the integrity requirement is met (no Integrity Event is flagged), then the integrity entity that determined the Boolean variable result (e.g., LMF, UE or both) is also sent. o When the boolean variable is set to false, indicating that the integrity requirement is not met (Integrity Event is flagged), then the target TIR and/or achievable TIR are optional sent, and the integrity entity (e.g., LMF, UE or both) that calculate the achievable TIR is also sent. Examples of 3GPP contributions may be drafted in the following manners: Draft CR to TS 29.515 V17.8.0 Reason for Change: When performing positioning request, the NF consumer may provide the integrity requirements for the positioning request and network/UE will take the integrity requirement into account when handling the positioning request. However, when reporting the UE location to the NF consumer, the integrity result is not provided, e.g. whether the integrity requirement is fulfilled or not, the actual integrity value for the positioning measurement. Without such information, the NF consumer cannot aware the quality of the positioning measurement and may misuse the UE location with certain business logic. The integrity result will include the following information: - The integrity computing entities who calculated (and determined) the integrity result. - The calculated PL value, the LCS client use this information to determine by itself whether the system is available or not. - The indication whether the integrity requirements met or not. o when the integrity requirements are not met, the achieved TIR. Summary of change: 1/ Specify the new data types for Integrity Result. 2/ Add the integrity Result in Location Data and Event Notify Data. 3/ Update OpenAPI accordingly. 5.2.2.2.2 Provide Location of a single UE The service operation is used during the procedures: - 5GC-MT-LR Procedure for the commercial location service (see 3GPP TS 23.273 [4], clause 6.1.2) - Deferred 5GC-MT-LR Procedure for Periodic, Triggered and UE Available Location Events (see 3GPP TS 23.273 [4], clause 6.3.1) The ProvideLocation service operation is invoked by a NF Service Consumer, e.g. a NEF or GMLC, towards the GMLC to request to provide the location information (geodetic location and, optionally local and/or civic location) for a target UE or to subscribe to periodic or triggered deferred location for a target UE. See Figure 5.2.2.2.2-1 (FIG.17 in the present document) 2a. On success, "200 OK" shall be returned. The response body shall contain the parameters related to the determined position of the UE if any (geodetic position, local position, civic location, positioning methods, integrity result, …). If geographic area(s) are received in the request for area event, the GMLC (or V- GMLC when roaming) shall convert the received geographic area(s) into a corresponding list of cell and/or tracking area identities when invoking AMF location services. 5.2.2.5.2 EventNotify for a single UE The service operation is used during the procedure: - Deferred 5GC-MT-LR Procedure for Periodic, Triggered and UE Available Location Events (see 3GPP TS 23.273 [4], clause 6.3.1 or clause 6.3.2) The EventNotify for a single UE enables the consumer NF (e.g. (H)GMLC, NEF) to get notified about the geodetic and optionally local and/or civic location, the completion or activation of deferred location, mobility to a different AMF/MME of a UE with deferred location for a target UE when some certain events are detected. See Figure 5.2.2.5.2-1. (FIG.18 in the present document) 1. The GMLC shall send an HTTP POST to the locationNotificationUri to send a notification. The input parameters for the notification (Notification Correlation ID, UE (SUPI and if available GPSI), Type of location related event (e.g. deferred location for the UE available event, activation of location for periodic or triggered location, mobility of a target UE to a new AMF or MME for a deferred location, Geodetic Location, Local Location, Civic Location, Position Methods Used, serving LMF identification, integrity result, etc.) should be included in the HTTP POST request body. 6.1.5.1 General This clause specifies the application data model supported by the API. Table 6.1.5.1-1 specifies the data types defined for the Ngmlc_Location service based interface protocol. Table 6.1.5.1-1: Ngmlc_Location specific Data Types 6.1.5.2.3 Type: LocationData Table 6.1.5.2.3-1: Definition of type LocationData ype: EventNotifyData Table 6.1.5.2.6-1: Definition of type EventNotifyData ype: IntegrityProtectionLevel Table 6.1.5.2.xx-1: Definition of type IntegrityProtectionLevel 6.1.5.2.yy Type: IntegrityResult Table 6.1.5.2.yy-1: Definition of type IntegrityResult 6.1.5.3.x Enumeration: IntegrityComputingEntity The enumeration IntegrityDeterminingEntity represents the entity who calculated (and determined) the integrity result. It shall comply with the provisions defined in table 6.1.5.3.x-1. Table 6.1.5.3.x-1: Enumeration IntegrityComputingEntity A.2 Ngmlc_Location API ******************* Text Skipped for Clarity ********************* LocationData: description: Contains the response parameters in ProvideLocation service operation type: object properties: gpsi: $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi' ******************* Text Skipped for Clarity ********************* haGnssMetrics: $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/HighAccuracyGnssMetrics' integrityResult: $ref: '#/components/schemas/IntegrityResult' ******************* Text Skipped for Clarity ********************* EventNotifyData: description: Contains the input parameters for the target UE in EventNotify Notification service operation type: object required: - eventNotifyDataType - ldrReference properties: gpsi: $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi' ******************* Text Skipped for Clarity ********************* haGnssMetrics: $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/HighAccuracyGnssMetrics' integrityResult: $ref: '#/components/schemas/IntegrityResult' ******************* Text Skipped for Clarity ********************* AlertLimit: description: Alert Limit. type: object required: - horizontalProtectionLevel properties: horizontalProtectionLevel: $ref: '#/components/schemas/HorizontalProtectionLevel' verticalProtectionLevel: $ref: '#/components/schemas/VerticalProtectionLevel' # # SIMPLE TYPES # ******************* Text Skipped for Clarity ********************* SuccessType: description: Success Type to indicate full or partial success anyOf: - type: string enum: - SUCCESS_COMPLETELY - SUCCESS_PARTIALLY - type: string IntegrityComputingEntity: description: Integrity Computing Entity anyOf: - type: string enum: - UE - LMF - BOTH - type: string Draft CR to TS 29.518 V17.11.0 Reason for change: When performing positioning request, the NF consumer may provide the integrity requirements for the positioning request and network/UE will take the integrity requirement into account when handling the positioning request. However, when reporting the UE location to the NF consumer, the integrity result is not provided, e.g. whether the integrity requirement is fulfilled or not, the actual integrity value for the positioning measurement. Without such information, the NF consumer cannot aware the quality of the positioning measurement and may misuse the UE location with certain business logic. The integrity result will include the following information: - The integrity computing entities who calculated (and determined) the integrity result. - The calculated PL value, the LCS client use this information to determine by itself whether the system is available or not. - The indication whether the integrity requirements met or not. o when the integrity requirements are not met, the achieved TIR Summary of Change: 1/ Add the integrity Result in Location Data and Event Notify Data. 2/ Update OpenAPI accordingly. Consequence if not approved: The NF consumer cannot be aware of the system availability and may misuse the UE location when the integrity requirements are not met. 6.4.6.1 General This clause specifies the application data model supported by the API. […] Table 6.4.6.1-2 specifies data types re-used by the Namf_Location service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Namf_Location service based interface. Table 6.4.6.1-2: Namf_Location re-used Data Types ProvidePosInfo Table 6.4.6.2.3-1: Definition of type ProvidePosInfo NotifiedPosInfo
Table 6.4.6.2.4-1: Definition of type NotifiedPosInfo A.5 Namf_Location ******************* Text Skipped for Clarity ********************* ProvidePosInfo: description: Data within Provide Positioning Information Response type: object properties: locationEstimate: $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/GeographicArea' ******************* Text Skipped for Clarity ********************* haGnssMetrics: $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/HighAccuracyGnssMetrics' integrityResult: $ref: 'TS29515_Ngmlc_Location.yaml#/components/schemas/IntegrityResult' NotifiedPosInfo: description: Data within EventNotify notification type: object properties: locationEvent: $ref: '#/components/schemas/LocationEvent' supi: $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi' ******************* Text Skipped for Clarity ********************* haGnssMetrics: $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/HighAccuracyGnssMetrics' integrityResult: $ref: 'TS29515_Ngmlc_Location.yaml#/components/schemas/IntegrityResult' required: - locationEvent ******************* Text Skipped for Clarity ********************* Draft CR to TS 29.572 V17.9.0 Reason for change: When performing positioning request, the NF consumer may provide the integrity requirements for the positioning request and network/UE will take the integrity requirement into account when handling the positioning request. However, when reporting the UE location to the NF consumer, the integrity result is not provided, e.g. whether the integrity requirement is fulfilled or not, the actual integrity value for the positioning measurement. Without such information, the NF consumer cannot aware the quality of the positioning measurement and may misuse the UE location with certain business logic. The integrity result will include the following information: - The integrity computing entities who calculated (and determined) the integrity result. - The calculated PL value, the LCS client use this information to determine by itself whether the system is available or not. - The indication whether the integrity requirements met or not. o when the integrity requirements are not met, the achieved TIR Summary of Change: 1/ Add the integrity Result in Location Data and Event Notify Data. 2/ Update OpenAPI accordingly. Consequence if not approved: The NF consumer cannot be aware of the system availability and may misuse the UE location when the integrity requirements are not met. 5.2.2.2.2 Retrieve UE Location This procedure allows a consumer NF to request the location information (geodetic location and, optionally, local and/or civic location) for a target UE or to activate periodic or triggered deferred location for a target UE. See Figure 5.2.2.2.2-1 (FIG.19 in the present document). 2a. On success, "200 OK" shall be returned. The response body shall contain the parameters related to the determined position of the UE if any (geodetic position, local location, civic location, positioning methods, integrity result, …); 5.2.2.3.2 Periodic or Triggered Event Notification This procedure notifies the NF Service Consumer (i.e. GMLC) about event information related to periodic or triggered location of a target UE. […] See Figure 5.2.2.3.2-1 (FIG.20 in the present document). 1. The LMF shall send a POST request to the GMLC callback URI determined as described above. The request body shall include a notification correlation ID (LDR reference), the UE identification (SUPI and if available GPSI), the type of event and may include a geodetic location, local location, civic location, position methods used, and other available parameters related to the position if any (e.g. Velocity, Altitude etc.), H-GMLC callback URI (if the NF consumer is a V-GMLC) , integrity result, and serving LMF identification. 6.1.6.1 General This clause specifies the application data model supported by the API. […] Table 6.1.6.1-2 specifies data types re-used by the Nlmf_Location service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Nlmf_Location service based interface. Table 6.1.6.1-2: Nlmf_Location re-used Data Types 6.1.6.2.3 Type: LocationData Table 6.1.6.2.3-1: Definition of type LocationData 6.1.6.2.34 Type: EventNotifyData Table 6.1.6.2.34-1: Definition of type EventNotifyData A.2 Nlmf_Location API ******************* Text Skipped for Clarity ********************* LocationData: description: Information within Determine Location Response. type: object required: - locationEstimate properties: locationEstimate: $ref: '#/components/schemas/GeographicArea' ******************* Text Skipped for Clarity ********************* haGnssMetrics: $ref: '#/components/schemas/HighAccuracyGnssMetrics' integrityResult: $ref: 'TS29515_Ngmlc_Location.yaml#/components/schemas/IntegrityResult' ******************* Text Skipped for Clarity ********************* EventNotifyData: description: Information within Event Notify Request. type: object required: - reportedEventType - ldrReference properties: reportedEventType: $ref: '#/components/schemas/ReportedEventType' supi: $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi' ******************* Text Skipped for Clarity ********************* haGnssMetrics: $ref: '#/components/schemas/HighAccuracyGnssMetrics' integrityResult: $ref: 'TS29515_Ngmlc_Location.yaml#/components/schemas/IntegrityResult' ******************* Text Skipped for Clarity ********************* Example Embodiments: Example A1. A network node configured to communicate with a wireless device, the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: receive an integrity result from one of a wireless device and a location management function , the one of the wireless device and the location management function being a positioning integrity entity; and send to a location services (LCS) client an indication of which of the wireless device and the location management function is the positioning integrity entity for each of a plurality of positioning sessions. Example A2. The network node of Example A1, wherein the indication of positioning integrity entity includes integrity results determined by the positioning integrity entity. Example A3. The network node of any of Examples A1 and A2, wherein the indication of positioning integrity entity includes integrity results verified by the one of the wireless device and the location management function that is not the positioning integrity entity. Example A4. The network node of any of Examples A1-A3, wherein an indication of positioning integrity from the wireless device includes an indication of a radio access technology (RAT)-dependent positioning integrity. Example A5. The network node of any of Examples A1-A4, wherein the network node, radio interface and/or processing circuitry are further configured to receive a global navigation satellite system (GNSS) integrity. Example A6. The network node of any of Examples A1-A5, wherein the integrity result includes a protection level, PL, and an entity that determined the PL. Example B1. A method implemented in a network node configured to communicate with a wireless device, the method comprising: receiving an integrity result from one of a wireless device and a location management function, the one of the wireless device and the location management function being a positioning integrity entity; and sending to a location services (LCS) client an indication of which of the wireless device and the location management function is the positioning integrity entity for each of a plurality of positioning sessions. Example B2. The method of Example B1, wherein the indication of positioning integrity entity includes integrity results determined by the positioning integrity entity. Example B3. The method of any of Examples B1 and B2, wherein the indication of positioning integrity entity includes integrity results verified by the one of the wireless device and the location management function that is not the positioning integrity entity. Example B4. The method of any of Examples B1-B3, wherein an indication of positioning integrity from the wireless device includes an indication of a radio access technology (RAT)-dependent positioning integrity. Example B5. The method of any of Examples B1-B4, further comprising receiving a global navigation satellite system (GNSS) integrity. Example B6. The method of any of Examples B1-B5, wherein the integrity result includes a protection level, PL, and an entity that determined the PL. Example C1. A core network node configured to communicate with a wireless device, the core network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: receive from a second network node an indication indicating which of at least one of a first wireless device and a location management function is a position integrity entity; and determine via an access and mobility function (AMF) a positioning integrity result based at least in part on the indication of the position integrity entity. Example C2. The core network node of Example C1, wherein the core network node, radio interface and/or processing circuitry are further configured to transmit to a second wireless device an indication of the position integrity result. Example C3. The core network node of Example C1, wherein the core network node, radio interface and/or processing circuitry are configured to transmit to a second wireless device an indication of an identity of the position integrity entity. Example C4. The core network node of any of Examples C1-C3, wherein determining the positioning integrity result further includes determining an age and accuracy of the position integrity result. Example C5. The core network node of any of Examples C1-C5, wherein the integrity result includes a protection level, PL, and an entity that determined the PL. Example D1. A method implemented in a core network node configured to communicate with a wireless device and a second network node, the method comprising: receiving from the second network node an indication indicating which of at least one of a first wireless device and a location management function is a position integrity entity; and determining via an access and mobility function a positioning integrity result based at least in part on the indication of the position integrity entity. Example D2. The method of Example D1, further comprising transmitting to a second wireless device an indication of the position integrity result. Example D3. The method of Example D1, further comprising transmitting to a second wireless device an indication of an identity of the position integrity entity. Example D4. The method of any of Examples D1-D3, wherein determining the positioning integrity result further includes determining an age and accuracy of the position integrity result. Example D5. The method of any of Examples D1-D5, wherein the integrity result includes a protection level, PL, and an entity that determined the PL. Example E1. A wireless device configured to communicate with a network node, the wireless device configured to, and/or comprising a radio interface and/or processing circuitry configured to: transmit radio access technology (RAT)-dependent positioning integrity result to the network node, the positioning integrity result including at least one of a location request, a quality of service request and an identity of a location management function to receive the positioning integrity result. Example E2. The wireless device of Example E1, wherein the positioning integrity result includes a request for one of a position and location assistance data. Example E3. The wireless device of any of Examples E1 and E2, wherein the wireless device, radio interface and/or processing circuitry are further configured to receive from a location management function a scheduled location time for determining the positioning integrity result. Example E4. The wireless device of any of Example E1-E3, wherein the wireless device, radio interface and/or processing circuitry are further configured to perform an integrity computation and include the integrity computation in the positioning integrity result. Example E5. The wireless device of any of Examples E1-E5, wherein the integrity result includes a protection level, PL, and an entity that determined the PL. Example F1. A method implemented in a wireless device, the method comprising: transmitting radio access technology (RAT)-dependent positioning integrity result to the network node, the positioning integrity result including at least one of a location request, a quality of service request and an identity of a location management function to receive the positioning integrity result. Example F2. The method of Example F1, wherein the positioning integrity result includes a request for one of a position and location assistance data. Example F3. The method of any of Examples F1 and F2, further comprising receiving from a location management function a scheduled location time for determining the positioning integrity result. Example F4. The method of any of Example F1-F3, further comprising performing an integrity computation and including the integrity computation in the positioning integrity result. Example F5. The method of any of Examples F1-F5, wherein the integrity result includes a protection level, PL, and an entity that determined the PL. As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that may be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices. Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer program instructions may also be stored in a computer readable memory or storage medium that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows. Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments may be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination. It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

CLAIMS 1. A network node (16) configured to communicate with a wireless device (22), the network node (16) configured to: receive an integrity result from one of the wireless device (22) and a location management function (98) the one of the wireless device (22) and the location management function (98) being a positioning integrity entity; and send to a location services client an indication of which of the wireless device (22) and the location management function (98) is the positioning integrity entity for each of a plurality of positioning sessions.
2. The network node (16) of Claim 1, wherein sending the indication of positioning integrity entity includes sending integrity results determined by the positioning integrity entity.
3. The network node (16) of any of Claims 1 and 2, wherein the indication of positioning integrity entity includes integrity results verified by the one of the wireless device (22) and the location management function (98) that is not the positioning integrity entity.
4. The network node (16) of any of Claims 1-3, wherein an indication of positioning integrity from the wireless device (22) includes an indication of a radio access technology, RAT,-dependent positioning integrity.
5. The network node (16) of any of Claims 1-4, wherein the network node (16) is configured to receive a global navigation satellite system, GNSS, integrity.
6. The network node (16) of any of Claims 1-5, wherein the integrity result includes a protection level, PL, and an entity that determined the PL.
7. A method implemented in a network node (16) configured to communicate with a wireless device, wireless device (22), the method comprising: receiving (S134) an integrity result from one of the wireless device (22) and a location management function (98) the one of the wireless device (22) and the location management function (98) being a positioning integrity entity; and sending (S136) to a location services client an indication of which of the wireless device (22) and the location management function (98) is the positioning integrity entity for each of a plurality of positioning sessions.
8. The method of Claim 7, wherein sending the indication of positioning integrity entity includes sending integrity results determined by the positioning integrity entity.
9. The method of any of Claims 7 and 8, wherein the indication of positioning integrity entity includes integrity results verified by the one of the wireless device (22) and the location management function (98) that is not the positioning integrity entity.
10. The method of any of Claims 7-9, wherein an indication of positioning integrity from the wireless device (22) includes an indication of a radio access technology, RAT,-dependent positioning integrity.
11. The method of any of Claims 7-10, further comprising receiving a global navigation satellite system, GNSS, integrity.
12. The method of any of Claims 7-11, wherein the integrity result includes a protection level, PL, and an entity that determined the PL.
13. A core network node (36) configured to communicate with a wireless device (22), the core network node (36) configured to: receive from a second network node (16) an indication indicating which of at least one of a first wireless device (22) and a location management function (98) is a position integrity entity; and determine via an access and mobility function (96) a positioning integrity result based at least in part on the indication of the position integrity entity.
14. The core network node (36) of Claim 13, wherein the core network node (36) is configured to transmit to a second wireless device (22) an indication of the position integrity result.
15. The core network node (36) of Claim 13, wherein the core network node (36) is configured to transmit to a second wireless device (22) an indication of an identity of the position integrity entity.
16. The core network node (36) of any of Claims 13-15, wherein determining the positioning integrity result further includes determining an age and accuracy of the position integrity result.
17. The core network node (36) of any of Claims 13-16, wherein the integrity result includes a protection level, PL, and an entity that determined the PL.
18. A method implemented in a core network node (36) configured to communicate with a wireless device (22), and a second network node (16), the method comprising: receiving (S138) from the second network node (16) an indication indicating which of at least one of a first wireless device (22) and a location management function (98) is a position integrity entity; and determining (S140) via an access and mobility function (96) a positioning integrity result based at least in part on the indication of the position integrity entity.
19. The method of Claim 18, further comprising transmitting to a second wireless device (22) an indication of the position integrity result.
20. The method of Claim 18, further comprising transmitting to a second wireless device (22) an indication of an identity of the position integrity entity.
21. The method of any of Claims 18-20, wherein determining the positioning integrity result further includes determining an age and accuracy of the position integrity result.
22. The method of any of Claims 18-21, wherein the integrity result includes a protection level, PL, and an entity that determined the PL.
23. A wireless device (22) configured to communicate with a network node (16), the wireless device (22) configured to: transmit radio access technology, RAT,-dependent positioning integrity result to the network node (16), the positioning integrity result including at least one of a location request, a quality of service request and an identity of a location management function (98) to receive the positioning integrity result.
24. The wireless device (22) of Claim 23, wherein the positioning integrity result includes a request for one of a position and location assistance data.
25. The wireless device (22) of any of Claims 23 and 24, wherein the wireless device (22) is configured to receive from the location management function (98) a scheduled location time for determining the positioning integrity result.
26. The wireless device (22) of any of Claims 23-25, wherein the wireless device (22) is configured to perform an integrity computation and include the integrity computation in the positioning integrity result.
27. The wireless device (22) of any of Claims 23-26, wherein the integrity result includes a protection level, PL, and an entity that determined the PL.
28. A method implemented in a wireless device (22) configured to communicate with network node (16), the method comprising: transmitting (S142) radio access technology, RAT,-dependent positioning integrity result to the network node (16), the positioning integrity result including at least one of a location request, a quality of service request and an identity of a location management function (98) to receive the positioning integrity result.
29. The method of Claim 28, wherein the positioning integrity result includes a request for one of a position and location assistance data.
30. The method of any of Claims 28 and 29, further comprising receiving from the location management function (98) a scheduled location time for determining the positioning integrity result.
31. The method of any of Claims 28-30, further comprising performing an integrity computation and including the integrity computation in the positioning integrity result.
32. The method of any of Claims 28-31, wherein the integrity result includes a protection level, PL, and an entity that determined the PL.
EP23808765.4A 2022-11-15 2023-11-15 Methods to indicate positioning integrity entity Pending EP4620205A1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US202263425562P 2022-11-15 2022-11-15
US202363596136P 2023-11-03 2023-11-03
PCT/EP2023/081942 WO2024105119A1 (en) 2022-11-15 2023-11-15 Methods to indicate positioning integrity entity

Publications (1)

Publication Number Publication Date
EP4620205A1 true EP4620205A1 (en) 2025-09-24

Family

ID=88839090

Family Applications (1)

Application Number Title Priority Date Filing Date
EP23808765.4A Pending EP4620205A1 (en) 2022-11-15 2023-11-15 Methods to indicate positioning integrity entity

Country Status (2)

Country Link
EP (1) EP4620205A1 (en)
WO (1) WO2024105119A1 (en)

Also Published As

Publication number Publication date
WO2024105119A1 (en) 2024-05-23

Similar Documents

Publication Publication Date Title
US12069541B2 (en) Terminal device location determining method and device
US20240171340A1 (en) New radio positioning reference signal enhancements
EP2238774B1 (en) Method and apparatus for using service capability information for user plane location
CN115152284B (en) Supporting control plane positioning methods using user plane location solutions
US9226257B2 (en) Positioning for WLANs and other wireless networks
US9585160B2 (en) Prioritizing location request of a certain type in a congestion situation
US20240365275A1 (en) Positioning method and positioning apparatus
US12363672B2 (en) User equipment, network node and methods in a radio communications network
KR20230044278A (en) Reporting of integrity-related information for positioning
CN115349281A (en) Positioning confidence control method and device
CN115997431A (en) Method, device, system and product for position determination
US9883341B2 (en) Wireless device, a radio network node, a network node and methods therein
US20240196165A1 (en) Location determining method and apparatus
US12376182B2 (en) Method and device for controlling terminal connection state for providing ultra-low-latency location information service in wireless communication system
WO2022079665A1 (en) Satellite system real time kinematic positioning in wireless communication network
WO2024105119A1 (en) Methods to indicate positioning integrity entity
US20250088329A1 (en) On-demand prs configuration parameters
US20240298290A1 (en) Network action based on co-hosted cells
US20250365698A1 (en) Communication Method and Apparatus
US20250031178A1 (en) Apparatuses and methods for enhanced positioning supported by positioning reference units
US20260052505A1 (en) Positioning integrity determination methods, apparatus, device, and medium
BR112024012512B1 (en) USER EQUIPMENT, METHOD ON A USER EQUIPMENT, NETWORK ENTITY COMPRISING A LOCATION SERVER AND METHOD ON A LOCATION SERVER
CN121793107A (en) Error handling for location reporting on the user face

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20250613

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)