ISO/TR 22625:2025
(Main)Intelligent transport systems — Mobility integration — Physical and functional view
Intelligent transport systems — Mobility integration — Physical and functional view
This document describes the physical and functional views defined in ISO/TS 14812 on integrated mobility, based on the role and responsibilities models in the mobility-as-a-service (MaaS) and mobility on demand (MOD) ecosystems as described in ISO/TR 4447 and ISO/TR 7878. This document focuses on mobility service concepts where the included transport services are publicly available.
Titre manque
General Information
Standards Content (Sample)
Technical
Report
ISO/TR 22625
First edition
Intelligent transport systems —
2025-09
Mobility integration — Physical and
functional view
Reference number
© ISO 2025
All rights reserved. Unless otherwise specified, or required in the context of its implementation, 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
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 1
3.1 Terms and definitions .1
3.2 Abbreviated terms .2
4 The core physical and functional objects in the provision of mobility services . 2
4.1 General .2
4.2 MSU requests, books, uses, and pays for the mobility service .4
4.2.1 Use case physical and functional objects .4
4.2.2 Use case interfaces .7
4.3 Manage mobility services .9
4.3.1 Use case Physical objects and functional objects .9
4.3.2 Use case interfaces .11
4.3.3 Interface between TSP Central system and Transport means on-board
Equipment interface .11
4.4 Manage transport services .11
4.4.1 Use case Physical and Functional objects .11
4.4.2 Use case interfaces . 13
4.5 Manage transport infrastructure .14
4.5.1 Use case Physical and Functional objects .14
4.5.2 Use case interfaces . 15
5 External physical objects . 16
5.1 General .16
5.2 Systems for data security .17
5.3 Systems for positioning .17
5.4 Communication systems . .17
5.5 Systems for data management services .17
5.6 PSP systems.17
5.7 Electronic fee and fare collection systems .17
Bibliography .18
iii
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 document 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).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
iv
Introduction
Urbanization, changes in climate and demographic and societal changes are some of the major trends
that have had an impact on transport systems and services over the last decades. Combined with the
implementation of ITS services and Internet of Things (IoT), new transport concepts have been developed.
User requirements on efficiency, availability and interoperability have also been driving forces for new
transport concepts for the integration of multimodal, existing and new transport services as described and
implemented in mobility concepts like mobility as a service (MaaS) and mobility on demand (MOD). Co-
operative, connected and automated mobility (CCAM) can also have a significant effect on how travellers plan
and implement their journeys between multiple modes of transport in the integrated mobility environment.
Integrated mobility concepts are evolving around the world, mostly based on the MaaS and MOD concepts.
There is a need for a generic, common, and world-wide concept description mapping all existing and foreseen
concepts for interoperable, integrated and seamless multimodal transport services.
The role and responsibility models for MaaS and MOD have already been described in ISO/TR 4447.
However, there is also a need for a common role and responsibility model for integrated and multimodal
mobility services, recognizing and including the work already done by the two mainstream organizations
for integrated mobility services, MaaS and MOD.
[3]
A common role and responsibility model can be described from an enterprise view , where the stakeholders,
actors and roles in the MaaS and MOD ecosystems are merged into one enterprise view. The enterprise view
addresses the relationships between the entities (e.g. organizations) involved in the provision of the mobility
services. An enterprise view has been described in ISO/TR 7878.
[3]
The objective of this document is to describe integrated mobility from a physical and functional view , to
which existing implementations of integrated mobility systems can potentially be mapped. This is intended
to enable a common understanding, an exchange of information and knowledge, and a convergence towards
one world-wide integrated mobility concept description.
The physical view describes the physical objects (systems and devices) and the information exchanges
that support ITS. The physical objects interact and exchange information and services. Physical objects are
[3]
defined to represent the major physical components of the ITS architecture .
The functional view addresses the analysis of abstract functional elements and their logical interactions. The
functional objects are allocated to the physical objects based on the analysis of the functional requirements
[3]
for each of the physical objects .
v
Technical Report ISO/TR 22625:2025(en)
Intelligent transport systems — Mobility integration —
Physical and functional view
1 Scope
This document describes the physical and functional views defined in ISO/TS 14812 on integrated mobility,
based on the role and responsibilities models in the mobility-as-a-service (MaaS) and mobility on demand
(MOD) ecosystems as described in ISO/TR 4447 and ISO/TR 7878.
This document focuses on mobility service concepts where the included transport services are publicly
available.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO/TR 7878, Intelligent transport systems — Mobility integration — Enterprise view
ISO/TS 14812, Intelligent transport systems — Vocabulary
ISO 24014-1, Public transport — Interoperable fare management system — Part 1: Architecture
3 Terms, definitions and abbreviated terms
For the purposes of this document, the terms and definitions given in ISO/TR 7878, ISO/TS 14812,
ISO 24014-1 and the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1 Terms and definitions
3.1.1
commercial rule
rule defining the settlement and commission between the enterprise objects involved in the provision of the
mobility services
Note 1 to entry: This definition is adapted from the definition of commercial rules in ISO 24014-1.
3.1.2
mobility service
service that provides an integrated interface for multiple transport services
Note 1 to entry: The integrated interface can include an online interface, a payment interface, and/or rules for
physically accessing the various transport services.
Note 2 to entry: The typical goal of a mobility service is to fulfil the needs of a transport user in an optimal fashion,
even if that requires using multiple transport services.
3.1.3
mobility service provider
entity that delivers one or more mobility services
3.1.4
mobility service product
specification of one single or two or more integrated transport services provided by the mobility service
provider and defined by usage rules, pricing rules and commercial rules
Note 1 to entry: A mobility service product can in many cases be regarded as a combination of transport service
products.
3.1.5
pricing rule
rule defining the price and payment/billing relationships to the mobility service user
Note 1 to entry: This definition is based on the definition of pricing rules in ISO 24014-1.
3.1.6
transport service product
specification of a transport service provided by the transport service provider and defined by usage rules,
pricing rules and commercial rules
3.2 Abbreviated terms
MSP mobility service provider
MSU mobility service user
TSP transport service provider
PSP payment service provider
TIO transport infrastructure operator
4 The core physical and functional objects in the provision of mobility services
4.1 General
The three core enterprise objects were described in ISO/TR 7878:
— Mobility service user (MSU) is the enterprise object that requests the mobility service, selects the
mobility service fulfilling the user needs and preferences, uses the service and pays for it. However, the
user responsibilities/activities can be divided between different persons, organisations, legal entities,
etc. This includes, for example, between the traveller using the mobility service and the entity paying for
the mobility service, such as a parent or employer.
— Mobility service provider (MSP) is the enterprise object that provides the MSU with access to the mobility
services fulfilling the user needs. The mobility services are based on the collected offers from transport
services and the optimisation of the different transport services that fulfils the user needs, e.g. fastest,
cheapest or most environmental-friendly combination of transport services.
— Transport service provider (TSP) is the enterprise object that owns and operates the transport means
used for the provision of transport services enabling the movement of goods and persons.
Between the enterprise objects there are two types of relationships:
— Agreement that describes the obligations and rights between two enterprise objects or a joint agreement
between several enterprise objects
— Expectations that describe what the different enterprise objects expect from each other, e.g. information,
services, and payments.
Figure 1 shows the main relationships between core enterprise objects described in ISO/TR 7878. The
system architecture used in ISO/TR 7878 and this document is based on Reference [3].
Key
ITS Central system class
ITS Personal system class
SOURCE ISO/TR 7878:2023, 6.1.1, modified — Symbol key added.
Figure 1 — Enterprise view for the three core enterprise objects
The physical view shows the physical objects, e.g. systems and devices, that enable the enterprise objects to
handle and provide information and services and to communicate with each other based on different types
of C-ITS communication.
Figure 2 shows an example on a physical and functional view.
Key
ITS Central system class
ITS Personal system class
Figure 2 — Example on Physical and functional view and object ITS classes and colour codes
The figure shows two physical objects: the MSP central system and the MSU personal equipment, e.g.
a smartphone. The enterprise objects and their relationships to the physical objects can optionally be
included in this type of diagram. The main functions of the physical objects are shown as grey boxes inside
the physical object boxes. The interface between the two physical objects in the example is defined by the
information flows between them.
The main concept of the physical and functional architecture is described by four use cases:
— the MSU requests, books, uses, and pays for the mobility service;
— the MSP manages and provides the mobility services;
— the TSP manages and provides the transport services;
— the TIO provides and operates the transport infrastructure used by the TSP.
Note that the functional objects and information flows between two enterprise objects can differ from one
use case to another. The rationale behind is that the Figures 3 to 6 would be overloaded with functional
objects and information flows if all use cases are shown in one and the same figure. The functional objects
and information flows have therefore been limited to the most relevant objects and flows for the different
use cases.
4.2 MSU requests, books, uses, and pays for the mobility service
4.2.1 Use case physical and functional objects
The use case is shown in Figure 3. The physical and functional objects are:
— MSU equipment
The function Manage and secure MSU data handles the MSU data where the username, address, age,
phone number, disability and user preferences are typical examples on user data. A typical example on
user preferences is that the user prefers specific travel means, favourite travel origin and destination,
and cheapest, fastest or most sustainable transport modes and means.
The function Manage and secure MSU Access rights handles the access rights received from the MSP. The
access rights could also be seen as one or more tickets ensuring the user access to the transport services
included in the mobility service.
The function Manage and secure MSU Payment means stores and secure the payment means used for
the payment of the mobility services, e.g. tokens, bank account or credit card data stored in the MSU
equipment.
— MSP central system
The function TSP, TIO and MSU data collection and analyses collects data from the TSP, TIO and MSU.
The data is used to analyse, prepare and present different alternatives for mobility services based on 1)
availability and status of transport services and transport infrastructure and; 2) user needs, user data
and user preferences.
The function Manage mobility services and access rights manages the TSP and TIO data enabling the MSP
to have an overview and register of the TSPs and their travel products (transport services) and the
TIOs and their transport infrastructure network and status of network nodes and links. Further, the
function enables the MSP to have an overview and register of access rights that MSP has sent to the MSU
equipment.
The function Inform MSU informs the MSU about the status of the transport services included in the
mobility service. The status, e.g. delays or cancellations, is based on the transport service status
message from the TSPs and from the TIOs.
The function Monitor transport service controls the execution of the provision of the transport services,
e.g. that the availability and reliability quality requirements are met.
The function manage transport services covers the function Manage MSP related claims and payments which
manages the claims and payment flows in the value network related to the use and provision of the mobility
service. For simplification reasons, not all the value flows in the value network are shown in Figure 3.
Key
ITS Central system class
ITS Field system class
ITS Personal system class
ITS Vehicle system class
ITS Support system class
NOTE For simplification reasons, the TIO input to the MSP Central system is left out in this diagram, but shown in
the use case Manage and operate transport infrastructure.
Figure 3 — MSU requests, books, uses and pays the mobility service
— TSP Central system
The function Manage TSP products supports the development, storage and distribution of the travel
products of the TSP. Examples on travel products (transport services) are a bus ride from A to B, rent-a-
bike, share-a-taxi and access to the road network in a geofences zone.
The function Manage bookings, capacity and discrepancies manages the bookings from the MSU via the
MSP, manages the capacity of the transport means fleet in relation to the bookings enabling the TSP to
deliver the booked travel products with the required quality and finally, to handle any discrepancy, e.g.
transport means breakdown, major delays and cancellations and transport infrastructure unwanted or
unexpected events.
The function Manage transport means enables the TSP to monitor the status and position of the transport
means operated by the TSP. A typical example is a fleet management system for buses.
The function Monitor transport service enables the TSP to control the quality of the transport services
provided, e.g. that the demand is less than the capacity and that the service level is found to be acceptable
by a certain percentage of the users.
The function manage TSP related claims and payments supports the TSP in handling the claims from
the TSP to the MSP for transport services provided based on the pricing rules, and payments from the
MSP or PSP depending on the value network established by the contractual framework between the
enterprise objects in the mobility service concept.
— TSP field equipment and TSP vehicle equipment
The functions Validate access rights allocated to the TSP field equipment and vehicle equipment validates
the access right carried by the MSU equipment, e.g., a mobile phone, smart card or On-board equipment
(OBE) in a vehicle. Examples on TSP field and vehicle equipment are gates at a metro station, validators
on-board a bus and gantries with short range communication equipment reading vehicle OBEs with
access rights to the transport infrastructure in a geofence zone in a city.
— Position support system
The function Position support supports the MSU equipment with position services, e.g. corrected
positions from Global Navigation Satellite Systems (GNSS) or from local positioning systems, e.g. in
tunnels or city valleys.
— PSP system
The function Support payment services supports the MSP, the MSU and the TSP with the claims and
payment handling by a value network with claim and payment flows. Not all claims and payment flows
are shown in Figure 3 for simplification reasons.
4.2.2 Use case interfaces
4.2.2.1 Interface between MSU Equipment and MSP Central system
The interface between the MSU equipment and the MSP Central system is described by the following
information flows:
— transport needs which carries information on the MSU needs, e.g., a travel from A to B, the user preferences
concerning transport means, preferred departure or arrival time in addition to the MSU data stored in
the MSU equipment. The MSU data can include information related to traveller birth date, walking speed,
disabilities, preferred class, benefits and discounts, preferred language, and payment means. The MSU
needs and data is collected by the MSP and used for finding one or more mobility services that fulfils the
user needs.
— transport options includes the MSP offer to the MSU. The offer can be one or more combinations of
transport services that moves the traveller from A to B. The combinations can, e.g. be offering the best
price, the fastest, the most sustainable travel and the best fit for disabled travellers.
— selected option and booking contains the MSU choice of option which enables the MSP to inform the TSP
about the booking and reserve the transport services, e.g. a seat on a train (if required), an el-scooter or
a shared car.
— access rights includes information that ensures the MSU access to the transport services that are
included in the mobility service. The access rights can be issued in many formats, preferably in electronic
formats, enabling the MSU to carry the access rights in the MSU equipment. Even if the access rights for
all transport services in the mobility service are electronically stored in the MSU equipment, the TSP
validators in the field equipment or vehicle equipment can differ and require separate formats on the
access rights.
— transport service update contains updated information on the mobility service based on status reports
from the TSPs and the TIO. Status reports from the TSP can include delays and cancelations, which again
could have an impact on the mobility service and its route, schedule, and transport means. Status repo
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...