Versions Compared

Old Version 2

changes.mady.by.user Davide Cherubini

Saved on

compared with

New Version Current

changes.mady.by.user Davide Cherubini

Saved on

Key

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

The CCVPN E-LAN Service Use Case will impact each of the Projects listed on this page.  

Options for CCVPN E-LAN Services 

Service Creation

OPTION 1 

  • This is the current implementation for CCVPN P2P services in Casablanca
  • Service Decomposition happens in the Portal/UUI
    1. Multiple Service Orders (ideally via TMF 641 if from external BSS portal), with 1 service orderItem for each of the services that make up EP-LAN Service
    2. In Casablanca, the UUI made separate calls to SO, i.e., did decomposition but without Service Orders
    • The VNF must be orchestrated via SO

    Depending on the chosen implementation Option (listed here), impact will be different. Listed impacts refer to Option 2 for Service Creation and Option A for Service Modification

    AAI

    1. Support Composite Service Instances (multi-operator)

    DCAE

    •  Performance management - Stretched GOAL - POSTPONED TO R5

    OOF 

    • TBC

    SDN-C 

    • TBC

    Modeling 

    • Need to support Composite Services

    SDC

    1. Support Composite Services creation
    2. Must be able to model LCM operations/Interfaces and expose the modification capabilities through the Service Catalog

    External API

    1. Implement TMF 641 for external BSS Portal (parameters passed as one composite/single orerItem)
    2. implement East-West cross-operator  External API-External API ("patch service" for service modification)

    SO

    1. Implement ability to "decompose" the End-to-End service (in collaboration with SDC). The same applies for the Service Change. 
    2. Implement Service Modification API and associated workflows to interact with other projects (SDN-C, A&AI & ExtAPI)