Figure SO.31 TIP Service Management - Service Definition and Service Template

The abstract class ServiceSpecification has been extended to support two new concepts introduced in the TIP Service Management interfaces:<br/><b>ServiceDefinition</b><br/>        • used during service design time to define the characteristics of a service, their associated data types, and default values. These characteristics, known as ServiceSpecCharacteristics (SSC), may be globally set, which implies they can be defined in a service template, or otherwise only passed in real-time over an activation interface<br/><br/><b>ServiceTemplate </b><br/>        • defines specific ServiceSpecCharacteristicsValues (SSCVs) for the SSCs that were defined in the Service Definition as being globally settable. The Service Template is checked against its associated Service Definition by verifying the presence of the SSCs and the validity of the corresponding assigned SSCVs. Only Service Templates that contain SSCs/SSCVs that are in conformance with their specification in the Service Definition are considered valid.<br/><br/>Both Service Activation interfaces make use of the Service Definition and Service Template concepts in the activation of CustomerFacingServices and ResourceFacingServices.<br/>The ServiceDefinition and ServiceTemplate further define the Service Specification through their respective associations, with the versions being identified through the ServiceSpecVersion. The association class ServiceSpecRelationship allows for Service Specifications to contain other Service Specifications, which thus holds true for Service Definitions and Service Templates.  For example, there may be a type of Service Definition for Ethernet Services, and contained within that type are E-LINE, E-LAN, and E-TREE Service Definitions. <br/>The ServiceAccessPoint (SAP) represents a unique (logical and/or physical) resource where the Service can be accessed. The Sap Specification defines a set of attributes and associated values that may be applied to one or more SAPs. The relationship between the Service Specification and the Sap Specification illustrates that for every Service Specification, there may be associated multiple Sap Specifications. For example, given an Ethernet E-LINE Service Specification, there may be multiple Sap Specifications that correspond to various Bandwidth Profile Specifications that can be applied to the Sap – one for GOLD, one for SILVER, and one for BRONZE. Likewise, there may be a single Sap Specification , or in this case Bandwidth Profile Specification, that is used for multiple Ethernet Service Specifications – E-LINE and E-LAN. A Bandwidth Profile Specification defines Service Level Agreement guarantees and may be applied per UNI, per EVC, or per CoS Id. They contain frame delivery per Service Level Objectives (Committed Information Rate, Committed Burst Size), and amount of excess frame delivery allowed (Excess Information Rate, Excess Burst Size).<br/>A ServiceCatalog represents a grouping of Service Specifications and SSCs.  For example, a catalog could group all internet related Service Specifications. The following figure illustrates the Service Definition, and Service Template concepts, and the relationship between the Service Catalog and the Service Specification.<br/><br/>