ETSI’s Mobile Edge Computing ISG looks to define MEC terminology, lay out technical requirements and use cases for mobile network deployments
The European Telecommunications Standards Institute released a trio of “foundation-level” group specifications through its Mobile Edge Computing Industry Specifications Group, which it claims define MEC terminology, study technical requirements and use cases, and specify the framework and reference architecture of MEC.
ETSI said by providing a “glossary of terms related to the conceptual, architectural and functional elements” of MEC will support a more consistent use of terminology within ETSI MEC specifications and more widely across the industry. The study technical requirements and use cases are expected to support greater interoperability and deployment, and describe examples of use cases of MEC, while the framework and reference architecture is said to enable mobile edge applications to run more efficiently and seamlessly in a mobile network.
Together, ETSI said the moves should help maintain MEC “momentum in the industry,” with the technology seen as a “key building block in the evolution of mobile broadband networks, complementing [network functions virtualization] and [software-defined networking].”
Moving forwards, ETSI said its MEC ISG is working on nine new studies related to APIs, management interfaces and platform functionality; plans to study mobile edge computing in an NFV environment; and work on end-to-end mobility. The group noted MEC has been identified as a “key enabler for [Internet of Things] and mission-critical, vertical solutions and is recognized as one of the key architectural concepts and technologies for ‘5G.’”
ETSI earlier this month said its Open Source MANO group has laid out a roadmap for work this year on management and orchestration efforts, including a leadership structure and plans to roll out an initial specification release. ETSI plans to launch Release 0 of its plans within the next two months, with that release is set to include a code base from Telefonica, RIFT.io, Canonical and others, with plans for new releases using open source workflows and tools to be issued every six months. Further support is to come from an end user advisory group to supply “guidance to overcome the challenges in functional requirements of the code and those arising from the real world integration with existing systems, notably the existing [operating support and business support] systems of service providers.”
Bored? Why not follow me on Twitter
