BSI PD CEN/TS 17184:2022:2023 Edition
$198.66
Intelligent transport systems. eSafety. eCall High level application protocols (HLAP) using IP Multimedia Subsystem (IMS) over packet switched networks
Published By | Publication Date | Number of Pages |
BSI | 2023 | 56 |
In respect of 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 (IP Multimedia Subsystem) and wireless access (such as LTE, NR and their successors). This document assumes support of eCall using IMS over packet switched networks by an IVS and a PSAP and further assumes that all PLMNs available to an IVS at the time an eCall or test eCall is initiated are packet switched networks. Support of eCall where eCall using IMS over packet switched networks is not supported by an IVS or PSAP is out of the scope of this document. At some moment in time packet switched networks will be the only Public Land Mobile Networks (PLMN) available. However as long as GSM/UMTS PLMNs are available (Teleservice 12/TS12) ETSI TS 122 003 will remain operational. Both the use of such PLMNs and the logic behind choosing the appropriate network in a hybrid situation (where both packet-switched and circuit-switched networks are available) are out of scope of this document. 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,. This document makes reference to those provisions but does not duplicate them.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
8 | 1 Scope 2 Normative references |
10 | 3 Terms and definitions |
14 | 4 Symbols and abbreviations |
15 | 5 Conformance 6 General overview of pan European eCall session via Packet Switched networks 6.1 General principle |
16 | 6.2 eCall over Packet Switched networks 6.3 eCall using IMS over Packet Switched networks |
21 | 6.4 The hybrid situation |
22 | 7 Requirements 7.1 General requirements 7.1.1 General 7.1.2 Enabled IVS 7.1.3 Enabled PSAP 7.1.4 eCall-only IVS |
23 | 7.2 Procedures following power-up of the in-vehicle system 7.2.1 Self-test 7.2.2 Standby mode applicable to eCall-only IVS 7.3 Activation 7.3.1 Activation of eCall using IMS over packet switched networks |
24 | 7.3.2 Activation of a test eCall 7.4 Call set-up 7.4.1 General 7.4.2 eCall in progress |
25 | 7.4.3 Network selection and registration 7.4.3.1 General 7.4.3.2 IVS network access device (NAD) already registered on PLMN 7.4.3.3 eCall-only IVS 7.4.4 Authentication of the subscriber 7.4.5 Establishment of an eCall using IMS over packet switched networks |
26 | 7.4.6 Cell localization (by network) 7.4.7 Manual termination of eCall by vehicle occupants before trigger confirmation 7.4.8 Call failure 7.4.9 Security 7.5 MSD transfer for eCall using IMS over packet switched networks |
27 | 7.6 Application layer acknowledgement (AL-ACK) 7.6.1 General |
28 | 7.6.2 Successful receipt by the PSAP of the initial MSD 7.6.3 Unsuccessful receipt by the PSAP of initial MSD 7.6.4 No receipt of acknowledgement |
29 | 7.6.5 Other forms of acknowledgement 7.7 PSAP requests a new MSD 7.7.1 General 7.7.2 Before session clear-down |
30 | 7.7.3 After session clear-down 7.8 MSD transfer using in-band modem (optional) 7.9 Audio link to vehicle occupants 7.10 eCall clear-down |
31 | 7.11 PSAP call back 7.12 Rerouting to another PSAP/emergency control centre |
32 | 7.13 Handling non equipped situations / error cases 7.13.1 Network related issues 7.13.1.1 Network registration fails 7.13.1.2 The eCall using IMS over packet switched networks support indicator (ECL) 7.13.2 MSD related issues 7.13.2.1 MSD not transmitted correctly 7.13.2.2 MSD corrupted |
33 | 7.13.3 PSAP network/ICT failure 7.13.3.1 PSAP application failure 7.13.3.2 PSAP operator does not respond 7.13.3.3 PSAP system too busy |
34 | 7.13.4 Call related issues 7.13.4.1 Call failure before the MSD is acknowledged 7.13.4.2 Call dropped 7.13.4.3 Problems with the Audio link 8 Third party services supported eCall (TPS-eCall) |
35 | 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 |
36 | Annex A (normative)Table of timings |
38 | Annex B (informative)SIP and IMS explained B.1 Introduction B.2 Session Initiation Protocol (SIP) B.2.1 General B.2.2 SIP INVITE |
39 | B.2.3 SIP URI B.2.4 Request-Line-URI B.2.5 Via B.2.6 From B.2.7 To B.2.8 Contact |
40 | B.2.9 Allow B.2.10 ACK B.2.11 BYE B.2.12 CANCEL B.2.13 INFO B.2.14 INVITE B.2.15 NOTIFY |
41 | B.2.16 OPTIONS B.2.17 PRACK B.2.18 REFER B.2.19 REGISTER B.2.20 SUBSCRIBE B.2.21 UPDATE B.3 IMS: Internet Protocol (IP) multimedia core network subsystem B.3.1 IMS Overview |
45 | B.3.2 Roles of Session Control Functions B.3.2.1 Central session control function B.3.2.2 Proxy CSCF |
46 | B.4 Emergency Communications B.4.1 Overview of ETSI TS 123 167 |
47 | B.4.2 High Level Procedures for IMS Emergency Services B.4.2.1 UE Detectable Emergency Session |
48 | B.4.2.2 Emergency Session Establishment using Local Retrieval Function (LRF)/Routing Determination Function (RDF) |
49 | B.4.2.3 Emergency Call Service (ECS) redirecting IMS Emergency Call |
51 | B.4.2.4 Handling of location information B.4.2.5 Further detail and Information |