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 14 Next »

This is a proposal for a new Blueprint Species addition to the existing Integrated Cloud Native NFV (ICN) blueprint. The contributors to this blueprint are the same as the original ICN blueprint (with some changes), and we will seek more members to join the blueprint.

Case Attributes

Description

Informational

Type

New


Blueprint Family - Proposed   Name

Integrated Cloud Native NFV (ICN)


Use Case

End to end connectivity using Private LTE/5G over the CBRS band 


Blueprint proposed Name

Private LTE/5G ICN blueprint


Initial POD Cost (capex)

Same as ICN — 50K minimum


Scale & Type

Same as ICN — Minimum of 4 Xeon Servers + 1 Xeon server as genesis 


Applications

RAN+Core (initially LTE, eventually 5G), and reuse of existing ICN applications: ML/DL Analytics, EdgeXFoundry and 360 degree Video streaming


Power Restrictions

TBD


Orchestration

Same as ICN —

Infrastructure Orchestration

  • Bare Metal Provisioning :  ironic with Metal3 controlled by Cluster API
  • Kubernetes provisioning :  KuD.
  • Centralized controller:  With Cluster-API
  • Docker for containers and Virtlet for VMs

Service Orchestration : ONAP4K8s

MEC framework: OpenNESS

Site orchestrator :  Kubernetes upstream

Traffic Orchestration within a cluster: ISTIO

Traffic orchestration with external entities : ISTIO-ingress and ISTIO-egress with MCDeployment

Knative for function orchestration


SDN

Same as ICN — OVN, SRIOV, Flannel


Workload Type

Containers and functions


Additional Details

Our roadmap will be:

  • Private LTE
  • Private 5G Option 5 (i.e. LTE radio + 5GC)
  • Private 5G SA (i.e. 5G ratio + 5GC)

Use cases:

  • Manufacturing
  • Farming
  • Healthcare
  • V2X
  • Others


Contributors:

Committer

Committer Company

Committer Contact Info

Committer Bio / Contributions

Committer Picture

Self Nominate for PTL (Y/N)

Prem Sankar GopannanLumina Networks



Yes
Ravi ChunduruVerizonEnd user requirements guidance

Manoj MouryaOrange
End user requirements and contributions

Srinivasa AddepalliIntel

With MICN as the basis for this,  my colleagues and I at Intel will help in following:

  • MICN integration
  • SD-EWAN CNF
  • OVN-for-K8s-NFV network controller
  • ONAP4K8s.

Will work with other team members in adding new controllers in ONAP4K8s to auto program the UPF & adjacent gateway micro-service to steer the traffic to locally offloaded applications.



Amar Kapadia

Aarna NetworksONAP4K8s

Sriram RupanaguntaAarna Networks
ONAP4K8s

Ramki KrishnanAdvisor, VMware


Pradnesh DangeRebacaTesting

Sivasothy SHANMUGALINGAMIndependent sothy shanUPF and SMF


Mansoor KhanWavelabs.aiMansoor KhanSystems Integration

Parthiban NWavelabs.aiParthiban N

Orchestration

CI/CD, DevOps



Mohamed El GamalNetNumberMohamed El Gamal


Vikram BalimidiCloudlyte - Tata CommunicationsVikram BalimidiEnd-user requirements and guidance

Vineet AnshumanCloudlyte - Tata Communicationsvineet anshumanEnd-user requirements and guidance

Files:


  • No labels