Skip to end of metadata
Go to start of metadata

The purpose of 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 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 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 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. 

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 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 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 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 with no ready made answers. Needless to say, business relationships of all Edge players is 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 coming years, Edge is not only a location play, but also a network capability play. In order to promote 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.


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

  • UPF shunting capability -- routing the traffic to desired applications and network functions
  • Local breakout – video traffic offiload
  • Wireless air-port status
  • Location service -- location of a specific UE, or identification of UEs within a geographical area
  • QoS acceleration – provide low latency, high throughput for OTT applications
  • Slicing scheduling management -- offering dedicated resources specifically tailored for application needs
  • Authentication – provided as service enablement (e.g., two-factor authentication) used by most OTT service providers 
  • Security – provided as service enablement (e.g., firewall service insertion)


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

  • UPF shunting capability -- routing the traffic to desired applications and network functions
  • Local breakout – video traffic offiload
  • Wireless air-port status
  • Location service -- location of a specific UE, or identification of UEs within a geographical area
  • QoS acceleration – provide low latency, high throughput for OTT applications
  • Slicing scheduling management -- offering dedicated resources specifically tailored for application needs
  • Authentication – provided as service enablement (e.g., two-factor authentication) used by most OTT service providers 
  • Security – provided as service enablement (e.g., firewall service insertion)


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.

  • Portability
  • Location capabilities
  • Wireless network information capabilities

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

Telco Edge deployments can provide APIs to support capabilities such as the following

  • UPF shunting capability -- routing the traffic to desired applications and network functions
  • Local breakout – video traffic offload
  • Wireless air-port status
  • Location service -- location of a specific UE, or identification of UEs within a geographical area
  • QoS acceleration – provide low latency, high throughput for OTT applications
  • Slicing scheduling management -- offering dedicated resources specifically tailored for application needs
  • Authentication – provided as service enablement (e.g., two-factor authentication) used by most OTT service providers 
  • Security – provided as service enablement (e.g., firewall service insertion)


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.

  • Portability
  • Location capabilities
  • Wireless network information capabilities

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 which 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 USAgusu@chinamobile.com


Tencentallenwchen@tencent.com


Changming BaiAlibabachangming.bcm@alibaba-inc.com


Bruce LiAlibababruce.lxc@alibaba-inc.com


Equinixoberzin@equinix.com

Y
Jian LiChina Mobile Tech USA

lijianyj@chinamobile.com




AT&Tkk0563@att.com


AT&Tdd5826@att.com


Armtina.tsou@arm.com


Gao Chen China Unicomcheng96@chinaunicom.cn







David PlunkettAT&Tdp7642@att.com



Contributor

Contributor

Company

 Contributor Contact Info

Contributor Bio

Contributor Picture





Jeff Brower



Jane ShenFutureweijane.shen@futurewei.com





  • No labels