Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Participants:

AT&T, Orange, Fujitsu (member list  below)

Description: 

Provide end to end multi-operator L1 services orchestrated by ONAP across multiple optical transport domains


Goals:

  • Incorporate & harmonize with MEF L1 Subscriber and Operator service definitions
  • E2E optical service work flow definitions & on-boarding of network resources
  • Align, harmonize, reconcile common information/data models in ONAP to enable Optical Transport services design & instantiation 
  • Optical Transport domain management through standard models / APIs. Eg: OpenROADM, Transport API

BUSINESS DRIVER

This section describes Business Drivers needs.

Executive Summary  - This use case is to automate the service design and activation resulting from an optical (L0/L1) service request that requires "off-net" resources to complete, requiring coordination between two or more service providers.

Business Impact - Automation of the design and activation of services spanning service provider networks will speed time to revenue.

Business Markets - This use case is applicable to any service provider offering global enterprise services or services that otherwise extend beyond their own network resources. It may also apply to service providers with independent operational units that effectively operate as separate service providers. 

Funding/Financial Impacts - While this automation may result in some CAPEX savings due to improved management of interconnect points, it will primarily reduce OPEX by automating some of the manual steps required for service provider interconnections. It will also allow service providers to respond more quickly to service orders requiring off-net resources, thus reducing time to revenue. A goal of this use case is to ensure support for SLAs and adherence to service constraints that potentially allow for the development of new premium service offerings.

Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service provider's "normal" ONAP deployment and its attendant organizational resources


Team Accomplishments:

First draft Frankfurt accomplishments

April 8th MDONS demo conducted by THIRILOSHINI KRISHNAKUMAR  and Xin Miao (Unlicensed) (star)(big grin)(star)

  • Scroll down to April 8th meeting notes for demo link

Frankfurt Integration testing status link


Initial use-case proposal (Frankfurt)

ONAP-optical-usecase-proposal.pptx


Proposed MDONS enhancements (Guilin):   (green star)

Service-Assurance-in-MDONS-042020-v0.1.pdf

MDONS-guilin-v2.pptx

MDONS-guilin-v1.pptx

Link to MDONS extensions in Guilin: MDONS Extension in R7

Architecture Subcommittee presentation: mdons-guilin-archcom.pptx

Event drive reconfiguration discussion: Event-driven-reconfiguration.pptx


Business requirements:

L1 interconnect business reqts agreed 5-16.pptxCDS based Workflows updates:


EUAG Proposal

EUAG L1 Interconnect PoC final - 05.pptx

EUAG L1 Interconnect PoC draft - 04..pptx

EUAG L1 Interconnect PoC draft.pptx


Archiecture and Workflow Proposals:

ONAP-Project-Proposal-rv12OrangeContribV3.pptx

ONAP-optical-usecase-proposal-with-cds-4/29

ONAP-optical-usecase-proposal-with-cds-4/29


Modeling

MDON-Service-Use-Case-2019.pptx

Optical Modeling_L1 Subscriber and Operator Services_v2.pptx


Other items of interest

ONAP_Transport_Slicing_briefing.pptx




Functional Requirements:

ONAP ComponentsComments
CDS (future release)Started Discussion with CDS group to identify the required changes to support this blue print.  (Future Release)
SDC Use existing feature support w/o change code in Frankfurt
SO

Will need some changes in SO to accomplish the decomposition of end to end optical service. More details need to be ironed out.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2432

SDN-C

Have done some prototyping in Dublin for adding new DGs to extract topology from external domain controllers and map them to A&AI schema. Will need additional work to integrate this with proposed CDS workflow in Future release.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDNC-928

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCCSDK-1828

A&AI

Have done some prototyping in Dublin to ingest topology from external controllers and show them in A&AI. Will need more work to act on notifications from controllers and keep the topology in sync

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2623

OOF (for future release)

OOF to provide the intermediate endpoints/inter-connection selection that will support to form the end to end L1 service

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOPTFRA-622

Policy ( future release/Phase 2)Need to understand how we can use the policy to store inter SP agreements which can later be translated by OOF to determine the partner SP and also the end points at the partner side. (Future release)
EXT-APINeed to have alignment on how we can use the MEF interlude API for inter SP interactions. EXT-API and SO communications also has to be flushed out.
ModelingNeed to define the extensions to the currently agreed upon service model so that we can use it to represent an end to end Layer1(L1) Optical service. This L1 Optical service can span across multiple service providers which are controlled by one or more ONAP instances.  Every SP can in turn have multiple domains that are controlled by external domain controllers.
UUI

Modify the component for the user to be able to initial L1 service from user interface and verify APIs.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyUSECASEUI-348


Interested Parties

Viewtracker report