...

• e.g., MEC APIs - Location info, Radio control info etc.
• e.g., Cloud APIs - IaaS/PaaS + Context Awareness (time, places, activity, weather etc.)  

Edge Infrastructure Profiles

( example based on Akraino Edge Stack..but, need to generalize)  

...

Edge Infrastructure Profile Summary

...

Summary 

• Distributed
  • 1000's of edge locations of varying capacity
  • Casablanca - Implementation
    • 10-100 edge locations (simple starting point)
• Peformance-awareness
  
  • GPU, FPGAs, SR-IOV etc.
  • Casablanca - Implementation
    • SR-IOV desired for Data Plane (5G CU-UP)
    • NIC offload desired for tunnel encap/decap e.g. 5G CU-UP GTP tunnel
• Resource Isolation through fine-grained QoS
  
  • Support both Latency-sensitive and General purpose applications
  • Support ONAP Management plane components in the same cloud with Workloads
  • Casablanca - Implementation
    • Min/Max resource reservation model desired
• Security
  • Workloads are often deployed in external (non-dc-type) locations and need HW security (TPM etc.) 
  • 3rd party applications which need additional HW security (VM, Containers in VM etc.) and SW security (Inter-component TLS etc.)
  • Casablanca - Implementation
    
    • Edge Clouds with private IP addresses, i.e. reachable via private connections 
    • For example, edge cloud in a public cloud provider reachable via AWS direct connect or Azure express route or Google partner interconnect 
• Capacity constraints
  • Very small footprint (few nodes per physical location), Medium footprint (10's of nodes per physical location), Large footprint (100's of nodes per physical location)
  • Casablanca - Deployment
    • Need number of cores per servers; Need storage capacity/pool
• Cloud Diversity

  • Private and Public Cloud Providers

  • Casablanca - Implementation
    • Note: ONAP currently supports private edge clouds based on VMware VIO, Wind River Titanium Cloud, Upstream OpenStack
    • Desire to have at least one Public Cloud Provider (Azure, AWS, GCE etc.) as an Edge Cloud Provider
      • ONAP central instantiates an Edge Cloud instance (blue cloud provider in gliffy) via a IaaS API to cloud provider
      • ONAP central instantiates one or more ONAP edge components as need, e.g. DCAE
      • ONAP central instantiates one or more NFs, e.g. 5G CU-UP/CP
• Configuration Diversity
  • 5G Factory Automation, 5G General Mobility Services etc. – User Plane components (DU, CU-UP, UPF etc.) 

Hierarchical (ONAP Central, Edge) Architecture

...

Key Challenges w/Centralized ONAP Architecture for Network Function Edge App/Infra Profiles

WAN network bandwidth & latency issues for the following key functions

• Conveying Application & Infrastructure metrics, faults in real-time from Edge Cloud to Centralized ONAP for closed-loop fault management for a single edge site with a single Cloud control plane
• Conveying Application & Infrastructure metrics, faults, alerts in real-time from Edge Cloud to Centralized ONAP for dynamic network function closed-loop fault management/placement optimization across multiple edge sites with a single Cloud control plane 
• Conveying Application & Infrastructure metrics, faults, alerts in real-time from Edge Cloud to Centralized ONAP for dynamic network function closed-loop fault management/placement optimization across multiple edge sites with multiple Cloud control planes 

Exemplary Network Function Placement/Service Assurance Policy for demonstrating the aforementioned challenges

• "5G CU-UP VNF location to be proximal to a specific physical DC based on 5G DU, bounded by a max wire latency from physical DC"

 Landscape for addressing aforementioned Challenges

• Cloud Providers
  • Public Clouds such as Azure, Amazon, GCP do not support dynamic network function closed-loop fault management/placement optimization across multiple edge sites with single/multiple Cloud control planes 
• Akraino Open Source
  • Defines Blueprints for Edge Cloud using OpenStacks (VMs) and K8S (Containers)
  • Plans to use ONAP for VNF/Service Orchestration for addressing aforementioned challenges

Hierarchical (ONAP Central, Edge) Architecture

Single Provider - Hierarchical Architecture

• Cloud Provider Business Unit: 
  • Provides hosting of Workloads, ie., IaaS/PaaS
    • SP installs and manages ONAP in separate 'Management Cloud' instances
    • SP installs and manages Network Services + 3rd Party Apps in separate 'Services/Apps Cloud' instances
• Cloud Provider Business Unit: 
  • Provides SaaS, eg., Analytics/Closed Loop as a Service, LCM of Apps, etc. 
  • • ONAP Edge may not be needed
• Cloud Provider Business Unit: 
  • Types of virtualized cloud resource tenant and their characteristics
    • Virtualized Network Workload Cloud Resource Tenant Category
    • Network Management Cloud Resource Tenant Category
    • Virtualized Application Workload Cloud Resource Tenant Category
    • Application Management Cloud Resource Tenant Category 
  • Physical Network Function and their characteristics
    • Part of Edge Cloud Orchestrator
• Immediate interest to ONAP for 5G Network Function use cases
  • Virtualized Network Workload Cloud Resource Tenant Category
    • Guaranteed
    • Burstable (with minimum guarantee)
    • Best Effort
  • Network Management Cloud Resource Tenant Category 
    
    • Burstable (with minimum guarantee) 

Single Provider - Edge Functional Decomposition 

Single Provider - Sequence Diagram

ONAP Activity Goal #1: ONAP requires IaaS/PaaS attributes (see ongoing work – Edge Cloud Infrastructure Enablement in ONAP, 5G Items for Casablanca) from Cloud providers for Infrastructure profiles that allow Distributed, Highly-secure, Config/Cloud-diverse, Capacity-constrained and Peformance/Isolation-aware

ONAP Activity Goal #2: Define hierarchical ONAP Central, Edge Architecture/functional interactions (API reference points) to support aforementioned Application/Infrastrcuture profile in Any "Cloud" (internal Business Unit or external Partner) at Any "Location" edge, regional or central.