BS ISO 15638-10:2017
$198.66
Intelligent transport systems. Framework for cooperative telematics applications for regulated commercial freight vehicles (TARV) – Emergency messaging system/eCall
Published By | Publication Date | Number of Pages |
BSI | 2017 | 56 |
This document 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.
This document 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:
-
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)
-
Means to realise the service
-
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. This document 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.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | National foreword |
7 | Foreword |
8 | Introduction |
9 | 1 Scope 2 Normative references |
10 | 3 Terms and definitions |
15 | 4 Symbols and abbreviated terms |
16 | 5 Conformance 6 General overview and framework requirements 7 Requirements for services using generic vehicle data |
17 | 8 Application services that require data in addition to basic vehicle data 8.1 General 8.2 Quality of service requirements 8.3 Test requirements 8.4 Marking, labelling and packaging 9 Common features of regulated TARV application services 9.1 General |
18 | 9.2 Common role of the jurisdiction, approval authority, service provider and user. 9.3 Common characteristics for instantiations of regulated application services |
19 | 9.4 Common sequence of operations for regulated application services 9.5 Quality of service 9.6 Information security 9.7 Data naming content and quality 9.8 Software engineering quality systems 9.9 Quality monitoring station 9.10 Audits 9.11 Data access control policy 9.12 Approval of IVSs and service providers |
20 | 10 TARV emergency messaging/eCall system (EMS) 10.1 TARV EMS service description and scope 10.1.1 TARV EMS use case |
21 | 10.1.2 Description of TARV EMS regulated application service 10.1.3 Description of eCall regulated application service |
22 | 10.2 Concept of operations for TARV EMS 10.2.1 General 10.2.2 Statement of the goals and objectives of the TARV EMS 10.2.3 Strategies, tactics, policies, and constraints affecting the TARV EMS 10.2.4 Organisations, activities, and interactions among participants and stakeholders in TARV EMS |
23 | 10.2.5 Clear statement of responsibilities and authorities delegated for TARV EMS |
24 | 10.2.6 Operational processes for the TARV EMS 10.2.7 Role of TARV EMS service provider 10.2.8 Role of TARV EMS user |
25 | 10.3 Concept of operations for eCall via TARV 10.3.1 General concept of TARV eCall 10.3.2 Statement of the goals and objectives of the TARV eCall system |
26 | 10.3.3 Strategies, tactics, policies, and constraints affecting the TARV eCall system 10.3.4 Organisations, activities, and interactions among participants and stakeholders for TARV eCall 10.3.5 Clear statement of responsibilities and authorities delegated in TARV eCall 10.3.6 Operational processes for the TARV eCall system |
27 | 10.3.7 Role of service provider in TARV eCall 10.3.8 Role of user in TARV eCall 10.4 Sequence of operations for TARV eCall |
30 | 10.5 Sequence of operations for TARV EMS |
31 | 10.6 TARV EMS naming content and quality 10.7 Specific TARV EMS data naming content and quality 10.7.1 eCall Minimum set of data 10.7.2 HGV eCall dataset 10.7.3 Other TARV EMS emergency messages 10.8 TARV EMS service elements 10.8.1 TARV EMS SE1: TARV eCall 10.8.2 TARV EMS SE2: Establish ‘TARV Emergency Call’ (TARV EMS) jurisdiction regulations or system specification 10.8.3 TARV EMS SE3: Request system approval 10.8.4 TARV EMS SE4: User (operator) contracts with prime service provider 10.8.5 TARV EMS SE5: User (operator) equips vehicle with a means to provide consignment data |
32 | 10.8.6 TARV EMS SE6: User contracts with application service provider 10.8.7 TARV EMS SE7: Application service provider uploads software into the TARV equipped vehicles of the operator 10.8.8 TARV EMS SE8: Recording of vehicle consignment data 10.8.9 TARV EMS SE9: EMS trigger 10.8.10 TARV EMS SE10: Make TARV EMS emergency call |
33 | 10.8.11 TARV EMS SE11: Obtain/request consignment data 10.8.12 TARV EMS SE12: Contact emergency responder 10.8.13 TARV EMS SE13: Notification to operator (3.32) |
34 | 10.8.14 TARV EMS SE13: Emergency response 10.9 TARV EMS Emergency messaging access methods to provision and retrieve data 10.10 Contents of the ‘Minimum Set of Data’ (MSD) 10.10.1 Basic contents of MSD 10.10.2 Contents of the optionalAdditionalData for Schema A |
37 | 10.10.3 Contents of the optionalAdditionalData for Schema B |
39 | 10.11 TARV EMS application service specific provisions for quality of service 10.12 TARV EMS application service specific provisions for test requirements 10.13 TARV EMS application specific rules for the approval of IVSs and ‘Service Providers’ |
40 | 11 Declaration of patents and intellectual property |
41 | Annex A (informative) ASN.1 definition of optional datablock |
45 | Annex B (informative) ASN.1 definition of complete MSD message with HGV info |
53 | Bibliography |