ISO/TS 17427:2014

Intelligent transport systems - Cooperative systems - Roles and responsibilities in the context of cooperative ITS based on architecture(s) for cooperative systems

ISO/TS 17427:2014 describes the (actor invariant) roles and responsibilities required to deploy and operate Cooperative-ITS (C-ITS). The organizational architecture described in this document is to be used for a fully operational system. ISO/TS 17427:2014 is couched in terms of an organizational or enterprise viewpoint, as defined in ISO/IEC 10746 Open Distributed Processing. ISO/TS 17427:2014 is applicable to all types of road traffic of all classes. The description of roles is completely technology agnostic and, in terms of C-ITS communication modes, embraces vehicle-vehicle communications, vehicle-infrastructure communications and infrastructure-infrastructure communications. ISO/TS 17427:2014 provides a methodology for the identification of service specific roles and their corresponding responsibilities based on a process oriented approach. Additionally, the defined methodology is used to identify the roles and responsibilities for C-ITS, in general. Both the methodology, as well as, the roles and responsibilities for C-ITS are deduced from the reference model: Open Distributed Processing (ISO/IEC 10746). Open Distributed Processing offers five viewpoints of which the enterprise viewpoint corresponds with the organizational architecture and the roles and responsibilities. ISO/TS 17427:2014 separates C-ITS roles into 'external' and 'internal'. Those considered to be internal are all roles set up for the sole purpose of C-ITS and those considered to be external are all roles involved in C-ITS but not set up for the sole purpose of C-ITS. ISO/TS 17427:2014 describes high-level architectural viewpoint on C-ITS. It can be used as a blueprint when implementing C-ITS and the corresponding organizational structures. The characteristics of C-ITS entail a huge number of data/information exchanges. Therefore, the implementation of the organizational architecture stringently needs to respect privacy and data protection, as defined in ISO/TR 12859 and in the national laws and regulations (where instantiated). Privacy and data protection affect all roles defined in this Technical Specification and due to these characteristics, all actors occupying roles in C-ITS need to respect the corresponding standards and regulations.

Systèmes intelligents de transport — Systèmes coopératifs — Rôles et responsabilités dans le contexte des ITS fondés sur l'architecture de systèmes coopératifs

General Information

• Status: Withdrawn
• Publication Date: 03-Jul-2014
• Withdrawal Date: 03-Jul-2014
• ICS: 03.220.01 - Transport in general
• ICS: 35.240.60 - IT applications in transport
• Technical Committee: ISO/TC 204 - Intelligent transport systems
• Drafting Committee: ISO/TC 204/WG 18 - Cooperative systems
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 15-Jun-2018
• Completion Date: 13-Dec-2025

Relations

• Revised: ISO 17427-1:2018 - Intelligent transport systems - Cooperative ITS - Part 1: Roles and responsibilities in the context of co-operative ITS architecture(s)
• Effective Date: 05-Nov-2015

Standards Content (Sample)

TECHNICAL ISO/TS
SPECIFICATION 17427
First edition
2014-07-01
Intelligent transport systems —
Cooperative systems — Roles and
responsibilities in the context
of cooperative ITS based on
architecture(s) for cooperative
systems
Systèmes intelligents de transport — Systèmes coopératifs — Rôles et
responsabilités dans le contexte des ITS fondés sur l’architecture de
systèmes coopératifs
Reference number
©
ISO 2014
© ISO 2014
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
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland
ii © ISO 2014 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Symbols (and abbreviated terms) . 5
5 Introduction and theoretical framework. 5
5.1 Transferring ODP to roles and responsibilities for C-ITS . 5
5.2 External Enterprise Objects . 6
6 Roles and responsibilities . 8
6.1 Introduction . 8
6.2 General responsibilities of actors involved in C-ITS . 9
6.3 Role: System operation .10
6.4 Role: Using the service .12
6.5 Role: System management .12
6.6 Role: Policy framework .14
6.7 Profiles .15
7 Compliance .15
Annex A (informative) Methodology and its sample application .16
Annex B (informative) Profiles .29
Bibliography .45
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.
iv © ISO 2014 – All rights reserved

Introduction
Cooperative-ITS (C-ITS) are a promising and remarkable advancement of Intelligent Transport Systems
(ITS). Numerous cooperative applications are specified that open up new possibilities to make traffic
safer, more efficient and smarter. Technologies are developed and improved to realize and support those
new services and applications. But, to finally implement C-ITS and to achieve the benefits of more safety
and better mobility, various actors from different industries will have to cooperate with each other in a
completely new way. Actors that did not collaborate so far will have to find a way to do so. This requires
a precise definition and assignment of behaviours, responsibilities and liabilities. Therefore a general,
abstract organizational architecture with the description of the single roles, their behaviour and the
corresponding responsibilities is the essential basis for the deployment of C-ITS.
The organizational architecture itself with the description of the roles and responsibilities is a crucial
part of the whole C-ITS architecture. The organizational architectural viewpoint has extensive influences
on the deployment and implementation of C-ITS.
This document describes the high level roles and responsibilities that enable C-ITS Service provision.
TECHNICAL SPECIFICATION ISO/TS 17427:2014(E)
Intelligent transport systems — Cooperative systems —
Roles and responsibilities in the context of cooperative ITS
based on architecture(s) for cooperative systems
1 Scope
This Technical Specification describes the (non-actor specific) roles and responsibilities required
to deploy and operate Cooperative-ITS (C-ITS). The organizational architecture described in this
document is to be used for a fully operational system. The Technical Specification is couched in terms of
[1]
an organizational or enterprise viewpoint, as defined in ISO/IEC 10746 Open Distributed Processing.
This Technical Specification is applicable to all types of road traffic of all classes. The description of
roles is completely technology agnostic and, in terms of C-ITS communication modes, embraces vehicle-
vehicle communications, vehicle-infrastructure communications and infrastructure-infrastructure
communications.
This Technical Specification provides a methodology for the identification of service specific roles
and their corresponding responsibilities based on a process oriented approach. Additionally, the
defined methodology is used to identify the roles and responsibilities for C-ITS, in general. Both the
methodology, as well as, the roles and responsibilities for C-ITS are deduced from the reference model:
[1]
Open Distributed Processing (ISO/IEC 10746). Open Distributed Processing offers five viewpoints
of which the enterprise viewpoint corresponds with the organizational architecture and the roles and
responsibilities.
This Technical Specification separates C-ITS roles into ‘external’ and ‘internal’. Those considered to be
internal are all roles set up for the sole purpose of C-ITS and those considered to be external are all roles
involved in C-ITS but not set up for the sole purpose of C-ITS.
This Technical Specification describes high-level architectural viewpoint on C-ITS. It can be used as a
blueprint when implementing C-ITS and the corresponding organizational structures. The characteristics
of C-ITS entail a huge number of data/information exchanges. Therefore, the implementation of the
organizational architecture stringently needs to respect privacy and data protection, as defined
in ISO/TR 12859 and in the national laws and regulations (where instantiated). Privacy and data
protection affect all roles defined in this Technical Specification and due to these characteristics, all
actors occupying roles in C-ITS need to respect the corresponding standards and regulations.
2 Normative references
The following referenced documents, in whole or in part, are normatively referenced in this document
and are indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 10746:1996, Information technology — Open Distributed Processing — Reference model
ISO 14817:2002, Transport information and control systems — Requirements for an ITS/TICS central Data
Registry and ITS/TICS Data Dictionaries
ISO/TS 17419, Intelligent transport systems — Co-operative systems — Classification and management of
ITS applications in a global context”
ISO/TS 17931, Intelligent transport systems — Extension of map database specifications for Local Dynamic
Map for applications of Cooperative ITS
ISO/IEC 19501:2005, Information technology — Open Distributed Processing — Unified Modeling Language
(UML) Version 1.4.2
ISO 21217:2013, Intelligent transport systems — Communications access for land mobiles (CALM) —
Architecture
ETSI/TS 102-637:2011, Intelligent Transport Systems (ITS); Vehicular Communications Basic Set of
Applications
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply
3.1
action
something which happens
[SOURCE: ISO/IEC 10746-2, see Bibliography reference 2]
3.2
actor
user playing a coherent set of roles when interacting with the system within a particular use case
[SOURCE: ISO 24014-1:2007, see Bibliography reference 6]
3.3
application
mechanism of delivering some or all parts of an ITS service (3.23)
[SOURCE: ISO/TR 17465-1, see Bibliography reference 18]
3.4
behaviour
collection of actions (3.1) with a set of constraints on when they may occur
[SOURCE: ISO/IEC 10746-2, see Bibliography reference 2]
3.5
community
configuration of objects (3.13) formed to meet an objective
[SOURCE: ISO/IEC 10746-3, see Bibliography reference 3]
3.6
cooperative-ITS
C-ITS
DEPRECATED: cooperative systems
subset 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
Note 1 to entry: As an alternative to a “subset”, cooperative-ITS could be viewed as a “paradigm” in overall ITS.
[SOURCE: ISO/TR 17465-1, see Bibliography reference 18]
3.7
enterprise object
object (3.13) in enterprise viewpoint (3.10)
2 © ISO 2014 – All rights reserved

3.8
external enterprise object
enterprise object (3.7) involved in C-ITS but not set up for the only purpose of C-ITS
[SOURCE: ISO/TS 17574:2009, see Bibliography reference 4]
3.9
internal enterprise object
complementary to external enterprise object (3.8)
3.10
enterprise viewpoint
a viewpoint on an ODP system and its environment that focuses on the purpose, scope and policies for
that system
[SOURCE: ISO/IEC 10746-3, see Bibliography reference 3]
3.11
infrastructure
system of facilities, equipment and ITS services (3.23) that is needed for the operation of an organization
Note 1 to entry: Specifically in the case of C-ITS the most stationary part of C-ITS incorporating sensors, actuators,
static ITS Station(s) (3.12).
[SOURCE: ISO 9000:2005, see Bibliography reference 7]
3.12
ITS station
entity in a communication network capable of communicating with other similar entities
Note 1 to entry: From an abstract point of view, the term “ITS station” refers to a set of functionalities. The
term is often used to refer to an instantiation of these functionalities in a physical unit. Often the appropriate
interpretation is obvious from the context. The proper name of physical instantiation of an ITS-S is ITS station
unit (ITS-SU).
[SOURCE: ISO 21217:2010, see Bibliography reference 10]
3.13
object
model of an entity
Note 1 to entry: An object is characterized by its behaviour (3.4) and dually by its state. An object is distinct from
any other object. An object is encapsulated, i.e. any change in its state can only occur as a result of an internal
action (3.1) or as a result of an interaction with its environment.
[SOURCE: ISO/IEC 10746-2, see Bibliography reference 2]
3.14
process
process that describes a sequence of actions (3.1)
Note 1 to entry: A process can also be a set of interrelated or interacting activates which transform inputs into
[8]
outputs.
[SOURCE: ISO 9000:2005, see Bibliography reference 7]
3.15
process chain
sequence of processes (3.14) that wait in the background for an event
Note 1 to entry: Some of these processes (3.14) trigger a separate event that can start other processes (3.14) in turn
[SOURCE: SAP Help Portal, see Bibliography reference 9]
3.16
sequential process
process (3.14) based on sequence of actions (3.1) executed
3.17
(data) lifecycle process
process (3.14) based on data element transformation
3.18
responsibility
being accountable or answerable, as for an entity, function, system, security service or obligation
EXAMPLE A responsibility might be a legally backed assignment of actions (3.1) to a role (3.20).
[SOURCE: ISO/TS 17574:2009, see Bibliography reference 4]
3.19
roadside unit
implementation of roadside ITS Station (3.12) combined with other roadside equipment
EXAMPLE Sensors, actuator.
3.20
role
identifies a behaviour (3.4) to be associated with one of the component objects
[SOURCE: ISO/IEC 10746-2, see Bibliography reference 2]
3.21
sub-role
subordinate role (3.20) consisting of a defined fragment of the superior role (3.20)
3.22
scenario
general description of activities between (possible) participating actors (3.2)
3.23
ITS service
functionality provided to users of intelligent transport systems designed to increase safety, sustainability,
efficiency, and/or comfort
Note 1 to entry: This definition also appears in the latest version of ISO 21217.
3.24
ITS service in push mode
ITS service (3.23) operating on data delivered without request by an actor or its system
3.25
service in pull mode
ITS service (3.23) actively requesting the data that is required for the service operation
3.26
stakeholder
individual or organization having a right, share, claim or interest in a system or in its possession of
characteristics that meet their needs and expectations
[SOURCE: ISO/IEC 12207:2008, see Bibliography reference 5]
4 © ISO 2014 – All rights reserved

4 Symbols (and abbreviated terms)
C-ITS Cooperative ITS
GNSS Global Navigation Satellite System
HMI Human Machine Interface
ITS Intelligent Transport Systems
LDM Local Dynamic Map
PKI Public Key Infrastructure
ODP Open Distributed Processing
5 Introduction and theoretical framework
5.1 Transferring ODP to roles and responsibilities for C-ITS
Cooperative-ITS (C-ITS) features the characteristics of a distributed system with its partition onto
multiple ITS stations (3.12). Hence methodologies for the description of distributed systems are consulted
when describing the overall architecture of C-ITS and its different viewpoints. For the description
of the organisational architecture as one of the viewpoints of C-ITS, the concept of Open Distributed
[1] [2] [3]
Processing , , is applied. The organisational architecture corresponds with the enterprise viewpoint
(3.10) in ODP, defining the “purpose, scope and policies governing the activities of the specified system
within the organization of which it is part”. Conveyed to C-ITS, this Technical Specification is part of the
organizational architecture for C-ITS and focuses on the description of C-ITS specific roles (3.20) and
responsibilities (3.18).
Following the concept and terminology of ODP for the description of the roles (3.20) and responsibilities
(3.18), C-ITS can be described as a community (3.5) composed of external and internal enterprise objects
(3.8, 3.9) (see Figure 1) with the objective of providing C-ITS with its benefits regarding traffic safety,
traffic efficiency, comfort and ecologic mobility to the user. External enterprise objects (3.8) are involved
in C-ITS but are not set up for the sole purpose of C-ITS. Therefore this document limits itself to the
identification of roles and responsibilities of external enterprise objects (3.8).
Figure 1 — Relationship between Community, Internal and External Enterprise Objects and
Roles
5.2 External Enterprise Objects
C-ITS, as internal enterprise object (3.9), is connected with various external enterprise objects (3.8). The
diagram (Figure 2) illustrates the external enterprise objects (3.8) and their interfaces to the internal
enterprise object (3.9). Figure 2 shall illustrate the variety of parties (external enterprise objects) involved
in C-ITS. The external enterprise objects (3.8) comprise examples from different levels.
6 © ISO 2014 – All rights reserved

Figure 2 — External and Internal Enterprise Objects in a C-ITS Community
From the enterprise objects (3.5) displayed in Figure 2, the following are closely connected with C-ITS
and rather have an external-internal status:
— Telecommunication systems;
— Certification;
— Standardization bodies;
— Authorities.
Criteria for the categorization of “external-internal” is that the external enterprise objects (3.8) are deeply
involved in C-ITS and partially exhibit C-ITS specific roles (3.20). More details are given in Clause 6. The
standard functionalities that external enterprise objects (3.8) provide are documented in the respective
standards referenced in Clause 6.
Additionally, as shown in Figure 2, C-ITS has interfaces with other ITS systems. These are not explicitly
denominated in this Technical Specification.
5.2.1 Internal Enterprise Objects
C-ITS, as internal enterprise object (3.9), consists of a set of specific roles (3.20) that are identified and
described in the subsequent Clauses. The methodology that describes how these roles and responsibilities
originally were identified and verified can be found in Annex A.
6 Roles and responsibilities
6.1 Introduction
All roles (3.20) and the corresponding responsibilities (3.18) identified through use of the methodology
described in Annex A are described in the following subclauses.
6.1.1 Generic description of organizational architecture
In the generic view of the organizational architecture four major roles (3.20) were identified (Figure 3):
Figure 3 — Global description of Organisational Architecture
6.1.2 System operation
The role (3.20) “‘System operation” is responsible for the proper execution of the applications (3.3) that
provide an end-to-end ITS service(s) (3.23). This includes reliability for the coordination, organization
and execution of the whole process (3.14) from initial data collection to the presentation of the final
service result. One of the major interfaces of this role (3.20) is with the actor(s) (3.2) of the role (3.20)
“Using the service” who receive(s) the service result.
Relationships with other roles (3.20):
The role (3.20) “System operation” is connected with the role (3.20) “System management”. In this
relationship, denominated with the term “managed by” in Figure 3, the actor(s) (3.2) with the role
(3.20) “System management” provide supporting functionalities to the actor(s) (3.2) with the role
(3.20) “System operation”. This mainly includes functionalities enabling and facilitating the “System
management” behaviour (3.4) and responsibilities (3.18).
8 © ISO 2014 – All rights reserved

The role (3.20) “‘System operation” is connected with the role (3.20) “Policy framework”. In this
relationship, denominated with the term “governed by” in Figure 3, the actor(s) (3.2) with the role
“Policy framework” provide policies and regulations as well as their enforcement to the actor(s) (3.2)
with the role (3.20) “System operation”.
The role (3.20) “System operation” is connected with the role (3.20) “Using the system”. In this
relationship, denominated with the term “used by” in Figure 3, the actor(s) (3.2) with the role (3.20)
“System operation” provide the achieved results to the actor(s) (3.20) with the role (3.20) “Using the
system”. The role (3.20) “Using the system” make(s) use of these results.
6.1.3 Using the system
The role (3.20) “Using the system” is responsible to perform an appropriate reaction to the service result
received from the actors (3.20) with role (3.20) “System operation”. The role (3.20) “Using the system”
might stimulate the role (3.20) “System operation” (trigger an ITS service (3.23)).
6.1.4 System management
The role (3.20) “System management” is responsible to fulfil all required management activities within
the system, this especially includes activities supporting “System operation”. Additional actions (3.1)
are the management of the “Policy framework” activities.
Relationship with other roles (3.20):
The role (3.20) “System management” is connected with the role (3.20) “Policy framework”, in this
relationship, denominated with the term “managed by” in Figure 3, the actor(s) (3.2) with role (3.20)
“System management” provide supporting functionalities to the actor(s) (3.2) with the role (3.20) “Policy
framework”. This mainly includes functionalities enabling and facilitating the “Policy Framework”
behaviour (3.4) and responsibilities (3.18). Additionally the actor(s) (3.2) with the role (3.20) “Policy
framework” provide(s) policies and regulations as well as their enforcement to the actor(s) (3.2) with
the role (3.20) “System management”. This is denominated with the term “governed by” in Figure 3.
6.1.5 Policy framework
The role (3.20) “Policy framework’ is responsible for all governing and institutional activities required
in the system.
Relationship with other Roles (3.20):
See above (“System operation”, “System management”). Relationships of role (3.20) “Policy Framework”
with role (3.20) “System Operation” and role (3.20) “System Management” have already been given in
subclauses 6.2.1 and 6.2.3.
The three main roles (3.20) “System operation”, “System management” and “Policy framework” are
detailed with sub-roles. Those are described in the following subclauses. The role (3.20) “Using the
service” is not further detailed, a more detailed description of its responsibilities is appended.
6.2 General responsibilities of actors involved in C-ITS
6.2.1 Registration and authorization
Prior to the use of the system each role (3.20) and, therefore each actor (3.2), shall be responsible to
participate in activities related to the request of access permission. This includes both registration and
authorization:
— Registration – defined as registration to the system itself, necessary prior to the first use of the
system (compare with sign-up):
— issue request for registration to the system,
— receive certificates for registered ITS Stations.
— Authorization – defined as authorization prior to every system usage (comparable to sign-in):
— issue request for authorization,
— receive confirmation of authorization.
Details of the activities following the registration or authorization request and leading to the reception
of a permission or confirmation base on the standard registration and authorization mechanisms
defined in ISO 14817.
6.2.2 Privacy and Data Protection
The definition of C-ITS, as stated in ISO 17465, mentions two core characteristics of C-ITS: (a) The
distributed implementation of ITS services (3.23), which requires a huge number of data and information
exchanges between ITS Stations (3.12) to realize the respective end-to-end ITS service (3.23) and, (b)
The sharing of data and information between ITS Stations (3.12) for purposes other than the original
intent. Both properties lead to serious consequences on C-ITS regarding privacy and data protection.
ISO/TR 12859 provides a detailed description of privacy and data protection issues for C-ITS, as a whole.
Additionally, this important subject needs to be reflected in every single C-ITS standard including this
Technical Specification. It will be one of the major tasks of the actors (3.2) that claim one of the roles
(3.20) defined in this Technical Specification to respect the responsibilities (3.18) regarding privacy and
data protection.
Much of the data/information collected and processed in C-ITS can be associated with an individual.
This especially applies to any kind of data/information collected through a vehicle (floating car data)
including any ITS Station that is moving e.g. mobile device. Therefore this content is subject to strict
privacy and data protection Regulations and the roles (3.20) collecting or handling this content have to
respect the corresponding regulations.
Each role (3.20) and, therefore each actor (3.2), is responsible to respect both ISO/TR 12859 and national
regulations and laws on privacy and data protection when participating in C-ITS.
In general, this applies for the following actions (3.1):
— Collection of data/information (content): each actor (3.2) collecting data/information (including
the hand-over of data/information from other parties) handles this data/information with care and
respect the originators privacy based on the principles outlined in ISO/TR 12859;
— Processing of data/information (content): each actor (3.2) processing data/information handles
this data/information with care and complies with the principles outlined in ISO/TR 12859;
— Deletion of data/information (content) after usage: each actor (3.2) handling data/information
ensures the proper deletion of data/information after usage based on the principles outlined in
ISO/TR 12859;
— Transmission of data/information (content): each actor (3.2) providing an ITS service (3.23)
that transmits data/information complies with the principles outlined in ISO/TR 12859.
Any role (3.20) described in the following Clauses is, in a way, in touch with data/information collected
or used in C-ITS and, therefore, needs to comply with these requirements.
6.3 Role: System operation
6.3.1 General description
The role (3.20) “System operation” is responsible for all activities related to the operation of the system.
The responsibilities reflect the process chain of the corresponding services.
10 © ISO 2014 – All rights reserved

The role (3.20) “System operation” is composed of the sub-roles (3.21) content provision, service
provision and presentation provision. The mentioned sub-roles share the responsibilities (3.18) of the
role (3.20) “System operation”. The role (3.20) “System operation” itself bundles all responsibilities (3.18)
of the sub-roles (3.21).
6.3.2 Sub-role: Content provision
The sub-role (3.21) “Content provision” shall provide various types of content. This includes every type
of data between raw data and highly (pre-) processed information.
Prior to the provision of content the sub-role (3.21) shall be responsible for the registration of itself as a
content provider and the content that is provided:
— subscribe content provision activity,
— cancel content provision activity,
— registration of content (data/information),
— cancel/deregistration of content (data/information).
Details of content (data/information) registration related activities can be found in ISO 14817.
The responsibilities (3.18) associated with this sub-role (3.21) that have a tight relation to the “Service
provision” itself are:
— receive content request,
— obtain content (data/information),
— provide content (data/information).
Additionally the role ‘Content Provision’ is responsible for ensuring data integrity.
6.3.3 Sub-role: Service provision
The sub-role (3.21) “Service provision” shall connect the sub-role (3.21) “Content provision” with the sub-
role (3.21) “Presentation provision”.
The sub-role (3.21) “Service provision” identifies which algorithm is suitable to fulfil the end-to-end
ITS service (3.23), it determines the content that is required to run the ITS service (3.23), afterwards
runs the ITS service (3.23) and provides a suitable service response. The content required to run the
ITS service (3.23) is requested and received from the sub-role (3.21) “Content provision”. The service
results shall be delivered to the sub-role (3.21) ”Presentation provision”.
Prior to the provision of the ITS service (3.23), the registration of the ITS service (3.23) with the role
(3.20) “Service catalogue management” shall be required. The sub-role (3.21) ”Service provision” shall
be responsible for the activities:
— subscribe new ITS service (3.23),
— cancel/deregistration of ITS service (3.23).
Details of these activities are described in ISO/TS 17419.
The responsibilities (3.18) related to the sub-role (3.21) “Service provision” that have a tight link to the
execution of the service itself are:
— receive service request,
— select ITS service (3.23)/ application (3.3)/algorithm,
— operate ITS service (3.23)/ application (3.3)/ algorithm (service generation),
— request content (data/information) for service execution,
— receive content (data/information) for service execution,
— provision of service (result).
6.3.4 Sub-role: Presentation provision
The sub-role (3.21) “Presentation provision” shall be responsible for the suitable presentation of the
service results. This includes the scheduling of presentations, the prioritization of information to be
presented and the selection of the presentation mode (visual, auditory, tactile).
Responsibilities (3.18) tied to the sub-role (3.21) are:
— receive service results,
— scheduling of presentations,
— prioritization of service results,
— selection of presentation mode,
— conformance of presentation with regulation(s).
6.4 Role: Using the service
The role (3.20) “Using the service” incorporates the triggering of ITS services (3.23) available within the
system. The entity occupying the role therefore issues service requests and receives service responses.
The responsibilities (3.18) related to the role (3.20) “Using the service” therefore have a tight relation to
the service operation itself:
— issue service request,
— recognition of service result presentation,
— judge the need for reaction,
— react accordingly.
6.5 Role: System management
The role (3.20) “system management” is responsible for all management activities in the system. It
supports both “System operation” and “Policy framework”.
The sub-roles (3.21) of the role (3.20) “system management” are derived from the ones defined in ITIL V3
[17]
(Information Technology Infrastructure Library). Not all roles (3.20) from ITIL V3 will be used in
C-ITS – the appropriate ones regarding level of detail and C-ITS characteristics were selected. Where
necessary, roles (3.20) were merged and renamed.
Despite the revision and adaptation of the ITIL V3 roles (3.20) the remaining roles (3.20) can partially
be grouped. This is announced in the text accompanying the following descriptions.
System management is a distributed role (multiple entities).
6.5.1 Sub-role: Service catalogue manager
This sub-role (3.21) shall be responsible for up-to-date maintaining of the service catalogue that lists all
registered ITS services (3.23) and their status. This includes:
— add new ITS service (3.23) to the service catalogue,
12 © ISO 2014 – All rights reserved

— remove ITS service (3.23) that are unsubscribed from the service catalogue.
A detailed description can be found in ISO/TS 17419.
6.5.2 Sub-role: Communication manager
This sub-role (3.21) shall be responsible for enabling the communication among ITS Stations (3.12). This
may includes:
— Station internal communication management (ISO 24102-1),
— Station remote communication management (ISO 24102-2),
— Inter-station communication management.
6.5.3 Sub-role: Service owner
This sub-role (3.21) shall be responsible for designing and delivering a particular C-ITS end-to-end
ITS service (3.23) within the agreed service levels. Service ownership shall as well occur on a per process
step (content provision, service provision, presentation provision) level.
6.5.4 Sub-role: C-ITS architect
This sub-role (3.21) shall be responsible for maintaining the implemented C-ITS Architecture, including
architecture viewpoints.
6.5.5 Sub-role: Project manager
This sub-role (3.21) shall be responsible for planning and coordinating the resources (including software,
hardware) to deploy, operate and maintain C-ITS.
6.5.6 Sub-role: Test manager
This sub-role (3.21) shall ensures that deployed ITS services (3.23) fulfil their specification.
6.5.7 Sub-roles for preparation, operation and maintenance of service environment
The following sub-roles (3.21) all focus on the preparation, operation and maintenance of the service
environment.
6.5.8 Sub-role: Service level manager
This sub-role shall be responsible for negotiating C-ITS service level agreements and ensuring that these
are met.
6.5.9 Sub-role: Risk manager
This sub-role (3.21) shall be responsible for identifying, assessing and controlling risks.
6.5.10 Sub-role: Capacity manager
This sub-role shall be responsible for ensuring that ITS services (3.23) and infrastructure (3.11) are able
to deliver the agreed capacity and performance targets.
6.5.11 Sub-role: Availability manager
This sub-role (3.21) shall be responsible for defining, analysing, planning, measuring and improving all
aspects of the availability of the C-ITS system.
6.5.12 Sub-roles for IT-security
The following sub-roles (3.21) focus on IT security including access control
6.5.12.1 Sub-role: Information security manager’
This sub-role (3.21) shall be responsible for ensuring the confidentiality, integrity and availability of the
system, data, information, C-ITS services and the user.
6.5.12.2 Sub-role: Access manager
This sub-role (3.21) shall be responsible for granting the right to use a C-ITS service to authorized users
and preventing access to non-authorized users.
6.5.13 Sub-roles for system maintenance and update
The following sub-roles (3.21) focus on system maintenance and update
6.5.13.1 Sub-role: Technical analyst
This sub-role (3.21) is a Technical Management role (3.20) which provides technical expertise and
support for the management of the C-ITS infrastructure.
6.5.13.2 Sub-role: Change manager
This sub-role (3.21) shall be responsible for all change activities including collection of change requests,
handling of change requests and application of changes.
6.5.13.3 Sub-role: Configuration manager
This sub-role (3.21) shall be responsible for maintaining information about infrastructure (3.11)/
equipment/hardware required to deliver C-ITS services.
6.5.13.4 Sub-role: Homologation manager
This sub-role (3.21) shall be responsible for product certification, test or authorization prior to
deployment.
6.5.13.5 Sub-role: System monitoring
This sub-role (3.21) shall be responsible for monitoring the system state.
6.5.13.6 Sub-role: Financial Manager
This sub-role (3.21) is optional depending on the type of ITS service (3.23) (e.g. free safety related traffic
information versus commercial services). The financial manager is responsible for managing budgeting,
accounting and charging in the context of the ITS service (3.23).
6.6 Role: Policy framework
6.6.1 General description
The role (3.20) “Policy framework” shall be responsible for all governing and institutional activities in
the system and governs the management and system operational activities.
14 © ISO 2014 – All rights reserved

6.6.2 Sub-role: Compliance manager
This sub-role (3.21) shall be responsible to ensure that standards, guidelines, laws and regulations for
C-ITS are followed and applied.
6.6.3 Sub-role: Policy institution
This sub-role (3.21) shall be responsible for the definition of regulatory and non-regulatory policies
(e.g. agreements between stakeholders (3.26), regulations) regarding the design, implementation,
deployment or operation of C-ITS.
6.6.4 Sub-roles: Miscellaneous
Other sub-roles (3.21) that are defined in the corresponding documents are listed in the following
subclauses.
6.6.4.1 Sub-role: Standardization organization
Standardization is defined as an activity of establishing, with regard to actual or potential problems,
provisions for common and repeated use, aimed at the achievement of the optimum degree of order in a
[8]
given context. Details can be found in ISO/IEC Guide 2.
6.6.4.2 Sub-role: Security certificate body
[10] [11] [12] [13]
Description can be found in TR 11176, TR 11769, ISO 24100 and IEEE 1609.2 −2006.
6.6.4.3 Sub-role: Legislation, jurisdiction
Description can be found in national regulations.
6.7 Profiles
A profile provides a set of one or more base assignment of roles (3.20) and, where applicable, the
identification of chosen classes, conforming subsets, options and parameters of those base roles (3.20)
(or in the case of ITS systems, standards or otherwise defined systems), necessary to accomplish a
particular function/service with its characteristics.
The different profiles demonstrate key characteristics of an organisational architecture:
— one role (3.20) can be assigned to multiple actors,
— one actor can occupy multiple roles (3.20).
7 Compliance
It is recommended that any implementation of an organizational architecture for C-ITS should comply
with this Technical Specification. Compliance with this Technical Specification is achieved when all roles
(3.20) and sub-roles (3.21) described in Clause 6 are assigned to corresponding actors in C-ITS.
Annex A
(informative)
Methodology and its sample application
A.1 Methodology to identify cooperative ITS roles, behaviour and responsibilities
A.1.1 Introduction
To identify the “Roles and responsibilities in the context of cooperative ITS based on architecture(s) for
cooperative systems” an abstract methodology is defined. This methodology can be applied to any C-ITS
service. It starts from the identification of the ITS service (3.23) specific stakeholders (3.26) and actors
(3.2), identifies their behaviour (3.3) and responsibilities (3.18) with the support of an abstract process
description of the service operation and finally transforms the results into a basic organisational model
for this ITS service (3.23).
A.1.2 Stakeholders
For the implementation of C-ITS, various players from different industries that did not collaborate so
far will have to cooperate to realize one or more of the numerous implementation scenarios (3.22) of
ITS service (3.23).
Stakeholders (3.26) are not necessarily active participants in C-ITS i.e. they only have an occasional
interest in the deployment and/or operation of C-ITS itself. Hence the group of stakeholders (3.26)
incorporates the following entities:
— national/regional authorities (e.g. government, ministry),
— interest groups (e.g. user),
— lobby groups (e.g. industry),
— industry associations.
A.1.2.1 Actors
C-ITS can be implemented in various scenarios (3.22) with the participation of different actors (3.2). A
structure was developed to clearly arrange the different actors (3.2). On the first level, the structuring
elements are the C-ITS components to which the behaviour of the actors (3.2) can be assigned to, more
precisely:
— the hardware platform (sensors, actuators, others) that is required to execute the ITS service (3.23),
(both mobile and static),
— the software running on this hardware platform to provide the ITS service (3.23).
The actors (3.2) in these fields are further subdivided into those responsible for:
— operation,
— system management functionalities like maintenance and installation/disassembly,
— policy framework functionalities like agreement on frameworks.
EXAMPLE There will be an actor (3.2) who has a behaviour (3.3) and responsibilities (3.18) tied to the
operation of the hardware platform. Another one will maintain the software part.
16 © ISO 2014 – All rights reserved

IS
...