Open APIs

Hello Michel,

I also did not found any guiding principles about the topic. As well I didn't find Domain Context Specialization for MEF.

On the MEF website, I found only a diagram that somehow differentiates between the use of TMF and MEF APIs. You may have already seen it.

There is some analysis material on the Standardizing Wholesale Broadband - Fibre Access (BFA) project which partially addresses this topic ( note you have to be a member and join the project at TM Forum - Site Content - Page - Collaboration projects)

DCS Options Pros - Cons - Standardising Wholesale Broadband – Fibre Access (BFA) - TM Forum Confluence

MEF and TMF Wholesale BB Analyse - Standardising Wholesale Broadband – Fibre Access (BFA) - TM Forum Confluence

on guidelines I believe the API team is developing as part of API guidelines  update but not aware of anything be published over an above what is in the two references above.  Maybe an API team member can comment

------------------------------
Dave Milham
TM Forum, Chief Architect
------------------------------

MEF is currently working with TM Forum to align their APIs with the Gen5 Open API standards - see this press release and the extract below:

TM Forum and MEF are collaborating to harmonize MEF's APIs with TM Forum's Gen5 Open API standards to streamline automation within the MEF Network-as-a-Service (NaaS) domain, including Carrier Ethernet and IP services, SD-WAN and E2E network slicing, SASE, SSE and ZTNA delivered across a global partner ecosystem. Through the project, MEF's Lifecycle Service Orchestration (LSO) automation APIs will become fully conformant with TM Forum's Gen5 Open API standards. Harmonization with TM Forum Gen5 APIs will enable fully automated end-to-end management and operations of MEF NaaS services, reducing costs and speeding time to market. Initial work on the first APIs has established a clear technical path to delivering a full API suite for automation within MEF's NaaS domain by the end of 2025.

The plan is for the MEF Sonata APIs to become Gen5 DCS APIs and remain aligned to the Open API standards.  MEF will define the payloads for their NaaS domain, and will also collaborate with TM Forum to define the service models for the MEF NaaS domain which will enable end-to-end automation (see the diagram posted by Yurii).  The work is in progress.

Hi,

Assuming you are a member of most relevant TMF project (=Wiki spaces in TMF Confluence), you can search "MEF" in the wiki. That will give you additional information (e.g. "how to use ODA to realise MEF", "TMF-MEF alignment").

IG1228 also has a use case using MEF.

Matthieu

PS: in addition to MEF, there is a also the https://camaraproject.org/ that has defined multiple telecom APIs