With the Internet of Everything here among us, and GPS is ubiquitous in vehicles, and cars will have full internet capability, it will not be long before we have Smart Roads. Each road will have an IP address.
I began wondering what the data package would look like for Smart Roads, and then I was struck with the axiom that the best way to predict the future is to invent it.
So without further ado, I cracked together and XML file of what the Smart Road dataset would look like. Here is my first crack at creating a Smart Road Data Standard:
<?xml version="1.0" encoding="UTF-8"?>
<!-- Smart Road Markup Language version 1.0-->
<smart_road>
<!-- Main Element. It consists of a header, data and trailer elements. -->
<header>
<!-- Header Element. -->
<ref_number></ref_number> <!-- This could be a database Primary Key Identifier. -->
<country></country>
<state></state>
<province></province>
<county></county>
<township></township>
<ip6_address></ip6_address> <!-- Each Smart Road will have their own IP address. -->
<start_gps></start_gps>
<classification></classification> <!-- There could be subclassifications like carriageways etc. -->
<end_gps></end_gps>
<length_kms></length_kms>
<maximum_speed_limit></maximum_speed_limit>
<options></options> <!-- This could be a control element for suppressing some header info on subsequent exchanges. -->
</header>
<data> <!-- Message Section. -->
<data_sent>
<general_data> <!-- This section contains general data sent to the vehicles -->
<alerts>
<current_alerts></current_alerts>
<upcoming_alerts></upcoming_alerts>
</alerts>
<flags></flags>
<messages>
<alerts></alerts>
<construction></construction>
<law_enforcement></law_enforcement>
<traffic></traffic>
<weather></weather>
<misc></misc>
<user_specific>
<destination_address></destination_address>
<ack_flag> </ack_flag>
<message_payload></message_payload>
<delivery_receipt></delivery_receipt>
</user_specific>
</messages>
</general_data>
<location_specific_data><!-- This section contains location-specific sent to the vehicles -->
<current_gps_marker>
<current_maximum_allowable_speed></current_maximum_allowable_speed>
<alerts>
<current_alerts></current_alerts>
<upcoming_alerts></upcoming_alerts>
</alerts>
<flags></flags>
<messages>
<alerts></alerts>
<construction></construction>
<law_enforcement></law_enforcement>
<traffic></traffic>
<weather></weather>
<misc></misc>
<user_specific><!-- It is anticipated that if a vehicle's onboard messaging is not working, one can billboard messages -->
<!-- This can also be used to send violation notices and service-related messages to the vehicle -->
<destination_address></destination_address>
<ack_flag> </ack_flag>
<message_payload></message_payload>
<delivery_receipt></delivery_receipt>
</user_specific>
</messages>
</current_gps_marker>
</location_specific_data>
</data_sent>
<data_received>
<vehicle>
<type></type>
<description></description>
<direction></direction>
<velocity></velocity>
<timestamp></timestamp>
</vehicle>
</data_received>
</data>
<meta-data>
<!-- Big Data meta data on usage stats etc.-->
</meta-data>
<trailer>
<protocols_supported> </protocols_supported><!-- Various devices will have their own native Smart Road protocols -->
<device_types></device_types>
<end></end>
</trailer>
</smart_road>
This is just a first iteration. It needs to be tested and validated in real time. It is anticipated that the vehicle will send its GPS coordinates to the database defined by the IP address, and the location specific data will be returned.
No comments:
Post a Comment