Architecture for collecting traffic accident information based on blockchain
draft-zhang-t2trg-accident-blockchain-00

Document Type Active Internet-Draft (individual)
Authors Ru Li  , Xiaodong Zhang  , Jun Fan 
Last updated 2021-03-24
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                              R. Li
Internet-Draft                                             X. Zhang, Ed.
Intended status: Informational                                    J. Fan
Expires: July 2, 2021                          Inner Mongolia University
                                                       December 29, 2020

   Architecture for collecting traffic accident information based on
                               blockchain
                draft-zhang-t2trg-accident-blockchain-00

Abstract

   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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 2, 2021.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Li, et al.                Expires July 2, 2021                  [Page 1]
Internet-Draft   Collecting traffic accident information   December 2020

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Relate work . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  System structure  . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Perception layer  . . . . . . . . . . . . . . . . . . . .   6
     3.2.  Edge computing layer  . . . . . . . . . . . . . . . . . .   6
     3.3.  Service layer . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Scheme design . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Traffic accident information query  . . . . . . . . . . .   7
     4.2.  Traffic accident information return . . . . . . . . . . .   7
       4.2.1.  Resource fragmenting method . . . . . . . . . . . . .   7
       4.2.2.  Resource Naming Method  . . . . . . . . . . . . . . .   8
     4.3.  RSUs consensus  . . . . . . . . . . . . . . . . . . . . .   8
     4.4.  Traffic accident information storage  . . . . . . . . . .   9
   5.  Discuss . . . . . . . . . . . . . . . . . . . . . . . . . . .  10
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   8.  Conclusion  . . . . . . . . . . . . . . . . . . . . . . . . .  10
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   10. Informative References  . . . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   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.

   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
Show full document text