Global Realization Number Tracking for Logical Network Entities

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed virtual networks, it is difficult to determine whether logical entities have been realized in the network infrastructure at a particular point in time, and identifying the source of realization issues is challenging due to the ephemeral nature of the realized state, which changes as the system environment evolves.

Innovation Solution

A method and tool that utilize a global realization number (GRN) to track the realization status of logical entities by querying the control plane, associating the GRN with both desired and realized states, and providing incremental updates to determine the status of logical entities across different time instances, allowing users to query the realization status of multiple entities simultaneously.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the system continuously updates the realized state of logical entities as the environment changes, then the system remains adaptive and current, but it becomes difficult to determine the realization status at a particular point in time

Engineering Contradiction:
Improvesystem adaptabilityVSAvoidrealization status information
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The system captures and stores the realized state of logical entities at specific points in time before environmental changes occur. By proactively saving state snapshots associated with global realization numbers, the system preserves historical realization status information that would otherwise be lost due to continuous state changes from VM migrations, hypervisor failures, and other environmental dynamics.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates copies of the logical entity realization states at different time instances and stores them with associated global realization numbers. These state copies allow users to query and compare realization status at any historical point without affecting the current adaptive state, thus resolving the contradiction between maintaining current adaptability and preserving historical information.

Inventive Principle:
Principle #26Copying

2Measurement precision

If the system tracks the realization status of multiple logical entities individually, then the realization status of each entity can be determined, but the complexity of querying and managing multiple entities increases

Engineering Contradiction:
Improverealization status trackingVSAvoidquery management complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system merges the tracking of multiple logical entities by associating them with a single global realization number that represents a specific point in time. When users query the realization status, they can do so for multiple entities simultaneously at a particular GRN, and the system returns a consolidated view of all entity states at that moment, significantly reducing query management complexity while maintaining precise tracking.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The global realization number serves as a universal identifier that applies to all logical entities in the system. A single query mechanism using the GRN can determine the realization status of any number of logical entities, making the system universally applicable for multi-entity tracking without requiring separate management procedures for each entity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Measurement precision

If the system stores detailed runtime data for all logical entities to track realization status, then accurate determination of realization status is possible, but the storage requirements and data processing overhead increase

Engineering Contradiction:
Improverealization status determinationVSAvoiddata storage volume
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The system extracts only the essential realization status information from the complete runtime data at each global realization number. Instead of storing all detailed runtime data continuously, the system captures snapshots of the critical realization state at specific GRN points, significantly reducing storage requirements while maintaining sufficient information for accurate realization status determination.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system implements partial tracking by storing realization state information at discrete global realization number intervals rather than continuously tracking all changes. This partial action approach captures sufficient information to determine realization status at any GRN point without the excessive overhead of storing and processing every individual state change, achieving a balance between precision and resource consumption.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10241820B2Determining the realization status of logical entities in logical networks
Publication Date: 2019.03.26 VMWARE INC
  • US10241820B2 patent drawing
  • US10241820B2 patent drawing
  • US10241820B2 patent drawing

AI summary

Some embodiments provide a method for identifying a realization status of one or more logical entities of a logical network. In some embodiments the method is implemented by a controller that controls network data communications in a logical network. The method receives a request for realization status of a set of logical entities at a particular point of time that is associated with a particular value of a realization number. The method determines whether configuration data up to the particular point of time for each logical entity in the set has been processed and distributed to a set of local controllers that operates on a set of host machines. The method returns a realization reply that includes a successful realization message when the configuration data up to the particular point in time for each logical entity in the set has been processed and distributed to the set of local controllers.