Page History

Attributes

Description

Informational

Type

Industry Sector

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

Other restrictions

Additional details