TL;DR
This paper introduces a novel workflow-based architecture for automating the complex process of provisioning BGP/MPLS VPN services. By defining a flexible workflow control scheme and applicable workflow patterns, it aims to streamline service delivery, reduce operational costs, and improve customer satisfaction in the competitive telecommunications market.
What Problem Does This Paper Address?
The telecommunications industry faces intense competition, driving the need for rapid and efficient service delivery to retain and attract customers. Traditionally, provisioning complex services like BGP/MPLS VPNs involves intricate, often manual, processes that are prone to errors, slow, and costly. This leads to customer dissatisfaction and hinders an operator's ability to quickly introduce new offerings. The paper addresses the challenge of automating and standardizing this service delivery process, bridging the gap between business process management and the technical intricacies of network service provisioning.
Methods
The paper proposes a workflow-based service delivery architecture for telecommunications services. This architecture is built upon two key components:
- Workflow Patterns: The authors identify and define five basic workflow patterns (Sequence, Split, Merge, Cycle, Branch) that are commonly applicable to telecommunications service delivery. These patterns provide a standardized way to model and represent the flow of tasks and information.
- Workflow Control Scheme: This scheme consists of two modules:
- Workflow Control Module (WCM): This module handles service order distribution and workflow administration/monitoring. It's designed using a GUI interface (Workflow Administration and Monitoring Tool - WAMT) and stores workflow definitions in an XML-based Workflow Information Base (WIB).
- Work Process (WP): These modules represent the actual application processes and perform specific activities like order reception, validation, service configuration, and connectivity testing.
The paper also details a specific workflow for BGP/MPLS VPN service provisioning, breaking it down into distinct Work Processes (WP-OR, WP-OV, WP-ALP, WP-SC, WP-NC, WP-CT, WP-OC) and illustrating their interactions.
Datasets
Not discussed in the paper.
Key Insights and Ideas
- Workflow as a Unifying Concept: The paper highlights how workflow management, when applied effectively, can act as a unifying layer to integrate disparate telecommunications components (BSS/OSS, network elements) and automate complex business processes.
- Standardized Workflow Patterns: Defining a set of basic workflow patterns provides a common language and framework for designing and implementing service delivery workflows, making them more understandable and manageable.
- XML for Workflow Definition: Using XML to store workflow definitions in the Workflow Information Base (WIB) offers flexibility and interoperability, allowing for dynamic modification and easier integration.
- Modular Work Processes: Breaking down the service delivery into distinct Work Processes (WPs) allows for specialization and distributed execution, enhancing scalability and efficiency.
- Focus on Service Configuration: While acknowledging network configuration, the paper strategically focuses on the Service Configuration Activities (SCA) as the core of the service delivery process for VPNs, recognizing its direct impact on customer-facing services.
Key Results
The paper proposes a conceptual framework and architecture for workflow-based BGP/MPLS VPN service provisioning. It describes a detailed workflow scenario for this service. The key results are the proposed architecture and the workflow control scheme, which are designed to:
- Differentiate carriers by providing exceptional customer service.
- Increase service visibility for customers.
- Enable faster telecommunications service delivery.
- Expand market reach and increase order processing volumes.
- Increase productivity and reduce personnel involvement in service delivery.
- Achieve lower operating expenses.
Limitations and Future Work
- Conceptual Focus: The paper primarily presents a conceptual design and a case study scenario. It does not include empirical results from a deployed system or quantitative performance metrics.
- Future Work: The authors suggest several avenues for future research:
- Enabling customers to manage their own VPNs via web-based self-care portals.
- Implementing better tracking and feedback mechanisms for real-time SLA conditions and rebates.
- Facilitating the rapid deployment of additional products and services through the proposed architecture.
Summary updated