# ETSI ITS protocols project ## General Information This repositories contains the test specifications and test adapter code for ETSI ITS protocols testing. ETSI ITS protocols project supports: - ETSI EN 302 637-2: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 2: Specification of Cooperative Awareness Basic Service" - ETSI EN 102 637-3: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 3: Specifications of Decentralized Environmental Notification Basic Service" - ETSI TS 103 301: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Facilities layer protocols and communication requirements for infrastructure services" - EN 302 636-5-1: "Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 5: Transport Protocols; Sub-part 1: Basic Transport Protocol" - EN 302 636-4-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" In addition, it also support ITS Security as define by: - ETSI TS 103 940: "Intelligent Transport Systems (ITS); Security; Security Architecture and Management". - ETSI TS 102 941: "Intelligent Transport Systems (ITS); Security; Trust and Privacy Management technical specification" - IEEE Std 1609.2™-2016: "IEEE Standard for Wireless Access in Vehicular Environments –Security Services for Applications and Management Messages" - IEEE Std 1609.2a™-2017: "Standard for Wireless Access In Vehicular Environments – Security Services for Applications and Management Messages Amendment 1". Contact information Email at cti_support at etsi dot org License Unless specified otherwise, the content of this repository and the files contained are released under the ETSI Software License. See the attached LICENSE file or visit https://forge.etsi.org/etsi-software-license ## STFs The following STFs were or are currently involved in the evolutions of the ETSI ITS protocols project: - STF 405, STF 422, STF 424, STF 455, STF 462, STF 481, STF 484, STF 507, STF 517, STF 525, STF 538, STF 545 ## Installation The ETSI ITS protocols project builds and tests regularly on the following platforms: - Linux (Ubuntu) Note: The [OpenSSL](https://www.openssl.org) version > 1.1.x is also required. ### How to do it? They are two different methods: - Using [Vagrant](https://www.vagrantup.com/) - Using [Docker](https://www.docker.com/) How to choose one of these methods is depending of your host system. NOTE: In all case, if you want to setup an continuous integration process (e.g. Jenkins), Docker is the best choice. #### The host system is Windows The both methods require a virtual machine. You can use either VirtualBox or WMware. In this case, the easiest way is to use Vagrant. #### The host system is Linux Vagrant requires a virtual machine. You can use either VirtualBox or WMware. Docker does not need a virtual machine, so it is the more efficant way. ### Using Vagrant Pre-requisites on your host machine: - Install [Virtualbox](https://www.virtualbox.org/manual/ch01.html) - Install [Vagrant](https://www.vagrantup.com/intro/getting-started/) - Install Vagrant plugin vagrant-vbguest - Credentials to access [ETSI forge](https://forge.etsi.org/gitlab/users/sign_in) - Set the environment variable USERNAME to your ETSI EOL account user name - Set the environment variable PASSWORD to your ETSI EOL account password Procedure: - On your host machine, open a command line session (PuTTY, DOS window...) - From the ETSI ITS protocols project, clone the Vagrant folder - In the file Vagrantfile, modify the tag config.vm.provision replacing & strings by your ETSI credentials - In the Vagrant folder, execute the following commands: ```sh $ vagrant up --provider virtualbox --provision ... ``` NOTE The creation and the installations will take some time to achieve - Stop vagrant virtual machine ```sh $ vagrant halt ... ``` - Update the file 'Vagrantfile' to match with your networks configuration - Re-start the vagrant virtual machine and log to to the machine ```sh $ vagrant up ... $ vagrant ssh ``` - Switch to the next clause (Usage) NOTE The user password is vagrant. ### Using Docker Pre-requisites on your host machine: - Install Virtualbox - Install Docker Procedure for a Windows host machine: - On your host machine, open a the Docker Quickstart Terminal Procedure for a Linux host machine: - On your host machine, open a terminal and change to a working folder such as $HOME/temp On your host machine, clone the following items from ETSI ITS protocols project: - The docket folder - The .jenkins.sh script file (hidden file) From the your current directory, execute the following commands: ```sh $ ./.jenkins.sh ... ``` NOTE The creation and the installations will take some time to achieve - Start the container ```sh $ ./docker/run-container.sh ... ``` - Switch to the next clause (Usage) ### From scratch Pre-requisites: - Install Virtualbox Procedure: - Install a new Linux Virtual machine (Mint, Debian...) - Update your system with the latest version of kernel and security packages - Install the following packages (According to the Linux chosen, the package naming can be different) autoconf bison build-essential cmake curl dos2unix doxygen emacs expect flex g++:latest gcc:latest graphviz gdb git-core gnutls-bin libglib2.0-dev libpcap-dev libgcrypt-dev libncurses5-dev libssl-dev libtool-bin libtool libwireshark-dev libxml2-dev lsof ntp pkg-config qt5-default qtmultimedia5-dev libqt5svg5-dev subversion sudo sshpass tcpdump texlive-font-utils tshark valgrind vim vsftpd xutils-dev tree tzdata unzip wget xsltproc - In your home directory, create the following folders: - $HOME/frameworks, - $HOME/dev - $HOME/lib - In $HOME/frameworks, build the following package: - asn1c, according the procedure specified [here](https://github.com/vlm/asn1c.git) - Eclipse IDE for C/C++ Developers, according the procedure specified [here](https://www.eclipse.org/cdt/) - TITAN, according the procedure specified [here](https://github.com/eclipse/titan.core) - Import the TITAN plugin into your Eclipse IDE, according the procedure specified [here](https://github.com/eclipse/titan.core) - Clone the ETSI ITS protocols project into $HOME/dev folder ```sh $ git clone ``` - Update your default environment with the content of the script $HOME/dev/STF525_Its/scripts/devenv.bash.ubuntu - Switch to the next clause (Usage) ## Usage This clause describes how to compile and execute an Abstract Test Suite. The procedures below illustrate how to run the CAM test suite. The same procedures will apply for any other ETSI ITS test suite. Pre-requisites: - Your machine is installed following one of the installation method describes in the previous clause - Refer to the ETSI TS 103 099 for the description of the Test System architecture and configuration - Your are logged as 'etsi' or 'vagrant' user Procedure using Eclipse TITAN: - Start eclipse using a new workspace, (e.g. with the name workspace_titan) - Download and follow the steps to install Eclipse plugins for TITAN, accessible [here]{https://www.eclipse.org/downloads/download.php?file=/titan/Eclipse_installationguide.pdf} - Open the workspace_titan - Create a new TITAN project (e.g. STF525_Its) Procedure in TITAN command line: - Open several SSH session (PuTTY...) - Change to the directory ~/dev/STF525_Its/src/AtsCAM/objs - Build the test suite AtsCAM ```sh $ ../bin/cam_generate_makefile.bash ... ``` - Edit the file ../etc/AtsCAM.cfg - Update the following fields (see ETSI TS 103 099 for details): - system.camPort.params - system.utPort.params - To run the test suitem, execute the following command: ```sh $ ../bin/run-all.bash ... ``` - The log files are located in ../logs folder. You can edit them using any editor or using the Eclipse TITAN log plugins ## How to generate ITS test certificates The Test System includes a tool, asn1cert, to generate ITS test certificates used for Conformance Testing. This tool is located in the folder '~/dev/STF525_Its/tools/itscertgen/'. Note: These certificates can not be used in a true architectures, there are present only for testing and/or debug purposes. ### Build the tool 'asn1cert' To build the tool, run the 'make' command in each of the following folders: - cshared - cxml - checker - asn1certgen ### Generate the certificates After that change to the folder '~/dev/STF525_Its/data/v3' and execute 'make command. The certificates will be located in the folder '~/dev/STF525_Its/data/v3/certificates'. ### Modify or create new certificates The folder '~/dev/STF525_Its/data/v3/profiles' contains an XML file for each certificate to be generated. This XML file describes the certificate content (e.g. CERT_IUT_A_RCA.xml describes the root certificate for all CERT_IUT_A certificates). By modifying these files, you can change create new certificate with different geographical area, different validity periods or different SSPs. To re-generates the certificates, refer to the previous clause. ## Wireshark with support of ETSI ITS Protocols The official version of Wireshark, supporting ETSI ITS Protocols, is available [here](https://www.wireshark.org/download.html). Some sample capture files are available [here](https://wiki.wireshark.org/SampleCaptures). ## How to Report a Bug The ETSI ITS protocols project is under constant development, so it is possible that you will encounter a bug while using it. Please report bugs at cti_support at etsi dot org.