add informative references

The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding but are not required for conformance to the present document.

<span id="_ref_i.1"></span><a name="_ref_i.1">[i.1]</a>

<span id="_ref_i.1"></span><a name="_ref_i.1">[i.1]</a> [ETSI GS MEC 003](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/04.01.01_60/gs_mec003v040101p.pdf): \"Multi-access Edge Computing (MEC); Framework and Reference Architecture\".

<span id="_ref_i.2"></span><a name="_ref_i.2">[i.2]</a> [ETSI GS MEC 040](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.02.01_60/gs_MEC040v030201p.pdf): \"Multi-access Edge Computing (MEC); Federation enablement APIs\".

<span id="_ref_i.3"></span><a name="_ref_i.3">[i.3]</a> [GSMA OPG.02](https://www.gsma.com/solutions-and-impact/technologies/networks/wp-content/uploads/2012/10/OPG.02-v11.0-Operator-Platform-Requirements-and-Architecture.pdf): \"Operator Platform: Requirements and Architecture\".

<span id="_ref_i.4"></span><a name="_ref_i.4">[i.4]</a> [GSMA OPG.04](https://www.gsma.com/solutions-and-impact/technologies/networks/wp-content/uploads/2025/03/OPG.04-v6.0-EWBI-APIs.pdf): \"East-Westbound Interface APIs\".

# 3 Definition of terms, symbols and abbreviations

This annex provides a technical and architectural feasibility assessment for integrating GSMA Operator Platform (OP) federation capabilities—implemented within the ETSI SDG OpenOP project—into the Edge Native Platform (ENC).

The study evaluates interoperability between:

- ETSI MEC federation architecture as defined in ETSI GS MEC 003 and ETSI GS MEC 040,

- GSMA PRD OPG.04 (East/West Bound Interface – EWBI),

- ETSI MEC federation architecture as defined in ETSI GS MEC 003 [[i.1]](#_ref_i.1) and ETSI GS MEC 040 [[i.2]](#_ref_i.2) ,

- GSMA PRD OPG.04 (East/West Bound Interface – EWBI) [[i.4]](#_ref_i.4),

- GSMA Operator Platform Northbound Interface (NBI),

- API exposure and Edge Application Management principles.

The federation capabilities of MEC systems were introduced in:

- ETSI GS MEC 003

- ETSI GS MEC 040

- ETSI GS MEC 003 [[i.1]](#_ref_i.1)

- ETSI GS MEC 040 [[i.2]](#_ref_i.2)

The architectural motivation was to enable:

In parallel, the GSMA Operator Platform Group developed a “connect once, connect to many” federation paradigm and defines federation the East/West Bound Interface (EWBI) formalized in:

- GSMA OPG.0X

- GSMA OPG.04 [[i.4]](#_ref_i.4)

<!-- Correct below paragrah terms terminology -->

The EWBI allows operators to establish federation partnerships, synchronize availability zones, exchange capability information, and maintain status notifications between Operator Platform instances.

### A.3.1 Internal Registration (Mfm)

In MEC federation, internal system registration is performed via the Mfm reference point. This corresponds to Clause 5.2.2.1.1 of MEC 040, where the MEO registers to its local MEFM.

In MEC federation, internal system registration is performed via the Mfm reference point. This corresponds to Clause 5.2.2.1.1 of MEC 040 [[i.2]](#_ref_i.2), where the MEO registers to its local MEFM.

Before cross-system federation is possible:

### A.3.3 Information Model Considerations

ETSI GS MEC 040 [\[i.\]]() specifies Federation Enablement APIs primarily for interworking between MEC systems (via MEC Federators, or MEFs) to enable the shared use of services across different MEC or cloud systems. However, it (as per informative refence) aligns with the GSMA Operator Platform (OP), as described in informative refernce**clause 4.2**.

ETSI GS MEC 040 [[i.2]](#_ref_i.2) specifies Federation Enablement APIs primarily for interworking between MEC systems (via MEC Federators, or MEFs) to enable the shared use of services across different MEC or cloud systems. However, it (as per informative refence) aligns with the GSMA Operator Platform (OP), as described in informative refernce **clause 4.2**.

<!-- Remove this line -->

The operator platform is defined as a facilitator for seamless access to edge applications across federated networks (referencing GSMA PRD OPG.02 [\[i.\]]()).

The operator platform is defined as a facilitator for seamless access to edge applications across federated networks (referencing GSMA PRD OPG.02 [[i.3]](#_ref_i.3)).

MEC 040's federation procedures in clause 5.2.4 (Creation/Update/Removal of MEC federation between two partners) are informative and based on GSMA PRD OPG.04 clause 2.2.1 [\[i.\]](), which provides the normative details for federation over the East/West Bound Interface (E/WBI), as a result,

MEC 040's federation procedures in clause 5.2.4 (Creation/Update/Removal of MEC federation between two partners) are informative and based on GSMA PRD OPG.04 clause 2.2.1 [[i.4]](#_ref_i.4), which provides the normative details for federation over the East/West Bound Interface (E/WBI), as a result,

If an ETSI MEC system (via its MEF) needs to federate with a GSMA OP, the MEF acts analogously to an OP instance in the GSMA framework. The procedure uses the GSMA E/WBI APIs for directed (one-way) federation, where resources/capabilities are shared from the Partner (responding entity) to the Originating (initiating entity). This enables shared usage of MEC services/applications across MEC and OP systems.

Below is the detailed procedure, structured as per GSMA OPG.04 clause 2.2.1 [\[i.\]]().

Below is the detailed procedure, structured as per GSMA OPG.04 clause 2.2.1 [[i.4]](#_ref_i.4).

#### 1. Create Federation

- **Initiator**: Originating entity.

## A.4 Fedeation Architectural Integration Options

In MEC 040, it is given "These procedures provide key functionalities to establish MEC federation between two partners, which are based on the

GSMA PRD OPG.04 [5], clause 2.2.1.", but no normative work can be found on semantics on the Mff interface.

GSMA PRD OPG.04 [[i.4]](#_ref_i.4), clause 2.2.1.", but no normative work can be found on semantics on the Mff interface.

Howerver, GSMA PRD OPG.04 has define normatice work for EWBI semantics (I.e. payload, requests/response.)