hs-pseudonym-schemes-in-v2x/main.tex

\documentclass[10pt,conference,onecolumn,final]{IEEEtran}

\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \defaultfontfeatures{Ligatures=TeX} % To support LaTeX quoting style
  %\setromanfont{Vollkorn}
\else
  \usepackage[T1]{fontenc}
  \usepackage[utf8]{inputenc}
\fi

\usepackage{clrscode}
\usepackage{xcolor}
\usepackage[]{graphicx}

\newcommand{\comment}[1]{{\parindent0pt\fbox{\begin{minipage}{0.45\textwidth}{\em #1}\end{minipage}}}}
\newenvironment{changed}{\red}{\color{black}}
\newcommand{\todo}[1]{ \color{red} \footnote{ \color{red}[#1] \color{black}} \color{black}}
\newcommand{\Hide}[1]{%
 { 
   \parindent0pt
   \emph{\scriptsize #1}
 }
}
%\renewcommand{\Hide}[1]{}

\newcommand{\documenttitle}{An ETSI look at the State of the Art of pseudonym scheme in Vehicle-to-Everything (V2X) communication}

\begin{document}

%----------------------------------------------------------------------
% Title Information, Abstract and Keywords
%----------------------------------------------------------------------
\title{\documenttitle}

% % %
% In case of double blind submissions:
\author{
  \IEEEauthorblockN{Anonymous}
  \IEEEauthorblockA{Some Research Group\\
    Some Institution\\
    Some Email Addresses%
  }
}

%\author{
%  \IEEEauthorblockN{Oliver Schmidt}
%  \IEEEauthorblockA{TU Dresden\\
%    oliver.schmidt3$[$at$]$mailbox.tu-dresden.de%
%   } 
%}


\maketitle

% % % 
% sources on writing papers:
% look for a /good/ outline at the end of this text, the /why/ is found at this link:
% http://homepages.inf.ed.ac.uk/bundy/how-tos/writingGuide.html
% http://www-net.cs.umass.edu/kurose/writing/
% http://www.cs.columbia.edu/~hgs/etc/writing-style.html
% Read ``Zen - or the art of motorcycle maintenance'' to understand what science and research is
% Read ``The craft of research'' to /really/ learn how to conduct research and report about it! :-)
% some hints on plagiarism: http://www.williamstallings.com/Extras/Writing_Guide.html 
% read the text above again. the most important part (that we all tend to forget) is only 5 paragraphs

\begin{abstract} 

\Hide{
1) Problem statement: The Problem (one is more than sufficient for each paper!)\\
2) Relevance: Why ist this problem /really/ a problem?\\
3) Response: What is our solution to the problem?\\
4) Confidence: how do we show in this paper, that our solution is good?
}
\end{abstract}

\begin{IEEEkeywords}
% Are NOT: Peer-To-Peer, Anonymity, Privacy.
% BUT TAKEN FROM THIS LIST: 
% http://www.ieee.org/organizations/pubs/ani_prod/keywrd98.txt
Networks, Intelligent transportation systems, Security, Mesh networks, Privacy
\end{IEEEkeywords}
% }

%\maketitle

\IEEEpeerreviewmaketitle

\section{Introduction}

% % % 
% Broad Topic
\Hide{Broad Topic, potentially little broad background}

% \IEEEPARstart{F}{irst} word


% % % 
% Thema, special problem we're looking at, motivation
% pbly more background for our problem (why is it actually hard?) 
% Broad background, general definitions
\Hide{Topic, some background}

% % % 
% our goal and our claims (what are we solving in this work?)
\Hide{Our goal, research question, motivation and relevance (Why is it a problem the reader should care about? Why is it hard?)}
% % % 
% Requirements for our solution
\Hide{Requirements for a good solution}
% % % 
% Which metrics can we use to show the quality/quantity of our solution?
% pbly rough definition of metrics
\Hide{Metrics to measure how good a solution is}

\Hide{\{If space missing the related work may be presented in a paragraph here\}}

% % % 
% Summary of our solution
\Hide{Overview of our solution and first confidence (how do we show that it's good?)}

\Hide{Our contributions in this paper}

% % % 
% outline of the paper / reader's digest
\Hide{Reader's digest}

- I look only at middle layers \\
- look at ETSI ITS

% % % 
% Literature Survey and Background
\section{Background}
\label{sec:background}

\subsection{ITS Architecture}

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}

% \nocite{european_telecommunications_standards_institute_etsi_etsi_2010}

\subsection{Identifiers}

\section{Pseudonym Schemes}

\subsection{Pseudonym Schemes for ETSI ITS Systems}

\subsection{Pseudonym Change Strategies}

\subsection{Further Pseudonym Techniques}

\section{Evaluation}

\subsection{Attacker Model}

\section{Summary}
% % % 
% Theory (probably)

% % % 
% Specifications

% % % 
% Implementation

% % % 
% Evaluation

% % % 
% Related work (can be done together with literature survey)
% STATE HOW THE RELATED WORK RELATES TO YOUR WORK!! (how is it similar, how is it different?)
% Related work is not your enemy, but gives you ``the shoulders of giants'' you can stand on
% (and besides: some of the authors might review your paper... ;)

% % % 
% Further work and conclusion


\section{Glossary}

\include{glossary}

%\nocite{booth08craft}
\bibliographystyle{IEEEtran}
\bibliography{mybib}

%----------------------------------------------------------------------

\end{document}


% % % 
% A good outline for a computer science paper (according to Al Bundy)
% 
% Title
%     * - ideally the title should state the hypothesis of the paper 
% 
% Abstract
%     * - state hypothesis and summarise the evidence that supports or refutes it 
% 
% Introduction
%     * - motivate the contribution! 
% 
% Literature Survey
%     * - broad and shallow account of the field, rival approaches, drawbacks of each, major outstanding problems 
% 
% Background
%     * - states previous work in more detail, where this is necessary for understanding 
% 
% Theory
%     * - underlying theory, definitions, theorems etc. 
% 
% Specification
%     * - requirements and specs of implementation 
% 
% Implementation Evaluation Related Work
%     * - narrow but deep comparison with main rivals 
% 
% Further Work Conclusion
%     * - summarise research, discuss significance, restate hypothesis and the evidence for and against it, - recapitulate original motivation, reassess the state of the field in the light of this new contribution 
% 
% Appendices 
%