Project Structure
SELF4COOP (Self-optimizing Networked Edge Control for Cooperative Vehicle Autonomy) is a multi-disciplinary project that aims to develop the fundamental building blocks for Cooperative Driving-as-a-Service (CDaaS). The project focuses on the seamless integration of heterogeneous communication technologies, optimal placement of MEC (Multi-access Edge Computing) applications, and advanced cooperative perception and control strategies.
The project is organized into three main pillars:
- Flexible Networking: Integrating multiple communication technologies (5G, 4G, V2V) to enable seamless switching and concurrent use.
- System Optimization: Jointly optimizing networking and computing configurations, including traffic routing and control function placement on edge servers.
- Cooperative Perception and Vehicle Control: Enabling safer and smoother CAV driving through up-to-date shared data and robust control algorithms for coordinated maneuvers.
Work Packages (WPs)
The project activities are articulated into six Work Packages:
WP1: Vision, architecture, and scenarios
- T1.1: Definition of the system architecture, scenarios, and Key Performance Indicators (KPIs).
- T1.2: Performance analysis, validation, and future vision. This involves setting up a testbed and a simulation framework to validate the project results.
WP2: Flexible networking
Focuses on Pillar 1 (Flexible networking).
- T2.1: Seamless integration of network protocols (convergence and abstraction layers for 5G, 4G, 802.11p).
- T2.2: Fast handover mechanisms (improving handovers to prevent connectivity gaps).
WP3: System optimization
Focuses on Pillar 2 (System optimization).
- T3.1: Control requirement-driven connectivity optimization (selecting the best technology based on vehicle control requirements).
- T3.2: Computing infrastructure monitoring and control function placement (orchestrating the placement of control functions on MEC/vehicle resources).
WP4: Cooperative perception and vehicle control
Focuses on Pillar 3 (Cooperative perception and control).
- T4.1: Cooperative road and vehicle status mapping (extracting road/vehicle status from shared data).
- T4.2: Trajectory computation and coordinated maneuvering in dense traffic scenarios (optimizing traffic flow via on-demand platooning, merging, etc.).
WP5: Integration and performance evaluation
- T5.1: Reference evaluation architecture and integration (defining building blocks and interfaces).
- T5.2: Testbed setup (realizing a testbed with model autonomous vehicles and MEC infrastructure).
- T5.3: Federated simulation framework (integrating simulation tools for large-scale scenario evaluation).
WP6: Management, dissemination, communication, outreach, and exploitation
- T6.1: Management and coordination (strategic and technical coordination).
- T6.2: Dissemination (scientific publications and open source contributions).
- T6.3: Communication, outreach and exploitation (educational outreach, industrial engagement, and public events).
Project Timeline
The project has a duration of 24 months. Technical design tasks (WPs 2-4) run until month 22 to allow for feedback and validation, while integration (WP5) and management/dissemination (WP6) continue through the end of the project.