IMS-based emergency calling - Emergency Services Workshop

advertisement
Emergency Services Demo
with Location-based Services,
IMS, and WiMAX
Emerging Mobile Technologies Group
Telcordia Applied Research
May 11, 2010
Mike Loushine (PM)
Andrei Ghetie
Melbourne Barton
Don Lukacs
Copyright © 2010 Telcordia Technologies, Inc.
All rights reserved.
Phiroz Madon
Dan Harasty
Vijay Varma
Nicholas Linnenkamp
Outline







Demo Objectives
Technology Standards Supported
Demo Scenario
Demo Architecture
Demo Contributions
On to the Demo…
Lessons Learned
2
Demo Objectives
 Explore the potential of ubiquitous locationbased services and the IP Multimedia
Services (IMS) platform
 Demonstrate using IMS location and
presence service building-blocks to make an
E911 emergency services application
3
Demo Objectives
 Provide feedback to Standards Forums based
on experiences from the demonstrations
4
Supporting Standards –
OMA LOCSIP Technical Specification
Implementer: Telcordia
Location
Client
LS-1
PRS-17
Home
Subscription
Agent
Remote
SIP/IP
Core
IP-1
PRS-4
SIP/IP
Core
XDM-2
Implementation:
 Location Client
 Location Server
 Resource List Server
Resource List Server
PRS-10
PRS-9
RLS
XDMS
Shared
List
XDMS
XDMC
Location
Policy XDMS
XDM Enabler
XDM-14
XDM-12
Trusted XDMC
GPM.PEM-1
LS-2
GPM
Location Server
5
Role in Demo:
 Provide ongoing locations,
situational awareness for all
actors involved in
Emergency scenario
 Support location-based
resource list queries
Supporting Standards –
OMA Presence SIMPLE V2 Specification
DM
Client
DM-1
DM
Server
PRS-17
Watcher
Agent
Subscription Proxy
XDM-10
Implementer: Telcordia
XDM-2
SIP/IP
Core
Watcher
Information
Subscriber
PRS-9
Resource
PRS-4
Resource
List
ListServer
Server
PRS-10
PRS-16
RLS
XDMS
PRS-11
Watcher
Watcher
PRS-2
PRS-14
PRS-15
Presence
Presence
Source
Source
Shared
List
XDMS
Content
Server
PRS-13
PRS-6
PRS-1
Presence
XDMS
PRS-8
PRS-19
PRS-3
PRS-12
Presence
Presence
Server
Server
Implementation:
 Presence Source
 Watcher
 Presence Server
 Resource List Server
PRS-5
PRS-21
PRS-20
Presence
Content
XDMS
PRS-7
XDM-4
 Provide situational
awareness of actors in
scenario through status
publish and notifications
PRS-18
XDM-1
XDMC
Aggregation Proxy
XDM-3
XDM-8
IP-1
Cross-Network Proxy
NNI-1
SIP/IP Core
Cross-Network Proxy
Remote Network
NOTE:
Bold boxes identify Presence SIMPLE functional entities that are defined by this document.
Bold arrows identify Presence SIMPLE reference points that are defined by this document.
Role in Demo:
6
Supporting Standards –
3GPP IMS Emergency Services Specification
(3GPP TS 23.267)
Implementer: FOKUS
Le (e.g. E2)
from PSAP
LRF
to PSAP or ECS
via IP multimedia
Network
MI
Mm
UE
Gm
Mw
P-CSCF
E-CSCF
Mi/Mg
EATF
Role in Demo:
Mm/Mw
S-CSCF
 Open Source IMS Core
Network
 Emergency Services Branch
to PSAP
(via PSTN
via BGCF/
MGCF)
I4
Mw
Implementation:
from PSAP
7
 Routes IMS SIP-based
messages between multiple
clients and IMS application
servers
 Routes 911 call from person
in trouble to appropriate
PSAP
Supporting Standards –
IETF HELD Specification
Implementer: BBN
<MJL: FInd a picture or else center text.>
Implementation:
 HELD Client
 HELD Location Information
Server (LIS)
Role in Demo:
 Enables IMS Client who makes
911 call to determine its own
location
 Location is then published
over IMS, providing dispatcher
with the location
Source: Andrew Corporation
8
Supporting Standards –
IETF LoST Specification
Implementer: Columbia U.
Implementation:
 Location-to-Service
Translation (LoST) Server
Role in Demo:
 Provides PSAP URI based on
terminal location
9
GSMA Rich Communication Suite –
Release 1, 2, and 3
Implementer: Telcordia
Implementation:


RCS Device
Presence Server
Role in Demo:


Publish presence to a
Presence Server
Publish location
information to the LOCSIP
Location Server
 Note: not part of any
current specification
10
WiMAX (IEEE 802.16e Specification)
R1
ASN
ASN
GW
BS
R6
CPE
Implementer: MAXWell Lab
BS
R3
Implementation:
CSN
AAA
DHCP/
DNS
 WiMAX Network
HA/
Router
PF
Role in Demo:
 Transmit and receive voice,
video, and situational
awareness data
Internet / Application
Service Provider
(ASP) Network
11
Standards functionality demonstrated…
 3GPP IMS to
 provide a SIP/IP core
network infrastructure
 route 911 calls
 OMA LOCSIP to
 IETF LoST to
 select the PSAP to answer
911 calls
 GSMA RCS to
 publish locations and
presence
 perform user-based position
determination of terminals
 convey terminal locations
 provide situational
awareness
 OMA Presence SIMPLE
to
 provide situational
awareness through status
publish and notifications
 IETF HELD to
 perform network-based
position determination of
terminals
 WiMAX to
 transmit and receive voice,
video, and situational
awareness data
12
Demo Scenario – PSAP View
13
Demo Architecture
PSAP
911 Caller
UMDP Patrol Car
PGFD Fire Chief
HELD
LIS
Google
Network
Location
Service
WiMAX
Network
MyVue Clients
(Interoperability
– Maryland Day)
ROVER
Server
P-CSCF
E-CSCF
LRF
IMS Core
S-CSCF
I-CSCF
HSS
LOCSIP
Servers
Resource List
Server
Presence
Server
14
Location
Server
LOST
Server
Demo Contributions
 Created prototype of the OMA LOCSIP Architecture
 Location Server
 Location Client
 Resource List Server
 Performed interoperability test between Telcordia LOCSIP
Location Server and FOKUS Emergency Services IMS Core
 LOCSIP Location Server - LRF Interface
 Integrated OMA LOCSIP and Presence Services
 Presence Server – LOCSIP Location Server
 Implemented aspects of GSMA Rich Communication Suite
Release 3 approach to location-based services with OMA LOCSIP
and Presence Services
 RCS Device – LOCSIP Location Server
 RCS Device – Presence Server
15
Contact
For more information, contact :
Mike Loushine
Senior Scientist / Program Manager
[email protected]
Office: +1 (732) 758-5358
Mobile: +1 (732) 762-0242
16
Sit back and enjoy the demos…
17
Demo Presentation…
18
Lessons Learned

IMS location, presence, resource-list building-blocks are quite versatile for
constructing a variety of useful services and applications. Some additional
ideas for location-based services:
 Lost child or pet location
 Traffic monitoring over a comprehensive set of roads. Integration of this service with
people’s car GPS systems
 Social networking with the added dimension of location
 Situational awareness applications.

SIP headers, their values and meanings, can be open to interpretation!
 For interoperability, following the specs can get you 75% of the way
 After that, end-to-end debugging is needed.

PIDF-LO XML format is also open to interpretation
 RFC 4479 “A Data Model for Presence” makes a significant departure from earlier
RFCs (most notably, 4119) on the PIDF XML format
 End-to-end debugging is needed, for interoperability

Performance and scaling are issues that will have to be systematically
addressed
 We started seeing problems (over a wired Ethernet) at ~20 SIP messages/sec
 A NOTIFY message with a RCS-specified XML body is 2 K bytes
 Problems are typically due to time-outs caused by long wait times as messages go
through the core.
19
Download
Related flashcards
Create Flashcards