Horizontal Synchronization Extensions for Optical Network Service Resizing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing control planes and management platforms in optical networks do not support efficient recovery from failures associated with service resizing operations, leading to service outages and blocked bandwidth during Media Channel (MC) or Optical channel Data Unit Flexible (ODUflex) resizing.

Innovation Solution

Implementing horizontal synchronization extensions between nodes in the network to detect mismatches and revert to a last known stable state during resizing operations, using horizontal synchronization messages to manage and correct the state and size of services such as MC or ODUflex, and enabling recovery actions to maintain service integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If service resizing operations are implemented in optical networks, then service flexibility and adaptability are improved, but system reliability deteriorates due to failures during resizing leading to service outages

Engineering Contradiction:
Improveservice resizing capabilityVSAvoidservice continuity during resizing
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent establishes a last known good state (LKGS) before resizing operations begin. This preliminary action creates a recovery anchor point that enables automatic restoration if resizing fails, thus maintaining reliability while allowing service flexibility.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements horizontal synchronization messages that continuously exchange state information between adjacent nodes. This feedback mechanism detects mismatches during resizing and triggers recovery actions, ensuring service continuity while maintaining resizing capability.

Inventive Principle:
Principle #23Feedback

2Stability of the object's composition

If horizontal synchronization messages are exchanged between nodes, then service state consistency is improved, but network communication overhead increases

Engineering Contradiction:
Improveservice state consistencyVSAvoidnetwork communication overhead
Core Design Contradiction:
Stability of the object's compositionVSLoss of energy

Solution Approach 1:

The patent segments the synchronization process into targeted horizontal synchronization messages exchanged only between adjacent nodes experiencing mismatches, rather than universal node-to-node communication. This reduces overall network overhead while maintaining state consistency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies synchronization selectively at local levels where mismatches occur between adjacent nodes, rather than implementing global synchronization across the entire network. This localized approach maintains consistency where needed while minimizing unnecessary communication overhead.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9985724B2Horizontal synchronization extensions for service resizing in optical networks
Publication Date: 2018.05.29 CIENA CORP
  • US9985724B2 patent drawing
  • US9985724B2 patent drawing
  • US9985724B2 patent drawing

AI summary

Systems and methods for horizontal synchronization are implemented by a first node with a second node adjacent to the first node in a network with a control plane. The horizontal synchronization manages and corrects for a state of a service which is resizable. The systems and methods include providing a first horizontal synchronization message to the second node with a first state comprising the state of the service at the node and a first size comprising a size of the service at the node; receiving a second horizontal synchronization message from the second node with a second state comprising the state of the service at the second node and a second size comprising a size of the service at the second node; detecting a mismatch of the service with the second node based on the second horizontal synchronization message; and performing a recovery action to correct the mismatch.