overview about used networking layer protocols & tackled citations
This commit is contained in:
parent
2cb13d5223
commit
207b8c19c8
18
glossary.tex
18
glossary.tex
|
|
@ -1,3 +1,19 @@
|
|||
\todo{include long version of abbreviations at first mention}
|
||||
|
||||
\textbf{AU}: application unit
|
||||
|
||||
\textbf{CCU}: communication \& control unit
|
||||
|
||||
\textbf{ETSI}: European Telecommunications Standards Institute
|
||||
|
||||
\textbf{ITS}: Intelligent Transportation Systems
|
||||
\textbf{ITS}: Intelligent Transportation Systems
|
||||
|
||||
\textbf{LS}: GeoNetworking Location Service
|
||||
|
||||
\textbf{LT}: GeoNetworking Location Table
|
||||
|
||||
\textbf{OBU}: on-board unit
|
||||
|
||||
\textbf{RSU}: road-site unit
|
||||
|
||||
\textbf{VANET}: vehicular ad-hoc network
|
||||
|
|
|
|||
60
main.tex
60
main.tex
|
|
@ -1,7 +1,7 @@
|
|||
\documentclass[10pt,conference,twocolumn,final]{IEEEtran}
|
||||
|
||||
\usepackage{ifxetex}
|
||||
\ifxetex
|
||||
\usepackage{ifluatex}
|
||||
\ifluatex
|
||||
\usepackage{fontspec}
|
||||
\defaultfontfeatures{Ligatures=TeX} % To support LaTeX quoting style
|
||||
%\setromanfont{Vollkorn}
|
||||
|
|
@ -150,7 +150,13 @@ Networks, Intelligent transportation systems, Security, Mesh networks, Privacy
|
|||
|
||||
This section gives a brief overview of the ETSI architecture for Intelligent Transport Systems. It isn't meant to be elaborate but has a focus on identifiers and other message contents allowing linkability of messages.
|
||||
|
||||
The overall architecture of ITS stations according to the ETSI reference architecture \cite{europeantelecommunicationsstandardsinstituteetsiETSI3026652010} is mostly based on the well-known OSI layer model.
|
||||
VANETs have some special requirements: Due to many nodes being constantly on the move at higher speeds, tolerance for quickly changing topologies and low-latency communication are important points. Multi-hop mesh-networking is an important ability to keep the network functional in areas without designated infrastructure.
|
||||
|
||||
A VANET consists of different kinds of ITS stations: \\
|
||||
On-board units (OBU) residing inside vehicles can be divided into the communication and control unit (CCU), managing the ITS specific network communication over the car's wireless interfaces, and application units (AU) utilising the network services provided by the CCU to communicate transparently over a standard IPv6 stack. \\
|
||||
On the stationary infrastructure side, road-site units (RSU) can either just provide some special local services or even be connected to a network operator's infrastructure and thus provide an uplink to the internet.
|
||||
|
||||
The protocol architecture of ITS stations according to the ETSI reference architecture \cite{europeantelecommunicationsstandardsinstituteetsiETSI3026652010} is mostly based on the well-known OSI layer model.
|
||||
|
||||
\begin{figure}
|
||||
% center graphic
|
||||
|
|
@ -160,12 +166,47 @@ The overall architecture of ITS stations according to the ETSI reference archite
|
|||
\label{fig:etsi-its-arch}
|
||||
\end{figure}
|
||||
|
||||
OSI layers 1 and 2 are combined into the \textit{Access} layer, OSI layers 3 and 4 into the \textit{Networking \& Transport} layer and OSI layers 5, 6 and 7 are put into the \textit{Facilities} layer (see Fig. \ref{fig:etsi-its-arch} ). \\
|
||||
The two vertical \textit{Management} and \textit{Security} layers provide supporting functionality throughout the whole stack. \textit{Applications} make use of the ITS-station services and thus sit on top of it all.
|
||||
OSI layers 1 and 2 are combined into the \textit{Access} layer, OSI layers 3 and 4 into the \textit{Networking \& Transport} layer and OSI layers 5, 6 and 7 are put into the \textit{Facilities} layer (see Fig. \ref{fig:etsi-its-arch} ). \\
|
||||
The two vertical \textit{Management} and \textit{Security} layers provide supporting functionality throughout the whole stack. \textit{Applications} make use of the ITS-station services and thus sit on top of it all.
|
||||
|
||||
Designed for modularity, the ETSI ITS architecture allows for a big number of access protocols. Similarly, a great variety of applications can run on top of the stack. Because of that variety, these two layers are considered out-of-scope of this survey.
|
||||
\todo{participants, structure, special requirements: changing topology, speed, realtime}
|
||||
|
||||
% \nocite{european_telecommunications_standards_institute_etsi_etsi_2010}
|
||||
Designed for modularity, the ETSI ITS architecture allows for a big number of access protocols. Similarly, a great variety of applications can run on top of the stack. Because of that variety, these two layers are considered out-of-scope of this survey.
|
||||
|
||||
The \textbf{Networking \& Transport} layer takes care of addressing and routing of messages within the ITS network and multiplexing them to higher-level services. Similarly to the OSI model, the groundwork of this functionality is provided by various networking protocols: \\
|
||||
ETSI explicitly mentions the usage of IPv6 (possibly equipped with mobility support), the CALM FAST protocol \cite{TN_libero_mab2} and the GeoNetworking protocol, which can also be used to encapsulate IPv6 packets.
|
||||
|
||||
CALM FAST \cite{TN_libero_mab2} is a non-IP port-mapper protocol designed for single-hop communication between ITS stations and extensible with additional features. Due to a lack of proper access to the standard document, this protocol is considered out-of-scope of this survey.
|
||||
|
||||
\subsubsection{GeoNetworking}
|
||||
|
||||
GeoNetworking (GN, \cite{europeantelecommunicationsstandardsinstituteetsiETSI30263612014} and following) is an ETSI-standardized networking protocol for routing and forwarding packets through VANETs based on geographical Information. It sits between the link and network layer and provides its services to other networking and transport protocols. The background section of \cite{sandonisVehicleInternetCommunications2016} gives a good high-level overview of the GN networking architecture and the rationale behind it.
|
||||
|
||||
Every GN node has to know its geographical position, e.g. through GNSS (Global Navigation Satellite Systems), for the routing to work. The services provided by GN are:
|
||||
|
||||
\begin{itemize}
|
||||
\item geo-unicast: routing a packet to a single node at a specific location
|
||||
\item geo-multicast: first routing a packet to a specified destination area, then flooding it to all nodes within that area
|
||||
\item topology-scoped broadcast: broadcast of packet within a a certain depth of neighbouring nodes
|
||||
\item single-hop broadcast: sending packets to all neighbouring nodes
|
||||
\item geo-anycast: routing packet to an arbitrary node within a specified geographical area
|
||||
\end{itemize}
|
||||
|
||||
For this to work, each node maintains a location table (LT) with the positions of its direct neighbours. This LT is populated with information from periodically-sent beaconing messages, advertising a node's position, GN address, its speed, station type \todo{check advertised information}. This information is also included in all other sent GN packets. LT entries have a lifetime attached, after which they expire if not refreshed periodically.
|
||||
For allowing to retrieve the position of non-neighbour nodes, the Location Service (LS) forwards request packets, until the node with the destination GN address is found and has replied via geo-unicast or a retransmission counter has expired.\todo{influence of frequent pseudonym change}
|
||||
|
||||
Security properties of GN messages are ensured by signing (authenticity), encrypting (confidentiality) the messages and checking their plausability and consistency. The necessary information for that is given in a security header \cite{europeantelecommunicationsstandardsinstituteetsiETSI302636412017}.
|
||||
|
||||
\subsubsection{IPv6}
|
||||
|
||||
IPv6 \cite{RFC8200} \nocite{baeckerRFCE014IPv6} specifies the 6th version of the Internet Protocol, the routing protocol used in the Networking layer of the internet. Relevant details for VANETs are the addressing using 128 bit long IP addresses \cite{RFC4291} with the first up to 64 bits specifiying the network part and the last 64 bits specifying the interface ID (node ID) within that subnetwork. Additionally to the globally unique routable address, nodes are also addressable in the scope of the same OSI layer 2 link using their link-local address automatically derived from lower-layer identifiers. Together with the huge number of globally unique IPv6 addresses, this new property makes it usable for vehicular ad-hoc networks. Another improvement in IPv6 is the \textit{router advertisement} \cite{RFC4861} of clients, where routers just periodically announce their parameters so clients are able to derive an address themselves without further negotiation.
|
||||
|
||||
\subsubsection{IPv6 over GeoNetworking}
|
||||
|
||||
Transparently exposing IP networking to higher layers allows re-using existing services based on the classical internet TCP/IP stack without modification. The GeoNetworking to IPv6
|
||||
Adaptation Sub-Layer (GN6ASL) \cite{europeantelecommunicationsstandardsinstituteetsiETSI302636612014} specifies a mechanism for sending IPv6 packets over the GN protocol by using it as a sub-IP coupling layer. GN takes care of encapsulating and routing the IP packet to its final destination node, so that the whole underlying VANET looks like a flat layer 2 network to IP services.
|
||||
GN6ASL specifies how to derive a GN address from an IPv6 address and extends IPv6 with some GeoNetworking specific extensions like geographic multicast, Geographically
|
||||
Scoped stateless Address Configuration or (un)reachability detection.
|
||||
|
||||
\subsection{Identifiers}
|
||||
|
||||
|
|
@ -206,9 +247,10 @@ Designed for modularity, the ETSI ITS architecture allows for a big number of ac
|
|||
|
||||
\section{Glossary}
|
||||
|
||||
\include{glossary}
|
||||
\nobreak
|
||||
|
||||
\input{glossary.tex}
|
||||
|
||||
%\nocite{booth08craft}
|
||||
\bibliographystyle{IEEEtran}
|
||||
\bibliography{mybib}
|
||||
|
||||
|
|
|
|||
119
mybib.bib
119
mybib.bib
|
|
@ -274,7 +274,7 @@
|
|||
author = {{European Telecommunications Standards Institute (ETSI)}},
|
||||
month = may,
|
||||
year = {2014},
|
||||
keywords = {GeoNetworking,IPv6},
|
||||
keywords = {GeoNetworking,pseudonyms,IPv6},
|
||||
file = {/home/spiollinux/Zotero/storage/TRJW42GU/en_3026360601v010201p.pdf}
|
||||
}
|
||||
|
||||
|
|
@ -284,28 +284,28 @@
|
|||
author = {{European Telecommunications Standards Institute (ETSI)}},
|
||||
month = aug,
|
||||
year = {2017},
|
||||
keywords = {unread,GeoNetworking},
|
||||
keywords = {GeoNetworking},
|
||||
file = {/home/spiollinux/Zotero/storage/H43WFVVS/en_3026360401v010301p.pdf}
|
||||
}
|
||||
|
||||
@misc{europeantelecommunicationsstandardsinstituteetsiETSITS1022011,
|
||||
title = {{{ETSI TS}} 102 636-5-1 {{V1}}.1.1; {{Intelligent Transport Systems}} ({{ITS}}); {{Vehicular Communications}}; {{GeoNetworking}}; {{Part}} 5: {{Transport Protocols}}; {{Sub}}-Part 1: {{Basic Transport Protocol}}},
|
||||
@misc{europeantelecommunicationsstandardsinstituteetsiETSI302636512017,
|
||||
title = {{{ETSI EN}} 302 636-5-1 {{V2}}.1.1; {{Intelligent Transport Systems}} ({{ITS}}); {{Vehicular Communications}}; {{GeoNetworking}}; {{Part}} 5: {{Transport Protocols}}; {{Sub}}-Part 1: {{Basic Transport Protocol}}},
|
||||
lccn = {ETSI TS 102 636-5-1},
|
||||
author = {{European Telecommunications Standards Institute (ETSI)}},
|
||||
month = feb,
|
||||
year = {2011},
|
||||
month = aug,
|
||||
year = {2017},
|
||||
keywords = {GeoNetworking,BTP},
|
||||
file = {/home/spiollinux/Zotero/storage/F8XAEDNF/ts_1026360501v010101p.pdf}
|
||||
file = {/home/spiollinux/Zotero/storage/PSKDF7X4/en_3026360501v020101p.pdf}
|
||||
}
|
||||
|
||||
@misc{europeantelecommunicationsstandardsinstituteetsiETSITS1022010a,
|
||||
title = {{{ETSI TS}} 102 636-3 {{V1}}.1.1; {{Intelligent Transport Systems}} ({{ITS}}); {{Vehicular Communications}}; {{GeoNetworking}}; {{Part}} 3: {{Network}} a Rchitecture},
|
||||
@misc{europeantelecommunicationsstandardsinstituteetsiETSI30263632014,
|
||||
title = {{{ETSI EN}} 302 636-3 {{V1}}.2.1; {{Intelligent Transport Systems}} ({{ITS}}); {{Vehicular Communications}}; {{GeoNetworking}}; {{Part}} 3: {{Network}} Architecture},
|
||||
lccn = {ETSI TS 102 636-3},
|
||||
author = {{European Telecommunications Standards Institute (ETSI)}},
|
||||
month = mar,
|
||||
year = {2010},
|
||||
month = dec,
|
||||
year = {2014},
|
||||
keywords = {GeoNetworking},
|
||||
file = {/home/spiollinux/Zotero/storage/J55YKLRB/ts_10263603v010101p.pdf}
|
||||
file = {/home/spiollinux/Zotero/storage/VIZQJ69B/en_30263603v010201p.pdf}
|
||||
}
|
||||
|
||||
@article{sandonisVehicleInternetCommunications2016,
|
||||
|
|
@ -326,44 +326,24 @@
|
|||
file = {/home/spiollinux/Zotero/storage/DE8US3BX/Sandonis et al. - 2016 - Vehicle to Internet communications using the ETSI .pdf}
|
||||
}
|
||||
|
||||
@misc{europeantelecommunicationsstandardsinstituteetsiETSITS1022011a,
|
||||
title = {{{ETSI TS}} 102 636-4-1 {{V1}}.1.1; {{Intelligent Transport Systems}} ({{ITS}}); {{Vehicular}} Communications; {{GeoNetworking}}; {{Part}} 4: {{Geographical}} Addressing and Forwarding for Point-to-Point and Point-to-Multipoint Communications; {{Sub}}-Part 1: {{Media}}-{{Independent Functionality}}},
|
||||
lccn = {ETSI TS 102 636-4-1 V1.1.1},
|
||||
author = {{European Telecommunications Standards Institute (ETSI)}},
|
||||
month = jun,
|
||||
year = {2011},
|
||||
keywords = {unread,GeoNetworking},
|
||||
file = {/home/spiollinux/Zotero/storage/KLAA6RFN/ts_1026360401v010101p.pdf}
|
||||
}
|
||||
|
||||
@misc{europeantelecommunicationsstandardsinstituteetsiETSITS1022010b,
|
||||
title = {{{ETSI TS}} 102 636-3 {{V1}}.1.1; {{Intelligent Transport Systems}} ({{ITS}}); {{Vehicular Communications}}; {{GeoNetworking}}; {{Part}} 3: {{Network}} Architecture},
|
||||
lccn = {ETSI TS 102 636-3 V1.1.1},
|
||||
author = {{European Telecommunications Standards Institute (ETSI)}},
|
||||
month = mar,
|
||||
year = {2010},
|
||||
keywords = {unread,GeoNetworking},
|
||||
file = {/home/spiollinux/Zotero/storage/59AWF99A/ts_10263603v010101p.pdf}
|
||||
}
|
||||
|
||||
@misc{europeantelecommunicationsstandardsinstituteetsiETSITS1022010c,
|
||||
title = {{{ETSI TS}} 102 636-2 {{V1}}.1.1; {{Intelligent Transport Systems}} ({{ITS}}); {{Vehicular Communications}}; {{GeoNetworking}}; {{Part}} 2: {{Scenarios}}},
|
||||
@misc{europeantelecommunicationsstandardsinstituteetsiETSI30263622013,
|
||||
title = {{{ETSI EN}} 302 636-2 {{V1}}.2.1; {{Intelligent Transport Systems}} ({{ITS}}); {{Vehicular Communications}}; {{GeoNetworking}}; {{Part}} 2: {{Scenarios}}},
|
||||
lccn = {ETSI TS 102 636-2 V1.1.1},
|
||||
author = {{European Telecommunications Standards Institute (ETSI)}},
|
||||
month = mar,
|
||||
year = {2010},
|
||||
month = nov,
|
||||
year = {2013},
|
||||
keywords = {unread,GeoNetworking},
|
||||
file = {/home/spiollinux/Zotero/storage/KU6CNASI/ts_10263602v010101p.pdf}
|
||||
file = {/home/spiollinux/Zotero/storage/53W38GKN/en_30263602v010201p.pdf}
|
||||
}
|
||||
|
||||
@misc{europeantelecommunicationsstandardsinstituteetsiETSITS1022010d,
|
||||
title = {{{ETSI TS}} 102 636-1 {{V1}}.1.1; {{Intelligent Transport Systems}} ({{ITS}}); {{Vehicular Communications}}; {{GeoNetworking}}; {{Part}} 1: {{Requirements}}},
|
||||
@misc{europeantelecommunicationsstandardsinstituteetsiETSI30263612014,
|
||||
title = {{{ETSI EN}} 302 636-1 {{V1}}.2.1; {{Intelligent Transport Systems}} ({{ITS}}); {{Vehicular Communications}}; {{GeoNetworking}}; {{Part}} 1: {{Requirements}}},
|
||||
lccn = {ETSI TS 102 636-1 V1.1.1},
|
||||
author = {{European Telecommunications Standards Institute (ETSI)}},
|
||||
month = mar,
|
||||
year = {2010},
|
||||
month = apr,
|
||||
year = {2014},
|
||||
keywords = {unread,GeoNetworking},
|
||||
file = {/home/spiollinux/Zotero/storage/ABPICAXS/ts_10263601v010101p.pdf}
|
||||
file = {/home/spiollinux/Zotero/storage/5D63HWLL/en_30263601v010201p.pdf}
|
||||
}
|
||||
|
||||
@misc{europeantelecommunicationsstandardsinstituteetsiETSITS1022012b,
|
||||
|
|
@ -412,4 +392,59 @@
|
|||
file = {/home/spiollinux/Zotero/storage/6KJFFAMX/c-its_security_policy_release_1.pdf}
|
||||
}
|
||||
|
||||
@article{TN_libero_mab2,
|
||||
title = {{{ISO}} 29281-1},
|
||||
abstract = {Bibliographische Datenbank (monatlich aktualisiert, 3sprachig) mit ca. 1.100.000 Daten von Normen aus 23 L{\"a}ndern, (z.B. ANSI, DIN, ISO), technischen Regeln sowie von deutschen Rechtsvorschriften mit technischen Bezug und geltenden EU-Richtlinien incl. VDI-Richtlinien. Der Volltextzugriff auf Normen ist nur bei entsprechender Lizenz verf{\"u}gbar!},
|
||||
author = {intelligents de transport {ISO/TC 204 Systeme f{\"u}r Verkehrsbeeinflussung und -information , ISO/TC 204 Intelligent transport systems}, ISO/TC 204 Syst{\`e}mes},
|
||||
year = {2013},
|
||||
keywords = {DIN-Norm,Internationale Norm,Norm,Regeln der Technik,Verzeichnis},
|
||||
publisher = {{ISO Internationale Organisation f{\"u}r Normung, ISO International Organization for Standardization, ISO Organisation Internationale de Normalisation}}
|
||||
}
|
||||
|
||||
@techreport{RFC8200,
|
||||
type = {{{STD}}},
|
||||
title = {Internet {{Protocol}}, {{Version}} 6 ({{IPv6}}) {{Specification}}},
|
||||
number = {86},
|
||||
institution = {{RFC Editor}},
|
||||
author = {Deering, S. and Hinden, R.},
|
||||
month = jul,
|
||||
year = {2017},
|
||||
issn = {2070-1721},
|
||||
howpublished = {Internet Requests for Comments}
|
||||
}
|
||||
|
||||
@techreport{RFC4291,
|
||||
type = {{{RFC}}},
|
||||
title = {{{IP Version}} 6 {{Addressing Architecture}}},
|
||||
number = {4291},
|
||||
institution = {{RFC Editor}},
|
||||
author = {Hinden, R. and Deering, S.},
|
||||
month = feb,
|
||||
year = {2006},
|
||||
issn = {2070-1721},
|
||||
howpublished = {Internet Requests for Comments},
|
||||
note = {http://www.rfc-editor.org/rfc/rfc4291.txt}
|
||||
}
|
||||
|
||||
@misc{baeckerRFCE014IPv6,
|
||||
title = {{RFCE014: IPv6}},
|
||||
copyright = {Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License},
|
||||
language = {German},
|
||||
number = {14},
|
||||
author = {Baecker, Anna-Lena and Schrimpe, Clemens}
|
||||
}
|
||||
|
||||
@techreport{RFC4861,
|
||||
type = {{{RFC}}},
|
||||
title = {Neighbor {{Discovery}} for {{IP}} Version 6 ({{IPv6}})},
|
||||
number = {4861},
|
||||
institution = {{RFC Editor}},
|
||||
author = {Narten, T. and Nordmark, E. and Simpson, W. and Soliman, H.},
|
||||
month = sep,
|
||||
year = {2007},
|
||||
issn = {2070-1721},
|
||||
howpublished = {Internet Requests for Comments},
|
||||
note = {http://www.rfc-editor.org/rfc/rfc4861.txt}
|
||||
}
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue