Restcomm Geolocation API and GMLC Restconn 2017

Restcomm Geolocation API & GMLC

Mechanisms for Mobile Geolocation Value-Added Services

across Legacy and Next Generation NetworksRestconn 2017 - Fernando Mendioroz

Location Based Services

Brief review of LBS in heterogeneous

Mobile Core Networks

3

Smartphone apps vs. reality: Ericsson Mobility Report 2017

© 2017 Telestax, Confidential Do Not Copy

Location Based Services in Mobile Core Networks

4

Smartphone apps vs. reality: Ericsson Mobility Report 2017



• Approximately 4 billion 2G/3G feature phones for 2022 (~43%).– Feature phones will still have a deep market penetration for the next decade.

• No GPS-based applications available for those.

• Location Services triggered by legacy methods over circuit switched core

networks over SS7 still needed for quite a long time.

• ~10% of cellular mobile coverage only thru GSM/EDGE for 2020 y 95% of

global GSM/EDGE coverage for 2022.

• ~45% non-LTE or 5G subscriptions for 2022.

5

GPS-based LBS limitations



6

Location Based Services methods in Cellular legacy and NG Networks



• Retrieve radio access entities Identifiers from the HLR (Cell ID/Location Area

Code):

–SS7 MAP Any Time Interrogation to the HLR.

• Trigger procedures at the Radio Access Network for location estimate in

Universal Coordinates, via SS7 MAP (UMTS) or Diameter (LTE), e.g.:– SS7 MAP procedures with the HLR and MSC/SGSN (UMTS).

– Diameter-based requests for LTE SLh and SLg interfaces:

• Observed/Uplink Time Difference of Arrival (O/UTDOA)

• Enhanced Observed Time Difference (E-OTD)

• Timing Advance (TA)

• Angle of Arrival (AoA)

7

Location Services architecture in legacy mobile networks: GSM/EDGE



8

Location Services architecture in legacy mobile networks: UMTS/HSPA+



9

Location Services architecture in NGN mobile networks: LTE and beyond



Restcomm Geolocation API

Overview and status by May 2017

11

Main objectives



• RestComm Geolocation API aims offering an API that Web Developers can

understand without the need of any knowledge about the underlying

Telecom infrastructure and jargon and thus make it as easy as it gets to

include Geolocation as a value-added feature in their applications.

• The API aims to catering either cellular telephony Geolocation (from Mobile

Network Operator´s core and radio access networks, either by SS7 MAP or

LTE Diameter operations) or IP Geolocation (from Restcomm iOS and

Android SDKs).

12

Some use cases



• Notify RestComm the current location of client X or certain MSISDN (e.g.

iWatch cardio activity alarm –2015 TADHack Chicago winner-, NG911,

friend/family finder, etc.).

• Notify RestComm if client X or certain MSISDN enters or exits a geofence.

Mobile advertising use cases apply to this type of Geolocation service.

• Notify RestComm if client X is within N meters from client Y. Many use cases

apply to this type of Geolocation service, namely:– Parental control: Notify a parent when their child/children are further than X metres

away.

– Hanging out: Notify friends when they are within X metres.

– Business matching: at a conference, notify attendees of other attendees within

range who also have related interest based on LinkedIn profile.

– Court restraining order: when someone is legally not allowed to be writhing certain

range of another individual.

13© 2017 Telestax, Confidential Do Not Copy



Restcomm Geolocation APICellular Geolocation


Restcomm Geolocation APIWiFi Geolocation

Restcomm GMLC

Overview, current features and

roadmap


Restcomm GMLCAll interfaces and Architecture

18

Version 2.0.0 features


Restcomm GMLC

• Legacy SS7 MAP ATI for obtaining CID/LAC

• Legacy SS7 MAP operations used:– MAP SRIforLCS (GMLC ↔ HLR/HSS): Obtain routing information from HLR/HSS.

– MAP PSL (GMLC ↔ MSC/SGSN): Provide Subscriber Location from the UTRAN.

– MAP SLR (MSC/SGSN ↔ GMLC): Subscriber Location Report –event driven

triggered by earlier MAP PSL- from the UTRAN.

• Location Services through positioning methods in UTRAN triggered by an

Stand-Alone SMLC.

• Immediate and Event-driven Location Reports.

19

Version 3.0.0 features in progress


Restcomm GMLC

• Diameter based operations used:– SLh RIR/RIA (GMLC ↔ HLR/HSS): Routing Information Request/Answer from

HLR/HSS.

– SLg (ELP) PLR/PLA (GMLC ↔ MME): Provide Location Request/Answer from the

E-UTRAN (LTE).

– SLg (ELP) LRR/LRA (MME ↔ GMLC): Location Report Request/Answer –event

driven triggered by earlier MAP PLA- from the E-UTRAN.

• Location Services through positioning methods in E-UTRAN (LTE) triggered

by an Enhanced-SMLC.

• Immediate and Event-driven Location Reports.

Restcomm Geolocation API & GMLC

Before and After, Demos, Traces, roadmap

and integration with Restcomm-Connect

and RVD

21

Before


Restcomm Geolocation API and GMLC

22

After



23

Work done in RESTCOMM Communications Platform



24

Simple LBS call flow in GSM



HTTP POST

HTTPGET

MAP ATIRequest

MAP ATIResponse

HTTP200 OK

HTTP 200 OK

curl -X POST -H "application/json" http://ACae6e420f425248d6a26948c17a9e2acf:[email protected]:8080/restcomm/2012-04-24/Accounts/ACae6e420f425248d6a26948c17a9e2acf/Geolocation/Immediate-d "DeviceIdentifier=59899077937" -d "StatusCallback=http://52.2.24.19:8888/ACae6e420f425248d6a26948c17a9e2acf"

GSM MAPComponent: returnResultLast (2)

returnResultLastinvokeID: 0resultretres

opCode: localValue (0)localValue: anyTimeInterrogation (71)

subscriberInfolocationInformation

ageOfLocationInformation: 5geographicalInformation: 104f01231f9a0e00vlr-number: 915555556566cellGlobalIdOrServiceAreaIdOrLAI: cellGlobalIdOrServiceAreaIdFixedLength:

52f0107d0000ddsubscriberState: assumedIdle (0)

assumedIdle

Hypertext Transfer ProtocolHTTP/1.1 200 OK\r\n

[Expert Info (Chat/Sequence): HTTP/1.1 200 OK\r\n]Request Version: HTTP/1.1Status Code: 200Response Phrase: OK

[HTTP response 1/1][Time since request: 0.341487879 seconds][Request in frame: 10]HTTP chunked response

Data chunk (61 octets)End of chunked encoding\r\n

Data (61 bytes) mcc=250,mnc=1,lac=32000,cellid=221,aol=5,vlrNumber=5555555666

<RestcommResponse><Geolocation>

<Sid>GLe35105b146b340a9a2dea2dd93429ef3</Sid><DateCreated>Sat, 3 Dec 2016 01:24:48 -0200</DateCreated><DateUpdated>Sat, 3 Dec 2016 01:24:48 -0200</DateUpdated><DateExecuted>Sat, 3 Dec 2016 01:24:48 -0200</DateExecuted><AccountSid>ACae6e420f425248d6a26948c17a9e2acf</AccountSid><DeviceIdentifier>59899077937</DeviceIdentifier><GeolocationType>Immediate</GeolocationType><GeolocationData>

<CellId>221</CellId><LocationAreaCode>32000</LocationAreaCode><MobileCountryCode>250</MobileCountryCode><MobileNetworkCode>1</MobileNetworkCode><NetworkEntityAddress>5555555666</NetworkEntityAddress><LocationAge>5</LocationAge>

</GeolocationData><ApiVersion>2012-04-24</ApiVersion><Uri>/restcomm/2012-04-

24/Accounts/ACae6e420f425248d6a26948c17a9e2acf/Geolocation/Immediate/GLe35105b146b340a9a2dea2dd93429ef3</Uri>

</Geolocation></RestcommResponse>

25

Documentation, Demo and Wireshark Traces



• Simple GSM location services:

– Documentation:– Restcomm Geolocation API

– Restcomm GMLC

– Demo: https://www.youtube.com/watch?v=uSBItQaDnrQ

– Wireshark trace:

http://documentation.telestax.com/connect/api/geolocation-api.html

http://documentation.telestax.com/core/gmlc/GMLC_Admin_Guide.html

https://www.youtube.com/watch?v=uSBItQaDnrQ

26

Wireshark Traces for Legacy and LTE LCS (Immediate and Event-driven)


Restcomm GMLC

• Location Services through positioning methods in E-UTRAN (LTE)

triggered by an Enhanced-SMLC:

– Wireshark trace:

• Location Services through positioning methods in E-UTRAN (LTE)

triggered by an Enhanced-SMLC:

– Wireshark traces + dictionary additions/contributions:

27

Location Services triggered by USSD and with SMS notification using Restcomm SMSC and USSD Gateways within heterogeneous networks



*543#

MAP USSD Beg SIP INVITE

USSI

SLh Diameter RIR

SLh Diameter RIA

SLg Diameter PLR

HTTP POST

SLs Diameter LCS-AP req

SLs Diameter LCS-AP ans

SLg Diameter PLA

SIP BYE USSIHTTP POST

HTTP 200 OK

SIP MESSAGE

MAP SRIforSM Beg

MAP SRIforSM End

MAP MT-fwSM

MAP USSD End

*543#Resp

SMS

SLg Diameter LRR

SLg Diameter LRA

HTTP POST

HTTP 200 OK

HTTP POST

HTTP 200 OK

S1-MME Diameter LPP req

S1-MME Diameter LPP ans

S1-MME Diameter LPP

HTTP POST

HTTP 200 OK

USSD over SIP (USSI) is translated to USSD over MAP (SS7) according to 3GPP TS 29.002

USSD over SS7 (MAP) is translated to USSD over SIP (USSI) according to 3GPP TS 24.390

CSFB

USSD *543# request is routed via MAP (SS7) to Restcomm USSD Gateway

Restcomm-Connect triggers LTE location procedure via Restcomm GMLC according to 3GPP TS 29.172/173

E-SMLC, MME and Radio Access Network proceed to locate the mobile equipment by a positioning method (e.g. OTDOA)

Location information is sent back via ELP (Diameter) to the GMLC and then to Restcomm, which resumes service logic

According to service logic, user equipment location needs to be reported back to the user that initiated the service via USSD

SMS over SIP is translated by Restcomm SMSC to SMS over MAP (SS7)

The Radio Access Network detects a location event to be reported according to service logic

28

Roadmap for 2017-2018



• Work along with team from Illinois Institute of Technology on WiFi and Bluetooth

indoors location, for adding Restcomm Geolocation API to their current work on

NG911. Adding Restcomm iOS and Android SDKs into the mix for the latter.

• Enhance OMA MLP for full specification compliance.

• Global Cell Identity / Service Area Identity → latitude/longitude conversion

database.

• User plane location via OMA SUPL.

• SIP support between RC GL API and GMLC.

• Management console.

• WildFly 10.1 migration.

• E-SMLC project from scratch, starting with jDiameter SLs interface.

© 2017 Telestax

Thank you

For more information, visit us at: www.telestax.com

Engineering

Restcomm Geolocation API and GMLC Restconn 2017