Intelligent transport systems — Wide area communication — Protocol management information

ISO 15662:2006 provides information as a checklist to consider handling messages that are defined by the application working groups of ISO/TC204, installing systems and selecting suitable wide area communication systems for providing ITS application services.

Systèmes de transport intelligents — Communication étendue — Protocole de gestion de l'Information

General Information

Status
Published
Publication Date
03-Dec-2006
Current Stage
9060 - Close of review
Start Date
04-Mar-2026
Ref Project

Buy Standard

Standard
ISO 15662:2006 - Intelligent transport systems -- Wide area communication -- Protocol management information
English language
34 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 15662
First edition
2006-12-15

Intelligent transport systems — Wide area
communication — Protocol management
information
Systèmes de transport intelligents — Communication étendue —
Protocole de gestion de l'Information




Reference number
ISO 15662:2006(E)
©
ISO 2006

---------------------- Page: 1 ----------------------
ISO 15662:2006(E)
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.


©  ISO 2006
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.org
Web www.iso.org
Published in Switzerland

ii © ISO 2006 – All rights reserved

---------------------- Page: 2 ----------------------
ISO 15662:2006(E)
Contents Page
Foreword. iv
Introduction . v
1 Scope . 1
2 Normative references . 2
3 Terms and definitions. 2
4 Requirements for protocol management information items. 2
4.1 Selection of communication system . 2
4.2 Application identifiers . 8
4.3 Address. 9
4.4 Priority . 11
4.5 Security. 12
4.6 Application execution. 14
Annex A (normative) Protocol management information structure . 17
Annex B (normative) Protocol management information data type definition. 18
Annex C (informative) Protocol management information usage. 21
Annex D (informative) Extracting protocol management information items . 32
Bibliography . 34

© ISO 2006 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO 15662:2006(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
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.
ISO 15662 was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.
iv © ISO 2006 – All rights reserved

---------------------- Page: 4 ----------------------
ISO 15662:2006(E)
Introduction
Most of the application services in the ITS sector use a variety of wide area communication systems in order
to connect user terminals and “Service Centres”. In addition, the application services that are currently being
provided connect specific user terminals to specific service centres using specific wide area communications
systems. In other words, the various conditions that must be established to provide services are fixed.
However, when the future modes of service use are considered, it is assumed that a user will utilize the same
terminal to access “Service Centre A” in some cases and “Service Centre B” in other cases. It can also be
assumed that in some cases the user may be on foot and in others he or she may be travelling in a vehicle. It
can also be assumed that some users may access the service centre from “smart phones”, while others may
do so from navigation systems, while still others may do so using interactive TVs.
When a variety of user terminals use a variety of wide area communications systems to connect to a variety of
service centres in this manner, the type and content of the conditions that must be established will differ for
each individual service usage. In order to provide appropriate service based on these conditions, it is crucial to
establish a mechanism by which the type of conditions and the content established for them are transmitted to
an appropriate entity and interpreted.
This International Standard summarizes information as a checklist to consider internal processing in
communication systems, terminals and so forth (“protocol management information”) suitable for providing ITS
application services utilizing wide area communication systems.
© ISO 2006 – All rights reserved v

---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO 15662:2006(E)

Intelligent transport systems — Wide area communication —
Protocol management information
1 Scope
This International Standard provides information as a checklist to consider handling messages that are
defined by the application working groups of ISO/TC 204, installing systems and selecting suitable wide area
communication systems for providing ITS application services.
The usages of this information are for frameworks of message headers, pay load items for initializing
communication links, checklists for system design and so on. Thus, these information items are not
necessarily contained in message instances and/or headers that are actually transmitted.
For example, this information is used to organize the characteristics of messages such as those requesting
hand-over based on the relationship between the size of the information service area and the communication
range of each communication system (see Figure 1).

Figure 1 — Scope of 15662 (in the architecture of ISO/TC 204/WG 16)
© ISO 2006 – All rights reserved 1

---------------------- Page: 6 ----------------------
ISO 15662:2006(E)
2 Normative references
The following referenced documents are indispensable for the application 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 14817, Transport information and control systems — Requirements for an ITS/TICS central Data Registry
and ITS/TICS Data Dictionaries
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 14817 and the following apply.
3.1
protocol management information
information as a checklist to consider handling messages that are defined by the application working groups of
ISO/TC 204, installing systems and selecting suitable wide area communication systems for providing ITS
application services
NOTE Protocol management information items are not necessarily contained in message instances and/or headers
that are actually transmitted.
4 Requirements for protocol management information items
Protocol management information is defined as follows and its structure is described in Annex A. Each item is
defined in the abstract, so it does not specify location and time reference manner, granularity and so on. If
some service providers use them for message headers, they shall define the code strictly.
4.1 Selection of communication system
This information is for selecting the wide area communication system to be used for the response in
accordance with the requirements for executing the application service, the usage environment of the service
user, the status of the user terminal and so forth.
4.1.1 Responsiveness
4.1.1.1 Descriptive name
ProtocolManagementInformation. responsiveness
4.1.1.2 ASN.1 object identifier
{iso(1) standard(0) iso15662(15662) protocolManagementInformation(1)
selectionOfCommunicationSystem(1) responsiveness(1)}
4.1.1.3 Definition
This information represents the response speed and allowed delay time while receiving services in terms of
whether response will take place in real time and how much delay time will be allowed.
In cases where response time is conditioned for executing application services, the wide area communication
system shall be selected in accordance with the required response time, and this information can be used to
make such assessment. Furthermore, in case of receiving information in an “on demand” mode, this
information indicates the time from request until reception, for emergency bulletins, it indicates the time until
the information reaches the other party, and for transportation support and the like, it indicates the time until
forward road status, pavement status or other services are completed.
2 © ISO 2006 – All rights reserved

---------------------- Page: 7 ----------------------
ISO 15662:2006(E)
The following depict some examples of categories:
⎯ Within 1 second,
⎯ Within 30 seconds,
⎯ Within 1 minute,
⎯ Within 15 minutes,
⎯ 15 minutes or longer.
In addition, the required response time may be concretely specified as necessary.
4.1.1.4 Descriptive name context
“Protocol management information”.
4.1.1.5 Data concept type
Data element concept.
4.1.2 Directionality
4.1.2.1 Descriptive name
ProtocolManagementInformation. directionality
4.1.2.2 ASN.1 object identifier
{iso(1) standard(0) iso15662(15662) protocolManagementInformation(1)
selectionOfCommunicationSystem(1) directionality(2)}
4.1.2.3 Definition
This information indicates the combinations of unidirectional or bidirectional and symmetric or asymmetric with
respect to transmission and reception of information.
In cases where the directionality of communications (unidirectional, interactive, etc.) is needed to execute
application services, the wide area communication system shall be selected in accordance with the type of
communication (unidirectional or bidirectional, symmetric or asymmetric), and this information can be used to
make such assessment. Furthermore, interactive indicates cases where a response is expected to a given
message, while unidirectional indicates cases where a response is not expected to a message.
The following depict combination examples:
⎯ Unidirectional: In the case of an uplink, this corresponds to information provided from the vehicle such as
emergency bulletins. In the case of a downlink, it corresponds to cases in which the service user cannot
(or does not need to) make a request in order for the service provider to make the decision to start
service.
⎯ Interactive-symmetric: When service begins in response to a request from the service user and the
amount of data being transmitted and data being received is almost equal.
⎯ Interactive-asymmetric (large uplink): When service begins in response to a request from the service user
and when the amount of data being transmitted is greater than the amount of data being received.
⎯ Interactive-asymmetric (large downlink): When service begins in response to a request from the service
user and when the amount of data being received is greater than the amount of data being transmitted.
© ISO 2006 – All rights reserved 3

---------------------- Page: 8 ----------------------
ISO 15662:2006(E)
4.1.2.4 Descriptive name context
“Protocol management information”.
4.1.2.5 Data concept type
Data element concept.
4.1.3 Usage environment
4.1.3.1 Descriptive name
ProtocolManagementInformation. usageEnvironment
4.1.3.2 ASN.1 object identifier
{iso(1) standard(0) iso15662(15662) protocolManagementInformation(1)
selectionOfCommunicationSystem(1) usageEnvironment(3)}
4.1.3.3 Definition
This information represents the combination of the means of transportation when using services and the
speed of movement when receiving services.
Depending on the usage environment of the service user, the requirements for responsiveness and
directionality may not be met in some cases. For this reason, the wide area communication system shall be
selected in accordance with the means of transportation, speed of movement and other usage environment
factors, and this information can be used for making such assessment.
The following depict examples of categories by means of transportation:
⎯ Vehicle: In the case of driving a vehicle;
⎯ Public transportation: In the case of riding on public transportation;
⎯ Pedestrians: In the case of being on foot or on a bicycle;
⎯ Other categories: Bicycle, Motorcycle, Moped, Car, Truck, Emergency vehicle, Bus, Tram, Train, Ferry,
Taxi, etc.
The following indicate examples of categories by speed of movement:
⎯ Fast: In the case of travelling on expressways, case of travelling on a railroad (60-350 km/h);
⎯ Medium speed: In the case of travelling on ordinary roads (20-60 km/h);
⎯ Slow: In the case of travelling slowly at speeds at which it is possible to stop quickly (less than 20 km/h);
⎯ Stopped: In the case of not being in motion.
In addition, the speed may be more precisely specified as necessary.
4.1.3.4 Descriptive name context
“Protocol Management Information”.
4 © ISO 2006 – All rights reserved

---------------------- Page: 9 ----------------------
ISO 15662:2006(E)
4.1.3.5 Data concept type
Data element concept.
4.1.4 Service (provision) area
4.1.4.1 Descriptive name
ProtocolManagementInformation. serviceArea
4.1.4.2 ASN.1 object identifier
{iso(1) standard(0) iso15662(15662) protocolManagementInformation(1)
selectionOfCommunicationSystem(1) serviceArea(4)}
4.1.4.3 Definition
This information represents the range/areas at which users receive services and the need for continuity.
In cases where a service area and the continuity of this area and other conditions are required to use
application services, the wide area communication system shall be selected to match the areas in which
service can be provided, and this information can be used to make such assessment.
The following depict examples of categories for continuity:
⎯ Continuous area designation: When the area in which service is provided shall be continuous and users
shall be able to use the service anywhere (this can be broken down into two types: “area-wide continuity”
covering an entire area and “linear continuity” limited to a specific route);
⎯ Non-continuous: When service can only be used in specific non-continuous locations.
In addition, positional information of the range and areas at which services are provided are specified as the
range/areas (see Figure 2).

Key
1 area in which service is provided
Figure 2 — Service provision areas
© ISO 2006 – All rights reserved 5

---------------------- Page: 10 ----------------------
ISO 15662:2006(E)
4.1.4.4 Descriptive name context
“Protocol management information”.
4.1.4.5 Data concept type
Data element concept.
4.1.5 Service (provision) time
4.1.5.1 Descriptive name
ProtocolManagementInformation. serviceTime
4.1.5.2 ASN.1 object identifier
{iso(1) standard(0) iso15662(15662) protocolManagementInformation(1)
selectionOfCommunicationSystem(1) serviceTime(5)}
4.1.5.3 Definition
This information represents the information service starting time, service ending time and the continuity of
service time.
When the conditions relating to communication connection time for use of application services are required,
the wide area communication system must be selected to match the service time, and this information can be
used to make such assessment.
The following depict examples of categories:
⎯ Start and end times: In the case of specifying the times that information service starts and ends;
⎯ Start time: In the case of specifying the time that information service starts;
⎯ End time: In the case of specifying the time that information service ends;
⎯ Continuous: In the case of specifying that information is provided continuously.
In addition, time is also specified as necessary.
4.1.5.4 Descriptive name context
“Protocol management information”.
4.1.5.5 Data concept type
Data element concept.
4.1.6 Bandwidth
4.1.6.1 Descriptive name
ProtocolManagementInformation. bandwidth
6 © ISO 2006 – All rights reserved

---------------------- Page: 11 ----------------------
ISO 15662:2006(E)
4.1.6.2 ASN.1 object identifier
{iso(1) standard(0) iso15662(15662) protocolManagementInformation(1)
selectionOfCommunicationSystem(1) bandwidth(6)}
4.1.6.3 Definition
This information represents the transmission ability in terms of the transmission capacity and format (text,
audio, simple graphic, still image, video) required by the information to be provided.
Depending on the amount of information to be transmitted and the format of the data involved in the use of
application services, the conditions for responsiveness and data format, etc. may not be satisfied in some
cases. Accordingly, the wide area communication system shall be selected to match the transmission capacity,
data format and other aspects of transmission ability, and this information can be used to make such
assessment.
The following depict examples of describing transmission capacity and data format:
⎯ Transmission capacity: Described according to the required transmission speed (bps);
⎯ Format: Text, audio, simple graphic, still image, video, other special format which can describe the data
volume.
4.1.6.4 Descriptive name context
“Protocol management information”.
4.1.6.5 Data concept type
Data element concept.
4.1.7 Connection cost
4.1.7.1 Descriptive name
ProtocolManagementInformation. connectionCost
4.1.7.2 ASN.1 object identifier
{iso(1) standard(0) iso15662(15662) protocolManagementInformation(1)
selectionOfCommunicationSystem(1) connectionCost(7)}
4.1.7.3 Definition
This information represents the communication cost requirements for providing information.
When conditions relating to communication connection costs (upper limit, etc.) for use of application services
are required, the wide area communication system shall be selected to match the cost requirements, and this
information can be used to make such assessment.
The following depict examples of categories:
⎯ Upper limit specification: Case of specifying an upper limit price of the total cost value of communication;
⎯ Unit price upper limit specification: Case of specifying the upper limit of the unit price of communication
costs (in communication time units or transmitted information volume units).
In addition, the upper limit cost is specified as necessary.
© ISO 2006 – All rights reserved 7

---------------------- Page: 12 ----------------------
ISO 15662:2006(E)
4.1.7.4 Descriptive name context
“Protocol management information”.
4.1.7.5 Data concept type
Data element concept.
4.2 Application identifiers
This information is for identifying requested application services.
4.2.1 Message identifier
4.2.1.1 Descriptive name
ProtocolManagementInformation. messageIdentifier
4.2.1.2 ASN.1 object identifier
{iso(1) standard(0) iso15662(15662) protocolManagementInformation(1)
applicationIdentifiers(2) messageIdentifier(1)}
4.2.1.3 Definition
This identifies the message belonging to an application or a specific batch.
4.2.1.4 Descriptive name context
“Protocol management information”.
4.2.1.5 Data concept type
Data element concept.
4.2.2 Message number
4.2.2.1 Descriptive name
ProtocolManagementInformation. messageNumber
4.2.2.2 ASN.1 object identifier
{iso(1) standard(0) iso15662(15662) protocolManagementInformation(1)
applicationIdentifiers(2) messageNumber(2)}
4.2.2.3 Definition
This identifies the order of transmission and reception for a series of messages belonging to an application or
a specific batch.
4.2.2.4 Descriptive name context
“Protocol management information”.
8 © ISO 2006 – All rights reserved

---------------------- Page: 13 ----------------------
ISO 15662:2006(E)
4.2.2.5 Data concept type
Data element concept.
4.2.3 Time of message transmission
4.2.3.1 Descriptive name
ProtocolManagementInformation. timeOfMessageTransmission
4.2.3.2 ASN.1 object identifier
{iso(1) standard(0) iso15662(15662) protocolManagementInformation(1)
applicationIdentifiers(2) timeOfMessageTransmission(3)}
4.2.3.3 Definition
This information represents the time when an individual message transmission was started.
The time is indicated at which an individual message was transmitted from the communication carrier to the
user (see Figure 3).

Figure 3 — Time of message transmission
4.2.3.4 Descriptive name context
“Protocol management information”.
4.2.3.5 Data concept type
Data element concept.
4.3 Address
This information is for identifying service users and the internal processing of the service provider.
A wide area communication system shall be selected and routing shall be performed for use of applications
services to match the processing of the service provider and the communication system used by the service
user, and this information is contained for this reason.
4.3.1 Address of origin (Address of service provider)
4.3.1.1 Descriptive name
ProtocolManagementInformation. addressOfOrigin
© ISO 2006 – All rights reserved 9

---------------------- Page: 14 ----------------------
ISO 15662:2006(E)
4.3.1.2 ASN.1 object identifier
{iso(1) standard(0) iso15662(15662) protocolManagementInformation(1) address(3)
addressOfOrigin(1)}
4.3.1.3 Definition
This information represents the service provider or the internal processing of the service provider.
This contains the following data on the presumption of the use of multiple communication systems, IP
communication and so forth:
⎯ IP address in an IP network;
⎯ Address information containing data that can be routed;
Example: “Area (Province) Code”, “Service Car type Code”, “Group Code Serial Number”, others which
can identify the adequate user terminal;
⎯ Multiple address information in case multiple communication systems can be used.
4.3.1.4 Descriptive name context
“Protocol management information”.
4.3.1.5 Data concept type
Data element concept.
4.3.2 Address of destination (Address of user)
4.3.2.1 Descriptive name
ProtocolManagementInformation. addressOfDestination
4.3.2.2 ASN.1 object identifier
{iso(1) standard(0) iso15662(15662) protocolManagementInformation(1) address(3)
addressOfDestination(2)}
4.3.2.3 Definition
This information represents the address of the user terminal and so forth that has requested the service.
It contains the following data on the presumption of the use of multiple communication systems, IP
communication and so forth:
⎯ IP address in an IP network;
⎯ Address information containing the data that can be routed;
⎯ Multiple address information in case multiple communication systems can be used;
⎯ Multiple address information in case multiple user terminals can be used.
10 © ISO 2006 – All rights reserved

---------------------- Page: 15 ----------------------
ISO 15662:2006(E)
4.3.2.4 Descriptive name context
“Protocol management information”.
4.3.2.5 Data concept type
Data element concept.
4.4 Priority
This information identifies the priority of application processing on the part of the service provider.
4.4.1 Interrupt handling
4.4.1.1 Descriptive name
ProtocolManagementInformation. interruptHandling
4.4.1.2 ASN.1 object identifier
{iso(1) standard(0) iso15662(15662) protocolManagementInformation(1) priority(4)
interruptHandling(1)}
4.4.1.3 Definition
This information represents the priority level in the case of requiring interrupt.
In cases where the provided information is of high urgency, that information must be processed by interrupt
processing, and this information can be used to make such assessment.
The priority may have 255 levels and/or the following depict examples of categories:
⎯ Low priority: Case of interrupt having low priority;
⎯ Medium priority: Case of interrupt having medium priority;
⎯ High priority: Case of interrupt having high priority.
4.4.1.4 Descriptive name context
“Protocol management information”.
4.4.1.5 Data concept type
Data element concept.
4.4.2 Queue control
4.4.2.1 Descriptive name
ProtocolManagementInformation. queueControl
4.4.2.2 ASN.1 object identifier
{iso(1) standard(0) iso15662(15662) protocolManagementInformation(1) priority(4)
queueControl(2)}
© ISO 2006 – All rights reserved 11

---------------------- Page: 16 ----------------------
ISO 15662:2006(E)
4.4.2.3 Definition
This information indicates the control method in case queuing in line has occurred in message processing.
Although control is typically performed on a first-in first-out (FIFO) basis, since it is also possible to perform
processing based on last-in first-out (LIFO), this information can be used to make such assessment. In
addition, in the case where transmission has failed due to a collision and so forth, this information also makes
it possible to assess whether or not retry is necessary, the need for an error notification and so forth.
The following depict examples of processing categories of queuing lines:
⎯ Undefined: Processing is based on first-in first-out (FIFO);
⎯ LIFO: Processing is based on last-in first-out (LIFO);
⎯ Random: Processing is performed randomly regardless of order.
The following depict processing categories when transmission has failed:
⎯ Re-try: Case of performing resending processing when transmission has failed;
⎯ Error notification: Case of notifying the transmission source of an error when transmission has failed.
4.4.2.4 Descriptive name context
“Protocol management information”.
4.4.2.5 Data concept type
Data element concept.
4.5 Security
This information represents the need for security for receiving and transferring messages.
Since messages may contain confidential or private information, and may not permit impersonation, tampering,
disclosure and so forth, this information indicates what type of security is necessary.
4.5.1 Mutual authentication
4.5.1.1 Descriptive name
ProtocolManagementInformation. mutualAuthentication
4.5.1.2 ASN.1 object identifier
{iso(1) standard(0) iso15662(15662) protocolManagementInformation(1) security(5)
mutualAuthentication(1)}
4.5.1.3 Definition
This information represents the need for authentication of both persons engaged in the receiving and
transferring of data.
It can be used for authentication processing and so forth for preventing impersonation and the like in the
transfer of data between service providers and users. In addition, this information identifies whether or not the
user or terminal is to be authenticated as necessary based on the contents of the provided data and the
conditions of the terminal used by the user.
12 © ISO 2006 – All rights reserved

---------------------- Page: 17 ----------------------
ISO 15662:2006(E)
The following depict examples of mutual authentication categories:
⎯ User authentication: Case of requiring u
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.