add annex 7: Federation Management and GSMA Northbound Interface (NBI) Technical Procedure (ToDo)

- Identified mismatches, semantic gaps, or payload inconsistencies are documented during implementation.

- Normative updates to ETSI GS MEC 040 are proposed only after validated software evidence.

<mark>For both integration options given below an implementation of MEC 10-2 is required.</mark> 

<mark>For  integration options, an implementation of MEC 10-2 is required.</mark> 

## A.7 GSMA Northbound Interface (NBI) – Future Work (ToDo)

## A.7 Federation Management and GSMA Northbound Interface (NBI) – Technical Procedure (ToDo)

In addition to the federation lifecycle alignment analysed in this annex (Mff ↔ EWBI), further work is required to assess and integrate selected **GSMA Operator Platform Northbound Interface (NBI)** APIs within the ENC platform.

### A.7.1 Introduction

The following NBI functional areas are identified as **ToDo items** for subsequent phases of analysis and implementation:

This clause defines the technical procedure for integrating **Federation Management** and the **GSMA Operator Platform Northbound Interface (NBI)** into the ENC platform.

- **AvailabilityZoneInfoSynchronization**

  Management and synchronization of partner Operator Platform (OP) availability zones and related status updates.

  Future work shall evaluate alignment with MEC system/resource discovery models and federation-aware exposure of availability information.

The implementation depends on the architectural option selected in Clause A.4:

- **ArtefactManagement**

  Upload, removal, and retrieval of application descriptors, charts, and packages over E/WBI toward a partner OP.

  Future analysis shall assess compatibility with ETSI GS MEC 010-2 application package management and the MEC 037 package structure, including the potential need for an adapter layer.

* Option 1 – MEC FM-Centric Native Implementation

* Option 2 – Transformation Function Integration

* Option 3 – Software-First Integration

- **ApplicationOnboardingManagement**

  Registration, retrieval, update, and removal of applications toward a partner OP.

  Alignment with MEC federation onboarding procedures and CAMARA Edge Application Management APIs shall be evaluated.

The procedure below outlines the required milestones and technical components. Detailed API harmonization and implementation tasks shall be performed according to the selected option.

- **ApplicationDeploymentManagement**

  Creation, update, retrieval, and termination of application instances over E/WBI toward a partner OP.

  Federation-aware lifecycle management, cross-domain orchestration, and instance state synchronization require further analysis.

At this stage, the integration of the GSMA NBI APIs is considered outside the scope of the present feasibility assessment and remains subject to:

### A.7.2 Phase 1: Federation Management Integration

TODO

### A.7.3 Phase 2: API Analysis and Semantic Alignment (NBI)

TODO

### A.7.4 Phase 3: Architecture Design

#### A.7.4.1 Integration Model Selection

Based on Option 1, 2, or 3:

* Define whether NBI is hosted:

  * Inside MEFM (Option 1),

  * Through a Transformation Function (Option 2),

  * Natively via OpenOP components (Option 3).

TODO

---

#### A.7.4.2 Component Design

TODO

### A.7.5 Phase 4: Availability Zone Information Synchronization

TODO

### A.7.6 Phase 5: Artefact Management Integration

TODO

### A.7.7 Phase 6: Application Onboarding Management

TODO

### A.7.8 Phase 7: Application Instance Lifecycle Management

TODO

### A.7.9 Phase 8: Testing and Validation

TODO

### A.7.10 Phase 9: Standardization Feedback

TODO

- Architectural decisions taken for the ENC federation model (Option 1, Option 2, or Option 3),

- Identification of normative gaps in ETSI GS MEC 040,

- Alignment considerations with GSMA NBI/CAMARA API frameworks.