<\/span><\/h2>\nWhen the OPU carries low-rate class ODUs, the ODU needs to be adapted by ODTU (Optical Data Tributary Unit). ODTU contains an overhead part and a Payload part, the following are the bandwidths of various ODTU signal payloads.<\/p>\n
![\"the](\"https:\/\/www.fibermall.com\/blog\/wp-content\/uploads\/2023\/04\/the-bandwidths-of-various-ODTU-signal-payloads.png\")
<\/p>\n
There are two types of ODTU:<\/p>\n
1) ODTU01, ODTU12, ODTU13, ODTU23 are one type (ODTUjk), referring to the tributary units that map the lower level ODUj to the higher level OPUk, using AMP mapping;<\/p>\n
2) ODTU2.ts, ODTU3.ts, and ODTU4.ts is another type (ODTUk.ts), which refers to the tributary unit that uses ts high rate level OPUk, using GMP mapping.<\/p>\n
In order to illustrate the rate law of ODTU more clearly, let’s first look at the process of mapping low-rate-level ODUs to high-rate-level OPUs.<\/p>\n
![\"the](\"https:\/\/www.fibermall.com\/blog\/wp-content\/uploads\/2023\/04\/the-process-of-mapping-low-rate-level-ODUs-to-high-rate-level-OPUs.png\")
<\/p>\n
Step 1: ODUj can be mapped to ODTUjk by AMP mapping or to ODTUk.ts by GMP mapping.<\/p>\n
Step 2: HO OPUk will be divided into many 1.25G\/2.5G tributary slots, and ODTUjk or ODTUk.ts will be mapped into these 1.25G\/2.5G tributary slots by byte synchronous mapping (simple time division multiplexing).<\/p>\n
![\"ODUj\"](\"https:\/\/www.fibermall.com\/blog\/wp-content\/uploads\/2023\/04\/ODUj-1.png\")
<\/p>\n
For example, mapping ODU2 into OPU3 is divided into two steps:<\/p>\n
1) first map ODU2 to ODTU23, then map ODTU23 to OPU3<\/p>\n
2) The rate of ODTU23 is about 10G, which needs to occupy 8 1.25G tributary slots, so you need to map ODTU23 to the 8 1.25G tributary slots of OPU3.<\/p>\n
Another example is to map ODU2 to OPU4, which is divided into 2 steps:<\/p>\n
1) first map ODU2 to ODTU4.8<\/p>\n
2) The rate of ODTU4.8 is about 10G, which needs to occupy 8 1.25G tributary slots, so you need to map ODTU4.8 to the 8 1.25G tributary slots of OPU4.<\/p>\n
It should be noted that the 1.25G tributaries of OPU2\/OPU3\/OPU4, although they are all called 1.25G tributaries, actually have different rates, with OPU2’s 1.25G tributary being the slowest at about 1.249Gbps and OPU4’s 1.25G tributary being the fastest at about 1.301Gbps.<\/p>\n
Rule 5<\/strong>: The payload bandwidth formula of ODTUjk includes two parts: the integer and the mantissa.<\/p>\n1) Integer: OPUk can carry several ODTUjk, then the integer part is 3808 divided by it.<\/p>\n
a) OPU1 can carry 2 ODTU01, the integer part 1904=3808\/2<\/p>\n
b) OPU2 can carry 4 ODTU12, the integer part 952=3808\/4<\/p>\n
c) OPU3 can carry 16 ODTU23, the integer part 238=3808\/16<\/p>\n
d) OPU3 can carry 4 ODTU13, the integer part 952=3808\/4<\/p>\n
2) Mantissa: OPUk can carry several ODTUjk, then the integer part is 1\/4 divided by it.<\/p>\n
a) OPU1 can carry 2 ODTU01, the fractional part 1\/4\/2 = 1\/8<\/p>\n
b) OPU2 can carry 4 ODTU12, the fractional part1\/4\/4 = 1\/16<\/p>\n
c) OPU3 can carry 16 ODTU13, the fractional part 1\/4\/16 = 1\/64<\/p>\n
d) OPU3 can carry 4 ODTU23, the fractional part 1\/4\/4 = 4\/64<\/p>\n
The mapping of ODTU to OPU is time division multiplexing, OPU is divided into multiple 1.25G\/2.5G tributary slots (TS) and ODTU is mapped into these tributary slots, the mapping method is simple time division multiplexing.<\/p>\n
When OPU1 carries 2 ODTU01, the load of each ODTU01 occupies 1\/2 of the OPU1 load, so the load of ODTU01 should be half of the OPU1 load rate, i.e. 3808\/2\/3808*OPU1 load rate = 1904\/3824*ODU1 load rate.<\/p>\n
In addition, we need to take into account the NJO adjustment opportunity in the OPU1 overhead. Each OPU1 frame (4 lines) has only 1 byte of NJO adjustment opportunity, so for 2 ODTU01s, each ODTU01 needs two OPU1 frames to have 1 byte of NJO adjustment opportunity. After taking this adjustment opportunity into account, ODTU01 should also add 1\/4\/2 \/3808* OPU1 load rate. This is the fractional part of the bandwidth calculation. It is a similar calculation for both OPU2\/OPU3.<\/p>\n
Rule 6<\/strong>: The payload rate of ODTUk.ts is proportional to the number of occupied tributary slots ts and proportional to the number of columns of 1.25G tributary slots in OPUk.<\/p>\nODTUk.ts all use 1.25G tributary slots. ts indicates the number of occupied tributary slots, so the speed is of course proportional to ts. The more ts tributaries are needed, the higher the speed of ODTUk.ts. In different OPUk, the number of columns occupied by 1.25G tributary slots is different. the higher the speed level of OPUk, the less the number of columns occupied by 1.25G tributary slots. Therefore, the rate of ODUk.ts is proportional to the number of 1.25G tributary slots in OPUk when the rate of ODUk is used as the base.<\/p>\n
In OPU2, there are 8 1.25G tributary slots, so the number of columns is 3808\/8 = 476;<\/p>\n
In OPU3, there are 32 1.25G tributary slots, so the number of columns is 3808\/32= 119;<\/p>\n
In OPU4, there are 80 1.25G tributary slots, so the number of columns is 3800\/80 = 47.5 (where the rightmost 8 columns are filled);<\/p>\n
ODTUk.ts does not use NJO adjustment opportunities, so its rate is not related to NJO and does not have a fractional part like ODTUjk.<\/p>\n
<\/span>How to Solve <\/b><\/strong>t<\/b><\/strong>he Rate Difference<\/b><\/strong><\/span><\/span><\/h2>\nWhen the data is mapped to OPU (including the case that the customer side signal is directly mapped to OPU, and the low rate level ODU is mapped to the high rate level OPU, etc.), there is a certain difference between the data rate and the OPU load rate.<\/p>\n
This difference may be due to the mismatch between the data rate and the OPU rate itself, or it may be caused by the inconsistency between the clock of data generation and the clock of OPU. The rate difference problem can be solved by a reasonable mapping method, and the OTN protocol specifies AMP, BMP, GMP, and GFP-F mapping methods.<\/p>\n
AMP: Asynchronous Mapping Procedure<\/p>\n
BMP: Bit-synchronous Mapping Procedure<\/p>\n
GMP: Generic Mapping Procedure<\/p>\n
GFP-F: Frame-mapped Generic Framing Procedure<\/p>\n
![\"the](\"https:\/\/www.fibermall.com\/blog\/wp-content\/uploads\/2023\/04\/the-OTN-protocol-specifies-AMP-BMP-GMP-and-GFP-F-mapping-methods.png\")
<\/p>\n
The differences between the use of BMP, AMP, and GMP mapping methods are shown in the table above.<\/p>\n
BMP must have the Server clock and the Client clock completely homogeneous;<\/p>\n
AMP mapping must have the Client signal clock frequency within 65 ppm of the OPUk’s load clock frequency<\/p>\n
GMP must have a Client signal rate no greater than the load rate of OPUk.<\/p>\n
There are two ways to map the signal to OPU, one is to map directly to OPU, and the other is to map to ODU and then map to OPU at a higher speed level. The following is the mapping type of ODUj to OPUk.<\/p>\n
![\"the](\"https:\/\/www.fibermall.com\/blog\/wp-content\/uploads\/2023\/04\/the-mapping-type-of-ODUj-to-OPUk.png\")
<\/p>\n
Rule 7: The mapping of PT=20 is 1.25G tributary mapping (except ODU0->OPU1); the mapping of PT=21 is 2.5G tributary mapping, and the mapping of PT=22 is 5G tributary mapping.<\/p>\n
Mapping of ODU0:<\/b><\/strong><\/p>\nODU0 -> ODTU01 (AMP) -> OPU1 (PT=20)<\/p>\n
ODU0 -> ODTU2.1 (GMP) -> OPU2 (PT=21)<\/p>\n
ODU0 -> ODTU3.1 (GMP) -> OPU3 (PT=21)<\/p>\n
ODU0 -> ODTU4.1 (GMP) -> OPU4 (PT=21)<\/p>\n
Mapping of ODU<\/b><\/strong>1:<\/b><\/strong><\/p>\nODU1 -> ODTU12 (AMP)-> OPU2 (PT=20, PT=21)<\/p>\n
ODU1 -> ODTU13 (AMP) -> OPU3 (PT=20, PT=21)<\/p>\n
ODU1 -> ODTU4.2 (GMP) -> OPU4 (PT=21)<\/p>\n
Mapping of ODU<\/b><\/strong>2:<\/b><\/strong><\/p>\nODU2-> ODTU23 (AMP) -> OPU3 (PT = 20, PT=21)<\/p>\n
ODU2-> ODTU4.8(GMP) -> OPU4 (PT=21)<\/p>\n
Mapping of ODU<\/b><\/strong>2e:<\/b><\/strong><\/p>\nODU2-> ODTU3.9 (GMP) -> OPU3 (PT=21)<\/p>\n
ODU2-> ODTU4.8(GMP) -> OPU4 (PT=21)<\/p>\n
Mapping of ODU<\/b><\/strong>3:<\/b><\/strong><\/p>\nODU3-> ODTU4.31 (GMP) -> OPU4 (PT=21)<\/p>\n
We also list the cases where SDH and ETH client signals are directly mapped to OPUs as follows:<\/p>\n
STM-16 -> OPU2 (AMP PT=02, BMP PT=03)<\/p>\n
STM-64 -> OPU3 (AMP PT=02, BMP PT=03)<\/p>\n
STM-256 -> OPU4(AMP PT = 02, BMP PT=03)<\/p>\n
1000 BASE-X -> OPU0 (GMP PT=07)<\/p>\n
10G BASE-R -> OPU2e (BMP, PT=07?)<\/p>\n
40G BASE-R -> OPU3 (GMP PT = 07)<\/p>\n
100G BASE-R-> OPU4 (GMP PT = 07)<\/p>\n
Rule 8<\/strong>: The various customer signals are mapped as follows:<\/p>\nODTU01, ODTU12, ODTU13, ODTU23 using AMP mapping;<\/p>\n
ODTUk.ts uses GMP mapping;<\/p>\n
SDH to the corresponding OTU using AMP or BMP mapping;<\/p>\n
GMP mapping for Ethernet signals (except OTU2e);<\/p>\n
10GE to OTU2e using BMP mapping.<\/p>\n
Note that 10GE to OTU2e can only use BMP mapping, this is because the 10GE signal frequency deviation is 100ppm, AMP cannot support such a large clock jitter, so only BMP mapping can be used.<\/p>\n
\n- BMP without rate difference<\/li>\n<\/ol>\n
BMP mapping applies only when the rate of the Client signal is proportional to that of the Server signal. After a fractional frequency multiplication of the Client signal clock, it can be used as the clock of the Server signal; After the fractional frequency division in the recovery of the Server signal, it can be used as the clock of the Client signal.<\/p>\n
BMP is used to map 10BASE-R to OPU2e. The STM signal to the corresponding OPUk can be mapped using either BMP or AMP.<\/p>\n
\n- AMP resolves the rate difference<\/li>\n<\/ol>\n
The AMP signal resolves the difference between the Client signal rate and the Server signal rate within a small range. There are two situations:<\/p>\n
1) Frequency of Client signal and Server signal in a proportional relationship:<\/p>\n
But because each uses its own local clock, errors in the clock itself can lead to differences in speed. For example, when STM-16 is loaded into OPU2 and OPU2 is sent with the local clock, the difference between the sent local clock and the STM-16 clock will cause an error in the rate ratio relation. This needs to be solved by the pointer adjustment method of the AMP map.<\/p>\n
![\"Frequency](\"https:\/\/www.fibermall.com\/blog\/wp-content\/uploads\/2023\/04\/Frequency-of-Client-signal-and-Server-signal-in-a-proportion.png\")
<\/p>\n
AMP mapping can resolve errors of +\/-65ppm, input signal +\/-45ppm, and OPU clock +\/-20ppm. So where did this 65ppm figure come from? In fact, it is very simple: the payload area of OPUk is 3080*4 bytes. For each OPUk frame, there is a 1-byte positive adjustment opportunity PJO and a 1-byte negative adjustment opportunity NJO. Therefore, the maximum acceptable rate difference is +\/-1 \u00f7 (3080*4) = +\/-65.7ppm.<\/p>\n
2) AMP mapping of ODTUjk:<\/p>\n
When ODUj is mapped to a 1.25G or 2.5G branch of OPUk via ODTUjk, ODTUjk has its own branch overhead TSOH to accommodate the rate difference between ODUj and ODTUjk. ODTUjk contains 1-byte negative tune-opportunity NJO and 2 bytes positive tune-opportunity PJO1 and PJO2. The methods of judging adjustment opportunities through JC are as follows:<\/p>\n
![\"AMP](\"https:\/\/www.fibermall.com\/blog\/wp-content\/uploads\/2023\/04\/AMP-mapping-of-ODTUjk.png\")
<\/p>\n
Since each branch needs to use the overhead byte of OPUk, so the JC, NJO and so on of each branch slot are time multiplexed, that is, each branch slot uses the corresponding complex frame to indicate the OPUk overhead of the frame represented by MFAS. The same is true for PJOs, where the PJO overhead of two bytes per branch also uses the first and second column bytes indicated by the corresponding MFAS value. As shown in the picture below:<\/p>\n
![\"each](\"https:\/\/www.fibermall.com\/blog\/wp-content\/uploads\/2023\/04\/each-branch-needs-to-use-the-overhead-byte-of-OPUk.png\")
<\/p>\n
Then, the accepted range of rate difference for AMP mapping of ODTUjk is (-65ppm , +130ppm). The rate difference is calculated as follows:<\/p>\n
![\"the](\"https:\/\/www.fibermall.com\/blog\/wp-content\/uploads\/2023\/04\/the-calculation-of-the-rate-difference.png\")
<\/p>\n
The following is the fixed padding of ODU1 mapped to ODTU13, there are 238 columns, and 119 columns are set as fixed padding.<\/p>\n
![\"the](\"https:\/\/www.fibermall.com\/blog\/wp-content\/uploads\/2023\/04\/the-fixed-padding-of-ODU1-mapped-to-ODTU13.png\")
<\/p>\n
When ODUjk is loaded, the rate difference ranges from 0 to 35.5ppm, the clock difference of input data is +\/-20ppm, and the clock difference of output data is also +\/-20ppm, so the rate difference of loading is -40ppm to 75.5ppm. A tuner of +\/-65ppm for such a byte is obviously not enough. Therefore, ODUjk needs to use a 2-byte positive adjustment opportunity to make an acceptable rate difference of -65 PPM to 130ppm.<\/p>\n
\n- GMP mapping solves greater rate differences<\/li>\n<\/ol>\n
GMP mapping can address larger rate differences, requiring that the client-side signal must be smaller than OPUk’s load rate. GMP does not use NJO bytes. GMP uses the Sigma-Delta algorithm to intermittently mark certain data in the OPUk load as fixed fill and cannot be filled in the customer-side model, thus making the customer-side signal use the OPUk load rate.<\/p>\n
OTUk.ts carrier mode: GMP mapping mode is used. At the same time, 1000BASE<\/span><\/a>-X, 40GBASE-R, and 100GBASE-R are mapped to OPU0, OPU3, and OPU4 respectively in GMP mode.<\/p>\n![\"OTUk.ts](\"https:\/\/www.fibermall.com\/blog\/wp-content\/uploads\/2023\/04\/OTUk.ts-carrier-mode.png\")
<\/p>\n
<\/span>Summary<\/b><\/strong><\/span><\/span><\/h2>\nFiberMall summarizes the various rate definitions in the OTN protocol and illustrates the principles implied by these rate definitions. This includes the OTN\/ODU\/OPU rates, the ODTU rates, and the pointer adjustment rules to resolve these rate differences.<\/p>\n