LBS Interoperability Through Standards Ko Hye-Kyeong Mobile Data Engineering Lab. Dept. of Computer Science and Engineering, Korea University
2 Contents Standards of LBS Standards Support LBS Business Models Multiple Consortia Provide LBS Standards A Key Standard : The GeoMobility Server Standards at Work in the Chapter 2 Use Case Standards in Korea Conclusion
3 General Trends in Location Services TIA moving from emergency to commercial services Telecommunications Industry Association, mostly this hemisphere GSM moving from commercial to emergency services Global System for Mobile Telecommunications, mostly rest of the world Operators looking for technical solutions to interoperability Operators trying to figure out long-term business models around interoperability
4 Standards of LBS (1/3) Information and communications technology standards are important to the commercial rollout of LBS and the fulfilment of their potential S/W 2S/W 1Standard Geospatial data Transferring Geospatial Data between Different H/W and S/W
5 Standards of LBS (2/3) Standards are Important to LBS Users Open service and information framework enables roaming between location cells
6 Standards of LBS (3/3) Standards are Important to LBS Providers With open interfaces, applications can access many sources of content and services
7 Brief History of Standards (1/2) With pahase I architecture model, most carriers/operators took an approach in which they simply opened up prestandards interface access to their network MPC/GMLC to all spatially enabled applications residing outside the network firewall in the IP domain. Approach for Carrier/Operator LBS Architectures
8 Brief History of Standards (2/2) Due to the integration problems encountered with the Phase I approach, carriers/operators chose to implement two additional components within the core LBS architecture model Phare II model ensures that the carrier/operator has complete control over how any application developer interfaces to the core network, and it dramatically reduces implementation costs Approach for Carrier/Operator LBS Architectures
9 Standards Support LBS Business Models (1/4) Technologies for location service Wireless communications Position determination Store, serve, and apply georeferenced data in response to queries
10 Standards support LBS Business Models (2/4) Today’s reality of service technology Despite telecom industry mergers and acquisitions, the number of carriers, service providers, application providers, and content providers is growing Standards To maintain integration among even a target subset of the possible permutations of devices, Location Engines, service providers, and content providers Saving time, money and reducing business risks
11 Standards support LBS Business Models(3/4) LBS standards benefit providers in the LBS value chain Increased billable utilization of carrier’s spectrum and wireless network Niches for providers with special products and services A business case for different content providers Expansion of LBS from a niche service to a mass market service GSM Assorication, AOL, Microsoft, and AAA
12 LBS Value Chain
13 Multiple Consortia provide LBS Standards(2/2)
14 Open GIS Consortium (OGC) opens Initiative starting from Oct involves a broad and complex set of geospatial software interoperability issues at the level in the communications technology stack Working Groups Navigation Services WG (John Herring, Oracle) Directory(POI) Services WG (Vipul Sawhney, LocatioNet) Presentation Services WG (Serge Margoulies, Ionic) Location Utility Services WG (Jonathan Williams, Hutchison 3G) Gateway Services WG (Richard Wong, SignalSoft) Encodings & Protocols WG (Marwa Mabrouk, ESRI)
15 OGC focuses at the application interface level Geospatial interoperability issues Coordinate transformation Web mapping XML encoding of spatial information
16 Open Mobile Alliance (OMA) designed to be a center for mobile service specification work, stimulating and contributing to the creation of interoperable services
17 The Value Chain of OMA OMA member companies fall into 4 categories that essentially define the various parts of the end-to-end value chain. They include: Wireless Vendors Information Technology Companies Mobile Operators Application & Content Providers & Others
18 Available OMA Enablers OMA Multimedia Messaging Service (MMS) OMA Instant Messaging and Presence server (IMPS) OMA Digital Rights Management (DRM) OMA Download OMA Client Provisioning (client device property management) OMA Browsing OMA Billing Framework OMA notification OMA User Agent Profile OMA Domain Name Server
19 Location Interoperability Forum (LIF) founded in September 2000 by Motorola, Ericsson, and Nokia with the purpose of developing and promoting industry common solutions for LBS now merged with OMA addressed early and obvious problems related to the multiplicity of methods for location determination
20 LIF’s Mobile Location Protocol MLP serves as the interface between a location server and a location-based application
21 LIF’s Mobile Location Protocol OpensLS and Location Interoperability Forum (LIF) Mobile Location Protocal (MLP)
22 LIF’s Mobile Location Protocol MLP Version complete Standard Immediate Location Service Emergency Immediate Location Service Standard Location Reporting Service Emergency Location Reporting Service Triggered Location Reporting Service
23 OGC’s OpenLS Services equate with LIF’s Advanced MLP Services provides a larger and more comprehensive geospatial framework.
24 WAP (Wireless Application Protocol) Forum part of OMA Worldwide standard for providing wireless Internet communications and advanced telephony services on digital mobile phones, pagers, PDAs, and other wireless terminals
25 Other International Standards (1/4) 3GPP (3 rd Generation Partnership project) TS Location Services(LCS) Service Description, Stage 1 TS Service Aspects; Virtual Home Environment TS Functional description of LCS – Stage 2 TS Service Aspects; Charging and billing TSR Enhanced support for User Privacy in location services TS Supplementary service operation – Stage 3 TS Location Services(LCS), Location services management 3GPP2 S.R0019 : Location-Based Services System (LBSS)
26 Other International Standards (2/4) The Parlay Group’s Open Service Architecture Define an interface between third party applications Provides secure portal element, open interfaces, and integrated media control capabilities
27 Other International Standards (3/4) The Cellular Telecommunication & Internet Association (CTIA) Have occasional communication with LBS standards groups Two ISO technical committees Working in the spatial technologies domain
28 Other International Standards (4/4) Automotive Multimedia Interface Consortium (AMIC) A group of automobile manufacturers facilitating the development of standards for in-car navigation system, cell phones, pagers, video systems, CD players, PDAs, and automotive PCs
29 A Key Standard : The Geomobility Server (GMS) Standard is freely available to the public at XML for Location Services (XLS) : The Opens Platform Interoperability Enables LBS platform providers and content providers to provide their software and data to multiple carriers
30 A Key Standard : The Geomobility Server (GMS) The Relationship between LIF’s MLP, OGC’s GeoMobility Server and ASPs
31 A Key Standard : The Geomobility Server (GMS) A typical service/request response via the GeoMobility Server
32 A Key Standard : The Geomobility Server (GMS) OGC’s GMS provides open interfaces to core services for LBS Route determination Determine route and navigation information between locations Location utility Geocode : adress -> X, Y Reverse Geocode : X, Y -> Address Presentation Create display inforamtion showing map, route, POI, or route instructions Gateway Obtain position of a moble terminal “from the network” Directory Services Search for POIs
33 GMS basic information construct used by the GeoMobility Server and associated Core Services Consists of well-known data types and structures for location information Defined as application schemas that are encoded in XML for Location Services (XLS).
34 Use Case Example How a Position ADT might be used Q : Joe wants to see where his house is located on a map One way to do this is to have the Geocoder Service geocode his address, thus determining a Position ADT
35 Standards at Work in Find Friend Use Case in Chpater 2 developen by Kivera for AT & T Application was developed before most of the LBS standards described had been developed, Kivera could not take advantageof those specifications How the standards might be applied in this application?
36 Kivera – Web Demo
37 receive latitude/longitude coordinates pinpointing the location of a user’s mobile phone resolve these positions come from a Nortel GMLC Use Case : Find Friend Geocoding/Reverse geocoding subscriber would connect to the carrier’s portal to request service portal’s front end would transmit the request to the GeoMobility Server through an interface implementing the OpensLS specification GMS would use the LIF MLP API to get the subscriber’s coordinates from the GMLC/MPC Geocoding/Reverse geocoding beforeafter
38 TCS (Telecommunication System)
39 Friend Finder(Qualcomm Company)
40 Friend Finder
41 Friend Finder
42 Friend Finder
43 Friend Finder
44 Wireless Internet Platform for Interoperability (WIPI) in Korea Korea Wireless Internet Standardization Forum [KWISF] Established in 2001 Research and development of standard specifications for the wireless internet related technologies Wireless Application Protocol Wireless Internet Service (MMS, VOD etc) Terminal Services Network for Wireless Access WIPI Platform with Terminal Members SK Telecom KTF LG TeleCom ETRI RRL TTA Samsung Electronics LG Electronics Pantech & Curitel Telson Electronics Appeal Telecom IBM Motorola Sun Microsystems Qualcomm Nokia Etc(about 100 Implemeters)
45 Wireless Internet Platform for Interoperability (WIPI) Application execution environment specification for the mass market handsets Developed under the guidance of KWISF (Korea Wireless Internet Standardization Forum) as Forum Standard Made official standard in Korea through TTA (Telecommunication Technology Association) Specification embodies the knowledge of the carriers, handset vendors and application developers gained through deploying various platform technologies
46 Platform Architecture with WIPI WIPI Run-time Engine Basic API Handset Hardware & Native System Software HAL (Handset Adaptation Layer) Location Based Video Streaming Games Character/Bell Group Chatting IM MMS App. Manager Dynamic Component Manages application life cycle: download, install, stop, delete, etc. Updates/adds APIs and components to WIPI as dynamic linked library. Renders all the above layers in the stack hardware independent, thus the platform operates on common hardware abstraction layer. Set of APIs exposed to application programmers. These APIs support both programs written in C and Java TM programming language. APIs and components added/updated through App. Manager Area of Standardization
47 Vastly heterogeneous application run time environment in Korea(2000 ~ ) The RFP, containing the wish lists of the carriers, handset vendors and application developers, was disseminated by KWISF to platform developers Development project for the specifications and implementation began in 2001, with KWISF members (specially SKT, KTF, LGT, ETRI, TTA, RRL and about 26 members) as the project members SK Telecom / SK IMTKTF / KTiCOMLG TeleCom WIPI Implementation 1, WIPI Implementation 2, WIPI Implementation n Content Provider Content Provider Content Provider Handset Vendor Handset Vendor Handset Vendor SK Telecom GVMSK-VM KTF MAPBREW LG TeleCom CLDC/MIDP Content Provider Content Provider Content Provider Handset Vendor Handset Vendor Handset Vendor
48 Conclusion Interoperability is key to long-term success of location based services Some decent workarounds available today More robust standardized solutions are well on their way Business models to take advantage of interoperability are still being developed
49 Q & A