Automated Telecommunication Service Provisioning via Data-Driven Templates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The integration of new devices and services into telecommunication networks is time-consuming and expensive, requiring custom code development in complex OSS/BSS systems, and lacks automation, leading to inefficient configuration processes.
Innovation Solution
A data-driven, agentless approach for automating the provisioning of telecommunication services using service templates, recipes, and subrecipes, which allow for customizable service instance creation and management without the need for manual coding or product-specific adapters, supporting various protocols like REST, SOAP, and NETCONF.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If custom code development is performed in OSS/BSS systems to integrate new devices and services, then integration capability is improved, but integration time and cost increase significantly
Solution Approach 1:
The patent uses service templates as reusable copies of configuration patterns. Instead of developing custom code for each new device or service integration, the system captures integration logic once in a template format and reuses it repeatedly. The template stores configuration data, workflow steps, and integration logic that can be instantiated multiple times for different devices and services, eliminating the need for repeated custom code development.
Solution Approach 2:
The system transforms rigid custom code into flexible parameter-driven templates. By converting integration logic into parameterized service templates with configurable fields, the system allows adaptation to different devices and services through parameter changes rather than code modifications. This enables the same template framework to handle various integration scenarios by simply changing the input parameters and configuration data.
2Adaptability or versatility
If custom code development is performed in OSS/BSS systems to integrate new devices and services, then integration capability is improved, but development cost increases
Solution Approach 1:
Service templates serve as reusable copies that eliminate repeated development work. Once an integration scenario is captured in a template, it can be copied and applied to multiple devices and services without additional development cost. The template captures the entire integration logic, configuration requirements, and workflow steps, which can be instantiated indefinitely without requiring new custom code development for each case.
Solution Approach 2:
The template system creates universal integration solutions that work across multiple device types and service scenarios. A single service template can be applied to different devices and services by changing parameters, making the integration capability universal rather than requiring device-specific custom code. This multi-functionality reduces development cost by consolidating integration logic into reusable templates that serve multiple purposes.
3Device complexity
If sequential GUI screens are used for configuration in OSS/BSS systems, then system complexity is maintained, but automation level decreases
Solution Approach 1:
The patent replaces manual mechanical interaction with automated data-driven processes. Instead of requiring operators to manually navigate sequential GUI screens, the system uses service templates that automatically execute configuration steps based on input parameters. The template engine automates the entire provisioning workflow, substituting manual mechanical operations with automated computational processes that read template definitions and execute configuration steps without human intervention.
Solution Approach 2:
The service template system enables self-service automation where the configuration process executes itself based on template definitions. Once a template is created and parameters are provided, the system automatically performs all configuration steps, workflow executions, and device provisioning without requiring manual guidance through GUI screens. The automation engine reads the template, determines the required actions, and executes them autonomously, making the system self-sufficient for configuration tasks.
Data Source
AI summary
Systems and methods for building service templates that allow for an agentless, data-driven and stateful automation of a provisioning of services to mobile network customers. Data associated with a request to create a target schema object class for a device and protocol are received. Based on the device and protocol information, a set of data fields associated with CRUD semantics is retrieved from either a database or from user provided data. A decorated target object class is created based on the requested target schema object class. A subrecipe is created including the decorated target object class, and one or more other decorated target object classes. A recipe is processed for transmission to an execution engine to form a service instance, the service instance being customizable by an operator for a specific network device such that the service instance data fields that are not pre-filled can be customized by the operator.


