Network Element Configuring Entity Identifier for SDN Conflict Prevention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In software-defined networking, configuring network elements to prevent conflicts between mutually uncoordinated applications and controllers is challenging, as existing methods do not effectively manage distinct applications and controllers, leading to potential misconfiguration and service disruptions.
Innovation Solution
A network element and controller system that utilize a configuring entity-specific identifier to uniquely address different applications and controllers, ensuring that the correct configuration system components are used for each application or controller, thereby preventing conflicts and ensuring proper operation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple applications and controllers are used to program a network element, then the functionality and versatility of the network element is improved, but the risk of configuration conflicts and system reliability deteriorates
Solution Approach 1:
The patent segments the configuration space by introducing application-specific identifiers that divide the configuration system into distinct, non-conflicting segments. Each application (e.g., VoIP, VoD, online gaming) receives a unique identifier, allowing multiple applications to coexist in the same network element without interference. This segmentation resolves the contradiction by enabling multi-functionality while preventing configuration conflicts through spatial separation in the configuration namespace.
Solution Approach 2:
The patent introduces an intermediary mechanism in the form of a configuration system that mediates between multiple applications and controllers. This intermediary uses application-specific identifiers to manage and coordinate configuration data from different sources, ensuring that conflicts are prevented through controlled access and proper identification. The mediator resolves the contradiction by allowing multiple entities to interact with the network element simultaneously while maintaining system reliability through coordinated management.
2Device complexity
If traditional configuration methods are used without application-specific identifiers, then the device complexity is reduced, but the measurement precision of configuration management and ability to detect conflicts deteriorates
Solution Approach 1:
The patent applies a metaphorical 'color change' principle by introducing distinctive application-specific identifiers that act as unique markers or labels for different applications. Each application is assigned a specific identifier (such as a unique string or code) that distinguishes it from others, enabling precise identification and tracking of configuration data sources. This resolves the contradiction by maintaining relative simplicity while dramatically improving identification accuracy and conflict detection capability through these distinctive markers.
3Ease of operation
If configuration data is sent to each network element individually, then the ease of operation is improved, but the productivity and time required for network-wide configuration deteriorates
Solution Approach 1:
The patent applies universality by creating a standardized configuration framework that uses common application-specific identifiers across the entire network. This universal identification system allows configuration data to be managed consistently whether deployed to a single network element or across the entire network, enabling both individual customization and network-wide efficiency. The standardized approach resolves the contradiction by maintaining operational flexibility at the individual element level while enabling scalable, efficient network-wide configuration through consistent identification and management practices.
Data Source
AI summary
A network element of a software-defined network includes a data transfer interface (211) for receiving and transmitting data and a processing system (212) for constructing, in accordance with configuration data received from a controller system of the software-defined network, a configuration system for managing data to be forwarded. The processing system is adapted to configure a first portion of the configuration system to associate, with data received at the network element, a configuring entity-specific identifier (CEID) that identifies a configuring entity, for example an application, related to the received data. The configuring entity-specific identifier constitutes at least a part of metadata associated with the received data. Appropriate other portions of the configuration system are configured to use this metadata when determining actions to be carried out in conjunction with the received data. The configuring entity-specific identifier prevents conflicts between different configuring entities, for example applications, in the configuration system.