Service configuration processes include activities necessary to allocate, implement and configure the necessary resources to meet customer requirements including resource provisioning. For example, with an E-Line service, resource provisioning would be performed at each UNI-Network (UNI-N) demarcation point, where the customer ingress and egress traffic engineering and conditioning processes are occurring, in accordance with the service level specification (SLS). The resources, or equipment, that provides the customer’s service must be provisioned to enable the end-to-end service delivery with the required service attributes. Examples of configuration attributes defined at the UNI-N demarcation include:
IEEE 802.3 PHY Medium, speed and mode
UNI interfaces and EVC segment
UNI-to-EVC associations
bandwidth profiles
It is important to note that both service configuration as well as Service OAM (SOAM) configuration is performed at this stage of the workflow to enable service assurance mechanisms the moment the service is deployed to the customer. Examples of SOAM configuration for Ethernet services include:
Configuration of maintenance domains (MDs), maintenance associations (MAs), MEGs, MEPs and MIPs
Configuration of fault management functions including Continuity Check, Alarm Indication Signal and Fault Alarm Generation
Configuration of performance monitoring functions including Frame Loss and Frame Delay measurements and event generation for threshold crossing alerts (TCAs)