Suzy Gu Deepak Kataria Oleg Berzin
The purpose of Public Cloud Edge Interface (PCEI) Blueprint family is to specify a set of open APIs for enabling interworking between multiple functional entities or Domains that provide services needed for implementation of Edge capabilities/applications that require close integration between the Mobile Edge, the Public Cloud Core and Edge as well as the 3rd-Party provided Edge functions. As Public Cloud Service Providers and 3rd-Party Edge Compute/Application Providers deploy Edge instances to better serve their end users and applications, Telco/Mobile Network Operator (MNO) Edge deployments offer many opportunities for collaboration by exposing their network capabilities to provide value added services (note that in this document the terms Telco and MNO are used interchangeably).
Currently, the challenges include (but not limited to):
By leveraging Data Center and Interconnection infrastructures, this BP family is targeted to develop solutions addressing these challenges for MNOs, Public Cloud and 3rd-Party MEC providers,.
The Mobile Edge deployments will provide APIs to support below capabilities:
Public Cloud Service Providers and 3rd-Party MEC Providers are deploying Edge instances to better serve their end-users and applications, A multitude of these applications require close inter-working with the MNO Edge deployments to provide predictable latency & throughput, reliability, and other telco-grade requirements. The purpose of this blueprint family is to specify a standard set of APIs to expose towards Public Cloud and 3rd-Party MEC Service Provider instances at the Edge.
The need to interface and exchange information through these open APIs will allow competitive offerings for Consumers, Enterprises, and Vertical Industry end-user segments. For instance, open APIs will be provided between Telcos and public cloud edge compute platforms such as Google Cloud Platform (GCP) Anthos, AliCloud Edge Node Service (ENS), AWS Wavelength, Microsoft Azure Edge Zones, Tencent ECM, to name a few. These APIs are not limited to providing basic connectivity services but will include the ability to deliver predictable data rate, predictable latency, reliability, service insertion, security, AI and RAN analytics, network slicing, and more. These capabilities are needed to support a multitude of emerging applications such as AR/VR, Industrial IoT, autonomous vehicles, drones, Industry 4.0 initiatives, Smart Cities, Smart Ports. Other APIs will include exposure to edge orchestration and management, Edge monitoring (KPIs), and more. These open APIs will be the foundation for service and instrumentation APIs when integrating with public cloud development environments and will be defined as part of the implementation. Even though these APIs will be common across all Telco operators, the differentiation will based on services provided through those APIs.
Jane Shen Deepak Kataria Oleg Berzin
The high-level architectural view of PCEI is shown below in Figure 1. This BP will bring a new "Enabler" layer as PCEI between the Mobile/Telco Network and Public Cloud as well as the 3rd-Party MEC platforms at the Edge. The PCEI Enabler layer is responsible for :
In the Southbound direction (PCEI to MNO), this layer will encapsulate the core network capabilities, interwork with BSS/OSS/management system from telco operators. Depending on the business model, this layer may be deployed as part of the MNO functions on MNO edge hardware resources. The PCEI Enabler may also be deployed by a neutral operator (e.g. a Data Center and Interconnection provider) in highly interconnected and distributed locations where the Public Clouds, the 3rd-Party MEC providers as well as many other ecosystem partners meet and exchange traffic and data.
Note that as part of the Southbound capabilities, there is a need for APIs exposed by the Data Center providers, Bare-Metal Hardware Orchestration providers as well as the Interconnection providers in order to facilitate distribution of processing resources as well as the interconnection between multiple entities providing/consuming Edge services/applications.
In the Northbound direction (PCEI to Public Cloud and/or 3rd-Party MEC providers), it exposes RESTFUL APIs and SDKs to be called and integrated by the Edge services/application providers.
Figure 1. High-level Architecture of PCEI.
The PCEI Enabler is expected to provide Multi-Domain Interworking capabilities between the following domains:
The following figure shows high-level relationships between the domains:
Figure 2. PCEI Domains.
The Data Center Facility (DCF) Domain. The DCF Domain includes Data Center physical facilities that provide the physical location and the power/space infrastructure for other domains and their respective functions.
The Interconnection of Core and Edge (ICE) Domain. The ICE Domain includes the physical and logical interconnection and networking capabilities that provide connectivity between other domains and their respective functions.
The Mobile Network Operator (MNO) Domain. The MNO Domain contains all Access and Core Network Functions necessary for signaling and user plane capabilities to allow for mobile device connectivity. These functions include the Radio Access Network (RAN), including the 5G New RAN (5GNR), Packet Core, including the Virtualized Evolved Packet Core (vEPC) and the 5G Core (5GC).
The Public Cloud Core (PCC) Domain. The PCC Domain includes all IaaS/PaaS functions that are provided by the Public cloud to their customers. These include Virtual Private Cloud and Public/Private Networking capabilities.
The Public Cloud Edge (PCE) Domain. The PCE Domain includes the PCC Domain functions that are instantiated in the DCF Domain locations that are positioned closer (in terms of geographical proximity) to the functions of the MNO Domain. In general, the PCE functions are expected to be managed from the PCC functions.
The 3rd party Edge (3PE) Domain. The 3PE domain is in principle similar to the PCE Domain, with a distinction that the 3PE functions may be provided by 3rd parties (with respect to the MNOs and Public Clouds) as stand-alone instances of Edge Computing resources/applications.
The PCEI Reference Architecture and the Interface Reference Points (IRP) are shown in the figures below. Note this figure also provides a component layer view of the PCEI Architecture:
Figure 3a. The PCEI Summary Reference Architecture.
Figure 3b. The PCEI Detailed Reference Architecture.
The PCEI Reference Architecture layers are described below:
The PCEI Data Center (DC) Physical Layer belongs to the DCF Domain and provides the physical DC infrastructure located in appropriate geographies (e.g. Metropolitan Areas). It is assumed that the Public Cloud Core infrastructure is interfaced to the PCEI DC Physical Layer through the PCEI L1-L3 Interconnection layer.
The PCEI L1-L3 Interconnection Layer belongs to the ICE Domain and provides physical and logical interconnection and networking functions to all other components of the PCEI architecture.
Within the MNO Domain, the PCEI Reference Architecture includes the following layers:
Within the Public Cloud Domain, the PCEI Reference Architecture includes the following layers:
Within the 3rd Party Edge Domain, the PCEI Reference Architecture includes the following layers:
The PCEI Enabler. A set of functions that facilitate the interworking between PCEI Architecture Domains. The structure of the PCEI Enabler is described later in this document.
The PCEI Portal. An optional component of the PCEI Architecture responsible for providing the users of PCEI a way to express and communicate their intended functional, performance, and service requirements.
P1 – User Intent. Provides ability for User/Customer to specify PCEI access and functional requirements E.g. Type of Access, Performance, Connectivity, Location, Topology
P2 – Interface between PCEI and Mobile Network. Provides the ability to accept requests from MNO for PCEI service and request MNO to provide 4G/5G access to PCEI customers. E.g. Network Slicing, LBO.
P2' - Interface between PCEI and the MNO Core Functions such as UPF, SMF. In case of a UPF the P2' interface can be used to configure the parameters responsible for interfacing the UPF and the virtual/contextual configuration structures within the UPF with the PCC/PCE and 3PE resources by way of the L1-L3 Interconnection layer. The P2' interface implies the availability of standard or well-specified UPF provisioning models provided by MNOs.
P3 – Interface between PCEI and Compute Hardware Orchestrator for distributed MNO functions (e.g. non-MNO locations). Provides ability for PCEI to trigger orchestration of appropriate HW resources for MNO User Plane and other appropriate functions. May be triggered through P2 by MNO
P4 – Interface between PCEI and Interconnection Fabric. Provides abilities to request and orchestrate network connectivity and performance KPIs between MNO UPF, Cloud Core and Edge resources (including 3rd Party Edge)
P5 – Interface between PCEI and 3rd Party Edge Functions (e.g. NFV). Provides abilities to access Edge APIs exposed by 3rd Party Edge Functions (e.g. deployment of NFVs and Edge Processing workloads)
P6 – Interface between PCEI and Edge Compute Hardware Orchestrator. Provides the ability for PCEI to trigger orchestration of appropriate HW resources for Edge Compute functions including Public Cloud Edge and 3rd party Edge.
P7 – Interface between PCEI and Public Cloud Edge Functions (maybe part of P8). Provides abilities to access APIs to deploy Public Cloud Edge functions/Instances (may be done through P8)
P8 - Interface between PCEI and Public Cloud Core Functions (may include control over Public Cloud Edge functions). Provides the ability to access Public Cloud APIs including the ability to deploy Public Cloud edge functions.
P9 - Interface between PCEI and the NFVI layer of the 3PE Domain. P9 may be used If an MNO chooses to expose the NFVI layer to PCEI.
PCEI Enabler is based on EMCO - Edge Multi-Cluster Orchestrator:
The target software architecture of the PCEI Enabler based on EMCO is shown below. Note that all references to specific APIs and SDOs are for mapping purposes only, subject to ongoing analysis and do not indicate compliance with APIs/SDO specs.
Figure 4. General structure of PCEI Enabler.
Jane Shen Deepak Kataria
APIs with reference to Architecture and Modules
High-Level definition of APIs are stated here, assuming Full definition APIs are in the API documentation
Suzy Gu Deepak Kataria
provide an end to end deployment with this enable layer between telco and public cloud.