Method and apparatus for supporting location service for multiple user equipment sharing same location in a wireless communication system

Abstract

The disclosure relates to a fifth generation (5G) or sixth generation (6G) communication system for supporting higher data rates. Embodiments herein provide a method and system for handling location service support for multiple UE sharing same location. The solution includes detecting, by location management client (100) of a first UE (105), whether a second UE (106) is in proximity to the first UE based on the location report. The location management client of a first UE generates a location reuse request message by adding information to enable the reuse of location of the first UE for the second UE, when the second UE is in proximity to the first UE. If the second UE is not in the proximity, location reuse request message includes information to disable the reuse of location of the first UE for the second UE. The location management client of the first UE transmits the location reuse request message to location management server and receive a location reuse response message from the location management server.

Description

METHOD AND APPARATUS FOR SUPPORTING LOCATION SERVICE FOR MULTIPLE USER EQUIPMENT SHARING SAME LOCATION IN A WIRELESS COMMUNICATION SYSTEM

[0001] The present application is based on and claims priority from an Indian Provisional Application Number 202441047230 filed on 19th June 2024, the disclosure of which is hereby incorporated by reference herein. The proposed invention relates to wireless communication and more particularly relates to a method and system for a location service support for multiple User Equipment (UE) sharing same location.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] The present disclosure relates to wireless communication systems and, more specifically, the present disclosure relates to supporting location service for multiple user equipment sharing same location in a wireless communication system.

[0009] The principal object of the embodiments herein is to provide a system and method for the location service support for multiple UEs sharing the same location.

[0010] Another object of the embodiments herein is to determine whether the first UE and the second UE are in proximity based on an off-network location report.

[0011] Yet another object of the embodiments herein is to provide a location reuse request message to a location management server to enable the reuse of the location of the first UE for the second UE when the second UE is in proximity to the first UE.

[0012] Yet another object of the embodiments herein is to provide the location reuse request message to the location management server to disable the reuse of the location of the first UE for the second UE when the second UE is not in proximity to the first UE.

[0013] Yet another object of the embodiments herein is to enable the reuse of the location of the first UE for the second UE when the second UE is in proximity to the first UE.

[0014] Yet another object of the embodiments herein is to disable the reuse of the location of the first UE for the second UE when the second UE is not in proximity to the first UE.

[0015] In an aspect, the objects are achieved by providing a method for location service support for multiple UE. The method includes detecting by a location management client of a first UE whether a second UE is in proximity to the first UE. The location management client of the first UE generates a location reuse request message by adding information to enable reuse of a location of the first UE for the second UE when the second UE is in proximity to the first UE. The location management client of the first UE transmits the location reuse request message to a location management server and receives a location reuse response message from the location management server. The location reuse response message is received when the location management server enables the reuse of the location of the first UE for the second UE. Further, the location management client of the first UE generates a location reuse request message by adding information to disable the reuse of the location of the first UE for the second UE when the second UE is not in proximity to the first UE and transmits the location reuse request message to the location management server. Further, the location management client of the first UE receives a location reuse response message from the location management server. The location reuse response message is received when the location management server disables the reuse of the location of the first UE for the second UE.

[0016] In another aspect, the objects are achieved by providing a method for the location service support in the wireless communication. The method includes receiving by the location management server the location reuse request message from the location management client of the first UE. Further, the location management server determines whether the location reuse request message comprises information to enable reuse of a location of the first UE for a second UE when the first UE is in proximity to the second UE or disable the reuse of the location of the first UE for the second UE when the first UE is not in proximity to the second UE. The location management server authenticates and authorizes the user of the first UE based on the information available in the location reuse request message when the information indicates enabling the reuse of the location of the first UE for the second UE. Further, the location management server stores the location of the first UE and enables the reuse of the location of the first UE for the second UE when the user of the first UE is authenticated and authorized to reuse the location of the first UE for the second UE. The location management server sends the location reuse response message to the first UE and reuses the location of the first UE for the second UE. Furthermore, the location management server authenticates and authorizes the user of the first UE based on the information available in the location reuse request message when the information indicates disabling the reuse of the location of the first UE for the second UE. Further, the location management server disables the reuse of the location of the first UE for the second UE when the location reuse request message includes information to disable the reuse of the location of the first UE for a second UE and sends the location reuse response message to the first UE.

[0017] In yet another aspect, the objects are achieved by providing a system that includes the location management client of the first UE for the location service support for multiple User Equipment (UE). The system includes a memory, a processor, a multi-UE location management controller coupled with the memory and the processor, where the location management controller detects whether a second UE is in proximity to the first UE and generates the location reuse request message by adding information to enable reuse of the location of the first UE for the second UE when the second UE is in proximity to the first UE. Further, the location management controller transmits the location reuse request message to the location management server and receives the location reuse response message from the location management server. The location reuse response message is received when the location management server enables the reuse of the location of the first UE for the second UE. The location management controller generates the location reuse request message by adding information to disable the reuse of the location of the first UE for the second UE when the second UE is not in proximity to the first UE. Also, the location management controller transmits the location reuse request message to the location management server and receives the location reuse response message from the location management server. The location reuse response message is received when the location management server disables the reuse of the location of the first UE for the second UE.

[0018] In yet another aspect, the objects are achieved by providing a system that includes the location management server, associated with a memory, a processor, a multi-UE location management controller coupled with the memory and the processor. The location management controller receives the location reuse request message from the location management client of the first UE and determines whether the location reuse request message comprises information to enable reuse of a location of the first UE for a second UE when the first UE is in proximity to the second UE or disable reuse of the location of the first UE for the second UE when the first UE is in proximity to the second UE. The location management controller stores the location of the first UE and enables the reuse of the location of the first UE for the second UE when the user of the first UE is authenticated and authorized to reuse the location of the first UE for the second UE. The location management controller sends a location reuse response message to the first UE and reuses the location of the first UE for the second UE. Further, the location management controller authenticates and authorizes the user of the first UE based on the information available in the location reuse request message when the information indicates disabling the reuse of the location of the first UE for the second UE. Also, the location management controller disables the reuse of the location of the first UE for the second UE when the location reuse request message comprises information to disable the reuse of the location of the first UE for the second UE when the second UE is not within the proximity. Furthermore, the location management controller sends the location reuse response message to the first UE.

[0019] In yet another aspect, the objects are achieved by providing a method performed by a first user equipment (UE) in a communication system, the method comprising: receiving, from a second UE, a location report associated with an off-network; based on the location report, identifying whether the second UE is within a certain range of the first UE to determine that the second UE is within an allowed proximity range of the first UE; based on the identification, transmitting, to a service enabler architecture layer (SEAL) location management server (LMS), a location reuse request message including an indication whether to enable or disable a reuse of a location of the first UE for the second UE; and as a response to the location reuse request message, receiving, from the SEAL LMS, a response message.

[0020] In yet another aspect, the objects are achieved by providing a method performed by a service enabler architecture layer (SEAL) location management server (LMS) in a communication system, the method comprising: receiving, from a first user equipment (UE), a location reuse request message including an indication whether to enable or disable a reuse of a location of the first UE for a second UE; performing an authentication of a user; based on the authentication of the user, determining whether to store the location of the first UE; identifying whether the first UE and the second UE are associated and identifying whether the reuse is allowed; and as a response to the location reuse request message, transmitting, to the first UE, a response message.

[0021] In yet another aspect, the objects are achieved by providing a first user equipment (UE) comprising: memory storing instructions; and processing circuitry coupled to the memory and configured, based at least partially on execution of the instructions, to cause the first UE to: receive, from a second UE, a location report associated with an off-network; based on the location report, identify whether the second UE is within a certain range of the first UE to determine that the second UE is within an allowed proximity range of the first UE; based on the identification, transmit, to a service enabler architecture layer (SEAL) location management server (LMS), a location reuse request message including an indication whether to enable or disable a reuse of a location of the first UE for the second UE; and as a response to the location reuse request message, receive, from the SEAL LMS, a response message.

[0022] In yet another aspect, the objects are achieved by providing a service enabler architecture layer (SEAL) location management server (LMS) comprising: memory storing instructions; and processing circuitry coupled to the memory and configured, based at least partially on execution of the instructions, to cause the SEAL LMS to: receive, from a first user equipment (UE), a location reuse request message including an indication whether to enable or disable a reuse of a location of the first UE for a second UE; perform an authentication of a user; based on the authentication of the user, determine whether to store the location of the first UE; identify whether the first UE and the second UE are associated and identifying whether the reuse is allowed; and as a response to the location reuse request message, transmit, to the first UE, a response message.

[0023] The aspects of these embodiments will be better understood with the following description and accompanying drawings. The descriptions, while indicating preferred embodiments and specific details, are for illustration and not limitation. Many changes and modifications can be made within the scope of these embodiments without departing from their spirit, and all such modifications are included.

[0024] According to an embodiment of the disclosure, a wireless communication can be performed efficiently. Especially, a supporting location service for multiple user equipment sharing same location in a wireless communication system can be performed efficiently.

[0025] The features, aspects, and advantages of the present embodiments are illustrated in the accompanying drawings, where like reference letters indicate corresponding parts across various figures. The embodiments will be better understood from the following description and drawings.

[0026] Fig. 1 is a block diagram that illustrates hardware features associated with the location management client of the first UE according to the embodiments as disclosed herein.

[0027] Fig. 2 is a block diagram that illustrates hardware features associated with the location management server according to the embodiments as disclosed herein.

[0028] Fig. 3 is a sequence diagram that illustrates an example scenario of enabling and disabling the location reuse request by the location management client of the UE based on the proximity according to the embodiments as disclosed herein.

[0029] Fig. 4 is a flow diagram that illustrates the flow of location service support provided by the location management client of the first UE for multiple UEs in wireless communication according to the embodiments as disclosed herein.

[0030] Fig. 5 is a flow diagram that illustrates the flow of a method of location service support for multiple UEs provided by the location management server in wireless communication according to the embodiments as disclosed herein.

[0031] The 3rd Generation Partnership Project (3GPP) has defined the Service Enabler Layer Architecture (SEAL) to facilitate various services, one of which is the Location Management (LM) service. The SEAL LM service supports a range of features, including event-based location reporting, on-demand location reporting, location information subscription, obtaining UEs from an area, monitoring location deviations, and location area monitoring. These services enable the Vertical Application Layer (VAL) server to receive location reports from subscriber UEs to provide efficient services.

[0032] In various scenarios, multiple UEs with standalone Universal Subscriber Identity Modules (USIMs) may share the same location. Examples include multi-USIM UEs, vehicles equipped with multiple vehicle-mounted devices, and wearable devices belonging to a single individual. A common characteristic of these scenarios is that these multiple UEs with standalone USIMs tend to share similar locations.

[0033] Currently, when multiple USIMs belonging to one user share the same location at the same time (e.g., a mobile phone and a smartwatch of a user), both UEs report the user's location information to the SEAL LM server independently. This redundancy results in unnecessary location reports being sent to the SEAL LM server. If the location of the first UE (e.g., a mobile phone) is already known to the LM server, there is no need for the server to obtain the location of the second UE (e.g., a smartwatch) separately. This redundancy leads to increased signaling message traffic over the air, consumes additional network resources, and results in higher energy and power consumption for the UEs.

[0034] However, to avoid redundant location reporting from the second UE, the SEAL LM server must be aware of the proximity of the second UE to the first UE. Currently, the SEAL LM server lacks the capability to determine whether the second UE is within the proximity of the first UE, thereby necessitating the independent reporting of location information by each UE. This gap in the system leads to inefficiencies in network resource utilization and increased power consumption for the UEs.

[0035] Thus, it is desired to address the above-mentioned disadvantages, issues or other shortcomings or at least provide a useful alternative.

[0036] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and details in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. The term “or” as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples are not be construed as limiting the scope of the embodiments herein.

[0037] As is traditional in the field, embodiments are described and illustrated in terms of blocks that carry out a described function or functions.　These blocks, which referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and optionally be driven by firmware and software. The circuits, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.　The circuits constituting a block be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments be physically separated into two or more interacting and discrete blocks without departing from the scope of the proposed method.　Likewise, the blocks of the embodiments be physically combined into more complex blocks without departing from the scope of the proposed method.

[0038] The accompanying drawings aid in understanding the technical features, but the embodiments are not limited to these drawings. The proposed method includes any alterations, equivalents, and substitutes beyond those shown. Terms like "first" and "second" are used for distinction and do not limit the elements.

[0039] Location management is a SEAL service that provides the location management-related capabilities to one or more vertical applications. In an embodiment, a Vertical Application Layer (VAL) user is an authorized user who can use a VAL UE to participate in one or more VAL services. In an embodiment, the VAL user and user of the first UE are used interchangeably and have the same meaning. The VAL user ID is a generic name for the user ID of the VAL user within a specific VAL service. The VAL UE is a UE that can be used to participate in one or more VAL services.

[0040] A VAL client is an entity that provides the client-side functionalities corresponding to the vertical applications (e.g., V2X client). The VAL client supports interactions with the SEAL client(s), whereas a SEAL client is an entity that provides the client-side functionalities corresponding to the specific SEAL service. The SEAL client provides the client-side functionalities corresponding to the specific SEAL service. The SEAL client(s) supports interactions with the VAL client(s). The SEAL client also supports interactions with the corresponding SEAL client between the two UEs.

[0041] The VAL service is a generic name for any service offered by the VAL service provider to their VAL users, whereas the SEAL service is a generic name for a common service (e.g., group management, configuration management, location management) that can be utilized by multiple vertical applications. The vertical application is an application catering to a specific vertical. A VAL server provides the server-side functionalities corresponding to the vertical applications (e.g., V2X application servers).

[0042] In current systems, there are no methods for avoiding reception of the location of different UEs of the same user to save energy and power. If multiple USIMs belonging to one user share the same location at the same time (e.g., mobile and watch of a user), both of them report the person's location information to the SEAL LM Server respectively. In such a case, there is no need for the SEAL LM Server to obtain the location for the second UE (e.g., watch) separately if the location of the first UE (e.g., mobile phone) has been known to the LM Server. This can help in reducing the signaling message over the air and also at the same time can save energy and power. However, in order to avoid getting a location report from the second UE, the SEAL LM server currently is not aware of whether the second UE is within proximity of the first UE or not.

[0043] The proposed solution provides a method and system for location service support for multiple UEs. In an embodiment, a method is described to enable or disable reuse of the location of the UE. During the consideration of two UEs, a first UE and a second UE, the location management client of the first UE sends a request to the location management server to enable using the location of the first UE for the second UE. The request includes the user's identity, security parameters, and the latest location report. Further, the location management server authenticates and authorizes the user. If authorized, then the location management server stores the location of the first UE. The location management client of the first UE sends a request to the location management server to disable using the location of the first UE for the second UE when the second UE is not in proximity. The request includes the user's identity, security parameters, and the latest location report.

[0044] In an embodiment, the first UE and the second UE are used as an example, but this same concept can be applied to any number of UEs. For example, the location management client of the first UE can determine three or more other UEs to be within the predefined proximity range and can consider them to be in proximity. Further, the UE can send the location reuse request to the location management server indicating the location management server to enable the reuse of the location of the UE for all the three or more other UEs. Further, the first UE and the second UE may belong to difference users.

[0045] Referring now to the drawings and more particularly to Figs. 1 through 4, where similar reference characters denote corresponding features consistently throughout the figure, these are shown preferred embodiments.

[0046] Fig. 1 is a block diagram that illustrates hardware features associated with the location management client of the first UE in a wireless communication network system, according to the embodiments as disclosed herein.

[0047] Examples of the first UE (105) and the second UE (106) can include, but are not limited to, Consumer Electronics (such as Mobile Phones and Smartphones), Tablets, Wearable Devices, Computing Devices (such as Laptops, Notebooks, Desktops, Workstations, etc.), IoT Devices, Automotive Systems (such as connected cars, Autonomous Vehicles, Vehicle-to-Everything (V2X) communication devices, etc.), Enterprise Devices such as robotics, Specialized Equipment (such as Medical Devices, Public Safety Devices, etc.), Media Devices (such as Gaming Consoles, Streaming Devices, etc.). Further the first UE (105) and the second UE (106) can belong to same user or the different user.

[0048] Examples of the wireless communication network system include, but are not limited to, Cellular Networks (such as 2G, 3G, 4G, 5G, Beyond 5G (B5G) / 6G, or advanced cellular networks), Local Area Networks (LANs) (such as Wi-Fi, Li-Fi, etc.), Personal Area Networks (PANs) (such as Bluetooth, Zigbee, Z-Wave, etc.), Wide Area Networks (WANs) (such as Satellite Communication Networks, Long Range Wide Area Network, Narrowband IoT, Low-bandwidth communication for IoT, etc.), Metropolitan Area Networks (MANs), Machine-to-Machine (M2M), Ad Hoc and Mesh Networks, Emerging and Advanced Networks.

[0049] With reference to Fig 1, the location management client of the first UE (100) can encompass a diverse range of devices, including but not limited to SEAL LM client, Edge Enabler Client, Application Data Analytics Enablement (ADAE) client, or any other SEAL client, among others. The location management client (100) of the first UE (105) is a functional entity that acts as an application client for location management functions. The location management client (100) of the first UE (105) interacts with the location management server (200) and provides the UE-based positioning and location-related information. The location management client (100) of the first UE (105) also supports interactions with the corresponding location management client between the two UEs.

[0050] In an embodiment, the location management client (100) of the first UE (105) includes a memory (101), a processor (102), an I / O interface (103), and a Multi-UE Location Management Controller (104). The memory (101) stores instructions to be executed by the processor (102). The memory (101) can include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard disks, optical disks, floppy disks, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (101) may in some examples be considered a non-transitory storage medium. The term non-transitory may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term non-transitory should not be interpreted that the memory (101) is non-movable. In some examples, the memory (101) stores larger amounts of information. In certain examples, a non-transitory storage medium may store data that can over time change (e.g., in Random Access Memory (RAM) or cache). The memory (101) stores the location information of the first UE (105), a user identity of the first UE (105), security parameters, an identity of the first UE (105), an identity of the second UE (106) and a location report of the first UE (105).

[0051] The processor (102) may include one or a plurality of processors. The one or the plurality of processors may be a general-purpose processor such as a central processing unit (CPU), an Application Processor (AP), or the like, a graphics-only processing unit such as a Graphics Processing Unit (GPU), a Visual Processing Unit (VPU), and / or an AI-dedicated processor such as a Neural Processing Unit (NPU). The processor (102) may include multiple cores and is configured to execute the instructions stored in the memory (101). The processor (102) fetches the location information of the first UE (105), the user identity of the first UE (105), security parameters, the identity of the first UE (105), the identity of the second UE (106) and the location report of the first UE (105). Further, the processor (102) retrieves instructions and executes them.

[0052] The I / O interface (103) transmits the information between the memory (101) and external peripheral devices. The peripheral devices are the input-output devices associated with the location management client (100) of the first UE (105). The I / O interface (103) receives several pieces of information from a plurality of UEs, network devices, servers, and the like. The I / O interface (103) ensures that the operating speed of the processor is synchronized with respect to the input and output devices. The I / O interface (103) establishes a connection between different peripheral devices like multi-UE location management controller (104), memory (101), and others to perform the location service support for any scenario-specific action like to enable reuse or disable the reuse of the location of the first UE (105) to the second UE (106) based on the proximity.

[0053] In an embodiment, the multi-UE location management controller (104) of the location management client (100) of the first UE (105) communicates with the processor (102), the I / O interface (103), and the memory (101) to manage location service support in the wireless network system. The multi-UE location management controller (104) detects whether the second UE (106) is in proximity to the first UE (105) upon receiving off-network location report from second UE (106). Based on this proximity, the multi-UE location management controller (104) generates a location reuse request message by adding information to enable the reuse of the location of the first UE (105) for the second UE (106) when the second UE (106) is in proximity to the first UE (105).

[0054] Additionally, the multi-UE location management controller (104) transmits the location reuse request message to the location management server (200) and receives a location reuse response message from the location management server. The location reuse response message is received when the location management server (200) enables the reuse of the location of the first UE (105) for the second UE (106).

[0055] Furthermore, the multi-UE location management controller (104) generates a location reuse request message by adding information to disable the reuse of the location of the first UE (105) for the second UE (106) when the second UE (106) is not in proximity to the first UE (105). The multi-UE location management controller (104) transmits this location reuse request message to the location management server (200) and receives the location reuse response message from the location management server (200). The location reuse response message is received when the location management server disables the reuse of the location of the first UE (105) for the second UE (106).

[0056] In an embodiment, the information includes the user identity of the first UE (105), security parameters, the identity of the first UE (105), the identity of the second UE (106), and the location report of the first UE (105). Location information of the VAL service user shall be provided by the location management client to the location management server. The location information reporting triggers are based on the location reporting configuration. Different types of location information can be provided.

[0057] The VAL user presents the user identity to an identity management server during a user authentication transaction to provide an identity management client a means for VAL service authentication. In general, since identity management is a common SEAL service, it uses a set of credentials (e.g., biometrics, secure ID, username / password) that may not necessarily be tied to a single VAL service. The user credentials uniquely identify the VAL user to the identity management server.

[0058] The identity of the first UE (105) or the second UE (106) includes at least one of a VAL user identity (VAL user ID), VAL service ID, VAL group identity (VAL group ID), VAL system identity (VAL system ID), and others. The VAL user ID is a unique identifier within the VAL service that represents the VAL user. For example, the VAL user ID may be a URI. The VAL user ID is used for authentication and authorization purposes for providing the VAL service towards the VAL user via the VAL UE. The VAL user ID also indicates the VAL service provider with whom the VAL user has a VAL service agreement. The VAL user may have a VAL service agreement with several VAL service providers and thus will have obtained a unique VAL user ID per VAL service provider. The VAL user ID can be used to access any SEAL service. Further, the VAL service ID is a unique identifier that represents the VAL service.

[0059] A VAL server provides a list of VAL services towards the VAL users or VAL UE. Each VAL service is uniquely identified by a VAL service ID, which is an identifier of the VAL application providing that VAL service. The VAL service ID can be used for policy mapping, QoS handling for VAL communication, and VAL message distribution. For example, an identifier of a V2X service, e.g., ITS-AID or PSID, can be used as a V2X service ID. The VAL group ID is a unique identifier within the VAL service that represents a set of VAL users or VAL UE according to the VAL service. The set of VAL users may belong to the same or different VAL service providers. It indicates the VAL application server where the group is defined. Further, the VAL system ID is a globally unique identifier representing a VAL system.

[0060] Further, the location report is a message that is used in mobility management and positioning procedures. The location report provides the location of the VAL user.

[0061] In an embodiment, the multi-UE location management controller (104) receives an off-network location report from the second UE (106) and determines that the second UE (106) is in proximity when the second UE (106) is within the predefined proximity range of the first UE (105) based on the off-network location report. Further, the multi-UE location management controller (104) determines that the second UE (106) is not in proximity when the second UE (106) is not within the predefined proximity range of the first UE (105) based on the off-network location report.

[0062] In an embodiment, the predefined proximity range is a pre-defined or a pre-configured range which indicates how near the second UE (106) should be present to consider the second UE (106) to be in proximity and to reuse the location of the first UE (105) for the second UE (106). For example, if the predefined proximity range is 1 meter, that means when two devices are within a 1-meter range of each other, then they can reuse the location. If they go more than 1 meter, then they have to disable the reuse of location.

[0063] Fig. 2 is a block diagram that illustrates hardware features associated with the location management server (200) according to the embodiments as disclosed herein. With reference to Fig. 2, the location management client (100) of the first UE (105) can encompass a diverse range of devices including but not limited to Location Management Function (LMF), Access and Mobility Management Function (AMF), SEAL LM server, Edge Enabler Server, ADAE server, or any other SEAL server and others. The location management server (200) is a functional entity that receives and stores user location information and provides user location information to the VAL server. The location management server (200) also acquires location information provided by the PLMN operator. The location management service may optionally obtain location information from 3rd party location servers.

[0064] The location management server acts as Common API Framework (CAPIF's) API exposing function as specified in 3GPP. The location management server (200) also supports interactions with the corresponding location management server in distributed SEAL deployments. The location management server (200) with the fused location function may combine / aggregate location information from multiple sources to provide a more accurate UE location. The location management server (200) also supports reporting the value-added location information (e.g., Geofencing, monitoring events, history location data, prediction related to UE location, and others) to the VAL server (205). In an embodiment, the location management server (200) includes a memory (201), a processor (202), an I / O interface (203), and a multi-UE location management controller (204).

[0065] The memory (201) stores instructions to be executed by the processor (202). The memory (201) can include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard disks, optical disks, floppy disks, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (201) may in some examples be considered a non-transitory storage medium. The term non-transitory may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term non-transitory should not be interpreted that the memory (201) is non-movable. In some examples, the memory (201) stores larger amounts of information. In certain examples, a non-transitory storage medium may store data that can over time change (e.g., in Random Access Memory (RAM) or cache). The memory (201) stores the location information of the first UE (105), a user identity of the first UE (105), security parameters, an identity of the first UE (105), an identity of the second UE (106), and a location report of the first UE (105).

[0066] The processor (202) may include one or a plurality of processors. The one or the plurality of processors may be a general-purpose processor such as a central processing unit (CPU), an Application Processor (AP), or the like, a graphics-only processing unit such as a Graphics Processing Unit (GPU), a Visual Processing Unit (VPU), and / or an AI-dedicated processor such as a Neural Processing Unit (NPU). The processor (202) may include multiple cores and is configured to execute the instructions stored in the memory (201). The processor (202) fetches the location information of the first UE (105), the user identity of the first UE (105), security parameters, the identity of the first UE (105), the identity of the second UE (106), and the location report of the first UE (105). Further, the processor (202) retrieves instructions and executes them.

[0067] The I / O interface (203) transmits the information between the memory (201) and external peripheral devices. The peripheral devices are the input-output devices associated with the location management client (100) of the first UE (105). The I / O interface (203) receives several pieces of information from a plurality of UEs, network devices, servers, and the like. The I / O interface (203) ensures that the operating speed of the processor is synchronized with respect to the input and output devices. The I / O interface (203) establishes a connection between different peripheral devices like the multi-UE location management controller (204), memory (201), and others to perform the location service support for any scenario-specific action like enabling reuse or disabling the reuse of the location of the first UE (105) to the second UE (106) based on the proximity.

[0068] In an embodiment, the multi-UE location management controller (104) of the location management client (100) of the first UE (105) communicates with the processor (102), the I / O interface (103), and the memory (101) for managing location service support in the wireless network system. The multi-UE location management controller (204) receives the location reuse request message from the location management client (100) of the first UE (105). Further, the multi-UE location management controller (204) determines whether the location reuse request message includes information to enable the reuse of the location of the first UE (105) for the second UE (106) when the first UE (105) is in proximity to the second UE (106) or disable reuse of the location of the first UE (105) for the second UE (106) when the first UE (105) is in proximity to the second UE (106). Furthermore, the multi-UE location management controller (204) authenticates and authorizes the user of the first UE (105) based on the information available in the location reuse request message when the information indicates enabling the reuse of the location of the first UE (105) for the second UE (106). Also, the multi-UE location management controller (204) stores the location of the first UE (105) and enables the reuse of the location of the first UE (105) for the second UE (106) when the user of the first UE is authenticated and authorized to reuse the location of the first UE (105) for the second UE (106). The multi-UE location management controller (204) sends the location reuse response message to the first UE (105) and performs the reuse of the location of the first UE (105) for the second UE (106).

[0069] Further, the multi-UE location management controller (204) authenticates and authorizes the user of the first UE based on the information available in the location reuse request message when the information indicates disabling the reuse of the location of the first UE (105) for the second UE (106). The multi-UE location management controller (204) disables the reuse of the location of the first UE (105) for the second UE (106) when the user of the first UE (105) is authenticated and authorized to reuse the location of the first UE (105) for the second UE (106).

[0070] Figs 1 and 2 show the hardware components of the location management client (100) of the first (105) and server (200). Alternative embodiments may include different or additional components. The labels are illustrative and do not limit the invention's scope. Components may also be combined to perform similar functions.

[0071] Fig 3 is a sequence diagram that illustrates an example scenario of enabling and disabling of the location reuse request by the location management client of the UE based on the proximity according to the embodiments as disclosed herein. As pre-conditions, the location management client (100) of the first UE (105) has offline configured location reporting triggered to the location management client (100) of the second UE (in the second UE) as specified in 3GPP.

[0072] At step S301, the location management client (100) of the first UE (105) receives an off-network location report from the second UE (106). Based on the location report, if the second UE (106) is within a certain range of the first UE (105), the location management client (100) of the first UE (105) determines that the second UE (106) (where the location management client of the second UE resides and shared the off-network location report) is within the allowed / configured proximity range of the first UE (105) (i.e., the first UE (105) and the second UE (106) are paired), and so the first UE's location can be used by the location management server (200) instead of the second UE's location.

[0073] At step S302, the location management client (100) of the first UE (105) sends a request message to the location management server (200) to enable the reuse of the location of the first UE (105) for the second UE (106). The request message includes the user's identity, security parameters, the first UE identity, the identity of the second UE (106), and the latest location report of the first UE (105). In an embodiment, the location management client (100) of the first UE (105) sends a location report to the location management server (200), which includes an indication to enable the reuse of the location of the first UE (105) for the second UE (106). The request includes the user's identity, security parameters, the identity of the first UE (105), and the identity of the second UE (106). In another embodiment, the request message includes the list of UE identities of multiple UEs which are within the proximity of the first UE (105).

[0074] At step S303, the enabler server authenticates and authorizes the user. If authorized, then the location management server (200) stores the location of the first UE (105) and enables the reuse of the location of the first UE (105) for all UEs included in the request message. The location management server (200) sends a response back to the location management client (100) of the first UE (105). In an embodiment, if the second UE (106) and the first UE (105) do not belong to the same user, then the location management server (200) takes the user consent of the user of the second UE (106) to reuse the location of the first UE (105) instead of the second UE (106). If the user of the second UE (106) agrees and sends a successful response, then only the location management server (200) enables the reuse of the location of the first UE (105) for the second UE (106). If the user of the second UE (106) does not agree and sends a failure response, then the location management server (200) does not enable the reuse of the location of the first UE (105) for the second UE (106).

[0075] At step S304, the VAL server (205) requests the location of the first UE (105). If the latest location of the first UE (105) is not available or the stored location of the first UE (105) is expired, the location management server (200) gets the current location of the first UE (105) as illustrated at step S305. At step S306, the location management server (200) sends the location report of the first UE (105) to the VAL server (205). Further, at step S307, the VAL server (205) requests the location of the second UE (106). At step S308, the location management server (200) determines that the second UE (106) is within the proximity of the first UE (105) and the first UE (105) has already enabled the reuse of the location of the first UE for the second UE (106). So the location management server (200) sends the location report of the first UE (105) to the VAL server (205). The steps S307 and S308 can be repeated multiple times, which means different VAL servers may request the second UE's location, and the location management server (200) reuses the location of the first UE (105) instead of sending a request message to the second UE (106) to get the location report.

[0076] At step S309, the location management client (100) of the first UE (105) receives an off-network location report from the location management client of the second UE (in the second UE (106)). Based on the location report, if the second UE is not within a certain range of the first UE (105), the location management client (100) of the first UE (105) determines that the second UE (106) (where the location management client of the second UE resides and shared the off-network location report) is out of the allowed / configured proximity range of the first UE (i.e., the first UE and the second UE are unpaired), and so the first UE's location cannot be used by the location management server (200) instead of the second UE's location. At step S310, the location management client (100) of the first UE (105) sends a request message to the location management server to disable the reuse of the location of the first UE (105) for the second UE (106). The request message includes the user's identity, security parameters, the identity of the first UE (105), the identity of the second UE (106), and may include the latest location report of the first UE (105). In an embodiment, the location management client (100) of the first UE (105) sends a location report to the location management server (200), which includes the indication to disable the reuse of the location of the first UE (105) for the second UE (106). The request includes the user's identity, security parameters, the identity of the first UE, and the identity of the second UE. In another embodiment, the request message includes a list of UE identities of multiple UEs which went away from the proximity of the first UE (105).

[0077] At step S311, the location management server (200) authenticates and authorizes the user. If authorized, then the location management server (200) stores the location of the first UE (105) and disables the reuse of the location of the first UE (105) for all the UEs included in the request message. The location management server (200) sends a response back to the location management client (100) of the first UE (105). At step S312, the VAL server (205) requests the location of the second UE (106). At step S313, the location management server (200) determines that the second UE (106) is not within the proximity of the first UE (105) and the first UE (105) has already disabled the reuse of the location of the first UE (105) for the second UE (106). So if the latest location of the second UE (106) is not available or the stored location of the second UE (106) is expired, the location management server (200) gets the current location of the second UE (106) as specified in 3GPP. At step S314, the location management server (200) sends the location report of the second UE (106) to the VAL server (205).

[0078] In case the step S310 occurs between steps S307 and S308, the location management server (200) may still decide to reuse the first UE's location in the response message, or the location management server (200) may decide to get the second UE (106) location on-demand before sending the response. When multiple USIMs belonging to one user share the same location at the same time (e.g., mobile and watch of a user), both of them report the person's location information to the SEAL LM Server respectively. In such a case, there is no need for the SEAL LM Server to obtain the location for the second UE (e.g., watch) separately if the location of the first UE (e.g., mobile phone) has been known to the LM Server. This can help in reducing the signaling message over the air and also at the same time can save energy and power. However, in order to avoid getting a location report from the second UE, the SEAL LM server currently is not aware of whether the second UE is within the proximity of the first UE or not. The current embodiment proposes a method for the SEAL LM server to know when the second UE (106) comes within the proximity of the first UE (105) and thus the location management server (200) can decide to avoid getting a location report from the second UE (106). Similarly, the embodiment also proposes a method for the location management server (200) to know when the second UE (106) goes out of the proximity of the first UE (105) and thus the location management server (200) can decide to start getting a location report from the second UE (106).

[0079] Fig. 4 is a flow diagram that illustrates the flow of location service support provided by the location management client (100) of the first UE (105) for multiple UEs in wireless communication according to the embodiments as disclosed herein. The figure illustrates the location management client-side location service support where the location management client (100) of the first UE (105) transmits the location reuse request message with the information to perform either enable or disable the reuse of the location of the first UE (105) for the second UE (106).

[0080] At step S401, the location management client (100) of the first UE (105) receives the off-network location report from the second UE (106). Further, the location management client (100) of the first UE (105) detects whether the second UE (106) is in proximity to the first UE (105) as illustrated at step S402. Further, when the second UE (106) is within the predefined proximity range, the location management client (100) of the first UE (105) generates the location reuse request message by adding information to enable reuse of the location of the first UE (105) for the second UE (106) as illustrated at step S403.

[0081] At step S404, the location management client (100) of the first UE (105) transmits the location reuse request message to the location management server (200). Further, at step S405, the location management client (100) of the first UE (105) receives the location reuse response message from the location management server (200). The location reuse response message is received when the location management server (200) enables the reuse of the location of the first UE (105) for the second UE (106).

[0082] When the location management client (100) of the first UE (105) detects that the second UE (106) is not within the proximity at step S402, the location management client (100) of the first UE (105) generates the location reuse request message by adding information to disable the reuse of the location of the first UE (105) for the second UE (106) as illustrated at step S406. Further, at step S407, the location management client (100) of the first UE (105) transmits the location reuse request message with the information to disable the reuse of the location of the first UE (105) for the second UE (106). At step S408, the location management client (100) of the first UE (105) receives the location reuse response message from the location management server (200). The location reuse response message is received when the location management server (200) disables the reuse of the location of the first UE (105) for the second UE (106).

[0083] In an embodiment, the information includes the user identity of the first UE, security parameters, the identity of the first UE, the identity of the second UE, and the location report of the first UE.

[0084] In an embodiment, the location management client (100) of the first UE (105) detects whether the second UE is in proximity to the first UE includes receiving by the location management client of the first UE (105) the off-network location report from the second UE (106). Further, based on the location report, the location management client (100) of the first UE (105) determines that the second UE (106) is in the proximity when the second UE is within a predefined proximity range of the first UE. Also, if the second UE (106) is not within the predefined proximity range of the first UE (105), the location management client (100) of the first UE (105) determines that the second UE (106) is not in the proximity.

[0085] Fig. 5 is a flow diagram that illustrates the flow of the method of location service support for multiple UEs in wireless communication according to the embodiments as disclosed herein. The figure illustrates the location management service support provided by the location management server (200). The location management server (200), based on the location reuse request from the location management client (100) of the first UE (105), enables or disables the reuse of the location of the first UE (105) for the second UE (106).

[0086] At step S501, the location management server receives the location reuse request message from the location management client (100) of the first UE (105). Further, at step S502, the location management server (200) determines whether the location reuse request message includes information to enable reuse of the location of the first UE (105) for the second UE (106) when the first UE (105) is in proximity to the second UE (106) or disable the reuse of the location of the first UE (105) for the second UE (106) when the first UE (105) is in proximity to the second UE (106). At step S503, the location management server (200) authenticates and authorizes the user of the first UE based on the information available in the location reuse request message when the information indicates enabling the reuse of the location of the first UE (105) for the second UE (106). Further, the location management server (200) stores the location of the first UE (105) and enables the reuse of the location of the first UE (105) for the second UE (106) when the user of the first UE is authenticated and authorized to reuse the location of the first UE (105) for the second UE (106) as illustrated at step S504. At step S505, the location management server (200) sends the location reuse response message to the first UE (105) and reuses the location of the first UE (105) for the second UE (106).

[0087] Furthermore, the location management server (200) authenticates and authorizes the user of the first UE based on the information available in the location reuse request message when the information indicates disabling the reuse of the location of the first UE for the second UE. Further, at step S507, the location management server (200) disables the reuse of the location of the first UE for the second UE (106) when the location reuse request message includes information to disable the reuse of the location of the first UE for a second UE. Step S508 illustrates sending the location reuse response message to the first UE (105) by the location management server.

[0088] In an embodiment, the location management server (200) receives a location request message for the second UE (106) from the VAL server (205) and sends the location of the first UE (105) instead of the location of the second UE (106) to the VAL server when reuse of the location of the first UE (105) for the second UE (106) is enabled.

[0089] In an embodiment, the location management server (200) receives the location request message for the second UE (106) from the VAL server (205). Further, the location management server (200) sends the location of the first UE (105) instead of the location of the second UE (106) to the VAL server (205) when reuse of the location of the first UE (105) for the second UE (106) is enabled.

[0090] In an embodiment, the location management server (200) receives the location request message for the second UE (106) from the VAL server (205). The location management server (200) obtains the current location of the second UE (106) from an off-network location report of the second UE (106) when reuse of the location of the first UE (105) for the second UE (106) is disabled. Further, the location management server (200) sends the location of the second UE (106) to the VAL server.

[0091] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described herein.

Claims

1.A method performed by a first user equipment (UE) in a communication system, the method comprising:receiving, from a second UE, a location report associated with an off-network;based on the location report, identifying whether the second UE is within a certain range of the first UE to determine that the second UE is within an allowed proximity range of the first UE;based on the identification, transmitting, to a service enabler architecture layer (SEAL) location management server (LMS), a location reuse request message including an indication whether to enable or disable a reuse of a location of the first UE for the second UE; andas a response to the location reuse request message, receiving, from the SEAL LMS, a response message.2.The method of claim 1, further comprising:in case that the second UE is within the certain range of the first UE, based on the location report, determining that the second UE is within an allowed proximity range of the first UE,wherein in case that the second UE is within the certain range of the first UE, the location reuse request message further includes the indication to enable the reuse of the location of the first UE for the second UE,3.The method of claim 1, further comprising:in case that the second UE is out of the certain range of the first UE, based on the location report, determining that the second UE is outside the allowed proximity range of the first UE,wherein in case that the second UE is out of the certain range of the first UE, the location reuse request message further includes the indication to disable the reuse of the location of the first UE for the second UE.4.The method of claim 1,wherein the location reuse request message further includes at least one of an identity of a user, an identity of the first UE, an identity of the second UE, or a latest location report of the first UE.5.A method performed by a service enabler architecture layer (SEAL) location management server (LMS) in a communication system, the method comprising:receiving, from a first user equipment (UE), a location reuse request message including an indication whether to enable or disable a reuse of a location of the first UE for a second UE;performing an authentication of a user;based on the authentication of the user, determining whether to store the location of the first UE;identifying whether the first UE and the second UE are associated and identifying whether the reuse is allowed; andas a response to the location reuse request message, transmitting, to the first UE, a response message.6.The method of claim 5, further comprising:receiving, from a VAL server, a location request for the second UE; andin case that the reuse is enabled, transmitting, to the VAL server, the location of the first UE instead of a location of the second UE.7.The method of claim 5, further comprising:receiving, from a VAL server, a location request for the second UE; andin case that the reuse is disabled, transmitting, to the VAL server, a location of the second UE only instead of reusing the location of the first UE.8.The method of claim 5,wherein the location reuse request message further includes at least one of an identity of a user, an identity of the first UE, an identity of the second UE, or a latest location report of the first UE.9.A first user equipment (UE) comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the first UE to:receive, from a second UE, a location report associated with an off-network;based on the location report, identify whether the second UE is within a certain range of the first UE to determine that the second UE is within an allowed proximity range of the first UE;based on the identification, transmit, to a service enabler architecture layer (SEAL) location management server (LMS), a location reuse request message including an indication whether to enable or disable a reuse of a location of the first UE for the second UE; andas a response to the location reuse request message, receive, from the SEAL LMS, a response message.10.The first UE of claim 9, wherein the instructions further cause the first UE to:in case that the second UE is within the certain range of the first UE, based on the location report, determine that the second UE is within an allowed proximity range of the first UE,wherein in case that the second UE is within the certain range of the first UE, the location reuse request message further includes the indication to enable the reuse of the location of the first UE for the second UE,11.The first UE of claim 9, wherein the instructions further cause the first UE to:in case that the second UE is out of the certain range of the first UE, based on the location report, determine that the second UE is outside the allowed proximity range of the first UE,wherein in case that the second UE is out of the certain range of the first UE, the location reuse request message further includes the indication to disable the reuse of the location of the first UE for the second UE.12.The first UE of claim 9,wherein the location reuse request message further includes at least one of an identity of a user, an identity of the first UE, an identity of the second UE, or a latest location report of the first UE.13.A service enabler architecture layer (SEAL) location management server (LMS) comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the SEAL LMS to:receive, from a first user equipment (UE), a location reuse request message including an indication whether to enable or disable a reuse of a location of the first UE for a second UE;perform an authentication of a user;based on the authentication of the user, determine whether to store the location of the first UE;identify whether the first UE and the second UE are associated and identifying whether the reuse is allowed; andas a response to the location reuse request message, transmit, to the first UE, a response message.14.The SEAL LMS of claim 13, wherein the instructions further cause the SEAL LMS to:receive, from a VAL server, a location request for the second UE; andin case that the reuse is enabled, transmit, to the VAL server, the location of the first UE instead of a location of the second UE.15.The SEAL LMS of claim 13, wherein the instructions further cause the SEAL LMS to:receive, from a VAL server, a location request for the second UE; andin case that the reuse is disabled, transmit, to the VAL server, a location of the second UE only instead of reusing the location of the first UE,wherein the location reuse request message further includes at least one of an identity of a user, an identity of the first UE, an identity of the second UE, or a latest location report of the first UE.

Images