Network Traffic Classification Using ClassID for Cloud Policy Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increased complexity and ephemeral nature of IP addresses in cloud networks make it difficult to reliably associate applications with data flows, leading to operational disruptions and inefficiencies in cloud network management.
Innovation Solution
A cloud network infrastructure that uses a classification identifier (ClassID) to reliably associate applications with data flows based on user-defined network policies, assigning ClassIDs based on static and dynamic attributes, and employing a decision tree or API to determine the appropriate policy, ensuring accurate routing and minimizing gateway configuration changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If IP addresses are used to identify applications in cloud networks, then applications can be assigned network addresses, but the ephemeral nature of IP addresses makes reliable association between applications and data flows difficult
Solution Approach 1:
The patent introduces a ClassID (classification identifier) as an intermediary between the IP address and the application. The ClassID is extracted from the data flow and used to identify the source application, decoupling the application identification from the ephemeral IP address. This mediator maintains reliable application association even when IP addresses change.
2Productivity
If gateways frequently update routing configurations to manage increased data traffic, then network management can adapt to changing conditions, but operational complexity and communication disruptions increase
Solution Approach 1:
The patent extracts the application identification function from the IP address and places it in the ClassID, which is then used for routing decisions. This separation allows gateways to use stable ClassIDs for routing configurations rather than relying on frequently changing IP addresses, reducing the need for frequent configuration updates and lowering operational complexity.
Solution Approach 2:
The patent changes the routing parameter from IP address to ClassID. Since ClassIDs are stable and directly associated with applications, routing configurations based on ClassIDs remain valid longer, reducing the frequency of configuration updates needed as data traffic increases.
3Adaptability or versatility
If more enterprises migrate software components to cloud networks, then cloud network resources are better utilized, but data traffic volume and gateway monitoring complexity increase
Solution Approach 1:
The ClassID serves as a mediator that simplifies gateway monitoring. Instead of monitoring and tracking numerous ephemeral IP addresses to identify applications, the gateway uses the stable ClassID to directly identify the source application, significantly reducing monitoring complexity even as data traffic volume increases due to more enterprises migrating to the cloud.
Data Source
AI summary
A network device, such as an ingress gateway for example, includes data analytic logic and message reconfiguration logic. The data analytic logic is configured to determine which of at least one network policy of a plurality of network policies is applicable to an incoming data flow and assigning a classification identifier in accordance with the at least one network policy. The classification identifier is configured to influence routing paths through at least one cloud network. The message reconfiguration logic is configured to encapsulate the classification identifier into content of the incoming data flow in order to generate a classified data flow for routing from a source to a destination through the at least one cloud network.