<figure><img src="image_1.png" /></figure>

HAL
open science

# A blueprint for the new research instrument

Damien Saucez

► To cite this version:

Damien Saucez. A blueprint for the new research instrument. 2024. hal-04756126

HAL Id: hal-04756126

https://inria.hal.science/hal-04756126v1

Submitted on 29 Oct 2024

HAL is a multi-disciplinary open access
archive for the deposit and dissemination of sci-
entific research documents, whether they are pub-
lished or not. The documents may come from
teaching and research institutions in France or
abroad, or from public or private research centers.

L'archive ouverte pluridisciplinaire HAL, est
destinée au dépôt et à la diffusion de documents
scientifiques de niveau recherche, publiés ou non,
émanant des établissements d'enseignement et de
recherche français ou étrangers, des laboratoires
publics ou privés.

Public Domain
<figure><img src="image_2.png" /></figure>

# A blueprint for the new research instrument

Damien Saucez, Inria

01/29/2024

<figure><img src="image_3.png" /></figure>

core

<figure><img src="image_4.png" /></figure>

edge

<figure><img src="image_5.png" /></figure>

RAN

<figure><img src="image_6.png" /></figure>
# The blueprint concept in a nutshell

* Help collaboration between engineers and non-engineers to work together on developing applications.

* Define a common terminology that doesn't require in-depth, technical knowledge

* to produce consistent vision on the application with a focus on the future objective.

* Pick up the right resources, be iterative, review and validate, and keep it as a baseline.

* Adapted from [0a, 0b]

<figure><img src="image_7.png" /></figure>

slicesc

<footnote>[0a] https://dev.to/jayjayjpg/what-is-a-software-blueprint-5388</footnote>

<footnote>[0b] https://www.qrpinternational.fr/blog/faq/blueprint-quest-ce-que-cest/</footnote>

<footnote>2</footnote>
# A post-5G research infrastructure

<figure><img src="image_8.png" /></figure>
What for?

* Vertical service integration and testing (e.g., LiDAR)

* Software Defined Networking (e.g., xAPP)

* Radio/network development software (e.g., custom PHY)

* Low-level access to radio resources (e.g., THz)

* Joint use of post-5G infrastructure and HPC resources (e.g., digital twin, code generation, fuzzing)
What for?

* Vertical service integration and testing (e.g., LiDAR)

Repeatability (Same team, same experimental setup)

Reproducibility (Different team, same experimental setup)

Replicability (Different team, different experimental setup)
## Documented and with reference implementation

* Concepts fully documented

* Reference implementation:

* Terraform (AWS/GCP/OpenStack) + Ansible for deployments

* k8s

* OAI

* Software and/or hardware

* USRP/AW2S

* Tofino/Tofino2 with SD-Fabric

* Complete documentation and SLICES academy integration

<figure><img src="image_9.png" /></figure>
# Documented and with reference

<figure><img src="image_10.png" /></figure>

* Software

<figure><img src="image_11.png" /></figure>

<figure><img src="image_12.png" /></figure>

<figure><img src="image_13.png" /></figure>

* Code

<figure><img src="image_14.png" /></figure>

## Deployment

<figure><img src="image_15.png" /></figure>

<figure><img src="image_16.png" /></figure>
# Lessons learned – Diversity (1/2)

* On-prem

* Core + HW RAN @ Eurecom

* Core + HW RAN @ Inria Sophia

* Core/RAN split

* Local 200Gbps fiber: Core @ Inria Sophia / HW RAN @ Eurecom

* International dedicated VLAN 1Gbps/10ms: Core @ imec / RAN @ Inria Sophia

* Commercial Internet:

* Core @ Sorbonne Université / RAN @ UTH

* Core @ Sorbonne Université / RAN @ Inria Sophia

* Split 7.2 Core + RAN @ Inria Sophia

* Public cloud aided

* Core by Inria @ GCP / HW RAN @ Eurecom

* Core by Inria @ GCP / HW RAN @ UTH

* Core @ CNR / RAN by Inria @ GCP

* In testbeds

* Summer school in TUM testbed, Virtual Wall

<figure><img src="image_17.png" /></figure>

<figure><img src="image_18.png" /></figure>

<figure><img src="image_19.png" /></figure>

<figure><img src="image_20.png" /></figure>
Lessons learned – Diversity (2/2)

* Network interconnect

* Commercial Internet accessible

* Dedicated links

* VPN service

* Identification / Authentication

* Users based on the light federation from SLICES (OIDC) is ok

* PKIs... how to unify certificates

* People test first in virtual environments (must support VM)

<figure><img src="image_21.png" /></figure>

slicesc
# Lessons learned – HW is a real constraint

* O-RAN Open FHI in OpenAirInterface

* Optimized for Intel-based x86-64 (e.g., AVX512)

* How to move to AMD and ARM?

* Complexity in network infrastructure

* Raw Ethernet

* Usually 3 VLAN (need sr-iov): management, control/user plane

* PTP distribution and PTP HW time stamping on NICs

<figure><img src="image_22.png" /></figure>
# Lessons learned – Doomed by dependencies

* Strong dependency with independent open source projects

* all with their own agenda

* dependencies brake frequently

* freeze versions whenever possible

* document dependency graph

* test, test, test

<figure><img src="image_23.png" /></figure>
# Lessons learned – Monitoring is key

* Passive measurement is hard (e.g., P4, snmp)

* Active measurement is impossible (e.g., LLDP, CPU load)

* What is really needed?

<figure><img src="image_24.png" /></figure>
Roadmap (->2024)

* Seed ->| 06/2022

* PoC ->| 06/2023

* First deployments ->| 12/2023

* Pre-operation ->| 06/2024
# Roadmap (->2024)

* Seed ->| 06/2022

* PoC ->| 06/2023

* First deployments ->| 12/2023

Get involved with our next hackathon!
<figure><img src="image_25.png" /></figure>