over particular roads and crossings, measuring the
number of mobile phone users within a particular
tower’s range and then converting this information
to the vehicular traffic conditions in that area. Such
systems are not only dependent on statistical
assumptions but also require large investment in new
infrastructure that doesn’t make them readily
deployable.
3 PROPOSED TRAFFIC
INFORMATION SYSTEM -
OTIS
In the proposed system, a mobile phone user will be
able to send and receive traffic updates using SMS
(Harris 2003). Figure 1 illustrates the interaction of
OTIS with the mobile station (MS). The various
processes that will be involved in OTIS are
discussed below.
3.1 Receiving Traffic Information from
Mobile Users
The user can generate an SMS indicating the traffic
conditions on the road and send it to a predefined
number. Since the current technology cannot
ascertain the area information of a user sending an
SMS, the user will also have to message his location
along with the traffic update. The receiving short
message entity (SME), i.e. OTIS in this case, will
continuously store and process all incoming traffic
updates.
The form of the incoming traffic information
SMSs will determine the complexity of the
processing step in OTIS. Therefore, it is essential to
strike a balance between user’s convenience in
generating a traffic condition message and the
system’s ability to correctly interpret the message in
a timely manner. A plain English language message
will require natural language processing, filtering,
matching and estimation capabilities whereas a
keyword based message would be much simpler to
process. Although it seems that a natural language
message will be more convenient for a user it may
not always be so. For instance, if the user wishes to
inform to the system that traffic in area X is heavy
then a natural language form of the message would
be something like ‘heavy traffic in area X’.
However, if a keyword based format is used where
the keyword 3 indicates heavy traffic then the same
message can be written in the form – ‘3 area X’ –
which is clearly much easier and faster for the user
to type and at the same time makes the processing
easier and unambiguous. This paper suggests a part
keyword, part English format - <keyword>
<location> - as illustrated in the right column of the
table in figure 2.
3.2 Processing Traffic Information
This is the most crucial step of the system where all
the updates will come together and be consolidated
to generate meaningful and correct information.
Assuming the format of the incoming SMS as
proposed in this paper, the first keyword of the
incoming message could indicate the level of
congestion, while the following text could refer to
the location. A database of known locations and
roads could be created and the incoming messages
could be processed to ascertain which locations are
being referred to. A way to measure traffic condition
of a location could be to take sum of all the traffic
status keywords belonging to the same location.
Then, a higher sum would indicate more traffic
congestion and an appropriate update could be
generated and dispatched to the users. However, it is
important that only messages within a predefined
timeframe are considered for generating
information. For instance, if a 10 minute time
window is chosen then all updates received within
this time slot will affect the traffic status for that
period after which they will become void. This
means that although the traffic status of a location
would be continuously updated, only those SMSs
received within a particular time slot will be used for
the calculation. This would prevent old information
from affecting the current traffic status.
3.3 Propagating Updates to Mobile
Users
Many schemes may be employed to send traffic
updates to the mobile users. The users may choose
to receive updates at regular intervals or send
explicit requests to receive traffic updates. In the
latter case a user may send an SMS to the system
requesting a traffic update using the <keyword>
<location> format. Here the location is the place for
which the user seeks traffic information and the
keyword could be a predefined number, such as ‘0’,
to indicate to the system that the incoming message
requests a traffic update. Figure 3 summarizes the
processes of receiving, processing and propagating
information in the data flow diagram of the system.
WINSYS 2008 - International Conference on Wireless Information Networks and Systems
234