The purpose of the Public Cloud Edge Interface (PCEI) Blueprint family is to specify a set of open APIs for Telco Edge Blueprints to expose towards Public Cloud Service Provider instances at the Edge. As Public Cloud Service Providers deploy Edge instances to better serve their end-users and applications, Telco Edge deployments offer many opportunities for collaboration by exposing their network capabilities to provide value added services.
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 provides Open APIs 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 Edge Computing Machine (ECM), to name a few. Open API coverage includes edge capability exposure, 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 be based on services provided through those APIs.
The purpose of this blueprint family is to address all aspects of API interoperability to include API definition, API gateway functions (AAA, policy, security) so as to offer a secure, controllable, traceable, scalable and measurable way for accessing APIs by public edge cloud service providers.
The partnership announcement between AWS and Verizon/KDDI/SKTelecom/Vodafone during last November's AWS re' Invent signified the official entrance of Hyperscalers into the MEC edge domain. Over the last 12 months, AT&T has announced partnerships with the big 3 Hyperscalers (AWS, Microsoft Azure and Google Cloud). In Asia, similar partnerships have formed between China Mobile and Tencent/Alibaba. It seems that after years of exploration, the MEC edge domain sees a viable business model where Hyperscalers bring in applications and end-users, while the mobile network operators leverage their edge capabilities and locations.
Telcos and Hyperscalers are powerful in their respective domains. How would their partnerships work when they meet at the edge? What would be the technical collaboration interfaces? Within each country, usually there are M operators with overlapping coverages coverage and N Hyperscalers serving the same areas. With this M to N mesh relationship, would it make sense to have common interfaces? Hyperscalers are big on APIs – how would Telco network edge capabilities be exposed as APIs? There are many questions . However there are with no ready-made answers. Needless Needless to say, the business relationships of all MEC Edge players is are equally important in this domain. Telcos and Hyperscalers both carry their own eco-systems. How these eco-systems would collaborate poses another challenge.
This blueprint project family intends to help find these answers. The project will showcase collaboration via case studies. Meanwhile, broader discussions will be held with telcos and Hyperscalers during the project phase. With the massive deployment of 5G in the coming years, MEC Edge is not only a location play , but also a network capability play. In order to promote a rich application developer ecosystem, Telcos will need to expose network capabilities in a synergistic manner to public edge cloud service providers and other third parties to deliver value to the application developer and end-user segments. The game for Telco Edge starts to get interesting. .
| View file | ||||
|---|---|---|---|---|
|
Use Case Details:
Attributes | Description | Informational | ||
Type | New | |||
Industry Sector | Cloud, Telco | |||
Business driver |
| Public Cloud Service Providers are deploying Edge instances to better serve their end-users and applications, A multitude of these applications require close inter-working with Telco 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 Service Provider instances at the Edge. | ||
Business use cases | Telco Edge deployments can provide APIs to support capabilities such as the following | Business use cases |
| |
Business Cost - Initial Build Cost Target Objective | The API platform (Gateway, SDK) will be deployed as cloud native containerized technology using Kubernetes. | |||
Business Cost – Target Operational Objective | The APIs will be exposed and published to external public cloud service providers and application developers in a secure, controllable, traceable, scalable, and measurable way. | |||
Security need | Northbound API platform (Gateway) will provide AAA, ACL, Policy enforcement functions. Southbound APIs that are used to call the core network functions of Telco will follow all the security requirements of 5G/4G core. | |||
Regulations | N/A | |||
Other restrictions | N/A | |||
Additional details | N/A |
Blueprint Family Details:
Case Attributes | Description | Informational |
Type | New | |
Blueprint Family - Proposed Name | Public Cloud Edge Interface (PCEI) | |
Use Case | Telco Edge deployments can provide APIs to support capabilities such as the following
| |
Blueprint proposed | Public Cloud Edge Interface (PCEI) | |
Initial POD Cost (capex) | 1 x86/Arm server, 4G/5G radio, switch | |
Scale & Type | x86/Arm servers + FPGA acceleration | |
Applications | Value-added capabilities of operators to open up, e.g.
Different applications will trigger different APIs. | |
Power Restrictions | N/A | |
Infrastructure orchestration | OS : Ubuntu 16.x, Centos7 VM: Airship, ONAP Containers: K8s | |
SDN | OVS-DPDK, SR-IOV | |
Workload Type | VMs, Containers | |
Additional Details | Need 4G/5G radio environment for POD |
Blueprint Details:
Case Attributes | Description | Informational | |||
Type | New | ||||
Blueprint Family | Public Cloud Edge Interface (PCEI) | ||||
Use Case | PCI) Blueprint FamilyUse Case | Telco Edge deployments can provide APIs to support capabilities such as the following
|
| serverice
| |
Blueprint proposed Name | Public Cloud Edge Interface (PCEI) | ||||
Initial POD Cost (capex) | 1 x86/Arm server, 4G/5G radio, switch | ||||
Scale & Type | x86/Arm servers + FPGA acceleration | ||||
Applications | Value-added capabilities of operators to open up, e.g.
Different applications will trigger different APIs. | ||||
Power Restrictions | N/A | ||||
Infrastructure orchestration | OS : Ubuntu 16.x, Centos7 VM: Airship, ONAP Containers: K8s | ||||
SDN | OVS-DPDK, SR-IOV | ||||
Workload Type | VMs, Containers | ||||
Additional Details | Need 4G/5G radio environment for POD |
As per the Akraino Community process and directed by TSC, a blueprint that has only one nominee for Project Technical Lead (PTL) will be the elected lead once at least one committer seconds the nomination after the close of nominations. If there are two or more, an election will take place.
Self Nomination began on 23 April 2020 and will continue until 29 April.
Oleg Berzin was the only person self-nominated. Confirmation o
Committer | Committer Company | Committer Contact Info | Committer Bio | Committer Picture | Self Nominate for PTL (Y/N) |
| China Mobile Tech USA | gusu@chinamobile.com | ||||
| Tencent | allenwchen@tencent.com | ||||
| Changming Bai | Alibaba | changming.bcm@alibaba-inc.com | |||
| Bruce Li | Alibaba | bruce.lxc@alibaba-inc.com | |||
| Equinix | oberzin@equinix.com | Y | |||
| Jian Li | China Mobile Tech USA | ||||
| AT&T | kk0563@att.com | ||||
| AT&T | dd5826@att.com | ||||
| Arm | tina.tsou@arm.com | ||||
| Gao Chen | China Unicom | cheng96@chinaunicom.cn | |||
| David Plunkett | AT&T | dp7642@att.com | |||
| Microsoft | cixing@microsoft.com | ||||
| Tide Wang | Phytium | wanghailong@phytium.com.cn | |||
| Arm | trevor.tao@arm.com | ||||
| Phytium | wangyanning@phytium.com.cn | ||||
| xinhuili | Salesforce | xinhui.li@salesforce.com |
Contributor | Contributor Company | Contributor Contact Info | Contributor Bio | Contributor Picture |
| Jeff Brower | ||||
| Jane Shen | Futurewei | jane.shen@futurewei.com |