Figure PF.03 - Performance Specification

The definition of performance specification and performance entities is based on four other key types of entities<br/>        • Performance Indicator (KPI) entities<br/>        • Performance Category entities<br/>        • Performance Network Address (IP and Point Code) entities<br/>        • Performance Characteristic (dynamic attribute) entities<br/><br/>Each of these types of entities is detailed in separate sections of this document.  Following Figure shows the core entities for each type and their relationship with PerformanceSpecification and Performance.  These types of entities also employ the EntitySpecification/Entity pattern.  For example, the PeformanceIndicatorSpecification entity defines a KPI with a name of pealPacketJitter, its description, how it is derived, and so forth; the PerformanceIndicator for peakPacketJitter contains the value for the KPI and the time at which it was calculated and so forth.<br/>Note that all the performance specification related entities have an n-n association with PerformanceSpecification.  This enables instances of these entities, such as PerformanceIndicatorSpecification, to be shared by many PerformanceSpecifications.  For example, peakPacketDelay can be a KPI for a PerformanceSpecification that measures the performance of a GGSN to a SGSN and a SGSN and a BSS.  From a PerformanceIndicator perspective, it does not make sense that all the instances of these entities be shared by instances of Performance.  Entities that classify or further define the Performance, such as PeformanceCategory and PerformanceNetworkAddress, are shared.  For example, a Codec with a value of GSM can classify many instances of Performance.  Entities, such as PerformanceIndicator and PerformanceCharacteristicValue, define a single instance of Performance and are not shared.  For example, the 1000 sent packets defines a single instance of the Performance between the north Dallas BSS and the Dallas SGSN.<br/>