Figure U.10 - Mapping IPDR base model to SID

The following Figure describes the mapping between the IPDR base model and the SID.<br/>The anchor for all record definitions in the IPDR base model is the IPDRType. In other words, all records definitions must be extensions of the IPDRType and instance of IPDRType (or one of its derived classes) is usage record. Usage class has exactly the same role in the SID. So IPDRType in the IPDR maps to the Usage class in the SID.<br/>In the SID there are three predefined Usage records (Resource Usage, Service Usage and Product Usage abstract records) but as information model it does not define any specific resource usage, service usage or product usage. The IPDR model does not define any layer between the IPDRType and each specific IPDR Service Specification.<br/>The IPDR Service Specifications that are defined and standardized up to the time this document is written, can all be considered as Service Usage.<br/>The instance of UsageSpecCharacteristic class in the SID presents a Usage's attribute. Exactly the same role holds by the elements referred by IPDRType definition or its inherited classes definitions. For example seqNum in the IPDRType or VoIP:callProgressState in the IPDR-VoIP-Type are attributes in the proper IPDR Service Specification.<br/>As a rule: each element referred by IPDRType definition or its inherited classes definitions in the IPDR model is mapped to specific instance UsageSpecCharacteristic in the SID.<br/>The UsageSpecCharacteristicValue in the SID is responsible for specifying constrains and default value for each specific UsageCharacteristicValue.<br/>In the IPDR model there is no clear separation between the attribute definition and its behavior definition (default values and constrains). An attribute in the IPDR model is first defined with its behavior definition values and then can be used by referring to it in specific IPDR Service Specification definition.<br/>As a rule: each data type and Element whenever it includes constrains and default values mapped logically to UsageSpecCharacteristicValue. <br/>Note: SID UsageSpecification and IPDR Service Specification cannot be mapped to each other. Instance of SID UsageSpecification and the IPDR Service Specification itself can be logically mapped to each other. <br/>An instance of SID UsageSpecification defines the usage Meta data. Realization of usage Meta data is the usage record itself.<br/>IPDR Service Specification itself is the usage metadata and instance of it is usage record.<br/>