Hi All,
There have been long debates in our team about Resource Activation and how it's being orchestrated.
First, let me provide some background about our implementation. We implemented a PSR structure with:
- CFS (with a concept of Service Configuration by including the concept of version). In other words, a CFS may have multiple versions which represent the different configurations it took throughout its lifecycle (i.e. when the customer calls to change the DownloadSpeed or add a voice Feature)
- RFS (also with a concept of version), which carries the configuration of the Service for the given Technology. (For example, CFS with DownloadSpeed 25 and UploadSpeed 10 will derive a SpeedProfile xxx111 on gpon)
- Resource (no concept of version). In our implementation, resources are static. Resource Characteristics are details like Port #...
In Resource Operating phase, where we need to configure a resource for a given Service, we need to hit the Network Element with:
- Resource Details (i.e. port#)
- Configuration details (i.e Speed Profile xxx111)
Question: In your opinion, is it considered ResourceActivation or ServiceActivation?
- Some could argue that since, at the end, a Resource is being touched, we could use API 702. However, how would you pass the configuration details on 702 (ResourceActivation)? (in our current resource catalog, we do not carry service-related details)
- Others could argue that we are trying to activate the RFS (which is the glue between the CFS and Resource), therefore, use 640 (ServiceActivation)
At the end, our challenge is that if we decide to use the Resource Domain APIs (ResourceOrder, ResourceActivation), with our current model, we fail to understand how to pass the Configuration on the payload since, for example, a ResourceOrder only contains Resource/ResourceCharacteristics
- Unless we evolve our model to add Configuration properties in our Resource Catalog (i.e. Adding SpeedProfile to the DSLPort Resource), we don't see other ways.
- Then, it would bring another challenge: Introducing the concept of resource configuration (versioning) at the resource level...
Any thoughts/recommendations?
------------------------------
Stephane AH-KO
CGI Info Systems Management Consulting Inc.
------------------------------