update federation integration options

MEO → MEFM → Mff → OpenOP Partner 

(Image) -->

Based on below following option can be approched:

Based on above following options can be approched:

option1: MEC FM-Centric Native Implementation for Federation

option2: Complete GR study. Based on GR, do software word, and optionally followed MEC 40 can be enhanced

### A.4.2 Option 1: MEC FM-Centric Native Implementation for Federation

<!-- ### A.4.2 Option 1: MEC FM-Centric Native Implementation for Federation

This option involves extending the ETSI GS MEC 040 Federation Management APIs to normatively support

translation of GSMA PRD OPG.04 EWBI semantics into MEC 040 federation constructs.

This capability may leverage the ETSI SDG OpenOP Transformation Function (TF) SDK as a reference

implementation, or a simplified TF integrated within MEC 040 or the ENC platform, to perform the required

translation and normalization logic.

translation and normalization logic. -->

### A.4.2 Option 1: MEC FM-Centric Native Implementation for Federation

This option follows a standards-first approach in which federation alignment between ETSI MEC and GSMA Operator Platform is primarily achieved through normative enhancement of ETSI GS MEC 040, based on analysis of GSMA PRD OPG.04.

The objective is to make the MEC Federation Manager (MEFM) natively capable of supporting EWBI-aligned federation semantics on the Mff reference point.

The approach proceeds in three steps.

#### Step 1 – Completion of the Present GR Study

The present Group Report performs:

- Detailed semantic gap between ETSI GS MEC 040 (Mff procedures) and GSMA PRD OPG.04 (EWBI Federation Management APIs), including relevant GSMA NBI elements.

- Mapping of lifecycle operations (Create, Update, Retrieve, Remove).

- Analysis of federation directionality, availability zone exposure, capability exchange, and notification models.

- Determination of required extensions to MEC information models.

The outcome of this step is a technically validated gap analysis forming the basis for normative enhancement.

#### Step 2 – Normative Enhancement of ETSI GS MEC 040

Based on the GR findings, ETSI GS MEC 040 is enhanced to:

- Define explicit Mff payload structures aligned with EWBI semantics.

- Introduce normative attribute definitions where currently informative references exist.

- Clarify federation lifecycle state models.

- Define optional or mandatory support of EWBI-aligned capabilities.

The MEFM becomes normatively capable of interoperating with EWBI.

#### Step 3 – Software Implementation

Following normative alignment:

- The MEC Federation Manager (MEFM) is implemented according to the enhanced ETSI GS MEC 040 specification.

- Federation state management is handled natively inside MEFM.

- If required, an internal transformation module may be implemented to normalize external EWBI payload formats, but this remains an implementation detail.

- Interoperability testing is performed against Operator Platform implementations such as the ETSI SDG OpenOP Federation Manager.

<!-- 

#### Architecture:

    TF["Transformation Function (EWBI Mapping)"]

    OPFM["OpenOP Federation Manager (Partner)"]

    MEO <--> MEFM

    MEFM <--> TF

    TF <--> OPFM

    MEO < MEFM

    MEFM < TF

    TF <--OPFM

```

 -->

### A.4.3 Option 2: GR-Based Study Followed by Software-First Integration and Subsequent Normative Alignment of ETSI GS MEC 040

### Step 1 – GR Study Phase

A dedicated Group Report (GR) shall be conducted to:

The present Group Report (GR) analyses:

- Analyse semantic differences between ETSI GS MEC 040 (Mff) and GSMA PRD OPG.04 (EWBI).

- Identify payload mismatches and structural inconsistencies.

- Assess lifecycle alignment between MEC Federation procedures and OPG.04 Federation Management APIs.

- Evaluate transformation requirements and architectural placement options.

- Assess lifecycle alignment between MEC Federation procedures and OPG.04 Federation Management APIs (included NBI APIs).

- Transformation requirements and architectural placement options.

- High-level architectural design options for integrating MEC Federation with GSMA Operator Platform components, including potential Transformation Function placement, MEFM enhancements, and interaction flows.

The GR serves as a technical investigation document and does not introduce normative changes.

- Interoperability validation is performed using real software evidence.

### Step 3 – Normative Alignment Phase

Following validated implementation results:

### Step 3 – Optional Normative Alignment Phase

* Identified gaps are analysed.

* Concrete proposals are prepared to enhance ETSI GS MEC 040.

* Normative updates may introduce:

Following validated implementation results, normative updates to ETSI GS MEC 040 may be considered:

  * Clarified Mff payload semantics,

  * Explicit alignment with OPG.04,

  * Optional normative mapping rules.

- Identified gaps are analysed.

- Concrete proposals are prepared to enhance ETSI GS MEC 040.

This step ensures that normative evolution is driven by validated software experience rather than theoretical assumptions.

-> This step ensures that normative evolution is driven by validated software experience rather than theoretical assumptions.

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