Overview

Edge clouds are located at close proximity to end users. Typical deployment locations are within the access networks or at the boundary of access networks. In some deployments, they can be within the customer premises (e.g., home; enterprise; factory floor; vehicles including trains, planes, private cars). The core thrusts of edge clouds for applications are low latency, high bandwidth, and trusted computing and storage. Various edge cloud architectures have already emerged from different communities and potentially can be plugged into the ONAP architecture for service orchestration. The group analyzes the orchestration requirements of services over various edge clouds and how these requirements impact ONAP components in terms of data collection, processing, policy management, resource management, control loop models, security, as well as application & network function deployment and control.

Scope

This group will address the needs of an edge automation environment to satisfy following 

• Providing contextual information to application services after gathering information from 5G network functions.
• Traffic  steering to the right edge applications (e.g  Programming UE classifier of UPF)
• Scaling needs 
• Securing confidential information/keys/secrets and detecting any software tampering.
• Optimal placing of edge applications. For example placing edge applications in close proximity of end users.
• Supporting various application types (VMs and containers)
• Performance determinism and high throughput edge 
• Deploying IoT specific infrastructure software in edges.
  
  

This group will study the needs of edges,  identify ONAP role,  identify gaps in ONAP to satisfy above needs and propose solutions to address the gaps.

Few examples:  on scaling -   OOM based scaling may not be good enough and  there may be a need to  offload some ONAP functionality to regional level as the target number of edge clouds could be in tens of thousands.   Also, to reduce amount of data to central ONAP services for analytics,  there is a need for offloading DCAE functions to regional level, which could involve  identifying real time data sources, collecting and analyzing the data and disseminating output data to central ONAP function.  Controlling fabric (L2/L3 switches in edge-clouds and WAN links) is another function that may require offloading some ONAP SDNC functions to regional sites. 

ONAPARC-63 - Getting issue details... STATUS

Problem Statement:

Initial Draft: Cagatay/Vimal/Kaniz drafted the following, waiting your input.

Edge Scoping-r3.docx

To Do:

• Problem Statement - Clarify Where/What is Edge...and, focus of this effort
  • See Figure 3 in ATT-Edge_Compute_White_Paper FINAL2.pdf
  • Edge = vCPE at customer Premises
  • Edge = Cell Tower
  •  Edge = Small Central Office (eg., CU for vRAN)
• Identify Target Communities
• Requirements for ONAP R2+
  • Target April 30th for Use Case sub committee update
  • Target May 1st for Architecture sub committee update 

Call Schedule:

• Time: 8:00am PT - 9:30am PT

• Day: Every Monday
• Zoom: zoom.us/j/7626591316 (will move to ONAP zoom shortly)