Location reporting in a wireless communication system

Abstract

Various aspects of the present disclosure relate to a first network entity for wireless communication. The first network entity may be configured to, capable of, or operable to: receive, from a second network entity, a location reporting requirement, wherein the location reporting requirement is for reporting a location of a user equipment, UE, according to an energy management criterion for the UE; and transmit, to the UE, a location reporting configuration for the UE, wherein the location reporting configuration is based on the energy management criterion.

Description

LOCATION REPORTING IN A WIRELESS COMMUNICATION SYSTEMTECHNICAL FIELD

[0001] The present disclosure relates generally to wireless communication, including location reporting.BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, which may be otherwise knowns as network equipment (NE) supporting wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY

[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, asDocket No. SMM920250193-GR-NPused herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] A first network entity for wireless communication is described. The first network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the first network entity may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive, from a second network entity, a location reporting requirement, wherein the location reporting requirement is for reporting a location of a UE according to an energy management criterion for the UE; and transmit, to the UE, a location reporting configuration for the UE, wherein the location reporting configuration is based on the energy management criterion.

[0005] A method performed or performable by the first network entity is described herein. The method may comprise: receiving, from a second network entity, a location reporting requirement, wherein the location reporting requirement is for reporting a location of a UE according to an energy management criterion for the UE; and transmitting, to the UE, a location reporting configuration for the UE, wherein the location reporting configuration is based on to the energy management criterion.

[0006] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a second network entity, a location reporting requirement, wherein the location reporting requirement is for reporting a location of a UE according to an energy management criterion for the UE; and transmit, to the UE, a location reporting configuration for the UE, wherein the location reporting configuration is based on the energy management criterion.

[0007] A UE for wireless communication is described. The UE may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the UE may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the UE to: receive, from a first networkDocket No. SMM920250193-GR-NPentity, a location reporting configuration, wherein the location reporting configuration is for reporting a location of the UE, wherein the location reporting configuration is determined according to an energy management criterion.

[0008] A method performed or performable by the UE is described herein. The method may comprise: receiving, from a first network entity, a location reporting configuration, wherein the location reporting configuration is for reporting a location of the UE, wherein the location reporting configuration is determined according to an energy management criterion.

[0009] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a first network entity, a location reporting configuration, wherein the location reporting configuration is for reporting a location of the UE, wherein the location reporting configuration is determined according to an energy management criterion.BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure.

[0011] Figure 2 illustrates an example of an on-network function model for Location Management (LM) 200 in accordance with aspects of the present disclosure.

[0012] Figure 3 illustrates an example of an off-network function model for LM 300 in accordance with aspects of the present disclosure.

[0013] Figure 4 illustrates an example of a process flow 400 for location reporting in accordance with aspects of the present disclosure.

[0014] Figure 5 illustrates an example of a UE 500 in accordance with aspects of the present disclosure.

[0015] Figure 6 illustrates an example of a processor 600 in accordance with aspects of the present disclosure.Docket No. SMM920250193-GR-NP

[0016] Figure 7 illustrates an example of a NE 700 in accordance with aspects of the present disclosure.

[0017] Figure 8 illustrates a flowchart of a method 800 performed by a UE in accordance with aspects of the present disclosure.

[0018] Figure 9 illustrates a flowchart of a method 900 performed by a NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0019] A wireless communication system, including one or more UE and NE may be configured to support Location Services (LCS). The wireless communication system may also be configured to support verticals. Verticals refers to industry sectors that use wireless communication systems to enable their own specialized applications and services. The industrial sectors may include automotive, transportation, healthcare, smart manufacturing, public safety, energy, or logistics. Verticals have industry-specific requirements such as precise positioning for vehicles, ultra-reliable communication for factories, or massive connectivity for smart meters. Third Generation Partnership Project (3GPP) architectures such as Service Enabler Application Layer (SEAL), Vertical Application Layer (VAL), and network slicing are designed to support these vertical industries by exposing network capabilities and providing tailored functionality so that each vertical may run its applications efficiently and reliably over the wireless communication system.

[0020] In the 3 GPP Vehicle-to-anything (V2X) and SEAL architecture, a VAL UE (e.g., a vehicle, roadside unit, UE or user terminal) may run a VAL application that generates or consumes location information. A Location Management Server (LMS) is a network-side entity responsible for collecting, managing, and distributing location data from multiple VAL UEs. During location reporting, the VAL UE obtains its position (e.g., Global Navigation Satellite System (GNSS) or network-based positioning) and sends a location report to the LMS through SEAL or VAL interfaces. The LMS stores and processes this information. The LMS may sharing this information with authorized VAL Servers or other UEs to enable services (e.g., cooperative awareness, fleet tracking, or collision avoidance).Docket No. SMM920250193-GR-NP

[0021] In verticals, LCS many be performed across a large number of different use cases and scenarios. Each use case or scenario may require different location reporting requirements. This increases the complexity of the location reporting signalling since different signalling may be required for different use cases or scenarios. Examples described herein generally provide an approach to location reporting that considers an energy management criterion of the VAL UE which tends to reduce the overall complexity of the location reporting signalling.

[0022] Aspects of the present disclosure are described in the context of a wireless communications system.

[0023] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as a Long Term Evolution (LTE) network or an LTE- Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a New Radio (NR) network, such as a 5G network, a 5 G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0024] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102Docket No. SMM920250193-GR-NPand a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signalling, transmit signalling) over a Uu interface.

[0025] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0026] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0027] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0028] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In someDocket No. SMM920250193-GR-NPimplementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0029] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0030] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0031] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In someDocket No. SMM920250193-GR-NPimplementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0032] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / t=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / t=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / / =1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., g=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / t=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / t=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0033] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0034] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / t=0,Docket No. SMM920250193-GR-NPjtz=l, =2, / z=3, / z=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / t=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0035] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0036] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / t=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / / =1), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / / =2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g.,Docket No. SMM920250193-GR-NP / t=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / t=3), which includes 120 kHz subcarrier spacing.

[0037] LCS is inherently part of the 3GPP Architecture and Radio Access Node (RAN) framework. LCS may enable the identification and standardised reporting of a UE’s / group of UEs location information. This location information may be exposed to the user, mobile equipment, network operator, service provider, value added service providers and for Public Land Mobile Network (PLMN) internal operations. Given the large of variety number of use cases and applications that require LCS functionality, it is beneficial to have an LCS framework that caters to each of the scenarios and use cases.

[0038] A common LCS framework may not be applied to multiple scenarios. A location Application Program Interface (API) which may be offered to a vertical may have completely different network handling and requirements for different scenarios. Different API exposure per different case is a complex task which may require additional signaling / complexity at the network or application side to provide one time and with the required Quality of Service (QoS).

[0039] Examples described herein generally relate to adapting the configuration of location reporting from a VAL UE given the expected or actual energy consumption, battery level, energy efficiency for an entire UE or per app or per session of the UE.

[0040] The different variety of use cases / verticals, scenarios, and application services (e.g., V2X, IIoT, Unmanned Air System (UAS)) that require LCS in addition to data communications tends to increase the complexity of the LCS framework and corresponding interactions between 3 GPP and non-3GPP entities. The location-related Key Performance Indicators of the various use cases not only require varying levels of accuracy (e.g., horizontal, vertical, 2D, 3D), but also different location fix latency requirements, availability requirements, speed, and heading, etc. However, the end devices (e.g., UE) have different energy capacity and constraints and the accuracy / QoS of the LCS may be affected due to an energy criterion (e.g., energy management criterion).

[0041] Examples described herein provide a unified framework that takes into account the energy consumption or efficiency of the VAL UE for provisioning (e.g., configuring)Docket No. SMM920250193-GR-NPlocation reporting towards the server / network. The LCS profile (which encloses a set of attributes to satisfy the specific requirements of a use case and / or application service across Mobile Network Operator (MNO)(s), verticals and 3rd party operators) may be enhanced to consider the energy criterion.

[0042] Examples described herein may relate to an energy-aware configuration and signaling of the location reporting requirement. Some examples described herein may relate to signaling of an LCS profile. Some examples described herein may use of a middleware for translating a location request from a vertical application to an energy-aware location reporting (e.g., the LCS profile). Some examples described herein may provide value-added services for the vertical.

[0043] A location service may be provided by a wireless communication system. Location services may serve vertical industries or provide target applications.

[0044] Positioning requirements may be stringent with respect to accuracy, latency, and reliability. Table 1 below shows the positioning performance requirements for different scenarios in an Industrial Internet of Things (IIoT) or indoor factory setting. Examples of such positioning performance requirements are defined in TS 22.104 V19.2.0.Docket No. SMM920250193-GR-NPTable 1: IIoT Use Case Positioning Performance Requirements

[0045] Table 2 below provides details of positioning service levels defined in TS22.261 V20.4.0 for IIOT use cases.Docket No. SMM920250193-GR-NPTable 2: Positioning service levels for HOT use cases.Docket No. SMM920250193-GR-NP

[0046] The following numbered notes are relevant to Table 2. NOTE 1 : The objective for the vertical positioning requirement is to determine the floor for indoor use cases and to distinguish between superposed tracks for road and rail use cases (e.g. bridges). NOTE 2: Indoor includes location inside buildings such as offices, hospital, industrial buildings.NOTE 3: 5G positioning nodes are infrastructure equipment deployed in the service area to enhance positioning capabilities (e.g. beacons deployed on the perimeter of a rendezvous area or on the side of a warehouse).

[0047] To achieve the above location service requirement, different positioning techniques have been specified in Rel-16 and are listed in Table 3 (e.g., see in 3GPP TS 38.305 V19.0.0). These include both Radio Access Technology (RAT)-dependent and RAT-independent positioning techniques.Table 3: Supported Rel-16 UE positioning methodsDocket No. SMM920250193-GR-NP

[0048] The following numbered notes are relevant to Table 3. NOTE 1 : This includes TBS positioning based on Positioning Reference Signals (PRS) signals. NOTE 2: In this version of the specification only Observed Time Difference Of Arrival (OTDOA) based on LTE signals is supported. NOTE 3: Void. NOTE 4: This includes Cell-ID for NR method. NOTE 5: In this version of the specification only for TBS positioning based on MBS signals. NOTE 6: Void.

[0049] The following RAT-dependent positioning techniques are supported in Rel-16 (e.g., see in TS 38.305 V19.0.0): DL-TDoA, Downlink Angle-of-Departure (DL-AoD), Multiple-Round Trip Time (Multi-RTT), E-CID, NR E-CID, Uplink Time Difference Of Arrival (UL-TDoA), and UL-AoA.

[0050] The DL-TDoA positioning method makes use of the Downlink (DL) Reference Signal Time Difference (RSTD) (and optionally DL PRS Received Signal Received Power (RSRP)) of downlink signals received from multiple TPs, at the UE. The UE measures the DL RSTD (and optionally DL PRS RSRP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to locate the UE in relation to the neighbouring TPs.

[0051] The DL-AoD positioning method makes use of the measured DL PRS RSRP of downlink signals received from multiple TPs, at the UE. The UE measures the DL PRS RSRP of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to locate the UE in relation to the neighbouring TPs.

[0052] The Multi-RTT positioning method makes use of the UE Receive-Transmit (Rx- Tx) measurements and DL PRS RSRP of downlink signals received from multiple TRPs, measured by the UE and the measured gNB Rx-Tx measurements and Uplink (UL) Sounding Reference Signal (SRS)-RSRP at multiple TRPs of uplink signals transmitted from UE.

[0053] The UE measures the UE Rx-Tx measurements (and optionally DL PRS RSRP of the received signals) using assistance data received from the positioning server, and the TRPs measure the gNB Rx-Tx measurements (and optionally UL SRS-RSRP of theDocket No. SMM920250193-GR-NPreceived signals) using assistance data received from the positioning server. The measurements are used to determine the Round Trip Time (RTT) at the positioning server which are used to estimate the location of the UE.

[0054] In the E-CID / NR E-CID positioning methods, the position of a UE is estimated with the knowledge of its serving next generation Evolved NodeB (ng-eNB), gNB and cell and is based on LTE signals. The information about the serving ng-eNB, gNB and cell may be obtained by paging, registration, or other methods. In NR E-CID, positioning refers to techniques which use additional UE measurements and / or NR radio resource and other measurements to improve the UE location estimate using NR signals.

[0055] Although NR E-CID positioning may utilize some of the same measurements as the measurement control system in the Radio Resource Control (RRC) protocol, the UE generally is not expected to make additional measurements for the sole purpose of positioning; e.g., the positioning procedures do not supply a measurement configuration or measurement control message, and the UE reports the measurements that it has available rather than being required to take additional measurement actions.

[0056] The UL-TDoA positioning method makes use of the UL-TDoA (and optionally UL SRS-RSRP) at multiple RPs of uplink signals transmitted from UE. The RPs measure the UL-TDoA (and optionally UL SRS-RSRP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE.

[0057] The UL-AoA positioning method makes use of the measured Azimuth- Angle of arrival (A-AoA) and Zenith-AoA (Z-AoA) at multiple RPs of uplink signals transmitted from UE. The RPs measure A-AoA and Z-AoA of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE.

[0058] RAT-Independent positioning techniques (e.g., see in TS 38.305 V19.0.0) include: Network-assisted GNSS methods, barometric pressure sensor positioning, WLAN positioning, Bluetooth positioning, TBS positioning, and motion sensor positioning.Docket No. SMM920250193-GR-NP

[0059] Network-assisted GNSS methods make use of UEs that are equipped with radio receivers capable of receiving GNSS signals. In 3GPP specifications, the term GNSS encompasses both global and regional / augmentation navigation satellite systems. Examples of global navigation satellite systems include Global Positioning System (GPS), Modernized GPS, Galileo, GLONASS, and BeiDou Navigation Satellite System (BDS). Regional navigation satellite systems include QZSS while the many augmentation systems, are classified under the generic term of Space Based Augmentation Systems (SB AS) and provide regional augmentation services. In this concept, different GNSSs may be used separately or in combination to determine the location of a UE.

[0060] The barometric pressure sensor method makes use of barometric sensors to determine the vertical component of the position of the UE. The UE measures barometric pressure, optionally aided by assistance data, to calculate the vertical component of its location or to send measurements to the positioning server for position calculation. This method should be combined with other positioning methods to determine the 3D position of the UE.

[0061] The WLAN positioning method makes use of the WLAN measurements (e.g., Access Point (AP) identifiers and optionally other measurements) and databases to determine the location of the UE. The UE measures received signals from WLAN APs, optionally aided by assistance data, to send measurements to the positioning server for position calculation. Using the measurement results and a references database, the location of the UE is calculated. Alternatively, the UE makes use of WLAN measurements and optionally WLAN AP assistance data provided by the positioning server, to determine its location.

[0062] The Bluetooth positioning method makes use of Bluetooth measurements (e.g., beacon identifiers and optionally other measurements) to determine the location of the UE. The UE measures received signals from Bluetooth beacons. Using the measurement results and a references database, the location of the UE is calculated. The Bluetooth methods may be combined with other positioning methods (e.g., WLAN) to improve positioning accuracy of the UE.Docket No. SMM920250193-GR-NP

[0063] TBS comprises a network of ground-based transmitters, broadcasting signals only for positioning purposes. TBS positioning signals include: the MBS signals and (PRS (e.g., see in TS 36.211 V19.1.0). The UE measures received TBS signals, optionally aided by assistance data, to calculate its location or to send measurements to the positioning server for position calculation.

[0064] The motion sensor method makes use of different sensors such as accelerometers, gyros, magnetometers, to calculate the displacement of UE. The UE estimates a relative displacement based upon a reference position and / or reference time. UE sends a report comprising the determined relative displacement which can be used to determine the absolute position. This method should be used with other positioning methods for hybrid positioning.

[0065] Examples described herein generally relate to Location Exposure (e.g., LCS exposure). In 3GPP, mainly SA2 and SA6 are the groups which discuss the LCS exposure. In SA2 (e.g., as discussed in 3GPP TS 23.273 V19.4.0), a location service may be exposed to the authorized control plane Network Function (NF) or the LCS client to obtain the UE location to enable their application and services using the Mobile Terminated Location Request (MT-LR) procedure. For the location service exposed to the Application Function (AF) which is not allowed to directly interact with the Gateway Mobile Location Centre (GMLC) or AMF, Common API Framework (CAPIF) API may be used between Network Exposure Function (NEF) and the AF e.g., as described in clause 6.2.5.1 of TS 23.501 V19.5.0. For an AF not allowed to directly interact with the GMLC or AMF, the LCS service request is sent to NEF using the service-based interface. To support location service exposure through NEF, when NEF receives a LCS service request, it determines (e.g., based on the location accuracy of the QoS requirement, e.g. lower or higher than cell-ID level) whether to invoke the GMLC service or the AMF service for the LCS service request.

[0066] In SA6, the SEAL specifies an LM layer. The SEAL LM layer provides support for vertical industries. The LM server is a functional entity that receives and stores user location information and provides user location information to the vertical application server. The LMS may also acquire location information provided by PLMN operator via T8Docket No. SMM920250193-GR-NPreference point. The LMS acts as CAPIF's API exposing function as specified in 3GPP TS 23.222 V19.7.0. The LMS also supports interactions with the corresponding LMS in distributed SEAL deployments. The Location Management Component / Client (LMC) acts as the application client for location management functions. The LMC interacts with the LMS. The LMC also supports interactions with the corresponding LMC between the two UEs. There are two architecture options for on-network and off-network support.

[0067] Figure 2 illustrates an example of an on-network function model for LM 200 in accordance with aspects of the present disclosure. The on-network function model for LM 200 comprises a UE 210, a 3GPP network system 220, a VAL server(s) 232 and LMS 250. The UE 210 comprises a VAL client(s) 230. The UE 210 further comprises an LMC 240. The LMC 240 communicates with the LMS over an LM-UU reference point. The LMC 240 provides the support for LM functions to the VAL client(s) 230 over an LM-C reference point. The VAL server(s) 232 communicates with the LMS 250 over an LM-S reference point. The LMS 250 communicates with a Service Capability Exposure Function (SCEF) via T8 reference point to obtain location information from the underlying 3 GPP network system 220. The VAL server(s) 232 may be an application specific server (e.g., a Platooning server) or a vertical specific enabler server.

[0068] Figure 3 illustrates an example of an off-network function model for LM 300 in accordance with aspects of the present disclosure. The off-network function model for LM 300 comprises a first UE 310 and a second UE 312. The first UE 310 comprises a first VAL client(s) 330 and a first LMC 340. The first VAL client(s) 330 communicates with the first LMC 340 via a first LM-C reference point. The second UE 312 comprises a second VAL client(s) 332 and a second LMC 342. The second VAL client(s) 332 communicates with the second LMC 342 via a second LM-C reference point. The first VAL client(s) 330 and second VAL client(s) 332 communicate via a VAL-PC5 reference point. The first LMC 340 and second LMC 342 communicate via an LM-PC5 reference point. The first VAL client(s) 330 and second VAL client(s) 332 care part of the VAL. The first LMC 340 and second LMC 342 are part of the SEAL.

[0069] In EDGEAPP [e.g., see 3GPP TS 23.558 V20.0.0] scenarios, an API to be exposed to the edge application may be the Location API. The Edge Enabler Layer (EEL)Docket No. SMM920250193-GR-NPmay provide value-added services when exposing such information to the edge servers. TS 23.558 V20.0.0 discusses an example of the Location API which is provided by the EEL to the edge application servers. The Edge Enabler Server exposes the UE location API to the Edge Application Server in order to support tracking or checking the valid location of the UE. The UE location API exposed by the Edge Enabler Server may rely on the 3 GPP core network capabilities. The Edge Application Server (EAS) may request UE location API for one-time reporting to check current UE location and for continuous reporting to track UE's location. The UE location API supports both request-response for one-time queries (e.g., in order to check UE's current location) as well as subscribe-notify models for providing UE's location to Edge Application Server (EAS) on a continuous basis and enabling the EAS to track UE's location (e.g., as the UE location changes).

[0070] Furthermore, in 3GPP Release 18, an SA6 study on 5G-enabled fused location service capability exposure [e.g., see TR 23.700-96 V18.0.0] studies and evaluates the application architecture aspects and solutions to address potential new and enhanced location capabilities for a vertical application enabler. One of the features related to location fusion (e.g., see TS 23.434 V19.7.0), where the LMS enhanced with the Fuse Location Function (FLF) supports the creation of location profiles for location service at the application enablement layer and the mapping of location profiles to one or more vertical applications. Location profiling is based on the vertical driven hybrid positioning requirements and policies, with attributes as exemplified in Table 4 below. Table 4 is related to Table D-l of TS 23.434 V19.7.0.Docket No. SMM920250193-GR-NPTable 4: Exemplary location profile attributes

[0071] Examples described herein may relate to energy-related Location Service configuration. In SA6 Rel-20, a study on Application Enablement to support Energy Saving (e.g., see TR 23.700-44 VO.2.0) has the following objectives: study the potential requirements for application enablement layer (e.g., Network Slice Capability Enablement (NSCE)) for supporting use cases related to energy savings (e.g., re-map the user / application to the slice, network slice diagnostics enhancement with energy saving information); investigate enhancements of existing procedures to add support for exposure of energy consumption related information to applications; study potential usage and enhancements of SEAL enablers (e.g., Service Enabler Application Layer Distributed Data (SEALDD), Artificial Intelligence Machine Learning Enabler (AIMLE), LM, Application Data Analytics Enabler (ADAE) services) to further optimize energy savings; and study whether and how other working groups (e.g., SA2, SA5) exposure of energy efficiency and energy saving capabilities can be consumed by SA6 enablers (e.g., energy consumption information provided by the Core Network (e.g. Edge Enabler Function (EIF) see TS 23.501 VI 9.5.0) and measurement information exposed by management system (e.g. introduced in TS 28.552 V20.0.0 and TS 28.19.5.0)) to address the above enhancements.

[0072] Key Issue#6 studies whether existing application enablement layer services (e.g., SEALDD, LM, ADAE) may be enhanced to support energy saving of the resourcesDocket No. SMM920250193-GR-NPused by applications. For example, the LM client reports location information and consumes energy. The LM service on the location information collection may be adjusted. For example, adjusting the LCS QoS to reduce energy consumption or switch the LM client location reporting to network location reporting which tends to save energy at the UE side.

[0073] Solution #10 in TR 23.700-44 V0.2.0 proposes to enable the LMS to adjust the location reporting configuration to save the energy consumption for the VAL UE. In this solution, based on the energy related information analysis received from AD AES and the service request from VAL server, the LMS determines the UE location reporting configuration. For example, the LMS may decrease the reporting frequency when the UE’s energy consumption almost reaches its daily maximum, and vice versa. Alternatively, the LMS may send the location reporting when the time point of peak energy consumption is approaching e.g., based on the UE's energy information prediction.

[0074] Examples described herein provide a method to allow the energy-aware configuration and provisioning of LCS via the enablement layer (e.g., LMS, LMC). The method may comprise a first step of obtaining, at a LCS Configuration entity (e.g., LMS, Energy Enabler, AF / NF), a requirement (e.g., a request) from the consumer which may comprise at least one of: an energy saving indicator (e.g., an energy saving criterion); an indication from the LCS consumer that the reporting should be energy-aware (e.g., energy constrained); an energy consumption trigger (e.g., an upper bound for energy consumption, an upper limit for energy consumption) for the VAL UE(s) supporting the location reporting (e.g., the energy consumption trigger may be used for updating the configuration in an energy-aware manner or an energy constrained manner); a policy or requirement (e.g., trigger event-action pair) from the consumer for automatically updating the configuration when the trigger event (e.g., threshold for energy consumption) is met (e.g., the trigger action may comprise at least one of a: change of periodicity of reporting, a change of the accuracy of reporting, a change of the VAL UE performing the location reporting (e.g., if the reporting is for a certain area), the use of sidelink positioning to save energy consumption related to the propagation (e.g., moving from on-network to off-network / Proximity Services (ProSE))); obtaining an indication of the positioning method(s) to be used in association with the energy saving indi cation / criteria for the reporting or the LCSDocket No. SMM920250193-GR-NPprofile requirement (e.g., if the LCS profile is created and known in both the consumer and MNO by a Service Level Agreement (SLA)); or obtaining a time validity and service area for the requirement (e.g., the time validity may be for a reporting configuration expected or predicted at a future time (e.g., using a time horizon)).

[0075] In a second step, the LCS Configuration entity may receive at least one energy related event. The energy related event may comprise at least one of an expected or predicted high energy consumption of one or more VAL UEs of interest; an expected or predicted low energy efficiency of one or more VAL UEs of interest; an expected or predicted high energy consumption of one or more applications (e.g., LMC, VAL Client) of the one or more VAL UEs of interest; an alert indicating high energy consumption for the given LCS service (e.g., entire service comprises the sessions used for location reporting); or an indication of a core network function entering an energy saving state. The network function may be a location function (e.g., LMF) or NWDAF (e.g., for location related analytics).

[0076] The method may further comprise a third step of determining an action for updating an LCS configuration (e.g., an LCS provisioning) based on the energy saving criterion or the indications described above in the first step or second. The update of the LCS configuration tends to reduce the energy consumption of the VAL UE (e.g., VAL client, LMC, LM service).

[0077] The update to the LCS configuration may comprise at least one of adapting (e.g., changing, modifying, updating) the reporting configuration for the location reporting; adapting the LCS QoS / accuracy to reduce the energy consumption associated with the location reporting; adapting the VAL UE of interest for providing location reporting, this may be used in group based communications (e.g. V2X platoon, AGVs) where a different UE may be selected to report location associated with the group (This may be applicable to scenarios where the location reporting is for an entire zone / area and the VAL UE(s) providing the reporting may be updated based on the energy factor); adapting the positioning method(s) for deriving the location reporting from the VAL UE; adapting the LCS profile for the location service and in particular the VAL UE (the LCS profile may be associated with a certain configuration instance (e.g., matching requirements, positioningDocket No. SMM920250193-GR-NPmethods)); or introducing a new LCS profile (e.g., corresponding to the existing LCS profile but with energy constraints (e.g. EE_LCS Profile #x vs LCS Profile #x)); adapting the means of location reporting (e.g., changing to side-link positioning if the VAL LIE of interest is energy constrained), since the energy consumption for the LCS includes UE to Server / Network propagation, using another VAL UE (e.g., in proximity, not energy constrained) to send the reporting to the LMS tends to reduce the energy consumption of the VAL UE initially tasked to provide the location report.

[0078] The method may comprise a fourth step of sending the updated configuration and / or provisioning parameters associated with the determined action to the VAL UE (s) (e.g., LMC, enabler client, VAL client).

[0079] The method may comprise a fifth step of sending the determined action and the updated configuration and / or provisioning parameters to the consumer if these result to changing the LCS QoS / accuracy to the consumer to notify or get confirmation before or after the fourth step.

[0080] Some examples described herein may include techniques to perform the mapping and translation between the Location Service Enabler (LSE) Server and LSE client located within a VAL UE. Some examples described herein may comprise LCS Profile mapping to an energy criteria. Some examples described herein may relate to enhancing the SEAL LMS feature of LCS profiling as in clause 9.3.14 of TS 23.434 V19.7.0, to support the energy related criteria and determination. Table 5 shows an LCS profile mapping table.Docket No. SMM920250193-GR-NPTable 5 LCS profile mapping table.

[0081] Some examples described herein include the translation of a vertical request to a location profile (e.g., LCS profile, location service profile) and the derivation of the requested location information report. The LMS may be configured with a set of LCS profiles.

[0082] Figure 4 illustrates an example of a process flow 400 for location reporting in accordance with aspects of the present disclosure. The process flow 400 may implement or be implemented by aspects of the wireless communication system 100. For example, the process flow 400 may include a VAL Client 430, an LMC 440, a third party location server 452, a 5GC 420, an LMS (e.g., FLF) 450, and a VAL Server 432 which may be one or more examples of devices described herein with reference to Figure 1.

[0083] The process flow 400 may be referred to as a procedure, including one or more operations performed by one or more of the VAL Client 430, the LMC 440, the third party location server 452, the 5GC 420, the LMS (e.g., FLF) 450, and the VAL Server 432.Docket No. SMM920250193-GR-NP

[0084] In the following description of the process flow 400, the operations or signalling performed between one or more of the VAL Client 430, the LMC 440, the third party location server 452, the 5GC 420, the LMS (e.g., FLF) 450, and the VAL Server 432 may be performed or signalled (e.g., transmitted, received) in a different order than the example order shown, or the operations or signalling performed by one or more of the VAL Client 430, the LMC 440, the third party location server 452, the 5GC 420, the LMS (e.g., FLF) 450, and the VAL Server 432 may be performed or signalled (e.g., transmitted, received) in different orders or at different times. Some operations or signalling may also be omitted from the process flow 400. Additionally, although some operations or signalling may be shown to occur at different times, these operations or signalling may occur at the same time or in overlapping time periods.

[0085] A location reporting requirement may comprise at least one of: an energy saving indicator; an indicator for energy-aware reporting; an energy consumption trigger; a requirement for updating the location reporting configuration; an indicator for a positioning method; an indicator of a time validity of the location reporting requirement; or an indicator of a service area for the location reporting requirement.

[0086] An energy saving indicator may comprise an energy saving criterion. The indicator for energy-aware reporting may comprise an indication from the consumer (e.g., LCS consumer) for reporting that is energy-aware. The energy consumption trigger may comprise an upper bound (e.g., an upper limit) for the UE supporting the location reporting. The energy consumption trigger may be used for updating the location reporting configuration in an energy-aware manner. The requirement for updating the location reporting configuration may comprise a policy or requirement (e.g., trigger event-action pair) from the consumer for automatically updating the configuration when the trigger event (e.g., threshold for energy consumption) is met.

[0087] An energy management criterion may comprise at least one of: an energy saving indicator; a high energy consumption indicator; a low energy efficiency indicator; a low battery level indicator; or a high battery drain indicator. The energy management criterion may relate to at least one of: an application of the UE; a location management client at the UE; or a vertical location service running at the UE.Docket No. SMM920250193-GR-NP

[0088] Process flow 400 starts at step 471. The LMS 450 receives a location reporting trigger from the VAL Server 432 and activates a location reporting procedure e.g., see in clause 9.3.5.

[0089] The location reporting trigger may comprise at least one of: an energy saving indicator (e.g., energy saving criteria); an indication from the LCS consumer for reporting to be energy-aware (e.g., energy constrained); an energy consumption trigger (e.g., an energy consumption upper bound, upper limit) for the VAL UE(s) supporting the location reporting, the energy consumption trigger may be used for updating the configuration in an energy-aware / manner; a policy or requirement (e.g., trigger event-action pair) from the consumer for automatically updating the configuration when the trigger event is met (e.g., reaching the threshold for energy consumption), the policy may involve performing a trigger action, the trigger action may comprise at least one of: changing the periodicity of reporting, changing the accuracy of reporting, change of VAL UE performing the location reporting (e.g., if the location reporting is for a certain area), or using sidelink positioning (which tends to save energy consumption related to the propagation) (e.g., moving from on- network to off-network / ProSE); an indication of the positioning method(s) for the energy saving indicator for the reporting or the LCS profile requirement (e.g., the LCS profiles may be created and known to the consumer and MNO by SLA); or a time validity and service area for which the requirement applies, the time validity may be for a reporting an expected or predicted configuration (e.g., using a time horizon).

[0090] In step 472a, the FLF in the LMS 450 determines (e.g., identifies, receives) a mapping of the vertical location services for an LCS profile based on the location request information. The LCS profiles and the location capability may be of the VAL UE which registered to the LMS 450 previously. If the LCS profile requirement is already indicated in step 471, the mapping uses this requirement as a basis for selecting / confirming the profile.

[0091] In step 472b, the FLF in the LMS 450 determines a mapping (or update of the mapping) of the vertical location services to an LCS profile (e.g., a new LCS profile or switching to different LCS profile) based on the energy criteria / requirement as in step 471. To determine the mapping, a possible input may be an energy related event (e.g., based on a subscription, query or a request) from the VAL UE or core network side (e.g., based on anDocket No. SMM920250193-GR-NPindication from the LCS consumer for the reporting to be energy-aware, the indication may be at least one of 1) an expected or predicted high energy consumption of one or more VAL UEs of interest, 2) an expected or predicted low energy efficiency of one or more VAL UEs of interest, 3) an expected or predicted high energy consumption of one or more applications (e.g., LMC 440, VAL Client 430) of the one or more VAL UEs of interest, 4) an alert indicating high energy consumption for the given LCS service (e.g., if the entire service comprises the sessions used for location reporting), or 5) an indication of a core network function entering an energy saving state, where the network function is a location function (e.g. LMF) or NWDAF (e.g., for location related analytics).

[0092] The FLF of the LMS 450 may also determine a mapping between the determined LCS profile and the energy saving indicator and / or an energy rating / weight / ranking for the LCS profile.

[0093] In step 473a, the LMS 450 requests from the LMC 440 (e.g., sends or transmits a request to the LMC 440) the location information of the target VAL UE (comprising the VAL Client 430 and LMC 44) optionally with the requested location information (e.g., access type, positioning method) based on the determined LCS profiles configured in the LMS 450; e.g., obtained in step 472a.

[0094] As part of this request, the LMS 450 sends (e.g., transmits) to the LMC 440 the alternative or energy-aware LCS profile or location information, which may be used to update the location reporting (e.g., accuracy, periodicity) or for allowing the VAL UE to change the location reporting attributes (e.g., if the VAL UE determines that energy consumption is high or the energy criteria is met). The LMS 450 may include the configuration of the energy criteria / consumption threshold in the request. The LMC 440 may locally update the location reporting configuration based on the request.

[0095] In step 473b, the LMC 440 responds (e.g., sends, transmits) to the LMS (450) a location report based on the request. If the LMC 440 locally updates the LCS profile in the case of an energy event at the VAL UE side, the LMC 440 provides the notification for this update to the LMS 450.Docket No. SMM920250193-GR-NP

[0096] In step 474, the LMS 450 performs a location information request to one or more of the following (based on the LCS profile): to GMLC directly or via NEF (e.g., see in TS 23.273 VI 9.4.0), acting as AF; or to the third party location server 452. The LMS 450 retrieves location information reports per location profile and vertical application (using the energy criteria or the LCS profiles).

[0097] In step 475, the FLF of the LMS 450 calculates the location information based on the location reports from steps 473-474 and checks (e.g., determines) whether the location reports fulfil the LCS profile requirements.

[0098] In steps 476-477, if the requirements are not fulfilled, the LMS 450 may repeat steps 473-475 iteratively to request location information and re-check whether the requirements are met or not.

[0099] In step 478, if the requirements are fulfilled, the LMS 450 sends (e.g., transmits) the location information report to the VAL Server 432.

[0100] Some examples described herein include positioning method / attributes fine tuning to meet an energy criteria. Some examples described herein illustrate a high-level procedure of an LMS for adjusting the location reporting configuration to reduce energy consumption. This may involve an enhancement to Solution #10 in TR 23.700-44 V0.2.0.

[0101] In step 1, the VAL server sends (e.g., transmits) a location reporting trigger to the LMS to activate a location reporting procedure for obtaining the location information of LMC with the parameters defined in clause 9.3.2.4 of 3GPP TS 23.434

[0014] , The location reporting trigger is periodical and the request also includes the energy saving indicator which means the LMS may consider saving the energy when performing the location services for the target UE.

[0102] The location reporting trigger may include at least one of: an energy saving indicator / criteria; an indication from the LCS consumer that the reporting needs to be energy-aware / constrained an energy consumption trigger / upper bound for the VAL UE(s) supporting the location reporting, where this trigger may be used for updating the configuration in an energy-aware / constrained manner; a policy or requirement (e.g., trigger event-action pair) from the consumer for automatically updating the configuration when theDocket No. SMM920250193-GR-NPtrigger event (e.g., threshold for energy consumption) is met. Such trigger action may be at least one of: the change of periodicity of reporting or the accuracy of reporting, the change of VAL UE performing the location reporting if this reporting is for a certain area, or the use of sidelink positioning to save energy consumption related to the propagation (e.g., moving from on-network to off-network / ProSE); an indication of the positioning method(s) to be used in association with the energy saving indication / criteria for the reporting or the LCS profile requirement (e.g., the LCS profiles may be created and known in both the consumer and MNO by SLA); or a time validity and service area for which the requirement applies. Such time validity may be for a requirement for a reporting configuration which is expected or predicted in future time (e.g., a time horizon may be provided).

[0103] In step 2, upon receiving the service request, the LMS subscribes the energy information analysis from the AD AES for the target UE, following the procedure as described in clause 6.10.1.1.

[0104] The AD AES transmits an indication associated with the energy related information analysis for the target UE, to the LMS, and may include the energy information statistic (e.g., maximum / average / minimum energy consumption information over a certain period of time), energy information predication (e.g., the time point of peak energy consumption), etc.

[0105] In step 3, based on the energy related information analysis received from AD AES and the service request from VAL server, the LMS determines the UE location reporting configuration. For example, the LMS may decrease the reporting frequency when the UE’s energy consumption almost reaches its daily maximum, and vice versa. Or the LMS may send the location reporting when the time point of peak energy consumption is coming based on the UE's energy information prediction.

[0106] In step 3b, the LMS determines a further action (which is different to changing the reporting frequency) based on the energy criteria / requirement as in step 1. The further action may comprise at least one of: a) adapting the LCS QoS / accuracy to reduce the energy consumption associated with the location reporting; b) adapting the VAL UE of interest for providing location reporting (this may be used in group based communications (e.g. V2X platoon, AGVs) where a different UE may be selected to report locationDocket No. SMM920250193-GR-NPassociated with the group) (this may be also applicable to scenarios where the location reporting is for an entire zone / area, and the VAL UE(s) providing the reporting may be updated based on the energy factor); c) adapting the positioning method (s) to be used for deriving the location reporting from the VAL UE; d) adapting the LCS profile for the location service and in particular the VAL UE, where the profile is associated with a certain configuration instance (matching requirements and positioning methods); e). introducing a new LCS profile which may be equivalent to the existing LCS profile but with energy constraints (e.g. EE LCS Profile #x vs LCS Profile #x); f) adapting the means of location reporting and in particular changing to side-link positioning if the VAL UE of interest is energy constrained (this may help since the energy consumption for the LCS comprises the UE to Server / Network propagation, and using another VAL UE which is in proximity (and not energy constrained) to send the reporting to the LMS may reduce the energy consumption for the VAL UE who is initially tasked to provide the location report).

[0107] For the determination of the further action, a possible input may be an energy related event (e.g., based on subscription or query / request) from the VAL UE or core network side (e.g., an indication from the LCS consumer for the reporting to be energy- aware). The input may comprise at least one of: 1) expected or predicted high energy consumption of one or more VAL UEs of interest, 2) expected or predicted low energy efficiency of one or more VAL UEs of interest, 3) expected or predicted high energy consumption of one or more applications (e.g., LMC, VAL Client) of the one or more VAL UEs of interest, 4) an alert indicating high energy consumption for the given LCS service (entire service comprises the sessions used for location reporting), or 5) an indication of a core network function entering an energy saving state, where the network function is a location function (e.g. LMF) or NWDAF (e.g,, for location related analytics).

[0108] In step 4, the LMS may interact with the VAL server regarding the determined UE location reporting configuration and send (e.g., transmit) the adaptive location reporting configuration provisioning messages e.g., see in clause 9.3.20 of 3GPP TS 23.434 V19.7.0

[0014] , For certain actions (e.g. if these result to changing the LCS QoS / accuracy to the consumer or changing the VAL UE of interest), a notification may be required or confirmation by the VAL Server.Docket No. SMM920250193-GR-NP

[0109] In step 5, if the VAL Server approves the suggested location reporting configuration, the LMS sends such configurations to the LMC e.g., see in clause 9.3.3 of 3GPP TS 23.434 V19.7.0

[0014] , If the VAL Server rejects the suggested location configuration, the LMS may discard the configuration.

[0110] In step 6, considering the received location reporting configuration, the LMC reports the location information to the LMS dynamically when the location reporting trigger is met.[OHl] In step 7, the LMS reports the received location information for the target UE to the VAL Server.

[0112] Figure 5 illustrates an example of a UE 500 in accordance with aspects of the present disclosure. The UE 500 may be a VAL UE as described herein. The UE 500 may include a processor 502, a memory 504, a controller 506, and a transceiver 508. The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0113] The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0114] The processor 502 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 502 may be configured to operate the memory 504. In some other implementations, the memory 504 may be integrated into the processor 502. The processor 502 may be configured to execute computer-readable instructions stored in the memory 504 to cause the UE 500 to perform various functions of the present disclosure.Docket No. SMM920250193-GR-NP

[0115] The memory 504 may include volatile or non-volatile memory. The memory 504 may store computer-readable, computer-executable code including instructions when executed by the processor 502 cause the UE 500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 504 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0116] In some implementations, the processor 502 and the memory 504 coupled with the processor 502 may be configured to cause the UE 500 to perform one or more of the functions described herein (e.g., executing, by the processor 502, instructions stored in the memory 504). For example, the processor 502 may support wireless communication at the UE 500 in accordance with examples as disclosed herein. The UE 500 may be configured to support a means for receiving, from a second network entity, a location reporting requirement, wherein the location reporting requirement is for reporting a location of a UE according to an energy management criterion for the UE; and transmitting, to the UE, a location reporting configuration for the UE, wherein the location reporting configuration is based on the energy management criterion.

[0117] The controller 506 may manage input and output signals for the UE 500. The controller 506 may also manage peripherals not integrated into the UE 500. In some implementations, the controller 506 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 506 may be implemented as part of the processor 502.

[0118] In some implementations, the UE 500 may include at least one transceiver 508. In some other implementations, the UE 500 may have more than one transceiver 508. The transceiver 508 may represent a wireless transceiver. The transceiver 508 may include one or more receiver chains 510, one or more transmitter chains 512, or a combination thereof.

[0119] A receiver chain 510 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 510Docket No. SMM920250193-GR-NPmay include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 510 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 510 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 510 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0120] A transmitter chain 512 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 512 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 512 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 512 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0121] Figure 6 illustrates an example of a processor 600 in accordance with aspects of the present disclosure. The processor 600 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 600 may include a controller 602 configured to perform various operations in accordance with examples as described herein. The processor 600 may optionally include at least one memory 604, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 600 may optionally include one or more arithmetic-logic units (ALUs) 606. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0122] The processor 600 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining,Docket No. SMM920250193-GR-NPidentifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 600) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0123] The controller 602 may be configured to manage and coordinate various operations (e.g., signalling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 600 to cause the processor 600 to support various operations in accordance with examples as described herein. For example, the controller 602 may operate as a control unit of the processor 600, generating control signals that manage the operation of various components of the processor 600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0124] The controller 602 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 604 and determine subsequent instruction(s) to be executed to cause the processor 600 to support various operations in accordance with examples as described herein. The controller 602 may be configured to track memory address of instructions associated with the memory 604. The controller 602 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 602 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 600 to cause the processor 600 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 602 may be configured to manage flow of data within the processor 600. The controller 602 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 600.

[0125] The memory 604 may include one or more caches (e.g., memory local to or included in the processor 600 or other memory, such RAM, ROM, DRAM, SDRAM,Docket No. SMM920250193-GR-NPSRAM, MRAM, flash memory, etc. In some implementations, the memory 604 may reside within or on a processor chipset (e.g., local to the processor 600). In some other implementations, the memory 604 may reside external to the processor chipset (e.g., remote to the processor 600).

[0126] The memory 604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 600, cause the processor 600 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 602 and / or the processor 600 may be configured to execute computer-readable instructions stored in the memory 604 to cause the processor 600 to perform various functions. For example, the processor 600 and / or the controller 602 may be coupled with or to the memory 604, the processor 600, the controller 602, and the memory 604 may be configured to perform various functions described herein. In some examples, the processor 600 may include multiple processors and the memory 604 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0127] The one or more ALUs 606 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 606 may reside within or on a processor chipset (e.g., the processor 600). In some other implementations, the one or more ALUs 606 may reside external to the processor chipset (e.g., the processor 600). One or more ALUs 606 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 606 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 606 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 606 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 606 to handle conditional operations, comparisons, and bitwise operations.Docket No. SMM920250193-GR-NP

[0128] The processor 600 may support wireless communication in accordance with examples as disclosed herein. The processor 600 may be configured to support a means for receiving, from a second network entity, a location reporting requirement, wherein the location reporting requirement is for reporting a location of a UE according to an energy management criterion for the UE; and transmitting, to the UE, a location reporting configuration for the UE, wherein the location reporting configuration is determined according to the energy management criterion. The processor 600 may be configured to or operable to support a means for receiving, from a first network entity, a location reporting configuration, wherein the location reporting configuration is for reporting a location of the UE, wherein the location reporting configuration is determined according to an energy management criterion.

[0129] Figure 7 illustrates an example of a NE 700 in accordance with aspects of the present disclosure. The NE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0130] The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0131] The processor 702 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 702 may be configured to operate the memory 704. In some other implementations, the memory 704 may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in the memory 704 to cause the NE 700 to perform various functions of the present disclosure.Docket No. SMM920250193-GR-NP

[0132] The memory 704 may include volatile or non-volatile memory. The memory 704 may store computer-readable, computer-executable code including instructions when executed by the processor 702 cause the NE 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 704 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0133] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the NE 700 to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704). For example, the processor 702 may support wireless communication at the NE 700 in accordance with examples as disclosed herein. The NE 700 may be configured to support a means for receiving, from a first network entity, a location reporting configuration, wherein the location reporting configuration is for reporting a location of the UE, wherein the location reporting configuration is determined according to an energy management criterion.

[0134] The controller 706 may manage input and output signals for the NE 700. The controller 706 may also manage peripherals not integrated into the NE 700. In some implementations, the controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 706 may be implemented as part of the processor 702.

[0135] In some implementations, the NE 700 may include at least one transceiver 708. In some other implementations, the NE 700 may have more than one transceiver 708. The transceiver 708 may represent a wireless transceiver. The transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.

[0136] A receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 710 may include one or more antennas for receive the signal over the air or wireless medium.Docket No. SMM920250193-GR-NPThe receiver chain 710 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 710 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 710 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0137] A transmitter chain 712 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 712 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 712 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0138] Figure 8 illustrates a flowchart of a method 800 in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.

[0139] At 802, the method 800 may include receiving, from a first network entity, a location reporting configuration, wherein the location reporting configuration is for reporting a location of the UE, wherein the location reporting configuration is determined according to an energy management criterion. The operations of 802 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 802 may be performed by a UE as described with reference to Figure 5.

[0140] It should be noted that the method 800 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.Docket No. SMM920250193-GR-NP

[0141] Figure 9 illustrates a flowchart of a method 900 in accordance with aspects of the present disclosure. The operations of the method 900 may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0142] At 902, the method 900 may include receiving, from a second network entity, a location reporting requirement, wherein the location reporting requirement is for reporting a location of a UE according to an energy management criterion for the UE. The operations of 902 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 902 may be performed by a NE as described with reference to Figure 7.

[0143] At 904, the method 900 may include transmitting, to the UE, a location reporting configuration for the UE, wherein the location reporting configuration is based on the energy management criterion. The operations of 904 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 904 may be performed by a NE as described with reference to Figure 7.

[0144] It should be noted that the method 900 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0145] There is provided herein a first network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive, from a second network entity, a location reporting requirement, wherein the location reporting requirement is for reporting a location of a UE according to an energy management criterion for the UE; and transmit, to the UE, a location reporting configuration for the UE, wherein the location reporting configuration is determined according to the energy management criterion. Such a first network entity tends to allow for improved adaptation of location reporting to take account of energy consumption or efficiency within a wireless communication system.Such a first network entity tends to reduce the complexity of location reporting; particularly for location services with a wide variety of use cases or scenarios.Docket No. SMM920250193-GR-NP

[0146] The location reporting configuration may be determined according to the energy management criterion. The location reporting configuration may be determined based on the energy management criterion.

[0147] The first network entity may be part of a wireless communication network. The wireless communication network may comprise a wireless communication system. The wireless communication network may comprise a 5G network. The wireless communication network may comprise a 6G network. The first network entity may comprise an LMS. The first network entity may comprise an LCS configuration entity. The second network entity may be part of the wireless communication network. The second network entity may comprise a VAL server. The UE may comprise a VAL UE. The UE may comprise a VAL client. The LE may comprise a location management client. The LE may comprise a location management service.

[0148] The energy management criterion may relate to the management of LE power consumption. The energy management criterion may relate to the management of LE power consumption during location reporting. The energy management criterion may comprise energy consumption of the LE. The energy management criterion may comprise a battery level of the LE. The energy management criterion may comprise an energy efficiency of the LE. The energy management criterion may comprise an energy parameter. The energy management criterion may comprise an energy criterion. The energy management criterion excludes a frequency of reporting the location of the LE.

[0149] The location reporting configuration may be further based on a location reporting frequency. The location reporting configuration may be further determined according to the location reporting frequency. The location reporting configuration may be further determined based on the location reporting frequency. Where the location reporting configuration is further determined according to a location reporting frequency, the location reporting configuration is determined according to both the energy management criterion and the location reporting frequency.

[0150] The location reporting requirement may comprise at least one of an energy saving indicator; an indicator for energy-aware reporting; an energy consumption trigger; a requirement for updating the location reporting configuration; an indicator for a positioningDocket No. SMM920250193-GR-NPmethod; an indicator of a time validity of the location reporting requirement; or an indicator of a service area for the location reporting requirement.

[0151] The energy saving indicator may comprise an energy saving criterion. The indicator for energy-aware reporting may comprise an indication from the consumer (e.g., LCS consumer) for reporting that is energy-aware. The energy consumption trigger may comprise an upper bound (e.g., an upper limit) for the UE supporting the location reporting. The energy consumption trigger may be used for updating the location reporting configuration in an energy-aware manner. The requirement for updating the location reporting configuration may comprise a policy or requirement (e.g., trigger event-action pair) from the consumer for automatically updating the configuration when the trigger event (e.g., threshold for energy consumption) is met.

[0152] The energy management criterion may comprise at least one of: an energy saving indicator; a high energy consumption indicator; a low energy efficiency indicator; a low battery level indicator; or a high battery drain indicator. The energy management criterion may relate to at least one of: an application of the UE; a location management client at the UE; or a vertical location service running at the UE.

[0153] The at least one processor may be further configured to cause the first network entity to: determine the location reporting configuration for the UE according to the energy management criterion. To determine the location reporting configuration, the at least one processor may be configured to cause the first network entity to: map a vertical location service to a location service profile in accordance with the energy management criterion.

[0154] The location reporting configuration may comprise at least one of: QoS for reporting the location of the UE according to the energy management criterion; an accuracy for reporting the location of the UE according to the energy management criterion; determining a UE from a group of UEs for reporting the location of the UE; a positioning method; a location service profile according to the energy management criterion; or a signalling method for reporting the location of the UE. The signalling method for reporting the location of the UE may comprise sidelink signalling. The positioning method may comprise at least one of: DL-TDoA, DL-AoD, Multi-RTT, E-CID, NR E-CID, UL-TDoA,Docket No. SMM920250193-GR-NPUL-AoA, GNSS, barometric pressure sensor positioning, WLAN positioning, Bluetooth positioning, TBS positioning, or motion sensor positioning.

[0155] The at least one processor may be further configured to cause the first network entity to: transmit, to the second network entity, a request for confirmation of a change to a vertical location service requirement or mapping to a location profile. The at least one processor may be further configured to cause the first network entity to: transmit, to the UE, an indication of a permission to locally update the location reporting configuration based on the energy management criterion. The permission to locally update the location reporting configuration may be a permission for the UE to change the reporting configuration based on the energy management criterion.

[0156] Transmitting, to the second network entity, the request for confirmation of a change to a vertical location service requirement or mapping to a location profile may be part of a negotiation process with the second network entity. The negotiation process may comprise requesting the confirmation from the second network entity on the expected change of the vertical location service requirement and / or the mapping to a location profile. The vertical location service requirement may be a requirement for the network’s location capability e.g., accuracy, latency, update frequency, reliability, coverage, or triggering conditions. The vertical location service requirement may relate to how the SEAL, VAL, and LCS functions expose and deliver positioning information.

[0157] There is further provided herein a method performed or performable by a first network entity, the method comprising: receiving, from a second network entity, a location reporting requirement, wherein the location reporting requirement is for reporting a location of a UE according to an energy management criterion for the UE; and transmitting, to the UE, a location reporting configuration for the UE, wherein the location reporting configuration is determined according to the energy management criterion. Such a method performed by the first network entity tends to allow for improved adaptation of location reporting to take account of energy consumption or efficiency within a wireless communication system. Such a method performed or performable by the first network entity tends to reduce the complexity of location reporting; particularly for location services with a wide variety of use cases or scenarios.Docket No. SMM920250193-GR-NP

[0158] The location reporting configuration may be further determined according to a location reporting frequency. The location reporting requirement may comprise at least one of an energy saving indicator; an indicator for energy-aware reporting; an energy consumption trigger; a requirement for updating the location reporting configuration; an indicator for a positioning method; an indicator of a time validity of the location reporting requirement; or an indicator of a service area for the location reporting requirement.

[0159] The energy management criterion may comprise at least one of an energy saving indicator; a high energy consumption indicator; a low energy efficiency indicator; a low battery level indicator; or a high battery drain indicator. The energy management criterion may relate to at least one of an application of the UE; a location management client at the UE; or a vertical location service running at the UE.

[0160] The method may further comprise determining the location reporting configuration for the UE according to the energy management criterion. Determining the location reporting configuration may comprises mapping a vertical location service to a location service profile in accordance with the energy management criterion.

[0161] The location reporting configuration may comprise at least one of QoS for reporting the location of the UE according to the energy management criterion; an accuracy for reporting the location of the UE according to the energy management criterion; determining a UE from a group of UEs for reporting the location of the UE; a positioning method; a location service profile according to the energy management criterion; or a signalling method for reporting the location of the UE.

[0162] The signalling method for reporting the location of the UE may comprise sidelink signalling. The positioning method may comprise at least one of DL-TDoA, DL- AoD, Multi-RTT, E-CID, NR E-CID, UL-TDoA, UL-AoA, GNSS, barometric pressure sensor positioning, WLAN positioning, Bluetooth positioning, TBS positioning, or motion sensor positioning.

[0163] The method may further comprise transmitting, to the second network entity, a request for confirmation of a change to a vertical location service requirement or mapping to a location profile. The method may further comprise transmitting, to the UE, anDocket No. SMM920250193-GR-NPindication of a permission to locally update the location reporting configuration based on the energy management criterion.

[0164] There is further provided herein a UE for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive, from a first network entity, a location reporting configuration, wherein the location reporting configuration is for reporting a location of the UE, wherein the location reporting configuration is determined according to an energy management criterion. Such a UE tends to allow for improved adaptation of location reporting to take account of energy consumption or efficiency within a wireless communication system. Such a UE tends to reduce the complexity of location reporting; particularly for location services with a wide variety of use cases or scenarios.

[0165] The at least one processor may be further configured to cause the UE to report a location of the UE in accordance with the location reporting configuration. Reporting the location of the UE in accordance with the location reporting configuration may be in response to the UE receiving, from the first network entity, the location reporting configuration. The location of the UE may comprise at least one of: latitude, longitude, altitude, uncertainty values, timestamp, velocity, heading, or optional metadata. The optional metadata may be for the network to interpret or refine the location of the UE.

[0166] The location reporting configuration may be further determined according to a location reporting frequency. The energy management criterion comprises at least one of: an energy saving indicator; a high energy consumption indicator; a low energy efficiency indicator; a low battery level indicator; or a high battery drain indicator. The energy management criterion may relate to at least one of: an application of the UE; a location management client at the UE; or a vertical location service running at the UE. The location reporting configuration may comprise at least one of: a QoS for reporting the location of the UE according to the energy management criterion; an accuracy for reporting the location of the UE according to the energy management criterion; determining a UE from a group of UEs for reporting the location of the UE; a positioning method; a location service profile according to the energy management criterion; or a signalling method for reporting the location of the UE. The method may further comprise receiving, from the first networkDocket No. SMM920250193-GR-NPentity, an indication of a permission to locally update the location reporting configuration based on the energy management criterion.

[0167] There is further provided herein a method performed or performable by a user equipment, UE, the method comprising: receiving, from a first network entity, a location reporting configuration, wherein the location reporting configuration is for reporting a location of the UE, wherein the location reporting configuration is determined according to an energy management criterion. Such a method performed by the UE tends to allow for improved adaptation of location reporting to take account of energy consumption or efficiency within a wireless communication system. Such a method performed or performable by the UE tends to reduce the complexity of location reporting; particularly for location services with a wide variety of use cases or scenarios.

[0168] The location reporting configuration may be further determined according to a location reporting frequency. The energy management criterion may comprise at least one of: an energy saving indicator; a high energy consumption indicator; a low energy efficiency indicator; a low battery level indicator; or a high battery drain indicator.

[0169] There is further provided herein a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a first network entity, a location reporting configuration, wherein the location reporting configuration is for reporting a location of the UE, wherein the location reporting configuration is determined according to an energy management criterion. Such a processor tends to allow for improved adaptation of location reporting to take account of energy consumption or efficiency within a wireless communication system. Such a processor tends to reduce the complexity of location reporting; particularly for location services with a wide variety of use cases or scenarios.

[0170] Examples describe herein relate to how to adapt the configuration of location reporting from a VAL UE given the expected or actual energy consumption, battery level, or energy efficiency for the entire UE, per app or per session of the UE.

[0171] Examples described herein provide a mechanism that takes account energy consumption or efficiency of the VAL UE for provisioning / configuring location reportingDocket No. SMM920250193-GR-NPtowards the server / network. In some examples described herein, he LCS profile [which may enclose a set of attributes to satisfy the specific requirements of use cases and / or application service across MNO(s), verticals and third party operators] may be enhanced to consider the energy factor. Previous solutions only consider the configuration of the location reporting frequency as part of the energy-aware configuration.

[0172] Some examples described herein relate to enhancing the SEAL LMS feature of LCS profiling as in clause 9.3.14 of TS 23.434 V19.7.0, to support the energy related criteria and determination. Some examples described herein describe a high-level procedure of the LMS for adjusting the location reporting configuration to save the energy consumption. This is an enhancement to Solution #10 as in TR 23.700-44 VO.2.0.

[0173] There is further provided herein a method for provisioning a vertical location service using energy criteria, the method comprising: receiving a requirement for providing location reporting associated with at least one UE, wherein the requirement comprises an energy parameter, configuring at least one location reporting parameter, based on the received requirement and in particular the received energy parameter, and sending the configured at least one location reporting parameter to at least one application.

[0174] The requirement may comprise at least one of an energy saving indicator / criteria, an indication from the LCS consumer that the reporting needs to be energy-aware / constrained, an energy consumption trigger for the UE(s) supporting the location reporting, a policy or requirement from the consumer for automatically updating the configuration upon meeting an energy consumption threshold, an indication of the positioning method(s) to be used in association with the energy criteria / parameter for the reporting, or a time validity and a service area for which the requirement applies.

[0175] The energy parameter may comprise an energy saving indicator, a high energy consumption indicator, a low energy efficiency indicator, a low battery level indicator, ahigh battery drain indicator for the at least one UE. The energy parameter may be set per application of the UE or for a location management client at the UE or a for a vertical location service running at the UE. The method may further comprise determining to configure at least one location reporting parameter, wherein the determination comprisesDocket No. SMM920250193-GR-NPmapping of the vertical location service to a location service profile using the energy criteria.

[0176] The method may further comprise obtaining an energy event prior configuring the location reporting, wherein this energy event is one or more of: an expected or predicted high energy consumption of one or more VAL UEs of interest, an expected or predicted low energy efficiency of one or more VAL UEs of interest, an expected or predicted high energy consumption of one or more applications (e.g., LMC, VAL Client) of the one or more VAL UEs of interest, an alert indicating high energy consumption for the given LCS service (entire service comprises the sessions used for location reporting), or an indication of a core network function entering an energy saving state, where the network function is a location function (e.g. LMF) or NWDAF (e.g., for location related analytics).

[0177] The configuration and / or location reporting parameter may comprise an action from the following: adapting the LCS QoS / accuracy to reduce the energy consumption associated with the location reporting, adapting the VAL UE of interest for providing location reporting, adapting the positioning method (s) to be used for deriving the location reporting from the VAL UE, adapting the LCS profile for the location service and in particular the VAL UE, where the profile is associated with a certain configuration instance (e.g., matching requirements and positioning methods), introducing a new LCS profile which may be equivalent to the existing LCS profile but with energy constraints, or adapting the means of location reporting and in particular changing to side-link positioning if the VAL UE of interest is energy constrained.

[0178] The method may further comprise negotiating with the consumer [e.g., VAL server] the configured location reporting parameter, wherein negotiating involves requesting the confirmation from the consumer on the expected change of vertical location service requirements and / or the mapping to a location profile. The method may further comprise applying / executing the location reporting based on the configured location reporting parameter. The method may further comprise providing to the at least one UE permission and capability to locally update the configuration of the location reporting based on the energy criteria.Docket No. SMM920250193-GR-NP

[0179] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0180] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.Docket No. SMM920250193-GR-NP

Claims

CLAIMSWhat is claimed is:

1. A first network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive, from a second network entity, a location reporting requirement, wherein the location reporting requirement is for reporting a location of a user equipment, UE, according to an energy management criterion for the UE; and transmit, to the UE, a location reporting configuration for the UE, wherein the location reporting configuration is based on the energy management criterion.

2. The first network entity of claim 1, wherein the location reporting configuration is further based on a location reporting frequency.

3. The first network entity of claim 1 or claim 2, wherein the location reporting requirement comprises at least one of: an energy saving indicator; an indicator for energy-aware reporting; an energy consumption trigger; a requirement for updating the location reporting configuration; an indicator for a positioning method; an indicator of a time validity of the location reporting requirement; or an indicator of a service area for the location reporting requirement.

4. The first network entity of any one of claims 1 to 3, wherein the energy management criterion comprises at least one of: an energy saving indicator; a high energy consumption indicator; a low energy efficiency indicator;Docket No. SMM920250193-GR-NPa low battery level indicator; or a high battery drain indicator.

5. The first network entity of any one of claims 1 to 4, wherein the energy management criterion relates to at least one of an application of the UE; a location management client at the UE; or a vertical location service running at the UE.

6. The first network entity of any one of claims 1 to 5, wherein the at least one processor is further configured to cause the first network entity to: determine the location reporting configuration for the UE according to the energy management criterion.

7. The first network entity of claim 6, wherein to determine the location reporting configuration, the at least one processor is configured to cause the first network entity to: map a vertical location service to a location service profile in accordance with the energy management criterion.

8. The first network entity of any one of claims 1 to 7, wherein the location reporting configuration comprises at least one of: a quality of service, QoS for reporting the location of the UE according to the energy management criterion; an accuracy for reporting the location of the UE according to the energy management criterion; determining a UE from a group of UEs for reporting the location of the UE; a positioning method; a location service profile according to the energy management criterion; or a signalling method for reporting the location of the UE.Docket No. SMM920250193-GR-NP9. The first network entity of any one of claims 1 to 8, wherein the at least one processor is further configured to cause the first network entity to: transmit, to the second network entity, a request for confirmation of a change to a vertical location service requirement or mapping to a location profile.

10. The first network entity of any one of claims 1 to 9, wherein the at least one processor is further configured to cause the first network entity to: transmit, to the UE, an indication of a permission to locally update the location reporting configuration based on the energy management criterion.

11. A method performed or performable by a first network entity, the method comprising: receiving, from a second network entity, a location reporting requirement, wherein the location reporting requirement is for reporting a location of a user equipment, UE, according to an energy management criterion for the UE; and transmitting, to the UE, a location reporting configuration for the UE, wherein the location reporting configuration is determined according to the energy management criterion.

12. A user equipment, UE, for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive, from a first network entity, a location reporting configuration, wherein the location reporting configuration is for reporting a location of the UE, wherein the location reporting configuration is determined according to an energy management criterion.

13. The UE of claim 12, wherein the location reporting configuration is further determined according to a location reporting frequency.Docket No. SMM920250193-GR-NP14. The UE of any one of claims 12 or 13, wherein the energy management criterion comprises at least one of: an energy saving indicator; a high energy consumption indicator; a low energy efficiency indicator; a low battery level indicator; or a high battery drain indicator.

15. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a first network entity, a location reporting configuration, wherein the location reporting configuration is for reporting a location of a user equipment, UE, wherein the location reporting configuration is determined according to an energy management criterion.Docket No. SMM920250193-GR-NP

Images