WO2024205481A1

WO2024205481A1 - Selective network storage of assisting user equipment (ue) information

Info

Publication number: WO2024205481A1
Application number: PCT/SE2024/050291
Authority: WO
Inventors: Ritesh SHREEVASTAV; Göran RUNE; Richárd BÁTORFI
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2023-03-30
Filing date: 2024-03-28
Publication date: 2024-10-03
Anticipated expiration: 2025-09-30

Abstract

Embodiments include methods for a network function (NF) configured to manage positioning and/or sensing operations in a communication network. Such methods include receiving, from an access and mobility management function (AMF) of the communication network, an association request for a user equipment (UE). The association request includes or is received with the following information: a first indication that the UE is configured to operate as an assisting UE, and a second indication of whether the UE is stationary or mobile. Such methods include sending to the AMF an association response indicating whether the NF accepted the association request for the UE and, when the NF accepts the association request, selectively storing, based on the second indication, information about the UE's operation as an assisting UE. Other embodiments include complementary methods for an AMF and for a UE.

Description

SELECTIVE NETWORK STORAGE OF ASSISTING USER EQUIPMENT (UE) INFORMATION

TECHNICAL FIELD

The present disclosure relates generally to positioning or sensing operations performed in a radio access network (RAN), and more specifically to techniques for handling network storage of information related to user equipment (UEs) configured to assist with positioning or sensing with respect to other targets in the RAN.

BACKGROUND

Currently the fifth generation (5G) of cellular systems is being standardized within the Third-Generation Partnership Project (3GPP). 5G is developed for maximum flexibility to support many different use cases including 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 a high-level view of an exemplary 5G network architecture, consisting of a Next Generation Radio Access Network (NG-RAN, 199) and a 5G Core (5GC, 198). The NG-RAN can include one or more gNodeB’s (gNBs) connected to the 5GC via one or more NG interfaces, such as gNBs (100, 150) connected via respective interfaces (102, 152). More specifically, the gNBs can be connected to one or more Access and Mobility Management Functions (AMFs) in the 5GC via respective NG-C interfaces and to one or more User Plane Functions (UPFs) in 5GC via respective NG-U interfaces. The 5GC can include various other network functions (NFs), such as Session Management Function(s) (SMF).

The NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). 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.

NG RAN logical nodes (e.g., gNB 100) include a Central Unit (CU or gNB-CU, e.g., 110) and one or more Distributed Units (DU or gNB-DU, e.g., 120, 130). CUs are logical nodes that host higher-layer protocols and perform various gNB functions such controlling the operation of DUs. DUs are decentralized logical nodes that host lower layer protocols and can include, depending on the functional split option, various subsets of the gNB functions. Each CU and DU can include various circuitry needed to perform their respective functions, including processing circuitry, communication interface circuitry e.g., transceivers), and power supply circuitry.

A gNB-CU connects to one or more gNB-DUs over respective Fl logical interfaces (e.g., 122 and 132 shown in Figure 1). However, each gNB-DU can be connected to only one gNB-CU. The gNB-CU and its connected gNB-DU(s) are only visible to other gNBs and the 5GC as a gNB. In other words, the Fl interface is not visible beyond gNB-CU.

Another change in 5G networks (e.g., in 5GC) is that traditional peer-to-peer interfaces and protocols found in earlier-generation networks are modified and/or replaced by a Service Based Architecture (SB A) in which Network Functions (NFs) provide one or more services to one or more service consumers. This can be done, for example, by Hyper Text Transfer Protocol/Representational State Transfer (HTTP/REST) application programming interfaces (APIs). In general, the various services are self-contained functionalities that can be changed and modified in an isolated manner without affecting other services.

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.

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, which can transmit uplink (UL) reference signals, perform positioning measurements, and report these measurements to a positioning node. 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. From the positioning node’s perspective, the PRU is considered to be a UE at a known location.

Recently, 3GPP defined some use cases and requirements for sensing in 3GPP TR 22.837 (v0.3.0) and has defined study items to identify use cases and architectural enhancements that will enable joint communications and sensing (JCAS) in cellular networks. In this context, the general goal of sensing is to detect and localize a target that is not necessarily connected to the network, such as a pedestrian, an animal, an object, etc.

Sensing involves the network transmitting radio signals and receiving/measuring versions of those signals that have been reflected by the target (and possibly other surroundings). The transmitting and receiving can be performed by the same node(s) or by different node(s). Processing output of the sensing measurements yields information of the target and its surroundings that the radio signals interacted with, possibly including sources of attenuation, reflection, refraction, etc.

A sensing request may originate from applications external to the network. 3 GPP has defined a Sensing Management Function (SeMF) to handle these requests and to trigger the necessary sensing operations in the RAN, including any UEs that have capability to assist with the sensing. SeMF is a logical entity that resides in the RAN (e.g., gNB) or in 5GC (e.g., a NF).

SUMMARY

An unresolved technical issue is how PRUs should be registered in a 5G network, such that other network nodes or functions are aware of their existence and capabilities. Different proposed solutions involve storing PRU information (including location) in the NRF in 5GC. However, this violates some general policies for use of NRF.

For example, NRF is generally expected to handle static storage and is not designed to handle frequently updated information. Even if a PRU’s location is known, it may also change as the PRU (as a UE) moves around the network. This may occur frequently since there are no restrictions on PRU movement. In such case, the PRU’s information stored in NRF would need to be updated frequently, which violates policies on NRF usage. Similar problems may occur when information of UEs that assist with sensing is stored in NRF, since locations of the sensing UEs may also change frequently.

An object of embodiments of the present disclosure is to improve network management of information about UEs that assist with measurement or sensing tasks in the network, 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 a network function (NF) configured to manage positioning and/or sensing operations in a communication network. These exemplary methods include receiving, from an access and mobility management function (AMF) of the communication network, an association registration request for a UE. The association request includes or is received with the following: a first indication that the UE is configured to operate as an assisting UE, and a second indication of whether the UE is stationary or mobile. These exemplary methods also include sending to the AMF an association response indicating whether the NF accepted the association request for the UE. These exemplary methods also include, when the NF accepts the association request, selectively storing, based on the second indication, information about the UE’s operation as an assisting UE. In some embodiments, the association request includes the second indication only when the second indication indicates that the UE is stationary, and absence of the second indication from the association request indicates that the UE is mobile.

In some embodiments, selectively storing the information based on the second indication includes the following operations:

• when the second indication indicates that the UE is stationary, storing the information in a network repository function (NRF) of the communication network; and

• when the second indication indicates that the UE is mobile, performing one of the following: discarding the information, or storing the information locally in the NF.

In some embodiments, the selectively stored information includes an association between the UE and one or more of the following: a tracking area, a serving cell, one or more neighbor cells, and geographic coordinates. In some embodiments, at least a portion of the selectively stored information is included in the association request.

In some embodiments, the association request also includes one or more of the following information: a reason for the association, a third indication of the UE’s positioning and/or sensing capabilities, UE location information, and a second identifier associated with a user subscription to the communication network (e.g., SUPI).

Other embodiments include methods e.g., procedures) for an AMF of a communication network. These exemplary methods include receiving from a UE an association request that includes a first indication that the UE is configured to operate as an assisting UE. These exemplary methods also include verifying the first indication based on subscription information for the UE. These exemplary methods also include, based on verifying the first indication, sending a further association request for the UE to a NF configured to manage positioning and/or sensing operations in the communication network. The further association request includes or is sent together with the following: a first indication that the UE is configured to operate as an assisting UE, and a second indication of whether the UE is stationary or mobile.

In some embodiments, the further association request includes or is sent with the second indication only when the second indication indicates that the UE is stationary, and absence of the second indication in or with the further association request indicates that the UE is mobile. In some embodiments, further association request includes or is sent together with an indication that the AMF verified the first indication.

In some of these embodiments, the association request from the UE also includes one or more of the following: a reason for the association, a further indication of whether the UE is stationary or mobile, a third indication of the UE’s positioning and/or sensing capabilities, UE location information, a first identifier associated with the UE (e.g., PEI), and a second identifier associated with a user subscription to the communication network (e.g., SUPI).

In some of these embodiments, these exemplary methods also include, using the first identifier or the second identifier, retrieving the subscription information for the UE from a unified data management function (UDM) of the communication network. Also, verifying the first indication is based on the retrieved subscription information.

In some embodiments, these exemplary methods also include receiving from the NF an association response indicating whether the NF accepted the further association request for the UE and forwarding the association response to the UE. In some of these embodiments, the association request is received together with a routing identifier and these exemplary methods also include selecting the NF based on one or more of the following: the routing identifier, and a tracking area associated with the UE.

Other embodiments include methods e.g., procedures) for a UE configured to assist with positioning and/or sensing operations in a communication network. These exemplary methods include sending, to an AMF of the communication network, an association request that includes a first indication that the UE is configured to operate as an assisting UE. These exemplary methods also include receiving from the AMF a response indicating whether the association request was accepted or rejected by a NF configured to manage positioning and/or sensing operations in the communication network.

In some embodiments, the association request also includes one or more of the following: a reason for the association, a second indication of whether the UE is stationary or mobile, a third indication of the UE’s positioning and/or sensing capabilities, UE location information, a first identifier associated with the UE (e.g., PEI), and a second identifier associated with a user subscription to the communication network (e.g., SUPI).

In some embodiments, the association request is sent together with a routing identifier associated with the NF, and the association response includes one of the following:

• a correlation identifier associated with the NF, when the association response indicates that the NF accepted the association request; or

• a second routing identifier associated with a different NF, when the association response indicates that the NF rejected the association request.

In some embodiments, the UE is a PRU and the NF is a location management function (LMF) in a 5GC. In other embodiments, the UE is a sensing UE and the NF is a sensing management function (SeMF) in a 5GC.

Other embodiments include network equipment configured to implement the AMF and/or the NF (e.g., LMF, SeMF, etc.) that perform some exemplary methods summarized above, as well as UEs (e.g., wireless devices, etc.) configured to perform other exemplary methods summarized above. Other embodiments include non-transitory, computer-readable media storing program instructions that, when executed by processing circuitry, configure such UEs, NFs, and AMFs to perform operations corresponding to any of the exemplary methods described herein.

These and other embodiments described herein may limit the storage of PRU information in LMF NF profile in NRF to only stationary PRUs. Since stationary PRUs are not moving, the PRU information in the LMF’s NF profile can be stored once without need for updates (e.g., removal and addition of PRUs). In this manner, PRUs deployed as stationary devices associated with an LMF may be identified in the LMF’s NF profile, while other non-stationary PRUs are not. This storage selectivity may reduce network signaling, prevent NRF from becoming a “dynamic” database, and retain the NRF design principle of storage of network-related information (e.g., LMF-associated PRUs) rather than UE-related information that can change frequently as UEs change cells, tracking areas, etc.

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 view of an exemplary 5G/NR network architecture.

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

Figure 3 shows signaling diagrams for four different solutions for positioning reference unit (PRU) management.

Figure 4 illustrates three different sensing techniques that can be used in a cellular network.

Figure 5 illustrates how a sensing management function (SeMF) can control sensing patterns for three gNBs.

Figure 6 is a signaling diagram according to various embodiments of the present disclosure.

Figure 7 shows a signaling diagram of a PRU association procedure according to some embodiments of the present disclosure.

Figure 8 shows a signaling diagram of an LMF-initiated PRU disassociation procedure according to some embodiments of the present disclosure.

Figure 9 shows a signaling diagram of a PRU-initiated PRU disassociation procedure according to some embodiments of the present disclosure.

Figure 10 shows a flow diagram of an exemplary method (e.g., procedure) for a UE (e.g., wireless device), according to various embodiments of the present disclosure. Figure 11 shows a flow diagram of an exemplary method (e.g., procedure) for measurement collection node, according to various embodiments of the present disclosure.

Figure 12 shows a flow diagram of an exemplary method (e.g., procedure) for a RAN node (e.g., base station), according to various embodiments of the present disclosure.

Figure 13 shows a communication system according to various embodiments of the present disclosure.

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

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

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

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

Figure 18 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.

In general, all terms used herein are to be interpreted according to their ordinary meaning to a person of ordinary skill in the relevant technical field, unless a different meaning is expressly defined and/or implied from the context of use. 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 or clearly implied from the context of use. The operations of any methods and/or procedures disclosed herein do not have to be performed in the exact order disclosed, unless an operation is explicitly described as following or preceding another operation and/or where it is implicit that an operation must follow or precede another operation. Any feature of any embodiment disclosed herein can apply to any other disclosed embodiment, as appropriate. Likewise, any advantage of any embodiment described herein can apply to any other disclosed embodiment, as appropriate.

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 3 GPP 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. • 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, IAB node) based on its specific characteristics in any given context.

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

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 and can be applied to any communication system that may benefit from them.

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 2 is a block diagram illustrating a high-level architecture for supporting UE positioning in NR networks. NG-RAN (220) can include nodes such as gNBs (e.g., 222) and ng-eNBs (e.g., 221). Each ng-eNB provides the fourth generation (4G) LTE radio interface and 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, 230) in the 5GC via respective NG-C interfaces (both of which may or may not be present), while the AMF communicates with a location management function (LMF, 240) via an NLs interface (241). The 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 UEs (e.g., 210) and NG-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 enhanced serving mobile location center (E-SMLC, 250) and a secure user plane location platform (SLP, 260) in an LTE network via communication interfaces 251 and 261, respectively. These communication interfaces can be implemented according to standardized protocols, proprietary protocols, or a combination thereof.

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

Similarly, the E-SMLC can include, or be associated with, various processing circuitry (252), by which the E-SMLC performs various operations described herein. The processing circuitry can include similar types of processing circuitry as described herein in relation to other network nodes (see, e.g., description of Figures 12 and 14). The E-SMLC can also include, or be associated with, a non-transitory computer-readable medium (253) storing instructions (also referred to as a computer program product) that can facilitate the operations of the processing circuitry. The medium can include similar types of computer memory as described herein in relation to other network nodes (see, e.g., description of Figures 12 and 14). The E-SMLC can also have communication interface circuitry that is appropriate for communicating via an interface (251), which can be similar to other interface circuitry described herein in relation to other network nodes (see, e.g., description of Figures 12 and 14).

Similarly, the SLP can include, or be associated with, various processing circuitry (262), by which the SLP performs various operations described herein. The processing circuitry can include similar types of processing circuitry as described herein in relation to other network nodes (see, e.g., description of Figures 12 and 14). The SLP can also include, or be associated with, a non-transitory computer-readable medium (263) storing instructions (also referred to as a computer program product) that can facilitate the operations of the processing circuitry. The medium can include similar types of computer memory as described herein in relation to other network nodes (see, e.g., description of Figures 12 and 14). The SLP can also have communication interface circuitry that is appropriate for communicating via an interface (261), which can be similar to other interface circuitry described herein in relation to other network nodes (see, e.g., description of Figures 12 and 14).

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 can 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, which can transmit UL reference signals, perform positioning measurements, and report these measurements to a positioning node (e.g., LMF). 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. From the positioning node’s perspective, the PRU is a UE at a known location.

An unresolved technical issue is how PRUs should be registered in a 5G network, such that other network nodes or functions are aware of their existence and capabilities. 3GPP TR 23.700-86 (v2.0.0) discusses various solutions for management of PRUs by the 5G network, including a PRU management procedure used by 5GC to obtain information about PRUs available in the 5G network. Figure 3 shows signaling diagrams for four different solutions for PRU management, which are described individually below.

In option A, a PRU (310) initiates a registration procedure towards an AMF (330) via an NG-RAN (320) serving the PRU, and includes PRU capabilities and user location information such as cell global identity (CGI) and tracking area identity (TAI). The PRU may also include its mobility state (e.g., mobile or static/fixed) in its registration, so AMF can maintain all the available PRU with related information dynamically. Subsequently, AMF invokes the Nnr NFManagement NFUpdate Request (PRU location, PRU existence indication) service operation towards an NRF (350) to indicate PRU existence in certain areas (e.g., in one or multiple TAIs). The NRF maintains this information.

In option B.1, a UE (310) provides an indication to its serving AMF whether it can function as a PRU. The serving AMF then registers the PRU-capable UE to an LMF (340). Subsequently, the LMF invokes the Nnrf NFManagement NFUpdate Request (PRU location, PRU existence indication) service operation towards the NRF to indicate PRU existence in certain areas (e.g., in one or multiple TAIs). The NRF maintains this information.

In option B.2, which is a variant of option B.1, the LMF obtains available PRU information via LPP procedures, prior to invoking the same NRF service operation as in option B.l. In option C, a UE (310) may be pre-configured as a PRU (or PRU-capable) with the PRU information included in the UE subscription data stored in the unified data management function (UDM, 360) in 5GC, e.g., as a new parameter set.

Returning to option B. l, the AMF may verify that the sender of the PRU Registration Request is a PRU, using subscription information obtained from the UDM. The AMF then selects the serving LMF based on the PRU’s current TAI and transfers the PRU Registration Request to the serving LMF using an Namj Communication N IMessageNotify service operation, including the PRU’s subscription permanent identifier (SUPI) and an indication that the PRU was verified by the AMF. The serving LMF authenticates the PRU, which can be based on the indication received from AMF or on matching the received SUPI to a corresponding SUPI stored by LMF.

All of the above-described options involve storing PRU information (including location) in the NRF. However, this violates some general policies for usage of NRF. For example, NRF is generally expected to handle static storage and is not designed to handle frequently updated information. Even if a PRU’s location is known, it may also change as the PRU (as a UE) moves around the network. This may occur frequently since there are no restrictions on PRU movement. In such case, the PRU’s information stored in NRF would need to be updated frequently, which violates policies on NRF usage.

The 3GPP study is directed to defining a 5G end-to-end Harmonized Communication and Sensing (HCS) architecture to enable sensing services, and includes the following objectives:

• Gap analysis of the existing 5GS architecture and functionalities for the support of HCS service.

• Study E2E architecture enhancements required to support new sensing service, including: o Overall HCS architecture, e.g., whether new network functions, interfaces, and/or protocols are needed; o RAN and CN functional split to support sensing service. o End-to-end (E2E) signaling interactions to support sensing service including sensing control and sensing reporting among UE, RAN, core network (CN), and application functions (AF). o Sensing service authorization and exposure. In general, sensing involves the network transmitting radio signals and receiving/measuring versions of those signals that have been reflected by the target (and possibly other surroundings). The transmitting and receiving can be performed by the same node(s) or by different node(s). Processing output of the sensing measurements yields information of the target and its surroundings that the radio signals interacted with, possibly including sources of attenuation, reflection, refraction, etc.

Figure 4 illustrates three different sensing techniques that can be used in a cellular network. In the upper left, mono-static sensing involves the same node (or antenna) transmitting the sensing signals and receiving/measuring the reflected versions. In the upper right, bi-static sensing involves a first node (or antenna) transmitting the sensing signals and a second node (or antenna) at a different location receiving/measuring the reflected versions. At the bottom, multi-static sensing involves multiple first nodes (or antennas) at different locations transmitting the sensing signals and multiple second nodes (or antennas) at other different locations receiving/measuring the reflected versions.

In any of these cases, the receiver may perform one or more of the following sensing measurements on the received sensing signals:

• Timing measurement (e.g., round-trip time, TOA, Rx-Tx time difference, etc.) of the signal (time when signal was sent + time when the reflected signal was received by the sender)

• Signal strength, signal quality, signal-to-noise ratio, etc.

• Phase measurement;

• Channel impulse response, multipath characteristics, power delay profile;

• Delay spread, Doppler spectra, Doppler spread, Doppler shift, Doppler frequency,

• Velocity, Angle of arrival, angle of departure.

These various measurements can be processed to obtain information about the target and its surroundings that affected the transmitted sensing signals, including one or more of the following:

• Characteristics (shape, size, number, etc.) of target and/or obstacles;

• Velocity of target and/or obstacles;

• Weather conditions (e.g., rain);

• Recognition of objects (e.g., wall, blocker, scatterer, etc.).

A sensing request may originate from applications external to the network. 3 GPP has defined a Sensing Management Function (SeMF) to handle these requests and to trigger the necessary sensing operations in the RAN, including any UEs that have capability to assist with the sensing. SeMF is a logical entity that resides in the RAN (e.g., gNB) or in 5GC (e.g., a NF). In general, the SeMF should be able to determine which nodes (e.g., gNBs, sensing units, UEs, etc.) should enable their sensing function for a given sensing request. If the same sensing request comes from multiple sources, the SeMF should reuse sensing information to satisfy all of these requests. The SeMF should be able to collect and aggregate measurements from multiple sensing nodes and provide them to a single processing unit.

The SeMF should also be able to configure sensing patterns for nodes (e.g., gNBs, sensing units, UEs, etc.) and collaborate with these nodes to configure or coordinate transmissions and/or receptions of the necessary sensing signals, while avoiding or minimizing interference (e.g., in case of bi- or multi-static sensing). Figure 5 shows a simplified example that illustrates how an SeMF (510) can control sensing patterns for three gNBs. The SeMF provides each gNB with a six-bit pattern, with each bit associated with a different sensing period. A value of “1” in a bit indicates the receiving gNB should activate sensing during the associated sensing period, while a value of “0” in a bit indicates that the receiving gNB should deactivate sensing during the associated sensing period.

The SeMF will need to obtain information about sensing target(s) and sensing participants associated with a request, such as accurate position, synchronization level, orientation, velocity (e.g., 6D), environment type (e.g., indoor/outdoor, stationary/moving, etc.). This information may be obtained on demand, e.g., from UE(s) in the target area, from RAN nodes, from sensing UEs, etc.). This information can be used as sensing assistance information to facilitate sensing configuration (e.g., antenna configuration, radio signal configuration, participant selection, receiver configuration, measurement configuration), performing measurements, and measurement processing.

The SeMF may need to handle prioritization and scheduling of sensing measurements and their processing. For sensing units that are actively communicating, the SeMF needs to find periods (e.g., timeslots) that can be used for sensing. Alternately, the SeMF may instruct these active sensing units to insert sensing signals (e.g., reference signals) into their transmitted communication signals, or to expect sensing signals in their received communication signals. Additionally, the SeMF may coordinate and support the synchronization mechanism for gNBs or sensing units required by bi- or multi-static sensing.

To support this functionality, the SeMF needs to be aware of which sensing-capable UEs are available in a given area. One option is to store such information in NRF in a similar manner as for PRUs, discussed above. Even so, similar problems may occur when information about sensing-capable UEs is stored in NRF, since locations of these UEs may also change frequently.

Accordingly, embodiments of the present disclosure address these and other problems, issues, and/or difficulties by providing techniques for UEs to indicate during registration with the network (e.g., AMF) whether they are stationary or mobile. The AMF verifies the UE subscription, registers the UE as a PRU, and sends to the LMF a further message for LCS registration of the UE. If the PRU is verified as stationary, the AMF includes the stationary indication in the LCS registration message to the LMF. Alternately, the AMF may include the indication regardless of whether the PRU is stationary or mobile.

Based on the presence/absence/value of this indication, the LMF determines whether to store information associated with the UE in the LMF’s NF profile in the NRF. For example, when the indication indicates that the UE is stationary, the LMF can store UE location information (e.g., serving cell ID) in the NF profile. Alternately, the LMF can store other UE location information such as neighbor cell IDs (e.g., cells where UE may perform cell reselection), tracking area indication (TAI), etc. When the indication is absent or indicates that the UE is mobile, the LMF refrains from storing UE location information in the LMF’s NF profile in NRF.

The disclosed techniques are equally applicable to sensing UEs and SeMFs, whereby the SeMF can determine whether to register a sensing UE in its NF profile in NRF based on presence/absence/value of an indication received in a message received from the AMF.

Embodiments can provide various technical benefits and/or advantages. For example, as mentioned above, embodiments may limit the storage of PRU information in LMF NF profile in NRF to only stationary PRUs. Since stationary PRUs are not moving, the PRU information in the LMF’s NF profile may be stored once without need for updates (e.g., removal and addition of PRUs). In this manner, PRUs deployed as stationary device associated with an LMF may be identified in the LMF’s NF profile, while other non-stationary PRUs are not. This storage selectivity may reduce network signaling, prevent NRF from becoming a “dynamic” database, and retain the NRF design principle of storage of network-related information (e.g., LMF- associated PRUs) rather than UE-related information that can change frequently as UEs change cells, tracking areas, etc.

As used herein, the term “assisting UE” (or “assistant UE”) refers to any UE that is capable of assisting with sensing and/or positioning operations performed in a communication network (e.g., by network nodes or functions), particularly operations in which the assisting UE is not a target (i.e., another UE or object is the target). PRUs and sensing (or sensing capable) UEs are examples of assisting UEs, with those examples being used sometimes in the following description to illustrate features applicable to all assisting UEs.

Figure 6 shows a signaling diagram according to some embodiments of the present disclosure. In particular, Figure 6 shows signaling between a PRU (610, i.e., a type of assisting UE), a RAN node (620, e.g., gNB), an AMF (630), an LMF (640), and an NRF (650). Although the operations in Figure 6 are given numerical labels, this is done to facilitate explanation rather than to require or imply any specific operational order, unless expressly stated otherwise.

As a pre-condition to the operations in Figure 6, a Routing ID of the serving LMF has been configured in the PRU or has received a Routing ID in a previous registration procedure (as described in operations 7a-b below). Note that Routing ID may also be referred to as “Correlation ID”, specifically in the context of an identifier in an NL1 service operations between an AMF and LMF. In contrast, “Routing ID” is used in the context of an identifier in a NAS message sent over the N1 reference point between PRU and AMF.

In operation 1, the PRU performs a UE Triggered Service Request if in connection management (CM) IDLE state. In operation 2, the PRU sends a supplementary services PRU Registration Request to its serving AMF in an UL Non-Access Stratum (NAS) TRANSPORT message. The PRU includes the preconfigured Routing ID for an initial Registration or the Routing ID received during a previous Registration procedure. The PRU Registration Request is included in the UL NAS TRANSPORT message as a “Location services message container” at the NAS level. The PRU Registration Request includes a reason for the Registration (e.g., initial Registration, Registration update), the PRU’s positioning capabilities, PRU location information (if known), PRU type and state including stationary/mobile status, and may include a PRU identifier (e.g., subscription permanent identifier (SUPI), permanent equipment identifier (PEI), etc.).

In operation 3, the AMF verifies that the sender of the PRU Registration Request is a PRU, based on UE subscription-related information retrieved from a unified data management function (UDM) in the 5GC. If verified, the AMF registers the sender as a PRU; otherwise, the AMF registers the sender as a normal UE. In some embodiments, the AMF also verifies the stationary/mobile status indicated by the sender based on the subscription-related information. In other embodiments, the AMF accepts the stationary/mobile status indicated by the sender without verification.

In operation 4, the AMF selects the serving LMF based on the Routing ID included in the message received in operation 2, optionally also based on the PRU’s current TAI. The AMF transfers the PRU Registration Request to the selected LMF using an Namf_Communication_NlMessageNotify service operation. If operation 3 was performed successfully, the AMF includes in the service operation an indication that the PRU was verified by the AMF. If the AMF verified that the PRU was stationary in accordance with the received indication, the AMF includes the stationary status indication in the service operation. Alternately, the AMF includes the stationary/mobile status indication, regardless of value. When included in the service operation in this manner, the indication(s) may be within or separate from the PRU Registration Request. The AMF also includes in the service operation the PRU’s SUPI, which may be obtained if not already included in the received Registration request.

In operation 5, the serving LMF authenticates the PRU. This can be based on an indication that the PRU was verified by the AMF if included operation 4, or may be based on matching the SUPI for the PRU received in operation 4 with a corresponding SUPI configured in the LMF.

In operation 6a, if the serving LMF authenticates the PRU and can accept the registration, the serving LMF returns a PRU Registration Accept to the serving AMF, as a location services supplementary services message. The LMF also includes a Correlation ID assigned by the serving LMF to identify itself and optionally the PRU. The PRU Registration Accept indicates conditions for performing PRU Registration updates with the serving LMF, e.g., periodic PRU Registration update timer, PRU Registration update trigger events such as a change of PRU location, change of PRU TAI, change of serving AMF, etc. Optionally, the PRU Registration Accept may include Routing IDs for additional serving LMFs. In operation 7a, the serving AMF forwards the PRU Registration Accept and a Routing ID corresponding (e.g., equal) to the Correlation ID to the PRU. The PRU stores the Routing ID which is used for any further PRU Registration update with the serving LMF, as mentioned above.

Alternately, if the LMF cannot authenticate the PRU and/or cannot accept registration for another reason (e.g., incorrect LMF), in operation 6b the LMF sends a PRU Registration Reject to the serving AMF and may include a Routing ID of another serving LMF. In operation 7b, the serving AMF forwards the PRU Registration Reject to the PRU.

In operation 8, assuming successful PRU Registration in operations 6a and 7a, the serving LMF may optionally verify any PRU location provided at operation 4 or obtain a more accurate location of the PRU using the positioning procedures defined in 3GPP TS 23.273 (vl 8.0.0) clause 6.11. The LMF also stores information received for the PRU.

In operation 8a, the LMF selectively stores the PRU information based on the presence/ absence/value of the stationary/mobile status indication in the message received in operation 4. For example, if the indication is present and indicates that the PRU is stationary, the LMF may decide to store the PRU information received in operation 4 in NRF and subsequently proceeds with operation 9 described below. On the other hand, if the indication is absent or present but indicates that the PRU is mobile, the LMF may refrain from storing the PRU information in NRF, and instead either discards the PRU information or stores the PRU information in the LMF’s local profile.

In some embodiments, the LMF stores the PRU information in association with a particular area. Examples of areas include tracking area ID, cell ID, neighbor cell IDs, latitude/longitude, etc. In such case, the stored PRU information can be later identified based on querying for PRUs associated with the particular area.

In operation 9, if PRU Registration is performed successfully in operations 6a-7a and if this is an initial PRU Registration or a PRU Registration update due to change in PRU location, the serving LMF may optionally instigate an Nnrf ’ NFManagement NFUpdate Request service operation towards an NRF and includes an indication of a PRU, a PRU identifier (which may be local or global), and the location of the PRU. If the PRU identifier already exists in the NF profile for the serving LMF (e.g., from a previous Registration), the NRF overwrites the old PRU location with the new PRU location. Otherwise, the NRF adds the PRU information to the NF profile information stored in the NRF for the serving LMF.

In operation 10, the NRF returns a confirmation response to the serving LMF. In operation 11, if the PRU receives Routing IDs for additional serving LMFs in operation 7a, the PRU may perform an initial PRU Registration procedure with each of the additional serving LMFs. If the PRU receives a Routing ID of a new serving LMF in operation 7b, the PRU performs an initial PRU Registration procedure with the new serving LMF.

In some cases, a PRU may be configured with a limit on the number and/or duration of unsuccessful PRU Registration attempts. When this limit is reached or if a PRU Registration is rejected in operation 7b without a new serving LMF being indicated, the PRU may send an indication to a controlling NF or application function (AF). The controlling NF or AF could then reconfigure the PRU with a different serving LMF or could indicate that the PRU is temporarily deactivated. Likewise, in some cases a PRU may be configured to limit registration with additional serving LMFs.

Although Figure 6 shows signaling for PRU registration, a similar signaling flow can be used for sensing UE (or sensing reference unit, SRU) registration, with the SeMF performing operations substantially similar to operations performed by LMF in Figure 6. The specific messages shown in Figure 6 may have the same or different names in these embodiments.

Figure 7 shows a signaling diagram of a PRU association procedure according to some embodiments of the present disclosure. In particular, Figure 7 shows signaling between a PRU (710, i.e., a type of assisting UE), a RAN node (720, e.g., gNB), an AMF (730), an LMF (740), and an NRF (750). Although the operations in Figure 7 are given numerical labels, this is done to facilitate explanation rather than to require or imply any specific operational order, unless expressly stated otherwise.

Figure 7 and its description correspond to section 6.17.1 of Appendix 1 of the priority document for the present Application. As a pre-condition to the operations in Figure 7, the PRU is currently registered in its home PLMN. For initial PRU Association, a Routing ID of the serving LMF has been configured in the PRU. For subsequent PRU Association, a Routing ID of the serving LMF has been provided to the PRUC in a previous PRU association procedure (as described in operations 6a-b below). Note that Routing ID may also be referred to as “Correlation ID”, as discussed above.

In operation 1, the PRU performs a UE Triggered Service Request if in CM-IDLE state. In operation 2, the PRU sends a supplementary services PRU Association Request to its serving AMF in an UL Non-Access Stratum (NAS) TRANSPORT message. The PRU includes the preconfigured Routing ID for an initial Association or the Routing ID received during a previous Association procedure. The PRU Association Request is included in the UL NAS TRANSPORT message at the NAS level. The PRU Association Request includes a reason for the Association (e.g., initial Association, Association update), the PRU’s positioning capabilities, PRU location information (if known), and optionally an indication of PRU stationary status.

In operation 3, the AMF verifies that the sender of the PRU Registration Request is a PRU, using subscription-related information retrieved from a UDM in the 5GC. If the AMF received an indication of PRU stationary status in operation 2, based on subscription information the AMF also verifies that the PRU can work as stationary PRU.

In operation 4, the AMF selects the serving LMF based on criteria defined in 3 GPP TS 23.273 (vl8.1.0) clause 5.1 or based on the Routing ID included in the message received in operation 2. The AMF may override the Routing ID based on criteria of 3GPP TS 23.273 (vl 8.1.0) clause 5.1. The AMF transfers the PRU Association Request to the serving LMF using an Namf_Communication_NlMessageNotify service operation. The AMF includes in the Namf_Communication_NlMessageNotify service operation an indication of whether the request corresponds to a PRU subscription, and an indication of whether the PRU is stationary. The AMF also includes the SUPI, TAI, and cell ID of the PRU

In operation 5a, if the AMF indicates in operation 4 that the request corresponds to a PRU and if the serving LMF can accept the PRU Association, the serving LMF returns a PRU Association Accept and a Correlation ID in a supplementary services message, using Namf_Communication_NlN2MessageTransfer service operation towards the AMF. The Correlation ID is assigned by the serving LMF to identify the serving LMF and optionally the PRU. The PRU Association Accept indicates conditions for performing PRU Association updates with the serving LMF, which may include a periodic PRU Association update timer and PRU Association update based on a change of PRU location, change of PRU TAI, change of serving AMF. Note that a periodic PRU Association is independent of a periodic NAS Registration and may occur with greater, equal, or lesser frequency. In operation 6a, the serving AMF forwards the PRU Association Accept and a Routing ID corresponding (e.g., equal) to the Correlation ID to the PRU in a DL NAS TRANSPORT message. The PRU stores the Routing ID which is used for any further PRU Association update with the serving LMF. This Routing ID overrides any Routing ID used in previous Association updates, if any.

Alternately, if the AMF indicates in operation 4 that the request does not correspond to a PRU subscription or if the LMF cannot accept the PRU Association for some other reason (e.g., LMF is not the correct serving LMF for PRU), in operation 5b the LMF returns a PRU Association Reject message using Namf_Communication_NlN2MessageTransfer service operation towards the AMF, and may include a Routing ID for another serving LMF if the request in operation 4 corresponds to a PRU. In operation 6b, the AMF forwards the PRU Association Reject to the PRU in a DL NAS TRANSPORT message.

In operation 7, If PRU Association was performed successfully in operations 5a and 6a, the serving LMF may optionally verify any PRU location provided in operation 4 or obtain a more accurate location of the PRU using the procedures defined in 3GPP TS 23.273 (vl8.1.0) clause 6.11. The LMF also stores information received for the PRU.

In operation 8, If PRU Association was performed successfully in operations 5a and 6a, and if this is an initial PRU Association or a PRU Association update of information for the PRU that has changed, and if PRU is stationary, the serving LMF may optionally instigate an Nnrf_NFManagement_NFUpdate Request service operation towards an NRF and include an existence indication of a PRU associated with a TAI. The LMF also indicates to the NRF to remove the TAI associated existence of PRU(s) when there are no longer any PRUs associated in the LMF for this TAI.

If requested by the serving LMF in operation 8, the NRF returns a confirmation response to the serving LMF in operation 9. In operation 11, if rejected by the AMF in operation 6b, the PRU may perform a PRU Association procedure with a new serving LMF if the rejection in operation 6b included an appropriate Routing ID.

Figure 8 shows a signaling diagram of an LMF-initiated PRU disassociation procedure according to some embodiments of the present disclosure. In particular, Figure 8 shows signaling between a PRU (810, i.e., a type of assisting UE), a RAN node (820, e.g., gNB), an AMF (830), an LMF (840), and an NRF (850). Although the operations in Figure 8 are given numerical labels, this is done to facilitate explanation rather than to require or imply any specific operational order, unless expressly stated otherwise.

Figure 8 and its description correspond to section 6.17.2 of Appendix 1 of the priority document for the present Application. As a pre-condition to the operations in Figure 8, the PRU has previously associated with the serving LMF using the procedure shown in Figure 7 and/or specified in 3GPP TS 23.273 (vl8.1.0) clause 6.17.1.

In operation 1, the serving LMF sends the AMF a PRU Disassociation Request and a Correlation ID identifying the serving LMF in a supplementary services message, using the Namf_Communication_NlN2MessageTransfer service operation. The PRU Disassociation Request may include a Routing ID for a new serving LMF for the PRU. Note that the Correlation ID for the serving LMF is transferred to the serving AMF to provide the Routing ID for operation 3. The Routing ID for a new serving LMF, if provided, is included inside the PRU Disassociation Request and is not visible to the serving AMF. This Routing ID is different from the Routing ID used in operation 3-5 and enables the PRU to perform an Association with a new serving LMF in operation 8, as described below.

In operation 2, if the PRU is in CM IDLE state, the serving AMF performs a Network Triggered service request to place the PRU in CM CONNECTED state. In operation 3, the serving AMF forwards the PRU Disassociation Request and a Routing ID equal to the Correlation ID to the PRU using DL NAS TRANSPORT message.

In operation 4, the PRU returns a supplementary services PRU Disassociation Accept to the serving AMF in an UL NAS TRANSPORT message and includes the Routing ID received in operation 3. In operation 5, the serving AMF forwards the PRU Disassociation Accept to the serving LMF indicated by the Routing ID received at step 4 and includes a Correlation ID equal to the Routing ID.

In operation 6, if the serving LMF has indicated the PRU to an NRF during PRU Association and if the serving LMF does not have any other PRU associated to the TAI, the serving LMF uses an Nnrf_NFManagement_NFUpdate Request service operation towards the NRF to request an indication of PRU removal. The NRF then removes the TAI associated PRU existence indication and in operation 7 returns a confirmation response to the serving LMF.

In operation 8, if the PRU received a new Routing ID for a new serving LMF at operation 3, the PRU may perform a PRU Association with the new serving LMF using the procedure shown in Figure 7 and/or specified in 3GPP TS 23.273 (vl8.1.0) clause 6.17.1.

Figure 9 shows a signaling diagram of a PRU-initiated PRU disassociation procedure according to some embodiments of the present disclosure. In particular, Figure 9 shows signaling between a PRU (910, i.e., a type of assisting UE), a RAN node (920, e.g., gNB), an AMF (930), an LMF (940), and an NRF (950). Although the operations in Figure 9 are given numerical labels, this is done to facilitate explanation rather than to require or imply any specific operational order, unless expressly stated otherwise.

Figure 9 and its description correspond to section 6.17.3 of Appendix 1 of the priority document for the present Application. As a pre-condition to the operations in Figure 9, the PRU has previously associated with the serving LMF using the procedure shown in Figure 7 and/or specified in 3GPP TS 23.273 (vl8.1.0) clause 6.17.1, and is currently registered in its HPLMN.

In operation 1, the PRU performs a UE Triggered Service Request if in CM IDLE state. In operation 2, the PRU sends a supplementary services PRU Disassociation Request to the serving AMF in an UL NAS TRANSPORT message and includes the Routing ID received at operation 6a of the procedure shown in Figure 7 and/or specified in 3GPP TS 23.273 (vl8.1.0) clause 6.17.1, i.e., for a previous PRU Association procedure. The PRU also indicates whether an acknowledgment is expected. The PRU Disassociation Request is included in the UL NAS TRANSPORT message at the NAS level. Note that a PRU could indicate whether an acknowledgment is expected according to whether the PRU expects to be still able to receive the acknowledgment at a later time.

In operation 3, the AMF verifies whether the sender of the PRU Disassociation Request is a PRU using subscription information from the UDM. In operation 4, the AMF selects the serving LMF based on the Routing ID and optionally the current TAI and transfers the PRU Disassociation Request to the serving LMF using an Namf_Communication_NlMessageNotify service operation. The AMF includes in the Namf_Communication_NlMessageNotify service operation an indication of whether the sender of the PRU Disassociation Request is a PRU. The AMF also includes the SUPI of the PRU.

In operation 5, the serving LMF verifies that the PRU is currently associated in the serving LMF. If the PRU is not currently associated in the serving LMF, the serving LMF performs operations 6-7 but otherwise performs operations 8-9. Note that inconsistency between Association in a PRU versus a serving LMF might arise if a PRU is powered off or loses network coverage and if the serving LMF then performs an LMF initiated PRU Disassociation.

In operation 6, if the PRU has indicated that an acknowledgment is expected, the serving LMF returns a PRU Disassociation Accept, as a supplementary services message, using an Namf_Communication_NlN2MessageTransfer service operation towards the AMF, and a Correlation ID. In operation 7, the serving AMF forwards the PRU Disassociation Accept and a Routing ID equal to the Correlation ID to the PRU in a DL NAS TRANSPORT message.

In operation 8, if the serving LMF has indicated the PRU to an NRF during a previous PRU Association and if serving LMF does not have any other PRU associated to the TAI, the serving LMF invokes an Nnrf_NFManagement_NFUpdate Request service operation towards the NRF and requests an indication of PRU removal. The NRF then removes the TAI associated PRU existence indication and in operation 9 returns a confirmation response to the serving LMF.

Various features of the embodiments described above correspond to various operations illustrated inFigures 10-12, which show exemplary methods e.g., procedures) for aUE, anetwork function (NF), and an AMF, respectively. In other words, various features of the operations described below correspond to various embodiments described above. Furthermore, the exemplary methods shown in Figures 10-12 can be used cooperatively to provide various benefits, advantages, and/or solutions to problems described herein. Although Figures 10-12 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 10 shows an exemplary method (e.g., procedure) for a UE configured to assist with positioning and/or sensing operations in a communication network, according to various embodiments of the present disclosure. The exemplary method can be performed by a UE (e.g., wireless device, etc.) such as described elsewhere herein.

The exemplary method includes the operations of block 1010, where the UE sends, to an access and mobility management function (AMF) of the communication network, an association request that includes a first indication that the UE is configured to operate as an assisting UE. The exemplary method also includes the operations of block 1020, where the UE receives from the AMF a response indicating whether the association request was accepted or rejected by a NF configured to manage positioning and/or sensing operations in the communication network.

In addition, Figure 11 shows an exemplary method (e.g., procedure) for a network function (NF) configured to manage positioning and/or sensing operations in a communication network, according to various embodiments of the present disclosure. The exemplary method can be performed by an LMF, an SeMF, or similar node or function, as described elsewhere herein.

The exemplary method includes the operations of block 1110, where the NF receives, from an AMF of the communication network, an association request for a UE. The association request includes or is received with the following: a first indication that the UE is configured to operate as an assisting UE, and a second indication of whether the UE is stationary or mobile. The exemplary method also includes the operations of block 1130, where the NF sends to the AMF an association response indicating whether the NF accepted the association request for the UE. The exemplary method also includes the operations of block 1140, where when the NF accepts the association request, the NF selectively stores, based on the second indication, information about the UE’s operation as an assisting UE.

In some embodiments, the association request includes the second indication only when the second indication indicates that the UE is stationary, and absence of the second indication from the association request indicates that the UE is mobile.

In some embodiments, selectively storing the information based on the second indication in block 1140 includes the following operations, labelled with corresponding sub-block numbers:

• (1141) when the second indication indicates that the UE is stationary, storing the information in a network repository function (NRF) of the communication network; and

• (1142) when the second indication indicates that the UE is mobile, performing one of the following: discarding the information, or storing the information locally at the NF.

In some embodiments, the association request also includes one or more of the following information: a reason for the association, a third indication of the UE’s positioning and/or sensing capabilities, UE location information, and a second identifier associated with a user subscription to the communication network (e.g., SUPI). For example, any of the above information can be selectively stored in block 1140.

In some of these embodiments, the exemplary method also includes the operations of block 1120, where the NF determines whether to accept the association request based on authentication of the UE and on a determination of whether the NF is a proper serving NF for the UE. In some variants of these embodiments, authentication of the UE is based on one of the following:

• a match or relation between the second identifier and a corresponding identifier configured in the NF (e.g., SUPI); or • a further indication received with the association request, indicating that the AMF verified the first indication.

In some embodiments, the association response includes one of the following:

In some embodiments, the UE is a PRU and the NF is an LMF in a 5GC. In other embodiments, the UE is a sensing UE and the NF is an SeMF in a 5GC.

In addition, Figure 12 shows an exemplary method (e.g., procedure) for an access and mobility management function (AMF) of a communication network, according to various embodiments of the present disclosure. The exemplary method can be performed by an AMF such as described elsewhere herein.

The exemplary method includes the operations of block 1210, where the AMF receives from a UE an association request that includes a first indication that the UE is configured to operate as an assisting UE. The exemplary method also includes the operations of block 1230, where the AMF verifies the first indication (i.e., that the UE is an assisting UE) based on subscription information for the UE. The exemplary method also includes the operations of block 1260, where based on verifying the first indication, the AMF sends a further association request for the UE to a NF configured to manage positioning and/or sensing operations in the communication network. The further association request includes or is sent together with the following: a first indication that the UE is configured to operate as an assisting UE, and a second indication of whether the UE is stationary or mobile.

In some of these embodiments, the exemplary method also includes the operations of block 1220, where using the first identifier or the second identifier, the AMF retrieves the subscription information for the UE from a unified data management function (UDM) of the communication network. Also, verifying the first indication in block 1230 is based on the retrieved subscription information.

In some of these embodiments, the exemplary method also includes the operations of block 1240, where the AMF determines whether the UE is stationary or mobile based on one or more of the following: the subscription information for the UE; and the further indication of whether the UE is stationary or mobile, when included in the association request. In some variants of these embodiments, the first identifier is a permanent equipment identifier (PEI), the second identifier is a subscription permanent identifier (SUPI), the SUPI is included in the forwarded association request, and one of the following applies:

• the PEI is included in the received association request and used to retrieve the subscription information, which includes the SUPI; or

• the SUPI is also included in the received association and used to retrieve the subscription information.

In some embodiments, the exemplary method also includes the operations of blocks 1270- 1280, where the AMF receives from the NF an association response indicating whether the NF accepted the further association request for the UE and forwards the association response to the UE. In some of these embodiments, the association request is received together with a routing identifier and the exemplary method also includes the operations of block 1250, where the AMF selects the NF based on one or more of the following: the routing identifier, and a tracking area associated with the UE. In some variants of these embodiments, the association response includes one of the following:

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 13 shows an example of a communication system 1300 in accordance with some embodiments. In this example, communication system 1300 includes a telecommunication network 1302 that includes an access network 1304 (e.g., RAN) and a core network 1306, which includes one or more core network nodes 1308. Access network 1304 includes one or more access network nodes, such as network nodes 13 lOa-b (one or more of which may be generally referred to as network nodes 1310), or any other similar 3GPP access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, telecommunication network 1302 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in telecommunication network 1302 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in telecommunication network 1302, including one or more network nodes 1310 and/or core network nodes 1308.

Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU- CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. Network nodes 1310 facilitate direct or indirect connection of UEs, such as by connecting UEs 1312a-d (one or more of which may be generally referred to as UEs 1312) to core network 1306 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 1300 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 1300 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

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

In the depicted example, core network 1306 connects network nodes 1310 to one or more hosts, such as host 1316. 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. Core network 1306 includes one or more core network nodes (e.g., 1308) 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 core network node 1308. 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 1316 may be under the ownership or control of a service provider other than an operator or provider of access network 1304 and/or telecommunication network 1302, and may be operated by the service provider or on behalf of the service provider. Host 1316 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 1300 of Figure 13 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 1302 is a cellular network that implements 3 GPP standardized features. Accordingly, telecommunication network 1302 may support network slicing to provide different logical networks to different devices that are connected to telecommunication network 1302. For example, telecommunication network 1302 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, UEs 1312 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to access network 1304 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from access network 1304. 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 1314 communicates with access network 1304 to facilitate indirect communication between one or more UEs (e.g., UE 1312c and/or 1312d) and network nodes (e.g., network node 1310b). In some examples, hub 1314 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, hub 1314 may be a broadband router enabling access to core network 1306 for the UEs. As another example, hub 1314 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 1310, or by executable code, script, process, or other instructions in hub 1314. As another example, hub 1314 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 1314 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, hub 1314 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which hub 1314 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, hub 1314 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

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

In some embodiments, core network node 1308 can be configured to perform operations attributed to an LMF, SeMF, and/or AMF in the above descriptions of the exemplary procedures shown in Figures 10-12. As a specific example, core network node 1308 can implement an AMF, an LMF, or an SeMF configured to perform such operations. In some embodiments, any of UEs 1312a-d can be configured to perform operations attributed to a UE in the above descriptions of the exemplary procedures shown in Figures 10-12.

Figure 14 shows a UE 1400 in accordance with some embodiments. 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, vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by 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 1400 includes processing circuitry 1402 that is operatively coupled via a bus 1404 to an input/output interface 1406, a power source 1408, a memory 1410, a communication interface 1412, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 14. 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.

Processing circuitry 1402 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 memory 1410. Processing circuitry 1402 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, processing circuitry 1402 may include multiple central processing units (CPUs).

In the example, input/output interface 1406 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 1400. 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, power source 1408 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. Power source 1408 may further include power circuitry for delivering power from power source 1408 itself, and/or an external power source, to the various parts of UE 1400 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of power source 1408. Power circuitry may perform any formatting, converting, or other modification to the power from power source 1408 to make the power suitable for the respective components of UE 1400 to which power is supplied.

Memory 1410 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, memory 1410 includes one or more application programs 1414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1416. Memory 1410 may store, for use by UE 1400, any of a variety of various operating systems or combinations of operating systems.

Memory 1410 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.’ Memory 1410 may allow UE 1400 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 memory 1410, which may be or comprise a device-readable storage medium.

Processing circuitry 1402 may be configured to communicate with an access network or other network using communication interface 1412. Communication interface 1412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1422. Communication interface 1412 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 1418 and/or a receiver 1420 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, transmitter 1418 and receiver 1420 may be coupled to one or more antennas (e.g., antenna 1422) and may share circuit components, software, or firmware, or alternatively be implemented separately.

In the illustrated embodiment, communication functions of communication interface 1412 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 1412, 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., when moisture is detected an alert is sent), 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 1400 shown in Figure 14.

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.

In some embodiments, UE 1400 can be configured to perform operations attributed to a UE in the above descriptions of the exemplary procedures shown in Figures 10-12.

Figure 15 shows a network node 1500 in accordance with some embodiments. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (e.g., radio base stations, Node Bs, eNBs, gNBs), and 0-RAN nodes or components of an 0-RAN node (e g., 0-RU, 0-DU, O-CU).

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, distributed units (e.g., in an O-RAN access node) 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).

Network node 1500 includes processing circuitry 1502, memory 1504, communication interface 1506, and power source 1508. Network node 1500 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 network node 1500 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, network node 1500 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1504 for different RATs) and some components may be reused (e.g., a same antenna 1510 may be shared by different RATs). Network node 1500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1500, 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 1500.

Processing circuitry 1502 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 1500 components, such as memory 1504, to provide network node 1500 functionality.

In some embodiments, processing circuitry 1502 includes a system on a chip (SOC). In some embodiments, processing circuitry 1502 includes one or more of radio frequency (RF) transceiver circuitry 1512 and baseband processing circuitry 1514. In some embodiments, RF transceiver circuitry 1512 and baseband processing circuitry 1514 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 1512 and baseband processing circuitry 1514 may be on the same chip or set of chips, boards, or units.

Memory 1504 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 1502. Memory 1504 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 (collected denoted computer program 1504a, which may be in the form of a computer program product) capable of being executed by processing circuitry 1502 and utilized by network node 1500. Memory 1504 may be used to store any calculations made by processing circuitry 1502 and/or any data received via communication interface 1506. In some embodiments, processing circuitry 1502 and memory 1504 is integrated.

Communication interface 1506 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, communication interface 1506 comprises port(s)/terminal(s) 1516 to send and receive data, for example to and from a network over a wired connection. Communication interface 1506 also includes radio frontend circuitry 1518 that may be coupled to, or in certain embodiments a part of, antenna 1510. Radio front-end circuitry 1518 comprises filters 1520 and amplifiers 1522. Radio front-end circuitry 1518 may be connected to an antenna 1510 and processing circuitry 1502. The radio front-end circuitry may be configured to condition signals communicated between antenna 1510 and processing circuitry 1502. Radio front-end circuitry 1518 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. Radio front-end circuitry 1518 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1520 and/or amplifiers 1522. The radio signal may then be transmitted via antenna 1510. Similarly, when receiving data, antenna 1510 may collect radio signals which are then converted into digital data by radio front-end circuitry 1518. The digital data may be passed to processing circuitry 1502. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 1500 does not include separate radio front-end circuitry 1518, instead, processing circuitry 1502 includes radio front-end circuitry and is connected to antenna 1510. Similarly, in some embodiments, all or some of RF transceiver circuitry 1512 is part of communication interface 1506. In still other embodiments, communication interface 1506 includes one or more ports or terminals 1516, radio front-end circuitry 1518, and RF transceiver circuitry 1512, as part of a radio unit (not shown), and communication interface 1506 communicates with baseband processing circuitry 1514, which is part of a digital unit (not shown).

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

Antenna 1510, communication interface 1506, and/or processing circuitry 1502 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, antenna 1510, communication interface 1506, and/or processing circuitry 1502 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.

Power source 1508 provides power to the various components of network node 1500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1508 may further comprise, or be coupled to, power management circuitry to supply the components of network node 1500 with power for performing the functionality described herein. For example, network node 1500 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 power source 1508. As a further example, power source 1508 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 network node 1500 may include additional components beyond those shown in Figure 15 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, network node 1500 may include user interface equipment to allow input of information into network node 1500 and to allow output of information from network node 1500. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1500.

In various embodiments, one or more network nodes 1500 can be configured to perform operations attributed to an LMF, SeMF, and/or AMF in the above descriptions of the exemplary procedures shown in Figures 7-9. As a specific example, a network node 1500 can implement an AMF, an LMF, or an SeMF configured to perform such operations.

Figure 16 is a block diagram of a host 1600, which may be an embodiment of host 1316 of Figure 13, in accordance with various aspects described herein. As used herein, host 1600 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. Host 1600 may provide one or more services to one or more UEs.

Host 1600 includes processing circuitry 1602 that is operatively coupled via a bus 1604 to an input/output interface 1606, a network interface 1608, a power source 1610, and a memory 1612. 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 14 and 15, such that the descriptions thereof are generally applicable to the corresponding components of host 1600.

Memory 1612 may include one or more computer programs including one or more host application programs 1614 and data 1616, which may include user data, e.g., data generated by a UE for host 1600 or data generated by host 1600 for a UE. Embodiments of host 1600 may utilize only a subset or all of the components shown. Host application programs 1614 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). Host application programs 1614 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, host 1600 may select and/or indicate a different host for over-the-top services for a UE. Host application programs 1614 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 17 is a block diagram illustrating a virtualization environment 1700 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 1700 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. In some embodiments, the virtualization environment 1700 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

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

In various embodiments, one or more virtual nodes 1702 can be configured operations to perform operations attributed to an LMF, SeMF, and/or AMF in the above descriptions of the exemplary procedures shown in Figures 10-12. As a specific example, a virtual node 1702 can implement an AMF, an LMF, or an SeMF configured to perform such operations.

Hardware 1704 includes processing circuitry, memory that stores software and/or instructions (collected denoted computer program 1704a, which may be in the form of a computer program product) 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 1706 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1708a-b (one or more of which may be generally referred to as VMs 1708), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. Virtualization layer 1706 may present a virtual operating platform that appears like networking hardware to the VMs 1708. VMs 1708 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1706. Different embodiments of the instance of a virtual appliance 1702 may be implemented on one or more of VMs 1708, 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, each VM 1708 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each VM 1708, and that part of hardware 1704 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 1708 on top of the hardware 1704 and corresponds to the application 1702.

Hardware 1704 may be implemented in a standalone network node with generic or specific components. Hardware 1704 may implement some functions via virtualization. Alternatively, hardware 1704 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 function 1710, which, among others, oversees lifecycle management of applications 1702. In some embodiments, hardware 1704 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 1712 which may alternatively be used for communication between hardware nodes and radio units.

Figure 18 shows a communication diagram of a host 1802 communicating via a network node 1804 with a UE 1806 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1312a of Figure 13 and/or UE 1400 of Figure 14), network node (such as network node 1310a of Figure 13 and/or network node 1500 of Figure 15), and host (such as host 1316 of Figure 13 and/or host 1600 of Figure 16) discussed in the preceding paragraphs will now be described with reference to Figure 18. Like host 1600, embodiments of host 1802 include hardware, such as a communication interface, processing circuitry, and memory. Host 1802 also includes software, which is stored in or accessible by host 1802 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 1806 connecting via an over-the-top (OTT) connection 1850 extending between UE 1806 and host 1802. In providing the service to the remote user, a host application may provide user data which is transmitted using OTT connection 1850.

Network node 1804 includes hardware enabling it to communicate with host 1802 and UE 1806. Connection 1860 may be direct or pass through a core network (like core network 1306 of Figure 13) 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 1806 includes hardware and software, which is stored in or accessible by UE 1806 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 1806 with the support of host 1802. In host 1802, an executing host application may communicate with the executing client application via OTT connection 1850 terminating at UE 1806 and host 1802. 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 1850 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 1850.

OTT connection 1850 may extend via a connection 1860 between host 1802 and network node 1804 and via a wireless connection 1870 between network node 1804 and UE 1806 to provide the connection between host 1802 and UE 1806. Connection 1860 and wireless connection 1870, over which OTT connection 1850 may be provided, have been drawn abstractly to illustrate the communication between host 1802 and UE 1806 via network node 1804, 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 1850, in step 1808, host 1802 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 1806. In other embodiments, the user data is associated with a UE 1806 that shares data with host 1802 without explicit human interaction. In step 1810, host 1802 initiates a transmission carrying the user data towards UE 1806. Host 1802 may initiate the transmission responsive to a request transmitted by UE 1806. The request may be caused by human interaction with UE 1806 or by operation of the client application executing on UE 1806. The transmission may pass via network node 1804, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1812, network node 1804 transmits to UE 1806 the user data that was carried in the transmission that host 1802 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1814, UE 1806 receives the user data carried in the transmission, which may be performed by a client application executed on UE 1806 associated with the host application executed by host 1802.

In some examples, UE 1806 executes a client application which provides user data to host 1802. The user data may be provided in reaction or response to the data received from host 1802. Accordingly, in step 1816, UE 1806 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 1806. Regardless of the specific manner in which the user data was provided, UE 1806 initiates, in step 1818, transmission of the user data towards host 1802 via network node 1804. In step 1820, in accordance with the teachings of the embodiments described throughout this disclosure, network node 1804 receives user data from UE 1806 and initiates transmission of the received user data towards host 1802. In step 1822, host 1802 receives the user data carried in the transmission initiated by UE 1806.

One or more of the various embodiments improve the performance of OTT services provided to UE 1806 using OTT connection 1850, in which wireless connection 1870 forms the last segment. More precisely, the teachings of these embodiments can limit the storage of PRU information in LMF NF profile in NRF to cases where the PRU is stationary. Since stationary PRUs are not moving, the PRU information in the LMF’s NF profile can be stored once without need for updates (e.g., removal and addition of PRUs). In this manner, PRUs deployed as fixed device associated with an LMF can be identified in the LMF’s NF profile, while other non- stationary PRUs are not. This selectivity reduces network signaling, prevents NRF from becoming a “dynamic” database, and retains the NRF design principle of storage of network-related information (e.g., LMF-associated PRUs) rather than UE-related information that can change frequently as UEs change cells, tracking areas, etc. When delivered via networks improved in this manner, OTT services become more valuable to both end users and service providers.

In an example scenario, factory status information may be collected and analyzed by host 1802. As another example, host 1802 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, host 1802 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, host 1802 may store surveillance video uploaded by a UE. As another example, host 1802 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 1802 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 1850 between host 1802 and UE 1806, 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 1802 and/or UE 1806. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which OTT connection 1850 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 1850 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of network node 1804. 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 1802. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 1850 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 to 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 user equipment (UE) configured to assist with positioning and/or sensing operations in a communication network, the method comprising: sending, to an access and mobility management function (AMF) of the communication network, a registration request that includes the following: a first indication that the UE is configured to operate as an assisting UE, and a second indication of whether the UE is stationary or mobile; and receiving, from the AMF, a response indicating whether the registration request was accepted or rejected by a network node or function (NNF) configured to manage positioning and/or sensing operations in the communication network.

A2. The method of embodiment Al, wherein the registration request also includes one or more of the following: a reason for the registration, a third indication of the UE’s positioning and/or sensing capabilities, UE location information, a first identifier associated with the UE, and a second identifier associated with a user subscription to the communication network.

A3. The method of any of embodiments A1-A2, wherein: the registration request is sent together with a routing identifier associated with the NNF; and the registration response includes one of the following: a correlation identifier associated with the NNF, when the registration response indicates that the NNF accepted the registration request; or a second routing identifier associated with a different NNF, when the registration response indicates that the NNF rejected the registration request.

A4. The method of any of embodiments A1-A3, wherein one of the following applies: the UE is a positioning reference unit (PRU) and the NNF is a location management function (LMF) in a 5G core network (5GC); and the UE is a sensing UE and the NNF is a sensing management function (SeMF) in a 5GC. Bl. A method for a network node or function (NNF) configured to manage positioning and/or sensing operations in a communication network, the method comprising: receiving, from an access and mobility management function (AMF) of the communication network, a registration request by a user equipment (UE), wherein the registration request includes the following information: a first indication that the UE is configured to operate as an assisting UE, and a second indication of whether the UE is stationary or mobile; and sending to the AMF a registration response indicating whether the NNF accepted the registration request by the UE; and when the NNF accepts the registration request, selectively storing, based on the second indication, information about the UE’s operation as an assisting UE.

B2. The method of embodiment Bl, wherein the registration request includes the second indication only when the second indication indicates that the UE is stationary, and absence of the second indication from the registration request indicates that the UE is mobile.

B3. The method of any of embodiments B1-B2, wherein selectively storing the information based on the second indication comprises: when the second indication indicates that the UE is stationary, storing the information in a network repository function (NRF) of the communication network; and when the second indication indicates that the UE is mobile, performing one of the following: discarding the information, or storing the information locally in the NNF.

B4. The method of any of embodiments B1-B3, wherein the selectively stored information includes an association between the UE and one or more of the following: a tracking area, a serving cell, one or more neighbor cells, and geographic coordinates.

B5. The method of any of embodiments B1-B4, wherein at least a portion of the selectively stored information is included in the registration request.

B6. The method of any of embodiments B1-B5, wherein the registration request also includes one or more of the following information: a reason for the registration, a third indication of the UE’s positioning and/or sensing capabilities, UE location information, and a second identifier associated with a user subscription to the communication network. B7. The method of embodiment B6, further comprising determining whether to accept the registration request based on authentication of the UE and on a determination of whether the NNF is a proper serving NNF for the UE.

B8. The method of embodiment B7, wherein authentication of the UE is based on one of the following: a match or relation between the second identifier and a corresponding identifier configured in the NF; or a further indication received with the registration request, indicating that the AMF verified the first indication.

B9. The method of any of embodiments B1-B8, wherein the registration response includes one of the following: a correlation identifier associated with the NNF, when the registration response indicates that the NF accepted the registration request; or a second routing identifier associated with a different NNF, when the registration response indicated that the NF rejected the registration request.

BIO. The method of any of embodiments B1-B9, wherein one of the following applies: the UE is a positioning reference unit (PRU) and the NNF is a location management function (LMF) in a 5G core network (5GC); and the UE is a sensing UE and the NNF is a sensing management function (SeMF) in a 5GC.

Cl . A method for an access and mobility management function (AMF) of a communication network, the method comprising: receiving, from a user equipment (UE), a registration request that includes the following: a first indication that the UE is configured to operate as an assisting UE, and a second indication of whether the UE is stationary or mobile; and based on verifying the first indication, registering the UE as an assisting UE; and forwarding the registration request to a network node or function (NNF) configured to manage positioning and/or sensing operations in the communication network. C2. The method of embodiment Cl, wherein the registration request forwarded to the NNF includes the second indication only when the second indication indicates that the UE is stationary, and absence of the second indication from the forwarded registration request indicates that the UE is mobile.

C3. The method of any of embodiments C1-C2, wherein the registration request also includes one or more of the following: a reason for the registration, a third indication of the UE’s positioning and/or sensing capabilities, UE location information, a first identifier associated with the UE, and a second identifier associated with a user subscription to the communication network.

C4. The method of embodiment C3, wherein: the method further comprises, using the first identifier or the second identifier, retrieving UE subscription information from a unified data management function (UDM) of the communication network; and verifying the first indication is based on the UE subscription information.

C5. The method of embodiment C4, further comprising verifying the second indication based on the UE subscription information.

C6. The method of embodiment C5, wherein the first identifier is a permanent equipment identifier (PEI), the second identifier is a subscription permanent identifier (SUPI), the SUPI is included in the forwarded registration request, and one of the following applies: the PEI is included in the received registration request and used to retrieve the subscription information, which includes the SUPI; or the SUPI is also included in the received registration and used to retrieve the subscription information.

C7. The method of any of embodiments C1-C6, further comprising: receiving, from the NNF, a registration response indicating whether the NNF accepted the registration request by the UE; and forwarding the registration response to the UE. C8. The method of embodiment C7, wherein the registration request is received together with a routing identifier, and the method further comprises selecting the NNF based on one or more of the following: the routing identifier, and a tracking area associated with the UE.

C9. The method of embodiment C8, wherein the registration response includes one of the following: a correlation identifier associated with the NNF, when the registration response indicates that the NNF accepted the registration request; or a second routing identifier associated with a different NNF, when the registration response indicates that the NNF rejected the registration request.

CIO. The method of any of embodiments C1-C9, wherein the registration request is forwarded together with a further indication that the AMF verified the first indication.

Cl 1. The method of any of embodiments C1-C10, wherein one of the following applies: the UE is a positioning reference unit (PRU) and the NNF is a location management function (LMF) in a 5G core network (5GC); and the UE is a sensing UE and the NNF is a sensing management function (SeMF) in a 5GC.

DI . A user equipment (UE) configured to assist with positioning and/or sensing operations in a communication network, the UE 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 A1-A4.

D2. A user equipment (UE) configured to assist with positioning and/or sensing operations in a communication network, the UE being further configured to perform operations corresponding to any of the methods of embodiments A1-A4.

D3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured to assist with positioning and/or sensing operations in a communication network, configure the UE to perform operations corresponding to any of the methods of embodiments A1-A4.

D4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured to assist with positioning and/or sensing operations in a communication network, configure the UE to perform operations corresponding to any of the methods of embodiments A1-A4.

El . A network node or function (NNF) configured to manage positioning and/or sensing operations in a communication network, the NNF comprising: communication interface circuitry configured to communicate with other NNFs 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 Bl -BIO.

E2. A network node or function (NNF) configured to manage positioning and/or sensing operations in a communication network, the NNF being further configured to perform operations corresponding to any of the methods of embodiments Bl -BIO.

E3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a network node or function (NNF) configured to manage positioning and/or sensing operations in a communication network, configure the NNF to perform operations corresponding to any of the methods of embodiments Bl -BIO.

E4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a network node or function (NNF) configured to manage positioning and/or sensing operations in a communication network, configure the NNF to perform operations corresponding to any of the methods of embodiments Bl -BIO.

Fl. An access and mobility management function (AMF) of a communication network, the AMF comprising: communication interface circuitry configured to communicate with user equipment (UEs) and with other network nodes or functions (NNFs) 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 C 1 -C 11.

F2. An access and mobility management function (AMF) of a communication network, the AMF being configured to perform operations corresponding to any of the methods of embodiments C 1 -C 11.

F3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of an access and mobility management function (AMF) of a communication network, configure the RAN node to perform operations corresponding to any of the methods of embodiments Cl-Cl 1.

F4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of an access and mobility management function (AMF) of a communication network, configure the RAN node to perform operations corresponding to any of the methods of embodiments Cl-Cl 1.

Claims

1. A method for a network function, NF, configured to manage positioning and/or sensing operations in a communication network, the method comprising: receiving (1110), from an access and mobility management function, AMF, of the communication network, an association request for a user equipment, UE, wherein the association request includes or is received with the following: a first indication that the UE is configured to operate as an assisting UE, and a second indication of whether the UE is stationary or mobile; and sending (1130) to the AMF an association response indicating whether the NF accepted the association request for the UE; and when the NF accepts the association request, selectively storing (1040), based on the second indication, information about the UE’s operation as an assisting UE.

2. The method of claim 1, wherein the association request includes or is received with the second indication only when the second indication indicates that the UE is stationary, and absence of the second indication in or with the association request indicates that the UE is mobile.

3. The method of any of claims 1-2, wherein selectively storing (1140) the information based on the second indication comprises: when the second indication indicates that the UE is stationary, storing (1141) the information in a network repository function, NRE, of the communication network; and when the second indication indicates that the UE is mobile, performing (1142) one of the following: discarding the information, or storing the information locally at the NF.

4. The method of any of claims 1-3, wherein the selectively stored information includes an association between the UE and one or more of the following: a tracking area, a serving cell, one or more neighbor cells, and geographic coordinates.

5. The method of any of claims 1-4, wherein at least a portion of the selectively stored information is included in the association request.

6. The method of any of claims 1-5, wherein the association request also includes one or more of the following information: a reason for the association, a third indication of the UE’s positioning and/or sensing capabilities, UE location information, and a second identifier associated with a user subscription to the communication network.

7. The method of claim 6, further comprising determining (1120) whether to accept the association request based on authentication of the UE and on a determination of whether the NF is a proper serving NF for the UE.

8. The method of claim 7, wherein authentication of the UE is based on one of the following: a match or relation between the second identifier and a corresponding identifier configured in the NF; or a further indication received with the association request, indicating that the AMF verified the first indication.

9. The method of any of claims 1-8, wherein the association response includes one of the following: a correlation identifier associated with the NF, when the association response indicates that the NF accepted the association request; or a second routing identifier associated with a different NF, when the association response indicated that the NF rejected the association request.

10. The method of any of claims 1-9, wherein one of the following applies: the UE is a positioning reference unit, PRU, and the NF is a location management function, LMF, in a 5G core network, 5GC; and the UE is a sensing UE and the NF is a sensing management function, SeMF, in a 5GC.

11. A method for an access and mobility management function, AMF, of a communication network, the method comprising: receiving (1210), from a user equipment, UE, an association request that includes a first indication that the UE is configured to operate as an assisting UE; verifying (1230) the first indication based on subscription information for the UE; and based on verifying (1230) the first indication, sending (1260) a further association request for the UE to a network function, NF, configured to manage positioning and/or sensing operations in the communication network, wherein the further association request includes or is sent together with the following: a first indication that the UE is configured to operate as an assisting UE, and a second indication of whether the UE is stationary or mobile.

12. The method of claim 11, wherein the further association request includes or is sent with the second indication only when the second indication indicates that the UE is stationary, and absence of the second indication in or with the further association request indicates that the UE is mobile.

13. The method of any of claims 11-12, wherein the association request also includes one or more of the following: a reason for the association, a further indication of whether the UE is stationary or mobile, a third indication of the UE’s positioning and/or sensing capabilities,

UE location information, a first identifier associated with the UE, and a second identifier associated with a user subscription to the communication network.

14. The method of claim 13, wherein: the method further comprises, using the first identifier or the second identifier, retrieving (1220) the subscription information for the UE from a unified data management function, UDM, of the communication network; and verifying the first indication is based on the retrieved subscription information.

15. The method of any of claims 13-14, further comprising determining (1240) whether the UE is stationary or mobile based on one or more of the following: the subscription information for the UE, and the further indication of whether the UE is stationary or mobile, when included in the association request.

16. The method of claim 15, wherein the first identifier is a permanent equipment identifier, PEI; the second identifier is a subscription permanent identifier, SUPI; the SUPI is included in the further association request; and one of the following applies: the PEI is included in the association request and used to retrieve the subscription information, which includes the SUPI; or the SUPI is also included in the association and used to retrieve the subscription information.

17. The method of any of claims 11-16, further comprising: receiving (1270) from the NF an association response indicating whether the NF accepted the further association request for the UE; and forwarding (1280) the association response to the UE.

18. The method of claim 17, wherein the association request is received together with a routing identifier, and the method further comprises selecting (1250) the NF based on one or more of the following: the routing identifier, and a tracking area associated with the UE.

19. The method of claim 18, wherein the association response includes one of the following: a correlation identifier associated with the NF, when the association response indicates that the NF accepted the further association request; or a second routing identifier associated with a different NF, when the association response indicates that the NF rejected the further association request.

20. The method of any of claims 11-19, wherein the further association request includes or is sent together with an indication that the AMF verified the first indication.

21. The method of any of claims 11-20, wherein one of the following applies: the UE is a positioning reference unit, PRU, and the NF is a location management function, LMF, in a 5G core network, 5GC; and the UE is a sensing UE and the NF is a sensing management function, SeMF, in a 5GC.

22. A method for a user equipment (UE) configured to assist with positioning and/or sensing operations in a communication network, the method comprising: sending (1010), to an access and mobility management function, AMF, of the communication network, an association request that includes a first indication that the UE is configured to operate as an assisting UE; and receiving (1020), from the AMF, a response indicating whether the association request was accepted or rejected by a network function, NF, configured to manage positioning and/or sensing operations in the communication network.

23. The method of claim 22, wherein the association request also includes one or more of the following: a reason for the association, a second indication of whether the UE is stationary or mobile; a third indication of the UE’s positioning and/or sensing capabilities,

24. The method of any of claims 22-23, wherein: the association request is sent together with a routing identifier associated with the NF; and the association response includes one of the following: a correlation identifier associated with the NF, when the association response indicates that the NF accepted the association request; or a second routing identifier associated with a different NF, when the association response indicates that the NF rejected the association request.

25. The method of any of claims 22-24, wherein one of the following applies: the UE is a positioning reference unit, PRU, and the NF is a location management function, LMF, in a 5G core network, 5GC; and the UE is a sensing UE and the NF is a sensing management function, SeMF, in a 5GC.

26. Network equipment (1308, 1500, 1702) arranged to implement a network function, NF (240, 340, 510, 640, 740, 840, 940) configured to manage positioning and/or sensing operations in a communication network (199, 220, 320, 1302), the NNF comprising: communication interface circuitry (1506, 1704) configured to communicate with other NFs of the communication network; and processing circuitry (1502, 1704) operatively coupled to the communication interface circuitry, wherein the processing circuitry and the communication interface circuitry are configured to: receive, from an access and mobility management function, AMF (230, 330, 630, 730, 830, 930), of the communication network, an association request for a user equipment, UE (210, 310, 610, 710, 810, 910, 1312, 1400), wherein the association request includes or is received with the following information: a first indication that the UE is configured to operate as an assisting UE, and a second indication of whether the UE is stationary or mobile; and send to the AMF an association response indicating whether the NF accepted the association request for the UE; and when the NF accepts the association request, selectively store, based on the second indication, information about the UE’s operation as an assisting UE.

27. The network equipment of claim 26, wherein the processing circuitry and the communication interface circuitry are further configured to perform operations corresponding to any of the methods of claims 2-10.

28. Network equipment (1308, 1500, 1702) arranged to implement a network function, NF (240, 340, 510, 640, 740, 840, 940) configured to manage positioning and/or sensing operations in a communication network (199, 220, 320, 1302), the network equipment being further arranged to: receive, from an access and mobility management function, AMF (230, 330, 630, 730, 830, 930), of the communication network, an association request for a user equipment, UE (210, 310, 610, 710, 810, 910, 1312, 1400), wherein the association request includes or is received with the following information: a first indication that the UE is configured to operate as an assisting UE, and a second indication of whether the UE is stationary or mobile; and send to the AMF an association response indicating whether the NF accepted the association request for the UE; and when the NF accepts the association request, selectively store, based on the second indication, information about the UE’s operation as an assisting UE.

29. The network equipment of claim 28, being further arranged to perform operations corresponding to any of the methods of claims 2-10.

30. A non-transitory, computer-readable medium (1504, 1704) storing computer-executable instructions that, when executed by processing circuitry (1502, 1704) associated with a network function, NF (240, 340, 510, 640, 740, 840, 940) configured to manage positioning and/or sensing operations in a communication network (199, 220, 320, 1302), configure the NF to perform operations corresponding to any of the methods of claims 1-10.

31. A computer program product (1204a, 1404a) comprising computer-executable instructions that, when executed by processing circuitry (1502, 1704) associated with a network function, NF (240, 340, 510, 640, 740, 840, 940) configured to manage positioning and/or sensing operations in a communication network (199, 220, 320, 1302), configure the NF to perform operations corresponding to any of the methods of claims 1-10.

32. Network equipment (1308, 1500, 1702) configured to implement an access and mobility management function, AMF (230, 330, 630, 730, 830, 930) of a communication network (199, 220, 320, 1302), the network equipment comprising: communication interface circuitry (1506, 1704) configured to communicate with user equipment, UEs, and with other network functions, NFs, of the communication network; and processing circuitry (1502, 1704) operatively coupled to the communication interface circuitry, wherein the processing circuitry and the communication interface circuitry are configured to: receive, from a user equipment, UE (210, 310, 610, 710, 810, 910, 1312, 1400), an association request that includes a first indication that the UE is configured to operate as an assisting UE; verify the first indication based on subscription information for the UE; and based on verifying the first indication, send a further association request for the UE to a network function, NF (240, 340, 510, 640, 740, 840, 940) configured to manage positioning and/or sensing operations in the communication network, wherein the further association request includes or is sent together with a second indication of whether the UE is stationary or mobile.

33. The network equipment of claim 32, wherein the processing circuitry and the communication interface circuitry are further configured to perform operations corresponding to any of the methods of claims 12-21.

34. Network equipment (1308, 1500, 1702) configured to implement an access and mobility management function, AMF (230, 330, 630, 730, 830, 930) of a communication network (199, 220, 320, 1302), the network equipment being configured to: receive, from a user equipment, UE (210, 310, 610, 710, 810, 910, 1312, 1400), an association request that includes a first indication that the UE is configured to operate as an assisting UE; verify the first indication based on subscription information for the UE; and based on verifying the first indication, send a further association request for the UE to a network function, NF (240, 340, 510, 640, 740, 840, 940) configured to manage positioning and/or sensing operations in the communication network, wherein the further association request includes or is sent together with a second indication of whether the UE is stationary or mobile.

35. The network equipment of claim 34, being further configured to perform operations corresponding to any of the methods of claims 12-21.

36. A non-transitory, computer-readable medium (1504, 1704) storing computer-executable instructions that, when executed by processing circuitry (1502, 1704) associated with an access and mobility management function, AMF (230, 330, 630, 730, 830, 930) of a communication network (199, 220, 320, 1302), configure the AMF to perform operations corresponding to any of the methods of claims 11-21.

37. A computer program product (1504a, 1704a) comprising computer-executable instructions that, when executed by processing circuitry (1502, 1704) associated with an access and mobility management function, AMF (230, 330, 630, 730, 830, 930) of a communication network (199, 220, 320, 1302), configure the AMF to perform operations corresponding to any of the methods of claims 11-21.

38. User equipment, UE (210, 310, 610, 710, 810, 910, 1312, 1400) configured to assist with positioning and/or sensing operations in a communication network (199, 220, 320, 1302), the UE comprising: communication interface circuitry (1412) configured to communicate with an access and mobility management function, AMF (230, 330, 630, 730, 830, 930) of the communication network; and processing circuitry (1402) operatively coupled to the communication interface circuitry, wherein the processing circuitry and the communication interface circuitry are configured to: send, to the AMF, an association request that includes a first indication that the UE is configured to operate as an assisting UE; and receive, from the AMF, a response indicating whether the association request was accepted or rejected by a network function, NF (240, 340, 510, 640, 740, 840, 940) configured to manage positioning and/or sensing operations in the communication network.

39. The UE of claim 38, wherein the processing circuitry and the communication interface circuitry are further configured to perform operations corresponding to any of the methods of claims 23-25.

40. User equipment, UE (210, 310, 610, 710, 810, 910, 1312, 1400) configured to assist with positioning and/or sensing operations in a communication network (199, 220, 320, 1302), the UE being further configured to: send, to an access and mobility management function, AMF (230, 330, 630, 730, 830, 930) of the communication network, an association request that includes a first indication that the UE is configured to operate as an assisting UE; and receive, from the AMF, a response indicating whether the association request was accepted or rejected by a network function, NF (240, 340, 510, 640, 740, 840, 940) configured to manage positioning and/or sensing operations in the communication network.

41. The UE of claim 40, being further configured to perform operations corresponding to any of the methods of claims 23-25.

42. A non-transitory, computer-readable medium (1110) storing computer-executable instructions that, when executed by processing circuitry (1102) of user equipment, UE (210, 310, 610, 710, 810, 910, 1312, 1400) configured to assist with positioning and/or sensing operations in a communication network (199, 220, 320, 1302), configure the UE to perform operations corresponding to any of the methods of claims 22-25.

43. A computer program product (1114) comprising computer-executable instructions that, when executed by processing circuitry (1102) of user equipment, UE (210, 310, 610, 710, 810, 910, 1312, 1400) configured to assist with positioning and/or sensing operations in a communication network (199, 220, 320, 1302), configure the UE to perform operations corresponding to any of the methods of claims 22-25.