Abstract: Systems and methods implemented by a network element in a G.8032 ring include steps of operating an Operations, Administration, and Maintenance (OAM) session with an adjacent network element; and detecting an optical bypass in the G.8032 ring based on the OAM session. The steps can include flushing a forwarding database of the network element based on the optical bypass. The steps can include detecting prior to the optical bypass, that a neighboring node includes a ring block; and subsequent to the optical bypass, installing a new channel block. The optical bypass enables faster protection switching and the present disclosure incorporates an optical bypass in G.8032.

Abstract: Systems and methods implemented by a network element in a G.8032 ring include steps of operating an Operations, Administration, and Maintenance (OAM) session with an adjacent network element; and detecting an optical bypass in the G.8032 ring based on the OAM session. The steps can include flushing a forwarding database of the network element based on the optical bypass. The steps can include detecting prior to the optical bypass, that a neighboring node includes a ring block; and subsequent to the optical bypass, installing a new channel block. The optical bypass enables faster protection switching and the present disclosure incorporates an optical bypass in G.8032.

Abstract: Systems and methods include receiving Interior Gateway Protocol (IGP) messages from one or more network elements in a network; extracting timing information from any of the IGP messages where the timing information includes timing reference for a given network element for any of frequency, phase, and time; and storing the timing information. The steps can further include one of displaying a Graphical User Interface of the network including an operational timing trail for any of frequency, phase, and time; and displaying the timing information for the one or more network elements via a Command Line Interface (CLI).

Abstract: Systems and methods for detecting a rogue network device at a physical layer include monitoring physical layer characteristics of a wired link at both a first network device and a second network device; determining whether there are detectable variances in the physical layer characteristics; and detecting a rogue network device inserted on the link based on the detectable variances.

Abstract: A network element includes circuitry configured to receive information related to clock distribution from Precision Time Protocol (PTP) messages from an upstream network element, determine a delta between a network clock from the information and a Primary Reference Time Clock (PRTC), and transmit the delta in PTP messages to downstream network elements. The circuitry can be further configured to receive a configuration of a clock class of a clock at the network element, and transmit the clock class in the PTP messages with the delta. The clock class can be one of A, B, C, and D from G.8273.2 or G.8273.4.

Abstract: A network element includes circuitry configured to receive information related to clock distribution from Precision Time Protocol (PTP) messages from an upstream network element, determine a delta between a network clock from the information and a Primary Reference Time Clock (PRTC), and transmit the delta in PTP messages to downstream network elements. The circuitry can be further configured to receive a configuration of a clock class of a clock at the network element, and transmit the clock class in the PTP messages with the delta. The clock class can be one of A, B, C, and D from G.8273.2 or G.8273.4.

Abstract: Systems and methods for detecting a rogue network device at a physical layer include obtaining physical layer characteristics of a link between a first network device and a second network device; analyzing the physical layer characteristics of the link; and detecting the rogue network device based on the analyzed physical layer characteristics, wherein the rogue network device was inserted in the link and causes detectable variances in the physical layer characteristics. The physical layer characteristics can include one of noise introduced in clock frequency and jitter.

Abstract: Systems and methods of storing phase history, and enhancing and restoring phase accuracy for a embedded Global Navigation Satellite System (GNSS) receiver include storing a phase history of the GNSS receiver output; determining an expected value of phase of the GNSS receiver output based on the phase history; and, responsive to a degradation of the GNSS receiver output, adjusting the GNSS receiver output utilizing the expected value of phase. The systems and method can further include, responsive to degradation being a loss of the GNSS receiver output, utilizing a holdover output from a physical frequency reference and with a phase adjusted based on the expected value of phase, and, responsive to the variation, utilizing the phase history to re-generate the GNSS receiver output for performance enhancement.

Abstract: A node can include a clock; and mapper circuitry configured to determine a timestamp from the clock, and transmit the timestamp to a second node in a Radio over Ethernet (RoE) frame with the timestamp in a control subtype and with an operational code (opcode) that designates the timestamp is in the frame. The node can also include a demapper circuit configured to receive a second timestamp from the second node in a second RoE frame, and provide the second timestamp to a Differential Clock Recovery (DCR) circuit for adjustment of the clock to a second clock at the second node.

Abstract: Systems and methods of storing phase history, and enhancing and restoring phase accuracy for a embedded Global Navigation Satellite System (GNSS) receiver include storing a phase history of the GNSS receiver output; determining an expected value of phase of the GNSS receiver output based on the phase history; and, responsive to a degradation of the GNSS receiver output, adjusting the GNSS receiver output utilizing the expected value of phase. The systems and method can further include, responsive to degradation being a loss of the GNSS receiver output, utilizing a holdover output from a physical frequency reference and with a phase adjusted based on the expected value of phase, and, responsive to the variation, utilizing the phase history to re-generate the GNSS receiver output for performance enhancement.

Abstract: Systems and methods of compensating for the delay asymmetry of coherent optical modems in a packet optical network include measuring fill levels of one or more queues each including an elastic First-In-First-Out (FIFO) circuit used in a transport mapping scheme, wherein the transport mapping scheme is one or more of client mapping to Optical Transport Unit (OTU) and OTU mapping to Flexible OTN (FlexO); and performing adjustments in a clock based in part on the measured fill levels, wherein the adjustments are configured to reduce a Time Error (TE) in the packet network based on delay asymmetry between two nodes.

Abstract: Systems and methods of compensating for the delay asymmetry of coherent optical modems in a packet optical network include measuring fill levels of one or more queues each including an elastic First-In-First-Out (FIFO) circuit used in a transport mapping scheme, wherein the transport mapping scheme is one or more of client mapping to Optical Transport Unit (OTU) and OTU mapping to Flexible OTN (FlexO); and performing adjustments in a clock based in part on the measured fill levels, wherein the adjustments are configured to reduce a Time Error (TE) in the packet network based on delay asymmetry between two nodes.

Abstract: Clock synchronization in a network includes receiving, by a slave network device from a master network device via at least a intervening network device, a timing packet comprising a transmission timestamp and a residence time. The transmission timestamp is based on a master clock of the master network device. The residence time corresponds to a delay of the timing packet traversing the intervening device. Clock synchronization in a network further includes generating, by the slave network device in response to receiving the timing packet, a receiving timestamp based on a slave clock of the slave network device, and generating, based at least on the transmission timestamp, the residence time, and the receiving timestamp, a time difference between the master clock and the slave clock. Clock synchronization in a network further includes synchronizing, based at least on the time difference, the master clock and the slave clock.

Abstract: Systems and methods for detecting a rogue network device at a physical layer include obtaining physical layer characteristics of a link between a first network device and a second network device; analyzing the physical layer characteristics of the link; and detecting the rogue network device based on the analyzed physical layer characteristics, wherein the rogue network device was inserted in the link and causes detectable variances in the physical layer characteristics. The physical layer characteristics can include one of noise introduced in clock frequency and jitter.

Abstract: Clock synchronization in a network includes receiving, by a slave network device from a master network device via at least a intervening network device, a timing packet comprising a transmission timestamp and a residence time. The transmission timestamp is based on a master clock of the master network device. The residence time corresponds to a delay of the timing packet traversing the intervening device. Clock synchronization in a network further includes generating, by the slave network device in response to receiving the timing packet, a receiving timestamp based on a slave clock of the slave network device, and generating, based at least on the transmission timestamp, the residence time, and the receiving timestamp, a time difference between the master clock and the slave clock. Clock synchronization in a network further includes synchronizing, based at least on the time difference, the master clock and the slave clock.

Abstract: A system for managing holdover. The system may include a local oscillator device. The system may include a phase locked loop (PLL) device coupled to the local oscillator device and a reference clock source. The PLL device may obtain a reference clock signal from the reference clock source to produce an extracted clock signal. The system may include a drift monitoring device coupled to the local oscillator device and the PLL device. The drift monitoring device may determine an amount of oscillator drift within the local oscillator device using the extracted clock signal and an oscillator signal from the local oscillator device. The system may include a drift compensation device coupled to the drift monitoring device and the PLL device. The drift compensation device may transmit a drift compensation signal to the PLL device based on the amount of oscillator drift.

Abstract: A system for managing holdover. The system may include a local oscillator device. The system may include a phase locked loop (PLL) device coupled to the local oscillator device and a reference clock source. The PLL device may obtain a reference clock signal from the reference clock source to produce an extracted clock signal. The system may include a drift monitoring device coupled to the local oscillator device and the PLL device. The drift monitoring device may determine an amount of oscillator drift within the local oscillator device using the extracted clock signal and an oscillator signal from the local oscillator device. The system may include a drift compensation device coupled to the drift monitoring device and the PLL device. The drift compensation device may transmit a drift compensation signal to the PLL device based on the amount of oscillator drift.

Abstract: A method of routing traffic through a packet network having a mesh physical topology. At least two types of network primitive are defined, each type of network primitive providing a respective model of traffic forwarding through at least two neighbor nodes of the network. A network model encompassing at least a portion of the network is constructed using a set of two or more interconnected network primitives. The network model has nodes and links corresponding to respective nodes and lines of the network. Respective forwarding information is computed for each node of the network model. For each node of the network model, the respective computed forwarding information is installed in a forwarding database of the corresponding node of the network, such that traffic is forwarded by each node of the network in accordance with the respective computed forwarding information.

Abstract: A method of routing traffic through a packet network having a mesh physical topology. At least two types of network primitive are defined, each type of network primitive providing a respective model of traffic forwarding through at least two neighbour nodes of the network. A network model encompassing at least a portion of the network is constructed using a set of two or more interconnected network primitives. The network model has nodes and links corresponding to respective nodes and lines of the network. Respective forwarding information is computed for each node of the network model. For each node of the network model, the respective computed forwarding information is installed in a forwarding database of the corresponding node of the network, such that traffic is forwarded by each node of the network in accordance with the respective computed forwarding information.

Abstract: A method of routing traffic through a packet network having a mesh physical topography. At least two types of network primitive are defined, each type of network primitive providing a respective model of traffic forwarding through at least two neighbor nodes of the network. A network model encompassing at least a portion of the network is constructed using a set of two or more interconnected network primitives. The network model has nodes and links corresponding to respective nodes and lines of the network. Respective forwarding information is computed for each node of the network model. For each node of the network model, the respective computed forwarding information is installed in a forwarding database of the corresponding node of the network, such that traffic is forwarded by each node of the network in accordance with the respective computed forwarding information.