IEEE 1609.1:2006 pdf free download – IEEE Trial-Use Standard for Wireless Access in Vehicular Environments (WAVE) – Resource Manager
1.2 Purpose
The purpose of this standard is to enable complete interoperability of applications using WAVE in a mannerthat simplifies the onboard vehicle systems, reducing cost and improving performance.Effective use of thememory pages by applications can also minimize configuration management issues over the life of a system.
This standard is intended to cnable a wide range of applications to be supported by an OBU of the lowestpossible cost. The low cost is enabled by removing the need for the OBU to interpret application messages.There is no OBU software representing applications using RM; thus the processing，memory，andconfiguration management requirements are removed from the OBU.Instead of putting such processingrequirements on the OBU, they are placed on the RSU or an application processor remote from the RSU.The only processing requirement is that of interpreting the specific commands and message headers definedherein, which is application independent. The OBU merely serves as a mobile mailbox to carry applicationmessages and data from one RSU to another or as a common interface point to transfer data to other onboardsystems.
By allowing memory to be assigned to an application at any time during the life of the OBU, futureapplications can be developed and deployed without onboard hardware or software modification.
For applications using RM as a mobile mailbox, with no onboard use of the data stored in memory, there aresignificant security advantages.By having the OBU treat each application’s messages as a bit-stream to besaved and later retrieved from memory, such data can be encrypted in a manner that is not known to theOBU.There is no need for the OBU to support the encryption schemes used by these applications, and suchsecurity schemes can be under the total and absolute control of each of these applications.
All remote access to pages is via a secured RF link. Some pages are accessible to all RMAs;others areregistered to a specific RMA and accessible only to that RMA. Such registration is in accordance withAnnex B. Registered pages are allocated to a specific RMA across a set of OBUs and are consideredresources accessible to the RMA to which they are registered. The management is done using the set ofcommands specified in Clause 6. Some of the pages are defined so that storing data on, and retrieving datafrom, them performs the management of Uls that are part of, or connected to, the OBU.These pages are saidto be memory-mapped to the UI. Some pages are defined so that they act as a communication buffer betweenthe OBU and onboard equipment or network interfaced to the OBU. These pages are known as transferpages.Writing data to transfer pages initiates the transfer of these data to the associated equipment ornetwork. As well, the equipment or network associated with the interface may write data onto this or anotherpage allowing these data to be read by the associated RMA to complete the interchange.
This standard, by defining a command set that provides access to pages and by specifying that each resourcebe mapped to a page, allows any RMA, by the use of the command set, to manage in a standardized andinteroperable manner all OBU RCP resources to which it has access.
Figure l illustrates that there is a two-stage process involved in the interchange of commands and responses.One stage is from RMA to RM via defined application protocol data unit (APDU); the other is from RM toRCP through a set of commands and responses. Commands,encapsulated and transmitted by the RMA inAPDUs over a network,are received by the RM. Upon receipt,the RM extracts the commands andencapsulates them in User Datagram Protocol (UDP) packets that it transmits，via the RF link，to thespecified OBU’s RCP.Upon receipt, the RCP executes the commands and returns the appropriate responsesto the RM, encapsulated in UDP packets. The RM, in turn, extracts and reencapsulates the responses inAPDUs for transmission to the RMA.The APDUs are described in Clause 7.The commands and responsesare described in Clause 6.