Jump to content

Multi-access edge computing

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by NokiaMEC (talk | contribs) at 14:35, 13 October 2014 (Created page with '{{subst:AFC submission/draftnew}} <!--- Important, do not remove this line before article has been created. ---> Mobile Edge Computing (MEC) is a Network arch...'). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

Mobile Edge Computing (MEC) is a Network architecture concept that enables Cloud computing capabilities and an IT service environment at the edge of the Cellular network.

MEC has been developed from the evolution of cellular base stations and is driven from the convergence of IT and telecommunications networking. It promises a new ecosystem and value chain where cellular operators can open their Radio access network (RAN) to authorized third-parties, such as application developers and content providers.

MEC will enable the flexible and rapid deployment of innovative applications and services towards cellular subscribers, Enterprise and vertical segments. RAN characteristics such as proximity, context, agility and speed can be translated into value for the various stakeholders in the value chain.

Distributed computing in the RAN

MEC provides a highly Distributed computing environment for application and service hosting. It also has the ability to store and process content in close proximity to cellular subscribers, creating a more responsive experience. Applications can also be exposed to real-time RAN information to offer a personalized and contextualized experience.

The key element is the MEC application server, which is integrated at the RAN element. This server provides computing resources, storage capacity, connectivity and access to RAN information. It supports a flexible and efficient Multitenancy run-time and hosting environment for applications. The Virtual appliance applications are delivered as packaged operating system Virtual machine (VM) images, allowing complete freedom of implementation. The platform also provides a set of Middleware application and infrastructure services. Application software can be provided from equipment vendors, service providers and third-parties. The MEC application server and its services are application agnostic.

Deployment scenarios

The MEC application server can be deployed at various locations within the RAN: the macro base station EnodeB that is part of an LTE cellular network, the Radio Network Controller (RNC) that is part of a 3G cellular network and at a multi-technology cell aggregation site. The multi-technology cell aggregation site can be located indoors within an Enterprise (e.g. a hospital, a large corporate headquarters) or indoors/outdoors in a large public building or arena (e.g. a shopping mall, a stadium) to control a number of localized access points.

Business and technical benefits

A cellular operator can rapidly deploy new services for different business segments that drive new revenue streams and differentiate subscriber experience. Applications that are aware of the local context in which they operate will drive the creation of new service categories with enriched and personalized offerings.

Application and service hosting at the edge of cellular networks will reduce the volume of signaling offloaded to the core network, as well as reducing Operating Expenditure (OPEX) for the cellular operator compared to hosting applications and services within the core.

MEC will give the cellular operator the ability to recognize revenue based on the application server resource usage, in terms of storage, network bandwidth, CPU utilization, etc, for each application or service deployed by a third party.

Application developers and content providers can benefit through the development of innovative applications and services that take advantage of close proximity to cellular subscribers and real-time RAN information.

MEC is underpinned with the use of open standards and Application programming interfaces (APIs). Familiar programming models, relevant tool chains and Software development kits (SDKs) are key pillars to encourage and expedite the development of new and disruptive applications for the new MEC environment.

MEC use cases

A number of different use cases that leverage the benefits of MEC are already available.

Active Device Location Tracking is a use case that enables real-time network measurement-based tracking of active terminal equipment, totally independent of Global Positioning System (GPS) functionality. The use-case is derived from third-party Geolocation algorithms within an application hosted on the MEC application server. This use case leverages from efficient and localized measurement processing and is advantageous where GPS coverage is not available.

Distributed content and Domain Name System (DNS) caching is a use case that leverages from the proximity to connected subscribers to create an improved experience, as well as providing relief to other parts of the cellular network (e.g. core and transport).

Further details can be found from the Introductory Technical White Paper (section 2.4)[1]

MEC within the European Telecommunications Standards Institute (ETSI)

ETSI plays an active role in the development and implementation of telecommunication standards, some of which relate to cloud and internet technologies. The MEC initiative is a new Industry Specification Group (ISG) within ETSI, officially formed on September 26th, 2014. The initiative has been created with a set of founding members as per Annex 2 of the MEC ISG Agreement for ETSI Members [2]. The founding members are Nokia Networks, Huawei, IBM, Intel, NTT DoCoMo and Vodafone. Other members are encouraged to actively participate in the ISG, to contribute to the development of the specifications, to share best practices and demonstrate Proof of Concepts.

MEC ISG deliverables

The objective of the MEC ISG is to create a standardized and open environment for the efficient and seamless integration of applications for multi-vendor MEC platforms. This interoperability is also key in developing favorable market conditions to create sustainable business for all players in the value chain and to facilitate global market growth.

The ISG will produce (Standards Track Deliverables) interoperable and deployable group specifications that will allow the hosting of applications in a multi-vendor MEC environment. An informational Ontology containing the terminology to be used consistently by the set of MEC specifications will also be produced. The following (normative) specifications will be developed:

  • Requirements
  • Framework and reference architecture
  • Gap analysis, identifying critical functional elements and techniques that need to be standardized to provide greater value
  • Specifications relating to the platform services and APIs

In addition, the ISG MEC will advance MEC within the industry, to accelerate the adoption of the concept and the standards and will strive to create a favorable legal and regulatory environment. The group will produce informative reports in the form of white papers and tutorials and will arrange workshops and events.

Relationship to Network Functions Virtualization within ETSI

Network Functions Virtualization (NFV) is focused on porting network functions to virtual environments in order to enable the migration from proprietary appliance based embodiments to a standard hardware and cloud based infrastructure.

MEC brings a new dimension of capability by focusing on innovative applications and services that are hosted within the RAN. The MEC ISG has a different business objective than NFV, but utilizes some of the concepts/solutions developed for NFV. Both concepts can be complementary, although they can exist independently.

ETSI portal for MEC

Additional information concerning the MEC ISG can be found from the ETSI website, which includes the MEC Introductory Technical White Paper that introduces the concept and the related key market drivers. It also describes some key use cases, the enablers, the requirements and challenges for MEC as well as the objectives of the ISG.

References

  1. ^ [1] Introductory Technical White Paper
  2. ^ [2] MEC ISG Agreement for ETSI Members

ETSI portal for MEC ISG Introductory Technical White Paper MEC Executive Brief ETSI MEC Proposal Terms of Reference