Mobile Location Protocol

Last updated

The Mobile Location Protocol (MLP) is an application-level protocol for receiving the position of Mobile Stations (MS: mobile phones, wireless devices, etc.) independent of underlying network technology. [1] [2] [3] [4]

Contents

The MLP serves as the interface between a Location Server and a location-based application. Basic MLP Services are based on location services defined by 3GPP. The Mobile Location Protocol (MLP) is described in LIF TS 101 Specification. [5]

Background

The purpose of this technology is to define a simple and secure access method that allows mobile application to query location information from a wireless network, regardless of its underlying network technology and positioning methods.

The MLP can be used by a location-based application to request mobile station location information from a location server (GMLC/MPC or other entity in the wireless network). This protocol has been prepared by Location Interoperability Forum (LIF: Open Mobile Alliance in nowadays) to provide a simple and secure API (Application Programmer’s Interface), but also could be used for other kinds of location servers and entities in the wireless network.

The API is based on XML and is defined to be transported in HTTP or SOAP. Only mapping to HTTP is defined in present days. For security reasons Secure Socket Layer (SSL) or Transport Layer Security (TLS) cryptographic protocols can be used to carry HTTP (HTTPS). Apart from HTTPS Mobile Location Protocol which uses authentication by user and password, the information is carried in header part of MLP message.

Features: [6]

Last draft of MLP specification is OMA-TS-MLP v 3.3 from March 2009. [5] Version 3.3 provides these features:

Standard Location Immediate Service (SLIS)

Used for requesting the location of one or more Mobile Subscribers (MS). It is used when immediate response is required. Response can be returned in more than one message if the request contained more Mobile Subscribers.

Emergency Location Immediate Service (ELIS)

Used for requesting the location of one or more MS involved in an emergency call. Response can be returned in more than one message if the server supports it.

Standard Location Reporting Service (SLRS)

This service is initiated by MS by sending Mobile Originated Location Request [TS23271] through wireless network. It is performed when Mobile Subscriber wants an LCS client to receive MS location.

Emergency Location Reporting Service (ELRS)

This service is initiated by network when MS initiates or releases emergency call. Report is generated and sent from Location Server to predefined LCS client.

Triggered Location Reporting Service (TLRS)

This service is used when LCS client wants to track several MS. Triggers can be timers or MS events like change of location.

Historic Location Immediate Service (HLIS)

This service is used to request reporting of historic locations of one MS when large amount of data is expected.

Common Element Definitions: [7]

Identity Element Definitions

<!ELEMENT msid (#PCDATA)> <!ATTLIST msid type (MSISDN | IMSI | IMEI | MIN | MDN | EME_MSID | IPV4 | IPV6) "MSISDN" enc (ASC | B64 | CRP) "ASC"> <!ELEMENT msid_range (start_msid, stop_msid)> <!ATTLIST msid_range type (MSISDN | IMSI | IMEI | MIN | MDN | EME_MSID | IPV4 | IPV6) "MSISDN" enc (ASC | B64 | CRP) "ASC"> <!ELEMENT msids ((msid, session? | msid_range)+)> <!ELEMENT esrd (#PCDATA)> <!ATTLIST esrd type (NA) "NA"> <!ELEMENT esrk (#PCDATA)> <!ATTLIST esrk type (NA) "NA"> <!ELEMENT session (#PCDATA) session Type (APN | dial) #REQUIRED> <!ELEMENT start_msid (#PCDATA)> <!ELEMENT stop_msid (#PCDATA)>

Function Element Definitions

<!ELEMENT add_info (#PCDATA)> <!ELEMENT eme_event (eme_pos+)> <!ATTLIST eme_event eme_trigger (EME_ORG | EME_REL) #REQUIRED> <!ELEMENT tlrr_event (time | area_change | ms_action)> <!ELEMENT ms_action EMPTY> <!ATTLIST ms_action type (MS_AVAIL) #REQUIRED> <!ELEMENT interval (#PCDATA)> <!ELEMENT loc_type EMPTY> <!ATTLIST loc_type type (CURRENT | LAST | CURRENT_OR_LAST | INITIAL) "CURRENT"> <!ELEMENT poserr (result, time)> <!ELEMENT prio EMPTY> <!ATTLIST prio type (NORMAL | HIGH) "NORMAL"> <!ELEMENT pushaddr (url)> <!ELEMENT req_id (#PCDATA)> <!ELEMENT result (#PCDATA)> <!ATTLIST result resid CDATA #REQUIRED> <!ELEMENT start_time (#PCDATA)> <!ATTLIST start_time utc_off CDATA "0000"> <!ELEMENT stop_time (#PCDATA)> <!ATTLIST stop_time utc_off CDATA "0000"> <!ELEMENT time (#PCDATA)> <!ATTLIST time utc_off CDATA "0000"> <!ELEMENT url (#PCDATA)> <!ELEMENT Time_remaining (#PCDATA)>

Location Element Definitions

<!ELEMENT pos (msid, (pd | poserr), gsm_net_param?)> <!ELEMENT eme_pos (msid, esrd?, esrk?, (pd | poserr))> <!ELEMENT trl_pos (msid, (pd | poserr))> <!ELEMENT trl_pos <!ATTLIST trl_trigger (TIMER | PERIODIC | MS_AVAIL) <!ELEMENT pd (time, shape, (alt, alt_acc?)?, speed?, direction?, lev_conf?)> <!ELEMENT alt (#PCDATA)> <!ELEMENT alt_acc (#PCDATA)> <!ELEMENT direction (#PCDATA)> <!ELEMENT easting (#PCDATA)> <!ELEMENT geo_info (coord_sys, datum, format? Zone?)> <!ELEMENT coord_sys (#PCDATA) <!ELEMENT datum (#PCDATA) <!ELEMENT format (#PCDATA)> <!ELEMENT lat (#PCDATA)> <!ELEMENT ll_point (lat, long)> <!ELEMENT long (#PCDATA)> <!ELEMENT northing (#PCDATA)> <!ELEMENT utm_point (easting, northing, zone, zone_des)> <!ELEMENT speed (#PCDATA)> <!ELEMENT x (#PCDATA)> <!ELEMENT xy_point (x, y)> <!ELEMENT y (#PCDATA)> <!ELEMENT zone (#PCDATA)> <!ELEMENT zone_des (#PCDATA)> <!ELEMENT lev_conf (#PCDATA)>

Shape Element Definitions

<!ELEMENT shape (point | circle | circ_arc | ellipse | polygon )> <!ELEMENT point (ll_point | utm_point | xy_point)> <!ELEMENT angle (#PCDATA)> <!ELEMENT circ_arc (point, in_rad, out_rad, start_angle, stop_angle)> <!ELEMENT circle (point, rad)> <!ELEMENT ellipse (point, angle, semi_major, semi_minor)> <!ELEMENT in_rad (#PCDATA)> <!ELEMENT out_rad (#PCDATA)> <!ELEMENT polygon (point+)> <!ELEMENT rad (#PCDATA)> <!ELEMENT semi_major (#PCDATA)> <!ELEMENT semi_minor (#PCDATA)> <!ELEMENT start_angle (#PCDATA)> <!ELEMENT stop_angle (#PCDATA)>

Quality of Position Element Definitions

<!ELEMENT eqop (resp_req?, resp_timer?, (ll_acc | hor_acc)?, alt_acc?, max_loc_age?)> <!ELEMENT qop ((ll_acc | hor_acc)?, alt_acc?)> <!ELEMENT ll_acc (#PCDATA)> <!ELEMENT hor_acc (#PCDATA)> <!ELEMENT resp_req EMPTY> <!ATTLIST resp_req type (NO_DELAY | LOW_DELAY | DELAY_TOL) "DELAY_TOL"> <!ELEMENT resp_timer (#PCDATA)>

Network Parameters Element Definitions

<!ELEMENT gsm_net_param (cgi?, neid?, nmr?, ta?)> <!ELEMENT cgi (mcc, mnc, lac, cellid)> <!ELEMENT neid (vmscid | vlrid)> <!ELEMENT vmscid (cc, ndc, vmscno)> <!ELEMENT vlrid (cc, ndc, vlrno)> <!ELEMENT nmr (#PCDATA)> <!ELEMENT mcc (#PCDATA)> <!ELEMENT ndc (#PCDATA)> <!ELEMENT cc (#PCDATA)> <!ELEMENT vmscno (#PCDATA)> <!ELEMENT vlrno (#PCDATA)> <!ELEMENT lac (#PCDATA)> <!ELEMENT cellid (#PCDATA)> <!ELEMENT ta (#PCDATA)>

Context Element Definitions

<!ELEMENT client (id, pwd?, serviceid? servicetype?)> <!ELEMENT sessionid (#PCDATA)> <!ELEMENT id (#PCDATA)> <!ELEMENT originator (id, serviceid?)> <!ELEMENT pwd (#PCDATA)> <!ELEMENT serviceid (#PCDATA)> <!ELEMENT servicetype EMPTY> <!ATTLIST servicetype type (ACTIVE | PASSIVE) "PASSIVE"> <!ELEMENT subclient (id, pwd?, serviceid?)> <!ATTLIST subsclient last_client (YES | NO) "NO">]

Related Research Articles

General Packet Radio Service (GPRS) is a packet oriented mobile data standard on the 2G and 3G cellular communication network's global system for mobile communications (GSM). GPRS was established by European Telecommunications Standards Institute (ETSI) in response to the earlier CDPD and i-mode packet-switched cellular technologies. It is now maintained by the 3rd Generation Partnership Project (3GPP).

IPv6 Version 6 of the Internet Protocol

Internet Protocol version 6 (IPv6) is the most recent version of the Internet Protocol (IP), the communications protocol that provides an identification and location system for computers on networks and routes traffic across the Internet. IPv6 was developed by the Internet Engineering Task Force (IETF) to deal with the long-anticipated problem of IPv4 address exhaustion. IPv6 is intended to replace IPv4. In December 1998, IPv6 became a Draft Standard for the IETF, who subsequently ratified it as an Internet Standard on 14 July 2017.

Wireless LAN Computer network that links devices using wireless communication within a limited area

A wireless LAN (WLAN) is a wireless computer network that links two or more devices using wireless communication to form a local area network (LAN) within a limited area such as a home, school, computer laboratory, campus, or office building. This gives users the ability to move around within the area and remain connected to the network. Through a gateway, a WLAN can also provide a connection to the wider Internet.

A location-based service (LBS) is a general term denoting software services which utilize geographic data and information to provide services or information to users. LBS can be used in a variety of contexts, such as health, indoor object search, entertainment, work, personal life, etc. Commonly used examples of location based services include navigation software, social networking services, location-based advertising, and tracking systems. LBS can also include mobile commerce when taking the form of coupons or advertising directed at customers based on their current location. They include personalized weather services and even location-based games.

Virtual private network Allows a private network to go through a public network

A virtual private network (VPN) extends a private network across a public network and enables users to send and receive data across shared or public networks as if their computing devices were directly connected to the private network. Applications running across a VPN may therefore benefit from the functionality, security, and management of the private network. Encryption is a common, although not an inherent, part of a VPN connection.

Roaming

Roaming is a wireless telecommunication term typically used with mobile devices, such as mobile phones. It refers to the mobile phone being used outside the range of its home network and connects to another available cell network.

Zero-configuration networking (zeroconf) is a set of technologies that automatically creates a usable computer network based on the Internet Protocol Suite (TCP/IP) when computers or network peripherals are interconnected. It does not require manual operator intervention or special configuration servers. Without zeroconf, a network administrator must set up network services, such as Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS), or configure each computer's network settings manually.

Network switching subsystem (NSS) is the component of a GSM system that carries out call out and mobility management functions for mobile phones roaming on the network of base stations. It is owned and deployed by mobile phone operators and allows mobile devices to communicate with each other and telephones in the wider public switched telephone network (PSTN). The architecture contains specific features and functions which are needed because the phones are not fixed in one location.

Mobile IP is an Internet Engineering Task Force (IETF) standard communications protocol that is designed to allow mobile device users to move from one network to another while maintaining a permanent IP address. Mobile IP for IPv4 is described in IETF RFC 5944, and extensions are defined in IETF RFC 4721. Mobile IPv6, the IP mobility implementation for the next generation of the Internet Protocol, IPv6, is described in RFC 6275.

Global System for Mobile Communications (GSM) services are a standard collection of applications and features available to mobile phone subscribers all over the world. The GSM standards are defined by the 3GPP collaboration and implemented in hardware and software by equipment manufacturers and mobile phone operators. The common standard makes it possible to use the same phones with different companies' services, or even roam into different countries. GSM is the world's most dominant mobile phone standard.

The IP Multimedia Subsystem or IP Multimedia Core Network Subsystem (IMS) is an architectural framework for delivering IP multimedia services. Historically, mobile phones have provided voice call services over a circuit-switched-style network, rather than strictly over an IP packet-switched network. Alternative methods of delivering voice (VoIP) or other multimedia services have become available on smartphones, but they have not become standardized across the industry. IMS is an architectural framework to provide such standardization.

Radiolocation, also known as radiolocating or radiopositioning, is the process of finding the location of something through the use of radio waves. It generally refers to passive uses, particularly radar—as well as detecting buried cables, water mains, and other public utilities. It is similar to radionavigation, but radiolocation usually refers to passively finding a distant object rather than actively one's own position. Both are types of radiodetermination. Radiolocation is also used in real-time locating systems (RTLS) for tracking valuable assets.

The Precision Time Protocol (PTP) is a protocol used to synchronize clocks throughout a computer network. On a local area network, it achieves clock accuracy in the sub-microsecond range, making it suitable for measurement and control systems. PTP is currently employed to synchronize financial transactions, mobile phone tower transmissions, sub-sea acoustic arrays, and networks that require precise timing but lack access to satellite navigation signals.

IP multicast is a method of sending Internet Protocol (IP) datagrams to a group of interested receivers in a single transmission. It is the IP-specific form of multicast and is used for streaming media and other network applications. It uses specially reserved multicast address blocks in IPv4 and IPv6.

IEEE 802.11u-2011 is an amendment to the IEEE 802.11-2007 standard to add features that improve interworking with external networks.

Wireless Application Protocol (WAP) is a technical standard for accessing information over a mobile wireless network. A WAP browser is a web browser for mobile devices such as mobile phones that use the protocol. Introduced in 1999, WAP achieved some popularity in the early 2000s, but by the 2010s it had been largely superseded by more modern standards. Most modern handset internet browsers now fully support HTML, so they do not need to use WAP markup for web page compatibility, and therefore, most are no longer able to render and display pages written in WML, WAP's markup language.

In computing, Microsoft's Windows Vista and Windows Server 2008 introduced in 2007/2008 a new networking stack named Next Generation TCP/IP stack, to improve on the previous stack in several ways. The stack includes native implementation of IPv6, as well as a complete overhaul of IPv4. The new TCP/IP stack uses a new method to store configuration settings that enables more dynamic control and does not require a computer restart after a change in settings. The new stack, implemented as a dual-stack model, depends on a strong host-model and features an infrastructure to enable more modular components that one can dynamically insert and remove.

Locator/Identifier Separation Protocol

Locator/ID Separation Protocol (LISP) is a "map-and-encapsulate" protocol which is developed by the Internet Engineering Task Force LISP Working Group. The basic idea behind the separation is that the Internet architecture combines two functions, routing locators and identifiers in one number space: the IP address. LISP supports the separation of the IPv4 and IPv6 address space following a network-based map-and-encapsulate scheme. In LISP, both identifiers and locators can be IP addresses or arbitrary elements like a set of GPS coordinates or a MAC address.

A mobile wireless sensor network (MWSN) can simply be defined as a wireless sensor network (WSN) in which the sensor nodes are mobile. MWSNs are a smaller, emerging field of research in contrast to their well-established predecessor. MWSNs are much more versatile than static sensor networks as they can be deployed in any scenario and cope with rapid topology changes. However, many of their applications are similar, such as environment monitoring or surveillance. Commonly, the nodes consist of a radio transceiver and a microcontroller powered by a battery, as well as some kind of sensor for detecting light, heat, humidity, temperature, etc.

References

  1. Kolodziej, Krzysztof W.; Hjelm, Johan (19 December 2017). Local Positioning Systems: LBS Applications and Services. CRC Press. pp. 441–443. ISBN   9781420005004 . Retrieved 7 December 2016.
  2. Jagoe, Andrew (2003). Mobile Location Services: The Definitive Guide. Prentice Hall Professional. pp. 219–312. ISBN   9780130084569 . Retrieved 7 December 2016.
  3. Salkintzis, Apostolis; Passas, Nikos (31 October 2005). Emerging Wireless Multimedia: Services and Technologies. John Wiley & Sons. pp. 408–409. ISBN   9780470021507.
  4. Dixit, Sudhir; Wu, Tao (11 November 2004). Content Networking in the Mobile Internet. John Wiley & Sons. pp. 466–467. ISBN   9780471478287 . Retrieved 7 December 2016.
  5. 1 2 OMA Technical Section
  6. Implementing Mobile Location Protocol, Research and Development Center for Mobile Applications, 2009
  7. LIF TS 101 v2.0.0, Mobile Location Protocol, draft v.2.0, Location Inter-operability Forum (LIF), 2001