Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Project Technical Lead: Lokanath Padhu

Project Committers detail:

Initial Committers for a project will be specified at project creation. Committers have the right to commit code to the source code management system for that project.

A Contributor may be promoted to a Committer by the project’s Committers after demonstrating a history of contributions to that project.

Candidates for the project’s Project Technical Leader will be derived from the Committers of the Project.

Only Committers for a project are eligible to vote for a project’s Project Technical Lead.


Please see Akraino Technical Community Document section 3.1.3 for more detailed information.

Committer

Committer

Company

Committer

Contact Info

 Committer BioCommitter Picture 

Self Nominate for PTL (Y/N)

Lokanath PadhuNokialokanath.padhu@nokia.com

Y
Pekka KuureNokiapekka.kuure@nokia.com  


Use case


Use Case Attributes

Description

Informational

Type

New submission

 

Industry Sector

Telco and carrier networks, enterprise networks, private networks, multi-access networks, edge cloud and verticals

 

Business driver

One of the key drivers of 5G Systems are ultra low latency and high reliability communications enabled by edge clouds. Services can be hosted close to the end users and new type pf services can be enabled by exposing contextual information to applications. In this framework the services can be enhanced with Machine Learning. Applications hosted in distributed cloud i.e. edge and central cloud, can consume services offered by service producers. Service consumers can discover the services that are available in that location via API framework. Similarly. the service producers can advertise their offerings via the same API framework. In addition to service discovery, the API framework allows authentication and authorization and can also provide communications transport to the service consumers and producers.

 

Business use cases

For Example:

      
  1. Customer Edge deployable at Customer premises such as home, enterprises, offices to support Edge services such as SD-WAN
    2.   
  2. Customer Edge deployable at Public buildings such as Stadiums, Smart cities, etc., to support edge applications for example - Video Analytics, AI/ML based detection, etc.,
    3.   
  3. Edge Cloud deployable at Cell tower to support RAN related workload
    4.   
  4. Edge Cloud deployable at Central offices ranging from one rack to multiple racks

 

Business Cost - Initial Build

For Example:

      
  1. Edge Cloud deployable at Central offices with single rack should be less than 150K $

 

Business Cost - Operational

For Example:

      
  1. Edge Cloud deployable at Central offices with single rack should be less than 100K $ as operating cost per year.
    2.   
  2. In-place upgrade of the Edge cloud should be supported without impacting the availability of the edge applications

 

Operational need

For Example:

Edge Solution should have role based access controls, Single Pane of Glass control, administrative and User Based GUIs to manage all network cloud family based blueprints.

The automation should also support zero touch provisioning and management tools to keep operational cost lower

 

Security need

For Example:

The solution should have granular access control and should support periodic scanning

 

Regulations

For Example:

The Edge cloud solution should meet all the industry regulations of   data privacy, telco standards (NEBS), etc.,

 

Other restrictions

Consider the power restrictions of specific location in the design (example - Customer premise)

 

Additional details

The Edge Cloud Solution should be deployable across the globe and should be able to support more than 10,000 locations

 




  • No labels