Detection of Fiber Faults in Passive Optical Networks

Abstract

Wider deployment of fiber in the last mile is driven by increased customer needs for broadband communication services. This deployment requires solutions that reduce operational expenditures for the operator. A costefficient fully reliable and accurate monitoring solution supporting fault detection, identification, and localization in different fiber access architectures will be essential. In this article, we present a fast, automatic, and precise monitoring method applicable to both power-splitter-and wavelength-router-based passive optical networks through the combined techniques of optical time domain reflectometry and optical transceiver monitoring. The description of the architecture, components, and process flow is followed by tests on setups with live data transmission.

HUBBLE: an optical link management system for dense wavelength divisionmultiplexing networks

“…A signaling-free fault management with monitoring resource allocation that is based on near shortest m-trails can be used to find the failure of neighbouring nodes is studied in [22]. An approach for access links with OTDR testing is described in [23].…”

Single-Ended In-Service Hybrid Monitoring of Fiber-Extended Copper Lines

“…An economical comparative analysis of monitoring of a PON network by applying remote/centralized tools versus traditional handheld equipment can be found in [6]. In the context of single-ended network monitoring, we also tackle a striking factor: the capability of coexistence between data and monitoring signals for in-service monitoring.…”

Embedded Otdr Monitoring Systems for Next Generation Optical Access Networks

“…As discussed by Esmail & Fathallah [41] and Urban et al [42], an efficient monitoring system needs to fulfill the following requirements: 1) be able to quickly detect and localize faults in a cost-efficient way, 2) provide high resolution in distance measurement, 3) be centralized in the Central Office (CO), 4) monitor the network automatically and remotely, 5) avoid/eliminate impact on data transmission, and 6) be scalable towards different network architectures.…”