Generic Framework for Network Element Management System Provisioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing network element management system (EMS) requires significant customized development to support new services, leading to potential bugs, increased development time and cost, and complexity in user experience due to numerous interfaces between EMS clients and servers.
Innovation Solution
A generic framework for EMS servers processes communications from EMS clients using a generic interface, service modules, and a database manager, allowing new services to be added without modifying the framework, using a generic record to store service data and selecting appropriate service modules for provisioning.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If customized development is performed for each new service in the EMS server, then the service can be supported, but development time and cost increase significantly
Solution Approach 1:
The patent implements a universal service module framework where a single generic record structure and common processing logic can handle multiple different services. The EMS server uses a standardized interface that accommodates various services (VoIP, data services, etc.) without requiring separate customized development for each service type, thus reducing development time while maintaining service diversity.
Solution Approach 2:
The patent segments the service handling into modular components: a generic record structure that separates service-specific data from common processing logic. This segmentation allows the system to reuse the same framework across different services, eliminating the need for full customized development for each new service and significantly reducing development time.
2Adaptability or versatility
If customized development is performed for each new service in the EMS server, then the service can be supported, but the possibility of introducing bugs increases
Solution Approach 1:
By implementing a universal service module framework with standardized interfaces and common processing logic, the patent reduces the variability introduced by customized development. The generic record structure and reusable components have been thoroughly tested and validated, thereby maintaining high reliability while supporting diverse services.
Solution Approach 2:
The patent uses template-based service module definitions that can be copied and instantiated for different services. Rather than creating custom code from scratch for each service, the system replicates proven, bug-free template structures, significantly reducing the introduction of new bugs while maintaining service-specific functionality.
3Adaptability or versatility
If customized interfaces are created for each provisioned service, then the service can be supported, but the complexity of user experience increases
Solution Approach 1:
The patent implements a universal interface framework where a single standardized interface handles multiple services. The generic record structure provides a consistent data model that works across different services, presenting a uniform user experience while supporting service diversity underneath. This eliminates the need for multiple customized interfaces and reduces user-facing complexity.
4Adaptability or versatility
If customized development is performed for each new service, then the service can be supported, but the amount of interfaces to maintain and support increases
Solution Approach 1:
The patent creates a universal service module framework with standardized interfaces and common processing logic that can be reused across multiple services. This consolidation reduces the total number of interfaces that need to be maintained and supported, as the same generic record structure and framework handle diverse services, significantly lowering maintenance effort while preserving service adaptability.
Data Source
AI summary
A method and apparatus for deploying EMS provisioning services is provided. A communication to administer a particular service on a network element is transmitted from an EMS client to an EMS server. The communication contains service data that describes a particular service to be administered on the network element. The EMS server constructs an instance of a generic record that stores the service data. The EMS server selects a service module to process the instance based on which service is associated with the service data stored in the instance. The instance is processed to produce result data that describes the result of processing the service data at the network element. The EMS server stores the result data in a persistent store. This generic framework enables communications between EMS clients and the EMS server involving different services to be processed similarly. New services are added without modification to the generic framework.