EENA 2016 - Standards Update (2/3)
29
-
Upload
eena-european-emergency-number-association -
Category
Technology
-
view
246 -
download
2
Transcript of EENA 2016 - Standards Update (2/3)
Outline
• Definition and description of IMS
– What?, When? and….
• … where and why (now) may IMS be important for PSAPs?
• Available standards
• Conclusions & recommendations
2
IMS QUESTIONSDefinition and description of IMS
3
IMS What?
• IP Multimedia Subsystem• 3GPP main standards
– TS 22.228 Service requirements for an IMS system.– TS 23.228 Architecture and main flows for an IMS system.– TS 24.229 IP multimedia call control protocol based on
Session Initiation Protocol (SIP) and Session DescriptionProtocol (SDP); Stage 3
– IETF• SIP RFC 3261• SDP RFC 3264• RTP RFC 1889• Diameter RFC 3588• Presence RFC 3856
4
UnderlyingNetwork
Technology 1
UnderlyingNetwork
Technology 2
UnderlyingNetwork
Technology 3
TraditionalTelco
Internet“startup”
IP
IMS What?
OTT overlayIMS
P-CSCF I-CSCF S-CSCF
HSS
MGCF
OMA SIMPLEPresence
RLS
Presence
XDMS
E-CSCF
LRF
PCRF
PCEFMRFP
SGW
EmergencyCall
PCC(QoS) transcoding
Interfacing
Cross-ciphering
IBCF
CARRIER GRADEIMS CORETELCO FRIENDLY
MultimediaOTT for telcos
5
IMS When?
1980 1990 2000 2010 2020
An
alo
g
GSM
GP
RS
UM
TS R
99
R4
R5
R6
R7
LTE
R8
R9
R1
0
R1
1
R1
2
R1
3
CIRCUITSWITCHING
VOICE CSDATA PS
DECOUPLINGNO CS
6
…IS (NOW) IMPORTANT FOR PSAPS?
WHERE AND WHY
7
Regular/Prioritized access on
commercial networks
ESINET
PSAPs 112/911Call
takers/Dispatchers
Emergency ControlCentres Authorities
Volunteers
Victims
Witnesses
PSTN
2G/3G
VoIP overPublic Access
Other/NG
First Responders
NG FR
ESINETESINET
Citizens to AuthorityAmong PSAPsAmong FRsPSAPs/Authorities FRsOther technologiesPSAPs Other AuthoritiesAuthorities to Citizens
Surveillance/Sensors
PMR
Other Technologies
(NG)112 in the Emergency Communication Ecosystem
8
Volunteers
ESINET
PSAPs 112/911Call
takers/DispatchersVictims
Emergency ControlCentres
Witnesses
PSTN
2G/3G
VoIP overPublic Access
Other/NG
ESINETESINET
(NG)112 in the Emergency Communication Ecosystem
9
First Responders
PSAPs 112/911Call
takers/Dispatchers
Surveillance/Sensors
Victims Volunteers
Authorities
Witnesses
PSTN
SDH/ATM/..
SS7
Acc
ess
Net
wo
rkTr
ansp
ort
Net
wo
rk
Co
ntr
ol/
Sign
allin
g
Voice
Serv
ice
Phone
Dev
ice
LLCTETRA
AI
SwMI
TETRAMLE
Voice callPTTSDS
TETRAterminal
MMI
XDSLCABLEFTTH
Agg.MPLS
IP
Prop/SIP
VoiceMultime
dia
VoIPAPP/
Phone
GERAN/UTR
AN
SGSN/GGSN
AAL5-ATM/IP
RRCRANA
PSSCP
VoiceSMSMMS
CellPhone
TETRAPOL
AI
SwMI
TETRAPOL
TLCC
MM
Voice callPTT
Data Poll
TETRAPOL
terminal
GPRS/UMTS
WiMAXPMROther
AccessDependant
Many
DataVideoeCALL
SensorVideoeCALL
IVS
PSTN
SDH/ATM/..
SS7
Voice
Phone
Prop/SIP
VoiceMultime
dia
VoIPAPP/
Phone
GERAN/UTR
AN
SGSN/GGSN
AAL5-ATM/IP
RRCRANA
PSSCP
VoiceSMSMMS
VoIPAPP/
Phone
P25
CAI
RFSS
P25NMMM
Voice callPTTData
P25
terminal
Many
ManyTowards IP
Many
VoiceMCV
eCALL
IntegratedControlRoom
XDSLCABLEFTTH
Agg.MPLS
IP
IMS Where and Why now?
10
IMS Where and Why now?
1980 1990 2000 2010 2020
An
alo
g
GSM
GP
RS
UM
TS R
99
R4
R5
R6
R7
LTE
R8
R9
R1
0
R1
1
R1
2
R1
3
CIRCUITSWITCHING
VOICE CSDATA PS
DECOUPLINGNO CS
CS-FALLBACK
SV-LTE
11
Acc
ess
Net
wo
rkTr
ansp
ort
Net
wo
rk
Co
ntr
ol/
Sign
allin
gSe
rvic
e
Phone
Dev
ice TETRA
terminalMMI
VoIPAPP/
Phone
CellPhone
TETRAPOL
terminal
SensorVideoeCALL
IVS
PhoneVoIPAPP/
Phone
VoIPAPP/
Phone
P25
terminal
IntegratedControlRoom
Rugged“SMART
PHONE”
SMARTPHONE
OT
TIP
PSTN
SDH/ATM/..
SS7
Voice
LLCTETRA
AI
SwMI
TETRAMLE
Voice callPTTSDS
XDSLCABLEFTTH
Agg.MPLS
IP
Prop/SIP
VoiceMultime
dia
GERAN/UTR
AN
SGSN/GGSN
AAL5-ATM/IP
RRCRANA
PSSCP
VoiceSMSMMS
TETRAPOL
AI
SwMI
TETRAPOL
TLCC
MM
Voice callPTT
Data Poll
GPRS/UMTS
WiMAXPMROther
AccessDependant
Many
DataVideoeCALL
PSTN
SDH/ATM/..
SS7
Voice
Prop/SIP
VoiceMultime
dia
GERAN/UTR
AN
SGSN/GGSN
AAL5-ATM/IP
RRCRANA
PSSCP
VoiceSMSMMS
P25
CAI
RFSS
P25NMMM
Voice callPTTData
Many
ManyTowards IP
Many
VoiceMCV
eCALL
XDSLCABLEFTTH
Agg.MPLS
IP
EPCIP
IMS
MCPTT
EUTRAN
EPCIP
IMS
VoLTE
EUTRAN
IMS Where and Why now?
First Responders
PSAPs 112/911Call
takers/Dispatchers
Surveillance/Sensors
Victims Volunteers
Authorities
Witnesses
12
Current status• VoLTE
• Next Generation Public Safety over LTE– Firstnet US – ESMCP UK– Europe
• Study on 'Use of commercial mobile networks and equipment for "mission-critical" high-speed broadband communications in specific sectors'
• DRS-18
– South Korea SafeNet
Source: http://www.gsma.com/network2020/resources/all-ip-statistics/
13
IMS STANDARDISATION3GPP
14
Standards
• Different SDOs and areas
– 3GPP emergency calling
– NG112/NG911 & IMS @ATIS
– 3GPP and NG PS
– IMS ecall
– ETSI Total Conversation
15
P-CSCF E-CSCF
S-CSCF
LRF
UE Gm Mw
MI
Mw
Mm/Mw
from PSAP
Mi/Mg
Mm
Le (e.g. E2)
to PSAP or ECS
via IP multimedia
Network
to PSAP
(via PSTN
via BGCF/
MGCF)
from PSAP
Evolution of emergency calling in 3GPP TS 23.167
2006 2007 2008 2009 2010 2011 2012 2013 2014 2015
R8
R11
R12
2016 2017
R13
R14
R7
R9
R10
LTE specific supportSession Continuity
(use of EATF)
Hosted Enterprise Services and
Private Networks (use of AS)
NOVES outcomesDifferent media types
Dynamic PCC
WLAN untrusted access
to EPC
eCall IMSEnhanced
indoor/outdoor location
ARCHUMTS PS and CS
LCSI-WLANNENA I2
16
R7
R10
R9
Evolution of emergency calling in 3GPP TS 23.167
P-CSCF E-CSCF
S-CSCF
LRF
UEGm Mw
MI
Mw
Mm/Mw
from PSAP
Mi/Mg
Mm
Le (e.g. E2)
to PSAP or ECSvia IP multimedia
Network
to PSAP(via PSTNvia BGCF/
MGCF)
from PSAP
P-CSCF E-CSCF
S-CSCF
LRF
UEGm Mw
MI
Mw
Mm/Mw
from PSAP
Mi/Mg
Mm
Le (e.g. E2)
to PSAP or ECSvia IP multimedia
Network
to PSAP(via PSTNvia BGCF/
MGCF)
from PSAP
EATF
I4
from I-CSCFI5
P-CSCF E-CSCF
S-CSCF
LRF
UEGm Mw
MI
Mw
Mm/Mx/Mw
from PSAP
Mi/Mg
Mm/Mx
Le (e.g. E2)
to PSAP or ECS(via IBCF/IPmultimediaNetwork)
to PSAP(via PSTNvia BGCF/
MGCF)
from PSAP
EATF
I4
from I-CSCFI5
From AS
ISC/Mw
From privatenetwork viaIBCF-I-CSCF Mx/Mw
Mw
17
Analysis / Discussion
• 3GPP specifies its own comprehensive / standalone system for emergencycalling• Specific support for different access technologies (procedures,
location…)• If PSAP is IMS user, CSCF can determine the route
• Otherwise, use a default exit point?• Some (old) interoperability with NENA i2• Keeps integrating new features
• NG112 LTD• ESInet as the core network, with BCF as entry point• PSAPs connected to the ESInet (directly or through access networks)• IMS as another access network
• Signalling / media issues?• QoS / policy issues?• Location: trusted? Access from external PSAP to LRF?
18
3GPP Public Safety Communications• Triggered by Public Safety administrations
• Huge effort to finish specifications in R13 (target freeze date: March 2016)
• Evolution– Stage 2 high level architecture
• SIP core, non IMS specific, but similar external interfaces
– Stage 3 protocol specifications• Mainly IMS-related protocol specifications
– “IMS Profile to support Mission Critical Push To Talk over LTE”
19
3GPP MCPTT Related SA Documents (R13, SA#71, March 2016)
Doc. Code Contents Vers. Resp.
3GPP TS 22.179 Requirements (Stage 1)13.3.0
(12-2015)S1
3GPP TR 23.779 Technical options - study and evaluation13.0.0
(09-2015)S6
3GPP TS 23.179Architecture, procedures and information flows (Stage 2)
13.1.0(03-2016)
S6
3GPP TR 26.879MCPTT media handling and codecs (key issues) -study and evaluation
13.0.0(12-2015)
S4
3GPP TS 26.346 MBMS protocols and codecs13.4.0
(03-2016)S4
3GPP TS 26.179 MCPTT media handling and codecs13.0.0
(03-2016)S4
3GPP TR 33.879MCPTT security aspects(key issues) - study and evaluation
13.0.0(03-2016)
S3
3GPP TS 33.179 MCPTT security framework13.0.0
(03-2016)S3
20
3GPP MCPTT Related SA Documents (R13, SA#71, March 2016)
Doc. Code Contents Vers. Resp.
3GPP TS 24.379MCPTT call control protocol specification 13.0.1
(03-2016)C1
3GPP TS 24.380 MCPTT floor control protocol specification13.0.2
(03-2016)C1
3GPP TS 24.381 MCPTT group management protocol specification13.0.1
(03-2016)C1
3GPP TS 24.382MCPTT identity management protocol specification
13.0.1(03-2016)
C1
3GPP TS 24.383 MCPTT Management Object (MO)13.0.1
(03-2016)C1
3GPP TS 24.384MCPTT configuration management; Protocol specification
13.0.1(03-2016)
C4
3GPP TS 24.980IMS Profile to support Mission Critical Push To Talk over LTE
13.0.1(03-2016)
C1
21
NG911 and IMS
• ATIS
Source: http://www.911.gov/pdf/NG911-Standards-Identification-Analysis_03222016.pdf
22
IMS eCALL
• ETSI TR 103 140– STF456
• Why we do it:– eCall is being deployed on 2G and 3G networks but these will not last forever. Already there are 4G networks,
and cooperative ITS is on the horizon.
• How we do it:– We are making proposals to 3GPP to show how eCall could be specified for 4G. We are considering how eCall
would migrate to 4G and ITS, and in this respect we make presentations to as many eCall stakeholderorganisations as possible (e.g. EeIP, HeERO, CEN TC 278, ETSI TC ITS, ISO TC204) to get their views.
• RATIONALE– In band eCALL not long lasting solution when compared with cars lifetime
23
UID code title%
doneRelease
lead Group
WIDlast updat
edremarks
impacts
700020 EIEIEvolution to and Interworking with eCall in IMS
12% Rel-14 SP-1502752015-06-09
12/15: created byMCC todistinguishStage 1 fromStage 2
22.101
680004Stage 1 of Evolutionto and Interworkingwith eCall in IMS
100% Rel-14 S1 SP-1502751970-01-01
22.101
700021 -Stage 2 of Evolutionto and Interworkingwith eCall in IMS
20% Rel-14 S2 SP-1506231970-01-01
7/3/16: 0%->20
23.167, 23.401
710020EIEI-CT
CT aspects of evolution to and interworking with
0% Rel-14 C6, C1 CP-1600531970-01-01
IMS eCALL (3GPP)
• The objective of this work item is to specify the system impacts for an eCall based on IMS emergency calls that will allow for enhanced eCall user experience and functionality, and for the long-term phase out of CS core and access networks. The work will be based on service requirements defined by WI EIEI in SA1 and captured in TS 22.101.
• Based on stage-1 requirements at least the following work is identified for SA2 so far:• TS 23 401: introduce eCall for EPS and define its impact on the procedures.• - TS 23.167: provide architectural and other stage 2 support.• Support of eCall based on IMS Emergency Services is expected to make use of the requirements captured in TS
22.101.• Support of eCall on IMS Emergency Services using the PS domain is only considered over LTE. eCall in CS mode or
using ICS procedures will be used when in GSM, or UMTS RATs, and is not in the scope of this work item.
24
112eCALL
ETSI total conversation
• STF 489
– TR 103.201 Implementation Guidelines
25
ETSI total conversation
• Identification and invocation of assisting relay service– Issue #1: Invoking the conference for inclusion of an assisting relay service
• Solution #3: Conference invocation in the ESInet
– Issue #2: Indicating/identifying the communication needs of the Total Conversation user• Solution #4: Use of Additional Data to indicate communication needs and / or a specific
relay service
– Issue #3: Emergency session handling at the assisting relay service• Solution #5: include a SIP priority tag in the call to the assisting relay service to indicate
its emergency status
– Issue #4: Obtaining the identity of a specific assisting service• Solution #2: Identity communicated by the Total Conversation user terminal
– Issue #5: Total Conversation user default behaviour
• Automatic translation– Solution #2: Automatic translation at the Total Conversation user terminal
26
Conclusions
2 G/3 G
CSFB
Evangelist
Tradit ional
PM ROt her
VoIP
Flavour
27
112eCALL
…. recommendations
28
• IMS is a worth considering zombie technology
• Gaining momentum• Haters gonna hate
– Overengineered– Telco only– “…..Just another” SIP technology
• LEGAL Disclaimer AKA “excusatio non petita accusation manifiesta”– Final reality may vary due to different factors*
* Including but not limited to technical issues, (un)intentionally incorrect publicly available info, my cognitive bias, market drivers, lobbying, telco/PS company cartel, political corruption, financial crisis…
