Network Service Topology Identification Using VLAN Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Network management systems face challenges in distinguishing between multiple independent services sharing the same VLAN ID, leading to confusion and incorrect identification of operational issues, as network devices lack a global view and may inadvertently shut down separate services during troubleshooting.
Innovation Solution
A method is implemented to identify and separate different services using a network management system that starts at an arbitrary network device with a shared traffic identifier, branching out to connect nodes until all elements are determined, allowing for the creation of service containers with unique IDs for efficient diagnosis and management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If network devices use shared VLAN IDs for multiple services, then resource utilization is improved, but service identification accuracy deteriorates
Solution Approach 1:
The patent segments the network service identification by creating service containers that group network devices into distinct services based on topology analysis. Each service container receives a unique service ID, allowing multiple services to share VLAN IDs while maintaining accurate identification through topological differentiation rather than relying solely on VLAN IDs.
Solution Approach 2:
The patent introduces service containers as an intermediary layer between the network devices and the network management system. These containers act as mediators that aggregate topology information and provide accurate service identification, resolving the conflict between shared VLAN IDs and service differentiation.
2Ease of operation
If network management systems rely on VLAN IDs for service identification, then configuration simplicity is improved, but fault isolation capability deteriorates
Solution Approach 1:
The patent segments service identification into two layers: the configuration layer continues to use simple VLAN IDs, while the management layer uses topology-based service containers. This segmentation allows configuration simplicity to be maintained while fault isolation capability is improved through accurate service boundary definition.
Solution Approach 2:
Service containers serve as an intermediary that translates simple VLAN ID configurations into accurate service boundaries for fault management. The containers aggregate topology information to provide precise service identification without requiring complex configuration changes.
3Measurement precision
If service containers are created through topology analysis, then service identification accuracy is improved, but computational complexity increases
Solution Approach 1:
The patent performs preliminary topology analysis to pre-establish service containers before fault detection or service management operations. By pre-computing the service boundaries and creating containers in advance, the system avoids repeated computational complexity during actual service management while maintaining high identification accuracy.
Data Source
AI summary
Disclosed is a method of identifying service topologies in a network, including determining a group of network devices having a same traffic identifier and indicating each network device of the group as not processed, selecting a first network device that is indicated as not processed in the group, indicating the selected first network device as partially processed, and associating the first network device with a service container identifier, identifying, for each port of the selected first network device, at least another network device in the group indicated as not processed connected to the first network device or a termination point, wherein the identified another network device is identified as partially processed and associated with the service container identifier, repeating step (c) for each identified another network device until only termination points are reached, wherein the identified another network device becomes the first network device in step (c), and when any network devices in the group of network devices remain not processed repeating the steps (b)-(d).