ISO 22085-2:2021

INTERNATIONAL ISO
STANDARD 22085-2
First edition
2021-07
Intelligent transport systems (ITS) —
Nomadic device service platform for
micro mobility —
Part 2:
Functional requirements and dataset
definitions
Systèmes de transport intelligents - Plateforme de services de
dispositifs portables pour la micro mobilité - Partie 2 : Exigences
fonctionnelles et définitions des données —
Partie 2: Exigences fonctionnelles et définitions des données
Reference number
©
ISO 2021
© ISO 2021
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 © ISO 2021 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms, definitions, symbols and abbreviated terms . 1
3.1 Terms and definitions . 1
3.2 Abbreviated terms . 2
4 Document overview and structure . 3
5 General information . 3
5.1 Purpose . 3
5.2 Use case overview . 4
6 Functional requirements and dataset definition . 5
6.1 Functional requirements . 5
6.1.1 Functional requirements with related general use cases . 5
6.1.2 Functional requirements for the connectivity among P-ITS-S, MM and MMCS . 6
6.2 Dataset definitions . 6
6.2.1 Introduction . 6
6.2.2 Pre-trip . 6
6.2.3 En-route . 9
6.2.4 Post-trip .13
7 Dataset definitions .15
7.1 request-mm-status .15
7.2 mm-status-response .16
7.3 stop-notify-mm-status .16
7.4 notify-mm-service .16
7.5 stop-notify-mm-service .17
7.6 charging-station-information .17
7.7 parking-space-information .18
7.8 reservation-acceptance .18
7.9 public-transit-schedule .19
7.10 public-transit-reserved-information .19
7.11 navigation-route-information .20
7.12 traffic-information .20
7.13 accident-information .21
7.14 danger-zone-information .21
7.15 warning-message .22
7.16 toll-balance-information .22
7.17 disconnection-warning-message .23
7.18 return-information .24
7.19 payment-information .24
7.20 request-public-transit-schedule .25
7.21 request-public-transit-reservation .25
Bibliography .26
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 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.
A list of all parts in the ISO 22085 series can be found on the ISO website.
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 © ISO 2021 – All rights reserved

Introduction
Micro mobility can be defined as a small or compact-sized electric vehicle. Normally, it is designed to
be used as a first-mile and last-mile service connecting public transit routes or to provide personal
mobility with one or two passengers for a short-distance trip.
The nomadic device service platform aims to accommodate the specific needs of integrated mobility
services for either urban or rural areas. The service platform focuses on the use of data exchange
interface standards between micro mobility and nomadic devices to enable the development of cloud-
based ITS using wireless networks.
This document fosters the introduction of nomadic devices in the public transport and automotive
world. It specifies functional requirements and dataset definitions based on Vehicle Interface Data
Format (VIDF) at the application level regarding pre-trip, post-trip and while driving, in order to
identify connectivity between a user’s personal ITS stations (P-ITS-S, for example nomadic devices),
roadside-ITS-station, vehicle-ITS-station gateway (V-ITS-S) and central ITS station (C-ITS-S). The
functional requirements and the dataset can be used as a measure for exchanging information required
to implement mobility services to be included in integrated mobility and parcel delivery services.
INTERNATIONAL STANDARD ISO 22085-2:2021(E)
Intelligent transport systems (ITS) — Nomadic device
service platform for micro mobility —
Part 2:
Functional requirements and dataset definitions
1 Scope
This document provides definitions of functional requirements for connectivity among nomadic
devices, cloud servers and micro mobility during pre-trip, post-trip and while driving, which is defined
in ISO/TR 22085-1, and datasets for providing seamless mobility service. In addition, it also delivers
related standards required to develop and operate the service platform between a nomadic device and
micro mobility with intelligent transport systems (ITS) technologies. The functional requirements and
the datasets can be used as a measure of exchanging information required to promote micro mobility
as a new type of urban and rural transport mode, and so increase the possibility of being included in an
integrated mobility and parcel delivery system.
This document defines functional requirements and messages set by use case and a dataset of each
message to provide services for use cases, which are defined in ISO/TR 22085-1 as follows:
— Pre-trip (Use case 1.1-1.5)
— En-route (Use case 2.1-2.7)
— Post-trip (Use case 3.1-3.4)
2 Normative references
There are no normative references in this document.
3 Terms, definitions, symbols and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological 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.1
central ITS station
C-ITS-S
network server between personal ITS server (i.e. nomadic device or mobile device) and micro mobility
service provider
3.1.2
personal ITS station
P-ITS-S
implementation of an ITS station as a personal ITS subsystem (e.g. nomadic device or mobile device)
which provides communication connectivity via a wireless communication network (3G, 4G, and 5G),
mobile wireless broadband (WIMAX, HC-SDMA, etc.), WiFi and short-range links, such as Bluetooth,
Zigbee, etc. to connect portable devices to the motor vehicle communications system network
3.1.3
micro mobility
MM
new concept of eco-friendly personal electric vehicle for one or two passengers
3.1.4
in mobility network
IMN
local network bus among electrical control units in MM, providing diagnostics information to P-ITS-S
through vehicle-ITS-station gateway (V-ITS-S)
3.1.5
micro mobility service provider
MMSP
service provider including parking lot management service, public transit authority, charging station
management service, tolling service authority, car sharing service, traffic information service, etc.
3.1.6
micro mobility communication network
MMCN
communication network between P-ITS-S and C-ITS-S
3.1.7
public communication network
PCN
network between MMCS and service providers used to provide MM services information on, for
example, charging stations, parking lots and traffic congestion
3.2 Abbreviated terms
C conditional
Cvt. convention (M, O, C)
DTC diagnostic trouble code
EXE executor
FR functional requirement
IMN in mobility network
ITIPS interconnected transfer information providing service
ND nomadic device
M mandatory
MEC mobile edge computing
MM micro-mobility
2 © ISO 2021 – All rights reserved

MMCN micro mobility communication network
MMCS micro-mobility cloud server
MTS mobile tolling service
O optional
OBD on board diagnostic
PCN public communication network
R-ITS-S roadside-intelligent transport system-station
SOC state of charge
SAPSS searching available parking space service on the way
SMMRS shared micro mobility return service
V-ITS-S vehicle ITS station
WiFi wireless fidelity
4 Document overview and structure
This document provides all documents and references required to support the implementation of the
requirements related to standardized access to nomadic device service platforms for micro mobility.
This document consists of three sections:
— General information is provided in Clause 5.
Clause 5 provides a purpose and overview, including a service framework architecture.
— Functional requirements and messages set by use case are described in Clause 6.
Clause 6 specifies all use case technical requirements and datasets related to nomadic device
service platforms for micro mobility to be interfaced with micro mobility cloud servers and micro
mobility service providers. The requirements reflect functional requirements as specified in this
document.
— Datasets are described in Clause 7.
Clause 7 provides definitions of each message including message ID, dataset and data type.
5 General information
5.1 Purpose
This document addresses two major areas:
— Identification of the functional requirements for describing the P-ITS-S interfaced with V-ITS-S and
C-ITS-S (or MMCS).
— Definition of the message set required in the general use cases defined in ISO/TR 22085-1.
— Definition of the dataset of each message from the use cases.
5.2 Use case overview
Conceptual aspects of the general use cases of ISO/TR 22085-1 are shown in Figure 1 and are
summarized in Table 1.
Figure 1 — Conceptual aspects of the general use cases in ISO/TR 22085-1
Table 1 — Use cases clusters and associated use cases overview
Title of use cases cluster Brief description
1. Pre-trip This cluster specifies the detailed use cases at the pre-trip stage for micro mobil-
ity. It includes 5 different use cases, including MM information providing service,
navigation service linked information on charging stations, pre-scanning availa-
ble parking space service, micro mobility sharing service and micro mobility as
an integrated mobility service.
— UC 1.1 – Micro mobility information providing services
— UC 1.2 – Navigation service linked information on charging stations
— UC 1.3 – Pre-scanning available parking space services
— UC 1.4 – Micro mobility sharing services
— UC 1.5 – Micro mobility as an integrated mobility service
4 © ISO 2021 – All rights reserved

Table 1 (continued)
Title of use cases cluster Brief description
2. En-route This cluster specifies the detailed use cases at the en-route stage for micro
mobility. It includes 7 different use cases, including traffic information providing
service, micro mobility fault management service, mobile tolling service, adaptive
route management service, searching available parking space service on the way,
keyless go service for shared micro mobility and interconnected transfer infor-
mation providing service.
— UC 2.1 – Traffic information providing service
— UC 2.2 – Micro mobility status monitoring service
— UC 2.3 – Mobile tolling service
— UC 2.4 – Adaptive route management service
— UC 2.5 – Searching available parking space service on the way.
— UC 2.6 – Keyless go service for shared micro mobility
— UC 2.7 – Interconnected transfer information providing service
3. Post-trip This cluster specifies the detailed use cases at the post-trip stage for micro mobil-
ity. It includes 4 different use cases, including micro mobility driving information
providing service, charging station information service, parked micro mobility
position providing service and sharing micro mobility return service.
— UC 3.1 – Micro mobility driving information providing service
— UC 3.2 – Charging station information service
— UC 3.3 – Parked micro mobility position providing service
— UC 3.4 – Sharing micro mobility return service
6 Functional requirements and dataset definition
6.1 Functional requirements
This document provides functional requirements (FRs) for providing integrated mobility or postal
delivery services using a P-ITS-S, for instance, a nomadic device.
The FRs consist of connectivity, power supply, data collection and data storing for services provided in
pre-trip, post-trip, and en-route phases, and requirements for components of the service platform (i.e.,
P-ITS-S, V-ITS-S, C-ITS-S [or MMCS]).
6.1.1 Functional requirements with related general use cases
Table 2 — Functional requirements overview
FR# Description
FR1 IMN of MM provides V-ITS-S with status information (mileage, SOC, DTC) of MM.
FR2 V-ITS-S provides P-ITS-S with status information of MM.
FR3 P-ITS-S provides status information of MM to a driver.
FR4 P-ITS-S sends location information along with MM status to C-ITS-S.
FR5 P-ITS-S should always be in V2N (vehicle-to-network) with MM.
C-ITS-S manages all MM-related information (e.g. charging station, parking space, navigation route
FR6
information, toll balance information).
FR7 C-ITS-S stores MM driving information and calculates balance after driving.
6.1.2 Functional requirements for the connectivity among P-ITS-S, MM and MMCS
6.1.2.1 P-ITS-S
The P-ITS-S is always interfaced with the V-ITS-S via a wireless communication link.
6.1.2.2 MM
MM should include interfaces which can transfer the MM’s information to the P-ITS-S and the MMCS.
6.1.2.3 C-ITS-S (or MMCS)
The C-ITS-S (or MMCS) should be able to store and accumulate information related to the MM’s status.
The C-ITS-S (or MMCS) should include interfaces through which data can be exchanged between the
C-ITS-S and public service providers (e.g. car sharing service, etc.).
6.2 Dataset definitions
6.2.1 Introduction
This document provides dataset definitions which contain required data and the required data type for
each use case defined in ISO/TR 22085-1, in order to provide integrated mobility or a postal delivery
service.
6.2.2 Pre-trip
6.2.2.1 General
The following subclauses define datasets in the pre-trip phase, including information on vehicle
identification, location and status, which is provided to an MM driver through a P-ITS-S.
6.2.2.2 UC 1.1 Micro mobility information providing service
Use case 1.1 requires a dataset containing the status information of the MM. When the MM is chosen,
V-ITS-S-ID and status information of the MM and an MM driver’s P-ITS-S identification is transferred
to a C-ITS-S (or MMCS) for providing services in use case 1.1. Table 3 shows data, data type and a
description of the dataset required for use case 1.1.
Table 3 — Dataset definition for use case 1.1
Micro mobility (MM) identification (V-ITS-S-ID) and
Cluster 1- Pre-trip
status information such as SOC, DTC is provided to MM
driver, who utilizes it to decide to choose the MM or not.
Name UC 1.1 — Micro mobility informa-
tion providing service
Subclause Name Exe Description
request-mm-status
7.1 P Request that V-ITS-S notifies MM status with SOC, DTC,
mileage and V-ITS-S-ID.
mm-status-response
7.2 V Send MM status information (SOC, DTC, mileage) to P-ITS-S.
stop-notify-mm-status
7.3 P Stop the communication to the V-ITS-S.
notify-mm-service
7.4 P Send MM status information, V-ITS-S-ID, position and user
information to C-ITS-S. After the first contact, send only
the P-ITS-S position and MM status information, V-ITS-
S-ID, in a predefined time interval.
stop-notify-mm-service
7.5 P Stop the communication to the C-ITS-S.
6 © ISO 2021 – All rights reserved
Messages Use case
6.2.2.3 UC 1.2 Navigation service linked information on charging station
Use case 1.2 requires a dataset to provide routes-linked information on charging station to an MM
driver. When a destination is set, the C-ITS-S (or MMCS) collects information on expected routes for
the MM and locations of charging stations. Then, the C-ITS-S (or MMCS) transfers them to the P-ITS-S.
Information on locations of charging stations includes charging stations on the way to or nearest to the
destination. Table 4 shows data, data type and a description of the dataset required for use case 1.2.
Table 4 — Dataset definition for use case 1.2
The route to destination is guided with the charging
Cluster 1- Pre-trip
station information on a P-ITS-S. The location of the
Name UC 1.2 — Navigation service linked
charging station can include that which is nearest to
information on charging station
the destination, or one on the way to the destination.
Sub- Name Exe Description
clause
request-mm-status
7.1 P Request that V-ITS-S notifies MM status with SOC, DTC,
mileage and V-ITS-S-ID.
mm-status-response
7.2 V Send MM status information (SOC, DTC, mileage) to
P-ITS-S.
stop-notify-mm-status
7.3 P Stop the communication to the V-ITS-S.
notify-mm-service
7.4 P Send MM status information, V-ITS-S-ID, position and
user information to C-ITS-S. After the first contact, send
only the P-ITS-S position and MM status information,
V-ITS-S-ID, in a predefined time interval.
charging-station-
7.6 C Send charging station location to the P-ITS-S.
information
navigation-route-
7.11 C Send navigation route information to the P-ITS-S.
information
stop-notify-mm-service
7.5 P Stop the communication to the C-ITS-S.
6.2.2.4 UC 1.3 Pre-scanning available parking space service
Use case 1.3 requires a dataset for providing information to an MM driver in pre-trip phase on available
parking spaces near to the destination. The C-ITS-S (or MMCS) transfers the information on available
parking spaces near to the destination to the P-ITS-S. Table 5 shows data, data type and a description of
the dataset required for use case 1.3.
Table 5 — Dataset definition for use case 1.3
Prior to driving, available parking space information
Cluster 1- Pre-trip
near to the destination is scanned and provided on the
Name UC 1.3 — Pre-scanning available
P-ITS-S, related with the navigation service defined in
parking space service
UC 1.3.
Use Case Messages Use Case
Table 5 (continued)
Sub- Name Exe Description
clause
request-mm-status
7.1 P Request that V-ITS-S notifies MM status with SOC, DTC,
mileage and V-ITS-S-ID.
mm-status-response
7.2 V Send MM status information (SOC, DTC and mileage) to
P-ITS-S.
stop-notify-mm-status
7.3 P Stop the communication to the V-ITS-S.
notify-mm-service
7.4 P Send MM status information, V-ITS-S-ID, position and
user information to C-ITS-S. After the first contact, send
only the P-ITS-S position and MM status information,
V-ITS-S-ID, in a predefined time interval.
parking-space-information
7.7 C Send available parking space information to the
P-ITS-S.
navigation-route-
7.11 C Send navigation route information to the P-ITS-S.
information
stop-notify-mm-service
7.5 P Stop the communication to the C-ITS-S.
6.2.2.5 UC 1.4 Micro mobility sharing service
Use case 1.4 requires a dataset to provide information related to the MM sharing service. Information
related to searching available MM, reservation and payment is transferred to a C-ITS-S (or MMCS).
Table 6 shows data, data type and a description of the dataset required for use case 1.4.
Table 6 — Dataset definition for use case 1.4
Reserves MM for sharing service and displays reserved
Cluster 1- Pre-trip
information on a P-ITS-S.
Name UC 1.4 — Micro mobility sharing
Available MM information is provided by a C-ITS-S (or
service
MMCS).
Sub- Name Exe Description
clause
request-mm-status
7.1 P Request that V-ITS-S notifies MM status with SOC, DTC,
mileage and V-ITS-S-ID.
mm-status-response
7.2 V Send MM status information (SOC, DTC, mileage) to
P-ITS-S.
stop-notify-mm-status
7.3 P Stop the communication to the V-ITS-S.
notify-mm-service
7.4 P Send MM status information, V-ITS-S-ID, position and
user information to C-ITS-S. After the first contact,
send only the P-ITS-S position and MM status informa-
tion, V-ITS-S-ID, in a predefined time interval.
reservation-acceptance
7.8 C Send reservation acceptance information to the
P-ITS-S.
stop-notify-mm-service
7.5 P Stop the communication to the C-ITS-S.
6.2.2.6 UC 1.5 Micro mobility as an integrated mobility service
Use case 1.5 requires a dataset to provide information to an MM driver which is related to transferring
to public transportation before/after using MM. The C-ITS-S (or MMCS) transfers information to
P-ITS-S. Concerning transferable public transportation and available stations related to the MM driver’s
destination. Table 7 shows data, data type and a description of the dataset required for use case 1.5.
8 © ISO 2021 – All rights reserved
Messages Use Case Messages
Table 7 — Dataset definition for use case 1.5
Provides interconnected public transit transfer infor-
Cluster 1- Pre-trip
mation to MM driver on the P-ITS-S.
Name UC 1.5 — Micro mobility as an inte-
grated mobility service
Sub- Name Exe Description
clause
request-mm-status
7.1 P Request that V-ITS-S notifies MM status with SOC, DTC,
mileage and V-ITS-S-ID
mm-status-response
7.2 V Send MM status information (SOC, DTC, mileage) to the
P-ITS-S.
stop-notify-mm-status
7.3 P Stop the communication to the V-ITS-S.
notify-mm-service
7.4 P Send MM status information, V-ITS-S-ID, position and
user information to C-ITS-S. After the first contact, send
only the P-ITS-S position and MM status information,
V-ITS-S-ID, in a predefined time interval.
public-transit-schedule
7.9 C Send public transit information with arrival/departure
time and transit type to P-ITS-S.
stop-notify-mm-service
7.5 P Stop the communication to the C-ITS-S.
6.2.3 En-route
6.2.3.1 General
The following subclauses define datasets in the en-route phase, including information on MM operation
and traffic in the surrounding area, which is provided to an MM driver and a C-ITS-S (or MMCS) through
a P-ITS-S.
6.2.3.2 UC 2.1 Traffic information providing service
Use case 2.1 requires a dataset to provide information to an MM driver relating to traffic around the
MM while driving. The P-ITS-S transfers route information to the C-ITS-S (or MMCS). That C-ITS-S (or
MMCS) then transfers traffic information around the route to an MM driver through P-ITS-S. Table 8
shows data, data type and a description of the dataset required for use case 2.1.
Table 8 — Dataset definition for use case 2.1
While driving, traffic information is provided by a
Cluster 2- En-route
C-ITS-S (or MMCS) in real time. To provide traffic
Name UC 2.1 — Traffic information pro-
information, route information on a P-ITS-S is sent to a
viding service
C-ITS-S (or MMCS). Then, a C-ITS-S (or MMCS) requests
the relevant traffic information provider through a PCN.
Sub- Name Exe Description
clause
notify-mm-service
7.4 P Send MM status information, V-ITS-S-ID, position and user
information to C-ITS-S. After the first contact, send only
the P-ITS-S position and MM status information, V-ITS-S-
ID, in a predefined time interval.
traffic-information
7.12 C Send traffic information to the P-ITS-S.
accident-information
7.13 C Send accident location information to the P-ITS-S.
danger-zone-information
7.14 C Send danger zone location information to the P-ITS-S.
stop-notify-mm-service
7.5 P Stop the communication to the C-ITS-S.
Messages Use Case Messages Use Case

6.2.3.3 UC 2.2 Micro mobility status monitoring service
Use case 2.2 requires a dataset to provide information to an MM driver when a fault or a malfunction
occurs in an MM while driving. A V-ITS-S transfers information to a P-ITS-S in a case of malfunction in
the MM. Table 9 shows data, data type and a description of the dataset required for use case 2.2.
Table 9 — Dataset definition for use case 2.2
MM diagnostic information is provided to a driver by
Cluster 2- En-route
V-ITS-S while driving when a major electrical com-
Name UC 2.2 — Micro mobility status
ponent such as the invertor, battery, etc. is in fault or
monitoring service
malfunction status. To provide MM DTC information,
the V-ITS-S broadcasts DTC information to the P-ITS-S.
Sub- Name Exe Description
clause
request-mm-status
7.1 P Request that the V-ITS-S notifies MM status with SOC,
DTC, mileage and V-ITS-S-ID.
mm-status-response
7.2 V Send MM status information (SOC, DTC, mileage) to P-ITS-S.
stop-notify-mm-status
7.3 P Stop the communication to the V-ITS-S.
notify-mm-service
7.4 P Send MM status information, V-ITS-S-ID, position, and
user information to C-ITS-S. After the first contact, send
only the P-ITS-S position and MM status information,
V-ITS-S-ID, in a predefined time interval.
warning-message
7.15 C Send warning message containing corresponding DTC
description information to the P-ITS-S.
stop-notify-mm-service
7.5 P Stop the communication to the C-ITS-S.
6.2.3.4 UC 2.3 Mobile tolling service
Use case 2.3 requires a dataset to provide toll payment information to an MM driver when an MM
drives through a toll gate. A toll service provider and a payment service provider transfer the payment
information to the P-ITS-S. Table 10 shows data, data type and a description of the dataset required for
use case 2.3.
Table 10 — Dataset definition for use case 2.3
Cluster 2- En-route Toll payment is requested through a C-ITS-S (or MMCS)
when the MM passes toll roads. MTS is provided to MM
Name UC 2.3 — Mobile tolling service
driver by the combination of following service provid-
ers, such as payment service provider, communication
service operator, and toll road management service
provider.
Chapter Name Exe Description
request-mm-status
7.1 P Request that V-ITS-S notifies MM status with SOC, DTC,
mileage, V-ITS-S-ID.
mm-status-response
7.2 V Send MM status information (SOC, DTC, mileage) to the
P-ITS-S.
stop-notify-mm-status
7.3 P Stop the communication to the V-ITS-S.
notify-mm-service
7.4 P Send MM status information, V-ITS-S-ID, position and user
information to C-ITS-S. After the first contact, send only
the P-ITS-S position and MM status information, V-ITS-
S-ID, in a predefined time interval.
toll-balance-information
7.16 C Send toll balance information to the P-ITS-S.
payment-information
7.19 P Send the user’s payment information to the C-ITS-S.
stop-notify-mm-service
7.5 P Stop the communication to the C-ITS-S.
10 © ISO 2021 – All rights reserved
Messages Use Case Messages Use Case

6.2.3.5 UC 2.4 Adaptive route management service
Use case 2.4 requires a dataset to provide new route information to an MM driver when an MM deviates
from a route set in a pre-trip phase. A P-ITS-S transfers information related to the MM’s current location
to a C-ITS-S (or MMCS). That C-ITS-S (or MMCS) then transfers new route information to P-ITS-S, taking
into consideration the surrounding traffic and locations of charging stations. Table 11 shows data, data
type and a description of the dataset required for use case 2.4.
Table 11 — Dataset definition for use case 2.4
Cluster 2- En-route New route to destination is provided by MMCS when
MM deviates from a planned route while driving. To
Name UC 2.4 — Adaptive route manage-
suggest a new route to destination, the C-ITS-S (or
ment service
MMCS) receives traffic condition and charging station
information from relevant service providers. Then, the
C-ITS-S (or MMCS) sends the information to the P-ITS-S.
Sub- Name Exe Description
clause
request-mm-status
7.1 P Request that V-ITS-S notifies MM status with SOC, DTC,
mileage and V-ITS-S-ID.
mm-status-response
7.2 V Send MM status information (SOC, DTC, mileage) to the
P-ITS-S.
stop-notify-mm-status
7.3 P Stop the communication to the V-ITS-S.
notify-mm-service
7.4 P Send MM status information, V-ITS-S-ID, position, and
user information to C-ITS-S. After the first contact, send
only the P-ITS-S position and MM status information,
V-ITS-S-ID, in a predefined time interval.
charging-station-
7.6 C Send charging station location to the P-ITS-S.
information
navigation-route-
7.11 C Send navigation route information to the P-ITS-S.
information
stop-notify-mm-service
7.5 P Stop the communication to the C-ITS-S.
6.2.3.6 UC 2.5 Searching available parking space service on the way
Before an MM arrives at a destination, use case 2.5 requires a dataset to provide information on
available parking spaces near to an MM driver and a driving route can be recalculated if necessary.
The C-ITS-S (or MMCS) transfers information on available parking spaces near to a destination to the
P-ITS-S automatically. Table 12 shows data, data type and a description of the dataset required for use
case 2.5.
Table 12 — Dataset definition for use case 2.5
Cluster 2- En-route Before MM approaches its destination, available
parking space information near to the destination is
Name UC 2.5 — Searching available park-
searched and provided on the P-ITS-S. If necessary, nav-
ing space service on the way
igation routes can be re-searched according to available
parking spaces. SAPSS automatically requests to search
available parking spaces near to the destination.
Use Case Messages Use Case
Table 12 (continued)
Sub- Name Exe Description
clause
request-mm-status
7.1 P Request that V-ITS-S notifies MM status with SOC, DTC,
mileage, V-ITS-S-ID.
mm-status-response
7.2 V Send MM status information (SOC, DTC, mileage) to the
P-ITS-S.
stop-notify-mm-status
7.3 P Stop the communication to the V-ITS-S.
notify-mm-service
7.4 P Send MM status information, V-ITS-S-ID, position, and
user information to C-ITS-S. After the first contact, send
only the P-ITS-S position and MM status information,
V-ITS-S-ID, in a predefined time interval.
parking-space-information
7.7 C Send available parking space information to the
P-ITS-S.
navigation-route-
7.11 C Send navigation route information to the P-ITS-S.
information
stop-notify-mm-service
7.5 P Stop the communication to the C-ITS-S.
6.2.3.7 UC 2.6 Keyless go service for shared micro mobility
When MM is disconnected from P-ITS-S while driving, use case 2.6 requires dataset to lock the MM.
When MM is disconnected from P-ITS-S, a warning message is transferred to P-ITS-S. Table 13 shows
data, data type and a description of the dataset required for use case 2.6.
Table 13 — Dataset definition for use case 2.6
The V-ITS-S locks MM automatically when the P-ITS-S
Cluster 2- En-route
is disconnected with the V-ITS-S. A warning message is
Name UC 2.6 — Keyless go service for
displayed on the P-ITS-S and is sent to the C-ITS-S (or
shared micro mobility
MMCS) simultaneously when the P-ITS-S is disconnect-
ed with the V-ITS-S.
Sub- Name Exe Description
clause
request-mm-status
7.1 P Request that V-ITS-S notifies MM status with SOC, DTC,
mileage and V-ITS-S-ID.
mm-status-response
7.2 V Send MM status information (SOC, DTC, mileage) to P-ITS-S
notify-mm-service
7.4 P Send MM status information, V-ITS-S-ID, position and user
information to C-ITS-S. After the first contact, send only
the P-ITS-S position and MM status information, V-ITS-
S-ID, in a predefined time interval.
disconnection-warning-
7.17 P A message of disconnection occurrence is sent to the
message
P-ITS-S while the driver is away from the MM.
stop-notify-mm-service
7.5 P Stop the communication to the C-ITS-S.
6.2.3.8 UC 2.7 Interconnected transfer information providing service
After an MM is parked, use case 2.7 requires a dataset to provide information to an MM driver concerning
available public transportation services from a parking space to a destination and reservation of this
service. C-ITS-S (or MMCS) transfers information on the available public transportation service and
reservation of the service, which is provided by a public transportation service provider, to the P-ITS-S.
Table 14 shows data, data type and a description of the dataset required for use case 2.7.
12 © ISO 2021 – All rights reserved
Messages Use Case Messages
Table 14 — Dataset definition for use case 2.7
ITIPS provides interconnected transfer information
Cluster 2- En-route
and notification of reserved transit mode information.
Name UC 2.7 — Interconnected transfer
information providing service
Sub- Name Exe Description
clause
request-mm-status
7.1 P Request that V-ITS-S notifies MM status with SOC, DTC,
mileage and V-ITS-S-ID.
mm-status-response
7.2 V Send MM status information (SOC, DTC, mileage) to P-ITS-S.
stop-notify-mm-status
7.3 P Stop the communication to the V-ITS-S.
notify-mm-service
7.4 P Send MM status information, V-ITS-S-ID, position and user
information to the C-ITS-S. After the first contact, send
only the P-ITS-S position and MM status information,
V-ITS-S-ID, in a predefined time interval.
request-public-transit-
7.20 P Request public transit schedule.
schedule
public-transit-schedule
7.9 C Send public transit information with arrival/departure
time and transit type to the P-ITS-S.
request-public-transit-
7.21 P Make public transit reservation if necessary.
reservation
public-transit-reserved-
7.10 C Send reservation information to a nomadic device (P-ITS-S).
information
stop-notify-mm-service
7.5 P Stop the communication to the C-ITS-S.
6.2.4 Post-trip
6.2.4.1 General
The following subclauses define datasets in the post-trip phase, including information on vehicle
operation after driving, which is provided to an MM driver and a C-ITS-S (or MMCS) through a P-ITS-S.
6.2.4.2 UC 3.1 Micro mobility driving information providing service
Use case 3.1 requires a dataset to provide information to an MM driver concerning an identification,
location, status and driving record of an MM, and green mileage points. The driving record is saved in
a C-ITS-S (or MMCS) with the MM’s identification and the P-ITS-S’s identification. Table 15 shows data,
data type and a description of the dataset required for use case 3.1.
Table 15 — Dataset definition for use case 3.1
P-ITS-S displays trip and MM status information after
Cluster 3- Post-trip
driving.
Name UC 3.1—Micro mobility driving
information providing service
Use Case Messages Use Case
Table 15 (continued)
Chapter Name Exe Description
request-mm-status
7.1 P Request that V-ITS-S notifies MM status with SOC, DTC,
mileage and V-ITS-S-ID.
mm-status-response
7.2 V Send MM status information (SOC, DTC, mileage) to P-ITS-S.
stop-notify-mm-status
7.3 P Stop the communication to the V-ITS-S.
notify-mm-service
7.4 P Send MM status information, V-ITS-S-ID, position and user
information to the C-ITS-S. After the first contact, send
only the P-ITS-S position and MM status information,
V-ITS-S-ID, in a predefined time interval.
stop-notify-mm-service
7.5 P Stop the communication to the C-ITS-S.
6.2.4.3 UC 3.2 Charging station information service
Use case 3.2 requires a da
...