ETSI TR 102 197-2003 Services and Protocols for Advanced Networks (SPAN) Preliminary analysis of EMTEL and Local Emergency Service requirements for IP networks and Next Generation _1.pdf

1、 ETSI TR 102 197 V1.1.1 (2003-10)Technical Report Services and Protocols for Advanced Networks (SPAN);Preliminary analysis of EMTEL andLocal Emergency Service requirements forIP networks and Next Generation NetworksETSI ETSI TR 102 197 V1.1.1 (2003-10) 2 Reference DTR/SPAN-130318 Keywords analysis,

2、emergency ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present docu

3、ment can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispu

4、te, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ET

5、SI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: editoretsi.org Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to

6、reproduction in all media. European Telecommunications Standards Institute 2003. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of it

7、s Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TR 102 197 V1.1.1 (2003-10) 3 Contents Intellectual Property Rights4 Foreword.4 Introduction 4 1 Scope 5 2 References 5 3 Abbreviations .5 4 Enhanced emergency call

8、for assistance 6 4.1 Protocol interfaces6 4.1.1 Fixed line user.7 4.1.2 Mobile user .8 4.1.3 Data network user .9 4.1.3.1 Data based users9 4.1.3.2 Message data based users10 4.1.4 Alarm data users .10 4.2 Multiple PSAP and cross border protocol interfaces11 5 Disaster communications .12 5.1 Pre-dis

9、aster requirements .13 5.1.1 Unknown disasters13 5.1.2 Known disasters13 5.2 Immediate requirements .14 5.2.1 Citizen to authority .14 5.2.2 Authority to authority .14 5.2.3 Authority to citizen .14 5.3 Long term requirements .15 5.3.1 Citizen to authority .15 5.3.2 Authority to authority .15 5.3.3

10、Authority to citizen .15 6 Requirements on NGN/IP networks.15 7 Recommendations 16 History 18 ETSI ETSI TR 102 197 V1.1.1 (2003-10) 4 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essen

11、tial IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates

12、 are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ET

13、SI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI Technical Committee Services and Protocols for Advanced Networks (SPAN). Introduction The present document gives a preliminary analysis of the technica

14、l requirements for the support of EMTEL and localization service for Emergency and Priority services within the PSTN/ISDN/IP signalling transport services in Europe. When Emergency communications is talked about there is a great deal of confusion of what is meant by an emergency. The present documen

15、t separates the telecommunication requirements arising from disaster situations (natural (e.g. flood, earthquake), or manmade (e.g. terrorist attacks) from the emergency (e.g. those requiring police ambulance and fire brigade on an individual basis). The point at which an emergency situation becomes

16、 a disaster situation has been defined by the impact upon telecommunications networks. The present document has been separated into three main clauses. Clause 4 investigates the emergency calls scenarios where the service has been enhanced to include the location information of the caller. Clause 5

17、deals with a disaster scenario that has an adverse impact upon the network. Clause 6 outlines some of the requirements to support EMTEL on the next generation network (NGN) that is based upon IP technology. These clauses do have a relationship but the situation and therefore the requirements expecte

18、d of the networks are different. ETSI ETSI TR 102 197 V1.1.1 (2003-10) 5 1 Scope The present document gives a preliminary analysis of technical requirements for the support of EMTEL and location services for emergency and priority services within the PSTN/ISDN/IP signalling transport services in Eur

19、ope, to progress toward the enhancement signalling transport protocol standards documentation. 2 References For the purposes of this Technical Report (TR), the following references apply: 1 CGALIES: CGALIES Final Report V1.0. 2 LOCUS: Final Report D6. 3 ETSI TS 102 164: “Services and Protocols for A

20、dvanced Networks (SPAN); Emergency Location Protocols“. 4 WERT FINAL REPORT for the September 11, 2001 New York City World Trade Centre Terrorist Attack. 5 Project MESA; Service Specification Group Services and Applications; Statement of Requirements. 6 ETSI TIPHON STF 225 report. 7 ITU-T Workshop o

21、n Telecommunications for Disaster Relief, Geneva 17 - 19 February 2003; http:/www.itu.int/ITU-T/worksem/ets/index.html. 8 ETSI Workshop on Emergency Telecommunications, Sophia Antipolis 26 - -27 February 2002; http:/www.emtel.etsi.org/Workshop/workshop.htm. 9 ETSI SR 002 180: “Requirements for commu

22、nication of citizens with authorities/organizations in case of distress (emergency call handling)“. 3 Abbreviations For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project ATM Asynchronous Transfer Mode CGALIES Co-ordination Group on Acces

23、s to Location Information for Emergency Services CLI Calling Line Identity CPC Calling Party Category DECT Digital Enhanced Cordless Telecommunications EMTEL EMergency TELecommunications ETS Emergency Telecommunications Service EU European Union GMLC Gateway Mobile Location Centre GPS Global Positio

24、ning Satellite GSM Global System for Mobile communications GTS Global Telematics protocol System ISDN Integrated Services Digital Network ISUP ISDN User Part IP Internet Protocol LAN Local Area NetworkLIF Location Interoperability Forum LOCUS LOcation of Cellular Users for emergency Services MLP Mob

25、ile Location Protocol ETSI ETSI TR 102 197 V1.1.1 (2003-10) 6 NGN Next Generation Network PSTN Public Switched Telephone Network PSAP Public Safety Answering Points SCN Switched Circuit Network SMLC Serving Mobile Location Centre SMS Short Message Service SS7 Signalling System No 7 TDR Telecommunica

26、tions for Disaster Relief TETRA TErrestrial Trunked RAdio UMTS Universal Mobile Telecommunications System VoIP Voice over IP VPN Virtual Private Network WAN Wide Area Network WERT Wireless Emergency Response Team WLAN Wireless LAN 4 Enhanced emergency call for assistance The need for and means of im

27、proved telecommunication services for disaster relief communications and emergency call handling was debated in ITU and ETSI workshops 7, 8. The requirements for the Enhanced 112 (E112) service are contained in the CGALIES report 1 and in the LOCUS reports 2 which outline the regulatory and technica

28、l feasibility for the introduction of location information to the Public Service Answering Point PSAP. Thence this location information can then be passed on to the appropriate emergency service operator/dispatcher. A collection of various national requirements for the purpose of taking them into ac

29、count in the standardization work of ETSI is contained in draft ETSI SR 002 180 Requirements for communication of citizens with authorities/organizations in case of distress (emergency call handling) (for V0.2.0 2003-06) see 9 http:/docbox.etsi.org/ocg/OCG_EMTEL/EMTEL03_Jun2003_Sophia/ 4.1 Protocol

30、interfaces Figure 1 indicates how the location information of the caller is passed to the appropriate emergency service. The caller has been categorized into four basic types, a mobile user, a fixed line user, a data packet user, and an automatic alarm user. These protocol interfaces are marked thre

31、esanstwosansonesansfoursans. foursanscuspopen1telephonesolidcellularphonephone pcmedicalpolicefireDispatcheronesanstwosansthreesanseightsansfivesanssixsanssevensansninesansninesansninesansDispatcherDispatcherbelleightsansFigure 1: E112 Emergency service functional architecture ETSI ETSI TR 102 197 V

32、1.1.1 (2003-10) 7 It should be noted that the dotted line denotes a notional interface, as the PSAP may also be the dispatcher to the particular emergency service. They are separated here as they represent two separate functionalities. Interfaces fivesans, sixsans, and sevensans are not currently st

33、andardized. This could be an area that ETSI/EU would want to be standardized as this could be an impediment to cross border co-operation between emergency services (see clause 4.2). In national and cross-border cases all communications from the PSAP to a dispatcher or another PSAP will be priority c

34、alls in order to bypass network congestion, failure etc. It should also be noted that for the case where the PSAP and dispatcher are the same person then the national and cross border communications will be via the interface . Figure 1 shows location information being requested and delivered to the

35、database across interface g3784 for the case of mobile networks. Although it should be noted that this protocol may not be standardized it is currently out for vote within ETSI SPAN as TS 102 164 3. Figure 1 also shows that the location information is requested and delivered to the emergency dispatc

36、her, this scenario may not be valid for all implementations of emergency services. In some implementations the PSAP and dispatcher are one, in others they are separated as shown so that both the PSAP and the dispatchers have direct access to the location database. Whilst the PSAP is able to retrieve

37、 the emergency location in terms of a broad region the dispatchers is able to retrieve all available information about the exact emergency location. Nevertheless the dispatcher will receive the location information and send it to the appropriate emergency vehicle across interface ninesans by radio T

38、his interface ninesans is shown as being one interface and one protocol to all the emergency services whereas it should be noted that this may not be the case, as it may be possible that one service uses TETRA another uses GSM technology or a proprietary system. 4.1.1 Fixed line user This user inclu

39、des the normal telephony user that dials for emergency assistance using the pan European emergency number 112, or national specific emergency number. As well as the voice telephony service other data services such as SMS or telemetry, may be used to alert the PSAP (or are configured such that an ale

40、rt can be sent directly to the appropriate emergency service). The latter service may also include “panic button“ type services used by elderly and infirm persons at home using radio type technology. The main protocol deployed at interface twosans internationally for this service is ISUP and there a

41、re many national variants of this as well as other SS No7 (SS7) protocols. The location of the caller is derived from the CLI, which in the fixed network gives a very high probability that the emergency service is sent to the correct address/location. It should be noted that fixed networks start sup

42、porting SMS and that a short message includes the CLI. The CLI is used to interrogate a database from which the correct address/location of the network access point can be obtained. This database can be a centrally maintained and funded by all operators or each operator will run its own database. In

43、 the decentralized case the PSAP and dispatcher need to be aware of which CLI belongs to which operator, this needs to be maintained to cover the number portability service. A network identifier indicating the database to interrogate and provided in association with the emergency call could be advan

44、tageous for the decentralized scenario. The transaction g3784 between the fixed network and the database is not required because a database update is required infrequently at network access installation time or after number portability since the network access is fixed. The transactions 8 between th

45、e PSAP/dispatcher and the database are required. ETSI ETSI TR 102 197 V1.1.1 (2003-10) 8 4.1.2 Mobile user eightsans cellularphone Radio Access Network SMLC GMLC Core Ntwk PSAP eightsans Figure 2: Mobile users with location information functional architecture Figure 2 shows how for a GSM customer th

46、at dials for emergency assistance, using the pan European emergency number 112 or national specific emergency number, location information is made available to a database from where it can be retrieved by the PSAP/dispatcher. Today in most networks the CLI information is transported by means of sign

47、alling to the PSAP, the PSAP then can obtain the location information from the database using this CLI. The Serving Mobile Location Centre (SMLC) collects the estimated location information for this mobile. The location information is then passed to the Gateway Mobile Location Centre (GMLC) and the

48、GMLC is responsible for the interworking to the protocol eightsans and also performs other tasks such as authorization and privacy functionality. The CLI is used to interrogate a database from which the correct location of the mobile can be obtained. This database can be a centrally maintained and f

49、unded by all operators or each operator will run its own database. In the decentralized case the PSAP and dispatcher need to be aware of which CLI belongs to which operator, this needs to be maintained to cover the number portability service. A network identifier indicating the database to interrogate and provided in association with the emergency call could be advantageous for the decentralized scenario. Users of the next generation of mobile technologies, 3GPP UMTS should also be included in this category of caller. UMTS emergency calls wi