Sierra Hardware Design – All Things Electrical Design Blog
This post presents the 7th of the 7 Videos that covers training on the Peformance Monitoring of the ODUk Layer (for Non-Multiplexed Applications). This post focuses on the 100Gbps Ethernet Adaptation Sink Atomic Function, within the Sink Direction ODU-Layer Atomic Functions.
This video discusses how the ODUkP/CBR_ETC100GR-g_A_Sk (100Gbps Ethernet Adaptation Sink) Atomic Function processes an ODU4 signal that it receives from the upstream ODUk_TT_Sk Function.
In particular, this video discusses how this function terminates the ODU4 overhead, extracts out processes, and terminates the OPU4 overhead before it extracts and processes the 100GBASE-R client signal.
This post presents the 1st of the 7 Videos that covers training on the Peformance Monitoring of the ODUk Layer (for Non-Multiplexed Applications). This post focuses on the Source Direction ODU-Layer Atomic Functions.
This video begins our discussion of the Source-Direction ODU-Layer Atomic Functions for Non-Multiplexed Applications.
This video begins with a high-level overview of the Source-Direction circuitry (for Non-Multiplexed Applications). Afterward, this video covers the ODUkP/CBR-ETC100GR-g_A_So (or 100Gbps Ethernet Adaptation Source Atomic Function).
This atomic function takes a 100GBASE-R client signal and maps it into an ODU4 server signal.
This video discusses much of the processing that the ODUkP/CBR-ETC100GR-g_A_So Atomic Function will perform on this 100GBASE-R signal, as GMP maps this signal into an ODU4 server signal.
Continue reading “OTN – Lesson 10 – Video 1N (100Gbps Ethernet Adaptation Source) Atomic Function”
This post presents ITU-T G.806’s definition of a defect or defect condition.
ITU-T G.806 defines the word defect as follows:
Defect: The density of anomalies has reached a level where the ability to perform a required function has been interrupted.
We use defects as an input for performance monitoring, controlling consequent actions, and determining fault causes.
In other words, defects are bad.
If some piece of networking equipment is declaring a defect condition, it is saying it “cannot do its job properly” because of this condition.
We cover the following defects in this blog.
This post describes the role of the PSI (Payload Structure Identifier) byte, within the OPUk Overhead, is used within the OTN.
The PSI (or Payload Structure Identifier) byte is an Overhead byte within the OPUk structure.
Figure 1 presents an OPU frame with the location of the PSI byte identified.
Figure 1, Illustration of an OPUk Frame Structure with the Overhead Bytes (along with the PSI Byte) Identified
The purpose of the PSI byte is to permit an OTN Path Terminating Equipment (PTE) to transport a 256-byte PSI (payload structure identifier) message throughout the OTN (Optical Transport Network).
The primary purpose of this 256-byte PSI Message is to permit the Source PTE to alert the OTN (Network) of the type of data (or traffic) we are transporting within this particular OPU data stream.
Since each OPUk frame contains only 1 PSI byte, an OTN PTE will have to transmit 256 consecutive OPU frames to transmit this PSI message completely.
The OTN PTE will align its transmission of this 256-byte PSI message with the MFAS byte.
Please see the OTUk Frame Structure post for more information on the MFAS byte.
In other words, whenever the OTN PTE is transmitting an OTUk frame with the MFAS byte set to “0x00”, then the OTN PTE will also be sending the first byte of the PSI message (e.g., PSI[0]) via the PSI byte-field.
Likewise, whenever the OTN PTE is transmitting an OTUk frame with the MFAS byte set to “0x01”, then the OTN PTE will also be sending the second byte within this 256-byte message (e.g., PSI[1]) via the PSI byte field, and so on.
An OTN Source PTE will transport one of two types of PSI Messages.
I will describe each of these types of PSI Messages below.
We will use the Non-Multiplexed Traffic PSI Message when transporting Non-Multiplexed Traffic within our OPU data stream.
Examples of Non-Multiplexed Traffic would be:
In other words, we are handling Non-Multiplexed Traffic whenever we only transport a single Non-OTN client signal via this OPUk data stream.
I present an illustration of an OPU Frame, with the PSI field highlighted (along with a break-out of the Non-Multiplexed Traffic type of PSI Message) below in Figure 2.
Figure 2, Illustration of an OPU Frame, transporting the Non-Multiplexed traffic of PSI Message
NOTE: The easiest way to tell if you’re working with the Non-Multiplexed Traffic type of PSI Message is to check and see if you see the CSF (Client Signal Fail) bit-field in PSI Byte # 2.
If the CSF bit-field is present, you’re dealing with the Non-Multiplexed Traffic type of PSI Message.
If the CSF bit-field is NOT present (within the PSI Message), then you are dealing with the other type of PSI Message.
We use the Multiplexed Traffic type of PSI Message anytime we work with an OPU server signal transporting numerous lower-speed ODUj Tributary Signals.
For example, if we mapped and multiplexed 80 ODU0 tributary signals into an OPU4 server signal, then this OPU4 signal would transport the Multiplexed Traffic type of PSI Message.
Figure 3 presents an illustration of an OPU Frame, with the PSI field highlighted, along with a break-out of the Multiplexed Type of PSI Message.
Figure 3, Illustration of an OPU Frame transporting the Multiplexed Traffic Type of PSI Message
Again, one big difference between the Multiplexed Traffic type of PSI Message and that for Non-Multiplexed Traffic is that the Multiplexed Traffic type of PSI Message will not have the CSF (Client Signal Fail) bit-field.
The PSI (Payload Structure Identifier) message is a 256-byte message that an OTN terminal will transport via the PSI byte for 256 consecutive OPUk/ODUk/OTUk frames.
Let’s talk a little bit about the data that we are transporting within these PSI Messages.
The first byte of the PSI Message (e.g., PSI[0]) carries the Payload Type (or PT) value. The PT byte identifies the type of client data the OPUk structure is transporting via its payload.
First, Table 1 presents a list of standard PT values and the corresponding client data types (being transported within the OPUk Structure).
Table 1a, PT (PSI[0]) Values, and the Corresponding Client Data within the OPUk Structure – Part I
Table 1b, PT (PSI[0]) Values, and the Corresponding Client Data within the OPUk Structure – Part II
NOTES:
Table 1c, PT (PSI[0]) Values, and the Corresponding Client Data within the OPUk Structure – Part III
NOTE:
Table 1d, PT (PSI[0]) Values, and the Corresponding Client Data within the OPUk Structure – Part IV
Other posts contain detailed information on how ITU-T G.709 recommends that the System Designer map each client signal into their corresponding OPUk structure.
Click HERE for more information about the PT = 0x21 Method for Mapping/Multiplexing Lower-Speed ODUj signals into a Higher-Speed ODUk Signal.
PSI bytes 1 and 3 through 255 are for “Mapping and Concatenation Specific” roles that we will discuss in another post.
For the Multiplexed-Traffic type of PSI Message, we use these bytes to transport MSI (Multiplex Structure Identifier) information throughout the OTN.
In other words, we will transport the MSI information (via these PSI Messages) for applications in which we are mapping/multiplexing lower-speed ODUj tributary signals into higher-speed OPUk/ODUk server signals.
The MSI aims to identify these lower-speed ODUj tributary signals we are transporting via this OPUk/ODUk signal to the OTN.
You can think of the MSI as a passenger list or manifest of lower-speed ODUj tributary signals riding along (or being transported) within this OPUk server signal.
PSI byte 2, Bit 1 (for the Non-Multiplexed Traffic PSI Message) is the CSF (or Client Signal Fail) indicator. The ITU-T Standards Committee has reserved PSI Byte 2, Bits 2 through 8 for “future standardization.”
We discuss the CSF indicator and the MSI information in other posts.
We also extensively discuss these PSI Messages within THE BEST DARN OTN TRAINING PRESENTATION….PERIOD!!!.
You can click on the Banner below to learn more our this training package.
