ISO/TR 14813-2:2000

TECHNICAL ISO/TR
REPORT 14813-2
First edition
2000-12-15
Transport information and control
systems — Reference model architecture(s)
for the TICS sector —
Part 2:
Core TICS reference architecture
Systèmes de commande et d'information des transports — Architecture(s)
du modèle de référence du secteur TICS —
Partie 2: Architecture de référence du noyau des TICS
Reference number
©
ISO 2000
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not
be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this
file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this
area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters
were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event
that a problem relating to it is found, please inform the Central Secretariat at the address given below.
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic
or mechanical, including photocopying and microfilm, without permission in writing 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 copyright@iso.ch
Web www.iso.ch
Printed in Switzerland
ii © ISO 2000 – All rights reserved

Contents
Foreword.viii
Introduction.x
1 Scope .1
2 Normative references.2
3 Terms and definitions .2
4 Symbols and abbreviated terms .5
4.1  Use Case diagram.5
4.2  Package Diagram.5
4.3  Class diagram .6
4.4  Association Diagram.6
4.5  Sequence (Interaction) Diagram .7
5 Overview of the Core TICS Reference Architecture.7
5.1  Generalised Use Cases in the Core TICS Reference Architecture.7
5.2  Generalised Actors in the Core TICS Reference Architecture.10
5.3  Generalised Packages of the Core TICS Reference Architecture .10
6 Actors associated with the Core TICS Reference Architecture.12
6.1  User.12
6.1.1  Traveller.13
6.1.2  Forwarder .13
6.1.3  Consignor/Consignee .13
6.1.4  Pedestrian .13
6.1.5  Passenger.13
6.1.6  Driver.13
6.1.7  Emergency Vehicle Driver .14
6.1.8  Commercial Vehicle Driver .14
6.1.9  Public Transport Driver.14
6.2  Service Enabler.14
6.2.1  Carrier Operator.14
6.2.2  Conformance Agency.15
6.2.3  Emergency Service.15
6.2.4  Location Data Source.15
6.2.5  Public Transport Operator.15
6.2.6  Traffic Operator.15
6.2.7  Transport Inspection.15
6.2.8  Transport Planner.15
6.2.9  Traveller Information.16
6.3  Financial .16
6.3.1  Clearing Operator .16
6.3.2  Collection Agent .16
6.4  Infrastructure .16
6.4.1  Parking.17
6.4.2  Multimodal Crossing .17
6.4.3  Rail Operations .17
6.5  Information Provider/Consumer .17
6.5.1  Event Promoter .18
6.5.2  Media.18
6.5.3  Information Consumer .18
6.5.4  Meteorology .18
6.5.5  Geographic Information Provider .18
6.6  Service Provider.19
6.6.1  Inter-modal Passenger Service Provider .19
6.6.2  Yellow Pages Service .19
6.7  Vehicle .19
6.7.1  (Base) Vehicle .20
6.7.2  Commercial Vehicle.20
6.7.3  Emergency Vehicle.20
6.7.4  Public Transport Vehicle.21
7 Use Cases of the Core TICS Reference Architecture.21
7.1  Traveller Information Use Case Diagram .22
7.1.1  Pre-Journey Information .22
7.1.2  Journey Payment.23
7.1.3  On-Trip Traveller Information.23
7.1.4  Route Guidance and Navigation .23
7.1.5  Journey Schedule.23
7.1.6  Demand Responsive Public Transport.23
7.2  Traffic Management Use Case Diagram .23
7.2.1  Transportation Planning Support .24
7.2.2  Performance Prediction .24
7.2.3  Traffic Control .25
7.2.4  Traffic & Pollution Measurement & Control .25
7.2.5  Performance Evaluation.26
7.2.6  Incident Management .26
7.2.7  Demand Management.26
7.2.8  Infrastructure Maintenance Management .26
7.3  Vehicle Use Case Diagram.26
7.3.1  Vehicle Status .26
7.3.2  Vehicle Operation .26
7.4  Commercial Vehicle Use Case Diagram.27
7.4.1  Order and Shipment .28
7.4.2  Commercial Vehicle Tour Planning .28
7.4.3  Commercial Vehicle Administrative Processes .29
7.4.4  Commercial Vehicle Road Operation.29
7.4.5  Route Guidance and Navigation .29
7.4.6  Journey Payment.29
7.4.7  On-Trip Traveller Information.29
7.5  Public Transport Diagram.29
7.5.1  Route & Schedule Planning.29
7.5.2  Fixed Route Public Transport.30
7.5.3  Demand Responsive Public Transport.30
7.5.4  Journey Schedule.30
7.5.5  Route Guidance and Navigation .31
7.6  Emergency Use Case Diagram.31
7.6.1  Emergency Notification & Personal Security .31
7.6.2  Emergency Resources Allocation.31
7.6.3  Emergency Vehicle Management.31
7.6.4  Route Guidance and Navigation .31
7.7  Electronic Payment Use Case Diagram.31
7.7.1  Payment Means.32
7.7.2  Fare Collection.32
7.7.3  Vehicle Charges.32
7.7.4  Payment Transaction .33
7.7.5  Journey Payment.34
7.7.6  On-Trip Traveller Information.34
7.8  Safety Use Case Diagram .34
7.8.1  Safety Enhancement for Vulnerable Road Users.34
7.9  Actor/Use Case Matrix.34
8 Sequence Diagrams.39
8.1  Traveller Information .40
iv © ISO 2000 – All rights reserved

8.1.1  Class Operations for Traveller Information .40
8.1.2  Traveller Information Sequence Diagram .43
8.2  Traffic Management.43
8.2.1  Class Operations for Traffic Management .43
8.2.2  Traffic Management Sequence Diagram .46
8.3  Vehicle .48
8.3.1  Class Operations for Vehicle.48
8.3.2  Vehicle Sequence Diagram.50
8.4  Commercial Vehicle.50
8.4.1  Class Operations for Commercial Vehicle.50
8.4.2  Commercial Vehicle Sequence Diagram.52
8.5  Public Transport .54
8.5.1  Class Operations for Public Transport.54
8.5.2  Public Transport Sequence Diagram.55
8.6  Emergency.56
8.6.1  Class Operations for Emergency.56
8.6.2  Emergency Sequence Diagram.57
8.7  Electronic Payment .58
8.7.1  Class Operations for Electronic Payment.58
8.7.2  Electronic Payment Sequence Diagram.59
8.8  Safety .60
8.8.1  Class Operations for Safety.60
8.8.2  Safety Sequence Diagram.61
Annex A (informative) Core TICS Reference Architecture Development Approach .62
Bibliography.66
List of figures
Figure 1 — Use Case diagram .5
Figure 2 — Package Diagram .5
Figure 3 — Class diagram .6
Figure 4 — Association diagram .6
Figure 5 — Sequence (Interaction) diagram .7
Figure 6 — Core TICS Reference Architecture Top Level Use Case Diagram. A set of generalised use case and
actors that define the scope of the core TICS reference architecture.9
Figure 7 — Core TICS Reference Architecture Top Level Packages The diagram defines the conceptual packages
which comprise the TICS system package .12
Figure 8 — The hierarchy of actors of type User.13
Figure 9 — The hierarchy of actors of type Service Enabler.14
Figure 10 — The hierarchy of actors of type Financial.16
Figure 11 — Actors of type Infrastructure.17
Figure 12 — Actors of type Information Provider/Consumer.18
Figure 13 — Actors of type Service Provider .19
Figure 14 — The actors of type Vehicle .20
Figure 15 — Traveller information Use Case diagram .24
Figure 16 — Traffic management use case diagram .25
Figure 17 — Vehicle use case diagram.27
Figure 18 — Commercial Vehicle use case diagram .28
Figure 19 — Public Transport use case diagram .30
Figure 20 — Emergency use case diagram .32
Figure 21 — Electronic Payment use case diagram .33
Figure 22 — Safety use case diagram .34
Figure 23 — Packages and their abstract classes .41
Figure 24 — Operations of the abstract classes relevant to the Traveller Information object interactions in Figure 25
.............................................................................................................................................................................42
Figure 25 — Sequence diagram showing the main interactions and operations for the Traveller Information Use
Case Diagram.44
Figure 26 — Operations of the abstract classes relevant to the Traffic Management object interactions in Figure 27
.............................................................................................................................................................................45
Figure 27 — Sequence diagram showing the main interactions and operations for the Traffic Management Use
Case Diagram.47
Figure 28 — Operations of the abstract classes relevant to the Vehicle object interactions in Figure 29 .49
Figure 29 — Sequence diagram showing the main interactions and operations for the Vehicle Use Case Diagram50
Figure 30 — Operations of the abstract classes relevant to the Commercial Vehicle object interactions in Figure 31
.............................................................................................................................................................................51
Figure 31 — Sequence diagram showing the main interactions and operations for the Commercial Vehicle Use
Case Diagram.53
Figure 32 — Operations of the abstract classes relevant to the Public Transport object interactions in Figure 33.54
Figure 33 — Sequence diagram showing the main interactions and operations for the Public Transport Use Case
Diagram .56
Figure 34 — Operations of the abstract classes relevant to the Emergency object interactions in Figure 35.57
Figure 35 — Sequence diagram showing the main interactions and operations for the Emergency Use Case
Diagram .58
Figure 36 — Operations of the abstract classes relevant to the Payment object interactions in Figure 37.59
Figure 37 — Sequence diagram showing the main interactions and operations for the Electronic Payment Use
Case Diagram.60
Figure 38 — Operations of the abstract classes relevant to the Safety object interactions in Figure 39.61
Figure 39 — Sequence diagram showing the main interactions and operations for the Safety Use Case Diagram.61
vi © ISO 2000 – All rights reserved

List of tables
Table 1 — Service Grouping .8
Table 2 —Mapping of TICS Fundamental Services to Use Cases .21
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 main task of technical committees is to prepare International Standards, but in exceptional circumstances a
technical committee may propose the publication of a Technical Report of one of the following types:
— type 1, when the required support cannot be obtained for the publication of an International Standard, despite
repeated efforts;
— type 2, when the subject is still under technical development or where for any other reason there is the future
but not immediate possibility of an agreement on an International Standard;
— type 3, when a technical committee has collected data of different kind from that which is normally published
as an International Standard ("state of the art", for example).
Technical Reports of types 1 and 2 are subject to review within three years of publication, to decide whether they
can be transformed into International Standards. Technical Reports of type 3 do not necessarily have to be
reviewed until the data they provide are considered to be no longer valid or useful.
Technical Reports are drafted in accordance with the rules given in the ISO/IEC Directives, Part 3.
Attention is drawn to the possibility that some of the elements of this part of ISO/TR 14813 may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO/TR 14813-2, which is a Technical Report of type 2, was prepared by Technical Committee ISO/TC 204,
Transport information and control systems.
This document is being issued in the Technical Report (type 2) series of publications (according to
subclause G.3.2.2 of Part 1 of the ISO/IEC Directives, 1995) as a “prospective standard for provisional application”
in the field of transport information and control systems because there is an urgent need for guidance on how
standards in this field should be used to meet an identified need.
This document is not to be regarded as an “International Standard”. It is proposed for provisional application so that
information and experience of its use in practice may be gathered. Comments on the content of this document
should be sent to the ISO Central Secretariat.
A review of this Technical Report (type 2) will be carried out not later than three years after its publication with the
options of: extension for another three years; conversion into an International Standard; or withdrawal.
ISO/TR 14813 consists of the following parts, under the general title Transport information and control systems —
Reference model architecture(s) for the TICS sector:
 Part 1: TICS fundamental services. This document presents the definition of 32 TICS fundamental services
that are the informational products or services or applications areas provided to a TICS user.
 Part 2: Core TICS reference architecture. This document describes an abstract object-oriented system
architecture based on the TICS fundamental services.
viii © ISO 2000 – All rights reserved

 Part 3: Example elaboration. This document refines the core TICS reference architecture (part 2) with some
emphasis on traffic management.
 Part 4: Reference model tutorial. This document describes the basic terms, graphical representations and
modelling views exploited in the object-oriented definition of the architecture development of parts 2 and 3.
 Part 5: Requirements for architecture description in TICS standards. This document describes the terminology
and form to be used when documenting or referencing aspects of architecture description in TICS standards.
 Part 6: Data presentation in ASN.1. This document establishes the use of ASN.1 as the normal syntax notation
to be used in standards for the TICS sector and a common message form for such ASN.1 based data
elements.
Annex A of this part of ISO/TR 14813 is for information only.
Introduction
TC204/WG1 is a working group whose prime objectives are to provide services to ISO TC204 and its working
groups. A specific mission of WG1 is to:
“Provide ISO TC204, its working Groups, related bodies and those involved in the TICS sector, with a reference
model of Conceptual Reference Architecture(s) that show the structure and inter-relationships of the sector .”
It is expected that there may well be more than one single TICS Architecture approach to be considered and
documented and that existing architecture approaches will have previously-produced documentation developed
according to disparate standards and conventions.
It is also implicit in the work being undertaken by WG1, that working group members will require a clear, well-
structured understanding of the work of the following participant groups:
• Other TC 204 Working Groups
• CEN TC 278 Working Groups
• Japanese initiatives
• European Road Transport and Traffic Telematics programs
• US Intelligent Transportation Systems program
• Australian initiatives
• Canadian Initiatives
Full documentation of all possible architectural approaches is obviously not feasible given the high level of
resources required to carry this out. Indeed full documentation and description of all possible approaches is
undesirable as an item for Standardisation.
A defined and consistent approach is however required to facilitate the specification of architecture requirements to
enable a clear view to be developed and presented of the work of each participant group This document is one of a
set of WG1 documents intended to respond to stated WG1 objectives regarding the production of a TICS
Reference Architecture.
In order to document an architecture, graphical and textual components of a model are required. WG1 has adopted
a methodology based on the Unified Modelling Language (UML) for documenting the TICS Reference Architecture.
A tutorial on the UML is provided in Part 4. UML is a visual modelling language for building object-oriented and
component-based systems. A commercially available Computer Aided Software Engineering (CASE) tool has been
used by WG1 to document the Architecture. While the tool is a commercial product, UML is open and non-
proprietary.
x © ISO 2000 – All rights reserved

TECHNICAL REPORT ISO/TR 14813-2:2000(E)
Transport information and control systems — Reference model
architecture(s) for the TICS sector — Part 2: Core TICS reference
architecture
1 Scope
The architecture of an information and control system merges hardware and software considerations into a
coordinated and integrated system view. The system architecture is a high level abstraction, or model, of the
system. A system architecture should embrace both today’s applications and the applications that are expected in
the future. Architecture begins with the definition of the conceptual services (e.g. Part 1 - TICS fundamental
services). There are several identifiable stages of system architecture development:
 1. Reference architecture
 2. Logical architecture
 3. Physical architecture
A reference architecture is the first of all architectures. It is a concise generic framework which guides the
development of more concrete system architectures. It is large enough that distinct concepts are not merged out of
necessity and small enough that it does not become unwieldy.
A most significant example of a reference architecture in information systems is the Reference Model of Open
Systems Interconnection (often called the seven layer model) developed by ISO in the 1970’s. This model has
underpinned the development of all modern computer networks, allowing services such as global networking, of
which the prime example is the Internet, to become a reality.
A reference architecture is generic and non-prescriptive and captures the concepts of the system. A logical
architecture elaborates the conceptual behaviour, and in so doing it provides more detail about the modularity. A
physical architecture is reached when the actual distribution of the system modules is defined, thus leading to
important implications for communications.
There is no firm demarcation between a reference architecture and a logical architecture. Thus the essence of
behaviour and modularity is present in a reference architecture. The TICS Reference Architecture developed by
WG1 shows important inter-relationships that arise in the provision of the services of the sector. However the TICS
Reference Architecture is more abstract than, for example, the logical architecture of the US National Architecture.
It is envisioned that the TICS Reference Architecture will be used by the TC204 Working Groups to develop their
own logical and physical architectures in a cohesive manner.
Some TICS Fundamental Services are already well developed by the industry, while others are less mature.
Therefore the TICS Reference Architecture does not have a uniform granularity across all services. This
characteristic is a direct result of the fore mentioned requirement that architecture embrace the applications that are
intended in the future. This suggests one of the ways in which the architecture will undergo change in the future.
Architectures may present only static characteristics or both static and dynamic characteristics. Dynamic
characteristics may be seen as belonging solely to the design/implementation stages of system development.
However by including dynamic characteristics at the reference architecture stage one gains important insights into
the static architecture. Thus two orthogonal views of architecture are presented:
 1. static relationship view (class diagram)
 2. dynamic interactive view (sequence diagram)
This part of ISO/TR 14813 develops a core reference architecture. The static scope is determined by deriving the
system boundary and the use cases from an analysis of the TICS fundamental services (part 1 of ISO/TR 14813).
The Core Reference Architecture is a reference for the development of national architectures.
Part 3 of ISO/TR14813 elaborates the core reference architecture by refinement of two orthogonal views. The
elaboration calls upon domain expertise that would be provided by other TC204 Working Groups in the
development of ISO standards or by national groups developing national architectures and standards.
The core reference architecture is described in clauses 5 to 8. Clause 5 introduces the architecture at a highly
abstract level. Clause 6 defines all the actors. Clause 7 derives all the use case from the TICS fundamental
services and develops eight use case diagrams. Clause 8 defines an abstract collection of classes and develops a
set of sequence diagrams, one per use case diagram.
Readers should refer to Part 4 of ISO/TR 14813 (Tutorial) for an introduction to the modelling views used in this
part and the methodology applied. The methodology is repeated in Annex A.
2 Normative references
The following normative documents contain provisions that, through reference in this text, constitute provisions of
this part of ISO/TR 14813. For dated references, subsequent amendments to, or revisions of, any of these
publications do not apply. However, parties to agreements based on this part of ISO/TR 14813 are encouraged to
investigate the possibility of applying the most recent editions of the normative documents indicated below. For
undated references, the latest edition of the normative document referred to applies. Members of ISO and IEC
maintain registers of currently valid International Standards.
ISO/TR 14813-1:1999, Transport information and control systems – Reference model architecture(s) for the TICS
sector – Part 1:TICS fundamental services.
ISO/TR 14813-3:2000, Transport information and control systems – Reference model architecture(s) for the TICS
sector – Part 3: Example elaboration.
ISO/TR 14813-4:2000, Transport information and control systems – Reference model architecture(s) for the TICS
sector – Part 4: Reference model tutorial.
3 Terms and definitions
For the purposes of this part of ISO/TR 14813, the following semantic definitions apply.
3.1
The Unified Modeling Language (UML) is the industry-standard language for specifying, visualising, constructing,
and documenting the artefacts of software systems. It simplifies the complex process of software design, making a
“blueprint” for construction.
3.2
A use case is a coherent unit of functionality provided by a system or class as manifested by sequences of
messages exchanged among the system and one or more outside interactors (called actors) together with actions
performed by the system.
http://www.rational.com/uml/
2 © ISO 2000 – All rights reserved

3.3
An actor is a role of an object or objects outside of a system that interacts directly with it as part o
...