NG112 and the new Emergency Services Networks landscape · 08-502 E9-1-1 Requirements Informaon Document 2004/07/23 08-501 ... • Driven by the PSAP community (users and industry)

NG112 and the new Emergency Services Networks landscape

Fidel Liberal [email protected]

Challenges and opportunities

Executive Summary

• NG112 and next generation emergency networks

•  Challenges and opportunities

>  The evolution of telco technologies has significantly changed the way people communicate >  Multimedia capabilities are available everywhere >  This evolution has reached also the emergency networks ecosystem in different areas >  How this new landscape will impact NG112 from different (technical, economical, legal/regulatory) points of view will

be analyzed

2

Table of Contents •  1.-Introduc-on•  2.-NG112•  3.-IMS•  4.-SIPConnect2.0•  5.-M/493•  6.-PEMEA•  7.-(NG)eCALL•  8.-AML•  9.-WebRTC•  10.-Others•  11.-MCPTT•  12.-Transna-onalexperiences•  13.-Conclusions

3

CHAPTER

1Introduction: The next generation emergency networks landscape

No se puede mostrar la imagen. Puede que su equipo no tenga suficiente memoria para abrir la imagen o que ésta esté dañada. Reinicie el equipo y, a continuación, abra

FirstResponders

MCPTToverLTE

Next Genera2on Emergency Networks landscape

5

Regular/Priori-zedaccessoncommercialnetworksESINET

PSAPs112/911Calltakers/Dispatchers

EmergencyControlCentres Authori-es

Volunteers

Vic-ms

Witnesses

PSTN

2G/3G

VoIPoverPublicAccess

Other/NG

ESINETESINET

Ci#zenstoAuthorityAmongPSAPsAmongFRsPSAPs/Authori#esóFRsOthertechnologiesPSAPsóOtherAuthori#esAuthori#estoCi#zens

Surveillance/Sensors

PMR

OtherTechnologies

eCall


6 FirstResponders

MCPTToverLTE

Regular/Priori9zedaccessoncommercialnetworksESINET


EmergencyControlCentres Authori9es

Volunteers

Vic9ms

Witnesses

PSTN

2G/3G


Other/NG

ESINETESINET


Surveillance/Sensors

PMR

OtherTechnologies

eCall

Volunteers

ESINET


Vic-ms

EmergencyControlCentres

Witnesses

PSTN

2G/3G


Other/NG

ESINETESINET


NG112is“only”aspecificpartoftheNGEmergencyNetworksecosystem


7

NG112

eCALL

Evolu#onofcommercialtechnologies

Evolu#onofNGPSNetworks

Evolu-onofcommunica-onslandscape

Mul-mediacapabili-esandVoIParebecomingavailableineverysingletechnologydomainintheemergencynetworks

Q:IsLongTermDefini#onArchitecture“LongTerm”enough?


8

NG112

Funding

Contractualobliga#ons

Legisla#on

FragmentedOrganiza#ons

Notonlytechnicalimpact

NewFundingopportuni-esNewEmergencysupra-na-onalorganiza-onsinEuropeNewlegisla-on/harmoniza-on?

Q:Willnon-technicalaspectsbecomethekeydriverstoNG112adop#on?


9

NG112

Ci#zens

Regulators SDOsPSAPS

Stakeholders

Specific“interestgroups”mayhaveabigrelevanceintoNG112evolu-onandsuccessExample:MobileOSCaseStudy1:AMLCaseStudy2:VoLTE/RCS

M(V)NOs

UEmanufacturers

Internet/devcommunity

Q:Howwillspecificstakeholders’interestsimpactNG112?

Conclusions

• Bothgeneralpurpose-andemergency-communica-onslandscapehavesignificantlyevolvedsinceNG112LTDarchitecturewasini-allyconceived

•  Furthermore,manyfactorswhichwilllikelyaffectNG112evolu-onarenottechnicalones

• Arevisionofnewtechnologiesandstakeholders’posi-onsneedstobecarriedouttocheckNG112’shealthandlongevity

• Adertheanalysisweshouldbeabletoanswertothefollowing…

10

… ques2ons

11

Will new technology/situation X probably…

• …replace …

• …complement …

• …push …

• …delay …

…NG112?

CHAPTER EENA NG112 2

History of NG112 architecture

• NG9-1-1&NG112

Ref:hgp://www.nena.org/resource/resmgr/ng9-1-1_project/ng9-1-1_history.pdf2000 2005 2010 2015 2020

Planningfor

NG-9-1-1

NENANG911Project

Func#onalandinterfacestandards

Detailedfunc#onalandinterfacestandardsfori3

Firstinteroperability(ICE)event

StateofWashington

FirstState-wideESINET

IETFECRITBOF

I3RequirementsDocument

NG112LTDpublishedIntroduc#onto

EuropeanNG-112

NG112standardiza#onac#vi#esinETSI

13

History of NG112 architecture

•  I3ArchitecturefromNENA’sNG9-1-1

Doc Number Doc Name Approved Date NENA-STA-010.2-2016 (originally 08-003) DetailedFunc-onalandInterfaceStandardsfortheNENAi3Solu-on 2016/09/10 NENA/APCO-REQ-001.1.1-2016 NENA/APCONG9-1-1PSAPRequirementsDocument 2016/01/15 NENA-INF-009.1-2014 RequirementsforaNa-onalForestGuideInforma-onDocument 2014/08/14 NENA-INF-006.1-2014 NG9-1-1PlanningGuidelinesInforma-onDocument 2014/01/08 NENA-INF-003.1-2013 Poten-alPointsofDemarca-oninNG9-1-1NetworksInforma-onDocument 2013/03/21 08-506 EmergencyServicesIPNetworkDesignforNG9-1-1Informa-onDocument*****UpdateInProgress***** 2011/12/14 57-750 NG9-1-1SystemandPSAPOpera-onalFeaturesandCapabili-esRequirementsDocument 2011/06/14 73-501 UseCases&SuggestedRequirementsforNon-Voice-CentricEmergencyServicesInforma-onDocument 2011/01/11 08-002 Func-onalandInterfaceStandardsforNextGenera-on9-1-1Version 2007/12/18 08-505 MethodsforLoca-onDetermina-ontoSupportIP-BasedEmergencyServicesInforma-onDocument 2006/12/21 08-752 Loca-onInforma-ontoSupportIP-BasedEmergencyServicesRequirementsDocument 2006/12/21 08-751 NENAi3RequirementsDocument 2006/09/28 08-502 E9-1-1RequirementsInforma-onDocument 2004/07/23

08-501 InterfacebetweentheE9-1-1ServiceProviderNetworkandtheInternetProtocol(IP)PSAPInforma-onDocument 2004/06/15

14

MCPTT

Meanwhile

2000 2005 2010 2015 2020

R4

R5

R6

PSTNshutdown

R7

LTER8

R9

R10

R11

R12

R13

R14

R15

AMLPEMEA

15 2018

NG112: Architecture

BCF

LIS/interface ESRP

ECRF

PSAP-1

PSAP-2

PSAP-N

ESINET

PSAPDOMAIN

VoIPCapable

ACCESSNET

LNGLegacyACCESSNET

UE

UE

L/R

DifferentOrigina-ngNetworks

Loca#onnode

LIF

PIF NIFBCF

LNG

16

NG112: Main characteris2cs

•  “Driven”byPSAPindustryandusers(groupedinNENA/EENA)•  Toberevisiteduponnewcommunica-onsparadigms(unbound/unregulated)

•  Evolu-onof112to(Vo)IP•  Voice+Video+RTTcapable•  Loca-onconveyancebyvalue/referencepossiblyassistedbydifferentnodes•  Advancedcallrou-ngconsideringPSAPs’specificdemands

• Origina-ngnetworkagnos-c(beforeAll-IPnetworks)•  LNG+BCFasthekeyenablersformul-pleheterogeneousorigina-ngnetworks

• DifferentPSAPmodels•  EmergencycallsaredeliveredintheBCF“PointofPresence”andinternallyroutedaccordingto“complex”PSAP-definedESINETpoliciesRef:EENALTD1.1 17

NG112: Key technologies/protocols

•  Signalling:•  Overall

•  SIP/RTP•  UseofSOSserviceurnforemergencycallrou-ng

•  Loca-onquerying/retrieval/update•  Geoloca-onheader(byvalue/byreference)

•  PIDF-LO•  ByValue

•  Mul-partMIMEbody•  ByReference

•  HELD(HTTPtransport)•  SIPsubscribe/no-fymechanisms(SIPsimple)

•  LOST•  Loca-ontoservicemapping,HTTPtransport

Ref:EENALTD1.1 18

NG112: Key technologies/protocols

• Media•  Codec

•  Audio:G.711(uandalaws)mandatory.AMR,AMR-WB,EVRC-*recommended•  Video:H264/MPEG-410Baselineprofilemandatory.ScalableBaselinerecommended•  Non-human:CAP,EDXL

•  Messaging•  RTT(RFC5194and4103)•  IM:SIP/SIMPLE&MSRP

Ref:EENALTD1.1 19

NG112: Current status • NG112

•  Plugtestevents’conclusions•  15organiza-ons(Asia,Europe,North-America)•  NG112coreelementsstable

•  Commercialstatus•  Termappearingintenders•  NG112“buzzword”?

Ref:hgp://www.eena.org/publica-ons/next-genera-on-112-report-of-ng112-communica-ons-plugtests-event-now-available20

Company UE/APP IMS UC PIF NIF BCF LIS ESRP ECRF PSAP XXXXX X X XXXXX X X XXXXX x X XXXXX X XXXXX X X X X X XXXXX X X …

XXXXX X X X XXXXX X X X X XXXXX X XXXXX X X XXXXX X

AVAILABILITY YES YES YES YES YES YES YES YES YES YES

NG112: Current status • NG9-1-1

Ref:hgp://www.nena.org/?NG911_StateAc-vity21

Na-onal-wideLOSTrou-ngs-llanissue

Analysis of new landscape

22

Is EENA NG112 … • …pushing …

• …delaying …

…NG112?

Analysis of NG112 & new landscape •  Technicalinteroperabilityques-ons

•  NG112specificSIPheadersandMIMEformatsóSBCs,otherSIPbasedsystems•  Codecs

•  Tobeanalysedinap2pbasis

•  Concernsoftheneedforstandardsolu-ons(atall)andstandardizingwholearchitecture•  LTDbasedonstandardized(i.e.byIETF)protocolsanddataformats•  DebateintheUSonNG911standard/NENASDOstatus•  Standardiza-onac-vi-esinETSIongoing

•  Lackofawareness•  TelcoworldnotfullyfamiliarwithNG112architectureandactualtechnicaldetails

•  Isemergencycallrou-ngbyanymeansabusinesscaseforM(V)NOsorontheotherhandconsideredasunfairdutyduetoUniversalServicedirec-ves

•  Advantagesofhavingastandards-basedsolu-on•  Mul-plelocal-onlyandproprietaryappsallegedlyprovidingequivalentfunc-onali-es

•  SIPs-llthemostlyused/bestcandidate?•  WebRTC

•  Missing(regional/na-onal/european)levelharmoniza-on

23

Analysis of NG112: already taken measures

Ref:EENAworkshopsreports2015and2017 24

Conclusions

•  NG112LTDarchitectureisbasedoni3fromNENA•  Defini-onoverthelastdecade•  DrivenbythePSAPcommunity(usersandindustry)•  Usesstandardizedandwellknownprotocols(SIP/RTP,HELD,LOST)andcodecs

•  Mainpurpose•  VoIP,totalconversa-onandloca-on•  DifferentPSAPmodels(emergencycallrou-ngpoliciesintheESINET)•  Accommoda-ngdifferentorigina-ngnetworks

•  Beforenetworksmovingtoall-(Vo)IP•  “Noneed”forNG112appbutcouldreusena-vemul-mediacapabili-es(i.e.byaccommoda-ngVoLTE)

•  Currentstatus•  Slowadop-oninEurope,some-mesduelackofawarenessandmisunderstanding•  Needtofightwithproprietary“NG”112solu-ons

•  Valueofstandardizedsolu-onsapparentlyunclearforpurchasers•  Newroleofparadigm-shidingtechnologies(unregulated/uncontrolled)s-llunclear•  Unclearshareofresponsibili-esfordeployments

•  OperatorsduetoUniversalServicedirec-ves?•  Emergencybodies/ControlCentres•  Whathappenswithunregulatedcommunica-onislands(WhatsApp,Skype,Line,FBMessenger,GoogleTalk)?

25

CHAPTER IMS

3

IMS: Main characteris2cs

•  Definedby3GPPRelease5•  Drivenbytelcovendors

•  Fromini-alhypeólongperiodofno-business-caseórebirthwithVoLTE&PSTNshutdown

•  VoLTE!=IMS!=RCS•  Emergencycallingbuil-nineveryVoLTE+RCScapable4Gphone

•  IMS+LTE(emergency)registra-on•  Noneedforaddi-onalapp

•  Iden-fica-on:SIM/IMEIbased•  Loca-on:

•  Geoloca-onHeader:UE,LRF(byreference)•  P-ANI:P-CSCF,S-CSCF

Ref:TS24229 27

IMS: Key technologies/protocols


•  SIP/RTP•  Specificheaders+tags

•  inoverallIMS•  specifictoVxLTE

•  Loca-onconveyanceinemergencysessions•  Ifloca-on/URIisavailableintheUE=>PIDF-LORFC4119/6442•  Other(Networkassisted)

Ref:TS24229 28

IMS/VxLTE/RCS: Key technologies/protocols

• NOTE:VxLTE-RCS=>subsetofIMS(GSMA)• Media

•  Codec•  Audio:AMR&AMR-WBmandatory,EVSop-onal•  Video:H.264ConstrainedHighProfile(CHP)Level3.1asspecifiedin3GPPrelease13TS26.114

•  Messaging•  SIPMessage•  RTT

•  TelephonyservicesTS26114•  ITUT-140(RFC4103)

•  MSRP

Ref:GSMAIR.92,GSMAIR.94 29

ARCHUMTSPSandCS

LCSI-WLANNENAI2

2006 2007 2008 2009 2010 2011 2012 2013 2014 2015

R8

R11

R12

2016 2017

R13R14

R7

R9R10

LTEspecificsupportSessionCon#nuity(use

ofEATF)

HostedEnterpriseServicesandPrivateNetworks(useofAS)

NOVESoutcomesDifferentmediatypes

DynamicPCC

WLANuntrustedaccesstoEPC

eCallIMSEnhancedindoor/outdoorloca#on

30

Evolu2on of emergency calling 3GPP TS 23.167

IMS: emergency calling architecture

P-CSCF E-CSCF

S-CSCF

LRF

UEGm Mw

MI

Mw

Mm/Mx/Mw

fromPSAP

Mi/Mg

Mm/Mx

Le(e.g.E2)

toPSAPorECS(viaIBCF/IPmul#mediaNetwork)

toPSAP(viaPSTNviaBGCF/MGCF)

fromPSAP

EATF

I4

fromI-CSCFI5

FromAS

ISC/Mw

FromprivatenetworkviaIBCF-I-CSCF Mx/Mw

Mw

31

NOTE1:lihlereferencetonon-3GPPaccessorigina#ngnetworks

NOTE2:Legacyandi2PSAPasfinaldes#na#on

NOTE3:Le(i.e.GMLCnotdirectlyconsideredasLISinterfaceinNG112)

Analysis of IMS

• Mainconcernsiden-fied•  AlignmentofNG112withIMS

•  SOSurnIMS=>COMPATIBLE•  TS24229

•  Sec-on5.1.6.8.X(referencetoTS22101)anduseofurn:service:sosinR-URIinorigina-ngUE•  MSRP/SIPsimplepresence•  Deploymentissues

•  SBC&SOSurn

32

IMS/RCS/VoLTE status

•  IMSgainingmomentum•  NotonlyVoLTEbutreplacementofSS7/PSTN

•  IMSwillbeprobablyincorporatedinto5G

33 Ref:hgps://www.gsma.com/futurenetworks/resources/all-ip-sta-s-cs/

IMS and emergency calling: current status

• MostIMScoresdonotsupportna-veemergencycalling•  Duetothelackof:

•  NG-capable-PSAPs•  regulatoryobliga-ontoprovidemul-mediaexchangecapabili-eswhilecalling112=>no“businesscase”

•  legacyPSTN“breakout”mechanismsinplace•  In4G=>CSfallback

•  IftheP-CSCFrecognizesanemergencynumberorurn:service:sos•  380Alterna-veServicewithandXMLbodyó<ims-3gpp>element,withthe<alterna-ve-service>.

•  TheUEagemptstheCSdomain.

34

NG911 and IMS

• ATISRef:NG911Standardsiden-fica-onandReviewMarch2017

35

NG911 and IMS

•  NextGenera-on9-1-1networkandemergencycallprocessingarchitecturebasedon:•  contribu-onsreceivedsince2011•  requirementsbyanumberofwirelesscarrierstohaveanIPMul-mediaSubsystem(IMS)-compa-bleNG9-1-1design.•  NENAi3ArchitectureWorkingGroupdeferredtheIMS-basedESInetdevelopmenttoATIS.

•  ATIS’goalindevelopingthisstandardhasbeentransparentinteroperabilitybetweenthetwonetworkdesigns.

•  ATIS’intentinthisdevelopmentworkwastoproduceastandardmethodforIMS-basedcarrierstoofferNG9-1-1serviceswhollywithintheirIMSplatorms,whilemaintainingconsistencyandinteroperabilitywiththeNENAi3ESInet/NGCS(NextGenera-onCoreServices)designgoals.

•  transparency,bothupstreamanddownstreambetweenarchitectures,ensuresthatani3PSAPshouldfindnodifferencewhetherthei3PSAPinterconnectstoaNENAi3ESInetwithNGCS,orinterconnectstoanATISIMS-basedNG9-1-1ServiceArchitecture.

•  Foren--esearlyintheprocessofselec-ngESInetsolu-ons,theexpecta-onwithinthisATISdevelopmentworkwasthattheATISIMS-basedNG9-1-1ServiceArchitecturewouldofferachoiceforcarriersthatalreadyhadanIMSecosystem,butnotbeconsideredaviablearchitecturechoicefor9-1-1serviceen--esthathadnoplansforanIMSinfrastructure.

•  PublicSafetyen--esshouldnaturallyunderstandtheapplicabilityofanIMS-basedNG9-1-1ServiceArchitecturenetworkapproachtoprocessingemergencycalls,yetinthiscase,theycanremainconfidentlyfocusedonNENAi3-basedNG9-1-1architectures,(thisisbecauseIMSmaybeofinteresttocarriers,nottojurisdic-ons),whichmeansthatPublicSafety’sprogressandmomentumtoadoptNG9-1-1willnotbeimpededbytheintroduc-onofthisATISNG9-1-1ServiceArchitecturestandard.

Ref:ATIS0500032

36

IMS and emergency calling: current status

• Universalservicedirec-veshouldbeappliedtoanyVoIPcall(notonlybutincludingIMSbased)

•  Inanycaseemergencycallingduring(inter)na-onal(i.e.unregistered)roamingnotconsideredbyna-onalregula-ons

37 Ref:CaseStudiesonIP-basedInterconnec-onforVoiceServicesintheEuropeanUnion.BEREC

Ref:112andtheEULegisla-veFrameworkEENA.

IMS and NG112: Interconnec2on example

38

P-CSCF E-CSCF

S-CSCF

LRF

UEGm Mw

MI

Mw

Mm/Mx

Mw

BCF

LIS/interface

ESRP

ECRF

PSAP-1

PSAP-2

PSAP-N

ESINET

PSAPDOMAIN

L/R

(M)(V)NOrou-ngtoNa-onal/Regional/LocalPointofpresence

IMS and NG112: Interconnec2on example •  Testedin1stand2ndNG112plugtestshostedbyETSIin2016&2017•  Leinterfacenotmandatoryby3GPP:mayuseMLP….

•  EastwoundNG112LISinterfacecompa-ble

• VoLTE(IMS)awareBCF•  SIPsani-zing

•  IMSspecificheaders•  BorderControlling•  B2BUAmode•  Trans-codingifAMR-WBnotsupportedintheESINET•  QoSpre-condi-ons

39

IMS and NG112: Interconnec2on example •  Loca-on(ini-al)conveyance

•  FromUEorNetworkassistedusingPANIinforma-on

•  Loca-onupdate•  Notconsideredinthe1stNG112plugtest

•  SIPpresencebasedmechanism+LISSubscribe/No-fy?

• Messaging•  MSRPconsideredinNG112

• ALTERNATIVE:•  ATIS0500032

40

Analysis / Discussion: …will replace?...

•  3GPPspecifiesitsowncomprehensive/standalonesystemforemergencycalling•  Specificsupportfordifferentaccesstechnologies(procedures,loca-on…)•  IfPSAPisIMSuser,CSCFcandeterminetheroute

•  Otherwise,useadefaultexitpoint?•  Some(old)interoperabilitywithNENAi2•  Keepsintegra-ngnewfeatures

•  Thelackofwidespreadadop-onofIMSasVoIPtechnologyandmissingfeaturesmo-vatedtheneedfori3architectureandprotocolsinthelast10years•  Anylonger?

•  Missingfeaturesinoriginal(3GPP’s):•  Advancedpolicyrou-ng•  Explicitintegra-onofnon-IMStechnologies•  Unifiedloca-onretrievalmechanism(fromPSAPs)

41

Analysis / Discussion: …will complement?...

•  NG112LTD•  ESInetasthecorenetwork,withBCFasentrypoint•  PSAPsconnectedtotheESInet(directlyorthroughaccessnetworks)

•  IMSasanotheraccessnetwork•  Signalling/mediaissues?•  QoS/policyissues?•  Loca-on:trusted?AccessfromexternalPSAPtoLRF?

42


43

Will IMS/VxLTE/RCS probably… • …replace …

•  AcompleteIMScorewouldbecomeaprerequisiteforANYorigina-ngnetwork

• …complement … •  commercialoperatorbasedrou-ngtosinglePoP(BCF)andlaterPSAP-awarerou-ngintheESINET

• …push … •  na-veNG112supportinevery4GphoneóVxLTEcapableódifferentpenetra-ons

• …delay … •  IfeverythingisbecomingIMS,shouldIwaittoIMSbasedNG112?NOTEonATISIMScomment(notfromaPSAPpointofview)

…NG112?

CHAPTER SIPconnect 2.0 4

SIPconnect: Main characteris2cs

•  Industry-wide,standards-basedapproachtodirectIPpeeringbetweenSIP-enabledIPPBXsandVoIPserviceprovidernetworks

•  DrivenbyVoIPIndustry(SIPForum)•  NotanSDObutinteroperabilityevents(SIPit),compliancetests,bestprac-ces..

•  Tworeferencepoints(Signallingandmedia)•  BetweenEnterpriseNetworkandtheServiceProviderNetwork•  Theprimaryserviceaudio-basedcallorigina-onand/ortermina-onbetweentheEnterpriseandServiceProviderNetworks,includingemergencyservices.Thedeliveryofanyotherservice(e.g.instantmessaging,etc.)isoutofscope.

•  Emergencyaspects•  Specifica-on1.1

•  AroadmaponwhatimplementerscanexpectinsubsequentSIPconnectrevisions(IPv6,EmergencyServices,etc.)

•  Specifica-on2.0•  Specifica-onofminimumrequirementsforemergencycalling

Ref:SIPForum 45

SIPconnect: Key technologies/protocols


•  SIP/SDP•  RFC3261/RFC3264+Specificprofile•  Registra-onandsta-cmodes•  TLS•  E.164;user=phone

•  Otheriden--esoutofscope•  (S)RTP

• Media:•  CodecG.711PCM(a,ulaws)mandatory,G.729op-onal

Ref:SIPconnectTechnicalSpecifica-on2.0 46

47

History of SIPconnect

2000 2005 2010 2015 2020

SipConnectComplianceProgramIPPBXand

ServiceProviderInteroperabilityTaskGroup

SIPconnectCer#fica#on

Tes#ngProgram

SIPconnectTechnical

Recommenda#on1.1

SIPconnectTechnical

Recommenda#on1.0

SIPconnectTechnical

Recommenda#on2.0

SIPconnect: reference architecture

SIP-PBXSIPSignalingEn#ty(SP-SSE)

48

MediaEndpoint MediaEndpoint(2)RTP/SRTP

(1)SIP

SessionBorder

Controller

EnterpriseNetworkServiceProviderNetwork

SIPconnect and emergency calling

• Voicecalling“only”•  R-URI=>dialstringURIwithna-onalnumber(notserviceurn)•  PAI

•  Loca-onconveyance•  MAY/SHOULD(notmandatory)•  Geoloca-onHeaderRFC6442+pidf-loRFC5491,RFC4119

•  SIPForum3.0•  STIR/SHAKENtrustworthyID

49


50

Will SIPconnect… • …replace …

•  Notlikely:veryspecificreferencepoints(SIPexchange/trunking)• …complement …

•  NA

• …push … •  Notlikely.Origina-ngenterpriseSIPnetworks“only”•  Referencepointsnotfullyaligned

•  +112insteadossosserviceurn

• …delay … • Willdependoftheevolu-onofSIPconnectadop-onvs.IMSvs.NG112

…NG112?

CHAPTER M/493

5

M/493: Main characteris2cs

•  Loca-ondetermina-onandtransport• DrivenbyECdemands

•  “Thedetermina-onandtransportofcallerloca-oninforma-onforVoIPneedstobefullystandardised”

•  singlefunc-onalmodel+thenecessaryinterfacesandprotocols.•  Theenhancement,i.e.loca-ondataprovisionmaybedeliveredbymeansoftradi-onalornewmethods

•  ThisworkshallnotbefocusedonNGNbutshalladdresscurrentimplementa-onsforalltypesofvoicecalls(fixed,mobile,sta-candnomadicVoIP)inEUcountries.

•  Twomechanisms•  Push/PullRef:ECM/493Ref:ETSIES203178

52

M/493: Key technologies/protocols


•  SIP/RTP•  Specificreferenceto“IMScompa-bility”(AKAimplementa-onconsidera-ons)

•  Loca-onquerying/retrieval/update•  HELDorMLP

Ref:ETSIES203283 53

M/493: an alterna2ve NG112 architecture?

•  Originallyloca-ondetermina-on•  +Callrou-ng/PSAPdetermina-on?•  Iainterfaceoutofscope(anyVoIPtechnology)

•  Commoninterfaces•  “Theinterfacesia,ib,icandieareexternal,whichmeansbetweencountryAandanywhereand(withtheexcep-onofia)arespecifiedindetailtoensurethatallVSPsandVAPscanpar-cipateintheprocessesforemergencyservicecallerloca-ondetermina-onandtransportbasedonthearchitectureofETSIES203178[1]withincountryA.”

•  Na-onaldomain(framework)•  “Theinterfacesid,if,ig,ih,ii,ij,ik,il,imandinareinternal,insidecountryA,andshouldbespecifiedconsideringtheexis-ngna-onalimplementa-onsandregula-onsincountryA.Whenotherprotocolsareusedcareistobetakenthatallinforma-onelementsoutlinedinthearchitecturearecovered.”

54

ETSIES203178(architecture)

History of M/493

2000 2005 2010 2015 2020

55

ECMandateM/493

WIcrea#oninETSI

ETSIES203283protocols

M/493: Architecture

56

UE

LSDiscovery

ib

AccessNetworkProvider

ia

LS

ic

VoiceServiceProvider

VSPCallControl

EmergencyCallServiceProvider

LSproxy

ESRF

PSAPserviceProvider

IPPSAP

ESRP

RouteServer

if

PSTNPSAP

ig

id

im

il ij ii

ih ik

in

ie

CpuntryA

M/493 and NG112 interconnec2on example

57

UE

LSDiscovery

ib

AccessNetworkProvider

ia

LS

ic

VoiceServiceProvider

VSPCallControl

EmergencyCallServiceProvider

LSproxy

ESRF

PSAPserviceProvider

ESRP

RouteServer

ifig

id

imil

ij

ih

in

ie

CpuntryA

57 PSAPDOMAIN

ESRP

ECRF

PSAP-1

PSAP-2

PSAP-N

L/R

M/493resul-ngloca-on&rou-ngtoNa-onalPointofpresence

BCFIPPSAP

ij:interface“compa#ble”serviceurninR-URIóna#onalmaher

ESINET


58

Will M/493… • …replace …

•  Notlikely:itfocusonorigina-ngnetworksandna-onaldetails• …complement …

•  commercialoperatorbasedrou-ngtosinglePoP(BCF)andlaterPSAP-awarerou-ngintheESINET

•  Comprehensiveanalysisofthemappingbetweenarchitecturesshouldbecarriedout• …push …

•  Ifresul-ngarchitecturefromM/493istransposedtosomeEuropeandirec-ve=>harmoniza-onisalwaysgoodNOTE:na-onalmagerspecificallymen-oned

• …delay … •  Maybe,duetothe“possible”uncertaintyonresul-ngharmoniza-on,needforcoopera-onfromAccessNetworkproviders

…NG112?

CHAPTER PEMEA

6

PEMEA: Main characteris2cs

• AllowlocalizedmobileappstoroamacrossEurope• Drivenby(NG)112appsdevelopersinEENA• Dataexchangeandsecuritymodel

•  +Loca-on• Calling?

•  PEMEAwasintendedtoprovideasteppingstonetotheCoreelementfornetworkindependentaccesstoemergencyservicesTS103479NOTE:NG112

•  byreusingmanyofthesamedatastructureusedintheIETFand3GPPspecifica-onsaswellasTS103479.

•  Clauses8.2and8.3providedescrip-onsforacallisSIP-basedandtraversestheBorderControlFunc-on(BCF)toentertheESInet,andthelegacycasewherethecallenterstheESInetviaalegacynetworkgateway(LNG).Theinforma-oncontainedintheseclausesisinforma-veonly. 60

PEMEA: Key technologies/protocols

•  Signalling:•  NotspecificforVoiceCallingNOTEalignmentwithTS103473•  DataexchangeusingXMLoversecureHTTP

•  registry•  Loca-onquerying/retrieval/update=>pemea:informa-onType

•  HELDorMLP

•  Ppoutofscope(PSAPtoPSP)=>couldbeNG112• Media:

•  Codec/etc:•  Notmandatory

Ref:ETSIdradTS103478v.0.0.6 61

PEMEAarchitectureandrequirements

EENA

History of PEMEA

2000 2005 2010 2015 2020

62

112AppsstrategyEENA

PEMEAprotocolandproceduresEENA

PEMEAstandardiza#onac#vi#esinETSI

TS103478

PEMEA: Architecture

63

AppAplica#onProvider

Ref:PEMEAinanutshellEENAconference2017

Pa PSAPServiceProvider

PsPSAP

Pp

Aggrega#ngServiceProvider



PsPSAP

Pp

Pr

Pr

InscopeofPEMEA

PEMEA and NG112 interconnec2on example

64 64

ESRP

ECRF

PSAP-1

PSAP-2

PSAP-N

L/R

BCF

ESINET



Ps

PEMEANG112interworkingforemergencycallingLoca-onretrievaltestedin2ndNG112Plugtest

LIS/interface

NG112call+loc+caching

LIS


65

Will PEMEA… • …replace …

•  Notlikely:targe-ngdataexchangeforapps,callingcapabili-esopen• …complement …

•  Yes:bothas“enhancedinfoaddi-onalchannel”andinterconnec-onmechanismforapps“origina-ngnetworks”

• …push … • WilldependonNG112’sandPSAPs’evolu-onratherthanonPEMEA

• …delay … •  NA

…NG112?

CHAPTER (NG) eCALL

7

(NG) eCALL: Main characteris2cs

67

• DrivenbyEC,carsmanufacturers(ERTICO,ACEA)•  “Supported”byEENA

•  Setupvoicecall+sendMSDinthecaseofaccident• MandatoryfornewcarsfromMarch2018• NGeCALL

•  BasedonIMS•  Transi-onfromCStoNGecall

•  AllNGeCALLcarsmustsupportCSeCALL•  1sttryNGeCALL(basedonsupportindicator)and/orfallbacktoCSeCALL

eCALL: Key technologies/protocols

•  Tradi-onal:•  Signalling:

•  InBandMSD

•  (NG)eCALL

•  IMSemergencysignalling

Ref:CEN,ETSI 68

(NG) eCALL: Main characteris2cs

Ref:ETSISTF456report 69

•  ETSITR103140•  STF456

•  Whywedoit:•  eCallisbeingdeployedon2Gand3Gnetworksbutthesewillnotlastforever.Alreadythereare

4Gnetworks,andcoopera-veITSisonthehorizon.•  Howwedoit:

•  Wearemakingproposalsto3GPPtoshowhoweCallcouldbespecifiedfor4G.WeareconsideringhoweCallwouldmigrateto4GandITS,andinthisrespectwemakepresenta-onstoasmanyeCallstakeholderorganisa-onsaspossible(e.g.EeIP,HeERO,CENTC278,ETSITCITS,ISOTC204)togettheirviews.

•  RATIONALE•  InbandeCALLnotlonglas-ngsolu-onwhencomparedwithcarslife-me

(NG) eCALL: Key technologies/protocols

• BasedonIMSemergencycall• Rou-ngtoPSAPbasedonUniformResourceNames(URN)

•  urn:service:sos.ecall.manualformanualeCall•  urn:service:sos.ecall.automa-cforautoma-ceCall•  urn:service:test.sos.ecallfortesteCall

•  Ini-alMinimumSetofData(MSD)issentinSIPINVITEMSDisacknowledgedintheINVITEresponse

• AnewMSDcanberequestedbythePSAPusingSIPINFO

Ref:DavidWilliamQualcoommRef:RFC8147

70

ETSITR103140VoIPeCALL

History of (NG) eCALL

Ref:hgps://ec.europa.eu/digital-single-market/ecall--me-saved-lives-saved2000 2005 2010 2015 2020

Ini#alidea[Galileo]

Allnewcarsequippedwith

eCALL

EuropeanParlamentvotedinfavourofeCALL

regula#on

eCALLMoU

71

ECDelegatedregula#ononupda#ngPSAPs

Ref:eCALLFactsheetEENARef:HeEROproject

eCALLMSDstdbyCEN RFC8147

eCALLmodemstdsinETSI

HeEROprojectstarts

ETSISTF456

CircuitSwitched2G/3GNetwork

EMERGENCYIMSCORE

(NG)eCALL: Architecture

72

P-CSCF E-CSCF

S-CSCF

LRF

CARGm Mw

MI

Mw

Mm/Mx

Mw

VoIPEnabledPSAP

CAR LegacyPSAPInBandMODEM+MSD

Voiceto112


73

Will (NG) eCALL… • …replace …

•  Notlikely:Specificnichetechnology,maypushIMSemergencycalling• …complement …

•  commercialoperatorbasedrou-ngtosinglePoP(BCF)andlaterPSAP-awarerou-ngintheESINET

• …push … •  eCALLdirec-vepushingevolu-ontoIPcapablePSAPs•  GoodexampleofECmovingfromMoUtolegisla-on•  Supportofsosurnbutna-veIMS“transport”mechanism

• …delay … •  Notlikely:Specificnichetechnology

…NG112?

CHAPTER AML

8

AML: Main characteris2cs

75

• Drivenbyini-alini-a-veofBT(EE,O2,&HTC)inUK,greatlypushedbyGoogle(Android),supportedbyEENAandlaterextendedtoothercountries.

•  Standardiza-oneffortsini-ated(EMTEL/ETSI)•  ETSITR103393

• Automatedloca-onconveyancewhenaemergencycallisini-ated•  Silentac-va-onofdifferentloca-onmethods+•  “Outofband”SMS/HTTPsPUSHbasedsignalling

Ref:EENA’sworkonAMLRef:ADVANCEDMOBILELOCATION(AML)INTHEUK,EENARef:AMLFAQ,EENA

Source:BT

AML: Key technologies/protocols

•  SMSbased•  messageagributesseparatedbyasemicolon(;)•  Eachagributeconsistsofaname/valuepairwherenamesandvaluesareseparatedbyanequals(=)character

• HTTPsbased:•  Encapsula-ngthe“DataSMS”

76 Ref:AdvancedMobileLoca-on(AML)Specifica-ons&Requirements,EENA

History of AML

2000 2005 2010 2015 2020

77

Reportontrialresults

1stimplementa#onsonHTChandsets

inUKETSITRbyEMTEL

AMLrequirementdocumentEENA

AndroidincludesAML(ELS)inall>=ICSversions

CircuitSwitched2G/3GNetwork

AML: Architecture

78

AMLenabledPSAPAML

enabledUE

VoicePSAPTradi-onalvoicecallto112

SMSgateway

AMLserver

Op-on1:SMS

Op-on1:HTTPsPUSHoverIPconnec-on

AML: Current status

79

AML and NG112 interconnec2on example

80 80

ESRP

ECRF

PSAP-1

PSAP-2

PSAP-N

L/R

ESINET

AMLNG112interworkingforemergencycallingLoca-onretrievaltestedin2ndNG112Plugtest

LIS

2G/3G(CS)4G(PS)Network

AMLenabled

UE

Tradi-onalvoicecallto112

SMSgateway

AMLserver

Op-on1:SMS

Op-on1:HTTPsPUSHoverIPconnec-on

LNG

LIF

PIF NIFBCF

LNG


81

Will AML… • …replace …

•  No:loca-onconveyanceusingtradi-onalvoicecalls

• …complement … •  It’sastepforwardasmore-accurate-loca-onprovidingorigina-ngnetwork

• …push … •  Raisesawarenessontheneedtoenhancedemergencycommunica-ons

• …delay … •  MayreducetheurgefromPSAPstomovetotrulyall-(Vo)IP

…NG112?

CHAPTER WebRTC

9

WebRTC: Main characteris2cs

83

•  Easy/portable/plugin-freemechanismtobringmul-mediatowebapps/browsers•  Solvingcommonproblems

•  NATtraversal/Security/Mediaprocessing/Codec“harmoniza-on”/SIPcomplexity

•  DrivenbyOpenSourceimplementa-onsinbrowsers•  OpenSourceproject

•  Google,Mozilla,Opera,…•  Google

•  2010•  OpenSourceGIPs

•  2012•  Chrome

•  Standardiza-onefforts•  IETF•  W3C

•  AlmostP2P-capableandsignallingagnos-c•  SDPoffer/answers-llneeded

WebRTC: Key technologies/protocols

84

•  Signalling•  Implementa-onspecific(SDPexchange)•  Examples

•  SIP/XMPP/JSEP

• Media•  RTP/DTLS

• NAT•  ICE,STUN,TURN,RTP-over-TCP

• Codecs•  OPUS,G.711[G.722,iLBC,andiSAC]•  VP8,H264

Ref:hgps://webrtc.org/faq/Ref:RFC7874 Ref:RFC7875 Ref:RFC7742

History of WebRTC

2000 2005 2010 2015 2020

GoogleChromeadds

webRTC

WebRTC1.0W3CCandidaterecommenda#on

IETFGroupset

up

Firefox20addswebRTC

IETFrtcwebWG

RFC7875RFC7874

RFC7478[INF]

RFC7742

WebServer

WebRTC: Architecture

86

WebRTCclient

Source:WebRTCandEmergencyServices(EENADocument)

Browser

Script

APIWebRTCclient

Browser

Script

API

WebRTCAplica#on

HTTP(s),Websockets

HTTP(s),Websockets

DTLS-SRTP/STUN/ICE

SIGNALLING

MEDIA

WebRTC and emergency calling Op-on1:Na-veóper-webrtcapp-signallingneedstobeaddedtothePSAP

ExamplesinWebRTCandEmergencyServices(EENADocument)

Op-on2:webrtc-2-SIP/PSTN“breakout”gatewayExampleinNG112plugtest

WebRTC and NG112 interconnec2on example

88 88

ESRP

ECRF

PSAP-1

PSAP-2

PSAP-N

L/R

ESINET

WebRTCandNG112interworkingforemergencycallingtestedin2ndNG112Plugtest

LIS

IPAccess

WeB

WebRTC2SIPgateway

BCF

Op-on1:webRTCbasedcallee

WebPSAP

Op-on2:webRTCbasedPSAP

WebRTC2SIPgateway


89

Will WebRTC… • …replace …

•  Notlikelyintheshorttem:webRTCisaparadigmshidaffec-nganycommunica-ons,foreseenimpactwouldberelatedto“universalservice”

• …complement … •  DependonwebRTCpenetra-onandevolu-onof“tradi-onaltelcos”

• …push … •  Byallowingeasiest“built-in”accesstomediarichcommunica-ons

• …delay … •  NA

…NG112?

CHAPTER Others

10

PSTN shutdown

91

Source:hgps://www.mfcomm.co.uk/blog/bt-shut-pstn-isdn-networks-2025-business-ready/

Source:hgps://voipstudio.com/pstn-switch-off/


92

Will PSTN shutdown…

• …push … •  Probably,duetotheneedtobecome(Vo)IPbutwilldependonwhetherIMS/VoLTE/RCSismonopolizingalltheorigina-ngnetworks

…NG112?

CHAPTER MCPTT

11

MCPTT: Main characteris2cs

94

•  Drivenby3GPP•  NotpurelytelcosbutSA6,pushedbyHO/MoIfromdifferentcountries(UK,US,FR…)

•  Communica-onsamongfirstresponders•  Evolu-onfromnarrowbandPMRtobroadbandVoIPbasedMCservicesoverSIP/IMSoverLTE

•  IMScore“op-onal”buthighlyvisibleinsomeTSs•  LTEanchorsforPCC(MCPTT-5RxInterface)andMul-cast(eMBMSMB2-U/Cinterfaces)

•  StandardizedinRel’13•  MC-Voice(MCPTT)

• WouldnotonlycoverPublicSafetybutalsoextendabletoPublicTransport,u-li-es,…

•  Mari-me•  Railways(FRMCS)•  Other…“towardsMC-everything”

MCPTT: Key technologies/protocols

•  Signalling:•  SIP/SDP+RTP

•  Specificheaders=>problemswithSBCs•  +XMLencodedmul-partbodiestoconveyMCPTTspecificinforma-on(mcpg-info)

•  RTCP-appbasedFloorControlling•  XCAP(HTTP,IMSUt-like)•  CSCserversforOAM,AAA,GroupManagement,KeyexchangeandbinderstoLTE

•  OpenIDCoreConnect,Diameter,others…

• Media•  MCVoice:codecAMR-WB(mandatory),EVSop-onal•  MCVideo:H264AVC(mandatory),otherprofilesandH265(HEVC)op-onals•  MCData:specific(i.e.SDS)

•  Loca-on•  MCPTTspecificloca-onconveyance(vnd.3gpp.mcpg-loca-on-info+xml!=pidf-lo)

Ref:3GPPTS24379,TS26281,TS24282 95

History of MCPTT

Ref:hgp://www.3gpp.org/news-events/3gpp-news/1875-mc_services2000 2005 2010 2015 2020

96

R12

R13

R14“Complete”MCVoicestds.

EarlyMissionCri#calEnablers

EnhancementstoMCVMCDataMCVideo

R15

Addi#onsandenhancementstoMCV,MCDataand

MCVideoMari#me,FRMCs…

MCPTTUE

MCPTT-1

MCPTT: Architecture (Applica2on plane unicast- simplified)

SIPCORE/IMSB

SIPCORE/IMSA

EPSA EPSB

MCPTTUE

MCPTTServer

(Par#cip.)

MCPTT-1

MCPTTServer(controlling)

MCPTTServer

(Par#cip.)

MCPTT-3 MCPTT-3

MCPTT-5 MCPTT-5

Ref:TS24379


98

Will MCPTT… • …replace …

•  Not:targe-ngcommunica-onsamongfirstrespondersonly• …complement …

•  Yes,possibleinforma-ontraversalfromci-zenstofirstrespondersthroughthecontrolroom/dispatchermighttakeadvantageofcommonVoIPbasedframework(i.e.IMS)

• …push … •  Probably,dependingonjointna-onalac-vi-esNGPS/NG911(tobeanalyzedlater)capablena-onalnetworks

• …delay … • Willdependonwhetherbudgetalloca-onismovedfrompossibleNG112/NG911migra-onstoNGPSonesinhybridorganiza-ons

…NG112?

CHAPTER

12 (supra) national initiatives

Ongoing (supra)na2onal ini2a2ves

• MostlyPSdriven•  Butgoodsynergies

•  Interconnec-on•  Testbeds/evalua-ons

•  Examples•  Europe

•  UKESMCP•  Broadmap/Broadnet•  FR

•  US•  Firstnet

•  Korea•  Safenet

Common analysis • Doesitmakesensetosharecommontechnologyinsteadoflegacymul-technologyvoiceonlymatrixamong?

•  Ci-zens•  PSAPs•  FirstResponders•  Authori-es

ProbablyYESExample:Sharingdatafromci-zenstoFRsSource:NG911&Firstnet..byTheNa-onal911ProgramandNASNA

UK ESMCP •  Frontrunner

•  Pre-standard• Controlroomupgrade

•  Consideredas“enablingproject”•  Referencetoenhancedemergencycommunica-onfromci-zensnotexplicit

•  AML,ecall,999eye,NG112….

Source:Ref:hgp://www.wireless-mag.com/esn/RoundTables/40798/esn-round-table.aspx

US Firstnet & NG911

103

• NeedtoalignFirstnetandNG911underongoingdiscussion•  Inprinciplebudgetnotallocated

US Firstnet & NG911

104

Source:NG911&FirstnetTogetherBuildingthefutureofPublicSafetyCommunica-onsbyTheNa-onal911ProgramandNASNA

Broadmap/Broadnet •  EuropeanIni-a-ve(throughH2020fundedR&DprojectsandPCP)towardsoachievefutureevolu-onofEuropeanbroadbandapplica-onsandinteroperableradiocommunica-onsolu-ons

• 

Ref:Broadmapproject

Supplier B

Supplier C

Supplier D

Phase 1 Solution design

Phase 2 Prototype development

Phase 3 Original development of limited volume of first test products / services Supplier A

Supplier B

Supplier C

Supplier D

Supplier B

Phase 0 Requirements Solutions Transition Roadmapping

Applied R&D / Pre-commercial Procurement (PCP)

Phase 4 Deployment of commercial volumes of end-products Wide diffusion of newly developed solutions

Supplier D

Public Procurement of Innovative Solutions (PPI)

Supplier(s) A,B,C,D and/or X

Also normally multiple sourcing here to keep competition going

BROADMAPCo#ordina)on*and*Support*Ac)on*(CSA)*

2016% 2018% Circa%2020,2022% 2025%

2025*–*Commercially*Deployed*Interoperable*

Broadband*Applica)ons,*Services,*Networks,*Devices*

for*PPDR*

BROADMAP*will*inform*Horizon*2020’s*co#funded*procurement*

process*which*will*likely*use*the*PCP*and*PPI*instruments*of*

H2020*and/or*other*instruments*such*as*the*Interna)onal*

Security*Fund*(ISF).*The*diagram*below*illustrates*an*expecta)on*

of*)meframe.*BROADMAP*cons)tutes*Phase*0.*

*BROADWAY* BROADNET*

105

Broadmap/Broadnet • Objec-ves:

•  Tocollect,assessandvalidatethePPDR’swirelessbroadbandcommunica-onrequirements

•  Toestablishacoresetofspecifica-onstofulfiltherequirements•  Todefinetransi-onroadmapsforresearchandstandardisa-onforfutureevolu-onofEuropeaninteroperableradiocommunica-onsolu-ons,withinlegalprocurementconstraints

•  Topreparethegroundforaneweco-systemtocatalysenewapplica-ons,servicesandprocessesmakinguseofbroadbandcapabili-esforPublicSafetyandSecurity

Ref:Broadmapproject106

Broadmap/Broadnet •  FocusonPPDRonly

•  Gradualapproach

• Butintegra-onwithci-zens(i.e.NG112)ofapossibleEuropeanhighscaletestbedworthconsidering

Ref:Broadmapproject107

Conclusions • Publicsafety(supra)na-onalini-a-vesaregainingmomentumandmayresultinpossiblecoopera-onopportuni-es

• NeedtofosterawarenessonNG112withinthesenewplatormstoavoidreinven-ngthewheel

• ControlRoomsandradio-mul--technologygatewaysseemtobeintheneartermthecommoninterfacingmechanismsbetween(NG)112andotheremergencytechnologies

108

CHAPTER Conclusions

13

Would NG112 be “NG” networks friendly? •  Evolu-onofMVNOtechnology…

110


111


TowardsAll(Vo)IP,flat,uncoupled,IMSbased?

MoreNG112-readythanever!!!112

Conclusion 1: NG112 s2ll on shape

• MostofthetechnologiesontheNGemergencynewlandscapeanalysedareeitherfullyNG112compa-bleorcanbeintegratedeasilyasorigina-ngnetworks

•  SIP/RTP+pidf-lo+MSRPeverywhere•  SBCissuesshouldbeconsideredspecifically(i.e.withSBCvendors)

•  Therefore,NG112iss-llcapableofaccommoda-ngnewtechnologies• BeingIMSthemostseriousalterna-vethescopeandrequirementsares-lldifferentconsideringthestakeholdersinvolved

•  Althoughthebusinessdriversmightaffectthefuture•  AllTelcosmighteasilymovetoIMScoreintheshorttermbutcouldPSAPsaffordIMScoresjustforinternal(withinESINET)emergencycallrou-ng?

Conclusion 2: Need to raise awareness

•  Targetdifferentstakeholders•  NG112:PSAPcommunity(EENA)•  IMS:Telcos•  SIPconnect:VoIPindustry•  eCALL:carindustry+EC•  M/493:EC•  PEMEA:PSAPcommunityandappsdevelopers(EENA)•  AML:telco’s,OSmanufacturers

Conclusion 3: Sinergies

• NG112shouldbeincludedintheagendaoftheongoingnextgenera-onemergencynetworksandrelatedini-a-ves(i.e.SmartCi-es)inordertoavoidreinven-ngthewheel

• Harmoniza-onand“lessonslearned”fromAML(mobileOSside)andM/493andeCALL(fromharmoniza-ontoECmandate)s-llconsideredkeyenablersforNG112success

Recommendations

Stakeholders Ac#ons

MVNOs(individual+organiza-ons)Devcommunity

RaiseawarenessWhoisresponsibleforwhat?Externalvs.internalECrou-ngvs.ESINET

Exchangetechnicalinfo“Howto”

Newsuprana-onalPublicSafetyorganiza-ons/evalua-ontestbeds

Integra-onofNG112/NG-9-1-1Avoidreinven-ngthewheelHarmoniza-on/Regula-onini-a-ves

BigOSvendors LessonslearnedfromAML

SDOs+debateonneedsforstandards Keeppushingstandardiza-onefforts

•  AAA: Awareness, Awareness, Awareness + “Be water my friend”

116

TheEuropeanEmergencyNumberAssocia-on

> [email protected] Fidel Liberal

Questions/Comments to Cristina Lumbreras

[email protected]

Documents

NG112 and the new Emergency Services Networks landscape · 08-502 E9-1-1 Requirements Informaon Document 2004/07/23 08-501 ... • Driven by the PSAP community (users and industry)