Versions Compared

Key

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

Use Case Authors:

China Mobile, Vodafone, China Mobile, Huawei, ZTE, VMWare, Intel, WindRiver.

NOTE: More participants are welcome.

...

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. 

...


High Priority Extensions (enhancements) in Dublin release:

 Service Creation (Priority: Layer 3  > Layer2 > Layer1)

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 (Priority: Layer 3  > Layer2 > Layer1)

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.

...

Besides the change of service components like adding or deleting the sites, we also have the needs to add a VNF like vFW in the service or change the inputs parameters of an existing service.

Specific sub-use cases cases / functional requirements


Additional Extensions

...

...