Versions Compared

Old Version 2

changes.mady.by.user Davide Cherubini

Saved on

compared with

New Version 3

changes.mady.by.user Davide Cherubini

Saved on

Key

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

•Service Instance relationships would need to be maintained in A&AI to relate to the one EP-LAN.

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 

Image Added

  1. This is the current implementation for CCVPN P2P services in Casablanca
  2. 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

  3. To remove the EP-LAN Service fully would involve the Portal making multiple separate Service Orders

    The VNF must be orchestrated via SO

    with one orderItem, each with an action of ‘delete’ ( i.e. there is no E2E Service Instance that corresponds to the full EP-LAN Service)

  4. Service Instance relationships would need to be maintained in A&AI to relate to the one EP-LAN