What is the pF_DS (Far-End Defect Second) Performance-Monitoring Parameter for the ODUk Layer?

This blog post breifly defines the pF_DS (Far-End Defect Second) Performance Monitoring paramteter that the OTN PTE will compute and generate.

This blog post aims to briefly define and describe the pF_DS (Far-End Defect Second) Performance Monitoring parameter that the OTN PTE (or ODUk_TT_Sk Atomic Function) will compute and generate.

The OTN PTE (or ODUk_TT_Sk function) will include information on pF_DS without each Performance Monitoring report that it sends to System Management.

Performance Monitoring Reports

NOTES:

  1. The OTN STE (OTUk_TT_Sk Atomic Function) also monitors and generates information on the pF_DS (Far-End Defect Second) parameter at the OTUk Layer. Please see the pF_DS at OTUk Layer Post for more details on this parameter.
  2. Throughout this post, I will use the terms: OTN PTE and ODUk_TT_Sk Function interchangeably. In the context of this blog post, these two terms mean the same thing.

Introduction

At the ODUk Layer, the OTN (Sink) PTE is the entity that is responsible for detecting and reporting Far-End Defect Second events.

As the OTN PTE receives and monitors its incoming ODUk signal, it will check for many things. It will continuously check for the incoming ODUk signal for Service-Affecting Defect (e.g., dAIS, dOCI, dLCK, dTIM, etc.) as well as bit (or symbol) errors (e.g., PM-BIP-8 errors and PM-BEI errors).

Another thing that the OTN PTE will do (as it continuously monitors its incoming ODUk signal) is to divide each second of (monitoring) time into the following two categories:

  • Far-End Available (Working) Seconds, and
  • Far-End Defect Seconds

Anytime the OTN PTE detects and categorizes a given one-second period as being a Far-End Defect Second, it will increment the pF_DS parameter and report that information to System Management.

New Comprehensive OTN Training…. Available Now. Click on the Banner Below to Learn More!!

Discounts Available for a Short Term!!

So When does the OTN PTE detect and flag a given One-Second Period as being a “Far-End Defect Second”?

ITU-T G.798 presents the following Performance Monitoring Equation for the ODUk_TT_Sk function.

pF_DS <- dBDI

Where:

dBDI is the current state of the ODUk-BDI or the Backward Defect Indicator Defect (at the ODUk Layer).

The OTN PTE (or ODUk_TT_Sk function) will continuously evaluate the above equation as it monitors its incoming ODUk signal.

This equation states that the OTN PTE will declare a given one-second period as being a Far-End Defect Second if it has declared the dBDI defect condition during any portion of that one second.

A given OTN PTE will declare a one-second period as a Far-End Defect Second if the remote OTN PTE declares any of the following defect conditions:

  • dAIS (ODU-AIS)
  • dOCI
  • dLCK
  • dTIM

In this case, the OTN PTE will increment the pF_DS parameter for each one-second period it categorizes as a Far-End Defect Second.

Conversely, the OTN PTE will declare a one-second period as an Available Second if the remote OTN PTE is not declaring any of the defects mentioned above. The OTN PTE will NOT increment the pF_DS parameter in this case.

What Does This Mean in English?

Of course, if the OTN PTE declares the dBDI defect condition, then this also means that the remote PTE is declaring a service-affecting defect condition. In other words, the pF_DS parameter reflects the health of the remote (or Far-End) terminal.

If the remote terminal declares no service-affecting defects, the near-end terminal will not increment the pF_DS parameter. On the other hand, if the remote terminal declares a service-affecting defect, then the near-end terminal will increment the pF_DS parameter.

So, if the ODUk_TT_Sk function has declared the dBDI defect condition for even a fraction of a given one-second period, it will declare it as a Far-End Defect Second. It will also set the parameter pF_DS to 1 and report that information to System Management.

Conversely, if the OTN PTE determines that the ODUk_TT_Sk function did not declare the dBDI defect condition at all during a given one-second period. In that case, it will declare that one-second period is a Far-End Available (Working) Second. In this case, the OTN STE will NOT set the parameter pF_DS to 1.

Hence the pF_DS parameter reflects the network’s health at the remote terminal (e.g., the other end of the ODUk Path).

Is there such a thing as a Near-End Defect Second?

Throughout this post, we have used the term: Far-End Defect Second. Does this mean that there is another parameter called Near-End Defect Second?

Answer: Yes, there is such a parameter. See the Near-End Defect Seconds (pN_DS) post at the ODUk Layer for more details.

Clueless about OTN? We Can Help!! Click on the Banner Below to Learn More.

Discounts Available for a Short Time!!

And Finally, Click on the Image Below to see More OTN-Related Topics in this Blog.

OTN Related Blog

OTN Related Topics within this Blog

OTN Related Topics within this Blog General Topics Consequent Equations - What are they and How can you use them? ...

OTN – Lesson 12 – Detailed Discussion of SNC/S Monitoring (Protection Switching)

This blog post presents a video that describes (in detail) SNC/S (Subnetwork Circuit Protection – Sublayer) Monitoring for Protection Switching.

Lesson 12 – Video 7 – Detailed Discussion of SNC/S (Subnetwork Circuit – Sublayer) Monitoring for Protection Switching

This blog post contains a video that presents a detailed discussion of SNC/S (Subnetwork Circuit – Sublayer) Monitoring for Protection Switching purposes at the ODU Layer.

In particular, this video will discuss the following topics:

  • A Detailed Review of SNC/S (Subnetwork Circuit Protection/Sublayer) Monitoring.
  • This video shows example locations/conditions of where we would use SNC/S Monitoring and why we would use this form of monitoring.
  • This video also highlights similarities of SNC/S with SNC/I Monitoring.
  • It also shows the differences between SNC/S and SNC/Ne or SNC/Ns monitoring.
  • Finally, this video reviews a Multi-Administrative Domain Network (and
    Tandem Connection Monitoring) and describes how SNC/S works within a given “Protect Domain.”

Check Out the Video Below.

Continue reading “OTN – Lesson 12 – Detailed Discussion of SNC/S Monitoring (Protection Switching)”

OTN – Lesson 12 – Detailed Discussion of SNC/N Monitoring (Protection Switching)

This blog post presents a video that describes (in detail) SNC/N (Subnetwork Protection – Non-Intrusive) Monitoring for Protection Switching.

Lesson 12 – Video 6 – Detailed Discussion of SNC/N (Subnetwork Circuit – Non-Intrusive) Monitoring for Protection Switching

This blog post contains a video that presents a detailed discussion of SNC/N (Subnetwork Circuit – Non-Intrusive Monitoring, for Protection-Switching purposes, at the ODU Layer.

In particular, this video will discuss the following topics:

  • A Detailed Review of SNC/Ne (Subnetwork Circuit Protection/Non-Intrusive End-to-End) Monitoring, and
  • A Detailed Review of SNC/Ns (Subnetwork Circuit Protection/Non-Intrusive Sublayer) Monitoring.
  • This video shows example locations/conditions of where we would use SNC/Ne or SNC/Ns Monitoring and why we would use this form of monitoring.
  • This video also highlights the similarities and differences between SNC/Ne and SNC/Ns Monitoring.

Check Out the Video Below

Continue reading “OTN – Lesson 12 – Detailed Discussion of SNC/N Monitoring (Protection Switching)”

OTN – Lesson 12 – Detailed Discussion of CL-SNCG/I Monitoring (Protection Switching)

This blog post presents a video that describes (in detail) CL-SNCG/I (Compound Links – Subnetwork Circuit Group – Inherent) Monitoring for Protection Switching.

Lesson 12 – Video 5 – Detailed Discussion of CL-SNCG/I (Compound Links – Subnetwork Circuit Group – Inherent) Monitoring for Protection Switching

This blog post contains a video that presents a detailed discussion of CL-SNCG/I Monitoring ], for Protection Switching purposes, at the ODU layer.

In particular, this video will discuss the following topics:

  • A Quick Review of the SNC/I Monitoring at the ODU Layer
    • A Single ODUj Tributary is the Normal Traffic Signal
    • How CI_SSF and CI_SSD initiate Protection Switching
  • How to perform CL-SNCG/I Monitoring at the ODU Layer
    • What Circuitry (Atomic Functions) that we should use
    • What defects to monitor
    • Which is the Normal Traffic Signal when doing CL-SNCG/I Monitoring at the ODU Layer?
    • What happens when we declare an ODUk Server-Layer service-affecting defects (such as dAIS, dOCI, dLCK, dTIM)?
    • What happens when we declare the PM-dDEG (ODU-Layer Signal Degrade) defect?
    • How does protection-switching work?
  • How does CL-SNCG/I Monitoring (for Protection-Switching) differ from SNC/I Monitoring for Protection-Switching?
    • PI-TSF/PI-TSD versus CI_SSF[n]/CI_SSD[n]
    • Multiple ODUj Tributary Signals are the Normal Traffic Signal
    • dPLM, dLOOMFI, dMSIM[n], and dLOFLOM[n] do not cause Protection-Switching when CL-SNCG/I Monitoring.

Check Out the Video Below

Continue reading “OTN – Lesson 12 – Detailed Discussion of CL-SNCG/I Monitoring (Protection Switching)”

OTN – Lesson 12 – Detailed Discussion of SNC/I Monitoring (Protection Switching)

This blog post presents a video that describes (in detail) SNC/I (Subnetwork Circuit – Inherent) Monitoring for Protection Switching.

Lesson 12 – Video 4 – Detailed Discussion of SNC/I (Subnetwork Circuit – Inherent) Monitoring for Protection Switching

This blog post contains a video that presents a detailed discussion of SNC/I Monitoring, both at the OTU and ODU layers.

In particular, this video will discuss the following topics:

  • How to perform SNC/I Monitoring at the OTU Layer
    • What Circuitry (Atomic Functions) that we should use
    • What defects to monitor
    • Which is the Normal Traffic Signal when doing SNC/I Monitoring at the OTU Layer.
    • What happens when we declare an OTU Layer Service-Affecting defect (dLOS, dLOF, dLOM, dLOL, dLOFLOM, dLOR, dAIS, and dTIM)?
    • What happens when we declare the SM-dDEG (OTU-layer Signal Degrade) defect?
    • How does protection-switching work?
  • How to perform SNC/I Monitoring at the ODU Layer
    • What Circuitry (Atomic Functions) that we should use
    • What defects to monitor
    • Which is the Normal Traffic Signal when doing SNC/I Monitoring at the ODU Layer.
    • What happens when we declare an ODUk Server-Layer service-affecting defects (such as dAIS, dOCI, dLCK, dTIM, dLOOMFI, and dPLM)?
    • What happens when we declare ODUj Tributary-Layer service-affecting defects (such as dLOFLOM and dMSIM)
    • What happens when we declare the PM-dDEG (ODU-layer Signal Degrade) defect?
    • How does protection-switching work?

Check Out the Video Below

Continue reading “OTN – Lesson 12 – Detailed Discussion of SNC/I Monitoring (Protection Switching)”

OTN – Lesson 12 – Introduction to SNCP (Subnetwork Circuit Protection)

This blog post introduces the concept of SNCP (Subnetwork Circuit Protection) Switching. This post also briefling introduction SNCP Monitoring schemes such as SNC/I, CL-SNCG/I, SNC/Ne, SNC/Ns and SNC/S.

Lesson 12 – Video 3 – Introduction to SNCP (Subnetwork Circuit Protection) Switching

This blog post contains a video that covers the introductory part of Subnetwork Circuit Protection switching.

In particular, this video will discuss the following topics:

  • Introduction to the concept of Subnetwork Circuit Protection (SNCP)-Switching
    • How is SNCP different from Trail Protection Switching
    • Why does the Industry prefer SNCP Monitoring/Switching instead of Trail Protection Monitoring/Switching?
  • Introduction to the following forms of SNCP Monitoring:
    • SNC/I – Subnetwork Circuit/Inherent Monitoring
    • CL-SNCG/I – Compound Link – Subnetwork Circuit Group/Inherent Monitoring
    • SNC/N – Subnetwork Circuit/Non-Intrusive Monitoring
      • SNC/Ne – Subnetwork Circuit/Non-Intrusive (End-to-End) Monitoring
      • SNC/Ns – Subnetwork Circuit/Non-Intrusive (Sublayer) Monitoring
    • SNC/S – Subnetwork Circuit/Sublayer Monitoring

We will cover each of these monitoring forms (for Protection-Switching purposes), in much greater detail, throughout the remaining videos in Lesson 12.

In particular, we will cover these forms of SNCP Monitoring (in detail) in the following videos.

This particular video provides a broad overview of each of these forms of monitoring.

Check Out the Video Below

Continue reading “OTN – Lesson 12 – Introduction to SNCP (Subnetwork Circuit Protection)”

OTN – Lesson 12 – Introduction to Linear Protection Switching – Part TWO

This blog post contains a Video that serves as the 2nd Introductory Video to Linear Protection-Switching. This video covers Hold-Off Timers, Wait-to-Restore Timers and reviews Trail Protection.

Lesson 12 – Video 2 – Introduction to Linear Protection Switching – Part TWO

This blog post contains a video that covers the second part of our Introduction to Linear Protection-Switching.

In particular, this video discusses and defines the following topics that pertain to Protection-Switching:

  • Nested Protection-Switching Domains
  • Hold-Off Timers – What are They and How are They Useful in a Protection-Switching Design?
  • Wait-to-Restore (WTR) Timers – What are WTR Timers, and why do We Use them?
  • A Review of Trail Protection – This video discusses what Trail Protection is and why it is not very popular in Protection-Switching Applications.

Check Out the Video Below

Continue reading “OTN – Lesson 12 – Introduction to Linear Protection Switching – Part TWO”

OTN – Lesson 11 – Tandem Connection Monitoring Multi-Administrative Domain Defect Analysis – Part TWO

This blog post contains the second of two videos that analyzes how the Multi-Administrative Domain uses Tandem Connection Monitoring to respond to service-affecting defects within an ODU signal passing through it.

Lesson 11 – Video 11 – Tandem Connection Monitoring (TCM) Multi-Administrative Domain Defect Analysis – Part TWO

This blog post contains a video covering the second (and final) part of the Multi-Administrative Domain Walk-Through when defects occur.

In particular, this video discusses how the Multi-Administrative Domain will respond to the presence of defects.

This video will analyze the Multi-Administrative Domain’s response to the following two cases.

Case 2 – Whenever a Service-Affecting defect occurs within Serving Operator Domain – Operator B, and

Case 3 – Whenever a Service-Affecting defect occurs within the Protect Domain.

NOTE: In the previous video, we analyzed Case 1 (Service-Affecting defect occurs within the ODU signal but outside of any of the administrative regions).

As we analyze the Multi-Administrative Domain’s response to these defects (for Cases 2 and 3), we will cover the following topics:

  • What exactly occurs within an ODU signal that experiences a service-affecting defect?
  • How do ODU-layer, ODUT-layer, and OTU-layer circuitry respond to such defects?
  • How does the circuitry within these Administrative Domains respond to the service-affecting defects associated with Cases 2 and 3?
  • What does the Path Terminating Equipment (at the remote terminal) do in response to these service-affecting defects?

This video will close out our discussion of Lesson 11 – Tandem Connection Monitoring.

Check Out the Video Below.

Continue reading “OTN – Lesson 11 – Tandem Connection Monitoring Multi-Administrative Domain Defect Analysis – Part TWO”

OTN – Lesson 11 – Tandem Connection Monitoring Multi-Administrative Domain Defect Analysis – Part ONE

This blog post contains the first of two videos that analyzes how the Multi-Administrative Domain uses Tandem Connection Monitoring to respond to service-affecting defects within the ODU signal passing through it.

Lesson 11 – Video 10 – TCM Multi-Administrative Domain Defect Analysis – Part ONE

This blog post contains a video covering the first part of the Multi-Administrative Domain Walk-Through when defects occur.

In particular, this video discusses how the Multi-Administrative Domain will respond to the presence of defects.

During this video, we assume that we are experiencing a service-affecting defect within the ODU signal (that passes through the Multi-Administrative Domain). However, in this case, we assume that the defect occurs outside any administrative regions. As we analyze the Multi-Administrative Domain’s response to this defect, we will cover the following topics:

  • What exactly occurs within an ODU signal that experiences a service-affecting defect?
  • How do ODU-layer, ODUT-layer, and OTU-layer circuitry respond to such defects?
  • How does each Administrative Domain respond to the presence of a service-affect defect outside of the Service-Requesting (or any other Domain) using Tandem Connection Monitoring?
  • What does the Path Terminating Equipment (at the remote terminal) do in response to this service-affecting defect?

I hope the student will better understand Tandem Connection Monitoring as we go through this and the following video.

Check Out the Video Below.

Continue reading “OTN – Lesson 11 – Tandem Connection Monitoring Multi-Administrative Domain Defect Analysis – Part ONE”

OTN – Lesson 11 – Tandem Connection Monitoring Multi-Administration Domain Walk-Thru – Part TWO

This post serves as Part TWO (and the Final Part) for the Multi-Administrative Domain Walk Through and Analysis for our study of Tandem Connection Monitoring.

Lesson 11 – Video 9 – TCM Multi-Administration Domain Walk Through – Part TWO

This blog post contains a video that covers the second (and final) part of the Multi-Administrative Domain Walk-Through.

In particular, this video covers the following topics:

  • Part TWO of our Multi-Administration Domain Walk-Through (using our knowledge of TCM-related atomic functions to analyze this network).

In particular, this post covers the following parts of the Multi-Administration Domain Walk-Through.

  • Initializing the Serving Operating Domain (Operator B) – TCM Level 3
  • Terminating the Serving Operating Domain (Operator B) – TCM Level 3
  • Initializing the Serving Operating Domain (Operator C) – TCM Level 3
  • Initializing the Protect Domain – TCM Level 4
  • Terminating the Protect Domain – TCM Level 4
  • Terminating the Serving Operating Domain (Operator C) – TCM Level 3
  • Terminating the Leased Service Serving Operator Domain – TCM Level 2
  • Terminating the Service Requesting Domain – TCM Level 1

This video serves as Part TWO (and the Final Part) of our Multi-Administration Domain Walk-Through and Analysis.

Check Out the Video Below.

Continue reading “OTN – Lesson 11 – Tandem Connection Monitoring Multi-Administration Domain Walk-Thru – Part TWO”