BSI PD CEN/TS 17184:2018
$198.66
Intelligent transport systems. eSafety. eCall High level application Protocols (HLAP) using IMS packet switched networks
| Published By | Publication Date | Number of Pages |
| BSI | 2018 | 60 |
In respect of 112-eCall (pan-European eCall) (operating requirements defined in EN 16072), this document defines the high level application protocols, procedures and processes required to provide the eCall service via a packet switched wireless communications network using IMS (Internet protocol Multimedia System) and LTE/ 4G/E-UTRAN wireless access. NOTE 1 The objective of implementing the pan-European in-vehicle emergency call system (eCall) is to automate the notification of a traffic accident, wherever in Europe, with the same technical standards and the same quality of services objectives by using a PLMN (such as ETSI prime medium) which supports the European harmonized 112/E112 emergency number (TS12 ETSI TS 122 003 or IMS packet switched network) and to provide a means of manually triggering the notification of an emergency incident. NOTE 2 HLAP requirements for third party services supporting eCall can be found in EN 16102, and have been developed in conjunction with the development of this work item, and are consistent in respect of the interface to the PSAP. This document makes reference to those provisions but does not duplicate them.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 2 | undefined |
| 10 | 1 Scope 2 Normative references |
| 11 | 3 Terms and definitions |
| 16 | 4 Symbols and abbreviations |
| 18 | 5 Conformance 6 General overview of the eCall session for Pan European eCall |
| 24 | 7 Requirements 7.1 Procedures following power-up of the in-vehicle system 7.1.1 General 7.1.2 Enabled IVS |
| 25 | 7.1.3 Enabled PSAP |
| 26 | 7.1.4 IVS configured only for 112-eCall 7.1.5 Self-test 7.1.6 Standby mode applicable to IVS configured only for 112-eCall 7.2 Activation 7.2.1 Activation of pan-European IMS-eCall |
| 27 | 7.2.2 Activation of a test eCall 7.3 Call set-up 7.3.1 General 7.3.2 IVS network access device (NAD) already registered on PLMN 7.3.3 eCall in progress |
| 28 | 7.3.4 Network selection and registration 7.3.5 Authentication of the subscriber 7.3.6 IMS-eCall establishment |
| 29 | 7.3.7 Cell localization (by network) 7.3.8 Manual termination of eCall by vehicle occupants before trigger confirmation |
| 30 | 7.4 MSD transfer in IMS-eCall 7.4.1 General 7.4.2 MSD transfer to a PSAP supporting IMS-eCall |
| 32 | 7.4.3 MSD Transfer to a PSAP not supporting IMS-eCall |
| 33 | 7.4.4 Security 7.5 Application layer acknowledgement (AL- ACK) 7.6 In the event of IMS-eCall failure |
| 34 | 7.7 PSAP requests a new MSD 7.7.1 General |
| 35 | 7.7.2 After session clear-down 7.8 PSAP application features 7.8.1 General requirements |
| 36 | 7.8.2 MSD display to the PSAP operator 7.8.3 PSAP operator user interface 7.9 Audio link to vehicle occupants 7.10 eCall clear-down 7.11 PSAP call back |
| 37 | 7.12 Rerouting to another PSAP/emergency control centre 7.13 Handling non equipped situations / error cases 7.13.1 MSD not transmitted correctly 7.13.2 Network registration fails 7.13.3 Call failure before the MSD is acknowledged |
| 38 | 7.13.4 Mobile network not supporting eCall URN or not provided with routing tables 7.13.4.1 General 7.13.4.2 PSAP not equipped to support the IMS-eCall service 7.14 PSAP network/ICT failure 7.14.1 General 7.14.2 PSAP application failure 7.14.3 PSAP operator does not respond |
| 39 | 7.14.4 PSAP system not available 7.14.5 MSD corrupted 7.14.6 Audio link not established 7.14.7 Audio link established but subsequently fails |
| 40 | 7.14.8 Automatic repeat attempts 8 Third party services supported eCall (TPS-eCall) 9 Defences against attack (Security provisions) 10 Quality of service requirements 11 Test and conformance requirements 12 Marking, labelling and packaging 13 Declaration of patents and intellectual property |
| 41 | Annex A (normative)Table of timings |
| 43 | Annex B (informative)SIP and IMS explained B.1 Introduction B.2 Session Initiation Protocol B.2.1 SIP B.2.2 SIP URI B.2.3 SIP INVITE |
| 44 | B.2.4 Request-Line-URI B.2.5 Via B.2.6 From B.2.7 To B.2.8 Contact B.2.9 Allow |
| 45 | B.2.10 BYE B.2.11 CANCEL B.2.12 INFO B.2.13 INVITE B.2.14 NOTIFY B.2.15 OPTIONS B.2.16 PRACK |
| 46 | B.2.17 REFER B.2.18 REGISTER B.2.19 SUBSCRIBE B.2.20 UPDATE B.3 IMS: Internet Protocol (IP) multimedia core network subsystem B.3.1 IMS Overview |
| 49 | B.3.2 Roles of Session Control Functions B.3.2.1 Central session control function B.3.2.2 Proxy CSCF |
| 51 | B.4 Emergency Communications B.4.1 Overview of ETSI TS 123 167 B.4.2 High Level Procedures for IMS Emergency Services B.4.2.1 UE Detectable Emergency Session |
| 53 | B.4.2.2 Emergency Session Establishment using Local Retrieval Function (LRF)/Routing Determination Function (RDF) |
| 54 | B.4.2.3 Emergency Call Centre (ECS) redirecting IMS Emergency Call |
| 56 | B.4.2.4 Handling of location information B.4.2.5 Further detail and Information |
Related products
-
BSI PD CEN/TR 17868:2022
Intelligent transport systems. EU-ICIP. ITS standards deliverables (2022) Published By Publication Date Number of Pages…
