{"id":440104,"date":"2024-10-20T08:12:59","date_gmt":"2024-10-20T08:12:59","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-178702023\/"},"modified":"2024-10-26T15:21:59","modified_gmt":"2024-10-26T15:21:59","slug":"bs-en-178702023","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-178702023\/","title":{"rendered":"BS EN 17870:2023"},"content":{"rendered":"
This document defines an additional data concept that can be transferred as the \u2018optional additional data\u2019 part of an eCall MSD, as defined in EN 15722, that can be transferred from a vehicle to a PSAP in the event of a crash or emergency via an eCall communication session. The purpose of this document is to provide means to notify the PSAP of any limitations to the sending equipment that are endorsed by other standards, but not (immediately) apparent to the receiver. Lack of knowledge about these limitations can hamper the emergency process. This document describes an additional data concept which facilitates the inclusion of information about such limitations in a consistent and usable matter. This document can be seen as an addendum to EN 15722; it contains as little redundancy as possible. NOTE 1 The communications media protocols and methods for the transmission of the eCall message are not specified in this document. NOTE 2 Additional data concepts can also be transferred, and it is advised to register any such data concepts using a data registry as defined in EN ISO 24978 [1]. See www.esafetydata.com for an example.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
7<\/td>\n | 1 Scope 2 Normative references 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
8<\/td>\n | 4 Symbols and abbreviations 5 Conformance 6 Requirements 6.1 General 6.2 Concepts and formats 6.2.1 MSD data concepts <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | 6.2.2 Representation of MSD data concepts 6.2.3 Distribution of MSD data 6.2.4 Equipment limitations additional data-concept \u2018Object Identifier\u2019 6.2.5 Equipment limitations additional data concept \u2018data\u2019 6.3 Contents of the \u2018Minimum Set of Data\u2019 (MSD) 6.3.1 Context <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | 6.3.2 Basic contents of MSD 6.3.3 Contents of the optionalAdditionalData <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 6.4 Mode of operation <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | Annex A (normative)ASN.1 definition of additional data block A.1 General A.2 Definition of contents of optionalAdditionalData A.2.1 Context A.2.2 ASN.1 definition <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | A.2.3 Syntax check of ASN.1 definition A.2.4 Example <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | Annex B (informative)ASN.1 definition of complete MSD message with equipment limitations B.1 General B.2 ASN.1 definition of complete extended MSD message <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | B.3 Example <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Intelligent transport systems. eSafety. eCall additional data concept for equipment limitations<\/b><\/p>\n |