Академический Документы
Профессиональный Документы
Культура Документы
Abstract—The Dedicated Short-Range Communications by means of RFID transponders. Major industrial suppliers
(DSRC) standards suite is based on multiple cooperating of electronic toll collection quickly discovered that further
standards mainly developed by the IEEE. In particular, we development on 915 MHz might pave the road for much
focus this paper on the core design aspects of DSRC which is
called Wireless Access in Vehicular Networks (WAVE). WAVE elegant breed of applications facilitating enhanced road safety
is highlighted in IEEE 1609.1/.2/.3/.4. The DSRC and WAVE and collision avoidance. The group of electronic toll suppliers
standards have been the center of major attention in both along with other stake holders formed a consortium focused
research and industrial communities. In 2008, WAVE standard on DSRC development. Coincidently, multiple studies on
was the third best seller standards in the history of the IEEE. vehicular safety and collision avoidance revealed that short-
This attention reflects the potential of WAVE to facilitate
much of the vehicular safety applications. In this paper we range communication (<300 feet) would be sufficient for most
present a fairly detailed tutorial of the WAVE standards. We safety application [3].
extend the paper by describing some of the lessons learned The DSRC community then attempted to standardize the
from particular design approaches. We direct the reader to 915 MHz using the ASTM framework but quickly thought
the landmark research papers in relevant topics. We alert the
reader about major open research issues that might lead to of the IEEE 802.11 approach and the 5.9 GHz as a direct
future contribution to the WAVE design. way to benefit from its ad-hoc mode. The ad-hoc mode of
IEEE 802.11 resembles the situation of vehicle-to-vehicle
Index Terms—DSRC, WAVE, ITS, 802.11p, VII, vehicular
communications, IntelliDriveSM . communications and hence, simplifies the development of
DSRC. Almost a decade of DSRC standards development
has resulted in the IEEE 802.11p standards along with IEEE
I. DSRC I NTRODUCTION AND H ISTORIC N OTES 1609.x, both standards represent together proposed DSRC
suite of standards.
TABLE I
DSRC VS . O THER W IRELESS T ECHNOLOGIE
E. Reference Model
To clarify the fairly complex DSRC design we present a
simplified reference model by dividing major WAVE architec-
ture into blocks. From a layered perspective, WAVE devices
employ almost common ISO/OSI stack as displayed in Figure
6. The figure illustrates a common communication stack and
identifies the related standard for both data and management
planes [14].
In Figure 6, we intended to avoid meandering details and
conserve the core model ideas. A typical communication stack
can be seen as two major planes, data plane and management
plane. Data plane is focused on processing of data like adding
or removing frame headers. Data Service Access Points (the
green SAPs on the right in Figure 6) define formal interfaces
between different data stacks. Management plane is focused on
communication commands such as synchronization, channel
switching, etc. Sizable part of WAVE standards are centered on
defining Management Service Access Point (the red SAPs on
the left in Figure 6) for each entity. Standardizing SAPs allow
plugging different entities. For instance, the SAP between
WME and WSE as shown in Figure 6 is defined in both 1609.3
[7] and 1609.2 [10].
In Figure 6, blocks highlighted in light blue represent the
focus of the WAVE standards. Blocks highlighted in dark blue
represent WAVE amendments to other standards. The green
Fig. 6. Simplified WAVE Communication Stack
blocks in the top right represent common WAVE interfaces
with established standards outside the DSRC. For simplicity,
WAVE applications are not presented in Figure 6. WAVE
IV. WAVE MAC S ERVICES
applications use common UDP/TCP interface stack.
It is important also to highlight the WAVE Short Message The following subsections illustrate the MAC layer services
Protocol WSMP since it is unique to DSRC. WSMP packets of the WAVE communications stack. The focus is on WAVE
may require special services like being transmitted using a par- QoS and MAC queues operations, Channel Coordination be-
ticular power or data-rate. These unique requirements impose tween different WAVE devices, and describing the different
challenges to the WAVE-MAC layer and below. The MAC and Types of WAVE Communications. WAVE QoS and channel
PHY layers must test the contents of each packet to adjust operations are fundamental to understanding and utilizing
radio power and data-rate before each packet transmission WAVE stack.
[18][14].
The WAVE Management Entity (WME) represents another
A. Quality of Service (QoS)
entity that is unique to WAVE standards and performs much
of the operations unique to WAVE standards. For instance, This subsection is focused on WAVE QoS by introducing
when data frames are scheduled, the transmission channel two main concepts, namely channel routing and channel
must be defined along with QoS priorities. Those priorities selector. Then the section discusses the use of user priority to
must allow an emergency safety message to be transmitted apply WAVE QoS. Finally, we discuss the main issues relevant
at anytime with very limited latency. Management of frame to WAVE QoS.
queuing, priority channels and handling of safety messages WAVE QoS captures the fundamentals of 802.11e and
are quite unique to WAVE standards. The WME handles those extends it to cover two channel operations. As illustrated in
particular processing in coordination with other design entities. Figure 3, the WAVE and 802.11p follow the 802.11e Enhanced
The WAVE Security Entity (WSE) provides management Distributed Channel Access (EDCA) QoS paradigm. One of
of data encryption mechanisms and key management. The the major additions in WAVE networks is the transmission of
WSMP also takes part in enforcing security policies besides WSMP packets. For each WSMP packet the WAVE standards
monitoring traffic patterns and responding to possible attacks dictate that it should be transmitted using:
[7]. 1) data-rate defined in-packet,
A sample scenario here would describe how different ven- 2) Channel number defined in-packet, and;
dors may implement and build WAVE devices. For instance, 3) Transmission power defined in-packet
one vendor might implement the blue boxes then use an of- The WAVE design extrapolates the 802.11e EDCA architec-
the-shelf stacks as illustrated by the green boxes of Figure 6. ture as illustrated in Figure 7 to service both IPv6 and WSMP
The stack illustrated in Figure 6 also facilitates the building packets. For simplicity, Figure 7 avoids details of management
of devices that employ cellular and WAVE at the same time. and signaling traffic.
MORGAN: NOTES ON DSRC & WAVE STANDARDS SUITE: ITS ARCHITECTURE, DESIGN, AND CHARACTERISTICS 509
the necessary TSF Timer Offset value, and sets the standard Fig. 10. Detailed Guard Interval
deviation to that of the standard deviation of the time output of
the GPS device under the given operating conditions [18]. A
slightly more complex implementation could use information be synchronized to UTC if it complies with the following
from the Timing Information Field in received WAVE service condition;
announcement to update an internal estimator of UTC time SyncT ol.
along with an estimation error variance (standard deviation) 3xTSF Timer Std Dev < 2
as outlined hereafter. Single-channel WAVE devices that are not synchronized to
The Timing Information Field is detailed in Figure 9. This UTC monitor the CCH continuously, do not offer services on
field holds information that can be used by recipients to SCH, and do not act as a Service Provider. If a WAVE device is
estimate UTC. The Timing Information Field includes the a member of a WBSS and is processing a transaction on SCH
Timing Capabilities, a TSF Timer Offset, and TSF Timer at the time when synchronization is lost, the device simply
Standard Deviation subfields. discontinues the ongoing transaction and reverts to monitoring
The Timing Capabilities subfield identifies the timing capa- the CCH.
bilities of the initiator WAVE device in terms of being single 5) Issues and Lessons Learned: Timing accuracy presents
/ multi-channel, having generated UTC through a GPS, and a cornerstone in the development of the WAVE standards.
having continuous time source availability. Roaming users are authenticated by presenting a security cer-
The TSF Timer Offset subfield contains the 2’s complement tificate that has a limited time span. A simple attack may copy
integer of the TSF timer offset in micro-seconds, which when a certificate, alter it, and reuse towards malicious objective.
added to the WAVE device’s TSF timer value generates the The limited time span of a certificate is essential to secured
WAVE device best estimate of UTC time at the instant when communication. The multiples of microsecond accuracy may
the first bit of the WAVE service announcement is transmitted be acceptable for current computing devices but it is inevitable
from the WAVE device’s antenna connector. The TSF Timer that higher accuracy will be needed in the future.
Standard Deviation subfield is an unsigned integer of number Time synchronization is critical to WAVE channel coordi-
of microseconds. This number represents the estimate of the nation. Evidently, this section included sufficient details on
standard deviation of the UTC error in the WAVE device’s es- the fairly complex WAVE synchronization mechanisms. The
timate of UTC time. When the TSF Timer Standard Deviation complexity, though, emanates from the initial decision to inter-
subfield is set to its maximum value (224), it indicates that the operate both single and multi-radios. This decision is based
value of the TSF Timer Offset subfield is meaningless. on the current availability and cost of short-range radios. In
The value of the TSF Timer Standard Deviation and the a forward look to the future version of the WAVE standards
TSF Timer Offset are function of various environmental and beyond the ’trial use’, one may assume the use of multi-radio
implementation factors; and may vary with time. At startup, that can listen to CCH while communicating on one or more
the TSF Timer Offset is set to zero and the TSF Timer SCH. This approach not only simplifies the design, it improves
Standard Deviation is set to its maximum value to indicate channel utilization by the following percentage:
that the TSF Timer Offset is currently invalid. Once a lower Enhancement % = (CCHI + 2GI) / Sync. Interval
variance source of UTC time becomes available, the new Another issue in the current design is the fact that it
source and its error variance are adopted as initial conditions utilizes limited band of the assigned spectrum at any point in
for the UTC estimator. time/location while leaving the majority of the assigned band
4) Synchronization Tolerance: Figure 8 illustrates the syn- unutilized. In an ideal design, a roaming multi-radio OBU may
chronization timeline in WAVE environment. Each CCHI and listen to CCH; communicate with an RSU on one SCH, while
SCHI starts by a GI (Guard Interval). Figure 10 details communicating with other OBUs on many different SCHs.
the GI to be the sum of Synchronization Tolerance and the It is especially intriguing to think of an adaptive algorithm
Max Channel Switch Time. The Synchronization Tolerance that allow OBUs to dynamically and autonomously locate and
is defined to be double the 95% probability threshold value utilize different SCHs based on sensing resource availability.
that determines whether a WAVE device is synchronized to We believe that developing such an algorithm facilitates the
UTC. The Max Channel Switch Time is the maximum time development of much alluring applications, especially V2V
the WAVE device takes to switch channels. applications [19].
Since local device clocks at two different devices may Then, another challenge may seem a little peculiar at first.
drift in opposite directions. WAVE devices are defined to A short-range wireless technology like WAVE may need
512 IEEE COMMUNICATIONS SURVEYS & TUTORIALS, VOL. 12, NO. 4, FOURTH QUARTER 2010
The user role is assumed by devices that join the WBSS On the other hand, persistent WBSS offers different sets
based on receipt of the announcement. A device may change of applications over time by altering the announced Provider
its role when it participates on a different WBSS. The terms Service Table (PST) during different CCH interval. To support
provider and user do not imply any particular behavior of the the dynamic PST feature, the announcement’s destination
applications once the WBSS is initiated or joined. A device MAC address is constrained to be the broadcast address.
can be a provider for one service and a user of another. Applications come and go from the provider’s WBSS as
3) WBSS Initiation and Operations: A WBSS is initiated triggered by the application request primitive. The provider
by the WAVE Management Entity (WME Figure 6) when a WME may also end a persistent WBSS as described in the
provider application redefines some of the WBSS parameters previous subsection.
like the persistence status. The announcing WAVE device User applications start and stop participation on a persistent
forms the Provider Service Table PST. As soon as a user appli- WBSS during its existence. The WME maintains a table of
cation starts on a WAVE device, it must register all services it active/inactive status of each participating application. The
might need with the local WME. Upon the receipt of a WAVE WME of the user WAVE device joins and ends local participa-
service announcement, the receiving WME checks whether the tion on the WBSS as required based on the user applications’
provider application, defined by the Provider Service Identifier status [7].
(PSID) in the announcement, is of interest to any locally 6) Issues and Lessons Learned: WAVE standards work-
registered user applications. User applications have the option group have decided to adopt the use of IPv6 as a network layer
to be informed of announcement containing both PSID match. protocol. The decision is fueled by the massive demands the
When a match is found, the WME takes one of two actions, DSRC environment imposes on the WAVE standards design.
depending on the user application registration parameter. In The number of roaming vehicles demanding IP addresses is
the simple case, the WME generates the necessary MAC simply beyond the IPv4 capabilities. Further, IPv6 approach
primitives to cause the local device to join the announced to managing mobility is much favorable compared to IPv4.
WBSS, by tuning device to the correct SCH at the correct time, The WAVE standards also uses both WBSS and non-WBSS
and by setting any other lower layer configuration parameters operations. Non-WBSS operations should not be confused
appropriately to support the communications. Alternately, the with the Independent Basic Service Set (IWBSS) which sup-
user application may choose to reconfirm before joining of ports decentralized wireless ad-hoc networks. It is widely be-
the announced WBSS. This gives the user application an lieved that a new WAVE-IWBSS operational mode is required
additional control level allowing any application to decline to facilitate fast, adaptive, self-configuring V2V communica-
participation in specific service if it has recently accomplished tions. Regrettably, current WAVE standards do not provide
some milestone objectives. any design mechanisms in response to such aspiration. That
Upon decision to join the announcing WBSS and as soon as ambitious is shared with other stakeholders and we believe
the communication parameters are set successfully, the WME WAVE-IWBSS mode will be part of next WAVE efforts.
sends a notification to the local user application. Subsequently, The IETF attempted to synchronize the development of both
the user application is free to generate WSMP or IPv6 data NEMO and MEXT standards with WAVE standards. NEMO
packets for transmission on the SCH. Received packets are (Network Mobility) and MEXT (MAC Layer Management
delivered up the WSMP or IPv6 stack. The WBSS stays in Entity) projects were established to resolve issues pertaining
place at the local device until it is terminated [7]. to mobility. Researchers must pay attention to the current
4) WBSS Termination: Once initiated, a WBSS stays in limitation and propose competitive solutions. One common
place at each participating device until locally terminated. disclaimer remains important since the WAVE standards do
WAVE devices may independently decide to leave a WBSS. not preclude the use of point-to-point mechanisms towards
There is no protocol exchange over the air interface to confirm V2V communications [19].
the end of a WBSS. The WAVE device WME may decide to WAVE service types have been developed with
issue a request to its MAC layer to leave a WBSS and to IntelliDriveSM architecture and applications in mind.
inform all the affected applications through a notification (i.e. The ideas of persistence and termination of WBSS are highly
process WBSS termination) in any of the following situations: relevant to the vehicular environment. Both mechanisms
• All applications indicate the completion of their activities, show how stringent environments impose specific design
via a request changing their status. constructs.
• Participation on a conflicting WBSS (e.g., on another Another issue of major concern here is scalability. The
channel) is required to support a higher priority appli- expected size of DSRC network is high enough to raise
cation. scalability concerns. The, interference with non-DSRC devices
• The lower layer indicates the SCH has been idle for a magnifies scalability concerns even further. Up to this date,
predefined amount of time, implying an irrecoverable loss there have been almost no publications on the issue of DSRC
of the WBSS scalability and load balancing. The reader is encouraged to
• The security credentials associated with the WBSS an- look at [22] and the scalability research on ad-hoc networks
nouncement expire at the user or are determined to be as it has closer resemblance to vehicular networks.
invalid when checked. Final comment here is relevant to IP address assignment
5) Changing WBSS Services: In a non-persistent WBSS, a and auto-configuration. While IP addressing is relevant to
provider application that is registered after issuing the initial the general WAVE architecture, it is important to realize that
WBSS cannot join the ongoing WBSS services. both WAVE and 802.11p are Link Layer Control standards.
514 IEEE COMMUNICATIONS SURVEYS & TUTORIALS, VOL. 12, NO. 4, FOURTH QUARTER 2010
Mechanism described in WAVE 1609.3 should be treated as show that some sort of authorization and authentication takes
mere recommendations, and users may or may not follow place. Similarly, some of the terms described hereafter are
it without violating the standards. We refer the reader to introduced to simplify reading. Our experience has shown
[23] and [24] for more mechanisms designed for the WAVE that reading through the standards drafts and RFCs with
environment. cluttered cross references and legally driven clauses can be
quite confusing. The approach we followed here simplifies
V. WAVE S ERVICES M ANAGEMENT reading, yet adheres wherever possible to the formal terms
used by the WAVE standards.
This subsection described WAVE service management The mechanism described hereafter illustrates how WAVE
which elaborates WAVE approach to managing services and devices grant application access to WAVE services. The fol-
providing applications with information on available services, lowing subsections detail the WAVE service management in
in addition to enforcing policies. The following subsections precise terms.
describe the process for application registration, WBSS man-
agement, and join policies. Then describe the WBSS status
transition and maintenance. We also describe how channel A. Application Registration and Removal
activities are being monitored. Finally, we discuss the main All applications must register, as a provider or user, with
issues pertaining to WAVE service management. its WAVE device WME before gaining services. Applications
As a general rule, the WAVE standards prohibit unregistered registered on the same WAVE device must have a unique
applications from gaining access to WAVE services. This PSID. This rule is not limited to WAVE-applications; it applies
rule improves WAVE security level compared to common even to typical IP-based data access. The only exception is that
WiFi standards. The few exceptions to this rule are explained unregistered WSMP provider application may send WSMP
hereafter. packets. WSMP user application must be registered to receive
Let’s define a provider device as a WAVE device that has any WSMP.
legitimate applications registered to offer WAVE services and The WME maintains a record of all registered applications
is also the initiator of a WBSS. A provider WAVE device in an Application Registration Table (ART). In other words,
is a sender of WSM. Then, define a user device as a WAVE the ART is merely the union of the local PST and the local
device that has legitimate applications registered to use WAVE UST.
services and is also the joiner of a WBSS. User WAVE device ART = (local PST ∪ local UST)
is a receiver of WSM. Before accepting new application registration the WME
A Provider-Service-Table (PST) is a collection of data confirms that the new application is unique and has the
describing all applications registered with a WAVE device to, necessary security credentials to gain the required access to
legitimately, offer services. Provider applications must register its WAVE media. Applications failing to satisfy the two con-
with the WAVE device using its Provider-Service-ID (PSID). ditions are denied registration and receive registration denial
Each provider WAVE device builds its own PST and maintains message. Otherwise, applications are registered and receive a
it over time. confirmations message.
Similarly, a User-Service-Table (UST) is a collection of data The ART table is maintained by the WME which monitors
describing all applications registered with a WAVE device to, an application status field. The WME uses the application
legitimately, use services. User applications must register with status field to monitor the active/inactive status. Other fields
the WAVE device using its User-Service-ID (USID). Each user maintain operational information like the IPv6 notification
WAVE device builds its own UST and maintains it over time. address, port and priority. Any Application can remove its
A provider WAVE device announces its PST. When a user registration by sending a message to the WME. In such a case,
WAVE device locates the provider’s WBSS it extracts the the WME removes the application registration entry from the
provider PST; and then, the user WAVE device compares the ART. If the ART contains no active applications the WME
set of PSID available in the provider PST with its own UST ends the current WBSS [7].
that is available through its WME and contains local USID
of applications demanding service. The user WME generates
a new table of applications with matching interests. This new B. WBSS Management
table represents the set of applications that are allowed to have Generally, all WBSS are established on the CCH. But based
WAVE services. on an application request, a WAVE device may establish the
Before we go any further, three notes are important here. WBSS on a SCH, and announce its presence on the CCH
First, the WAVE standards use the term PST to describe in order for other devices to join that WBSS. All WBSS are
both PST and UST. Second, the WAVE standards use the initiated based on service priority and the availability of radio
term PSID when referring to both PSID and USID. We resources. A WBSS can be newly established or it can be a
thought that distinguishing the terms into PST, PSID, UST, modification to existing persistent WBSS.
and USID alleviates confusion. Finally, the use of the term Another important table is the Application of Interest Table
‘legitimate’ in this section indicates an exchange of signed (AOIT). As soon as a user device discovers a new WBSS, it
security certificate. Section V.D illustrates the use of time-out uses the remote PST it receives via WBSS and its local UST
mechanism to issue and revoke those certificates. To simplify to generate the AOIT as follows:
the reading of this section, we use the term ‘legitimate’ to AOIT = (remote PST ∩ local UST)
MORGAN: NOTES ON DSRC & WAVE STANDARDS SUITE: ITS ARCHITECTURE, DESIGN, AND CHARACTERISTICS 515
management. We described the use of channel coordination, CRL Certificate Revocation List
WAVE communication types and WBSS policies in plain CSMA/CA Carrier Sense Multiple Access with Col-
language. We guided the reader into specific subjects that lision Avoidance
require further research hoping to motivate researchers to join DSRC Dedicated Short-Range Communica-
and contribute to the next work on the WAVE standards. In tions
many cases, we identified the lessons learned from developing EDCA Enhanced Distributed Channel Access
the current standards and defined why specific design choices GPS Geographical Positioning Systems
have been made. I2V Infrastructure-Vehicle Communications
IETF Internet Engineering Task Force
Lately, some cynical reviews of DSRC have been published Intelli-
in business magazines. A common set of arguments are shared
DriveSM Vehicle-Infrastructure Integration
by most skeptics. For one, the use of term ’trial use’ shaped
IWBSS Independent Basic Service Set
the opinion that DSRC cannot be ready soon enough, and LoS Line of Sight
therefore, it is better to rely on alternative technology that can
MAC Media Access Control
deliver now. A second argument is the lack of agreement on MEXT Mobility EXTensions for IPv6
various technical issues like WAVE service layer and security.
MLME MAC Layer Management Entity
A third argument stems from common misunderstanding of
NEMO Network Mobility
the exact role DSRC plays and how various wireless tech- OBU On-Board Unit
nologies complement each other. Another argument questions
PHY Physical Layer
the feasibility and the cost of deployment.
PKI Public Key Infrastructure
We maintain the view that DSRC is the base technology for PLME Physical Layer Management Entity
future vehicular safety communications. Currently, DSRC is PSC Provider Service Context
gaining popularity among researchers and most know technical PSID Provider Service ID
issues are resolvable. Misconceptions about the technology PST Provider Service Table
will clear up as we promote DSRC in more and more technical RFC Request for Comments
and business gatherings. Parallel efforts on business, legal RFID Radio Frequency Identification
and legislative fronts will shape up the business models, RSU Road-Side Unit
address distractive concerns, and build up the case for gradual SAP Service Access Point
deployment. SCH Service Channel
Perhaps the most powerful support behind DSRC comes SCHI Service Channel Interval
from two facts. First, the astute and well-crafted relation TSF Timestamp Field
between IntelliDriveSM and DSRC which illustrate a situation USID User-Service-ID
where both IntelliDriveSM and DSRC fuel and support the UST User Service Table
success of each other while the failure of either initiative is UTC Coordinated Universal Time
not expected to drag the other one. The DSRC has been build V2V Vehicle-Vehicle Communications
with IntelliDriveSM in mind and therefore, offered services VII Vehicle-Infrastructure Integration
that are not available in WiMAX, WiFi, or cellular networks. WAVE Wireless Access in Vehicular Env.
Another strong point in supporting DSRC is the availability of WBSS WAVE Basic Service Set
75 MHz bandwidth around the 5.9 GHz dedicated for safety Wifi IEEE 802.11 Wireless LAN Standards.
applications. In a conservative estimate, the DSRC bandwidth WiMax IEEE 802.16 Wireless LAN Standards.
is evaluated to more than $20 Billion. It would be irrational WME WAVE Management Entity
to shun this value because the system is not ready right now. WSA WAVE Service Announcement
WSE WAVE Security Entity
WSMP WAVE Short-Message Protocol
R EFERENCES
VII. G LOSSARY OF T ERMS
[1] National Center for Statistics and Analysis, “Traffic safety facts 2003,"
Report DoT HS 809 767, Nat’l. Highway Traffic Safety Admin., U.S.-
DoT, Washington, DC, 2004.
AAT Active Application Table [2] US Department of Transportation, National Highway traffic Safety
ACI Access Category Index Admistration, “Vehicle safety communications project", Final Report,
AOIT Application of Interest Table Apr. 2006.
[3] NHTSA, ITS Joint Program Office, “Report to Congress on the National
ASTM American Society for Testing & Mate- Highway Traffic Safety Administration ITS Program, Program Progress
rials During 1992-1996 and Strategic Plan for 1997-2002," U.S. Department
ART Application Registration Table of Transportation, Washington, DC, Jan. 1997.
[4] T. Willke, P. Tientrakool, and N. Maxemchuk, “A survey of inter-vehicle
CCF Channel Coordination Function communication protocols and their applications," IEEE J. Commun.
CCH Control Channel Survey Turorials (JCST), vol. 11, no. 2, 2009.
CCHI Control Channel Interval [5] J. G. Jordán, F. Soriano, D. Graullera, and G. Martín. “A comparison
of different technologies for EFC and other ITS applications", in Proc.
CICAS Cooperative Intersection Collision IEEE Intelligent Transportation Syst. Conf., pp. 1172-1177, Oakland
Avoidance Systems USA, Aug. 2001.
518 IEEE COMMUNICATIONS SURVEYS & TUTORIALS, VOL. 12, NO. 4, FOURTH QUARTER 2010
[6] IEEE 802.11p SWG et al, “Draft amendment to standard for information [23] M. Fazio, C. Palazzi, S. Das, and M. Gerla, “Facilitating real-time
technology - telecommunications and information exchange between applications in VANETs through fast address auto-configuration," in
systems - local and metropolitan networks - specific requirements - Proc. 4th IEEE Consumer Commun. Netw. Conf. (CCNC-07), pp. 981-
part 11: Wireless LAN medium access control (MAC) and physical 985, Las Vegas-USA, Jan. 2007.
layer (PHY) specifications: Ammendment: Wireless access in vehicular [24] M. Fazio, S. Das, C. Palazzi, and M.Gerla, “Automatic IP address
environments," IEEE 802.11p D6.0, June 2009. configuration in VANETs", in Proc. 3rd ACM International Workshop
[7] IEEE P1609.3 SWG et al, “Wireless access in vehicular environments Veh. Ad Hoc Netw. (VANET 2006), MOBICOM-06, Los Angeles-USA,
(WAVE) networking services," IEEE P1609.3 D1.2, June 2009. Sept. 2006.
[8] IEEE P1609.4 SWG et al, “IEEE P1609.4 trial-use standard for wireless [25] G. Golden and Richard III, “Service advertisement and discovery:
access in vehicular environments (WAVE) - multi-channel operation," Enabling universal device cooperation," IEEE Internet Computing Mag.,
IEEE P1609.4 D12, June 2009. vol. 4, no. 5, pp. 18-26, Oct. 2000.
[9] IEEE P1609.1 SWG et al, “IEEE P1609.1 trial-use standard for wireless [26] I. Sedov, S. Preuss, C. Cap, M. Haase, and D. Timmermann, “Time
access in vehicular environments (WAVE) resource manager," IEEE and energy efficient service discovery in bluetooth," in Proc. 57th IEEE
P1609.1 D0.6, June 2009. Semiannual Veh. Technol. Conf. (VTC-03-Spring), vol. 1, pp. 418-422,
[10] IEEE P1609.2 SWG et al, “IEEE P1609.2 trial-use standard for wireless Jeju Island-Korea, Apr. 2003.
access in vehicular environments - security services for applications and [27] Z. Yue and L. Kwei-Jay, “Hierarchical management of service account-
menegement messages," IEEE P1609.2 D07, June 2009. ability in service oriented architectures," in Proc. IEEE International
[11] J. Mar, C. H. Chou, C.C. Kuo, Y.R. Lin, “A pilot sub-carrier-aided Conf. Service-Oriented Comput. Appl. (SOCA-07), pp. 55-64, June 2007.
frequency equalizer for the dedicated short-range communications sys- [28] M. Raya and J.P. Hubaux, “The security of vehicular ad hoc networks,"
tem over time-varying fading channels," in Proc. Management Technol. in Proc. 3rd ACM Workshop Security Ad Hoc Sensor Netw., Workshop
Forum, China Commun., pp. 33-41, Dec. 2006. Security Ad Hoc Sensor Netw., Alexandria USA, pp. 11-21, 2005.
[12] J. Liu; J. Li, “Packet design and signal processing for OFDM-based mo- [29] K. Tokuda, “Impact of security/AAA on Intelligent transport systems,"
bile broadband wireless communication systems," IEEE Trans. Mobile J. Wireless Personal Commun., vol. 22, no. 2, pp. 245-251, Springer
Comput., vol. 5, no. 9, pp. 1133-1142, Sept. 2006. Netherlands, Aug. 2002.
[13] T. Tsuboi, J. Yamada, N. Yamauchi, M. Hayashi, “Dual receiver [30] X. Lin, R. Lu, C. Zhang, H. Zhu, P. Ho, and X. Shen, “Security in
communication system for DSRC," 2nd Int’l Conf. Future Generation vehicular ad-hoc networks," IEEE Commun. Mag., vol. 46, no. 4, pp.
Commun. Netw., FGCN-08, vol. 1, pp. 459-464, Sanya-Hainan Islannd, 88-95, July 2008.
China, Dec. 2008. [31] J.P. Hubaux, S. Capkun and J. Luo, “The security and privacy of smart
[14] C. Cseh; “Architecture of the dedicated short-range communications vehicles," IEEE Security Privacy Mag., vol. 2, no. 3, pp. 49-55, 2004.
(DSRC) protocol," in Proc. IEEE 48th Veh. Technol. Conf. VTC-98, [32] M. Wolf, A. Weimerskirch, and C. Paar, “Security in automotive bus
vol. 3, pp. 2095-2099, Ottawa-Canada, May 1998. systems," in Proc. Embedded Security Cars Workshop (ESCAR-04),
[15] Y. Morgan and T. Kunz, “The full ESWAN destination-based approach; Bochum Germany, Nov. 2004.
operations and evaluation," J. Inf. Commun. Technol. JICT, Special Issue [33] J. Yin, T. ElBatt, G. Yeung, B. Ryu, S. Habermas, H. Krishnan and
Cross-Layer Design Multi-hop Wireless Netw., vol. 3, no. 2, Oct. 2007. T. Talty, “Performance evaluation of safety applications over DSRC
[16] Y. Morgan and T. Kunz, “PYLON-lite: QoS model for gateways to ad- vehicular ad hoc networks," in 1st ACM International Workshop Veh.
hoc network," J. Special Issue Recent Advances Wireless Netw. Syst., Ad Hoc Netw., International Conf. Mobile Comput. Netw., Philadelphia,
Comput. Electrical Eng. J. CAEE, vol. 32, no. 1-3, pp 68-87, Oct. 2005. USA, pp. 1-9, 2004.
[17] H. Anh, J. Kim, W. Cho, J. Choi, K. Lim and J. Kwak, “A robust and [34] B. Lee, C. Yim, D. Ahn, and D. Oh, “Performance evaluation of the
low-complexity timing synchronization algorithm for a DSRC system," physical layer of the DSRC operating in 5.8 GHz frequency band," J.
in Proc. 2nd IFIP International Conf. Wireless Optical Commun. Netw. Electron. Telecommun. Research Institute (ETRI), vol. 23, no. 3, pp.
WOCN-06, Tashkent- Uzbekistan, Apr. 2006. 121-128, Sept. 2001.
[18] International Radio Consultative Committee (CCIR), “Report 517, Stan-
dard Frequency and Time-Signal Emissions: Detailed Instructions by
SWG-7 for the Implementation of Recommendation 460 Concerning
the Improved Coordinated Universal Time (UTC) System, January
1972, XIIth Plenary Assembly CCIR," New Delhi, India 1970, Geneva, Dr. Y. Morgan is a known researcher with man-
International Telecommun., 1970, vol. III, 258a-258d; reprinted in ifest contributions in the area of mobile vehicular
Time and Frequency: Theory and Fundamentals, U.S. Monograph 140, communications. Dr. Morgan received his Ph.D.
Washington, D.C., U.S. Govt. Printing Office, 1974, 32-35. Reprinted by from Carleton University and has taught in Carleton
Geneva, International Telecommun. Union, Radio Comm. Bureau 1998. University and University of Regina. Dr. Morgan
[19] S. Biswas, R. Tatchikou; and F. Dion, “Vehicle-to-vehicle wireless is focused on research related to Vehicular Ad-
communication protocols for enhancing highway traffic safety," IEEE Hoc Networking VANET especially pertaining to
Commun. Mag., vol. 44, no. 1, pp. 74-82, Jan. 2006. 5.9 GHz DSRC and IntelliDrive initiatives.
[20] M. Umemoto; “An experimental DSRC multimode terminal using soft- Dr. Morgan had been part of the IEEE 802.11p
ware defined radio technology," in Proc. IEEE Radio Wireless Conf. standards group and the IEEE 1609.0/.1/.2/.3/.4/.5
RAWCON-2001, pp. 165-168, Aug. 2001. groups as well. He authored and co-authored many
[21] A. Yokoyamai and H. Harada; “Implementation of multi-channel modem research papers in addition to contributions to standards like 3GPP, IETF,
for DSRC system on signal processing platform for software defined IEEE, and IEEE-SA. Dr. Morgan is also an active member and reviewer in
radio," Special Section Software Defined Radio Technol. Applications, the VTC and the VTS societies that are focused on vehicular transportation
IEICE Trans. Commun., vol. E89-B, no. 12, pp. 3225-3232, Nov. 2006. systems and applications.
[22] Y. Toor, P. Mühlethaler, A. Laouiti and A. De La Fortelle, “Vehicle The objective of Dr. Morgan research is to develop real-time effective and
ad hoc networks: Applications and related technical issues," IEEE J. secure communications. He is also interested in modern and revolutionary
Commun. Survey Tuts. (JCST), vol. 10, no. 3, pp. 74-88, 2008. architecturs focused on nontraditional and obscure networks.