Start Simu5G/Simu4G analysis

For the purposes of the present document, the [following] abbreviations [given in ... and the following] apply:

`5GC     5G Core`

`5G NR   5G New radio`

`API     Application Programming Interface`

`eNodeB  Evolved NodeB (4G base station)`

`EPC     Evolved Packet Core`

`gNB     gNodeB (5G base station)`

`GIS     Geographic Information System`

`IP      Inyernet Protocol`

`LTE     Long Term Evolution`

`MEC     Multi-access Edge Computing`

`POA     Point of Access`

`POC     Proof of Concept`

4. Static Characteristics: Network characteristics are configured, not dynamically calculated from radio conditions

5. No Core Network: No EPC/5GC simulation, only access network characteristics

## A.3 Simu5G/SimuLTE Description

### A.3.1 Overview

The Simu5G/SimuLTE simulators [\[i.5\]] are open-source, system-level network simulators built on the OMNeT++ [\[i.4\]] discrete event simulation framework. They provide comprehensive simulation of 3GPP-compliant 4G (LTE/LTE-A) and 5G (NR) networks.

The key characteristics are:

- Framework: OMNeT++ 6.0.x with INET Framework 4.5.x;

- License: LGPL v2.1;

- Language: C++;

- Architecture: Modular, event-driven simulation.

### A.3.2 SimuLTE (4G/LTE) features

Simu5G provides a full 4G/LTE/LTE-A (E‑UTRAN) data‑plane stack alongside 5G NR, including eNodeB, UE, and core gateway models that support LTE-only and LTE/NR dual-connectivity scenarios with:

- Complete LTE protocol stack (RRC, PDCP, RLC, MAC, PHY);

- EPC (Evolved Packet Core) simulation;

- Support for eNodeB and UE entities;

- Mobility management and handover procedures;

- Channel models (path loss, shadowing, fading);

- Traffic models and QoS support.

### A.3.3 Simu5G (5G NR) features

The Simu5G (5G NR) models the full 5G NR user‑plane stack (Rel‑16‑oriented) with gNB, UE, and UPF entities, supporting both Standalone NR and LTE–NR Dual Connectivity deployments over FDD and TDD, with heterogeneous cells and realistic PHY/channel models:

- 5G NR protocol stack (RRC, SDAP, PDCP, RLC, MAC, PHY);

- 5GC (5G Core) simulation;

- Support for gNB and UE entities;

- Advanced features: Network Slicing, MEC integration;

- Real-time emulation support;

- Integration with real applications.

### A.3.4 Simu5G/SimuLTE simulators capabilities

#### A.3.4.1 Realistic Radio Propagation

- Path Loss Models: Free space, Okumura-Hata, COST 231

- Shadowing: Log-normal shadowing

- Fading: Rayleigh, Rician, Nakagami-m fading models

- Interference: Inter-cell and intra-cell interference modeling

#### A.3.4.2 Protocol Stack Simulation

- Complete Stack: All layers from PHY to application

- 3GPP Compliance: Implements 3GPP specifications

- Dynamic Behavior: Handovers, connection establishment, bearer management

#### A.3.4.3 MEC Integration

- MEC Support: Built-in MEC entity models

- ETSI Compliance: Supports ETSI MEC standards

- Service Models: MEC services and applications

<mark>We have to check if we can integrate the ADVANTedge components. An implementation of MEC 10-2 is required. This can be another way to go.</mark> 

#### A.3.4.4 Real-Time Emulation

- Emulation Mode: Can run in real-time mode

- External Interfaces: TUN/TAP interfaces for real application integration

- Synchronization: Time synchronization with real world

#### A.3.5 Simulation modes

The Simu5G/SimuLTE simulators [\[i.5\]] provides 2 simulations:

- The non‑emulation simulation is pure, offline discrete‑event runs where all traffic endpoints are simulated modules and time is virtual, - - - The emulation simulation runs in real time and connect the simulated 5G network to real interfaces and applications so real packets traverse the simulated RAN and core network.

This is the emulation mode that is required here. The emulation scenarios map simulated network interfaces (e.g. at UE, router...) to real host interfaces (TAP/veth, NICs), so IP packets from real processes or devices enter the simulation, traverse the 5G NR/LTE stack, and return to the real network.

### A.3.5 Architecture

#### A.3.5.1 Overview

The fugure below shows a simplified architecture of Simu5G.

```

┌─────────────────────────────────────────┐

│         OMNeT++ Simulation Kernel       │

├─────────────────────────────────────────┤

│         INET Framework (TCP/IP)         │

├─────────────────────────────────────────┤

│  Simu5G/SimuLTE Network Models          │

│  ├── UE Models                          │

│  ├── gNB/eNodeB Models                  │

│  ├── Core Network Models                │

│  └── Channel Models                     │

├─────────────────────────────────────────┤

│  MEC Models (if applicable)             │

└─────────────────────────────────────────┘

```

#### A.3.5.2 Network description

<mark>To explain what is NED?</mark>

#### A.3.5.3 Behaviour implementation (C++ classes)

<mark>To explain behaviour implementation using C++ classes?</mark>

#### A.3.5.4 Probes

<mark>To explain how to use the probes?</mark>

#### A.3.5.5 ETS MEC Support in Simu5G

<mark>To explain ETS MEC support in Simu5G?</mark>

#### A.3.5.6 Why do we choose the Probes solution?

<mark>To explain why do we choose Probes mechanism isnstead of Simu5G MEC RNI?</mark>

#### A.3.5.5 How to develop a UE application in Simu5G environment

<mark>Not sure this clause is useful at this stage</mark>

### A.3.6 Advantages of Simu5G/Simu4G simulators

- Realistic Protocol Simulation: Complete 3GPP protocol stack

- Dynamic Network Behavior: Handovers, connection management, bearer setup

- Accurate Radio Models: Realistic propagation, fading, interference

- Core Network: EPC/5GC simulation for end-to-end scenarios

- MEC Integration: Built-in MEC support

- Research-Grade: Widely used in academic and industry research

### A.3.7 Limitations of Simu5G/Simu4G simulators

- Performance: Discrete event simulation can be slower than simple TC-based approach

- Complexity: Requires understanding of OMNeT++ and simulation concepts

- Integration: Need to bridge simulation with Kubernetes/Docker environment

- Real-Time: Real-time emulation requires careful synchronization

- WiFi: Limited WiFi support (additional modules are required, particularly )

### A.3.7 Conclusions

Even if this study does not cover WiFi support, the replacement of the current network simulation with Simu5G/SimuLTE simulators [\[i.5\]] represents a strategic upgrade that will transform the ETSI MEC Sandbox from a basic network emulator into a research-grade, 3GPP-compliant simulation platform.

The use of Simu5G/SimuLTE simulators [\[i.5\]] provides the following advantages:

- Accuracy & Realism with:

    - Realistic channel models;

    - Realistic metrics for MEC applications;

- Protocol-Level Simulation with:

    - Complete 3GPP stack (Dynamic, realistic network behavior);

    - Handovers, connection management, and resource allocation work as in real networks;

- Standards Compliance:

    - 3GPP-compliant;

    - Enhanced credibility, interoperability, and future-proofing;

- Advanced Features with:

    - Full 5G NR features → Network slicing, URLLC, eMBB, mMTC;

    - Support for cutting-edge 5G use cases and future requirements;

-Maintainability with

    - Community-supported (Shared maintenance, continuous improvements);

    - Faster feature development;

- Research Value with:

    - Research-grade platform;

    - Enable advanced research, academic collaborations, innovation;

- Business Value with:

    - Industry-standard → Enhanced market position;

    - Competitive advantage, better customer confidence, strategic positioning.

The counterpart is a huge changes in the current ETSI MEC Sandbox architecture, and a higher complexity. To support 10 simultaneous connections to the new ETSI MEC Sandbox, a very higher hardware requirements are necessary (CPUs, GPUs & memories). 

**Note:** In addition, a phase of learning is mandatory before to start the replacement of the current network similation by Simu5G/Simu4G simulators [\[i.5\]].

## A.4. Replacement procedure

### 4.1 Introduction

This part of the study propose a list of milestone to implement the replacement of the network simulation step by step.

# Annex B: <br>Title of annex

## B.1 First clause of the annex