WO2023136761A1 - Authorizing location management function (lmf) usage of positioning reference unit (pru) - Google Patents

Abstract

Embodiments include methods for a location management function (LMF) of a communication network. Such methods include sending, to an access and mobility management function (AMF) of the communication network, a request to perform a positioning procedure with a target device in the communication network. The request includes an indication that the target device is a positioning reference unit (PRU). Such methods include receiving, from the AMF, a response including an identifier associated with at least one of the target device and the positioning procedure and, based on the response, performing the positioning procedure with the target device as a PRU. Other embodiments include complementary methods for a unified data management (UDM) function and a positioning target device, as well as LMFs, UDMs, and target devices configured to perform such methods.

Description

AUTHORIZING LOCATION MANAGEMENT FUNCTION (LMF) USAGE OF POSITIONING REFERENCE UNIT (PRU)

TECHNICAL FIELD

The present disclosure generally relates to wireless communication networks, and more specifically to user equipment (UE) location determination based on sidelink (SL) communication with positioning reference units (PRUs) associated with a radio access network (RAN).

BACKGROUND

Currently the fifth generation (“5G”) of cellular systems, also referred to as New Radio (NR), is being standardized within the Third-Generation Partnership Project (3GPP). NR is developed for maximum flexibility to support multiple and substantially different use cases. These include enhanced mobile broadband (eMBB), machine type communications (MTC), ultra-reliable low latency communications (URLLC), side-link device-to-device (D2D), and several other use cases.

Figure 1 illustrates an exemplary high-level view of the 5G network architecture, consisting of a Next Generation RAN (NG-RAN) 199 and a 5G Core (5GC) 198. NG-RAN 199 can include a set of gNodeB’s (gNBs) connected to the 5GC via one or more NG interfaces, such as gNBs 100, 150 connected via interfaces 102, 152, respectively. In addition, the gNBs can be connected to each other via one or more Xn interfaces, such as Xn interface 140 between gNBs 100 and 150. With respect the NR interface to UEs, each of the gNBs can support frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof.

NG-RAN 199 is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, /.< ., the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL. For each NG-RAN interface (NG, Xn, Fl) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport and signaling transport.

The NG RAN logical nodes shown in Figure 1 include a central (or centralized) unit (CU or gNB-CU) and one or more distributed (or decentralized) units (DU or gNB-DU). For example, gNB 100 includes gNB-CU 110 and gNB-DUs 120 and 130. CUs (e.g., gNB-CU 110) are logical nodes that host higher-layer protocols and perform various gNB functions such controlling the operation of DUs. Each DU is a logical node that hosts lower-layer protocols and can include, depending on the functional split, various subsets of the gNB functions. As such, each of the CUs and DUs can include various circuitry needed to perform their respective functions, including processing circuitry, transceiver circuitry (e.g., for communication), and power supply circuitry. A gNB-CU connects to gNB-DUs over respective Fl logical interfaces, such as interfaces 122 and 132 shown in Figure 1. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB. In other words, the Fl interface is not visible beyond gNB-CU.

Sidelink (SL) is a type of device-to-device (D2D) communication whereby UEs can communicate with each other directly rather than indirectly via a 3GPP RAN. The first 3GPP standardization of SL was in LTE Rel-12 targeting public safety use cases and proximity-based services (ProSe). Since then, a number of enhancements have been introduced to broaden the use cases that could benefit from D2D technology. For example, the D2D extensions in LTE Rel-14 and Rel-15 include supporting vehicle-to-everything (V2X) communication.

3GPP Rel-16 specifies the NR SL interface. NR Rel-16 SL targets advanced V2X services, which can be categorized into four use case groups: vehicles platooning, extended sensors, advanced driving, and remote driving. The advanced V2X services require a new SL in order to meet the stringent requirements in terms of latency and reliability. The NR SL is designed to provide higher system capacity and better coverage, and to allow for extension to support the future development of even more advanced V2X services and other related services.

Broadcast, groupcast, and unicast transmissions are desirable for the services targeted by NR SL. In groupcast (or multicast), the intended receiver of a message consists of only a subset of the possible recipients in proximity to the transmitter, whereas a unicast message is intended for only one recipient in proximity to the transmitter. For example, in the platooning service there are certain messages that are only of interest of the members of the platoon, for which groupcast can be used. Unicast is a natural fit for use cases involving only a pair of vehicles.

Furthermore, NR SL is designed such that it is operable both with and without network coverage and with varying degrees of interaction between the UEs (user equipment) and the RAN, including support for standalone, network-less operation. For example, national security and public safety (NSPS) services often need to operate without (or with partial) RAN coverage, such as during indoor firefighting, forest firefighting, earthquake rescue, sea rescue, etc. Network coverage extension is a crucial enabler in these scenarios. 3GPP Rel-17 includes a study item for coverage extension for SL-based communication, including UE-to-network (U2N) relay for cellular coverage extension and UE-to-UE (U2U) relay for SL coverage extension. Additionally, improving performance of power-limited UEs (e.g., pedestrian UEs, first responder UEs, etc.) and improving performance using resource coordination are also important goals for the Rel-17 work.

3 GPP standards provide various ways for positioning (e.g., determining the position of, locating, and/or determining the location of) UEs operating in 3GPP networks. In general, a positioning node configures the target device (e.g., UE) and/or a RAN node to perform one or more positioning measurements according to one or more positioning methods. For example, the positioning measurements can include timing (and/or timing difference) measurements on UE, network, and/or satellite transmissions. The positioning measurements are used by the target device, the RAN node, and/or the positioning node to determine the location of the target device.

NR Rel-16 positioning was developed based on network-transmitted positioning reference signals (PRS), which can provide added value in terms of enhanced location capabilities. For example, PRS transmission in low and high frequency bands (e.g., below and above 6 GHz) and use of massive antenna arrays provide additional degrees of freedom to substantially improve positioning accuracy.

Positioning servers (e.g., location management function, LMF) in 5G networks can initiate procedures to determine the position of a UE, which in various forms are referred to as mobile- terminated location requests (MT-LR) or network-initiated location requests (NI-LR). These procedures include various features and/or constraints related to security, privacy, charging, and other network policies. Many of these are based on the LMF’s awareness of a unique subscription permanent identifier (SUPI) associated with the UE.

One positioning enhancement being discussed for 3GPP Rel-17 and beyond is the use of positioning reference units (PRUs) in the network. A PRU is a network node or device, at a known location, that can transmit uplink (UL) signals and perform positioning measurements. In this manner, PRUs can help identify positioning errors and facilitate compensation for these errors in positions determined for UEs that are proximate in the network. PRUs are also expected to be enablers for SL-based positioning. For example, a UE without line of sight (i.e., non-LOS) to a network node (e.g., gNB) may use a PRU as a positioning reference.

SUMMARY

However, there are various security and/or privacy risks associated with using PRUs to support MO-LR and/or NI-LR. Unlike for UEs, there are currently no security -related procedures defined for obtaining a PRU location for MO-LR and/or NI-LR. As such, a PRU is unable to discern whether a location request is from an authorized or malicious source, and an LMF is unable to discern whether a PRU is an authorized or malicious PRU. This can create various problems, issues, and/or difficulties

Embodiments of the present disclosure provide specific improvements to using PRUs for positioning in wireless networks, such as by providing, enabling, and/or facilitating solutions to overcome exemplary problems summarized above and described in more detail below.

Embodiments include methods e.g., procedures) for an LMF of a communication network. These exemplary methods can include sending, to an access and mobility management function (AMF) of the communication network, a request to perform a positioning procedure with a target device in the communication network, wherein the request includes an indication that the target device is a positioning reference unit (PRU). These exemplary methods can also include receiving, from the AMF, a response including an identifier associated with at least one of the target device and the positioning procedure. These exemplary methods can also include, based on the response, performing the positioning procedure with the target device as a PRU.

In some embodiments, the indication that the target device is a PRU is one of the following associated with the target device: a subscription permanent identifier (SUPI), or a generic public subscription identifier (GPSI). In some of these embodiments, the response indicates that the LMF is authorized to perform the positioning procedure with the target device as a PRU. In some of these embodiments, the identifier is a correlation identifier (ID) that enables the LMF to communicate with the target device.

In some variants of these embodiments, the response also includes a further indication of one or more of the following: the target device’s location is known by the AMF, and the target device’s location should not be reported to the AMF. In such case, performing the positioning procedure based on the response comprises selectively obtaining the target device’s location during the positioning procedure, based on the further indication.

Other embodiments include methods (e.g., procedures) for a unified data management (UDM) function of a communication network. These exemplary method can include receiving, from an AMF of the communication network, a request for an LMF of the communication network to perform a positioning procedure with a target device in the communication network. The request includes a first indication that the target device is a PRU. These exemplary methods can also include sending, to the AMF, a second indication of whether the target device supports or allows positioning as a PRU.

In some embodiments, the UDM is configured with a list of PRUs that are authorized to be located by the LMF and these exemplary methods also include determining the second indication based on whether the target device is among the list of PRUs authorized to be located. In some of these embodiments, the first indication that the target device is a PRU is one of the following associated with the target device: a subscription permanent identifier (SUPI), or a generic public subscription identifier (GPSI). Also, the list of PRUs comprises a list of SUPIs associated with PRUs that are authorized to be located.

In some embodiments, when the second indication indicates that the target device supports or allows positioning as a PRU, the second indication also indicates whether the target device is mobile or stationary.

Other embodiments include methods (e.g., procedures) for a positioning target device configured to operate in a communication network. These exemplary methods can include receiving, from an LMF of the communication network, a request to perform a positioning procedure as a PRU. These exemplary methods can also include performing one of the following operations based on determining that the positioning target device will not perform the requested positioning procedure as a PRU: refraining from responding to the request, or sending an indication that the positioning target device will not perform the requested positioning procedure as a PRU .

In some embodiments, the indication is sent to a node or function of the communication network other than the LMF. In some of these embodiments, the node or function is a radio access network (RAN) node and the indication is sent in a radio resource control (RRC) message. In other of these embodiments, the node or function is an AMF and the indication is sent in a non- access stratum (NAS) message.

In some embodiments, the indication that the positioning target device will not perform the requested positioning procedure includes a failure cause indication, which indicates a reason why the positioning target device determined it will not perform the requested positioning procedure. In some of these embodiments, the indicated failure cause is one of the following: PRU functionality not supported, potential security issue, or potential privacy issue.

In some embodiments, the exemplary methods also include, based on determining that the positioning target device will perform the requested positioning procedure as a PRU, sending to the LMF an acknowledgement that the positioning target device will perform the requested positioning procedure as a PRU.

Other embodiments include LMFs, UDMs, and positioning target devices (e.g., PRUs, wireless devices, etc.) configured to perform operations corresponding to any of the exemplary methods described herein. Other embodiments include non-transitory, computer-readable media storing program instructions that, when executed by processing circuitry, configure such LMFs, UDMs, and positioning target devices to perform operations corresponding to any of the exemplary methods described herein.

These and other embodiments described herein provide techniques to ensure that the PRU usage is fully authorized, such that a network can authenticate that a node claiming to be a PRU is an actual PRU before using the node/PRU for positioning-related procedures. Also, embodiments can ensure that LMF -initiated location requests are only for authorized PRUs and not for any non-PRU device (e.g., UE) or unauthorized PRU. Additionally, embodiments improve positioning privacy by preventing malicious LMFs from obtaining location of a non- PRU device using procedures intended for obtaining location of a PRU. In this manner, embodiments improve security and privacy of positioning -related procedures involving PRUs. These and other objects, features, and advantages of embodiments of the present disclosure will become apparent upon reading the following Detailed Description in view of the Drawings briefly described below.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 illustrates a high-level views of an exemplary 5G/NR network architecture.

Figure 2 shows an exemplary configuration of NR user plane (UP) and control plane (CP) protocol stacks.

Figure 3 shows an exemplary arrangement of interfaces between two V2X UEs and a RAN.

Figure 4 shows three exemplary network coverage scenarios for two UEs and a gNB serving a cell.

Figures 5-6 show exemplary SL UP and CP protocol stacks, respectively, including layer- 2 (L2) UE-to-Network Relay (U2N).

Figure 7 shows an exemplary protocol stack for layer-3 (L3) ProSe 5G U2N Relay.

Figure 8 illustrates a high-level architecture for UE positioning in NR networks.

Figure 9 (which includes Figures 9A-B) shows a signal flow diagram of a 5GC-MT-LR procedure for commercial location services (LCS), according to various embodiments of the present disclosure.

Figure 10 shows a signal flow diagram of a gateway mobile location center (GMLC)- based authentication, according to various embodiments of the present disclosure.

Figures 11-12 show signal flow diagrams of different unified data management (UDM) function-based authentications, according to various embodiments of the present disclosure.

Figure 13 shows a signal flow diagram of a positioning target device-based authentication, according to various embodiments of the present disclosure.

Figure 14 shows an exemplary ASN.1 data structure for ^LocationMeasurementlndication RRC message, according to various embodiments of the present disclosure.

Figure 15 shows a flow diagram of an exemplary method (e.g., procedure) for an LMF, according to various embodiments of the present disclosure.

Figure 16 shows a flow diagram of an exemplary method (e.g., procedure) for a GMLC, according to various embodiments of the present disclosure.

Figure 17 shows a flow diagram of an exemplary method (e.g., procedure) for a UDM function, according to various embodiments of the present disclosure.

Figure 18 shows a flow diagram of an exemplary method (e.g., procedure) for a positioning target device (e.g., PRU, UE, etc.), according to various embodiments of the present disclosure. Figure 19 shows a communication system according to various embodiments of the present disclosure.

Figure 20 shows a UE according to various embodiments of the present disclosure.

Figure 21 shows a network node according to various embodiments of the present disclosure.

Figure 22 shows host computing system according to various embodiments of the present disclosure.

Figure 23 is a block diagram of a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.

Figure 24 illustrates communication between a host computing system, a network node, and a UE via multiple connections, at least one of which is wireless, according to various embodiments of the present disclosure.

DETAILED DESCRIPTION

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

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

Furthermore, the following terms are used throughout the description given below:

• Radio Access Node: As used herein, a “radio access node” (or equivalently “radio network node,” “radio access network node,” or “RAN node”) can be any node in a radio access network (RAN) that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., gNB in a 3GPP 5G/NR network or an enhanced or eNB in a 3GPP LTE network), base station distributed components (e.g., CU and DU), a high-power or macro base station, a low-power base station (e.g., micro, pico, femto, or home base station, or the like), an integrated access backhaul (IAB) node, a transmission point (TP), a transmission reception point (TRP), a remote radio unit (RRU or RRH), and a relay node.

• Core Network Node: As used herein, a “core network node” is any type of node in a core network. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a serving gateway (SGW), a PDN Gateway (P-GW), a Policy and Charging Rules Function (PCRF), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a Charging Function (CHF), a Policy Control Function (PCF), an Authentication Server Function (AUSF), a location management function (LMF), or the like.

• Wireless Device: As used herein, a “wireless device” (or “WD” for short) is any type of device that is capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Communicating wirelessly can involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. Unless otherwise noted, the term “wireless device” is used interchangeably herein with the term “user equipment” (or “UE” for short), with both of these terms having a different meaning than the term “network node”.

• Radio Node: As used herein, a “radio node” can be either a “radio access node” (or equivalent term) or a “wireless device.”

• Network Node: As used herein, a “network node” is any node that is either part of the radio access network (e.g., a radio access node or equivalent term) or of the core network (e.g., a core network node discussed above) of a cellular communications network. Functionally, a network node is equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the cellular communications network, to enable and/or provide wireless access to the wireless device, and/or to perform other functions (e.g., administration) in the cellular communications network.

• Base station: As used herein, a “base station” may comprise a physical or a logical node transmitting or controlling the transmission of radio signals, e.g., eNB, gNB, ng-eNB, en- gNB, centralized unit (CU)/distributed unit (DU), transmitting radio network node, transmission point (TP), transmission reception point (TRP), remote radio head (RRH), remote radio unit (RRU), Distributed Antenna System (DAS), relay, etc. • Node: As used herein, the term “node” (without prefix) can be any type of node that can in or with a wireless network (including RAN and/or core network), including a radio access node (or equivalent term), core network node, or wireless device. However, the term “node” may be limited to a particular type (e.g., radio access node) based on its specific characteristics in any given context.

• Positioning measurements: As used herein, “positioning measurements” may include timing measurements (e.g., time difference of arrival, TDOA, RSTD, time of arrival, TO A, Rx-Tx, RTT, etc.), power-based measurements (e.g., RSRP, RSRQ, SINR, etc.), and/or identifier detection/measurement (e.g., cell ID, beam ID, etc.) that are configured for a positioning method (e.g., OTDOA, E-CID, etc.). UE positioning measurements may be reported to a network node or may be used for positioning purposes by the UE.

The above definitions are not meant to be exclusive. In other words, various ones of the above terms may be explained and/or described elsewhere in the present disclosure using the same or similar terminology. Nevertheless, to the extent that such other explanations and/or descriptions conflict with the above definitions, the above definitions should control.

Note that the description given herein focuses on a 3 GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system. Furthermore, although the term “cell” is used herein, it should be understood that (particularly with respect to 5G NR) beams may be used instead of cells and, as such, concepts described herein apply equally to both cells and beams.

Figure 2 shows an exemplary configuration of NR user plane (UP) and control plane (CP) protocol stacks between a UE (210), a gNB (220), and an access and mobility management function (AMF, 230) in the 5GC. The Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP) layers between the UE and the gNB are common to UP and CP. The PDCP layer provides ciphering/deciphering, integrity protection, sequence numbering, reordering, and duplicate detection for both CP and UP. In addition, PDCP provides header compression and retransmission for UP data.

On the UP side, Internet protocol (IP) packets arrive to the PDCP layer as service data units (SDUs), and PDCP creates protocol data units (PDUs) to deliver to RLC. The Service Data Adaptation Protocol (SDAP) layer handles quality-of-service (QoS) including mapping between QoS flows and Data Radio Bearers (DRBs) and marking QoS flow identifiers (QFI) in UL and DL packets. The RLC layer transfers PDCP PDUs to the MAC through logical channels (LCH). RLC provides error detection/correction, concatenation, segmentation/reassembly, sequence numbering, reordering of data transferred to/from the upper layers. The MAC layer provides mapping between LCHs and PHY transport channels, LCH prioritization, multiplexing into or demultiplexing from transport blocks (TBs), hybrid ARQ (HARQ) error correction, and dynamic scheduling (on gNB side). The PHY layer provides transport channel services to the MAC layer and handles transfer over the NR radio interface, e.g., via modulation, coding, antenna mapping, and beam forming.

On CP side, the non-access stratum (NAS) layer is between UE and AMF and handles UE/gNB authentication, mobility management, and security control. The RRC layer sits below NAS in the UE but terminates in the gNB rather than the AMF. RRC controls communications between UE and gNB at the radio interface as well as the mobility of a UE between cells in the NG-RAN. RRC also broadcasts system information (SI) and performs establishment, configuration, maintenance, and release of DRBs and Signaling Radio Bearers (SRBs) and used by UEs. Additionally, RRC controls addition, modification, and release of carrier aggregation (CA) and dual -connectivity (DC) configurations for UEs. RRC also performs various security functions such as key management.

After a UE is powered ON it will be in the RRC IDLE state until an RRC connection is established with the network, at which time the UE will transition to RRC CONNECTED state (e.g., where data transfer can occur). The UE returns to RRC IDLE, after the connection with the network is released. In RRC IDLE state, the UE’s radio is active on a discontinuous reception (DRX) schedule configured by upper layers. During DRX active times, an RRC IDLE UE receives SI broadcast in the cell where the UE is camping, performs measurements of neighbor cells to support cell reselection, and monitors a paging channel on PDCCH for pages from 5GC via gNB. An NR UE in RRC IDLE state is not known to the gNB serving the cell where the UE is camping. However, NR RRC includes an RRC_INACTIVE state in which a UE is known (e.g., via UE context) by the serving gNB. RRC INACTIVE has some properties similar to a “suspended” condition used in LTE.

DRX functionality is also used by RRC CONNECTED UEs. This allows a UE to turn off at least some of its receiver circuitry when no incoming data is expected, which helps reduce the energy consumption. When configured, the DRX functionality controls the expected UE behavior in terms of reception and processing of transmissions. Similar to RRC IDLE DRX, RRC CONNECTED DRX includes an Active Time (also referred to as Active Time state or ACTIVE state), in which the UE is expected to receive and process incoming transmissions as appropriate. For example, the UE is expected to decode the downlink (DL) control channels, process grants, etc. When the UE is not in Active Time (i.e., the UE is in Inactive mode), there is no expectation by the network for the UE to receive and process transmissions. Typically, UEs that are not in Active Time turn off some of their components and enter a reduced-energy (i.e., sleeping) mode. To ensure that the UE switches regularly to Active Time (i.e., wakes up), a DRX cycle is defined. This DRX cycle is controlled by two parameters: a periodicity, which controls how frequently the UE switches to Active Time; and a duration, which controls for how long the UE remains in active state each time it enters.

A vehicle-to-everything (V2X) UE can support unicast communication via the uplink/downlink radio interface (also referred to as “Uu”) to a 3GPP RAN, such as the LTE Evolved-UTRAN (E-UTRAN) or the NG-RAN. A V2X UE can also support SL unicast over the PC5 interface. Figure 3 shows an exemplary arrangement of interfaces between two V2X UEs and a RAN. In addition to Uu and PC5 interfaces, the V2X UEs can communicate with a ProSe (PROximity-based SErvices) network function (NF) via respective PC3 interfaces. Communication with the ProSe NF requires a UE to establish a connection with the RAN, either directly via the Uu interface or indirectly via PC5 and another UE’s Uu interface. The ProSe function provides the UE various information for network related actions, such as service authorization and provisioning of PLMN-specific information (e.g., security parameters, group IDs, group IP addresses, out-of-coverage radio resources, etc.).

Figure 4 shows three exemplary network coverage scenarios for two UEs ( 10, 420) and a gNB (430) serving a cell. In the full coverage scenario (left), both UEs are in the coverage of the cell, such that they both can communicate with the gNB via respective Uu interfaces and directly with each other via the PC5 interface. In the partial coverage scenario (center), only one of the UEs is in coverage of the cell, but the out-of-coverage UE can still communicate with the gNB indirectly via the PC5 interface with the in-coverage UE. In the out-of-coverage scenario, both UEs can only communicate with each other via the PC5 interface.

In general, the term “SL standalone” refers to direct communication between two SL- capable UEs (e.g., via PC5) in which source and destination are the UEs themselves. In contrast, the term “SL relay” refers to indirect communication between a network node and a remote UE via a first interface (e.g., Uu) between the network node an intermediate (or relay) UE and a second interface (e.g., PC5) between the relay UE and the remote UE. In this case the relay UE is neither the source nor the destination.

In general, an “out-of-coverage UE” is one that cannot establish a direct connection to the network and must communicate via either SL standalone or SL relay. UEs that are in coverage can be configured (e.g., by a gNB) via RRC signaling and/or system information. Out-of-coverage UEs rely on a (pre-)configuration available in their SIMs. These pre-configurations are generally static but can be updated by the network when a UE is in coverage. A “peer UE” refers to a UE that can communicate with the out-of-coverage UE via SL standalone or SL relay (in which case the peer UE is also a relay UE).

As briefly mentioned above, two UE-based relay capabilities were studied for NR SL in Rel-17: UE-to-Network (U2N) relay, where a UE extends the network connectivity to another nearby UE by using direct communication; and UE-to-UE (U2U) relay, where a UE uses two direct communication links to connect two UEs in its proximity that otherwise are not able to communicate. U2N relay functionality is fundamental for network coverage extension for public safety in remote areas, for wearable devices tethering in commercial use cases (e.g., sensors, virtual reality headsets), etc. U2U relay functionality was not part of the LTE ProSe specification, and its inclusion on NR ProSe can be beneficial for public safety communications range extension for both in-network and off-network use cases. However, 3 GPP decided not to include U2U relay in 3GPP Rel-17 work item.

LTE U2N relay functionality uses a Layer 3 (L3) architecture in which the relay of data packets via the PC5 interface is performed at the network layer, and UEs connected to a L3 U2N relay are transparent to the network. NR SL U2N relay uses two different architectures: a L3 architecture similar to LTE, and a newly defined architecture in which PC5 relaying occurs within Layer 2 (L2), over the RLC sublayer.

3GPP TR 23.752 (v2.0.0) section 6.6 describes L3-based U2N relay functionality (also referred to as “ProSe 5G U2N Relay”) that can be used for both public safety and commercial services. A ProSe 5G U2N Relay UE supports connectivity to the 5GS (i.e., NG-RAN and 5GC) for other UEs that have successfully established a PC5 link to the ProSe 5G U2N Relay UE.

3GPP TR 23.752 (v2.0.0) section 6.7 describes L2-based U2N relay functionality, which includes forwarding functionality that can relay any type of traffic over the PC5 interface between two UEs. A L2 U2N Relay UE supports connectivity to the 5GS (i.e., NG-RAN and 5GC) for other UEs that have successfully established a PC5 link to the L2 U2N Relay UE. A UE connected to a L2 U2N relay is expected to be seen by the network as a regular UE., as if it was directly connected to the network. This gives the network control of the connection and services but requires the definition of several new mechanisms not present or needed in the L3 architecture.

Unless expressly stated otherwise, the term “relay UE” (or “U2N relay UE”) will be used herein to refer to both a ProSe 5G U2N Relay UE and a L2 U2N Relay UE. Likewise, the term “remote UE” will be used to refer to a UE that has successfully established a PC5 link to a relay UE. Remote UEs can be located within NG-RAN coverage or outside of NG-RAN coverage.

Before a remote UE can communicate via a relay UE, the two UEs must discover each other. In NR SL, a ProSe direct discovery procedure can be used for a UE to discover or be discovered by other UE(s) in proximity over the PC5 interface (similar to LTE ProSe). The UE can discover other UE(s) with interested application(s) and/or interested group(s) using the ProSe direct discovery procedure. This feature aims to provide a common direct discovery procedure for discovering a 5G ProSe-enabled UE, a 5G ProSe U2N Relay UE, or a 5G ProSe UE-to-UE (U2U) Relay UE.

Discovery can also take place on L2 in the case of L2 U2N relay UEs. A UE connected to a L2 U2N relay is expected to be seen by the network as a regular UE, as if it was directly connected to the network. This gives the network control of the connection and services but requires definition of several new mechanisms not present or needed in the L3 architecture.

Figure 5 illustrates an exemplary user plane (UP) SL protocol stack for a protocol data unit (PDU) Session, including a L2 U2N Relay UE. Below the application (APP) layer, the PDU layer carries data between the remote UE and the user plane function (UPF) in the 5GC, as part of the PDU session. In contrast, the PDCP layer is terminated at the remote UE and the gNB, and the L2 relay function is below PDCP. One consequence is that user data security is ensured between the remote UE and the gNB without exposing user data at the relay UE.

The Adaptation layer between the L2 U2N Relay UE and the gNB is able to differentiate between Uu bearers of a particular remote UE. Different Remote UEs and different Uu bearers of the Remote UE are indicated by additional information (e.g., UE IDs and bearer IDs) included in adaptation layer header that is added to each PDCP PDU. The adaptation layer can be considered as part of PDCP sublayer or a separate new layer between PDCP sublayer and RLC sublayer.

When both the remote UE and the L2 U2N Relay UE are in RRC IDLE or RRC IN ACTIVE states and there is incoming DL traffic for the remote UE, the network will page the remote UE. The L2 U2N relay UE monitors for this paging and informs the remote UE that there is incoming DL traffic. Both the remote UE and the L2 U2N Relay UE the establish/resume their RRC connections to the gNB and the remote UE’s incoming DL traffic is transferred from the gNB to the remote UE transparently via the L2 U2N Relay UE.

Figure 6 illustrates an exemplary control plane (CP) SL protocol stack for non-access stratum (NAS) messages, including a L2 U2N Relay UE. The NAS connection is between the remote UE and the AMF (for NAS-MM) and a session management function (SMF, for NAS- SM) in the 5GC. The NAS messages are transparently transferred between the remote UE and 5G-AN via the relay UE. In particular, the relay UE forwards SRB messages without any modification. Moreover, the relay UE uses the same protocol stack for forwarding both CP messages and UP PDUs, as illustrated in Figures 5-6.

Figure 7 shows an exemplary protocol stack for L3 ProSe 5G U2N Relay, as further described in 3GPP TR 23.752. The ProSe 5G U2N Relay shall relay UL and DL unicast traffic between the Remote UE and the network (e.g., NG-RAN). One-to-one Direct Communication is used between Remote UEs and ProSe 5G U2N Relays for unicast traffic as specified in solutions for Key Issue #2 in 3GPP TR 23.752. The ProSe U2N Relay provides a generic function that can relay any IP, Ethernet, or unstructured traffic at the PDU layer. Furthermore, the remote UE is invisible to the 5GC, i.e., it does not have its own context and PDU session in the 5GC and its traffic is forwarded in relay UE’s PDU session. For IP PDU Session Type and IP traffic over PC5 reference point, the L3 U2N relay UE allocates IPv6 prefix or IPv4 address for the remote UE.

In case the L3 U2N relay UE is in in RRC IDLE or RRC INACTIVE state and there is incoming DL traffic for the remote UE, the network will page the L3 U2N relay UE. The L3 U2N relay UE then establishes/resumes its RRC connection, and then forwards the remote UE’s traffic received from the network.

Various identities or identifiers are used to support NR SL communications. For example, a Source Layer-2 ID identifies a sender of SL data. The Source Layer-2 ID is 24 bits long and is split in the MAC layer into two bit strings. The eight (8) least significant bits (LSB) is used in physical layer (PHY) SL control information (SCI) to identify the sender and is used for filtering of packets at the PHY of the receiver. The 16 most significant bits (MSB) are carried in the MAC- layer header and are used for filtering of packets at the MAC layer of the receiver. Likewise, the Destination Layer-2 ID identifies the intended recipient of the data. Like the Source Layer-2 ID, it includes eight (8) LSBs used in the sender/receiver PHY layers and 16 MSBs used in the sender/receiver MAC layers.

Another identifier is the PC5 Link ID, which uniquely identifies a PC5 unicast link used by a UE during the link’s lifetime. For example, the PC5 Link ID is used to indicate to upper layers the particular PC5 unicast link in which SL radio link failure (RLF) was declared and the corresponding PC5-RRC connection was released.

As briefly mentioned above, 3GPP standards provide various ways for positioning (e.g., determining the position of, locating, and/or determining the location of) UEs operating in 3GPP networks. The following positioning methods are supported in NR:

• Enhanced Cell ID (E-CID). Utilizes information to associate the UE with the geographical area of a serving cell, and then additional information to determine a finer granularity position. The following measurements are supported for E-CID: AoA (base station only), UE Rx-Tx time difference, timing advance (TA) types 1 and 2, reference signal received power (RSRP), and reference signal received quality (RSRQ).

• Assisted GNSS. The UE receives and measures signals transmitted by GNSS satellites (e.g., GPS), supported by assistance information provided to the UE by a positioning node. • OTDOA (Observed Time Difference of Arrival). The UE receives and measures DL RS (e.g., PRS) transmitted by the RAN, supported by assistance information provided to the UE by a positioning node.

• UTDOA (Uplink TDOA). The UE transmits UL RS (e.g., SRS) that are detected and measured by RAN nodes at known positions. These measurements are forwarded to a positioning node for multilateration.

• Multi -RTT : Both UE and RAN nodes compute Rx-Tx time differences, with the results being combined by a positioning node to find the UE position based upon round trip time (RTT) calculation.

• DL angle of departure (DL-AoD): RAN node or positioning node calculates the UE angular position based upon UE DL RSRP measurement results (e.g., of PRS transmitted by RAN nodes).

• UL angle of arrival (UL-AoA): RAN node calculates the UL AoA based upon measurements of a UE’s UL SRS transmissions.

In addition to these methods, a UE can also perform positioning measurements (and optionally calculate position) based on WLAN signals, Bluetooth signals, terrestrial beacon system (TBS) signals, and UE sensors (e.g., barometric pressure, accelerometer, etc.).

Additionally, one or more of the following positioning modes can be utilized in each of the positioning methods listed above:

• 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.

• Standalone: The UE performs measurements and calculates its own position without network assistance.

The detailed assistance data may include information about network node locations, beam directions, etc. The assistance data can be provided to the UE via unicast or via broadcast.

Figure 8 is a block diagram illustrating a high-level architecture for supporting UE positioning in NR networks. NG-RAN 820 can include nodes such as gNB 822 and ng-eNB 821. Each ng-eNB may control several transmission points (TPs), such as remote radio heads. Similarly, each gNB may control several transmission/reception points (TRPs).

In addition, the NG-RAN nodes communicate with an Access and Mobility Management Function (AMF) 830 in the 5GC via respective NG-C interfaces (both of which may or may not be present), while AMF 830 communicates with a location management function (LMF) 840 communicate via an NLs interface 841. LMF supports various functions related to UE positioning, including location determination for a UE, obtaining DL location measurements or a location estimate from the UE, obtaining UL location measurements from the NG RAN, and obtaining non-UE associated assistance data from the NG RAN.

In addition, positioning-related communication between UE 810 and theNG-RAN nodes occurs via the RRC protocol, while positioning-related communication between NG-RAN nodes and LMF occurs via an NRPPa protocol. Optionally, the LMF can also communicate with an E- SMLC 850 and a SUPL 860 in an LTE network via communication interfaces 851 and 861, respectively. Communication interfaces 851 and 861 can implemented according to standardized protocols, proprietary protocols, or a combination thereof.

LMF 840 can also include, or be associated with, various processing circuitry 842, by which the LMF performs various operations described herein. Processing circuitry 842 can include similar types of processing circuitry as described herein in relation to other network nodes (see, e.g., description of Figures 21 and 23). LMF 840 can also include, or be associated with, a non-transitory computer-readable medium 843 storing instructions (also referred to as a computer program program) that can facilitate the operations of processing circuitry 842. Medium 843 can include similar types of computer memory as described herein in relation to other network nodes (see, e.g., description of Figures 21 and 23). Additionally, LMF 840 can include various communication interface circuitry 841 (e.g., Ethernet, optical, and/or radio transceivers) that can be used, e.g., for communication via the NLs interface. For example, communication interface circuitry 841 can be similar to other interface circuitry described herein in relation to other network nodes (see, e.g., description of Figures 21 and 23).

Similarly, E-SMLC 850 can also include, or be associated with, various processing circuitry 852, by which the E-SMLC performs various operations described herein. Processing circuitry 852 can include similar types of processing circuitry as described herein in relation to other network nodes (see, e.g., description of Figures 21 and 23). E-SMLC 850 can also include, or be associated with, a non-transitory computer-readable medium 853 storing instructions (also referred to as a computer program program) that can facilitate the operations of processing circuitry 852. Medium 853 can include similar types of computer memory as described herein in relation to other network nodes (see, e.g., description of Figures 21 and 23). E-SMLC 850 can also have communication interface circuitry that is appropriate for communicating via interface 851, which can be similar to other interface circuitry described herein in relation to other network nodes (see, e.g., description of Figures 21 and 23).

Similarly, SLP 860 can also include, or be associated with, various processing circuitry 862, by which the SLP performs various operations described herein. Processing circuitry 662 can include similar types of processing circuitry as described herein in relation to other network nodes (see, e.g., description of Figures 21 and 23). SLP 860 can also include, or be associated with, a non-transitory computer-readable medium 863 storing instructions (also referred to as a computer program program) that can facilitate the operations of processing circuitry 862. Medium 863 can include similar types of computer memory as described herein in relation to other network nodes (see, e.g., description of Figures 21 and 23). SLP 860 can also have communication interface circuitry that is appropriate for communicating via interface 861, which can be similar to other interface circuitry described herein in relation to other network nodes (see, e.g., description of Figures 21 and 23).

In a typical operation, the AMF can receive a request for a location service associated with a particular target UE from another entity (e.g., a gateway mobile location center, GMLC), or the AMF can initiate a location service on behalf of a particular target UE (e.g., for an emergency call by the UE). The AMF then sends a location services (LS) request to the LMF. The LMF processes the LS request, which may include transferring assistance data to the target UE to assist with UE- based and/or UE-assisted positioning; and/or positioning of the target UE. The LMF then returns the result of the LS (e.g., a position estimate for the UE and/or an indication of any assistance data transferred to the UE) to the AMF or to another entity (e.g., GMLC) that requested the LS.

An LMF may have a signaling connection to an E-SMLC, enabling the LMF to access information from E-UTRAN, e.g., to support E-UTRA OTDOA positioning by obtaining measurements made by a target UE based on DL PRS. An LMF can also have a signaling connection to an SLP, the LTE entity responsible for user-plane positioning.

Various interfaces and protocols are used for, or involved in, NR positioning. The LTE Positioning Protocol (LPP) is used between a target device (e.g., UE in the control -plane, or SET in the user-plane) and a positioning server (e.g., LMF in the control-plane, SLP in the user-plane). LPP can use either CP or UP protocols as underlying transport. NRPP is terminated between a target device and the LMF. RRC protocol is used between UE and gNB (via NR radio interface) and between UE and ng-eNB (via LTE radio interface).

Furthermore, the NR Positioning Protocol A (NRPPa) carries information between the NG-RAN Node and the LMF and is transparent to the AMF. As such, the AMF routes the NRPPa PDUs transparently (e.g., without knowledge of the involved NRPPa transaction) over NG-C interface based on a Routing ID corresponding to the involved LMF. More specifically, the AMF carries the NRPPa PDUs over NG-C interface either in UE associated mode or non-UE associated mode. The NGAP protocol between the AMF and an NG-RAN node (e.g., gNB or ng-eNB) is used as transport for LPP and NRPPa messages over the NG-C interface. NGAP is also used to instigate and terminate NG-RAN-r elated positioning procedures. LPP/NRPP are used to deliver messages such as positioning capability request, OTDOA positioning measurements request, and OTDOA assistance data to the UE from a positioning node (e.g., location server). LPP/NRPP are also used to deliver messages from the UE to the positioning node including, e.g., UE capability, UE measurements for UE-assisted OTDOA positioning, UE request for additional assistance data, UE configuration parameter(s) to be used to create UE- specific OTDOA assistance data, etc. NRPPa is used to deliver the information between ng- eNB/gNB and LMF in both directions. This can include LMF requesting some information from ng-eNB/gNB, and ng-eNB/gNB providing some information to LMF. For example, this can include information about PRS transmitted by ng-eNB/gNB that are to be used for OTDOA positioning measurements by the UE.

As briefly mentioned above, network-based positioning reference units (PRUs) are being discussed in 3GPP as a positioning enhancement for Rel-17 and beyond. APRU is a network node or device, at a known location, that can transmit UL signals and perform positioning measurements (e.g., on DL signals). In this manner, PRUs can help identify positioning errors and facilitate compensation for these errors in positions determined for UEs that are proximate in the network. PRUs are also expected to be enablers for SL-based positioning. For example, a UE without line of sight (i.e., non-LOS) to a network node (e.g., gNB) may use a PRU as a positioning reference.

PRUs may support some of the Rel-16 positioning functionalities of UEs such as providing positioning measurements (e.g., RSTD, RSRP, Rx-Tx time differences) of DL PRS, transmitting the UL SRS signals for positioning, etc. An LMF may request a PRU to provide its known location and, if known, the PRUs antenna orientation or direction.

Currently, UEs use PRUs at their own risk. For example, a UE cannot determine if an available PRU is from a malicious source that is trying to obtain location of users without their consent and/or provide incorrect or misleading positioning information to UEs. This can cause serious problems for critical applications (e.g., NSPS) or emergency calls. The network also faces risk from malicious devices, e.g., that attempt to pose as PRUs while providing incorrect measurements and location information. This can create various problems, issues, and/or difficulties when the network uses information from such malicious PRUs in calibration location errors for legitimate UEs served by the network.

Accordingly, embodiments of the present disclosure address these and other problems, issues, and/or difficulties by providing techniques to ensure that the PRU usage is fully authorized, such that a network can authenticate that a node claiming to be a PRU is an actual PRU before using the node/PRU for positioning-related procedures. Furthermore, these techniques can ensure that LMF -initiated location requests are only for authorized PRUs and not for any non-PRU device (e.g., UE) or unauthorized PRU.

In this manner, embodiments avoid and/or prevent the various problems, issues, and/or difficulties discussed above and in general improve the security of positioning-related procedures involving PRUs. Additionally, embodiments improve positioning privacy by preventing malicious LMFs from obtaining location of a non-PRU device using procedures intended for obtaining location of a PRU.

In some embodiments, PRU device information (e.g., UE ID) is configured via 0AM in the LMF. Whenever the LMF needs measurement and/or location information from a PRU, it initiates a MT-LR procedure towards the PRU, but which is initially directed towards a GMLC or an AMF. Depending upon the sequence there can be multiple ways in which authentication is performed.

Figure 9 (which includes Figures 9A-B) shows a signal flow diagram of a 5GC -MT-LR procedure for commercial LCS, as further described in 3GPP TS 23.373 (vl7.2.0) section 6.1.2. This procedure is between a target UE (910), AMF (920), LMF (930), GMLC (940, shown as VGMLC/HGMLC), and UDM (950), as well as certain other entities shown. This diagram illustrates general network positioning requested by an LCS client or by an application function (AF). In this scenario, it is assumed that the target UE may be identified using a subscription permanent identifier (SUPI) or a generic public subscription identifier (GPSI). This procedure assumes that privacy verification may be required for the location service request and that the LCS client or the AF needs to be authorized to use the location service.

The description in 3GPP TS 23.373 (vl7.2.0) section 6.1.2 of the numbered operations shown in Figure 9 is used as a baseline for the following, which describes various ones of the numbered operations that are modified according to embodiments of the present disclosure.

In operation 1, the LCS Client or AF (via network exposure function, NEF) sends a request to the (H)GMLC for a location and optionally a velocity for a target UE, which may be identified by a GPSI or a SUPI. The request may include the required QoS, supported GAD shapes, LCS client type, LCS service type (as defined in 3GPP TS 22.071 (vl6.0.0)) and other attributes.

(H)GMLC (in operation la) or NEF (in operation lb) authorizes the LCS Client or the AF for usage of the LCS service. For an LMF-initiated location request for a PRU, (H)GMLC verifies and/or authorizes the provided SUPI belongs to a PRU. If the authorization fails, step 2-23 are skipped and (H)GMLC (for operation la) or NEF (for operation lb) responds in operation 24 to the LCS Client or the AF indicating failure of the service authorization. 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. In operation 2 (assuming the authorization is successful), the (H)GMLC invokes a Nudm SDM Get service operation towards the 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 including consent if UE can be positioned internally by LMF as a PRU. The (H)GMLC checks the UE LCS privacy profile. If the target UE is not allowed to be located, operations 3-23 are skipped.

In operation 5, in the case 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 ProvidePositioninglnfo service operation towards the AMF to request the current location of the UE or that reference measurements are performed. The service operation includes the SUPI and the client type, and may include the required LCS QoS, supported GAD shapes, service type, indication of PRU, and other attributes as received or determined in operation 1.

Operations 10-13 are the same as operations 6-9 defined in 3GPP TS 23.273 (vl7.2.0) section 6.1.1 with the following additions or exceptions:

• The following also may be indicated to the LMF: 1) service type; and 2) the request is for a PRU (or reference device) and no location estimate is to be reported to AMF; and

• 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.

In operation 14, the AMF sends the Namf Location ProvidePositioninglnfo Response to (V)GMLC (or HGMLC for roaming when the NL3 reference point is not supported) to return the current location of the UE or an indication that a reference measurement has been performed (e.g., via PRU). The service operation may include the location estimate, its age and accuracy, and information about the positioning method.

Figure 10 shows a signal flow diagram of GMLC-based authentication based on PRU indication to AMF and LMF, according to some embodiments of the present disclosure. The procedure shown in Figure 10 involves an AMF (1020), an LMF (1030, and a GMLC (1040). Although the operations shown in Figure 10 are given numerical labels, this is done to facilitate explanation rather than to require or imply any specific operational order, unless expressly stated otherwise.

In operation 1, the LMF determines a need to trigger positioning for a PRU and sends a PRU location request to the GMLC. In operations 2-3, the GMLC performs an authorization of the location request and initiates a MT-LR request to the AMF with an indication that LCS target is a PRU.

In operation 4, the AMF provides a correlation ID so that LMF can communicate to the PRU. In some cases, the AMF may also inform LMF that there is no need to provide location since the PRU’s location is known. However, the AMF may query a UDM based upon UE subscription information whether PRU is mobile or stationary. If PRU is mobile, then the AMF may obtain the PRU location. In operation 5, the LMF performs the LPP Positioning procedure towards the PRU using the correlation ID received in operation 4.

In some embodiments, the GMLC can be configured with LCS client data that includes an authorized PRU list. This can be a list of SUPIs for which a location and measurement request can be originated by the LMF. The GMLC can use this list, for example, for the authorization operations in Figures 9-10, discussed above. The table below shows exemplary GMLC permanent data for an LCS client including an authorized PRU list.

Figure 11 shows a signal flow diagram of UDM based authentication, according to other embodiments of the present disclosure. The procedure shown in Figure 11 involves an AMF (1120), an LMF (1130, and a UDM (1150). Although the operations shown in Figure 11 are given numerical labels, this is done to facilitate explanation rather than to require or imply any sequential order, unless expressly stated to the contrary.

In operation 1, the LMF determines a need to trigger positioning for a PRU and sends a PRU location request to the AMF, which forwards the request to the UDM in operation 2. In operation 3, the UDM performs an authorization of the location request and verifies from PRU subscription whether it is mobile, stationary etc. In operation 4, the UDM responds to the AMF. In operation 5, the AMF provides a correlation ID so that LMF can communicate to the PRU. In operation 6, the LMF performs an LPP Positioning procedure towards the PRU.

Figure 12 shows a signal flow diagram of an alternate UDM based authentication, according to other embodiments of the present disclosure. The procedure shown in Figure 12 involves an AMF (1120), an LMF (1130, and a UDM (1150). Although the operations shown in Figure 12 are given numerical labels, this is done to facilitate explanation rather than to require or imply any sequential order, unless expressly stated to the contrary. In operation 1, the LMF determines a need to trigger positioning for a PRU and sends a PRU location request to the GMLC, which forwards the request to the AMF in operation 2. In operation 3, the AMF forwards the request to the UDM. In operation 4, the UDM performs an authorization of the location request and verifies from PRU subscription whether it is mobile, stationary, etc. in a similar manner as in Figure 11 operation 3. In operation 5, the UDM responds to the AMF in a similar manner as in Figure 11 operation 4.

In operation 6, the AMF provides a correlation ID so that LMF can communicate to the PRU. In some cases, the AMF may also inform LMF that there is no need to provide location since the PRU’s location is known. However, the AMF may query a UDM based upon UE subscription information whether PRU is mobile or stationary. If PRU is mobile, then the AMF may obtain the PRU location. In operation 7, the LMF performs an LPP Positioning procedure towards the PRU.

Referring to Figure 9, and as explained in the description in 3GPP TS 23.373 (vl7.2.0) section 6.1.2, in operation 8 the target UE notifies the user about the location request received from AMF in operation 7 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 user does not respond after a predetermined time period, the AMF shall infer a "no response" condition. The AMF returns an error response in operation 14 and if roaming VGMLC in operation 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 operations 10-13 are skipped.

The notification result in operation 8 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.

In operation 9, the AMF invokes a Nudm ParameterProvision Update (LCS privacy) service operation to store in the UDM the Location Privacy Indication information received from the UE in operation 8. The UDM may then store the updated UE privacy setting information into the UDR as the “LCS privacy” Data Subset of the Subscription Data.

To perform the authorization operations described above in relation to Figures 11-12, The UDM may also store a list of authorized PRUs, e.g., a list of SUPIs for authorized PRUs (i.e., authorized to be located by LMF as LCS client). Note this list may correspond to the “Authorized PRU List” discussed above in relation to other embodiments. The table below shows an exemplary data structure of UDM information according to these embodiments.

In other embodiments, the network (e.g., LMF) indicates to the target device for positioning that the positioning procedure is triggered and/or intended for a PRU. The target then responds with an acknowledgement (ACK) indicating that the target device accepts positioning as a PRU, or a rejection (NACK) indicating that the target device rejects the request on basis of privacy and/or security concerns.

Figure 13 shows an exemplary signal flow diagram that illustrates these embodiments. The procedure shown in Figure 13 involves a target device (1310) and a network node (1320). In operation 1, the network node (e.g., LMF) explicitly indicates in a paging procedure or an LPP procedure that measurements are being sought from a PRU. If the target device is a PRU and allows the positioning request, it responds to the LMF with an acknowledgement in operation 2a as mentioned above.

On the other hand, if the target device is not a PRU (e.g., a normal UE) and/or does not allow the positioning request, it sends a rejection in operation 2b as mentioned above. This rejection can be a NAS message or an RRC message that includes a failure cause indicating why the request was rejected (e.g., due to potential security or privacy concerns). Figure 14 discussed below shows an example failure cause. In the procedure shown in Figure 13, this message is not sent to the LMF but rather to another node such as AMF (for NAS) or gNB (for RRC). In other variants, the target device can refrain from responding to (i.e., ignore) the rejected request.

Figure 14 shows an exemplary ASN.1 data structure for ^LocationMeasurementlndication RRC message that is modified in accordance with these embodiments. This message is sent from UE to network such as shown in Figure 13. This message includes a LocationMeasurementIndication-IEs-rl8 information element (IE) that contains various fields including a locationFailureCause-rl8 field. As shown in Figure 14, this field includes one of an emuerated set of values, with each value indicating a different failure cause. For example, the value “potential Securityissue” indicates that the location measurement request failed because of a potential security issue. Various features of the embodiments described above correspond to various operations illustrated in Figures 15-18, which show exemplary methods (e.g., procedures) for an LMF, a GMLC, a UDM function, and a positioning target device, respectively. In other words, various features of the operations described below correspond to various embodiments described above. Furthermore, the exemplary methods shown in Figures 15-18 can be used cooperatively to provide various benefits, advantages, and/or solutions to problems described herein. Although Figures 15- 18 show specific blocks in particular orders, the operations of the exemplary methods can be performed in different orders than shown and can be combined and/or divided into blocks having different functionality than shown. Optional blocks or operations are indicated by dashed lines.

In particular, Figure 15 shows an exemplary method (e.g., procedure) for an LMF configured to operate in a communication network (e.g., 5GC), according to various embodiments of the present disclosure. The exemplary method can be performed by an LMF such as described elsewhere herein.

The exemplary method can include the operations of block 1510, where the LMF can send, to a first node or function of the communication network, a request to perform a positioning procedure with a target device in the communication network. The request includes an indication that the target device is a PRU. The exemplary method can also include the operations of block 1520, where the LMF can receive, from a second node or function of the communication network, a response including one of the following associated with at least one of the target device and the positioning procedure: an indication or an identifier. The exemplary method can also include the operations of block 1530, where the LMF can, based on the identifier, perform the positioning procedure with the target device as a PRU.

In some embodiments, the indication that the target device is a PRU is one of the following associated with the target device: a subscription permanent identifier, (SUPI) or a generic public subscription identifier (GPSI). In some of these embodiments, the response indicates that the LMF is authorized to perform the positioning procedure with the target device as a PRU. In some of these embodiments, the identifier included in the response is a correlation identifier (ID) that enables the LMF to communicate with the target device.

In some embodiments, the first node or function is a GMLC and the second node or function is an AMF. Figures 10 and 12 show examples of these variants.

In other embodiments, the first node or function is an AMF and the second node or function is the same AMF. Figure 11 shows an example of these embodiments. In these embodiments, the LMF sends the request to the AMF in block 1510 and receives the response from the (same) AMF in block 1520. In such embodiments, the response can include the identifier (e.g., correlation ID). In some embodiments, the response also includes a further indication of one or more of the following: the target device’s location is known by the second node or function (e.g., AMF), and the target device’s location should not be reported to the LMF. In such embodiments, performing the positioning procedure in block 1530 includes the operations of sub-block 1531, where the LMF can selectively obtain the target device’s location during the positioning procedure, based on the further indication.

In other embodiments, the first node or function is the target device (i.e., PRU) the second node or function is the target device, and the response includes an acknowledgement that the LMF is authorized to perform the positioning procedure with the target device as a PRU. Figure 13 shows an example of these embodiments.

In addition, Figure 16 shows an exemplary method (e.g., procedure) for a GMLC configured to operate in a communication network (e.g., 5GC), according to various embodiments of the present disclosure. The exemplary method can be performed by a GMLC such as described elsewhere herein.

The exemplary method can include the operations of block 1610, where the GMLC can receive, from an LMF of the communication network, a request to perform a positioning procedure with a target device in the communication network. The request includes a first indication that the target device is a PRU. The exemplary method can also include the operations of block 1620, where the GMLC can determine whether the LMF is authorized to perform the positioning procedure with the target device as a PRU. The exemplary method can also include the operations of block 1630, where the GMLC can, based on determining that the LMF is authorized, send a location request to an AMF of the communication network. The location request includes a second indication that the target device is a PRU.

In some embodiments, the first indication that the target device is a PRU is one of the following associated with the target device: a SUPI, or a GPSI.

In some of these embodiments, the GMLC is configured with a list comprising a plurality of SUPIs associated with a respective plurality of PRUs authorized to perform positioning procedures with the LMF. Also, determining whether the LMF is authorized in block 1620 includes the operations of sub-block 1621, where the GMLC can compare the SUPI associated with the target device to the SUPIs comprising the list. Figure 10 shows an example of these embodiments.

In other of these embodiments, determining whether the LMF is authorized in block 1620 includes the operations of sub-blocks 1622-1624. In sub-block 1622, the GMLC can send the SUPI or the GPSI associated with the target device to a UDM function of the communication network. In sub-block 1623, the GMLC can receive, from the UDM function, a third indication of whether the target device supports or allows positioning as a PRU. In sub-block 1624, the GMLC can determine whether the LMF is authorized based on the third indication. Figure 9 shows an example of these embodiments.

In some embodiments, the location request to the AMF further indicates one or more of the following: that reference measurements should be performed by the target device as a PRU; and that a location of the target device is not required.

In addition, Figure 17 shows an exemplary method (e.g., procedure) for a UDM function configured to operate in a communication network (e.g., 5GC), according to various embodiments of the present disclosure. The exemplary method can be performed by UDM function such as described elsewhere herein.

The exemplary method can include the operations of block 1710, where the UDM function can receive, from an AMF of the communication network, a request for an LMF of the communication network to perform a positioning procedure with a target device in the communication network. The request includes a first indication that the target device is a PRU. The exemplary method can also include the operations of block 1730, where the UDM function can send, to the AMF, a second indication of whether the target device supports or allows positioning as a PRU.

In some embodiments, the UDM is configured with a list of PRUs that are authorized to be located by the LMF and the exemplary method also includes the operations of block 1720, where the UDM function can determine the second indication based on whether the target device is among the list of PRUs authorized to be located. In some of these embodiments, the first indication that the target device is a PRU is one of the following associated with the target device: a SUPI, or a GPSI. In such embodiments, the list of PRUs comprises a list of SUPIs associated with PRUs that are authorized to be located.

In some embodiments, when the second indication indicates that the target device supports or allows positioning as a PRU, the second indication also indicates whether the target device is mobile or stationary.

In addition, Figure 18 shows an exemplary method (e.g., procedure) for a positioning target device configured to operate in a communication network (e.g., 5GC), according to various embodiments of the present disclosure. The exemplary method can be performed by a positioning target device (e.g., PRU, UE, etc.) such as described elsewhere herein.

The exemplary method can include the operations of block 1810, where the positioning target device can receive, from an LMF of the communication network, a request to perform a positioning procedure as a PRU. The exemplary method can also include the operations of block 1820, where the positioning target device can perform one of the following operations (labelled with corresponding sub-block numbers) based on determining that the positioning target device will not perform the requested positioning procedure as a PRU:

• (1821) refraining from responding to the request; or

• (1822) sending an indication that the positioning target device will not perform the requested positioning procedure as a PRU.

In some embodiments, the indication is sent to a node or function of the communication network other than the LMF. Figure 13 shows an example of these embodiments. In some of these embodiments, the node or function is a RAN node (e.g., serving gNB) and the indication is sent in an RRC message. In other of these embodiments, the node or function is an AMF and the indication is sent in a non-access stratum (NAS) message.

In some embodiments, the indication that the positioning target device will not perform the positioning procedure requested by the LMF includes a failure cause indication, which indicates a reason why the positioning target device determined it will not perform the requested positioning procedure. In some variants, the indicated failure cause is one of the following: PRU functionality not supported, potential security issue, or potential privacy issue. Figure 14 shows an example of these embodiments.

In some embodiments, the exemplary method can also include the operations of block 1830, where based on determining that it will perform the requested positioning procedure as a PRU, the positioning target device sends to the LMF an acknowledgement that the positioning target device will perform the requested positioning procedure as a PRU.

Although various embodiments are described above in terms of methods, techniques, and/or procedures, the person of ordinary skill will readily comprehend that such methods, techniques, and/or procedures can be embodied by various combinations of hardware and software in various systems, communication devices, computing devices, control devices, apparatuses, non-transitory computer-readable media, computer program products, etc.

Figure 19 shows an example of a communication system 1900 in accordance with some embodiments. In this example, the communication system 1900 includes a telecommunication network 1902 that includes an access network 1904, such as a radio access network (RAN), and a core network 1906, which includes one or more core network nodes 1908. Access network 1904 includes one or more access network nodes, such as network nodes 1910a-b (one or more of which may be generally referred to as network node 1910), or any other similar 3 GPP access node or non-3GPP access point. Network nodes 1910 facilitate direct or indirect connection of UEs, such as by connecting UEs 1912a-d (one or more of which may be generally referred to as UEs 1912) to core network 1906 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, communication system 1900 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. Communication system 1900 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

UEs 1912 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with network nodes 1910 and other communication devices. Similarly, network nodes 1910 are arranged, capable, configured, and/or operable to communicate directly or indirectly with UEs 1912 and/or with other network nodes or equipment in telecommunication network 1902 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in telecommunication network 1902.

In the depicted example, core network 1906 connects network nodes 1910 to one or more hosts, such as host 1916. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1906 includes one more core network nodes (e.g., core network node 1908) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1908. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

Host 1916 may be under the ownership or control of a service provider other than an operator or provider of access network 1904 and/or telecommunication network 1902, and may be operated by the service provider or on behalf of the service provider. The host 1916 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

As a whole, communication system 1900 of Figure 19 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

In some examples, telecommunication network 1902 is a cellular network that implements 3GPP standardized features. Accordingly, telecommunications network 1902 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1902. For example, telecommunications network 1902 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs.

In some examples, the UEs 1912 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1904 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1904. Additionally, a UE may be configured for operating in single- or multi -RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e., being configured for multi -radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

In the example, hub 1914 communicates with the access network 1904 to facilitate indirect communication between one or more UEs (e.g., UE 1912c and/or 1912d) and network nodes (e.g., network node 1910b). In some examples, hub 1914 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, hub 1914 may be a broadband router enabling access to the core network 1906 for the UEs. As another example, hub 1914 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1910, or by executable code, script, process, or other instructions in hub 1914. As another example, hub 1914 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, hub 1914 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, hub 1914 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which hub 1914 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, hub 1914 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

Hub 1914 may have a constant/persistent or intermittent connection to the network node 1910b. Hub 1914 may also allow for a different communication scheme and/or schedule between hub 1914 and UEs (e.g., UE 1912c and/or 1912d), and between hub 1914 and the core network 1906. In other examples, hub 1914 is connected to the core network 1906 and/or one or more UEs via a wired connection. Moreover, hub 1914 may be configured to connect to an M2M service provider over the access network 1904 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1910 while still connected via hub 1914 via a wired or wireless connection. In some embodiments, hub 1914 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1910b. In other embodiments, hub 1914 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1910b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

Figure 20 shows a UE 2000 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3 GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

UE 2000 includes processing circuitry 2002 that is operatively coupled via a bus 2004 to an input/output interface 2006, a power source 2008, a memory 2010, a communication interface 2012, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 20. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

The processing circuitry 2002 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 2010. The processing circuitry 2002 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general -purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 2002 may include multiple central processing units (CPUs).

In the example, the input/output interface 2006 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into UE 2000. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. In some embodiments, the power source 2008 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 2008 may further include power circuitry for delivering power from the power source 2008 itself, and/or an external power source, to the various parts of UE 2000 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 2008. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 2008 to make the power suitable for the respective components of UE 2000 to which power is supplied.

The memory 2010 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 2010 includes one or more application programs 2014, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 2016. The memory 2010 may store, for use by UE 2000, any of a variety of various operating systems or combinations of operating systems.

The memory 2010 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 2010 may allow UE 2000 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 2010, which may be or comprise a device-readable storage medium.

The processing circuitry 2002 may be configured to communicate with an access network or other network using the communication interface 2012. The communication interface 2012 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 2022. The communication interface 2012 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 2018 and/or a receiver 2020 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 2018 and receiver 2020 may be coupled to one or more antennas (e.g., antenna 2022) and may share circuit components, software or firmware, or alternatively be implemented separately.

In the illustrated embodiment, communication functions of the communication interface 2012 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 2012, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., an alert is sent when moisture is detected), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to UE 2000 shown in Figure 20.

As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3 GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.

In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

Figure 21 shows a network node 2100 in accordance with some embodiments. Examples of network nodes include, but are not limited to, access points (e.g., radio access points) and base stations (e.g., radio base stations, Node Bs, eNBs, and gNBs).

Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).

The network node 2100 includes a processing circuitry 2102, a memory 2104, a communication interface 2106, and a power source 2108. The network node 2100 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 2100 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 2100 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 2104 for different RATs) and some components may be reused (e.g., a same antenna 2110 may be shared by different RATs). The network node 2100 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 2100, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 2100.

Processing circuitry 2102 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 2100 components, such as the memory 2104, to provide network node 2100 functionality. In some embodiments, processing circuitry 2102 includes a system on a chip (SOC). In some embodiments, processing circuitry 2102 includes one or more of radio frequency (RF) transceiver circuitry 2112 and baseband processing circuitry 2114. In some embodiments, the radio frequency (RF) transceiver circuitry 2112 and the baseband processing circuitry 2114 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 2112 and baseband processing circuitry 2114 may be on the same chip or set of chips, boards, or units.

Memory 2104 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 2102. The memory 2104 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions (collective denoted computer program product 2104a) capable of being executed by processing circuitry 2102 and utilized by the network node 2100. Memory 2104 may be used to store any calculations made by processing circuitry 2102 and/or any data received via the communication interface 2106. In some embodiments, processing circuitry 2102 and memory 2104 is integrated.

Communication interface 2106 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 2106 comprises port(s)/terminal(s) 2116 to send and receive data, for example to and from a network over a wired connection. The communication interface 2106 also includes radio front-end circuitry 2118 that may be coupled to, or in certain embodiments a part of, the antenna 2110. Radio front-end circuitry 2118 comprises filters 2120 and amplifiers 2122, and may be connected to antenna 2110 and processing circuitry 2102. The radio front-end circuitry may be configured to condition signals communicated between antenna 2110 and processing circuitry 2102.

Radio front-end circuitry 2118 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. Radio front-end circuitry 2118 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 2120 and/or amplifiers 2122. The radio signal may then be transmitted via antenna 2110. Similarly, when receiving data, antenna 2110 may collect radio signals which are then converted into digital data by radio front-end circuitry 2118. The digital data may be passed to processing circuitry 2102. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, the network node 2100 does not include separate radio front-end circuitry 2118, instead, processing circuitry 2102 includes radio front-end circuitry and is connected to the antenna 2110. Similarly, in some embodiments, all or some of the RF transceiver circuitry 2112 is part of the communication interface 2106. In still other embodiments, the communication interface 2106 includes one or more ports or terminals 2116, the radio frontend circuitry 2118, and the RF transceiver circuitry 2112, as part of a radio unit (not shown), and the communication interface 2106 communicates with the baseband processing circuitry 2114, which is part of a digital unit (not shown).

The antenna 2110 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 2110 may be coupled to the radio front-end circuitry 2118 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 2110 is separate from the network node 2100 and connectable to the network node 2100 through an interface or port.

The antenna 2110, communication interface 2106, and/or processing circuitry 2102 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 2110, the communication interface 2106, and/or processing circuitry 2102 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.

The power source 2108 provides power to the various components of network node 2100 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 2108 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 2100 with power for performing the functionality described herein. For example, the network node 2100 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 2108. As a further example, the power source 2108 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail. Embodiments of the network node 2100 may include additional components beyond those shown in Figure 21 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 2100 may include user interface equipment to allow input of information into the network node 2100 and to allow output of information from the network node 2100. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 2100.

Also, various arrangements and/or configurations of network node 2100 can be used to implement various nodes or functions that perform exemplary procedures described herein, such as LMFs, UDM functions, GMLCs, etc.

Figure 22 is a block diagram of a host 2200, which may be an embodiment of the host 1916 of Figure 19, in accordance with various aspects described herein. As used herein, the host 2200 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 2200 may provide one or more services to one or more UEs.

Host 2200 includes processing circuitry 2202 that is operatively coupled via bus 2204 to input/output interface 2206, network interface 2208, power source 2210, and memory 2212. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 20 and 21, such that the descriptions thereof are generally applicable to the corresponding components of host 2200.

The memory 2212 may include one or more computer programs including one or more host application programs 2214 and data 2216, which may include user data, e.g., data generated by a UE for the host 2200 or data generated by the host 2200 for a UE. Embodiments of the host 2200 may utilize only a subset or all of the components shown. The host application programs 2214 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 2214 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 2200 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 2214 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

Figure 23 is a block diagram illustrating a virtualization environment 2300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 2300 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

Applications 2302 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

Hardware 2304 includes processing circuitry, memory that stores software and/or instructions (collective denoted computer program product 2304a) executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 2306 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 2308a and 2308b (one or more of which may be generally referred to as VMs 2308), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 2306 may present a virtual operating platform that appears like networking hardware to the VMs 2308.

The VMs 2308 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 2306. Different embodiments of the instance of a virtual appliance 2302 may be implemented on one or more of VMs 2308, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, a VM 2308 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 2308, and that part of hardware 2304 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 2308 on top of the hardware 2304 and corresponds to the application 2302.

Hardware 2304 may be implemented in a standalone network node with generic or specific components. Hardware 2304 may implement some functions via virtualization. Alternatively, hardware 2304 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 2310, which, among others, oversees lifecycle management of applications 2302. In some embodiments, hardware 2304 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 2312 which may alternatively be used for communication between hardware nodes and radio units.

Also, virtualization environment 2300 can be used to implement and/or host various nodes or functions that perform exemplary procedures described herein, such as LMFs, UDM functions, GMLCs, etc. For example, one or more of these nodes or functions can be implemented as a virtual node 2302 in virtualization environment 2300.

Figure 24 shows a communication diagram of host 2402 communicating via network node 2404 with UE 2406 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1912a of Figure 19 and/or UE 2000 of Figure 20), network node (such as network node 1910a of Figure 19 and/or network node 2100 of Figure 21), and host (such as host 1916 of Figure 19 and/or host 2200 of Figure 22) discussed in the preceding paragraphs will now be described with reference to Figure 24.

Like host 2200, embodiments of host 2402 include hardware, such as a communication interface, processing circuitry, and memory. Host 2402 also includes software, which is stored in or accessible by host 2402 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as UE 2406 connecting via an over-the-top (OTT) connection 2450 extending between UE 2406 and host 2402. In providing the service to the remote user, a host application may provide user data which is transmitted using OTT connection 2450.

Network node 2404 includes hardware enabling it to communicate with host 2402 and UE 2406. The connection 2460 may be direct or pass through a core network (like core network 1906 of Figure 19) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

UE 2406 includes hardware and software, which is stored in or accessible by UE 2406 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 2406 with the support of host 2402. In host 2402, an executing host application may communicate with the executing client application via OTT connection 2450 terminating at UE 2406 and host 2402. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. OTT connection 2450 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through OTT connection 2450.

OTT connection 2450 may extend via a connection 2460 between host 2402 and network node 2404 and via a wireless connection 2470 between network node 2404 and UE 2406 to provide the connection between host 2402 and UE 2406. The connection 2460 and wireless connection 2470, over which OTT connection 2450 may be provided, have been drawn abstractly to illustrate the communication between host 2402 and UE 2406 via network node 2404, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

As an example of transmitting data via OTT connection 2450, in step 2408, host 2402 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with UE 2406. In other embodiments, the user data is associated with a UE 2406 that shares data with host 2402 without explicit human interaction. In step 2410, host 2402 initiates a transmission carrying the user data towards UE 2406. Host 2402 may initiate the transmission responsive to a request transmitted by UE 2406. The request may be caused by human interaction with UE 2406 or by operation of the client application executing on UE 2406. The transmission may pass via network node 2404, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 2412, network node 2404 transmits to UE 2406 the user data that was carried in the transmission that host 2402 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2414, UE 2406 receives the user data carried in the transmission, which may be performed by a client application executed on UE 2406 associated with the host application executed by host 2402.

In some examples, UE 2406 executes a client application which provides user data to host 2402. The user data may be provided in reaction or response to the data received from host 2402. Accordingly, in step 2416, UE 2406 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of UE 2406. Regardless of the specific manner in which the user data was provided, UE 2406 initiates, in step 2418, transmission of the user data towards host 2402 via network node 2404. In step 2420, in accordance with the teachings of the embodiments described throughout this disclosure, network node 2404 receives user data from UE 2406 and initiates transmission of the received user data towards host 2402. In step 2422, host 2402 receives the user data carried in the transmission initiated by UE 2406.

One or more of the various embodiments improve the performance of OTT services provided to UE 2406 using OTT connection 2450, in which wireless connection 2470 forms the last segment. More precisely, embodiments described herein ensure that the PRU usage is fully authorized, such that a network can authenticate that a node claiming to be a PRU is an actual PRU before using the node/PRU for positioning-related procedures. Also, embodiments can ensure that LMF-initiated location requests are only for authorized PRUs and not for any non- PRU device or unauthorized PRU. Additionally, embodiments improve positioning privacy by preventing malicious LMFs from obtaining location of a non-PRU device using procedures intended for obtaining location of a PRU. In this manner, embodiments improve security and privacy of positioning-related procedures involving PRUs. Accordingly, embodiments increase the value of OTT services that rely on positioning to both end users and services providers.

In an example scenario, factory status information may be collected and analyzed by host 2402. As another example, host 2402 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, host 2402 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, host 2402 may store surveillance video uploaded by a UE. As another example, host 2402 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, host 2402 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.

In some examples, 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 OTT connection 2450 between host 2402 and UE 2406, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of host 2402 and/or UE 2406. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which OTT connection 2450 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 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 2450 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of network node 2404. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by host 2402. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 2450 while monitoring propagation times, errors, etc.

The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in view of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the disclosure and can be thus within the spirit and scope of the disclosure. Various exemplary embodiments can be used together with one another, as well as interchangeably therewith, as should be understood by those having ordinary skill in the art.

The term unit, as used herein, can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

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

As described herein, device and/or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor. Furthermore, functionality of a device or apparatus can be implemented by any combination of hardware and software. A device or apparatus can also be regarded as an assembly of multiple devices and/or apparatuses, whether functionally in cooperation with or independently of each other. Moreover, devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.

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.

In addition, certain terms used in the present disclosure, including the specification and drawings, can be used synonymously in certain instances (e.g., “data” and “information”). It should be understood, that although these terms (and/or other terms that can be synonymous to one another) can be used synonymously herein, there can be instances when such words can be intended to not be used synonymously.

Embodiments of the techniques and apparatus described herein also include, but are not limited to, the following enumerated examples: Al . A method for a location management function (LMF) of a communication network, the method comprising: sending, to a first node or function of the communication network, a request to perform a positioning procedure with a target device in the communication network, wherein the request includes an indication that the target device is a positioning reference unit (PRU); receiving, from a second node or function of the communication network, a response including one of the following associated with at least one of the target device and the positioning procedure: an indication or an identifier; and based on the identifier, performing the positioning procedure with the target device as a PRU.

A2. The method of embodiment Al, wherein the indication that the target device is a PRU is one of the following associated with a particular PRU: a subscription permanent identifier, (SUPI) or a generic public subscription identifier (GPSI).

A3. The method of embodiment A2, wherein the response indicates that the LMF is authorized to perform the positioning procedure with the particular PRU.

A4. The method of any of embodiments A2-A3, wherein the identifier included in the response is a correlation identifier that enables the LMF to communicate with the particular PRU.

A5. The method of embodiment A4, wherein the first node or function is a gateway mobile location center (GMLC), and the second node or function is an access and mobility management function (AMF).

A6. The method of embodiment A4, wherein the first node or function is an access and mobility management function (AMF), and the second node or function is the same AMF.

A7. The method of any of embodiments A3-A6, wherein: the response also includes a further indication of one or more of the following: the particular PRU’s location is known by the second node or function, and the particular PRU’s location should be provided by the LMF; and performing the positioning procedure comprises selectively obtaining the particular PRU’s location during the positioning procedure, based on the further indication.

A8. The method of embodiment A2, wherein the first node or function is the particular PRU, the second node or function is the particular PRU, and the response includes an acknowledgement that the LMF is authorized to perform the positioning procedure with the particular PRU.

Bl. A method for a gateway mobile location center (GMLC) of a communication network, the method comprising: receiving, from a location management function (LMF) of the communication network, a request to perform a positioning procedure with a target device in the communication network, wherein the request includes a first indication that the target device is a positioning reference unit (PRU); determining whether the LMF is authorized to perform the positioning procedure with the target device as a PRU; and based on determining that the LMF is authorized, sending a location request to an access and mobility management function (AMF) of the communication network, wherein the location request includes a second indication that the target device is a PRU.

B2. The method of embodiment Bl, wherein the first indication that the target device is a PRU is one of the following associated with the target device: a subscription permanent identifier (SUPI), or a generic public subscription identifier (GPSI).

B3. The method of embodiment B2, wherein: the GMLC is configured with a list comprising a plurality of SUPIs associated with a respective plurality of PRUs authorized to perform positioning procedures with the LMF; and determining whether the LMF is authorized to perform the positioning procedure with the target device as a PRU comprises comparing the SUPI associated with the target device to the SUPIs comprising the list.

B4. The method of embodiment B2, wherein determining whether the LMF is authorized to perform the positioning procedure with the target device as a PRU comprises: sending the SUPI or the GPSI associated with the target device to a unified data management (UDM) function of the communication network; and receiving, from the UDM function, a third indication of whether the target device supports or allows positioning as a PRU; and determining whether the LMF is authorized based on the third indication.

B5. The method of any of embodiments B1-B4, wherein the location request to the AMF further indicates one or more of the following: that reference measurements should be performed by the target device as a PRU; and that a location of the target device is not required.

Cl . A method for a unified data management (UDM) function of a communication network, the method comprising: receiving, from an access and mobility management function (AMF) of the communication network, a request for a location management function (LMF) of the communication network to perform a positioning procedure with a target device in the communication network, wherein the request includes a first indication that the target device is a positioning reference unit (PRU); and sending, to the AMF, a second indication of whether the target device supports or allows positioning as a PRU.

C2. The method of embodiment Cl, wherein the first indication that the target device is a PRU is one of the following associated with the target device: a subscription permanent identifier (SUPI), or a generic public subscription identifier (GPSI).

C3. The method of embodiment C2, wherein: the UDM is configured with a list of location services (LCS) clients that are permitted to perform positioning procedures with the target device as a PRU; and the method further comprises determining the second indication based on whether the LMF is among the list of LCS clients.

DI. A method for a positioning target device operating in a communication network, the method comprising: receiving, from a location management function (LMF) of the communication network, a request to perform a positioning procedure as a positioning reference unit (PRU); and sending one of the following messages in response: to the LMF, an acknowledgement that the positioning target device will perform the requested positioning procedure as a PRU; or to another node or function of the communication network, an indication that the positioning target device will not perform the positioning procedure requested by the LMF.

D2. The method of embodiment DI, wherein the indication that the positioning target device will not perform the positioning procedure requested by the LMF includes a failure cause indication.

D3. The method of embodiment D2, wherein the indicated failure cause is one of the following: PRU functionality note supported, potential security issue, or potential privacy issue.

D4. The method of any of embodiments D1-D3, wherein one of the following applies: the other node or function is a radio access network (RAN) node and the indication is sent in a radio resource control (RRC) message; or the other node or function is an access and mobility management function (AMF) and the indication is sent in a non-access stratum (NAS) message.

El . A location management function (LMF) configured to operate in a communication network, the LMF comprising: communication interface circuitry configured to communicate with a plurality of other nodes or functions of the communication network and with positioning target devices; and processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to perform operations corresponding to any of the methods of embodiments A1-A8.

E2. A location management function (LMF) configured to operate in a communication network, the LMF being further configured to perform operations corresponding to any of the methods of embodiments A1-A8. E3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry associated with a location management function (LMF) configured to operate in a communication network, configure the LMF to perform operations corresponding to any of the methods of embodiments A1-A8.

E4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry associated with a location management function (LMF) configured to operate in a communication network, configure the LMF to perform operations corresponding to any of the methods of embodiments A1-A8.

FL A gateway mobile location center (GMLC) configured to operate in a communication network, the GMLC comprising: communication interface circuitry configured to communicate with one or more other nodes or functions of the communication network; and processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to perform operations corresponding to any of the methods of embodiments B1-B5.

F2. A gateway mobile location center (GMLC) configured to operate in a communication network, the GMLC being further configured to perform operations corresponding to any of the methods of embodiments B1-B5.

F3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry associated with a gateway mobile location center (GMLC) configured to operate in a communication network, configure the GMLC to perform operations corresponding to any of the methods of embodiments B1-B5.

F4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry associated with a gateway mobile location center (GMLC) configured to operate in a communication network, configure the GMLC to perform operations corresponding to any of the methods of embodiments B1-B5.

G1. A unified data management (UDM) function configured to operate in a communication network, the UDM function comprising: communication interface circuitry configured to communicate with an access and mobility management function (AMF) of the communication network; and processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to perform operations corresponding to any of the methods of embodiments C1-C3.

G2. A unified data management (UDM) function configured to operate in a communication network, the UDM function being further configured to perform operations corresponding to any of the methods of embodiments C1-C3.

G3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry associated with a unified data management (UDM) function configured to operate in a communication network, configure the UDM function to perform operations corresponding to any of the methods of embodiments C1-C3.

G4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry associated with a unified data management (UDM) function configured to operate in a communication network, configure the UDM function to perform operations corresponding to any of the methods of embodiments C1-C3.

Hl . A positioning target device configured to operate in a communication network, the positioning target device comprising: communication interface circuitry configured to communicate with a location management function (LMF) of the communication network via a radio access network (RAN); and processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to perform operations corresponding to any of the methods of embodiments D1-D4.

H2. A positioning target device configured to operate in a communication network, the positioning target device being further configured to perform operations corresponding to any of the methods of embodiments D1-D4. H3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a positioning target device configured to operate in a communication network, configure the positioning target device to perform operations corresponding to any of the methods of embodiments D1-D4.

H4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a positioning target device configured to operate in a communication network, configure the positioning target device to perform operations corresponding to any of the methods of embodiments D1-D4.

Claims

1. A method for a location management function, LMF, of a communication network, the method comprising: sending (1510), to an access and mobility management function, AMF, of the communication network, a request to perform a positioning procedure with a target device in the communication network, wherein the request includes an indication that the target device is a positioning reference unit, PRU; receiving (1520), from the AMF, a response including an identifier associated with at least one of the target device and the positioning procedure; and based on the response, performing (1530) the positioning procedure with the target device as a PRU.

2. The method of claim 1, wherein the indication that the target device is a PRU is one of the following associated with the target device: a subscription permanent identifier, SUPI; or a generic public subscription identifier, GPSI.

3. The method of claim 2, wherein the response indicates that the LMF is authorized to perform the positioning procedure with the target device as a PRU.

4. The method of any of claims 2-3, wherein the identifier is a correlation identifier, ID, that enables the LMF to communicate with the target device.

5. The method of any of claims 3-4, wherein: the response also includes a further indication of one or more of the following: the target device’s location is known by the AMF, and the target device’s location should not be reported to the AMF; and performing (1530) the positioning procedure based on the response comprises selectively obtaining (1531) the target device’s location during the positioning procedure, based on the further indication.

6. A method for a unified data management, UDM, function of a communication network, the method comprising: receiving (1710), from an access and mobility management function, AMF, of the communication network, a request for a location management function, LMF, of

53 the communication network to perform a positioning procedure with a target device in the communication network, wherein the request includes a first indication that the target device is a positioning reference unit, PRU; and sending, to the AMF, a second indication of whether the target device supports or allows positioning as a PRU.

7. The method of claim 6, wherein: the UDM is configured with a list of PRUs that are authorized to be located by the LMF; and the method further comprises determining (1720) the second indication based on whether the target device is among the list of PRUs authorized to be located.

8. The method of claim 7, wherein: the first indication that the target device is a PRU is one of the following associated with the target device: a subscription permanent identifier, SUPI; or a generic public subscription identifier, GPSI; and the list of PRUs comprises a list of SUPIs associated with PRUs that are authorized to be located.

9. The method of any of claims 6-8, wherein when the second indication indicates that the target device supports or allows positioning as a PRU, the second indication also indicates whether the target device is mobile or stationary.

10. A method for a positioning target device configured to operate in a communication network, the method comprising: receiving (1810), from a location management function, LMF, of the communication network, a request to perform a positioning procedure as a positioning reference unit, PRU; and performing (1820) one of the following operations based on determining that the positioning target device will not perform the requested positioning procedure as a PRU: refraining (1821) from responding to the request; or sending (1822) an indication that the positioning target device will not perform the requested positioning procedure as a PRU.

54

11. The method of embodiment 10, wherein the indication is sent to a node or function of the communication network other than the LMF.

12. The method of claim 11, wherein one of the following applies: the node or function is a radio access network, RAN, node and the indication is sent in a radio resource control, RRC, message; or the node or function is an access and mobility management function, AMF, and the indication is sent in a non-access stratum, NAS, message.

13. The method of any of claims 10-12, wherein the indication that the positioning target device will not perform the requested positioning procedure includes a failure cause indication, which indicates a reason why the positioning target device determined it will not perform the requested positioning procedure.

14. The method of claim 13, wherein the indicated failure cause is one of the following: PRU functionality not supported, potential security issue, or potential privacy issue.

15. The method of any of claims 10-14, further comprising, based on determining that the positioning target device will perform the requested positioning procedure as a PRU, sending (1830) to the LMF an acknowledgement that the positioning target device will perform the requested positioning procedure as a PRU.

16. A location management function, LMF (840, 930, 1030, 1130, 1230, 1330, 1908, 2100, 2302) configured to operate in a communication network (198, 1902), the LMF comprising: communication interface circuitry (2106, 2304) configured to communicate with a plurality of other nodes or functions of the communication network and with positioning target devices (810, 910, 1310, 1912, 2000, 2406); and processing circuitry (2102, 2304) operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to: send, to an access and mobility management function, AMF (830, 920, 1130, 1220, 1908, 2100, 2302) of the communication network, a request to perform a positioning procedure with a target device in the communication network, wherein the request includes an indication that the target device is a positioning reference unit, PRU;

55 receive, from the AMF, a response including an identifier associated with at least one of the target device and the positioning procedure; and based on the response, perform the positioning procedure with the target device as a PRU.

17. The LMF of claim 16, wherein the processing circuitry and the communication interface circuitry are further configured to perform operations corresponding to any of the methods of claims 2-5.

18. A location management function, LMF (840, 930, 1030, 1130, 1230, 1330, 1908, 2100, 2302) configured to operate in a communication network (198, 1902), the LMF being further configured to: send, to an access and mobility management function, AMF (830, 920, 1130, 1220, 1908, 2100, 2302) of the communication network, a request to perform a positioning procedure with a target device (810, 910, 1310, 1912, 2000, 2406) in the communication network, wherein the request includes an indication that the target device is a positioning reference unit, PRU; receive, from the AMF, a response including an identifier associated with at least one of the target device and the positioning procedure; and based on the response, perform the positioning procedure with the target device as a PRU.

19. The LMF of claim 18, being further configured to perform operations corresponding to any of the methods of claims 2-5.

20. A non-transitory, computer-readable medium (2104, 2304) storing computer-executable instructions that, when executed by processing circuitry (2102, 2304) associated with a location management function, LMF (840, 930, 1030, 1130, 1230, 1330, 1908, 2100, 2302) configured to operate in a communication network (198, 1902), configure the LMF to perform operations corresponding to any of the methods of claims 1-5.

21. A computer program product (2104a, 2304a) comprising computer-executable instructions that, when executed by processing circuitry (2102, 2304) associated with a location management function, LMF (840, 930, 1030, 1130, 1230, 1330, 1908, 2100, 2302) configured to

56 operate in a communication network (198, 1902), configure the LMF to perform operations corresponding to any of the methods of claims 1-5.

22. A unified data management, UDM, function (950, 1150, 1250, 1908, 2100, 2302) configured to operate in a communication network (198, 1902), the UDM function comprising: communication interface circuitry (2106, 2304) configured to communicate with an access and mobility management function, AMF (830, 920, 1020, 1120, 1220, 1908, 2100, 2302) of the communication network; and processing circuitry (2102, 2304) operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to: receive, from the AMF, a request for a location management function, LMF (840, 930, 1030, 1130, 1230, 1330, 1908, 2100, 2302) of the communication network to perform a positioning procedure with a target device (810, 910, 1310, 1912, 2000, 2406) in the communication network, wherein the request includes a first indication that the target device is a positioning reference unit, PRU; and send, to the AMF, a second indication of whether the target device supports or allows positioning as a PRU.

23. The UDM function of claim 22, wherein the processing circuitry and the communication interface circuitry are further configured to perform operations corresponding to any of the methods of claims 7-9.

24. A unified data management, UDM, function (950, 1150, 1250, 1908, 2100, 2302) configured to operate in a communication network (198, 1902), the UDM function being further configured to: receive, from an access and mobility management function, AMF (830, 920, 1020, 1120, 1220, 1908, 2100, 2302) of the communication network, a request for a location management function, LMF (840, 930, 1030, 1130, 1230, 1330, 1908, 2100, 2302) of the communication network to perform a positioning procedure with a target device (810, 910, 1310, 1912, 2000, 2406) in the communication network, wherein the request includes a first indication that the target device is a positioning reference unit, PRU; and send, to the AMF, a second indication of whether the target device supports or allows positioning as a PRU.

25. The UDM function of claim 24, being further configured to perform operations corresponding to any of the methods of claims 7-9.

26. A non-transitory, computer-readable medium (2104, 2304) storing computer-executable instructions that, when executed by processing circuitry (2102, 2304) associated with a unified data management, UDM, function (950, 1150, 1250, 1908, 2100, 2302) configured to operate in a communication network (198, 1902), configure the UDM function to perform operations corresponding to any of the methods of claims 6-9.

27. A computer program product (2104a, 2304a) comprising computer-executable instructions that, when executed by processing circuitry (2102, 2304) associated with a unified data management, UDM, function (950, 1150, 1250, 1908, 2100, 2302) configured to operate in a communication network (198, 1902), configure the UDM function to perform operations corresponding to any of the methods of claims 6-9.

28. A positioning target device (810, 910, 1310, 1912, 2000, 2406) configured to operate in a communication network (198, 1902), the positioning target device comprising: communication interface circuitry (2012) configured to communicate with at least a location management function, LMF (840, 930, 1030, 1130, 1230, 1330, 1908, 2100, 2302) of the communication network, via a radio access network, RAN (199, 820, 1904); and processing circuitry (2002) operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to: receive, from the LMF, a request to perform a positioning procedure as a positioning reference unit, PRU; and perform one of the following operations based on determining that the positioning target device will not perform the requested positioning procedure as a PRU: refrain from responding to the request; or send an indication that the positioning target device will not perform the requested positioning procedure as a PRU.

29. The positioning target device of claim 28, wherein the processing circuitry and the communication interface circuitry are further configured to perform operations corresponding to any of the methods of claims 11-15.

30. A positioning target device (810, 910, 1310, 1912, 2000, 2406) configured to operate in a communication network (198, 1902), the positioning target device being further configured to: receive, from a location management function, LMF (840, 930, 1030, 1130, 1230, 1330, 1908, 2100, 2302) of the communication network, a request to perform a positioning procedure as a positioning reference unit, PRU; and perform one of the following operations based on determining that the positioning target device will not perform the requested positioning procedure as a PRU: refrain from responding to the request; or send an indication that the positioning target device will not perform the requested positioning procedure as a PRU.

31. The positioning target device of claim 30, being further configured to perform operations corresponding to any of the methods of claims 11-15.

32. A non-transitory, computer-readable medium (2010) storing computer-executable instructions that, when executed by processing circuitry (2002) of a positioning target device (810, 910, 1310, 1912, 2000, 2406) configured to operate in a communication network (198, 1902), configure the positioning target device to perform operations corresponding to any of the methods of claims 10-15.

33. A computer program product (2014) comprising computer-executable instructions that, when executed by processing circuitry (2002) of a positioning target device (810, 910, 1310, 1912, 2000, 2406) configured to operate in a communication network (198, 1902), configure the positioning target device to perform operations corresponding to any of the methods of claims 10-15.

59