...

Furthermore, from an Operator perspective, it is important to introduce the capability to manage the performance of the CCVPN End-to-End service (especially when it spans across different Operators).

Current Situation

In Casablanca release, the CCVPN service is created by mean of separate multiple Service Orders via TMF 641, with one service orderItem for each of the services that make up the CCVPN connectivity Service. (Note -the UUI in Casablanca makes separate calls to SO, i.e. does decomposition but without Service Orders)

The complete removal of the CCVPN Service would involve the Portal/UUI making multiple separate Service Orders with one orderItem, each with a ‘delete’ action. This because there is no E2E Service Instance that corresponds to the full CCVPN Service. 

Proposed enhancements for Dublin release

Service Creation

In an ideal implementation, the Portal creates a single Service Order via TMF 641, with multiple service orderItem(s) for each of the services that make up the CCVPN Service.

• SDC should support Composite Services creation and SO should have the capability to decompose and (eventually) delegate the nested Services.
• A&AI should maintain composite End-to-End Service Instance for CCVPN.
• Parameters for all services can be passed as one composite orderItem to External API. 

...