...
In an ideal implementation, the Portal shall create 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.
Service Change
A CCVPN End-to-End Service Change (e.g., bandwidth change), should be either triggered by the portal (as TMF 641 single service orderItem with ACTION ‘change’) or by a policy implemented to guarantee that SLS is met.
Similarly to the Service Creation, this change (or modification) should be handled by SO, which decomposes the Service Change and sends it, via External API, to the other Operator(s) in the form of PATCH service.
SO should offer Service Modification API and associated workflows to interact with SDN-C, A&AI and External API to make the required service adjustments.
Finally, SDC must be able to model the LCM Operation/Interfaces for modifications allowed on the CCVPN Service (e.g., AdjustBandwidth) so that the modification capability can be exposed through the Service Catalog.
...