10.1007@978-3-319-93332-01
10.1007@978-3-319-93332-01
1.1 Introduction
Communication and information technology are the driving force behind some
of the most notable innovations in the automotive industry and modern society.
In the last two decades, mobile communications have transformed our lives by
allowing the exchange of information, anywhere and anytime. The use of such
mobile communications systems in vehicles is expected to become a reality in
the near future, as industries, universities, and governments around the world
devote significant efforts and resources to the development of safer vehicles and
infrastructure for road transport. These investments can be verified through many
national and international initiatives dedicated to vehicular networks [3, 19, 24].
provide higher road safety, efficient mobility, and comfort to drivers and passengers
of vehicles traveling on city streets. The rest of the chapter is organized as follows.
In Sect. 1.2, we describe the concepts of an intelligent transport system and present
the principal ITS architectures and applications. We also explain the various issues
involved with security and privacy in an ITS. Finally, we discuss the most significant
challenges involved in integrating ITSs into smart urban centers.
Modern vehicles come equipped with a series of sensors, cameras, processing units,
and communication resources. All these embedded capabilities enable vehicles to
collect, transmit, and interpret information to assist in the acquisition of data and in
taking some action to help the driver and devices take action. These features turn
vehicles into a valuable tool for smart cities, serving as a source for capturing real-
time, relevant information used in the management of either traffic or resources. A
smart city can be defined as an intelligent environment that embeds information
and communication technologies that create interactive environments that bring
4 1 Intelligent Transportation Systems
regarding the monitoring and interpretation of data that can be used in decision
making. The analysis output should be usable in a large variety of applications,
such as allocating or moving physical resources not only for citizens but also for
municipal services, such as fire departments, ambulances, and police.
1.2.2 Architecture
The architecture used in the United States has been developed by the U.S.
Department of Transportation [22]. Its design focuses on assisting urban mobility
through a cooperative system. The architecture is referred to as the Architecture
Reference for Cooperative and Intelligent Transportation (ARC-IT); it consists of
a set of interconnected components organized into four views, as we can see in
Fig. 1.1. We describe each of the views as follows:
Functional View
Data Flows
Service
Packages
Requirements Processes
Functional View
Physical View
Phisical Objects
Fig. 1.1 Architectural reference for cooperative and intelligent transportation [22]
6 1 Intelligent Transportation Systems
• Enterprise View deals with the relationship between users and organizations,
establishing rules that such organizations follow within the cooperative ITS
environment. Therefore, the relationships between an entity, user, and system
depend on the roles that entities receive when interacting with user services.
Enterprise View consists of a set of objects such as:
– Enterprise Object is an individual or organization that interacts with an object.
An Enterprise Object can comprise several other objects by participating
in the interaction of various functionalities. For instance, Device Developer
is a component of Auto Manufacturer, but it also participates in Standards
Body [22];
– Resource supports the execution of some object. It may be a physical or virtual
element with limited dispersion;
– Relationship defines the coordination between Enterprise Objects, for exam-
ple, a contract;
– Role consists of a set of actions, functions, and rules that an object participat-
ing in a relationship carries out or follows.
Thus, in summary, the Enterprise View is composed of Enterprise Objects that
cooperate and interact to exchange information, manage systems, and operate
actions. Also, Enterprise View establishes relationships among those Enterprise
Objects, defining the method for Enterprise Objects to interact with other objects
that may appear in the View as Resources. The relationships among Enterprise
Objects establish a contract or agreement that seeks to find common purposes
necessary to implement and deliver an ITS service.
• Functional View focuses on the functioning of the abstract elements and
their logical interactions. Therefore, Functional View defines the functional
requirements to support the needs of ITS users. For this, the data flows and
processes provide a structure of presentation of interactions and functions that
preserve the requested requirements.
The ARC-IT functional model falls under a structural analysis methodology.
The methodology employs the National ITS Architecture’s logical architecture.
The architecture applies the work of Hatley/Pirbhai and includes Yourdon-
Demarco data flow diagrams (DFDs) to illustrate the flow of data between
functional elements [22]. The functional model does not include diagrams, just
collections of processes and their data flows. The Functional View uses some
structural artifacts, described as follows:
– Process consists of a function or activity that is required to perform actions
and achieve an objective or to support actions of another process, such as to
collect data and generate data;
– Process Specification corresponds to a function primitive, which is the textual
definition of the most detailed processes, including a set of inputs and outputs
of the functions, their requirements, and an overview;
– Data Flows comprise the flow of information among processes and an object
within a process;
1.2 Intelligent Transportation System Concepts 7
• Service Package represents a service-oriented entry point that shares each of the
four views. The Service Packages specify not only the technologies but also the
views that involve the ARC-IT architecture.
1.2 Intelligent Transportation System Concepts 9
RSE Gateway
OBE status
• Security is responsible not only for the safety of the system but also for the safety
of the vehicles’ mobility on the roads. The ARC-IT handles security holistically,
addressing security concerns spanning all four views.
The USA architecture provides the framework for the description of ITSs, which
defines the functions that must be performed by Physical Objects. Although the
architecture supplies several services to its users, it does not clarify the support of
the simultaneous use of various communication technologies to meet the needs of
its users. Another limitation of this architecture is related to the flexibility of the
system with respect to using new computing paradigms, such as cloud computing
and fog computing.
Transport Canada introduced the Canadian ITS architecture [2] and provided a
framework for planning, defining, and integrating ITSs. The architecture contains
the follows elements:
• The functions reflect the actions required for ITS, such as gathering traffic
information or requesting a route;
• The physical entities or subsystems correspond to the elements affected by the
functions, such as the field or the vehicle;
• The information flows and data flows are the connections between these functions
and physical subsystems together in an integrated system.
This framework contains a clear description of each element and subsystem. The
architecture is divided into five distinct components, as shown in Fig. 1.5. We review
each component in what follows.
1.2 Intelligent Transportation System Concepts 11
• User Services describe the services offered in the platform and accessed by users.
The platform provides 37 services to its users. These services present a set of
functions that allow the user to travel quietly and securely. Among the provided
services, we mention Traffic Management, Traveler Information, and Emergency
Management;
• Logical Architecture defines the functions and activities of each process to
meet the requirements of the user services. This architecture also seeks to
help identify the system functions and information flows and attempts to guide
the development of functional requirements for new systems. The Logical
Architecture provides a graphical view that shows the fit between processes
and data flows. However, this architecture does not define where or by whom
functions are performed in the system, nor does it describe how to implement a
function.
Therefore, in the Canadian framework, the architecture defines the set of informa-
tion and data flows and processes that meet user service requirements. Processes
and data flows are grouped to form particular transportation management func-
tions and are represented graphically by bubble charts, which decompose into
several levels of detail.
• Physical Architecture describes the physical entities that define subsystems
and Terminators. The architecture specifies Architecture Flows that detail the
integration of subsystems and Terminators in the system. However, this architec-
ture provides agencies with a physical representation of how the system should
provide the required functionality. Thus, the architecture takes the processes
identified in the Logical Architecture and assigns them to physical entities.
The subsystems represent a set of capabilities, corresponding to the principal
structural elements of the ITS physical architecture. These subsystems are
divided into four classes, as shown in Fig. 1.6. Center defines the control
and management center of the entire system, which executes the services.
Field encompasses all the infrastructure of the environment, such as roadside
units (RSUs), monitoring sensors, and cameras. Vehicles represent vehicles and
onboard sensors. Travelers correspond to the devices used by people during a
trip. Terminators describe the boundary of an architecture and represent people,
systems, and the general environment that interface to an ITS.
Physical Architecture also uses an entity called Equipment Packages that divides
the subsystems into deployment-sized pieces. Equipment Packages serve to
group functions of a particular subsystem together into an “implementable”
software package and hardware capabilities.
• Service Packages consist of slices of the Physical Architecture that deal with
specific services related to transportation problems, such as surface control. A
service involves a set of Equipment Packages required to work together and
deliver a given transportation service. Therefore, a service collects different
information from many subsystems, Equipment Packages, and Terminators to
provide the required service output.
• Standards are methods that facilitate the deployment of interoperable systems at
local, regional, and national levels without impeding an innovation as technology
12 1 Intelligent Transportation Systems
Centres
Travellers Traffic Emergency Toll Commercial Maintenance &
Vehicle Construction
Management Management Administration Administration Management
Remote
Traveller
Support Information Emissions Transit Fleet and Archived Data Border
Service Management Management Freight Management Inspection
Personal Provider Management Administration
Information
Access
Wide Area Wireless (Mobile) Fixed Point - Fixed Point
Communications Communications
Vehicle Roadway
Emergency Security
Vehicle Monitoring
Commercial Toll
Communications
Communications
Vehicle - Vehicle
Vehicle Collection
Field - Vehicle
Transit Parking
Vehicle Management
Maintenance & Commercial
Construction Vehicle Check
Vehicle
Intermodal
Freight Intermodal
Equipment Terminal
Border
Inspection
Systems
Vehicles Field
Fig. 1.6 ITS architecture for Canada subsystems and communications [2]
ITS-S Host
Vehicle ITS Gateway
ITS-S Router
Personal ITS Station
Internal Network
MF
SF
Facilities
Management
NF
Security
Networking &
WN
SN
Transport
IN
SI
MI
Access
MS
• Networking and Transport define the addressing and routing of network infor-
mation, as well as the sending of information over the network. This module
corresponds to layers 3 and 4 of the OSI model;
• Facilities comprise layers 5, 6, and 7 of the OSI model and are intended to
assist ITS applications that share functions and information according to their
functionality and application. They manage all data coding and application
sessions;
• Applications refer to ITS applications. These applications may contain features
of more than one service, and one service may be the result of a combination of
other applications;
• Management is in charge of managing communications within the ITS-S;
• Security Entity provides security services.
Therefore, an ITS-S hosts a variety of ITS applications and communicates with
other components within the subsystem and other ITS-Ss [7]. An ITS-S can be
composed of the following functional elements:
• ITS Station Host provides access to ITS applications through personal devices;
• ITS Station Gateway supports external communication. It connects two differ-
ent OSI protocol stacks at layers 5–7;
• ITS Station Router establishes a vehicle-to-vehicle (V2V) or vehicle-to-
infrastructure (V2I) communication or communication between ITS-Ss, meaning
an interconnection between OSI layer 4 (transport) and 3 (network) of the OSI
model;
• ITS Station Border Router provides nearly the same functionality as ITS-S
routers, with the difference that the external network may not support the same
management and security principles of the ITS [1].
The European architecture presents a set of subsystems that offer ITS services.
Like the architectures mentioned previously, this one also has limitations, such
as the use of a centralized control element and the lack of integration with new
1.2 Intelligent Transportation System Concepts 15
interconnections among vehicles. Future trends for the Internet consist of peer-
to-peer (P2P) wireless communications and a support infrastructure for the proper
provisioning of applications and services. In what follows, we highlight some works
that make use of infrastructure integrated with ad hoc networks, demonstrating
how an ITS can become complete and more efficient through the use of hybrid
architectures, and discussing the challenges that need to be overcome.
An analysis of the impact of urban features [9] has shown that the appropriate
placement and installation of RSUs, together with the corresponding communi-
cation configurations, could ensure successful V2I communications. The study
made use of tests in a real urban scenario, the city of Bologna, where experiments
employed the IEEE 802.11p protocol for V2I communication. The obtained results
demonstrated that the use of the IEEE 802.11p protocol was strongly affected by
the layout of the streets, elevation of the terrain, traffic density, presence of heavy
vehicles, and other obstacles, such as trees and vegetation. These enforced the
suggestion that these environmental elements must be taken into consideration for
adequate deployment of RSUs and for the configuration of radio communication.
We may observe in several works in the literature [10, 11, 17, 23] the use of infras-
tructure in the design of ITSs in which RSUs extend the primary communication
mechanisms to serve as devices with the computational power to assist in the ITS
architecture. More recent works show a growing trend toward merging vehicular
networks with cloud computing. This merging of the two technologies aims to
provide greater scalability for transportation services. These joint technologies also
make it possible to increase the computational power of ITS architectures through
mobile cloud communication brought about dynamically among devices, vehicles,
and the static cloud, which corresponds to control centers or data centers [14].
With the ease of communication between vehicles and with a road infrastructure,
vehicular networks provide diverse applications and services for users. The design
of ITS services and applications aim to assist drivers and passengers during their
travels, with a focus on reducing accidents and managing traffic in large cities. In
addition, other types of applications help and promote services to drivers, making
their travel more peaceful and enjoyable. The main applications focused on ITS are
as follows:
• Safety applications are intended to alert drivers to the possibility of imminent
collisions with other vehicles or with obstacles ahead. In some scenarios, a driver
needs to react by making a quick decision to avoid a collision. For this reason, this
type of application has severe restrictions on delay and reliability. Some types of
this class of applications involve alerting drivers to hazards on highways, warning
of collisions, notifying about accidents on the road, and informing drivers about
construction work ahead. All services aim at avoiding collisions between vehicles
and supporting efficient access for first responders;
1.2 Intelligent Transportation System Concepts 17
Concerns about ITS safety focus on information protection and the transportation
infrastructure. More than ever, information-based transportation systems have
become inherently accounted for to detect, collect, process, and disseminate data
and essential to improving the efficiency of moving goods and people, enhancing
the safety of our transportation system, and providing travel alternatives. The vast
collection and dissemination of information raises significant security and privacy
issues due to the large-scale exchange of sensitive data.
Security concerns have been addressed in the ITS architecture using two
approaches [22]:
• ITS Security Areas discretize and classify security issues that might arise in ITS
environments. As previously described, ITSs can be used to improve the safety
of the surface transportation system. Figure 1.9 shows eight security applications
defined for an ITS that can be used to detect, respond to, and recover from threats
against the transport system.
18 1 Intelligent Transportation Systems
Infrastructure Security
aspects relevant to ITS
HAZMAT Security
Traveler Security
Vehicle Security
architecture
Transit Security
and Evacuation
Transportation
Rail Security
ITS
Security
Areas
Information Security
Securing ITS Personal Security
ITS Operational Security
Security Management
• Securing an ITS addresses the issue of protecting information from the ITS to
safeguard ITS applications so that they are reliable and available when needed.
Owing to the nature of communication, the information exchanged between the
elements of an ITS is subject to tampering and unauthorized use, in which false
or erroneous information can cause a severe accident to the driver or passengers
in a vehicle. Thus, security is concerned with not only preventing unauthorized
disclosure of confidential information but also covering a wide range of threats
that may disrupt or change the operation of the system. For these aspects,
information security is one of the great challenges for an ITS operating in a city.
When considering the security aspect of information in an ITS, the safety
components need to be explicitly established. Some research works, such as that
presented in [13], describe several components that smart transportation systems
need to consider. These elements include keeping the system secure, addressing the
threats faced by the system, and providing security services to protect against threats
while allowing the system to perform in line with its objectives.
In securing an ITS, we can highlight the following contextual aspects:
• Confidentiality aims to ensure that data and the system are not accessible to
unauthorized entities, processes, or systems;
• Availability refers to allowing access to data and the system to authorized
entities, as well as other processes and even systems;
• Integrity involves ensuring that ITS data retain their meaning, completeness, and
consistency.
The design of an ITS must be such that possible threats are avoided so that
the aforementioned security requirements are met. We can broadly define a threat
as anything that might cause an issue in the system and arise accidentally or
intentionally due to a natural disaster. Threats are also present in ITSs, and the
following list summarizes the major ones in the context of ITSs:
1.2 Intelligent Transportation System Concepts 19
References
15. Mutalik P, Nagaraj S, Vedavyas J, Biradar RV, Patil VGC (2016) A comparative study on
AODV, DSR and DSDV routing protocols for Intelligent Transportation System (ITS) in metro
cities for road traffic safety using VANET route traffic analysis (VRTA). In: Proceedings of
the IEEE international conference on advances in electronics, communication and computer
technology. IEEE, Piscataway, pp 383–386
16. Nam T, Aldama FA, Chourabi H, Mellouli S, Pardo TA, Gil-Garcia JR, Scholl HJ, Ojo A,
Estevez E, Zheng L (2011) Smart cities and service integration. In: Proceedings of the 12th
annual international digital government research conference: digital government innovation in
challenging times, dg.o’11. ACM, New York, pp 333–334
17. Olariu S, Khalil I, Abuelela M (2011) Taking VANET to the clouds. Int J Pervasive Comput
Commun 7(1):7–21
18. Pan G, Qi G, Zhang W, Li S, Wu Z, Yang L (2013) Trace analysis and mining for smart cities:
issues, methods, and applications. IEEE Commun Mag 51(6):120–126
19. PATH (2017) Official website path
20. Qin H, Zhang W (2011) Charging scheduling with minimal waiting in a network of electric
vehicles and charging stations. In: Proceedings of the eighth ACM international workshop on
vehicular inter-networking, VANET ’11. ACM, New York, pp 51–60
21. Steventon A, Wright S (eds) (2006) Intelligent spaces: the application of pervasive ICT.
Computer communications and networks, vol XVIII
22. U.S. Department of Transportation (2017) Architecture reference for cooperative and intelli-
gent transportation
23. Trullols O, Fiore M, Casetti C, Chiasserini C, Ordinas JB (2010) Planning roadside infras-
tructure for information dissemination in intelligent transportation systems. Comput Commun
33(4):432–442
24. VICS (2017) Official web site of vehicle information and communication system (VICS) Japan
25. Zhu J, Feng Y, Liu B (2013) Pass: parking-lot-assisted carpool over vehicular ad hoc networks.
Int J Distrib Sens Netw 9(1):1–9