ISO 15638-10:2017
(Main)Intelligent transport systems — Framework for cooperative telematics applications for regulated commercial freight vehicles (TARV) — Part 10: Emergency messaging system/eCall
Intelligent transport systems — Framework for cooperative telematics applications for regulated commercial freight vehicles (TARV) — Part 10: Emergency messaging system/eCall
ISO 15638-10:2017 addresses the provision of ?Emergency messaging system/eCall' using the TARV framework, architecture and communications methodology (as defined in ISO 15638‑1 to 6) and specifies the form and content of such data required to support such systems, and access methods (3.1) to that data. ISO 15638-10:2017 provides specifications (3.40) for common communications and data exchange aspects of the application service (3.3) ?Emergency Messaging System/eCall' that a regulator (3.28) may elect to require or support as an option, including: a) High level definition of the service that a service provider (3.38) has to provide, (The service definition describes common service elements; but does not define the detail of how such an application service (3.3) is instantiated, not the acceptable value ranges of the data concepts defined) b) Means to realise the service c) Application data, naming content and quality that an IVS (3.23) has to deliver. The definition of what comprises a ?regulated' service is regarded as an issue for National decision, and may vary from jurisdiction (3.27) to jurisdiction. ISO 15638-10:2017 does not impose any requirements on nations in respect of which services for regulated commercial freight vehicles jurisdictions will require, or support as an option, but provides standardised sets of requirements descriptions for identified services to enable consistent and cost efficient implementations where instantiated. The ISO 15638 suite of standards has been developed for use in the context of regulated commercial freight vehicles [hereinafter referred to as regulated vehicles (3.36)]. There is nothing however to prevent a jurisdiction extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.
Systèmes intelligents de transport — Cadre pour applications télématiques coopératives pour véhicules de fret commercial réglementé (TARV) — Partie 10: Système de messagerie d'urgence/appel électronique
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 15638-10
First edition
2017-06
Intelligent transport systems —
Framework for cooperative telematics
applications for regulated commercial
freight vehicles (TARV) —
Part 10:
Emergency messaging system/eCall
Systèmes intelligents de transport — Cadre pour applications
télématiques coopératives pour véhicules de fret commercial
réglementé (TARV) —
Partie 10: Système de messagerie d’urgence/appel électronique
Reference number
©
ISO 2017
© ISO 2017, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2017 – All rights reserved
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Symbols and abbreviated terms . 7
5 Conformance . 8
6 General overview and framework requirements . 8
7 Requirements for services using generic vehicle data . 8
8 Application services that require data in addition to basic vehicle data .9
8.1 General . 9
8.2 Quality of service requirements . 9
8.3 Test requirements . 9
8.4 Marking, labelling and packaging . 9
9 Common features of regulated TARV application services . 9
9.1 General . 9
9.2 Common role of the jurisdiction, approval authority, service provider and user. .10
9.3 Common characteristics for instantiations of regulated application services .10
9.4 Common sequence of operations for regulated application services .11
9.5 Quality of service .11
9.6 Information security .11
9.7 Data naming content and quality .11
9.8 Software engineering quality systems .11
9.9 Quality monitoring station .11
9.10 Audits .11
9.11 Data access control policy .11
9.12 Approval of IVSs and service providers .11
10 TARV emergency messaging/eCall system (EMS).12
10.1 TARV EMS service description and scope .12
10.1.1 TARV EMS use case .12
10.1.2 Description of TARV EMS regulated application service .13
10.1.3 Description of eCall regulated application service .13
10.2 Concept of operations for TARV EMS .14
10.2.1 General.14
10.2.2 Statement of the goals and objectives of the TARV EMS .14
10.2.3 Strategies, tactics, policies, and constraints affecting the TARV EMS .14
10.2.4 Organisations, activities, and interactions among participants and
stakeholders in TARV EMS .14
10.2.5 Clear statement of responsibilities and authorities delegated for TARV EMS .15
10.2.6 Operational processes for the TARV EMS .16
10.2.7 Role of TARV EMS service provider .16
10.2.8 Role of TARV EMS user .16
10.3 Concept of operations for eCall via TARV .17
10.3.1 General concept of TARV eCall .17
10.3.2 Statement of the goals and objectives of the TARV eCall system .17
10.3.3 Strategies, tactics, policies, and constraints affecting the TARV eCall system .18
10.3.4 Organisations, activities, and interactions among participants and
stakeholders for TARV eCall .18
10.3.5 Clear statement of responsibilities and authorities delegated in TARV eCall .18
10.3.6 Operational processes for the TARV eCall system .18
10.3.7 Role of service provider in TARV eCall .19
10.3.8 Role of user in TARV eCall .19
10.4 Sequence of operations for TARV eCall .19
10.5 Sequence of operations for TARV EMS .22
10.6 TARV EMS naming content and quality .23
10.7 Specific TARV EMS data naming content and quality .23
10.7.1 eCall Minimum set of data .23
10.7.2 HGV eCall dataset .23
10.7.3 Other TARV EMS emergency messages .23
10.8 TARV EMS service elements .23
10.8.1 TARV EMS SE1: TARV eCall .23
10.8.2 TARV EMS SE2: Establish ‘TARV Emergency Call’ (TARV EMS) jurisdiction
regulations or system specification .23
10.8.3 TARV EMS SE3: Request system approval.23
10.8.4 TARV EMS SE4: User (operator) contracts with prime service provider .23
10.8.5 TARV EMS SE5: User (operator) equips vehicle with a means to provide
consignment data .23
10.8.6 TARV EMS SE6: User contracts with application service provider .24
10.8.7 TARV EMS SE7: Application service provider uploads software into the
TARV equipped vehicles of the operator .24
10.8.8 TARV EMS SE8: Recording of vehicle consignment data .24
10.8.9 TARV EMS SE9: EMS trigger .24
10.8.10 TARV EMS SE10: Make TARV EMS emergency call .24
10.8.11 TARV EMS SE11: Obtain/request consignment data .25
10.8.12 TARV EMS SE12: Contact emergency responder .25
10.8.13 TARV EMS SE13: Notification to operator (3.32) .25
10.8.14 TARV EMS SE13: Emergency response .26
10.9 TARV EMS Emergency messaging access methods to provision and retrieve data .26
10.10 Contents of the ‘Minimum Set of Data’ (MSD) .26
10.10.1 Basic contents of MSD .26
10.10.2 Contents of the optionalAdditionalData for Schema A .26
10.10.3 Contents of the optionalAdditionalData for Schema B .29
10.11 TARV EMS application service specific provisions for quality of service .31
10.12 TARV EMS application service specific provisions for test requirements .31
10.13 TARV EMS application specific rules for the approval of IVSs and ‘Service Providers’ .31
11 Declaration of patents and intellectual property .32
Annex A (informative) ASN.1 definition of optional datablock .33
Annex B (informative) ASN.1 definition of complete MSD message with HGV info .37
Bibliography .
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.