Use Case Authors:
Vodafone, China Mobile
NOTE: More participants are welcome.
Description
CCVPN Use Case extension for Dublin, includes Service Creation and Modification using the concepts of Unified and Composite Services.
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 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.
Service OAM
The Service OAMs (Fault & Performance Management) are used to guarantee the SLA objectives. Initial focus for CCVPN Dublin Release should be on modeling SOAM-PM for Composite Services in the Service Catalog.
Specific sub-use cases
Priorities for Dublin
(Initial assessment)
FEATURE | IMPACTED PROJECTS | IMPACT LEVEL | PRIORITY | NOTES |
|---|---|---|---|---|
Information Model | Modelling | HIGH | Extend CCVPN IM for Composite Services | |
Service Order & Activation/ Configuration | External API (SO) (SDC) (A&AI) | HIGH | API extension Composite Services | |
Direct Service Modification* (existing service) | External API (SDC) (SO) | HIGH | Change ‘service’ API E.g., Inter-Carrier change bandwidth /elastic bandwidth for E2E Service | |
Service Catalog Notification* | External API (SDC) | MEDIUM | Notify to other SP that the Service has been created in the Service Catalogue | |
PM modeling in Service Catalog | Modelling (DCAE) (SDC) | MEDIUM | Model SOAM in Service Catalog for Composite Services |
*feature alreadyproposed for Dublin release