<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
     which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- One method to get references from the online citation libraries.
     There has to be one entity for each item to be referenced. 
     An alternate method (rfc include) is described in the references. -->

<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2629 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2629.xml">
<!ENTITY RFC3552 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3552.xml">
<!ENTITY RFC5226 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs), 
     please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
     (Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space 
     (using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="info" docName="draft-zhang-t2trg-accident-blockchain-00" ipr="trust200902">
  <!-- category values: std, bcp, info, exp, and historic
     ipr values: trust200902, noModificationTrust200902, noDerivativesTrust200902,
        or pre5378Trust200902
     you can add the attributes updates="NNNN" and obsoletes="NNNN" 
     they will automatically be output with "(if approved)" -->

  <!-- ***** FRONT MATTER ***** -->

  <front>
    <!-- The abbreviated title is used in the page header - it is only necessary if the 
         full title is longer than 39 characters -->

    <title abbrev="Collecting traffic accident information">Architecture for collecting traffic accident information based on blockchain
    </title>

    <!-- add 'role="editor"' below for the editors if appropriate -->

    <!-- Another author who claims to be an editor -->

    <author fullname="Ru Li" initials="R"
            surname="Li">
      <organization>Inner Mongolia University</organization>
      <address>
        <postal>
          <street></street>
          <!-- Reorder these if your country does things differently -->
          <city>Hohhot</city>
          <region></region>
          <code>010021</code>
          <country>China</country>
        </postal>
        <phone>+86 15804712558</phone>
        <email>csliru@imu.edu.cn</email>
        <!-- uri and facsimile elements may also be added -->
      </address>
    </author>

    <author fullname="Xiaodong Zhang" initials="X" role="editor"
            surname="Zhang">
      <organization>Inner Mongolia University</organization>
      <address>
        <postal>
          <street></street>
          <!-- Reorder these if your country does things differently -->
          <city>Hohhot</city>
          <region></region>
          <code>010021</code>
          <country>China</country>
        </postal>
        <phone>+86 15247168840</phone>
        <email>cszxd@imu.edu.cn</email>
        <!-- uri and facsimile elements may also be added -->
      </address>
    </author>

    <author fullname="Jun Fan" initials="J"
            surname="Fan">
      <organization>Inner Mongolia University</organization>
      <address>
        <postal>
          <street></street>
          <!-- Reorder these if your country does things differently -->
          <city>Hohhot</city>
          <region></region>
          <code>010021</code>
          <country>China</country>
        </postal>
        <phone>+86 18686016307</phone>
        <email>250832228@qq.com</email>
        <!-- uri and facsimile elements may also be added -->
      </address>
    </author>
    <date day="29" month="December" year="2020" />

    <!-- If the month and year are both specified and are the current ones, xml2rfc will fill 
         in the current day for you. If only the current year is specified, xml2rfc will fill 
	 in the current day and month for you. If the year is not the current one, it is 
	 necessary to specify at least a month (xml2rfc assumes day="1" if not specified for the 
	 purpose of calculating the expiry date).  With drafts it is normally sufficient to 
	 specify just the year. -->

    <!-- Meta-data Declarations -->

    <area>General</area>

    <workgroup>Network Working Group</workgroup>

    <!-- WG name at the upperleft corner of the doc,
         IETF is fine for individual submissions.  
	 If this element is not present, the default is "Network Working Group",
         which is used by the RFC Editor as a nod to the history of the IETF. -->

    <keyword>blockchain</keyword>

    <!-- Keywords will be incorporated into HTML output
         files in a meta tag but they have no effect on text or nroff
         output. If you submit your draft to the RFC Editor, the
         keywords will be used for the search engine. -->

    <abstract>
      <t>Blockchain is a distributed technology, and it uses cryptography and hash functions to store data in a chain to ensure that data are tamper-resistant and traceable. So, this document proposes an architecture for collecting traffic accident information based on blockchain. At the same time, this document describes the working method of collecting traffic accident information under this architecture.</t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
      <t>With the development of society, there are more and more vehicles on the road, and a problem that follows is that the incidence of traffic accidents is also increasing. The frequent occurrence of traffic accidents has brought a serious impact on human life, and has brought certain pressure on the relevant traffic departments to deal with traffic accidents. The handling of traffic accidents must be timely, and the evidence must be obtained correctly, so as to avoid traffic jams, secondary accidents and legal disputes. Therefore, how to use the existing technology to quickly, correctly and effectively deal with traffic accidents has become a very important issue.</t>
      <t>The most important thing to deal with traffic accidents is to collect traffic accident information (also known as "resources"). At present, the main methods of collecting traffic accident information are manual and automatic. Among them, manual methods include measuring tape, witness investigation, and on-site photographing. The automatic method is to use the camera at the intersection. These methods require a long time, and cause certain difficulties for rapid recording, rapid evacuation of traffic, subsequent accident analysis and liability determination.</t>
      <t>In the past few years, with the development of wireless communication technology and the automobile industry, the Vehicular Ad Hoc Network (VANET) has developed significantly <xref target="Misra2009"></xref>. Based on the VANET researchers have proposed a large number of related applications, which are divided into safety-related applications and comfort-related applications <xref target="Eze2014"></xref>. These applications mainly use the cooperation between vehicles to transmit messages. The driving recorder is an instrument that records the video image and sound of the vehicle during driving. If a traffic accident occurs in front of the vehicle, it can provide strong evidence for handling the traffic accident. Resources can also be collected through cooperation between vehicles. It can be seen that the use of vehicle-to-vehicle collaboration in the VANET can transmit driving recorder?s data to relevant departments, which is beneficial to better handling of traffic accidents.</t>
      <t>Most of the resources transmitted is used as evidence. It is necessary to ensure that the data transmitted to the relevant transportation department are true, confidential, and not tampered, and traceable. However, in the communication process, resources security is the main concern, including the safety protection issues in transmission process, the security issues of centralized storage in the data center, the access control and privacy protection.</t>
      <t>Blockchain is a distributed technology. It uses cryptography and hash functions to store data in a chain to ensure that data are tamper-resistant and traceable. And the technology uses a consensus protocol to ensure data consistency. Therefore, blockchain technology can be applied to the VANET environment to solve the security problem and remove the dependence on trusted central entities. However, the process of consensus has to solve the large computational problem which cannot be done on computing resources constrained vehicles. As a new type of technology, Mobile Edge Computing (MEC) can be used not only to offload computationally intensive tasks from mobile devices to edge networks, but also to optimize processing before sending data to the core network, and to provide edge cloud services for mobile users at the edge.</t>
      <t>Therefore, this document proposes an architecture for collecting traffic accident information based on blockchain. It uses blockchain to ensure that resources are tamper-resistant and traceable, and uses edge computing to solve the large computational problem of blockchain consensus process.</t>
      <t>In section 2, some current researches on collecting transaction accident information are described, and their shortcomings are analyzed.  Section 3 proposes the structure of this document. Section 4 describes the working method of collecting traffic accident information in the framework proposed in this document. Section 5 discusses how the architecture guarantees the security of VANET. Section 6 summarizes the full document.</t>
    </section>

    <section title="Relate work">
      <t>With the increase of vehicles on the road, the number of traffic accidents has also increased. The traditional methods of collecting traffic accident information are manual methods-pulling a measuring tape, witnessing investigation, and taking pictures on the spot, which takes a long time and is not conducive to the rapid evacuation of traffic and rapid recording of the scene. Therefore, there are a large number of researchers in collecting traffic accident information.</t>
      <t>Among these studies, one type of research is to use web-based methods to obtain accident information. Users upload the accident information to the server of the relevant transportation department through the browser, and the relevant transportation department obtains the traffic accident information from the server as the basis for handling the traffic accident. Lobont et al. collect basic information of accidents in a web-based traffic accident collection system, including time and location <xref target="Lobont2013"></xref>. In a web-based traffic accident collection system, Williams et al. collect information on the severity of accidents, vehicle types, casualties, road conditions, weather conditions, and light conditions <xref target="Williams2015"></xref>. Another form of such research is the use of smart phones. CrashData <xref target="Derdus2014"></xref> proposed by Derdus et al. is an application based on mobile smart phones. The application can upload the basic information of the traffic accident to the server. This type of research must be connected to the Internet and requires users to participate in actively uploading information, but users may not upload resources voluntarily.</t>
      <t>Another type of research is to install fixed infrastructure on both sides of the road to obtain traffic accident information. In the traffic accident investigation and management system based on GPS VRS, GIS road database and stereo vision technology proposed by Qingwu H et al. <xref target="Hu2011"></xref>, the traffic accident information is mainly obtained through GPS VRS and GIS road database, and then restored using stereo vision technology. In the system for collecting traffic accident information based on ultrasound and ZigBee wireless transmission technology proposed by Song H et al. <xref target="Song2014"></xref>, the state of the vehicle during a traffic accident is measured by ultrasound, including information such as speed and direction. This type of research is limited by the location of fixed infrastructure, and traffic accident information cannot be collected where there is no fixed infrastructure.</t>
      <t>Other research is firstly obtaining traffic accident information through various sensors on the vehicle, and then using the VANET to transmit the traffic accident information to the relevant traffic department. In the literature <xref target="Abduljalil2012"></xref>, Abduljalil FM et al. use on-board angle sensors, airbag sensors, cameras, GPS sensors, etc. to obtain traffic accident information, and then use Wi-Fi, GPRS, 3G, WIMAX, 4G-LTE wireless transmission technology to transfer traffic accident information to the relevant department. In the VWaas service architecture proposed by Hussain R et al. <xref target="Hussain2013"></xref>, when a traffic accident occurs, the surrounding vehicles use the car?s camera to capture the traffic accident information, and then send the captured content to the centralized server facility. In this process, the vehicle directly sends traffic accident information to the server via 3G/4G or transmits the traffic accident information to the RSUs (Road Side Units) via DSRC, and then the RSU transmits the information to the RSUs server.</t>
      <t>Among the above methods for collecting traffic accident information, the web-based method requires users to upload traffic accident information to a server, which must be connected to the Internet, and the time for collecting information is relatively long. Based on the way roadside infrastructure collects traffic accident information, limited by the fixed location of the infrastructure, it is impossible to collect traffic accident information in areas not covered by the infrastructure. The method of collecting traffic accident information based on vehicle sensors and the VANET requires the participation of RSUs. In the above three methods of collecting traffic accident information, only the information after the traffic accident can be collected, and the information before the traffic accident cannot be obtained. The analysis of the accident and the determination of responsibility after the accident have certain difficulties. And there is no guarantee that the collected traffic accident information is not been tampered with and can be traced to the source.</t>
    </section>

    <section title="System structure">
      <t>This document proposes a security architecture for collecting traffic accident information based on blockchain. The architecture consists of three layers, namely perception layer, edge computing layer, and service layer. The perception layer comprises vehicle and RSU, together forming blockchain network. The edge computing layer provides computing resources and edge cloud services for the perception layer. The service layer includes cloud services and blockchain.</t>
      <section title="Perception layer">
        <t>A driving recorder is installed on the vehicle, which can record the traffic accident information of the vehicle passing position. Because of the constraint of computing resource and the mobility, the vehicle cannot perform all blockchain functions, including wallet (save address and private key), miner (mining), complete blockchain (save all blockchain data), network routing (validate and propagate transaction block information, discover and maintain connections to peer nodes). In this document, vehicle performs the functions of wallet and network routing.</t>
        <t>The RSU connects each other by wired communication, forming stable blockchain network which can ensure a unique ledger for collecting traffic accident information. Therefore, all blockchain functions are performed on the RSU. Even while one vehicle is moving, it can communicate with RSU directly or through other vehicles.</t>
      </section>
      <section title="Edge computing layer">
        <t>There are lots of transactions occurred for collecting traffic accident information. If all the consensus work of the blockchain transaction is completed in RSU, it will inevitably affect the network performance and bring high delay. Therefore, this document offloads the computationally intensive work to MEC, and the result is returned to the RSU after completion. MEC is also responsible for handling other computationally intensive work, such as video or image processing, etc.</t>
      </section>
      <section title="Service layer">
        <t>The traffic accident information recorded by the driving recorder is video, which has a large amount of data and is not suitable for storage in blockchain of RSUs. Because the blockchain is distributed storage, each blockchain node stores all the data, which consumes lots of storage resources. So, the document stores the traffic accident information on the cloud server, which can not only store the data permanently, but also facilitate the inspection and evidence collection by the traffic police department.</t>
        <t>So, for data stored in the service layer, part of the data which are tamper-resistant and traceable, such as traffic accident data, traffic violation data, etc. are stored using blockchain. The other part of data is stored on the cloud service.</t>
      </section>

    </section>

    <section title="Scheme design">
      <t>Based on the above architecture, the working method of collecting traffic accident information includes 4 steps, including traffic accident information query, traffic accident information return, RSUs consensus, and traffic accident information storage. The working methods of collecting traffic accident information are as follows.</t>
      <section title="Traffic accident information query">
        <t>The traffic police department initiates a traffic accident information inquiry request based on the time and location of the traffic accident. The query request is sent to the vehicles driving on the road through the RSUs. Because it is uncertain which vehicles have captured the traffic accident information, in order to enable more vehicles within the communication range of the RSU to receive the traffic accident information query request, the document uses the flooding method to send the query request. At the same time, delay tolerant network technology is used to forward query requests to vehicles that are not within the communication range of RSU by using moving vehicles.</t>
      </section>
      <section title="Traffic accident information return">
        <t>The vehicle receives the traffic accident information query request and checks whether the traffic accident information is recorded locally. If recording, extract the traffic accident information from the driving recorder and transmit it to the nearest RSU. If the vehicle does not directly communicate with the RSUs in a single hop, it is forwarded through the intermediate vehicle.</t>
        <t>The vehicle is in a moving state. If the traffic accident information recorded by the driving recorder is directly disseminated on the network, the probability of transmission failure will be very high, and the network performance will be affected. Therefore, this document processes the traffic accident information in fragments, and then transmits the fragmented traffic accident information, and finally aggregates it through the RSUs.</t>
        <section title="Resource fragmenting method">
          <t>The resources need to be transmitted in fragments. However, the size of the fragments must ensure that a complete resource can be transmitted within the shortest communication time between vehicles. Therefore, this document determines the size of resource fragments according to the shortest communication time of vehicles on urban roads. First, determine the shortest time for vehicle communication on urban roads. The movement of vehicles on urban roads can be divided into two types: same direction driving and reverse direction driving. When two vehicles are driving in the same direction and in the reverse direction on the city road at the same speed, the communication time for them when driving in the reverse direction is shorter.</t>
          <t>Generally, vehicles on urban roads are not allowed to exceed the prescribed speed. When the vehicle is traveling at the maximum speed specified on the city road, the communication time between them is the shortest. Therefore, the fragment size of the resource is defined as the data size that can be transmitted in the shortest communication time between vehicles, which can ensure that any resource can be transmitted within the vehicle communication time range.</t>
        </section>
        <section title="Resource Naming Method">
          <t>The traffic accident information after fragmentation is named according to certain rules, which is convenient to distinguish from other vehicles and to facilitate aggregation. The naming rules are as follows:</t>
          <t>
            <list>
              <t>NodeID_SerialNum_TotalNum_Time_Location</t>
            </list>
          </t>

          <t>Among them, NodeID represents the ID of the node, that is, the license plate number of the vehicle; SerialNum represents the serial number of the traffic accident information fragment; TotalNum represents the total number of traffic accident information fragments; Time represents the time when the traffic accident occurred; Location represents the location of the traffic accident, that is, the latitude and longitude.</t>
          <t>For the same traffic accident resource, the node ID can distinguish which vehicle provides the resource, and the resource sequence number and the total number of resource fragments can distinguish each fragment of the resource provided by the vehicle. For the same car (same node ID), even if the resources of multiple traffic accidents are captured, different traffic accidents can be distinguished by the time and location of the traffic accident. Moreover, each fragment of the same traffic accident resource can be distinguished by the resource sequence number and the total number of resource fragments.</t>
        </section>
      </section>
      <section title="RSUs consensus">
        <t>The traffic accident information needs to be verified, agreed, and added to the blockchain. The specific process is as follows:
          <list style="letters">
            <t>When RSUs receive traffic accident information, they generate a transaction based on the basic information and hash value of the traffic accident information (NodeID, SerialNum, TotalNum, Time, Location) and forward it to other RSUs.</t>
            <t>Other RSUs in the blockchain network receive the transaction and check whether the transaction is valid and the format is correct. If the inspection meets the requirements, it is placed in the transaction storage pool and forwarded to other RSUs. The other RSUs that receive the transaction repeat the process.</t>
            <t>The RSU that obtains the right to packaging the transactions in the transaction storage pool into a block, and then mines the block. The mining process needs to complete a large number of calculations, and RSUs generally do not have the ability to complete a large number of calculations, and the calculation tasks need to be offloaded to edge computing. Edge computing completes the calculation task and returns the result to the RSUs. The RSUs sends the block to other RSUs to spread across the entire network.</t>
            <t>After receiving the block, other RSUs verify the block. If the block is verified, the RSUs deletes the completed consensus transaction from the transaction storage pool and the block being mined, and at the same time adds it to the blockchain.</t>
          </list>
        </t>
      </section>
      <section title="Traffic accident information storage">
        <t>The RSUs aggregate the traffic accident information fragmented in the blockchain. The aggregating process involves video processing, so this process is also offloaded to edge computing to reduce the workload of RSUs and increase its effectiveness. After the edge computing completes the aggregation of the traffic accident information, it sends the complete traffic accident information to the RSUs.</t>
        <t>The blockchain in RSUs cannot store all traffic accident information. So it is uploaded to the cloud for storage, and the blockchain in the RSUs only store the digest of traffic accident information. In order to ensure the security of data in cloud, the data which are tamper-resistant and traceable are stored using blockchain. While, other data adopt the original storage method of the cloud, guaranteeing security by cloud computing architecture.</t>
      </section>
    </section>

    <section title="Discuss">
      <t>This section focuses on how the architecture guarantees the security for collecting traffic accident information.</t>
      <t>In this security architecture, vehicles and RSUs in the perception layer together form blockchain network to improve the security for collecting traffic accident information. However, traffic accident information generated by the vehicle generally are stored in the cloud or a centralized platform so as to provide data support for related department. Considering a large amount of traffic accident information, the perception layer does not have enough space to store. Therefore, in this security architecture, the traffic accident information is still stored in the cloud of the service layer. In order to ensure the security of data in cloud, the data which are tamper-resistant and traceable are stored using blockchain. While, other data adopt the original storage method of the cloud, guaranteeing security by cloud computing architecture.</t>
      <t>At the perception layer, the main challenge is security of traffic accident information during transmission. So, blockchain in the perception layer is used to solve the security problem in the transmission process. And the data solving the security problem in transmission process need to be stored in perception layer blockchain. By combining MEC, the perception layer can ensure the security of traffic accident information in transmission process.</t>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>There are no IANA considerations related to this document.</t>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>There are no Security Considerations related to this document.</t>
    </section>

    <section title="Conclusion">
      <t>This document proposes an architecture for collecting traffic accident information based on blockchain. The architecture includes three layers, namely perception layer, edge computing layer and service layer. The perception layer ensures the security of VANET data in the transmission process through the blockchain. The edge computing layer provides computing resources and edge cloud services for the perception layer. The service layer uses the combination of traditional cloud storage and blockchain to ensure the security of data.</t>
    </section>

    <section anchor="Acknowledgements" title="Acknowledgements">
      <t>This work was supported by the Inner Mongolia Autonomous Region Science and Technology Achievements Transformation Project (No. CGZH2018124).</t>
    </section>

  </middle>

  <!--  *****BACK MATTER ***** -->

  <back>
    <!-- References split into informative and normative -->

    <!-- There are 2 ways to insert reference entries from the citation libraries:
     1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (as shown)
     2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml"?> here
        (for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.xml")

     Both are cited textually in the same manner: by using xref elements.
     If you use the PI option, xml2rfc will, by default, try to find included files in the same
     directory as the including file. You can also define the XML_LIBRARY environment variable
     with a value containing a set of directories to search.  These can be either in the local
     filing system or remote ones accessed by http (http://domain/dir/... ).-->


    <references title="Informative References">
      <!-- Here we use entities that we defined at the beginning. -->
      <!-- &RFC2629;-->
      <!-- &RFC3552;-->
      <!-- &RFC5226;-->

      <!-- A reference written by by an organization not a person. -->
      <reference anchor="Misra2009">
        <front>
          <title>Guide to wireless ad hoc networks</title>
          <author initials="S" surname="Misra" fullname="S. Misra"></author>
          <author initials="I" surname="Zhang" fullname="I. Zhang"></author>
          <author initials="S" surname="Misra" fullname="S.C. Misra"></author>
          <date year="2009" />
        </front>
        <seriesInfo name="" value="Springer Science &amp; Business Media"/>
      </reference>

      <reference anchor="Eze2014">
        <front>
          <title>Centralized Conferencing (XCON) Media Models</title>
          <author initials="E" surname="Eze" fullname="Elias C. Eze"></author>
          <author initials="S" surname="Zhang" fullname="Sijing Zhang"></author>
          <author initials="E" surname="Liu" fullname="Enjie Liu"></author>
          <date year="2014"/>
        </front>
        <seriesInfo name="" value="2014 20th International Conference on Automation and Computing"/>
      </reference>

      <reference anchor="Lobont2013">
        <front>
          <title>Improving traffic safety using modern methods for accident data collection</title>
          <author initials="L" surname="Lobont" fullname="Lucian Lobont"></author>
          <author initials="A" surname="FILICHI" fullname="Adrian Cosmin FILICHI"></author>
          <author initials="L" surname="POPESCU" fullname="Liliana Georgeta POPESCU"></author>
          <date year="2013"/>
        </front>
        <seriesInfo name="" value="ANNALS OF THE ORADEA UNIVERSITY Fascicle of Management and Technological Engineering" />
      </reference>

      <reference anchor="Williams2015">
        <front>
          <title>Online Road Traffic Accident Monitoring System for Nigeria</title>
          <author initials="K" surname="Williams" fullname="Kehinde Williams"></author>
          <author initials="P" surname="Idowu" fullname="Peter Adebayo Idowu"></author>
          <author initials="E" surname="Olonade" fullname="Emmanuel Olonade"></author>
          <date year="2015"/>
        </front>
        <seriesInfo name="" value="Transactions on Networks and Communications" />
      </reference>

      <reference anchor="Derdus2014">
        <front>
          <title>A mobile solution for road accident data collection</title>
          <author initials="K" surname="Derdus" fullname="Kenga Mosoti Derdus"></author>
          <author initials="V" surname="Ozianyi" fullname="Vitalis Gavole Ozianyi"></author>
          <date year="2014"/>
        </front>
        <seriesInfo name="" value="Proceedings of the 2nd Pan African International Conference on Science, Computing and Telecommunications (PACT 2014)" />
      </reference>

      <reference anchor="Hu2011">
        <front>
          <title>A Framework for Traffic Accident Scene Investigation with GPS VRS, Road Database and Stereo Vision Integration</title>
          <author initials="Q" surname="Hu" fullname="Qingwu Hu"></author>
          <author initials="H" surname="Wang" fullname="Haiying Wang"></author>
          <date year="2011"/>
        </front>
        <seriesInfo name="" value="2011 International Workshop on Multi-Platform/Multi-Sensor Remote Sensing and Mapping" />
      </reference>

      <reference anchor="Song2014">
        <front>
          <title>Wireless Positioning System for Investigation of Road Traffic Accidents</title>
          <author initials="H" surname="Song" fullname="Hong Song"></author>
          <author initials="J" surname="Ming" fullname="Jianxiong Ming"></author>
          <author initials="J" surname="Tang" fullname="Jun Tang"></author>
          <author initials="D" surname="Zeng" fullname="Ding Zeng"></author>
          <author initials="w" surname="Duan" fullname="Weijian Duan"></author>
          <author initials="Z" surname="Yin" fullname="Zhiyong Yin"></author>
          <date year="2014"/>
        </front>
        <seriesInfo name="" value="Proceedings of the International Conference on Logistics, Engineering, Management and Computer Science" />
      </reference>

      <reference anchor="Abduljalil2012">
        <front>
          <title>A framework for vehicular accident management using wireless networks</title>
          <author initials="F" surname="Abduljalil" fullname="Fekri M. Abduljalil"></author>
          <date year="2012"/>
        </front>
        <seriesInfo name="" value="2012 IEEE 13th International Conference on Information Reuse &amp; Integration (IRI)" />
      </reference>

      <reference anchor="Hussain2013">
        <front>
          <title>Vehicle witnesses as a service: Leveraging vehicles as witnesses on the road in vanet clouds</title>
          <author initials="R" surname="Hussain" fullname="Rasheed Hussain"></author>
          <author initials="A" surname="Abbas" fullname="Fizza Abbas"></author>
          <author initials="S" surname="Son" fullname="Junggab Son"></author>
          <author initials="K" surname="Kim" fullname="Donghyun Kim"></author>
          <author initials="K" surname="Kim" fullname="Sangjin Kim"></author>
          <author initials="O" surname="Oh" fullname="Heekuck Oh"></author>
          <date year="2013"/>
        </front>
        <seriesInfo name="" value="2013 IEEE 5th International Conference on Cloud Computing Technology and Science" />
      </reference>
    </references>
  </back>
</rfc>
