Commit dc6fe652 authored by Yann Garcia's avatar Yann Garcia
Browse files

Start workinmg procedure: Learning phase

parent 8c5a2f6f
Loading
Loading
Loading
Loading
+94 −0
Original line number Original line Diff line number Diff line
@@ -632,8 +632,102 @@ The counterpart is a huge changes in the current ETSI MEC Sandbox architecture,


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


### 4.2 Phase 1: Preparation and Analysis


#### A.4.1.1 Learning phase


The purpose is to learn how Simu5G/SimuLTE simulators are working.

##### A.4.1.1.1 Install OMNeT++ 6.0.x/INet Framework 4.x
   ```bash
   # Download the latest package [here](https://omnetpp.org/download/)
   # Execute the script `install.sh`
   # Execute `source setenv`
   # Run the IDE `omnetpp`
   # Install OMNeT++ 6.0.x
   ```

**Note**: Visit [this link](https://inet.omnetpp.org/Installation.html).

##### A.4.1.1.2 Testing Basic Functionality
- Run example scenarios
- Verify 4G/5G simulation capabilities
- Test MEC integration features

**Note**: Visit [this link](https://omnetpp.org/documentation/).

##### A.4.1.1.3 Install Simu5G/SimuLTE:
   ```bash
   # Install INET Framework 4.5.x
   # Clone and build Simu5G
   git clone https://github.com/Unipisa/Simu5G.git
   cd Simu5G
   make
   ```

##### A.4.1.1.4 Testing Basic Functionality
- Run example scenarios
- Verify 4G/5G simulation capabilities
- Test MEC integration features

### A.4.2 Phase 2: Architecture Design

#### A.4.2.1 Integration Architecture

##### A.4.2.1.1 Design Components

###### A.4.2.1.1.1 Simu5G/SimuLTE Service
- New microservice: `meep-simu5g-engine`
- Runs OMNeT++ simulation in container
- Exposes REST API for scenario control

###### A.4.2.1.1.2 Simulation Adapter
- Converts MEC Sandbox scenarios to Simu5G/SimuLTE configuration
- Maps POAs to gNB/eNodeB
- Maps UEs to simulation UE entities

###### A.4.2.1.1.3 Metrics Bridge
- Extracts metrics from simulation
- Converts to MEC Sandbox format
- Publishes to Redis/InfluxDB

###### A.4.2.1.1.4 Real-Time Emulation Bridge
- TUN/TAP interfaces for pod connectivity
- Network namespace integration
- Traffic routing between pods and simulation

#### A.4.2.2 Architecture Diagram
```
┌──────────────────────────────────────────────────────┐
│              MEC Sandbox Control Plane               │
│  ┌──────────┐  ┌──────────┐  ┌──────────┐            │
│  │GIS Engine│  │TC Engine │  │RNIS      │            │
│  └────┬─────┘  └────┬─────┘  └────┬──────┘           │
└───────┼─────────────┼─────────────┼──────────────────┘
        │             │             │
        └─────────────┴─────────────┘

        ┌─────────────▼─────────────┐
        │   Simulation Adapter      │
        │  (Scenario Converter)     │
        └─────────────┬─────────────┘

        ┌─────────────▼─────────────┐
        │   Simu5G/SimuLTE Engine   │
        │   (OMNeT++ Simulation)    │
        └─────────────┬─────────────┘

        ┌─────────────▼─────────────┐
        │   Metrics Bridge          │
        │   (Extract & Publish)     │
        └─────────────┬─────────────┘

        ┌─────────────▼─────────────┐
        │   Redis / InfluxDB        │
        └───────────────────────────┘
```

#### 4.2.2.3 Component Design