Content uploaded by José Iván San José Vieco
Author content
All content in this area was uploaded by José Iván San José Vieco on Apr 05, 2015
Content may be subject to copyright.
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring∗
Jose I. San Jose†
, Juan J. de Dios, Roberto Zangroniz, Jose M. Pastor
Institute of Audiovisual Technologies (http://itav.uclm.es)
University of Castilla-La Mancha
Cuenca, Spain
{JoseIvan.SanJose,JuanJose.deDios,Roberto.Zangroniz,JoseManuel.Pastor}@uclm.es
Abstract
Automatic Vehicle Location (AVL) Systems are being introduced increasingly in many cities
around the world. These systems are aimed at cost reduction and optimization of time and resources.
A Radio Frequency Identification (RFID) based system called RFID Urban Transportation Monitor-
ing System (RUTMS), is proposed in this paper for urban transportation tracking. The monitoring
of bus stops and lines on the route map has been integrated and an EPCGlobal-based WebServices
interface to the proposed system has been developed. RFID readers are located in the bus stops for
retrieving real-time data, as these data can be compared to the information of the transport routes
stored in the database of the tracking system. A Web environment is proposed for this purpose, as
these data can be accessed anytime through whichever device using a web browser. The architectural
model is based on a Fosstrak EPCIS Repository, as it has been certified by EPCGlobal, and it can be
used in any open source software platform implementing the EPC Network specifications. Two Web
services are developed: the first one is used for monitoring the transport location and the second one
is used for displaying the arrival time of any bus to a specific bus stop. A graphical interface has also
been integrated on the tracking system. The system we propose is a simple and inexpensive tool to
locate bus transport in a Geographic Information System (GIS), by using RFID readers in the bus
stops and RFID tags in the buses.
Keywords: EPCGlobal, Web Services, RFID, location, AVL.
1 Introduction
Automatic Vehicle Location (AVL) [2] provides real-time location information for any mobile assets
upon which it is installed. AVL is used for different traceability purposes, especially for those related
to tracking one vehicle or a fleet of vehicles. Tracking system technology [3] was made possible by the
integration of several navigational technologies, as Global Positioning System (GPS) [4], Geographic
Information System (GIS) [5] and General Packet Radio Service (GPRS) [6]. Also, AVL can be used
together with other technologies such as Radio Frequency Identification (RFID) [7] or Wireless Sensor
Networks (WSN) [8].
RFID technology [9] is one of the most innovative technologies in object location and identifica-
tion, as it provides a good solution for the traceability and tracking of any kind of products in a simple
∗This paper is an extended version of the work originally presented at the International Workshop on Pervasive Internet
of Things and Smart Cities (PITSaC-2013) in conjunction with AINA-2013 International IEEE Conference, Barcelona, Spain,
March 2013, titled “RFID Tracking for urban transportation using EPCGlobal-based WebServices”[1]. A more detailed de-
scription of our proyect is added. Besides, the Web interface is described in greater detail. Also made a comparison with other
projects, that use GPS or RFID to locate public transport on a map.
†Corresponding author: Institute of Audiovisual Technologies, University of Castilla-La Mancha, Cuenca (Spain). Tel: +34
969-179-100 ext. 4773, email: JoseIvan.SanJose@uclm.es
1
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
and economic way. On one hand, the application of RFID technology can benefit consumers through
improved product availability, speed of service, and quality assurance. RFID tagging of products by
manufacturers, wholesalers, and retailers appears to be the most promising approach to reliable product
tracking and tracing, instead of bar codes.
On the other hand, RFID helps companies to improve the supply chain efficiency, and provides a
high added value by optimizing the distribution process and the available resources [10]. Besides, tags
can be used for identification, inventory, and product traceability.
The Electronic Product Code (EPC) [11] [12] is designed as a universal identifier that provides a
unique identity for physical objects. EPC is generally thought of as the next generation of the standard
bar code. It is used in information systems that need to track or otherwise refer to physical objects. A
very large subset of applications that use the Electronic Product Code also rely upon RFID Tags as a data
carrier, and enables the assignation of a unique global number to any product, so that it can be associated
with specific product information, such as date of manufacturing, origin and destination of the shipment.
In this paper, we design a storage system for the events detected in the RFID readers located along
the distribution chain of the products, from their manufacturing till they are delivered to customers. Data
are stored and retrieved using an RFID tag which transmits the ID of the product when prompted by the
RFID reader.
Our main goal is to design and implement an EPCGlobal RFID-based system, to store tracking and
tracing data events. These stored events may be accessed via a Web service specifically devised for this
purpose, with the capability to be accessible from any device, either a PC or any mobile device (smart-
phones, tablets, etc.).
We propose a system, called RFID Urban Transportation Monitoring System (RUTMS), that will en-
sure a set of minimum requirements of scalability, extendibility, and compatibility. In order to meet these
criteria, EPCGlobal standard is fulfilled. In addition, the proposed system also provides the necessary
tools to building our system. A simulation of the system will be implemented, as it is not possible to
achieve all the resources required for this implementation at the moment.
Another goal of this paper is to locate any element through a GIS, Google Maps JavaScript API v3
[13] [14] is used. Google Maps is commonly accepted, and globally referenced due to its usability.
The architecture of RUTMS is based on the Fosstrak EPCIS Repository, as it is a complete implemen-
tation of the EPCIS standard specification, including what we need to deploy the application. Besides, it
is also certified by EPCglobal. Futhermore, in this paper we also perform a comparative study with other
similar systems using RFID or GPS to locate vehicles.
In this paper, we describe the general methodology that could be defined to develop any other type
of similar system. Finally, and as a particular case, we will implement an application for monitoring the
transport location and the arrival time of a bus route. This application is defined as a Web Service. The
user queries the information of the current situation of a bus, the system will display it on the map and
the time left to reach to the selected bus stop will be also indicated on the route.
2
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
2 Related Works
At present, beyond the simple management of vehicles [15], which comprise a fleet, different ways of
working are essential, related not only to the management of the vehicle itself, but going a step further,
related to the goods carried within them. Therefore a new set of technologies is necessary to meet the
needs that allow us to be able to offer services that enable monitoring, tracking and traceability of prod-
ucts contained inside the cargo area of vehicles that come into play to implement this new solution.
AVL Systems are being introduced increasingly in many cities around the world [16]. The objective
is to improve the efficiency of the road-based passenger transport systems. Satellite-based location and
communication systems, particularly the GPS, have been the infraestructure needed for AVL systems,
which are now supporting several types of applications as: Real-Time Passenger Information (RTPI),
Fleet Management and Operations (FMOs) and Public Tansport Priorities (PTPs).
On one hand, most of the AVL Systems are using GPS as the main location technology. London’s
iBus [17], Sydney PTIPS [18], Auckland SR/RTPIS [19] or Glasgow BiAS [20] are examples of public
transport that use GPS as location technology.
On the other hand, we can find AVL Systems based on RFID. There are systems that use RFID and
WSN [21] or automatic vehicle tracking [22].
In a more visual way, we compared the different systems in two tables. Table 1 shows a comparative
between RUTMS, and the systems mentioned before. In this table, we compare the location technology,
data transmission technology, data storage location, data processing location and bus priority at traffic
signals of each system.
Table 2 shows the different applications that have been developed in each system, as real time / esti-
mation location, passenger information display, app for mobile devices, route calculation and number of
buses arriving to a bus stop.
For the tracking tasks described above, GPS technology has already been well established, by which
it is possible to determine the absolute position of a particular vehicle, whose position can be associated
with an existing map, obtaining additional information about the path that the vehicle on which the re-
ceiver is installed.
Also, RFID technology allows to determine the position of a particular vehicle, when the vehicle
passes near an RFID Reader. The measurement distance depends on the kind of tag attached to the
vehicle (active or passive), also depends on the position of the tag on the bus, and the RFID antennas.
3 Technologies
For developing our system, the following technologies are used: RFID, Electronic Product Code Infor-
mation Services (EPCIS)[23], Fosstrak EPCIS Project [24] and Web Services [25].
3.1 RFID
Radio frequency identification (RFID) is a generic term that is used to describe a system that transmits
the identity (unique serial number) of objects or people wirelessly, using radio waves. It’s grouped under
3
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
Location
Technology
Data
transmission
technology
Data storage
location
Data
processing
location
Bus priority
at traffic
signals
London
(iBus) GPS GPRS /
WLAN
AVL Centre
and Bus
AVL Centre
(lateness) and
Bus
Yes
Sidney
(PTIPS) GPS GPRS AVL Centre
and Bus AVL Centre Yes
Auckland
(RTPIS) GPS GPRS AVL Centre
and Bus AVL Centre Yes
Glasgow
(BiAS) GPS Radio / LAN AVL Centre
and Bus Bus (lateness) Yes
BMS using
RFID and
WSN
RFID WSN AVL Centre AVL Centre No
RUTMS RFID LAN / WLAN
/ WSN AVL Centre AVL Centre No
Table 1: Comparative of technology
Real time /
estimation
location
Passenger
information
display
APP for
mobile
devices
Route
calculation
Number of
buses will
arrive to bus
stop
London
(iBus) Real time Yes No No 1
Sidney
(PTIPS) Real time Yes No No 1
Auckland
(RTPIS) Real time Yes No No 1
Glasgow
(BiAS) Real time Yes No No 2
BMS using
RFID and
WSN
Estimation Yes No No 1
RUTMS Estimation Yes Yes Yes 2
Table 2: Comparative of applications
the broad category of automatic identification (Auto-ID) technologies, which have been used to reduce
the amount of time and labor needed to input data manually and to improve data accuracy.
Bar code systems often require a person to manually scan a label to capture the data. RFID is de-
signed to enable readers to capture data on tags and transmit it to a computer system, without needing a
person to be involved.
A typical RFID tag consists of a microchip attached to a radio antenna mounted on a substrate, and
4
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
contains the identification data of the object to which are attached. The RFID tags may generate a radio
frequency signal related to the data, so it can be received by an RFID reader, which retrieves the data
stored on the tag and converts it to a digital format according to the specific application.
Currently, the organization of companies and universities around the world, called EPCGlobal (for-
merly Auto-ID Labs), is responsible for developing standards and the necessary technology to be able to
identify any object effectively. In 2003, the RFID technology really began to spread through the industry,
driven by technological advances, the reduction of costs and the efforts of the Department of Defense of
the United States.
3.2 Electronic Product Code Information Services (EPCIS)
EPCIS is a standard designed by EPCglobal to allow sharing and pooling of data between different
companies. The aim is to allow the participants of the EPCGlobal Network get a common view of the
disposition of the various objects within the business environment.
The Architecture Framework published by EPCglobal [26] provides a comprehensive overview of
the EPCglobal standards. It shows how the different interface standards are related and outlines the prin-
ciples that have guided the design of the standards.
EPCIS defines standard interfaces that allow the EPC data being captured and later be used by op-
erations and an associated data model. Capture and query of these data, includes the use of persistent
databases and the sharing of information application-to-application.
The EPCGlobal Architecture Framework1(see Figure 1) is a collection of interrelated standards for
hardware, software, and data interfaces, together with core services that are operated by EPCglobal and
its delegates, all in service of a common goal of enhancing the supply chain through the use of Electronic
Product Codes.
This framework does not dictate particular system architecture, but leaves this to implementers or
manufacturers who can choose the system architectures that are most appropriate for their deployments.
EPCIS only specifies the interface between applications and data collection needed to access them.
It does not specify how to implement the operations or databases, but in no case the definition of
the interfaces will be outside of the framework scope. In our development we use the RFID reader of
SkyeModuleM9 to capture data. This hardware meets the EPCGlobal standards and specifications, but it
has its own communication protocol and other special features.
Therefore, EPCIS is a standard that has a layered structure, extensible and modular. This feature
offers a number of advantages such as, for example, the reuse of code. The different layers described
within the EPCIS standard: Abstract Data Model Layer, Data Definition Layer, Service Layer and Bind-
ings are presented in Figure 2).
These layers are described briefly below2:
1More information about data standards, interface standards and standards in development at: http://www.gs1.org/
gsmp/kc/epcglobal
2More information about the layers at: http://www.gs1.org/gsmp/kc/epcglobal/epcis/epcis_1_0_
1-standard-20070921.pdf
5
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
Figure 1: EPCGlobal Arqhitecture Framework
•The Abstract Data Model Layer specifies the generic structure of EPCIS data and this layer speci-
fies the general requirements for creating data definitions within the Data Definition Layer.
•The Data Definition Layer specifies what data is exchanged through EPCIS, what its abstract struc-
ture is, and what it means. Data definitions in the Data Definition Layer are specified abstractly,
following rules defined by the Abstract Data Model Layer.
•The Service Layer defines service interfaces through which EPCIS clients interact. Two Service
Layers are defined: the Core Capture Operations Module and the Core Query Operations Module.
•Bindings specify concrete realizations of the Data Definition Layer and the Service Layer. In this
specification, nine bindings are defined for the modules defined in the Data Definition and Service
Layers.
The layered technique for specification promotes extensibility, as one layer may be reused by more
than one implementation in another layer. Besides the inherit extensibility, EPCIS provides us two
specific methods to do the extensibility: Subclassing and Extension Points.
•Subclassing. A subclass is a new type that includes all of the fields of an existing type, extending
it with new fields. An instance of a subclass may be used in any context in which an instance of
the parent class is expected.
•Extension Points. Data definitions and service specifications also include extension points that
may use to provide extended functionality without creating subclasses.
6
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
Figure 2: EPCIS Layers
The modularity consists of several single associated specifications. This property allows to EPCIS
grow and envolve in a distributed way. Together with the layered structure and extensibility, the modu-
larity allows the definition of the structure in different documents as well as promote the consistency of
the structure.
3.3 Fosstrak EPCIS Project
Fosstrak EPCIS Project is an open source software platform that implements the GS1 EPC Network spec-
ifications. It provides an EPCglobal-certified EPCIS Repository as well as Query and Capture clients.
Fosstrak EPCIS Project features are, as follows:
•Deploying an EPCIS Repository.
•Run queries to an EPCIS Repository through a Graphic User Interface (GUI).
•Adding information to an existing EPCIS Repository through a GUI. This GUI is different than
the before GUI.
7
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
In addition to these standards-compliant modules, it also offers a ”Web adapter” for easy EPCIS ac-
cess via web protocols (e.g., REST). Fosstrak has a regular client-server architecture consisting of three
modules: the Repository is the server, Query and Capture clients.
The repository is responsible for analyzing the requests of the clients, which are processed according
to the rules defined in the specification of the standard. It implements five bindings as defined by the
EPCIS specification: XML (eXtended Markup Language) for Data Definition Layer, HTTP for the Cap-
ture Interface, SOAP/HTTP for the Query Control Interface, HTTP and HTTPS for the Query Callback
Interface.
The clients communicate with the repository via transport protocols. These protocols are: XML over
HTTP to Capture client and SOAP (Simple Object Access Protocol) over HTTP to Query client, as we
can see in Figure 3.
To capture EPC data, it is necessary to wrap the data into XML conformin the EPCIS XML Schema
for event types. This EPCIS event must then be sent in an HTTP POST request to the repository’s capture
interface. An example of capture event, serialized into XML, is shown in Figure 4.
Queries for EPCIS Events must be inside a valid SOAP request to the repository. An examle of XML
is shown in Figure 5.
Both clients, Capture and Query, have a development client API and a client GUI. The API is used
by other applications to send queries to the repository. Manually, the interface is used to send events
within the repository. Fosstrak also provides a set of libraries and documentation to be able to integrate
clients Capture and Query in an architecture type J2EE.
3.4 Web Services (WS)
Web Services are technologies that integrate a set of standards and protocols to exchange data between
applications developed in different programming languages and they can run on any platform. We can
use the Web Services to exchange data in both private computer networks and the Internet.
Interoperability is achieved by open standards. Organizations such as OASIS and W3C are responsi-
ble for indicating the type of architecture and Web services regulation. Web Services are loosely coupled
software components that offer standardized interfaces based on mainly two languages: the Web Service
Definition Language (WSDL) which is used to define the syntax of the interfaces, and SOAP which de-
fines the format of messages that are exchanged when invoking services.
In the future Internet [27] , real-world devices will be able to offer their functionality via SOAP-based
Web Services (WS-*) or RESTful APIs, enabling other components to interact with them dynamically.
The functionality offered by these devices is often referred to as real-world services because they are
provided by embedded systems that are related directly to the physical world.
Unlike traditional enterprise services and applications, which are mainly virtual entities, real-world
services provide real-time data about the physical world. Armed with this additional knowledge, one can
support a more efficient decision making process. Hence, the devices are providing their functionality as
a Web Services can be used by other entities such as enterprise applications or even other devices. No
8
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
Figure 3: Fosstrak EPCIS Project Implementation
device drivers are needed anymore and a new level of efficiency can be achieved as web service clients
can be generated dynamically at runtime.
4 Development Methodology
This section describes the methodology that has been proposed for the development of a generic ap-
plication and that, subsequently, will serve us for the development of the application proposed in the
introduction section. Our methodology is divided into three parts: design, modeling, and implementa-
tion.
9
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
Figure 4: XML Capture EPCIS Events
4.1 Design
Before programming, we must consider a series of requirements previously, since it is necessary to be
clear about the application you want to perform.
As indicated earlier, our application must be able to show us the information that it stores in a
database. To do so, we must build a Web site on which we are able to access from any device (PC,
Tablet, Smartphone, etc.), whichever browser, anywhere in the world to query of the information.
To do this, our application must meet a series of functional and non-functional requirements:
1. The functional requirements are the following: RFID readers must be able to access the central
database through either a microprocessor or DSP. Each hardware element reading will connect
through a port serial or USB to its processor, which will also have Internet connection. The infor-
mation captured by the RFID readers in the bus stops, can be sent by different ways: via ethernet
connection, WIFI or through the new Wireless Sensor Networks infraestructures that are being in-
10
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
Figure 5: XML Query for EPCIS Events
stalled in many cities. For a global interconnect, IPv6 addresses are used and IPv4 addresses will
be translated into IPv6 if needed to maintain compatibility. The Web Application can also access
the same database in order to query, modify or update such data.
2. As non-functional requirements, our application must comply with the following: it seems inter-
active for the user in order to request information from the server. The interface must be rather
simple so that any user can use it. The system should be robust against errors, and report either
the time in which they occur or whether not-allowed access to the data is tried out. It must provide
security for the data stored in the database, so that they can only be modified by authorized users.
Once these requirements are met, we may enhance them according to the desired approach imple-
mented for our application.
Within this section, it is also necessary to select the platform on which we are going to develop our
application. For its development, the following elements have been selected as the proposed architecture
is based on Fosstrak EPCIS Repository and we need all the elements are fully compatible with Fosstrak.
Items selected for our development are as follows:
1. J2EE [28] development architecture.
2. Apache Tomcat [29] to be used as application server.
3. MySQL [30] to be used as database administrator.
4. Eclipse [31] and Visual Studio [32] to be used as development environments.
We have selected these elements because they are compatible with Fosstrak and EPCGlobal, they are
programmed in Java, they are free, open source and secure. In the case of Visual C#, we use it because
SkyeTek development APIs [33] are written in C and Microsoft NET. In this way we connect, configure
11
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
and control our hardware SkyeModule M9 [34] and the captured information can be send to the central
database for our application.
4.2 Modeling
Once the design is defined and the development platform has been also determined, the next step is to
apply to particular cases such as urban transport routing and bus stops location on a map. It also estimates
the arrival time of a bus stop.
In our case, our application consists of the design and implementation of an EPCGlobal system based
on RFID to store event data, more specifically location events. These data will be available to be accessed
through any device and any Web browser.
RFID passive tags are used because they are a good solution for tracking products along the dis-
tribution process and they are used in the first layer of our model. The RFID passive tags are cheap,
can store up to 128 Kbytes of data and the RFID readers can read several tags simultaneously. Besides,
RFID passive tags are used as they do not need maintenance an are more widespread than their active
counterparts, so wharehouses, generally, have the requiered handling equipment. However, it is possible
to use RFID active tags for specific applications, such as sensors, if required.
After deciding the application, the next step is to create the tables in the MySQL database and the
various Java classes needed to work comfortably and easily, with the tables of the database that we create.
Within the database, the first task we carry out will be the filling a table named Read Point. The idea
is to place a Read Point at each stop. In this way the name of the stop will be assigned and related to the
located data (latitude, longitude and address) to identify it.
The next step will be to create and load the tables in the database that are for working with urban
transport lines and the different buses. As our application is rather simple, we only need to define three
Java classes to be able to properly write the tables that we have created within the database. The three
proper classes are: EPCIS, line and stop. As we can see in Figure 8, the properties of the line and stop
classes are specific for the database modeling.
Another important issue to consider when developing the data model, it is to analyze the relationships
between the different tables and see how they relate to each other, to achieve a correct and consistent with
our application data model. In Figure 9, we can see how they are related and how nodes are connected
to.
4.3 Integration
One of the main objectives of regular client-server architecture is the separation of the business logics
from the design logics. In other words, the goal is to separate the presentation data layer from the user
layer. Currently, when designing an application for big computer systems, it is often programmed via
layers or multilevel architectures.
The main advantage of this model of development is that the application is splitted up into several
levels or layers. Thus, each layer will play a simple role within the application, so we make a minor
12
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
modification on the application, where it is not properly working.
To develop our application, a three-layer model is used (see Figure 6). It will consist of the following
layers:
1. Presentation layer, for the user interface of the application. It introduces the system to the user,
communicates information to him and returns the answer to the user applying a previous filter
in order to check that there is no error. The interface consist of JSP components, because dy-
namic content is created in an HTML document. the file is completed with JavaScript functions to
communicate with Google Maps.
2. Business logic layer, for the business processes of the application. This layer is where the programs
are running. It communicates with the presentation layer, to receive requests and present results,
and with the data layer, to asking the system manager database for data storage or retrieval.
3. Data layer corresponds to the definition, storage and access to the application data. In an EPC-
Global system, it translates into the definition of the tables necessary to store data of events, vo-
cabularies, bus, bus lines, etc. This layer consists of one or more databases management and it
receives store request and retrieval information from the Business logic layer.
Figure 6: 3-layer model
Once the layer model to be used is decided, the next section will describe the process that we follow
for the application development.
Another important task in our development is to connect, to configure and subsequent control of
RFID readers with Visual C#. This is a crucial task, because the location information captured is stored
in a MySQL database, that is controlled by the developer, and these elements will be located on the map.
Finally, to conclude this section, the main libraries that we have used for deploying this application
are:
•SkyeTek .NET API. It is a simple object-oriented interface that allows to use .NET framework in
a computer. This interface allows to create commands for SkyeTek Protocol v3 (STPv3) [35] for
SkyeModule readers. The requests and responses are written following the STPv3 standard.
•JDBC (Java Database Connectivity) API. This API is necessary to work with MySQL DB. It allows
to run different MySQL commands using Java in any DB.
•Fosstrak API. It is neccesary to define an EPCIS Repository to develop our application. For this,
the Fosstrak API default libraries, the EPCIS Clients and the TDT Engine are used.
13
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
EPCIS Capture Client and EPCIS Query Client. These clients allow capture and query for all
the EPC information.
EPCIS Repository. It is a file that is stored in the Web Server. Whenever that the system
needs to capture or show information through EPCIS, the system queries to this context. EPCIS
Repository has several Java components that are necessary to develop our application.
TDT Engine. It traslates automatically the EPC information3that it receives from the Skye-
Module M9 into Pure Identity URIs.
•Google Maps JavaScript API v3. With this API, Google Maps can be added in a Web page. Also,
we can find several utilities to work and services to add information to Google Maps. Google Maps
API v3 is specially designed to work with mobile devices and traditional desktop applications.
5 Location transport and arrival time
Once the theoretical model of the system has been presented, in this section we describe the development
of a particular WS for the location of urban transportation. In addition, the Web Application shows more
information about bus lines, bus routes, prices, etc.
The WS indicates the arrival time of the bus at a particular stop and it locates all the bus lines on the
route map, representing the specific position and displaying the time left for a bus to arrive at a particular
stop. Besides, the application can calculate routes between two bus stops with the possibility of one
transfer between two different busses.
As indicated in the previous sections, we develop a Web Application based on regular client-server
architecture. The client requests through a Web browser the WS to the Web server. In our own local
network, there is a DB server that provides access, security and storage of all the data in the system. One
of our development goal is that our application can be viewed from any compatible device, using any
web browser, and which can be accessed from anywhere in the world.
On the other hand, we will have nodes related to the RFID reader that connects by USB to a micro-
processor, so the Web server updates the system when an event occurs. This will happen when an RFID
tag goes nearby the antenna of a reader.
Subsequently, the location of the various elements that will form our system through Google Maps
will be displayed. As discussed in previous sections, there will be a simulation of the system, due to the
unavailability of all the resources involved to achieve the actual implementation.
To begin our development, we create a Web Application information retrieval. To access procedures
to the database, it is using the default ones in Fosstrak EPCIS Repository. We will also use all default
methods leading to capture EPCIS events, thus following the standard marked by EPCglobal.
In the modeling process of our system, we are designing the necessary MySQL tables (Figure 7) for
proper operation. Are also being designed Java classes (Figure 8) which form our model, taking special
care in relationships and how to communicate between nodes our architecture consists of (Figure 9).
3EPCIS standard works in Pure Identity URI format. The EPC information is a hexadecimal code.
14
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
Figure 10 represents a simple Use Case Diagram with the different user options available in the Web
Application. In addition, a sequence diagram of a request for a transfer between two different busses is
shown in Figure 11.
Figure 7: MySQL Tables Diagram
In order to achieve all the information needed to locate all the elements (buses, bus stops, etc.) and
calculate the remaining time for a bus to arrive at a specific stop, we are using the SkyeTek libraries .Net
API needed to work with the module SkyeTek M9.
Also, to run operations in the database, the JDBC API is being used. Fosstrak EPCIS Repository, as
we have already indicated above, being used for capture and information operations.
Finally, the Google Maps JavaScript API is being used in order to use Google Maps and be able to
locate buses with great accuracy within these maps. The RFID tag information, that is captured through
the antennas, is stored in a database that will be accessed by the application of Google Maps and thus be
able to show all that information in the Web Application.
It has also made the connection, configuration and subsequent control of RFID readers through the
Visual Studio environment. As mentioned above, this task was crucial because the location information
captured is stored in a MySQL database. From this information and through the Google Maps API, we
can locate all the buses in our Web Application.
A screenshot of the Web Application is displayed in Figure 12, for showing the route of line C bus
and their bus stops on the map, and the time left for reaching the rearest bus stop. As we can see, the Web
Application is divided into six different sections with the following options for our application: Index,
Schedule and Prices, Routes, Bus Stops, Route Calculation and Waiting Time.
15
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
Figure 8: UML Class Diagram
Figure 9: Communication between nodes: UML Deployment Diagram
16
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
Figure 10: UML Use Case Diagram
•Index. In this section, we briefly explain the Web Application.
•Schedule and Prices. This section includes several information about bus lines, bus stops, phone
numbers, points of interest and special bus lines.
•Routes. It show us the different routes of each bus lines.
•Bus Stops. The Web Application show us each bus stop on Google Maps. For that and following
the three-layer model, when we select a bus stop, the application sends a query to the DB server
and receives the information that it shows us on Google Maps. The Web Application allows to the
user filter by bus line to get only the bus stops of one single bus line.
•Route Calculation. This section allows to the user to select an origin bus stop and a destination
bus stop, and it calculates the most efficient route with the possibility of one transfer between two
different buses. Once the Web Application receives the information, it shows this information
(origin bus stop, destination bus stop, transfer between busses) on a Google Maps screen.
•Waiting Time. The last section show us the time left to arrive of a bus of a particular bus line to a
certain bus stop. Also, we can get the location of this bus on Google Maps and the route to arrive
to the actual bus stop.
6 Conclusions
The creation of a project based on a J2EE Web Application is proposed in this paper. The procedures
needed for accessing the databases using the Fosstrak EPCIS Repository to capture events according to
17
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
Figure 11: UML Sequence Diagram
the EPCglobal standard have been defined. Although, we have performed small scale tests and we are in
negotiations with local authorities for actual testing on a real urban environment.
Combining two technologies, RFID and GIS, the tracking system referred in previous works can be
improved and more features can be added, with the design of Web Services. Besides, we have been
integrated the tracking system in a Web environment as two Web Services, the monitoring of buses and
real-time information of the bus stops.
18
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
Figure 12: Web Application
In addition, a three-layer model is proposed for the development of our application. Additional simi-
lar applications can be developed by using the proposed model. Also we have used JavaScript functions,
which may be reusable in future works.
Our original motivation was to complete the development initially achieved by our research group in
the lower layers of the EPCIS standard, in order to advance through to the upper layers. Our previous
research was focused on developing hardware and networking middleware for RFID systems.
6.1 Discussion
In this section, we will perform a comparison among all the systems mentioned in this paper and ours,
indicating the advantages and disadvantages of the RUTMS system. Table 3 shows this comparison in a
more graphical way, including the applications we consider important in evaluating RUTMS.
The advantage of our system RUTMS consists on the use of the communications infraestructure of
the city itself. RUTMS can transmit data via LAN, WIFI or WSN. In this way, we have got no additional
expenses, as in cases where the position must be transmitted from the vehicle, usually via GSM, GPRS,
3G, 4G, etc.
In RUTMS, the installation of RFID readers in each bus stop can initially be more expensive than
installing GPS receivers and a mobile device to send the data in each bus. But in our case, we would
have an initial investment cost, but we would not have to pay for the communication lines of each bus
every month during the usual operation of the system.
19
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
Passenger
information
display
APP for
mobile
devices
Route
calculation
Transfer
between
buses
Number of
buses will
arrive to bus
stop
London
(iBus) 37 7 7 1
Sidney
(PTIPS) 37 7 7 1
Auckland
(RTPIS) 37 7 7 1
Glasgow
(BiAS) 37 7 7 2
BMS using
RFID and
WSN
37 7 7 1
RUTMS 3 3 3 3 2
Table 3: Systems comparative
In all systems, passengers are able to query bus information on screens installed at bus stops. Only
in BiAS and RUTMS systems, it is possible to check information about the next two buses at a particular
bus stop.
Besides the web environment in which we can calculate routes and a transfer between two buses, we
are also developing a new app compatible to all the operating systems for mobile devices (Android, iOS y
Windows Phone). This application will include the same options implemented for the Web environment
we have described previously. These two new contributions we have introduced in the proposed system
are not available in any of the related works mentioned in this paper.
One of the disadvantages of the RFID technology compared to GPS: the real-time position of each
bus is not available. But, as we have an adequate estimation of the time between stops, the problem is
reduced. Ibus, PTIPS, RTPIS and BiAS allow real-time location. While BMS using RFID and WSN and
RUTMS only allow estimated location of the buses when not in a bus stop.
Another disadvantage compared to the other systems is that the priority of the bus can not be changed
to be higher than the other vehicles. Though only, iBus, PTPS, RTPIS and BiAS have implemented this
application. In our system, this feature can be implemented by introducing a new device specifically for
this purpose, but this solution will make the proposed system more expensive.
6.2 Future Work
Our future work will consist on developing and integrating several sensors which can send data to a cen-
tral server so the application data can be stored in the tracking system. Besides, a filtering and collection
interface can be used in order to filter and collect raw tag reads, over different time intervals delimited
by several events defined by the EPCIS Capturing Application. Besides, as we are considering only one
transfer among buses, several transfers can be developed in future implementations of the tracking sys-
tem.
20
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
On one hand, we have considered only one transfer among buses, so several transfers can be devel-
oped in future implementations of the tracking system.
On the other hand, a WSN can be added to our system to know the number of passengers on the
bus in real time. With this information and the hours of passenger transport peak, each route can be
reinforced in their peak times of usage.
Additionally, the date provided by the sensors in the buses to get traffic information in real time can
be sent this to other buses or vehicles through WSN.
We are developing several sensors which can send data to a central server so the application infor-
mation can be stored. Besides, a filtering and collection interface can be implemented in order to filter
and collect raw tag reads, over different time intervals delimited by several events defined by the EPCIS
Capturing Application.
Our final intention is to develop an architecture and software tools in order to implement tracking
and tracing applications in different fields: logistics, people tracking and Wireless Sensor Networks.
6.3 Acknowledgments
This work was partially supported by Ministerio de Ciencia e Innovaci´
on (project BIA2009-10225) and
by Viceconsejer´
ıa de Ciencia y Tecnolog´
ıa - Junta de Comunidades de Castilla-La Mancha (Project
PII1I09-0134-5683).
References
[1] J. I. San Jose, J. M. Pastor, R. Zangroniz, and J. J. de Dios, “Rfid tracking for urban transportation us-
ing epcglobal-based web services,” IEEE AINA-2013 (IEEE 27th International Conference on Advanced
Information Networking and Applications), 25-28 March 2013, Barcelona (Spain), pp. 1295–1300. ISBN
978-0-7695-4952-1/13.
[2] A. Burlarley-Hyland, B. Toothill, and A. Das, “Use of automatic vehicle location systems, geographic in-
formation systems, and global positioning systems to increase efficiencies and decrease cost in maintenance
management,” Maintenance Management, pp. 46–54, 2012.
[3] O. Aloquili, A. Elbanna, and A. Al-Azizi, “Automatic vehicle location tracking system based on gis environ-
ment,” IET Software, vol. 3 (4), pp. 255–263, 2009. ISSN 1751-8814.
[4] M. Grewal, L. Weill, and A. Andrews, Global Positioning Systems, Inertial Navigation, and Integration.
Wiley-Interscience, 2007. ISBN 978-0-470-04190-1.
[5] K. Chang, Introduction to Geographic Information Systems. McGraw-Hill, 2010. ISBN 978-0-071-26758-8.
[6] J. Ebersp¨
acher, H. V¨
ogel, and C. Bettstetter, “General packet radio service (gprs),” GSM Switching, Services
and Protocols, Second Edition, pp. 241–269, 2001.
[7] RFIDJournal, “What is rfid?.” http://www.rfidjournal.com/article/view/1339, September 2005.
[8] P. Baronti, P. Prashant, V. Chooki, S. Chessa, A. Gotta, and Y. Fun Hu, “Wireless sensor networks: a survey
on the state of the art,” Computer Communications, vol. 30 (7), 2007.
[9] R. Glidden, C. Bockorick, S. Cooper, C. Diorio, D. Dressler, V. Gutnik, C. Hagen, D. Hara, T. Hass,
T. Humes, J. Hyde, R. Oliver, O. Onen, A. Pesavento, K. Sundstrom, and M. Thomas, “Design of ultra
low cost uhf rfid tags for supply chain applications,” IEEE Communications Magazine, no. 8, pp. 140–151,
2004.
21
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
[10] A. Garc´
ıa, Y. Chang, and R. Valverde, “Impact of new identification and tracking technologies in a distribu-
tion center,” Computers and Industrial Engineering, ScienceDirect, vol. 51 (3), pp. 542–552, 2006.
[11] EPCGlobal, “Epcglobal frequently asked questions.” http://www.gs1.org/docs/epcglobal/
Frequently_Asked_Questions.pdf, 2007.
[12] EPCGlobal, “Tag data standard (tds) v. 1.7.” http://www.gs1.org/sites/default/files/docs/tds/
tds_1_7-Std.pdf, 2013.
[13] G. Svennerberg, Beginning Google Maps API 3. Apress, 2010. ISBN 978-1-430-22802-8.
[14] G. Developers, “Google maps javascript v3 api.” https://developers.google.com/maps/
documentation/javascript/?hl=en, 2013.
[15] M. Castro, A. Jara, and A. Skarmeta, “Architecture for improving terrestrial logistics based on the web of
things,” Sensors, vol. 12 (5), pp. 6538–6575, 2012.
[16] N. Hounsell, B. Sherestha, and A. Wong, “Data management and applications in a world-leading bus fleet,”
Transportation Research Part C: Emerging Technologies, vol. 22, pp. 76–87, 2012.
[17] R. Clarke, T. Bowen, and J. Head, “Mass deployment of bus priority using real-time passenger information
systems in london,” Proc. European Transport conference, Leeuwenhorst, Netherlands, 2007.
[18] A. Mehaffey and G. Jarjees, “Preliminary trial results of the public transport information and priority system
(ptips),” Proc. 8th World Congress on Intelligent Transport Systems, Sydney, 2001.
[19] V. Vencatachellum, “Auckland’s signal pre-emption and real-time passenger information system.” http:
//www.ipenz.org.nz/ipenztg/papers/2003/11_Vadi_Vencatachellum.pdf, 2002.
[20] G. City Council, “The bus information and signalling system - bias.” http://www.glasgow.gov.uk/
index.aspx?articleid=5203, 2004.
[21] B. Ammar Hatem and H. Hamman, “Bus management system using rfid in wsn,” European and Mediter-
ranean Conference on Information Systems 2010 (EMCIS2010), 2009.
[22] D. Bajaj and N. Gupta, “Gps based automatic vehicle tracking using rfid,” International Journal of Engineer-
ing and Innovative Technology (IJEIT), vol. 1 (1), 2012.
[23] EPCGlobal, “Epc information services (epcis) version 1.0.1 specification.” http://www.gs1.org/gsmp/
kc/epcglobal/epcis/, 2007.
[24] F. E. Project, “Epcis architecture guide.” https://code.google.com/p/fosstrak/wiki/
EpcisArchitectureGuide, February 2012.
[25] D. Guinard, V. Trifa, S. Karnouskos, P. Spiess, and D. Savio, “Interacting with the soa-based internet of
things: Discovery, query, selection, and on-demand provisioning of web services,” IEEE Transactions on
Services Computing, vol. 3, no. 3, pp. 223–235, 2010.
[26] EPCGlobal, “The epcglobal architecture framework.” http://www.gs1.org/gsmp/kc/epcglobal/
architecture/, 2010.
[27] Towards Physical Mashups in the Web of Things, IEEE Xplore, 2009.
[28] R. Johnson, “J2ee development frameworks,” Computer, vol. 38 (1), pp. 107–110, 2005.
[29] V. Chopra, S. Li, and J. Genender, Professional Apache Tomcat 6. Paperback, August 2008. ISBN 978-0-
471-75361-2.
[30] P. Dubois, La Biblia de MySQL. Ed. Anaya Multimedia, 2007. ISBN 978-8-441-51558-1.
[31] T. E. Fundation. http://www.eclipse.org, 2013.
[32] M. Gousset, B. Keller, and M. Woodward, Professional Application Lifecycle Management with Visual Studio
2010. Wrox, 2010.
[33] SkyeTek, “Skyetek development apis.” http://www.skyetek.com/ProductsServices/
EmbeddedRFIDReaders/Firmware/SkyeAPI/tabid/419/Default.aspx, 2013.
[34] SkyeTek, “Skyemodule m9.” http://www.skyetek.com/ProductsServices/EmbeddedRFIDReaders/
SkyeModuleM9/tabid/208/Default.aspx, 2013.
[35] SkyeTek, “Skyetek c and .net api reference guide.” http://www.anyhing.com/rfdoc/eng/SkyeTekAPI_
Developers_Guide.pdf, April 2008.
22
WebServices Integration on an RFID-Based Tracking
System for Urban Transportation Monitoring San Jose, de Dios, Zangroniz and Pastor
Author Biography
Jose Ivan San Jose received his Master degree in Advanced Computer Technologies
from the University of Castilla-la Mancha in 2011. Currently, he continues his studies
as a PhD student and participates in several research projects, and he is a researcher
of Institute of Audiovisual Technologies in Cuenca (Spain) since 2010. His research
interests are RFID, Web Services, Internet of Things, Smart Objects and Wireless
Sensor Networks.
Juan Jose de Dios received the Ingeniero de Telecomunicaci´
on degree in 1991 and
the Doctor Ingeniero de Telecomunicaci´
on degree (PhD in Communications) summa
cum laude in 2004 from the E.T.S. Ingenieros de Telecomunicaci´
on of the Universi-
dad Polit´
ecnica de Madrid (Spain). Since 1999 he has been with the E. U. Polit´
ecnica
de Cuenca of the Universidad de Castilla–La Mancha (Spain). He is an associate pro-
fessor of television systems in the Department of Signal Theory and Communications.
Previously, he was working for Lucent Technologies (formerly AT&T) at the Trans-
mission Engineering Lab in Madrid (Spain) from 1991 to 1999. His professional interests include RFID
technology, image and video processing.
Roberto Zangroniz received the Science (Physics) degree in 1999, and the Electron-
ics Engineering degree in 2001, from the University of Valladolid, Spain. Roberto has
ample experience in the design and development of microcontroller driven devices.
His research interests include RF data communications applied to RFID, Wireless
Sensor Networks and, Real-Time Location Systems through the design of electron-
ics systems. In 2001, he joined the University of Castilla–La Mancha, where he is a
Lecturer of the Polytechnic school at Cuenca (Spain).
Jose Manuel Pastor was born in Leon, Spain. He received the Electronics and Auto-
matic Control Engineering degree from the Polytechnic University of Madrid (UPM)
in 1991. In 1992 he begins his doctoral research in Robotics in Construction Industry.
In 1996 Dr. Pastor moves to the Engineering Department of the Carlos III University
of Madrid. He received his Ph.D. in Robotics and Artificial Intelligence in 1997 from
the UPM. His research interests include RFID, factory automation, intelligent manu-
facturing and logistics systems. He is currently an Associate Professor at University
of Castilla-La Mancha, and director of Research Institute of Audiovisual Technologies.
23