Hello,
While integrating an IMS platform in a TMF based solution following question popped up:
Certain Characteristics of a Service or Resource can be changed by a customer without passing via OSS. e.g. the CallForwarding in Telephony (*21*[phone number]#).
It should also be possible to change these Characteristics via the ServiceActivation or ResourceActivation API.
So we do not want to store data about these kind of Characteristics in the ServiceInventory or ResourceInventory since this may be out of sync with what is present in the network.
What is the recommended way to indicate that a Characteristic should not be persisted ?
- keep some reference data to indicate this.
- extend the definition of 'Characteristic'
- something else ?
Kind Regards
Jan
------------------------------
Jan Segers
Proximus SA
------------------------------