Mapping of applications and location service profiles

The method and apparatus for managing location service profiles in wireless networks address configuration issues by determining and transmitting optimized profiles, improving the performance and accuracy of location services across different applications and environments.

KR103044738B1Active Publication Date: 2026-11-06LENOVO (SINGAPORE) PTE LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
KR1020247005156
Authority / Receiving Office
KR · KR
Patent Type
Patents
Current Assignee / Owner
Priority Date
2021-08-18
Filing Date
2021-09-28
Publication Date
2026-11-06
Estimated Expiration
2041-09-28

AI Technical Summary

Technical Problem

Location service profiles in wireless communication networks may not function properly if not properly configured, leading to inefficiencies and suboptimal performance.

Method used

A method and apparatus for configuring and managing location service profiles, including determining mappings and fused location estimates based on location requests, using a processor to manage multiple profiles with various parameters and transmitting these profiles to location service producers.

Benefits of technology

Enhances the functionality and efficiency of location services by ensuring proper configuration and integration of location service profiles, meeting specific quality and accuracy requirements for diverse applications and environments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 112024017129729-PCT00006_ABST
    Figure 112024017129729-PCT00006_ABST
Patent Text Reader

Abstract

Devices, methods, and systems for mapping applications and location service profiles are disclosed. One method (900) includes the step (902) of configuring location service profiles. Each location service profile includes at least one location determination method, at least one service quality parameter, at least one mapping to at least one location service producer, at least one application service type, and / or at least one service area type. The method (900) includes the step (904) of receiving a location request from a location service consumer. The method (900) includes the step (906) of determining a first mapping of at least one application to a first location service profile among the location service profiles based on the location request. The method (900) includes the step (908) of transmitting the first mapping and the first location service profile to at least one location service producer. The method (900) includes the step (910) of determining a fused location estimate for the first location service profile.
Need to check novelty before this filing date? Find Prior Art

Description

Technology Field

[0001] The subject matter disclosed in this specification relates generally to wireless communications and more specifically to mapping applications and location service profiles. Background Technology

[0002] In certain wireless communication networks, location service profiles may be used to support location services. If not properly configured, location services may not function properly.

[0003] Methods for mapping applications and location service profiles are disclosed. Devices and systems also perform the functions of these methods. One embodiment of the method in a location service enabler includes the step of configuring a plurality of location service profiles. Each of the plurality of location service profiles includes at least one location determination method, at least one service quality parameter, at least one mapping to at least one location service producer, at least one application service type, at least one service area type, or a combination thereof. In some embodiments, the method includes the step of receiving a location request from a location service consumer. In certain embodiments, the method includes the step of determining a first mapping of at least one application of at least one user device to a first location service profile among the plurality of location service profiles based on the location request. In various embodiments, the method includes the step of transmitting the first mapping and the first location service profile to at least one location service producer. In some embodiments, the method includes the step of determining a fused location estimate for the first location service profile.

[0004] An apparatus for mapping applications and location service profiles includes a location service enabler. In some embodiments, the apparatus includes a processor that configures a plurality of location service profiles. Each of the plurality of location service profiles includes at least one location determination method, at least one service quality parameter, at least one mapping to at least one location service producer, at least one application service type, at least one service area type, or a combination thereof. In various embodiments, the apparatus includes a receiver that receives a location request from a location service consumer. Based on the location request, the processor determines a first mapping of at least one application of at least one user device to a first location service profile among the plurality of location service profiles. In some embodiments, the apparatus includes a transmitter that transmits the first mapping and the first location service profile to at least one location service producer. In certain embodiments, the processor determines a fused location estimate for the first location service profile. Brief explanation of the drawing

[0005] A more detailed description of the embodiments briefly described above will be given with reference to specific embodiments exemplified in the attached drawings. With the understanding that these drawings depict only some embodiments and are therefore not to be considered as limiting the scope, these embodiments will be described and explained with additional specificity and detail through the use of the attached drawings: FIG. 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for mapping applications and location service profiles. FIG. 2 is a schematic block diagram illustrating one embodiment of a device that can be used to map applications and location service profiles. FIG. 3 is a schematic block diagram illustrating one embodiment of a device that can be used to map applications and location service profiles. FIG. 4 is a block diagram illustrating one embodiment of a system for applying LCS profile mapping. FIG. 5 is a block diagram illustrating another embodiment of a system for application to LCS profile mapping. FIG. 6 is a flowchart illustrating one embodiment of a method for verifying requirements. FIG. 7 is a block diagram illustrating an additional embodiment of a system for application to LCS profile mapping. FIG. 8 is a block diagram illustrating another embodiment of a system for application to LCS profile mapping. FIG. 9 is a flowchart diagram illustrating one embodiment of a method for mapping applications and location service profiles. Specific details for implementing the invention

[0006] As will be recognized by those skilled in the art, aspects of these embodiments may be implemented as a system, device, method, or program product. Accordingly, embodiments may take the form of an embodiment that is entirely hardware, an embodiment that is entirely software (including firmware, resident software, microcode, etc.), or an embodiment that combines software and hardware aspects, all of which may be generally referred to herein as a “circuit,” “module,” or “system.” Additionally, embodiments may take the form of a program product implemented in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code, referred to hereinafter as code. These storage devices may be tangible, non-transient, and / or non-transmitting. These storage devices may not implement signals. In certain embodiments, these storage devices only adopt signals for accessing code.

[0007] Certain of the functional units described herein may be labeled as modules to further emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom "VLSI (very-large-scale integration) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other distinct components. A module may also be implemented as a programmable hardware device such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0008] Modules may also be implemented as code and / or software for execution by various types of processors. An identified module of code may include, for example, one or more physical or logical blocks of executable code that can be organized as objects, procedures, or functions. Nevertheless, the executables of the identified module do not need to be physically located together, but may include different instructions stored in different locations that contain the module and achieve the stated purposes for the module when logically combined.

[0009] In practice, a module of code may be a single instruction or a number of instructions, and may even be distributed across different code segments among different programs and across multiple memory devices. Similarly, computational data may be identified and exemplified within the modules herein, implemented in any suitable form, and organized within any suitable type of data structure. Such computational data may be collected as a single data set or distributed across different locations, including distributed across different computer-readable storage devices. Where a module or parts of a module are implemented in software, the software parts are stored on one or more computer-readable storage devices.

[0010] Any combination of one or more computer-readable media may be used. Such computer-readable media may be computer-readable storage media. Such computer-readable storage media may be storage devices that store code. Such storage devices may be, for example, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, devices, or any suitable combination of the foregoings, but are not limited thereto.

[0011] More specific examples (a non-comprehensive list) of such storage devices are as follows: electrical connections having one or more wires, portable computer diskettes, hard disks, "RAM (random access memory), "ROM (read-only memory), "EPROM (erasable programmable read-only memory) or flash memory, portable "CD-ROM (compact disc read-only memory)," optical storage devices, magnetic storage devices, or any suitable combination of the foregoings. In the context of this document, a computer-readable storage medium may be any type of tangible medium capable of containing or storing a program to be used by or in relation to an instruction execution system, device, or device.

[0012] Code for executing operations for the embodiments may consist of any number of lines and may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, etc., conventional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly languages. Such code may be executed entirely on the user's computer, as a standalone software package, partially on the user's computer, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer via any type of network including a "LAN" (local area network) or a "WAN" (wide area network), or an external computer may be connected (e.g., via the Internet using an Internet service provider).

[0013] Throughout this specification, references to “one embodiment,” “an embodiment,” or similar language mean that the detailed features, structures, or characteristics described with respect to such embodiment are included in at least one embodiment. Accordingly, throughout this specification, appearances of phrases such as “in one embodiment,” “in an embodiment,” and similar language may all refer to the same embodiment, but are not necessarily so, and unless explicitly stated otherwise, mean “one or more but not all embodiments.” Terms such as “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless otherwise explicitly stated. An enumerated listing of items does not imply that any or all of the items are mutually exclusive. The terms “a,” “an,” and “the” also refer to “one or more,” unless otherwise explicitly stated.

[0014] Additionally, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details, such as examples of programming, software modules, user choices, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments may be practiced without one or more of these specific details, or with other methods, components, materials, etc. In other cases, known structures, materials, or operations are not illustrated or described in detail to avoid obscuring the aspects of the embodiments.

[0015] Aspects of these embodiments are described below with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatuses, systems, and program products according to the embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, may be implemented by code. Such code may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing unit to produce a machine, and instructions executed through the processor of the computer or other programmable data processing unit generate means for implementing the functions / operations specified in the blocks of the schematic flowcharts and / or schematic block diagrams.

[0016] Code that can instruct a computer, other programmable data processing unit, or other devices to function in a detailed manner to produce a manufactured article, including instructions stored in the storage device that implement the functions / operations specified in the blocks or blocks of schematic flowcharts and / or schematic block diagrams, may also be stored in the storage device.

[0017] Such code may also be loaded onto a computer, other programmable data processing device, or other devices, so as to cause a series of operation steps to be performed on the computer, other programmable device, or other devices to produce a computer-implemented process, thereby providing processes for the code executed on the computer or other programmable device to implement the functions / operations specified in the blocks or blocks of the flowchart and / or block diagram.

[0018] In the drawings, schematic flowcharts and / or schematic block diagrams illustrate the architecture, functionality, and operation of possible implementations of devices, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flowcharts and / or schematic block diagrams may represent a module, segment, or part of code containing one or more executable instructions of code for implementing specified logical function(s).

[0019] It should also be noted that in some alternative implementations, functions noted in blocks may occur out of the order noted in the drawings. For example, two blocks depicted consecutively may, in fact, substantially be executed simultaneously, or these blocks may be executed in reverse order from time to time depending on the accompanying functionality. Other steps and methods equivalent in function, logic, or effect to one or more blocks, or parts thereof, of the illustrated drawings may be conceived.

[0020] While various arrow and line types may be adopted in flowcharts and / or block diagrams, it is understood that these do not limit the scope of the corresponding embodiments. In practice, some arrows or other connecting lines may be used merely to indicate the logical flow of the described embodiments. For example, arrows may indicate waiting or monitoring periods of unspecified duration between the enumerated steps of the described embodiments. It will also be noted that individual blocks of the block diagrams and / or flowcharts, and combinations of blocks in these block diagrams and / or flowcharts, may be implemented by special-purpose hardware-based systems or combinations of special-purpose hardware and code that perform the specified functions or operations.

[0021] The description of elements in each drawing may refer to elements in subsequent drawings. Similar numbers in all drawings refer to similar elements, including alternative embodiments of similar elements.

[0022] FIG. 1 depicts an embodiment of a wireless communication system (100) for mapping applications and location service profiles. In one embodiment, the wireless communication system (100) includes remote units (102) and network units (104). Although a specific number of remote units (102) and network units (104) is depicted in FIG. 1, a person skilled in the art will recognize that any number of remote units (102) and network units (104) may be included in the wireless communication system (100).

[0023] In one embodiment, the remote units (102) may include computing devices such as desktop computers, laptop computers, PDAs (personal digital assistants), tablet computers, smartphones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), on-board computers, network devices (e.g., routers, switches, modems), aircraft, drones, etc. In some embodiments, the remote units (102) include wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, the remote units (102) may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, devices, or other terms used in the art. Remote units (102) can communicate directly with one or more of the network units (104) via UL communication signals. In certain embodiments, remote units (102) can communicate directly with other remote units (102) via sidelink communication.

[0024] Network units (104) can be distributed across geographical areas. In specific embodiments, the network unit (104) includes an access point, access terminal, base, base station, location server, "CN" (core network), radio network entity, node-B, eNB (evolved node-B), gNB (5G node-B), home node-B, relay node, device, core network, aviation server, radio access node, "AP" (access point), "NR" (new radio), network entity, "AMF" (access and mobility management function), "UDM" (unified data management), "UDR" (unified data repository), UDM / UDR, "PCF" (policy control function), "RAN" (radio access network), "NSSF" (network slice selection function), "OAM" (operations, administration, and management), "SMF" (session management function), "UPF" (user plane function), application function, "AUSF" (authentication server function), "SEAF" (security anchor functionality), "TNGF" (trusted non-3GPP gateway function), application function, SEAL (Service Enabler Architecture Layer) function, vertical application enabler It may also be referred to as a server, edge enabler server, edge configuration server, mobile edge computing platform function, mobile edge computing application, middleware entity, location enabler server, location server, or one or more of these, and / or may include them, or may be referred to by any other term used in the technology.Network units (104) are generally part of a radio access network comprising one or more controllers that are communicably coupled to one or more corresponding network units (104). The radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, among other networks, such as the Internet and public switched telephone networks. These and other elements of radio access and core networks are not illustrated but are generally known to those skilled in the art.

[0025] In one implementation, the wireless communication system (100) complies with NR protocols standardized by the "3GPP" (third generation partnership project), wherein the network unit (104) transmits using an OFDM modulation scheme on the "DL" (downlink) and the remote units (102) transmit using an "SC-FDMA" (single-carrier frequency division multiple access) scheme or an "OFDM" (orthogonal frequency division multiplexing) scheme on the "UL" (uplink). However, more generally, a wireless communication system (100) may implement some other open or proprietary communication protocols, among other protocols, such as WiMAX, IEEE (Institute of Electrical and Electronics Engineers) 802.11 variants, GSM (Global System for Mobile Communications), GPRS (General Packet Radio Service), UMTS (Universal Mobile Telecommunications System), LTE (Long Term Evolution) variants, CDMA2000 (Code Division Multiple Access 2000), Bluetooth®, ZigBee, and Sigfoxx. The present disclosure is not intended to be limited to any detailed wireless communication system architecture or implementation of a protocol.

[0026] Network units (104) can service multiple remote units (102) within a serving area, for example, a cell or cell sector, via a wireless communication link. Network units (104) transmit DL communication signals to service the remote units (102) in a time, frequency, and / or space domain.

[0027] In certain embodiments, the network unit (104) may configure a plurality of location service profiles. Each of the plurality of location service profiles includes at least one location determination method, at least one service quality parameter, at least one mapping to at least one location service producer, at least one application service type, at least one service area type, or a combination thereof. In some embodiments, the network unit (104) may receive a location request from a location service consumer. In certain embodiments, the network unit (104) may determine a first mapping of at least one application of at least one user device to a first location service profile among the plurality of location service profiles based on the location request. In various embodiments, the network unit (104) may transmit the first mapping and the first location service profile to at least one location service producer. In some embodiments, the network unit (104) may determine a fused location estimate for the first location service profile. Thus, the network unit (104) may be used to map applications and location service profiles.

[0028] FIG. 2 depicts one embodiment of a device (200) that can be used to map applications and location service profiles. The device (200) includes one embodiment of a remote unit (102). Additionally, the remote unit (102) may include a processor (202), memory (204), an input device (206), a display (208), a transmitter (210), and a receiver (212). In some embodiments, the input device (206) and the display (208) are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit (102) may not include any input device (206) and / or display (208). In various embodiments, the remote unit (102) may include one or more of the processor (202), memory (204), transmitter (210), and receiver (212), and may not include the input device (206) and / or display (208).

[0029] In one embodiment, the processor (202) may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor (202) may be a microcontroller, a microprocessor, a CPU (central processing unit), a GPU (graphics processing unit), an auxiliary processing unit, a FPGA (field programmable gate array), or a similar programmable controller. In some embodiments, the processor (202) executes instructions stored in memory (204) to perform the methods and routines described herein. The processor (202) is communicably coupled to memory (204), an input device (206), a display (208), a transmitter (210), and a receiver (212).

[0030] In one embodiment, memory (204) is a computer-readable storage medium. In some embodiments, memory (204) includes a volatile computer storage medium. For example, memory (204) may include RAM, including "DRAM" (dynamic RAM), "SDRAM" (synchronous dynamic RAM), and / or "SRAM" (static RAM). In some embodiments, memory (204) includes a non-volatile computer storage medium. For example, memory (204) may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory (204) includes both volatile and non-volatile computer storage media. In some embodiments, memory (204) also stores program code and related data, such as operating systems or other controller algorithms running on the remote unit (102).

[0031] The input device (206) may, in one embodiment, include any known computer input device, such as a touch panel, a button, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device (206) may be integrated with the display (208), for example, as a touchscreen or a similar touch-sensitive display. In some embodiments, the input device (206) includes a touchscreen on which text can be entered using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, the input device (206) includes two or more different devices, such as a keyboard and a touch panel.

[0032] In one embodiment, the display (208) may include any known electronically controllable display or display device. The display (208) may be designed to output visual, auditory, and / or haptic signals. In some embodiments, the display (208) includes an electronic display capable of outputting visual data to a user. For example, the display (208) may include, but is not limited to, an LCD (liquid crystal display), an LED (light emitting diode) display, an OLED (organic light emitting diode) display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another, non-limiting example, the display (208) may include a wearable display such as a smart watch, smart glasses, a head-up display, etc. Additionally, the display (208) may be a component of a smartphone, a personal digital assistant, a television, a table computer, a laptop computer, a personal computer, a vehicle dashboard, etc.

[0033] In certain embodiments, the display (208) includes one or more speakers for producing sound. For example, the display (208) may produce an auditory alarm or notification (e.g., a beep or a chime). In some embodiments, the display (208) includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or part of the display (208) may be integrated with an input device (206). For example, the input device (206) and the display (208) may form a touchscreen or a similar touch-sensitive display. In other embodiments, the display (208) may be positioned close to the input device (206).

[0034] Even if only one transmitter (210) and one receiver (212) are exemplified, the remote unit (102) may have any suitable number of transmitters (210) and receivers (212). The transmitter (210) and receiver (212) may be any suitable type of transmitter and receiver. In one embodiment, the transmitter (210) and receiver (212) may be part of a transceiver.

[0035] FIG. 3 depicts one embodiment of a device (300) that can be used to map applications and location service profiles. The device (300) includes one embodiment of a network unit (104). Additionally, the network unit (104) may include a processor (302), memory (304), input device (306), display (308), transmitter (310), receiver (312), network interface (314) (e.g., for communicating with network devices), and application interface (316) (e.g., for communicating with applications). As may be acknowledged, the processor (302), memory (304), input device (306), display (308), transmitter (310), and receiver (312) may each be substantially similar to the processor (202), memory (204), input device (206), display (208), transmitter (210), and receiver (212) of the remote unit (102).

[0036] In certain embodiments, the processor (302) configures a plurality of location service profiles. Each of the plurality of location service profiles includes at least one location determination method, at least one service quality parameter, at least one mapping to at least one location service producer, at least one application service type, at least one service area type, or a combination thereof. In various embodiments, the receiver (312) receives a location request from a location service consumer. Based on this location request, the processor (302) determines a first mapping of at least one application of at least one user device to a first location service profile among the plurality of location service profiles. In some embodiments, the transmitter (310) transmits the first mapping and the first location service profile to at least one location service producer. In certain embodiments, the processor (302) determines a fused location estimate for the first location service profile.

[0037] In certain embodiments, "LCS (location services)" is part of the "3GPP (third generation partnership program)" architecture and "RAN (radio access network)" framework that enables the identification and standardized reporting of location information of "UEs (user equipment's)" and / or groups of UEs. Location information may be exposed to users, "ME (mobile equipment), network operators, service providers, value-added service providers, and internal operations of "PLMN (public land mobile network)." In some embodiments, the LCS framework may be used for all different types of location information.

[0038] In various embodiments, the positional "API (application programming interface)" may be provided to vertical devices that may have completely different "NW (network) handling capabilities and requirements for different scenarios. Different API exposures for different configurations may use additional signaling and / or complexity on the network or application side to provide the required "QoS (quality of service)."

[0039] In certain embodiments, location exposure can be performed based on different vertical requirements (e.g., which may vary dynamically over time and area) without imposing additional complexity on vertical applications.

[0040] In some embodiments, an "MNO" (mobile network operator) and / or a third-party "SP" (service provider) may dynamically provide customized value-added location services (e.g., location augmentation, location prediction) as APIs to improve vertical user experience and / or vertical server awareness.

[0041] In various embodiments, if there is a mix of non-3GPP and 3GPP positioning methods, the positioning methods can be integrated and negotiated.

[0042] In certain embodiments, location services may be dynamically provided in edge and / or "MEC (mobile edge computing) environments by a combination of minimum complexity and / or signaling and location methods.

[0043] In some embodiments, off-network location support for verticals can be efficiently handled (e.g., UE-to-UE("PC5") communication can be used for some out-of-coverage scenarios; however, assuming authorized resources and multi-operator vertical services, location reporting can be performed by NW and / or middleware).

[0044] In various embodiments, in addition to data communications that can increase the complexity of the LCS framework and corresponding interactions between 3GPP and non-3GPP entities, there may be various use cases, verticals, scenarios, and application services using LCS (e.g., V2X (vehicle to everything), IIoT (industrial internet of things), UAS (unmanned aerial system)). Location-related KPIs (key performance indicators) of various use cases may require various accuracy levels (e.g., horizontal, vertical, 2D (two-dimensional), 3D (three-dimensional)), and different location-fixed latency requirements, availability requirements, speed, and / or course.

[0045] In certain embodiments, there may be an integrated framework using an LCS profile that considers a set of attributes to meet specific requirements for use cases and / or application services across MNOs, verticals, and third-party operators. An LCS profile solution may include 1) configuration and signaling of the LCS profile; and / or 2) the use of middleware to convert location requests from vertical applications into an LCS profile and provide value-added services to the verticals.

[0046] In some embodiments, handling API calls from vertical customers and matching them to northbound APIs per LCS profile can facilitate vertical integration into "5GS" (fifth generation system) and enable faster time location reporting (e.g., one location API may be provided to the vertical API); however, multiple LCS profiles (e.g., which may be "hidden" from customers) may be negotiated and consumed by middleware.

[0047] In various embodiments, location services are a type of service that can be provided by a mobile communication system. Location-based services can serve specific vertical industries or can be provided for target applications.

[0048] In certain embodiments, location-based services may include emergency services, emergency alert services, people tracking, vehicle management, asset management, traffic congestion reporting, roadside assistance, routing to the nearest commercial enterprise, traffic and public transport information, city tourism, localized advertising, mobile yellow pages, weather, and / or asset and service discovery.

[0049] In some embodiments, an LCS session associated with an LCS profile can be defined and configured, and can be performed with minimal exposure to third parties and / or customers. Without these embodiments, the application server may need to integrate all measurements and interact with different systems to obtain the required location. The LCS profile can help optimize location determination based on the environment and UE context, and can facilitate profile checking and / or monitoring.

[0050] In various embodiments, the steps of defining and / or configuring an LCS profile may include converting a vertical request into an LCS profile and deriving a requested location report. In certain embodiments, a "location service enabler (LSE) server and / or device may fetch location reports in an iterative manner and / or based on priorities to facilitate the satisfaction of vertical requirements with minimal signaling and / or complexity.

[0051] FIG. 4 is a block diagram illustrating one embodiment of a system (400) for application to LCS profile mapping. The system (400) includes an "N3GPP" (non-3GPP) "LSP" (location service producer) (402), a 3GPP LSP (404) (e.g., a 3GPP-based LSP, "LMF" (location management function), "RAN" (radio access network), "SEAL" (service enabler application layer), "LSE" (location service enabler) (406) (and / or middleware), and an "LSC" (location service consumer) (408) (e.g., a vertical application, "AF" (application function)). As may be recognized, any of the communications described herein may include one or more messages. It should be noted that a location service consumer may be a UE or a group of UEs within a service area.

[0052] Steps 410 through 434 describe initial mapping and transformation, and steps 436 through 442 provide re-mapping due to application changes and / or monitoring.

[0053] In the first communication (410), the LSE (406) receives a new location request from the LSC (408) (e.g., a vertical application). This location request may include requirements regarding location granularity, reporting, response time, end-to-end location latency (e.g., time to first fixation), etc.

[0054] The LSE (406) maps an application "ID" (identifier) ​​(e.g., "VAL" (vertical application layer) server ID, external UE ID, group ID, etc.) or a service ID and / or type to an LCS profile from an available list of LCS profiles (412) (e.g., may be pre-configured by a location service provider and / or MNO). This mapping includes: 1) application service type (e.g., corresponding to different applications based on vertical use cases); 2) environment or service area type (e.g., indoor, outdoor, urban, suburban, etc.); 3) QoS requirements (e.g., accuracy); 4) capabilities of the accompanying UEs; 5) energy constraints for devices; 6) time validity for requests; 7) service and / or slice profiles of the application; 8) preference for specific location methods (e.g., RAT-dependent (e.g., 3GPP-based location methods) or RAT-independent methods); 9) LCS service levels (e.g., for IIoT verticals); 10) priorities of location methods; and / or 11) loading of location functions involved in the process may be considered.

[0055] Table 1 illustrates one example of mapping information.

[0056]

[0057] In the second communication (414) of the options, there may be a configuration of LCS producers having the required location methods per LCS profile and a mapping to the application (e.g., to know capabilities and / or approvals). This may include the configuration of LMF, RAN-LMC, UE-LCS, and / or SEAL "LMC" (location management component) along with information on which method to use and with what priority.

[0058] In the third communication (416), the LSE (406) (e.g., based on an application LCS profile) transmits a location request and / or subscription to one or more of the 3GPP defined functions (e.g., based on the required location methods): 1) an application of the UE (or a group of UEs based on the profile)—which may be an LSE client activated on the UE side—such a request may include additional data such as UE mobility, route, etc.; 2) an LMF via the "NEF" (network exposure function) or via the GMLC and / or "LRF" (location retrieval function); 3) a RAN and / or RAN LCS—the LSE may request this indirectly through the UE modem (e.g., from the LSE to the LCS, from the UE to the RAN); and / or 4) a SEAL "LMS" (location management server) via the SEAL API (e.g., an LSE acting as a VAL server).

[0059] In the fourth communication (418), the LSE (406) receives location responses and / or reports based on these requests: 1) applications of the UE (or a group of UEs based on the profile); 2) LMF; 3) RAN and / or RAN LCS - the RAN may provide these indirectly through a UE modem (e.g., RAN-to-LCS UE-to-LSE client-to-LSE server); and / or 4) SEAL LMS.

[0060] LSE (406) can request from all functions simultaneously, or sequentially and conditionally, depending on whether the requirements are met. LSE (406) can check after receiving all reports (420) and decide whether to perform additional requests. LSE (406) can proceed in descending order, starting from the function with the highest priority. LSE (406) can perform location estimation processing and determine additional input and / or processing based on the LCS profile.

[0061] LSE (406) checks whether LCS requirements (e.g., QoS requirements) are met (422) and evaluates whether additional action is required. In particular, such additional action may be one of the following: 1) requesting location reports from non-3GPP systems (e.g., based on the LCS profile) or from application servers and / or clients (e.g., via GPS, Bluetooth, motion sensors, etc., from "WLAN" (wireless local area network), "GNSS" (global navigation satellite system), etc.); 2) location verification through multiple sources (e.g., this may be useful in UAS scenarios if the "UAV" (unmanned aerial vehicle) reported location is unreliable); 3) location augmentation (e.g., by 3D live maps, etc.); 4) Check the locations of all and / or additional UEs within that area and / or proximity (e.g., because the expected location of a UE may be correlated with other UEs in that area (e.g., UEs located in a rectangular grid such as a zone); 5) Use analysis and / or historical data to increase precision; 6) Take input regarding the location of the target UE from other UEs in the area; and / or 7) Group-based localization.

[0062] In the optional fifth communication (424), optional sixth communication (426), optional seventh communication (428), and optional ninth communication (430), if the action requires information from location reports, the LSE (406) requests and / or receives location reports and / or supplementary information from one or more of the UE's apps, RAN, LMF, SEAL and / or non-3GPP systems.

[0063] LSE (406) calculates the location estimates of the UEs of the application (e.g., actual location, expected location, estimated location) (432) and transmits the location information to the vertical application server in the 10th communication (434). This may be a one-time event or may occur periodically and / or based on trigger events.

[0064] Steps 436 through 442 describe the trigger event and the procedure for adaptation.

[0065] In the first communication (436), the LSE (406) can monitor the location of app#1 (e.g., along a path) and, if the location QoS cannot be satisfied, if the service profile mapping changes, if the location and / or mobility of the UE changes, or if the application is expected to be relocated to a different "DNN" ("DN" (data network) name) or slice, it can trigger an update of the mapping of app#a to the LCS profile.

[0066] When the trigger comes from the application, the LSE (406) receives the application-to-service profile remapping or the expected change in application requirements (e.g., location accuracy and / or QoS). When the trigger comes from monitoring, the monitoring capability in the LSE is required to trigger an action (438) which is an adaptation of an attribute (e.g., UE moving from the outdoors into the tunnel).

[0067] In the 12th communication (440), the LSE (406) repeats steps 412 through 434 to update the LCS profile and inbound report to ensure that location requirements are met (e.g., update remapping).

[0068] One example of an updated mapping is shown in Table 2, where intersecting elements are removed from the profile and other elements are added.

[0069]

[0070] In the 13th communication (442), if such a change was triggered by the application, the LSE (406) provides the application with a report and / or response indicating the change in the report and / or profile.

[0071] Certain embodiments include techniques for performing mapping and conversion between an LSE client and an LSE server located within the VAL UE.

[0072] In the first embodiment, LCS profile mapping and transformation may be performed by an LSE server. In the first embodiment, the LCS profile is configured by and / or for telecommunications operators and / or providers (e.g., MNOs or cloud providers). LSE-S may be an enhancement of SEAL LMS or a new entity.

[0073] FIG. 5 is a block diagram illustrating another embodiment of a system (500) for application to LCS profile mapping. The system (500) includes applications (502) (e.g., connected by GPS, Bluetooth, etc.), an LSE client (504), a UE-LCS client (506), a RAN (508), an LMF (510) (e.g., "5GC" (fifth generation core) LMF, "GLMS" (global location management system)), a SEAL LMS (512), an LSE server (514) ("LSE-S"), a VAL server (516), and a non-3GPP access network (518) (e.g., trusted, untrusted). The applications (502), the LSE client (504), and the UE-LCS client (506) may all be part of a VAL UE. As may be acknowledged, any of the communications described herein may include one or more messages.

[0074] In the first communication (520), a location request message may be transmitted from the VAL server (516) to the LSE server (514). The location request message may include a VAL server ID, an application ID, an application type, location QoS requirements (e.g., accuracy, response time, etc.), location granularity (e.g., coordinates, cell-level, civic addresses, topological location), vertical specific support information (e.g., planned route, road map, etc.), time validity for requirements, valid area, predictive location service, service profile, device capabilities (e.g., GPS receiver, supported "RATs" (radio access technologies), supported location method), power constraints, time expiration for the request, minimum time between consecutive reports, and / or event triggering criteria (e.g., location reports need to be transmitted under the criteria).

[0075] LSE-S (514) performs mapping of applications to LCS profiles (e.g., based on IDs received in step 520) (522).

[0076] An LCS profile (or profiles) includes one or more of the following attributes: vertical, use case, environment, location service level (e.g., for IIoT), LCS QoS parameters and / or accuracy, supported location methods, priorities and / or preferences of location methods, associated 3GPP functionalities and priorities, associated non-3GPP access networks (e.g., trusted, untrusted), required APIs and / or API information, location verification flags, location augmentation flags, and / or group-based location flags.

[0077] Mapping may consider 1) application service type; 2) environment (e.g., indoor, outdoor, urban, suburban, etc.); 3) QoS requirements (e.g., accuracy); 4) capabilities of the accompanying UEs; 5) energy constraints for the devices; 6) time validity for the request; 7) service and / or slice profile of the application; 8) preference for specific location methods (e.g., RAT-dependent or RAT-independent methods); 9) LCS service level (e.g., for IIoT verticals); 10) priorities of location methods; and / or 11) loading of location functions accompanying the process.

[0078] One exemplary method for mapping an application to an LCS profile is to match the context information received in step 520 with the attributes of the LCS profile and further check the loading of the LCS profiles (e.g., the loading of LCS profiles affecting the loading of each location service provider function). Mapping policies (e.g., based on application type) can be pre-configured based on vertical and / or OAM.

[0079] In a second communication (524) (e.g., a set of communications from LSE-S (514)), LSE-S (514) configures the 3GPP functions and the application enabler client in the UE involved in mapping the application to an LCS profile and configuring reports corresponding to the application's LCS profile. This configuration includes the following parameters: 1) UE ID, a list of UE IDs, a group ID, a service ID, a VAL server ID, and / or an application type; 2) a mapping of app#1 to LCS profile #x (e.g., this may also be a sequence of mappings for app#1, such as along a UE path); 3) a report configuration (e.g., event triggering, periodicity of the report, format of the report, thresholds for minimum time between consecutive reports); 4) priority of location methods; 5) location report granularity (e.g., coordinates, cell-level, civic addresses, topology location); 6) LCS profile attributes (e.g., if not already known by the associated entity); and / or 7) may include at least one of time validity and / or valid region for such configuration. In some embodiments, step 524 may occur before step 520 (e.g., at the time the application registers with LSE-S (514)).

[0080] In the third communication (526, 530, 534, and 538), the LSE-S (514) performs a location request for one or more of the following: 1) to a SEAL LMS acting as a VAL server to request location information for one or more UEs (e.g., VAL-triggered location report triggers)—such report triggers may also be enhanced to display LCS profile IDs and the locations of all UEs having such LCS profiles in these areas; 2) to an LMF and / or "GMLC (gateway mobile location center)" directly or via an NEF acting as an AF—the LCS service request is transmitted to the GMLC and / or LMF or AMF via the NEF using a service-based interface or a "CAPIF (common API framework) API, or directly to the GMLC if permitted (e.g., for an LSE-S within an MNO trust domain); 3) Relating to the RAN and / or RAN-LMC – such requests may be transmitted to a RAN function that calculates the location for one or more UEs – and such requests may include an app ID, location QoS requirements (e.g., absolute and relative horizontal and vertical accuracy, response time), location methods and priorities related to location methods and associated location measurements, requests for location information for all UEs with the same profile, the number of locations for a specific UE, confidence intervals, alert limits, alert duration, targets, and integrity of the location estimate, such as integrity risk;4) Regarding the UE's application (e.g., LSE-S, "SEAL-C" ("SEAL" (server enabler application layer) "C" (client))) – these requests may be similar to location information requests and may be enriched to include the LCS profile ID (e.g., if the app-profile mapping is not transmitted in step 524), as well as requests for location reporting for other UEs in close proximity within the same service and / or profile; and / or 5) Regarding the MEC platform by calling the location API – these requests may be enriched to include the LCS profile ID and configuration information (e.g., if the MEC capability does not recognize the profiles).;

[0081] In the fourth communication (528, 532, 536, and 540), the LSE-S (514) receives a location response (e.g., including a location report) from the entities requested in step 526, which provides location information and / or estimates based on the requested granularity (e.g., coordinates, cell level, civic address, etc.), timestamp, triggering event (e.g., if the request is only about transmitting a location report in the case of an event), whether the UE's actual or predicted location is, and / or the reliability of the provided location estimate, and / or associated confidence interval or associated metric.

[0082] LSE-S (514) performs location report processing (542) and checks whether the received location information satisfies the LCS profile requirements (e.g., based on QoS parameters such as accuracy and / or response time). If the information satisfies the requirements, the method moves to step 554.

[0083] If the information does not meet the requirements, LSE-S (514) performs additional processing based on the context received in step 520 and the received location reports (544) and rechecks the fused location estimate. The additional processing may include: 1) location augmentation (e.g., by 3D live maps, etc.); 2) analysis and / or use of historical data to increase precision; and / or 3) one or more of UE and / or group UE mobility information.

[0084] In an optional fifth communication (546), if steps (542 and 544) do not provide the requested LCS (or if LSE-S (514) does not have up-to-date information regarding the application context), LSE-S (516) requests supplementary information related to UE location from one or more 3GPP entities as LSE-clients, or from a MEC platform via a MEC API, SEAL LMS and / or LMC, LMF and / or AMF, "NWDAF" (network data analytics function) in the UE.

[0085] In an optional sixth communication (548), the LSE-S (514) receives supplementary information based on a request. The information may include actual and / or predicted UE mobility, locations for all and / or additional UEs within an area and / or proximity, UE locations by other sources for location verification (e.g., may be used for UAS-related profiles), "HD" (high definition) maps for a specific area, augmented locations, relative locations between UEs within an application (e.g., between a drone and a pilot, between vehicles in a platoon), and location requests for one UE to be provided on behalf of other UEs (e.g., a group leading to the collection and transmission of other UE locations).

[0086] In an optional seventh communication (550A), an optional eighth communication (550B), an optional ninth communication (552A), and an optional tenth communication (552B), the LSE-S (514) checks whether the LCS profile requirements for the application are met. If the requirements are not met, the LSE-S (514) and / or the LSE client (504) provide this information and request non-3GPP domains to receive location information.This may be achieved through one or more of three methods: 1) as indicated in UE-assisted and UE-based location procedures via N3IWF, TNGF, and / or "W-AGF (wireless access gateway function)" or via the application layer (e.g., an interface out of 3GPP coverage) - when interacting with an N3GPP access network, the reported location information depends on whether it is trusted - and such information may include the UE local "IP (internet protocol) address or the UE and / or N5CW device local IP address, in the case of WLAN access, the attached AP's "BSSID (basic service set identifier)" or the detected AP's BSSID, and / or civic address and / or geospatial location information; 2) via N3IWF, TNGF, and / or W-AGF or via the application layer (e.g., an interface outside the 3GPP scope), such as a network-assisted positioning procedure—this information may be the UE and / or N5CW device local IP address and optionally a "UDP (user datagram protocol)" or "TCP (transmission control protocol)" source port, and a "TNAP (trusted non-3GPP access point)" and / or "TWAP (trusted WLAN access proxy)" ID (e.g., for trusted devices); and / or 3) indirectly requesting UE position information via a SEAL LMC and / or LSE client (e.g., from a "GPS (global positioning system)" receiver, Bluetooth receiver, etc.).

[0087] LSE-S (514) calculates a fused location estimate based on the previous steps (554) and checks whether the requested location QoS is satisfied (e.g., based on the LCS profile).

[0088] In the 11th communication (556), LSE-S (514) reports location information to the VAL server (516).

[0089] One possible flowchart for the procedure described in FIG. 5 is illustrated in FIG. 6 and described in this specification.

[0090] In steps 558 through 564, events that may be provided by the application-side, by the network, by the OAM, and / or the UE may trigger the remapping of the application to a different LCS profile. Such trigger events may result from a change in environment (e.g., from indoors to outdoors), a change in the service profile for the application (e.g., a change in the service operation level), a change in the availability of the location service profile in the target area, a change in the location service profile area, or mobility events that may require the relocation of the application to a different DN and / or slice. In certain embodiments, if there is a mismatch between the application requirements for the LCS and the LCS profile, the LSE server may be able to adapt the mapping to facilitate the fulfillment of the location QoS requirements.

[0091] If the trigger originates from OAM, the trigger can affect the re-mapping of all applications for different LCS profiles in target geographic or topological regions (e.g., cell regions, trace regions) or slice instances.

[0092] In the 12th communication (558), the LSE-S (514) can monitor the location of app#1 (e.g., along a path) and, if the location QoS cannot be satisfied, if the service profile mapping changes, if the location and / or mobility of the UE changes, or if the application is expected to be relocated to a different DNN or slice, it can trigger an update of the mapping of app#a to the LCS profile. When the trigger comes from the application, the LSE-S (514) receives the application-to-service profile remapping, or the expected change in application requirements (e.g., location accuracy and / or QoS).

[0093] If the trigger comes from monitoring, monitoring capability in LSE-S (514) may be required, and an action (560) that may be an adaptation of an attribute (e.g., UE moving from the outside into the tunnel) may be triggered.

[0094] In the 13th communication (562), LSE-S (514) may repeat steps (522 to 556) to update the LCS profile and inbound report to facilitate the fulfillment of location requirements.

[0095] In the 14th communication (564), if the change was triggered by the application, LSE-S (514) provides the application with a report and / or response indicating the change in the report and / or profile.

[0096] FIG. 6 is a flowchart illustrating one embodiment of a method (600) for verifying requirements. The method (600) includes the step (602) of mapping an application (e.g., app#1) to an LCS profile (e.g., LCS profile #x). The method (600) further includes the step (604) of requesting and / or receiving location reports from high-priority LCS producers (e.g., based on profile #x). The method (600) includes the step (606) of determining whether the reports satisfy requirements (e.g., QoS requirements). If the reports satisfy the requirements, the method (600) includes the step of terminating (608) and / or transmitting location information to a VAL server. If the reports do not satisfy the requirements, the method (600) includes the step (610) of placing the next LCS producer at a first-priority location (e.g., based on profile #x). Next, the method (600) returns to step 604 until there are no more LCS producers and / or a time threshold is reached.

[0097] When there are no more LCS producers and / or a time threshold is reached, the method (600) performs additional processing on the profile and / or application (e.g., using location augmentation, analysis, and / or supplementary information) (612). The method (600) determines whether the process location estimate meets the requirements (614). If the process location estimate meets the requirements, the method (600) performs step 608. If the process location estimate does not meet the requirements, the method (600) requests (616) and receives reports from non-3GPP access points and returns to step 612.

[0098] In the second embodiment, LCS profile mapping can be performed by an LSE client (e.g., on the device side based on the LSE server configuration - the LSE client resides in the VAL UE).

[0099] FIG. 7 is a block diagram illustrating an additional embodiment of a system (700) for application to LCS profile mapping. The system (700) includes a first VAL UE (e.g., VAL UE #1) comprising a first application (702) (e.g., app#1), a first LSE client (704) (e.g., and / or SEAL LMC), and a first UE-LCS client (706). The system (700) also includes a second VAL UE (e.g., VAL UE #2) comprising a second application (708) (e.g., app#2), a second LSE client (710), and a second UE-LCS client (712). The system (700) includes a non-3GPP access network (714), a RAN (716) (e.g., or CN, SEAL, MEC), and an LSE server (718) (LSE-S). As may be acknowledged, any of the communications described in this specification may include one or more messages.

[0100] In the first communication (720) and the second communication (722), the LSE-S (718) configures LSE clients on the UE side for mapping applications to LCS profiles and configuring reports corresponding to the applications' LCS profiles. This configuration may be in the form of a request and includes the following parameters: 1) UE ID, a list of UE IDs, a group ID, a service ID, a VAL server ID, and / or an application type; 2) a predetermined mapping of app#1 to LCS profile #x (e.g., this may be a sequence of mappings for app#1, such as along a UE path); 3) a report configuration (e.g., event triggering, periodicity of the report, format of the report, thresholds for minimum time between consecutive reports); 4) priority of location methods; 5) location report granularity (e.g., coordinates, cell-level, civic addresses, topology location); 6) LCS profile attributes (e.g., if not already known by the associated entity); and / or 7) may include at least one of time validity and / or validity area for such configuration. Next, the LSE client may send back a response message (e.g., "ACK" (acknowledgement) and / or "NACK" (negative acknowledgement)) to notify of the success of the configuration.

[0101] In an optional third communication (724), the first LSE client (704) configures the LSE profiles of other UEs and / or LSE clients in proximity and / or within the same group within the service and / or application.

[0102] In the fourth communication (726), a location request message is transmitted from the first application (702) in the UE to the first LSE client (704) and includes one or more of an application ID, application type, location QoS requirements (e.g., accuracy, response time, etc.), location granularity (e.g., coordinates, cell level, civic address, topology location), vertical specific support information (e.g., planned route, road map, etc.), time validity for requirements, valid area, predictive location service, service profile, device capability (e.g., GPS receiver, supported RAT, supported location method), power constraints, time expiration for the request, minimum time between consecutive reports, and / or event triggering criteria (e.g., location reports need to be transmitted under the criteria).

[0103] The first LSE client (704) performs mapping of the application to an LCS profile (728) (e.g., based on the ID received in steps 720 and 722).

[0104] LCS profiles include one or more of the following attributes: vertical, use case, environment, location service level (e.g., for IIoT), LCS QoS parameters and / or accuracy, supported location methods, priorities and / or preference of location methods, integrity and reliability of location estimates, associated 3GPP functionalities and priorities, associated non-3GPP access networks (e.g., trusted, untrusted), required APIs and / or API information, location verification flags, location augmentation flags, and / or group-based location flags.

[0105] Mapping may consider 1) application service type; 2) environment (e.g., indoor, outdoor, urban, suburban, etc.); 3) QoS requirements (e.g., accuracy); 4) capabilities of the accompanying UEs; 5) energy constraints for the devices; 6) time validity for the request; 7) service and / or slice profile of the application; 8) preference for specific location methods (e.g., RAT-dependent or RAT-independent methods); 9) LCS service level (e.g., for IIoT verticals); 10) priorities of location methods; and / or 11) loading of location functions accompanying the process.

[0106] One exemplary method for mapping an application to an LCS profile is to match the context information received in step 726 with most of the attributes of the LCS profile and additionally check the loading of the LCS profiles (e.g., the loading of the LCS profiles affects the loading of each location service provider function). Mapping policies (e.g., based on application type) can be pre-configured based on vertical and / or OAM.

[0107] In the fifth communication (730), the second "LSE-C (LSE client) (704) may transmit a mapping of an application to an LCS profile (e.g., based on the ID received in steps 720 through 724) to other UEs and / or LSE clients within the service and / or application, adjacent to and / or within the same group (e.g., configured with an LSE profile in 724).

[0108] In the sixth communication (732), if VAL UE #1 has an LCS client, it may also fetch location information locally from the first UE-LCS client (706) (e.g., depending on the implementation regarding how this is received in the first LSE-C (704)).

[0109] In the seventh communication (734), the first LSE-C (704) performs a location request for one or more of the following: 1) to the LMF and / or GMLC via the AF and via the NEF – the LCS service request is transmitted to the NEF via the AF (e.g., SEAL LMS and / or LSE-S) and from the AF to the GMLC and / or LMF or AMF, via the NEF using a service-based interface or CAPIF API, or directly to the GMLC if permitted; 2) to the RAN – such a request may be transmitted to a RAN function that calculates the location for one or more UEs – and such a request may include an application ID, location QoS requirements (e.g., absolute and relative horizontal and vertical accuracy, response time), location methods and priorities related to the location methods and associated location measurements, a request for location information for all UEs having the same profile, the number of location estimates for a specific UE, the integrity of the location estimate, confidence intervals, alarm limits, alarm time, target and / or integrity risk; 3) Regarding applications of the UE – these requests may be similar to location information requests and may be strengthened to include an LCS profile ID (e.g., if the application mapping to the profile is not transmitted in step 726), as well as requests for location reporting for other UEs in close proximity within the same service and / or profile; and / or 4) Regarding the MEC platform by calling a location resolution API (e.g., from an LSE client to a MEC location resolution service) – these requests may be strengthened to include an LCS profile ID and configuration information (e.g., if the MEC capability does not recognize the profile).

[0110] In the eighth communication (736), the first LSE-C (704) receives a location response (e.g., including a location report) from the entity requested in step 736, and this response provides location information and / or estimates based on the requested granularity (e.g., coordinates, cell level, civic address, etc.), timestamp, triggering event (e.g., if the request is only about transmitting a location report in the case of an event), whether the UE's actual location or predicted location, and associated confidence interval or associated metric indicating the reliability of the provided location estimate.

[0111] The first LSE-C (704) checks whether the received location information satisfies the LCS profile requirements (e.g., based on QoS parameters such as accuracy and / or response time) (738). If the requirements are satisfied, proceed to step 752.

[0112] If the requirements are not met, the first LSE-C (704) performs additional processing based on the context and received location reports received in steps (720 to 724) (740); and checks the fused location estimate. The processing may include 1) using location augmentation such as 3D live maps; 2) using analysis and / or historical data to increase precision; and / or 3) UE and / or group UE mobility information.

[0113] In the ninth communication (742), if steps (738 and 740) do not provide the requested LCS (or if the LSE-C does not have the latest information regarding the application context), the first LSE-C (704) requests supplementary information regarding UE location from all and / or additional UEs in the UE's area and / or proximity area via group cast and / or broadcast messages to all users in the LCS profile or in a given area.

[0114] In the 10th communication (744), the 1st LSE-C (704) receives supplementary information based on the request.

[0115] In optional first communication (746) and optional second communication (748), the first LSE-C (704) rechecks whether the LCS profile requirements for the application are met. If the profile requirements are not met, the first LSE-C (704) requests the non-3gpp access network (e.g., WLAN) to provide this information and receive location information. When interacting with the N3GPP access network, the reported location information depends on whether it is trusted. This information may be the UE local IP address or the UE and / or "N5CW" (non 5G compatible over WLAN) device local IP address, in the case of WLAN access, the BSSID of the attached AP or the BSSID of the detected AP, civic address and / or geospatial location information.

[0116] The first LSE-C (704) calculates a fused position estimate based on the previous steps (750) and checks whether the requested position QoS is satisfied (e.g., based on the profile).

[0117] In the 13th communication (752), the 1st LSE-C (704) reports location information to the 1st application (702).

[0118] In the third embodiment, LSE functionality can enhance the functionality (or new services) of LMF and / or GMLC based on deployment on the network side.

[0119] FIG. 8 is a block diagram illustrating another embodiment of a system (800) for application to LCS profile mapping. The system (800) includes a UE (802), an N3IWF (non-3GPP inter-working function) (804) (e.g., and / or TNGF and / or W-AGF), a RAN (806), an AMF (808) (e.g., and / or GMLC and / or LMF and / or LSE function), a UDM (810), and an external LCS client (812) (e.g., AF, application). As may be recognized, any of the communications described herein may include one or more messages.

[0120] In the first communication (814), there may be an LCS profile configuration.

[0121] In the second communication (816), a location request (e.g., including subscription to location events) comes from an external LCS client (812). The AMF (808) can receive non-UE associated contexts and / or measurements and can support location augmentations.

[0122] In the third communication (818), the AMF (808) retrieves an application-to-LCS profile mapping from the UDM (810). Here, the AMF (808) or the UDM (810) maintains a mapping between the application and / or UE and the LCS profile. The LCS profile provides location access types, methods, QoS, etc.

[0123] The AMF (808) configures the required reports, which entities to request reports from, and which priorities to set (820). The AMF (808) also considers the priorities of different location methods based on the LCS profile. The AMF (808) may also consider the UE's "RRC" (radio resource control) status to configure an energy-efficient location method, which may or may not affect the achievable accuracy.

[0124] In the fourth communication (822), the AMF (808) transmits a location request having an LCS profile ID and / or a UE ID to the RAN (806). The fourth communication (822) can be performed by the AMF (808) through a network location message transmitted to a serving "NG-RAN" ("NG" (next generation) RAN) node in the N2 transmission message.

[0125] The RAN (806) calculates (824) and / or obtains arbitrary location information for a profile and / or UE. The RAN (806) returns the arbitrary location information obtained to the AMF (808) in the fifth communication (826). This can be done through the AMF (808) in a network location message included in an N2 transmission message (e.g., between the RAN (806) and the AMF (808)) and from the AMF (808) to the LSE through a service-based interface.

[0126] In the sixth communication (828), the AMF (808) transmits a location request to the N3IWF (804) having a UE ID and optionally an LCS profile ID and / or information. This can be done by the AMF (808) via a network location message to the serving N3IWF (804).

[0127] N3IWF (804) calculates and / or obtains arbitrary location information for a profile and / or UE (829). In the seventh communication (830), N3IWF (804) returns the obtained arbitrary location information to AMF (808). The reported location information depends on whether it is trusted. This information may be the UE local IP address or the UE and / or N5CW device local IP address, in the case of WLAN access, the BSSID of the attached AP or the BSSID of the detected AP, civic address, and / or geospatial location information.

[0128] In the eighth communication (832), the AMF (808) transmits a location request having an LCS profile ID and / or information to the UE (802) (e.g., to the UE (802) via a downlink location message in a DL "NAS" non-access stratum transmission message).

[0129] The UE (802) stores any auxiliary data provided in the downlink positioning message (834) and performs any positioning measurement and / or position calculation requested by the downlink positioning message. In the ninth communication (836), the UE (802) transmits an uplink positioning message included in a NAS transmission message to the AMF (808) (e.g., to acknowledge the downlink positioning message) and returns any positioning information or any capabilities based on the profile.

[0130] AMF (808) checks whether the received location information satisfies the LCS profile requirements (based on QoS parameters such as accuracy and / or response time, for example) (838).

[0131] If the requirements are not met, the AMF (808) performs additional processing based on the context received at step 816 and the received location reports (840) and rechecks the fused location estimate. This processing may include 1) location augmentation using 3D live maps; 2) using analysis and / or historical data to increase precision; and / or 3) UE and / or group UE mobility information.

[0132] In the 10th communication (842), if steps (832 to 836) do not provide the requested LCS (or if the LSE does not have the latest information regarding the app context), the AMF (808) requests and receives supplementary information.

[0133] AMF (808) calculates a fused location estimate based on the previous steps (844) and checks whether the requested location QoS is satisfied (e.g., based on the profile).

[0134] In the 11th communication (846), the AMF (808) reports location information to the external LCS client (812).

[0135] FIG. 9 is a flowchart diagram illustrating one embodiment of a method (900) for mapping applications and location service profiles. In some embodiments, the method (900) is performed by a device, such as a network unit (104). In certain embodiments, this method (900) may be performed by a processor executing program code, e.g., a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0136] In various embodiments, the method (900) includes the step (902) of configuring a plurality of location service profiles. Each of the plurality of location service profiles includes at least one location determination method, at least one service quality parameter, at least one mapping for at least one location service producer, at least one application service type, at least one service area type, or a combination thereof. In some embodiments, the method (900) includes the step (904) of receiving a location request from a location service consumer. In certain embodiments, the method (900) includes the step (906) of determining a first mapping of at least one application of at least one user device for a first location service profile among the plurality of location service profiles based on the location request. In various embodiments, the method (900) includes the step (908) of transmitting the first mapping and the first location service profile to at least one location service producer. In some embodiments, the method (900) includes the step (910) of determining a fused location estimate for the first location service profile.

[0137] In certain embodiments, the method (900) further comprises the step of receiving at least one location report corresponding to a first location service profile, and the at least one location report is derived through at least one radio access technology-dependent location determination method, at least one radio access technology-independent location determination method, or a combination thereof. In some embodiments, a fused location estimate for the first location service profile is determined based on at least one location report. In various embodiments, the method (900) further comprises the step of transmitting the fused location estimate to a location service consumer.

[0138] In one embodiment, the method (900) further includes the step of determining whether location service quality requirements are met based on fused location estimates. In certain embodiments, the method (900) further includes the steps of transmitting a request for supplementary information and receiving a response to the request for supplementary information. In some embodiments, the supplementary information includes actual user equipment mobility information, predicted user equipment mobility information, location information for user equipment within an area, user equipment location information obtained from an auxiliary source, a map for a specific area, augmented location information, relative location information between user equipment within an application, location request information, or some combination thereof.

[0139] In various embodiments, the method (900) further comprises the step of transmitting a fused location estimate to at least one user device within a service area, a user device group, or a combination thereof. In one embodiment, each of the plurality of location service profiles includes application information, user device context information, priority information, application programming interface information, location augmentation requirements, location prediction requirements, sidelink location determination assistance requirements, proximity-based location estimate requirements, location verification requirements, or some combination thereof. In specific embodiments, the method (900) further comprises the step of transmitting a request for location reporting to at least one location service producer based on the first location service profile.

[0140] In some embodiments, at least one location service producer includes a service enabler application layer location management server, a gateway mobile location center, a non-Gen 3 partnership program interworking function, a trusted non-Gen 3 partnership program gateway function, a wireless access gateway function, a mobile edge computing service, a radio access network, a user device, or a combination of some of these. In various embodiments, a location service consumer includes a vertical application server, an application function, a vertical enabler server, an application on the user device, an application enabler client, an external location service client, a network device, or a combination thereof. In one embodiment, the location service enabler is an application on the user device, a middleware application device, a network device, or a combination thereof.

[0141] In certain embodiments, the method (900) further comprises receiving a trigger event from at least one location service producer, an application entity, or a combination thereof; determining a second mapping of at least one application of at least one user device to a second location service profile among a plurality of location service profiles based on a first location service profile among a plurality of location service profiles and the trigger event; and transmitting the second mapping and the second location service profile to at least one location service producer. In some embodiments, the method (900) further comprises receiving at least one additional location report for the second location service profile, and the at least one additional location report is derived through at least one radio access technology-dependent location determination method, at least one radio access technology-independent location determination method, or a combination thereof.

[0142] In various embodiments, the method (900) further includes the step of determining a second fused location estimate for a second location service profile based at least partially on at least one additional location report. In one embodiment, the method (900) further includes the step of transmitting the second fused location estimate to a location service consumer.

[0143] In one embodiment, a method in a location service enabler comprises: configuring a plurality of location service profiles—each of the plurality of location service profiles comprises at least one location determination method, at least one service quality parameter, at least one mapping to at least one location service producer, at least one application service type, at least one service area type, or a combination thereof—; receiving a location request from a location service consumer; determining a first mapping of at least one application of at least one user device to a first location service profile among the plurality of location service profiles based on the location request; transmitting the first mapping and the first location service profile to at least one location service producer; and determining a fused location estimate for the first location service profile.

[0144] In certain embodiments, the method further comprises the step of receiving at least one location report corresponding to a first location service profile, wherein the at least one location report is derived through at least one radio access technology-dependent location determination method, at least one radio access technology-independent location determination method, or a combination thereof.

[0145] In some embodiments, the fused location estimate for the first location service profile is determined based on at least one location report.

[0146] In various embodiments, this method further includes the step of transmitting the fused location estimate to a location service consumer.

[0147] In one embodiment, this method further includes the step of determining whether location service quality requirements are met based on fused location estimates.

[0148] In certain embodiments, this method further includes the steps of transmitting a request for supplementary information and receiving a response to the request for supplementary information.

[0149] In some embodiments, supplementary information includes actual user equipment mobility information, predicted user equipment mobility information, location information for user equipment within an area, user equipment location information obtained from an auxiliary source, a map for a specific area, augmented location information, relative location information between user equipment within an application, location request information, or some combination thereof.

[0150] In various embodiments, this method further comprises the step of transmitting the fused location estimate to at least one user device within a service area, a group of user devices, or a combination thereof.

[0151] In one embodiment, each of the plurality of location service profiles includes application information, user equipment context information, priority information, application programming interface information, location augmentation requirements, location prediction requirements, sidelink location determination assistance requirements, proximity-based location estimate requirements, location verification requirements, or a combination of some of these.

[0152] In certain embodiments, this method further includes the step of transmitting a request for location reporting to at least one location service producer based on a first location service profile.

[0153] In some embodiments, at least one location service producer includes a service enabler application layer location management server, a gateway mobile location center, a non-3rd generation partnership program interworking function, a trusted non-3rd generation partnership program gateway function, a wireless access gateway function, a mobile edge computing service, a radio access network, user equipment, or a combination of some of these.

[0154] In various embodiments, a location service consumer comprises a vertical application server, an application function, a vertical enabler server, an application of a user device, an application enabler client, an external location service client, a network device, or a combination thereof.

[0155] In one embodiment, the location service enabler is an application of the user equipment, a middleware application device, a network device, or a combination thereof.

[0156] In certain embodiments, the method further comprises: receiving a trigger event from at least one location service producer, an application entity, or a combination thereof; determining a second mapping of at least one application of at least one user device to a second location service profile among a plurality of location service profiles based on a first location service profile among a plurality of location service profiles and the trigger event; and transmitting the second mapping and the second location service profile to at least one location service producer.

[0157] In some embodiments, the method further comprises the step of receiving at least one additional location report for a second location service profile, wherein the at least one additional location report is derived through at least one radio access technology-dependent location method, at least one radio access technology-independent location method, or a combination thereof.

[0158] In various embodiments, this method further includes the step of determining a second fused location estimate for a second location service profile based at least partially on at least one additional location report.

[0159] In one embodiment, this method further includes the step of transmitting a second fused location estimate to a location service consumer.

[0160] In one embodiment, the device includes a location service enabler. The device further comprises: a processor for configuring a plurality of location service profiles—each of the plurality of location service profiles comprises at least one location determination method, at least one service quality parameter, at least one mapping to at least one location service producer, at least one application service type, at least one service area type, or a combination thereof—; a receiver for receiving a location request from a location service consumer—the processor determines a first mapping of at least one application of at least one user device to a first location service profile among the plurality of location service profiles based on the location request—; and a transmitter for transmitting the first mapping and the first location service profile to at least one location service producer; and the processor determines a fused location estimate for the first location service profile.

[0161] In certain embodiments, the receiver receives at least one location report corresponding to a first location service profile, and the at least one location report is derived through at least one radio access technology-dependent location determination method, at least one radio access technology-independent location determination method, or a combination thereof.

[0162] In some embodiments, the fused location estimate for the first location service profile is determined based on at least one location report.

[0163] In various embodiments, the transmitter transmits the fused location estimate to the location service consumer.

[0164] In one embodiment, the processor determines whether location service quality requirements are met based on fused location estimates.

[0165] In certain embodiments, the transmitter transmits a request for supplementary information and receives a response to the request for supplementary information.

[0166] In some embodiments, supplementary information includes actual user equipment mobility information, predicted user equipment mobility information, location information for user equipment within an area, user equipment location information obtained from an auxiliary source, a map for a specific area, augmented location information, relative location information between user equipment within an application, location request information, or some combination thereof.

[0167] In various embodiments, the transmitter transmits the fused location estimate to at least one user device within a service area, a group of user devices, or a combination thereof.

[0168] In one embodiment, each of the plurality of location service profiles includes application information, user equipment context information, priority information, application programming interface information, location augmentation requirements, location prediction requirements, sidelink location determination assistance requirements, proximity-based location estimate requirements, location verification requirements, or a combination of some of these.

[0169] In certain embodiments, the transmitter transmits a request for a location report to at least one location service producer based on a first location service profile.

[0170] In some embodiments, at least one location service producer includes a service enabler application layer location management server, a gateway mobile location center, a non-3rd generation partnership program interworking function, a trusted non-3rd generation partnership program gateway function, a wireless access gateway function, a mobile edge computing service, a radio access network, user equipment, or a combination of some of these.

[0171] In various embodiments, a location service consumer comprises a vertical application server, an application function, a vertical enabler server, an application of a user device, an application enabler client, an external location service client, a network device, or a combination thereof.

[0172] In one embodiment, the location service enabler is an application of the user equipment, a middleware application device, a network device, or a combination thereof.

[0173] In certain embodiments, a receiver receives a trigger event from at least one location service producer, an application entity, or a combination thereof; a processor determines a second mapping of at least one application of at least one user device to a second location service profile among a plurality of location service profiles based on a first location service profile among a plurality of location service profiles and the trigger event; and a transmitter transmits the second mapping and the second location service profile to at least one location service producer.

[0174] In some embodiments, the receiver receives at least one additional location report for a second location service profile, and the at least one additional location report is derived through at least one radio access technology-dependent location method, at least one radio access technology-independent location method, or a combination thereof.

[0175] In various embodiments, the processor determines a second fused location estimate for a second location service profile based at least partially on at least one additional location report.

[0176] In one embodiment, the transmitter transmits a second fused location estimate to a location service consumer.

[0177] The embodiments may be implemented in other specific forms. The described embodiments are not limiting in all respects and should be considered merely illustrative. Accordingly, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All modifications falling within the meaning and scope of the equivalents of the claims shall be included within such scope.

Claims

Claim 1 A method in a location service enabler, the method comprises: configuring a plurality of location service profiles, wherein each of the plurality of location service profiles comprises at least one location determination method, at least one service quality parameter, at least one mapping for at least one location service producer, at least one application service type, at least one service area type, or a combination thereof; receiving a location request from a location service consumer; determining a first mapping of at least one application of at least one user device for a first location service profile among the plurality of location service profiles based on the location request; transmitting a location request based on the first mapping and the first location service profile to the at least one location service producer; and determining a fused location estimate for the first location service profile based on at least one location report corresponding to the first location service profile received from the at least one location service producer in response to the transmitted location request. Claim 2 A method according to claim 1, wherein the at least one location report is derived through at least one radio access technology-dependent location determination method, at least one radio access technology-independent location determination method, or a combination thereof, and the fused location estimate for the first location service profile is determined based on the at least one location report. Claim 3 A method according to paragraph 2, further comprising the step of transmitting the fused location estimate to the location service consumer. Claim 4 A method according to paragraph 3, further comprising the steps of transmitting a request for supplementary information and receiving a response to the request for supplementary information. Claim 5 In paragraph 4, the supplementary information comprises actual user equipment mobility information, predicted user equipment mobility information, location information for user equipment within an area, user equipment location information obtained from an auxiliary source, a map for a specific area, augmented location information, relative location information between user equipment within an application, location request information, or a combination of some of these. Claim 6 In claim 5, each of the plurality of location service profiles comprises application information, user equipment context information, priority information, application programming interface information, location augmentation requirements, location prediction requirements, sidelink location determination assistance requirements, proximity-based location estimate requirements, location verification requirements, or a combination of some of these. Claim 7 A method according to claim 6, further comprising the step of transmitting a request for location reporting to at least one location service producer based on the first location service profile. Claim 8 In claim 7, the method wherein at least one location service producer comprises a service enabler application layer location management server, a gateway mobile location center, a non-3rd generation partnership program interworking function, a trusted non-3rd generation partnership program gateway function, a wireless access gateway function, a mobile edge computing service, a radio access network, user equipment, or a combination of some of these. Claim 9 In claim 8, the location service consumer comprises a vertical application server, an application function, a vertical enabler server, an application of the user equipment, an application enabler client, an external location service client, a network device, a remote device, a group of user equipment, or a combination thereof. Claim 10 In claim 9, the location service enabler is an application of the user equipment, a middleware application device, a network device, or a combination thereof. Claim 11 A method according to claim 10, further comprising: receiving a trigger event from at least one location service producer, application entity, network entity, or a combination thereof; determining a second mapping of at least one application of at least one user device to a second location service profile among a plurality of location service profiles based on a first location service profile among a plurality of location service profiles and the trigger event; and transmitting the second mapping and the second location service profile to the at least one location service producer. Claim 12 In claim 11, the method further comprises the step of receiving at least one additional location report for the second location service profile, wherein the at least one additional location report is derived through at least one radio access technology-dependent location determination method, at least one radio access technology-independent location determination method, or a combination thereof. Claim 13 A method according to claim 12, further comprising the step of determining a second fused location estimate for the second location service profile based at least partially on the at least one additional location report and transmitting the second fused location estimate to the location service consumer. Claim 14 A location service enabler comprising: a processor comprising a plurality of location service profiles, wherein each of the plurality of location service profiles comprises at least one location determination method, at least one service quality parameter, at least one mapping for at least one location service producer, at least one application service type, at least one service area type, or a combination thereof; a receiver receiving a location request from a location service consumer, wherein the processor determines a first mapping of at least one application of at least one user device for a first location service profile among the plurality of location service profiles based on the location request; and a transmitter transmitting a location request based on the first mapping and the first location service profile to the at least one location service producer; wherein the processor determines a fused location estimate for the first location service profile based on at least one location report corresponding to the first location service profile received from the at least one location service producer in response to the transmitted location request. Claim 15 In paragraph 14, the receiver receives a trigger event from at least one location service producer, an application entity, or a combination thereof; the processor determines a second mapping of at least one application of at least one user device to a second location service profile among a plurality of location service profiles based on a first location service profile among a plurality of location service profiles and a trigger event; and the transmitter transmits the second mapping and the second location service profile to the at least one location service producer.