SO R6 Frankfurt Architecture Review

Brief Project Overview (brief as it should be known)

The SO provides orchestration at a very high level, with an end-to-end view of the infrastructure, network, and applications.

Functional features intended to be delivered in Service Orchestrator project in Frankfurt release and the companies involved:

• Integrate the AAF and upgrade the APIs to Https - ATT

• ETSI alignment improvements - Ericcson, Huawei, Samsung, Verizon

  • SOL005 adaptation

  • SOL003 adaptation

  • SOL002 adaptation

  • SOL004 - Using the ETSI catalog manager for the SDC models.

• PNF orchestration Enhancements - Ericcson, Huawei, Nokia

  • PNF sotware upgrade  

  • PNF PNP enhancement  

• CCVPN Enhancement

  • MDONS support -  Fujitsu

  • Eline support - Bell, Huawei, CMCC

• 5G Slicing - ATT, Amdocs, CMCC, Huawei, Wipro

• CDS integration enhancement - ATT, Bell, Tech Mahindra, Orange

• (SO Multi Cloud plugin improvements - Intel)

• HPA -  Intel (Testing effort)

• Java 11 Upgrade - HCL, Orange (Egypt)

New component capabilities for Frankfurt, i.e. the functional enhancements.

The following table lists the Frankfurt functional requirements which impact SO.

These requirements require enhancements to existing SO functionality. 

New or modified interfaces

SO provide the following new APIs:

• Extension to retrieve PNF workflow: SO-2540

• Support custom PNF workflow, like software upgrade (shall be generic enough to support  execution of PNF-level workflow: SO-2071

• Support the LCM for the CSMF and NSMF operations  SO-2543 , SO-2544

• APIs to SOL002 adapter SO-2427

• APIs on the Package Mgmt for the SOL003 Adapter - SO-2156

• Enhancement to the existing SOL005 interfaces SO-2437

If they are modified, are the backwards compatible?

SO APIs would be made https based but we also tend to provide the functionality to disable it on need basis.

Note:

• Current focus area : External -> SO interactions. ER interfaces with SO as the server.

• Hardening of the interfaces from API handler and the SO monitoring.

Interface naming (point to an example)

• All APIs have Swagger documentation, which is referenced in readthedocs

Reference to the interfaces.

• All APIs have Swagger documentation, which is referenced in readthedocs

Involved use cases, architectural capabilities or functional requirements.

SO is used in the following use cases / Functional requirements:

• vFW

• vDNS

• vCPE

• VoLTE

• BBS

• CCVPN

• 5G

• HPA

• Change Management

Listing of new or impacted models used by the project (for information only).

New components to be introduced in SO in F release:

• SOL002 Adapter - Extension to the ETSI alignment work. This will be a temporary stage and discussion are through to move it to generic network controller as and when available. 

• NSSMF Adapter - As part of the 5G slice management requirement, this adapter would interact with the external NSSMF (CN, TN or AN) of the 5G network.

Majorly impacted modules of SO in F release:

• API Handler - All new APIs defined would be developed in this module.

• BPMN Infra - Enhancements to the existing workflows for the functional requirements mentioned in the above sections.

• SDNC adapter - CDS interaction and enhancements to the controller APIs

Lateral changes would be brought in due to the following requirements:

• Java 11 upgrade

• AAF integration

What are the system limits?