Modular Host Core Model for Carrier Network Device Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In carrier networks, full-customization mode for device configuration is labor-intensive and resource-heavy, making it difficult to reuse configurations across projects and requiring significant manpower and material resources for maintenance and upgrades.
Innovation Solution
A configuration method that involves obtaining a service requirement, determining a host core model and components, generating a packet based on these elements, and configuring devices independently, allowing for pre-creation of host core models and components to reduce complexity and resource requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If full-customization mode is used for device configuration, then device configuration can be completed based on actual project requirements, but configuration complexity and resource consumption increase significantly
Solution Approach 1:
The patent segments the configuration process into independent components (host core model, network element model, component mapping) that can be reused across projects. The configuration is divided into modular units that can be independently selected and combined, reducing overall complexity while maintaining adaptability to different project requirements.
Solution Approach 2:
The patent creates universal host core models and component libraries that can serve multiple projects and scenarios. The same host core model can be applied to different network elements and service types, making the configuration system multi-functional and reducing the need for project-specific customization.
2Adaptability or versatility
If full-customization mode is used for device configuration, then configuration can be tailored to specific project needs, but reuse across projects becomes difficult
Solution Approach 1:
The patent performs preliminary actions by pre-defining host core models, network element models, and component mappings before actual configuration. These pre-prepared templates can be directly applied to new projects, eliminating the need to create configurations from scratch and significantly improving productivity while maintaining project-specific customization capabilities.
Solution Approach 2:
The patent enables copying of configuration templates and models across projects. The host core model and component mappings can be copied and adapted to different network elements and service types, allowing rapid deployment of configurations while maintaining the ability to customize for specific project requirements.
3Ease of operation
If full-customization mode is used for device configuration, then each device can be configured according to actual situation, but manpower and material resources required increase
Solution Approach 1:
The patent implements self-service configuration where the system automatically generates configuration packets by selecting appropriate host core models and components based on project requirements. This automated approach reduces the need for manual configuration work and decreases the quantity of human resources required while maintaining configuration flexibility and adaptability.
4Adaptability or versatility
If full-customization mode is used for device configuration, then configuration can be completed for each project, but maintenance and upgrade become more difficult
Solution Approach 1:
The patent segments the configuration into modular components (host core model, network element model, component mapping) that can be independently maintained and upgraded. This segmentation allows specific components to be updated without affecting the entire configuration system, making maintenance and upgrades easier while preserving project-specific customization capabilities.
Data Source
AI summary
A method includes obtaining a first service requirement related to a first device; determining, based on the first service requirement, a first host core model and at least one component hooked to the first host core model; generating a first packet based on the host core model and the at least one component; and configuring the first device based on the first packet. Because a configuration apparatus can run independently of a device that is in a service requirement, configuration can be completed on the device based on the service requirement when a service of the device is not broken. Difficulty in configuration can be effectively reduced by hooking the component to the host core model.