SAFESPOT SP2 Workshop CRF – Antonio Scopelliti www.safespot-eu.org safespot@crf.it SAFESPOT

It will cover four different aspects: Agenda This slideshow would be a little overview about comunication Among SPs, LDM and Sintech Router. It will cover four different aspects: RSU “black-boxes” SPs Layout from comunication point of view. A very little introduction to Sintech Router LDM requirements A general presentation about SPs and Router interactions A summary of hardware and software installation requirements for Sintech Router

SP2 SP3 SP5 LDM Sintech Router LAN Part 1: RSU Layout SP2 SP3 SP5 LDM Sintech Router TCP LAN UDP TCP is used to access LDM through API UDP is used for messages exchanging between Sintech Router and other SPs.

Part 2: How Router and LDM work together Sintech Router egomotorvehicle egorsu Even if LDM and Sintech Router are parts of the same SP, usually they’re physically located on different PCs. Sintech Router reads only 2 of Tables included in LDM: egomotorvehicle and egorsu egomotorvehicle is used only for initialization purposes (NodeId & NodeType)

Sintech SP5 Router UDP Part 3: A deeper look… MsgManager UDP HMI Message Application layer uses MsgManager for comunication from/to Sintech Router, through a set of UDP Messages. SP5’s MsgManager handles two kinds of Messages: HMIEvent and HMIPeriodic: HMIEvent is usually a single message (which could be both a broadcast or unicast message) used to comunicate a specific situation occurring through VANET HMIPeriodic has the same data structure of HMIEvent, but it’ll be re-transmitted several times according to its period and TTL. MsgManager requests Sintech Router for HMI Transmission through VANET (Wireless).

A deeper look… (2) Sintech Router SP5 AbortEventMessage MsgManager UDP SendHmiEventMessage Sintech Router according to its internal rules (Congestion Control and Addressing Checking), could Accept or Reject VANET Transmission. Once Sintech Router received an HMI Transmission request from SP5’s MsgManager, it could send a reply message according to the action performed: HMIEvent (SendHmiEventMessage): Message sent: no reply! Message rejected: AbortedEventMessage

Sintech SP5 Router UDP A deeper look… (3) HMIPeriodic: AbortPeriodicMessage MsgManager UDP StartSendingHmiPeriodicMessage HMIPeriodic: In order to enque a Periodic Message SP5’s MsgManager send to router a StartSendingHmiPeriodicMessage. This message has the same data structure of SendHmiEventMessage plus period and TTL info. Above message is enqued by Router in a Periodic Sending Table. Each “period” message is handled by router to be sent as for HmiEvent and re-enqued in Periodic Sending Table. If HmiPeriodic could not enqued, an AbortedPeriodicMessage is sent to SP5’s MsgManager. Router could decide to not re-enque a HMIPeriodic previously enqued in Periodic Sending Table, according to Congestion Control or HMIPeriodic TTL (message validity time is expired). In this case an AbortedPeriodicMessage is sent to SP5’s MsgManager.

Sintech SP5 Router UDP HMIPeriodic: A deeper look… (4) Sintech Router SP5 HMIPeriodic FrequencyChangedForPeriodicMessage MsgManager UDP ChangeFrequencyForPeriodicMessage HMIPeriodic: SP5’s MsgManager could change HMIPeriodic frequency sending a ChangeFrequencyForPeriodicMessage to Router using messageID in order to select which HMIPeriodic frequency to change. Router re-enque HMIPeriodic with new period and replies to a message with an FrequencyChangedForPeriodicMessage.

Sintech SP5 Router UDP HMIPeriodic: A deeper look… (5) Sintech Router SP5 HMIPeriodic AbortedPeriodicMessage MsgManager UDP StopSendingPeriodicMessage HMIPeriodic: MsgManager could choose to stop HMIPeriodic sending before validity period expires, sending a StopSendingPeriodicMessage to Router using messageID in order to select which HMIPeriodic to stop. Router doesn’t re-enque HMIPeriodic and replies to a Stop message always with an AbortedPeriodicMessage.

Sintech Router SP2 UDP UDP A deeper look… (6) Sintech Router SP2 to LDM UDP UDP VanetMsg2UDP LDMObject Incoming VANET messages (wireless), direct to egonode (broadcast or unicast to the egonode) are packed to UDP messages and feeded to SP2 for LDM filling. Feeded Messages could be both Beacon or Generic Messages from Vehicle (Event, Periodic or Emergency). Feeded Message should be supported by SP2 in order to update LDM fields.

Part 4: Sintech Router installation Hardware requirements: Alix.3C board (AMD Geode LX800, VGA, 256MBytes RAM, 1xLAN, 2xminiPCI-x, 2xUSB) 4GBytes CompactFlash for storage IEEE802.11p (or IEEE802.11a) compliant miniPCI-x wireless board (for example QFree 802.11p sample board) SMA Female - Pigtail* *: Using QFree 802.11p sample board you need an UF-L to SMA-female pigtail adapter. Other cards could require different pigtails.

Sintech Router installation (2) Software Requirements: Fedora* or another RedHat-based linux distro (Fedora 8 or later is required for IEEE802.11p driver installation). openNTP (for time sync). Postgresql libraries (for accessing LDM). Trolltech QT4 (used by Sintech router executable) *: Required to use Sintech Router prebuilt packages and configuration scripts. Not required for self-made builds and configurations.

Sintech Router installation (3) Other (external) Requirements: A running LDM compliant to LDM’s schemes Rev7.0 or later (used for router startup and beaconing). Position data (longitude, latitude, position TimeStamp and so on) are retrieved from EgoPositioning UDP Message. This Message in Vehicle is sent from Positioning PC. In RSU there’s no Positioning PC, so you need any kind of system to provide (at least) this message once after Sintech Router Started up! A NTP server for time Sync.

Thanks For Your Attention End Thanks For Your Attention