Patent Description:
Examples of mobile or wireless telecommunication systems may include <NUM> RAT, the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), LTE Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), LTE-A Pro, NR access technology, and/or MulteFire Alliance. <NUM> wireless systems refer to the next generation (NG) of radio systems and network architecture. A <NUM> system is typically built on a <NUM> NR, but a <NUM> (or NG) network may also be built on E-UTRA radio. It is expected that NR can support service categories such as enhanced mobile broadband (eMBB), ultra-reliable low-latency-communication (URLLC), and massive machine type communication (mMTC). NR is expected to deliver extreme broadband, ultra-robust, low latency connectivity, and massive networking to support the Internet of Things (IoT). The next generation radio access network (NG-RAN) represents the RAN for <NUM>, which may provide radio access for NR, LTE, and LTE-A. It is noted that the base station (BS) in <NUM> (e.g., similar to the Node B in UTRAN or the Evolved Node B (eNB) in LTE) providing radio access functionality to a user equipment may be referred to as next-generation Node B (gNB) when built on NR radio, and may be referred to as next-generation eNB (NG-eNB) when built on E-UTRA radio.

<NPL> addresses the remaining issue on TRP ID definition and its presence in NRPPa. The following proposals regarding NRPPa leftover issues from last meeting have been made:.

It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for coordinating transmission reception point (TRP) selection between a location management function (LMF) and base station (BS) is not intended to limit the scope of certain embodiments, but is instead representative of selected example embodiments.

As noted above, <FIG> illustrates a NG-RAN positioning architecture with a LMF and TRP. The LMF may manage various location services for target user equipment (UE), including UE positioning. The LMF may determine which positioning method to use, such as according to quality of service (QoS) requirements, UE capabilities, and BS capabilities, and invokes the positioning method in the UE and/or BSs to produce positioning measurements. The LMF may then combine all of the received measurement results with other assistance data to calculate a location estimate for the target UE. In contrast, the TRP is a functional component of the BS that may support functions for a transmission point (TP), reception point (RP), and/or TP-RP combination.

New Radio Positioning Protocol A (NRPPa) may carry information between the BS and LMF via an access and mobility management function (AMF). NRPPa messages could be transferred over a next generation control plane (NG-C) interface using next generation application protocol (NGAP) signaling, either UE-associated or non UE-associated. In particular, UE-associated signaling may use a logical connection associated to a UE that is uniquely identified by at least one UE NGAP identifier (ID), enabling UE identification at the BS. Furthermore, non UE-associated signaling does not use a UE-associated logical connection; thus, UE identification is not possible at the BS in this way.

3GPP Rel-<NUM> introduced new positioning methods, such as Multi-RTT, uplink (UL) time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA), using NR reference signal measurements to calculate the location of a target UE. Some of these NR positioning methods rely on measurements of uplink reference signals, such as UL sounding reference signals (SRS), transmitted by the target UE, where the measurements are performed by TRPs hosted by the serving and/or non-serving BSs. Uplink measurement may be associated with applicable positioning methods as follows:.

The example NRPPa measurement procedures illustrated in <FIG> and <FIG> may enable the LMF to request one or more TRPs in the BS to perform and report positioning measurements. For example, a MEASUREMENT REQUEST message may include any combination of a TRP Measurement Request List information element (IE) indicating the TRP(s) from which measurements are requested, and a Measurement Quantities IE indicating the desired measurements (e.g., UL-relative time of arrival (RTOA) and/or UL AoA).

For certain positioning methods such as Multi-RTT, it is necessary for TRP selection to be centralized at the LMF, such that uplink measurements by BS(s) and downlink measurements by the target UE are associated with the same set of TRPs. However, for certain positioning methods such as UL TDOA and UL AoA, which require only uplink measurements, it could be beneficial for a BS to perform TRP selection. TRP selection by a BS may be for instance beneficial in case there is a high density of TRPs where UE mobility prevents optimal selection performance by the LMF. In addition, multiple UE mobility profiles, such as stationary, pedestrian, and/or vehicle, located in the same geographical area may prevent optimal TRP selection by the LMF and reduce the performance of the positioning. Furthermore, if a BS has an active MDT configuration running across multiple TRPs, it may be beneficial for the BS to complete the MDT operation on the existing TRPs before reconfiguring a new set of TRPs.

Certain embodiments described herein may have various benefits and/or advantages to overcome the disadvantages described above. For example, certain embodiments may enable an LMF to continue controlling TRP selection for scenarios where it is required, while also allowing flexibility for the BS to perform TRP selection for scenarios where it may be beneficial. Some embodiments may also improve TRP selection results through efficient performance of NR positioning, such as with improved accuracy due to better quality measurements and/or reduction of measurement failures due to incorrect TRP selection. Certain embodiments may also allow the BS to use other information otherwise unavailable at the LMF, such as radio resource control (RRC)/radio resource management (RRM) and/or UE mobility history. Thus, certain embodiments discussed below are directed to improvements in computer-related technology.

<FIG> illustrates an example of a signaling diagram depicting flexible TRP selection coordination between NE <NUM> and LMF <NUM>. NE <NUM> and LMF <NUM> may be similar to NE <NUM>, as illustrated in <FIG>, according to certain embodiments.

At <NUM>, LMF <NUM> transmits at least one measurement report request to NE <NUM>. In some embodiments, the measurement report request includes at least one measurement quantities IE (e.g., "Measurement Quantities IE") indicating a request for UL RTOA measurements for UL-TDOA. The measurement report request includes at least one measurement request list IE (e.g., "TRP Measurement Request List IE") containing a list of TRP IDs selected by LMF <NUM> configured to perform uplink measurements.

The measurement report request includes one or more indications that NE <NUM> may modify the list of TRP IDs. The indication may indicate that the list of TRP IDs is a recommendation or requirement, and/or may designate specific TRPs in the list of TRP IDs as a recommendation or requirement. For example, the measurement report request may include an indication, such as TRP List Modification Allowed IE, indicating whether the list of TRP IDs is a recommendation and may be modified by NE <NUM>. This indication may be a Boolean value (e.g., "true" or "false") or any enumerated value (e.g., "allowed"). If the list of TRP IDs is a recommendation, the indication may indicate that NE <NUM> is authorized to add and/or remove TRPs from the list of TRP IDs. Alternatively, if the list of TRP IDs is a requirement, the indication may indicate that NE <NUM> is not authorized to add and/or remove TRPs from the list of TRP IDs. Other indications may indicate that NE <NUM> is authorized to remove from - but not add to - the list of TRP IDs.

The measurement report request includes any number of TRP modification rules, and, optionally, constraints to further control how NE <NUM> may modify the list of TRP IDs in case TRP modification is allowed. As an example, LMF <NUM> may include for recommended TRP IDs a list of alternative TRP IDs ("white list") that NE <NUM> may use to replace the recommended TRP IDs in the list of TRP IDs. Additionally, LMF <NUM> may signal rankings in the white list by a recommended selection priority. Furthermore, the measurement report request may specify any combination of a maximum and/or minimum number of TRPs; a maximum and/or minimum distance between TRPs; an absolute and/or relative direction of TRPs; indications of TRPs that NE <NUM> should exclude from the list of TRP IDs ("black list"); indications of TRPs that NE <NUM> should preserve in the list of TRP IDs; and indications of TRPs that NE <NUM> should include in the list of TRP IDs reported in a first measurement report, but may exclude in subsequent measurement reports.

In certain embodiments, the measurement report request may be transmitted via UE-associated signalling with NE <NUM> while using non-UE-associated signaling with non-serving NEs (which may also be similar to NE <NUM> in <FIG>). Measurement procedures performed by NE <NUM> may also be UE-associated, allowing NE <NUM> to select TRPs using UE-specific information, such as RRM measurements, MDT configurations, and/or UE history information. UEs may be similar to UE <NUM>, as shown in <FIG>.

In some embodiments, the measurement report request may include at least one report characteristics IE (e.g., "Report Characteristics IE") indicating whether the measurement request is "on-demand" or "periodic. " In some embodiments, this indication may be a Boolean value (e.g., "true" or "false") or any enumerated value (e.g., "OnDemand" or "Periodic").

At <NUM>, where the at least one report characteristics IE includes at least one predetermined parameter, such as "OnDemand," NE <NUM> may transmit to LMF <NUM> at least one measurement response, which may include an altered or unaltered list of TRP IDs and their requested measurements. In various embodiments, where NE <NUM> received TRP List Modification Allowed IE with an affirmative value at <NUM>, NE <NUM> may modify the list of TRP IDs selected by LMF <NUM> with all or a subset of TRPs included in a white list received from LMF <NUM>, such as when NE <NUM> is positioning a UE in an existing MDT session to leverage the same set of measurements. If TRP List Modification Allowed IE was affirmatively indicated by LMF <NUM>, NE <NUM> may replace TRP-A in the recommended list with TRP-B from the white list. If NE <NUM> received indications that particular TRPs are recommendations without receiving a white list from LMF <NUM>, NE <NUM> may select alternative TRPs which differ from those TRPs selected by LMF <NUM>. NE <NUM> may also select TRP IDs based on RRM measurements and/or other performance information known locally by NE <NUM>. NE <NUM> may also drop TRP IDs from the list of TRP IDs selected by LMF <NUM> without selecting an alternative TRP.

Additionally or alternatively, NE <NUM> may measure a larger group of TRPs, such as according to spatial relation information in an SRS configuration, and report a pre-determined number of strongest TRPs to LMF <NUM>. NE <NUM> may use different TRP IDs to reflect UE history information and/or estimated UE mobility profiles.

In certain embodiments, NE <NUM> may transmit to LMF <NUM> indications that any number of TRP IDs are alternatives, enabling LMF <NUM> to interpret the information associated with the TRPs indicated by NE <NUM> accordingly. For example, a modification flag IE (e.g., "Modification Flag IE") in the measurement response may indicate to LMF <NUM> that missing and/or new TRP IDs should be considered a result of the modification process performed by NE <NUM>, rather than an error. The modification flag IE may be configured as a Boolean value (e.g., "true" or "false") or any enumerated value (e.g., "modified"), and/or may be indicated per TRP ID.

In some embodiments, if a report characteristics IE (e.g., "Report Characteristics IE") indicates "on-demand," NE <NUM> may transmit the list of TRP IDs and/or measurement results in, for example, a measurement response message to LMF <NUM>. Alternatively, if the Report Characteristics IE indicates "periodic," NE <NUM> may transmit a measurement response message to LMF <NUM> without the list of TRP IDs and/or measurement results, followed by, at <NUM>, transmitting at least one measurement report message to LMF <NUM> including the altered or unaltered list of TRP IDs and/or measurement results according to the requested periodicity. In various embodiments, where the report characteristics IE indicates "periodic," the measurement report message may also include the modification flag IE.

At <NUM>, LMF <NUM> may determine at least one position estimate according to the requested measurements performed by the modified set of TRP IDs, which may improve the accuracy of a position computation. For example, such an improved position estimate computation may be based on requested measurements from a modified set of TRP IDs selected by NE <NUM> at <NUM> that are more optimal than the list of TRP IDs selected by LMF <NUM> at <NUM>, for example, due to the location of the modified set of TRPs relative to a UE, the location of the modified set of TRPs relative to each other, and the number of TRPs in the modified set of TRPs.

<FIG> illustrates an example of a flow diagram of a method that may be performed by a NE, such as NE <NUM> illustrated in <FIG>, according to various embodiments. At <NUM>, the NE may receive at least one measurement report request from a LMF, such as NE <NUM> in <FIG>. In some embodiments, the measurement report request may include at least one measurement quantities IE (e.g., "Measurement Quantities IE") indicating at least one request for UL RTOA measurements for UL-TDOA. The measurement report request includes at least one measurement request list IE (e.g., "TRP Measurement Request List IE") containing a list of TRP IDs selected by the LMF configured to perform uplink measurements.

The measurement report request includes one or more indications that the NE may modify the list of TRP IDs. The one or more indications may indicate that the list of TRP IDs is a recommendation or requirement, or may designate specific TRPs in the list of TRP IDs as a recommendation or requirement. For example, the measurement report request may include an indication, such as TRP List Modification Allowed IE, indicating whether the list of TRP IDs is a recommendation and may be modified by the NE. This indication may be a Boolean value (e.g., "true" or "false") or any enumerated value (e.g., "allowed"). If the list of TRP IDs is a recommendation, the indication may designate that the NE is authorized to add and/or remove TRPs from the list of TRP IDs. Alternatively, if the list of TRP IDs is a requirement, the indication may designate that the NE is not authorized to add and/or remove TRPs from the list of TRP IDs. Other indications may indicate that the NE is authorized to remove from - but not add to - the list of TRP IDs.

The measurement report request includes any number of TRP modification rules , and, optionally, constraints to further control how the NE may modify the list of TRP IDs in case TRP modification is allowed. As an example, the LMF may include for recommended TRP IDs a list of alternative TRP IDs ("white list") that the NE may use to replace the recommended TRP IDs in the list of TRP IDs. Additionally, the LMF may signal rankings in the white list by a recommended selection priority. Furthermore, the measurement report request may specify any combination of a maximum and/or minimum number of TRPs; a maximum and/or minimum distance between TRPs; an absolute and/or relative direction of TRPs; indications of TRPs that the NE should exclude from the list of TRP IDs ("black list"); indications of TRPs that the NE should preserve in the list of TRP IDs; and indications of TRPs that the NE should include in the list of TRP IDs reported in a first measurement report, but may exclude in subsequent measurement reports.

In certain embodiments, the measurement report request may be transmitted via UE-associated signalling with the NE while using non-UE-associated signaling with non-serving NEs (which may also be similar to NE <NUM> in <FIG>). Measurement procedures performed by the NE may also be UE-associated, allowing the NE to select TRPs using UE-specific information, such as RRM measurements, MDT configurations, and/or UE history information. UEs may be similar to UE <NUM>, as shown in <FIG>.

In some embodiments, the measurement report request may include a report characteristics IE (e.g., "Report Characteristics IE") indicating whether the measurement request is "on-demand" or "periodic. " In some embodiments, this indication may be a Boolean value (e.g., "true" or "false") or any enumerated value (e.g., "OnDemand" or "Periodic").

At <NUM>, where the at least one report characteristics IE includes at least one predetermined parameter, such as "OnDemand", the NE may transmit to the LMF at least one measurement response, which may include an altered or unaltered list of TRP IDs and their requested measurements. In various embodiments, where the NE received TRP List Modification Allowed IE with an affirmative value at <NUM>, the NE may modify the list of TRP IDs selected by the LMF with all or a subset of TRPs included in a white list received from the LMF, such as when the NE is positioning a UE in an existing MDT session to leverage the same set of measurements. If TRP List Modification Allowed IE was affirmatively indicated by the LMF, the NE may replace TRP-A in the recommended list with TRP-B from the white list. If the NE received indications that particular TRPs are recommendations without receiving a white list from the LMF, the NE may select alternative TRPs which differ from those TRPs selected by the LMF. The NE may also select TRP IDs based on RRM measurements and/or other performance information known locally by NE <NUM>.

Additionally or alternatively, the NE may measure a larger group of TRPs, such as according to spatial relation information in an SRS configuration, and report a pre-determined number of strongest TRPs to the LMF. The NE may use different TRP IDs to reflect UE history information and/or estimated UE mobility profiles.

In certain embodiments, the NE may transmit to the LMF indications that any number of TRP IDs are alternatives, enabling the LMF to interpret the information associated with the TRPs indicated by the NE accordingly. For example, a modification flag IE (e.g., "Modification Flag IE") in the measurement response may indicate to the LMF that missing and/or new TRP IDs should be considered a result of the modification process performed by the NE, rather than an error. The modification flag IE may be configured as a Boolean value (e.g., "true" or "false") or any enumerated value (e.g., "modified"), and/or may be indicated per TRP ID.

In some embodiments, if a report characteristics IE (e.g., "Report Characteristics IE") indicates "on-demand," the NE may transmit the list of TRP IDs and/or measurement results in, for example, a measurement response message to the LMF. Alternatively, if the Report Characteristics IE indicates "periodic," the NE may transmit a measurement response message to the LMF without the list of TRP IDs and/or measurement results, followed by, at <NUM>, transmitting at least one measurement report message to the LMF including the altered or unaltered list of TRP IDs and/or measurement results according to the requested periodicity.

<FIG> illustrates an example of a flow diagram of a method that may be performed by a LMF, such as NE <NUM> illustrated in <FIG>, according to various embodiments. At <NUM>, the LMF transmits at least one measurement report request to a NE. In some embodiments, the measurement report request may include at least one measurement quantities IE (e.g., "Measurement Quantities IE") indicating a request for UL RTOA measurements for UL-TDOA. The measurement report request includes at least one measurement request list IE (e.g., "TRP Measurement Request List IE") containing a list of TRP IDs selected by the LMF configured to perform uplink measurements.

The measurement report request includes one or more indications that the NE may modify the list of TRP IDs. The indication may indicate that the list of TRP IDs is a recommendation or requirement, and/or may designate specific TRPs in the list of TRP IDs as a recommendation or requirement. For example, the measurement report request may include an indication, such as TRP List Modification Allowed IE, indicating whether the list of TRP IDs is a recommendation and may be modified by the NE. This indication may be a Boolean value (e.g., "true" or "false") or any enumerated value (e.g., "allowed"). If the list of TRP IDs is a recommendation, the indication may indicate that the NE is authorized to add and/or remove TRPs from the list of TRP IDs. Alternatively, if the list of TRP IDs is a requirement, the indication may indicate that the NE is not authorized to add and/or remove TRPs from the list of TRP IDs. Other indications may indicate that the NE is authorized to remove from - but not add to - the list of TRP IDs.

In some embodiments, the measurement report request may include a report characteristics IE (e.g., "Report Characteristics IE") indicating whether the measurement request is "on-demand" or "periodic. " This indication may be a Boolean value (e.g., "true" or "false") or any enumerated value (e.g., "OnDemand" or "Periodic").

At <NUM>, where the at least one report characteristics IE includes at least one predetermined parameter, such as "OnDemand," the LMF may receive from the NE at least one measurement response, which may include an altered or unaltered list of TRP IDs and their requested measurements. In various embodiments, where the NE received TRP List Modification Allowed IE with an affirmative value at <NUM>, the NE may modify the list of TRP IDs selected by the LMF with all or a subset of TRPs included in a white list received from the LMF, such as when the NE is positioning a UE in an existing MDT session to leverage the same set of measurements. If TRP List Modification Allowed IE was affirmatively indicated by the LMF, the NE may replace TRP-A in the recommended list with TRP-B from the white list. If the NE received indications that particular TRPs are recommendations without receiving a white list from the LMF, the NE may select alternative TRPs which differ from those TRPs selected by the LMF. The NE may also select TRP IDs based on RRM measurements and/or other performance information known locally by the NE.

In certain embodiments, the LMF may receive from the NE indications that any number of TRP IDs are alternatives, enabling the LMF to interpret the information associated with the TRPs indicated by the NE accordingly. For example, a modification flag IE (e.g., "Modification Flag IE") in the measurement response may indicate to the LMF that missing and/or new TRP IDs should be considered a result of the modification process performed by the NE, rather than an error. The modification flag IE may be configured as a Boolean value (e.g., "true" or "false") or any enumerated value (e.g., "modified"), and/or may be indicated per TRP ID.

In some embodiments, if a report characteristics IE (e.g., "Report Characteristics IE") indicates "on-demand," the LMF may receive the list of TRP IDs and/or measurement results in, for example, a measurement response message from the NE. Alternatively, if the Report Characteristics IE indicates "periodic," the LMF may receive a measurement response message from the NE without the list of TRP IDs and/or measurement results, followed by, at <NUM>, receiving at least one measurement report message from the NE including the altered or unaltered list of TRP IDs and/or measurement results according to the requested periodicity. In various embodiments, where the report characteristics IE indicates "periodic," the measurement report message may also include the modification flag IE.

At <NUM>, the LMF may determine at least one position estimate according to the requested measurements performed by the modified set of TRP IDs, which may improve the accuracy of a position computation. For example, such an improved position estimate computation may be based on requested measurements from a modified set of TRP IDs selected by the NE at <NUM> that are more optimal than the list of TRP IDs selected by the LMF at <NUM>, for example, due to the location of the modified set of TRPs relative to a UE, the location of the modified set of TRPs relative to each other, and the number of TRPs in the modified set of TRPs.

<FIG> illustrates an example of a system according to certain example embodiments. In one example embodiment, a system may include multiple devices, such as, for example, NE <NUM> and/or UE <NUM>.

NE <NUM> may be one or more of a LMF, a base station (such as a NB, eNB, gNB, or NG-eNB), a serving gateway, a server, and/or any other access node or combination thereof. Furthermore, NE <NUM> and/or UE <NUM> may be one or more of a citizens broadband radio service device (CBSD).

NE <NUM> may further comprise at least one gNB-CU, which may be associated with at least one gNB-DU. The at least one gNB-CU and the at least one gNB-DU may be in communication via at least one F1 interface, at least one Xn-C interface, and/or at least one NG interface via a 5GC.

UE <NUM> may include one or more of a mobile device, such as a mobile phone, smart phone, personal digital assistant (PDA), tablet, or portable media player, digital camera, pocket video camera, video game console, navigation unit, such as a global positioning system (GPS) device, desktop or laptop computer, single-location device, such as a sensor or smart meter, or any combination thereof.

NE <NUM> and/or UE <NUM> may include at least one processor, respectively indicated as <NUM> and <NUM>. Processors <NUM> and <NUM> may be embodied by any computational or data processing device, such as a central processing unit (CPU), application specific integrated circuit (ASIC), or comparable device. The processors may be implemented as a single controller, or a plurality of controllers or processors.

At least one memory may be provided in one or more of the devices, as indicated at <NUM> and <NUM>. The memory may be fixed or removable. The memory may include computer program instructions or computer code contained therein. Memories <NUM> and <NUM> may independently be any suitable storage device, such as a non-transitory computer-readable medium. A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. The memories may be combined on a single integrated circuit as the processor, or may be separate from the one or more processors. Furthermore, the computer program instructions stored in the memory, and which may be processed by the processors, may be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.

Processors <NUM> and <NUM>, memories <NUM> and <NUM>, and any subset thereof, may be configured to provide means corresponding to the various blocks of <FIG>. Although not shown, the devices may also include positioning hardware, such as GPS or micro electrical mechanical system (MEMS) hardware, which may be used to determine a location of the device. Other sensors are also permitted, and may be configured to determine location, elevation, velocity, orientation, and so forth, such as barometers, compasses, and the like.

As shown in <FIG>, transceivers <NUM> and <NUM> may be provided, and one or more devices may also include at least one antenna, respectively illustrated as <NUM> and <NUM>. The device may have many antennas, such as an array of antennas configured for multiple input multiple output (MIMO) communications, or multiple antennas for multiple RATs. Other configurations of these devices, for example, may be provided. Transceivers <NUM> and <NUM> may be a transmitter, a receiver, both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception.

The memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus, such as UE, to perform any of the processes described above (i.e., <FIG>). Therefore, in certain embodiments, a non-transitory computer-readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain embodiments may be performed entirely in hardware.

In certain embodiments, an apparatus may include circuitry configured to perform any of the processes or functions illustrated in <FIG>. For example, circuitry may be hardware-only circuit implementations, such as analog and/or digital circuitry. In another example, circuitry may be a combination of hardware circuits and software, such as a combination of analog and/or digital hardware circuitry with software or firmware, and/or any portions of hardware processors with software (including digital signal processors), software, and at least one memory that work together to cause an apparatus to perform various processes or functions. In yet another example, circuitry may be hardware circuitry and or processors, such as a microprocessor or a portion of a microprocessor, that includes software, such as firmware, for operation. Software in circuitry may not be present when it is not needed for the operation of the hardware.

<FIG> illustrates an example of a <NUM> network and system architecture according to certain embodiments. Shown are multiple network functions that may be implemented as software operating as part of a network device or dedicated hardware, as a network device itself or dedicated hardware, or as a virtual function operating as a network device or dedicated hardware. The NE and UE illustrated in <FIG> may be similar to NE <NUM> and UE <NUM>, respectively. The user plane function (UPF) may provide services such as intra-RAT and inter-RAT mobility, routing and forwarding of data packets, inspection of packets, user plane quality of service (QoS) processing, buffering of downlink packets, and/or triggering of downlink data notifications. The application function (AF) may primarily interface with the core network to facilitate application usage of traffic routing and interact with the policy framework.

For example, the usage of the phrases "various embodiments," "certain embodiments," "some embodiments," or other similar language throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an example embodiment may be included in at least one example embodiment. Thus, appearances of the phrases "in various embodiments," "in various embodiments," "in certain embodiments," "in some embodiments," or other similar language throughout this specification does not necessarily all refer to the same group of example embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.

Additionally, if desired, the different functions or procedures discussed above may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions or procedures may be optional or may be combined. As such, the description above should be considered as illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.

Claim 1:
A method of positioning a target user equipment, comprising:
receiving, by a network entity (<NUM>), at least one measurement report request from a location management function (<NUM>) comprising a list of at least one transmission reception point identifier from which measurements of uplink reference signals are requested, wherein the location management function (<NUM>) manages location service for a target user equipment;
determining, by the network entity (<NUM>), to modify at least one transmission reception point identifier in the transmission reception point measurement request list based at least in part on the at least one measurement report request; and
transmitting, by the network entity (<NUM>), at least one measurement response to the location management function (<NUM>) comprising a transmission reception point measurement response list of at least one transmission reception point identifier from which measurements are performed, wherein the transmission reception point measurement response list is different than the transmission reception point measurement request list;
the method being characterized in that
the at least one measurement report request further comprises one indication that the network entity (<NUM>) is allowed to modify the transmission reception point measurement request list and at least one transmission reception point modification rule configured to control by the location management function at least one modification by the network entity of at least one transmission reception point identifier.