ISO/TR 17427-3:2015
(Main)Intelligent transport systems — Cooperative ITS — Part 3: Concept of operations (ConOps) for 'core' systems
Intelligent transport systems — Cooperative ITS — Part 3: Concept of operations (ConOps) for 'core' systems
ISO/TR 17427-3:2015 provides the high-level generic requirements for the "Concept of operations" for a ?Core System' (CorSys) (3.10) to support C-ITS service delivery. It is intended as an input to the planning and development elaboration of core functions that will support the deployment of cooperative intelligent transport systems (C-ITS) in a connected vehicle-highway paradigm The objective of ISO/TR 17427-3:2015 is to raise awareness of and consideration of such issues and to give pointers, where appropriate, to standards existing that provide specifications for all or some of these aspects. This Technical Report does not provide specifications for solutions of these issues. ISO/TR 17427-3:2015 is agnostic in respect of technology and operates with whatever (and probably multiple) communications technologies and hardware technologies that can support its functionalities.
Systèmes intelligents de transport — Systèmes intelligents de transport coopératifs — Partie 3: Concept des opérations (ConOps) pour les systèmes 'principaux'
General Information
Relations
Standards Content (Sample)
TECHNICAL ISO/TR
REPORT 17427-3
First edition
2015-11-01
Intelligent transport systems —
Cooperative ITS —
Part 3:
Concept of operations (ConOps) for
‘core’ systems
Systèmes intelligents de transport — Systèmes intelligents de
transport coopératifs —
Partie 3: Concept des opérations (ConOps) pour les systèmes
‘principaux’
Reference number
ISO/TR 17427-3:2015(E)
©
ISO 2015
---------------------- Page: 1 ----------------------
ISO/TR 17427-3:2015(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2015, 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 2015 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/TR 17427-3:2015(E)
Contents Page
Foreword .vi
Introduction .viii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 4
5 Using this Technical Report. 5
6 Overview of the role of a ‘Core System’ in C-ITS . 5
6.1 What is a Concept of operations? . 5
6.2 What are the core functions? . 6
6.3 Functional subsystems . 6
6.4 Institutional context . 7
6.5 Specific service features characterizing C-ITS service provision . 8
6.6 C-ITS and communication technologies .10
6.6.1 General.10
6.6.2 VANETs, MANETs and ‘latency’ .10
6.6.3 Hybrid communications .13
6.6.4 Short and medium range communication .15
6.6.5 Long range communication .16
6.6.6 Wide area broadcast .16
6.6.7 Positioning services .16
6.6.8 Digital road map data .17
6.7 Actors involved in C-ITS service provision .17
6.8 C-ITS enabling data .20
6.9 Cooperative ITS applications and services .22
6.9.1 System of systems .23
6.10 C-ITS Privacy and anonymity .23
6.10.1 Privacy overview . . .23
6.10.2 Data messages and privacy .24
6.10.3 Security .25
6.10.4 Data management (including capture, storage and access) .25
7 ‘Core’ systems .26
7.1 Core system overview .26
7.1.1 General.26
7.1.2 Single core systems .27
7.1.3 Multiple core systems .27
7.1.4 Other ‘Central’ systems .27
7.1.5 Facilitate a platform for sharing of information and efficient use of resources .28
7.2 Justification for ‘Core Systems’ .28
7.2.1 Vision, drivers and objectives .28
7.2.2 Key strategic objectives for the deployment of core system support .29
7.2.3 Key technical objectives for the deployment of core system support.29
7.2.4 Principal elements of a core system .30
7.2.5 Proposed features of C-ITS core systems.31
7.2.6 Main mission of the ‘Core System’ .35
7.2.7 Scope of ‘Core System’ services .36
7.2.8 Exclusions from CorSys .36
7.2.9 Probe data storage.36
7.2.10 Roadside equipment (RSE) .37
7.2.11 External support systems (ESS) .37
7.2.12 Communications options .37
7.2.13 Authority/jurisdiction databases .38
© ISO 2015 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/TR 17427-3:2015(E)
7.2.14 Core system stakeholders .39
7.2.15 Core system communications .39
7.2.16 Applications .42
7.2.17 Core system interactions .42
7.2.18 Core system operational goals .43
7.3 ‘Core system’ overview of requirements .44
7.3.1 Definition of a requirement .44
7.3.2 ‘Core System’ requirements identification process .44
7.3.3 Functional components .49
7.4 Background, objectives and scope of a ‘Core System’ .50
7.5 Operational policies and constraints .51
7.5.1 Certification .51
7.5.2 Operations and maintenance .52
7.5.3 Security management .52
7.5.4 Data provision/ownership .52
7.5.5 System performance management .52
7.5.6 Flexibility .53
7.5.7 Core system characteristics and environment .53
7.5.8 Deployment configurations .54
7.5.9 Deployment footprint .54
7.5.10 Subsystems .57
7.5.11 Subsystem descriptions .57
7.6 Modes of operation .62
7.7 User types and other involved personnel .64
7.8 Operational scenarios .65
7.9 Vehicle-originated broadcast .66
7.10 Infrastructure-vehicle-unicast .69
7.11 Support environment .71
7.11.1 Subsystems .72
7.11.2 Personnel .72
7.11.3 Processes .72
7.12 Disadvantages and limitations .72
8 Example use cases .73
8.1 General .73
8.2 Example Use Case (1): User data exchange .74
8.3 Example Use Case (2): Certificate distribution .75
8.4 Example Use Case (3): Certificate revocation list distribution .75
8.5 Example Use Case (4): Misbehaviour action: Certificate revocation list addition .76
8.6 Example Use Case (5): Data subscription .77
8.7 Example Use Case (6): Remote services.78
8.8 Example Use Case (7): Core service status distribution .79
8.9 Example Use Case (8): ‘Core System’ operations .80
8.10 Example Use Case (9): System expansion .80
8.11 Example Use Case (10): Core discovery .81
8.12 Example Use Case (11): Service data backup .82
8.13 Example Use Case (12): Service takeover .82
9 Summary of impacts .83
9.1 Operational impacts .83
9.1.1 Policy .83
9.1.2 System management.84
9.1.3 System operation .85
9.1.4 Service receipt.85
9.2 Organizational impacts .87
9.2.1 Policy .87
9.2.2 System management.88
9.2.3 System operation .89
9.3 Impacts during the deployment phases .89
iv © ISO 2015 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/TR 17427-3:2015(E)
9.3.1 System management.90
9.4 Measuring the impacts .90
10 Cooperative vehicle and highway systems policy and institutional issues .91
11 Funding and governance .91
Bibliography .94
© ISO 2015 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/TR 17427-3:2015(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO’s adherence to the WTO principles in the Technical
Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information
The committee responsible for this document is ISO/TC 204, Intelligent transport systems.
ISO 17427 consists of the following parts under the general title, Intelligent transport systems —
Cooperative ITS:
— Part 2: Framework overview [Technical Report]
— Part 3: Concept of operations (ConOps) for ‘Core’ systems [Technical Report]
— Part 4: Minimum system requirements and behaviour for core systems [Technical Report]
— Part 6: Core systems risk assessment methodology [Technical Report]
— Part 7: Privacy aspects [Technical Report]
— Part 8: Liability aspects [Technical Report]
— Part 9: Compliance and enforcement aspects [Technical Report]
— Part 10: Driver distraction and information display [Technical Report]
The following parts are under preparation:
— Part 1: Roles and responsibilities in the context of co-operative ITS architectures(s)
— Part 5: Common approaches to security [Technical Report]
— Part 11: Compliance and enforcement aspects [Technical Report]
— Part 12: Release processes [Technical Report]
— Part 13: Use case test cases [Technical Report]
— Part 14: Maintenance requirements and processes [Technical Report]
vi © ISO 2015 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/TR 17427-3:2015(E)
This Technical Report provides an informative ‘Concept of operations for ore systems’ supporting
Cooperative intelligent transport systems (C-ITS). It is intended to be used alongside ISO 17427-1,
ISO/TR 17465-1 and other parts of ISO 17465, and ISO 21217. Detailed specifications for the application
context will be provided by other ISO, CEN and SAE deliverables, and communications specifications
will be provided by ISO, IEEE and ETSI.
© ISO 2015 – All rights reserved vii
---------------------- Page: 7 ----------------------
ISO/TR 17427-3:2015(E)
Introduction
Intelligent transport systems (ITS) are transport systems in which advanced information, communication,
sensor and control technologies, including the Internet, are applied to increase safety, sustainability,
efficiency, and comfort in the movement of people and goods.
A distinguishing feature of ‘ITS’ is its communication with outside entities.
Some ITSs operate autonomously, for example, ‘adaptive cruise control’ uses radar/lidar/and/or video
to characterize the behaviour of the vehicle in front and adjust its vehicle speed accordingly. Some ITSs
are informative, for example, ‘Variable Message Signs’ at the roadside, or transmitted into the vehicle,
provide information and advice to the driver. Some ITSs are semi-autonomous, in that they are largely
autonomous, but rely on ‘static’ or ‘broadcast’ data, for example, GNSS-based ‘SatNav’ systems operate
autonomously within a vehicle but are dependent on receiving data broadcast from satellites in order to
calculate the location of the vehicle.
Cooperative intelligent transport systems (C-ITS) are a group of ITS technologies where service provision
is enabled by, or enhanced by, the use of ‘live’, present situation related, dynamic data/information from
other entities of similar functionality [for example, from one vehicle to other vehicle(s)], and/or between
different elements of the transport network, including vehicles and infrastructure [for example, from the
vehicle to an infrastructure-managed system or from an infrastructure-managed system to vehicle(s)].
Effectively, these technologies enable vehicles to ‘talk’ to each other and to the infrastructure, and in
so doing will have significant potential to improve the safe, sustainable and efficient operation of the
transport network.
A distinguishing feature of ‘C-ITS’ is that data is used across application/service boundaries. This means
that data collected at one point and/or processed by one application becomes available to be re-used by
other applications, which may be operating in the same, or different physical entities.
The difference between any ‘ITS implementation’ and a ‘C-ITS implementation’ is that C-ITSs are
dependent on the interaction with other vehicles and/or the infrastructure, and the exchange
of dynamic data, to receive data to enable their function, or conversely to provide data to other
vehicles/infrastructure to enable their C-ITSs to function.
C-ITS as an entity, is therefore the functionality that enables such ‘cooperative’ and collaborative
exchange of data, and in some cases, collaborative control, or even decision making, that will enable
applications to provide their services to one or more actors (3.1).
ISO/TR 17465-1 provides a summary definition of C-ITS as a “subset paradigm of overall ITS that
communicates and shares information between ITS-stations to give advice or facilitate actions with
the objective of improving safety, sustainability, efficiency and comfort beyond the scope of stand-
alone systems”.
ISO 17427-1 will provide descriptions of the roles and responsibilities of actors involved in the provision
and use of C-ITS.
ISO/TR 17427-2 provides a framework overview which characterize the components of a Cooperative-
ITS (C-ITS), its context and relevance for ITS service provision, and provides references to Standards
deliverables where specific aspects of C-ITS are defined.
This Technical Report concerns the high-level generic requirements for the “Concept of operations” for
a ‘Core System’ (CorSys) (3.10) to support C-ITS in a connected vehicle-highway system paradigm. It is
agnostic in respect of technology and operates with whatever (and probably multiple) communications
technologies and hardware technologies that can support its functionalities.
The benefits of Intelligent Co-operative Systems (C-ITS) stem from the increased information that is
available from the vehicle and its environment and from other vehicles. The same set of information
can be used to extend the functionality of the in-vehicle safety systems and through vehicle-to-
viii © ISO 2015 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/TR 17427-3:2015(E)
infrastructure communications for more efficient traffic control and management. The benefits include
the following:
— improved safety;
— increased road network capacity;
— reduced congestion and pollution;
— shorter and more predictable journey times;
— improved traffic safety for all road users;
— lower vehicle operating costs;
— more efficient logistics;
— improved management and control of the road network (both urban and inter-urban);
— increased efficiency of the public transport systems;
— better and more efficient response to hazards, incidents and accidents.
(source: EC project CVIS)
It is important to understand that C-ITS is not an end in itself, but a combination of t
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.