This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Background - 3GPP Long Term Evolution (LTE) Positioning Protocol (LPP)
Overview of LPPe Functionality
LPPe Version 1.0 Status
OMA Location in SIP/IP core (LOCSIP)
High-Level Architecture
Overview of LOCSIP Functionality
LOCSIP Version 1.0 Status
Disclaimer: This presentation is not an official OMA presentation
3
Secure User Plane Location (SUPL)
High-Level Architecture
SUPL
Agent
SUPL-Enabled
Terminal (SET)
/ SUPL Agent
LOCSIP,
MLP, …
SMSCSMS SMPP
PPG
POTAP PAP
ULP
Abbreviations:
LOCSIP Location in SIP/IP core
MLP Mobile Location Protocol
PAP WAP Push Access Protocol
POTAP WAP Push Over The Air Protocol
PPG WAP Push Proxy Gateway
SUPL
Location
Platform
SMPP Short Message Peer-to-Peer Protocol
SMS Short Message Service
SMSC Short Message Service Center
ULP UserPlane Location Protocol
WAP Wireless Access Protocol
Software or hardware
entity that accesses the
SUPL enabler to obtain
location information
SLP is responsible for
Location Service
Management and
Position Determination
SET is a logical entity in a
device that is capable of
communicating with a
SUPL Network
Example: Mobile
device used by
emergency caller
Example:
PSAP
4
SUPL V3.0 Capabilities
OMA SUPL V3.0 builds upon SUPL V1.0 and V2.0
Introduces new features
Enhances existing features
Some simplifications from SUPL V1.0 and V2.0
Additional bearers supported:
Fixed broadband (e.g., cable, DSL, etc.)
WLAN
Supported positioning protocols and positioning methods:
LTE Positioning Protocol (LPP) , LPP Extensions (LPPe), and TIA-801
Radio Resource LCS Protocol [RRLP] and Radio Resource Control [RRC] are no longer supported
Support for positioning methods based on LPP/LPPe and TIA-801
Supported modes of operation and roaming models:
Proxy mode only (non-proxy no longer supported in SUPL V3.0)
Only roaming with H-SLP supported (roaming with V-SLP is no longer supported)
Additional SUPL services /Other capabilities:
Generic SUPL Session (GSS)
Support of Discovered SLP (D-SLP)
Bearer and positioning-technology agnostic protocols (ULP and ILP)
5
SUPL V3.0 - Status
Requirements Document (OMA-RD-SUPL-V3_0-20100921-C) approved as candidatehttp://member.openmobilealliance.org/ftp/Public_documents/LOC/Permanent_documents/OMA-RD-SUPL-V3_0-20100921-C.zip
Architecture Document (OMA-AD-SUPL-V3_0-20110308-C) approved as candidate http://member.openmobilealliance.org/ftp/Public_documents/LOC/Permanent_documents/OMA-AD-SUPL-V3_0-20110308-C.zip
Technical Specifications [draft] (OMA-TS-ULP-V3_0-20110317-D) still being workedhttp://member.openmobilealliance.org/ftp/Public_documents/LOC/Permanent_documents/OMA-TS-ULP-V3_0-20110317-D.zip
No architecture document prepared, consistent with OMA „fast track‟ process
LPPe builds on OMA Location Services architecture as defined for SUPL
Technical Specifications [draft] (OMA-TS-LPPe-V1_0-20110211-D) available – OMA consistency review underwayhttp://member.openmobilealliance.org/ftp/Public_documents/LOC/Permanent_documents/OMA-TS-LPPe-V1_0-20110211-D.zip
Background - 3GPP Long Term Evolution (LTE) Positioning Protocol (LPP)
Overview of LPPe Functionality
LPPe Version 1.0 Status
OMA Location in SIP/IP core (LOCSIP)
High-Level Architecture
Overview of LOCSIP Functionality
LOCSIP Version 1.0 Status
12
SIP / IP Core
Location Client
Location Server
Target
13
2
Out-of-scope for LOCSIP
e.g., Secure User Plane
Location (SUPL)
Location in SIP/IP core (LOCSIP) High-Level Architecture
LOCSIP specifies how to use Session Initiation Protocol
(SIP) to obtain location information
Messaging is based
on SIP SUBSCRIBE /
NOTIFY procedures
Location Client - Functional entity
that subscribes to a Location Server
in order to obtain location information
for one or more Targets.
Location Server - Functional entity
that handles location service
subscription request and retrieves the
location information of the Target.
Target - The device or the
user associated with a device
whose location is requested.
13
Location in SIP/IP core (LOCSIP) Capabilities
LOCSIP allows an application to obtain location information in a SIP/IP core network (e.g., an IP Multimedia Subsystem [IMS])
Reuses capabilities in a SIP/IP core network (e.g., security associations, Application Servers) for receiving and responding to location subscriptions over a standardised SIP-based interface
Synergy with other OMA enablers that potentially use location information (e.g., Presence SIMPLE and PoC)
Reuse available IETF specifications (e.g., IETF Geopriv deliverables)
Rich set of capabilities include:
Support for “Immediate”, “Periodic” and “Area Trigger” Location Delivery
Support filtering of location notifications (accuracy, response time, age)
Support for Location Client in a SIP Application Server or in a terminal.
Location Client able to request location information for a group of Targets, based on referenced list or request-contained list
Support Geographic or Civic location information format
More detailed material was previously presented at Emergency Services Workshop 2010 “Location in SIP/IP Core (LOCSIP) - Location Conveyance with IMS: the OMA
LOCSIP Service Enabler”, 12-May-2010
____________________________________SIMPLE: SIP for Instant Messaging and Presence Leveraging Extensions
PoC: Push to talk Over Cellular
14
Location in SIP/IP core (LOCSIP) - Status
LOCSIP specifications originally attained candidate enabler status in August 2009 and were revised in August 2010