OMA Location Working Group


The OMA LOC WG continues the work begun in the Location Interoperability Forum (LIF) and Location Drafting Committee of the WAP Forum. OMA LOC WG develops specifications to ensure the interoperability of Location Services on an end-to-end basis and provides technical expertise and consultancy on Location Services for other working groups across OMA. Additionally, the OMA LOC WG is responsible for End-To-End Architectural applications and content interfaces, including privacy, security, charging, billing, and roaming for location services. OMA LOC WG coordinates with other industry organizations, including 3GPP, 3GPP2, IETF NFC and GSMA, to ensure architectural conformance, security, and interoperability of specifications and to address new opportunities for collaboration across the mobile industry.

Bringing Value to the Mobile Industry and Public Safety

OMA LOC WG has made significant contributions to network operators in the public and private sectors to deliver a variety of reliable location enabled services. As wireless industry advances have made it commercially feasible to locate mobile stations on a mass scale, simultaneously, wireless operators continue to expand their ability to transport data. Examples of additional services include: Authorized Emergency Services seeking to locate residents in emergencies and mobile operators and application vendors wanting to provide location-enabled data and voice services.

To enable emergency and commercial services, several parties must cooperate in controlling and exchanging location data, including mobile operators, network infrastructure manufacturers, mobile terminal manufacturers, application developers, application service providers and geographic information service vendors. Different companies must cooperate to provide an interoperable End-to-End solution to meet increasing consumer demand for seamless roaming. OMA LOC WG provides a standard way to exchange location data, which will allow the entire industry to more readily satisfy emergency and commercial needs.

Specific OMA enablers for location services include OMA Secure User Plane Location (OMA SUPL) 1.0 and OMA SUPL 2.0, which are deployed ubiquitously across the industry. Currently, OMA SUPL 2.0 is used for both value added services as well as emergency services while OMA SUPL 1.0 is used for value added services. During 2011 the Global Certification Forum (GCF) certified more than 160 different mobile devices as compliant with OMA SUPL 1.0 specifications. Through September 2011, the PTCRB Certified 800 different mobile devices as compliant with OMA SUPL 1.0 specifications.

OMA Mobile Location Services—Mobile Location Protocol (OMA MLS-MLP) has wide deployment across the industry and provides a standard protocol between the location server and the application server. OMA MLP has been deployed as protocol for emergency call location retrieval in Europe, Canada and Japan.

OMA LPPe will gain importance as LTE networks take off worldwide. OMA LPPe 1.0 provides important extensions to the existing 3GPP positioning protocol LPP and is expected to be used widely with OMA SUPL. OMA LOC WG is currently focused on extending location services into areas considered difficult to serve (i.e., Indoor Location) and to support the latest technologies such as Wi-Fi positioning, image recognition based positioning, sensors, etc.

One example is the AT&T deployment of OMA SUPL 1.0, OMA SUPL 2.0 and OMA MLP 3.0 in the production network as primary components of the location engine to support AT&T’s commercial Location Based Services offers. AT&T is actively evaluating more recent versions of OMA SUPL, including the DSLP concept that has emerged as a major new feature for future upgrades to its SUPL infrastructure.


LOC WG Highlighted Achievements 2002-2017

The following enablers represent some of the successful specifications delivered by LOC WG over the last 10 years.

OMA Secure User Plane Location (OMA SUPL)

The objective of the SUPL enabler is to provide an industry standard framework for positioning over the User Plane as an alternative to existing control plane solutions, which are bandwidth-constrained and limited to access types that are part of the control plane system. “User Plane” may comprise IP and SMS bearers in the MNO environment and IP bearers in the WLAN/Internet environment. This mechanism could be implemented in a wide range of contexts (i.e. a controlled mobile network operator’s environment or an open Internet/WLAN environment.)

OMA Mobile Location Service (OMA MLS)

The MLS enabler provides XML based protocols for mobile location, roaming location, and privacy checking (MLP, RLP, and CPC respectively) to support the 3GPP requirements and architecture specified in TS 22.071 and 3GPP TS 23.271. OMA MLS also defines its own requirements and architecture to support location services not driven by 3GPP. Specifically, the OMA SUPL enabler inter-works with MLS by using RLP to support roaming scenarios and MLP for communication toward applications.

OMA LTE Positioning Protocol extensions (OMA LPPe)

3GPP has developed a positioning protocol for LTE networks (LPP) intended to be usable in both 3GPP and OMA domains. LPP provides a solid framework to define additional positioning technologies on top of the 3GPP-defined items; however, there are a variety of current and emerging positioning technologies that are not in the scope of 3GPP LPP. In addition, LPP in its 3GPP-defined form does not support the positioning technology enhancements required by the SUPL3.0 enabler. Accordingly, LPP has also been designed to allow for an external to 3GPP to extend LPP and 3GPP (.)? one sentence? RAN WG2 has agreed that OMA can define its User Plane specific extensions to LPP.

OMA Dynamic Navigation (DynNav)







DynNav represents a tool for delivering customers’ traffic information to mobile operators. Traffic information is generated by processing mobile network signaling data or it can be retrieved from external sources. The DynNav enabler intends to leverage existing OMA enablers (e.g. SUPL) to provide real time delivery of travel assistance data (e.g. traveling time/delays due to traffic, accidents, road work, parking information, etc.) to location enabled terminals. Delivering dynamic routing information over a mobile data network appeals to mobile network operators who are able to leverage network information to provide real time and forecast traffic information, and specific traffic information may be provided for each single journey according to time, origin and destination information. Mobile operators can adopt DynNav as part of their customer retention strategies.

The DynNav application will be integrated with SUPL tracking and triggering procedures and also with GNSS Assistance procedure for high accuracy assistance for lane detection available in SUPL framework.


OMA SUPL Configuration Services

OMA SUPL Configuration Service 1.0 provides a mobile operator with the ability to host a SUPL configuration and provisioning service that handsets may query to obtain SUPL configuration information.

The configuration information may include but not be limited to:

  • An H-SLP or E-SLP for each roaming partner of a mobile operator
  • An H-SLP for the use of the handset OEM
  • An H-SLP for operating system vendors such as Google
  • D-SLP information for a given region
  • H-SLP to utilize for an individual application
  • Application Identifier information to be used when using the SUPL 2.0 or above location protocols

This complex SLP configuration mechanism is needed to allow the mobile operator the most flexibility when building their mobile LBS platforms. This will minimize the expense of the operator, as they will no longer have to pay SLP vendors for application use where the operator does not sponsor the application.

This work item defines the methods for configuring SUPL configuration data from a service to the mobile using the OMA SUPL DM Management Object.

OMA LTE Positioning Protocol extensions 2.0 (OMA LPPe 2.0)

OMA LPPe adds new positioning methods and enhancements to LPPe Release 1. These new positioning methods and enhancements will improve location service quality such as service availability, accuracy and time to fix and extend the service to areas traditionally difficult to serve (e.g., indoor locations).

The work areas in scope for LPPe 2.0 are:

  • Extend LPPe to support Image Recognition Based Positioning (IRBP) as new positioning method. IRBP uses image feature analysis in the target device or on the location server to determine, or help determine, the target device’s position
  • Extend LPPe to support Pedestrian Dead Reckoning (PDR) as new positioning method. PDR enables pedestrian borne target devices to calculate their current position by extrapolating from previously known positions using target device sensor input and server provided step length models and environment information (e.g., building information, floor plans etc.)
  • Extend LPPe to enhance positioning accuracy and availability in WLAN environments
  • Extend LPPe to support Crowd Sourcing via measurements a target device normally obtains for its own location
    NOTE: crowd sourcing may require support from SUPL as well as LPPe
  • Extend LPPe to allow provision of maps in standard existing format if possible. Maps can be provided for both indoor and outdoor. Map information may include additional information such as altitude information, etc.

This work item aims to increase service quality, particularly for indoor environments, by introducing support for new positioning methods.

OMA LOC WG and Machine-to-Machine Communication

OMA is well established in Location Services and is therefore well positioned to extend its work to M2M Communication.

OMA M2M LOC WI defines, within the M2M platform, a set of application level location procedures for tracking and triggering mobile terminals, similar to those defined in MLP. The new standardization activity will simplify the access to location features in the M2M context, avoiding the use of a location specific API such as MLP. The integration of position resolution functionalities in the M2M framework, as defined in LPPe, could also be addressed by LOC and this is currently under evaluation within the LOC WG.