1+1 Protection Switching Crossover Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional 1+1 protection switching systems fail to maintain communication integrity in the presence of crossover connections, as they assume direct port-to-port connections and cannot properly switch between active and backup links when crossover couplings occur.
Innovation Solution
The system automatically detects crossover connections by analyzing pair identifier fields in embedded operations channel messages and configures a programmable logic unit to reverse timeslots and alarms, enabling successful data transfer and coordinated protection switching even in crossover scenarios.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional 1+1 protection switching systems assume direct port-to-port connections, then the system operation is simple, but the system fails to maintain communication integrity when crossover connections occur
Solution Approach 1:
The system performs preliminary detection of crossover connections by analyzing pair identifier fields in embedded operations channel messages before protection switching operations. This preliminary action identifies potential issues in advance, allowing the system to configure the programmable logic unit appropriately to maintain communication integrity during failure scenarios.
Solution Approach 2:
The system uses feedback from embedded operations channel messages containing pair identifier fields to detect crossover connections. This feedback mechanism provides continuous information about the actual connection topology, enabling the system to adapt its protection switching behavior and maintain reliability despite unexpected crossover configurations.
2Reliability
If the system detects and configures for crossover connections, then protection switching reliability is improved, but the detection and configuration process becomes more complex
Solution Approach 1:
The system uses its own embedded operations channel messages, which already contain pair identifier fields for other purposes, to detect crossover connections. This self-service approach leverages existing infrastructure without requiring separate detection protocols or additional message types, reducing the difficulty of detection while improving reliability.
3Measurement precision
If the system uses embedded operations channel messages with pair identifier fields, then crossover detection accuracy is improved, but the message processing complexity increases
Solution Approach 1:
The pair identifier fields in embedded operations channel messages serve multiple functions: they identify communication pairs for their original purpose and simultaneously enable crossover connection detection. This multi-functionality allows accurate crossover detection without requiring separate detection messages or processing systems, maintaining simplicity while improving measurement precision.
Data Source
AI summary
A communication system that comprises at least two links to carry signals, a first communication unit and a second communication unit. The first communication unit comprises at least two ports, each port configured to transmit and receive signals; and a logic unit configured to process the signals transmitted and received by each of the at least two ports in the first communication unit. The second communication unit comprises at least two ports, each port configured to transmit and receive signals and coupled to a respective one of the at least two ports in the first communication unit via a respective one of the at least two links; a programmable logic unit configured to process the signals transmitted and received by each of the at least two ports in the second communication unit; and a processor. The processor is configured to detect a crossover connection between one of the at least two ports in the second communication unit and the respective one of the at least two ports in the first communication unit based on an analysis of a pair identifier field in a message received at the second communication unit, wherein the pair identifier field is separate from the address field of the received message.


