Figure U.11 - Mapping between the IPDR - SP model and the SID

The following Figure describes the mapping between the IPDR/SP model and the SID.<br/>The Template Block class in the IPDR/SP defines the usage Meta data, it has identification (templateId) and it associates with IPDR Service Specification (schemaName, typeName). The Meta data itself is defined by list of field descriptors (FieldDescriptor) that defines the name and the type of the field.<br/>An instance of Template Block is the usage meta-data and the SID UsageSpecification has exactly the same role.  It also appears that the FieldDescriptor has exactly the same role as the UsageSpecCharacteristic.  The Template Block in the IPDR/SP is mapped to the SID UsageSpecification and The FieldDescriptor in the IPDR/SP is mapped to the UsageSpecCharacteristic in the SID.  The Data entity in the IPDR/SP model is mainly consists of identification (seqNum), association with its template (templateId - instance of TemplateBlock has an id) and the Data entity.  The data itself is just an opaque array. It can be decoded using the instance of TemplateBlock it associates with (its meta-data).  The objective of the Data class is to hold the usage data. The Usage entity has the same role and Data attributes n the IPDR/SP which is shown mapped to the SID Usage entity.<br/>