](https://global.ihs.com/search_res.cfm?RID=TIA&org_code=TIA&INPUT_DOC_NUMBER=TIA-825)
+
+# 3 Terms and definitions
+
+In the definition and text, $L$ will refer to the relative power level of a signal, expressed in dBm0 (as defined by [ITU-T G.711]) and $A$ will refer to the attenuation or loss of a signal path expressed in dB. These definitions assume that non-linearities are not present in the echo path and that the signal at $S_{\text{in}}$ is purely echo. It is recognized that non-linearities may be present in a network.
+
+This Recommendation defines the following terms:
+
+## 3.1 acoustic echo
+
+Acoustic echoes consist of reflected signals caused by acoustic environments. In these acoustic environments, an echo path is introduced by the acoustic path from the loudspeaker or earpiece to the microphone, e.g., echo created from hands-free speakerphones.
+
+## 3.2 cancelled end
+
+The side of an echo canceller which contains the echo path on which this echo canceller is intended to operate. This includes all transmission facilities and equipment (including the hybrid and terminating telephone set) which is included in the echo path. In previous versions of ITU-T G.168, this was defined as the near end.
+
+## 3.3 combined loss ( $A_{\text{COM}}$ )
+
+The sum of echo return loss, echo return loss enhancement and non-linear processing loss (if present). This loss relates $L_{\text{Rin}}$ to $L_{\text{RET}}$ by:
+
+$$L_{\text{RET}} = L_{\text{Rin}} - A_{\text{COM}}, \text{ where:}$$
+$$A_{\text{COM}} = A_{\text{ECHO}} + A_{\text{CANC}} + A_{\text{NLP}}$$
+
+## 3.4 comfort noise
+
+Insertion of pseudo-random noise during the silent interval when the NLP operates or allowance of some of the background or idle channel noise to pass through the NLP in order to prevent the annoyance of intervals of speech with background noise followed by intervals of silence.
+
+## 3.5 composite echo
+
+Composite echoes consist of the electric echoes and acoustic echoes caused by reflected signals at hybrids and acoustic environments, e.g., analogue hands-free telephones.
+
+## 3.6 convergence
+
+The process of developing a model of the echo path which will be used in the echo estimator to produce the estimate of the circuit echo.
+
+## 3.7 convergence time
+
+For a defined echo path, the interval between the instant a defined test signal is applied to the receive-in port of an echo canceller with the estimated echo path impulse response initially set to zero, and the instant the returned echo level at the send-out port reaches a defined level.
+
+## 3.8 double-talk
+
+The simultaneous application of signals at $R_{\text{in}}$ and $S_{\text{gen}}$ .
+
+## 3.9 echo canceller
+
+A voice-operated device placed in the 4-wire portion of a circuit and used for reducing the cancelled end echo present on the send path by subtracting an estimation of that echo from the cancelled end echo (see Figure 2).
+
+
+
+Figure 2: Location of levels and loss of an echo canceller. This block diagram shows the internal structure of an echo canceller. A 'Hybrid' component on the left connects to two 'Network elements'. The top 'Network elements' block outputs a signal S\_in to a 'Digital subtractor'. The bottom 'Network elements' block receives a signal R\_out from the 'Digital subtractor'. A dashed line labeled 'Cancelled end' with an arrow pointing to the signal path between the network elements and the digital subtractor is labeled A\_ECHO. The 'Digital subtractor' also receives an input from an 'Echo estimator and other control circuitry' block. The output of the digital subtractor is sent to a 'Non-linear processor' block. The 'Non-linear processor' outputs a signal S\_out. The 'Non-linear processor' block is also labeled with A\_NLP and L\_RES. The 'Echo estimator and other control circuitry' block receives inputs from both the 'Digital subtractor' and the 'Receive path' (labeled R\_in). The 'Receive path' is a horizontal line at the bottom of the diagram. The entire echo canceller unit is enclosed in a dashed box. Labels include A\_CANC, Send path, Non-cancelled end, L\_RET, L\_Rin, and G.168(09)\_F02.
+
+Figure 2 – Location of levels and loss of an echo canceller
+
+## 3.10 echo cancellers in tandem
+
+Multiple echo cancellers in a connection that are meant to cancel echo from the same echo source.
+
+## 3.11 echo path
+
+The transmission path between $R_{out}$ and $S_{in}$ of an echo canceller. This term is intended to describe the signal path of the echo.
+
+## 3.12 echo path capacity ( $\Delta$ )
+
+The maximum echo path delay for which an echo canceller is designed to operate.
+
+## 3.13 echo path delay ( $t_d$ )
+
+The delay from the $R_{out}$ port to the $S_{in}$ port due to the delays inherent in the echo path transmission facilities *including* dispersion time due to the network elements. In case of multiple echo paths, all delays and dispersions of any individual echo path are included. The dispersion time, which varies with different networks, is required to accommodate the band-limiting, and hybrid transit effects (see Figure 3).
+
+
+
+Figure 3: Example of an impulse response of an echo path. This graph shows the impulse response h(t) of an echo path. The vertical axis is labeled h(t) and the horizontal axis represents time. The response starts with a small initial peak, followed by a series of oscillations that decay over time. Two time intervals are marked: t\_r (transit time) from the start to the beginning of the main oscillations, and t\_d (echo path delay) from the start to the end of the significant oscillations. The label G.168(09)\_F03 is present in the bottom right corner.
+
+Figure 3 – Example of an impulse response of an echo path
+
+## **3.14 echo return loss (ERL) ( $A_{\text{ECHO}}$ )**
+
+The attenuation of a signal from the receive-out port ( $R_{\text{out}}$ ) to the send-in port ( $S_{\text{in}}$ ) of an echo canceller, due to transmission and hybrid loss, i.e., the loss in the (cancelled-end) echo path.
+
+NOTE – ERL is not the same as echo loss defined in clause 2.2 of [ITU-T G.122] since echo loss is a weighted integral of the loss/frequency function over the band 300-3400 Hz, and so has a fixed value for any particular echo path characteristic. Also, echo loss applies to loss of the a-t-b path viewed from the virtual switching point of the international circuit. The echo canceller may be located closer to the echo reflection point.
+
+## **3.15 echo return loss enhancement (ERLE) ( $A_{\text{CANC}}$ )**
+
+The attenuation of the echo signal as it passes through the send path of an echo canceller. This definition specifically excludes any non-linear processing on the output of the canceller to provide for further attenuation.
+
+## **3.16 electric echo**
+
+Electric echoes consist of reflected signals caused by the cancelled-end impedance mismatch, e.g., at a 2-wire/4-wire conversion unit (hybrid).
+
+## **3.17 H register**
+
+The register within the echo canceller which stores the impulse response model of the echo path.
+
+## **3.18 H register reset**
+
+Clear (zero) the H register and initialize any other appropriate internal variables of the echo canceller. This action is meant to simulate what happens at the start of a call for those cancellers externally controlled by the switch.
+
+## **3.19 leak time**
+
+The interval between the instant a test signal is removed from the receive-in port of a fully-converged echo canceller and the instant the echo path model in the echo canceller changes such that, when a test signal is reapplied to $R_{\text{in}}$ with the convergence circuitry inhibited, the returned echo is at a defined level.
+
+This definition refers to echo cancellers employing, for example, leaky integrators in the convergence circuitry.
+
+## **3.20 non-cancelled end**
+
+The side of an echo canceller which does not contain the echo path on which this echo canceller is intended to operate. In previous versions of ITU-T G.168, this was defined as the far end.
+
+## **3.21 non-linear processor (NLP)**
+
+A device having a defined suppression threshold level and in which:
+
+- a) signals having a level detected as being below the threshold are suppressed; and
+- b) signals having a level detected as being above the threshold are passed although the signal may be distorted (for example see Annex B).
+
+This Recommendation assumes an echo canceller is equipped with an NLP function that can be enabled or disabled when performing the tests defined in this Recommendation. An NLP function can be enabled or disabled by the user (for the purpose of performing a particular test), or may also be disabled upon detection of an appropriate disabling tone (e.g., 2100 Hz) as described in clause 7.1.
+
+NOTE 1 – The precise operation of an NLP depends upon the detection and control algorithm used.
+
+NOTE 2 – An example of an NLP is an analogue centre clipper in which all signal levels below a defined threshold are forced to some minimum value.
+
+## **3.22 non-linear processing loss ( $A_{\text{NLP}}$ )**
+
+Additional attenuation of residual echo level by an NLP placed in the send path of an echo canceller.
+
+NOTE – Strictly, the attenuation of a non-linear process cannot be characterized by a loss in dB. However, for purposes of illustration and discussion of echo canceller operation, the careful use of $A_{\text{NLP}}$ is helpful.
+
+## **3.23 open echo path**
+
+An echo path with infinite echo return loss.
+
+NOTE – In tests where an open echo path is used, it is important to break the path at a specific location. This location is stated in each individual test.
+
+## **3.24 pure delay ( $t_r$ )**
+
+The delay from the $R_{\text{out}}$ port to the $S_{\text{in}}$ port due to the delays inherent in the near-end echo path transmission facilities, not including dispersion time due to the network elements. In this case, the transit time directly across the hybrid is assumed to be zero (see Figure 3).
+
+## **3.25 residual echo level ( $L_{\text{RES}}$ )**
+
+The level of the echo signal which remains at the send-out port of an operating echo canceller after imperfect cancellation of the circuit echo. It is related to the receive-in signal $L_{\text{Rin}}$ by:
+
+$$L_{\text{RES}} = L_{\text{Rin}} - A_{\text{ECHO}} - A_{\text{CANC}}$$
+
+Any non-linear processing is not included.
+
+## **3.26 returned echo level ( $L_{\text{RET}}$ )**
+
+The level of the echo signal at the send-out port of an operating echo canceller which will be returned to the talker. The attenuation of an NLP is included, if one is normally present. $L_{\text{RET}}$ is related to $L_{\text{Rin}}$ by:
+
+$$L_{\text{RET}} = L_{\text{Rin}} - (A_{\text{ECHO}} + A_{\text{CANC}} + A_{\text{NLP}})$$
+
+If non-linear processing is not present, note that $L_{\text{RES}} = L_{\text{RET}}$ .
+
+## **3.27 signal processing device (SPD)**
+
+A hardware device that contains functions such as electric or acoustic echo control, noise reduction or automatic level control.
+
+## **3.28 signal processing function (SPF)**
+
+A software function that performs voice processing such as electric or acoustic echo control, noise reduction or automatic level control.
+
+## **3.29 signal processing network equipment/element (SPNE)**
+
+Type of network equipment or element which contains one or more signal processing functions or devices.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|-------|---------------------------------------------|
+| ADPCM | Adaptive Differential Pulse Code Modulation |
+| ATME | Automatic Test and Measurement Equipment |
+| CED | Called station Identification |
+| CNG | CalliNG Tone |
+| CPE | Customer Premises Equipment |
+| CSI | Called Subscriber Identification |
+| CSS | Composite Source Signal |
+| DCME | Digital Circuit Multiplication Equipment |
+| DCS | Digital Command Signal |
+| DEC | Digital Echo Canceller |
+| DIS | Digital Identification Signal |
+| DT | Double Talk |
+| DTDT | Double Talk Detection Threshold |
+| DTMF | Dual Tone Multi-Frequency |
+| EC | Echo Canceller |
+| ERL | Echo Return Loss |
+| ERLE | Echo Return Loss Enhancement |
+| FAX | Facsimile |
+| FFT | Fast Fourier Transform |
+| FIR | Finite Impulse Response |
+| HDLC | High-level Data Link Control |
+| ISDN | Integrated Services Digital Network |
+| MLS | Maximal Length Sequence |
+| MOS | Mean Opinion Score |
+| NLMS | Normalized Least-Mean Square |
+| NLP | Non-Linear Processor |
+| NSF | Non-Standard Facilities |
+| NSS | Non-standard Set-up |
+| PCM | Pulse Code Modulation |
+| PCME | Packet Circuit Multiplication Equipment |
+| PN | Pseudo Noise |
+| PSTN | Public Switched Telephone Network |
+| RMS | Root Mean Square |
+
+| | |
+|------|---------------------------------------------|
+| SPD | Signal Processing Device |
+| SPF | Signal Processing Function |
+| SPNE | Signal Processing Network Equipment/Element |
+| TCLw | Weighted Terminal Coupling Loss |
+| TSI | Transmitting Subscriber Identification |
+| TTL | Transistor-Transistor Logic |
+
+# 5 Test signals
+
+The tests in this Recommendation use special signals such as noise, tones, Group 3 facsimile signals, and a subset of the composite source signals (CSS) consisting of the bandlimited CSS with speech like power density spectrum (pseudo noise signal generated using 8192 pt. FFT) and the bandlimited CSS for double talk (see Annex C and [ITU-T P.501]). The CSS emulates the characteristics of speech, and its use as a test signal improves the ability to measure echo canceller performance for speech signals.
+
+Furthermore, network echo cancellers should perform adequately on many non-speech signals, e.g., voiceband data, as well as under non-ideal network scenarios. Tests are included to test performance for Group 3 facsimile signals, residual acoustic echoes (optional), and non-linearities in the echo path such as may arise with low bit rate encoding in the echo path (optional).
+
+# 6 Characteristics of echo cancellers
+
+## 6.1 General
+
+This Recommendation is applicable to the design of echo cancellers (ECs). The echo cancellers are assumed to be "half" echo cancellers, i.e., those in which cancellation takes place only in the send path due to signals present in the receive path. A full echo canceller is possible consisting of two half echo cancellers, with each pointing in the opposite direction.
+
+## 6.2 Purpose, operation and environment
+
+Echo cancellers have the following fundamental requirements:
+
+- 1) rapid convergence;
+- 2) low returned echo level during single talk;
+- 3) low divergence during double talk and cancelled end speech;
+- 4) assured double talk detection and cancelled end speech detection;
+- 5) proper operation during facsimile and low speed ( $< 9.6$ kbit/s) voiceband data transmissions.
+
+Echo cancellers may remain active for several non-voice signals as well, in particular, Group 3 facsimile and low speed ( $< 9.6$ kbit/s) voiceband data transmissions. Tests 10 and 14 address these issues.
+
+If appropriate signalling to disable echo cancellers in tandem is not implemented, then it is possible that echo cancellers can appear in tandem in a connection. Suitable tests for ensuring adequate performance for tandem echo cancellers are currently under study in Test 11. When echo cancellers are located on the subscriber side of the international signalling equipment, signalling tones do not pass through the cancellers so no special action is necessary. When cancellers are on the international side of the signalling equipment, they are normally disabled by the switch during the active signalling exchange intervals in order to prevent distortion of the signalling tones by the echo canceller. When
+
+signalling tones simultaneously appear at the canceller receive and send ports (double talk), the receive signal will be processed through the echo path model contained in the canceller. The signal estimate produced by the canceller may sufficiently distort the send side signal so that it will not be properly recognized by the signalling receive unit (see Note 1).
+
+An echo canceller should be disabled during the transmission of the ITU-T No. 6 and No. 7 continuity check signal (Note 2). If an echo canceller conforming to this Recommendation is located on the international side of a circuit with ITU-T No. 6 or No. 7 signalling and is not externally disabled by the switch, it will not corrupt the return of the continuity check tone only if it is able to pass the optional Test No. 8. Similarly, if an echo canceller conforming to this Recommendation is located on the international side of ITU-T No. 5 signalling units and is not disabled by the switch, it will not corrupt the continuously compelled line signalling exchange only if it is able to pass the optional Test No. 8.
+
+NOTE 1 – For some echo cancellers, this problem may not occur when the send and receive frequencies are different.
+
+NOTE 2 – [ITU-T Q.271] on ITU-T No. 6 and [ITU-T Q.724] on ITU-T No. 7 both include the following statement: "As the presence of active echo suppressors in the circuit would interfere with the continuity check, it is necessary to disable the suppressors during the check and to re-enable them, if required, after the check has been completed." This consideration also applies to echo cancellers.
+
+To improve the subjective performance when conference bridge circuits are in use, it is recommended that each 2-wire network connection to a conference bridge be equipped with a dedicated echo canceller that is oriented away from the bridge, towards the hybrid of the terminating end in order to prevent echo entering the summing node of the conference bridge. In such an arrangement, the talker echo and listener echo (listener hearing multiple copies of distorted talker voice) will be avoided and an EC will not see multiple hybrid reflections, resulting in more natural communication for all users of the bridge.
+
+The following tests address convergence properties of network echo cancellers under various conditions of operation:
+
+- Test No. 2 – Convergence and Steady state residual and returned echo level tests.
+ - Test 2A: Convergence and re-convergence test with NLP enabled.
+ - Test 2B: Convergence and re-convergence test with NLP disabled.
+ - Test 2C: Convergence test in the presence of background noise.
+- Test No. 5 – Infinite return loss convergence test.
+- Test No. 10 – Facsimile test during call establishment phase.
+ - Test 10A: Canceller operation on the calling station side.
+ - Test 10B: Canceller operation on the called station side.
+- Test No. 15 – PCM offset test.
+
+The term "convergence time" is defined in clause 3.7; however it is recognized that a single number for "convergence time" is not sufficient to provide meaningful information regarding overall convergence properties of an echo canceller. If a value of convergence time is specified, the following information should be defined accordingly:
+
+- The hybrid model, ERL, and echo path delay ( $t_d$ ) used for the echo path.
+- The type of test signal used (e.g., CSS, White Gaussian Noise), and the level at the receive-in port.
+- Whether the NLP is enabled or disabled.
+
+- The defined level of returned echo at the send-out port, for which a sustained amount of cancellation is achieved after the convergence time.
+
+NOTE 3 – Although convergence time may be tested with echo path models that include an echo path delay ( $t_d$ ), the value of $t_d$ may be subtracted from the value of convergence time.
+
+## 6.3 External enabling/disabling
+
+Certain digital echo cancellers may be disabled directly by a digital signal (e.g., see Recommendation [b-ITU-T Q.55]). These echo cancellers should provide 64 kbit/s bit sequence integrity (i.e., if integrated, the A-law to $\mu$ -law or $\mu$ -law to A-law conversion will also be disabled) in the externally disabled state.
+
+## 6.4 Tests and requirements for performance with input signals applied to the send and receive paths
+
+### 6.4.1 Transmission performance
+
+The performance characteristics apply, unless otherwise noted, when steady state signals are separately applied to the send and receive paths.
+
+A digital network echo canceller inserted between codecs into a digital transmission path meeting the performance characteristics of [ITU-T G.712] shall not alter performance such that the requirements of [ITU-T G.712] are violated.
+
+The appropriate transmission performance requirements as noted below also apply.
+
+#### 6.4.1.1 Delay
+
+The maximum delay experienced at any frequency in the voiceband in the send path should be kept to a minimum and should not exceed 1 ms. No significant delay should occur in the receive path.
+
+NOTE 1 – The creation of frame slips in the echo path can lead to an occasional degradation of the echo cancellation. If a delay is necessary to synchronize the digital send and receive paths, the global admissible delay on the send path, including the group delay mentioned above, should not exceed 1 ms and on the receive path 250 $\mu$ s.
+
+NOTE 2 – A method to measure one directional delay through an echo canceller is for further study.
+
+#### 6.4.1.2 Measuring input and output levels
+
+For testing purposes, the method defined for measuring the input level of the composite source signals is a RMS method. Unless otherwise specified within a test, the RMS method should also be used for measuring the output levels at $S_{out}$ . Other methods that would give equivalent results are possible (see Annex C). For the RMS method, specifically, CSS is measured using:
+
+$$S(k) = 3.14 + 20 \log \left[ \frac{\sqrt{\frac{2}{n} \sum_{i=k}^{k-n+1} e_i^2}}{4096} \right] \quad (\text{A-law encoding})$$
+
+$$S(k) = 3.17 + 20 \log \left[ \frac{\sqrt{\frac{2}{n} \sum_{i=k}^{k-n+1} e_i^2}}{8159} \right] \quad (\mu\text{-law encoding})$$
+
+where:
+
+$S(k)$ = signal level in dBm0
+
+$e_i$ = linear equivalent of the PCM encoded signal at time $i$
+
+$k$ = discrete time index
+
+$n$ = number of samples over which the RMS measurement is made, and $n = \alpha\tau$ with $\alpha \geq 1$ (an integer) and $\tau$ = period of CSS (5600 for the single-talk portion and 6400 for the double talk portion of CSS)
+
+Some tests in this Recommendation, e.g., Test No. 2, use the RMS value that is measured over the active portion of the CSS (i.e., excluding the pause in the CSS) only. The subscript "act" in a signal level is used to denote the level measurement in this case. For example, if $L_{Rin}$ is the RMS level of $R_{in}$ including the pause, then $L_{Rin,act}$ is the RMS level of $R_{in}$ excluding the pause. The RMS level of the CSS excluding the pause is larger than that including the pause. The difference is 1.49 dB for single talk CSS and 1.66 dB for double talk CSS. In other words, given a CSS signal level $L_x$ in the unit of dBm0, $L_{x,act}$ can be obtained from:
+
+$$L_{x,act} = L_x + 1.49 \text{ dB, for single talk CSS}$$
+
+$$L_{x,act} = L_x + 1.66 \text{ dB, for double talk CSS}$$
+
+Refer to Annex C for the details regarding the single talk CSS and double talk CSS.
+
+##### 6.4.1.2.1 Level measurement device
+
+For some of the tests in this Recommendation, e.g., Test No. 2, it is necessary to measure the short-term level of the signal. This is achieved using the following level measurement device.
+
+The measurement device comprises a frequency-weighting network, a squaring circuit, an exponential filter, and a detector-indicator. This device may use either analogue or digital methods. The impulse response of the frequency-weighting network is listed in Table 1. The table is read in columns. The measurement device will have the characteristics that correspond to the following block diagram.
+
+
+
+```
+
+graph LR
+ A[Frequency weighting] --> B[Squaring circuit]
+ B --> C["35 ms, 1-pole exponential filter"]
+ C --> D[Detector-indicator]
+
+```
+
+G.168(09)\_F6.4.1.2.1
+
+Block diagram of the level measurement device. It consists of four blocks connected in series: 'Frequency weighting', 'Squaring circuit', '35 ms, 1-pole exponential filter', and 'Detector-indicator'. The signal flows from left to right through these blocks. Below the diagram is the text 'G.168(09)\_F6.4.1.2.1'.
+
+This frequency weighting network is used to provide a greater attenuation of the frequencies outside the band of interest that can be achieved by the filters identified in [IEC 61672-1]. This filter is required because of D.C. effects due to the bias induced by A-law encoding. The filter is a 101-element finite impulse response bandpass filter with the impulse response shown in Figure 4 and the frequency response shown in Figure 5. The coefficients of the filter are:
+
+**Table 1 – Coefficients of bandpass filter for level measurement device**
+
+| | | | | | |
+|------------------|---------|------------------|---------|------------------|---------|
+| $f_0, f_{100}$ | 0.0000 | $f_{17}, f_{83}$ | -0.0019 | $f_{34}, f_{66}$ | 0.0092 |
+| $f_1, f_{99}$ | 0.0006 | $f_{18}, f_{82}$ | -0.0033 | $f_{35}, f_{65}$ | 0.0000 |
+| $f_2, f_{98}$ | 0.0005 | $f_{19}, f_{81}$ | -0.0047 | $f_{36}, f_{64}$ | 0.0164 |
+| $f_3, f_{97}$ | 0.0004 | $f_{20}, f_{80}$ | -0.0000 | $f_{37}, f_{63}$ | -0.0210 |
+| $f_4, f_{96}$ | 0.0011 | $f_{21}, f_{79}$ | -0.0068 | $f_{38}, f_{62}$ | 0.0161 |
+| $f_5, f_{95}$ | -0.0000 | $f_{22}, f_{78}$ | 0.0036 | $f_{39}, f_{61}$ | -0.0375 |
+| $f_6, f_{94}$ | 0.0015 | $f_{23}, f_{77}$ | -0.0057 | $f_{40}, f_{60}$ | 0.0000 |
+| $f_7, f_{93}$ | -0.0003 | $f_{24}, f_{76}$ | 0.0054 | $f_{41}, f_{59}$ | -0.0406 |
+| $f_8, f_{92}$ | 0.0012 | $f_{25}, f_{75}$ | 0.0000 | $f_{42}, f_{58}$ | -0.0357 |
+| $f_9, f_{91}$ | -0.0002 | $f_{26}, f_{74}$ | 0.0044 | $f_{43}, f_{57}$ | -0.0267 |
+| $f_{10}, f_{90}$ | 0.0000 | $f_{27}, f_{73}$ | 0.0095 | $f_{44}, f_{56}$ | -0.0871 |
+| $f_{11}, f_{89}$ | 0.0002 | $f_{28}, f_{72}$ | 0.0017 | $f_{45}, f_{55}$ | -0.0000 |
+| $f_{12}, f_{88}$ | -0.0020 | $f_{29}, f_{71}$ | 0.0188 | $f_{46}, f_{54}$ | -0.1420 |
+| $f_{13}, f_{87}$ | 0.0005 | $f_{30}, f_{70}$ | 0.0000 | $f_{47}, f_{53}$ | 0.0289 |
+| $f_{14}, f_{86}$ | -0.0040 | $f_{31}, f_{69}$ | 0.0225 | $f_{48}, f_{52}$ | -0.1843 |
+| $f_{15}, f_{85}$ | 0.0000 | $f_{32}, f_{68}$ | 0.0024 | $f_{49}, f_{51}$ | 0.0475 |
+| $f_{16}, f_{84}$ | -0.0047 | $f_{33}, f_{67}$ | 0.0163 | $f_{50}$ | 0.8006 |
+
+
+
+Figure 4 – Impulse response of frequency weighting network. The graph shows the coefficient value (Y-axis, ranging from -0.2 to 1.2) versus time (X-axis, ranging from 0 to 120). The response is near zero until approximately x=40, where it exhibits a sharp, high-amplitude spike reaching about 0.8, followed by a rapid decay and small oscillations around zero. A label 'G.168(09)\_F04' is present in the bottom right corner.
+
+**Figure 4 – Impulse response of frequency weighting network**
+
+
+
+Figure 5: Magnitude response of frequency weighting network. The graph shows Gain (dB) on the y-axis (from -80 to 10) versus Frequency (Hz) on the x-axis (from 0 to 4000). The curve starts at -80 dB at 0 Hz, rises sharply to 0 dB at 500 Hz, remains flat at 0 dB until approximately 3400 Hz, and then drops sharply to -80 dB at 4000 Hz. There are several small ripples in the passband and stopband regions. A label 'G.168(09)\_F05' is visible in the bottom right corner of the plot area.
+
+**Figure 5 – Magnitude response of frequency weighting network**
+
+The magnitude response given in Figure 5 was generated using the following equation:
+
+$$|H(\omega)| = 10 \log_{10} \left( \sum_{n=0}^{100} h_n e^{-j\omega n} \right)^2 \text{ [dB]}, \quad 0 < \omega < \pi$$
+
+and the frequency in the x-axis is formed by:
+
+$$f = \frac{\omega}{\pi} 4000 \text{ Hz}$$
+
+##### 6.4.1.2.2 Level measurement device for peaks
+
+For tests that have requirements on the peaks at $S_{out}$ , the measurement method used is a 35 ms rectangular sliding window in place of the 35 ms one-pole exponential filter of clause 6.4.1.2.1.
+
+### 6.4.2 Echo canceller performance
+
+The performance requirements that follow are for echo cancellers that include NLPs.
+
+For testing purposes, it is required that the NLP can be disabled, that the echo path impulse response store (H register) can be reset (set to zero) and that adaptation can be inhibited.
+
+The tests in this Recommendation require a bearer signal interface and a control signal interface to the echo canceller under test as depicted in Figure 6.
+
+The bearer signal interface is for the four-port access to signals, $R_{in}$ , $R_{out}$ , $S_{in}$ , and $S_{out}$ . The digital signals are coded in [ITU-T G.711] $\mu$ -law/A-law at a bit rate of 64 kbit/s and are usually carried over T1/E1 links. If the echo canceller under test does not support T1/E1 links for bearer signals, some interconnection equipment should be provided to make the echo canceller under test accessible by the testing unit through an appropriate interface.
+
+The control signal interface is for echo canceller control functions such as reset H register and enabling/disabling adaptation. The network echo canceller should be able to be controlled by a control link in such a way that the H register of the echo canceller can be reset or the adaptation inhibited/enabled at the right time synchronized with the test signals according to the specifications defined in the test requirements. The interface to the control link shall be well documented and provide for ease of implementation. Two examples of a control interface are given in Appendix VI.
+
+The requirements are described in terms of tests made by applying signals to $R_{in}$ and $S_{in}$ of an echo canceller, and measuring the $S_{out}$ signals. The test set-up is as shown in Figures 6 and 7. The ports are assumed to be at equal relative level points. For all values of $R_{in}$ , and for all tests in this Recommendation, the level at $R_{out}$ should be equal to the level at $R_{in}$ . Any optional processing included in the echo canceller which may affect level transparency between $R_{in}$ and $R_{out}$ should be disabled during all tests in this Recommendation. The composite source signals, which consist of the receive-input test signal and send-input test signal (see Annex C and [ITU-T P.501]) are used as the test signals, unless otherwise indicated.
+
+For multiple channel implementations, including implementations where other signal processing functions may share common processing resources, sufficient resources shall be provided for each channel of echo cancellation to meet the requirements of this Recommendation. Tests to ensure that the implementation fulfils this requirement are for further study. When performing the tests described in this Recommendation, for enhanced repeatability, all channels not being tested should have idle code (e.g., 01111111 for 1544 kbit/s systems or 01010100 for 2048 kbit/s systems as outlined in Recommendation ITU-T Q.522) applied to the inputs. It is generally recognized that some operators may wish to apply simulated traffic loading to the untested channels. This type of channel loading is for further study.
+
+The ERL used in these tests have a minimum value of 6 dB. It should be noted that 6 dB is a typical worst-case value encountered for most networks, and most current networks have typical ERL values better than this.
+
+Also, it should be noted that the test configurations specified in this Recommendation are artificial for purposes of test and result repeatability, and do not fully represent all conditions that would be expected in real networks.
+
+The requirements in clause 6.4.2 are based on the use of the composite source signals, noise, tones, FAX signals, and voiceband data signals as the test signals.
+
+Two echo path models should be used for the tests in this Recommendation (as denoted in Figures 6 and 7). With the exception of Test No. 13, the tests in this Recommendation do not address performance requirements for echo cancellers when the echo path manifests non-linearities beyond the ones incurred in the course of ITU-T G.711/ITU-T G.712 companding as shown in Figures 6 and 7.
+
+Comfort noise should be disabled unless otherwise indicated.
+
+
+
+This functional diagram illustrates the setup for echo canceller performance measurements. A signal generator N provides an input signal $S_{gen}$ to a Summer. The Summer also receives inputs from three parallel echo path models: ERL A, ERL B, and ERL C. Each ERL block is preceded by an 'Echo path delay' block (A, B, and C respectively). The output of the Summer is converted by a G.711/G.712 A/D converter to produce $S_{in}$ , which is fed into the Echo canceller. The Echo canceller produces an output $S_{out}$ measured by a 'Measurement device (analogue or digital)'. A feedback loop exists where the Echo canceller's output $R_{out}$ is converted by a G.711/G.712 D/A converter and fed back into the 'Echo path delay' blocks. The Echo canceller also has control inputs: 'H register to zero (reset)', 'Inhibit convergence', and 'Disable non-linear processing'. A separate 'Signal generator' is connected to a G.711/G.712 A/D converter, which provides an input $R_{in}$ to the Echo canceller. A dashed box encloses the Summer, the three echo path models, and the D/A converter.
+
+Functional diagram for echo canceller performance measurements (Figure 6).
+
+G.168(09)\_F06
+
+NOTE – The sum of the absolute values of the gains $G_A$ , $G_B$ , $G_C$ that correspond to ERL A, B, C, respectively, taken in dB, should be less than or equal to $-6$ dB (i.e., $20\log(|G_A| + |G_B| + |G_C|) \leq -6$ dB), and echo path delay $A \leq \Delta$ ms, echo path delay $B \leq \Delta$ ms, and echo path delay $C \leq \Delta$ ms.
+
+**Figure 6 – Functional diagram for echo canceller performance measurements**
+
+An echo path model which allows more realistic end paths to be modelled can be realized by replacing the dotted box in Figure 6 with Figure 7. The characteristics of the end path, which include A to $\mu$ law converters, can be modelled as an impulse response $g(k)$ .
+
+
+
+This diagram shows an alternative echo path model. An input signal $S_{gen}$ enters a G.711/G.712 A/D converter. The output is then processed by an A/ $\mu$ PCM converter. The output of this converter is summed with the output of a block labeled $g(k)$ at a summing junction. The result is then processed by a PCM A/ $\mu$ converter to produce the final output $S_{in}$ . A feedback loop exists where the input $R_{out}$ is processed by a PCM A/ $\mu$ converter and fed into the $g(k)$ block. A dashed box encloses the A/D converter, the A/ $\mu$ PCM converter, the summing junction, the $g(k)$ block, and the PCM A/ $\mu$ converter.
+
+Echo path model using g(k) (Figure 7).
+
+G.168(09)\_F07
+
+**Figure 7 – Echo path model using $g(k)$**
+
+The primary purpose of an echo canceller is to control the echo of a speech signal. This is done by synthesizing a replica of the echo path impulse response and using it to generate an estimate of the echo which is subtracted from the actual circuit echo. The synthesis should be accomplished using a speech input signal. Because of the difficulty of defining a speech test signal, the following tests are type tests and rely upon the use of a composite source signal primarily for convenience and repeatability. These tests should be performed on an echo canceller only after the design has been
+
+shown to properly synthesize a replica of the echo path impulse response from a speech input signal and its corresponding echo. Speech signals are not used in the tests in this clause. Additionally, the NLP in the echo canceller should be designed to minimize and potentially avoid undesirable effects such as double talk clipping, gaps in transmitted speech signals, and noise contrast (see Test 9 described later in this Recommendation for noise contrast, and see Appendix I for further discussion on double talk clipping).
+
+Different echo cancellers may be designed to work satisfactorily for different echo path delays depending on their application in various networks. Thus $\Delta$ , whenever it appears in this Recommendation, represents the maximum echo path delay for which the echo canceller is designed.
+
+In some cases, a delay is present between the test equipment and echo canceller at the non-cancelled end side. This delay occurs for example if the echo canceller under test can interface only a packet network (such as an IP network) at the non-cancelled end side and is the consequence of packetization, etc. This Recommendation primarily addresses echo cancellers that have 64 kbit/s digital interfaces on both sides of the canceller (see Figure 1). However, if the Recommendation is used to test echo cancellers deployed in gateway devices that interface with packet networks, then any such additional delay should be taken into account by appropriately shifting the test requirements in time.
+
+See Appendix IV for some guidelines on the use of parameters for testing echo cancellers.
+
+#### 6.4.2.1 Echo path models for $g(k)$
+
+See Annex D for the echo path models that may be used as the $g(k)$ in Figure 7 for the tests in this Recommendation. This does not represent an exhaustive set, and other models may be used provided that they meet the echo path requirements for each individual test. Note that the digital version of Figure 6 where three echo path reflection points are present may also be represented by a $g(k)$ . A specific model including this is not described in Annex D. A more complex model that includes realistic dispersion and other effects is for further study. See also Appendix III for additional information.
+
+To ensure that the magnitude response of the echo path $g(k)$ does not exceed 0 dB over the frequency range of some of the models contained in Annex D, the minimum ERL values must be greater than 6 dB. See Annex D for the exact minimum ERL value for each model. Note that the minimum ERL values provided in Annex D overrule the requirement of $ERL \geq 6$ dB given in the following tests if there is a conflict between the two.
+
+#### 6.4.2.2 Test No. 1 – Steady state residual and returned echo level test (deleted)
+
+This test has been incorporated into Test 2.
+
+#### 6.4.2.3 Test No. 2 – Convergence and steady state residual and returned echo level tests
+
+This test is meant to ensure that the echo canceller converges rapidly for all combinations of input signal levels, echo paths, and certain echo path changes (but not including continuously varying echo paths)1 , and that the returned echo level is sufficiently low. This test is also meant to ensure that the steady state cancellation ( $A_{CANC}$ ) is sufficient to produce a residual echo level which is sufficiently low to permit the use of non-linear processing without undue reliance on it. In general, given that all other variables are equal, a higher value of ERLE or lower values of $L_{RES}$ will allow for less dependence on the NLP functionality.
+
+---
+
+1 Convergence requirements for continuously changing echo path impulse responses (non-abrupt change tracking of the echo path impulse response) are not covered by this Recommendation.
+
+At the beginning of a call, the convergence should be fast enough to be subjectively unnoticeable. In general, the convergence should be fast enough to handle changes in the echo path in a subjectively transparent fashion. Faster convergence than required in Figures 10 and 12 is desirable, but only if no degradation is observed during single or double talk and the stability of the canceller can be maintained in all network conditions (e.g., various echo path conditions, including various hybrids) and for all voiceband signals.
+
+In Tests 2A-2C, the level at $R_{in}$ is $L_{Rin,act}$ . It is the signal level measure using the RMS method over the active portion of the CSS only (i.e., excluding the pause of the CSS) as described in clause 6.4.1.2.
+
+
+
+Figure 8 consists of two parts, (a) and (b), illustrating signal and time relationships for Test No. 2A/2B.
+
+**a) Part A:** This diagram shows the signal $R_{in}$ (top line) with two bursts of activity. Below it, the 'Adaptation' signal is shown as a solid line that goes high at least 200 ms before the start of the first burst. The 'Inhibit' signal is a dashed line that is low during the bursts. The 'Enable' signal is a dashed line that is high during the bursts. A vertical dashed line labeled $t_0$ marks the start of the 'Measurement' period, which begins after the first burst.
+
+**b) Part B:** This diagram shows the signal $R_{in}$ (top line) with four bursts of activity. Below it, the 'Echo path model A' signal is shown as a solid line that is high during the first two bursts and low during the last two. The 'ERL A' signal is a solid line that is high during the first two bursts and low during the last two. The 'Pure delay A' signal is a solid line that is high during the first two bursts and low during the last two. The 'Adaptation' signal is a solid line that goes high at least 200 ms before the start of the first burst. The 'Inhibit' signal is a dashed line that is low during the bursts. The 'Enable' signal is a dashed line that is high during the bursts. The diagram is divided into three phases: 'Phase I' (Initially converged state), 'Path change (model, ERL, pure delay)' (the transition between Phase I and Phase II), and 'Phase II' (Re-convergence measurement). A vertical dashed line labeled $t_0$ marks the start of the 'Re-convergence measurement' period, which begins after the third burst.
+
+Figure 8: Signal and time relationships for Test No. 2A/2B. Part A shows the signal R\_in, Adaptation, Inhibit, and Enable lines. Part B shows the signal R\_in, Echo path model A, ERL A, Pure delay A, Adaptation, Inhibit, Enable, Initially converged state, Path change (model, ERL, pure delay), and Re-convergence measurement lines.
+
+Figure 8 – Signal and time relationships for Test No. 2A/2B
+
+##### 6.4.2.3.1 Test 2A: Convergence and re-convergence test with NLP enabled
+
+###### a) Convergence test with NLP enabled
+
+###### Requirement
+
+With the H register initially reset, or alternatively, with an open echo path resulting in $S_{in} = 0$ and the H register content converged to 0, and the NLP enabled, for all values $L_{Rin,act} \geq -30$ dBm0 and $\leq 0$ dBm0 and for all values of ERL $\geq 6$ dB and echo path delay, $t_d \leq \Delta$ ms, the combined loss ( $L_{Rin,act} - L_{RET}$ ) should be greater than or equal to that shown in Figure 10a. After $1 + t_d + t_0$ s, the combined loss should be greater than or equal to that in Figure 9. The level at $S_{out}$ is measured using a meter conforming to the characteristics of clause 6.4.1.2.1. In addition, no peaks (see clause 6.4.1.2.2) are allowed that exceed 5 dB above the requirements in Figure 9.
+
+Adaptation is enabled at least 200 ms before the start of a CSS burst (see Figure 8a). This period is to allow for the latency time in the adaptation control of the canceller. The residual or returned echo
+
+level is then measured as a function of time to reveal the convergence and steady-state properties of the echo canceller.
+
+The variable $L_{\text{Rin,act}} - L_{\text{RET}}$ in Figure 10a may be replaced by the variable $L_{\text{Sin}} - L_{\text{Sout}} + \text{ERL}$ , where $L_{\text{Sin}}$ and $L_{\text{Sout}}$ are the levels of $S_{\text{in}}$ and $S_{\text{out}}$ respectively. The signal levels $L_{\text{Sin}}$ and $L_{\text{Sout}}$ are measured using the measurement device in clause 6.4.1.2.1, and should be synchronized. The ERL is the value chosen in the test. This method may also be used to observe convergence as a continuous plot over time.
+
+NOTE – The method stated in the preceding paragraph takes into account any dispersion in the echo path, but does not take into account any dispersion present between the $S_{\text{in}}$ and $S_{\text{out}}$ ports of the echo canceller.
+
+
+
+| $L_{\text{Rin,act}}$ (dBm0) | $L_{\text{RET}}$ (dBm0) |
+|-----------------------------|-------------------------|
+| -30 | -65 |
+| -20 | -65 |
+| -10 | -65 |
+| 0 | -55 |
+
+Figure 9: Relationship between receive input level (L\_Rin,act) and return echo level (L\_RET) with NLP enabled. The graph shows a piecewise linear relationship. The x-axis is L\_Rin,act (dBm0) from -30 to 0. The y-axis is L\_RET (dBm0) from -70 to -50. The curve is constant at -65 dBm0 for L\_Rin,act from -30 to -10 dBm0, and then increases linearly to -55 dBm0 at 0 dBm0. A label G.168(09)\_F09 is in the bottom right corner.
+
+**Figure 9 – Relationship between receive input level ( $L_{\text{Rin,act}}$ ) and return echo level ( $L_{\text{RET}}$ ) with NLP enabled**
+
+The requirements in Figure 9 may not be met with echo cancellers containing a comfort noise feature, if enabled, and so, for the purposes of this test, comfort noise is disabled. For $R_{\text{in}}$ signal levels exceeding $-5$ dBm0, CSS will be clipped. This does not, however, imply that the requirements of Figures 9 and 10 need not be met at $R_{\text{in}}$ levels of $-5$ dBm0 or above. For this range, special care should be taken to ensure that the echo path is linear. Non-linearities in the real network may result in performance less than indicated in the figure.
+
+
+
+Figure 10a: Convergence characteristics with NLP enabled. A graph showing the combined loss (L\_Rin,act - L\_RET) in dB over time. The y-axis has values 6, 20, and (a). The x-axis has time markers: t\_0, 50ms + t\_d + t\_0, 1 s + t\_d + t\_0, 3 mins + t\_0, and a reference G.168(15)\_F10. The graph shows a constant level of 6 dB from t\_0 to 50ms + t\_d + t\_0, a linear increase to 20 dB at 1 s + t\_d + t\_0, and a constant level of 20 dB (labeled 'Steady state') from 1 s + t\_d + t\_0 to 3 mins + t\_0. A dashed line extends from (a) on the y-axis to the start of the steady state.
+
+(a) As derived from Figure 9.
+
+**Figure 10a – Convergence characteristics with NLP enabled**
+
+###### **b) Re-convergence test with NLP enabled**
+
+##### **Requirement**
+
+With the H register initially converged to any echo path, at time $t_0$ the echo path is changed to any other different echo path (which includes echo path model change and/or ERL change (up or down) and/or pure delay change (up or down)). The adaptation enable/inhibit control should remain enabled throughout the test. For all values $L_{Rin,act} \geq -30$ dBm0 and $\leq 0$ dBm0 and for all values of ERL $\geq 6$ dB and echo path delay, $t_d \leq \Delta$ ms (for both echo path models), the combined loss ( $L_{Rin,act} - L_{RET}$ ) should be greater than or equal to that shown in Figure 10b. That is, the return echo level ( $L_{RET}$ ) after $1 + t_d + t_0$ s, should be lower than or equal to that shown in Figure 9. The level at $S_{out}$ is measured using a meter conforming to the characteristics of clause 6.4.1.2.1. In addition, during steady state, no peaks (see clause 6.4.1.2.2) are allowed that exceed 5 dB above the requirements in Figure 9. The NLP should be enabled for this test.
+
+With the following terminology regarding characteristics of Phases I and II (see Figure 8b):
+
+- Phase I: $ERL_A$ , echo path model A (in short, $hybrid_A$ ), pure delay A (in short, $delay_A$ )
+- Phase II: $ERL_B = ERL_A - \Delta ERL$ [dB], $hybrid_B$ , $delay_B$ ,
+
+it is recommended that, at minimum, the following combinations be tested:
+
+- $hybrid_B \neq hybrid_A$ and $ERL_B = ERL_A$ , with $delay_B = delay_A$
+- $hybrid_B = hybrid_A$ and $ERL_B < ERL_A$ ( $\Delta ERL = 10$ dB or greater), with $delay_B = delay_A$
+- $hybrid_B \neq hybrid_A$ and $ERL_B < ERL_A$ ( $\Delta ERL = 10$ dB or greater), with $delay_B = delay_A$
+
+For Phase II, it is recommended that, at minimum, the models which have the longest dispersion time, i.e., models $m_4$ , $m_6$ , $m_7$ and $m_8$ and the largest pure delay, model $m_6$ , be used.
+
+
+
+Figure 10b: Re-convergence characteristics with NLP enabled. A graph showing the loss L\_Rin,act - L\_RET (dB) on the y-axis against time on the x-axis. The x-axis has markers for t\_0, 1 s + t\_d + t\_0, and 3 mins + t\_0. A horizontal dashed line at level (a) is shown. The region from t\_0 to 1 s + t\_d + t\_0 is labeled 'No requirement'. The region from 1 s + t\_d + t\_0 to 3 mins + t\_0 is shaded gray and labeled 'Steady state'.
+
+(a) As derived from Figure 9
+
+G.168(15)\_F10b
+
+**Figure 10b – Re-convergence characteristics with NLP enabled**
+
+##### 6.4.2.3.2 Test 2B: Convergence and re-convergence test with NLP disabled
+
+###### a) Convergence test with NLP disabled
+
+###### Requirement
+
+With the H register initially reset, or alternatively, with an open echo path resulting in $S_{in} = 0$ , and the H register content converged to 0, and the NLP disabled, for all values $L_{Rin,act} \geq -30$ dBm0 and $\leq 0$ dBm0 and for all values of ERL $\geq 6$ dB and echo path delay, $t_d \leq \Delta$ ms, the loss $L_{Rin,act} - L_{RES}$ should be greater than or equal to that shown in Figure 12a. After $10 + t_d + t_0$ s, the loss ( $L_{Rin,act} - L_{RES}$ ) should be greater than or equal to that in Figure 11. The level at $S_{out}$ is measured using a meter conforming to the characteristics of clause 6.4.1.2.1. In addition, no peaks (see clause 6.4.1.2.2) are allowed that exceed 5 dB above the requirements in Figure 11.
+
+Adaptation is enabled at least 200 ms before the start of a CSS burst (see Figure 8a). This period is to allow for the latency time in the adaptation control of the canceller. The residual or returned echo level is then measured as a function of time to reveal the convergence and steady-state properties of the echo canceller.
+
+The variable $L_{Rin,act} - L_{RES}$ in Figure 12a may be replaced by the variable $L_{Sin} - L_{Sout} + ERL$ , where $L_{Sin}$ and $L_{Sout}$ are the levels of $S_{in}$ and $S_{out}$ respectively. The signal levels $L_{Sin}$ and $L_{Sout}$ are measured using the measurement device in clause 6.4.1.2.1, and should be synchronized. The ERL is the value chosen in the test. This method may also be used to observe convergence as a continuous plot over time.
+
+NOTE 1 – The method stated in the preceding paragraph takes into account any dispersion in the echo path, but does not take into account any dispersion present between the $S_{in}$ and $S_{out}$ ports of the echo canceller.
+
+NOTE 2 – Some echo cancellers employ a supplementary NLP function which cannot be disabled. For information covering this case, see clause 8.2.6, Testing of NLPs.
+
+
+
+A line graph showing the relationship between receive input level ( $L_{\text{Rin,act}}$ ) on the x-axis and residual echo level ( $L_{\text{RES}}$ ) on the y-axis, both in dBm0. The x-axis ranges from -30 to 0 with major ticks every 10 units. The y-axis ranges from -55 to -30 with major ticks every 5 units. A solid diagonal line starts at (-30, -55) and ends at (0, -30). Dashed horizontal and vertical grid lines are present at -20, -10, and -40 dBm0.
+
+Figure 11: Relationship between receive input level (L\_Rin,act) and residual echo level (L\_RES) with NLP disabled. The graph shows a linear relationship from (-30, -55) to (0, -30).
+
+**Figure 11 – Relationship between receive input level ( $L_{\text{Rin,act}}$ ) and residual echo level ( $L_{\text{RES}}$ ) with NLP disabled**
+
+
+
+A graph showing the loss $L_{\text{Rin,act}} - L_{\text{RES}}$ (dB) on the y-axis against time on the x-axis. The y-axis has labels at 6 and 20 dB. The x-axis has time markers: $t_0$ , $50 \text{ ms} + t_d + t_0$ , $1 \text{ s} + t_d + t_0$ , $10 \text{ s} + t_d + t_0$ , and $3 \text{ mins} + t_0$ . The graph shows a piecewise linear increase in loss: it starts at 6 dB at $t_0$ , remains constant until $50 \text{ ms} + t_d + t_0$ , then increases linearly to 20 dB at $1 \text{ s} + t_d + t_0$ , and remains constant at 20 dB until $10 \text{ s} + t_d + t_0$ . After $10 \text{ s} + t_d + t_0$ , the loss increases further, reaching a higher constant value labeled 'Steady state' at $3 \text{ mins} + t_0$ . Dashed vertical lines mark the time intervals.
+
+Figure 12a: Convergence characteristics with NLP disabled. The graph shows the loss L\_Rin,act - L\_RES (dB) over time, starting at 6 dB, rising to 20 dB, and then entering a steady state.
+
+(a) As derived from Figure 11
+
+G.168(15)\_F12a
+
+**Figure 12a – Convergence characteristics with NLP disabled**
+
+###### **b) Re-convergence test with NLP disabled**
+
+###### **Requirement**
+
+With the H register initially converged to any echo path, at time $t_0$ the echo path is changed to any other different echo path (which includes echo path model change and/or ERL change (up or down) and/or pure delay change (up or down)). The adaptation enable/inhibit control should remain enabled throughout the test. For all values $L_{\text{Rin,act}} \geq -30 \text{ dBm0}$ and $\leq 0 \text{ dBm0}$ and for all values of ERL $\geq 6 \text{ dB}$ and echo path delay, $t_d \leq \Delta \text{ ms}$ (for both echo path models), the loss $L_{\text{Rin,act}} - L_{\text{RES}}$ should be greater than or equal to that shown in Figure 12b. That is, the loss $L_{\text{Rin,act}} - L_{\text{RES}}$ after $1 + t_d + t_0 \text{ s}$ , should be greater than or equal to 20 dB. After $10 + t_d + t_0 \text{ s}$ the loss $L_{\text{Rin,act}} - L_{\text{RES}}$ should be greater than or equal to that derived from Figure 11. The level at $S_{\text{out}}$ is measured using a meter conforming to the characteristics of clause 6.4.1.2.1. In addition, during steady state, no peaks (see clause 6.4.1.2.2) are
+
+allowed that exceed 5 dB above the requirements in Figure 11. The NLP should be disabled for this test.
+
+With the following terminology regarding characteristics of Phases I and II (see Figure 8b):
+
+- Phase I: $ERL_A$ , echo path model A (in short, $hybrid_A$ ), pure delay A (in short, $delay_A$ )
+- Phase II: $ERL_B = ERL_A - \Delta ERL$ [dB], $hybrid_B$ , $delay_B$ ,
+
+it is recommended that, at minimum, the following combinations be tested:
+
+- $hybrid_B \neq hybrid_A$ and $ERL_B = ERL_A$ , with $delay_B = delay_A$
+- $hybrid_B = hybrid_A$ and $ERL_B < ERL_A$ ( $\Delta ERL = 10$ dB or greater), with $delay_B = delay_A$
+- $hybrid_B \neq hybrid_A$ and $ERL_B < ERL_A$ ( $\Delta ERL = 10$ dB or greater), with $delay_B = delay_A$
+
+For Phase II, it is recommended that, at minimum, the models which have the longest dispersion time, i.e., models $m_4$ , $m_6$ , $m_7$ and $m_8$ and the largest pure delay, model $m_6$ , be used.
+
+
+
+(a) As derived from Figure 11
+
+G.168(15)\_F12b
+
+Figure 12b: Re-convergence characteristics with NLP disabled. The graph plots L\_Rin,act - L\_RES (dB) on the y-axis against time on the x-axis. The y-axis has a value of 20 dB marked. The x-axis has time points t\_0, 1 s + t\_d + t\_0, 10 s + t\_d + t\_0, and 3 mins + t\_0. A horizontal dashed line at 20 dB extends from t\_0 to 1 s + t\_d. A vertical dashed line is at 1 s + t\_d. A shaded region labeled 'No requirement' is between t\_0 and 1 s + t\_d. A shaded region labeled 'Steady state' starts at 1 s + t\_d and continues to the right. A horizontal dashed line at 20 dB continues from 1 s + t\_d to 10 s + t\_d. A vertical dashed line is at 10 s + t\_d. A shaded region starts at 10 s + t\_d and continues to the right.
+
+**Figure 12b – Re-convergence characteristics with NLP disabled**
+
+NOTE – Test 5B (Re-convergence during call transfer test) and Test 12 (Residual acoustic echo test) have similarities to Test 2B-b. However, Test 5B is specifically designed to exercise real-world scenarios where significant ERL changes are presented to the network during call transfers.
+
+##### 6.4.2.3.3 Test 2C: Convergence test in the presence of background noise
+
+Test No. 2C is meant to ensure that the steady state cancellation is sufficient to produce an echo level that is sufficiently low and that the echo canceller converges rapidly for all combinations of input signal levels and echo paths in the presence of background noise.
+
+The test procedure is to reset the H register and inhibit adaptation. A Hoth noise source (see [ITU-T P.800]) with level $L_{Sgen}$ is applied as the signal $S_{gen}$ . Adaptation is enabled at least 200 ms before the start of a CSS burst (see Figure 13). After the adaptation interval, inhibit adaptation, remove $S_{gen}$ and measure the residual echo level.
+
+The level at $S_{out}$ is measured using a meter conforming to the characteristics of clause 6.4.1.2.1.
+
+The variable $L_{Rin,act} - L_{RES}$ in Figure 16 may be replaced by the variable $L_{Sin} - L_{Sout} + ERL$ , where $L_{Sin}$ and $L_{Sout}$ are the levels of $S_{in}$ and $S_{out}$ respectively. The signal levels $L_{Sin}$ and $L_{Sout}$ are measured using the measurement device in clause 6.4.1.2.1, and should be synchronized. The ERL is the value chosen in the test. This method may also be used to observe convergence as a continuous plot over time.
+
+NOTE 1 – The method stated in the preceding paragraph takes into account any dispersion in the echo path, but does not take into account any dispersion present between the $S_{in}$ and $S_{out}$ ports of the echo canceller.
+
+
+
+Figure 13: Test No. 2C signal and time relationships. The diagram shows four signal lines over time. R\_in starts with yellow blocks, then has a gap, then another yellow block. S\_gen is a step function that goes high at t\_0 and low at R\_in OFF. Adaptation Inhibit Enable is high from t\_0 to R\_in OFF, then low. A horizontal double-headed arrow labeled 'Adaptation interval (t\_a)' spans from t\_0 to R\_in OFF. A time interval τ = max(t\_d, 150) ms is shown between R\_in OFF and R\_in ON. A 200 ms waiting period is shown between R\_in ON and the start of the 'Measurement' phase. A ≥ 200 ms interval is shown before t\_0. The diagram is labeled G.168(09)\_F13.
+
+**Figure 13 – Test No. 2C signal and time relationships**
+
+NOTE 2 – At the end of this test, a time period of $\geq 1$ s is allowed for possible latency in the adaptation inhibit command. $R_{in}$ is switched off to prevent further adaptation before the inhibit command is effective. A time period of $\tau = \max(t_d, 150)$ ms is allowed before the adaptation inhibit command to clear the impulse response of an echo path. $R_{in}$ is switched on again to perform the measurement. The 200 ms waiting time before measurement is not needed, if the contents of the bandpass filter and exponential filter in the measurement device are set to zero (flushed) before any measurement is performed.
+
+###### **a) Convergence test with NLP enabled**
+
+###### **Requirement**
+
+With the H register initially reset and the NLP enabled, for all values of $L_{Rin,act} \geq -30$ dBm0 and $\leq 0$ dBm0, $L_{Sgen} = L_{Rin,act} - 15$ dB but no higher than $-30$ dBm0, ERL $\geq 6$ dB and echo path delay, $t_d \leq \Delta$ ms, convergence should occur within 1.0 s ( $t_a$ ) and $L_{RET}$ should be $\leq L_{Sgen}$ (see Figure 14).
+
+
+
+Figure 14: Test No. 2C requirements NLP enabled. This is a line graph showing L\_RET (dBm0) on the y-axis versus L\_Rin,act (dBm0) on the x-axis. The y-axis ranges from -55 to -30 in increments of 5. The x-axis ranges from -30 to 0 in increments of 10. A solid line starts at (-30, -45) and increases linearly to (-15, -30), then remains constant at -30 dBm0 for higher L\_Rin,act values. The text 'After 1.0 s' is placed near the start of the line. The diagram is labeled G.168(09)\_F14.
+
+**Figure 14 – Test No. 2C requirements NLP enabled**
+
+###### b) Steady state cancellation test with NLP disabled
+
+###### Requirement
+
+With the H register initially reset and the NLP disabled, for all values of $L_{Rin,act} \geq -30$ dBm0 and $\leq 0$ dBm0, $L_{Sgen}$ as given in Figure 15, ERL $\geq 6$ dB, echo path delay $t_d \leq \Delta$ ms, and adaptation interval $t_a \geq 10$ s, $L_{RES}$ should be less than that shown in Figure 15 for the corresponding value of $L_{Sgen}$ .
+
+
+
+The graph shows the relationship between $L_{RES}$ (dBm0) on the y-axis and $L_{Rin,act}$ (dBm0) on the x-axis. The y-axis ranges from -55 to -25 dBm0, and the x-axis ranges from -30 to 0 dBm0. Three lines are plotted: $L_{Sgen} = L_{Rin,act} - 15$ dB, $L_{Sgen} = -30$ dBm0, and $L_{Sgen} = -55$ dBm0. The lines represent the maximum allowed $L_{RES}$ values for different $S_{gen}$ signal levels. The graph is labeled G.168(09)\_F15.
+
+Figure 15: Test No. 2C steady state requirements NLP disabled. A graph showing L\_RES (dBm0) on the y-axis versus L\_Rin,act (dBm0) on the x-axis. The y-axis ranges from -55 to -25 dBm0, and the x-axis ranges from -30 to 0 dBm0. Three lines are plotted: L\_Sgen = L\_Rin,act - 15 dB, L\_Sgen = -30 dBm0, and L\_Sgen = -55 dBm0. The lines represent the maximum allowed L\_RES values for different S\_gen signal levels. The graph is labeled G.168(09)\_F15.
+
+Figure 15 – Test No. 2C steady state requirements NLP disabled
+
+###### c) Convergence test with NLP disabled
+
+This test differs from parts (a) and (b) above, in that adaptation is not inhibited during the test, the noise applied as the $S_{gen}$ signal is not discontinued during the test and, once started, CSS is applied continuously at $R_{in}$ throughout the test.
+
+##### Requirement
+
+With the H register initially reset and the NLP disabled, for all values of $L_{Rin,act} \geq -30$ dBm0 and $\leq 0$ dBm0, $L_{Sgen} = L_{Rin,act} - 15$ dB but no higher than $-30$ dBm0, ERL $\geq 6$ dB and echo path delay $t_d \leq \Delta$ ms, the loss $L_{Rin,act} - L_{RES}$ within an adaptation interval of $t_a = 10$ s should be greater than or equal to that shown in Figure 16. The value X is given below:
+
+$$X = (L_{Rin,act} - L_{Sgen}) - 6 \text{ dB, for } X \leq 17 \text{ dB}$$
+
+$$X = 17 \text{ dB, otherwise}$$
+
+NOTE 1 – The method used to measure the noise in this test, results in fluctuating levels and can result in difficulty when performing this test.
+
+NOTE 2 – In this case, $L_{RES}$ contains the noise component, $L_{Sgen}$ .
+
+NOTE 3 – The requirement of $L_{Rin,act} - L_{RES}$ in Figure 16 is 5 dB from $t_0$ to $50 \text{ ms} + t_d + t_0$ although the minimum ERL is 6 dB. This is to accommodate the presence of background noise at $S_{in}$ because the background noise increases the fluctuations and consequently the value of $L_{RES}$ .
+
+
+
+Figure 16: A graph showing the convergence requirements for Test No. 2C with NLP disabled. The y-axis is labeled L\_Rin,act - L\_RES (dB) and has a value of 5 at the start and a target value X. The x-axis shows time intervals: t\_0, 50 ms + t\_d + t\_0, 1 s + t\_d + t\_0, and 10 s + t\_d + t\_0. The graph shows a constant value of 5 dB until 50 ms + t\_d + t\_0, then a linear increase to X dB at 1 s + t\_d + t\_0, and finally a constant value of X dB until 10 s + t\_d + t\_0. The label G.168(09)\_F16 is in the bottom right corner.
+
+**Figure 16 – Test No. 2C Convergence requirements NLP disabled**
+
+#### 6.4.2.4 Test No. 3 – Performance under conditions of double talk
+
+The three parts of this test are meant to test the performance of the canceller under various conditions of double talk. During conditions of double talk, the echo canceller can give rise to unwanted artefacts such as clipping, distortion, and noise contrast (see Appendix I). The tests make the assumption that, upon detection of double talk, measures are taken to prevent or slow adaptation in order to avoid excessive reduction in cancellation.
+
+For this test, the $R_{in}$ signal is CSS and the $S_{gen}$ signal is the double talk CSS. While CSS is used for this test, it is recognized that it is only a statistical approximation of real speech. Double talk tests performed with actual speech samples may produce results somewhat different than those shown in this test. This test is intended to provide a guideline on how the double talk performance of an echo canceller should be measured. It is possible that this test and its requirements may change as the correlation between CSS and real speech is better understood. Use of different languages has been shown to provide considerable variation in the results for tests 3A and 3B (see [b-ITU-T GSTP.CSS] in clause I.8 for more details).
+
+See clause I.7.4 for guidelines on other double talk test methods for tests 3A and 3B.
+
+##### 6.4.2.4.1 Test 3A: Double talk convergence test with low cancelled-end levels
+
+Test No. 3A is meant to ensure that the double talk detection is not so sensitive that echo and low level cancelled end speech falsely cause operation of the double talk detector to the extent that adaptation does not occur. The test procedure is to reset the H register; then for some value of echo path delay and ERL, a signal is applied to $R_{in}$ . Simultaneously (see Figure 17) an interfering signal (double talk CSS), which is sufficiently low in level to not seriously hamper the ability of the echo canceller to converge, is applied as the signal $S_{gen}$ . This signal should allow adaptation and cancellation to occur. After the allowed adaptation interval, the adaptation is inhibited and the residual echo measured. The NLP should be *disabled*.
+
+
+
+Timing diagram for Test No. 3A showing signal and time relationships. The diagram includes four horizontal timelines: R\_in, S\_gen, Adaptation Inhibit/Enable, and Measurement. R\_in shows a signal with yellow blocks. S\_gen shows a signal with yellow blocks. Adaptation Inhibit/Enable shows a step function. Measurement shows a pulse. Key time intervals include: Adaptation interval (5 s), tau = max(t\_d, 150) ms, >= 1 s, 200 ms, and >= 200 ms. Labels include R\_in OFF, R\_in ON, and S\_gen OFF. The diagram is labeled G.168(09)\_F17.
+
+**Figure 17 – Test No. 3A signal and time relationships**
+
+NOTE – At the end of this test, a time period of $\geq 1$ s is allowed for possible latency in the adaptation inhibit command. $R_{in}$ is switched off to prevent further adaptation before the inhibit command is effective. A time period of $\tau = \max(t_d, 150)$ ms is allowed before the adaptation inhibit command to clear the impulse response of an echo path. $R_{in}$ is switched on again to perform the measurement. The 200 ms waiting time before measurement is not needed, if the contents of the bandpass filter and exponential filter in the measurement device are set to zero (flushed) before any measurement is performed.
+
+##### Requirement
+
+With the H register initially reset for all values of $L_{R_{in},act} \geq -25$ dBm0 and $\leq 0$ dBm0, $L_{S_{gen},act} = L_{R_{in},act} - 15$ dB, ERL $\geq 6$ dB and echo path delay, $t_d \leq \Delta$ ms, convergence should occur within 5 s and $L_{RES}$ should be $\leq L_{S_{gen},act}$ . The level measurement device of clause 6.4.1.2.1 should be used to measure the signal at $S_{out}$ .
+
+##### 6.4.2.4.2 Test 3B: Double talk stability test
+
+Test No. 3B is meant to ensure that the double talk detector is sufficiently sensitive and operates fast enough to prevent large divergence during double talking.
+
+The test procedure is to fully converge the echo canceller for a given echo path by applying CSS to $R_{in}$ . After the canceller is fully converged (see Figure 18), a signal $S_{gen}$ is applied that has a level $L_{S_{gen}}$ at least that of $R_{in}$ . This should cause the double talk detector to operate. After any arbitrary time, $\delta_t > 0$ , the adaptation is inhibited, the $S_{gen}$ signal is removed, and the residual echo measured. The NLP should be *disabled*.
+
+
+
+Figure 18: Test No. 3B signal and time relationships. The diagram shows four horizontal timelines. The top timeline is labeled R\_in and shows a signal with yellow rectangular pulses. The second timeline is labeled S\_gen and also shows yellow rectangular pulses. The third timeline is labeled 'Adaptation Inhibit Enable' and shows a step function. The bottom timeline is labeled 'Measurement' and shows a series of time intervals. Key time points and durations are marked: 'Fully converged' at the start of the adaptation inhibit enable signal; 'Double talk duration δt' between the start of the adaptation inhibit enable signal and the R\_in OFF pulse; 'R\_in OFF' and 'R\_in ON' pulses on the R\_in timeline; 'S\_gen OFF' pulse on the S\_gen timeline; 'τ = max(t\_d, 150) ms' between R\_in OFF and the start of the adaptation inhibit enable signal; '≥ 1 s' between the start of the adaptation inhibit enable signal and the S\_gen OFF pulse; '500 ms' between the S\_gen OFF pulse and the start of the measurement period.
+
+**Figure 18 – Test No. 3B signal and time relationships**
+
+NOTE – At the end of this test, a time period of $\geq 1$ s is allowed for possible latency in the adaptation inhibit command. $R_{in}$ is switched off to prevent further adaptation before the inhibit command is effective. A time period of $\tau = \max(t_d, 150)$ ms is allowed before the adaptation inhibit command to clear the impulse response of an echo path. $R_{in}$ is switched on again to perform the measurement. The 500 ms waiting time before measurement is not needed, if the contents of the bandpass filter and exponential filter in the measurement device are set to zero (flushed) before any measurement is performed.
+
+[b-ITU-T GSTP.CSS] in clause I.8 shows a wide variation of performance for different languages for this test. Note that test 3B is even more sensitive to real speech variations and CSS may not provide adequate approximation of real speech for this test.
+
+###### **a) Double talk stability test with high cancelled-end levels**
+
+###### **Requirement**
+
+With the echo canceller initially in the fully converged state for all values of $L_{Rin,act} \geq -30$ dBm0 and $\leq 0$ dBm0, and for all values of $L_{Sgen,act} \geq L_{Rin,act}$ and for all values of ERL $\geq 6$ dB and echo path delay $t_d \leq \Delta$ ms, the residual echo level after the simultaneous application of $R_{in}$ and $S_{gen}$ for any time period should not increase more than 10 dB over the steady state requirements of Figure 11. The level measurement device of clause 6.4.1.2.1 should be used to measure the signal at $S_{out}$ .
+
+###### **b) Double talk stability test with low cancelled-end levels**
+
+##### **Requirement**
+
+The test definition is identical to part (a) except that $L_{Sgen,act} = L_{Rin,act} - X$ dB. For all values $6 \text{ dB} \leq X \leq 30 \text{ dB}$ , the steady state requirement of Figure 11 + 3 dB would apply.
+
+##### **6.4.2.4.3 Test 3C: Double talk test under simulated conversation**
+
+Test No. 3C is meant to ensure that the echo canceller does not produce undesirable artefacts during and after periods of double talk (see clause I.7).
+
+The test procedure is to reset the H register. Then for some value of echo path delay, $t_d \leq \Delta$ ms, and ERL $\geq 6$ dB, a signal is applied to $R_{in}$ . Simultaneously (see Figure 19), a signal $S_{gen}$ is applied that has a level $L_{Sgen}$ at least that of $R_{in}$ . After a time $t_1$ , $S_{gen}$ is removed and $S_{out}$ is measured. During time $t_4$ and $t_5$ , $S_{gen}$ is reapplied and the output is evaluated for artefacts. $R_{in}$ is removed during period $t_5$ . The NLP should be enabled for this test.
+
+
+
+Figure 19: Test No. 3C signal and time relationships diagram. It shows three signal lines: R\_in, S\_gen, and Adaptation. R\_in consists of several gray rectangular blocks. S\_gen consists of dark gray rectangular blocks. The Adaptation line has 'Inhibit' and 'Enable' states. Time intervals are marked: t1 (5.6 s), t2 (1.4 s), t3 (5 s), t4 (5.6 s), and t5 (5.6 s). A >= 200 ms interval is marked at the start. The diagram is labeled G.168(09)\_F19.
+
+**Figure 19 – Test No. 3C signal and time relationships**
+
+##### **Requirement**
+
+With the H register initially reset, for all values of $L_{Rin,act} \geq -25$ dBm0 and $\leq 0$ dBm0, and for all values of $L_{Sgen,act} \geq L_{Rin,act}$ and for all values of ERL $\geq 6$ dB and echo path delay $t_d \leq \Delta$ ms, any peaks (see clause 6.4.1.2.2) during period $t_2$ should not exceed the level $L_{Sgen,act}$ during period $t_1$ . The returned echo level (measured using the level measurement device of clause 6.4.1.2.1) during time period $t_3$ should meet the requirements of Figure 9 with NLP enabled. During $t_4$ and $t_5$ , no peaks (see clause 6.4.1.2.2) should exceed the level of $L_{Sgen,act} + 6$ dB.
+
+Level offsets between $L_{Rin}$ and $L_{Sgen}$ can cause inappropriate operation of the NLP and can cause speech degradation and is for further study. Variation of CSS may be useful for this purpose.
+
+#### **6.4.2.5 Test No. 4 – Leak rate test**
+
+This test is meant to ensure that the leak time is not too fast, i.e., that the contents of the H register do not go to zero too rapidly.
+
+The test procedure is to fully converge the echo canceller using CSS for a given echo path and then to remove all signals from the echo canceller. After two minutes the contents of the H register are frozen, CSS is reapplied to $R_{in}$ and the residual echo measured (see Figure 20). The NLP should be *disabled*.
+
+
+
+Figure 20: Test No. 4 signal and time relationships diagram. It shows three signal lines: R\_in, S\_gen, and Adaptation. R\_in has yellow rectangular blocks. S\_gen is a line at 0. The Adaptation line has 'Inhibit' and 'Enable' states. Time intervals are marked: 2 min, >= 1 s, and Measurement. The diagram is labeled G.168(09)\_F20.
+
+**Figure 20 – Test No. 4 signal and time relationships**
+
+NOTE – At the end of this test, a time period of $\geq 1$ s is necessary to allow for possible latency in the adaptation inhibit command. $R_{in}$ is switched on to perform the measurement.
+
+##### Requirement
+
+With the echo canceller initially in the fully converged state for all values of $L_{Rin,act} \geq -30$ dBm0 and $\leq 0$ dBm0, two minutes after the removal of the $R_{in}$ signal, the residual echo level should not increase more than 10 dB over the steady state requirement of Test No. 2 (Figure 11). The level measurement device of clause 6.4.1.2.1 should be used to measure the signal at $S_{out}$ .
+
+#### 6.4.2.6 Test No. 5 – Infinite return loss convergence test
+
+These tests are meant to ensure that the echo canceller has some means to prevent the unwanted generation of echo during significant echo path model changes. This may occur when the H register contains an echo path model, either from a previous connection or the current connection, and the echo path is significantly changed (for example: circuit echo vanishes or reappears) while a signal is present at $R_{in}$ .
+
+The tests are divided into two parts and are designed to test real-world scenarios as follows:
+
+- **Test No. 5A** is the same as Test No. 5 in versions of ITU-T G.168 up to 03/2009, and is designed to ensure that the echo canceller has some means to prevent the unwanted generation of echo when the echo path is opened (infinite ERL). This may occur due to switch action or a transmission fault in the echo path.
+- **Test No. 5B** is designed to simulate a call transfer scenario where a call is transferred from destination A to destination B and then back to destination A, where A and B have echo paths that are significantly different (e.g., a call to a 2-wire telephone is transferred to a 4-wire ISDN telephone and vice-versa)
+
+##### 6.4.2.6.1 Test No. 5A: Infinite return loss convergence test
+
+The test procedure is to fully converge the echo canceller using CSS for a given echo path. The echo path is then interrupted at $R_{out}$ while a CSS is applied to $R_{in}$ , and the output at $S_{out}$ measured (see Figure 21a). The NLP should be disabled.
+
+
+
+Figure 21a: Test No. 5A signal and time relationships diagram. The diagram shows three horizontal lines representing signals over time. The top line is labeled 'R\_in' and shows a signal starting at time '0' and continuing through a series of five rectangular blocks. The middle line is labeled 'Echo path' and has two states: 'Closed' (a solid line) and 'Open' (a dashed line). The 'Closed' state continues until time 't\_0', at which point it switches to the 'Open' state. The bottom line is labeled 'G.168(15)\_F21a' and shows a signal that is continuous until 't\_0', where it becomes a dashed line. A vertical dashed line at 't\_0' connects all three signals, indicating the point of interruption.
+
+**Figure 21a – Test No. 5A signal and time relationships**
+
+The level at $R_{in}$ in the test requirement is $L_{Rin,act}$ . It is the signal level measured using the RMS method over the active portion of the CSS only (i.e., excluding the pause of the CSS) as described in clause 6.4.1.2.
+
+##### Requirement
+
+With the echo canceller initially in the fully converged state for all values of $ERL \geq 6$ dB, and for all values of $L_{Rin,act} \geq -30$ dBm0 and $\leq 0$ dBm0, and at time $t_0$ the echo path is interrupted with an open echo path, the combined loss $L_{Rin,act} - L_{RES}$ should meet the requirements of Figure 12a, as measured using the method of clause 6.4.1.2.1.
+
+The level at $S_{out}$ is measured using a meter conforming to the characteristics of clause 6.4.1.2.1.
+
+##### 6.4.2.6.2 Test No. 5B: Re-convergence during call transfer test
+
+The test procedure is to fully converge the echo canceller using CSS for a given echo path. The ERL of the echo path is then changed while a CSS is applied to $R_{in}$ , and the output at $S_{out}$ measured (see Figures 21b and 21c below). The NLP should be disabled for this test.
+
+The following echo path model changes represent various call transfer scenarios:
+
+- 1) Low-high-low ERL transitions as shown in Figure 21b, and
+- 2) High-low-high ERL transitions as shown in Figure 21c.
+
+
+
+Figure 21b: Signal and timing relationships for low-high-low ERL transitions. The diagram shows a signal path starting with Rin connected to a series of four blocks. Below the path, the 'Low ERL Echo path' is indicated by a solid line, and the 'High ERL' path is indicated by a dashed line. The path is divided into three segments: '2-wire' (Low ERL) from the start to time t1, '4-wire' (High ERL) from t1 to t2, and '2-wire' (Low ERL) from t2 onwards. Vertical dashed lines mark times t1 and t2. The label 'G.168(15)\_F21b' is in the bottom right.
+
+Figure 21b – Test No. 5B signal and timing relationships for low-high-low ERL transitions
+
+
+
+Figure 21c: Signal and timing relationships for high-low-high ERL transitions. The diagram shows a signal path starting with Rin connected to a series of four blocks. Below the path, the 'Low ERL Echo path' is indicated by a dashed line, and the 'High ERL' path is indicated by a solid line. The path is divided into three segments: '4-wire' (High ERL) from the start to time t1, '2-wire' (Low ERL) from t1 to t2, and '4-wire' (High ERL) from t2 onwards. Vertical dashed lines mark times t1 and t2. The label 'G.168(15)\_F21c' is in the bottom right.
+
+Figure 21c – Test No. 5B signal and timing relationships for high-low-high ERL transitions
+
+The level at $R_{in}$ in the test requirement is $L_{Rin,act}$ . It is the signal level measured using the RMS method over the active portion of the CSS only (i.e., excluding the pause of the CSS) as described in clause 6.4.1.2.
+
+##### Requirement
+
+With the echo canceller initially in the fully converged state for $30 \text{ dB} \geq \text{ERL} \geq 6 \text{ dB}$ (for low ERL echo path models), and $\text{ERL} \geq 46 \text{ dB}$ (for high ERL echo path models), and for all values of $L_{Rin,act} \geq -30 \text{ dBm0}$ and $\leq 0 \text{ dBm0}$ , the combined loss $L_{Rin,act} - L_{RES}$ should meet the requirements of Figure 12b at times $t_1$ and $t_2$ (where $t_2 \geq t_1 + 14 \text{ s}$ , in multiples of the 700 ms CSS period, and both $t_1$ and $t_2$ in Figures 21b and 21c correspond to $t_0$ in Figure 12b). The level at $S_{out}$ is measured using a meter conforming to the characteristics of clause 6.4.1.2.1.
+
+NOTE 1 – The value of $t_2 \geq t_1 + 14 \text{ s}$ in Test 5B is chosen so that at least 10 s is allowed for re-convergence, and the echo path change aligns with the start of a CSS burst.
+
+NOTE 2 – Test 5B is designed to represent a real-world call transfer scenario and the example given in Figures 21b and 21c refers to the transfer between a 2-wire telephone and a 4-wire ISDN telephone. In the case of 4-wire ISDN telephones, the electrical ERL would normally be infinite, but the requirement is for an $\text{ERL} \geq 46 \text{ dB}$ . This is to allow for the possibility of acoustic echo from the handset of the 4-wire telephone as given in Recommendation [ITU-T P.310]. Note that the 46 dB Weighted Terminal Coupling Loss (TCLw) given in Recommendation [ITU-T P.310] is a frequency-weighted measurement. However, for the purpose of this test, the ERL definition in ITU-T G.168 (see clause 3.14) should be used. Suggested values of high ERL to use for this test are 46 dB, 55 dB and infinity. Note also that the acoustic echo is modelled using a linear echo path.
+
+NOTE 3 – Test 5A requirements refer to Figure 12a and Test 5B requirements to Figure 12b. This is intentional, since the transition to an infinite ERL in Test 5A means that the theoretical loss $L_{\text{Rin,act}} - L_{\text{RES}}$ (due to the combined signals from the echo path and echo canceller) cannot be less than 6 dB. This is not the case for Test 5B, where the ERLs are finite and a theoretical loss $L_{\text{Rin,act}} - L_{\text{RES}}$ of less than 6 dB immediately after the ERL transition is possible.
+
+NOTE 4 – The requirement of Test 5B specifies only a change to the ERL. However, the call transfer scenarios that this test is designed to emulate would normally also include changes to the echo path model and the echo path delay. The user is therefore encouraged to consider these aspects when performing this test.
+
+#### 6.4.2.7 Test No. 6 – Non-divergence on narrow-band signals
+
+This test has the object of verifying that the echo canceller will remain converged for subscriber-originated narrow-band signals after having converged on a wideband signal. The residual echo level is measured before and after the application of a sinusoidal wave or a wave composed of two frequencies.
+
+The method consists of completely converging the echo canceller as in Test 2. The sequence of tones of Table 2 is then applied at $R_{\text{in}}$ . After the sequence is completed, the adaptation is inhibited and the residual echo is measured with the signal of Test 2. The period of $\geq 1$ s allowed following the adaptation inhibit command should be applied. The NLP should be disabled.
+
+##### Requirement
+
+The echo canceller is fully converged as in Test 2 for all values of ERL $\geq 6$ dB, and echo path delay $t_d \leq \Delta$ ms. Once chosen, the echo path remains the same throughout the test. This test incorporates both CSS and tones. The scaling factors defined in Table D.1a should be used to scale the coefficients of the echo path models defined in Annex D. The sequence of tones of Table 2 (with the higher frequency 2 dB higher than the lower frequency for the dual tone combinations) is then applied for 5 s each to $R_{\text{in}}$ such that $L_{\text{Rin}} \geq -30$ dBm0 and $\leq 0$ dBm0. After the application of the tone sequence, the adaptation is inhibited. Using the same signal as in Test No. 2, the measured residual echo should not degrade more than 10 dB from the requirements of Figure 11 of Test No. 2. The NLP is disabled for this test. The level measurement device of clause 6.4.1.2.1 should be used to measure the signal at $S_{\text{out}}$ .
+
+**Table 2 – Sequence of tones**
+
+| |
+|--------------|
+| 697 |
+| 941 |
+| 1336 |
+| 1633 |
+| 697 and 1209 |
+| 770 and 1336 |
+| 852 and 1477 |
+| 941 and 1633 |
+
+#### 6.4.2.8 Test No. 7 – Stability test
+
+The object of this test is to verify that the echo canceller will remain stable for narrow-band signals. The residual echo is measured throughout the application of a mono-frequency sinusoidal wave.
+
+The test method is as follows: with the H register initially reset, and the NLP disabled, the echo canceller is converged on the sinusoidal signal for two minutes. The residual echo level is measured continuously throughout the two minutes that the input signal is applied.
+
+##### Requirement
+
+With the echo canceller H register initially reset, apply a mono-frequency signal, except for those identified in Table 3 of Test No. 8, for two minutes at $R_{in}$ . The residual echo level, measured continuously throughout the two minutes that the input signal is applied, should be less than or equal to that shown in Figure 22 after an initial adaptation period of 10 s. The level of $R_{in}$ for this test should be in the range $L_{Rin} \geq -30$ dBm0 and $\leq +3$ dBm0, with an echo path consisting of two ERL values of 6 dB and 20 dB, with an echo path delay $t_d \leq \Delta$ ms.
+
+NOTE – $t_d$ is assumed to be negligible relative to the adaptation period allowed in this test. It is therefore not accounted for explicitly in the requirement.
+
+The residual echo level is measured using a meter conforming to the characteristics of clause 6.4.1.2.1.
+
+
+
+Figure 22: Performance requirements for Test No. 7. A line graph showing the relationship between the input signal level L\_Rin (dBm0) on the x-axis and the residual echo level L\_RES (dBm0) on the y-axis. The x-axis ranges from -30 to +3 dBm0 with major ticks every 10 dBm0. The y-axis ranges from -55 to -27.5 dBm0 with major ticks every 5 dBm0. A solid diagonal line starts at (-30, -55) and ends at (+3, -27.5). The equation for the line is L\_RES = 0.83L\_Rin - 30. The label G.168(09)\_F22 is in the bottom right corner.
+
+Note that the equation for the line in Figure 22 is: $L_{Res} = 0.83L_{Rin} - 30$ .
+
+**Figure 22 – Performance requirements for Test No. 7**
+
+#### 6.4.2.9 Test No. 8 – Non-convergence of echo cancellers on specific ITU-T Nos. 5, 6 and 7 in-band signalling and continuity check tones (optional)
+
+Echo cancellers, which are not externally disabled by the switch and which are located on the line side of Signalling System Nos. 5, 6 and 7 in international exchanges or are associated with national exchanges, should minimize the impairment, if any, on specific in-band signalling and continuity check tones. The following tests simulate a possible network scenario where a call is terminated after an echo canceller has converged during the call, and then signalling tones are applied. The tests are meant to ensure that echo cancellers will not remove or cancel a mono or bi-frequency signal transmitted in a handshaking protocol in the transmit direction either before or after receiving the same signal (except for amplitude and phase) in the receive direction. This is intended to allow a correct transmission of specific signalling or continuity check tones without externally disabling the echo canceller. The NLP should be enabled.
+
+For an echo canceller equipped with this optional capability, the echo canceller is initially converged using CSS to a given echo path with an ERL $\geq 6$ dB, and an echo path delay $t_d \leq \Delta$ . For simplification, the fully converged state may be achieved with an ERL of 6 dB. Then in sequence the CSS is removed, the echo path is opened at $R_{out}$ , and one of the signals from Table 3 for which the echo canceller is optioned is applied at $S_{in}$ . Within 90 ms either before or after the application of the signal at $S_{in}$ , the same signal (may differ in amplitude and phase) is applied at $R_{in}$ . After the detection time, the level at $S_{out}$ is measured.
+
+The power level $M$ , of each signal applied should be within the following limits:
+
+**System 5:** $-16 \leq M \leq -2$ dBm0
+
+NOTE 1 – This range applies to the single frequency signals $f_1$ and $f_2$ . The level of the individual signals in the compound signal may differ from each other by not more than 5 dB. Note that when the levels of the individual signals approach $-2$ dBm0, the compound signal may be clipped. The nominal transmit level is specified as $-9 \pm 1$ dBm0.
+
+See [ITU-T Q.143] and [ITU-T Q.144].
+
+**System 6:** $-18 \leq M \leq -6$ dBm0
+
+NOTE 2 – The nominal transmit level is $-12 \pm 1$ dBm0.
+
+See [ITU-T Q.271].
+
+**System 7:** $-18 \leq M \leq -6$ dBm0
+
+NOTE 3 – The nominal transmit level is $-12 \pm 1$ dBm0.
+
+See clause 7 of [ITU-T Q.724].
+
+The above levels are designed to ensure that the echo canceller will operate with signals that occupy the entire range of levels given in the appropriate signalling ITU-T Recommendations.
+
+The echo canceller response should be sufficiently long to provide immunity from false operation due to voice signals. Also, the echo canceller response should not be so long as to needlessly extend the time for the signal to appear on the network.
+
+##### Requirement
+
+The level at $S_{out}$ , as measured using the method of clause 6.4.1.2.1, should not vary more than 2 dB with respect to the level at $S_{in}$ after an allowed 1 second detection time.
+
+**Table 3 – Applicable signalling tones**
+
+| System 5 | System 6 | System 7 |
+|---------------------------------------|------------------|------------------|
+| $2400 \pm 15$ Hz | $2000 \pm 30$ Hz | $2000 \pm 30$ Hz |
+| $2600 \pm 15$ Hz | | |
+| $2400 \pm 15$ Hz and $2600 \pm 15$ Hz | | |
+
+#### 6.4.2.10 Test No. 9 – Comfort noise test
+
+##### 6.4.2.10.1 Test No. 9A – Comfort noise performance with step change of background noise level
+
+This test is meant to ensure that the echo canceller is able to provide a comfort noise signal on $S_{out}$ which matches noise received on $S_{in}$ . It also tests whether the canceller is able to adjust the level of this comfort noise signal to compensate for changes in the level of input noise. As this test is not intended as a test of echo cancellation capability, an ERL of 12 dB is used for the entire test. The steps of this test should be applied in sequence. They consist of setting the level of $S_{gen}$ to a value between $-50$ dBm0 and $-40$ dBm0, lowering the level of $S_{gen}$ by $\delta$ dB, and then raising the level of $S_{gen}$ back to the initial level. Consequently, the test covers a range of operation for $L_{S_{gen}}$ between $-60$ dBm0 and $-40$ dBm0. The level of $R_{in}$ will be at silence or at $-10$ dBm0. White Gaussian Noise, band-limited 300 Hz – 3400 Hz, with a crest factor of $11$ dB $\pm 1$ dB is used for all input signals for this test. The level at $S_{out}$ is measured using the RMS method of clause 6.4.1.2 (i.e., no filtering should precede the RMS calculation). The NLP and comfort noise feature should be enabled.
+
+###### a) Part 1 (matching)
+
+- 1) Set $L_{S_{gen}}$ to a level between $-50$ dBm0 and $-40$ dBm0.
+- 2) Set $L_{R_{in}}$ to silence ( $< -60$ dBm0) and hold for 10 s.
+- 3) $L_{R_{in}}$ to $-10$ dBm0.
+- 4) Measure $L_{RET}$ after 2 s.
+
+###### Requirement
+
+For all values of $L_{S_{gen}}$ , $L_{RET}$ should be within 2.0 dB of $L_{S_{gen}}$ when measured over a 700 ms window. Also, this value should hold as long as noise level $L_{S_{gen}}$ remains constant, and sequential 700 ms measurements should be made over a minimum period of 7.7 s to check this.
+
+###### b) Part 2 (adjustment down)
+
+The following 8 steps should be performed in sequence for $\delta = 5$ dB and $\delta = 10$ dB:
+
+- 1) Lower $L_{S_{gen}}$ by $\delta$ dB from the level in Part 1.
+- 2) Set $L_{R_{in}}$ to silence ( $< -60$ dBm0) and hold for 10 s.
+- 3) $L_{R_{in}}$ to $-10$ dBm0.
+- 4) Measure $L_{RET}$ after 2 s.
+
+###### Requirement
+
+$L_{RET}$ should be within 2.0 dB of $L_{S_{gen}}$ when measured over a 700 ms window. Also, this value should hold as long as noise level $L_{S_{gen}}$ remains constant, and sequential 700 ms measurements should be made over a minimum period of 7.7 s to check this.
+
+###### c) Part 3 (adjustment up)
+
+- 5) Raise $L_{S_{gen}}$ by $\delta$ dB from the level in Part 2.
+- 6) Set $L_{R_{in}}$ to silence ( $< -60$ dBm0) and hold for 10 s.
+- 7) Set $L_{R_{in}}$ to $-10$ dBm0.
+- 8) Measure $L_{RET}$ after 2 s.
+
+##### Requirement
+
+$L_{\text{RET}}$ should be within 2.0 dB of $L_{\text{Sgen}}$ when measured over a 700 ms window. Also, this value should hold as long as noise level $L_{\text{Sgen}}$ remains constant, and sequential 700 ms measurements should be made over a minimum period of 7.7 s to check this.
+
+##### 6.4.2.10.2 Test No. 9B – Comfort noise performance with dynamic change of background noise level
+
+This test examines the dynamic behaviour of the comfort noise generator by investigating its performance during the continuous change of background noise level. The test is divided into two parts:
+
+- **Part 1 – Mandatory:** This part is meant to ensure that the echo canceller is able to provide a comfort noise signal on $S_{\text{out}}$ which tracks the changing level of a background noise signal at $S_{\text{gen}}$ . This part has requirements that are derived from Test No. 9A and is performed over the same range of noise levels at $S_{\text{gen}}$ (–60 to –40 dBm0).
+- **Part 2 – Optional:** This part is meant to examine the behaviour of the comfort noise generator for changing levels of background noise over the range from –70 to –40 dBm0.
+
+Altogether, the two parts of this test provide an analysis of comfort noise stability over a wide range of varying background noise levels. The test is performed with different values of ERL to simulate different network configurations, including 2-wire and 4-wire terminations.
+
+NOTE 1 – This test is designed to investigate the overall performance of the NLP and the Comfort Noise Generator algorithm during the continuous change of background noise level. For example, the 2 seconds long active high level $R_{\text{in}}$ parts usually trigger the NLP and with that the generation of comfort noise, whereas the 2 second long silent periods allow the Comfort Noise Generator to learn the level and characteristic of the new background noise. However this behaviour is not ensured. It depends on the NLP design. This means that the $S_{\text{out}}$ signal may not be generated by the Comfort Noise Generator, but it can be the background noise itself. Care should be taken if someone wants to investigate the performance of the Comfort Noise Generator algorithm itself with this test.
+
+###### Test signals
+
+The $R_{\text{in}}$ test signal duration is 350 seconds long. The first 10 seconds of this test vector consist of 1 second of silence, followed by 6 cycles (12 bursts) of single-talk CSS at –10 dBm0 followed by silence. The remaining duration of this test vector consists of 2 seconds of continuous CSS (continuous CSS is defined as CSS bursts with the silence intervals removed) followed by 2 seconds of silence with a logarithmically increasing continuous CSS test signal level from –40 to –10 dBm0 for 170 seconds followed by a logarithmically decreasing continuous CSS test signal level from –10 to –40 dBm0 for the remaining 170 seconds.
+
+The $S_{\text{gen}}$ test signal duration is also 350 seconds long. The first 10 seconds of this test vector consist of 5.5 seconds of silence followed by 6 cycles (12 bursts) of single-talk CSS at –40 to –10 dBm0 followed by silence. The remaining duration of this test signal consists of White Gaussian Noise, band-limited 300 Hz – 3400 Hz, with a crest factor of 11 dB $\pm$ 1 dB increasing logarithmically in level from –86 to –20 dBm0 for 170 seconds and then logarithmically decreasing in level from –20 to –86 dBm0 for the remaining 170 seconds.
+
+NOTE 2 – The first 10 seconds of this test that include 12 bursts of CSS signal in $R_{\text{in}}$ and 12 bursts of CSS in $S_{\text{gen}}$ are optional and they only serve as a simple pre-conditioning to allow consistent test results for the CNG measurements.
+
+NOTE 3 – A logarithmic rate of increase and decrease in signal level is used, since the natural sensitivity of the human ear is logarithmic with respect to noise level perception. Furthermore, the use of logarithmically increasing and decreasing signal levels for testing allows for linear presentation on a dB scale.
+
+NOTE 4 – For simplicity, a constant signal level at $R_{in}$ may be used, but this may result in crosstalk when using analogue interfaces, especially for $S_{out}$ signal levels between $-80$ and $-60$ dBm0. If using a constant level at $R_{in}$ , a value of $-20$ dBm0 is recommended, although anywhere in the range $-30$ to $-10$ dBm0 is acceptable.
+
+###### Test procedure
+
+With the H register initially reset, or alternatively, with an open echo path resulting in $S_{in} = 0$ and the H register content converged to 0, the echo canceller must then be fully converged using a CSS test signal at $R_{in}$ for $\geq 30$ seconds for a given value of echo path delay, $TD \leq \Delta$ ms, and $ERL \geq 6$ dB. The NLP and comfort noise feature should be enabled for this test.
+
+Optionally, Test 2A-a may be conducted to allow optimum echo canceller convergence prior to Test No. 9b execution. This optional pre-conditioning allows sufficient time for echo canceller convergence and minimizes any variance in the test results when performing this test.
+
+Apply the $R_{in}$ and $S_{gen}$ signals simultaneously and record $S_{out}$ (and optionally $R_{in}$ and/or $R_{out}$ ) for the duration of the test. The level at $R_{in}$ , $S_{out}$ and $S_{gen}$ should be measured using the method of clause 6.4.1.2.1.
+
+##### Requirement
+
+**Part 1 – Mandatory:** $L_{RET}$ should be within $\pm 6$ dB of $L_{Sgen}$ when $L_{Sgen}$ is within the range $-60$ to $-40$ dBm0.
+
+**Part 2 – Optional:** $L_{RET}$ should be within $\pm 6$ dB of $L_{Sgen}$ when $L_{Sgen}$ is within the range $-70$ to $-40$ dBm0.
+
+As a minimum, this test should be performed with ERL values of 40, 15 and 6 dB.
+
+Example results for this test are shown in Figures 23a, 23b and 23c. These tests were performed at different values of ERL.
+
+NOTE 5 – For each of the following figures, the green trace labelled Source is used to represent the $R_{in}$ test signal, and the blue trace labelled Ch1 is used to represent the $S_{out}$ signal.
+
+NOTE 6 – In Figure 23a, the test has been performed with a 4-wire network configuration ( $ERL \geq 40$ dB) to obtain a baseline performance of the echo canceller comfort noise generation before repeating the test for 6 and 15 dB ERLs. Optionally, the echo canceller may be disabled to verify similar baseline performance to the 4-wire network configuration. It is highly recommended to investigate any significant inconsistencies.
+
+NOTE 7 – To visualise the requirements of this test, Figures 1 to 3 show the approximate upper and lower limits of $L_{RET}$ relating to both the *Mandatory* and *Optional* test requirements. These limits are relative to the average level of $L_{Sgen}$ and not to the values of $L_{Sgen}$ as measured at the output of the 35 ms filter using the method of clause 6.4.1.2.1. The latter approach, which is used in the requirements, results in a measurement uncertainty of up to 2 dB (see Appendix III of [b-ITU-T G.160]). This uncertainty has been taken into account in the $\pm 6$ dB tolerance allowed within the requirement. This effect is for further study.
+
+
+
+Figure 23a: Dynamic comfort noise level matching at ≥ 40 dB ERL. The graph plots signal level in U/dBm0 (y-axis, 0 to -90) against time in t/s (x-axis, 0 to 350). It features four series: CH1 (blue line), Source (green vertical bursts), Lower limit (magenta line), and Upper limit (red line). The Source signal's envelope rises from -40 dBm0 at 50s to -15 dBm0 at 175s, then falls back to -40 dBm0 at 300s. The CH1 signal follows the lower envelope of the Source. The Upper and Lower limits form a corridor around the CH1 signal, with the Upper limit having a flat top at -5 dBm0 between approximately 135s and 225s. The graph is identified as G.168(15)\_F23a.
+
+**Figure 23a – Dynamic comfort noise level matching at $\geq 40$ dB ERL**
+
+
+
+Figure 23b: Dynamic comfort noise level matching at 15 dB ERL. This graph is similar to Figure 23a but for a lower ERL. The y-axis is U/dBm0 (0 to -90) and the x-axis is t/s (0 to 350). The Source signal (green) and CH1 (blue) follow a similar triangular envelope as in 23a. The Upper limit (red) and Lower limit (magenta) define the acceptable range for the comfort noise level. The Upper limit has a flat plateau at -5 dBm0 between 135s and 225s. The graph is identified as G.168(15)\_F23b.
+
+**Figure 23b – Dynamic comfort noise level matching at 15 dB ERL**
+
+
+
+Figure 23c: Dynamic comfort noise level matching at 6 dB ERL. The graph plots signal levels (U/dBm0) against time (t/s). The y-axis ranges from 0 to -90 dBm0. The x-axis ranges from 0 to 350 seconds. The graph shows four data series: CH1 (blue line), Source (green line), Lower limit (magenta line), and Upper limit (red line). The Source signal is a high-frequency, high-amplitude signal. The CH1 signal is a lower-frequency, lower-amplitude signal. The Lower limit and Upper limit signals are step-like signals that define the dynamic range of the comfort noise. The graph is divided into three regions: Region I (0 to 50 s), Region II (50 to 150 s), and Region III (150 to 350 s). The Upper limit signal is at -30 dBm0 in Region I, -40 dBm0 in Region II, and -50 dBm0 in Region III. The Lower limit signal is at -70 dBm0 in Region I, -80 dBm0 in Region II, and -90 dBm0 in Region III. The Source signal is at -10 dBm0 in Region I, -20 dBm0 in Region II, and -30 dBm0 in Region III. The CH1 signal is at -70 dBm0 in Region I, -80 dBm0 in Region II, and -90 dBm0 in Region III. The graph is labeled G.168(15)\_F23c.
+
+**Figure 23c – Dynamic comfort noise level matching at 6 dB ERL**
+
+#### 6.4.2.11 Test No. 10 – Facsimile test
+
+This test is meant to ensure that the echo cancellers located at each end of a connection converge rapidly on the initial handshaking sequences of a facsimile call and have some means to prevent the unwanted generation of echo. The test and requirements were originally developed to overcome problems in the network due to the turnaround of fax handshaking signals (see clause 5.2.1 of [ITU-T G.161]: "Interaction of echo cancellers with facsimile transmission"). Customer complaints were reduced following the introduction of this test. The test is split into three parts. Test 10A looks at the performance of the echo canceller located on the calling station side, and Test 10B looks at the performance of the echo canceller on the called station side. Test 10C looks at the performance of the echo canceller on the calling station side during page transmission.
+
+NOTE 1 – The vast majority of echo cancellers use some form of the least-squares algorithm to model the echo path impulse response. When a sinusoidal input signal or a narrow-band signal like ITU-T V.21 is used as the input for the echo canceller, an exact model of the echo path is not possible. This response to a sinusoidal input signal is a well-known and understood consequence of the least-squares algorithm, and can cause a problem with Test 10A and Test 10B.
+
+NOTE 2 – In Test 10A, Region II starts during the application of the CED signal, and extends to the beginning of Sequence No. 1. Because of the response of least-squares-based algorithms to sinusoidal inputs, during that portion of Region II from the cessation of the CED signal to the beginning of Region III, the echo canceller may produce a residual echo (or echo bursts) that exceeds the recommendation limits at the end of the CED signal. The user should be aware that this may not be a failure of the echo canceller, but merely a response to the sinusoidal CED input signal. When this response occurs, additional investigation is warranted.
+
+The test has been designed to run in a laboratory environment using an echo canceller and a fax simulator. The tests should be run separately.
+
+NOTE 3 – When using the hybrid models given in Annex D, the $K_i$ factors for tone signals given in Table D.1b should be used for this test.
+
+The tests should be performed with [ITU-T G.165] or this Recommendation tone disabler switched on. The requirements with NLP disabled are now more relevant following the introduction of the option to disable the NLP during fax transmission as described in clause 7.1.
+
+The provisioned state of the NLP for Test 10A is enabled. However, if the NLP is reliably disabled automatically by means as described in clause 7.1, then only the requirements for NLP disabled are
+
+relevant. If NLP can be enabled or disabled as a configurable feature, then Test 10A shall exercise both modes of operation. This statement may also be applied to Tests 10B and 10C if the NLP is guaranteed to remain disabled throughout the fax call. If the NLP is likely to re-enable due to sufficiently long gaps during sequences of message exchange (during a facsimile call, there are a number of silent periods that may be long enough to permit the re-enabling of the NLP, see clause 5.2.1 of [ITU-T G.161]), then the requirements for NLP enabled in Tests 10B and 10C apply. Test results showed that the periods of silence during sequences of message exchange may extend to more than the maximum release time 400 ms. A specific test for this mode of operation is for further study.
+
+For this purpose, the following signals should be applied (bits are transmitted left to right). The initial flag is repeated 37 times for each sequence.
+
+###### **FAX test sequences:**
+
+###### **Calling tone (CNG)**
+
+###### *Conditions*
+
+Signal 1100 Hz $\pm$ 38 Hz
+
+Duration On for 0.5 s, Off for 3 s ( $\pm 15\%$ )
+
+###### **Called station identification (CED)**
+
+###### *Conditions*
+
+Signal 2100 Hz $\pm$ 15 Hz
+
+Duration 2.6-4 s
+
+###### **Binary coded sequences**
+
+###### **Sequence No. 1 (called station):**
+
+###### **Non-standard facilities (NSF) frame:**
+
+| Flag | HDLC address field | HDLC control field | Control field NSF | Information field, 8 octets (country, manufacturer, additional code number) | Frame check sequence | Flag |
+|-----------|--------------------|--------------------|-------------------|-----------------------------------------------------------------------------|----------------------|-----------|
+| 0111 1110 | 1111 1111 | 1100 1000 | 0000 0100 | 0101 0101, 0101 0101, 0101 0101, ... | 1010 1010 | 0111 1110 |
+
+###### **Called subscriber identification (CSI) frame:**
+
+| Flag | HDLC address field | HDLC control field | Control field CSI | Information field, 20 octets (receiver code number) | Frame check sequence | Flag |
+|-----------|--------------------|--------------------|-------------------|-----------------------------------------------------|----------------------|-----------|
+| 0111 1110 | 1111 1111 | 1100 1000 | 0000 0100 | 0101 0101, 0101 0101, 0101 0101, ... | 1010 1010 | 0111 1110 |
+
+###### **Digital identification signal (DIS) frame:**
+
+| Flag | HDLC address field | HDLC control field | Control field DIS | Information field, 3 octets | Frame check sequence | Flag |
+|-----------|--------------------|--------------------|-------------------|---------------------------------|----------------------|-----------|
+| 0111 1110 | 1111 1111 | 1100 1000 | 0000 0001 | 0101 0101, 0101 0101, 0101 0101 | 1010 1010 | 0111 1110 |
+
+**Sequence No. 2 (calling station):**
+
+**Non-standard set-up (NSS) frame:**
+
+| Flag | HDLC address field | HDLC control field | Control field NSS | Information field, 3 octets | Frame check sequence | Flag |
+|-----------|--------------------|--------------------|-------------------|---------------------------------|----------------------|-----------|
+| 0111 1110 | 1111 1111 | 1100 1000 | 1100 0100 | 0101 0101, 0101 0101, 0101 0101 | 1010 1010 | 0111 1110 |
+
+**Transmitting subscriber identification (TSI) frame:**
+
+| Flag | HDLC address field | HDLC control field | Control field TSI | Information field, 20 octets (Transmitter code number) | Frame check sequence | Flag |
+|-----------|--------------------|--------------------|-------------------|--------------------------------------------------------|----------------------|-----------|
+| 0111 1110 | 1111 1111 | 1100 1000 | 1100 0010 | 0101 0101, 0101 0101, 0101 0101, ... | 1010 1010 | 0111 1110 |
+
+**Digital command signal (DCS) frame:**
+
+| Flag | HDLC address field | HDLC control field | Control field DCS | Information field, 20 octets (Transmitter code number) | Frame check sequence | Flag |
+|-----------|--------------------|--------------------|-------------------|--------------------------------------------------------|----------------------|-----------|
+| 0111 1110 | 1111 1111 | 1100 1000 | 1100 0001 | 0101 0101, 0101 0101, 0101 0101, ... | 1010 1010 | 0111 1110 |
+
+###### **Data transmission conditions**
+
+The transmission of sequences No. 1 and No. 2 in the telephone channel is obtained by means of frequency shift (see [ITU-T V.21]).
+
+###### *Conditions*
+
+| | |
+|----------------------------------------------|--------------|
+| Data signalling rate, synchronous | 300 bit/s |
+| Centre frequency | 1750 Hz |
+| Frequency deviation | $\pm 100$ Hz |
+| Characteristic frequencies | 1650/1850 Hz |
+| Tolerances of the characteristic frequencies | $\pm 6$ Hz |
+
+The higher characteristic frequency corresponds to a binary "0".
+
+##### **6.4.2.11.1 Test No. 10A: Canceller operation on the calling station side**
+
+The convergence test procedure is to reset the H register and to inhibit adaptation. Then adaptation is enabled while CNG, CED and sequence No. 1 are applied (see Figure 24). During the adaptation interval, the residual/returned echo level is measured. This test should be performed with the NLP both enabled and disabled.
+
+###### **Requirement**
+
+With the H register initially reset and the value $L_{Rin} = -13$ dBm0 for the entire test, the following specific requirements apply for all values of ERL $\geq 6$ dB and echo path delay $t_d \leq \Delta$ ms. The test should run by applying CED and repeating sequence No. 1 four times.
+
+###### *Region I (converging on CED tone)*
+
+- the peaks (see clause 6.4.1.2.2) of $L_{RES}$ should be $\leq \max(-37$ dBm0, $(-13 - A_{ECHO})$ dBm0);
+- the time to enter Region II should be $\leq (0.15$ s $+ t_d)$ with respect to the start of the CED signal.
+
+*Region II (converged on CED tone)*
+
+- the peaks (see clause 6.4.1.2.2) of LRES should be $\leq -37$ dBm0.
+
+*Region III (converging on sequence No. 1)*
+
+- the peaks (see clause 6.4.1.2.2) of LRES should be $\leq \max(-37 \text{ dBm0}, (-13 - A_{\text{ECHO}}) \text{ dBm0})$ ;
+- the time to enter Region IV should be $\leq (1.3 \text{ s} + t_d)$ with respect to the start of the Sequence No. 1 signal.
+
+*Region IV (converged on sequence No. 1)*
+
+- the peaks (see clause 6.4.1.2.2) of LRES should be $\leq -24$ dBm0.
+
+If the NLP is enabled, the peaks (see clause 6.4.1.2.2) of LRET should be $\leq -37$ dBm0 in Regions II and IV.
+
+NOTE – The $-37$ dBm0 upper limit on the LRES requirement in Regions I and III is to address an issue with the quantization error that may occur with low level A-law signals and high values of ERL.
+
+
+
+The diagram illustrates the signal and time relationships for Test No. 10A. It consists of four horizontal signal lines and several time markers.
+
+- LSin :** Shows a CNG (Continuous Noise Generator) burst. The duration of this burst is specified as 425 to 575 ms.
+- LRin :** Shows a CED (Call Establishment Data) tone. The duration of this tone is specified as 2.6-4 s. This is followed by "Sequence No. 1, 4 times".
+- Adaptation Inhibit Enable:** A signal that is active (high) for a duration of < 2.55 s, starting from the beginning of the CNG burst.
+- LRES :** Shows the residual echo level. It is divided into four regions:
+ - Region I:** The initial convergence region, starting at time $t_d$ .
+ - Region II:** The region after the CED tone.
+ - Region III:** The region after the start of Sequence No. 1.
+ - Region IV:** The final convergence region.
+
+Time markers and constraints:
+
+- A time interval of $\geq 200$ ms is indicated between the start of the CNG burst and the start of the CED tone.
+- A time interval of $75 \pm 20$ ms is indicated between the start of the CED tone and the start of Sequence No. 1.
+- The time to enter Region IV is specified as $\leq (1.3 \text{ s} + t_d)$ .
+- The time to enter Region II is specified as $\leq (0.15 \text{ s} + t_d)$ .
+- The diagram is labeled G.168(09)\_F23.
+
+Figure 24 – Test No. 10A signal and time relationships. The diagram shows four signal levels over time: L\_Sin, L\_Rin, Adaptation Inhibit Enable, and L\_RES. L\_Sin shows a CNG burst of 425 to 575 ms. L\_Rin shows a CED tone of 2.6-4 s, followed by Sequence No. 1, 4 times. Adaptation Inhibit Enable is active for < 2.55 s. L\_RES shows convergence curves in Regions I, II, III, and IV. Time markers include t\_d, (0.15 s + t\_d), and (1.3 s + t\_d).
+
+**Figure 24 – Test No. 10A signal and time relationships**
+
+##### 6.4.2.11.2 Test No. 10B: Canceller operation on the called station side
+
+The convergence test procedure is to reset the H register and to inhibit adaptation. Then adaptation is enabled, while sequence No. 2 is applied (see Figure 25). During the adaptation interval, the residual/returned echo level is measured. This test should be performed with the NLP both enabled and disabled.
+
+###### Requirement
+
+With the H register initially reset and the value $L_{\text{Rin}} = -13$ dBm0 for the entire test, the following specific requirements apply for all values of ERL $\geq 6$ dB and echo path delay $t_d \leq \Delta$ ms. The test should run by repeating sequence No. 2 four times.
+
+*Region I (converging on sequence No. 2)*
+
+- the peaks (see clause 6.4.1.2.2) of LRES should be $\leq \max(-37 \text{ dBm0}, (-13 - A_{\text{ECHO}}) \text{ dBm0})$ ;
+
+- the time to enter Region II should be $\leq (1.3 \text{ s} + t_d)$ with respect to the start of the Sequence No. 2 signal.
+
+*Region II (converged on sequence No. 2)*
+
+- the peaks (see clause 6.4.1.2.2) of $L_{\text{RES}}$ should be $\leq -24 \text{ dBm0}$ .
+
+If the NLP is enabled, the peaks (see clause 6.4.1.2.2) of $L_{\text{RET}}$ should be $\leq -37 \text{ dBm0}$ in Region II.
+
+NOTE – The $-37 \text{ dBm0}$ upper limit on the $L_{\text{RES}}$ requirement in Region I is to address an issue with the quantization error that may occur with low level A-law signals and high values of ERL.
+
+
+
+Figure 25: Test No. 10B signal and time relationships. The diagram shows three signal levels over time. The top signal, L\_Rin, is a constant level until a point, then jumps to a higher level labeled 'Sequence No. 2, 4 times'. The middle signal, 'Adaptation', has two states: 'Inhibit' and 'Enable'. It transitions from 'Inhibit' to 'Enable' at the same time as L\_Rin jumps. A horizontal double-headed arrow between the transition of L\_Rin and the transition of Adaptation is labeled '≥ 200 ms'. The bottom signal, L\_RES, is a constant level until the transition point, then drops sharply and levels off at a lower constant level. The time from the start of the sequence to the start of the L\_RES drop is labeled t\_d. The time from the start of the sequence to the start of Region II is labeled ≤ (1.3 + t\_d)\_s. The diagram is divided into two regions, I and II, by a vertical dashed line. The text 'G.168(15)\_F25' is in the bottom right corner.
+
+**Figure 25 – Test No. 10B signal and time relationships**
+
+##### 6.4.2.11.3 Test No. 10C: Canceller operation on the calling station side during page transmission and page breaks (for further study)
+
+Figure 26 shows the sequence of message exchange for a typical fax transmission consisting of two pages. The sequence begins with an ITU-T V.21 message handshake procedure. Operation and performance of the echo cancellers at each end of the link are tested during this period by Tests 10A and 10B. This test is designed to check the operation and performance of the echo canceller at the calling station side during page transmission and page breaks as shown in Figure 26.
+
+Test 10C uses data files A and B and software implementations of FSK and PSK modems. The test described uses ITU-T V.29 modulation for the transmission of image data, but can be further extended to cover different types of modems such as ITU-T V.17 and ITU-T V.27 *ter* as well as different timing relationships between handshake signals (represented by the ITU-T V.21 modem) and page transmission (represented by the ITU-T V.29 modem). The timing relationship shown in Figure 27 has been designed to mimic the real facsimile T.30 protocol.
+
+
+
+Figure 26: Sequence of message exchange for a typical 2-page fax transmission. The diagram shows two horizontal timelines for 'Calling side' and 'Called side' over 'Time'. The Calling side includes CNG (1100 Hz), TSI/NCC/DCS (V.21), TCF (PSK), IMAGE (PSK), MPS (V.21), IMAGE (PSK), EOP (V.21), and DCN (V.21). The Called side includes CED (2100 Hz), CSI/NSF/DIS (V.21), CFR (V.21), MCF (V.21), and MCF (V.21). Tests 10A and 10B cover the initial sequence, while Test 10C covers the second page sequence.
+
+**Figure 26 – Sequence of message exchange for a typical 2-page fax transmission**
+
+
+
+Figure 27: Canceller operation during page transmission and page breaks. The top part is a block diagram showing ASCII data files A, B, and C connected to V.21 and V.29 modulators/demodulators and an Echo canceller. The bottom part is a graph of signal levels (R\_in, S\_in) over time (t in ms). R\_in shows a V.21 MCF sequence at -13 dBm0. S\_in shows a Simulated V.21 MCF echo at -13-ERL dBm0 and V.29 image data at -13 dBm0, with a timing offset t\_d.
+
+**Figure 27 – Canceller operation during page transmission and page breaks**
+
+The test procedure is to reset the H register and inhibit adaptation. Adaptation is then enabled and the canceller is converged by sending data file A via the ITU-T V.21 modulator, into $R_{in}$ of the echo canceller (see Figure 27). This is meant to simulate the MCF signal transmitted by the called fax machine at the end of the first page. To simulate the echo signal, data file A is also transmitted (using the ITU-T V.21 modulator) to the echo canceller's $S_{in}$ input, at a level of $\geq 6$ dB below $R_{in}$ and with a timing offset of $t_d$ . Following this, data file B is transmitted (using the ITU-T V.29 modulator) to the echo canceller's $S_{in}$ input.
+
+The ITU-T V.29 data from the echo canceller's $S_{out}$ output is first collected, stored and demodulated off-line. The recovered file C is then analysed. The data from the echo canceller's $R_{out}$ output is discarded (on the assumption that no impairments are introduced).
+
+Note that in the latest version of T.30, an echo protect tone (EPT) is specified before all ITU-T V.29 transmissions (TCF and image data). This EPT signal was originally intended to "turn around" echo suppressors and prevent any front-end clipping of TCF or image data. In the case of echo cancellers, it helps to open the NLP before the transmission of TCF or image data to avoid corruption. However, many of the fax implementations currently in the field do not incorporate this EPT signal, so it has not been included in this test. In this respect, this test therefore represents a worst-case scenario.
+
+The NLP should be enabled during this test. Note that some echo cancellers will automatically disable the NLP on detection of a 2100 Hz tone.
+
+###### Data File A
+
+In the following table, all data is given in hex. The initial flag is repeated 37 times.
+
+| Flag | HDLC address field | HDLC control field | Control field MCF | Frame check sequence | Flag |
+|------|--------------------|--------------------|-------------------|----------------------|------|
+| 7E | FF | C8 | B1 | D4, 07 | 7E |
+
+###### Data File B
+
+Data File B should be taken from the following ITU-T CD-ROM:
+
+- ITU-T Recommendation T.24 (1998), *Standardized digitized image set*, Document No. 1, "slerexe" letter.
+
+##### Requirement
+
+The intent is to compare the results with the echo canceller first disabled and then enabled. The actual requirements are for further study. The requirements should be based on a comparison of files B and C.
+
+#### 6.4.2.12 Test No. 11 – Tandem echo canceller test (for further study)
+
+This test is meant to ensure that echo cancellers operating in tandem will not degrade the quality of a call below acceptable limits. See [ITU-T G.161] for further discussion on this issue. The following points summarize the philosophy of the approach to this test:
+
+- The echo canceller "under test" should be used in both positions (cancelled end and tandemed – see Figure 28). This is the simplest case and avoids the necessity to test with combinations of other canceller types. The philosophy behind this approach is that if a canceller is designed to perform well in tandem with itself, then it has a good chance of performing well with other types too. It also makes it easier to demonstrate "compliance" to this Recommendation since it means only one set of tests needs to be performed.
+- Neither of the cancellers in the test are controlled (h-reset, etc.). This reduces the complexity of the test and is also representative of what happens in practice (one of the reasons that tandem echo cancellers will appear in the field is if they are not controlled by the switch on call set-up).
+- Only steady state performance is tested. There may be convergence artefacts, but the dominant effect on voice quality as perceived by the users is what happens during steady state.
+
+Figure 28 shows the proposed set-up for the tandem echo canceller test and the conventions used.
+
+
+
+Figure 28 – Test No. 11 configuration. The diagram shows a signal flow from left to right. A 'Signal generator' on the far left connects to an 'Echo path' block. The 'Echo path' block outputs a signal labeled S\_in to a 'Cancelled end echo canceller' (a yellow block labeled 'Echo canceller under test'). This canceller outputs a signal labeled S\_out to an 'Impairments' block containing a 'Delay'. The output of the delay is labeled S\_in and connects to a 'Tandemed echo canceller' (another yellow block labeled 'Echo canceller under test'). This second canceller outputs a signal labeled S\_out to a 'Measurement device' on the far right. A return path is also shown: a 'Signal generator' on the far right outputs a signal labeled R\_in to the 'Tandemed echo canceller'. This canceller outputs a signal labeled R\_out to an 'Impairments' block containing a 'Delay'. The output of this delay is labeled R\_in and connects to the 'Cancelled end echo canceller'. This canceller outputs a signal labeled R\_out back to the 'Echo path' block. The text 'G.168(15)\_F28' is in the bottom right corner of the diagram.
+
+**Figure 28 – Test No. 11 configuration**
+
+Note that the terms *cancelled end* and *tandemed* are used to distinguish between the two echo cancellers. The *cancelled end* echo canceller is the one nearest the echo source and therefore doing most of the work. The *tandemed* echo canceller is the one in tandem furthest from the echo source and doing least work.
+
+The impairments block shows delay. The test should be performed with values of delay both inside and outside the tail capacity of the *tandemed* echo canceller.
+
+**Initial conditions** – To be determined. For example, the canceller either converged to 0 or any other echo path; NLP enabled; etc.
+
+**Test signals** – To be determined.
+
+**Measurement methods** – To be determined.
+
+**Requirements** – TBD.
+
+#### 6.4.2.13 Test No. 12 – Residual acoustic echo test
+
+See clauses I.6.3, I.6.3.1 and [ITU-T G.161] for further discussion on this issue. This test is meant to check the performance of the echo canceller in the presence of residual acoustic echo and to ensure that its performance with electric echo is not overly degraded in the presence of acoustic echo.
+
+The following example of a call to a loud-speaking telephone illustrates the rationale behind this test:
+
+A user makes a call to a loud-speaking telephone. The call is answered first using the handset, and is then switched to loud-speaker mode to share the conversation with other listeners in the room. The call is then returned to handset mode for a private conversation before clearing down.
+
+This scenario is summarized in Figure 29. Phases 1 and 3 correspond to the presence of electric echo only. Phases 1 and 3 have the same "echo" properties, i.e., the same ERL and the same echo path. Phase 2 corresponds to the presence of electric and acoustic echoes. In terms of echo properties, Phase 2 is associated with a lower ERL (presence of residual acoustic echo + electrical echo) and an echo path that is not the same as Phases 1 and 3. An echo canceller involved in such a scenario is required to converge three times during the call.
+
+
+
+```
+
+graph LR
+ subgraph Phase1 [Phase 1]
+ A1[Echo path model A]
+ S1[Initially converged state]
+ end
+ subgraph Phase2 [Phase 2]
+ B[Echo path model B]
+ S2[Re-Convergence measurement]
+ end
+ subgraph Phase3 [Phase 3]
+ A2[Echo path model A]
+ S3[Re-Convergence measurement]
+ end
+ A1 -- "t1: Path and ERL change" --> B
+ B -- "t2: Path and ERL change" --> A2
+
+```
+
+Figure 29: A conversation scenario with acoustic echo. The diagram shows a signal R\_in entering a series of echo path models. The models are labeled 'Echo path model A', 'Echo path model B', and 'Echo path model A' again. The signal passes through these models in three phases: Phase 1 (initially converged state), Phase 2 (re-convergence measurement), and Phase 3 (re-convergence measurement). Vertical dashed lines at t1 and t2 indicate 'Path and ERL change' events. Below the signal path, there are horizontal lines for 'Adaptation Inhibit' and 'Enable'. The 'Adaptation Inhibit' line is active during Phase 2. The 'Enable' line is active during Phases 1 and 3. The diagram is labeled G.168(15)\_F29.
+
+**Figure 29 – A conversation scenario with acoustic echo**
+
+##### Test procedure
+
+The test procedure of Tests 2A should be used for this test. The following echo path characteristics should be used for each phase:
+
+- Phase 1: $ERL_A$ and Echo Path Model A, where $ERL_A \geq 16$ dB
+- Phase 2: $ERL_B = ERL_A - 10$ dB and Echo Path Model B (B not equal to A)
+- Phase 3: $ERL_A$ and Echo Path Model A
+
+NOTE – Echo Path Model A may be any model represented by Figures 6 and 7. Echo Path Model B should be $g(k)$ models $m_4$ , $m_7$ and $m_8$ defined in Annex D, since these models represent echo paths with long dispersion times.
+
+##### Requirement
+
+The convergence requirement of Test 2A(a) should apply to Phase 1 of Figure 29 and the re-convergence requirement of Test 2A(b) should apply to Phases 2 and 3 of Figure 29, without resetting the H-register.
+
+NOTE 1 – The test procedure and requirements defined above do not consider the possibility of non-linear echo paths or echo paths that extend beyond the tail capacity of the echo canceller that may be present in real conversation scenarios.
+
+NOTE 2 – The requirement above is a sub-set of the existing requirements for Test 2.
+
+NOTE 3 – This test may be enhanced by the future addition of test vectors that represent real acoustic echo signals. This enhancement is for further study.
+
+#### 6.4.2.14 Test No. 13 – Performance with ITU-T low-bit rate coders in echo path (optional)
+
+This test is meant to ensure that the echo canceller will not degrade the performance of the network beyond acceptable limits when any ITU-T low-bit rate coder, as stated in the requirement, is included in the echo path of the echo canceller. The user should test the echo canceller using the stated ITU-T low-bit rate coders that may appear in the echo path of the echo canceller in the user's network. See clauses I.5.3, I.5.4 and [ITU-T G.161] for further discussion of ITU-T low-bit rate coders and non-linearities in the echo path.
+
+The test method is to place the echo canceller in the test configuration of Figure 30. Tests 2A and 2B are performed with the echo canceller disabled, and the residual echo level measured using a meter conforming to the characteristics of clause 6.4.1.2.1. The highest measured level is used as a baseline for the next stage of the test. Tests 2A and 2B are then repeated with the echo canceller enabled and the performance is compared with the baseline.
+
+The impact on speech quality performance by low-bit-rate coders in the echo path is for further study.
+
+
+
+Figure 30 – Test No. 13 configuration diagram. The diagram shows a signal flow from a 'Signal generator N' through an 'End path' block. The output of the 'End path' is split into two 'See A below' blocks. The top 'See A below' block outputs S\_in to an 'Echo canceller' block. The bottom 'See A below' block receives R\_out from the 'Echo canceller' block. The 'Echo canceller' block outputs S\_out to a 'Measurement device' block and receives R\_in from a 'Signal generator' block. Below the main diagram, a box labeled 'A' contains an 'Encoder' block followed by a 'Decoder' block. A note below the 'Encoder' and 'Decoder' blocks states: 'NOTE – This assumes that the decoder/encoder accepts and produces digital signals.' The diagram is labeled G.168(15) F 30.
+
+**Figure 30 – Test No. 13 configuration**
+
+NOTE 1 – The interface to the echo canceller shown in Figure 30 conforms to [ITU-T G.711].
+
+##### Requirement
+
+For the stated ITU-T coders, the residual echo power measured (see clause 6.4.1.2.1) with the echo canceller enabled should be no more than 0.5 dB greater than the measured baseline with the echo canceller disabled. In addition, no peaks (see clause 6.4.1.2.2) are allowed that exceed 5 dB above the measured baseline with the echo canceller disabled. The coders for which this test is applicable are to be stated by the user.
+
+NOTE 2 – This test includes non-linear echo path. See clauses I.5.3, I.5.4, I.6.3 and [ITU-T G.161] for further discussion on this issue.
+
+NOTE 3 – A low bit-rate coder exhibits a finite throughput delay. This throughput delay will be present in the echo path of the echo canceller and should be taken into account when performing this test, such that the overall delay in the echo path does not exceed the tail capacity of the echo canceller.
+
+NOTE 4 – The 0.5 dB tolerance is to allow for statistical variations in the measurement process. The intent is to allow a practical tolerance that is effectively inaudible.
+
+#### 6.4.2.15 Test No. 14 – Performance with V-series low-speed data modems
+
+This test is meant to ensure that echo cancellers will not impair the performance of data modems and text telephones that do not disable, or allow the re-enabling of the network echo cancellers. This includes the following two cases:
+
+- i) the network echo cancellers are not disabled at the start of the call and remain enabled for the duration of the call;
+- ii) the network echo cancellers are disabled at the start of the call, but are re-enabled at some point or points during the call.
+
+NOTE 1 – Text telephones commonly use different modes of operation, including switching back and forth between voice and text during the call. The switching back and forth between text and voice is the basic operational mode of textphones of type TIA 825, ITU-T V.21 110 bits/s half duplex and DTMF. [ITU-T V.18] describes an automoding procedure that collects many textphone types into one connection procedure in order to provide backwards compatibility. [ITU-T V.18] describes briefly the modulations and operating characteristics of the text telephone types. Different types dominate in different regions, but users may travel and expect to be able to use the textphones anywhere.
+
+The scope of the test is to cover modems and text telephones that operate over the global PSTN. In practice, the set of modem types given in Table 4 represents a practical sub-set that should be used for testing. For each application listed in Table 4, a number of different modem types are also given. This test should be performed with each application and its associated modem types listed in Table 4. The intent is to allow the echo canceller vendor to demonstrate acceptable performance with a range of different modem types and for the network operator to gain a level of confidence that existing modem traffic will not be impaired.
+
+Table 4 represents a practical sub-set of modems that are mandatory for this test. In practice, developers are encouraged to test with as wide a range of different modems as possible. A more comprehensive list (although not all inclusive) is given in Appendix V.
+
+The performance criteria for this test depend on the type of modem being tested. In general, for low speed data modems, bit error rate (BER) is used to measure performance (measured synchronously where possible). For text telephones, however, character error rate is more appropriate. The performance criteria that should be used for each type of modem are given in Table 4.
+
+##### Test method
+
+The sequence for this test is to measure the performance of each modem type with the echo canceller DISABLED and compare this performance with the echo canceller ENABLED. The philosophy is that when enabled, the echo canceller should not degrade performance compared to that when disabled.
+
+The echo canceller is placed in the test configuration of Figure 31. The test procedure is to first disable the echo cancellers and allow the modems to train. The modems are then operated for the time it takes to send the minimum volume of test data as defined for each modem type given in Table 4 (e.g., bit error rate, character error rate, etc.). This performance is noted and the test is then repeated with the echo cancellers enabled. First reset the H-register and ensure the NLP is enabled before allowing the modems to train.
+
+In the test set-up, the artificial 2-wire lines and the hybrids should simulate the actual range of echo paths that the echo canceller under test is intended to cope with. For the hybrid, this means a specification of the equivalent balance network.
+
+NOTE 2 – Examples of typical balance networks are given in Figure 11 of [ITU-T Q.552].
+
+For the artificial line, this means a specification of the fundamental cable parameters, e.g., ohms/km and nF/km for unloaded cables. The length of the artificial lines should be variable. Test cases should include minimum and maximum lengths as well as that length for which the highest weighted echo loss, calculated according to [ITU-T G.122], is obtained.
+
+The hybrid and artificial line arrangements should be equal at each side of the test set-up.
+
+NOTE 3 – When evaluating the suitability of an echo canceller for a specific network, the test configuration of Figure 31 is well-suited to the purpose of Test 14. However, for generalized evaluation across a range of networks, the number of different real hybrids, balancing networks and proprietary modems makes full and thorough testing complex. In this context, 4-wire software emulations of the modems and the ranges of echo path models defined in Figures 6 and 7 provide an efficient test environment, and can be used to supplement the 2-wire modems and real hybrids of Figure 31. For these cases, line emulations would be used in place of the 2-wire artificial lines.
+
+The values of the settings should be as follows:
+
+R1, R2 = 6 dB to simulate access/egress loss.
+
+T1 = 3 dB to 9 dB (3 dB is the nominal level, 9 dB simulates a 6 dB level offset).
+
+T2 = 3 dB.
+
+DR1, DR2 = echo path delay $\leq \Delta$ ms.
+
+N1, N2 = set to produce signal-to-noise ratios of not less than 25 dB, and, no noise.
+
+D1, D2 = set to produce a round trip delay of up to 520 ms, with D1 = D2.
+
+The transmit level at the 2-wire interface of a modem is determined by the regulations applying to the particular country in which the modem is used. This level is usually factory pre-set and is not adjustable by the user. For Test 14, where it is desired to vary the levels at the input to the network echo cancellers, this can be achieved by the use of different lengths of artificial line (W1 and W2 in Figure 31) together with the transmit attenuators T1 and T2.
+
+##### **Requirement**
+
+With the H register initially reset and the NLP enabled, for the conditions specified above, the percentage of data errors should not increase when the echo canceller is enabled, compared with when the echo canceller is disabled, when data is exchanged between the two terminals for the given minimum volume of data transmitted.
+
+**Table 4 – Minimum set of modems to be used for Test 14**
+
+| Application | Modulation type | Data rate (bits/s) | Answer tone | Performance criteria | Minimum volume of data | Comments |
+|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Dial-up data | ITU-T V.21 ITU-T V.22 bis | ITU-T V.21: 300 ITU-T V.22 bis : 1200 and 2400 | ANS | BER | ITU-T V.21: 20 kbits ITU-T V.22 bis : 100 kbits | |
+| Point of sale terminal | ITU-T V.21 ITU-T V.22 bis Bell 103 Bell 212A | ITU-T V.21 and Bell 103: 300 ITU-T V.22 bis : 2400 Bell 212A: 1200 | Proprietary | BER | ITU-T V.21 and Bell 103: 20 kbits ITU-T V.22 bis and Bell 212A: 100 kbits | |
+| Telemetry | ITU-T V.23 | 600 and 1200 | ANS (optional) | BER | 20 kbits | |
+| Text telephone | ITU-T V.18 (Note 7) DTMF (Note 9) ITU-T V.21 110 half duplex low channel (Note 8) ("EDT") ITU-T V.21 300 bits/s full duplex TIA 825A (Baudot) ITU-T V.23 | ITU-T V.18 300 bit/s DTMF rate n/a ITU-T V.21: 110 half duplex low channel ("EDT") ITU-T V.21: 300 full duplex TIA 825A: 45.45 and 50 ITU-T V.23 1200/75 | ITU-T V.18 and ITU-T V.21: ANS (optional) DTMF, TIA 825A and ITU-T V.23: None | Character error rate | ITU-T V.18, ITU-T V.21, TIA 825A and ITU-T V.23: 1000 characters DTMF: 300 characters | |
+| Security/Alarm system | SIA DC-02 SIA DC-05 | Pulse and DTMF: 10 to 33 pulses/s Bell 103: 300 | Various handshake tones | Character error rate | 300 characters | The SIA standards specify a number of different pulse, DTMF and FSK formats for use by security/alarm systems. In addition, SIA DC-03 specifies a standard protocol for use with Bell 103 systems. |
+
+**Table 4 – Minimum set of modems to be used for Test 14**
+
+| Application | Modulation type | Data rate (bits/s) | Answer tone | Performance criteria | Minimum volume of data | Comments |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------|--------------------|-----------------------------|-------------------------------|-----------------|
+| Leased line dial back-up | Bell 208 A/B Bell 202 | Bell 208 A/B: 4800 Bell 202: 1200 | Unknown | BER | 100 kbits | |
+| Key to abbreviations: ANS 2100 Hz Answer Tone as defined in ITU-T V.25 BER Bit Error Rate NOTE 1 – Where possible, synchronous testing should be performed, since this more accurately detects bit errors due to transmission problems. The exceptions to this are ITU-T V.21 and Bell 103, which are usually tested in asynchronous mode. In general, error correction should be switched off. NOTE 2 – Point of sale modems may use standard and proprietary versions of modulations. NOTE 3 – Security and Alarm system modems may use standard and proprietary versions of modulations. NOTE 4 – SIA DC-02 Security Industry Association (SIA) General Protocols – Available from www.siaonline.org NOTE 5 – SIA DC-03 Security Industry Association (SIA) SIA Format – Available from www.siaonline.org NOTE 6 – SIA DC-05 Security Industry Association (SIA) Ademco Contact ID Standard – Available from www.siaonline.org NOTE 7 – ITU-T V.18 is an automoding procedure using ITU-T V.8 and all other textphone modulations. ITU-T V.8 uses ITU-T V.21 300 bits/s one channel at a time both before and after ANSAM. Full information is found in ITU-T V.18 and ITU-T V.8. NOTE 8 – ITU-T V.21 110 bits/s half duplex is used for EDT, a legacy sub-mode of ITU-T V.18. Only lower channel is used. Pauses between text transmissions are silent or used for voice. EDT is used for text telephony in Germany, Italy, Spain and Switzerland. NOTE 9 – DTMF is for textphone based on DTMF coded text. | | | | | | |
+
+
+
+| | | | |
+|----------|------------------|--------|---------------------|
+| CB | Channel bank | N1, N2 | Noise generator |
+| D1, D2 | Long-haul delay | PA | Protocol analyzer |
+| DR1, DR2 | Echo path delay | R1, R2 | Receive attenuator |
+| EC1, EC2 | Echo canceller | T1, T2 | Transmit attenuator |
+| H1, H2 | Hybrid | W1, W2 | Wire simulator |
+| M1, M2 | Modem under test | | |
+
+G.168(15)\_F31
+
+Figure 31 – Test No. 14 configuration. A block diagram showing a test setup for echo cancellation. The signal path starts from M1/PA through W1 to H1. From H1, it splits to T1 (with noise N1 added) and R1. The T1 path goes through CB, EC1, D1, DR2, and another CB to R2 and H2. The H2 path goes through W2 to M2/PA. A return path goes from H2 through T2 (with noise N2 added) to the second CB, then through EC2, D2, DR1, and the first CB back to R1 and H1.
+
+**Figure 31 – Test No. 14 configuration**
+
+#### 6.4.2.16 Test No. 15 – PCM offset test (Optional)
+
+This test is meant to ensure that the echo canceller will operate properly in the presence of PCM offset in the speech signal applied to $S_{in}$ or in the speech signal applied to $R_{in}$ .
+
+PCM offset is an unwanted, fixed DC level in the $S_{in}$ signal relative to the $R_{out}$ signal, or in the $R_{in}$ signal itself. This can be caused by some network equipment, such as A/D converters, and can result in degraded performance of echo canceller and other speech processing equipment. The methods consist of performing Test 2B, but with a DC offset applied at $S_{in}$ or $R_{in}$ .
+
+##### Part 1
+
+Apply a PCM offset error to the $S_{in}$ signal relative to the $R_{in}$ signal as indicated in Figure 32. Depending on the preference by the users, the PCM offset can be injected at point A – the linear domain, or at point B – the $A/\mu$ law domain.
+
+NOTE 1 – Offset injection at point B is not a linear operation.
+
+
+
+Figure 32: Test configuration for Sin PCM offset test. The diagram shows a signal flow from Sgen through a G.711/G.712 A/D converter and an A/μ PCM block into a summing junction (point A). A feedback signal from g(k) is added at this junction. The signal then passes through another PCM A/μ block (point B) into an Echo canceller as Sin. The Echo canceller's output Sout is measured by a Measurement device. The Echo canceller also receives an Rin signal from a G.711/G.712 A/D converter connected to a Signal generator. Control inputs for the Echo canceller include 'H register to zero (reset)', 'Inhibit convergence', and 'Disable non-linear processing'. A dashed box encloses the A/D converter, PCM blocks, summing junction, and g(k) block, with a label 'Linear domain' on the left and 'A/μ law domain' on the right of the second PCM block.
+
+**Figure 32 – Test configuration for $S_{in}$ PCM offset test**
+
+##### **Part 2**
+
+Apply a PCM offset error to the $R_{in}$ signal as indicated in Figure 33. Depending on the preference by the users, the PCM offset can be injected at point A – the linear domain, or at point B – the A/μ law domain.
+
+NOTE 2 – Offset injection at point B is not a linear operation.
+
+
+
+Figure 33: Test configuration for Rin PCM offset test. This diagram is similar to Figure 32 but focuses on the Rin signal path. The Rin signal path from the Signal generator passes through a G.711/G.712 A/D converter. Point B is located at the input of this A/D converter (A/μ law domain), and point A is at its output (linear domain). The Echo canceller receives Rin and outputs Sout to a Measurement device. A dashed box encloses the signal processing components for Sin. Control signals for the echo canceller are shown at the bottom.
+
+**Figure 33 – Test configuration for $R_{in}$ PCM offset test**
+
+The level at $R_{in}$ in the test requirement is $L_{R_{in,act}}$ . It is the signal level measure using the RMS method over the active portion of the CSS only (i.e., excluding the pause of the CSS) as described in clause 6.4.1.2.
+
+##### Requirement
+
+For both Part 1 and Part 2 above, with the H register initially reset, or alternatively, with an open echo path resulting in $S_{in} = 0$ , the H register content is converged to 0, and then the adaptation is inhibited. Adaptation is then enabled at least 200 ms before a DC offset at a level of $-40$ dBm0 is injected at either point A or point B in Figure 32 (for the Part 1 test) or Figure 33 (for the Part 2 test). The first CSS burst is applied to $R_{in}$ at the same instant the DC offset is applied. With the NLP disabled, for all values $L_{Rin,act} \geq -30$ dBm0 and $\leq 0$ dBm0 and for all values of ERL $\geq 6$ dB and echo path delay, $t_d \leq \Delta$ ms, the loss $L_{Rin,act} - L_{RES}$ should be greater than or equal to that shown in Figure 12a. The level at $S_{out}$ is measured using a meter conforming to the characteristics of clause 6.4.1.2.1. In addition, no peaks (see clause 6.4.1.2.2) are allowed that exceed 5 dB above the requirements in Figure 11.
+
+The variable $L_{Rin,act} - L_{RES}$ in Figure 12a may be replaced by the variable $L_{Sin} - L_{Sout} + ERL$ , where $L_{Sin}$ and $L_{Sout}$ are the levels of $S_{in}$ and $S_{out}$ respectively. The signal levels $L_{Sin}$ and $L_{Sout}$ are measured using the measurement device in clause 6.4.1.2.1, and should be synchronized. The ERL is the value chosen in the test. This method may also be used to observe convergence as a continuous plot over time.
+
+NOTE 3 – The method stated in the preceding paragraph takes into account any dispersion in the echo path, but does not take into account any dispersion present between the $S_{in}$ and $S_{out}$ ports of the echo canceller.
+
+NOTE 4 – As the level measurement device includes a band-pass filter, this test does not imply that the echo canceller must remove the DC offset.
+
+NOTE 5 – This test includes a non-linear echo path. See clauses I.5.3, I.5.4 and [ITU-T G.161] for further discussion on this issue.
+
+#### 6.4.2.17 Test No. 16 – Dual Tone Multi-Frequency (DTMF) transparency test (optional)
+
+This test has the objective of verifying that the echo canceller will transmit, without excessive distortions, narrow-band signals (specifically, DTMF digits) applied at $S_{gen}$ , during the presence of the dial tone or human voice (emulated by the CSS for testing purposes) which is applied at $R_{in}$ . The echo canceller's adaptation is enabled throughout the entire test. The NLP should be enabled.
+
+Both parts of this test are optional, depending on the nature of the echo canceller deployment. Details of when to perform each test are given in the individual test descriptions.
+
+##### 6.4.2.17.1 Test 16A: DTMF transparency in the presence of a dial tone (optional)
+
+The method consists of enabling adaptation prior to applying the dial tone. After the dial tone is applied, a DTMF digit sequence is applied at $S_{gen}$ . The sequence is to continue so that at least one DTMF digit is present after the dial tone is terminated.
+
+The optional nature of this test is motivated by the fact that the echo cancellers that are controlled by central office or gateway actions may not need to conform to this test.
+
+###### Test method
+
+The echo canceller is enabled. NLP is enabled. The test is to be performed for all values of ERL $\geq 6$ dB. Once chosen, the echo path (along with its ERL as well as $t_r$ ) remains the same throughout the test. The dial tone levels are to be within the range of $[-15$ dBm0, $-5$ dBm0], see [ITU-T E.180]. The DTMF levels and the timing are to be within the range specified in Table A.1 of [ITU-T Q.24]. The timing of the dial tone and DTMF tones has to be such that the first DTMF digit applied at $S_{gen}$ has to be delayed with respect to the start of the dial tone by $T_{ad}$ ( $T_{ad} > 400$ ms) (see Figure 34). The dial tone shall last for $T_{dto} > 40$ ms (40 ms represents a typical DTMF detection time) beyond the start of the first DTMF digit. At least one digit should be applied after the dial tone is removed (see Figures 35 and 36).
+
+
+
+Timing diagram illustrating requirements for DTMF transparency in the presence of dial tone. It shows four signal lines: Rin, Sgen, Sin, and Sout over time (t). Rin has a continuous tone of duration Tdt. Sgen has five pulses starting at t0, with the first pulse delayed by Tdto from the start of Rin. Sin has a tone of duration Tad starting at t0, followed by five pulses. Sout has an adaptation signal starting at t0, followed by five pulses. An 'Inhibit' signal is active before t0, and an 'Enable' signal is active after t0 for a duration of > 200ms. The diagram is labeled G.168(15) F34.
+
+**Figure 34 – Illustration of requirements for DTMF transparency in the presence of dial tone**
+
+###### Requirements
+
+###### *Specific requirements for DTMF digit/sequence selection*
+
+The DTMF test sequence should consist of 5 different DTMF digits selected from the set of {0,...,9, #, \*, A, B, C, D}, see [ITU-T Q.23]. The minimum sub-set of test conditions is proposed to include 16 DTMF sequences that are to be tested. The sequences are built by placing all possible digits at the front of the sequences while the remaining four digits in each sequence should be taken from the full set such that every digit in the sequence is different. Table 5 defines the sequences.
+
+**Table 5 – DTMF test sequences (as per minimum sub-set of test conditions)**
+
+| Sequence No. | 1st digit | 2nd digit | 3rd digit | 4th digit | 5th digit |
+|--------------|-----------|-----------|-----------|-----------|-----------|
+| 1 | 0 | 1 | 2 | 3 | 4 |
+| 2 | 1 | 2 | 3 | 4 | 5 |
+| 3 | 2 | 3 | 4 | 5 | 6 |
+| 4 | 3 | 4 | 5 | 6 | 7 |
+| 5 | 4 | 5 | 6 | 7 | 8 |
+| 6 | 5 | 6 | 7 | 8 | 9 |
+| 7 | 6 | 7 | 8 | 9 | # |
+| 8 | 7 | 8 | 9 | # | * |
+
+**Table 5 – DTMF test sequences (as per minimum sub-set of test conditions)**
+
+| Sequence No. | 1st digit | 2nd digit | 3rd digit | 4th digit | 5th digit |
+|--------------|-----------|-----------|-----------|-----------|-----------|
+| 9 | 8 | 9 | # | * | A |
+| 10 | 9 | # | * | A | B |
+| 11 | # | * | A | B | C |
+| 12 | * | A | B | C | D |
+| 13 | A | B | C | D | 0 |
+| 14 | B | C | D | 0 | 1 |
+| 15 | C | D | 0 | 1 | 2 |
+| 16 | D | 0 | 1 | 2 | 3 |
+
+###### *Specific requirements for DTMF versus dial tone timing*
+
+Two versions of timing constitute the minimum sub-set of test conditions.
+
+The first version of timing includes the full overlap of four DTMF digits with the dial tone (see Figure 35). The duration $T_{dt}$ of the dial tone is defined as 1000 ms. The first DTMF digit starts at $T_{ad} = 450$ ms after the start of the dial tone. The length of each DTMF digit is 50 ms. The interval between the DTMF digits is 100 ms.
+
+
+
+The diagram illustrates the timing for 'fast' DTMF reaction. The top signal, $R_{in}$ , is a continuous dial tone starting at $t_0$ and ending at $t_0 + T_{dt}$ , where $T_{dt} = 1000$ ms. The middle signal, $S_{gen}$ , consists of five DTMF digits. The first digit starts at $t_0 + T_{ad}$ , where $T_{ad} = 450$ ms. Each digit has a duration of 50 ms, and there is a 100 ms interval between consecutive digits. The bottom signal, $S_{in}$ , is the sum of the dial tone and the DTMF digits. Below the signals, the 'Adaptation' signal is shown as a step function. The 'Inhibit' signal is high initially and goes low at $t_0$ . The 'Enable' signal goes high at $t_0 + > 200$ ms.
+
+Timing diagram for Figure 35 showing signal levels for Rin, Sgen, and Sin over time. Rin shows a continuous dial tone of duration Tdt = 1000 ms. Sgen shows five DTMF digits, each 50 ms long, starting at Tad = 450 ms, with 100 ms intervals between them. Sin shows the combined signal. Adaptation and Inhibit/Enable signals are also shown, with the Enable signal going high > 200 ms after the start of the dial tone.
+
+**Figure 35 – Test timing version 1: "fast" DTMF reaction and a "slow" removal of the dial tone**
+
+The second version of timing includes a partial overlap of the first DTMF digit with the dial tone (see Figure 36). The duration $T_{dt}$ of the dial tone is defined as 2030 ms. The first DTMF digit starts at
+
+$T_{ad} = 2000$ ms after the start of the dial tone. The length of each DTMF digit is 50 ms. The interval between the DTMF digits is 100 ms.
+
+
+
+Figure 36: Test timing version 2. A timing diagram showing three signal lines: R\_in, S\_gen, and S\_in. R\_in shows a continuous dial tone starting at t\_0. S\_gen shows five DTMF digits starting at T\_ad = 2000 ms, with each digit lasting 50 ms and a 100 ms gap between them. S\_in shows the received signal, which includes the dial tone until the first DTMF digit is detected at T\_ad = 2030 ms (T\_dial), at which point the dial tone is removed and the DTMF digits are received. Below the signals, an 'Adaptation' line is high from t\_0 to the start of the first digit. An 'Inhibit' line is high from t\_0 to the start of the first digit. An 'Enable' line is low from t\_0 to the start of the first digit, then goes high for a duration of > 200 ms.
+
+G.168(15) F36
+
+**Figure 36 – Test timing version 2: a "typical" DTMF reaction and an almost instantaneous removal of the dial tone upon detection of the first DTMF digit by the system**
+
+Specific requirements for the levels of DTMF digits and dial tone as well as the echo path models and ERL values
+
+While the proposed requirements for this test include all valid dial tone and DTMF tone parameters combined with all $ERL \geq 6$ dB and all echo path models, the minimum sub-set of test conditions consists of:
+
+- Dial tone levels: range of $[-15 \text{ dBm0}, -5 \text{ dBm0}]$ see [ITU-T E.180], with steps of 5 dB;
+- DTMF levels: range of $[-27 \text{ dBm0}, -6 \text{ dBm0}]$ see [ITU-T Q.24], Table A.1, with steps of 3 dB;
+- ERL values: range of $[6 \text{ dB}, 30 \text{ dB}]$ , with steps of 3 dB;
+- Echo path model: ITU-T G.168 model $m_1$ ;
+- Pure delay: $t_r = 0$
+
+NOTE – The minimum sub-set of test conditions is limited to the normative frequencies (DTMF and dial tone) and no twist (DTMF). No DTMF distortions and/or electrical noise simulation make part of the minimum sub-set of test conditions.
+
+###### *Specific requirements for DTMF at $S_{out}$ : DTMF detection scores*
+
+The method of determining whether the echo canceller distorts the DTMF digits beyond recognition uses a DTMF tone detector compliant with [ITU-T Q.24]. Signals $S_{out}$ (for echo canceller enabled) and $S_{out}$ (for echo canceller disabled), as generated using the test vectors defined in Table 5, should be applied to the DTMF tone detector. The DTMF detection score for the case with echo canceller enabled should not be lower than for the case of echo canceller disabled.
+
+##### **6.4.2.17.2 Test 16B: DTMF transparency in the presence of speech (optional)**
+
+The test method includes enabling adaptation prior to applying the CSS. After the CSS is applied, a DTMF digit sequence is applied at $S_{\text{gen}}$ . The sequence is to continue so that at least one DTMF digit is present after the CSS is terminated.
+
+The optional nature of this test is motivated by the fact that there are TDM switches/gateway architectures where a DTMF detector component follows the echo canceller component (i.e., where the $S_{\text{out}}$ signal becomes the input signal to the DTMF detector). In such a case, this test is necessary. Otherwise (i.e., where the DTMF detectors receive the $S_{\text{in}}$ signal), this test is not required.
+
+###### **Test method**
+
+The echo canceller is enabled. NLP is enabled. Once chosen, the echo path (including its ERL as well as the $t_r$ ) remains the same throughout the test. The test is to be performed for all values of ERL $\geq 6$ dB. The CSS levels are to be within the range of $[-15 \text{ dBm}0, -5 \text{ dBm}0]$ . The DTMF levels and the timing are to be within the range specified in Table A.1 of [ITU-T Q.24]. The timing of the CSS and DTMF tones has to be such that the first DTMF digit applied at $S_{\text{gen}}$ has to be delayed with respect to the start of the CSS by $T_{\text{ad}}$ ( $T_{\text{ad}} > 1500$ ms) (see Figure 37). At least one digit (but not more than two digits) shall be applied following the time when the CSS is removed.
+
+The convergence characteristic during the time the CSS is present at $R_{\text{in}}$ and $S_{\text{gen}}$ is silence (the time duration of $T_{\text{ad}}$ ) should conform to Test No. 2A(a) requirements, as illustrated in Figure 10a with pure delay $t_r = 0$ .
+
+###### **Requirements**
+
+###### *Specific requirements for DTMF digit/sequence selection*
+
+The DTMF test sequence should consist of DTMF digits selected from the set of $\{0, \dots, 9, \#, *, A, B, C, D\}$ . The minimum sub-set of test conditions is proposed to include any 4 of 16 DTMF sequences that cover the entire DTMF digit set (for example, Sequences No. 1, 6, 11 and 16). Note that the sequences are built by placing all possible digits at the front of the sequences, while the remaining four digits in each sequence should be taken from the full set, such that every digit in the sequence is different. Table 6 defines the sequences.
+
+
+
+Detailed description of Figure 37: The diagram consists of four horizontal axes representing signals over time: Rin , Sgen , Sin , and Sout .
+1. Rin : Shows a sequence of five shaded blocks representing CSS bursts. A horizontal double-headed arrow labeled $T_{dt}$ spans from the start of the first burst to the end of the fifth burst.
+2. Sgen : Shows a sequence of DTMF digits (represented by vertical bars). The first digit starts at a time $T_{ad}$ after the start of the CSS. There are four digits shown, followed by an ellipsis and a final digit.
+3. Sin : Shows the superposition of Rin and Sgen . The first four DTMF digits overlap with the CSS bursts.
+4. Sout : Shows the output signal. It starts with a decaying signal labeled 'Convergence requirements as per Test 2A(a)'. The DTMF digits appear later in the timeline.
+Below the axes, there is a timing diagram for 'Adaptation', 'Inhibit', and 'Enable' states. A vertical dashed line marks $t_0$ . A horizontal arrow indicates a duration of $> 200$ ms between a state change and $t_0$ .
+
+Figure 37: Illustration of requirements for DTMF transparency in the presence of CSS. The diagram shows four signal timelines: R\_in, S\_gen, S\_in, and S\_out. R\_in shows a Continuous Speech Signal (CSS) with duration T\_dt. S\_gen shows DTMF digits starting at T\_ad after the start of the CSS. S\_in shows the combined signal. S\_out shows the output signal with adaptation and inhibition. A vertical dashed line marks t\_0. A horizontal double-headed arrow indicates a duration of > 200 ms between t\_0 and the start of the adaptation. Labels include 'Convergence requirements as per Test 2A(a)', 'Inhibit', and 'Enable'.
+
+G.168(15)\_F37
+
+**Figure 37 – Illustration of requirements for DTMF transparency in the presence of CSS**
+
+###### *Specific requirements for DTMF versus announcement/speech (CSS) timing*
+
+The timing relationship specified here constitutes a minimum sub-set of test conditions.
+
+**Mandatory:** The first five digits in Table 6 (1st digit to 5th digit) are used. The timing relationship includes at least a partial overlap of four DTMF digits with the CSS (see Figure 37), while the fifth digit does not overlap the CSS. The duration $T_{dt}$ of the CSS is defined as 2000 ms. The first DTMF digit starts at $T_{ad} = 1500$ ms after the start of the CSS. The length of each DTMF digit is 50 ms. The interval between the DTMF digits is 100 ms.
+
+**Optional:** All ten DTMF digits in Table 6 are used in order to provide more adequate means for statistical processing of the test results. In the timing relationship, the duration $T_{dt}$ of the CSS is changed to 2700 ms so that the last two DTMF digits do not overlap with CSS pulses. Other timing details remain unchanged per the five DTMF digits case.
+
+###### *Specific requirements for the levels of DTMF digits and CSS as well as the echo path models, ERL and pure delay values*
+
+While the proposed requirements for test setup include all valid CSS and DTMF tone parameters combined with all $ERL \geq 6$ dB and all echo path models, the minimum sub-set of test conditions consists of:
+
+- CSS levels: range of [−15 dBm0, −5 dBm0], with steps of 5 dB;
+- DTMF levels: range of [−27 dBm0, −6 dBm0], see [ITU-T Q.24], with steps of 3 dB;
+- ERL values: range of [6 dB, 30 dB], with steps of 3 dB;
+
+Echo path model: ITU-T G.168 m1 ;
+
+Pure delay: $t_r = 0$ .
+
+NOTE – The minimum sub-set of test conditions is limited to the normative frequencies and twist (DTMF). No DTMF distortions and/or electrical noise simulation make part of the minimum sub-set of test conditions.
+
+*Specific requirements for DTMF at $S_{out}$ : DTMF detection scores*
+
+The method of determining whether the echo canceller distorts the DTMF digits beyond recognition uses a DTMF tone detector compliant with [ITU-T Q.24]. Signals $S_{out}$ (for echo canceller enabled) and $S_{out}$ (for echo canceller disabled), as generated using the test sequences defined in Table 6, should be applied to the DTMF tone detector. The DTMF detection score for the case with echo canceller enabled should not be lower than for the case of echo canceller disabled.
+
+**Table 6 – DTMF test sequences (as per minimum sub-set of test conditions)**
+
+| Set No. | 1st digit | 2nd digit | 3rd digit | 4th digit | 5th digit | 6th digit | 7th digit | 8th digit | 9th digit | 10th digit |
+|---------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|------------|
+| 1 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 |
+| 2 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | # |
+| 3 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | # | * |
+| 4 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | # | * | A |
+| 5 | 4 | 5 | 6 | 7 | 8 | 9 | # | * | A | B |
+| 6 | 5 | 6 | 7 | 8 | 9 | # | * | A | B | C |
+| 7 | 6 | 7 | 8 | 9 | # | * | A | B | C | D |
+| 8 | 7 | 8 | 9 | # | * | A | B | C | D | 0 |
+| 9 | 8 | 9 | # | * | A | B | C | D | 0 | 1 |
+| 10 | 9 | # | * | A | B | C | D | 0 | 1 | 2 |
+| 11 | # | * | A | B | C | D | 0 | 1 | 2 | 3 |
+| 12 | * | A | B | C | D | 0 | 1 | 2 | 3 | 4 |
+| 13 | A | B | C | D | 0 | 1 | 2 | 3 | 4 | 5 |
+| 14 | B | C | D | 0 | 1 | 2 | 3 | 4 | 5 | 6 |
+| 15 | C | D | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
+| 16 | D | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
+
+# 7 Characteristics of an echo canceller tone disabler
+
+## 7.1 General
+
+The echo cancellers covered by this Recommendation should be equipped with a tone detector that conforms to this clause. This tone detector should disable the echo canceller only upon detection of a signal which consists of a 2100 Hz tone with periodic phase reversals inserted in that tone, and not disable with any other in-band signal, e.g., speech or a 2100 Hz tone without phase reversals. The tone disabler should detect and respond to a disabling signal which may be present in either the send or the receive path.
+
+To improve the operation of the echo canceller for fax signals and low-speed voiceband data, it may be beneficial for some echo cancellers to disable the NLP for such calls. In this case, the echo canceller may optionally detect any 2100 Hz tone without phase reversals. If 2100 Hz tone without phase reversal is detected, the echo canceller shall remain enabled, and the NLP may optionally be disabled. The frequency characteristics of the tone detector are given in Figure 38. The tone disabler characteristics as specified in clauses 7.4 through 7.9 also apply for this NLP disabling detector. Note that if the 2100 Hz tone contains phase reversals, then the echo canceller shall be disabled as defined elsewhere in this clause.
+
+The term disabled in this clause refers to a condition in which the echo canceller is configured in such a way as to no longer modify the signals which pass through it in either direction. Under this condition, no echo estimate is subtracted from the send path, the non-linear processor is made transparent, and the delay through the echo canceller still meets the conditions specified in clause 6.4.1. However, no relationship between the circuit conditions before and after disabling should be assumed. The impulse response stored in the echo canceller prior to convergence (and prior to the disabling tone being sent) is arbitrary. This can lead to apparent additional echo paths which, in some echo canceller implementations, remain unchanged until the disabling tone is recognized. Also note that echo suppressors could be on the same circuit and there is no specified relationship between their delay in the enabled and disabled states. In spite of the above, it is possible, for example, to measure the round-trip delay of a circuit with the disabling tone but the trailing edge of the tone burst should be used and sufficient time for all devices to be disabled should be allotted before terminating the disabling tone and starting the timing.
+
+It should be noted that the echo canceller should provide 64 kbit/s bit-sequence integrity when disabled.
+
+## 7.2 Detector characteristics
+
+The tone detector shall detect a tone in the frequency range of $2100\text{ Hz} \pm 21\text{ Hz}$ (see [ITU-T V.21]). The detection channel bandwidth should be chosen wide enough to encompass this tone (and possibly other disabling tones used within national networks). At the same time, the detection channel bandwidth should be such that, in conjunction with guard action and timing, adequate protection is provided against false operation of the detector by speech signals. The detector channel sensitivity (threshold level) should be such that the detector will operate on the lowest expected power of the disabling tone. The band characteristics shown in Figure 38 will permit disabling by the 2100 Hz disabling tone as well as others used in North America. The figure indicates that in the frequency band 2079 Hz to 2121 Hz detection **must** be possible whilst in the band 1900 Hz to 2350 Hz detection **may** be possible.
+
+Providing that only the recommended 2100 Hz disabling tone is used internationally, interference with signalling equipment will be avoided.
+
+The dynamic range of the detector should be consistent with the input levels as specified in [ITU-T V.2] with allowances for variation introduced by the public switched telephone network.
+
+
+
+Figure 38: Required disabling band characteristics. A graph showing Disabling signal level (dBm0) on the y-axis (0 to -37) versus Frequency (Hz) on the x-axis (1900 to 2350). The graph is divided into three regions: 'Not disabled' (top, 0 to -27 dBm0), 'Disabled' (middle, -27 to -35 dBm0), and 'Tolerance Region' (bottom, -35 to -37 dBm0). The 'Disabled' region is centered around 2100 Hz, with a width of 200 Hz (2000 to 2200 Hz). The 'Tolerance Region' is a narrow band at the bottom, centered around 2100 Hz, with a width of 100 Hz (2050 to 2150 Hz). The 'Not disabled' regions are on the left (below 1900 Hz) and right (above 2350 Hz). The graph is labeled G.168(15)\_F38.
+
+**Figure 38 – Required disabling band characteristics**
+
+### 7.2.1 Phase reversal detection
+
+The echo canceller tone disabler requires the detection of a 2100 Hz tone with periodic phase reversals which occur every $450 \pm 25$ ms. The characteristics of the transmitted signal are defined in [ITU-T V.25] and [ITU-T V.8]. Phase variations in the range of $180^\circ \pm 25^\circ$ should be detected while those in the range of $0^\circ \pm 110^\circ$ should not be detected. This restriction is to minimize the probability of false disabling of the echo canceller due to speech currents and network-induced phase changes. The $\pm 110^\circ$ range represents the approximate phase shift caused by a single frame slip in a PCM system.
+
+## 7.3 Guardband characteristics
+
+Energy in the voice band, excluding the disable band, must be used to oppose disabling so that speech will not falsely operate the tone disabler. The guard band should be wide enough and with a sensitivity such that the speech energy outside the disabling band is utilized. The sensitivity and shape of the guard band must not be such that the maximum idle or busy circuit noise will prevent disabling. In the requirement, white noise is used to simulate speech and circuit noise. Thus, the requirement follows:
+
+Given that white noise (in a band of approximately 300-3400 Hz) is applied to the tone disabler simultaneously with a 2100 Hz signal, the 2100 Hz signal is applied at a level 3 dB above the midband disabler threshold level. The white noise energy level required to inhibit disabling should be no greater than the level of the 2100 Hz signal and no less than a level 5 dB below the level of the 2100 Hz signal. As the level of the 2100 Hz signal is increased over the range of levels to 30 dB above the midband disabler threshold level, the white noise energy level required to inhibit disabling should always be less than the 2100 Hz signal level. These requirements, together with the noise tolerance requirements given in clause 7.3.1 are illustrated in Figure 39.
+
+
+
+Figure 39: Guardband and noise tolerance requirements. A vertical diagram showing SNR levels from 0 dB to 11 dB and below. The top section (above 0 dB) is labeled 'Should not disable'. The section between 0 dB and 5 dB is shaded with diagonal lines and labeled 'May or may not disable'. The section between 5 dB and 11 dB is also shaded with diagonal lines and labeled 'Should disable but increase of 1% error operation allowed per dB reduction in SNR'. The bottom section (below 11 dB) is labeled 'Should disable'. The vertical axis is labeled 'S/N' at the bottom. The diagram is labeled 'G.168(15)\_F39' at the bottom right.
+
+**Figure 39 – Guardband and noise tolerance requirements**
+
+NOTE – The possibility of interference during the phase reversal detection period has been taken into account. One potential source of interference is the presence of calling tone as specified in [ITU-T V.25]. If the calling tone interferes with the detection of the phase reversal, the entire disabling detection sequence is restarted, but only one time. [ITU-T V.25] ensures at least one second of quiet time between calling tone bursts.
+
+### 7.3.1 Noise tolerance
+
+The detector should operate correctly with white noise less than or equal to 11 dB below the level of the 2100 Hz signal. No definitive guidelines can be given for the range between 5 and 11 dB because of the variations in the test equipment used. In particular, performance may vary with the peak-to-average ratio of the noise generator used. As a general guideline, however, the percentage of correct operation (detection of phase variations of $180^\circ \pm 25^\circ$ and non-detection of phase variations of $0^\circ \pm 110^\circ$ ) should fall by no more than 1% for each dB reduction in the signal-to-noise ratio below 11 dB. It is noted that it is possible to design a detector capable of operating correctly at 5 dB signal-to-noise ratio.
+
+## 7.4 Holding-band characteristics
+
+The tone detector, after disabling either the NLP or the echo canceller, should hold the NLP or echo canceller in the disabled state for tones in a range of frequencies specified below. The release sensitivity should be sufficient to maintain disabling for the lowest level data signals expected, but should be such that the detector will release for the maximum idle or busy circuit noise. Thus the requirement follows:
+
+The tone detector should hold the NLP or echo canceller in the disabled state for any single-frequency sinusoid in the band from 390-700 Hz having a level of $-27$ dBm0 or greater, and from 700-3000 Hz having a level of $-31$ dBm0 or greater. The tone disabler should release for any signal in the band from 200-3400 Hz having a level of $-36$ dBm0 or less.
+
+## 7.5 Operate time
+
+The operate time should be sufficiently long to provide immunity from false operation due to voice signals, but not so long as to needlessly extend the time to disable. The tone disabler is required to operate within one second of the receipt of the disabling signal. The one second operate time permits the detection of the 2100 Hz tone and ensures that two-phase reversals will occur.
+
+## 7.6 False operation due to speech currents
+
+It is desirable that the tone disabler should rarely operate falsely on speech. To this end, a reasonable objective is that, for an echo canceller installed on a working circuit, usual speech currents should not
+
+on the average cause more than 10 false operations during 100 hours of speech. In addition to the talk-off protection supplied by the disabling channel bandwidth, by guard band operation and by the operate time, talk-off protection can be supplied by recycling. That is, if speech which simulates the disabling signal is interrupted because of inter-syllabic periods, before disabling has taken place, the operate timing mechanism should reset. However, momentary absence or change of level in a true disabling signal should not reset the timing.
+
+## **7.7 False operation due to data signals**
+
+It is desirable that the tone disabler should rarely operate falsely on data signals from data sets that would be adversely affected by disabling the echo canceller. To this end, a reasonable objective is that, for an echo canceller installed on a working circuit, usual data signals from such data sets should not, on the average, cause more than 10 false operations during 100 hours of data transmissions.
+
+To this end, in the reference tone disabler described in Annex B of [ITU-T G.165], which meets the above requirements, the tone disabler circuitry becomes inoperative if one second of clear (*i.e.*, no phase reversals or other interference) 2100 Hz tone is detected. The detector circuit remains inoperative during the data transmission and only becomes operative again $250 \pm 150$ ms after a signal in the holding band falls at least 3 dB below the maximum holding sensitivity. Thus the possibility of inadvertent disabling of the echo canceller during facsimile or low speed ( $< 9.6$ kbit/s) voiceband data transmission is minimized.
+
+## **7.8 Release time**
+
+The disabler should not release for signal drop-outs less than the ITU-T recommended value of 100 ms. To cause a minimum of impairment upon accidental speech disabling, it should release within $250 \pm 150$ ms after a signal in the holding band falls at least 3 dB below the maximum holding sensitivity in both directions of signal transmission.
+
+## **7.9 Other considerations**
+
+Both the echo of the disabling tone and the echo of the calling tone may disturb the detection of the echo canceller disabling tone. As such, it is not recommended to add the receive and transmit signal inputs together to form an input to a single detector.
+
+Careful attention should be given to the number of phase reversals required for detection of the disabling tone. Some Administrations favour relying on 1 to improve the probability of detection even in the presence of slips, impulse noise, and low signal-to-noise ratio. Other Administrations favour relying on 2 to improve the probability of correctly distinguishing between non-phase-reversed and phase-reversed 2100 Hz tones, and to reduce the likelihood of false triggering of the tone disabler by speech or data signals.
+
+# **8 Non-linear processors (NLPs) for use in echo cancellers**
+
+## **8.1 Scope**
+
+For the purpose of this Recommendation, the term "NLP" is intended to mean only those devices which fall within the definition given in clause 3.21 and which have been proven to be effective in echo cancellers. It is possible to implement such NLPs in a number of ways (centre clippers being just one example), with fixed or adaptive operating features, but no recommendation is made for any particular implementation. General principles and guidelines are given in clause 8.2. More detailed and concrete information requires reference to specific implementations. This is done in Annex B for the particular case of a "reference NLP". The use of this term denotes an implementation given for guidance and illustration only. It does not exclude other implementations nor does it imply that the
+
+reference NLP is necessarily the most appropriate realization on any technical, operational or economic grounds.
+
+## **8.2 General principles and guidelines**
+
+### **8.2.1 Function**
+
+#### **8.2.1.1 General**
+
+The NLP is located in the send path between the output of the subtractor and the send-out port of the echo canceller. Conceptually, it is a device which blocks low level signals and passes high-level signals. Its function is to further reduce the residual echo level ( $L_{\text{RES}}$ as defined in clause 3.25) which remains after imperfect cancellation of the circuit echo so that the necessary low returned echo level ( $L_{\text{RET}}$ as defined in clause 3.26) can be achieved.
+
+#### **8.2.1.2 Network performance**
+
+Imperfect cancellation can occur because echo cancellers which conform to this Recommendation may not be capable of adequately modelling echo paths which generate significant levels of non-linear distortion (see [ITU-T G.161]). Such distortion can occur, for example, in networks conforming to Recommendation [b-ITU-T G.113] in which up to five pairs of PCM codecs (conforming to [ITU-T G.712]) are permitted in an echo path. The accumulated quantization distortion from these codecs may prevent an echo canceller from achieving the necessary $L_{\text{RET}}$ by using linear cancellation techniques alone. It is therefore recommended that all echo cancellers capable only of modelling the linear components of echo paths but intended for general network use should incorporate suitable NLPs. In specific network environments with low delay or high ERL, it may be possible to disable the NLP in an echo canceller with a sufficiently high ERLE. This may result in higher overall speech quality, as NLPs sometimes cause speech degradation.
+
+#### **8.2.1.3 Limitations**
+
+This use of NLPs represents a compromise in the circuit transparency which would be possible by an echo canceller which could achieve the necessary $L_{\text{RET}}$ by using only modelling and cancellation techniques. Ideally, the non-linear processor should not cause distortion of cancelled end speech. In practical devices, it may not be possible to sufficiently approach this ideal. In this case, it is recommended that NLPs should not be active under double talk or cancelled end single speech conditions. From this it follows that excessive dependence should not be placed on the NLP and that $L_{\text{RES}}$ should be low enough to prevent objectionable echo under double talk conditions.
+
+#### **8.2.1.4 Data transmission**
+
+NLPs may affect the transmission of data through an enabled echo canceller. This is under study.
+
+### **8.2.2 Suppression threshold**
+
+#### **8.2.2.1 General**
+
+The suppression threshold level ( $T_{\text{SUP}}$ ) of an NLP is expressed in dBm0 and is equal to the highest level of a sine-wave signal at a given moment that is just suppressed. Either fixed or adaptive suppression threshold levels may be used.
+
+#### **8.2.2.2 Fixed suppression threshold**
+
+With a fixed suppression threshold level, the appropriate level to use will depend upon the cancellation achieved and the statistics of speech levels and line conditions found in the particular network in which the echo canceller is to be used. Values of fixed suppression threshold levels to be used are under study – see Notes 1 and 2.
+
+NOTE 1 – As an interim guide, it is suggested that the suppression threshold level should be set a few decibels above the level that would result in the *peaks* of $L_{\text{RES}}$ for a "2s-talker" and a "2s-ERL" being suppressed.
+
+NOTE 2 – Results of a field trial reported by one Administration indicated that a fixed suppression threshold level of $-36 \text{ dBm}0$ gave a satisfactory performance. A theoretical study, by another Administration, of an echo path containing five pairs of PCM codecs showed that for an $L_{\text{Rin}}$ of $-10 \text{ dBm}0$ , the quantization noise could result in an $L_{\text{RES}}$ of $-38 \text{ dBm}0$ .
+
+#### 8.2.2.3 Adaptive suppression threshold
+
+A good compromise can be made between using a high $T_{\text{SUP}}$ to prevent it being exceeded by loud talker residual echo and using a low $T_{\text{SUP}}$ to reduce speech distortion on break-in by making $T_{\text{SUP}}$ adaptive to the actual circuit conditions and speech levels. This may be achieved in a number of ways and no recommendation is made for any particular implementation. General guidelines applicable to the control algorithm and suppression threshold levels are under study.
+
+### 8.2.3 Control of NLP activation
+
+#### 8.2.3.1 General
+
+To conform to the recommendation made in clause 8.2.1.3, it is necessary to control the activation of the NLP so that it is not active when cancelled end speech is likely to be present. When "active", the NLP should function as intended to reduce $L_{\text{RES}}$ . When "inactive", it should not perform any non-linear processing on any signal passing through the echo canceller.
+
+#### 8.2.3.2 Control guidelines
+
+It is recommended that the following two guidelines should govern control of the activation of an NLP. First, because they are intended to further reduce $L_{\text{RES}}$ , they should be active when $L_{\text{RES}}$ is at a significant level. Second, because they should not distort cancelled end speech, they should be inactive when cancelled end speech is present. Where these two guidelines conflict, the control function should favour the second.
+
+#### 8.2.3.3 Static characteristics
+
+A conceptual diagram showing the two operational states of an NLP is shown in Figure 40. The $L_{\text{Sin}} L_{\text{Rin}}$ plane is divided into two regions, W and Z by the threshold WZ ( $T_{\text{WZ}}$ ). In the W region the NLP is inactive while in the Z region it is active. Proper control of the NLP to ensure operation in the appropriate region requires recognition of the double talk condition or the presence of cancelled end speech. Imperfect detection of double talk combined with a high suppression threshold level will result in distortion of cancelled end speech. The echo canceller then exhibits some of the characteristics of an echo suppressor. A low suppression level will permit easy double talking, even if a detection error is made because the cancelled end speech will suffer only a low level of non-linear distortion. If the suppression threshold level is too low, then peaks of residual echo may be heard.
+
+
+
+The figure is a graph with the y-axis labeled 'Level of signal at send-in port $L_{\text{Sin}}$ (dBm0)' and the x-axis labeled 'Level of signal at receive-in port $L_{\text{Rin}}$ (dBm0)'. A diagonal line runs from the bottom-left to the top-right. The area above and to the left of the line is labeled 'NLP inactive' and contains the letter 'W'. The area below and to the right of the line is labeled 'NLP active' and contains the letter 'Z'. Four numbered circles with arrows indicate transitions across the diagonal line:
+
+
+- Arrow 1 is in the 'Z' region, pointing right, indicating a transition from Z to W as $L_{\text{Rin}}$ increases.
+- Arrow 2 is in the 'W' region, pointing left, indicating a transition from W to Z as $L_{\text{Rin}}$ decreases.
+- Arrow 3 is in the 'Z' region, pointing up, indicating a transition from Z to W as $L_{\text{Sin}}$ increases.
+- Arrow 4 is in the 'W' region, pointing down, indicating a transition from W to Z as $L_{\text{Sin}}$ decreases.
+
+ The diagram is labeled 'G.168(15)\_F40' in the bottom right corner.
+
+Figure 40: NLP operating regions. A graph showing the relationship between the level of signal at the send-in port (L\_Sin in dBm0) on the y-axis and the level of signal at the receive-in port (L\_Rin in dBm0) on the x-axis. A diagonal line separates the 'NLP inactive' region (top-left) from the 'NLP active' region (bottom-right). Four numbered arrows indicate transitions: 1 (W to Z), 2 (Z to W), 3 (Z to W), and 4 (W to Z). The diagram is labeled G.168(15)\_F40.
+
+**Figure 40 – NLP operating regions**
+
+#### 8.2.3.4 Dynamic characteristics
+
+The dynamic characteristics can be specified by stating the time that elapses when the signal conditions pass from a point in one area to a point in the other area before the state appropriate to the second area is established. Four such transitions are shown by arrows in Figure 40.
+
+##### Transition No. 1 – W to Z, $L_{\text{Sin}}$ constant, $L_{\text{Rin}}$ increasing
+
+In this case, the $L_{\text{Sin}}$ signal occurred first and the $L_{\text{Rin}}$ is increasing to a sufficiently high level to override the $L_{\text{Sin}}$ signal in the control path and cause the NLP to change from the inactive to the active state. Since this will cause distortion of the $L_{\text{Sin}}$ signal (cancelled end talker speech in this case), the action should not be initiated too quickly.
+
+##### Transition No. 2 – Z to W, $L_{\text{Sin}}$ constant, $L_{\text{Rin}}$ decreasing
+
+In this case, the $L_{\text{Rin}}$ signal has overridden the $L_{\text{Sin}}$ signal in the control path and the NLP is in the active state. The $L_{\text{Rin}}$ signal is now decreasing. The NLP should remain in the active state sufficiently long to prevent echo, which is stored in the echo path, from being heard by the far talker.
+
+##### Transition No. 3 – Z to W, $L_{\text{Rin}}$ constant, $L_{\text{Sin}}$ increasing
+
+This transition is replicating the onset of double talk. As soon as possible after the $L_{\text{Sin}}$ signal is detected, the NLP should be switched to the inactive state in order to minimize any distortion of the cancelled end talker speech.
+
+##### Transition No. 4 – W to Z, $L_{\text{Rin}}$ constant, $L_{\text{Sin}}$ decreasing
+
+In this case, $L_{\text{Sin}}$ has been recognized but is decreasing. Any action which is taken should favour continuing to permit the $L_{\text{Sin}}$ signal to pass. This implies there should be some delay in switching the NLP back to the active state.
+
+### 8.2.4 Frequency limits of control paths
+
+Under study.
+
+NOTE – Depending on the particular implementation of the NLP, the considerations and frequency response limits given in clause 3.2.4.2 of [ITU-T G.164] for the suppression and break-in control paths of echo suppressors may also be applicable to similar control paths used in NLPs. These control paths may include the activation control and adaptive suppression threshold level control.
+
+### 8.2.5 Signal attenuation below threshold level
+
+The attenuation of signals having a level below that of the suppression threshold level of an NLP in the active state should be such that the requirements of clause 6.4.2.3.1 are met.
+
+### **8.2.6 Testing of NLPs**
+
+The NLP may be considered as a special case of an echo suppressor which is limited to suppressing only low-level signals. The types of test required to determine the NLP performance characteristics are very similar to the echo suppressor tests given in [ITU-T G.164]. However, depending on the specific implementation of an NLP, the transitions between areas W and Z of Figure 40 may not be as sharply defined as is the case for echo suppressors. Signals observed at the send-out port of the echo canceller may be distorted for short periods when transitions between the W and Z operating regions occur. Although [ITU-T G.164] may be used as a guide to the testing of NLPs, it may be necessary to introduce unique test circuit modifications in order to make measurements on some specific NLP implementations. In particular, it is known that some echo cancellers employ a supplementary NLP technique independent of the NLP enable/disable control. Those tests of this Recommendation which call for NLP disabled do not strictly apply to such cancellers unless some further interpretation of results is made. The following clause suggests a technique for identifying the presence of such supplementary NLP functions.
+
+#### **8.2.6.1 Testing for the presence of an NLP**
+
+Set up Test 2B of this Recommendation (Convergence without NLP). However, modify the test by mixing uncorrelated noise at various known levels below the returned CSS echo in the Send path. The noise level establishes a floor below which noise plus residual echo due to cancellation should not fall. Observing residual echo levels below the noise floor, then, is an indication of NLP action.
+
+# Annex A
+
+## **Description of an echo canceller reference tone disabler**
+
+*Former Annex A of 2000 edition has been deleted.
+Any information or requirements have been transferred
+to clause 7 of this Recommendation*
+
+# Annex B
+
+## Description of a reference non-linear processor
+
+(This annex forms an integral part of this Recommendation.)
+
+## B.1 General
+
+This annex, which is for the purposes of illustration only and not intended as a detailed design (see clause 8.1), describes a reference non-linear processor (NLP) based upon concepts that are as simple as possible but having included in it a sufficient number of features to give guidance for a wide range of possible implementations. To this end, two variants of the reference NLP are included. Both are based on a centre clipper having either of the idealized transfer functions illustrated in Figure B.1. The suppression threshold level (determined, in this case by the clipping level) in the first variant is adaptive, adaptation being by reference to $L_{\text{Rin}}$ . Activation control is by reference to the difference between $L_{\text{Rin}}$ and $L_{\text{Sin}}$ . In the second variant, the suppression threshold is fixed. It is assumed that the reference NLP is used in an echo canceller which can achieve a cancellation of the linear components of any returned echo of at least $N$ dB. The value of $N$ is under study.
+
+
+
+Figure B.1 shows two idealized centre clipper transfer functions, labeled a) and b). Both plots show Output (O/P) versus Input (I/P). Plot a) shows a clipping level that is adaptive, indicated by a double-headed arrow labeled 'Clipping level'. Plot b) shows a fixed clipping level, also indicated by a double-headed arrow labeled 'Clipping level'. The text 'G.168(09)\_FB.1' is visible in the bottom right corner of the figure area.
+
+Figure B.1 – Two examples of idealized centre clipper transfer function
+
+## B.2 Suppression threshold ( $T_{\text{SUP}}$ )
+
+Adaptive $T_{\text{SUP}} = (L_{\text{Rin}} - x \pm 3)$ dBm0 for $-30 \leq L_{\text{Rin}} \leq -10$ dBm0
+
+Fixed $T_{\text{SUP}} = x'$ dBm0
+
+NOTE – Values of $x$ and $x'$ are under study. Values of 18 for $x$ and $-36$ for $x'$ have been suggested but confirmation is required that these values are appropriate for use in all networks.
+
+## B.3 Static characteristics of activation control
+
+$T_{\text{WZ}} = (L_{\text{Rin}} - y \pm 3)$ dBm0 for $-30 \leq L_{\text{Rin}} \leq -10$ dBm0
+
+NOTE 1 – $T_{\text{WZ}}$ is as defined in clause 8.2.3.3.
+
+NOTE 2 – The value of $y$ may be different for each variant, and this is under study. Values of $x$ dB in the case of the adaptive $T_{\text{SUP}}$ and $\geq 6$ dB for $y$ in the case of the fixed $T_{\text{SUP}}$ seem reasonable.
+
+## **B.4 Dynamic characteristics of activation control**
+
+Dynamic characteristics of the activation control are given in Tables B.1 and B.2. Also see Figure 40.
+
+**Table B.1 – NLP hangover times**
+
+| Boundary | | Initial signal | | Final signal | | Recommended value (ms) | Test No. [ITU-T G.164] | Excursion (see Figure 40) | Test circuit, Figure: | Oscilloscope trace |
+|----------|----------|------------------------------|---------------------------------|------------------------------|---------------------------------|------------------------|------------------------|---------------------------|-----------------------|---------------------------------------|
+| | | Send L Sin (dBm0) | Receive L Rin (dBm0) | Send L Sin (dBm0) | Receive L Rin (dBm0) | | | | | |
+| | Fixed | -25 | -10 | -25 | -30 | 15-64 | | | | |
+| Z/W | Adaptive | -55 -40 -30 | -20 -15 -5 | -55 -40 -30 | -40 -40 -30 | Δ | 5 | Transition 2 | 14/ITU-T G.164 | Trace 1 and trace 2 of Figure B.3 (β) |
+| | Fixed | -15 | -25 | -40 | -25 | 16-120 | | | | |
+| | Adaptive | -40 -40 -25 | -50 -30 -15 | -55 -55 -40 | -50 -30 -15 | 30-50 | 6 | Transition 4 | 17/ITU-T G.164 | Trace 1 and trace 2 of Figure B.2 (β) |
+
+**Table B.2 – NLP operate times**
+
+| Boundary | | Initial signal | | Final signal | | Recommended value (ms) | Test No. [ITU-T G.164] | Excursion (see Figure 40) | Test circuit, Figure: | Oscilloscope trace |
+|----------|----------|------------------------------|---------------------------------|------------------------------|---------------------------------|------------------------|------------------------|---------------------------|-----------------------|---------------------------|
+| | | Send L Sin (dBm0) | Receive L Rin (dBm0) | Send L Sin (dBm0) | Receive L Rin (dBm0) | | | | | |
+| | Fixed | -25 | -30 | -25 | -10 | 16-120 | | | | |
+| W/Z | Adaptive | -55 -40 -30 | -40 -40 -30 | -55 -40 -30 | -20 -15 -5 | 15-75 | 4 | Transition 1 | 14/ITU-T G.164 | Trace 2 of Figure B.3 (α) |
+| | Fixed | -40 | -25 | -15 | -25 | ≤ 1 | | | | |
+| | Adaptive | -55 -55 -40 | -50 -30 -15 | -40 -40 -25 | -50 -30 -15 | ≤ 5 | 6 | Transition 3 | 17/ITU-T G.164 | Trace 2 of Figure B.2 (α) |
+
+## B.5 Frequency limits of control paths
+
+See clause 8.2.4.
+
+## B.6 Testing
+
+Tables B.1 and B.2 indicate, by reference to [ITU-T G.164], how the dynamic performance of NLP activation control may be checked using sine wave signals. Figures B.2 and B.3 show the traces obtained on an oscilloscope for these tests.
+
+
+
+Figure B.2: Oscilloscope traces for NLP operate and hangover time with L\_Rin constant. Trace 1 (S\_in) shows a rectangular pulse. Trace 2 (S\_out) shows the output signal, which follows S\_in with some distortion. The time interval between the rising edge of S\_in and the start of the distorted region of S\_out is labeled alpha (operate time). The time interval between the falling edge of S\_in and the end of the distorted region of S\_out is labeled beta (hangover time). The total duration of the distorted region of S\_out is labeled tau. A shaded area on Trace 2 indicates the distorted signal. The label G.168(09)\_FB.2 is in the bottom right corner.
+
+**Figure B.2 – Traces for NLP operate and hangover time, $L_{Rin}$ constant**
+
+
+
+Figure B.3: Oscilloscope traces for NLP operate and hangover times with L\_Sin constant. Trace 1 (R\_in) shows a rectangular pulse. Trace 2 (S\_out) shows the output signal. The time interval between the rising edge of R\_in and the start of the distorted region of S\_out is labeled alpha (operate time). The time interval between the falling edge of R\_in and the end of the distorted region of S\_out is labeled beta (hangover time). The total duration of the distorted region of S\_out is labeled tau. The label G.168(09)\_FB.3 is in the bottom right corner.
+
+**Figure B.3 – Traces for NLP operate and hangover times, $L_{Sin}$ constant**
+
+$\alpha$ Operate time
+
+$\beta$ Hangover time
+
+$\tau$ Time interval in which the distorted signal may be observed
+
+# Annex C
+
+## Composite source signals for testing of speech echo cancellers – Signal, description and analysis
+
+(This annex forms an integral part of this Recommendation.)
+
+## C.1 Introduction
+
+This annex describes the subset of composite source signals that are used for testing speech echo cancellers in the network under single and double talk conditions. The exact definition of these signals is part of [ITU-T P.501] on test signals for use in telephonometry (see [b-ITU-T GSTP.CSS] in clause I.8 for more details). First, a general description of composite source signals is given. The following clauses give the exact definition of both signals for testing speech echo cancellers under single and double talk conditions. Moreover, kinds of analysis are considered and described to test the specific parameters of echo cancellers especially for the tests of this Recommendation.
+
+## C.2 Composite source signal – General considerations
+
+### C.2.1 General description of the different sequences
+
+Composite source signals, in general, consists of different sequences including voiced and unvoiced sounds as well as pauses.
+
+*Voiced signal produced from the "artificial voice" signal according to [ITU-T P.50]*
+
+The voiced signal part of CSS is the conditioning signal intended to activate possible speech detectors in voice-controlled systems and to reproduce voiced sounds of real speech in general. As the duration, beginning and end of the voiced signal are known exactly, this signal can also be used to measure the switching time for the direction of transmission under test. By means of the signal shape in the time domain, the switching time and delay time of the entire system can be determined. The duration of the signal amounts to 50 ms approximately.
+
+*Pseudo noise signal*
+
+The signal presented after the voiced artificial speech sound is the Pseudo Noise (PN) signal. This signal has certain noise-like features. The magnitude of its Fourier transform is initially constant with frequency while the phase is changing. For tests usually only the magnitude of the transfer function is of interest, the phase is not that important but can be determined as well.
+
+The signal is produced as follows:
+
+First a complex spectrum is produced in the frequency domain according to the following equation:
+
+$$H(k) = W(k)e^{j \cdot i_k \cdot \pi}; k = -\frac{M}{2}, \dots, \frac{M}{2} \text{ without } 0; i_k \in \{+1, 0\}, i_k = -i_{-k} \text{ random} \quad (C.2-1)$$
+
+The index $M$ is adjusted to the chosen FFT size (e.g., 2048, 4096 or 8192 points). The equation shows that the amount of the produced complex spectrum is constant for all frequencies if $W(k)$ is chosen equal to 1 for all frequencies, whereas the phase may be $\pi$ or 0 for each frequency, corresponding to a random sequence. However, to produce a different weighting in the frequency domain, $W(k)$ can easily be adjusted in order to produce different spectra for the duration of the PN-sequence. Then, this spectrum will be transformed into the time domain by means of the inverse Fourier transform producing the following signal:
+
+$$S(n) = \frac{1}{M} \sum_{k=-M/2, k \neq 0}^{M/2} H(k) \cdot e^{j2\pi \cdot n \cdot k/M}, \quad n = -\frac{M}{2}, \dots, \frac{M}{2} - 1 \quad (C.2-2)$$
+
+NOTE 1 – Thus, a signal is produced which is limited in time (corresponding to the chosen length of the Fourier transform) and which is adjusted to the chosen FFT size correctly. If a longer time sequence is wanted, the signal can be cycled. This method permits time sequences of any length. The duration of this measurement signal amounts to about 200 ms by appropriate choice of $M$ , the sampling rate and numbers of repetitions.
+
+The pseudo noise sequence of the composite source signal for measurements of speech echo cancellers is calculated in that way that $W(k)$ is chosen constant and the corresponding signal $S(n)$ (calculated by inverse Fourier transform) is filtered with a transfer function which is given below in clause C.3.1.
+
+NOTE 2 – Typically, the length of the FFT should be short for systems with highly time variant parameters such as companding techniques in order to get a good short time estimation of the time variant transfer function. For systems incorporating adaptive techniques such as echo cancellers or noise cancellers a higher number of $M$ (close to 200 ms signal duration) may be appropriate in order to have the autocorrelation function of the measurement signal not periodically within the processing window of the device under test.
+
+#### *Pause*
+
+The third part of the composite source signal is a pause. Regarding the composite source signal as a measurement signal that reproduces important characteristics of real running speech, the pause has the purpose to provide suitable amplitude modulation to the composite signal. Moreover it reproduces real speech pauses that occur in running speech signals as well. This also means a certain period without excitation signal, which gives the possibility to analyse noise or artefacts produced by the system under test. The length of the pause is chosen between 100 ms and 150 ms.
+
+In order to achieve a long term offset free sequence, the repeated CS-sequence should be inverted in amplitude (phase shift by $180^\circ$ ).
+
+### **C.2.2 Calculation and analysis using a composite source signal**
+
+When using CSS for measurements, the sequence of voiced sound, pseudo noise signal and pause can be cycled. This means that after the pause the sequence starts again beginning with a voiced sound. Using this procedure sequences of any length may be produced.
+
+Having created a sequence as described above, this signal can be handled like a standard measurement signal, e.g., a white noise signal or a switched pink noise. The level calibration (acoustical and electrical) is done using the whole sequence including voiced sounds, PN-sequences and pauses. In principle a standard RMS meter with a bandwidth of 20 kHz operating with "fast" averaging can be used. Another method is to use a FFT analysis for level calculations. The parameters for the FFT based calculation are:
+
+- sampling rate according to the one chosen for signal generation (preferred 44.1 kHz or 48 kHz);
+- FFT length according to the one chosen for signal generation;
+- rectangular windowing;
+- no overlap;
+- averaging over the whole (cycled) sequence, including voiced sounds, PN-sequences, pauses;
+- calculation of the level from the power density spectrum derived by the FFT calculation (integration of the levels over all frequency components).
+
+## C.3 Bandlimited composite source signal with speech like power density spectrum – Practical realization for measurements of echo cancellers
+
+Both composite source signals described below in this annex have a speech-like power density spectrum. This means that the noise sequences of both signals (the measurement signal and the signal to simulate double talk) are shaped with a decrease of 5 dB/octave towards higher frequency. The convergence characteristics of speech echo cancellers largely depend on the power density spectrum of the input signal. Therefore, these composite source signals were adapted in this way to reproduce the power density spectrum of real speech.
+
+### C.3.1 Composite source signal for single talk
+
+Figure C.1 shows the principle construction of the composite source signal for single talk.
+
+
+
+Duration: $T_{VST}$ (voiced sound): 48.62 ms $T_{ST1}$ (one period): 350.00 ms
+ $T_{PN}$ (pseudo noise): 200.00 ms $T_{ST}$ (whole period): 700.00 ms
+ $T_{PST}$ (pause): 101.38 ms
+
+G.168(09)\_FC.1
+
+Schematic diagram of the composite source signal for measuring echo cancellers. The diagram shows two parts, 'Part no. 1' and 'Part no. 2', each consisting of three segments: voiced sound (T\_VST), pseudo noise (T\_PN), and pause (T\_PST). The total duration of one part is T\_ST1 (350.00 ms), and the total duration of both parts is T\_ST (700.00 ms).
+
+**Figure C.1 – Composite source signal for measuring echo cancellers (schematic)**
+
+#### *Bandlimited voiced signal*
+
+In Table C.1 the 16-bit word values for the voiced signal, bandlimited between 200 Hz and 3.6 kHz can be found. According to a sampling rate of 44.1 kHz, the 134 16-bit word values amount to 3.04 ms. The values are to be read in columns:
+
+**Table C.1 – 16-bit word values of the bandlimited voiced signal**
+
+| | | | | | | | | | | |
+|------|------|------|------|------|------|------|-------|-------|-------|-------|
+| -155 | 948 | 3224 | 4000 | 3129 | 1440 | 241 | -888 | -1853 | -6137 | -3474 |
+| 276 | 1362 | 3370 | 4043 | 3043 | 1310 | 190 | -957 | -2121 | -6560 | -2508 |
+| 517 | 1741 | 3500 | 4034 | 2914 | 1146 | 103 | -1034 | -2414 | -6948 | -1595 |
+| 578 | 2043 | 3569 | 3974 | 2750 | 965 | -9 | -1103 | -2707 | -7301 | -802 |
+| 491 | 2276 | 3603 | 3862 | 2560 | 776 | -138 | -1146 | -3017 | -7568 | |
+| 302 | 2422 | 3603 | 3724 | 2353 | 603 | -267 | -1181 | -3319 | -7732 | |
+| 86 | 2500 | 3595 | 3577 | 2155 | 448 | -388 | -1190 | -3612 | -7758 | |
+| -103 | 2552 | 3586 | 3439 | 1991 | 345 | -491 | -1198 | -3913 | -7620 | |
+| -207 | 2595 | 3595 | 3336 | 1853 | 276 | -569 | -1215 | -4224 | -7310 | |
+| -198 | 2655 | 3638 | 3267 | 1750 | 250 | -638 | -1259 | -4560 | -6810 | |
+| -60 | 2758 | 3724 | 3224 | 1672 | 250 | -698 | -1327 | -4922 | -6155 | |
+| 190 | 2896 | 3819 | 3198 | 1603 | 267 | -759 | -1457 | -5301 | -5344 | |
+| 543 | 3060 | 3922 | 3172 | 1534 | 267 | -813 | -1629 | -5715 | -4439 | |
+
+The values of the voiced signal in the frequency range 200 Hz-3.6 kHz again are calculated such that the RMS value of the voiced signal and the PN-sequence are equal. The sequence is repeated 16 times to achieve a length of 48.62 ms.
+
+#### *Pseudo noise signal generated using 2048 pt. FFT*
+
+The parameters for the PN-sequence are:
+
+Sampling rate 44.1 kHz, 16-bit word length, length of Fourier transform 2048 points.
+
+$$H(k) = \begin{cases} W(k) \cdot e^{j i_k \pi}; k = -928, \dots, +928 \text{ except } 0, i_k \in \{+1, 0\}, \text{random}, i_k = -i_{-k} \\ 0 \text{ else} \end{cases} \quad (C.3-1)$$
+
+According to the above-described Formula C.2-2, the time signal is calculated by inverse Fourier-Transformation. This sequence is repeated 4.307 times to achieve a length of 200 ms for the PN sequence. The crest factor of the PN-sequence is $11 \text{ dB} \pm 1 \text{ dB}$ .
+
+According to the frequency resolution of 21.5 Hz (44.1 kHz/2048), there are 928 FFT values in the frequency range between 0 and 20 kHz. Each value $W(k)$ (before filtering) is 152 680. It is calculated such that levels within a bandwidth of 20 kHz are the same for the voiced signal and the PN sequence.
+
+#### *Pseudo noise signal generated using 8192 pt. FFT*
+
+According to the above-described Formula C.2-2, the time signal is calculated by inverse Fourier-Transformation. This sequence is repeated 1.077 times to achieve a length of 200 ms for the PN-sequence. The crest factor of the PN sequence is $11 \text{ dB} \pm 1 \text{ dB}$ .
+
+According to the frequency resolution of 5.4 Hz (44.1 kHz/8192), there are 3715 FFT values in the frequency range between 0 and 20 kHz. Each value $W(k)$ before filtering is 305 360. It is calculated such that levels within a bandwidth of 20 kHz are the same for the voiced signal and the PN-sequence.
+
+In order to achieve the same RMS value for the bandlimited PN-sequence the filter function shown in Figure C.2 should be applied. The filter is chosen such, that the levels of the filtered and the unfiltered PN-sequence are equal. The filter corner frequencies are shown in Table C.2.
+
+NOTE – By appropriate up- or down-sampling other sampling rates for the described sequence can be achieved. The interpolation filter used for up- and down-sampling should be close to an ideal rectangular filter. The stopband attenuation should be $> 60 \text{ dB}$ , the passband ripple $< \pm 0.2 \text{ dB}$ .
+
+
+
+Figure C.2: Transfer function of the filter for bandlimiting the PN-sequence. The graph plots gain L/dB on the y-axis (from -30 to 10) against frequency f/Hz on a logarithmic x-axis (from 50 to 2000). The curve starts at -25.8 dB at 50 Hz, rises to a peak of 17.8 dB at 215 Hz, and then gradually declines, crossing 0 dB at 2.85 kHz and reaching -30 dB at 3.68 kHz. The label 'G.168(09)\_FC.2' is in the bottom right corner.
+
+**Figure C.2 – Transfer function of the filter for bandlimiting the PN-sequence**
+
+**Table C.2 – Table of filter corner frequencies**
+
+| | | | | | | | | | |
+|----------|----------|---------|---------|---------|--------|----------|---------|----------|----------|
+| 50 Hz | 100 Hz | 200 Hz | 215 Hz | 500 Hz | 1 kHz | 2.85 kHz | 3.6 kHz | 3.66 kHz | 3.68 kHz |
+| -25.8 dB | -12.8 dB | 17.4 dB | 17.8 dB | 12.2 dB | 7.2 dB | 0 dB | -2 dB | -20 dB | -30 dB |
+
+For adaptive systems such as echo cancellers, a longer PN sequence may be preferable in order not to have correlated measurement signals within the adaptation window. For those systems the FFT length should be extended to 8192 points when using 44.1 kHz sampling rate as described above.
+
+#### *Pause*
+
+The length of the pause is chosen to 101.38 ms in order to achieve a complete length of 350 ms for the voiced sound, the pseudo noise sequence and the pause.
+
+To achieve a long term offset free sequence, this CS-sequence of 350 ms is repeated and inverted in amplitude (phase shift by 180°). The complete length amounts to 700 ms.
+
+### **C.3.2 Bandlimited composite source signal to simulate double talk**
+
+The double talk sequence is generated in the same way as the single talk signal. Figure C.7 shows the principle construction of the double talk signal. However, the times of the voiced signal and the pause are slightly different in order to achieve a typical double talk condition with two signals applied the same time, signal present only in one channel, voiced signals present on both sides as well as voiced signals and unvoiced signals present the same time in the different channels. The correlation between single talk signal and double talk signal is low. This is achieved by choosing a different voiced signal with a different pitch frequency and a random noise signal instead of the PN sequence. The duration of the voiced signal is 72.69 ms, the duration of the random noise signal is 200 ms and the duration of the pause amounts to 127.31 ms.
+
+#### *Voiced signal*
+
+The voiced signal for double talk was chosen to have a different base frequency than the signal talk voiced signal. The values for the voiced signal for double talk can be found in Table C.3. The level
+
+of this sound again is the same as the one for single talk. Using a sampling rate of 44.1 kHz 229 16-bit word values represent 5.19 ms. The table is to be read in columns:
+
+**Table C.3 – 16-bit word values for the bandlimited double talk voiced signal**
+
+| | | | | | | | | | | |
+|------|-------|-------|------|------|-------|-------|------|-------|-------|------|
+| -198 | 1146 | -8292 | 4827 | 5853 | 1422 | -1293 | -810 | -690 | -1052 | -621 |
+| -112 | 871 | -8715 | 5094 | 5715 | 1224 | -1302 | -793 | -724 | -1043 | -560 |
+| -9 | 560 | -9077 | 5344 | 5560 | 1026 | -1293 | -767 | -767 | -1043 | -509 |
+| 103 | 233 | -9370 | 5594 | 5387 | 819 | -1267 | -741 | -793 | -1052 | -457 |
+| 233 | -121 | -9542 | 5827 | 5215 | 603 | -1250 | -698 | -819 | -1060 | -397 |
+| 388 | -491 | -9542 | 6043 | 5043 | 388 | -1233 | -672 | -845 | -1060 | -345 |
+| 543 | -871 | -9361 | 6215 | 4879 | 181 | -1224 | -638 | -853 | -1060 | -276 |
+| 724 | -1250 | -8956 | 6344 | 4732 | 9 | -1224 | -603 | -871 | -1052 | -207 |
+| 896 | -1638 | -8327 | 6413 | 4586 | -181 | -1224 | -595 | -879 | -1034 | -112 |
+| 1060 | -2043 | -7465 | 6422 | 4439 | -328 | -1224 | -586 | -888 | -1017 | |
+| 1233 | -2465 | -6396 | 6379 | 4276 | -448 | -1215 | -595 | -896 | -991 | |
+| 1388 | -2896 | -5163 | 6310 | 4086 | -543 | -1198 | -603 | -922 | -957 | |
+| 1517 | -3345 | -3827 | 6215 | 3870 | -629 | -1172 | -621 | -948 | -931 | |
+| 1638 | -3819 | -2448 | 6120 | 3629 | -707 | -1129 | -629 | -974 | -905 | |
+| 1747 | -4310 | -1103 | 6051 | 3370 | -784 | -1077 | -938 | -1009 | -888 | |
+| 1810 | -4810 | 155 | 6000 | 3086 | -871 | -1026 | -638 | -1026 | -862 | |
+| 1845 | -5319 | 1293 | 5991 | 2801 | -948 | -974 | -638 | -1052 | -845 | |
+| 1845 | -5836 | 2241 | 5991 | 2534 | -1026 | -922 | -638 | -1069 | -819 | |
+| 1802 | -6353 | 3034 | 6000 | 2267 | -1112 | -888 | -638 | -1077 | -793 | |
+| 1707 | -6853 | 3655 | 6008 | 2034 | -1181 | -871 | -638 | -1069 | -767 | |
+| 1569 | -7353 | 4138 | 5991 | 1819 | -1241 | -845 | -647 | -1060 | -724 | |
+| 1379 | -7836 | 4517 | 5939 | 1612 | -1276 | -828 | -664 | -1060 | -672 | |
+
+In order to achieve the required length of 72.69 ms, the values are to be repeated 14 times.
+
+#### *Random noise*
+
+The random noise is chosen as a White Gaussian Noise bandlimited at 20 kHz. The crest factor of the signal is $12 \pm 1$ dB. The RMS value of the bandlimited random noise is chosen to be the same as the one for the voiced signal.
+
+In order to bandlimit the random noise between 200 Hz and 3.6 kHz, the filter function shown in Figure C.2 is used. This ensures the same RMS value for the bandlimited random noise.
+
+#### *Pause*
+
+The pause is chosen to 127.31 ms in order to achieve a length of 400 ms for the voiced sound, the random noise sequence and the pause.
+
+Again, in order to achieve a long-term signal which is free of offset, this sequence of 400 ms is repeated and inverted in amplitude (phase shift by $180^\circ$ ). Thus the resulting length of the double talk signal is 800 ms.
+
+
+
+This graph displays the power density spectrum of a bandlimited CSS signal. The y-axis, labeled 'L/dB', ranges from -70 to -20 in increments of 10. The x-axis, labeled 'f/Hz', is logarithmic with major ticks at 100, 200, 500, 1000, 2000, and 5000. The spectrum shows a noisy signal that starts at approximately -45 dB at 100 Hz, rises to a peak of about -20 dB at 300 Hz, and then gradually declines with some fluctuations to about -40 dB at 4000 Hz. Beyond 4000 Hz, there is a very sharp drop-off, with the signal level falling to below -70 dB by 5000 Hz. The label 'G.168(09)\_FC.3' is visible in the bottom right corner.
+
+Figure C.3: Power density spectrum of the bandlimited CSS (single talk signal, analysis window: Hanning). The graph shows a noisy spectrum with a peak around 300 Hz and a sharp drop-off after 4000 Hz. The y-axis is L/dB from -70 to -20, and the x-axis is f/Hz from 100 to 5000.
+
+**Figure C.3 – Power density spectrum of the bandlimited CSS
+(single talk signal, analysis window: Hanning)**
+
+
+
+This graph displays the power density spectrum of a bandlimited voiced signal. The y-axis, labeled 'L/dB', ranges from -60 to -10 in increments of 10. The x-axis, labeled 'f/Hz', is logarithmic with major ticks at 100, 200, 500, 1000, 2000, and 5000. The spectrum consists of a series of sharp, narrow peaks (harmonics) that decrease in amplitude as frequency increases. The first prominent peak is at approximately 300 Hz with a level of about -15 dB. Subsequent peaks are visible at roughly 600 Hz, 1000 Hz, 1500 Hz, 2000 Hz, 2500 Hz, 3000 Hz, 3500 Hz, and 4000 Hz, with their amplitudes progressively decreasing. The label 'G.168(09)\_FC.4' is visible in the bottom right corner.
+
+Figure C.4: Power density spectrum of the bandlimited voiced signal (single talk signal, analysis window: Hanning). The graph shows a series of sharp peaks (harmonics) that decrease in amplitude as frequency increases. The y-axis is L/dB from -60 to -10, and the x-axis is f/Hz from 100 to 5000.
+
+**Figure C.4 – Power density spectrum of the bandlimited voiced signal
+(single talk signal, analysis window: Hanning)**
+
+
+
+Figure C.5: Power density spectrum of the bandlimited double-talk CSS. The graph shows a noisy spectrum with a general downward trend, starting around -50 dB at 100 Hz and dropping to -70 dB at 4000 Hz. The x-axis is logarithmic from 100 to 5000 Hz, and the y-axis is linear from -70 to -20 dB. A label 'G.168(09)\_FC.5' is in the bottom right corner.
+
+**Figure C.5 – Power density spectrum of the bandlimited double-talk CSS
+(analysis window: Hanning)**
+
+
+
+Figure C.6: Power density spectrum of the bandlimited double talk-voiced signal. The graph shows a series of sharp peaks (harmonics) that decrease in amplitude as frequency increases. The peaks are located at approximately 200, 400, 600, 800, 1000, 1200, 1400, 1600, 1800, 2000, 2200, 2400, 2600, 2800, 3000, 3200, 3400, 3600, 3800, and 4000 Hz. The x-axis is logarithmic from 100 to 5000 Hz, and the y-axis is linear from -60 to -10 dB. A label 'G.168(09)\_FC.6' is in the bottom right corner.
+
+**Figure C.6 – Power density spectrum of the bandlimited double talk-voiced signal
+(analysis window: Hanning)**
+
+NOTE – By appropriate up- or down-sampling, other sampling rates for the described sequence can be achieved. The interpolation filter used for up- and down-sampling should be close to an ideal rectangular filter. The stopband attenuation should be $> 60$ dB, the passband ripple $< \pm 0.2$ dB.
+
+
+
+Duration:
+
+| | | | |
+|---------------------------|-----------|--------------------------|-----------|
+| $T_{VDT}$ (voiced sound): | 72.69 ms | $T_{DTI}$ (one period): | 400.00 ms |
+| $T_{RN}$ (random): | 200.00 ms | $T_{DT}$ (whole period): | 800.00 ms |
+| $T_{PDT}$ (pause): | 127.31 ms | | |
+
+G.168(09)\_FC.7
+
+Schematic diagram of composite source signals to simulate double talk. The diagram shows two identical blocks labeled 'Part no. 1' and 'Part no. 2'. Each block is divided into three sections: a small initial section labeled T\_VDT, a larger middle section labeled T\_RN, and a final section labeled T\_PDT. The duration of one block is indicated as T\_DTI, and the total duration of both blocks is T\_DT. Horizontal arrows indicate the time spans for each variable.
+
+**Figure C.7 – Composite source signals to simulate double talk (schematic)**
+
+#### Application
+
+The application of the bandlimited composite source signals for single talk as well as for double talk is for all testing where bandlimited systems need to be tested working non-linear and time variant and requiring the typical long-term power density spectrum of speech. The typical application is the testing of speech echo cancellers in the network. For all one directional tests, the bandlimited CSS for single talk tests should be used. In case of tests in double talk conditions, the double talk signal should be used in double talk direction ( $S_{gen}$ ), whereas the single talk signal is fed in the far-end direction ( $R_{in}$ ).
+
+## C.4 Appropriate analyses to determine convergence characteristics of speech echo cancellers using the composite source signal
+
+The composite source signal for testing speech echo cancellers and the second composite source signal to simulate double talk are described above. If the echo signal level should be measured, there are several possibilities of analysis technique. Calculations can be made in the time or frequency domain.
+
+### C.4.1 Calculation in the frequency domain
+
+The signal level can be determined by calculations in the frequency domain, after the time sequence has been transformed by Fourier Transformation. This allows the level calculations in a certain frequency range, i.e., the telephone bandwidth of 300 Hz to 3.4 kHz. Another advantage is that the Fourier Transformation gives the possibility to analyse further characteristics of the echo signal in the frequency range, for example the echo attenuation versus frequency. For the composite source signal, a rectangle window should be used before calculating the Fourier Transformation. The Pseudo Noise sequence is generated with a 8192 points FFT. The sampling rate should be 44.1 kHz as described above in clauses C.3.1 and C.3.2 for generating the composite source signals. The sequence length used for transformation should be the complete length of 700 ms including the voiced sound, the pseudo noise sequence and the pause. Various measurements showed that due to signal delay or noise produced by the circuit under test, additional artefacts may appear during the pauses (e.g., switched residual echo signal or modulated background noise). Therefore it is suitable to analyse the echo signal over a sequence length of 700 ms, i.e., one whole period of the composite source signal. A disadvantage of level calculations from the frequency range is due to the fact that this gives only a limited time resolution of one Fourier Transformation length. The level calculation in the frequency domain should be used to determine signal levels and residual echo levels after full convergence of after inhibiting adaptation.
+
+### **C.4.2 Calculation in the time domain**
+
+The echo signal level calculation from the time domain is necessary for analysis of echo attenuation versus time because of its high resolution in the time domain. A suitable method is given through [IEC 61672-1], sound level meters. It describes the sound level measurement and recommends three different time constants, "Slow" (1000 ms), "Fast" (125 ms) and "Impulse" (35 ms). If measurement results of different laboratories should be compared, an agreement about the measurement procedure is necessary. A short time constant has advantages because of the highest possible resolution in the time domain, whereas longer time constants have the advantage that the results obtained with this kind of calculation demonstrate more the average level of the time sequence that is analysed. Especially if several measurements calculated, for example, as the level versus time are represented in the same picture, very short time constants may lead to confusing representations. This is due to the fact that using a very short time constant of, for example, 35 ms ("Impulse"), the calculation is more sensitive to even very small signal variations. For this reasons the use of the time constant "Fast" (125 ms) according to [IEC 61672-1] is more suitable for level calculations versus time.
+
+This is a suitable method to analyse the convergence speed of speech echo cancellers at the beginning of adaptation. The echo signal level is calculated using the time constant "Fast" according to [IEC 61672-1]. Level fluctuations due to input signal fluctuations can be eliminated if the echo signal level is referred to the input signal level. This represents the echo return loss enhancement (ERLE) versus time. A disadvantage is that no further analysis is possible in the frequency domain. When using the meters of [IEC 61672-1], any peak detection or decay time constants referenced in [IEC 61672-1] should not be incorporated for measurements in this Recommendation.
+
+### **C.4.3 Level calculations according to [ITU-T P.56] active speech level**
+
+Level calculations can also be done according to [ITU-T P.56]. This calculation is made from the time domain as well. It delivers one value and a percentage of speech activity. It may be suitable to calculate the residual echo level but there are more parameters that have to be defined to guarantee the same implementation of this algorithm. Difficulties may appear if echo signals with a very low level are analysed. It may fall below the recognition level for active speech. Another disadvantage is, although this is a calculation in the time domain it delivers only one value. It is not possible to achieve the level variation versus time, as it is important for convergence measurements. Therefore it is more suitable to analyse residual echo signal level using the Fourier Transformation as described in clause C.4.1 or the level calculation in the time domain for time varying echo signals (e.g., the convergence of echo cancellers) based on [IEC 61672-1] as described in clause C.4.2.
+
+# Annex D
+
+## Echo-path models for testing of speech echo cancellers
+
+(This annex forms an integral part of this Recommendation.)
+
+## D.1 Introduction
+
+The following echo path models can be used for the tests in this Recommendation. The echo path is simulated by a linear digital filter with the impulse response $g(k)$ . To account for various delays, different ERLs and different dispersion characteristics and time widths, $g(k)$ is chosen as a delayed and attenuated version of any of the sequences $m_i(k)$ , $i = 1, 2, \dots, 8$ , that are given in tables in clauses D.2 and D.3.
+
+$$g(k) = (10^{-ERL/20} K_i) m_i(k - \delta) \quad (D-1)$$
+
+The sequences $m_i(k)$ represent echo paths with various dispersion characteristics and different time widths. The delay $\delta$ should be chosen such that the non-zero values of $g(k)$ can be captured by the H register of the echo canceller. The scaling factor $K_i$ depends on the input signals used in the tests. The value of $K_i$ in Table D.1a results in an ERL that is equivalent to the value used in Equation D-1 when measured with CSS. The value of $K_i$ in Table D.1b is used to limit the maximum of the magnitude response to the chosen ERL value. The $K_i$ factors for CSS or white noise input, and for tone input are given below. Specifically for Test 10 Fax test, the $K_i$ factors for tone signal given in Table D.1b should be used. Caution should be used when using Table D.1a for white noise, as the measured ERL may not be equal to the ERL value used in Equation D-1. Only Test 9 uses white noise as the input signal.
+
+### D.1.1 CSS or white noise input
+
+For the tests that use CSS or white noise as the input signals, the values of $K_i$ are given in the Table D.1a for the eight sequences $m_i(k)$ :
+
+**Table D.1a – Scaling factors $K_i$ for the eight digital echo path models**
+
+| Echo path model #(i) | Scaling factor $K_i$ | Minimum ERL for CSS (dB) (Note) |
+|----------------------|-----------------------|---------------------------------|
+| 1 | $1.39 \times 10^{-5}$ | 6 |
+| 2 | $1.44 \times 10^{-5}$ | 6.55 |
+| 3 | $1.52 \times 10^{-5}$ | 6 |
+| 4 | $1.77 \times 10^{-5}$ | 6 |
+| 5 | $9.33 \times 10^{-6}$ | 6 |
+| 6 | $1.51 \times 10^{-5}$ | 6 |
+| 7 | $2.33 \times 10^{-5}$ | 11.06 |
+| 8 | $1.33 \times 10^{-5}$ | 9.27 |
+
+NOTE – A minimum ERL value of 6 dB should be used in the tests for echo path models $m_1$ , $m_3$ , $m_4$ , $m_5$ and $m_6$ . For echo path models $m_2$ , $m_7$ and $m_8$ , the minimum ERL values used in the tests should be, respectively, 6.55 dB, 11.06 dB and 9.27 dB. This is to ensure that the magnitude response of the scaled echo-path $g(k)$ does not exceed 0 dB over the appropriate frequency range.
+
+### D.1.2 Tone(s) input
+
+For the tests that use tone(s) as input signals, the values of $K_i$ should be computed using the formula
+
+$$K_i = \frac{1}{\max_f |M_i(f)|} \quad (D-2)$$
+
+where:
+$$M_i(f) = \sum_{k=0}^{L-1} m_i(k) \exp\left(-\frac{j2\pi f k}{8192}\right) \quad (D-3)$$
+
+with: $i = 1, 2, \dots, 8$
+ $f = 0, 1, \dots, 4095$
+ $L = \text{length of } m_i(k)$
+
+The values of $K_i$ computed from Equations D-2 and D-3 are given in Table D.1b for the eight sequences $m_i(k)$ :
+
+**Table D.1b – Scaling factors $K_i$ for the eight digital echo path models for tones**
+
+| Echo path model #(i) | Scaling factor $K_i$ | Minimum ERL for Tones (dB) (Note) |
+|----------------------|-----------------------|-----------------------------------|
+| 1 | $1.22 \times 10^{-5}$ | 6 |
+| 2 | $6.78 \times 10^{-6}$ | 6 |
+| 3 | $9.66 \times 10^{-6}$ | 6 |
+| 4 | $1.07 \times 10^{-5}$ | 6 |
+| 5 | $7.05 \times 10^{-6}$ | 6 |
+| 6 | $8.60 \times 10^{-6}$ | 6 |
+| 7 | $6.58 \times 10^{-6}$ | 6 |
+| 8 | $4.58 \times 10^{-6}$ | 6 |
+
+NOTE – A minimum ERL value of 6 dB should be used in the tests for all 8 echo path models. Each scaling factor is used to limit the maximum of the magnitude response to the chosen ERL value.
+
+## D.2 Echo path models from network hybrid simulator
+
+This clause contains four echo path models that are generated from a network hybrid simulator. Tables D.2, D.3, D.4 and D.5 show the values for $m_i(k)$ for $i = 1, 2, 3, 4$ . They are to be read in columns. Echo path model $m_1(k)$ has short dispersion, $m_2(k)$ has median-short dispersion, $m_3(k)$ has median-long dispersion and $m_4(k)$ has long dispersion. The corresponding impulse responses and magnitude responses are shown in Figures D.1, D.2, D.3 and D.4. As an example, an ERL of 12 dB is chosen for the plots of magnitude responses.
+
+**Table D.2 – $m_1(k)$ : impulse response of echo path model 1**
+
+| | | | | | | | | | | |
+|--------|--------|-------|-------|-------|------|------|-----|------|------|------|
+| -436 | 46150 | 390 | -3948 | -1098 | 745 | 1033 | 899 | 73 | -512 | -772 |
+| -829 | 34480 | -8191 | -2557 | -618 | 716 | 1091 | 716 | -119 | -580 | -820 |
+| -2797 | -10427 | -1751 | -3372 | -340 | 946 | 1053 | 390 | -109 | -704 | -839 |
+| -4208 | 9049 | -6051 | -1808 | -61 | 880 | 1042 | 313 | -176 | -618 | -724 |
+| -17968 | -1309 | -3796 | -2259 | 323 | 1014 | 794 | 304 | -359 | -685 | |
+| -11215 | -6320 | -4055 | -1300 | 419 | 976 | 831 | 304 | -407 | -791 | |
+
+
+
+Figure D.1: Impulse response and magnitude response of echo path model 1. The top plot shows the impulse response m1(k) versus Sample (0 to 120), with a peak value around 4.5 x 10^4. The bottom plot shows the magnitude response 20\*log(Mag. response) versus Freq. (Hz) (0 to 4000), comparing two input types: CSS input (solid line) and tones(s) input (dashed line). Both curves show a flat response around -10 dB until approximately 3000 Hz, where they roll off sharply.
+
+NOTE – 12 dB ERL, CSS input with scaling factor from Table D.1a (solid line), tones(s) input with scaling factor from Table D.1b (dashed line).
+
+**Figure D.1 – Impulse response and magnitude response of echo path model 1**
+
+**Table D.3 – $m_2(k)$ : impulse response of echo path model 2**
+
+| | | | | | | | | | | |
+|-------|--------|--------|-------|-------|-------|------|------|------|------|------|
+| -381 | -21370 | 13509 | -3858 | 1316 | -1468 | 789 | 658 | -331 | -479 | -249 |
+| 658 | -5307 | 17115 | -1979 | -693 | -1221 | 954 | 476 | -347 | -479 | -216 |
+| 1730 | 23064 | 13952 | 6029 | -759 | -842 | 756 | 377 | -430 | -512 | -249 |
+| -51 | 24020 | 13952 | 5616 | -1517 | -463 | 839 | 377 | -314 | -479 | -265 |
+| -3511 | 1020 | 97 | 7214 | -2176 | -298 | 872 | 262 | -430 | -397 | -166 |
+| -1418 | -12374 | -9326 | 6820 | -2028 | -68 | 1020 | 97 | -463 | -430 | -232 |
+| 7660 | -16296 | -9046 | 3935 | -2654 | 64 | 789 | -68 | -463 | -397 | |
+| 8861 | -19524 | -15208 | 3919 | -1814 | 493 | 822 | -183 | -414 | -298 | |
+| -8106 | -7480 | -9853 | 921 | -2077 | 723 | 558 | -232 | -381 | -265 | |
+
+
+
+The figure consists of two vertically stacked plots. The top plot shows the impulse response $m_2(k)$ over 120 samples. The y-axis is labeled $m_2(k)$ and has a scale factor of $\times 10^4$ at the top left. The y-axis ranges from -4 to 4, and the x-axis ranges from 0 to 120. The response shows a sharp initial peak around sample 10, followed by several smaller oscillations that decay towards zero. The bottom plot shows the magnitude response in dB versus frequency in Hz. The y-axis is labeled $20 \cdot \log(\text{Mag. response})$ and ranges from -60 to 0. The x-axis is labeled $\text{Freq. (Hz)}$ and ranges from 0 to 4000. Two curves are shown: a solid line representing CSS input with scaling factor from Table D.1a, and a dashed line representing tones input with scaling factor from Table D.1b. Both curves show a general downward trend as frequency increases, with some local peaks and dips. The solid line is generally higher than the dashed line in the mid-frequency range. A small label 'G.168(09)\_FD.2' is visible in the bottom right corner of the plot area.
+
+Figure D.2: Impulse response and magnitude response of echo path model 2. The top graph shows the impulse response m2(k) over 120 samples, with a scale factor of 10^4. The bottom graph shows the magnitude response 20\*log(Mag. response) in dB versus frequency in Hz from 0 to 4000 Hz, comparing two input types: CSS input (solid line) and tones input (dashed line).
+
+NOTE – 12 dB ERL, CSS input with scaling factor from Table D.1a (solid line), tones(s) input with scaling factor from Table D.1b (dashed line).
+
+**Figure D.2 – Impulse response and magnitude response of echo path model 2**
+
+**Table D.4 – $m_3(k)$ : impulse response of echo path model 3**
+
+| | | | | | | | | | | |
+|-------|--------|--------|-------|-------|------|-------|-------|------|------|------|
+| -448 | -26261 | 14164 | 3271 | -3101 | 2172 | -139 | -1066 | -814 | -233 | -390 |
+| -436 | -16249 | 13467 | 6566 | -9269 | 5387 | -573 | -1020 | -871 | -333 | -482 |
+| 2230 | 21637 | 4438 | 4277 | -6146 | 4598 | -1100 | -1100 | -734 | -356 | -459 |
+| 2448 | 25649 | 8627 | 11131 | -2553 | 3535 | -1157 | -1008 | -642 | -390 | -482 |
+| -4178 | -2267 | 456 | 7562 | -6272 | 4004 | -1180 | -1077 | -562 | -310 | -551 |
+| -7050 | -10311 | -11879 | 1475 | 811 | 2311 | -1455 | -1088 | -356 | -265 | -573 |
+| 5846 | -4693 | -6352 | 3728 | 124 | 2150 | -1123 | -917 | -379 | -368 | |
+| 18581 | -12690 | -5104 | -3525 | 788 | 1017 | -1386 | -917 | -345 | -310 | |
+| 2322 | -7428 | -7496 | -7301 | 5147 | 330 | -1123 | -963 | -230 | -310 | |
+
+
+
+The figure consists of two vertically stacked plots. The top plot displays the impulse response $m_3(k)$ against the sample number, ranging from 0 to 120. The y-axis is scaled by $10^4$ and ranges from -4 to 4. The response shows a sharp initial peak followed by several smaller oscillations that decay towards zero. The bottom plot shows the magnitude response $20 \cdot \log(\text{Mag. response})$ against frequency in Hz, ranging from 0 to 4000 Hz. The y-axis ranges from -60 to 0. Two curves are plotted: a solid line representing CSS input with a scaling factor from Table D.1a, and a dashed line representing tones(s) input with a scaling factor from Table D.1b. Both curves show a general downward trend as frequency increases, with a significant drop-off starting around 3500 Hz.
+
+Figure D.3: Impulse response and magnitude response of echo path model 3. The top plot shows the impulse response m3(k) over 120 samples, with a scale factor of 10^4. The bottom plot shows the magnitude response 20\*log(Mag. response) over a frequency range of 0 to 4000 Hz, comparing two input types: CSS input (solid line) and tones(s) input (dashed line).
+
+NOTE – 12 dB ERL, CSS input with scaling factor from Table D.1a (solid line), tones(s) input with scaling factor from Table D.1b (dashed line).
+
+**Figure D.3 – Impulse response and magnitude response of echo path model 3**
+
+**Table D.5 – $m_4(k)$ : impulse response of echo path model 4**
+
+| | | | | | | | | | | |
+|-------|--------|--------|-------|-------|-------|-------|-------|------|------|------|
+| 160 | 4041 | 14624 | 6850 | 2393 | 1592 | 2654 | 4617 | -220 | 203 | -57 |
+| 312 | 14484 | -6975 | 3944 | 2784 | -4752 | -881 | 3576 | -306 | -111 | -24 |
+| -241 | -1477 | -17156 | 6969 | -892 | -3646 | -4113 | 2382 | 257 | 95 | 30 |
+| -415 | -21739 | -187 | 8694 | -7366 | -5207 | -3244 | 2839 | 615 | -79 | -68 |
+| 897 | -4470 | 149 | -4068 | -3376 | -5577 | -7289 | -404 | 225 | 30 | 84 |
+| 908 | 25356 | 1515 | -3852 | -5847 | -501 | -3830 | 539 | 561 | 84 | -155 |
+| -1326 | 11458 | 14907 | -5793 | -2399 | -1174 | -4600 | -1803 | 8 | -13 | -68 |
+| -1499 | -19696 | 4345 | -9371 | 3011 | 4041 | -2508 | -1401 | 344 | -68 | 19 |
+| 2405 | -11800 | -7128 | 453 | 1537 | 5647 | 431 | -1705 | 127 | -241 | |
+| 3347 | 5766 | -2757 | 1060 | 6623 | 4628 | -144 | -2269 | -57 | -68 | |
+| -3624 | 789 | -10185 | 3965 | 4205 | 7252 | 4184 | -783 | 182 | -24 | |
+| -7733 | 6633 | -7083 | 9463 | 1602 | 2123 | 2372 | -1608 | 41 | 19 | |
+
+
+
+Figure D.4: Impulse response and magnitude response of echo path model 4. The top plot shows the impulse response m4(k) versus Sample (0 to 120), with a scale factor of 10^4. The response is a decaying oscillation. The bottom plot shows the magnitude response 20\*log(Mag. response) versus Freq. (Hz) (0 to 4000). It features two curves: a solid line (CSS input) and a dashed line (tones input). Both curves show a flat response between 500 Hz and 3000 Hz, with roll-offs at the low and high frequency ends. A label 'G.168(09)\_FD.4' is present in the bottom right corner.
+
+NOTE – 12 dB ERL, CSS input with scaling factor from Table D.1a (solid line), tones(s) input with scaling factor from Table D.1b (dashed line).
+
+**Figure D.4 – Impulse response and magnitude response of echo path model 4**
+
+## D.3 Echo path models measured from telephone networks in North America
+
+This clause presents four realistic digital echo path models measured from telephone networks in North America. The measurement method for the echo path models is described in clause II.2.2.1.
+
+Clause II.4 also includes the statistical characteristics (magnitude response, dispersion time width and the number of reflections) of echo paths measured in North America.
+
+Tables D.6, D.7, D.8 and D.9 below tabulate the four echo path models. The numbers are read in columns. The impulse responses as well as the magnitude responses of the models are shown in Figures D.5, D.6, D.7 and D.8 respectively.
+
+The echo path model shown in Table D.6 has a single reflection with a dispersion width of about 6 ms. This model has a frequency domain characteristic very close to the mean of the measured echo path magnitude responses. This kind of echo path occurs most often in the measurements.
+
+The echo path model shown in Table D.7 has a single reflection. It has a longer dispersion width of about 9 ms. The long dispersion width is due to the spectral peak at about 250 Hz.
+
+The echo path model shown in Table D.8 has double reflections. The impulse responses from the two reflectors are overlapped with each other. The dispersion width of this model is about 6 ms.
+
+Note that due to the specific magnitude response of echo path model $m_7$ , it may not be an effective model for Tests 10A and 10B when the NLP is disabled. This is, coincidentally, due to notches in the magnitude response at the frequencies used in the tests. Model $m_8$ in Table D.9 is an alternative double-reflection model that may be used for Tests 10A and 10B, since it does not contain notches in the magnitude response at the frequencies used in these tests.
+
+The impulse responses and magnitude responses of the four echo path models are shown in Figures D.5, D.6, D.7 and D.8. As an example, an ERL of 12 dB is chosen for the plots of magnitude responses.
+
+**Table D.6 – $m_5(k)$ : impulse response of the echo path model 5**
+
+| | | | | | | | | | | |
+|-----|------|-------|--------|-------|-------|-------|------|------|------|------|
+| 293 | 896 | 20 | -22548 | 3889 | -5022 | -1608 | 1640 | 733 | -513 | -404 |
+| 268 | 604 | -938 | -43424 | 7241 | -4039 | -645 | 1901 | 665 | -473 | -344 |
+| 475 | 787 | -523 | 2743 | 925 | -4842 | -495 | 1687 | 323 | -588 | -290 |
+| 460 | 561 | -1438 | 25897 | 2018 | -4104 | 279 | 1803 | 221 | -612 | -202 |
+| 517 | 538 | -1134 | 7380 | -821 | -4089 | 471 | 1543 | -14 | -652 | -180 |
+| 704 | 440 | -1887 | 21499 | -2068 | -3582 | 947 | 1566 | -107 | -616 | -123 |
+| 581 | 97 | -1727 | 11983 | -2236 | -2978 | 1186 | 1342 | -279 | -566 | |
+| 879 | 265 | -1698 | 10400 | -4283 | -2734 | 1438 | 1163 | -379 | -515 | |
+| 573 | -385 | -4266 | 11667 | -3406 | -1805 | 1669 | 963 | -468 | -485 | |
+
+
+
+The figure consists of two vertically stacked plots. The top plot shows the impulse response $m_5(k)$ on the y-axis (ranging from -4 to 4, scaled by $10^4$ ) against the sample number on the x-axis (ranging from 0 to 120). The response is near zero until approximately sample 25, where it exhibits a sharp negative spike reaching about $-4 \times 10^4$ , followed by a positive peak and subsequent oscillations that dampen over time. The bottom plot shows the magnitude response in $20 \cdot \log(\text{Mag. response})$ on the y-axis (ranging from -60 to 0) against frequency in Hz on the x-axis (ranging from 0 to 4000). Two curves are plotted: a solid line representing CSS input and a dashed line representing tones input. Both curves show a sharp drop at 0 Hz, a peak around 250 Hz, and a gradual decline towards 4000 Hz, with the solid line generally showing higher magnitude than the dashed line in the mid-frequency range.
+
+Figure D.5: Impulse response and magnitude response of echo path model 5. The top plot shows the impulse response m5(k) versus Sample (0 to 120), with a sharp negative peak around sample 30. The bottom plot shows the magnitude response 20\*log(Mag. response) versus Freq. (Hz) (0 to 4000), comparing CSS input (solid line) and tones input (dashed line).
+
+NOTE – 12 dB ERL, CSS input with scaling factor from Table D.1a (solid line), tones(s) input with scaling factor from Table D.1b (dashed line).
+
+**Figure D.5 – Impulse response and magnitude response of echo path model 5**
+
+**Table D.7 – $m_6(k)$ : impulse response of the echo path model 6**
+
+| | | | | | | | | | | |
+|------|------|------|--------|-------|-------|-------|-------|------|------|------|
+| 29 | -450 | 158 | 19522 | 2469 | 5025 | -1117 | -1956 | 1724 | 482 | -838 |
+| 109 | -105 | 1341 | 8421 | -7994 | 3946 | -2134 | -1539 | 1871 | 289 | -837 |
+| -83 | -503 | 195 | -50953 | 490 | 4414 | -2547 | -1239 | 1767 | 54 | -834 |
+| 198 | 145 | 1798 | -9043 | -3860 | 4026 | -2589 | -570 | 1802 | -137 | -740 |
+| -294 | -490 | 344 | 18046 | -837 | 3005 | -3310 | -377 | 1630 | -321 | -673 |
+| -135 | 267 | 1845 | -13553 | 490 | 3380 | -2778 | 251 | 1632 | -490 | -581 |
+| -415 | -231 | 629 | 13336 | -636 | 1616 | -3427 | 331 | 1379 | -638 | -493 |
+| -202 | 340 | 1604 | -3471 | 3682 | 2007 | -2779 | 964 | 1271 | -764 | -436 |
+| -444 | 77 | 1182 | -107 | 1141 | 158 | -3116 | 1177 | 1063 | -836 | -327 |
+| -337 | 343 | 940 | 1788 | 5019 | 388 | -2502 | 1449 | 856 | -800 | -201 |
+| -313 | 783 | 5163 | -7409 | 2635 | -1198 | -2399 | 1564 | 711 | -859 | |
+
+
+
+The figure consists of two vertically stacked plots. The top plot is the impulse response $m_6(k)$ versus Sample. The y-axis is labeled $m_6(k)$ and has a multiplier of $\times 10^4$ at the top. The y-axis scale ranges from -6 to 4. The x-axis is labeled 'Sample' and ranges from 0 to 120. The impulse response shows a sharp peak around sample 35, reaching a value of approximately $2.5 \times 10^4$ . The bottom plot is the magnitude response $20 \cdot \log(\text{Mag. response})$ versus Freq. (Hz). The y-axis is labeled $20 \cdot \log(\text{Mag. response})$ and ranges from -60 to 0. The x-axis is labeled 'Freq. (Hz)' and ranges from 0 to 4000. Two curves are shown: a solid line (CSS input) and a dashed line (tones(s) input). Both curves show a sharp peak around 200 Hz, followed by a relatively flat response between 1000 Hz and 3500 Hz, and a sharp drop-off above 3500 Hz. The label 'G.168(09)\_FD.6' is visible in the bottom right corner of the plot area.
+
+Figure D.6: Impulse response and magnitude response of echo path model 6. The top plot shows the impulse response m6(k) versus Sample (0 to 120), with a peak value of approximately 2.5 x 10^4. The bottom plot shows the magnitude response 20\*log(Mag. response) versus Freq. (Hz) (0 to 4000), comparing two inputs: CSS input (solid line) and tones(s) input (dashed line). The magnitude response is relatively flat between 1000 Hz and 3500 Hz, with a sharp drop-off above 3500 Hz.
+
+NOTE – 12 dB ERL, CSS input with scaling factor from Table D.1a (solid line), tones(s) input with scaling factor from Table D.1b (dashed line).
+
+**Figure D.6 – Impulse response and magnitude response of echo path model 6**
+
+Note that due to the specific magnitude response of echo path model $m_7$ , it may not be an effective model for Tests 10A and 10B when the NLP is disabled. This is, coincidentally, due to notches in the magnitude response at the frequencies used in the tests.
+
+**Table D.8 – $m_7(k)$ : impulse response of the echo path model 7**
+
+| | | | | | | | | | | |
+|------|-------|--------|-------|--------|--------|-------|-------|------|------|-----|
+| 258 | -343 | -1601 | 8950 | 18072 | -4342 | 6868 | 1239 | -415 | -325 | 365 |
+| -111 | -596 | -1389 | -1574 | -14410 | -7415 | -2195 | 2 | -372 | -245 | 303 |
+| 337 | -177 | -13620 | 758 | -7473 | 7929 | 3425 | -427 | -769 | -255 | 251 |
+| -319 | -1187 | -720 | 3526 | 19836 | -10726 | 1969 | 596 | -183 | -60 | 230 |
+| 347 | -52 | 33818 | -3118 | -16854 | 6239 | -109 | -1184 | -785 | 35 | 209 |
+| -434 | -1781 | -10683 | 2421 | -3115 | -2526 | 3963 | 551 | -270 | 218 | 179 |
+| 192 | -147 | -6742 | -8966 | 9483 | -1317 | -1275 | -1244 | -659 | 149 | |
+| -450 | -1959 | 12489 | -4901 | -17799 | 5345 | 3087 | 141 | -377 | 340 | |
+| -108 | -326 | -9862 | 11385 | 7399 | -4565 | -892 | -743 | -523 | 233 | |
+
+
+
+The figure consists of two plots. The top plot shows the impulse response $m_7(k)$ versus Sample. The y-axis is labeled $m_7(k)$ and has a scale factor of $\times 10^4$ at the top. The y-axis range is from -3 to 4. The x-axis is labeled 'Sample' and ranges from 0 to 120. The plot shows a sharp initial peak around sample 20, followed by a decaying oscillatory response. The bottom plot shows the magnitude response $20 \cdot \log(\text{Mag. response})$ versus Freq. (Hz). The y-axis is labeled $20 \cdot \log(\text{Mag. response})$ and ranges from -60 to 0. The x-axis is labeled 'Freq. (Hz)' and ranges from 0 to 4000. There are two curves: a solid line representing CSS input with scaling factor from Table D.1a, and a dashed line representing tones input with scaling factor from Table D.1b. Both curves show a series of peaks and dips across the frequency spectrum. A label 'G.168(09)\_FD.7' is present in the bottom right corner of the plot area.
+
+Figure D.7: Impulse response and magnitude response of echo path model 7. The top plot shows the impulse response m7(k) versus Sample (0 to 120), with a scale factor of 10^4. The bottom plot shows the magnitude response 20\*log(Mag. response) versus Freq. (Hz) (0 to 4000), comparing CSS input (solid line) and tones input (dashed line).
+
+NOTE – 12 dB ERL, CSS input with scaling factor from Table D.1a (solid line), tones(s) input with scaling factor from Table D.1b (dashed line).
+
+**Figure D.7 – Impulse response and magnitude response of echo path model 7**
+
+**Table D.9 – $m_8(k)$ : impulse response of the echo path model 8**
+
+| | | | | | | | | | | |
+|------|--------|--------|--------|--------|-------|------|-----|-----|-----|------|
+| 80 | -102 | -1457 | 33871 | -5907 | 5553 | 3083 | 806 | 452 | 669 | 356 |
+| 31 | -26 | -229 | -176 | -10257 | -2596 | 1917 | 869 | 538 | 619 | 147 |
+| 4 | 1002 | 15659 | -16421 | 5336 | 3992 | 1756 | 471 | 717 | 500 | 107 |
+| 42 | -9250 | -6786 | 18173 | -12933 | 1255 | 2478 | 646 | 723 | 650 | -50 |
+| 42 | -22562 | 16791 | -9669 | 4348 | 1450 | 1027 | 438 | 850 | 615 | -88 |
+| -61 | 39321 | 3860 | -10163 | -4802 | 4079 | 1871 | 449 | 756 | 516 | -59 |
+| -81 | 35681 | 2239 | 9941 | -1791 | 324 | 845 | 432 | 753 | 492 | -238 |
+| -64 | -35289 | -28730 | -19365 | 3035 | 4340 | 1284 | 473 | 899 | 427 | -165 |
+| -121 | 25312 | -11885 | 3592 | -4433 | 1059 | 813 | 394 | 555 | 291 | -183 |
+
+
+
+Figure D.8: Impulse response and magnitude response of echo path model 8. The top plot shows the impulse response m8(k) versus Sample (0 to 120), with a scale factor of 10^4. The response starts at 0, has a sharp negative peak around sample 15, followed by several oscillations that decay towards zero. The bottom plot shows the magnitude response 20\*log(Mag. response) versus Freq. (Hz) (0 to 4000). It features two curves: a solid line (CSS input) and a dashed line (tones input). Both curves show a series of peaks and dips, with the solid line generally having higher magnitude than the dashed line. The dips occur at approximately 500 Hz, 1500 Hz, 2500 Hz, and 3500 Hz.
+
+NOTE – 12 dB ERL, CSS input with scaling factor from Table D.1a (solid line), tones(s) input with scaling factor from Table D.1b (dashed line).
+
+**Figure D.8 – Impulse response and magnitude response of echo path model 8**
+
+## D.4 Echo path models measured from telephone networks in Europe
+
+Measurements were made in the telephone networks in France (see clause II.2.2.2 for measurement method and clause II.4.2 for typical impulse responses observed). Three different types of echo path impulse responses were observed and they have equivalent characteristics of echo path models $m_1(k)$ , $m_5(k)$ and $m_6(k)$ .
+
+# Annex E
+
+# Embedded Echo Cancellers (EECs)
+
+(This annex forms an integral part of this Recommendation.)
+
+## E.1 Scope
+
+This annex applies to embedded echo cancellers (EECs). Its purpose is to define performance requirements for an embedded echo canceller function, together with a test set-up that may be used to perform tests.
+
+Characteristics of an embedded echo canceller include:
+
+- Limited or no access to the control signals used to perform ITU-T G.168 tests (e.g., h-register freeze, NLP on/off).
+- Limited or no access to conventional 4-wire TDM signal ports. Examples include echo cancellers embedded in access gateways where the interface at the cancelled-end is 2-wire analogue and echo cancellers embedded in IP gateways where at least one interface is packet-based.
+
+## E.2 Definitions
+
+This annex defines the following terms:
+
+### E.2.1 Embedded echo canceller (EEC)
+
+An echo canceller function that may not provide access to control signals (e.g., h-register freeze) that are necessary to perform some of the tests in ITU-T G.168.
+
+NOTE – In addition, some EECs may have no direct access to some or all of the input-output ports ( $R_{in}$ , $R_{out}$ , $S_{in}$ , $S_{out}$ ). An example of this is an EEC integrated with other voice processing functions in a single device.
+
+## E.3 EEC requirements
+
+An embedded echo canceller that complies with this annex will pass all of the mandatory tests in the body of ITU-T G.168 and any optional tests that are applicable to the intended application of the device containing the EEC. Compliance or partial compliance may be tested using one of the test methodologies defined in Appendix VIII.
+
+### E.3.1 EEC performance under load
+
+The performance requirements given in the paragraph regarding multiple channel implementations in clause 6.4.2 also apply to EECs. Specific tests for EEC performance under load are for further study.
+
+## E.4 EEC testing
+
+Figure E.1 shows the test set-up that may be used for performing ITU-T G.168 tests according to this annex. This test set-up requires clear channel access via ITU-T G.711 coding to $R_{in}$ , $R_{out}$ , $S_{in}$ and $S_{out}$ ports of the EEC.
+
+NOTE 1 – If an echo canceller is embedded with other signal processing functions, the other functions should be disabled while performing these tests. It is also recommended that further testing is performed with the other signal processing functions enabled to evaluate their effect on overall performance.
+
+
+
+Figure E.1 – Test set-up for use with EECs. The diagram shows a 'Call set-up' block connected to a 'Gateway controller', which is connected to an 'EEC host (gateway)'. Inside the host is the 'EEC function under test (channel i)'. A 'Signal generator (Ch i)' provides an input signal R\_in(Ch i) to an 'A/μ encode/decode packetise/de-packetise p layout buffer'. A 'Measurement device (Ch i)' receives an output signal S\_out(Ch i) from the same buffer. The buffer is connected to a 'Non-Cancelled-end packet interface e.g., GigE'. The 'EEC function under test' receives R\_in and sends S\_out to the buffer. The buffer also receives R\_in from all channels except Ch i from a 'Traffic generator (All channels except Ch i)'. The 'EEC function under test' sends R\_out to a 'Cancelled-end TDM interface e.g., STM1-1'. This interface is connected to an 'A/μ encode/decode Mux/Demux'. The 'Mux/Demux' sends S\_in to the 'EEC function under test' and also connects to two 'Echo path g(k)' blocks. One 'Echo path g(k)' is for 'Ch i' and the other is for 'All channels except Ch i'. Both echo paths are summed with a signal S\_gen(Ch i) from a 'Signal generator (Ch i)' via a switch. The diagram is labeled G.168(15)\_FE.1.
+
+G.168(15)\_FE.1
+
+**Figure E.1 – Test set-up for use with EECs**
+
+NOTE 2 – The test set-up in Figure E.1 is not applicable to access gateways, where the interface is 2-wire analogue.
+
+NOTE 3 – Call set-up may either be performed via the gateway controller (as shown) or by any other means (e.g., using permanently "nailed-up" connections via a special "Test Mode").
+
+NOTE 4 – ITU-T G.168 tests are performed on a single channel only. The other channels are loaded using the Traffic Generator.
+
+NOTE 5 – $g(k)$ represents any of the echo path models depicted in Figure 6 or Figure 7 of this Recommendation.
+
+Possible approaches are given in Appendix VIII for testing an embedded echo canceller, depending on what control signals are available.
+
+## E.5 Special considerations
+
+For the purpose of evaluating echo cancellation performance, the embedded speech codec should be set to the highest coding rate or the best quality mode when generating the $R_{in}$ signal for the testing of the embedded echo canceller. Any voice activity detection (VAD), discontinuous transmission (DTX) or other silence compression functions should also be disabled.
+
+# Appendix I
+
+## Guidance for application of echo cancellers
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## I.1 Scope
+
+Echo cancellers are adaptive signal processors used to control echo; they are expected to replace echo suppressors in modern telecommunication networks. Echo cancellers are increasingly present on nearly every long distance connection and may be encountered singly or in tandem on a given connection. The purpose of this appendix is to:
+
+- explain the general principles of operation of echo cancellers;
+- identify a limited set of application rules and the constraints under which echo cancellers operate;
+- identify how echo cancellers may affect the perceived quality of speech and the quality of voiceband data;
+- explain the effects of high-level speech on echo cancellers;
+- provide network and service evolutionary considerations;
+- offer some considerations of echo canceller performance during double talk;
+- provide some guidelines on the use of parameters for testing echo cancellers.
+
+## I.2 Echo control in the public switched telephone network
+
+In the past, echo suppressors were used to control echo in long distance networks. Today, however, the echo canceller is the device of choice. While public switched telephone network (PSTN) planners and designers typically deploy the most current and modern technologies, it should be understood by modem designers, end users, and others, that for the foreseeable future the worldwide embedded plant may include some older echo control technologies on some connections. For example, connections through the PSTN may include some combinations of ITU-T G.164 analogue or digital echo suppressors, ITU-T G.165 analogue or digital echo cancellers equipped with ITU-T G.164 tone disableers, and ITU-T G.165 analogue or digital echo cancellers and digital echo cancellers of this Recommendation equipped with ITU-T G.165 or ITU-T G.168 tone disableers. The following two clauses summarize the reasons for the use of echo cancellers instead of echo suppressors in modern telephone networks.
+
+### I.2.1 Echo suppressors
+
+The principle of echo suppressors is well-known; it is summarized as follows: When speech is detected on the receive path, a very high attenuation is inserted in the send path. When double talk is detected, the send path is closed and a receive loss is inserted in the receive path. Thus, during double talk, there is no echo suppression in the send path, but the echo is more attenuated than the direct speech. Other refinements are possible, as indicated in [ITU-T G.164].
+
+Generally, echo suppressors do not provide the same level of performance for speech, voiceband data, or facsimile as echo cancellers. Many problems can occur in the operation of echo suppressors. First, low level double talk speech could be mutilated if the echo level is high. Second, the tandeming of echo suppressors is not recommended. Third, echo suppressors may create problems for facsimile transmission. Clause 5.2 of [ITU-T G.161] contains the detailed explanation about the disadvantages of echo suppressors.
+
+### 1.2.2 Echo cancellers
+
+Echo cancellers are devices that use adaptive signal processing to reduce or eliminate echoes. Echo cancellers are placed in the 4-wire portion of a circuit, and reduce (or cancel) the echo by subtracting an estimate of the echo from the returned echo signal. Echo cancellers may operate on a single circuit or on a multiplexed facility, e.g., echo cancellers operate on a 64 kbit/s speech facility that is multiplexed into a primary rate link.
+
+Echo cancellers are designed to:
+
+- cancel linear echo path signals;
+- refrain from cancelling the echo when requested to do so by an in-band disabling signal;
+- return to an operational mode after being disabled when the in-band signal power level drops below a specified level for a specified period of time. This design allows some networks to transport voiceband data on the same speech channels. It also allows the echo canceller to re-enable during a voice call after it has been turned off erroneously (talkoff).
+
+Echo cancellers are characterized by whether the interface path is analogue or digital, and/or whether the subtraction of the echo is by analogue or digital means. This appendix is limited to echo cancellers that have a digital input and digital subtractors.
+
+Echo cancellers have the following main advantages over echo suppressors:
+
+- send path transparency is improved;
+- NLP hangover introduces fewer impairments;
+- there is no receive insertion loss;
+- echo cancellation continues during double talk;
+- tandeming is possible (for well-designed echo cancellers).
+
+Some echo cancellers are optioned to disable on the 2100 Hz tone specified in [ITU-T G.164] for echo suppressors, and some are disabled with a 2100 Hz tone with periodic phase reversals of $180^\circ \pm 25^\circ$ , as specified in [ITU-T G.165] and in this Recommendation for echo cancellers. Use of ITU-T G.165 or ITU-T G.168 tone is intended to allow echo cancellers to be disabled independently of echo suppressors. Echo cancellers that respond to ITU-T G.165 or ITU-T G.168 disabling tone are not disabled by the 2100 Hz tone without phase reversal.
+
+### 1.2.3 Responsibilities of modem manufacturers and end users
+
+It is the responsibility of the modem manufacturers and end users to understand the characteristics of the network-based echo canceller fully and decide whether the echo cancellers should be enabled or disabled. If the modem manufacturers and end users decide that the network-based echo canceller functionality should be disabled, they should ensure that the terminal uses the appropriate approved methods, defined in Recommendations, to disable cancellers. Additionally, it is the end user's responsibility to ensure that terminals and private networks are designed to operate in a fashion compatible with the PSTN network-based echo cancellers. For example:
+
+- Digital telephone sets are expected to control their own echoes, see [ITU-T G.122], [ITU-T G.131], [ITU-T P.340] and [ITU-T P.310] (the PSTN network is not responsible for cancelling acoustic echoes).
+- Terminals and private networks should be designed to provide circuit extensions compatible with the design intent of the PSTN, e.g., echo paths outside the PSTN-network should be linear and time-invariant or the terminal should control its own echo.
+
+- Either the delay of the terminal or private network should be within the operational limits of the network-based echo canceller, or the terminal/private network should control its own echo.
+
+## **I.3 Application rules and operational constraints**
+
+The following items should be considered for application rules and operational constraints of echo cancellers:
+
+- public network transmission planning;
+- transmission delay and echo return loss;
+- echo-path characteristics and echo-path capacity of an echo canceller;
+- end user/manufacturer/private network transmission planning.
+
+The detailed descriptions of these items can be found in ITU-T Recommendations on transmission planning aspects of echo cancellers (see [b-ITU-T G.108.2]).
+
+## **I.4 Effect of cancellers on voice and data services**
+
+Network-based echo cancellers are present on connections that experience long delays. They should be designed to allow a speech channel to support voiceband data, including facsimile. This means that they should retain the capability of being disabled upon an appropriate request from customer terminal equipment. However, the modem manufacturer is responsible for determining if network-based echo cancellers should be enabled or disabled.
+
+Full-duplex data transmission in the voiceband can occur, depending on the modem modulation scheme. New modulation schemes are being introduced, and manufacturers should determine the optimal state in which the echo canceller should be when the modem is operating, i.e., if the canceller should be enabled or disabled, or whether the call should be routed on a connection that never has an echo canceller functionality present.
+
+The designers of facsimile terminals generated these terminals with the understanding that network providers were installing network-based echo control devices as per [ITU-T G.164], [ITU-T G.165] and this Recommendation. Thus, PSTN network planners were expected to continue to evolve the network in such a way that it would not knowingly prevent the continued carriage of a permissive voiceband data/facsimile service.
+
+ITU-T V.32 modems, in contrast, use the same band of frequencies in both directions and achieve duplex operation through the use of an integrated echo canceller. The echo canceller integrated in this voiceband data modem is not to be confused with the network echo cancellers that conform to [ITU-T G.165] and to this Recommendation because the performance requirements for each are very different.
+
+Details of the interaction of echo control with voiceband data and facsimile transmission can be found in clause 5.2.1 of [ITU-T G.161].
+
+## **I.5 High-level speech**
+
+### **I.5.1 Introduction**
+
+A number of sources could produce high speech levels in the network. In hands-free telephones, for example, the microphone may allow high speech levels to be generated. With this perspective in mind, [ITU-T G.165] was modified in 1993 to include an overload test (Test No. 8) at levels exceeding 0 dBm0 and to increase the maximum test levels from –10 dBm0 to 0 dBm0.
+
+The presence of high speech levels may cause increased non-linearities that would degrade the performance of some echo cancellers, especially echo cancellers that have not been implemented in a fully digital manner. Another area in which high signal levels may cause difficulty is in the double talk detection and non-linear processor control circuits. These are discussed in the following two clauses.
+
+### **I.5.2 Double talk detection and activity detection**
+
+The performance of echo cancellers is very dependent on the activity detection and double talk detection algorithms used. For example, if double talk is not recognized quickly, the cancelled end speech masks the residual echo that is used to update the impulse response model of the echo canceller.
+
+The following items are for further study:
+
+- the effect of activity detection algorithms for low bit rate coders;
+- the effect of double talk detection in the presence of high signal levels.
+
+New echo canceller requirements for echo canceller design may result.
+
+### **I.5.3 Effects of low bit rate coders**
+
+For network planning purposes it is useful to know what degradation low-bit rate coders in the echo path of an echo canceller may cause. An echo canceller may provide a certain amount of echo return loss enhancement.
+
+This topic is for further study.
+
+### **I.5.4 Effects of a non-linear echo path**
+
+The theory of echo cancellation assumes that the echo path is linear and time-invariant. An echo canceller will have limited ability to cancel echo in the presence of a non-linear echo path resulting from clipping and non-linear distortion in the echo path between $R_{out}$ and $S_{in}$ . More information about the effects of non-linear echo path can be found in clause 5.2.5.1 of [ITU-T G.161].
+
+### **I.5.5 Guidelines for $R_{out}$ usage in echo cancellers**
+
+The configuration in which the same signal feeds both $R_{in}$ and the echo path may result in degraded performance if $R_{out}$ is not digitally equivalent (bit for bit) to $R_{in}$ under all signal conditions. The signal $R_{rev}$ used internally by the echo canceller after passing through the $R_{in}$ port can be used as the source signal for the echo path. Therefore, it is recommended that $R_{out}$ (which is used to drive the echo path) should be digitally equivalent to $R_{rev}$ .
+
+## **I.6 Network and service evolutionary considerations**
+
+### **I.6.1 Bit transparency of echo cancellers**
+
+[ITU-T G.165] was amended in 1993 to make it clear that a 2100 Hz disabling tone with phase reversals should cause the echo canceller to disable and provide an analogue clear-channel signal path. In other words, a tone between 300 Hz and 3400 Hz should pass with its power level and frequency unaltered through the echo canceller, but 64 kbit/s bit-transparency is not guaranteed (see clause 3.3 of [ITU-T G.165]). It is noted that 64 kbit/s transparency is achievable and is implemented in some echo cancellers, but to remain in that state, the in-band power level should remain above a predefined power level.
+
+If cancellers are to be applied to trunks and disabled by use of a "switch to echo canceller signalling channel", the canceller should support a 64 kbit/s clear channel capability, if such capability is to be provided.
+
+### I.6.2 Convergence speed
+
+High speed of convergence is desirable to reduce echo during initial acquisition, and to minimize echo when the echo path is changing. Some echo cancellers generate noise in trying to continuously adapt to the echo path. This may be related to adaptation speed. The effect is very noticeable and annoying, especially during double talk, if the adaptation process is not suspended. For some echo canceller implementations, as the speed of adaptation is increased beyond the optimum speed, the accuracy of the transfer function after adaptation becomes poorer. High speed of convergence is desirable for initial acquisition, while lower convergence may be needed for subsequent tracking, since the echo transfer function changes very slowly. The need of high convergence speed when time varying components are in the echo path is still under study.
+
+### I.6.3 Acoustic echo control and environments
+
+Acoustic echo control is becoming an important issue due to the increase in hands-free telephone sets. Although there is some commonality between issues encountered for acoustic echo cancellation and network echo cancellation, there are also many differences. The issues of level points, natural echo path loss (or gain), degree of loss-switching, as well as level and/or type of singing (howling) protection are all important to a study of acoustic echo cancellers. In addition, it is important that an acoustic echo canceller is capable of working in harmony with a network-based electric echo canceller.
+
+#### I.6.3.1 References to acoustic echo control
+
+The following materials are extracted from the Recommendations related to acoustic echo control.
+
+Information about acoustic echo controllers and speech enhancement devices can be found in clause 10 of [ITU-T P.340].
+
+##### I.6.3.1.1 Weighted terminal coupling loss (TCLw) (from clause 6.1 of [b-ITU-T P.341])
+
+The TCLw measured from the digital input to digital output shall be at least 35 dB when corrected to the nominal values of SLR and RLR as specified in clauses 4.1 and 5.1 of [b-ITU-T P.341], respectively. If a volume control is provided, the requirement applies at a setting as close as possible to the nominal value of RLR as specified in clause 5.1 of [b-ITU-T P.341].
+
+##### I.6.3.1.2 Terminal coupling loss (from clause 6.1 of [b-ITU-T P.342])
+
+The weighted terminal coupling loss (TCLw) should be greater than 40 dB when measured under field conditions and with SLR normalized to SLR = +13 dB and RLR = +2 dB. For example, if the measured TCLw is 42 dB, the measured SLR is +16 dB and the measured RLR is 0 dB, then the normalized value of TCLw = 42 dB + (13 – 16) dB + (2 – 0) dB = 41 dB.
+
+However, in order to meet ITU-T G.131 talker echo objective requirements, a TCLw greater than 45 dB is desirable and should be striven for.
+
+NOTE – The perceived echo impairment, by the person at the opposite end of the connection from a telephone set that has a TCLw of less than 45 dB, is a function of the magnitude of the talker echo signal as well as the talker echo path delay. A telephone set that has a TCLw of less than 45 dB will provide an echo signal that becomes more disturbing as the talker echo path delay increases. Thus, a telephone set that has a TCLw of less than 45 dB may provide satisfactory performance on low delay connections while the same may not be true for connections that have a long delay.
+
+It is assumed that this requirement is met if TCL and TCLw, respectively, meet the values of Table I.1 with the receive volume control in its maximum setting.
+
+**Table I.1**
+
+| TCL (1/3-octave band) | TCLw |
+|---------------------------------------------------------------------|-------------|
+| > 25 dB | > 35 dB |
+| NOTE – These values assume no other echo control in the connection. | |
+
+If information is available in the terminal about the one-way transmission time of the connection, and if the terminal operates in double talk, then the limits defined in Table I.2 may apply.
+
+**Table I.2**
+
+| | One-way transmission time | TCLw |
+|----------------------------------------------------------------------------------------|----------------------------------|----------------------------|
+| Single talk | $\leq 10$ ms | $\geq 25$ dB |
+| Double talk | $\leq 10$ ms | $\geq 19$ dB a) |
+| a) To achieve MOS $\geq 4$ . Further information is found in [ITU-T P.340]. | | |
+
+### I.6.4 Comfort noise
+
+As the telephone network migrates to more digital connections, it becomes more likely that the echo path will be analogue while the long distance connections path will be digital. One consequence is that the long distance path has a low idle channel noise while the echo path has a higher idle channel noise. This in turn leads to a situation called "noise modulation". When the NLP operates, the talker "hears" the idle channel noise of the digital long distance path, but when the NLP releases, the talker "hears" the idle channel noise of the echo path and the far-end environmental noise. Thus, the talker hears intervals of speech with background noise followed by intervals of silence, which can be very annoying in some instances.
+
+There are two known approaches for comfort noise. The first solution is to insert pseudo-random noise during the silent interval. The second solution is to allow some of the background or idle channel noise to pass through the NLP.
+
+NOTE – Based on the input from ITU-T experts on "end-to-end transmission performance of networks and terminals":
+
+- Artefacts due to comfort noise insertions should be minimized.
+- The noise used should match the background noise, both in frequency content and level (discussions indicate that this may not be a good idea for high and low noise levels).
+- Level of the inserted noise should match that of the background noise; appropriate level measurements and adjustments should be done using dBm0p.
+- The time course of changes in the level of the inserted noise should match, as closely as possible, the level changes that are occurring in the background noise.
+
+## I.7 Considerations regarding echo canceller performance during double talk
+
+### I.7.1 Introduction
+
+A double talk situation (as the name suggests) could occur when both signals present at the input of an echo canceller have characteristics of active speech.
+
+The CSS, which simulates double talk, consists of a burst (of constant energy) and a real pause. However, it was shown that a better double talk signal could be achieved with a signal in which the two bursts with high signal energy are identical to the original one, while the pause is filled up with
+
+a shortened CSS consisting of a voiced sound, a noise sequence and a real pause. Figure I.1 shows the modified double talk signal with the sequence length of 800 ms.
+
+
+
+Figure I.1: Modified double talk signal waveform. The plot shows a complex signal with two main active segments. The first segment is from 0 to approximately 0.35 seconds, featuring a dense, noisy waveform with peaks reaching up to 25 and down to -20. This is followed by a short, low-amplitude pause until about 0.4 seconds. The second active segment begins at 0.4 seconds and continues to the end of the plot at 0.8 seconds, showing a similar dense, noisy waveform. The x-axis is labeled from 0 to 0.8 in increments of 0.1. The y-axis is labeled from -20 to 26 in increments of 10. A small label 'G.168(09)\_FI.1' is visible in the bottom right corner of the plot area.
+
+**Figure I.1 – Modified double talk signal**
+
+### I.7.2 Double talk parameters
+
+The performance of echo cancellers under conditions of double talk is determined by many parameters. From recordings and listening tests, the following aspects can be derived:
+
+- One of the most noticeable degradations when listening to the double talk signal is caused by the erroneous insertion of the NLP during continuous speech.
+- Speech gaps caused by the NLP as mentioned above during continuous speech seem to be more annoying than clipping at the beginning of a double talk sequence (first word of the first sound).
+- The detectability and annoyance of echo signals during double talk depend on the echo signal level and echo signal sound.
+- Echo cancellers behave in a different way if double talk occurs at the beginning of adaptation or after full convergence.
+- Based on the input from ITU-T experts on "end-to-end transmission performance of networks and terminals": Temporal clipping (i.e., syllable clipping or mutilation) introduced by the NLP should be less than 64 ms and less than 0.1% of active speech.
+
+### I.7.3 Analysis of technical parameters that influences performance under double talk conditions
+
+The following parameters need to be taken into account when defining a test signal and the measurement procedure:
+
+- signal levels at the $R_{in}$ and $S_{gen}$ port (receive signal and double talk signal);
+- level ratio and time pattern of both signals at the $R_{in}$ and the $S_{gen}$ port;
+- time of double talk (convergence status of echo canceller);
+- duration of double talk.
+
+The performance of the echo canceller itself is determined by technical parameters such as:
+
+- 1) sensitivity of double talk detection;
+- 2) threshold level of double talk detection (insertion of NLP, possible adaptive control);
+- 3) reliability of double talk detection;
+- 4) switching time of NLP;
+- 5) double talk detection hangover time;
+- 6) frequency characteristics of the residual echo signal loss measured between the $R_{in}$ and $S_{out}$ port (ERL versus frequency, "sound" of echo signal);
+- 7) divergence during double talk.
+
+Again these influencing parameters can be separated into different groups:
+
+- points 1-3 are determined by the performance of double talk detection (sensitivity, reliability);
+- the switching characteristics of the NLP determine points 4 and 5;
+- points 6 and 7 (frequency characteristics, i.e., ERL vs. frequency and divergence) depend on the filter algorithm.
+
+A suitable measurement procedure to evaluate double talk performance requires a suitable measurement sequence. A combination of two composite source signals was derived to reproduce typical speech double talk sequences. Both signals are described in [ITU-T P.501]. The length of the measurement CSS is 700 ms, the second CSS, which simulates the double talk fed into the echo path, has a duration of 800 ms. Due to their different sequence length, the level relationships on both echo cancellers inputs $R_{in}$ and $S_{gen}$ (or) $S_{in}$ change, if both signals are periodically repeated. The same relationships can be observed if real speech signals are used. Various measurements on different echo cancellers demonstrate that this signal combination reproduces results under double talk conditions compared to speech.
+
+### I.7.4 Conducting the double talk Tests 3A and 3B without inhibiting the adaptation
+
+#### I.7.4.1 Introduction
+
+In Tests 3A and 3B, the echo canceller is exposed to double talk for some time $\delta t$ and the convergence $C$ /divergence $D$ is determined thereafter by removing the double talk and freezing the adaptation while the CSS remains active on the receive-in port. Thus, each experiment yields only one single point of the graph $C = C(\delta t)$ or $D = D(\delta t)$ . Instead, one could measure the whole graph $C = C(\delta t)$ or $D = D(\delta t)$ in one experiment by subtracting the cancelled end double talk component $s_{gen}(k)$ from the signal $e(k)$ at the send-out port. The difference $e_r(k) = e(k) - s_{gen}(k)$ would be the residual echo, which directly leads to $C = C(\delta t)$ or $D = D(\delta t)$ .
+
+#### I.7.4.2 Test procedure
+
+The test is performed using the test configuration of Figure I.2. For high levels of $s_{gen}(k)$ , the magnitude of sum of $s_{gen}(k)$ and the echo, $g(k)*c(k)$ , may exceed the linear range of the A/ $\mu$ -law coder. As a result, the echo canceller sees the saturated value of $s_{gen}(k)+g(k)*c(k)$ . The double-talk component at the send-in port becomes:
+
+$$s_{gen\_sat}(k) = \text{codec}[s_{gen}(k) + g(k)*c(k)] - g(k)*c(k)$$
+
+Thereby the function $\text{codec}(\cdot)$ is defined as a linear to A/ $\mu$ -law conversion followed by an A/ $\mu$ -law to linear conversion. The signal $s_{gen\_sat}(k)$ is computed by the far left blocks of Figure I.2.
+
+Some echo cancellers contain a high- or bandpass filter in the send-path. If that is the case, $s_{gen\_sat}(k)$ must be passed through such a filter before it can be subtracted from the send-out signal. This can be achieved in various ways. If the filter is known, it appears simplest to pass $s_{gen\_sat}(k)$ directly through the filter. If it is unknown, one can pass $s_{gen\_sat}(k)$ through the echo canceller while there is silence on the receive-in port (see Figure I.2). The obtained signal $s_{gen\_sat\_filt}(k)$ represents the double talk component of the send-out signal, and can be subtracted to compute the residual echo $e_r(k)$ .
+
+The requirements on the power level of $e_r(k)$ should be the same as on $L_{RES}$ . This procedure provides a continuous (rather than discrete) view of the echo canceller behaviour throughout the double-talk course. Hence, it does not require freezing the echo canceller adaptation, and it eliminates the possibility of a potential distortion of the echo canceller measured performance. Note that the $S_{out}$ signal is measured during the application of the double talk signal, $S_{gen}$ .
+
+
+
+Block diagram of a test setup to subtract the double talk component from the send-out signal. The diagram shows two echo canceller (EC) blocks. The top EC block has inputs Sgen\_sat(k) and Silence (via x(k)). It outputs Sgen\_sat\_filt(k) and c(k). The bottom EC block, labeled 'EC under test', has inputs y(k) and x(k). It outputs e(k) and c(k). A 'Codec' block processes Sgen(k) to produce y(k). A summation node subtracts Sgen\_sat\_filt(k) from Sgen\_sat(k) to produce e\_res(k), which is then evaluated. Control signals 'Disable NLP' and 'Reset H reg.' are shown for the bottom EC block. Signal labels include S\_in, R\_out, R\_in, and S\_out.
+
+Figure I.2 – Test to subtract the double talk component from the send-out signal
+
+### I.7.5 Subjective and objective echo canceller testing
+
+#### I.7.5.1 Subjective and objective echo canceller testing – Fundamentals
+
+One of the most important points in studying the performance of echo cancellers is to investigate how objective tests correlate with subjective tests.
+
+The subjective test procedures (conversational test, talking and listening tests, listening-only tests) were suggested for standardization in [b-ITU-T P.831]. Based on the data from subjective tests parameters, determining the transmission quality for speech echo cancellers can be identified and in a second step conclusions can be drawn about important test procedures and requirements for laboratory tests.
+
+The following clauses summarize how subjective test results were used in order to develop objective tests.
+
+##### 1.7.5.1.1 Auditory test procedures
+
+Figure I.3 demonstrates the structure and relation of the different subjective test procedures like *conversational tests*, *talking and listening tests* and *listening-only tests* together with parameters which can be assessed by these tests. The different procedures were developed as parts of the whole test set-up. The procedures were not performed in isolation but each test for a certain purpose.
+
+
+
+The diagram illustrates the structure of subjective test procedures for speech echo cancellers. It is organized into three columns. The left column shows a vertical axis representing the spectrum of test conditions, ranging from **Realistic test conditions** at the top to **Exactly defined measurement conditions** at the bottom. This axis is marked with **reality +** and **comparability, sensitivity +**. The middle column lists three test procedures: **Conversational tests** (2 subjects, far end and near end), **Talking and listening tests** (1 subject far end, 1 HATS near end), and **Listening-only tests** (2 HATS, far end and near end, subjects as "observers"). The right column lists seven parameters that can be assessed: **Overall quality**, **Difficulties**, **Disturbances caused by echoes**, **Disturbances caused by switching**, **Direct comparison**, **Parameter identification**, and **Data basis for comparison**. Arrows indicate the relationships: solid lines connect each test type to all seven parameters, while dashed lines connect each test type to the first four parameters. A small label **G.168(09)\_FI.3** is present in the bottom right corner.
+
+Diagram showing the structure of subjective test procedures for speech echo cancellers. It maps three test types to seven parameters. The left side shows a continuum from 'Realistic test conditions' to 'Exactly defined measurement conditions'. The middle side lists 'Conversational tests', 'Talking and listening tests', and 'Listening-only tests'. The right side lists parameters: Overall quality, Difficulties, Disturbances caused by echoes, Disturbances caused by switching, Direct comparison, Parameter identification, and Data basis for comparison. Arrows show the relationship between test types and parameters.
+
+**Figure I.3 – Structure of subjective test procedures for speech echo cancellers and a selection of parameters**
+
+*Conversational tests* play an important role in the evaluation of speech echo cancellers, since the performance of the echo canceller influences the perceived quality of the overall telephone connection. During a conversational test, subjects give their rating of the quality of the *overall* connection after a *complete* conversation, thus taking into account all of the aforementioned performance factors. Conversational tests are therefore probably the most important tests designed to evaluate the influence of speech echo cancellers on overall transmission performance.
+
+Furthermore the conversational tests are necessary to identify those parameters, which play an important role concerning the complex parameter "*overall quality*". But on the other hand, such tests are not sensitive enough to evaluate specific transmission performance characteristics. If laboratory tests shall be developed and requirements for specific transmission parameters for echo cancellers shall be fixed (residual echo level, initial convergence, NLP behaviour, etc.), other test procedures are necessary. For this purpose, *talking and listening tests* and *listening-only tests* have been developed. If these tests are properly designed, they provide a powerful and effective method to investigate the effect which specific echo canceller parameters have on overall transmission performance. The results of these tests may therefore be directly correlated to the results of objective measurements.
+
+##### 1.7.5.1.2 Parameter identification by conversational tests
+
+In 1996, conversational tests were carried out with 4 commercially available echo cancellers being at least ITU-T G.165 compliant. After the test was finished, the operators who were present in the test
+
+rooms interviewed subjects about the *overall quality rating* and the *percentage difficulty in talking or listening over the connection (% D)*. The echo path characteristics and the corresponding test results are given in Figures I.4 and I.5.
+
+In addition to these recommended questions, all subjects who answered the question about difficulties with "Yes" were additionally asked about *the kind of difficulties* they had. At the end of the interview, each subject was asked about *the most annoying aspect* during the call they just had finished. The answers are of special interest for the operators not only for the subjective tests itself but also for the evaluation of those technical parameters which cause the problems for the subscribers. This information gives an important idea about the relevance of instrumental parameters.
+
+
+
+| Echo Canceller | MOS (Mean Opinion Score) | % D (Percentage Difficulty) |
+|----------------|--------------------------|-----------------------------|
+| EC A | ~2.9 | ~72% |
+| EC B | ~3.7 | ~32% |
+| EC C | ~2.8 | ~72% |
+| EC D | ~2.8 | ~72% |
+
+Figure I.4: Bar chart showing overall quality mean opinion score (MOS) and percentage difficulty (% D) for four echo cancellers (EC A, EC B, EC C, EC D). The left Y-axis represents MOS (1 to 5) and the right Y-axis represents % D (0% to 100%). MOS is shown as grey bars, and % D is shown as black diamonds.
+
+**Figure I.4 – Results from *conversational tests*, overall quality mean opinion score (MOS) and % D (rhombus) for the 4 echo cancellers, ERL 7 dB, room noise level 40 dB(A), corresponding level –61 dBm0**
+
+A significant difference between echo canceller B and the other cancellers A, C and D could be analysed in Figure I.4. The main focus of these tests was not to compare different echo cancellers but to identify the parameters that determine the subjectively perceived quality. If the comments about the difficulties during the conversation are analysed, most of these quotations concern the following points:
+
+- Audible speech clipping during double talk (implementation of the NLP). This is especially relevant for the design of Test 3C.
+
+Instrumental measurements based on the composite source signals demonstrate that echo canceller B in Figure I.4 shows a very good double talk performance. In connection with a high echo attenuation this leads to the best rating given through Figure I.4.
+
+- Disturbances caused by echoes (initial convergence and residual echo). This is especially relevant for Tests 2A and 2B.
+
+The echo signal of EC D itself was typically characterized as "distorted" or "...like whispering". This leads to significant worse MOS values compared to echo canceller B although the double talk performance was good.
+
+
+
+| Echo Canceller | MOS (Left Axis) | % D (Right Axis) |
+|----------------|-----------------|------------------|
+| EC A | ~2.5 | ~90% |
+| EC B | ~3.8 | ~35% |
+| EC C | ~2.5 | ~80% |
+| EC D | ~3.8 | ~45% |
+
+Figure I.5: Bar chart showing overall quality MOS and % D for four echo cancellers (EC A, EC B, EC C, EC D). The left Y-axis represents MOS (1 to 5) and the right Y-axis represents % D (0% to 100%). EC A has a MOS of approximately 2.5 and % D of approximately 90%. EC B has a MOS of approximately 3.8 and % D of approximately 35%. EC C has a MOS of approximately 2.5 and % D of approximately 80%. EC D has a MOS of approximately 3.8 and % D of approximately 45%.
+
+**Figure I.5 – Results from *conversational tests*, overall quality MOS and % D (rhombus) for the 4 echo cancellers, 4-wire echo path, room noise level 50 dB(A), corresponding level –55 dBm0**
+
+The echo cancellers can be divided into two groups in Figure I.5. Both cancellers A and C are judged significantly worse than the cancellers B and D. Analysing the comments of subjects after the tests expressing their rating of percentage difficulty, it clearly points out two important aspects:
+
+- Clipping during double talk as the most annoying impairment. This is as especially relevant for the design of Test 3C.
+
+Both echo cancellers B and D with good double talk performances in connection with this kind of echo path realization are judged significantly better.
+
+- Quality of background noise transmission. There is currently no test to examine the quality of background noise transmission in this Recommendation.
+
+The modulation of background noise is audible and annoying for subjects especially if the noise disappears when they start talking and the echo canceller attenuates the send path.
+
+Conversational tests conducted by another Administration under different network conditions also pointed out the importance of the NLP performance. Significant differences between two of the echo cancellers under test appeared in these evaluations, when the signal levels were either above or below nominal. In one condition, it was concluded that the difference in performance was due to the clipping of speech in time, caused by operation of the non-linear processor and its associated control.
+
+The results of conversational tests published by two Administrations and corresponding results of specific listening-only tests under double talk conditions indicate that the occurrence of clipping and gaps is very important to subjective performance. Objective measurements, concerning the switching characteristics of the NLP, give correlated parameters. The results of the different subjective test procedures clearly indicate that the control of the NLP and the associated switching characteristic under single and double talk conditions is one of the most important parameters. This influences the quality of background noise transmission and double talk performance. In addition, the echo attenuation during initial convergence and steady state conditions (under single and double talk conditions) is important.
+
+##### I.7.5.1.3 Specific talking and listening tests
+
+In the conversational tests, complaints were given concerning the echo disturbances for some of the echo cancellers under test. This indicates the need for a specific subjective test and corresponding objective test results to fix requirements for laboratory tests. For this purpose, specific *talking and*
+
+*listening tests* were designed to evaluate talking related disturbances. Four echo cancellers were tested.
+
+One part of this test considered the initial convergence of the echo cancellers, both with enabled and disabled NLP. The results of the subjective tests and correlating objective measurements are given in Figures I.6 and I.7.
+
+
+
+| Echo Canceller | MOS |
+|----------------|-----|
+| EC A | 3.4 |
+| EC B | 4.0 |
+| EC C | 4.3 |
+| EC D | 1.5 |
+
+Bar chart showing MOS values for four echo cancellers (EC A, EC B, EC C, EC D) with NLP disabled. The y-axis is MOS (1 to 5). EC A is ~3.4, EC B is ~4.0, EC C is ~4.3, and EC D is ~1.5. The chart is labeled G.168(09)\_FI.6.
+
+**Figure I.6 – Results from *talking and listening tests*, MOS, disturbance caused by echoes, digital echo path, ERL 6 dB, no cancelled end background noise, NLP disabled**
+
+
+
+Line graph showing convergence test versus time for four echo cancellers (A, B, C, D) with NLP disabled. The y-axis is dB (-40 to 0) and the x-axis is time (0 to 5 s). A horizontal dashed line at -15 dBm0 indicates the convergence level. EC D converges to the highest level (least negative dB), while EC C converges to the lowest level (most negative dB). The chart is labeled G.168(09)\_FI.7.
+
+**Figure I.7 – Convergence test versus time, digital echo path, ERL 6 dB, no cancelled end background noise, receive level –15 dBm0, NLP disabled**
+
+If the NLP is disabled, the results are given in Figure I.6. This test characterizes the convergence of the adaptive filters. The *talking and listening tests* are sensitive enough to point out differences between the tested echo cancellers. These differences could be expected from the test subjects' comments during the conversational tests but the conversational tests were not sensitive enough for a further comparison between the tested echo cancellers. The echo signal, which is produced by EC D causes the highest annoyance. These MOS values correlate to objective test results measured for the same echo cancellers as given in Figure I.7. This is relevant for Test 2B.
+
+
+
+| Echo Canceller | MOS |
+|----------------|-----|
+| EC A | 4.2 |
+| EC B | 4.8 |
+| EC C | 4.2 |
+| EC D | 2.8 |
+
+Bar chart showing MOS values for four echo cancellers (EC A, EC B, EC C, EC D) with NLP enabled and background noise. The y-axis is MOS (1 to 5). EC A is ~4.2, EC B is ~4.8, EC C is ~4.2, and EC D is ~2.8. The chart is labeled G.168(09)\_FI.8.
+
+**Figure I.8 – Results from *talking and listening tests*, MOS, disturbance caused by echoes, digital echo path, ERL 6 dB, background noise –55 dBm0, NLP enabled**
+
+
+
+| EC | MOS |
+|------|-----|
+| EC A | 4.5 |
+| EC B | 4.5 |
+| EC C | 4.5 |
+| EC D | 2.8 |
+
+Bar chart showing MOS (Mean Opinion Score) for four echo cancellers (EC A, EC B, EC C, EC D). The y-axis ranges from 1 to 5. EC A, EC B, and EC C all have a MOS of approximately 4.5. EC D has a significantly lower MOS of approximately 2.8. The chart is labeled G.168(09)\_Fl.9.
+
+**Figure I.9 – Results from *talking and listening tests*, MOS, disturbance caused by audible switching, digital echo path, ERL 6 dB, background noise –55 dBm0, NLP enabled**
+
+Figures I.8 and I.9 give the results, if the NLP is enabled. Figure I.8 shows the ratings for the echo disturbances, if the NLP is enabled, and Figure I.9 shows the corresponding results for audible clipping. EC D obtains the worse ratings with less than 3 points for both parameters. Echoes can be heard for a longer time until they are suppressed (Figure I.8). Audible switching causes a higher annoyance compared to the other three echo cancellers EC A, EC B and EC C (Figure I.9). The switching characteristic of EC D is more annoying compared to the other echo cancellers.
+
+- Basically, several parameters cause the annoyance at the beginning of convergence: The initial convergence speed, determined as the echo attenuation vs. time is one important aspect as given through the correlated subjective and objective test results in Figures I.6 and I.7. The switching characteristics of the NLP and the echo attenuation vs. frequency influence the annoyance too. Correlated objective measurement results are given in Figure I.10. The pictures show a spectral analysis of the echo signal versus time (x-axis) and frequency (y-axis) during initial convergence for the echo cancellers which were tested subjectively (Figures I.8 and I.9). High echo signal peaks are given in light colours, dark colours represent a better echo attenuation. These measurement results are again a very good example of how subjectively obtained test results can be correlated to objective analyses. The tests clearly point out that the echo cancellers A, B and C which were judged significantly better in the talking and listening tests (Figures I.8 and I.9) attenuate and suppress the residual echo faster than echo canceller D. This is relevant for Tests 2A and 2C. There is currently no test to examine the quality of background noise transmission in this Recommendation.
+
+
+
+Spectrogram for Echo cancellers A showing residual echo spectrum over time and frequency. The x-axis represents frequency in kHz from 0 to 5, and the y-axis represents time in seconds from 0.3 to 3. The color scale indicates power levels in dB from -70 to -30.
+
+Echo cancellers A
+
+
+
+Spectrogram for Echo cancellers B showing residual echo spectrum over time and frequency. The x-axis represents frequency in kHz from 0 to 5, and the y-axis represents time in seconds from 0.3 to 3. The color scale indicates power levels in dB from -70 to -30.
+
+Echo cancellers B
+
+
+
+Spectrogram for Echo cancellers C showing residual echo spectrum over time and frequency. The x-axis represents frequency in kHz from 0 to 5, and the y-axis represents time in seconds from 0.3 to 3. The color scale indicates power levels in dB from -70 to -30.
+
+Echo cancellers C
+
+
+
+Spectrogram for Echo cancellers D showing residual echo spectrum over time and frequency. The x-axis represents frequency in kHz from 0 to 5, and the y-axis represents time in seconds from 0.3 to 3. The color scale indicates power levels in dB from -70 to -30.
+
+Echo cancellers D
+
+G.168(09)\_FI.10
+
+**Figure I.10 – Spectral analysis of residual echo during initial convergence**
+
+###### Listening-only tests
+
+A listening-only test is probably the most sensitive test method for the direct comparison of echo cancellers and for the evaluation of single transmission parameters. In addition to conversational tests and talking and listening tests, this test method was used for the evaluation of specific transmission parameters like residual echo levels, initial convergence or double talk performance.
+
+Figures I.11 and I.12 show one example how the subjective test results were used to find values for laboratory tests. The double talk performance of six echo cancellers was assessed by a group of untrained subjects (Figure I.11) and experts (Figure I.12) for an ERL of 24 dB, a receive level of $-15$ dBm0 and a double talk level of $-30$ dBm0.
+
+
+
+| Condition | MOS |
+|-----------|-----|
+| Ref. | 4.2 |
+| EC1 | 1.8 |
+| EC2 | 3.8 |
+| EC3 | 2.1 |
+| EC4 | 4.0 |
+| EC5 | 1.9 |
+| EC6 | 1.3 |
+
+Bar chart titled 'Double talk performance, untrained subjects' showing MOS values for Ref., EC1, EC2, EC3, EC4, EC5, and EC6. The y-axis is labeled 'MOS' and ranges from 1 to 5. The x-axis labels are Ref., EC1, EC2, EC3, EC4, EC5, and EC6. The chart includes a small label 'G.168(09)\_FI.11' in the bottom right corner.
+
+**Figure I.11 – Results from listening-only tests, untrained subjects, double talk performance MOS, ERL 24 dB, receive level –15 dBm0, double talk level –30 dBm0**
+
+
+
+| Condition | MOS |
+|-----------|-----|
+| Ref. | 4.8 |
+| EC1 | 2.2 |
+| EC2 | 4.5 |
+| EC3 | 2.5 |
+| EC4 | 4.8 |
+| EC5 | 2.5 |
+| EC6 | 2.0 |
+
+Bar chart titled 'Disturbance caused by speech gaps, expert listeners' showing MOS values for Ref., EC1, EC2, EC3, EC4, EC5, and EC6. The y-axis is labeled 'MOS' and ranges from 1 to 5. The x-axis labels are Ref., EC1, EC2, EC3, EC4, EC5, and EC6. The chart includes a small label 'G.168(09)\_FI.12' in the bottom right corner.
+
+**Figure I.12 – Results from listening-only tests, experts, disturbances during double talk caused by speech gaps MOS, ERL 24 dB, receive level –15 dBm0, double talk level –30 dBm0**
+
+Although the double talk signal level is very weak, the two echo cancellers EC2 and EC4 reach comparable MOS values like the undisturbed reference in Figure I.11. The untrained subjects assessed the parameter "double talk performance". This demonstrates the sensitivity of listening-only tests and indicates that even under these conditions a good transmission quality can be expected for echo cancellers. The other four speech echo cancellers are judged significantly worse. The ratings of the experts group for the disturbances caused by speech gaps (given in Figure I.12) show the same order of preference of the echo cancellers. This result again correlates to the conversational test result and the corresponding comments. It demonstrates that the annoyance caused by speech gaps seems to be the most important parameter.
+
+Objective tests and test signals could be adapted to measure the correlated parameters. The tests pointed out that the degradation of a transmitted double talk signal is mainly determined by the insertion of the NLP during continuous speech. The correlated parameter is the switching characteristic of the NLP and its control during double talk. This is especially relevant for the design of Test 3C.
+
+#### **I.7.5.2 Subjective tests with the purpose of qualifying those effects of the echo cancellation process that cannot be captured by objective measurements**
+
+Subjective tests were performed with the purpose of qualifying those effects of the echo cancellation process that cannot be captured by objective measurements.
+
+The results of the tests, judged by untrained and trained listeners, pointed out that one degradation of a transmitted double talk signal is mainly determined by the insertion of the NLP during continuous speech if the echo cancellers are fully converged. If CSS is used for the objective measurements, the switching characteristics can easily be determined after a burst of the double talk signal, because the time duration of all components is exactly defined for CSS. Subjective tests pointed out that a good double talk performance can be achieved even with double talk signal levels 15 dB lower than the receive input signal levels. If the bursts of the double talk CSS are not completely transmitted, the probability is high that longer speech gaps occur.
+
+# Appendix II
+
+## Measurement methods for characteristics of echo paths
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## II.1 Introduction
+
+Knowledge of an echo path is necessary in order to control voice echo efficiently in telecommunication systems. Two of the main characteristics of an echo path are the dispersion time and frequency response. This appendix summarizes the measurement techniques used to obtain the echo-path impulse responses in telephone networks. It also provides analysis results for the echo paths measured in real networks.
+
+This appendix is organized as follows. Clause II.2 gives details on the existing measurement procedures. The generation of echo-path characteristics is explained in clause II.3. Clause II.4 contains examples of the characteristics of echo paths measured in real networks. Finally, clause II.5 presents the conclusions.
+
+This appendix does not include any reference to echo return loss (ERL) measurements. This is because this Recommendation specifies that all echo cancellers should operate and meet the requirements of all the tests with an $ERL \geq 6$ dB.
+
+More information on the characteristics of echo paths may be found on the ITU-T website.
+
+## II.2 Measurement procedure
+
+Figure II.1 shows a typical call configuration where $x(k)$ and $y(k)$ are, respectively, the signals to and from the cancelled end. Because of the impedance mismatch in the hybrid that connects the 2-wire and 4-wire circuits, part of the signal from the non-cancelled end will leak through the hybrid and propagate back to the talker to form an echo. If the user in the cancelled end is not talking, $y(k)$ will be the echo signal. Therefore measurement of the signals $x(k)$ and $y(k)$ is performed to obtain the echo-path characteristics.
+
+**NOTE** – The existence of level control devices, e.g., ALC (automatic level control), HLC (high level compensation), amplifiers, or attenuators along the path from the hybrid to the measurement device, can affect the measured ERL values.
+
+
+
+```
+
+graph LR
+ subgraph "Non-cancelled end (4-wire)"
+ A(( ))
+ end
+ subgraph "Cancelled end (2-wire)"
+ B{ }
+ end
+ H[Hybrid/Echo Path]
+
+ X(( )) -- x(k) --> H
+ H --> B
+ B -. Echo Path .-> H
+ H -- y(k) --> A
+
+```
+
+The diagram illustrates a typical call connection for echo path measurement. On the left, a 'Non-cancelled end' is represented by a 4-wire interface (a circle). A signal $x(k)$ is shown entering the system from the top, passing through a rectangular block (representing a hybrid or echo canceller), and then entering the 4-wire interface. From the 4-wire interface, the signal $y(k)$ is shown returning through the rectangular block. On the right, a 'Cancelled end' is represented by a 2-wire interface (a diamond shape). A dashed curved arrow indicates the echo path from the 4-wire interface, through the rectangular block, to the 2-wire interface, and back. The signal $y(k)$ is also shown exiting the 2-wire interface. The diagram is labeled 'G.168(09)\_FII.1' in the bottom right corner.
+
+Diagram of a typical call connection showing signal flow between a 4-wire non-cancelled end and a 2-wire cancelled end via a hybrid.
+
+**Figure II.1 – A typical call connection**
+
+### II.2.1 Measurement set-up
+
+#### II.2.1.1 Intrusive measurement set-up
+
+
+
+The diagram illustrates an intrusive measurement configuration. On the left, a rectangular block labeled 'Measurement device' is connected via dashed lines to another rectangular block labeled 'E1/T1'. From the right side of the 'E1/T1' block, two signal paths emerge. The top path is labeled '4-wire' and carries signal $x(n)$ . The bottom path carries signal $y(n)$ . These paths lead to a diamond-shaped hybrid symbol which transitions to a '2-wire' line on the right. A curved dashed arrow labeled 'Echo path' indicates signal reflection from the $x(n)$ path back to the $y(n)$ path. The diagram is identified by the code G.168(09)\_FII.2.
+
+Block diagram of intrusive measurement set-up (Figure II.2).
+
+**Figure II.2 – Block diagram of intrusive measurement set-up**
+
+Figure II.2 is the block diagram of the intrusive measurement set-up. The measurement device generates the test signal and performs the signal recording. The equipment uses a 4-wire connection for sending and receiving signals.
+
+When a T1/E1 interface is not available, the test signal could be generated at a 2-wire point. In any case, the signals (transmit and receive) should be measured at the 4-wire digital point where the signals are well defined (in terms of level).
+
+During measurement, the equipment first dials a telephone number. It then sends out the test signal after the call is established. The test signal goes through the T1/E1 interface, the central office (CO) and the PSTN to a distant user. Part of the transmitted signal is reflected back in the form of an echo. Both the transmitted signal and the returned echo are recorded in the equipment using a synchronous recorder. The two recorded signals are the $R_{in}$ and $S_{in}$ signals for an echo canceller.
+
+NOTE – It must be ensured that neither an echo canceller nor an echo suppressor is present in the connection.
+
+#### II.2.1.2 Non-intrusive measurement set-up
+
+
+
+The diagram shows a non-intrusive measurement configuration. A rectangular block labeled 'Measurement device' is positioned at the top, with dashed lines tapping into the signal paths of an 'E1' block below it. Similar to Figure II.2, the 'E1' block connects to a '4-wire' path with signal $x(n)$ and a return path with signal $y(n)$ . These paths connect to a diamond-shaped hybrid symbol which leads to a '2-wire' line. A curved dashed arrow labeled 'Echo path' shows the reflection from the $x(n)$ path to the $y(n)$ path. The diagram is identified by the code G.168(09)\_FII.3.
+
+Block diagram of non-intrusive measurement set-up (Figure II.3).
+
+**Figure II.3 – Block diagram of non-intrusive measurement set-up**
+
+Figure II.3 is the block diagram of the non-intrusive measurement set-up based on the use of an "In-service non-intrusive measurement device" (see [b-ITU-T P.561] for complete information). Prior to any measurements, it must be ensured that no echo canceller or echo suppressor is present in the connection. The measurement device monitors the source signal $x(n)$ and echo signal $y(n)$ at the T1/E1 interface.
+
+### II.2.2 Computation of the echo path impulse response
+
+Computation of the echo path impulse response requires the perfect knowledge of the transmit and receive test signals. Three methods based on three different test signals are described herein.
+
+#### II.2.2.1 Method 1: LS/LMS algorithms based on white noise injection
+
+The test signal used is shown in Figure II.4. It consists of three segments. The first segment is a 2100 Hz tone with phase reversal. The purpose of the tone is to disable all the echo cancellers and echo suppressors in the link during measurement. The duration of the tone is set to $T_1 = 1.35$ s. The amplitude of the tone is $-12$ dBm0. The second segment is a pause. Its purpose is to obtain the background noise characteristics in the returned echo signal. Since a tone-disabled echo canceller, as specified in clause 7 and [ITU-T G.164] and [ITU-T G.165], will enable itself within $250$ ms $\pm 150$ ms when the signal level is below $-39$ dBm0, the duration of the pause is set to $T_2 = 80$ ms. The third segment is a White Gaussian Noise signal which is used to identify the echo-path impulse response. The power level of the white noise signal is $-18$ dBm0 and its duration is $T_3 = 5$ s.
+
+
+
+The figure illustrates a test signal waveform over time. It is divided into three distinct segments by vertical dashed lines. Segment 1, labeled 'Disabling tone' and 'Segment 1', has a duration of $T_1$ and is represented by a solid black rectangular block. Segment 2, labeled 'Pause' and 'Segment 2', has a duration of $T_2$ and is represented by a thin horizontal line. Segment 3, labeled 'White noise signal' and 'Segment 3', has a duration of $T_3$ and is represented by a noisy black rectangular block. Below the waveform, horizontal double-headed arrows indicate the durations $T_1$ , $T_2$ , and $T_3$ for each segment respectively. The text 'G.168(09)\_FII.4' is visible in the bottom right corner of the diagram area.
+
+Figure II.4: Test signal for echo-path measurement. The diagram shows a signal waveform divided into three segments: Segment 1 (Disabling tone) with duration T1, Segment 2 (Pause) with duration T2, and Segment 3 (White noise signal) with duration T3. The signal is represented by a horizontal line with a black rectangular block for the tone and a noisy block for the white noise signal.
+
+Figure II.4 – Test signal for echo-path measurement
+
+##### Computation of impulse response
+
+The echo signal can be modelled as:
+
+$$y(n) = x(n) * h^o(n) + v(n) = \sum_{i=0}^{N-1} h^o(i)x(n-i) + v(n), \quad n = 0, 1, 2, \dots, L-1$$
+
+where $N$ is the length of the echo-path impulse response and $L$ is the total number of data samples available. Define vectors:
+
+$$\mathbf{h}^o = [h^o(0), h^o(1), \dots, h^o(N-1)]^T$$
+
+and:
+
+$$\mathbf{x}(n) = [x(n), x(n-1), \dots, x(n-N+1)]^T$$
+
+In vector notation,
+
+$$y(n) = \mathbf{x}(n)^T \mathbf{h}^o + v(n), \quad n = 0, 1, 2, \dots, L-1$$
+
+The estimation problem can be stated as follows: Given $L$ samples of $x(n)$ and $y(n)$ , compute the echo-path impulse response $\mathbf{h}^0$ . This is a standard system identification problem which can be solved by two common approaches. One is the least-squares (LS) method and the other is the iterative method using the normalized least-mean square (NLMS) algorithm. The first method yields a good solution with short data record. However, it is more computationally intensive than the second method. In most cases, provided that the data length $L$ is large enough, the final solutions from both methods are very close and the difference is insignificant.
+
+##### LS method
+
+Define error signal:
+
+$$e(n) = y(n) - \mathbf{h}^T \mathbf{x}(n)$$
+
+where $\mathbf{h}$ is the echo-path impulse response estimate. The LS method minimizes:
+
+$$J = \sum_{n=0}^{L-1} e(n)^2$$
+
+to determine $\mathbf{h}$ . The corresponding solution can be shown to be:
+
+$$\mathbf{h} = \mathbf{R}^{-1} \mathbf{p}$$
+
+where:
+
+$$\mathbf{R} = \sum_{n=0}^{L-1} \mathbf{x}(n) \mathbf{x}(n)^T$$
+
+$$\mathbf{p} = \sum_{n=0}^{L-1} y(n) \mathbf{x}(n)$$
+
+##### NLMS method
+
+The NLMS method finds $\mathbf{h}$ iteratively using the following equations:
+
+$$e(n) = y(n) - \mathbf{h}(n)^T \mathbf{x}(n)$$
+
+$$\mathbf{h}(n+1) = \mathbf{h}(n) + \frac{\mu}{\delta + \mathbf{x}(n)^T \mathbf{x}(n)} e(n) \mathbf{x}(n)$$
+
+where $\mathbf{h}(n)$ denotes the echo-path estimate at time $n$ , $\delta$ is a small positive number and $\mu$ is a positive constant called step-size. The step-size must be less than two to allow convergence.
+
+#### II.2.2.2 Method 2: Hadamard transform based on MLS sequence injection
+
+The test signal consists in the use of MLS (maximal length sequence) (binary sequence which instantaneous normalized value is $\pm 1$ , periodical of period $L$ ). The test signal is therefore a pseudo-random signal which has statistical properties close to white noise. Its autocorrelation function is circular and can be expressed as:
+
+$$C_{xx}(n) = \frac{1}{L} \sum_{m=0}^{L-1} x(m-n)x(m) = \begin{cases} \frac{1}{L} & \text{if } n \equiv 0 \pmod{L} \\ -\frac{1}{L} & \text{otherwise} \end{cases}$$
+
+Defining the function $\delta^L(n)$ by:
+
+$$\delta^L(n) = \begin{cases} 1 & \text{if } n \equiv 0 \text{ modulo } L \\ 0 & \text{otherwise,} \end{cases}$$
+
+the autocorrelation function can be rewritten as:
+
+$$C_{xx}(n) = \left(1 + \frac{1}{L}\right)\delta^L(n) - \frac{1}{L}$$
+
+##### Computation of impulse response
+
+The echo signal can be modelled as: $y(n) = h * x(n)$ when the circuit noise is ignored. If we assume that the signal $x(n)$ is a white noise, the impulse response $h$ is given by the cross-correlation function of signals $y(n)$ and $x(n)$ :
+
+$$C_{xy}(n) = C_{xx}(n) * h$$
+
+In case of a MLS sequence as described above, this equation is expressed equivalently as:
+
+$$C_{xy}^L(n) = \frac{1}{L} \sum_{m=0}^{m=L-1} x(m-n)y(m) = \left(1 + \frac{1}{L}\right)\delta^L(n) * h - \frac{1}{L}\bar{h}$$
+
+where $\bar{h} = \sum_{m=0}^{L-1} h(m)$ is the DC offset. The resulting estimate of the echo path impulse response is then given by:
+
+$$h(n) = \frac{L}{L+1} [C_{xy}^L(n) + \bar{C}_{xy}^L], n = 0, \dots, L-1$$
+
+where $\bar{C}_{xy}^L = \sum_{m=0}^{L-1} C_{xy}^L(m) = \bar{h}/L$ . In fact, the term $\bar{C}_{xy}^L$ may be ignored since the measured impulse response has zero mean in principle and/or the length of the sequence $L$ is chosen to be large. In practice, it is recommended that the length of the sequence is at least $2^{14}$ samples, since this will ensure good white noise-like properties. Then, this equation shows that the measured impulse response $h(n)$ may be directly approximated by the cross-correlation function $C_{xy}^L(n)$ , for $n=0, \dots, L-1$ . Since $x(n)$ is a pseudo-random noise having normalized values $\pm 1$ , computing the cross-correlation function is easily performed by the Hadamard transform (see [b-Borish]).
+
+#### II.2.2.3 Method 3: FFT algorithm based on periodic noise injection
+
+The test signal consists of a periodic sequence having unit magnitude at discrete frequency points. It is defined using a superposition of sinusoidal signals having increasing frequencies, constant magnitudes and random phases:
+
+$$x(n) = \frac{1 + (-1)^n}{N} + \frac{2}{N} \sum_{k=1}^{\frac{N}{2}-1} \cos\left(\frac{2\pi kn}{N} + \Phi_k\right), n = 0, \dots, N-1$$
+
+where $\Phi_k$ are independent, identically distributed random variables having uniform distribution between 0 and $2\pi$ . The period of the test signal $x(n)$ , $N$ , is selected to be larger than the expected echo path pure delay ( $t_r$ , expressed in samples) and controls the frequency resolution of the test signal. Depending on the noise level affecting the receive signal $y(n)$ , an appropriate number of frames, $M$ , is selected for periodically transmitting $x(n)$ . In this way, the overall test signal will have duration of
+
+$M \times N$ samples. At the echo path receiving end, $M$ received frames of $y(n)$ are averaged to generate $\bar{y}(n), n = 0, \dots, N-1$ , so that the estimated echo path impulse response is then given by:
+
+$$h(n) = IFFT[FFT[\bar{y}(n)] \cdot FFT[x(n)]^*]$$
+
+During the injection of the test signal, the existing echo canceller connected to the echo path must be disabled.
+
+## II.3 Analysis of echo-path characteristics
+
+This clause describes methods of echo-path impulse response analysis. The echo-path characteristics considered are dispersion width and magnitude response of echo paths.
+
+Before the analysis of echo-path characteristics, the measured echo-path impulse responses should be post-processed by a bandpass filter which covers the same frequency region as a speech signal. The passband of the filter is from 200 Hz to 3600 Hz, the same frequency range as that of the CS signal specified in clause C.3.1.
+
+### II.3.1 Dispersion time
+
+The echo-path impulse response is not a single impulse. It has a finite duration which we shall refer to as dispersion time. The dispersion time is a factor to determine the length of the H register in an echo canceller. A region where the echo reflection occurs is first located from an impulse response measurement. The duration for this region should be long enough to cover the entire echo reflection. For example, in the North American measurements, it was set to 30 ms. This corresponds to 240 samples at 8 kHz sampling rate. The impulse response in this range is denoted as $h(n), n = 0, 1, \dots, M$ , where $M = 239$ . If we truncate $h(n)$ by keeping the impulse response values from $n = N_1$ to $N_2$ , then the relative square-error due to truncation is:
+
+$$ERR = 1 - \frac{\sum_{n=N_1}^{N_2} h(n)^2}{\sum_{n=0}^M h(n)^2}$$
+
+Figure II.5 shows such a possible truncation. According to Figure 11, we need the largest amount of echo reduction at 0 dBm0 $L_{Rin}$ . With 6 dB ERL, this translates to $30 - 6 = 24$ dB ERLE provided by an echo canceller. Hence the dispersion time is considered to be the shortest length $N_2 - N_1 + 1$ such that the $ERR$ is less than $-24$ dB.
+
+Note that the method suggested here to compute the dispersion time is for the worst-case scenario. This is because a 6 dB ERL is assumed to compute the $ERR$ threshold. In practice, the ERL is much higher. The dispersion time is shorter when ERL increases.
+
+
+
+G.168(09)\_FII.5
+
+Figure II.5: A graph showing the echo-path impulse response h(n) versus n. The curve starts at N1 and ends at N2, with a peak amplitude around N1. The curve is labeled h(n) on the vertical axis and n on the horizontal axis. The truncation points N1 and N2 are marked with vertical dashed lines.
+
+**Figure II.5 – Echo-path truncation for dispersion time estimate**
+
+### II.3.2 Magnitude response of echo path
+
+While the echo-path impulse responses can be quite different in shape, the frequency domain characteristics of the echo paths are expected to have some similarity. The magnitude response characteristics of echo path can be generated by taking the average of the magnitude of the Fourier transform of each echo-path measurement.
+
+## II.4 Examples of echo path measurements from real networks
+
+### II.4.1 Echo-path characteristics from measurements in North America
+
+During the period from June 1998 to April 1999, 101 long-distance calls were made from Montreal to the following Provinces and States across North America: Arizona, British Columbia, California, Louisiana, Manitoba, Massachusetts, Michigan, Minnesota, Missouri, Nevada, New York, North Carolina, Ontario, Quebec, Saskatchewan, Texas and Wisconsin. The measurements were made using the set-up as shown in Figure II.2. The send-out and returned signals were recorded in each call and the echo-path impulse responses were computed using the method described in clause II.2.2.1. This clause reports the echo-path characteristics generated from the above echo-path measurements.
+
+#### II.4.1.1 Dispersion time
+
+Figure II.6 is the histogram of the echo-path dispersion time. The largest percentage of dispersion time was between 5-7 ms. Only two calls had dispersion time between 11-12 ms. There was no call with dispersion time over 12 ms.
+
+
+
+Histogram of dispersion time from 88 long-distance calls
+
+| Dispersion time (ms) | Number of calls |
+|----------------------|-----------------|
+| 3 - 4 | 19 |
+| 4 - 5 | 10 |
+| 5 - 6 | 21 |
+| 6 - 7 | 16 |
+| 7 - 8 | 11 |
+| 8 - 9 | 6 |
+| 9 - 10 | 1 |
+| 10 - 11 | 2 |
+| 11 - 12 | 2 |
+
+G.168(09)\_FII.6
+
+Histogram of dispersion time from 88 long-distance calls. The x-axis is 'Dispersion time (ms)' ranging from 2 to 13. The y-axis is 'Number of calls' ranging from 0 to 25. The histogram shows a distribution with peaks around 3.5 ms and 5.5 ms.
+
+**Figure II.6 – Histogram of dispersion time for long-distance calls:
+Mean = 6.02 ms, StD = 2.26 ms**
+
+#### II.4.1.2 Magnitude response of echo path
+
+Figure II.7 is the average of the magnitude spectra of the measured echo-path impulse responses. The impulse responses were normalized to have unit energy before the spectra were computed. The solid line is the mean and the two dotted lines represent the one standard deviation region. It appears that the variance of magnitude spectra is not large. This indicates that there is a high consistency among the magnitude responses in the echo-paths. The averaged magnitude spectrum has a small peak around 250 Hz. In addition, the magnitude responses are relatively flat.
+
+The results are consistent with the study in the article "Echo Performance of Toll Telephone Connections in the United States," by F.P. Duffy, G.K. McNees, I. Nasell, and T.W. Thatcher, Jr., in Bell System Technical Journal, 1974.
+
+
+
+Spectral means and deviations from 88 long-distance calls
+
+Figure II.7: Magnitude spectra of echo paths for long-distance calls. The graph shows Magnitude (dB) on the y-axis (from -80 to -30) versus Frequency (Hz) on the x-axis (from 0 to 4000). A solid line represents the mean spectrum, which peaks at approximately -36 dB at 400 Hz, dips to -40 dB at 1600 Hz, and then rises to -38 dB at 3200 Hz. Two dashed lines represent the upper and lower bounds of the deviations. The upper dashed line peaks at -32 dB at 400 Hz and stays around -35 dB until 3200 Hz. The lower dashed line peaks at -43 dB at 400 Hz and stays around -42 dB until 3200 Hz. Both lines drop sharply after 3600 Hz. A label 'G.168(09)\_FII.7' is in the bottom right corner.
+
+**Figure II.7 – Magnitude spectra of echo paths for long-distance calls,
+echo paths normalized to have unity energy**
+
+#### II.4.1.3 Multiple reflections
+
+We have observed 6 double reflections from the 101 long-distance calls. However, the total dispersion times of these double reflections were all limited to 10 ms. In other words, the two reflectors in each of these cases were closely located.
+
+The number of reflections did not exceed two in the measurements.
+
+### II.4.2 Echo path characteristics from measurements in Europe
+
+Measurements were made in the telephone networks in France using the set-up described in clause II.2.1. There are three types of echo path impulse responses. The impulse and frequency responses of these three types of echo paths are shown in Figures II.8 to II.10. They have equivalent characteristics of echo path models $m_1(k)$ , $m_5(k)$ and $m_6(k)$ of Annex D.
+
+
+
+The figure consists of two vertically stacked plots. The top plot shows the impulse response $g_1(k)$ versus Sample number. The y-axis ranges from -0.1 to 0.2, and the x-axis ranges from 0 to 150. The response shows a sharp peak around sample 25, followed by a decaying oscillation that settles near zero after sample 50. The bottom plot shows the magnitude response $20 \cdot \log(\text{Mag. response})$ versus Frequency (Hz). The y-axis ranges from -100 to 0, and the x-axis ranges from 0 to 4000. The response is relatively flat between 500 Hz and 3000 Hz, with a sharp roll-off above 3500 Hz and a sharp roll-off below 500 Hz. A label 'G.168(09)\_FII.8' is visible in the bottom right corner of the magnitude response plot.
+
+Two plots showing the echo path impulse response g1(k) and its magnitude response 20\*log(Mag. response) versus frequency (Hz).
+
+**Figure II.8 – Echo path impulse response $g_1$ , an ERL of 12 dB was used in the magnitude response plot**
+
+
+
+The figure consists of two vertically stacked plots. The top plot shows the impulse response $g_2(k)$ versus Sample number. The y-axis ranges from -0.1 to 0.2, with grid lines at -0.1, 0, 0.1, and 0.2. The x-axis ranges from 0 to 150, with labels at 50, 100, and 150. The response shows a sharp peak around sample 25, followed by a decaying oscillation that settles near zero after sample 50. The bottom plot shows the magnitude response $20 \cdot \log(\text{Mag. response})$ versus Frequency (Hz). The y-axis ranges from -100 to 0 in increments of 20. The x-axis ranges from 0 to 4000 Hz in increments of 500. The magnitude response is relatively flat at approximately -12 dB between 500 Hz and 3500 Hz, with a peak around 200 Hz and a sharp roll-off above 3500 Hz, showing significant ripple in the stopband. A label 'G.168(09)\_FII.9' is visible in the bottom right corner of the magnitude response plot.
+
+Two plots showing the echo path impulse response g2(k) and its magnitude response 20\*log(Mag. response) versus frequency (Hz).
+
+**Figure II.9 – Echo path impulse response $g_2$ , an ERL of 12 dB was used in the magnitude response plot**
+
+
+
+The figure consists of two vertically stacked plots. The top plot shows the impulse response $g_3(k)$ on the y-axis (ranging from -0.1 to 0.2) against Sample on the x-axis (ranging from 0 to 150). A sharp positive peak is visible at approximately sample 25, followed by smaller oscillations that decay towards zero. The bottom plot shows the magnitude response $20 \cdot \log(\text{Mag. response})$ on the y-axis (ranging from -100 to 0) against Frequency in Hz on the x-axis (ranging from 0 to 4000). The response is relatively flat between 500 Hz and 3000 Hz at approximately -10 dB, with a sharp roll-off starting around 3500 Hz and significant oscillations below 500 Hz and above 3500 Hz. A small label 'G.168(09)\_FII.10' is present in the bottom right corner of the magnitude response plot.
+
+Figure II.10: Echo path impulse response g3 and its magnitude response plot. The top plot shows the impulse response g3(k) versus Sample (0 to 150), with a sharp peak around sample 25. The bottom plot shows the magnitude response 20\*log(Mag. response) versus Freq. (Hz) (0 to 4000), with a flat response around -10 dB and a sharp drop-off above 3500 Hz.
+
+**Figure II.10 – Echo path impulse response $g_3$ , an ERL of 12 dB was used in the magnitude response plot**
+
+## II.5 Conclusions
+
+This appendix summarized the measurement procedures together with the computation of echo-path impulse response and its characteristics. Also included are the results from a number of echo paths measured in North America and Europe. The results can serve as references in designing a digital echo path for the testing of echo cancellers in this Recommendation. Specifically, the following important properties of echo paths are observed:
+
+- The dispersion time of an echo path is within 12 ms.
+- The magnitude response of most echo paths is relatively flat, with a small peak around 250 Hz.
+- On some occasions double reflections may occur. Three or more reflections, however, rarely occur.
+
+# Appendix III
+
+## Multiple tail circuits
+
+(This appendix does not form an integral part of this Recommendation.)
+
+In modern networks, it may be the case that a two-party call is modified after the call is initially set up, so that one or more additional parties can participate in the conversation, as illustrated in Figure III.1.
+
+
+
+The diagram illustrates a network configuration for a bridged telephone call. On the left, an 'Originating telephone set' is connected via a 'Long-haul connection' to a 'PSTN' cloud. This cloud connects to an 'Echo canceller', which in turn connects to the '1st PBX (H)'. The '1st PBX (H)' is connected to the '1st destination telephone set' and also to another 'PSTN' cloud. This second 'PSTN' cloud connects to the '2nd PBX (H)', which is connected to the '2nd Destination telephone set'. The '2nd PBX (H)' is also connected to a third 'PSTN' cloud, which connects to the '3rd PBX (H)', which is connected to the '3rd destination telephone set'. A '1st bridged connection' is shown between the '1st PBX (H)' and the '1st destination telephone set'. Three echo paths are indicated by dashed lines: 'Echo path 1' from the Echo canceller to the 1st PBX, 'Echo path 2' from the Echo canceller to the 2nd PBX, and 'Echo path 3' from the Echo canceller to the 3rd PBX. A legend at the bottom left shows a circle with an 'H' labeled 'Hybrid'. The diagram is labeled 'G.168(09)\_FIII.1' at the bottom right.
+
+Diagram illustrating multiple tail circuits in a typical bridged telephone call. The diagram shows an originating telephone set connected via a long-haul connection to a PSTN cloud, which is then connected to an Echo canceller. The Echo canceller is connected to the 1st PBX (H). The 1st PBX is connected to the 1st destination telephone set and also to a PSTN cloud. This PSTN cloud is connected to the 2nd PBX (H), which is connected to the 2nd Destination telephone set. The 2nd PBX is also connected to a PSTN cloud, which is connected to the 3rd PBX (H), which is connected to the 3rd destination telephone set. The 1st PBX is also connected to the 1st destination telephone set via a 1st bridged connection. The diagram illustrates three echo paths: Echo path 1 (from the Echo canceller to the 1st PBX), Echo path 2 (from the Echo canceller to the 2nd PBX), and Echo path 3 (from the Echo canceller to the 3rd PBX). A legend indicates that (H) represents a Hybrid.
+
+**Figure III.1 – Multiple tails in a typical bridged telephone call**
+
+In Figure III.1, the originating telephone set initiates a call to the 1st destination set. The echo canceller sees the hybrid associated with the 1st PBX, illustrated as echo path 1. The recipient at the 1st PBX then bridges in a 2nd destination set by using the bridging function found on all modern PBXs. The echo canceller now sees the second hybrid, appended to the first, and delayed in time by the network delay between PBX 1 and 2. This is illustrated as echo path 2. The second destination may well bridge in a third destination, adding another hybrid tail associated with the hybrid in the 3rd PBX, and delayed by the sum of the network delay between PBX 1 and 2, and PBX 2 and 3. This is illustrated as echo path 3.
+
+PBXs may not have any echo cancellation built into them, even though they perform this bridging function. This requires that the network echo canceller be able to support multiple tails up to the echo tail capacity of the canceller.
+
+Network operators and administrators should take this into account when testing echo cancellers for use in their network.
+
+# Appendix IV
+
+## Guidelines on the use of parameters for testing echo cancellers
+
+(This appendix does not form an integral part of this Recommendation.)
+
+The tests in this Recommendation have many parameters which are specified as ranges. To provide some guidelines on a set of test conditions which should be considered at a minimum, the following is suggested. It is strongly cautioned that these values do not imply a sufficient set for compliance to this Recommendation, which is left for the discretion of the telecommunication providers. Also, it should be noted that all possible combinations of these parameters listed below would be time consuming.
+
+- 1) *Echo path delay*
+ - a) $\Delta$ – dispersion of $g(k)$ – 4.
+ - b) $\Delta/2$ – 4.
+ - c) $\Delta/10$ .
+- 2) *Echo return loss*
+ - a) 6 dB.
+ - b) 15 dB.
+ - c) 30 dB.
+- 3) *Receive-in level ( $L_{Rin}$ )*
+ - a) Maximum specified input level for the particular test.
+ - b) –10 dBm0.
+ - c) –20 dBm0.
+ - d) Minimum specified input level for the particular test.
+- 4) *Initial condition of H Register*
+ - a) H register reset.
+ - b) H register converged to an open echo path.
+ - c) H register converged to some $g(k)$ .
+
+# **Appendix V**
+
+## **List of low speed modems for optional use with Test No. 14**
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This appendix contains a comprehensive list of low speed modems that may optionally be used in Test No. 14. The list has been compiled by operators in different countries and is meant to augment the minimum set that is required to demonstrate ITU-T G.168 compliance given in Test No. 14.
+
+**Table V.1 – List of low speed modems for optional use with Test No. 14**
+
+| Application | Modulation type | Data rate (bits/s) | Answer tone | Performance criteria | Minimum volume of data | Comments |
+|------------------------|-------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Dial-up data | ITU-T V.21 ITU-T V.22 ITU-T V.22 bis ITU-T V.32 ITU-T V.32 bis | ITU-T V.21: 300 ITU-T V.22: 1200 ITU-T V.22 bis : 1200 and 2400 ITU-T V.32: 4800 and 9600 ITU-T V.32 bis : 4800 to 14400 | ITU-T V.21, ITU-T V.22 and ITU-T V.22 bis : ANS ITU-T V.32 and ITU-T V.32 bis : ANS and /ANS | BER | ITU-T V.21: 20 kbits ITU-T V.22 and ITU-T V.22 bis : 100 kbits ITU-T V.32 and ITU-T V.32 bis : 1 Mbits | ITU-T V.32 and ITU-T V.32 bis are generally used with /ANS but can be used with ANS with the internal echo canceller switched off for double satellite hops where the internal echo canceller does not have sufficient tail capacity. Used for text telephony in conjunction with ITU-T V.61. |
+| Point of sale terminal | ITU-T V.21 ITU-T V.22 ITU-T V.22 bis ITU-T V.23 Bell 103 Bell 212A | ITU-T V.21 and Bell 103: 300 ITU-T V.22 bis : 2400 ITU-T V.22 and Bell 212A: 1200 ITU-T V.23: 75, 600 and 1200 | Proprietary | BER | ITU-T V.23 (75): 1 kbits ITU-T V.21, Bell 103 and ITU-T V.23 (600/1200): 20 kbits ITU-T V.22, ITU-T V.22 bis and Bell 212A: 100 kbits | |
+| Telemetry | ITU-T V.23 | 600 and 1200 | ANS (optional) | BER | 20 kbits | |
+| Text telephone | ITU-T V.21 half duplex low channel ("EDT") ITU-T V.21 full duplex TIA 825A (Baudot) ITU-T V.23 ITU-T V.18 DTMF | ITU-T V.18: 300 bit/s ITU-T V.21: 110 half duplex low channel ("EDT") ITU-T V.21: 300 full duplex TIA 825A: 45.45 and 50 ITU-T V.23: 1200/75 DTMF rate n/a | ITU-T V.18, ITU-T V.21 and ITU-T V.23: ANS (optional) DTMF and TIA 825A: None | Character error rate | ITU-T V.18, ITU-T V.21, ITU-T V.23 and TIA 825A: 1000 characters DTMF: 300 characteristics | |
+
+**Table V.1 – List of low speed modems for optional use with Test No. 14**
+
+| Application | Modulation type | Data rate (bits/s) | Answer tone | Performance criteria | Minimum volume of data | Comments |
+|--------------------------|--------------------------|----------------------------------------------------|-------------------------|----------------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Security/Alarm system | SIA DC-02 SIA DC-05 | Pulse and DTMF: 10 to 33 pulses/s Bell 103: 300 | Various handshake tones | Character error rate | 300 characters | The SIA standards specify a number of different pulse, DTMF and FSK formats for use by security/alarm systems. In addition, SIA DC-03 specifies a standard protocol for use with Bell 103 systems. |
+| Leased line dial back-up | Bell 208 A/B Bell 202 | Bell 202: 1200 Bell 208 A/B: 4800 | Unknown | BER | 100 kbits | |
+
+Legend:
+ANS 2100 Hz Answer Tone as defined in [ITU-T V.25]
+/ANS 2100 Hz Answer Tone with phase reversals as defined in [ITU-T V.25]
+BER Bit Error Rate
+NOTE 1 – Where possible, synchronous testing should be performed, since this more accurately detects bit errors due to transmission problems. The exceptions to this are ITU-T V.21 and Bell 103, which are usually tested in asynchronous mode. In general, error correction should be switched off.
+NOTE 2 – Point of sale modems may use standard and proprietary versions of modulations.
+NOTE 3 – Security and Alarm system modems may use standard and proprietary versions of modulations.
+NOTE 4 – SIA DC-02 Security Industry Association (SIA) General Protocols – Available from [www.siaonline.org](http://www.siaonline.org).
+NOTE 5 – SIA DC-03 Security Industry Association (SIA) SIA Format – Available from [www.siaonline.org](http://www.siaonline.org).
+NOTE 6 – SIA DC-05 Security Industry Association (SIA) Ademco Contact ID Standard – Available from [www.siaonline.org](http://www.siaonline.org).
+NOTE 7 – ITU-T V.18 is an automoding procedure using ITU-T V.8 and all other textphone modulations. ITU-T V.8 uses ITU-T V.21 300 bits/s one channel at a time both before and after ANSam. Full information is found in [ITU-T V.18] and [ITU-T V.8].
+NOTE 8 – ITU-T V.21 110 bits/s half duplex is used for EDT, a legacy sub-mode of ITU-T V.18. Only lower channel is used. Pauses between text transmissions are silent or used for voice. EDT is used for text telephony in Germany, Italy, Spain, and Switzerland.
+NOTE 9 – DTMF is for textphones with text coding based on DTMF coded text.
+
+# Appendix VI
+
+## Example control interfaces
+
+(This appendix does not form an integral part of this Recommendation.)
+
+The following are two examples of control interfaces used for the required control functions that include enable/disable NLP, inhibit/enable adaptation, and reset H-register.
+
+## VI.1 Parallel transistor-transistor logic (TTL) connection for digital signals
+
+Figure VI.1 is an example of TTL connection on an echo canceller testing unit. A cable needs to be provided by the echo canceller manufacturer for the connection to the echo canceller under test.
+
+
+
+The diagram shows a front view of a DB-9 female connector, which is a trapezoidal shape with nine pins arranged in two rows: the top row contains pins 5, 4, 3, 2, 1 from left to right, and the bottom row contains pins 9, 8, 7, 6 from left to right. To the right of the diagram is a table listing the pin numbers and their corresponding connections.
+
+| Pin | Connection |
+|-----|---------------------------|
+| 1 | Ground |
+| 2 | N/A |
+| 3 | Adaptation inhibit/enable |
+| 4 | H-register reset |
+| 5 | N/A |
+| 6 | Ground |
+| 7 | N/A |
+| 8 | NLP enable/disable |
+| 9 | N/A |
+
+G.168(09)\_FVI.1
+
+Diagram of a TTL DB-9 female connector front view and its pinout table.
+
+**Figure VI.1 – Connector wiring for echo canceller cable**
+
+## VI.2 Serial data link (ITU-T V.24 or RS-232) for software commands
+
+The serial data link is used for the software command control of the echo canceller under test. Besides the serial cable for the connection between the testing unit and the echo canceller under test, a set of commands needs to be provided by the echo canceller manufacturer for the required control functions.
+
+To meet the requirements on the synchronization between the test signals and the operation mode change of the echo canceller under test, the control signals must be well aligned with the test signals. Since it may take certain time from the moment a control signal is transmitted from the testing unit to the moment the echo canceller under test changes its operational mode, a control signal must be transmitted a control-ahead time before the test signals, so that the echo canceller can change its mode at a moment aligned with the test signals. It is required that the echo canceller manufacturer provide the control-ahead time. It is recommended that this control-ahead time be specified in the interface document and it shall be kept to no more than 200 ms.
+
+# Appendix VII
+
+## Guidance on echo canceller orientation in conference bridge applications
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## VII.1 Introduction
+
+In call topologies that include conference bridges where the participants are distant from each other, it is assumed that each conference bridge participant has an echo canceller intended to protect him from echo. The echo cancellers can be oriented in two ways: (a) facing the conference bridge circuit, or (b) facing the conference bridge participants. It is explained below that it is preferred to orient the echo cancellers facing the individual conference bridge participants for the purpose of cancelling the echoes created from their hybrids before the echoes leak to the network and get distributed by the conference bridge to the participants. Such a placement of echo cancellers not only avoids the degradation in Quality of Experience of other conference bridge participants, but also eliminates the occurrence of multiple-reflection echo in a conferencing scenario.
+
+One should avoid orienting echo cancellers to face the conference bridge circuit because the other participants in the call will experience quality degradation caused by listener echo [b-ITU-T G.126] from the hybrid reflections, regardless of the capabilities of the individual echo cancellers to handle multiple reflections. The reason for this is explained in the following clauses.
+
+## VII.2 Echo canceller oriented towards the hybrid of the conference bridge participant (recommended)
+
+Figure VII.1 gives the configuration when placing echo cancellers oriented towards the hybrids of conference bridge participants. The conference bridge participant 1 echo canceller will cancel any echo caused by his own hybrid so that the outgoing signal from conference bridge participant 1 entering the bridging network will be free of echo.
+
+When conference bridge participant 1 is talking, his voice will go through the hybrids of different conference bridge participants. However, the cancellers of different conference bridge participants ensure that hybrid reflections are not present in their respective out-going signals to the bridging network. As a result, no participant in the conference bridge will be subjected to listener echo in the incoming voice signal. Furthermore, conference bridge participant 1 is protected from echo indirectly because no echo is present in the bridge connection. An added benefit for such placement of echo canceller is that each canceller is dealing with a single hybrid reflection and it will not encounter multiple reflections caused by the hybrids of different conference bridge participants. Consequently, this will improve the initial echo canceller rate of adaptation and double-talk performance.
+
+
+
+Figure VII.1: Conference bridge with echo canceller facing the hybrid of conference bridge participant. The diagram shows multiple participants (2, 3, ..., N) connected to a central 'Conference bridge' block. Each participant's path includes a hybrid and an echo canceller. Arrows labeled 'No reflection' point from the echo cancellers into the bridge. On the right, 'Conference bridge participant 1' is shown with signal labels S\_in, S\_out, and R\_in. A reference label G.168(11)-Amd.1(12)\_FVII.1 is at the bottom right.
+
+**Figure VII.1 – Conference bridge with echo canceller facing the hybrid of conference bridge participant**
+
+## **VII.3 Echo canceller oriented away from the hybrid of the conference bridge participant (not recommended)**
+
+Figure VII.2 depicts the block diagram of a conference bridge when the echo cancellers are oriented away from the conference bridge circuit. When conference bridge participant 1 is talking, his voice will be reflected by the hybrids of different conference bridge participants and the echo canceller of conference bridge participant 1 will see multiple-reflection echoes in the send-path for cancellation.
+
+
+
+Figure VII.2: Conference bridge with echo canceller facing the bridging circuit. This diagram is similar to Figure VII.1 but shows 'Reflection' arrows pointing from the bridge back into the echo cancellers of participants 2, 3, ..., N. Participant 1 on the right shows signal labels R\_in, S\_in, and S\_out. A reference label G.168(11)-Amd.1(12)\_FVII.2 is at the bottom right.
+
+**Figure VII.2 – Conference bridge with echo canceller facing the bridging circuit**
+
+When echo canceller 1 is operating properly, conference bridge participant 1 will not hear his own echo. However, the reflection of the voice from conference bridge participant 1 caused by the hybrid of conference bridge participant 2 will propagate to other conference bridge participants; conference bridge participant 3 will hear the original conference bridge participant 1 signal plus its attenuated and delayed version from the reflection of the conference bridge participant 2 hybrid. If the delay in the reflected signal is not small relative to the original signal, the echo will be noticeable. Similarly, other conference participants will encounter voice quality degradation due to such reflections. In other words, having the echo canceller oriented towards the network can protect the talker from his/her own echo but cannot avoid the degradation of Quality of Experience perceived by other conference bridge participants.
+
+For echo cancellers configured in this manner, the voice signal perceived by conference bridge participant $i$ can be approximated by:
+
+$$X_i = \sum_{\substack{j=1 \\ j \neq i}}^N \left( S_j + \sum_{k=1}^N m^{(k)} * S_j \right)$$
+
+where $N$ is the number of participants in the conference call, $S_j$ is the speech signal from talker $j$ , $m^{(k)}$ is the hybrid impulse response of conference bridge participant $k$ and $*$ denotes the convolution operation. The second term inside the parenthesis represents listener echo due to hybrid reflections which can significantly degrade the Quality of Experience for conference bridge participant $i$ . Note that the echo canceller of conference bridge participant $i$ is configured to remove his own echo using his originating speech signal as $R_{in}$ . It should be emphasized that no matter how well this echo canceller is designed, it will not be able to remove the listener echo component because it is not caused by the speech of conference bridge participant $i$ .
+
+### VII.3.1 Echo canceller orientation for conference bridge participant with small tail end delays (special case)
+
+In conferencing scenarios in which the terminating connections do not have echo cancellers for the reason that the listener echoes are not noticeable due to the short echo delays, the echo canceller may be positioned after the conference bridge to remove the talker echo of the far-end user. This scenario is shown in Figure VII.3, in which the conference bridge participants 2 to $N$ are not too far from each other and they do not have individual echo cancellers. Owing to the small differences in echo delays, the echo canceller in this case will not see separated multiple hybrid reflections (the reflections largely overlap with each other), but could encounter echo path change when some of conference participants 2 to $N$ enter and/or leave during the conference call. To protect conference bridge participants 2 to $N$ against the echo caused by the hybrid of the far-end user (conference bridge participant 1), another echo canceller facing the far-end-user hybrid is needed before the incoming signal is distributed to participants 2 to $N$ . The suggested arrangement for the two echo cancellers is shown in Figure VII.3. However, if technically or economically feasible, it is highly recommended to adopt separate echo canceller arrangements shown in Figure VII.1 to ensure higher voice quality.
+
+
+
+The diagram illustrates a conference bridge scenario. On the left, multiple participants (labeled 'Conference bridge participant 2', 'Conference bridge participant 3', and 'Conference bridge participant N') are connected to a central 'Conference bridge' block. Each participant is connected via a diamond-shaped switch. Dashed arrows indicate echo paths from the bridge back to these participants. On the right, 'Conference bridge participant 1' is also connected via a diamond-shaped switch. This participant's connection includes signal processing blocks: $R_{in}$ and $S_{in}$ (rectangles) and $S_{out}$ (circles). Arrows show signal flow between these blocks and the bridge. A cloud shape represents a network or delay element between the bridge and participant 1's processing blocks. A small text label 'G.168(11)-Amd.1(12)\_FVII.3' is located at the bottom right of the diagram.
+
+Diagram of a conference bridge scenario showing multiple participants (2 to N) and one participant (1) connected to a central conference bridge. The diagram illustrates signal flow and echo delays for the participants.
+
+**Figure VII.3 – Conference bridge scenario in which the terminating connections for participants 2 to $N$ do not experience listener echoes due to short echo delays amongst them**
+
+# Appendix VIII
+
+## Test methodologies for use on embedded echo cancellers
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## VIII.1 Introduction
+
+The purpose of this appendix is to define methods for testing embedded echo cancellers (EECs) for conformance with Annex E.
+
+The appendix defines two test methodologies. Test methodology 1 uses a special "Test Mode" to access the various echo canceller control signals required to perform ITU-T G.168 Annex E tests. Test methodology 2 provides a means to perform the tests when h-register freeze is not available. This will allow for testing of an EEC that has conventional 4-wire access (TDM or packet), together with some means to control the NLP. Test methodology 2 may not be applicable to all echo canceller algorithms that are otherwise compliant to ITU-T G.168 (i.e., the algorithm itself is tested as a non-embedded echo canceller for ITU-T G.168 compliance, before it becomes embedded). For example, it requires that the echo canceller inhibits adaptation immediately after the near end signal level is higher than the far end signal level. In order to avoid misleading results with methodology 2, it is important to check its applicability to the echo canceller algorithm. Procedures to do so are for further study. This methodology cannot be used for tests where the NLP is on (for example Test 2C a), thus it can provide only partial compliance to Annex E. Methodology 2 has not been thoroughly tested, therefore it should be considered experimental and a topic for further study. Testing of EECs with 2-wire interfaces and where NLP on/off control is not available is also for further study.
+
+## VIII.2 Test Methodology 1: Testing with the aid of a special "Test Mode" (under study)
+
+With this methodology, the EEC under test should be provided with a special "TEST MODE". When this mode is entered the EEC will accept pre-defined control signals (such as NLP on/off, h-register reset, h-register freeze, etc.) using a method to be determined. The "TEST MODE" may be entered by either a hardware or software binary switch provided by the EEC host. When in the "TEST MODE", other functions associated with the EEC host (e.g., voice coding) that would be active during normal operation MUST remain active.
+
+## VIII.3 Test Methodology 2: Testing without access to control signals (under study)
+
+This methodology requires that the EEC under test is equipped with a double talk (DT) detector that will freeze h-register adaptation immediately upon detection of a DT signal and keeps the adaptation frozen during the presence of this signal. The inhibition of h-register adaptation is accomplished by injecting a high level DT signal to the $S_{gen}$ port. The artificial DT signal occupies a portion of the frequency range only, so that it can be filtered out by processing the $S_{out}$ signal. The residual echo component that does not reside in the same frequency range as the artificial DT signal will remain in the filter output for EEC performance evaluation.
+
+The method uses two pairs of filters. One pair ( $G_{LL}(z), G_{LH}(z)$ ) is for assessing the echo cancellation performance in the low-frequency portion of the voice spectrum. The other pair ( $G_{HL}(z), G_{HH}(z)$ ) is for assessing the performance in the high-frequency portion. The magnitude responses of the filters should satisfy the following three conditions over the voice frequency range from 0 to 4000 Hz:
+
+$$|G_{LL}(f)|(dB) + |G_{LH}(f)|(dB) \leq -55\text{ dB} \quad (\text{VIII-1})$$
+
+$$|G_{HL}(f)|(dB) + |G_{HH}(f)|(dB) \leq -55\text{ dB} \quad (\text{VIII-2})$$
+
+$$-0.1\text{ dB} \leq 10 \log \left( |G_{LL}(f)|^2 + |G_{HH}(f)|^2 \right) (\text{dB}) \leq 0.1\text{ dB} \quad (\text{VIII-3})$$
+
+Note that the additions in equations (VIII-1) and (VIII-2) are in log-scale and the sum in equation (VIII-3) is in linear-scale. Condition (VIII-1) guarantees the filter pair ( $G_{LL}(z), G_{LH}(z)$ ) complement each other and have a net gain sufficiently close to zero when a signal goes through the two filters. Condition (VIII-2) guarantees these properties for the pair ( $G_{HL}(z), G_{HH}(z)$ ). Condition (VIII-3) ensures the two filters $G_{LL}(z)$ and $G_{HH}(z)$ together provide nearly unit energy gain over the entire frequency range. An example of the filters is shown in Tables VIII.1 to VIII.4, where the coefficients are specified in fixed-point integer format. Figures VIII.1 to VIII.3 confirm that the filters satisfy the three conditions listed above.
+
+To perform ITU-T G.168 tests in which adaptation of the h-register must be inhibited, the following steps are used:
+
+- i) Performance evaluation in the low frequency region:
+ - Generate white Gaussian noise (WGN) of $\pm 11$ dB crest factor
+ - Pass the WGN through the filter $G_{LH}(z)$ to generate Gaussian noise $w_{HP}(n)$ that has high-frequency content only
+ - Scale $w_{HP}(n)$ to have a level higher than $L_{Rin}$
+ - Add $w_{HP}(n)$ to the $S_{gen}$ port whenever h-register adaptation is required to be disabled during the test
+ - Process the $S_{out}$ signal using $G_{LL}(z)$ to generate $S_{out,LP}(n)$ , the component of $S_{out}$ in the low part of the spectrum
+ - Measure the level of $S_{out,LP}(n)$ , $L_{Sout, LP}$
+- ii) Performance evaluation in the high frequency region
+ - Generate white Gaussian noise (WGN) of $\pm 11$ dB crest factor
+ - Pass the WGN through the filter $G_{HL}(z)$ to generate Gaussian noise $w_{LP}(n)$ that has low-frequency content only
+ - Scale $w_{LP}(n)$ to have a level higher than $L_{Rin}$
+ - Add $w_{LP}(n)$ to the $S_{gen}$ port whenever h-register adaptation is required to be disabled during the test
+ - Process the $S_{out}$ signal using $G_{HH}(z)$ to generate $S_{out,HP}(n)$ , the component of $S_{out}$ in the high part of the spectrum
+ - Measure the level of $S_{out,HP}(n)$ , $L_{Sout, HP}$
+- iii) Performance evaluation (measuring EEC residual echo during DT)
+ - Add $L_{Sout, LP}$ and $L_{Sout, HP}$ (on a power basis) to form $L_{Sout}$ to assess ITU-T G.168 test requirements.
+
+NOTE 1 – The use of other artificial DT signals and filters, such as tones and notch filters, are currently under investigation.
+
+NOTE 2 – Depending on implementation, the $w(n)$ signal level may be attenuated before reaching the $S_{in}$ port of an EEC (e.g., by other signal processing functions such as noise reduction, etc.). To ensure the $w(n)$ signal level is sufficient to activate the DT detector, a level check on $w(n)$ in $S_{out}$ with respect to the original level should be made while the $R_{in}$ signal is removed.
+
+NOTE 3 – The level of $w(n)$ should be set high enough to activate promptly the DT detector, but to avoid possible clipping of the $w(n)$ signal it should not be too high.
+
+**Table VIII.1 – Coefficients $g_{LL}(k)$ of the filter $G_{LL}(z)$ (Q15 fixed-point format)**
+
+| Index k | $g_{LL}(k)$ | Index k | $g_{LL}(k)$ | Index k | $g_{LL}(k)$ |
+|-----------------------------|-------------|-----------------------------|-------------|-----------------------------|-------------|
+| 0, 64 | 22 | 16, 48 | 208 | 32 | 16762 |
+| 1, 63 | -20 | 17, 47 | -370 | | |
+| 2, 62 | -36 | 18, 46 | -240 | | |
+| 3, 61 | 18 | 19, 45 | 502 | | |
+| 4, 60 | 44 | 20, 44 | 272 | | |
+| 5, 59 | -39 | 21, 43 | -680 | | |
+| 6, 58 | -67 | 22, 42 | -301 | | |
+| 7, 57 | 59 | 23, 41 | 930 | | |
+| 8, 56 | 88 | 24, 40 | 327 | | |
+| 9, 55 | -92 | 25, 39 | -1305 | | |
+| 10, 54 | -115 | 26, 38 | -349 | | |
+| 11, 53 | 135 | 27, 37 | 1950 | | |
+| 12, 52 | 144 | 28, 36 | 365 | | |
+| 13, 51 | -193 | 29, 35 | -3394 | | |
+| 14, 50 | -175 | 30, 34 | -375 | | |
+| 15, 49 | 270 | 31, 33 | 10402 | | |
+
+**Table VIII.2 – Coefficients $g_{LH}(k)$ of the filter $G_{LH}(z)$ (Q15 fixed-point format)**
+
+| Index k | $g_{LH}(k)$ | Index k | $g_{LH}(k)$ | Index k | $g_{LH}(k)$ |
+|-----------------------------|-------------|-----------------------------|-------------|-----------------------------|-------------|
+| 0, 64 | 26 | 16, 48 | 238 | 32 | 12731 |
+| 1, 63 | 2 | 17, 47 | 223 | | |
+| 2, 62 | -35 | 18, 46 | -486 | | |
+| 3, 61 | 36 | 19, 45 | 90 | | |
+| 4, 60 | 17 | 20, 44 | 563 | | |
+| 5, 59 | -65 | 21, 43 | -560 | | |
+| 6, 58 | 24 | 22, 42 | -299 | | |
+| 7, 57 | 78 | 23, 41 | 982 | | |
+| 8, 56 | -100 | 24, 40 | -382 | | |
+| 9, 55 | -26 | 25, 39 | -1040 | | |
+| 10, 54 | 158 | 26, 38 | 1394 | | |
+| 11, 53 | -89 | 27, 37 | 355 | | |
+| 12, 52 | -144 | 28, 36 | -2488 | | |
+| 13, 51 | 234 | 29, 35 | 1697 | | |
+| 14, 50 | 5 | 30, 34 | 3334 | | |
+| 15, 49 | -313 | 31, 33 | -9778 | | |
+
+**Table VIII.3 – Coefficients $g_{HL}(k)$ of the filter $G_{HL}(z)$ (Q15 fixed-point format)**
+
+| Index k | $g_{HL}(k)$ | Index k | $g_{HL}(k)$ | Index k | $g_{HL}(k)$ |
+|-----------------------------|-------------|-----------------------------|-------------|-----------------------------|-------------|
+| 0, 64 | 26 | 16, 48 | 239 | 32 | 12 732 |
+| 1, 63 | −1 | 17, 47 | −222 | | |
+| 2, 62 | −35 | 18, 46 | −486 | | |
+| 3, 61 | −37 | 19, 45 | −91 | | |
+| 4, 60 | 17 | 20, 44 | 563 | | |
+| 5, 59 | 65 | 21, 43 | 560 | | |
+| 6, 58 | 24 | 22, 42 | −299 | | |
+| 7, 57 | −78 | 23, 41 | −982 | | |
+| 8, 56 | −100 | 24, 40 | −382 | | |
+| 9, 55 | 26 | 25, 39 | 1039 | | |
+| 10, 54 | 158 | 26, 38 | 1394 | | |
+| 11, 53 | 90 | 27, 37 | −355 | | |
+| 12, 52 | −143 | 28, 36 | −2488 | | |
+| 13, 51 | −234 | 29, 35 | −1698 | | |
+| 14, 50 | 5 | 30, 34 | 3334 | | |
+| 15, 49 | 313 | 31, 33 | 9778 | | |
+
+**Table VIII.4 – Coefficients $g_{HH}(k)$ of the filter $G_{HH}(z)$ (Q15 fixed-point format)**
+
+| Index k | $g_{HH}(k)$ | Index k | $g_{HH}(k)$ | Index k | $g_{HH}(k)$ |
+|-----------------------------|-------------|-----------------------------|-------------|-----------------------------|-------------|
+| 0, 64 | 22 | 16, 48 | 207 | 32 | 16 762 |
+| 1, 63 | 20 | 17, 47 | 370 | | |
+| 2, 62 | −36 | 18, 46 | −240 | | |
+| 3, 61 | −18 | 19, 45 | −503 | | |
+| 4, 60 | 44 | 20, 44 | 271 | | |
+| 5, 59 | 39 | 21, 43 | 681 | | |
+| 6, 58 | −67 | 22, 42 | −301 | | |
+| 7, 57 | −59 | 23, 41 | −930 | | |
+| 8, 56 | 88 | 24, 40 | 327 | | |
+| 9, 55 | 92 | 25, 39 | 1305 | | |
+| 10, 54 | −115 | 26, 38 | −348 | | |
+| 11, 53 | −135 | 27, 37 | −1950 | | |
+| 12, 52 | 144 | 28, 36 | 364 | | |
+| 13, 51 | 193 | 29, 35 | 3394 | | |
+| 14, 50 | −175 | 30, 34 | −374 | | |
+| 15, 49 | −270 | 31, 33 | −10403 | | |
+
+
+
+This graph shows the magnitude responses of two filters, $|G_{LL}(f)|$ (blue line) and $|G_{LH}(f)|$ (green line), over a frequency range from 0 to 4000 Hz. The y-axis represents the magnitude response in dB, ranging from -100 to 20. The $|G_{LL}(f)|$ filter is a low-pass filter that is flat at 0 dB from 0 to approximately 1800 Hz, then drops sharply to -100 dB by 2500 Hz, and exhibits ripples between -60 dB and -100 dB from 2500 Hz to 4000 Hz. The $|G_{LH}(f)|$ filter is a high-pass filter that is flat at 0 dB from approximately 2200 Hz to 4000 Hz, and exhibits ripples between -60 dB and -100 dB from 0 Hz to 2200 Hz. The two filters are complementary, with their passbands meeting around 2000 Hz.
+
+Magnitude responses of the filter pair (G\_LL(z), G\_LH(z))
+
+**Figure VIII.1 – Magnitude responses of the filter pair ( $G_{LL}(z)$ , $G_{LH}(z)$ ) generated from the coefficients specified in Tables VIII.1 and VIII.2**
+
+
+
+This graph shows the magnitude responses of two filters, $|G_{HL}(f)|$ (green line) and $|G_{HH}(f)|$ (blue line), over a frequency range from 0 to 4000 Hz. The y-axis represents the magnitude response in dB, ranging from -100 to 20. The $|G_{HL}(f)|$ filter is a high-pass filter that is flat at 0 dB from 0 to approximately 1500 Hz, then drops sharply to -100 dB by 2000 Hz, and exhibits ripples between -60 dB and -100 dB from 2000 Hz to 4000 Hz. The $|G_{HH}(f)|$ filter is a low-pass filter that is flat at 0 dB from approximately 2200 Hz to 4000 Hz, and exhibits ripples between -60 dB and -100 dB from 0 Hz to 2200 Hz. The two filters are complementary, with their passbands meeting around 1800 Hz.
+
+Magnitude responses of the filter pair (G\_HL(z), G\_HH(z))
+
+**Figure VIII.2 – Magnitude responses of the filter pair ( $G_{HL}(z)$ , $G_{HH}(z)$ ) generated from the coefficients specified in Tables VIII.3 and VIII.4**
+
+
+
+The figure is a line graph with a blue curve representing the total gain. The y-axis is labeled $(|G_{LL}(f)|^2 + |G_{HH}(f)|^2) \text{ (dB)}$ and has major ticks at -0.1, -0.08, -0.06, -0.04, -0.02, 0, 0.02, 0.04, 0.06, 0.08, and 0.1. The x-axis is labeled 'Frequence f (Hz)' and has major ticks at 0, 500, 1000, 1500, 2000, 2500, 3000, 3500, and 4000. The curve oscillates around 0 dB. It has a sharp negative peak at 2000 Hz, reaching approximately -0.06 dB. Other smaller peaks and troughs occur at regular intervals, roughly every 250 Hz. A small label 'G.168(15)\_FVIII.3' is located in the bottom right corner of the plot area.
+
+A line graph showing the total gain resulting from G\_LL(z) and G\_HH(z) across a frequency range from 0 to 4000 Hz. The y-axis is labeled (|G\_LL(f)|^2 + |G\_HH(f)|^2) (dB) and ranges from -0.1 to 0.1. The x-axis is labeled 'Frequence f (Hz)' and ranges from 0 to 4000. The graph shows a blue oscillating signal with a significant dip at 2000 Hz.
+
+**Figure VIII.3 – Total gain resulting from $G_{LL}(z)$ , $G_{HH}(z)$**
+
+# Bibliography
+
+- [b-ITU-T G.108.2] Recommendation ITU-T G.108.2 (2007), *Transmission planning aspects of echo cancellers.*
+- [b-ITU-T G.113] Recommendation ITU-T G.113 (2007), *Transmission impairments due to speech processing.*
+- [b-ITU-T G.126] Recommendation ITU-T G.126 (1993), *Listener echo in telephone networks.*
+- [b-ITU-T G.160] Recommendation ITU-T G.160 (2012), *Voice Enhancement Devices.*
+- [b-ITU-T P.341] Recommendation ITU-T P.341 (2005), *Transmission characteristics for wideband (150-7000 Hz) digital hands-free telephony terminals.*
+- [b-ITU-T P.342] Recommendation ITU-T P.342 (2000), *Transmission characteristics for telephone band (300-3400 Hz) digital loudspeaking and hands-free telephony terminals.*
+- [b-ITU-T P.561] Recommendation ITU-T P.561 (2002), *In-service non-intrusive measurement device – Voice service measurements.*
+- [b-ITU-T P.831] ITU-T Recommendation P.831 (1998), *Subjective performance evaluation of network echo cancellers.*
+- [b-ITU-T Q.55] Recommendation ITU-T Q.55 (1999), *Signalling between signal processing network equipments (SPNE) and international switching centres (ISC).*
+- [b-ITU-T V.32] Recommendation ITU-T V.32 (1993), *A family of 2-wire, duplex modems operating at data signalling rates of up to 9600 bit/s for use on the general switched telephone network and on leased telephone-type circuits.*
+- [b-ITU-T V.32 bis] Recommendation ITU-T V.32 bis (1991), *A duplex modem operating at data signalling rates of up to 14 400 bit/s for use on the general switched telephone network and on leased point-to-point 2-wire telephone-type circuits.*
+- [b-ITU-T V.61] Recommendation ITU-T V.61 (1996), *A simultaneous voice plus data modem, operating at a voice plus data signalling rate of 4800 bit/s, with optional automatic switching to data-only signalling rates of up to 14 400 bit/s, for use on the General Switched Telephone Network and on leased point-to-point 2-wire telephone type circuits.*
+- [b-ITU-T GSTP.CSS] ITU-T Technical Paper GSTP.CSS (2010), *The composite source signal as a measuring signal and a summary of various investigations on speech echo cancellers.*
+- [b-Borish] Borish, J. and Angel, J.B. (1983), *An efficient algorithm for measuring the impulse response using pseudo-random noise*, Journal of the Audio Engineering Society, Vol. 31, pp. 478-488.
+
+
+
+# SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|---------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/G/T-REC-G.176-199704-I_PDF-E/raw.md b/marked/G/T-REC-G.176-199704-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..004cb557e22093dcc3f7d3a1849d47645a3055a6
--- /dev/null
+++ b/marked/G/T-REC-G.176-199704-I_PDF-E/raw.md
@@ -0,0 +1,413 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**G.176**
+
+(04/97)
+
+SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
+DIGITAL SYSTEMS AND NETWORKS
+
+International telephone connections and circuits –
+Transmission plan aspects of special circuits and
+connections using the international telephone connection
+network
+
+---
+
+**Planning guidelines for the integration of ATM
+technology into networks supporting voiceband
+services**
+
+ITU-T Recommendation G.176
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS**
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 |
+| General definitions | G.100–G.109 |
+| General Recommendations on the transmission quality for an entire international telephone connection | G.110–G.119 |
+| General characteristics of national systems forming part of international connections | G.120–G.129 |
+| General characteristics of the 4-wire chain formed by the international circuits and national extension circuits | G.130–G.139 |
+| General characteristics of the 4-wire chain of international circuits; international transit | G.140–G.149 |
+| General characteristics of international telephone circuits and national extension circuits | G.150–G.159 |
+| Apparatus associated with long-distance telephone circuits | G.160–G.169 |
+| Transmission plan aspects of special circuits and connections using the international telephone connection network | G.170–G.179 |
+| Protection and restoration of transmission systems | G.180–G.189 |
+| Software tools for transmission systems | G.190–G.199 |
+| INTERNATIONAL ANALOGUE CARRIER SYSTEM | |
+| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 |
+| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 |
+| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 |
+| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 |
+| TRANSMISSION MEDIA CHARACTERISTICS | |
+| DIGITAL TRANSMISSION SYSTEMS | |
+| TERMINAL EQUIPMENTS | G.700–G.799 |
+| DIGITAL NETWORKS | G.800–G.899 |
+| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 |
+
+For further details, please refer to ITU-T List of Recommendations.
+
+## **ITU-T RECOMMENDATION G.176**
+
+# **PLANNING GUIDELINES FOR THE INTEGRATION OF ATM TECHNOLOGY INTO NETWORKS SUPPORTING VOICEBAND SERVICES**
+
+## **Summary**
+
+This Recommendation provides transmission performance planning guidance to network and service planners who are responsible for the integration of ATM technology, e.g. digital processing equipment, multiplexers, and switches, into the PSTN. This Recommendation recognizes and addresses: the interconnection of other networks, e.g. Private Networks and Digital Cellular Networks, with the PSTN, and the continued need to support existing voiceband services.
+
+### **Source**
+
+ITU-T Recommendation G.176 was prepared by ITU-T Study Group 12 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 18th of April 1997.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, the ITU had/had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 1997
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+###### Page
+
+| | | |
+|-----|----------------------------------------------------------------------------|---|
+| 1 | Preamble ..... | 1 |
+| 2 | Scope..... | 1 |
+| 3 | Normative references..... | 1 |
+| 4 | Terms and definitions ..... | 2 |
+| 5 | Abbreviations..... | 4 |
+| 6 | Assumed network operating configuration..... | 4 |
+| 7 | ATM technology functions..... | 5 |
+| 7.1 | ATM technology as a digital signal processing unit..... | 5 |
+| 7.2 | ATM technology as a multiplexer ..... | 5 |
+| 7.3 | ATM technology as a transport system..... | 6 |
+| 7.4 | ATM as a switched network function..... | 6 |
+| 7.5 | ATM interworking function (ATM cell – PDH/SDH interworking function) ..... | 7 |
+| 8 | Planning guidelines..... | 7 |
+
+
+
+# **PLANNING GUIDELINES FOR THE INTEGRATION OF ATM TECHNOLOGY INTO NETWORKS SUPPORTING VOICEBAND SERVICES**
+
+*(Geneva, 1997)*
+
+# **1 Preamble**
+
+This Recommendation is intended to provide transmission performance planning guidance to network and service planners who are responsible for the integration of ATM technology into networks. This Recommendation assumes that ATM will always ride on a standard physical layer transmission system, e.g. SONET (Synchronous Optical NETwork), Synchronous Digital Hierarchy (SDH).
+
+The current regulatory operating environment in certain countries has made allowance for other networks to interconnect with the PSTN. Thus, this Recommendation also addresses the interconnection of other networks, e.g. Private Networks and Digital Cellular Networks, with the PSTN and it is consistent with the concept that customers may provision their own terminal equipment. The information in this Recommendation is intended to provide guidance consistent with this operating environment.
+
+# **2 Scope**
+
+This Recommendation deals with the subject of planning the integration of ATM technology into networks. The introduction of ATM technology into the PSTN will make it more difficult to convey in a unique fashion what is meant by the term "digital PSTN" and in some instances will require an ability to uniquely reference the portion of technology within it that is ATM or non-ATM in character. To overcome this hurdle, the term "Plesiochronous Digital Hierarchy/Synchronous Digital Hierarchy (PDH/SDH) oriented networks" will be used, the intention being that these networks represent the byte domain while ATM networks represent the cell domain. To work between these domains, viz. between the PDH/SDH and the ATM cell domain, it is understood that an interworking function must exist and while it may physically occur in the PDH/SDH or the ATM cell-oriented hardware, it is always deemed to occur at the boundaries of the PDH/SDH and ATM cell networks.
+
+A number of existing Recommendations deal with the subject of transmission impairments that affect modern telephone connections with regards to the quality of speech communications, and to some extent, data transmission in a generic sense, and are not intended to be tied to the technology used for the transmission medium. Thus, although they do not include explicit statements to say that they are intended to provide guidance on the integration of ATM technology into the PSTN, they can and should be used for guidance, e.g. Recommendations G.113, G.114 and G.131. Planning rules associated with the initial creation of ATM islands and planning rules for the introduction of additional ATM technology within each of these islands will be presented.
+
+# **3 Normative references**
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the
+
+most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
+
+- ITU-T Recommendation G.101 (1996), *The transmission plan*.
+- ITU-T Recommendation G.113 (1996), *Transmission impairments*.
+- ITU-T Recommendation G.114 (1996), *One-way transmission time*.
+- ITU-T Recommendation G.122 (1993), *Influence of national systems on stability talker echo in international connections*.
+- ITU-T Recommendation G.126 (1993), *Listener echo in telephone networks*.
+- ITU-T Recommendation G.131 (1996), *Control of talker echo*.
+- CCITT Recommendation G.132 (1988), *Attenuation distortion*.
+- ITU-T Recommendation I.361 (1995), *B-ISDN ATM Layer Specification*.
+- ITU-T Recommendation Q.552 (1996), *Transmission characteristics at 2-wire analogue interfaces of digital exchanges*.
+- ITU-T Recommendation G.712 (1996), *Transmission performance characteristics of pulse code modulation channels*.
+- ITU-T Recommendation I.731 (1996), *Types and general characteristics of ATM equipment*.
+- ITU-T Recommendation I.732 (1996), *Functional characteristics of ATM equipment*.
+
+# 4 Terms and definitions
+
+This Recommendation defines the following terms:
+
+**4.1 asynchronous transfer mode (ATM):** The term applied to a technology that is based on the premise that information is transported in cells. Specifically, in this Recommendation ATM is used to apply to technology that uses Recommendation I.361 B-ISDN ATM Layer Specification for ATM cell size and makeup, viz. 53 octets per cell with 5 octets allocated for the header and 48 octets allocated to carry payload information.
+
+Additionally, the ATM technology is expected to be designed consistent with Recommendation I.731 and operate consistent with the functional characteristics defined in Recommendation I.732.
+
+**4.2 ATM digital signal processing function (see Figure 2):** The term applied to ATM technology that operates with cell-based signals operating over standard line rates on both the inputs and the outputs, e.g. E3 on the input and E3 on the output, and which modifies the payload contents of the cells as they pass through in some prescribed manner. This device may modify none, some, or all of the cells that pass through it. This cell modification is intended to change the transmission characteristics of the signals in the virtual connections, e.g. this device may perform echo cancellation or speech compression on some or all the virtual connections that pass through it.
+
+**4.3 ATM multiplexer/crossconnect (see Figure 3):** The term applied to a cell-multiplexing device that operates with cell-based signals and over standard line rates on all interfaces, e.g. T1 and T3, and which passes the cells received on an input to an output. The relationship between input and output, i.e. the virtual circuits routing, does not change on a per call basis, i.e. only permanent virtual circuits are supported. This device does not allow blocking or signal compression.
+
+**4.4 ATM transport system (see Figure 4):** The term applied to a transport system that is composed of a carrier system terminated by an ATM multiplexer at each end. The relationship between input and output, i.e. virtual circuits, cannot change on a per call basis, i.e. permanent virtual circuits only are supported. This device does not allow blocking or signal compression.
+
+**4.5 ATM switch (digital interfaces only) (see Figure 5):** The term applied to ATM technology that operates with cell-based signals and over standard line rates on both the inputs and the outputs, e.g. T1 or E1 on the input and T3 or E3 on the output, and which passes the cells received on the input to the output. The relationship between input and output, can change on a per call basis, i.e. switched virtual circuits must be supported and permanent virtual circuits may be supported. This device allows blocking and performs concentration.
+
+**4.6 ATM switch (analogue and digital interfaces) (see Figure 6):** The term applied to ATM technology that operates with analogue 2-wire interfaces1 and standard digital line rates on both the inputs and the outputs, e.g. T1 on the input and T3 on the output, and which passes the cells received on the input to the output. The relationship between input and output, can change on a per call basis, i.e. switched virtual circuits must be supported and permanent virtual circuits may be supported. (For the purposes of this Recommendation it is assumed that the cell formation function associated with an analogue input is performed before the switch function occurs. However, this definition is not intended to constrain technical implementations.) This device allows blocking and concentration. The switch function is also required to perform 2-wire to 4-wire conversion as well as A/D conversion.
+
+**4.7 ATM interworking function (with narrowband services in the PDH/SDH byte-oriented domain) (see Figure 7):** The term applied to a technology device that allows ATM systems, i.e. cell-oriented systems, to interwork with narrowband, byte-oriented systems. Although interworking will have to occur in both the transmission plane and the signalling plane, this Recommendation will restrict itself to the transmission plane.
+
+**4.8 DS1 signal:** The term used to apply to a primary rate line signal. The signal at an interface can be specified as either E1 or T1.
+
+**4.9 DS3 signal:** The term used to apply to a line signal operating at the 3rd level in the transmission hierarchy. The signal at an interface can be specified as either E3 or T3.
+
+**4.10 equipment impairment factor:** A number allocated to a network element, in units of "eif", that indicates the anticipated incremental level of impairment that would result when this element is inserted into a connection. See Recommendation G.113.
+
+**4.11 equipment impairment factor unit:** The unit "eif" (Equipment Impairment Factor) is used to specify the impairment associated with a particular network element, e.g. transmission circuit or digital signal processing unit. See Recommendation G.113.
+
+**4.12 guidance not required (GNR):** The term GNR is used in Table 1 and is used to indicate that the associated parameter should have negligible or no impact on the ATM functionality under consideration (This is because approved ATM or SDH objectives for these parameters are sufficiently stringent so as not to affect the performance of the derived voiceband channels.) It is the responsibility of the network planner to ensure that this assumption is not invalidated by selection of inappropriate equipment.
+
+**4.13 preliminary guidance available (PGA):** The term "PGA" is used in Table 1 and is used to indicate that the associated parameter must be considered in the context of transmission performance for end-to-end connections and that preliminary guidance is available. (Sources where guidance information can be found is provided within square brackets within Table 1.)
+
+---
+
+1 This configuration is not intended to exclude analogue 4-wire interfaces. However, the intended focus is on the 2-wire interface. For convenience, this 2-wire interface is assumed to occur in a 2-wire line card. However, use of this term is not intended to constrain technical implementations.
+
+**4.14 requires further study (RFS):** The term "RFS" is used in Table 1 and is used to indicate that a reference cannot be made to a Recommendation that provides guidance needed in this area. Further, it is recognized that this guidance should be available and is urgently required.
+
+**4.15 total impairment value:** A numerical value, obtained by summing up all of the element impairment factors of the end-to-end connection and which provides an indication of the expected quality of speech communication of the particular telephone connection. The Total Impairment Value consists of the sum of several Impairment Factors and is expressed in units of "eif".
+
+# 5 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|-------|----------------------------------------------------------------|
+| ATM | Asynchronous Transfer Mode |
+| eif | equipment impairment factor |
+| IWF | Interworking Function |
+| OC3 | Optical Carrier System Operating at the 3rd Hierarchical Level |
+| PBX | Private Automatic Branch Exchange |
+| PDH | Plesiochronous Digital Hierarchy |
+| PSTN | Public Switched Telecommunications Network |
+| SDH | Synchronous Digital Hierarchy |
+| SONET | Synchronous Optical Network |
+
+# 6 Assumed network operating configuration
+
+This Recommendation assumes a generic network operating configuration as shown in Figure 1. In this figure it can be seen that there are three interworking functions considered. The first one to consider is shown on the right and deals with A/D conversions as per Recommendation G.711 and typically would exist as a function built within a subscriber line interface of a PDH/SDH local exchange or PBX, e.g. Recommendation Q.552. This interworking function will not be addressed further as it has been added for completeness only and does not impact on our planning guideline discussions. The second interworking unit is on the left and deals with A/D conversions as per Recommendation G.711 and typically would exist as a function built within a line card of an ATM local exchange or PBX. A Recommendation covering this configuration is currently under development in ITU-T Study Group 15. Note that A/D conversions to other data rates may be performed at this physical point; however, such conversions are not contained within the current set of Recommendations and while it may be performed within a particular network, it is assumed that the G.711 signal format will be the normal signal carried across network boundaries. The use of other rates is an item for further study. The third interworking unit is shown between the ATM and PDH/SDH networks. The signals on the PDH/SDH and the ATM side are assumed to be G.711 compliant signals. While this unit could perform conversions between data rates, it is currently agreed that the G.711 signal format will be the normal signal carried across network boundaries. The use of other rates is an item for further study.
+
+
+
+The diagram illustrates an assumed operating configuration for G.176. It features two main network domains connected by an Interworking Function (IWF).
+ On the left, a 'Portion of network that operates using cells i.e. in the ATM cell domain' is shown. It is connected to two 'Digital 4-wire telephone' units and an 'IWF' block. The 'IWF' block is associated with 'G.711 Encoding (Note)' and 'A/D conversion here', and it connects to an 'Analogue 2-wire' line.
+ On the right, a 'PDH/SDH portion of network that operates using bytes, but not cells i.e. not in the ATM domain' is shown. It is connected to two 'digital 4-wire telephone' units and another 'IWF' block. This 'IWF' block is also associated with 'G.711 Encoding' and 'A/D conversion here', and it connects to an 'Analogue 2-wire' line.
+ The two 'IWF' blocks are connected to each other. Between them, text indicates 'Conversion between ATM and PDH/SDH performed here'.
+ A reference code 'T1208400-96' is located at the bottom right of the diagram.
+
+Diagram of assumed operating configuration showing two network domains connected by an IWF. The left domain is an ATM cell domain with digital 4-wire telephones and an IWF for analogue 2-wire conversion. The right domain is a PDH/SDH byte domain with digital 4-wire telephones and an IWF for analogue 2-wire conversion. Conversion between the two domains is performed in the center IWF.
+
+IWF Interworking Function
+
+NOTE – G.711 coding is shown. Other rates are for further study.
+
+**Figure 1/G.176 – Assumed operating configuration**
+
+# 7 ATM technology functions
+
+In the definition clause a number of ATM network element functions were identified, e.g. digital signal processing function and a multiplexer function. In this clause, these functions are considered packaged on a one per black box basis. As a result, the function is deemed to operate on a standalone basis and this is the way they are treated in a table in clause 8. However, in practice, more than one function could appear in a device. For these cases, the appropriate columns from the matrix table in clause 8 should be used. The reason for identifying the function of ATM as a digital signal processing unit is to focus discussion on the interfaces which exist on both sides of this ATM device.
+
+## 7.1 ATM technology as a digital signal processing unit
+
+An illustration of ATM technology acting as a digital signal processing unit is shown in Figure 2.
+
+
+
+The diagram shows a central grey rectangular block representing ATM technology acting as a digital signal processor. Two horizontal lines, representing signal paths, enter and exit this block from the left and right. Above each line is the text 'ATM over a standard bit rate signal e.g. DS3'. A reference code 'T1208410-96' is located at the bottom right of the diagram.
+
+Diagram of ATM technology operating as a digital signal processor, showing a central processing unit with two inputs/outputs labeled 'ATM over a standard bit rate signal e.g. DS3'.
+
+NOTE – This device may have more than one input and one output and the input and output rates can be different.
+
+**Figure 2/G.176 – ATM technology operating as a digital signal processor**
+
+## 7.2 ATM technology as a multiplexer
+
+An illustration of ATM technology acting as a multiplexer is shown in Figure 3. The reason for identifying the function of ATM as a multiplexing system is to focus discussion on the interfaces
+
+which exist on both sides of the ATM device. This category is intended to include devices which may be used to perform a digital cross-connect function.
+
+
+
+The diagram shows a central rectangular block representing an ATM device. On the left, four horizontal lines enter the block, each preceded by a small square bullet. To the left of these lines is the text 'ATM over a standard bit rate signal e.g. DS1, DS3'. On the right, a single horizontal line exits the block. To the right of this line is the text 'ATM over a standard bit rate signal e.g. DS1, DS3'. Below the block is the identifier 'T1208420-96'.
+
+Diagram of ATM technology operating as a multiplexer.
+
+**Figure 3/G.176 – ATM technology operating as a multiplexer**
+
+## 7.3 ATM technology as a transport system
+
+An illustration of ATM technology acting as a transport entity is shown in Figure 4. This is intended to address the situation where ATM multiplexers are used in conjunction with a transport system, e.g. when ATM multiplexers are combined with SONET/SDH to provide a transport function which has DS1 interfaces. Note that the supported service can be any rate below the T1 or E1 rate. In this configuration, the ATM multiplexer uses permanent virtual circuits which have constant bit rate channels and thus a signal compression function is not performed. For the purposes of this Recommendation, a multiplexer is defined as a device whose payload output is equal to the sum of the inputs plus overhead.
+
+
+
+The diagram shows two rectangular blocks, each labeled 'ATM technology as a multiplexer'. Between them is a horizontal line labeled 'Line transmission system operating at a standard rate e.g. DS3, OC3'. On the left, four horizontal lines with square bullets enter the first block, labeled 'ATM over a standard bit rate signal e.g. DS1, DS3'. On the right, four horizontal lines with square bullets exit the second block, also labeled 'ATM over a standard bit rate signal e.g. DS1, DS3'. Below the second block is the identifier 'T1208430-96'.
+
+Diagram of ATM technology operating as a transport system.
+
+**Figure 4/G.176 – ATM technology operating as a transport system**
+
+## 7.4 ATM as a switched network function
+
+ATM technology can operate as a switch. Figure 5 shows this switch configured with digital interfaces only. This figure is intended to apply to switches that could assume the functions of a PBX, an end office, or a tandem office.
+
+Figure 6 shows the switch with 2-wire analogue interfaces, intended to terminate a standard 2-wire telephone set on a loop access facility in the PBX or Local Exchange environment. This figure is also intended to apply to those cases where the ATM switch could terminate a digital loop subscriber carrier system.
+
+This Recommendation is not intended to promote particular operating configurations, but rather is focused on determining if standards exist for all operating arrangements.
+
+
+
+Diagram of ATM technology as a switch with digital interfaces only. A central grey rectangular switch is connected to two sets of digital facilities. On the left, 'ATM over digital facilities operating at a standard bit rate e.g. DS1, or DS3 or digital telephone access facilities' are connected via five dashed lines. On the right, 'ATM over digital facilities operating at a standard bit rate e.g. DS1, or DS3' are connected via five dashed lines. The reference 'T1208440-96' is at the bottom right.
+
+**Figure 5/G.176 – ATM technology as a switch – digital interfaces only (PBX, local exchange, tandem)**
+
+
+
+Diagram of ATM technology as a switch with 2-wire analogue and digital interfaces. A central grey rectangular switch is connected to two sets of facilities. On the left, '2-wire analogue phone access facilities (digital telephone access facilities may also be present)' are connected via five dashed lines. On the right, 'ATM over digital facilities operating at a standard bit rate e.g. DS1, DS3' are connected via five dashed lines. The reference 'T1208450-96' is at the bottom right.
+
+**Figure 6/G.176 – ATM technology as a switch – 2-wire analogue and digital interfaces (PBX, local exchange)**
+
+## 7.5 ATM interworking function (ATM cell – PDH/SDH interworking function)
+
+ATM systems will have to interwork with narrowband systems if ATM is to be integrated into current byte oriented networks, see Figure 7. The interworking function will have to occur in both the transmission plane and the signalling plane. This Recommendation will restrict itself to the transmission plane.
+
+
+
+Diagram of ATM technology operating as an interworking unit. A central grey rectangular block labeled 'Interworking function' is connected to two circular network domains. The left domain is 'Portion of network that operates using cells i.e. in the ATM cell domain'. The right domain is 'PDH/SDH portion of the network that operates using bytes, but not cells i.e. not in the ATM domain'. Both connections are labeled 'Standard line rate'. The reference 'T1208460-96' is at the bottom right.
+
+**Figure 7/G.176 – ATM technology operating as an interworking unit**
+
+# 8 Planning guidelines
+
+The guidelines developed in this clause are intended for use by a network or service planner who intends to either generate a new ATM domain, or an ATM island, within the PSTN or to add incremental ATM technology to an already existing ATM domain. These guidelines follow:
+
+- 1) The number of ATM islands in a connection should be minimized. While it is recognized that ATM islands will occur in the early stages of evolution of the PDH/SDH PSTN to an ATM PSTN, the total delay should be limited, see Recommendation G.114.
+- 2) The overall quality of a connection (see Recommendation G.101), depends upon the total equipment impairment factor units, viz. *Itot *, (see Recommendation G.113).
+- 3) It is the responsibility of the ATM domain provider to provide echo control or ensure that echo control is provided when:
+ - the one-way delay caused by an all ATM network domain exceeds G.131 requirements when completing connections between analogue terminals, terminated on it;
+ - the incremental additional delay caused by insertion of the ATM domain causes delay on connections to exceed the guidelines of G.131;
+ - the incremental one-way delay caused by the ATM delay exceeds 5 ms and there is uncertainty as to whether the requirements of Recommendation G.131 will be met for connections routed through the ATM domain.
+- 4) Unless there is a bilateral agreement to do otherwise, the ATM network implementor is expected to transmit a G.711 compliant signal across both ATM and PDH/SDH network boundaries and should expect to receive G.711 signals across both ATM and PDH/SDH network boundaries. It is also assumed that these G.711 compliant signals were generated using a G.712 or Q.552 compliant interface converter.
+- 5) The ATM network implementor should take into consideration the technical performance aspects associated with connections through the ATM domain. Table 1 below provides direction as to where guidance information may be obtained.
+
+In summary, Table 1 makes it clear that:
+
+- for the parameter of delay, all ATM functions are affected;
+- except for the ATM functions of ATM Digital Signal Processing and ATM Switching, all other ATM functions have little impact on embedded analogue signal performance parameters. Special attention should be given to the ATM Digital Signal Processing and ATM Switch functions, because many of the embedded analogue signal performance parameters can be affected.
+
+Table 1 provides network planners responsible for the integration of ATM technology into the PSTN with recommended sources for transmission performance planning guidance information.
+
+In Table 1, when standards appear in brackets within a cell, it means that these standards represent a valid provisional source of basic information and guidance until such time as definitive Recommendations associated with ATM can be generated. See clause 4 for the definitions and clause 5 for the abbreviations used in this table.
+
+**Table 1/G.176**
+
+| Parameter (Note 1) | ATM digital processing function (Figure 2) | ATM multiplex function (Digital interfaces) Figure 3) | ATM transport function (Digital interfaces) (Figure 4) | ATM switch function [PBX, local exchange & transit] (Digital interfaces) (Figure 5) | ATM switch function [PBX & local exchange] (Digital trunk & 2-wire analogue line interfaces) (Figure 6) | ATM Interworking unit function to narrowband PSTN (Figure 7) | |
+|----------------------------------------------------------------------------------------------|-----------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|----------------|
+| | | | | | | (Analogue interface in ATM and digital interface at the point of connection to the PSTN) | |
+| Embedded analogue signals & analogue interface parameters | Attenuation distortion | GNR (Note 3) | GNR | GNR | GNR | PGA (Notes 4, 5) [G.113, G.132, Q.552] | GNR |
+| | Crosstalk | GNR | GNR | GNR | GNR | PGA (Note 5) [Q.552] | GNR |
+| | Delay (Steady state) | PGA [G.114] | PGA [G.114] | PGA [G.114] | PGA [G.114] | PGA (Note 5) [G.113, G.114] | PGA [G.114] |
+| | Delay (Variation) | RFS (Note 6) | RFS | RFS | RFS | RFS (Note 5) | RFS |
+| | Dropout | GNR | GNR | GNR | GNR | GNR | GNR |
+| | Echo return loss | PGA [G.131] | GNR | GNR | GNR | PGA (Note 5) [G.113, G.131] | PGA [G.131] |
+| | Group delay | GNR | GNR | GNR | GNR | PGA (Note 5) [Q.552] | GNR |
+| | Gain hits | GNR | GNR | GNR | GNR | GNR | GNR |
+| | Listener echo | GNR | GNR | GNR | GNR | PGA (Note 5) [G.113, G.126] | GNR |
+| | Loss (Single frequency) | GNR (Note 7) | GNR (Note 7) | GNR (Note 7) | GNR (Note 7) | PGA (Note 5) [G.113] | GNR (Note 7) |
+| | Noise (impulse) | GNR | GNR | GNR | GNR | RFS (Note 5) | GNR |
+| | Noise (Quantization, including total distortion) | PGA [G.113] | GNR | GNR | GNR (Note 8) | PGA (Notes 5, 8) [G.113, Q.552] | GNR |
+| | Noise (Steady state) | GNR | GNR | GNR | GNR | PGA (Note 5) [G.113] | GNR |
+| | Phase hit (Analogue) | GNR | GNR | GNR | GNR | RFS | RFS |
+| | Phase jitter (Analogue) | GNR | GNR | GNR | GNR | RFS (Note 5) | RFS |
+| | Relative Level – Input | GNR | GNR | GNR | GNR | PGA (Note 5) [G.552] | GNR |
+| | Relative Level – Output | GNR | GNR | GNR | GNR | PGA (Note 5) [G.552] | GNR |
+| | Return loss [Looking into the port(s)] | GNR | GNR | GNR | GNR | PGA (Note 5) [G.113, G.131] | GNR |
+| | Signal clipping (Power) | PGA [G.712] | GNR | GNR | GNR | PGA (Note 5) [G.552] | GNR |
+
+**Table 1/G.176 (concluded)**
+
+| Parameter (Note 1) | ATM digital processing function (Figure 2) | ATM multiplex function (Digital interfaces) Figure 3) | ATM transport function (Digital interfaces) (Figure 4) | ATM switch function [PBX, local exchange & transit] (Digital interfaces) (Figure 5) | ATM switch function [PBX & local exchange] (Digital trunk & 2-wire analogue line interfaces) (Figure 6) | ATM Interworking unit function to narrowband PSTN (Figure 7) |
+|--------------------------------------|--------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|
+| | | | | | | (Analogue interface in ATM and digital interface at the point of connection to the PSTN) |
+| Signal clipping (Speech burst) | PGA [G.174] | GNR | GNR | GNR (Note 9) | PGA [G.174] | GNR |
+| Singing return loss | PGA [G.122] | GNR | GNR | GNR | PGA (Notes 5, 10) [G.113] | GNR |
+| Talker echo path loss | PGA [G.131] | GNR | GNR | GNR | PGA (Notes 5, 10) [G.113] | GNR |
+
+NOTE 1 – See Recommendation G.100 for parameter definitions.
+
+NOTE 2 – This column applies only to the analogue interfaces of an ATM switch which has 2-wire analogue line side and 4-wire digital trunk interfaces. The digital line side interface requirements are addressed in the column labelled ATM switch function (Digital interfaces).
+
+NOTE 3 – GNR: Guidance Not Required. The term used in Table 1 to indicate that the associated parameter should have negligible or no impact on the ATM functionality under consideration
+
+NOTE 4 – PGA: Provisional Guidance Available. The term used in Table 1 to indicate that the associated parameter must be considered in the context of transmission performance for end-to-end connections and that preliminary guidance is available.
+
+NOTE 5 – Note that this requirement is part of a line card specification and when a parameter value is developed it should appear in an ATM switch (including PBX) standard.
+
+NOTE 6 – RFS: Requires Further Study. The term used in Table 1 to indicate that the associated parameter must be considered in the context of transmission performance for end-to-end connections and that preliminary guidance is not currently available.
+
+NOTE 7 – While, strictly speaking, this entry could have been labelled RFS, there is a general underlying agreement that digital networks will not insert loss/gain unless it is part of a network element that is implementing this function as part of the loss transmission plan.
+
+NOTE 8 – This is not applicable unless the device performs transcoding.
+
+NOTE 9 – This is not applicable unless the device performs compression.
+
+NOTE 10 – This parameter will depend upon the assumptions made about how echo control will be handled in the ATM network. For example, echo control could be assumed to be totally controlled by: an active hybrid in a line card; an echo canceller in a line card; an echo canceller situated after the analogue signal is digitized but before the cells are generated; or by a digital speech processing device which operates on a cell stream and which may reside within or external to the terminating ATM local exchange or PBX. If industry agreement cannot be obtained to limit the number of operating configurations, then industry should agree upon appropriate values for each operating configuration.
+
+# ITU-T RECOMMENDATIONS SERIES
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of the ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communication |
+| Series Z | Programming languages |
\ No newline at end of file
diff --git a/marked/G/T-REC-G.177-199909-I_PDF-E/raw.md b/marked/G/T-REC-G.177-199909-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..ef5a112f2be6d9e014349ed2144c8a682fcf326b
--- /dev/null
+++ b/marked/G/T-REC-G.177-199909-I_PDF-E/raw.md
@@ -0,0 +1,625 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**G.177**
+
+(09/99)
+
+SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
+DIGITAL SYSTEMS AND NETWORKS
+
+International telephone connections and circuits –
+Transmission plan aspects of special circuits and
+connections using the international telephone connection
+network
+
+---
+
+**Transmission planning for voiceband services
+over hybrid Internet/PSTN connections**
+
+ITU-T Recommendation G.177
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS**
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 |
+| General definitions | G.100–G.109 |
+| General Recommendations on the transmission quality for an entire international telephone connection | G.110–G.119 |
+| General characteristics of national systems forming part of international connections | G.120–G.129 |
+| General characteristics of the 4-wire chain formed by the international circuits and national extension circuits | G.130–G.139 |
+| General characteristics of the 4-wire chain of international circuits; international transit | G.140–G.149 |
+| General characteristics of international telephone circuits and national extension circuits | G.150–G.159 |
+| Apparatus associated with long-distance telephone circuits | G.160–G.169 |
+| Transmission plan aspects of special circuits and connections using the international telephone connection network | G.170–G.179 |
+| Protection and restoration of transmission systems | G.180–G.189 |
+| Software tools for transmission systems | G.190–G.199 |
+| INTERNATIONAL ANALOGUE CARRIER SYSTEM | |
+| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 |
+| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 |
+| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 |
+| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 |
+| TESTING EQUIPMENTS | |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.600–G.699 |
+| DIGITAL TRANSMISSION SYSTEMS | |
+| TERMINAL EQUIPMENTS | G.700–G.799 |
+| DIGITAL NETWORKS | G.800–G.899 |
+| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 |
+
+*For further details, please refer to ITU-T List of Recommendations.*
+
+# **TRANSMISSION PLANNING FOR VOICEBAND SERVICES OVER HYBRID INTERNET/PSTN CONNECTIONS**
+
+## **Summary**
+
+This Recommendation provides transmission performance guidelines for voiceband services over networks that are an interconnection of an IP network (e.g. "the Internet") and the PSTN. As modern telecommunications systems continue to evolve, hybrid networks of various kinds will become more prevalent. This tendency, together with the reality that voiceband communications will be an important source of traffic on such networks, has led ITU-T to develop this Recommendation. The intent is to provide to a wide audience a set of principles on transmission performance aspects of hybrid Internet/PSTN connections.
+
+### **Source**
+
+ITU-T Recommendation G.177 was prepared by ITU-T Study Group 12 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on 30 September 1999.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation the term *recognized operating agency (ROA)* includes any individual, company, corporation or governmental organization that operates a public correspondence service. The terms *Administration*, *ROA* and *public correspondence* are defined in the *Constitution of the ITU (Geneva, 1992)*.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2000
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+###### Page
+
+| | | |
+|-------|-----------------------------------------------------------|----|
+| 1 | Scope, purpose and application..... | 1 |
+| 1.1 | Scope..... | 1 |
+| 1.2 | Purpose..... | 1 |
+| 1.3 | Application..... | 1 |
+| 2 | Terminology..... | 2 |
+| 3 | Acronyms and Abbreviations..... | 2 |
+| 4 | References..... | 4 |
+| 5 | Performance of hybrid Internet/PSTN connections ..... | 5 |
+| 6 | Transmission channel characteristics of IP networks ..... | 7 |
+| 7 | Speech performance (end-to-end)..... | 7 |
+| 7.1 | Speech coder performance..... | 8 |
+| 7.1.1 | E-Model equipment impairment factors (eifs) ..... | 9 |
+| 7.1.2 | Tandeming performance..... | 9 |
+| 7.1.3 | Other considerations for speech coders ..... | 9 |
+| 7.2 | Effects of transmission errors and packet loss..... | 9 |
+| 7.2.1 | Bit errors ..... | 10 |
+| 7.2.2 | Packet loss ..... | 10 |
+| 7.3 | Loudness ratings and terminal characteristics ..... | 10 |
+| 7.4 | Delay and echo..... | 11 |
+| 7.4.1 | Delay..... | 11 |
+| 7.4.2 | Delay variation..... | 12 |
+| 7.4.3 | Echo control..... | 13 |
+| 7.5 | Temporal (syllable) clipping..... | 14 |
+| 7.6 | Environmental (acoustic) noise..... | 14 |
+| 7.7 | Idle channel noise ..... | 14 |
+| 7.8 | Noise contrast and comfort noise..... | 14 |
+| 7.9 | Bandwidth..... | 15 |
+| 7.10 | Stability loss..... | 15 |
+| 7.11 | Distortion ..... | 15 |
+| 8 | Speech transmission planning in hybrid networks..... | 15 |
+| 9 | Non-voice transmission (end-to-end) ..... | 16 |
+
+
+
+# **TRANSMISSION PLANNING FOR VOICEBAND SERVICES OVER HYBRID INTERNET/PSTN CONNECTIONS**
+
+*(Geneva, 1999)*
+
+# **1 Scope, purpose and application**
+
+## **1.1 Scope**
+
+This Recommendation provides transmission planning guidelines for voiceband services over connections that include Internet and PSTN segments, i.e. hybrid Internet/PSTN connections. In particular, "voice over the Internet" or "Voice over Internet Protocol" (VoIP) connections are considered, where at least part of the connection is over an Internet Protocol (IP) network. PSTN-only connections (i.e. connections that begin, end, and are carried only on the PSTN) are considered as the reference against which the performance of other connections is compared.
+
+This Recommendation provides end-to-end transmission performance guidance for hybrid Internet/PSTN connections carrying voiceband services. When one of the terminals is attached to an IP network, it is assumed that this terminal has functionality defined in Recommendation H.323. (The terminal need not be an H.323 terminal, but is assumed to have that functionality.) To support these end-to-end guidelines, guidance is given for interworking functions between Internet and PSTN. The functionality provided by Internet/PSTN gateways presents special performance issues that must be addressed to ensure high quality service. Protocol details of IP and higher level protocols (e.g. TCP, UDP, RTP, RSVP) are not considered in this Recommendation. Rather, the impact on performance of voiceband services of the packetized aspects of IP networks, such as delay associated with packet assembly, lost or discarded packets, is of primary interest here.
+
+The importance of user expectations for voiceband services on hybrid Internet/PSTN networks is recognized. However, this Recommendation does not address this subject, nor does it offer detailed suggestions of how to assess the impact of user expectations on the acceptability of these services. Additional guidance on many of these issues is available in ITU-T P-series and G.100-series Recommendations.
+
+This Recommendation also includes discussion of issues associated with the interworking functions provided by Internet/PSTN gateways.
+
+## **1.2 Purpose**
+
+This Recommendation provides guidance on basic telephony issues involved in providing voiceband services over hybrid Internet/PSTN connections. This information will also be useful to equipment manufacturers, VoIP service providers, Internet Service Providers (ISPs), software developers, and PSTN providers where service goes over a gateway to IP networks. Traditional PSTN engineers will be familiar with the telephony aspects of this Recommendation, but will find useful the material on Internet-specific features of voiceband services over connections that incorporate an Internet segment.
+
+## **1.3 Application**
+
+It is intended that the guidelines provided in this Recommendation be applied by equipment manufacturers, VoIP service providers, ISPs, software developers, and PSTN providers. Those who provide services where the PSTN interconnects with IP networks through a gateway should find this information useful as they design equipment, software and services for voiceband services over
+
+hybrid Internet/PSTN connections. Application of the guidelines herein by equipment manufacturers, VoIP service providers, Internet Service Providers, software developers, and PSTN providers should enhance the quality of voiceband services delivered over hybrid Internet/PSTN connections. Furthermore, if widespread customer acceptance of VoIP service is desired, the resulting voiceband service quality should approach that of the PSTN.
+
+The guidance in this Recommendation applies to situations/connections where at least part of the connection is on an IP network. Special attention focussed on the "Gateway/Inter-Working Function" (which provides the essential interworking capabilities of these hybrid connections). A major application of this Recommendation will be Internet Telephony where the terminal (e.g. a PC) enjoys H.323 stack functionality. As noted above, this Recommendation will use PSTN-only connections as the reference against which the performance of other connections will be compared.
+
+This Recommendation applies to connections where the data transfer phase occurs over hybrid Internet/PSTN connections. Issues of call set-up, number translation (between PSTN and IP numbering), etc., are not considered in this Recommendation.
+
+This Recommendation applies to IP networks that provide voice telephony in accordance with any of the scenarios described in clause 5, Performance of hybrid Internet/PSTN connections. This Recommendation contains general information on end-to-end quality and the way in which quality is affected by various components in the VoIP system. A description of the relationship of the performance of terminals and of the network is also included.
+
+# 2 Terminology
+
+This Recommendation defines the following terms:
+
+**2.1 hybrid PSTN/Internet:** A connection that includes at least one segment where traffic is carried on the PSTN and at least one segment where traffic is carried on a network that uses the Internet Protocol suite.
+
+**2.2 gateway/IWF:** A connection element that interconnects different networks and performs the necessary translation between the protocols used on those networks.
+
+**2.3 interwork:** The ability of two networks to be connected and transfer traffic from one to the other.
+
+**2.4 H.323-based terminal:** A terminal that is either dedicated (e.g. a telephone set) or general purpose (e.g. a computer running an application that performs the terminal function) and that:
+
+- is intended for connection to an IP network;
+- provides the functionality defined in Recommendation H.323.
+
+# 3 Acronyms and Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|-------|---------------------------------------------|
+| %GoB | Per cent Good-or-Better |
+| %PoW | Per cent Poor-or-Worse |
+| ACELP | Algebraic-Code-Excited Linear-Prediction |
+| ACR | Absolute Category Rating |
+| ADPCM | Adaptive Differential Pulse Code Modulation |
+| ADSL | Asymmetric Digital Subscriber Line |
+| ATM | Asynchronous Transfer Mode |
+
+| | |
+|------------------|------------------------------------------------------------------|
+| BER | Bit Error Ratio |
+| CNG | Comfort Noise Generator |
+| CS-ACELP | Conjugate Structure Algebraic-Code-Excited Linear-Prediction |
+| dB(A) | dB SPL, A-weighted |
+| dBm | decibels referred to 1 milliwatt |
+| dBm0p | dBm as measured at the zero dBr point, weighted psophometrically |
+| dBmp | dBm, psophometrically weighted |
+| DTMF | Dual-Tone Multi-Frequency |
+| EC | Echo Canceller |
+| eif | E-Model equipment impairment factor |
+| ERL | Echo Return Loss |
+| GSM | Global System for Mobile communications |
+| GSM EFR | GSM Enhanced Full Rate Speech Coder |
+| GSM FR | GSM Full Rate Speech Coder |
+| GSM HR | GSM Half Rate Speech Coder |
+| GW | Gateway |
+| IP | Internet Protocol |
+| ISDN | Integrated Services Digital Network |
+| ISP | Internet Service Provider |
+| IWF | Interworking function |
+| LAN | Local Area Network |
+| LD-CELP | Low-Delay Code-Excited Linear Prediction |
+| PCME | Packetized Circuit Multiplication Equipment |
+| PPP | Point-to-Point Protocol |
+| PSTN | Public Switched Telephone Network |
+| QoS | Quality of Service |
+| RLR | Receive Loudness Rating |
+| RSVP | Resource Reservation Set-Up Protocol |
+| RTP | Real-Time Transport Protocol |
+| SCN | Switched Communications Network |
+| SLR | Send Loudness Rating |
+| SPL | Sound Pressure Level |
+| STU | Secure Telephone Unit |
+| TCL w | Weighted Terminal Coupling Loss |
+| TCP | Transmission Control Protocol |
+| TDD | Telecommunications Terminal for the Deaf |
+| TTY | Teletype |
+
+| | |
+|------|---------------------------------------------------------|
+| UDP | User Datagram Protocol |
+| VBD | Voiceband Data |
+| VDSL | Very High Speed Digital Subscriber Line |
+| VoIP | Voice over Internet Protocol |
+| VTOA | Voice and Telephony over ATM |
+| xDSL | ADSL, VDSL and other Digital Subscriber Line Techniques |
+
+# 4 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
+
+- ITU-T Recommendation G.101 (1996), *The transmission plan*.
+- ITU-T Recommendation G.107 (1998), *The E-model, a computational model for use in transmission planning*.
+- ITU-T Recommendation G.108 (1999), *Application of the E-model – A planning guide*.
+- ITU-T Recommendation G.109 (1999), *Definition of categories of speech transmission quality*.
+- ITU-T Recommendation G.113 (1996), *Transmission impairments*.
+- ITU-T Recommendation G.114 (1996), *One-way transmission time*.
+- ITU-T Recommendation G.116 (1999), *Transmission performance objectives applicable to end-to-end international connections*.
+- ITU-T Recommendation G.131 (1996), *Control of talker echo*.
+- ITU-T Recommendation G.168 (1997), *Digital network echo cancellers*.
+- ITU-T Recommendation G.173 (1993), *Transmission planning aspects of the speech service in digital public land mobile networks*.
+- ITU-T Recommendation G.174 (1994), *Transmission performance objectives for terrestrial digital wireless systems using portable terminals to access the PSTN*.
+- ITU-T Recommendation G.175 (1997), *Transmission planning for private/public network interconnection of voice traffic*.
+- ITU-T Recommendation G.176 (1997), *Planning guidelines for the integration of ATM technology into networks supporting voiceband services*.
+- CCITT Recommendation G.711 (1988), *Pulse code modulation (PCM) of voice frequencies*.
+- ITU-T Recommendation G.723.1 (1996), *Speech coders: Dual rate speech coder for multimedia communications transmitting at 5.3 and 6.3 kbit/s*.
+- CCITT Recommendation G.726 (1990), *40, 32, 24, 16 kbit/s adaptive differential pulse code modulation (ADPCM)*.
+- CCITT Recommendation G.728 (1992), *Coding of speech at 16 kbit/s using low-delay code excited linear prediction*.
+
+- ITU-T Recommendation G.729 (1996), *Coding of speech at 8 kbit/s using Conjugate-Structure Algebraic-Code-Excited Linear-Prediction (CS-ACELP)*.
+- ITU-T Recommendation G.729 Annex A (1996), *Reduced complexity 8 kbit/s CS-ACELP speech codec*.
+- CCITT Recommendation G.764 (1990), *Voice packetization – Packetized voice protocols*.
+- ITU-T Recommendation H.225.0 (1998), *Call signalling protocols and media stream packetization for packet-based multimedia communication systems*.
+- ITU-T Recommendation H.245 (1998), *Control protocol for multimedia communication*.
+- ITU-T Recommendation H.323 (1998), *Packet-based multimedia communications systems*.
+- ITU-T Recommendation P.11 (1993), *Effect of transmission impairments*.
+- ITU-T Recommendation P.56 (1993), *Objective measurement of active speech level*.
+- ITU-T Recommendation P.79 (1993), *Calculation of loudness ratings for telephone sets*.
+- CCITT Recommendation P.82 (1988), *Method for evaluation of service from the standpoint of speech transmission quality*.
+- ITU-T Recommendation P.310 (1996), *Transmission characteristics for telephone-band (300-3400 Hz) digital telephones*.
+- ITU-T Recommendation P.561 (1996), *In-service, Non-intrusive measurement device – Voice service measurements*.
+- ITU-T Recommendation P.800 (1996), *Methods for subjective determination of transmission quality*.
+- ITU-T Recommendation P.861 (1998), *Objective quality measurement of telephone-band (300-3400 Hz) speech codecs*.
+- RFC 1889, *RTP: A Transport Protocol for Real-Time Applications*.
+- RFC 2205, *Resource ReSerVation Protocol (RSVP) – Version 1 Functional Specification*.
+- RFC 2212, *Specification of Guaranteed Quality of Service*.
+
+# 5 Performance of hybrid Internet/PSTN connections
+
+Figure 1 shows specific Internet/PSTN connection arrangements that are of interest in this Recommendation. The terminals attached to the Internet are assumed to have H.323 functionality from the point of view of speech transmission. These terminals may be connected to the Internet via a direct connection (e.g. Ethernet, Token Ring, etc.) or a dial-up connection (e.g. modem and PPP link). The Internet and PSTN sections are connected through a gateway. For convenience, this gateway is designated with a single box in Figure 1. In practice, the gateway may be composed of multiple pieces of equipment, each with specialized functions. Performance aspects of the gateway are of particular interest here.
+
+
+
+Diagram illustrating four specific connection types (1, 2, 3, 4) between H.323 Terminals and Phones via an IP Network and a Gateway connected to an SCN. The diagram shows two large ovals representing the IP Network and the SCN, connected by a central Gateway box. On the left, two boxes labeled 'H.323 Term.' are connected to the IP Network oval. On the right, two boxes labeled 'Phone' are connected to the SCN oval. Four numbered arrows indicate different connection paths: (1) from an H.323 Term. through the IP Network, Gateway, and SCN to a Phone; (2) from a Phone through the SCN, Gateway, and IP Network to an H.323 Term.; (3) from a Phone through the SCN, Gateway, and IP Network to another H.323 Term.; and (4) from an H.323 Term. through the IP Network, Gateway, and SCN to another Phone. A small text 'T1211660-99' is in the bottom right corner of the diagram area.
+
+NOTE – Four connection types are shown. See text for details.
+
+**Figure 1/G.177 – Specific connection types of interest in this Recommendation**
+
+The specific functions of the gateway will depend on whether the direction of transmission is from the Internet to the PSTN or vice versa. In particular, the functions in the gateway include (but are not limited to):
+
+- Internet → PSTN
+ - Packet disassembly (including "IP stack")
+ - Speech decoder (including error concealment, comfort noise, silence insertion, etc.)
+ - Management or regulation of delay variation
+ - Echo cancellation.
+- PSTN → Internet
+ - Speech encoder (including silence removal, comfort noise decisions, etc.)
+ - Packet assembly (including "IP stack")
+ - Management or regulation of delay variation.
+
+Four connection arrangements are considered in this Recommendation, each of which is shown in Figure 1. They are:
+
+- 1) H.323 → Phone (H.323 → Internet → PSTN → Phone)
+- 2) Phone → H.323 (Phone → PSTN → Internet → H.323)
+- 3) Phone → Phone (Phone → PSTN → Internet → PSTN → Phone)
+- 4) H.323 → H.323 (H.323 → Internet → PSTN → Internet → H.323)
+
+Each of these connection arrangements requires at least one use of the gateway. Hence, connections that are purely PSTN-based or are strictly H.323-to-H.323 using only the Internet are not the subject of this Recommendation.
+
+- This Recommendation describes factors that play a role in determining end-to-end QoS and the parameters by which QoS is characterized.
+
+# 6 Transmission channel characteristics of IP networks
+
+In many respects, transmission in IP networks is similar to transmission of voiceband services over packetized systems and networks. Appendix I/G.764 gives an introduction to packetized systems and the performance issues associated with them.
+
+Transmission in IP networks is accomplished by assembling multiple bytes into packets. These packets include headers with essential information such as source and destination for the packet, which is added at the transport and network layers. The size of the payload and of the header may vary, depending on the application and on the nature of the protocols being used. Communication between two endpoints is via a "data stream" (somewhat analogous to a connection in a connection-oriented network such as the PSTN), which usually consists of multiple packets. Each of the packets from a given source may take different routes to a given destination. As a consequence, packets from a given data stream may arrive at the destination in an order that is different from the order in which they were transmitted (i.e. the packets arrive out of sequence). Protocol features such as sequence numbers or time stamps allow the packets to be reassembled in the proper order at the destination.
+
+Proper sequencing of the packets in the data stream is the responsibility of the higher layers in the protocol stack and is not part of the IP protocol. When an application requires the arriving packets to be used in proper sequence, sufficient delay must be included to allow integration of late packets. For applications such as speech communications, where end-to-end delays as short as possible must be maintained, it may be necessary to declare "very late" packets as lost in order to achieve acceptable delay. The tradeoff between long delay (which may result in higher speech transmission quality, but will increase the difficulty of conversation) and dropped packets (which will result in lower speech transmission quality, but will ease the ability to have an interactive conversation) must be given careful consideration when designing VoIP services.
+
+# 7 Speech performance (end-to-end)
+
+Many factors influence the overall end-to-end speech quality of VoIP services. These factors include choice of speech coder, delay (and any associated echo), overall level (loudness), etc. Important factors are considered, in turn, in this clause. The widespread use of digital wireless terminals (and associated speech coding) in the PSTN, and the interaction of wireless systems with speech processing elements in VoIP systems is an area for further study.
+
+A useful tool for assessing the relative impact of transmission planning decisions on speech performance is the E-Model. The E-Model has been included in various ITU-T Recommendations on transmission planning. In particular, the E-Model is the subject of Recommendation G.107.
+
+The E-Model introduces the notion of "equipment impairment factor" (eif), which has shown great utility in capturing the effects on transmission performance of new speech signal processing devices. Recommendation G.113 outlines the eif methodology.
+
+Recommendation G.109 provides useful guidance on categories of voice quality, using E-Model R-values, and their use in speech communications.
+
+Overall assessment of the speech transmission quality of a hybrid Internet/PSTN service is advisable. While it is important to assess the speech quality of various system components (e.g. speech coders, echo cancellers), the cumulative effects of impairments from multiple speech signal processing devices will be the limiting factor in determining user acceptability of a new service. Recommendation P.800 provides general guidance on conducting subjective evaluations of speech transmission quality. Recommendation P.830 provides detailed guidance for evaluation of speech codecs.
+
+Objective measures of speech quality may also be appropriate. Recommendation P.861 describes one such objective measurement algorithm for evaluation of speech codecs. Application of
+
+Recommendation P.861 for other purposes should be made with caution. The scope of Recommendation P.861 must be consulted for guidance.
+
+NOTE – ITU-T is studying the issue of what new or modified objective techniques can be applied to situations relevant to VoIP. In particular, Appendix I/P.861 provides a method that is quite robust with respect to frame erasure.
+
+## 7.1 Speech coder performance
+
+Transmission in IP networks is characterized by periods of relatively error-free transmission, punctuated by occasional bursts of lost frames. These lost frames occur when packets are lost in transit or are discarded due to late arrival as part of a delay management strategy at the destination. Thus, speech coders for VoIP applications must be evaluated in terms of their performance when multiple sequential frames are lost or discarded. Some VoIP applications are also likely to encounter high ambient acoustic noise at the sending end of the connection (e.g. when one of the endpoints is a personal computer). Hence, it is also desirable that the speech coder shows robust performance in the presence of acoustic background noise.
+
+The performance effect caused by lost or missing packets at the destination, and the associated effects on low bit rate speech coders, is of particular concern. In many applications, it will be necessary to include multiple frames of coded speech in a single IP packet. Thus, speech coders for VoIP applications should be robust with respect to loss of multiple sequential frames. Accordingly, it is recommended that one of the G.700-series codecs be used. These coders have been tested extensively and have been shown to have good quality and to be robust in their performance under a wide range of conditions. In particular, G.723.1, G.728, and G.729 have been evaluated for their performance under conditions that lead to random frame loss as well as "bursty" frame loss. However, they have not been evaluated thoroughly for one effect that may be peculiar to IP transmission, viz., the effect of loss of multiple sequential frames, either in isolation or in "bursty" situations. H.323 makes specific provisions for G.711, G.723.1, G.728, and G.729 (including Annexes A and B).
+
+Opinion tests of the coder that is selected for VoIP applications should indicate that (individually) its overall quality under error-free conditions should be no worse than that of 32 kbit/s ADPCM (Recommendation G.726) coder. The 8 kbit/s ITU-T CS-ACELP coder (G.729 and Annex A/G.729) satisfies this requirement, although its interworking performance with other coding technologies is different from that of Recommendation G.726. For this reason, the provisional eif assigned to G.729 and Annex A/G.729 is higher than the established eif for G.726 at 32 kbit/s.
+
+Under conditions of bursty 3% missing frames, it is recommended that the proportion of Poor-or-Worse judgements should not increase by more than 0.1 relative to that of 32-kbit/s ADPCM for the error-free case. Similar requirements for loss of multiple sequential frames, as noted above, have not been determined.
+
+The use of speech coders that are already in wide use in digital wireless systems (or newer coders that are under consideration for such applications) should be considered for use in VoIP systems. While the transmission characteristics of wireless channels and those of IP systems may differ, speech coders for wireless applications are designed to be robust with respect to coded frames that have been corrupted, declared unusable, and discarded. Hence, they exhibit properties that are desirable in a speech coder for VoIP applications. Moreover, since it can be expected that an increasing number of voice calls will include an IP/PSTN gateway and a wireless terminal, it is desirable that both systems should be using the same speech coder. In particular, it is recommended that, when possible, only one encode/decode of speech be performed. To achieve this, it will be necessary to establish appropriate methods for communicating the type of codec in use so that the IP/PSTN gateway does not do speech encoding or decoding in these situations. The objective is to eliminate tandem processing by speech coders whenever possible.
+
+### **7.1.1 E-Model equipment impairment factors (eifs)**
+
+The subjective performance of a speech coder is conveniently captured by the Equipment Impairment Factor (eif) of the E-Model (see Recommendation G.113 for a summary of these eifs and methods for extracting eifs from subjective data). E-Model eifs are empirically (subjectively) determined and provide a useful metric for comparing speech coders on a scale of subjective performance (i.e. speech quality). The eif for a given codec captures the subjective effect of speech impairments that are introduced by the speech codec. Performance of multiple codecs (whether of the same or of different type) arranged in tandem is an important consideration for the overall speech quality of a connection. The eif also captures the effects of such arrangements. All other things being equal, a lower eif is better than a higher eif. For speech coders with equal eifs, other considerations (such as delay or bit rate) may play decisive roles in choice of a speech coder. A current list of eif assignments for many speech codecs, including those that are available as options in Recommendation H.323, is found in Appendix I/G.113.
+
+The processing delay associated with a codec is also captured in the E-Model, but is not part of the eif.
+
+### **7.1.2 Tandeming performance**
+
+In some calling scenarios, the speech signal will be subjected to encodings by more than one speech codec. An obvious example is the H.323 → H.323 example illustrated in Figure 1. The transmission path passes through two gateways. Hence, speech will be encoded and decoded two times by a speech codec. Other important cases will be calls where one of the voice terminals is a wireless terminal, digital answering machine, or digital voice mail system. In these cases, the ability of the VoIP codec to operate well (from a subjective standpoint) in tandem with the other codec must be given proper consideration.
+
+In general, tandeming of speech codecs leads to an overall degradation in speech quality. If equipment impairment factors are available, the E-Model (Recommendation G.107) may be used to assess the potential impact of multiple speech codecs in the transmission path.
+
+Use of a G.711 codec in the VoIP terminal will lead to toll quality results on the PSTN and ISDN and normal digital wireless system performance when terminated in a digital wireless network.
+
+### **7.1.3 Other considerations for speech coders**
+
+As noted above, use of speech codecs has a number of possible negative effects on voice services. Designers of VoIP services using speech coders should consider the requirements of such services as they build their networks. In particular, the effects of speech coding on the following applications should be considered:
+
+- Speaker Recognition – Speech codecs should not have an adverse affect on the ability of humans or machines to recognize and identify a talker.
+- Speech Recognition – Speech codecs should not have an adverse affect on the ability of humans or machines to recognize speech content.
+- Text-to-Speech (TTS) – The artificial speech generated by speech production systems may not have the same characteristics as real speech. Since modern speech codecs exploit such characteristics, it is possible that coding of artificial speech may generate unexpected impairments.
+
+## **7.2 Effects of transmission errors and packet loss**
+
+For VoIP applications, two primary types of transmission errors may occur:
+
+- 1) bit errors on the transmission facility; and
+- 2) lost or discarded IP packets.
+
+### 7.2.1 Bit errors
+
+Bit errors may occur on transmission facilities. As a result, IP packets arriving at a destination may be corrupted. The IP layer will detect corrupted IP headers, but will not detect errors that occur in the payload of the IP packet, i.e. the coded speech. Higher level protocols must detect corrupted speech frames. Whether such detection and correction is handled at the Transport Layer or at the Application Layer, and how detection and correction of errors is achieved, may ultimately affect the overall quality of speech transmission.
+
+### 7.2.2 Packet loss
+
+A potentially more severe performance issue is that of lost or discarded IP packets. An IP packet may be lost due to congestion in the IP network. An IP packet may also be discarded at the destination. This would occur, for example, when a packet is sufficiently late that the destination declares the packet lost. Discarding packets that are very late is preferable to having the destination increase delay and delay variation by potentially waiting for long time periods (see 7.4, Delay and echo).
+
+Loss of a single IP packet will result in loss of one or more coded speech frames, depending on the speech coder in use and the number of frames per packet. As noted above, the speech coder should be robust with respect to loss of coded frames. In particular, if multiple frames are assembled into an IP packet, the performance of the speech coder must be assessed under frame loss conditions that reflect those of the network in use. The impact of large percentages of frame loss (as much as 20-30%) should be assessed.
+
+## 7.3 Loudness ratings and terminal characteristics
+
+Two important characteristics of telephone sets are the Send Loudness Rating (SLR) and the Receive Loudness Rating (RLR), as defined in Recommendation P.79. SLR and RLR define, respectively, the acoustic-to-electric efficiency of the transmitter and the electric-to-acoustic efficiency of the receiver. Transmitters and receivers for VoIP applications may not be typical telephone voice terminals. Other possibilities include headsets with microphone, stand-alone microphones together with separate loudspeakers, and built-in microphone and speakers (as available in laptop computers).
+
+Handsets and headsets provide specified means to control input and output levels. Usually the frequency characteristics are also well suited for telephony. Acoustic echo is also less of a problem since the acoustic coupling loss is generally over 50 dB. Handsets and headsets typically provide significantly greater background noise rejection than stand-alone microphones. When stand-alone microphones and speakers are used in hands-free situations, the performance is highly dependent on several factors, including the linearity of the equipment and their positioning. The acoustic coupling also need proper echo-control in the form of half-duplex switching solutions or full-duplex echo cancellation solutions. The echo canceller must cope with background noise (e.g. office environment) and double-talk conditions (when users speak at the same time), and cancel the echo in single-talk (normal working) conditions. Poor echo performance mainly affects the user at the other end of the connection.
+
+The sending and receiving frequency response of microphones, loudspeakers, ear-pieces and headsets should be matched to the audio bandwidth used. For narrow-band telephony the bandwidth should be [300-3400] Hz with a flat frequency response (within $\pm 3$ dB).
+
+While Loudness Ratings of non-traditional voice terminals are, in principle, easy to specify, the measurement procedures to verify compliance have not been defined. General guidance can be provided. Active speech levels in the network have an average of about $-20$ dBm, with a standard deviation of about 5 dBm. These values usually produce acoustic levels at the output of a "typical" telephone receiver that are centred at about 80 dB SPL. A "typical" talker should produce an active
+
+speech level (as measured according to Recommendation P.56) of about $-20$ dBm at the $0$ dBr point, which should produce an acoustic level of about $80$ dB SPL at the output of the receiver.
+
+When traditional telephone sets or handsets are used, they should meet the requirements in Recommendation P.310. New work is under way in ITU-T to define performance characteristics for a digital voice terminal intended for use in packetized systems.
+
+## 7.4 Delay and echo
+
+Extremely long transmission times will result in difficulty in conducting interactive conversations. As delay increases, interaction between users will degenerate to "push to talk" or "over and out" style of conversation. If widespread acceptance and use of IP-based voice services is desired, these situations should be minimized.
+
+### 7.4.1 Delay
+
+In modern digital telecommunication networks, delay is a key performance parameter whose increase should be minimized. Although the delay of IP networks may exceed the typical delay of the PSTN, the degradation caused by additional delay might be compensated for by benefits provided by new network and service capabilities. These tradeoffs need to be quantified.
+
+Delay can have two effects on voice performance. Firstly, it increases the subjective effect of any echo impairment. Secondly, as indicated in Recommendation G.114, even when echo is controlled, one-way delays above $150$ ms can interfere with the dynamics of voice conversation, depending upon the type of conversation and degree of interaction. Recommendations G.114 and G.131 and Annex A/G.173 give additional information regarding effects of delay and echo.
+
+In addition, delay can impair the performance of particular voiceband data applications, some applications being even more sensitive to the delay than voice applications. Total delay of hybrid Internet/PSTN networks should be limited, even with the use of echo control. Recommendation G.114 should be consulted for additional information.
+
+#### 7.4.1.1 Codec delay
+
+Modern speech codecs operate on collections of speech samples known as frames. Each input frame is processed into a compressed frame. The coded speech frame is not generated until all speech samples in the input frame have been collected by the encoder. Thus, there is a delay of one frame before processing can begin. In addition many coders also look into the succeeding frame to improve compression efficiency. The length of this advance look is known as the look-ahead time of the coder. The time required to process an input frame is assumed to be the same as the frame length since efficient use of processor resources will be accomplished when an encoder/decoder pair (or multiple encoder/decoder pairs operating in parallel on multiple input streams) fully uses the available processing power (evenly distributed in the time domain). Thus, the delay through an encoder/decoder pair is normally assumed to be:
+
+$$2 \times \text{frame size} + \text{look-ahead}$$
+
+If the output facility is running at the same rate as the speech codec (e.g. an $8$ kbit/s facility for G.729), then an additional frame of delay is incurred when clocking the compressed frame to the facility. Thus, the maximum delay attributable to codec-related processing in conventional systems (i.e. the PSTN) is:
+
+$$3 \times \text{frame size} + \text{look-ahead}$$
+
+If the output facility is an IP network, then the frame output by the encoder will instantaneously be dropped into an IP packet. The additional delay required for IP packet assembly and presentation to the underlying link layer will depend on the link layer. When the link layer is a LAN (e.g. Ethernet), this additional time may be quite small.
+
+If multiple speech frames are grouped together into a single IP packet, further delay is added to the speech signal. This delay will be the duration of one extra speech frame for each additional speech frame added to the IP packet:
+
+$$(N + 1) \times \text{frame size} + \text{look-ahead}$$
+
+where N is the number of frames in each packet.
+
+#### 7.4.1.2 IP terminal buffering delay
+
+Audio cards and telephone cards in PCs usually include large internal buffers, in order to provide a fixed rate interface to A/D and D/A converter and an asynchronous interface to the application layer.
+
+Additionally, modems and network adapters use internal buffers to increase network access efficiency. They have been optimized for data transmission where delay is not a problem, but this optimization may not be appropriate for voice transmission where delay is a critical issue.
+
+There are also software buffering delays. Application or device drivers can store large amounts of data in order to process them easily and efficiently or to manage the delay jitter in received packets.
+
+#### 7.4.1.3 H.323 packetization/buffering delays
+
+Packetization delay may be introduced while packets are being constructed. Buffering delay may be introduced when they are being disassembled.
+
+Packetization delay is the time required to collect enough information to fill a packet. When fixed length packets are used with a frame-oriented codec, packetization can introduce an additional delay if the packet length differs from the frame length of the codec.
+
+Buffering delay is due to queuing in the receiver and is usually used to compensate for network jitter. Voice playback requires equally spaced (in time) packets but network delays are variable, thus the receiver must delay packets that arrive early to synchronize them with those arriving later.
+
+#### 7.4.1.4 Network transmission delays
+
+Transmission delay is the time spent by packets to reach their destination during transmission through the network. Components of network delay include:
+
+- the transmission delay, introduced by sending a packet over a link (e.g. sending a 256 byte packet over a 64 kbit/s link takes 32 ms);
+- the propagation delay, due to signal propagation over physical link. This delay is usually negligible if links are shorter than 1000 km;
+- the node delay, due to router queuing and processing of packets;
+- the protocol delay, due to packet retransmissions (if used, e.g. for TCP) or network access (e.g. CSMA-CD for Ethernet);
+- gateway delay, introduced by interconnection between networks (e.g. packet disassembly/assembly and speech coding/decoding).
+
+Network transmission delays may be negligible in fixed SCNs. However, significant transmission delays may be encountered in data networks (e.g. modem links or IP networks).
+
+### 7.4.2 Delay variation
+
+Packetized transmission systems exhibit variable delay in packet delivery times. Delay variation may have a negative impact on speech transmission quality. Depending on the nature of delay variations, the result may be experienced as time warping in speech or as impairments associated with lost speech packets.
+
+Delay variations especially affect the performance of modems with auto-ranging echo cancellers. Accordingly, a guideline for limiting delay variation is desirable and is for further study.
+
+### 7.4.3 Echo control
+
+Current assessment of delay in hybrid Internet/PSTN connections indicates that echo control is required for all types of calls. Control of echo from the PSTN should be provided in the gateway between the IP network and the PSTN.
+
+The H.323-based terminal on the IP network should control echo from that terminal. Echo from a four-wire H.323-based terminal will be primarily acoustic.
+
+#### 7.4.3.1 Echo from H.323-based terminals
+
+Figure 2 illustrates the echo path that may arise at the H.323-based terminal. When the terminal is using a microphone and loudspeaker as the transmitter and receiver, the echo will be due to acoustic coupling between transmitter and receiver. The existing PSTN infrastructure probably will not provide adequate echo protection if the acoustic coupling loss in the terminal is too low and the delay is too high. Recommendation H.225.0 indicates that control of acoustic echo from the H.323 terminal is the responsibility of the terminal. In order to provide echo protection all H.323-based terminals should meet the Weighted Terminal Coupling Loss ( $TCL_w$ ) objective of 45 dB, as is specified for digital wireline terminals in Recommendation P.310. Such acoustic isolation may be achieved relatively easily in standard handset terminals by careful design. However, in hands-free operation (e.g. microphone and speaker), other more complex techniques may have to be used. For example, introduction of advanced echo control technology capable of increasing acoustic isolation in hands-free terminals may be needed (standard echo cancellers may not be capable of providing sufficient isolation in a non-linear acoustic environment).
+
+
+
+The diagram shows a sequence of components: H.323, Internet, GW, PSTN, End Office, and Phone. A signal path is shown from the H.323 terminal, through the Internet, Gateway (GW), PSTN, and End Office to the Phone. A return path is shown from the Phone, through the End Office, PSTN, and GW back to the H.323 terminal. A curved arrow at the H.323 terminal indicates an acoustic echo path from the receiver back to the transmitter. The diagram is labeled T1211670-99.
+
+Diagram of acoustic echo path from H.323 terminal.
+
+Figure 2/G.177 – Acoustic echo generated at the 4-wire H.323 terminal
+
+#### 7.4.3.2 Echo from the PSTN
+
+Figure 3 illustrates the echo path that arises at the PSTN end of the connection due to a poor impedance match at the 4-to-2 wire conversion point. In this configuration an echo canceller is applied in the Interworking Function to control echo. The echo cancelling function may, in practice, be implemented at any location within the system. However, practical considerations (i.e. capabilities of existing echo cancellers) indicate that the appropriate location is in the gateway.
+
+
+
+The diagram shows a sequence of components: H.323, Internet, GW, EC (Echo Canceller), PSTN, End Office, and Phone. A signal path is shown from the H.323 terminal, through the Internet, Gateway (GW), Echo Canceller (EC), PSTN, and End Office to the Phone. A return path is shown from the Phone, through the End Office, PSTN, EC, and GW back to the H.323 terminal. A curved arrow at the End Office indicates an echo path from the receiver back to the transmitter. The diagram is labeled T1211690-99.
+
+Diagram of echo canceller deployment to control echo from the PSTN.
+
+Figure 3/G.177 – Example of echo canceller deployment to control echo from the PSTN
+
+Based on the existing PSTN infrastructure, the gateway should provide echo cancellation. It is likely that such echo cancellers will, in some configurations, be working in tandem with the PSTN echo control devices. This should not degrade the overall echo control function in the connection. In addition, effects of interaction of echo cancellers in the gateway with signal processing devices in the PSTN (e.g. PCME or conference bridges) is under study in ITU-T.
+
+Recommendation G.168 provides specifications for digital network echo cancellers. At a minimum, echo cancellers deployed in the gateway should meet these requirements.
+
+#### **7.4.3.3 Voiceband data considerations**
+
+The issue of whether network echo control devices, such as echo cancellers, significantly degrade certain types of voiceband data transmission is unresolved. Additional information on this subject is available in Appendix I/G.168.
+
+## **7.5 Temporal (syllable) clipping**
+
+Temporal speech clipping is the loss of speech signal at any time, and can occur when, for example, voice activity detection is used, when low bit rate coders change rate, or during protection switching and uncontrolled slips. The subjective impact of clipping depends on four factors: duration of clip; percentage of speech clipped; frequency of clipping; and overall speech activity. Based on the results of detailed subjective tests, two guidelines (specified in Recommendation G.116) to maintain good speech quality are:
+
+- clipping of speech segments $\geq 64$ ms should always be avoided; and
+- clipped segments $< 64$ ms should be kept below 0.2 per cent of active speech.
+
+## **7.6 Environmental (acoustic) noise**
+
+Acoustic noise at the transmitting end of a connection will have a negative impact on the performance of speech coders. The speech coders found in the G.72x-series have been tested for the effects of environmental noise at the sending end of the connection. However, some codecs have been tested more extensively than others. All have been shown to be fairly robust under conditions that included addition of circuit noise or speech babble to the input speech. If a particular type of background noise will be dominant in a given application, it is advisable to verify that performance of the speech codec is satisfactory under those conditions.
+
+Pick-up of environmental noise with non-standard handsets may present special problems for the quality of speech when low bit rate codecs are used. In these situations, selection of a speech codec that is robust in the presence of acoustic background noise is especially important.
+
+## **7.7 Idle channel noise**
+
+Idle channel noise in VoIP applications should be negligible. If present, however, background idle channel noise should be less than $-68$ dBm0p, a value consistent with Recommendation G.106.
+
+## **7.8 Noise contrast and comfort noise**
+
+Noise contrast occurs when background noise is interrupted due to digital speech processing, such as echo cancellation using centre clippers, and voice activity detection (silence removal). Comfort noise is noise that can be introduced to mask the negative effects of noise contrast. Recommendations on noise contrast limits, and comfort noise values, are for future study.
+
+For comfort noise insertion, some digital cellular systems (e.g. GSM) use an approach where noise parameters are extracted at the sending end and transmitted to the receiving end at a low bit rate. It is then possible to reconstruct (to good approximation) the background noise. This approach should provide superior subjective performance for voice users of circuits using voice activity detection and
+
+comfort noise insertion. The voice activity detectors and comfort noise generators described in Annex B/G.729 and Annex A/G.723.1 both operate in this fashion.
+
+The best (subjective) performance will be realized when the noise inserted at the receiving end matches, as closely as possible, the background noise at the sending end. The following comments on CNGs can be made:
+
+- the noise used should match the background noise, both in frequency content and level;
+- level of the inserted noise should match that of the background noise; appropriate level measurements and adjustments should be done using dBm0p;
+- the time course of changes in the level of the inserted noise should match, as closely as possible, the level changes that occur in the background noise.
+
+## 7.9 Bandwidth
+
+To maintain good speech quality and intelligibility, a minimum passband of 300-3400 Hz (3 dB points) should be delivered. For non-waveform coders, traditional measurement methods using single-frequency sine waves may not be adequate to evaluate effective bandwidth and level stability. At the date of this Recommendation, there are no industry-accepted methods to assess bandwidth of these non-linear systems.
+
+## 7.10 Stability loss
+
+For VoIP systems interfacing digitally to the PSTN, a minimum loss of 6 dB is recommended between the digital input and output paths of the VoIP system at the access port of the terminal. This guideline is provided to assure that singing does not occur when the handset terminal is used under conditions different from those to which the $TCL_w$ measurement applies (e.g. placing a handset on a hard surface should not cause singing).
+
+## 7.11 Distortion
+
+Distortion in packetized systems such as Internet Telephony will be due primarily to the operation of speech codecs. It is essential that high quality speech codecs are used and that they have been thoroughly tested (subjectively) to ensure that there are no annoying effects.
+
+# 8 Speech transmission planning in hybrid networks
+
+The E-model (Recommendation G.107) is the recommended approach for use by network designers and transmission planners to describe and plan for handling the impairments that affect the quality of transmitted speech. This approach uses "the Equipment Impairment Factor Method" (Recommendation G.113), and is intended for use in a wide variety of transmission planning scenarios. Table 1 shows sample E-Model calculations for combinations of delay and equipment impairment factor. Recommendation G.108 provides general guidance for using the E-Model in transmission planning. $I_e$ values in Table 1 are taken from Appendix I/G.113. Cells in the table are shaded according to the categories defined in Recommendation G.109.
+
+**Table 1/G.177 – R-values for indicated combinations of Ie and end-to-end mean one-way delay**
+
+| Delay (ms) | Ie value | | | | | | | | |
+|------------|----------|---------|----------|-------|-------------|-----------------------|-----------------------------|--------|-----------------------|
+| | 0 | 5 | 7 | 10 | 15 | 19 | 19 | 20 | 26 |
+| | G.711 | GSM-EFR | G.726@32 | G.729 | G.723.1@6.3 | G.729A+VAD w/ 2% loss | G.723.1@5.3 | GSM-FR | G.729A+VAD w/ 4% loss |
+| | | | G.728@16 | | | | G.723.1@6.3 +VAD w/ 1% loss | IS-54 | |
+| ~0 | 94 | | 87 | | | | | | |
+| 50 | 93 | | 86 | 83 | | 74 | | | 67 |
+| 100 | 92 | 87 | 85 | 82 | 77 | 73 | 73 | 72 | 66 |
+| 150 | 90 | 85 | 83 | 80 | 75 | 71 | 71 | 70 | 64 |
+| 200 | 87 | 82 | 80 | 77 | 72 | 68 | 68 | 67 | 61 |
+| 250 | 80 | 75 | 73 | 70 | 65 | 61 | 61 | 60 | 54 |
+| 300 | 74 | 69 | 67 | 64 | 59 | 55 | 55 | 54 | 48 |
+| 350 | 68 | 63 | 61 | 58 | 53 | 49 | 49 | 48 | 42 |
+| 400 | 63 | 58 | 56 | 53 | 48 | 44 | 44 | 43 | 37 |
+| 450 | 59 | 54 | 52 | 49 | 44 | 40 | 40 | 39 | 33 |
+
+NOTE 1 – R-values in this table have been calculated using the indicated values for Ie and T (T=Ta=Tr/2) along with the default values from Table 3/G.107 for all other parameters.
+
+NOTE 2 – Unless indicated otherwise, examples do not include packet loss or Voice Activity Detection (VAD).
+
+NOTE 3 – Blackened cells indicate combinations of delay and codec that are impossible to realize.
+
+# 9 Non-voice transmission (end-to-end)
+
+There are a variety of user applications used on the PSTN that must continue to operate properly on hybrid connections. These include facsimile, encryption of voice and data (e.g. STU-III), ASCII file transfer, and use of special terminals. Packet loss and/or effects of low bit rate speech coding may limit the success of many of the more stringent applications. Difficulties associated with low bit rate coding require special care to ensure that these applications continue to operate at level that is satisfactory to end-users. These applications include:
+
+- Fax – Proper fax transmission over hybrid Internet/PSTN connections will require special consideration. The role of the gateway will be central to this process. Each of the scenarios shown in Figure 1 must be considered.
+- DTMF – DTMF signals from the VoIP terminals may be used to interact with DTMF-based services such as message retrieval. Thus, the VoIP system should support good end-to-end transmission of DTMF signals. Since some speech codecs will corrupt DTMF signals, special considerations may be necessary to ensure acceptable DTMF transmission. For an example of typical DTMF requirements, see ANSI/TIA/EIA/464-B-96.
+- Call Progress Signals – It is also expected that call progress signals, such as audible ringback and busy, not be seriously degraded by the VoIP system. Detailed guidelines are for further study.
+- TTY Devices and TDD Devices – The very low bit rate terminals are used on the PSTN and may find use on hybrid connections.
+
+# ITU-T RECOMMENDATIONS SERIES
+
+- Series A Organization of the work of the ITU-T
+- Series B Means of expression: definitions, symbols, classification
+- Series C General telecommunication statistics
+- Series D General tariff principles
+- Series E Overall network operation, telephone service, service operation and human factors
+- Series F Non-telephone telecommunication services
+- Series G Transmission systems and media, digital systems and networks**
+- Series H Audiovisual and multimedia systems
+- Series I Integrated services digital network
+- Series J Transmission of television, sound programme and other multimedia signals
+- Series K Protection against interference
+- Series L Construction, installation and protection of cables and other elements of outside plant
+- Series M TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits
+- Series N Maintenance: international sound programme and television transmission circuits
+- Series O Specifications of measuring equipment
+- Series P Telephone transmission quality, telephone installations, local line networks
+- Series Q Switching and signalling
+- Series R Telegraph transmission
+- Series S Telegraph services terminal equipment
+- Series T Terminals for telematic services
+- Series U Telegraph switching
+- Series V Data communication over the telephone network
+- Series X Data networks and open system communications
+- Series Y Global information infrastructure and Internet protocol aspects
+- Series Z Languages and general software aspects for telecommunication systems
\ No newline at end of file
diff --git a/marked/G/T-REC-G.180-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.180-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f4eb59a86e7f853a82bd7fa9ccf45c68cb116248
--- /dev/null
+++ b/marked/G/T-REC-G.180-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e2afd90e5081164a00e7d9b25ccefdddc83a8b608d0e6869a6e97256dd6bb58
+size 8227
diff --git a/marked/G/T-REC-G.180-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg b/marked/G/T-REC-G.180-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f142c1d91e3fb187cc142648f2fc81c0aaaa6845
--- /dev/null
+++ b/marked/G/T-REC-G.180-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8c4e27839619cfd88edaeab55d9dd998e4fedb8287018e178fabc0de06e931b0
+size 130220
diff --git a/marked/G/T-REC-G.180-199303-I_PDF-E/e6b5ee67ac260b0a3ed3e3c5ad7ea19c_img.jpg b/marked/G/T-REC-G.180-199303-I_PDF-E/e6b5ee67ac260b0a3ed3e3c5ad7ea19c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4cdb0008f9e0212fac03e498cf70e41398b516e1
--- /dev/null
+++ b/marked/G/T-REC-G.180-199303-I_PDF-E/e6b5ee67ac260b0a3ed3e3c5ad7ea19c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2ed53f51899413b11b8bd7be6bcaf1878c7bf9683c764681dff971175cb8f0ca
+size 25042
diff --git a/marked/G/T-REC-G.180-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/G/T-REC-G.180-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e815cdf39462faf1ee5f78e1e49b1088fb26b0ad
--- /dev/null
+++ b/marked/G/T-REC-G.180-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:35851fcd53a871bdc467d8183077835aa99497fbae38a32d34f9b03d6b89c4dd
+size 69489
diff --git a/marked/G/T-REC-G.180-199303-I_PDF-E/raw.md b/marked/G/T-REC-G.180-199303-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..9b26e7258bd9e52fc92dcad53c91d4c63800bc50
--- /dev/null
+++ b/marked/G/T-REC-G.180-199303-I_PDF-E/raw.md
@@ -0,0 +1,431 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**G.180**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(03/93)
+
+**GENERAL CHARACTERISTICS OF INTERNATIONAL
+TELEPHONE CONNECTIONS AND INTERNATIONAL
+TELEPHONE CIRCUITS**
+
+---
+
+**CHARACTERISTICS OF N + M TYPE DIRECT
+TRANSMISSION RESTORATION SYSTEMS
+FOR USE ON DIGITAL AND ANALOGUE
+SECTIONS, LINKS OR EQUIPMENT**
+
+**ITU-T Recommendation G.180**
+
+(Previously "CCITT Recommendation")
+
+---
+
+# FOREWORD
+
+The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecommunication Union. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+ITU-T Recommendation G.180 was revised by the ITU-T Study Group XV (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993).
+
+# --- NOTES
+
+1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector.
+
+In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms "CCITT, CCIR or IFRB" or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure.
+
+2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+# CONTENTS
+
+*Page*
+
+| | | |
+|-------------|------------------------------------------------------------------------------------------------------------|----|
+| 1 | General ..... | 1 |
+| 2 | Object of Recommendation..... | 1 |
+| 3 | RSE specifications..... | 2 |
+| 3.1 | Interfaces ..... | 3 |
+| 3.2 | Operational aspects ..... | 3 |
+| 4 | RSCE specifications ..... | 5 |
+| 4.1 | Interfaces ..... | 5 |
+| 4.2 | Operational aspects ..... | 6 |
+| Annex A | ..... | 7 |
+| A.1 | Maximum permissible intrinsic jitter at output ports of regenerative restoration switching equipment ..... | 7 |
+| Annex B | ..... | 9 |
+| B.1 | Jitter transfer characteristics recommended for regenerative restoration switching equipment ..... | 9 |
+| Appendix I | – Examples of alarms and status criteria for digital systems ..... | 11 |
+| Appendix II | – Examples for monitoring and self-test procedures for digital system ..... | 12 |
+
+
+
+# **CHARACTERISTICS OF N + M TYPE DIRECT TRANSMISSION RESTORATION SYSTEMS FOR USE ON DIGITAL AND ANALOGUE SECTIONS, LINKS OR EQUIPMENT**
+
+*(Melbourne, 1988; amended at Helsinki, 1993)*
+
+# **1 General**
+
+Transmission restoration functions are often implemented in the modern telecommunication networks to improve the availability and quality of service, by minimizing the effects or potential effects of a transmission failure, and to make the maintenance operations easier.
+
+The terminology and general principles of transmission restoration are described in Recommendation M.495. The functional organization for automatic transmission restoration is described in Recommendation M.496.
+
+# **2 Object of Recommendation**
+
+This Recommendation specifies the characteristics of equipment for N + M type direct transmission restoration systems (protection link switching) for digital and analogue sections, links and equipment (see Recommendations G.701 and G.211). The general arrangement of a system for N + M direct transmission restoration is shown in Figure 1. This Recommendation refers to the equipment labelled as RSE (restoration switching equipment) and RSCE (restoration switching control equipment).
+
+This Recommendation is intended also to cover the case where the signals at the interfaces T belong to different hierarchical levels. In this case, each access at one side can be a group of accesses as indicated in the example of Figure 2. The left part of this figure refers to the particular case where the restored path is not on a complete link but just through a multiplex equipment.
+
+NOTE – The equipment specified in this Recommendation can possibly be used also for N + M automatic or semi-automatic transmission rerouting (protection network switching) but generally this type of restoration function is implemented by different equipment, often incorporating also other functions (such as, for example, automatic digital distribution frames).
+
+Three types of direct transmission restoration systems are considered by this Recommendation:
+
+The first one should permit routing of any one of N normal links on to any one of M restoration links.
+
+The second type should permit the interconnection of any of the N accesses to any one of the N + M links.
+
+The third one should permit routing of any one of N normal links to a single restoration link (in many cases this type can be considered just a special case of the first type).
+
+For all the types two options exist:
+
+- a) to switch the two directions of transmission independently; and
+- b) to switch the two directions of transmission simultaneously.
+
+This Recommendation does not cover the restoration systems fully embedded in transmission systems and the 1 + 1 systems where the switching occurs at the receive end only (see Recommendation G.181).
+
+The hierarchical levels at interfaces T are those specified in Recommendation G.702 (hierarchy levels 1 and up). For RSE to be used on analogue transmission systems the frequency bands at interface T are those specified in Recommendation G.211.
+
+
+
+Sections, links or equipment
+
+T
+
+M
+
+Optional spare link accesses
+
+1
+
+N
+
+1
+
+RSE
+
+X
+
+Y
+
+LT
+
+MUX
+
+N + M
+
+3
+
+2
+
+1
+
+Embedded in the restoration and/or normal links or separate
+
+Z
+
+Local manual control
+
+RSCE
+
+Q
+
+T1513480-93/d01
+
+RSE Restoration switching equipment
+
+RSCE Restoration switching control equipment
+
+LT
+
+MUX
+
+X Non-standardized (or standard Q) interface. If RSE and RSCE are combined interface X does not exist
+
+Y Interface to be standardized in the future (possibly standard Q)
+
+Z Interface possibly to be standardized
+
+Q Optional standard Q interface to the TMN (telecommunication management network) or to a control centre
+
+T Transmission path interfaces
+
+This link can be replaced by connection in the TMN
+
+Diagram of an N + M direct transmission restoration system. It shows two Restoration Switching Equipment (RSE) blocks connected to two Restoration Switching Control Equipment (RSCE) blocks. The RSE blocks are connected to a series of Line Terminal (LT) and Multiplexing (MUX) units. These units are connected to 'Sections, links or equipment' represented by transmission path interfaces (T). The RSCE blocks are connected to 'Local manual control' and have an 'Embedded in the restoration and/or normal links or separate' link between them. The RSCE blocks also have an interface X with the RSE blocks and an interface Q with the TMN. The diagram includes a legend defining the interfaces: X (Non-standardized or standard Q interface), Y (Interface to be standardized in the future), Z (Interface possibly to be standardized), Q (Optional standard Q interface to the TMN), and T (Transmission path interfaces). The legend also defines RSE and RSCE, and indicates that a dashed link can be replaced by connection in the TMN.
+
+## NOTES
+
+- 1 The failing of a section or link can possibly be detected in the RSE and the information transferred to the RSCE. In this case interface Y may not exist.
+- 2 The interworking with the TMN via interface Q is at present beyond the scope of the Recommendation.
+- 3 The N + M links or sections can be in the same cable or follow different routes.
+- 4 Spare link accesses may be used to convey low priority traffic.
+- 5 The interface between the RSCE and local manual control is not standardized and it is not covered by this Recommendation.
+
+FIGURE 1/G.180
+N + M direct transmission restoration system
+
+## 3 RSE specifications
+
+Two types of RSE are considered by this Recommendation: “regenerative” and “non-regenerative”.
+
+The first type, where the digital signal undergoes a complete process of retiming and reshaping, is for digital systems only. It makes the RSE a digital equipment, and it is sometimes considered to be advantageous, e.g. from the station cabling point of view.
+
+
+
+RSE Restoration switching equipment
+ MUX Digital multiplexing or analogue translating equipment
+ LT Line terminal equipment
+
+T1513490-93/d02
+
+Two diagrams illustrating restoration systems with different hierarchical levels at the two ends. The left diagram shows a system with Optional accesses (M to 1) and Regular accesses (N to 1) connected to an RSE, which is then connected to four MUX units, which are then connected to another RSE. The right diagram shows a system with Optional accesses (M to 1) and Regular accesses (N to 1) connected to an RSE, which is then connected to four MUX units, which are then connected to four LT units. The LT units are labeled N+M, 3, 2, and 1 from left to right. These LT units are then connected to a final RSE. A legend defines RSE as Restoration switching equipment, MUX as Digital multiplexing or analogue translating equipment, and LT as Line terminal equipment. The code T1513490-93/d02 is present at the bottom right of the diagrams.
+
+FIGURE 2/G.180
+
+### **Examples of restoration systems where the hierarchical levels at the two ends are different**
+
+The second type, where the output signal is proportional to the input signal (except for minor distortion) is considered to be useful for digital systems under some circumstances, e.g. from a reliability and cost point of view, and it is the only one usable for analogue systems.
+
+### 3.1 Interfaces
+
+#### 3.1.1 Transmission path interfaces (T)
+
+The relevant parameters and the recommended values are listed in the uppermost part of Table 1 for the non-regenerative RSE, to be used for digital systems. The uppermost part of Table 2 covers the regenerative RSE. The uppermost part of Table 3 is for the non-regenerative RSE to be used for analogue systems.
+
+#### 3.1.2 Control interfaces
+
+The only control interface of the RSE is X. This interface is not at present specified by the CCITT. However in the future, it may be specified as a Q interface (see Recommendation G.773).
+
+If the interface X is not standardized, the separation between the RSE and RSCE (and consequently between clauses 3 and 4) will be somewhat arbitrary.
+
+### 3.2 Operational aspects
+
+#### 3.2.1 Transfer of the switched signals
+
+The relevant parameters and the recommended values are listed in the lower part of Table 1 for the non-regenerative RSE to be used for digital systems. The lower part of Table 2 covers the regenerative RSE. The lower part of Table 3 is for the non-regenerative RSE to be used for analogue systems.
+
+TABLE 1/G.180
+
+#### **Recommended values for the interface and transfer characteristics of non-regenerative RSE for use on digital systems**
+
+| Interface | Nominal impedance | As stated in Rec. G.703 |
+|-----------|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | Return loss at the input port (with the output port terminated on the nominal impedance) | 6 dB above the values stated in Rec.G.703 |
+| | Accepted levels | The output levels considered in Rec. G.703 |
+| Transfer | Transfer function between the input and the output of the RSE (terminated on the nominal impedances) (see Note 2 of Table 2) | < 10% of the interconnecting pair loss and phase distortion allowed in Rec. G.703 for the relevant hierarchical level, or the complement thereof, plus or minus 0.5 dB flat loss.
It is assumed that the loss vs frequency distortion approximates to the \sqrt{f} law
|
+| | Crosstalk attenuation | ≥ 40 dB from any channel
≥ 30 dB multi-channel interference evaluated on a voltage-sum basis. These values apply up to a frequency value equal to the nominal bit-rate
|
+
+TABLE 2/G.180
+
+#### **Recommended values for the interface and transfer characteristics of regenerative RSE**
+
+| | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|
+| Interface (Note 2) | Connecting pairs Test impedance and return loss at the input ports Pulse shape and levels Tolerable input jitter | As stated in Rec. G.703 |
+| | Intrinsic output jitter | As stated in Annex A |
+| Transfer (Note 2) | Jitter transfer | As stated in Annex B |
+| | Error performance | 99.99% error-free seconds (Note 1) |
+| | Others | The paths across each switch shall maintain bit sequence independence and integrity |
+| NOTES 1 Evaluated under maximum loading condition and excluding any external source of interference. 2 The nominal bit rate and tolerance are as stated in Recommendation G.703. | | |
+
+TABLE 3/G.180
+
+#### **Recommended values for the interface and transfer characteristics of non-regenerative RSE for use on analogue systems**
+
+| | | |
+|-------------------------|----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|
+| Interface | Nominal relative levels in switching points | As stated in Recommendation G.233 |
+| | Nominal impedance at the input/output ports | |
+| | Return loss at the input/output ports | |
+| | Longitudinal balance conversion loss | (Note) $\geq 46$ dB |
+| Transfer | Insertion loss | $\leq 0.3$ dB |
+| | Frequency response as stated in Recommendation G.211 | $\pm 0.2$ dB |
+| | Noise referred to the voice-frequency channel bandwith | $\leq 20$ pW0 for a pair of RSEs loaded by the signal of maximum power averaged over one minute interval |
+| | Intelligible crosstalk ratio between ports within the same RSE | $\geq 90$ dB |
+| NOTE – For groups only. | | |
+
+#### 3.2.2 Response
+
+For RSE providing M restoration paths to N normal paths ( $M = 1$ included) it is recommended that in response to a RSCE command the RSE should apply the incoming interface signal belonging to a given normal link to the input port of a given restoration link. The signal should not be removed from the input port of the concerned normal link, except that it may be replaced by a test signal.
+
+For RSE providing $N + M$ link to N accesses it is recommended that in response to a RSCE command, the RSE should apply the incoming interface signal belonging to a given access from 1 to N to a given link from 1 to $N + M$ .
+
+The time required for the above response is the restoration transfer time, as defined in Recommendation M.495.
+
+#### 3.2.3 Other operational aspects
+
+A recognized failure of the RSCE or its disconnection from the RSE at interface X (when applicable) should either:
+
+- Cause the RSE to route all the signals on the N normal links. After the failure of the RSCE is cleared or the RSCE is reconnected to the RSE, normal restoration operations will resume.
+- Not alter the state of the RSE. The cross-connection pattern of the RSE should be available by interrogation from the RSCE to enable it to update, when the failure is cleared or it is reconnected to the RSE, its own record on the cross-connection pattern.
+
+For the restoration systems of the second type (as defined alternative in b) only holds. For the systems of the first and third types both alternatives are applicable.
+
+## 4 RSCE specifications
+
+## 4.1 Interfaces
+
+Interfaces Y, Z of the RSCE (see Figure 1) are at present non standardized. However they may be standardized in the future.
+
+### **4.2 Operational aspects**
+
+#### **4.2.1 Responses**
+
+A switching to a restoration link should be initiated under a request coming from interfaces Y, Z, Q (and X where the faults are detected within the RSE) or on command from the local manual control.
+
+When decided in the RSCE the allocation of a restoration link can optionally take place according to defined priority rules based on:
+
+- defined priority for each normal link;
+- request type (low or high priority request).
+
+Otherwise the allocation should be specified by the information coming from interfaces Z, Q or local manual control.
+
+For the restoration systems providing M restoration links (M = 1 included) on N normal links, when a successful restoration request clears, traffic should be returned to the pertinent normal link and the pertinent restoration link should be released.
+
+It should be possible from interfaces Z, Q and under local manual control to lock in a working link (e.g. during system maintenance).
+
+The time required for the above response is the sum of the waiting time and the restoration procedure time, as defined in Recommendation M.495.
+
+#### **4.2.2 Alarm and status criteria**
+
+The alarm and status criteria provided by the RSCE are not standardized. Examples are reported in Appendix I.
+
+#### **4.2.3 Monitoring and self-test procedures**
+
+The monitoring and self-test procedures of the RSCE are not standardized. Examples are reported in Appendix II.
+
+# Annex A
+
+(This annex provides information which is supplementary to Table 2 and does not form an integral part of this Recommendation)
+
+## A.1 Maximum permissible intrinsic jitter at output ports of regenerative restoration switching equipment
+
+NOTE – Values for bit rates of the 1544 kbit/s digital hierarchy are not covered by this Recommendation.
+
+### A.1.1 For asynchronous space matrix RSE
+
+| Digital rate (kbit/s) | Maximum value Unit interval peak-peak | Parameter value | |
+|-----------------------|---------------------------------------|---------------------------------------------------------------------------------------------|----------|
+| | | Measurement filter bandwith | |
+| | | Bandpass filter having a lower cut-off frequency $f_1$ and an upper cut-off frequency $f_4$ | |
+| | | $f_1$ | $f_4$ |
+| 2 048 | 0.1 | 20 Hz | 100 kHz |
+| 8 448 | 0.1 | 20 Hz | 400 kHz |
+| 34 368 | 0.075 | 100 Hz | 800 kHz |
+| 139 264 | 0.05 | 200 Hz | 3500 kHz |
+
+### A.1.2 For synchronous RSE using central timing
+
+| Digital rate (kbit/s) | Parameter value | | | | |
+|--------------------------|---------------------------------------------|-----------------------------------|---------------------------------------------------------------------------------------------------------|--------------------|----------|
+| | Maximum value Unit interval peak-peak | | Measurement filter bandwidth | | |
+| | | | Bandpass filter having a lower cut-off frequency $f_1$ or $f_3$ and an upper cut-off frequency $f_4$ | | |
+| | $B_1$ ( $f_1 \div f_4$ filter) | $B_2$ ( $f_3 \div f_4$ filter) | $f_1$ | $f_3$ | $f_4$ |
+| 2 048 | 0.25 | 0.05 | 20 Hz | 18 kHz (700 Hz) | 100 kHz |
+| 8 448 | 0.25 | 0.05 | 20 Hz | 3 kHz (80 kHz) | 400 kHz |
+| 34 368 | 0.35 | 0.05 | 100 Hz | 10 kHz | 800 kHz |
+| 139 264 | 0.35 | 0.05 | 200 Hz | 10 kHz | 3500 kHz |
+
+## NOTES
+
+- 1 UI Unit interval
+ for 2 048 kbit/s 1 UI 488 ns
+ for 8 448 kbit/s 1 UI 118 ns
+ for 34 368 kbit/s 1 UI 29.1 ns
+ for 139 264 kbit/s 1 UI 7.18 ns.
+- 2 These figures shall be met for any valid signal in the absence of input jitter. The measurement shall be implemented using equipment designed in accordance with Recommendation O.171.
+- 3 Clause 2/G.823 indicates the measurement method.
+- 4 The frequency values in parentheses only apply to certain national interfaces.
+
+# Annex B
+
+(This annex provides information which is supplementary to Table 2 and does not form an integral part of this Recommendation)
+
+## B.1 Jitter transfer characteristics recommended for regenerative restoration switching equipment
+
+NOTE – Values for bit rates of the 1544 kbit/s digital hierarchy are not covered by this Recommendation.
+
+
+
+Graph of Jitter gain vs Jitter frequency (log scale). The y-axis is Jitter gain with markers x, 0, and -y. The x-axis is Jitter frequency (log scale) with markers f0, f5, f6, and f7. The graph shows a flat region at gain x from f0 to f5, a downward sloping region from f5 to f6 with a label 'Slope 20 dB/decade', and a flat region at gain -y from f6 to f7. The area above the curve is shaded with diagonal lines. A small label 'T1513500-93/d03' is at the bottom right.
+
+### B.1.1 For asynchronous space matrix RSE
+
+| Digital rate (kbit/s) | Parameter value | | | | | | |
+|-----------------------|-------------------|-------------|------------|-------------|-------------|-------------|------------------------------------------|
+| | $x$ (dB) (Note 5) | $-y$ (dB) | $f_0$ (Hz) | $f_5$ (kHz) | $f_6$ (kHz) | $f_7$ (kHz) | Test signal (pseudorandom as Rec. O.151) |
+| 2 048 | 0.5 | -8.4 (-9.5) | (Note 1) | 36 (1.4) | 100 (4.4) | 100 | $2^{15} - 1$ |
+| 8 448 | 0.5 | -9.5 (-7.5) | (Note 1) | 6 (160) | 19 (400) | 400 | $2^{15} - 1$ |
+| 34 368 | 0.5 | -9.5 | (Note 1) | 20 | 64 | 800 | $2^{23} - 1$ |
+| 139 264 | 0.5 | -9.5 | (Note 1) | 20 | 64 | 3500 | $2^{23} - 1$ |
+
+#### NOTES
+
+- 1 The frequency $f_0$ should be as low as possible (e.g. 10 Hz) taking into account the limitations of measuring equipment.
+- 2 The measuring method should be selective with a bandwidth sufficiently small referred to the relevant measuring frequency, but not wider than 40 Hz.
+- 3 In the $f_6$ to $f_7$ frequency range the jitter gain should be less than $-y$ dB, with the exception of spurious responses, which should be suppressed below $-6$ dB.
+- 4 The frequency values shown in parentheses only apply to certain national interfaces.
+- 5 A value of 0.2 dB has been suggested as technically possible for this type of equipment. This may be useful where large numbers of RSE are employed in the network.
+
+### **B.1.2 For synchronous RSE using central timing**
+
+| Digital rate (kbit/s) | Parameter value | | | | | | |
+|--------------------------|-----------------|-----------|------------|------------|------------|-------------|------------------------------------------------|
+| | $x$ (dB) | $-y$ (dB) | $f_0$ (Hz) | $f_5$ (Hz) | $f_6$ (Hz) | $f_7$ (kHz) | Test signal (pseudorandom as Rec. O.151) |
+| 2 048 | 0.5 | 19.5 | (Note 1) | 40 | 400 | 100 | $2^{15} - 1$ |
+| 8 448 | 0.5 | 19.5 | (Note 1) | 100 | 1000 | 400 | $2^{15} - 1$ |
+| 34 368 | 0.5 | 19.5 | (Note 1) | 300 | 3000 | 800 | $2^{23} - 1$ |
+| 139 264 | 0.5 | 19.5 | (Note 1) | 900 | 9000 | 3500 | $2^{23} - 1$ |
+
+NOTES
+
+- 1 The frequency $f_0$ should be as low as possible (e.g. 10 Hz) taking into account the limitations of measuring equipment.
+- 2 The measuring method should be selective with a bandwidth sufficiently small referred to the relevant measuring frequency, but not wider than 40 Hz.
+
+# Appendix I
+
+## Examples of alarms and status criteria for digital systems
+
+(Both refer to a N + 1 system)
+
+(This appendix does not form an integral part of this Recommendation)
+
+| Provided by STC PLC | Provided by AT&T Network Systems International |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Alarms
The system should include:
a) System fail. b) Protection failure. c) Manual switch in operation d) System software self check in operation. e) Control system failure. f) System software failure. g) Communication failure. h) Stand-by channel failure. i) Power supply failure. j) Card removal. | Separate alarm criteria shall be issued at the occurrence of the following faulty conditions:
a) Loss of signal at the traffic input port, transmit side. b) Loss of signal at the traffic output port, receive side. c) Automatic lock-in (see Note). d) Switch failure. e) Protection failure. f) Control system failure. g) Communication failure. h) Stand-by channel failure. i) Power supply unit failure. j) Loss of power supply. k) Switch exerciser failure. Separate status criteria shall be issued, on the occurrence of the following situations:
a) Switch operated. b) Switch locked. c) Switch request pending. d) Switch in manual mode. The protective switching control equipment shall make available to the remote control and maintenance centre alarm and status information corresponding to the criteria shown above.
|
+| NOTE – This system is required to automatically lock in the normal or the protection channel if an excessive number of switching operations are made in a given period.
| |
+
+# Appendix II
+
+## Examples for monitoring and self-test procedures for digital system
+
+(Both refer to a N + 1 system)
+
+(This appendix does not form an integral part of this Recommendation)
+
+| | |
+|------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Provided by STC PLC | Standby channel monitoring
The system should include means of monitoring the standby channel continuously for proper operation.
Self-check
The system should include self-check facilities as follows:
a) Communication channel. b) Background-checking of the memory, coaxial relay drive buffer and other hardware. c) Correct programme execution. |
+| Provided by AT&T Network Systems International | Standby channel monitoring
The standby channel shall be monitored continuously for proper operation.
Switch exerciser
The protective switching system shall provide a switch exerciser meeting the following requirements:
The exerciser shall test the complete switch-over procedure up to but excluding the last transfer switch in the direction of transmission.
The switching system shall drop the exerciser routine and serve switch requests from failed or deteriorated channels.
A facility for including the last switch in the exercise routine may be provided. This feature shall have the capability of being disabled.
|
\ No newline at end of file
diff --git a/marked/G/T-REC-G.181-199303-I_PDF-E/raw.md b/marked/G/T-REC-G.181-199303-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..76db92f50646c99a8850411114492be27542b0cb
--- /dev/null
+++ b/marked/G/T-REC-G.181-199303-I_PDF-E/raw.md
@@ -0,0 +1,174 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**G.181**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(03/93)
+
+**GENERAL CHARACTERISTICS OF INTERNATIONAL
+TELEPHONE CONNECTIONS AND INTERNATIONAL
+TELEPHONE CIRCUITS**
+
+---
+
+**CHARACTERISTICS OF 1 + 1 TYPE
+RESTORATION SYSTEMS FOR USE
+ON DIGITAL TRANSMISSION LINKS**
+
+**ITU-T Recommendation G.181**
+
+(Previously "CCITT Recommendation")
+
+---
+
+# FOREWORD
+
+The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecommunication Union. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+ITU-T Recommendation G.181 was revised by the ITU-T Study Group XV (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993).
+
+# --- NOTES
+
+1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector.
+
+In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms "CCITT, CCIR or IFRB" or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure.
+
+2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+# CONTENTS
+
+| | Page |
+|----------------------------------|-------------|
+| 1 General ..... | 1 |
+| 2 Object of Recommendation..... | 1 |
+| 3 Equipment specifications ..... | 1 |
+| 3.1 Interfaces ..... | 1 |
+| 3.2 Operational aspects..... | 1 |
+
+
+
+# **CHARACTERISTICS OF 1 + 1 TYPE RESTORATION SYSTEMS FOR USE ON DIGITAL TRANSMISSION LINKS**
+
+*(Melbourne, 1988; amended at Helsinki, 1993)*
+
+# **1 General**
+
+Transmission restoration functions are often implemented in the modern telecommunication network to improve the availability and quality of services, by minimizing the effects or potential effects of a transmission failure, and to make the maintenance operations easier.
+
+The terminology and general principles of transmission restoration are described in Recommendation M.495. The functional organization for automatic transmission restoration is described in Recommendation M.496.
+
+# **2 Object of Recommendation**
+
+This Recommendation specifies the characteristics of equipment for 1 + 1 type transmission restoration systems (protection link switching) for digital transmission links (see Recommendation G.701). The general arrangement of a system of this type is shown in Figure 1. It uses hybrid on the send side, splitting the input path into two output paths. On the receive side the two paths are supervised and are connected further by a switch automatically controlled by the received signals. The switch may additionally be operated manually or by some kind of remote procedure. The two transmission directions are handled independently.
+
+This Recommendation refers to the equipment labelled as H (hybrid) RSE (restoration switching equipment) and RSCE (restoration switching control equipment).
+
+This Recommendation does not cover the restoration systems fully embedded in transmission systems.
+
+The hierarchical level at interface T is 2048 kbit/s.
+
+# **3 Equipment specifications**
+
+Equipment H and RSE (see Figure 1) may be of the regenerative or non-regenerative type.
+
+## **3.1 Interfaces**
+
+### **3.1.1 Transmission path interfaces (T)**
+
+For H and RSE equipment of the regenerative type the interfaces shall be as specified in Recommendation G.703. The intrinsic output jitter should be not greater than 0.05 UI (measurement filter bandwidth: 20 Hz to 100 kHz).
+
+Interface characteristics for H and RSE equipment of the non-regenerative type are at present not covered by this Recommendation.
+
+### **3.1.2 Control interface (X)**
+
+The control interface X is not at present standardized by CCITT. However in the future it may be specified as a Q interface (see Recommendation G.773).
+
+## **3.2 Operational aspects**
+
+### **3.2.1 Transfer of the switched signals**
+
+For H and RSE equipment of the regenerative type the jitter transfer gain should be not greater than 0.5 dB.
+
+The transfer characteristics for H and RSE equipment of the non-regenerative type are at present not covered by this Recommendation.
+
+### 3.2.2 Response
+
+Switching between the two paths occurs only on the receive side, as indicated in Figure 1.
+
+
+
+Diagram of a 1 + 1 transmission restoration system. It shows a Hybrid (H) unit on the left with input I and two outputs II and III. These connect via 'Digital links' to a Restoration Switching Equipment (RSE) unit on the right. The RSE has two inputs II' and III' and one output IV. Output IV connects to a Restoration Switching Control Equipment (RSCE) unit. The RSCE has a control interface X and is also connected to a 'Local manual control' box. A legend defines the symbols: H (Hybrid), RSE (Restoration switching equipment), RSCE (Restoration switching control equipment), T (Transmission interface), and X (Control interface). The diagram is labeled T1513510-93/d01.
+
+# NOTES
+
+- 1 The two digital links can be in the same cable or follow different routes.
+- 2 The interface between the RSCE and the local manual control is not standardized and it is not covered by this Recommendation.
+
+FIGURE 1/G.181
+**1 + 1 transmission restoration system**
+
+One of the two paths may be the path with the primary right, e.g. path II/II'. If this path fails the switch is operated to path III/III'. After restoration of path II/II' the switch will automatically be set back to this path.
+
+If the two paths have the same right the switch will remain in the last position even after restoration of a failed path. This is the preferred method.
+
+NOTE 1 – Paths II/II' and III/III' have the same performance under normal planning conditions of transmission routes and systems. The “method of the same right” reduces the frequency of switching and resynchronization by a factor of 2.
+
+Switching to a failed path must be avoided.
+
+The RSCE should operate the switch:
+
+- automatically according to the criteria expressed by Tables 1 and 2, based on AIS reception and loss of incoming signal or (as an option) on transmission quality (see Note 2);
+- manually on command from the local manual control;
+- under a request coming from interface X.
+
+NOTE 2 – As an option the switching can be based on transmission quality as defined in Recommendation G.821 and by agreement between Administrations. In this case the transmitted signals need to have a standard frame structure in accordance with Recommendation G.704 which for 2048 kbit/s should also include the CRC4 option.
+
+It is recommended that the time required for the above response actions, that is the “confirmation time” plus the “restoration transfer time” should be less than 10 ms for terrestrial routes and 500 ms for satellite routes.
+
+TABLE 1/G.181
+
+#### **Response criteria for the hybrid H at the transmit side**
+
+| Fault condition | Consequent action (signal at II and III) |
+|-----------------------------------------------------------------------------------------------------|---------------------------------------------|
+| No signal at I | AIS |
+| AIS receive at I | AIS |
+| Failure of power supply, system failure | AIS (if possible a) ) |
+| a) The equipment may not be able to send AIS; this depends on the nature of the failure. | |
+
+TABLE 2/G.181
+
+#### **Switching criterion for the RSE at the receive side**
+
+| Condition | Consequence action | Remark | |
+|----------------------------------------------------|-------------------------------------------------------|-----------------------------------|--------|
+| Received signal II' and III' | (See Note) | Signal at IV | |
+| Received signal at II' AIS or no signal at III' | Switch to II' | Signal at IV | |
+| Received signal at III' AIS or no signal at II' | Switch to III' | Signal at IV | |
+| AIS at II' and III' | Switch to II' or III' | Received AIS is through-connected | |
+| No signal at II' and III' | The switching equipment sends AIS at IV | | |
+| AIS at II' and no signal at III' | Switch to II' | Received AIS is | |
+| AIS at III' and no signal at II' | Switch to III' | through-connected | |
+| Correct signal at II' Bad quality at III' | Switch to II' | Correct signal at IV | Option |
+| Correct signal at III' Bad quality at II' | Switch to III' | Idem | |
+| Bad quality at II' AIS or no signal at III' | Switch to II' | Bad quality at IV | |
+| Bad quality at III' AIS or no signal at II' | Switch to III' | Idem | |
+| Bad quality at III' Bad quality at II' | (See Note) | Bad quality at IV | |
+| Failure of power supply system failure | The switching equipment sends AIS (if possible) at IV | | |
+
+NOTE – Switch to paths II/II' or III/III' if both paths have the same right. Switch to the path with the primary right if the other method is used (see 3.2.2).
\ No newline at end of file
diff --git a/marked/G/T-REC-G.212-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.212-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7d2dfe00f4cf9e5686d207d6a909d4a9686cefe1
--- /dev/null
+++ b/marked/G/T-REC-G.212-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b133508a80d1c9aa0d8d0acc0b8b606980d791f3a4679fa615e58e6c84726b96
+size 7306
diff --git a/marked/G/T-REC-G.214-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.214-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..04e1632fdd79eb5bb234b48097989a4fdb1be5cf
--- /dev/null
+++ b/marked/G/T-REC-G.214-198811-I_PDF-E/raw.md
@@ -0,0 +1,69 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**G.214**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+# **INTERNATIONAL ANALOGUE CARRIER SYSTEMS GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS** ---
+
+## **LINE STABILITY OF CABLE SYSTEMS**
+
+**ITU-T Recommendation G.214**
+
+(Extract from the *Blue Book*)
+
+---
+
+## NOTES
+
+1 ITU-T Recommendation G.214 was published in Fascicle III.2 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below).
+
+2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+### Recommendation G.214
+
+## LINE STABILITY OF CABLE SYSTEMS1)
+
+(Mar del Plata, 1968)
+
+Line regulation has a threefold purpose:
+
+- 1) to keep actual line relative levels within such limits that thermal or intermodulation noise never exceeds acceptable values;
+- 2) to keep levels at the ends of regulated-line sections within such limits that regulators of the following multiplex equipment are able to function;
+- 3) to ensure that regulation is precise enough to make it generally unnecessary to provide an automatic group regulator and/or supergroup regulator for the group, supergroup, etc., links set up on a single regulated-line section.
+
+It appears that all three objectives will be secured if levels at the end of the longest regulated section envisaged are stabilized to $\pm 1$ dB at any frequency in the band transmitted.
+
+The CCITT therefore *unanimously recommends that:*
+
+Designers of line-regulating systems take account of the daily and seasonal variations in temperature to which the cables and repeaters are likely to be subjected, the predictable ageing of components, and also the nominal range of variation of power supplies, assuming that appropriate precautions are taken in the placing of the cable, in the design of buildings and in regulation of power supplies.
+
+As a design objective for the residual effects of sustained power and temperature variations, and the predictable ageing of components, over the ranges expected in any period between two successive manual adjustments, the change in insertion gain of a regulated-line section at any frequency in the transmitted band should not exceed 1 dB.
+
+For the purposes of this Recommendation, it is assumed that a regulated-line section will not be longer than a homogeneous section of the hypothetical reference circuit applicable to the type of system considered and that the interval between two successive manual adjustments will be not less than a fortnight.
+
+The variations in gain of a regulated-line section in service is also affected by maintenance operations and adjustments. The design objective excludes these effects.
+
+Moreover, the dynamic stability of the regulating system should be such that any swinging of the gain is damped and at a suitable rate as a result of an abrupt change in pilot level. If, for example, the pilot level is suddenly increased by 2 dB at the origin of the regulated-line section, the pilot level must not increase or diminish by more than 2 dB at the end of the regulated-line section. The resulting fluctuations in pilot level must fall off progressively.
+
+*Note* - It may be desirable to specify immunity of the regulating system to interference from components of television signals when transmitted.
+
+## Reference
+
+- [1] CCITT Recommendation *Stability of transmission*, Vol. IV, Rec. M.160.
+
+---
+
+1) Stability of transmission is also the subject of Recommendation M.160 of Volume IV [1].
\ No newline at end of file
diff --git a/marked/G/T-REC-G.215-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.215-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..99138d38ec6676f0023e3605f9b4fe5e3951d147
--- /dev/null
+++ b/marked/G/T-REC-G.215-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa65ab234ca7d71e8a87800bda77e2a00132c8ba26ed84ea2f9a86d51172b89d
+size 7471
diff --git a/marked/G/T-REC-G.215-198811-I_PDF-E/b612b838f94982799a69461ffb078a73_img.jpg b/marked/G/T-REC-G.215-198811-I_PDF-E/b612b838f94982799a69461ffb078a73_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b0f3b512309213defbb18575807848d29e0e29f7
--- /dev/null
+++ b/marked/G/T-REC-G.215-198811-I_PDF-E/b612b838f94982799a69461ffb078a73_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9c6cfed8e178e0cca0d955110952e8f669f622599be7194e8d4b5deeed956d08
+size 33299
diff --git a/marked/G/T-REC-G.215-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.215-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3c6853097d2a4949a90fe7cbb5eebedf2ed28345
--- /dev/null
+++ b/marked/G/T-REC-G.215-198811-I_PDF-E/raw.md
@@ -0,0 +1,86 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**G.215**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+# **INTERNATIONAL ANALOGUE CARRIER SYSTEMS GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS** ---
+
+## **HYPOTHETICAL REFERENCE CIRCUIT OF 5000 KM FOR ANALOGUE SYSTEMS**
+
+**ITU-T Recommendation G.215**
+
+(Extract from the *Blue Book*)
+
+---
+
+### NOTES
+
+1 ITU-T Recommendation G.215 was published in Fascicle III.2 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below).
+
+2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+### **HYPOTHETICAL REFERENCE CIRCUIT OF 5000 km FOR ANALOGUE SYSTEMS**
+
+*(Geneva, 1980)*
+
+#### **1 Composition of the hypothetical reference circuit**
+
+This hypothetical reference circuit is 5000 km long and applies to various types of carrier systems on coaxial cable and radio-relay systems, specially designed for very long international circuits. It has, for each direction of transmission, a total of:
+
+- one pair of channel modulators which includes translation from the audio-frequency band to the basic group and vice versa;
+- three pairs of group modulators, each pair including translation from the basic group to the basic supergroup and vice versa;
+- six pairs of supergroup modulators, each pair including translation from the basic supergroup to a higher order modem and vice versa;
+- twelve pairs of higher order modulators, each pair providing the necessary modulation stages to and from the line frequency.
+
+Figure 1/G.215 shows the principle of the hypothetical reference circuit.
+
+This hypothetical reference circuit consists of 12 homogeneous sections of equal length (see Recommendation G.212). Two homogeneous sections may be connected in tandem without translating equipment at the junction if the transmission system has suitable line regulating capability and does not introduce undesirable noise and crosstalk into any telephone channel.
+
+
+
+Diagram of a hypothetical reference circuit of 5000 km. The diagram shows a horizontal line representing the circuit, with 12 distinct sections marked by vertical bars. Above the line, a double-headed arrow indicates a total length of 5000 km. Below the line, each section is represented by a group of vertical rectangles of varying heights, representing different types of modulators. The text 'CCITT - 41970' is visible in the bottom right corner of the diagram area.
+
+*Note* - Each homogenous section has a length of approximately 420 km.
+
+FIGURE 1/G.215
+**Diagram of a hypothetical reference circuit of 5000 km**
+
+#### **2 Design objectives for circuit noise1) **
+
+The same noise values as for the 2500 km HRC apply (Recommendation G.222, § 1).
+
+*Note 1* - This design objective is in line with Recommendation G.123, "Circuit noise in national networks", which in § 2.1.1 recommends that the line noise in channels used to provide very long-distance circuits (over 2500 km) should not exceed 2 pW0p/km.
+
+1) Although the noise objective for the 5000 km HRC is in principle agreed, some countries will not be soon in the position to install equipment of the desired performance, and will continue to use existing systems on the very long national and international circuits, according to established planning and design practices.
+
+*Note 2* - Designers are expected to fit their noise distribution curves fall below all §§ 1.1 and 1.2 of Recommendation G.222.
+
+*Note 3* - In applying these design objectives, §§ 2.4 through 2.7 of Recommendation G.222 should be taken into account.
+
+The subdivision of the total noise between the various sources of noise is left entirely to the designer of the system, within the limits of 2500 pWOp for the terminal equipment and 7500 pWOp for the line. This allocation is intended to permit the use of modulating equipment meeting the maximum values recommended in Table 1/G.222 of Recommendation G.222 as indicated in Table 1/G.215.
+
+TABLE 1/G.215
+
+| Equipment | Maximum noise contributed by the send and receive side together | Number of modulator pairs | Total noise |
+|------------------------------|-----------------------------------------------------------------|---------------------------|-------------|
+| Channel modulators | 200 pWOp | 1 | 200pWOp |
+| Group modulators | 80 pWOp | 3 | 240 pWOp |
+| Supergroup modulators | 60 pWOp | 6 | 360 pWOp |
+| Higher order modulators | 120 pWOp | 12 | 1440 pWOp |
+| Through connecting equipment | – | – | 260 pWOp |
+| Total: | | | 2500 pWOp |
+
+*Note* - This Table assumes two stages of modulation in the higher modulator.
\ No newline at end of file
diff --git a/marked/G/T-REC-G.226-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.226-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7
--- /dev/null
+++ b/marked/G/T-REC-G.226-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e
+size 7392
diff --git a/marked/G/T-REC-G.233-198811-I_PDF-E/252ea48d02dce93965b91746fb376f35_img.jpg b/marked/G/T-REC-G.233-198811-I_PDF-E/252ea48d02dce93965b91746fb376f35_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..91d6dcafc3227417dffbdfa6493602b2d04e98b7
--- /dev/null
+++ b/marked/G/T-REC-G.233-198811-I_PDF-E/252ea48d02dce93965b91746fb376f35_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b289497336c1b56d71bfd5dd5d6500fd25d9191e7d44feac72e3221a8dab8e8
+size 47945
diff --git a/marked/G/T-REC-G.233-198811-I_PDF-E/431b8889a0e7f676f0eef40859590349_img.jpg b/marked/G/T-REC-G.233-198811-I_PDF-E/431b8889a0e7f676f0eef40859590349_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b31bbf1c4b1405b44b06c3c1d250cfe0ba239e98
--- /dev/null
+++ b/marked/G/T-REC-G.233-198811-I_PDF-E/431b8889a0e7f676f0eef40859590349_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:20f385bec3759b928edfd511300bb5159928185197eaccf8ca588c66253fa293
+size 42057
diff --git a/marked/G/T-REC-G.233-198811-I_PDF-E/de6e8b740c69dac308cce9edfec3eff4_img.jpg b/marked/G/T-REC-G.233-198811-I_PDF-E/de6e8b740c69dac308cce9edfec3eff4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..888f5f041cfd6c75831ec2ee087d70b79aec7c68
--- /dev/null
+++ b/marked/G/T-REC-G.233-198811-I_PDF-E/de6e8b740c69dac308cce9edfec3eff4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:01af44ce46759847df7ab6a8d2c0b599d9158d6e42df880ee67160b603f74cd0
+size 117056
diff --git a/marked/G/T-REC-G.233-198811-I_PDF-E/f961cbef0f8217e216b553bed270315b_img.jpg b/marked/G/T-REC-G.233-198811-I_PDF-E/f961cbef0f8217e216b553bed270315b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c17680db7168818f7079cf26693056ad72edff37
--- /dev/null
+++ b/marked/G/T-REC-G.233-198811-I_PDF-E/f961cbef0f8217e216b553bed270315b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:41a6dd9c02a902dbdf92f556149e39b39a217d5dc801febfd0449f913bcff2d7
+size 33121
diff --git a/marked/G/T-REC-G.422-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.422-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7
--- /dev/null
+++ b/marked/G/T-REC-G.422-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e
+size 7392
diff --git a/marked/G/T-REC-G.441-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.441-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7
--- /dev/null
+++ b/marked/G/T-REC-G.441-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e
+size 7392
diff --git a/marked/G/T-REC-G.441-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.441-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..f674641d275f2284d17ab2e661bef093dcc8b77b
--- /dev/null
+++ b/marked/G/T-REC-G.441-198811-I_PDF-E/raw.md
@@ -0,0 +1,80 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**G.441**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**INTERNATIONAL ANALOGUE CARRIER SYSTEMS
+GENERAL CHARACTERISTICS OF INTERNATIONAL
+CARRIER TELEPHONE SYSTEMS ON
+RADIO - RELAY OR SATELLITE LINKS AND
+INTERCONNECTION WITH METALLIC LINES**
+
+---
+
+**PERMISSIBLE CIRCUIT NOISE ON
+FREQUENCY - DIVISION MULTIPLEX
+RADIO - RELAY SYSTEMS**
+
+**ITU-T Recommendation G.441**
+
+(Extract from the *Blue Book*)
+
+---
+
+# NOTES
+
+- 1 ITU-T Recommendation G.441 was published in Fascicle III.2 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below).
+- 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## Recommendation G.441
+
+## PERMISSIBLE CIRCUIT NOISE ON FREQUENCY-DIVISION MULTIPLEX RADIO-RELAY SYSTEMS
+
+### 1 Design objectives for noise on hypothetical reference circuits
+
+In CCIR Recommendation 3931) [1] it is recommended:
+
+"1 that the noise power at a point of zero relative level in any telephone channel on a 2500-km hypothetical reference circuit for frequency-division multiplex radio-relay systems should not exceed the values given below, which have been chosen to take account of fading:
+
+- 1.1 7500 pW0p, psophometrically weighted,2) one-minute mean power,3) for more than 20% of any month;
+- 1.2 47 500 pW0p, psophometrically weighted,2) one-minute mean power,3) for more than 0.1 % of any month;
+- 1.3 1 000 000 pW0, unweighted (with an integrating time of 5 ms), for more than 0.01% of any month."
+
+Adding these values to the 2500 pW0p of psophometric power allowed for multiplexing equipment (Recommendation G.222, § 3) gives the recommended objectives shown in Recommendation G.222, § 1.1 for the telephone transmission and signalling aspect. CCIR Recommendation 393 [1] gives the conditions for applying these objectives to radio-relay systems; these conditions are in general the same as those given in Recommendation G.222, § 2 and in Recommendation G.223.
+
+The CCIR has not yet recommended any noise objectives in connection with voice-frequency telegraph transmission. CCITT Recommendation G.442 covers this aspect.
+
+### 2 Noise on real circuits
+
+(See CCIR Recommendation G.395 [3].)
+
+## References
+
+- [1] CCIR Recommendation *Allowable noise power in the hypothetical reference circuit for radio-relay systems for telephony using frequency division multiplex*, Vol. IX, Rec. 393, Dubrovnik, 1986.
+- [2] CCIR Recommendation *Allowable noise power in the hypothetical reference circuit of transhorizon radio-relay systems for telephony using frequency division multiplex*, Vol. IX, Rec. 397, Dubrovnik, 1986.
+- [3] CCIR Recommendation *Noise in the radio portion of circuits to be established over real radio-relay links for FDM telephony*, Vol. IX, Rec. 395, Dubrovnik, 1986.
+
+---
+
+1) This Recommendation relates only to "line-of-sight" radio-relay systems. Trans-horizon radio-relay systems are dealt with in Recommendation 397 [2].
+
+2) The level of uniform-spectrum noise power in a 3.1-kHz band must be reduced by 2.5 dB to obtain the psophometrically weighted noise power.
+
+3) For carrier transmission systems with one minute mean noise power distributions which are not well defined, the inclusion of another one minute mean noise clause would be desirable to ensure equivalent performance for all systems. This clause would specify that:
+
+The mean psophometric noise power over one minute shall not exceed 20 000 pW0p for more than 3% of any month.
+
+This clause has not been specifically included because CCIR has determined that for radio-relay links the application of clauses 1.2.1 and 1.2.2 are sufficient to ensure, with high probability, that the additional clause will also be satisfied.
\ No newline at end of file
diff --git a/marked/G/T-REC-G.601-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.601-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..7f524203c4c0feb039fbe06e444c0b797c8d761d
--- /dev/null
+++ b/marked/G/T-REC-G.601-198811-I_PDF-E/raw.md
@@ -0,0 +1,331 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**G.601**
+
+**TRANSMISSION MEDIA CHARACTERISTICS**
+
+---
+
+**TERMINOLOGY FOR CABLES**
+
+**ITU-T Recommendation G.601**
+
+(Extract from the *Blue Book*)
+
+---
+
+# NOTES
+
+1 ITU-T Recommendation G.601 was published in Fascicle III.3 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below).
+
+2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## TERMINOLOGY FOR CABLES
+
+(Geneva, 1980)
+
+## 1 General terms: repeaters, power feeding, etc.
+
+### 1001 repeater
+
+*F: répéteur*
+
+*S: repetidor*
+
+An equipment essentially including one or several amplifiers and/or *regenerators*, and associated devices, inserted at a point in a transmission medium.
+
+*Note - A repeater may operate in one or both directions of transmission.*
+
+### 1002 analogue repeater; analog repeater
+
+*F: répéteur analogique*
+
+*S: repetidor analógico*
+
+A *repeater* for amplifying analogue signals or *digital signals* and capable of other functions, but excluding *regeneration of digital signals*.
+
+### 1003 regenerative repeater
+
+*F: répéteur régénérateur*
+
+*S: repetidor regenerativo*
+
+A *repeater* ensuring *regeneration of digital signals*, and capable of other functions.
+
+*Note - This definition is different from that given in Recommendation G.701 [1]. At the time when Recommendation G.701 was drafted, a suitable CCITT definition of *repeater* was not available. The ensemble of definitions given here makes it desirable to incorporate the *regenerative repeater* in the family of transmission systems, instead of defining it only as a device, as is the case in Recommendation G.701.*
+
+### 1004 directly powered (repeater) station
+
+*F: station (de répéteurs) à alimentation indépendante*
+
+*S: estación (de repetidores) alimentada directamente*
+
+A *repeater station* which receives its electric power directly from the local mains or from a local generator.
+
+### 1005 power feeding (repeater) station
+
+*F: station d'alimentation (de répéteurs)*
+
+*S: estación (de repetidores) de telealimentación*
+
+A *directly powered repeater station* which supplies electric power to other *repeater stations*
+
+### 1006 **dependent (repeater) station**
+
+*F: station (de répéteurs) téléalimentée*
+
+*S: estación (de repetidores) telealimentada*
+
+A *repeater station* which receives its electric power supply from a *power feeding repeater station*.
+
+*Note* - Electric power may be conveyed to the dependent station either by the physical transmission medium itself, or by conductors in the same cable sheath, or by exterior cables.
+
+### 1007 **section termination**
+
+*F: extrémité de section*
+
+*S: extremo de sección*
+
+A point selected conventionally to be the interface between the physical transmission medium and associated equipment such as *repeaters*.
+
+*Note* - The precise selection of the point to constitute the section termination should take into account associated accessories such as splices, connectors or flexible connecting cables in order to include them, as the case may be, on one side or on both sides of the termination.
+
+### 1008 **elementary cable section**
+
+*F: section élémentaire de câble*
+
+*S: sección elemental de cable*
+
+All of the physical transmission media and accessories such as splices, connectors or flexible connecting cables included between two consecutive *section terminations*.
+
+### 1009 **elementary repeated section**
+
+*F: section élémentaire amplifiée*
+
+*S: sección elemental con amplificación*
+
+In a given direction of transmission an *elementary cable section* together with the immediately following *analogue repeater*, all included between two *section terminations*.
+
+### 1010 **elementary regenerated section**
+
+*F: section élémentaire régénérée*
+
+*S: sección elemental con regeneración*
+
+In a given direction of transmission, an *elementary cable section* together with the immediately following *regenerative repeater*, all included between two *section terminations*.
+
+### 1011 **take-up factor**
+
+*F: facteur de câblage*
+
+*S: factor de cableado*
+
+Ratio between the value of a linear parameter measured on the length unit of a cable and the value of the same parameter measured on the length unit of a pair of that cable.
+
+The result of cabling (assembly of components and possibly twisting of wires in pairs and then in quads) is that the length of the cable components is greater than that of the axial length of the cable. The take-up factor is the ratio between these two lengths.
+
+### 1012 Graphic illustration of the use of some terms in § 1.
+
+
+
+Diagram of a generic reference to repeaters and cable sections. It shows a signal path from left to right: a section termination 'a', a 'Repeater' block, a section termination 'b', an 'Elementary cable section' (labeled 'Physical transmission medium'), a section termination 'c', another 'Repeater' block, and a section termination 'd'. The distance between 'b' and 'c' is labeled 'Elementary cable section'. The distance between 'c' and 'd' is labeled 'Equipment'. The label 'CCITT - 32390' is at the bottom right. A note at the bottom left states 'a, b, c, d Section terminations'.
+
+FIGURE 1/G.601
+Terminology for generic reference to repeaters and cable sections
+
+
+
+Diagram of terminology for elementary repeated section. It shows two repeater blocks, 'A' and 'B', each containing two triangular repeater symbols. Between them is an 'Elementary cable section'. The distance from the input of repeater A to the input of repeater B is labeled 'Elementary repeated section (A → B)'. The distance from the output of repeater B back to the input of repeater A is labeled 'Elementary repeated section (B → A)'. The label 'CCITT - 32400' is at the bottom right. A note at the bottom left shows an 'X' symbol and the text 'Section termination'.
+
+FIGURE 2/G.601
+Terminology for elementary repeated section
+
+## 2 Terms concerning cables measurements
+
+### 2.1 Use of the word echo, in cable testing only
+
+#### 2101 echo
+
+*F: écho*
+
+*S: eco*
+
+An electric, acoustic or electromagnetic wave which arrives at a given point, after reflection or indirect propagation, with sufficient magnitude and delay for it to be perceptible at the given point, as a wave distinct from that directly transmitted.
+
+#### 2102 backward echo
+
+*F: écho (vers l'amont)*
+
+*S: eco hacia atrás*
+
+An *echo* arriving at a defined point and having a direction of transmission opposite to that of the direct signal.
+
+#### 2103 **forward echo**
+
+*F: écho vers l'aval, traînage*
+
+*S: eco hacia adelante*
+
+An *echo* arriving at a defined point and having the same direction of transmission as that of the direct signal.
+
+### 2.2 *Pulse measurements*
+
+#### 2201 **echometric measurement**
+
+*F: mesure échométrique*
+
+*S: medición ecométrica*
+
+A measurement made by studying the *echo* which follows the emission of a signal of limited duration, known as a "measuring signal", with a view to analyzing all the causes of reflections.
+
+#### 2202 **pulse duration**
+
+*F: durée d'une impulsion*
+
+*S: duración del impulso*
+
+The interval of time between the first and last instant at which the instantaneous value of a pulse (or of its envelope if a carrier frequency pulse is concerned) reaches a specified fraction of the peak amplitude.
+
+#### 2203 **sine-squared**
+
+*F: impulsion en sinus carré*
+
+*S: impulso en seno cuadrado*
+
+A unidirectional pulse defined by the expression:
+
+$$y = K \sin^2 (\pi t/2T); 0 \leq t \leq 2T$$
+
+$$y = 0; t < 0 \text{ and } t > 2T$$
+
+where
+
+*K* is the amplitude
+
+*T* is the *pulse duration* at half-amplitude
+
+*t* is the time.
+
+#### 2204 **pulse echo meter**
+
+*F: échomètre à impulsions*
+
+*S: ecómetro de impulsos*
+
+Apparatus designed to take *echometric measurements* by means of pulses.
+
+#### 2205 **elementary echo**
+
+*F: écho élémentaire*
+
+*S: eco elemental*
+
+In an *echometric measurement*, the state of the echo in a time interval of a duration comparable to that of the test signal.
+
+#### 2206 **peak amplitude of an elementary echo**
+
+*F: amplitude de crête d'un écho élémentaire*
+
+*S: amplitud de cresta de un eco elemental*
+
+Maximum value of echo amplitude reached in the duration of an *elementary echo*
+
+#### 2207 **relative amplitude of an elementary echo**
+
+*F: amplitude relative d'un écho élémentaire*
+
+*S: amplitud relativa de un eco elemental*
+
+Ratio between the *peak amplitude of an elementary echo* and the maximum amplitude of the measuring signal, evaluated at the emission point.
+
+#### 2208 **pulse echo return loss ; pulse echo attenuation**
+
+*F: affaiblissement d'écho*
+
+*S: pérdida de retorno para el eco; atenuacion de eco*
+
+*Relative amplitude of an elementary echo* expressed in transmission units.
+
+#### 2209 **amplitude-corrected echo**
+
+*F: écho corrigé en amplitude*
+
+*S: eco corregido en amplitud*
+
+An *echo* observed, after processing to carry out at least partial correction of propagation effects.
+
+#### 2210 **amplitude- and phase-corrected echo**
+
+*F: écho corrigé en amplitude et phase*
+
+*S: eco corregido en amplitud y en fase*
+
+An *echo* observed, after processing has been made to correct the propagation effects on the amplitude and shape of the echo.
+
+#### 2211 **echo curve**
+
+*F: courbe d'écho*
+
+*S: curva de eco*
+
+A graphic or oscilloscopic representation of *echo* amplitude function of time.
+
+*Note* - The echo may be corrected in amplitude or in amplitude and phase; the curve is then called, as the case may be, "amplitude-corrected echo curve" or "amplitude- and phase-corrected echo curve".
+
+#### 2212 **equivalent resistance error**
+
+*F: écart équivalent*
+
+*S: error de resistencia equivalente*
+
+The value of a hypothetical impedance deviation which, if situated at the end of a section of a transmission medium, would produce in an echometric measurement at that end the same reflected energy as all the irregularities of the section.
+
+#### 2213 **corrected equivalent resistance error**
+
+*F: écart équivalent corrigé*
+
+*S: error de resistencia equivalente corregido*
+
+*Equivalent resistance error* evaluated by an echometric measurement comprising echo correction. The correction may be effected in amplitude or in amplitude and phase or according to other criteria (e.g. in energy).
+
+*Note - The corrected equivalent resistance error* may be evaluated in terms of one kilometre, as the ratio $\Delta_k$ between corrected equivalent resistance error $\Delta_e$ as measured on a cable section, and the square root of the length $L$ of this section, in km.
+
+$$\Delta_k = \Delta_e / \sqrt{L} \Omega \cdot \text{km}^{-1/2}$$
+
+### 2.3 *Measurements made with sine-wave signals*
+
+#### 2301 **irregularity reflection coefficient**
+
+*F: facteur de réflexion sur les irrégularités*
+
+*S: coeficiente de reflexión de las irregularidades*
+
+The reflection coefficient measured at one end of a section of a transmission medium, for a specified mode of propagation, under conditions allowing for the elimination of the effects of reflections other than those due to irregularities inherent in the section concerned.
+
+#### 2302 **regularity loss**
+
+*F: affaiblissement de l'onde réfléchie sur les irrégularités*
+
+*S: pérdida de retorno por irregularidades*
+
+The expression in transmission units of the modulus of *irregularity reflection coefficient* $P_i$ . Its value in decibels is equal to:
+
+$$A_i = -20 \log_{10} |P_i|.$$
+
+## **Reference**
+
+- [1] CCITT Recommendation *Vocabulary of pulse code modulation (PCM) and digital transmission terms*, Vol III, Rec. G.701.
\ No newline at end of file
diff --git a/marked/G/T-REC-G.613-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.613-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7
--- /dev/null
+++ b/marked/G/T-REC-G.613-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e
+size 7392
diff --git a/marked/G/T-REC-G.614-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.614-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..b28f96eac43a30841d080d4b9c8437340bba22d1
--- /dev/null
+++ b/marked/G/T-REC-G.614-198811-I_PDF-E/raw.md
@@ -0,0 +1,179 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**G.614**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+# **TRANSMISSION MEDIA CHARACTERISTICS** ---
+
+**CHARACTERISTICS OF SYMMETRIC PAIR
+STAR-QUAD CABLES DESIGNED EARLIER
+FOR ANALOGUE TRANSMISSION SYSTEMS
+AND BEING USED NOW FOR DIGITAL
+SYSTEM TRANSMISSION AT BIT RATES
+OF 6 TO 34 Mbit/s**
+
+**ITU-T Recommendation G.614**
+
+(Extract from the *Blue Book*)
+
+---
+
+## NOTES
+
+1 ITU-T Recommendation G.614 was published in Fascicle III.3 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below).
+
+2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## **CHARACTERISTICS OF SYMMETRIC PAIR STAR-QUAD CABLES DESIGNED EARLIER FOR ANALOGUE TRANSMISSION SYSTEMS AND BEING USED NOW FOR DIGITAL SYSTEM TRANSMISSION AT BIT RATES OF 6 TO 34 Mbit/s**
+
+*(Melbourne, 1988)*
+
+## **1 Introduction**
+
+This Recommendation relates to symmetric pair star-quad cables which have been designed earlier and used to provide 60 or 120 carrier telephone channels of analogue transmission systems on each quad pair. Further, after reconstruction of the line, these cables are used for digital system transmission at bit rates of 6 to 34 Mbit/s. The cables concerned have no screened pairs and quads.
+
+For digital transmission systems with a bit rate of 8 Mbit/s both one-cable and two-cable operations may be used. For systems with a bit rate of 34 Mbit/s two-cable operation is used only.
+
+For digital transmission systems both several, or all cable pairs may be used.
+
+## **2 Parameters to be measured**
+
+All parameters specified in Recommendation G.612, namely characteristic impedance, attenuation coefficient, far-end crosstalk between pairs on the same direction of transmission, and near-end crosstalk between pairs of two different cables intended for different directions of transmission are to be measured. If the cable is intended for use with both directions of transmission it is also necessary to measure the near-end crosstalk between pairs intended for different directions of transmission.
+
+### **2.1 *Characteristics impedance***
+
+The characteristics impedance is measured according to § 2.1 of Recommendation G.612.
+
+### **2.2 *Attenuation coefficient***
+
+The attenuation coefficient is measured according to § 2.2 of Recommendation G.612.
+
+### **2.3 *Crosstalk***
+
+The crosstalk is specified in sinusoidal mode at a frequency near the timing half-frequency of the digital system and/or at other frequencies. Digital mode of measuring may be used also.
+
+#### **2.3.1 *Measurement of far-end crosstalk between pairs of different quads***
+
+The measurement of the far-end crosstalk is carried out on pairs used in the same direction of transmission at a frequency above about 0.1 MHz when a length of cable is $L$ . If the frequency of measurements differs from the timing half-frequency of the digital transmission system the value to be measured will be corrected to the factor $20 \log_{10} f$ . The values are corrected to the length of 1000 m by the factor $10 \log_{10} L$ .
+
+#### **2.3.2 *Measurement of far-end crosstalk between pairs of the same quad***
+
+This measurement is carried out at a cable length equal to maximum permissible length of regenerator section of digital transmission system with bit rates of 6 to 34 Mbit/s at a frequency above about 1.0 MHz (measurement is carried out for each rate of digital transmission system separately) with systematic component of crosstalk in the same quad compensated. The compensation of systematic crosstalk component is carried out by one of the approximately equivalent transposition patterns (see Figure 1/G.614). When regenerator sections are of less length these methods of falling the elementary cable sections into separate parts and of transposition in quad provide the greater values of the far-end crosstalk between pairs than those values when measurements are carried out at, a maximum length of regenerator section.
+
+
+
+Diagram showing six transposition patterns (I-VI) for pairs of wires. Each pattern shows two pairs of wires (Pair 1 and Pair 2) crossing over three sleeves (Sleeve 1, Sleeve 2, Sleeve 3). The patterns illustrate different ways to cross the wires to achieve specific crosstalk characteristics. Pattern I shows a simple cross. Pattern II shows a more complex cross with additional arcs. Patterns III-VI show variations of these crosses. The diagram is labeled 'FIGURE 1/G.614' and 'TT501200-88'.
+
+*Note 1* - Transposition pattern No. 1 was proposed by the Netherlands Administration in 1978 (see COM XV-135, period 1977-1980).
+
+*Note 2* - Transposition pattern No. 2 has been proposed by the German Democratic Republic Administration.
+
+*Note 3* - Transposition patterns Nos. 3, 4, 5 and 6 are proposed by the USSR Administration.
+
+FIGURE 1/G.614
+
+#### 2.3.3 *Measurement of near-end crosstalk between pairs of the same or different cables intended for different directions of transmission*
+
+This measurement is carried out either between pairs of the same cable (when one-cable operation is used), or between pairs of two different cables intended for different directions of transmission (when two-cable operation is used). The measurements are carried out both in sinusoidal and digital modes.
+
+## 3 Cable specification
+
+Administrations which decided to use cables designed earlier and used for analogue carrier systems with up to 120 channels in digital operation at bit rates 6 to 34 Mbit/s are recommended to choose cables with characteristics given in Tables 1/G.614 and 2/G.614.
+
+### 3.1 *Tables used for digital transmission systems with bit rates of 6 to 8 Mbit/s in one-cable operation*
+
+See Table 1/G.614.
+
+TABLE 1/G.614
+
+| Characteristics | Requirements | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|----------------|-----------------|
+| | I (Note 1) | II (Note 1) | III (Note 1) |
+| Types of cable | | | |
+| Operational bit rate C, kbit/s | 8448 | 8448 | 8448 |
+| Line code | HDB-3 | HDB-3 | HDB-3 |
+| Modulation rate, kbaud | 8448 | 8448 | 8448 |
+| Tolerate attenuation of regenerator section at a frequency of C/2 when pairs of cable are of maximum use and directions of transmission are set in different quads (maximum permissible value), dB | 23 | 23 | 45 (Note 3) |
+| Diameter of copper conductor, mm | 1.2 | 1.2 | 1.3 |
+| Previous cable operating range | HF | HF | AF, HF |
+| Type of insulation | PI | PI | PI, P |
+| Number of star quads | 4 | 7 (Note 2) | 3, 4, 8 |
+| Characteristic impedance at 1 MHz, ohms | 165 | 165 | 170 |
+| Nominal capacity, nF/km | 24.5 | 24.5 | 21.0 |
+| Attenuation coefficient, dB/km at 10°C | | | |
+| - at 1 MHz | 4.8 | 4.5 | 3.7 |
+| -at a frequency C/2 | 10.6 | 9.7 | 8.0 |
+| Near-end crosstalk at a frequency of C/2, dB | | | |
+| -mean value | 48 | 50 | 50 |
+| -minimum value | 34 | 34 | 44 |
+| Far-end crosstalk between pairs of different quads (minimum value referred to 1,000 m), dB | | | |
+| - at 1 MHz | 54 | 54 | 60 |
+| - at a frequency of C/2 | 42 | 42 | 48 |
+| Far-end crosstalk between pairs of the same quad (minimum value at regenerator section of maximum length), dB | | | |
+| - at 1 MHz | 60 | 60 | 60 |
+| - at a frequency of C/2 | 43 | 43 | 48 |
+
+Note 1 - These characteristics relate to cables with aluminium covering.
+
+Note 2 - Central quad not used for digital system transmission.
+
+Note 3 - Regenerators of the transmission direction B-A installed in midpoint of the section of the opposite direction A-B.
+
+HF High-frequency
+
+AF Audio-frequency
+
+PI String polysterene
+
+P Paper
+
+### 3.2 Cables used for digital transmission systems with bit rates of 6 to 34.368 Mbit/s in two-cable operation
+
+See Table 2/G.614.
+
+TABLE 2/G.614
+
+| Characteristics | Requirements | | |
+|---------------------------------------------------------------------------------------------------------------------------|---------------|----------------|-----------------|
+| | I (Note 1) | II (Note 1) | III (Note 1) |
+| Type of cable | | | |
+| Operational bit rate C, kbit/s | 8448 | 34 368 | 34 368 |
+| Line code | HDB-3 | 5B6B | 5B6B |
+| Modulation rate, kbaud | 8448 | 41 242 | 41 242 |
+| Attenuation of regenerator section at a frequency of C/2 when all pairs of cable are used (maximum permissible value), dB | 70 | 85 | 85 |
+| Diameter of copper conductor, mm | 1.2 | 1.2 | 1.3 |
+| Number of star quads | 4 | 4 | 3, 4, 8 |
+| Characteristic impedance at 1 MHz, ohms | 165 | 165 | 170 |
+| Nominal capacity, nF/km | 24.5 | 24.5 | 21.0 |
+| Attenuation coefficient, dB/km at 10°C | | | |
+| - at 1 MHz | 4.8 | 4.8 | 3.7 |
+| - at a frequency C/2 | 10.6 | 24.0 | 17.0 |
+| Far-end crosstalk between pair of different quads (minimum value referred to 1,000m), dB | | | |
+| - at 1 MHz | 54 | 51 | 60 |
+| - at 4 MHz | 42 | 42 | 48 |
+| - at 12 MHz | - | 32 | 30 |
+| - at 17 MHz | - | 30 | 26 |
+| Far-end crosstalk between pairs of the same quad (minimum value at a regenerator section of maximum length), dB | | | |
+| - at 1 MHz | 42 | - | 60 (Note 3) |
+| - at 4 MHz | 30 | 33 (Note 2) | 48 (Note 3) |
+| - at 12 MHz | - | 17 (Note 2) | 27 (Note 3) |
+| - at 17 MHz | - | 13 (Note 2) | 17 (Note 3) |
+
+Note 1 - These characteristics relate to cables with aluminium covering.
+
+Note 2 - These values are obtained by means of transposition pattern No. 5 (see Figure 1/G.614) for four cable lengths (0.825 km).
+
+Note 3 - These values are obtained by means of transposition pattern No. 2 (see Figure 1/G.614).
\ No newline at end of file
diff --git a/marked/G/T-REC-G.641-202511-I_PDF-E/raw.md b/marked/G/T-REC-G.641-202511-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..43da25b919c333dba7cbadb70da53150cfc83e1e
--- /dev/null
+++ b/marked/G/T-REC-G.641-202511-I_PDF-E/raw.md
@@ -0,0 +1,661 @@
+
+
+# Recommendation**ITU-T G.641 (11/2025)**
+
+SERIES G: Transmission systems and media, digital systems and networks
+
+Transmission media and optical systems characteristics –
+Free space optical systems
+
+---
+
+# **Terrestrial free-space optics for mobile backhaul with short reach interfaces**
+
+
+
+The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with a white grid pattern, overlaid by the letters 'ITU' in a bold, blue, sans-serif font. The globe is stylized with a white arrow pointing upwards and to the right, symbolizing global communication and progress.
+
+ITU logo
+
+## ITU-T G-SERIES RECOMMENDATIONS
+
+## Transmission systems and media, digital systems and networks
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100-G.199 |
+| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200-G.299 |
+| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300-G.399 |
+| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400-G.449 |
+| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450-G.499 |
+| TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS | G.600-G.699 |
+| General | G.600-G.609 |
+| Symmetric cable pairs | G.610-G.619 |
+| Land coaxial cable pairs | G.620-G.629 |
+| Submarine cables | G.630-G.639 |
+| Free space optical systems | G.640-G.649 |
+| Optical fibre cables | G.650-G.659 |
+| Characteristics of optical components and subsystems | G.660-G.679 |
+| Characteristics of optical systems | G.680-G.699 |
+| DIGITAL TERMINAL EQUIPMENTS | G.700-G.799 |
+| DIGITAL NETWORKS | G.800-G.899 |
+| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900-G.999 |
+| MULTIMEDIA QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER-RELATED ASPECTS | G.1000-G.1999 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.6000-G.6999 |
+| DATA OVER TRANSPORT – GENERIC ASPECTS | G.7000-G.7999 |
+| PACKET OVER TRANSPORT ASPECTS | G.8000-G.8999 |
+| ACCESS NETWORKS | G.9000-G.9999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+# Recommendation ITU-T G.641
+
+# Terrestrial free-space optics for mobile backhaul with short reach interfaces
+
+## Summary
+
+Recommendation ITU-T G.641 provides optical interface specifications for free-space optics (FSO) applications, primarily intended for mobile backhaul with short reach. Applications are defined using optical interface parameters. This Recommendation specifies both the FSO interface and the fibre interface.
+
+### History\*
+
+| Edition | Recommendation | Approval | Study Group | Unique ID |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0 | ITU-T G.641 | 2025-11-29 | 15 | 11.1002/1000/16549 |
+
+## Keywords
+
+Mobile backhaul, terrestrial free-space optics.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at .
+
+© ITU 2026
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+###### Page
+
+| | | |
+|-----|------------------------------------------------------------------------------------------------------------------|----|
+| 1 | Scope..... | 1 |
+| 2 | References..... | 1 |
+| 3 | Definitions ..... | 2 |
+| 3.1 | Terms defined elsewhere ..... | 2 |
+| 3.2 | Terms defined in this Recommendation..... | 2 |
+| 4 | Abbreviations and acronyms ..... | 2 |
+| 5 | Conventions ..... | 2 |
+| 6 | Classification of optical interfaces..... | 3 |
+| 6.1 | Applications..... | 3 |
+| 6.2 | Reference points ..... | 3 |
+| 6.3 | Nomenclature ..... | 4 |
+| 6.4 | Application codes ..... | 4 |
+| 7 | Parameter definitions ..... | 4 |
+| 7.1 | General information..... | 5 |
+| 7.2 | Interface at point SS ..... | 6 |
+| 7.3 | Interface at point FPS ..... | 6 |
+| 7.4 | Free-space optical path from point FPs to FPR..... | 7 |
+| 7.5 | Interface at point FPR..... | 7 |
+| 7.6 | Interface at point RS..... | 8 |
+| 8 | Parameter values ..... | 8 |
+| 9 | Optical safety considerations ..... | 9 |
+| | Appendix I – Definitions of free-space optical link related parameters and calculation of link attenuation ..... | 10 |
+| I.1 | Visibility ..... | 10 |
+| I.2 | Scintillation..... | 10 |
+| I.3 | Definition of angle of arrival (AOA) loss and AOA statistical model..... | 11 |
+| I.4 | Definition of solar radiation ..... | 12 |
+| I.5 | Calculation of link attenuation ..... | 12 |
+| | Appendix II – A media model for bidirectional application..... | 14 |
+| | Bibliography..... | 15 |
+
+
+
+# Recommendation ITU-T G.641
+
+# Terrestrial free-space optics for mobile backhaul with short reach interfaces
+
+# 1 Scope
+
+The purpose of this Recommendation is to provide optical interface specifications for free-space optics (FSO) short-reach terrestrial applications towards realization of transversely compatible point to point systems in C band, primarily intended for mobile backhaul. O band applications are also in scope but are not specified in this version of the Recommendation.
+
+The FSO system specified in this Recommendation is protocol and data rate transparent. The transition from optical fibre to FSO and vice versa is protocol and data rate transparent as well. The optical interface specified in this Recommendation assumes the presence of an acquisition, tracking and pointing (ATP) mechanism, which is not part of this Recommendation.
+
+The specifications in this Recommendation are organized according to application codes.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [[ITU-T G.652](#)] Recommendation ITU-T G.652 (2024), *Characteristics of a single-mode optical fibre and cable*.
+- [[ITU-T G.664](#)] Recommendation ITU-T G.664 (2012), *Optical safety procedures and requirements for optical transmission systems*.
+- [[ITU-T G.698.2](#)] Recommendation ITU-T G.698.2 (2018), *Amplified multichannel dense wavelength division multiplexing applications with single channel optical interfaces*.
+- [[ITU-T G.826](#)] Recommendation ITU-T G.826 (2002), *End-to-end error performance parameters and objectives for international, constant bit-rate digital paths and connections*.
+- [[ITU-T G.828](#)] Recommendation ITU-T G.828 (2000), *Error performance parameters and objectives for international, constant bit-rate synchronous digital paths*.
+- [[ITU-T G.959.1](#)] Recommendation ITU-T G.959.1 (2024), *Optical transport network physical layer interfaces*.
+- [[ITU-T L.109](#)] Recommendation ITU-T L.109 (2024), *Construction of optical/metallic hybrid cables*.
+- [ITU-R F.2106-1] Report ITU-R F.2106-1 (2010), *Fixed service applications using free-space optical links*.
+- [ITU-R P.1814-1] Recommendation ITU-R P.1814-1 (2025), *Prediction methods required for the design of terrestrial free-space optical links*.
+- [ITU-R P.1817-1] Recommendation ITU-R P.1817-1 (2012), *Propagation data required for the design of terrestrial free-space optical links*.
+
+- [IEC 60825-1] IEC 60825-1 (2014), *Safety of laser products – Part 1: Equipment classification and requirements*.
+- [IEC 60825-2] IEC 60825-2 (2010), *Safety of laser products – Part 2: Safety of optical fibre communication systems (OFCs)*.
+- [IEC 60825-12] IEC 60825-12 (2022), *Safety of laser products – Part 12: Safety of free-space optical communication systems used for transmission of information*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+- 3.1.1 optical tributary signal (OTSi)** [ITU-T G.959.1].
+- 3.1.2 optical tributary signal class NRZ 10G** [ITU-T G.959.1].
+- 3.1.3 errored second** [ITU-T G.826] and [ITU-T G.828].
+- 3.1.4 severely errored second** [ITU-T G.826] and [ITU-T G.828].
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+- 3.2.1 free-space optical signal:** Optical signal that is transmitted from a free space source main path interface (FPS ) to a free space receive main path interface (FPR ).
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+- AOA Angle of Arrival
+- ATP Acquisition, Tracking and Pointing
+- BER Bit Error Ratio
+- ES Errored Second
+- FSO Free-Space Optics
+- NRZ Non-Return to Zero
+- OSNR Optical Signal to Noise Ratio
+- Rx Receiver
+- SES Severely Errored Second
+- Tx Transmitter
+- WDM Wavelength Division Multiplexing
+
+# 5 Conventions
+
+This Recommendation uses the following conventions:
+
+- FPR Free space Receive main Path interface
+- FPS Free space Source main Path interface
+- Rs Single-channel Receive
+
+Ss Single-channel Source
+
+# 6 Classification of optical interfaces
+
+## 6.1 Applications
+
+This Recommendation provides physical layer parameters and values for channel interfaces of free-space optics (FSO) systems in point-to-point applications. These FSO systems are primarily intended to be used in terrestrial mobile backhaul networks.
+
+The specification method in this Recommendation uses a "black link" approach, which means that optical interface parameters for both single channel optical tributary and free-space signal are specified. This approach enables transverse compatibility at both single fibre channel and free-space reference points using a FSO black box configuration. The specification methodology in this Recommendation assumes the guidelines in [ITU-R F.2106-1].
+
+Wavelength division multiplexing (WDM) applications are in the scope of this Recommendation but are not considered in the current version.
+
+## 6.2 Reference points
+
+### 6.2.1 Two-fibre bidirectional applications
+
+Figure 6-1 shows reference points for two-fibre bidirectional connections (interfaces Ss and Rs ) of transmitter (Tx) and receiver (Rx) and for the free-space link between FSO network elements (interfaces FPS and FPR ).
+
+As shown in Figure 6-1, the black link consists of a free-space black link and two free-space networking elements, or FSO black box, whose main function is coupling the light signal from fibre to free-space and vice versa. The FSO black box may contain optical amplifiers, as specified by the application code.
+
+The reference points in Figure 6-1 are defined as follows:
+
+- Ss is a single channel reference point at free-space network element tributary input. It is the output port of the Tx from the tributary side transceiver and the input port of the FSO black box;
+- Rs is a single channel reference point at free-space network element tributary output. It is the input port of the Rx from the tributary side transceiver and the output port of the FSO black box
+- FPS is a free-space reference point at free-space network element output;
+- FPR is a free-space reference point at free-space network element input.
+
+The fibres connecting Tx/Rx and free-space network elements are part of the black link. The maximum fibre length shall be compatible with the application codes in [ITU-T G.959.1] or [ITU-T G.698.2] used at the Ss and Rs interfaces of the black link or in case of hybrid cables with the length specified in [ITU-T L.109].
+
+The FSO link is bidirectional, meaning that the centres of transmitter and the receiver lens at FPS and FPR points are on the same axis.
+
+
+
+Diagram of a linear 'black link' approach for two-fibre bidirectional application. It shows two 'Free-space network elements' connected by a 'Free space' link. Each element contains a 'Fibre' connected to an 'FSO black box'. The FSO black box is connected to a 'Tx' (Transmitter) and an 'Rx' (Receiver) via interface points Ss and Rs. The FSO black box is also connected to the 'Free space' link via interface points FPs and FPRs. The diagram is labeled G.641(25).
+
+**Figure 6-1 – Linear "black link" approach for two-fibre bidirectional application**
+
+## 6.3 Nomenclature
+
+The application code identifies the network, implementation and architectural characteristics of an application.
+
+The application code notation is constructed as follows:
+
+**WDL-x-a**
+
+where:
+
+- **W** is a letter indicating the operating wavelength, such as:
+ - **C** indicating C band with nominally 1 550 nm laser source.
+- **D** is a letter indicating the highest class of optical tributary signal supported:
+ - **3** indicating NRZ 10G.
+- **L** is a letter indicating the distance from FPs to FPRs, such as:
+ - **s** indicating short reach up to 2 km.
+- **x** is fibre type at Ss and Rs:
+ - **2** indicating ITU-T G.652 fibre.
+- **a** if present, indicates the application code uses optical amplifiers.
+
+## 6.4 Application codes
+
+Table 6-1 summarizes the single-channel application codes, according to the nomenclature in clause 6.3.
+
+**Table 6-1 – Classification of applications**
+
+| Application | Short reach |
+|----------------------------------------|-------------|
+| Optical tributary signal class NRZ 10G | C3s-2-a |
+
+# 7 Parameter definitions
+
+Table 7-1 provides interface points and clauses for the definition of the parameters used in this Recommendation.
+
+**Table 7-1 – Physical layer parameters for single channel free-space applications using the "black link" approach**
+
+| Parameter | Units | Defined in clause: |
+|----------------------------------------------------------------------------|--------|--------------------|
+| General information | | |
+| Operating central frequency | THz | 7.1.1 |
+| Operating wavelength range | nm | 7.1.2 |
+| Bit rate/line coding of optical tributary signals | Gbit/s | 7.1.3 |
+| Maximum bit error ratio | – | 7.1.4 |
+| Isolation | dB | 7.1.5 |
+| Interface at point Ss | | |
+| Maximum mean channel output power | dBm | 7.2.1 |
+| Minimum mean channel output power | dBm | 7.2.2 |
+| Minimum side mode suppression ratio | dBm | 7.2.3 |
+| Minimum channel extinction ratio | dB | 7.2.4 |
+| Eye mask | – | 7.2.5 |
+| Interface at point FPs | | |
+| Maximum mean channel output power | dBm | 7.3.1 |
+| Minimum mean channel output power | dBm | 7.3.2 |
+| Minimum side mode suppression ratio | dBm | 7.3.3 |
+| Minimum channel extinction ratio | dB | 7.3.4 |
+| Eye mask | – | 7.3.5 |
+| Transmitter beam radius | mm | 7.3.6 |
+| Divergence angle | μrad | 7.3.7 |
+| Acceptable alignment error margin for transmitter | μrad | 7.3.8 |
+| Free-space optical path from point FPs to FPR | | |
+| Link attenuation | dB | 7.4.1 |
+| FSO link bit error rate outage probability | % | 7.4.2 |
+| FSO receive power outage probability | % | 7.4.3 |
+| Maximum latency | μs | 7.4.4 |
+| Interface at point FPR | | |
+| Maximum mean channel input power | dBm | 7.5.1 |
+| Minimum mean channel input power | dBm | 7.5.2 |
+| Maximum geometry attenuation | dB | 7.5.3 |
+| Interface at point Rs | | |
+| Maximum mean input power | dBm | 7.6.1 |
+| Minimum mean input power | dBm | 7.6.2 |
+| Minimum optical signal-to-noise ratio (OSNR) | dB | 7.6.3 |
+
+## 7.1 General information
+
+### 7.1.1 Operating central frequency
+
+The operating central frequency is defined as in [ITU-T G.959.1]. This Recommendation does not specify a central frequency value for the free-space optical link.
+
+### **7.1.2 Operating wavelength range**
+
+The operating wavelength range is defined as in [ITU-T G.959.1]. This Recommendation does not specify an operating wavelength range value for the free-space optical link.
+
+### **7.1.3 Bit rate/line coding of optical tributary signals**
+
+Optical tributary signal class NRZ 10G is defined as in [ITU-T G.959.1].
+
+### **7.1.4 Maximum bit error ratio**
+
+The maximum bit-error ratio is defined as in [ITU-T G.959.1].
+
+### **7.1.5 Isolation**
+
+The ratio, in dB, of the Tx optical power (at Ss interface) leaking into the Rx at the same side (Rs interface).
+
+## **7.2 Interface at point Ss **
+
+### **7.2.1 Maximum mean channel output power**
+
+The maximum mean channel output power is defined as in [ITU-T G.959.1] or [ITU-T G.698.2].
+
+### **7.2.2 Minimum mean channel output power**
+
+The minimum mean channel output power is defined as in [ITU-T G.959.1] or [ITU-T G.698.2].
+
+### **7.2.3 Minimum side mode suppression ratio**
+
+The minimum side mode suppression ratio is defined as in [ITU-T G.959.1].
+
+### **7.2.4 Minimum channel extinction ratio**
+
+The minimum channel extinction ratio is defined as in [ITU-T G.959.1] or [ITU-T G.698.2].
+
+### **7.2.5 Eye mask**
+
+The eye mask is defined as in [ITU-T G.959.1].
+
+## **7.3 Interface at point FP s**
+
+### **7.3.1 Maximum mean channel output power**
+
+The maximum value of the average channel optical power at interface FP s. These values must comply with the eye safety regulations in [IEC 60825-1], [IEC 60825-2] and [IEC 60825-12].
+
+### **7.3.2 Minimum mean channel output power**
+
+The minimum value of the average channel optical power at interface FP s, compatible with the specified bit error ratio (BER).
+
+### **7.3.3 Minimum side mode suppression ratio**
+
+The minimum side mode suppression ratio (SMSR) is defined as in [ITU-T G.959.1]. The free-space interface SMSR value is tested and defined by coupling the free-space signal into the optical fibre.
+
+### **7.3.4 Minimum channel extinction ratio**
+
+The minimum channel extinction ratio is defined as in [ITU-T G.959.1]. The free-space interface extinction ratio value is tested and defined by coupling the free-space signal into the optical fibre.
+
+### **7.3.5 Eye mask**
+
+The eye mask is defined as in [ITU-T G.959.1]. The free-space interface eye mask template is tested and defined by coupling the free-space signal into the optical fibre.
+
+### **7.3.6 Transmitter beam radius**
+
+The transmitter beam radius is the radius where for a Gaussian beam at a certain cross section, the light intensity falls to $1/e^2$ from the centre. It can also be termed as $1/e^2$ beam radius. If the cross section is at beam waist, the radius is called the beam waist radius. Beam waist is the smallest cross section of the transmitted Gaussian beam.
+
+### **7.3.7 Divergence angle**
+
+The beam divergence angle is a measure of the speed at which the beam spreads outward from the beam waist.
+
+### **7.3.8 Acceptable alignment error margin for transmitter**
+
+It is the maximum acceptable value of the deviation angle of the light beam at the transmitter from the reference position due to pointing error such as building sway.
+
+## **7.4 Free-space optical path from point FPs to FPR**
+
+### **7.4.1 Link attenuation**
+
+The link attenuation includes several contributors such as geometric attenuation, free-space attenuation, atmospheric scattering, absorption and weather numerical models. The aforementioned contributors are described in [ITU-R P.1814-1] and [ITU-R P.1817-1].
+
+### **7.4.2 FSO link bit error rate outage probability**
+
+Outage probability, or unavailability, is defined as the percentage of unavailable time to total time in a given observation period of the FSO link (the period is usually one year). Unavailable time begins at the onset of 10 consecutive severely errored second (SES) outcomes and ends at the onset of 10 consecutive non-SES outcomes. A severely errored second (SES) is a one-second period which contains $\geq 30\%$ errored blocks or at least one defect.
+
+### **7.4.3 FSO receive power outage probability**
+
+FSO receive power outage probability is defined as the percentage of time to total time measured during the observation period (the period is usually one year), when received signal strength falls below receiver sensitivity.
+
+### **7.4.4 Maximum latency**
+
+The latency is defined as the time it takes for a signal to travel from the FPs transmitter to the FPR receiver. The maximum latency is the maximum latency value to meet the specified BER.
+
+## **7.5 Interface at point FPR**
+
+### **7.5.1 Maximum mean channel input power**
+
+The maximum acceptable value of the average received channel power at point FPR to achieve the specified maximum BER.
+
+### **7.5.2 Minimum mean channel input power**
+
+The minimum value of the mean received optical power at point FPR. This power is the minimum mean channel output power minus the maximum total attenuation.
+
+### **7.5.3 Maximum geometry attenuation**
+
+The maximum geometry attenuation is defined as in [ITU-R P.1814-1].
+
+## 7.6 Interface at point Rs
+
+### 7.6.1 Maximum mean input power
+
+The maximum mean input power is defined as in [ITU-T G.959.1] or [ITU-T G.698.2]
+
+### 7.6.2 Minimum mean input power
+
+The minimum sensitivity is defined as in [ITU-T G.959.1].
+
+### 7.6.3 Minimum optical signal-to-noise ratio (OSNR)
+
+The minimum optical signal-to-noise ratio (OSNR) is defined as in [ITU-T G.698.2].
+
+# 8 Parameter values
+
+The parameters and values of C3s-2-a are given in Table 8-1.
+
+**Table 8-1 – Physical layer parameters and values for C3s-2-a application**
+
+| Parameter | Units | C3s-2-a |
+|------------------------------------------------------|-----------------|-----------------------------------|
+| General information | | |
+| Operating central frequency | THz | NA |
+| Operating wavelength range | nm | NA |
+| Bit rate/line coding of optical tributary signals | Gbit/s | Refer to DW100C-2A2(C) in G.698.2 |
+| Maximum bit error ratio | – | Refer to DW100C-2A2(C) in G.698.2 |
+| Isolation | dB | $\geq 45$ |
+| Interface at point Ss | | |
+| Maximum mean channel output power | dBm | Refer to DW100C-2A2(C) in G.698.2 |
+| Minimum mean channel output power | dBm | Refer to DW100C-2A2(C) in G.698.2 |
+| Minimum side mode suppression ratio | dBm | Refer to DW100C-2A2(C) in G.698.2 |
+| Minimum channel extinction ratio | dB | Refer to DW100C-2A2(C) in G.698.2 |
+| Eye mask | – | Refer to DW100C-2A2(C) in G.698.2 |
+| Interface at point FPs | | |
+| Maximum mean channel output power | dBm | 23 |
+| Minimum mean channel output power | dBm | 0 |
+| Minimum side mode suppression ratio | dBm | 20 |
+| Minimum channel extinction ratio | dB | Refer to DW100C-2A2(C) in G.698.2 |
+| Eye mask | – | Refer to DW100C-2A2(C) in G.698.2 |
+| Transmitter beam radius | mm | 10-100 |
+| Divergence angle | $\mu\text{rad}$ | $\leq 500$ |
+| Acceptable alignment error margin for transmitter | $\mu\text{rad}$ | $< 100$ |
+| Free-space optical path from point FPs to FPR | | |
+| Link attenuation | dB | See Note 1 |
+| FSO link bit error rate outage probability | % | See Note 2 |
+| FSO receive power outage probability | % | See Note 2 |
+| Maximum Latency | $\mu\text{s}$ | TBD |
+
+**Table 8-1 – Physical layer parameters and values for C3s-2-a application**
+
+| Parameter | Units | C3s-2-a |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-----------------------------------|
+| Interface at point FPR | | |
+| Maximum mean channel input power | dBm | 0 |
+| Minimum mean channel input power | dBm | -26 |
+| Maximum geometry attenuation | dB | 3.5-30 |
+| Interface at point RS | | |
+| Maximum mean input power | dBm | Refer to DW100C-2A2(C) in G.698.2 |
+| Minimum mean input power | dBm | Refer to DW100C-2A2(C) in G.698.2 |
+| Minimum optical signal-to-noise ratio (OSNR) | dB | Refer to DW100C-2A2(C) in G.698.2 |
+| NOTE 1 – The total link attenuation from interfaces FP S to FP R must be compatible with the application codes. | | |
+| NOTE 2 – The values of outage probabilities are not specified in this Recommendation but are specified by the operators based on the operation environment of the FSO link. | | |
+
+# 9 Optical safety considerations
+
+See [ITU-T G.664], [IEC 60825-1], [IEC 60825-2] and [IEC 60825-12] for optical safety considerations.
+
+# Appendix I
+
+## Definitions of free-space optical link related parameters and calculation of link attenuation
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### I.1 Visibility
+
+The visibility for 550 nm laser is defined as in [ITU-R P.1817-1]. The definition is also applicable for 1 550 nm laser in free space, that is, the distance to an object where the image contrast drops to 2% of its original value. But for the same transmission distance, 1 550 nm laser has 1.4 times better transmittivity than 550 nm. Thus, the equation for 550 nm visibility $V_{\text{km}}$ in [ITU-R P.1817-1] times 1.4 is the visibility value for 1 550 nm when image contrast drops to 2%.
+
+### I.2 Scintillation
+
+Due to atmospheric turbulence, the refraction index of the atmosphere varies randomly with time and space. When a laser beam propagates through the atmosphere, the wavefront is distorted by the random fluctuation, which causes constructive and destructive interference within the laser beam cross-section. The random intensity fluctuation of the received optical signal is defined as scintillation. Scintillation can be characterized by scintillation index $\sigma_I^2$ , which is the normalized variance of the laser beam intensity, and can be defined as:
+
+$$\sigma_I^2 = \frac{\langle I^2 \rangle}{\langle I \rangle^2} - 1 \quad (\text{I.1})$$
+
+where $I$ [W/m2 ] is the intensity in the detector plane, and the angle bracket denotes an ensemble average.
+
+For weak turbulence when $\sigma_I^2 < 1$ , scintillation index equals the Rytov variance $\sigma_R^n$ . In case of plane waves, scintillation index can be expressed as:
+
+$$\sigma_I^2 = \sigma_R^2 = 1.23 C_n^2 k^{7/6} L^{11/6} \quad (\text{I.2})$$
+
+where $\sigma_R^n$ is the Rytov variance that is related to the strength of optical turbulence, $k$ is wave number, $L$ is the link distance. $C_n^2$ [m-2/3 ] is the refractive index structure parameter. $C_n^2$ determines the strength of turbulence in the atmosphere, and varies with time of day, geographical location and height.
+
+Several models have been proposed to describe the scintillation intensity statistical model. For weak turbulence $\sigma_I^2 < 1$ , the intensity statistics can be given by log-normal distribution [b-Vetelino]. For strong turbulence $\sigma_I^2 \geq 1$ , the intensity statistics is negative exponential [b-Tannaz]. For $3 < \sigma_I^2 < 4$ , the intensity statistics is given by $K$ distribution [b-Tannaz]. There are other models as $I-K$ [b-Shah] and Gamma-Gamma models [b-Vetelino] can be applicable to all conditions of atmospheric turbulence.
+
+Scintillation can cause fluctuation in the received signal intensity, which is equivalent to introducing a random noise into the transmitted signal, resulting in the degradation of the free-space link BER. When knowing the received intensity statistical model and probability distribution, the average BER under the influence of atmospheric fading can be calculated. This BER degradation can be regarded as a scintillation loss, which is the required receive power ratio between disturbed and undisturbed case, to achieve the same BER.
+
+
+
+Figure I.1: Dependency of scintillation loss on propagation distance for various values of turbulence strength C\_n^2. The graph plots Scintillation loss in dB (y-axis, 0 to 10) against Propagation distance in m (x-axis, 0 to 5000). Four curves are shown for different C\_n^2 values: 5e-14 m^-2/3, 2e-14 m^-2/3, 1e-14 m^-2/3, and 5e-15 m^-2/3. The curves show that scintillation loss increases with propagation distance and is higher for larger C\_n^2 values. The curve for C\_n^2 = 5e-14 m^-2/3 rises most steeply, reaching about 7 dB at 1500 m. The curve for C\_n^2 = 5e-15 m^-2/3 rises most gradually, reaching about 5 dB at 5000 m. A label G.641(25) is present in the bottom right corner of the plot area.
+
+**Figure I.1 – Dependency of scintillation loss on propagation distance for various values $C_n^2$ of turbulence strength**
+
+For example, for a weak turbulence situation, assuming the log-normal power distribution, Figure I.1 shows the numerical results of scintillation loss with different $C_n^2$ for short propagation distance [b-David]. Within this range, the scintillation loss in dB is roughly proportional to the third power of the propagation distance.
+
+### I.3 Definition of angle of arrival (AOA) loss and AOA statistical model
+
+The angle of arrival (AOA) refers to the angle at which an optical beam reaches the receiver relative to its optical axis. Variations in the AOA at the photodetector reduce the amount of collected optical power, leading to amplitude fluctuations. This effect is particularly pronounced in receivers with a limited field of view (FOV). In practical high-speed FSO communication systems, small photodetectors or light coupled into ITU-T G.652 fibres are commonly used to achieve higher data transmission rates, which further restricts the receiver FOV. The Rayleigh distribution has been widely employed to model the random attenuation caused by AOA fluctuations in FSO systems with a limited FOV [b-Zedini].
+
+The probability density function (PDF) of the deviation angle $\theta_d$ in AOA fluctuations is modeled using the Rayleigh distribution [b-Zedini]:
+
+$$f(\theta_d) = \frac{\theta_d}{\sigma_0^2} \exp\left(-\frac{\theta_d^2}{2\sigma_0^2}\right), \quad \theta_d \geq 0$$
+
+where $\sigma_0^2$ represents the variance of the deviation angle $\theta_d$ . The typical values of AOA and $\sigma_0^2$ vary from mrad to $\mu\text{rad}$ [b-Zedini].
+
+### I.4 Definition of solar radiation
+
+Solar background radiation can significantly impact FSO communication systems. Solar radiation reaches the FSO receiver through four primary paths: direct sunlight, reflected sunlight (specular reflection), sunlight scattered by hydrometeors, and reflections from surrounding objects such as white walls of buildings [b-Sidorovich]. The solar irradiance is highest in the visible region (400-700 nm), peaking around 500-600 nm at approximately 1.5 to 2 W/m2 /nm. At 980 nm, the irradiance decreases to about 0.5 W/m2 /nm, while at 1310 nm, it further drops to around 0.2-0.3 W/m2 /nm. At 1 550 nm, commonly used in FSO systems, the solar irradiance is approximately 0.2 W/m2 /nm, making it favourable due to lower solar background noise[b-Bozzetti]. The intensity of solar radiation depends on several factors, including spectral wavelength density, the bandwidth of the optical filter, system transmittance, lens diameter, effective focal area, optical system FOV, the mean solid angle of the sun, reflectivity of scattering surfaces, and atmospheric transmittance. To accurately estimate the effect of solar radiation noise under different scenarios, specific mathematical models are employed like the one in the following.
+
+The noise power contributed by direct sunlight at the receiver can be mathematically expressed as [b-Sidorovich]:
+
+$$\sigma_{SD}^2 = F_\lambda S_R \eta_R B_0$$
+
+where $F_\lambda$ is the spectral density (W·m-2 ·nm-1 ), $S_R$ is the effective area of the receiver's converging lens, $\eta_R$ is the system transmittance, and $B_0$ is the optical bandpass filter bandwidth.
+
+In addition to direct sunlight, highly collimated sunlight reflected by optically flat surfaces such as windows or polished objects can also reach the receiver. This reflected noise contribution is modelled as [b-Sidorovich]:
+
+$$\sigma_{SR}^2 = 0.1 F_\lambda S_R \eta_R \eta_a \left( \frac{R^2 B_0}{\Omega_S} \right)$$
+
+where $\eta_a$ is the transmittance of the reflecting object, R is the distance between the reflector and the receiver, and $\Omega_S$ is the mean solid angle of the sun.
+
+When sunlight is scattered by aerosols such as clouds or fog, the background light incident on the receiver is given by [b-Sidorovich]:
+
+$$\sigma_{SH}^2 = B S_R \eta_R \Omega_R B_0$$
+
+where $\Omega_R$ is the receiver's FOV solid angle and B is the brightness of the scattered sunlight.
+
+Solar radiation is particularly critical when optical preamplifiers are used at the receiver front-end. Additionally, careful alignment of the FSO system is essential to prevent pointing the receiver toward the sun, which could not only degrade system performance but also risk damaging the equipment. Among the various modes of solar radiation ingress, direct sunlight presents the most severe impact on system performance [b-Sidorovich].
+
+### I.5 Calculation of link attenuation
+
+Link attenuation contains different categories according to [ITU-R P.1814-1] and [ITU-R P.1817-1], for reference. The main contributors are rain, fog and snow. The attenuation coefficient corresponding to visibility is listed below. These sets of parameters are only provided for better link planning.
+
+#### Fog attenuation:
+
+< 0.03 dB (Visibility > 50 km)
+
+0.34 dB-0.04 dB (6 km < Visibility < 50 km)
+
+> 0.42 dB (Visibility < 6 km)
+
+#### **Rain attenuation**
+
+Japan model: 3.16 dB-20.86 dB (Rainfall of 1-20 mm/h)
+
+France model: 2.15-16 dB (Rainfall of 1-20 mm/h)
+
+#### **Snow attenuation**
+
+7.90 dB (Wet snow of 1 m/h)
+
+11.16 dB (Dry snow of 1 m/h)
+
+# Appendix II
+
+## A media model for bidirectional application
+
+(This appendix does not form an integral part of this Recommendation.)
+
+To have a better understanding of how the optical signal is transmitted through the FSO system to the destination, a media model reflecting the functional architecture is illustrated in Figure II.1.
+
+An optical signal at the $S_S$ reference point propagates through the FSO black box, crosses the $FP_S$ reference point, propagates through the free-space media and crosses the $FP_R$ reference point, propagates through the FSO black box and emerges at the $R_S$ reference point. Thus, for bidirectional application, there should be five media links. That is: Four fibre links are from $S_S$ to the media port at $FP_S$ , the media port at $FP_R$ to $R_S$ and vice versa. A free-space media link is between $FP_S$ and $FP_R$ . The media model is illustrated in Figure II.1.
+
+
+
+The diagram shows a symmetrical bidirectional system. On the left and right sides are 'Media elements' containing a Receiver (R) and a Transmitter (T).
+
+On the left:
+ - Transmitter (T) sends a signal down through reference point $S_S$ into a 'Fibre media channel'.
+ - Receiver (R) receives a signal up through reference point $R_S$ from a 'Fibre media channel'.
+ - These fibre channels connect to 'Free space media channels' at reference points $FP_S$ (for transmission) and $FP_R$ (for reception).
+
+On the right:
+ - The setup is mirrored. The transmitter (T) sends through $S_S$ to $FP_S$ , and the receiver (R) receives from $FP_R$ to $R_S$ .
+
+The 'Free space media channels' consist of two parallel paths between the two media elements. A dashed line across the top connects the R/T blocks, labeled 'Network media channel'.
+
+G.641(25)
+
+Diagram of a bidirectional application with five media links.
+
+**Figure II.1 – Bidirectional application with five media links**
+
+# Bibliography
+
+- [b-Bozzetti] M. Bozzetti, G. de Candia, M. Gallo, O. Losito, L. Mescia and F. Prudenzano (2010), *Analysis and design of a solar rectenna*, IEEE International Symposium on Industrial Electronics, Bari, Italy, 2010, pp. 2001-2004.
+- [b-David] David F. (2004), *Scintillation loss in free-space optic IM/DD systems[C]//Free-space laser communication technologies XVI*. SPIE, 5338: 65-75.
+- [b-Shah] Shah, D., Nayak, B., Jethawani, D. (2014), *Study of different atmospheric channel models*. Int. J. Elect. Com. Eng. Tech. (IJECET), 5(1):105-112.
+- [b-Sidorovich] Sidorovich, Vladimir G. (2002), *Solar background effects in wireless optical communications*, in Optical Wireless Communications V, vol. 4873, pp. 133-142. SPIE.
+- [b-Tannaz] S. Tannaz, C. Ghobadi, J. Nourinia and E. Mostafapour (2018), *The Effects of Negative Exponential and K-distribution Modeled FSO Links on the Performance of Diffusion Adaptive Networks*, 9th International Symposium on Telecommunications (IST), Tehran, Iran, 2018, pp. 19-22.
+- [b-Vetelino] Vetelino F S, Young C, Andrews L. (2007), *Fade statistics and aperture averaging for Gaussian beam waves in moderate-to-strong turbulence[J]*. Applied optics, 46(18): 3780-3789.
+- [b-Zedini] E. Zedini, Y. Ata, A. Kammoun and M. -S. Alouini (2025), *A novel approach to approximating generalized pointing errors modeled by beckmann distribution in FSO communication systems*, in IEEE Open Journal of the Communications Society, vol. 6, pp. 727-741, doi: 10.1109/OJCOMS.2024.3523304.
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/031e354d9de9563c9f650e3e4fcba16d_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/031e354d9de9563c9f650e3e4fcba16d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..72fb7449aae522e7e32bd23867c4b23437903721
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/031e354d9de9563c9f650e3e4fcba16d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cb6bc973167165c954486667c71134af8ea0df6d3ff3c78f6a2b6291e5c30d5f
+size 24189
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..639747fc14470fdb399ae13cc896cc9022f977e0
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:845cb2d194066252ce119c4b407d3c04176815b4539cf566f59b968c22898abf
+size 4171
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/25fab88fda841d5eec316c440656187e_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/25fab88fda841d5eec316c440656187e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..054532c92c3967f4787c7b5eecda4c69e2c9c7d1
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/25fab88fda841d5eec316c440656187e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be063016385856030445f1ef837c4a34ae7f54d5f1394574ebd02df17d0d3107
+size 58244
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/3b6177b1edfdc8c7740f03f346d7838f_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/3b6177b1edfdc8c7740f03f346d7838f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e36b7360bff75675fd09882907a5d9c200af412d
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/3b6177b1edfdc8c7740f03f346d7838f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:95bbb54440aa015e63a313ebff619b099aacebbe6fd86d341830bbe174feb270
+size 32958
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/3c47f29e8e1963959009844c7f3ee025_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/3c47f29e8e1963959009844c7f3ee025_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b7030101e1f1cd12ffeacbf8e93a1a60457fc5ae
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/3c47f29e8e1963959009844c7f3ee025_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:92fe65c4309599d5fac317133238d8a0a1e2a7a81c3272f078cbe616eed58ae7
+size 40458
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/48a4d999034fb203698ddc187c259679_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/48a4d999034fb203698ddc187c259679_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..03b7943473bcb6dfbd381e3dde5e4ae6e91f2c88
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/48a4d999034fb203698ddc187c259679_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:911792541c2c4a80d52bc8060fa43b18ddaa7282a64aaf097a65f25dba9547e3
+size 41956
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ee5d8e94e6597df619a06df180fbb32134b930ad
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b5943f385f8fae0fcd8f5e2fe4811d9f9a7dca302c31748f79ea187523bef85
+size 100823
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d082b134a519c5b7bcc06dd15c6380c1c2d98687
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:22e6be78dc7b7a653b55b491d3edf1c9bf11574c87e0c7269e197e8aed8dccd4
+size 58940
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/65678100712a6817696109be76a51f0f_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/65678100712a6817696109be76a51f0f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9c223ab69c309fc0a7ed26b124d44b21c2bf6d17
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/65678100712a6817696109be76a51f0f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1cfb6b175c97714bd61c49389d74e75f61c3dde6008eae5f3563dba82d2fb093
+size 29972
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/76959415a1298a6f58ea1fff16fb01b6_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/76959415a1298a6f58ea1fff16fb01b6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ef2c629321532fc024f6fa9f7e406b9482248a14
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/76959415a1298a6f58ea1fff16fb01b6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e387240dc0ffd239dd8af2e3782b5d022e9e2726808017c15641dafc9f4f488f
+size 69146
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/7d2d1d3870cd224c4430d19334557716_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/7d2d1d3870cd224c4430d19334557716_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..913489667f123c04033f6d0b74108f854d09ccc1
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/7d2d1d3870cd224c4430d19334557716_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:666c1f71cf3814846b00c2d0a993efdeea51cfa5a0fa7ec8198db5fcc645da4f
+size 90502
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d78d23b15ded2cd767ff2cb7194e6e5ee358b78c
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f9b6fa6bb89daf7d2e949cd160417552af767a6ae9c98b8519842f90741cc132
+size 135902
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/810e9c03f216ccb41879979badc63a3f_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/810e9c03f216ccb41879979badc63a3f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aca8b5482ff9cbef364dfbbc54aa90597e826e37
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/810e9c03f216ccb41879979badc63a3f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d5f0cf19b3c0308e3c28357a4a5f7cd92f2edcf11f533f79c518bb5c275fbc1c
+size 41371
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/91b12db3c85bbf466ad27eb3665a1b06_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/91b12db3c85bbf466ad27eb3665a1b06_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4b6760dfbb6d461b76417802f6dabfb0a940f970
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/91b12db3c85bbf466ad27eb3665a1b06_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3b6f440083fa4ed9a6d706c65798a28b829bd731368e9f4a6a811821f64646f8
+size 35691
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/9857175bc98d86591d24a161fe615f12_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/9857175bc98d86591d24a161fe615f12_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..03d24b312412d9283b5d7a6eb3e5a4951489f018
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/9857175bc98d86591d24a161fe615f12_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e488f7a110b343d2f14d86094adc208c69bc7fc6e9b9d25ad6c42a7928acc7d5
+size 66563
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/a74fdbc8b78564b89bc1b262cfd995b6_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/a74fdbc8b78564b89bc1b262cfd995b6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a98f7a667b12b74f6e22fa4c5ec0d0fae05d0b25
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/a74fdbc8b78564b89bc1b262cfd995b6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6090365fca27d78d8526253afd6c15d6d9c674262e66308ada043dd554da983d
+size 21526
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/a7c51c18111139f9aca2805114108565_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/a7c51c18111139f9aca2805114108565_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..12d4a07e0d049da99a5aba5e86085a61ff42d792
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/a7c51c18111139f9aca2805114108565_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1b0504911ac4a76fbb801ee303bf4d6a1069b22c814f291324d64161315f0236
+size 29529
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/a844248c1fa0a79f187fc9aa111182f7_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/a844248c1fa0a79f187fc9aa111182f7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..41344e5d792b4d3176a92e5168fb54474caaec4f
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/a844248c1fa0a79f187fc9aa111182f7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be208379792ecf128afeea80a58a5f08937a227414669242e2d850561f0e64e9
+size 34803
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/a8523d225a4e279ab9e02f3c28cfa36a_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/a8523d225a4e279ab9e02f3c28cfa36a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c787d83d85bfcd6d5c4e29c1b2b1d44b22b40aae
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/a8523d225a4e279ab9e02f3c28cfa36a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:77becf8ffbde3c1df58e944475930a141f7589d33820024aca58dc883074b93b
+size 27224
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/b2d16e07bfa79d67a8adabf7e26c7764_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/b2d16e07bfa79d67a8adabf7e26c7764_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d6beee4c758b83e0ff96b2612dc1bcb9b58e3cac
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/b2d16e07bfa79d67a8adabf7e26c7764_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:34822700de14531d322bbf546199546f38b37c1bad3eb71ed9ba4ac701355c9e
+size 35856
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/b8d13287be9197ff7a1d474afd187b6e_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/b8d13287be9197ff7a1d474afd187b6e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9548cce6695487e3d7d225a9fbe8f734f0104afd
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/b8d13287be9197ff7a1d474afd187b6e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f99c5bbe81c579d74d8942e64ec821c0683e0cf6fc593a68084567b0de16f3e3
+size 25922
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/bc6b860289610cf05b09018ab47c90aa_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/bc6b860289610cf05b09018ab47c90aa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ce41e8de58ff601fbf2bb473994e5dc584fcf3cc
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/bc6b860289610cf05b09018ab47c90aa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8476df1e60db3451e432debf01e8979f95f9309fdca965c212f4b38cb7629095
+size 16206
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/bfb6d182d624680db577069bbc0b2a93_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/bfb6d182d624680db577069bbc0b2a93_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f7873abed6ce714a974a192f63693e3649767055
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/bfb6d182d624680db577069bbc0b2a93_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:560201b94139ecb0739a4156f4a660909d1ee2791be21b6a285af683bfa559c4
+size 50100
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/c17eaf807acd5faec68da19dd16929be_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/c17eaf807acd5faec68da19dd16929be_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e6a8cdbe87a15a2f2b204cbd13a4439b5fef179b
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/c17eaf807acd5faec68da19dd16929be_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d29abf8247163977403122809389ece5e94221e6011be353e1d16c0799b35bd7
+size 46360
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/c53adc66eab40abd5f8b9107d950ad04_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/c53adc66eab40abd5f8b9107d950ad04_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cace143a117c0564521c2a12302fc6dddb96a27e
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/c53adc66eab40abd5f8b9107d950ad04_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f1926b1e3f901e511d1d981e1e07bb934cd2ecf921e4c8499a6bec75a4b3b82a
+size 72912
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..69c33c2cff1f7a14ca2b57f2330da8b910db0f6f
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f744d1afa09f26f20eeec18fc86535ff340247434d865e356c3b016857344413
+size 45161
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/cb74fd9f5ec715dd3e2e325b864b48bc_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/cb74fd9f5ec715dd3e2e325b864b48bc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9c5156d50e1ad3eeb1eca945084892ab5b2ce4b2
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/cb74fd9f5ec715dd3e2e325b864b48bc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e23f81015bc981ff91b5e109e89d1734756bf03546413828c4e38392bc1a0125
+size 70045
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/cfc852835f2d91bea8dc074568937e22_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/cfc852835f2d91bea8dc074568937e22_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..322ceaa69878b156341ca1c1ca8e3382536f0987
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/cfc852835f2d91bea8dc074568937e22_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:64e0f4d71c66a524d2f40c652c7a59d8856d9258d94ee147f250cc3d1b554bb5
+size 46550
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/d3c5090abad168738b2dd27087f89fdc_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/d3c5090abad168738b2dd27087f89fdc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..468f17993faf5d9f48abd733625e7566ef0bef21
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/d3c5090abad168738b2dd27087f89fdc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9740378b37e4d174ef51474f598fe760f2943620997e161fa27d30bb887d8f0b
+size 33195
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/d68ecc44f3cfaed866a846f9fa4bdf38_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/d68ecc44f3cfaed866a846f9fa4bdf38_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da1d04104756c390665b7d45035fe468bea3c4ee
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/d68ecc44f3cfaed866a846f9fa4bdf38_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f9b999237d67f656c29a7e86644cde40feff141ee402c66f05126f177d1ae26a
+size 35414
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..29b9ab79b93853d111bdfa0e1c3e878cee8ec7e3
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:502b6118989d57caf5b2c4e5470f2dbeb521f240bc05dcc947286e142a0c2728
+size 46092
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/d74e83c626faf36154df84683d6c6673_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/d74e83c626faf36154df84683d6c6673_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..231a495dce7ea24c690aff870811c24682b4f1bb
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/d74e83c626faf36154df84683d6c6673_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0137ebf25c9e5a6621b06861b940867fa92bcdff567bd839f7ec583c45fd876b
+size 37061
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..53567af804bf447ab762511d987924961d77c5e1
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b2ad79ca90dd94bc3d44248310367ff074caba796f24565bb1637080ea9de80
+size 77446
diff --git a/marked/G/T-REC-G.650.2-201508-I_PDF-E/fe6af03ab7804980cff28a06241be192_img.jpg b/marked/G/T-REC-G.650.2-201508-I_PDF-E/fe6af03ab7804980cff28a06241be192_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..50596678e3bde03e38ff437e2a19da4af3776a3b
--- /dev/null
+++ b/marked/G/T-REC-G.650.2-201508-I_PDF-E/fe6af03ab7804980cff28a06241be192_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b53379b91dc9819eb108fb5a93e825113e81da8b2eb05fc14ece0c875297a719
+size 29758
diff --git a/marked/G/T-REC-G.651.1-201811-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/G/T-REC-G.651.1-201811-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c7ff549cb6215423533cb6d04c93b27280e09e92
--- /dev/null
+++ b/marked/G/T-REC-G.651.1-201811-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc443d2b97af4d8c6b8adec2e09b6fb65208c842320962efbc79a56c2a64e5af
+size 4104
diff --git a/marked/G/T-REC-G.655-200911-I_PDF-E/3102c32204f998dba666e1e915d5babf_img.jpg b/marked/G/T-REC-G.655-200911-I_PDF-E/3102c32204f998dba666e1e915d5babf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..04659ddedc8386e803a13caef610ec2759ab305e
--- /dev/null
+++ b/marked/G/T-REC-G.655-200911-I_PDF-E/3102c32204f998dba666e1e915d5babf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:814be0506b60322d54950b63471caf5796a4202696099b848d2efabcbc977ee8
+size 55593
diff --git a/marked/G/T-REC-G.655-200911-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/G/T-REC-G.655-200911-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fab773e02c0ac55a5877a1257992caf40611caf9
--- /dev/null
+++ b/marked/G/T-REC-G.655-200911-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:15e03c4ddd198980f5976a458ec6a2debbabbee2212b8e1ad670ae79ae5bfaf2
+size 7515
diff --git a/marked/G/T-REC-G.655-200911-I_PDF-E/96a7eac66ef72bb016c280278506ac63_img.jpg b/marked/G/T-REC-G.655-200911-I_PDF-E/96a7eac66ef72bb016c280278506ac63_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..044b1f8e8c0512c92f2814284c958d034f2d3880
--- /dev/null
+++ b/marked/G/T-REC-G.655-200911-I_PDF-E/96a7eac66ef72bb016c280278506ac63_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:83c026f9fde8ccd4adb07b3d18a1a2782d3bd1a6842c6841e627d783a6a1b8a9
+size 46927
diff --git a/marked/G/T-REC-G.655-200911-I_PDF-E/ebce355620876e10f907f8b71926c112_img.jpg b/marked/G/T-REC-G.655-200911-I_PDF-E/ebce355620876e10f907f8b71926c112_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4bca0c7d9b9043470c990c775bef60df9b2c8b00
--- /dev/null
+++ b/marked/G/T-REC-G.655-200911-I_PDF-E/ebce355620876e10f907f8b71926c112_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6193e2dd339a821dafa8d2863ebc5ced0a7c5d18e2e5d19a1439b8216cbbe29b
+size 49205
diff --git a/marked/G/T-REC-G.655-200911-I_PDF-E/f8630b0582d6e5b1d81f877880ef0dda_img.jpg b/marked/G/T-REC-G.655-200911-I_PDF-E/f8630b0582d6e5b1d81f877880ef0dda_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..be43eb9a789475e8804c3b239028e681f6efdd1f
--- /dev/null
+++ b/marked/G/T-REC-G.655-200911-I_PDF-E/f8630b0582d6e5b1d81f877880ef0dda_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7b08b41b1e6f80ef1dfbabeaec09e6c5a0fd7c56d77faab3a12fc4996ec33f6a
+size 52175
diff --git a/marked/G/T-REC-G.655-200911-I_PDF-E/raw.md b/marked/G/T-REC-G.655-200911-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..687d6c5381e986484c72d6dba8032fe720c3e853
--- /dev/null
+++ b/marked/G/T-REC-G.655-200911-I_PDF-E/raw.md
@@ -0,0 +1,705 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**G.655**
+
+(11/2009)
+
+SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
+DIGITAL SYSTEMS AND NETWORKS
+
+Transmission media and optical systems characteristics –
+Optical fibre cables
+
+# --- **Characteristics of a non-zero dispersion-shifted single-mode optical fibre and cable**
+
+Recommendation ITU-T G.655
+
+
+
+The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it, symbolizing global communication. To the right of the globe, the text "International Telecommunication Union" is written in a blue, sans-serif font.
+
+ITU logo
+
+## ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS**
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 |
+| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 |
+| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 |
+| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 |
+| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 |
+| TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS | G.600–G.699 |
+| General | G.600–G.609 |
+| Symmetric cable pairs | G.610–G.619 |
+| Land coaxial cable pairs | G.620–G.629 |
+| Submarine cables | G.630–G.639 |
+| Free space optical systems | G.640–G.649 |
+| Optical fibre cables | G.650–G.659 |
+| Characteristics of optical components and subsystems | G.660–G.679 |
+| Characteristics of optical systems | G.680–G.699 |
+| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 |
+| DIGITAL NETWORKS | G.800–G.899 |
+| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 |
+| MULTIMEDIA QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER-RELATED ASPECTS | G.1000–G.1999 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.6000–G.6999 |
+| DATA OVER TRANSPORT – GENERIC ASPECTS | G.7000–G.7999 |
+| PACKET OVER TRANSPORT ASPECTS | G.8000–G.8999 |
+| ACCESS NETWORKS | G.9000–G.9999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## **Recommendation ITU-T G.655**
+
+# **Characteristics of a non-zero dispersion-shifted single-mode optical fibre and cable**
+
+# **Summary**
+
+This Recommendation describes the geometrical, mechanical, and transmission attributes of a single-mode optical fibre which has the absolute value of the chromatic dispersion coefficient greater than some non-zero value throughout the wavelength range from 1530 nm to 1565 nm. This dispersion reduces the growth of non-linear effects which are particularly deleterious in dense wavelength division multiplexing systems. The last revision in 2006 adds two new categories of this fibre in Tables D and E. Both of these categories limit the chromatic dispersion coefficient by a pair of bounding curves versus wavelength for the range of 1460 nm to 1625 nm. Although the dispersion can change sign at wavelengths less than 1530 nm, the inclusion of these lower wavelengths is intended to provide information to support coarse wavelength division multiplexing applications which do not have significant non-linear impairments, at channels from 1471 nm and higher. These tables are introduced to distinguish the two main families of ITU-T G.655 fibres that are supported by multiple vendors. Table 1, "G.655.A attributes", Table 2, "G.655.B attributes", and Table 3, "G.655.C attributes", of the 2003 edition have not been changed, of which, only the G.655.C attributes table is included in this current edition. This is the latest revision of a Recommendation that was first created in 1996. This revision adds a new note in the G.655.C, G.655.D and G.655.E attributes tables, allowing higher maximum cabled attenuation for short cables. Jumper cable cut-off wavelength is deleted as well. This revision is expected to improve harmonization with IEC standards.
+
+###### **Source**
+
+Recommendation ITU-T G.655 was approved on 13 November 2009 by ITU-T Study Group 15 (2009-2012) under Recommendation ITU-T A.8 procedures.
+
+# FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2010
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+# CONTENTS
+
+| | Page |
+|----------------------------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References..... | 2 |
+| 3 Terms and definitions ..... | 2 |
+| 4 Abbreviations..... | 2 |
+| 5 Fibre attributes ..... | 2 |
+| 5.1 Mode field diameter ..... | 3 |
+| 5.2 Cladding diameter ..... | 3 |
+| 5.3 Core concentricity error..... | 3 |
+| 5.4 Non-circularity ..... | 3 |
+| 5.5 Cut-off wavelength..... | 3 |
+| 5.6 Macrobending loss..... | 3 |
+| 5.7 Material properties of the fibre..... | 4 |
+| 5.8 Refractive index profile..... | 4 |
+| 5.9 Longitudinal uniformity of chromatic dispersion..... | 4 |
+| 5.10 Chromatic dispersion coefficient..... | 4 |
+| 6 Cable attributes ..... | 5 |
+| 6.1 Attenuation coefficient ..... | 5 |
+| 6.2 Polarization mode dispersion (PMD) coefficient..... | 6 |
+| 7 Tables of recommended values ..... | 6 |
+| Appendix I – Information for link attributes and system design ..... | 11 |
+| I.1 Attenuation ..... | 11 |
+| I.2 Chromatic dispersion..... | 11 |
+| I.3 Differential group delay (DGD) ..... | 12 |
+| I.4 Non-linear coefficient..... | 12 |
+| I.5 Tables of common typical values ..... | 12 |
+| I.6 Examples of implementation..... | 13 |
+| I.7 Chromatic dispersion coefficient limits for Tables 2 and 3 ..... | 13 |
+| Bibliography..... | 17 |
+
+# Introduction
+
+The following paragraphs provide a summary of the evolution of Recommendation ITU-T G.655, from its first 1996 version to the latest 2009 edition.
+
+- 1996 Edition 1.0.
+- 2000 Edition 2.0. This revision includes the addition of tables for different levels of system support.
+- 2003 Edition 3.0. In accordance with the agreement on spectral bands, the description of the L band upper limit is changed from 16xx to 1625 nm. Terms of base subcategory and subcategory are revised to base category and category, respectively. PMD requirements are added for all categories and two categories have reduced limits (compared to 0.5 ps/√km). For the macrobending test, mandrel diameter is reduced to 30 mm radius. As seen above, this Recommendation has evolved considerably over the years; therefore, the reader is warned to consider the appropriate version to determine the characteristics of an already deployed product, taking into account the year of production. In fact, products are expected to comply with the Recommendation that was in force at the time of their manufacture, but may not fully comply with subsequent versions of the Recommendation.
+- 2006 Edition 4.0. This revision adds two new categories of this fibre in Tables D and E. Both of these categories limit the chromatic dispersion coefficient by a pair of bounding curves versus wavelength for the range of 1460 nm to 1625 nm. Although the dispersion can change sign at wavelengths less than 1530 nm, the inclusion of these lower wavelengths is intended to provide information to support coarse wavelength division multiplexing applications which do not have significant non-linear impairments, at channels from 1471 nm and higher. These tables are introduced to distinguish the two main families of G.655 fibres that are supported by multiple vendors. Tables A, B, and C have not been changed. Tables A and B are not included in this version of this Recommendation, but are in the 2003 edition.
+- 2009 Edition 5.0. IEC 60794-2-11 (2005) is added as one of the Informative references. The tables have been renumbered. Tables 1, 2, and 3 of edition 5.0 correspond, respectively, to Tables 3, 4, and 5 of edition 4.0. Uncabled fibre PMD coefficient requirements have been added in Tables 2 and 3. A new note has been introduced in Tables 1 to 3, to allow higher maximum cabled attenuation for short cables.
+
+## Recommendation ITU-T G.655
+
+# Characteristics of a non-zero dispersion-shifted single-mode optical fibre and cable
+
+# 1 Scope
+
+This Recommendation describes a single-mode fibre with a chromatic dispersion coefficient (absolute value) that is greater than some non-zero value throughout the wavelengths larger than 1530 nm. This dispersion reduces the growth of non-linear effects that can be particularly deleterious in dense wavelength division multiplexing (DWDM) systems. At lower wavelengths, the dispersion coefficient can cross zero, but chromatic dispersion coefficient values at these wavelengths may be specified to support coarse wavelength division multiplexing (CWDM) systems that do not have significant impairments due to non-linear effects.
+
+These fibres were originally intended for use at wavelengths in a prescribed region between 1530 nm and 1565 nm. Provisions have been made to support transmission at higher wavelengths of up to 1625 nm and lower wavelengths down to 1460 nm.
+
+In clause 7, Tables 2 and 3 distinguish the two main families of ITU-T G.655 fibre implementations that are supported by multiple vendors. The G.655.A, G.655.B and G.655.C attributes tables can be used to define other implementations. The G.655.A and G.655.B attributes tables of the 2003 edition are not included in the current version of this Recommendation.
+
+The geometrical, optical, transmission and mechanical parameters are described below in three categories of attributes:
+
+- fibre attributes are those attributes that are retained throughout cabling and installation;
+- cable attributes that are recommended for cables as they are delivered;
+- link attributes that are characteristics of concatenated cables, describing estimation methods of system interface parameters based on measurements, modelling, or other considerations. Information for link attributes and system design are in Appendix I.
+
+This Recommendation, and the different performance categories found in the tables of clause 7, is intended to support the following related system Recommendations:
+
+- ITU-T G.691;
+- ITU-T G.692;
+- ITU-T G.693;
+- ITU-T G.695;
+- ITU-T G.696.1;
+- ITU-T G.698.1;
+- ITU-T G.957;
+- ITU-T G.959.1.
+
+This Recommendation contains a combination of fibre designs able to cover a broad spectrum of applications. Some re-arrangement might be considered in the future. However, the system compatibility of fibres with different characteristics is not proved and, in general, their simultaneous use in one system might be questioned and should be agreed in advance between the user and manufacturers.
+
+The meaning of the terms used in this Recommendation and the guidelines to be followed in the measurement to verify the various characteristics are given in [ITU-T G.650.1] and [ITU-T G.650.2]. The characteristics of this fibre, including the definitions of the relevant
+
+parameters, their test methods and relevant values, will be refined as studies and experience progress.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+[ITU-T G.650.1] Recommendation ITU-T G.650.1 (2004), *Definitions and test methods for linear, deterministic attributes of single-mode fibre and cable.*
+
+[ITU-T G.650.2] Recommendation ITU-T G.650.2 (2007), *Definitions and test methods for statistical and non-linear related attributes of single-mode fibre and cable.*
+
+# 3 Terms and definitions
+
+For the purposes of this Recommendation, the definitions given in [ITU-T G.650.1] and [ITU-T G.650.2] apply. Values shall be rounded to the number of digits given in the tables of recommended values before conformance is evaluated.
+
+# 4 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|------------------|-----------------------------------------|
+| $A_{\text{eff}}$ | Effective area |
+| CWDM | Coarse Wavelength Division Multiplexing |
+| DGD | Differential Group Delay |
+| DWDM | Dense Wavelength Division Multiplexing |
+| GPa | GigaPascal |
+| PMD | Polarization Mode Dispersion |
+| PMD Q | Statistical Parameter for PMD link |
+| SDH | Synchronous Digital Hierarchy |
+| TBD | To Be Determined |
+| WDM | Wavelength Division Multiplexing |
+
+# 5 Fibre attributes
+
+Only those characteristics of the fibre providing a minimum essential design framework for fibre manufacturers are recommended in this clause. Ranges or limits on values are presented in the tables of clause 7. Of these, cable manufacture or installation may significantly affect the cabled fibre cut-off wavelength and PMD. Otherwise, the recommended characteristics will apply equally to individual fibres, fibres incorporated into a cable wound on a drum, and fibres in an installed cable.
+
+## 5.1 Mode field diameter
+
+Both a nominal value and tolerance about that nominal value shall be specified at 1550 nm. The nominal that is specified shall be within the range found in clause 7. The specified tolerance shall not exceed the value in clause 7. The deviation from nominal shall not exceed the specified tolerance.
+
+## 5.2 Cladding diameter
+
+The recommended nominal value of the cladding diameter is 125 µm. A tolerance is also specified and shall not exceed the value in clause 7. The cladding deviation from nominal shall not exceed the specified tolerance.
+
+## 5.3 Core concentricity error
+
+The core concentricity error shall not exceed the value specified in clause 7.
+
+## 5.4 Non-circularity
+
+### 5.4.1 Mode field non-circularity
+
+In practice, the mode field non-circularity of fibres having nominally circular mode fields is found to be sufficiently low that propagation and jointing are not affected. It is, therefore, not considered necessary to recommend a particular value for the mode field non-circularity. It is not normally necessary to measure the mode field non-circularity for acceptance purposes.
+
+### 5.4.2 Cladding non-circularity
+
+The cladding non-circularity shall not exceed the value found in clause 7.
+
+## 5.5 Cut-off wavelength
+
+Two useful types of cut-off wavelength can be distinguished:
+
+- a) Cable cut-off wavelength, $\lambda_{cc}$ .
+- b) Fibre cut-off wavelength, $\lambda_c$ .
+
+NOTE – For some specific submarine cable applications, other cable cut-off wavelength values may be required.
+
+The correlation of the measured values of $\lambda_c$ and $\lambda_{cc}$ depends on the specific fibre and cable design and the test conditions. While in general, $\lambda_{cc} < \lambda_c$ , a general quantitative relationship cannot be easily established. The importance of ensuring single-mode transmission in the minimum cable length between joints, at the minimum operating wavelength, is paramount. This may be performed by recommending the maximum cable cut-off wavelength $\lambda_{cc}$ of a cabled single-mode fibre to be 1480 nm, or for worst-case length and bends, by recommending a maximum fibre cut-off wavelength to be 1470 nm.
+
+The cable cut-off wavelength, $\lambda_{cc}$ , shall be less than the maximum specified in clause 7.
+
+## 5.6 Macrobending loss
+
+Macrobending loss varies with wavelength, bend radius and number of turns about a mandrel with a specified radius. Macrobending loss shall not exceed the maximum given in clause 7 for the specified wavelength(s), bend radius, and number of turns.
+
+NOTE 1 – A qualification test may be sufficient to ensure that this requirement is being met.
+
+NOTE 2 – The recommended number of turns corresponds to the approximate number of turns deployed in all splice cases of a typical repeater span. The recommended radius is equivalent to the minimum bend-radius widely accepted for long-term deployment of fibres in practical systems installations to avoid static-fatigue failure.
+
+NOTE 3 – If, for practical reasons, fewer than the recommended number of turns are chosen to be implemented, it is suggested that not less than 40 turns, and a proportionately smaller loss increase be required.
+
+NOTE 4 – The macrobending loss recommendation relates to the deployment of fibres in practical single-mode fibre installations. The influence of the stranding-related bending radii of cabled single-mode fibres on the loss performance is included in the loss specification of the cabled fibre.
+
+NOTE 5 – In the event that routine tests are required, a smaller diameter loop with one or several turns can be used instead of the recommended test, for accuracy and measurement ease. In this case, the loop diameter, number of turns, and the maximum permissible bend loss for the several-turn test should be chosen so as to correlate with the recommended test and allowed loss.
+
+## 5.7 Material properties of the fibre
+
+### 5.7.1 Fibre materials
+
+The substances of which the fibres are made should be indicated.
+
+NOTE – Care may be needed in fusion splicing fibres of different substances. Provisional results indicate that adequate splice loss and strength can be achieved when splicing different high-silica fibres.
+
+### 5.7.2 Protective materials
+
+The physical and chemical properties of the material used for the fibre primary coating and the best way of removing it (if necessary) should be indicated. In the case of single jacketed fibre, similar indications shall be given.
+
+### 5.7.3 Proofstress level
+
+The specified proofstress, $\sigma_p$ , shall not be less than the minimum specified in clause 7.
+
+NOTE – The definitions of the mechanical parameters are contained in clauses 3.2.3 and 5.6 of [ITU-T G.650.1].
+
+## 5.8 Refractive index profile
+
+The refractive index profile of the fibre does not generally need to be known.
+
+## 5.9 Longitudinal uniformity of chromatic dispersion
+
+Under study.
+
+NOTE – At a particular wavelength, the local absolute value of chromatic dispersion coefficient can vary away from the value measured on a long length. If the value decreases to a small value at a wavelength that is close to an operating wavelength in a WDM system, four-wave mixing can induce the propagation of power at other wavelengths, including, but not limited to, other operating wavelengths. The magnitude of the four-wave mixing power is a function of the absolute value of chromatic dispersion coefficient, the chromatic dispersion slope, the operating wavelengths, the optical power, and the distance over which four-wave mixing occurs.
+
+## 5.10 Chromatic dispersion coefficient
+
+The chromatic dispersion coefficient, $D$ , is specified with a wavelength range. [ITU-T G.650.1] provides measurement methods. There are two methods for specifying the limits, the original method, which is a box-like specification, and a newer method, in which the dispersion coefficient values are bound by a pair of curves.
+
+NOTE 1 – Chromatic dispersion uniformity should be consistent with the functioning of the system.
+
+NOTE 2 – The requirements on chromatic dispersion follow from WDM system design, which must balance first order chromatic dispersion with various non-linear effects, such as four-wave mixing, cross-phase modulation, modulation instability, stimulated Brillouin scattering, and soliton formation (see [b-ITU-T G.663]). The effect of chromatic dispersion is interactive with the fibre non-linearity, described by the non-linear coefficient.
+
+NOTE 3 – It is not necessary to measure the chromatic dispersion coefficient on a routine basis.
+
+### 5.10.1 Original specification form
+
+This specification form applies to Table 1 in clause 7, as well as to the G.655.A and G.655.B tables.
+
+The chromatic dispersion coefficient, $D$ , is specified within a wavelength range by stating a range of allowed absolute values of the chromatic dispersion coefficient. The chromatic dispersion coefficient shall not cross zero within the specified wavelength range. The sign of the chromatic dispersion is also specified. The form of the specification is:
+
+$$D_{min} \leq |D(\lambda)| \leq D_{max} \quad \text{for } \lambda_{min} \leq \lambda \leq \lambda_{max}$$
+
+where:
+
+$$0.1 \text{ ps/nm}\cdot\text{km} \leq D_{min} \leq D_{max} \leq 10.0 \text{ ps/nm}\cdot\text{km}$$
+
+$$1530 \text{ nm} \leq \lambda_{min} \leq \lambda_{max} \leq 1565 \text{ nm}$$
+
+$$D_{max} \leq D_{min} + 5.0 \text{ ps/nm}\cdot\text{km}$$
+
+Values for $D_{min}$ , $D_{max}$ , $\lambda_{min}$ , $\lambda_{max}$ , and sign shall be within the ranges given in clause 7. Some examples of implementation are given in Appendix I. Extension to wavelength ranges above 1565 nm and below 1530 nm are under consideration.
+
+NOTE 1 – $D_{min}$ does not necessarily occur at $\lambda_{min}$ and $D_{max}$ does not necessarily occur at $\lambda_{max}$ .
+
+NOTE 2 – The sign of $D$ does not change over the above wavelength range for a given fibre, but it may change from one fibre to another within a system.
+
+NOTE 3 – Depending on the system design and transmission type, it may be necessary to specify the sign of $D$ .
+
+### 5.10.2 Specification based on a pair of limiting curves
+
+This specification form applies to Tables 2 and 3 of clause 7.
+
+For each wavelength, $\lambda$ , the chromatic dispersion coefficient, $D(\lambda)$ , shall be restricted to a range of values associated with two limiting curves, $D_{min}(\lambda)$ and $D_{max}(\lambda)$ , for one or more specified wavelength ranges defined in terms of $\lambda_{min}$ and $\lambda_{max}$ .
+
+An example set of curves is represented symbolically as a pair of straight lines:
+
+$$D_{min}(\lambda) = a_{min} + b_{min}(\lambda - 1460) \quad (\text{ps/nm}\cdot\text{km})$$
+
+$$D_{max}(\lambda) = a_{max} + b_{max}(\lambda - 1460) \quad (\text{ps/nm}\cdot\text{km})$$
+
+$$D_{min}(\lambda) \leq D(\lambda) \leq D_{max}(\lambda) \quad (\text{ps/nm}\cdot\text{km})$$
+
+The bounding curves may vary from one wavelength range to another.
+
+# 6 Cable attributes
+
+Since the geometrical and optical characteristics of fibres given in clause 5 are barely affected by the cabling process, this clause will give recommendations mainly relevant to transmission characteristics of cabled factory lengths. Environmental and test conditions are paramount and are described in the guidelines for test methods.
+
+## 6.1 Attenuation coefficient
+
+The attenuation coefficient is specified with a maximum value at one or more wavelengths in the 1550 nm region. The optical fibre cable attenuation coefficient values shall not exceed the values found in clause 7.
+
+NOTE – The attenuation coefficient may be calculated across a spectrum of wavelengths, based on measurements at a few (3 to 4) predictor wavelengths. This procedure is described in clause 5.4.4 of [ITU-T G.650.1] and an example is given in Appendix III of [ITU-T G.650.1].
+
+## 6.2 Polarization mode dispersion (PMD) coefficient
+
+When required, cabled fibre polarization mode dispersion shall be specified on a statistical basis, not on an individual fibre basis. The requirements pertain only to the aspect of the link calculated from cable information. The metrics of the statistical specification are found below. Methods of calculations are found in [b-IEC/TR 61282-3] and are summarized in Appendix IV of [ITU-T G.650.2].
+
+The manufacturer shall supply a PMD link design value, $PMD_{Q}$ , that serves as a statistical upper bound for the PMD coefficient of the concatenated optical fibre cables within a defined possible link of *M* cable sections. The upper bound is defined in terms of a small probability level, *Q*, which is the probability that a concatenated PMD coefficient value exceeds $PMD_{Q}$ . For the values of *M* and *Q* given in clause 7, the value of $PMD_{Q}$ shall not exceed the maximum PMD coefficient specified in clause 7.
+
+Measurements and specifications on uncabled fibre are necessary, but not sufficient to ensure the cabled fibre specification. The maximum link design value specified on uncabled fibre shall be less than or equal to that specified for the cabled fibre. The ratio of PMD values for uncabled fibre to cabled fibre depends on the details of the cable construction and processing, as well as on the mode coupling condition of the uncabled fibre. [ITU-T G.650.2] recommends a low mode coupling deployment requiring a low tension wrap on a large diameter spool for uncabled fibre PMD measurements.
+
+The limits on the distribution of PMD coefficient values can be interpreted as being nearly equivalent to limits on the statistical variation of the differential group delay (DGD), that varies randomly with time and wavelength. When the PMD coefficient distribution is specified for optical fibre cable, equivalent limits on the variation of DGD can be determined. The metrics and values for link DGD distribution limits are found in Appendix I.
+
+NOTE 1 – $PMD_{Q}$ specification would be required only where cables are employed for systems that have the specification of the max DGD, i.e., for example, $PMD_{Q}$ specification would not be applied to systems recommended in [b-ITU-T G.957].
+
+NOTE 2 – $PMD_{Q}$ should be calculated for various types of cables, and they should usually be calculated using sampled PMD values. The samples would be taken from cables of similar construction.
+
+NOTE 3 – The $PMD_{Q}$ specification should not be applied to short cables such as jumper cables, indoor cables and drop cables.
+
+# 7 Tables of recommended values
+
+The following tables summarize the recommended values for a number of categories of fibres that satisfy the objectives of this Recommendation. These categories are largely distinguished on the basis of PMD requirements and chromatic dispersion characteristics. See Appendix I for information about transmission distances and bit-rates relative to PMD requirements.
+
+Tables 1, 2 and 3 of this version correspond to Tables 3, 4 and 5 of the 2006 edition, respectively.
+
+Table 1, "G.655.C Attributes", retains the original "box-type" specification for the dispersion coefficient, which allows a reference to negative dispersion fibres that may be suitable as part of dispersion managed links such as those that may be used in submarine systems. This also supports optical interface Recommendations such as [b-ITU-T G.691], [b-ITU-T G.959.1] and [b-ITU-T G.693]. For DWDM systems, channel spacings defined in [b-ITU-T G.694.1] are supported, depending on the minimum dispersion that is selected. The PMD requirement allows operation of STM-64 systems to lengths of up to 2000 km, depending on other system elements.
+
+Table 2, "G.655.D Attribute", defines the chromatic dispersion coefficient requirements as a pair of bounding curves versus wavelength for wavelengths from 1460 nm to 1625 nm. For wavelengths greater than 1530 nm, the dispersion is positive and of sufficient magnitude to suppress most non-linear impairments. For these wavelengths, the applications mentioned in Table 1 are supported. For wavelengths less than 1530 nm, the dispersion crosses zero, but the fibre can be used to support CWDM applications at channels from 1471 nm and higher.
+
+Table 3, "G.655.E Attribute", defines the chromatic dispersion requirements in the same style as Table 2, but has higher values which can be important for some systems, e.g., for those with the smallest channel spacings. The applications mentioned in Table 1 are supported. Fibres meeting these requirements are positive and non-zero at wavelengths above 1460 nm.
+
+NOTE – Many submarine applications can utilize these fibres. For some submarine applications, the full optimization can lead to choosing different limits than are found here. One example could be to allow cable cut-off wavelength values as high as 1500 nm.
+
+Appendix I illustrates various implementation examples that are differentiated on the basis of different chromatic dispersion values, dispersion slope, and different non-linear coefficient link values. These options illustrate possibilities for different tradeoffs between power, channel spacing, link length, amplifier spacing, and bit rate.
+
+**Table 1 – G.655.C attributes**
+
+| Fibre attributes | | |
+|--------------------------------------------------------------------|-------------------------------------|----------------------|
+| Attribute | Detail | Value |
+| Mode field diameter | Wavelength | 1550 nm |
+| | Range of nominal values | 8-11 µm |
+| | Tolerance | ± 0.7 µm |
+| Cladding diameter | Nominal | 125 µm |
+| | Tolerance | ± 1 µm |
+| Core concentricity error | Maximum | 0.8 µm |
+| Cladding non-circularity | Maximum | 2.0% |
+| Cable cut-off wavelength | Maximum | 1450 nm |
+| Macrobend loss | Radius | 30 mm |
+| | Number of turns | 100 |
+| | Maximum at 1625 nm | 0.50 dB |
+| Proof stress | Minimum | 0.69 GPa |
+| Chromatic dispersion coefficient Wavelength range: 1530-1565 nm | $\lambda_{min}$ and $\lambda_{max}$ | 1530 nm and 1565 nm |
+| | Minimum value of $D_{min}$ | 1.0 ps/nm·km |
+| | Maximum value of $D_{max}$ | 10.0 ps/nm·km |
+| | Sign | Positive or negative |
+| | $D_{max} - D_{min}$ | ≤ 5.0 ps/nm·km |
+| Chromatic dispersion coefficient Wavelength range: 1565-1625 nm | $\lambda_{min}$ and $\lambda_{max}$ | TBD |
+| | Minimum value of $D_{min}$ | TBD |
+| | Maximum value of $D_{max}$ | TBD |
+| | Sign | Positive or negative |
+| Uncabled fibre PMD coefficient | Maximum | (Note 1) |
+
+**Table 1 – G.655.C attributes**
+
+| Cable attributes | | |
+|-------------------------------------|--------------------------|-------------|
+| Attribute | Detail | Value |
+| Attenuation coefficient (Note 2) | Maximum at 1550 nm | 0.35 dB/km |
+| | Maximum at 1625 nm | 0.4 dB/km |
+| PMD coefficient (Note 3) | M | 20 cables |
+| | Q | 0.01% |
+| | Maximum PMD Q | 0.20 ps/√km |
+
+NOTE 1 – According to clause 6.2, a maximum PMDQ value on uncabled fibre is specified in order to support the primary requirement on cable PMDQ .
+NOTE 2 – The attenuation coefficient values listed in this table should not be applied to short cables such as jumper cables, indoor cables and drop cables. For example, [b-IEC 60794-2-11] specifies the attenuation coefficient of indoor cables as 1.0 dB/km or less at both 1310 and 1550 nm.
+NOTE 3 – Larger PMDQ values (e.g., ≤ 0.5 ps/√km) can be agreed for particular applications between the manufacturer and user.
+
+**Table 2 – G.655.D attributes**
+
+| Fibre attributes | | |
+|------------------------------------------------|-----------------------------------|------------------------------------------|
+| Attribute | Detail | Value |
+| Mode field diameter | Wavelength | 1550 nm |
+| | Range of nominal values | 8-11 μm |
+| | Tolerance | ± 0.6 μm |
+| Cladding diameter | Nominal | 125 μm |
+| | Tolerance | ± 1 μm |
+| Core concentricity error | Maximum | 0.6 μm |
+| Cladding non-circularity | Maximum | 1.0% |
+| Cable cut-off wavelength | Maximum | 1450 nm |
+| Macrobend loss | Radius | 30 mm |
+| | Number of turns | 100 |
+| | Maximum at 1625 nm | 0.1 dB |
+| Proof stress | Minimum | 0.69 GPa |
+| Chromatic dispersion coefficient (ps/nm·km) | $D_{min}(\lambda)$ : 1460-1550 nm | $\frac{7.00}{90}(\lambda - 1460) - 4.20$ |
+| | $D_{min}(\lambda)$ : 1550-1625 nm | $\frac{2.97}{75}(\lambda - 1550) + 2.80$ |
+| | $D_{max}(\lambda)$ : 1460-1550 nm | $\frac{2.91}{90}(\lambda - 1460) + 3.29$ |
+| | $D_{max}(\lambda)$ : 1550-1625 nm | $\frac{5.06}{75}(\lambda - 1550) + 6.20$ |
+
+**Table 2 – G.655.D attributes**
+
+| Fibre attributes | | |
+|-------------------------------------|--------------------------|-------------|
+| Attribute | Detail | Value |
+| Uncabled fibre PMD coefficient | Maximum | (Note 1) |
+| Attenuation coefficient (Note 2) | Maximum at 1550 nm | 0.35 dB/km |
+| | Maximum at 1625 nm | 0.4 dB/km |
+| PMD coefficient (Note 3) | M | 20 cables |
+| | Q | 0.01% |
+| | Maximum PMD Q | 0.20 ps/√km |
+
+NOTE 1 – According to clause 6.2, a maximum PMDQ value on uncabled fibre is specified in order to support the primary requirement on cable PMDQ .
+
+NOTE 2 – The attenuation coefficient values listed in this table should not be applied to short cables such as jumper cables, indoor cables and drop cables. For example, [b-IEC 60794-2-11] specifies the attenuation coefficient of indoor cables as 1.0 dB/km or less at both 1310 and 1550 nm.
+
+NOTE 3 – Larger PMDQ values (e.g., ≤ 0.5 ps/√km) can be agreed for particular applications between the manufacturer and user.
+
+**Table 3 – G.655.E attributes**
+
+| Fibre attributes | | |
+|------------------------------------------------|-----------------------------------|------------------------------------------|
+| Attribute | Detail | Value |
+| Mode field diameter | Wavelength | 1550 nm |
+| | Range of nominal values | 8-11 μm |
+| | Tolerance | ± 0.6 μm |
+| Cladding diameter | Nominal | 125 μm |
+| | Tolerance | ± 1 μm |
+| Core concentricity error | Maximum | 0.6 μm |
+| Cladding non-circularity | Maximum | 1.0% |
+| Cable cut-off wavelength | Maximum | 1450 nm |
+| Macrobend loss | Radius | 30 mm |
+| | Number of turns | 100 |
+| | Maximum at 1625 nm | 0.1 dB |
+| Proof stress | Minimum | 0.69 GPa |
+| Chromatic dispersion coefficient (ps/nm·km) | $D_{min}(\lambda)$ : 1460-1550 nm | $\frac{5.42}{90}(\lambda - 1460) + 0.64$ |
+| | $D_{min}(\lambda)$ : 1550-1625 nm | $\frac{3.30}{75}(\lambda - 1550) + 6.06$ |
+| | $D_{max}(\lambda)$ : 1460-1550 nm | $\frac{4.65}{90}(\lambda - 1460) + 4.66$ |
+
+**Table 3 – G.655.E attributes**
+
+| Fibre attributes | | |
+|-------------------------------------|-----------------------------------|------------------------------------------|
+| Attribute | Detail | Value |
+| | $D_{max}(\lambda)$ : 1550-1625 nm | $\frac{4.12}{75}(\lambda - 1550) + 9.31$ |
+| Uncabled fibre PMD coefficient | Maximum | (Note 1) |
+| Attenuation coefficient (Note 2) | Maximum at 1550 nm | 0.35 dB/km |
+| | Maximum at 1625 nm | 0.4 dB/km |
+| PMD coefficient (Note 3) | M | 20 cables |
+| | Q | 0.01% |
+| | Maximum PMD Q | 0.20 ps/√km |
+
+NOTE 1 – According to clause 6.2, a maximum PMDQ value on uncabled fibre is specified in order to support the primary requirement on cable PMDQ .
+
+NOTE 2 – The attenuation coefficient values listed in this table should not be applied to short cables such as jumper cables, indoor cables and drop cables. For example, [b-IEC 60794-2-11] specifies the attenuation coefficient of indoor cables as 1.0 dB/km or less at both 1310 and 1550 nm.
+
+NOTE 3 – Larger PMDQ values (e.g., $\leq 0.5$ ps/√km) can be agreed for particular applications between the manufacturer and user.
+
+# Appendix I
+
+## Information for link attributes and system design
+
+(This appendix does not form an integral part of this Recommendation)
+
+A concatenated link usually includes a number of spliced factory lengths of optical fibre cable. The requirements for factory lengths are given in clauses 5 and 6. The transmission parameters for concatenated links must take into account not only the performance of the individual cable lengths but also the statistics of concatenation.
+
+The transmission characteristics of the factory length optical fibre cables will have a certain probability distribution which often needs to be taken into account if the most economic designs are to be obtained. The following clauses should be read with this statistical nature of the various parameters in mind.
+
+Link attributes are affected by factors other than optical fibre cables by such things as splices, connectors, and installation. These factors cannot be specified in this Recommendation. For the purpose of link attribute values estimation, typical values of optical fibre links are provided in clause I.5. Clause I.6 contains examples of implementation where the typical values of chromatic dispersion vary from example to example. The estimation methods of parameters needed for system design are based on measurements, modelling, or other considerations.
+
+## I.1 Attenuation
+
+The attenuation $A$ of a link is given by:
+
+$$A = \alpha L + \alpha_s x + \alpha_c y$$
+
+where:
+
+$\alpha$ : typical attenuation coefficient of fibre cables in a link
+
+$\alpha_s$ : mean splice loss
+
+$x$ : number of splices in a link
+
+$\alpha_c$ : mean loss of line connectors
+
+$y$ : number of line connectors in a link (if provided)
+
+$L$ : link length
+
+A suitable margin should be allocated for future modifications of cable configurations (additional splices, extra cable lengths, ageing effects, temperature variations, etc.). The above equation does not include the loss of equipment connectors. The typical values found in clause I.5 are for the attenuation coefficient of optical fibre links. The attenuation budget used in designing an actual system should account for the statistical variations in these parameters.
+
+### I.2 Chromatic dispersion
+
+The chromatic dispersion in ps/nm can be calculated from the chromatic dispersion coefficients of the factory lengths, assuming a linear dependence on length, and with due regard for the signs of the coefficients (see clause 5.10).
+
+When these fibres are used for transmission in the 1550 nm region, chromatic dispersion accommodation is sometimes employed. In this case, the average link chromatic dispersion is used for design. The relationship is described in terms of the typical chromatic dispersion coefficient and chromatic dispersion slope coefficient at 1550 nm.
+
+Typical values for the chromatic dispersion coefficient, $D_{1550}$ , and chromatic dispersion slope coefficient, $S_{1550}$ , at 1550 nm vary with the specific implementation. Values may be found in clause I.6 for the examples given. These values, together with link length, $L_{Link}$ , can be used to calculate the typical dispersion for use in optical link design.
+
+$$D_{Link}(\lambda) = L_{Link} [D_{1550} + S_{1550}(\lambda - 1550)] \quad (ps/nm)$$
+
+### I.3 Differential group delay (DGD)
+
+The differential group delay is the difference in arrival times of the two polarization modes at a particular wavelength and time. For a link with a specific PMD coefficient, the DGD of the link varies randomly with time and wavelength as a Maxwell distribution that contains a single parameter which is the product of the PMD coefficient of the link and the square root of the link length. The system impairment due to PMD at a specific time and wavelength depends on the DGD at that time and wavelength. So, means of establishing useful limits on the DGD distribution, as it relates to the optical fibre cable PMD coefficient distribution and its limits, have been developed and are documented in [b-IEC/TR 61282-3]. The metrics of the limitations of the DGD distribution follow:
+
+- Reference link length, $L_{Ref}$ : A maximum link length to which the maximum DGD and probability will apply. For longer link lengths, multiply the maximum DGD by the square root of the ratio of actual length to the reference length.
+- Typical maximum cable length, $L_{Cab}$ : The maxima are assured when the typical individual cables of the concatenation or the lengths of the cables that are measured in determining the PMD coefficient distribution are less than this value.
+- Maximum DGD, $DGD_{max}$ : The DGD value that can be used when considering optical system design.
+- Maximum probability, $P_F$ : The probability that an actual DGD value exceeds $DGD_{max}$ .
+
+NOTE – The determination of the contribution of components other than optical fibre cable is beyond the scope of this Recommendation, but is discussed in [b-IEC/TR 61282-3].
+
+### I.4 Non-linear coefficient
+
+The effect of chromatic dispersion is interactive with the non-linear coefficient, $n_2/A_{eff}$ , regarding system impairments induced by non-linear optical effects (see [b-ITU-T G.663] and [ITU-T G.650.2]). Typical values vary with the implementation. The test methods for non-linear coefficient remain under study.
+
+### I.5 Tables of common typical values
+
+The values in Tables I.1 and I.2 are representative of concatenated optical fibre links according to clauses I.1 and I.3, respectively. The implied fibre induced maximum DGD values in Table I.2 are intended for guidance in regard to the requirements for other optical elements that may be in the link.
+
+**Table I.1 – Link attenuation values**
+
+| Attenuation coefficient | Wavelength region | Typical link value |
+|-------------------------|-------------------|--------------------|
+| (Note) | 1530-1565 nm | 0.275 dB/km |
+| | 1565-1625 nm | 0.35 dB/km |
+
+NOTE – Typical link value corresponds to the link attenuation coefficient used in [b-ITU-T G.957] and [b-ITU-T G.692].
+
+**Table I.2 – Differential group delay**
+
+| Maximum PMD Q (ps/√km) | Link length (km) | Implied fibre induced maximum DGD (ps) | Channel bit rates |
+|--------------------------------------|---------------------|----------------------------------------------|-------------------|
+| No specification | | | Up to 2.5 Gbit/s |
+| 0.5 | 400 | 25.0 | 10 Gbit/s |
+| | 40 | 19.0 (Note 1) | 10 Gbit/s |
+| | 2 | 7.5 | 40 Gbit/s |
+| 0.20 | 3000 | 19.0 | 10 Gbit/s |
+| | 80 | 7.0 | 40 Gbit/s |
+| 0.10 | > 4000 | 12.0 | 10 Gbit/s |
+| | 400 | 5.0 | 40 Gbit/s |
+
+NOTE 1 – This value applies also for 10 Gigabit Ethernet systems.
+
+NOTE 2 – Cable section length is 10 km except for the 0.10 ps/√km, > 4000 km link, where it is set to 25 km, the probability level is $6.5 \cdot 10^{-8}$ .
+
+### I.6 Examples of implementation
+
+The following are examples of implementations that are designed to optimize various tradeoffs in power, channel spacing, amplifier separation, link length and bit rate. All these examples are primarily variations in the allowed chromatic dispersion, dispersion slope, and non-linear coefficient. These are examples only, which do not preclude other possible implementations. The example identifiers are arbitrary and do not reflect any priority.
+
+**Table I.3 – Examples for $\lambda_{min} = 1530$ nm and $\lambda_{max} = 1565$ nm**
+
+| Example ID | $D_{min}$ (ps/nm·km) | $D_{max}$ (ps/nm·km) | Sign | Typical dispersion coefficient at 1550 nm (ps/nm·km) | Typical dispersion slope at 1550 nm (ps/nm 2 ·km) |
+|---------------|-------------------------|-------------------------|------|------------------------------------------------------------|--------------------------------------------------------------------|
+| A | 1.3 | 5.8 | + | 3.7 | 0.070 |
+| B | 2.0 | 6.0 | + | 4.2 | 0.085 |
+| C | 2.6 | 6.0 | + | 4.4 | 0.045 |
+| D | 5.0 | 10.0 | + | 8.0 | 0.058 |
+| E | 1.0 | 6.0 | – | –2.3 | 0.065 |
+
+NOTE – Corresponding values of chromatic dispersion for the 1600 nm wavelength region are under consideration.
+
+### I.7 Chromatic dispersion coefficient limits for Tables 2 and 3
+
+The equations bounding the chromatic dispersion coefficient versus wavelength are based on two surveys, one for the fibres represented by Table 2 and one for the fibres represented by Table 3. There were five and four vendors respectively. Each provided average and standard deviation as a function of wavelength for wavelengths from 1460 to 1625 nm in 5 nm increments. For wavelength and vendor, the average plus and minus three standard deviation was calculated. Then the minimum and maximum across vendors was calculated. These results were fitted with a line spline using a breakpoint at 1550 nm to minimize the sum of absolute values of the difference while maintaining the principle of including all the data within the envelope.
+
+The results for Tables 2 and 3 are shown in Figures I.1 and I.2 respectively. The solid lines are the limits from clause 7. The rest of the data represent the survey results.
+
+
+
+Figure I.1: Table 2 fibre dispersion boundary. A line graph showing Dispersion coeff (ps/nm x km) on the y-axis (ranging from -5.00 to 11.00) versus Wavelength (nm) on the x-axis (ranging from 1460 to 1620). The graph displays several data series, including solid lines and various markers (circles, triangles, crosses, plus signs), all showing a positive correlation between wavelength and dispersion coefficient. The data points are clustered between approximately 3.00 and 9.00 ps/nm x km at 1620 nm. The label G.655\_Fl.1 is present in the bottom right corner.
+
+**Figure I.1 – Table 2 fibre dispersion boundary**
+
+
+
+Figure I.2: Table 3 fibre dispersion boundary. A line graph showing Dispersion coeff (ps/nm x km) on the y-axis (ranging from 0 to 14) versus Wavelength (nm) on the x-axis (ranging from 1460 to 1620). The graph displays several data series, including solid lines and various markers (circles, triangles, crosses, plus signs, asterisks), all showing a positive correlation between wavelength and dispersion coefficient. The data points are clustered between approximately 4.00 and 13.00 ps/nm x km at 1620 nm. The label G.655\_Fl.2 is present in the bottom right corner.
+
+**Figure I.2 – Table 3 fibre dispersion boundary**
+
+The limits in clause 7 are for individual fibres. The range of values associated with links which are a concatenation of individual fibres can be smaller. For ITU-T G.652 fibres, where the diversity of values from vendor to vendor is reduced, the average plus one standard deviation, which is documented in Supplement 39 to the ITU-T G-series Recommendations, can be used for system limit considerations.
+
+The methodology described above was applied to determine the bounding curves that include all the average plus or minus one standard deviation results. The results are presented graphically in Figures I.3 and I.4. The plus or minus three standard deviation data are also presented for comparison. The equations that bound the plus or minus one standard deviation survey results are in Tables I.4 and I.5.
+
+
+
+G.655\_FI.3
+
+Figure I.3: Comparison of Table 2 fibre dispersion boundaries. A line graph showing Dispersion coeff (ps/nm × km) vs Wavelength (nm). The y-axis ranges from -5.00 to 11.00 in increments of 2.00. The x-axis ranges from 1460 to 1620 in increments of 20. Four curves are plotted: 1σ min (blue dashed), 1σ max (purple dashed), 3σ min (red dash-dot), and 3σ max (green solid). All curves show a positive correlation with wavelength. The 3σ max curve is the highest, followed by 1σ max, then 1σ min, and finally 3σ min.
+
+**Figure I.3 – Comparison of Table 2 fibre dispersion boundaries**
+
+
+
+G.655\_FI.4
+
+Figure I.4: Comparison of Table 3 fibre dispersion boundaries. A line graph showing Dispersion coeff (ps/nm × km) vs Wavelength (nm). The y-axis ranges from 0 to 14 in increments of 2. The x-axis ranges from 1460 to 1620 in increments of 20. Four curves are plotted: 1σ min (blue dashed), 1σ max (purple dashed), 3σ min (red dash-dot), and 3σ max (green solid). All curves show a positive correlation with wavelength. The 3σ max curve is the highest, followed by 1σ max, then 1σ min, and finally 3σ min.
+
+**Figure I.4 – Comparison of Table 3 fibre dispersion boundaries**
+
+**Table I.4 – Table 2 fibre $\pm$ one standard deviation limits**
+
+| | | |
+|------------------------------------------------|-----------------------------------|------------------------------------------|
+| Chromatic dispersion coefficient (ps/nm·km) | $D_{min}(\lambda)$ : 1460-1550 nm | $\frac{6.94}{90}(\lambda - 1460) - 3.34$ |
+| | $D_{min}(\lambda)$ : 1550-1625 nm | $\frac{3.13}{75}(\lambda - 1550) + 3.60$ |
+| | $D_{max}(\lambda)$ : 1460-1550 nm | $\frac{2.78}{90}(\lambda - 1460) + 2.60$ |
+| | $D_{max}(\lambda)$ : 1550-1625 nm | $\frac{5.28}{75}(\lambda - 1550) + 5.38$ |
+
+**Table I.5 – Table 3 fibre $\pm$ one standard deviation limit**
+
+| | | |
+|------------------------------------------------|-----------------------------------|------------------------------------------|
+| Chromatic dispersion coefficient (ps/nm·km) | $D_{min}(\lambda)$ : 1460-1550 nm | $\frac{5.28}{90}(\lambda - 1460) + 1.68$ |
+| | $D_{min}(\lambda)$ : 1550-1625 nm | $\frac{3.05}{75}(\lambda - 1550) + 6.96$ |
+| | $D_{max}(\lambda)$ : 1460-1550 nm | $\frac{4.56}{90}(\lambda - 1460) + 3.89$ |
+| | $D_{max}(\lambda)$ : 1550-1625 nm | $\frac{3.96}{75}(\lambda - 1550) + 8.45$ |
+
+# Bibliography
+
+- [b-ITU-T G.663] Recommendation ITU-T G.663 (2000), *Application related aspects of optical amplifier devices and subsystems.*
+- [b-ITU-T G.691] Recommendation ITU-T G.691 (2006), *Optical interfaces for single channel STM-64 and other SDH systems with optical amplifiers.*
+- [b-ITU-T G.692] Recommendation ITU-T G.692 (1998), *Optical interfaces for multichannel systems with optical amplifiers.*
+- [b-ITU-T G.693] Recommendation ITU-T G.693 (2006), *Optical interfaces for intra-office systems.*
+- [b-ITU-T G.694.1] Recommendation ITU-T G.694.1 (2002), *Spectral grids for WDM applications: DWDM frequency grid.*
+- [b-ITU-T G.695] Recommendation ITU-T G.695 (2005), *Optical interfaces for coarse wavelength division multiplexing applications.*
+- [b-ITU-T G.696.1] Recommendation ITU-T G.696.1 (2005), *Longitudinally compatible intra-domain DWDM applications.*
+- [b-ITU-T G.698.1] Recommendation ITU-T G.698.1 (2005), *Multichannel DWDM applications with single-channel optical interfaces.*
+- [b-ITU-T G.957] Recommendation ITU-T G.957 (2006), *Optical interfaces for equipments and systems relating to the synchronous digital hierarchy.*
+- [b-ITU-T G.959.1] Recommendation ITU-T G.959.1 (2006), *Optical transport network physical layer interfaces.*
+- [b-IEC 60794-2-11] IEC 60794-2-11 (2005), *Optical fibre cables – Part 2-11: Indoor cables – Detailed specification for simplex and duplex cables for use in premises cabling.*
+- [b-IEC/TR 61282-3] IEC/TR 61282-3 (2002), *Fibre optic communication design guides – Part 3: Calculation of polarization mode dispersion.*
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|---------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/G/T-REC-G.661-202505-I_PDF-E/raw.md b/marked/G/T-REC-G.661-202505-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..628a484e129e781777f30c357c701cf0fc528be7
--- /dev/null
+++ b/marked/G/T-REC-G.661-202505-I_PDF-E/raw.md
@@ -0,0 +1,1013 @@
+
+
+# Recommendation**ITU-T G.661 (05/2025)**
+
+SERIES G: Transmission systems and media, digital systems and networks
+
+Transmission media and optical systems characteristics –
+Characteristics of optical components and subsystems
+
+---
+
+### **Definitions and test methods for the relevant generic parameters of optical amplifier devices and subsystems**
+
+
+
+The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font overlaid on the globe.
+
+ITU logo
+
+## ITU-T G-SERIES RECOMMENDATIONS **Transmission systems and media, digital systems and networks**
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100-G.199 |
+| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200-G.299 |
+| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300-G.399 |
+| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400-G.449 |
+| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450-G.499 |
+| TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS | G.600-G.699 |
+| General | G.600-G.609 |
+| Symmetric cable pairs | G.610-G.619 |
+| Land coaxial cable pairs | G.620-G.629 |
+| Submarine cables | G.630-G.639 |
+| Free space optical systems | G.640-G.649 |
+| Optical fibre cables | G.650-G.659 |
+| Characteristics of optical components and subsystems | G.660-G.679 |
+| Characteristics of optical systems | G.680-G.699 |
+| DIGITAL TERMINAL EQUIPMENTS | G.700-G.799 |
+| DIGITAL NETWORKS | G.800-G.899 |
+| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900-G.999 |
+| MULTIMEDIA QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER-RELATED ASPECTS | G.1000-G.1999 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.6000-G.6999 |
+| DATA OVER TRANSPORT – GENERIC ASPECTS | G.7000-G.7999 |
+| PACKET OVER TRANSPORT ASPECTS | G.8000-G.8999 |
+| ACCESS NETWORKS | G.9000-G.9999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T G.661
+
+# Definitions and test methods for the relevant generic parameters of optical amplifier devices and subsystems
+
+## Summary
+
+Recommendation ITU-T G.661 provides the definitions of the relevant parameters, common to the different types of optical amplifiers and the test methods of said parameters to be followed, as far as applicable, for optical amplifier devices and subsystems covered by ITU-T Recommendations.
+
+In this edition of Recommendation ITU-T G.661, the reference diagram and definition of the remote optically pumped amplifier (ROPA) are added.
+
+## History \*
+
+| Edition | Recommendation | Approval | Study Group | Unique ID |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0 | ITU-T G.661 | 1993-03-12 | 15 | 11.1002/1000/888 |
+| 2.0 | ITU-T G.661 | 1996-11-11 | 15 | 11.1002/1000/3813 |
+| 3.0 | ITU-T G.661 | 1998-10-13 | 15 | 11.1002/1000/4512 |
+| 4.0 | ITU-T G.661 | 2006-03-29 | 15 | 11.1002/1000/8752 |
+| 5.0 | ITU-T G.661 | 2007-07-29 | 15 | 11.1002/1000/9153 |
+| 6.0 | ITU-T G.661 | 2025-05-14 | 15 | 11.1002/1000/16330 |
+
+## Keywords
+
+Erbium-doped fibre amplifiers, EDFA, optical amplifiers, planar optical waveguide amplifiers, POWA, remote optically pumped optical amplifiers, ROPA, semiconductor optical amplifiers, SOA.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at .
+
+© ITU 2026
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|--------------------------------------------------------------------------------------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References ..... | 1 |
+| 3 Definitions ..... | 2 |
+| 3.1 Terms defined elsewhere ..... | 2 |
+| 3.2 Terms defined in this Recommendation ..... | 2 |
+| 4 Abbreviations and acronyms ..... | 15 |
+| 5 Conventions ..... | 16 |
+| 6 Classification ..... | 16 |
+| 7 Test methods ..... | 17 |
+| Appendix I – Main differences between optical fibre amplifiers and semiconductor optical amplifiers ..... | 19 |
+| I.1 General remarks ..... | 19 |
+| I.2 Comparison of optical performance characteristics between SOA and OFA ..... | 20 |
+| I.3 Applications ..... | 21 |
+| Appendix II – Environmental, mechanical, physical and reliability parameters of optical amplifier devices and subsystems ..... | 22 |
+| II.1 Parameters for OA devices ..... | 22 |
+| II.2 Parameters for OA subsystems ..... | 23 |
+| II.3 Environmental and reliability test methods ..... | 24 |
+| Appendix III – Remote optically pumped optical amplifiers (ROPA) ..... | 25 |
+| III.1 ROPA structure ..... | 25 |
+| III.2 ROPA amplification mechanism ..... | 25 |
+| III.3 Typical configurations of an ROPA ..... | 25 |
+| Bibliography ..... | 27 |
+
+
+
+# Recommendation ITU-T G.661
+
+# Definitions and test methods for the relevant generic parameters of optical amplifier devices and subsystems
+
+## 1 Scope
+
+This Recommendation applies to all commercially available optical amplifiers (OAs), optically amplified subsystems and optical network elements (ONEs) containing OAs. It applies to OAs using optically pumped fibres (OFAs based either on rare-earth doped fibres or on the Raman effect), semiconductors (SOAs) and waveguides (POWs).
+
+This Recommendation provides the definitions of the relevant parameters, common to the different types of OAs, listed in clause 6, and the test methods of said parameters described in clause 7, to be followed, as far as applicable, for OA devices and subsystems covered by ITU-T Recommendations. Parameter definitions applicable specifically to distributed Raman amplifiers, however, can be found in [ITU-T G.665].
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [[ITU-T G.662](#)] Recommendation ITU-T G.662 (2005), *Generic characteristics of optical amplifier devices and subsystems*.
+- [[ITU-T G.664](#)] Recommendation ITU-T G.664 (2012), *Optical safety procedures and requirements for optical transmission systems*.
+- [[ITU-T G.665](#)] Recommendation ITU-T G.665 (2005), *Generic characteristics of Raman amplifiers and Raman amplified subsystems*.
+- [[ITU-T G.680](#)] Recommendation ITU-T G.680 (2007), *Physical transfer functions of optical network elements*.
+- [IEC 60825-1] IEC 60825-1:2014, *Safety of laser products – Part 1: Equipment classification and requirements*.
+- [IEC 60825-2] IEC 60825-2:2021, *Safety of laser products – Part 2: Safety of optical fibre communication systems (OFCs)*.
+- [IEC 61290-x] IEC 61290 (all parts), *Optical amplifiers – Test methods*.
+- [IEC TR 61292-3] IEC TR 61292-3:2020, *Optical amplifiers – Part 3: Classification, characteristics and applications*.
+- [IEC TR 61292-4] IEC TR 61292-4:2023, *Optical amplifiers – Part 4: Maximum permissible optical power for the damage-free and safe use of optical amplifiers, including Raman amplifiers*.
+
+Parameters specified for OAs are those characterizing the transmission, operation, reliability and environmental properties of the OA seen as a "black box" from a general point of view. In [ITU-T G.662], a subset of these parameters is specified according to the type and application of the particular OA device or subsystem.
+
+# 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+None.
+
+### 3.2 Terms defined in this Recommendation
+
+The list of parameter definitions of OAs, given in the following part of this clause, is divided into two parts: the first part lists those parameters relevant for OA devices, namely power, pre-, line-, distributed amplifiers and ONEs containing OAs; the second part lists the parameters relevant for optically amplified, elementary subsystems, namely the optically amplified transmitter (OAT) and the optically amplified receiver (OAR).
+
+Where the value of a parameter is given for a particular device, it will be necessary to specify certain appropriate operating conditions such as temperature, bias current, pump optical power, etc. In this clause, two different operating conditions are referred to: *nominal operating conditions*, which are those suggested by the manufacturer for normal use of the OA, and *limiting operating conditions*, in which all the parameters adjustable by the user (e.g., temperature, gain, pump laser injection current, etc.) are at their maximum values, according to the *absolute maximum ratings* stated by the manufacturer.
+
+The OA is considered as a "black box", as shown in Figure 1. The OA device has two optical ports, namely an input and an output port. The ONE, as shown in Figure 2, contains one or more OAs, which can be located at the input as well as at the output. The location and number of OAs depend on their function in the ONE. Some ONE examples are described in [ITU-T G.680]. Each ONE has, at a minimum, one input and one output. The ONE is considered as a "black box". The OAT and OAR are considered as an OA integrated with a transmitter or a receiver, respectively. Both kinds of integration imply that the connection between the transmitter or the receiver and the OA is proprietary and not to be specified. Consequently, only the optical output port can be defined for the OAT (after the OA, as shown in Figure 3) and only the optical input port can be defined for the OAR (before the OA, as shown in Figure 4). The ROPA, as shown in Figure 5, contains an RGU and an RPU. The optical ports may consist of unterminated fibres or optical connectors. Electrical connections for power supply (not shown in Figures 1 to 5) are also necessary. Following this "black box" approach, the loss of both pairs of connectors directly associated with the device (labelled C and C' in Figures 1 to 4, and labelled C1, C2 and C3 in Figure 5) and the corresponding uncertainty will be included within the values of gain, noise figure and other parameters of the OA device.
+
+
+
+Figure 1 – OA device reference diagram. The diagram shows a rectangular box representing the OA device. Inside the box, from left to right, there is a connector labeled 'C'', an optical amplifier labeled 'OA', and another connector labeled 'C''. An input optical fibre enters the box from the left, passing through the first connector. An output optical fibre exits the box from the right, passing through the second connector. Above the box, 'R'' is labeled on the left and 'S'' is labeled on the right. Below the box, the text 'G.661\_F01' is present.
+
+S' Reference point in the optical fibre just after the optical connection (C') of the OA device.
+R' Reference point in the optical fibre just before the optical connection (C') of the OA device.
+
+**Figure 1 – OA device reference diagram**
+
+
+
+Figure 2 – ONE device reference diagram. A block diagram of a ONE device containing an Optical Amplifier (OA) and other functions. The device has two input/output ports. The left port shows a reference point R' in the optical fibre just before the optical connection C' of the ONE device, and a reference point S' in the optical fibre just after the optical connection C' of the ONE device. The right port shows a reference point S' in the optical fibre just after the optical connection C' of the ONE device, and a reference point R' in the optical fibre just before the optical connection C' of the ONE device. The diagram is labeled G.661(07)\_02.
+
+- S' Reference point in the optical fibre just after the optical connection (C') of the ONE device.
+ R' Reference point in the optical fibre just before the optical connection (C') of the ONE device.
+
+**Figure 2 – ONE device reference diagram**
+
+
+
+Figure 3 – OAT reference diagram. A block diagram of an OAT device containing a Transmitter (Tx) and an Optical Amplifier (OA). The device has an output port on the right showing a reference point S in the optical fibre just after the optical connection (C) of the OAT. The diagram is labeled G.661\_F03.
+
+- S Reference point in the optical fibre just after the optical connection (C) of the OAT.
+
+**Figure 3 – OAT reference diagram**
+
+
+
+Figure 4 – OAR reference diagram. A block diagram of an OAR device containing an Optical Amplifier (OA) and a Receiver (Rx). The device has an input port on the left showing a reference point R in the optical fibre just before the optical connection (C) of the OAR. The diagram is labeled G.661(25).
+
+- R: Reference point in the optical fibre just before the optical connection (C) of the OAR
+
+**Figure 4 – OAR reference diagram**
+
+
+
+Figure 5 – ROPA reference diagram. A block diagram of a ROPA device containing an RGU (Regenerator) and an RPU (Regenerator). The device has two input/output ports. The left port shows a reference point R in the optical fibre before the optical connection (C1) of the ROPA. The right port shows a reference point S in the optical fibre after the optical connection (C3) of the ROPA. The diagram is labeled G.661(25).
+
+- S: Reference point in the optical fibre after the optical connection (C3) of the ROPA
+ R: Reference point in the optical fibre before the optical connection (C1) of the ROPA
+
+**Figure 5 – ROPA reference diagram**
+
+It should be noted that the configurations in Figures 1 to 5 are shown in the context of ITU-T reference points. It indicates the loss of two connector pairs are included in the black box OA or ONE rather than one. ITU-T reference planes normally account for connector losses differently, as indicated in [ITU-T G.662]. More complete treatment of this topic can be found in Appendix III of [ITU-T G.665]. The user is advised to take the appropriate loss differences into consideration.
+
+The OA amplifies signals in a nominal *operating wavelength* region. In addition, other signals outside of the band of operating wavelength can in some applications also cross the OA. The purpose of these *out-of-band* signals and their wavelength, or wavelength region, can be specified in the detailed specifications.
+
+When signals at multiple wavelengths are incident on the OA, as is the case in multichannel systems, suitable adjustment of the definitions of some existing relevant parameters is needed together with the introduction of definitions of new parameters relevant to this different application.
+
+A typical configuration of an OA in a multichannel application is shown in Figure 6. At the transmitting side $n$ signals, coming from $n$ optical transmitters, Tx1, Tx2, . . . Txn, each with a unique wavelength, $\lambda_1, \lambda_2, \dots, \lambda_n$ , respectively, are combined by an optical multiplexer (OM). At the receiving side, the $n$ signals at $\lambda_1, \lambda_2, \dots, \lambda_n$ , are separated with an optical demultiplexer (OD) and routed to separate optical receivers, Rx1, Rx2, . . . Rxn, respectively. To characterize the OA in this multichannel application, an input reference plane and an output reference plane are defined at the OA input and output ports, respectively, as shown in Figure 6.
+
+
+
+Figure 6: An optical amplifier in a multichannel application. The diagram shows n optical transmitters (Tx1, Tx2, ..., Txn) connected to an optical multiplexer (OM). The output of the OM is connected to the input of an optical amplifier (OA) via an input reference plane. The input powers at this plane are labeled P\_i1, P\_i2, ..., P\_in. The output of the OA is connected to an optical demultiplexer (OD) via an output reference plane. The output powers at this plane are labeled P\_o1, P\_o2, ..., P\_on, and the amplified spontaneous emission (ASE) noise power spectral density is labeled P\_ASE(λ). The output of the OD is connected to n optical receivers (Rx1, Rx2, ..., Rxn). The diagram is labeled G.661(25) in the bottom right corner.
+
+**Figure 6 – An optical amplifier in a multichannel application**
+
+At the input reference plane, $n$ input signals at the $n$ wavelengths are considered, each with a unique power level, $P_{i1}, P_{i2}, \dots, P_{in}$ , respectively. At the output reference plane, $n$ output signals at the $n$ wavelengths, resulting from the optical amplification of the corresponding $n$ input signals, are considered, each with power level $P_{o1}, P_{o2}, \dots, P_{on}$ , respectively. Moreover, the amplified spontaneous emission, ASE, with a noise power spectral density, $P_{ASE}(\lambda)$ , is also to be considered at the OA output port.
+
+It should be noted that the location of the reference planes in Figure 3 is provided in context of the nomenclature normally used in ITU-T Recommendations. IEC nomenclature treats connector losses differently. A more complete discussion of this topic can be found in Appendix III of [ITU-T G.665].
+
+Most definitions of relevant single-channel parameters can be suitably extended to multichannel applications. When this extension is straightforward, the word "channel" is used in the pertinent parameter. In particular, the noise figure and the signal-spontaneous noise figure may be extended to multichannel applications, channel by channel, by considering the value of $P_{ASE}(\lambda)$ at each channel wavelength and the channel signal bandwidth. For each channel wavelength, there is a unique value of noise figure that is a function of the input power level of all signals. In this case, the parameters channel noise figure and channel signal-spontaneous noise figure are introduced. However, some additional parameters also need to be defined. For each parameter, the particular multichannel configuration, including the full set of channel signal wavelengths and input powers, needs to be specified.
+
+NOTE 1 – Except where noted, the optical powers mentioned in the following are average powers.
+
+NOTE 2 – The parameters defined below will, in general, depend also on temperature and polarization state of input channels. The temperature and state of polarization should be kept constant or controlled or be measured and reported together with the measured parameter.
+
+NOTE 3 – In the case of the distributed amplifier, all the parameters are related to a suitable reference fibre used to emulate the transmission fibre in conjunction with the pumping module.
+
+#### 3.2.1 Definitions for OA devices and ONEs containing OAs
+
+The definitions listed in this clause refer to the meaning of the terms used in the specifications of OA devices and ONEs containing OAs.
+
+**3.2.1.1 gain:** In an OA, the increase of signal optical power from the input reference point R' to the output reference point S', expressed in dB.
+
+NOTE 1 – Care should be taken to exclude the amplified spontaneous emission power from the signal optical powers at both the input and output.
+
+NOTE 2 – This definition is different from the corresponding IEC definition in that it includes the effects of any connectors directly associated with the OA device at both the input and output.
+
+**3.2.1.2 small-signal gain:** The gain of the amplifier, when operated in linear regime, where it is essentially independent of the input signal optical power at a given signal wavelength and pump optical power level.
+
+NOTE – This property can be described at a discrete wavelength or as a function of wavelength.
+
+**3.2.1.3 reverse small-signal gain:** The small-signal gain measured in the reverse direction, i.e., from output port to input port.
+
+**3.2.1.4 maximum small-signal gain:** The highest small-signal gain that can be achieved when the OA is operated within the stated nominal operating conditions.
+
+**3.2.1.5 maximum small-signal gain wavelength:** The wavelength at which the maximum small-signal gain occurs.
+
+**3.2.1.6 maximum small-signal gain variation with temperature:** The change in small-signal gain for temperature variation within a specified range, expressed in dB.
+
+**3.2.1.7 gain-slope under single wavelength operation (for analogue operation):** In the presence of a signal of given wavelength and input power, the derivative of the gain of a small probe versus wavelength, at the signal wavelength, expressed in dB/nm.
+
+NOTE – The probe total average power level should be at least 20 dB below the input signal level, to minimize the effect on the gain wavelength-profile.
+
+**3.2.1.8 small-signal gain variation with wavelength:** The peak-to-peak variation of the small-signal gain over a given wavelength range.
+
+**3.2.1.9 small-signal gain stability:** The degree of small-signal gain fluctuation expressed by the ratio (in dB) of the maximum and minimum small-signal gain, for a certain specified test period, under nominal operating conditions.
+
+**3.2.1.10 large-signal output stability:** The degree of output optical power fluctuation expressed by the ratio (in dB) of the maximum and minimum output signal optical powers, for a certain specified test period, under nominal operating conditions and a specified large input signal optical power.
+
+**3.2.1.11 polarization dependent gain (PDG):** The maximum variation of the OA gains due to a variation of the state of polarization of the input signal under nominal operating conditions.
+
+NOTE – A source of PDG in OAs is the polarization dependent loss of the passive components used inside.
+
+**3.2.1.12 saturation output power (gain compression power):** The optical power level associated with the output signal at which the gain is reduced by $N$ dB (typically $N = 3$ ) with respect to the small-signal gain at the signal wavelength.
+
+NOTE 1 – The wavelength at which the parameter is specified should be stated.
+
+NOTE 2 – The optical pump power, for OFAs, or the pump current, for SOAs, should be stated when applicable.
+
+**3.2.1.13 nominal output signal power:** The signal optical power at the output for a specified signal optical power at the input under nominal operating conditions.
+
+**3.2.1.14 maximum output signal power:** The highest signal optical power at the output that can be obtained from the OA under nominal operating conditions.
+
+**3.2.1.15 input power range:** The range of optical power levels at the input for which the corresponding output signal optical power lies in the specified output power range, where the OA performance is ensured.
+
+**3.2.1.16 channel input power range:** The range of optical channel power levels at the input of the OA or ONE over which all of the other parameters of the device are required to remain within the allowed limits.
+
+**3.2.1.17 output power range:** The range of optical power levels at the output of the OA for which the corresponding input signal power lies in the specified input power range, where the OA performance is ensured.
+
+**3.2.1.18 channel output power range:** The range of optical channel power levels at the output of the OA or ONE that must be present while the corresponding input channels are within the channel input power range.
+
+**3.2.1.19 optical signal-to-noise ratio (OSNR):** The optical signal-to-noise ratio (OSNR) is the ratio of the signal power in the wanted channel to the highest noise power density (referred to 0.1 nm) within the channel frequency range.
+
+**3.2.1.20 noise figure (NF)** (applicable to OA devices only): The decrease of the signal-to-noise ratio (SNR), at the output of an optical detector with unitary quantum efficiency, due to the propagation of a shot-noise-limited signal through the OA, expressed in dB.
+
+NOTE 1 – The operating conditions at which the noise figure is specified should be stated.
+
+NOTE 2 – This property can be described at a discrete wavelength or as a function of wavelength.
+
+NOTE 3 – The noise degradation due to the OA is attributable to multiple contributions, e.g., signal-spontaneous beat noise, spontaneous-spontaneous beat noise, internal reflections noise, signal shot noise, and spontaneous shot noise. Each of these contributions depends on various conditions which should be specified for a correct evaluation of the noise figure.
+
+NOTE 4 – By convention, the noise figure is a positive number.
+
+NOTE 5 – In the case of OAs for analogue applications, the noise figure also represents the ratio between input and the output carrier-to-noise ratios.
+
+**3.2.1.21 forward amplified spontaneous emission (ASE) power level:** The optical power in a specified wavelength range associated with the ASE exiting from the output port under nominal operating conditions.
+
+NOTE 1 – This parameter is particularly important for OAs used as pre-amplifiers or line amplifiers and it depends mainly on the filter used.
+
+NOTE 2 – The operating conditions (e.g., the gain and input signal optical power) at which the ASE level is specified should be stated.
+
+**3.2.1.22 reverse ASE power level:** The optical power in a specified wavelength range associated with the ASE exiting from the optical input port under nominal operating conditions.
+
+**3.2.1.23 maximum input reflectance:** The maximum fraction of incident optical power, at the operating wavelength and over all states of input light polarization, reflected by the OA or ONE from the input port, under nominal specified operating conditions, expressed in dB.
+
+NOTE – The measurement is performed with a given input signal optical power.
+
+**3.2.1.24 output reflectance** (not applicable to optically amplified receivers): The fraction of incident optical power at the operating wavelength reflected by the OA or ONE from the output port, under nominal operating conditions, expressed in dB.
+
+**3.2.1.25 maximum reflectance tolerable at input:** The maximum fraction of power, expressed in dB, exiting the optical input port of the OA or ONE which, when reflected back into the OA or ONE, allows the device to still meet its specifications.
+
+NOTE 1 – The measurement is performed with a given input signal optical power.
+
+NOTE 2 – The noise figure is the parameter most sensitive to this reflectance.
+
+**3.2.1.26 maximum reflectance tolerable at output:** The maximum fraction of power, expressed in dB, exiting the optical output port of the OA or ONE which, when reflected back into the OA or ONE, allows the device to still meet its specifications.
+
+NOTE 1 – The measurement is performed with a given input signal optical power.
+
+NOTE 2 – The noise figure is the parameter most sensitive to this reflectance.
+
+**3.2.1.27 pump leakage to output:** The pump optical power which is emitted from the OA output port.
+
+NOTE 1 – The measurement is performed with a given input signal optical power.
+
+NOTE 2 – The maximum pump leakage to output may occur for no input signal.
+
+**3.2.1.28 pump leakage to input:** The pump optical power which is emitted from the OA input port.
+
+NOTE 1 – The measurement is performed with a given input signal optical power.
+
+NOTE 2 – The maximum pump leakage to input may occur for no input signal.
+
+**3.2.1.29 out-of-band insertion loss:** OA insertion loss for a signal at the specified out-of-band wavelength(s).
+
+**3.2.1.30 out-of-band reverse insertion loss:** OA insertion loss for a signal at the specified out-of-band wavelength(s), measured in the reverse direction, i.e., from output port to input port.
+
+**3.2.1.31 powering and control requirements:** Those electrical currents and/or voltages as well as those electrical signals necessary for OA operation within the stated maximum ratings. Necessary tolerances on electrical powering and switching on and off procedures are included.
+
+**3.2.1.32 maximum power consumption:** Electrical power needed by the OA operating within the absolute maximum ratings.
+
+**3.2.1.33 maximum total output power:** The highest optical power level at the output port of the OA or ONE operating within the absolute maximum ratings.
+
+**3.2.1.34 operating temperature:** The temperature range within which the OA can be operated while still meeting all its specified parameter values.
+
+**3.2.1.35 optical connections:** The connector and/or the fibre type used as input and/or output ports of the OA.
+
+NOTE – The optical, mechanical and environmental characteristics and performances of the optical connectors and of the connecting fibres should be in compliance with [b-IEC 60874-1] and [b-IEC 60793-2], respectively.
+
+**3.2.1.36 polarization mode dispersion (PMD):** When an optical signal travels through an optical fibre, component or subsystem (such as an optical amplifier), the change in the shape and width of the pulse due to the differential group delay (DGD) (the propagation delay difference between the two principal states of polarisation (PSPs)) and to the waveform distortion for each PSP, is due to PMD. PMD, together with polarization dependent loss (PDL) and polarization dependent gain (PDG), may introduce large waveform distortions leading to an unacceptable bit error ratio increase.
+
+NOTE – The level of PMD may depend on temperature and operating conditions.
+
+**3.2.1.37 principal states of polarization (PSP):** At a given frequency (or wavelength), the two orthogonal input states of polarization for which the corresponding output states of polarization (SOPs) are independent of optical frequency to first order.
+
+NOTE 1 – An optical fibre, component or subsystem is typically characterized by two PSPs that are a function of the intrinsic birefringence of the material and the induced external and internal stresses acting on it.
+
+NOTE 2 – The DGD between these two PSPs can vary with time and wavelength.
+
+NOTE 3 – A signal whose SOP is aligned with one of the PSPs will be unaffected by the amount of PMD, at least to first order.
+
+**3.2.1.38 degree of polarization (DOP)** (applicable to pumping devices for fibre Raman amplifiers): For each emission wavelength of the optical pump source, the value:
+
+$$\frac{P_{\max} - P_{\min}}{P_{\max} + P_{\min}}$$
+
+expressed as a percentage, where $P_{\max}$ and $P_{\min}$ are, respectively, the maximum and minimum optical output powers of the pump source over all states of polarization at that wavelength of emission and measured within a specified bandwidth.
+
+NOTE 1 – Because the Raman effect exploited in Raman amplifiers is polarization dependent, the degree of polarization can influence the polarization dependent gain of the amplifier.
+
+NOTE 2 – Because Raman amplifiers are often pumped with multiple wavelengths and multimode lasers, it is necessary to determine separately the degree of polarization at every wavelength of emission, rather than just the degree of polarization of the total optical output.
+
+**3.2.1.39 noise factor (F)**: The noise figure expressed in linear form.
+
+**3.2.1.40 multi-path interference (MPI) figure of merit**: The noise factor contribution caused by multi-path interference integrated over all baseband frequencies (zero to infinity).
+
+NOTE – For example, multiple path interference can be caused by successive partial reflections in the optical path.
+
+**3.2.1.41 double Rayleigh scattering figure of merit**: The noise factor contribution caused by multi-path interference due to double Rayleigh scattering integrated over all baseband frequencies (zero to infinity).
+
+NOTE – Double Rayleigh scattering is particularly relevant to fibre Raman amplifiers, both distributed and discrete, because of the long amplifying fibre lengths providing substantial amounts of scattered light together with gain. Other fibre amplifiers with high gain and long fibres can also show this effect. The contribution becomes larger at higher gain levels.
+
+**3.2.1.42 frequency-independent contribution to noise factor**: The noise factor excluding the noise contribution from multi-path interference.
+
+**3.2.1.43 signal-spontaneous noise figure ( $NF_{\text{sig-sp}}$ )**: The signal-spontaneous beat noise contribution to the noise figure, expressed in dB.
+
+**3.2.1.44 (equivalent) spontaneous-spontaneous optical bandwidth ( $B_{\text{sp-sp}}$ )**: The equivalent optical bandwidth by which the square of the ASE spectral power density, $\rho_{\text{ase}}$ , at the signal optical frequency, $v_{\text{sig}}$ , is multiplied in order to obtain the integral of the squared ASE spectral power density over the full ASE bandwidth, $B_{\text{ase}}$ , that is:
+
+$$B_{\text{sp-sp}} = \rho_{\text{ase}}^{-2}(v_{\text{sig}}) \cdot \int_{B_{\text{ase}}} \rho_{\text{ase}}^2(v) dv$$
+
+NOTE 1 – The equivalent spontaneous-spontaneous optical bandwidth can be minimized by using an optical filter at the output of the OA.
+
+NOTE 2 – This parameter is related to the spontaneous-spontaneous beat noise generation, and thus it requires the use of the squared ASE spectral power density.
+
+**3.2.1.45 effective noise figure** (only applicable to distributed amplifiers): The decrease of the signal-to-noise ratio (SNR) at the output of an optical detector with unitary quantum efficiency, due to the propagation of a shot-noise-limited signal through an optical fibre providing distributed
+
+amplification when the pumping is active compared to when the pumping is disabled, expressed in dB.
+
+NOTE 1 – The effective noise figure differs from the noise figure in that it does not compare the SNR at the output with the SNR at the input of the amplifier. The increase in signal strength relevant to the change in SNR is thus the effective gain rather than the gain. In particular, the contribution of signal-spontaneous noise figure, which can be calculated from the difference between ASE power and gain expressed in dB, is then reduced in the effective noise figure by the amount of passive loss between the input and output. It is thus possible for the effective noise figure of distributed amplification to be negative, expressed in dB.
+
+NOTE 2 – The effective noise figure can be understood as the noise figure of an equivalent discrete optical amplifier placed at the end of the optical fibre, which produces the effective gain and the same ASE output power as the distributed amplification. Because the ASE produced within the fibre of the distributed amplifier is also partially reduced by the attenuation of this fibre, the ASE output power can be lower than physically realisable from such a discrete amplifier.
+
+**3.2.1.46 equivalent signal-spontaneous noise figure** (only applicable to distributed amplifiers): The signal-spontaneous beat noise contribution to the effective noise figure.
+
+**3.2.1.47 ASE bandwidth:** The difference between the two wavelengths at which a specified decrease of the output ASE from the peak value of the output ASE spectrum is observed.
+
+NOTE 1 – A decrease of 30 to 40 dB is considered to be adequate.
+
+NOTE 2 – Due to possible distortion of the measured spectrum, e.g., caused by pump leakage, a suitable extrapolation may be necessary.
+
+**3.2.1.48 in-band insertion loss** (applicable to OA devices only): In an electrically unpowered condition, the signal insertion loss for the OA at a given input signal wavelength and a given signal power level.
+
+NOTE 1 – This property can be described at a discrete wavelength or as a function of wavelength.
+
+NOTE 2 – Care should be taken to exclude the output ASE contribution in the measurement of this parameter.
+
+NOTE 3 – The in-band insertion loss is a function of the input signal power level.
+
+**3.2.1.49 maximum reflectance tolerable at input and output** (applicable to OA devices only): The maximum reflectance of two identical reflectors simultaneously placed at both input and output ports of an OA, for which the OA still meets its specifications.
+
+NOTE 1 – The measurement is performed with a given input signal optical power.
+
+NOTE 2 – The noise figure is the most sensitive parameter to reflectance.
+
+**3.2.1.50 power wavelength band** (applicable to power amplifiers only): The wavelength range within which the OA output signal power is maintained in the specified output power range, while the OA input signal power lies within the specified input power range.
+
+**3.2.1.51 available signal wavelength band** (applicable to pre-amplifiers with optical filter(s) only): The resulting pre-amplifier OA wavelength band including the effect of the optical filter(s).
+
+**3.2.1.52 tuneable wavelength range** (applicable to pre-amplifiers and optically amplified receivers with tuneable optical filter(s) only): The wavelength range within which the tuneable optical filter(s) inside the pre-amplifier OA can be tuned.
+
+**3.2.1.53 channel gain** (for multichannel operation): Gain for each channel (at wavelength $\lambda_j$ ) in a specified multichannel configuration, expressed in dB.
+
+Channel gain ( $G_j$ ) can be expressed as follows ( $P_{ij}$ and $P_{oj}$ being respectively the input and output power levels, in dBm, of the $j$ -th channel and $j = 1, 2, \dots, n$ ; $n$ total number of channels):
+
+$$G_j = P_{oj} - P_{ij}$$
+
+NOTE – Since the amplifier saturation power level is determined by the combined effect of the input signals at all wavelengths, the channel gain is dependent on the input power level of all signals.
+
+**3.2.1.54 multichannel gain variation (inter-channel gain difference)** (for multichannel operation): The difference between the channel gains of any two of the channels in a specified multichannel configuration, expressed in dB.
+
+Multichannel gain variation can be expressed as follows ( $G_j$ and $G_l$ being respectively the channel gains of $j$ -th and $l$ -th channel and $j, l = 1, 2, \dots, n; j \neq l; n$ total number of channels):
+
+$$\Delta G_{jl} = G_j - G_l$$
+
+NOTE – Normally, this parameter is specified as the maximum multichannel gain variation, intended as the maximum absolute value of multichannel gain variation, considering all possible combinations of channel pairs. The input power levels would normally be set to their minimum and maximum specified values. Input power levels may also be specified to achieve certain gain values or total output power levels. Maximum multichannel gain variation can be expressed as follows:
+
+$$\Delta G_{MAX} = MAX_{j,l} \left\{ \left| \Delta G_{jl} \right| \right\}$$
+
+**3.2.1.55 gain cross-saturation** (for multichannel operation): For a specified multichannel configuration, the ratio of the change in channel gain of one channel, $\Delta G_j$ , to a given change in the input power level of another channel, $\Delta P_l$ , while the input power levels of all other channels are kept constant, expressed in dB per dB.
+
+Gain cross-saturation can be expressed as follows ( $j, l = 1, 2, \dots, n; j \neq l; n$ total number of channels):
+
+$$GXS_{jl} = \Delta G_j / \Delta P_l$$
+
+NOTE – Normally, this parameter is specified for an initial input power distribution among channels in which each channel is at the minimum allowed power level. Other distributions may be indicated in the appropriate product specification.
+
+**3.2.1.56 multichannel gain-change difference (inter-channel gain-change difference)** (for multichannel operation): For a specified channel allocation, the difference of change in gain in one channel with respect to the change in gain of another channel for two specified sets of channel input powers, expressed in dB.
+
+Multichannel gain-change difference can be expressed as follows ( $G_j^{(1)}$ , $G_j^{(2)}$ and $G_l^{(1)}$ , $G_l^{(2)}$ being the channel gains of the $j$ -th and $l$ -th channel at each of the two specified sets of channel input power (1) and (2) respectively, and $j, l = 1, 2, \dots, n; n$ total number of channels):
+
+$$GD_{jl} = \left[ G_j^{(1)} - G_j^{(2)} \right] - \left[ G_l^{(1)} - G_l^{(2)} \right]$$
+
+NOTE 1 – The two specified sets of channel input powers are in general: (1) all input power levels set to the minimum value and (2) all input power levels set to the maximum value.
+
+NOTE 2 – Normally, the maximum multichannel gain-change difference will be specified. Different sets of input conditions could be defined in the appropriate product specification.
+
+NOTE 3 – Forward ASE power level can be relevant for OAs used as pre-amplifiers or line amplifiers. In this case, the channel input power will include the forward ASE contribution.
+
+NOTE 4 – This parameter can be used instead of the multichannel gain tilt when the definition of the gain tilt cannot be applied.
+
+**3.2.1.57 multichannel gain tilt (inter-channel gain-change ratio)** (for multichannel operation): The ratio of the changes in gain in each channel to the change in gain at a reference channel as the input conditions are varied from one set of input channel powers to a second set of input channel powers, expressed in dB per dB.
+
+Multichannel gain tilt can be expressed as follows ( $G_j^{(1)}$ , $G_j^{(2)}$ and $G_r^{(1)}$ , $G_r^{(2)}$ being, respectively, the channel gains of the $j$ -th and the reference channel at each of the two specified sets of channel input powers and $j = 1, 2, \dots, n$ ; $n$ total number of channels):
+
+$$GT_j = [G_j^{(1)} - G_j^{(2)}] / [G_r^{(1)} - G_r^{(2)}]$$
+
+NOTE 1 – Multichannel gain tilt is normally used to predict the gains for each channel for various sets of input channel powers based on observed changes in the reference channel.
+
+NOTE 2 – The sets of input channel powers are generally those in which (1) all power levels are set equal to the maximum allowed and (2) all powers are set equal to the minimum allowed.
+
+NOTE 3 – The reference channel should be specified in the appropriate product specification. The multichannel gain tilt of the reference channel is by definition equal to 1 dB/dB.
+
+NOTE 4 – Application of multichannel gain tilt to prediction of channel gain under different conditions could be impaired in the cases of hybrid multistage amplifiers, inhomogeneous gain media and, in particular, for amplifiers with automatic gain control.
+
+**3.2.1.58 channel addition/removal (steady-state) gain response** (for multichannel operation): For a specified multichannel configuration, the steady-state change in channel gain of any one of the channels due to the addition/removal of one or more other channels, expressed in dB.
+
+NOTE 1 – Normally, the parameter specified is the maximum channel addition/removal gain response when the final or initial power level of each of the input channels is equal to the minimum allowed. However, different final or initial power levels may be indicated in the appropriate product specification.
+
+NOTE 2 – The worst-case channel addition/removal gain response is generally expected to occur when all but one of the channels are added or removed.
+
+**3.2.1.59 channel addition/removal transient gain response** (for multichannel operation): For a specified multichannel configuration, the maximum change in channel gain of any one of the channels due to the addition/removal of one or more other channels during the transient period after channel addition/removal, expressed in dB.
+
+NOTE 1 – Normally, the parameter specified is the maximum channel addition/removal transient gain response when the final or initial power level of each of the input channels is equal to the minimum allowed. However, different final or initial power levels may be indicated in the appropriate product specification.
+
+NOTE 2 – The worst-case channel addition/removal transient gain response is generally expected to occur when all but one of the channels are added or removed.
+
+NOTE 3 – This definition includes both transient gain increase and transient gain reduction in a single parameter and is an alternative method of describing the gain response to the parameters in clauses 3.2.1.65 and 3.2.1.66.
+
+**3.2.1.60 channel addition/removal transient response time constant** (for multichannel operation): The time period from the addition/removal of a channel to the time when the output power level of that or another channel reaches and remains within $\pm N$ dB from its steady-state value.
+
+NOTE 1 – The value of $N$ should be specified in the relevant product specification.
+
+NOTE 2 – This definition is an alternative method of describing the transient duration to the parameter in clause 3.2.1.64.
+
+**3.2.1.61 rate of change of power:** This is the maximum rate of change (in dB/ms) of the total optical power at the input of an OA or ONE for which all other parameters of the device (e.g., transient gain increase or reduction) must remain within the allowed limits for the undisturbed channels.
+
+**3.2.1.62 total input power range:** The range of total optical power level (the sum of all of the channel powers) at the input of the OA or ONE over which all of the other parameters of the device are required to remain within the allowed limits.
+
+**3.2.1.63 input (or output) power change:** The maximum change of the total optical power at the input (or output) of an OA or ONE due to the addition/removal of one or more channels where the power of one or more of the input channels remains undisturbed. This is illustrated in Figure 7. The left side of the figure shows a negative input power change (resulting in a negative value in dB) and the right side shows a positive input power change (resulting in a positive value in dB).
+
+
+
+G.661(25)
+
+Figure 7 consists of six line graphs arranged in two columns and three rows. The left column represents 'Dropped channel(s)' and the right column represents 'Added channel(s)'. Row 1: 'Channel power' vs 'Time'. Left graph shows power dropping to zero; right graph shows power rising from zero. Row 2: 'Channel power' vs 'Time' for 'Undisturbed channel(s)'. Both graphs show a constant horizontal line. Row 3: 'Total input (or output) power' vs 'Time'. Left graph shows a step down in total power; right graph shows a step up. Vertical double-headed arrows indicate the 'Input (or output) power change' between the initial and final steady states.
+
+**Figure 7 – Illustration of input (or output) power change**
+
+**3.2.1.64 transient duration (for multichannel operation):** The time period from the addition/removal of one or more channels to the time when the output power level all of the other channels reaches and remains within $\pm 0.2$ dB from its steady-state value. This is illustrated in Figure 8.
+
+
+
+G.661(25)
+
+Figure 8 is a graph of 'Gain' vs 'Time'. A solid curve represents the gain response over time following a channel change. The curve oscillates (overshoot and undershoot) before settling. Two horizontal dashed lines represent a tolerance band of ±0.2 dB around the final steady-state gain value. The 'Transient duration' is indicated by a horizontal double-headed arrow extending from the start of the gain change to the point where the curve enters and stays within the ±0.2 dB band.
+
+**Figure 8 – Illustration of transient duration**
+
+**3.2.1.65 transient gain increase (for multichannel operation):** For a specified multichannel configuration, the maximum increase in channel gain of any one of the channels due to the addition/removal of one or more other channels during the transient duration after channel addition/removal, expressed in dB. This is illustrated in Figure 9.
+
+
+
+Figure 9: Illustration of transient gain increase and reduction. The graph shows Gain on the y-axis and Time on the x-axis. A curve starts at a baseline, rises to a peak (labeled 'Transient gain increase'), then falls below the baseline to a trough (labeled 'Transient gain reduction'), and finally returns towards the baseline. The label 'G.661(25)' is in the bottom right corner.
+
+**Figure 9 – Illustration of transient gain increase and reduction**
+
+**3.2.1.66 transient gain reduction** (for multichannel operation): For a specified multichannel configuration, the maximum reduction in channel gain of any one of the channels due to the addition/removal of one or more other channels during the transient duration after channel addition/removal, expressed in dB. This is illustrated in Figure 9.
+
+**3.2.1.67 channel noise figure** (for multichannel operation): For a specified multichannel configuration, the noise figure for each channel in a specified optical bandwidth, expressed in dB.
+
+**3.2.1.68 channel signal-spontaneous noise figure** (for multichannel operation): The signal-spontaneous noise figure for each channel in a specified multichannel configuration, expressed in dB.
+
+**3.2.1.69 channel allocation** (for multichannel operation): The channel allocation is given by the number of channels, the nominal central frequencies/wavelengths of the channels and their central frequency/wavelength tolerance.
+
+**3.2.1.70 optical safety**: The precautions or agreed safety standards that installers, operators and manufacturers should observe for safe operation with OAs. Unless otherwise specified, [IEC 60825-1] and [IEC 60825-2] should be used. Additional guidance can be found in [ITU-T G.664] and [IEC TR 61292-4].
+
+#### **3.2.2 Parameters for OA subsystems**
+
+Definitions contained in this clause concern the relevant parameters of elementary OA subsystems, namely the optically amplified transmitter (OAT) and the optically amplified receiver (OAR).
+
+##### **3.2.2.1 Generic OA subsystem**
+
+**3.2.2.1.1 signal wavelength**: The wavelength of the signal optical carrier.
+
+**3.2.2.1.2 signal linewidth**: The full-width half-maximum (FWHM) of the signal optical spectrum.
+
+##### **3.2.2.2 Optically amplified transmitter (OAT) subsystem**
+
+**3.2.2.2.1 signal power after output connector**: The optical power associated with the signal exiting the optical output port of the OAT.
+
+**3.2.2.2.2 operating signal wavelength range**: The wavelength range within which the OAT output signal power is maintained in a specified output power range.
+
+**3.2.2.2.3 ASE power level**: The optical power associated with ASE (amplified spontaneous emission) exiting the optical output port of the OAT, under nominal operating conditions.
+
+**3.2.2.2.4 output reflectance**: The fraction of incident optical power, at the operating wavelength, reflected by the OAT from the optical output port, under nominal operating conditions, expressed in dB.
+
+**3.2.2.2.5 maximum return optical power:** The maximum optical power that can enter the output port of the OAT, for which the OAT still meets its specifications.
+
+**3.2.2.2.6 pump leakage to output:** The pump optical power, which is emitted from the OAT output port, under nominal operating conditions.
+
+NOTE 1 – The measurement is performed with a given signal optical power.
+
+NOTE 2 – The maximum pump leakage to output may occur for no signal.
+
+**3.2.2.2.7 optical connections:** The connector type and/or the fibre type used as the output port of the OAT.
+
+NOTE – The optical, mechanical and environmental characteristics and performances of the optical connector and of the connecting fibre should be in compliance with [b-IEC 60874-1] and [b-IEC 60793-2], respectively.
+
+##### **3.2.2.3 Optically amplified receiver (OAR) subsystem**
+
+**3.2.2.3.1 sensitivity:** The minimum optical power associated with the input signal, immediately before the input connector, necessary to achieve a fixed BER value (e.g., $10^{-12}$ ).
+
+NOTE – Other definitions may be applicable for this parameter and are under consideration.
+
+**3.2.2.3.2 operating signal wavelength range:** The wavelength range within which the OAR has the specified sensitivity and overload input power at a specified BER (e.g., $10^{-12}$ ) and at a specified bit rate.
+
+**3.2.2.3.3 tunable wavelength range** (for OARs with tunable optical filter(s) only): The wavelength range (within the operating signal wavelength range) over which the tunable optical filter(s) inside the OAR can be tuned.
+
+**3.2.2.3.4 ASE power level:** The optical power associated with ASE exiting the input optical port of the OAR, under nominal operating conditions.
+
+**3.2.2.3.5 input reflectance:** The fraction of incident optical power, at the operating wavelength, reflected by the OAR from the optical input port, under nominal operating conditions, expressed in dB.
+
+**3.2.2.3.6 ASE filter bandwidth:** The wavelength FWHM of the ASE filter.
+
+NOTE – The ASE filter bandwidth fixes the maximum linewidth of the input signal.
+
+**3.2.2.3.7 maximum input optical power:** The maximum optical power that can enter the input port of the OAR, for which the OAR still meets its specifications.
+
+**3.2.2.3.8 pump leakage to input:** The pump optical power, which is emitted from the OAR input port, under nominal operating conditions.
+
+NOTE 1 – The measurement is performed with a given input signal optical power.
+
+NOTE 2 – The maximum pump leakage to input may occur for no input signal.
+
+**3.2.2.3.9 optical connections:** The connector type and/or the fibre type used as the input port of the OAR.
+
+NOTE – The optical, mechanical and environmental characteristics and performances of the optical connector and of the connecting fibre should be in compliance with [b-IEC 60874-1] and [b-IEC 60793-2], respectively.
+
+**3.2.2.3.10 safety:** The precautions or agreed safety standards that installers, operators and manufacturers should observe for safe operation with OA subsystems. Unless otherwise specified, [IEC 60825-1] and [IEC 60825-2] should be used. Additional guidance can be found in [ITU-T G.664], Optical safety procedures and requirements for optical transport systems, and [IEC TR 61292-4].
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|--------|---------------------------------------------|
+| ASE | Amplified Spontaneous Emission |
+| BER | Bit Error Ratio |
+| Bsp-sp | Spontaneous-spontaneous optical bandwidth |
+| DGD | Differential Group Delay |
+| DOP | Degree of Polarization |
+| EDFA | Erbium-Doped (silica-based) Fibre Amplifier |
+| F | noise Factor |
+| FIT | Failures In Time |
+| FWHM | Full-Width Half-Maximum |
+| MPI | Multi-Path Interference |
+| MTBF | Mean Time Between Failures |
+| NF | Noise Figure |
+| OA | Optical Amplifier |
+| OAR | Optically Amplified Receiver |
+| OAT | Optically Amplified Transmitter |
+| OBA | Optical Booster Amplifier |
+| ODU | Optical Demultiplexing Unit |
+| OFA | Optical Fibre Amplifier |
+| OMU | Optical Multiplexing Unit |
+| ONE | Optical Network Element |
+| OPA | Optical Pre-Amplifier |
+| OSA | Optical Spectrum Analyser |
+| OTM | Optical Terminal Multiplexer |
+| OTU | Optical channel Transport Unit |
+| PDG | Polarization Dependent Gain |
+| PDL | Polarization Dependent Loss |
+| PMD | Polarization Mode Dispersion |
+| POWA | Planar Optical Waveguide Amplifier |
+| PSP | Principal State of Polarization |
+| RGU | Remote Gain Unit |
+| ROPA | Remote Optically Pumped Amplifier |
+| RPU | Remote Pump Unit |
+| SNR | Signal-to-Noise Ratio |
+| SOA | Semiconductor Optical Amplifier |
+| SOP | State Of Polarization |
+| TM | Test Method |
+
+## 5 Conventions
+
+None.
+
+# 6 Classification
+
+Different OA application categories are defined depending on the technology used and the utilization of the OA itself. Classification of optical amplifier technologies is also given in [IEC TR 61292-3].
+
+These categories are identified by a capital letter, a number and a lower case letter, as follows:
+
+### *Capital letter*
+
+- A OFAs using silica-based fibres doped with erbium ions to produce an active fibre
+- B OFAs using other doped active fibres
+- C Raman amplifiers
+- D SOA
+- E POWA
+- F ROPA
+
+### *Number*
+
+- 1 Power amplifiers (post-amplifiers or booster amplifiers)
+- 2 Pre-amplifiers
+- 3 Line amplifiers
+- 4 Optically amplified transmitter (OAT)
+- 5 Optically amplified receiver (OAR)
+- 6 Distributed amplifiers
+- 7 Composite distributed and discrete amplifiers
+
+### *Lower case letter*
+
+- a Amplifiers for analogue, single (wavelength) channel transmission
+- b Amplifiers for digital, single (wavelength) channel transmission
+- c Amplifiers for digital, multichannel (wavelength) transmission
+
+EXAMPLE – Category A2b refers to optical pre-amplifiers for single-channel digital transmission which use a silica-based fibre doped with Erbium ions.
+
+The *power amplifier* is a high saturation-power OA device to be used directly after the optical transmitter to increase its signal power level.
+
+The *pre-amplifier* is a very low noise OA device to be used directly before an optical receiver to improve its sensitivity.
+
+The *line amplifier* is a low noise OA device to be used between passive fibre sections to increase the distance covered before regeneration is necessary or in correspondence with a point-multipoint connection to compensate for branching losses in the optical access network.
+
+The OAT is an OA subsystem in which a power amplifier is integrated with an optical transmitter, resulting in a higher power transmitter.
+
+The OAR is an OA subsystem in which a pre-amplifier is integrated with an optical receiver, resulting in a higher sensitivity receiver.
+
+The *distributed amplifier* is a device configuration that provides amplification over an extended length of the optical fibre used for transmission, as by Raman pumping, and is thus distributed over part or all of the transmission span.
+
+The *composite distributed and discrete amplifiers* are defined in [ITU-T G.665].
+
+## 7 Test methods
+
+According to an agreement with IEC-SC86C/WG3, the guidelines to be followed for the measurement of most of the parameters defined in clause 3 are generally given in [IEC 61290-x]. Each test method is generally given for the measurement of a group of related parameters. The grouping of the related parameters is given in Table 1, together with the corresponding test method specification reference. The test methods presently reported in [IEC 61290-x] for each group of parameters are also given in Table 1.
+
+NOTE 1 – The test methods contained in these IEC documents relate to IEC parameter definitions which treat connector losses differently from the definitions contained in this Recommendation. A more complete discussion of this topic can be found in Appendix III of [ITU-T G.665].
+
+NOTE 2 – The comparative evaluation of the test methods given in the IEC basic specifications is currently under development. When it is available, the chosen reference test methods and possible alternative test methods for each relevant parameter defined in this Recommendation will be indicated.
+
+**Table 1 – Recommended test methods for parameters defined in clause 3**
+
+| Group of test parameters | Test method specification number | Test methods (TMs) |
+|------------------------------|----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Gain parameters | IEC 61290-1 | IEC 61290-1-1: Optical spectrum analyser (OSA) TM IEC 61290-1-2: Electrical spectrum analyser TM IEC 61290-1-3: Optical power meter TM IEC 61290-10-1: Multichannel pulse method with optical switch and OSA TM IEC 61290-10-2: Multichannel pulse method with gated OSA TM IEC 61290-10-3: Multichannel probe methods TM |
+| Optical power parameters | IEC 61290-1 | IEC 61290-1-1: Optical spectrum analyser TM IEC 61290-1-2: Electrical spectrum analyser TM IEC 61290-1-3: Optical power meter TM IEC 61290-10-1: Multichannel pulse method with optical switch and OSA TM IEC 61290-10-2: Multichannel pulse method with gated OSA TM IEC 61290-10-3: Multichannel probe methods TM |
+| Noise parameters | IEC 61290-3: Test methods for noise figure parameters | IEC 61290-3-1: Optical spectrum analyser TM IEC 61290-3-2: Electrical spectrum analyser TM IEC 61290-10-1: Multichannel pulse method with optical switch and OSA TM IEC 61290-10-2: Multichannel pulse method with gated OSA TM IEC 61290-10-3: Multichannel probe methods TM |
+| Polarization mode dispersion | IEC 61290-11 | IEC 61290-11-1: Jones matrix eigenanalysis TM IEC 61290-11-2: Poincaré sphere analysis TM |
+
+**Table 1 – Recommended test methods for parameters defined in clause 3**
+
+| Group of test parameters | Test method specification number | Test methods (TMs) |
+|---------------------------------|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Reflectance parameters | IEC 61290-5 | IEC 61290-5-1: Optical spectrum analyser TM IEC 61290-5-2: Electrical spectrum analyser TM IEC 61290-5-3: Reflectance tolerance test, electrical spectrum analyser TM |
+| Pump leakage parameters | IEC 61290-6 | IEC 61290-6-1: Optical demultiplexer TM |
+| Insertion loss parameters | IEC 61290-7 | IEC 61290-7-1: Filtered power meter TM |
+| OA subsystem parameters | IEC 61290-9 | Under consideration |
+
+## Appendix I
+
+## Main differences between optical fibre amplifiers and semiconductor optical amplifiers
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This appendix discusses key differences between optical fibre amplifiers and semiconductor optical amplifiers. Broad classes of optical amplifiers including semiconductor amplifiers, optical fibre amplifiers using many types of rare earth dopants and other types of amplifiers are more fully treated in [IEC TR 61292-3]. Additional information on distributed Raman optical amplifiers can be found in [ITU-T G.665].
+
+### I.1 General remarks
+
+The physical mechanism providing gain in semiconductor optical amplifiers (SOAs) differs in various aspects from that of optical fibre amplifiers. Basically, SOAs are semiconductor lasers without the optical cavity feedback (the facets of the chip have an anti-reflection coating) and so the population inversion is generated in the active region by an electrical current. The stimulated emission of photons occurs via electron-hole recombination processes induced by the signal photons (at wavelengths included in the amplification band of the semiconductor material). The gain of semiconductor materials per unit length is much greater than that of rare-earth doped active fibres (REDFs); this accounts for the very short lengths of these devices: 0.5 mm against some tens of metres for REDFs. This fact, together with direct pumping via the bias current, renders the SOAs very simple and compact devices compared to OFAs that require long active fibres, laser sources for optical pumping and various fibre-optic components.
+
+Moreover, SOAs are flexible in terms of operating wavelength and, depending on the composition of the semiconductor material, can be used in second (1310 nm) or third (1550 nm) wavelength region while, at present, high-grade OFAs operate typically around 1550 nm.
+
+Another important difference is that the gain dynamics of SOAs is much faster than that of OFAs. The characteristic time required for the gain to recover completely is typically 200 ps in a SOA against 0.5-10 ms in an OFA. Consequently, SOAs are not immune from cross-saturation interference and saturation induced waveform distortion as OFAs are.
+
+The fast gain-dynamics also implies that SOAs are strongly non-linear when operated in the saturation regime, contrary to OFAs which behave linearly in almost all the operating conditions of interest in optical telecommunications. This feature, which may be detrimental for applications of SOAs as line amplifiers in WDM systems, can be turned to advantage in the implementation of some important system functionalities, such as wavelength conversion, optical switching and demultiplexing.
+
+Finally, the geometry of SOA active guides does not match with that of optical fibres, producing quite high coupling losses with the fibres of the line and, due to the rectangular symmetry, can cause a marked PDG.
+
+These structural differences among SOAs and OFAs do reflect on the performance of the devices. The scope of this appendix is to compare the characteristics of the two types of optical amplifiers. The list of the main optical parameters that should be considered to characterize and to compare the optical performance of the SOAs and EDFA is given in clause I.2. In the following, some indications are given about the values that can be associated with the mentioned SOA parameters and a comparison with the corresponding values for the OFAs. The values reported for OFAs are those typical for EDFAs.
+
+In fact EDFAs represent the most mature OFA technology; EDFA technology is very well consolidated and EDFAs have been distributed on the market for several years and are produced by various manufacturers worldwide. On the other hand, SOAs are still at the R&D stage. Today, very few manufacturers produce them, and the yield is very low. Even though the technology of SOAs is based on the very well assessed semiconductor laser technology, several important problems related to packaging, pig tailing, anti-reflection coating and polarization sensitivity have not found yet satisfactory mass scale production solutions.
+
+Moreover, field trials with SOAs have started recently and there is today only a limited experience in using SOAs in the field [b-REID].
+
+In this appendix, only the amplifying characteristics of the SOAs are taken into consideration as their possible use for the implementation of other functionalities is outside the scope of this appendix.
+
+### I.2 Comparison of optical performance characteristics between SOA and OFA
+
+The values of SOA parameters reported in the following comparison are only indicative and reflect the present state-of-art in SOA technology; they can be subject to changes as SOA technology evolves.
+
+#### – *Small-signal gain*
+
+The small-signal gain of SOAs is affected by the fibre-amplifier coupling loss (negligible in the case of EDFAs). Typical values are around 30 dB for lab prototypes, not including the coupling loss, and 10-15 dB fibre-to-fibre for pigtailed commercial units. For EDFA units, small-signal gain is typically greater than 30 dB.
+
+#### – *Wavelength bandwidth*
+
+The width of wavelength band of SOAs is typically 40 nm or more, compared to 35 nm for EDFAs. SOAs can be used in second (1310 nm) or third (1550 nm) wavelength region, depending on the composition of the semiconductor material. Recent experiments on multi-quantum well SOAs demonstrated the possibility to achieve a wavelength bandwidth as wide as 120 nm.
+
+#### – *Small-signal gain variation with wavelength*
+
+The use of very good anti-reflection coatings on the facets of the chip has allowed to reduce, in commercial SOAs, the peak-to-peak small-signal gain variation with wavelength to less than 1 dB over the width of the wavelength band.
+
+#### – *Saturation output power*
+
+Saturation output power can be as high as +15 dBm for lab prototype SOAs (fibre-to-fibre). The obtained values for this parameter begin to be comparable to those of commercial EDFA units (+17/+20 dBm and more).
+
+#### – *Noise figure (NF)*
+
+The NF of SOAs is affected by the quite high coupling loss with fibres. In SOA lab modules, values around 5-6 dB have been obtained while, in commercial pigtailed units, values ranging from 7 to 9 dB are typical. Typical values for commercial EDFAs are 5-6 dB for 980 nm pumped EDFAs, and 6-7 dB for 1480 nm pumped EDFAs.
+
+#### – *Polarization dependent gain (PDG)*
+
+In lab SOA prototypes, the PDG has been reduced down to negligible values (0.2 dB). In commercial SOAs, typical values are 2-5 dB. PDG is negligible in EDFAs (0.2 dB).
+
+#### – *Gain-dynamic crosstalk*
+
+Under study.
+
+### **I.3 Applications**
+
+At the present stage of the SOA technology, the most suitable applications of SOAs as gain blocks in optical point-to-point systems seem to be as booster amplifiers, integrated with the emitter laser, even though there are some limitations in terms of output power.
+
+Problems related to line and pre-amplifier applications (such as polarization sensitivity and relatively high noise figure) are going to be solved (for example by using gain-clamped SOAs [b-VAN DEN HOVEN]). Recently, SOAs have been successfully utilized as line amplifiers in 10 Gbit/s field trials [b-KUINDERSMA]. In this transmission experiment, the optical system was operated at 1310 nm: a spectral window where high-grade OFAs have not been developed so far.
+
+Moreover, SOAs have a great potential as functional devices in optical switches, to simultaneously provide gain and fast gating functions, and in other signal processing devices (wavelength converters, optical multiplexers and demultiplexers), due to the strong non-linear response they have in the saturation regime. They can also be integrated in optical switch matrices to compensate for the losses internal to the matrix itself.
+
+## Appendix II
+
+## Environmental, mechanical, physical and reliability parameters of optical amplifier devices and subsystems
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Additional terms for the environmental, mechanical, physical and reliability aspects of optical amplifier devices and subsystems are provided for information. These terms are normative terms in [b-IEC 61291-1].
+
+### II.1 Parameters for OA devices
+
+#### II.1.1 External dimensions and weight
+
+The maximum height, length, width and weight of the OA.
+
+#### II.1.2 Environmental conditions
+
+The range of temperature, humidity and vibration level within which the OA can be stored, operated or shipped and still meet all its specified parameter values.
+
+#### II.1.3 Maximum operating relative humidity
+
+The maximum relative humidity at which the OA can be operated and still meet all its specified parameter values.
+
+#### II.1.4 Maximum operating vibration level
+
+The maximum vibration level at which the OA can be operated and still meet all its specified parameter values.
+
+#### II.1.5 Storage temperature
+
+The temperature range within which the OA can be stored and still meet all its specified parameter values.
+
+#### II.1.6 Maximum storage relative humidity
+
+The maximum relative humidity at which the OA can be stored and still meet all its specified parameter values.
+
+#### II.1.7 Maximum transport vibration/shock level
+
+The maximum vibration and shock level that the OA can bear when shipped and still meet all its specified parameter values.
+
+#### II.1.8 Reliability
+
+The expectation of operational lifetime. The reliability of an OA is expressed by either of the following two parameters: mean operating time between failures (MTBF) or failures in time (FIT). The MTBF is the mean period of OA continuous operation without any failure at specified operating and environmental conditions. The FIT is the number of failures in $10^9$ hours under specified operating and environmental conditions.
+
+NOTE – Reliability qualification is addressed by [b-IEC 61291-5-2].
+
+#### II.1.9 Remote and local alarm control
+
+The functions that can check the operation of the OA subsystem, detecting and signalling possible faults.
+
+### **II.2 Parameters for OA subsystems**
+
+Definitions contained in this clause concern the relevant parameters for the environmental, mechanical, physical and reliability aspects of generic OA subsystems, namely the optically amplified transmitter (OAT) and the optically amplified receiver (OAR).
+
+#### **II.2.1 Powering and control requirements**
+
+Those electrical currents and/or voltages as well as those electrical signals necessary for OA subsystem operation within the stated maximum ratings. Necessary tolerances on electrical powering and switching on and off procedures are included.
+
+#### **II.2.2 Maximum power consumption**
+
+The electrical power needed to keep the OA subsystem operating at the stated maximum ratings.
+
+#### **II.2.3 Operating temperature**
+
+The temperature range within which the OA subsystem can be operated and still meet all its specified parameter values.
+
+#### **II.2.4 Maximum operating relative humidity**
+
+The maximum relative humidity at which the OA subsystem can be operated and still meet all its specified parameter values.
+
+#### **II.2.5 Maximum operating vibration level**
+
+The maximum vibration level at which the OA subsystem can be operated and still meet all its specified parameter values.
+
+#### **II.2.6 Storage temperature**
+
+The temperature range within which the OA subsystem can be stored and still meet all its specified parameter values.
+
+#### **II.2.7 Maximum storage relative humidity**
+
+The maximum relative humidity at which the OA subsystem can be stored and still meet all its specified parameter values.
+
+#### **II.2.8 Maximum transport vibration/shock level**
+
+The maximum vibration and shock level that the OA subsystem can bear when shipped and still meet all its specified parameter values.
+
+#### **II.2.9 Reliability**
+
+The expectation of operation lifetime. The reliability of an OA subsystem is expressed by either of the following two parameters: mean operating time between failures (MTBF) or failures in time (FIT). The MTBF is the mean period of continuous operation without any failure at specified operating and environmental conditions. The FIT is the number of failures in $10^9$ hours at specified operating and environmental conditions.
+
+NOTE – Reliability qualification is addressed by [b-IEC 61291-5-2].
+
+#### **II.2.10 Remote and local alarm control**
+
+The functions that can check the operation of the OA subsystem, detecting and signalling possible faults.
+
+### II.3 Environmental and reliability test methods
+
+The test methods presently reported in the IEC 61290 series for parameters defined in this appendix are given in Table II.1.
+
+**Table II.1 – Recommended test methods for parameters defined in Appendix II**
+
+| Group of test parameters | Test method specification number | Test methods (TMs) |
+|------------------------------------------|-------------------------------------------------|---------------------------|
+| Environmental and reliability parameters | [b-IEC 61291-5-2]: Reliability qualification | Under consideration |
+
+## Appendix III
+
+## Remote optically pumped optical amplifiers (ROPA)
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### III.1 ROPA structure
+
+ROPA is a distributed optical amplifier that embeds an erbium-doped fibre in the transmission optical fibre and amplifies optical signals by providing pump light at a remote site. An ROPA consists of two parts:
+
+- A) A remote pump unit (RPU) placed either at the receiving site (backward pumping scheme) or at the transmitting site (forward pumping scheme). In order to achieve long-distance transmission, the pump wavelength is usually set to 1480 nm (with a 980 nm pump, fibre's attenuation would be higher);
+- B) A remote gain unit (RGU) placed within the transmission optical fibre. The RGU contains a section of erbium-doped fibre (EDF) acting as amplification medium for the ROPA.
+
+### III.2 ROPA amplification mechanism
+
+In an ROPA, EDF gain and Raman gain both contribute to amplify the optical signal. The EDF gain acts within an EDF separated from the pump laser and placed in the transmission link, providing amplification without the need of electrical power at an intermediate site. In a backward pumping scheme, the Raman gain, due to the same pump laser, amplifies the signal before it enters into the EDF, improving the optical signal to noise ratio. In a forward pumping scheme, the Raman gain amplifies the signal at the output of the EDF, boosting its power.
+
+### III.3 Typical configurations of an ROPA
+
+ROPA-based transmission systems have two typical configurations, shown in Figure III.1 and Figure III.2:
+
+- A) ROPA with backward pump
+
+In this configuration, pump light and optical signal counter-propagate in the same optical fibre, as shown in Figure III.1.
+
+
+
+The diagram illustrates a ROPA with backward pump configuration. It shows two Optical Transport Module (OTM) units connected by an optical fibre. Each OTM unit contains multiple Optical Transport Units (OTUs) connected to an Optical Multiplexer/Demultiplexer (OMU/ODU). The top OTM unit has OTUs (OTU1, OTU2, OTU3, ..., OTUn) connected to an OMU, which is connected to an Optical Booster Amplifier (OBA). The bottom OTM unit has OTUs connected to an ODU, which is connected to an Optical Pre-Amplifier (OPA). The OPA is connected to a Remote Pump Unit (RPU) containing a Pump laser. The optical fibre between the two OTM units contains two Remote Gain Units (RGU). The pump light from the RPU in the bottom OTM unit propagates backward (upwards) through the fibre, passing through the RGUs and the OPA, and then through the OBA in the top OTM unit. The optical signal from the top OTM unit propagates forward (downwards) through the fibre, passing through the OBA, the RGUs, and the ODU in the bottom OTM unit. The diagram is labeled G.661(25) in the bottom right corner.
+
+Diagram of ROPA with backward pump configuration showing two OTM units connected by optical fibre with RGUs and RPUs.
+
+Figure III.1 – ROPA with backward pump
+
+#### **B) ROPA with forward pump**
+
+In this configuration, pump light and optical signal co-propagate in the same optical fibre, as shown in Figure III.2.
+
+
+
+The diagram illustrates a bidirectional optical communication system using ROPA with forward pump. It consists of two Optical Transport Module (OTM) units connected by two optical fibers. Each fiber contains a Random Gain Unit (RGU) and a pump/RPU component.
+
+**Left OTM Unit:**
+
+- The top path shows multiple Optical Transport Units (OTUs), labeled OTU1, OTU2, OTU3, ..., OTUn, connected to an Optical Multiplexer (OMU). The output of the OMU is connected to an Optical Booster Amplifier (OBA). The OBA is connected to a pump/RPU component. The output of the pump/RPU is connected to an optical fiber via a coupler (represented by a circle).
+- The bottom path shows the same OTUs connected to an Optical Demultiplexer (ODU). The output of the ODU is connected to an Optical Pre-Amplifier (OPA). The OPA is connected to an optical fiber via a coupler.
+
+**Right OTM Unit:**
+
+- The top path shows the optical fiber from the left OTM unit connected to a coupler, which is then connected to an Optical Pre-Amplifier (OPA). The OPA is connected to an Optical Demultiplexer (ODU). The ODU is connected to the OTUs (OTU1, OTU2, OTU3, ..., OTUn).
+- The bottom path shows the OTUs connected to an Optical Multiplexer (OMU). The output of the OMU is connected to an Optical Booster Amplifier (OBA). The OBA is connected to a pump/RPU component. The output of the pump/RPU is connected to the optical fiber via a coupler.
+
+The optical fibers between the OTM units are shown with two couplers each, indicating the co-propagation of pump light and optical signals. The label G.661(25) is present in the bottom right corner of the diagram.
+
+Diagram of ROPA with forward pump configuration showing two OTM units connected by optical fibers with RGUs and pump/RPU components.
+
+**Figure III.2 – ROPA with forward pump**
+
+# Bibliography
+
+- [b-IEC 60793-2] IEC 60793-2:2019, *Optical fibres – Part 2: Product specifications – General*.
+- [b-IEC 60874-1] IEC 60874-1:2006, *Fibre optic interconnecting devices and passive components – Connectors for optical fibres and cables – Part 1: Generic specification*.
+- [b-IEC 61291-1] IEC 61291-1:2018, *Optical amplifiers – Part 1: Generic specification*.
+- [b-IEC 61291-5-2] IEC 61291-5-2:2017, *Optical amplifiers – Part 5-2: Qualification specifications – Reliability qualification for optical fibre amplifiers*.
+- [b-KUINDERSMA] KUINDERSMA (P.I.) *et al.: Proceedings of the 11th International Conference on Integrated Optics and Optical Fibre Communications (IOOC) and of the 23rd European Conference on Optical Communications (ECOC)*, Vol. 1, p. 79, Edinburgh (UK) 1997.
+- [b-REID] REID (J.J.E.) *et al.: 11th International Conference on Integrated Optics and Optical Fibre Communications (IOOC) and of the 23rd European Conference on Optical Communications (ECOC)*, Vol. 1, p. 83, Edinburgh (UK) 1997.
+- [b-VAN DEN HOVEN] VAN DEN HOVEN (G.N.), TIEMEIJER, (L.F.): *Technical Digest of Optical Amplifiers and their Applications (OAA)*, Invited Paper TuC1, Victoria (BC, Canada) 1997.
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/G/T-REC-G.663-201104-I_PDF-E/raw.md b/marked/G/T-REC-G.663-201104-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..5142fdd944689b7c3b83f335778a110cb223a398
--- /dev/null
+++ b/marked/G/T-REC-G.663-201104-I_PDF-E/raw.md
@@ -0,0 +1,1154 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**G.663**
+
+(04/2011)
+
+SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
+DIGITAL SYSTEMS AND NETWORKS
+
+Transmission media and optical systems characteristics –
+Characteristics of optical components and subsystems
+
+# --- **Application-related aspects of optical amplifier devices and subsystems**
+
+Recommendation ITU-T G.663
+
+## ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS**
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 |
+| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 |
+| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 |
+| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 |
+| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 |
+| TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS | G.600–G.699 |
+| General | G.600–G.609 |
+| Symmetric cable pairs | G.610–G.619 |
+| Land coaxial cable pairs | G.620–G.629 |
+| Submarine cables | G.630–G.639 |
+| Free space optical systems | G.640–G.649 |
+| Optical fibre cables | G.650–G.659 |
+| Characteristics of optical components and subsystems | G.660–G.679 |
+| Characteristics of optical systems | G.680–G.699 |
+| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 |
+| DIGITAL NETWORKS | G.800–G.899 |
+| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 |
+| MULTIMEDIA QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER-RELATED ASPECTS | G.1000–G.1999 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.6000–G.6999 |
+| DATA OVER TRANSPORT – GENERIC ASPECTS | G.7000–G.7999 |
+| PACKET OVER TRANSPORT ASPECTS | G.8000–G.8999 |
+| ACCESS NETWORKS | G.9000–G.9999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## Recommendation ITU-T G.663
+
+# Application-related aspects of optical amplifier devices and subsystems
+
+## Summary
+
+Recommendation ITU-T G.663 covers application-related aspects of optical amplifier (OA) devices and subsystems, primarily those used in digital systems. Applications include both single-channel and multi-channel systems used in point-to-point and point-to-multipoint configurations for use in long-distance networks and optical access networks. The purpose of this Recommendation is to identify which aspects should be considered for each application and to specify appropriate parameter values and ranges for each type of OA device. In this version of this Recommendation, information about non-linear optical effects in Appendix II is updated.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group |
+|---------|---------------------------|------------|-------------|
+| 1.0 | ITU-T G.663 | 1996-10-18 | 15 |
+| 2.0 | ITU-T G.663 | 2000-04-04 | 15 |
+| 2.1 | ITU-T G.663 (2000) Amd. 1 | 2003-01-31 | 15 |
+| 3.0 | ITU-T G.663 | 2011-04-13 | 15 |
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2011
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+###### Page
+
+| | | |
+|------|---------------------------------------------------------------------------------------------------------|----|
+| 1 | Scope ..... | 1 |
+| 2 | References..... | 1 |
+| 3 | Definitions ..... | 2 |
+| 4 | Abbreviations and acronyms ..... | 2 |
+| 5 | Applications..... | 4 |
+| 5.1 | Booster (power) amplifier ..... | 4 |
+| 5.2 | Pre-amplifier..... | 5 |
+| 5.3 | Line amplifier ..... | 5 |
+| 5.4 | Optically amplified transmitter..... | 5 |
+| 5.5 | Optically amplified receiver ..... | 6 |
+| 5.6 | Single-channel applications..... | 6 |
+| 5.7 | Multi-channel applications ..... | 6 |
+| 5.8 | Point-to-point applications ..... | 6 |
+| 5.9 | Point-to-multipoint applications..... | 6 |
+| 6 | Operation, administration and maintenance aspects..... | 7 |
+| 7 | Parameter values and ranges for OFA devices..... | 7 |
+| 7.1 | Booster (power) amplifier ..... | 7 |
+| 7.2 | Pre-amplifier..... | 7 |
+| 7.3 | Line amplifier ..... | 8 |
+| 8 | Parameter values and ranges for OFA-related aspects of OFA subsystems..... | 8 |
+| 8.1 | Optically amplified transmitter..... | 8 |
+| 8.2 | Optically amplified receiver ..... | 8 |
+| 9 | Environmental conditions..... | 8 |
+| 10 | Optical safety aspects ..... | 8 |
+| | Appendix I – Parameter values and ranges for OFA devices in single-channel point-to-point systems ..... | 9 |
+| I.1 | Booster (power) amplifier..... | 9 |
+| I.2 | Pre-amplifier ..... | 9 |
+| | Appendix II – Transmission-related aspects ..... | 11 |
+| II.1 | Purpose ..... | 11 |
+| II.2 | Factors influencing OA transmission applications..... | 11 |
+| II.3 | Fibre optical non-linearities..... | 12 |
+| II.4 | Polarization properties..... | 24 |
+| II.5 | Fibre dispersion properties ..... | 29 |
+| II.6 | Other OA-related properties ..... | 30 |
+| | Appendix III – Pre-amplifier parameters ..... | 36 |
+| | Appendix IV – OAM aspects of OAs ..... | 39 |
+
+| | Page |
+|-----------------------------|------|
+| IV.1 OA subsystems ..... | 39 |
+| IV.2 OA devices ..... | 39 |
+| Bibliography..... | 40 |
+
+## Recommendation ITU-T G.663
+
+# Application-related aspects of optical amplifier devices and subsystems
+
+# 1 Scope
+
+This Recommendation covers application-related aspects of optical amplifier (OA) devices and subsystems, primarily those used in digital systems. Optical amplifiers operating in the 1550 nm region, or 1310 nm region, or other wavelength regions are included. Generic characteristics of OA devices and subsystems are described in [ITU-T G.662]. Applications include both single-channel and multi-channel systems used in point-to-point and point-to-multipoint configurations for use in long-distance networks and optical access networks.
+
+The purpose of this Recommendation is to identify which aspects should be considered for each application and to specify common parameter values and ranges for each type of OA device (booster amplifier, pre-amplifier, and line amplifier). This Recommendation pertains to the development of new equipment including OA devices and includes guidelines to apply OA devices and OA subsystems to existing equipment. As an objective, for systems specified as transversely compatible, the degree of compatibility should not be changed by the use of OA devices.
+
+Important topics contained in this Recommendation include transmission aspects, maintenance aspects, and optical safety.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T G.652] Recommendation ITU-T G.652 (2009), *Characteristics of a single-mode optical fibre and cable*.
+- [ITU-T G.653] Recommendation ITU-T G.653 (2010), *Characteristics of a dispersion-shifted, single-mode optical fibre and cable*.
+- [ITU-T G.654] Recommendation ITU-T G.654 (2010), *Characteristics of a cut-off shifted, single-mode optical fibre and cable*.
+- [ITU-T G.655] Recommendation ITU-T G.655 (2009), *Characteristics of a non-zero dispersion-shifted single-mode optical fibre and cable*.
+- [ITU-T G.661] Recommendation ITU-T G.661 (2007), *Definition and test methods for the relevant generic parameters of optical amplifier devices and subsystems*.
+- [ITU-T G.662] Recommendation ITU-T G.662 (2005), *Generic characteristics of optical amplifier devices and subsystems*.
+- [ITU-T G.664] Recommendation ITU-T G.664 (2006), *Optical safety procedures and requirements for optical transport systems*.
+- [ITU-T G.671] Recommendation ITU-T G.671 (2009), *Transmission characteristics of optical components and subsystems*.
+
+- [ITU-T G.691] Recommendation ITU-T G.691 (2006), *Optical interfaces for single channel STM-64 and other SDH systems with optical amplifiers.*
+- [ITU-T G.692] Recommendation ITU-T G.692 (1998), *Optical interfaces for multichannel systems with optical amplifiers.*
+- [ITU-T G.783] Recommendation ITU-T G.783 (2006), *Characteristics of synchronous digital hierarchy (SDH) equipment functional blocks.*
+- [ITU-T G.955] Recommendation ITU-T G.955 (1996), *Digital line systems based on the 1544 kbit/s and the 2048 kbit/s hierarchy on optical fibre cables.*
+- [ITU-T G.957] Recommendation ITU-T G.957 (2006), *Optical interfaces for equipments and systems relating to the synchronous digital hierarchy.*
+- [IEC 60721-3-0] IEC 60721-3-0 (1997), *Classification of environmental conditions – Part 3: Classification of groups of environmental parameters and their severities. Introduction.*
+- [IEC 60721-3-1] IEC 60721-3-1 (1997), *Classification of environmental conditions – Part 3 Classification of groups of environmental parameters and their severities – Section 1: Storage.*
+- [IEC 60721-3-2] IEC 60721-3-2 (1997), *Classification of environmental conditions – Part 3: Classification of groups of environmental parameters and their severities – Section 2: Transportation.*
+- [IEC 60721-3-3] IEC 60721-3-3 (1994), *Classification of environmental conditions – Part 3: Classification of groups of environmental parameters and their severities – Section 3: Stationary use at weatherprotected locations.*
+- [IEC 60721-3-4] IEC 60721-3-4 (1995), *Classification of environmental conditions – Part 3: Classification of groups of environmental parameters and their severities – Section 4: Stationary use at non-weatherprotected locations.*
+- [IEC 60825-1] IEC 60825-1 (2007), *Safety of laser products – Part 1: Equipment classification and requirements.*
+- [IEC 60825-2] IEC 60825-2 (2010), *Safety of laser products – Part 2: Safety of optical fibre communication systems (OFCS).*
+- [IEC/TR 61282-3] IEC/TR 61282-3 (2006), *Fibre optic communication system design guides – Part 3: Calculation of link polarization mode dispersion.*
+
+# 3 Definitions
+
+For the purpose of this Recommendation, the definitions given in [ITU-T G.661] and [ITU-T G.662] apply.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|-----|--------------------------------|
+| AM | Amplitude Modulation |
+| APR | Automatic Power Reduction |
+| ASE | Amplified Spontaneous Emission |
+| ASK | Amplitude Shift Keying |
+| BA | Booster (power) Amplifier |
+
+| | |
+|-------|--------------------------------------------|
+| BER | Bit Error Ratio |
+| CD | Chromatic Dispersion |
+| CMC | Coherent Multichannel |
+| CW | Continuous Wave |
+| DA | Dispersion Accommodation |
+| DPSK | Differential Phase Shift Keying |
+| DQPSK | Differential Quadrature Phase Shift Keying |
+| EDFA | Erbium-Doped Fibre Amplifier |
+| FDM | Frequency-Division Multiplexing |
+| FWHM | Full Width at Half Maximum |
+| FWM | Four-Wave Mixing |
+| IFWM | Intra-channel Four-Wave Mixing |
+| IXPM | Intra-channel Cross-Phase Modulation |
+| LA | Line Amplifier |
+| LOS | Loss of Signal |
+| MI | Modulation Instability |
+| NPN | Non-linear Phase Noise |
+| NRZ | Non-Return to Zero |
+| OA | Optical Amplifier |
+| OAM | Operation, Administration and Maintenance |
+| OAN | Optically Amplified Network |
+| OAR | Optically Amplified Receiver |
+| OAT | Optically Amplified Transmitter |
+| OFA | Optical Fibre Amplifier |
+| OFDM | Optical Frequency Domain Multiplexing |
+| PA | Pre-Amplifier |
+| PDH | Plesiochronous Digital Hierarchy |
+| PDL | Polarization Dependent Loss |
+| PHB | Polarization Hole Burning |
+| PM | Phase Modulation |
+| PMD | Polarization Mode Dispersion |
+| PSK | Phase Shift Keying |
+| QPSK | Quadrature Phase Shift Keying |
+| RZ | Return to Zero |
+| SBS | Stimulated Brillouin Scattering |
+| SDH | Synchronous Digital Hierarchy |
+| SMF | Single-Mode Fibre |
+
+| | |
+|-----|----------------------------------|
+| SNR | Signal-to-Noise Ratio |
+| SOA | Semiconductor Optical Amplifier |
+| SPM | Self-Phase Modulation |
+| SRS | Stimulated Raman Scattering |
+| TRE | Terminal Receiver Equipment |
+| WDM | Wavelength Division Multiplexing |
+| XPM | Cross-Phase Modulation |
+
+# 5 Applications
+
+Application of OAs in optical transmission systems offers a number of advantages. Chief among these advantages is the ability to realize very significant unrepeatable system lengths as well as very long unregenerated system lengths. Deployment of OAs is likely to permit the retirement of many existing conventional regenerator sites and, in the case of new routes, to render unnecessary the construction of many new sites. OAs also enable serious consideration of new optical system architectures for application in terrestrial and submarine long haul, and access networks. Two examples of this are wavelength division multiplexing and point-to-multipoint applications, approaches heretofore generally considered prohibitively complex and expensive. OAs also offer potential advantages with respect to network upgrade options due to their independence from modulation format and bit rate.
+
+However, the application of OAs also brings to light some new and potentially serious system impairments, which result from the high power levels produced by the OAs and the long distances between regeneration. These transmission effects include optical fibre non-linearities, polarization effects and effects due to the amplification characteristics of the OA itself. Chromatic dispersion also becomes increasingly significant for the long unregenerated systems enabled by the OA. In addition to determining chromatic dispersion limitations, the dispersion characteristics of the fibre influence the severity of the impairment produced by several of the dominant non-linear effects. As a result, dispersion management has been considered in system design. In the following clauses, the OA applications are described and important considerations for each application are identified.
+
+If the characteristics are longitudinally compatible, the OA devices specified in this Recommendation can also be used to increase the distance in ITU-T G.955 plesiochronous digital hierarchy (PDH) optical line systems (which are not transversely compatible). To ensure transverse compatibility between OA devices and synchronous digital hierarchy (SDH) equipments and to satisfy the requirements of the ITU-T G.690-series Recommendations, either ITU-T G.957 equipment in accordance with clauses 6.1 and 6.2.2 of [ITU-T G.957] or a transponder(s) may be used.
+
+## 5.1 Booster (power) amplifier
+
+The booster (power) amplifier (BA) is a high saturation-power OA device to be used directly after the optical transmitter to increase its signal power level. The BA does not need stringent requirements for noise and optical filtering. The operation, administration and maintenance (OAM) functions for the BA may or may not be shared with the optical transmitter.
+
+The application of BAs (often in conjunction with pre-amplifiers) is very attractive, especially in those cases where intermediate locations with active equipment are either undesirable or inaccessible, as in submarine systems. In any case, fewer intermediate locations imply easier maintenance for the network operator. The most direct and simple means to increase the available power budget is to use either a BA directly after the regular transmitter or an optically amplified transmitter (see clause 5.4).
+
+Because of the relatively high level of input power, the undesirable amplified spontaneous emission (ASE) noise, inherently present due to the statistical process of photon generation inside the OA, is usually negligible. However, application of BAs may result in fibre non-linearity induced system penalties due to the high optical power levels produced by BAs and the long interactive lengths provided by the optical path.
+
+## 5.2 Pre-amplifier
+
+The pre-amplifier (PA) is a very low noise OA device to be used directly before an optical receiver to improve its sensitivity. The requisite low level of ASE noise may be achieved through the use of narrow-band optical filters. In this case, automatic tuning of the centre wavelength of the pre-amplifier filter to the transmitter wavelength would be advantageous, since it would permit the relaxation of requirements on both the initial transmitter wavelength tolerance and its long-term stability. As noted previously, the use of PAs (usually in conjunction with BAs) is a straightforward means to realize significant increases in available power budget. The OAM function for PAs may or may not be shared with the optical receiver. In STM-64 or higher level systems, the use of a PA-only configuration can be useful (e.g., to avoid potential problems due to fibre non-linearities).
+
+## 5.3 Line amplifier
+
+The line amplifier (LA) is a low-noise OA device to be used between passive fibre sections to increase the regeneration lengths or in correspondence with a multipoint connection to compensate for branching losses in the optical access network. As noted previously, line amplifiers might replace some or all conventional regenerators in long-haul fibre sections. It can be envisioned that more than one conventional regenerator can be replaced by a single LA, with the evident advantage of reduced equipment in transmission links. Furthermore, a situation can be envisaged where both line amplifiers for compensation of signal attenuation, and conventional regenerators for compensation of signal distortion, appear in long-distance networks.
+
+A separate communication channel must exist in systems using LAs, which would allow alarming, supervision and control of the installed remote LAs. It is preferable for such a supervisory channel not to place restrictions on the selection of pump laser wavelength or operating window. Because each LA must be able to insert its own status and alarm information, the supervisory channel must be recovered, regenerated (with new information inserted) and retransmitted at each LA.
+
+Theoretically, ultra-long (thousands of kilometres) transmission distances can be realized by periodically inserting line amplifiers in the optical path. However, in the case where many OAs are cascaded, deteriorated system performance can occur due to noise accumulation, spectral dependency of total gain, effects of polarization and chromatic dispersion and non-linear effects. Laboratory tests have shown that the overall system behaviour in the case of many cascaded line amplifiers is much more complex than that for the case of a few cascaded line amplifiers. In particular, the total gain of a chain of line amplifiers in series is generally peaked around a specific wavelength, depending on the specific amplifier configuration, giving considerable reduction of the usable OA operating wavelength range. Therefore, design of this type of system will be very much different from the situation with only a few cascaded line amplifiers.
+
+## 5.4 Optically amplified transmitter
+
+The optically amplified transmitter (OAT) is an OA subsystem in which a power amplifier is integrated with the laser transmitter, resulting in a high-power transmitter. The connection between the transmitter and the OA is proprietary and shall not be specified. The application considerations of OATs are generally the same as those for BAs (see clause 5.1).
+
+## 5.5 Optically amplified receiver
+
+The optically amplified receiver (OAR) is an OA subsystem in which a pre-amplifier is integrated with the optical receiver, resulting in a high sensitivity receiver. The connection between the receiver and the OA is proprietary and shall not be specified. The application considerations of OARs are generally the same as those for PAs (see clause 5.2).
+
+## 5.6 Single-channel applications
+
+BAs, PAs, LAs, OATs and OARs all find application in single-channel systems. In the case of single-channel transmission, noise accumulation can be reduced by using low noise OAs in combination with adequate band pass optical filtering. The dispersion limitations can be normally minimized by operating close to the fibre zero dispersion wavelength or by using suitable dispersion accommodation (DA) techniques. Furthermore, care must be taken to keep non-linear effects, like stimulated Brillouin scattering (see clause II.3.6) and self-phase modulation (see clause II.3.1), under control.
+
+The main optical path interface parameter values for point-to-point, single-channel, long-haul synchronous digital hierarchy (SDH) systems utilizing OAs are described in the ITU-T G.690-series Recommendations. The reference configurations and functional characteristics of these systems are described in [ITU-T G.783].
+
+## 5.7 Multi-channel applications
+
+OAs also find application in multi-channel systems. In addition to the transmission impairments found in single-channel systems, multi-channel systems may also suffer degraded performance due to certain non-linear effects. These include four-wave mixing (FWM), cross-phase modulation (XPM) and potentially stimulated Raman scattering (SRS). As a result, special precautions must be taken when designing multi-channel systems to avoid or alleviate these impairments. In multi-channel systems using a series of LAs to provide long unregenerated lengths, the effects of cascaded amplifiers, especially the reduction of the usable gain spectrum, must also be considered.
+
+The optical interface parameter values for point-to-point, multi-channel, long-haul SDH systems utilizing OAs are described in [ITU-T G.692]. The reference configurations and functional characteristics of these systems are described in [ITU-T G.783].
+
+## 5.8 Point-to-point applications
+
+Schemes of insertion of OA devices and subsystems in point-to-point applications are indicated in [ITU-T G.662] (see in particular, Figures 1, 2 and 3 of [ITU-T G.662]).
+
+## 5.9 Point-to-multipoint applications
+
+OAs can be used in optically amplified networks (OANs) to increase the optical power budget or to allow for higher splitting ratios in point-to-multipoint networks. Therefore, generally speaking, both power and line amplifiers will be used in these types of networks. The use of OAs in ring networks just before branching devices, in order to compensate for splitting/branching losses, is an example of a potential application.
+
+NOTE – One of the first applications of the OAs may be for the distribution of video signals. In the case of analogue video systems, additional requirements compared to the ones of the OAs for digital applications are necessary in order to maintain adequate carrier-to-noise ratio and avoid signal distortion. If AM modulated lasers are used, for instance, the OA gain must be very flat, in order to avoid frequency to intensity modulation conversions, leading to increased signal distortions. This effect can be minimized when using continuous wave (CW) operated lasers in combination with external modulators. In this way, polarization effects could be minimized too. Also, special care must be taken to keep OAs output power at acceptable levels in order to reduce non-linear effects like SBS.
+
+# **6 Operation, administration and maintenance aspects**
+
+Certain considerations on operation, administration and maintenance (OAM) aspects of OAs are given in Appendix IV.
+
+# **7 Parameter values and ranges for OFA devices**
+
+In this clause, parameter values of optical power amplifier (OFA) devices (BA, PA, LA) are provided, according to the lists given in clauses 7, 8 and 9 of [ITU-T G.662], with the aim of ensuring, as far as possible, optical transverse compatibility amongst OFA subsystems and OFA devices in point-to-point system configurations.
+
+## **7.1 Booster (power) amplifier**
+
+### **7.1.1 Point-to-point**
+
+The output parameters for power amplifiers are system specific and are specified in the relevant system Recommendations (ITU-T G.690-series). Some example, input parameter values for power amplifiers can be found in Appendix I. The output parameters for power amplifiers, as described by the interfaces in the relevant system Recommendations, are assumed to be applicable for PDH systems as well.
+
+#### **7.1.1.1 Single-channel systems**
+
+Some example input parameter values for power amplifiers can be found in Appendix I. Output parameter values are specified in the ITU-T G.690-series Recommendations.
+
+#### **7.1.1.2 Multi-channel systems**
+
+Parameter values for power amplifiers to be used in digital multi-channel systems are for further study.
+
+### **7.1.2 Point-to-multipoint**
+
+Because applications in point-to-multipoint architectures requiring power amplifiers are more likely to be analogue in nature, the associated parameter values are for further study.
+
+## **7.2 Pre-amplifier**
+
+### **7.2.1 Point-to-point**
+
+The input parameters for pre-amplifiers are system specific and are specified in the relevant system ITU-T G.690-series Recommendations. Some example output parameter values for pre-amplifiers can be found in Appendix I. The input parameters for pre-amplifiers, as described by the interfaces in the relevant system Recommendations, are assumed to be applicable for PDH systems as well.
+
+##### **7.2.1.1 Single-channel systems**
+
+Some example output parameter values for pre-amplifiers can be found in Appendix I. Input parameter values are specified in the ITU-T G.690-series Recommendations.
+
+##### **7.2.1.2 Multi-channel systems**
+
+Parameter values for pre-amplifiers to be used in digital multi-channel systems are for further study.
+
+## **7.3 Line amplifier**
+
+### **7.3.1 Point-to-point**
+
+#### **7.3.1.1 Single-channel systems**
+
+Specific parameter values for line amplifiers in point-to-point single-channel systems are specified in the ITU-T G.690-series Recommendations.
+
+#### **7.3.1.2 Multi-channel systems**
+
+Specific parameter values for line amplifiers in point-to-point multi-channel systems are for further study.
+
+### **7.3.2 Point-to-multipoint**
+
+Because applications in point-to-multipoint architectures requiring line amplifiers are more likely to be analogue in nature, the associated parameter values are for further study.
+
+# **8 Parameter values and ranges for OFA-related aspects of OFA subsystems**
+
+## **8.1 Optically amplified transmitter**
+
+Parameter values for optically amplified transmitters for single-channel systems are specified in the ITU-T G.690-series Recommendations.
+
+## **8.2 Optically amplified receiver**
+
+Parameter values for optically amplified receivers for single-channel systems are specified in the ITU-T G.690-series Recommendations.
+
+# **9 Environmental conditions**
+
+Various classes of environmental conditions are specified in [IEC 60721-3-0]. Further details can be found in [IEC 60721-3-1] for storage, [IEC 60721-3-2] for transportation, [IEC 60721-3-3] for stationary use at weatherprotected locations, and [IEC 60721-3-4] for stationary use at non-weatherprotected locations.
+
+# **10 Optical safety aspects**
+
+Under certain conditions (fibre break, open connectors), the optical output power of an OA may become accessible and may be hazardous to the human eye. Special precautions and requirements for installation and use of optical systems (including amplifiers) and a description of viewing aids are given in [IEC 60825-2].
+
+Due to the high level of optical power involved, mainly in booster amplifiers and OATs, optical safety and optical surge generation issues (i.e., protection of personnel and equipment) are of primary relevance in line systems using OA devices and subsystems.
+
+An appropriate procedure for automatic power reduction (APR), restart and safe operation of OAs is given in [ITU-T G.664].
+
+# Appendix I
+
+## Parameter values and ranges for OFA devices in single-channel point-to-point systems
+
+(This appendix does not form an integral part of this Recommendation.)
+
+In this appendix, example parameter values for OFA devices (BA and PA) are shown for single-channel point-to-point systems. These parameter values are according to the lists given in clauses 7 and 8 of [ITU-T G.662] and were developed to ensure, as far as possible, compatibility with parameter values specified in [ITU-T G.957].
+
+As indicated in clause 7, optical interface specifications for the main optical path are provided by the ITU-T G.690-series Recommendations.
+
+### I.1 Booster (power) amplifier
+
+The parameter values given in Table I.1 are examples of a minimum list of relevant input parameters (as given in [ITU-T G.662]) for power amplifiers in point-to-point single-channel systems. Only the input parameters have been included in the table, since the output parameters are system specific and are specified in the ITU-T G.690-series Recommendations.
+
+**Table I.1 – Input parameters for power amplifiers in single-channel systems**
+
+| Parameter | Unit | Value |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------------|
+| Input power range | dBm | -6/+3 |
+| Reverse ASE power level | dBm | $\leq -20$ |
+| Input reflectance | dB | $\leq -27$ |
+| Pump leakage | dBm | $\leq -15$ (Note) |
+| Maximum reflectance tolerable at input | dB | -27 |
+| Power wavelength band | nm | 1530-1565 |
+| NOTE – The measured value of -15 dBm (max) takes into account all of the contributions coming from the power distribution around the peak value down to 30 dB below the peak value itself. | | |
+
+### I.2 Pre-amplifier
+
+The parameter values given in Table I.2 are examples of a minimum list of relevant output parameters (as given in [ITU-T G.662]) for pre-amplifiers in point-to-point single-channel systems. Only the output parameters have been included in the table, since the input parameters are system specific and are specified in the ITU-T G.690-series Recommendations.
+
+**Table I.2 – Output parameters for pre-amplifier in single-channel systems**
+
+| Parameter | Unit | Value |
+|-----------------------------------------|-------------|--------------|
+| Output power range | dBm | –16/–9 |
+| Small signal gain | dB | $\geq 20$ |
+| Signal-spontaneous noise figure | dB | under study |
+| Maximum reflectance tolerable at output | dB | –27 |
+| Maximum total output power (Note) | dBm | –9 |
+| (Small-signal gain) wavelength band | nm | 1530-1565 |
+
+NOTE – This parameter is evaluated in the available signal wavelength band, when an optical filter is used inside the OFA.
+
+# Appendix II
+
+## Transmission-related aspects
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### II.1 Purpose
+
+OAs permit the consideration of new optical transmission system architectures by providing very high optical power levels and allowing much longer distances between regenerators. When combined with wavelength division multiplexing, OAs also simplify the transport of multiple channels of information by reducing the need for dedicated equipment for each channel. This makes it more economical to achieve greater amounts of bandwidth. As a result of the use of OAs, new transmission effects and limitations have emerged which must now be considered. These include optical non-linearities such as stimulated Brillouin scattering, four-wave mixing and self-phase modulation. These new effects add or combine with fibre chromatic dispersion and polarization mode dispersion. In addition, characteristics of the OA can also contribute to system impairments. Many approaches for solving transmission-related problems have been investigated. However, the technologies differ in their performance and application.
+
+In order to design economical and reliable OA-supported systems following ITU-T Recommendations on optical interface parameters, it is important that both operators and equipment vendors share a common understanding regarding OA-related problems and their remedy. To that end, this clause seeks to do the following:
+
+- Describe the transmission effects induced by optical non-linearities, polarization and chromatic dispersion properties, and other OA-related properties in OA-supported transmission systems.
+- Identify the limitations due to the mentioned effects in the various types of relevant transmission systems (e.g., digital/analogue, coherent, wavelength division multiplexing, etc.).
+- Indicate possible remedies for these impairments, together with the corresponding field of effectiveness.
+
+## II.2 Factors influencing OA transmission applications
+
+The factors influencing OA transmission applications can be divided into four general categories: optical non-linearities, polarization properties, dispersion properties, and other OA-related properties. The factors dealt with in each category are given below and their effects are described in the following clauses:
+
+- a) *Fibre optical non-linearities*
+ - 1) self-phase modulation;
+ - 2) soliton formation;
+ - 3) cross-phase modulation;
+ - 4) modulation instability;
+ - 5) four-wave mixing;
+ - 6) stimulated Brillouin scattering;
+ - 7) stimulated Raman scattering.
+- b) *Polarization properties*
+ - 1) polarization mode dispersion;
+ - 2) polarization dependent loss;
+
+- 3) polarization hole burning.
+- c) *Fibre dispersion properties*
+ - chromatic dispersion.
+- d) *Other OA-related properties*
+ - 1) noise accumulation;
+ - 2) self-filtering effect;
+ - 3) optical surge generation;
+ - 4) induced non-linearity in SOAs.
+
+## II.3 Fibre optical non-linearities
+
+Non-linear interactions between the signal and the silica fibre transmission medium begin to appear as optical signal powers are increased to achieve longer span lengths at high bit rates. Consequently, non-linear fibre behaviour has emerged as an important consideration both in high capacity systems and in long unregenerated routes. These non-linearities can be generally categorized as either scattering effects (stimulated Brillouin scattering and stimulated Raman scattering) or effects related to the fibre's intensity dependent index of refraction (self-phase modulation, cross-phase modulation, modulation instability, soliton formation and four-wave mixing). A variety of parameters influence the severity of these non-linear effects, including line code (modulation format), transmission rate, fibre dispersion characteristics, the effective area and non-linear refractive index of the fibre, the number and spacing of channels in multiple channel systems, overall unregenerated system length, as well as signal intensity and source line-width. Since the implementation of transmission systems with higher bit rates than 10 Gbit/s and alternative line codes (modulation formats) than NRZ-ASK or RZ-ASK, described in [b-ITU-T G-Sup.39], non-linear fibre effects previously not considered can have a significant influence, e.g., intra-channel cross-phase modulation (IXPM), intra-channel four-wave mixing (IFWM) and non-linear phase noise (NPN).
+
+#### II.3.1 Self-phase modulation
+
+##### II.3.1.1 Description of effects
+
+Because a fibre's refractive index depends on the optical intensity of the signal, the temporal variation of the optical intensity of the signal induces a modulation of its own phase. This effect is called self-phase modulation (SPM). The fibre refractive index may be written [b-Marcuse] as:
+
+$$n = n_0 + \frac{n_2}{A_{eff}} P$$
+
+hence:
+
+$$\frac{\partial n}{\partial t} = \frac{n_2}{A_{eff}} \frac{\partial P}{\partial t}$$
+
+where $n_2$ is the fibre non-linear refractive index in $\text{m}^2/\text{W}$ , $A_{eff}$ is the fibre effective area, and $P$ is the launched power.
+
+In single wavelength systems, self-phase modulation will gradually broaden the signal spectrum when changes in optical intensity result in changes in phase (see Figure II.3-1). Once spectral broadening is introduced by SPM, the signal experiences a greater temporal broadening as it propagates along the length of the fibre, due to the effects of chromatic dispersion, in the normal dispersion region of the fibre (i.e., below the zero-dispersion wavelength). Conversely, in the anomalous dispersion region, the chromatic dispersion and SPM can compensate each other, giving less temporal broadening. The soliton propagation is based on this phenomenon (see clause II.3.2).
+
+The interaction of a signal with the ASE noise of optical amplifiers results in amplitude to phase-noise conversion by the Gordon-Mollenauer effect. The generated NPN has also been called Gordon-Mollenauer phase noise or phase jitter [b-Gordon].
+
+
+
+The figure illustrates the spectral broadening mechanism due to self-phase modulation (SPM). At the top, a plot shows the intensity $I(t)$ versus time $t$ , featuring a pulse with a rising and falling edge. A box labeled "Kerr effect $n = n_0 + n_2 I$ " points to the rising edge. Below this, the rising edge is shown with arrows indicating $dI/dt$ and $dn/dt$ . The falling edge is shown with an arrow indicating $d\phi/dt = 2\pi f$ . Below the pulse, the resulting frequency $f(t)$ is plotted, showing a series of impulses. The text "T1523410-96" is at the bottom right.
+
+Figure II.3-1: Spectral broadening mechanism due to self-phase modulation. The diagram shows a pulse I(t) with a rising and falling edge. The rising edge is associated with dI/dt and dn/dt. The falling edge is associated with dφ/dt = 2π f. The resulting frequency f(t) is shown as a series of impulses. A box labeled 'Kerr effect n = n0 + n2I' is shown above the pulse.
+
+**Figure II.3-1 – Spectral broadening mechanism due to self-phase modulation**
+
+##### II.3.1.2 Induced transmission limitations
+
+Generally, the effects of SPM are significant only in systems with high cumulative dispersion or in very long systems. Systems operating in the normal dispersion regime which are dispersion-limited may not tolerate the additional effects due to SPM. In multiple-channel systems with very closely spaced channels, the spectral broadening induced by SPM may also create interference between adjacent channels. The effect of SPM may also induce degradation when combined with narrow-band optical filtering. Since SPM is essentially a single channel effect, it is not influenced by the greater channel counts. The distortion penalty of SPM is increased by larger launched channel powers. It is also increased by a higher channel bit rate, since signals with higher bit rates have higher rising/falling bit slopes.
+
+SPM on low-chirp intensity-modulated signals leads to pulse compression on ITU-T G.652 fibres and on ITU-T G.655 fibres with anomalous dispersion as a function of transmitter power. The pulse compression counteracts the chromatic dispersion and offers some dispersion accommodation. However, limits of maximum dispersion and related transmission length exist.
+
+For transmission over multiple fibre spans, the SPM-introduced phase shift accumulates in each successive fibre span. The maximum tolerable channel launch power into each span becomes respectively smaller as more fibre spans are applied. This phase shift accumulation has been described by the "integrated power product" behaviour [b-Faerbert].
+
+While ASK modulation formats suffer less from SPM generated non-linear phase noise (phase jitter) than PSK modulation formats i.e., (D)PSK and (D)QPSK, it can become one of the major transmission limitation factors. The more bits per symbol that are transmitted (the lower the symbol rate (baud)), the higher are the NPN impairments.
+
+##### **II.3.1.3 Minimization of induced limitations**
+
+The use of ITU-T G.653 fibre and the placement of the signal channel near the dispersion zero will reduce the impact of SPM. For systems less than approximately 1000 km, SPM may be controlled through the implementation of dispersion compensation at appropriate intervals along the length of an ITU-T G.652 fibre system. The effects of SPM may be mitigated by operating at wavelengths above the zero-dispersion wavelength of ITU-T G.655 fibre. Fibres with attributes of increased fibre effective area, or decreased non-linear refractive index, also reduce the SPM penalty. For all fibre designs, SPM effects may be reduced by decreasing the launched channel powers, though system design trends call for larger powers to allow longer span distances.
+
+#### **II.3.2 Soliton formation**
+
+##### **II.3.2.1 Description of effects**
+
+In the anomalous dispersion region of the fibre (i.e., above the zero-dispersion wavelength), the interplay between the non-linear refractive index and chromatic dispersion may give origin to particular propagation regimes, called soliton pulses, which propagate for long distances periodically reproducing their time shape and frequency spectrum. Other kinds of signals can spontaneously evolve into solitons. Although the fundamental soliton is very robust and can be used to achieve long-distance transmission, the higher order solitons undergo very complex evolution, involving pulse reshaping, spectral modifications, and also pulse breaking. These effects may be detrimental to system operation.
+
+##### **II.3.2.2 Induced transmission limitations**
+
+Effects due to soliton formation may be relevant in ITU-T G.652, ITU-T G.653 and ITU-T G.655 fibre systems. While fundamental soliton formation can be useful, other solitons generally give rise to a strong degradation of the transmitted signal. Thus, higher order soliton formation sets a limit to the maximum power that can be launched into the fibre.
+
+##### **II.3.2.3 Methods to minimize induced limitations**
+
+Soliton formation can be avoided by operating at wavelengths below the zero-dispersion wavelength of the link. However, in this regime, soliton transmission is not supported and both dispersion and non-linearity contribute to pulse broadening. Signal degradation can be minimized by proper management of the dispersion along the link.
+
+#### **II.3.3 Cross-phase modulation**
+
+##### **II.3.3.1 Description of effects**
+
+In multi-channel systems, cross-phase modulation (XPM) will gradually broaden the signal spectrum when changes in optical intensity result in changes in phase due to interactions between adjacent channels. The amount of spectral broadening introduced by XPM is related to the rate of the transmission signal, channel separation and fibre chromatic dispersion, since the dispersion-induced differential group velocities will cause the interacting pulses to separate as they propagate down the fibre. Once spectral broadening is introduced by XPM, the signal experiences a greater temporal broadening as it propagates along the length of the fibre due to the effects of chromatic dispersion. With the introduction of systems with higher bit rates than 10 Gbit/s and broader signal spectra, the cross-phase modulation within the channel becomes a dominating factor. This is denoted by the term intra-channel cross-phase modulation (IXPM). The term XPM usually describes the interaction between adjacent channels, also denoted as inter-channel cross-phase modulation.
+
+As in the case of SPM, the interaction of IXPM (XPM) with ASE noise of optical amplifiers also results in NPN or phase jitter.
+
+Besides the bit rate (symbol rate), IXPM as well as XPM impairments are modulation format dependent.
+
+##### II.3.3.2 Induced transmission limitations
+
+The systems penalty from XPM is increased by smaller channel spacings and larger channel counts (though this saturates depending on distance). As noted for SPM, the change in signal phase is related to the change in fibre refractive index, which in turn is related to the channel power. Larger average launched powers lead to larger phase shifts, which when combined with dispersion effects lead to a larger system penalty.
+
+While the XPM penalty decreases for higher channel bit rates, since lower bit rate signals experience longer bit interactions or "walk-through", IXPM penalty actually increases for higher channel bit rates, especially for ASK modulation format channels, as the higher bit rate signal pulses experience much stronger temporal broadening due to chromatic dispersion (factor of 16 between 10 Gbit/s and 40 Gbit/s) which results in bit interactions or "walk-through" of consecutive bits.
+
+While PSK modulated channels are only slightly affected by IXPM and XPM due to their constant amplitude modulation, they are impaired by non-linear phase noise.
+
+XPM induced non-linear phase noise impairments can also become significant for mixed transmission systems with ASK and PSK line coding, depending on the channel spacing, the rates of the signals and the related bit (symbol) "walk-through". The ASK modulated channels penalize the PSK modulated channels.
+
+The impairments from XPM are more significant in ITU-T G.652 fibre systems, relative to ITU-T G.653 and ITU-T G.655 fibre systems. The broadening due to XPM may result in interference between adjacent channels in multiple-channel systems.
+
+##### II.3.3.3 Minimization of induced limitations
+
+XPM can be controlled through the appropriate selection of channel spacing. Studies have shown that only adjacent channels contribute significantly to XPM-induced signal distortion in multiple-channel systems. The signal-to-noise ratio (SNR) of the centre channel of a three-channel system will approach that of a single-channel system as channel separation is increased. As a result, the effect of XPM can be rendered negligible with adequate spacing between the signal channels. Channel separations of 100 GHz were shown to be sufficient for 10 Gbit/s ASK systems to reduce XPM effects in a simulation of a system with 5 mW of power/channel [b-Koch]. Dispersion penalties due to XPM may also be controlled by the implementation of dispersion compensation at appropriate intervals along the length of the system. Fibres with attributes of increased fibre effective area, or decreased non-linear refractive index, also reduce the XPM penalty. XPM effects are also reduced by lower fibre attenuation, which ensures that XPM phase distortion between two pulses more nearly equalizes as the pulses "walk through" one another.
+
+For all fibre designs, XPM effects may be reduced by decreasing the launched channel powers, though system design trends call for larger powers to allow longer span distances.
+
+#### II.3.4 Modulation instability
+
+##### II.3.4.1 Description of effects
+
+Modulation instability (MI) breaks a CW signal or a pulse into a modulated structure. It can be induced by SPM in the anomalous dispersion regime (i.e., above the zero-dispersion wavelength), where a quasi-monochromatic signal spontaneously tends to generate two symmetric spectral sidebands, as shown in Figure II.3-2. MI can also be induced by XPM. XPM-induced MI can occur in both the anomalous and normal (i.e., below the zero-dispersion wavelength) regimes.
+
+
+
+Figure II.3-2: Power spectrum of a pulse after propagation in 1 km-long fibre. The plot shows Intensity (arb. units) on the y-axis versus Wavelength (nm) on the x-axis, ranging from 1313 to 1325 nm. A central peak is visible at approximately 1319 nm, with several side lobes on either side. The label T1523390-96 is present in the bottom right corner.
+
+**Figure II.3-2 – Power spectrum of a pulse after propagation in 1 km-long fibre
+(input pulse width: 100 ps, peak power: 7 W).
+Spectral side lobes appeared due to MI**
+
+For SPM-induced MI, frequency separation and gain of the sidebands are determined by the intensity of the wave and by the dispersion and non-linear coefficients of the fibre. The maximum conversion efficiency occurs at a frequency separation given by:
+
+$$\Omega_{\max} = \pm \left[ \frac{8\pi^2 c n_2 P_o}{\lambda^3 A_{eff} D(\lambda)} \right]^{1/2}$$
+
+where $n_2$ is the fibre non-linear refractive index, $A_{eff}$ is the fibre effective area, $P_o$ is the launched power, $D(\lambda)$ is the chromatic dispersion coefficient and $\lambda$ is the operation wavelength. Sidebands located at $\pm \Omega_{\max}$ from the carrier experience a gain per unit length: $g_{\max} = 4\pi P_o / (\lambda A_{eff})$ . Fibre loss can be taken into account by slightly modifying the equations above. Dependence of MI gain on the frequency deviation with respect to the signal is given in Figure II.3-3 in the presence of fibre loss and for various values of fibre dispersion.
+
+The MI can be viewed as a particular case of FWM where two photons of the intense incoming signal are converted into two photons at two different frequencies.
+
+
+
+Figure II.3-3: Calculated MI gain versus frequency detuning. The plot shows Parametric gain (dB) on the y-axis (0 to 15) versus Frequency detuning (GHz) on the x-axis (-400 to 400). Five curves are shown for different chromatic dispersion values: +0.05, +0.10, +0.20, +0.50, and +1.00 ps/nm·km. The gain peaks at different detuning values for each dispersion coefficient. The label T1523400-96 is present in the bottom right corner.
+
+**Figure II.3-3 – Calculated MI gain versus frequency detuning, from 30 km-long fibres
+(0.24 dB/km loss) with five different dispersion coefficient values,
+for +16 dBm CW signal launched power**
+
+##### II.3.4.2 Induced transmission limitations
+
+Modulation instability may decrease the signal-to-noise ratio (SNR) due to the generation of sidebands either spontaneously or seeded by the amplifier spontaneous emission. As the maximum degradation of the signal is expected for high values of $g_{max}$ and for $\Omega$ close to the bandwidth of the signal, MI may be critical when using very powerful boosters in dispersion-shifted fibre links with directly modulated lasers. On long-distance unrepeaters systems, MI can be observed at lower power levels and may cause excess amplification of the spontaneous emission noise of the cascaded OAs. The broadening at signal spectral tails can cause signal-carrier depletion and the tails may be attenuated by the narrow-band ASE filters or by the self-filtering effect in very long systems.
+
+##### II.3.4.3 Methods to minimize induced limitations
+
+The effect of MI can be minimized either by decreasing the power level or by operating at wavelengths below the zero-dispersion wavelength of the link. Dispersion managing may also be useful to reduce MI sidebands formation. Otherwise, the received signal should be electrically filtered in order to lower the level of the spurious amplified noise. External modulation of the lasers, giving narrower spectra, may decrease considerably the impact of MI.
+
+#### II.3.5 Four-wave mixing
+
+##### II.3.5.1 Description of effects
+
+Four-wave mixing (FWM), also called four-photon mixing, occurs when the interaction of two or three optical waves at different wavelengths generates new optical waves, called mixing products or sidebands, at other wavelengths. This interaction can occur between signals in multiple-channel systems, between OA ASE noise and a single channel (NPN), as well as between the main mode and side modes of a single channel (IFWM). In the case of two signals, the intensity modulation at their beat frequency modulates the fibre refractive index and produces a phase modulation at a difference frequency. The phase modulation creates two sidebands at frequencies given by this difference. In the case of three signals, more and stronger mixing products are produced (see Figure II.3-4) which will fall directly on adjacent signal channels when the channel spacings are equal in frequency. Two optical waves propagating along a fibre produce FWM with high efficiency if the phase matching condition is achieved between the sidebands and the initial signals.
+
+
+
+Figure II.3-4: Mixing products generated due to four-wave mixing of three signals. The diagram shows a frequency axis with three main signals at f1, f2, and f3. Between f1 and f2, there are sidebands f113, f123,213, f112, and f223. Between f2 and f3, there are sidebands f132,312, f221, and f231,321. To the right of f3, there are sidebands f332 and f331. The x-axis is labeled 'Frequency' and has a small code 'T1523370-96' at the bottom right.
+
+Figure II.3-4 – Mixing products generated due to four-wave mixing of three signals
+
+Assuming that all channels have the same modulation format, input power and equal channel spacing, the FWM efficiency, $\eta$ , of a fibre can be expressed as the ratio of the FWM power to the per channel output power from the fibre and is proportional to [b-Kaminow]:
+
+$$\eta \propto \left[ \frac{n_2 P}{A_{eff} D (\Delta \lambda)^2} \right]^2$$
+
+where $n_2$ is the fibre non-linear refractive index, $P$ is the channel input power, $A_{eff}$ is the fibre effective area, $D$ is the fibre chromatic dispersion coefficient, and $\Delta\lambda$ is the channel spacing. Note that FWM efficiency is not influenced by an increasing bit rate.
+
+As for IXPM, with the introduction of systems with bit rates higher than 10 Gbit/s and broader signal spectra, the four-wave mixing within the channel becomes a dominating factor. This is denoted by the term intra-channel four-wave mixing (IFWM). The term FWM usually describes the interaction between adjacent channels, also denoted as inter-channel four-wave mixing.
+
+##### II.3.5.2 Induced transmission limitations
+
+The generation of FWM sidebands can result in a significant depletion of the signal power. Furthermore, when the mixing products fall directly on signal channels, they cause a parametric interference which manifests itself as amplitude gain or loss in the signal pulse, depending on the phase interaction of the signal and sideband.
+
+Parametric interference causes closure of the eye pattern at the receiver output, thereby degrading bit error ratio (BER) performance. Multi-channel systems are trending towards greater channel counts, which increases the number of possible mixing products falling on signal channels.
+
+As seen by the equation in clause II.3.5.1, increased frequency spacing and chromatic dispersion reduce the efficiency of the FWM process by destroying the phase matching between the interacting waves. However, systems are trending towards decreased frequency spacings, to allow more channels to occupy the same OA passband. Furthermore, as launched channel powers increase, the FWM efficiency (and hence system penalty) also increases.
+
+Multi-channel systems deployed in the 1550 nm operating window over ITU-T G.652 fibre experience much less FWM impairment compared to systems deployed over ITU-T G.653 fibre, because ITU-T G.652 fibre has much more chromatic dispersion, as well as a larger fibre effective area. Conversely, the placement of a signal channel directly at or near the dispersion zero can result in a very significant build-up of the FWM products over a relatively short fibre length (i.e., 10 s of km).
+
+When used in the 1550 nm zero dispersion region of ITU-T G.653 fibres, sometimes referred to as C-Band, four-wave mixing can create a serious system impairment in multi-channel systems on ITU-T G.653 fibre, since the signal channels experience only a small value of chromatic dispersion. The impact of dispersion on achievable system capacity for a four-channel system over three amplifier spans is shown in Figure II.3-5. This illustrates what can happen at high power levels when conditions promote the generation of mixing products. The capacity limitation is based on a worst-case calculation of the mixing products generated by the FWM process with four 8 dBm signal channels centred around the dispersion value shown. This system develops intolerable levels of distortion due to FWM as the dispersion experienced by the signal channels approaches zero.
+
+
+
+T1523380-96
+
+Figure II.3-5: Impact of dispersion on system capacity in the presence of FWM. The graph shows 4-Channel capacity (Gbit/s) on a logarithmic y-axis (1, 10, 100) versus Chromatic dispersion (ps/nm·km) on a linear x-axis (-4 to 4). Three curves represent different channel spacings: 2.0 nm, 1.5 nm, and 1.0 nm. All curves show a sharp minimum capacity at 0 ps/nm·km dispersion, with the 1.0 nm spacing curve reaching the lowest point. Capacity increases as dispersion moves away from zero, and higher channel spacings result in higher capacities.
+
+**Figure II.3-5 – Impact of dispersion on system capacity in the presence of FWM**
+
+The non-zero dispersion shifted fibre [ITU-T G.655] has been developed to eliminate FWM effect in the C-Band. However, four-wave mixing may possibly also impair multi-channel systems even on [ITU-T G.655] fibre, depending on channel spacings of 50 GHz or less, fibre dispersion, and fibre non-linear coefficient (proportional to the non-linear refractive index divided by the effective area).
+
+In single-channel systems, the FWM interaction can occur between OA ASE noise and the transmission channel, as well as between the main mode and the side modes of the optical transmitter. Phase noise is added to the signal carrier due to the accumulated ASE via the non-linear index of refraction effect, thus broadening the signal spectral tails.
+
+##### II.3.5.3 Minimization of induced limitations
+
+As previously noted, chromatic dispersion, such as that in ITU-T G.652 and ITU-T G.655 fibres, may be used to suppress the generation of the FWM sidebands. Fibres with attributes of an increased fibre effective area, or a decreased non-linear refractive index, also reduce the FWM efficiency. Uneven channel spacing may also be incorporated to mitigate the severity of the FWM impairment. Reduction of the input power levels in ITU-T G.653 fibre systems could permit multiple channel operation, but might compromise the economical advantages of optical amplification.
+
+In order to adequately suppress the generation of mixing products, use of a fibre (covered by either existing or new Recommendations under study) with a minimum permitted (i.e., non-zero) dispersion within the region of the OA amplification band has been proposed. Alternating spans of such non-zero dispersion fibre with opposite dispersion characteristics has also been considered as a potential option, since the resultant cable would maintain a net chromatic dispersion of approximately zero. However, this alternative may present difficulties in the areas of installation, operations and maintenance by introducing a second fibre type into the outside plant environment. Similar approaches using long spans of fibre with small finite dispersion and short lengths of opposite and higher dispersion fibre (to provide compensation) have also been demonstrated. In
+
+particular, in links with periodical amplification, a short piece of compensating fibre can be located inside the box in which the optical amplifier is located.
+
+Uneven channel spacing and larger channel spacing have been proposed as means to mitigate the effects of non-linearities and allow deployment of dense WDM systems on ITU-T G.653 fibre. Uneven channel spacing ensures that mixing products generated by three or more channels do not fall directly on other channel wavelengths. However, the transfer of power from the signals into the mixing products (i.e., signal depletion) remains unaffected by making the channel spacing uneven and may still cause significant eye closure. Increased channel spacing also reduces the effects of four-wave mixing. Use of these mitigation techniques may be constrained by the effects of gain narrowing due to the concatenation of optical amplifiers, which reduces the width of the usable amplification spectrum. Uneven channel spacing and increased channel spacing unfortunately also require more of the OA passband.
+
+WDM transmission using longer wavelengths (L-band) in addition to the 1550 nm band is proposed. Transmission using the long wavelength band (L-band) is generally useful on all types of fibre since it allows the total number of wavelengths to be increased. L-band transmission on ITU-T G.652 and ITU-T G.654 fibre may require dispersion compensation due to large dispersion values. With ITU-T G.653 fibres, L-band transmission enables simple wavelength design because minimal FWM effect is observed in the L-band. Dispersion of the L-band in ITU-T G.653 fibre may not require dispersion compensation, depending on the transmission bit rate.
+
+NOTE – The definition of the L-band can be found in [b-ITU-T G-Sup.39].
+
+#### II.3.6 Stimulated Brillouin scattering
+
+##### II.3.6.1 Description of effects
+
+In an intensity-modulated system using a source with a narrow line-width, significant optical power is transferred from the forward-propagating signal to a backward-propagating signal when the stimulated Brillouin scattering (SBS) threshold is exceeded. In the SBS, the forward-propagating light is scattered from acoustic phonons. However, only the backward-propagating scattered light is guided by the single-mode fibre. The scattered light is downshifted or Brillouin-shifted by approximately 11 GHz at 1550 nm.
+
+Of the non-linear effects described here, the SBS has the lowest threshold power. While studies have shown that the SBS threshold can vary between fibre types and even among individual fibres, it is typically in the order of 5 to 10 mW for externally modulated, narrow line-width sources, but may be 20 to 30 mW for directly modulated lasers. The SBS threshold for a system deployed on ITU-T G.653 fibre is slightly lower than that for a system using ITU-T G.652 fibre, due to the smaller effective area of ITU-T G.653 fibre. This is generally true for all of the non-linear effects. The SBS threshold is sensitive to the source line-width and power level. It is independent of the number of channels.
+
+##### II.3.6.2 Induced transmission limitations
+
+SBS effectively limits the amount of light that can be transmitted through a fibre path. Figure II.3-6 [b-Koch] and [b-Mao] shows this effect for a narrow-band source, where all of the signal power falls within the Brillouin bandwidth. The transmitted power becomes saturated and the backscattered power rapidly increases. The input power level to the fibre at which this rapid increase occurs is defined as the SBS threshold. In the general case, the SBS threshold is expressed as:
+
+$$P_{th} = 21 \frac{KA_{eff}}{gL_{eff}} \cdot \frac{\Delta\nu_p + \Delta\nu_B}{\Delta\nu_B}$$
+
+where $g$ denotes the Brillouin gain coefficient ( $\sim 4 \times 10^{-9}$ cm/W), and $A_{eff}$ is the fibre effective area. $K$ is a constant determined by the degree of freedom of the polarization state (in ITU-T G.652 fibres, $K = 2$ ). $\Delta\nu_B$ and $\Delta\nu_p$ represent the Brillouin bandwidth and a line-width of a pump light, respectively. $L_{eff}$ denotes the effective length defined as:
+
+$$L_{eff} = \frac{1 - \exp(-\alpha L)}{\alpha}$$
+
+where $\alpha$ is the fibre attenuation coefficient and $L$ is the fibre length.
+
+The SBS threshold, $P_{th}$ , depends on the line-width of the pump light, $\Delta\nu_p$ . When the line-width of the pump light is small compared to the Brillouin bandwidth, the SBS threshold power can be estimated using the following relation:
+
+$$P_{th} = 21 \frac{KA_{eff}}{gL_{eff}}$$
+
+
+
+Figure II.3-6: Stimulated Brillouin scattering effect for narrow-band source. The graph shows two curves plotted against Injected power (dBm) on the x-axis, ranging from -5 to 25. The left y-axis represents Scattered power (dBm) from -35 to 25. The right y-axis represents Output power (dBm) from -15 to 15. The scattered power curve starts at -35 dBm at -5 dBm injected power and increases linearly until it reaches a threshold of approximately 5 dBm at 10 dBm injected power, after which it levels off. The output power curve starts at -15 dBm at -5 dBm injected power and increases until it reaches a threshold of approximately 10 dBm at 10 dBm injected power, after which it also levels off. Arrows indicate the correspondence between the curves and their respective y-axes.
+
+**Figure II.3-6 – Stimulated Brillouin scattering effect for narrow-band source**
+
+##### II.3.6.3 Minimization of induced limitations
+
+Stimulated Brillouin scattering impairments will not arise in systems where the source line-width significantly exceeds the Brillouin bandwidth or where the signal power is below the threshold power (calculated from expressions in clause II.3.6.2).
+
+NOTE – Further information concerning SBS can be found in clause II.5 of [b-ITU-T G.650.2].
+
+#### II.3.7 Stimulated Raman scattering
+
+##### II.3.7.1 Description of effects
+
+Stimulated Raman scattering is a broadband effect which involves the interaction of light and the vibrational modes of silica molecules. SRS causes a signal wavelength to behave as a Raman pump for longer wavelengths, either other signal channels or spontaneously scattered Raman-shifted light. In any case, the shorter wavelength signal is attenuated by this process, which amplifies the longer wavelength signal.
+
+##### II.3.7.2 Induced transmission limitations
+
+Stimulated Raman scattering (SRS) can occur in both single- and multiple-channel systems. Signal powers in the order of 1W or more are needed to experience impairment from this phenomenon with only a single channel without line amplifiers. However, shorter wavelength signals in multiple-channel systems with channels spanning a wide wavelength range can suffer degraded signal-to-noise performance when a portion of their power is transferred to longer wavelength channels through the SRS. This results in total system capacity limitations based on the total number of channels, channel spacing, average input power and overall system length. In particular, the threshold for the observation of a 1 dB penalty in a multi-channel system due to Raman gain in dispersion-unshifted fibre can be estimated to be [b-Koch] and [b-Chraplyvy]:
+
+$$P_{tot} \cdot \Delta\lambda \cdot L_{eff} < 40 \text{ mW} \cdot \text{nm} \cdot \text{Mm}$$
+
+where $P_{tot}$ is the combined power of all of the channels, $\Delta\lambda$ is the optical spectrum over which the channels are distributed and $L_{eff}$ is the effective length (in units of $10^6$ metres (Mm)). The SRS threshold for a system deployed on ITU-T G.653 fibre is slightly lower than that for a system using ITU-T G.652 fibre, due to the smaller effective area of ITU-T G.653 fibre. The SRS does not practically degrade single-channel systems; conversely, it may limit the capability of WDM systems.
+
+##### II.3.7.3 Minimization of induced limitations
+
+In single-channel systems, filters can be used to remove the unwanted spectrum. However, no practical techniques to eliminate the effects of the SRS in multiple-channel systems have been reported. The effects of the SRS may also be mitigated by reducing the input optical power. However, the SRS does not appear to present a practical limitation to the deployment of the currently contemplated WDM systems.
+
+#### II.3.8 Fibre non-linearity summary
+
+A summary of the non-linear effects described in the previous clauses is given in Table II.1.
+
+**Table II.1 – Non-linear optical effects in optical fibres**
+
+| Non-linear optical effect | Cause | Characteristics | Critical light power in SMF | Impact |
+|--------------------------------------------------------------|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Self-phase modulation (SPM) and cross-phase modulation (XPM) | Intensity-dependent refractive index | – Phase shift • self-induced (SPM) • adjacent channel (XPM) • spectral frequency broadening • accumulation with each fibre span – Non-linear phase noise • Gordon-Mollenauer effect | $P_c > \sim 10 \text{ mW}$ (for single span) | – Spectral broadening increases effect of dispersion – Power/dispersion limited high bit rate transmission – Initial pulse compression (in positive dispersion regime) – Accelerated pulse broadening (in negative dispersion regime) – Pulse propagation (solitons) – Limitations in PSK systems by AM/PM conversion |
+
+**Table II.1 – Non-linear optical effects in optical fibres**
+
+| Non-linear optical effect | Cause | Characteristics | Critical light power in SMF | Impact |
+|----------------------------------------------|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Four-wave mixing (FWM) or four-photon mixing | Intensity-dependent refractive index | – Mixing products generated f_{ijk} = f_i + f_j - f_k (i, j≠k) | $P_c > \sim 10$ mW (for ITU-T G.653 fibres) – depends on specific parameters, e.g., channel spacing and closeness to \lambda_0 | – Optical crosstalk in WDM systems – Signal power depletion |
+| Stimulated Brillouin scattering (SBS) | Interaction: photon-acoustic phonons | – Brillouin lines in backward direction f - \Delta f \Delta f = \sim 13 GHz (1310 nm) \Delta f = \sim 11 GHz (1550 nm) | $P_c > \sim 5$ mW (for narrow line-width optical source) – P_c increases with signal line-width | – Signal instability – Optical loss in fibre – Optical crosstalk in bidirectional multi-channel systems |
+| Stimulated Raman scattering (SRS) | Interaction of photon-optical phonons | – Raman lines f-n \Delta f (Stokes) \Delta f = \sim 12 THz \Delta \lambda = \sim 70 nm (1310 nm) \Delta \lambda = \sim 102 nm (1550 nm) | $P_c > \sim 1$ W (for single channel) $P_c > \sim 1$ mW for Raman amplification in a WDM system with critical channel spacing, $\Delta \lambda$ | – Optical loss in fibre – Optical crosstalk in a WDM system – Signal power depletion |
+
+A second summary is given in Table II.2, comparing long-haul system trends to their effects on non-linear systems penalties.
+
+**Table II.2 – Long-haul system trends vs non-linear penalties**
+
+| Long-haul system trends | SPM penalty | (I)XPM penalty | | (I)FWM penalty | | NPN penalty (Note) | SBS penalty | SRS penalty |
+|---------------------------------------------|-------------|----------------|----|----------------|----|--------------------|-------------|-------------|
+| | | XPM | I- | FWM | I- | | | |
+| a) Decreased channel spacing | – | ↑ | – | ↑ | – | – | ffs | ffs |
+| b) Increased channel count | – | ↑ | – | ↑ | – | – | ffs | ↑ |
+| c) Increased channel power | ↑ | ↑ | ↑ | ↑ | ↑ | ↑ | ↑ | ↑ |
+| d) Increased number of spans | ↑ | ↑ | ↑ | ↑ | ↑ | ↑ | ↑ | ↑ |
+| e) Increased channel bit rate (symbol rate) | ↑ | ↓ | ↑ | – | ↑ | – | ↓ | ffs |
+| f) PSK versus OOK modulation formats | ↓ | ↓ | ↓ | ↓ | ↓ | ↑ | | |
+
+↑ Penalty increases
+↓ Penalty decreases
+– Penalty is not significantly affected
+ffs Penalty is for further study
+NOTE – NPN can be generated by SMP, (I)XPM or (I)FWM.
+
+## II.4 Polarization properties
+
+#### II.4.1 Polarization mode dispersion
+
+##### II.4.1.1 Description of effects
+
+It is well known that the fundamental mode of a circularly symmetric dielectric waveguide is doubly degenerate. In a real optical fibre, this degeneracy is split by birefringence. The birefringence may be introduced deliberately, as in a polarization-maintaining fibre, for example, or it may be an unwanted by-product of fibre manufacture or cable manufacture. In this case, the birefringence is introduced in a random way by, for example, geometrical or stress-induced perturbations.
+
+The propagation constants, $\beta_i(\omega)$ , of the two orthogonal modes can be expanded in a Taylor series around the centre frequency, $\omega_0$ :
+
+$$\beta_i(\omega_0) = \beta_i(\omega_0) + \left. \frac{\partial \beta_i}{\partial \omega} \right|_{\omega=\omega_0} (\omega - \omega_0) + \frac{1}{2} \left. \frac{\partial^2 \beta_i}{\partial \omega^2} \right|_{\omega=\omega_0} (\omega - \omega_0)^2 + \dots$$
+
+where the $\beta_i(\omega_0)$ is the phase velocity $v_p$ , $\frac{\partial \beta_i}{\partial \omega}$ is related to the group velocity $v_g$ , and $\frac{\partial^2 \beta_i}{\partial \omega^2}$ is related to the dispersion of the group velocity (or chromatic dispersion, $D$ ), etc.
+
+With the development of dispersion-shifted fibres and the deployment of systems operating near the dispersion-zero wavelength, the contribution to the dispersion from the second order term, or chromatic dispersion, reduces and the first order term can now become significant. For the case of birefringent fibres, this first order term leads to a group delay called polarization dispersion. This polarization dispersion introduces a differential group delay between orthogonal states of polarization. Although the effect of polarization mode dispersion (PMD) is to change randomly the polarization state of a pulse propagating in a fibre, it is possible to define a pair of orthogonal states or "principal states" at the input whose output states are orthogonal and show no dependence on
+
+wavelength to the first order. (In some situations, however, this approximation falls apart and the principal states can show a wavelength dependence, leading to a further system degradation through a coupling to chromatic dispersion.)
+
+As alluded to in the first paragraph above, the birefringence introduced to the fibre is caused by local random and asymmetric mechanisms such as stress, bending and twisting. These random birefringence mechanisms redefine the local birefringence axes along the length of the fibre, thus causing random coupling between the polarization modes along the length of the fibre. The cabling process also introduces a certain amount of random birefringence and random mode coupling. The fibre length between such changes is usually referred to as the coupling length, which for a fibre is usually quoted as the ensemble average of all of the local coupling lengths. Furthermore, changes in local environmental conditions, such as temperature for example, cause fluctuations in the local birefringence axes, thus causing random polarization coupling. As a result of the randomly changing polarization coupling, the magnitude of the differential group delay (DGD) becomes a statistically varying function. It can be shown that distribution of the differential group delays is described by a Maxwellian distribution function, defined by:
+
+$$P(\Delta\tau) = \frac{32\Delta\tau^2}{\pi^2\langle\Delta\tau\rangle^3} \exp\left[-\frac{4\Delta\tau^2}{\pi\langle\Delta\tau\rangle^2}\right]$$
+
+where $\Delta\tau$ is the differential group delay between the two principal states, and $\langle\Delta\tau\rangle$ is the mean differential group delay (usually referred to as the PMD value). As a consequence of the statistical nature of polarization mode dispersion, the magnitude of $\langle\Delta\tau\rangle$ increases with the square root of the fibre or cable length, for lengths much longer than the coupling length. Polarization mode dispersion is usually quoted in units of ps or ps/√km. The unit of ps is usually reserved for single optical elements which have a fixed dispersion (e.g., a coupler or isolator) or short fibre sections which do not exhibit mode coupling.
+
+##### II.4.1.2 Induced transmission limitations
+
+In a digital transmission system, the principal effect of polarization mode dispersion is to cause intersymbol interference. As an approximate rule of thumb, a 1 dB penalty occurs when the total instantaneous differential group delay equals 0.3 T, and both principal states of polarization are excited equally (gamma = 0.5), where T is the bit period. This is a commonly used value for the maximum tolerable system power penalty. The related instantaneous DGD can also be considered, in the same way, as the maximum tolerable system value: $\text{DGD}_{\max} \leq 0.3 T$ . The relationship between $\text{DGD}_{\max}$ and PMD value is to be determined on the base of the Maxwellian probability distribution, choosing a proper adjustment factor that is related to the desired maximum outage probability. For example, a value of the adjustment factor equal to 3, i.e., $\text{DGD}_{\max} = 3 \times \text{PMD value}$ , corresponds to an outage probability of approximately $4 \times 10^{-5}$ , see [ITU-T G.691]. Higher bit rate systems have shorter bit periods, so they tolerate less differential group delay. Current studies, e.g., [IEC/TR 61282-3], indicate that optical fibres and cables will be specified according to either the $\text{DGD}_{\max}$ defined above or to the mean level of differential group delay (PMD value). Using the example value of the adjustment factor of 3, the system design rule for PMD impairments becomes: $\text{PMD value} \leq 0.1 T$ .
+
+In optical transmission systems operating at 10 Gbit/s, a statistical specification of 0.5 ps/√km has been proposed for concatenated links of optical fibre cable. From the Maxwell statistics, the probability that the 1 dB penalty at 10 Gbit/s is exceeded for a 400 km span is less than $4 \times 10^{-5}$ (see [ITU-T G.691]). Here, the contribution of other components to PMD is not taken into account. The PMD impairment can therefore be seen as a system power penalty combined with a probability that this penalty will be exceeded.
+
+For systems operating at 40 Gbit/s, the mean differential group delay equal to one-tenth of a bit period, $0.1 T$ , corresponds to 2.5 ps. As a general assumption, part of this tolerated value could be allocated to the cable and part to optical repeaters, depending on the link characteristics (PMD quality of used fibres and subsystems). The total PMD of a link encompassing optical fibres and optical subsystems is the quadratic sum (square root of the sum of the squares) of the fibre and subsystems PMD:
+
+$$PMD_{TOT} = \left[ PMD_F^2 + \sum_i PMD_{Ci}^2 \right]^{1/2}$$
+
+where:
+
+$PMD_{TOT}$ : TOTAL PMD link (ps)
+
+$PMD_F$ : PMD of concatenated optical fibre cables (ps)
+
+$PMD_{Ci}$ : PMD value of the $i$ th subsystem (ps)
+
+For example, considering a PMD value of the concatenated optical fibre cables of the link of 0.1 ps/sqrt(km), (that can be considered advisable at 40 Gbit/s), 2.0 ps is the PMD cable contribution on 400 km long links. According to the previous formula, this still leaves a 1.5 ps PMD margin for optical subsystems. Assuming the use of 4 optical subsystems with a PMD value of 0.6 ps, the total PMD will be below the 2.5 ps limit stated before for 40 Gbit/s systems.
+
+$$PMD_{TOT} = \sqrt{(0.1 \cdot \sqrt{400})^2 + 4 \cdot (0.6)^2} = 2.33 \text{ ps} < 2.5 \text{ ps}$$
+
+The second or higher order PMD may give a non-negligible effect on the total PMD penalty. Further study is required.
+
+Furthermore, in long-haul amplifier systems employing polarization scramblers (devices which deliberately modulate the polarization state of a signal laser so that it appears to be unpolarized), the polarization mode dispersion causes an increase in the degree of polarization of the signal. This degrades the system performance through interactions with polarization-dependent loss and polarization hole burning (see the following clauses). In an analogue system, the interaction of polarization mode dispersion with laser chirp leads to a second order distortion proportional to the modulation frequency. A further second order penalty, independent of the modulation frequency, is incurred when additional polarization-dependent loss is present in the system.
+
+It has also been shown, and mentioned briefly above, that a second order effect can cause a coupling between polarization mode dispersion and chromatic dispersion. This is caused by the wavelength dependence of the differential group delay, and more importantly, the wavelength dependence of the principal states of polarization. This leads to a statistical contribution to the chromatic dispersion. This is an area which is not well understood and is under study. The use of chromatic dispersion compensating devices also has an unclear impact on the PMD penalty. The impact of higher launched channel power on non-linear PMD also requires further study.
+
+For amplified 1550 nm systems, PMD is likely to be more of an issue for vintage fibres operating on 10 Gbit/s or higher TDM systems than for newer ITU-T G.652, ITU-T G.653 or ITU-T G.655 fibres.
+
+##### II.4.1.3 Methods to minimize induced limitations
+
+Given that the problem arises from birefringence, much of the effort in reducing the effects of the polarization mode dispersion have been concerned with minimizing the birefringence introduced by fibre or cable manufacture. Care is taken to optimize fibre production to ensure geometrical and optical circular symmetry, and/or to induce polarization mode coupling. Optical cables are manufactured using materials and processes which minimize the residual strain in the cable structure across the fibre. Elaborate cable structures can also be used which introduce a circular
+
+component to the induced birefringence. By careful design, such an effect can counteract linear birefringence to produce a cable with a resultant zero polarization mode dispersion. Typically, the mean polarization mode dispersion of fibres and cables lie in the range:
+
+$$0 < \langle \Delta\tau \rangle < 0.5 \quad ps / \sqrt{km}$$
+
+Furthermore, improved fibre designs show smaller PMD values, e.g., 0.1 ps/sqrt(km), as mentioned earlier.
+
+Additionally, another method to reduce the effect of PMD is dynamic PMD compensation. A PMD compensator can accept at its input a signal affected by PMD and would provide at its output a signal with reduced distortion. It generally consists of a PMD equalizer, a PMD monitor and a feed-back controller. The equalizer and the monitor can be implemented in the optical or in the electrical domain. There is also the possibility for mixed or hybrid solutions. The feed-back controller takes decisions on the basis of the monitored information, according to a predefined algorithm and drives the equalizer according to the decisions. Dynamic PMD compensation is currently performed on a per-wavelength channel basis.
+
+#### **II.4.2 Polarization-dependent loss**
+
+##### **II.4.2.1 Description of effects**
+
+Polarization-dependent loss (PDL) arises from the dichroism of the passive optical components such as isolators, couplers, etc., in the signal path. When the signal passes through the dichroic element, the component of its electric field parallel to the lossy axis is attenuated. As in the case of polarization mode dispersion, the axes which define the polarization-dependent loss are oriented randomly with respect to each other.
+
+##### **II.4.2.2 Induced transmission limitations**
+
+To examine the effect of polarization-dependent loss, let us examine a possible system configuration. In amplified systems, one mode of amplifier control is to operate at constant signal power. Both the signal and noise are affected by polarization-dependent losses. However, because the noise is unpolarized, the signal and noise are affected differently. The noise can be resolved into a component parallel to the signal and a component orthogonal to the signal. It can be shown that the combined effect of PDL and optical amplification is always to increase the component of the noise orthogonal to the signal. Furthermore, the magnitude of the orthogonal noise component changes with time as the signal polarization changes due to polarization mode dispersion. This leads to a reduction in the signal-to-noise ratio and the Q-value at the receiver. Furthermore, the fluctuations time lead to fading of the signal-to-noise and Q-value at the receiver, both of which lead to an impairment in system performance.
+
+In analogue systems, the polarization-dependent loss can interact with laser chirp and polarization mode dispersion to reduce the system performance in terms of composite second order distortion. As expected, this impairment is time varying and leads to fluctuations in the system composite second order with time.
+
+##### **II.4.2.3 Methods to minimize induced limitations**
+
+As for the case of polarization mode dispersion, it is important that the polarization-dependent loss of the optical components be minimized. However, it should be noted that the impact of polarization-dependent loss on the system performance increases as the number of amplifiers increases. In long-haul submarine systems, for example, the requirements are extremely tight, because the number of amplifiers can be several hundred. In a short-haul terrestrial system, where only a few amplifiers are concatenated, the impact of polarization-dependent loss on system performance is still under study.
+
+Polarization modulation, or scrambling, has been shown to improve system performance by reducing the fluctuations and improving the average Q. This technique is described more fully in clause II.4.3.3.
+
+#### **II.4.3 Polarization hole burning**
+
+##### **II.4.3.1 Description of effects**
+
+Polarization hole burning (PHB) results from an anisotropic saturation created by a polarized saturating signal launched into the erbium fibre. This results in a selective depopulation of excited states aligned with the polarized field. Consequently, the available gain in the orthogonal direction is higher. Although the erbium ions are distributed randomly within the glass matrix, on a microscopic level the dipole associated with the erbium ion is anisotropic. The polarization hole burning effect is maximum where the linearly polarized saturating signal is aligned with the major axis of the dipole and is reduced where the polarization state of the saturating signal is elliptical or circular. Both the signal laser and the pump laser contribute to the total effect, the total differential gain being the vector sum of the two contributions. The degree of hole burning is proportional to the degree of the polarization of the saturating signal. For an unpolarized saturating signal, there is no hole burning. In principle, this is similar to the case of a circularly polarized signal.
+
+##### **II.4.3.2 Induced transmission limitations**
+
+The polarization hole burning impacts the system performance by causing the noise build-up along the amplifier chain to be greater than that which would be predicted from simple linear theory. That is, the signal-to-noise is reduced by polarization hole burning and, as for the cases of polarization mode dispersion and polarization-dependent loss, the measured Q fluctuates in time. As there are two contributions to polarization hole burning, there are two ways in which the system performance is affected. The total effect is proportional to the gain saturation, increasing with an increased degree of saturation.
+
+First of all, let us consider the effect of the polarized pump laser. It can be considered for the purposes of this discussion that the pump polarization is fixed and invariant. The pump causes a differential gain in the direction orthogonal to its polarization axis. Noise aligned orthogonally to the pump experiences a higher gain than noise aligned with the pump. However, the polarization axes of the pump lasers in each amplifier along a chain are uncorrelated with each other. Therefore, the cumulative effect is similar to a random walk, and the pump-induced polarization hole burning can be considered as a contribution to the polarization-dependent loss of the amplifier. Thus, averaged over a number of amplifiers, the noise build-up should be linear as expected from a simple theory.
+
+The signal laser induced polarization hole burning is slightly different. As the signal laser propagates along the system, the noise polarized along parallel to the signal laser will see the same gain as the signal. However, noise polarized orthogonal to the signal laser will always experience a higher gain because it will always be orthogonal to the signal polarization axis. Therefore, the total noise will increase in a non-linear way along the chain of amplifiers.
+
+The total differential gain due to polarization hole burning varies as the polarization state of the signal changes (due to polarization mode dispersion) along the amplifier chain. It varies because the signal hole burning effect is correlated with the pump effect. As the relative polarization states of the signal and pump lasers change, the magnitude of the differential gain changes. Therefore, although the total noise increases non-linearly along the chain, it does so in such a way that the total noise fluctuates in time. Consequently, as explained above, the signal-to-noise is reduced and fluctuates in time. The system Q is, therefore, reduced and fluctuates in time.
+
+##### **II.4.3.3 Methods to reduce induced transmission limitations**
+
+There exist several ways to reduce the effect of polarization hole burning. Operating the amplifiers in the small signal regime is one potential solution, but this is not always possible and, in many cases, not desirable. In practice, the simplest solution is to use a depolarized signal. A depolarized signal can be created in many ways, but is most commonly generated by polarization scrambling. Using a phase modulator, the polarization state is varied between two orthogonal states in time. The signal then appears to be depolarized.
+
+It has been shown that it is optimal to impose the polarization modulation at twice the bit rate. This is because polarization-dependent loss in the amplifier converts the polarization modulation to amplitude modulation. By polarization modulating at twice the bit rate, the amplitude fluctuations are at a rate higher than the detector bandwidth and so are not seen by the receiver. Using such techniques, the performance of very long-haul systems have been improved to the point where the predicted performance is met with a high degree of confidence. Polarization modulation is now a standard implementation in transoceanic amplified systems.
+
+However, in long amplified systems, polarization mode dispersion causes a re-polarization of the signal, thus allowing polarization hole burning to again degrade the system performance. Such an effect illustrates the complex nature of the interaction of the polarization phenomena in amplified links.
+
+### **II.5 Fibre dispersion properties**
+
+#### **II.5.1 Chromatic dispersion**
+
+##### **II.5.1.1 Description of effects**
+
+Chromatic dispersion is predominantly a transmission capacity limitation which results from the transmission source spectral characteristics and the chromatic dispersion of the optical fibre. Optical amplifiers inherently do not significantly change the chromatic dispersion, unless a form of dispersion compensation function is incorporated into an amplified subsystem.
+
+Optical amplifiers produce light around the signal transmission wavelength, known as amplified spontaneous emission (ASE). Usually, the ASE component is not modulated and so it is not detected synchronously with the signal. In many optical amplifier implementations, the ASE is blocked by a filter within the amplifier, signal path or receiver. Unless the ASE is modulated along with the transmission signal, its presence results in optical noise as described more fully in clause II.6.1. The broader spectrum of the ASE does not alter the interaction of the signal spectral characteristics with the optical fibre chromatic dispersion.
+
+Generally, optical amplifiers do not significantly alter the overall chromatic dispersion by their addition to a system. There is a small amount of chromatic dispersion added by the rare-Earth doped fibre used as the active gain medium in an OFA, but those fibre lengths are in the order of tens of metres to a few hundred metres. The chromatic dispersion of the rare-Earth doped fibres is not significantly different from that found in ITU-T G.652, ITU-T G.653 and ITU-T G.655 fibres. For systems which are tens to hundreds of kilometres in length, this dispersion contribution is considered negligible.
+
+##### **II.5.1.2 Induced transmission limitations**
+
+Generally, optical amplifiers do not alter transmission limitations due to chromatic dispersion. Certain non-linear effects may interact with the fibre chromatic dispersion due to the high output amplified power levels. These effects and methods to minimize induced limitations are described more fully in clause II.3.
+
+The presence of an optical amplifier does not affect the chromatic dispersion in a system. However, OAs do enable consideration of long unregenerated systems, where system penalties due to chromatic dispersion may become significant. For example, a zero chirp, single frequency source has an optical power penalty at 1550 nm of up to approximately 1 dB when the following equation is met [b-Kaminow2]:
+
+$$B^2 D L \leq 104'000$$
+
+Where $B$ is bit rate in Gbit/s, $D$ is the chromatic dispersion coefficient in ps/nm-km, and $L$ is the total route length in km.
+
+A relevant detailed discussion can be found in clause 9.2.1.1. of [b-ITU-T G-Sup.39]. The above equation applies to linear systems, but may be incorrect when non-linearities are taken into consideration [b-Chbat]. This is an area requiring further study. Additionally, the interaction of non-linear effects with chromatic dispersion can produce interactions that cannot be undone by dispersion compensation. This has implications on the ideal amount of dispersion that a fibre should have, and on its uniformity with wavelength.
+
+##### II.5.1.3 Minimization of induced limitations
+
+The presence of an optical amplifier does not affect the chromatic dispersion in a system, and thus no specific methods to minimize these effects are required. In some optically amplified subsystems, a passive dispersion compensation function may be combined with the optical amplifier to result in an amplified subsystem which adds a finite amount of chromatic dispersion to the system, with a sign opposite that of the system fibre. This results in lower overall system chromatic dispersion. This function may be co-located with an OA in order to overcome the losses associated with the passive dispersion compensation function. The changes to the chromatic dispersion in the transmission system are due to the presence of the passive dispersion compensation function (more fully described in the ITU-T G.690-series Recommendations), and not the optical amplifier.
+
+NOTE – Additional techniques to minimize the limitations induced by chromatic dispersion are described in the ITU-T G.690-series Recommendations.
+
+## II.6 Other OA-related properties
+
+#### II.6.1 Noise accumulation
+
+##### II.6.1.1 Description of effects
+
+In transmission systems with cascaded OAs, the ASE noise generated at an OA repeats a cycle of attenuation and amplification in the same way as the signal light. Since the incoming ASE noise is amplified at each OA and added to the ASE noise generated at that OA, the total ASE noise power increases nearly proportionally with the number of OAs, and the signal power accordingly decreases. The noise power can exceed the signal power.
+
+The ASE noise spectral profile also evolves along the system length. When ASE noise from the first OA is input to a second OA, the gain profile of the second OA changes due to the ASE noise power via the gain saturation effect. Similarly, the effective gain profile of the third OA is then modified by the output-power spectrum of the second OA. Such an effect is transmitted all the way down to the last OA. The ASE noise accumulates even if narrow-band filters are used at each OA because the noise exists over frequency ranges that include the signal frequency.
+
+##### II.6.1.2 Induced transmission limitations
+
+ASE noise accumulation affects the SNR of the system because the degradation in the received-signal SNR is due predominantly to ASE-related beat noise. Such beat noises increase linearly with the number of OAs. Thus, the error rate worsens with the increasing numbers of OAs. In addition, noise accumulates exponentially with the magnitude of the amplifier gain.
+
+As a result of the gain spectrum of the OA, the ASE noise spectrum after many OAs tends to have a peak at a wavelength due to the self-filtering effect, which is described in clause II.6.2. In particular, if a closed all optical ring network architecture is considered, the ASE noise accumulates as if an infinite number of OAs were cascaded. Although the accumulation of ASE noise in filtered systems is considerably reduced by the filters, in-band ASE still increases with the number of cascaded OAs. Thus, the SNR degrades as the number of OAs increases.
+
+##### **II.6.1.3 Minimization of the effect of noise accumulation**
+
+The ASE noise accumulation can be reduced by decreasing the OA spacing (while maintaining the total gain equal to the total loss of the transmission path), since ASE noise accumulates exponentially with the magnitude of the amplifier gain. One of the following filtering techniques can further reduce the unwanted effect of ASE noise: use of ASE noise filters, or use of the self-filtering effect (self-filtering method).
+
+The self-filtering method is applicable for systems with several tens of OAs or more. In this method, the signal wavelength is aligned with the self-filtering wavelength so that the ASE noise received at the detector is reduced, just as if a narrow-band filter had been used. This is most effective when used with shortened OA spans and low-gain OAs to reduce the initial ASE noise.
+
+The self-filtering method is not applicable if an all-optical WDM closed ring network is considered. In fact, the resulting peak in the OAs overall gain spectrum may strongly affect the system performance. In this case, the accumulation of the ASE noise can be minimized with the ASE-filter method, which is obtained by filtering the WDM channels not dedicated to the network node before switching them out of the node.
+
+For systems with fewer OAs, the self-filtering method is less effective than the ASE-filter method. The ASE-filter method allows flexibility in the choice of the signal wavelength and provides other advantages (see clause II.6.2). Care must be taken in the selection of the filter characteristics, since the cascaded-filter passband is narrower than the passband of a single filter (unless it has a rectangular spectral passband). Conventional filters with a full width at half maximum (FWHM) in the order of 3 nm could be used in long-distance single-channel systems.
+
+#### **II.6.2 Self-filtering effect**
+
+##### **II.6.2.1 Description of effects**
+
+As a result of the ASE noise accumulation in non-filtered systems, the characteristic profile of the ASE spectrum (or the overall gain spectrum) tends to have a peak. The peak spectral line-width narrows with increasing numbers of OAs until it finally saturates after some number of OAs. This may result in only 2~3 nm wide spectral line-width after several tens of OAs. This effect is called self-filtering.
+
+The self-filtering effect is determined by the spectral shape of the emission and absorption cross-sections and by the degree of inversion of OAs. The self-filtering wavelength may change with changes in the host glass composition, input optical power, or inter-amplifier loss and their dependence on wavelength, pump wavelength and the length of the doped fibre. The self-filtering effect can generally be considered desirable in single-channel systems (as noted in clause II.6.1.3), but undesirable in multi-channel systems.
+
+##### **II.6.2.2 Induced transmission limitations**
+
+For systems with a limited number of OAs, the spectral width of the self-filtering gain peak remains broad and does not reduce ASE noise accumulation, even with the signal wavelength adjusted to the peak wavelength. In systems with many OAs and a well-developed self-filtering gain peak, the SNR can be high but may degrade if the signal wavelength shifts from the self-filtering wavelength. This shift can occur after system reconfiguration or repair because of changes in inter-amplifier loss.
+
+Multi-channel systems with cascaded OAs can suffer from power variation among channels that exponentially increase with the number of OAs (the number of OAs is the exponent). For example, the power spread for a five-channel system of $\sim 3$ dB after the first erbium-doped fibre amplifier (EDFA) increases to $\sim 15$ dB after the sixth EDFA. For multi-channel systems, changes in the total number of channels result in gain-spectral changes which perturb other channels. Saturation-induced spectrally-dependent gain also generates gain variation among the channels.
+
+Therefore, the loss-budget margin must be carefully designed to accommodate such EDFA-gain spectral changes both in filtered and non-filtered systems. The use of ASE filters eliminates the problem, as described in clause II.6.2.3.
+
+##### **II.6.2.3 Methods to deal with self-filtering effects**
+
+This clause discusses the use of both OA self-filtering effects and ASE noise filters to improve system performance.
+
+Using the self-filtering method to improve SNR is most effective when the optimum dispersion wavelength, self-filtering wavelength, and signal wavelength coincide. This method does not require the use of ASE noise filters, which can bring degradation associated with polarization-dependent losses in the filter. This is particularly true in transoceanic submarine systems. On the other hand, reliance on the self-filtering effect complicates system design, reconfiguration and repair because the signal wavelength must always meet the changeable self-filtering wavelength. The spectral characteristics of both OA gains and inter-amplifier losses should be as uniform as possible. Otherwise, the self-filtering gain peak may not become sufficiently narrow, thus degrading the SNR improvement and making it more difficult to prevent ASE noise-induced saturation in long-haul systems.
+
+To avoid such disadvantages, the ASE-filter method can be used to reduce ASE accumulation with the filter passband adjusted to the signal frequency. Narrow-band filters with FWHM $< 1$ nm are commercially available. The ASE noise accumulation is then minimized and the system can be freed from restrictions such as complexities of system design, reconfiguration and repair, and the requirements of short OA span and uniform performance of each OA.
+
+In multi-channel systems, the inter-channel power spread due to the self-filtering effect can be avoided by amplifying each channel in a physically separated OA. This method, however, demands a costly demultiplexer, separate OAs and a multiplexer. An alternative is to provide optical channel power equalization at each network node, even if this method demands additional control electronics and a more critical power budget through the network. An additional method is to use a less saturated or less strongly inverted OA, because this makes the attenuation less wavelength-dependent, and accordingly reduces inter-channel power spread. In a strongly inverted EDFA cascade, however, the ASE grows with the number of EDFAs at the first gain peak of $\sim 1530$ nm and needs to be eliminated with a short-wavelength-eliminating filter. In addition, the pre-emphasis method minimizes SNR differences for all channels by adjusting the transmitter optical powers for each channel based on the received signal information from the end terminal.
+
+#### **II.6.3 Optical surge generation**
+
+##### **II.6.3.1 Description of effects**
+
+When optical signal input power rapidly increases in sufficiently pumped EDFAs, optical surge occurs because of the slow gain dynamics of EDFAs. The optical surge is likely to occur particularly from output-power-controlled EDFAs. This is because the pump power for such EDFAs increases with the decrease in the optical input power and optical surge tends to occur when the input power suddenly recovers. Figure II.6-1 illustrates optical surge generation.
+
+When reconnecting a conventional connector, an optical-power rise time (10-90%) was $\sim 0.3$ ms, which is short enough to cause an optical surge. If the EDFA is already optically saturated, however, additional rapid increase in the optical input power may not cause significant optical surges.
+
+
+
+The figure consists of two parts. The left part is a schematic diagram of an Erbium-doped active fibre (EDFA). It shows an 'Input' signal entering from the left, a 'Constant pump power' source (indicated by an upward arrow), and an 'Output' signal exiting to the right. The active fibre is represented by three overlapping circles. The right part contains three timing diagrams. The top diagram shows 'Input power' as a step function increasing over 'Time'. The middle diagram shows 'Gain' starting at a higher 'Unsaturated gain' level and dropping to a lower 'Operating gain' level as the input power increases. The bottom diagram shows 'Output power' exhibiting a sharp 'Optical surge' (a peak) before settling to a new steady-state level.
+
+Figure II.6-1: Schematic and timing diagrams of optical surge generation in an EDFA.
+
+T1523420-96
+
+**Figure II.6-1 – Example of optical surge generation**
+
+##### II.6.3.2 Induced transmission limitations
+
+In EDFA cascades, under particular conditions, the optical surge peak power can range up to several watts, possibly damaging O/E converters and/or electrical pre-amps and optical components including optical-connector end faces. Optical surge is also harmful to human eyes. The threshold for damage for a contaminated optical-connector end face has been observed to be at optical power levels of about 20 dBm.
+
+##### II.6.3.3 Minimization of the effect of surge generation
+
+The following functions can be considered for optical surge prevention:
+
+- 1) to reduce or shut down the pump power to EDFAs when the loss of input signal is detected;
+- 2) to recover the pump power level to EDFAs when the recovery of the input signal is detected. In this respect, the reactivation of the pump laser power level up to its nominal value should happen gradually and a related minimum reactivation time should be defined.
+
+Figure II.6-2 shows an example of configuration that achieves surge prevention, where a loss-of-signal detection unit controls the pump laser on/off status. In case of a loss of signal just for a time sufficiently shorter than the gain dynamics of the EDFA, e.g., $< 1$ ms, the pump laser power needs to be kept unchanged.
+
+
+
+The diagram shows an optical path with 'Input' on the left and 'Output' on the right. A 'Loss-of-signal detection unit' is connected to the input path. This unit is also connected to a 'Pump laser', which in turn is connected to the Erbium-doped active fibre (represented by three overlapping circles). The pump laser's output is coupled into the optical path via a coupler (indicated by a diagonal line).
+
+Figure II.6-2: Schematic diagram of a surge-prevention system for an EDFA.
+
+T1523430-96
+
+**Figure II.6-2 – Example of a surge-prevention system**
+
+#### II.6.4 Saturation-induced non-linearity in SOAs
+
+##### II.6.4.1 Description of effects
+
+Semiconductor optical amplifiers (SOAs) suffer from a peculiar type of non-linear behaviour, related to the combined action of the fast gain-dynamics of the SOAs and the amplitude-phase coupling typical of semiconductor amplifying media.
+
+This phenomenon, referred to throughout as saturation-induced non-linearity, may affect the performance of telecommunication systems using SOAs due to the fact that the carrier lifetime $\tau_c$ (0.2-0.5 ns) of SOA is comparable to the width of the optical pulses used for transmission. In fact, the SOA gain can saturate so fast that the rising edge and the trailing edge of the optical pulse experience different gain. The temporal evolution of saturation depends in general on the temporal profile of the pulse whereas the degree of gain compression depends on the pulse energy, compared to the saturation energy of the SOA ( $E_{sat} = P_{sat} \tau_c$ , where a typical value for the saturation power intrinsic of the SOA is 30 mW – not to be confused with the 3 dB saturation power which is lower, 10-15 mW). This behaviour is ruled by the following equation:
+
+$$\frac{d\Gamma^{(t)}}{dt} = \frac{\Gamma_0 - \Gamma(t)}{\tau_c} - \frac{P_{in}(t)}{E_{sat}} \{\exp(\Gamma(t)) - 1\}$$
+
+where $\Gamma(t)$ is the gain coefficient integrated over the SOA length, $\Gamma_0$ is the unsaturated integrated gain of the SOA and $P_{in}(t)$ is the temporal profile of the optical signal. The gain of the SOA is given by $G(t) = \exp[\Gamma(t)]$ .
+
+Therefore, the optical signal exiting the amplifier is distorted by the differential gain, since $P_{out}(t) = G(t) P_{in}(t)$ . This behaviour can cause pattern effects in the optical data sequence, since the gain experienced by a pulse does change depending on the presence of logical 'marks' or 'spaces' in the preceding bits. It is important to note that this phenomenon can occur in every type of laser amplifier (including EDFAs), but in SOA the gain saturation time scale is comparable to the temporal duration of the optical bit.
+
+The peculiar aspect of SOAs is that the amplified pulse is also chirped and frequency shifted, due to the amplitude-phase coupling typical of semiconductor media. The reason for this is that the optical power of the pulse entering the SOA depletes the carrier population and thus modifies the index of refraction of the semiconductor cavity. As a consequence, the phase of the pulse changes dynamically as follows:
+
+$$\phi_{out}(t) = \phi_{in}(t) - \frac{1}{2} \beta_c \Gamma(t)$$
+
+$\beta_c$ is the line enhancement factor, the parameter measuring the strength of the amplitude-phase coupling (typically 4-6 for SOAs). The instantaneous frequency shift is obtained by differentiating the equation above with respect to time and taking into account the equation for $\Gamma(t)$ . This phenomenon is referred to as *saturation induced self-phase modulation* (SI-SPM), see [b-Agrawal]. SI-SPM can be detrimental when combined with fibre chromatic dispersion.
+
+##### II.6.4.2 Induced transmission limitations
+
+Conventional single-channel point-to-point optical systems using NRZ transmitters are predominantly impaired by pattern effects and, to a lesser extent, by SOA-induced pulse chirp [b-Settembre]. Pattern effects can also affect propagation of RZ pulses; in this case, if the pulse power is sufficiently high, the frequency-shift of the pulse may also play a relevant role. When the fibre dispersion at the wavelength of operation is different from zero, the frequency shift is converted into time jitter that can destroy the original bit sequence, thus setting limitations to the system reach. This effect may be particularly detrimental when non-linear transmission techniques
+
+are used, such as optical solitons, because for solitons the pulse energy should be maintained high and the dispersion should be different from zero (anomalous), see [b-Mecozzi].
+
+##### **II.6.4.3 Methods to minimize induced limitations**
+
+The saturation-induced non-linearity is inherent to the SOA. It can be avoided by operating the SOA in the linear regime or by implementing gain clamping techniques. In the first case, attention should be paid to ASE accumulation along the optical link; use of an optical filter after each amplifier can be useful to avoid static gain saturation effects due to ASE accumulation. On the other hand, gain clamping reduces the available gain. By keeping the average power low (1-5 mW) and dispersion close to zero, good performance of NRZ and RZ systems has been demonstrated experimentally up to 400 km [b-Reid]. The impairments due to SI-SPM in long-haul soliton systems can be alleviated by using suitable filtering techniques (sliding filters), see [b-Reid].
+
+# Appendix III
+
+## Pre-amplifier parameters
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This appendix contains the definition of the relevant characteristic parameters of the pre-amplifier which allows, by standard formulae, to obtain the minimum input power which ensures a $BER = 10^{-12}$ at the terminal receiver equipment (TRE).
+
+On the basis of theoretical considerations and experimental tests related to optical amplifier noise, the relevant PA characteristic parameters which allow to obtain the minimum input power which ensures a $BER = 10^{-12}$ at the TRE are:
+
+- max small signal gain "GMax" ([ITU-T G.661]);
+- small signal gain "G" ([ITU-T G.661]);
+- signal-spontaneous noise figure " $NF_{s-sp}$ " ([ITU-T G.661]);
+- noise figure "NF" ([ITU-T G.661]);
+- (equivalent) spontaneous-spontaneous beat noise optical bandwidth ( $B_{sp-sp}$ ) ([ITU-T G.661]).
+
+The optimum amplifier (without internal reflection noise) noise is dominated by two principal components in addition to the contribution of the shot noise of the signal and spontaneous emission noise. These two principal components are the signal-spontaneous beat noise and the spontaneous-spontaneous beat noise.
+
+NOTE – The output noise terms can be subdivided into five categories:
+
+- a) shot noise from the amplified input signal;
+- b) shot noise from the amplified spontaneous emission (ASE);
+- c) signal-spontaneous beat noise from signal mixing with ASE;
+- d) spontaneous-spontaneous beat noise from ASE mixing with itself;
+- e) reflection noise.
+
+Each of the noise contributions can be expressed in the form of a partial noise factor "F", where the total noise figure is the sum of all individual contributions. The total noise factor (in linear, not in logarithmic units) is:
+
+$$F_{total} = F_{shot-sig} + F_{shot-ASE} + F_{sig-sp} + F_{sp-sp} + F_{refl}$$
+
+This equation can be used both for evaluating the noise factor from optical measurements, as well as for estimating the influence of such parameters as gain, reflections, source line-width and baseband frequency. It represents a complete noise factor model of an OFA.
+
+In these conditions it is possible to obtain, by standard formulae, the following expression for total noise factor:
+
+$$F = F_{s-sp} \left( 1 + \frac{h\nu n_{sp} B_{sp-sp}}{2P_{in}} \frac{G-1}{G} \right)$$
+
+where:
+
+$$F_{s-sp} = 2n_{sp} \left( \frac{G-1}{G} \right) \text{ and } n_{sp} = \frac{n_2}{n_2 - n_1}$$
+
+$h\nu$ is the signal photon energy, $P_{in}$ is the optical power at PA input, $n_2$ is the population density of the excited level, $n_1$ is the population density of the base level and $G$ and $B_{sp-sp}$ have been defined before. It is clear that $F$ reduces, by reducing the $B_{sp-sp}$ value, but, for compatibility with existing [ITU-T G.957], it has to be limited at values of the order of 1 nm (a 120 GHz). The SNR at the TRE is given by the following formula:
+
+$$SNR = \frac{m^2 P_{in}}{h\nu \cdot B \cdot F + \frac{N_{R_x}}{P_{in} G^2}}$$
+
+where $m$ is the modulation depth $\left(1 - \frac{1}{ExtRatio}\right)$ , $B$ is the receiver electrical bandwidth (proportional to the bit rate) and $N_{R_x}$ is the TRE equivalent noise. From the previous two formulae, it is possible to obtain the minimum input power of the PA for $BER = 10^{-12}$ on the TRE. It is clear that the optimum PA must have a sufficiently high gain in order to make negligible the noise contribution of the TRE compared to the pre-amplifier one. The SNR value for BER better than $10^{-12}$ must be maintained in all the input power range. The PA will be characterized, from the noise point of view, by defining small signal gain ( $G$ ), signal-spontaneous emission contribution to the noise factor ( $F_{s-sp}$ ) and spontaneous-spontaneous beat noise equivalent bandwidth ( $B_{sp-sp}$ ). It is important to verify the total noise figure of the PA in order to be sure that no contributions from internal reflection noise are affecting the PA.
+
+### Example
+
+#### Calculation of the SNR ratio for a receiver equipped with a PA able to ensure a BER = $10^{-12}$ at 2.5 Gbit/s SDH-TRE
+
+On the basis of the previous considerations and the previously defined parameters, the SNR at the output of the PA can be calculated from the following formula:
+
+$$SNR_{(PA)} = \frac{m^2 P_{in}}{h\nu \cdot B \cdot F}$$
+
+In the above formula, the shot noise contribution has not been considered because it is negligible compared to the beating noise components, having defined a small signal gain of 20 dB. This formula assumes the worst-case approximation where the noise on the zeros is considered equal to that on the ones (zeros do not present a signal-spontaneous beat noise) and where the output noise is considered Gaussian.
+
+From the above-mentioned formula, it is easy to obtain the sensitivity of the PA.
+
+The overall sensitivity of the composite receiver (PA + TRE) is obtained adding to the divisor of the previous formula the term $\frac{N_{R_x}}{P_{in} G^2}$ , in which $N_{R_x}$ is the TRE equivalent noise.
+
+$$SNR_{(PA+TRE)} = \frac{m^2 P_{in}}{h\nu \cdot B \cdot F + \frac{N_{R_x}}{P_{in} G^2}}$$
+
+It is, however, obvious that the term $\frac{N_{R_x}}{P_{in}G^2}$ is negligible for sufficiently high values of the gain $G$ .
+
+Taking into account the compatibility in accordance with [ITU-T G.957] for a 2.5 Gbit/s TRE with a minimum sensitivity of $-26$ dBm for $BER = 10^{-12}$ and the characteristic parameters of the PA previously considered:
+
+- | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| – Maximum small signal gain | 24 dB | |
+| – Small signal gain ( $G$ ) | $\geq 20$ dB | |
+| – Signal-spontaneous noise figure ( $NF_{s-sp}$ ) | $\leq 5.5$ dB | |
+| – Available signal wavelength band ( $B_{s-sp}$ ) | 1 nm (0.8 – 1.2) | |
+| – Signal-to-noise ratio (SNR) for $BER = 10^{-12}$ on the TRE | 3 dB | |
+| – Extinction ratio of the optical source | 8.2 dB | |
+| – TRE pass bandwidth (the electrical bandwidth of the receiver, proportional to the bit rate value) $B = f_{Nyquist} (1 + \ell)$ ; where $f_{Nyquist} = (\text{bit rate})/2 = (2.5 \text{ Gbit/s})/2$ and $\ell$ is the roll-off coefficient of the Nyquist's channel, variable between 0 and 1 | | $\begin{cases} \text{min. value} &= \frac{2.5}{2} \text{ GHz} \\ \text{average value} &= \frac{2.5}{2} \cdot 1.5 \text{ GHz} \\ \text{maximum value} &= 2.5 \text{ GHz} \end{cases}$ |
+
+It is easy to establish that for values of the receiver signal of $-16$ dBm, the contribution of the TRE noise can be considered negligible. With the parameter values previously considered, a minimum input power of $-36$ dBm for $BER = 10^{-12}$ at the TRE is obtained. This value can be considered inclusive of the margin due to the worst-case hypothesis introduced in the calculations. Due to the maximum gain value, the output signal from the PA will be $-12$ dBm, allowing the sensitivity of the PA to be considered as that of the composite receiver (PA + TRE). With respect to the PA the minimum gain operating conditions (small-signal gain, $G = 20$ dB), and the average optical power at the output of the PA will be $-16$ dBm allowing again the sensitivity of the PA to be considered as that of the composite receiver (PA + TRE).
+
+By using the previous values and formulae, it is also possible to compute that a pre-amplifier output SNR ratio better than 13 dB is achievable with a pre-amplifier input power level down to $-43$ dBm, when a configuration without line amplifiers is used.
+
+# Appendix IV
+
+## OAM aspects of OAs
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Possible generic OAM aspects for OA subsystems and devices are given below.
+
+## IV.1 OA subsystems
+
+Because OATs and OARs from a maintenance perspective are not different from conventional transmitters and receivers, the associated operation, administration and maintenance (OAM) aspects are identical to those of transmitters and receivers specified in [ITU-T G.783].
+
+## IV.2 OA devices
+
+The following OAM conditions can be presented as information to the involved management system:
+
+- OA loss of signal (LOS), indicating possible loss of input signal (transmission defect);
+- OA failure, indicating that an optical amplifier can no longer perform its basic function of optical amplification (equipment defect);
+- OA in shut-down conditions (output status).
+
+This distinction is made to provide the user with information on the equipment and/or cable plant. Furthermore, OAs can be provided with an "enable/disable output" control signal in order to be able to limit optical power levels possibly needed to satisfy optical safety requirements.
+
+NOTE – The use of further sources of equipment failure like "OA degradation" or "loss of optical supervisory channel" (in case of the presence of line amplifiers) is for further study.
+
+# Bibliography
+
+- [b-ITU-T G.650.2] ITU-T G.650.2 (2007), *Definitions and test methods for statistical and non-linear related attributes of single-mode fibre and cable*.
+- [b-ITU-T G-Sup.39] ITU-T G-series Recommendations – Supplement 39 (2006), *Optical system design and engineering considerations*.
+- [b-Agrawal] Agrawal, G.P., Olsson, N.A. (1989), *Self-phase modulation and spectral broadening of optical pulses in semiconductor laser amplifiers*, IEEE Journal of Quantum Electronics, Volume 25, pp. 2297-2306.
+- [b-Chbat] Chbat, M., Bigo, S. (1998), *Measurement of the impact of fiber non linearities on high data rate, dispersion-managed WDM systems*, Symposium on Optical Fiber Measurements, NIST (USA), September.
+- [b-Chraplyvy] Chraplyvy, A.R., Tkach, R.W. (1993), *What is the actual capacity of single-mode fibers in amplified lightwave systems?* IEEE Photonics Technology Letters, Volume 5, pp. 666-668.
+- [b-Faerbert] Faerbert, A., *et al.* (1999), *Optimised dispersion management scheme for long-haul optical communication*, Electronics Letters, Volume 35-21, pp. 1865-1866.
+- [b-Gordon] Gordon, J.-P., and Mollenauer, L.F. (1990), *Phase noise in photonic communications systems using linear amplifiers*, Optics Letters, Vol. 15, No. 23, pp. 1351-1353, Dec.
+- [b-Kaminow] Kaminow, I.P., and Koch, T.L. (1997), *Optical Fiber Telecommunications*, Academic Press, Volume IIIA, p. 213.
+- [b-Kaminow2] Kaminow, I.P., and Koch, T.L., *ibid.* p. 167.
+- [b-Koch] Koch, T.L., Kaminow, I.P. (1997), *Optical Fiber Telecommunication*, Academic Press, Volume IIIA, Chapter 8.
+- [b-Mao] Mao, X.P., Tkach, R.W., Chraplyvy, A.R., Jopson, R.M., and Derosier, R.M. (1992), *Stimulated Brillouin Threshold dependence on fiber type and uniformity*, IEEE Photonics Technology Letters, Volume 4, pp. 66.
+- [b-Marcuse] Marcuse, D., Chraplyvy, A.R., and Tkach, R.W. (1994), *Dependence of cross-phase modulation on channel number in fiber WDM systems*, Journal of Lightwave Technology, Volume 12, Number 5, pp. 885-890, May.
+- [b-Mecozzi] Mecozzi, A. (1995), *Soliton transmission control with semiconductor amplifiers*, Optics Letters, Volume 20, pp. 1616-1618.
+- [b-Reid] Reid, J.J.E., *et al.*, *An international field trial at 1.3 μm using an 800 km cascade of semiconductor optical amplifiers*, Proc. of ECOC'98 (1998), Volume 1, pp. 567-568, Madrid (Spain).
+- [b-Settembre] Settembre, M., *et al.* (1997), *Cascaded optical communication systems with in-line semiconductor optical amplifiers*, J. Wavelength Technol., Volume 15, pp. 962-967.
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|---------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7007878365d2a1546caa6f47199dc793303fd541
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2759a445a3e8db1230ea39c639a9f7018d14163437b6cb672a16c9bcbf5bc5f0
+size 32656
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2ff3c8f8b0b39439be365d5d26d02ab02a320d9d
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aea48c6f9d98a2112fb34d5ba707f70d4278daa70c467408d75fac26c409340a
+size 35311
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/183007754364096b2d89f42200cf870f_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/183007754364096b2d89f42200cf870f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6bbf4ad06ba5fa05170ac19ba23f32b999d3275d
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/183007754364096b2d89f42200cf870f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2165cc0a059daf1687c4a0b939c41572ce6853b55b349cb91f5734c3c1e65dc
+size 74500
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c35f283d045ab7edac18992a6d6b03b14ad70ab6
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:20127d93b0eaed4017458cad10fe2f67bbc30c16f9b0eca6a72744eff54f6072
+size 11379
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a3b32abf2536cc2f9249d37b9703deb4eb94a002
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f0fc16446469c540159aa0f085e0b4a4b6a5b3548a90e50426dab0b4721a4e6a
+size 47097
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ddece25de26bc456a3d7ed0c794cb990cae809c1
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e873d26ee58196b83413b5ede8e82377033682c12d8650d0dd5cbf72687ead65
+size 16625
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/4636adff5682a064f0ae5f13a1d464a6_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/4636adff5682a064f0ae5f13a1d464a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1f60bbc76cf39b888b835d83b27e2104a5c30a2a
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/4636adff5682a064f0ae5f13a1d464a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:76482d000ce57f6f5a80c34a03d1473a9ce81b2bed1590ca586ccee567a6b406
+size 32538
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a3528448dcc2cdd0dee6cb5361cd31407a962bb1
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e2b8d2c5166f824d0221d25590c9fb3c5ca35f3a249b87b0d4f867f60b02d892
+size 20991
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..03b75fee7e0a32df97c12031a13673d8eb120fb6
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:67ca91286ddde18b660f48a7411f5e64220f6bc502b95b6ab5a72c41036bfcff
+size 15276
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/48a08e5cabec8b75386679d8a57dec3e_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/48a08e5cabec8b75386679d8a57dec3e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..44d99dc365c1b126a8557bd2a721c82f86d0b7a7
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/48a08e5cabec8b75386679d8a57dec3e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4be67a918d6914dc34d69ffa22ee7cf06fc1fdfd78a3e223605fcf61953f485c
+size 53191
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..981050bbc5f68c7b9a0701b6fde2f3a28987ef8a
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b991c4c280c953f720c58d71395b5b14a823a08b635147995a84f31a4b774ab0
+size 26418
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/4f148853ae68fdcf5e43f7604cab457d_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/4f148853ae68fdcf5e43f7604cab457d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a5a5440e9574c6b4d496100b5eb7c5a3e722a698
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/4f148853ae68fdcf5e43f7604cab457d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e6b5fd100799751d0b9826a1554f393e780af1ab63fcc80c7129f62d61ff3eff
+size 19985
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..002df7057a63157fa1bf19d456d3b4da33075747
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:50eb80a155df7e4c5abfda86b4626d120993ee27262d2c40a6a1df6ccf6fb5e2
+size 35632
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..04b4707942fbfc3299c20dd7cb9d751bb4466037
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:050ead467ada64a38411736cd84262ccd7f6870845774c19db18834e1006f5b9
+size 26753
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/63e0c22852c26699d0bd095a2d796bab_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/63e0c22852c26699d0bd095a2d796bab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..732b213ab5097d7883b43be37a4bcd18730e2790
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/63e0c22852c26699d0bd095a2d796bab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a609ccccf0b6378755fe44a04d3ca126c4f101382b38f7b046219927b7022b50
+size 10722
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..585a0a4afab7b3f17e222ef1554faaf4581b10c8
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a11909a9f74801ee0a0fceafa5eaaa74a41c4145055870248f6c8ed897c3cbbc
+size 21959
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f6cb886705a8e033f989f8dcb868f2880286d0dd
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:11374f3a65d500c37b495bdc2e22b0f19d9093431abeb37cac72ff37bbdbcdfc
+size 53933
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f04b5429e0dbdb78c9cbcbe77528a85be80aef13
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be6319edda00386ecb24169382dddff73074782f4e9d0ff145de8fd695bc2ec6
+size 51152
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/744acfe8d4e31bcf03f95714c2f6e567_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..28f750bc39d0e67894ba0e48dc05b27e799598c8
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/744acfe8d4e31bcf03f95714c2f6e567_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b41ab456c4a5794d13f36006d98b3b8ec8da6dfabafc69dc4e4aa8405242b34b
+size 30898
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a61a2126efc8a5f75b57603c61ae42518d6e169a
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:45cb86aff53340b0ba92070d55a69d4e3344b475ba4e605a94b342451afc342c
+size 8338
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..604c176a069e182c9aaafee170d8184b45c4acfe
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a2703044a233fc9c11e7c087e9ba7fb0b2dd0500b65cf816bc1a316b6c1c67b1
+size 31721
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b1237bc64deb4628497430ffd2399be114b2bb27
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c4af5ccfaab3b839dc857b86b467129c00ea7d63ef61f8295878383600f5c06d
+size 37388
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/91be14371a97fb5ce9eeb29ae18d07c3_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/91be14371a97fb5ce9eeb29ae18d07c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4974e9e8d6379c9d56f37e72d331d4aa9f6dd0d7
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/91be14371a97fb5ce9eeb29ae18d07c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:01fedcc0ce6285a2dcecec638866b3875c9e3a28880035dd0088da15493ecb42
+size 35972
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d7c0bb316ceb1cb8fd8f954acbcc9e3ab5627b6b
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:14e8ca3ec6682410ed6970499d23d1042384ef2481420a4b3b9183d2a22658d9
+size 27024
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c72b271d28dcb6091b99ab5539f5fb5f70b121b8
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:20e0cb0e2eeac8fe1d1e96ab77e7e78c27f35d9bd8f4f779a77cf2b38b6eee4e
+size 41567
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2a1b1d683e1881c44aad95358734d20d903aaa11
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:41424e64ca403cbffa04b2019cf5751c3acc55d6b6bc8442cfe8af98209c7095
+size 33943
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/a3472689858b068ef469213682965325_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/a3472689858b068ef469213682965325_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da65134fd92a5627d86ba8bb1b0fd4f884110beb
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/a3472689858b068ef469213682965325_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a5bf7b3b75fcc6a0192a53c3becf6da628baea68b26b70a9e607e2a57a0711a0
+size 48608
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/adb1f42239329fa8283d1a40005f989f_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/adb1f42239329fa8283d1a40005f989f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3ffb24a73d0f7a22f2aecc5b2827b3eb7272b4c1
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/adb1f42239329fa8283d1a40005f989f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f33fbea6ee51bb86d8ff812ad22ae4af525020c1482699713e5a60b1208136d2
+size 23081
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e584ddeb5e60b3c5682f298804599bc4c4c80b1f
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3c011efdd901efea4db65e12d25e8a52a70378c37ac40f9450d21a834eac557b
+size 11020
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4b765c315c3b7ecc808dbdfd4475dfbe465d003a
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2fc81b45aaef4126cacc78a19e6f270cf84a46d5a907a6ac597d55a9347c5fdc
+size 41116
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da7a78896a802278f4a847c4f5f87a6dc8cb01b8
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5670572b59f33f0d9a577d19b5d08e2dedb90d8e879a946db956b1ece64396bd
+size 18522
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9e10cf6febeaa55f840357744a22a648722d2c0c
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1bea83677a98e727261cb886c313c6dbd6bf0f35f277f5d275bb03d4ddd278d
+size 54582
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/d68ecc44f3cfaed866a846f9fa4bdf38_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/d68ecc44f3cfaed866a846f9fa4bdf38_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9e5dbf2cc4efa90f9eb5a81fb8bd0b656fd93e11
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/d68ecc44f3cfaed866a846f9fa4bdf38_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7712ffaf564b1206ffd0c76e4b320e0a99732b4cae68197c2c892d43b3605aa3
+size 73288
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bd41db4562fc8549d4a3d8a2d50c7cc4aa0c0c96
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:774ab9b6eafc8dab9ff3494dccca1064fc069916fc33e0f8d946caaff4ea65a3
+size 36922
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..622e236cffa69980a5ac763f8a20a090e2cc237c
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0094fa697cfbd653a8342b29ae0c2d3406a69496a75eac2c73667843ebd9e71a
+size 62054
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/f2ea0f64a770b22b902820457d262265_img.jpg b/marked/G/T-REC-G.667-200612-I_PDF-E/f2ea0f64a770b22b902820457d262265_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..91c47fa01926600221dfe25a49e83879bc807521
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/f2ea0f64a770b22b902820457d262265_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9753baa44c3dfc03f6859b9419478a79e19cebe63ec39a7dc4e742e25088813d
+size 37232
diff --git a/marked/G/T-REC-G.667-200612-I_PDF-E/raw.md b/marked/G/T-REC-G.667-200612-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..abc8c12c88d3a4bf4814b186d38111bb4e0d2f61
--- /dev/null
+++ b/marked/G/T-REC-G.667-200612-I_PDF-E/raw.md
@@ -0,0 +1,900 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**G.667**
+
+(12/2006)
+
+SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
+DIGITAL SYSTEMS AND NETWORKS
+
+Transmission media and optical systems characteristics –
+Characteristics of optical components and subsystems
+
+# --- **Characteristics of adaptive chromatic dispersion compensators**
+
+ITU-T Recommendation G.667
+
+
+
+The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking through it, symbolizing global communication. To the right of the globe, the text "International Telecommunication Union" is written in blue.
+
+ITU logo
+
+## ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS**
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 |
+| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 |
+| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 |
+| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 |
+| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 |
+| TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS | G.600–G.699 |
+| General | G.600–G.609 |
+| Symmetric cable pairs | G.610–G.619 |
+| Land coaxial cable pairs | G.620–G.629 |
+| Submarine cables | G.630–G.639 |
+| Free space optical systems | G.640–G.649 |
+| Optical fibre cables | G.650–G.659 |
+| Characteristics of optical components and subsystems | G.660–G.679 |
+| Characteristics of optical systems | G.680–G.699 |
+| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 |
+| DIGITAL NETWORKS | G.800–G.899 |
+| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 |
+| QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER-RELATED ASPECTS | G.1000–G.1999 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.6000–G.6999 |
+| DATA OVER TRANSPORT – GENERIC ASPECTS | G.7000–G.7999 |
+| PACKET OVER TRANSPORT ASPECTS | G.8000–G.8999 |
+| ACCESS NETWORKS | G.9000–G.9999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# **Characteristics of adaptive chromatic dispersion compensators**
+
+## **Summary**
+
+ITU-T Recommendation G.667 contains parameters and definitions for devices providing adaptive chromatic dispersion compensation. These devices are needed for transmission and detection of optical signals in a system exhibiting high levels of dynamic variation of chromatic dispersion which would otherwise impair system operation. Single and multichannel line adaptive dispersion compensators are described, as well as single and multichannel adaptive dispersion compensating transmitters and receivers which may comprise electrical or optical forms of chromatic dispersion compensation. Information on single channel and multichannel adaptive chromatic dispersion compensation implementation, as well as principles of adaptive dispersion compensation, can be found in informative appendices.
+
+## **Source**
+
+ITU-T Recommendation G.667 was approved on 14 December 2006 by ITU-T Study Group 15 (2005-2008) under the ITU-T Recommendation A.8 procedure.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2007
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+# CONTENTS
+
+| | Page |
+|-------------------------------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References..... | 1 |
+| 3 Terms and definitions ..... | 2 |
+| 3.1 Terms defined elsewhere ..... | 2 |
+| 3.2 Terms defined in this Recommendation..... | 2 |
+| 4 Abbreviations..... | 5 |
+| 5 Reference configurations ..... | 6 |
+| 5.1 Line ADCs..... | 6 |
+| 5.2 ADC transmitters..... | 7 |
+| 5.3 ADC receivers ..... | 7 |
+| 6 Parameters of ADCs ..... | 8 |
+| Appendix I – Single-channel and multichannel ADC implementation ..... | 13 |
+| I.1 Single or multichannel line ADC implementation ..... | 13 |
+| I.2 Single-channel ADC transmitter implementation ..... | 14 |
+| I.3 Multichannel ADC transmitter implementation..... | 15 |
+| I.4 Single-channel ADC receiver implementation..... | 16 |
+| I.5 Multichannel ADC receiver implementation ..... | 18 |
+| Appendix II – Principles of adaptive dispersion compensation (ADC)..... | 20 |
+| II.1 Introduction ..... | 20 |
+| II.2 Adaptive dispersion compensation applications ..... | 20 |
+| II.3 Principles of adaptive dispersion compensation..... | 21 |
+| II.4 Chromatic dispersion monitoring..... | 25 |
+| Bibliography..... | 29 |
+
+
+
+# Characteristics of adaptive chromatic dispersion compensators
+
+# 1 Scope
+
+This Recommendation contains parameters and definitions for devices providing adaptive chromatic dispersion compensation needed for transmission and detection of optical signals in a system exhibiting dynamic variation of chromatic dispersion. The adaptive dispersion compensating devices described include both single and multichannel applications. This Recommendation defines requirements and key parameters for adaptive dispersion compensators (ADC). This Recommendation distinguishes line adaptive dispersion compensators from adaptive dispersion compensating transmitters and receivers which may comprise electrical as well as optical forms of chromatic dispersion compensation.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T G.650.2] ITU-T Recommendation G.650.2 (2005), *Definitions and test methods for statistical and non-linear related attributes of single-mode fibre and cable.*
+- [ITU-T G.652] ITU-T Recommendation G.652 (2005), *Characteristics of a single-mode optical fibre and cable.*
+- [ITU-T G.653] ITU-T Recommendation G.653 (2006), *Characteristics of a dispersion-shifted single-mode optical fibre and cable.*
+- [ITU-T G.654] ITU-T Recommendation G.654 (2006), *Characteristics of a cut-off shifted single-mode optical fibre and cable.*
+- [ITU-T G.655] ITU-T Recommendation G.655 (2006), *Characteristics of a non-zero dispersion-shifted single-mode optical fibre and cable.*
+- [ITU-T G.656] ITU-T Recommendation G.656 (2006), *Characteristics of a fibre and cable with non-zero dispersion for wideband transport.*
+- [ITU-T G.661] ITU-T Recommendation G.661 (2006), *Definition and test methods for the relevant generic parameters of optical amplifier devices and subsystems.*
+- [ITU-T G.662] ITU-T Recommendation G.662 (2005), *Generic characteristics of optical amplifier devices and subsystems.*
+- [ITU-T G.665] ITU-T Recommendation G.665 (2005), *Generic characteristics of Raman amplifiers and Raman amplified subsystems.*
+- [ITU-T G.666] ITU-T Recommendation G.666 (2005), *Characteristics of PMD compensators and PMD compensating receivers.*
+- [ITU-T G.671] ITU-T Recommendation G.671 (2005), *Transmission characteristics of optical components and subsystems.*
+
+# 3 Terms and definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined in [ITU-T G.671]:
+
+- channel frequency range;
+- channel insertion loss;
+- channel insertion loss deviation;
+- phase ripple;
+- insertion loss;
+- polarization dependent loss;
+- polarization dependent reflectance;
+- polarization mode dispersion.
+
+This Recommendation uses the following term defined in ITU-T Rec. G.692:
+
+- maximum central frequency deviation.
+
+This Recommendation uses the following term defined in ITU-T Rec. G.698.1:
+
+- maximum spectral excursion.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 ADC transmitter:** An optical transmitter containing adaptive chromatic dispersion compensation functionality.
+
+**3.2.2 ADC receiver:** An optical receiver containing adaptive chromatic dispersion compensation functionality.
+
+**3.2.3 dispersion compensation parameter:** This parameter depends on the type of dispersion compensation device, and describes the achievable dispersion compensation performance of an ADC.
+
+For an ADC transmitter, the transmission performance related to dispersion of the ADC transmitter can be changed adaptively according to the dispersion change of the optical transmission link in which it is operating. The dispersion compensation parameter is the dispersion accommodation value of the optical transmitter signal that can be achieved by the ADC transmitter over the channel frequency range.
+
+For a line ADC, the dispersion compensation value between the input port and the output port of the line ADC can be changed adaptively according to the dispersion change of the optical transmission link in which the line ADC is operating. The dispersion compensation parameter is the dispersion compensation value between the input port and the output port that can be achieved by the line ADC device over the channel frequency range.
+
+For an ADC receiver, the dispersion tolerance of the receiver can be changed adaptively according to the residual dispersion value of the optical transmission link. The dispersion compensation parameter is the acceptable residual dispersion value of the optical input signal to the ADC receiver over the channel frequency range while the BER remains lower than the specified limit.
+
+**3.2.4 dispersion compensation tuning range:** The difference between the maximum value of the dispersion compensation parameter and the minimum value of the dispersion compensation parameter of an ADC device (measured as ps/nm).
+
+**3.2.5 dispersion compensation tuning time:** For an ADC transmitter or a line ADC, this is the time duration from the start of a change of the dispersion compensation parameter to the time after which it remains within the limits of the new target value plus and minus the specified tolerance. This is illustrated in Figure 3-1.
+
+
+
+The figure is a line graph showing the 'Dispersion compensation parameter' on the vertical axis and 'Time' on the horizontal axis. A curve starts at a lower constant value and at a certain point in time, it begins to rise sharply. It overshoots a central dashed horizontal line (labeled 'Target value') and reaches a peak. After the peak, it oscillates, dipping below the target value and then rising again, gradually settling towards the target value. A horizontal double-headed arrow, labeled 'Dispersion compensation tuning time', starts at the beginning of the rise and ends at a vertical dashed line that marks the point where the curve has settled within the tolerance range. To the right of the graph, three horizontal lines are indicated with arrows: the top dotted line is 'Target value + tolerance', the middle dashed line is 'Target value', and the bottom dotted line is 'Target value - tolerance'.
+
+Figure 3-1: Illustration of dispersion compensation tuning time for an ADC transmitter or a line ADC. The graph shows the dispersion compensation parameter (Y-axis) versus Time (X-axis). A step change occurs at the start, followed by an overshoot and settling. The tuning time is the duration from the start of the change to the point where the parameter settles within the target value ± tolerance. The target value is indicated by a dashed line, and the tolerance limits are indicated by dotted lines.
+
+**Figure 3-1 – Illustration of dispersion compensation tuning time for an ADC transmitter or a line ADC**
+
+For an ADC transmitter, the specified tolerance is the specified error of the dispersion accommodation value.
+
+For a line ADC, the tolerance is the specified error of the dispersion compensation value.
+
+For an ADC receiver, the dispersion compensation tuning time is the time duration from a step change of the input signal residual dispersion to the time after which the BER remains lower than the specified limit. This is illustrated in Figure 3-2.
+
+
+
+Figure 3-2: Illustration of dispersion compensation tuning time for an ADC receiver. The graph plots Bit Error Ratio (BER) on the y-axis against Time on the x-axis. A horizontal dashed line represents the BER limit. The BER curve starts at a high value, remains constant for a short duration, then drops sharply, dips below the BER limit, and then rises back to a high value. A horizontal double-headed arrow labeled 'Dispersion compensation tuning time' spans the duration from the start of the drop to the point where the BER curve returns to its initial high value. Below the x-axis, a downward-pointing arrow is labeled 'Error free', indicating the region where the BER is below the limit.
+
+**Figure 3-2 – Illustration of dispersion compensation tuning time for an ADC receiver**
+
+NOTE – The tuning time will depend on the range between the current state and the new target state.
+
+**3.2.6 maximum rate of change of dispersion compensation parameter:** This is the maximum rate of change of link chromatic dispersion with time that can be adequately compensated for by the ADC device.
+
+This parameter depends on the type of the dispersion compensation device.
+
+For an ADC transmitter or a line ADC, this is the maximum value of the rate of change of link chromatic dispersion with time (in ps/nm/s) that can be compensated for while maintaining the residual dispersion of the link within the specified tolerance.
+
+For an ADC receiver, this is the maximum value of the rate of change of link chromatic dispersion with time (in ps/nm/s) that can be tolerated while meeting the specified BER.
+
+**3.2.7 minimum optical signal-to-noise ratio:** The value of optical signal-to-noise ratio (OSNR) at point MPI-R to achieve the specified BER for the optimum link residual dispersion. This parameter depends on the type of optical system.
+
+For a single-channel system, this is the minimum value of the ratio of the signal power to the noise power density (referred to 0.1 nm) at the signal wavelength.
+
+For a multichannel system, this is the minimum value of the ratio of the signal power in the wanted channel to the highest noise power density (referred to 0.1 nm) in the range of the central frequency plus and minus the central frequency deviation or the maximum spectral excursion.
+
+**3.2.8 OSNR penalty due to chromatic dispersion:** The difference in the optical signal-to-noise ratio at point MPI-R to achieve the specified BER between optimum link residual dispersion and the worst value for all specified values of link residual dispersion.
+
+**3.2.9 ADC receiver sensitivity:** The value of mean received power at point MPI-R to achieve the specified BER. This must be met for the optimum link residual dispersion with a worst-case transmitter, but does not have to be met with degradations of the optical path other than dispersion.
+
+**3.2.10 ADC receiver sensitivity penalty due to chromatic dispersion:** The difference in the mean received power at point MPI-R to achieve the specified BER between optimum link residual dispersion and the worst value for all specified values of link residual dispersion. This does not have to be met with degradations of the optical path other than dispersion.
+
+# 4 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|----------|-------------------------------------------------------------|
+| ADC | Adaptive Dispersion Compensation |
+| ADC-Rx | Adaptive Dispersion Compensating Receiver |
+| ADC-Tx | Adaptive Dispersion Compensating Transmitter |
+| BER | Bit Error Ratio |
+| DEMUX | Demultiplexer |
+| DFE | Decision Feedback Equalization |
+| EDC | Electrical Dispersion Compensation |
+| FBG | Fibre Bragg Grating |
+| FFE | Feed Forward Equalization |
+| LADC | Line Adaptive Dispersion Compensator |
+| M-ADC-Rx | Multichannel Adaptive Dispersion Compensating Receiver |
+| M-ADC-Tx | Multichannel Adaptive Dispersion Compensating Transmitter |
+| M-LADC | Multichannel Line Adaptive Dispersion Compensator |
+| MLSE | Maximum Likelihood Sequence Estimation |
+| MPI | Main Path Interface |
+| MUX | Multiplexer |
+| NRZ | Non-Return to Zero |
+| OA | Optical Amplifier |
+| O-E-O | Optical-Electrical-Optical (conversion) |
+| OSNR | Optical Signal-to-Noise Ratio |
+| PDL | Polarization-Dependent Loss |
+| PMD | Polarization Mode Dispersion |
+| RZ | Return to Zero |
+| S-ADC-Rx | Single-Channel Adaptive Dispersion Compensating Receiver |
+| S-ADC-Tx | Single-Channel Adaptive Dispersion Compensating Transmitter |
+| S-LADC | Single-Channel Line Adaptive Dispersion Compensator |
+| VIPA | Virtually-Imaged Phased-Array |
+| VSB | Vestigial Side Band |
+| WDM | Wavelength Division Multiplexing |
+
+# 5 Reference configurations
+
+ADCs are intended to be used to reduce dispersion-induced signal degradations in optical transmission systems with dynamic dispersion change. Therefore, characteristics of ADCs must be considered – at least in part – in conjunction with a whole transmission system.
+
+ADCs are expected to be used in at least two applications:
+
+The first is to use the ADC to compensate for slow changes of link dispersion over time due to environmental effects, such as temperature. This is referred to as a slow change link dispersion application.
+
+The second is to use the ADC to compensate for sudden step changes of link dispersion due to switching or other transmission link re-configuration process. This is referred to as a step change link dispersion application.
+
+A generic configuration of a transmission system with ADC(s) is shown in Figure 5-1. It consists of a transmitter terminal, a receiver terminal and a transmission link in-between with optional line ADC(s). A single-channel system contains a single-channel transmitter and receiver terminal while a multichannel transmitter and receiver terminal is used in a multichannel system.
+
+In the following clauses optical line ADCs (LADC) are distinguished from ADC transmitters and receivers. A black box approach is applied for the line ADCs, ADC transmitters and receivers. Monitoring and control (if present) is included in the black box. Further information concerning the implementation options of all of these devices can be found in Appendix I and details of the underlying technology used in them are contained in Appendix II.
+
+
+
+Figure 5-1: Generic configuration of a transmission system with ADCs. The diagram shows three main components in a horizontal line: a 'Transmitter terminal with optional ADC(s)' on the left, a 'Transmission link with optional line ADC(s)' in the center, and a 'Receiver terminal with optional ADC(s)' on the right. The transmitter terminal is connected to the transmission link via a line labeled 'MPI-S'. The transmission link is connected to the receiver terminal via a line labeled 'MPI-R'.
+
+Figure 5-1 – Generic configuration of a transmission system with ADCs
+
+## 5.1 Line ADCs
+
+Line ADCs have an optical input port and an optical output port and no O-E-O conversion is performed on the signal passing from one to the other. A single-channel line ADC (S-LADC) can handle a single-channel optical signal while a multichannel line ADC (M-LADC) is constructed for a multichannel optical signal. Both types are illustrated schematically in Figures 5-2 and 5-3 respectively.
+
+
+
+Figure 5-2: Reference configuration of a single-channel line ADC (S-LADC). The diagram shows a central rectangular block labeled 'S-LADC'. To its left, an optical fiber (represented by two concentric circles) connects to the block at a point labeled 'R\_S'. To its right, another optical fiber connects from the block at a point labeled 'S\_S'.
+
+Figure 5-2 – Reference configuration of a single-channel line ADC (S-LADC)
+
+
+
+A schematic diagram showing a central rectangular block labeled "M-LADC". To its left, a horizontal line (representing an optical fiber) has a reference point marked with a vertical tick and labeled $R_M$ . To its right, another horizontal line has a reference point marked with a vertical tick and labeled $S_M$ . Both lines terminate in optical connector symbols (two overlapping circles).
+
+Figure 5-3: Reference configuration of a multichannel line ADC (M-LADC).
+
+Figure 5-3 – Reference configuration of a multichannel line ADC (M-LADC)
+
+## **5.2 ADC transmitters**
+
+In the case of ADC transmitters (ADC-Tx), the ADC functionality is embedded in the transmitter black box. There are a number of options of how to realize ADC transmitters. Single-channel ADC transmitters are distinguished from multichannel ADC transmitters.
+
+A schematic diagram of a single-channel ADC transmitter (S-ADC-Tx) is shown in Figure 5-4. A single-channel optical signal outputs at the reference point MPI-S.
+
+
+
+A schematic diagram showing a rectangular block labeled "Single-channel ADC transmitter (S-ADC-Tx)". A horizontal line (optical fiber) exits the right side of the block and terminates in an optical connector symbol. A reference point on this line is marked with a vertical tick and labeled $MPI-S$ .
+
+Figure 5-4: Reference configuration of a single-channel ADC transmitter (S-ADC-Tx).
+
+Figure 5-4 – Reference configuration of a single-channel ADC transmitter
+
+A multichannel ADC transmitter is presented schematically in Figure 5-5. A multichannel optical signal outputs at the reference point MPI-S. There is an ADC before the multiplexer (MUX) and within the transmitter Tx for individual optical channels and/or an ADC after the multiplexer acting on the combined signal from all of the transmitters.
+
+
+
+A schematic diagram of a "Multichannel ADC transmitter" (M-ADC-Tx) shown within a large rectangular box. Inside the box, there are two blocks labeled "(ADC) Tx", with three vertical dots between them indicating multiple channels. These blocks connect to a trapezoidal multiplexer labeled "MUX". The output of the MUX connects to a dashed rectangular block labeled "Optional ADC". The output of the "Optional ADC" block exits the large box and terminates in an optical connector symbol. A reference point on this output line is marked with a vertical tick and labeled $MPI-S$ . The label "M-ADC-Tx" is placed at the bottom right of the large box.
+
+Figure 5-5: Reference configuration of a multichannel ADC transmitter (M-ADC-Tx).
+
+Figure 5-5 – Reference configuration of a multichannel ADC transmitter (M-ADC-Tx)
+
+## **5.3 ADC receivers**
+
+In the case of ADC receivers (ADC-Rx), the ADC functionality is embedded in the receiver black box. There are a number of options of how to realize ADC receivers. Single-channel ADC receivers are distinguished from multichannel ADC receivers.
+
+A schematic diagram of a single-channel ADC receiver (S-ADC-Rx) is shown in Figure 5-6. A single-channel optical signal enters the receiver at the reference point MPI-R. The signal is then detected with ADC functionality.
+
+
+
+The diagram shows an optical fiber input at a reference point labeled MPI-R. This input is connected to a rectangular block labeled "Single-channel ADC receiver (S-ADC-Rx)".
+
+Figure 5-6: Reference configuration of a single-channel ADC receiver (S-ADC-Rx).
+
+**Figure 5-6 – Reference configuration of a single-channel ADC receiver**
+
+A multichannel ADC receiver is presented schematically in Figure 5-7. A multichannel optical signal enters the receiver terminal at the reference point MPI-R. The ADC function may be performed after and/or in front of the DEMUX.
+
+
+
+The diagram shows an optical fiber input at a reference point labeled MPI-R. This input enters a large rectangular block labeled "Multichannel ADC receiver" and "M-ADC-Rx". Inside this block, the signal first passes through a dashed rectangular box labeled "Optional ADC". It then enters a trapezoidal block labeled "DEMUX" (with letters D, E, M, U, X stacked vertically). The output of the DEMUX is connected to a rectangular block labeled "(ADC) Rx". There are three vertical dots between the top and bottom "(ADC) Rx" blocks, indicating multiple parallel channels.
+
+Figure 5-7: Reference configuration of a multichannel ADC receiver (M-ADC-Rx).
+
+**Figure 5-7 – Reference configuration of a multichannel ADC receiver (M-ADC-Rx)**
+
+# 6 Parameters of ADCs
+
+In this clause, parameters for ADCs are presented. Common parameters for all ADC types are summarized in Table 6-1. Additional parameters for the various ADC types are included in Tables 6-2 to 6-7.
+
+**Table 6-1 – Common parameters**
+
+| Parameters | Reference point | Unit | Examples (for illustration of particular applications only) |
+|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------|
+| Fibre type | | | |
+| Line fibre type | MPI-S → R S or MPI-S → R M or S S → MPI-R or S M → MPI-R or MPI-S → MPI-R | – | G.652.A-D, G.653, G.654, G.655, G.656 |
+| Optical signal characteristics | | | |
+| Minimum bit rate | R S or R M or MPI-S or MPI-R | Gbit/s | |
+| Maximum bit rate | R S or R M or MPI-S or MPI-R | Gbit/s | |
+| Modulation format (or "signal format") | R S or R M or MPI-S or MPI-R | – | "Any format", "only NRZ", "NRZ and RZ" |
+
+**Table 6-1 – Common parameters**
+
+| Parameters | Reference point | Unit | Examples (for illustration of particular applications only) |
+|---------------------------------------------------------------------------|----------------------------------------------------------------------|---------|-------------------------------------------------------------|
+| Dispersion-independent parameters of the preceding optical path | | | |
+| Maximum accumulated polarization mode dispersion | $R_S$ or $R_M$ or $MPI-R$ | ps | |
+| Parameters related to dispersion | | | |
+| Minimum dispersion compensation tuning range | $R_S \rightarrow S_S$ or $R_M \rightarrow S_M$ or $MPI-S$ or $MPI-R$ | ps/nm | |
+| Maximum dispersion compensation tuning time a) | $R_S \rightarrow S_S$ or $R_M \rightarrow S_M$ or $MPI-S$ or $MPI-R$ | s | |
+| Minimum rate of change of dispersion compensation parameter b) | $R_S \rightarrow S_S$ or $R_M \rightarrow S_M$ or $MPI-S$ or $MPI-R$ | ps/nm/s | |
+
+a) This parameter must be met for an ADC used in a step change link dispersion application.
+b) This parameter must be met for an ADC used in a slow change link dispersion application.
+
+**Table 6-2 – Parameters for single-channel line ADC (S-LADC)**
+
+| Parameters | Reference point | Unit | Examples (for illustration of particular applications only) |
+|-------------------------------------------------------------------------|-----------------------|------|-------------------------------------------------------------|
+| General single-channel optical parameters | | | |
+| Nominal central optical frequency | $R_S$ | THz | |
+| Maximum central frequency deviation or spectral excursion | $R_S$ | GHz | |
+| Parameters related to optical power | | | |
+| Minimum input power | $R_S$ | dBm | |
+| Maximum input power | $R_S$ | dBm | |
+| Minimum insertion loss (incl. optional OA unit) a) | $R_S \rightarrow S_S$ | dB | |
+| Maximum insertion loss (incl. optional OA unit) a) | $R_S \rightarrow S_S$ | dB | |
+| Maximum insertion loss deviation (incl. optional OA unit) a) | $R_S \rightarrow S_S$ | dB | |
+| Maximum reflectance at the input port | $R_S$ | dB | |
+| Maximum polarization-dependent reflectance at the input port | $R_S$ | dB | |
+| Maximum polarization-dependent loss (PDL) | $R_S \rightarrow S_S$ | dB | |
+| Maximum polarization mode dispersion (PMD) | $R_S \rightarrow S_S$ | ps | |
+| Parameters related to dispersion | | | |
+| Maximum phase ripple | $R_S \rightarrow S_S$ | rad | |
+
+a) If the line ADC includes an optional optical amplifier, additional parameters are required. For details see ITU-T Recs G.661 and G.662.
+
+**Table 6-3 – Parameters for multichannel line ADC (M-LADC)**
+
+| Parameters | Reference point | Unit | Examples (for illustration of particular applications only) |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------|-------------------------------------------------------------|
+| General multichannel optical parameters | | | |
+| Maximum number of channels | $R_M$ | – | |
+| Nominal channel central frequencies | $R_M$ | THz | $191.9 + 0.2 \cdot m$ , $m = 0$ to $19$ |
+| Minimum channel spacing | $R_M$ | GHz | 100, 200 |
+| Maximum central frequency deviation or spectral excursion | $R_M$ | GHz | |
+| Parameters related to optical power | | | |
+| Minimum channel input power | $R_M$ | dBm | |
+| Maximum channel input power | $R_M$ | dBm | |
+| Minimum channel insertion loss (incl. optional OA unit) a) | $R_M \rightarrow S_M$ | dB | |
+| Maximum channel insertion loss (incl. optional OA unit) a) | $R_M \rightarrow S_M$ | dB | |
+| Maximum channel insertion loss deviation (incl. optional OA unit) a) | $R_M \rightarrow S_M$ | dB | |
+| Maximum reflectance at the input port | $R_M$ | dB | |
+| Maximum polarization-dependent reflectance at the input port | $R_M$ | dB | |
+| Maximum polarization mode dispersion (PMD) | $R_M \rightarrow S_M$ | ps | |
+| Maximum polarization-dependent loss (PDL) | $R_M \rightarrow S_M$ | dB | |
+| Parameters related to dispersion | | | |
+| Maximum channel phase ripple | $R_M \rightarrow S_M$ | rad | |
+| a) If the line ADC includes an optional optical amplifier, additional parameters are required. For details see ITU-T Recs G.661 and G.662. | | | |
+
+**Table 6-4 – Parameters for single-channel ADC transmitter (S-ADC-Tx)**
+
+| Parameters | Reference point | Unit | Examples (for illustration of particular applications only) |
+|-----------------------------------------------------------|-----------------|------|-------------------------------------------------------------|
+| General single-channel optical parameters | | | |
+| Nominal central optical frequency | MPI-S | THz | |
+| Maximum central frequency deviation or spectral excursion | MPI-S | GHz | |
+| Parameters related to optical power | | | |
+| Minimum output power | MPI-S | dB | |
+| Maximum output power | MPI-S | dB | |
+| Maximum return loss at the output port | MPI-S | dB | |
+
+**Table 6-5 – Parameters for multichannel ADC transmitter (M-ADC-Tx)**
+
+| Parameters | Reference point | Unit | Examples (for illustration of particular applications only) |
+|-----------------------------------------------------------|-----------------|------|-------------------------------------------------------------|
+| General multichannel optical parameters | | | |
+| Maximum number of channels | MPI-S | – | |
+| Nominal channel central frequencies | MPI-S | THz | $191.9 + 0.2 \cdot m$ , $m = 0$ to $19$ |
+| Minimum channel spacing | MPI-S | GHz | 100, 200 |
+| Maximum central frequency deviation or spectral excursion | MPI-S | GHz | |
+| Parameters related to optical power | | | |
+| Minimum channel output power | MPI-S | dBm | |
+| Maximum channel output power | MPI-S | dBm | |
+| Maximum return loss at the output port | MPI-S | dB | |
+
+**Table 6-6 – Parameters for single-channel ADC receiver (S-ADC-Rx)**
+
+| Parameters | Reference point | Unit | Examples (for illustration of particular applications only) |
+|------------------------------------------------------------------------------------------------------|-----------------|------|-------------------------------------------------------------|
+| General single-channel optical parameters | | | |
+| Nominal central optical frequency | MPI-R | THz | |
+| Maximum central frequency deviation or spectral excursion | MPI-R | GHz | |
+| Parameters related to optical power | | | |
+| Minimum input power | MPI-R | dBm | |
+| Maximum input power | MPI-R | dBm | |
+| Maximum reflectance at the input port | MPI-R | dB | |
+| Maximum polarization-dependent reflectance at the input port | MPI-R | dB | |
+| Single channel transmission system parameters | | | |
+| Maximum OSNR penalty due to chromatic dispersion a) | MPI-R | dB | |
+| Minimum optical signal-to-noise ratio a) | MPI-R | dB | |
+| Maximum ADC receiver sensitivity penalty due to chromatic dispersion b) | MPI-R | dB | |
+| Minimum ADC receiver sensitivity b) | MPI-R | dBm | |
+| a) These parameters must be met for an ADC receiver used in a link containing amplifiers. | | | |
+| b) These parameters must be met for an ADC receiver used in a link without amplifiers. | | | |
+
+**Table 6-7 – Parameters for multichannel ADC receiver (M-ADC-Rx)**
+
+| Parameters | Reference point | Unit | Examples (for illustration of particular applications only) |
+|------------------------------------------------------------------------------------------------------|-----------------|------|-------------------------------------------------------------|
+| General multichannel optical parameters | | | |
+| Maximum number of channels | MPI-R | – | |
+| Nominal channel central frequencies | MPI-R | THz | $191.9 + 0.2 \cdot m$ , $m = 0$ to 19 |
+| Minimum channel spacing | MPI-R | GHz | 100, 200 |
+| Maximum central frequency deviation or spectral excursion | MPI-R | GHz | |
+| Parameters related to optical power | | | |
+| Minimum channel input power | MPI-R | dBm | |
+| Maximum channel input power | MPI-R | dBm | |
+| Maximum reflectance at the input port | MPI-R | dB | |
+| Maximum polarization-dependent reflectance at the input port | MPI-R | dB | |
+| Multichannel transmission system parameters applied to each channel | | | |
+| Maximum OSNR penalty due to chromatic dispersion a) | MPI-R | dB | |
+| Minimum optical signal-to-noise ratio a) | MPI-R | dB | |
+| Maximum channel ADC receiver sensitivity penalty due to chromatic dispersion b) | MPI-R | dB | |
+| Minimum channel ADC receiver sensitivity b) | MPI-R | dBm | |
+| a) These parameters must be met for an ADC receiver used in a link containing amplifiers. | | | |
+| b) These parameters must be met for an ADC receiver used in a link without amplifiers. | | | |
+
+# Appendix I
+
+## Single-channel and multichannel ADC implementation
+
+(This appendix does not form an integral part of this Recommendation)
+
+## I.1 Single or multichannel line ADC implementation
+
+A single-channel line ADC (as shown generically in Figure 5-2) or a multichannel line ADC (as shown generically in Figure 5-3) can be realized by different implementation schemes. One option for a line ADC is presented in Figure I.1 using a tuneable dispersion compensator together with a chromatic dispersion monitor unit. The optical signal passes through the line ADC from the input reference point $R_S$ (or $R_M$ ) to the output reference point $S_S$ (or $S_M$ ). In this implementation, the control signal for the tuneable dispersion compensator is derived from a dispersion monitor that is within the S-LADC or M-LADC black box.
+
+
+
+```
+
+ graph LR
+ Input(( )) -- "R_S or R_M" --> Box
+ subgraph Box [Single or multichannel line ADC]
+ TDC[Tuneable dispersion compensator]
+ CDM[Chromatic dispersion monitor]
+ CDM -- "Control" -.-> TDC
+ TDC -- " " --> CDM
+ Label[S-LADC or M-LADC]
+ end
+ Box -- "S_S or S_M" --> Output(( ))
+
+```
+
+The diagram illustrates the internal structure of a 'Single or multichannel line ADC' (S-LADC or M-LADC). A main horizontal signal path enters from the left at reference point $R_S$ or $R_M$ (marked with a double-circle symbol and a vertical tick) and exits to the right at reference point $S_S$ or $S_M$ (similarly marked). Inside the main box, the signal path passes through a 'Tuneable dispersion compensator' block. After this block, a tap leads to a 'Chromatic dispersion monitor' block. A dashed line labeled 'Control' with an arrow points from the monitor back to the compensator, indicating a local control loop.
+
+Figure I.1: Implementation option A of a single-channel line ADC (S-LADC) or a multichannel line ADC (M-LADC).
+
+**Figure I.1 – Implementation option A of a single-channel line ADC (S-LADC) or a multichannel line ADC (M-LADC)**
+
+An alternative implementation is the use of a feedback signal from other optical node(s) as shown in Figure I.2. The dispersion-related information, e.g., the dispersion value of the whole optical line that the line ADC is compensating, or dispersion-related signal quality information from the optical receiver, which is gathered by a dispersion-related information exchange system within the whole optical line that the line ADC is compensating, is used to adjust the tuneable dispersion compensator to achieve optimized chromatic dispersion compensation performance.
+
+
+
+The diagram shows a large rectangular block labeled "Single or multichannel line ADC" at the top and "S-LADC or M-LADC" at the bottom. Inside this block, a smaller rectangle labeled "Tuneable dispersion compensator" is positioned. A dashed arrow labeled "Control" points from the top section to the compensator. A horizontal line representing an optical path passes through the compensator. To the left of the block, the path is marked with $R_S$ or $R_M$ and an optical connector symbol. To the right, it is marked with $S_S$ or $S_M$ and another optical connector symbol. Outside the block to the right, a dashed line extends from the top section, labeled "Chromatic dispersion related information exchange from/to other optical node(s)".
+
+Figure I.2: Implementation option B of a single-channel line ADC (S-LADC) or a multichannel line ADC (M-LADC).
+
+Figure I.2 – Implementation option B of a single-channel line ADC (S-LADC) or a multichannel line ADC (M-LADC)
+
+## I.2 Single-channel ADC transmitter implementation
+
+A single-channel ADC transmitter (as shown generically in Figure 5-4) can also be realized by different implementation schemes. One option is presented in Figure I.3. The optical signal exits from the ADC transmitter at reference point MPI-S. The feedback signal from/to other optical node(s) shown in Figure I.3 allows the ADC transmitter to operate in an optimized regime. The dispersion-related information, e.g., the dispersion value of the whole optical line that the ADC transmitter is compensating, or dispersion-related signal quality information from the optical receiver, which is gathered by a dispersion-related information exchange system within the whole optical line that the line ADC is compensating, is used to control the dispersion compensation of the tuneable dispersion transmitter to achieve optimized chromatic dispersion compensation performance.
+
+
+
+The diagram shows a large rectangular block labeled "Single-channel ADC transmitter" at the top and "S-ADC-Tx" at the bottom. Inside this block, a smaller rectangle labeled "Tuneable dispersion transmitter" is positioned. A dashed arrow labeled "Control" points from the top section to the transmitter. A horizontal line representing an optical path exits the transmitter and the block, marked with an optical connector symbol and the label "MPI-S". Outside the block to the right, a dashed line extends from the top section, labeled "Chromatic dispersion related information exchange from/to other optical node(s)".
+
+Figure I.3: Implementation option of a single-channel ADC transmitter (S-ADC-Tx).
+
+Figure I.3 – Implementation option of a single-channel ADC transmitter (S-ADC-Tx)
+
+## I.3 Multichannel ADC transmitter implementation
+
+Three implementation options for a multichannel ADC transmitter (as shown generically in Figure 5-5) are illustrated in Figures I.4 to I.6. Option A includes an optical ADC after the multiplexer with conventional transmitters. Option B uses only single-channel ADC transmitters and a multiplexer. Option C uses a combination of both single-channel ADC transmitters and a multichannel optical ADC after the multiplexer.
+
+
+
+Figure I.4 illustrates implementation option A of a multichannel ADC transmitter (M-ADC-Tx). The diagram shows a block labeled "Multichannel ADC transmitter" containing several "Transmitter" units (indicated by three dots) connected to a multiplexer (MUX). The output of the MUX is connected to a "Tuneable dispersion compensator". A dashed line labeled "Control" connects the compensator to the transmitters. The output of the compensator is connected to an optical node (represented by two circles) via an MPI-S interface. To the right of the optical node, text indicates "Chromatic dispersion related information exchange from/to other optical node(s)". The label "M-ADC-Tx" is placed below the MUX.
+
+Figure I.4: Implementation option A of a multichannel ADC transmitter (M-ADC-Tx).
+
+Figure I.4 – Implementation option A of a multichannel ADC transmitter (M-ADC-Tx)
+
+
+
+Figure I.5 illustrates implementation option B of a multichannel ADC transmitter (M-ADC-Tx). The diagram shows a block labeled "Multichannel ADC transmitter" containing several "ADC Transmitter" units (indicated by three dots) connected to a multiplexer (MUX). A dashed line labeled "Control" connects the ADC Transmitters to the MUX. The output of the MUX is connected to an optical node (represented by two circles) via an MPI-S interface. To the right of the optical node, text indicates "Chromatic dispersion related information exchange from/to other optical node(s)". The label "M-ADC-Tx" is placed below the ADC Transmitters.
+
+Figure I.5: Implementation option B of a multichannel ADC transmitter (M-ADC-Tx).
+
+Figure I.5 – Implementation option B of a multichannel ADC transmitter (M-ADC-Tx)
+
+
+
+The diagram shows a 'Multichannel ADC transmitter' block labeled 'M-ADC-Tx'. Inside this block, there are multiple 'ADC Transmitter' units, indicated by three dots between two shown units. These units are connected to a 'MUX' (multiplexer). A 'Tuneable dispersion compensator' is also connected to the MUX output. Dashed lines labeled 'Control' point from the top of the block to the ADC Transmitters and the Tuneable dispersion compensator. Outside the block, to the right, is a section labeled 'Chromatic dispersion related information exchange from/to other optical node(s)'. This section contains an optical fiber symbol and the label 'MPI-S'. A solid line connects the output of the Tuneable dispersion compensator to the MPI-S point.
+
+Figure I.6: Implementation option C of a multichannel ADC transmitter (M-ADC-Tx).
+
+Figure I.6 – Implementation option C of a multichannel ADC transmitter (M-ADC-Tx)
+
+## I.4 Single-channel ADC receiver implementation
+
+Single-channel ADC receivers (as shown generically in Figure 5-6) can be realized by different implementation schemes. One option is a single-channel line tuneable dispersion compensator as presented in Figure I.2 together with a conventional receiver. The optical signal at the reference point MPI-R passes through an optical tuneable dispersion compensator before entering the receiver. The dispersion of the optical tuneable dispersion compensator may be controlled using the dispersion-related signal quality information from the optical receiver allowing the tuneable dispersion compensator to operate in an optimized regime. An alternative option is to use the dispersion value of the whole optical line the S-ADC-Rx is compensating, which is not shown in Figure I.7.
+
+
+
+The diagram shows a 'Single-channel ADC receiver' block labeled 'S-ADC-Rx'. An optical fiber symbol and the label 'MPI-R' are on the left, with a solid line entering the block. Inside the block, the signal first passes through a 'Tuneable dispersion compensator' and then to a 'Receiver'. A dashed line labeled 'Control' points from the Receiver back to the Tuneable dispersion compensator. Above the Receiver, the text 'Chromatic dispersion related information' is present, with a dashed line extending from it to the Receiver. The entire assembly is labeled 'S-ADC-Rx' at the bottom.
+
+Figure I.7: Implementation option A of a single-channel ADC receiver (S-ADC-Rx).
+
+Figure I.7 – Implementation option A of a single-channel ADC receiver (S-ADC-Rx)
+
+An alternative implementation is the use of a receiver including electrical dispersion compensation (EDC) as indicated in Figure I.8. No additional optical device is used for the purpose of chromatic dispersion compensation. Instead, the ADC function is achieved inside the receiver by electrical means.
+
+
+
+The diagram shows an optical fiber input on the left, marked with a circle and a vertical line, labeled 'MPI-R'. This input is connected directly to a rectangular block labeled 'Rx including EDC'.
+
+Figure I.8: Implementation option B of a single-channel ADC receiver (S-ADC-Rx).
+
+**Figure I.8 – Implementation option B of a single-channel ADC receiver (S-ADC-Rx)**
+
+NOTE – Although the two implementations discussed above (optical or EDC) are not specified differently within this Recommendation, in [b-ITU-T G.959.1] applications appropriate to the use of optical dispersion compensators are given a suffix of "D" and applications appropriate to the use of EDC-based compensators are given a suffix of "E".
+
+A combination of the two above implementations is also possible as shown in Figure I.9.
+
+
+
+The diagram shows a large rectangular box labeled 'Single-channel ADC receiver' at the top and 'S-ADC-Rx' at the bottom. Inside this box, an optical fiber input (marked with a circle and vertical line, labeled 'MPI-R') enters from the left and connects to a 'Tuneable dispersion compensator' block. This block is connected to an 'Rx including EDC' block. A dashed line labeled 'Control' originates from the 'Rx including EDC' block and points to the 'Tuneable dispersion compensator' block. Above the 'Tuneable dispersion compensator' block, the text 'Chromatic dispersion related information' is present.
+
+Figure I.9: Implementation option C of a single-channel ADC receiver (S-ADC-Rx).
+
+**Figure I.9 – Implementation option C of a single-channel ADC receiver (S-ADC-Rx)**
+
+### I.5 Multichannel ADC receiver implementation
+
+Similarly to clause I.4, three implementation options for multichannel ADC receivers are illustrated in Figures I.10 to I.12. Option A includes an optical ADC in front of the demultiplexer with conventional receivers. Option B uses only ADC receivers. Option C uses a combination of both an optical ADC in front of the demultiplexer and ADC receivers. In either option B or C the ADC receivers can be implemented either optically or electrically. As for the single-channel case, the dispersion of the ADC function may be controlled using the dispersion-related signal quality information from the optical receiver allowing the ADC to operate in an optimized regime. An alternative option is to use the dispersion value of the whole optical line the M-ADC-Rx is compensating, which is not shown in Figures I.10 to I.12.
+
+
+
+This block diagram illustrates implementation option A for a multichannel ADC receiver (M-ADC-Rx). An optical signal enters from the left through an MPI-R (Multi-Port Interface - Receiver). The signal then passes through a 'Tuneable dispersion compensator'. A dashed line labeled 'Control' originates from the 'Chromatic dispersion related information' block and points to the compensator. The output of the compensator is connected to a demultiplexer (DEMUX), which is represented by a trapezoidal shape with the letters D, E, M, U, X stacked vertically. The DEMUX has multiple output ports, each connected to a 'Receiver' block. The entire assembly, including the compensator, DEMUX, and receivers, is enclosed in a large rectangle labeled 'Multichannel ADC receiver' at the top and 'M-ADC-Rx' at the bottom.
+
+Figure I.10: Implementation option A of a multichannel ADC receiver (M-ADC-Rx).
+
+Figure I.10 – Implementation option A of a multichannel ADC receiver (M-ADC-Rx)
+
+
+
+This block diagram illustrates implementation option B for a multichannel ADC receiver (M-ADC-Rx). An optical signal enters from the left through an MPI-R. The signal is then directly connected to a demultiplexer (DEMUX), represented by a trapezoidal shape with the letters D, E, M, U, X stacked vertically. The DEMUX has multiple output ports, each connected to an 'ADC Receiver' block. The entire assembly, including the DEMUX and ADC receivers, is enclosed in a large rectangle labeled 'Multichannel ADC receiver' at the top and 'M-ADC-Rx' at the bottom.
+
+Figure I.11: Implementation option B of a multichannel ADC receiver (M-ADC-Rx).
+
+Figure I.11 – Implementation option B of a multichannel ADC receiver (M-ADC-Rx)
+
+
+
+The diagram illustrates the internal architecture of a multichannel ADC receiver (M-ADC-Rx). An optical signal enters from the left through an MPI-R (represented by two overlapping circles). The signal then passes through a 'Tuneable dispersion compensator'. A 'Control' signal, indicated by a dashed arrow, is sent from the compensator to a 'Chromatic dispersion related information' block. This block is connected to a series of 'ADC Receiver' blocks via dashed lines. The signal from the compensator also enters a 'DEMUX' (represented by a trapezoid). The output of the DEMUX is connected to the first 'ADC Receiver'. Below the first 'ADC Receiver' are three vertical dots, and below them is another 'ADC Receiver' block. The entire assembly is labeled 'Multichannel ADC receiver' at the top and 'M-ADC-Rx' at the bottom.
+
+Block diagram of a multichannel ADC receiver (M-ADC-Rx) implementation option C. The diagram shows an optical signal entering from the left through an MPI-R (represented by two overlapping circles). The signal then passes through a 'Tuneable dispersion compensator'. A 'Control' signal, indicated by a dashed arrow, is sent from the compensator to a 'Chromatic dispersion related information' block. This block is connected to a series of 'ADC Receiver' blocks via dashed lines. The signal from the compensator also enters a 'DEMUX' (represented by a trapezoid). The output of the DEMUX is connected to the first 'ADC Receiver'. Below the first 'ADC Receiver' are three vertical dots, and below them is another 'ADC Receiver' block. The entire assembly is labeled 'Multichannel ADC receiver' at the top and 'M-ADC-Rx' at the bottom.
+
+Figure I.12 – Implementation option C of a multichannel ADC receiver (M-ADC-Rx)
+
+# Appendix II
+
+## Principles of adaptive dispersion compensation (ADC)
+
+(This appendix does not form an integral part of this Recommendation)
+
+## II.1 Introduction
+
+Chromatic dispersion in a single-mode fibre is a combination of material dispersion and waveguide dispersion and it contributes to pulse broadening and distortion in a digital signal. It does this by inducing a frequency-dependent phase shift of the signal travelling in the fibre, which causes pulse broadening of the optical waveform at the receiver.
+
+For links where the chromatic dispersion would otherwise be too large, a dispersion compensation device is used to compensate the chromatic dispersion of the optical path. At present, various different types of dispersion accommodation (DA) technology are used. For example, passive dispersion compensation (PDC), self-phase modulation (SPM), prechirp (PCH), and dispersion-supported transmission (DST) are included in ITU-T Rec. G.691.
+
+In some applications, the chromatic dispersion of the optical path varies with time or optical network re-configuration to such an extent that, to avoid signal degradations at the receiver, an adaptive dispersion compensator is used to dynamically compensate the chromatic dispersion change of the optical link.
+
+## II.2 Adaptive dispersion compensation applications
+
+ADCs are expected to be used in at least two applications: compensation of slow changes in link dispersion and compensation of step changes in link dispersion.
+
+#### II.2.1 Slow change link dispersion application
+
+In this application, the ADC(s) are used to compensate for slow changes of link dispersion over time due to environmental effects.
+
+One example application is an ultra-long-haul 10-Gbit/s optical transmission system. Since the chromatic dispersion in a fibre varies with time/temperature, the residual dispersion of each channel varies accordingly. If the variation of channel residual dispersion exceeds the dispersion tolerance of the transmitter-receiver pair, a single or multichannel adaptive dispersion compensator is needed to dynamically compensate for the chromatic dispersion change of the optical link.
+
+Similarly, for a long-distance 40-Gbit/s optical transmission system, since the dispersion tolerance of a transmitter-receiver pair is typically much lower than that of 10-Gbit/s systems, dynamically adjusted dispersion compensation may also be needed to compensate for the optical link fibre dispersion variation with time/temperature.
+
+Since the variation of fibre chromatic dispersion with time/temperature is slow, the minimum rate of change of dispersion compensation parameter is used to specify the tuning performance of the ADCs.
+
+#### II.2.2 Step change link dispersion application
+
+In this application, the ADC(s) are used to compensate for sudden step changes of link dispersion due to switching or other transmission link re-configuration process.
+
+One example application is illustrated in Figure II.1. A DWDM optical signal is originally routed through DWDM line segment A. After re-configuration, the route is changed from segment A to segment B. Since the link dispersion of DWDM line segment A is different from DWDM line segment B, a step change of channel residual dispersion occurs. If the step change of channel residual dispersion exceeds the dispersion tolerance of the transmitter-receiver pair, a single or
+
+multichannel adaptive dispersion compensator is needed to dynamically compensate for the chromatic dispersion change of the optical link.
+
+Since the change of dispersion in this case occurs as a step, the maximum dispersion compensation tuning time parameter is used to specify the tuning performance of the ADC(s).
+
+
+
+Figure II.1: Example step change link dispersion application. This diagram shows an optical network path. On the left, multiple transmitters (3R Tx λ1, 3R Tx λ2, ..., 3R Tx λN) are connected to an Optical Multiplexer (OM). The output of the OM passes through a cloud representing a network element and then enters a Packet Xchanger (PXC A). From PXC A, the signal can take one of two paths: the 'Original Route' through 'DWDM Line segment A' or the 'Backup Route' through 'DWDM Line segment B'. Both routes converge at another Packet Xchanger (PXC B). From PXC B, the signal passes through 'DWDM Line segment C' and then enters an Optical Demultiplexer (OD). The output of the OD is distributed to multiple receivers (3R Rx λ1, 3R Rx λ2, ..., 3R Rx λN).
+
+**Figure II.1 – Example step change link dispersion application**
+
+## II.3 Principles of adaptive dispersion compensation
+
+As discussed in clause 5, three types of adaptive dispersion compensator are defined in this Recommendation: pre-compensation, line compensation, and post-compensation. This is illustrated in Figure II.2.
+
+
+
+Figure II.2: Adaptive dispersion compensation principles. This diagram illustrates the signal flow in an optical link. It starts with an 'Optical Transmitter' containing a 'Pre-compensation' block. The signal then passes through a series of optical components, represented by circles with internal lines, to a 'Line compensation' block. This is followed by another optical component and then an 'Optical Receiver' containing a 'Post-compensation' block. A dashed line labeled 'Adaptive Feedback' originates from the 'Post-compensation' block and loops back to both the 'Pre-compensation' and 'Line compensation' blocks, indicating a control mechanism for dynamic adjustment.
+
+**Figure II.2 – Adaptive dispersion compensation principles**
+
+However, as can be seen from the discussion contained in Appendix I, the underlying technology used in these devices for dispersion compensation falls into the three main categories of:
+
+- optical dispersion compensators (which can appear in any of the three locations);
+- receiver-based electronic dispersion compensators;
+- transmitter-based electronic dispersion compensators.
+
+#### II.3.1 Optical dispersion compensators
+
+Several different types of tuneable dispersion compensation technologies can be used, such as fibre Bragg gratings (FBG), virtually-imaged phased-arrays (VIPA), and Gires-Tournois etalons, etc.
+
+FBGs are reflection-based devices created by modulating the refractive index of a fibre core. Dispersion tuning is accomplished by applying strain (usually via a thermal gradient) to a linearly chirped grating. A single FBG can provide wideband, low-loss, flat-top channelized dispersion compensator with high tuning resolution and low tuning speed. A typical FBG tunable dispersion compensation arrangement is illustrated in Figure II.3 [b-PAINCHAUD].
+
+
+
+Figure II.3 – Basic FBG-based compensator structure. The diagram shows an optical input (IN) entering a circulator. The circulator has two output ports: one labeled OUT and another connected to a 'Thermal gradient inducing platform'. Inside the platform, there are two fibre Bragg gratings: 'FBG 1: Negative dispersion' and 'FBG 2: Positive dispersion'.
+
+Figure II.3 – Basic FBG-based compensator structure
+
+VIPAs employ a combination of mirrors and lenses to adjust the optical propagation length [b-SHIRASAKI]. VIPAs have a wideband channelized response, high tuning resolution, moderate tuning speed, and high insertion loss. A typical VIPA-based tunable dispersion compensation arrangement is illustrated in Figure II.4.
+
+
+
+Figure II.4 – Basic VIPA structure. The diagram shows an optical signal entering a circulator. The output of the circulator passes through a 'Collimating lens', then a 'Line-focusing lens', and then a 'Glass plate'. The light then passes through a 'Focusing lens' and hits a '3-dimensional mirror'. The mirror is labeled with 'Shorter λ' and 'Dc > 0' for the upper part and 'Longer λ' and 'Dc < 0' for the lower part. An 'X-axis' is indicated at the bottom right. The output of the circulator is also labeled 'Optical Signal Out'.
+
+Figure II.4 – Basic VIPA structure
+
+The Gires-Tournois etalon has an inherent periodic time delay which can be exploited to provide tunable dispersion compensation by varying the separation of the etalon mirrors. A multichannel flat-top dispersion compensator can be realized using multiple etalons although this approach suffers from high insertion loss. The dispersion is tuned by changing the angle of input light to the etalon. Etalons offer high tuning speed with poor tuning resolution. One arrangement for this type of dispersion compensator is illustrated in Figure II.5.
+
+
+
+Figure II.5 – Basic Gires-Tournois etalon structure. The diagram shows an optical signal entering from the top left through a fiber/coupler, labeled 'Optical Signal In'. The signal path is shown as a line reflecting between a 'Mirror' and an 'Etalon' block. Specifically, it reflects off the mirror, then the etalon, then the mirror again, before exiting through another fiber/coupler labeled 'Optical Signal Out'.
+
+**Figure II.5 – Basic Gires-Tournois etalon structure**
+
+#### II.3.2 Receiver-based electronic dispersion compensators
+
+There are several different types of receiver-based electronic dispersion compensation (EDC) techniques. In all cases, however, an adaptive data processor is used to reduce the inter-symbol interference of the optical to electrical converted signal that was introduced by chromatic dispersion and other non-linear effects. This is shown in Figure II.6.
+
+
+
+Figure II.6 – Basic receiver-based electronic dispersion compensation structure. The diagram shows an input optical signal entering a large box. Inside, it first goes to an 'Optical/Electronic Convertor' block. The output of this block goes to an 'Adaptive Data Processor' block. The output of the processor is labeled 'Receiver Data'. There is a dashed line labeled 'Adaptive Feedback' pointing from the output path back into the 'Adaptive Data Processor' block.
+
+**Figure II.6 – Basic receiver-based electronic dispersion compensation structure**
+
+The different adaptive data processor technologies that are currently being used are: feed forward equalization (FFE), decision feedback equalization (DFE), and maximum likelihood sequence estimation (MLSE).
+
+FFE provides linear ISI equalization. The filter coefficients are tuned to optimize a performance criterion such as minimum mean squared error. This is illustrated in Figure II.7 [b-WATTS]. The boxes labelled $t_s$ are delays which are usually of 0.5- or 1-bit duration.
+
+
+
+Figure II.7 – Basic FFE structure. The diagram shows an input signal V\_RX(t) entering a series of four delay blocks, each labeled t\_s. Taps are taken before the first delay and after each delay block. Each of the five taps is connected to a multiplier (represented by a circle with an X) where it is multiplied by a coefficient C\_0, C\_1, C\_2, C\_3, and C\_4 respectively. The outputs of all five multipliers are fed into a summation block labeled Σ. The output of the summation block is V\_EQ(t). This output is also fed back into a 'Coefficient Adjustment Algorithm' block, which in turn provides control signals to each of the coefficient blocks C\_0 through C\_4.
+
+**Figure II.7 – Basic FFE structure**
+
+In contrast to this, DFE takes the output of the decision circuit and via a tapped delay line adds or subtracts a proportion of the previously detected bits. This is illustrated in Figure II.8 [b-WATTS].
+
+
+
+Figure II.8 – Basic DFE structure. This block diagram shows the input signal V\_Rx(t) entering a summation node (Σ). The output of the summation node goes to a Decision Circuit, which produces the equalized output V\_EQ(kt\_s). A feedback path from the Decision Circuit output passes through a tapped delay line consisting of two delay elements, D\_1 and D\_2, each followed by a delay block t\_s. The outputs of these taps are multiplied by coefficients and then summed at the summation node (Σ) to cancel out intersymbol interference. A Coefficient Adjustment Algorithm block receives the output of the Decision Circuit and adjusts the coefficients for the taps.
+
+Figure II.8 – Basic DFE structure
+
+The two processes described above (FFE and DFE) can also be used together as shown in Figure II.9 which combines the linear FFE equalizer with a non-linear feedback DFE equalizer [b-WATTS].
+
+
+
+Figure II.9 – Combined FFE and DFE structure. This block diagram shows the input signal V\_Rx(t) entering an FFE (Feed-Forward Equalizer) block. The output of the FFE block goes to a summation node (Σ). The output of the summation node goes to a Decision Circuit, which produces the equalized output V\_EQ(kt\_s). A feedback path from the Decision Circuit output passes through a tapped delay line consisting of two delay elements, D\_1 and D\_2, each followed by a delay block t\_s. The outputs of these taps are multiplied by coefficients and then summed at the summation node (Σ) to cancel out intersymbol interference. A Coefficient Adjustment Algorithm block receives the output of the Decision Circuit and adjusts the coefficients for the taps.
+
+Figure II.9 – Combined FFE and DFE structure
+
+MLSE compares the received waveform against a set of expected waveforms over several bits to determine the most likely transmitted bit sequence. This is shown in Figure II.10 [b-WATTS]. The received signal is digitized at a sample rate at least twice the data rate. For an N-bit data sequence, a $2^{N-1}$ state Viterbi decoder determines the most likely data sequence based on the state-based channel model stored in the channel estimator.
+
+
+
+```
+
+graph LR
+ VRX["VRX(t)"] --> ADC
+ ADC --> VD["Viterbi Decoder"]
+ VD --> VEQ["VEQ(kT)"]
+ VD --> CE["Channel Estimator"]
+ CE --> VD
+ CR["Clock Recovery"] --> ADC
+ VRX --> CR
+
+```
+
+Figure II.10 – Basic MLSE structure. A block diagram showing the signal flow: V\_RX(t) enters an ADC. The ADC output goes to a Viterbi Decoder. A Clock Recovery block provides a clock signal to the ADC. The Viterbi Decoder output is V\_EQ(kT). A Channel Estimator block receives feedback from the Viterbi Decoder and provides channel information to it.
+
+**Figure II.10 – Basic MLSE structure**
+
+#### II.3.3 Transmitter-based electronic dispersion compensators
+
+Transmitter-based pre-compensation uses electronic techniques that manipulate both the amplitude and phase of the tuneable transmitter within an adaptive dispersion compensator in order to transmit an optical signal which is distorted at the transmitter, but is undistorted after propagation through the transmission path dispersion. This is illustrated in Figure II.11 [b-McNICOL].
+
+
+
+```
+
+graph LR
+ TD["Transmit Data"] --> TDP["Transmit Data Processor"]
+ TDP --> OM["Optical Modulator"]
+ CL["CW Laser"] --> OM
+ OM --> Out(( ))
+ Out --> AF["Adaptive Feedback"]
+ AF --> TDP
+
+```
+
+Figure II.11 – Basic transmitter-based electronic dispersion compensation structure. A block diagram showing the transmitter components: Transmit Data enters a Transmit Data Processor. The output of the processor goes to an Optical Modulator. A CW Laser also enters the Optical Modulator. The output of the modulator is an optical signal. An Adaptive Feedback block receives information from the optical signal and provides feedback to the Transmit Data Processor.
+
+**Figure II.11 – Basic transmitter-based electronic dispersion compensation structure**
+
+## II.4 Chromatic dispersion monitoring
+
+As can be seen from Figures I.2 to I.12, the dispersion of adaptive dispersion compensators can be controlled according to dispersion-related information, which can be link residual dispersion information or other general dispersion-related performance monitoring information using signal related performance, such as the bit-error ratio (BER), eye opening or Q factor, etc.
+
+As can be seen from Figure I.1, some configurations that employ adaptive dispersion compensators incorporate a dispersion monitoring function. Three categories of methods for doing this are:
+
+- monitoring the electrical spectrum;
+- monitoring the amplitude of a pilot tone;
+- monitoring the time delay between the upper and lower sidebands.
+
+#### II.4.1 Monitoring the electrical spectrum
+
+When an optical signal is detected by a photodiode, the square-law detection process plays a useful role in identifying the frequency components of the optical signal which have been reduced in magnitude or nullified due to chromatic dispersion. The amplitude (power) change within a specific frequency band is directly related to the amount of chromatic dispersion that the signal has been subjected to within that frequency band [b-DEVAUX]. The electrical spectra of optical signals with different chromatic dispersions $|D_n|$ are shown in Figure II.12, where $|D_1| < |D_2| < |D_3|$ . Since the power within the specific frequency band $\Delta f$ uniquely corresponds to the specific chromatic dispersion $|D_n|$ , the required monitoring signal can be obtained.
+
+
+
+Figure II.12: Electrical spectrum of the detected signal. The graph plots Normalized power spectral density (dB) on the y-axis (0 to 1) against Frequency (Hz) on the x-axis (0 to 12 x 10^10). Three curves are shown: D1 (dashed line), D2 (dash-dot line), and D3 (solid line). All curves start at 1.0 dB at 0 Hz. D3 (solid) drops to a minimum of ~0.1 dB at ~7.5 x 10^10 Hz. D2 (dash-dot) drops to ~0.1 dB at ~8.5 x 10^10 Hz. D1 (dashed) drops to ~0.1 dB at ~9.5 x 10^10 Hz. A horizontal double-headed arrow labeled Δf is positioned between two vertical lines at approximately 4.5 and 6.5 x 10^10 Hz.
+
+**Figure II.12 – Electrical spectrum of the detected signal**
+
+#### **II.4.2 Monitoring the amplitude of a pilot tone**
+
+By adding a pilot tone to the optical signal at an appropriate frequency, the same phenomenon discussed in clause II.4.1 can be monitored by simply measuring the level of the pilot tone at the detector output using a narrow electrical filter [b-PETERSEN].
+
+Figure II.13 shows the observed electrical power spectrum for different accumulated dispersions where the power of tone-n is decreasing with the chromatic dispersion increasing from (a) to (c).
+
+
+
+Figure II.13: Electrical spectrum of the detected signal with pilot tone. The figure consists of three subplots (a), (b), and (c) showing normalized power spectral density (dB) versus frequency (Hz) x 10^10. Each plot shows a deep null at approximately 7.5 x 10^10 Hz. (a) shows 'Tone-1' at approximately 6.5 x 10^10 Hz with a peak power of about 0.95 dB. (b) shows 'Tone-2' at approximately 6.5 x 10^10 Hz with a peak power of about 0.8 dB. (c) shows 'Tone-3' at approximately 6.5 x 10^10 Hz with a peak power of about 0.6 dB.
+
+**Figure II.13 – Electrical spectrum of the detected signal with pilot tone**
+
+#### **II.4.3 Monitoring the time delay between the upper and lower sidebands**
+
+This scheme uses a filter to select the upper and lower vestigial sideband (VSB) signal in the data and monitors the relative clock phase-shift $\Delta\phi$ caused by dispersion [b-QIAN]. VSB filtering is implemented by tuning the filter apart from the spectral centre of the signal as shown in Figure II.14 for an RZ signal. Since the two sidebands occupy different wavelength ranges, fibre chromatic dispersion induces a relative group delay, and thus, a small clock phase-shift between the lower and upper VSB signals.
+
+
+
+The figure consists of four subplots arranged in a 2x2 grid, illustrating dispersion monitoring using VSB filters.
+
+- Top-left plot:** Optical power (a.u.) vs Frequency (a.u.). It shows two curves: a solid line labeled "VSB-L" and a dashed line labeled "Optical carrier". The "Optical carrier" curve is centered at 0 a.u. frequency, while the "VSB-L" curve is shifted to the left, peaking at approximately -2 a.u. frequency.
+- Top-right plot:** Intensity (a.u.) vs Time (a.u.) for "Bits (11010)". The plot shows a sequence of pulses corresponding to the bit sequence 11010. The x-axis ranges from 0 to 15 a.u. time, and the y-axis ranges from 0 to 1.5 a.u. intensity.
+- Bottom-left plot:** Optical power (a.u.) vs Frequency (a.u.). It shows two curves: a solid line labeled "VSB-U" and a dashed line labeled "Optical carrier". The "Optical carrier" curve is centered at 0 a.u. frequency, while the "VSB-U" curve is shifted to the right, peaking at approximately 2 a.u. frequency.
+- Bottom-right plot:** Intensity (a.u.) vs Time (a.u.). This plot shows the same pulse sequence as the top-right plot but with a phase shift. A horizontal arrow indicates a time delay, and a vertical double-headed arrow between the peaks of the third pulse in the top-right and bottom-right plots is labeled $\Delta\phi$ , representing the phase difference.
+
+G.667(06)\_FII.14
+
+Four plots showing optical power and intensity over frequency and time for dispersion monitoring using VSB filters. The top-left plot shows Optical power (a.u.) vs Frequency (a.u.) for VSB-L and Optical carrier. The top-right plot shows Intensity (a.u.) vs Time (a.u.) for Bits (11010). The bottom-left plot shows Optical power (a.u.) vs Frequency (a.u.) for VSB-U. The bottom-right plot shows Intensity (a.u.) vs Time (a.u.) with a phase shift Δφ.
+
+**Figure II.14 – Dispersion monitoring using VSB filters**
+
+# Bibliography
+
+- [b-ITU-T G.959.1] ITU-T Recommendation G.959.1 (2006), *Optical transport network physical layer interfaces*.
+- [b-ITU-T G.Sup39] ITU-T G-series Supplement 39 (2006), *Optical system design and engineering considerations*.
+- [b-DEVAUX] DEVAUX (F.), SOREL (Y.), Kerdiles (J.F.), Simple measurement of fibre dispersion and of chirp parameter of intensity modulated light emitter. *Journal of Lightwave Technology*, 1993. 11(12): pp. 1937-1940.
+- [b-McNICOL] McNicol (J.), O'Sullivan (M.), Roberts (K.), Comeau (A.), Mcghan (D.), Strawczynski (L.), Electrical Domain Compensation of Optical Dispersion, *OThJ3, OFC 2005*.
+- [b-PAINCHAUD] Painchaud (Y.), Lapointe (M.), Guy (M.), Slope-matched tunable dispersion compensation over the full C-band based on fiber Bragg gratings, *ECOC 2004*.
+- [b-PETERSEN] Petersen (M.N.) *et al*, Dispersion monitoring and compensation using a single inband subcarrier tone. *OFC 2001*, Volume 3, 2001 Page(s): WH4-1 to WH4-3 Vol. 3.
+- [b-QIAN] Qian (Y.) *et al*, Chromatic dispersion monitoring technique using sideband optical filtering and clock phase-shift detection. *Journal of Lightwave Technology*, 2002. 20(12): pp. 2267-2271.
+- [b-SHIRASAKI] Shirasaki (M.), Chromatic-dispersion compensator using virtually imaged phased array, *IEEE Photonics Technol. Lett.*, Vol. 9, pp. 1598-1600, 1997.
+- [b-WATTS] Watts (P.M.), Mikhailov (V.), Savory (S.), Glick (M.), Bayvel (P.), Killey (R.I.), Electronic signal processing techniques for compensation of chromatic dispersion, *NOC 2005*.
+
+
+
+
+
+## **SERIES OF ITU-T RECOMMENDATIONS**
+
+| | |
+|-----------------|---------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/G/T-REC-G.691-200603-I_PDF-E/07c5a1c0fddd7da92a8427f5af840ffa_img.jpg b/marked/G/T-REC-G.691-200603-I_PDF-E/07c5a1c0fddd7da92a8427f5af840ffa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..789f88f829df9a2dc8be775e2243508e303ebf5a
--- /dev/null
+++ b/marked/G/T-REC-G.691-200603-I_PDF-E/07c5a1c0fddd7da92a8427f5af840ffa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fde840cccadf303da2f7d3096fc9618402803394caf4fbda39b34a32c7af2434
+size 34046
diff --git a/marked/G/T-REC-G.691-200603-I_PDF-E/157e8c1d80a02c8eee893c2ea60a77a8_img.jpg b/marked/G/T-REC-G.691-200603-I_PDF-E/157e8c1d80a02c8eee893c2ea60a77a8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a885205006e6ecec9e9bf334bfad225fbe6cd824
--- /dev/null
+++ b/marked/G/T-REC-G.691-200603-I_PDF-E/157e8c1d80a02c8eee893c2ea60a77a8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e7ce4d96867ce0ed0442fcc56262e69d284eb3f4bd5f6330090a0c3d23b24f8b
+size 46309
diff --git a/marked/G/T-REC-G.691-200603-I_PDF-E/183007754364096b2d89f42200cf870f_img.jpg b/marked/G/T-REC-G.691-200603-I_PDF-E/183007754364096b2d89f42200cf870f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..360d2f539821cf6f219204bb31544dc7200ec9be
--- /dev/null
+++ b/marked/G/T-REC-G.691-200603-I_PDF-E/183007754364096b2d89f42200cf870f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a8dd372cb0bc881a39419387e6ce547a588227b2bd2d76c0e2beb25227f02bef
+size 21807
diff --git a/marked/G/T-REC-G.691-200603-I_PDF-E/24a89bcaba787f2bc1721356480a4a01_img.jpg b/marked/G/T-REC-G.691-200603-I_PDF-E/24a89bcaba787f2bc1721356480a4a01_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9f6e8e6ca65ac73705c34791e3f007d70c1b2f0b
--- /dev/null
+++ b/marked/G/T-REC-G.691-200603-I_PDF-E/24a89bcaba787f2bc1721356480a4a01_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bcc946822e71f8fe6a3146204eb1b9900fc46569dbc50b907fac7a77fbf0d999
+size 39713
diff --git a/marked/G/T-REC-G.691-200603-I_PDF-E/4bff5f22997753bcf1997c715118012d_img.jpg b/marked/G/T-REC-G.691-200603-I_PDF-E/4bff5f22997753bcf1997c715118012d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b132c03d14d5fa2e7146cbb2fa139e982ec21be8
--- /dev/null
+++ b/marked/G/T-REC-G.691-200603-I_PDF-E/4bff5f22997753bcf1997c715118012d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:69fa708b81bdce3bc0e72aced8ca467422dc0cfef6e1fcc114c18a611a09be36
+size 36740
diff --git a/marked/G/T-REC-G.691-200603-I_PDF-E/54b5c00e104d6abae06037df2ce1f075_img.jpg b/marked/G/T-REC-G.691-200603-I_PDF-E/54b5c00e104d6abae06037df2ce1f075_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..09f0715858cf6e45ef1121f74fbbc7cdf0e1968e
--- /dev/null
+++ b/marked/G/T-REC-G.691-200603-I_PDF-E/54b5c00e104d6abae06037df2ce1f075_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ac7eb34175d8b6a4bdf2ee6f4f42a9972897e83633635512a4c16e296e5d7cc
+size 27996
diff --git a/marked/G/T-REC-G.691-200603-I_PDF-E/7fdd9eacc17f06e094850c6755b47418_img.jpg b/marked/G/T-REC-G.691-200603-I_PDF-E/7fdd9eacc17f06e094850c6755b47418_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b1b1ccaa483f0c6b614bc7fba592d74d9fb6a7e5
--- /dev/null
+++ b/marked/G/T-REC-G.691-200603-I_PDF-E/7fdd9eacc17f06e094850c6755b47418_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1bd678634279bfc2220abdec01d2e53c074bb0119c6fbe177ecaf9ad82df2a27
+size 38836
diff --git a/marked/G/T-REC-G.691-200603-I_PDF-E/853ef5420f0432e626e83987e3f38a0b_img.jpg b/marked/G/T-REC-G.691-200603-I_PDF-E/853ef5420f0432e626e83987e3f38a0b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a05fe9a57e0590a570ec5c9f313323e5dce27e3b
--- /dev/null
+++ b/marked/G/T-REC-G.691-200603-I_PDF-E/853ef5420f0432e626e83987e3f38a0b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5bfc2523572fa7d485bb3005dd7adc50fa0c3e0656a7e3f9f721e2a485b38d97
+size 34497
diff --git a/marked/G/T-REC-G.691-200603-I_PDF-E/9db774ce7e2ae9d89f439a41156214dd_img.jpg b/marked/G/T-REC-G.691-200603-I_PDF-E/9db774ce7e2ae9d89f439a41156214dd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ba04dc78126946c67212923d99162284a2bf15e6
--- /dev/null
+++ b/marked/G/T-REC-G.691-200603-I_PDF-E/9db774ce7e2ae9d89f439a41156214dd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f7db7d931f455e21a4915de58f5b7c94f229f6a43b52a160f0337c1e0745743d
+size 37450
diff --git a/marked/G/T-REC-G.691-200603-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/G/T-REC-G.691-200603-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..771e88aaca10f12a428682a1eb5ee5e10afed629
--- /dev/null
+++ b/marked/G/T-REC-G.691-200603-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a98d389c10fb6a8d4132427bac06b49ce9398a240641efa51bca829863d9335b
+size 36221
diff --git a/marked/G/T-REC-G.691-200603-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/G/T-REC-G.691-200603-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c
--- /dev/null
+++ b/marked/G/T-REC-G.691-200603-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3
+size 4338
diff --git a/marked/G/T-REC-G.691-200603-I_PDF-E/ad29805cd4f64ad2828e14feb66de664_img.jpg b/marked/G/T-REC-G.691-200603-I_PDF-E/ad29805cd4f64ad2828e14feb66de664_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f329a51891454a1410e3c990cdaae599b0dceb5b
--- /dev/null
+++ b/marked/G/T-REC-G.691-200603-I_PDF-E/ad29805cd4f64ad2828e14feb66de664_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2be43a4c07cf9e78f49336a5aeda7d972d658c26a0916da4e6242a5d8bbfc7b9
+size 31219
diff --git a/marked/G/T-REC-G.691-200603-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/G/T-REC-G.691-200603-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..daa66f709cfb46f2898111cf31fcf8ef6ba631f5
--- /dev/null
+++ b/marked/G/T-REC-G.691-200603-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3e53094d61fe0c03275eeb50d76be81e33308e17ede036da8f0757a84fa804f6
+size 28629
diff --git a/marked/G/T-REC-G.691-200603-I_PDF-E/bd4a5cf22b8d8060c4bf3577beb30df8_img.jpg b/marked/G/T-REC-G.691-200603-I_PDF-E/bd4a5cf22b8d8060c4bf3577beb30df8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6349d69ea434895c084a365ef4595beafc91a733
--- /dev/null
+++ b/marked/G/T-REC-G.691-200603-I_PDF-E/bd4a5cf22b8d8060c4bf3577beb30df8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:950c1a88942ce46e6ea343023d41eb8972eb732466f6cfbb3a4e05d96429cee5
+size 39107
diff --git a/marked/G/T-REC-G.691-200603-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg b/marked/G/T-REC-G.691-200603-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e5d20532c485d914bd4eeb7d440320c147344982
--- /dev/null
+++ b/marked/G/T-REC-G.691-200603-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3f4015c63abb7aace038a5dbe166364de63bfb7259ef35b0a12c1c13240c86e0
+size 49576
diff --git a/marked/G/T-REC-G.691-200603-I_PDF-E/raw.md b/marked/G/T-REC-G.691-200603-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..578403610c034e9e92cf8cd222e8f28e568866aa
--- /dev/null
+++ b/marked/G/T-REC-G.691-200603-I_PDF-E/raw.md
@@ -0,0 +1,1430 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**G.691**
+
+(03/2006)
+
+SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
+DIGITAL SYSTEMS AND NETWORKS
+
+Transmission media characteristics – Characteristics of
+optical components and subsystems
+
+---
+
+**Optical interfaces for single channel STM-64
+and other SDH systems with optical amplifiers**
+
+ITU-T Recommendation G.691
+
+# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS**
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 |
+| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 |
+| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 |
+| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 |
+| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.600–G.699 |
+| General | G.600–G.609 |
+| Symmetric cable pairs | G.610–G.619 |
+| Land coaxial cable pairs | G.620–G.629 |
+| Submarine cables | G.630–G.649 |
+| Optical fibre cables | G.650–G.659 |
+| Characteristics of optical components and subsystems | G.660–G.699 |
+| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 |
+| DIGITAL NETWORKS | G.800–G.899 |
+| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 |
+| QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER-RELATED ASPECTS | G.1000–G.1999 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.6000–G.6999 |
+| DATA OVER TRANSPORT – GENERIC ASPECTS | G.7000–G.7999 |
+| ETHERNET OVER TRANSPORT ASPECTS | G.8000–G.8999 |
+| ACCESS NETWORKS | G.9000–G.9999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## **ITU-T Recommendation G.691**
+
+# **Optical interfaces for single channel STM-64 and other SDH systems with optical amplifiers**
+
+# **Summary**
+
+This Recommendation provides parameters and values for optical interfaces of single-channel long-haul STM-4, STM-16 and STM-64 systems utilizing optical preamplifiers and/or optical booster amplifiers. Furthermore, it provides optical interface parameters for single-channel STM-64 intra-office and short-haul systems without optical amplification
+
+## **Source**
+
+ITU-T Recommendation G.691 was approved on 29 March 2006 by ITU-T Study Group 15 (2005-2008) under the ITU-T Recommendation A.8 procedure.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2006
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+# CONTENTS
+
+| | | Page |
+|-------------|--------------------------------------------------------------------------|------|
+| 1 | Scope ..... | 1 |
+| 2 | References..... | 1 |
+| 3 | Terms and definitions ..... | 2 |
+| 3.1 | Definitions ..... | 2 |
+| 3.2 | Terms defined in other Recommendations..... | 2 |
+| 4 | Abbreviations..... | 3 |
+| 5 | Classification of optical interfaces..... | 4 |
+| 5.1 | Applications..... | 4 |
+| 5.2 | Reference and physical configurations..... | 6 |
+| 6 | Parameter definitions ..... | 7 |
+| 6.1 | System operating wavelength range..... | 7 |
+| 6.2 | Transmitter ..... | 7 |
+| 6.3 | Optical path ..... | 10 |
+| 6.4 | Receiver..... | 13 |
+| 7 | Optical parameter values ..... | 14 |
+| 8 | Optical engineering approach..... | 20 |
+| 8.1 | Design assumptions ..... | 20 |
+| 8.2 | Non-linearities ..... | 21 |
+| 8.3 | Dispersion accommodation ..... | 21 |
+| 8.4 | Stand-alone amplifiers..... | 24 |
+| 8.5 | Upgradability considerations..... | 24 |
+| 8.6 | Optical safety considerations..... | 25 |
+| Annex A | – Extinction ratio and eye mask penalties ..... | 25 |
+| A.1 | Measurement parameters..... | 25 |
+| A.2 | Extinction ratio penalty ..... | 26 |
+| A.3 | Eye mask penalty..... | 26 |
+| A.4 | Receiver sensitivity ..... | 27 |
+| Appendix I | – Polarization mode dispersion..... | 27 |
+| I.1 | The statistical distribution of PMD ..... | 27 |
+| I.2 | The path penalty due to PMD..... | 29 |
+| Appendix II | – Description of SPM as dispersion accommodation..... | 30 |
+| II.1 | SPM basics ..... | 30 |
+| II.2 | Using self phase modulation as a dispersion accommodation technique..... | 30 |
+| II.3 | SPM-breakdown..... | 31 |
+| II.4 | Optical parameter values for applications ..... | 31 |
+| II.5 | Source type ..... | 31 |
+| II.6 | Eye pattern mask ..... | 31 |
+
+| | Page |
+|------------------------------------------------------------------------------------------------|------|
+| II.7 Receiver ..... | 31 |
+| Appendix III – Dispersion accommodation by means of DST ..... | 32 |
+| III.1 Introduction ..... | 32 |
+| III.2 Principle of the DST technique ..... | 32 |
+| III.3 Optical receiver eye pattern mask after dispersive fibre transmission ..... | 33 |
+| III.4 Parameter definitions ..... | 34 |
+| III.5 Optical parameter values ..... | 37 |
+| Appendix IV – Measurement of the chirp parameter $\alpha$ of the optical transmit signal ..... | 38 |
+| IV.1 Measurement set-up ..... | 38 |
+| IV.2 Technical requirements for the measuring equipment ..... | 39 |
+| IV.3 Calibration ..... | 39 |
+| IV.4 Measurement procedure ..... | 40 |
+| IV.5 Data processing ..... | 40 |
+| IV.6 Examples and interpretation of data ..... | 41 |
+| Appendix V – Upgradability considerations ..... | 42 |
+
+# Optical interfaces for single channel STM-64 and other SDH systems with optical amplifiers
+
+# 1 Scope
+
+The purpose of this Recommendation is to provide optical interface specifications to enable transverse (multi-vendor) compatibility of single-channel STM-4, STM-16, and STM-64 inter-office systems using optical preamplifiers and/or optical booster amplifiers. Specifications to enable transversely compatible single-channel STM-64 intra-office and short-haul systems not requiring optical amplification are also included.
+
+The use of line amplifiers is not within the scope of this Recommendation.
+
+This Recommendation is based on the use of one fibre per direction.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [1] ITU-T Recommendation G.652 (2005), *Characteristics of a single-mode optical fibre and cable*.
+- [2] ITU-T Recommendation G.653 (2003), *Characteristics of a dispersion-shifted single-mode optical fibre and cable*.
+- [3] ITU-T Recommendation G.655 (2006), *Characteristics of a non-zero dispersion-shifted single-mode optical fibre and cable*.
+- [4] ITU-T Recommendation G.662 (2005), *Generic characteristics of optical amplifier devices and subsystems*.
+- [5] ITU-T Recommendation G.663 (2000), *Application related aspects of optical amplifier devices and subsystems*.
+- [6] ITU-T Recommendation G.664 (2006), *Optical safety procedures and requirements for optical transport systems*.
+- [7] ITU-T Recommendation G.671 (2005), *Transmission characteristics of optical components and subsystems*.
+- [8] ITU-T Recommendation G.693 (2005), *Optical interfaces for intra-office systems*.
+- [9] ITU-T Recommendation G.707/Y.1322 (2003), *Network node interface for the synchronous digital hierarchy (SDH)*.
+
+- [10] ITU-T Recommendation G.955 (1996), *Digital line systems based on the 1544 kbit/s and the 2048 kbit/s hierarchy on optical fibre cables.*
+- [11] ITU-T Recommendation G.957 (2006), *Optical interfaces for equipments and systems relating to the synchronous digital hierarchy.*
+- [12] ITU-T Recommendation G.959.1 (2006), *Optical transport network physical layer interfaces.*
+
+# 3 Terms and definitions
+
+## 3.1 Definitions
+
+This Recommendation defines the following terms:
+
+- 3.1.1 main (optical) path:** The fibre plant between the S point of the transmitter equipment and the R point of the receiver equipment. The main path does not include any auxiliary paths.
+- 3.1.2 main path interfaces:** The interfaces to the fibre plant specified in this Recommendation.
+- 3.1.3 auxiliary (optical) path:** The optical interconnection between a non-amplified transmitter or receiver and an (stand-alone) optical pre- or booster-amplifier device. An auxiliary path is not included in the main path.
+- 3.1.4 (optical) transponder:** A transmitter-receiver combination with or without pulse shaping and retiming that converts an optical signal into another optical signal by a conversion into the electrical domain.
+
+## 3.2 Terms defined in other Recommendations
+
+This Recommendation uses the following terms defined in other ITU-T Recommendations:
+
+| | |
+|----------------------------------|--------------------|
+| Booster amplifier: | (ITU-T Rec. G.662) |
+| Erbium doped fibre amplifier: | (ITU-T Rec. G.661) |
+| Joint engineering: | (ITU-T Rec. G.957) |
+| Longitudinal compatibility: | (ITU-T Rec. G.955) |
+| Optical amplifier device: | (ITU-T Rec. G.662) |
+| Optical amplifier subsystem: | (ITU-T Rec. G.662) |
+| Optical amplifier: | (ITU-T Rec. G.662) |
+| Optical fibre amplifier: | (ITU-T Rec. G.662) |
+| Optical return loss: | (ITU-T Rec. G.957) |
+| Optically amplified receiver: | (ITU-T Rec. G.662) |
+| Optically amplified transmitter: | (ITU-T Rec. G.662) |
+| Pre-amplifier: | (ITU-T Rec. G.662) |
+| S/R reference points: | (ITU-T Rec. G.955) |
+| Transverse compatibility: | (ITU-T Rec. G.957) |
+
+# 4 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|------|-----------------------------------|
+| APD | Avalanche Photo Diode |
+| ASE | Amplified Spontaneous Emission |
+| ASK | Amplitude Shift Keying |
+| BER | Bit Error Ratio |
+| DA | Dispersion Accommodation |
+| DGD | Differential Group Delay |
+| DST | Dispersion Supported Transmission |
+| EX | Extinction ratio |
+| FEC | Forward Error Correction |
+| ffs | For Further Study |
+| FM | Frequency Modulation |
+| FSK | Frequency Shift Keying |
+| FSR | Free Spectral Range |
+| FWHM | Full Width at Half Maximum |
+| I | Intra-Office |
+| IM | Intensity Modulation |
+| L | Long-Haul |
+| MLM | Multi-Longitudinal Mode |
+| MPI | Main Path Interface |
+| MPN | Mode Partition Noise |
+| NA | Not Applicable |
+| NRZ | Non-Return to Zero |
+| ORL | Optical Return Loss |
+| PCH | Prechirp |
+| PDC | Passive Dispersion Compensator |
+| PIN | "p-type" – intrinsic – "n-type" |
+| PMD | Polarization Mode Dispersion |
+| PRBS | Pseudo-Random Binary Sequence |
+| PSP | Principal State of Polarization |
+| RMS | Root Mean Square |
+| S | Short-Haul |
+| SDH | Synchronous Digital Hierarchy |
+| SLM | Single-Longitudinal Mode |
+| SMSR | Side Mode Suppression Ratio |
+| SNR | Signal to Noise Ratio |
+
+| | |
+|-------|-----------------------------------------|
+| SOP | State of Polarization |
+| SPM | Self Phase Modulation |
+| STM-N | Synchronous Transport Module of order N |
+| U | Ultra Long-Haul |
+| V | Very Long-Haul |
+| WDM | Wavelength Division Multiplex |
+
+# 5 Classification of optical interfaces
+
+## 5.1 Applications
+
+This Recommendation defines optical interfaces for single-channel inter-office line systems for terrestrial long-distance applications from STM-4 to STM-64. It is an extension of ITU-T Rec. G.957 based on the addition of optical amplifiers and the STM-64 data rate. Systems with line amplifiers are not within the scope of this Recommendation.
+
+The definitions of the application codes are extended from ITU-T Rec. G.957 as:
+
+Application – STM level.suffix number,
+
+where "application" corresponds to the target distance: I- (Intra-office), S- (Short-haul), L- (Long-haul), V- (Very long-haul), and U- (Ultra long-haul).
+
+The suffix number denotes:
+
+- 1 the use of nominally 1310 nm sources on G.652 (standard) fibre;
+- 2 the use of nominally 1550 nm sources on G.652 fibre;
+- 3 the use of nominally 1550 nm sources on G.653 (dispersion shifted) fibre;
+- 5 the use of nominally 1550 nm sources on G.655 (non-zero dispersion shifted) fibre.
+
+For some I-64 codes an "r" is added after the suffix number to indicate a reduced target distance. These application codes which belong to the intra-office family are dispersion limited. The same target distance can be achieved by means of other technological solutions, which are for further study (e.g., parallel interface approach).
+
+The target distances are based on approximately 40 km intervals for 1550 nm and 20 km intervals for 1310 nm, except for the very short reach and intra-office applications. The target distances are to be used for classification only and not for specification. They are estimated using the assumption of 0.275 dB/km installed fibre loss including splices and cable margins for 1550 nm systems, and 0.55 dB/km for 1310 nm systems. From a practical point of view, attenuation spans of 11 dB/20 km at 1310 nm and 11 dB/40 km at 1550 nm are defined, except for very short reach and intra-office applications. In practice, these values may not apply to all fibre cables, in which case the realistic distances that can be reached may be shorter.
+
+The primary specifications are the attenuation range and the maximum dispersion tolerance of the system. The main use of the target distance is to define the dispersion tolerance, which is calculated as the maximum fibre dispersion times the target distance. This gives added tolerance to the systems, as well as enabling the full utilization of low attenuation fibre plants. Tables 1a, 1b and 1c summarize the application codes described in this Recommendation.
+
+**Table 1a/G.691 – Classification of optical interfaces based on application and showing I application codes**
+
+| Applications | | | | | | |
+|--------------------------------|------------|-------------|-------------|----------|----------|----------|
+| Source nominal wavelength [nm] | 1310 | 1310 | 1550 | 1550 | 1550 | 1550 |
+| Fibre type | G.652 | G.652 | G.652 | G.652 | G.653 | G.655 |
+| Targ dist. [km] | 0.6 | 2 | 2 | 25 | 25 | 25 |
+| STM-64 | I-64.1r | I-64.1 | I-64.2r | I-64.2 | I-64.3 | I-64.5 |
+| Parameters given in | G.693 | G.693 | G.693 | G.959.1 | G.959.1 | G.959.1 |
+| As code | VSR600-2R1 | VSR2000-2R1 | VSR2000-2L2 | P1I1-2D2 | P1I1-2D3 | P1I1-2D5 |
+
+NOTE 1 – The target distances are approximate and are to be used for classification only and not for specification.
+NOTE 2 – I, S and L codes for STM-1, -4 and -16 are defined in ITU-T Rec. G.957.
+
+**Table 1b/G.691 – Classification of optical interfaces based on application and showing S and L application codes**
+
+| Applications | | | | | | | |
+|--------------------------------|----------|----------|----------|----------|----------|----------|----------|
+| Source nominal wavelength [nm] | 1310 | 1550 | 1550 | 1550 | 1310 | 1550 | 1550 |
+| Fibre type | G.652 | G.652 | G.653 | G.655 | G.652 | G.652 | G.653 |
+| Targ dist. [km] | 20 | 40 | 40 | 40 | 40 | 80 | 80 |
+| STM-64 | S-64.1 | S-64.2 | S-64.3 | S-64.5 | L-64.1 | L-64.2 | L-64.3 |
+| Parameters given in | G.959.1 | G.959.1 | G.959.1 | G.959.1 | G.959.1 | Table 5c | Table 5c |
+| As code | P1S1-2D1 | P1S1-2D2 | P1S1-2D3 | P1S1-2D5 | P1L1-2D1 | | |
+
+NOTE 1 – The target distances are approximate and are to be used for classification only and not for specification.
+NOTE 2 – I, S and L codes for STM-1, -4 and -16 are defined in ITU-T Rec. G.957.
+
+**Table 1c/G.691 – Classification of optical interfaces based on application and showing V and U application codes**
+
+| Applications | | | | | |
+|--------------------------------|---------|----------|----------|----------|----------|
+| Source nominal wavelength [nm] | 1310 | 1550 | 1550 | 1550 | 1550 |
+| Fibre type | G.652 | G.652 | G.653 | G.652 | G.653 |
+| Targ dist. [km] | 60 | 120 | 120 | 160 | 160 |
+| STM-1 | – | – | – | – | – |
+| STM-4 | V-4.1 | V-4.2 | V-4.3 | U-4.2 | U-4.3 |
+| Parameters given in | Table 3 | Table 3 | Table 3 | Table 3 | Table 3 |
+| Targ dist. [km] | 60 | 120 | 120 | 160 | 160 |
+| STM-16 | – | V-16.2 | V-16.3 | U-16.2 | U-16.3 |
+| Parameters given in | | Table 4 | Table 4 | G.959.1 | G.959.1 |
+| As code | | | | PIU1-1A2 | PIU1-1A3 |
+| Targ dist. [km] | 60 | 120 | 120 | | |
+| STM-64 | – | V-64.2 | V-64.3 | – | – |
+| Parameters given in | | Table 5d | Table 5d | | |
+
+NOTE – The target distances are approximate and are to be used for classification only and not for specification.
+
+## 5.2 Reference and physical configurations
+
+The focus of this Recommendation is to specify the main path interfaces (MPIs). The MPIs are the interfaces to the long-distance fibre plant. The properties of the main path set the requirements on the terminal equipment. The terminal equipment can, in principle, be organized in different ways in order to meet the required specifications of the MPIs. This concerns such aspects as integration level, dispersion accommodation method, or the use of stand-alone optical amplifiers.
+
+Due to the multiplicity of active and passive equipment in the optical path (amplifiers, multiplexers, etc.) in the Recommendations for single- and multichannel systems with optical amplifiers, the S and R reference points must be interpreted in a generic sense, and have to be detailed for each system. To distinguish the MPI-S and -R points from other reference points (e.g., S in ITU-T Rec. G.957) the transmit and receive ends of the main path are denoted MPI-S and MPI-R respectively, when used in a general sense.
+
+The optical interconnection paths (patchcords) between any optical devices within the terminal equipment, if present, are termed "auxiliary paths". For the purpose of this Recommendation, optical fibre line system interfaces can therefore be represented as shown in Figure 1.
+
+In Figure 1, the transmitter side is illustrated using a transmitter, connected through an auxiliary path to a stand-alone optical amplifier device, whereas on the receiver side an optically amplified receiver directly interfaces with the main path.
+
+
+
+The diagram illustrates an optical link between two pieces of equipment: Transmitter equipment and Receiver equipment. The Transmitter equipment is enclosed in a dashed box and contains two components: 'Tx' (Transmitter) and 'OA' (Optical Amplifier). An arrow labeled 'Auxiliary path (if present)' points into the 'Tx' component. The 'Tx' component is connected to the 'OA' component. The 'OA' component is connected to the 'Receiver equipment' via a horizontal line representing the 'Main optical path'. The connection point on the transmitter side is labeled 'MPI-S' and the connection point on the receiver side is labeled 'MPI-R'. The Receiver equipment is also enclosed in a dashed box and contains a component labeled 'OAR' (Optical Amplifier Receiver), which is connected to the 'Main optical path'. A double-headed arrow below the main optical path line is labeled 'Main optical path'. The label 'G.691\_F1' is located in the bottom right corner of the diagram.
+
+Diagram of an optical link showing transmitter and receiver equipment connected by a main optical path. The transmitter equipment contains a Tx (Transmitter) and an OA (Optical Amplifier). The receiver equipment contains an OAR (Optical Amplifier Receiver). The main optical path is labeled 'Main optical path' and is bounded by MPI-S (Main Path Interface - Sender) and MPI-R (Main Path Interface - Receiver). An auxiliary path (if present) is shown entering the transmitter equipment from below.
+
+**Figure 1/G.691 – An example of an optical link showing the interface points defined in this Recommendation**
+
+# 6 Parameter definitions
+
+All parameter values are worst-case values, assumed to be met over the range of standard operating conditions (i.e., temperature and humidity ranges), and they include ageing effects. The parameters are specified relative to an optical section design objective of a bit error ratio (BER) not worse than $10^{-12}$ for any combination of parameters within the ranges given in the tables for each specified system.
+
+The optical line coding used for system interfaces up to, and including, STM-64 is binary non-return to zero (NRZ) scrambled according to ITU-T Rec. G.707/Y.1322.
+
+## 6.1 System operating wavelength range
+
+The operating wavelength range is the maximum allowable range for source wavelength. Within this range, the source wavelength can be selected for different amplifier implementations and different fibre-related impairments. The receiver must have a minimum operating wavelength range that corresponds to the maximum allowable range for the source wavelength.
+
+The operating wavelength range of fibre optic transmission systems is basically determined by the attenuation and dispersion characteristics of the various fibre and source types. A detailed discussion of these aspects can be found in ITU-T Rec. G.957. In the long-distance systems with optical amplifiers considered in this Recommendation, the operating wavelength range is further restricted by the optical amplifiers themselves.
+
+NOTE – When a wavelength-fixed or tunable filter to eliminate amplified spontaneous emission (ASE) is used before the receiver, the operating wavelength band may be limited, and the transverse compatibility may not be guaranteed.
+
+## 6.2 Transmitter
+
+### 6.2.1 Spectral characteristics
+
+It is not expected that spectral measurements alone will be able to guarantee transverse compatibility, and these parameters should be viewed as necessary, but not sufficient, for that purpose. Presently, few values for the spectral parameters are given. Until these values are available, transversal compatibility cannot be guaranteed for these systems.
+
+#### 6.2.1.1 Maximum spectral width for SLM sources
+
+For single-longitudinal mode (SLM) sources, the spectral width is defined as the full width of the largest spectral peak, measured 20 dB down from the maximum amplitude of the peak.
+
+The maximum time-averaged spectral width is mainly used to guard against excessive chirp in directly modulated lasers. Such sources would primarily be intended for the low-dispersion
+
+applications (e.g., STM-4, and systems on G.653 fibre), but may also be used in some high-dispersion systems.
+
+High dispersion systems (mainly STM-16, or -64 on G.652 fibre) will usually employ modulator sources. Particularly STM-64 systems on G.652 fibre operate near to or at the typical dispersion limit. Their source power spectra must therefore, by definition, be practically ideal. The maximum spectral width definition, although still valid, then becomes less useful, and the most important parameter for modulator sources instead becomes the chirp parameter.
+
+#### 6.2.1.2 Maximum spectral width for MLM sources
+
+The maximum root mean square (RMS) width or the standard deviation $\sigma$ (in nm) of the spectral distribution of a multi-longitudinal mode (MLM) laser considers all laser modes, which are not more than 20 dB down from the peak mode. Only a system with an MLM laser at 1310 nm requires this specification.
+
+#### 6.2.1.3 Chirp parameter
+
+The source frequency chirp parameter (also known as the $\alpha$ -parameter) is defined as:
+
+$$\alpha = \frac{\frac{d\phi}{dt}}{\frac{1}{2P} \cdot \frac{dP}{dt}}$$
+
+where $\phi$ is the optical phase of the signal, and $P$ its power. It should be noted that with this definition, the chirp parameter is not constant during a pulse. Therefore, a pulse may have zero average chirp parameter value, but still not be chirp free.
+
+A positive chirp parameter corresponds to a positive frequency shift (blueshift) during the rising edge of a pulse, and to a negative frequency shift (redshift) during the falling edge of the pulse. A modulator typically has a chirp parameter of $-1$ to $+1$ rad, whereas the turn-on transient of a standard laser may have a chirp factor of 10-100 rad.
+
+Since several systems in this Recommendation operate at or near to the typical dispersion limit, their source spectra must be close to ideal. The frequency chirp specification is needed to control and describe the phase behaviour of the signal, which is hardly visible in the power spectrum defined by the other parameters.
+
+The phase behaviour of the signal can be used to "peak" the performance of a system, e.g., by employing chirp induced pulse compression. It can also be used to modify the behaviour of power-induced non-linearities. This interaction is complicated, and the allowed ranges of this parameter may therefore vary with the application code and other system parameters.
+
+A test method for source chirp is discussed in Appendix IV.
+
+#### 6.2.1.4 Side mode suppression ratio
+
+The side mode suppression ratio (SMSR) is defined as the ratio of the largest peak of the total source spectrum to the second largest peak. The spectral resolution of the measurement shall be better (i.e., the optical filter bandwidth shall be less) than the maximum spectral width of the peak, as defined above. The second largest peak may be next to the main peak or far removed from it.
+
+NOTE – Within this definition spectral peaks that are separated from the largest peak by the clock frequency are not considered to be side modes.
+
+The SMSR specification is intended to minimize the occurrence of BER degradations due to mode partition noise (MPN). Since MPN is a transient effect with low probability, SMSR measurements on PRBS or continuous signals may underestimate the MPN. The SMSR specification is relevant only to SLM laser sources.
+
+#### 6.2.1.5 Maximum spectral power density
+
+The maximum (optical) spectral power density is defined as the highest time-averaged power level per 10 MHz interval anywhere in the modulated signal spectrum. The measurement must therefore be made with a resolution of better (i.e., the optical filter bandwidth shall be less) than 10 MHz FWHM.
+
+This parameter is used to avoid entering into the Brillouin scattering regime for high-power sources with potentially narrow inherent linewidths, such as laser-modulator-amplifier combinations. The specification, however, applies to all source types.
+
+### 6.2.2 Mean launched power
+
+The mean launched power at point MPI-S is the average power of a pseudo-random data sequence coupled into the fibre by the transmitter. It is given as a range to allow for some cost optimization and to cover allowances for operation under the standard operating conditions, transmitter connector degradations, measurement tolerances, and ageing effects. These values allow the calculation of values for the sensitivity and overload point for the receiver at reference point MPI-R.
+
+In the case of fault conditions in the transmit equipment, the launched power and maximum possible exposure time of personnel should be limited for optical fibre/laser safety considerations.
+
+### 6.2.3 Extinction ratio
+
+The minimum admitted value of the extinction ratio (EX) is defined as:
+
+$$EX = 10 \times \log_{10}(A/B)$$
+
+where $A$ is the average optical power level at the centre of a logical "1", and $B$ is the average optical power level at the centre of a logical "0". The convention adopted for optical logic levels is:
+
+- emission of light for a logical "1";
+- no emission for a logical "0".
+
+### 6.2.4 Eye pattern mask
+
+In this Recommendation, general transmitter pulse shape characteristics including rise time, fall time, pulse overshoot, pulse undershoot, and ringing, all of which should be controlled to prevent excessive degradation of the receiver sensitivity, are specified in the form of a mask of the transmitter eye diagram at point MPI-S. For the purpose of an assessment of the transmit signal, it is important to consider not only the eye opening, but also the overshoot and undershoot limitations. The parameters specifying the mask of the transmitter eye diagram are shown in Figure 2. Annex A considers further aspects of the eye mask definitions.
+
+For systems employing dispersion accommodation techniques based on predistortion of the signal, the eye mask in the above sense can only be defined at points with undistorted signals. These points, however, do not coincide with the main path interfaces, and may thus not even be accessible. This definition is for further study.
+
+For systems employing non-linear effects for dispersion accommodation (presently L-64.2b and V-64.2b), the eye mask may be different from the eye mask employed for linear systems.
+
+Additionally, for systems that are subject to self phase modulation (SPM) due to high power output, a specification of the minimum rise time to avoid the SPM breakdown is required. The minimum rise time (10% to 90% value of the single pulse) for systems with transmitter power levels of +12 to +15 dBm has to be 30 ps. For lower power levels such as +10 to +13 dB this value and the interaction with the signal chirp is for further study.
+
+
+
+Figure 2/G.691 – Mask of the eye diagram for the optical transmit signal. The diagram shows a normalized eye diagram with a rectangular mask overlaid. The vertical axis represents signal level from -y4 to 1+y3, with key levels at 0, y1, y2, and 1. The horizontal axis represents time from 0 to 1 UI, with key points at 0, x1, x2, x3, x4, and 1. The mask is defined by the coordinates (x1, y1), (x2, y2), (x3, y2), and (x4, y1). The mean level of the center of logical '1' is indicated near the top, and the mean level of the center of logical '0' is indicated near the bottom. The label G.691\_F2 is present in the bottom right corner of the diagram area.
+
+| | STM-4 | STM-16 | STM-64 (a, c) (Notes 2, 3) | STM-64 (b) (Notes 2, 4) |
+|-----------|-----------|-----------|----------------------------------|----------------------------------------------------------------------------------|
+| $x_1/x_4$ | 0.25/0.75 | – | ffs | – |
+| $x_2/x_3$ | 0.40/0.60 | – | ffs | – |
+| $x_3-x_2$ | – | 0.2 | ffs | 0.2 |
+| $y_1/y_2$ | 0.20/0.80 | 0.25/0.75 | ffs | $\Delta + 0.25/\Delta + 0.75$ with $\Delta$ variable $-0.25 < \Delta < +0.25$ |
+| $y_3/y_4$ | 0.20/0.20 | 0.25/0.25 | ffs | 0.25/0.25 |
+
+NOTE 1 – In the case of STM-16 and STM-64, $x_2$ and $x_3$ of the rectangular eye mask need not be equidistant with respect to the vertical axes at 0 UI and 1 UI. The extent of this deviation is for further study. In view of the frequencies involved in STM-16 and STM-64 systems, and the consequent difficulties in making this filter (see Annex A), the parameter values for STM-16 and STM-64 may need slight revision in light of experience.
+
+NOTE 2 – a, b and c refer to the dispersion accommodation techniques used for the applications in Tables 5c and 5d.
+
+NOTE 3 – Includes L-64.2a, L-64.2c, and V-64.2a.
+
+NOTE 4 – Includes L-64.2b, L-64.3, V-64.2b, and V-64.3.
+
+**Figure 2/G.691 – Mask of the eye diagram for the optical transmit signal**
+
+## 6.3 Optical path
+
+To ensure system performance for each of the applications considered in Table 1, it is necessary to specify attenuation and dispersion characteristics of the optical path between points MPI-S and MPI-R.
+
+### 6.3.1 Attenuation
+
+In this Recommendation, the attenuation for each application is specified as a range, characteristic of the broad application distances indicated in Table 1. Attenuation specifications are assumed to be worst-case values including losses due to splices, connectors, optical attenuators (if used) or other passive optical devices, and any additional cable margin to cover allowances for:
+
+- 1) future modifications to the cable configuration (additional splices, increased cable lengths, etc.);
+- 2) fibre cable performance variations due to environmental factors; and
+- 3) degradation of any connectors, optical attenuators or other passive optical devices between points MPI-S and MPI-R, if used.
+
+### 6.3.2 Dispersion
+
+#### 6.3.2.1 Maximum chromatic dispersion
+
+All systems considered in this Recommendation are dispersion sensitive. Some of the systems even operate beyond the "classic" limit for chromatic dispersion by means of certain compensation methods known as dispersion accommodation techniques, see 8.3. This parameter defines the maximum uncompensated value of the main path chromatic dispersion that the system shall be able to tolerate.
+
+The required maximum dispersion tolerance of the systems is set to a value equal to the target distance times $20 \text{ ps/km} \times \text{nm}$ for G.652 fibre, and $3.3 \text{ ps/nm} \times \text{km}$ for G.653 fibre in the 1550 nm region, as well as for G.652 fibre in the 1310 nm region. This is considered a worst-case dispersion value for the relevant fibre types. The worst-case approach on this parameter is intended to give some margins on a sensitive parameter, as well as making it possible to stretch the transmission distances for low-loss fibre plants.
+
+The allowed penalty for the optical path considers all deterministic effects due to chromatic dispersion as well as the penalty due to the average polarization mode dispersion (PMD). The statistical variations of the first and second order PMD are, however, not included in this path penalty, see 6.4.3 and Appendix I.
+
+#### 6.3.2.2 Minimum chromatic dispersion
+
+Systems that employ any form of dispersion compensation through passive or active means may require a certain minimum dispersion to be present in the path.
+
+The minimum chromatic dispersion value is the lowest dispersion value that the system is required to operate with. This does not preclude systems that can operate at even lower or zero dispersion. Since the exact operating wavelength of the system is unknown, the value is determined as the minimum value for G.652 fibre over the system operating wavelength region.
+
+#### 6.3.2.3 Maximum differential group delay
+
+Differential group delay (DGD) is the time difference between the fractions of a pulse that are transmitted in the two principal states of polarization of an optical signal. For distances greater than several km, and assuming random (strong) polarization mode coupling, DGD in a fibre can be statistically modelled as having a Maxwellian distribution.
+
+In this Recommendation, the maximum differential group delay is defined to be the value of DGD that the system must tolerate with a maximum sensitivity degradation of 1 dB.
+
+Due to the statistical nature of PMD, the relationship between maximum DGD and mean DGD can only be defined probabilistically. The probability of the instantaneous DGD exceeding any given value can be inferred from its Maxwellian statistics. Therefore, if we know the maximum DGD that the system can tolerate, we can derive the equivalent mean DGD by dividing by the ratio of maximum to mean that corresponds to an acceptable probability. Some example ratios are given below in Table 2.
+
+**Table 2/G.691 – DGD means and probabilities**
+
+| Ratio of maximum to mean | Probability of exceeding maximum |
+|--------------------------|----------------------------------|
+| 3.0 | $4.2 \times 10^{-5}$ |
+| 3.5 | $7.7 \times 10^{-7}$ |
+| 4.0 | $7.4 \times 10^{-9}$ |
+
+### 6.3.3 Dispersion compensation
+
+The typical dispersion limit for STM-64 systems operating on G.652 fibre is about 60 km when using an ideal (transform limited) source spectrum. Several systems in this Recommendation operate beyond that limit by means of certain techniques known as dispersion accommodation (DA) techniques. A DA technique is any method used to span longer distances on a certain fibre type than what is possible using an ideal intensity modulated signal. These methods are only used in STM-64 systems. More detailed descriptions of the DA techniques are contained in 8.3 and in the tutorial Appendices III to V.
+
+### 6.3.4 Reflections
+
+Reflections are caused by refractive index discontinuities along the optical path. If not controlled, they can degrade system performance through their disturbing effect on the operation of the optical source or amplifier, or through multiple reflections which lead to interferometric noise at the receiver. In this Recommendation, reflections from the optical path are controlled by specifying the:
+
+- minimum optical return loss (ORL) of the cable plant at point MPI-S, including any connectors; and
+- maximum discrete reflectance between points MPI-S and MPI-R.
+
+Reflectance denotes the reflection from any single discrete reflection point, whereas the return loss is the total returned power from the entire fibre including both discrete reflections and distributed backscattering such as Rayleigh scattering.
+
+Measurement methods for reflections are described in Appendix I/G.957. For the purpose of reflectance and return loss measurements, points MPI-S and MPI-R are assumed to coincide with the endface of each connector plug. It is recognized that this does not include the actual reflection performance of the respective connectors in the operational system. These reflections are assumed to have the nominal value of reflection for the specific type of connectors used.
+
+The maximum number of connectors or other discrete reflection points which may be included in the optical path (e.g., for distribution frames, or WDM components) must be such as to allow the specified overall optical return loss to be achieved. If this cannot be done using connectors meeting the maximum discrete reflections cited in Tables 3 to 5, then connectors having better reflection performance must be employed. Alternatively, the number of connectors must be reduced. It may also be necessary to limit the number of connectors, or to use connectors having improved reflectance performance in order to avoid unacceptable impairments due to multiple reflections.
+
+In Tables 3 to 5 the value of $-27$ dB maximum discrete reflectance between points MPI-S and MPI-R is intended to minimize the effects of multiple reflections (e.g., interferometric noise). The value for maximum receiver reflectance is chosen to ensure acceptable penalties due to multiple reflections for all likely system configurations involving multiple connectors, etc. Systems employing fewer or higher performance connectors produce fewer multiple reflections and consequently are able to tolerate receivers exhibiting higher reflectance.
+
+## 6.4 Receiver
+
+### 6.4.1 Sensitivity
+
+Receiver sensitivity is defined as the minimum value of mean received power at point MPI-R to achieve a $1 \times 10^{-12}$ BER. This must be met with a transmitter with worst-case values of transmitter eye mask, extinction ratio, optical return loss at point MPI-S, receiver connector degradations and measurement tolerances. The definition of receiver sensitivity under worst-case conditions is further discussed in Annex A.
+
+The receiver sensitivity does not have to be met in the presence of dispersion or reflections from the optical path. These effects are specified separately in the allocation of maximum optical path penalty.
+
+NOTE – The receiver sensitivity does not have to be met in the presence of transmitter jitter in excess of the appropriate jitter generation limit (e.g., G.783 for SDH optical tributary signals).
+
+Ageing effects are not specified separately since they are typically negotiated between a network provider and an equipment manufacturer.
+
+Typical margins between a beginning-of-life, nominal temperature receiver and its end-of-life, worst-case counterpart are desired to be in the 2 to 4 dB range. The receiver sensitivities specified in Tables 3 to 5 are worst-case, end-of-life values.
+
+### 6.4.2 Overload
+
+Receiver overload is the maximum acceptable value of the received average power at point MPI-R for a $1 \times 10^{-12}$ BER.
+
+### 6.4.3 Path penalty
+
+The path penalty is the apparent reduction of receiver sensitivity due to distortion of the signal waveform during its transmission over the path. It is manifested as a shift of the system's BER-curves towards higher input power levels. This corresponds to a positive path penalty. Negative path penalties may exist under some circumstances, but should be small. (A negative path penalty indicates that a less than perfect transmitter eye has been partially improved by the path dependent distortions.) Ideally, the BER-curves should be translated only, but shape variations are not uncommon, and may indicate the emergence of BER-floors. Since the path penalty is a change in the receiver's sensitivity, it is measured at a BER-level of $10^{-12}$ .
+
+A maximum path penalty of 1 dB for low-dispersion systems, and 2 dB for high-dispersion systems is allowed. The path penalties are not made proportional to the target distances to avoid operating systems with high penalties.
+
+For systems employing dispersion accommodation techniques based on predistortion of the signal at the transmitter, the path penalty in the above sense can only be defined between points with undistorted signals. These points, however, do not coincide with the main path interfaces, and may thus not even be accessible. The definition of path penalty for this case is for further study.
+
+The average value of the random dispersion penalties due to PMD is included in the allowed path penalty. In this respect, the transmitter/receiver combination is required to tolerate an actual DGD of 0.3 bit period with a maximum sensitivity degradation of 1 dB (with 50% of optical power in each principal state of polarization). For a well-designed receiver, this corresponds to a penalty of 0.1-0.2 dB for a DGD of 0.1 bit period. The actual DGD that may be encountered in operation is a randomly varying fibre/cable property, and cannot be specified in this Recommendation. This subject is further discussed in Appendix I.
+
+Note that an SNR reduction due to optical amplification is not considered a path penalty.
+
+### **6.4.4 Reflectance**
+
+Reflections from the receiver back to the cable plant are specified by the maximum permissible reflectance of the receiver measured at reference point MPI-R.
+
+# **7 Optical parameter values**
+
+Optical parameter values for the applications of Table 1 are given in Tables 3 to 5. Definitions are given in clause 6. Some measurement methods are discussed in annexes and appendices. These tables do not preclude the use of systems that meet the requirements of more than one application code.
+
+The terminal equipment can in principle be organized in different ways to meet the requirements of the main path. There are also different options that increase the flexibility of the basic application code, and which are indicated by notes.
+
+Higher or lower power level ranges may be used to meet specific requirements such as upgradability, accommodation of higher losses, or countering optical non-linearities. Currently, these power levels are not specified in this Recommendation.
+
+Currently the optical parameter values in this Recommendation are obtained without the application of in-band FEC according to ITU-T Rec. G.707/Y.1322.
+
+**Table 3/G.691 – Parameters specified for STM-4 optical interfaces**
+
+| Application code (Table 1) | Unit | V-4.1 | V-4.2 | V-4.3 | U-4.2 | U-4.3 |
+|-----------------------------------------------------------|-----------|-----------|-----------|-----------|-----------|-----------|
+| | | (Note 1) | (Note 2) | (Note 2) | (Note 3) | (Note 3) |
+| Transmitter at reference point MPI-S | | | | | | |
+| Operating wavelength range | nm | 1290-1330 | 1530-1565 | 1530-1565 | 1530-1565 | 1530-1565 |
+| Mean launched power | | | | | | |
+| – maximum | dBm | 4 | 4 | 4 | 15 | 15 |
+| – minimum | dBm | 0 | 0 | 0 | 12 | 12 |
+| Spectral characteristics | | | | | | |
+| – maximum –20 dB width | nm | ffs | ffs | ffs | ffs | ffs |
+| – chirp parameter, $\alpha$ | rad | NA | NA | NA | NA | NA |
+| – maximum spectral power density | mW/10 MHz | ffs | ffs | ffs | ffs | ffs |
+| – minimum SMSR | dB | ffs | ffs | ffs | ffs | ffs |
+| Minimum EX | dB | 10 | 10 | 10 | 10 | 10 |
+| Main optical path, MPI-S to MPI-R | | | | | | |
+| Attenuation range | | | | | | |
+| – maximum | dB | 33 | 33 | 33 | 44 | 44 |
+| – minimum | dB | 22 | 22 | 22 | 33 | 33 |
+| Chromatic dispersion | | | | | | |
+| – maximum | ps/nm | 200 | 2400 | 400 | 3200 | 530 |
+| – minimum | ps/nm | NA | NA | NA | NA | NA |
+| Maximum DGD | ps | 480 | 480 | 480 | 480 | 480 |
+| Min ORL of cable plant at MPI-S, including any connectors | dB | 24 | 24 | 24 | 24 | 24 |
+| Maximum discrete reflectance between MPI-S and MPI-R | dB | –27 | –27 | –27 | –27 | –27 |
+| Receiver at reference point MPI-R | | | | | | |
+| Minimum sensitivity (BER of $1 \times 10^{-12}$ ) | dBm | –34 | –34 | –34 | –34 | –33 |
+| Minimum overload | dBm | –18 | –18 | –18 | –18 | –18 |
+| Maximum optical path penalty | dB | 1 | 1 | 1 | 2 | 1 |
+| Maximum reflectance of receiver, measured at MPI-R | dB | –27 | –27 | –27 | –27 | –27 |
+
+NOTE 1 – The target distance is only achieved with installed fibre loss including splices and cable margins less than or equal to 0.55 dB/km.
+
+NOTE 2 – Under the assumptions given in 8.4, a G.957 transmitter and receiver together with a booster amplifier give similar system performance.
+
+NOTE 3 – The optical preamplifier specified for, e.g., U-16.x or V-64.x systems may be used instead of an optical booster amplifier. That system may get a somewhat lower attenuation range.
+
+**Table 4/G.691 – Parameters specified for STM-16 optical interfaces**
+
+| Application code (Table 1) | Unit | V-16.2 | V-16.3 | U-16.2 | U-16.3 |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------------|--------------|-------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|
+| | | (Notes 1, 2) | (Notes 1, 2) | | |
+| Transmitter at reference point MPI-S | | | | Parameters given in G.959.1 as code P1U1-1A2 | Parameters given in G.959.1 as code P1U1-1A3 |
+| Operating wavelength range | nm | 1530-1565 | 1530-1565 | | |
+| Mean launched power | | | | | |
+| – maximum | dBm | 13 | 13 | | |
+| – minimum | dBm | 10 | 10 | | |
+| Spectral characteristics | | | | | |
+| – maximum –20 dB width | nm | ffs | ffs | | |
+| – chirp parameter, $\alpha$ | rad | ffs | ffs | | |
+| – maximum spectral power density | mW/ 10 MHz | ffs | ffs | | |
+| – minimum SMSR | dB | ffs | ffs | | |
+| Minimum EX | dB | 8.2 | 8.2 | | |
+| Main optical path, MPI-S to MPI-R | | | | | |
+| Attenuation range | | | | | |
+| – maximum | dB | 33 | 33 | | |
+| – minimum | dB | 22 | 22 | | |
+| Chromatic dispersion | | | | | |
+| – maximum | ps/nm | 2400 | 400 | | |
+| – minimum | ps/nm | NA | NA | | |
+| Maximum DGD | ps | 120 | 120 | | |
+| Min ORL of cable plant at MPI-S, including any connectors | dB | 24 | 24 | | |
+| Maximum discrete reflectance between MPI-S and MPI-R | dB | –27 | –27 | | |
+| Receiver at reference point MPI-R | | | | | |
+| Minimum sensitivity (BER of $1 \times 10^{-12}$ ) | dBm | –25 | –24 | | |
+| Minimum overload | dBm | –9 | –9 | | |
+| Maximum optical path penalty | dB | 2 | 1 | | |
+| Maximum reflectance of receiver, measured at MPI-R | dB | –27 | –27 | | |
+| NOTE 1 – The optical preamplifier specified for, e.g., U-16.x or V-64.x systems may be used instead of an optical booster amplifier. That system may get a somewhat lower attenuation range.
NOTE 2 – Under the assumptions given in 8.4, a G.957 transmitter and receiver together with a booster amplifier give similar system performance.
| | | | | |
+
+**Table 5a/G.691 – Parameters specified for STM-64 optical interfaces**
+
+| Application code (Table 1) | Unit | I-64.1r | I-64.1 | I-64.2r | I-64.2 | I-64.3 | I-64.5 |
+|-----------------------------------------------------------|-----------|---------|--------|---------|--------|--------|--------|
+| Transmitter at reference point MPI-S | | | | | | | |
+| Source type | | | | | | | |
+| Operating wavelength range | nm | | | | | | |
+| Mean launched power | | | | | | | |
+| – maximum | dBm | | | | | | |
+| – minimum | dBm | | | | | | |
+| Spectral characteristics | | | | | | | |
+| – maximum RMS width ( $\sigma$ ) | nm | | | | | | |
+| – maximum –20 dB width | nm | | | | | | |
+| – chirp parameter, $\alpha$ | rad | | | | | | |
+| – maximum spectral power density | mW/10 MHz | | | | | | |
+| – minimum SMSR | dB | | | | | | |
+| Minimum EX | dB | | | | | | |
+| Main optical path, MPI-S to MPI-R | | | | | | | |
+| Attenuation range | | | | | | | |
+| – maximum | dB | | | | | | |
+| – minimum | dB | | | | | | |
+| Chromatic dispersion | | | | | | | |
+| – maximum | ps/nm | | | | | | |
+| – minimum | ps/nm | | | | | | |
+| Passive dispersion compensation | | | | | | | |
+| – maximum | ps/nm | | | | | | |
+| – minimum | ps/nm | | | | | | |
+| Maximum DGD | ps | | | | | | |
+| Min ORL of cable plant at MPI-S, including any connectors | dB | | | | | | |
+| Maximum discrete reflectance between MPI-S and MPI-R | dB | | | | | | |
+| Receiver at reference point MPI-R | | | | | | | |
+| Minimum sensitivity (BER of $1 \times 10^{-12}$ ) | dBm | | | | | | |
+| Minimum overload | dBm | | | | | | |
+| Maximum optical path penalty | dB | | | | | | |
+| Maximum reflectance of receiver, measured at MPI-R | dB | | | | | | |
+
+NOTE – All applications in this Recommendation use single-longitudinal mode (SLM) lasers as sources except the I-64.1r application that uses multi-longitudinal mode (MLM) lasers.
+
+**Table 5b/G.691 – Parameters specified for STM-64 optical interfaces**
+
+| Application code (Table 1) | Unit | S-64.1 | S-64.2a | S-64.2b | S-64.3a | S-64.3b | S-64.5a | S-64.5b |
+|-----------------------------------------------------------|---------------|--------|---------|---------|---------|---------|---------|---------|
+| Transmitter at reference point MPI-S | | | | | | | | |
+| Operating wavelength range | nm | | | | | | | |
+| Mean launched power | | | | | | | | |
+| – maximum | dBm | | | | | | | |
+| – minimum | dBm | | | | | | | |
+| Spectral characteristics | | | | | | | | |
+| – maximum –20 dB width | nm | | | | | | | |
+| – chirp parameter, $\alpha$ | rad | | | | | | | |
+| – maximum spectral power density | mW/ 10 MHz | | | | | | | |
+| – minimum SMSR | dB | | | | | | | |
+| Minimum EX | dB | | | | | | | |
+| Main optical path, MPI-S to MPI-R | | | | | | | | |
+| Attenuation range | | | | | | | | |
+| – maximum | dB | | | | | | | |
+| – minimum | dB | | | | | | | |
+| Chromatic dispersion | | | | | | | | |
+| – maximum | ps/nm | | | | | | | |
+| – minimum | ps/nm | | | | | | | |
+| Passive dispersion compensation | | | | | | | | |
+| – maximum | ps/nm | | | | | | | |
+| – minimum | ps/nm | | | | | | | |
+| Maximum DGD | ps | | | | | | | |
+| Min ORL of cable plant at MPI-S, including any connectors | dB | | | | | | | |
+| Maximum discrete reflectance between MPI-S and MPI-R | dB | | | | | | | |
+| Receiver at reference point MPI-R | | | | | | | | |
+| Minimum sensitivity (BER of $1 \times 10^{-12}$ ) | dBm | | | | | | | |
+| Minimum overload | dBm | | | | | | | |
+| Maximum optical path penalty | dB | | | | | | | |
+| Maximum reflectance of receiver, measured at MPI-R | dB | | | | | | | |
+
+NOTE – S-64.2a, 3a, and 5a have transmitter power levels appropriate for APD receivers; S-64.2b, 3b, and 5b have transmitter power levels appropriate for PIN receivers.
+
+**Table 5c/G.691 – Parameters specified for STM-64 optical interfaces**
+
+| Application code (Table 1) | Unit | L-64.1 | L-64.2a | L-64.2b | L-64.2c | L-64.3 |
+|-----------------------------------------------------------|----------|--------|--------------|-----------|-----------|-----------|
+| | | | (Notes 1, 2) | (Note 1) | (Note 1) | |
+| Transmitter at reference point MPI-S | | | | | | |
+| Operating wavelength range | nm | | 1530-1565 | 1530-1565 | 1530-1565 | 1530-1565 |
+| Mean launched power | | | | | | |
+| – maximum | dBm | | +2 | 13 | +2 | 13 |
+| – minimum | dBm | | –2 | 10 | –2 | 10 |
+| Spectral characteristics | | | | | | |
+| – maximum –20 dB width | nm | | ffs | ffs | ffs | ffs |
+| – chirp parameter, $\alpha$ | rad | | ffs | ffs | ffs | ffs |
+| – maximum spectral power density | mW/10MHz | | ffs | ffs | ffs | ffs |
+| – minimum SMSR | dB | | ffs | ffs | ffs | ffs |
+| Minimum EX | dB | | 10 | 8.2 | 10 | 8.2 |
+| Main optical path, MPI-S to MPI-R | | | | | | |
+| Attenuation range | | | | | | |
+| – maximum | dB | | 22 | 22 | 22 | 22 |
+| – minimum | dB | | 11 | 16 | 11 | 16 |
+| Chromatic dispersion | | | | | | |
+| – maximum | ps/nm | | 1600 | 1600 | 1600 | 260 |
+| – minimum | ps/nm | | ffs | ffs | ffs | NA |
+| Passive dispersion compensation | | | | | | |
+| – maximum | ps/nm | | ffs | NA | NA | NA |
+| – minimum | ps/nm | | ffs | NA | NA | NA |
+| Maximum DGD | ps | | 30 | 30 | 30 | 30 |
+| Min ORL of cable plant at MPI-S, including any connectors | dB | | 24 | 24 | 24 | 24 |
+| Maximum discrete reflectance between MPI-S and MPI-R | dB | | –27 | –27 | –27 | –27 |
+| Receiver at reference point MPI-R | | | | | | |
+| Minimum sensitivity (BER of $1 \times 10^{-12}$ ) | dBm | | –26 | –14 | –26 | –13 |
+| Minimum overload | dBm | | –9 | –3 | –9 | –3 |
+| Maximum optical path penalty | dB | | 2 | 2 | 2 | 1 |
+| Maximum reflectance of receiver, measured at MPI-R | dB | | –27 | –27 | –27 | –27 |
+
+Parameters given in G.959.1 as code P11.1-2D1
+
+NOTE 1 – L-64.2a uses PDC as DA, L-64.2b uses SPM as DA, and L-64.2c uses prechirp as DA.
+
+NOTE 2 – See 8.3.2 on the values and placement of the PDC.
+
+**Table 5d/G.691 – Parameters specified for STM-64 optical interfaces**
+
+| Application code (Table 1) | Unit | V-64.2a | V-64.2b | V-64.3 |
+|-----------------------------------------------------------|---------------|--------------|-----------|-----------|
+| | | (Notes 1, 2) | (Note 2) | |
+| Transmitter at reference point MPI-S | | | | |
+| Operating wavelength range | nm | 1530-1565 | 1530-1565 | 1530-1565 |
+| Mean launched power | | | | |
+| – maximum | dBm | 13 | 15 | 13 |
+| – minimum | dBm | 10 | 12 | 10 |
+| Spectral characteristics | | | | |
+| – maximum –20 dB width | nm | ffs | ffs | ffs |
+| – chirp parameter, $\alpha$ | rad | ffs | ffs | ffs |
+| – maximum spectral power density | mW/ 10 MHz | ffs | ffs | ffs |
+| – minimum SMSR | dB | ffs | ffs | ffs |
+| Minimum EX | dB | 10 | 8.2 | 8.2 |
+| Main optical path, MPI-S to MPI-R | | | | |
+| Attenuation range | | | | |
+| – maximum | dB | 33 | 33 | 33 |
+| – minimum | dB | 22 | 22 | 22 |
+| Chromatic dispersion | | | | |
+| – maximum | ps/nm | 2400 | 2400 | 400 |
+| – minimum | ps/nm | ffs | ffs | NA |
+| Passive dispersion compensation | | | | |
+| – maximum | ps/nm | ffs | ffs | NA |
+| – minimum | ps/nm | ffs | ffs | NA |
+| Maximum DGD | ps | 30 | 30 | 30 |
+| Min ORL of cable plant at MPI-S, including any connectors | dB | 24 | 24 | 24 |
+| Maximum discrete reflectance between MPI-S and MPI-R | dB | –27 | –27 | –27 |
+| Receiver at reference point MPI-R | | | | |
+| Minimum sensitivity (BER of $1 \times 10^{-12}$ ) | dBm | –25 | –23 | –24 |
+| Minimum overload | dBm | –9 | –7 | –9 |
+| Maximum optical path penalty | dBm | 2 | 2 | 1 |
+| Maximum reflectance of receiver, measured at MPI-R | dB | –27 | –27 | –27 |
+
+NOTE 1 – See 8.3.2 on the values and placement of the PDC.
+
+NOTE 2 – V-64.2a uses PDC as DA and V-64.2b uses a combination of SPM and PDC as DA.
+
+# 8 Optical engineering approach
+
+## 8.1 Design assumptions
+
+This clause discusses the design aspects introduced in this Recommendation due to, e.g., optical amplifiers and dispersion accommodation. A general discussion on worst-case and statistical design approaches can be found in ITU-T Rec. G.957.
+
+## 8.2 Non-linearities
+
+Due to the introduction of optical amplifiers, sufficiently high optical powers may be used that significant effects due to optical non-linearities may be encountered. A detailed discussion of these non-linearities can be found in ITU-T Rec. G.663.
+
+## 8.3 Dispersion accommodation
+
+The typical dispersion limit for STM-64 systems operating on G.652 fibre is about 60 km when using an ideal (transform limited) source spectrum. Several systems in this Recommendation operate beyond that limit by means of certain techniques known as dispersion accommodation (DA) techniques. A DA technique is any method used to span longer distances on a certain fibre type than is possible using an ideal intensity modulated signal. These methods are only used in STM-64 systems.
+
+Presently, this Recommendation includes DA by passive dispersion compensation (PDC), self phase modulation (SPM), prechirp (PCH), and dispersion supported transmission (DST). The preferred choice of method is for further study.
+
+### 8.3.1 Design principle
+
+Dispersion accommodation is required above 50-60 km of G.652 fibre at STM-64 data rates. The S-64.2 systems are below this limit and do not employ any DA. For the L-64.2 systems, some form of DA is applied to compensate the additional dispersion incurred in the 40-80 km range. This DA may be of different forms.
+
+Both active and passive DA methods are employed for the L-64.2 systems. The passive method uses a PDC to compensate the inherent dispersion of the fibre. The active methods (SPM, PCH, and DST) instead tailor the interface parameters in such a way that the dispersion is balanced out. For the V-64.2 systems, additional passive DA is added to compensate for the extra 40 km of fibre.
+
+In practice, all presently proposed DA schemes compensate the dispersion over a more restricted range than from zero to full link length. These systems may depend on some minimum dispersion to be present in the link. The parameter "minimum chromatic dispersion" has therefore been introduced. When testing DA systems back to back, it may, for some systems, be necessary to introduce a minimum dispersion in the test set-up. This is analogous to the use of attenuators in order not to overload a receiver during back-to-back testing.
+
+All methods are required to be transverse compatible within their application code. However, until the spectral characteristics and measurement methods have been defined, transversal compatibility cannot be guaranteed. The transverse compatibility between different DA methods is for further study.
+
+### 8.3.2 Passive dispersion compensation
+
+One method to overcome the dispersion limit is to add a passive dispersion compensator (PDC) to the transmitter, the receiver, or both. This Recommendation is intended to cover all types of passive dispersion compensators.
+
+It is assumed that the PDC is not inserted into the main path since the insertion loss of the device (presently several dBs) would decrease the system attenuation range. Instead, the PDC is normally added before an optical power amplifier or after an optical preamplifier. The gain of the amplifiers is used to compensate for the insertion loss of the PDC without detracting from the system power budget.
+
+This description does not imply any particular integration level of the transmitter or receiver, i.e., they can be realized as either stand-alone devices or as integrated, optically amplified, transmitters or receivers.
+
+The guiding principle for the use of PDCs in STM-64 systems is that the S-systems at 40 km are designed without DA. For each longer application code, i.e., L-64.2 and V-64.2, a PDC for each additional 40 km is added, see Figure 3. The nominal dispersion value for each PDC then becomes $-680 \text{ ps/nm}$ at 1550 nm. The exact value, and whether the PDC should create an over- or under-compensation, is for further study. In theory, the PDC for an L-64.2 system would only need to compensate for the difference between the target distance and the typical dispersion limit. However, that would lead to small operating margins, and the present approach also facilitates the use of identical equipment building blocks that are used in all systems. PDCs are specified in ITU-T Rec. G.671.
+
+
+
+Figure 3/G.691 – Scheme for passive dispersion compensation for systems without line amplifiers. The diagram shows three optical link configurations: (a) Tx connected to a 40 km fiber and then to Rx; (b) Tx connected to an 80 km fiber, followed by an optical amplifier (OA), a PDC, and then Rx; (c) Tx connected to a PDC, then an OA, a 120 km fiber, another OA, a PDC, and finally Rx. Fiber segments are represented by three overlapping circles.
+
+G.691\_F3
+
+NOTE – The values and placement of the PDC are for further study.
+
+**Figure 3/G.691 – Scheme for passive dispersion compensation for systems without line amplifiers**
+
+If a PDC is used at the transmitter side, the PDC creates a predistortion of the signal before it is sent out on the optical path. The transmitter eye diagrams specified in 6.2.4 are then not available at point MPI-S. If the non-distorted signal is available, the eye diagrams specifications are valid at that point. The MPI-S eye diagram specification for predistorted systems is for further study.
+
+Since the use of a PDC at the transmitter side implies the use of an optical booster amplifier to compensate for the loss of the PDC, the power levels will be high enough to generate SPM and possibly other non-linear effects in the signal. The PDC is, however, a linear dispersion compensator, and the non-linear distortion of the transmitted signal may degrade the linear dispersion compensation if applied at the transmitter.
+
+For the L-64.2 system, the specified placement of the PDC is therefore at the receiver. This will lead to the use of an optical preamplifier and a non-amplified transmitter, and give a system that does not operate in the non-linear regime.
+
+For the V-64.2 system, where the use of a booster amplifier is necessary, further actions may have to be taken to ascertain that the non-linear effects do not excessively degrade the linear dispersion compensation if it is placed at the transmitter side. This is for further study.
+
+If a PDC is located in the fibre plant, it is considered to belong to the path, and it will typically then "convert" a G.652 path to a G.653-like path if the transmit power level is lower than approximately +10 dBm, and the behaviour of the optical path is linear. The system itself is then considered to be a X-xx.3 system, and the system requirements with regard to path attenuation and dispersion are given by the X-xx.3 application codes. Partial compensation of a path is considered as joint engineering and is not treated in this Recommendation.
+
+### 8.3.3 Self phase modulation
+
+Self phase modulation (SPM) uses the non-linear Kerr effect in the G.652 fibre to obtain a pulse compression that increases the transmission distance. A tutorial description of the technique is given in Appendix II.
+
+Since this technique requires the power level of the signal to be in the non-linear regime of the fibre, the SPM dispersion compensation effect is caused by the transmitted power and occurs in the transmission fibre close to the transmitter, as long as the signal power is above the non-linearity threshold. When the signal has propagated on the order of 15-40 km (with the power levels used in the L- and V-64.2 systems), it has been attenuated so that it is no longer in the non-linear regime. The rest of the propagation is therefore linear. This gives the possibility to combine SPM on the transmitter side with a PDC on the receiver side.
+
+The pulse propagation is also influenced by the frequency chirping of the pulse, which can also be used for pulse compression. It is therefore necessary to specify the chirp parameter. In order not to overcompensate for the dispersion, the chirping parameter should be close to zero when using SPM.
+
+The non-linear phase modulation depends also on the pulse shape. This may lead to different eye masks for systems employing SPM as compared to the linear systems. This is for further study.
+
+### 8.3.4 Prechirp
+
+Another method uses prechirp in the transmitter to obtain a pulse compression effect, and thereby increase the transmission distance. However, the use of a high-power transmitter in this case would give rise to both prechirp and SPM at the same time. This combination would lead to an overcompensation of the system for the L-64 application code.
+
+The prechirp scheme is therefore used with a low power transmitter and an optically preamplified receiver. This will, however, lead to required transmitter power levels of -1 dBm, which may presently not be easy to achieve with all transmitter types. The transmitter and receiver interface parameters for this application code are for further study.
+
+### 8.3.5 Combinations of techniques
+
+The only combination of DA techniques presently specified is to use SPM together with a PDC in a V-64.2 system. The SPM is used to accommodate the dispersion for the first 80 km, as in the basic L-64.2b SPM based system, and the added 40 km are fully compensated by a PDC. This latter compensation occurs in the linear regime, and should therefore not be influenced by the non-linear technique employed for the initial part of the link.
+
+In a similar way a DST system designed for an 80 km target distance (DST L-64.2) can be combined with a PDC in a V-64.2 system if the added 40 km are fully compensated by a PDC.
+
+### **8.3.6 Dispersion supported transmission**
+
+A further method, dispersion supported transmission (DST), uses a combination of intensity and frequency modulation instead of intensity modulation to counter the dispersion. A tutorial description and a specification for the DST method, as applied to L-64.2 and V-64.2 systems, are given in Appendix III.
+
+## **8.4 Stand-alone amplifiers**
+
+A stand-alone amplifier (optical amplifier device) can be used for new installations or as an upgrade path. In either case, a stand-alone booster- or pre-amplifier interfaces the main path, as specified in this Recommendation, on one side, and a non-amplified (selected G.957, S-64.x, etc.) system on the other side. Since the purpose of the stand-alone amplifier is to increase the transmission distance, the system integrator must ascertain that the properties of the interfaced, non-amplified, system are such that it can indeed operate over the extended distance. This may require wavelength ranges and spectral characteristics as suggested in 6.1/G.957 and 6.2.2/G.957, and additional parameter values in accordance with this Recommendation.
+
+If the original system does not possess the properties necessary for operation over longer distances, the stand-alone amplifier functionality can be extended to adapt these parameters to become compatible with this Recommendation. It may, for example, implement some dispersion accommodation technique as described in 8.3, or it may use a transponder for spectral conversion.
+
+The supervision of stand-alone booster- and/or pre-amplifiers can be accomplished through an electrical interface to the SDH equipment or through direct access to the management system.
+
+## **8.5 Upgradability considerations**
+
+Transmission-capacity requirements of the systems covered by this Recommendation are expected to increase in the near future. Upgradability would be a key to cope with this evolution.
+
+The term "upgrade" means any equipment change intended to achieve increased performance that does not require new fibres or buildings. Most upgrades require equipment replacement in which case the upgrade is, by definition, out of service. Protection switching may, however, be used to keep the system operating while specific parts of the systems are out of service. System performance is generally not sacrificed for upgradability.
+
+Forward error correction (FEC) can provide both improvement of the BER and additional system margin. For SDH systems treated in this Recommendation only in-band FEC is applicable according to ITU-T Rec. G.707/Y.1322. However, the optical parameter values specified for the application codes are applicable when the FEC is disabled. Possible modification to the optical parameter values when FEC is enabled is for further study.
+
+Various types of upgrades are categorized in 8.5.1 followed by upgrade guidelines in 8.5.2.
+
+### **8.5.1 Types of upgrades**
+
+#### **8.5.1.1 Upgrades to longer distances**
+
+In general, upgrades to longer distances are equal to "equipment reuse or replacement" since longer distances require larger attenuation spans and tighter tolerances on, e.g., spectral properties.
+
+#### **8.5.1.2 Upgrades to higher bit rates**
+
+Capacity expansion by going to a higher bit rate also means equipment replacement and would lead to service interruption if no additional measures are taken (e.g., protection switching). Within a wavelength band the target distances for inter-office systems are in equal steps in each wavelength band (40 km for the 1550 nm band and 20 km for the 1310 nm band).
+
+Appendix V provides additional information on upgrades to higher bit rate systems.
+
+#### **8.5.1.3 Upgrades from single- to multichannel systems**
+
+An upgrade from a single-channel to a multichannel system is an out-of-service, equipment-reuse type of upgrade. If an in-service capacity expansion is required, a multichannel system should be employed from the beginning.
+
+#### **8.5.1.4 Upgrades using stand-alone optical amplifiers**
+
+When using a stand-alone amplifier for upgrade purposes, the same considerations as in 8.4 apply.
+
+### **8.5.2 Guidelines of upgrades**
+
+Reserving upgradabilities of single-channel systems and of multichannel systems with no line amplifiers may not be advantageous because the optically amplified transmitter and optically amplified receiver have to be significantly modified or even renewed for a bit rate upgrade, while just the fibres are reused.
+
+Reserving upgradabilities from single-channel systems to multichannel systems may not be advantageous. This is because their design philosophies are very different from many viewpoints including fibre-amplifier design and control, power budget and, from the considerations of dispersion, fibre non-linearity and signal-to-noise ratios.
+
+## **8.6 Optical safety considerations**
+
+See ITU-T Rec. G.664 for optical safety considerations.
+
+# **Annex A**
+
+## **Extinction ratio and eye mask penalties**
+
+## **A.1 Measurement parameters**
+
+The eye mask measurement specification is grouped in two parts; one for STM-4 and STM-16 interfaces, and one for the STM-64 interfaces.
+
+- i) For STM-4/STM-16, an eye mask measurement procedure and reference receiver such as is outlined in Annex B/G.957 is assumed, i.e., a fourth order Bessel-Thomson filter with the appropriate cut-off frequencies for the bit rate in question. The tolerance values of this reference receiver are given in Table A.1.
+- ii) For STM-64, an eye mask measurement procedure and optical reference receiver such as is outlined in Annex B/G.957 is assumed also, i.e., a fourth order Bessel-Thomson filter with the appropriate cut-off frequencies for the STM-64. For this rate, however, the optical reference receiver function is defined as the total frequency response of any combination of photodetector, low-pass filter and oscilloscope functional elements, together with any interconnection of those elements. The tolerance values of this transfer function are given in the last column (STM-64) of Table A.1.
+
+**Table A.1/G.691 – Tolerance values of the attenuation of the optical reference receiver**
+
+| f/fr | $\Delta a$ [dB] | | |
+|------------------------|------------------------|------------------------|-------------------------|
+| | STM-4 | STM-16 | STM-64 |
+| 0.001 to 1 | $\pm 0.3$ | $\pm 0.5$ | $\pm 0.85$ |
+| 1 to 2 (Note) | $\pm 0.3$ to $\pm 2.0$ | $\pm 0.5$ to $\pm 3.0$ | $\pm 0.85$ to $\pm 4.0$ |
+
+NOTE – Intermediate values of $\Delta a$ should be interpolated linearly on a logarithmic frequency scale.
+
+Figure A.1 illustrates the penalties that may be incurred from eye mask and extinction ratio (EX) imperfections. In the figure, the EX is the ratio $a/b$ , and the relative eye opening is the ratio $d/c$ . Ideally, the EX is infinite, and the eye is completely open and symmetric. The entire optical power is then available for modulation, and the EX and eye mask penalties are 0 dB.
+
+
+
+Figure A.1/G.691 – Eye mask and extinction ratio penalties. The diagram shows an eye diagram with various parameters labeled. 'a' is the total height of the signal envelope. 'b' is the height of the lower signal envelope. 'c' is the height of the upper signal envelope. 'd' is the height of the eye opening. 'Mean level of centre of logical "1"' is the top horizontal line. 'Eye mask (example)' is a shaded region. 'Average power' is the middle horizontal line. 'Mean level of centre of logical "0"' is the bottom horizontal line. 'Zero power' is the bottom-most horizontal line. The label G.691\_FA.1 is at the bottom right.
+
+**Figure A.1/G.691 – Eye mask and extinction ratio penalties**
+
+## A.2 Extinction ratio penalty
+
+The extinction ratio leads to some fraction of the optical power not being available for modulation, it corresponds to a receiver sensitivity penalty. The exact penalty depends on the application and the chosen receiver implementation.
+
+## A.3 Eye mask penalty
+
+In addition to the limited EX, the eye may be closed from its average "0" and "1" levels due to transient signal imperfections such as rise and fall times, overshoot, etc. If the relative eye opening $d/c$ is less than one, a penalty is incurred. The eye mask penalty, $P_{EM}$ can be written as:
+
+$$P_{EM} = 10 \log_{10} \left( \frac{d}{c} \right) \quad [dB]$$
+
+which corresponds to the loss in receiver sensitivity compared to a signal with completely open eye. Since the BER is an extremely steep function of the signal, a single imperfection can determine the entire BER. It is therefore the innermost lines in the eye (the open eye) that determine the BER. Even lines that are so rare that they are not easily visualized in an eye mask measurement (due to a limited measurement time) can have profound effects on the BER.
+
+The present eye mask allows for an eye closure of up to 50% of the eye opening. The actual system penalty associated with this eye closure depends upon the implementation of the system. In a given situation, the eye mask penalty can be reasonably well estimated as the relative (vertical) eye opening at the decision point of the receiver.
+
+To evaluate the eye mask penalty, the eye mask measurement filter and measurement procedure should correspond to the used receiver behaviour. Since this is not specified in detail, the eye mask penalty is not a precise receiver penalty. However, the correspondence is usually quite good since most receiver designs are reasonably similar to the filter used in the eye mask measurement procedure.
+
+## A.4 Receiver sensitivity
+
+Extinction ratio penalty and eye mask penalty are additive in dB. For example, if the EX penalty is 1.3 dB, and the eye mask penalty is 3 dB, the worst-case signal will show a sensitivity of 4.3 dB less than when using an ideal transmitter.
+
+According to the definition of the receiver sensitivity, it should be measured under worst-case conditions. If this is not done, a correction for the receiver sensitivity due to a measurement under too benign conditions can be estimated from the EX and relative eye opening of the test transmitter. This estimation may be preferred to testing with a strict worst-case signal, which may be difficult to generate.
+
+# Appendix I
+
+## Polarization mode dispersion
+
+## I.1 The statistical distribution of PMD
+
+As described in 6.3.2.3, the differential group delay (DGD) between the polarization states in a non-polarization preserving fibre is a random variable. It is often assumed to have a Maxwellian distribution with the following probability density function:
+
+$$f(\Delta\tau) = 32 \frac{\Delta\tau^2}{\pi^2 \langle \Delta\tau \rangle^3} \exp\left(-\frac{4\Delta\tau^2}{\pi \langle \Delta\tau \rangle^2}\right)$$
+
+where $\Delta\tau$ is the DGD, $\langle \Delta\tau \rangle$ is the mean DGD. Figure I.1 shows the probability density function $f(\Delta\tau)$ . At a given instant, however, the system will experience a specific DGD, $\tau$ , that is some realization of the random distribution of DGD values, with the average given by the PMD of the link. A pulse train may thus suffer from a delay difference that is smaller or larger than the average PMD of the link.
+
+
+
+Figure I.1/G.691: A plot of the probability density function f(Δτ) versus differential group delay Δτ. The curve is a bell-shaped distribution centered at the mean value <Δτ>. The area under the curve to the left of the mean is labeled 'Area 1', and the area to the right is labeled 'Area 2'. An arrow points to the peak with the text 'Area 1 = Area 2'. The x-axis is marked with 0, <Δτ>, 2 <Δτ>, and 3 <Δτ>. The y-axis is labeled f(Δτ). The figure is identified by the code G.691\_FI.1.
+
+**Figure I.1/G.691 – The Maxwellian distribution function (illustration) –
+Probability density function $f(\Delta\tau)$ vs differential group delay, $\Delta\tau$**
+
+Integrating this probability density function from $\Delta\tau_1$ to $+\infty$ gives the probability $P(\Delta\tau \geq \Delta\tau_1)$ :
+
+$$P(\Delta\tau \geq \Delta\tau_1) = \int_{\Delta\tau_1}^{\infty} f(\Delta\tau) d(\Delta\tau)$$
+
+This probability $P(\Delta\tau \geq \Delta\tau_1)$ is depicted in Figure I.2.
+
+For example, if DGD is greater than 3 times the mean of DGD, $\Delta\tau_1 = 3 \langle \Delta\tau \rangle$ , then it can be read from Figure I.2 that $P(\Delta\tau \geq 3 \langle \Delta\tau \rangle) \approx 4 \times 10^{-5}$ .
+
+![Figure I.2/G.691: A plot of the probability P(Δτ ≥ Δτ₁) versus differential group delay Δτ₁. The y-axis is logarithmic, ranging from 1.0E+00 down to 1.0E-10. The x-axis is linear, marked with 0, <Δτ>, 2 <Δτ>, and 3 <Δτ>. The curve starts at 1.0E+00 and decreases as Δτ₁ increases. A horizontal dashed line at approximately 4 × 10⁻⁵ is labeled p[Δτ ≥ 3 <Δτ>], and a vertical dashed line at 3 <Δτ> intersects it. The figure is identified by the code G.691_FI.2.](54b5c00e104d6abae06037df2ce1f075_img.jpg)
+
+Figure I.2/G.691: A plot of the probability P(Δτ ≥ Δτ₁) versus differential group delay Δτ₁. The y-axis is logarithmic, ranging from 1.0E+00 down to 1.0E-10. The x-axis is linear, marked with 0, <Δτ>, 2 <Δτ>, and 3 <Δτ>. The curve starts at 1.0E+00 and decreases as Δτ₁ increases. A horizontal dashed line at approximately 4 × 10⁻⁵ is labeled p[Δτ ≥ 3 <Δτ>], and a vertical dashed line at 3 <Δτ> intersects it. The figure is identified by the code G.691\_FI.2.
+
+**Figure I.2/G.691 – Probability $P(\Delta\tau \geq \Delta\tau_1)$**
+
+The DGD variations depend on the polarization states excited in the fibre, the strain in different parts of the fibre, temperature variations, etc., and are thus rather slowly varying. Assuming that it takes about a day for the DGD to change significantly, the above probability corresponds to a period of about 70 years between instances when the PMD rises to three times its average value.
+
+The characteristic time of the PMD variations are, however, strongly influenced by the fibre environment, and, e.g., aerial cables may have shorter variation times. If the characteristic time is instead assumed to be one minute, the PMD will rise to three times its average about once every 17 days.
+
+The "outage time", during which the path penalty due to PMD is high, will also be on the order of the characteristic time, i.e., one day, and one minute, respectively, in the above two examples.
+
+### I.2 The path penalty due to PMD
+
+Since PMD is a fibre property, it cannot be specified in this Recommendation. Instead, the amount of total PMD in the link corresponding to a worst-case path penalty of 1 dB is considered. The worst case is based on a DGD of 0.3 bit period in conjunction with the assumption that both principal states of polarization (PSP) carry the same optical power.
+
+![Figure I.3/G.691 – The dependence of the receiver penalty on the actual DGD (illustration). The graph plots PMD penalty [dB] on the y-axis against DGD [U.I.] on the x-axis. Two curves are shown: one for a receiver with signal dependent noise (steeper) and one for a receiver without signal dependent noise (e.g., PIN) (shallower). The y-axis has markers at 0, 0.1-0.2 (Average PMD penalty), 0.5, and 1. The x-axis has markers at 0, 0.1, 0.2, and 0.3. Vertical lines at DGD 0.1, 0.2, and 0.3 intersect the curves at penalty levels of approximately 0.1-0.2, 0.5, and 1 dB respectively.](9db774ce7e2ae9d89f439a41156214dd_img.jpg)
+
+Figure I.3/G.691 – The dependence of the receiver penalty on the actual DGD (illustration). The graph plots PMD penalty [dB] on the y-axis against DGD [U.I.] on the x-axis. Two curves are shown: one for a receiver with signal dependent noise (steeper) and one for a receiver without signal dependent noise (e.g., PIN) (shallower). The y-axis has markers at 0, 0.1-0.2 (Average PMD penalty), 0.5, and 1. The x-axis has markers at 0, 0.1, 0.2, and 0.3. Vertical lines at DGD 0.1, 0.2, and 0.3 intersect the curves at penalty levels of approximately 0.1-0.2, 0.5, and 1 dB respectively.
+
+**Figure I.3/G.691 – The dependence of the receiver penalty on the actual DGD (illustration)**
+
+A Maxwellian distribution function is assumed for the DGD (see Figure I.1). The connection between the DGD (being in direct coincidence with the PMD-induced signal pulse width broadening if the same optical power in both PSPs is assumed) and the corresponding path penalty, is a receiver characteristic, and is illustrated in Figure I.3. With realistic assumptions and a well-designed receiver, it can be deduced that an actual DGD of 0.3 bit period (and 50% of optical power in both PSPs) will give a penalty of about 0.5 dB for a receiver with signal independent noise (PIN-receiver), and up to 1 dB for a receiver with signal dependent noise (APD or preamplifier).
+
+The corresponding allowable maximum PMD of the fibre depends on several items including:
+
+- the statistical distribution of the DGD;
+- the tolerable probability that the penalty may exceed 0.5 dB (PIN) or 1 dB (e.g., APD);
+- the correlation between the spatial fluctuations of the PSPs and the fluctuations of the DGD;
+- the orientation of the input state of polarization (SOP) of the light emitted by the laser transmitter, relative to the orientation of the PSPs.
+
+A realistic correlation between the allowable maximum PMD and the maximum signal pulse width broadening is for further study. A first estimation can be deduced by the following illustrative example: A maximum PMD of 0.1 bit period indicates a probability of $4 \times 10^{-5}$ for a path penalty of larger than 1 dB (see Figures I.2 and I.3). However, it is expected to have a much smaller probability than $4 \times 10^{-5}$ for $>1$ dB path penalty in this example because of the following reason: when the DGD is changed (e.g., by strain or temperature variation) then, in general, the spatial orientation of the PSPs is changed as well. Consequently, the orientation of the input SOP of laser transmitter light relative to the orientation of the PSPs will alter. Therefore, the spatially fluctuating PSPs will usually not carry the same optical power resulting in a smaller penalty at the receiver (because the probability of $4 \times 10^{-5}$ only holds for the assumption of equal power in both PSPs). Inversely, it is likely that a tolerable probability of $4 \times 10^{-5}$ for $>1$ dB path penalty will allow a maximum PMD which is larger than 0.1 bit period.
+
+# Appendix II
+
+## Description of SPM as dispersion accommodation
+
+## II.1 SPM basics
+
+When using high power transmitters, as in unrepeatable long-haul transmission systems, non-linear effects such as self phase modulation (SPM) play an important role in the transmission quality. In intensity modulated systems, a modulation of the refractive index of the optical fibre is introduced at high transmitter powers, giving rise to different refractive indices in a "1", as compared to a "0" in the bits. The modulation of the refractive index by the changing power levels is referred to as the Kerr effect.
+
+The optical intensity variation of a given pulse modulates the refractive index of the fibre which in turn leads to a modulation of the phase of the optical wave. This is the process known as SPM. The time derivative of phase is frequency, and the optical signal will experience an asymmetrical frequency deviation from its midpoint so that the spectral components at the rising edge of the pulse experience a downward frequency shift, a red shift, whilst the spectral components at the falling edge of the pulse experience an upward frequency shift, a blue shift.
+
+In G.652 fibre at 1550 nm, red shifted components travel slower whilst blue shifted components travel faster relative to one another. The propagation speed of the spectral components towards the back of the pulse is therefore faster than that of the spectral components at the front. This will lead to a reduced net chromatic dispersion effect, or pulse compression, and will delay the onset of the chromatic dispersion induced transmission span limitation.
+
+The maximum phase shift introduced by SPM is proportional to the optical power launched by the transmitter, and inversely proportional to the attenuation coefficient and the effective core area of the transmission fibre.
+
+## II.2 Using self phase modulation as a dispersion accommodation technique
+
+The pulse compression obtained by SPM counteract the pulse broadening caused by the fibre dispersion. Therefore SPM can be used as a dispersion accommodation (DA) technique. The SPM used as a dispersion accommodation technique depends on the following parameters: transmitter output power, fibre attenuation coefficient, fibre core area, fibre non-linear index, transmitter wavelength, transmitter prechirp, and fibre chromatic dispersion.
+
+In 10 Gbit/s systems with a target distance of 80 km and with non-dispersion shifted fibres, SPM can be used as a dispersion accommodation technique with transmitter output powers up to +17 dBm, and with dispersion shifted fibres up to +13 dBm with a penalty of less than 1.5 dB.
+
+### **II.3 SPM-breakdown**
+
+There is an upper limit for the transmitter output power. This limit is given by the SPM-breakdown. The SPM-breakdown power level is defined as the transmitter power for which the leading edge and the trailing edge of the pulse coincide. If the transmitter power is increased above the SPM-breakdown level, it will lead to a dramatic penalty increase.
+
+The dominating parameters in determining the SPM-breakdown power level are the rise and fall times, and the extinction ratio. Both parameters are used to control the time derivative of the optical power and thus the SPM. The other parameters (e.g., fibre attenuation coefficient, fibre effective core area, etc.) have a minor influence on the SPM-breakdown power level compared to these parameters.
+
+## **II.4 Optical parameter values for applications**
+
+Following the principle of SPM for STM-64 systems, a more precise description of the spectral behaviour than the pure spectral width value of the transmitted optical signal is in principle required. The most important additional parameter is the source chirp, mostly described as the $\alpha$ -parameter in case of directly modulated sources. It has to be noted, that if this value is specified, it has to be done not only for small signal operation, but for large signal operation in the non-linear optical regime of the fibres as well.
+
+There are measurement methods for this parameter. However, the simplest method is to measure the transmission behaviour in conjunction with the related optical path. That means, in principle it is not really necessary to specify this parameter, but to specify a table where the receiver and transmitter values have to be considered together with the path. That means the transmitter spectral behaviour is defined indirectly in conjunction with receiver sensitivity and path characteristics, in this case namely dispersion and attenuation.
+
+## **II.5 Source type**
+
+The optical source type for 10 Gbit/s L- and V-type, intensity modulated, signals can normally be an indirectly modulated laser, where both Mach-Zehnder or electro-absorption modulator implementations can be used. Integrated with the optical transmitter, a booster amplifier is normally used to achieve the necessary transmitter power levels. However, the implementations are not subject to be standardized, and the only relevant values are those specified in Tables 4 and 5. In addition to these values, the definition of the eye mask is necessary in order to achieve transverse compatibility.
+
+## **II.6 Eye pattern mask**
+
+The general transmitter pulse shape characteristic including rise- and fall-times, and pulse over- and under-shoot, which should be controlled in order to prevent degradation, should be specified in form of an eye mask. This eye mask is valid at the reference point MPI-S.
+
+## **II.7 Receiver**
+
+For these systems implementing an intensity modulation scheme, direct detection receiver implementations can be used. However, the implementation is not subject to standardization. The required sensitivity and reflectance values are given in Tables 4 and 5.
+
+# Appendix III
+
+## Dispersion accommodation by means of DST
+
+### III.1 Introduction
+
+Dispersion supported transmission (DST) is an active dispersion accommodation (DA) technique. The transmitter generates an optical signal that includes a suitable optical frequency modulation. The chromatic dispersion of transmission fibre is used to convert the optical frequency modulation into an intensity modulation at the receiver. Using this effect, transmission beyond the typical dispersion limit (for conventional ASK modulation with ideal transform limited source spectrum) is possible. This appendix considers a tutorial description of the DST technique and DST system parameters and values.
+
+## III.2 Principle of the DST technique
+
+The optical transmitter generates an optical FSK/ASK (or a pure optical FSK) output signal in the new transmission scheme. The dispersive fibre is used to convert the FSK signal part at transmitter side into an ASK signal part at the receiver side. The full ASK signal is then detected by the optical receiver.
+
+By the incoming binary signal the optical frequency $\nu$ is switched between two values with the frequency shift $\Delta\nu$ , corresponding to the wavelength shift: $\Delta\lambda = \Delta\nu\lambda^2/c$ . Owing to the fibre dispersion, the different signal components with different wavelengths arrive at different times at the output of the fibre of length $L$ . The time difference $\Delta\tau$ is given by $\Delta\tau = \Delta\lambda D L$ . On the receiver side a 4- (or 3-) level signal is generated. The original signal can be recovered by:
+
+- a) a low-pass filter and a decision circuit with single threshold; or
+- b) a dual-threshold detection with threshold $P_1$ and $P_0$ and memory.
+
+In Figure III.1, the principle of "dispersion supported transmission" is shown for transmitter signals a) and receiver signals b), where $I$ indicates the transmitter driving signal, $\nu$ the optical frequency, $P_{\text{opt}}$ the optical input power, $V_{\text{LP}}$ the voltage at low-pass filter (LP) output and $V_{\text{dec}}$ the voltage at the decision circuit output.
+
+
+
+Figure III.1/G.691 – Principle of dispersion supported transmission; optical FSK/ASK transmission. The figure is divided into two parts: (a) Transmitter signals and (b) Receiver signals after dispersive fibre of length L. Part (a) shows three waveforms: current I, voltage V, and optical power P\_opt, all exhibiting square-like pulses. Part (b) shows five waveforms over time. From top to bottom: voltage V (showing a step-like transition with a time interval Δτ marked), optical power P\_opt (with levels P1 and P0 marked), low-pass filtered voltage V\_LP (showing smoothed versions of the pulses), and decision voltage V\_dec (showing a square-like pulse). A time interval 1/B is marked at the bottom right. The text 'time →' is present. The label 'G.691\_FIII.1' is in the bottom right corner.
+
+**Figure III.1/G.691 – Principle of dispersion supported transmission;
+optical FSK/ASK transmission**
+
+The principle of DST can also be described using a small signal analysis in the frequency domain: the adiabatic chirping (optical frequency modulation) of the transmitted optical signal in combination with the effect of the chromatic dispersion of the fibre leads to a high-pass-like transfer characteristic for low frequencies. This response can be equalized in the electrical domain by, e.g., using a low-pass filter ("DST-filter") in the receiver.
+
+## III.3 Optical receiver eye pattern mask after dispersive fibre transmission
+
+In contrast to a 2-level receiver eye diagram of a pure optical ASK signal, a pure optical FSK signal shows a 3-level receiver eye diagram and a joint FSK/ASK signal shows a 4-level receiver eye diagram after dispersive fibre transmission as indicated in Figure III.2 a) and b), respectively.
+
+
+
+Figure III.2/G.691 – Receiver eye diagrams after dispersive fibre. The figure contains two eye diagrams. Diagram (a) shows a 'Pure optical FSK signal of transmitter' with two overlapping waveforms forming an eye shape. Diagram (b) shows a 'joint optical FSK/ASK signal of transmitter' with more complex waveforms and a vertical axis labeled P\_opt and a horizontal axis labeled t. The text 'G.691\_FIII.2' is present in the bottom right of diagram (b).
+
+**Figure III.2/G.691 – Receiver eye diagrams after dispersive fibre**
+
+## III.4 Parameter definitions
+
+Only parameters with definitions unique to DST, or otherwise requiring comments, are defined here. Other parameters are defined in clause 6, and are fully applicable to the DST method if no other definition is given in this subclause.
+
+### III.4.1 Transmitter at reference point MPI-S
+
+#### III.4.1.1 Frequency deviation
+
+The frequency deviation is used to ensure that the transmit signal has the appropriate amount of optical frequency modulation for the transmission range in question.
+
+The frequency deviation $\Delta\nu$ of the transmitted optical signal at reference point MPI-S is defined by $\Delta\nu = \nu_1 - \nu_0$ , where $\nu_1$ is the optical frequency $\nu$ during transmission of a signal representing a logical "1" symbol (also corresponding to a high optical power level), and $\nu_0$ is the optical frequency during transmission of a signal representing a logical "0" symbol (also corresponding to a low optical power level).
+
+##### III.4.1.1.1 Measurement method
+
+The measurement set-up described in Appendix IV can be applied. The variables $V^+(t)$ and $V^-(t)$ are evaluated as described in Appendix IV. The time resolved frequency chirping $\nu_c(t) = \nu(t) - \nu_r$ is given by:
+
+$$v_c(t) = (2\pi)^{-1} FSR \arcsin\left(\frac{V^-(t)}{V^+(t)}\right)$$
+
+$v_c(t)$ is calculated and plotted together with $P(t)$ , compare with Figure IV.4.
+
+$v_1 - v_r$ is evaluated from $v_c(t)$ in the middle of the third bit of the A1 byte (11110110).
+
+$v_0 - v_r$ is evaluated from $v_c(t)$ in the middle of the last bit of the A2 byte (00101000).
+
+The frequency deviation is evaluated from $\Delta v = v_1 - v_0 = (v_1 - v_r) - (v_0 - v_r)$ .
+
+(An alternative evaluation of the frequency deviation using the test pattern shown in Figure II.1/G.957 is for further study.)
+
+#### III.4.1.2 Transmitter eye pattern mask
+
+As for pure IM systems, the transmitter eye mask is used to specify transmitter pulse shape characteristics and degradations. Since DST systems employ both intensity modulation as well as frequency modulation to convey the information, two eye mask measurement techniques are used to characterize the optical transmitter signal at reference point MPI-S.
+
+###### III.4.1.2.1 IM eye mask
+
+The IM eye mask definition specifies the intensity modulated part of the signal, and is identical to the IM eye mask definition and use in 6.2.4. Values for the IM eye mask as defined in 6.2.4, Figure 2, are given in Table III.1 below:
+
+**Table III.1/G.691 – Values for the IM eye mask for DST systems**
+
+| STM-64 IM eye mask (DST) | |
+|--------------------------|---------|
+| $x_1/x_4$ | – |
+| $x_2/x_3$ | – |
+| $x_3 - x_2$ | 0.2 |
+| $y_1/y_2$ | 0.3/0.6 |
+
+###### III.4.1.2.2 FM/IM eye mask
+
+The FM/IM eye mask has the corresponding function for the frequency modulation used to counter the link dispersion. To visualize also the FM-part of the signal, the FM/IM-mask test includes a specified FM to IM conversion and a specified frequency response of the reference receiver in the eye mask measurement set-up. The FM/IM eye mask measurement set-up is described in the following.
+
+The measurement set-up is similar to the set-up described in Figure B.1/G.957. In addition, the new measurement set-up includes:
+
+- i) a dispersive element that has a chromatic dispersion equivalent to a defined length of fibre according to ITU-T Rec. G.652; and
+- ii) an optical pre-amplifier for compensation of the attenuation of the dispersive element.
+
+The additional equipment i) and ii) is located between the transmitter under test and the optical input of the reference receiver. The transfer function $H(p)$ of the optical reference receiver is defined by (see Figure B.2/G.957):
+
+$$H(p) = \frac{U_0}{2U_2}$$
+
+For the FM/IM eye mask measurement, the following transfer function of the reference receiver is used:
+
+$$H = H_B \cdot H_D$$
+
+where $H_B$ represents a fourth-order Bessel-Thomson response according to Annex B/G.957, and $H_D$ first order low-pass filter given by:
+
+$$H_D = \left(1 + j \frac{f}{f_g}\right)^{-1} = \left(1 + \frac{f_r}{f_g} p\right)^{-1} = \left(1 + 0.75 \frac{f_0}{f_g} p\right)^{-1} = \left(1 + \frac{0.75}{2.114} \frac{f_0}{f_g} y\right)^{-1}$$
+
+where:
+
+$$p = j \frac{\omega}{\omega_r}, y = 2.114 p, \omega_r = 1.5\pi f_0, f_0 = \text{bit rate}, f_r = 0.75 f_0$$
+
+with cut-off frequency $f_g$ .
+
+The filter can be realized in hardware. As an alternative, it is proposed to realize the filter in software using, e.g., a PC or an eye diagram analyser; this is for further study.
+
+The characteristic values of the dispersive element that has a chromatic dispersion equivalent to a defined length of fibre according to ITU-T Rec. G.652 and the receiver filter cut-off frequency $f_g$ used in the measurement set-up are given in Table III.2 below:
+
+**Table III.2/G.691 – DST filter values**
+
+| | Unit | DST L-64.2/1 | DST L-64.2/2 | DST V-64.2 |
+|--------------------------------------------------|------|--------------|--------------|------------|
+| Filter cut-off frequency | MHz | 2500 | 2500 | 1400 |
+| Equivalent length of fibre (ITU-T Rec. G.652) | km | 80 | 80 | 120 |
+
+After this signal conversion in the dispersive element and including the modified frequency response of the reference receiver for the eye mask measurement, the definition and procedure is identical to the IM eye mask definition and use in 6.2.4.
+
+Values for the FM/IM eye mask are given in Table III.3:
+
+**Table III.3/G.691 – Values for the FM/IM eye mask for DST systems**
+
+| STM-64 FM/IM eye mask (DST) | |
+|-----------------------------|---------|
+| $x_1/x_4$ | – |
+| $x_2/x_3$ | – |
+| $x_3 - x_2$ | 0.2 |
+| $y_1/y_2$ | 0.3/0.6 |
+
+### III.4.2 Receiver at reference point MPI-R
+
+#### III.4.2.1 Minimum sensitivity
+
+Receiver sensitivity is defined as the minimum acceptable value of average received power at point MPI-R to achieve a $1 \times 10^{-12}$ BER. In DST systems, the receiver sensitivity definition includes a dispersive element between MPI-S and MPI-R. The chromatic dispersion of this dispersive element is equal to the minimum chromatic dispersion defined for the considered target distance, and the
+
+values are given in Table III.4. All other requirements on the receiver sensitivity as in 6.4.1 also apply to the DST receiver.
+
+In the main body of this Recommendation, details on the realization of the receiver, e.g., a specification of specific filter transfer function, are not given. Only the filter transfer function in the measurement set-up for the transmitter eye mask is standardized in Annex B/G.957. This does not imply that the optical receiver in the transmission system has the same filter transfer function.
+
+The same strategy applies for DST systems: only the filter transfer functions of the reference receivers for the transmitter eye-mask measurements are standardized. The filter transfer function in the optical receiver of the transmission system is not subject to standardization. A low-pass filter may be applied in the receiver; however, also a different approach using a specialized decision circuit capable of detecting multi-level eye diagrams may be employed.
+
+##### III.4.2.2 Maximum optical path penalty
+
+The definition of path penalty is given in 6.4.3. This definition is also applied for DST systems, taking into account the definition of receiver sensitivity for DST systems given above.
+
+## III.5 Optical parameter values
+
+Optical parameter values are given in Table III.4.
+
+**Table III.4/G.691 – Parameters values for STM-64 optical interfaces using DST**
+
+| Application code | Unit | DST L-64.2/1 | DST L-64.2/2 | DST V-64.2 |
+|-----------------------------------------------------------|--------|--------------|--------------|------------|
+| Transmitter at reference point MPI-S | | | | |
+| Operating wavelength range | nm | 1530-1565 | 1530-1565 | 1530-1565 |
+| Mean launched power | | | | |
+| – maximum | dBm | 3 | 13 | 17 |
+| – minimum | dBm | 0 | 10 | 14 |
+| Spectral characteristics | | | | |
+| – maximum chirp parameter $\alpha$ | rad | 3.5 | 3.5 | 3.5 |
+| – maximum frequency deviation | GHz | 8 | 8 | 6 |
+| – minimum frequency deviation | GHz | 7 | 7 | 5 |
+| – maximum spectral power density | mW/MHz | 0.02 | 0.02 | 0.02 |
+| – minimum SMSR | dB | 35 | 35 | 35 |
+| Minimum EX | dB | 3 | 3 | 2 |
+| Main optical path, MPI-S to MPI-R | | | | |
+| Attenuation range | | | | |
+| – maximum | dB | 22 | 22 | 33 |
+| – minimum | dB | 11 | 16 | 22 |
+| Chromatic dispersion | | | | |
+| – maximum | ps/nm | 1600 | 1600 | 2400 |
+| – minimum | ps/nm | 800 | 800 | 1600 |
+| Passive dispersion compensation | | | | |
+| – maximum | ps/nm | NA | NA | NA |
+| – minimum | ps/nm | NA | NA | NA |
+| Maximum DGD | ps | 30 | 30 | 30 |
+| Min ORL of cable plant at MPI-S, including any connectors | dB | 24 | 24 | 24 |
+
+**Table III.4/G.691 – Parameters values for STM-64 optical interfaces using DST**
+
+| Application code | Unit | DST L-64.2/1 | DST L-64.2/2 | DST V-64.2 |
+|------------------------------------------------------|------|--------------|--------------|------------|
+| Maximum discrete reflectance between MPI-S and MPI-R | dB | -27 | -27 | -27 |
+| Receiver at reference point MPI-R | | | | |
+| Minimum sensitivity | dBm | -24 | -14 | -21 |
+| Minimum overload | dBm | -8 | -3 | -5 |
+| Maximum optical path penalty | dB | 2 | 2 | 2 |
+| Maximum reflectance of receiver, measured at MPI-R | dB | -27 | -27 | -27 |
+
+# Appendix IV
+
+## Measurement of the chirp parameter $\alpha$ of the optical transmit signal
+
+This method for measuring the chirp parameter $\alpha$ is based on a direct time domain measurement of the power and the frequency deviation of the optical transmit signal.
+
+### IV.1 Measurement set-up
+
+The recommended set-up for measuring the chirp parameter is based on an optical two-beam interferometer (e.g., a Michelson interferometer or a Mach-Zehnder interferometer) a broadband optical converter and a broadband digital oscilloscope, see Figure IV.1.
+
+
+
+$n = 2^{10} \times 3^5 \times 5$ (STM-64)
+ $n = 2^8 \times 3^5 \times 5$ (STM-16)
+
+G.691\_FIV.1
+
+Figure IV.1/G.691 – Measurement set-up diagram. An SDH terminal has two optical ports, R and S. Port R is connected to an O/E-converter, which is connected to a Clock-recovery block, which is connected to a Prescaler 1/n block. Port S is connected to an Interferometer, which is connected to another O/E-converter, which is connected to an Oscilloscope. The Prescaler 1/n block provides an 'Ext. Trigger' signal to the Oscilloscope. The SDH terminal also has two electrical ports, Trb and T3, which are connected to a PRBS-generator and a Clock-generator respectively. Below the diagram, the following equations are given: n = 2^10 x 3^5 x 5 (STM-64) and n = 2^8 x 3^5 x 5 (STM-16). The diagram is labeled G.691\_FIV.1.
+
+**Figure IV.1/G.691 – Measurement set-up**
+
+The optical output of the transmitter under test is connected at the reference point S to the two-beam interferometer. The output of the interferometer is connected to the optical converter and the electrical signal out of the converter is recorded by the broadband digital oscilloscope. The oscilloscope is triggered by a frame sync signal generated by pre-scaling a clock recovered from the optically received signal.
+
+In order to keep the transmitter turned on during the measurement, a fraction of the light to the interferometer is coupled to the optical receiver port of the transmitter equipment. A $2^{23}-1$ PRBS data generator is connected to the tributary ports, which are configured in the loop-back mode.
+
+## IV.2 Technical requirements for the measuring equipment
+
+#### Two-beam interferometer
+
+Free spectral range (FSR): At least four times larger than the chirp of the transmitter.
+
+#### Transmitter
+
+Off-set wavelength: Adjustable. The range must be equal to or larger than the free spectral range of the interferometer.
+
+The two-beam interferometer must have a control circuit which locks the interferometer to the input signal. This control circuit should allow to lock the interferometer to the input signal at quadrature point A as well as quadrature point B, see Figure IV.2.
+
+
+
+Figure IV.2/G.691 – Sketch of the transfer function of the two-beam interferometer. The graph shows Amplitude on the y-axis (0.00 to 1.00) versus Optical frequency on the x-axis. The curve is a periodic wave with peaks at 1.00 and troughs at 0.00. The distance between two consecutive peaks is labeled FSR. Two points, A and B, are marked on the curve at an amplitude of 0.50, labeled as 'Quadrature points'.
+
+Figure IV.2/G.691 – Sketch of the transfer function of the two-beam interferometer showing the quadrature points A and B and defining the free spectral range
+
+### Combined frequency response for the optical converter and the oscilloscope
+
+Low –3 dB cut-off frequency: <100 kHz
+
+High –3 dB cut-off frequency: >20 GHz
+
+The oscilloscope shall have a storage capacity of at least four traces and be able to perform advanced mathematical functions on the traces or have the capability to transfer the measured data trace to a computer for further processing.
+
+## IV.3 Calibration
+
+The free spectral range of the interferometer is determined by the delay $t_d$ related to the two optical paths inside the interferometer:
+
+$$FSR = \frac{1}{t_d}$$
+
+$t_d$ can either be measured directly by detecting the time difference in the arrival of data from each of the beams by using the oscilloscope or it can be measured indirectly by using a ruler and calculating
+
+the delay. The FSR can also be found by measuring the transfer function of the interferometer using a lightwave component analyser. The first zero in the transfer function occurs at a frequency equal to FSR/2.
+
+The quadrature point of the interferometer is adjusted to match the transmitter wavelength by fine tuning the FSR. The correct position is identified by monitoring the average power of the SDH transmitter signal through the interferometer as a function of the fine tuning of the FSR. The quadrature point is the position where the average power through the interferometer is halfway between the maximum and the minimum power on a linear scale. The interferometer shall be locked to the transmitter signal in this position.
+
+## IV.4 Measurement procedure
+
+- 1) Arrange the equipment as shown in Figure IV.1. Apply sufficient attenuation to the signal to the receiver to avoid overload.
+- 2) Configure the tributary input of the transmitter in the loop-back mode and connect the PRBS-generator to the first tributary input.
+- 3) Synchronize the transmitter to the recovered clock by configuring the timing source for the aggregate signal as T3 (external clock input).
+- 4) Calibrate the two-beam interferometer in accordance with IV.3. Lock the interferometer to the quadrature point A.
+- 5) Adjust the time delay on the digital oscilloscope until the framing bytes A1 A2 of the SDH overhead is displayed on the oscilloscope. Record the trace of the transition from the A1 to the A2 byte (11110110 to 00101000) and store the trace as $V_A(t)$ .
+- 6) Lock the interferometer to the quadrature point B.
+- 7) Store the trace of the data on the oscilloscope as $V_B(t)$ .
+
+## IV.5 Data processing
+
+The chirp parameter is determined by the sum and the difference between $V_A(t)$ and $V_B(t)$ . Therefore the variables $V^+(t)$ and $V^-(t)$ are defined:
+
+$$V^+_{(t)} = \frac{V_A(t) + V_B(t)}{2}$$
+
+$$V^-_{(t)} = \frac{V_A(t) - V_B(t)}{2}$$
+
+The time varying intensity $P(t)$ of the transmitter is proportional to $V^+(t)$ . The chirp parameter is calculated as:
+
+$$\alpha(t) = 2 \times FSR \times \frac{V^+_{(t)} \times \arcsin \frac{V^-_{(t)}}{V^+_{(t)}}}{\frac{\partial V^+_{(t)}}{\partial t}}$$
+
+$P(t)$ and $\alpha(t)$ are calculated and plotted on the same graph. The chirp parameter of the transmitter is defined as the value of $\alpha(t)$ calculated at the time where the intensity $P(t)$ is half-way between the level representing the "0" and the "1" symbols of the data.
+
+## IV.6 Examples and interpretation of data
+
+In Figure IV.3, an example of the measured result of the two traces $V_A(t)$ and $V_B(t)$ is shown measured on a PRBS signal with a bit rate of 10 Gbit/s.
+
+![Figure IV.3/G.691: Data traces of a 10 Gbit/s PRBS signal measured with the interferometer adjusted to the quadrature points A and B, respectively. The plot shows two traces, V_B(t) (solid line) and V_A(t) (dashed line), over a time range from -600 ps to 600 ps. The y-axis represents Amplitude [A.U.] from -0.20 to 1.00. The traces show periodic pulses with a period of approximately 200 ps. The solid trace V_B(t) has a peak amplitude of about 0.9, while the dashed trace V_A(t) has a peak amplitude of about 0.8. The x-axis is labeled 'Time [ps]' and the plot is identified by 'G.691_FIV.3'.](7fdd9eacc17f06e094850c6755b47418_img.jpg)
+
+Figure IV.3/G.691: Data traces of a 10 Gbit/s PRBS signal measured with the interferometer adjusted to the quadrature points A and B, respectively. The plot shows two traces, V\_B(t) (solid line) and V\_A(t) (dashed line), over a time range from -600 ps to 600 ps. The y-axis represents Amplitude [A.U.] from -0.20 to 1.00. The traces show periodic pulses with a period of approximately 200 ps. The solid trace V\_B(t) has a peak amplitude of about 0.9, while the dashed trace V\_A(t) has a peak amplitude of about 0.8. The x-axis is labeled 'Time [ps]' and the plot is identified by 'G.691\_FIV.3'.
+
+**Figure IV.3/G.691 – Data traces of a 10 Gbit/s PRBS signal measured with the interferometer adjusted to the quadrature points A and B, respectively**
+
+Figure IV.4 shows a plot of the calculation of $P(t)$ and $\alpha(t)$ as described in clause IV.5.
+
+![Figure IV.4/G.691: Plot of the calculated values for P(t) and alpha(t). The plot shows two traces over a time range from -600 ps to 600 ps. The y-axis represents Amplitude [A.U.] or alpha(t) from -2.00 to 1.00. The trace P(t) (solid line) shows pulses with a peak amplitude of about 0.8. The trace alpha(t) (dashed line) shows values ranging from -1.5 to 0.5. Two arrows indicate the calculation of the chirp parameter: one vertical arrow points from the zero line to the peak of P(t) at approximately -400 ps, and one horizontal arrow points from the zero line to the minimum of alpha(t) at approximately -400 ps. The x-axis is labeled 'Time [ps]' and the plot is identified by 'G.691_FIV.4'.](07c5a1c0fddd7da92a8427f5af840ffa_img.jpg)
+
+Figure IV.4/G.691: Plot of the calculated values for P(t) and alpha(t). The plot shows two traces over a time range from -600 ps to 600 ps. The y-axis represents Amplitude [A.U.] or alpha(t) from -2.00 to 1.00. The trace P(t) (solid line) shows pulses with a peak amplitude of about 0.8. The trace alpha(t) (dashed line) shows values ranging from -1.5 to 0.5. Two arrows indicate the calculation of the chirp parameter: one vertical arrow points from the zero line to the peak of P(t) at approximately -400 ps, and one horizontal arrow points from the zero line to the minimum of alpha(t) at approximately -400 ps. The x-axis is labeled 'Time [ps]' and the plot is identified by 'G.691\_FIV.4'.
+
+**Figure IV.4/G.691 – Plot of the calculated values for $P(t)$ and $\alpha(t)$ ; The arrows show how to find the chirp parameter**
+
+The chirp parameter can be calculated on the leading and the trailing edges of the data pulses. In Figure IV.4 the identification of the chirp parameter is shown for the first leading edge of the pulses in the trace. The chirp parameter varies slightly depending on the position of the pulse in the trace. The minimum and the maximum chirp parameter over the pattern shall be within the specified limits for the system.
+
+How the chirp parameter influences the system performance is for further study. Whether the chirp parameter is to be calculated on the leading or trailing edge, as an average, or as a worst case is also for further study.
+
+# Appendix V
+
+## Upgradability considerations
+
+One example of upgrades to higher bit rates is from an STM-16, line-amplified single-channel system to STM-64. A 640-km-long STM-16 regenerating span with seven line amplifiers, for example, can be upgraded to STM-64 by replacing the line amplifier at the middle with a regenerator while the rest of the line amplifiers and their span remain unchanged. Figure V.1 shows this upgrade.
+
+
+
+The diagram illustrates two optical transmission paths. The top path, labeled 'STM-64', consists of nine square components connected in series. The first, fifth, and ninth components are labeled 'Regenerator' and contain a black triangle pointing right. The second, third, fourth, sixth, seventh, and eighth components are labeled 'Line amplifiers' and contain a white triangle pointing right. The bottom path, labeled 'STM-16', also consists of nine square components. The first and ninth components are 'Regenerator' (black triangle), while the second through eighth components are 'Line amplifiers' (white triangles). A vertical arrow labeled 'Upgrade' points from the STM-16 path to the STM-64 path, indicating the replacement of the fifth component (a line amplifier in STM-16) with a regenerator in STM-64. The label 'G.691\_FV.1' is located at the bottom right of the diagram.
+
+Diagram illustrating the upgrade from STM-16 to STM-64. The top path (STM-64) shows a sequence of nine components: Regenerator, Line amplifier, Line amplifier, Line amplifier, Regenerator, Line amplifier, Line amplifier, Line amplifier, Regenerator. The bottom path (STM-16) shows a sequence of nine components: Regenerator, Line amplifier, Line amplifier, Line amplifier, Line amplifier, Line amplifier, Line amplifier, Line amplifier, Regenerator. An arrow labeled 'Upgrade' points from the STM-16 path to the STM-64 path, indicating the replacement of the middle line amplifier with a regenerator.
+
+**Figure V.1/G.691 – An example of upgrading from STM-16 to STM-64**
+
+Upgrades from STM-4 to STM-16 would have no practical merit because STM-4 systems with line amplifiers would not be cost effective unless the line amplifier cost is greatly reduced.
+
+
+
+# SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|---------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/G/T-REC-G.694.2-200312-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.694.2-200312-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30
--- /dev/null
+++ b/marked/G/T-REC-G.694.2-200312-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359
+size 8245
diff --git a/marked/G/T-REC-G.694.2-200312-I_PDF-E/raw.md b/marked/G/T-REC-G.694.2-200312-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..b855b2fb47d34b8369e08d9a3f0b3c3fa71cb990
--- /dev/null
+++ b/marked/G/T-REC-G.694.2-200312-I_PDF-E/raw.md
@@ -0,0 +1,257 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**G.694.2**
+
+(12/2003)
+
+SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
+DIGITAL SYSTEMS AND NETWORKS
+
+Transmission media characteristics – Characteristics of
+optical components and subsystems
+
+---
+
+**Spectral grids for WDM applications: CWDM
+wavelength grid**
+
+ITU-T Recommendation G.694.2
+
+---
+
+# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS**
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 |
+| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 |
+| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 |
+| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 |
+| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 |
+| TESTING EQUIPMENTS | G.500–G.599 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.600–G.699 |
+| General | G.600–G.609 |
+| Symmetric cable pairs | G.610–G.619 |
+| Land coaxial cable pairs | G.620–G.629 |
+| Submarine cables | G.630–G.649 |
+| Optical fibre cables | G.650–G.659 |
+| Characteristics of optical components and subsystems | G.660–G.699 |
+| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 |
+| DIGITAL NETWORKS | G.800–G.899 |
+| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 |
+| QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER-RELATED ASPECTS | G.1000–G.1999 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.6000–G.6999 |
+| DIGITAL TERMINAL EQUIPMENTS | G.7000–G.7999 |
+| DIGITAL NETWORKS | G.8000–G.8999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## **ITU-T Recommendation G.694.2**
+
+# **Spectral grids for WDM applications: CWDM wavelength grid**
+
+## **Summary**
+
+This Recommendation provides the wavelength grid for coarse wavelength division multiplexing (CWDM) applications. This wavelength grid supports a channel spacing of 20 nm.
+
+The wavelength grid in this version of this Recommendation has been moved by 1 nm to align it with current industry practice while maintaining symmetrical nominal central wavelength deviations.
+
+###### **Source**
+
+ITU-T Recommendation G.694.2 was approved on 14 December 2003 by ITU-T Study Group 15 (2001-2004) under the ITU-T Recommendation A.8 procedure.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2004
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+# CONTENTS
+
+| | Page |
+|-----------------------------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References..... | 1 |
+| 2.1 Normative references..... | 1 |
+| 2.2 Informative references..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined in this Recommendation..... | 1 |
+| 3.2 Terms defined in other Recommendations..... | 1 |
+| 4 Abbreviations and acronyms ..... | 2 |
+| 5 Coarse WDM and its applications ..... | 2 |
+| 6 Nominal central wavelengths for coarse WDM systems..... | 2 |
+| Appendix I – Central wavelength spacing and wavelength variation..... | 3 |
+| Appendix II – Wavelength allocation ..... | 4 |
+
+
+
+# Spectral grids for WDM applications: CWDM wavelength grid
+
+# 1 Scope
+
+The purpose of this Recommendation is to provide the definition of a wavelength grid to support coarse wavelength division multiplexing (CWDM) applications. This grid is designed to allow simultaneous transmission of several wavelengths with sufficient separation to permit the use of uncooled sources.
+
+# 2 References
+
+## 2.1 Normative references
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [1] ITU-T Recommendation G.671 (2002), *Transmission characteristics of optical components and subsystems*.
+
+## 2.2 Informative references
+
+The following ITU-T Recommendations contain other relevant information.
+
+- [2] ITU-T Recommendation G.983.3 (2001), *A broadband optical access system with increased service capability by wavelength allocation*.
+- [3] ITU-T Recommendation J.185 (2002), *Transmission equipment for transferring multi-channel television signals over optical access networks by FM conversion*.
+- [4] ITU-T Recommendation J.186 (2002), *Transmission equipment for multi-channel television signals over optical access networks by sub-carrier multiplexing (SCM)*.
+
+# 3 Definitions
+
+## 3.1 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+- 3.1.1 wavelength grid:** A wavelength grid is a reference set of vacuum optical wavelengths used to denote allowed nominal central wavelengths that may be used in defining applications.
+
+## 3.2 Terms defined in other Recommendations
+
+This Recommendation uses terms defined in ITU-T Rec. G.671:
+
+- Coarse Wavelength Division Multiplexing (CWDM).
+- Dense Wavelength Division Multiplexing (DWDM).
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|------|-----------------------------------------|
+| CWDM | Coarse Wavelength Division Multiplexing |
+| DWDM | Dense Wavelength Division Multiplexing |
+| WDM | Wavelength Division Multiplexing |
+
+# 5 Coarse WDM and its applications
+
+Coarse Wavelength Division Multiplexing (CWDM), a WDM technology, is characterized by wider channel spacing than Dense WDM (DWDM) as defined in ITU-T Rec. G.671. CWDM systems can realize cost-effective applications, through a combination of uncooled lasers, relaxed laser wavelength selection tolerances and wide passband filters.
+
+CWDM systems can be used in transport networks in metropolitan areas for a variety of clients, services and protocols.
+
+Appendix I provides an explanation of the rationale for choosing the central wavelength spacing and the determining factors of the wavelength variation.
+
+# 6 Nominal central wavelengths for coarse WDM systems
+
+The nominal central wavelengths for coarse WDM systems are used as a reference to define, for each channel used, an upper wavelength bound and a lower wavelength bound. These bounds define limits for the wavelength of the transmitter under all conditions and at the same time the wavelength limits over which the specifications of the optical multiplexers and demultiplexers must be met.
+
+The upper wavelength bound is the central wavelength of the channel plus the central wavelength deviation found in the Recommendation defining the application.
+
+The lower wavelength bound is the central wavelength of the channel minus the central wavelength deviation found in the Recommendation defining the application.
+
+The CWDM grid wavelengths within the range 1271 nm to 1611 nm are shown in Table 1. The value of "c" (speed of light in vacuum) that should be used for converting between wavelength and frequency is $2.99792458 \times 10^8$ m/s.
+
+**Table 1/G.694.2 – Nominal central wavelengths**
+
+| Nominal central wavelengths (nm) for spacing of 20 nm |
+|------------------------------------------------------------------|
+| 1271 |
+| 1291 |
+| 1311 |
+| 1331 |
+| 1351 |
+| 1371 |
+| 1391 |
+| 1411 |
+| 1431 |
+| 1451 |
+| 1471 |
+| 1491 |
+| 1511 |
+| 1531 |
+| 1551 |
+| 1571 |
+| 1591 |
+| 1611 |
+| NOTE – The endpoints of this table are illustrative only. |
+
+## **Appendix I**
+
+## **Central wavelength spacing and wavelength variation**
+
+Effective CWDM realizations with uncooled lasers and wide passband filters require a nominal central wavelength spacing of not less than 20 nm. Total source wavelength variation of the order of $\pm 6$ -7 nm is expected to be compatible with current filter technologies. As for the guardband, one third of the minimum channel spacing is sufficient. Therefore, in order to maximize the number of channels, 20 nm has been chosen.
+
+Specific values and allocations of this variation will be defined in individual applications.
+
+The wavelength variation is determined by mainly two factors. First, the laser manufacturer is allowed a wavelength variation around the nominal wavelength in order to achieve a higher yield and/or relax fabrication tolerances. Second, the use of uncooled lasers will cause the wavelength to change with temperature within the specified temperature range of the laser.
+
+# **Appendix II**
+
+### **Wavelength allocation**
+
+ITU-T Rec. G.983.3 (March 2001) defines the wavelength allocation for video distribution signals multiplexed with B-PON. ITU-T Recs J.185 and J.186 (February 2002) define the wavelength allocation for transferring multi-channel television signals.
+
+
+
+# SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure, Internet protocol aspects and Next Generation Networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/G/T-REC-G.698.2-201811-I_PDF-E/raw.md b/marked/G/T-REC-G.698.2-201811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..2c4d99f25b3774d716a716ceff7827e058185974
--- /dev/null
+++ b/marked/G/T-REC-G.698.2-201811-I_PDF-E/raw.md
@@ -0,0 +1,1444 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**G.698.2**
+
+(11/2018)
+
+SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
+DIGITAL SYSTEMS AND NETWORKS
+
+Transmission media and optical systems characteristics –
+Characteristics of optical systems
+
+---
+
+**Amplified multichannel dense wavelength
+division multiplexing applications with single
+channel optical interfaces**
+
+Recommendation ITU-T G.698.2
+
+# ITU-T G-SERIES RECOMMENDATIONS
+
+## TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 |
+| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 |
+| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 |
+| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 |
+| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 |
+| TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS | G.600–G.699 |
+| General | G.600–G.609 |
+| Symmetric cable pairs | G.610–G.619 |
+| Land coaxial cable pairs | G.620–G.629 |
+| Submarine cables | G.630–G.639 |
+| Free space optical systems | G.640–G.649 |
+| Optical fibre cables | G.650–G.659 |
+| Characteristics of optical components and subsystems | G.660–G.679 |
+| Characteristics of optical systems | G.680–G.699 |
+| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 |
+| DIGITAL NETWORKS | G.800–G.899 |
+| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 |
+| MULTIMEDIA QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER-RELATED ASPECTS | G.1000–G.1999 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.6000–G.6999 |
+| DATA OVER TRANSPORT – GENERIC ASPECTS | G.7000–G.7999 |
+| PACKET OVER TRANSPORT ASPECTS | G.8000–G.8999 |
+| ACCESS NETWORKS | G.9000–G.9999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## Recommendation ITU-T G.698.2
+
+# Amplified multichannel dense wavelength division multiplexing applications with single channel optical interfaces
+
+## Summary
+
+Recommendation ITU-T G.698.2 provides optical parameter values for physical layer interfaces of dense wavelength division multiplexing (DWDM) systems primarily intended for metro applications which include optical amplifiers. Applications are defined using optical interface parameters at the single-channel connection points between optical transmitters and the optical multiplexer, as well as between optical receivers and the optical demultiplexer in the DWDM system. This Recommendation uses a methodology which does not specify the details of the optical link, e.g., the maximum fibre length, explicitly. This version of this Recommendation includes unidirectional DWDM applications at 100 Gbit/s with 100 GHz and 50 GHz channel frequency spacing.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T G.698.2 | 2007-07-29 | 15 | 11.1002/1000/9183 |
+| 2.0 | ITU-T G.698.2 | 2009-11-13 | 15 | 11.1002/1000/10396 |
+| 3.0 | ITU-T G.698.2 | 2018-11-29 | 15 | 11.1002/1000/13740 |
+
+## Keywords
+
+100G, 10G, 2.5G, application codes, black link, DWDM, metro, multi-vendor, OADM, optical.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2019
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|----------------------------------------------------------------------------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Terms and definitions ..... | 2 |
+| 3.1 Terms defined elsewhere ..... | 2 |
+| 3.2 Terms defined in this Recommendation..... | 3 |
+| 4 Abbreviations and acronyms ..... | 3 |
+| 5 Classification of optical interfaces..... | 4 |
+| 5.1 Applications..... | 4 |
+| 5.2 Reference points ..... | 4 |
+| 5.3 Nomenclature ..... | 7 |
+| 5.4 Single-channel interfaces at the reference points S S and RS..... | 8 |
+| 6 Transverse compatibility ..... | 9 |
+| 7 Parameter definitions ..... | 10 |
+| 7.1 General information..... | 11 |
+| 7.2 Interface at point SS ..... | 12 |
+| 7.3 Optical path parameters from S S to RS ..... | 18 |
+| 7.4 Interface at point RS..... | 22 |
+| 8 Parameter values ..... | 24 |
+| 9 Optical safety considerations ..... | 34 |
+| Annex A – Reference receiver characteristics for DP-DQPSK 100G ..... | 35 |
+| Appendix I – Measurement of transmitter (residual) dispersion OSNR penalty and optical path OSNR penalty ..... | 36 |
+| Appendix II – Transponder elimination via single channel DWDM interfaces ..... | 38 |
+| Bibliography..... | 40 |
+
+
+
+## Recommendation ITU-T G.698.2
+
+## Amplified multichannel dense wavelength division multiplexing applications with single channel optical interfaces
+
+# 1 Scope
+
+The purpose of this Recommendation is to provide optical interface specifications towards the realization of transversely compatible dense wavelength division multiplexing (DWDM) systems primarily intended for metro applications which include optical amplifiers.
+
+This Recommendation defines and provides values for single-channel optical interface parameters of physical point-to-point and ring DWDM applications on single-mode optical fibres through the use of the "black link" approach. The black links covered by this Recommendation may contain optical amplifiers.
+
+The use of these single channel optical interfaces for DWDM systems enables the elimination of transponders which would otherwise be needed in multivendor DWDM optical transmission networks. Further details can be found in Appendix II.
+
+This Recommendation describes single channel interfaces to DWDM systems that include the following features:
+
+- channel frequency spacing: 50 GHz and wider (defined in [ITU-T G.694.1]);
+- bit rate of signal channel: Up to 100 Gbit/s.
+
+Specifications are organized according to application codes.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T G.652] Recommendation ITU-T G.652 (2016), *Characteristics of a single-mode optical fibre and cable*.
+- [ITU-T G.653] Recommendation ITU-T G.653 (2010), *Characteristics of a dispersion-shifted single-mode optical fibre and cable*.
+- [ITU-T G.655] Recommendation ITU-T G.655 (2006), *Characteristics of a non-zero dispersion-shifted single-mode optical fibre and cable*.
+- [ITU-T G.664] Recommendation ITU-T G.664 (2009), *Optical safety procedures and requirements for optical transport systems*.
+- [ITU-T G.671] Recommendation ITU-T G.671 (2012), *Transmission characteristics of optical components and subsystems*.
+- [ITU-T G.691] Recommendation ITU-T G.691 (2006), *Optical interfaces for single channel STM-64 and other SDH systems with optical amplifiers*.
+- [ITU-T G.692] Recommendation ITU-T G.692 (1998), *Optical interfaces for multichannel systems with optical amplifiers*.
+
+- [ITU-T G.694.1] Recommendation ITU-T G.694.1 (2012), *Spectral grids for WDM applications: DWDM frequency grid.*
+- [ITU-T G.709] Recommendation ITU-T G.709/Y.1331 (2016), *Interfaces for the Optical Transport Network (OTN).*
+- [ITU-T G.709.2] Recommendation ITU-T G.709.2/Y.1331.2 (2018), *OTU4 long-reach interface.*
+- [ITU-T G.709.3] Recommendation ITU-T G.709.3/Y.1331.3 (2018), *Flexible OTN long-reach interfaces.*
+- [ITU-T G.957] Recommendation ITU-T G.957 (2006), *Optical interfaces for equipments and systems relating to the synchronous digital hierarchy.*
+- [ITU-T G.959.1] Recommendation ITU-T G.959.1 (2018), *Optical transport network physical layer interfaces.*
+- [IEC 60825-1] IEC 60825-1:2014, *Safety of laser products – Part 1: Equipment classification and requirements.*
+- [IEC 60825-2] IEC 60825-2:2010, *Safety of laser products – Part 2: Safety of optical fibre communication systems (OFCS).*
+
+# 3 Terms and definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined in [ITU-T G.671]:
+
+- Dense Wavelength Division Multiplexing (DWDM);
+- Channel insertion loss;
+- Reflectance;
+- Ripple;
+- Channel spacing;
+- Differential group delay;
+- Reflectance.
+
+This Recommendation uses the following term defined in [ITU-T G.691]:
+
+- (Optical) transponder.
+
+This Recommendation uses the following term defined in [ITU-T G.694.1]:
+
+- Frequency grid.
+
+This Recommendation uses the following term defined in [ITU-T G.709]:
+
+- Completely standardized OTUk (OTUk).
+
+This Recommendation uses the following terms defined in [ITU-T G.709.2]:
+
+- OTL4.4-SC;
+- OTU4-SC.
+
+This Recommendation uses the following term defined in [ITU-T G.709.3]:
+
+- FOIC1.4-SC.
+
+This Recommendation uses the following terms defined in [ITU-T G.957]:
+
+- Joint engineering;
+
+- Transverse compatibility.
+
+This Recommendation uses the following terms defined in [ITU-T G.959.1]:
+
+- Optical tributary signal;
+- Optical tributary signal class NRZ 2.5G;
+- Optical tributary signal class NRZ 10G.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 optical tributary signal class DP-DQPSK 100G:** A class of continuous digital signals with non-return to zero differential quadrature phase shift keying modulation applied separately to two orthogonal polarizations of a carrier, operating at a total bit rate from nominally 103.1 Gbit/s to nominally 112.74 Gbit/s. Optical tributary signal class DP-DQPSK 100G includes a signal with FOIC1.4-SC bit rate according to [ITU-T G.709.3] and OTL4.4-SC bit rate according to [ITU-T G.709.2].
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|------------|----------------------------------------------------------------------------------------------------|
+| APD | Avalanche Photodiode |
+| ASE | Amplified Spontaneous Emission |
+| BER | Bit Error Ratio |
+| DGD | Differential Group Delay |
+| DP-DQPSK | Dual Polarization – Differential Quadrature Phase Shift Keying |
+| EX | Extinction ratio |
+| FEC | Forward Error Correction |
+| FIR | Finite Impulse Response |
+| FOIC1.4-SC | FlexO Interface of order C1 with 4 lanes |
+| NA | Not Applicable |
+| NE | Network Element |
+| NRZ | Non-Return to Zero |
+| OA | Optical Amplifier |
+| OADM | Optical Add-Drop Multiplexer |
+| OD | Optical Demultiplexer |
+| OM | Optical Multiplexer |
+| ONE | Optical Network Element |
+| OTL4.4-SC | Group of 4 Optical Transport Lanes that carry one OTU4-SC |
+| OTU4-SC | Completely standardized 100G Optical Transport Unit for long-reach applications with Staircase FEC |
+| OTUk | Completely standardized optical channel transport unit – k |
+| PDL | Polarization Dependent Loss |
+| PIN | P type-intrinsic-n type |
+
+| | |
+|----------------|-----------------------------------------------------------------------------|
+| PMD | Polarization Mode Dispersion |
+| R s | Single-channel reference point at the DWDM network element tributary output |
+| SOP | State of Polarization |
+| S s | Single-channel reference point at the DWDM network element tributary input |
+| VOA | Variable Optical Attenuator |
+| WDM | Wavelength Division Multiplexing |
+
+# 5 Classification of optical interfaces
+
+## 5.1 Applications
+
+This Recommendation provides the physical layer parameters and values for single-channel interfaces of DWDM multichannel optical systems in physical point-to-point and ring applications.
+
+The specification method in this Recommendation uses a "black link" approach, which means that optical interface parameters for only (single-channel) optical tributary signals are specified. Additional specifications are provided for the black link parameters, such as residual chromatic dispersion, ripple and polarization mode dispersion. This approach enables transverse compatibility at the single-channel point using a direct wavelength-multiplexing configuration. However, it does not enable transverse compatibility at the multichannel points.
+
+This Recommendation considers DWDM applications where the black link may contain optical amplifiers.
+
+## 5.2 Reference points
+
+### 5.2.1 Unidirectional applications
+
+Figure 5-1 shows a set of reference points, for the linear "black link" approach, for single-channel connection (Ss and Rs ) between transmitters (Tx) and receivers (Rx). Here the DWDM network elements include an optical multiplexer (OM) and an optical demultiplexer (OD) (which are used as a pair with the opposing element), one or more optical amplifiers and may also include one or more optical add-drop multiplexers (OADMs).
+
+The arrangement of elements within the black link shown in Figures 5-1 to 5-4 is not intended to place constraints on the construction of the black link, but simply to define the location of the single channel interfaces.
+
+
+
+Figure 5-1: Linear 'black link' approach diagram. A central 'DWDM network elements' block contains an Optical Multiplexer (OM), an Optical Add-Drop Multiplexer (OADM), and an Optical Demultiplexer (OD). On the left, multiple transmitters (Tx λ1, Tx λ2, ..., Tx λN) are connected to the OM via single-channel reference points Ss. On the right, the OD is connected to multiple receivers (Rx λ1, Rx λ2, ..., Rx λN) via single-channel reference points Rs. Below the main block, a 'DWDM link' is shown with its own Ss and Rs reference points, connected to a receiver (Rx λx) and a transmitter (Tx λy). The diagram is labeled G.698.2(09)\_F5-1.
+
+**Figure 5-1 – Linear "black link" approach**
+
+As indicated in Figure 5-1, in cases where the transmitter or receiver is some distance from the OM, OD or OADM, the fibre between point Ss or Rs and the DWDM network element is considered to be part of the black link.
+
+Figure 5-2 shows a corresponding set of reference points for the ring "black link" approach, for single-channel connection (Ss and Rs) between transmitters (Tx) and receivers (Rx). Here the DWDM network elements include one or more amplifiers and two or more OADMs connected in a ring.
+
+
+
+Figure 5-2: Ring 'black link' approach diagram. A central 'DWDM network elements' block contains a ring of four OADMs. Multiple transmitters (Tx) and receivers (Rx) are connected to the ring via single-channel reference points Ss and Rs. Below the main block, a 'DWDM link' is shown with its own Ss and Rs reference points, connected to a receiver (Rx) and a transmitter (Tx). The diagram is labeled G.698.2(09)\_F5-2.
+
+**Figure 5-2 – Ring "black link" approach**
+
+The reference points in Figures 5-1 and 5-2 are defined as follows:
+
+- Ss is a single-channel reference point at the DWDM network element tributary input;
+
+– $R_s$ is a single-channel reference point at the DWDM network element tributary output.
+
+Here, single-channel reference points $S_s$ and $R_s$ are applied to systems for the (linear or ring) "black link" approach where every path from $S_s$ to its corresponding $R_s$ must comply with the parameter values of the application code.
+
+### 5.2.2 Bidirectional applications
+
+While this Recommendation does not currently contain any bidirectional applications, it is expected that they will be added in a future revision. Figure 5-3 shows a set of reference points, for the single-fibre bidirectional linear "black link" approach, for single-channel connection ( $S_s$ and $R_s$ ) between transmitters (Tx) and receivers (Rx). Here the DWDM network elements include an OM/OD (which is used as a pair with the opposing element), one or more optical amplifiers and may also include one or more OADMs.
+
+
+
+Figure 5-3: Linear 'black link' approach for bidirectional applications. The diagram shows a linear DWDM link with two OM/OD units at the ends and an OADM in the middle. On the left, transmitters Tx λ1 and Tx λ2 are connected to the link via reference points Ss, and receivers Rx λN-1 and Rx λN are connected via reference points Rs. On the right, receivers Rx λ1 and Rx λ2 are connected via reference points Rs, and transmitters Tx λN-1 and Tx λN are connected via reference points Ss. Below the main link, a dashed box shows a single channel path from a transmitter Tx λy to a receiver Rx λx via reference points Ss and Rs. The diagram is labeled G.698.2(09)\_F5-3.
+
+Figure 5-3 – Linear "black link" approach for bidirectional applications
+
+Figure 5-4 shows a corresponding set of reference points for the single-fibre bidirectional ring "black link" approach, for single-channel connection ( $S_s$ and $R_s$ ) between transmitters (Tx) and receivers (Rx). Here the DWDM network elements include one or more amplifiers and two or more OADMs connected in a ring.
+
+
+
+Figure 5-4: Ring 'black link' approach for bidirectional applications. The diagram shows a central 'DWDM network elements' block connected to four 'OADM' (Optical Add-Drop Multiplexer) units. These OADM units are part of a 'DWDM link' ring. Each OADM is connected to external 'Tx' (Transmitter) and 'Rx' (Receiver) units via reference points labeled Ss and Rs. The entire system is enclosed in a large grey box. A small label 'G.698.2(09)\_F5-4' is in the bottom right corner.
+
+**Figure 5-4 – Ring "black link" approach for bidirectional applications**
+
+The reference points in Figures 5-3 and 5-4 are as defined in clause 5.2.1.
+
+## 5.3 Nomenclature
+
+The application code notation is constructed as follows:
+
+DScW-ytz(v)
+
+where,
+
+**D** is the indicator of DWDM applications.
+
+**S** indicates options of maximum spectral excursion such as:
+
+- **N** indicating narrow spectral excursion.
+- **W** indicating wide spectral excursion.
+
+**c** is the channel spacing in GHz.
+
+**W** indicates the black link dispersion compensation regime as follows:
+
+- **C** indicating that the chromatic dispersion values are appropriate to a black link that is dispersion compensated.
+- **U** indicating that the chromatic dispersion values are appropriate to a black link that is dispersion uncompensated.
+
+NOTE 1 – This letter is used to indicate the dispersion tolerance of the transmitters and receivers and not to constrain the construction of the black link. While application codes that include "C" have transmitters and receivers that have dispersion tolerance appropriate to DWDM links including dispersion compensation, they may be used with black links that do not contain dispersion compensators provided that the application code parameters are met. Likewise, while application codes that include "U" have transmitters and receivers that have dispersion tolerance appropriate to DWDM links without dispersion compensation, they may be used with black links that contain dispersion compensators provided that the application code parameters are met.
+
+y indicates the highest class of optical tributary signal supported:
+
+- 1 indicating NRZ 2.5G.
+- 2 indicating NRZ 10G.
+- 8 indicating DP-DQPSK 100G.
+
+t is a letter indicating the configuration supported by the application code. In the current version of this Recommendation, the only value used is:
+
+- A indicating that the black link may contain optical amplifiers.
+
+z indicates the fibre types, as follows:
+
+- 2 indicating ITU-T G.652 fibre.
+- 3 indicating ITU-T G.653 fibre.
+- 5 indicating ITU-T G.655 fibre.
+
+v indicates the operating wavelength range in terms of spectral bands (see [b-ITU-T G-Sup.39]):
+
+| V | Descriptor | Nominal wavelength range (nm) |
+|---|------------------|-------------------------------|
+| S | Short wavelength | 1460 to 1530 |
+| C | Conventional | 1530 to 1565 |
+| L | Long wavelength | 1565 to 1625 |
+
+If more than one spectral band is used, then v becomes the band letters separated by "+", e.g., for an application requiring the use of both of the C and L bands, v would be "C+L".
+
+NOTE 2 – The nominal wavelength ranges given here are for classification and not specification. The actual minimum and maximum wavelength for each application should be calculated from the maximum and minimum channel frequencies for that application.
+
+A bidirectional system is indicated by the addition of the letter **B** at the front of the application code. For DWDM application codes, this will be:
+
+B-DScW-ytz(v)
+
+For some application codes, a suffix is added to the end of the code. The only suffix currently defined is:
+
+- F to indicate that this application requires FEC bytes as specified in [ITU-T G.709] or for DP-DQPSK 100G in [ITU-T G.709.2] or [ITU-T G.709.3] to be transmitted.
+
+## 5.4 Single-channel interfaces at the reference points Ss and Rs
+
+The single-channel interfaces described in this Recommendation are intended to enable transverse compatibility at the single-channel interfaces at either end of the DWDM black link as shown in Figures 5-1 to 5-4.
+
+Further requirements related to transverse compatibility can be found in clause 6.
+
+Table 5-1 summarizes the single-channel application codes, which are structured according to the nomenclature in clause 5.3.
+
+**Table 5-1 – Classification of applications**
+
+| | Dispersion compensated | Dispersion uncompensated |
+|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Optical tributary signal class NRZ 2.5G | DN100C-1A2(C) DW100C-1A2(C) DN100C-1A3(L) DW100C-1A3(L) DN100C-1A5(C) DW100C-1A5(C) | DN100U-1A2(C) DN100U-1A3(L) DN100U-1A5(C) |
+| OTU1 with FEC enabled | DW100C-1A2(C)F DW100C-1A3(L)F DW100C-1A5(C)F | |
+| Optical tributary signal class NRZ 10G | DN100C-2A2(C) DW100C-2A2(C) DN100C-2A3(L) DW100C-2A3(L) DN100C-2A5(C) DW100C-2A5(C) DN50C-2A2(C) DN50C-2A3(L) DN50C-2A5(C) | |
+| OTU2 with FEC enabled | DN100C-2A2(C)F DW100C-2A2(C)F DN100C-2A3(L)F DW100C-2A3(L)F DN100C-2A5(C)F DW100C-2A5(C)F DN50C-2A2(C)F DN50C-2A3(L)F DN50C-2A5(C)F | DN100U-2A2(C)F DN100U-2A3(L)F DN100U-2A5(C)F DN50U-2A2(C)F DN50U-2A3(L)F DN50U-2A5(C)F |
+| OTL4.4-SC or FOIC1.4-SC | | DN50U-8A2(C)F DN50U-8A3(L)F DN50U-8A5(C)F DN100U-8A2(C)F DN100U-8A3(L)F DN100U-8A5(C)F DW50U-8A2(C)F DW50U-8A3(L)F DW50U-8A5(C)F DW100U-8A2(C)F DW100U-8A3(L)F DW100U-8A5(C)F |
+
+The amplified multichannel systems with single-channel interfaces in this Recommendation are specified in Tables 8-1 to 8-8.
+
+# 6 Transverse compatibility
+
+This Recommendation specifies parameters in order to enable transverse (i.e., multivendor) compatibility at single-channel reference points Ss and Rs of the "black link" approach DWDM NEs.
+
+The single-channel reference points Ss and Rs are intended to make multiple tributary interfaces of DWDM NEs transversely compatible. In this case, multiple tributary signal transmitters (Tx λi ) and receivers (Rx λi ) may be from different vendors.
+
+Transverse (multivendor) compatibility is enabled for all single-channel reference points Ss and Rs of "black link" approach DWDM NEs having exactly the same application code.
+
+Coexistence of tributary interfaces with different application codes over the same black link is a matter of joint engineering. Care must be taken, particularly with respect to critical parameters that must be consistent, e.g., Ss output power and Rs input power, Ss bit rate/line coding and Rs bit rate/line coding, etc.
+
+For the element of the application code referring to the maximum spectral excursion (indicator S in the application code; see clause 5.3), a mismatch between the indicator of the transmitter and that of the link will cause incompatibility when the transmitter has a code containing W (wide spectral excursion) and the link contains N (narrow spectral excursion). All other combinations are transversely compatible.
+
+# 7 Parameter definitions
+
+The parameters in Table 7-1 are defined at the interface points, and the definitions are provided in the clauses below.
+
+**Table 7-1 – Parameters for DWDM applications using the "black link" approach with amplifiers**
+
+| Parameter | Units | For Tables 8-1 to 8-6, defined in | For Tables 8-7 and 8-8, defined in |
+|--------------------------------------------------------|-------|-----------------------------------|------------------------------------|
+| General information | | | |
+| Minimum channel spacing | GHz | 7.1.1 | 7.1.1 |
+| Bit rate/line coding of optical tributary signals | – | 7.1.2 | 7.1.2 |
+| Maximum bit error ratio | – | 7.1.3 | 7.1.3 |
+| Fibre type | – | 7.1.4 | 7.1.4 |
+| Interface at point Ss | | | |
+| Maximum mean channel output power | dBm | 7.2.1 | 7.2.1 |
+| Minimum mean channel output power | dBm | 7.2.1 | 7.2.1 |
+| Minimum central frequency | THz | 7.2.2 | 7.2.2 |
+| Maximum central frequency | THz | 7.2.2 | 7.2.2 |
+| Maximum spectral excursion | GHz | 7.2.3 | 7.2.3 |
+| Minimum side mode suppression ratio | dB | 7.2.4 | 7.2.4 |
+| Minimum channel extinction ratio | dB | 7.2.5 | NA |
+| Eye mask | – | 7.2.6 | NA |
+| Maximum transmitter (residual) dispersion OSNR penalty | dB | 7.2.7 | NA |
+| Maximum laser linewidth | kHz | NA | 7.2.8 |
+
+**Table 7-1 – Parameters for DWDM applications using the "black link" approach with amplifiers**
+
+| Parameter | Units | For Tables 8-1 to 8-6, defined in | For Tables 8-7 and 8-8, defined in |
+|------------------------------------------------------------------------|-------------|-----------------------------------|------------------------------------|
+| Maximum offset between the carrier and the nominal central frequency | GHz | NA | 7.2.9 |
+| Maximum power difference between polarizations | dB | NA | 7.2.10 |
+| Maximum skew between the two polarizations | ps | NA | 7.2.11 |
+| Maximum error vector magnitude | % | NA | 7.2.12 |
+| Maximum I-Q offset | dB | NA | 7.2.13 |
+| Optical path from point Ss to Rs | | | |
+| Maximum ripple | dB | 7.3.1 | 7.3.1 |
+| Maximum (residual) chromatic dispersion | ps/nm | 7.3.2 | 7.3.2 |
+| Minimum (residual) chromatic dispersion | ps/nm | 7.3.2 | 7.3.2 |
+| Minimum optical return loss at S s | dB | 7.3.3 | 7.3.3 |
+| Maximum discrete reflectance between S s and R s | dB | 7.3.4 | 7.3.4 |
+| Maximum differential group delay | ps | 7.3.5 | 7.3.5 |
+| Maximum polarization dependent loss | dB | 7.3.6 | 7.3.6 |
+| Maximum polarization rotation speed | krad/s | NA | 7.3.7 |
+| Maximum inter-channel crosstalk at R s | dB | 7.3.8 | 7.3.8 |
+| Maximum interferometric crosstalk at R s | dB | 7.3.9 | 7.3.9 |
+| Maximum optical path OSNR penalty | dB | 7.3.10 | 7.3.10 |
+| Interface at point Rs | | | |
+| Maximum mean input power | dBm | 7.4.1 | 7.4.1 |
+| Minimum mean input power | dBm | 7.4.1 | 7.4.1 |
+| Minimum OSNR | dB (0.1 nm) | 7.4.2 | NA |
+| Minimum OSNR(193.6) | dB (0.1 nm) | NA | 7.4.2 |
+| Receiver OSNR tolerance | dB (0.1 nm) | 7.4.3 | NA |
+| Receiver OSNR tolerance(193.6) | dB (0.1 nm) | NA | 7.4.3 |
+| Maximum reflectance of receiver | dB | 7.4.4 | 7.4.4 |
+
+## 7.1 General information
+
+### 7.1.1 Minimum channel spacing
+
+This is the minimum nominal difference in frequency between two adjacent channels. All possible tolerances of actual frequencies are considered in clause 7.2.3.
+
+### 7.1.2 Bit rate/line coding of optical tributary signals
+
+Optical tributary signal class NRZ 2.5G applies to continuous digital signals with non-return to zero line coding, from nominally 622 Mbit/s to nominally 2.67 Gbit/s. Optical tributary signal class NRZ 10G applies to continuous digital signals with non-return to zero line coding, from nominally 2.4 Gbit/s to nominally 10.71 Gbit/s.
+
+Optical tributary signal class DP-DQPSK 100G applies to continuous digital signals with non-return to zero differential quadrature phase shift keying modulation applied separately to two orthogonal polarizations of a carrier, operating at a total bit rate from nominally 103.1 Gbit/s to nominally 112.74 Gbit/s.
+
+Optical tributary signal class DP-DQPSK 100G uses two orthogonal polarizations, each carrying a DQPSK signal.
+
+Each DQPSK signal is generated from two of the four client lanes by taking one bit from each lane and then encoding them as a change in phase angle between successive symbols. Hence the phase change between two successive symbols encodes two bits of data according to the mapping shown in Table 7-2.
+
+**Table 7-2 – Bit mapping for the phase change of one polarization of the DP-DQPSK 100G signal**
+
+| Lane bit values | Phase change between successive symbols |
+|-----------------|-----------------------------------------|
+| AB | (Radians) |
+| 00 | 0 |
+| 10 | $\pi/2, -3\pi/2$ |
+| 11 | $\pi, -\pi$ |
+| 01 | $3\pi/2, -\pi/2$ |
+
+Bit A comes from any of the four lanes and bit B comes from any other lane. The lanes providing bits A and B cannot change while the link is in service. The other two lanes are used to generate the DQPSK signal on the other polarization in a similar manner.
+
+For an application that does not have a suffix of F, the parameter values are the same for any bit rate within the range of the applicable optical tributary signal class. When an optical system uses one of these codes, therefore, it is necessary to specify both the application code and also the exact bit rate of the system. In other words, there is no requirement for equipment compliant with one of these codes to operate over the complete range of bit rates specified for its optical tributary signal class.
+
+### 7.1.3 Maximum bit error ratio
+
+The parameters are specified relative to an optical section design objective of a bit error ratio (BER) not worse than the value specified by the application code. This value applies to each optical channel under the extreme case of optical path attenuation and dispersion conditions in each application. In the case of application codes requiring FEC bytes to be transmitted (i.e., having a code with a suffix of F), the BER is required to be met only after the correction (if used) has been applied. For all other application codes, the BER is required to be met without the use of FEC.
+
+### 7.1.4 Fibre type
+
+Single mode optical fibre types are chosen from those defined in [ITU-T G.652], [ITU-T G.653] and [ITU-T G.655].
+
+## 7.2 Interface at point Ss
+
+### 7.2.1 Maximum and minimum mean channel output power
+
+The mean launched power of each optical channel at reference point Ss is the average power of a pseudo-random data sequence coupled into the DWDM link. It is given as a range (maximum and minimum) to allow for some cost optimization and to cover allowances for operation under the standard operating conditions, connector degradations, measurement tolerances and ageing effects.
+
+Note that it is not required for any implementation to provide a mean channel output power that is as high as the maximum mean channel output power or as low as the minimum mean channel output power. Furthermore, the actual mean channel output power of a particular interface device must not exceed the limits defined for the maximum and minimum mean channel output power but can be somewhere between those limits.
+
+### 7.2.2 Minimum and maximum central frequency
+
+The central frequency is the nominal single-channel frequency on which the digital coded information of the particular optical channel is modulated by the line code.
+
+The central frequencies of all channels within an application lie on the frequency grid for the minimum channel spacing of the application given in [ITU-T G.694.1].
+
+While the specific central frequencies used within each application are not specified in this Recommendation, the nominal central frequencies of all channels within an application should be greater than or equal to the minimum central frequency and less than or equal to the maximum central frequency.
+
+Note that the value of "c" (speed of light in a vacuum) that should be used for converting between frequency and wavelength is $2.99792458 \times 10^8$ m/s.
+
+### 7.2.3 Maximum spectral excursion
+
+This is the maximum acceptable difference between the nominal central frequency of the channel and the –15 dB points of the transmitter spectrum furthest from the nominal central frequency measured at point Ss for NRZ type signals or the –2.5 dB points of the transmitter spectrum furthest from the nominal central frequency measured at point Ss for DP-DQPSK type signals. This is illustrated in Figure 7-1 for NRZ-type signals and in Figure 7-2 for DP-DQPSK type signals.
+
+NOTE – The measurement of the –15 dB points of the transmitter spectrum for the NRZ-type signals and -2.5 dB points for the DP-DQPSK type signals should be performed with a nominal resolution bandwidth of 0.01 nm.
+
+
+
+The figure is a line graph showing the power spectral density of an NRZ-type signal. The y-axis is labeled 'Power relative to peak (dB)' and ranges from 0 to -30 in increments of 5. The x-axis is labeled 'Offset from nominal central frequency (GHz)' and has a central mark at 0. A dashed vertical line at 0 GHz indicates the 'Nominal central frequency'. Two solid vertical lines, one to the left and one to the right of the center, indicate the 'Nominal central frequency minus maximum spectral excursion' and 'Nominal central frequency plus maximum spectral excursion' respectively. The spectral curve starts at 0 dB at the nominal frequency and drops off, reaching -15 dB at the excursion limits. The regions beyond these limits are shaded gray, indicating the maximum spectral excursion.
+
+Figure 7-1: Illustration of maximum spectral excursion for NRZ-type signals. The graph shows Power relative to peak (dB) on the y-axis (0 to -30) versus Offset from nominal central frequency (GHz) on the x-axis. A dashed vertical line at 0 GHz marks the Nominal central frequency. Two solid vertical lines mark the Nominal central frequency minus maximum spectral excursion (left) and Nominal central frequency plus maximum spectral excursion (right). The spectral power curve shows a peak at the nominal frequency and drops to -15 dB at the excursion limits. The areas outside the excursion limits are shaded gray.
+
+Figure 7-1 – Illustration of maximum spectral excursion for NRZ-type signals
+
+
+
+Figure 7-2: Illustration of maximum spectral excursion for DP-DQPSK type signals. The graph shows Power relative to peak (dB) on the y-axis (from -20 to 0) versus Offset from nominal central frequency (GHz) on the x-axis. Two overlapping spectral curves are shown, centered at 0 GHz. The left curve is labeled 'Nominal central frequency minus maximum spectral excursion' and the right curve is labeled 'Nominal central frequency plus maximum spectral excursion'. The area between the two curves is shaded with diagonal lines. The text 'G.698.2(18)\_F7-2' is in the bottom right corner.
+
+**Figure 7-2 – Illustration of maximum spectral excursion for DP-DQPSK type signals**
+
+This parameter also defines the range of frequencies over which the ripple specifications must be met.
+
+### 7.2.4 Minimum side mode suppression ratio
+
+The minimum side mode suppression ratio is the minimum value of the ratio of the largest peak of the total transmitter spectrum to the second largest peak. The spectral resolution of the measurement shall be better than the maximum spectral width of the peak, as defined in [ITU-T G.691]. The second largest peak may be next to the main peak, or far removed from it.
+
+NOTE – Within this definition, spectral peaks that are separated from the largest peak by the clock frequency are not considered to be side modes.
+
+### 7.2.5 Minimum channel extinction ratio
+
+The extinction ratio ( $EX$ ) is defined as:
+
+$$EX = 10 \log_{10}(A/B)$$
+
+In the above definition of $EX$ , $A$ is the average optical power level at the centre of a logical "1" and $B$ is the average optical power level at the centre of a logical "0". The convention adopted for optical logic levels is:
+
+- emission of light for a logical "1";
+- no emission for a logical "0".
+
+The minimum channel extinction ratio is not required to be met in the presence of a fourth-order Bessel-Thomson filter.
+
+### 7.2.6 Eye mask
+
+The definition and limits for this parameter are found in [ITU-T G.959.1].
+
+#### 7.2.7 Maximum transmitter (residual) dispersion OSNR penalty
+
+The transmitter (residual) dispersion OSNR penalty is defined as:
+
+Lowest OSNR at $S_s$ with worst case (residual) dispersion – Lowest OSNR at $S_s$ with no dispersion
+
+Where:
+
+- Lowest OSNR at $S_S$ with no dispersion is the lowest OSNR that meets the maximum BER of the application from a reference receiver as defined in clause B.3 of [ITU-T G.959.1] at point $S_S$ .
+- Lowest OSNR at $S_S$ with worst case (residual) dispersion is the lowest OSNR that meets the maximum BER of the application from a reference receiver as defined in clause B.3 of [ITU-T G.959.1] at point $S_S$ with the chromatic dispersion (within the range specified for the application code) applied which gives the highest OSNR penalty.
+
+NOTE – The measurement of the transmitter (residual) dispersion OSNR penalty therefore requires filtered ASE noise to be added to the signal at point $S_S$ . This subject is further discussed in Appendix I.
+
+This penalty is not part of the system budget directly (since it is included as part of the optical path OSNR penalty defined in clause 7.3.9) but rather provides an upper bound on the OSNR penalty due to dispersion alone, thereby ensuring that some of the optical path OSNR penalty is available to cover the other impairments listed.
+
+### 7.2.8 Maximum laser linewidth
+
+The laser linewidth is defined as: The level of the white noise component of the power spectrum density of the instantaneous laser frequency multiplied by $\pi$ .
+
+### 7.2.9 Maximum offset between the carrier and the nominal central frequency
+
+The offset between the carrier and the nominal central frequency is defined as:
+
+Difference between the centroid of the power spectrum of the optical signal and the nominal central frequency of the channel.
+
+### 7.2.10 Maximum power difference between polarizations
+
+The power difference between polarizations is defined as:
+
+Difference $\Delta P_{\text{pol}}$ of the optical power levels $P_X$ and $P_Y$ at the reference point $S_S$ , i.e.:
+
+$$\Delta P_{\text{pol}} = \text{abs} (10 \cdot \log_{10} (P_X / P_Y)),$$
+
+where by $P_X$ and $P_Y$ are the powers of the two nominally orthogonal polarizations carrying the two data streams.
+
+### 7.2.11 Maximum skew between the two polarizations
+
+The skew between the two polarizations is defined as:
+
+The time delay between the symbol sequences on each polarization at reference point $S_S$ when the same sequence is applied to both polarizations.
+
+### 7.2.12 Maximum error vector magnitude
+
+The error vector magnitude is defined as follows:
+
+N pairs of in-phase (I) and quadrature (Q) samples are acquired for each of the two polarizations after filtering with a 4th order Bessel-Thomson low-pass filter with a $-3$ dB bandwidth of 0.7 times the symbol rate. The following calculations are done for each of the polarizations separately.
+
+Split the sample pairs into blocks of size B (where B equals 1000 for DP-DQPSK 100G) and for each block:
+
+The carrier frequency offset $f_{\text{offs}}$ is estimated for each individual block of pairs of raw in-phase (I) and quadrature (Q) samples by first calculating the phase error of each sample pair:
+
+$$\varphi_{\text{raw}}(b) = \frac{\pi}{4} - \text{mod} \left( \text{atan2}(Q_{\text{raw}}(b), I_{\text{raw}}(b)), \frac{\pi}{2} \right)$$
+
+where:
+
+$$\text{mod}(a, m) = a - m \cdot \text{floor}\left(\frac{a}{m}\right)$$
+
+and $\text{floor}(x)$ rounds $x$ to the nearest integer less than or equal to that element and:
+
+$$\text{atan2}(y, x) = \begin{cases} \arctan(y/x) & :x>0 \\ \arctan(y/x)+\pi & :y\geq 0, x<0 \\ \arctan(y/x) - \pi & :y<0, x<0 \\ +\pi/2 & :y>0, x=0 \\ -\pi/2 & :y<0, x=0 \\ \text{undefined} & :y=0, x=0 \end{cases}$$
+
+Calculate the phase offset for each sample:
+
+$$\varphi_{\text{offset}}(b) = \varphi_{\text{raw}}(b) - \sum_{k=0}^{B-1} \pi/2 \text{ round}\left(\frac{\varphi_{\text{raw}}(k+1) - \varphi_{\text{raw}}(k)}{\pi/2}\right)$$
+
+Finally calculate the frequency offset by calculating the slope of the phase offset:
+
+$$f_{\text{offs}} = -\frac{B \sum_{k=0}^{B-1} k \varphi_{\text{offset}}(k) - (\sum_{k=0}^{B-1} k) \times (\sum_{k=0}^{B-1} \varphi_{\text{offset}}(k))}{2\pi T [B \sum_{k=0}^{B-1} k^2 - (\sum_{k=0}^{B-1} k)^2]}$$
+
+The samples in this block are then rotated using a linear increasing phase:
+
+$$\begin{aligned} I(b) &= I_{\text{raw}}(b) \cdot \cos\left(b \cdot 2\pi \cdot \frac{f_{\text{offs}}}{f_{\text{symbol}}}\right) - Q_{\text{raw}}(b) \cdot \sin\left(b \cdot 2\pi \cdot \frac{f_{\text{offs}}}{f_{\text{symbol}}}\right) \\ Q(b) &= I_{\text{raw}}(b) \cdot \sin\left(b \cdot 2\pi \cdot \frac{f_{\text{offs}}}{f_{\text{symbol}}}\right) + Q_{\text{raw}}(b) \cdot \cos\left(b \cdot 2\pi \cdot \frac{f_{\text{offs}}}{f_{\text{symbol}}}\right) \end{aligned}$$
+
+where $f_{\text{symbol}}$ is the symbol rate of the samples and $b$ is the symbol number within the block starting at 0.
+
+For $B$ pairs of in-phase (I) and quadrature (Q) samples, calculate the DC offsets for the I and Q samples:
+
+$$\begin{aligned} I_{\text{mean}} &= \sum_{b=0}^{B-1} I(b)/B \\ Q_{\text{mean}} &= \sum_{b=0}^{B-1} Q(b)/B \end{aligned}$$
+
+The values for $I_{\text{mean}}$ and $Q_{\text{mean}}$ are then corrected for any imbalance in the symbol occurrence within each block.
+
+Subtract the DC offsets from the $B$ sample pairs to obtain the DC-free sample pairs:
+
+$$\begin{aligned} I_{\text{AC}}(b) &= I(b) - I_{\text{mean}} \\ Q_{\text{AC}}(b) &= Q(b) - Q_{\text{mean}} \end{aligned}$$
+
+Find the signal power of the I and Q samples:
+
+$$P_{Signal} = \sum_{b=0}^{B-1} (I_{AC}^2(b) + Q_{AC}^2(b)) / B$$
+
+Divide the DC-free sample pairs by the square root of half the signal power to obtain the normalized sample pairs:
+
+$$I_{norm}(b) = I_{AC}(b) / \sqrt{P_{signal}/2}$$
+
+$$Q_{norm}(b) = Q_{AC}(b) / \sqrt{P_{signal}/2}$$
+
+Calculate the phase error:
+
+$$\varphi_{err} = \frac{\pi}{4} - \frac{1}{B} \sum_{b=0}^{B-1} \text{mod} \left( \text{atan2}(Q_{norm}(b), I_{norm}(b)), \frac{\pi}{2} \right)$$
+
+rotate the data:
+
+$$I_{\varphi}(b) = \cos(\varphi_{err}) I_{norm}(b) - \sin(\varphi_{err}) Q_{norm}(b)$$
+
+$$Q_{\varphi}(b) = \sin(\varphi_{err}) I_{norm}(b) + \cos(\varphi_{err}) Q_{norm}(b)$$
+
+Create an integer value between 0 and 3 to define which of the four constellation points each sample belongs to:
+
+$$D(b) = \text{mod} \left( \text{round} \left( \frac{\text{atan2}(Q_{\varphi}(b), I_{\varphi}(b))}{\pi/2} - \frac{1}{2} \right), 4 \right)$$
+
+Calculate the average values $I_k$ and $Q_k$ for each of the four constellation points:
+
+$$\hat{I}_k = \sum_{b=0}^{B-1} (I_{\varphi}(b) \cdot \delta(D(b) - k)) / \sum_{b=0}^{B-1} \delta(D(b) - k), \quad k = [0, 1, 2, 3]$$
+
+$$\hat{Q}_k = \sum_{b=0}^{B-1} (Q_{\varphi}(b) \cdot \delta(D(b) - k)) / \sum_{b=0}^{B-1} \delta(D(b) - k), \quad k = [0, 1, 2, 3]$$
+
+where:
+
+$$\delta(x) = \begin{cases} 1 & : x = 0 \\ 0 & : x \neq 0 \end{cases}$$
+
+Calculate the remaining phase error:
+
+$$\delta_{err} = \frac{1}{2} \text{arccos} \left( \frac{\hat{Q}_3 + \hat{Q}_0 - \hat{Q}_1 - \hat{Q}_2}{\sqrt{(\hat{I}_3 + \hat{I}_0 - \hat{I}_1 - \hat{I}_2)^2 + (\hat{Q}_3 + \hat{Q}_0 - \hat{Q}_1 - \hat{Q}_2)^2}} \right) - \frac{1}{2} \text{arccos} \left( \frac{\hat{I}_0 + \hat{I}_1 - \hat{I}_2 - \hat{I}_3}{\sqrt{(\hat{I}_0 + \hat{I}_1 - \hat{I}_2 - \hat{I}_3)^2 + (\hat{Q}_0 + \hat{Q}_1 - \hat{Q}_2 - \hat{Q}_3)^2}} \right)$$
+
+White Gaussian noise is added to the resulting $I_{\varphi}(b)$ and $Q_{\varphi}(b)$ of the previous step. The amplitude of the noise for each quadrature is calculated from the following equation:
+
+$$A_{RMS} = \sqrt{\frac{1.466 \cdot f_{symbol}}{10^{\frac{OSNR(193.6)}{10}} \cdot 12.5}}$$
+
+Where $f_{symbol}$ is the symbol rate in GHz and OSNR(193.6) is the Minimum OSNR at reference point $R_s$ referenced to 193.6 THz, specified in the applicable parameter value tables.
+
+NOTE – The value of 193.6 THz was chosen so that the optical measurement bandwidth of 0.1 nm corresponds to 12.5 GHz, which is a value commonly used in the industry.
+
+The data is then equalized using a real valued 7-tap T-spaced finite impulse response (FIR) filter. The sum of all filter tap coefficients is equal to one, and the largest coefficient can be for any of the 7 taps. The individual filter taps are found by minimizing the $EVM_{RMS}$ value, which is calculated as described below.
+
+Remove the remaining phase error:
+
+$$I_\delta(b) = \cos(\delta_{err}) I_\phi(b) - \sin(\delta_{err}) Q_\phi(b)$$
+
+$$Q_\delta(b) = \sin(\delta_{err}) I_\phi(b) + \cos(\delta_{err}) Q_\phi(b)$$
+
+Calculate the error vector magnitude for each sample pair in each of the polarizations:
+
+$$EVM(b) = \sqrt{[(|I_\delta(b)| - 1)^2 + (|Q_\delta(b)| - 1)^2]}/2$$
+
+Using all the N samples from the x polarization calculate $EVM_{RMS,x}$ as:
+
+$$EVM_{RMS,x} = \sqrt{\frac{1}{N} \sum_{n=0}^{N-1} EVM(n)^2}$$
+
+Using all the N samples from the y polarization and calculate $EVM_{RMS,y}$ as:
+
+$$EVM_{RMS,y} = \sqrt{\frac{1}{N} \sum_{n=0}^{N-1} EVM(n)^2}$$
+
+Then calculate $EVM_{RMS}$ from:
+
+$$EVM_{RMS} = \sqrt{0.5(EVM_{RMS,x}^2 + EVM_{RMS,y}^2)} \times 100\%$$
+
+### 7.2.13 Maximum I-Q offset
+
+The I-Q offset of a modulated signal relates to the average signal amplitudes in the I- and Q-phases of that signal. The relative excess (unmodulated) power, $P_{excess}$ , is a measure of this impairment and is obtained from the parameters $I_{mean}$ and $Q_{mean}$ and $P_{Signal}$ , which are intermediate results during the calculation of the error vector magnitude (see clause 7.2.12):
+
+$$P_{excess} = \frac{I_{mean}^2 + Q_{mean}^2}{P_{Signal}}$$
+
+$$IQ_{offset} = 10 \log_{10}(P_{excess})$$
+
+## 7.3 Optical path parameters from Ss to Rs
+
+### 7.3.1 Maximum ripple
+
+The ripple (of a DWDM device) is defined in [ITU-T G.671]. In this Recommendation, it is applied to the entire black link from reference point Ss to the corresponding Rs. For any optical channel, it is the peak-to-peak difference in insertion loss between the input and output ports of the black link for that channel in the frequency range of the central frequency of the channel $\pm$ the maximum spectral excursion. This is illustrated in Figure 7-3.
+
+
+
+Figure 7-3: Illustration of maximum ripple. The graph shows the insertion loss (-10 Log(Loss) in dB) versus the offset from the nominal central frequency (in GHz). A curve represents the loss, which is relatively flat between two vertical dashed lines representing the 'Nominal central frequency minus maximum spectral excursion' and 'Nominal central frequency plus maximum spectral excursion'. The 'Maximum ripple' is indicated by a vertical double-headed arrow between the peak and trough of the curve within this range. The x-axis is labeled 'Offset from nominal central frequency (GHz)' and has a '0' at the center. The y-axis is labeled '-10 Log(Loss) (dB)'. The figure is labeled 'G.698.2(18)\_F7-3' in the bottom right corner.
+
+Figure 7-3 – Illustration of maximum ripple
+
+### 7.3.2 Maximum and minimum (residual) chromatic dispersion
+
+These parameters define the maximum and minimum value of the optical path end-to-end chromatic dispersion that the system shall be able to tolerate. These are the worst-case dispersion values of the optical path from point Ss to the corresponding receive reference point Rs. In the case that the black link contains dispersion compensation between these two points, its effect is included.
+
+These parameters contain the word "residual" in brackets because, in the case of links which include dispersion compensators, these are the maximum and minimum residual chromatic dispersion, and in the case of links that do not include any dispersion compensators, these parameters are simply the maximum and minimum chromatic dispersion.
+
+### 7.3.3 Minimum optical return loss at Ss
+
+Reflections are caused by refractive index discontinuities along the optical path. If not controlled, they can degrade system performance through their disturbing effect on the operation of the optical source, or through multiple reflections which lead to interferometric noise at the receiver. Reflections from the optical path are controlled by specifying the:
+
+- minimum optical return loss of the cable plant at the source reference point (Ss), including any connectors; and
+- maximum discrete reflectance between source reference point (Ss) and receive reference point (Rs).
+
+Reflectance denotes the reflection from any single discrete reflection point, whereas the optical return loss is the ratio of the incident optical power to the total returned optical power from the entire fibre including both discrete reflections and distributed backscattering such as Rayleigh scattering.
+
+Measurement methods for reflections are described in Appendix I of [ITU-T G.957]. For the purpose of reflectance and return loss measurements, points Ss and Rs are assumed to coincide with the endface of each connector plug. It is recognized that this does not include the actual reflection performance of the respective connectors in the operational system. These reflections are assumed to have the nominal value of reflection for the specific type of connectors used.
+
+### 7.3.4 Maximum discrete reflectance between Ss and Rs
+
+Optical reflectance is defined to be the ratio of the reflected optical power present at a point, to the optical power incident to that point. Control of reflections is discussed extensively in [ITU-T G.957]. The maximum number of connectors or other discrete reflection points which may be included in the optical path (e.g., for distribution frames, or WDM components), must be such as to allow the specified overall optical return loss to be achieved. If this cannot be done using connectors meeting the maximum discrete reflections cited in the tables of clause 8, then connectors having better reflection performance must be employed. Alternatively, the number of connectors must be reduced. It also may be necessary to limit the number of connectors or to use connectors having improved reflectance performance in order to avoid unacceptable impairments due to multiple reflections.
+
+In the tables of clause 8, the value of maximum discrete reflectance between source reference points and receive reference points is intended to minimize the effects of multiple reflections (e.g., interferometric noise). The value for maximum receiver reflectance is chosen to ensure acceptable penalties due to multiple reflections for all likely system configurations involving multiple connectors, etc. Systems employing fewer or higher performance connectors produce fewer multiple reflections and consequently are able to tolerate receivers exhibiting higher reflectance.
+
+### 7.3.5 Maximum differential group delay
+
+Differential group delay (DGD) is the time difference between the fractions of a pulse that are transmitted in the two principal states of polarization of an optical signal. For distances greater than several kilometres, and assuming random (strong) polarization mode coupling, DGD in a fibre can be statistically modelled as having a Maxwellian distribution.
+
+In this Recommendation, for NRZ application codes, the maximum differential group delay is defined to be the value of DGD that the system must tolerate with a maximum OSNR penalty of 2 dB.
+
+Due to the statistical nature of polarization mode dispersion (PMD), the relationship between maximum DGD and mean DGD can only be defined probabilistically. The probability of the instantaneous DGD exceeding any given value can be inferred from its Maxwellian statistics. Therefore, if we know the maximum DGD that the system can tolerate, we can derive the equivalent mean DGD by dividing by the ratio of maximum to mean that corresponds to an acceptable probability. Some example ratios are given in Table 7-3.
+
+**Table 7-3 – DGD means and probabilities**
+
+| Ratio of maximum to mean | Probability of exceeding maximum |
+|--------------------------|----------------------------------|
+| 3.0 | $4.2 \times 10^{-5}$ |
+| 3.5 | $7.7 \times 10^{-7}$ |
+| 4.0 | $7.4 \times 10^{-9}$ |
+
+### 7.3.6 Maximum polarization dependent loss
+
+The polarization dependent loss (PDL) is the difference (in dB) between the maximum and minimum values of the channel insertion loss (or gain) of the black link from point Ss to Rs due to a variation of the state of polarization (SOP) over all SOPs.
+
+### 7.3.7 Maximum polarization rotation speed
+
+The polarization rotation speed is the rate of rotation in Stokes space of the two polarizations of the optical signal at point Rs measured in krad/s.
+
+### 7.3.8 Maximum inter-channel crosstalk
+
+This parameter places a requirement on the isolation of a link conforming to the "black link" approach such that under the worst-case operating conditions the inter-channel crosstalk at any reference point Rs is less than the maximum inter-channel crosstalk value.
+
+Inter-channel crosstalk is defined as the ratio of total power in all of the disturbing channels to that in the wanted channel, where the wanted and disturbing channels are at different wavelengths.
+
+Specifically, the isolation of the link shall be greater than the amount required to ensure that when any channel is operating at the minimum mean output power at point Ss and all of the others are at the maximum mean output power, then the inter-channel crosstalk at the corresponding point Rs is less than the maximum inter-channel crosstalk value.
+
+### 7.3.9 Maximum interferometric crosstalk
+
+This parameter places a requirement on the isolation of a link conforming to the "black link" approach such that, under the worst-case operating conditions, the interferometric crosstalk at any reference point Rs is less than the maximum interferometric crosstalk value.
+
+Interferometric crosstalk is defined as the ratio of the disturbing power to the wanted power within a single channel, where the disturbing power is the power (not including ASE) within the optical channel that would remain if the wanted signal were removed from the link while leaving all of the other link conditions the same.
+
+Specifically, the isolation of the link shall be greater than the amount required to ensure that when any channel is operating at the minimum mean output power at point Ss and all of the others are at the maximum mean output power, then the interferometric crosstalk at the corresponding point Rs is less than the maximum interferometric crosstalk value.
+
+### 7.3.10 Maximum optical path OSNR penalty
+
+The optical path OSNR penalty is defined as:
+
+$$\text{Lowest OSNR at R}_s - \text{Lowest OSNR at S}_s$$
+
+where:
+
+- Lowest OSNR at Ss is the lowest OSNR that meets the maximum BER of the application from a reference receiver as defined in clause B.3 of [ITU-T G.959.1] for NRZ signal classes and in Annex A for DP-DQPSK 100G, at point Ss i.e., *before* transmission through the black link.
+- Lowest OSNR at Rs is the lowest OSNR that meets the maximum BER of the application from a reference receiver as defined in clause B.3 of [ITU-T G.959.1] for NRZ signal classes and in Annex A for DP-DQPSK 100G, at point Rs i.e., *after* transmission through the black link.
+
+NOTE – The measurement of the optical path OSNR penalty therefore requires filtered ASE noise to be added to the signal at points Ss and Rs . This subject is further discussed in Appendix I.
+
+The effects that contribute to the optical path OSNR penalty include:
+
+- transmitter (residual) dispersion penalty for NRZ signal classes;
+- non-linear effects within the black link;
+- inter-channel crosstalk;
+- interferometric crosstalk;
+- reflections from the optical path;
+- polarization dependent loss.
+
+The average value of the random dispersion penalties due to PMD is included in the allowed path OSNR penalty. The actual DGD that may be encountered in operation is a randomly varying fibre/cable property, and cannot be specified in this Recommendation. This subject is further discussed in Appendix I of [ITU-T G.691].
+
+For NRZ signal classes, the transmitter/receiver combination is required to tolerate an actual DGD of 0.3-bit period with a maximum optical path OSNR penalty of 2 dB (with 50% of optical power in each principal state of polarization). For a well-designed receiver, this corresponds to an OSNR penalty of 0.2 – 0.4 dB for a DGD of 0.1-bit period.
+
+## 7.4 Interface at point $R_s$
+
+### 7.4.1 Maximum and minimum mean input power
+
+The maximum and minimum values of the average received power at point $R_s$ .
+
+For any optical power level at point $R_s$ that is between these two values and while all of the other parameters are within their limiting values, the receiver is required to achieve the specified maximum BER of the application code.
+
+This means that the receiver must meet the specified maximum BER for a transmitter with worst-case values of:
+
+- transmitter eye mask for NRZ signal classes or $EVM_{RMS}$ for DP-DQPSK signal classes;
+- extinction ratio for NRZ signal classes or IQ offset for DP-DQPSK signal classes;
+- optical return loss at point $S_s$ ,
+
+and a link with worst-case values of:
+
+- (residual) dispersion;
+- OSNR;
+- optical path OSNR penalty.
+
+Ageing effects are not specified separately. Worst-case, end-of-life values are specified.
+
+This parameter (together with the maximum and minimum mean channel output power) also places a requirement on the maximum and minimum channel insertion loss (or gain) of the black link.
+
+The requirement is that while the mean channel output power at point $S_s$ is within the specified limits, the channel insertion loss (or gain) of the black link for that channel must be such that the power level at point $R_s$ is within the maximum and minimum mean input power limits.
+
+Channel insertion loss is defined in [ITU-T G.671]. For any optical channel, it is the minimum (or maximum) reduction or gain in optical power between the input and output ports of the black link for that channel in the frequency range of the central frequency of the channel $\pm$ the maximum spectral excursion.
+
+Insertion loss specifications are assumed to be worst-case values including losses due to the OM/OD pair, splices, connectors, optical amplifiers and optical attenuators (if used) or other optical devices, and any additional margin to cover allowances for:
+
+- future modifications to the cable configuration (additional splices, increased cable lengths, etc.);
+- performance variations due to environmental factors;
+- degradation of any connectors, optical amplifiers, optical attenuators or other optical devices between points Ss and Rs , if used.
+
+### 7.4.2 Minimum optical signal-to-noise ratio (OSNR) and OSNR(193.6)
+
+The minimum optical signal-to-noise ratio (OSNR) is the minimum value of the ratio of the signal power in the wanted channel to the highest noise power density (referred to 0.1 nm) in the range of the central frequency plus and minus the maximum spectral excursion. For the purposes of this definition, the noise is defined to be that which would be present if the signal in the wanted channel were removed from the black link while keeping all other black link conditions the same (e.g., the gain and noise figure of all amplifiers).
+
+This parameter places a requirement on the characteristics of the black link that the OSNR at any reference point Rs must be greater than the minimum OSNR.
+
+For 100 Gbit/s applications, specified in Tables 8-7 and 8-8, the minimum optical signal-to-noise ratio OSNR(*f*) is specified as a function of channel frequency *f* and referred to its value at 193.6 THz, OSNR(193.6), according to the following relationship:
+
+$$OSNR(f) = OSNR(193.6) - 20 \log_{10}(f / 193.6) \quad (\text{dB})$$
+
+where:
+
+*f*: is the channel central frequency in THz.
+
+OSNR(*f*): is the minimum optical signal-to-noise ratio of the channel with channel central frequency *f* in dB (0.1 nm).
+
+OSNR(193.6): is the minimum optical signal-to-noise ratio referred to 193.6 THz in dB (0.1 nm).
+
+### 7.4.3 Receiver OSNR tolerance and OSNR tolerance(193.6)
+
+The receiver OSNR tolerance is defined as the minimum value of OSNR at point Rs that can be tolerated while maintaining the maximum BER of the application. This must be met for all powers between the maximum and minimum mean input power with a transmitter with worst-case values of:
+
+- transmitter eye mask for NRZ signal classes or EVMRMS for DP-DQPSK signal classes;
+- extinction ratio for NRZ signal classes or IQ offset for DP-DQPSK signal classes;
+- optical return loss at point Ss ,
+- receiver connector degradations;
+- measurement tolerances.
+
+The receiver OSNR tolerance does not have to be met in the presence of chromatic dispersion, non-linear effects, reflections from the optical path, PMD, PDL or optical crosstalk; these effects are specified separately in the allocation of maximum optical path OSNR penalty.
+
+For 100 Gbit/s applications, specified in Tables 8-7 and 8-8, the receiver optical signal-to-noise ratio tolerance is specified as a function of channel frequency *f* and referred to its value at 193.6 THz, receiver OSNR tolerance(193.6), according to the following relationship:
+
+$$OSNR\_tolerance(f) = OSNR\_tolerance(193.6) - 20 \log_{10}(f / 193.6) \quad (\text{dB})$$
+
+where:
+
+$f$ is the channel central frequency in THz.
+
+$OSNR\_tolerance(f)$ is the receiver optical signal-to-noise ratio tolerance of the channel with channel central frequency $f$ in dB (0.1 nm).
+
+$OSNR\_tolerance(193.6)$ is the receiver optical signal-to-noise ratio tolerance referred to 193.6 THz in dB (0.1 nm).
+
+NOTE 1 – The receiver OSNR tolerance is equal to the minimum OSNR at point $R_s$ minus the maximum optical path OSNR penalty.
+
+NOTE 2 – The receiver OSNR tolerance does not have to be met in the presence of transmitter jitter in excess of the appropriate jitter generation limit (e.g., [b-ITU-T G.8251] for OTN optical tributary signals).
+
+Ageing effects are not specified separately. Worst-case, end-of-life values are specified.
+
+### 7.4.4 Maximum reflectance of receiver
+
+Reflections from the receiver back into the DWDM link are specified by the maximum permissible reflectance of the receiver measured at reference point $R_s$ . Optical reflectance is defined in [ITU-T G.671].
+
+# 8 Parameter values
+
+The physical layer parameters and values are given in Tables 8-1 to 8-8.
+
+**Table 8-1 – Physical layer parameters and values for class NRZ 2.5G without FEC, 100-GHz-spaced applications**
+
+| Parameter | Units | DN100C-1A2(C) DN100C-1A3(L) DN100C-1A5(C) | | DW100C-1A2(C) DW100C-1A3(L) DW100C-1A5(C) | DN100U-1A2(C) DN100U-1A3(L) DN100U-1A5(C) |
+|---------------------------------------------------|-------|-------------------------------------------------|--|-------------------------------------------------|-------------------------------------------------|
+| | | | | | |
+| General information | | | | | |
+| Minimum channel spacing | GHz | 100 | | | 100 |
+| Bit rate/line coding of optical tributary signals | – | NRZ 2.5G | | | NRZ 2.5G |
+| Maximum bit error ratio | – | $10^{-12}$ | | | $10^{-12}$ |
+| Fibre type | – | G.652, G.653, G.655 | | | G.652, G.653, G.655 |
+| Interface at point S_s | | | | | |
+| Maximum mean channel output power | dBm | +6 | | | +6 |
+| Minimum mean channel output power | dBm | –3 | | | –3 |
+| Minimum central frequency | THz | 191.5 for (C) 186.0 for (L) | | | 191.5 for (C) 186.0 for (L) |
+| Maximum central frequency | THz | 196.2 for (C) 191.5 for (L) | | | 196.2 for (C) 191.5 for (L) |
+| Maximum spectral excursion | GHz | $\pm 12.5$ | | $\pm 20$ | $\pm 12.5$ |
+| Minimum side mode suppression ratio | dB | 30 | | | 30 |
+| Minimum channel extinction ratio | dB | 8.2 | | | 8.2 |
+
+**Table 8-1 – Physical layer parameters and values for class NRZ 2.5G without FEC, 100-GHz-spaced applications**
+
+| Parameter | Units | DN100C-1A2(C) | DW100C-1A2(C) | DN100U-1A2(C) |
+|------------------------------------------------------------------------|---------------|----------------------|---------------|----------------------|
+| | | DN100C-1A3(L) | DW100C-1A3(L) | DN100U-1A3(L) |
+| DN100C-1A5(C) | DW100C-1A5(C) | DN100U-1A5(C) | | |
+| Eye mask | – | NRZ 2.5G per G.959.1 | | NRZ 2.5G per G.959.1 |
+| Maximum transmitter (residual) dispersion OSNR penalty | dB | 2 | | 2 |
+| Optical path from point Ss to Rs | | | | |
+| Maximum ripple | dB | 2 | | 2 |
+| Maximum (residual) chromatic dispersion | ps/nm | +2200 | | +9600 |
+| Minimum (residual) chromatic dispersion | ps/nm | –600 | | 0 |
+| Minimum optical return loss at S s | dB | 24 | | 24 |
+| Maximum discrete reflectance between S s and R s | dB | –27 | | –27 |
+| Maximum differential group delay | ps | 120 | | 120 |
+| Maximum polarization dependent loss | dB | ffs | | ffs |
+| Maximum inter-channel crosstalk | dB | –16 | | –16 |
+| Maximum interferometric crosstalk | dB | –40 | | –40 |
+| Maximum optical path OSNR penalty | dB | 5 | | 5 |
+| Interface at point Rs | | | | |
+| Maximum mean input power | dBm | –9 | | –9 |
+| Minimum mean input power | dBm | –24 | | –24 |
+| Minimum OSNR | dB (0.1 nm) | 21 | 23 | 21 |
+| Receiver OSNR tolerance | dB (0.1 nm) | 16 | 18 | 16 |
+| Maximum reflectance of receiver | dB | –27 | | –27 |
+
+**Table 8-2 – Physical layer parameters and values for class NRZ 2.5G with FEC enabled, 100-GHz-spaced applications**
+
+| Parameter | Units | DW100C-1A2(C)F |
+|----------------------------|-------|----------------|
+| | | DW100C-1A3(L)F |
+| DW100C-1A5(C)F | | |
+| General information | | |
+| Minimum channel spacing | GHz | 100 |
+
+**Table 8-2 – Physical layer parameters and values for class NRZ 2.5G
+with FEC enabled, 100-GHz-spaced applications**
+
+| Parameter | Units | DW100C-1A2(C)F DW100C-1A3(L)F DW100C-1A5(C)F |
+|------------------------------------------------------------------------|-------------|----------------------------------------------------|
+| Bit rate/line coding of optical tributary signals | – | NRZ OTU1 FEC enabled |
+| Maximum bit error ratio | – | $10^{-12}$ (Note) |
+| Fibre type | – | G.652, G.653, G.655 |
+| Interface at point Ss | | |
+| Maximum mean channel output power | dBm | +6 |
+| Minimum mean channel output power | dBm | –3 |
+| Minimum central frequency | THz | 191.5 for (C) 186.0 for (L) |
+| Maximum central frequency | THz | 196.2 for (C) 191.5 for (L) |
+| Maximum spectral excursion | GHz | ±20 |
+| Minimum side mode suppression ratio | dB | 30 |
+| Minimum channel extinction ratio | dB | 8.2 |
+| Eye mask | – | NRZ 2.5G per G.959.1 |
+| Maximum transmitter (residual) dispersion OSNR penalty | dB | 2 |
+| Optical path from point Ss to Rs | | |
+| Maximum ripple | dB | 2 |
+| Maximum (residual) chromatic dispersion | ps/nm | +2200 |
+| Minimum (residual) chromatic dispersion | ps/nm | –600 |
+| Minimum optical return loss at S s | dB | 24 |
+| Maximum discrete reflectance between S s and R s | dB | –27 |
+| Maximum differential group delay | ps | 120 |
+| Maximum polarization dependent loss | dB | ffs |
+| Maximum inter-channel crosstalk | dB | –16 |
+| Maximum interferometric crosstalk | dB | –40 |
+| Maximum optical path OSNR penalty | dB | 5 |
+| Interface at point Rs | | |
+| Maximum mean input power | dBm | –9 |
+| Minimum mean input power | dBm | –26 |
+| Minimum OSNR | dB (0.1 nm) | 15 |
+| Receiver OSNR tolerance | dB (0.1 nm) | 10 |
+| Maximum reflectance of receiver | dB | –27 |
+
+NOTE – The BER for these application codes is required to be met only after the error correction (if used) has been applied. The BER at the input of the FEC decoder can, therefore, be significantly higher than $10^{-12}$ .
+
+**Table 8-3 – Physical layer parameters and values for class NRZ 10G
+without FEC, 100-GHz-spaced applications**
+
+| Parameter | Units | DN100C-2A2(C) DN100C-2A3(L) DN100C-2A5(C) | DW100C-2A2(C) DW100C-2A3(L) DW100C-2A5(C) |
+|------------------------------------------------------------------------|-------------|-------------------------------------------------|-------------------------------------------------|
+| | | | |
+| | | | |
+| General information | | | |
+| Minimum channel spacing | GHz | 100 | |
+| Bit rate/line coding of optical tributary signals | – | NRZ 10G | |
+| Maximum bit error ratio | – | $10^{-12}$ | |
+| Fibre type | – | G.652, G.653, G.655 | |
+| Interface at point SS | | | |
+| Maximum mean channel output power | dBm | +6 | |
+| Minimum mean channel output power | dBm | –3 | |
+| Minimum central frequency | THz | 191.5 for (C) 186.0 for (L) | |
+| Maximum central frequency | THz | 196.2 for (C) 191.5 for (L) | |
+| Maximum spectral excursion | GHz | ±12.5 | ±20 |
+| Minimum side mode suppression ratio | dB | 30 | |
+| Minimum channel extinction ratio | dB | 8.2 | |
+| Eye mask | – | NRZ 10G 1550 nm region per G.959.1 | |
+| Maximum transmitter (residual) dispersion OSNR penalty | dB | 2 | |
+| Optical path from point SS to RS | | | |
+| Maximum ripple | dB | 2 | |
+| Maximum (residual) chromatic dispersion | ps/nm | +800 | |
+| Minimum (residual) chromatic dispersion | ps/nm | –300 | |
+| Minimum optical return loss at S S | dB | 24 | |
+| Maximum discrete reflectance between S S and R S | dB | –27 | |
+| Maximum differential group delay | ps | 30 | |
+| Maximum polarization dependent loss | dB | ffs | |
+| Maximum inter-channel crosstalk | dB | –16 | |
+| Maximum interferometric crosstalk | dB | –40 | |
+| Maximum optical path OSNR penalty | dB | 5 | |
+| Interface at point RS | | | |
+| Maximum mean input power | dBm | 0 | –8 |
+| Minimum mean input power | dBm | –11 | –17 |
+| Minimum OSNR | dB (0.1 nm) | 27 | |
+| Receiver OSNR tolerance | dB (0.1 nm) | 22 | |
+| Maximum reflectance of receiver | dB | –27 | |
+
+**Table 8-4 – Physical layer parameters and values for class NRZ 10G with FEC enabled, 100-GHz-spaced applications**
+
+| Parameter | Units | DN100C-2A2(C)F DN100C-2A3(L)F DN100C-2A5(C)F | | DW100C-2A2(C)F DW100C-2A3(L)F DW100C-2A5(C)F | | DN100U-2A2(C)F DN100U-2A3(L)F DN100U-2A5(C)F | |
+|------------------------------------------------------------------------|-------------|----------------------------------------------------|--|----------------------------------------------------|--|----------------------------------------------------|--|
+| | | | | | | | |
+| General information | | | | | | | |
+| Minimum channel spacing | GHz | 100 | | 100 | | | |
+| Bit rate/line coding of optical tributary signals | – | NRZ OTU2 FEC enabled | | NRZ OTU2 FEC enabled | | | |
+| Maximum bit error ratio | – | $10^{-12}$ (Note) | | $10^{-12}$ (Note) | | | |
+| Fibre type | – | G.652, G.653, G.655 | | G.652, G.653, G.655 | | | |
+| Interface at point Ss | | | | | | | |
+| Maximum mean channel output power | dBm | +6 | | +6 | | | |
+| Minimum mean channel output power | dBm | –3 | | –3 | | | |
+| Minimum central frequency | THz | 191.5 for (C) 186.0 for (L) | | 191.5 for (C) 186.0 for (L) | | | |
+| Maximum central frequency | THz | 196.2 for (C) 191.5 for (L) | | 196.2 for (C) 191.5 for (L) | | | |
+| Maximum spectral excursion | GHz | $\pm 12.5$ | | $\pm 20$ | | $\pm 12.5$ | |
+| Minimum side mode suppression ratio | dB | 30 | | 30 | | | |
+| Minimum channel extinction ratio | dB | 8.2 | | 8.2 | | | |
+| Eye mask | – | NRZ 10G 1550 nm region per G.959.1 | | NRZ 10G amplified per G.959.1 | | | |
+| Maximum transmitter (residual) dispersion OSNR penalty | dB | 2 | | 2 | | | |
+| Optical path from point Ss to Rs | | | | | | | |
+| Maximum ripple | dB | 2 | | 2 | | | |
+| Maximum (residual) chromatic dispersion | ps/nm | +800 | | +3200 | | | |
+| Minimum (residual) chromatic dispersion | ps/nm | –300 | | 0 | | | |
+| Minimum optical return loss at S s | dB | 24 | | 24 | | | |
+| Maximum discrete reflectance between S s and R s | dB | –27 | | –27 | | | |
+| Maximum differential group delay | ps | 30 | | 30 | | | |
+| Maximum polarization dependent loss | dB | ffs | | ffs | | | |
+| Maximum inter-channel crosstalk | dB | –16 | | –16 | | | |
+| Maximum interferometric crosstalk | dB | –40 | | –40 | | | |
+| Maximum optical path OSNR penalty | dB | 5 | | 5 | | | |
+| Interface at point Rs | | | | | | | |
+| Maximum mean input power | dBm | 0 | | –8 | | 0 | |
+| Minimum mean input power | dBm | –14 | | –20 | | –14 | |
+| Minimum OSNR | dB (0.1 nm) | 21 | | 21 | | | |
+| Receiver OSNR tolerance | dB (0.1 nm) | 16 | | 16 | | | |
+| Maximum reflectance of receiver | dB | –27 | | –27 | | | |
+
+NOTE – The BER for these application codes is required to be met only after the error correction (if used) has been applied. The BER at the input of the FEC decoder can, therefore, be significantly higher than $10^{-12}$ .
+
+**Table 8-5 – Physical layer parameters and values for class NRZ 10G without FEC, 50-GHz-spaced applications**
+
+| Parameter | Units | DN50C-2A2(C) DN50C-2A3(L) DN50C-2A5(C) | |
+|------------------------------------------------------------------------|-------------|----------------------------------------------|--------------|
+| General information | | | |
+| Minimum channel spacing | GHz | 50 | |
+| Bit rate/line coding of optical tributary signals | – | NRZ 10G | |
+| Maximum bit error ratio | – | $10^{-12}$ | |
+| Fibre type | – | G.652, G.653, G.655 | |
+| Interface at point Ss | | | |
+| Maximum mean channel output power | dBm | +6 | |
+| Minimum mean channel output power | dBm | –3 | |
+| Minimum central frequency | THz | 191.5 for (C) 186.0 for (L) | |
+| Maximum central frequency | THz | 196.2 for (C) 191.5 for (L) | |
+| Maximum spectral excursion | GHz | $\pm 11$ ( $\pm 12.5$ Note 1) | |
+| Minimum side mode suppression ratio | dB | 30 | |
+| Minimum channel extinction ratio | dB | 8.2 | |
+| Eye mask | – | NRZ 10G 1550 nm region per G.959.1 | |
+| Maximum transmitter (residual) dispersion OSNR penalty | dB | 2 | |
+| Optical path from point Ss to Rs | | | |
+| Maximum ripple | dB | 2 | |
+| Maximum (residual) chromatic dispersion | ps/nm | +800 | |
+| Minimum (residual) chromatic dispersion | ps/nm | –300 | |
+| Minimum optical return loss at S s | dB | 24 | |
+| Maximum discrete reflectance between S s and R s | dB | –27 | |
+| Maximum differential group delay | ps | 30 | |
+| Maximum polarization dependent loss | dB | ffs | |
+| Maximum inter-channel crosstalk | dB | –16 | |
+| Maximum interferometric crosstalk | dB | –40 | |
+| Maximum optical path OSNR penalty | dB | 5 | |
+| Interface at point Rs | | | |
+| Maximum mean input power | dBm | 0 (Note 2) | –8 (Note 3) |
+| Minimum mean input power | dBm | –11 (Note 2) | –17 (Note 3) |
+| Minimum OSNR | dB (0.1 nm) | 27 | |
+| Receiver OSNR tolerance | dB (0.1 nm) | 22 | |
+| Maximum reflectance of receiver | dB | –27 | |
+
+NOTE 1 – If the ripple specification of the black link is met over a width of at least $\pm 12.5$ GHz, then the transmitter can have a maximum spectral excursion of $\pm 12.5$ GHz.
+NOTE 2 – These power levels are appropriate for P type-intrinsic-n type (PIN) receivers. As an alternative, the power levels appropriate for avalanche photodiode (APD) receivers can be used.
+NOTE 3 – These power levels are appropriate for APD receivers. As an alternative, the power levels appropriate for PIN receivers can be used.
+
+**Table 8-6 – Physical layer parameters and values for class NRZ 10G
+with FEC, 50-GHz-spaced applications**
+
+| Parameter | Units | DN50C-2A2(C)F DN50C-2A3(L)F DN50C-2A5(C)F | DN50U-2A2(C)F DN50U-2A3(L)F DN50U-2A5(C)F |
+|---------------------------------------------------------------|-------|-------------------------------------------------|-------------------------------------------------|
+| General information | | | |
+| Minimum channel spacing | GHz | 50 | 50 |
+| Bit rate/line coding of optical tributary signals | – | NRZ OTU2 FEC enabled | NRZ OTU2 FEC enabled |
+| Maximum bit error ratio | – | $10^{-12}$ (Note 1) | $10^{-12}$ (Note 1) |
+| Fibre type | – | G.652, G.653, G.655 | G.652, G.653, G.655 |
+| Interface at point Ss | | | |
+| Maximum mean channel output power | dBm | +6 | +6 |
+| Minimum mean channel output power | dBm | –3 | –3 |
+| Minimum central frequency | THz | 191.5 for (C) 186.0 for (L) | 191.5 for (C) 186.0 for (L) |
+| Maximum central frequency | THz | 196.2 for (C) 191.5 for (L) | 196.2 for (C) 191.5 for (L) |
+| Maximum spectral excursion | GHz | $\pm 11$ ( $\pm 12.5$ Note 2) | $\pm 11$ ( $\pm 12.5$ Note 2) |
+| Minimum side mode suppression ratio | dB | 30 | 30 |
+| Minimum channel extinction ratio | dB | 8.2 | 8.2 |
+| Eye mask | – | NRZ 10G 1550 nm region per G.959.1 | NRZ 10G amplified per G.959.1 |
+| Maximum transmitter (residual) dispersion OSNR penalty | dB | 2 | 2 |
+| Optical path from point Ss to Rs | | | |
+| Maximum ripple | dB | 2 | 2 |
+| Maximum (residual) chromatic dispersion | ps/nm | +800 | +3200 |
+| Minimum (residual) chromatic dispersion | ps/nm | –300 | 0 |
+| Minimum optical return loss at SS | dB | 24 | 24 |
+| Maximum discrete reflectance between SS and RS | dB | –27 | –27 |
+| Maximum differential group delay | ps | 30 | 30 |
+| Maximum polarization dependent loss | dB | ffs | ffs |
+| Maximum inter-channel crosstalk | dB | –16 | –16 |
+| Maximum interferometric crosstalk | dB | –40 | –40 |
+| Maximum optical path OSNR penalty | dB | 5 | 5 |
+
+**Table 8-6 – Physical layer parameters and values for class NRZ 10G with FEC, 50-GHz-spaced applications**
+
+| Parameter | Units | DN50C-2A2(C)F DN50C-2A3(L)F DN50C-2A5(C)F | | DN50U-2A2(C)F DN50U-2A3(L)F DN50U-2A5(C)F | |
+|---------------------------------|-------------|-------------------------------------------------|--------------|-------------------------------------------------|--------------|
+| | | | | | |
+| Interface at point Rs | | | | | |
+| Maximum mean input power | dBm | 0 (Note 3) | -8 (Note 4) | 0 (Note 3) | -8 (Note 4) |
+| Minimum mean input power | dBm | -14 (Note 3) | -20 (Note 4) | -14 (Note 3) | -20 (Note 4) |
+| Minimum OSNR | dB (0.1 nm) | 21 | | 21 | |
+| Receiver OSNR tolerance | dB (0.1 nm) | 16 | | 16 | |
+| Maximum reflectance of receiver | dB | -27 | | -27 | |
+
+NOTE 1 – The BER for these application codes is required to be met only after the error correction (if used) has been applied. The BER at the input of the FEC decoder can, therefore, be significantly higher than $10^{-12}$ .
+
+NOTE 2 – If the ripple specification of the black link is met over a width of at least $\pm 12.5$ GHz, then the transmitter can have a maximum spectral excursion of $\pm 12.5$ GHz.
+
+NOTE 3 – These power levels are appropriate for PIN receivers. As an alternative, the power levels appropriate for APD receivers can be used.
+
+NOTE 4 – These power levels are appropriate for APD receivers. As an alternative, the power levels appropriate for PIN receivers can be used.
+
+**Table 8-7 – Physical layer parameters and values for
+class DP-DQPSK 100G, narrow spectral excursion applications**
+
+| Parameter | Units | DN50U-8A2(C)F | DN50U-8A3(L)F | DN50U-8A5(C)F | DN100U-8A2(C)F | DN100U-8A3(L)F | DN100U-8A5(C)F |
+|------------------------------------------------------------------------|--------|--------------------------------|---------------|---------------|----------------|----------------|----------------|
+| | | 50 | | | 100 | | |
+| General information | | | | | | | |
+| Minimum channel spacing | GHz | 50 | | | 100 | | |
+| Bit rate/line coding of optical tributary signals | – | OTL4.4-SC or FOIC1.4-SC | | | | | |
+| Maximum bit error ratio | – | $10^{-12}$ (Note 1) | | | | | |
+| Fibre type | – | G.652, G.653, G.655 | | | | | |
+| Interface at point Ss | | | | | | | |
+| Maximum mean channel output power | dBm | 0 | | | | | |
+| Minimum mean channel output power | dBm | –5 | | | | | |
+| Minimum central frequency | THz | 191.5 for (C) 186.0 for (L) | | | | | |
+| Maximum central frequency | THz | 196.2 for (C) 191.5 for (L) | | | | | |
+| Maximum spectral excursion | GHz | $\pm 15$ | | | | | |
+| Minimum side mode suppression ratio | dB | 30 | | | | | |
+| Maximum laser linewidth | kHz | 500 | | | | | |
+| Maximum offset between the carrier and the nominal central frequency | GHz | 1.8 | | | | | |
+| Maximum power difference between polarizations | dB | 1.5 | | | | | |
+| Maximum skew between the two polarizations | ps | 5 | | | | | |
+| Maximum error vector magnitude | % | 26 | | | | | |
+| Maximum I-Q offset | dB | –25 | | | | | |
+| Optical path from point Ss to Rs | | | | | | | |
+| Maximum ripple | dB | 2.5 | | | | | |
+| Maximum (residual) chromatic dispersion | ps/nm | 10 000 | | | | | |
+| Minimum (residual) chromatic dispersion | ps/nm | –820 | | | | | |
+| Minimum optical return loss at S s | dB | 24 | | | | | |
+| Maximum discrete reflectance between S s and R s | dB | –27 | | | | | |
+| Maximum differential group delay | ps | 50 | | | | | |
+| Maximum polarization dependent loss | dB | 2 | | | | | |
+| Maximum polarization rotation speed | krad/s | 50 | | | | | |
+| Maximum inter-channel crosstalk | dB | –16 | | | | | |
+| Maximum interferometric crosstalk | dB | –25 | | | | | |
+| Maximum optical path OSNR penalty | dB | 5 | | | | | |
+
+**Table 8-7 – Physical layer parameters and values for
+class DP-DQPSK 100G, narrow spectral excursion applications**
+
+| Parameter | Units | DN50U-8A2(C)F DN50U-8A3(L)F DN50U-8A5(C)F | DN100U-8A2(C)F DN100U-8A3(L)F DN100U-8A5(C)F |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------------------------------------------|----------------------------------------------------|
+| Interface at point Rs | | | |
+| Maximum mean input power | dBm | 0 | |
+| Minimum mean input power | dBm | –18 | |
+| Minimum OSNR(193.6) (Note 2) | dB (0.1 nm) | 21 | |
+| Receiver OSNR tolerance(193.6) (Note 3) | dB (0.1 nm) | 16 | |
+| Maximum reflectance of receiver | dB | –27 | |
+| NOTE 1 – The BER for these application codes is required to be met only after the error correction (if used) has been applied. The BER at the input of the FEC decoder can, therefore, be significantly higher than $10^{-12}$ . | | | |
+| NOTE 2 – The value for minimum OSNR(193.6) is specified at a channel frequency of 193.6 THz. For OSNR values at other channel frequencies, the formula shown in clause 7.4.2 should be applied. | | | |
+| NOTE 3 – The value for receiver OSNR tolerance(193.6) is specified at a channel frequency of 193.6 THz. For OSNR tolerance values at other channel frequencies, the formula shown in clause 7.4.3 should be applied. | | | |
+
+**Table 8-8 – Physical layer parameters and values for
+class DP-DQPSK 100G, wide spectral excursion applications**
+
+| Parameter | Units | DW50U-8A2(C)F DW50U-8A3(L)F DW50U-8A5(C)F | DW100U-8A2(C)F DW100U-8A3(L)F DW100U-8A5(C)F |
+|---------------------------------------------------|-------|-------------------------------------------------|----------------------------------------------------|
+| General information | | | |
+| Minimum channel spacing | GHz | 50 | 100 |
+| Bit rate/line coding of optical tributary signals | – | OTL4.4-SC or FOIC1.4-SC | |
+| Maximum bit error ratio | – | $10^{-12}$ (Note 1) | |
+| Fibre type | – | G.652, G.653, G.655 | |
+| Interface at point Ss | | | |
+| Maximum mean channel output power | dBm | –3 | |
+| Minimum mean channel output power | dBm | –8 | |
+| Minimum central frequency | THz | 191.5 for (C) 186.0 for (L) | |
+| Maximum central frequency | THz | 196.2 for (C) 191.5 for (L) | |
+| Maximum spectral excursion | GHz | $\pm 15$ | |
+
+**Table 8-8 – Physical layer parameters and values for
+class DP-DQPSK 100G, wide spectral excursion applications**
+
+| Parameter | Units | DW50U-8A2(C)F | DW50U-8A3(L)F | DW50U-8A5(C)F | DW100U-8A2(C)F | DW100U-8A3(L)F | DW100U-8A5(C)F |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------------------------------|---------------|---------------|----------------|----------------|----------------|
+| | | Minimum side mode suppression ratio | dB | 30 | | | |
+| Maximum laser linewidth | kHz | 500 | | | | | |
+| Maximum offset between the carrier and the nominal central frequency | GHz | 1.8 | | | | | |
+| Maximum power difference between polarizations | dB | 1.5 | | | | | |
+| Maximum skew between the two polarizations | ps | 10 | | | | | |
+| Maximum error vector magnitude | % | 23 | | | | | |
+| Maximum I-Q offset | dB | -25 | | | | | |
+| Optical path from point Ss to Rs | | | | | | | |
+| Maximum ripple | dB | 2.5 | | | | | |
+| Maximum (residual) chromatic dispersion | ps/nm | 2 400 | | | | | |
+| Minimum (residual) chromatic dispersion | ps/nm | -200 | | | | | |
+| Minimum optical return loss at S s | dB | 24 | | | | | |
+| Maximum discrete reflectance between S s and R s | dB | -27 | | | | | |
+| Maximum differential group delay | ps | 20 | | | | | |
+| Maximum polarization dependent loss | dB | 1.5 | | | | | |
+| Maximum polarization rotation speed | krad/s | 50 | | | | | |
+| Maximum inter-channel crosstalk | dB | -16 | | | | | |
+| Maximum interferometric crosstalk | dB | -25 | | | | | |
+| Maximum optical path OSNR penalty | dB | 5 | | | | | |
+| Interface at point Rs | | | | | | | |
+| Maximum mean input power | dBm | 0 | | | | | |
+| Minimum mean input power | dBm | -18 | | | | | |
+| Minimum OSNR(193.6) (Note 2) | dB (0.1 nm) | 24 | | | | | |
+| Receiver OSNR tolerance(193.6) (Note 3) | dB (0.1 nm) | 19 | | | | | |
+| Maximum reflectance of receiver | dB | -27 | | | | | |
+| NOTE – The BER for these application codes is required to be met only after the error correction (if used) has been applied. The BER at the input of the FEC decoder can, therefore, be significantly higher than $10^{-12}$ . NOTE 2 – The value for minimum OSNR(193.6) is specified at a channel frequency of 193.6 THz. For OSNR values at other channel frequencies, the formula shown in clause 7.4.2 should be applied. NOTE 3 – The value for receiver OSNR tolerance(193.6) is specified at a channel frequency of 193.6 THz. For OSNR tolerance values at other channel frequencies, the formula shown in clause 7.4.3 should be applied. | | | | | | | |
+
+# 9 Optical safety considerations
+
+See [ITU-T G.664], [IEC 60825-1] and [IEC 60825-2] for optical safety considerations.
+
+# Annex A
+
+## Reference receiver characteristics for DP-DQPSK 100G
+
+(This annex forms an integral part of this Recommendation.)
+
+The reference receiver includes the following steps as defined in the EVM calculation in clause 7.2.12, except the first item:
+
+- compensate for chromatic dispersion and differential group delay;
+- demultiplex the two polarizations;
+- remove the frequency offset between carrier laser and local oscillator;
+- recover the carrier phase;
+- retiming and resampling to one sample per symbol;
+- compensate for IQ-offset;
+- apply a 7-tap T-spaced FIR filter with the tap coefficients optimized for BER.
+
+## Appendix I
+
+### Measurement of transmitter (residual) dispersion OSNR penalty and optical path OSNR penalty
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Since the applications in this Recommendation use the "black link" approach, single-channel reference points ( $S_s$ and $R_s$ ) can be used to access the individual signals for measuring OSNR penalty. Three measurements for OSNR penalty are performed as illustrated in Figures I.1 to I.3.
+
+For measurement 1, the lowest OSNR to achieve the reference BER at $S_s$ with no dispersion is established by varying the amount of ASE noise added to the signal using a set-up similar to that shown in Figure I.1.
+
+For measurement 2, the lowest OSNR to achieve the reference BER at $S_s$ with worst case (residual) dispersion is established using a set-up similar to that shown in Figure I.2.
+
+For measurement 3, the lowest OSNR to achieve the reference BER at $R_s$ *after* transmission through the black link is established using a set-up similar to that shown in Figure I.3.
+
+In the case of transmitter (residual) dispersion OSNR penalty, measurements 1 and 2 are performed as above and then:
+
+Maximum transmitter (residual) dispersion OSNR penalty = OSNR of measurement 2 – OSNR of measurement 1.
+
+In the case of optical path OSNR penalty, measurements 1 and 3 are performed as above and then:
+
+Maximum optical path OSNR penalty = OSNR of measurement 3 – OSNR of measurement 1.
+
+
+
+```
+graph LR; ASE[ASE] --> VOA[Variable optical attenuator]; VOA --> OC1[Optical coupler]; Tx["Tx λN"] -- Ss --> OC1; OC1 --> OC2[Optical coupler]; OC2 --> OSNR[OSNR monitor]; OC2 --> FBF["Reference bandpass filter λN"]; FBF --> RR[Reference receiver];
+```
+
+Figure I.1: Configuration for measurement 1 (at Ss). The diagram shows a transmitter (Tx λN) connected to an optical coupler at point Ss. ASE noise is added via a variable optical attenuator. The signal then splits: one path goes to an OSNR monitor, and the other goes through another optical coupler, a reference bandpass filter λN, and a reference receiver. The label G.698.2(18)\_FI.1 is present.
+
+Figure I.1 – Configuration for measurement 1 (at $S_s$ )
+
+
+
+```
+graph LR; ASE[ASE] --> VOA[Variable optical attenuator]; VOA --> OC1[Optical coupler]; Tx["Tx λN"] -- Ss --> OC1; OC1 --> CD[Chromatic dispersion]; CD --> OC2[Optical coupler]; OC2 --> OSNR[OSNR monitor]; OC2 --> FBF["Reference bandpass filter λN"]; FBF --> RR[Reference receiver];
+```
+
+Figure I.2: Configuration for measurement 2 (at Ss). This diagram is similar to Figure I.1 but includes a 'Chromatic dispersion' block between the first and second optical couplers. The label G.698.2(18)\_FI.2 is present.
+
+Figure I.2 – Configuration for measurement 2 (at $S_s$ )
+
+
+
+Figure I.3 – Configuration for measurement 3 (at Rs). The diagram shows a DWDM link with network elements (OM, OD, and a dispersion element). Transmitters (Tx λ1, Tx λ2, ..., Rx λN) are connected to the link at points Ss. Receivers (Rx λ1, ..., Rx λN) are connected at points Rs. A monitoring path branches off from the Rs point, passing through an optical coupler, a variable optical attenuator (VOA) controlled by ASE, another optical coupler, an OSNR monitor, a reference bandpass filter (λ1), and a reference receiver. The diagram is labeled G.698.2(18)\_FI.3.
+
+**Figure I.3 – Configuration for measurement 3 (at Rs)**
+
+It should be noted that:
+
+- The reference bandpass filter is defined in clause B.2 of [ITU-T G.959.1].
+- The reference receiver is defined in clause B.3 of [ITU-T G.959.1].
+- The means used to introduce the chromatic dispersion in measurement 2 should not result in non-linear effects. Any optical amplifiers used to offset the loss of this dispersive element should be inserted before the OSNR monitoring point.
+- The amount of ASE noise that is added to the signal at Ss or Rs (and therefore the OSNR) is controlled by adjusting the variable optical attenuator (VOA). The OSNR monitoring point should be after the last optical amplifier, e.g., before the reference bandpass filter.
+- When significant noise shaping is present before the monitoring point, e.g., at point Rs due to OD filtering or OADMs in the black link, care must be taken to use an OSNR monitoring technique that gives an accurate reading. More information on this issue can be found in Appendix III of [b-ITU-T G.697].
+- An optical amplifier or optical attenuator may be used when the input power of the reference receiver is not appropriate, however, any added optical amplifiers must be placed before the OSNR monitoring point.
+
+## Appendix II
+
+### Transponder elimination via single channel DWDM interfaces
+
+(This appendix does not form an integral part of this Recommendation.)
+
+The transport network of most operators is based on the use of equipment from a variety of different vendors.
+
+Previously, for those parts of the network involving DWDM optical transmission, this has been achieved via the use of optical transponders as shown in Figure II.1. The optical interfaces labelled "single channel non-DWDM interfaces from other vendor(s)" and "Single channel non-DWDM interfaces to/from other vendor(s)" can then be any short-reach standardized optical interface that both vendors support, such as those found in [ITU-T G.957] [ITU-T G.691], [ITU-T G.693], [ITU-T G.959.1], etc. This arrangement allows the direct connection of a wide variety of equipment to the DWDM line system, for example:
+
+- a digital cross-connect with multiple optical interfaces, supplied by a different vendor from the line system;
+- multiple optical client devices, each from a different vendor, supplying one channel each;
+- a combination of the above.
+
+Through the use of the single channel DWDM interfaces found in this Recommendation, however, this interconnection can also be achieved while removing the need for one short reach transmitter and receiver pair per channel (eliminating the transponders) with obvious associated cost savings.
+
+This is shown in Figure II.2.
+
+
+
+The diagram illustrates a multivendor DWDM line system. A central grey box labeled "System provided by a single vendor" contains a DWDM link. On the left, multiple "Tx" (transmitter) blocks are connected to "Rx" (receiver) blocks, which are then connected to "Tx" blocks, forming "Transponders". These transponders are connected to an "OM" (optical multiplexer). The "OM" is connected to a "DWDM link" which consists of an "OADM" (optical add-drop multiplexer) and two "OD" (optical demultiplexer) units. The "OADM" is connected to a "Tx" block, which is connected to an "Rx" block, forming another transponder. The "OD" units are connected to "Rx" blocks, which are then connected to "Tx" blocks, forming transponders. These transponders are connected to "Single channel non-DWDM interfaces to other vendor(s)". The "Single channel non-DWDM interfaces from other vendor(s)" are connected to "Tx" blocks, which are connected to "Rx" blocks, forming transponders. These transponders are connected to the "OM".
+
+Diagram of a multivendor DWDM line system with transponders.
+
+G.698.2(09)\_FII-1
+
+Figure II.1 – Multivendor DWDM line system with transponders
+
+
+
+Diagram of a multivendor DWDM line system with transponders removed. It shows a central 'DWDM link' (labeled 'Black-link' provided by a single vendor) containing an Optical Multiplexer (OM), an Optical Add-Drop Multiplexer (OADM), and an Optical Demultiplexer (OD). On the left, multiple transmitters (Tx) with wavelengths λ1, λ2, ..., λn and signals S1, S2, ..., Sn are connected to the OM. On the right, the OD is connected to multiple receivers (Rx) with wavelengths λ1, λ2, ..., λn and signals R1, R2, ..., Rn. Below the main link, a dashed box shows a receiver (Rx) with signal Rx and wavelength λx connected to a transmitter (Tx) with signal Sx and wavelength λy. Vertical text on the left and right identifies 'Single channel DWDM interfaces from other vendor(s)' and 'Single channel DWDM interfaces to/from other vendor(s)' respectively. The diagram is labeled G.698.2(09)\_FII-2.
+
+**Figure II.2 – Multivendor DWDM line system with transponders removed**
+
+# Bibliography
+
+- [b-ITU-T G.697] Recommendation ITU-T G.697 (2009), *Optical monitoring for dense wavelength division multiplexing systems.*
+- [b-ITU-T G.8251] Recommendation ITU-T G.8251 (2001), *The control of jitter and wander within the optical transport network (OTN).*
+- [b-ITU-T G-Sup.39] ITU-T G-series Recommendations – Supplement 39 (2006), *Optical system design and engineering considerations.*
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/G/T-REC-G.702-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg b/marked/G/T-REC-G.702-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da20fab7ca7ef10c6db4e7c65f0251cd40529736
--- /dev/null
+++ b/marked/G/T-REC-G.702-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4b56f8173a325a6f6cad15736f5edfb8449d8da22107cb01034c8483db8a13e8
+size 184315
diff --git a/marked/G/T-REC-G.702-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.702-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7
--- /dev/null
+++ b/marked/G/T-REC-G.702-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e
+size 7392
diff --git a/marked/G/T-REC-G.702-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg b/marked/G/T-REC-G.702-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a31b4325be0d3733533924e98ec2ac2db17ceb03
--- /dev/null
+++ b/marked/G/T-REC-G.702-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:52f722feca412a6a0244bede461940e47bb787e7f4ea7b9c6200c1221822b085
+size 187540
diff --git a/marked/G/T-REC-G.702-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.702-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..0224f8f9d3a745e46ca8a38b1ae3f7c9e6db7459
--- /dev/null
+++ b/marked/G/T-REC-G.702-198811-I_PDF-E/raw.md
@@ -0,0 +1,213 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**G.702**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**GENERAL ASPECTS OF DIGITAL TRANSMISSION
+SYSTEMS**
+
+**TERMINAL EQUIPMENTS**
+
+---
+
+**DIGITAL HIERARCHY BIT RATES**
+
+**ITU-T Recommendation G.702**
+
+(Extract from the *Blue Book*)
+
+---
+
+# NOTES
+
+- 1 ITU-T Recommendation G.702 was published in Fascicle III.4 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below).
+- 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+# **DIGITAL HIERARCHY BIT RATES**
+
+*(Malaga-Torremolinos, 1984; amended at Melbourne, 1988)*
+
+The CCITT,
+
+*considering*
+
+(a) that digital hierarchy bit rates are those bit rates which are or will be used as the basis for higher digital hierarchy levels if such levels exist (see Recommendation G.701, definition 4003);
+
+(b) that the specification of hierarchical bit rates is necessary to prevent the proliferation of interface standards used in digital networks;
+
+(c) that international interconnections of digital network components are preferably carried out at hierarchical bit rates;
+
+(d) that when determining hierarchical bit rates a number of factors relating to services, transmission media and networking need to be taken into account, for example:
+
+- characteristics of and suitable coding method for analogue source signals;
+- bit rates of digital source signals;
+- use of available transmission media;
+- compatibility with analogue multiplex systems;
+- modularity and flexibility in assembling and routing groups of source signals,
+
+*recommends*
+
+that the following bit rates should be used as hierarchical bit rates in digital networks:
+
+| Digital Hierarchy Level | Hierarchical bit rates (kbit/s) for networks with the digital hierarchy based on a first level bit rate of | |
+|-------------------------|------------------------------------------------------------------------------------------------------------|-------------|
+| | 1544 kbit/s | 2048 kbit/s |
+| | 64 | 64 |
+| 1 | 1544 | 2 048 |
+| 2 | 6312 | 8 448 |
+| 3 | 32 064 44 736 | 34 368 |
+| 4 | 97 728 | 139 264 |
+
+Figure 1/G.702 and Figure 2/G.702 show the recommended hierarchical bit rates only, including references to related Recommendations on network interfaces, multiplex equipments, digital sections/systems.
+
+Recommendations on the following may also exist, but are not identified in Figure 1/G.702 and Figure 2/G.702:
+
+- multiplex equipments operating between non-adjacent levels of the digital hierarchy;
+- network interfaces, multiplex equipments and digital sections/systems at non-hierarchical bit rates.
+
+Annex A to this Recommendation provides guidelines on usable bits available for services.
+
+
+
+The diagram illustrates the hierarchical bit rates for networks based on the first level bit rate of 1544 kbit/s. It shows various input sources and equipment being multiplexed through different levels of digital multiplexers.
+
+**Input Sources and Equipment:**
+
+- TV: Videoconferencing H.120, H.130
+- Voice (1 to 24): PCM multiplex G.733
+- Voice (1 to 48): ADPCM multiplex G.724
+- Digital exchange G.705, Q.511, Q.512
+- Basic Group B (1 to 2) (60-108 kHz): Transmultiplex G.794
+- Transcoder G.762
+- Digital circuit multiplication equipment G.763
+- Digital line system G.951, G.955
+- Voice (1 to 96): PCM multiplex G.746
+- Digital exchange G.705, Q.511
+- Digital line system G.951, G.955
+- Digital line system G.955
+- Digital line system G.953, G.955
+
+**Multiplexers and Interfaces:**
+
+- Level 1:** Digital multiplex G.734 (inputs: 1 to 23 (24)). Interface G.703 (bit rate: 64 kbit/s).
+- Level 2:** Digital multiplex G.743 (inputs: 1 to 4). Interface G.703 (bit rate: 1544 kbit/s).
+- Level 3:** Two Digital multiplex G.752 units. The first has 1 to 5 inputs, the second has 1 to 7 inputs. Interface G.703 (bit rate: 6312 kbit/s).
+- Level 4:** Two Digital multiplex G.752 units. The first has 1 to 3 inputs, the second has 1 to 7 inputs. Interface G.703 (bit rates: 32064 kbit/s and 44736 kbit/s).
+- Level 5:** Digital line system G.953, G.955. Interface G.703 (bit rate: 97728 kbit/s).
+
+**Hierarchical bit rates and levels:**
+
+| bit rate kbit/s | level |
+|-----------------|-------|
+| 64 | |
+| 1544 | 1 |
+| 6312 | 2 |
+| 32064 | 3 |
+| 44736 | 3 |
+| 97728 | 4 |
+
+TI807761-89
+
+Diagram of hierarchical bit rates for networks with the digital hierarchy based on the first level bit rate of 1544 kbit/s. The diagram shows various input sources (TV, Voice, Basic Group B) being multiplexed through different equipment (Videoconferencing, PCM multiplex, ADPCM multiplex, Digital exchange, Transmultiplex, Transcoder, Digital circuit multiplication equipment, Digital line system) into a hierarchical structure of digital multiplexers (G.734, G.743, G.752) at different levels. The bit rates increase at each level: Level 1 (1544 kbit/s), Level 2 (6312 kbit/s), Level 3 (32064 kbit/s and 44736 kbit/s), and Level 4 (97728 kbit/s). Interfaces G.703 are shown between the levels.
+
+FIGURE 1/G.702
+
+Hierarchical bit rates for networks with the digital hierarchy based on the first level bit rate of 1544 kbit/s
+
+
+
+The diagram illustrates the hierarchical bit rates for networks with the digital hierarchy based on the first level bit rate of 2048 kbit/s. It shows how various input signals are multiplexed together at different levels.
+
+**Inputs and Processing Blocks:**
+
+- TV: Videoconferencing H.120, H.130
+- Voice and/or 64/320/384 kbit/s:
+ - 1 to 30 PCM multiplex G.732, G.735, G.738
+ - Digital exchange G.705, Q.511, Q.512
+- Basic supergroup (312-552 kHz):
+ - Transmultiplex G.793 (inputs 1, 2)
+ - Transcoder G.761 (inputs 1, 2)
+ - Digital circuit multiplication equipment G.763
+ - Digital section/line system G.921, G.952, G.956
+- Voice:
+ - 1 to 120 PCM multiplex G.744
+ - Digital exchange G.705, Q.511
+ - Digital section/line system G.921, G.952, G.954, G.956
+ - Digital line system G.954, G.956
+
+**Multiplexing Hierarchy:**
+
+- Level 1:** Digital multiplex G.736 (inputs 1 to 31) and External access G.737, G.739 (inputs 1 to n) lead to Level 1 at 2048 kbit/s via Interface G.703.
+- Level 2:** Digital multiplex G.742, G.745 (inputs 1 to 4) leads to Level 2 at 8448 kbit/s via Interface G.703.
+- Level 3:** Digital multiplex G.751, G.753 (inputs 1 to 4) leads to Level 3 at 34368 kbit/s via Interface G.703.
+- Level 4:** Digital multiplex G.751, G.754 (inputs 1 to 4) leads to Level 4 at 139264 kbit/s via Interface G.703.
+
+**Hierarchical bit rate table:**
+
+| Hierarchical | |
+|-----------------|-------|
+| bit rate kbit/s | level |
+| 64 | |
+| 2048 | 1 |
+| 8448 | 2 |
+| 34368 | 3 |
+| 139264 | 4 |
+
+T1207771-89
+
+A complex flow diagram showing the multiplexing hierarchy for digital networks. On the left, various input sources like TV (Videoconferencing H.120, H.130), Voice (PCM multiplex G.732, G.735, G.738, G.744), and Basic supergroup (Transmultiplex G.793, Transcoder G.761) are shown. These inputs feed into a series of digital multiplexers (G.736, G.742, G.745, G.751, G.753, G.754) and digital section/line systems. The flow moves from top to bottom and left to right, increasing in bit rate at each level. The levels are marked on the right side: Level 1 (2048 kbit/s), Level 2 (8448 kbit/s), Level 3 (34368 kbit/s), and Level 4 (139264 kbit/s). Interface G.703 is specified at each level transition.
+
+FIGURE 2/G.702
+**Hierarchical bit rates for networks with the digital hierarchy based on the first level bit rate of 2048 kbit/s**
+
+# ANNEX A
+
+(to Recommendation G.702)
+
+## **Usable bit rates available for services**
+
+In the case of access to the ISDN for broadband services, bit rates up to the primary hierarchy level are specified in the I.200 series of Recommendations.
+
+In general, with regard to bit rates available for transport of service signals, the following guidelines apply:
+
+A.1 For the hierarchies based on the 1544 kbit/s primary rate, the principle has been established that some bits in the frame should be reserved, in particular to perform quality control of the digital paths when several digital sections in tandem are involved. Table A-1/G.702 provides the necessary information.
+
+TABLE A-1/G.702
+
+## **Bit rates available for services and frame structures required at hierarchical interfaces**
+
+| Hierarchy bit rate (kbit/s) | Frame structure as per Recommendations | Reserved bits | Bit rate available for services (kbit/s) |
+|-----------------------------|----------------------------------------|-----------------------------------------|------------------------------------------|
+| 1 544 | G. 704 | F a) | 1 536 |
+| 6 312 b) | Not applicable | None | 6 312 |
+| 6 312 c) | G.704 | F bits and bits in time slots 97 and 98 | 6 144 |
+| 44 736 | G.752 | $M_j^d$ $F_0, F_{11}, F_{12}$ | 44 407 d) |
+
+a) The use of the F-bit for purposes additional to framing is under study.
+
+b) In networks with asynchronous operation.
+
+c) In networks with synchronous operation.
+
+d) In some applications, the C-bits ( $C_{j1}$ , $C_{j2}$ and $C_{j3}$ ) may also need to be reserved. In this case, the bit rate available for services becomes 44 209 kbit/s.
+
+A.2 In case of networks using 2048 kbit/s based hierarchy there is in principle no basic restriction on the use of full capacity of the digital path. However, it is recognized that compatibility with recommended frame structures at the various levels of the 2 Mbit/s hierarchy (e.g. the use of the same frame alignment pattern) could be a preferred solution since it offers the following advantages:
+
+- use of the same framing devices for switched and non-switched applications;
+- end-to-end quality control performed in a unique way by the network when the maintenance entity that terminates the service (e.g. the encoding device) does not belong to the network;
+- possibility of performing additional network management functions that could be required, depending on the applications.
+
+The preference for compatibility with recommended frame structures could be reconsidered for the applications where significant restrictions on the efficient use of the digital path capability can be identified.
\ No newline at end of file
diff --git a/marked/G/T-REC-G.7043-200407-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg b/marked/G/T-REC-G.7043-200407-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..482606e40b47d03b0a2e6f1ae557fcf87d80cdc6
--- /dev/null
+++ b/marked/G/T-REC-G.7043-200407-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cf3f0102480653907c295ac678115d5576fbb30c343563f01411a8479e80b340
+size 40364
diff --git a/marked/G/T-REC-G.7043-200407-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.7043-200407-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30
--- /dev/null
+++ b/marked/G/T-REC-G.7043-200407-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359
+size 8245
diff --git a/marked/G/T-REC-G.7043-200407-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg b/marked/G/T-REC-G.7043-200407-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e2c50a8f6e82e270d042a229497662db5891f6e1
--- /dev/null
+++ b/marked/G/T-REC-G.7043-200407-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6867bad8b7510868b89b74ef75a9b540ffa88f06d4043188e35891bd25328f2d
+size 60826
diff --git a/marked/G/T-REC-G.7043-200407-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/G/T-REC-G.7043-200407-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e11fda54424954f1269d61d9e40bd03d0bc1f891
--- /dev/null
+++ b/marked/G/T-REC-G.7043-200407-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f0d63c6d42a029b2a55d8b8297df4034782796c5e8df738c39b26b87c25fd33c
+size 38937
diff --git a/marked/G/T-REC-G.7043-200407-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/marked/G/T-REC-G.7043-200407-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9db1603b526cc41c46b14b780e367e0ab6d5749e
--- /dev/null
+++ b/marked/G/T-REC-G.7043-200407-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b917a2df3b997bde5d46d710a682578cbcd6ca024f205990f5ed6cd5ac6a9284
+size 30590
diff --git a/marked/G/T-REC-G.7043-200407-I_PDF-E/raw.md b/marked/G/T-REC-G.7043-200407-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..cd685306b2e344623e853941422c4e7f5f7c0fe3
--- /dev/null
+++ b/marked/G/T-REC-G.7043-200407-I_PDF-E/raw.md
@@ -0,0 +1,443 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**G.7043/Y.1343**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(07/2004)
+
+SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
+DIGITAL SYSTEMS AND NETWORKS
+
+Digital terminal equipments – General
+
+SERIES Y: GLOBAL INFORMATION
+INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS
+AND NEXT GENERATION NETWORKS
+
+Internet protocol aspects – Transport
+
+---
+
+**Virtual concatenation of plesiochronous digital
+hierarchy (PDH) signals**
+
+ITU-T Recommendation G.7043/Y.1343
+
+---
+
+# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS**
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------|
+| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 |
+| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 |
+| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 |
+| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 |
+| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 |
+| TESTING EQUIPMENTS | G.500–G.599 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.600–G.699 |
+| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 |
+| DIGITAL NETWORKS | G.800–G.899 |
+| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 |
+| QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER-RELATED ASPECTS | G.1000–G.1999 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.6000–G.6999 |
+| DIGITAL TERMINAL EQUIPMENTS | G.7000–G.7999 |
+| General | G.7000–G.7099 |
+| Coding of analogue signals by pulse code modulation | G.7100–G.7199 |
+| Coding of analogue signals by methods other than PCM | G.7200–G.7299 |
+| Principal characteristics of primary multiplex equipment | G.7300–G.7399 |
+| Principal characteristics of second order multiplex equipment | G.7400–G.7499 |
+| Principal characteristics of higher order multiplex equipment | G.7500–G.7599 |
+| Principal characteristics of transcoder and digital multiplication equipment | G.7600–G.7699 |
+| Operations, administration and maintenance features of transmission equipment | G.7700–G.7799 |
+| Principal characteristics of multiplexing equipment for the synchronous digital hierarchy | G.7800–G.7899 |
+| Other terminal equipment | G.7900–G.7999 |
+| DIGITAL NETWORKS | G.8000–G.8999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## **ITU-T Recommendation G.7043/Y.1343**
+
+# **Virtual concatenation of plesiochronous digital hierarchy (PDH) signals**
+
+## **Summary**
+
+This Recommendation specifies the virtual concatenation of 1544, 2048, 34 368 and 44 736 kbit/s PDH signals. This Recommendation makes use of the frame structures defined in ITU-T Recs G.704 and G.832.
+
+## **Source**
+
+ITU-T Recommendation G.7043/Y.1343 was approved on 22 July 2004 by ITU-T Study Group 15 (2001-2004) under the ITU-T Recommendation A.8 procedure.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2004
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+# CONTENTS
+
+| | Page |
+|--------------------------------------------------------------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 4 Abbreviations..... | 1 |
+| 5 Conventions ..... | 2 |
+| 6 Specification of the virtually concatenated interfaces ..... | 2 |
+| 6.1 Interface at $N \times 1544$ kbit/s with virtual concatenation of a clear channel payload ..... | 2 |
+| 6.2 Interface at $N \times 2048$ kbit/s with virtual concatenation of a clear channel payload ..... | 4 |
+| 6.3 Interface at $N \times 34\,368$ kbit/s with virtual concatenation of a clear channel payload ..... | 5 |
+| 6.4 Interface at $N \times 44\,736$ kbit/s with virtual concatenation of a clear channel payload ..... | 7 |
+
+# Introduction
+
+The basic PDH signal frame structures for 1544, 2048 and 44 736 kbit/s signals are defined in ITU-T Rec. G.704 and the octet structured 34 368 kbit/s is defined in ITU-T Rec. G.832. This Recommendation enhances the functions of these frame structures to support the virtual concatenation of these frame structures to form larger transport entities (containers). Only frame structures of the same type can be virtually concatenated together. This virtual concatenation supports the Link Capacity Adjustment Scheme (LCAS) specified in ITU-T Rec. G.704/Y.1305.
+
+# Virtual concatenation of plesiochronous digital hierarchy (PDH) signals
+
+# 1 Scope
+
+This Recommendation enhances the frame structures of PDH signals of 1544, 2048 and 44 736 kbit/s, as defined in ITU-T Rec. G.704, and the octet structured 34 368 kbit/s, as defined in ITU-T Rec. G.832 to support virtual concatenation. Specifically, frame structures of the same type may be virtually concatenated together to form larger transport entities (containers). This virtual concatenation supports the Link Capacity Adjustment Scheme (LCAS) specified in ITU-T Rec. G.7042/Y.1305.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- ITU-T Recommendation G.702 (1988), *Digital hierarchy bit rates*.
+- ITU-T Recommendation G.704 (1998), *Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736 kbit/s hierarchical levels*.
+- ITU-T Recommendation G.707/Y.1322 (2003), *Network node interface for the synchronous digital hierarchy (SDH)*.
+- ITU-T Recommendation G.832 (1998), *Transport of SDH elements on PDH networks – Frame and multiplexing structures*.
+- ITU-T Recommendation G.7041/Y.1303 (2003), *Generic framing procedure (GFP)*.
+- ITU-T Recommendation G.7042/Y.1305 (2004), *Link capacity adjustment scheme (LCAS) for virtual concatenated signals*.
+- ITU-T Recommendation G.8040/Y.1340 (2004), *GFP frame mapping into plesiochronous digital hierarchy (PDH)*.
+
+# 3 Definitions
+
+This Recommendation defines the following term:
+
+- 3.1 nibble:** A group of four bits.
+
+# 4 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|------|----------------------------------------|
+| CTRL | Control field sent from source to sink |
+| DNU | Do Not Use |
+| EOS | End of Sequence |
+| GFP | Generic Framing Procedure |
+
+| | |
+|--------|--------------------------------------------|
+| GID | Group Identification |
+| LCAS | Link Capacity Adjustment Scheme |
+| MFI | MultiFrame Indicator |
+| MST | Member Status |
+| NORM | Normal Operating Mode |
+| PDH | Plesiochronous Digital Hierarchy |
+| RS-Ack | Re-sequence Acknowledge |
+| SQ | Sequence Indicator |
+| VCG | Virtual Concatenation Group |
+| VLI | Virtual concatenation and LCAS Information |
+
+# 5 Conventions
+
+The order of transmission of information in all the diagrams in this Recommendation is first from left to right and then from top to bottom. Within each byte or nibble the most significant bit is transmitted first. The most significant bit (bit 1) is illustrated at the left in all the diagrams.
+
+# 6 Specification of the virtually concatenated interfaces
+
+## 6.1 Interface at $N \times 1544$ kbit/s with virtual concatenation of a clear channel payload
+
+### 6.1.1 Frame and multiframe format
+
+The multiframe structure for the 24-frame multiframe as described in ITU-T Rec. G.704 shall be used. The first octet following the first framing bit of the multiframe is used to carry the concatenation overhead for each 1544 kbit/s signal, as illustrated in Figure 6-1. This octet is reserved for all values of $N$ ( $N = 1 \dots 16$ ).
+
+
+
+The diagram illustrates the structure of a multiframe consisting of 24 frames. The vertical axis is labeled 'Frame number' and lists frames 1 through 24, with vertical ellipses between frames 5 and 23. Each frame is represented by a horizontal bar. The first bit of each frame is labeled 'F' for framing. The first octet (8 bits) of each frame, immediately following the framing bit, is shaded with diagonal lines and labeled 'Concatenation overhead octet' with an arrow pointing to it. A horizontal double-headed arrow at the top indicates a duration of 125 μs for the entire multiframe. The diagram is labeled 'G.7043-Y.1343\_F6-1' in the bottom right corner.
+
+Diagram of frame structure showing concatenation overhead octet location.
+
+**Figure 6-1/G.7043/Y.1343 – Concatenation overhead location for the $N \times 1544$ kbit/s signal**
+
+### 6.1.2 Concatenation of $N$ 1544 kbit/s signals
+
+The concatenation overhead octet allows the virtual concatenation of $N$ 1544 kbit/s signals to form a single channel referred to as a virtual concatenation group (VCG). The payload container bandwidth of the resulting VCG is $N \times [1536 - (64/24)]$ kbit/s $\approx N \times 1533$ kbit/s. Client signals are mapped into the $N$ 1544 kbit/s signal members of the VCG on an octet-wise, round robin basis. The round robin sequence follows the ascending order of the per-member sequence numbers that are
+
+communicated in each member's concatenation overhead octet. For example, if a data packet's octet 1 is mapped into the 1544 kbit/s signal with sequence number 0, the next packet octet is mapped into the 1544 kbit/s signal with sequence number 1, etc. Up to sixteen 1544 kbit/s signals can be virtually concatenated into a single VCG.
+
+In general, the virtual concatenation and associated Link Capacity Adjustment Scheme (LCAS) functionality and definitions are the same as those specified for SDH virtual containers in ITU-T Rec. G.707/Y.1322. The areas in which they differ are specified in this Recommendation.
+
+#### 6.1.2.1 Concatenation overhead octet definition
+
+The concatenation overhead octet is time-multiplexed to carry the overhead required for virtual concatenation. This time multiplexing takes the form of a 16-nibble VLI that is transmitted one nibble per concatenation overhead octet. The concatenation overhead octet contains one nibble for the VLI and one nibble for the MFI1. The contents and format of the concatenation overhead octet and VLI are shown in Figure 6-2.
+
+| Concatenation overhead octet definition | | | | | | | |
+|-----------------------------------------|----------------|----------------|----------------|-------|-------|-------|-------|
+| Bit 1 | Bit 2 | Bit 3 | Bit 4 | Bit 5 | Bit 6 | Bit 7 | Bit 8 |
+| Control packet | | | | MFI1 | | | |
+| MST (bits 1-4) | | | | 1 | 0 | 0 | 0 |
+| MST (bits 5-8) | | | | 1 | 0 | 0 | 1 |
+| 0 | 0 | 0 | RS-ACK | 1 | 0 | 1 | 0 |
+| Reserved (0000) | | | | 1 | 0 | 1 | 1 |
+| Reserved (0000) | | | | 1 | 1 | 0 | 0 |
+| Reserved (0000) | | | | 1 | 1 | 0 | 1 |
+| Reserved (0000) | | | | 1 | 1 | 1 | 0 |
+| SQ bits 1-4 | | | | 1 | 1 | 1 | 1 |
+| MFI2 MSBs (bits 1-4) | | | | 0 | 0 | 0 | 0 |
+| MFI2 LSBs (bits 5-8) | | | | 0 | 0 | 0 | 1 |
+| CTRL | | | | 0 | 0 | 1 | 0 |
+| 0 | 0 | 0 | GID | 0 | 0 | 1 | 1 |
+| Reserved (0000) | | | | 0 | 1 | 0 | 0 |
+| Reserved (0000) | | | | 0 | 1 | 0 | 1 |
+| C 1 | C 2 | C 3 | C 4 | 0 | 1 | 1 | 0 |
+| C 5 | C 6 | C 7 | C 8 | 0 | 1 | 1 | 1 |
+
+**Figure 6-2/G.7043/Y.1343 – Virtual concatenation control packet format for $N \times 1544/2048$ kbit/s signals**
+
+The definitions of the fields within the control packet are given in ITU-T Rec. G.7042/Y.1305. MFI1 is the least significant four bits of the concatenation multiframe count and is incremented once per concatenation overhead octet with its LSB located in bit 8.
+
+The Cn bits are the CRC check over the control packet, with C1 being the MSB of the CRC. CRC generator polynomial is $x^8 + x^2 + x + 1$ , and the calculation method is specified in ITU-T Rec. G.7042/Y.1305.
+
+The member status (MST) information is time-multiplexed across multiple control packets as determined by the MFI2 LSB value. This time-sharing forms a member status multiframe that is specified in Figure 6-3.
+
+| MFI2 bit 8 (LSB) value | VLI octet | | | | Member numbers |
+|------------------------|-----------|-------|-------|-------|----------------|
+| | Bit 1 | Bit 2 | Bit 3 | Bit 4 | |
+| 0 | 0 | 1 | 2 | 3 | Member numbers |
+| | 4 | 5 | 6 | 7 | |
+| 1 | 8 | 9 | 10 | 11 | |
+| | 12 | 13 | 14 | 15 | |
+
+**Figure 6-3/G.7043/Y.1343 – Member status bit assignments for $N \times 1544/2048$ kbit/s signals**
+
+#### 6.1.2.2 Differential delay detection
+
+All $N$ 1544 kbit/s member signals that constitute a VCG are aligned at their transmission from the VCG source with respect to their 1544 kbit/s clock frequency, PDH signal frame and multiframe, MFI1 and MFI2. The VCG sink can determine the differential delay that the different members encountered in the network by comparing their respective MFI1 and MFI2 values, and performing the proper realignment. Note that the four MSBs of MFI2 are not used for differential delay compensation. The maximum differential delay that can be detected is $\pm(256)(24)(125\mu\text{s})/2 = \pm 384$ ms.
+
+## 6.2 Interface at $N \times 2048$ kbit/s with virtual concatenation of a clear channel payload
+
+### 6.2.1 Frame and multiframe format
+
+The basic frame and 16-frame multiframe structure at 2048 kbit/s as described in ITU-T Rec. G.704 shall be used. The time slot 1 of the first frame of the multiframe is used to carry the concatenation overhead for each 2048 kbit/s signal, as illustrated in Figure 6-4. This octet is reserved for all values of $N$ ( $N = 1 \dots 16$ ).
+
+
+
+The diagram illustrates a multiframe structure consisting of 16 frames, numbered 1 to 16 on the vertical axis labeled 'Frame number'. Each frame contains multiple time slots, with the first one labeled 'T.S.0'. In frame 1, the first 'T.S.0' is shaded and labeled 'Concatenation overhead octet' with an arrow pointing to it. A horizontal double-headed arrow above the entire structure indicates a duration of 125 μs. Vertical ellipsis dots between frame 5 and frame 15 indicate that the same pattern repeats for all 16 frames. The text 'G.7043-Y.1343\_F6-4' is located at the bottom right.
+
+Diagram showing the concatenation overhead location for the N x 2048 kbit/s signal. It displays a multiframe structure with 16 frames. Each frame contains time slots (T.S.0). The first time slot of the first frame is designated as the 'Concatenation overhead octet'. A horizontal double-headed arrow above the diagram indicates a duration of 125 μs.
+
+**Figure 6-4/G.7043/Y.1343 – Concatenation overhead location for the $N \times 2048$ kbit/s signal**
+
+### 6.2.2 Concatenation of $N$ 2048 kbit/s signals
+
+The concatenation overhead octet allows the virtual concatenation of $N$ 2048 kbit/s signals to form a single channel referred to as a virtual concatenation group. The payload container bandwidth of the resulting VCG is $N \times [1984 - (64/16)]$ kbit/s = $N \times 1980$ kbit/s. Client signals are mapped into the $N$ 2048 kbit/s signal members of the VCG on an octet-wise, round robin basis. The round robin sequence follows the ascending order of the per-member sequence numbers that are communicated in each member's concatenation overhead octet. For example, if a data packet's octet 1 is mapped into the 2048 kbit/s signal with sequence number 0, the next packet octet is mapped into the 2048 kbit/s signal with sequence number 1, etc. Up to sixteen 2048 kbit/s signals can be virtually concatenated into a single VCG.
+
+In general, the virtual concatenation and associated link capacity adjustment scheme functionality and definitions are the same as those specified for SDH virtual containers in ITU-T Rec. G.707/Y.1322. The areas in which they differ are specified in this Recommendation.
+
+#### 6.2.2.1 Concatenation overhead octet definition
+
+The concatenation octet definitions for the 2048 kbit/s signal are the same as those specified in 6.1.2.1.
+
+#### 6.2.2.2 Differential delay detection
+
+The differential delay compensation for the 2048 kbit/s signal is the same as specified in 6.1.2.2 except that the clock frequency is 2048 kbit/s. Note that the four MSBs of MFI2 are not used for differential delay compensation. The maximum differential delay that can be detected is $\pm(256)(16)(125\mu\text{s})/2 = \pm 256 \text{ ms}$ .
+
+## 6.3 Interface at $N \times 34\,368 \text{ kbit/s}$ with virtual concatenation of a clear channel payload
+
+### 6.3.1 Frame and multiframe format
+
+The multiframe structure for the 24-frame multiframe as described in ITU-T Rec. G.832 shall be used with the addition of a concatenation overhead byte. Specifically, the first octet following the FA2 byte is used to carry the concatenation overhead for each 34 368 kbit/s signal, as illustrated in Figure 6-5. This octet is reserved for all values of $N$ ( $N = 1 \dots 8$ ).
+
+
+
+The diagram illustrates the frame structure for the $N \times 34\,368 \text{ kbit/s}$ signal. The frame is 59 columns wide and 9 rows high. The first column contains overhead bytes: FA1, EM, TR, MA, NR, and GC. The second column contains FA2. The third column contains the Concatenation overhead (VLI). The remaining 56 columns (columns 4 to 59) contain the 529 octet payload. The diagram is labeled G.7043-Y.1343\_F6-5.
+
+Diagram of a frame structure for the N x 34 368 kbit/s signal. The frame is 59 columns wide and 9 rows high. The first column contains overhead bytes: FA1, EM, TR, MA, NR, and GC. The second column contains FA2. The third column contains the Concatenation overhead (VLI). The remaining 56 columns (columns 4 to 59) contain the 529 octet payload. The diagram is labeled G.7043-Y.1343\_F6-5.
+
+Figure 6-5/G.7043/Y.1343 – Concatenation overhead location for the $N \times 34\,368 \text{ kbit/s}$ signal
+
+### 6.3.2 Concatenation of $N$ 34 368 kbit/s signals
+
+The concatenation overhead octet allows the virtual concatenation of $N$ 34 368 kbit/s signals to form a single channel referred to as a virtual concatenation group. The payload container bandwidth of the resulting VCG is $N \times [(529/537) \times 34\,368] \text{ kbit/s} \approx N \times 33\,856 \text{ kbit/s}$ . Client signals are mapped into the $N$ 34 368 kbit/s signal members of the VCG on an octet-wise, round robin basis. The round robin sequence follows the ascending order of the per-member sequence numbers that are communicated in each member's concatenation overhead octet. For example, if data packet's octet 1 is mapped into the 34 368 kbit/s signal with sequence number 0, the next packet octet is mapped into the 34 368 kbit/s signal with sequence number 1, etc. Up to eight 34 368 kbit/s signals can be virtually concatenated into a single VCG.
+
+In general, the virtual concatenation and associated link capacity adjustment scheme functionality and definitions are the same as those specified for SDH virtual containers in ITU-T Rec. G.707/Y.1322. The areas in which they differ are specified in this Recommendation.
+
+#### 6.3.2.1 Concatenation overhead octet definition
+
+The concatenation overhead octet is time-multiplexed to carry the overhead required for virtual concatenation. This time multiplexing takes the form of a 16-nibble VLI that is transmitted one nibble per control octet. The control octet contains one nibble for the VLI and one nibble for the MFI1. The contents and format of the concatenation overhead octet and VLI are shown in Figure 6-6.
+
+| Concatenation overhead octet definition | | | | | | | | | | |
+|-----------------------------------------|----------------|----------------|----------------|-------|-------|-------|-------|--|--|--|
+| Bit 1 | Bit 2 | Bit 3 | Bit 4 | Bit 5 | Bit 6 | Bit 7 | Bit 8 | | | |
+| Control packet | | | | MFI1 | | | | | | |
+| MST (bits 1-4) | | | | 1 | 0 | 0 | 0 | | | |
+| MST (bits 5-8) | | | | 1 | 0 | 0 | 1 | | | |
+| 0 | 0 | 0 | RS-ACK | 1 | 0 | 1 | 0 | | | |
+| Reserved (0000) | | | | 1 | 0 | 1 | 1 | | | |
+| Reserved (0000) | | | | 1 | 1 | 0 | 0 | | | |
+| Reserved (0000) | | | | 1 | 1 | 0 | 1 | | | |
+| Reserved (0000) | | | | 1 | 1 | 1 | 0 | | | |
+| 0 | SQ bits 1-3 | | | 1 | 1 | 1 | 1 | | | |
+| MFI2 MSBs (bits 1-4) | | | | 0 | 0 | 0 | 0 | | | |
+| MFI2 LSBs (bits 5-8) | | | | 0 | 0 | 0 | 1 | | | |
+| CTRL | | | | 0 | 0 | 1 | 0 | | | |
+| 0 | 0 | 0 | GID | 0 | 0 | 1 | 1 | | | |
+| Reserved (0000) | | | | 0 | 1 | 0 | 0 | | | |
+| Reserved (0000) | | | | 0 | 1 | 0 | 1 | | | |
+| C 1 | C 2 | C 3 | C 4 | 0 | 1 | 1 | 0 | | | |
+| C 5 | C 6 | C 7 | C 8 | 0 | 1 | 1 | 1 | | | |
+
+**Figure 6-6/G.7043/Y.1343 – Virtual concatenation control packet format for $N \times 34\ 368$ and $N \times 44\ 736$ kbit/s signals**
+
+The definitions of the fields within the control packet are given in ITU-T Rec. G.7042/Y.1305.
+
+MFI1 is the least significant four bits of the concatenation multiframe count and is incremented once per concatenation overhead octet with its LSB located in bit 8. MFI2 is the most significant eight bits of the 12-bit concatenation frame count.
+
+The Cn bits are the CRC check over the control packet, with C1 being the MSB of the CRC. CRC generator polynomial is $x^8 + x^2 + x + 1$ , and the calculation method is specified in ITU-T Rec. G.7042/Y.1305.
+
+The member status information is carried in each control packet as specified in Figure 6-7.
+
+| Frame number (MFI1) | VLI octet | | | | Member numbers |
+|---------------------|-----------|-------|-------|-------|----------------|
+| | Bit 1 | Bit 2 | Bit 3 | Bit 4 | |
+| 0 | 0 | 1 | 2 | 3 | Member numbers |
+| 1 | 4 | 5 | 6 | 7 | |
+
+**Figure 6-7/G.7043/Y.1343 – Member status bit assignments for $N \times 34\ 368$ and $N \times 44\ 736$ kbit/s signals**
+
+#### 6.3.2.2 Differential delay detection
+
+All $N$ 34 368 kbit/s member signals that constitute a VCG are aligned at their transmission from the VCG source with respect to their 34 368 kbit/s clock frequency, PDH signal frame and multiframe, MFI1 and MFI2. The VCG sink can determine the differential delay that the different members encountered in the network by comparing their respective MFI1 and MFI2 values, and performing the proper realignment. The maximum differential delay that can be detected is $\pm[(536)(8)(2^{12})]/2/34368000 = \pm 255$ ms.
+
+## 6.4 Interface at $N \times 44\ 736$ kbit/s with virtual concatenation of a clear channel payload
+
+### 6.4.1 Multiframe format for $N \times 44\ 736$ kbit/s
+
+The multiframe structure for 44 736 kbit/s signal described in ITU-T Rec. G.704 shall be used. For the case of an $N \times 44\ 736$ kbit/s signal, the first octet (two nibbles) following the first framing bit (X1) of the multiframe is used to carry the concatenation overhead in each constituent 44 736 kbit/s signal, as illustrated in Figure 6-8. This octet is reserved for all values of $N$ ( $N = 1 \dots 8$ ).
+
+
+
+Figure 6-8: 44 736 kbit/s signal multiframe with reserved concatenation overhead octet for N x 44 736 kbit/s mappings. The diagram shows a 680-bit subframe structure. The first octet (X1) is the concatenation overhead octet. The remaining 679 bits are divided into 84 bits of payload and 595 bits of overhead. The overhead is organized into 7 subframes (master-frame), each containing 85 bits. The payload is organized into 84 bits, which are divided into 10.5 nibbles. The diagram shows the mapping of these nibbles into the 84 bits of the payload. The mapping is as follows: X1 (concatenation overhead octet) is followed by F1, C11, F2, C12, F3, C13, F4, X2, F1, C21, F2, C22, F3, C23, F4, P1, F1, C31, F2, C32, F3, C33, F4, P2, F1, C41, F2, C42, F3, C43, F4, M1, F1, C51, F2, C52, F3, C53, F4, M2, F1, C61, F2, C62, F3, C63, F4, M3, F1, C71, F2, C72, F3, C73, F4. The 84 bits of payload are divided into 10.5 nibbles, which are mapped into the 84 bits of the payload. The mapping is as follows: the first nibble is mapped into the first bit of the first payload octet, the second nibble is mapped into the second bit of the first payload octet, and so on, until the 10.5 nibbles are mapped into the 84 bits of the payload.
+
+Figure 6-8/G.7043/Y.1343 – 44 736 kbit/s signal multiframe with reserved concatenation overhead octet for $N \times 44\ 736$ kbit/s mappings
+
+### 6.4.2 Concatenation of $N$ 44 736 kbit/s signals
+
+The concatenation overhead octet allows the virtual concatenation of $N$ 44 736 kbit/s signals to form a single channel referred to as a virtual concatenation group. The payload container bandwidth of the resulting VCG is $N \times (44\ 736)[(7)(680 - 8) - 8]/[(7)(680)]$ kbit/s $\approx N \times 44\ 134$ kbit/s. Client data signals are mapped into the $N$ 44 736 kbit/s signal members of the VCG on a nibble-wise, round robin basis. The round robin sequence follows the ascending order of the per-member sequence numbers that are communicated in each member's concatenation overhead octet. For example, if the most significant nibble of GFP frame octet 1 is mapped into the 44 736 kbit/s signal with sequence number 0, the least significant nibble of GFP frame octet 1 is mapped into the 44 736 kbit/s signal with sequence number 1, the most significant nibble of GFP frame octet 2 is mapped into the 44 736 kbit/s signal with sequence number 2, etc. Up to eight 44 736 kbit/s signals can be virtually concatenated into a single VCG.
+
+The virtual concatenation and associated link capacity adjustment scheme functionality and definitions are the same as those specified for SDH virtual containers in ITU-T Rec. G.707/Y.1322.
+
+#### 6.4.2.1 Concatenation overhead octet definition
+
+The concatenation overhead octet is time-multiplexed to carry the overhead required for virtual concatenation. This time multiplexing takes the form of consecutive 16-octet control packets. The contents and format of the control packets are shown in Figure 6-6.
+
+The definitions of the fields within the control packet are given in ITU-T Rec. G.7042/Y.1305. MFI1 is the least significant four bits of the concatenation multiframe count and is incremented once per concatenation overhead octet with its LSB located in bit 8. MFI2 is the most significant eight bits of the 12-bit concatenation frame count.
+
+The $C_n$ bits are the CRC check over the control packet, with $C_1$ being the MSB of the CRC. CRC generator polynomial is $x^8 + x^2 + x + 1$ , and the calculation method is specified in ITU-T Rec. G.7042/Y.1305.
+
+The member status information is carried in each control packet as specified in Figure 6-7.
+
+#### **6.4.2.2 Differential delay detection**
+
+All $N$ 44 736 kbit/s member signals that constitute a VCG are aligned at their transmission from the VCG source with respect to their 44 736 kbit/s clock frequency, signal frame and multiframe, and their MFI1 and MFI2 frame count values. The VCG sink can determine the differential delay that the different members encountered in the network by comparing their respective MFI1 and MFI2 values, and performing the proper realignment. The maximum differential delay that can be detected is $\pm[(7)(680)(2^{12})]/2/44736000 = \pm 217$ ms.
+
+# ITU-T Y-SERIES RECOMMENDATIONS
+
+# GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT GENERATION NETWORKS
+
+| | |
+|--------------------------------------------------------------------|----------------------|
+| GLOBAL INFORMATION INFRASTRUCTURE | |
+| General | Y.100–Y.199 |
+| Services, applications and middleware | Y.200–Y.299 |
+| Network aspects | Y.300–Y.399 |
+| Interfaces and protocols | Y.400–Y.499 |
+| Numbering, addressing and naming | Y.500–Y.599 |
+| Operation, administration and maintenance | Y.600–Y.699 |
+| Security | Y.700–Y.799 |
+| Performances | Y.800–Y.899 |
+| INTERNET PROTOCOL ASPECTS | |
+| General | Y.1000–Y.1099 |
+| Services and applications | Y.1100–Y.1199 |
+| Architecture, access, network capabilities and resource management | Y.1200–Y.1299 |
+| Transport | Y.1300–Y.1399 |
+| Interworking | Y.1400–Y.1499 |
+| Quality of service and network performance | Y.1500–Y.1599 |
+| Signalling | Y.1600–Y.1699 |
+| Operation, administration and maintenance | Y.1700–Y.1799 |
+| Charging | Y.1800–Y.1899 |
+| NEXT GENERATION NETWORKS | |
+| Frameworks and functional architecture models | Y.2000–Y.2099 |
+| Quality of Service and performance | Y.2100–Y.2199 |
+| Service aspects: Service capabilities and service architecture | Y.2200–Y.2249 |
+| Service aspects: Interoperability of services and networks in NGN | Y.2250–Y.2299 |
+| Numbering, naming and addressing | Y.2300–Y.2399 |
+| Network management | Y.2400–Y.2499 |
+| Network control architectures and protocols | Y.2500–Y.2599 |
+| Security | Y.2700–Y.2799 |
+| Generalized mobility | Y.2800–Y.2899 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure, Internet protocol aspects and Next Generation Networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/05b0f658f02a1301691b547d089c485a_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/05b0f658f02a1301691b547d089c485a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c12754b4d7b5d2b337cdc41c703fe3aa744057b8
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/05b0f658f02a1301691b547d089c485a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:46e96c8c8e628a626d80a17a7ba64bcdb2e0714640336859119e64956efbaa93
+size 46052
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/060648daa95345c57f019fc00ad75993_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/060648daa95345c57f019fc00ad75993_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b879b29ced78ba75c5c1ae4d37f1f0cfe3e390e7
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/060648daa95345c57f019fc00ad75993_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:544aa6d6ea7010452ce1160f4f9f267cffd73a54e8d137d59c853ff66d2cfe18
+size 31243
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/0b452c5334567cbdc22ee9817e1246f5_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/0b452c5334567cbdc22ee9817e1246f5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fb85910738fc659bd8e1f492675cb14b3ff3d0d1
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/0b452c5334567cbdc22ee9817e1246f5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d79487f2cc1fc0b034a5d869c4f044b0d18ae1ceaa0cd5c1fae2b2127418f247
+size 35443
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/0eb57eefa7cd45d30e68829ca8a03843_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/0eb57eefa7cd45d30e68829ca8a03843_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..91cf34bbb5d8f5490e8c00578a069b4172eb7f44
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/0eb57eefa7cd45d30e68829ca8a03843_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f917ca3b0d9542730bc9c96d2f713e1b489a88edc8700240b15cbb55386680ca
+size 36503
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8a374d4ff619c91ef4990abe588f790255fb8c85
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:29b941a295ce333c695cbbdaa41a549c20ecf830983f2efde7a62a523bd9e350
+size 37819
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/130e5cca4d4856272e57a0247d14e094_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/130e5cca4d4856272e57a0247d14e094_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..97745de241990d7225f8e72ca7cf8968ef732f03
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/130e5cca4d4856272e57a0247d14e094_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:116d0b7d3e636a7a11349669d19175d3899b410970ff3ae74c76afdf1d4efb01
+size 200255
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c61b153afc9ab8a854b3eb755d2ab44c7776f54c
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:362e259b7e217f65ee1d10977b2eeded80b5cf26f71005d5cb89bd70609b7a80
+size 141734
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fd2a626624f23ee9b7b11cff42feb4ab7ef673ba
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:37ac4508c069147a81e61ad0c84d54eea9a1aefc80055e0485a630cc60edc13e
+size 115142
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/1594605eb94cd26a95fcfdb0b8af86ca_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/1594605eb94cd26a95fcfdb0b8af86ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..91c2660397bcda74023f509049fe657c55fdc515
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/1594605eb94cd26a95fcfdb0b8af86ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5013906077172f27bd15aad33d16d45f906c5325ecc1f7a036087896fd5321c5
+size 41161
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/18b914bd6d55df64c6935e65803a3f79_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/18b914bd6d55df64c6935e65803a3f79_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eb1b89ac99fb7aa0cd5523ab56d0ed93a194ab41
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/18b914bd6d55df64c6935e65803a3f79_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6f4d10f853474fe72bcc6826aab2b830f48d07d803bc5787bd3d3dff9fed8198
+size 178057
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/1ddf3a99e7935a2f5f85e7f7e038e2fa_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/1ddf3a99e7935a2f5f85e7f7e038e2fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..18a07f3a9dcdc4790779da38ab72b7bcd708bde3
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/1ddf3a99e7935a2f5f85e7f7e038e2fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d36c7c557e414f11615e8e90387fbdec7c2a2d06f92e239d71321db97c379179
+size 94128
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/1eb72b1e2fe3920b483f6245e5d477e8_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/1eb72b1e2fe3920b483f6245e5d477e8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..06d998f3a1d3a737bf9447f0fb51d7c6464a9ded
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/1eb72b1e2fe3920b483f6245e5d477e8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8927a03096802d3ee58cf4a28677a3473cfb343c8a92c82f975bc7e4fa5787ea
+size 142309
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/207817524fe964425718e1723d5b7d9e_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/207817524fe964425718e1723d5b7d9e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..990cb51cb757425be2803ef0f12c85898610ccc3
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/207817524fe964425718e1723d5b7d9e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8df86513bddeb02032b78da73f5923ccb968b0e2198693141289e27f2c476e60
+size 28938
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/20c9f09356fc57958b8bfda4a1c84e90_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/20c9f09356fc57958b8bfda4a1c84e90_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9a1e362431ab2db00e1934bd1beb53fc9b31f36e
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/20c9f09356fc57958b8bfda4a1c84e90_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:996990057cc38ac074d15876ef819f5c393be8167bd6bbc7656c066eca663a90
+size 76494
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/21ef9d902c520892c25ad348622b2f04_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/21ef9d902c520892c25ad348622b2f04_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..05e20c1f0f05f0433f8f5168e86853e1a4aae123
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/21ef9d902c520892c25ad348622b2f04_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:adcf9a52a4d503f345d7376100bc7781e3a67c59ef8db9401fb23b55bb45260a
+size 34576
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/26d6d8d333f84acff82b7a9f9b303da6_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/26d6d8d333f84acff82b7a9f9b303da6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..13ccc63d71c8de5e17262f83bd4a441e567389be
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/26d6d8d333f84acff82b7a9f9b303da6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f8a9035188750ab1727c3567464cfe4cc37606b41a1acba7e6f71acd24bacdd6
+size 28395
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/27788c2a26d9641e68232a4eff1299b9_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/27788c2a26d9641e68232a4eff1299b9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..89ae45b2b6bfcf03cb4101cacc7a3ae973094f87
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/27788c2a26d9641e68232a4eff1299b9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d6edf36864a8b4ae2dc3102856ed812abcbf5ae3242c560878d3b1d42c4580d
+size 100429
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/27d6042f4bce01ea5789efbd9e8d1f50_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/27d6042f4bce01ea5789efbd9e8d1f50_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dada013f40b9b12be1fb827cd76ce7f00a798df2
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/27d6042f4bce01ea5789efbd9e8d1f50_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1448661fd9e6b9cfc7f31a119293e6f8e373344c152c4880841a48aad9f8e04d
+size 37650
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/28085f681b9fff76a53c5b8b32338ee1_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/28085f681b9fff76a53c5b8b32338ee1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e4c324bbfb7632f68c219f02d60f0d6eb49f4086
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/28085f681b9fff76a53c5b8b32338ee1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bc28d2964905996a2f257d9b1b591e9759eae3aa23ce72190c9c11bef4072276
+size 81911
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/2876be3592c7b4878400b85f209b2b6a_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/2876be3592c7b4878400b85f209b2b6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ed473626de5ee1c7e49c569e99fd80548e8573c7
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/2876be3592c7b4878400b85f209b2b6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d4c26f808fc29b0d298e7dbea15b175c6eba6334816757fd167ef19c5c368f49
+size 18400
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/2e83263cd91cb4bcdc0ad2973f715412_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/2e83263cd91cb4bcdc0ad2973f715412_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..63c6ebb99d10da1efb39258e9780196bbea05167
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/2e83263cd91cb4bcdc0ad2973f715412_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:245adedef65d193c3a496d18aa57df500629779b95ec0ae691c2b2701708b39e
+size 33240
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..37d250d5a2dfd63abaae541351fe3059ffbf57a9
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0321ead15d4b8032cd30e4fc7728bdb1dee3505cb7e0913318f6236060c1e4c8
+size 122256
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/3349dc82c6333221b0610be6ee7250b6_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/3349dc82c6333221b0610be6ee7250b6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cb9d559755506eb370949afdd7c07574d7568aba
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/3349dc82c6333221b0610be6ee7250b6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d4d2f0c8e841b1acd07b28abe89fd017407f28153204897ec32792c99a48226b
+size 38235
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/3481cde1adf61b0452dd6489dada6d6a_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/3481cde1adf61b0452dd6489dada6d6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..24982da3d1404beae2e3bfc6457afbf2f4200628
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/3481cde1adf61b0452dd6489dada6d6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:18cd02e1250c692b016e1c6bf9153bdd6352462dc8984b23e29220a23ae0a556
+size 42078
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/3766b291e69420b0437ae278b057b5ee_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/3766b291e69420b0437ae278b057b5ee_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..01fa91c5a5f6623c4b8dff6e321db77c74fc5071
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/3766b291e69420b0437ae278b057b5ee_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1e75e9071ad03ebe9191d9d71166e916ed7697899aadbdadc3a1197282a4b1f7
+size 100541
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/387a316ca4f909a5260b0c5e232d5cc8_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/387a316ca4f909a5260b0c5e232d5cc8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d9538ad08238c5054e225e195ff4c9f036bcdf23
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/387a316ca4f909a5260b0c5e232d5cc8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f27a0f4b343c8881973aca7a5fdc5fe3c3e86e3b32f5f6c764b0243bef739e3c
+size 27706
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4460ddeda28ba1273079d3039403828e8979a2a0
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e91ae6df9cefbc242499fdc2f014fa66f40caa3d520a475dabb9781a3b2e79ba
+size 147812
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/3c99312f83459559d9a301148555d7b9_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/3c99312f83459559d9a301148555d7b9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ee46bfca52fdf53369f8b1a9ac2c76037c15d1cb
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/3c99312f83459559d9a301148555d7b9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8d92aa5864be4af96d4bc546ba07efb115fc0a31bd787975edc9aa8e1121dd53
+size 61689
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/3ce04f1c7128814978c6b34d654a25cc_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/3ce04f1c7128814978c6b34d654a25cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d2124fcf75545cf1b8962f07c6ff4aefc2e80d82
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/3ce04f1c7128814978c6b34d654a25cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:239dbb2ac88ca6e737d22aba3c0883eca0bc5ed9941359f330d17c97cb7379f8
+size 72339
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/43437211ce989e9da795fecc0d499c05_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/43437211ce989e9da795fecc0d499c05_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..11e277a8d3d39630935177d2b3502b2cc1a68db1
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/43437211ce989e9da795fecc0d499c05_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dac1e1b7469af19ab78cf8f31ed15a91dbe53b77f7cfe1b99f723b212ae46bdc
+size 82906
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/49d7bfbc65a92a7e1bd61777326a212d_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/49d7bfbc65a92a7e1bd61777326a212d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a2ff4932b8bbfca43c05dc058f1d6273014081cb
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/49d7bfbc65a92a7e1bd61777326a212d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b73baf441a27811fb2dec2f0ece6e98d4a9341048dc475ba6861b573bc3a082f
+size 36493
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/4c4d1f9c0946faff8f5432a60c4c3f94_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/4c4d1f9c0946faff8f5432a60c4c3f94_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..94da99fee9dcf5d2d73b01fe18ea64257ae99a4d
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/4c4d1f9c0946faff8f5432a60c4c3f94_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fed88d4cd2f0efaeef1a16d04ac482426884f12486182708b11a4144462126fc
+size 53447
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/4f148853ae68fdcf5e43f7604cab457d_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/4f148853ae68fdcf5e43f7604cab457d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1935bfdb319e72329fbee73bca7a4afccbcad0e6
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/4f148853ae68fdcf5e43f7604cab457d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:963c14521941d4cf5b4cf620bf86b0307f6868307cc9788659785428c3585057
+size 54341
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/52ed951cbf3a5e682e913881bc0d13c5_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/52ed951cbf3a5e682e913881bc0d13c5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c78909221f8c3a2999ba346c925b2415d796d5c2
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/52ed951cbf3a5e682e913881bc0d13c5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7156935600ddf6bfe3eeeb8df06a2b85a7f682135703c94047a0e22b1c77eee2
+size 25953
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/54ef4ea5d6908b45fab8d81e656ca970_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/54ef4ea5d6908b45fab8d81e656ca970_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..58a34ecd9112b6dd2419ea99f2592ee2285366b7
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/54ef4ea5d6908b45fab8d81e656ca970_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:57293f9d6a43f68b1104b39a57120cb985d7b5895c97d08278a669965b8a45ae
+size 62712
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/55a415876cf7b7c2509c0318bb857efa_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/55a415876cf7b7c2509c0318bb857efa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..658877d38513a2f0963b51fdd36bc66bcd480929
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/55a415876cf7b7c2509c0318bb857efa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ed8525c71338cf6120331488c01c8fa124421bb36421ef9b932fe67e49effdf2
+size 25874
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..90640d8be7810be758eb7a63e6e0cb68218dbc3b
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d5a73bdeb4f38298bdf059adae3ffc103baf7ae776e17a525fff30869da0e4e7
+size 56595
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/572cf014db14c8234f91c07d5a5a28c6_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/572cf014db14c8234f91c07d5a5a28c6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7361f17ed33b87cb4980be79aa58c6db47c85479
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/572cf014db14c8234f91c07d5a5a28c6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71139b7ca8a06e7b7e676797d49ad3214282e3b197c68ac51971c21fb4094da6
+size 23582
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0f511dde2ce76830c12aea57373d50192a5309d3
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dc8d886a4c5d1452b861f2f46e0519b0f2676c3379e87cff8ebf74e43626682b
+size 7119
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/5ec3284657e4df0df3653dd61d0ecd13_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/5ec3284657e4df0df3653dd61d0ecd13_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9c6a9371dc9c1688b4965d6250a5e64d41602570
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/5ec3284657e4df0df3653dd61d0ecd13_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5c885cddc9a52ee8ef33db1f9ddbab286c44eb2ec3bda5334a801f00ffdb9b10
+size 63520
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/64c2e4d0fd8137f0740be6ec148b3ce2_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/64c2e4d0fd8137f0740be6ec148b3ce2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3bb735ce6d3eaa0fe43cf996595fa459b32a1425
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/64c2e4d0fd8137f0740be6ec148b3ce2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:42eab9dfc45dbada3cd8f5557e5f7881768a0488ab5647369bbcb0c330b2ab19
+size 121893
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/669c88c4149a2add62ce1cbc7e8bb659_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/669c88c4149a2add62ce1cbc7e8bb659_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36f77316a1006225a1917303e625fed2ebba4887
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/669c88c4149a2add62ce1cbc7e8bb659_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e73a3c2019fa145b2b671a1bf66b988f25b01ab795dcd8bf4c03b1a46f89320
+size 216398
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/6834375fe386f94a73387a3e15eb8837_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/6834375fe386f94a73387a3e15eb8837_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..24cba5cab6729727f3674bad8247fdbb0d63a539
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/6834375fe386f94a73387a3e15eb8837_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2693a64407be15e05b1f6c163707560f031afa229c344952f3aff8d92024ed98
+size 86599
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8ca9d5d06219c60aaae318c36802ef3477dc0ac2
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:83741def74ce286d342cbe11257e3a7664c5fb28f40f585951006efdf3083cdf
+size 23704
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d8c31059b4fd966a2625688131b55303d4fd0599
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7fad89b31f433015bd5e15b6aeca6157999e55956cb030fbd04e20ce1c37eebf
+size 36205
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/6d697ce8828ba75fddee0a1b7767a7ca_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/6d697ce8828ba75fddee0a1b7767a7ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..74da97ee9e014e878d4c2bb1c2125777cd95afdf
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/6d697ce8828ba75fddee0a1b7767a7ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:806d32479483bde2f78770c3d1648584644598071079a382f788ac410e8b81bc
+size 35106
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c640744c43bf67ca4d5e0660a323e50f1c9fcab2
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7df27608f6badb35efee83a859b458a236eefd2b581f14336183bb0a5d8ce599
+size 80470
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..57a3cec51cc0a5215750908b8c4f9f7d9b5ddf83
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0e06c3b5666e245969ed42a90af2c3b988633801234e808923b2b27430cfd40d
+size 13158
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c38656bc27caf832c06c63a77e57ea542aa040ac
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c033a978287dfb2781d49b693d168dc97abf383c754d7c3c35c4cf3b36f4c5a1
+size 110434
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/77464a47f104d0d647b2414591137b64_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/77464a47f104d0d647b2414591137b64_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36999d4ab70746a0466dae26262cd8682dec8deb
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/77464a47f104d0d647b2414591137b64_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71eca3f3017f4cfb7d267e8cc62cd24aa3b0453fc6ee9d38d23391f3a84760af
+size 51407
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/77a781dfb114c3e2b399f876f1808cfd_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/77a781dfb114c3e2b399f876f1808cfd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ac4769977d6ef37725bdeec3c62af03ead5991bb
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/77a781dfb114c3e2b399f876f1808cfd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c581d5d636aa58faddb3332c688516d5c4e059e533202a084f6a2790df7f6de7
+size 91790
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/7818b1bd115c04ee738bcf90f51d945b_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/7818b1bd115c04ee738bcf90f51d945b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..94bb9a6a306521f6dffa40b386ba2e49a4a3ea97
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/7818b1bd115c04ee738bcf90f51d945b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3ea8aa624b094a555affce1b18a5e38b7f2e7a72e2284c324ae08e9e50af0aa3
+size 37415
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/7f7211748473542096717109ebe5a9d6_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/7f7211748473542096717109ebe5a9d6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d157f5401950a85391a82aa144d8f56fc6c301ce
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/7f7211748473542096717109ebe5a9d6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9a91b7cfbf6b81b5881fb010511f891a9e5113f23ee930d29e1e17ebf16e9147
+size 63045
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/85e2327652d513a7fee8fdbf97ad06f1_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/85e2327652d513a7fee8fdbf97ad06f1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2dd29d2ae1182f85c2ed4807ef8d9ab16212ce96
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/85e2327652d513a7fee8fdbf97ad06f1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7700f534a62ae3b5b26895daf3dd53df8edbce817f4be493d883fbbfbc4fb924
+size 119802
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/892c6816711b2d83080366cf799d2c62_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/892c6816711b2d83080366cf799d2c62_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dcbd64835e47d9535c8b0bebf96dc1fd9bc4b8a8
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/892c6816711b2d83080366cf799d2c62_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b2d0edad4a7316bd2719efcf306f1b2e7b4d5322b96010d6c68ed79bb2ebfba
+size 115843
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/8c3eb53c927f55acd19723cfcd0c43b6_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/8c3eb53c927f55acd19723cfcd0c43b6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e8f4bcdefbd70ecf7cc2369b23864c3dbb4b6bed
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/8c3eb53c927f55acd19723cfcd0c43b6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c26f5070bd505c769311ba6333bcd288c1e2afaee15453877eac72ccab6a8f18
+size 125623
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5dba83ea940d1c1ad1c145234c0c1112bf9fde27
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fbc02dcc23cb1dd2f8648058fe65ade47c8eeae301fb4425be2abdf0893829d0
+size 123361
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/94796d524bd7e0f31f89a379bae95996_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/94796d524bd7e0f31f89a379bae95996_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dfa074ef0411ceca5cdf2edef4580aeaa1c4cbf5
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/94796d524bd7e0f31f89a379bae95996_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:87d9dc2f12180430d0e1a4719c293408b138931f2258249abc5c40a37457b9b0
+size 137084
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f636cc1c213077f86020f3338569701605e1dfa3
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf4deb4afcc9a41504aecb7ddd35a24b6ba5d9ceaad9b6859d58104bd0536198
+size 73301
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d625ada2d76014e24b0eaa6675901a7eb6ec05c3
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b31bb29a12e3ca2b60f7580905862bb5f8c5bf244590350e9f1d605143af74a8
+size 20794
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..42d9d6ad560e1e1af0963a7f81485d968f95b438
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7e7d2c1af06b0c5726e10b6eb1b7d4ebd9ca4604e68aee3dd1188848fd6affab
+size 24208
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/9faa3512b2ff7973283e76192e91bf65_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/9faa3512b2ff7973283e76192e91bf65_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8487cf39b8a127500ae04901e1590c206ad3ea33
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/9faa3512b2ff7973283e76192e91bf65_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f12f3098e5a728d4a17accd00686e48b4b6cc179f89f98148678c4f446ae6fcb
+size 58004
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/a0fdaf0b566e05f53f0085cf41e2dbad_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/a0fdaf0b566e05f53f0085cf41e2dbad_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..24a4342674466ebe75265501e816b22e0834c22c
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/a0fdaf0b566e05f53f0085cf41e2dbad_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7baf648fef747955dea7e5aacfdcc40a6fa398b27cbd2810559d6b232f02c03e
+size 151705
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/a52d0eb8feb4ddf21fec03f9f175e9d1_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/a52d0eb8feb4ddf21fec03f9f175e9d1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9aa31a1374b85890555712f32bc979e84ae6d89f
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/a52d0eb8feb4ddf21fec03f9f175e9d1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f5c4e2e4e5f5c794cfc6aca950ce4e8782c7c9e003f53ce5d9e492253f27ae0e
+size 144735
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/a72d02d4e6305689a79b46d36739cd51_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/a72d02d4e6305689a79b46d36739cd51_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..09ae117c8f9ed08bf1e2968c4c74e469e84d13ad
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/a72d02d4e6305689a79b46d36739cd51_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2c7f107faa15722b2b9bec50f024d77d784867dd10047d7c7ff57e23be6c00ad
+size 147727
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..51f8bd6f0b0b8c392c7fdddf78609c2d481e27c2
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/a734898ce18e972938949637c32a34f4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:89c061a8d189e2ba040f867e6ba090e2165f26843391fa569514005be0adbd6c
+size 79279
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/a7450c80e88ad3f6ca1427ad84020998_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/a7450c80e88ad3f6ca1427ad84020998_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3e0c4b2e5fb384cfdca900e6d301318a78f1e711
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/a7450c80e88ad3f6ca1427ad84020998_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9ab798edb3b45ac706f016d1077346c341cbaac8a7f8de792eb81db0b998a61c
+size 34673
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f467124041f1fb4368cc786a25bf9769d009f5a6
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a1833cd662804ffe00328ef990315a8f636b4955ba6fbe302a7cd594fa20d451
+size 35519
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/af4f213abb5ad1891a43425e0d758021_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/af4f213abb5ad1891a43425e0d758021_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fd27f5b02a280447c2db660881857bb786c33925
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/af4f213abb5ad1891a43425e0d758021_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bb7b3de96bda2a09ca3b4468d33c84f606dca4cb19ddf7628efd9b937bd63d3f
+size 59015
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/b1601cda0f9b4fadfd55056c4f8ebce1_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/b1601cda0f9b4fadfd55056c4f8ebce1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..691a70c12eccac7585615c972a20523b1d25376a
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/b1601cda0f9b4fadfd55056c4f8ebce1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c0bb803d05d11f4d82cd4e57983215601ea93ea78a5bf7b390d5055de55ec935
+size 116823
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e2d1f7d31e780508dffbbf041e0ff737289b19c9
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:09c85e5d087435658485b2893ea175e0ea0d6cb4ca00c99da9cdaa668f565508
+size 112063
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b35a18460c7c970e83844ca05d0ce9fe0745b5a2
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a7d170e057e41feab96f97d7c7be1eb07a8f65a8bb0613f525d27ec65d83649c
+size 89750
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/b469750c58d24c1d4904a2ded546fb35_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/b469750c58d24c1d4904a2ded546fb35_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..178e88a97a2b674317573694eac63540e2a5e2f5
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/b469750c58d24c1d4904a2ded546fb35_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e9c0a01ec5dcf28a55c40c001440c3f3c790aed4e5c4d1529989fe737470679
+size 106334
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/b5b908b453ca50ed3b4cca88aef080fa_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/b5b908b453ca50ed3b4cca88aef080fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e649a042b381f7e63cd976264affc7ec134f8e13
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/b5b908b453ca50ed3b4cca88aef080fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:36128754e3baff11550be9b84385d54b36375c228cf2282ad874a11c0c3520b0
+size 60116
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/bc27b89af9bb19320f22b573f65ab3c9_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/bc27b89af9bb19320f22b573f65ab3c9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..beede478d38d57ad3f0a83f8c7ab1a2c6cf6074b
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/bc27b89af9bb19320f22b573f65ab3c9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1e9b3e7665e653a790c91e9855139bece632378a9832331010e4ab1d1ec055b8
+size 85563
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/beda549cc2a4e2b9ac7f74fe9ed72b67_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/beda549cc2a4e2b9ac7f74fe9ed72b67_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..617cf45e350749183f4c47d71ba725496165308b
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/beda549cc2a4e2b9ac7f74fe9ed72b67_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1d3d80591320778459dadd7220c56b1a6fe44a7cddb974256c8ff177c11e8cca
+size 117369
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/c0f64806753a053854921deb8f4fc798_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/c0f64806753a053854921deb8f4fc798_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..62006ccee2058ecaa203afe9f104129aee65a113
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/c0f64806753a053854921deb8f4fc798_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8fa74f15936dbe3cdda41ecec2b5662de3a39d7a72db03c41ff04f56c49605dc
+size 26693
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/c19f37cdfc7768db716bfc0cc5934cfb_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/c19f37cdfc7768db716bfc0cc5934cfb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f7cd947740d30dc2845ee18da32170df8f480c14
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/c19f37cdfc7768db716bfc0cc5934cfb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:40cbd95273f0c35e20ad05398daf4394f5c2ebf33d6bb1ec67be33c1c05c63f6
+size 70220
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..51720c629c1a28295cb6d239089e8f3bdd55be8f
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:81b0e1a841a5ed549819bd81ac11633b31c1015dfbcae5ff2628f0482a7be9c1
+size 9824
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3
+size 4338
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/c7e27041e661260fd0c8e89c763bb32e_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/c7e27041e661260fd0c8e89c763bb32e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7757a88872c21c3cd65084f611cc02149aaaa4e3
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/c7e27041e661260fd0c8e89c763bb32e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:81d657214f9c7c74bd5a03f96e1ede84deb77ba8f2bb1c190db6a11c56d30b17
+size 75741
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/ca86f53f9735fe98b6c6003d1b759f64_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/ca86f53f9735fe98b6c6003d1b759f64_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..55ded586ecd06cd92b2e1f09f71f14709042409f
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/ca86f53f9735fe98b6c6003d1b759f64_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88d94fd98d751f083452c54985d54804b100c5258f524660b78b4f4f9537ae22
+size 116160
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..20d70f6d0cc588575dc1c7f0c8106271d59165f6
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fa0f7ad6a3d6881fd3563ee73aa8cf9a2c9365b26148300b500d87db62bdd7bd
+size 35456
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3803fce1d08d0b172daad886d92619ea0b041431
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c3182f3ee9b9950adcabaf3bf82b35210c3e7af3421a7219ffc84abcf1bc7ff
+size 41049
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/cfb98c691c1af5befe32ff9442eea511_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/cfb98c691c1af5befe32ff9442eea511_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2984a103917bbbbc19e140d82b57987427e02bfd
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/cfb98c691c1af5befe32ff9442eea511_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:33c1f2909c6b4660277d7dcb93bef17d0e20ad319d5a407a6ef16e283f1f6903
+size 113433
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/d3162014eae89d17bf0117dabb0c8796_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/d3162014eae89d17bf0117dabb0c8796_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..94873ea7fb493a4fecfed2e07fd10042154ea4e8
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/d3162014eae89d17bf0117dabb0c8796_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5692c100960c9ac48d85c9902a2a328c8fc29f39a23cd916730f2d8c7b0431ce
+size 25328
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/d49bc18ad8867b97bbb9aa580449a641_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/d49bc18ad8867b97bbb9aa580449a641_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0e41f69fcc6a68ded97c9eff9f6569638ea48a70
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/d49bc18ad8867b97bbb9aa580449a641_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4b30dcb9e11bf12971e5918937d16cb2913b96e72a1fb4034793ea899630de12
+size 143906
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..479fdfa922e1503d99097885d5a4a7569c0ecd7f
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d3779c6e5bb75e605d7ba20d08aa7bd8e326a7ea41d089cafb7e8124c8ccf1b2
+size 19967
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4c1aa511921f3b58f71b0366b39de14953800f56
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c88026e17fb046606d32ab1baac0cea449a09ee1255715f7de0166a5bc389c26
+size 149246
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6753635f430b469c4d4a6f46bed0595dab736851
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf47fa764a0f3dae0252eafcbe0870634baac753d455ce3e550df2927ddf962c
+size 131830
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/ddb58f51e65a3ae8ebc5911df26e18e0_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/ddb58f51e65a3ae8ebc5911df26e18e0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0271ce711a03c180afd527a01eface9d64a3d0c8
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/ddb58f51e65a3ae8ebc5911df26e18e0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:90be924dff95bd2ff33fdbbcd84c3b3a4387099ae3b4ba599737cdbe8099323c
+size 69212
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/defe20e5056d0c3552de2d50ce88c5cb_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/defe20e5056d0c3552de2d50ce88c5cb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6344f9408d63161119432b350b001b9e005592a3
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/defe20e5056d0c3552de2d50ce88c5cb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:10890027c8cd06bd4a6ea634f40f9a4f1c91376494fccf7f43057726fb10f0ee
+size 59004
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/dfafe39c233a62ec8ebd71e42992c14d_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/dfafe39c233a62ec8ebd71e42992c14d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a6716f675c18945dad7fa2dbada3ea5541a2d0e2
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/dfafe39c233a62ec8ebd71e42992c14d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2278dd777aadad8a33a78da05049903a9657c0c02c50fd202189091b914844e5
+size 50420
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4b2239de7f2b67eb01e3ed77618e84a38113159d
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b791f39fed1458b89722a2bdbbea3a5b3e833174d18855c01c19b94373e6d788
+size 132634
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b608c20ac28eef4a95af41c69d16f73f27c4183a
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eef885a9fa6f786a660c3be492632c04ab3d539b2ef3f383323bb79929a3e1a8
+size 58535
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f8a5d5e2ba346c4dee289ee8a5f265c542fd990a
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0e939d4553db8d4659f191b6c249e0cf3cc159683ff12414339a08db8c65dbb3
+size 52759
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/ef3cc411849a8effc80adb5a6ad57b36_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/ef3cc411849a8effc80adb5a6ad57b36_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d3f3b9d4fe956c23d416f18b8c04c52779689a49
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/ef3cc411849a8effc80adb5a6ad57b36_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:141a53b99dd853468fc678319a4ffc05b4ed568eb30d1d0918ba282415f2e714
+size 6140
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/ef45b00396c293be0b18d32b97118bf4_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/ef45b00396c293be0b18d32b97118bf4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..df6acaaf18f1aa09f6df3ccbfb73d96d0ba825bd
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/ef45b00396c293be0b18d32b97118bf4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d934287bacd9fffd5dc51670cbfaa07c2ad4d24d1bd60c6c41c682bdefbe7ce7
+size 146860
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/efbdff107f5a5aade487cf4ea0eae150_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/efbdff107f5a5aade487cf4ea0eae150_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..00fdc385397f8cc49f485405bc35ac04ab9b91ee
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/efbdff107f5a5aade487cf4ea0eae150_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b81064c58759be8b9e1a40de09b334c0ac335f72c525ff259a2be783147a78b
+size 145504
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/f142b022cfc716cd967297f027efe647_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/f142b022cfc716cd967297f027efe647_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e61696bfe754e79bdb973adecdb8c9ec5e771b40
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/f142b022cfc716cd967297f027efe647_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cd2a49323919fb189142435b361cd1d3fb0e79421cc44df5227f6a4802522742
+size 134420
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/f2486d5031b55e42b300903a716b0a00_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/f2486d5031b55e42b300903a716b0a00_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..62a338a276897ec7f43f217264ced37ca44ad86d
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/f2486d5031b55e42b300903a716b0a00_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1105657645dec2fee46f85bb697397c23e1008c9f560dc92c4ddab17828562fd
+size 81531
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/f2b561f8d2d2b8402379552179d9fbef_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/f2b561f8d2d2b8402379552179d9fbef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..853b46f88167adcc4fcedadc156ae901ab946fd7
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/f2b561f8d2d2b8402379552179d9fbef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d47f53f89215a69bd492a3c440aba3fb891c39c2c3edc3e48641260eb82141c8
+size 27970
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/f431b5db0c635c95318cff1adbe10c05_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/f431b5db0c635c95318cff1adbe10c05_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f5fec63f649e792888bf16b92d642d5522e23ccd
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/f431b5db0c635c95318cff1adbe10c05_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:98ab0ba30db4139f77a46b6055ed16ebadd7c7376b0efe4126c52b35e26d4b57
+size 25366
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/f4b18e76e0aa0f9625a027b444379b51_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/f4b18e76e0aa0f9625a027b444379b51_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..29768d7ba7f2723556ab1cbc7dfdb7b0432a2456
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/f4b18e76e0aa0f9625a027b444379b51_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1866304e51018d2fd513001b9db531c9dd5ef4e231e119d923e3f7dc695c9ca6
+size 116123
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/f8f8916ae391a1233c13ce738c699109_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/f8f8916ae391a1233c13ce738c699109_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..edaaf0d7eea4a55068cd3115ceff65b1572bb0a9
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/f8f8916ae391a1233c13ce738c699109_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d6bd143731a41e36b305fe0075da8c65bee2ac06ebdce3ed1d42e08341509af
+size 47957
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/f943b07ab747bfd85e302e5a31c20ba8_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/f943b07ab747bfd85e302e5a31c20ba8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2b6858490e98c1ae6d9096c0958b4eace734b1d5
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/f943b07ab747bfd85e302e5a31c20ba8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ff8d14097e83e332cba5cd68f5e2eda7477d06438951fc86ab720baf7bf64714
+size 38104
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..14120ee8aaf902f736494a29a60f599ba78dedde
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2bd0b0c33e38afc78c8ee1ff76a2f5da3d7db4ab7f7c3934e1aa4ebbd5b5b7d2
+size 48105
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b4ca880ecc84f4475fbbe7ffbc34ae723d30f965
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b2467e975632cfa15c7283a63f24b57f8dd93b5912d3fbb9e5dbd275caf6796e
+size 140765
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/fc7c83167c4e9e614f40e52b39ef735d_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/fc7c83167c4e9e614f40e52b39ef735d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e01a13bbdfb512e00557a4e3d9e30438e3cb84c4
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/fc7c83167c4e9e614f40e52b39ef735d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc5ec45fd82a77348b504cb82c079646d2fd1cd8853036cafac91c3813392f31
+size 120354
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/feae5a5b6e128162dbced0860fd97b9b_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/feae5a5b6e128162dbced0860fd97b9b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7225ff2a5a632abe4da0e233a4e63062569778e9
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/feae5a5b6e128162dbced0860fd97b9b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:95339a571114c9d8c25bafefc058f45cfb79131cb8ec8b6409076365e1550128
+size 104778
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/fee87ee34f98efee162e918fbaeec613_img.jpg b/marked/G/T-REC-G.707-200701-I_PDF-E/fee87ee34f98efee162e918fbaeec613_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f304ef92b5955a5712e993995aaee793fba4e08e
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/fee87ee34f98efee162e918fbaeec613_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:76cbfdb52e0fc3e20f93936d462a1e31241442a0ea08f628aa2a95dbd5b09f8a
+size 100429
diff --git a/marked/G/T-REC-G.707-200701-I_PDF-E/raw.md b/marked/G/T-REC-G.707-200701-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3661c8dd6528d724862466403d9c3ccb3cfcb600
--- /dev/null
+++ b/marked/G/T-REC-G.707-200701-I_PDF-E/raw.md
@@ -0,0 +1,6697 @@
+
+
+**ITU-T**
+
+**G.707/Y.1322**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(01/2007)
+
+SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
+DIGITAL SYSTEMS AND NETWORKS
+
+Digital terminal equipments – General
+
+SERIES Y: GLOBAL INFORMATION
+INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS
+AND NEXT-GENERATION NETWORKS
+
+Internet protocol aspects – Transport
+
+---
+
+**Network node interface for the synchronous
+digital hierarchy (SDH)**
+
+ITU-T Recommendation G.707/Y.1322
+
+# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS**
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 |
+| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 |
+| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 |
+| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 |
+| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 |
+| TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS | G.600–G.699 |
+| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 |
+| General | G.700–G.709 |
+| Coding of analogue signals by pulse code modulation | G.710–G.719 |
+| Coding of analogue signals by methods other than PCM | G.720–G.729 |
+| Principal characteristics of primary multiplex equipment | G.730–G.739 |
+| Principal characteristics of second order multiplex equipment | G.740–G.749 |
+| Principal characteristics of higher order multiplex equipment | G.750–G.759 |
+| Principal characteristics of transcoder and digital multiplication equipment | G.760–G.769 |
+| Operations, administration and maintenance features of transmission equipment | G.770–G.779 |
+| Principal characteristics of multiplexing equipment for the synchronous digital hierarchy | G.780–G.789 |
+| Other terminal equipment | G.790–G.799 |
+| DIGITAL NETWORKS | G.800–G.899 |
+| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 |
+| QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER-RELATED ASPECTS | G.1000–G.1999 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.6000–G.6999 |
+| DATA OVER TRANSPORT – GENERIC ASPECTS | G.7000–G.7999 |
+| PACKET OVER TRANSPORT ASPECTS | G.8000–G.8999 |
+| ACCESS NETWORKS | G.9000–G.9999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## ITU-T Recommendation G.707/Y.1322
+
+# Network node interface for the synchronous digital hierarchy (SDH)
+
+## Summary
+
+This Recommendation provides the requirements for the STM-N signals at the network node interface of a synchronous digital network, including B-ISDN in terms of:
+
+- bit rates;
+- frames structures;
+- formats for mapping and multiplexing of client signals (e.g., PDH, ATM and Ethernet) elements;
+- functionalities of the overheads.
+
+Revision 7.0 of ITU-T Recommendation G.707/Y.1322 is based on:
+
+- revision 6.0 approved 2003-12-14;
+- Corrigendum 1 approved 2004-06-13;
+- Amendment 1 approved 2004-08-22;
+- Corrigendum 2 approved 2005-08-22; and
+- editorial (non-technical) corrections.
+
+Amendment 1 provides a reciprocal linkage from the SDH Recommendation to the G-PON Recommendation G.984.3, and explains how the G-PON encapsulation method (GEM) transport of SDH signals fits into the multiplexing hierarchy.
+
+## Source
+
+ITU-T Recommendation G.707/Y.1322 was approved on 9 January 2007 by ITU-T Study Group 15 (2005-2008) under the ITU-T Recommendation A.8 procedure, including Amendment 1 to ITU-T Recommendation G.707/Y.1322 (2007), which was approved on 29 July 2007 by ITU-T Study Group 15 (2005-2008) under the ITU-T Recommendation A.8 procedure.
+
+## History
+
+| | | |
+|-----|-----------------------------|------------|
+| 1.0 | G.707 | 1988-11-25 |
+| 2.0 | G.707 | 1991-04-05 |
+| 3.0 | G.707 | 1993-03-12 |
+| 4.0 | G.707 | 1996-03-20 |
+| 5.0 | G.707/Y.1322 | 2000-10-06 |
+| 5.1 | G.707/Y.1322 (2000) Cor.1 | 2001-03-15 |
+| 5.2 | G.707/Y.1322 (2000) Cor.2 | 2001-11-29 |
+| 5.3 | G.707/Y.1322 (2000) Amend.1 | 2001-11-29 |
+| 5.4 | G.707/Y.1322 (2000) Amend.2 | 2002-08-06 |
+| 5.4 | G.707/Y.1322 (2000) Cor.3 | 2003-03-16 |
+| 5.5 | G.707/Y.1322 (2000) Amend.3 | 2003-04-13 |
+| 6.0 | G.707/Y.1322 | 2003-12-14 |
+| 6.1 | G.707/Y.1322 (2004) Cor.1 | 2004-06-13 |
+| 6.2 | G.707/Y.1322 (2004) Amend.1 | 2004-08-22 |
+| 6.3 | G.707/Y.1322 (2005) Cor.2 | 2005-08-22 |
+| 7.0 | G.707/Y.1322 | 2007-01-09 |
+| 7.1 | G.707/Y.1322 (2007) Amend.1 | 2007-07-29 |
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2008
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+# CONTENTS
+
+###### Page
+
+| | | |
+|------|---------------------------------------------------------------------------|-----|
+| 1 | Scope ..... | 1 |
+| 2 | References ..... | 1 |
+| 3 | Terms and definitions ..... | 2 |
+| 3.1 | Terms defined elsewhere..... | 2 |
+| 3.2 | Terms defined in this Recommendation..... | 3 |
+| 4 | Acronyms and abbreviations ..... | 4 |
+| 5 | Conventions ..... | 6 |
+| 6 | Basic multiplexing principles ..... | 7 |
+| 6.1 | Multiplexing structure ..... | 7 |
+| 6.2 | Basic frame structure..... | 11 |
+| 6.3 | Hierarchical bit rates ..... | 15 |
+| 6.4 | Interconnection of STM-Ns ..... | 16 |
+| 6.5 | Scrambling ..... | 17 |
+| 6.6 | Physical specification of the NNI..... | 18 |
+| 7 | Multiplexing method ..... | 18 |
+| 7.1 | Multiplexing of administrative units into STM-N ..... | 18 |
+| 7.2 | Multiplexing of tributary units into VC-4 and VC-3 ..... | 23 |
+| 7.3 | AU-n/TU-n numbering scheme..... | 27 |
+| 8 | Pointers..... | 49 |
+| 8.1 | AU-n pointer ..... | 49 |
+| 8.2 | TU-3 pointer ..... | 56 |
+| 8.3 | TU-2, TU-12 and TU-11 pointers ..... | 59 |
+| 9 | Overhead bytes description ..... | 64 |
+| 9.1 | Types of overhead ..... | 64 |
+| 9.2 | SOH description ..... | 64 |
+| 9.3 | POH descriptions..... | 77 |
+| 10 | Mapping of tributaries into VC-n/VC-m..... | 85 |
+| 10.1 | Mapping of G.702 type signals ..... | 85 |
+| 10.2 | Mapping of ATM cells..... | 100 |
+| 10.3 | Mapping of HDLC framed signals..... | 105 |
+| 10.4 | Mapping of DQDB into VC-4..... | 106 |
+| 10.5 | Asynchronous mapping for FDDI at 125 000 kbit/s into VC-4..... | 106 |
+| 10.6 | Mapping of GFP frames..... | 107 |
+| 10.7 | Asynchronous mapping of ODUk into a C-4-X transported via a VC-4-Xv. .... | 108 |
+
+| | Page |
+|----------------------------------------------------------------------------------------------|-------------|
+| 11 VC concatenation ..... | 113 |
+| 11.1 Contiguous concatenation of X VC-4s (VC-4-Xc, X = 4, 16, 64, 256)..... | 113 |
+| 11.2 Virtual concatenation of X VC-3s/VC-4s (VC-3-Xv/VC-4-Xv, X = 1 ... 256)..... | 114 |
+| 11.3 Contiguous concatenation of X VC-2s in a higher order VC-3 (VC-2-Xc, X = 1 ... 7) ..... | 120 |
+| 11.4 Virtual concatenation of X VC-11/VC-12/VC-2 ..... | 120 |
+| Annex A – Forward error correction for STM-64, and STM-256..... | 126 |
+| A.1 Network reference model ..... | 126 |
+| A.2 The FEC function ..... | 126 |
+| A.3 Mapping into the SDH frame ..... | 127 |
+| A.4 In-band FEC regenerator functions ..... | 129 |
+| A.5 Performance monitoring..... | 129 |
+| A.6 FEC activation and deactivation ..... | 130 |
+| A.7 Performance of in-band FEC..... | 131 |
+| Annex B – CRC-7 polynomial algorithm..... | 132 |
+| B.1 Multiplication/division process ..... | 132 |
+| B.2 Encoding procedure..... | 132 |
+| B.3 Decoding procedure ..... | 132 |
+| Annex C – VC-4-Xc/VC-4/VC-3 tandem connection monitoring protocol: Option 1 ..... | 133 |
+| C.1 Tandem connection overhead – Byte location ..... | 133 |
+| C.2 Definitions ..... | 135 |
+| C.3 Tandem connection bundling..... | 135 |
+| C.4 Incoming error count (IEC)..... | 136 |
+| C.5 B3 compensation ..... | 138 |
+| C.6 Data link ..... | 139 |
+| C.7 Treatment of incoming signal failures ..... | 146 |
+| C.8 Tandem connection idle signal..... | 148 |
+| C.9 Tandem connection test signal ..... | 148 |
+| Annex D – VC-4-Xc/VC-4/VC-3 tandem connection monitoring protocol: Option 2 ..... | 149 |
+| D.1 N1 byte structure ..... | 149 |
+| D.2 TCM functionality at the tandem connection source ..... | 150 |
+| D.3 TCM functionality at the tandem connection sink ..... | 151 |
+| D.4 BIP-8 compensation ..... | 152 |
+| Annex E – VC-2, VC-12 and VC-11 tandem connection monitoring protocol ..... | 153 |
+| E.1 N2 byte structure ..... | 153 |
+| E.2 TCM functionality at the tandem connection source ..... | 154 |
+| E.3 TCM functionality at the tandem connection sink ..... | 154 |
+| E.4 BIP-2 compensation ..... | 155 |
+
+| | Page |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Annex F – Transport of 10 Gbit/s Ethernet in a VC-4-64c ..... | 156 |
+| F.1 Mapping of Ethernet MAC into VC-4-64c using 64B/66B coding ..... | 156 |
+| Annex G – Mapping of $N \times$ TU-12 in $M$ virtual concatenated SHDSL pairs (dSTM-12N $M_i$ )..... | 157 |
+| G.1 Multiplex structure ..... | 157 |
+| G.2 Mapping overview..... | 159 |
+| Annex H – Mapping of TU-11, TU-12, TU-2 and TU-3 in G-PON GEM connections ..... | 160 |
+| H.1 Multiplex structure ..... | 160 |
+| H.2 Mapping overview..... | 160 |
+| Appendix I – Relationship between TU-2 address and location of columns within a VC-4... | 162 |
+| Appendix II – Relationship between TU-12 address and location of columns within a VC-4 ..... | 163 |
+| Appendix III – Relationship between TU-11 address and location of columns within a VC-4 ..... | 165 |
+| Appendix IV – Relationship between TU-2 address and location of columns within a VC-3 ..... | 168 |
+| Appendix V – Relationship between TU-12 address and location of columns within a VC-3 ..... | 169 |
+| Appendix VI – Relationship between TU-11 address and location of columns within a VC-3 ..... | 170 |
+| Appendix VII – Enhanced remote defect indication (ERDI) ..... | 171 |
+| VII.1 VC-4-Xc/VC-4/VC-3 paths..... | 171 |
+| VII.2 VC-2, VC-12 and VC-11 paths ..... | 172 |
+| Appendix VIII – Unexpected behaviour, dependence of TC monitoring on the incoming signal ..... | 174 |
+| VIII.1 Entering AIS condition (in case of VC-3/VC-4/VC-4-Xc)..... | 174 |
+| VIII.2 Entering AIS condition (in case of VC-11/VC-12/VC-2)..... | 174 |
+| VIII.3 Recovery from a phase jump (valid for all VC-n) ..... | 174 |
+| Appendix IX – Forward error correction for STM-16..... | 175 |
+| Appendix X – Performance of in-band FEC ..... | 176 |
+| Appendix XI – Nominal justification ratios for asynchronous mapping of ODU1 into C-4-17 and ODU2 into C-4-68..... | 179 |
+| Appendix XII – Consideration on 10 Gbit/s Ethernet WAN clock accuracy ..... | 182 |
+| Appendix XIII – Example LCAS control packet CRC calculations ..... | 183 |
+| XIII.1 Example of CRC-8 computation for LCAS and virtual concatenation carried in the H4 byte (i.e., VC-3-Xv and VC-4-Xv) ..... | 183 |
+| XIII.2 Example of CRC-3 computation for LCAS and virtual concatenation carried in bit 2 of the K4 byte (i.e., VC-2-Xv, VC-12-Xv and VC-11-Xv)... | 184 |
+| Appendix XIV – Mapping serial data into a VCG ..... | 185 |
+| Bibliography ..... | 186 |
+
+
+
+# Network node interface for the synchronous digital hierarchy (SDH)
+
+# 1 Scope
+
+This Recommendation covers the network node interface (NNI) specifications which are necessary to enable interconnection of network elements at their synchronous digital hierarchy (SDH) interfaces for the transport of different types of payloads.
+
+Therefore, this Recommendation specifies:
+
+- the bit rates for STM-N signals;
+ - the frames structures for STM-N signals;
+ - the formats for mapping and multiplexing of client signals (e.g., PDH, ATM and Ethernet) elements into an STM-N frame;
+ - the functionalities to be implemented in the different overheads of an STM-N frame;
+- at the NNI of a synchronous digital network, including B-ISDN.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- ITU-T Recommendation G.691 (2006), *Optical interfaces for single-channel STM-64 and other SDH systems with optical amplifiers*.
+- ITU-T Recommendation G.702 (1988), *Digital hierarchy bit rates*.
+- ITU-T Recommendation G.703 (2001), *Physical/electrical characteristics of hierarchical digital interfaces*.
+- ITU-T Recommendation G.704 (1998), *Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736 kbit/s hierarchical levels*.
+- ITU-T Recommendation G.709/Y.1331 (2003), *Interfaces for the Optical Transport Network (OTN)*.
+- ITU-T Recommendation G.780/Y.1351 (2004), *Terms and definitions for synchronous digital hierarchy (SDH) networks*.
+- ITU-T Recommendation G.783 (2006), *Characteristics of synchronous digital hierarchy (SDH) equipment functional blocks*.
+- ITU-T Recommendation G.7041/Y.1303 (2005), *Generic framing procedure (GFP)*.
+- ITU-T Recommendation G.7042/Y.1305 (2006), *Link capacity adjustment scheme (LCAS) for virtual concatenated signals*.
+- ITU-T Recommendation G.802 (1988), *Interworking between networks based on different digital hierarchies and speech encoding laws*.
+- ITU-T Recommendation G.803 (2000), *Architecture of transport networks based on the synchronous digital hierarchy (SDH)*.
+
+- ITU-T Recommendation G.806 (2006), *Characteristics of transport equipment – Description methodology and generic functionality.*
+- ITU-T Recommendation G.831 (2000), *Management capabilities of transport networks based on the synchronous digital hierarchy (SDH).*
+- ITU-T Recommendation G.841 (1998), *Types and characteristics of SDH network protection architectures.*
+- ITU-T Recommendation G.957 (2006), *Optical interfaces for equipments and systems relating to the synchronous digital hierarchy.*
+- ITU-T Recommendation G.984.3 (2004), *Gigabit-capable Passive Optical Networks (G-PON): Transmission convergence layer specifications.*
+- ITU-T Recommendation G.991.2 (2003), *Single-pair high-speed digital subscriber line (SHDSL) transceivers.*
+- ITU-T Recommendation I.432.1 (1999), *B-ISDN user-network interface – Physical layer specification: General characteristics.*
+- ITU-T Recommendation I.432.2 (1999), *B-ISDN user-network interface – Physical layer specification: 155 520 kbit/s and 622 080 kbit/s operation.*
+- ITU-T Recommendation O.181 (2002), *Equipment to assess error performance on STM-N interfaces.*
+- ITU-T Recommendation Q.921 (1997), *ISDN user-network interface – Data link layer specification.*
+- ITU-R Recommendation F.750-4 (2000), *Architectures and functional aspects of radio-relay systems for synchronous digital hierarchy (SDH)-based networks.*
+- ITU-R Recommendation S.1149-2 (2005), *Network architecture and equipment functional aspects of digital satellite systems in the fixed-satellite service forming part of synchronous digital hierarchy transport networks.*
+- ETSI ETS 300 216 (1992), *Network Aspects (NA); Metropolitan Area Network (MAN); Physical layer convergence procedure for 155,520 Mbit/s.*
+- IEEE Standard 802.3 (2005), *Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks – Specific requirements Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications Amendment: Media Access Control (MAC) Parameters, Physical Layers, and Management Parameters for 10 Gb/s Operation.*
+
+# 3 Terms and definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+- 3.1.1 **synchronous digital hierarchy (SDH)**: See ITU-T Rec. G.780/Y.1351.
+- 3.1.2 **synchronous transport module (STM)**: See ITU-T Rec. G.780/Y.1351.
+- 3.1.3 **virtual container-n (VC-n)**: See ITU-T Rec. G.780/Y.1351.
+- 3.1.4 **administrative unit-n (AU-n)**: See ITU-T Rec. G.780/Y.1351.
+- 3.1.5 **tributary unit-n (TU-n)**: See ITU-T Rec. G.780/Y.1351.
+- 3.1.6 **container-n (n=11, 12, 2, 3, 4)**: See ITU-T Rec. G.780/Y.1351.
+
+**3.1.7 network node interface (NNI):** See ITU-T Rec. G.780/Y.1351.
+
+Figure 3-1 gives a possible network configuration to illustrate the location of NNI specified in this Recommendation.
+
+
+
+DXC Digital cross-connect equipment
+EA External Access equipment
+SM Synchronous Multiplexer
+TR Tributary
+
+G.707-Y1322\_F3-1
+
+Figure 3-1: Location of the NNI. The diagram shows a network configuration with four NNI points. On the left, three tributaries (TR) are connected to synchronous multiplexers (SM). Two SMs are connected to a central 'Line/radio systems' block via an NNI. The third SM is connected to the same 'Line/radio systems' block via another NNI. The 'Line/radio systems' block is connected to a 'DXC/EA' block via an NNI. The 'DXC/EA' block is connected to another 'Line/radio systems' block via an NNI. This second 'Line/radio systems' block is connected to two more SMs via NNIs. These SMs are then connected to three more tributaries (TR) on the right. A legend at the bottom left defines the abbreviations: DXC (Digital cross-connect equipment), EA (External Access equipment), SM (Synchronous Multiplexer), and TR (Tributary). A reference code G.707-Y1322\_F3-1 is shown in the bottom right.
+
+**Figure 3-1 – Location of the NNI**
+
+**3.1.8 pointer:** See ITU-T Rec. G.780/Y.1351.
+
+**3.1.9 administrative unit group (AUG):** See ITU-T Rec. G.780/Y.1351.
+
+**3.1.10 SDH mapping:** See ITU-T Rec. G.780/Y.1351.
+
+**3.1.11 SDH multiplexing:** See ITU-T Rec. G.780/Y.1351.
+
+**3.1.12 SDH aligning:** See ITU-T Rec. G.780/Y.1351.
+
+**3.1.13 Bit Interleaved Parity-X (BIP-X):** See ITU-T Rec. G.780/Y.1351.
+
+**3.1.14 concatenation:** See ITU-T Rec. G.780/Y.1351.
+
+**3.1.15 shortened binary-BCH:** See ITU-T Rec. G.780/Y.1351.
+
+**3.1.16 generator polynomial:** See ITU-T Rec. G.780/Y.1351.
+
+**3.1.17 systematic code:** ITU-T Rec. G.780/Y.1351.
+
+**3.1.18 tributary unit group (TUG):** See ITU-T Rec. G.780/Y.1351.
+
+**3.1.19 dSTM-12*Ni* interface:** See ITU-T Rec. G.780/Y.1351.
+
+## **3.2 Terms defined in this Recommendation**
+
+This Recommendation defines the following terms:
+
+**3.2.1 gSTM-11 interface:** An SDH transmission interface which transports one TU-11, with G-PON based Section overhead. gSTM-11 interfaces are defined for G-PON transport technologies. Refer to Table H.1.
+
+**3.2.2 gSTM-12 interface:** An SDH transmission interface which transports one TU-12, with G-PON based Section overhead. gSTM-12 interfaces are defined for G-PON transport technologies. Refer to Table H.1.
+
+**3.2.3 gSTM-2 interface:** An SDH transmission interface which transports one TU-2, with G-PON based Section overhead. gSTM-2 interfaces are defined for G-PON transport technologies. Refer to Table H.1.
+
+**3.2.4 gSTM-3 interface:** An SDH transmission interface which transports one TU-3, with G-PON based Section overhead. gSTM-3 interfaces are defined for G-PON transport technologies. Refer to Table H.1.
+
+# **4 Acronyms and abbreviations**
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|-------|------------------------------------------|
+| AIS | Alarm Indication Signal |
+| API | Access Point Identifier |
+| APS | Automatic Protection Switching |
+| ATM | Asynchronous Transfer Mode |
+| AU-n | Administrative Unit-n |
+| AUG-N | Administrative Unit Group-N |
+| BCH | Bose-Chaudhuri-Hocquenghem |
+| BCH-3 | Triple error correcting BCH code |
+| BER | Bit Error Ratio |
+| BIP-X | Bit Interleaved Parity-X |
+| C-n | Container-n |
+| CAS | Channel Associated Signalling |
+| CRC-N | Cyclic Redundancy Check, width N |
+| CTRL | Control word sent from source to sink |
+| DCC | Data Communication Channel |
+| DQDB | Distributed Queue Dual Bus |
+| DNU | Do Not Use |
+| dSTM | SHDSL based Synchronous Transport Module |
+| EOS | End of Sequence |
+| FCS | Frame Check Sequence |
+| FDDI | Fibre Distributed Data Interface |
+| FEFE | Far End Block Error (renamed as REI) |
+| FEC | Forward Error Correction |
+| FERF | Far End Receive Failure (renamed as RDI) |
+| FSI | FEC Status Indication |
+| GEM | G-PON Encapsulation Method |
+| GID | Group Identification |
+| gSTM | GEM based Synchronous Transport Mode |
+| HDLC | High-level Data Link Control |
+| HEC | Header Error Control |
+| HOVC | Higher Order Virtual Container |
+| IEC | Incoming Error Count |
+
+| | |
+|---------|-----------------------------------------------|
+| IP | Internet Protocol |
+| ISF | Incoming Signal Failure |
+| ISDN | Integrated Services Digital Network |
+| ISID | Idle Signal Identification |
+| LAPD | Link Access Protocol for D-channel |
+| LAPS | Link Access Procedure – SDH |
+| LCAS | Link Capacity Adjustment Scheme |
+| LCD | Loss of Cell Delineation |
+| LOP | Loss of Pointer |
+| LOVC | Lower Order Virtual Container |
+| LSB | Least Significant Bit |
+| MAN | Metropolitan Area Network |
+| MFI | MultiFrame Indicator |
+| MSB | Most Significant Bit |
+| MS-AIS | Multiplex Section Alarm Indication Signal |
+| MSF-AIS | Multiplex Section FEC Alarm Indication Signal |
+| MSOH | Multiplex Section Overhead |
+| MS-RDI | Multiplex Section Remote Defect Indication |
+| MS-REI | Multiplex Section Remote Error Indication |
+| MST | Member Status |
+| MSTE | Multiplex Section Terminating Element |
+| NDF | New Data Flag |
+| NNI | Network Node Interface |
+| NORM | Normal Operating Mode |
+| ODI | Outgoing Defect Indication |
+| ODUk | Optical channel Data Unit-k |
+| OEI | Outgoing Error Indication |
+| OH | Overhead |
+| OPUk | Optical channel Payload Unit-k |
+| OTN | Optical Transport Network |
+| OTUk | Optical channel Transport Unit-k |
+| PDH | Plesiochronous Digital Hierarchy |
+| PLM | Payload Mismatch |
+| POH | Path Overhead |
+| PPP | Point-to-Point Protocol |
+| PTE | Path Terminating Element |
+| PTR | Pointer |
+
+| | |
+|---------|--------------------------------------------|
+| RDI | Remote Defect Indication (former FERF) |
+| REI | Remote Error Indication (former FEBE) |
+| RFI | Remote Failure Indication |
+| RS-Ack | Re-sequence Acknowledge |
+| RSOH | Regenerator Section Overhead |
+| SD | Signal Degrade |
+| SDH | Synchronous Digital Hierarchy |
+| SLM | Signal Label Mismatch |
+| SOH | Section Overhead |
+| SQ | Sequence Indicator |
+| SSU | Synchronization Supply Unit |
+| STM(-N) | Synchronous Transport Module (-N) |
+| TCM | Tandem Connection Monitoring |
+| TC-RDI | Tandem Connection Remote Defect Indication |
+| TC-REI | Tandem Connection Remote Error Indication |
+| TCOH | Tandem Connection Overhead |
+| TCT | Tandem Connection Trace |
+| TCETE | Tandem Connection Terminating Element |
+| TIM | Trace Identifier Mismatch |
+| TSID | Test Signal Identification |
+| TTI | Trail Trace Identifier |
+| TU-n | Tributary Unit-n |
+| TUG(-n) | Tributary Unit Group (-n) |
+| UNEQ | UNEQuipped |
+| VC-n | Virtual Container-n |
+| VC-n-X | X concatenated Virtual Container-ns |
+| VC-n-Xc | X Contiguously concatenated VC-ns |
+| VC-n-Xv | X Virtually concatenated VC-ns |
+| VCG | Virtual Concatenation Group |
+| WAN | Wide Area Network |
+
+# 5 Conventions
+
+The order of transmission of information in all the figures in this Recommendation is first from left to right and then from top to bottom. Within each byte, the most significant bit is transmitted first. The most significant bit (bit 1) is illustrated at the left in all the figures.
+
+# 6 Basic multiplexing principles
+
+## 6.1 Multiplexing structure
+
+Figure 6-1 shows the relationship between various multiplexing elements that are defined in Table 6-1, and illustrates possible multiplexing structures.
+
+Figures 6-2, 6-3, 6-4 and 6-5 show how various signals are multiplexed using these multiplexing elements.
+
+Details of the multiplexing method and mappings are given in clauses 7 and 10.
+
+Descriptions of the various multiplexing elements are given in clauses 8 to 10.
+
+Descriptions of the various concatenations are given in clause 11.
+
+NOTE – High rate VC-4-Xc could be used without any constraints in point-to-point connections. SDH networks may be limited to a certain bit rate of VC-4-Xc (e.g., $X \leq 64$ ), e.g., due to rings with MS SPRING that has to reserve 50% of the STM-N bandwidth for protection.
+
+**Table 6-1 – VC types and capacity**
+
+| VC type | VC bandwidth | VC payload |
+|-----------|-------------------|-------------------|
+| VC-11 | 1 664 kbit/s | 1 600 kbit/s |
+| VC-12 | 2 240 kbit/s | 2 176 kbit/s |
+| VC-2 | 6 848 kbit/s | 6 784 kbit/s |
+| VC-3 | 48 960 kbit/s | 48 384 kbit/s |
+| VC-4 | 150 336 kbit/s | 149 760 kbit/s |
+| VC-4-4c | 601 344 kbit/s | 599 040 kbit/s |
+| VC-4-16c | 2 405 376 kbit/s | 2 396 160 kbit/s |
+| VC-4-64c | 9 621 504 kbit/s | 9 584 640 kbit/s |
+| VC-4-256c | 38 486 016 kbit/s | 38 338 560 kbit/s |
+
+
+
+STM-256 $\xrightarrow{\times 1}$ AUG-256 $\xleftarrow{\times 1}$ AU-4-256c $\dashleftarrow$ VC-4-256c $\xleftarrow{\times 1}$ C-4-256c
+ STM-64 $\xrightarrow{\times 1}$ AUG-64 $\xleftarrow{\times 1}$ AU-4-64c $\dashleftarrow$ VC-4-64c $\xleftarrow{\times 1}$ C-4-64c
+ STM-16 $\xrightarrow{\times 1}$ AUG-16 $\xleftarrow{\times 1}$ AU-4-16c $\dashleftarrow$ VC-4-16c $\xleftarrow{\times 1}$ C-4-16c
+ STM-4 $\xrightarrow{\times 1}$ AUG-4 $\xleftarrow{\times 1}$ AU-4-4c $\dashleftarrow$ VC-4-4c $\xleftarrow{\times 1}$ C-4-4c
+ STM-1 $\xrightarrow{\times 1}$ AUG-1 $\xleftarrow{\times 1}$ AU-4 $\dashleftarrow$ VC-4 $\xleftarrow{\times 1}$ C-4
+ STM-0 $\xrightarrow{\times 1}$ AU-3 $\dashleftarrow$ VC-3 $\xleftarrow{\times 1}$ C-3
+
+AUG-256 $\xleftarrow{\times 4}$ AUG-64
+ AUG-64 $\xleftarrow{\times 4}$ AUG-16
+ AUG-16 $\xleftarrow{\times 4}$ AUG-4
+ AUG-4 $\xleftarrow{\times 4}$ AUG-1
+
+VC-4 $\xleftarrow{\times 3}$ TUG-3 $\xleftarrow{\times 1}$ TU-3 $\dashleftarrow$ VC-3 $\xleftarrow{\times 1}$ C-3
+ VC-3 $\xleftarrow{\times 7}$ TUG-2 $\xleftarrow{\times 1}$ TU-2 $\dashleftarrow$ VC-2 $\xleftarrow{\times 1}$ C-2
+ TUG-2 $\xleftarrow{\times 3}$ TU-12 $\dashleftarrow$ VC-12 $\xleftarrow{\times 1}$ C-12
+ TUG-2 $\xleftarrow{\times 4}$ TU-11 $\dashleftarrow$ VC-11 $\xleftarrow{\times 1}$ C-11
+
+Legend:
+ [Hatched Box] Pointer processing
+ $\xleftarrow{\text{solid}}$ Multiplexing
+ $\dashleftarrow$ Aligning
+ $\xleftarrow{\text{solid}}$ Mapping
+
+G.707-Y1322\_F6-1
+
+A complex block diagram showing the multiplexing structure for STM signals. It starts with STM-256, STM-64, STM-16, STM-4, STM-1, and STM-0 on the left. These are processed through AUG (AUG-256, AUG-64, AUG-16, AUG-4, AUG-1) and AU (AU-4-256c, AU-4-64c, AU-4-16c, AU-4-4c, AU-4, AU-3) blocks, then VC (VC-4-256c, VC-4-64c, VC-4-16c, VC-4-4c, VC-4, VC-3) blocks, and finally C (C-4-256c, C-4-64c, C-4-16c, C-4-4c, C-4, C-3) blocks. The diagram also shows further multiplexing of lower-order signals through TUG-3, TUG-2, TU-3, TU-2, TU-12, and TU-11 blocks into VC-3, VC-2, VC-12, and VC-11 blocks, leading to C-2, C-12, and C-11 blocks. A legend at the bottom left defines the symbols: hatched box for 'Pointer processing', solid line with arrow for 'Multiplexing', dashed line with arrow for 'Aligning', and solid line with arrow for 'Mapping'. The text 'G.707-Y1322\_F6-1' is in the bottom right corner.
+
+Figure 6-1 – Multiplexing structure
+
+
+
+The diagram illustrates the multiplexing hierarchy for SDH/SONET. At the top, a **Container-1n** is shown. Below it, a **VC-1n** is formed by adding a **VC-1n POH** to the **Container-1n**. This **VC-1n** is then mapped into a **TU-1n**. The **TU-1n** contains a **TU-1n PTR** and a shaded **VC-1n** payload. Multiple **TU-1n** units are multiplexed into a **TUG-2**. Multiple **TUG-2** units are then multiplexed into a **TUG-3**. A **VC-4 POH** is added to the **TUG-3** to form a **VC-4**. This **VC-4** is mapped into an **AU-4**, which contains an **AU-4 PTR** and a shaded **VC-4** payload. Finally, the **AU-4** is mapped into an **AUG-1**.
+
+→ Logical association
+ - - - - - Physical association
+
+G.707/Y.1322COR.1\_F6-2
+
+Diagram illustrating the multiplexing method directly from container-11/container-12 using AU-4. The diagram shows the hierarchy of SDH/SONET structures: Container-1n, VC-1n, TU-1n, TUG-2, TUG-3, VC-4, AU-4, and AUG-1. Logical associations are shown with solid arrows, and physical associations with dashed lines. Shaded areas represent VC-1n and VC-4 components. PTR (Pointer) fields are shown for TU-1n and AU-4. Legend for associations
+
+NOTE 1 – Unshaded areas are phase aligned. Phase alignment between the unshaded and shaded areas is defined by the pointer (PTR) and is indicated by the arrow.
+
+NOTE 2 – n = 1, 2.
+
+**Figure 6-2 – Multiplexing method directly from container-11/container-12 using AU-4**
+
+
+
+The diagram illustrates the multiplexing hierarchy for container-11/container-12 using AU-3. It starts with Container-1n at the top, which is mapped into VC-1n (consisting of VC-1n POH and Container-1n). This VC-1n is then mapped into TU-1n (consisting of TU-1n PTR and VC-1n). Two TU-1n units are mapped into TUG-2 (consisting of TU-1n PTR, VC-1n, and TU-1n PTR). Two TUG-2 units are mapped into VC-3 (consisting of VC-3 POH and two TUG-2 units). This VC-3 is mapped into AU-3 (consisting of AU-3 PTR and VC-3). Finally, two AU-3 units are mapped into AUG-1 (consisting of AU-3 PTR, VC-3, and AU-3 PTR). Logical associations are shown with solid arrows, and physical associations are shown with dashed lines. Shaded areas indicate phase-aligned regions.
+
+Diagram of multiplexing method directly from container-11/container-12 using AU-3. It shows the hierarchy from Container-1n down to AUG-1, with logical and physical associations between various pointers (TU-1n PTR, VC-1n POH, VC-1n, VC-3 POH, TUG-2, AU-3 PTR, VC-3, AUG-1) and containers. Shaded areas represent phase-aligned regions.
+
+➔ Logical association
+
+Physical association
+
+G.707/Y.1322COR.1\_F6-3
+
+NOTE 1 – Unshaded areas are phase aligned. Phase alignment between the unshaded and shaded areas is defined by the pointer (PTR) and is indicated by the arrow.
+
+NOTE 2 – n = 1, 2.
+
+**Figure 6-3 – Multiplexing method directly from container-11/container-12 using AU-3**
+
+
+
+The diagram illustrates the multiplexing hierarchy for container-3 using AU-3. It starts with Container-3 at the top, which is mapped into VC-3 (consisting of VC-3 POH and Container-3). This VC-3 is mapped into AU-3 (consisting of AU-3 PTR and VC-3). Finally, two AU-3 units are mapped into AUG-1 (consisting of AU-3 PTR, VC-3, and AU-3 PTR). Logical associations are shown with solid arrows, and physical associations are shown with dashed lines. Shaded areas indicate phase-aligned regions.
+
+Diagram of multiplexing method directly from container-3 using AU-3. It shows the hierarchy from Container-3 down to AUG-1, with logical and physical associations between various pointers (VC-3 POH, AU-3 PTR, VC-3, AUG-1) and containers. Shaded areas represent phase-aligned regions.
+
+➔ Logical association
+
+Physical association
+
+G.707-Y.1322\_F6-4
+
+NOTE – Unshaded areas are phase aligned. Phase alignment between the unshaded and shaded areas is defined by the pointer (PTR) and is indicated by the arrow.
+
+**Figure 6-4 – Multiplexing method directly from container-3 using AU-3**
+
+
+
+→ Logical association
+- - - Physical association
+
+G.707-Y.1322\_F6-5
+
+Diagram illustrating the multiplexing method directly from container-4 using AU-4. It shows the hierarchy from Container-4 down to AUG-1. Container-4 is shown as a single block. Below it, a VC-4 is formed by adding a VC-4 POH to the Container-4. This VC-4 is then mapped into an AU-4, which includes an AU-4 PTR. The AU-4 is then mapped into an AUG-1, which also includes an AU-4 PTR. The diagram uses solid arrows for logical associations and dashed lines for physical associations. A legend indicates that unshaded areas are phase aligned and shaded areas are not. The pointer (PTR) is indicated by an arrow.
+
+NOTE – Unshaded areas are phase aligned. Phase alignment between the unshaded and shaded areas is defined by the pointer (PTR) and is indicated by the arrow.
+
+**Figure 6-5 – Multiplexing method directly from container-4 using AU-4**
+
+## 6.2 Basic frame structure
+
+STM-N frame structure is shown in Figure 6-6. The three main areas of the STM-N frame are indicated:
+
+- SOH;
+- Administrative unit pointer(s);
+- Information payload.
+
+
+
+G.707-Y.1322\_F6-6
+
+Diagram illustrating the STM-N frame structure. The frame is shown as a grid of 9 rows and 270 x N columns (bytes). The first 9 columns (3 for STM-0) are Section Overhead (SOH), which is divided into two shaded regions: rows 1-3 and rows 5-9. Row 4 contains the Administrative unit pointer(s). The remaining 261 columns (87 for STM-0) form the STM-N payload, which is an unshaded region. The total number of columns is 270 x N (90 columns for STM-0). The total number of rows is 9.
+
+**Figure 6-6 – STM-N frame structure**
+
+### 6.2.1 Section overhead
+
+Rows 1-3 and 5-9 of columns 1 to $9 \times N$ of the STM-N in Figure 6-6 are dedicated to the SOH.
+
+The allocation of SOH capacity and an explanation of the overhead functions are given in clause 9.
+
+### 6.2.2 Administrative unit pointers
+
+Row 4 of columns 1 to $9 \times N$ in Figure 6-6 is available for administrative unit pointers. The application of pointers and their detailed specifications are given in clause 8.
+
+### 6.2.3 Administrative units in the STM-N
+
+The STM-N payload supports one AUG-N where the:
+
+- a) AUG-256 may consist of:
+ - 1) four AUG-64;
+ - 2) one AU-4-256c.
+- b) AUG-64 may consist of:
+ - 1) four AUG-16;
+ - 2) one AU-4-64c.
+- c) AUG-16 may consist of:
+ - 1) four AUG-4;
+ - 2) one AU-4-16c.
+- d) AUG-4 may consist of:
+ - 1) four AUG-1;
+ - 2) one AU-4-4c.
+- e) AUG-1 may consist of:
+ - 1) one AU-4;
+ - 2) three AU-3s.
+
+The VC-n associated with each AU-n does not have a fixed phase with respect to the STM-N frame. The location of the first byte of the VC-n is indicated by the AU-n pointer. The AU-n pointer is in a fixed location in the STM-N frame. Examples are illustrated in Figures 6-2, 6-3, 6-4, 6-5, 6-6, 6-7 and 6-8.
+
+The AU-4 may be used to carry, via the VC-4, a number of TU-ns ( $n=11, 12, 2, 3$ ) forming a two-stage multiplex. An example of this arrangement is illustrated in Figures 6-7 a and 6-8 a. The VC-n associated with each TU-n does not have a fixed phase relationship with respect to the start of the VC-4. The TU-n pointer is in a fixed location in the VC-4 and the location of the first byte of the VC-n is indicated by the TU-n pointer.
+
+The AU-3 may be used to carry, via the VC-3, a number of TU-ns ( $n=11, 12, 2$ ) forming a two-stage multiplex. An example of this arrangement is illustrated in Figures 6-7 b and 6-8 b. The VC-n associated with each TU-n does not have a fixed phase relationship with respect to the start of the VC-3. The TU-n pointer is in a fixed location in the VC-3 and the location of the first byte of the VC-n is indicated by the TU-n pointer.
+
+
+
+Diagram a) STM-1 with one AU-4. It shows a vertical stack of three boxes on the left. The top box is empty, the middle box contains an 'X' (AU-n pointer), and the bottom box is empty. To the right of the middle box is a large rectangle labeled 'VC-4'.
+
+a) STM-1 with one AU-4
+
+
+
+Diagram b) STM-1 with three AU-3s. It shows a vertical stack of three boxes on the left. The top box is empty, the middle box contains three 'X's (three AU-n pointers), and the bottom box is empty. To the right of the middle box are three overlapping rectangles, the front-most labeled 'VC-3'.
+
+G.707-Y.1322\_F6-7
+
+b) STM-1 with three AU-3s
+
+X AU-n pointer
+
+AU-n AU-n pointer + VC-n (see clause 8)
+
+**Figure 6-7 – Administrative units in STM-1 frame**
+
+
+
+Diagram a) STM-1 with one AU-4 containing TUs. It shows a vertical stack of three boxes on the left. The top box is empty, the middle box contains an 'X' (AU-n pointer), and the bottom box is empty. To the right of the middle box is a large rectangle labeled 'VC-4'. Inside this rectangle, at the top, is a smaller rectangle containing 'o o . . . o' (TU-n pointers). Below that is another rectangle containing '....'. At the bottom is a rectangle labeled 'VC-n' with 'n = 11, 12, 2, 3' below it.
+
+a) STM-1 with one AU-4 containing TUs
+
+X AU-n pointer
+
+o TU-n pointer
+
+AU-n AU-n pointer + VC-n (see clause 8)
+
+TU-n TU-n pointer + VC-n (see clause 8)
+
+
+
+Diagram b) STM-1 with three AU-3s containing TUs. It shows a vertical stack of three boxes on the left. The top box is empty, the middle box contains three 'X's (three AU-n pointers), and the bottom box is empty. To the right of the middle box are three overlapping rectangles, the front-most labeled 'VC-3'. Each of these rectangles contains a smaller rectangle at the top with 'o o . . . o' (TU-n pointers), a middle rectangle with '....', and a bottom rectangle labeled 'VC-n' with 'n = 11, 12, 2' below it.
+
+G.707/Y.1322COR.1\_F6-8
+
+b) STM-1 with three AU-3s containing TUs
+
+**Figure 6-8 – Two-stage multiplex**
+
+### 6.2.4 Maintenance signals
+
+#### 6.2.4.1 Alarm indication signals
+
+An alarm indication signal (AIS) is a signal sent downstream as an indication that an upstream defect has been detected.
+
+##### 6.2.4.1.1 MS-AIS
+
+The multiplex section AIS (MS-AIS) is specified as all "1"s in the entire STM-N, excluding the STM-N RSOH.
+
+##### 6.2.4.1.2 MSF-AIS
+
+The multiplex section FEC AIS (MSF-AIS) is specified as all "1"s in the entire STM-N, excluding the STM-N RSOH except P1 and Q1 bytes.
+
+##### 6.2.4.1.3 AU/TU-AIS
+
+The administrative unit AIS (AU-AIS) is specified as all "1"s in the entire AU-n (n=3, 4, 4-Xc), including the AU-n pointer.
+
+The tributary unit AIS (TU-AIS) is specified as all "1"s in the entire TU-n (n=11, 12, 2, 3), including the TU-n pointer.
+
+##### 6.2.4.1.4 VC-AIS
+
+An AU/TU-AIS incoming to a tandem connection (TC) is translated into a virtual container AIS (VC-AIS) within the tandem connection because a valid AU-n/TU-n pointer is needed for tandem connection monitoring (TCM).
+
+VC-n (n=3, 4, 4-Xc) AIS is specified as all "1"s in the entire VC-n with a valid network operator byte N1, supporting TCM functionality, and a valid error detection code in the B3 byte.
+
+VC-m (m=11, 12, 2) AIS is specified as all "1"s in the entire VC-m with a valid network operator byte N2, supporting TCM functionality, and a valid error detection code in bits 1 and 2 of the V5 byte.
+
+#### 6.2.4.2 Unequipped VC-n/VC-m signal
+
+##### 6.2.4.2.1 Case of network supporting the transport of tandem connection signals
+
+For the case of networks supporting the transport of tandem connection signals, the VC-n (n=3, 4) or VC-4-Xc unequipped signal is a signal having an all "0"s in the higher order virtual container path signal label byte (C2), the tandem connection monitoring byte (N1) and the path trace byte (J1), and a valid BIP-8 byte (B3). The virtual container payload and the remaining path overhead bytes are unspecified.
+
+For the case of networks supporting the transport of tandem connection signals, the VC-m (m=11, 12, 2) unequipped signal is a signal having an all "0"s in the lower order virtual container path signal label (bits 5, 6, 7 of byte V5), the tandem connection monitoring byte (N2) and the path trace byte (J2), and a valid BIP-2 (bits 1, 2 of byte V5). The virtual container payload and the remaining path overhead bytes are unspecified.
+
+These signals indicate to downstream transport processing functions (refer to ITU-T Rec. G.803) that the virtual container is unoccupied, not connected to a path termination source function. Additional information on the quality is only available by means of the BIP monitoring.
+
+Within a tandem connection, an unequipped VC-n/VC-m signal generated before the tandem connection will have a valid (non all "0"s) tandem connection monitoring byte (N1, N2).
+
+##### 6.2.4.2.2 Case of network not supporting the transport of tandem connection signals
+
+For the case of networks not supporting the transport of tandem connection signals, the VC-n (n=3, 4) or VC-4-Xc unequipped signal is a signal having an all "0"s in the higher order virtual container path signal label byte (C2) and the path trace byte (J1), and a valid BIP-8 byte (B3). The virtual container payload and the remaining path overhead bytes are unspecified.
+
+For the case of networks not supporting the transport of tandem connection signals, the VC-m (m=11, 12, 2) unequipped signal is a signal having an all "0"s in the lower order virtual container path signal label (bits 5, 6, 7 of byte V5) and the path trace byte (J2), and a valid BIP-2 (bits 1, 2 of byte V5). The virtual container payload and the remaining path overhead bytes are unspecified.
+
+#### 6.2.4.3 Supervisory-unequipped VC-n/VC-m signal
+
+##### 6.2.4.3.1 Case of network supporting the transport of tandem connection signals
+
+For the case of networks supporting the transport of tandem connection signals, the VC-n (n=3, 4) or VC-4-Xc supervisory-unequipped signal is a signal having an all "0"s in the higher order virtual
+
+container path signal label byte (C2) and the tandem connection monitoring byte (N1), a valid BIP-8 byte (B3), a valid path trace identifier byte (J1), and a valid path status byte (G1). The virtual container payload is unspecified. The content of the remaining path overhead bytes F2, H4, F3 and K3 is for further study.
+
+The VC-n (n=3, 4) supervisory-unequipped signal is an enhanced unequipped VC-n signal.
+
+For the case of networks supporting the transport of tandem connection signals, the VC-m (m=11, 12, 2) supervisory-unequipped signal is a signal having an all "0"s in the lower order virtual container path signal label (bits 5, 6, 7 of byte V5) and the tandem connection monitoring byte (N2), a valid BIP-2 (bits 1, 2 of byte V5), a valid path trace byte (J2), and valid path status (bits 3 and 8 of byte V5). The virtual container payload is unspecified. The content of the remaining path overhead bytes/bits V5 bit 4 and K4 is for further study.
+
+The VC-m (m=11, 12, 2) supervisory-unequipped signal is an enhanced unequipped VC-m signal.
+
+These signals indicate to downstream transport processing functions (refer to ITU-T Rec. G.803) that the virtual container is unoccupied, and sourced by a supervisory generator. Additional information on quality, source and status of the connection is available by means of the bit error, path trace and path status indications.
+
+Within a tandem connection, a supervisory-unequipped VC-n/VC-m signal generated before the tandem connection will have a valid (non all "0"s) tandem connection monitoring byte (N1, N2).
+
+##### **6.2.4.3.2 Case of network not supporting the transport of tandem connection signals**
+
+For the case of networks not supporting the transport of tandem connection signals, the VC-n (n=3, 4) or VC-4-Xc supervisory-unequipped signal is a signal having an all "0"s in the higher order virtual container path signal label byte (C2), a valid BIP-8 byte (B3), a valid path trace identifier byte (J1), and a valid path status byte (G1). The virtual container payload is unspecified. The content of the remaining path overhead bytes F2, H4, F3, K3 and N1 is for further study.
+
+For the case of networks not supporting the transport of tandem connection signals, the VC-m (m=11, 12, 2) supervisory-unequipped signal is a signal having an all "0"s in the lower order virtual container path signal label (bits 5, 6, 7 of byte V5), a valid BIP-2 (bits 1, 2 of byte V5), a valid path trace byte (J2), and valid path status (bits 3 and 8 of byte V5). The virtual container payload is unspecified. The content of the remaining path overhead bytes/bits V5 bit 4, N2 and K4 is for further study.
+
+## **6.3 Hierarchical bit rates**
+
+The zero level of the synchronous digital hierarchy shall be 51 840 kbit/s.
+
+The first level of the synchronous digital hierarchy shall be 155 520 kbit/s.
+
+Higher synchronous digital hierarchy bit rates shall be obtained as integer multiples of the first level bit rate and shall be denoted by the corresponding multiplication factor of the first level rate.
+
+The bit rates listed in Table 6-2 constitute the synchronous digital hierarchy.
+
+**Table 6-2 – SDH hierarchical bit rates**
+
+| Synchronous digital hierarchy level | Hierarchical bit rate (kbit/s) |
+|----------------------------------------------------------------------------|---------------------------------------|
+| 0 | 51 840 |
+| 1 | 155 520 |
+| 4 | 622 080 |
+| 16 | 2 488 320 |
+| 64 | 9 953 280 |
+| 256 | 39 813 120 |
+| NOTE – The specification of levels higher than 256 requires further study. | |
+
+## **6.4 Interconnection of STM-Ns**
+
+The SDH is designed to be universal, allowing transport of a large variety of signals including all those specified in ITU-T Rec. G.702. However, different structures can be used for the transport of virtual containers. The following interconnection rules will be used:
+
+- a) The rule for interconnecting two AUG-1s based upon two different types of administrative unit, namely AU-4 and AU-3, will be to use the AU-4 structure. Therefore, the AUG-1 based upon AU-3 will be demultiplexed to the VC-3 or TUG-2 level according to the type of the payload, and remultiplexed within an AUG-1 via the TUG-3/VC-4/AU-4 route. This is illustrated in Figures 6-9 a and 6-9 b.
+- b) The rule for interconnecting VC-11s transported via different types of tributary unit, namely TU-11 and TU-12, will be to use the TU-11 structure. This is illustrated in Figure 6-9 c. VC-11, TU-11 and TU-12 are described in the following clauses.
+- c) The rule for interconnecting concatenated VC-3s/4s transported via different types of concatenation, namely contiguous and virtual, will be to use the contiguous concatenation unless otherwise mutually agreed by the operators providing the transport.
+
+
+
+a) Interconnection of VC-3 with C-3 payload
+
+b) Interconnection of TUG-2
+
+c) Interconnection of VC-11
+
+G.707-Y.1322\_F6-9
+
+Three diagrams (a, b, c) showing SDH interconnection paths for different payloads. Diagram (a) shows VC-3 interconnection, (b) shows TUG-2 interconnection, and (c) shows VC-11 interconnection. Each diagram illustrates the multiplexing and demultiplexing stages between STM-N signals.
+
+**Figure 6-9 – Interconnection of STM-Ns**
+
+This SDH interconnection rule does not modify the interworking rules defined in ITU-T Rec. G.802 for networks based upon different plesiochronous digital hierarchies and speech encoding laws.
+
+## 6.5 Scrambling
+
+The STM-N (N=0, 1, 4, 16, 64, 256) signal must have sufficient bit timing content at the NNI. A suitable bit pattern, which prevents a long sequence of "1"s or "0"s is provided by using a scrambler.
+
+The STM-N (N=0, 1, 4, 16, 64, 256) signal shall be scrambled with a frame synchronous scrambler of sequence length 127 operating at the line rate.
+
+The generating polynomial shall be $1 + X^6 + X^7$ . Figure 6-10 gives a functional diagram of the frame synchronous scrambler.
+
+
+
+```
+
+graph LR
+ subgraph LFSR
+ FF1[D Q S] --> FF2[D Q S]
+ FF2 --> FF3[D Q S]
+ FF3 --> FF4[D Q S]
+ FF4 --> FF5[D Q S]
+ FF5 --> FF6[D Q S]
+ FF6 --> FF7[D Q S]
+ end
+ FF6 -- tap --> XOR1((+))
+ FF7 -- tap --> XOR1
+ XOR1 -- feedback --> FF1
+ FF7 --> XOR2((+))
+ DataIn[Data in] --> XOR2
+ XOR2 --> ScrambledOut[Scrambled data out]
+ Clock[STM-N clock] --> FF1 & FF2 & FF3 & FF4 & FF5 & FF6 & FF7
+ Pulse[Frame pulse] --> FF1 & FF2 & FF3 & FF4 & FF5 & FF6 & FF7
+
+```
+
+G.707-Y1322\_F6-10
+
+Figure 6-10 – Frame synchronous scrambler (functional diagram). The diagram shows a series of seven D flip-flops connected in a chain. Each flip-flop has a 'D' input, a 'Q' output, and an 'S' (set) input. The 'Q' output of one flip-flop is connected to the 'D' input of the next. The 'S' input of each flip-flop is connected to a common 'STM-N clock' line. A 'Frame pulse' is also connected to this common line. The output of the sixth and seventh flip-flops are connected to an XOR gate. The output of this XOR gate is fed back to the input of the first flip-flop. The output of the seventh flip-flop is also connected to another XOR gate, where it is combined with 'Data in' to produce 'Scrambled data out'.
+
+**Figure 6-10 – Frame synchronous scrambler
+(functional diagram)**
+
+The scrambler shall be reset to "1111111" on the most significant bit of the byte following the last byte of the first row of the STM-N SOH S (1,9,N). This bit, and all subsequent bits to be scrambled shall be added modulo 2 to the output from the $X^7$ position of the scrambler. The scrambler shall run continuously throughout the complete STM-N frame.
+
+The first row of the STM-N ( $N \leq 64$ ) SOH ( $9 \times N$ bytes, 3 bytes for STM-0, including the A1 and A2 framing bytes) shall not be scrambled.
+
+NOTE 1 – Care should be taken in selecting the binary content of the Z0 bytes and of the bytes reserved for national use which are excluded from the scrambling process of the STM-N signal to ensure that long sequences of "1"s or "0"s do not occur.
+
+For the first row of the STM-256 SOH bytes only S (1,3,193) [1,705] to S (1,4,64) [1,832] shall not be scrambled.
+
+NOTE 2 – The scrambler shall continue to run during the above-mentioned frame positions.
+
+NOTE 3 – Thus STM-256, SOH bytes S (1,1,1) [1,1] to S (1,3,192) [1,704] and S (1,4,65) [1,833] to S (1,9,256) [1,2304] shall be scrambled with the scrambler running from the reset in the previous STM-256 frame.
+
+NOTE 4 – For the unused bytes in row 1 of the STM-256 frame, a pattern should be used that provides sufficient transitions and no significant DC unbalance after scrambling.
+
+## 6.6 Physical specification of the NNI
+
+Specifications for physical electrical characteristics of the NNI are contained in ITU-T Rec. G.703.
+
+Specifications for physical optical characteristics of the NNI are contained in ITU-T Recs G.957 and G.691.
+
+# 7 Multiplexing method
+
+## 7.1 Multiplexing of administrative units into STM-N
+
+### 7.1.1 Multiplexing of administrative unit groups (AUGs) into STM-N
+
+#### 7.1.1.1 Multiplexing of AUG-N into STM-N, $N=(1, 4, 16, 64, 256)$
+
+The AUG-N is a structure of 9 rows by $N \times 261$ columns plus $N \times 9$ bytes in row 4 (for the AU-n pointers). The STM-N consists of an SOH as described in clause 9.2 and a structure of 9 rows by $N \times 261$ columns with $N \times 9$ bytes in row 4 (for the AU-n pointers). The AUG-N is multiplexed into this structure and has a fixed phase relationship with respect to the STM-N as shown in Figure 7-1.
+
+
+
+Figure 7-1: Multiplexing of AUG-N into STM-N. The diagram shows the structure of an STM-N frame. The total width is N x 261 columns. The first N x 9 columns are used for overhead. Rows 1-3 are RSOH (N x 9 bytes). Row 4 contains AU-n pointers (N x 9 bytes). Rows 5-9 are MSOH (N x 9 bytes). The remaining N x 261 columns are used for the AUG-N payload. The diagram is labeled G.707/Y.1322COR.1\_F7-1.
+
+Figure 7-1 – Multiplexing of AUG-N into STM-N
+
+#### 7.1.1.2 Multiplexing of AUG-Ns into AUG-4xN
+
+The arrangement of 4 AUG-Ns multiplexed into the AUG-4xN is shown in Figure 7-2. The AUG-N is a structure of 9 rows by $N \times 261$ columns plus $N \times 9$ bytes in row 4 (for the AU-n pointers). The 4 AUG-Ns are block interleaved into the AUG-4xN structure with a block length of N bytes. The AUG-Ns have a fixed phase relationship with respect to the AUG-4xN.
+
+
+
+Figure 7-2: Multiplexing of 4 AUG-Ns into AUG-4xN. The diagram shows four AUG-N blocks, labeled #1, #2, #3, and #4. Each block has a width of N x 261 columns and 9 rows. The first N x 9 columns of each block are overhead. The remaining N x 261 columns are payload. The four blocks are interleaved into a single AUG-4xN structure. The interleaving is shown by dashed lines connecting blocks #1, #2, #3, and #4. The resulting AUG-4xN structure has a total width of 4 x N x 261 columns and a total height of 4 x N x 9 rows. The diagram is labeled G.707/Y.1322COR.1\_F7-2.
+
+Figure 7-2 – Multiplexing of 4 AUG-Ns into AUG-4xN
+
+### 7.1.2 Multiplexing of an AU-4 via AUG-1
+
+The multiplexing arrangement of a single AU-4 via the AUG-1 is depicted in Figure 7-3. The 9 bytes at the beginning of row 4 are allocated to the AU-4 pointer. The remaining 9 rows by 261 columns is allocated to the virtual container-4 (VC-4). The phase of the VC-4 is not fixed with respect to the AU-4. The location of the first byte of the VC-4 with respect to the AU-4 pointer is given by the pointer value. The AU-4 is placed directly in the AUG-1.
+
+
+
+The diagram illustrates the multiplexing of an AU-4 via AUG-1. It shows three stacked frames: VC-4, AU-4, and AUG-1. The VC-4 frame is a 9x261 grid of bytes, with the first 9 bytes of row 4 being the VC-4 POH (J1, B3, C2, G1, F2, H4, F3, K3, N1). The AU-4 frame is a 9x261 grid of bytes, with the first 9 bytes of row 4 being the AU-4 pointer (H1, Y, Y, H2, 1\*, 1\*, H3, H3, H3). The AUG-1 frame is a 9x261 grid of bytes. The VC-4 is mapped into the AUG-1, with the VC-4 POH being mapped into the AU-4 POH. The diagram also shows the 'Floating phase' and 'Fixed phase' of the VC-4. The AU-4 pointer is shown as a sequence of bytes: H1 Y Y H2 1\* 1\* H3 H3 H3. The VC-4 POH is shown as a sequence of bytes: J1 B3 C2 G1 F2 H4 F3 K3 N1. The legend indicates that 1\* is an All 1s byte and Y is 1001 SS11 (S bits are unspecified). The diagram is labeled G.707-Y.1322\_F7-3.
+
+Diagram illustrating the multiplexing of an AU-4 via AUG-1. It shows the structure of the VC-4, AU-4, and AUG-1 frames. The VC-4 is a 9x261 grid of bytes. The AU-4 is a 9x261 grid of bytes, with the first 9 bytes of row 4 being the AU-4 pointer. The AUG-1 is a 9x261 grid of bytes. The diagram shows the VC-4 being mapped into the AUG-1, with the VC-4 POH (Virtual Container-4 Path Overhead) being mapped into the AU-4 POH. The VC-4 is shown as a shaded grid of 9 rows and 261 columns. The AU-4 is shown as a grid of 9 rows and 261 columns, with the first 9 bytes of row 4 being the AU-4 pointer. The AUG-1 is shown as a grid of 9 rows and 261 columns. The diagram also shows the 'Floating phase' and 'Fixed phase' of the VC-4. The AU-4 pointer is shown as a sequence of bytes: H1 Y Y H2 1\* 1\* H3 H3 H3. The VC-4 POH is shown as a sequence of bytes: J1 B3 C2 G1 F2 H4 F3 K3 N1. The legend indicates that 1\* is an All 1s byte and Y is 1001 SS11 (S bits are unspecified).
+
+1\* All 1s byte
+
+Y 1001 SS11 (S bits are unspecified)
+
+Figure 7-3 – Multiplexing of AU-4 via AUG-1
+
+### 7.1.3 Multiplexing of AU-3s via AUG-1
+
+The multiplexing arrangement of three AU-3s via the AUG-1 is depicted in Figure 7-4. The 3 bytes at the beginning of row 4 are allocated to the AU-3 pointer. The remaining 9 rows by 87 columns is allocated to the VC-3 and two columns of fixed stuff. The bytes in each row of the two columns of fixed stuff of each AU-3 shall be the same. The phase of the VC-3 and the two columns of fixed stuff is not fixed with respect to the AU-3. The location of the first byte of the VC-3 with respect to the AU-3 pointer is given by the pointer value. The three AU-3s are one-byte interleaved in the AUG-1.
+
+
+
+The diagram illustrates the multiplexing of three AU-3s (A, B, and C) into a single AUG-1 frame. Each AU-3 is shown as a block containing a VC-3 plus two columns of fixed stuff. The VC-3 POH is indicated, and the floating phase is shown. The AUG-1 frame is shown as a sequence of bytes A, B, C, A, B, C, A, B, C, with the first three bytes (A, B, C) being the AU-3 pointer. The diagram also includes column numbers (1, 29, 30, 31, 58, 59, 60, 87) and row labels (J1, B3, C2, G1, F2, H4, F3, K3, N1). The text 'VC-3 plus 2 columns of fixed stuff' is on the right, and 'Three AU-3' and 'One-byte interleaved fixed phase' are also present. The source 'G.707-Y.1322\_F7-4' is noted at the bottom right.
+
+Diagram illustrating the multiplexing of three AU-3s via AUG-1. The diagram shows three AU-3 structures (A, B, and C) being interleaved into a single AUG-1 frame. Each AU-3 contains a VC-3 plus two columns of fixed stuff. The VC-3 POH is shown, and the floating phase is indicated. The AUG-1 frame is shown as a sequence of bytes A, B, C, A, B, C, A, B, C, with the first three bytes (A, B, C) being the AU-3 pointer. The diagram also includes column numbers (1, 29, 30, 31, 58, 59, 60, 87) and row labels (J1, B3, C2, G1, F2, H4, F3, K3, N1).
+
+NOTE – The byte in each row of the two columns of fixed stuff of each AU-3 shall be the same.
+
+Figure 7-4 – Multiplexing of AU-3s via AUG-1
+
+### 7.1.4 Multiplexing of AU-3 into STM-0
+
+The AU-3 is a structure of 9 rows by 87 columns plus 3 bytes in row 4 (for the AU-3 pointers). The STM-0 consists of an SOH as described in clause 9.2 and a structure of 9 rows by 87 columns with 3 bytes in row 4 (for the AU-3 pointers). The AU-3 is multiplexed into this structure and has a fixed phase relationship with respect to the STM-0 as shown in Figure 7-5.
+
+
+
+The diagram illustrates the mapping of an AU-3 into an STM-0 frame. The top portion shows a VC-3 plus two columns of fixed stuff, with columns 1, 29, 30, 31, 58, 59, 60, and 87 explicitly labeled. Rows are labeled J1, B3, C2, G1, F2, H4, F3, K3, N1. An arrow labeled 'VC-3 POH' points to the start of the VC-3 structure, and another arrow labeled 'Floating phase' points to the AU-3 structure. The bottom portion shows the STM-0 structure with RSOH, HI H2 H3, and MSOH sections, and a large AU-3 payload. The label 'G.707-Y1322\_F7-5' is in the bottom right corner.
+
+Diagram showing the multiplexing of AU-3 into STM-0. The top part shows a VC-3 plus 2 columns of fixed stuff, with columns 1, 29, 30, 31, 58, 59, 60, and 87 labeled. Rows are labeled J1, B3, C2, G1, F2, H4, F3, K3, N1. An arrow labeled 'VC-3 POH' points to the start of the VC-3 structure, and another arrow labeled 'Floating phase' points to the AU-3 structure. The bottom part shows the STM-0 structure with RSOH, HI H2 H3, and MSOH sections, and a large AU-3 payload. The label 'G.707-Y1322\_F7-5' is in the bottom right corner.
+
+NOTE – The byte in each row of the two columns of fixed stuff of each AU-3 shall be the same.
+
+**Figure 7-5 – Multiplexing of AU-3 into STM-0**
+
+## 7.2 Multiplexing of tributary units into VC-4 and VC-3
+
+### 7.2.1 Multiplexing of tributary unit group-3s (TUG-3s) into a VC-4
+
+The arrangement of three TUG-3s multiplexed in the VC-4 is shown in Figure 7-6. The TUG-3 is a 9-row by 86-column structure. The VC-4 consists of one column of VC-4 POH, two columns of fixed stuff and a 258-column payload structure. The three TUG-3s are single byte interleaved into the 9-row by 258-column VC-4 payload structure and have a fixed phase with respect to the VC-4.
+
+As described in clause 7.1, the phase of the VC-4 with respect to the AU-4 is given by the AU-4 pointer.
+
+
+
+Diagram showing the multiplexing of three TUG-3s (A, B, and C) into a VC-4. Each TUG-3 is 86 columns wide. The VC-4 payload is 258 columns wide, formed by single-byte interleaving of the three TUG-3s. The VC-4 structure includes 1 column of VC-4 POH, 2 columns of fixed stuff, and the 258-column payload. The interleaving pattern is shown as A B C A B C A ... for the first 10 columns of the payload. The diagram is labeled G.707-Y.1322\_F7-6.
+
+Figure 7-6 – Multiplexing of three TUG-3s into a VC-4
+
+### 7.2.2 Multiplexing of a TU-3 via TUG-3
+
+The multiplexing of a single TU-3 via the TUG-3 is depicted in Figure 7-7. The TU-3 consists of the VC-3 with a 9-byte VC-3 POH and the TU-3 pointer. The first column of the 9-row by 86-column TUG-3 is allocated to the TU-3 pointer (bytes H1, H2, H3) and fixed stuff. The phase of the VC-3 with respect to the TUG-3 is indicated by the TU-3 pointer.
+
+
+
+Diagram showing the multiplexing of a TU-3 via a TUG-3. The TUG-3 is 86 columns wide. The first column contains the TU-3 pointer (H1, H2, H3) and fixed stuff. The remaining 85 columns contain the TU-3, which consists of the VC-3 (85 columns) and the VC-3 POH (1 column). The VC-3 is shown as a shaded area labeled 'Container-3'. The diagram is labeled G.707-Y.1322\_F7-7.
+
+Figure 7-7 – Multiplexing of a TU-3 via a TUG-3
+
+### 7.2.3 Multiplexing of TUG-2s via a TUG-3
+
+The multiplexing structure for the TUG-2 via the TUG-3 is depicted in Figure 7-8. The TUG-3 is a 9-row by 86-column structure with the first two columns of fixed stuff.
+
+
+
+The diagram illustrates the internal structure of a TUG-3 frame, which is 86 columns wide. The first two columns are designated as 'Fixed stuff'. The remaining 84 columns are used for multiplexing seven TUG-2s. Each TUG-2 consists of a TU-2 PTR, a POH, and a VC-2. The diagram shows the first TUG-2 and the last TUG-2 (TU-11/12 PTRs). The total capacity is 3 VC-12s or 4 VC-11s in 1 × TUG-2.
+
+86 columns
+
+TUG-2
+
+TUG-2
+
+TUG-3
+(7 × TUG-2)
+
+Fixed stuff
+
+TU-2 PTR
+
+POH
+
+VC-2
+
+TU-11/12 PTRs
+
+POH
+
+VC-11/12
+
+3 VC-12s or 4 VC-11s
+in 1 × TUG-2
+
+PTR Pointer
+
+Diagram of TUG-3 structure showing the multiplexing of seven TUG-2s. The TUG-3 is 86 columns wide. The first two columns are 'Fixed stuff'. The remaining 84 columns are divided into seven TUG-2s. Each TUG-2 contains a TU-2 PTR, a POH, and a VC-2. The diagram shows the first TUG-2 and the last TUG-2 (TU-11/12 PTRs). The total capacity is 3 VC-12s or 4 VC-11s in 1 x TUG-2.
+
+G.707/Y.1322COR.1\_F7-8
+
+Figure 7-8 – Multiplexing of seven TUG-2s via a TUG-3
+
+A group of seven TUG-2s can be multiplexed via the TUG-3.
+
+The arrangement of seven TUG-2s multiplexed via the TUG-3 is depicted in Figure 7-9. The TUG-2s are one-byte interleaved in the TUG-3.
+
+
+
+Diagram showing the multiplexing of seven TUG-2s into a TUG-3. The TUG-3 is a long horizontal bar with 86 slots. The first two slots are labeled 'Fixed stuff'. Slots 3 through 86 are divided into seven groups of 12 slots each, labeled (1) through (7). Each group contains 7 bytes of data from a TUG-2, interleaved with 5 bytes of fixed stuff. Above each group (1) through (7) is a TUG-2 block. Above the first TUG-2 is TU-11 (3 slots), above the second is TU-12 (3 slots), and above the third is TU-2 (7 slots). Dashed lines show the mapping of bytes from the TUG-2s into the TUG-3 slots. The TUG-3 slots are numbered 1 to 86, with 1 and 2 being 'Fixed stuff', and 3-86 being data slots. The data slots are further subdivided into 7-byte chunks labeled 1 through 7 within each of the seven groups.
+
+G.707-Y.1322\_F7-9
+
+Figure 7-9 – Multiplexing of seven TUG-2s via a TUG-3
+
+### 7.2.4 Multiplexing of TUG-2s into a VC-3
+
+The multiplexing structure for TUG-2s into a VC-3 is depicted in Figure 7-10. The VC-3 consists of VC-3 POH and a 9-row by 84-column payload structure. A group of seven TUG-2s can be multiplexed into the VC-3.
+
+
+
+The diagram illustrates the internal structure of a VC-3. The total width is 85 columns. On the far left, a vertical strip represents the VC-3 POH. Next to it is a TU-2 PTR block. The main payload area contains multiple VC-2 blocks, each with its own POH. There are ellipses indicating more VC-2 blocks. On the right side, there is a TU-11/12 PTR block, followed by more VC-11/12 blocks, each with its own POH. The rightmost part of the VC-3 is another vertical strip for the VC-3 POH. Above the diagram, a bracket labeled 'TUG-2' spans a portion of the payload. Another bracket labeled 'VC-3 (7 × TUG-2)' spans the entire 85-column width. Below the right side, a bracket indicates that one TUG-2 contains '3 VC-12s or 4 VC-11s'. A legend at the bottom left defines 'PTR Pointer'. A reference code 'G.707/Y.1322COR.1\_F7-10' is at the bottom right.
+
+Diagram showing the multiplexing of seven TUG-2s into a VC-3. The VC-3 has 85 columns. It contains TU-2 PTR, TU-11/12 PTR, POH, VC-2, and VC-11/12. A TUG-2 contains 3 VC-12s or 4 VC-11s.
+
+Figure 7-10 – Multiplexing of seven TUG-2s into a VC-3
+
+The arrangement of seven TUG-2s multiplexed into the VC-3 is depicted in Figure 7-11. The TUG-2s are one-byte interleaved in the VC-3. An individual TUG-2 has a fixed location in the VC-3 frame.
+
+
+
+Diagram illustrating the arrangement of seven TUG-2s multiplexed into a VC-3 frame. The diagram shows the hierarchy from TU-11, TU-12, and TU-2 down to TUG-2, and finally to the VC-3 frame. The VC-3 frame is shown as a long horizontal bar with columns numbered 1 to 85. The first column is labeled 'VC POH'. The remaining columns are grouped into seven TUG-2s, labeled (1) through (7). Each TUG-2 contains 12 columns, with bytes numbered 1 through 7. The bytes are interleaved across the TUG-2s. The diagram also shows the internal structure of the TUG-2s, with TU-11s and TU-12s being one-byte interleaved within them. The TU-2s are shown as a single block of 12 columns. The VC-3 frame is shown as a single block of 85 columns. The bytes are numbered 1 through 7 within each TUG-2. The VC POH is shown as a shaded column at the beginning of the VC-3 frame. The columns are numbered 1 to 85, with an ellipsis between 9 and 83. The bytes are numbered 1 through 7 within each TUG-2. The VC POH is shown as a shaded column at the beginning of the VC-3 frame. The columns are numbered 1 to 85, with an ellipsis between 9 and 83.
+
+G.707-Y.1322\_F7-11
+
+**Figure 7-11 – Arrangement of seven TUG-2s multiplexed into a VC-3**
+
+### 7.2.5 Multiplexing of a TU-2 via TUG-2s
+
+The multiplexing arrangement of a single TU-2 via the TUG-2 is depicted in Figure 7-11.
+
+### 7.2.6 Multiplexing of TU-11s or TU-12s via TUG-2s
+
+The multiplexing arrangements of four TU-11s or three TU-12s via the TUG-2 are depicted in Figure 7-11. The TU-11s/TU-12s are one-byte interleaved in the TUG-2.
+
+## 7.3 AU-n/TU-n numbering scheme
+
+An STM-N frame comprises $N \times 270$ columns (numbered 1 to $N \times 270$ ). The first $N \times 9$ columns contain the SOH and AU-4/AU-4-Xc pointer(s) with the remaining $N \times 261$ columns containing the higher order data payload (higher order tributaries).
+
+The higher order payload columns may be addressed by means of a two (B,A), three (C,B,A), four (D,C,B,A) or five (E,D,C,B,A) figure address, where A represents the AU-3 number, B the AUG-1 number, C the AUG-4 number, D the AUG-16 number and E the AUG-64 number. Refer to Figures 7-12 to 7-25.
+
+In the case of an AU-4 structured frame, the payload columns may be addressed by means of a three figure address (K, L, M) where K represents the TUG-3 number, L the TUG-2 number, and M the TU-11/TU-12 number. Refer to Figures 7-27 and 7-28 and Table 7-1. In the case of an AU-3 structured frame, only L and M coordinates are used. Refer to Figure 7-29 and Table 7-2.
+
+In order to provide a simple and convenient means of determining the total tributary capacity, i.e., the number of lower order tributaries provided, the payload columns are allocated a time slot number. The number of time slots per tributary in each frame is determined by the payload configuration.
+
+AU time slots (TS) are numbered from left to right in the STM-N as shown in Figures 7-12 to 7-26. TU time slots (TS) are numbered from left to right in the VC-4/VC-3 as shown in Figures 7-27 to 7-29.
+
+AUs and TUs can either be numbered in a sequential hierarchy, indicated in Figures 7-12 to 7-29 by "time slot number", or by using the multiplex hierarchy, indicated in Figures 7-12 to 7-29 by "address".
+
+For example, an STM-256 can comprise 64 AU-4-4c numbered 1 to 64, where AU-4-4c with time slot number 17 has address (2, 1, 1, 0, 0) and a VC-4 can comprise 63 TU-12 numbered 1 to 63, where TU-12 with time slot number 17 has address (2, 6, 1).
+
+### **7.3.1 Numbering of AU-ns (VC-ns) in an STM-256**
+
+The STM-256 can comprise four AUG-64s, which shall be numbered #1 to #4:
+
+- AUG-64 #1 is accommodated in columns 1...64, 257...320, 513...576, etc., of the STM-256;
+- AUG-64 #2 is accommodated in columns 65...128, 321...384, 577...640, etc., of the STM-256;
+- AUG-64 #3 is accommodated in columns 129...192, 385...448, 641...704, etc., of the STM-256;
+- AUG-64 #4 is accommodated in columns 193...256, 449...512, 705...768, etc., of the STM-256.
+
+Each AUG-64 can comprise four AUG-16s, which shall be numbered #1 to #4. Each AUG-16 can comprise four AUG-4s, which shall be numbered #1 to #4. Each AUG-4 can comprise four AUG-1s, which shall be numbered #1 to #4. Each AUG-1 can comprise three AU-3s, which shall be numbered #1 to #3.
+
+#### 7.3.1.1 Numbering of AU-4s (VC-4s) in an STM-256
+
+Any AU-4 can be allocated a number in the form #E, #D, #C, #B, #A, where E designates the AUG-64 number (1 to 4), D designates the AUG-16 number (1 to 4), C designates the AUG-4 number (1 to 4), B designates the AUG-1 number (1 to 4), and A is always 0, see Figure 7-12. The location of the columns in the STM-256 occupied by AU-4 (E,D,C,B,0) is given by:
+
+$$X\text{th column} = 1 + 64 \times [E-1] + 16 \times [D-1] + 4 \times [C-1] + [B-1] + 256 \times [X-1] \quad \text{for } X = 1 \text{ to } 270.$$
+
+Therefore, AU-4 (1,1,1,1,0) resides in columns 1, 257, 513, 769, ... 68 865 of the STM-256, and AU-4 (4,4,4,4,0) resides in columns 256, 512, 768, ..., 69 120 of the STM-256.
+
+
+
+The figure illustrates the mapping of AU-4s to columns in an STM-256 frame. It consists of a large grid of columns. The top row is labeled 'STM-N column number' and contains values 1 through 9. Below this is the 'Time slot number' row, which contains values 1 through 9, followed by a repeating sequence of 0 through 9. The bottom section is labeled 'Address' and contains five rows: E, D, C, B, and A. The columns are grouped by AU-4 addresses (E,D,C,B,A). The right side of the figure shows a continuation of the grid, with a vertical label '69120' indicating the total number of columns. A small table on the far right shows the values 2, 5, 2, 4, 4, 4, 0, which correspond to the address rows E, D, C, B, A for a specific AU-4. The label 'G.707-Y.1322\_F7-12' is at the bottom right.
+
+Figure 7-12: AU-4 numbering scheme within an STM-256's AU pointer row and payload columns. The diagram shows a grid of columns and rows. The top row is labeled 'STM-N column number' with values 1-9. The next row is 'Time slot number' with values 1-9, followed by a repeating sequence of 0-9. The bottom section is 'Address' with rows E, D, C, B, and A. Columns are grouped by AU-4 addresses (E,D,C,B,A). The right side shows a continuation of the grid with a vertical label '69120' and a small table with values 2, 5, 2, 4, 4, 4, 0. A label 'G.707-Y.1322\_F7-12' is at the bottom right.
+
+**Figure 7-12 – AU-4 numbering scheme within an STM-256's AU pointer row and payload columns**
+
+#### 7.3.1.2 Numbering of AU-3s (VC-3s) in an STM-256
+
+Any AU-3 can be allocated a number in the form #E, #D, #C, #B, #A, where E designates the AUG-64 number (1 to 4), D designates the AUG-16 number (1 to 4), C designates the AUG-4 number (1 to 4), B designates the AUG-1 number (1 to 4), and A designates the AU-3 number (1 to 3), see Figure 7-13. The location of the columns in the STM-256 occupied by AU-3 (E,D,C,B,A) is given by:
+
+$$X\text{th column} = 1 + 64 \times [E-1] + 16 \times [D-1] + 4 \times [C-1] + [B-1] + 256 \times [A-1] + 768 \times [X-1] \quad \text{for } X = 1 \text{ to } 90.$$
+
+Therefore, AU-3 (1,1,1,1,1) resides in columns 1, 769, 1537, 2305, ... 68 353 of the STM-256, and AU-3 (4,4,4,4,3) resides in columns 768, 1536, 2304, ... 69 120 of the STM-256.
+
+
+
+Figure 7-13: AU-3 numbering scheme within an STM-256's AU pointer row and payload columns. The diagram shows a grid of columns and rows. The top row is labeled 'STM-N column number' with values 1 to 9. The second row is labeled 'Time slot number' with values 1 to 9, followed by a repeating pattern of 0-9. The third row is labeled 'Address' with sub-rows E, D, C, B, and A. The grid contains a repeating pattern of numbers 1-9. On the right side, there is a vertical column of numbers 69120, 77777, 66666, 45678, 44444, 44444, 34444, 41234, 33333. A dashed line separates the main grid from the right-side numbers. The bottom right corner has the text G.707-Y.1322\_F7-13.
+
+**Figure 7-13 – AU-3 numbering scheme within an STM-256's AU pointer row and payload columns**
+
+#### 7.3.1.3 Numbering of AU-4-4cs (VC-4-4cs) in an STM-256
+
+Any AU-4-4c can be allocated a five-figure address in the form #E, #D, #C, #B, #A, where E designates the AUG-64 number (1 to 4), D designates the AUG-16 number (1 to 4), C designates the AUG-4 number (1 to 4), B and A are always 0, see Figure 7-14. The location of the columns in the STM-256 occupied by AU-4-4c (E,D,C,0,0) is given by:
+
+$$X\text{th column} = [X \bmod 4] + 64 \times [E-1] + 16 \times [D-1] + 4 \times [C-1] + 256 \times [X \text{ DIV } 4] \quad \text{for } X = 1 \text{ to } 1080.$$
+
+Therefore, AU-4-4c (1,1,1,0,0) resides in columns 1,2,3,4, 257,258,259,260, 513,514,515,516, ... 68 865,68 866,68 867,68 868 of the STM-256, and AU-4-4c (4,4,4,0,0) resides in columns 253,254,255,256, 509,510,511,512, 765,766,767,768, ... 69 117,69 118,69 119,69 120 of the STM-256.
+
+
+
+**Figure 7-14 – AU-4-4c numbering scheme within an STM-256's AU pointer row and payload columns**
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------|---|---|---|---|---|---|---|---|---|---|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|-------|-------|-------|-------|-------|-------|--|--|
+| STM-N column number | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | | | | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | 75 | 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | 88 | | 69117 | 69118 | 69119 | 69120 | | |
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Time slot number | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | | 16 | 17 | 17 | 17 | 17 | 18 | 18 | 18 | 18 | 19 | 19 | 19 | 19 | 20 | 20 | 20 | 20 | 21 | 21 | 21 | 21 | 22 | 22 | 22 | 22 | | 17280 | 17280 | 17280 | 17280 | | | | |
+| Address | E | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | | 4 | 4 | 4 | 4 | | | |
+| | D | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | | 1 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | | 4 | 4 | 4 | 4 | | | |
+| | C | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | | 4 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | 3 | 3 | 3 | 4 | 4 | 4 | 4 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | | 4 | 4 | 4 | 4 | | | |
+| | B | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 0 | 0 | 0 | 0 | | | |
+| | A | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 0 | 0 | 0 | 0 | | | |
+
+G.707-Y1322\_F7-14
+
+Figure 7-14 – AU-4-4c numbering scheme within an STM-256's AU pointer row and payload columns
+
+31 ITU-T Rec. G.707/Y.1322 (01/2007)
+
+#### 7.3.1.4 Numbering of AU-4-16cs (VC-4-16cs) in an STM-256
+
+Any AU-4-16c can be allocated a five-figure address in the form #E, #D, #C, #B, #A, where E designates the AUG-64 number (1 to 4), D designates the AUG-16 number (1 to 4), C, B and A are always 0, see Figure 7-15. The location of the columns in the STM-256 occupied by AU-4-16c (E,D,0,0,0) is given by:
+
+$$\text{Xth column} = [X \bmod 16] + 64 \times [E-1] + 16 \times [D-1] + 256 \times [X \text{ DIV } 16] \quad \text{for } X = 1 \text{ to } 4320.$$
+
+Therefore, AU-4-16c (1,1,0,0,0) resides in columns 1...16, 257...272, ..., 68 865...68 880 of the STM-256, and AU-4-16c (4,4,0,0,0) resides in columns 241...256, 497...512, ..., 69 105...69 120 of the STM-256.
+
+
+
+| | | | | | | | | | | | | |
+|---------------------|---|---|---|---|---|---|---|---|---|---|-----|-------|
+| STM-N column number | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | ... | 69120 |
+| Time slot number | | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ... | 16 |
+| Address | E | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ... | 4 |
+| | D | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ... | 4 |
+| | C | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ... | 0 |
+| | B | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ... | 0 |
+| | A | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ... | 0 |
+
+**Figure 7-15 – AU-4-16c numbering scheme within an STM-256's AU pointer row and payload columns**
+
+Figure 7-15 – AU-4-16c numbering scheme within an STM-256's AU pointer row and payload columns
+
+32 ITU-T Rec. G.707/Y.1322 (01/2007)
+
+#### 7.3.1.5 Numbering of AU-4-64cs (VC-4-64cs) in an STM-256
+
+Any AU-4-64c can be allocated a five-figure address in the form #E, #D, #C, #B, #A, where E designates the AUG-64 number (1 to 4), D, C, B and A are always 0, see Figure 7-16. The location of the columns in the STM-256 occupied by AU-4-64c (E,0,0,0,0) is given by:
+
+$$\text{Xth column} = [\text{X mod } 64] + 64 \times [\text{E}-1] + 256 \times [\text{X DIV } 64] \quad \text{for X = 1 to 17 280.}$$
+
+Therefore, AU-4-16c (1,0,0,0,0) resides in columns 1...64, 257...321, ..., 68 865...68 928 of the STM-256, and AU-4-16c (4,0,0,0,0) resides in columns 193...256, 449...512, ..., 69 057...69 120 of the STM-256.
+
+
+
+Figure 7-16: AU-4-64c numbering scheme within an STM-256's AU pointer row and payload columns. The diagram shows a grid of columns and rows. The top row is labeled 'STM-N column number' with values 1 to 9. The second row is labeled 'Time slot number' with values 1 to 22. The third row is labeled 'Address' with sub-columns E, D, C, B, and A. The E sub-column contains '1' for columns 1-16, '2' for columns 17-32, and '4' for columns 65-80. The D, C, B, and A sub-columns are all '0'. A dashed line on the right indicates a jump to column 69120, where the values for E, D, C, B, and A are 4, 0, 0, 0, and 0 respectively. The text 'G.707-Y.1322\_F7-16' is at the bottom right.
+
+Figure 7-16 – AU-4-64c numbering scheme within an STM-256's AU pointer row and payload columns
+
+#### 7.3.1.6 Numbering of an AU-4-256c in an STM-256
+
+There is one AU-4-256c in an STM-256 signal. This signal does not need a number, but can be referred to as (0,0,0,0,0).
+
+### 7.3.2 Numbering of AU-ns (VC-ns) in an STM-64
+
+The STM-64 can comprise four AUG-16s, which shall be numbered #1 to #4:
+
+- AUG-16 #1 is accommodated in columns 1...16, 65...80, 129...144, etc., of the STM-64;
+- AUG-16 #2 is accommodated in columns 17...32, 81...96, 145...160, etc., of the STM-64;
+- AUG-16 #3 is accommodated in columns 33...48, 97...112, 161...176, etc., of the STM-64;
+- AUG-16 #4 is accommodated in columns 49...64, 113...128, 177...192, etc., of the STM-64.
+
+Each AUG-16 can comprise four AUG-4s, which shall be numbered #1 to #4. Each AUG-4 can comprise four AUG-1s, which shall be numbered #1 to #4. Each AUG-1 can comprise three AU-3s, which shall be numbered #1 to #3.
+
+#### 7.3.2.1 Numbering of AU-4s (VC-4s) in an STM-64
+
+Any AU-4 can be allocated a number in the form #D, #C, #B, #A, where D designates the AUG-16 number (1 to 4), C designates the AUG-4 number (1 to 4), B designates the AUG-1 number (1 to 4), and A is always 0, see Figure 7-17. The location of the columns in the STM-64 occupied by AU-4 (D,C,B,0) is given by:
+
+$$X\text{th column} = 1 + 16 \times [D-1] + 4 \times [C-1] + [B-1] + 64 \times [X-1] \quad \text{for } X = 1 \text{ to } 270.$$
+
+Therefore, AU-4 (1,1,1,0) resides in columns 1, 65, 129, 193, ... 17 217 of the STM-64, and AU-4 (4,4,4,0) resides in columns 64, 128, 192, ..., 17 280 of the STM-64.
+
+
+
+Figure 7-17: AU-4 numbering scheme within an STM-64's AU pointer row and payload columns. The diagram shows a grid of columns and rows. The top row is labeled 'STM-N column number' with values 1 to 9. The second row is labeled 'Time slot number' with values 1 to 8, followed by a repeating sequence of 0-9. The bottom section is labeled 'Address' and contains four rows: D, C, B, and A. Row D shows the AUG-16 number (1-4) repeating. Row C shows the AUG-4 number (1-4) repeating. Row B shows the AUG-1 number (1-4) repeating. Row A shows '0' for all columns. On the right, a vertical label '17280' is present. A small table on the far right shows a snippet of the pattern for columns 17276-17280.
+
+G.707-Y.132\_F7-17
+
+**Figure 7-17 – AU-4 numbering scheme within an STM-64's AU pointer row and payload columns**
+
+#### 7.3.2.2 Numbering of AU-3s (VC-3s) in an STM-64
+
+Any AU-3 can be allocated a number in the form #D, #C, #B, #A, where D designates the AUG-16 number (1 to 4), C designates the AUG-4 number (1 to 4), B designates the AUG-1 number (1 to 4), and A designates the AU-3 number (1 to 3), see Figure 7-18. The location of the columns in the STM-64 occupied by AU-3 (D, C, B, A) is given by:
+
+$$X\text{th column} = 1 + 16 \times [D-1] + 4 \times [C-1] + [B-1] + 64 \times [A-1] + 192 \times [X-1] \quad \text{for } X = 1 \text{ to } 90.$$
+
+Therefore, AU-3 (1,1,1,1) resides in columns 1, 193, 385, 577, ... 17 089 of the STM-64, and AU-3 (4,4,4,3) resides in columns 192, 384, 576 ..., 17 280 of the STM-64.
+
+
+
+Figure 7-18: AU-3 numbering scheme within an STM-64's AU pointer row and payload columns. The diagram shows a grid of columns and rows. The top row is labeled 'STM-N column number' with values 1 to 9. The second row is labeled 'Time slot number' with values 1 to 9 followed by a repeating sequence of 0-9. The third row is labeled 'Address' and contains four sub-rows labeled D, C, B, and A. The D row shows a repeating pattern of 1s and 2s. The C row shows a repeating pattern of 1s, 2s, 3s, and 4s. The B row shows a repeating pattern of 1, 2, 3, 4. The A row shows a repeating pattern of 1s and 2s. On the right side, there is a vertical column of numbers 17280, and a small grid showing the last few columns (17089 to 17280) with corresponding values for the D, C, B, and A rows. The source code G.707-Y.1322\_F7-18 is noted at the bottom right.
+
+**Figure 7-18 – AU-3 numbering scheme within an STM-64's AU pointer row and payload columns**
+
+### 7.3.2.3 Numbering of AU-4-4cs (VC-4-4cs) in an STM-64
+
+Any AU-4-4c can be allocated a four-figure address in the form #D, #C, #B, #A, where D designates the AUG-16 number (1 to 4), C designates the AUG-4 number (1 to 4), B and A are always 0, see Figure 7-19. The location of the columns in the STM-64 occupied by AU-4-4c (D,C,0,0) is given by:
+
+$Xth\ column = [X\bmod 4] + 16 \times [D-1] + 4 \times [C-1] + 64 \times [X\operatorname{DIV} 4]$ for X = 1 to 1080.
+
+Therefore, AU-4-4c (1,1,0,0) resides in columns 1,2,3,4,65,66,67,68,129,130,131,132, ..., 17 217, 17 218, 17 219, 17 220 of the STM-64, and AU-4-4c (4, 4, 0, 0) resides in columns 61,62,63,64,125, 126,127,128, ..., 17 277, 17 278, 17 279, 17 280 of the STM-64.
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-----------------------------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|-------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|
+| STM-N column number | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 65 | | | | | | 17280 | | | | | |
+| Time slot number | 0 1 | 0 2 | 0 3 | 0 4 | 0 5 | 0 6 | 0 7 | 0 8 | 0 9 | 1 0 | 1 1 | 1 2 | 1 3 | 1 4 | 1 5 | 1 6 | 1 7 | 1 8 | 1 9 | 2 0 | 2 1 | 2 2 | 2 3 | 2 4 | 2 5 | 2 6 | 2 7 | 2 8 | 2 9 | 3 0 | 3 1 | 3 2 | 3 3 | 3 4 | 3 5 | 3 6 | 3 7 | 3 8 | 3 9 | 4 0 | 4 1 | 4 2 | 4 3 | 4 4 | 4 5 | 4 6 | 4 7 | 4 8 | 4 9 | 5 0 | 5 1 | 5 2 | 5 3 | 5 4 | 5 5 | 5 6 | 5 7 | 5 8 | 5 9 | 6 0 | 6 1 | 6 2 | 6 3 | 6 4 | 6 5 | 6 6 | 6 7 | 6 8 | 6 9 | 7 0 | | 1 7 2 7 6 | 1 7 2 7 7 | 1 7 2 7 8 | 1 7 2 7 9 | 1 7 2 8 0 |
+| Address D C B A | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 1 | 1 | 1 | 1 | 1 | | 4 | 4 | 4 | 4 | 4 | |
+| | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | 3 | 3 | 3 | 4 | 4 | 4 | 4 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | 3 | 3 | 3 | 4 | 4 | 4 | 4 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | 3 | 3 | 3 | 4 | 4 | 4 | 4 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | 3 | 3 | 3 | 4 | 4 | 4 | 4 | 1 | 1 | 1 | 1 | 1 | | 3 | 4 | 4 | 4 | 4 | |
+| | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 0 | 0 | 0 | 0 | 0 | |
+| | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 0 | 0 | 0 | 0 | 0 | |
+
+**Figure 7-19 – AU-4-4c numbering scheme within an
+STM-64's AU pointer row and payload columns**
+
+G.707-Y.1322\_F7-19
+
+36 **ITU-T Rec. G.707/Y.1322 (01/2007)**
+
+#### 7.3.2.4 Numbering of AU-4-16cs (VC-4-16cs) in an STM-64
+
+Any AU-4-16c can be allocated a four-figure address in the form #D, #C, #B, #A, where D designates the AUG-16 number (1 to 4), C, B and A are always 0, see Figure 7-20. The location of the columns in the STM-64 occupied by AU-4-16c (D,0,0,0) is given by:
+
+$$X\text{th column} = [X \bmod 16] + 16 \times [D-1] + 64 \times [X \text{ DIV } 16] \quad \text{for } X = 1 \text{ to } 4320.$$
+
+Therefore, AU-4-16c (1,0,0,0) resides in columns 1...16, 65...80, ..., 17 205...17 220 of the STM-64, and AU-4-16c (4,0,0,0) resides in columns 49...64, 113...128, ..., 17 265...17 280 of the STM-64.
+
+
+
+The diagram illustrates the mapping of STM-64 columns to AU-4-16c addresses. It shows the first 64 columns grouped into four sets of 16 (Time slots 1, 2, 3, 4 corresponding to Address D values 1, 2, 3, 4). After a break, it shows column 65 (Time slot 1, Address D=1) and the final columns ending at 17280 (Time slot 4, Address D=4). Addresses C, B, and A are always 0.
+
+| | | | | | |
+|---------------------|---------------------------------------------------------------------------------------------------------------------------------|--|----|--|-----------|
+| STM-N column number | 1 2 3 4 5 6 7 8 9 | | 65 | | 17280 |
+| Time slot number | 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 | | 1 | | 4 4 4 4 4 |
+| Address D | 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 | | 1 | | 4 4 4 4 4 |
+| Address C | 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 | | 0 | | 0 0 0 0 0 |
+| Address B | 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 | | 0 | | 0 0 0 0 0 |
+| Address A | 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 | | 0 | | 0 0 0 0 0 |
+
+Figure 7-20: AU-4-16c numbering scheme within an STM-64's AU pointer row and payload columns.
+
+G.707-Y.1322\_F7-20
+
+Figure 7-20 – AU-4-16c numbering scheme within an STM-64's AU pointer row and payload columns
+
+#### 7.3.2.5 Numbering of an AU-4-64c in an STM-64
+
+There is one AU-4-64c in an STM-64 signal. This signal does not need a number, but can be referred to as (0,0,0,0).
+
+#### 7.3.3 Numbering of AU-ns (VC-ns) in an STM-16
+
+The STM-16 can comprise four AUG-4s, which shall be numbered #1 to #4:
+
+- AUG-4 #1 is accommodated in columns 1...4, 17...20, 33...36, etc., of the STM-16;
+- AUG-4 #2 is accommodated in columns 5...8, 21...24, 36...40, etc., of the STM-16;
+- AUG-4 #3 is accommodated in columns 9...12, 25...28, 41...44, etc., of the STM-16;
+- AUG-4 #4 is accommodated in columns 13...16, 29...32, 45...48, etc., of the STM-16.
+
+Each AUG-4 can comprise four AUG-1s, which shall be numbered #1 to #4. Each AUG-1 can comprise three AU-3s, which shall be numbered #1 to #3.
+
+#### 7.3.3.1 Numbering of AU-4s (VC-4s) in an STM-16
+
+Any AU-4 can be allocated a number in the form #*C*, #*B*, #*A*, where *C* designates the AUG-4 number (1 to 4), *B* designates the AUG-1 number (1 to 4), and *A* is always 0, see Figure 7-21. The location of the columns in the STM-16 occupied by AU-4 (*C*,*B*,0) is given by:
+
+$$X\text{th column} = 1 + 4 \times [C-1] + [B-1] + 16 \times [X-1] \quad \text{for } X = 1 \text{ to } 270.$$
+
+Therefore, AU-4 (1,1,0) resides in columns 1, 17, 33, ..., 4305 of the STM-16, and AU-4 (4,4,0) resides in columns 16, 32, 48, ..., 4320 of the STM-16.
+
+
+
+The diagram shows the mapping between STM-N column numbers, time slot numbers, and addresses (C, B, A). The columns are grouped by 4. Time slots 1-16 correspond to addresses where C ranges from 1 to 4 and B ranges from 1 to 4, with A always 0. For example, time slot 1 is address (1,1,0), time slot 2 is (2,1,0), time slot 5 is (1,2,0), and so on. The sequence repeats every 16 time slots. The final time slots 4319 and 4320 correspond to addresses (3,4,0) and (4,4,0) respectively.
+
+| STM-N column number | 1 2 3 4 5 6 | | | | ... | 4319 4320 | | | | |
+|---------------------|-------------|---|---|---|-----|-----------|-----|------|------|---|
+| Time slot number | 1 | 2 | 3 | 4 | 5 | 6 | ... | 4319 | 4320 | |
+| Address | C | 1 | 2 | 3 | 4 | 1 | 2 | ... | 3 | 4 |
+| | B | 1 | 1 | 1 | 1 | 2 | 2 | ... | 4 | 4 |
+| | A | 0 | 0 | 0 | 0 | 0 | 0 | ... | 0 | 0 |
+
+Figure 7-21 – AU-4 numbering scheme within an STM-16's AU pointer row and payload columns
+
+**Figure 7-21 – AU-4 numbering scheme within an STM-16's AU pointer row and payload columns**
+
+#### 7.3.3.2 Numbering of AU-3s (VC-3s) in an STM-16
+
+Any AU-3 can be allocated a number in the form #*C*, #*B*, #*A*, where *C* designates the AUG-4 number (1 to 4), *B* designates the AUG-1 number (1 to 4), and *A* designates the AU-3 number (1 to 3), see Figure 7-22. The location of the columns in the STM-16 occupied by AU-3 (*C*,*B*,*A*) is given by:
+
+$$X\text{th column} = 1 + 4 \times [C-1] + [B-1] + 16 \times [A-1] + 48 \times [X-1] \quad \text{for } X = 1 \text{ to } 90.$$
+
+38
+
+ITU-T Rec. G.707/Y.1322 (01/2007)
+
+Therefore, AU-3 (1,1,1) resides in columns 1, 49, 97, ..., 4273 of the STM-16, and AU-3 (4,4,3) resides in columns 48, 96, 144, ..., 4320 of the STM-16.
+
+
+
+Figure 7-22 illustrates the mapping between STM-N column numbers (1-4320), time slot numbers (1-48 shown, then 445-448), and the three-figure address (C, B, A). The address components cycle as follows: A (1-3), B (1-4), C (1-4). For example, column 1 is (1,1,1), column 2 is (2,1,1), column 5 is (1,2,1), column 17 is (1,1,2), and column 4320 is (4,4,3).
+
+| STM-N column number | | 1 | 2 | 3 | 4 | 5 | 6 | ... | 4319 | 4320 |
+|---------------------|---|---|---|---|---|---|---|-----|------|------|
+| Time slot number | | 1 | 2 | 3 | 4 | 5 | 6 | ... | 447 | 448 |
+| Address | C | 1 | 2 | 3 | 4 | 1 | 2 | ... | 3 | 4 |
+| | B | 1 | 1 | 1 | 1 | 2 | 2 | ... | 4 | 4 |
+| | A | 1 | 1 | 1 | 1 | 1 | 1 | ... | 3 | 3 |
+
+**Figure 7-22 – AU-3 numbering scheme within an STM-16's AU pointer row and payload columns**
+
+Figure 7-22 – AU-3 numbering scheme within an STM-16's AU pointer row and payload columns
+
+### 7.3.3.3 Numbering of AU-4-4cs (VC-4-4cs) in an STM-16
+
+Any AU-4-4c can be allocated a three-figure address in the form #C, #B, #A, where C designates the AUG-4 number (1 to 4), B and A always 0, see Figure 7-23. The location of the columns in the STM-16 occupied by AU-4-4c (C,0,0) is given by:
+
+$4X\text{-3th column} = 1 + [C-1] + 16 \times [X-1]$ for X = 1 to 270.
+ $4X\text{-2th column} = 2 + [C-1] + 16 \times [X-1]$ for X = 1 to 270.
+ $4X\text{-1th column} = 3 + [C-1] + 16 \times [X-1]$ for X = 1 to 270.
+ $4X\text{th column} = 4 + [C-1] + 16 \times [X-1]$ for X = 1 to 270.
+
+Therefore, AU-4-4c (1,0,0) resides in columns 1...4, 17...20, ..., 4305...4308 of the STM-16, and AU-4-4c (4,0,0) resides in columns 13...16, 29...32, ..., 4317...4320 of the STM-16.
+
+
+
+Figure 7-23 shows the mapping for AU-4-4c. Columns are grouped in sets of 4. Columns 1-4 have address (1,0,0), 5-8 have (2,0,0), 9-12 have (3,0,0), and 13-16 have (4,0,0). This pattern repeats every 16 columns.
+
+| STM-N column number | | 1 | 2 | 3 | 4 | 5 | 6 | ... | 4319 | 4320 |
+|---------------------|---|---|---|---|---|---|---|-----|------|------|
+| Time slot number | | 1 | 1 | 1 | 1 | 2 | 2 | ... | 448 | 448 |
+| Address | C | 1 | 1 | 1 | 1 | 2 | 2 | ... | 4 | 4 |
+| | B | 0 | 0 | 0 | 0 | 0 | 0 | ... | 0 | 0 |
+| | A | 0 | 0 | 0 | 0 | 0 | 0 | ... | 0 | 0 |
+
+**Figure 7-23 – AU-4-4c numbering scheme within an STM-16's AU pointer row and payload columns**
+
+Figure 7-23 – AU-4-4c numbering scheme within an STM-16's AU pointer row and payload columns
+
+ITU-T Rec. G.707/Y.1322 (01/2007)
+
+39
+
+#### 7.3.3.4 Numbering of AU-4-16c in an STM-16
+
+There is one AU-4-16c in an STM-16 signal. This signal does not need a number, but can be referred to as (0,0,0).
+
+### 7.3.4 Numbering of AU-ns (VC-ns) in an STM-4
+
+The STM-4 can comprise four AUG-1s, which shall be numbered #1 to #4;
+
+- AUG-1 #1 is accommodated in columns 1, 5, 9, etc., of the STM-4;
+- AUG-1 #2 is accommodated in columns 2, 6, 10, etc., of the STM-4;
+- AUG-1 #3 is accommodated in columns 3, 7, 11, etc., of the STM-4;
+- AUG-1 #4 is accommodated in columns 4, 8, 12, etc., of the STM-4.
+
+Each AUG-1 can comprise three AU-3s, which shall be numbered #1 to #3.
+
+#### 7.3.4.1 Numbering of AU-4s (VC-4s) in an STM-4
+
+Any AU-4 can be allocated a number in the form #B, #A, where B designates the AUG-1 number (1 to 4), and A is always 0, see Figure 7-24. The location of the columns in the STM-4 occupied by AU-4 (B,0) is given by:
+
+$$X\text{th column} = 1 + [B-1] + 4 \times [X-1] \quad \text{for } X = 1 \text{ to } 270.$$
+
+Therefore, AU-4 (1,0) resides in columns 1, 5, 9, ..., 1077 of the STM-4, and AU-4 (4,0) resides in columns 4, 8, 12, ..., 1080 of the STM-4.
+
+
+
+Figure 7-24: AU-4 numbering scheme within an STM-4's AU pointer row and payload columns. The diagram shows a grid of columns and rows. The top row is labeled 'STM-N column number' and contains values 1, 2, 3, 4, 5, 6, followed by a gap, and then 1079, 1080. The next row is labeled 'Time slot number' and contains values 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, followed by a gap, and then 1, 1, 1. The third row is labeled 'Address' and contains two sub-rows: 'B' with values 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, followed by a gap, and then 2, 3, 4; and 'A' with values 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, followed by a gap, and then 0, 0, 0. A label 'G.707-Y.1322\_F7-24' is at the bottom right.
+
+**Figure 7-24 – AU-4 numbering scheme within an STM-4's AU pointer row and payload columns**
+
+#### 7.3.4.2 Numbering of AU-3s (VC-3s) in an STM-4
+
+Any AU-3 can be allocated a number in the form #B, #A, where B designates the AUG-1 number (1 to 4), and A designates the AU-3 number (1 to 3), see Figure 7-25. The location of the columns in the STM-4 occupied by AU-3 (B,A) is given by:
+
+$$X\text{th column} = 1 + [B-1] + 4 \times [A-1] + 12 \times [X-1] \quad \text{for } X = 1 \text{ to } 90.$$
+
+Therefore, AU-3 (1,1) resides in columns 1, 13, 25, ..., 1069 of the STM-4, and AU-4 (4,3) resides in columns 12, 24, 36, ..., 1080 of the STM-4.
+
+
+
+STM-N column number
+
+1 2 3 4 5 6 1079
+1080
+
+Time slot number
+
+1 2 3 4 5 6 7 8 9 1 1 1 1 2 ----- 1 1 1 1
+0 1 2
+
+Address
+
+B 1 2 3 4 1 2 3 4 1 2 3 4 1 2 ----- 2 3 4
+A 1 1 1 1 2 2 2 2 3 3 3 3 3 1 1 ----- 3 3 3
+
+G.707-Y.1322\_F7-25
+
+Figure 7-25: AU-3 numbering scheme within an STM-4's AU pointer row and payload columns. The diagram shows a grid of columns (1 to 6, then 1079 to 1080) and rows (Time slot number, Address). The Address row is split into two sections, B and A. Section B shows columns 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2. Section A shows columns 1, 1, 1, 1, 2, 2, 2, 2, 3, 3, 3, 3, 3, 1, 1. The right side shows columns 1079, 1080 with values 1, 1, 1, 1, 0, 1, 2, 2, 2, 3, 4, 3, 3, 3.
+
+**Figure 7-25 – AU-3 numbering scheme within an STM-4's AU pointer row and payload columns**
+
+#### **7.3.4.3 Numbering of an AU-4-4c in an STM-4**
+
+There is one AU-4-4c in an STM-4 signal. This signal does not need a number, but can be referred to as (0,0).
+
+### **7.3.5 Numbering of AU-ns (VC-ns) in an STM-1 signal**
+
+#### **7.3.5.1 Numbering of AU-4 (VC-4) in an STM-1 signal**
+
+There is one AU-4 (VC-4) in an STM-1 signal. This signal does not need a number, but can be referred to as (0).
+
+#### **7.3.5.2 Numbering of AU-3 (VC-3) in an STM-1 signal**
+
+Any AU-3 can be allocated a number in the form #A, where A designates the AU-3 number (1 to 3), see Figure 7-26. The location of the columns in the STM-1 occupied by AU-3 (A) is given by:
+
+Xth column = 1 + [A-1] + 3 × [X-1] for X = 1 to 90.
+
+Therefore, AU-3 (1) resides in columns 1, 4, 7, ..., 268 of the STM-1, and AU-3 (3) resides in columns 3, 6, 9, ..., 270 of the STM-1.
+
+
+
+STM-N column number
+
+1 2 3 4 5 6 269
+270
+
+Time slot number
+
+1 2 3 1 2 3 1 2 3 1 2 3 1 2 ----- 1 2 3
+
+Address
+
+A 1 2 3 1 2 3 1 2 3 1 2 3 1 2 ----- 1 2 3
+
+G.707-Y.1322\_F7-26
+
+Figure 7-26: AU-3 numbering scheme within an STM-1's AU pointer row and payload columns. The diagram shows a grid of columns (1 to 6, then 269 to 270) and rows (Time slot number, Address). The Address row is split into section A. Section A shows columns 1, 2, 3, 1, 2, 3, 1, 2, 3, 1, 2, 3, 1, 2. The right side shows columns 269, 270 with values 1, 2, 3, 1, 2, 3.
+
+**Figure 7-26 – AU-3 numbering scheme within an STM-1's AU pointer row and payload columns**
+
+### 7.3.6 Numbering of AU-3 (VC-3) in an STM-0 signal
+
+There is one AU-3 (VC-3) in an STM-0 signal. This signal does not need a number, but can be referred to as (0).
+
+### 7.3.7 Numbering of TU-3s in a VC-4
+
+The VC-4 can comprise three TUG-3s which shall be numbered #1, #2, and #3.
+
+- TUG-3 #1 (Corresponding to TUG-3 (A) in Figure 7-6) is accommodated in columns 4, 7, 10, ..., 259 of the VC-4;
+- TUG-3 #2 (Corresponding to TUG-3 (B) in Figure 7-6) is accommodated in columns 5, 8, 11, ..., 260 of the VC-4;
+- TUG-3 #3 (Corresponding to TUG-3 (C) in Figure 7-6) is accommodated in columns 6, 9, 12, ..., 261 of the VC-4.
+
+Each TUG-3 can comprise a TU-3.
+
+Thus any TU-3 can be allocated a three-figure address in the form #K, #L, #M, where K designates the TUG-3 number (1 to 3); L and M are always 0. The location of the columns in the VC-4 occupied by TU-3 (K,0,0) is given by the formula:
+
+$$\text{Xth column} = 4 + [K-1] + 3 \times [X-1] \quad \text{for } X = 1 \text{ to } 86.$$
+
+Thus TU-3 (1,0,0) resides in columns 4, 7, 10, ..., 259 of the VC-4, and TU-3 (3,0,0) resides in columns 6, 9, 12, ..., 261 of the VC-4.
+
+### 7.3.8 Numbering of TU-2s in a VC-4
+
+Each TUG-3 can comprise seven TUG-2s which shall be numbered #1 to #7 and each TUG-2 can comprise a TU-2.
+
+Thus any TU-2 can be allocated a three-figure address in the form #K, #L, #M, where K designates the TUG-3 number (1 to 3), L designates the TUG-2 number (1 to 7), and M is always 0. The location of the columns in the VC-4 occupied by TU-2 (K, L, 0) is given by the formula:
+
+$$\text{Xth column} = 10 + [K-1] + 3 \times [L-1] + 21 \times [X-1] \quad \text{for } X = 1 \text{ to } 12.$$
+
+Thus TU-2 (1,1,0) resides in columns 10, 31, 52, 73, 94, 115, 136, 157, 178, 199, 220 and 241 of the VC-4, and TU-2 (3,7,0) resides in columns 30, 51, 72, 93, 114, 135, 156, 177, 198, 219, 240 and 261 of the VC-4. A full listing of the location of the TU-2 columns within the VC-4 frame is given in Appendix I.
+
+### 7.3.9 Numbering of TU-12s in a VC-4
+
+Each TUG-3 can comprise seven TUG-2s which shall be numbered #1 to #7 and each TUG-2 can comprise three TU-12s which shall be numbered #1 to #3.
+
+Thus any TU-12 can be allocated a number in the form #K, #L, #M, where K designates the TUG-3 number (1 to 3), L designates the TUG-2 number (1 to 7), and M designates the TU-12 number (1 to 3). The location of the columns in the VC-4 occupied by TU-12 (K,L,M) is given by the formula:
+
+$$\text{Xth column} = 10 + [K-1] + 3 \times [L-1] + 21 \times [M-1] + 63 \times [X-1] \quad \text{for } X = 1 \text{ to } 4.$$
+
+Thus TU-12 (1,1,1) resides in columns 10, 73, 136, and 199 of the VC-4, and TU-12 (3,7,3) resides in columns 72, 135, 198 and 261 of the VC-4. A full listing of the location of the TU-12 columns within the VC-4 frame is given in Appendix II.
+
+### 7.3.10 Numbering of TU-11s in a VC-4
+
+Each TUG-3 can comprise seven TUG-2s which shall be numbered #1 to #7 and each TUG-2 can comprise four TU-11s which shall be numbered #1 to #4.
+
+Thus any TU-11 can be allocated a number in the form #K, #L, #M, where K designates the TUG-3 number (1 to 3), L designates the TUG-2 number (1 to 7), and M designates the TU-11 number (1 to 4). The location of the columns in the VC-4 occupied by TU-11 (K,L,M) is given by the formula:
+
+$$\text{Xth column} = 10 + [K-1] + 3 \times [L-1] + 21 \times [M-1] + 84 \times [X-1] \quad \text{for } X = 1 \text{ to } 3.$$
+
+Thus TU-11 (1,1,1) resides in columns 10, 94 and 178 of the VC-4, and TU-11 (3,7,4) resides in columns 93, 177 and 261 of the VC-4. A full listing of the location of the TU-11 columns within the VC-4 frame is given in Appendix III.
+
+### 7.3.11 Numbering of TU-2s in a VC-3
+
+As shown in Figures 7-9 and 7-10, a VC-3 can comprise seven TUG-2s which shall be numbered from #1 to #7. Each TUG-2 can comprise a TU-2.
+
+Thus any TU-2 can be allocated a two-figure address in the form #L, #M, where L designates the TUG-2 number (1 to 7) and M is always 0. The location of the columns in the VC-3 occupied by TU-2 (L, 0) is given by the formula:
+
+$$\text{Xth column} = 2 + [L-1] + 7 \times [X-1] \quad \text{for } X = 1 \text{ to } 12.$$
+
+Thus TU-2 (1,0) resides in columns 2, 9, ... and 79 of the VC-3, and TU-2 (7,0) resides in columns 8, 15, ... and 85 of the VC-3. A full listing of the location of the TU-2 columns with the VC-3 frame is given in Appendix IV.
+
+### 7.3.12 Numbering of TU-12s in a VC-3
+
+Each TUG-2 can comprise three TU-12s which shall be numbered #1 to #3.
+
+Thus any TU-12 can be allocated a two-figure address in the form #L, #M, where L designates the TUG-2 number (1 to 7) and M designates the TU-12 number (1 to 3). The location of the columns in the VC-3 occupied by TU-12 (L, M) is given by the formula:
+
+$$\text{Xth column} = 2 + [L-1] + 7 \times [M-1] + 21 \times [X-1] \quad \text{for } X = 1 \text{ to } 4.$$
+
+Thus TU-12 (1,1) resides in columns 2, 23, 44 and 65 of the VC-3, and TU-12 (7,3) resides in columns 22, 43, 64 and 85 of the VC-3. A full listing of the location of the TU-12 columns with the VC-3 frame is given in Appendix V.
+
+### 7.3.13 Numbering of TU-11s in a VC-3
+
+Each TUG-2 can comprise four TU-11s which shall be numbered #1 to #4.
+
+Thus any TU-11 can be allocated a two-figure address in the form #L, #M, where L designates the TUG-2 number (1 to 7) and M designates the TU-11 number (1 to 4). The location of the columns in the VC-3 occupied by TU-11 (L, M) is given by the formula:
+
+$$\text{Xth column} = 2 + [L-1] + 7 \times [M-1] + 28 \times [X-1] \quad \text{for } X = 1 \text{ to } 3.$$
+
+Thus TU-11 (1,1) resides in columns 2, 30 and 58 of the VC-3, and TU-11 (7,4) resides in columns 29, 57 and 85 of the VC-3. A full listing of the location of the TU-11 columns with the VC-3 frame is given in Appendix VI.
+
+NOTE – The time slot number contained in Figures 7-26 to 7-28 should not be interpreted as the tributary port number.
+
+An external tributary signal may be assigned to a particular payload capacity using a connection function.
+
+For example, at the VC-12 level:
+
+- Tributary #1 – TU-12 (1,1,1);
+- Tributary #2 – TU-12 (1,1,2);
+- Tributary #3 – TU-12 (1,1,3);
+- Tributary #4 – TU-12 (1,2,1);
+- :
+- Tributary #63 – TU-12 (3,7,3).
+
+
+
+TU-3 numbering scheme
+
+TU-3 numbering scheme diagram showing VC-4 columns 1-261. Columns 1-9 are POH. Columns 10-261 show a repeating pattern of K=1,2,3; L=0; M=0.
+
+
+
+TU-2 numbering scheme
+
+TU-2 numbering scheme diagram showing VC-4 columns 1-261. Columns 10-261 show a repeating pattern of K=1,2,3; L=1-7; M=0.
+
+
+
+TU-12 numbering scheme
+
+G.707-Y.1322\_F7-27
+
+TU-12 numbering scheme diagram showing VC-4 columns 1-261. Columns 10-261 show a repeating pattern of K=1,2,3; L=1-7; M=1-3.
+
+**Figure 7-27 – TU-3, TU-2 and TU-12 numbering scheme within a VC-4**
+
+45 **ITU-T Rec. G.707/Y.1322 (01/2007)**
+
+| VC-4 column number | Time slot number | K | L Address | M |
+|--------------------|------------------|---|-----------|---|
+| 1 | 1 | 1 | 1 | 1 |
+| 2 | 2 | 2 | 2 | 2 |
+| 3 | 3 | 3 | 3 | 3 |
+| 4 | 4 | 1 | 1 | 1 |
+| 5 | 5 | 2 | 2 | 2 |
+| 6 | 6 | 3 | 3 | 3 |
+| 7 | 7 | 1 | 1 | 1 |
+| 8 | 8 | 2 | 2 | 2 |
+| 9 | 9 | 3 | 3 | 3 |
+| 10 | 10 | 1 | 1 | 1 |
+| 11 | 11 | 2 | 2 | 2 |
+| 12 | 12 | 3 | 3 | 3 |
+| 13 | 13 | 1 | 1 | 1 |
+| 14 | 14 | 2 | 2 | 2 |
+| 15 | 15 | 3 | 3 | 3 |
+| 16 | 16 | 1 | 1 | 1 |
+| 17 | 17 | 2 | 2 | 2 |
+| 18 | 18 | 3 | 3 | 3 |
+| 19 | 19 | 1 | 1 | 1 |
+| 20 | 20 | 2 | 2 | 2 |
+| 21 | 21 | 3 | 3 | 3 |
+| 22 | 22 | 1 | 1 | 1 |
+| 23 | 23 | 2 | 2 | 2 |
+| 24 | 24 | 3 | 3 | 3 |
+| 25 | 25 | 1 | 1 | 1 |
+| 26 | 26 | 2 | 2 | 2 |
+| 27 | 27 | 3 | 3 | 3 |
+| 28 | 28 | 1 | 1 | 1 |
+| 29 | 29 | 2 | 2 | 2 |
+| 30 | 30 | 3 | 3 | 3 |
+| 31 | 31 | 1 | 1 | 1 |
+| 32 | 32 | 2 | 2 | 2 |
+| 33 | 33 | 3 | 3 | 3 |
+| 34 | 34 | 1 | 1 | 1 |
+| 35 | 35 | 2 | 2 | 2 |
+| 36 | 36 | 3 | 3 | 3 |
+| 37 | 37 | 1 | 1 | 1 |
+| 38 | 38 | 2 | 2 | 2 |
+| 39 | 39 | 3 | 3 | 3 |
+| 40 | 40 | 1 | 1 | 1 |
+| 41 | 41 | 2 | 2 | 2 |
+| 42 | 42 | 3 | 3 | 3 |
+| 43 | 43 | 1 | 1 | 1 |
+| 44 | 44 | 2 | 2 | 2 |
+| 45 | 45 | 3 | 3 | 3 |
+| 46 | 46 | 1 | 1 | 1 |
+| 47 | 47 | 2 | 2 | 2 |
+| 48 | 48 | 3 | 3 | 3 |
+| 49 | 49 | 1 | 1 | 1 |
+| 50 | 50 | 2 | 2 | 2 |
+| 51 | 51 | 3 | 3 | 3 |
+| 52 | 52 | 1 | 1 | 1 |
+| 53 | 53 | 2 | 2 | 2 |
+| 54 | 54 | 3 | 3 | 3 |
+| 55 | 55 | 1 | 1 | 1 |
+| 56 | 56 | 2 | 2 | 2 |
+| 57 | 57 | 3 | 3 | 3 |
+| 58 | 58 | 1 | 1 | 1 |
+| 59 | 59 | 2 | 2 | 2 |
+| 60 | 60 | 3 | 3 | 3 |
+| 61 | 61 | 1 | 1 | 1 |
+| 62 | 62 | 2 | 2 | 2 |
+| 63 | 63 | 3 | 3 | 3 |
+| 64 | 64 | 1 | 1 | 1 |
+| 65 | 65 | 2 | 2 | 2 |
+| 66 | 66 | 3 | 3 | 3 |
+| 67 | 67 | 1 | 1 | 1 |
+| 68 | 68 | 2 | 2 | 2 |
+| 69 | 69 | 3 | 3 | 3 |
+| 70 | 70 | 1 | 1 | 1 |
+| 71 | 71 | 2 | 2 | 2 |
+| 72 | 72 | 3 | 3 | 3 |
+| 73 | 73 | 1 | 1 | 1 |
+| 74 | 74 | 2 | 2 | 2 |
+| 75 | 75 | 3 | 3 | 3 |
+| 76 | 76 | 1 | 1 | 1 |
+| 77 | 77 | 2 | 2 | 2 |
+| 78 | 78 | 3 | 3 | 3 |
+| 79 | 79 | 1 | 1 | 1 |
+| 80 | 80 | 2 | 2 | 2 |
+| 81 | 81 | 3 | 3 | 3 |
+| 82 | 82 | 1 | 1 | 1 |
+| 83 | 83 | 2 | 2 | 2 |
+| 84 | 84 | 3 | 3 | 3 |
+| 85 | 85 | 1 | 1 | 1 |
+| 86 | 86 | 2 | 2 | 2 |
+| 87 | 87 | 3 | 3 | 3 |
+| 88 | 88 | 1 | 1 | 1 |
+| 89 | 89 | 2 | 2 | 2 |
+| 90 | 90 | 3 | 3 | 3 |
+| 91 | 91 | 1 | 1 | 1 |
+| 92 | 92 | 2 | 2 | 2 |
+| 93 | 93 | 3 | 3 | 3 |
+| 94 | 94 | 1 | 1 | 1 |
+| 95 | 95 | 2 | 2 | 2 |
+| 96 | 96 | 3 | 3 | 3 |
+| 97 | 97 | 1 | 1 | 1 |
+| 98 | 98 | 2 | 2 | 2 |
+| 99 | 99 | 3 | 3 | 3 |
+| 100 | 100 | 1 | 1 | 1 |
+| 101 | 101 | 2 | 2 | 2 |
+| 102 | 102 | 3 | 3 | 3 |
+| 103 | 103 | 1 | 1 | 1 |
+| 104 | 104 | 2 | 2 | 2 |
+| 105 | 105 | 3 | 3 | 3 |
+
+| VC-4 column number | Time slot number | K | L Address | M |
+|--------------------|------------------|---|-----------|---|
+| 82 | 1 | 1 | 1 | 1 |
+| 83 | 2 | 2 | 2 | 2 |
+| 84 | 3 | 3 | 3 | 3 |
+| 85 | 1 | 1 | 1 | 1 |
+| 86 | 2 | 2 | 2 | 2 |
+| 87 | 3 | 3 | 3 | 3 |
+| 88 | 1 | 1 | 1 | 1 |
+| 89 | 2 | 2 | 2 | 2 |
+| 90 | 3 | 3 | 3 | 3 |
+| 91 | 1 | 1 | 1 | 1 |
+| 92 | 2 | 2 | 2 | 2 |
+| 93 | 3 | 3 | 3 | 3 |
+| 94 | 1 | 1 | 1 | 1 |
+| 95 | 2 | 2 | 2 | 2 |
+| 96 | 3 | 3 | 3 | 3 |
+| 97 | 1 | 1 | 1 | 1 |
+| 98 | 2 | 2 | 2 | 2 |
+| 99 | 3 | 3 | 3 | 3 |
+| 100 | 1 | 1 | 1 | 1 |
+| 101 | 2 | 2 | 2 | 2 |
+| 102 | 3 | 3 | 3 | 3 |
+| 103 | 1 | 1 | 1 | 1 |
+| 104 | 2 | 2 | 2 | 2 |
+| 105 | 3 | 3 | 3 | 3 |
+
+| VC-4 column number | Time slot number | K | L Address | M |
+|--------------------|------------------|---|-----------|---|
+| 250 | 1 | 1 | 1 | 1 |
+| 251 | 2 | 2 | 2 | 2 |
+| 252 | 3 | 3 | 3 | 3 |
+| 253 | 1 | 1 | 1 | 1 |
+| 254 | 2 | 2 | 2 | 2 |
+| 255 | 3 | 3 | 3 | 3 |
+| 256 | 1 | 1 | 1 | 1 |
+| 257 | 2 | 2 | 2 | 2 |
+| 258 | 3 | 3 | 3 | 3 |
+| 259 | 1 | 1 | 1 | 1 |
+| 260 | 2 | 2 | 2 | 2 |
+| 261 | 3 | 3 | 3 | 3 |
+
+G.707-Y.1322\_F7-28
+
+Figure 7-28 – TU-11 numbering scheme within a VC-4
+
+
+
+**Table 7-1 – Allocation of TU-n capacity to time slots within a VC-4**
+
+| Address # | | | | | Address # | | | | | Address # | | | | |
+|-----------|------|-------|-------|-----|-----------|------|-------|-------|-----|-----------|------|-------|-------|-----|
+| TU-3 | TU-2 | TU-12 | TU-11 | TS# | TU-3 | TU-2 | TU-12 | TU-11 | TS# | TU-3 | TU-2 | TU-12 | TU-11 | TS# |
+| 100 | 110 | 111 | 111 | 1 | 200 | 210 | 211 | 211 | 2 | 300 | 310 | 311 | 311 | 3 |
+| | | 112 | 112 | 22 | | | 212 | 212 | 23 | | | 312 | 312 | 24 |
+| | | 113 | 113 | 43 | | | 213 | 213 | 44 | | | 313 | 313 | 45 |
+| | | | 114 | 64 | | | | 214 | 65 | | | | 314 | 66 |
+| | 120 | 121 | 121 | 4 | | 220 | 221 | 221 | 5 | | 320 | 321 | 321 | 6 |
+| | | 122 | 122 | 25 | | | 222 | 222 | 26 | | | 322 | 322 | 27 |
+| | | 123 | 123 | 46 | | | 223 | 223 | 47 | | | 323 | 323 | 48 |
+| | | | 124 | 67 | | | | 224 | 68 | | | | 324 | 69 |
+| | 130 | 131 | 131 | 7 | | 230 | 231 | 231 | 8 | | 330 | 331 | 331 | 9 |
+| | | 132 | 132 | 28 | | | 232 | 232 | 29 | | | 332 | 332 | 30 |
+| | | 133 | 133 | 49 | | | 233 | 233 | 50 | | | 333 | 333 | 51 |
+| | | | 134 | 70 | | | | 234 | 71 | | | | 334 | 72 |
+| | 140 | 141 | 141 | 10 | | 240 | 241 | 241 | 11 | | 340 | 341 | 341 | 12 |
+| | | 142 | 142 | 31 | | | 242 | 242 | 32 | | | 342 | 342 | 33 |
+| | | 143 | 143 | 52 | | | 243 | 243 | 53 | | | 343 | 343 | 54 |
+| | | | 144 | 73 | | | | 244 | 74 | | | | 344 | 75 |
+| | 150 | 151 | 151 | 13 | | 250 | 251 | 251 | 14 | | 350 | 351 | 351 | 15 |
+| | | 152 | 152 | 34 | | | 252 | 252 | 35 | | | 352 | 352 | 36 |
+| | | 153 | 153 | 55 | | | 253 | 253 | 56 | | | 353 | 353 | 57 |
+| | | | 154 | 76 | | | | 254 | 77 | | | | 354 | 78 |
+| | 160 | 161 | 161 | 16 | | 260 | 261 | 261 | 17 | | 360 | 361 | 361 | 18 |
+| | | 162 | 162 | 37 | | | 262 | 262 | 38 | | | 362 | 362 | 39 |
+| | | 163 | 163 | 58 | | | 263 | 263 | 59 | | | 363 | 363 | 60 |
+| | | | 164 | 79 | | | | 264 | 80 | | | | 364 | 81 |
+| | 170 | 171 | 171 | 19 | | 270 | 271 | 271 | 20 | | 370 | 371 | 371 | 21 |
+| | | 172 | 172 | 40 | | | 272 | 272 | 41 | | | 372 | 372 | 42 |
+| | | 173 | 173 | 61 | | | 273 | 273 | 62 | | | 373 | 373 | 63 |
+| | | | 174 | 82 | | | | 274 | 83 | | | | 374 | 84 |
+
+Address = TUG-3#, TUG-2#, TU-1# = #K, #L, #M
+
+**Table 7-2 – Allocation of TU-n capacity to time slots within a VC-3**
+
+| Address # | | | TS# |
+|----------------------------------|-------|-------|-----|
+| TU-2 | TU-12 | TU-11 | |
+| 10 | 11 | 11 | 1 |
+| | 12 | 12 | 8 |
+| | 13 | 13 | 15 |
+| | | 14 | 22 |
+| 20 | 21 | 21 | 2 |
+| | 22 | 22 | 9 |
+| | 23 | 23 | 16 |
+| | | 24 | 23 |
+| 30 | 31 | 31 | 3 |
+| | 32 | 32 | 10 |
+| | 33 | 33 | 17 |
+| | | 34 | 24 |
+| 40 | 41 | 41 | 4 |
+| | 42 | 42 | 11 |
+| | 43 | 43 | 18 |
+| | | 44 | 25 |
+| 50 | 51 | 51 | 5 |
+| | 52 | 52 | 12 |
+| | 53 | 53 | 19 |
+| | | 54 | 26 |
+| 60 | 61 | 61 | 6 |
+| | 62 | 62 | 13 |
+| | 63 | 63 | 20 |
+| | | 64 | 27 |
+| 70 | 71 | 71 | 7 |
+| | 72 | 72 | 14 |
+| | 73 | 73 | 21 |
+| | | 74 | 28 |
+| Address = TUG-2#, TU-1# = #L, #M | | | |
+
+# 8 Pointers
+
+## 8.1 AU-n pointer
+
+The AU-n pointer provides a method of allowing flexible and dynamic alignment of the VC-n within the AU-n frame.
+
+Dynamic alignment means that the VC-n is allowed to "float" within the AU-n frame. Thus, the pointer is able to accommodate differences, not only in the phases of the VC-n and the SOH, but also in the frame rates.
+
+### 8.1.1 AU-n pointer location
+
+The AU-4 pointer is contained in bytes H1, H2 and H3 as shown in Figure 8-1. The three individual AU-3 pointers are contained in three separate H1, H2 and H3 bytes as shown in Figure 8-2.
+
+
+
+### 8.1.2 AU-n pointer value
+
+The pointer contained in H1 and H2 designates the location of the byte where the VC-n begins. The two bytes allocated to the pointer function can be viewed as one word as shown in Figure 8-3. The last ten bits (bits 7-16) of the pointer word carry the pointer value.
+
+As illustrated in Figure 8-3, the AU-4 pointer value is a binary number with a range of 0 to 782 which indicates the offset, in three-byte increments, between the pointer and the first byte of the VC-4 (see Figure 8-1). Figure 8-3 also indicates one additional valid pointer, the concatenation indication. The concatenation indication is indicated by "1001" in bits 1-4, bits 5-6 unspecified, and ten "1"s in bits 7-16. The AU-4 pointer is set to concatenation indication for AU-4 concatenation (see 8.1.7).
+
+As illustrated in Figure 8-3, the AU-3 pointer value is also a binary number with a range of 0 to 782. Since there are three AU-3s in the AUG-1, each AU-3 has its own associated H1, H2 and H3 bytes. As shown in Figure 8-2, the H bytes are shown in sequence. The first H1, H2, H3 set refers to the first AU-3, and the second set to the second AU-3, and so on. For the AU-3s, each pointer operates independently.
+
+In all cases, the AU-n pointer bytes are not counted in the offset. For example, in an AU-4, the pointer value of 0 indicates that the VC-4 starts in the byte location that immediately follows the last H3 byte, whereas an offset of 87 indicates that the VC-4 starts three bytes after the K2 byte.
+
+
+
+**H1**
+**H2**
+**H3**
+
+| | | | | | | | | | | | | | | | | | |
+|---|---|---|---|---|---|---|---|---|----|----|----|----|----|----|----|--|--|
+| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | | |
+| N | N | N | N | S | S | I | D | I | D | I | D | I | D | I | D | | |
+
+↑
+10 bit pointer value
+
+↑
+Negative
+justification
+opportunity
+
+↑
+Positive
+justification
+opportunity
+
+
+
+I Increment
+D Decrement
+N New data flag
+
+*New data flag*
+
+- Enabled when at least 3 out of 4 bits match "1001"
+- Disabled when at least 3 out of 4 bits match "0110"
+- Invalid with other codes
+
+*Negative justification*
+
+- Invert 5 D-bits
+- Accept majority vote
+
+*Pointer value (b7-b16)*
+
+- Normal range is:
+for AU-4, AU-3: 0-782 decimal
+for TU-3: 0-764 decimal
+
+*Positive justification*
+
+- Invert 5 I-bits
+- Accept majority vote
+
+*Concatenation indication*
+
+- 1001SS1111111111 (SS bits are unspecified)
+
+
+
+| SS bits | AU-n/TU-n type |
+|---------|---------------------------|
+| 10 | AU-4, AU-4-Xc, AU-3, TU-3 |
+
+G.707-Y.1322\_F8-3
+
+**Figure 8-3 – AU-n/TU-3 pointer (H1, H2, H3) coding**
+
+**NOTE 1** – The AU-4, AU-4-Xc, AU-3 SS bits were included in the pointer detection algorithm (refer to the 1997 version of ITU-T Rec. G.783). Since the 2000 versions of ITU-T Recs G.783 and G.806, the SS bits are excluded from the AU-n pointer detection algorithm.
+
+**NOTE 2** – The pointer is set to all "1"s when AIS occurs.
+
+### 8.1.3 Frequency justification
+
+If there is a frequency offset between the frame rate of the AUG-N and that of the VC-n, then the pointer value will be incremented or decremented as needed, accompanied by a corresponding positive or negative justification byte or bytes. Consecutive pointer operations must be separated by at least three frames (i.e., every fourth frame) in which the pointer value remains constant.
+
+If the frame rate of the VC-n is too slow with respect to that of the AUG-N, then the alignment of the VC-n must periodically slip back in time and the pointer value must be incremented by one. This operation is indicated by inverting bits 7, 9, 11, 13 and 15 (I-bits) of the pointer word to allow 5-bit majority voting at the receiver. Three positive justification bytes appear immediately after the last H3 byte in the AU-4 frame containing inverted I-bits. Subsequent pointers will contain the new offset. This is illustrated in Figure 8-4.
+
+
+
+The diagram illustrates the AU-4 pointer adjustment operation with positive justification across four frames. The AU-4 frame structure is shown with columns 1-10 and AUG 270. The pointer value is tracked through four frames, showing the transition from $n$ to $n+1$ via inverted I-bits and three positive justification bytes in Frame 3.
+
+**Frame 1:** The pointer value is $n$ . The frame structure shows bytes H1, Y, Y, H2, I\*, I\*, H3, H3, H3. The pointer value $n$ is indicated by an arrow pointing to the start of the VC-4 payload.
+
+**Frame 2:** The pointer value remains $n$ . The frame structure is identical to Frame 1.
+
+**Frame 3:** The pointer value is $n$ (I-bits inverted). The frame structure shows bytes H1, Y, Y, H2, I\*, I\*, H3, H3, H3, followed by three positive justification bytes (highlighted in yellow). The pointer value $n$ is indicated by an arrow pointing to the start of the VC-4 payload. The new pointer value $n+1$ is indicated by an arrow pointing to the start of the VC-4 payload after the justification bytes.
+
+**Frame 4:** The pointer value is $n+1$ . The frame structure shows bytes H1, Y, Y, H2, I\*, I\*, H3, H3, H3. The pointer value $n+1$ is indicated by an arrow pointing to the start of the VC-4 payload.
+
+Timeline: Frame 1 at 125 $\mu\text{s}$ , Frame 2 at 250 $\mu\text{s}$ , Frame 3 at 375 $\mu\text{s}$ , Frame 4 at 500 $\mu\text{s}$ .
+
+Diagram illustrating AU-4 pointer adjustment operation with positive justification across four frames. The diagram shows the AU-4 frame structure with columns 1-10 and AUG 270. It tracks the pointer value (n) through four frames, showing the transition from n to n+1 via inverted I-bits and three positive justification bytes in Frame 3.
+
+G.707-Y.1322\_F8-4
+
+I\* All 1s byte
+
+Y 1001 SS11 (S bits are unspecified)
+
+**Figure 8-4 – AU-4 pointer adjustment operation – Positive justification**
+
+For AU-3 frames, a positive justification byte appears immediately after the individual H3 byte of the AU-3 frame containing inverted I-bits. Subsequent pointers will contain the new offset. This is illustrated in Figure 8-5.
+
+
+
+The diagram illustrates the AU-3 pointer adjustment operation with positive justification across four frames (Frame 1 to Frame 4) over a 500 μs period. The AUG (Administrative Unit Group) is shown with bytes 1-10 and 270. Each frame contains H1, H2, and H3 bytes. In Frame 3, the H3 byte is followed by a positive justification byte for VC-3 #3. Arrows indicate the pointer value (n, n+1, or inverted) pointing to the start of VC-3 #3. Upward arrows indicate the pointer operating on VC-3 #3.
+
+Key elements of the diagram:
+
+- Frame 1:** Start of VC-3 #3. Pointer value is n. The H3 byte points to the start of VC-3 #3.
+- Frame 2:** Pointer value is n. The H3 byte points to the start of VC-3 #3.
+- Frame 3:** Pointer value is (I-bits inverted). The H3 byte points to the start of VC-3 #3. A positive justification byte for VC-3 #3 is inserted after the H3 byte.
+- Frame 4:** Pointer value is (n + 1). The H3 byte points to the start of VC-3 #3.
+
+Time intervals: 125 μs, 250 μs, 375 μs, 500 μs.
+
+↑ Indicates pointer operating on VC-3 # 3
+
+G.707-Y.1322\_F8-5
+
+Timing diagram for AU-3 pointer adjustment operation with positive justification. It shows four frames (Frame 1 to Frame 4) over a 500 microsecond period. Each frame contains H1, H2, and H3 bytes. In Frame 3, the H3 byte is followed by a positive justification byte for VC-3 #3. Arrows indicate the pointer value (n, n+1, or inverted) pointing to the start of VC-3 #3. Upward arrows indicate the pointer operating on VC-3 #3.
+
+**Figure 8-5 – AU-3 pointer adjustment operation – Positive justification**
+
+If the frame rate of the VC-n is too fast with respect to that of the AUG-N, then the alignment of the VC-n must periodically be advanced in time and the pointer value must be decremented by one. This operation is indicated by inverting bits 8, 10, 12, 14 and 16 (D-bits) of the pointer word to allow 5-bit majority voting at the receiver. Three negative justification bytes appear in the H3 bytes in the AU-4 frame containing inverted D-bits. Subsequent pointers will contain the new offset. This is illustrated in Figure 8-6.
+
+
+
+1 2 3 4 5 6 7 8 9 10 AUG 270
+
+1 Start of VC-4
+
+2
+
+3
+
+4 H1 Y Y H2 1\* 1\* H3 H3 H3
+
+5 n-1 n n n n+1, n+1
+
+6
+
+7 Frame 1
+
+8
+
+9 125 μs
+
+1
+
+2 Pointer value (n)
+
+3
+
+4 H1 Y Y H2 1\* 1\* H3 H3 H3
+
+5 n-2, n-1, n-1, n-1 n n n n+1, n+1
+
+6
+
+7 Frame 2
+
+8
+
+9 250 μs
+
+1
+
+2 Pointer value (D-bits inverted)
+
+3
+
+4 H1 Y Y H2 1\* 1\* ← Negative justification bytes (data)
+
+5 n-2 n-1, n-1, n-1 n n n n+1, n+1
+
+6
+
+7 Frame 3
+
+8
+
+9 375 μs
+
+1
+
+2 Pointer value (n-1)
+
+3
+
+4 H1 Y Y H2 1\* 1\* H3 H3 H3
+
+5 n-2 n-1, n-1, n-1 n n n n+1, n+1
+
+6
+
+7 Frame 4
+
+8
+
+9 500 μs
+
+1\* All 1s byte
+Y 1001 SS11 (S bits are unspecified)
+
+G.707-Y.1322\_F8-6
+
+Timing diagram for AU-4 pointer adjustment operation with negative justification. It shows four frames (Frame 1 to Frame 4) over a 500 microsecond period. Each frame contains H1, H2, H3, and VC-4 payload bytes. The pointer value is shown in the H3 bytes. In Frame 1, the pointer value is n. In Frame 2, it is n-1. In Frame 3, the D-bits are inverted and the pointer value is n-2, with three negative justification bytes (data) following. In Frame 4, the pointer value is n-1. Arrows indicate the movement of the Start of VC-4 pointer across the frames.
+
+Figure 8-6 – AU-4 pointer adjustment operation – Negative justification
+
+For AU-3 frames, a negative justification byte appears in the individual H3 byte of the AU-3 frame containing inverted D-bits. Subsequent pointers will contain the new offset. This is illustrated in Figure 8-7.
+
+
+
+The diagram illustrates the AU-3 pointer adjustment operation for negative justification across four frames. The horizontal axis represents the AUG (AU-3 Group) from byte 1 to 270. The vertical axis shows the sequence of frames over time, with each frame lasting 125 μs. Each frame contains a pointer word (bits 1-10) and a payload. In Frame 1, the pointer points to the start of VC-3 #3. In Frame 2, the pointer value is n. In Frame 3, the pointer value is n-1, and a negative justification byte for VC-3 #3 is inserted. In Frame 4, the pointer value is n-1. Arrows indicate the pointer operating on VC-3 #3.
+
+| Frame | Time | Pointer Value | Notes |
+|---------|--------------|------------------|-----------------------------------------|
+| Frame 1 | 0 - 125 μs | Start of VC-3 #3 | |
+| Frame 2 | 125 - 250 μs | n | |
+| Frame 3 | 250 - 375 μs | n-1 | Negative justification byte for VC-3 #3 |
+| Frame 4 | 375 - 500 μs | n-1 | |
+
+↑ Indicates pointer operating on the VC-3 #3
+
+G.707-Y.1322\_F8-7
+
+Figure 8-7: AU-3 pointer adjustment operation – Negative justification. The diagram shows four frames (Frame 1 to Frame 4) over time (125 μs intervals). Each frame contains a pointer word (bits 1-10) and a payload. In Frame 1, the pointer points to the start of VC-3 #3. In Frame 2, the pointer value is n. In Frame 3, the pointer value is n-1, and a negative justification byte for VC-3 #3 is inserted. In Frame 4, the pointer value is n-1. Arrows indicate the pointer operating on VC-3 #3.
+
+**Figure 8-7 – AU-3 pointer adjustment operation – Negative justification**
+
+### 8.1.4 New data flag (NDF)
+
+Bits 1-4 (N-bits) of the pointer word carry an NDF which allows an arbitrary change of the pointer value if that change is due to a change in the payload.
+
+Four bits are allocated to the flag to allow error correction. Normal operation is indicated by a "0110" code in the N-bits. NDF is indicated by inversion of the N-bits to "1001". An NDF should be interpreted as enabled when three or more of the four bits match the pattern "1001". An NDF should be interpreted as disabled when three or more of the four bits match the pattern "0110". The remaining values (i.e., "0000", "0011", "0101", "1010", "1100" and "1111") should be interpreted as invalid. The new alignment is indicated by the pointer value accompanying the NDF and takes effect at the offset indicated.
+
+### 8.1.5 Pointer generation
+
+The following summarizes the rules for generating the AU-n pointers:
+
+- 1) During normal operation, the pointer locates the start of the VC-n within the AU-n frame. The NDF is set to "0110".
+- 2) The pointer value can only be changed by operation 3, 4 or 5.
+- 3) If a positive justification is required, the current pointer value is sent with the I-bits inverted and the subsequent positive justification opportunity is filled with dummy information. Subsequent pointers contain the previous pointer value incremented by one. If the previous
+
+pointer is at its maximum value, the subsequent pointer is set to zero. No subsequent increment or decrement operation is allowed for at least three frames following this operation.
+
+- 4) If a negative justification is required, the current pointer value is sent with the D-bits inverted and the subsequent negative justification opportunity is overwritten with actual data. Subsequent pointers contain the previous pointer value decremented by one. If the previous pointer value is zero, the subsequent pointer is set to its maximum value. No subsequent increment or decrement operation is allowed for at least three frames following this operation.
+- 5) If the alignment of the VC-n changes for any reason other than rules 3 or 4, the new pointer value shall be sent accompanied by NDF set to "1001". The NDF only appears in the first frame that contains the new values. The new location of the VC-n begins at the first occurrence of the offset indicated by the new pointer. No subsequent increment or decrement operation is allowed for at least three frames following this operation.
+
+### **8.1.6 Pointer interpretation**
+
+The following summarizes the rules for interpreting the AU-n pointers:
+
+- 1) During normal operation, the pointer locates the start of the VC-n within the AU-n frame.
+- 2) Any variation from the current pointer value is ignored unless a consistent new value is received three times consecutively or it is preceded by one of the rules 3, 4 or 5. Any consistent new value received three times consecutively overrides (i.e., takes priority over) rules 3 or 4.
+- 3) If the majority of the I-bits of the pointer word are inverted, a positive justification operation is indicated. Subsequent pointer values shall be incremented by one.
+- 4) If the majority of the D-bits of the pointer word are inverted, a negative justification operation is indicated. Subsequent pointer values shall be decremented by one.
+- 5) If the NDF is interpreted as enabled, then the coincident pointer value shall replace the current one at the offset indicated by the new pointer value unless the receiver is in a state that corresponds to a loss of pointer.
+
+### **8.1.7 AU-4 concatenation**
+
+See clauses 11.1 and 11.2.
+
+## **8.2 TU-3 pointer**
+
+The TU-3 pointer provides a method of allowing flexible and dynamic alignment of VC-3 within the TU-3 frame, independent of the actual content of the VC-3.
+
+### 8.2.1 TU-3 pointer location
+
+Three individual TU-3 pointers are contained in three separate H1, H2 and H3 bytes as shown in Figure 8-8.
+
+
+
+Figure 8-8: TU-3 pointer offset numbering diagram. It shows the structure of an AUG (Administrative Unit Group) frame, which is 261 bytes long, starting at byte 10 and ending at byte 270. The diagram illustrates the placement of TU-3 pointers (H1, H2, H3) within the frame. The first pointer is located in the first AUG frame, with H1, H2, and H3 bytes at offsets 10, 11, and 12 respectively. The second pointer is located in the second AUG frame, with H1, H2, and H3 bytes at offsets 139, 140, and 141. The third pointer is located in the third AUG frame, with H1, H2, and H3 bytes at offsets 268, 269, and 270. The diagram also shows the AU-4 pointer, which points to the start of the AUG. The AU-4 pointer is located in the first byte of the first AUG frame (byte 10). The AU-4 pointer value is 125 μs. The diagram also shows the fixed stuff bytes (J1, B3, C2, G1, F2, H4, F3, K3, N1) and the VC-3 payload bytes (83, 83, 83, 84, 84, 84, 593, 593, 593, 594, 594, 594, 763, 763, 763, 764, 764, 764).
+
+G.707-Y.1322\_F8-8
+
+Figure 8-8 – TU-3 pointer offset numbering
+
+### 8.2.2 TU-3 pointer value
+
+The TU-3 pointer value contained in H1 and H2 designates the location of the byte where the VC-3 begins. The two bytes allocated to the pointer function can be viewed as one word as shown in Figure 8-3. The last ten bits (bits 7-16) of the pointer word carry the pointer value.
+
+The TU-3 pointer value is a binary number with a range of 0-764 which indicates the offset between the pointer and the first byte of the VC-3 as shown in Figure 8-8.
+
+### 8.2.3 Frequency justification
+
+If there is a frequency offset between the TU-3 frame rate and that of the VC-3, then the pointer value will be incremented or decremented as needed accompanied by a corresponding positive or negative justification byte. Consecutive pointer operations must be separated by at least three frames in which the pointer value remains constant.
+
+If the frame rate of the VC-3 is too slow with respect to that of the TU-3 frame rate, then the alignment of the VC-3 must periodically slip back in time and the pointer must be incremented by one. This operation is indicated by inverting bits 7, 9, 11, 13 and 15 (I-bits) of the pointer word to allow 5-bit majority voting at the receiver. A positive justification byte appears immediately after the individual H3 byte in the TU-3 frame containing inverted I-bits. Subsequent TU-3 pointers will contain the new offset.
+
+If the frame rate of the VC-3 is too fast with respect to that of the TU-3 frame rate, then the alignment of the VC-3 must be periodically advanced in time and the pointer must be decremented by one. This operation is indicated by inverting bits 8, 10, 12, 14 and 16 (D-bits) of the pointer word to allow 5-bit majority voting at the receiver. A negative justification byte appears in the individual H3 byte in the TU-3 frame containing inverted D-bits. Subsequent TU-3 pointers will contain the new offset.
+
+### 8.2.4 New data flag (NDF)
+
+Bits 1-4 (N-bits) of the pointer word carry an NDF which allows an arbitrary change of the value of the pointer if that change is due to a change in the VC-3.
+
+Four bits are allocated to the flag to allow error correction. Normal operation is indicated by a "0110" code in the N-bits. NDF is indicated by inversion of the N-bits to "1001". An NDF should be interpreted as enabled when three or more of the four bits match the pattern "1001". An NDF should be interpreted as disabled when three or more of the four bits match the pattern "0110". The remaining values (i.e., "0000", "0011", "0101", "1010", "1100" and "1111") should be interpreted as invalid. The new alignment is indicated by the pointer value accompanying the NDF and takes effect at the offset indicated.
+
+### 8.2.5 Pointer generation
+
+The following summarizes the rules for generating the TU-3 pointers:
+
+- 1) During normal operation, the pointer locates the start of the VC-3 within the TU-3 frame. The NDF is set to "0110".
+- 2) The pointer value can only be changed by operation 3, 4 or 5.
+- 3) If a positive justification is required, the current pointer value is sent with the I-bits inverted and the subsequent positive justification opportunity is filled with dummy information. Subsequent pointers contain the previous pointer value incremented by one. If the previous pointer is at its maximum value, the subsequent pointer is set to zero. No subsequent increment or decrement operation is allowed for at least three frames following this operation.
+- 4) If a negative justification is required, the current pointer value is sent with the D-bits inverted and the subsequent negative justification opportunity is overwritten with actual data. Subsequent pointers contain the previous pointer value decremented by one. If the previous pointer value is zero, the subsequent pointer is set to its maximum value. No subsequent increment or decrement operation is allowed for at least three frames following this operation.
+- 5) If the alignment of the VC-3 changes for any reason other than rules 3 or 4, the new pointer value shall be sent accompanied by the NDF set to "1001". The NDF only appears in the first frame that contains the new value. The new VC-3 location begins at the first occurrence of the offset indicated by the new pointer. No subsequent increment or decrement operation is allowed for at least three frames following this operation.
+
+### 8.2.6 Pointer interpretation
+
+The following summarizes the rules for interpreting the TU-3 pointers:
+
+- 1) During normal operation the pointer locates the start of the VC-3 within the TU-3 frame.
+- 2) Any variation from the current pointer value is ignored unless a consistent new value is received three times consecutively or it is preceded by one of rules 3, 4 or 5. Any consistent new value received three times consecutively overrides (i.e., takes priority over) rules 3 or 4.
+- 3) If the majority of the I-bits of the pointer word are inverted, a positive justification is indicated. Subsequent pointer values shall be incremented by one.
+- 4) If the majority of the D-bits of the pointer word are inverted, a negative justification is indicated. Subsequent pointer values shall be decremented by one.
+- 5) If the NDF is interpreted as enabled, then the coincident pointer value shall replace the current one at the offset indicated by the new pointer value unless the receiver is in a state that corresponds to a loss of pointer.
+
+## 8.3 TU-2, TU-12 and TU-11 pointers
+
+The TU-11, TU-12 and TU-2 pointers provide a method of allowing flexible and dynamic alignment of the VC-11, VC-12 and VC-2 within the TU-11, TU-12 and TU-2 multiframes, independent of the actual contents of the VC-11, VC-12 and VC-2.
+
+### 8.3.1 TU-2, TU-12 and TU-11 pointer location
+
+The TU-2, TU-12 and TU-11 pointers are contained in the V1 and V2 bytes as illustrated in Figure 8-9.
+
+
+
+The diagram illustrates the mapping of Virtual Containers (VCs) within a Tributary Unit (TU) over a 500 μs period. The TU-n structure includes pointers V1, V2, V3, and V4, with V1 and V2 indicating the start of the VC-n structure. The VC-n structure includes V5, J2, N2, and K4. The following table shows the VC capacity in bytes per 500 μs for different VC types:
+
+| VC-11 | VC-12 | VC-2 |
+|---------------------------|-------|------|
+| 26 | 35 | 107 |
+| 26 | 35 | 107 |
+| 26 | 35 | 107 |
+| 26 | 35 | 107 |
+| 104 | 140 | 428 |
+| VC capacity (byte/500 μs) | | |
+
+Diagram illustrating virtual container mapping in a multiframed tributary unit. It shows the relationship between TU-n pointers (V1, V2, V3, V4) and VC-n containers (V5, J2, N2, K4) over a 500 μs period. The diagram includes byte addresses (XXXXX00 to XXXXXX11) and a table of VC capacity in bytes per 500 μs for VC-11, VC-12, and VC-2.
+
+TU Tributary Unit
+ VC Virtual Container
+ V1 TU Pointer 1
+ V2 TU Pointer 2
+ V3 TU Pointer 3 (action)
+ V4 Reserved
+
+G.707/Y.1322COR.1\_F8-9
+
+NOTE – V1, V2, V3 and V4 bytes are part of the TU-n and are terminated at the pointer processor.
+
+**Figure 8-9 – Virtual container mapping in multiframed tributary unit**
+
+### 8.3.2 TU-2, TU-12 and TU-11 pointer value
+
+The tributary unit pointer word is shown in Figure 8-10. The two S bits (bits 5 and 6) indicate the tributary unit type.
+
+
+
+The diagram illustrates the structure of the tributary unit pointer word, which consists of two 16-bit words, V1 and V2.
+
+**V1 and V2 Structure:**
+
+| | | | | | | | | | | | | | | | | |
+|----|----------------------------------------------------|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|
+| V1 | PTR1 | | | | | | | | | | | | | | | |
+| V2 | PTR2 | | | | | | | | | | | | | | | |
+| | ← Zero pointer offset location | | | | | | | | | | | | | | | |
+| V3 | PTR3 (action) ← Negative justification opportunity | | | | | | | | | | | | | | | |
+| | ← Positive justification opportunity | | | | | | | | | | | | | | | |
+| V4 | Reserved | | | | | | | | | | | | | | | |
+
+**V1 and V2 Bit Structure:**
+
+| V1 | | | | | | | | V2 | | | | | | | |
+|-----------------------|---|---|---|---|---|---|---|----|---|---|---|---|---|---|---|
+| N | N | N | N | S | S | I | D | I | D | I | D | I | D | I | D |
+| (S bits specify size) | | | | | | | | | | | | | | | |
+
+**Tributary Unit Pointer Word Structure:**
+
+| | | | | | | | | | | | | | | | | |
+|-------|--|-----|---|---|----------------------|--|--|--|--|--|--|--|--|--|--|--|
+| TU-2 | | NDF | 0 | 0 | 10-bit pointer value | | | | | | | | | | | |
+| TU-12 | | NDF | 1 | 0 | 10-bit pointer value | | | | | | | | | | | |
+| TU-11 | | NDF | 1 | 1 | 10-bit pointer value | | | | | | | | | | | |
+
+**Legend:**
+
+- I Increment
+- D Decrement
+- N New Data Flag
+
+**New data flag**
+
+- Enabled when at least 3 out of 4 bits match "1001"
+- Disabled when at least 3 out of 4 bits match "0110"
+- Invalid with other codes
+
+**Negative justification**
+
+- Invert 5 D-bits
+- Accept majority vote
+
+**Positive justification**
+
+- Invert 5 I-bits
+- Accept majority vote
+
+**Pointer value**
+
+Normal range is:
+
+- for TU-2: 0-427 decimal
+- for TU-12: 0-139 decimal
+- for TU-11: 0-103 decimal
+
+**Concatenation indication**
+
+- 1001SS11111111 (SS bits are unspecified)
+
+G.707-Y.1322\_F8-10
+
+Diagram of TU-2, TU-12, and TU-11 pointer coding showing V1 and V2 pointer words, their bit structures, and specific pointer value ranges for each tributary unit type.
+
+**Figure 8-10 – TU-2, TU-12 and TU-11 pointer coding**
+
+The pointer value (bits 7-16) is a binary number which indicates the offset from V2 to the first byte of the VC-2, VC-12 or VC-11. The range of the offset is different for each of the tributary unit sizes as illustrated in Figure 8-11. The pointer bytes are not counted in the offset calculation.
+
+
+
+Diagram illustrating the pointer offsets for TU-2, TU-12, and TU-11. The diagram shows the byte structure of each tributary unit, with V1, V2, V3, and V4 bytes highlighted. The offsets for V1 are 78 for TU-11, 105 for TU-12, and 321 for TU-2. The offsets for V2 are 0 for TU-11, 139 for TU-12, and 427 for TU-2. The offsets for V3 are 26 for TU-11, 35 for TU-12, and 106 for TU-2. The offsets for V4 are 52 for TU-11, 70 for TU-12, and 214 for TU-2. Arrows indicate the negative and positive justification opportunities for V3 in TU-2.
+
+Legend:
+
+- V1 PTR1
+- V2 PTR2
+- V3 PTR3 (action)
+- V4 Reserved
+
+Figure 8-11: TU-2, TU-12 and TU-11 pointer offsets diagram. It shows three vertical columns representing the byte structure of TU-11, TU-12, and TU-2. Each column contains bytes V1, V2, V3, and V4 at specific offsets. TU-11 starts at offset 0, TU-12 at 105, and TU-2 at 321. Arrows point to V3 in the TU-2 column, labeling it as a 'Negative justification opportunity' and the byte immediately following as a 'Positive justification opportunity'.
+
+Figure 8-11 – TU-2, TU-12 and TU-11 pointer offsets
+
+### 8.3.3 TU-2, TU-12 and TU-11 frequency justification
+
+The TU-2, TU-12 and TU-11 pointers are used to frequency justify the VC-2, VC-12 and VC-11 exactly in the same way that the TU-3 pointer is used to frequency justify the VC-3. A positive justification opportunity immediately follows the V3 byte. Additionally, V3 serves as the negative justification opportunity such that when the opportunity is taken, V3 is overwritten by data. This is also shown in Figure 8-11. The indication of whether or not a justification opportunity has been taken is provided by the I- and D-bits of the pointer in the current tributary unit multiframe. The value contained in V3 when not being used for a negative justification is not defined. The receiver is required to ignore the value contained in V3 whenever it is not used for negative justification.
+
+### 8.3.4 New data flag (NDF)
+
+Bits 1-4 (N-bits) of the pointer word carry an NDF. It is the mechanism which allows an arbitrary change of the value of a pointer.
+
+As with the TU-3 pointer NDF, the normal value is "0110", and the value "1001" indicates a new alignment for the VC-n, and possibly new size. An NDF should be interpreted as enabled when three or more of the four bits match the pattern "1001". An NDF should be interpreted as disabled when three or more of the four bits match the pattern "0110". The remaining values (i.e., "0000", "0011", "0101", "1010", "1100" and "1111") should be interpreted as invalid. The new alignment is indicated by the pointer value and size value accompanying the NDF and takes effect at the offset indicated.
+
+### 8.3.5 TU-2, TU-12 and TU-11 pointer generation and interpretation
+
+The rules for generating and interpreting the TU-2, TU-12 and TU-11 pointers for the VC-2, VC-12 and VC-11 are an extension to the rules provided in clauses 8.2.5 and 8.2.6 for the TU-3 pointer with the following modification:
+
+- The term TU-3 is replaced with TU-2, TU-12 or TU-11 and the term VC-3 is replaced with VC-2, VC-12 or VC-11.
+
+### 8.3.6 TU-2 concatenation
+
+See clauses 11.3 and 11.4.
+
+### 8.3.7 TU-2, TU-12 and TU-11 sizes
+
+Bits 5 and 6 of TU-2, TU-12 and TU-11 pointers indicate the size of the TU-m. Three sizes are currently provided; they are defined in Table 8-1 below:
+
+**Table 8-1 – TU-2, TU-12 and TU-11 sizes**
+
+| Size | Designation | TU-m pointer range (in 500 µs) |
+|-------------------------------------------------------------------------|-------------|-----------------------------------|
+| 00 | TU-2 | 0-427 |
+| 10 | TU-12 | 0-139 |
+| 11 | TU-11 | 0-103 |
+| NOTE – This technique is only used at the TU-2, TU-12 and TU-11 levels. | | |
+
+### 8.3.8 TU-2, TU-12 and TU-11 multiframe indication byte
+
+TU-2, TU-12 and TU-11 multiframe indication byte (H4) relates to the lowest level of the multiplexing structure and provides a 500 µs (4-frame) multiframe identifying frames containing the TU-2, TU-12 or TU-11 pointers. Figure 8-9 shows the VC-2, VC-12 and VC-11 mapping in the multiframe TU-2, TU-12 and TU-11.
+
+The value of the H4 byte, read from the VC-4/VC-3 POH, identifies the frame phase of the next VC-4/VC-3 payload as shown in Figure 8-12. The coding of the H4 byte is illustrated in Figure 8-13.
+
+
+
+Diagram of TU-2, TU-12 and TU-11 500 µs multiframe structure. It shows a vertical stack of frames. Each frame contains a POH section (H4, PTR) and a VC-3/VC-4 payload. The H4 byte values are H4(00), H4(01), H4(10), H4(11), and then repeating H4(00). The PTR values are (V4), PTR (V1), PTR (V2), PTR (V3), and (V4). A vertical double-headed arrow on the right indicates a duration of 9 rows.
+
+In H4 (XY), XY represent bits 7 and 8 of H4.
+
+**Figure 8-12 – TU-2, TU-12 and TU-11 500 µs multiframe indication using H4 byte**
+
+| H4 bits | | | | | | | | Frame No. | Time |
+|---------|---|---|---|---|---|---|---|-----------|------------------------|
+| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | | |
+| X | X | 1 | 1 | X | X | 0 | 0 | 0 | 0 |
+| X | X | 1 | 1 | X | X | 0 | 1 | 1 | |
+| X | X | 1 | 1 | X | X | 1 | 0 | 2 | |
+| X | X | 1 | 1 | X | X | 1 | 1 | 3 | 500 µs TU-m multiframe |
+
+X Bit reserved for future international standardization. Its content shall be set to "1" in the interim.
+
+**Figure 8-13 – Tributary unit multiframe indicator byte (H4) coding sequence**
+
+# 9 Overhead bytes description
+
+## 9.1 Types of overhead
+
+Several types of overhead have been identified for application in the SDH.
+
+### 9.1.1 SOH
+
+SOH information is added to the information payload to create an STM-N. It includes block framing information and information for maintenance, performance monitoring and other operational functions. The SOH information is further classified into regenerator section overhead (RSOH) which is terminated at regenerator functions and multiplex section overhead (MSOH) which passes transparently through regenerators and is terminated where the AUG-Ns are assembled and disassembled.
+
+NOTE – The FEC overhead defined in clause 9.2.4 uses both RSOH and MSOH. As the FEC is defined for the multiplex section, the FEC overhead located in the RSOH is not terminated at regenerator functions.
+
+The rows 1-3 of the SOH are designated as RSOH while rows 5-9 are designated to be MSOH. This is illustrated in Figure 9-3 for the case of STM-1.
+
+The SOH description is given in clause 9.2.
+
+### 9.1.2 Virtual container POH
+
+Virtual container POH provides for integrity of communication between the point of assembly of a virtual container and its point of disassembly. Two categories of virtual container POH have been identified:
+
+#### – *Higher order virtual container POH (VC-4/VC-3 POH)*
+
+VC-3 POH is added to either an assembly of TUG-2s or a container-3 to form a VC-3. VC-4 POH is added to either an assembly of TUG-3s or a container-4 to form a VC-4. Amongst the functions included within this overhead are virtual container path performance monitoring, alarm status indications, signals for maintenance purposes and multiplex structure indications (VC-4/VC-3 composition).
+
+#### – *Lower order virtual container POH (VC-3/VC-2/VC-12/VC-11 POH)*
+
+Lower order VC-m (m=11, 12, 2, 3) POH is added to the Container-m to form a VC-m. Among the functions included in this overhead are virtual container path performance monitoring, signals for maintenance purposes and alarm status indications.
+
+The POH descriptions are given in clause 9.3.
+
+## 9.2 SOH description
+
+### 9.2.1 SOH bytes location
+
+The location of SOH bytes within an STM-N, $N \geq 1$ , frame is identified by a three-coordinate vector S (a, b, c) where a (1 to 3, 5 to 9) represents the row number, b (1 to 9) represents a multi-column number and c (1 to N) represents the depth of the interleave within the multi-column. This is illustrated in Figure 9-1.
+
+The relationship between the row and column numbers and the coordinates is given by:
+
+- $\text{Row} = a;$
+- $\text{Column} = N (b-1) + c.$
+
+For example the K1 byte in an STM-1 is located at S (5, 4, 1) or at [5, 4] in [row, column] notation.
+
+For STM-0, identification of the SOH bytes by a three-coordinate vector is unnecessary since all STM-0 SOH bytes have a name.
+
+
+
+Figure 9-1 illustrates the numbering of SOH byte locations for STM-N. The diagram shows a grid of bytes organized into rows (a=1 to a=9) and columns grouped by STM-N sections (b=1, b=2, b=3, ..., b=9). Within each section, columns are labeled c=1, c=2, ..., c=N. Row 4 is designated for 'AU-n pointers'. The diagram is labeled G.707-Y.1322\_F9-1.
+
+Figure 9-1: Numbering of SOH byte locations for STM-N. A grid diagram showing rows a=1 to a=9 and columns grouped by STM-N sections b=1, b=2, b=3, and b=9. Columns are labeled c=1, c=2, c=N within each section. Row 4 contains 'AU-n pointers'.
+
+**Figure 9-1 – Numbering of SOH byte locations for STM-N**
+
+The assignment of the various SOH bytes in the STM-0/1/4/16/64/256 frames is illustrated in Figures 9-2 to 9-7.
+
+NOTE – Scrambling of the STM-N frames is described in clause 6.5.
+
+
+
+Figure 9-2 illustrates the STM-0 SOH structure. It shows a 9x3 grid of bytes. The first three rows (A1, A2, J0 to D1, D2, D3) are labeled RSOH. The remaining six rows (B2, K1, K2 to S1, M1, E2) are labeled MSOH. A legend indicates that grey cells are 'Unscrambled bytes'. The diagram is labeled G.707-Y.1322\_F9-2.
+
+Figure 9-2: STM-0 SOH. A 9x3 grid of bytes. The first three rows (A1, A2, J0 to D1, D2, D3) are labeled RSOH. The remaining six rows (B2, K1, K2 to S1, M1, E2) are labeled MSOH. A legend indicates that grey cells are 'Unscrambled bytes'.
+
+**Figure 9-2 – STM-0 SOH**
+
+9 bytes
+
+| | | | | | | | | | | |
+|--------------------------------|-----|----|----|-----|----|----|-----|---|---|--------|
+| 9 rows | A1 | A1 | A1 | A2 | A2 | A2 | J0 | * | * | } RSOH |
+| | B1 | Δ | Δ | E1 | Δ | | F1 | | | |
+| | D1 | Δ | Δ | D2 | Δ | | D3 | | | |
+| Administrative unit pointer(s) | | | | | | | | | | |
+| | B2 | B2 | B2 | K1 | | | K2 | | | } MSOH |
+| | D4 | | | D5 | | | D6 | | | |
+| | D7 | | | D8 | | | D9 | | | |
+| | D10 | | | D11 | | | D12 | | | |
+| | S1 | | | | | M1 | E2 | | | |
+
+G.707-Y.1322\_F9-3
+
+- Unscrambled bytes
+- Bytes reserved for national use
+- \* The content of these reserved bytes has to be carefully selected as they are not scrambled
+- Media-dependent bytes
+
+NOTE – All unmarked bytes are reserved for future international standardization (for media-dependent, additional national use and other purposes).
+
+### Figure 9-3 – STM-1 SOH
+
+36 bytes
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------|-----|---|--|--|--|--|--|--|--|----|---|--|-----|--|--|----|--|--|--|--|--|--|--|----|-----|----|----|----|---|---|---|---|---|---|---|---|--------|
+| 9 rows | A1 | | | | | | | | | | | | A2 | | | | | | | | | | | | J0 | Z0 | Z0 | Z0 | * | * | * | * | * | * | * | * | } RSOH |
+| | B1 | Δ | | | | | | | | E1 | Δ | | | | | F1 | | | | | | | | | | | | | | | | | | | | | |
+| | D1 | Δ | | | | | | | | D2 | Δ | | | | | D3 | | | | | | | | | | | | | | | | | | | | | |
+| Administrative Unit pointer(s) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | B2 | | | | | | | | | | | | K1 | | | | | | | | | | | | K2 | | | | | | | | | | | | } MSOH |
+| | D4 | | | | | | | | | | | | D5 | | | | | | | | | | | | D6 | | | | | | | | | | | | |
+| | D7 | | | | | | | | | | | | D8 | | | | | | | | | | | | D9 | | | | | | | | | | | | |
+| | D10 | | | | | | | | | | | | D11 | | | | | | | | | | | | D12 | | | | | | | | | | | | |
+| | S1 | | | | | | | | | | | | | | | | | | | | | | | M1 | | E2 | | | | | | | | | | | |
+
+G.707-Y.1322\_F9-4
+
+- Unscrambled bytes
+- Bytes reserved for national use
+- \* The content of these reserved bytes has to be carefully selected as they are not scrambled
+- Δ Media-dependent bytes
+
+NOTE – All unmarked bytes are reserved for future international standardization (for media-dependent, additional national use and other purposes).
+
+### Figure 9-4 – STM-4 SOH
+
+66 ITU-T Rec. G.707/Y.1322 (01/2007)
+
+
+
+144 bytes
+
+| | | | | | | | | | | | | | | | | | | | |
+|--------|--------------------------------|----|----|----|----|----|-----|----|----|----|----|----|-----|---|---|---|---|------|------|
+| 9 rows | A1 | A1 | A1 | A1 | A1 | A1 | A2 | A2 | A2 | A2 | A2 | J0 | *Z0 | * | * | * | * | RSOH | |
+| | B1 | † | D | D | D | D | E1 | † | D | D | | † | F1 | ⊗ | ⊗ | ⊗ | ⊗ | | ⊗ |
+| | D1 | † | D | D | D | D | D2 | † | D | D | | † | D3 | † | | † | | | ‡ |
+| | Administrative unit pointer(s) | | | | | | | | | | | | | | | | | | MSOH |
+| | B2 | B2 | B2 | B2 | B2 | B2 | K1 | † | | † | | † | K2 | † | | † | | † | |
+| | D4 | | | | | | D5 | | | | | | D6 | † | | † | | † | |
+| | D7 | | | | | | D8 | | | | | | D9 | † | | † | | † | |
+| | D10 | | | | | | D11 | | | | | | D12 | † | | † | | † | |
+| | S1 | † | | † | | † | | | | | | | E2 | ⊗ | ⊗ | ⊗ | ⊗ | ⊗ | |
+
+c = 2 16
+
+| | | | | | |
+|---|--|----|----|--|----|
+| † | | P1 | P1 | | P1 |
+|---|--|----|----|--|----|
+
+c = 2 16
+
+| | | | | | |
+|---|----|----|----|--|----|
+| ‡ | Q1 | P1 | P1 | | P1 |
+|---|----|----|----|--|----|
+
+Unscrambled bytes
+
+
+ Bytes reserved for national use
+ \* The content of these reserved bytes has to be carefully selected as they are not scrambled
+ D Media-dependent bytes
+ †, ‡ P1 and Q1 reserved for FEC
+
+NOTE – All unmarked bytes are reserved for future international standardization (for media-dependent, additional national use and other purposes).
+
+G.707-Y.1322\_F9-5
+
+Diagram showing a callout from the Administrative unit pointer(s) section to a small 4-byte box containing M1.
+
+**Figure 9-5 – STM-16 SOH**
+
+
+
+576 bytes
+
+| | | | | | | | | | | | | | | | | | | | |
+|--------|--------------------------------|----|----|----|----|----|-----|----|----|----|----|----|-----|------|---|---|---|---|------|
+| 9 rows | A1 | A1 | A1 | A1 | A1 | A1 | A2 | A2 | A2 | A2 | A2 | A2 | J0 | * Z0 | * | * | * | * | RSOH |
+| | B1 | † | D | D | D | D | E1 | † | D | D | | † | F1 | ✖ | ✖ | ✖ | ✖ | ✖ | |
+| | D1 | † | D | D | D | D | D2 | † | D | D | | † | D3 | † | | † | | ‡ | |
+| | Administrative unit pointer(s) | | | | | | | | | | | | | | | | | | |
+| | B2 | B2 | B2 | B2 | B2 | B2 | K1 | † | | † | | † | K2 | † | | † | | † | MSOH |
+| | D4 | | | | | | D5 | | | | | | D6 | † | | † | | † | |
+| | D7 | | | | | | D8 | | | | | | D9 | † | | † | | † | |
+| | D10 | | | | | | D11 | | | | | | D12 | † | | † | | † | |
+| | S1 | † | | † | | † | | | | | | | E2 | ✖ | ✖ | ✖ | ✖ | ✖ | |
+
+| | | | |
+|----|----|--|--|
+| M0 | M1 | | |
+|----|----|--|--|
+
+$M = 1 \dots 4$
+
+$c = 2$
+ $\uparrow$
+†
+
+| | | | | | | |
+|--------------------------|--|---------------------------|--|---------------------------|--|---------------------------|
+| $\underset{4}{\uparrow}$ | | $\underset{16}{\uparrow}$ | | $\underset{20}{\uparrow}$ | | $\underset{64}{\uparrow}$ |
+| P1 | | P1 | | P1 | | P1 |
+
+(M-1)\*16+4
+
+M\*16
+
+
+
+$\ddagger$
+
+| | | | | | | | |
+|----|----|--|----|--|----|--|----|
+| Q1 | P1 | | P1 | | P1 | | P1 |
+|----|----|--|----|--|----|--|----|
+
+Unscrambled bytes
+✖ Bytes reserved for national use
+ \* The content of these reserved bytes has to be carefully selected as they are not scrambled
+ D Media-dependent bytes
+ †, ‡ P1 and Q1 reserved for FEC
+
+G.707-Y.1322\_F9-6
+
+NOTE – All unmarked bytes are reserved for future international standardization (for media-dependent, additional national use and other purposes).
+
+**Figure 9-6 – STM-64 SOH**
+
+
+
+The diagram illustrates the structure of the STM-256 SOH, which is 2304 bytes wide and 9 rows high. The RSOH (Residual Section Overhead) consists of the first 3 rows, and the MSOH (Multiplex Section Overhead) consists of the remaining 6 rows. The framing bytes A1 and A2 are located at the top of the frame. The administrative unit pointer(s) are located in the middle of the RSOH. The MSOH contains various bytes for management and monitoring. The diagram also shows the scrambling of bytes in the MSOH, with specific byte locations and values for different scrambling patterns (M=1...16).
+
+**Legend:**
+
+- Unscrambled bytes (shaded box)
+- Bytes reserved for national use (X)
+- D Media-dependent bytes
+- †, ‡ P1 and Q1 reserved for FEC
+
+**NOTE – All unmarked bytes are reserved for future international standardization (for media-dependent, additional national use and other purposes).**
+
+G.707-Y.1322\_F9-7
+
+Diagram of STM-256 SOH structure showing RSOH and MSOH sections with byte locations and scrambling details.
+
+**Figure 9-7 – STM-256 SOH**
+
+### 9.2.2 SOH bytes description
+
+#### 9.2.2.1 Framing: A1, A2
+
+Two types of bytes are defined for framing:
+
+- A1: 11110110
+- A2: 00101000
+
+The frame alignment word of an STM-0 frame is composed of one A1 byte followed by one A2 byte. The frame alignment word of an STM-N frame (N=1, 4, 16, 64) is composed of $3 \times N$ A1 bytes followed by $3 \times N$ A2 bytes. The frame alignment word of an STM-256 frame is composed of 64 A1 bytes in the locations S (1,3,193) [1,705] to S (1,3,256) [1,768] followed by 64 A2 bytes in the locations S (1,4,1) [1,769] to S (1,4,64) [1,832]. The bytes in locations S (1,1,1) [1,1] to S (1,3,192) [1,704] and S (1,4,65) [833] to S (1,9,256) [1,1536] are reserved for future international standardization (for media-dependent, additional national use and other purposes).
+
+**NOTE – For the reserved bytes in row 1 of the STM-256 frame, a pattern should be used that provides sufficient transitions and no significant DC unbalance after scrambling.**
+
+#### 9.2.2.2 Regenerator section trace: J0
+
+The J0 byte located at S (1,7,1) or [1,6N+1] in an STM-N is allocated to a regenerator section trace. This byte is used to transmit repetitively a section access point identifier so that a section receiver can verify its continued connection to the intended transmitter. Within a national network, or within the domain of a single operator, this section access point identifier may use either a single byte (containing the code 0-255) or the access point identifier format as defined in clause 3/G.831. At international boundaries, or at the boundaries between the networks of different operators, the format defined in clause 3/G.831 shall be used unless otherwise mutually agreed by the operators providing the transport.
+
+A 16-byte frame is defined for the transmission of section access point identifiers where these conform to the definition contained in clause 3/G.831. The first byte of the 16-byte frame is a header byte and includes the result of a CRC-7 calculation over the previous frame. The following 15 bytes are used for the transport of 15 T.50 characters (international reference version) required for the section access point identifier. The 16-byte frame description is given in Table 9-1:
+
+**Table 9-1 – 16-byte frame for trail API**
+
+| Byte # | Value (bit 1, 2, ..., 8) | | | | | | | |
+|--------|--------------------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|
+| | 1 | C 1 | C 2 | C 3 | C 4 | C 5 | C 6 | C 7 |
+| 1 | 1 | | | | | | | |
+| 2 | 0 | X | X | X | X | X | X | X |
+| 3 | 0 | X | X | X | X | X | X | X |
+| ⋮ | ⋮ | | | ⋮ | | | | |
+| 16 | 0 | X | X | X | X | X | X | X |
+
+NOTE 1 – 1000 0000 0000 0000 in bit 1 of each byte is the trace identifier frame alignment signal.
+
+NOTE 2 – C1 C2 C3 C4 C5 C6 C7 is the result of the CRC-7 calculation over the previous frame. C1 is the MSB. The description of this CRC-7 calculation is given in Annex B.
+
+NOTE 3 – XXXXXXX represents a T.50 character.
+
+For interworking of equipment employing the regenerator section trace function with old equipment implementing the STM identifier functionality (see Notes), the former shall be able to transmit the pattern "0000 0001" in J0.
+
+NOTE 1 – STM identifier: C1.
+
+NOTE 2 – In earlier versions of this Recommendation, the content of bytes located at S (1,7,1) or [1,6N+1] to S (1,7,N) or [1,7N] was defined as a unique identifier indicating the binary value of the multi-column, interleave depth coordinate, c. It may have been used to assist in frame alignment.
+
+#### 9.2.2.3 Spare: Z0
+
+These bytes, which are located at positions S (1,7,2) or [1,6N+2] to S (1,7,N) or [1,7N], are reserved for future international standardization.
+
+In case of interworking of equipment implementing the STM identifier functionality (see Note 1) and equipment employing the regenerator section trace function, these bytes shall be as defined in the note below.
+
+NOTE 1 – STM identifier: C1.
+
+NOTE 2 – In earlier versions of this Recommendation, the content of bytes located at S (1,7,1) or [1,6N+1] to S (1,7,N) or [1,7N] was defined as a unique identifier indicating the binary value of the multi-column, interleave depth coordinate, c. It may have been used to assist in frame alignment.
+
+#### **9.2.2.4 BIP-8: B1**
+
+One byte is allocated for regenerator section error monitoring. This function shall be a Bit Interleaved Parity 8 (BIP-8) code using even parity. The BIP-8 is computed over all bits of the previous STM-N frame after scrambling and is placed in byte B1 of the current frame before scrambling. (For details of the scrambling process, see clause 6.5.)
+
+NOTE – Bit Interleaved Parity-X (BIP-X) code is defined in clause 3.13.
+
+#### **9.2.2.5 Orderwire: E1, E2**
+
+These two bytes may be used to provide orderwire channels for voice communication. E1 is part of the RSOH and may be accessed at regenerators. E2 is part of the MSOH and may be accessed at multiplex section terminations.
+
+#### **9.2.2.6 User channel: F1**
+
+This byte is reserved for user purposes (e.g., to provide temporary data/voice channel connections for special maintenance purposes).
+
+#### **9.2.2.7 RS data communication channel (DCCR ): D1-D3**
+
+A 192 kbit/s channel is defined using bytes D1, D2 and D3 as a regenerator section DCC.
+
+#### **9.2.2.8 MS data communication channel (DCCM ): D4-D12**
+
+For STM-N (N=1, 4, 16, 64, 256), a 576 kbit/s channel is defined using bytes D4 to D12 as a multiplex section DCC.
+
+#### **9.2.2.9 Extended MS data communication channel (DCCMx ): D13-D156**
+
+For STM-256, an additional 9216 kbit/s channel is defined using bytes D13 to D156 as an extended multiplex section DCC.
+
+- D13 to D60 are located in S (6,1,9) to S (6,1,56).
+- D61 to D108 are located in S (7,1,9) to S (7,1,56).
+- D109 to D156 are located in S (8,1,9) to S (8,1,56).
+
+#### **9.2.2.10 BIP-N × 24: B2**
+
+The B2 bytes are allocated for a multiplex section error monitoring function. This function shall be a Bit Interleaved Parity N × 24 code (BIP-N × 24) using even parity. The BIP-N × 24 is computed over all bits of the previous STM-N frame except for the first three rows of SOH and is placed in bytes B2 of the current frame.
+
+For STM-0, N should be read as 1/3 giving a BIP-8.
+
+#### **9.2.2.11 Automatic protection switching (APS) channel: K1, K2 (b1-b5)**
+
+Two bytes are allocated for APS signalling for the protection of the multiplex section. The bit assignments for these bytes and the bit-oriented protocol are given in ITU-T Rec. G.841.
+
+#### **9.2.2.12 MS-RDI: K2 (b6-b8)**
+
+The multiplex section remote defect indication (MS-RDI) is used to return an indication to the transmit end that the received end has detected an incoming section defect or is receiving MS-AIS. MS-RDI is generated by inserting a "110" code in positions 6, 7 and 8 of the K2 byte before scrambling.
+
+#### 9.2.2.13 Synchronization status: S1 (b5-b8)
+
+Bits 5 to 8 of byte S (9,1,1) or [9,1] are allocated for synchronization status messages. Table 9-2 gives the assignment of bit patterns to the four synchronization levels agreed to within ITU-T. Two additional bit patterns are assigned: one to indicate that quality of the synchronization is unknown and the other to signal that the section should not be used for synchronization. The remaining codes are reserved for quality levels defined by individual operators.
+
+**Table 9-2 – Assignment of SSM bit patterns**
+
+| S1 bits b5-b8 | SDH synchronization quality level description |
+|------------------|----------------------------------------------------|
+| 0000 | Quality unknown (existing synchronization network) |
+| 0001 | Reserved |
+| 0010 | ITU-T Rec. G.811 |
+| 0011 | Reserved |
+| 0100 | SSU-A |
+| 0101 | Reserved |
+| 0110 | Reserved |
+| 0111 | Reserved |
+| 1000 | SSU-B |
+| 1001 | Reserved |
+| 1010 | Reserved |
+| 1011 | ITU-T Rec. G.813 Option I (SEC) |
+| 1100 | Reserved |
+| 1101 | Reserved |
+| 1110 | Reserved |
+| 1111 | Do not use for synchronization (Note) |
+
+NOTE – This message may be emulated by equipment failures and will be emulated by a multiplex section AIS signal. The assignment of the "do not use for synchronization" quality level message is mandatory because the receipt of a multiplex section AIS is not necessarily interpreted as an indication of a physical failed synchronization source interface port. This assignment allows this state to be recognized without interaction with the multiplex section AIS detection process.
+
+#### 9.2.2.14 MS-REI: M0, M1
+
+For STM-N (N=0, 1, 4, 16), one byte (M1) is allocated for use as a multiplex section remote error indication (MS-REI).
+
+For STM-N (N=64 and 256), two bytes (M0, M1) are allocated for use as a multiplex section remote error indication (MS-REI).
+
+NOTE 1 – Interworking of equipment that supports MS-REI and equipment that does not support MS-REI cannot be achieved automatically.
+
+NOTE 2 – STM-64 interfaces of equipment designed prior to the 2003 version of this Recommendation may support the single M1 REI only. STM-64 interfaces of new equipment has to be configurable to support the single byte M1 REI.
+
+For STM-N levels, this byte conveys the count (in the range of [0, 255/65 536]) of interleaved bit blocks that have been detected in error by the BIP-24×N (B2). For STM-0, the count is based on a BIP-8 in B2. For the rate of STM-16, this value shall be truncated to 255.
+
+**STM-0, M1 generation:** The byte shall be set to convey the count of interleaved bit blocks that have been detected in error by the BIP-8 in the range of [0, 8].
+
+**STM-0, M1 interpretation:** The value in the byte shall be interpreted as follows in Table 9-3:
+
+**Table 9-3 – STM-0 M1 interpretation**
+
+| M1[2-8] code, bits 234 5678 | Interpretation |
+|--------------------------------|------------------|
+| 000 0000 | 0 BIP violation |
+| 000 0001 | 1 BIP violation |
+| 000 0010 | 2 BIP violations |
+| 000 0011 | 3 BIP violations |
+| : | : |
+| 000 1000 | 8 BIP violations |
+| 000 1001 | 0 BIP violation |
+| 000 1010 | 0 BIP violation |
+| : | : |
+| 111 1111 | 0 BIP violation |
+| NOTE – Bit 1 of M1 is ignored. | |
+
+**STM-1, M1 generation:** The byte shall be set to convey the count of interleaved bit blocks that have been detected in error by the BIP-24 in the range of [0, 24].
+
+**STM-1, M1 interpretation:** The value in the byte shall be interpreted as follows in Table 9-4:
+
+**Table 9-4 – STM-1 M1 interpretation**
+
+| M1[2-8] code, bits 234 5678 | Interpretation |
+|--------------------------------|-------------------|
+| 000 0000 | 0 BIP violation |
+| 000 0001 | 1 BIP violation |
+| 000 0010 | 2 BIP violations |
+| 000 0011 | 3 BIP violations |
+| : | : |
+| 001 1000 | 24 BIP violations |
+| 001 1001 | 0 BIP violation |
+| 001 1010 | 0 BIP violation |
+| : | : |
+| 111 1111 | 0 BIP violation |
+| NOTE – Bit 1 of M1 is ignored. | |
+
+**STM-4, M1 generation:** The byte shall be set to convey the count of interleaved bit blocks that have been detected in error by the BIP-96 in the range of [0, 96].
+
+**STM-4, M1 interpretation:** The value in the byte shall be interpreted as follows in Table 9-5:
+
+**Table 9-5 – STM-4 M1 interpretation**
+
+| M1[2-8] code, bits 234 5678 | Interpretation |
+|--------------------------------|-------------------|
+| 000 0000 | 0 BIP violation |
+| 000 0001 | 1 BIP violation |
+| 000 0010 | 2 BIP violations |
+| 000 0011 | 3 BIP violations |
+| 000 0100 | 4 BIP violations |
+| 000 0101 | 5 BIP violations |
+| : | : |
+| 110 0000 | 96 BIP violations |
+| 110 0001 | 0 BIP violation |
+| 110 0010 | 0 BIP violation |
+| : | : |
+| 111 1111 | 0 BIP violation |
+| NOTE – Bit 1 of M1 is ignored. | |
+
+**STM-16, M1 generation:** The byte shall be set to convey the count of interleaved bit blocks that have been detected in error by the BIP-384 (in the range of [0, 255]) where the value conveyed is truncated at 255.
+
+**STM-16, M1 interpretation:** The value in the byte shall be interpreted as follows in Table 9-6:
+
+**Table 9-6 – STM-16 M1 interpretation**
+
+| M1[1-8] code, bits 1234 5678 | Interpretation |
+|---------------------------------|--------------------|
+| 0000 0000 | 0 BIP violation |
+| 0000 0001 | 1 BIP violation |
+| 0000 0010 | 2 BIP violations |
+| 0000 0011 | 3 BIP violations |
+| 0000 0100 | 4 BIP violations |
+| 0000 0101 | 5 BIP violations |
+| : | : |
+| 1111 1111 | 255 BIP violations |
+
+**STM-64, M0 and M1 generation:** The bytes shall be set to convey the count of interleaved bit blocks that have been detected in error by the BIP-1536 (in the range of [0, 1536]). M0 bit 1 is most significant bit and M1 bit 8 is least significant bit. If interworking with old equipment supporting the single byte REI in M1, the value conveyed is truncated at 255 and inserted in M1.
+
+**STM-64, M0 and M1 interpretation:** The value in M0 and M1 is interpreted as given in Table 9-7. If interworking with old equipment supporting the single byte REI in M1, the value in M1 is interpreted as given in Table 9-8.
+
+NOTE 3 – Interworking cannot be achieved automatically. It has to be configured by the management systems.
+
+**Table 9-7 – STM-64 M0 and M1 interpretation**
+
+| M0[1-8] code, bits 1234 5678 | M1[1-8] code, bits 1234 5678 | Interpretation |
+|---------------------------------|---------------------------------|---------------------|
+| 0000 0000 | 0000 0000 | 0 BIP violation |
+| 0000 0000 | 0000 0001 | 1 BIP violation |
+| 0000 0000 | 0000 0010 | 2 BIP violations |
+| 0000 0000 | 0000 0011 | 3 BIP violations |
+| 0000 0000 | 0000 0100 | 4 BIP violations |
+| 0000 0000 | 0000 0101 | 5 BIP violations |
+| | : | : |
+| 0000 0110 | 0000 0000 | 1536 BIP violations |
+| 0000 0110 | 0000 0001 | 0 BIP violation |
+| 0000 0110 | 0000 0010 | 0 BIP violation |
+| | : | : |
+| 1111 1111 | 1111 1111 | 0 BIP violation |
+
+**Table 9-8 – STM-64 M1 interpretation**
+
+| M1[1-8] code, bits 1234 5678 | Interpretation |
+|---------------------------------|--------------------|
+| 0000 0000 | 0 BIP violation |
+| 0000 0001 | 1 BIP violation |
+| 0000 0010 | 2 BIP violations |
+| 0000 0011 | 3 BIP violations |
+| 0000 0100 | 4 BIP violations |
+| 0000 0101 | 5 BIP violations |
+| : | : |
+| 1111 1111 | 255 BIP violations |
+
+**STM-256, M0, M1 generation:** The bytes shall be set to convey the count of interleaved bit blocks that have been detected in error by the BIP-6144 (in the range of [0, 6144]). M0 bit 1 is most significant bit and M1 bit 8 is least significant bit.
+
+**STM-256, M0, M1 interpretation:** The value in the byte shall be interpreted as follows in Table 9-9:
+
+**Table 9-9 – STM-256 M0 and M1 interpretation**
+
+| M0[1-8] code, bits 1234 5678 | M1[1-8] code, bits 1234 5678 | Interpretation |
+|-----------------------------------------|-----------------------------------------|-----------------------|
+| 0000 0000 | 0000 0000 | 0 BIP violation |
+| 0000 0000 | 0000 0001 | 1 BIP violation |
+| 0000 0000 | 0000 0010 | 2 BIP violations |
+| 0000 0000 | 0000 0011 | 3 BIP violations |
+| 0000 0000 | 0000 0100 | 4 BIP violations |
+| 0000 0000 | 0000 0101 | 5 BIP violations |
+| | : | : |
+| 0001 1000 | 0000 0000 | 6144 BIP violations |
+| 0001 1000 | 0000 0001 | 0 BIP violation |
+| 0001 1000 | 0000 0010 | 0 BIP violation |
+| | : | : |
+| 1111 1111 | 1111 1111 | 0 BIP violation |
+
+#### **9.2.2.15 Media-dependant bytes**
+
+These 6N bytes, which are located at positions S (2,2,X) or [2,N+X], S (2,3,X) or [2,2N+X], S (2,5,X) or [2,4N+X], S (3,2,X) or [3,N+X], S (3,3,X) or [3,2N+X], S (3,5,X) or [3,4N+X] with X=1...N, are reserved for media-dependent applications.
+
+The definition of these media-dependent bytes is outside the scope of this Recommendation.
+
+NOTE – For SDH radio these bytes are defined in ITU-R Recommendation F.750.
+
+### **9.2.3 Reduced SOH functionalities interface**
+
+For some applications (e.g., intra-station interface), an interface with reduced SOH functionalities can be used. The SOH bytes to be used for this interface are given in Table 9-10:
+
+**Table 9-10 – Reduced SOH functionalities interface**
+
+| SOH bytes | Transmit functionality | Receive functionality |
+|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| A1, A2 | Required | Required |
+| J0-Z0/C1 | Optional | Optional |
+| B1 | Required | Unused |
+| E1 | Unused | Unused |
+| F1 | Unused | Unused |
+| D1-D3 | Unused | Unused |
+| B2 | Required | Required |
+| K1, K2 (APS) | Optional | Optional |
+| K2 (MS-AIS) | Required | Required |
+| K2 (MS-RDI) | Required | Required |
+| D4-D12 | Unused | Unused |
+| S1 | Unused, 00001111 generated | Unused |
+| M1 | Required | Optional |
+| E2 | Unused | Unused |
+| Other bytes | Unused | Unused |
+| Required | These signals at the interface shall contain valid information as defined by this Recommendation. | |
+| Optional | Valid information may or may not be present in these signals. Use of these functions shall be a local matter. | |
+| Unused | This function is not defined at the interface. The contents should, if not specified otherwise, be either 00000000 or 11111111 according to regional standard. | |
+
+### 9.2.4 Forward error correction: P1, Q1
+
+For STM-16, STM-64 and STM-256, the P1 and Q1 bytes are reserved for an optional forward error correction (FEC) function. The FEC function and details for STM-64 and STM-256 of the usage of the P1 and Q1 bytes are given in Annex A. The FEC function and details for STM-16 of the usage of the P1 and Q1 bytes are given in Appendix IX.
+
+NOTE – See clause A.4 regarding the functionality and transparency of regenerators.
+
+## 9.3 POH descriptions
+
+### 9.3.1 VC-4-Xc/VC-4/VC-3 POH
+
+The VC-4-Xc POH is located in the first column of the 9-row by X × 261-column VC-4-Xc structure.
+
+The VC-4 POH is located in the first column of the 9-row by 261-column VC-4 structure.
+
+The VC-3 POH is located in the first column of the 9-row by 85-column VC-3 structure.
+
+The VC-4-Xc/VC-4/VC-3 POH consists of 9 bytes denoted J1, B3, C2, G1, F2, H4, F3, K3 and N1 (see Figures 11-1, 7-3 and 7-4). These bytes are classified as follows:
+
+- Bytes or bits used for end-to-end communication with independent payload function: J1, B3, C2, G1, K3 (b1-b4).
+- Payload type-specific bytes: H4, F2, F3.
+- Bits reserved for future international standardization: K3 (b5-b8).
+
+- Byte which can be overwritten in an operator domain (without affecting the end-to-end performance monitoring facility of the byte B3): N1.
+
+NOTE – Payload-dependent and payload-independent information is communicated by different codings in C2 byte and bits 5 to 7 of G1 byte.
+
+#### 9.3.1.1 Path trace: J1
+
+This is the first byte in the virtual container; its location is indicated by the associated AU-n (n=3, 4) or TU-3 pointer. This byte is used to transmit repetitively a path access point identifier so that a path receiving terminal can verify its continued connection to the intended transmitter. A 16-byte frame is defined for the transmission of an access point identifier. This 16-byte frame is identical to the 16-byte frame defined in clause 9.2.2.2 for the description of the byte J0. At international boundaries, or at the boundaries between the networks of different operators, the format defined in clause 3/G.831 shall be used unless otherwise mutually agreed by the operators providing the transport. Within a national network or within the domain of a single operator, this path access point identifier may use a 64-byte frame.
+
+#### 9.3.1.2 Path BIP-8: B3
+
+One byte is allocated in each VC-4-Xc/VC-4/VC-3 for a path error monitoring function. This function shall be a BIP-8 code using even parity. The path BIP-8 is calculated over all bits of the previous VC-4-Xc/VC-4/VC-3. The computed BIP-8 is placed in the B3 byte of the current VC-4-Xc/VC-4/VC-3.
+
+#### 9.3.1.3 Signal label: C2
+
+One byte is allocated to indicate the composition or the maintenance status of the VC-4-Xc/VC-4/VC-3. Table 9-11, which is based on Hex code, provides codes for this byte.
+
+**Table 9-11 – C2 byte coding**
+
+| MSB | | LSB | | Hex code (Note 1) | Interpretation |
+|-----|---|-----|---|----------------------|------------------------------------------------------------------------------------------------|
+| 1 | 2 | 3 | 4 | | |
+| 0 | 0 | 0 | 0 | 00 | Unequipped or supervisory-unequipped (Note 2) |
+| 0 | 0 | 0 | 0 | 01 | Reserved (Note 3) |
+| 0 | 0 | 0 | 0 | 02 | TUG structure, see clause 7.2 |
+| 0 | 0 | 0 | 0 | 03 | Locked TU-n (Note 4) |
+| 0 | 0 | 0 | 0 | 04 | Asynchronous mapping of 34 368 kbit/s or 44 736 kbit/s into the container-3, see clause 10.1.2 |
+| 0 | 0 | 0 | 0 | 05 | Experimental mapping (Note 9) |
+| 0 | 0 | 0 | 1 | 12 | Asynchronous mapping of 139 264 kbit/s into the container-4, see clause 10.1.1.1 |
+| 0 | 0 | 0 | 1 | 13 | ATM mapping, see clauses 10.2.1 and 10.2.2 |
+| 0 | 0 | 0 | 1 | 14 | MAN DQDB [1] mapping, see clause 10.4 |
+| 0 | 0 | 0 | 1 | 15 | FDDI [3]-[11] mapping, see clause 10.5 |
+| 0 | 0 | 0 | 1 | 16 | Mapping of HDLC/PPP [12], [13] framed signal, see clause 10.3 |
+| 0 | 0 | 0 | 1 | 17 | Reserved for proprietary use (Note 10) |
+| 0 | 0 | 0 | 1 | 18 | Mapping of HDLC/LAPS [15] framed signals, see clause 10.3 |
+| 0 | 0 | 0 | 1 | 19 | Reserved for proprietary use (Note 10) |
+| 0 | 0 | 1 | 0 | 20 | Asynchronous mapping of ODUk (k=1,2) into VC-4-Xv (X=17,68), see clause 10.7 |
+
+**Table 9-11 – C2 byte coding**
+
+| MSB 1 2 3 4 5 6 7 8 | LSB | Hex code (Note 1) | Interpretation |
+|------------------------|-----|----------------------|--------------------------------------------------------|
+| 0 0 0 1 1 0 1 0 | | 1A | Mapping of 10 Gbit/s Ethernet frames [14], see Annex F |
+| 0 0 0 1 1 0 1 1 | | 1B | GFP mapping, see clause 10.6 |
+| 0 0 0 1 1 1 0 0 | | 1C | Mapping of 10 Gbit/s fibre channel frames (Note 8) |
+| 1 1 0 0 1 1 1 1 | | CF | Reserved (Note 7) |
+| 1 1 0 1 0 0 0 0 | | D0 | Reserved for proprietary use (Note 10) |
+| 1 1 0 1 1 1 1 1 | | DF | |
+| 1 1 1 0 0 0 0 1 | | E1 | Reserved for national use |
+| 1 1 1 1 1 1 0 0 | | FC | |
+| 1 1 1 1 1 1 1 0 | | FE | Test signal, O.181-specific mapping (Note 5) |
+| 1 1 1 1 1 1 1 1 | | FF | VC-AIS (Note 6) |
+
+NOTE 1 – There are 191 spare codes left for future use. Refer to Annex A/G.806 for the procedure to obtain one of these codes for a new payload type.
+
+NOTE 2 – Value "0" indicates "VC-4-Xc/VC-4/VC-3 path unequipped or supervisory-unequipped". This value is originated in the case of an open connection and in the case of a supervisory-unequipped signal that contains no payload.
+
+NOTE 3 – Value "1" should not be used in any equipment designed after the date of approval (10/2000) of version 5 of this Recommendation. In the past, this code meant "Equipped-non-specific" and has been used in cases where a mapping code is not defined in this table, see code "05" for new designs. For interworking with (old) equipment designed to transmit only the values "0" and "1", the following conditions apply:
+
+- For backward compatibility, old equipment shall interpret any value received other than value "0" as an equipped condition.
+- For forward compatibility, when receiving value "1" from old equipment, new equipment shall not generate a payload mismatch alarm.
+
+NOTE 4 – The code "03" shall, for backward compatibility purposes, continue to be interpreted as previously defined even if the locked mode byte synchronous mappings are not defined any more.
+
+NOTE 5 – Any mapping defined in ITU-T Rec. O.181 which does not correspond to a mapping defined in this Recommendation falls in this category.
+
+NOTE 6 – Value "FF" indicates VC-AIS. It is generated by a TCM source if no valid incoming signal is available and a replacement signal is generated.
+
+NOTE 7 – Previous value assigned for an obsolete mapping of HDLC/PPP framed signal [12], [13].
+
+NOTE 8 – This mapping is under study and the signal label is provisionally allocated.
+
+NOTE 9 – Value "05" is only to be used for experimental activities in cases where a mapping code is not defined in this table. Refer to Annex A/G.806 for more information on the use of this code.
+
+NOTE 10 – The code value(s) will not be subject to further standardization. Refer to Annex A/G.806 for more information on the use of these codes.
+
+#### 9.3.1.4 Path status: G1
+
+One byte is allocated to convey the path status and performance back to a VC-4-Xc/VC-4/VC-3 trail termination source as detected by a trail termination sink. This feature permits the status and performance of the complete duplex trail to be monitored at either end, or at any point along that trail. The allocation of bits in G1 is illustrated in Figure 9-8.
+
+| REI | | | | RDI | Reserved | | Spare |
+|-----|---|---|---|-----|----------|---|-------|
+| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
+
+Figure 9-8 – VC-4-Xc/VC-4/VC-3 path status (G1)
+
+Bits 1 through 4 convey the count of interleaved-bit blocks that have been detected in error by the trail termination sink using the path BIP-8 code (B3). This count has nine legal values, namely 0-8 errors. The remaining seven possible values represented by these four bits can only result from some unrelated condition and shall be interpreted as zero errors.
+
+Bit 5 is set to 1 to indicate a VC-4-Xc/VC-4/VC-3 path remote defect indication (RDI), otherwise it is set to 0. The VC-4-Xc/VC-4/VC-3 path RDI is sent back towards the trail termination source if either an AU-4-Xc/AU-4/AU-3 or TU-3 server signal failure or trail signal failure is being detected by the trail termination sink. RDI does not indicate remote payload or adaptation defects. Connectivity and server defects are indicated by RDI; for further details, see ITU-T Rec. G.783.
+
+Bits 6 and 7 are reserved for an optional use described in clause VII.1. If this option is not used, bits 6 and 7 shall be set to 00 or 11. A receiver is required to be able to ignore the contents of these bits. The use of the optional function is at the discretion of the owner of the trail termination source generating the G1 byte.
+
+Bit 8 is allocated for future use. This bit has no defined value. The receiver is required to ignore its content.
+
+NOTE – Equipment complying with the 1993 versions of the I.432.x series of ITU-T Recommendations may use bit 5 of G1 to indicate a remote loss of cell delineation (LCD).
+
+#### 9.3.1.5 Path user channels: F2, F3
+
+These bytes are allocated for user communication purposes between path elements and are payload dependent.
+
+For mapping of DQDB in VC-4, these two octets are used to carry the DQDB layer management information octets (M1 and M2) [1].
+
+#### 9.3.1.6 Position and sequence indicator: H4
+
+This byte provides a multiframe and sequence indicator for virtual VC-3/VC-4 concatenation (see clause 11.2) and a generalized position indicator for payloads. In the latter case, the content is payload specific (e.g., H4 can be used as a multiframe indicator for VC-2, VC-11 and VC-12 payload as defined in clause 8.3.8).
+
+For mapping of DQDB in VC-4, the H4 byte carries the slot boundary information and the link status signal (LSS). The bits 1 and 2 are used for the LSS code [1]. The bits 3 to 8 form the slot offset indicator. The slot offset indicator shall contain a binary number indicating the offset in octets between the H4 octet and the first slot boundary following the H4 octet. The valid range of the slot offset indicator value shall be 0 to 52. A received value of 53 to 63 corresponds to an error condition.
+
+#### 9.3.1.7 Automatic protection switching (APS) channel: K3 (b1-b4)
+
+These bits are allocated for APS signalling for protection at the VC-3/VC-4 path levels.
+
+#### 9.3.1.8 Network operator byte: N1
+
+This byte is allocated to provide a tandem connection monitoring (TCM) function. The details concerning the two possible implementations of the HO-TCM function are given in Annexes C and D.
+
+#### 9.3.1.9 Data link K3 (b7-b8)
+
+Bits 7 and 8 of K3 are reserved for a higher order path data link. The applications and protocols are outside the scope of this Recommendation.
+
+#### 9.3.1.10 Spare: K3 (b5-b6)
+
+These bits are allocated for future use. These bits have no defined value. The receiver is required to ignore their content.
+
+### 9.3.2 VC-2, VC-12 and VC-11 POH
+
+The bytes V5, J2, N2 and K4 are allocated to the VC-2, VC-12 and VC-11 POH. The V5 byte is the first byte of the multiframe and its position is indicated by the TU-2, TU-12 or TU-11 pointer. The position of these bytes in the multiframe is given in Figure 8-9.
+
+NOTE – Payload-dependent and payload-independent information is communicated by different codings in bits 5 to 7 of V5 and 5 to 7 of K4.
+
+#### 9.3.2.1 V5 byte
+
+The byte V5 provides the functions of error checking, signal label and path status of the VC-2, VC-12 and VC-11 paths. The bit assignments of the V5 byte are specified in the following clauses and are illustrated in Figure 9-9.
+
+| BIP-2 | | REI | RFI | Signal label | | | RDI |
+|-------|---|-----|-----|--------------|---|---|-----|
+| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
+
+Figure 9-9 – VC-2, VC-12 and VC-11 POH V5
+
+Bits 1 and 2 are used for error performance monitoring. A bit interleaved parity (BIP) scheme is specified. Bit 1 is set such that parity of all odd number bits (1, 3, 5 and 7) in all bytes in the previous VC-2, VC-12 or VC-11 is even and bit 2 is set similarly for the even number bits (2, 4, 6 and 8).
+
+Note that the calculation of the BIP-2 includes the VC-2, VC-12 or VC-11 POH bytes but excludes bytes V1, V2, V3 (except when used for negative justification) and V4.
+
+Bit 3 is a VC-2, VC-12 and VC-11 path remote error indication (REI) that is set to one and sent back towards a VC-2, VC-12 or VC-11 path originator if one or more errors were detected by the BIP-2, and is otherwise set to zero.
+
+Bit 4 is a VC-11 byte synchronous path remote failure indication (RFI). This bit is set to one if a failure is declared, otherwise it is set to zero. The VC-11 path RFI is sent back by the VC-11 termination. The use and content of this bit are undefined for VC-2 and VC-12.
+
+NOTE – A failure is a defect that persists beyond the maximum time allocated to the transmission system protection mechanisms.
+
+Bits 5 through 7 provide a VC-2, VC-12 and VC-11 signal label. Eight binary values are possible in these three bits. Value 000 indicates "VC-2, VC-12 or VC-11 path unequipped or supervisory-unequipped". Value 001 is used by old equipment to indicate "VC-2, VC-12 or VC-11 path equipped-non-specific payload". Other values are used by new equipment to indicate specific mappings as shown in Table 9-12. The value 101 indicates a VC-2, VC-12 or VC-11 mapping given
+
+by the extended signal label described in clause 9.3.2.4. Any value received, other than 000, indicates an equipped VC-2, VC-12 or VC-11 path.
+
+**Table 9-12 – VC-2, VC-12 and VC-11 V5 signal label coding**
+
+| b5 | b6 | b7 | Meaning |
+|----|----|----|-------------------------------------------------------------------------|
+| 0 | 0 | 0 | Unequipped or supervisory-unequipped |
+| 0 | 0 | 1 | Reserved (Note 1) |
+| 0 | 1 | 0 | Asynchronous, see clauses 10.1.3.1, 10.1.4.1 and 10.1.5.1 |
+| 0 | 1 | 1 | Bit synchronous, see clauses 10.1.3.2 and 10.1.5.2 (Note 2) |
+| 1 | 0 | 0 | Byte synchronous, see clauses 10.1.4.2, 10.1.4.3, 10.1.5.3 and 10.1.5.4 |
+| 1 | 0 | 1 | Extended signal label described in 9.3.2.4 (Note 1) |
+| 1 | 1 | 0 | Test signal, O.181-specific mapping (Note 3) |
+| 1 | 1 | 1 | VC-AIS (Note 4) |
+
+NOTE 1 – Value "1" should not be used in any equipment designed after the date of approval of version 5 (10/2000) of this Recommendation. In the past this code meant "equipped-non-specific" and has been used in cases where a mapping code is not defined in this table, see code "101" and extended signal label "08" in Table 9-13 for new designs. For interworking with (old) equipment designated to transmit only the values "0" and "1", the following conditions apply:
+
+- For backward compatibility, old equipment shall interpret any value received other than "0" as an equipped condition.
+- For forward compatibility, when receiving value "1" from old equipment, new equipment shall not generate a payload mismatch alarm.
+
+NOTE 2 – In the case of a VC-12, the code "3" shall, for backward compatibility purposes, continue to be interpreted as previously defined even if the bit synchronous mapping of 2048 kbit/s signal is not defined anymore.
+
+NOTE 3 – Any non-virtually concatenated mapping defined in ITU-T Rec. O.181 that does not correspond to a mapping defined in this Recommendation falls in this category.
+
+NOTE 4 – Value "7" indicates VC-AIS. It is generated by a TCM source if no valid incoming signal is available and a replacement signal is generated.
+
+Bit 8 is set to 1 to indicate a VC-2, VC-12 or VC-11 path remote defect indication (RDI); otherwise it is set to zero. The VC-2, VC-12 or VC-11 path RDI is sent back towards the trail termination source if either a TU-2, TU-12 or TU-11 server signal failure or trail signal failure condition is being detected by the trail termination sink. RDI does not indicate remote payload or adaptation defects. Connectivity and server defects are indicated by RDI; for further detail see ITU-T Rec. G.783.
+
+#### 9.3.2.2 Path trace: J2
+
+Byte J2 is used to transmit repetitively a lower order path access point identifier so that a path receiving terminal can verify its continued connection to the intended transmitter. This path access point identifier uses the format defined in clause 3/G.831. A 16-byte frame is defined for the transmission of path access point identifiers. This 16-byte frame is identical to the 16-byte frame defined in clause 9.2.2.2 for the description of the byte J0.
+
+NOTE – Equipment developed prior to the adoption of the 1993 version of ITU-T Rec. G.709 may not support this functionality.
+
+#### 9.3.2.3 Network operator byte: N2
+
+This byte is allocated to provide a tandem connection monitoring (TCM) function. The details concerning the implementation of the LO-TCM are given in Annex E.
+
+#### 9.3.2.4 Extended signal label: K4 (b1)
+
+This bit is allocated to an extended signal label. If the signal label in V5 bits 5 through 7 is 101, the contents of the extended signal label is valid and is described below. For all other values of V5 bits 5 through 7, the extended signal label bit is undefined and should be ignored by the receiver.
+
+The bit contains a 32-frame multiframe depicted in Figure 9-10. The multiframe alignment signal, MFAS, consists of "0111 1111 110". The extended signal label is contained in bits 12 to 19. Multiframe position 20 must contain "0". The remaining 12 bits are reserved for future standardization, should be set to all "0"s, and should be ignored by the receiver.
+
+NOTE 1 – The virtual concatenation multiframe in K4 bit 2 uses the MFAS of this bit. That means that the virtual concatenation function needs to consider this bit without confirming that the V5 signal label is 101.
+
+There are no inconsistency problems since all LO virtually concatenated payloads must have an extended signal label.
+
+NOTE 2 – If at a later stage the bits reserved for future use are activated, care must be taken to ensure that a sequence of nine "1"s (imitating the MFAS) is avoided.
+
+
+
+Bit number
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------|---|---|---|---|---|---|---|---|----|----|-----------------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|---|---|---|
+| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | | | |
+| MFAS | | | | | | | | | | | Extended signal label | | | | | | | | 0 | R | R | R | R | R | R | R | R | R | R | R | R | R | R | R |
+
+MFAS Multiframe alignment bits
+0 Zero
+R Reserved bit
+
+Figure 9-10 – K4 bit 1 multiframe
+
+The coding of the extended signal label is given in Table 9-13. The signal labels in Table 9-12 for the range "0" to "7" and the signal labels in Table 9-13 for the range of "08" to "FF" together forms the complete VC-11/VC-12/VC-2 signal label range of "00" to "FF".
+
+NOTE 3 – Signal label "5" is indicated by an equipment not supporting the extended signal label receiving an extended signal label.
+
+NOTE 4 – For interworking with equipment using the ATM mapping in clause 10.2.5 it may be necessary to accept the V5 signal label "5" without K4 bit 1 multiframe as an equipped condition.
+
+**Table 9-13 – VC-11/VC-12/VC-2 extended signal label byte coding**
+
+| MSB | | | | LSB | | | | Hex code (Note 1) | Interpretation |
+|-----|-----|-----|-----|-----|-----|-----|-----|----------------------|---------------------------------------------------------------------|
+| b12 | b13 | b14 | b15 | b16 | b17 | b18 | b19 | | |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 00 | Reserved (Note 2) |
+| ... | ... | ... | ... | ... | ... | ... | ... | ... | ... |
+| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 07 | |
+| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 08 | Experimental mapping (Note 3) |
+| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 09 | ATM mapping, see clauses 10.2.3 to 10.2.5 |
+| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0A | Mapping of HDLC/PPP [12], [13] framed signal, see clause 10.3 |
+| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | 0B | Mapping of HDLC/LAPS [15] framed signals, see clause 10.3 |
+| 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0C | Virtually concatenated test signal, O.181-specific mapping (Note 4) |
+| 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0D | GFP mapping, see clause 10.6 |
+| 1 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | D0 | Reserved for proprietary use (Note 5) |
+| ... | ... | ... | ... | ... | ... | ... | ... | ... | ... |
+| 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | DF | |
+| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | FF | Reserved |
+
+NOTE 1 – There are 225 spare codes left for future use. Refer to Annex A/G.806 for the procedure to obtain one of these codes for a new payload type.
+
+NOTE 2 – Values "00" to "07" are reserved to give a unique name to non-extended in Table 9-12 and extended signal labels.
+
+NOTE 3 – Value "08" is only to be used for experimental activities in cases where a mapping code is not defined in this table. Refer to Annex A/G.806 for more information on the use of this code.
+
+NOTE 4 – Any virtually concatenated mapping defined in ITU-T Rec. O.181 or its successors which does not correspond to a mapping defined in this Recommendation falls in this category.
+
+NOTE 5 – These 16-code values will not be subject to further standardization. Refer to Annex A/G.806 for more information on the use of these codes.
+
+#### 9.3.2.5 Lower order virtual concatenation: K4 (b2)
+
+This bit is allocated for the lower order virtual concatenation string. The bit is multiframed in 32 frames to form a 32-bit string. This function is described in clause 11.4.
+
+#### 9.3.2.6 Automatic protection switching (APS) channel: K4 (b3-b4)
+
+These bits are allocated for APS signalling for protection at the lower order path level. This function is for further study.
+
+#### 9.3.2.7 Reserved: K4 (b5-b7)
+
+Bits 5 to 7 of K4 are reserved for an optional use described in clause VII.2. If this option is not used, these bits shall be set to "000" or "111". A receiver is required to be able to ignore the contents of these bits. The use of the optional function is at the discretion of the owner of the trail termination source generating the K4 byte.
+
+#### 9.3.2.8 Data link: K4 (b8)
+
+Bit 8 of K4 is reserved for a lower order path data link. The applications and protocols are outside the scope of this Recommendation.
+
+# 10 Mapping of tributaries into VC-n/VC-m
+
+## 10.1 Mapping of G.702 type signals
+
+Accommodation of asynchronous and synchronous tributaries presently defined in ITU-T Rec. G.702 shall be possible.
+
+Figure 10-1 shows TU-11, TU-12 and TU-2 sizes and formats.
+
+
+
+**TU-11:** 27 bytes, 125 µs. Grid: 9 rows, 3 columns. Bit rate: 1728 kbit/s.
+
+**TU-12:** 36 bytes, 125 µs. Grid: 9 rows, 4 columns. Bit rate: 2304 kbit/s.
+
+**TU-2:** 108 bytes, 125 µs. Grid: 9 rows, 12 columns. Bit rate: 6912 kbit/s.
+
+G.707-Y.1322\_F10-1
+
+Diagram showing the sizes and formats of TU-11, TU-12, and TU-2. Each section shows a vertical stack of bytes (1, 2, ..., 27 for TU-11; 1, 2, ..., 36 for TU-12; 1, 2, ..., 108 for TU-2) with a total size in bytes and a duration of 125 µs. To the right, a grid shows the tributary unit structure with 9 rows and 3, 4, or 12 columns respectively, with a corresponding bit rate (1728 kbit/s, 2304 kbit/s, or 6912 kbit/s).
+
+NOTE – The tributary unit pointer bytes (V1-V4) are located in byte 1 (using a four frame multiframe).
+
+**Figure 10-1 – TU-11, TU-12 and TU-2 sizes and formats**
+
+### 10.1.1 Mapping into VC-4
+
+#### 10.1.1.1 Asynchronous mapping of 139 264 kbit/s
+
+One 139 264 kbit/s signal can be mapped into a VC-4 of an STM-1 frame as shown in Figures 10-2 and 10-3.
+
+The VC-4 consists of a 9-byte (1 column) path overhead (POH) plus a 9-row by 260-column payload structure as shown in Figure 10-2.
+
+
+
+The diagram illustrates the mapping of a VC-4 into an STM-1 frame. The STM-1 frame is 270 bytes wide and 9 rows high. The first column is the SOH (3 rows), followed by the AU-4 PTR (1 row), and then the SOH (5 rows). The remaining 261 bytes are the AU-4 payload. The AU-4 payload is divided into 20 blocks of 13 bytes each. The first byte of each block is the VC-4 POH, which is 9 bytes long (J1, B3, C2, G1, F2, H4, F3, K3, N1). The remaining 12 bytes of each block are the VC-4 payload. The VC-4 payload is 260 columns wide and 9 rows high. The diagram shows the first 13 columns of the VC-4 payload, with the first column being the POH and the remaining 12 columns being the payload. The text 'G.707-Y.1322\_F10-2' is in the bottom right corner.
+
+Diagram showing the multiplexing of VC-4 into STM-1 and the block structure of VC-4. The STM-1 frame is 270 bytes wide and 9 rows high. The first column is the SOH (3 rows), followed by the AU-4 PTR (1 row), and then the SOH (5 rows). The remaining 261 bytes are the AU-4 payload. The AU-4 payload is divided into 20 blocks of 13 bytes each. The first byte of each block is the VC-4 POH, which is 9 bytes long (J1, B3, C2, G1, F2, H4, F3, K3, N1). The remaining 12 bytes of each block are the VC-4 payload. The VC-4 payload is 260 columns wide and 9 rows high. The diagram shows the first 13 columns of the VC-4 payload, with the first column being the POH and the remaining 12 columns being the payload. The text 'G.707-Y.1322\_F10-2' is in the bottom right corner.
+
+**Figure 10-2 – Multiplexing of VC-4 into STM-1 and block structure of VC-4 for asynchronous mapping of 139 264 kbit/s**
+
+This payload can be used to carry one 139 264 kbit/s signal:
+
+- Each of the nine rows is partitioned into 20 blocks, consisting of 13 bytes each (Figure 10-2).
+- In each row, one justification opportunity bit (S) and five justification control bits (C) are provided (Figure 10-3).
+- The first byte of each block consists of:
+ - either eight data bits (D) (byte W); or
+ - eight fixed stuff bits (R) (byte Y); or
+ - one justification control bit (C) plus five fixed stuff bits (R) plus two overhead bits (O) (byte X); or
+ - six data bits (D) plus one justification opportunity bit (S) plus one fixed stuff bit (R) (byte Z).
+- The last 12 bytes of one block consist of data bits (D).
+
+The sequence of all these bytes is shown in Figure 10-3.
+
+
+
+1 12 bytes
+
+| | | | | | | | | | | |
+|-----|---|------|---|------|---|------|---|------|---|------|
+| POH | W | 96 D | X | 96 D | Y | 96 D | Y | 96 D | Y | 96 D |
+|-----|---|------|---|------|---|------|---|------|---|------|
+
+| | | | | | | | | | |
+|---|------|---|------|---|------|---|------|---|------|
+| X | 96 D | Y | 96 D | Y | 96 D | Y | 96 D | X | 96 D |
+|---|------|---|------|---|------|---|------|---|------|
+
+| | | | | | | | | | |
+|---|------|---|------|---|------|---|------|---|------|
+| Y | 96 D | Y | 96 D | Y | 96 D | X | 96 D | Y | 96 D |
+|---|------|---|------|---|------|---|------|---|------|
+
+| | | | | | | | | | |
+|---|------|---|------|---|------|---|------|---|------|
+| Y | 96 D | Y | 96 D | X | 96 D | Y | 96 D | Z | 96 D |
+|---|------|---|------|---|------|---|------|---|------|
+
+G.707-Y.1322\_F10-3
+
+| | |
+|------------------------------------------------------------------------------------|----------|
+| W
| DDDDDDDD |
+| X
| CRRRRROO |
+
+| | |
+|------------------------------------------------------------------------------------|----------|
+| Y
| RRRRRRRR |
+| Z
| DDDDDDSR |
+
+| | |
+|---|-------------------------------|
+| C | Justification control bit |
+| D | Data bit |
+| O | Overhead bit |
+| R | Fixed stuff bit |
+| S | Justification opportunity bit |
+
+Diagram of VC-4 container row structure showing byte sequences and bit definitions.
+
+NOTE – This figure shows one row of the nine-row VC-4 container structure.
+
+**Figure 10-3 – Asynchronous mapping of 139 264 kbit/s tributary into VC-4**
+
+The overhead bits (O) are reserved for further overhead communication purposes.
+
+The set of five justification control bits (C) in every row is used to control the corresponding justification opportunity bit (S). CCCCC = 00000 indicates that the S bit is an information bit, whereas CCCCC = 11111 indicates that the S bit is a justification bit.
+
+Majority vote should be used to make the justification decision in the desynchronizer for protection against single and double bit errors in the C bits.
+
+The value contained in the S bit, when used as justification bit, is not defined. The receiver is required to ignore the value contained in this bit whenever it is used as a justification bit.
+
+### 10.1.2 Mapping into VC-3
+
+#### 10.1.2.1 Asynchronous mapping of 44 736 kbit/s
+
+One 44 736 kbit/s signal can be mapped into a VC-3 as shown in Figure 10-4.
+
+
+
+Diagram of asynchronous mapping of 44 736 kbit/s tributary into VC-3. The diagram shows a grid of 9 subframes (rows) over a 125 μs period. Each subframe is 85 bytes long. The columns are labeled: POH, 8R, 8R, RRC (indicated by an arrow), 8R, CCRRRRRR, 8R, CCRROORS. The RRC section is further divided into 5D and 200D. The CCRRRRRR section is divided into 8D and 200D. The CCRROORS section is divided into 8D and 200D. Cells containing 'X' represent fixed stuff (R) bits. Cells containing 'D' represent data bits. Cells containing 'O' represent overhead bits. The total duration is 125 μs. The diagram is labeled G.707-Y.1322\_F10-4.
+
+- C Justification control bit
+- D Data bit
+- O Overhead bit
+- R Fixed stuff bit
+- S Justification opportunity bit
+
+**Figure 10-4 – Asynchronous mapping of 44 736 kbit/s tributary into VC-3**
+
+The VC-3 consists of nine subframes every 125 μs. Each subframe consists of one byte of VC-3 POH, 621 data bits, a set of five justification control bits, one justification opportunity bit and two overhead communication channel bits. The remaining bits are fixed stuff (R) bits. The O bits are reserved for future overhead communication purposes.
+
+The set of five justification control bits is used to control the justification opportunity (S) bit. CCCCC = 00000 indicates that the S bit is a data bit, whereas CCCCC = 11111 indicates that the S bit is a justification bit. Majority vote should be used to make the justification decision in the desynchronizer for protection against single and double bit errors in the C bits.
+
+The value contained in the S bit, when used as justification bits, is not defined. The receiver is required to ignore the value contained in this bit whenever it is used as a justification bit.
+
+#### **10.1.2.2 Asynchronous mapping of 34 368 kbit/s**
+
+One 34 368 kbit/s signal can be mapped into a VC-3 as shown in Figure 10-5.
+
+| | | | | |
+|------------|----|----|--|----------|
+| VC-3 POH → | J1 | T1 | | 3 rows |
+| | B3 | | | |
+| | C2 | | | |
+| | G1 | T2 | | 3 rows |
+| | F2 | | | |
+| | H4 | | | |
+| | F3 | T3 | | 3 rows |
+| | K3 | | | |
+| | N1 | | | |
+| | 1 | 84 | | 125 μs ↓ |
+
+Image: Detailed bit-level mapping diagram showing the arrangement of data bits (D), fixed stuff bits (R), justification control bits (C), and justification opportunity bits (S) across three rows of blocks.
+
+☒ = R R R R R R R R
+
+R R R R R R C1 C2 R R R R R R R S1 S2 D D D D D D D D
+
+- C Justification control bit
+- D Data bit
+- O Overhead bit
+- R Fixed stuff bit
+- S Justification opportunity bit
+
+**Figure 10-5 – Asynchronous mapping of 34 368 kbit/s tributary into VC-3**
+
+89 **ITU-T Rec. G.707/Y.1322 (01/2007)**
+
+G.707-Y.1322\_F10-5
+
+In addition to the VC-3 POH, the VC-3 consists of a payload of $9 \times 84$ bytes every 125 $\mu\text{s}$ . This payload is divided in three subframes, each subframe consisting of:
+
+- 1431 data bits (D);
+- two sets of five justification control bits ( $C_1, C_2$ );
+- two justification opportunity bits ( $S_1, S_2$ );
+- 573 fixed stuff bits (R).
+
+Two sets of five justification control bits $C_1$ and $C_2$ are used to control the two justification opportunity bits $S_1$ and $S_2$ , respectively.
+
+$C_1C_1C_1C_1C_1 = 00000$ indicates that $S_1$ is a data bit while $C_1C_1C_1C_1C_1 = 11111$ indicates that $S_1$ is a justification bit. $C_2$ bits control $S_2$ in the same way. Majority vote should be used to make the justification decision in the desynchronizer for protection against single and double bit errors in the C bits.
+
+The value contained in $S_1$ and $S_2$ , when they are justification bits, is not defined. The receiver is required to ignore the value contained in these bits whenever they are used as justification bits.
+
+NOTE – The same mapping could be used for bit or byte synchronous 34 368 kbit/s. In these cases, $S_1$ bit should be a fixed stuff and $S_2$ bit a data bit. By setting the $C_1$ bits to 1 and the $C_2$ bits to 0, a common desynchronize could be used for both asynchronous and synchronous 34 368 kbit/s mappings.
+
+### 10.1.3 Mapping into VC-2
+
+#### 10.1.3.1 Asynchronous mapping of 6312 kbit/s
+
+One 6312 kbit/s signal can be mapped into a VC-2. Figure 10-6 shows this over a period of 500 $\mu\text{s}$ .
+
+| | | | | |
+|----------|-------------------------|-------------------|----------|-------------------|
+| V5 | DDDDDDDR | $(24 \times 8)$ D | RRRRRRRR | 125 $\mu\text{s}$ |
+| RRRRRRRR | $C_1C_2$ OOOODR | $(24 \times 8)$ D | RRRRRRRR | |
+| DDDDDDDD | $C_1C_2$ OOOODR | $(24 \times 8)$ D | RRRRRRRR | |
+| RRRRRRRR | $C_1C_2$ DDD $S_1S_2$ R | $(24 \times 8)$ D | | |
+| J2 | DDDDDDDR | $(24 \times 8)$ D | RRRRRRRR | 250 $\mu\text{s}$ |
+| RRRRRRRR | $C_1C_2$ OOOODR | $(24 \times 8)$ D | RRRRRRRR | |
+| DDDDDDDD | $C_1C_2$ OOOODR | $(24 \times 8)$ D | RRRRRRRR | |
+| RRRRRRRR | $C_1C_2$ DDD $S_1S_2$ R | $(24 \times 8)$ D | | |
+| N2 | DDDDDDDR | $(24 \times 8)$ D | RRRRRRRR | 375 $\mu\text{s}$ |
+| RRRRRRRR | $C_1C_2$ OOOODR | $(24 \times 8)$ D | RRRRRRRR | |
+| DDDDDDDD | $C_1C_2$ OOOODR | $(24 \times 8)$ D | RRRRRRRR | |
+| RRRRRRRR | $C_1C_2$ DDD $S_1S_2$ R | $(24 \times 8)$ D | | |
+| K4 | DDDDDDDR | $(24 \times 8)$ D | RRRRRRRR | 500 $\mu\text{s}$ |
+| RRRRRRRR | $C_1C_2$ OOOODR | $(24 \times 8)$ D | RRRRRRRR | |
+| DDDDDDDD | $C_1C_2$ OOOODR | $(24 \times 8)$ D | RRRRRRRR | |
+| RRRRRRRR | $C_1C_2$ DDD $S_1S_2$ R | $(24 \times 8)$ D | | |
+
+C Justification control bit
+D Data bit
+O Overhead bit
+R Fixed stuff bit
+S Justification opportunity bit
+
+Figure 10-6 – Asynchronous mapping of 6312 kbit/s tributary
+
+In addition to the VC-2 POH, the VC-2 consists of 3152 data bits, 24 justification control bits, eight justification opportunity bits and 32 overhead communication channel bits. The remaining are fixed stuff bits (R). The O bits are reserved for future overhead communication purposes.
+
+Two sets ( $C_1$ , $C_2$ ) of three justification control bits, are used to control the two justification opportunities $S_1$ and $S_2$ , respectively.
+
+$C_1C_1C_1 = 000$ indicates that $S_1$ is a data bit, while $C_1C_1C_1 = 111$ indicates that $S_1$ is a justification bit. $C_2$ bits control $S_2$ in the same way. Majority vote should be used to make the justification decision in the desynchronizer for protection against single bit error in the C bits.
+
+The value contained in $S_1$ , and $S_2$ , when they are justification bits, is not defined. The receiver is required to ignore the value contained in these bits whenever they are used as justification bits.
+
+#### 10.1.3.2 Bit synchronous mapping of 6312 kbit/s
+
+The bit synchronous mapping for 6312 kbit/s tributaries is shown in Figure 10-7.
+
+Note that a common desynchronizer can be used for both asynchronous and bit synchronous mappings.
+
+| | | | | |
+|----------|-----------|-------------------|----------|--------|
+| V5 | DDDDDDDR | $(24 \times 8) D$ | RRRRRRRR | |
+| RRRRRRRR | 1ØØØØØØDR | $(24 \times 8) D$ | RRRRRRRR | |
+| DDDDDDDD | 1ØØØØØØDR | $(24 \times 8) D$ | RRRRRRRR | |
+| RRRRRRRR | 1ØØØØØØDR | $(24 \times 8) D$ | | 125 µs |
+| J2 | DDDDDDDR | $(24 \times 8) D$ | RRRRRRRR | |
+| RRRRRRRR | 1ØØØØØØDR | $(24 \times 8) D$ | RRRRRRRR | |
+| DDDDDDDD | 1ØØØØØØDR | $(24 \times 8) D$ | RRRRRRRR | |
+| RRRRRRRR | 1ØØØØØØDR | $(24 \times 8) D$ | | 250 µs |
+| N2 | DDDDDDDR | $(24 \times 8) D$ | RRRRRRRR | |
+| RRRRRRRR | 1ØØØØØØDR | $(24 \times 8) D$ | RRRRRRRR | |
+| DDDDDDDD | 1ØØØØØØDR | $(24 \times 8) D$ | RRRRRRRR | |
+| RRRRRRRR | 1ØØØØØØDR | $(24 \times 8) D$ | | 375 µs |
+| K4 | DDDDDDDR | $(24 \times 8) D$ | RRRRRRRR | |
+| RRRRRRRR | 1ØØØØØØDR | $(24 \times 8) D$ | RRRRRRRR | |
+| DDDDDDDD | 1ØØØØØØDR | $(24 \times 8) D$ | RRRRRRRR | |
+| RRRRRRRR | 1ØØØØØØDR | $(24 \times 8) D$ | | 500 µs |
+
+D Data bit
+
+O Overhead bit
+
+R Fixed stuff bit
+
+**Figure 10-7 – Bit synchronous mapping of 6312 kbit/s tributary**
+
+### 10.1.4 Mapping into VC-12
+
+NOTE – Refer to clause 9/G.803 for recommended selection criteria on the choice of primary rate mapping.
+
+#### 10.1.4.1 Asynchronous mapping of 2048 kbit/s
+
+One 2048 kbit/s signal can be mapped into a VC-12. Figure 10-8 shows this over a period of 500 µs.
+
+
+
+| |
+|--------------------------------------------------------|
+| V 5 |
+| R R R R R R R R |
+| 32 bytes |
+| R R R R R R R R |
+| J 2 |
+| C 1 C 2 O O O O R R |
+| 32 bytes |
+| R R R R R R R R |
+| N 2 |
+| C 1 C 2 O O O O R R |
+| 32 bytes |
+| R R R R R R R R |
+| K 4 |
+| C 1 C 2 R R R R R S 1 |
+| S 2 D D D D D D D |
+| 31 bytes |
+| R R R R R R R R |
+
+500 μs
+G.707-Y.1322\_F10-8
+
+- C Justification control bit
+- D Data bit
+- O Overhead bit
+- R Fixed stuff bit
+- S Justification opportunity bit
+
+**Figure 10-8 – Asynchronous mapping of 2048 kbit/s tributary**
+
+In addition to the VC-12 POH, the VC-12 consists of 1023 data bits, six justification control bits, two justification opportunity bits and eight overhead communication channel bits. The remaining are fixed stuff bits (R). The O bits are reserved for future overhead communication purposes.
+
+Two sets (C1 , C2 ) of three justification control bits are used to control the two justification opportunities S1 and S2 , respectively. $C_1C_1C_1 = 000$ indicates that S1 is a data bit, while $C_1C_1C_1 = 111$ indicates that S1 is a justification bit. C2 controls S2 in the same way. Majority vote should be used to make the justification decision in the desynchronizer for protection against single bit errors in the C bits.
+
+The value contained in S1 and S2 , when they are justification bits, is not defined. The receiver is required to ignore the value contained in these bits whenever they are used as justification bits.
+
+#### **10.1.4.2 Byte synchronous mapping of 2048 kbit/s**
+
+Figure 10-9 shows byte synchronous mapping for G.704 structured 2048 kbit/s tributaries employing, for example, common channel signalling (CCS) or channel associated signalling (CAS).
+
+
+
+140 bytes
+
+500 μs
+
+G.707-Y.1322\_F10-9
+
+Diagram showing the byte synchronous mapping for a 2048 kbit/s tributary. It consists of a vertical stack of 24 rows representing bytes. The total size is 140 bytes, and the duration is 500 μs. The rows are labeled from top to bottom: V5, R, Time slot 0, Time slots 1 to 15, Time slot 16, Time slots 17 to 31, R, J2, R, Time slot 0, Time slots 1 to 15, Time slot 16, Time slots 17 to 31, R, N2, R, Time slot 0, Time slots 1 to 15, Time slot 16, Time slots 17 to 31, R, K4, R, Time slot 0, Time slots 1 to 15, Time slot 16, Time slots 17 to 31, and R. A vertical double-headed arrow on the left indicates the 140-byte height. Below the diagram is the text '500 μs' and 'G.707-Y.1322\_F10-9'.
+
+R Fixed stuff byte
+
+**Figure 10-9 – Byte synchronous mapping for 2048 kbit/s tributary
+(30 channels with common channel signalling or channel associated signalling)**
+
+#### 10.1.4.3 Byte synchronous mapping of $31 \times 64$ kbit/s
+
+Byte synchronous mapping of $31 \times 64$ kbit/s tributaries is shown in Figure 10-10.
+
+
+
+140 bytes
+
+500 µs
+G.707-Y.1322\_F10-10
+
+Diagram of byte synchronous mapping for 31 x 64 kbit/s. It shows a vertical stack of 140 bytes over a 500 µs period. The stack contains various fields: V5, R, R (Note), Time slots 1-15, Time slot 16, Time slots 17-31, R, J2, R, R (Note), Time slots 1-15, Time slot 16, Time slots 17-31, R, N2, R, R (Note), Time slots 1-15, Time slot 16, Time slots 17-31, R, K4, R, R (Note), Time slots 1-15, Time slot 16, Time slots 17-31, and R. A vertical double-headed arrow on the left indicates the total height is 140 bytes. The bottom of the diagram is labeled 500 µs and G.707-Y.1322\_F10-10.
+
+R Fixed stuff byte
+
+NOTE – Inserting here a time slot 0 according to ITU-T Rec. G.704 would result in the 2048 kbit/s mapping described in Figure 10-9.
+
+**Figure 10-10 – Byte synchronous mapping for $31 \times 64$ kbit/s**
+
+### 10.1.5 Mapping into VC-11
+
+Different structures are defined for the transport of 1544 kbit/s and 64 kbit/s client signals. To support 1544 kbit/s transport across SDH and PDH networks, the rule for interconnecting VC-11 mappings will be to use the 1544 kbit/s asynchronous mapping unless otherwise mutually agreed by the operators providing the transport. This SDH interconnection rule does not modify the mapping recommendations in ITU-T Rec. G.803. Refer to clause 9/G.803 for additional information on selection criteria and the choice of primary rate mappings.
+
+#### 10.1.5.1 Asynchronous mapping of 1544 kbit/s
+
+One 1544 kbit/s signal can be mapped into a VC-11. Figure 10-11 shows this over a period of 500 $\mu$ s.
+
+
+
+| |
+|---------------------------------------------------------------------|
+| V5 |
+| R R R R R D R |
+| 24 bytes |
+| J2 |
+| C 1 C 2 O O O O D R |
+| 24 bytes |
+| N2 |
+| C 1 C 2 O O O O D R |
+| 24 bytes |
+| K4 |
+| C 1 C 2 R R R S 1 S 2 R |
+| 24 bytes |
+
+104 bytes
+
+500 $\mu$ s
+
+G.707-Y.1322\_F10-11
+
+C Justification control bit
+D Data bit
+O Overhead bit
+R Fixed stuff bit
+S Justification opportunity bit
+
+Diagram of asynchronous mapping of 1544 kbit/s tributary over 500 microseconds. The diagram shows a vertical stack of 104 bytes. The stack is divided into three main sections: V5 (1 byte), J2 (1 byte), and K4 (1 byte). Each section is followed by a 24-byte payload. Between the payloads are overhead bits: R R R R R D R (7 bits) after V5, C1 C2 O O O O D R (8 bits) after the first payload, N2 (1 byte) after the second payload, C1 C2 O O O O D R (8 bits) after the third payload, and C1 C2 R R R S1 S2 R (8 bits) after the fourth payload. A vertical double-headed arrow on the left indicates the total height is 104 bytes. The time duration is 500 microseconds. A legend below defines the bit types: C (Justification control bit), D (Data bit), O (Overhead bit), R (Fixed stuff bit), and S (Justification opportunity bit).
+
+**Figure 10-11 – Asynchronous mapping of 1544 kbit/s tributary**
+
+In addition to the VC-11 POH, the VC-11 consists of 771 data bits, six justification control bits, two justification opportunity bits and eight overhead communication channel bits. The remaining are fixed stuff bits (R). The O bits are reserved for future communication purposes.
+
+Two sets ( $C_1, C_2$ ) of three justification control bits are used to control the two justification opportunities, $S_1$ and $S_2$ , respectively.
+
+$C_1 C_1 C_1 = 000$ indicates that $S_1$ is a data bit while $C_1 C_1 C_1 = 111$ indicates that $S_1$ is a justification bit. $C_2$ controls $S_2$ in the same way. Majority vote should be used to make the justification decision in the desynchronizer for protection against single bit errors in the C bits.
+
+The value contained in $S_1$ and $S_2$ , when they are justification bits, is not defined. The receiver is required to ignore the value contained in these bits whenever they are used as justification bits.
+
+#### 10.1.5.2 Bit synchronous mapping of 1544 kbit/s
+
+The bit synchronous mapping for 1544 kbit/s tributaries is shown in Figure 10-12.
+
+Note that a common desynchronizer can be used for both asynchronous and bit synchronous mappings.
+
+
+
+The diagram illustrates the bit synchronous mapping for a 1544 kbit/s tributary. It shows a vertical stack of 104 bytes, with a double-headed arrow on the left indicating the total height. The stack is divided into four identical sections, each containing a 24-byte payload and a 2-byte overhead. The overhead is further divided into a 1-byte overhead (O) and a 1-byte fixed stuff (R) section, with a '1' bit prepended. The overhead sections are labeled V5, J2, N2, and K4. The total duration of the frame is 500 μs. The diagram is labeled G.707-Y.1322\_F10-12.
+
+| |
+|-----------------|
+| V5 |
+| 1 Ø R R R R D R |
+| 24 bytes |
+| J2 |
+| 1 Ø Ø Ø Ø Ø D R |
+| 24 bytes |
+| N2 |
+| 1 Ø Ø Ø Ø Ø D R |
+| 24 bytes |
+| K4 |
+| 1 Ø R R R R D R |
+| 24 bytes |
+
+104 bytes
+
+500 μs
+
+G.707-Y.1322\_F10-12
+
+D Data bit
+Ø Overhead bit
+R Fixed stuff bit
+
+Diagram of bit synchronous mapping for 1544 kbit/s tributary showing a 104-byte frame structure over 500 μs.
+
+Figure 10-12 – Bit synchronous mapping for 1544 kbit/s tributary
+
+#### 10.1.5.3 Byte synchronous mapping of 1544 kbit/s
+
+The byte synchronous mapping for 1544 kbit/s tributaries is shown in Figure 10-13.
+
+
+
+104 bytes
+
+500 μs
+
+G.707-Y.1322\_F10-13
+
+Diagram of byte synchronous mapping for 1544 kbit/s tributary. It shows a vertical stack of 104 bytes over a 500 μs period. The stack consists of four identical sections. Each section contains a V5, J2, N2, or K4 byte, followed by a byte with bits P1 P0 S1 S2 S3 S4 F R, and then 64 kbit/s channels 1-24. A vertical double-headed arrow on the left indicates the total height is 104 bytes. Below the stack, the time duration is labeled as 500 μs. The diagram is labeled G.707-Y.1322\_F10-13.
+
+F 1544 kbit/s tributary frame bit
+ S Signalling bits
+ P1 P0 Signalling phase indicator
+ P1 P0 00 on the first signalling byte of the multiframe
+
+**Figure 10-13 – Byte synchronous mapping for 1544 kbit/s tributary**
+
+The S1 , S2 , S3 and S4 bits contain the signalling for the 24 × 64 kbit/s channels. The F bit contains the 1544 kbit/s frame bit. The phase of the signalling bits and the F bit is indicated in the P1 and P0 bits. This is illustrated in Figure 10-14.
+
+If the S or F bits are not used in an application, then they shall be set to 0.
+
+| Signalling | | | | | | | | | | | | Formats | | | | |
+|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|----------------|-----------|---|----------------|----------------|
+| 2 state | | | | 4 state | | | | 16 state | | | | 24 frames | 12 frames | | | |
+| S 1 | S 2 | S 3 | S 4 | S 1 | S 2 | S 3 | S 4 | S 1 | S 2 | S 3 | S 4 | F 4 | FAS | S | P 1 | P 0 |
+| A 1 | A 2 | A 3 | A 4 | A 1 | A 2 | A 3 | A 4 | A 1 | A 2 | A 3 | A 4 | m | 1 | - | 0 | 0 |
+| A 5 | A 6 | A 7 | A 8 | A 5 | A 6 | A 7 | A 8 | A 5 | A 6 | A 7 | A 8 | e 1 | - | 0 | 0 | 0 |
+| A 9 | A 10 | A 11 | A 12 | A 9 | A 10 | A 11 | A 12 | A 9 | A 10 | A 11 | A 12 | m | 0 | - | 0 | 0 |
+| A 13 | A 14 | A 15 | A 16 | A 13 | A 14 | A 15 | A 16 | A 13 | A 14 | A 15 | A 16 | 0 | - | 0 | 0 | 0 |
+| A 17 | A 18 | A 19 | A 20 | A 17 | A 18 | A 19 | A 20 | A 17 | A 18 | A 19 | A 20 | m | 1 | - | 0 | 0 |
+| A 21 | A 22 | A 23 | A 24 | A 21 | A 22 | A 23 | A 24 | A 21 | A 22 | A 23 | A 24 | e 2 | - | 1 | 0 | 0 |
+| A 1 | A 2 | A 3 | A 4 | B 1 | B 2 | B 3 | B 4 | B 1 | B 2 | B 3 | B 4 | m | 0 | - | 0 | 1 |
+| A 5 | A 6 | A 7 | A 8 | B 5 | B 6 | B 7 | B 8 | B 5 | B 6 | B 7 | B 8 | 0 | - | 1 | 0 | 1 |
+| A 9 | A 10 | A 11 | A 12 | B 9 | B 10 | B 11 | B 12 | B 9 | B 10 | B 11 | B 12 | m | 1 | - | 0 | 1 |
+| A 13 | A 14 | A 15 | A 16 | B 13 | B 14 | B 15 | B 16 | B 13 | B 14 | B 15 | B 16 | e 3 | - | 1 | 0 | 1 |
+| A 17 | A 18 | A 19 | A 20 | B 17 | B 18 | B 19 | B 20 | B 17 | B 18 | B 19 | B 20 | m | 0 | - | 0 | 1 |
+| A 21 | A 22 | A 23 | A 24 | B 21 | B 22 | B 23 | B 24 | B 21 | B 22 | B 23 | B 24 | 1 | - | 0 | 0 | 1 |
+| A 1 | A 2 | A 3 | A 4 | A 1 | A 2 | A 3 | A 4 | C 1 | C 2 | C 3 | C 4 | m | 1 | - | 1 | 0 |
+| A 5 | A 6 | A 7 | A 8 | A 5 | A 6 | A 7 | A 8 | C 5 | C 6 | C 7 | C 8 | e 4 | - | 0 | 1 | 0 |
+| A 9 | A 10 | A 11 | A 12 | A 9 | A 10 | A 11 | A 12 | C 9 | C 10 | C 11 | C 12 | m | 0 | - | 1 | 0 |
+| A 13 | A 14 | A 15 | A 16 | A 13 | A 14 | A 15 | A 16 | C 13 | C 14 | C 15 | C 16 | 0 | - | 0 | 1 | 0 |
+| A 17 | A 18 | A 19 | A 20 | A 17 | A 18 | A 19 | A 20 | C 17 | C 18 | C 19 | C 20 | m | 1 | - | 1 | 0 |
+| A 21 | A 22 | A 23 | A 24 | A 21 | A 22 | A 23 | A 24 | C 21 | C 22 | C 23 | C 24 | e 5 | - | 1 | 1 | 0 |
+| A 1 | A 2 | A 3 | A 4 | B 1 | B 2 | B 3 | B 4 | D 1 | D 2 | D 3 | D 4 | m | 0 | - | 1 | 1 |
+| A 5 | A 6 | A 7 | A 8 | B 5 | B 6 | B 7 | B 8 | D 5 | D 6 | D 7 | D 8 | 1 | - | 1 | 1 | 1 |
+| A 9 | A 10 | A 11 | A 12 | B 9 | B 10 | B 11 | B 12 | D 9 | D 10 | D 11 | D 12 | m | 1 | - | 1 | 1 |
+| A 13 | A 14 | A 15 | A 16 | B 13 | B 14 | B 15 | B 16 | D 13 | D 14 | D 15 | D 16 | e 6 | - | 1 | 1 | 1 |
+| A 17 | A 18 | A 19 | A 20 | B 17 | B 18 | B 19 | B 20 | D 17 | D 18 | D 19 | D 20 | m | 0 | - | 1 | 1 |
+| A 21 | A 22 | A 23 | A 24 | B 21 | B 22 | B 23 | B 24 | D 21 | D 22 | D 23 | D 24 | 1 | - | 0 | 1 | 1 |
+
+G.707-Y.1322\_F10-14
+
+An Signalling bits
+Cn Signalling bits
+Bn Signalling bits
+Dn Signalling bits
+
+F Frame alignment signal bits
+m Data link bits
+en CRC bits
+FAS Frame alignment signal
+S Signalling multiframe FAS
+
+Figure 10-14 – Out slot signalling assignments (24-channel signalling operations)
+
+#### 10.1.5.4 Byte synchronous mapping of 384 kbit/s
+
+The byte synchronous mapping for four-byte interleaved 384 kbit/s tributaries is shown in Figure 10-15.
+
+
+
+Diagram of byte synchronous mapping for 384 kbit/s tributaries. It shows a vertical stack of 104 bytes. The stack consists of alternating sections: V5, R R S1 S2 S3 S4 R R, 384 kbit/s channels 1-4, J2, R R S1 S2 S3 S4 R R, 384 kbit/s channels 1-4, N2, R R S1 S2 S3 S4 R R, 384 kbit/s channels 1-4, K4, R R S1 S2 S3 S4 R R, and 384 kbit/s channels 1-4. A vertical double-headed arrow on the left indicates the total height is 104 bytes. Below the stack, a horizontal double-headed arrow indicates a duration of 500 μs. The text 'G.707-Y.1322\_F10-15' is at the bottom right. A legend at the bottom left shows 'S' for Signalling bits.
+
+Figure 10-15 – Byte synchronous mapping for 384 kbit/s tributaries
+
+The $S_1$ , $S_2$ , $S_3$ and $S_4$ bits contain the signalling for each of the four 384 kbit/s channels. The out slot signalling assignments for the channel associated signalling methods is shown in Figure 10-16.
+
+| Frame number | n | n + 1 | n + 2 | n + 3 | n + 4 | n + 5 | n + 6 | n + 7 |
+|-------------------------------------------|----------|----------|-------|-------|-------|-------|-------|----------|
+| Use of $S_i$ bits ( $i = 1, 2, 3, 4$ ) | $F_s$ | $Y_1$ | $Y_2$ | $Y_3$ | $Y_4$ | $Y_5$ | $Y_6$ | X |
+| (Notes 1 and 4) | (Note 2) | (Note 3) | | | | | | (Note 5) |
+
+NOTE 1 – Each $S_i$ ( $i = 1, 2, 3, 4$ ) constitutes an independent signalling multiframe over eight frames. $S_i$ includes the phase indicator in itself so that the PP bits cannot be used for the phase indicator.
+
+NOTE 2 – The $F_s$ bit is either alternate 0, 1 or the following 48-bit digital pattern:
+
+A101011011 0000011001 1010100111 0011110110 10000101
+
+For the 48-bit digital pattern, the A-bit is usually fixed to state 1 and is reserved for optional use. The pattern is generated according to the following primitive polynomial (refer to ITU-T Rec. X.50):
+
+$$X^7 + X^4 + 1$$
+
+NOTE 3 – $Y_j$ bit ( $j = 1$ to 6) carries channel associated signalling or maintenance information. When the 48-bit pattern is adopted as $F_s$ frame alignment signal, each $Y_j$ bit ( $j = 1$ to 6) can be multiframed, as follows:
+
+$$Y_{j1}, Y_{j2}, \dots, Y_{j12}$$
+
+$Y_{ji}$ bit carries the following 16-bit frame alignment pattern generated according to the same primitive polynomial as for the 48-bit pattern.
+
+A011101011011000
+
+The A-bit is usually fixed to 1 and is reserved for optional use. Each $Y_{ji}$ ( $i = 2$ to 12) bit carries channel associated signalling for substrate circuits and/or maintenance information.
+
+NOTE 4 – $S_i$ bits ( $F_s$ , $Y_1$ , $\dots$ , $Y_6$ and X) all at state 1 indicate alarm indication signal (AIS) for six 64 kbit/s channels.
+
+NOTE 5 – The X-bit is usually fixed to state 1. When backward AIS for six 64 kbit/s channels is required, the X-bit is set to state 0.
+
+Figure 10-16 – Out slot signalling assignments
+
+**Table 10-1 – Differences between G.707 and G.704 naming**
+
+| G.707 | G.704 |
+|-------|--------|
+| $S_i$ | $ST_i$ |
+| $Y_j$ | $S_j$ |
+| X | $S_p$ |
+
+### 10.1.6 VC-11 to VC-12 conversion for transport by a TU-12
+
+When transporting a VC-11 in a TU-12, the VC-11 is adapted by adding fixed stuff with even parity as shown in Figure 10-17. Thus the resulting TU-12 payload can be monitored and cross-connected in the network as though it were a VC-12 with its BIP value unchanged while preserving end-to-end integrity of the real VC-11 path.
+
+
+
+Diagram showing the conversion of VC-11 to VC-12 for transport by TU-12. It illustrates a vertical stack of cells with labels V5, J2, N2, and K4 on the left. A shaded vertical column in the center represents 'Fixed stuff with even parity'. An arrow points to this shaded column from the label 'Fixed stuff with even parity'. A time duration of 500 μs is indicated at the bottom right, along with the reference G.707-Y.1322\_F10-17.
+
+**Figure 10-17 – Conversion of VC-11 to VC-12 for transport by TU-12**
+
+## 10.2 Mapping of ATM cells
+
+The mapping of ATM cells is performed by aligning the byte structure of every cell with the byte structure of the virtual container used including the concatenated structure (VC-n, VC-n-X, $n \geq 1$ ). Since the relevant container-n, container-n-Xc or container-n-Xv capacity may not be an integer multiple of the ATM cell length (53 bytes), a cell is allowed to cross the container-n, container-n-Xc or container-n-Xv frame boundary.
+
+The ATM cell information field (48 bytes) shall be scrambled before mapping into the VC-n or VC-n-X. In the reverse operation, following termination of the VC-n or VC-n-X signal, the ATM cell information field will be descrambled before being passed to the ATM layer.
+
+A self-synchronizing scrambler with polynomial $x^{43} + 1$ shall be used. The scrambler operates for the duration of the cell information field. During the 5-byte header the scrambler operation is suspended and the scrambler state retained. The first cell transmitted on start-up will be corrupted because the descrambler at the receiving end will not be synchronized to the transmitter scrambler. Cell information field scrambling is required to provide security against false cell delineation and cell information field replicating the STM-N frame alignment word.
+
+When the VC-n or VC-n-X is terminated, the cell must be recovered. The ATM cell header contains a header error control (HEC) field which may be used in a similar way to a frame alignment word to achieve cell delineation. This HEC method uses the correlation between the header bits to be protected by the HEC (32 bits) and the control bit of the HEC (8 bits) introduced in the header after computation with a shortened cyclic code with generating polynomial $g(x) = x^8 + x^2 + x + 1$ .
+
+The remainder from this polynomial is then added to the fixed pattern "01010101" in order to improve the cell delineation performance. This method is similar to conventional frame alignment recovery where the alignment word is not fixed but varies from cell to cell.
+
+More information on HEC cell delineation is given in ITU-T Rec. I.432.1.
+
+### 10.2.1 Mapping into VC-4-Xc/VC-4-Xv
+
+The ATM cell stream is mapped into a container-4-Xc or container-4-Xv with its byte boundaries aligned with the container-4-Xc or container-4-Xv byte boundaries. The container-4-Xc or container-4-Xv is then mapped into VC-4-X together with the VC-4-X POH and (X-1) columns of fixed stuff (see Figure 10-18). The ATM cell boundaries are thus aligned with the VC-4-X byte boundaries. Since the container-4-Xc or container-4-Xv capacity ( $X \times 2340$ bytes) is not an integer multiple of the cell length (53 bytes), a cell may cross a container-4-Xc or container-4-Xv frame boundary.
+
+
+
+Diagram illustrating the mapping of ATM cells into VC-4-Xc. The diagram shows a large rectangle representing the VC-4-Xc frame. On the left, a vertical column labeled 'Fixed stuff' contains bytes J1, B3, C2, G1, F2, H4, F3, K3, and N1. Below this column is a bracket labeled 'X-1 VC-4-Xc POH'. The main body of the frame is labeled 'X x 260 bytes'. Inside this body, several ATM cells are shown as smaller rectangles, some of which are cut off by the right boundary of the frame. A label 'VC-4-Xc' with an arrow points to the right boundary. Below the main frame, a single ATM cell is shown as a rectangle divided into two parts, with a label '53 octets' below it. The text 'G.707-Y.1322\_F10-18' is in the bottom right corner of the main frame diagram.
+
+Figure 10-18 – Mapping of ATM cells into VC-4-Xc
+
+### 10.2.2 Mapping into VC-4/VC-3
+
+The ATM cell stream is mapped into container-4/container-3 with its byte boundaries aligned with the container-4/container-3 byte boundaries. The container-4/container-3 is then mapped into VC-4/VC-3 together with the VC-4/VC-3 POH (see Figure 10-19). The ATM cell boundaries are thus aligned with the VC-4/VC-3 byte boundaries. Since the C-4/C-3 capacity (2340/756 bytes respectively) is not an integer multiple of the cell length (53 bytes), a cell may cross a container-4/container-3 frame boundary.
+
+
+
+Diagram illustrating the mapping of ATM cells into a VC-4/VC-3 frame. The main diagram shows a large rectangle representing the VC-4/VC-3 frame. On the left, a vertical column lists overhead bytes: J1, B3, C2, G1, F2, H4, F3, K3, and N1. An arrow points from the text 'VC-4/VC-3 POH' to this column. The main body of the frame contains data. Two ATM cells are shown, each represented by a rectangle with a hatched header section. One cell is at the top, and another is at the bottom. Ellipses (...) indicate that the cells are not necessarily contiguous. An arrow points from the text 'VC-4/VC-3' to the right side of the frame. Below the main diagram, a separate box shows a single 'ATM Cell' structure, consisting of a hatched header and a data payload, with a double-headed arrow below it labeled '53 octets'. The diagram is labeled 'G.707-Y.1322\_F10-19' in the bottom right corner.
+
+Figure 10-19 – Mapping of ATM cells into VC-4/VC-3
+
+### 10.2.3 Mapping into VC-2-Xc/VC-2-Xv
+
+Figure 10-20 shows the mapping for an ATM cell stream with a data rate of $X \times 6.784$ Mbit/s where "*X*" can take any integer value between 1 and 7 inclusive for contiguous concatenation, and between 1 and 64 inclusive for virtual concatenation.
+
+The VC-2-*X* structure is organized as a four-frame multiframe. The frames of the VC-2-Xc (contiguous concatenation) multiframe consist of one byte of POH, (*X*-1) stuff bytes and $(X \times 106)$ bytes of payload area. The frames of the VC-2-Xv (virtual concatenation), multiframe consist of *X* independent bytes of POH and $(X \times 106)$ bytes of payload area. ATM cells are loaded into the VC-2-*X* payload area with the boundaries of the cells aligned with any VC-2-*X* byte boundary. Because the VC-2-*X* payload space is equivalent of exactly $(X \times 2)$ ATM cells per 125 µs frame, the alignment between ATM cell boundaries and the VC-2-*X* structure will remain constant from frame to frame. Cells can cross VC-2-*X* frame boundaries.
+
+
+
+| | |
+|----------------------------|------------------------------|
+| ( m × 428) bytes | V5 + ( X – 1) R bytes |
+| | ( X × 106) D bytes |
+| | J2 + ( X – 1) R bytes |
+| | ( X × 106) D bytes |
+| | N2 + ( X – 1) R bytes |
+| | ( X × 106) D bytes |
+| | K4 + ( X – 1) R bytes |
+| | ( X × 106) D bytes |
+
+500 µs
+G.707-Y.1322\_F10-20
+
+D Data
+R Fixed stuff
+
+Diagram of VC-2-Xc multiframe structure showing four frames with POH bytes (V5, J2, N2, K4), fixed stuff (R), and data (D) bytes.
+
+NOTE – In the case of virtual concatenation, the frames contain *X* independent VC-2-mc POH bytes.
+
+**Figure 10-20 – Mapping of ATM cells into VC-2-Xc
+using contiguous concatenation**
+
+### 10.2.4 Mapping into VC-2
+
+Figure 10-21 shows the mapping for an ATM cell stream with a data rate of 6.784 Mbit/s.
+
+The VC-2 structure is organized as a four-frame multiframe. The frames of the multiframe consist of one byte of VC-2 POH and 106 bytes of payload area. ATM cells are loaded into the VC-2 payload area with the boundaries of the cells aligned with any VC-2 byte boundary. Because the VC-2 payload space is the equivalent of exactly two ATM cells per 125 µs frame, the alignment between ATM cell boundaries and the VC-2 structure will remain constant from frame to frame. Cells can cross VC-2 frame boundaries.
+
+
+
+The diagram illustrates the structure of a VC-2 multiframe. It consists of four frames, each 125 µs long, totaling 500 µs. Each frame contains one byte of POH (V5, J2, N2, or K4) followed by 106 bytes of payload (D Data). A vertical double-headed arrow on the left indicates the total height of the multiframe is 428 bytes.
+
+| | |
+|-----------|-------------|
+| 428 bytes | V5 |
+| | 106 D bytes |
+| | J2 |
+| | 106 D bytes |
+| | N2 |
+| | 106 D bytes |
+| | K4 |
+| | 106 D bytes |
+
+500 µs G.707-Y.1322\_F10-21
+D Data
+
+Diagram of VC-2 multiframe structure showing four frames with POH bytes V5, J2, N2, K4 and 106 D bytes payload each. Total duration is 500 µs.
+
+**Figure 10-21 – Mapping of ATM cells into VC-2**
+
+### 10.2.5 Mapping into VC-12/VC-11
+
+Figures 10-22 and 10-23 show the mapping for ATM cell streams with data rates of 2.176 Mbit/s and 1.600 Mbit/s into VC-12 and VC-11, respectively.
+
+In floating TU-n mode, the VC-12/VC-11 structure is organized as a four-frame multiframe. The frames of the multiframe consist of one byte of VC-12/VC-11 POH and 34 or 25 bytes, respectively, of payload area. ATM cells are loaded into the VC-12/VC-11 payload area with the boundaries of the cells aligned with any VC-12/VC-11 byte boundary. Because the VC-12/VC-11 payload space is not related to the size of an ATM cell (53 bytes), the alignment between ATM cell boundaries and the VC-12/VC-11 structure will change from frame to frame in a sequence repeating every 53 frames. Cells can cross VC-12/VC-11 frame boundaries.
+
+
+
+| |
+|------------|
+| V5 |
+| 34 D bytes |
+| J2 |
+| 34 D bytes |
+| N2 |
+| 34 D bytes |
+| K4 |
+| 34 D bytes |
+
+140 bytes
+
+500 μs
+
+G.707-Y.1322\_F10-22
+
+D Data
+
+Diagram showing the mapping of ATM cells into VC-12. A vertical stack of 8 cells is shown. The total duration is 500 μs and the total size is 140 bytes. The cells alternate between overhead bytes (V5, J2, N2, K4) and data bytes (34 D bytes).
+
+**Figure 10-22 – Mapping of ATM cells into VC-12**
+
+
+
+| |
+|------------|
+| V5 |
+| 25 D bytes |
+| J2 |
+| 25 D bytes |
+| N2 |
+| 25 D bytes |
+| K4 |
+| 25 D bytes |
+
+104 bytes
+
+500 μs
+
+G.707-Y.1322\_F10-23
+
+D Data
+
+Diagram showing the mapping of ATM cells into VC-11. A vertical stack of 8 cells is shown. The total duration is 500 μs and the total size is 104 bytes. The cells alternate between overhead bytes (V5, J2, N2, K4) and data bytes (25 D bytes).
+
+**Figure 10-23 – Mapping of ATM cells into VC-11**
+
+## **10.3 Mapping of HDLC framed signals**
+
+The mapping of HDLC framed signals [2] is performed by aligning the byte structure of every frame with the byte structure of the virtual container used, including the concatenated structure (VC-n-Xc/VC-n-Xv/VC-n). Since the HDLC frames are of variable length (the mapping does not impose any restrictions on the maximum length), a frame may cross the container-x frame boundary.
+
+HDLC flags (01111110) shall be used for interframe fill to buffer out the asynchronous nature of the arrival of the HDLC framed signals according to the effective payload of the virtual container used (this excludes any fixed stuff bytes).
+
+The HDLC framed signal plus the interframe fill shall be scrambled before they are inserted as payload of the virtual container (VC-n-Xc/VC-n-Xv/VC-4/VC-3) used. In the reverse operation, following termination of the VC signal, the payload will be descrambled before it is passed on to the HDLC layer. A self-synchronizing scrambler with polynomial $x^{43}+1$ shall be used.
+
+The $x^{43}+1$ scrambler shall operate continuously through the bytes of the VC-n-Xc/VC-n-Xv/VC-4/VC-3, bypassing bytes of SDH path overhead. The scrambling state at the beginning of a VC-n-Xc/VC-n-Xv/VC-4/VC-3 shall be the state at the end of the previous VC-n. Thus, the scrambler runs continuously and is not reset per frame. An initial seed of the scrambler is unspecified. Consequently, the first 43 transmitted bits following start-up or SDH reframe operation will not be descrambled correctly.
+
+The $x^{43}+1$ scrambler operates on the input data stream with most significant bit (MSB) first, consistent with the bit ordering and transmission ordering defined for SDH in clause 5.
+
+The above mapping procedure with scrambling shall be used for the mapping of HDLC framed signals (e.g., HDLC/PPP or HDLC/LAPS with IP packets) in any VC-n-Xc/VC-n-Xv/VC-4/VC-3 while scrambling is not required for VC-2/VC-12/VC-11.
+
+There are no further specific requirements for any virtual container size, other than that the appropriate signal label for that container is inserted in the appropriate path overhead location. Path signal labels are specified in clause 9.3.
+
+NOTE – HDLC/PPP frames [13] are also referred to as packet over SDH/SONET (PoS) frames.
+
+## 10.4 Mapping of DQDB into VC-4
+
+The mapping of distributed queue dual bus (DQDB) signals [1] should be performed according to ETSI ETS 300 216.
+
+## 10.5 Asynchronous mapping for FDDI at 125 000 kbit/s into VC-4
+
+The 125 000 kbit/s fibre distributed data interface (FDDI) physical layer signal [3]-[11] is mapped into an SDH VC-4. The VC-4 consists of 1 column (9-bytes) of path overhead (POH) plus a 9-row by 260-column payload structure. For this mapping, each row of 260 bytes is partitioned into 20 blocks of 13 bytes each, see Figure 10-24.
+
+
+
+| | | | | | | | | | | | | | | | | | | | | |
+|----------|-----------------------|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
+| 1 byte | 13 bytes | | | | | | | | | | | | | | | | | | | |
+| J1 | J | A | B | B | B | A | B | B | B | A | B | B | B | A | B | B | B | A | B | X |
+| B3 | J | A | B | B | B | A | B | B | B | A | B | B | B | A | B | B | B | A | B | Y |
+| C2 | J | A | B | B | B | A | B | B | B | A | B | B | B | A | B | B | B | A | B | X |
+| G1 | J | A | B | B | B | A | B | B | B | A | B | B | B | A | B | B | B | A | B | Y |
+| F2 | J | A | B | B | B | A | B | B | B | A | B | B | B | A | B | B | B | A | B | X |
+| H4 | J | A | B | B | B | A | B | B | B | A | B | B | B | A | B | B | B | A | B | Y |
+| F3 | J | A | B | B | B | A | B | B | B | A | B | B | B | A | B | B | B | A | B | X |
+| K3 | J | A | B | B | B | A | B | B | B | A | B | B | B | A | B | B | B | A | B | Y |
+| N1 | J | A | B | B | B | A | B | B | B | A | B | B | B | A | B | B | B | A | B | X |
+| VC-4 POH | 20 blocks of 13 bytes | | | | | | | | | | | | | | | | | | | |
+
+G.707-Y.1322\_F10-24
+
+Figure 10-24: Block structure of VC-4 for asynchronous mapping of FDDI. The diagram shows a grid representing the VC-4 frame structure. The first column contains POH bytes (J1 to N1). The payload is divided into 20 blocks of 13 bytes each. The grid shows a repeating pattern of bytes labeled J, A, B, and ends with X or Y.
+
+**Figure 10-24 – Block structure of VC-4 for asynchronous mapping of FDDI**
+
+There are five block types: J, A, B, X and Y. The blocks consist of 13 bytes. The definitions of them are given in Figure 10-25.
+
+
+
+13-byte blocks
+
+| | | | | | | | | | | | | | | |
+|---|---|----|---|---|---|---|---|---|---|---|---|---|---|---|
+| J | = | O | I | I | I | R | I | I | I | R | I | I | I | I |
+| A | = | C | I | I | I | I | I | I | I | I | I | I | I | I |
+| B | = | R | I | I | I | R | I | I | I | R | I | I | I | I |
+| X | = | S1 | I | I | I | R | I | I | I | I | I | I | I | I |
+| Y | = | S2 | I | I | I | R | I | I | I | I | I | I | I | I |
+
+
+
+| | | | | | | | | | |
+|--------|---|--------|---|---|---|---|---|---|---|
+| 8 bits | | 8 bits | | | | | | | |
+| I | = | i | i | i | i | i | i | i | i |
+| O | = | i | i | i | i | i | i | i | o |
+| R | = | r | r | r | r | r | r | r | r |
+| C | = | i | i | i | i | i | i | i | c |
+| S1 | = | i | i | i | i | i | i | i | s |
+| S2 | = | i | i | i | i | i | i | s | r |
+
+G.707-Y.1322\_F10-25
+
+C Justification control bit
+ I Information bit
+ O Overhead bit
+ R Fixed justification bit
+ S Justification opportunity bit
+
+Figure 10-25: Block contents for asynchronous mapping of FDDI. The diagram shows five 13-byte blocks (J, A, B, X, Y) and their constituent bit patterns (I, O, R, C, S1, S2).
+
+**Figure 10-25 – Block contents for asynchronous mapping of FDDI**
+
+In order to accommodate the asynchronous FDDI payload (approximately $15\,625 \pm 1$ bits per VC-4), a bit justification mechanism is utilized. The 15 620 information bits (**i**) and the 9 justification opportunity bits (**s**) within this structure carry the FDDI physical layer bits. In each row of the payload structure, five justification control bits (**c**) are used to control the corresponding justification opportunity bit (**s**) of that row.
+
+If the **s** bit is used to carry information, the five **c** bits are set to zero $\{c\ c\ c\ c\ c = 0\ 0\ 0\ 0\ 0\}$ . If the **s** bit is used as a justification bit, the five **c** bits are set to one $\{c\ c\ c\ c\ c = 1\ 1\ 1\ 1\ 1\}$ . The value contained in the **s** bit when used as a justification bit is not defined. The receiver shall ignore the value contained in this bit whenever it is used as a justification bit. Majority vote should be used to make the justification decision in the desynchronizer for protection against single- and double-bit errors in the **c** bits.
+
+The overhead bits (**o**) are reserved for future overhead communication purposes. The remaining bits are fixed stuff bits (**r**).
+
+## 10.6 Mapping of GFP frames
+
+The GFP frame stream is mapped into a container-n ( $n = 11, 12, 2, 3, 4, 4-Xc, 11-Xv/12-Xv/2-Xv/3-Xv/4-Xv$ ) with its byte boundaries aligned with the byte boundaries of the container-n (see Figure 10-26). The container-n is then mapped into the VC-n respectively, together with the associated POH as specified in clause 9.3. The GFP frame boundaries are thus aligned with the VC-n byte boundaries. Since the container-n capacity is not an integer multiple of the variable length GFP Frame, a GFP frame may cross a container-n frame boundary.
+
+
+
+Diagram illustrating the mapping of GFP frames into a C-n container. The top part shows a large rectangle representing the C-n container, with several smaller rectangles representing GFP frames and GFP Idles being mapped into it. The bottom part shows a detailed view of a GFP frame, which consists of a 'Core header' and a 'Payload area'. A 'GFP Idle' is also shown as a separate entity. The diagram is labeled 'G.707-Y.1322\_F10-26'.
+
+**Figure 10-26 – Mapping of GFP frames into C-n**
+
+A GFP frame consists of a GFP core header and a GFP payload area. GFP frames arrive as a continuous byte stream with a capacity that is identical to the VC payload, due to the insertion of GFP Idles at the GFP adaptation stage. See also ITU-T Rec. G.704/Y.1303.
+
+NOTE – There is no rate adaptation or scrambling required at the mapping stage. The GFP adaptation process performs these functions.
+
+## 10.7 Asynchronous mapping of ODUk into a C-4-X transported via a VC-4-Xv
+
+The purpose of this mapping is to provide for the transport of a subset of OTN elements, as defined in ITU-T Rec. G.709/Y.1331, over existing SDH transport networks by means of VC-4 virtual concatenation.
+
+The number of VC-4s required to transport an OTN element by means of virtual concatenation is found by dividing the bit rate of the OTN entity by the payload rate of a VC-4-Xv, the C-4-X. These are provided in Table 10-2. As this number is not an integer, it is necessary to provide both a fixed stuff to pad the C-4-X payload area and a means of mapping the client into the remainder of the payload area.
+
+**Table 10-2 – Mapping of OTN elements in SDH virtually concatenated VC-4s**
+
+| OTN entity | Nominal bit rate, kbit/s ODUk | VC-4 virtual concatenation order (X) | Nominal bit rate, kbit/s VC-4-Xv |
+|------------|----------------------------------------------------------------|--------------------------------------|----------------------------------|
+| ODU1 | $239/238 \times 2\,488\,320$ ( $\approx 2\,498\,775.126$ ) | 17 | 2 545 920 |
+| ODU2 | $239/237 \times 9\,953\,280$ ( $\approx 10\,037\,273.924$ ) | 68 | 10 183 680 |
+
+The ODUk signal is extended with frame alignment overhead (FAS and MFAS bytes) as specified in clauses 15.6.2.1 and 15.6.2.2/G.709/Y.1331 and an all-0's pattern in the OTUk overhead field (Figure 10-27).
+
+
+
+| | | | |
+|-----|--------------------|----------------------|-------------------------------|
+| Row | Column | | 15 3824 |
+| | 1 7 | 8 14 | |
+| 1 | FA overhead area | Fixed-stuff (all-0s) | OPUk area (4 × 3810 bytes) |
+| 2 | ODUk overhead area | | |
+| 3 | | | |
+| 4 | | | |
+
+G.707-Y.1322\_F10-27
+
+Figure 10-27: Extended ODUk frame structure diagram. The diagram shows a grid with 4 rows and 3824 columns. Row 1 contains 'FA overhead area' (columns 1-7), 'Fixed-stuff (all-0s)' (columns 8-14), and 'OPUk area (4 x 3810 bytes)' (columns 15-3824). Rows 2, 3, and 4 contain 'ODUk overhead area' (columns 1-14) and 'OPUk area' (columns 15-3824). Column headers are '1 7', '8 14', '15', and '3824'. Row headers are '1', '2', '3', '4'.
+
+**Figure 10-27 – Extended ODUk frame structure
+(FA OH included, OTUk OH area contains fixed stuff)**
+
+Before the extended ODUk signal is mapped into the C-4-X, it is scrambled using a self-synchronizing scrambler with polynomial $x^{43}+1$ . The scrambler operates over the whole extended ODUk frame and is not reset per frame.
+
+### 10.7.1 Asynchronous mapping of ODU1 into a C-4-17 transported via a VC-4-17v
+
+The basic C-4-17 structure is as shown in Figure 10-28. It is comprised of 9 rows by 4420 (i.e., $17 \times 260$ ) columns.
+
+
+
+Figure 10-28: C-4-17 structure diagram. The diagram shows a grid with 9 rows and 4420 columns. The central area is labeled 'C-4-17 (9 x 4 420 bytes)'. Column headers are '1 2' and '4420'. Row headers are '1' through '9'.
+
+**Figure 10-28 – C-4-17 structure**
+
+This C-4-17 frame is transported via a VC-4-17v. Refer to clause 11.2.
+
+The extended ODU1 signal is asynchronously mapped into this C-4-17 with the following structure:
+
+- Each of the nine rows is partitioned into 5 blocks, consisting of 884 octets each (Figure 10-29).
+- Each block is partitioned into 17 subblocks, consisting of 52 octets each.
+ - In each subblock, one negative justification opportunity octet (S) and five justification control bits (C) are provided.
+
+- The first byte of each subblock consists of either:
+ - a fixed stuff byte (R); or
+ - a justification control byte (J), which consists of seven fixed stuff bits (bits R; bits 1 to 7) and a justification control bit (bit C, bit 8); or
+ - a negative justification opportunity byte (S).
+- The last 51 bytes of one subblock consist of data bytes (D).
+
+NOTE 1 – Each block contains a total of $(17 \times 51) = 867$ data bytes.
+
+The sequence of all these bytes is shown in Figure 10-29.
+
+
+
+1 2 4420
+
+| | | | | | |
+|---|------------|------------|------------|------------|------------|
+| 1 | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets |
+| 2 | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets |
+| 3 | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets |
+| 4 | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets |
+| 5 | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets |
+| 6 | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets |
+| 7 | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets |
+| 8 | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets |
+| 9 | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets |
+
+17 subblocks of 52 octets
+
+| | | | | | | | | | | | | | | | |
+|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|
+| R | 51D | J | 51D | R | 51D | R | 51D | J | 51D | R | 51D | R | 51D | J | 51D |
+|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|
+
+
+
+| | | | | | | | | | | | | | | | | | |
+|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|
+| R | 51D | R | 51D | J | 51D | R | 51D | R | 51D | J | 51D | R | 51D | R | 51D | S | 51D |
+|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|
+
+1 2 3 4 5 6 7 8
+
+| | | | | | | | |
+|---|---|---|---|---|---|---|---|
+| R | R | R | R | R | R | R | C |
+|---|---|---|---|---|---|---|---|
+
+51D 51 data octets
+R Fixed stuff
+C Justification control
+
+G.707/Y.1322\_F10-29
+
+**Figure 10-29 – Block structure for ODU1 mapping into C-4-17**
+
+The set of five justification control bits (C) in every subblock is used to control the corresponding negative justification opportunity byte (S). CCCCC = 00000 indicates that the S byte is an information byte, whereas CCCCC = 11111 indicates that the S byte is a justification byte.
+
+At the synchronizer all five C bits are set to the same value. Majority vote (3 out of 5) should be used to make the justification decision at the desynchronizer for protection against single and double bit errors in the JC bits.
+
+The value contained in the S byte when used as justification byte is all-ZEROs. The receiver is required to ignore the value contained in this byte whenever it is used as a justification byte.
+
+The value contained in the R bits and bytes is all-ZEROs. The receiver is required to ignore the value contained in these bits/bytes.
+
+NOTE 2 – The maximum bit-rate tolerance between C-4-17 and the ODU1 signal clock, which can be accommodated by this mapping scheme, is approximately $-720$ to $+420$ ppm. The nominal justification ratio
+
+is 75/119, which is approximately equal to 0.630252. Here, the justification ratio is normalized to 1, i.e., it is the long-run average fraction of justification opportunities for which there is a justification.
+
+### 10.7.2 Asynchronous mapping of ODU2 into a C-4-68 transported via a VC-4-68v
+
+The basic C-4-68 structure is as shown in Figure 10-30. It is comprised of 9 rows by 17 680 (i.e., $68 \times 260$ ) columns.
+
+
+
+The diagram illustrates the C-4-68 structure as a rectangular grid. Above the grid, a horizontal line with a dot at the left end and a dot at the right end spans the width, with the number '1' at the far left and '17 680' at the far right. To the left of the grid, the numbers '1' through '9' are listed vertically, corresponding to the rows. Inside the grid, the text 'C-4-68' and '(9 × 17 680 bytes)' is centered.
+
+Diagram of C-4-68 structure showing 9 rows and 17 680 columns.
+
+Figure 10-30 – C-4-68 structure
+
+This C-4-68 frame is transported via a VC-4-68v. Refer to clause 11.2.
+
+The extended ODU2 signal is asynchronously mapped into this C-4-68 with the following structure:
+
+- Each of the nine rows is partitioned into 20 blocks, consisting of 884 octets each (Figure 10-31).
+- Each block is partitioned into 13 subblocks, consisting of 68 octets each.
+ - In each subblock, one negative justification opportunity octet (S) and five justification control bits (C) are provided.
+ - The first byte of each subblock consists of either:
+ - a fixed stuff byte (R); or
+ - a justification control byte (J), which consists of seven fixed stuff bits (bits R; bits 1 to 7) and a justification control bit (bit C, bit 8); or
+ - a negative justification opportunity byte (S).
+ - The last 67 bytes of one subblock consist of data bytes (D).
+
+NOTE 1 – Each block contains a total of $(13 \times 67) = 871$ data bytes.
+
+The sequence of all these bytes is shown in Figure 10-31.
+
+
+
+1 2 ..... 17 680
+
+| | | | | | | | | | |
+|---|------------|------------|------------|------------|------------|------------|------------|-----------|------------|
+| 1 | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | - - - - - | 884 octets |
+| 2 | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | - - - - - | 884 octets |
+| 3 | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | - - - - - | 884 octets |
+| 4 | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | - - - - - | 884 octets |
+| 5 | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | - - - - - | 884 octets |
+| 6 | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | - - - - - | 884 octets |
+| 7 | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | - - - - - | 884 octets |
+| 8 | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | - - - - - | 884 octets |
+| 9 | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | 884 octets | - - - - - | 884 octets |
+
+13 subblocks of 68 octets
+
+| | | | | | | | | | | | |
+|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|
+| R | 67D | R | 67D | J | 67D | R | 67D | J | 67D | R | 67D |
+|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|
+
+| | | | | | | | | | | | | | |
+|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|
+| J | 67D | R | 67D | J | 67D | R | 67D | J | 67D | R | 67D | S | 67D |
+|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|---|-----|
+
+67D 67 data octets
+R Fixed stuff
+C Justification control
+
+| | | | | | | | |
+|---|---|---|---|---|---|---|---|
+| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
+| R | R | R | R | R | R | R | C |
+
+G.707/Y.1322\_F10-31
+
+**Figure 10-31 – Block structure for ODU2 mapping into C-4-68**
+
+The set of five justification control bits (C) in every subblock is used to control the corresponding negative justification opportunity byte (S). CCCCC = 00000 indicates that the S byte is an information byte, whereas CCCCC = 11111 indicates that the S byte is a justification byte.
+
+At the synchronizer, all five C bits are set to the same value. Majority vote (3 out of 5) should be used to make the justification decision at the desynchronizer for protection against single- and double-bit errors in the JC bits.
+
+The value contained in the S byte, when used as justification byte, is all-ZEROs. The receiver is required to ignore the value contained in this byte whenever it is used as a justification byte.
+
+The value contained in the R bits and bytes is all-ZEROs. The receiver is required to ignore the value contained in these bits/bytes.
+
+NOTE 2 – The maximum bit-rate tolerance between C-4-68 and the ODU2 signal clock, which can be accommodated by this mapping scheme, is approximately –330 to +810 ppm. The nominal justification ratio is 23/79, which is approximately equal to 0.291139. Here, the justification ratio is normalized to 1, i.e., it is the long-run average fraction of justification opportunities for which there is a justification.
+
+# 11 VC concatenation
+
+For the transport of payloads that do not fit efficiently into the standard set of virtual containers (VC-11, VC-12, VC-2, VC3, VC4) VC concatenation can be used. VC concatenation is defined for:
+
+- VC-4 – to provide transport for payloads that require capacity greater than one container-4;
+- VC-3 – to provide transport for payloads that require capacity greater than one container-3;
+- VC-2 – to provide transport for payloads that require capacity greater than one container-2;
+- VC-12 – to provide transport for payloads that require capacity greater than one container-12;
+- VC-11 – to provide transport for payloads that require capacity greater than one container-11.
+
+Two methods for concatenation are defined: contiguous and virtual concatenation. Both methods provide concatenated bandwidth of $X \times \text{container-n}$ at the path termination. The difference is the transport between the path terminations. Contiguous concatenation maintains the contiguous bandwidth throughout the whole transport, while virtual concatenation breaks the contiguous bandwidth into individual VCs, transports the individual VCs and recombines these VCs to a contiguous bandwidth at the end point of the transmission. Virtual concatenation requires concatenation functionality only at the path termination equipment, while contiguous concatenation requires concatenation functionality at each network element.
+
+It is possible to perform a conversion between the two types of concatenation. The conversion between virtual and contiguous VC-4 concatenation is defined in ITU-T Rec. G.783. The conversion between virtual and contiguous VC-2 concatenation is for further study.
+
+## 11.1 Contiguous concatenation of X VC-4s (VC-4-Xc, X = 4, 16, 64, 256)
+
+A VC-4-Xc provides a payload area of $X \times \text{container-4}$ and is represented by a C-4-X structure as shown in Figure 11-1. One common set of POH, located in the first column, is used for the whole VC-4-Xc (e.g., the BIP-8 covers all $261 \times X$ columns of the VC-4-Xc). Columns 2 to X are fixed stuff.
+
+
+
+The diagram illustrates the structure of a VC-4-Xc. It is a grid with 9 rows and X columns. Row 1 is labeled '1' and row 9 is labeled '9'. Column 1 contains the following bytes from top to bottom: J1, B3, C2, G1, F2, H4, F3, K3, and N1. This column is shaded and labeled 'Fixed stuff'. Columns 2 through X are labeled 'C-4-X'. Below the grid, a horizontal dimension line shows the total width as $X \times 261$ columns. A sub-dimension line shows the first column as '1' and the remaining columns as $X-1$ . Another sub-dimension line shows a segment of $X \times 260$ columns. To the right of the grid, a vertical dimension line indicates a duration of 125 µs. The diagram is labeled 'G.707-Y.1322\_F11-1' at the bottom right.
+
+Diagram of VC-4-Xc structure showing columns 1 to X and rows 1 to 9. Column 1 contains POH bytes (J1, B3, C2, G1, F2, H4, F3, K3, N1) and is labeled 'Fixed stuff'. Columns 2 to X are labeled 'C-4-X'. The total width is X \* 261 columns. A duration of 125 µs is indicated for the full frame.
+
+Figure 11-1 – VC-4-Xc structure
+
+The VC-4-Xc is transported in X contiguous AU-4 in the STM-N signal. The first column of the VC-4-Xc is always located in the first AU-4. The pointer of this first AU-4 indicates the position of the J1 byte of the VC-4-Xc. The pointers of the AU-4 #2 to X are set to the concatenation indication
+
+(see Figure 8-3) to indicate the contiguously concatenated payload. Pointer justification is performed in common for the X concatenated AU-4s and X\*3 stuffing bytes are used.
+
+A VC-4-Xc provides a payload capacity of 599'040 kbit/s for X = 4, 2'396'160 kbit/s for X = 16, 9'584'640 kbit/s for X = 64 and 38'338'560 kbit/s for X = 256.
+
+NOTE – High rate VC-4-Xc could be used without any constraints in point-to-point connections. SDH networks may be limited to a certain bit rate of VC-4-Xc (e.g., X ≤ 64), e.g., due to rings with MS SPRING that has to reserve 50% of the STM-N bandwidth for protection.
+
+## 11.2 Virtual concatenation of X VC-3s/VC-4s (VC-3-Xv/VC-4-Xv, X = 1 ... 256)
+
+A VC-3-Xv/VC-4-Xv provides the transport capability equivalent to X\*container-3/container-4, which can be represented by a C-3-X/C-4-X like structure, and has a payload capacity of X\*48'384/149'760 kbit/s as depicted in Figures 11-2 and 11-3. The payload is mapped into X individual VC-3s/VC-4s which form the VC-3-Xv/VC-4-Xv, as illustrated in Appendix XIV. Each VC-3/VC-4 has its own POH as specified in clause 9.3.1. The H4 POH byte is used for the virtual concatenation-specific sequence and multiframe indication as defined below.
+
+
+
+The diagram illustrates the structure of a VC-3-Xv. At the top, a large rectangle represents the C-3-X container, with a width of X × 84 bytes and a height of 125 μs. The left side of this container is divided into X slots, numbered 1 to X at the top and 1 to 9 at the bottom. Below the container, the text 'C-3-X' is centered.
+
+Below the C-3-X container, the diagram shows the internal structure of the individual VC-3s. A bracket on the right side groups several VC-3s, labeled 'VC-3-Xv'. The first VC-3 is labeled 'VC-3 #1' and the last one shown is 'VC-3 #X'. Each VC-3 has a width of 85 bytes and a height of 125 μs. The left side of each VC-3 is divided into slots numbered 1 to 9 at the bottom. The first slot (labeled '1' at the top) contains the POH bytes: J1, B3, C2, G1, F2, H4, F3, K3, and N1. The second slot (labeled '1' at the top) contains the H4 byte, which is shown as 'J1' and 'B3' in the diagram. The remaining 83 bytes of each VC-3 are shown as a series of dots, representing the payload.
+
+Lines connect the X slots in the C-3-X container to the corresponding VC-3s. The text 'G.707-Y.1322\_F11-2' is located at the bottom right.
+
+Diagram of VC-3-Xv structure showing the mapping of X individual VC-3s into a C-3-X container.
+
+Figure 11-2 – VC-3-Xv structure
+
+
+
+The diagram illustrates the structure of a VC-4-Xv frame within a C-4-X container. The container is shown as a rectangle labeled 'C-4-X' with dimensions 'X' (width) and '260' (height), and a duration of '125 μs'. The VC-4 #X frame is shown as a rectangle labeled 'VC-4 #X' with dimensions '261' (width) and '125 μs' (height). The frame contains a list of overhead bytes: J1, B3, C2, G1, F2, H4, F3, K3, N1. The J1 and B3 bytes are shown in a separate box above the main frame, with arrows pointing to their positions within the frame. The text 'G.707-Y.1322\_F11-3' is at the bottom right.
+
+Diagram of VC-4-Xv structure showing the mapping of VC-4 #X into a C-4-X container. The top part shows a C-4-X container of size X x 260 frames, with a duration of 125 μs. The bottom part shows a VC-4 #X frame of size 261 frames, with a duration of 125 μs. The VC-4 #X frame contains a list of overhead bytes: J1, B3, C2, G1, F2, H4, F3, K3, N1. The J1 and B3 bytes are shown in a separate box above the main frame, with arrows pointing to their positions within the frame. The text 'G.707-Y.1322\_F11-3' is at the bottom right.
+
+**Figure 11-3 – VC-4-Xv structure**
+
+Each VC-3/VC-4 of the VC-3-Xv/VC-4-Xv is transported individually through the network. Due to the different propagation delays of the VC-3s/VC-4s, a differential delay will occur between the individual VC-3s/VC-4s. At the path termination this differential delay has to be compensated and the individual VC-3s/VC-4s have to be realigned for access to the contiguous payload area. The realignment process has to cover at least a differential delay of 125 μs.
+
+A two-stage 512 ms multiframe is introduced to cover differential delays of 125 μs and above (up to 256 ms). The first stage uses H4, bits 5-8 for the 4-bit multiframe indicator (MFI1). MFI1 is incremented every basic frame and counts from 0 to 15. For the 8-bit multiframe indicator of the second stage (MFI2), H4, bits 1-4 in frame 0 (MFI2 bits 1-4) and 1 (MFI2 bits 5-8) of the first multiframe are used (see Table 11-1). MFI2 is incremented once every multiframe of the first stage and counts from 0 to 255. The resulting overall multiframe is 4096 frames (= 512 ms) long.
+
+**Table 11-1 – VC-3-Xv/VC-4-Xv sequence and multiframe indicator H4 coding**
+
+| H4 byte | | | | | | | | 1st multi-frame number | 2nd multi-frame number |
+|----------------------------------------------|-------|-------|-------|-------------------------------------------------|-------|-------|-------|------------------------|------------------------|
+| Bit 1 | Bit 2 | Bit 3 | Bit 4 | Bit 5 | Bit 6 | Bit 7 | Bit 8 | | |
+| | | | | 1st multiframe indicator MFI1 (bits 1-4) | | | | | |
+| Sequence indicator MSB (bits 1-4) | | | | 1 | 1 | 1 | 0 | 14 | n-1 |
+| Sequence indicator LSB (bits 5-8) | | | | 1 | 1 | 1 | 1 | 15 | |
+| 2nd multiframe indicator MFI2 MSB (bits 1-4) | | | | 0 | 0 | 0 | 0 | 0 | n |
+| 2nd multiframe indicator MFI2 LSB (bits 5-8) | | | | 0 | 0 | 0 | 1 | 1 | |
+| Reserved ("0000") | | | | 0 | 0 | 1 | 0 | 2 | |
+| Reserved ("0000") | | | | 0 | 0 | 1 | 1 | 3 | |
+| Reserved ("0000") | | | | 0 | 1 | 0 | 0 | 4 | |
+| Reserved ("0000") | | | | 0 | 1 | 0 | 1 | 5 | |
+| Reserved ("0000") | | | | 0 | 1 | 1 | 0 | 6 | |
+| Reserved ("0000") | | | | 0 | 1 | 1 | 1 | 7 | |
+| Reserved ("0000") | | | | 1 | 0 | 0 | 0 | 8 | |
+| Reserved ("0000") | | | | 1 | 0 | 0 | 1 | 9 | |
+| Reserved ("0000") | | | | 1 | 0 | 1 | 0 | 10 | |
+| Reserved ("0000") | | | | 1 | 0 | 1 | 1 | 11 | |
+| Reserved ("0000") | | | | 1 | 1 | 0 | 0 | 12 | |
+| Reserved ("0000") | | | | 1 | 1 | 0 | 1 | 13 | |
+| Sequence indicator SQ MSB (bits 1-4) | | | | 1 | 1 | 1 | 0 | 14 | |
+| Sequence indicator SQ LSB (bits 5-8) | | | | 1 | 1 | 1 | 1 | 15 | |
+| 2nd multiframe indicator MFI2 MSB (bits 1-4) | | | | 0 | 0 | 0 | 0 | 0 | n+1 |
+| 2nd multiframe indicator MFI2 LSB (bits 5-8) | | | | 0 | 0 | 0 | 1 | 1 | |
+| Reserved ("0000") | | | | 0 | 0 | 1 | 0 | 2 | |
+
+The sequence indicator (SQ) identifies the sequence/order in which the individual VC-3s/VC-4s of the VC-3-Xv/VC-4-Xv are combined to form the contiguous payload C-3-X/C-4-X like structure as shown in Figure 11-4. Each VC-3/VC-4 of a VC-3-Xv/VC-4-Xv has a fixed unique sequence number in the range of 0 to (X-1).
+
+The VC-4 transporting the:
+
+- data from cols 1, X+1, 2X+1, .. 259X+1 of the C-4-X like structure has the sequence number 0;
+- data from cols 2, X+2, 2X+2, .. 259X+2 of the C-4-X like structure has the sequence number 1;
+
+and so on up to the VC-4 transporting the:
+
+- data from cols X, X+X, 2X+X, ..259X+X of the C-4-X like structure has the sequence number (X-1).
+
+The VC-3 transporting the:
+
+- data from cols 1, X+1, 2X+1, ... 83X+1 of the C-3-X like structure has the sequence number 0;
+- data from cols 2, X+2, 2X+2, ... 83X+2 of the C-3-X like structure has the sequence number 1;
+
+and so on up to the VC-3 transporting the:
+
+- data from cols X, X+X, 2X+X, ... 83X+X of the C-3-X like structure has the sequence number (X-1).
+
+For applications requiring fixed bandwidth, the sequence number is fixed assigned and not configurable. This allows the constitution of the VC-3-Xv/VC-4-Xv to be checked without using the trace. The 8-bit sequence number (which supports values of X up to 256) is transported in bits 1 to 4 of the H4 bytes, using frame 14 (SQ bits 1-4) and 15 (SQ bits 5-8) of the first multiframe stage as shown in Table 11-1.
+
+
+
+G.707-Y.1322\_F11-4
+
+Diagram illustrating the mapping of C-3-X/C-4-X data to VC-3-Xv/VC-4-Xv multiframes. The left side shows a C-3-X/C-4-X structure with columns 1, X, and X+1. The right side shows the corresponding VC-3-Xv/VC-4-Xv multiframe structure, which is a vertical stack of frames. Each frame contains a POH (Path Overhead) and a payload. The sequence number (SQ) is indicated in the POH of each frame. The diagram shows three multiframes (MF) stacked vertically. The first multiframe contains frames with SQ = X-1, SQ = 0, and SQ = 0. The second multiframe contains frames with SQ = X-1, SQ = 0, and SQ = 0. The third multiframe contains frames with SQ = X-1, SQ = 0, and SQ = 0. The sequence number (SQ) is shown in the POH of each frame, along with MFI-1 and MFI-2 values. The diagram also shows the mapping of data from columns 1, X, and X+1 of the C-3-X/C-4-X structure to the VC-3-Xv/VC-4-Xv multiframe structure.
+
+**Figure 11-4 – VC-3-Xv/VC-4-Xv multiframe and sequence indicator**
+
+### 11.2.1 Higher order LCAS for VC-n-Xv (n = 3, 4)
+
+Table 11-2 depicts the modified VC-3, VC-4 H4 HO virtual concatenation 1st multiframe, as defined in clause 11.2, indicating the control codes used for the support of HO LCAS. See also ITU-T Rec. G.7042/Y.1305.
+
+- Frame indicator: A combination of the 1st multiframe and the 2nd multiframe counter [0-4095].
+- Sequence indicator: Number to identify each member in the VCG [0-255].
+- CTRL: LCAS control field, see Table 1/G.7042/Y.1305.
+- GID: Group identification bit.
+
+- Member status: The status report of the individual members uses the MST-multiframe as shown in Table 11-3. The status of all members (256) is transferred in 64 ms.
+- RS-Ack: Re-sequence acknowledge bit.
+- CRC: Eight-bit CRC check for fast acceptance of virtual concatenation OH. With this CRC-8 the probability of an undetected error is better than $1.52 \times 10^{-16}$ . The CRC generator polynomial is $x^8 + x^2 + x + 1$ .
+
+**Table 11-2 – VC-n-Xv sequence and multiframe indicator H4 coding**
+
+| H4 byte | | | | | | | | 1st multiframe number | 2nd multiframe number |
+|----------------------------------------------|----------------|----------------|----------------|-------|-------|-------|-------|-----------------------|-----------------------|
+| Bit 1 | Bit 2 | Bit 3 | Bit 4 | Bit 5 | Bit 6 | Bit 7 | Bit 8 | | |
+| 1st multiframe indicator MFI1 (bits 1-4) | | | | | | | | | |
+| Sequence indicator MSB (bits 1-4) | | | | 1 | 1 | 1 | 0 | 14 | n-1 |
+| Sequence indicator LSB (bits 5-8) | | | | 1 | 1 | 1 | 1 | 15 | |
+| 2nd multiframe indicator MFI2 MSB (bits 1-4) | | | | 0 | 0 | 0 | 0 | 0 | n |
+| 2nd multiframe indicator MFI2 LSB (bits 5-8) | | | | 0 | 0 | 0 | 1 | 1 | |
+| CTRL | | | | 0 | 0 | 1 | 0 | 2 | |
+| GID ("000x") | | | | 0 | 0 | 1 | 1 | 3 | |
+| Reserved ("0000") | | | | 0 | 1 | 0 | 0 | 4 | |
+| Reserved ("0000") | | | | 0 | 1 | 0 | 1 | 5 | |
+| CRC-8 | | | | 0 | 1 | 1 | 0 | 6 | |
+| CRC-8 | | | | 0 | 1 | 1 | 1 | 7 | |
+| Member status MST | | | | 1 | 0 | 0 | 0 | 8 | |
+| Member status MST | | | | 1 | 0 | 0 | 1 | 9 | |
+| 0 | 0 | 0 | RS_Ack | 1 | 0 | 1 | 0 | 10 | |
+| Reserved ("0000") | | | | 1 | 0 | 1 | 1 | 11 | |
+| Reserved ("0000") | | | | 1 | 1 | 0 | 0 | 12 | |
+| Reserved ("0000") | | | | 1 | 1 | 0 | 1 | 13 | |
+| Sequence indicator SQ MSB (bits 1-4) | | | | 1 | 1 | 1 | 0 | 14 | |
+| Sequence indicator SQ LSB (bits 5-8) | | | | 1 | 1 | 1 | 1 | 15 | |
+| 2nd multiframe indicator MFI2 MSB (bits 1-4) | | | | 0 | 0 | 0 | 0 | 0 | n+1 |
+| 2nd multiframe indicator MFI2 LSB (bits 5-8) | | | | 0 | 0 | 0 | 1 | 1 | |
+| CTRL | | | | 0 | 0 | 1 | 0 | 2 | |
+| 0 | 0 | 0 | GID | 0 | 0 | 1 | 1 | 3 | |
+| Reserved ("0000") | | | | 0 | 1 | 0 | 0 | 4 | |
+| Reserved ("0000") | | | | 0 | 1 | 0 | 1 | 5 | |
+| C 1 | C 2 | C 3 | C 4 | 0 | 1 | 1 | 0 | 6 | |
+| C 5 | C 6 | C 7 | C 8 | 0 | 1 | 1 | 1 | 7 | |
+| Member status MST | | | | 1 | 0 | 0 | 0 | 8 | |
+
+**Table 11-3 – H4 VC-n-Xv member status**
+
+| 2nd multiframe frame number | Member number | | | | |
+|-------------------------------------|---------------|-----|-----|-----|----------------|
+| | 0 | 1 | 2 | 3 | |
+| 0, 32, 64, 96, 128, 160, 192, 224 | 0 | 1 | 2 | 3 | MST-multiframe |
+| | 4 | 5 | 6 | 7 | |
+| 1, 33, 65, 97, 129, 161, 193, 225 | 8 | 9 | 10 | 11 | |
+| | 12 | 13 | 14 | 15 | |
+| . | . | . | . | . | |
+| . | . | . | . | . | |
+| . | . | . | . | . | |
+| | | | | | |
+| 30, 62, 94, 126, 158, 190, 222, 254 | 240 | 241 | 242 | 243 | |
+| | 244 | 245 | 246 | 247 | |
+| 31, 63, 95, 127, 159, 191, 223, 255 | 248 | 249 | 250 | 251 | |
+| | 252 | 253 | 254 | 255 | |
+
+NOTE 1 – There are 8 member statuses reported per VC-n-Xv frame. The 256 members require 32 frames at a frame rate of 2 ms each. This, therefore, results in the member status being refreshed every 64 ms if there is only one return channel.
+
+NOTE 2 – The interpretation of the member status bits according to this table is based on the 2nd multiframe value at the moment the member status word is received. In the case of VC-3/VC-4 this means that first the 2nd multiframe value is read from H4[1-4][0] and H4[1-4][1], a value between 0 and 255, and, consequently, this value is used (modulo 32) as an index for this table to identify the members of which the status is received in the H4[1-4][8] and H4[1-4][9] nibbles immediately after. This is still within the same 1st multiframe, but just in the next control packet.
+
+#### 11.2.1.1 High order control packet
+
+The high order control packet consists of:
+
+- MST (member status) field (two nibbles 1st multiframe #8 and #9);
+- RS-Ack (re-sequence acknowledge) bit (bit 4 of nibble 1st multiframe #10);
+- SQ (sequence indicator) field (two nibbles 1st multiframe #14 and #15);
+- MFI2 (2nd multiframe indicator) (two nibbles 1st multiframe #0 and #1);
+- CTRL (control) field (one nibble 1st multiframe #2);
+- GID (group identification) bit (bit 4 of nibble 1st multiframe #3);
+- The CRC-8 field is sent with one nibble in each of frame #6 and frame #7. (Note that in this paragraph, unless otherwise indicated, the frame numbers are those indicated by the 1st multiframe number field.) The CRC-8 field, $C_1C_2C_3C_4C_5C_6C_7C_8$ is the remainder of the CRC-8 calculation over the control packet. In the example of Table 11-2, the control packet bits are contained in H4[1-4] of the frames 8...15 of multiframe $n$ and H4[1-4] of the frames 0...7 of multiframe $n + 1$ (where multiframes $n$ and $n + 1$ are indicated by the 2nd multiframe indicator bits). The CRC-8 remainder is calculated as follows: The first 14 nibbles of the control packet bits represent a polynomial $M(x)$ of degree 55, where H4[1] of frame 8, 2nd multiframe $n$ is the most significant bit and H4[4] of frame 5, 2nd multiframe $n + 1$ is the least significant bit. $M(x)$ is first multiplied by $x^8$ and then divided (modulo 2) by generator polynomial $G(x) = x^8 + x^2 + x + 1$ to produce a remainder $R(x)$ of degree 7 or less. $R(x)$ is the CRC-8 code with $x^7$ of $R(x)$ corresponding to $C_1$ as the most significant bit of the remainder and $x^0$ of $R(x)$ corresponding to $C_8$ as the least significant bit of the remainder;
+- All other 1st multiframe nibbles (#11, #12, #13, #4 and #5) are reserved and should be set to "0000".
+
+The high order control packet starts at 1st multiframe #8 and ends at 1st multiframe #7 in the next multiframe as shown between the heavy lines in Table 11-2.
+
+## 11.3 Contiguous concatenation of X VC-2s in a higher order VC-3 (VC-2-Xc, X = 1 ... 7)
+
+A VC-2-Xc provides a payload area of $X \times \text{container-2}$ and is represented by a C-2-X structure as shown in Figure 11-5. One common set of POH, corresponding to the POH of the first VC-2, is used for the whole VC-2-Xc (e.g., the BIP-2 covers all $428 \times X$ bytes of the VC-2-Xc). The POH positions corresponding to VC-2 #2 to VC-2 #X are fixed stuff.
+
+
+
+Figure 11-5 – VC-2-Xc structure diagram. The diagram shows a rectangular block representing the VC-2-Xc structure. On the left, a vertical column contains four bytes: V5, J2, N2, and K4, collectively labeled 'Fixed stuff'. To the right of this column is a large area labeled 'C-2-X'. Above the block, a dimension line indicates a total width of 'X × 107'. Below this, another dimension line shows a segment of 'X-1' followed by a segment of 'X × 106'. On the far left, the numbers '1' and '4' are present. On the far right, '500 μs' is indicated. At the bottom center, the label 'VC-2-Xc' is present, and at the bottom right, the text 'G.707-Y.1322\_F11-5' is visible.
+
+Figure 11-5 – VC-2-Xc structure
+
+The VC-2-Xc is located in X contiguous TU-2 in a higher order VC-3. The first column of the VC-2-Xc is always located in the first TU-2. The pointer of this first TU-2 indicates the position of the V5 POH byte of the VC-2-Xc. The pointers of the TU-2 #2 to #X are set to the concatenation indication (see Figure 8-10) to indicate the contiguous concatenated payload. Pointer justification is performed in common for the X concatenated TU-2s and X stuffing bytes are used.
+
+With allowed values of X between 1 and 7, the VC-2-Xc provides a payload capacity between 6784 kbit/s and 47 488 kbit/s in steps of 6784 kbit/s.
+
+## 11.4 Virtual concatenation of X VC-11/VC-12/VC-2
+
+A VC-11-Xv/VC-12-Xv/VC-2-Xv provides the transport capability equivalent to $X \times \text{container-11/container-12/container-2}$ , which can be represented by a C-11-X/C-12-X/C-2-X like structure and has a payload capacity of $X \times 1600/2176/6784$ kbit/s, as depicted in Figures 11-6, 11-7 and 11-8. The container is mapped in X individual VC-11s/VC-12s/VC-2s which form the VC-11-Xv/VC-12-Xv/VC-2-Xv, as illustrated in Appendix XIV. Each VC-11/VC-12/VC-2 has its own POH.
+
+
+
+The diagram illustrates the structure of a VC-2-Xv. At the top, a horizontal bar represents the C-2-X component, with a duration of 500 μs and a size of X × 106 bytes. Below this, the VC-2 #1 component is shown, also with a 500 μs duration. It contains a vertical stack of bytes: V5, J2, N2, and K4. To the right of this stack, a smaller box contains V5, J2, and a series of dots, with a total size of 107 bytes. A bracket on the right groups the VC-2 #1 and VC-2 #X components under the label VC-2-Xv. The VC-2 #X component is shown as a box with a 500 μs duration. Lines connect the start and end of the C-2-X component to the start and end of the VC-2 #1 component. The label G.707-Y.1322\_F11-6 is at the bottom right.
+
+Diagram of VC-2-Xv structure showing C-2-X, VC-2 #1, and VC-2 #X components with timing and byte counts.
+
+Figure 11-6 – VC-2-Xv structure
+
+
+
+The diagram illustrates the structure of a VC-12-Xv. At the top, a horizontal bar represents the C-12-X component, with a duration of 500 μs and a size of X × 34 bytes. Below this, the VC-12 #1 component is shown, also with a 500 μs duration. It contains a vertical stack of bytes: V5, J2, N2, and K4. To the right of this stack, a smaller box contains V5, J2, and a series of dots, with a total size of 35 bytes. A bracket on the right groups the VC-12 #1 and VC-12 #X components under the label VC-12-Xv. The VC-12 #X component is shown as a box with a 500 μs duration. Lines connect the start and end of the C-12-X component to the start and end of the VC-12 #1 component. The label G.707-Y.1322\_F11-7 is at the bottom right.
+
+Diagram of VC-12-Xv structure showing C-12-X, VC-12 #1, and VC-12 #X components with timing and byte counts.
+
+Figure 11-7 – VC-12-Xv structure
+
+
+
+Diagram illustrating the VC-11-Xv structure. At the top, a container labeled 'C-11-X' has a duration of 500 μs and is shown as a sequence of X frames, with X multiplied by 25. Below this, a bracket labeled 'VC-11-Xv' contains multiple individual VC-11 frames. Each VC-11 frame has a duration of 500 μs and contains a payload area. The first VC-11 frame is labeled 'VC-11 #1' and shows its internal structure: a 1-byte V5 byte, a 1-byte J2 byte, a 4-byte N2 byte, and a 4-byte K4 byte. The second VC-11 frame is labeled 'VC-11 #X' and shows a 1-byte V5 byte, a 1-byte J2 byte, and a payload area. Lines connect the X frames in the C-11-X container to the individual VC-11 frames in the VC-11-Xv group. A small diagram shows the mapping of X frames to VC-11 frames, with V5 and J2 bytes being part of the VC-11 structure. The text 'G.707-Y.1322\_F11-8' is at the bottom right.
+
+**Figure 11-8 – VC-11-Xv structure**
+
+Each VC-11/VC-12/VC-2 of the VC-11-Xv/VC-12-Xv/VC-2-Xv is transported individually through the network. Due to the different propagation delays of the VC-11s/VC-12s/VC-2s, a differential delay will occur between the individual VC-11s/VC-12s/VC-2s. At the path termination, this differential delay has to be compensated and the individual VC-11s/VC-12s/VC-2s have to be realigned for access to the contiguous payload area. The realignment process has to cover at least a differential delay of 125 μs.
+
+Payload capacities are shown in Table 11-4 for VC-11-Xv, VC-12-Xv and VC-2-Xv.
+
+**Table 11-4 – Capacity of virtually concatenated VC-11-Xv/VC-12-Xv/VC-2-Xv**
+
+| | X | Capacity | In steps of |
+|----------|----------------|-------------------------------|-------------|
+| VC-11-Xv | 1 to 64 (Note) | 1600 kbit/s to 102 400 kbit/s | 1600 kbit/s |
+| VC-12-Xv | 1 to 64 | 2176 kbit/s to 139 264 kbit/s | 2176 kbit/s |
+| VC-2-Xv | 1 to 64 | 6784 kbit/s to 434 176 kbit/s | 6784 kbit/s |
+
+NOTE – Limited to 64 due to:
+a) six bits for sequence indicator in K4 bit 2 frame; and
+b) inefficient and unlikely to map more than 64 VC-11s in VC-4.
+
+To perform the realignment of the individual VC-ms ( $m = 2/12/11$ ) that belong to a virtually concatenated group, it is necessary to:
+
+- compensate for the differential delay experienced by the individual VC-ms;
+- know the individual sequence numbers of the individual VC-ms.
+
+Bit 2 of the K4 byte of the lower order VC-m POH is used to convey this information from the sending end to the receiving end of the virtually concatenated signal where the realignment process is performed. A serial string of 32 bits (over 32 four-frame multiframes) is arranged as in Figure 11-9. This string is repeated every 16 ms ( $32 \text{ bits} \times 500 \mu\text{s/bit}$ ) or every 128 frames.
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-------------|---|---|---|---|--------------------|---|---|---|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|---|---|
+| Bit number | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | | |
+| Frame count | | | | | Sequence indicator | | | | | | R | R | R | R | R | R | R | R | R | R | R | R | R | R | R | R | R | R | R | R | R | R | R |
+
+R Reserved bit
+
+**Figure 11-9 – K4 bit 2 multiframe**
+
+The LO virtual concatenation information in K4 bit 2 has a 32-bit multiframe depicted in Figure 11-9. The phase of the LO virtual concatenation information in K4 bit 2 should be the same as for the K4 bit 1 extended signal label described in clause 9.3.2.4.
+
+NOTE – Virtually concatenated VC-11/VC-12/VC-2 must use the extended signal label. Otherwise the frame phase of the K4 bit 2 multiframe cannot be established.
+
+The frame consists of the following fields:
+
+The LO virtual concatenation frame count is contained in bits 1 to 5. The LO virtual concatenation sequence indicator is contained in bits 6 to 11. The remaining 21 bits are reserved for future standardization, should be set to all "0"s and should be ignored by the receiver.
+
+The LO virtual concatenation frame count provides a measure of the differential delay up to 512 ms in 32 steps of 16 ms that is the length of the multiframe ( $32 \times 16 \text{ ms} = 512 \text{ ms}$ ).
+
+The LO virtual concatenation sequence indicator identifies the sequence/order in which the individual VC-11s/VC-12s/VC-2s of the VC-11-Xv/VC-12-Xv/VC-2-Xv are combined to form the contiguous payload C-11-X/C-12-X/C-2-X as shown in Figures 11-6 to 11-8. Each VC-11/VC-12/VC-2 of a VC-11-Xv/VC-12-Xv/VC-2-Xv has a fixed unique sequence number in the range of 0 to (X-1).
+
+The VC-11 transporting the:
+
+- data from cols 1, X+1, 2X+1, ...25X+1 of the C-11-X like structure has the sequence number 0;
+- data from cols 2, X+2, 2X+2, ... 25X+2 of the C-11-X like structure has the sequence number 1;
+
+and so on up to the VC-11 transporting the:
+
+- data from cols X, X+X, 2X+X, ... 25X+X of the C-11-X like structure has the sequence number (X-1).
+
+The VC-12 transporting the:
+
+- data from cols 1, X+1, 2X+1, ... 34X+1 of the C-12-X like structure has the sequence number 0;
+- data from cols 2, X+2, 2X+2, ... 34X+2 of the C-12-X like structure has the sequence number 1;
+
+and so on up to the VC-12 transporting the:
+
+- data from cols X, X+X, 2X+X, ... 34X+X of the C-12-X like structure has the sequence number (X-1).
+
+The VC-2 transporting the:
+
+- data from cols 1, X+1, 2X+1, ... 106X+1 of the C-2-X like structure has the sequence number 0;
+- data from cols 2, X+2, 2X+2, ... 106X+2 of the C-2-X like structure has the sequence number 1;
+
+and so on up to the VC-2 transporting the:
+
+- data from cols X, X+X, 2X+X, ... 106X+X of the C-2-X like structure has the sequence number (X-1).
+
+For applications requiring fixed bandwidth, the sequence number is fixed assigned and not configurable. This allows the constitution of the VC-11-Xv/VC-12-Xv/VC-2-Xv to be checked without using the trace.
+
+### 11.4.1 Lower order LCAS, VC-m-Xv (m = 11, 12, 2)
+
+Figure 11-10 depicts the modified K4[2] LO virtual concatenation multiframe, as defined in clause 11.4, indicating the control codes used for the support of LO LCAS. See also ITU-T Rec. G.7042/Y.1305.
+
+- Frame count: The multiframe counter [0-31].
+- Sequence indicator: Number to identify each member in the VCG [0-63].
+- CTRL: LCAS control field, see Table 1/G.7042/Y.1305.
+- GID: Group identification bit.
+- Member status: The status report of the individual members uses the MST-multiframe as shown in Table 11-5. The status of all members (64) is transferred in 128 ms.
+- RS-Ack: Re-Sequence Acknowledge bit.
+- CRC: Three-bit CRC check for fast acceptance of virtual concatenation overhead. With this CRC-3 the probability of an undetected error in a signal with an average BER of $5.32 \times 10^{-9}$ , is $4 \times 10^{-30}$ . The CRC generator polynomial is $x^3 + x + 1$ .
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-----------------|---|---|---|---|--------------------|---|---|---|----|------|----|----|----|----|-----|-----------------|----|----|----|----|--------|---------------|----|----|----|----|----|----|-------|----|----|
+| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 |
+| Frame indicator | | | | | Sequence indicator | | | | | CTRL | | | | | GID | Reserved "0000" | | | | | RS-Ack | Member status | | | | | | | C1 | C1 | C3 |
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | CRC-3 | | |
+
+Figure 11-10 – K4[2] VC-m-Xv supporting LCAS coding
+
+**Table 11-5 – LO LCAS VC-m-Xv frame-to-member number relation**
+
+| Frame number | Member number | | | | | | | | |
+|---------------|---------------|----|----|----|----|----|----|----|----------------|
+| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | |
+| 0, 8, 16, 24 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | MST-multiframe |
+| 1, 9, 17, 25 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | |
+| 2, 10, 18, 26 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | |
+| 3, 11, 19, 27 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | |
+| 4, 12, 20, 28 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | |
+| 5, 13, 21, 29 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | |
+| 6, 14, 22, 30 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | |
+| 7, 15, 23, 31 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | |
+
+NOTE – There are eight member statuses reported per VC-m-Xv frame. The 64 members require eight frames at a frame rate of 16 ms each. This thus results in the member status being refreshed every 128 ms if there is only one return channel.
+
+#### 11.4.1.1 Lower order control packet
+
+The lower order control packet consists of:
+
+- Multiframe indicator (MFI) (five bits: 1 to 5);
+- Sequence indicator (SQ) field (six bits: 6 to 11);
+- CTRL (control) field (four bits: 12 to 15);
+- GID (group identification) bit (one bit: 16);
+- RS-Ack (re-sequence acknowledge) bit (one bit: 21);
+- Member status (MST) field (eight bits: 22 to 29);
+- CRC-3 field (three bits: 30 to 32), $C_1C_2C_3$ , is the remainder of the CRC-3 calculation over the K4[2] bits 1...32. To calculate the CRC, we regard control packet bits 1-29 as a polynomial $M(x)$ where K4[2] of frame 1 is the most significant bit and K4[2] of frame 29 is the least significant bit of $M(x)$ . $M(x)$ is first multiplied by $x^3$ and then divided (modulo 2) by generator polynomial $G(x) = x^3 + x + 1$ to produce a remainder $R(x)$ of degree 2 or less. $R(x)$ is the CRC-3 code with $x^2$ of $R(x)$ corresponding to $C_1$ as the most significant bit of the remainder and $x^0$ of $R(x)$ corresponding to $C_3$ as the least significant bit of the remainder;
+- All other bits (#17, #18, #19 and #20) are reserved and should be set to '0'.
+
+The lower order control packet starts and stops at the same frames as the original multiframe (see Figure 11-10).
+
+# Annex A
+
+# Forward error correction for STM-64, and STM-256
+
+(This annex forms an integral part of this Recommendation)
+
+## A.1 Network reference model
+
+The network reference model for in-band FEC has the following characteristics:
+
+- Conceptually, the FEC falls below the MS layer and provides a "correction service" to the MS layer. Correction at intermediate regenerators is possible.
+- FEC covers and provides correction for the AUG-N area, all MSOH bytes and the FSI byte located in the RSOH.
+- The FEC uses overhead bytes from the MSOH and RSOH. Regenerators have to pass through the FEC-related RSOH bytes.
+- The FEC insertion function shall compensate B2 appropriately to reflect the changes in the FEC MSOH bytes. The FEC parity covers the compensated B2 bytes.
+- The MS layer signal degrade and other performance monitoring functions based on B2 apply to the corrected data; they are thus appropriate for service-related performance measurements (e.g., as used for protection switching), but give no information about the raw performance of the line.
+- FEC performance monitoring functions can provide information about the condition of the raw performance of the multiplex section. Use of in-band FEC performance monitoring is for further study.
+
+## A.2 The FEC function
+
+### A.2.1 Code type and parameters
+
+The code is a shortened, systematic binary-BCH code derived from a (8191, 8152) parent code. Sufficient parity bits are generated to support triple error correction.
+
+The block size is 1 row (bit-slice) of the STM-N (see Figure A.1) ordered in $8 \times N/16$ rows, i.e., $k = 4320$ information bits plus 39 parity bits per block, i.e., $n = 4359$ . The minimum code distance = 7, i.e., number of correctable errors, $t = 3$ .
+
+### A.2.2 FEC encoder description and algorithm
+
+The generator polynomial used is $G(x) = G1(x) \times G3(x) \times G5(x)$ where:
+
+$$G1(x) = x^{13} + x^4 + x^3 + x + 1$$
+
+$$G3(x) = x^{13} + x^{10} + x^9 + x^7 + x^5 + x^4 + 1$$
+
+$$G5(x) = x^{13} + x^{11} + x^8 + x^7 + x^4 + x + 1$$
+
+FEC encoding operates on a row-by-row basis. The code word is represented by the polynomial
+
+$$C(x) = I(x) + R(x)$$
+
+where:
+
+$$I(x) = a_{4358}x^{4358} + \dots + a_{39}x^{39} \text{ where } a_n \text{ (n = 4358 to 39) represents the information bits}$$
+
+and
+
+$$R(x) = a_{38}x^{38} + \dots + a_0 \text{ where } a_n \text{ (n = 38 to 0) represents the parity bits}$$
+
+The first bit of the overhead in each code block is the first bit of the code word and is the coefficient $a_{4358}$ of $x^{4358}$ . The information bits not covered (see clause A.2.5) in the FEC calculations are replaced with zeros in the FEC encoder and decoder.
+
+Since this is a systematic code, the parity bits $R(x)$ are provided by:
+
+$$R(x) = I(x) \bmod G(x)$$
+
+### A.2.3 Encoder and decoder locations
+
+The encoder is always located at the transmitter side of the equipment that terminates MSOH.
+
+There is always a decoder at the input of an in-band FEC-compliant equipment that terminates MSOH. Optionally, a regenerator equipment can decode (correct), but shall not re-encode.
+
+### A.2.4 FEC delay characteristic
+
+The decode delay is no more than 15 $\mu\text{s}$ wherever encountered. Equipment compliant with this standard shall have a FEC processing delay of no more than 15 $\mu\text{s}$ . In the case of in-band FEC being supported each correcting regenerator equipment adds no more than 15 $\mu\text{s}$ delay.
+
+### A.2.5 SDH and FEC check bits not included in FEC coding
+
+The bits and bytes that are not included in the coding of the FEC are:
+
+- All RSOH bytes including undefined RSOH bytes but not the Q1 bytes.
+- All FEC parity bits.
+
+NOTE – Although parity bits $R(x)$ of each code-word are transported in information bits $I(x)$ positions they are not included in $I(x)$ ; they form the $R(x)$ part of the code-word $C(x)$ . As such the $R(x)$ can be corrected. Intermediate regenerators correcting $I(x)$ errors must correct errors within the parity $R(x)$ . At MS terminating points, correction of errors within the parity bits $R(x)$ is not necessary.
+
+## A.3 Mapping into the SDH frame
+
+To minimize delay relative to maintaining RSOH/MSOH layer integrity, MSOH and RSOH for FEC parity bits are used to limit delay to 30 $\mu\text{s}$ per encoder/decoder.
+
+Figures 9-5, 9-6 and 9-7 give the allocation of P1 and Q1 parity and status bytes for STM-N, ( $N = 64, 256$ ), signals.
+
+### A.3.1 Location of the information bits
+
+Each of the 9 rows of an STM-N ( $N = 64, 256$ ) is considered equal and independent. There is no difference between the SOH and AUG-N regarding the information bits $I(x)$ .
+
+One row $K$ of the STM-N frame is shown in Figure A.1. The transmission order is column by column. The row is divided such that every $8 \times N/16$ bit forms one bit-slice. The FEC information bits $a_n$ ( $n = 4358 \dots 39$ ) are located in the positions shown in the figure. Each subrow forms one information word $I(x)$ of the FEC function.
+
+
+
+The diagram illustrates a row of an STM-N frame, which is 270 × 16 bits wide. The row is divided into subrows, each 8 × N/16 bits high. The first subrow at the top and the last subrow at the bottom are shown in detail. In each of these subrows, the first three bits are labeled $a_{4358}$ , $a_{4357}$ , and $a_{4356}$ from left to right. The last two bits in each subrow are labeled $a_{40}$ and $a_{39}$ from left to right. The middle subrows are represented by a dashed box labeled "Row of STM-N frame". A vertical double-headed arrow on the left indicates the height of one subrow as $8 \times N/16$ bits. A horizontal double-headed arrow at the top indicates the total width of the row as $270 \times 16$ bits. The diagram is labeled G.707-Y.1322\_FA.1 in the bottom right corner.
+
+Diagram of an STM-N frame row showing FEC information bit locations. The row is divided into subrows of 8 x N/16 bits. The first subrow shows bits a\_4358, a\_4357, a\_4356 at the start and a\_40, a\_39 at the end. The last subrow shows the same bits. The middle subrows are labeled 'Row of STM-N frame'. The total width is 270 x 16 bits.
+
+Figure A.1 – FEC information bits in row K of STM-N frame
+
+NOTE – Some of the FEC information bits $a_n$ are set to zero for the calculation of the parity $R(x)$ , see clause A.2.5.
+
+The 8-way bit interleaving in conjunction with BCH-3 provides 24-bit burst error correction capability per row for STM-64 and STM-256.
+
+### A.3.2 Location of in-band FEC parity
+
+The P1 bytes are allocated for FEC parity. There is one parity bits set $a_n$ , ( $n = 0 \dots 38$ ), for every subrow in Figure A.1 of an STM-N, i.e., $8 \times N/16$ sets. The FEC parity bit $a_n$ , ( $n = 0 \dots 38$ ), for row K is located in SOH byte:
+
+$$S(x, y, M \times 16 - n + 13 \times \text{Int}[n/13]);$$
+
+where $x, y$ for STM-N row K and parity bit $n$ is obtained from Table A.1, and
+
+$$M = 1, 2, 3, 4 \quad \text{for STM-64}$$
+
+$$M = 1, 2, \dots, 16 \quad \text{for STM-256}$$
+
+**Table A.1 – $x, y$ values for location of FEC parity $a_n$ for row K**
+
+| Row K | $(x, y)$ for $a_n$ $26 \leq n \leq 38$ | $(x, y)$ for $a_n$ $13 \leq n \leq 25$ | $(x, y)$ for $a_n$ $n \leq 12$ |
+|-------|-------------------------------------------|-------------------------------------------|-----------------------------------|
+| 1 | 2,1 | 2,4 | 2,6 |
+| 2 | 3,1 | 3,4 | 3,6 |
+| 3 | 3,7 | 3,8 | 3,9 |
+| 4 | 5,4 | 5,5 | 5,6 |
+| 5 | 5,7 | 5,8 | 5,9 |
+| 6 | 6,7 | 6,8 | 6,9 |
+| 7 | 7,7 | 7,8 | 7,9 |
+| 8 | 8,7 | 8,8 | 8,9 |
+| 9 | 9,1 | 9,2 | 9,3 |
+
+NOTE – The FEC parity $R(x)$ is not necessarily located in the same row as its information bits.
+
+### A.3.3 Location of status/control bits
+
+The FEC FSI carrying byte is located in the first Q1 byte S (3,9,3).
+
+FSI is a FEC status indicator. This is used at the FEC decoding point to determine whether FEC information is present to allow error correction to take place. The location of the FSI bits within the FSI byte is given in Figure A.2.
+
+
+
+| | | | | | | | |
+|----------|---|---|---|---|---|-----|---|
+| Reserved | | | | | | FSI | |
+| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
+
+**Figure A.2 – Q1 byte S (3,9,3)**
+
+### A.3.4 FEC status indication (FSI)
+
+The FEC encoder is required to generate the FEC status indication (FSI) bits to enable downstream decoders. This is to prevent downstream decoders from causing errors by mis-correction when FEC encoding is not present.
+
+The FSI bits are bits 7 and 8 of the FSI byte, see Figure A.2. The remaining bits in the FSI bytes are reserved, but are covered by the FEC. The transmitted default value for these remaining 6 bits shall be zero. The FSI bits (7 and 8) are checked prior to FEC decoding, but the entire FSI byte is included in the FEC block for correction before retransmission by correcting regenerators. The FSI bit coding is defined in clause A.6.2.
+
+### **A.3.5 B1 calculation at encoder and decoder**
+
+B1 is calculated according to clause 9.2.2.4. The FEC check bytes and FSI byte in the SOH are included in the B1 calculation.
+
+The B1 bit errors are calculated before the FEC based on the uncorrected signal. B1 calculation gives error performance of each regenerator section before error correction.
+
+### **A.3.6 B2 calculation at encoder and decoder**
+
+B2 is calculated according to clause 9.2.2.10. The FEC code bytes and FSI byte in the RSOH are not included in the B2 calculation. The FEC parity bytes in the MSOH are included in the B2 calculation. In other words, the B2 has to be compensated to include the FEC parity bytes accordingly in order to show the correct B2 parity.
+
+NOTE – The FEC coding is performed over the compensated B2 parity.
+
+The B2 bit errors are calculated after the FEC decoding based on the corrected signal and B2 bytes.
+
+## **A.4 In-band FEC regenerator functions**
+
+### **A.4.1 Regenerators not supporting in-band FEC**
+
+Regenerator equipment developed prior to the adoption of FEC in this revision of this Recommendation may not transparently pass through the P1 and Q1 bytes. If this information is blocked through older regenerator equipment, downstream equipment will not attempt correction as a result of not receiving the expected FSI byte value.
+
+### **A.4.2 Regenerators passing in-band FEC transparently without error correction**
+
+Regenerator equipment that permits in-band FEC but does not perform error correction shall pass through P1 and Q1 bytes unaltered.
+
+### **A.4.3 Regenerators with error correction**
+
+Optionally, regenerator equipment can perform FEC decoding and correction without re-encoding. The corrected FEC parity bits plus FSI byte are forwarded.
+
+## **A.5 Performance monitoring**
+
+### **A.5.1 FEC correctable error count**
+
+Correctable errors are those that are detected and corrected.
+
+Raw MS layer BER can be calculated with the aid of FEC correction counts. If error correction is performed, then the FEC correctable error count reflects the raw BER from the last decoding point.
+
+### **A.5.2 FEC uncorrectable error count**
+
+Uncorrectable errors are those that are detected but not corrected. The use of this is for further study.
+
+### **A.5.3 Error count after FEC decoding**
+
+B2 is used to calculate the error count after the FEC decoding at an MS termination point or non-intrusive monitor.
+
+## **A.6 FEC activation and deactivation**
+
+### **A.6.1 FEC operational states**
+
+#### **A.6.1.1 Encoder states**
+
+There are three operational states:
+
+- a) FEC on;
+- b) FEC off with encoder delay;
+- c) FEC off without encoder delay.
+
+The management layer controls the encoder operational state. Transitions to/from state c affect data path delay and will not be hitless.
+
+#### **A.6.1.2 Decoder states**
+
+There are three operational states:
+
+- a) FEC correction enabled;
+- b) FEC correction off with decoder delay;
+- c) FEC correction off without decoder delay.
+
+The state transitions to/from state c is solely under management layer control and affects data path delay. Therefore, this transition is not hitless. State transitions between state a and state b are controlled by the received FSI.
+
+### **A.6.2 FEC status indication (FSI)**
+
+#### **A.6.2.1 FSI interaction with decoder states**
+
+Decoder state a can only be entered with received FSI "on" condition. If operating in decoder state a and FSI "off" is received then the decoder shall enter state b. The transitions between state a and state b shall occur in a hitless manner.
+
+#### **A.6.2.2 FEC on/off state indication generation at transmitter**
+
+When the encoder is in state a, FSI = 01 is transmitted. When the encoder is in state b or in state c, FSI = 00. FSI = 10 and 11 are not valid encoder transmission values.
+
+In order to permit synchronized decoder switching at the receiver, the FSI is changed from 01 to 00 or (00 to 01) seven frames before the encoder is switched off (on). The encoder is turned off (on) starting with the first row of the 8th frame after the FSI change.
+
+#### **A.6.2.3 FEC on/off state detection at receiver**
+
+FSI On→Off transition is detected upon receipt of the 3rd consecutive non-01. FSI Off→On transition is detected upon receipt of the 9th consecutive "on" value of 01. This allows the decoder to implement an automatic on/off switch while building in robustness against erroneously performing decoding (and corrupting bits) when the encoder is off.
+
+### **A.6.3 MS-AIS interaction with FEC**
+
+An MS layer termination point is required to monitor for MSF-AIS prior to FEC corrections. If MSF-AIS is detected, FEC corrections should be disabled no later than the beginning of the following frame after MSF-AIS detection.
+
+A regenerator that performs corrections is required to monitor for MSF-AIS prior to corrections. If MSF-AIS is detected, FEC corrections should be disabled no later than the beginning of the following frame after MSF-AIS detection.
+
+Once the MSF-AIS defect is cleared, the FEC corrections should resume no later than the following frame after the clearing of MSF-AIS, assuming that the FSI is in the correction state.
+
+Regenerator section defects that corrupt FEC parity bits (e.g., LOS and LOF) shall disable FEC corrections. Regenerator section defects that do not corrupt FEC parity bits (e.g., J0 mismatch) shall not disable FEC corrections.
+
+## **A.7 Performance of in-band FEC**
+
+The performance of the in-band FEC is discussed in Appendix X.
+
+# Annex B
+
+## CRC-7 polynomial algorithm
+
+(This annex forms an integral part of this Recommendation)
+
+## B.1 Multiplication/division process
+
+A particular CRC-7 word is the remainder after multiplication by $X^7$ and then division (modulo 2) by the generator polynomial $X^7 + X^3 + 1$ , of the polynomial representation of the previous trail trace identifier multiframe (TTI).
+
+When representing the contents of the block as a polynomial, the first bit in the block, i.e., byte 1 bit 1 should be taken as being the most significant bit. Similarly, $C_1$ is defined to be the most significant bit of the remainder and $C_7$ the least significant bit of the remainder.
+
+## B.2 Encoding procedure
+
+Contrary to example CRC-4 procedure in 2 Mbit/s signals, the CRC-7 word is static because the data is static (the TTI represents the source address). This means that the CRC-7 checksum can be calculated *a priori* over the TTI multiframe. For consistency with existing Recommendations, the CRC-7 checksum is to be calculated over the previous multiframe. In theory, this means that the 16-byte string that is loaded in a device for repetition transmission should have the checksum as the last byte although, in practice, it does not really matter because the TTI is static.
+
+The encoding procedure is as follows:
+
+- i) The CRC-7 bits in the TTI are replaced by binary 0s.
+- ii) The TTI is then acted upon by the multiplication/division process referred to in clause B.1.
+- iii) The remainder resulting from the multiplication/division process is inserted into the CRC-7 location.
+
+The CRC-7 bits generated do not affect the result of the multiplication/division process because, as indicated in i) above, the CRC-7 bit positions are initially set to 0 during the multiplication/division process.
+
+## B.3 Decoding procedure
+
+The decoding procedure is as follows:
+
+- i) A received TTI is acted upon by the multiplication/division process referred to in clause B.1 after having its CRC-7 bits extracted and replaced by 0s.
+- ii) The remainder resulting from the division process is then compared on a bit-by-bit basis with the CRC-7 bits received.
+- iii) If the remainder calculated in the decoder exactly corresponds to the CRC-7 bits received, it is assumed that the checked TTI is error free.
+
+# Annex C
+
+# VC-4-Xc/VC-4/VC-3 tandem connection monitoring protocol: Option 1
+
+(This annex forms an integral part of this Recommendation)
+
+This annex describes the tandem connection overhead layer for SDH. The tandem connection sublayer is an optional sublayer which falls between the multiplex section and path layers defined in this Recommendation. This overhead sublayer deals with the reliable transport of path layer payload and its overhead across a network. The use of tandem connection is application-specific and at the discretion of the carrier. It is expected that the principal applications for tandem connection will be in the inter-office network and that tandem connections will generally not be used in applications such as the subscriber access network.
+
+NOTE – The TC monitoring may have an unexpected dependence to the incoming signal. See Appendix VIII for a description of the problem.
+
+## C.1 Tandem connection overhead – Byte location
+
+The N1 byte in the path overhead in each HOVC of the tandem connection is defined as tandem connection overhead (TCOH). Bits 1-4 of this byte in each HOVC of the tandem connection are used to provide a tandem connection incoming error count (IEC), which is defined below. The remaining four bits in byte N1 of the first VC-n within the tandem connection are used to provide an end-to-end data link.
+
+NOTE – Applications currently under consideration may require some LAPD messages generated before the originating TCTE to be transferred through the tandem connection data link. This is for further study.
+
+Figure C.1 shows the tandem connection overheads for an STM-1 rate tandem connection made up of a bundle of 3 VC-3 HO paths.
+
+
+
+Regenerator
+section
+overhead
+
+Multiplex
+section
+overhead
+
+POH # 1
+
+
+| |
+|------------------|
+| Trace J1 |
+| BIP-8 B3 |
+| Sig label C2 |
+| Path stat G1 |
+| User F2 |
+| Multiframe H4 |
+| Growth F3 |
+| Growth K4 |
+| TCOH N1 |
+
+POH # 2
+
+
+| |
+|------------------|
+| Trace J1 |
+| BIP-8 B3 |
+| Sig label C2 |
+| Path stat G1 |
+| User F2 |
+| Multiframe H4 |
+| Growth F3 |
+| Growth K4 |
+| TCOH N1 |
+
+POH # 3
+
+
+| |
+|------------------|
+| Trace J1 |
+| BIP-8 B3 |
+| Sig label C2 |
+| Path stat G1 |
+| User F2 |
+| Multiframe H4 |
+| Growth F3 |
+| Growth K4 |
+| TCOH N1 |
+
+| | | | | | | | |
+|-----|--|--|--|-----------|--|--|--|
+| IEC | | | | Data link | | | |
+| | | | | | | | |
+
+ Tandem connection overhead (N1)
+
+| | | | | | | | |
+|-----|--|--|--|------------|--|--|--|
+| IEC | | | | Unassigned | | | |
+| | | | | | | | |
+
+ Tandem connection overhead (N1)
+
+| | | | | | | | |
+|-----|--|--|--|------------|--|--|--|
+| IEC | | | | Unassigned | | | |
+| | | | | | | | |
+
+ Tandem connection overhead (N1)
+
+G.707-Y.1322\_FC.1
+
+Figure C.1 – Tandem connection overhead in STM-1 rate (AU-3 based) tandem connection
+
+**Figure C.1 – Tandem connection overhead in STM-1 rate (AU-3 based) tandem connection**
+
+## C.2 Definitions
+
+**C.2.1 tandem connection (TC):** A tandem connection is defined as a group of higher order VC-n which are transported and maintained together through one or more tandem line systems, with the constituent HOVC payload capacities unaltered. Note that, in support of the layered overhead approach used in SDH, the tandem connection sublayer falls between the multiplex section and path overhead layers (i.e., the original regenerator section, multiplex section and path functional overhead layering evolves to regenerator section, multiplex section, tandem connection and path layers).
+
+**C.2.2 tandem connection terminating element (TCTE):** The element which originates/terminates the tandem connection. A multiplex section terminating element (MSTE) or a path terminating element (PTE) may also be a TCTE.
+
+## C.3 Tandem connection bundling
+
+Tandem connection maintenance may be performed on a single higher order VC-n or on a bundle with a capacity of N STM-1s where N is any of the allowed SDH hierarchy levels defined in clause 6.3. The size of bundles supported is application-specific and an equipment issue. The following clause describes how tandem connection bundling is achieved.
+
+### C.3.1 Bundling of VC-3s within an STM-1
+
+The bytes from bundled VC-3s within an STM-1 shall be contiguous at the STM-1 level, but are not contiguous when interleaved to higher levels. The first VC-n of the bundle shall contain the tandem connection data link.
+
+Figure C.2 illustrates this for a tandem connection at the STM-1 rate.
+
+
+
+The shaded boxes represent the bytes which make up the tandem connection.
+
+G.707-Y.1322\_FC.2
+
+Diagram illustrating the bundling of VC-3s within an STM-1 rate tandem connection. On the left, 12 VC-3 inputs are shown, grouped into four sets of three (1-3, 4-6, 7-9, 10-12). Each set is multiplexed (3:1) into a sequence of three bytes (e.g., 3, 2, 1 for the first set). These four sequences are then multiplexed (4:1) into a single sequence of 12 bytes: 12, 9, 6, 3, 11, 8, 5, 2, 10, 7, 4, 1. The byte '3' in the fourth position is shaded, and an arrow points to the byte '1' in the twelfth position, labeling it as the 'TC data link'. A caption below states: 'The shaded boxes represent the bytes which make up the tandem connection.'
+
+**Figure C.2 – Example of an STM-1 rate tandem connection within an STM-N**
+
+### C.3.2 Bundling of VC-3s within an STM-N (N>1)
+
+Bundles of VC-3s within an STM-N (N is any of the allowed SDH hierarchy levels defined in clause 6.3) consist of multiples of STM-1s. The bytes from the constituent STM-1s shall be contiguous. The first HOVC of the tandem connection shall contain the tandem connection data link.
+
+### C.3.3 Tandem connection bundle contents
+
+A tandem connection bundle at the STM-N rate (N is any of the allowed SDH hierarchy levels defined in clause 6.3) may carry $3 \times N$ VC-3s or combinations of VC-4-Mcs ( $M \leq N$ ; $M = 1, 4, 16$ ) including one VC-4-Xc as per the concatenation mechanism defined in clause 8.1.7 (e.g., an STM-4 tandem connection could carry 12 VC-3s, or 4 VC-4s, or one VC-4-4c, or 2 VC-4s and 6 VC-3s, etc.). Note that a VC-4-Mc shall be contained wholly within a single tandem connection.
+
+Figure C.3 illustrates this for an STM-4 rate tandem connection made up of four VC-4s.
+
+
+
+The shaded boxes represent the bytes which make up the tandem connection.
+
+G.707-Y.1322\_FC.3
+
+Diagram illustrating an STM-4 rate tandem connection within an STM-16. On the left, 16 numbered boxes (1-16) represent the constituent STM-1 signals. These are multiplexed via a 16:1 ratio into a horizontal sequence of 16 numbered boxes (16-1) representing the bytes of the STM-16 frame. The last byte, labeled '1', is shaded and has an arrow pointing to it from the text 'TC data link'. A caption below the diagram states: 'The shaded boxes represent the bytes which make up the tandem connection.' A reference code 'G.707-Y.1322\_FC.3' is located in the bottom right corner of the diagram area.
+
+Figure C.3 – Example of an STM-4 rate tandem connection within an STM-16
+
+### C.3.4 Tandem connection bundles in higher rate signals
+
+A bundle of HOVCs forming a tandem connection may be multiplexed into a higher rate STM-N as per the multiplexing procedure defined in this Recommendation.
+
+## C.4 Incoming error count (IEC)
+
+In order to continually assess the tandem connection signal quality, the B3 bytes in the VC-n overhead of each of the HOVCs that make up the tandem connection signal are used to determine
+
+the number of errors which have accumulated in the tandem connection. In order to account for any errors that may be present in a VC-n at the originating end of the tandem connection, the number of errors detected in the incoming VC-n at the originating end of the tandem connection is written into bits 1-4 of byte N1 in the next frame using the coding given in Table C.1. This procedure is carried out for each of the VC-ns that make up the tandem connection.
+
+The tandem connection signal may then be carried through the network by STM-M SDH line system (of equal or higher transport rate), or number of SDH line systems in tandem where the tandem connection is made at the tandem connection, or higher, level (e.g., a VC-3 tandem connection may be cross-connected at the VC-3 rate or higher, and a TCB at the STM-4 rate may be cross-connected at the STM-4 rate or higher). At the terminating TCTE (far end of the tandem connection), the B3 byte in each of the constituent HOVCs is again used to calculate the number of errors which have accumulated. The magnitude (absolute value) of the difference between this calculated number of errors and the number of errors written into the IEC at the originating end is then used to determine the error performance of the tandem connection for each transmitted SDH frame. The IEC field is interpreted according to Table C.2. Note that the B3 byte data and the IEC read in the current frame both apply to the previous frame.
+
+On the outgoing side of the terminating TCTE, the IEC (first four bits of N1 byte) of all constituent HOVCs shall be set to all 0s. As a default, the tandem connection data link (last four bits of N1 in the first HOVC) shall be set to all 0s.
+
+NOTE – Applications currently under consideration may require some messages in the tandem connection data link to be forwarded on beyond the terminating TCTE. This is for further study.
+
+The unassigned bits (last four bits in the remaining Z5 bytes) shall be passed through unaltered. B3 shall then be compensated as defined in clause C.5.
+
+**Table C.1 – IEC coding**
+
+| b1 | b2 | b3 | b4 | Number of BIP-8 violations |
+|----|----|----|----|----------------------------|
+| 1 | 0 | 0 | 1 | 0 |
+| 0 | 0 | 0 | 1 | 1 |
+| 0 | 0 | 1 | 0 | 2 |
+| 0 | 0 | 1 | 1 | 3 |
+| 0 | 1 | 0 | 0 | 4 |
+| 0 | 1 | 0 | 1 | 5 |
+| 0 | 1 | 1 | 0 | 6 |
+| 0 | 1 | 1 | 1 | 7 |
+| 1 | 0 | 0 | 0 | 8 |
+| 1 | 1 | 1 | 0 | Incoming AIS |
+
+NOTE – To guarantee a non-all-zeroes N1 byte independent of the incoming signal status, it is required that the IEC code field contains at least one "1". When zero errors in the BIP-8 of the incoming signal are detected, then an IEC code is inserted with "1"s in it. In this manner it is possible for the tandem connection sink at the tail end of the tandem connection link to use the IEC code field to distinguish between unequipped conditions started within or before the tandem connection.
+
+**Table C.2 – IEC code interpretation**
+
+| b1 | b2 | b3 | b4 | IEC code interpretation |
+|-----------|-----------|-----------|-----------|--------------------------------|
+| 0 | 0 | 0 | 0 | 0 BIP violation |
+| 0 | 0 | 0 | 1 | 1 BIP violation |
+| 0 | 0 | 1 | 0 | 2 BIP violations |
+| 0 | 0 | 1 | 1 | 3 BIP violations |
+| 0 | 1 | 0 | 0 | 4 BIP violations |
+| 0 | 1 | 0 | 1 | 5 BIP violations |
+| 0 | 1 | 1 | 0 | 6 BIP violations |
+| 0 | 1 | 1 | 1 | 7 BIP violations |
+| 1 | 0 | 0 | 0 | 8 BIP violations |
+| 1 | 0 | 0 | 1 | 0 BIP violation |
+| 1 | 0 | 1 | 0 | 0 BIP violation |
+| 1 | 0 | 1 | 1 | 0 BIP violation |
+| 1 | 1 | 0 | 0 | 0 BIP violation |
+| 1 | 1 | 0 | 1 | 0 BIP violation |
+| 1 | 1 | 1 | 0 | 0 BIP violation, Incoming AIS |
+| 1 | 1 | 1 | 1 | 0 BIP violation |
+
+## C.5 B3 compensation
+
+Since the B3 parity check is taken over the VC-n payload and path overhead (including N1), writing into N1 at the originating TCTE will affect the path parity calculation. Unless this is compensated for, a device which monitors path parity within the tandem connection (e.g., a bridging monitor) may incorrectly count errors. The B3 parity byte should always be consistent with the current state of the VC-n. Therefore, whenever N1 is written, B3 shall be modified to compensate for the change in the N1 value. Since the B3 value in a given frame reflects a parity check over the previous frame (including the B3 byte in that frame), the changes made to the B3 byte in the previous frame shall also be considered in the compensation of B3 for the current frame. Therefore, the following equation shall be used for B3 compensation:
+
+$$B3'(t) = B3(t-1) \oplus B3'(t-1) \oplus N1(t-1) \oplus N1'(t-1) \oplus B3(t)$$
+
+where:
+
+- B3 the existing B3 value in the incoming signal
+- B3' the new (compensated) B3 value
+- N1 the existing N1 value in the incoming signal
+- N1' the new value written into the N1 byte (IEC plus data link at the originating TCTE, or all 0s at the terminating TCTE)
+- $\oplus$ exclusive OR operator
+- t the time of the current frame
+- t-1 the time of the previous frame
+
+## C.6 Data link
+
+Bits 5-8 of the N1 byte in the first VC-n of the tandem connection are designated as a 32 kbit/s tandem connection data link. The remaining four bits in byte N1 of the remaining VC-ns are unassigned and must not be altered by the TCTE. The signal format used on the tandem connection data link is comprised of messages that use a subset of the LAPD protocol (unnumbered, unacknowledged frame).
+
+NOTE – If future applications require LAPD messages generated and terminated outside the tandem connection to be transferred through the tandem connection data link, the above statement does not require that these messages also be unnumbered and unacknowledged.
+
+When these LAPD messages are not being transmitted (i.e., the data link is idle), LAPD flags (01111110) shall be continuously transmitted.
+
+Currently, four messages are defined below to support tandem connection maintenance:
+
+- tandem connection trace;
+- tandem connection idle signal ID;
+- tandem connection test signal ID;
+- tandem connection far end one-second performance report message.
+
+In practice, the tandem connection trace, idle signal ID or test signal ID message is transmitted continuously at a minimum rate of once per second. The tandem connection far end one-second performance report message is transmitted continuously at a rate of once per second.
+
+Operation, administration and maintenance of the network may cause messages, other than those defined above, to appear on the tandem connection data link. Network terminal and monitoring equipment should be able to disregard any such undefined messages. Such undefined message use must not interfere with the transmission of the messages defined in this Recommendation. Use of the tandem connection data link for other terminal-to-terminal messages beyond the described set is for future study.
+
+### C.6.1 Format of the LAPD messages
+
+The format of the LAPD messages uses a subset of the full Q.921/LAPD capabilities. The message structure is shown in Figure C.4. This message structure is that of a Q.921/LAPD, unnumbered and unacknowledged frame. The source of the LAPD messages shall generate the FCS and the zero stuffing required for transparency. Zero stuffing by a transmitter prevents the occurrence of the flag pattern (01111110) in the bits between the opening and closing flags of a Q.921/LAPD frame by inserting a zero after any sequence of five consecutive ones. A receiver removes a zero following five consecutive ones.
+
+There is no requirement for the boundaries of the LAPD octets and the N1 byte to coincide. The bits of the LAPD octet shall be transmitted in the order shown in Figure C.4, within the N1 byte. Thus, bits n, n + 1, n + 2 and n + 3 of an arbitrary LAPD octet would be loaded into bits 5, 6, 7 and 8, respectively, of the N1 byte.
+
+
+
+Order of transmission
+
+← 1
+↓ 2
+
+| Octet no. | Octet label | 8 7 6 5 4 3 2 1 | | | | | | | | Octet content | |
+|-----------|----------------------------------|-----------------|------|--|--|--|----|----|----|--------------------------------------------|-----------|
+| | | 1 | Flag | | | | | | | | |
+| 2 | SAPI | | | | | | CR | EA | | 0011110 0 or 10 | |
+| 3 | TEI | | | | | | | | EA | | 0000000 1 |
+| 4 | Control | | | | | | | | | 00000011 | |
+| 5 to 80 | 76 octet information field | | | | | | | | | CL/ID · TCT; or · ISID; or · TSID | |
+| 81 82 | FCS | | | | | | | | | | |
+
+G.707-Y.1322\_FC.4
+
+| | |
+|----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|
+| Flag 01111110 | Interpretation Interframe fill octet sequence |
+| SAPI CR EA 00111100 00111110 | Interpretation SAPI=15, CR=0 (DTE), EA=0 SAPI=15, CR=1 (Carrier), EA=0 |
+| TEI EA 00000001 | Interpretation TEI=0, EA=1 |
+| Control 00000011 | Interpretation Unacknowledged information transfer |
+| N octet information field Path ID Idle SIG. ID Test SIG. ID | Interpretation Common language identifier |
+| FCS Variable | Interpretation CRC-16 frame check sequence |
+
+**Figure C.4 – Q.921/LAPD message structure**
+
+### **C.6.2 Tandem connection trace, idle signal and test signal identification messages**
+
+The tandem connection identification messages discussed below shall be transmitted a minimum of once per second and shall use only the SAPI/TEI values shown in Figure C.4. The contents of the 76-octet information field is shown in Figure C.5 and is discussed in this clause.
+
+Tandem connection trace
+
+| Data elements | Binary value | |
+|---------------|-----------------|---------------|
+| TYPE | 0011 1000 | Connection ID |
+| EIC | XXXX XXXX..XXXX | 10 octets |
+| LIC | XXXX XXXX..XXXX | 11 octets |
+| FIC | XXXX XXXX..XXXX | 10 octets |
+| UNIT | XXXX XXXX..XXXX | 6 octets |
+| FI | XXXX XXXX..XXXX | 38 octets |
+
+Idle signal identification
+
+| Data elements | Binary value | |
+|---------------|-----------------|-----------|
+| TYPE | 0011 0100 | Idle ID |
+| EIC | XXXX XXXX..XXXX | 10 octets |
+| LIC | XXXX XXXX..XXXX | 11 octets |
+| FIC | XXXX XXXX..XXXX | 10 octets |
+| UNIT | XXXX XXXX..XXXX | 6 octets |
+| PORT No. | XXXX XXXX..XXXX | 38 octets |
+
+Test signal identification
+
+| Data elements | Binary value | |
+|---------------|-----------------|-----------|
+| TYPE | 0011 0010 | Test ID |
+| EIC | XXXX XXXX..XXXX | 10 octets |
+| LIC | XXXX XXXX..XXXX | 11 octets |
+| FIC | XXXX XXXX..XXXX | 10 octets |
+| UNIT | XXXX XXXX..XXXX | 6 octets |
+| GEN No. | XXXX XXXX..XXXX | 38 octets |
+
+G.707-Y.1322\_FC.5
+
+**Figure C.5 – Tandem connection trace-idle signal and test signal identification messages**
+
+NOTE – Note that the tandem connection trace message length of 76 bytes may be changed to 64 bytes to be consistent with the SDH path trace (J1 Byte), once the content of the J1 byte message (under study) has been standardized.
+
+The tandem connection trace (TCT), idle signal identification (ISID) and test signal identification (TSID) messages all use the same 76-octet structure made up of six data elements. Each data element, except the first, is a fixed length word made up of ASCII characters. The first data element is one byte long and defines the type of identification message being transmitted. The next four data elements identify the type of terminal equipment and the equipment location that sourced the
+
+identification message. Finally, given that terminal equipment may source more than one tandem connection signal, the final data element identifies a specific tandem connection signal.
+
+The first five data elements have the same meaning for all three messages, and will be defined first. The sixth data element is different for each of the messages (see Figure C.5). The data elements are designed to accommodate codes that are widely used in facility networks.
+
+The first five data elements, common to all three identification messages, are defined as follows:
+
+**TYPE** The type code is a one-octet code used to identify a particular type of identification message. Specific values are shown in Figure C.5.
+
+**EIC** The equipment identification code (up to 10 characters) describes a specific piece of equipment.
+
+**LIC** The location identification code (up to 11 characters) describes a specific location.
+
+**FIC** The frame identification code (up to 10 characters) identifies where the equipment is located within a building at a given location.
+
+**UNIT** A code (up to 6 characters) that identifies the equipment location within a bay.
+
+The final data element for the tandem connection trace message is the facility identification code:
+
+**FI** The facility identification code (up to 38 characters) identifies a specific tandem connection.
+
+The final data element for the idle signal identification message is the port number:
+
+**PORT No.** The PORT number is the designation of the equipment port that initiates the idle signal.
+
+The final data element for the test signal identification message is the generator number:
+
+**GEN No.** The number of the test signal generator that initiates the test signal.
+
+The ASCII null character shall be used to indicate the end of the string when the full length of the data element is not needed for a given word. The remaining bit positions of the data element may contain ones, zeros, or any combination of ones and zeros.
+
+In those cases where all the data elements are not needed for a given message, the first octet of the data element shall contain the ASCII null character. The remaining bit-positions of the data element may contain ones, zeros or any combination of ones and zeros.
+
+### **C.6.3 The far-end performance report message**
+
+The tandem connection far end one-second performance report message discussed below shall be transmitted once per second and shall use only the SAPI/TEI values shown in Figure C.6. The phase of the one-second report periods with respect to the occurrence of error events is arbitrary in that the one-second timing does not depend on the time of occurrence of any error event.
+
+The performance report contains performance information for each of the four previous one-second intervals. This is illustrated in Figure C.6, octets 5 through 20, and by an example in Figure C.7. Counts of events shall be accumulated in each contiguous one-second interval. At the end of each one-second interval, a modulo-4 counter shall be incremented, and the appropriate performance bits shall be set in the $t_0$ octets (octets 5 through 8 in Figure C.6). These octets and the octets that carry the performance bits of the preceding three one-second intervals form the performance report message.
+
+
+
+Order of transmission
+← 1
+↓ 2
+
+| | Octet label | | | | | | | | Octet content |
+|---|-------------|-----|-----|-----|-----|-----|-----|----|----------------------|
+| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| 1 | Flag | | | | | | | | 01111110 |
+| 2 | SAPI | | | | | | CR | EA | 00111000 or 00111010 |
+| 3 | TEI | | | | | | | EA | 00000001 |
+| 4 | Control | | | | | | | | 00000011 |
+| 5 | G8 | G7 | G6 | G5 | G4 | G3 | G2 | G1 | $t_0$ |
+| 6 | G16 | G15 | G14 | G13 | G12 | G11 | G10 | G9 | |
+| 7 | ALD | AIS | LOP | IDL | TST | CTI | Nm | NI | |
+| 8 | R | R | R | R | R | R | R | R | |
+| 9 | G8 | G7 | G6 | G5 | G4 | G3 | G2 | G1 | $t_0 - 1$ |
+| | G16 | G15 | G14 | G13 | G12 | G11 | G10 | G9 | |
+| | ALD | AIS | LOP | IDL | TST | CTI | Nm | NI | |
+| | R | R | R | R | R | R | R | R | |
+| | G8 | G7 | G6 | G5 | G4 | G3 | G2 | G1 | $t_0 - 2$ |
+| | G16 | G15 | G14 | G13 | G12 | G11 | G10 | G9 | |
+| | ALD | AIS | LOP | IDL | TST | CTI | Nm | NI | |
+| | R | R | R | R | R | R | R | R | |
+| | G8 | G7 | G6 | G5 | G4 | G3 | G2 | G1 | $t_0 - 3$ |
+| | G16 | G15 | G14 | G13 | G12 | G11 | G10 | G9 | |
+| | ALD | AIS | LOP | IDL | TST | CTI | Nm | NI | |
+| | R | R | R | R | R | R | R | R | |
+| | FCS | | | | | | | | Variable |
+
+G.707-Y.1322\_FC.6
+
+Address
+
+00111000
+00111010
+00000001
+
+Interpretation
+
+SAPI=14, C/R=0 (User) EA=0
+SAPI=14, C/R=1 (Carrier) EA=0
+TEI=0, EA=1
+
+Control
+
+00000011
+
+Interpretation
+
+Unacknowledged information transfer
+
+One-second report
+
+G1-G8
+G9-G16
+ALD = 1
+AIS = 1
+LOP = 1
+IDL = 1
+TST = 1
+CTI = 0
+R = 0
+NmNI = 00, 01, 10, 11
+
+Interpretation
+
+LSB of 2-byte tandem connection error event counter
+MSB of 2-byte tandem connection error event counter
+Tandem connection AIS/LOP defect
+Tandem connection AIS failure condition
+Tandem connection LOP failure condition
+Tandem connection idle signal received
+Tandem connection test signal received
+Error event counts are bit error counts
+Reserved (default value is 0)
+One-second report modulo 4 counter
+
+FCS
+
+Variable
+
+Interpretation
+
+CRC-16 frame check sequence
+
+**Figure C.6 – SDH tandem connection far-end performance report message status**
+
+| | $t = t_0$ | $t = t_0 + 1$ | $t = t_0 + 2$ | $t = t_0 + 3$ |
+|------------------|-----------------|-----------------|-----------------|-----------------|
+| Flag | 01111110 | 01111110 | 01111110 | 01111110 |
+| Address Octet 1 | 00111000 | 00111000 | 00111000 | 00111000 |
+| Address Octet 2 | 00000001 | 00000001 | 00000001 | 00000001 |
+| Control | 00000011 | 00000011 | 00000011 | 00000011 |
+| Message Octet 1 | 11111111 | 00000000 | 00000000 | 00000000 |
+| Message Octet 2 | 00000000 | 00000000 | 00000000 | 00000000 |
+| Message Octet 3 | 00000000 | 10000001 | 10000010 | 00100011 |
+| Message Octet 4 | 00000000 | 00000000 | 00000000 | 00000000 |
+| Message Octet 5 | 11110000 | 11111111 | 00000000 | 00000000 |
+| Message Octet 6 | 00000000 | 00000000 | 00000000 | 00000000 |
+| Message Octet 7 | 00000011 | 00000000 | 10000001 | 10000010 |
+| Message Octet 8 | 00000000 | 00000000 | 00000000 | 00000000 |
+| Message Octet 9 | 00001111 | 11110000 | 11111111 | 00000000 |
+| Message Octet 10 | 00000000 | 00000000 | 00000000 | 00000000 |
+| Message Octet 11 | 00000010 | 00000011 | 00000000 | 10000001 |
+| Message Octet 12 | 00000000 | 00000000 | 00000000 | 00000000 |
+| Message Octet 13 | 00000000 | 00001111 | 11110000 | 11111111 |
+| Message Octet 14 | 00000000 | 00000000 | 00000000 | 00000000 |
+| Message Octet 15 | 00000001 | 00000010 | 00000011 | 00000000 |
+| Message Octet 16 | 00000000 | 00000000 | 00000000 | 00000000 |
+| FCS Octet 1 | xxxxxxx | xxxxxxx | xxxxxxx | xxxxxxx |
+| FCS Octet 2 | xxxxxxx | xxxxxxx | xxxxxxx | xxxxxxx |
+
+#### NOTES
+
+| | | |
+|-----------------|--------------------------------------|--------------------------------------|
+| $t = t_0 - 3$ : | Tandem connection error count = 0; | all other parameters = 0; $N(t) = 1$ |
+| $t = t_0 - 2$ : | Tandem connection error count = 15; | all other parameters = 0; $N(t) = 2$ |
+| $t = t_0 - 1$ : | Tandem connection error count = 240; | all other parameters = 0; $N(t) = 3$ |
+| $t = t_0$ : | Tandem connection error count = 255; | all other parameters = 0; $N(t) = 0$ |
+| $t = t_0 + 1$ : | AIS/LOP defect detected; | all other parameters = 0; $N(t) = 1$ |
+| $t = t_0 + 2$ : | AIS/LOP defect detected; | all other parameters = 0; $N(t) = 2$ |
+| $t = t_0 + 3$ : | LOP failure detected; | all other parameters = 0; $N(t) = 3$ |
+
+**Figure C.7 – Example of an SDH tandem connection far-end performance report message status**
+
+#### C.6.3.1 Elements of the far-end performance report message
+
+Occurrences of performance anomalies, defects, failures and status conditions indicate the overall quality of transmission on a tandem connection. The tandem connection anomalies, defects, failures and status conditions that shall be detected and reported are:
+
+- tandem connection error event;
+- tandem connection AIS/LOP defect;
+- tandem connection AIS failure;
+
+- tandem connection LOP failure;
+- tandem connection idle signal received condition;
+- tandem connection test signal received condition;
+- tandem connection count type indicator (CTI).
+
+These tandem connection events and conditions are defined in the following clauses.
+
+#### **C.6.3.2 Tandem connection error event**
+
+A tandem connection error event is detected by comparing the calculated number of errors received at the end of the tandem connection, using the B3 byte, with the incoming error count contained in the tandem connection overhead (i.e., bits 1-4 of the N1 byte), for each of the signals that make up the tandem connection. The IEC field is interpreted according to Table C.2.
+
+#### **C.6.3.3 Tandem connection AIS/LOP defect**
+
+AU-n AIS defect and AU-n LOP defect are defined in ITU-T Rec. G.783. The occurrence of either one of these defects, in at least one of the signals that make up the tandem connection, constitutes a tandem connection AIS/LOP defect.
+
+#### **C.6.3.4 Tandem connection AIS failure**
+
+A tandem connection AIS failure is declared if the AU-n AIS defect is present, in at least one of the signals that make up the tandem connection, for a period T, where T is $2.5 \pm 0.5$ s.
+
+#### **C.6.3.5 Tandem connection LOP failure**
+
+A tandem connection LOP failure is declared if the AU-n LOP defect is present, in at least one of the signals that make up the tandem connection, for a period T, where T is $2.5 \pm 0.5$ s.
+
+#### **C.6.3.6 Tandem connection idle signal received condition**
+
+A tandem connection idle signal received condition occurs when a valid tandem connection idle signal is detected at the end of a tandem connection.
+
+#### **C.6.3.7 Tandem connection test signal received condition**
+
+A tandem connection test signal received condition occurs when a valid tandem connection test signal is detected at the end of a tandem connection.
+
+#### **C.6.3.8 Tandem connection count type indicator**
+
+The tandem connection count type indicator is set to 0 to indicate that the tandem connection IEC contains a count of the number of bit errors (not block errors) which were detected in the previous one-second interval.
+
+### **C.6.4 Special carrier applications**
+
+A carrier may require the use of the tandem connection data link for purposes related to the provisioning or maintenance of the tandem connection or SDH network. Such uses may cause interruptions, delays or reduction of throughput on the tandem connection data link, but shall not impact the timely transmission of the LAPD messages defined above.
+
+The LAPD messages defined above should be constructed and inserted on the data link by the source terminal (TCETE) that constructs the tandem connection signal whether it is a carrier (CR=1) or a DTE (CR=0) terminal. The messages should be delivered without alteration to the TCETE that sinks the information payload of the tandem connection signal.
+
+## C.7 Treatment of incoming signal failures
+
+AU-n (n=3, 4) AIS is specified as all 1s in the entire AU-n, including the AU-n pointer. Since the AU-n pointer is invalid during AIS, the HOVC POH cannot be accessed. Without the following changes, the tandem connection overhead would be lost during signal failures.
+
+When there is a failure on an incoming signal at the origination point of a tandem connection (originating TCTE), the pointers should be re-established within the tandem connection (in order to locate the tandem connection overhead). A new incoming signal failure (ISF) indicator shall be set within the tandem connection to indicate that there was a signal failure before the tandem connection, and AU-n AIS shall be inserted in the appropriate signal(s) at the end of the tandem connection.
+
+The following clauses discuss the treatment of signal failures which occur before and within the tandem connection, respectively.
+
+### C.7.1 Signal failures before the tandem connection
+
+Figure C.8 illustrates tandem connections with incoming signal failures. For transmission from left to right, when there is a signal failure on an incoming AU-n at the originating TCTE, that TCTE will insert a valid pointer value in H1, H2 and H3. With this pointer value, the originating TCTE will locate B3 and the TCOH. An incoming error count of 14 (1110) will be written into the IEC (bits 1-4 of the TCOH) and, for the first HOVC only, the data link will be written into bits 5-8 of the TCOH. All 1s will be written into the remainder of the HOVC, except for B3. B3 shall be calculated in order to provide even parity over the previous frame.
+
+Within the tandem connection, no special treatment is necessary. AU-ns which entered with a signal failure will have valid pointers within the tandem connection (inserted by the originating TCTE). Regenerator section and/or multiplex section terminating equipment within the tandem connection will see valid pointers and will treat the signals as if they were carrying traffic.
+
+At the end of the tandem connection, the terminating TCTE will interpret an IEC value of 14 as an incoming signal failure (ISF) indication. When an ISF indication is received, the terminating TCTE will insert AU-n AIS on the appropriate outgoing signals. For tandem connection error calculations, ISF values of 9 through 13 and 15 will be interpreted as zero incoming errors (IEC=0).
+
+NOTE – IEC values of 9 through 13 and 15 are reserved for future standardization.
+
+
+
+The diagram consists of two parts, top and bottom, illustrating a tandem connection between an Originating TCTE and a Terminating TCTE.
+
+**Top Diagram (Normal State):**
+
+- An arrow labeled "Direction of transmission" points from left to right.
+- On the left, "AIS" is shown entering the "Originating TCTE" (represented by a trapezoid).
+- The "Originating TCTE" is connected to an "LTE" block (represented by a rectangle).
+- The "LTE" block is connected to a "Network" oval.
+- The "Network" oval is connected to another "LTE" block.
+- The second "LTE" block is connected to the "Terminating TCTE" (represented by a trapezoid).
+- A long arrow labeled "ISF (IEC = 1110)" spans from the Originating TCTE to the Terminating TCTE.
+- On the right, "AU-n AIS" is shown exiting the "Terminating TCTE".
+
+**Bottom Diagram (Signal Failure State):**
+
+- An arrow labeled "Direction of transmission" points from left to right.
+- On the left, a signal failure is indicated by an "X" on the input line to the "Originating TCTE".
+- The "Originating TCTE" is connected to an "LTE" block.
+- The "LTE" block is connected to a "Network" oval.
+- The "Network" oval is connected to another "LTE" block.
+- The second "LTE" block is connected to the "Terminating TCTE".
+- A long arrow labeled "ISF (IEC = 1110)" spans from the Originating TCTE to the Terminating TCTE.
+- On the right, "AU-n AIS" is shown exiting the "Terminating TCTE".
+
+G.707-Y.1322\_FC.8
+
+Two diagrams illustrating tandem connections with incoming signal failures. The top diagram shows a normal state where AIS is converted to ISF at the originating TCTE, transmitted through LTE and Network, and then converted back to AU-n AIS at the terminating TCTE. The bottom diagram shows a failure state where a signal failure (indicated by an 'X') occurs before the originating TCTE, resulting in AU-n AIS being transmitted at the terminating TCTE.
+
+**Figure C.8 – Tandem connection with incoming signal failures**
+
+### C.7.2 Signal failures within the tandem connection
+
+Figure C.9 illustrates signal failures within a tandem connection. No special treatment is required for these failures. Regenerator section and/or multiplex section terminating equipment within the tandem connection will respond to signal failures. If AU-n AIS is received at the terminating TCTE, it will indicate a signal failure within the tandem connection.
+
+NOTE – As discussed above, signal failures before the originating TCTE will be converted to ISF by the originating TCTE. Therefore, AU-n AIS at the terminating TCTE indicates a failure inside the tandem connection.
+
+When the terminating TCTE receives a signal failure, it will insert AIS in the appropriate outgoing AU-ns, and will return the appropriate message to the originating TCTE via the tandem connection far-end performance report message.
+
+
+
+The figure consists of two diagrams illustrating signal failures within a tandem connection. Both diagrams show a signal flow from an 'Originating TCTE' on the left to a 'Terminating TCTE' on the right, passing through a 'Network' (represented by an oval) and 'LTE' (represented by rectangles). The 'Direction of transmission' is indicated by an arrow pointing from left to right.
+
+**Top Diagram (Successful Transmission):** The signal flows from the Originating TCTE through the first LTE, then through the Network, then through the second LTE. At the second LTE, an 'AIS' (Alarm Indication Signal) is generated and sent to the Terminating TCTE. The Terminating TCTE then generates an 'AU-n AIS' (Alarm Indication Signal) to the downstream equipment. A 'TC AIS message' is shown being sent from the Terminating TCTE back to the Originating TCTE.
+
+**Bottom Diagram (Signal Failure):** The signal flows from the Originating TCTE through the first LTE, then through the Network, then through the second LTE. At the second LTE, there is a failure (indicated by an 'X'). The Terminating TCTE receives an 'AU-n AIS' from the failed LTE. A 'TC LOP message' (Loss of Pointer message) is shown being sent from the Terminating TCTE back to the Originating TCTE.
+
+G.707-Y.1322\_FC.9
+
+Two diagrams illustrating signal failures within a tandem connection. The top diagram shows a successful transmission path with AIS and TC AIS messages. The bottom diagram shows a failure at the terminating LTE, resulting in AU-n AIS and TC LOP messages.
+
+**Figure C.9 – Signal failures within the tandem connection**
+
+### C.8 Tandem connection idle signal
+
+Tandem connection idle signal is defined as a tandem connection with all constituent signal labels set to "unequipped" (C2=00), and a valid idle signal ID message on the tandem connection data link (per clause C.6).
+
+### C.9 Tandem connection test signal
+
+Tandem connection test signal is defined as any valid tandem connection signal with a valid tandem connection test signal ID.
+
+## Annex D
+
+### VC-4-Xc/VC-4/VC-3 tandem connection monitoring protocol: Option 2
+
+(This annex forms an integral part of this Recommendation)
+
+NOTE – The TC monitoring may have an unexpected dependence to the incoming signal. See Appendix VIII for a description of the problem.
+
+#### D.1 N1 byte structure
+
+N1 is allocated for tandem connection monitoring for contiguously concatenated VC-4, the VC-4 and VC-3 levels. The structure of the N1 byte is given in Table D.1.
+
+- Bits 1-4 are used as an incoming error count (IEC); the coding is given in Table D.2.
+- Bit 5 operates as the TC-REI of the tandem connection to indicate errored blocks caused within the tandem connection.
+- Bit 6 operates as the OEI to indicate errored blocks of the egressing VC-n.
+- Bits 7-8 operate in a 76 multiframe as:
+ - the access point identifier of the tandem connection (TC-API); it complies with the generic 16-byte string format given in clause 9.2.2.2;
+ - the TC-RDI, indicating to the far end that defects have been detected within the tandem connection at the near end tandem connection sink;
+ - the ODI, indicating to the far end that AU/TU-AIS has been inserted into the egressing AU-n/TU-n at the TC-sink due to defects before or within the tandem connection;
+ - reserved capacity (for future standardization).
+
+The structure of the multiframe is given in Tables D.3 and D.4.
+
+**Table D.1 – N1 byte structure**
+
+| b1 | b2 | b3 | b4 | b5 | b6 | b7 | b8 |
+|-----|----|----|----|--------|-----|---------------------------------|----|
+| IEC | | | | TC-REI | OEI | TC-API, TC-RDI ODI, reserved | |
+
+**Table D.2 – IEC coding**
+
+| b1 | b2 | b3 | b4 | Number of BIP-8 violations |
+|----|----|----|----|----------------------------|
+| 1 | 0 | 0 | 1 | 0 |
+| 0 | 0 | 0 | 1 | 1 |
+| 0 | 0 | 1 | 0 | 2 |
+| 0 | 0 | 1 | 1 | 3 |
+| 0 | 1 | 0 | 0 | 4 |
+| 0 | 1 | 0 | 1 | 5 |
+| 0 | 1 | 1 | 0 | 6 |
+| 0 | 1 | 1 | 1 | 7 |
+| 1 | 0 | 0 | 0 | 8 |
+| 1 | 1 | 1 | 0 | Incoming AIS |
+
+**Table D.2 – IEC coding**
+
+NOTE – To guarantee a non all-zeros N1 byte independent of the incoming signal status, it is required that the IEC code field contains at least one "1". When zero errors in the BIP-8 of the incoming signal are detected, then an IEC code is inserted with "1"s in it. In this manner, it is possible for the tandem connection sink at the tail end of the tandem connection link to use the IEC code field to distinguish between unequipped conditions started within or before the tandem connection.
+
+**Table D.3 – b7-b8 multiframe structure**
+
+| Frame # | Bits 7 and 8 definition |
+|---------|-------------------------------------------------------------------------------------------------------------------------------|
+| 1-8 | Frame alignment signal: 1111 1111 1111 1110 |
+| 9-12 | TC-API byte #1 [ 1 C 1 C 2 C 3 C 4 C 5 C 6 C 7 ] |
+| 13-16 | TC-API byte #2 [ 0 X X X X X X X ] |
+| 17-20 | TC-API byte #3 [ 0 X X X X X X X ] |
+| : | : |
+| 65-68 | TC-API byte #15 [ 0 X X X X X X X ] |
+| 69-72 | TC-API byte #16 [ 0 X X X X X X X ] |
+| 73-76 | TC-RDI, ODI and reserved (see Table D.4) |
+
+**Table D.4 – Structure of frames Nos 73-76 of the b7-b8 multiframe**
+
+| TC-RDI, ODI and reserved capacity | | |
+|-----------------------------------|--------------------------|--------------------------|
+| Frame # | b7 definition | b8 definition |
+| 73 | Reserved (default = "0") | TC-RDI |
+| 74 | ODI | Reserved (default = "0") |
+| 75 | Reserved (default = "0") | Reserved (default = "0") |
+| 76 | Reserved (default = "0") | Reserved (default = "0") |
+
+## D.2 TCM functionality at the tandem connection source
+
+- If no valid AU-n/TU-n enters the tandem connection at the TC-source, then a valid pointer is inserted. This results in a VC-AIS signal as described in clause 6.2.4.1.4 being inserted; the IEC is set to "incoming AIS" code (see Table D.2).
+- If a valid AU-n/TU-n enters the tandem connection, then an even BIP-8 is computed for each bit n of every byte of the VC-n in the preceding frame including B3 and compared with byte B3 recovered from the current frames to determine the number of BIP violations arriving at the tandem connection source. This value is coded into bits 1 to 4 as shown in Table D.2.
+ - In both cases, bits 5-8 are assembled and transmitted according to Tables D.1, D.3 and D.4. The bits TC-REI, TC-RDI, OEI, ODI are set to "1" if the corresponding anomaly or defect is detected at the associated TC-sink of the reverse direction.
+ - The BIP-8 is compensated according to the algorithm described in clause D.4.
+
+NOTE – If an unequipped or supervisory unequipped signal enters a tandem connection, then the N1 and B3 bytes are overwritten with values not equal to all zeroes.
+
+### **D.3 TCM functionality at the tandem connection sink**
+
+- If no valid AU-n/TU-n arrives at the TC-sink, the corresponding defect caused within the tandem connection is declared. The TC-RDI and ODI bits are set to 1 in the reverse direction and an AU/TU-AIS is inserted in the egressing AU-n/TU-n.
+- If a valid AU-n/TU-n is present at the TC-sink the N1 byte is monitored:
+ - An "all-zeroes" N1-byte indicates a disconnection or misconnection within the tandem connection. In this case, the TC-RDI and ODI bits are set to 1 in the reverse direction and an AU/TU-AIS is inserted in the egressing AU-n/TU-n.
+ - The multiframe in bits 7 and 8 is recovered and the contents are interpreted. If the multiframe cannot be found, the TC-RDI and ODI bits are set to 1 in the reverse direction and AU/TU-AIS is inserted in the egressing AU-n/TU-n.
+ - The TC-API is recovered and compared with the expected TC-API. In the case of a mismatch, the TC-RDI and ODI bits are set to 1 in the reverse direction and AU/TU-AIS is inserted in the egressing AU-n/TU-n.
+ - The IEC field is interpreted according to Table D.5.
+
+An "incoming AIS" code indicates that a defect has already occurred before the tandem connection. In this case, only the ODI-bit is set to 1 in the reverse direction and AU/TU-AIS is inserted in the egressing AU-n/TU-n.
+
+The even BIP-8 parity is computed for each bit n of every byte of the VC-n in the preceding frame, including B3, and compared with byte B3 recovered from the current frames to determine the number of BIP violations. The OEI bit is set to 1 in the reverse direction if the number of determined BIP-violations is greater than zero. Furthermore, this value is compared with the number of BIP violations retrieved from IEC of the current frame. If the difference is not equal to zero, an errored block caused within the tandem connection is declared and a TC-REI bit is signalled in the reverse direction.
+
+If TU-n/AU-AIS is not inserted by the tandem connection sink, the N1 byte is set to all zeros and the BIP is compensated according to the algorithm described in clause D.4.
+
+**Table D.5 – IEC code interpretation**
+
+| b1 | b2 | b3 | b4 | IEC code interpretation |
+|-----------|-----------|-----------|-----------|--------------------------------|
+| 0 | 0 | 0 | 0 | 0 BIP violation |
+| 0 | 0 | 0 | 1 | 1 BIP violation |
+| 0 | 0 | 1 | 0 | 2 BIP violations |
+| 0 | 0 | 1 | 1 | 3 BIP violations |
+| 0 | 1 | 0 | 0 | 4 BIP violations |
+| 0 | 1 | 0 | 1 | 5 BIP violations |
+| 0 | 1 | 1 | 0 | 6 BIP violations |
+| 0 | 1 | 1 | 1 | 7 BIP violations |
+| 1 | 0 | 0 | 0 | 8 BIP violations |
+| 1 | 0 | 0 | 1 | 0 BIP violation |
+| 1 | 0 | 1 | 0 | 0 BIP violation |
+| 1 | 0 | 1 | 1 | 0 BIP violation |
+| 1 | 1 | 0 | 0 | 0 BIP violation |
+| 1 | 1 | 0 | 1 | 0 BIP violation |
+| 1 | 1 | 1 | 0 | 0 BIP violation, incoming AIS |
+| 1 | 1 | 1 | 1 | 0 BIP violation |
+
+#### D.4 BIP-8 compensation
+
+Since the BIP-8 parity check is taken over the VC-n (including N1), writing into N1 at the TC-source or TC-sink will affect the VC-4-Xc/VC-4/VC-3 path parity calculation. Because the BIP-8 parity should always be consistent with the current state of the VC-n, the BIP has to be compensated each time N1 byte is modified. Since the BIP-8 value in a given frame reflects the parity check over the previous frame, the changes made to BIP-8 bits in the previous frame shall also be considered in the compensation of BIP-8 in the current frame. Therefore, the following equation shall be used for compensation of the individual bits of the BIP-8:
+
+$$B3[i]'(t) = B3[i](t-1) \oplus B3[i]'(t-1) \oplus N1[i](t-1) \oplus N1[i]'(t-1) \oplus B3[i](t)$$
+
+where:
+
+B3[i] the existing B3[i] value in the incoming signal
+
+B3[i]' the new (compensated) B3[i] value
+
+N1[i] the existing N1[i] value in the incoming signal
+
+N1[i]' the new value written into the N1[i] bit
+
+$\oplus$ exclusive OR operator
+
+t the time of the current frame
+
+t-1 the time of the previous frame
+
+## Annex E
+
+### VC-2, VC-12 and VC-11 tandem connection monitoring protocol
+
+(This annex forms an integral part of this Recommendation)
+
+#### E.1 N2 byte structure
+
+N2 is allocated for tandem connection monitoring for the VC-2, VC-12 and VC-11 levels. The structure of the N2 byte is given in Table E.1.
+
+- Bits 1-2 are used as an even BIP-2 for the tandem connection.
+- Bit 3 is fixed to "1". This guarantees that the contents of N2 is not all zeros at the TC-source. This enables the detection of an unequipped or supervisory-unequipped signal at the tandem connection sink without the need of monitoring further OH-bytes.
+- Bit 4 operates as an "incoming AIS" indicator.
+- Bit 5 operates as the TC-REI of the tandem connection to indicate errored blocks caused within the tandem connection.
+- Bit 6 operates as the OEI to indicate errored blocks of the egressing VC-n.
+- Bits 7-8 operate in a 76 multiframe as:
+ - the access point identifier of the tandem connection (TC-API); it complies with the generic 16-byte string format given in clause 9.2.2.2;
+ - the TC-RDI, indicating to the far end that defects have been detected within the tandem connection at the near end tandem connection sink;
+ - the ODI, indicating to the far end that TU-AIS has been inserted at the TC-sink into the egressing TU-n due to defects before or within the tandem connection;
+ - reserved capacity (for future standardization).
+
+The structure of the multiframe is given in Tables E.2 and E.3.
+
+**Table E.1 – N2 byte structure**
+
+| b1 | b2 | b3 | b4 | b5 | b6 | b7 | b8 |
+|-------|----|-----|--------------|--------|-----|---------------------------------|----|
+| BIP-2 | | "1" | Incoming AIS | TC-REI | OEI | TC-API, TC-RDI ODI, reserved | |
+
+**Table E.2 – b7-b8 multiframe structure**
+
+| Frame # | b7-b8 definition |
+|---------|-------------------------------------------------------------------------------------------------------------------------------|
+| 1-8 | Frame alignment signal: 1111 1111 1111 1110 |
+| 9-12 | TC-API byte #1 [ 1 C 1 C 2 C 3 C 4 C 5 C 6 C 7 ] |
+| 13-16 | TC-API byte #2 [ 0 X X X X X X X ] |
+| 17-20 | TC-API byte #3 [ 0 X X X X X X X ] |
+| : | : |
+| 65-68 | TC-API byte #15 [ 0 X X X X X X X ] |
+| 69-72 | TC-API byte #16 [ 0 X X X X X X X ] |
+| 73-76 | TC-RDI, ODI and reserved (See Table E.3) |
+
+**Table E.3 – Structure of frames Nos 73-76 of the b7-b8 multiframe**
+
+| TC-RDI, ODI and reserved capacity | | |
+|------------------------------------------|--------------------------|--------------------------|
+| Frame # | b7 definition | b8 definition |
+| 73 | Reserved (default = "0") | TC-RDI |
+| 74 | ODI | Reserved (default = "0") |
+| 75 | Reserved (default = "0") | Reserved (default = "0") |
+| 76 | Reserved (default = "0") | Reserved (default = "0") |
+
+## **E.2 TCM functionality at the tandem connection source**
+
+- If no valid TU-n is entering the tandem connection at the TC-source, a valid pointer is inserted. This results in a VC-AIS signal as described in clause 6.2.4.1.4 being inserted and bit 4 is set to "1". Even BIP-2 parity is calculated over the inserted VC-AIS signal and written into bits 1-2 of N2.
+- If a valid TU-n is entering the tandem connection at the tandem connection source, then even BIP-2 parity is calculated over the incoming valid VC-n or the inserted VC-AIS signal and written into bits 1-2 of N2.
+ - In both cases, bits 3-8 are assembled and transmitted according to Tables E.1, E.2 and E.3.
+The bits TC-REI, TC-RDI, OEI, ODI are set to "1" if the corresponding anomaly or defect is detected at the associated TC-sink of the reverse direction.
+ - The original BIP-2 is compensated according to the algorithm described in clause E.4.
+
+NOTE – In an unequipped or supervisory-unequipped signal entering a tandem connection, the N2 and V5 bytes are overwritten with values not equal to all zeros.
+
+## **E.3 TCM functionality at the tandem connection sink**
+
+If no valid TU-n arrives at the TC-sink, the corresponding defect caused within the tandem connection is declared and the TC-RDI and ODI conditions apply. A TU-AIS is inserted in the outgoing TU-n.
+
+If a valid TU-n is present at the TC-sink, the N2 byte is monitored:
+
+- An "all-zeros" N2-byte indicates a disconnection or misconnection within the tandem connection. In this case, the TC-RDI and ODI-bits are set to "1" in the reverse direction and TU-AIS is inserted in the egressing TU-n.
+- Bit 4 of the received N2 set to "1" indicates that a defect has already occurred before the tandem connection. In this case, the ODI bit is set to "1" in the reverse direction and TU-AIS is inserted in the egressing TU-n.
+- The multiframe in bits 7 and 8 is recovered and the contents are interpreted. If the multiframe cannot be found, the TC-RDI and ODI bits are set to "1" in the reverse direction and TU-AIS is inserted in the egressing TU-n.
+- The TC-API is recovered and compared with the expected TC-API. In the case of a mismatch, the TC-RDI and ODI bits are set to "1" in the reverse direction and TU-AIS is inserted in the egressing TU-n.
+
+The even BIP-2 is computed for each bit pair of every byte of the preceding VC-n including V5 and compared with the BIP-2 retrieved from the V5-byte. A difference not equal to zero indicates that the VC-n has been corrupted and then the OEI bit is set to "1" in the reverse direction. Furthermore, the actual BIP-2 is compared with the BIP-2 retrieved from the N2-byte. A difference not equal to
+
+zero indicates that the VC-n has been corrupted within the tandem connection and then the TC-REI is set to "1" in the reverse direction.
+
+If TU-AIS is not inserted at the tandem connection sink, then the N2-byte is set to all zeroes and the BIP is compensated according to the algorithm described in clause E.4.
+
+#### E.4 BIP-2 compensation
+
+Since the BIP-2 parity check is taken over the VC-n (including N2), writing into N2 at the TC-source or TC-sink will affect the VC-2/VC-12/VC-11 path parity calculation. Unless this is compensated, the error monitoring mechanism of BIP-2 is corrupted. Because the parity should always be consistent with the current state of the VC-n, the BIP has to be compensated each time N2-byte is modified. Since the BIP-2 value in a given frame reflects the parity check over the previous frame, the changes made to BIP-2 bits in the previous frame shall also be considered in the compensation of BIP-2 in the current frame. Therefore, the following equation shall be used for compensation of the individual bits of the BIP-2:
+
+$$\begin{aligned}
+ V5[1]'(t) &= V5[1](t-1) \\
+ &\oplus V5[1]'(t-1) \\
+ &\oplus N2[1](t-1) \oplus N2[3](t-1) \oplus N2[5](t-1) \oplus N2[7](t-1) \\
+ &\oplus N2[1]'(t-1) \oplus N2[3]'(t-1) \oplus N2[5]'(t-1) \oplus N2[7]'(t-1) \\
+ &\oplus V5[1](t) \\
+ V5[2]'(t) &= V5[2](t-1) \\
+ &\oplus V5[2]'(t-1) \\
+ &\oplus N2[2](t-1) \oplus N2[4](t-1) \oplus N2[6](t-1) \oplus N2[8](t-1) \\
+ &\oplus N2[2]'(t-1) \oplus N2[4]'(t-1) \oplus N2[6]'(t-1) \oplus N2[8]'(t-1) \\
+ &\oplus V5[2](t)
+ \end{aligned}$$
+
+where:
+
+V5[i] the existing V5[i] value in the incoming signal
+ V5[i]' the new (compensated) V5[i] value
+ N2[i] the existing N2[i] value in the incoming signal
+ N2[i]' the new value written into the N2[i] bit
+ $\oplus$ exclusive OR operator
+ t the time of the current frame
+ t-1 the time of the previous frame
+
+## Annex F
+
+### Transport of 10 Gbit/s Ethernet in a VC-4-64c
+
+(This annex forms an integral part of this Recommendation)
+
+IEEE has defined in IEEE 802.3ae a 10 Gbit/s Ethernet WAN interface. This interface is basically an STM-64 with a VC-4-64c and the Ethernet MAC mapped into the VC-4-64c using a 64B/66B coding (see IEEE 802.3ae, sections 49 and 50). Some limitations on the use of overhead bytes apply (see IEEE 802.3ae, section 50). Furthermore, the 10 Gbit/s Ethernet WAN signal has a different clock accuracy (see Appendix XII).
+
+#### F.1 Mapping of Ethernet MAC into VC-4-64c using 64B/66B coding
+
+The Ethernet MAC data is 64B/66B coded as defined in IEEE 802.3ae, section 49.2.4. The 64B/66B coded continuous data stream is mapped into the VC-4-64c payload area as shown in Figure F.1. The mapping is independent of the Ethernet block and packet boundaries. A bit re-labelling process is used to accommodate the different bit numbering schemes used by IEEE 802.3 and SDH (see IEEE 802.3ae, sections 49.1.4.5 and 50.3.1).
+
+The C2 path signal label shall be set to "1A" as defined in Table 9-11.
+
+Note that this mapping is an alternative to the mapping of Ethernet MAC frames into a VC-4-64c using GFP (see 10.6 and ITU-T Rec. G.7041/Y.1303).
+
+
+
+The diagram illustrates the mapping of 64B/66B coded Ethernet MAC data into a VC-4-64c payload. The payload is shown as a grid of 9 rows. The first 63 octets of each row are labeled as 'Fixed stuff' and correspond to the SDH overhead bytes (J1, B3, C2, G1, F2, H4, F3, K3, N1). The remaining 16640 octets of each row are labeled as '64B/66B data'. The total width of the payload is 16704 octets. The total height is 9 rows. A label 'G.707/Y.1322\_F.1' is in the bottom right corner.
+
+Diagram of 64B/66B coded Ethernet MAC mapping into VC-4-64c. The diagram shows a rectangular frame representing the VC-4-64c payload. The left side contains a column of 9 rows labeled J1, B3, C2, G1, F2, H4, F3, K3, and N1. The first 63 octets of each row are designated as 'Fixed stuff'. The remaining 16640 octets of each row are designated as '64B/66B data'. The total width of the frame is 16704 octets. The total height is 9 rows. A label 'G.707/Y.1322\_F.1' is in the bottom right corner.
+
+Figure F.1 – 64B/66B coded Ethernet MAC mapping into VC-4-64c
+
+## Annex G
+
+### Mapping of $N \times$ TU-12 in $M$ virtual concatenated SHDSL pairs (dSTM-12*NMi*)
+
+(This annex forms an integral part of this Recommendation)
+
+Clause E.14/G.991.2 specifies the mapping of $N \times$ TU-12 ( $N = 1 \dots 9$ ) into $M$ ( $M = 1 \dots 4$ ) virtual concatenated SHDSL wire pairs with an optional $(M \times i \times 8)$ kbit/s DCC.
+
+This annex specifies the associated additional multiplexing route and the SDH-related signal names.
+
+#### G.1 Multiplex structure
+
+Figure G.1 shows, within the general SDH multiplexing scheme (including the one defined in ITU-T Rec. G.708 for sub-STM-0), the additional multiplexing route provided by clause E.14/G.991.2. I.e., the multiplexing routes of specific dSTM-12*NMi* (of order $N = 1 \dots 9$ , $M = 1 \dots 4$ and $i = 0 \dots 7$ (single-pair mode), $i = 0 \dots 4$ (2-pair mode), $i = 0 \dots 3$ (3-pair mode) and $i = 0, 1, 2$ (4-pair mode)) via a tributary unit group d12*N* (TUG-d12*N*).
+
+
+
+The diagram illustrates the additional multiplexing routes for dSTM, showing the hierarchy from STM-256 down to dSTM-12NMi. The components and their relationships are as follows:
+
+- STM-256** (× 1) → **AUG256** (× 4) → **AU-4-256c** (Pointer processing) → **VC-4-256c** (Aligning) → **C-4-256c** (Mapping)
+- STM-64** (× 1) → **AUG64** (× 4) → **AU-4-64c** (Pointer processing) → **VC-4-64c** (Aligning) → **C-4-64c** (Mapping)
+- STM-16** (× 1) → **AUG16** (× 1) → **AU-4-16c** (Pointer processing) → **VC-4-16c** (Aligning) → **C-4-16c** (Mapping)
+- STM-4** (× 1) → **AUG4** (× 1) → **AU-4-4c** (Pointer processing) → **VC-4-4c** (Aligning) → **C-4-4c** (Mapping)
+- STM-1** (× 1) → **AUG1** (× 1) → **AU-4** (Pointer processing) → **VC-4** (Aligning) → **C-4** (Mapping)
+- STM-0** (× 1) → **AU-3** (Pointer processing) → **VC-3** (Aligning) → **C-3** (Mapping)
+- sSTM-2n (\*\*)** (× 1) → **TUG-2n (\*\*)** (× n (\*\*)) → **TUG-2** (× 1) → **TU-2** (Pointer processing) → **VC-2** (Aligning) → **C-2** (Mapping)
+- sSTM-1k (\*)** (× 1) → **TUG-1k (\*)** (× k (\*)) → **TUG-2** (× 1) → **TU-12** (Pointer processing) → **VC-12** (Aligning) → **C-12** (Mapping)
+- dSTM-12NMi (\*\*\*)** (× 1) → **TUG-d12N (\*\*\*)** (× N (\*\*\*)) → **TUG-2** (× 1) → **TU-11** (Pointer processing) → **VC-11** (Aligning) → **C-11** (Mapping)
+
+Additional connections shown in the diagram:
+
+- VC-4** (× 3) → **TUG-3** (× 1) → **TU-3** (Pointer processing) → **VC-3** (Aligning) → **C-3** (Mapping)
+- VC-3** (× 7) → **TUG-2** (× 1)
+
+**Legend:**
+
+- Pointer processing: Shaded box
+- Aligning: Dotted line with arrow
+- Multiplexing: Red dashed line with arrow
+- Mapping: Blue solid line with arrow
+- dSTM-1NMi multiplexing routes: Red solid line with arrow
+
+**Notes:**
+
+- (\*) k = 1, 2, 4, 8 and 16
+- (\*\*) n = 1, 2 and 4
+- (\*\*\*) N = 1...9 M = 1...4 i = 0,...,7 (M = 1), i = 0,...,4 (M = 2), i = 0,...,3 (M = 3), i = 0, 1, 2 (M = 4) (see Table G.1)
+- C-n Container-n
+
+G.707/Y.1322\_FG-1
+
+Diagram showing additional multiplexing routes for dSTM. It illustrates the hierarchy from STM-256 down to dSTM-12NMi, showing various AUG, TUG, and TU stages with their respective multiplexing factors and container mappings.
+
+NOTE – This figure is informative and shows the additional multiplexing routes added by this Recommendation (dSTM-12NMi). It is adapted from ITU-T Recs G.707/Y.1322 and G.708.
+
+**Figure G.1 – Additional structure for dSTM**
+
+## G.2 Mapping overview
+
+Table G.1 provides an overview of the defined set of dSTM-12*NMi* signals. This table is based on Table E.42/G.991.2.
+
+**Table G.1 – Assignment of dSTM-12*NMi* names to *N* × TU-12/VC-12 connections over *M*-Pair SHDSL**
+
+| Number ( N ) of TU-12 / VC-12 connections | Aggregate payload bit rate [kbit/s] | 1-Pair SHDSL | 2-Pair SHDSL | 3-Pair SHDSL | 4-Pair SHDSL |
+|-----------------------------------------------------------|-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|
+| | | Size 1 × ks bits of each payload sub-block withks = i + n × 8 [bits] | Size 2 × ks bits of each payload sub-block withks = i + n × 8 [bits] | Size 3 × ks bits of each payload sub-block withks = i + n × 8 [bits] | Size 4 × ks bits of each payload sub-block withks = i + n × 8 [bits] |
+| | | M = 1 | M = 2 | M = 3 | M = 4 |
+| 1 | 2304 + M × i × 8 | n = 36; i = 0,...,7 dSTM-12110 to dSTM-12117 | n = 18; i = 0,...,4 dSTM-12120 to dSTM-12124 | n = 12; i = 0,...,3 dSTM-12130 to dSTM-12133 | n = 9; i = 0,1,2 dSTM-12140 to dSTM-12142 |
+| 2 | 4608 + M × i × 8 | n = 72; i = 0,...,7 dSTM-12210 to dSTM-12217 | n = 36; i = 0,...,4 dSTM-12220 to dSTM-12224 | n = 24; i = 0,...,3 dSTM-12230 to dSTM-12233 | n = 18; i = 0,1,2 dSTM-12240 to dSTM-12242 |
+| 3 | 6912 + M × i × 8 | – | n = 54; i = 0,...,4 dSTM-12320 to dSTM-12324 | n = 36; i = 0,...,3 dSTM-12330 to dSTM-12333 | n = 27; i = 0,1,2 dSTM-12340 to dSTM-12342 |
+| 4 | 9216 + M × i × 8 | – | n = 72; i = 0,...,4 dSTM-12420 to dSTM-12424 | n = 48; i = 0,...,3 dSTM-12430 to dSTM-12433 | n = 36; i = 0,1,2 dSTM-12440 to dSTM-12442 |
+| 5 | 11 520 + M × i × 8 | – | – | n = 60; i = 0,...,3 dSTM-12530 to dSTM-12533 | n = 45; i = 0,1,2 dSTM-12540 to dSTM-12542 |
+| 6 | 13 824 + M × i × 8 | – | – | n = 72; i = 0,...,3 dSTM-12630 to dSTM-12633 | n = 54; i = 0,1,2 dSTM-12640 to dSTM-12642 |
+| 7 | 16 128 + M × i × 8 | – | – | n = 84; i = 0,...,3 dSTM-12730 to dSTM-12733 | n = 63; i = 0,1,2 dSTM-12740 to dSTM-12742 |
+| 8 | 18 432 + M × i × 8 | – | – | – | n = 72; i = 0,1,2 dSTM-12840 to dSTM-12842 |
+| 9 | 20 736 + M × i × 8 | – | – | – | n = 81; i = 0,1,2 dSTM-12940 to dSTM-12942 |
+| | | If no data communication channel is used i = 0. If management, signalling, control and maintenance functions are to be transmitted over the Z-bits, i × 8 kbit/s per wire-pair are additionally required with i = 1,...,7 (1-pair), i = 1,...,4 (2-pair), i = 1, 2, 3 (3-pair) and i = 1, 2 (4-pair). | | | |
+
+## Annex H
+
+### Mapping of TU-11, TU-12, TU-2 and TU-3 in G-PON GEM connections
+
+(This annex forms an integral part of this Recommendation)
+
+Clause I.4/G.984.3 specifies the mapping of individual TU-11, TU-12, TU-2 and TU-3 into GEM connections supported on G-PON transport systems.
+
+This annex specifies the associated additional multiplexing routes and the SDH-related signal names.
+
+#### H.1 Multiplex structure
+
+Figure H.1 shows, within the general SDH multiplexing scheme (including the one defined in ITU-T Rec. G.708 for sub STM-0), the additional multiplexing routes provided by clause I.4/G.984.3. This includes: the multiplexing route of gSTM-11 via a tributary unit group g11 (TUG-g11), multiplexing route of gSTM-12 via a tributary unit group g12 (TUG-g12), multiplexing route of gSTM-2 via a tributary unit group 2 (TUG-2), and multiplexing route of gSTM-3 via a tributary unit group 3 (TUG-3).
+
+#### H.2 Mapping overview
+
+Table H.1 provides an overview of the defined set of gSTM-11, gSTM-12, gSTM-2 and gSTM-3 signals. This table is based on the table in clause I.4/G.984.3.
+
+**Table H.1 – Assignment of gSTM-x names to TU-x connections over GEM**
+
+| Type of TU-x connections | Aggregate payload bit rate [kbit/s] | Size of each GEM payload [bytes] |
+|--------------------------|-------------------------------------|----------------------------------|
+| 11 | $108 \times 8/0.5 = 1\,728$ | $4(3 \times 9) = 108$ |
+| 12 | $144 \times 8/0.5 = 2\,304$ | $4(4 \times 9) = 144$ |
+| 2 | $432 \times 8/0.5 = 6\,912$ | $4(12 \times 9) = 432$ |
+| 3 | $774 \times 8/0.125 = 49\,536$ | $86 \times 9 = 774$ |
+
+
+
+STM-256 $\xrightarrow{\times 1}$ AUG256 $\xrightarrow{\times 4}$ AU-4-256c $\dashleftarrow$ VC-4-256c $\leftarrow$ C-4-256c
+ STM-64 $\xrightarrow{\times 1}$ AUG64 $\xrightarrow{\times 4}$ AU-4-64c $\dashleftarrow$ VC-4-64c $\leftarrow$ C-4-64c
+ STM-16 $\xrightarrow{\times 1}$ AUG16 $\xrightarrow{\times 1}$ AU-4-16c $\dashleftarrow$ VC-4-16c $\leftarrow$ C-4-16c
+ STM-4 $\xrightarrow{\times 1}$ AUG4 $\xrightarrow{\times 4}$ AU-4-4c $\dashleftarrow$ VC-4-4c $\leftarrow$ C-4-4c
+ STM-1 $\xrightarrow{\times 1}$ AUG1 $\xrightarrow{\times 1}$ AU-4 $\dashleftarrow$ VC-4 $\leftarrow$ C-4
+ gSTM-3 $\xrightarrow{\times 1}$ TUG-3 $\xrightarrow{\times 1}$ TU-3 $\dashleftarrow$ VC-3 $\leftarrow$ C-3
+ STM-0 $\xrightarrow{\times 1}$ AU-3 $\dashleftarrow$ VC-3 $\leftarrow$ C-3
+ gSTM-2 $\xrightarrow{\times 1}$ TUG-2 $\xrightarrow{\times 1}$ TU-2 $\dashleftarrow$ VC-2 $\leftarrow$ C-2
+ sSTM-2n (\*\*) $\xrightarrow{\times 1}$ TUG-2n (\*\*) $\xrightarrow{\times n (**)}$ TUG-2 $\xrightarrow{\times 1}$ TU-2 $\dashleftarrow$ VC-2 $\leftarrow$ C-2
+ sSTM-1k (\*) $\xrightarrow{\times 1}$ TUG-1k (\*) $\xrightarrow{\times k (*)}$ TUG-2 $\xrightarrow{\times 3}$ TU-12 $\dashleftarrow$ VC-12 $\leftarrow$ C-12
+ dSTM-12NMi (\*\*\*) $\xrightarrow{\times 1}$ TUG-d12N (\*\*\*) $\xrightarrow{\times N (***)}$ TUG-2 $\xrightarrow{\times 4}$ TU-11 $\dashleftarrow$ VC-11 $\leftarrow$ C-11
+ gSTM-12 $\xrightarrow{\times 1}$ TUG-g12 $\xrightarrow{\times 1}$ TU-12 $\dashleftarrow$ VC-12 $\leftarrow$ C-12
+ gSTM-11 $\xrightarrow{\times 1}$ TUG-g11 $\xrightarrow{\times 1}$ TU-11 $\dashleftarrow$ VC-11 $\leftarrow$ C-11
+
+G.707/Y.1322\_FG-1
+
+Legend:
+ [Shaded Box] Pointer processing
+ $\dashleftarrow$ Aligning
+ $\leftarrow$ Mapping
+ $\dashrightarrow$ Multiplexing
+ $\xrightarrow{\text{solid red}}$ gSTM-x multiplexing routes
+
+(\*) $k = 1, 2, 4, 8$ and $16$
+ (\*\*) $n = 1, 2$ and $4$
+ (\*\*\*) $N = 1 \dots 9$ $M = 1 \dots 4$ $i = 0 \dots 7$ ( $M = 1$ ), $i = 0 \dots 4$ ( $M = 2$ ), $i = 0 \dots 3$ ( $M = 3$ ), $i = 0, 1, 2$ ( $M = 4$ ) (see Table G.1)
+ C-n Container-n
+
+Diagram showing the additional structure for gSTM-x multiplexing routes. It illustrates the flow from various STM signals (STM-256, STM-64, STM-16, STM-4, STM-1, gSTM-3, STM-0, gSTM-2, sSTM-2n (\*\*), sSTM-1k (\*), dSTM-12NMi (\*\*\*), gSTM-12, gSTM-11) through AUG, AU, VC, TUG, TU, and C containers. The diagram uses different line styles: dashed red for multiplexing, solid red for gSTM-x multiplexing routes, dotted black for aligning, and solid blue for mapping. Shaded boxes indicate pointer processing. Multipliers like 'x 1', 'x 4', 'x 3', 'x 7', 'x n (\*\*)', 'x k (\*)', 'x N (\*\*\*)' are shown at various stages. A legend at the bottom explains the symbols and line types. A note states that the figure is informative and shows additional gSTM-x multiplexing routes. A small label 'G.707/Y.1322\_FG-1' is present near the bottom right of the diagram.
+
+NOTE – This figure is informative and shows the additional gSTM-x multiplexing routes.
+
+Figure H.1 – Additional structure for gSTM-x
+
+## Appendix I
+
+### Relationship between TU-2 address and location of columns within a VC-4
+
+(This appendix does not form an integral part of this Recommendation)
+
+Table I.1 shows the relationship between TU-2 address and location of columns within a VC-4.
+
+**Table I.1 – Relationship between TU-2 address
+and location of columns within a VC-4**
+
+| TU-2 address | | | TU-2 column number | | | | | | | | | | | |
+|--------------|---|---|--------------------|----|----|----|-----|-----|-----|-----|-----|-----|-----|-----|
+| K | L | M | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
+| 1 | 1 | 0 | 10 | 31 | 52 | 73 | 94 | 115 | 136 | 157 | 178 | 199 | 220 | 241 |
+| 1 | 2 | 0 | 13 | 34 | 55 | 76 | 97 | 118 | 139 | 160 | 181 | 202 | 223 | 244 |
+| 1 | 3 | 0 | 16 | 37 | 58 | 79 | 100 | 121 | 142 | 163 | 184 | 205 | 226 | 247 |
+| 1 | 4 | 0 | 19 | 40 | 61 | 82 | 103 | 124 | 145 | 166 | 187 | 208 | 229 | 250 |
+| 1 | 5 | 0 | 22 | 43 | 64 | 85 | 106 | 127 | 148 | 169 | 190 | 211 | 232 | 253 |
+| 1 | 6 | 0 | 25 | 46 | 67 | 88 | 109 | 130 | 151 | 172 | 193 | 214 | 235 | 256 |
+| 1 | 7 | 0 | 28 | 49 | 70 | 91 | 112 | 133 | 154 | 175 | 196 | 217 | 238 | 259 |
+| 2 | 1 | 0 | 11 | 32 | 53 | 74 | 95 | 116 | 137 | 158 | 179 | 200 | 221 | 242 |
+| 2 | 2 | 0 | 14 | 35 | 56 | 77 | 98 | 119 | 140 | 161 | 182 | 203 | 224 | 245 |
+| 2 | 3 | 0 | 17 | 38 | 59 | 80 | 101 | 122 | 143 | 164 | 185 | 206 | 227 | 248 |
+| 2 | 4 | 0 | 20 | 41 | 62 | 83 | 104 | 125 | 146 | 167 | 188 | 209 | 230 | 251 |
+| 2 | 5 | 0 | 23 | 44 | 65 | 86 | 107 | 128 | 149 | 170 | 191 | 212 | 233 | 254 |
+| 2 | 6 | 0 | 26 | 47 | 68 | 89 | 110 | 131 | 152 | 173 | 194 | 215 | 236 | 257 |
+| 2 | 7 | 0 | 29 | 50 | 71 | 92 | 113 | 134 | 155 | 176 | 197 | 218 | 239 | 260 |
+| 3 | 1 | 0 | 12 | 33 | 54 | 75 | 96 | 117 | 138 | 159 | 180 | 201 | 222 | 243 |
+| 3 | 2 | 0 | 15 | 36 | 57 | 78 | 99 | 120 | 141 | 162 | 183 | 204 | 225 | 246 |
+| 3 | 3 | 0 | 18 | 39 | 60 | 81 | 102 | 123 | 144 | 165 | 186 | 207 | 228 | 249 |
+| 3 | 4 | 0 | 21 | 42 | 63 | 84 | 105 | 126 | 147 | 168 | 189 | 210 | 231 | 252 |
+| 3 | 5 | 0 | 24 | 45 | 66 | 87 | 108 | 129 | 150 | 171 | 192 | 213 | 234 | 255 |
+| 3 | 6 | 0 | 27 | 48 | 69 | 90 | 111 | 132 | 153 | 174 | 195 | 216 | 237 | 258 |
+| 3 | 7 | 0 | 30 | 51 | 72 | 93 | 114 | 135 | 156 | 177 | 198 | 219 | 240 | 261 |
+
+## Appendix II
+
+### Relationship between TU-12 address and location of columns within a VC-4
+
+(This appendix does not form an integral part of this Recommendation)
+
+Table II.1 shows the relationship between TU-12 address and location of columns within a VC-4.
+
+**Table II.1 – Relationship between TU-12 address and location of columns within a VC-4**
+
+| TU-12 address | | | TU-12 column number | | | |
+|---------------|---|---|---------------------|-----|-----|-----|
+| K | L | M | 1 | 2 | 3 | 4 |
+| 1 | 1 | 1 | 10 | 73 | 136 | 199 |
+| 1 | 1 | 2 | 31 | 94 | 157 | 220 |
+| 1 | 1 | 3 | 52 | 115 | 178 | 241 |
+| 1 | 2 | 1 | 13 | 76 | 139 | 202 |
+| 1 | 2 | 2 | 34 | 97 | 160 | 223 |
+| 1 | 2 | 3 | 55 | 118 | 181 | 244 |
+| 1 | 3 | 1 | 16 | 79 | 142 | 205 |
+| 1 | 3 | 2 | 37 | 100 | 163 | 226 |
+| 1 | 3 | 3 | 58 | 121 | 184 | 247 |
+| 1 | 4 | 1 | 19 | 82 | 145 | 208 |
+| 1 | 4 | 2 | 40 | 103 | 166 | 229 |
+| 1 | 4 | 3 | 61 | 124 | 187 | 250 |
+| 1 | 5 | 1 | 22 | 85 | 148 | 211 |
+| 1 | 5 | 2 | 43 | 106 | 169 | 232 |
+| 1 | 5 | 3 | 64 | 127 | 190 | 253 |
+| 1 | 6 | 1 | 25 | 88 | 151 | 214 |
+| 1 | 6 | 2 | 46 | 109 | 172 | 235 |
+| 1 | 6 | 3 | 67 | 130 | 193 | 256 |
+| 1 | 7 | 1 | 28 | 91 | 154 | 217 |
+| 1 | 7 | 2 | 49 | 112 | 175 | 238 |
+| 1 | 7 | 3 | 70 | 133 | 196 | 259 |
+| 2 | 1 | 1 | 11 | 74 | 137 | 200 |
+| 2 | 1 | 2 | 32 | 95 | 158 | 221 |
+| 2 | 1 | 3 | 53 | 116 | 179 | 242 |
+| 2 | 2 | 1 | 14 | 77 | 140 | 203 |
+| 2 | 2 | 2 | 35 | 98 | 161 | 224 |
+| 2 | 2 | 3 | 56 | 119 | 182 | 245 |
+| 2 | 3 | 1 | 17 | 80 | 143 | 206 |
+| 2 | 3 | 2 | 38 | 101 | 164 | 227 |
+| 2 | 3 | 3 | 59 | 122 | 185 | 248 |
+
+**Table II.1 – Relationship between TU-12 address
+and location of columns within a VC-4**
+
+| TU-12 address | | | TU-12 column number | | | |
+|---------------|---|---|---------------------|-----|-----|-----|
+| K | L | M | 1 | 2 | 3 | 4 |
+| 2 | 4 | 1 | 20 | 83 | 146 | 209 |
+| 2 | 4 | 2 | 41 | 104 | 167 | 230 |
+| 2 | 4 | 3 | 62 | 125 | 188 | 251 |
+| 2 | 5 | 1 | 23 | 86 | 149 | 212 |
+| 2 | 5 | 2 | 44 | 107 | 170 | 233 |
+| 2 | 5 | 3 | 65 | 128 | 191 | 254 |
+| 2 | 6 | 1 | 26 | 89 | 152 | 215 |
+| 2 | 6 | 2 | 47 | 110 | 173 | 236 |
+| 2 | 6 | 3 | 68 | 131 | 194 | 257 |
+| 2 | 7 | 1 | 29 | 92 | 155 | 218 |
+| 2 | 7 | 2 | 50 | 113 | 176 | 239 |
+| 2 | 7 | 3 | 71 | 134 | 197 | 260 |
+| 3 | 1 | 1 | 12 | 75 | 138 | 201 |
+| 3 | 1 | 2 | 33 | 96 | 159 | 222 |
+| 3 | 1 | 3 | 54 | 117 | 180 | 243 |
+| 3 | 2 | 1 | 15 | 78 | 141 | 204 |
+| 3 | 2 | 2 | 36 | 99 | 162 | 225 |
+| 3 | 2 | 3 | 57 | 120 | 183 | 246 |
+| 3 | 3 | 1 | 18 | 81 | 144 | 207 |
+| 3 | 3 | 2 | 39 | 102 | 165 | 228 |
+| 3 | 3 | 3 | 60 | 123 | 186 | 249 |
+| 3 | 4 | 1 | 21 | 84 | 147 | 210 |
+| 3 | 4 | 2 | 42 | 105 | 168 | 231 |
+| 3 | 4 | 3 | 63 | 126 | 189 | 252 |
+| 3 | 5 | 1 | 24 | 87 | 150 | 213 |
+| 3 | 5 | 2 | 45 | 108 | 171 | 234 |
+| 3 | 5 | 3 | 66 | 129 | 192 | 255 |
+| 3 | 6 | 1 | 27 | 90 | 153 | 216 |
+| 3 | 6 | 2 | 48 | 111 | 174 | 237 |
+| 3 | 6 | 3 | 69 | 132 | 195 | 258 |
+| 3 | 7 | 1 | 30 | 93 | 156 | 219 |
+| 3 | 7 | 2 | 51 | 114 | 177 | 240 |
+| 3 | 7 | 3 | 72 | 135 | 198 | 261 |
+
+## Appendix III
+
+### Relationship between TU-11 address and location of columns within a VC-4
+
+(This appendix does not form an integral part of this Recommendation)
+
+Table III.1 shows the relationship between TU-11 address and location of columns within a VC-4.
+
+**Table III.1 – Relationship between TU-11 address and location of columns within a VC-4**
+
+| TU-11 address | | | TU-11 column number | | |
+|---------------|---|---|---------------------|-----|-----|
+| K | L | M | 1 | 2 | 3 |
+| 1 | 1 | 1 | 10 | 94 | 178 |
+| 1 | 1 | 2 | 31 | 115 | 199 |
+| 1 | 1 | 3 | 52 | 136 | 220 |
+| 1 | 1 | 4 | 73 | 157 | 241 |
+| 1 | 2 | 1 | 13 | 97 | 181 |
+| 1 | 2 | 2 | 34 | 118 | 202 |
+| 1 | 2 | 3 | 55 | 139 | 223 |
+| 1 | 2 | 4 | 76 | 160 | 244 |
+| 1 | 3 | 1 | 16 | 100 | 184 |
+| 1 | 3 | 2 | 37 | 121 | 205 |
+| 1 | 3 | 3 | 58 | 142 | 226 |
+| 1 | 3 | 4 | 79 | 163 | 247 |
+| 1 | 4 | 1 | 19 | 103 | 187 |
+| 1 | 4 | 2 | 40 | 124 | 208 |
+| 1 | 4 | 3 | 61 | 145 | 229 |
+| 1 | 4 | 4 | 82 | 166 | 250 |
+| 1 | 5 | 1 | 22 | 106 | 190 |
+| 1 | 5 | 2 | 43 | 127 | 211 |
+| 1 | 5 | 3 | 64 | 148 | 232 |
+| 1 | 5 | 4 | 85 | 169 | 253 |
+| 1 | 6 | 1 | 25 | 109 | 193 |
+| 1 | 6 | 2 | 46 | 130 | 214 |
+| 1 | 6 | 3 | 67 | 151 | 235 |
+| 1 | 6 | 4 | 88 | 172 | 256 |
+| 1 | 7 | 1 | 28 | 112 | 196 |
+| 1 | 7 | 2 | 49 | 133 | 217 |
+| 1 | 7 | 3 | 70 | 154 | 238 |
+| 1 | 7 | 4 | 91 | 175 | 259 |
+| 2 | 1 | 1 | 11 | 95 | 179 |
+| 2 | 1 | 2 | 32 | 116 | 200 |
+| 2 | 1 | 3 | 53 | 137 | 221 |
+| 2 | 1 | 4 | 74 | 158 | 242 |
+
+**Table III.1 – Relationship between TU-11 address
+and location of columns within a VC-4**
+
+| TU-11 address | | | TU-11 column number | | |
+|---------------|---|---|---------------------|-----|-----|
+| K | L | M | 1 | 2 | 3 |
+| 2 | 2 | 1 | 14 | 98 | 182 |
+| 2 | 2 | 2 | 35 | 119 | 203 |
+| 2 | 2 | 3 | 56 | 140 | 224 |
+| 2 | 2 | 4 | 77 | 161 | 245 |
+| 2 | 3 | 1 | 17 | 101 | 185 |
+| 2 | 3 | 2 | 38 | 122 | 206 |
+| 2 | 3 | 3 | 59 | 143 | 227 |
+| 2 | 3 | 4 | 80 | 164 | 248 |
+| 2 | 4 | 1 | 20 | 104 | 188 |
+| 2 | 4 | 2 | 41 | 125 | 209 |
+| 2 | 4 | 3 | 62 | 146 | 230 |
+| 2 | 4 | 4 | 83 | 167 | 251 |
+| 2 | 5 | 1 | 23 | 107 | 191 |
+| 2 | 5 | 2 | 44 | 128 | 212 |
+| 2 | 5 | 3 | 65 | 149 | 233 |
+| 2 | 5 | 4 | 86 | 170 | 254 |
+| 2 | 6 | 1 | 26 | 110 | 194 |
+| 2 | 6 | 2 | 47 | 131 | 215 |
+| 2 | 6 | 3 | 68 | 152 | 236 |
+| 2 | 6 | 4 | 89 | 173 | 257 |
+| 2 | 7 | 1 | 29 | 113 | 197 |
+| 2 | 7 | 2 | 50 | 134 | 218 |
+| 2 | 7 | 3 | 71 | 155 | 239 |
+| 2 | 7 | 4 | 92 | 176 | 260 |
+| 3 | 1 | 1 | 12 | 96 | 180 |
+| 3 | 1 | 2 | 33 | 117 | 201 |
+| 3 | 1 | 3 | 54 | 138 | 222 |
+| 3 | 1 | 4 | 75 | 159 | 243 |
+| 3 | 2 | 1 | 15 | 99 | 183 |
+| 3 | 2 | 2 | 36 | 120 | 204 |
+| 3 | 2 | 3 | 57 | 141 | 225 |
+| 3 | 2 | 4 | 78 | 162 | 246 |
+| 3 | 3 | 1 | 18 | 102 | 186 |
+| 3 | 3 | 2 | 39 | 123 | 207 |
+| 3 | 3 | 3 | 60 | 144 | 228 |
+| 3 | 3 | 4 | 81 | 165 | 249 |
+| 3 | 4 | 1 | 21 | 105 | 189 |
+| 3 | 4 | 2 | 42 | 126 | 210 |
+
+**Table III.1 – Relationship between TU-11 address
+and location of columns within a VC-4**
+
+| TU-11 address | | | TU-11 column number | | |
+|---------------|---|---|---------------------|-----|-----|
+| K | L | M | 1 | 2 | 3 |
+| 3 | 4 | 3 | 63 | 147 | 231 |
+| 3 | 4 | 4 | 84 | 168 | 252 |
+| 3 | 5 | 1 | 24 | 108 | 192 |
+| 3 | 5 | 2 | 45 | 129 | 213 |
+| 3 | 5 | 3 | 66 | 150 | 234 |
+| 3 | 5 | 4 | 87 | 171 | 255 |
+| 3 | 6 | 1 | 27 | 111 | 195 |
+| 3 | 6 | 2 | 48 | 132 | 216 |
+| 3 | 6 | 3 | 69 | 153 | 237 |
+| 3 | 6 | 4 | 90 | 174 | 258 |
+| 3 | 7 | 1 | 30 | 114 | 198 |
+| 3 | 7 | 2 | 51 | 135 | 219 |
+| 3 | 7 | 3 | 72 | 156 | 240 |
+| 3 | 7 | 4 | 93 | 177 | 261 |
+
+## Appendix IV
+
+### Relationship between TU-2 address and location of columns within a VC-3
+
+(This appendix does not form an integral part of this Recommendation)
+
+Table IV.1 shows the relationship between TU-2 address and location of columns within a VC-3.
+
+**Table IV.1 – Relationship between TU-2 address
+and location of columns within a VC-3**
+
+| TU-2 address | | TU-2 column number | | | | | | | | | | | |
+|--------------|---|--------------------|----|----|----|----|----|----|----|----|----|----|----|
+| L | M | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
+| 1 | 0 | 2 | 9 | 16 | 23 | 30 | 37 | 44 | 51 | 58 | 65 | 72 | 79 |
+| 2 | 0 | 3 | 10 | 17 | 24 | 31 | 38 | 45 | 52 | 59 | 66 | 73 | 80 |
+| 3 | 0 | 4 | 11 | 18 | 25 | 32 | 39 | 46 | 53 | 60 | 67 | 74 | 81 |
+| 4 | 0 | 5 | 12 | 19 | 26 | 33 | 40 | 47 | 54 | 61 | 68 | 75 | 82 |
+| 5 | 0 | 6 | 13 | 20 | 27 | 34 | 41 | 48 | 55 | 62 | 69 | 76 | 83 |
+| 6 | 0 | 7 | 14 | 21 | 28 | 35 | 42 | 49 | 56 | 63 | 70 | 77 | 84 |
+| 7 | 0 | 8 | 15 | 22 | 29 | 36 | 43 | 50 | 57 | 64 | 71 | 78 | 85 |
+
+## Appendix V
+
+### Relationship between TU-12 address and location of columns within a VC-3
+
+(This appendix does not form an integral part of this Recommendation)
+
+Table V.1 shows the relationship between TU-12 address and location of columns within a VC-3.
+
+**Table V.1 – Relationship between TU-12 address and location of columns within a VC-3**
+
+| TU-12 address | | TU-12 column number | | | |
+|---------------|---|---------------------|----|----|----|
+| L | M | 1 | 2 | 3 | 4 |
+| 1 | 1 | 2 | 23 | 44 | 65 |
+| 1 | 2 | 9 | 30 | 51 | 72 |
+| 1 | 3 | 16 | 37 | 58 | 79 |
+| 2 | 1 | 3 | 24 | 45 | 66 |
+| 2 | 2 | 10 | 31 | 52 | 73 |
+| 2 | 3 | 17 | 38 | 59 | 80 |
+| 3 | 1 | 4 | 25 | 46 | 67 |
+| 3 | 2 | 11 | 32 | 53 | 74 |
+| 3 | 3 | 18 | 39 | 60 | 81 |
+| 4 | 1 | 5 | 26 | 47 | 68 |
+| 4 | 2 | 12 | 33 | 54 | 75 |
+| 4 | 3 | 19 | 40 | 61 | 82 |
+| 5 | 1 | 6 | 27 | 48 | 69 |
+| 5 | 2 | 13 | 34 | 55 | 76 |
+| 5 | 3 | 20 | 41 | 62 | 83 |
+| 6 | 1 | 7 | 28 | 49 | 70 |
+| 6 | 2 | 14 | 35 | 56 | 77 |
+| 6 | 3 | 21 | 42 | 63 | 84 |
+| 7 | 1 | 8 | 29 | 50 | 71 |
+| 7 | 2 | 15 | 36 | 57 | 78 |
+| 7 | 3 | 22 | 43 | 64 | 85 |
+
+## Appendix VI
+
+### Relationship between TU-11 address and location of columns within a VC-3
+
+(This appendix does not form an integral part of this Recommendation)
+
+Table VI.1 shows the relationship between TU-11 address and location of columns within a VC-3.
+
+**Table VI.1 – Relationship between TU-11 address and location of columns within a VC-3**
+
+| TU-11 address | | TU-11 column number | | |
+|---------------|---|---------------------|----|----|
+| L | M | 1 | 2 | 3 |
+| 1 | 1 | 2 | 30 | 58 |
+| 1 | 2 | 3 | 31 | 59 |
+| 1 | 3 | 5 | 33 | 61 |
+| 1 | 4 | 7 | 35 | 63 |
+| 2 | 1 | 4 | 32 | 60 |
+| 2 | 2 | 12 | 40 | 68 |
+| 2 | 3 | 18 | 46 | 74 |
+| 2 | 4 | 24 | 52 | 80 |
+| 3 | 1 | 6 | 34 | 62 |
+| 3 | 2 | 13 | 41 | 69 |
+| 3 | 3 | 19 | 47 | 75 |
+| 3 | 4 | 25 | 53 | 81 |
+| 4 | 1 | 8 | 36 | 64 |
+| 4 | 2 | 14 | 42 | 70 |
+| 4 | 3 | 20 | 48 | 76 |
+| 4 | 4 | 26 | 54 | 82 |
+| 5 | 1 | 9 | 37 | 65 |
+| 5 | 2 | 15 | 43 | 71 |
+| 5 | 3 | 21 | 49 | 77 |
+| 5 | 4 | 27 | 55 | 83 |
+| 6 | 1 | 10 | 38 | 66 |
+| 6 | 2 | 16 | 44 | 72 |
+| 6 | 3 | 22 | 50 | 78 |
+| 6 | 4 | 28 | 56 | 84 |
+| 7 | 1 | 11 | 39 | 67 |
+| 7 | 2 | 17 | 45 | 73 |
+| 7 | 3 | 23 | 51 | 79 |
+| 7 | 4 | 29 | 57 | 85 |
+
+## Appendix VII
+
+### Enhanced remote defect indication (E-RDI)
+
+(This appendix does not form an integral part of this Recommendation)
+
+As an option, equipment may provide additional defect differentiation. Remote defect indication (RDI), as defined in clauses 9.3.1.4 and 9.3.2.1, provides back to the trail termination source an indication if either server signal defects, or connectivity defects, are being detected by the trail termination sink. RDI does not differentiate between types of defects. This appendix defines an enhanced remote defect indication which supports three types of RDI indications: E-RDI server defect, E-RDI connectivity defect and E-RDI payload defect. It provides differentiation between server signal defects (E-RDI server), connectivity defects (E-RDI connectivity) and payload or adaptation defects (E-RDI payload). If more than one of these defects occurs at the same time, the priority for the type of indication used will be in the order of:
+
+- 1) E-RDI server;
+- 2) E-RDI connectivity;
+- 3) E-RDI payload.
+
+The use of this option provides an operator with enhanced fault sectionalization capabilities for a trail crossing multi-operator domains. The enhanced remote defect indication option is compatible with equipment supporting RDI.
+
+#### VII.1 VC-4-Xc/VC-4/VC-3 paths
+
+As described in clause 9.3.1.4, byte G1 is allocated to convey back to a VC-4-Xc/VC-4/VC-3 trail termination source the status and performance of the complete trail. Bits 5 to 7 of byte G1 may be used to provide an enhanced remote defect indication with additional differentiation between the payload defect (PLM), server defects (AIS, LOP) and connectivity defects (TIM, UNEQ). The codes from Table VII.1 will be used.
+
+**Table VII.1 – G1 (b5-b7) coding and triggers**
+
+| b5 | b6 | b7 | Meaning | Triggers |
+|----|----|----|---------------------------|------------------|
+| 0 | 0 | 1 | No remote defect | No remote defect |
+| 0 | 1 | 0 | E-RDI payload defect | PLM |
+| 1 | 0 | 1 | E-RDI server defect | AIS, LOP |
+| 1 | 1 | 0 | E-RDI connectivity defect | TIM, UNEQ |
+
+For the E-RDI codes, bit 7 is set to the inverse of bit 6. Table VII.2 provides the E-RDI G1 (b5-b7) code interpretation.
+
+**Table VII.2 – G1 (b5-b7) coding and E-RDI interpretation**
+
+| b5 | b6 | b7 | E-RDI Interpretation |
+|-----------|-----------|-----------|-------------------------------------|
+| 0 | 0 | 0 | No remote defect (Note 1) |
+| 0 | 0 | 1 | No remote defect |
+| 0 | 1 | 0 | E-RDI payload defect (Note 2) |
+| 0 | 1 | 1 | No remote defect (Note 1) |
+| 1 | 0 | 0 | E-RDI server defect (Note 1) |
+| 1 | 0 | 1 | Remote E-RDI server defect |
+| 1 | 1 | 0 | Remote E-RDI connectivity defect |
+| 1 | 1 | 1 | Remote E-RDI server defect (Note 1) |
+
+NOTE 1 – These codes are generated by RDI supporting equipment and are interpreted by E-RDI supporting equipment as shown. For equipment supporting RDI (see clause 9.3.1.4), this code is triggered by the presence or absence of one of the following defects: AIS, LOP, TIM or UNEQ. Equipment conforming to an earlier version of this Recommendation may include PLM as a trigger condition. ATM equipment complying with the 1993 version of the I.432.x series of ITU-T Recommendations may include LCD as a trigger condition. Note that for some national networks, this code is triggered only by an AIS or LOP defect.
+
+NOTE 2 – ATM equipment complying with the 1996 version of ITU-T Rec. I.432.2 may include LCD as a trigger condition.
+
+The E-RDI G1 (b5-b7) code interpretation provides for interworking with equipment which supports RDI. It is not necessary for the interpretation to identify if the equipment supports RDI or E-RDI.
+
+## VII.2 VC-2, VC-12 and VC-11 paths
+
+As described in clause 9.3.2.1, bits 3, 4 and 8 of byte V5 are allocated to convey back to a VC-2, VC-12 or VC-11 trail termination source the status and performance of the complete trail. Bits 5 to 7 of byte K4 may be used to provide an enhanced remote defect indication with additional differentiation between the payload defect (PLM), server defects (AIS, LOP) and connectivity defects (TIM, UNEQ). The codes from Table VII.3 will be used.
+
+**Table VII.3 – V5 b8 and K4 (b5-b7) coding and triggers**
+
+| V5 b8 | K4 b5 | K4 b6 | K4 b7 | Meaning | Triggers |
+|--------------|--------------|--------------|--------------|---------------------------|------------------|
+| 0 | 0 | 0 | 1 | No remote defect | No remote defect |
+| 0 | 0 | 1 | 0 | E-RDI payload defect | PLM |
+| 1 | 1 | 0 | 1 | E-RDI server defect | AIS, LOP |
+| 1 | 1 | 1 | 0 | E-RDI connectivity defect | TIM, UNEQ |
+
+For the E-RDI codes, V5 b8 is set to the same value as K4 b5. In addition, for the E-RDI codes, bit 7 is set to the inverse of bit 6. Table VII.4 provides the E-RDI K4 (b5-b7) code interpretation.
+
+**Table VII.4 – V5 b8 and K4 (b5-b7) coding and E-RDI interpretation**
+
+| V5 b8 | K4 b5 | K4 b6 | K4 b7 | E-RDI Interpretation |
+|-------|-------|-------|-------|------------------------------|
+| 0 | 0 | 0 | 0 | No remote defect (Note 1) |
+| 0 | 0 | 0 | 1 | No remote defect |
+| 0 | 0 | 1 | 0 | E-RDI payload defect |
+| 0 | 0 | 1 | 1 | No remote defect (Note 2) |
+| 0 | 1 | 0 | 0 | No remote defect (Note 2) |
+| 0 | 1 | 0 | 1 | No remote defect (Note 2) |
+| 0 | 1 | 1 | 0 | No remote defect (Note 2) |
+| 0 | 1 | 1 | 1 | No remote defect (Note 1) |
+| 1 | 0 | 0 | 0 | E-RDI server defect (Note 1) |
+| 1 | 0 | 0 | 1 | E-RDI server defect (Note 2) |
+| 1 | 0 | 1 | 0 | E-RDI server defect (Note 2) |
+| 1 | 0 | 1 | 1 | E-RDI server defect (Note 2) |
+| 1 | 1 | 0 | 0 | E-RDI server defect (Note 2) |
+| 1 | 1 | 0 | 1 | E-RDI server defect |
+| 1 | 1 | 1 | 0 | E-RDI connectivity defect |
+| 1 | 1 | 1 | 1 | E-RDI server defect (Note 1) |
+
+NOTE 1 – These codes are generated by RDI supporting equipment and are interpreted by E-RDI supporting equipment as shown. For equipment supporting RDI (see clause 9.3.2.1) this code is triggered by the presence or absence of one of the following defects: AIS, LOP, TIM or UNEQ. Equipment conforming to an earlier version of this Recommendation may include PLM as a trigger condition. Note, for some national networks, this code is triggered only by an AIS or LOP defect.
+
+NOTE 2 – This code is not applicable to any known standards; it is included here for completeness.
+
+The E-RDI V5 b8 and K4 (b5-b7) coding interpretation provides for interworking with equipment which supports RDI. It is not necessary for the interpretation to identify if the equipment supports RDI or E-RDI.
+
+## Appendix VIII
+
+### Unexpected behaviour, dependence of TC monitoring on the incoming signal
+
+(This appendix does not form an integral part of this Recommendation)
+
+#### VIII.1 Entering AIS condition (in case of VC-3/VC-4/VC-4-Xc)
+
+Entering of the AIS condition is already critical for the VC-3/VC-4/VC-4-Xc cases; the issue here is the moment the signal is replaced by all-1s.
+
+Assume that an all-1s signal is inserted at the moment the B3 byte would be output by the adaptation sink function (MSn/Sn\_A\_Sk). As such, the TC\_TT\_So function will detect B3=all-1s and detects a number of BIP violations. While all-1s (AIS) insertion is accompanied by SSF=true, the N1[1-4] bits will be written with IncAIS code (1110) according to our standards. It is not possible to forward the IEC count at this moment. This will cause the far-end (TC\_TT\_Sk) to detect BIP-8 violations in B3 and IncAIS code (or IEC=0); and consequently an errored block will be declared. Also, in this example, in the next frame, BIP-8 violations will be detected with IEC=0, and another EB is declared. The reason is that the insertion of AIS started "in the middle of the VC-n frame" (as said above at the B3 byte location). If the AIS insertion had started at the J1 byte location, or behind the B3 location, only a single frame would have been impacted.
+
+Conclusion: at VC-3/VC-4/VC-4-Xc tandem connections it is possible to get 1 or 2 errored seconds being detected by the TC-TT\_Sk function at the end of the TC as a result of the insertion of AIS in front of the TC.
+
+#### VIII.2 Entering AIS condition (in case of VC-11/VC-12/VC-2)
+
+This problem does not occur at the VC-11/VC-12/VC-2 level; there is a real BIP-2 there, not an IEC.
+
+#### VIII.3 Recovery from a phase jump (valid for all VC-n)
+
+Causes of phase jumps at the ingress of a TC that have been identified so far are:
+
+- recovery from SSF condition (LOP, AIS);
+- establishment of a different path as a result of a cross-connect change, (e.g., from B→A to C→A, from UNEQ→A to B→A, from B→A to UNEQ→A);
+- recovery of a byte synchronous mapped 2 Mbit/s signal from AIS condition; VC-12 signal will follow the phase jump of the 2 Mbit/s signal (see Annex C/ETSI EN 300 417-4-1 V1.2.1);
+- protection switching caused by external commands, by revertive operation, by signal degrade SD.
+
+The phase jump of the VC-n is to be communicated towards the VC-n path termination sink via the VC-n signal itself and via the AU/TU pointer. As a consequence, such phase jump travels with different speed through the network: the VC-n bytes go much faster than the AU/TU pointer. A VC-n signal will experience a few bytes delay in each pointer processor, while the AU/TU pointer will experience between 0 and (a little bit more than) one frame delay in each pointer processor.
+
+Consequently, the TC termination sink (and VC termination sink) will be misaligned for some frames; the last pointer processor before the TC [VC] termination sink still uses the previous pointer, which is no longer aligned with the VC-n data after the phase jump. This means that the wrong bytes are used as POH and the BIP-n calculation will be wrong.
+
+## Appendix IX
+
+### **Forward error correction for STM-16**
+
+(This appendix does not form an integral part of this Recommendation)
+
+See Annex A with N equal to 16 and M equal to 1.
+
+Figure 9-5 gives the allocation of P1 and Q1 parity and status bytes for STM-16 signal.
+
+The 8-way bit interleaving in conjunction with BCH-3 provides 24-bit burst error correction capability per row for STM-16.
+
+## Appendix X
+
+### Performance of in-band FEC
+
+(This appendix does not form an integral part of this Recommendation)
+
+A criterion for the evaluation of the intrinsic correcting performance of the in-band BCH-3 code is the theoretical relationship between the line BER after the FEC error correction ( $BER_{Output}$ , $P_c$ ) and the line BER before the FEC error correction ( $BER_{Input}$ , $p$ ).
+
+For BCH codes, this criterion can be mathematically computed with the assumptions that errors occur independently from each other and that the decoder never fails (probability of incorrect decoding equals zero).
+
+$$P_c = \sum_{i=4}^N \frac{i}{N} \cdot \binom{N}{i} \cdot p^i \cdot (1-p)^{N-i}$$
+
+where $N = 4359$ .
+
+This theoretical intrinsic performance gain of the BCH-3 code is given in Figures X.1 and X.2 versus input BER and Q value respectively.
+
+
+
+| Input BER | Output (corrected) BER (Without FEC) | Output (corrected) BER (With BCH-3) |
+|-----------|--------------------------------------|-------------------------------------|
+| 1.E-12 | 1.E-12 | 1.E-12 |
+| 1.E-11 | 1.E-11 | 1.E-11 |
+| 1.E-10 | 1.E-10 | 1.E-30 |
+| 1.E-09 | 1.E-09 | 1.E-30 |
+| 1.E-08 | 1.E-08 | 1.E-30 |
+| 1.E-07 | 1.E-07 | 1.E-30 |
+| 1.E-06 | 1.E-06 | 1.E-30 |
+| 1.E-05 | 1.E-05 | 1.E-30 |
+| 1.E-04 | 1.E-04 | 1.E-30 |
+| 1.E-03 | 1.E-03 | 1.E-03 |
+
+Figure X.1: Theoretical output (corrected) BER versus input BER (BCH-3). The graph is a log-log plot showing two lines. The 'Without FEC' line is a straight diagonal line representing a 1:1 relationship. The 'With BCH-3' line is a blue line with square markers that follows the diagonal until an input BER of approximately 1.E-10, where it drops sharply to 1.E-30 and remains there until an input BER of 1.E-03, where it rises back to 1.E-03. The Y-axis is labeled 'Output (corrected) BER' and ranges from 1.E-30 to 1.E-03. The X-axis is labeled 'Input BER' and ranges from 1.E-12 to 1.E-03.
+
+G.707-Y.1322\_FX.1
+
+**Figure X.1 – Theoretical output (corrected) BER versus input BER (BCH-3)**
+
+
+
+| 20 Log (Q) | Uncoded BER | BCH-3 BER |
+|------------|-------------|-----------|
+| 10 | 1E-03 | 1E-03 |
+| 11 | 1E-04 | 1E-05 |
+| 12 | 1E-05 | 1E-08 |
+| 13 | 1E-06 | 1E-11 |
+| 14 | 1E-07 | 1E-16 |
+| 15 | 1E-08 | < 1E-18 |
+| 16 | 1E-09 | - |
+| 17 | 1E-12 | - |
+
+Figure X.2: Theoretical output (corrected) BER versus Q value (BCH-3). The graph shows two curves: 'Uncoded' (purple squares) and 'BCH-3' (green squares). The y-axis is BER on a logarithmic scale from 1E-02 to 1E-18. The x-axis is 20 Log (Q) from 10 to 17. The BCH-3 curve shows a steeper decline, indicating better performance.
+
+**Figure X.2 – Theoretical output (corrected) BER versus Q value (BCH-3)**
+
+The FEC function performance can also be evaluated through the coding gain. In this Recommendation the coding gain is evaluated by the difference in Q-value required for coded and uncoded operation to a specified level of communication performance.
+
+Figure X.2 gives performance curves to provide the coding gain in terms of Q-value. The Q-value in the horizontal axis is provided as $20 \log(Q)$ . For example, the gain at $10^{-12}$ is 3.8 dB. The coding gain in terms of $20 \log(Q)$ is equivalent to coding gain as represented by optical signal-to-noise ratio (OSNR) when the line system uses optical amplifiers.
+
+The FEC performance may be slightly improved when the FEC decoding is optionally performed in the regenerators as described in clause A.4.3. The performance gain of using FEC per span versus end-to-end is given in Figure X.3. Note that equally distributed raw BER among the spans are assumed. Normally BER are different span-by-span and the FEC performance is mainly given by the worst BER span. Therefore, the assumption of equal BER distribution gives the worst-case performance for the end-to-end decoding method.
+
+
+
+| 20 Log(Q) | Uncoded (3 spans) BER | Uncoded (1 span) BER | BCH-3 (span-by-span) BER | BCH-3 (1 span) BER |
+|-----------|-----------------------|----------------------|--------------------------|--------------------|
+| 10 | ~1E-03 | ~1E-03 | ~1E-03 | ~1E-03 |
+| 11 | ~1E-04 | ~1E-04 | ~1E-05 | ~1E-06 |
+| 12 | ~1E-05 | ~1E-06 | ~1E-07 | ~1E-09 |
+| 13 | ~1E-06 | ~1E-08 | ~1E-10 | ~1E-12 |
+| 14 | ~1E-07 | ~1E-10 | ~1E-13 | ~1E-16 |
+| 15 | ~1E-08 | ~1E-12 | ~1E-16 | < 1E-18 |
+| 16 | ~1E-09 | ~1E-14 | < 1E-18 | < 1E-18 |
+| 17 | ~1E-10 | ~1E-16 | < 1E-18 | < 1E-18 |
+
+Figure X.3: Comparison of end-to-end versus span-by-span FEC. The graph plots BER (Bit Error Rate) on a logarithmic scale from 1E-18 to 1E-02 against 20 Log(Q) from 10 to 17. It compares four scenarios: Uncoded (3 spans) represented by a red line with triangles, Uncoded (1 span) represented by a black line with squares, BCH-3 (span-by-span decode for 3 spans) represented by a black line with crosses, and BCH-3 (1 span) represented by a black line with green squares. The BCH-3 (1 span) curve shows the lowest BER, indicating the best performance, while the Uncoded (3 spans) curve shows the highest BER.
+
+**Figure X.3 – Comparison of end-to-end versus span-by-span FEC**
+
+For $BER_{Input}$ above $10^{-3}$ , the probability of incorrect decoding (an incorrect decoding occurs when the decoder attempts correction but acts incorrectly because the error pattern is beyond its ability to correct) is no longer negligible and makes the previous indication of $BER_{Output}$ inaccurate. In such cases, the $BER_{Output}$ versus $BER_{Input}$ curves are even located below the non-corrected curve in Figure X.1.
+
+## Appendix XI
+
+### Nominal justification ratios for asynchronous mapping of ODU1 into C-4-17 and ODU2 into C-4-68
+
+(This appendix does not form an integral part of this Recommendation)
+
+Appendix V/G.709/Y.1331 provides a relation between justification ratio and frequency offset, for the case of either CBRx or ODUk mapped into ODUn ( $n > k$ ). Following the notation there, let $\alpha$ be the justification ratio, i.e., the average number of justifications per C-4-Xc frame; also, as is done there, let positive $\alpha$ correspond to negative justification and negative $\alpha$ correspond to positive justification. Then $0 \leq \alpha \leq 45$ for mapping ODU1 into C-4-17 and $0 \leq \alpha \leq 180$ for mapping ODU2 into C-4-68. In addition, as is done in Appendix V/G.709/Y.1331, define the following notation:
+
+$N$ number of fixed stuff bytes in the C-4-Xc payload area
+
+$S$ nominal ODUk client rate (bytes/s)
+
+$T$ nominal C-4-Xc frame period(s)
+
+$y_c$ client (ODUk) frequency offset (fraction)
+
+$y_s$ server (C-4-Xc) frequency offset (fraction)
+
+$N_f$ average number of client bytes mapped into a C-4-Xc frame, for the particular frequency offsets (averaged over a large number of frames)
+
+(Note that in Appendix V/G.709/Y.1331, a quantity $p$ , representing the fraction of the payload area for the client in question, was defined. Here, $p = 1$ because there is only one client being mapped; i.e., there is no possible multiplexing as there was in Appendix V/G.709/Y.1331.)
+
+Then $N_f$ is given by:
+
+$$N_f = ST \frac{1 + y_c}{1 + y_s} \quad (\text{XI-1})$$
+
+For frequency offsets small compared to 1, this may be approximated
+
+$$N_f = ST(1 + y_c - y_s) \equiv ST\beta \quad (\text{XI-2})$$
+
+The quantity $\beta - 1$ is the net frequency offset due to client and server frequency offset.
+
+Now, the average number of client bytes mapped into a C-4-Xc frame is also equal to the total number of bytes in the payload area available to the client for data mapping (i.e., excluding any fixed stuff bytes ( $N$ )), plus the average number of bytes stuffed for this client over a very large number of frames. The latter is equal to the justification ratio. The former is equal to:
+
+#### Number of data bytes in payload area for ODU1 mapped into C-4-17
+
+(51 data bytes/subblock)(17 subblocks/block)(5 blocks/row)(9 rows/frame) = 39 015 data bytes/frame.
+
+#### Number of data bytes in payload area for ODU2 mapped into C-4-68
+
+(67 data bytes/subblock)(13 subblocks/block)(20 blocks/row)(9 rows/frame) = 156 780 data bytes/frame.
+
+Combining the above with Equations (XI-1) and (XI-2) produces:
+
+**ODU1 mapped into C-4-17**
+
+$$ST\beta = \alpha + 39015 \quad (\text{XI-3})$$
+
+**ODU2 mapped into C-4-68**
+
+$$ST\beta = \alpha + 156780 \quad (\text{XI-4})$$
+
+The nominal stuff ratio occurs when the frequency offsets are zero, i.e., when $\beta = 1$ . We now set $\beta = 1$ and solve for $\alpha$ for each case.
+
+**ODU1 mapped into C-4-17**
+
+The quantity $ST$ is the nominal number of ODU1 bytes in the nominal C-4-17 frame period. The latter is equal to 125 $\mu\text{s}$ . The former is equal to $(239/238)(2.48832 \times 10^9 \text{ bits/s})(1 \text{ byte}/8 \text{ bits})$ . Then
+
+$$\begin{aligned} \alpha &= (125 \times 10^{-6}) \left( \frac{239}{238} \right) \left( \frac{2.48832 \times 10^9}{8} \right) - 39015 \\ &= \left( \frac{239}{238} \right) (38880) - 39015 \\ &= \frac{(239)(38880) - (238)(39015)}{238} \\ &= \frac{6750}{238} \\ &= \frac{3375}{119} \\ &\approx 28.361345 \end{aligned} \quad (\text{XI-5})$$
+
+Then, on average, there are approximately 28.361345 negative justifications per C-4-17 frame out of a total possible 45. The long-run average fraction of justification opportunities for which there is a justification is equal to the above, divided by 45 (denote this quantity by $\alpha'$ )
+
+$$\alpha' = \frac{3375}{(119)(45)} = \frac{75}{119} \approx 0.630252100840 \quad (\text{XI-6})$$
+
+**ODU2 mapped into C-4-68**
+
+The quantity $ST$ is the nominal number of ODU2 bytes in the nominal C-4-68 frame period. The latter is equal to 125 $\mu\text{s}$ . The former is equal to $(239/237)(9.95328 \times 10^9 \text{ bits/s})(1 \text{ byte}/8 \text{ bits})$ . Then
+
+$$\begin{aligned} \alpha &= (125 \times 10^{-6}) \left( \frac{239}{237} \right) \left( \frac{9.95328 \times 10^9}{8} \right) - 156780 \\ &= \left( \frac{239}{237} \right) (155520) - 156780 \\ &= \frac{(239)(155520) - (237)(156780)}{237} \\ &= \frac{12420}{237} \\ &= \frac{4140}{79} \\ &\approx 52.405063 \end{aligned} \quad (\text{XI-7})$$
+
+Then, on average, there are approximately 52.405063 negative justifications per C-4-68 frame out of a total possible 180. The long-run average fraction of justification opportunities for which there is a justification is equal to the above, divided by 180 (denote this quantity by $\alpha'$ )
+
+$$\alpha' = \frac{4140}{(79)(180)} = \frac{23}{79} \approx 0.291139240506 \quad (\text{XI-8})$$
+
+## Appendix XII
+
+### Consideration on 10 Gbit/s Ethernet WAN clock accuracy
+
+(This appendix does not form an integral part of this Recommendation)
+
+In IEEE 802.3ae, IEEE has defined a 10 Gbit/s Ethernet WAN interface. This interface is basically an STM-64 with a VC-4-64c, and the Ethernet MAC mapped into the VC-4-64c using a 64B/66B coding (see Annex F).
+
+IEEE 802.3ae defines a clock accuracy of $\pm 20$ ppm for the 10 Gbit/s WAN signal, while a clock accuracy of $\pm 4.6$ ppm is required for SDH signals (except for the MS-AIS case). A VC-4-64c with $\pm 20$ ppm clock accuracy may result in excessive AU pointer justifications, which results in alarms if pointer adjustment monitoring is active.
+
+The IEEE 802.3ae interface can be supported by an SDH network if the clock accuracy is improved to meet the SDH $\pm 4.6$ ppm requirement. No other changes are required. Alternately, a clock alignment can be performed at the entrance to a SDH network. The 10 Gbit/s WAN signal is terminated in this case. The 64B/66B data stream is extracted and re-inserted into a new VC-4-64c (see Annex F) generated by the SDH equipment clock. Clock adaptation is performed by insertion or deletion of idle characters as defined in IEEE 802.3ae, section 49.2.4.7.
+
+## Appendix XIII
+
+### Example LCAS control packet CRC calculations
+
+(This appendix does not form an integral part of this Recommendation)
+
+#### XIII.1 Example of CRC-8 computation for LCAS and virtual concatenation carried in the H4 byte (i.e., VC-3-Xv and VC-4-Xv)
+
+| | H4[1-4] function | Most significant nibble H4[1-4] | | | | Least significant nibble H4[5-8] | | | | H4[5-8] value | |
+|--------------------|--------------------------------------------------|------------------------------------|-------|-------|-------|-------------------------------------|-------|-------|-------|------------------|---------------------|
+| | | bit 1 | bit 2 | bit 3 | bit 4 | bit 5 | bit 6 | bit 7 | bit 8 | | |
+| MF-2 counter = 201 | Member Status [72-79] | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 8 | LCAS control packet |
+| | | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 9 | |
+| | H4[1-3] = Reserved ('0') H4[4] = RS-Ack ('1') | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 10 | |
+| | Reserved ('0') | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | 11 | |
+| | | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 12 | |
+| | | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 13 | |
+| | Sequence number (19 = 13 HEX ) | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 14 | |
+| | | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 15 | |
+| | MF-2 counter (202 = CA HEX ) | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | |
+| | | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | |
+| MF-2 counter = 202 | Control word ('NORM') | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 2 | LCAS control packet |
+| | H4[1-3] = Reserved ('0') H4[4] = GID ('1') | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 3 | |
+| | Reserved ('0') | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 4 | |
+| | | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 5 | |
+| | CRC-8 of previous 14 H4[1-4] nibbles | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 6 | |
+| | | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 7 | |
+| | Member status [80-87] | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 8 | |
+| | | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 9 | |
+| | H4[1-3] = Reserved ('0') H4[4] = RS-Ack ('1') | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 10 | |
+| | Reserved ('0') | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | 11 | |
+| | | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 12 | |
+| | | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 13 | |
+| | Sequence number (19 = 13 HEX ) | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 14 | |
+| | | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 15 | |
+| MF-2 counter = 203 | MF-2 counter (203 = CB HEX ) | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | LCAS control packet |
+| | | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | |
+| | Control word ('NORM') | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 2 | |
+| | H4[1-3] = Reserved ('0') H4[4] = GID ('0') | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 3 | |
+| | Reserved | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 4 | |
+| | | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 5 | |
+| | CRC-8 of previous 14 H4[1-4] nibbles | 0 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 6 | |
+| | | 1 | 0 | 0 | 1 | 0 | 1 | 1 | 1 | 7 | |
+| | Member status [88-95] | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 8 | |
+| | | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 9 | |
+
+Figure XIII.1 – High order LCAS CRC calculation example
+
+**XIII.2 Example of CRC-3 computation for LCAS and virtual concatenation carried in bit 2 of the K4 byte (i.e., VC-2-Xv, VC-12-Xv and VC-11-Xv)**
+
+| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------|-----------------|--------------------------|-----|-----------------|--------|---------------|---|---|----|----|------------------------|----|----|----|----|----|--------|----|----|----|----|----|--------|----|----|----|----|----|----|----|----|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|
+| K4[1] 32-bit multiframe structure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | Signal label extension | | | | | 0 | Unused | | | | | 0 | Unused | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| K4[2] 32-bit multiframe structure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Multiframe-2 indicator | Sequence number | LCAS control information | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | CTRL | GID | Reserved "0000" | RS-Ack | Member status | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Example: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| MF-2 = 7, sequence number = 22, CTRL = NORM, member status of members 56-63 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 0 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| MF-2 = 8, sequence number = 22, CTRL = NORM, member status of members 0-7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| MF-2 = 9, sequence number = 22, CTRL = NORM, member status of members 8-15 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 0 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| MF-2 = 10, sequence number = 22, CTRL = NORM, member status of members 16-23 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 0 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+**Figure XIII.2 – Lower order LCAS control packet examples including the CRC-3**
+
+## Appendix XIV
+
+### Mapping serial data into a VCG
+
+(This appendix does not form an integral part of this Recommendation)
+
+
+
+Diagram illustrating VCAT mapping order. It shows a 3D perspective view of multiple Virtual Containers (VCs) stacked along the X-axis. Each VC is a 2D grid of columns (C) and rows (R). The mapping order is indicated by arrows: first along the X-axis (VC-n#1, VC-n#2, VC-n#3, VC-n#4, ..., VC-n#X), then within each VC, along the C-axis (columns 1 to c), and finally along the R-axis (rows 1 to R). The diagram is labeled G.707-Y.1322\_FIXIX.1.
+
+**Figure XIV.1 – VCAT mapping order**
+
+Serial data is mapped into a VCG on an octet-by-octet basis in the following order:
+
+- 1) Xth VC;
+- 2) Cth column;
+- 3) Rth row;
+
+i.e., octet #1 maps into VC #1, column #1, row #1
+
+octet #2 maps into VC #2, column #1, row #1
+
+octet #3 maps into VC #3, column #1, row #1
+
+.
+
+.
+
+octet #X maps into VC #X, column #1, row #1
+
+octet #(X+1) maps into VC #1, column #2, row #1
+
+octet #(X+2) maps into VC #2, column #2, row #1
+
+octet #(X+3) maps into VC #3, column #2, row #1
+
+.
+
+.
+
+octet #(X+X) maps into VC #X, column #2 of row #1
+
+etc., until $X \cdot C \cdot R$ octets are mapped, then the sequence is repeated.
+
+## Bibliography
+
+- [1] IEEE Standard 802.6 (1990), *Distributed queue dual bus (DQDB) subnetwork of a metropolitan area network (MAN)*.
+- [2] ISO/IEC 3309:1993, *Information technology – Telecommunications and information exchange between systems – High-level data link control (HDLC) procedures – Frame structure*.
+- [3] ISO 9314-1:1989, *Information processing systems – Fibre Distributed Data Interface (FDDI) – Part 1: Token Ring Physical Layer Protocol (PHY)*.
+- [4] ISO 9314-2:1989, *Information processing systems – Fibre Distributed Data Interface (FDDI) – Part 2: Token Ring Media Access Control (MAC)*.
+- [5] ISO/IEC 9314-3:1990, *Information processing systems – Fibre Distributed Data Interface (FDDI) – Part 3: Physical Layer Medium Dependent (PMD)*.
+- [6] ISO/IEC 9314-4:1999, *Information technology – Fibre Distributed Data Interface (FDDI) – Part 4: Single Mode Fibre Physical Layer Medium Dependent (SMF-PMD)*.
+- [7] ISO/IEC 9314-5:1995, *Information technology – Fibre Distributed Data Interface (FDDI) – Part 5: Hybrid Ring Control (HRC)*.
+- [8] ISO/IEC 9314-6:1998, *Information technology – Fibre Distributed Data Interface (FDDI) – Part 6: Station Management (SMT)*.
+- [9] ISO/IEC 9314-7:1998, *Information technology – Fibre Distributed Data Interface (FDDI) – Part 7: Physical Layer Protocol (PHY-2)*.
+- [10] ISO/IEC 9314-8:1998, *Information technology – Fibre Distributed Data Interface (FDDI) – Part 8: Media Access Control-2 (MAC-2)*.
+- [11] X3 Project X3T12/765-D (ISO CD 9314-12), *Fibre Distributed data interface (FDDI) – Token ring SONET physical layer mapping (SPM)*.
+- [12] IETF RFC 1661 (1994), *The Point-to-Point Protocol (PPP)*.
+- [13] IETF RFC 1662 (1994), *PPP in HDLC-like Framing*.
+- [14] IEEE Standard 802.3 (2002), *Information Technology – Telecommunication and Information Exchange Between Systems – LAN/MAN – Specific Requirements – Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications*.
+- [15] ITU-T Recommendation X.85/Y.1321 (2001), *IP over SDH using LAPS*.
+
+ITU-T Y-SERIES RECOMMENDATIONS
+
+GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS
+
+GLOBAL INFORMATION INFRASTRUCTURE
+
+| | |
+|-------------------------------------------|-------------|
+| General | Y.100–Y.199 |
+| Services, applications and middleware | Y.200–Y.299 |
+| Network aspects | Y.300–Y.399 |
+| Interfaces and protocols | Y.400–Y.499 |
+| Numbering, addressing and naming | Y.500–Y.599 |
+| Operation, administration and maintenance | Y.600–Y.699 |
+| Security | Y.700–Y.799 |
+| Performances | Y.800–Y.899 |
+
+INTERNET PROTOCOL ASPECTS
+
+| | |
+|--------------------------------------------------------------------|----------------------|
+| General | Y.1000–Y.1099 |
+| Services and applications | Y.1100–Y.1199 |
+| Architecture, access, network capabilities and resource management | Y.1200–Y.1299 |
+| Transport | Y.1300–Y.1399 |
+| Interworking | Y.1400–Y.1499 |
+| Quality of service and network performance | Y.1500–Y.1599 |
+| Signalling | Y.1600–Y.1699 |
+| Operation, administration and maintenance | Y.1700–Y.1799 |
+| Charging | Y.1800–Y.1899 |
+
+NEXT GENERATION NETWORKS
+
+| | |
+|-------------------------------------------------------------------|---------------|
+| Frameworks and functional architecture models | Y.2000–Y.2099 |
+| Quality of Service and performance | Y.2100–Y.2199 |
+| Service aspects: Service capabilities and service architecture | Y.2200–Y.2249 |
+| Service aspects: Interoperability of services and networks in NGN | Y.2250–Y.2299 |
+| Numbering, naming and addressing | Y.2300–Y.2399 |
+| Network management | Y.2400–Y.2499 |
+| Network control architectures and protocols | Y.2500–Y.2599 |
+| Security | Y.2700–Y.2799 |
+| Generalized mobility | Y.2800–Y.2899 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/G/T-REC-G.708-199907-I_PDF-E/raw.md b/marked/G/T-REC-G.708-199907-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..86790620018de91b7ec218d0f10332ef4ea95c11
--- /dev/null
+++ b/marked/G/T-REC-G.708-199907-I_PDF-E/raw.md
@@ -0,0 +1,694 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**G.708**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(06/99)
+
+SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
+DIGITAL SYSTEMS AND NETWORKS
+
+Digital transmission systems – Terminal equipments –
+General
+
+---
+
+**Sub STM-0 network node interface for the
+synchronous digital hierarchy (SDH)**
+
+ITU-T Recommendation G.708
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS**
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 |
+| INTERNATIONAL ANALOGUE CARRIER SYSTEM | |
+| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 |
+| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 |
+| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 |
+| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 |
+| TESTING EQUIPMENTS | |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.600–G.699 |
+| DIGITAL TRANSMISSION SYSTEMS | |
+| TERMINAL EQUIPMENTS | G.700–G.799 |
+| General | G.700–G.709 |
+| Coding of analogue signals by pulse code modulation | G.710–G.719 |
+| Coding of analogue signals by methods other than PCM | G.720–G.729 |
+| Principal characteristics of primary multiplex equipment | G.730–G.739 |
+| Principal characteristics of second order multiplex equipment | G.740–G.749 |
+| Principal characteristics of higher order multiplex equipment | G.750–G.759 |
+| Principal characteristics of transcoder and digital multiplication equipment | G.760–G.769 |
+| Operations, administration and maintenance features of transmission equipment | G.770–G.779 |
+| Principal characteristics of multiplexing equipment for the synchronous digital hierarchy | G.780–G.789 |
+| Other terminal equipment | G.790–G.799 |
+| DIGITAL NETWORKS | G.800–G.899 |
+| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 |
+
+For further details, please refer to ITU-T List of Recommendations.
+
+# **SUB STM-0 NETWORK NODE INTERFACE FOR THE SYNCHRONOUS DIGITAL HIERARCHY (SDH)**
+
+## **Summary**
+
+This Recommendation is an extension of Recommendation G.707. It provides the requirements for the sub STM-0 signals at the Network Node Interface of a synchronous digital network in terms of:
+
+- bit rates;
+- frames structures;
+- formats for mapping and multiplexing elements;
+- functionalities of the overheads.
+
+## **Source**
+
+ITU-T Recommendation G.708 was prepared by ITU-T Study Group 15 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 22nd of June 1999.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation the term *recognized operating agency (ROA)* includes any individual, company, corporation or governmental organization that operates a public correspondence service. The terms *Administration*, *ROA* and *public correspondence* are defined in the *Constitution of the ITU (Geneva, 1992)*.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, the ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 1999
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+###### Page
+
+| | | |
+|-------|----------------------------------------------------------------|----|
+| 1 | Scope..... | 1 |
+| 2 | References..... | 1 |
+| 3 | Definitions ..... | 1 |
+| 4 | sSTM interface rates ..... | 2 |
+| 5 | Transport formats..... | 3 |
+| 5.1 | Section overhead..... | 3 |
+| 5.2 | Scrambling ..... | 4 |
+| 5.3 | Frame structure for the sSTM-2n interface ..... | 5 |
+| 5.4 | $n \times$ TUG-2 payloads ..... | 5 |
+| 6 | Overhead functions ..... | 5 |
+| 6.1 | Interface layers..... | 5 |
+| 6.1.1 | Physical layer..... | 5 |
+| 6.1.2 | Section layer ..... | 5 |
+| 6.1.3 | Path layer ..... | 5 |
+| 6.2 | sSTM section overhead..... | 5 |
+| 6.2.1 | Regenerator section overhead..... | 5 |
+| 6.2.2 | Multiplex section overhead ..... | 6 |
+| 6.3 | sSTM maintenance signals ..... | 8 |
+| 6.3.1 | VC-n Path layer maintenance signals..... | 8 |
+| 6.3.2 | sSTM multiplex section remote defect indication (MS-RDI) ..... | 8 |
+| 6.3.3 | sSTM multiplex section alarm indication signal (MS-AIS)..... | 8 |
+| 7 | sSTM-2n interface APS ..... | 8 |
+| 8 | Multiplexing and numbering structure ..... | 8 |
+| 8.1 | Multiplexing structure ..... | 8 |
+| 8.2 | Numbering structure ..... | 10 |
+| | Annex A – Structures for radio-relay applications ..... | 11 |
+| A.1 | Scope..... | 11 |
+| A.2 | Interface rates..... | 11 |
+| A.3 | $k \times$ TU-12 payloads ..... | 11 |
+| A.4 | Media-dependent overhead functions..... | 11 |
+| A.5 | Multiplexing and numbering structure ..... | 11 |
+| A.5.1 | Multiplexing structure ..... | 11 |
+| A.5.2 | Numbering structure ..... | 12 |
+
+| | |
+|---------------------------------------------------------------------------------------------------------------------------------------|----|
+| Annex B – Frame format of a reduced functionality sSTM-11 for intra-station crossconnects of TU-12 using existing office wiring ..... | 13 |
+| Annex C – Numbering structure of TUs into sSTM frame formats ..... | 14 |
+| C.1 Numbering of TU-2s in a sSTM-2n..... | 14 |
+| C.2 Numbering of TU-12s in a sSTM-2n..... | 14 |
+| C.3 Numbering of TU-11s in a sSTM-2n..... | 14 |
+| C.4 Numbering of TU-12s in a sSTM-1k..... | 14 |
+
+# SUB STM-0 NETWORK NODE INTERFACE FOR THE SYNCHRONOUS DIGITAL HIERARCHY (SDH)
+
+(Geneva, 1999)
+
+# 1 Scope
+
+Network node interface (NNI) specifications are necessary to enable interconnection of synchronous digital hierarchy (SDH) network elements for the transport of payloads.
+
+Therefore, this Recommendation specifies:
+
+- the bit rates for sub STM-0 signals;
+ - the frame structures for sub STM-0 signals;
+ - the functionalities to be implemented in the different overheads of a sub STM-0 frame
+- at the NNI of a synchronous digital network.
+
+Annex A specifies bit rates, frame structures and overhead functionalities to be used at radio interfaces to ensure consistent transport of SDH payloads and overhead functionalities when low/medium capacity (sub STM-0) radio systems are used.
+
+# 2 References
+
+The following UIT-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
+
+- ITU-T Recommendation G.707 (1996), *Network node interface for the synchronous digital hierarchy (SDH)*.
+- ITU-T Recommendation G.861 (1996), *Principles and guidelines for the integration of satellite and radio systems in SDH transport networks*.
+
+This Recommendation is an extension of Recommendation G.707 (1996), *Network node interface for the synchronous digital hierarchy (SDH)*. It must be used in conjunction with Recommendation G.707 and thus all the relevant references in Recommendation G.707 are also references of this Recommendation.
+
+# 3 Definitions
+
+This Recommendation defines the following terms:
+
+**3.1 tributary unit group-2:** A 9-row by 12-column structure (108 bytes) that carries one or more TUs of the same size, as defined by Recommendation G.707.
+
+**3.2 sSTM-2n interface:** A SDH transmission interface which transports one or more TU Group(s)-2, as defined by Recommendation G.707, with Section overhead (9 bytes per frame). sSTM-2n interfaces may be defined for optical, electrical or radio transport technologies.
+
+The number (n) of TUG in sSTM-2n interfaces provided by this Recommendation is limited to n = 1, 2 and 4.
+
+**3.3 sSTM-1k interface:** A SDH transmission interface which transports one or more TU-12, as defined by Recommendation G.707, with Section overhead (9 bytes per frame). sSTM-1k interfaces are defined for radio transport technologies (sSTM-1k interfaces are defined in Annex A), and the sSTM-11 interface may also be used for reduced functionality, intra-station connections, as defined in Annex B.
+
+The number (k) of TU-12 in sSTM-1k interfaces provided by this Recommendation is limited to k = 1, 2, 4, 8 and 16.
+
+# 4 sSTM interface rates
+
+As illustrated in Figure 1, for the n = 1 case, the sSTM-2n frame consists of nine overhead bytes and 108 payload bytes (i.e. one column of overhead and 12 columns of payload). The frame duration is 125 µs, for a resulting signal rate of 7.488 Mbit/s. For the other rates, see Table 1.
+
+
+
+| | | | | | | | | | | | | | |
+|---|---|-----------------------|------------------------------|---|---|-------|-------|---|---|----|----|----|----|
+| | 1 | An Framing | Vn | → | → | ..... | ..... | | | | | | |
+| R | 2 | (*) | TUG-2 9 rows × 12 columns | | | | | | | | | | |
+| S | 3 | (*) | | | | | | | | | | | |
+| O | 4 | D1 Data | | | | | | | | | | | |
+| H | 5 | (*) | | | | | | | | | | | |
+| | 6 | 4Ch: (#), J0,Z1,Z2 | | | | | | | | | | | |
+| M | 7 | 4Ch: S1, K1,Z3,Z4 | | | | | | | | | | | |
+| S | 8 | B2 BIP-8 | | | | | | | | | | | |
+| H | 9 | M1 Status | | | | | | | | | | | |
+| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 |
+
+(\*) Media-dependent bytes
+ (#) Media-specific error indicator byte (see 6.2.1.4)
+
+T1530310-99
+
+Diagram of sSTM interface frame format showing 13 columns and 9 rows of overhead and payload. Columns 1-9 are overhead, columns 10-13 are payload. Rows 1-9 are defined in the diagram. Payload is labeled TUG-2, 9 rows x 12 columns.
+
+**Figure 1/G.708 – sSTM interface frame format**
+
+**Table 1/G.708 – Interface rates for sSTM systems**
+
+| TU structure | # | Overhead | Payload envelope | Bit rate |
+|---------------------|----------|-----------------|-------------------------|-----------------|
+| TUG 2 | 1 | 9 bytes | 108 | 7.488 Mbit/s |
+| | 2 | | 216 | 14.400 Mbit/s |
+| | 4 | | 432 | 28.224 Mbit/s |
+| TU12 | 1 | 9 bytes | 36 | 2.88 Mbit/s |
+| | 2 | | 72 | 5.184 Mbit/s |
+| | 4 | | 144 | 9.792 Mbit/s |
+| | 8 | | 288 | 19.008 Mbit/s |
+| | 16 | | 576 | 37.44 Mbit/s |
+
+# **5 Transport formats**
+
+## **5.1 Section overhead**
+
+The sSTM interface has an associated Section overhead of 9 bytes. The location of the Section overhead bytes within the sSTM frame is shown in Figure 1.
+
+Some of these bytes are further subdivided into separated 16 kbit/s transmission capacity, using the multiframe structure, as shown in Figure 2.
+
+The detailed definitions and functions of these nine overhead bytes are described in clause 6.
+
+(Example for the sSTM-21 case)
+
+
+
+| | | | |
+|--------|-----|-------|--------|
+| 0 μsec | A1 | V1s → | |
+| | (*) | | |
+| | (*) | | |
+| | D1 | | |
+| | (*) | | |
+| | (#) | | |
+| | S1 | | |
+| | B2 | | |
+| | M1 | | |
+| | A2 | V2s → | 125 μs |
+| (*) | | | |
+| (*) | | | |
+| D1 | | | |
+| (*) | | | |
+| J0 | | | |
+| K1 | | | |
+| B2 | | | |
+| M1 | | | |
+| | A3 | V3s → | 250 μs |
+| (*) | | | |
+| (*) | | | |
+| D1 | | | |
+| (*) | | | |
+| Z1 | | | |
+| Z3 | | | |
+| B2 | | | |
+| M1 | | | |
+| | A4 | V4s → | 375 μs |
+| (*) | | | |
+| (*) | | | |
+| D1 | | | |
+| (*) | | | |
+| Z2 | | | |
+| Z4 | | | |
+| B2 | | | |
+| M1 | | | |
+| | | | 500 μs |
+
+Diagram of sSTM multiframe format showing byte sequences A1, (\*), (\*), D1, (\*), (#), S1, B2, M1, followed by V1s, then V2s, V3s, and V4s with their respective mapping areas and timing markers at 0, 125, 250, 375, and 500 microseconds.
+
+(\*) Media-dependent bytes
+
+(#) Media-specific error detection code byte (see 6.2.1.4)
+
+**Figure 2/G.708 – sSTM multiframe format**
+
+## 5.2 Scrambling
+
+A frame synchronous scrambler equal to that recommended in Recommendation G.707 for STM-N frame should be used to prevent long sequences of "1"s or "0"s. The frame alignment byte An should be excluded from the scrambling. The scrambler shall be reset to "11111111" on the most significant bit of the byte following the An.
+
+## **5.3 Frame structure for the sSTM-2n interface**
+
+The sSTM-2n interface frame structure, for the $N = 1$ case as illustrated in Figure 1, consists of thirteen columns and nine rows of 8-bit bytes for a total of 117 bytes (936 bits). The frame duration is 125 $\mu\text{s}$ (i.e. 8000 frames per second), which results in a bit rate of 7.488 Mbit/s. As with the STM-1 signal, the order of transmission bytes is row by row, from left to right. In each byte, the most significant bit is transmitted first.
+
+## **5.4 $n \times$ TUG-2 payloads**
+
+The payload portion of the sSTM-2n interface follows the TUG structure and interleaving format of the STM-1 signal described in Recommendation G.707. Specifically, the TUG payload may consist of four TU-11s, three TU-12s, or a single TU-2.
+
+# **6 Overhead functions**
+
+## **6.1 Interface layers**
+
+### **6.1.1 Physical layer**
+
+Physical layer specifications are defined in other Recommendations.
+
+### **6.1.2 Section layer**
+
+The Section overhead deals with the reliable transport of the TU or sSTM frame and overhead across the physical medium.
+
+### **6.1.3 Path layer**
+
+The VC Path layer for the sSTM interface is specified in Recommendation G.707.
+
+## **6.2 sSTM section overhead**
+
+The Section overhead is subdivided into regenerator section overhead (RSOH) and multiplex section overhead (MSOH) as shown in Figure 1.
+
+Any bytes or bits in the SOH defined as reserved or not required should be coded as all "0" and receivers should be able to ignore their content.
+
+### **6.2.1 Regenerator section overhead**
+
+#### **6.2.1.1 Framing and multiframe indicator (An)**
+
+This byte combines the framing and multiframe alignment functions for the sSTM signal. The byte values alternate between F6, 28, F7, and 29 Hex (11110110, 00101000, 11110111, and 00101001) as shown in Figure 3. The multiframe alignment function is required to identify the phase of the V1-V4 bytes of the TUs. The first byte transmitted directly after A1 is the V1 byte associated with the first TU; similarly the V2, V3 and V4 bytes, associated with the first TU, are transmitted directly after A2, A3 and A4 bytes, respectively.
+
+NOTE – The byte An values in sSTM frames 1 and 2 are the same as the STM-1 byte A1 and A2 values, respectively. The seven MSBs of the byte alternate between the two patterns, and the LSB is used to provide the additional multiframe information.
+
+| Frame | An | Value | Hex | V byte |
+|-------|----|----------|-----|--------|
+| 1 | A1 | 11110110 | F6 | V1 |
+| 2 | A2 | 00101000 | 28 | V2 |
+| 3 | A3 | 11110111 | F7 | V3 |
+| 4 | A4 | 00101001 | 29 | V4 |
+
+**Figure 3/G.708 – Framing pattern for the sSTM interface (byte An)**
+
+#### **6.2.1.2 Section trace (J0)**
+
+This byte is used for the same purpose and with the same codes provided for J0 byte in Recommendation G.707.
+
+#### **6.2.1.3 Data communications channel (D1)**
+
+A 64 kbit/s channel is defined using byte D1 as a section data communication channel (DCC).
+
+#### **6.2.1.4 Media-dependent error detection code**
+
+This byte is reserved for implementation-dependent methods of error detection for operation and maintenance purposes.
+
+#### **6.2.1.5 Growth (Z1, Z2)**
+
+These bytes are reserved for overhead functions.
+
+#### **6.2.1.6 Media-dependent bytes**
+
+These bytes are reserved for media-specific use.
+
+### **6.2.2 Multiplex section overhead**
+
+#### **6.2.2.1 Multiplex section status (M1)**
+
+This byte provides a combination of performance status, and maintenance functions. The partitioning of the byte is shown in Figure 4. The four-bit REI field (bits 1-4) shall be set to convey the count of interleaved bit blocks that have been detected in error by the BIP-8 in the range of [0, 8] received in the B2 byte from the opposite direction of transmission, thus allowing the terminals at each end of the span to monitor the section error performance with the same precision. The value in these bits shall be interpreted as shown in Table 2. Remote defects are indicated with MS-RDI in bit 5. The code 7 (111) in the three bits 6 to 8 is used for MS-AIS indication; the other codes (0 to 6) are reserved for future standardization.
+
+| MS-REI | | | | MS-RDI | MS-AIS & Reserved | | |
+|--------|---|---|---|--------|-------------------|---|---|
+| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
+
+**Figure 4/G.708 – sSTM section status byte (M1)**
+
+**Table 2/G.708 – M1 (bits 1 to 4) interpretation**
+
+| M1[1-4] code, bits 1234 | Interpretation |
+|-------------------------|------------------|
+| 0000 | 0 BIP violations |
+| 0001 | 1 BIP violation |
+| 0010 | 2 BIP violations |
+| 0011 | 3 BIP violations |
+| 0100 | 4 BIP violations |
+| 0101 | 5 BIP violations |
+| 0101 | 6 BIP violations |
+| 0111 | 7 BIP violations |
+| 1000 | 8 BIP violations |
+| 1001 | 0 BIP violations |
+| 1010 | 0 BIP violations |
+| . | . |
+| . | . |
+| . | . |
+| 1111 | 0 BIP violations |
+
+#### 6.2.2.2 Multiplex Section BIP-8
+
+Byte B2 is allocated for Multiplex Section error monitoring function. This function shall be a Bit Interleaved Parity-8 code using even parity. The Section BIP-8 is calculated over all payload bytes and excludes all 9 Section overhead bytes.
+
+#### 6.2.2.3 Synchronization status message (S1)
+
+Bits 5-8 of the S1 byte are for synchronization status messages. These messages provide an indication of the quality level of the synchronization source of the SDH signal. Synchronization messages that are currently defined, and their bit coding, are listed Recommendation G.707. Bits 1-4 of byte S1 are reserved for future use. The byte subdivision is shown in Figure 5.
+
+| Reserved | | | | Synchronization quality | | | |
+|----------|---|---|---|-------------------------|---|---|---|
+| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
+
+**Figure 5/G.708 – Synchronization status message (S1)**
+
+#### 6.2.2.4 APS channel (K1)
+
+This byte is reserved for those applications where 1+1 multiplex section bidirectional protection is required.
+
+#### 6.2.2.5 Growth (Z3, Z4)
+
+These bytes are reserved for overhead functions that may be defined in the future. The receiver is required to be able to ignore the values contained in these bytes.
+
+## **6.3 sSTM maintenance signals**
+
+### **6.3.1 VC-n Path layer maintenance signals**
+
+VC-n Path layer maintenance signals are defined in Recommendation G.707.
+
+### **6.3.2 sSTM multiplex section remote defect indication (MS-RDI)**
+
+MS-RDI shall be generated by setting bit 5 of the M1 byte to one, and shall be deactivated by setting bit 5 of the M1 byte to zero.
+
+NOTE – If MS-RDI is active, the four-bit REI field is to operate as normal if a valid frame is received; otherwise it is to be set to 0000.
+
+### **6.3.3 sSTM multiplex section alarm indication signal (MS-AIS)**
+
+MS-AIS is set by using a valid RSOH and placing all 1s in the MSOH and payload. MS-AIS is detected by all 1s in bits 6-8 of the M1 byte
+
+# **7 sSTM-2n interface APS**
+
+The sSTM-2n automatic protection switching scheme may support both 1+1 bidirectional and unidirectional switching, hence there is need for overhead (K1 byte) to coordinate switch action for the bidirectional case.
+
+# **8 Multiplexing and numbering structure**
+
+## **8.1 Multiplexing structure**
+
+Figure 6 shows, within the general G.707 multiplexing scheme, the additional multiplexing routes provided by this Recommendation.
+
+Multiplexing routes of specific sSTM-1k and sSTM-2n sSTM (of order $k = 1, 2, \dots, 16$ or $n = 1, 2, 4$ ).
+
+The actual mapping of TUG-2s into the sSTM-2n is shown in Figure 7 while that of TU-12s into the sSTM-1k is shown in Annex A.
+
+
+
+The diagram illustrates the SDH multiplexing hierarchy including sub-STM (sSTM) formats. The flow generally moves from right (containers) to left (Synchronous Transport Modules).
+
+- High-order path:** C-4-16c → VC-4-16c → AU-4-16c → AUG16 → AUG64 → STM-64. Also AUG16 → STM-16.
+- Medium-order path:** C-4-4c → VC-4-4c → AU-4-4c → AUG4 → AUG16. Also AUG4 → STM-4.
+- Standard path:** C-4 → VC-4 → AU-4 → AUG1 → AUG4. Also AUG1 → STM-1.
+- Tributary paths:**
+ - C-3 → VC-3 → AU-3 → STM-0.
+ - C-3 → VC-3 → TU-3 → TUG-3 → VC-4.
+ - C-2/C-12/C-11 → VC-2/VC-12/VC-11 → TU-2/TU-12/TU-11 → TUG-2 → TUG-3 or VC-3.
+- sSTM paths:**
+ - sSTM-2n (\*\*) → TUG-2n (\*\*) → TUG-2.
+ - sSTM-1k (\*) → TUG-1k (\*) → TUG-2.
+
+**Legend:**
+
+Pointer processing
+—→ Multiplexing
+ sSTM-1k, 2n multiplexing routes
+····> Aligning
+——> Mapping
+
+**Notes:**
+(\*) k = 1, 2, 4, 8 and 16
+(\*\*) n = 1, 2 and 4
+C-n Container-n
+
+T1530320-99
+
+Diagram showing the integration of sSTM formats into the G.707 multiplexing structure. It illustrates the hierarchy from STM-64 down to sSTM-1k and sSTM-2n, showing multiplexing stages (AUG, TUG) and pointer processing blocks (AU, TU). Shaded rectangle Thick arrow
+
+**Figure 6/G.708 – Integration of sSTM formats into the G.707 multiplexing structure**
+
+
+
+# ANNEX A
+
+## Structures for radio-relay applications
+
+## A.1 Scope
+
+This annex should be used in conjunction with Recommendation G.861, *Principles and guidelines for the integration of satellite and radio systems in SDH transport networks*. This annex specifies SDH bit rates, frame structures and media-specific overhead functionalities for use in low/medium capacity radio systems.
+
+## A.2 Interface rates
+
+Radio spectral allocations vary in different regions of the world requiring a wider range of bit rates in order to efficiently utilize the spectrum. Some areas of the world use frequency allocations based on increments of 5 MHz, typically for transmission of T1-based (1544 kbit/s) payload rates. For these areas, the bit rates and frame structures specified in the main body of this Recommendation are suitable, i.e. sSTM-2n. Some areas of the world use frequency allocations based on 7 MHz increments, typically for transmission of E1-based (2048 kbit/s) payload rates. For these areas, sub STM-0 radio systems need to use the sSTM-1k rates, with $k = 1, 2, 4, 8$ and 16 in order to maintain comparable spectrum efficiency. The complete list of rates is in Table 1.
+
+## A.3 $k \times$ TU-12 payloads
+
+The payload portion of the sSTM-1k interface is derived by the TUG structure and interleaving format of the STM-1 signal described in Recommendation G.707. Specifically, the $k \times$ TU-12 payload may consist of one, two, four, eight or sixteen TU-12.
+
+## A.4 Media-dependent overhead functions
+
+Bytes 2, 3 and 5 of RSOH may be used for radio specific uses.
+
+They can be used for system-specific control signals [examples are adaptive transmit power control (ATPC) to reduce nodal interference] and Early-Warning Switch information (to activate in the terminals 1+1 a real-time "hitless" protection for propagation-induced degradation in the RS in between); other examples are reported in ITU-R Recommendation F.751.
+
+Alternatively they can be used for other optional SDH functionalities such as E1 and F1 or as an additional D2 byte to be combined with D1 to create up to 128 kbit/s channel where subSTM-0 subnetwork complexity require more capacity for management protocols transmission.
+
+## A.5 Multiplexing and numbering structure
+
+### A.5.1 Multiplexing structure
+
+The mapping of TU-12s into sSTM-1k is shown in Figure A.1.
+
+
+
+Diagram showing the arrangement of k x TU-12s multiplexed into a sSTM-1k. At the top, four TU-12 units are shown, labeled (1) TU-12, (2) TU-12, (3) TU-12, and (k) TU-12. Each TU-12 is a vertical rectangle divided into four columns. Dashed lines connect the columns of these TU-12s to a large horizontal rectangle labeled sSTM-1k. The sSTM-1k rectangle is divided into three parts: a left section labeled 'sSTM-1k SOH' with columns numbered 1, 2, 3, ..., k; a large central section; and a right section with columns numbered 1, 2, 3, ..., k. Below the left section, the columns are numbered 1, 2, 3, ..., k, and the total number of columns is labeled k + 1. Below the right section, the total number of columns is labeled (k x 4) + 1. The text 'T1530340-99' is in the bottom right corner.
+
+**Figure A.1/G.708 – Arrangement of $k \times$ TU-12s multiplexed into a sSTM-1k
+( $k = 1, 2, 4, 8$ and $16$ )**
+
+### **A.5.2 Numbering structure**
+
+The numbering structure of the TU-12s in the sSTM-1k formats is described in Annex C.
+
+# ANNEX B
+
+## Frame format of a reduced functionality sSTM-11 for intra-station crossconnects of TU-12 using existing office wiring
+
+The sSTM-11 format of Annex A may also be used to support in-station cross-connects using existing 2048 kbit/s wiring. For this application, the only overhead functionality that is necessary is the An, J0, B2, M1 and S1 as described in the main body of this specification (see Figure B.1). Byte D1 may optionally be used.
+
+
+
+| | | | |
+|------|--------------|-------------------------------------------------|--------|
+| 0 μs | A1 | V1 TU-12 Mapping area (four columns) | 125 μs |
+| | NR | | |
+| | NR | | |
+| | D1(optional) | | |
+| | NR | | |
+| | NR | | |
+| | S1 | | |
+| | B2 | | |
+| | M1 | | |
+| | A2 | V2 TU-12 Mapping area (four columns) | 250 μs |
+| | NR | | |
+| | NR | | |
+| | D1(optional) | | |
+| | NR | | |
+| | J0 | | |
+| | NR | | |
+| | B2 | | |
+| | M1 | | |
+| | A3 | V3 TU-12 Mapping area (four columns) | 375 μs |
+| | NR | | |
+| | NR | | |
+| | D1(optional) | | |
+| | NR | | |
+| | NR | | |
+| | NR | | |
+| | B2 | | |
+| | M1 | | |
+| | A4 | V4 TU-12 Mapping area (four columns) | 500 μs |
+| | NR | | |
+| | NR | | |
+| | D1(optional) | | |
+| | NR | | |
+| | NR | | |
+| | NR | | |
+| | B2 | | |
+| | M1 | | |
+
+NR Not required
+
+**Figure B.1/G.708 – Frame format for reduced functionality TU-12 interface**
+
+# ANNEX C
+
+## Numbering structure of TUs into sSTM frame formats
+
+## C.1 Numbering of TU-2s in a sSTM-2n
+
+As shown in Figure C.1 a), a sSTM-2n can comprise "n" TUG-2s which shall be numbered from #1 to #n (n = 1, 2 and 4). Each TUG-2 can comprise a TU-2.
+
+Thus, any TU-2 can be allocated a two-figure address in the form #L, #M, where L designates the TUG-2 number (1 to n) and M is always 0. The location of the columns in the sSTM-2n occupied by TU-2(L, 0) is given by the formula:
+
+$$\text{xth column} = 2 + [L - 1] + n \times [x - 1], \text{ for } x = 1 \text{ to } 12$$
+
+Thus, TU-2(1, 0) resides in columns 2, 4, ... and 24 of the sSTM-22, and TU-2(2, 0) resides in columns 3, 7, ..., and 47 of the sSTM-24.
+
+## C.2 Numbering of TU-12s in a sSTM-2n
+
+As shown in Figure C.1 b), each TUG-2 can comprise three TU-12s which shall be numbered #1 to #3.
+
+Thus, any TU-12 can be allocated a two-figure address in the form #L, #M, where L designates the TUG-2 number (1 to n) and M designates the TU-12 number (1 to 3). The location of the columns in the sSTM-2n occupied by TU-12(L, M) is given by the formula:
+
+$$\text{xth column} = 2 + [L - 1] + n \times [M - 1] + 3n \times [x - 1], \text{ for } x = 1 \text{ to } 4$$
+
+Thus, TU-12(1, 1) resides in columns 2, 8, 14 and 20 of the sSTM-22 and TU-12(3, 3) resides in columns 12, 24, 36 and 48 of the sSTM-24.
+
+## C.3 Numbering of TU-11s in a sSTM-2n
+
+As shown in Figure C.1 c), each TUG-2 can comprise four TU-11s which shall be numbered #1 to #4.
+
+Thus, any TU-11 can be allocated a two-figure address in the form #L, #M, where L designates the TUG-2 number (1 to n) and M designates the TU-11 number (1 to 4). The location of the columns in the VC-3 occupied by TU-11(L, M) is given by the formula:
+
+$$\text{xth column} = 2 + [L - 1] + n \times [M - 1] + 4n \times [x - 1], \text{ for } x = 1 \text{ to } 3$$
+
+Thus, TU-11(1, 1) resides in columns 2, 10 and 18 of the sSTM-22, and TU-11(3, 4) resides in columns 16, 32 and 48 of the sSTM-24.
+
+## C.4 Numbering of TU-12s in a sSTM-1k
+
+As shown in Figure C.1 d), each sSTM-1k can comprise k TU-12s which shall be numbered #1 to #k.
+
+Thus, any TU-12 can be allocated a figure address in the form #M, where M designates the TU-12 number (1 to k). The location of the columns of any TU-12 in the sSTM-1k is given by the formula:
+
+$$\text{xth column} = 2 + [M - 1] + k \times [x - 1], \text{ for } x = 1 \text{ to } 4$$
+
+Thus, TU-12(1) resides in columns 2, 10, 18 and 26 of the sSTM-18, and TU-12(4) resides in columns 5, 9, 13 and 17 of the sSTM-14.
+
+NOTE – The time-slot number contained in Figure C.1 should not be interpreted as the tributary port number.
+
+An external tributary signal may be assigned to a particular payload capacity using a connection function.
+
+For example, at the VC-12 level mapped into sSTM-2n assigned to a specific coupling of L(TUG-2) and M(TU-1) address:
+
+| Tributary number | TU-12(L, M) |
+|-------------------------|--------------------|
+| Tributary #1 | TU-12(1, 1) |
+| Tributary #2 | TU-12(1, 2) |
+| Tributary #3 | TU-12(1, 3) |
+| Tributary #4 | TU-12(2, 1) |
+| ... | |
+| Tributary #3 × n | TU-12(n, 3) |
+
+while, when mapped into sSTM-1k, a single address M #1 to #k is sufficient.
+
+
+
+Diagram a) TU-2 numbering scheme into sSTM-2n. It shows a mapping from TU-2 time slots to sSTM-2n columns. The left table lists TU-2 slots 1, 2, 3, ..., n+1, n+2, ..., 2n+1, 2n+2. The right table lists sSTM-2n columns 1, 2, 3, ..., 12n+1. Rows are labeled S, H, O, M. The mapping shows TU-2 slot 1 maps to sSTM-2n column 1, TU-2 slot 2 maps to sSTM-2n column 2, etc. Address (L = 1, 2, 4) and Time-slot number are indicated.
+
+a) TU-2 numbering scheme into sSTM-2n
+
+
+
+Diagram b) TU-12 numbering scheme into sSTM-2n. It shows a mapping from TU-12 time slots to sSTM-2n columns. The left table lists TU-12 slots 1, 2, 3, ..., n+1, n+2, ..., 2n+1, 2n+2. The right table lists sSTM-2n columns 1, 2, 3, ..., 12n+1. Rows are labeled S, H, O, M. The mapping shows TU-12 slot 1 maps to sSTM-2n column 1, TU-12 slot 2 maps to sSTM-2n column 2, etc. Address (L = 1, 2, 4) and Time-slot number are indicated.
+
+b) TU-12 numbering scheme into sSTM-2n
+
+
+
+Diagram c) TU-11 numbering scheme into sSTM-2n. It shows a mapping from TU-11 time slots to sSTM-2n columns. The left table lists TU-11 slots 1, 2, 3, ..., n+1, n+2, ..., 2n+1, 2n+2. The right table lists sSTM-2n columns 1, 2, 3, ..., 12n+1. Rows are labeled S, H, O, M. The mapping shows TU-11 slot 1 maps to sSTM-2n column 1, TU-11 slot 2 maps to sSTM-2n column 2, etc. Address (L = 1, 2, 4) and Time-slot number are indicated.
+
+c) TU-11 numbering scheme into sSTM-2n
+
+
+
+Diagram d) TU-12 numbering scheme into sSTM-1k. It shows a mapping from TU-12 time slots to sSTM-1k columns. The left table lists TU-12 slots 1, 2, 3, ..., k+1, k+2, ..., 2k+1, 2k+2. The right table lists sSTM-1k columns 1, 2, 3, ..., 4k+1. Rows are labeled S, H, O, M. The mapping shows TU-12 slot 1 maps to sSTM-1k column 1, TU-12 slot 2 maps to sSTM-1k column 2, etc. Address (M = 1, 2, 4, 8, 16) and Time-slot number are indicated. Reference T1530350-99 is shown.
+
+d) TU-12 numbering scheme into sSTM-1k
+
+Figure C.1/G.708 – TU-2, TU-12 and TU-11 numbering scheme within a sSTM-2n and a sSTM-1k
+
+# ITU-T RECOMMENDATIONS SERIES
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of the ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/G/T-REC-G.709.4-202003-I_PDF-E/raw.md b/marked/G/T-REC-G.709.4-202003-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..5513324b8544c91dd215af8142db1053293f1100
--- /dev/null
+++ b/marked/G/T-REC-G.709.4-202003-I_PDF-E/raw.md
@@ -0,0 +1,782 @@
+
+
+**ITU-T**
+
+**G.709/Y.1331.4**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(03/2020)
+
+SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
+DIGITAL SYSTEMS AND NETWORKS
+
+Digital terminal equipments – General
+
+SERIES Y: GLOBAL INFORMATION
+INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS,
+NEXT-GENERATION NETWORKS, INTERNET OF
+THINGS AND SMART CITIES
+
+Internet protocol aspects – Transport
+
+**OTU25 and OTU50 short-reach interfaces**
+
+Recommendation ITU-T G.709/Y.1331.4
+
+# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS**
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 |
+| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 |
+| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 |
+| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 |
+| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 |
+| TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS | G.600–G.699 |
+| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 |
+| General | G.700–G.709 |
+| Coding of voice and audio signals | G.710–G.729 |
+| Principal characteristics of primary multiplex equipment | G.730–G.739 |
+| Principal characteristics of second order multiplex equipment | G.740–G.749 |
+| Principal characteristics of higher order multiplex equipment | G.750–G.759 |
+| Principal characteristics of transcoder and digital multiplication equipment | G.760–G.769 |
+| Operations, administration and maintenance features of transmission equipment | G.770–G.779 |
+| Principal characteristics of multiplexing equipment for the synchronous digital hierarchy | G.780–G.789 |
+| Other terminal equipment | G.790–G.799 |
+| DIGITAL NETWORKS | G.800–G.899 |
+| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 |
+| MULTIMEDIA QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER-RELATED ASPECTS | G.1000–G.1999 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.6000–G.6999 |
+| DATA OVER TRANSPORT – GENERIC ASPECTS | G.7000–G.7999 |
+| PACKET OVER TRANSPORT ASPECTS | G.8000–G.8999 |
+| ACCESS NETWORKS | G.9000–G.9999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## Recommendation ITU-T G.709.4/Y.1331.4
+
+## OTU25 and OTU50 short-reach interfaces
+
+# Summary
+
+Recommendation ITU-T G.709.4/Y.1331.4 specifies an interface for an OTU25 and OTU50 short-reach interconnect application.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|------------------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T G.709.4/Y.1331.4 | 2020-03-15 | 15 | 11.1002/1000/14201 |
+
+## Keywords
+
+OTN, OTU25, OTU50, Reed-Solomon FEC, short reach.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2020
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+###### Page
+
+| | | |
+|-----|-------------------------------------------------------------------------------------------------|----|
+| 1 | Scope ..... | 1 |
+| 2 | References..... | 1 |
+| 3 | Definitions ..... | 1 |
+| 3.1 | Terms defined elsewhere ..... | 1 |
+| 3.2 | Terms defined in this Recommendation..... | 2 |
+| 4 | Abbreviations and acronyms ..... | 2 |
+| 5 | Conventions ..... | 2 |
+| 6 | Introduction ..... | 3 |
+| 7 | Structure..... | 3 |
+| 7.1 | Basic signal structure..... | 3 |
+| 8 | OTU25-RS interface..... | 5 |
+| 8.1 | Frame structure ..... | 5 |
+| 8.2 | Bit rate and frame period ..... | 6 |
+| 8.3 | Overhead..... | 6 |
+| 8.4 | Scrambling..... | 7 |
+| 8.5 | Forward error correction..... | 7 |
+| 8.6 | Interface format ..... | 7 |
+| 9 | OTU50-RS interface..... | 7 |
+| 9.1 | Frame structure ..... | 7 |
+| 9.2 | Bit rate and frame period ..... | 8 |
+| 9.3 | Overhead..... | 8 |
+| 9.4 | Scrambling..... | 9 |
+| 9.5 | Forward error correction..... | 9 |
+| 9.6 | Interface format ..... | 10 |
+| 10 | Mapping OTU25 and OTU50 signal into OTU25-RS and OTU50-RS ..... | 10 |
+| | Annex A – Forward error correction for OTU-RS using 10-bit interleaved RS(544,514) codecs ..... | 11 |
+| | Annex B – OTU25u-RS and OTU50u-RS interfaces ..... | 13 |
+| B.1 | Introduction ..... | 13 |
+| B.2 | OTU25u-RS frame structures..... | 13 |
+| B.3 | Bit rates and frame periods..... | 13 |
+| B.4 | OTU25u-RS forward error correction ..... | 14 |
+| B.5 | Interfaces ..... | 14 |
+| | Annex C – Forward error correction for OTU-RS using 10-bit interleaved RS(528,514) codecs ..... | 15 |
+| | Bibliography..... | 17 |
+
+
+
+# OTU25 and OTU50 short-reach interfaces
+
+# 1 Scope
+
+This Recommendation specifies 25 Gbit/s and 50 Gbit/s optical transport network (OTN) short-reach interfaces with Reed-Solomon forward error correction codes (OTU25-RS, OTU50-RS) with lower overhead percentage than the Reed-Solomon forward error correction (FEC) code specified for OTU $k$ ( $k=1,2,3,4$ ) in [ITU-T G.709].
+
+The OTU25-RS and OTU50-RS interfaces complement the OTU25/ODU25 and OTU50/ODU50 functions specified in [ITU-T G.709], with a hard-decision FEC codec, which uses the same overhead percentage ( $\sim 5.8\%$ ) as the FlexO- $x$ -RS FEC codec.
+
+The OTU25-RS and OTU50-RS interfaces may be operated at an approximately 8% and 5% lower rate for use in network scenarios that do not require the support of all clients. Such interfaces are identified as OTU25u-RS and OTU50u-RS interfaces. The OTU25u-RS interface will be equipped with a hard-decision FEC code, which uses a $\sim 3\%$ lower overhead percentage.
+
+This Recommendation makes use of existing [ITU-T G.709], [ITU-T G.798] and [b-ITU-T G-Sup.58] functions by reference and it provides specifications for new functions that are specific to this new interface type. In addition, some introduction material for intended applications is included.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T G.709] Recommendation ITU-T G.709/Y.1331 (2020), *Interfaces for the optical transport network*.
+- [ITU-T G.798] Recommendation ITU-T G.798 (2017), *Characteristics of optical transport network hierarchy equipment functional blocks*.
+- [IEEE 802.3] IEEE Std 802.3TM -2018, IEEE Standard for Ethernet.
+- [IEEE 802.3cd] IEEE Std 802.3cdTM , IEEE Standard for Ethernet, *Amendment 3: Media Access Control Parameters for 50 Gb/s and Physical Layers and Management Parameters for 50 Gb/s, 100 Gb/s, and 200 Gb/s Operation*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+- 3.1.1 optical data unit $k$ (ODU $k$ ) [ITU-T G.709].
+- 3.1.2 optical transport network (OTN) [ITU-T G.709].
+- 3.1.3 optical payload unit $k$ (OPU $k$ ) [ITU-T G.709].
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 OTU25-RS:** Information structure consisting of an OTU25, plus code word marker, plus Reed-Solomon (544,514)10 FEC parity.
+
+**3.2.2 OTU25u-RS:** Information structure consisting of an OTU25u, plus code word marker, plus Reed-Solomon (528,514)10 FEC parity.
+
+**3.2.3 OTU50-RS:** Information structure consisting of an OTU50, plus alignment marker, plus Reed-Solomon (544,514)10 FEC parity.
+
+**3.2.4 OTU50u-RS:** Information structure consisting of an OTU50, plus alignment marker, plus Reed-Solomon (544,514)10 FEC parity.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|------------|---------------------------------------------------------------------------------------------------------------------------------------|
+| AM | Alignment Marker |
+| CMx | Common Marker #x |
+| CPx | Common Pad #x |
+| CWM | Code Word Marker |
+| FEC | Forward Error Correction |
+| LSB | Least Significant Bit |
+| MSB | Most Significant Bit |
+| ODU | Optical Data Unit |
+| ODUk | ODU order k |
+| OPU | Optical Payload Unit |
+| OPUk | OPU order k |
+| OTL50.k-RS | group of k Optical Transport Lanes with Reed-Solomon FEC that carry one OTU50 |
+| OTN | Optical Transport Network |
+| OTSi | Optical Tributary Signal |
+| OTU | Optical Transport Unit |
+| OTU-RS | Optical Transport Unit with AM/CWM and Reed-Solomon (528,514) 10 or (544,514) 10 FEC (e.g., OTU25-RS, OTU50-RS) |
+| RS | Reed Solomon |
+| UMx | Unique Marker #x |
+
+# 5 Conventions
+
+**Transmission order:** The order of transmission of information in all the diagrams in this Recommendation is first from left to right and then from top to bottom. Within each byte the most significant bit is transmitted first. The most significant bit (bit 1) is illustrated at the left in all the diagrams.
+
+**Value of reserved bit(s):** The value of an overhead bit, which is reserved or reserved for future international standardization, shall be set to "0".
+
+**Value of non-sourced bit(s):** Unless stated otherwise, any non-sourced bits shall be set to "0".
+
+# 6 Introduction
+
+An OTU-RS interface is defined for 25 and 50 Gbit/s short reach interoperable multi-vendor applications, over which a 25 or 50 Gbit/s optical transport unit (OTU) signal is adapted. Such applications include but are not limited to 5G transport over optical transport network (OTN) as described in [b-ITU-T G-Sup.67] and 25G and 50G OTN interfaces on customer premise equipment that support private line services.
+
+The specification of 25 and 50 Gbit/s OTU signals in [ITU-T G.709] excludes interface specific functions such as forward error correction (FEC), scrambling, bit alignment and lane distribution. These functions are specified in this Recommendation.
+
+# 7 Structure
+
+This clause specifies the basic signal structure for 25 and 50 Gbit/s OTU-RS interfaces.
+
+## 7.1 Basic signal structure
+
+The OTU-RS interface is specified for short-reach applications.
+
+The information structure for the OTU-RS interface is represented by information containment relationships and information flows. The principal information containment relationship is shown in Figures 7-1 and 7-2.
+
+One OTU25 signal is mapped into an OTU25-RS signal, as illustrated in Figure 7-1. The OTU25-RS interface signal is modulated onto one OTSi and the OTSi is transported via one media element.
+
+
+
+The diagram illustrates the information containment hierarchy for OTU25-RS. It shows the following layers and their components:
+
+- 1 or more clients**: The top-level clients.
+- OPU25**: Contains **OPU25 OH** and **OPU25 payload**.
+- ODU25 path**: Contains **ODU25 PMOH** and **OPU25**.
+- ODU25 tandem connection**: Contains **ODU25 TCMOH**.
+- OTU25 section**: Contains **OTU25 SMOH**.
+- OTU25-RS**: Contains **CWM**, **Payload**, and **FEC**.
+- OTSi**: Contains the **OTSi** signal.
+- Media element**: The bottom-most transport element.
+
+Dashed lines indicate the containment relationships between these layers. A label **G.709.4-Y.1331.4(20)\_F7-1** is present at the bottom right of the diagram.
+
+Diagram showing the principal information containment relationship for OTU25-RS. It illustrates the hierarchy from clients down to the media element, showing various overheads and payloads at different layers.
+
+**Figure 7-1 – OTU25-RS principal information containment relationship**
+
+One OTU50 signal is mapped into an OTU50-RS signal, as illustrated in Figure 7-2. The OTU50-RS interface signal is split into two OTL50.2-RS lane signals which are bit interleaved into a single OTL50.1-RS lane signal. This OTL50.1-RS lane signal is modulated onto one OTSi and the OTSi is transported via one media element.
+
+
+
+The diagram illustrates the information containment hierarchy for OTU50-RS. At the top, '1 or more clients' are shown. Below this, the hierarchy is defined by several layers, each with specific overheads and payloads:
+
+- OPU50:** Contains 'OPU50 OH' and 'OPU50 payload'.
+- ODU50 path:** Contains 'ODU50 PMOH' and 'OPU50'.
+- ODU50 tandem connection:** Contains 'ODU50 TCMOH'.
+- OTU50 section:** Contains 'OTU50 SMOH'.
+- OTU50-RS:** Contains 'AM' (Alignment Marker), 'Payload', and 'FEC' (Forward Error Correction).
+- OTL50.1-RS:** Contains 'OTL50.1-RS'.
+- OTS:** Contains 'OTS'.
+- Media element:** The final layer at the bottom.
+
+Dashed lines indicate the containment relationships between the layers. The label 'G.709.4-Y.1331.4(20)\_F7-2' is located at the bottom right of the diagram.
+
+Diagram showing the principal information containment relationship for OTU50-RS. It illustrates the hierarchy from clients down to the media element, showing various overheads and payloads at each layer.
+
+**Figure 7-2 – OTU50-RS principal information containment relationship**
+
+# 8 OTU25-RS interface
+
+## 8.1 Frame structure
+
+The OTU25-RS frame structure is shown in Figure 8-1 and consists of 1024 rows by 5440 1-bit columns.
+
+It contains a frame alignment area with a code word marker (CWM) in row 1, columns 1 to 256, a RS(544,514,10) forward error correction (FEC) parity area in columns 5141 to 5440 and a $(1024 \times 5140 - 256 =) 5,263,104$ bit payload area in the remainder of the frame.
+
+NOTE – The OTU25-RS frame structure is derived from 25 Gbit/s Ethernet clause 108 of [IEEE 802.3] FEC code word marker architecture, without any 66b alignment or 256b/257b transcoding functions and with RS(544,514) instead of RS(528,514) forward error correction.
+
+
+
+Figure 8-1: OTU25-RS and OTU50-RS frame structure diagram. The diagram shows a frame with 1024 rows. Row 1 starts with 'Frame alignment' (bits 1-256), followed by 'Payload' (bits 257-5140), and 'FEC parity' (bits 5141-5440). Rows 2 and 3 show 'Payload' and 'FEC parity'. Rows 4 through 1023 are represented by dashed lines, indicating they also contain 'Payload' and 'FEC parity'. Row 1024 shows 'Payload' and 'FEC parity'.
+
+NOTE – Frame alignment contains CWM for OTU25-RS or AM for OTU50-RS
+
+G.709.4-Y.1331.4(20)\_F8-1
+
+**Figure 8-1 – OTU25-RS and OTU50-RS frame structure**
+
+## 8.2 Bit rate and frame period
+
+The bit rate and tolerance of the OTU25-RS signal is defined in Table 8-1.
+
+**Table 8-1 – OTU25-RS and OTU50-RS interface bit rates**
+
+| OTU-RS type | OTU-RS nominal bit rate | OTU-RS bit-rate tolerance |
+|-------------------------------------------------------------------------------|--------------------------------------|---------------------------|
+| OTU25-RS | $255/227 \times 24\,883\,200$ kbit/s | $\pm 20$ ppm |
+| NOTE – The nominal OTU25-RS bit rate is approximately: 27 952 493.392 kbit/s. | | |
+
+The frame and multi-frame periods of the OTU25-RS signal is defined in Table 8-2.
+
+**Table 8-2 – OTU25-RS and OTU50-RS frame periods**
+
+| OTU-RS type | Frame period (Note) |
+|--------------------------------------------------------------------------|---------------------|
+| OTU25-RS | 199.278 $\mu$ s |
+| NOTE – The period is an approximated value, rounded to 3 decimal places. | |
+
+## 8.3 Overhead
+
+The OTU25-RS frame supports CWM overhead.
+
+### 8.3.1 CWM format
+
+Code word markers are used for FEC frame alignment. The code word marker (CWM) area length for an OTU25-RS frame is defined as 256 bits, which holds four 64-bit code word markers labelled CWM0 to CWM3 (see Figure 8-2). The value of CWM0 to CWM3 is specified in Table 8-3.
+
+NOTE – The OTU25-RS code word markers reuse the [IEEE 802.3] clause 108.5.2.4 CWM specifications.
+
+
+
+Figure 8-2: 256-bit CWM format diagram. It shows four 64-bit code word markers: CWM0, CWM1, CWM2, and CWM3. An arrow below them indicates the transmission order from left to right.
+
+G.709.4-Y.1331.4(20)\_F8-2
+
+**Figure 8-2 – 256-bit CWM format**
+
+**Table 8-3 – CWM encoding in OTN transmission order**
+
+| | CWMi Encodinga {M0, M1, M2, U0, M4, M5, M6, U1} |
+|------|-----------------------------------------------------------------------------|
+| CWM0 | 83, 16, 84, CC, 7C, E9, 7B, 33 |
+| CWM1 | 0F, 23, 67, CC, F0, DC, 98, 33 |
+| CWM2 | A3, A6, D9, CC, 5C, 59, 26, 33 |
+| CWM3 | 45, 9E, BC, CC, BA, 61, 43, 33 |
+
+NOTE – a The value in each byte of this table is in MSB-first transmission order. Note this per-byte ordering is the reverse of code word marker (CWM) values in [IEEE 802.3] Clause 108.5.2.4, which uses an LSB-first bit transmission order.
+
+## 8.4 Scrambling
+
+The OTN "frame additive" synchronous scrambler with sequence length of 65535 and generating polynomial $x^{16} + x^{12} + x^3 + x + 1$ is re-used. This is the same scrambler as used for any other OTUk or FlexO-x- frame format.
+
+Scrambler synchronization is similar to OTUk[NO FEC] scrambling. This means that the scrambler is synchronized using FAS of the OTU251 and operate the scrambler before CWM2 and FEC parity columns insertion. FEC parity is calculated on scrambled data, so that it shall contain sufficient clock content (same concept as for FlexO-x-RS or 25GE3 scramblers).
+
+## 8.5 Forward error correction
+
+The OTU25-RS FEC area contains the Reed-Solomon RS(544,514) FEC codes. The RS(544,514,10) FEC code shall be computed as specified in Annex A.
+
+## 8.6 Interface format
+
+An OTU25-RS interface presents the OTU25-RS signal in this format on the interface.
+
+NOTE – This interface format is compatible and can reuse optical modules developed for IEEE 25GBASE-R, with OTU25-RS rate support.
+
+The OTU25-RS interface format is intended for applications to be defined by application codes for metro networks.
+
+# 9 OTU50-RS interface
+
+## 9.1 Frame structure
+
+The OTU50-RS frame structure is shown in Figure 8-1 and consists of 1024 rows by 5,440 1-bit columns.
+
+It contains a frame alignment area with an alignment marker (AM) in row 1, columns 1 to 256, a RS(544,514,10) forward error correction (FEC) parity area in columns 5141 to 5440 and a $(1024 \times 5140 - 256 =)$ 5,263,104 bit payload area in the remainder of the frame.
+
+1 OTU50 in case of OTU50-RS scrambling as specified in clause 9.4.
+
+2 AM in case of OTU50-RS scrambling as specified in clause 9.4.
+
+3 50GE in case of OTU50-RS scrambling as specified in clause 9.4.
+
+
+
+**Table 9-3 – OTU50-RS alignment marker encodings**
+
+| am[i] | Encoding 1 | | | | | | | | | | | | | | | |
+|-------|-----------------------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|
+| | CM0 | CM1 | CM2 | CP0 | CM3 | CM4 | CM5 | CP1 | UM0 | UM1 | UM2 | CP2 | UM3 | UM4 | UM5 | CP3 |
+| 0 | 09 | 6E | E2 | AA | F6 | 91 | 1D | 55 | A3 | A6 | D9 | AA | 5C | 59 | 26 | 55 |
+| 1 | 09 | 6E | E2 | AA | F6 | 91 | 1D | 55 | 45 | 9E | BC | AA | BA | 61 | 43 | 55 |
+
+NOTE – The value in each byte of this table is in MSB-first transmission order. Note this per-byte ordering is the reverse of alignment marker (AM) values in IEEE 802.3 Table 82-3, which uses an LSB-first bit transmission order.
+
+The 256-bit OTU50-RS alignment marker area contains 10-bit interleaved parts of am0 and am1 as illustrated in Figure 9-2. The 256 bits contain the 10-bit interleaved parts of am0 to am1 in the order am0 , am1 , am0 , am1 , am0 , etc. The last 16 bits contain the last 8 bits of am0 and the last 8 bits of am1 .
+
+
+
+Diagram of the OTU50-RS alignment marker area showing 256 bits of data interleaved across two FEC lanes (FEC lane 0 and FEC lane 1). The diagram shows the mapping of 10-bit segments of alignment markers am0 and am1 to the lanes. FEC lane 0 carries the 1st, 3rd, 5th, 7th, 9th, and 11th 10-bit segments of am0, plus the first two bits of am1. FEC lane 1 carries the 2nd, 4th, 6th, 8th, 10th, and 12th 10-bit segments of am1, plus the last 8 bits of am0 and the last 8 bits of am1. The diagram is labeled with 'Bits' from 1 to 256 and 'AM' for the alignment marker area. A note at the bottom right indicates the source as G.709.4-Y.1331.4(20)\_F9-2.
+
+**Figure 9-2 – OTU50-RS alignment marker area with two interleaved lane alignment markers**
+
+The OTU50-RS frame signal supports subsequent distribution into two logical FEC lanes, numbered 0 and 1. FEC lane 0 carries the 128-bit alignment marker #0 (am0 ) as specified in Table 9-3 plus the first two bits of CP3 of alignment marker #1 as illustrated in Figure 9-2. FEC lane 1 carries the 128-bit alignment marker #1 (am1 ) as specified in Table 9-3, minus the first two bits of CP3.
+
+## 9.4 Scrambling
+
+Refer to clause 8.4.
+
+## 9.5 Forward error correction
+
+The OTU50-RS FEC area contains the Reed-Solomon RS(544,514) FEC codes. The RS(544,514,10) FEC code shall be computed as specified in Annex A.
+
+## 9.6 Interface format
+
+An OTU50-RS interface presents the OTU50-RS signal in an OTL50.1-RS interface format.
+
+NOTE 1 – This interface format is compatible and can reuse optical modules developed for IEEE 50GBASE-R, with OTU50-RS rate support.
+
+The OTU50-RS bits are distributed to two logical OTL50.2-RS lanes, in groups of 10-bits, in a round robin distribution scheme from the lowest to the highest numbered lanes. The specific scheme of distribution is specified in clause 134 of [IEEE 802.3cd] for 50GBASE-R interface. Each OTL50.2-RS logical lane is synchronous to the OTU50-RS frame.
+
+Each OTU50-RS frame contains $5440 \times 1024 = 5,570,560$ bits. Each logical OTL50.2-RS lane will carry 50% of these bits, which are 2,785,280 bits, or 278,528 10-bit blocks.
+
+NOTE 2 – Figure 9-2 illustrates the 10-bit distribution of the alignment marker to the two logical lanes.
+
+The physical lane of an OTL50.1-RS is generated by bit multiplexing the two logical OTL50.2-RS lanes onto the physical lane.
+
+The tolerated skew between logical lanes in an OTL50.1-RS interface signal is at least 180 ns.
+
+The bit rate and tolerance of the OTL50.1-RS signal are the same as the bit rate and tolerance of the OTU50-RS signal.
+
+The OTL50.1-RS interface format is intended for applications to be defined by application codes for metro networks.
+
+# 10 Mapping OTU25 and OTU50 signal into OTU25-RS and OTU50-RS
+
+Mapping an OTU25 signal into the OTU25-RS payload area is done by means of bit-synchronous mapping of 128-bit blocks of the OTU25 frame as illustrated in Figure 10-1. The 128-bit blocks of the OTU25 frames will float in the OTU25-RS payload area.
+
+
+
+Adapt 128-bit OTU25 | OTU50 blocks into 128-bit OTU25-RS | OTU50-RS payload blocks
+
+128 bit 128 bit 128 bit
+
+FA OH OTU OH OPU OH Payload Payload . . .
+
+128-bit
+
+AUC
+
+.....
+
+Parity FEC
+
+5140-bit 300-bit
+
+128-bit block spills over payload row and is not a perfect multiple; however there is an integer # of 1285 128-bit blocks per 32 rows and there is an integer # of 41118 128-bit payload blocks per 1024 rows
+
+G.709.4-Y.1331.4(20)\_F10-1
+
+Diagram illustrating the 128-bit based mapping of OTU25 into OTU25-RS and OTU50 into OTU50-RS. The diagram shows the adaptation of 128-bit OTU25/OTU50 blocks into 128-bit OTU25-RS/OTU50-RS payload blocks. The top part shows a sequence of 128-bit blocks containing FA OH, OTU OH, OPU OH, and Payload. The bottom part shows a grid of 128-bit blocks, with the first two blocks labeled 'AUC'. Arrows indicate the mapping of 128-bit blocks from the top sequence into the grid. The grid is divided into a 5140-bit section and a 300-bit section, with the latter containing Parity FEC. A note at the bottom states: '128-bit block spills over payload row and is not a perfect multiple; however there is an integer # of 1285 128-bit blocks per 32 rows and there is an integer # of 41118 128-bit payload blocks per 1024 rows'. The diagram is labeled G.709.4-Y.1331.4(20)\_F10-1.
+
+**Figure 10-1 – 128-bit based mapping of OTU25 into OTU25-RS and OTU50 into OTU50-RS**
+
+Mapping an OTU50 signal into the OTU50-RS payload area is done by means of bit-synchronous mapping of 128-bit blocks of the OTU50 as illustrated in Figure 10-1. The 128-bit blocks of the OTU50 frames will float in the OTU50-RS payload area.
+
+# Annex A
+
+## Forward error correction for OTU-RS using 10-bit interleaved RS(544,514) codecs
+
+(This annex forms an integral part of this Recommendation.)
+
+NOTE – The OTU-RS FEC is based on RS(544, 514,10), as specified in clause 91.5.2.7 of [IEEE 802.3].
+
+The forward error correction for the OTU-RS uses a single codec using a Reed-Solomon RS(544,514) code. The RS(544,514) code is a non-binary code (the FEC algorithm operates on 10-bit symbols) and belongs to the family of systematic linear cyclic block codes.
+
+For FEC processing, an OTU-RS row is processed by the FEC encoder/decoder. The 10-bit FEC parity check blocks are calculated over the 10-bit information blocks 1 to 514 of each row and transmitted in 10-bit blocks 515 to 544 of the same row, as shown in Figure A.1.
+
+| 10-bit information blocks | | 10-bit parity blocks | | FEC row = OTU-RS row |
+|---------------------------|-------|----------------------|---|---------------------------|
+| 1 | 5 5 5 | | 5 | |
+| | 1 1 1 | | 4 | |
+| | 4 5 6 | | 4 | G.709.4-Y.1331.4(20)_FA.1 |
+
+Figure A.1 – FEC row
+
+The 10-bit blocks in an OTU-RS row are defined by: $10 \times (i - 1)$ (for $i = 1 \dots 544$ ).
+
+The generator polynomial of the code is given by:
+
+$$G(z) = \prod_{i=0}^{29} (z - \alpha^i)$$
+
+where $\alpha$ is a root of the binary primitive polynomial $x^{10} + x^3 + 1$ .
+
+The FEC code word (see Figure A.2) consists of 10-bit information blocks and parity blocks (FEC redundancy) and is represented by the polynomial:
+
+$$C(z) = I(z) + R(z)$$
+
+
+
+Diagram of an RS(544,514) FEC code word structure. It shows a sequence of blocks labeled 'FEC row' with indices 1 to 544. The first four blocks are D\_543, D\_542, D\_541, D\_540. A block D\_j is shown with its 10 internal bits: d\_0j, d\_1j, d\_2j, d\_3j, d\_4j, d\_5j, d\_6j, d\_7j, d\_8j, d\_9j. A parity block R\_j is shown with its 10 internal bits: r\_0j, r\_1j, r\_2j, r\_3j, r\_4j, r\_5j, r\_6j, r\_7j, r\_8j, r\_9j. The transmission order is indicated by an arrow pointing right, starting from block 1 and ending at block 544. The diagram also shows blocks D\_31, D\_30, R\_29, R\_28, R\_j, R\_1, R\_0. The source identifier G.709.4-Y.1331.4(20)\_FA.2 is at the bottom right.
+
+Figure A.2 – RS(544,514) FEC code word
+
+10-bit information blocks are represented by:
+
+$$I(z) = D_{543} \cdot z^{543} + D_{542} \cdot z^{542} + \dots + D_{30} \cdot z^{30}$$
+
+Where $D_j$ ( $j = 30$ to $543$ ) is the 10-bit information block represented by an element out of $GF(256)$ and:
+
+$$D_j = d_{9j} \cdot \alpha^9 + d_{8j} \cdot \alpha^8 + \dots + d_{1j} \cdot \alpha^1 + d_{0j}$$
+
+Bit $d_{9j}$ is the MSB and $d_{0j}$ the LSB of the 10-bit information block.
+
+$D_{543}$ corresponds to 10-bit block 1 in the FEC row and $D_{30}$ to 10-bit block 514.
+
+10-bit parity blocks are represented by:
+
+$$R(z) = R_{29} \cdot z^{29} + R_{28} \cdot z^{28} + \dots + R_1 \cdot z^1 + R_0$$
+
+Where $R_j$ ( $j = 0$ to $29$ ) is the 10-bit parity block represented by an element out of $GF(2^{10})$ and:
+
+$$R_j = r_{9j} \cdot \alpha^9 + r_{8j} \cdot \alpha^8 + \dots + r_{1j} \cdot \alpha^1 + r_{0j}$$
+
+Bit $r_{9j}$ is the MSB and $r_{0j}$ the LSB of the 10-bit parity block.
+
+$R_{29}$ corresponds to the 10-bit block 515 in the FEC row and $R_0$ to 10-bit block 544.
+
+$R(z)$ is calculated by:
+
+$$R(z) = I(z) \bmod G(z)$$
+
+where "mod" is the modulo calculation over the code generator polynomial $G(z)$ with elements out of the $GF(2^{10})$ . Each element in $GF(2^{10})$ is defined by the binary primitive polynomial $x^{10} + x^3 + 1$ .
+
+The Hamming distance of the RS(544,514) code is $d_{\min} = 31$ . The code can correct up to 15 symbol errors in the FEC code word when it is used for error correction. The FEC can detect up to 30 symbol errors in the FEC code word when it is used for error detection capability only.
+
+# Annex B
+
+## OTU25u-RS and OTU50u-RS interfaces
+
+(This annex forms an integral part of this Recommendation.)
+
+### B.1 Introduction
+
+In network applications that do not require support of all client signals, the OTU25u-RS interface may be operated at an 8.4% lower rate and the OTU50u-RS interface may be operated at a 5.2% lower rate. The bit rates of such "under-clocked" OTU25u-RS and OTU50u-RS are specified in this annex. All other OTU25-RS and OTU50-RS specifications apply for the OTU25u-RS and OTU50u-RS, with exception of the forward error correction and frame structure of the OTU25u-RS (i.e., different FEC parity area). The OTU25u-RS frame structure and forward error correction is therefore specified in this annex as well.
+
+## B.2 OTU25u-RS frame structures
+
+The OTU25u-RS frame structure is illustrated in Figure B.1. It consists of 1024 rows by 5280 1-bit columns and a frame alignment overhead area with a CWM plus RS(528,514,10) FEC.
+
+NOTE – The OTU25u-RS FEC is different from the OTU25-RS FEC.
+
+
+
+Diagram of OTU25u-RS frame structure showing 1024 rows and 5280 columns. The first 256 columns are the frame alignment area, followed by payload columns up to 5140, and the final 140 columns (5280-5140) are for FEC parity. Row 1 shows the frame alignment, payload, and FEC parity. Rows 2 and 3 show payload and FEC parity. Rows 4 through 1023 show payload and FEC parity. Row 1024 shows payload and FEC parity. The diagram is labeled G.709.4-Y.1331.4(20)\_FB.1.
+
+Figure B.1 – OTU25u-RS frame structure
+
+## B.3 Bit rates and frame periods
+
+The bit rate and tolerance of the OTU25u-RS and OTU50u-RS signals are defined in Table B.1.
+
+The frame periods of the OTU25u-RS and OTU50u-RS are defined in Table B.2.
+
+Table B.1 – OTU25u-RS and OTU50u-RS interface bit rates
+
+| OTU-RS type | OTU-RS nominal bit rate | OTU-RS bit-rate tolerance |
+|-----------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|---------------------------|
+| OTU25u-RS | $660/637 \times 24\,883\,200$ kbit/s | $\pm 20$ ppm |
+| OTU50u-RS | $680/637 \times 49\,766\,400$ kbit/s | |
+| NOTE – The nominal OTU25u-RS and OTU50u-RS bit rates are approximately: 25 781 651.491 kbit/s (OTU25u-RS), 53 125 827.316 kbit/s (OTU50u-RS). | | |
+
+**Table B.2 – OTU25u-RS and OTU50u-RS frame periods**
+
+| OTU-RS type | Frame period (Note) |
+|--------------------------------------------------------------------------|----------------------------|
+| OTU25u-RS | 209.712 µs |
+| OTU50u-RS | 104.856 µs |
+| NOTE – The period is an approximated value, rounded to 3 decimal places. | |
+
+## **B.4 OTU25u-RS forward error correction**
+
+The OTU25u-RS FEC area contains the Reed-Solomon RS(528,514) FEC codes. The RS(528,514,10) FEC code shall be computed as specified in Annex C.
+
+## **B.5 Interfaces**
+
+#### **B.5.1 OTU25u-RS**
+
+An OTU25u-RS interface presents the OTU25u-RS signal in this format on the interface.
+
+NOTE – This interface format is compatible and can reuse optical modules developed for IEEE 25GBASE-R.
+
+The OTU25u-RS interface format is intended for applications to be defined by application codes for metro networks.
+
+#### **B.5.2 OTU50u-RS**
+
+An OTU50u-RS interface presents the OTU50u-RS signal in an OTL50u.1-RS interface format.
+
+NOTE – This interface format is compatible and can reuse optical modules developed for IEEE 50GBASE-R.
+
+The OTL50u.1-RS interface format and tolerated skew are the same as the OTL50.1-RS interface format and tolerated skew.
+
+The bit rate and tolerance of the OTL50u.1-RS interface signal are the same as the bit rate and tolerance of the OTU50u-RS signal.
+
+The OTL50u.1-RS interface format is intended for applications to be defined by application codes for metro networks.
+
+# Annex C
+
+## Forward error correction for OTU-RS using 10-bit interleaved RS(528,514) codecs
+
+(This annex forms an integral part of this Recommendation.)
+
+NOTE – The OTU-RS FEC is based on RS(528, 514,10), as specified in clause 91.5.2.7 of [IEEE 802.3].
+
+The forward error correction for the OTU-RS uses a single codec using a Reed-Solomon RS(528,514) code. The RS(528,514) code is a non-binary code (the FEC algorithm operates on 10-bit symbols) and belongs to the family of systematic linear cyclic block codes.
+
+For FEC processing, an OTU-RS row is processed by the FEC encoder/decoder. The 10-bit FEC parity check blocks are calculated over the 10-bit information blocks 1 to 514 of each row and transmitted in 10-bit blocks 515 to 528 of the same row, as shown in Figure C.1.
+
+| 10-bit information blocks | | 10-bit parity blocks | | FEC row = OTU-RS row |
+|---------------------------|-------|----------------------|---|---------------------------|
+| 1 | 5 5 5 | | 5 | |
+| | 1 1 1 | | 4 | |
+| | 4 5 6 | | 4 | G.709.4-Y.1331.4(20)_FC.1 |
+
+Figure C.1 – FEC row
+
+The 10-bit blocks in an OTU-RS row are defined by: $10 \times (i - 1)$ (for $i = 1 \dots 528$ ).
+
+The generator polynomial of the code is given by:
+
+$$G(Z) = \prod_{i=0}^{13} (Z - \alpha^i)$$
+
+where $\alpha$ is a root of the binary primitive polynomial $x^{10} + x^3 + 1$ .
+
+The FEC code word (see Figure C.2) consists of 10-bit information blocks and parity blocks (FEC redundancy) and is represented by the polynomial:
+
+$$C(z) = I(z) + R(z)$$
+
+
+
+Diagram of an RS(544,514) FEC code word structure. It shows a sequence of blocks labeled 'FEC row' with indices 1 to 528. The first four blocks are D527, D526, D525, D524. There is a gap indicated by a dashed line, followed by block Dj. Another gap, then blocks D15, D14, R13, R12. Another gap, then block Rj. Another gap, then blocks R1, R0. Above the blocks is an arrow labeled 'Transmission order within FEC code word'. Below block Dj, a tree diagram shows 10 sub-elements: d9j, d8j, d7j, d6j, d5j, d4j, d3j, d2j, d1j, d0j. Below block Rj, a similar tree diagram shows 10 sub-elements: r9j, r8j, r7j, r6j, r5j, r4j, r3j, r2j, r1j, r0j. The label 'G.709.4-Y.1331.4(20)\_FC.2' is at the bottom right.
+
+Figure C.2 – RS(544,514) FEC code word
+
+10-bit information blocks are represented by:
+
+$$I(z) = D_{527} \cdot z^{527} + D_{526} \cdot z^{526} + \dots + D_{14} \cdot z^{14}$$
+
+Where $D_j$ ( $j = 15$ to $527$ ) is the 10-bit information block represented by an element out of GF(256) and:
+
+$$D_j = d_{9j} \cdot \alpha^9 + d_{8j} \cdot \alpha^8 + \dots + d_{1j} \cdot \alpha^1 + d_{0j}$$
+
+Bit $d_{9j}$ is the MSB and $d_{0j}$ the LSB of the 10-bit information block.
+
+$D_{527}$ corresponds to 10-bit block 1 in the FEC row and $D_{14}$ to 10-bit block 514.
+
+10-bit parity blocks are represented by:
+
+$$R(z) = R_{13} \cdot z^{13} + R_{12} \cdot z^{12} + \dots + R_1 \cdot z^1 + R_0$$
+
+Where $R_j$ ( $j = 0$ to 29) is the 10-bit parity block represented by an element out of $GF(2^{10})$ and:
+
+$$R_j = r_{9j} \cdot \alpha^9 + r_{8j} \cdot \alpha^8 + \dots + r_{1j} \cdot \alpha^1 + r_{0j}$$
+
+Bit $r_{9j}$ is the MSB and $r_{0j}$ the LSB of the 10-bit parity block.
+
+$R_{29}$ corresponds to the 10-bit block 515 in the FEC row and $R_0$ to 10-bit block 544.
+
+$R(z)$ is calculated by:
+
+$$R(z) = I(z) \bmod G(z)$$
+
+where "mod" is the modulo calculation over the code generator polynomial $G(z)$ with elements out of the $GF(2^{10})$ . Each element in $GF(2^{10})$ is defined by the binary primitive polynomial $x^{10} + x^3 + 1$ .
+
+The Hamming distance of the RS(528,514) code is $d_{min} = 15$ . The code can correct up to 7 symbol errors in the FEC code word when it is used for error correction. The FEC can detect up to 14 symbol errors in the FEC code word when it is used for error detection capability only.
+
+# Bibliography
+
+- [b-ITU-T G-Sup.58] ITU-T G-series Recommendations – Supplement 58 (2020), *Optical transport network module framer interfaces.*
+- [b-ITU-T G-Sup.67] ITU-T G-series Recommendations – Supplement 67 (2019), *Application of optical transport network Recommendations to 5G transport.*
+
+
+
+# ITU-T Y-SERIES RECOMMENDATIONS
+
+# **GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES**
+
+### **GLOBAL INFORMATION INFRASTRUCTURE**
+
+| | |
+|-------------------------------------------|-------------|
+| General | Y.100–Y.199 |
+| Services, applications and middleware | Y.200–Y.299 |
+| Network aspects | Y.300–Y.399 |
+| Interfaces and protocols | Y.400–Y.499 |
+| Numbering, addressing and naming | Y.500–Y.599 |
+| Operation, administration and maintenance | Y.600–Y.699 |
+| Security | Y.700–Y.799 |
+| Performances | Y.800–Y.899 |
+
+### **INTERNET PROTOCOL ASPECTS**
+
+| | |
+|--------------------------------------------------------------------|----------------------|
+| General | Y.1000–Y.1099 |
+| Services and applications | Y.1100–Y.1199 |
+| Architecture, access, network capabilities and resource management | Y.1200–Y.1299 |
+| Transport | Y.1300–Y.1399 |
+| Interworking | Y.1400–Y.1499 |
+| Quality of service and network performance | Y.1500–Y.1599 |
+| Signalling | Y.1600–Y.1699 |
+| Operation, administration and maintenance | Y.1700–Y.1799 |
+| Charging | Y.1800–Y.1899 |
+| IPTV over NGN | Y.1900–Y.1999 |
+
+### **NEXT GENERATION NETWORKS**
+
+| | |
+|-------------------------------------------------------------------|---------------|
+| Frameworks and functional architecture models | Y.2000–Y.2099 |
+| Quality of Service and performance | Y.2100–Y.2199 |
+| Service aspects: Service capabilities and service architecture | Y.2200–Y.2249 |
+| Service aspects: Interoperability of services and networks in NGN | Y.2250–Y.2299 |
+| Enhancements to NGN | Y.2300–Y.2399 |
+| Network management | Y.2400–Y.2499 |
+| Network control architectures and protocols | Y.2500–Y.2599 |
+| Packet-based Networks | Y.2600–Y.2699 |
+| Security | Y.2700–Y.2799 |
+| Generalized mobility | Y.2800–Y.2899 |
+| Carrier grade open environment | Y.2900–Y.2999 |
+
+### **FUTURE NETWORKS**
+
+### **CLOUD COMPUTING**
+
+### **BIG DATA**
+
+### **QUANTUM KEY DISTRIBUTION NETWORKS**
+
+### **INTERNET OF THINGS AND SMART CITIES AND COMMUNITIES**
+
+| | |
+|---------------------------------------------------------|---------------|
+| General | Y.4000–Y.4049 |
+| Definitions and terminologies | Y.4050–Y.4099 |
+| Requirements and use cases | Y.4100–Y.4249 |
+| Infrastructure, connectivity and networks | Y.4250–Y.4399 |
+| Frameworks, architectures and protocols | Y.4400–Y.4549 |
+| Services, applications, computation and data processing | Y.4550–Y.4699 |
+| Management, control and performance | Y.4700–Y.4799 |
+| Identification and security | Y.4800–Y.4899 |
+| Evaluation and assessment | Y.4900–Y.4999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/G/T-REC-G.722.2-200307-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.722.2-200307-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30
--- /dev/null
+++ b/marked/G/T-REC-G.722.2-200307-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359
+size 8245
diff --git a/marked/G/T-REC-G.722.2-200307-I_PDF-E/3040912f5c829555787992af40034f60_img.jpg b/marked/G/T-REC-G.722.2-200307-I_PDF-E/3040912f5c829555787992af40034f60_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fcc7f90ab1f3147a02df82d3a2e04e6facc5b895
--- /dev/null
+++ b/marked/G/T-REC-G.722.2-200307-I_PDF-E/3040912f5c829555787992af40034f60_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b8c609a4d31437e9c555232113193e8e6edbf625e5dd8a7045ac289d09219b8c
+size 9149
diff --git a/marked/G/T-REC-G.722.2-200307-I_PDF-E/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/G/T-REC-G.722.2-200307-I_PDF-E/56a5265d174ce056c1dbe5e7a60839fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f1b37f0a06b31f07ca4115249268caa7fc3fcb24
--- /dev/null
+++ b/marked/G/T-REC-G.722.2-200307-I_PDF-E/56a5265d174ce056c1dbe5e7a60839fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d687fedb3cbf6da0121bd01e6578b05343ec820a79897a8976221bde32ce1cbf
+size 76405
diff --git a/marked/G/T-REC-G.722.2-200307-I_PDF-E/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/G/T-REC-G.722.2-200307-I_PDF-E/65e8c0628536d6d4245e9ab46ba070c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..076daa98e9492ec7f4a496716fca32fce21883a1
--- /dev/null
+++ b/marked/G/T-REC-G.722.2-200307-I_PDF-E/65e8c0628536d6d4245e9ab46ba070c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ddfc00dd0a4befe212fec45e2a8b9ccc43f08a5648e61535b982c19467cd96a2
+size 24662
diff --git a/marked/G/T-REC-G.722.2-200307-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/G/T-REC-G.722.2-200307-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dee3f510d0bcd4fb1a7bc2cea14ebc210844fa3c
--- /dev/null
+++ b/marked/G/T-REC-G.722.2-200307-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:197434f95cc21ba390a74f3e216439f86380aebb9cbf993c02d19e1233d17029
+size 35298
diff --git a/marked/G/T-REC-G.722.2-200307-I_PDF-E/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/marked/G/T-REC-G.722.2-200307-I_PDF-E/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..42af0a0ce1e0e1f3d59100e02bea0e0f070a26e3
--- /dev/null
+++ b/marked/G/T-REC-G.722.2-200307-I_PDF-E/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dd1458c212e6784f4baaa23b62f7771638030e34bcb720241b09994ef5a243c9
+size 15998
diff --git a/marked/G/T-REC-G.722.2-200307-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/G/T-REC-G.722.2-200307-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1095a9588d78853826535bfc06fb27cd3e900523
--- /dev/null
+++ b/marked/G/T-REC-G.722.2-200307-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5fe2b3304441bc7aebf98110573a716770293fd12cc8e06c9bb7f64c7573076c
+size 90729
diff --git a/marked/G/T-REC-G.722.2-200307-I_PDF-E/cc542843836eecb036b99cb270b54a1e_img.jpg b/marked/G/T-REC-G.722.2-200307-I_PDF-E/cc542843836eecb036b99cb270b54a1e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..668913d74c761512351f1339c8991cc7f762b7a2
--- /dev/null
+++ b/marked/G/T-REC-G.722.2-200307-I_PDF-E/cc542843836eecb036b99cb270b54a1e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8c63919079a7d4f8a7e9129361504a11fd51780aebcbbe498e175eab19a2b338
+size 48283
diff --git a/marked/G/T-REC-G.722.2-200307-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/G/T-REC-G.722.2-200307-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b23eb2d85dc11110ecff6c57d1de23a62ce95e62
--- /dev/null
+++ b/marked/G/T-REC-G.722.2-200307-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:927312e517de57dc52a073aed23ea0df1da9b769d077c035e03a2050fb35dcb7
+size 188625
diff --git a/marked/G/T-REC-G.722.2-200307-I_PDF-E/raw.md b/marked/G/T-REC-G.722.2-200307-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..bb4a459c910f0bc05afdeba039ac3096ebbfecf4
--- /dev/null
+++ b/marked/G/T-REC-G.722.2-200307-I_PDF-E/raw.md
@@ -0,0 +1,2414 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**G.722.2**
+
+(07/2003)
+
+SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
+DIGITAL SYSTEMS AND NETWORKS
+
+Digital terminal equipments – Coding of analogue signals
+by methods other than PCM
+
+---
+
+**Wideband coding of speech at around 16 kbit/s
+using Adaptive Multi-Rate Wideband (AMR-WB)**
+
+ITU-T Recommendation G.722.2
+
+---
+
+# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS**
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 |
+| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 |
+| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 |
+| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 |
+| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 |
+| TESTING EQUIPMENTS | G.500–G.599 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.600–G.699 |
+| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 |
+| General | G.700–G.709 |
+| Coding of analogue signals by pulse code modulation | G.710–G.719 |
+| Coding of analogue signals by methods other than PCM | G.720–G.729 |
+| Principal characteristics of primary multiplex equipment | G.730–G.739 |
+| Principal characteristics of second order multiplex equipment | G.740–G.749 |
+| Principal characteristics of higher order multiplex equipment | G.750–G.759 |
+| Principal characteristics of transcoder and digital multiplication equipment | G.760–G.769 |
+| Operations, administration and maintenance features of transmission equipment | G.770–G.779 |
+| Principal characteristics of multiplexing equipment for the synchronous digital hierarchy | G.780–G.789 |
+| Other terminal equipment | G.790–G.799 |
+| DIGITAL NETWORKS | G.800–G.899 |
+| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 |
+| QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER-RELATED ASPECTS | G.1000–G.1999 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.6000–G.6999 |
+| DIGITAL TERMINAL EQUIPMENTS | G.7000–G.7999 |
+| DIGITAL NETWORKS | G.8000–G.8999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## **ITU-T Recommendation G.722.2**
+
+# **Wideband coding of speech at around 16 kbit/s using Adaptive Multi-Rate Wideband (AMR-WB)**
+
+## **Summary**
+
+This Recommendation describes the high quality Adaptive Multi-Rate Wideband (AMR-WB) encoder and decoder that is primarily intended for 7 kHz bandwidth speech signals. AMR-WB operates at a multitude of bit rates ranging from 6.6 kbit/s to 23.85 kbit/s. The bit rate may be changed at any 20-ms frame boundary.
+
+Annex C includes an integrated C source code software package which contains the implementation of the G.722.2 encoder and decoder and its Annexes A and B and Appendix I. A set of digital test vectors for developers is provided in Annex D. These test vectors are a verification tool providing an indication of success in implementing this codec.
+
+G.722.2 AMR-WB is the same codec as the 3GPP AMR-WB. The corresponding 3GPP specifications are TS 26.190 for the speech codec and TS 26.194 for the Voice Activity Detector.
+
+## **Source**
+
+ITU-T Recommendation G.722.2 was approved on 29 July 2003 by ITU-T Study Group 16 (2001-2004) under the ITU-T Recommendation A.8 procedure.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2004
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## CONTENTS
+
+| | Page |
+|---------------------------------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 Normative references..... | 2 |
+| 3 Definitions, symbols and abbreviations..... | 2 |
+| 3.1 Definitions ..... | 2 |
+| 3.2 Symbols ..... | 3 |
+| 3.3 Abbreviations ..... | 7 |
+| 4 Outline description..... | 8 |
+| 4.1 Functional description of audio parts ..... | 8 |
+| 4.2 Preparation of speech samples..... | 8 |
+| 4.3 Principles of the adaptive multi-rate wideband speech encoder ..... | 8 |
+| 4.4 Principles of the adaptive multi-rate speech decoder ..... | 13 |
+| 4.5 Sequence and subjective importance of encoded parameters..... | 14 |
+| 5 Functional description of the encoder..... | 14 |
+| 5.1 Preprocessing..... | 14 |
+| 5.2 Linear prediction analysis and quantization ..... | 15 |
+| 5.3 Perceptual weighting ..... | 20 |
+| 5.4 Open-loop pitch analysis ..... | 20 |
+| 5.5 Impulse response computation ..... | 22 |
+| 5.6 Target signal computation ..... | 22 |
+| 5.7 Adaptive codebook..... | 23 |
+| 5.8 Algebraic codebook..... | 25 |
+| 5.9 Quantization of the adaptive and fixed codebook gains..... | 36 |
+| 5.10 Memory update..... | 37 |
+| 5.11 High-band gain generation ..... | 37 |
+| 6 Functional description of the decoder..... | 37 |
+| 6.1 Decoding and speech synthesis ..... | 38 |
+| 6.2 High-pass filtering, up-scaling and interpolation ..... | 40 |
+| 6.3 High frequency band ..... | 41 |
+| 7 Detailed bit allocation of the adaptive multi-rate wideband codec ..... | 43 |
+| 8 Homing sequences ..... | 51 |
+| 8.1 Functional description ..... | 51 |
+| 8.2 Definitions ..... | 52 |
+| 8.3 Encoder homing..... | 52 |
+| 8.4 Decoder homing ..... | 52 |
+
+| | Page |
+|--------------|--------------------------------------------------------------------------------|
+| 9 | Voice Activity Detector (VAD)..... 53 |
+| 9.1 | VAD symbols ..... 53 |
+| 9.2 | Functional description ..... 55 |
+| 10 | Mandatory AMR-WB codec modes for the speech telephony service in 3GPP ..... 62 |
+| BIBLIOGRAPHY | ..... 64 |
+
+# **Wideband coding of speech at around 16 kbit/s using Adaptive Multi-Rate Wideband (AMR-WB)**
+
+# **1 Scope**
+
+This Recommendation describes the detailed mapping from input blocks of 320 speech samples in 16-bit uniform PCM format to encoded blocks of 132, 177, 253, 285, 317, 365, 397, 461 and 477 bits and from encoded blocks of 132, 177, 253, 285, 317, 365, 397, 461 and 477 bits to output blocks of 320 reconstructed speech samples. The sampling rate is 16 000 samples/s leading to a bit rate for the encoded bit stream of 6.60, 8.85, 12.65, 14.25, 15.85, 18.25, 19.85, 23.05 or 23.85 kbit/s. The coding scheme for the multi-rate coding modes is the so-called Algebraic Code Excited Linear Prediction Coder, hereafter referred to as ACELP. The multi-rate wideband ACELP coder is referred to as AMR-WB. The codec described in this Recommendation also utilizes an integrated Voice Activity Detector (VAD).
+
+The foreseen applications for this Recommendation are the following: Voice over IP (VoIP) and Internet applications, Mobile Communications, PSTN applications, ISDN wideband telephony, ISDN videotelephony and video-conferencing.
+
+In addition to the algorithm specified in the main body of this Recommendation, Annexes A and B and Appendix I provide supplemental functionalities allowing interoperability with GSM and 3GPP wireless systems. These functionalities have originally been developed for these systems, but their use is not limited to mobile applications. Annexes D and E describe test vectors and frame structure respectively. These annexes may be implemented independently of this main body specification according to the different requirements of systems deploying the AMR-WB algorithm:
+
+- Annex A describes comfort noise aspects for use of the AMR-WB algorithm in source-controlled rate operation. The implementation of Annex A is essential for interoperability with GSM and 3GPP wireless systems.
+- Annex B describes the source-controlled rate operation for the AMR-WB algorithm. The implementation of Annex B is essential for interoperability with GSM and 3GPP wireless systems.
+- Annex D describes the digital test sequences, which are a verification tool providing an indication of success in implementing the AMR-WB codec.
+- Annex E describes the recommended frame structure for use with the different modes of operation for the AMR-WB algorithm.
+- Appendix I describes an example solution for error concealment of erroneous or lost AMR-WB frames.
+
+For better usability, the ANSI-C code with the low-level description of all these functionalities have been grouped into a single annex, Annex C. Should there be any discrepancy between the descriptions in any of the different parts of this Recommendation and the implementation of such descriptions in Annex C, the descriptions in Annex C shall prevail.
+
+In clause 8 a specific reset procedure, called codec homing, is described. This is a useful feature for bringing the codec into a known initial state (e.g., for testing purposes). Clause 9 specifies the Voice Activity Detector (VAD) used in this codec as well as in the source controlled rate operation (DTX) specified in Annex B. Clause 10 provides information on minimum requirements for support of AMR-WB modes in the 3GPP speech telephony service.
+
+# 2 Normative references
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [1] ITU-T Recommendation G.722 (1988), *7 kHz audio-coding within 64 kbit/s*.
+- [2] RFC 3267 (2002), *Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs*.
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+This Recommendation defines the following terms:
+
+**3.1.1 adaptive codebook:** The adaptive codebook contains excitation vectors that are adapted for every subframe. The adaptive codebook is derived from the long-term filter state. The lag value can be viewed as an index into the adaptive codebook.
+
+**3.1.2 algebraic codebook:** A fixed codebook where algebraic code is used to populate the excitation vectors (innovation vectors). The excitation contains a small number of non-zero pulses with predefined interlaced sets of potential positions. The amplitudes and positions of the pulses of the $k$ th excitation codevector can be derived from its index $k$ through a rule requiring no or minimal physical storage, in contrast with stochastic codebooks, whereby the path from the index to the associated codevector involves look-up tables.
+
+**3.1.3 anti-sparseness processing:** An adaptive post-processing procedure applied to the fixed codebook vector in order to reduce perceptual artifacts from a sparse fixed codebook vector.
+
+**3.1.4 closed-loop pitch analysis:** This is the adaptive codebook search, i.e. a process of estimating the pitch (lag) value from the weighted input speech and the long-term filter state. In the closed-loop search, the lag is searched using error minimization loop (analysis-by-synthesis). In the adaptive multi-rate wideband codec, closed-loop pitch search is performed for every subframe.
+
+**3.1.5 direct form coefficients:** One of the formats for storing the short-term filter parameters. In the adaptive multi-rate wideband codec, all filters which are used to modify speech samples use direct form coefficients.
+
+**3.1.6 fixed codebook:** The fixed codebook contains excitation vectors for speech synthesis filters. The contents of the codebook are non-adaptive (i.e., fixed). In the adaptive multi-rate wideband codec, the fixed codebook is implemented using an algebraic codebook.
+
+**3.1.7 fractional lags:** A set of lag values having subsample resolution. In the adaptive multirate wideband codec a sub-sample resolution of 1/4th or 1/2nd of a sample is used.
+
+**3.1.8 frame:** A time interval equal to 20 ms (320 samples at a 16-kHz sampling rate).
+
+**3.1.9 immittance spectral frequencies:** (see Immittance Spectral Pair)
+
+**3.1.10 immittance spectral pair:** Transformation of LPC parameters. Immittance Spectral Pairs are obtained by decomposing the inverse filter transfer function $A(z)$ to a set of two transfer functions, one having even symmetry and the other having odd symmetry. The Immittance Spectral
+
+Pairs (also called Immittance Spectral Frequencies) are the roots of these polynomials on the z-unit circle.
+
+**3.1.11 integer lags:** A set of lag values having whole sample resolution.
+
+**3.1.12 interpolating filter:** An FIR filter used to produce an estimate of subsample resolution samples, given an input sampled with integer sample resolution. In this implementation, the interpolating filter has low-pass filter characteristics. Thus the adaptive codebook consists of the low-pass filtered interpolated past excitation.
+
+**3.1.13 inverse filter:** This filter removes the short-term correlation from the speech signal. The filter models an inverse frequency response of the vocal tract.
+
+**3.1.14 lag:** The long-term filter delay. This is typically the true pitch period, or its multiple or submultiple.
+
+**3.1.15 LP analysis window:** For each frame, the short-term filter coefficients are computed using the high-pass filtered speech samples within the analysis window. In the adaptive multi-rate wideband codec, the length of the analysis window is always 384 samples. For all the modes, a single asymmetric window is used to generate a single set of LP coefficients. The 5-ms look-ahead is used in the analysis
+
+**3.1.16 LP coefficients:** Linear Prediction (LP) coefficients (also referred to as Linear Predictive Coding (LPC) coefficients) is a generic descriptive term for the short-term filter coefficients.
+
+**3.1.17 mode:** When used alone, refers to the source codec mode, i.e., to one of the source codecs employed in the AMR-WB codec
+
+**3.1.18 open-loop pitch search:** A process of estimating the near optimal lag directly from the weighted speech input. This is done to simplify the pitch analysis and confine the closed-loop pitch search to a small number of lags around the open-loop estimated lags. In the adaptive multi-rate wideband codec, an open-loop pitch search is performed in every other subframe.
+
+**3.1.19 residual:** The output signal resulting from an inverse filtering operation.
+
+**3.1.20 short-term synthesis filter:** This filter introduces short-term correlation into the excitation signal which models the impulse response of the vocal tract.
+
+**3.1.21 perceptual weighting filter:** This filter is employed in the analysis-by-synthesis search of the codebooks. The filter exploits the noise masking properties of the formants (vocal tract resonances) by weighting the error less in regions near the formant frequencies and more in regions away from them.
+
+**3.1.22 subframe:** A time interval equal to 5 ms (80 samples at 16-kHz sampling rate).
+
+**3.1.23 vector quantization:** A method of grouping several parameters into a vector and quantizing them simultaneously.
+
+**3.1.24 zero input response:** The output of a filter due to past inputs, i.e., due to the present state of the filter, given that an input of zeros is applied.
+
+**3.1.25 zero state response:** The output of a filter due to the present input, given that no past inputs have been applied, i.e., given that the state information in the filter is all zeros.
+
+## 3.2 Symbols
+
+This Recommendation uses the following symbols:
+
+$A(z)$ The inverse filter with unquantized coefficients
+
+$\hat{A}(z)$ The inverse filter with quantized coefficients
+
+| | |
+|-------------------------------|---------------------------------------------------------------------------------------|
+| $H(z) = \frac{1}{\hat{A}(z)}$ | The speech synthesis filter with quantized coefficients |
+| $a_i$ | The unquantized linear prediction parameters (direct form coefficients) |
+| $\hat{a}_i$ | The quantified linear prediction parameters |
+| $m$ | The order of the LP model |
+| $W(z)$ | The perceptual weighting filter (unquantized coefficients) |
+| $\gamma_1$ | The perceptual weighting factor |
+| $T$ | The integer pitch lag nearest to the closed-loop fractional pitch lag of the subframe |
+| $\beta$ | The adaptive prefilter coefficient (the quantified pitch gain) |
+| $H_{hp}(z)$ | Preprocessing high-pass filter |
+| $w(n)$ | LP analysis window |
+| $L_1$ | Length of the first part of the LP analysis window $w(n)$ |
+| $L_2$ | Length of the second part of the LP analysis window $w(n)$ |
+| $r(k)$ | The autocorrelations of the windowed speech $s'(n)$ |
+| $w_{lag}(i)$ | Lag window for the autocorrelations (60-Hz bandwidth expansion) |
+| $f_0$ | The bandwidth expansion in Hz |
+| $f_s$ | The sampling frequency in Hz |
+| $r'(k)$ | The modified (bandwidth expanded) autocorrelations |
+| $E(i)$ | The prediction error in the $i$ th iteration of the Levinson algorithm |
+| $k_i$ | The $i$ th reflection coefficient |
+| $a_j^{(i)}$ | The $j$ th direct form coefficient in the $i$ th iteration of the Levinson algorithm |
+| $F_1'(z)$ | Symmetric ISF polynomial |
+| $F_2'(z)$ | Antisymmetric ISF polynomial |
+| $F_1(z)$ | Polynomial $F_1'(z)$ |
+| $F_2(z)$ | Polynomial $F_2'(z)$ with roots $z = 1$ and $z = -1$ eliminated |
+| $q_i$ | The immittance spectral pairs (ISPs) in the cosine domain |
+| $\mathbf{q}$ | An ISP vector in the cosine domain |
+| $\hat{\mathbf{q}}_i^{(n)}$ | The quantified ISP vector at the $i$ th subframe of the frame $n$ |
+| $\omega_i$ | The immittance spectral frequencies (ISFs) |
+| $T_m(x)$ | A $m$ th order Chebyshev polynomial |
+| $f_1(i), f_2(i)$ | The coefficients of the polynomials $F_1(z)$ and $F_2(z)$ |
+| $f_1'(i), f_2'(i)$ | The coefficients of the polynomials $F_1'(z)$ and $F_2'(z)$ |
+| $f(i)$ | The coefficients of either $F_1(z)$ or $F_2(z)$ |
+
+| | |
+|-----------------------------------------|---------------------------------------------------------------------------------------|
+| $C(x)$ | Sum polynomial of the Chebyshev polynomials |
+| $x$ | Cosine of angular frequency $\omega$ |
+| $\lambda_k$ | Recursion coefficients for the Chebyshev polynomial evaluation |
+| $f_i$ | The immittance spectral frequencies (ISFs) in Hz |
+| $\mathbf{f}^t = [f_1 f_2 \dots f_{16}]$ | The vector representation of the ISFs in Hz |
+| $\mathbf{z}(n)$ | The mean-removed ISF vector at frame $n$ |
+| $\mathbf{r}(n)$ | The ISF prediction residual vector at frame $n$ |
+| $\mathbf{p}(n)$ | The predicted ISF vector at frame $n$ |
+| $\hat{\mathbf{r}}(n-1)$ | The quantified residual vector at the past frame |
+| $\hat{\mathbf{r}}_i^k$ | The quantified ISF subvector $i$ at quantization index $k$ |
+| $d_i$ | The distance between the immittance spectral frequencies $f_{i+1}$ and $f_{i-1}$ |
+| $h(n)$ | The impulse response of the weighted synthesis filter |
+| $H(z)W(z)$ | The weighted synthesis filter |
+| $T_1$ | The integer nearest to the fractional pitch lag of the previous (1st or 3rd) subframe |
+| $s'(n)$ | The windowed speech signal |
+| $s_w(n)$ | The weighted speech signal |
+| $\hat{s}(n)$ | Reconstructed speech signal |
+| $x(n)$ | The target signal for adaptive codebook search |
+| $x_2(n), \mathbf{x}_2^t$ | The target signal for algebraic codebook search |
+| $res_{LP}(n)$ | The LP residual signal |
+| $c(n)$ | The fixed codebook vector |
+| $v(n)$ | The adaptive codebook vector |
+| $y(n) = v(n) * h(n)$ | The filtered adaptive codebook vector |
+| $y_k(n)$ | The past filtered excitation |
+| $u(n)$ | The excitation signal |
+| $\hat{u}'(n)$ | The gain-scaled emphasized excitation signal |
+| $T_{op}$ | The best open-loop lag |
+| $t_{min}$ | Minimum lag search value |
+| $t_{max}$ | Maximum lag search value |
+| $R(k)$ | Correlation term to be maximized in the adaptive codebook search |
+| $R(k)_t$ | The interpolated value of $R(k)$ for the integer delay $k$ and fraction $t$ |
+| $A_k$ | Correlation term to be maximized in the algebraic codebook search at index $k$ |
+| $C_k$ | The correlation in the numerator of $A_k$ at index $k$ |
+| $E_{Dk}$ | The energy in the denominator of $A_k$ at index $k$ |
+
+| | |
+|------------------------------------------|---------------------------------------------------------------------------------------------------------------------|
+| $\mathbf{d} = \mathbf{H}^t \mathbf{x}_2$ | The correlation between the target signal $x_2(n)$ and the impulse response $h(n)$ , i.e., backward filtered target |
+| $\mathbf{H}$ | The lower triangular Toeplitz convolution matrix with diagonal $h(0)$ and lower diagonals $h(1), \dots, h(63)$ |
+| $\Phi = \mathbf{H}^t \mathbf{H}$ | The matrix of correlations of $h(n)$ |
+| $d(n)$ | The elements of the vector $\mathbf{d}$ |
+| $\phi(i, j)$ | The elements of the symmetric matrix $\Phi$ |
+| $c_k$ | The innovation vector |
+| $C$ | The correlation in the numerator of $A_k$ |
+| $m_i$ | The position of the $i$ th pulse |
+| $\vartheta_i$ | The amplitude of the $i$ th pulse |
+| $N_p$ | The number of pulses in the fixed codebook excitation |
+| $E_D$ | The energy in the denominator of $A_k$ |
+| $res_{LTP}(n)$ | The normalized long-term prediction residual |
+| $b(n)$ | The signal used for presetting the signs in algebraic codebook search |
+| $s_b(n)$ | The sign signal for the algebraic codebook search |
+| $d'(n)$ | Sign extended backward filtered target |
+| $\phi'(i, j)$ | The modified elements of the matrix $\Phi$ , including sign information |
+| $\mathbf{z}^l, z(n)$ | The fixed codebook vector convolved with $h(n)$ |
+| $E(n)$ | The mean-removed innovation energy (in dB) |
+| $\bar{E}$ | The mean of the innovation energy |
+| $\tilde{E}(n)$ | The predicted energy |
+| $[b_1 \ b_2 \ b_3 \ b_4]$ | The MA prediction coefficients |
+| $\hat{R}(k)$ | The quantified prediction error at subframe $k$ |
+| $E_I$ | The mean innovation energy |
+| $R(n)$ | The prediction error of the fixed-codebook gain quantization |
+| $E_Q$ | The quantization error of the fixed-codebook gain quantization |
+| $e(n)$ | The states of the synthesis filter $1/\hat{A}(z)$ |
+| $e_w(n)$ | The perceptually weighted error of the analysis-by-synthesis search |
+| $\eta$ | The gain scaling factor for the emphasized excitation |
+| $g_c$ | The fixed-codebook gain |
+| $g'_c$ | The predicted fixed-codebook gain |
+| $\hat{g}_c$ | The quantified fixed codebook gain |
+| $g_p$ | The adaptive codebook gain |
+| $\hat{g}_p$ | The quantified adaptive codebook gain |
+
+| | |
+|----------------------------|-------------------------------------------------------------------------|
+| $\gamma_{gc} = g_c / g_c'$ | A correction factor between the gain $g_c$ and the estimated one $g_c'$ |
+| $\hat{\gamma}_{gc}$ | The optimum value for $\gamma_{gc}$ |
+| $\gamma_{sc}$ | Gain scaling factor |
+
+## 3.3 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ACELP | Algebraic Code-Excited Linear Prediction |
+| AGC | Adaptive Gain Control |
+| AMR | Adaptive Multi-rate |
+| AMR-WB | Adaptive Multi-rate Wideband |
+| CELP | Code Excited Linear Prediction |
+| FIR | Finite Impulse Response |
+| GERAN | GSM EDGE Radio Access Network |
+| GMSK | Gaussian Modified Shift Keying |
+| ISF | Immittance Spectral Frequency |
+| ISP | Immittance Spectral Pair |
+| ISPP | Interleaved Single-Pulse Permutation |
+| LP | Linear Prediction |
+| LPC | Linear Predictive Coding |
+| LTP | Long-Term Predictor (or Long-Term Prediction) |
+| MA | Moving Average |
+| O-TCH/F | Octal TCH/Full rate: a 68.4-kbit/s gross bit-rate radio channel of GERAN-8PSK |
+| O-TCH/H | Octal-TCH/Half rate: a 32.4-kbit/s gross bit-rate radio channel of GERAN-8PSK |
+| S-MSVQ | Split-MultiStage Vector Quantization |
+| TCH | Traffic CHannel (dedicated radio channel for speech or data) |
+| TCH/F | TCH/Full rate: a 22.8-kbit/s gross bit-rate radio channel of GERAN-GMSK |
+| TCH/H | TCH/Half rate: a 11.4-kbit/s gross bit-rate radio channel of GERAN-GMSK |
+| TFO | Tandem Free Operation (Tandem Free is achieved using in-band signalling after call set-up) |
+| TrFO | Transcoder Free Operation (Tandem Free is achieved using out-of-band signalling before call set-up; the transcoders are in principle not in the communication path) |
+| UTRAN | UMTS Terrestrial Radio Access Network |
+| WB | Wideband |
+| 8PSK | 8 Phase Shift Keying |
+
+# 4 Outline description
+
+This Recommendation is structured as follows:
+
+- Clause 4.1 contains a functional description of the audio parts including the A/D and D/A functions.
+- Clause 4.2 describes input format for the AMR-WB encoder and the output format for the AMR-WB decoder.
+- Clauses 4.3 and 4.4 present a simplified description of the principles of the AMR-WB codec encoding and decoding process respectively.
+- In clause 4.5, the sequence and subjective importance of encoded parameters are given.
+- Clause 5 presents the functional description of the AMR-WB codec encoding, whereas clause 6 describes the decoding procedures.
+- In clause 7, the detailed bit allocation of the AMR-WB codec is tabulated.
+- Clause 8 describes the homing operation.
+
+## 4.1 Functional description of audio parts
+
+The analogue-to-digital and digital-to-analogue conversion will, in principle, comprise the following elements:
+
+- 1) Analogue to uniform digital PCM [1]
+ - microphone;
+ - input level adjustment device;
+ - input anti-aliasing filter;
+ - sample-hold device sampling at 16 kHz;
+ - analogue-to-uniform digital conversion to 14-bit representation.
+
+The uniform format shall be represented in two's complement.
+- 2) Uniform digital PCM to analogue [1]
+ - conversion from 14-bit/16-kHz uniform PCM to analogue;
+ - a hold device;
+ - reconstruction filter including $x/\sin(x)$ correction;
+ - output level adjustment device;
+ - earphone or loudspeaker.
+
+In the terminal equipment, the A/D function may be achieved
+
+ - by direct conversion to 14-bit uniform PCM format;
+
+For the D/A operation, the inverse operations take place.
+
+## 4.2 Preparation of speech samples
+
+The encoder is fed with data comprising samples with a resolution of 14 bits left justified in a 16-bit word. The decoder outputs data in the same format. Outside the speech codec, further processing must be applied if the traffic data occurs in a different representation.
+
+## 4.3 Principles of the adaptive multi-rate wideband speech encoder
+
+The AMR-WB codec consists of nine source codecs with bit rates of 23.85, 23.05, 19.85, 18.25, 15.85, 14.25, 12.65, 8.85 and 6.60 kbit/s.
+
+The codec is based on the code excited linear prediction (CELP) coding model. The input signal is pre-emphasized using the filter $H_{\text{pre-emph}}(z) = 1 - \mu z^{-1}$ . The CELP model is then applied to the pre-
+
+emphasized signal. A 16th-order linear prediction (LP), or short-term, synthesis filter is used which is given by:
+
+$$H(z) = \frac{1}{\hat{A}(z)} = \frac{1}{1 + \sum_{i=1}^m \hat{a}_i z^{-i}} \quad (1)$$
+
+where $\hat{a}_i, i = 1, \dots, m$ are the (quantized) linear prediction (LP) parameters, and $m = 16$ is the predictor order. The long-term, or pitch, synthesis filter is usually given by:
+
+$$\frac{1}{B(z)} = \frac{1}{1 - g_p z^{-T}} \quad (2)$$
+
+where $T$ is the pitch delay and $g_p$ is the pitch gain. The pitch synthesis filter is implemented using the so-called adaptive codebook approach.
+
+The CELP speech synthesis model is shown in Figure 1. In this model, the excitation signal at the input of the short-term LP synthesis filter is constructed by adding two excitation vectors from adaptive and fixed (innovative) codebooks. The speech is synthesized by feeding the two properly chosen vectors from these codebooks through the short-term synthesis filter. The optimum excitation sequence in a codebook is chosen using an analysis-by-synthesis search procedure in which the error between the original and synthesized speech is minimized according to a perceptually weighted distortion measure.
+
+
+
+Simplified block diagram of the CELP synthesis model. The diagram shows two input paths: an 'adaptive codebook' (represented by a waveform) and a 'fixed codebook' (represented by a grid of impulses). The adaptive codebook output is multiplied by a gain factor g\_p to produce v(n). The fixed codebook output is multiplied by a gain factor g\_c to produce c(n). These two signals are summed at a node labeled with a '+' to produce the excitation signal u(n). This signal u(n) is then filtered by an LP synthesis filter, represented by the transfer function 1/A(z), to produce the synthesized speech signal s\_hat(n). Finally, s\_hat(n) is processed by a 'post-processing' block. A dashed feedback loop connects the output s\_hat(n) back to the adaptive codebook. The diagram is labeled G.722.2\_F01.
+
+**Figure 1/G.722.2 – Simplified block diagram of the CELP synthesis model**
+
+The perceptual weighting filter used in the analysis-by-synthesis search technique is given by:
+
+$$W(z) = A(z/\gamma_1) H_{\text{de-emph}}(z) \quad (3)$$
+
+where $A(z)$ is the unquantized LP filter, $H_{\text{de-emph}} = \frac{1}{1 - 0.68z^{-1}}$ , and $\gamma_1 = 0.92$ is the perceptual weighting factor. The weighting filter uses the unquantized LP parameters.
+
+The encoder performs the analysis of the LPC, LTP and fixed codebook parameters at 12.8-kHz sampling rate. The coder operates on speech frames of 20 ms. At each frame, the speech signal is analysed to extract the parameters of the CELP model (LP filter coefficients, adaptive and fixed codebooks' indices and gains). In addition to these parameters, high-band gain indices are computed in 23.85-kbit/s mode. These parameters are encoded and transmitted. At the decoder, these parameters are decoded and speech is synthesized by filtering the reconstructed excitation signal through the LP synthesis filter.
+
+
+
+The diagram illustrates the detailed block structure of the ACELP encoder, organized into several functional stages:
+
+- preprocessing:** The **speech input** is processed through a **down-sample & HP filter** and **pre-emphasis** block.
+- frame** (consisting of **LPC analysis** and **open loop search (twice per frame)**):
+ - LPC analysis:** The signal $s(n)$ is processed through **windowing & autocorrelation**, **Levinson-Durbin**, $A(z) \rightarrow ISP$ , $ISP \rightarrow ISF$ , and **ISF quantization** to produce the **ISF index**. This is followed by **interpolation for 4 subframes** to generate the filter $\hat{A}(Z)$ .
+ - open loop search (twice per frame):** This stage involves **interpolation for 4 subframes**, **compute weighted speech**, and **find open-loop pitch**. It also feeds into the **Adaptive codebook search** via a **TO** (Target Output) block.
+- sub-frame** (consisting of **Adaptive codebook search**, **Innovative codebook search**, and **Memories update**):
+ - Adaptive codebook search:** This stage includes **compute target for adaptive codebook**, **find best delay and gain** (producing the **pitch index**), **compute adaptive codebook contribution**, **select adaptive codebook filter** (producing the **filter index**), and **compute impulse response**.
+ - Innovative codebook search:** This stage includes **compute target for innovation** (receiving $x(n)$ from the adaptive search), **find best innovation** (producing the **code index**), and **compute excitation** (receiving $x_2(n)$ from the innovation search).
+ - Memories update:** This stage includes **update filter memories for next subframe**, **compute excitation** (receiving input from the innovative search), and **gain vector quantization** (producing the **gain VQ index**).
+- Band Separation:** A dashed line separates the **Lower band** (containing the main processing blocks) from the **Higher band**.
+- Higher band:** This section includes **compute HB gain (23.85 kbit/s mode)** which produces the **High band gain index**. It also receives inputs from the **ISF quantization** and **gain vector quantization** blocks.
+
+Labels such as **speech input**, **frame**, **sub-frame**, **Lower band**, and **Higher band** are used to group related processing steps. The diagram is identified by the code **G.722.2\_F02** in the bottom right corner.
+
+Detailed block diagram of the ACELP encoder showing preprocessing, LPC analysis, open loop search, adaptive codebook search, innovative codebook search, and memories update stages across lower and higher bands.
+
+Figure 2/G.722.2 – Detailed block diagram of the ACELP encoder
+
+The signal flow at the encoder is shown in Figure 2. After decimation, high-pass and pre-emphasis filtering is performed. LP analysis is performed once per frame. The set of LP parameters is converted to immittance spectrum pairs (ISP) and vector quantized using split-multistage vector quantization (S-MSVQ). The speech frame is divided into 4 subframes of 5 ms each (64 samples at 12.8-kHz sampling rate). The adaptive and fixed codebook parameters are transmitted every subframe. The quantized and unquantized LP parameters or their interpolated versions are used depending on the subframe. An open-loop pitch lag is estimated in every other subframe or once per frame based on the perceptually weighted speech signal.
+
+The following operations are then repeated for each subframe:
+
+- The target signal $x(n)$ is computed by filtering the LP residual through the weighted synthesis filter $W(z)H(z)$ with the initial states of the filters having been updated by filtering the error between LP residual and excitation (this is equivalent to the common approach of subtracting the zero input response of the weighted synthesis filter from the weighted speech signal).
+- The impulse response $h(n)$ of the weighted synthesis filter is computed.
+- Closed-loop pitch analysis is then performed (to find the pitch lag and gain), using the target $x(n)$ and impulse response $h(n)$ , by searching around the open-loop pitch lag. Fractional pitch with 1/4th or 1/2nd of a sample resolution (depending on the mode and the pitch lag value) is used. The interpolating filter in fractional pitch search has low-pass frequency response. Further, there are two potential low-pass characteristics in the adaptive codebook and this information is encoded with 1 bit.
+- The target signal $x(n)$ is updated by removing the adaptive codebook contribution (filtered adaptive codevector), and this new target, $x_2(n)$ , is used in the fixed algebraic codebook search (to find the optimum innovation).
+- The gains of the adaptive and fixed codebook are vector quantified with 6 or 7 bits (with moving average (MA) prediction applied to the fixed codebook gain).
+- Finally, the filter memories are updated (using the determined excitation signal) for finding the target signal in the next subframe.
+
+The bit allocation of the AMR-WB codec modes is shown in Table 1. In each 20-ms speech frame, 132, 177, 253, 285, 317, 365, 397, 461 and 477 bits are produced, corresponding to a bit rate of 6.60, 8.85, 12.65, 14.25, 15.85, 18.25, 19.85, 23.05 or 23.85 kbit/s. More detailed bit allocation among the codec parameters is given in Tables 12a-12i. Note that the most significant bits (MSB) are always sent first.
+
+**Table 1/G.722.2 – Bit allocation of the AMR-WB coding algorithm for 20-ms frame**
+
+| Mode | Parameter | 1st subframe | 2nd subframe | 3rd subframe | 4th subframe | Total per frame |
+|--------------|----------------|--------------|--------------|--------------|--------------|-----------------|
+| 23.85 kbit/s | VAD-flag | | | | | 1 |
+| | ISP | | | | | 46 |
+| | LTP-filtering | 1 | 1 | 1 | 1 | 4 |
+| | Pitch delay | 9 | 6 | 9 | 6 | 30 |
+| | Algebraic code | 88 | 88 | 88 | 88 | 352 |
+| | Codebook gain | 7 | 7 | 7 | 7 | 28 |
+| | HB-energy | 4 | 4 | 4 | 4 | 16 |
+| | Total | | | | | 477 |
+
+**Table 1/G.722.2 – Bit allocation of the AMR-WB coding algorithm for 20-ms frame**
+
+| Mode | Parameter | 1st subframe | 2nd subframe | 3rd subframe | 4th subframe | Total per frame |
+|--------------|----------------|--------------|--------------|--------------|--------------|-----------------|
+| 23.05 kbit/s | VAD-flag | | | | | 1 |
+| | ISP | | | | | 46 |
+| | LTP-filtering | 1 | 1 | 1 | 1 | 4 |
+| | Pitch delay | 9 | 6 | 9 | 6 | 30 |
+| | Algebraic code | 88 | 88 | 88 | 88 | 352 |
+| | Gains | 7 | 7 | 7 | 7 | 28 |
+| | Total | | | | | 461 |
+| 19.85 kbit/s | VAD-flag | | | | | 1 |
+| | ISP | | | | | 46 |
+| | LTP-filtering | 1 | 1 | 1 | 1 | 4 |
+| | Pitch delay | 9 | 6 | 9 | 6 | 30 |
+| | Algebraic code | 72 | 72 | 72 | 72 | 288 |
+| | Codebook gain | 7 | 7 | 7 | 7 | 28 |
+| | Total | | | | | 397 |
+| 18.25 kbit/s | VAD-flag | | | | | 1 |
+| | ISP | | | | | 46 |
+| | LTP-filtering | 1 | 1 | 1 | 1 | 4 |
+| | Pitch delay | 9 | 6 | 9 | 6 | 30 |
+| | Algebraic code | 64 | 64 | 64 | 64 | 256 |
+| | Gains | 7 | 7 | 7 | 7 | 28 |
+| | Total | | | | | 365 |
+| 15.85 kbit/s | VAD-flag | | | | | 1 |
+| | ISP | | | | | 46 |
+| | LTP-filtering | 1 | 1 | 1 | 1 | 4 |
+| | Pitch delay | 9 | 6 | 9 | 6 | 30 |
+| | Algebraic code | 52 | 52 | 52 | 52 | 208 |
+| | Gains | 7 | 7 | 7 | 7 | 28 |
+| | Total | | | | | 317 |
+| 14.25 kbit/s | VAD-flag | | | | | 1 |
+| | ISP | | | | | 46 |
+| | LTP-filtering | 1 | 1 | 1 | 1 | 4 |
+| | Pitch delay | 9 | 6 | 9 | 6 | 30 |
+| | Algebraic code | 44 | 44 | 44 | 44 | 176 |
+| | Gains | 7 | 7 | 7 | 7 | 28 |
+| | Total | | | | | 285 |
+
+**Table 1/G.722.2 – Bit allocation of the AMR-WB coding algorithm for 20-ms frame**
+
+| Mode | Parameter | 1st subframe | 2nd subframe | 3rd subframe | 4th subframe | Total per frame |
+|--------------|----------------|--------------|--------------|--------------|--------------|-----------------|
+| 12.65 kbit/s | VAD-flag | | | | | 1 |
+| | ISP | | | | | 46 |
+| | LTP-filtering | 1 | 1 | 1 | 1 | 4 |
+| | Pitch delay | 9 | 6 | 9 | 6 | 30 |
+| | Algebraic code | 36 | 36 | 36 | 36 | 144 |
+| | Gains | 7 | 7 | 7 | 7 | 28 |
+| | Total | | | | | 253 |
+| 8.85 kbit/s | VAD-flag | | | | | 1 |
+| | ISP | | | | | 46 |
+| | Pitch delay | 8 | 5 | 8 | 5 | 26 |
+| | Algebraic code | 20 | 20 | 20 | 20 | 80 |
+| | Gains | 6 | 6 | 6 | 6 | 24 |
+| | Total | | | | | 177 |
+| 6.60 kbit/s | VAD-flag | | | | | 1 |
+| | ISP | | | | | 36 |
+| | Pitch delay | 8 | 5 | 5 | 5 | 23 |
+| | Algebraic code | 12 | 12 | 12 | 12 | 48 |
+| | Gains | 6 | 6 | 6 | 6 | 24 |
+| | Total | | | | | 132 |
+
+## 4.4 Principles of the adaptive multi-rate speech decoder
+
+The signal flow at the decoder is shown in Figure 3. At the decoder, the transmitted indices are extracted from the received bitstream. The indices are decoded to obtain the coder parameters at each transmission frame. These parameters are the ISP vector, the 4 fractional pitch lags, the 4 LTP filtering parameters, the 4 innovative codevectors, and the 4 sets of vector quantized pitch and innovative gains. In 23.85-kbit/s mode, also high-band gain index is decoded. The ISP vector is converted to the LP filter coefficients and interpolated to obtain LP filters at each subframe. Then, at each 64-sample subframe:
+
+- the excitation is constructed by adding the adaptive and innovative codevectors scaled by their respective gains;
+- the 12.8-kHz speech is reconstructed by filtering the excitation through the LP synthesis filter;
+- the reconstructed speech is de-emphasized.
+
+Finally, the reconstructed speech is upsampled to 16 kHz and high-band speech signal is added to the frequency band from 6 kHz to 7 kHz.
+
+
+
+Detailed block diagram of the ACELP decoder. The diagram shows the flow of data from various input indices through decoding and processing blocks to produce a speech output. Inputs include pitch index, gain VQ index, code index, ISF index, VAD flag, 16 kHz random excitation, and HB gain index. Processing blocks include decode adaptive codebook, LTP filter, decode gains, construct excitation, post-processing, synthesis filter, de-emphasis, up-sample, ISP to A(z), HB-synthesis filter, gain scaling, and BP filter. The output is the sum of the up-sampled signal and the BP filter output. A dashed line separates the 'Lower band' and 'Higher band' processing. A label 'G.722.2\_F03' is in the bottom right corner.
+
+**Figure 3/G.722.2 – Detailed block diagram of the ACELP decoder**
+
+## 4.5 Sequence and subjective importance of encoded parameters
+
+The encoder will produce the output information in a unique sequence and format, and the decoder must receive the same information in the same way. In Tables 12a-12i, the sequence of output bits and the bit allocation for each parameter is shown.
+
+The different parameters of the encoded speech and their individual bits have unequal importance with respect to subjective quality.
+
+# 5 Functional description of the encoder
+
+In this clause, the different functions of the encoder represented in Figure 2 are described.
+
+## 5.1 Preprocessing
+
+The encoder performs the analysis of the LPC, LTP and fixed codebook parameters at 12.8-kHz sampling rate. Therefore, the input signal has to be decimated from 16 kHz to 12.8 kHz. The decimation is performed by first upsampling by 4, then filtering the output through low-pass FIR filter $H_{\text{decim}}(z)$ that has the cut-off frequency at 6.4 kHz. Then, the signal is downsampled by 5. The filtering delay is compensated by adding zeros into the end of the input vector.
+
+After the decimation, two preprocessing functions are applied to the signal prior to the encoding process: high-pass filtering and pre-emphasizing (and signal down-scaling).
+
+(Down-scaling consists of dividing the input by a factor of 2 to reduce the possibility of overflows in the fixed-point implementation.)
+
+The high-pass filter serves as a precaution against undesired low frequency components. A filter at a cut-off frequency of 50 Hz is used, and it is given by:
+
+$$H_{h1}(z) = \frac{0.989502 - 1.979004z^{-1} + 0.989502z^{-2}}{1 - 1.978882z^{-1} + 0.9799126z^{-2}} \quad (4)$$
+
+(Both down-scaling and high-pass filtering are combined by dividing the coefficients at the numerator of $H_{hl}(z)$ by 2.)
+
+In the pre-emphasis, a first order high-pass filter is used to emphasize higher frequencies, and it is given by:
+
+$$H_{\text{pre-emph}}(z) = 1 - 0.68z^{-1} \quad (5)$$
+
+## 5.2 Linear prediction analysis and quantization
+
+Short-term prediction, or LP, analysis is performed once per speech frame using the autocorrelation approach with 30-ms asymmetric windows. An overhead of 5 ms is used in the autocorrelation computation. The frame structure is depicted below.
+
+
+
+Diagram illustrating the frame structure for LP analysis. It shows a sequence of 16 subframes, each 5 ms long, totaling 80 ms (4 x 5 ms). The first subframe is labeled 'frame n-1' and the second is 'frame n'. The third subframe is labeled 'frame n (4 x 5 ms)'. The fourth subframe is highlighted in black, indicating the center of the asymmetric window used for LP analysis.
+
+The autocorrelations of windowed speech are converted to the LP coefficients using the Levinson-Durbin algorithm. Then the LP coefficients are transformed to the ISP domain for quantization and interpolation purposes. The interpolated quantized and unquantized filters are converted back to the LP filter coefficients (to construct the synthesis and weighting filters at each subframe).
+
+### 5.2.1 Windowing and autocorrelation computation
+
+LP analysis is performed once per frame using an asymmetric window. The window has its weight concentrated at the fourth subframe and it consists of two parts: the first part is a half of a Hamming window and the second part is a quarter of a Hamming-cosine function cycle. The window is given by:
+
+$$\begin{aligned} w(n) &= 0.54 - 0.46 \cos\left(\frac{2\pi n}{2L_1 - 1}\right), & n &= 0, \dots, L_1 - 1 \\ &= \cos\left(\frac{2\pi(n - L_1)}{4L_2 - 1}\right), & n &= L_1, \dots, L_1 + L_2 - 1 \end{aligned} \quad (6)$$
+
+where the values $L_1 = 256$ and $L_2 = 128$ are used.
+
+The autocorrelations of the windowed speech $s'(n)$ , $n = 0, \dots, 383$ are computed by:
+
+$$r(k) = \sum_{n=k}^{383} s'(n)s'(n-k), \quad k = 0, \dots, 16 \quad (7)$$
+
+and a 60-Hz bandwidth expansion is used by lag windowing the autocorrelations using the window [3]:
+
+$$w_{\text{lag}}(i) = \exp\left[-\frac{1}{2}\left(\frac{2\pi f_0 i}{f_s}\right)^2\right], \quad i = 1, \dots, 16 \quad (8)$$
+
+where $f_0 = 60$ Hz is the bandwidth expansion and $f_s = 12\,800$ Hz is the sampling frequency. Further, $r(0)$ is multiplied by the white noise correction factor 1.0001 which is equivalent to adding a noise floor at $-40$ dB.
+
+### 5.2.2 Levinson-Durbin algorithm
+
+The modified autocorrelations $r'(0)=1.0001r(0)$ and $r'(k)=r(k)w_{lag}(k), k=1,\dots,16$ , are used to obtain the LP filter coefficients $a_k, k=1,\dots,16$ by solving the set of equations.
+
+$$\sum_{k=1}^{16} a_k r'(i-k) = -r'(i), \quad i=1,\dots,16 \quad (9)$$
+
+The set of equations in (9) is solved using the Levinson-Durbin algorithm [3]. This algorithm uses the following recursion:
+
+$$E(0) = r'(0)$$
+
+For $i=1$ to 16 do
+
+$$k_i = -\left[r'(i) + \sum_{j=1}^{i-1} a_j^{i-1} r'(i-j)\right] / E(i-1)$$
+
+$$a_i^{(i)} = k_i$$
+
+For $j=1$ to $i-1$ do
+
+$$a_j^{(i)} = a_j^{(i-1)} + k_i a_{i-j}^{(i-1)}$$
+
+$$E(i) = (1 - k_i^2) E(i-1)$$
+
+The final solution is given as $a_j = a_j^{(16)}, j=1,\dots,16$ .
+
+The LP filter coefficients are converted to the ISP representation [5] for quantization and interpolation purposes. The conversions to the ISP domain and back to the LP filter domain are described in 5.2.3 and 5.2.4.
+
+### 5.2.3 LP to ISP conversion
+
+The LP filter coefficients $a_k, k=1,\dots,16$ , are converted to the ISP representation for quantization and interpolation purposes. For a 16th-order LP filter, the ISPs are defined as the roots of the sum and difference polynomials:
+
+$$f_1'(z) = A(z) + z^{-16} A(z^{-1}) \quad (10)$$
+
+and:
+
+$$f_2'(z) = A(z) - z^{-16} A(z^{-1}) \quad (11)$$
+
+respectively. (The polynomials $f_1'(z)$ and $f_2'(z)$ are symmetric and antisymmetric, respectively.) It can be proven that all roots of these polynomials are on the unit circle and they alternate each other [6]. $f_2'(z)$ has two roots at $z=1$ ( $\omega=0$ ) and $z=-1$ ( $\omega=\pi$ ). To eliminate these two roots, we define the new polynomials:
+
+$$f_1(z) = f_1'(z) \quad (12)$$
+
+and:
+
+$$f_2(z) = f_2'(z) / (1 - z^{-2}) \quad (13)$$
+
+Polynomials $f_1(z)$ and $f_2(z)$ have 8 and 7 conjugate roots on the unit circle $(e^{\pm j\omega_i})$ , respectively. Therefore, the polynomials can be written as:
+
+$$F_1(z) = (1 + a[16]) \prod_{i=0,2,\dots,14} (1 - 2q_i z^{-1} + z^{-2}) \quad (14)$$
+
+and
+
+$$F_2(z) = (1 + a[16]) \prod_{i=1,3,\dots,13} (1 - 2q_i z^{-1} + z^{-2}) \quad (15)$$
+
+where $q_i = \cos(\omega_i)$ with $\omega_i$ being the immittance spectral frequencies (ISF) and $a[16]$ is the last predictor coefficient. ISFs satisfy the ordering property $0 < \omega_1 < \omega_2 < \dots < \omega_{16} < \pi$ . We refer to $q_i$ as the ISPs in the cosine domain.
+
+Since both polynomials $f_1(z)$ and $f_2(z)$ are symmetric, only the first 8 and 7 coefficients of each polynomial, respectively, and the last predictor coefficient need to be computed.
+
+The coefficients of these polynomials are found by the recursive relations:
+
+for $i = 0$ to 7
+
+$$\begin{aligned} f_1(i) &= a_i + a_{m-i} \\ f_2(i) &= a_i - a_{m-i} + f_2(i-2) \\ f_1(8) &= 2a_8 \end{aligned} \quad (16)$$
+
+where $m = 16$ is the predictor order, and $f_2(-2) = f_2(-1) = 0$ .
+
+The ISPs are found by evaluating the polynomials $F_1(z)$ and $F_2(z)$ at 100 points equally spaced between 0 and $\pi$ and checking for sign changes. A sign change signifies the existence of a root and the sign change interval is then divided 4 times to better track the root. The Chebyshev polynomials are used to evaluate $F_1(z)$ and $F_2(z)$ [7]. In this method the roots are found directly in the cosine domain $\{q_i\}$ . The polynomials $F_1(z)$ and $F_2(z)$ evaluated at $z = e^{j\omega}$ can be written as:
+
+$$F_1(\omega) = 2e^{-j8\omega} C_1(x) \text{ and } F_2(\omega) = 2e^{-j7\omega} C_2(x) \quad (17)$$
+
+with:
+
+$$C_1(x) = \sum_{i=0}^7 f_1(i) T_{8-i}(x) + f_1(8)/2 \text{ and } C_2(x) = \sum_{i=0}^6 f_2(i) T_{8-i}(x) + f_2(7)/2 \quad (18)$$
+
+where $T_m = \cos(m\omega)$ is the $m$ th order Chebyshev polynomial, $f(i)$ are the coefficients of either $F_1(z)$ or $F_2(z)$ , computed using the equations in (16). The polynomial $C(x)$ is evaluated at a certain value of $x = \cos(\omega)$ using the recursive relation:
+
+for $k = n_f - 1$ down to 1
+
+$$b_k = 2xb_{k+1} - b_{k+2} + f(n_f - k)$$
+
+end
+
+$$C(x) = xb_1 - b_2 + f(n_f)/2$$
+
+where $n_f = 8$ in case of $C_1(x)$ and $n_f = 7$ in case of $C_2(x)$ , with initial values $b_{n_f} = f(0)$ and $b_{n_f+1} = 0$ . The details of the Chebyshev polynomial evaluation method are found in [7].
+
+### 5.2.4 ISP to LP conversion
+
+Once the ISPs are quantized and interpolated, they are converted back to the LP coefficient domain $\{a_k\}$ . The conversion to the LP domain is done as follows. The coefficients of $F_1(z)$ and $F_2(z)$ are found by expanding Equations (14) and (15) knowing the quantized and interpolated ISPs $q_i$ , $i = 0, \dots, m-1$ , where $m = 16$ . The following recursive relation is used to compute $f_1(z)$ :
+
+for $i = 2$ to $m/2$
+
+$$f_1(i) = -2q_{2i-2}f_1(i-1) + 2f_1(i-2)$$
+
+for $j = i-1$ down to $2$
+
+$$f_1(j) = f_1(j) - 2q_{2i-2}f_1(j-1) + f_1(j-2)$$
+
+end
+
+$$f_1(1) = f_1(1) - 2q_{2i-2}$$
+
+end
+
+with initial values $f_1(0) = 1$ and $f_1(1) = -2q_0$ . The coefficients $f_2(i)$ are computed similarly by replacing $q_{2i-2}$ by $q_{2i-1}$ and $m/2$ by $m/2-1$ , and with initial conditions $f_2(0) = 1$ and $f_2(1) = -2q_1$ .
+
+Once the coefficients $f_1(z)$ and $f_2(z)$ are found, $F_2(z)$ is multiplied by $1-z^{-2}$ , to obtain $F'_2(z)$ ; that is:
+
+$$\begin{aligned} f'_2(i) &= f_2(i) - f_2(i-2), & i &= 2, \dots, m/2-1 \\ f'_1(i) &= f_1(i) & i &= 0, \dots, m/2 \end{aligned} \quad (19)$$
+
+Then $F'_1(z)$ and $F'_2(z)$ are multiplied by $1+q_{m-1}$ and $1-q_{m-1}$ , respectively. That is:
+
+$$\begin{aligned} f'_2(i) &= (1-q_{m-1})f'_2(i), & i &= 0, \dots, m/2-1 \\ f'_1(i) &= (1+q_{m-1})f'_1(i) & i &= 0, \dots, m/2 \end{aligned}$$
+
+Finally the LP coefficients are found by:
+
+$$\begin{aligned} a_i &= 0.5f'_1(i) + 0.5f'_2(i), & i &= 1, \dots, m/2-1 \\ &0.5f'_1(i) - 0.5f'_2(i), & i &= m/2+1, \dots, m-1 \\ &0.5f'_1(m/2), & i &= m/2 \\ &q_{m-1}, & i &= m \end{aligned} \quad (20)$$
+
+This is directly derived from the relation $A(z) = (F'_1(z) + F'_2(z))/2$ , and considering the fact that $F'_1(z)$ and $F'_2(z)$ are symmetric and antisymmetric polynomials, respectively.
+
+### 5.2.5 Quantization of the ISP coefficients
+
+The LP filter coefficients are quantized using the ISP representation in the frequency domain; that is:
+
+$$\begin{aligned} f_i &= \frac{f_s}{2\pi} \arccos(q_i), & i &= 0, \dots, 14 \\ &= \frac{f_s}{4\pi} \arccos(q_i), & i &= 15 \end{aligned} \quad (21)$$
+
+where $f_i$ are the ISFs in Hz [0, 6400] and $f_s = 12800$ is the sampling frequency. The ISF vector is given by $\mathbf{f}^t = [f_0, f_1, \dots, f_{15}]$ , with $t$ denoting transpose.
+
+A 1st-order MA prediction is applied, and the residual ISF vector is quantified using a combination of split vector quantization (SVQ) and multistage vector quantization (MSVQ). The prediction and quantization are performed as follows. Let $\mathbf{z}(n)$ denote the mean-removed ISF vector at frame $n$ . The prediction residual vector $\mathbf{r}(n)$ is given by:
+
+$$\mathbf{r}(n) = \mathbf{z}(n) - \mathbf{p}(n) \quad (22)$$
+
+where $\mathbf{p}(n)$ is the predicted LSF vector at frame $n$ . First-order MA prediction is used where:
+
+$$\mathbf{p}(n) = \frac{1}{3} \hat{\mathbf{r}}(n-1) \quad (23)$$
+
+where $\hat{\mathbf{r}}(n-1)$ is the quantized residual vector at the past frame.
+
+The ISF residual vector $\mathbf{r}$ is quantized using split-multistage vector quantization S-MSVQ. The vector is split into 2 subvectors $\mathbf{r}_1(n)$ and $\mathbf{r}_2(n)$ of dimensions 9 and 7, respectively. The 2 subvectors are quantized in two stages. In the first stage $\mathbf{r}_1(n)$ is quantized with 8 bits and $\mathbf{r}_2(n)$ with 8 bits.
+
+For 8.85-, 12.65-, 14.25-, 15.85-, 18.25-, 19.85-, 23.05- or 23.85-kbit/s modes, the quantization error vectors $\mathbf{r}_i^{(2)} = \mathbf{r}_i - \hat{\mathbf{r}}_i, i = 1, 2$ are split in the next stage into 3 and 2 subvectors, respectively. The subvectors are quantized using the bit rates described in Table 2.
+
+**Table 2/G.722.2 – Quantization of ISP vector for the 8.85-, 12.65-, 14.25-, 15.85-, 18.25-, 19.85-, 23.05- or 23.85-kbit/s modes**
+
+| 1) Unquantized 16-element-long ISP vector | | | | |
+|------------------------------------------------------|------------------------------------------------------|------------------------------------------------------|------------------------------------------------------|------------------------------------------------------|
+| 2) Stage 1 ( $\mathbf{r}_1$ ) 8 bits | | | 2) Stage 1 ( $\mathbf{r}_2$ ) 8 bits | |
+| 3) Stage 2 $(\mathbf{r}^{(2)}_{1,0-2})$ 6 bits | 3) Stage 2 $(\mathbf{r}^{(2)}_{1,3-5})$ 7 bits | 3) Stage 2 $(\mathbf{r}^{(2)}_{1,6-8})$ 7 bits | 3) Stage 2 $(\mathbf{r}^{(2)}_{2,0-2})$ 5 bits | 3) Stage 2 $(\mathbf{r}^{(2)}_{2,3-6})$ 5 bits |
+
+For 6.60-kbit/s mode, the quantization error vectors $\mathbf{r}_i^{(2)} = \mathbf{r}_i - \hat{\mathbf{r}}_i, i = 1, 2$ are split in the next stage into 2 and 1 subvectors, respectively. The subvectors are quantized using the bit rates described in Table 3.
+
+**Table 3/G.722.2 – Quantization of ISP vector for the 6.60 kbit/s mode**
+
+| 1) Unquantized 16-element-long ISP vector | | |
+|------------------------------------------------------|------------------------------------------------------|------------------------------------------------------|
+| 2) Stage 1 ( $\mathbf{r}_1$ ) 8 bits | | 2) Stage 1 ( $\mathbf{r}_2$ ) 8 bits |
+| 3) Stage 2 $(\mathbf{r}^{(2)}_{1,0-4})$ 7 bits | 3) Stage 2 $(\mathbf{r}^{(2)}_{1,5-8})$ 7 bits | 3) Stage 2 $(\mathbf{r}^{(2)}_{2,0-6})$ 6 bits |
+
+A squared error ISP distortion measure is used in the quantization process. In general, for an input ISP or error residual subvector $\mathbf{r}_i, i = 1, 2$ and a quantized vector at index $k$ , $\hat{\mathbf{r}}_i^k$ , the quantization is performed by finding the index $k$ which minimizes:
+
+$$E = \sum_{i=m}^n [r_i - \hat{r}_i^k]^2 \quad (24)$$
+
+where $m$ and $n$ are the first and last elements of the subvector.
+
+### 5.2.6 Interpolation of the ISPs
+
+The set of quantized (and unquantized) LP parameters is used for the fourth subframe whereas the first, second, and third subframes use a linear interpolation of the parameters in the adjacent frames. The interpolation is performed on the ISPs in the $\mathbf{q}$ domain. Let $\hat{\mathbf{q}}_4^{(n)}$ be the ISP vector at the 4th
+
+subframe of the frame, and $\hat{\mathbf{q}}_4^{(n-1)}$ the ISP vector at the 4th subframe of the past frame $n-1$ . The interpolated ISP vectors at the 1st, 2nd, and 3rd subframes are given by:
+
+$$\begin{aligned}\hat{\mathbf{q}}_1^{(n)} &= 0.55\hat{\mathbf{q}}_4^{(n-1)} + 0.45\hat{\mathbf{q}}_4^{(n)} \\ \hat{\mathbf{q}}_2^{(n)} &= 0.2\hat{\mathbf{q}}_4^{(n-1)} + 0.8\hat{\mathbf{q}}_4^{(n)} \\ \hat{\mathbf{q}}_3^{(n)} &= 0.04\hat{\mathbf{q}}_4^{(n-1)} + 0.96\hat{\mathbf{q}}_4^{(n)}\end{aligned}$$
+
+The same formula is used for interpolation of the unquantized ISPs. The interpolated ISP vectors are used to compute a different LP filter at each subframe (both quantized and unquantized) using the ISP to LP conversion method described in 5.2.4.
+
+## 5.3 Perceptual weighting
+
+The traditional perceptual weighting filter $W(z) = A(z/\gamma_1)/A(z/\gamma_2)$ has inherent limitations in modelling the formant structure and the required spectral tilt concurrently. The spectral tilt is more pronounced in wideband signals due to the wide dynamic range between low and high frequencies. A solution to this problem is to introduce the pre-emphasis filter at the input, compute the LP filter $A(z)$ based on the pre-emphasized speech $s(n)$ , and use a modified filter $W(z)$ by fixing its denominator. This structure substantially decouples the formant weighting from the tilt.
+
+A weighting filter of the form $W(z) = A(z/\gamma_1)H_{\text{de-emph}}(z)$ is used, where $H_{\text{de-emph}} = \frac{1}{1 - \beta_1 z^{-1}}$ and $\beta_1 = 0.68$ .
+
+Because $A(z)$ is computed based on the pre-emphasized speech signal $s(n)$ , the tilt of the filter $1/A(z/\gamma_1)$ is less pronounced compared to the case when $A(z)$ is computed based on the original speech. Since de-emphasis is performed at the decoder end, it can be shown that the quantization error spectrum is shaped by a filter having a transfer function $W^{-1}(z)H_{\text{de-emph}}(z) = 1/A(z/\gamma_1)$ . Thus, the spectrum of the quantization error is shaped by a filter whose transfer function is $1/A(z/\gamma_1)$ , with $A(z)$ computed based on the pre-emphasized speech signal.
+
+## 5.4 Open-loop pitch analysis
+
+Depending on the mode, open-loop pitch analysis is performed once per frame (each 20 ms) or twice per frame (each 10 ms) to find two estimates of the pitch lag in each frame. This is done in order to simplify the pitch analysis and confine the closed loop pitch search to a small number of lags around the open-loop estimated lags.
+
+Open-loop pitch estimation is based on the weighted speech signal $s_w(n)$ which is obtained by filtering the input speech signal through the weighting filter $W(z) = A(z/\gamma_1)H_{\text{de-emph}}(z)$ , where
+
+$H_{\text{de-emph}} = \frac{1}{1 - \beta_1 z^{-1}}$ and $\beta_1 = 0.68$ . That is, in a subframe of size $L$ , the weighted speech is given by:
+
+$$s_w(n) = s(n) + \sum_{i=1}^{16} a_i \gamma_1^i s(n-i) + \beta_1 s_w(n-1), \quad n = 0, \dots, L-1 \quad (25)$$
+
+The open-loop pitch analysis is performed to a signal decimated by two. The decimated signal is obtained by filtering $s_w(n)$ through a fourth-order FIR filter $H_{\text{decim2}}(z)$ and then downsampling the output by two to obtain the signal $s_{wd}(n)$ .
+
+### 5.4.1 6.60-kbit/s mode
+
+Open-loop pitch analysis is performed once per frame (every 20 ms) to find an estimate of the pitch lag in each frame.
+
+The open-loop pitch analysis is performed as follows. First, the correlation of decimated weighted speech is determined for each pitch lag value $d$ by:
+
+$$C(d) = \sum_{n=0}^{128} s_{wd}(n)s_{wd}(n-d)w(d), \quad d = 17, \dots, 115 \quad (26)$$
+
+where $w(d)$ is a weighting function. The estimated pitch lag is the delay that maximizes the weighted correlation function $C(d)$ . The weighting emphasises lower pitch lag values reducing the likelihood of selecting a multiple of the correct delay. The weighting function consists of two parts: a low pitch lag emphasis function, $w_l(d)$ , and a previous frame lag neighbouring emphasis function, $w_n(d)$ :
+
+$$w(d) = w_l(d)w_n(d) \quad (27)$$
+
+The low pitch lag emphasis function is given by:
+
+$$w_l(d) = cw(d) \quad (28)$$
+
+where $cw(d)$ is defined by a table in the fixed-point computational description. The previous frame lag neighbouring emphasis function depends on the pitch lag of previous speech frames:
+
+$$w_n(d) = \begin{cases} cw(|T_{old} - d| + 98), & v > 0.8 \\ 1.0, & \text{otherwise} \end{cases} \quad (29)$$
+
+where $T_{old}$ is the median filtered pitch lag of 5 previous voiced speech half-frames and $v$ is an adaptive parameter. If the frame is classified as voiced by having the open-loop gain $g > 0.6$ , then the $v$ -value is set to 1.0 for the next frame. Otherwise, the $v$ -value is updated by $v = 0.9v$ . The open loop gain is given by:
+
+$$g = \frac{\sum_{n=0}^{127} s_{wd}(n)s_{wd}(n-d_{max})}{\sqrt{\sum_{n=0}^{127} s_{wd}^2(n) \sum_{n=0}^{127} s_{wd}^2(n-d_{max})}} \quad (30)$$
+
+where $d_{max}$ is the pitch delay that maximizes $C(d)$ . The median filter is updated only during voiced speech frames. The weighting depends on the reliability of the old pitch lags. If previous frames have contained unvoiced speech or silence, the weighting is attenuated through the parameter $v$ .
+
+### 5.4.2 8.85-, 12.65-, 14.25-, 15.85-, 18.25-, 19.85-, 23.05- and 23.85-kbit/s modes
+
+Open-loop pitch analysis is performed twice per frame (every 10 ms) to find two estimates of the pitch lag in each frame.
+
+The open-loop pitch analysis is performed as follows. First, the correlation of decimated weighted speech is determined for each pitch lag value $d$ by:
+
+$$C(d) = \sum_{n=0}^{63} s_{wd}(n)s_{wd}(n-d)w(d), \quad d = 17, \dots, 115 \quad (31)$$
+
+where $w(d)$ is a weighting function. The estimated pitch lag is the delay that maximizes the weighted correlation function $C(d)$ . The weighting emphasises lower pitch-lag values reducing the likelihood of selecting a multiple of the correct delay. The weighting function consists of two parts:
+
+a low pitch lag emphasis function, $w_l(d)$ , and a previous frame lag neighbouring emphasis function, $w_n(d)$ :
+
+$$w(d) = w_l(d)w_n(d) \quad (32)$$
+
+The low pitch lag emphasis function is given by:
+
+$$w_l(d) = cw(d) \quad (33)$$
+
+where $cw(d)$ is defined by a table in the fixed point computational description. The previous frame lag neighbouring emphasis function depends on the pitch lag of previous speech frames:
+
+$$w_n(d) = \begin{cases} cw(|T_{old} - d| + 98), & v > 0.8, \\ 1.0, & \text{otherwise} \end{cases} \quad (34)$$
+
+where $T_{old}$ is the median filtered pitch lag of 5 previous voiced speech half-frames and $v$ is an adaptive parameter. If the frame is classified as voiced by having the open-loop gain $g > 0.6$ , then the $v$ -value is set to 1.0 for the next frame. Otherwise, the $v$ -value is updated by $v = 0.9v$ . The open loop gain is given by:
+
+$$g = \frac{\sum_{n=0}^{63} s_{wd}(n)s_{wd}(n - d_{max})}{\sqrt{\sum_{n=0}^{63} s_{wd}^2(n) \sum_{n=0}^{63} s_{wd}^2(n - d_{max})}} \quad (35)$$
+
+where $d_{max}$ is the pitch delay that maximizes $C(d)$ . The median filter is updated only during voiced speech frames. The weighting depends on the reliability of the old pitch lags. If previous frames have contained unvoiced speech or silence, the weighting is attenuated through the parameter $v$ .
+
+## 5.5 Impulse response computation
+
+The impulse response, $h(n)$ , of the weighted synthesis filter $H(z)W(z) = A(z/\gamma_1)H_{\text{de-emph}}(z)/\hat{A}(z)$ is computed each subframe. This impulse response is needed for the search of adaptive and fixed codebooks. The impulse response $h(n)$ is computed by filtering the vector of coefficients of the filter $A(z/\gamma_1)$ extended by zeros through the two filters $1/\hat{A}(z)$ and $H_{\text{de-emph}}(z)$ .
+
+## 5.6 Target signal computation
+
+The target signal for adaptive codebook search is usually computed by subtracting the zero-input response of the weighted synthesis filter $H(z)W(z) = A(z/\gamma_1)H_{\text{de-emph}}(z)/\hat{A}(z)$ from the weighted speech signal $s_w(n)$ . This is performed on a subframe basis.
+
+An equivalent procedure for computing the target signal, which is used in this codec, is the filtering of the LP residual signal $r(n)$ through the combination of synthesis filter $1/\hat{A}(z)$ and the weighting filter $A(z/\gamma_1)H_{\text{de-emph}}(z)$ . After determining the excitation for the subframe, the initial states of these filters are updated by filtering the difference between the LP residual and excitation. The memory update of these filters is explained in 5.10.
+
+The residual signal $r(n)$ which is needed for finding the target vector is also used in the adaptive codebook search to extend the past excitation buffer. This simplifies the adaptive codebook search procedure for delays less than the subframe size of 64 as will be explained in 5.7. The LP residual is given by:
+
+$$r(n) = s(n) = \sum_{i=1}^{16} \hat{a}_i s(n-i), \quad n = 0, \dots, 63 \quad (36)$$
+
+## 5.7 Adaptive codebook
+
+Adaptive codebook search is performed on a subframe basis. It consists of performing closed loop pitch search, and then computing the adaptive codevector by interpolating the past excitation at the selected fractional pitch lag.
+
+The adaptive codebook parameters (or pitch parameters) are the delay and gain of the pitch filter. In the search stage, the excitation is extended by the LP residual to simplify the closed-loop search.
+
+In 12.65-, 14.25-, 15.85-, 18.25-, 19.85-, 23.05- or 23.85-kbit/s modes, in the first and third subframes, a fractional pitch delay is used with resolutions 1/4 in the range [34, 1273 /4], resolutions 1/2 in the range [128, 1591 /2], and integers only in the range [160, 231]. For the second and fourth subframes, a pitch resolution of 1/4 is always used in the range [T1 -8, T1 +73 /4], where T1 is nearest integer to the fractional pitch lag of the previous (1st or 3rd) subframe.
+
+In 8.85-kbit/s mode, in the first and third subframes, a fractional pitch delay is used with resolutions 1/2 in the range [34, 911 /2], and integers only in the range [92, 231]. For the second and fourth subframes, a pitch resolution of 1/2 is always used in the range [T1 -8, T1 +71 /2], where T1 is nearest integer to the fractional pitch lag of the previous (1st or 3rd) subframe.
+
+In 6.60-kbit/s mode, in the first subframe, a fractional pitch delay is used with resolutions 1/2 in the range [34, 911 /2], and integers only in the range [92, 231]. For the second, third and fourth subframes, a pitch resolution of 1/2 is always used in the range [T1 -8, T1 +71 /2], where T1 is nearest integer to the fractional pitch lag of the first subframe.
+
+Closed-loop pitch analysis is performed around the open-loop pitch estimates on a subframe basis. In 8.85-, 12.65-, 14.25-, 15.85-, 18.25-, 19.85-, 23.05- or 23.85-kbit/s modes, in the first (and third) subframe the range Top ± 7, bounded by 34...231, is searched. In 6.60-kbit/s mode, in the first subframe the range Top ± 7, bounded by 34...231, is searched. For all the modes, for the other subframes, closed-loop pitch analysis is performed around the integer pitch selected in the previous subframe, as described above. In 12.65-, 14.25-, 15.85-, 18.25-, 19.85-, 23.05- or 23.85-kbit/s modes, the pitch delay is encoded with 9 bits in the first and third subframes and the relative delay of the other subframes is encoded with 6 bits. In 8.85-kbit/s mode, the pitch delay is encoded with 8 bits in the first and third subframes and the relative delay of the other subframes is encoded with 5 bits. In 6.60 kbit/s mode, the pitch delay is encoded with 8 bits in the first subframe and the relative delay of the other subframes is encoded with 5 bits.
+
+The closed loop pitch search is performed by minimizing the mean-square weighted error between the original and synthesized speech. This is achieved by maximizing the term:
+
+$$T_k = \frac{\sum_{n=0}^{63} x(n)y_k(n)}{\sqrt{\sum_{n=0}^{63} y_k(n)y_k(n)}} \quad (37)$$
+
+where $x(n)$ is the target signal and $y_k(n)$ is the past filtered excitation at delay $k$ (past excitation convolved with $h(n)$ ). Note that the search range is limited around the open-loop pitch as explained earlier.
+
+The convolution $y_k(n)$ is computed for the first delay in the searched range, and for the other delays, it is updated using the recursive relation:
+
+$$y_k(n) = y_{k-1}(n-1) + u(-k)h(n) \quad (38)$$
+
+where $u(n)$ , $n = -(231+17), \dots, 63$ , is the excitation buffer. Note that in search stage, the samples $u(n)$ , $n = 0, \dots, 63$ , are not known, and they are needed for pitch delays less than 64. To simplify the search, the LP residual is copied to $u(n)$ in order to make the relation in Equation (38) valid for all delays.
+
+Once the optimum integer pitch delay is determined, the fractions from $-\frac{3}{4}$ to $\frac{3}{4}$ with a step of $\frac{1}{4}$ around that integer are tested. The fractional pitch search is performed by interpolating the normalized correlation in Equation (37) and searching for its maximum. Once the fractional pitch lag is determined, $v'(n)$ is computed by interpolating the past excitation signal $u(n)$ at the given phase (fraction). (The interpolation is performed using two FIR filters (Hamming windowed sinc functions); one for interpolating the term in Equation (37) with the sinc truncated at $\pm 17$ and the other for interpolating the past excitation with the sinc truncated at $\pm 63$ .) The filters have their cut-off frequency ( $-3$ dB) at 6000 Hz in the oversampled domain, which means that the interpolation filters exhibit low-pass frequency response. Thus, even when the pitch delay is an integer value, the adaptive codebook excitation consists of a low-pass filtered version of the past excitation at the given delay and not a direct copy thereof. Further, for delays smaller than the subframe size, the adaptive codebook excitation is completed based on the low-pass filtered interpolated past excitation and not by repeating the past excitation.
+
+In order to enhance the pitch prediction performance in wideband signals, a frequency-dependent pitch predictor is used. This is important in wideband signals since the periodicity does not necessarily extend over the whole spectrum. In this algorithm, there are two signal paths associated to respective sets of pitch codebook parameters, wherein each signal path comprises a pitch prediction error calculating device for calculating a pitch prediction error of a pitch codevector from a pitch codebook search device. One of these two paths comprises a low-pass filter for filtering the pitch codevector and the pitch prediction error is calculated for these two signal paths. The signal path having the lowest calculated pitch prediction error is selected, along with the associated pitch gain.
+
+The low-pass filter used in the second path is in the form $B_{LP}(z) = 0.18z + 0.64 + 0.18z^{-1}$ . Note that 1 bit is used to encode the chosen path.
+
+Thus, for 8.85-, 12.65-, 14.25-, 15.85-, 18.25-, 19.85-, 23.05- or 23.85-kbit/s modes, there are two possibilities to generate the adaptive codebook $v(n)$ , $v(n) = v'(n)$ in the first path, or $v(n) = \sum_{i=1}^1 b_{LP}(i+1)v'(n+i)$ in the second path, where $\mathbf{b}_{LP} = [0.18, 0.64, 0.18]$ . The path which results in minimum energy of the target signal $x_2(n)$ defined in Equation (40) is selected for the filtered adaptive codebook vector. For 6.60-kbit/s mode, $v(n)$ is always:
+
+$$v(n) = \sum_{i=1}^1 b_{LP}(i+1)v'(n+i)$$
+
+The adaptive codebook gain is then found by:
+
+$$g_p = \frac{\sum_{n=0}^{63} x(n)y(n)}{\sqrt{\sum_{n=0}^{63} y(n)y(n)}}, \quad \text{bounded by } 0 \leq g_p \leq 1.2 \quad (39)$$
+
+where $y(n) = v(n)*h(n)$ is the filtered adaptive codebook vector (zero-state response of $H(z)W(z)$ to $v_i(n)$ ). To insure stability, the adaptive codebook gain $g_p$ is bounded by 0.95, if the adaptive codebook gains of the previous subframes have been small and the LP filters of the previous subframes have been close to being unstable.
+
+## 5.8 Algebraic codebook
+
+### 5.8.1 Codebook structure
+
+The codebook structure is based on interleaved single-pulse permutation (ISPP) design. The 64 positions in the codevector are divided into 4 tracks of interleaved positions, with 16 positions in each track. The different codebooks at the different rates are constructed by placing a certain number of signed pulses in the tracks (from 1 to 6 pulses per track). The codebook index, or codeword, represents the pulse positions and signs in each track. Thus, no codebook storage is needed, since the excitation vector at the decoder can be constructed through the information contained in the index itself (no look-up tables).
+
+An important feature of the used codebook is that it is a dynamic codebook consisting of an algebraic codebook followed by an adaptive prefilter $F(z)$ which enhances special spectral components in order to improve the synthesis speech quality. A prefilter relevant to wideband signals is used whereby $F(z)$ consists of two parts: a periodicity enhancement part $1/(1 - 0.85z^{-T})$ and a tilt part $(1 - \beta_1 z^{-1})$ , where $T$ is the integer part of the pitch lag and $\beta_1$ is related to the voicing of the previous subframe and is bounded by $[0.0, 0.5]$ . The codebook search is performed in the algebraic domain by combining the filter $F(z)$ with the weighed synthesis filter prior to the codebook search. Thus, the impulse response $h(n)$ must be modified to include the prefilter $F(z)$ . That is, $h(n) \leftarrow h(n) * f(n)$ .
+
+The codebook structures of different bit rates are given below.
+
+#### 5.8.1.1 23.85- and 23.05-kbit/s mode
+
+In this codebook, the innovation vector contains 24 non-zero pulses. All pulses can have the amplitudes $+1$ or $-1$ . The 64 positions in a subframe are divided into 4 tracks, where each track contains six pulses, as shown in Table 4.
+
+**Table 4/G.722.2 – Potential positions of individual pulses in the algebraic codebook, 23.85 and 23.05 kbit/s**
+
+| Track | Pulse | Positions |
+|-------|--------------------------------------------|--------------------------------------------------------------|
+| 1 | $i_0, i_4, i_8, i_{12}, i_{16}, i_{20}$ | 0, 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60 |
+| 2 | $i_1, i_5, i_9, i_{13}, i_{17}, i_{21}$ | 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, 61 |
+| 3 | $i_2, i_6, i_{10}, i_{14}, i_{18}, i_{22}$ | 2, 6, 10, 14, 18, 22, 26, 30, 34, 38, 42, 46, 50, 54, 58, 62 |
+| 4 | $i_3, i_7, i_{11}, i_{15}, i_{19}, i_{23}$ | 3, 7, 11, 15, 19, 23, 27, 31, 35, 39, 43, 47, 51, 55, 59, 63 |
+
+The six pulses in one track are encoded with 22 bits.
+
+This gives a total of 88 bits ( $22+22+22+22$ ) for the algebraic code.
+
+#### 5.8.1.2 19.85-kbit/s mode
+
+In this codebook, the innovation vector contains 18 non-zero pulses. All pulses can have the amplitudes $+1$ or $-1$ . The 64 positions in a subframe are divided into 4 tracks, where each of the first two tracks contains five pulses and each of the other tracks contains four pulses, as shown in Table 5.
+
+**Table 5/G.722.2 – Potential positions of individual pulses in the algebraic codebook,
+19.85 kbit/s**
+
+| Track | Pulse | Positions |
+|-------|---------------------------------|--------------------------------------------------------------|
+| 1 | $i_0, i_4, i_8, i_{12}, i_{16}$ | 0, 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60 |
+| 2 | $i_1, i_5, i_9, i_{13}, i_{17}$ | 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, 61 |
+| 3 | $i_2, i_6, i_{10}, i_{14}$ | 2, 6, 10, 14, 18, 22, 26, 30, 34, 38, 42, 46, 50, 54, 58, 62 |
+| 4 | $i_3, i_7, i_{11}, i_{15}$ | 3, 7, 11, 15, 19, 23, 27, 31, 35, 39, 43, 47, 51, 55, 59, 63 |
+
+The five pulses in one track are encoded with 20 bits. The four pulses in one track are encoded with 16 bits.
+
+This gives a total of 72 bits (20+20+16+16) for the algebraic code.
+
+#### 5.8.1.3 18.25-kbit/s mode
+
+In this codebook, the innovation vector contains 16 non-zero pulses. All pulses can have the amplitudes +1 or -1. The 64 positions in a subframe are divided into 4 tracks, where each track contains four pulses, as shown in Table 6.
+
+**Table 6/G.722.2 – Potential positions of individual pulses in the algebraic codebook,
+18.25 kbit/s**
+
+| Track | Pulse | Positions |
+|-------|----------------------------|--------------------------------------------------------------|
+| 1 | $i_0, i_4, i_8, i_{12}$ | 0, 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60 |
+| 2 | $i_1, i_5, i_9, i_{13}$ | 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, 61 |
+| 3 | $i_2, i_6, i_{10}, i_{14}$ | 2, 6, 10, 14, 18, 22, 26, 30, 34, 38, 42, 46, 50, 54, 58, 62 |
+| 4 | $i_3, i_7, i_{11}, i_{15}$ | 3, 7, 11, 15, 19, 23, 27, 31, 35, 39, 43, 47, 51, 55, 59, 63 |
+
+The four pulses in one track are encoded with 16 bits.
+
+This gives a total of 64 bits (16+16+16+16) for the algebraic code.
+
+#### 5.8.1.4 15.85-kbit/s mode
+
+In this codebook, the innovation vector contains 12 non-zero pulses. All pulses can have the amplitudes +1 or -1. The 64 positions in a subframe are divided into 4 tracks, where each track contains three pulses, as shown in Table 7.
+
+**Table 7/G.722.2 – Potential positions of individual pulses in the algebraic codebook,
+15.85 kbit/s**
+
+| Track | Pulse | Positions |
+|-------|--------------------|--------------------------------------------------------------|
+| 1 | $i_0, i_4, i_8$ | 0, 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60 |
+| 2 | $i_1, i_5, i_9$ | 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, 61 |
+| 3 | $i_2, i_6, i_{10}$ | 2, 6, 10, 14, 18, 22, 26, 30, 34, 38, 42, 46, 50, 54, 58, 62 |
+| 4 | $i_3, i_7, i_{11}$ | 3, 7, 11, 15, 19, 23, 27, 31, 35, 39, 43, 47, 51, 55, 59, 63 |
+
+The three pulses in one track are encoded with 13 bits.
+
+This gives a total of 52 bits (13+13+13+13) for the algebraic code.
+
+#### 5.8.1.5 14.25-kbit/s mode
+
+In this codebook, the innovation vector contains 10 non-zero pulses. All pulses can have the amplitudes +1 or -1. The 64 positions in a subframe are divided into 4 tracks, where each track contains two or three pulses, as shown in Table 8.
+
+**Table 8/G.722.2 – Potential positions of individual pulses in the algebraic codebook, 14.25 kbit/s**
+
+| Track | Pulse | Positions |
+|-------|-----------------|--------------------------------------------------------------|
+| 1 | $i_0, i_4, i_8$ | 0, 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60 |
+| 2 | $i_1, i_5, i_9$ | 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, 61 |
+| 3 | $i_2, i_6$ | 2, 6, 10, 14, 18, 22, 26, 30, 34, 38, 42, 46, 50, 54, 58, 62 |
+| 4 | $i_3, i_7$ | 3, 7, 11, 15, 19, 23, 27, 31, 35, 39, 43, 47, 51, 55, 59, 63 |
+
+Each two pulse positions in one track are encoded with 8 bits (4 bits for the position of every pulse), and the sign of the first pulse in the track is encoded with 1 bit.
+
+The three pulses in one track are encoded with 13 bits.
+
+This gives a total of 44 bits (13+13+9+9) for the algebraic code.
+
+#### 5.8.1.6 12.65-kbit/s mode
+
+In this codebook, the innovation vector contains 8 non-zero pulses. All pulses can have the amplitudes +1 or -1. The 64 positions in a subframe are divided into 4 tracks, where each track contains two pulses, as shown in Table 9.
+
+**Table 9/G.722.2 – Potential positions of individual pulses in the algebraic codebook, 12.65 kbit/s**
+
+| Track | Pulse | Positions |
+|-------|------------|--------------------------------------------------------------|
+| 1 | $i_0, i_4$ | 0, 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60 |
+| 2 | $i_1, i_5$ | 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, 61 |
+| 3 | $i_2, i_6$ | 2, 6, 10, 14, 18, 22, 26, 30, 34, 38, 42, 46, 50, 54, 58, 62 |
+| 4 | $i_3, i_7$ | 3, 7, 11, 15, 19, 23, 27, 31, 35, 39, 43, 47, 51, 55, 59, 63 |
+
+Each two pulse positions in one track are encoded with 8 bits (total of 32 bits, 4 bits for the position of every pulse), and the sign of the first pulse in the track is encoded with 1 bit (total of 4 bits). This gives a total of 36 bits for the algebraic code.
+
+#### 5.8.1.7 8.85-kbit/s mode
+
+In this codebook, the innovation vector contains 4 non-zero pulses. All pulses can have the amplitudes +1 or -1. The 64 positions in a subframe are divided into 4 tracks, where each track contains one pulse, as shown in Table 10.
+
+**Table 10/G.722.2 – Potential positions of individual pulses in the algebraic codebook, 8.85 kbit/s**
+
+| Track | Pulse | Positions |
+|-------|-------|--------------------------------------------------------------|
+| 1 | $i_0$ | 0, 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60 |
+| 2 | $i_1$ | 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, 61 |
+| 3 | $i_2$ | 2, 6, 10, 14, 18, 22, 26, 30, 34, 38, 42, 46, 50, 54, 58, 62 |
+| 4 | $i_3$ | 3, 7, 11, 15, 19, 23, 27, 31, 35, 39, 43, 47, 51, 55, 59, 63 |
+
+Each pulse position in one track is encoded with 4 bits and the sign of the pulse in the track is encoded with 1 bit. This gives a total of 20 bits for the algebraic code.
+
+#### 5.8.1.8 6.60-kbit/s mode
+
+In this codebook, the innovation vector contains 2 non-zero pulses. All pulses can have the amplitudes +1 or -1. The 64 positions in a subframe are divided into 2 tracks, where each track contains one pulse, as shown in Table 11.
+
+**Table 11/G.722.2 – Potential positions of individual pulses in the algebraic codebook, 6.60 kbit/s**
+
+| Track | Pulse | Positions |
+|-------|-------|---------------------------------------------------------------------------------------------------------------------------|
+| 1 | $i_0$ | 0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62 |
+| 2 | $i_1$ | 1, 3, 5, 7, 9, 11, 13, 15, 17, 19, 21, 23, 25, 27, 29, 31, 33, 35, 37, 39, 41, 43, 45, 47, 49, 51, 53, 55, 57, 59, 61, 63 |
+
+Each pulse position in one track is encoded with 5 bits and the sign of the pulse in the track is encoded with 1 bit. This gives a total of 12 bits for the algebraic code.
+
+### 5.8.2 Pulse indexing
+
+In 5.8.1, the number of bits needed to encode a number of pulses in a track was given. In this clause, the procedures used for encoding from 1 to 6 pulses per track will be described. The description will be given for the case of 4 tracks per subframe, with 16 positions per track and pulse spacing of 4 (which is the case for all modes except the 6.6 kbit/s mode).
+
+#### *Encoding 1 signed pulse per track*
+
+The pulse position index is encoded with 4 bits and the sign index with 1 bit. The position index is given by the pulse position in the subframe divided by the pulse spacing (integer division). The division remainder gives the track index. For example, a pulse at position 31 has a position index of $31/4 = 7$ and it belongs to the track with index 3 (4th track).
+
+The sign index here is set to 0 for positive signs and 1 for negative signs.
+
+The index of the signed pulse is given by:
+
+$$I_{lp} = p + s \times 2^M$$
+
+where $p$ is the position index, $s$ is the sign index, and $M = 4$ is the number of bits per track.
+
+#### *Encoding 2 signed pulses per track*
+
+In case of two pulses per track of $K = 2^M$ potential positions (here $M = 4$ ), each pulse needs 1 bit for the sign and $M$ bits for the position, which gives a total of $2M + 2$ bits. However, some redundancy exists due to the unimportance of the pulse ordering. For example, placing the first pulse at position $p$ and the second pulse at position $q$ is equivalent to placing the first pulse at position $q$ and the second pulse at position $p$ . One bit can be saved by encoding only one sign and deducing the second sign from the ordering of the positions in the index. Here the index is given by:
+
+$$I_{2p} = p_1 + p_0 \times 2^M + s \times 2^{2M}$$
+
+where $s$ is the sign index of the pulse at position index $p_0$ . If the two signs are equal then the smaller position is set to $p_0$ and the larger position is set to $p_1$ . On the other hand, if the two signs are not equal, then the larger position is set to $p_0$ and the smaller position is set to $p_1$ . At the decoder, the sign of the pulse at position $p_0$ is readily available. The second sign is deduced from the pulse ordering. If $p_0$ is larger than $p_1$ then the sign of the pulse at position $p_1$ is opposite to that at position $p_0$ . If this is not the case, then the two signs are set equal.
+
+#### *Encoding 3 signed pulses per track*
+
+In case of three pulses per track, similar logic can be used as in the case of two pulses. For a track with $2^M$ positions, $3M + 1$ bits are needed instead of $3M + 3$ bits. A simple way of indexing the pulses is to divide the track positions in two sections (or halves) and identify a section that contains at least two pulses. The number of positions in the section is $K/2 = 2^M/2 = 2^{M-1}$ , which can be represented with $M-1$ bits. The two pulses in the section containing at least two pulses are encoded with the procedure for encoding 2 signed pulses which requires $2(M-1) + 1$ bits and the remaining pulse which can be anywhere in the track (in either section) is encoded with the $M + 1$ bits. Finally, the index of the section that contains the two pulses is encoded with 1 bit. Thus the total number of required bits is $2(M-1) + 1 + M + 1 + 1 = 3M + 1$ .
+
+A simple way of checking if two pulses are positioned in the same section is done by checking whether the most significant bits (MSB) of their position indices are equal or not. Note that a MSB of 0 means that the position belongs to the lower half of the track (0-7) and MSB of 1 means it belongs to the upper half (8-15). If the two pulses belong to the upper half, they need to be shifted to the range (0-7) before encoding them using $2 \times 3 + 1$ bits. This can be done by masking the $M-1$ least significant bits (LSB) with a mask consisting of $M-1$ ones (which corresponds to the number 7 in this case).
+
+The index of the 3 signed pulses is given by:
+
+$$I_{3p} = I_{2p} + k \times 2^{2M-1} + I_{1p} \times 2^{2M}$$
+
+where $I_{2p}$ is the index of the two pulses in the same section, $k$ is the section index (0 or 1), and $I_{1p}$ is the index of the third pulse in the track.
+
+#### *Encoding 4 signed pulses per track*
+
+The 4 signed pulses in a track of length $K = 2^M$ can be encoded using $4M$ bits. Similar to the case of 3 pulses, the $K$ positions in the track are divided into 2 sections (two halves) where each section contains $K/2 = 8$ positions. Here we denote the sections as Section A with positions 0 to $K/2-1$ and Section B with positions $K/2$ to $K-1$ . Each section can contain from 0 to 4 pulses. The table below shows the 5 cases representing the possible number of pulses in each section:
+
+| Case | Pulses in Section A | Pulses in Section B | Bits needed |
+|------|---------------------|---------------------|-------------|
+| 0 | 0 | 4 | $4M-3$ |
+| 1 | 1 | 3 | $4M-2$ |
+| 2 | 2 | 2 | $4M-2$ |
+| 3 | 3 | 1 | $4M-2$ |
+| 4 | 4 | 0 | $4M-3$ |
+
+In cases 0 or 4, the 4 pulses in a section of length $K/2 = 2^{M-1}$ can be encoded using $4(M-1)+1 = 4M-3$ bits (this will be explained later on).
+
+In cases 1 or 3, the 1 pulse in a section of length $K/2 = 2^{M-1}$ can be encoded with $M-1+1 = M$ bits and the 3 pulses in the other section can be encoded with $3(M-1)+1 = 3M-2$ bits. This gives a total of $M+3M-2 = 4M-2$ bits.
+
+In case 2, the pulses in a section of length $K/2 = 2^{M-1}$ can be encoded with $2(M-1)+1 = 2M-1$ bits. Thus for both sections, $2(2M-1) = 4M-2$ bits are required.
+
+Now the case index can be encoded with 2 bits (4 possible cases) assuming cases 0 and 4 are combined. Then for cases 1, 2, or 3, the number of needed bits is $4M-2$ . This gives a total of $4M-2+2 = 4M$ bits. For cases 0 or 4, one bit is needed for identifying either case, and $4M-3$ bits are needed for encoding the 4 pulses in the section. Adding the 2 bits needed for the general case, this gives a total of $1+4M-3+2=4M$ bits.
+
+The index of the 4 signed pulses is given by:
+
+$$I_{4p} = I_{AB} + k \times 2^{4M-2}$$
+
+where $k$ is the case index (2 bits), and $I_{AB}$ is the index of the pulses in both sections for each individual case.
+
+For cases 0 and 4, $I_{AB}$ is given by:
+
+$$I_{AB\_0,4} = I_{4p\_section} + j \times 2^{4M-3}$$
+
+where $j$ is a 1-bit index identifying the section with 4 pulses and $I_{4p\_section}$ is the index of the 4 pulses in that section (which requires $4M-3$ bits).
+
+For case 1, $I_{AB}$ is given by:
+
+$$I_{AB\_1} = I_{3p\_B} + I_{1p\_A} \times 2^{3(M-1)+1}$$
+
+where $I_{3p\_B}$ is the index of the 3 pulses in Section B ( $3(M-1)+1$ bits) and $I_{1p\_A}$ is the index of the pulse in Section A ( $(M-1)+1$ bits).
+
+For case 2, $I_{AB}$ is given by:
+
+$$I_{AB\_2} = I_{2p\_B} + I_{2p\_A} \times 2^{2(M-1)+1}$$
+
+where $I_{2p\_B}$ is the index of the 2 pulses in Section B ( $2(M-1)+1$ bits) and $I_{2p\_A}$ is the index of the two pulses in Section A ( $2(M-1)+1$ bits).
+
+Finally, for case 3, $I_{AB}$ is given by:
+
+$$I_{AB\_3} = I_{1p\_B} + I_{3p\_A} \times 2^M$$
+
+where $I_{1p\_B}$ is the index of the pulse in Section B ( $(M-1)+1$ bits) and $I_{3p\_A}$ is the index of the 3 pulses in Section A ( $3(M-1)+1$ bits).
+
+For cases 0 and 4, it was mentioned that the 4 pulses in one section are encoded using $4(M-1)+1$ bits. This is done by further dividing the section into 2 subsections of length $K/4 = 2^{M-2}$ (= 4 in this case); identifying a subsection that contains at least 2 pulses; coding the 2 pulses in that subsection using $2(M-2)+1 = 2M-3$ bits; coding the index of the subsection that contains at least 2 pulses using 1 bit; and coding the remaining 2 pulses, assuming that they can be anywhere in the section, using $2(M-1)+1 = 2M-1$ bits. This gives a total of $(2M-3)+(1)+(2M-1) = 4M-3$ bits.
+
+#### *Encoding 5 signed pulses per track*
+
+The 5 signed pulses in a track of length $K = 2^M$ can be encoded using $5M$ bits. Similar to the case of 4 pulses, the $K$ positions in the track are divided into 2 sections A and B. Each section can contain from 0 to 5 pulses. A simple approach to encode the 5 pulses is to identify a section that contains at least 3 pulses and to encode the 3 pulses in that section using $3(M-1)+1 = 3M-2$ bits, and to encode the remaining 2 pulses in the whole track using $2M+1$ bits. This gives $5M-1$ bits. An extra bit is needed to identify the section that contains at least 3 pulses. Thus a total of $5M$ bits are needed to encode the 5 signed pulses.
+
+The index of the 5 signed pulses is given by:
+
+$$I_{5p} = I_{2p} + I_{3p} \times 2^{2M} + k \times 2^{5M-1}$$
+
+where $k$ is the index of the section that contains at least 3 pulses, $I_{3p}$ is the index of the 3 pulses in that section ( $3(M-1)+1$ bits), and $I_{2p}$ is the index of the remaining 2 pulses in the track ( $2M+1$ bits).
+
+#### *Encoding 6 signed pulses per track*
+
+The 6 signed pulses in a track of length $K = 2^M$ are encoded using $6M-2$ bits. Similar to the case of 5 pulses, the $K$ positions in the track are divided into 2 sections A and B. Each section can contain from 0 to 6 pulses. The table below shows the 7 cases representing the possible number of pulses in each section:
+
+| Case | Pulses in Section A | Pulses in Section B | Bits needed |
+|------|---------------------|---------------------|-------------|
+| 0 | 0 | 6 | $6M-5$ |
+| 1 | 1 | 5 | $6M-5$ |
+| 2 | 2 | 4 | $6M-5$ |
+| 3 | 3 | 3 | $6M-4$ |
+| 4 | 4 | 2 | $6M-5$ |
+| 5 | 5 | 1 | $6M-5$ |
+| 6 | 6 | 0 | $6M-5$ |
+
+Note that cases 0 and 6 are similar except that the 6 pulses are in different section. Similarly, cases 1 and 5 as well as cases 2 and 4 differ only in the section that contains more pulses. Therefore these cases can be coupled and an extra bit can be assigned to identify the section that contains more pulses. Since these cases initially need $6M-5$ bits, the coupled cases need $6M-4$ bits taking into account the section bit. Thus, we have now 4 states of coupled cases, that is (0,6), (1,5), (2,4), and (3), with 2 extra bits needed for the state. This gives a total of $6M-4+2 = 6M-2$ bits for the 6 signed pulses.
+
+In cases 0 and 6, 1 bit is needed to identify the section which contains 6 pulses. Five pulses in that section are encoded using $5(M-1)$ bits (since the pulses are confined to that section), and the remaining pulse is encoded using $(M-1)+1$ bits. Thus a total of $1+5(M-1)+M = 6M-4$ bits are needed for this coupled case. Extra 2 bits are needed to encode the state of the coupled case, giving a total of $6M-2$ bits. For this coupled case, the index of the 6 pulses is given by:
+
+$$I_{6p} = I_{1p} + I_{5p} \times 2^M + j \times 2^{6M-5} + k \times 2^{6M-4}$$
+
+where $k$ is the index of the coupled case (2 bits), $j$ is the index of the section containing 6 pulses (1 bit), $I_{5p}$ is the index of 5 pulses in that section ( $5(M-1)$ bits), and $I_{1p}$ is the index of the remaining pulse in that section ( $(M-1)+1$ bits).
+
+In cases 1 and 5, 1 bit is needed to identify the section which contains 5 pulses. The 5 pulses in that section are encoded using $5(M-1)$ bits and the pulse in the other section is encoded using $(M-1)+1$ bits. For this coupled case, the index of the 6 pulses is given by:
+
+$$I_{6p} = I_{1p} + I_{5p} \times 2^M + j \times 2^{6M-5} + k \times 2^{6M-4}$$
+
+where $k$ is the index of the coupled case (2 bits), $j$ is the index of the section containing 5 pulses (1 bit), $I_{5p}$ is the index of the 5 pulses in that section ( $5(M-1)$ bits), and $I_{1p}$ is the index of the pulse in the other section ( $(M-1)+1$ bits).
+
+In cases 2 or 4, 1 bit is needed to identify the section which contains 4 pulses. The 4 pulses in that section are encoded using $4(M-1)$ bits and the 2 pulses in the other section are encoded using $2(M-1)+1$ bits. For this coupled case, the index of the 6 pulses is given by:
+
+$$I_{6p} = I_{2p} + I_{4p} \times 2^{2(M-1)+1} + j \times 2^{6M-5} + k \times 2^{6M-4}$$
+
+where $k$ is the index of the coupled case (2 bits), $j$ is the index of the section containing 4 pulses (1 bit), $I_{4p}$ is the index of 4 pulses in that section ( $4(M-1)$ bits), and $I_{2p}$ is the index of the 2 pulses in the other section ( $2(M-1)+1$ bits).
+
+In case 3, the 3 pulses in each section are encoded using $3(M-1)+1$ bits in each section. For this case, the index of the 6 pulses is given by:
+
+$$I_{6p} = I_{3pB} + I_{3pA} \times 2^{3(M-1)+1} + k \times 2^{6M-4}$$
+
+where $k$ is the index of the coupled case (2 bits), $I_{3pB}$ is the index of 3 pulses in Section B ( $3(M-1)+1$ bits), and $I_{3pA}$ is the index of the 3 pulses in Section A ( $3(M-1)+1$ bits).
+
+### 5.8.3 Codebook search
+
+The algebraic codebook is searched by minimizing the mean square error between the weighted input speech and the weighted synthesis speech. The target signal used in the closed-loop pitch search is updated by subtracting the adaptive codebook contribution. That is:
+
+$$x_2(n) = x(n) - g_p y(n), \quad n = 0, \dots, 63 \quad (40)$$
+
+where $y(n) = v(n) * h(n)$ is the filtered adaptive codebook vector and $g_p$ is the unquantized adaptive codebook gain.
+
+The matrix **H** is defined as the lower triangular Toeplitz convolution matrix with diagonal $h(0)$ and lower diagonals $h(1), \dots, h(63)$ , and $\mathbf{d} = \mathbf{H}^t \mathbf{x}_2$ is the correlation between the target signal $x_2(n)$ and the impulse response $h(n)$ (also known as the backward filtered target vector), and $\Phi = \mathbf{H}^t \mathbf{H}$ is the matrix of correlations of $h(n)$ .
+
+The elements of the vector **d** are computed by:
+
+$$d(n) = \sum_{i=n}^{63} x_2(i)h(i-n), \quad n = 0, \dots, 63 \quad (41)$$
+
+and the elements of the symmetric matrix $\Phi$ are computed by:
+
+$$\phi(i, j) = \sum_{n=j}^{63} h(n-i)h(n-j), \quad i = 0, \dots, 63 \quad j = i, \dots, 63 \quad (42)$$
+
+If $\mathbf{c}_k$ is the algebraic codevector at index $k$ , then the algebraic codebook is searched by maximizing the search criterion:
+
+$$Q_k = \frac{(\mathbf{x}_2^t \mathbf{H} \mathbf{c}_k)^2}{\mathbf{c}_k^t \mathbf{H}^t \mathbf{H} \mathbf{c}_k} = \frac{(\mathbf{d}^t \mathbf{c}_k)^2}{\mathbf{c}_k^t \Phi \mathbf{c}_k} = \frac{(R_k)^2}{E_k} \quad (43)$$
+
+The vector $\mathbf{d}$ and the matrix $\Phi$ are usually computed prior to the codebook search.
+
+The algebraic structure of the codebooks allows for very fast search procedures since the innovation vector $\mathbf{c}_k$ contains only a few non-zero pulses. The correlation in the numerator of Equation (43) is given by:
+
+$$C = \sum_{i=0}^{N_p-1} a_i d(m_i) \quad (44)$$
+
+where $m_i$ is the position of the $i$ th pulse, $a_i$ is its amplitude, and $N_p$ is the number of pulses. The energy in the denominator of Equation (43) is given by:
+
+$$E = \sum_{i=0}^{N_p-1} \phi(m_i, m_i) + 2 \sum_{i=0}^{N_p-2} \sum_{j=i+1}^{N_p-1} a_i a_j \phi(m_i, m_j) \quad (45)$$
+
+To simplify the search procedure, the pulse amplitudes are predetermined based on a certain reference signal $b(n)$ . In this so-called signal-selected pulse amplitude approach, the sign of a pulse at position $i$ is set equal to the sign of the reference signal at that position. Here, the reference signal $b(n)$ is given by:
+
+$$b(n) = \sqrt{\frac{E_d}{E_r}} r_{LTP}(n) + \alpha d(n) \quad (46)$$
+
+where $E_d = \mathbf{d}^t \mathbf{d}$ is the energy of the signal $d(n)$ and $E_r = \mathbf{r}_{LTP}^t \mathbf{r}_{LTP}$ is the energy of the signal $r_{LTP}(n)$ which is the residual signal after long-term prediction. The scaling factor $\alpha$ controls the amount of dependence of the reference signal on $d(n)$ , and it is lowered as the bit rate is increased. Here $\alpha = 2$ for 6.6 and 8.85 modes; $\alpha = 1$ for 12.65, 14.25, and 15.85 modes; $\alpha = 0.8$ for 18.25 mode; $\alpha = 0.75$ for 19.85 mode; and $\alpha = 0.5$ for 23.05 and 23.85 modes.
+
+To simplify the search, the signal $d(n)$ and matrix $\Phi$ are modified to incorporate the pre-selected signs. Let $s_b(n)$ denote the vector containing the signs of $b(n)$ . The modified signal $d'(n)$ is given by:
+
+$$d'(n) = s_b(n) d(n) \quad n = 0, \dots, N-1$$
+
+and the modified autocorrelation matrix $\Phi'$ is given by:
+
+$$\phi'(i, j) = s_b(i) s_b(j) \phi(i, j), \quad i = 0, \dots, N-1; \quad j = i, \dots, N-1$$
+
+The correlation at the numerator of the search criterion $Q_k$ is now given by:
+
+$$R = \sum_{i=0}^{N_p-1} d'(i)$$
+
+and the energy at the denominator of the search criterion $Q_k$ is given by:
+
+$$E = \sum_{i=0}^{N_p-1} \phi'(m_i, m_i) + 2 \sum_{i=0}^{N_p-2} \sum_{j=i+1}^{N_p-1} \phi'(m_i, m_j)$$
+
+The goal of the search now is to determine the codevector with the best set of $N_p$ pulse positions assuming amplitudes of the pulses have been selected as described above. The basic selection criterion is the maximization of the above-mentioned ratio $Q_k$ .
+
+In order to reduce the search complexity, a fast search procedure known as depth-first tree search procedure is used, whereby the pulse positions are determined $N_m$ pulses at a time. More precisely, the $N_p$ available pulses are partitioned into $M$ non-empty subsets of $N_m$ pulses respectively such that $N_1 + N_2 + \dots + N_M = N_p$ . A particular choice of positions for the first $J = N_1 + N_2 + \dots + N_{m-1}$ pulses considered is called a level- $m$ path or a path of length $J$ . The basic criterion for a path of $J$ pulse positions is the ratio $Q_k(J)$ when only the $J$ relevant pulses are considered.
+
+The search begins with subset #1 and proceeds with subsequent subsets according to a tree structure whereby subset $m$ is searched at the $m$ th level of the tree. The purpose of the search at level 1 is to consider the $N_1$ pulses of subset #1 and their valid positions in order to determine one, or a number of, candidate path(s) of length $N_1$ which are the tree nodes at level 1. The path at each terminating node of level $m-1$ is extended to length $N_1 + N_2 + \dots + N_m$ at level $m$ by considering $N_m$ new pulses and their valid positions. One, or a number of, candidate extended path(s) are determined to constitute level- $m$ nodes. The best codevector corresponds to that path of length $N_p$ which maximizes the criterion $Q_k(N_p)$ with respect to all level- $M$ nodes.
+
+A special form of the depth-first tree search procedure is used here, in which two pulses are searched at a time, that is, $N_m = 2$ , and these 2 pulses belong to two consecutive tracks. Further, instead of assuming that the matrix $\Phi$ is precomputed and stored, which requires a memory of $N \times N$ words ( $64 \times 64 = 4k$ words), a memory-efficient approach is used which reduces the memory requirement. In this approach, the search procedure is performed in such a way that only a part of the needed elements of the correlation matrix are precomputed and stored. This part corresponds to the correlations of the impulse response corresponding to potential pulse positions in consecutive tracks, as well as the correlations corresponding to $\phi(j, j)$ , $j = 0, \dots, N-1$ (that is the elements of the main diagonal of matrix $\Phi$ ).
+
+In order to reduce complexity, while testing possible combinations of two pulses, a limited number of potential positions of the first pulse are tested. Further, in case of a large number of pulses, some pulses in the higher levels of the search tree are fixed. In order to guess intelligently which potential pulse positions are considered for the first pulse, or in order to fix some pulse positions, a "pulse-position likelihood-estimate vector" $\mathbf{b}$ is used, which is based on speech-related signals. The $p$ th component $b(p)$ of this estimate vector $\mathbf{b}$ characterizes the probability of a pulse occupying position $p$ ( $p = 0, 1, \dots, N-1$ ) in the best codevector we are searching for. Here the estimate vector $\mathbf{b}$ is the same vector used for preselecting the amplitudes and given in Equation (46).
+
+The search procedures for all bit rate modes are similar. Two pulses are searched at a time, and these two pulses always correspond to consecutive tracks. That is, the two searched pulses are in tracks $T_0-T_1$ , $T_1-T_2$ , $T_2-T_3$ , or $T_3-T_0$ .
+
+Before searching the positions, the sign of a pulse at a potential position $n$ sets the sign of $b(n)$ at that position. Then, the modified signal $d'(n)$ is computed as described above by including the predetermined signs.
+
+For the first 2 pulses (1st tree level), the correlation at the numerator of the search criterion is given by:
+
+$$R = d'(m_0) + d'(m_1)$$
+
+and the energy at the denominator of the search criterion $Q_k$ is given by:
+
+$$E = \phi'(m_0, m_0) + \phi'(m_1, m_1) + 2\phi'(m_0, m_1)$$
+
+where the correlations $\phi'(m_i, m_j)$ has been modified to include the preselected signs at positions $m_i$ and $m_j$ .
+
+For subsequent levels, the numerator and denominator are updated by adding the contribution of two new pulses. Assuming that two new pulses at a certain tree level with positions $m_k$ and $m_{k+1}$ from two consecutive tracks are searched, then the updated value of $R$ is given by:
+
+$$R = R + d'(m_k) + d'(m_{k+1}) \quad (47)$$
+
+and the updated energy is given by:
+
+$$E = E + \phi'(m_k, m_k) + \phi'(m_{k+1}, m_{k+1}) + 2\phi'(m_k, m_{k+1}) + 2R_{hv}(m_k) + 2R_{hv}(m_{k+1}) \quad (48)$$
+
+where $R_{hv}(m)$ is the correlation between the impulse response $h(n)$ and a vector $v_h(n)$ containing the addition of delayed versions of impulse response at the previously determined positions. That is:
+
+$$v_h(n) = \sum_{i=0}^{k-1} h(n - m_i)$$
+
+and:
+
+$$R_{hv}(m) = \sum_{n=m}^{N-1} h(n)v_h(n - m)$$
+
+At each tree level, the values of $R_{hv}(m)$ are computed online for all possible positions in each of the two tracks being tested. It can be seen from Equation (48) that only the correlations $\phi'(m_k, m_{k+1})$ corresponding to pulse positions in two consecutive tracks need to be stored ( $4 \times 16 \times 16$ words), along with the correlations $\phi'(m_k, m_k)$ corresponding to the diagonal of the matrix $\Phi$ (64 words). Thus the memory requirement in the present algebraic structure is 1088 words instead of $64 \times 64 = 4096$ words.
+
+The search procedures at the different bit rates modes are similar. The difference is in the number of pulses, and accordingly, the number of levels in the tree search. In order to keep a comparable search complexity across the different codebooks, the number of tested positions is kept similar.
+
+The search in the 12.65-kbit/s mode will be described as an example. In this mode, 2 pulses are placed in each track giving a total of 8 pulses per subframe of length 64. Two pulses are searched at a time, and these two pulses always correspond to consecutive tracks. That is, the two searched pulses are in tracks $T_0-T_1$ , $T_1-T_2$ , $T_2-T_3$ , or $T_3-T_0$ . The tree has 4 levels in this case. At the first level, pulse $P_0$ is assigned to track $T_0$ and pulse $P_1$ to track $T_1$ . In this level, no search is performed and the two pulse positions are set to the maximum of $b(n)$ in each track. In the second level, pulse $P_2$ is assigned to track $T_2$ and pulse $P_3$ to track $T_3$ . Four positions for pulse $P_2$ are tested against all 16 positions of pulse $P_3$ . The 4 tested positions of $P_2$ are determined based on the maxima of $b(n)$ in the track. In the third level, pulse $P_4$ is assigned to track $T_1$ and pulse $P_5$ to track $T_2$ . Eight positions for pulse $P_4$ are tested against all 16 positions of pulse $P_5$ . Similar to the previous search level, the 8 tested positions of $P_4$ are determined based on the maxima of $b(n)$ in the track. In the fourth level, pulse $P_6$ is assigned to track $T_3$ and pulse $P_7$ to track $T_0$ . Eight positions for pulse $P_6$ are tested against all 16 positions of pulse $P_7$ . Thus the total number of tested combination is $4 \times 16 + 8 \times 16 + 8 \times 16 = 320$ . The whole process is repeated 4 times (4 iterations) by assigning the pulses to different tracks. For example, in the 2nd iteration, pulses $P_0$ to $P_7$ are assigned to tracks $T_1$ , $T_2$ , $T_3$ , $T_0$ , $T_2$ , $T_3$ , $T_0$ , and $T_1$ , respectively. Thus the total number of tested position combinations is $4 \times 320 = 1280$ .
+
+As another search example, in the 15.85-kbit/s mode, 3 pulses are placed in each track giving a total of 12 pulses. There are 6 levels in the tree search whereby two pulses are searched in each level. In the first two levels, 4 pulses are set to the maxima of $b(n)$ . In the subsequent 4 levels, the number of tested combinations are $4 \times 16$ , $6 \times 16$ , $8 \times 16$ , and $8 \times 16$ , respectively. Four iterations are used giving a total of $4 \times 26 \times 16 = 1664$ combinations.
+
+## 5.9 Quantization of the adaptive and fixed codebook gains
+
+The adaptive codebook gain (pitch gain) and the fixed (algebraic) codebook gain are vector quantized using a 6-bit codebook for modes 8.85 and 6.60 kbit/s and using a 7-bit codebook for all the other modes.
+
+The fixed codebook gain quantization is performed using MA prediction with fixed coefficients. The 4th-order MA prediction is performed on the innovation energy as follows. Let $E(n)$ be the mean-removed innovation energy (in dB) at subframe $n$ , and given by:
+
+$$E(n) = 10 \log \left( \frac{1}{N} g_c^2 \sum_{i=0}^{N-1} c^2(i) \right) - \bar{E} \quad (49)$$
+
+where $N = 64$ is the subframe size, $c(i)$ is the fixed codebook excitation, and $\bar{E} = 30$ dB is the mean of the innovation energy. The predicted energy is given by:
+
+$$\tilde{E}(n) = \sum_{i=1}^4 b_i \hat{R}(n-i) \quad (50)$$
+
+where $[b_1 \ b_2 \ b_3 \ b_4] = [0.5, 0.4, 0.3, 0.2]$ are the MA prediction coefficients, and $\hat{R}(k)$ is the quantized energy prediction error at subframe $k$ . The predicted energy is used to compute a predicted fixed-codebook gain $g'_c$ as in Equation (49) (by substituting $E(n)$ by $\tilde{E}(n)$ and $g_c$ by $g'_c$ ). This is done as follows. First, the mean innovation energy is found by:
+
+$$E_i = 10 \log \left( \frac{1}{N} \sum_{i=0}^{N-1} c^2(i) \right) \quad (51)$$
+
+and then the predicted gain $g'_c$ is found by:
+
+$$g'_c = 10^{0.05(\tilde{E}(n) + \bar{E} - E_i)} \quad (52)$$
+
+A correction factor between the gain $g_c$ and the estimated one $g'_c$ is given by:
+
+$$\gamma = g_c / g'_c \quad (53)$$
+
+Note that the prediction error is given by:
+
+$$R(n) = E(n) - \tilde{E}(n) = 20 \log(\gamma) \quad (54)$$
+
+The pitch gain, $g_p$ , and correction factor $\gamma$ are jointly vector quantized using a 6-bit codebook for modes 8.85 and 6.60 kbit/s, and 7-bit codebook for other modes. The gain codebook search is performed by minimizing the mean-square of the weighted error between original and reconstructed speech which is given:
+
+$$E = x^t x + g_p^2 y^t y + g_c^2 z^t z - 2g_p x^t y - 2g_c x^t z + 2g_p g_c y^t z \quad (55)$$
+
+where $x$ is the target vector, $y$ is the filtered adaptive codebook vector, and $z$ is the filtered fixed codebook vector. (Each gain vector in the codebook also has an element representing the quantized energy prediction error.) The quantized energy prediction error associated with the chosen gains is
+
+used to update $\hat{R}(n)$ . In the search, only the 64 codevectors that are closest to the unquantized pitch gain, $g_p$ , are taken into account.
+
+## 5.10 Memory update
+
+An update of the states of the synthesis and weighting filters is needed in order to compute the target signal in the next subframe.
+
+After the two gains have been quantized, the excitation signal, $u(n)$ , in the present subframe is found by:
+
+$$u(n) = \hat{g}_p v(n) + \hat{g}_c c(n), \quad n = 0, \dots, 63 \quad (56)$$
+
+where $\hat{g}_p$ and $\hat{g}_c$ are the quantized adaptive and fixed codebook gains, respectively, $v_i(n)$ the adaptive codebook vector (interpolated past excitation), and $c(n)$ is the fixed codebook vector (algebraic code including pitch sharpening). The states of the filters can be updated by filtering the signal $r(n) - u(n)$ (difference between residual and excitation) through the filters $1/\hat{A}(z)$ and $A(z/\gamma_1)H_{\text{de-emph}}(z)$ for the 64-sample subframe and saving the states of the filters. This would require 3 filterings. A simpler approach which requires only one filtering is as follows. The local synthesis speech, $\hat{s}(n)$ , is computed by filtering the excitation signal through $1/\hat{A}(z)$ . The output of the filter due to the input $r(n) - u(n)$ is equivalent to $e(n) = s(n) - \hat{s}(n)$ . So the states of the synthesis filter $1/\hat{A}(z)$ are given by $e(n)$ , $n = 48, \dots, 63$ . Updating the states of the filter $A(z/\gamma_1)H_{\text{de-emph}}(z)$ can be done by filtering the error signal $e(n)$ through this filter to find the perceptually weighted error $e_w(n)$ . However, the signal $e_w(n)$ can be equivalently found by:
+
+$$e_w(n) = x(n) - \hat{g}_p y(n) - \hat{g}_c z(n) \quad (57)$$
+
+Since the signals $x(n)$ , $y(n)$ , and $z(n)$ are available, the states of the weighting filter are updated by computing $e_w(n)$ as in Equation (57) for $n = 48, \dots, 63$ . This saves two filterings.
+
+## 5.11 High-band gain generation
+
+In order to compute the high-band gain for 23.85-kbit/s mode, 16-kHz input speech is filtered through a band-pass FIR filter $H_{HB}(z)$ which has the passband from 6.4 to 7 kHz. The high-band gain $g_{HB}$ is obtained by:
+
+$$g_{HB} = \frac{\sum_{i=0}^{63} (s_{HB}(i))^2}{\sum_{i=0}^{63} (s_{HB2}(i))^2} \quad (58)$$
+
+where $s_{HB}(i)$ is band-pass filtered input speech and $s_{HB2}(i)$ is high-band speech synthesis obtained from high-band excitation $u_{HB2}(i)$ filtered through high-band synthesis filter $A_{HB}(z)$ described in 6.3.2.2.
+
+# 6 Functional description of the decoder
+
+The function of the decoder consists of decoding the transmitted parameters (LP parameters, adaptive codebook vector, adaptive codebook gain, fixed codebook vector, fixed codebook gain and high-band gain) and performing synthesis to obtain the reconstructed speech. The reconstructed speech is then postprocessed and upsampled (and upscaled). Finally high-band signal is generated to the frequency band from 6 to 7 kHz. The signal flow at the decoder is shown in Figure 3.
+
+## 6.1 Decoding and speech synthesis
+
+The decoding process is performed in the following order:
+
+**Decoding of LP filter parameters:** The received indices of ISP quantization are used to reconstruct the quantized ISP vector. The interpolation described in 5.2.6 is performed to obtain 4 interpolated ISP vectors (corresponding to 4 subframes). For each subframe, the interpolated ISP vector is converted to LP filter coefficient domain $a_k$ , which is used for synthesizing the reconstructed speech in the subframe.
+
+The following steps are repeated for each subframe:
+
+- 1) **Decoding of the adaptive codebook vector:** The received pitch index (adaptive codebook index) is used to find the integer and fractional parts of the pitch lag. The adaptive codebook vector $v(n)$ is found by interpolating the past excitation $u(n)$ (at the pitch delay) using the FIR filter described in 5.6. The received adaptive filter index is used to find out whether the filtered adaptive codebook is $v_1(n) = v(n)$ or $v_2(n) = 0.18v(n) + 0.64v(n - 1) + 0.18v(n - 2)$ .
+- 2) **Decoding of the innovative vector:** The received algebraic codebook index is used to extract the positions and amplitudes (signs) of the excitation pulses and to find the algebraic codevector $c(n)$ . If the integer part of the pitch lag is less than the subframe size 64, the pitch sharpening procedure is applied which translates into modifying $c(n)$ by filtering it through the adaptive prefilter $F(z)$ which consists of two parts: a periodicity enhancement part $1/(1-0.85z^{-T})$ and a tilt part $(1 - \beta_1 z^{-1})$ , where $T$ is the integer part of the pitch lag and $\beta_1(n)$ is related to the voicing of the previous subframe and is bounded by $[0.0, 0.5]$ .
+- 3) **Decoding of the adaptive and innovative codebook gains:** The received index gives the fixed codebook gain correction factor $\hat{\gamma}$ . The estimated fixed codebook gain $g'_c$ is found as described in 5.8. First, the predicted energy for every subframe $n$ is found by:
+
+$$\tilde{E}(n) = \sum_{i=1}^4 b_i \hat{R}(n-i) \quad (59)$$
+
+and then the mean innovation energy is found by:
+
+$$E_i = 10 \log \left( \frac{1}{N} \sum_{i=0}^{N-1} c^2(i) \right) \quad (60)$$
+
+The predicted gain $g'_c$ is found by:
+
+$$g'_c = 10^{0.05(\tilde{E}(n) + \bar{E} - E_i)} \quad (61)$$
+
+The quantized fixed codebook gain is given by:
+
+$$\hat{g}_c = \hat{\gamma} g'_c \quad (62)$$
+
+- 4) **Computing the reconstructed speech:** The following steps are for $n = 0, \dots, 63$ . The total excitation is constructed by:
+
+$$u(n) = \hat{g}_p v(n) + \hat{g}_c c(n) \quad (63)$$
+
+Before the speech synthesis, a post-processing of excitation elements is performed.
+
+- 5) **Anti-sparseness processing (6.60- and 8.85-kbit/s modes):** An adaptive anti-sparseness post-processing procedure is applied to the fixed codebook vector $c(n)$ in order to reduce perceptual artifacts arising from the sparseness of the algebraic fixed codebook vectors with only a few non-zero samples per subframe. The anti-sparseness processing consists of circular convolution of the fixed codebook vector with an impulse response. Three pre-stored impulse responses are used and a number $impNr = 0, 1, 2$ is set to select one of them.
+
+A value of 2 corresponds to no modification, a value of 1 corresponds to medium modification, while a value of 0 corresponds to strong modification. The selection of the impulse response is performed adaptively from the adaptive and fixed codebook gains. The following procedure is employed:
+
+```
+
+if $\hat{g}_p < 0.6$ then
+ $impNr = 0$ ;
+else if $\hat{g}_p < 0.9$ then
+ $impNr = 1$ ;
+else
+ $impNr = 2$ ;
+
+```
+
+Detect onset by comparing the fixed codebook gain to the previous fixed codebook gain. If the current value is more than three times the previous value, an onset is detected.
+
+If not onset and $impNr = 0$ , the median filtered value of the current and the previous 4 adaptive codebook gains are computed. If this value is less than 0.6, $impNr = 0$ .
+
+If not onset, the $impNr$ value is restricted to increase by one step from the previous subframe.
+
+If an onset is declared, the $impNr$ value is increased by one if it is less than 2.
+
+In case of 8.85-kbit/s mode, the $impNr$ value is increased by one.
+
+- 6) **Noise enhancer:** A non-linear gain smoothing technique is applied to the fixed codebook gain $\hat{g}_c$ in order to enhance excitation in noise. Based on the stability and voicing of the speech segment, the gain of the fixed codebook is smoothed in order to reduce fluctuation in the energy of the excitation in case of stationary signals. This improves the performance in case of stationary background noise.
+
+The voicing factor is given by $\lambda = 0.5(1-r_v)$ with $r_v = (E_v - E_c)/(E_v + E_c)$ , where $E_v$ and $E_c$ are the energies of the scaled pitch codevector and scaled innovation codevector, respectively. Note that since the value of $r_v$ is between $-1$ and $1$ , the value of $\lambda$ is between $0$ and $1$ . Note that the factor $\lambda$ is related to the amount of unvoicing with a value of $0$ for purely voiced segments and a value of $1$ for purely unvoiced segments.
+
+A stability factor $\theta$ is computed based on a distance measure between the adjacent LP filters. Here, the factor $\theta$ is related to the ISP distance measure and it is bounded by $0 \leq \theta \leq 1$ , with larger values of $\theta$ corresponding to more stable signals.
+
+Finally, a gain smoothing factor $S_m$ is given by:
+
+$$S_m = \lambda\theta \quad (64)$$
+
+The value of $S_m$ approaches $1$ for unvoiced and stable signals, which is the case of stationary background noise signals. For purely voiced signals or for unstable signals, the value of $S_m$ approaches $0$ .
+
+An initial modified gain $g_0$ is computed by comparing the fixed codebook gain $\hat{g}_c$ to a threshold given by the initial modified gain from the previous subframe, $g_{-1}$ . If $\hat{g}_c$ is larger or equal to $g_{-1}$ , then $g_0$ is computed by decrementing $\hat{g}_c$ by $1.5$ dB bounded by $g_0 \geq g_{-1}$ . If $\hat{g}_c$ is smaller than $g_{-1}$ , then $g_0$ is computed by incrementing $\hat{g}_c$ by $1.5$ dB bounded by $g_0 \leq g_{-1}$ .
+
+Finally, the gain is updated with the value of the smoothed gain as follows:
+
+$$\hat{g}_c = \theta g_0 + (1 - \theta) \hat{g}_c \quad (65)$$
+
+- 7) **Pitch enhancer:** A pitch enhancer procedure modifies the total excitation $u(n)$ by filtering the fixed codebook excitation through an innovation filter whose frequency response emphasizes the higher frequencies more than lower frequencies, and whose coefficients are related to the periodicity in the signal. A filter of the form:
+
+$$F_{inno}(z) = -c_{pe}z + 1 - c_{pe}z^{-1} \quad (66)$$
+
+where $c_{pe} = 0.125(1 - r_v)$ , with $r_v = (E_v - E_c)/(E_v + E_c)$ as described above. The filtered fixed codevector is given by:
+
+$$c'(n) = c(n) - c_{pe}(c(n+1) + c(n-1)) \quad (67)$$
+
+and the updated excitation is given by:
+
+$$u(n) = \hat{g}_p v(n) + \hat{g}_c c'(n) \quad (68)$$
+
+The above procedure can be done in one step by updating the excitation as follows:
+
+$$u(n) = u(n) - \hat{g}_c c_{pe} (c(n+1) + c(n-1)) \quad (69)$$
+
+- 8) **Post-processing of excitation elements (6.60- and 8.85-kbit/s modes):** A post-processing of excitation elements procedure is applied to the total excitation $u(n)$ by emphasizing the contribution of the adaptive codebook vector:
+
+$$\hat{u}(n) = \begin{cases} u(n) + 0.25\beta\hat{g}_p v(n) & \hat{g}_p > 0.5 \\ u(n), & \hat{g}_p \leq 0.5 \end{cases} \quad (70)$$
+
+Adaptive gain control (AGC) is used to compensate for the gain difference between the non-emphasized excitation $u(n)$ and emphasized excitation $\hat{u}(n)$ . The gain scaling factor $\eta$ for the emphasized excitation is computed by:
+
+$$\eta = \begin{cases} \sqrt{\frac{\sum_{n=0}^{63} u^2(n)}{\sum_{n=0}^{63} \hat{u}^2(n)}}, & \hat{g}_p > 0.5 \\ 1.0, & \hat{g}_p \leq 0.5 \end{cases} \quad (71)$$
+
+The gain-scaled emphasized excitation signal $\hat{u}'(n)$ is given by:
+
+$$\hat{u}'(n) = \hat{u}(n)\eta \quad (72)$$
+
+The reconstructed speech for the subframe of size 64 is given by:
+
+$$\hat{s}(n) = \hat{u}'(n) - \sum_{i=1}^{16} \hat{a}_i \hat{s}(n-i), \quad n = 0, \dots, 63 \quad (73)$$
+
+where $\hat{a}_i$ are the interpolated LP filter coefficients.
+
+The synthesis speech $\hat{s}(n)$ is then passed through an adaptive postprocessing which is described in the following clause.
+
+## 6.2 High-pass filtering, up-scaling and interpolation
+
+The high-pass filter serves as a precaution against undesired low-frequency components. The signal is filtered through the high-pass filter $H_{hp}(z)$ and de-emphasis filter $H_{de-emph}(z)$ .
+
+Finally, the signal is upsampled to 16 kHz to obtain the lower-band synthesis signal $\hat{s}_{16k}(n)$ . $\hat{s}_{16k}(n)$ is produced by first upsampling the lower-band synthesis $\hat{s}_{12.8k}(n)$ at 12.8 kHz by 5, then filtering the output through $H_{decim}(z)$ , and finally downsampling it by 4.
+
+(Up-scaling consists of multiplying the output from the high-pass filtering by a factor of 2 in order to compensate the down-scaling at the preprocessing stage.)
+
+## 6.3 High frequency band
+
+For the higher frequency band (6.4-7.0 kHz), excitation is generated to model the highest frequencies. The high frequency content is generated by filling the upper part of the spectrum with a white noise properly scaled in the excitation domain, then converted to the speech domain by shaping it with a filter derived from the same LP synthesis filter used for synthesizing the down-sampled signal.
+
+### 6.3.1 Generation of high-band excitation
+
+The high-band excitation is obtained by first generating white noise $u_{HB1}(n)$ . The power of the high-band excitation is set equal to the power of the lower band excitation $u_2(n)$ which means that:
+
+$$u_{HB2}(n) = u_{HB1}(n) \sqrt{\frac{\sum_{k=0}^{63} u_2^2(k)}{\sum_{k=0}^{63} u_{HB1}^2(k)}} \quad (74)$$
+
+Finally the high-band excitation is found by:
+
+$$u_{HB}(n) = \hat{g}_{HB} u_{HB2}(n) \quad (75)$$
+
+where $\hat{g}_{HB}$ is a gain factor.
+
+In the 23.85-kbit/s mode, $\hat{g}_{HB}$ is decoded from the received gain index.
+
+In 6.60-, 8.85-, 12.65-, 14.25-, 15.85-, 18.25-, 19.85- and 23.05-kbit/s modes, $g_{HB}$ is estimated using voicing information bounded by [0.1,1.0]. First, tilt of synthesis $e_{tilt}$ is found:
+
+$$e_{tilt} = \frac{\sum_{n=1}^{63} \hat{s}_{hp}(n) \hat{s}_{hp}(n-1)}{\sum_{n=0}^{63} \hat{s}_{hp}^2(n)} \quad (76)$$
+
+where $\hat{s}_{hp}(n)$ is high-pass filtered lower band speech synthesis $\hat{s}_{12.8k}(n)$ with cut-off frequency of 400 Hz. The $\hat{g}_{HB}$ is then found by:
+
+$$\hat{g}_{HB} = w_{SP} g_{SP} + (1 - w_{SP}) g_{BG} \quad (77)$$
+
+where $g_{SP} = 1 - e_{tilt}$ is gain for speech signal, $g_{BG} = 1.25 g_{SP}$ is gain for background noise signal, and $w_{SP}$ is a weighting function set to 1, when VAD is ON, and 0 when VAD is OFF. $g_{HB}$ is bounded between [0.1,1.0]. In case of voiced segments where less energy is present at high frequencies, $e_{tilt}$ approaches 1 resulting in a lower gain $g_{HB}$ . This reduces the energy of the generated noise in case of voiced segments.
+
+### 6.3.2 LP filter for the high frequency band
+
+#### 6.3.2.1 6.60-kbit/s mode
+
+The high-band LP synthesis filter $A_{HB}(z)$ is found by extrapolating the quantized ISF vector $\mathbf{f}$ into 20th-order ISF vector $\mathbf{f}_e$ . First, maximum of the autocorrelation $C_{\max}(i)$ of ISF vector difference vector $f_{\Delta}(i) = f(i+1) - f(i), i = 1, \dots, 14$ is obtained. Then new 16-kHz ISF vector $f'_e(i)$ is computed by:
+
+$$f'_e(i) = \begin{cases} f(i-1), & i = 1, \dots, 15 \\ f'_e(i-1) + f'_e(i - C_{\max}(i) - 1) - f'_e(i - C_{\max}(i) - 2), & i = 16, \dots, 19 \end{cases} \quad (78)$$
+
+An approximation of the last element of new ISF vector $f_{e19}$ is updated based on lower frequency coefficients. New extrapolated ISF vector difference vector $f'_{e\Delta}(i)$ is:
+
+$$f'_{e\Delta}(i) = c_{\text{scale}}(f'_e(i) - f'_e(i-1)), \quad i = 16, \dots, 19 \quad (79)$$
+
+where $c_{\text{scale}}$ scales $f'_{e\Delta}(i)$ so that $f'_e(19)$ will be equal to $f_{e19}$ . In order to insure stability, $f'_{e\Delta}(i)$ is bounded by:
+
+$$f'_{e\Delta}(i) + f'_{e\Delta}(i-1) > 500, \quad i = 17, \dots, 19 \quad (80)$$
+
+Finally, the extrapolated ISF vector $\mathbf{f}_e$ is obtained by:
+
+$$f_e(i) = \begin{cases} f(i), & i = 1, \dots, 15 \\ f'_{e\Delta}(i) + f_e(i-1), & i = 16, \dots, 19 \\ f(16), & i = 20 \end{cases} \quad (81)$$
+
+$\mathbf{f}_e$ is converted to cosine domain to obtain $\mathbf{q}_e$ with 16 000-Hz sampling rate. The high-band LP synthesis filter $A_{HB}(z)$ is obtained by converting $\mathbf{q}_e$ to LP filter as described in 5.2.4 with $m = 20$ .
+
+#### 6.3.2.2 8.85-, 12.65-, 14.25-, 15.85-, 18.25-, 19.85-, 23.05- or 23.85-kbit/s modes
+
+The high-band LP synthesis filter $A_{HB}(z)$ is weighted low-band LP synthesis filter:
+
+$$A_{HB}(z) = \hat{A}(z/0.8) \quad (82)$$
+
+where $\hat{A}(z)$ is the interpolated LP synthesis filter. $\hat{A}(z)$ has been computed analysing signal with the sampling rate of 12.8 kHz but it is now used for a 16-kHz signal. Effectively, this means that the frequency response $FR_{16}(f)$ of $A_{HB}(z)$ is obtained by:
+
+$$FR_{16}(f) = FR_{12.8}\left(\frac{12.8}{16} f\right) \quad (83)$$
+
+where $FR_{12.8}(f)$ is the frequency response of $A(z)$ . This means that the band 5.1-5.6 kHz in the 12.8-kHz domain will be mapped to 6.4-7.0 kHz in the 16-kHz domain.
+
+### 6.3.3 High-band synthesis
+
+$u_{HB}(n)$ is filtered through $A_{HB}(z)$ . The output of this high-band synthesis $s_{HB}(n)$ is filtered through a band-pass FIR filter $H_{HB}(z)$ which has the passband from 6 to 7 kHz. Finally, $s_{HB}$ is added to synthesized speech $\hat{s}_{16k}(n)$ to produce the synthesized output speech signal $\hat{s}_{\text{output}}(n)$ .
+
+# 7 Detailed bit allocation of the adaptive multi-rate wideband codec
+
+The detailed allocation of the bits in the adaptive multi-rate wideband speech encoder is shown for each mode in Tables 12a-12i. These tables show the order of the bits produced by the speech encoder. Note that the most significant bit (MSB) of each codec parameter is always sent first.
+
+**Table 12a/G.722.2 – Source encoder output parameters in order of occurrence and bit allocation within the speech frame of 477 bits/20 ms, 23.85-kbit/s mode**
+
+| Bits (MSB-LSB) | Description |
+|----------------|------------------------------------|
+| s1 | VAD-flag |
+| s2-s9 | index of 1st ISP subvector |
+| s10-s17 | index of 2nd ISP subvector |
+| s18-s23 | index of 3rd ISP subvector |
+| s24-s30 | index of 4th ISP subvector |
+| s31-s37 | index of 5th ISP subvector |
+| s38-s42 | index of 6th ISP subvector |
+| s43-s47 | index of 7th ISP subvector |
+| subframe 1 | |
+| s48-s56 | adaptive codebook index |
+| s57 | LTP-filtering-flag |
+| s58-s68 | Codebook Index1 for track 1 |
+| s69-s79 | Codebook Index1 for track 2 |
+| s80-s90 | Codebook Index1 for track 3 |
+| s91-s101 | Codebook Index1 for track 4 |
+| s102-s112 | Codebook Index2 for track 1 |
+| s113-s123 | Codebook Index2 for track 2 |
+| s124-s134 | Codebook Index2 for track 3 |
+| s135-s145 | Codebook Index2 for track 4 |
+| s146-s152 | codebook gains |
+| s153-s156 | High-band energy |
+| subframe 2 | |
+| s157-s162 | adaptive codebook index (relative) |
+| s163-s262 | same description as s57-s156 |
+| subframe 3 | |
+| s263-s371 | same description as s48-s156 |
+| subframe 4 | |
+| s372-s477 | same description as s157-s262 |
+
+**Table 12b/G.722.2 – Source encoder output parameters in order of occurrence and bit allocation within the speech frame of 461 bits/20 ms, 23.05-kbit/s mode**
+
+| Bits (MSB-LSB) | Description |
+|-----------------------|------------------------------------|
+| s1 | VAD-flag |
+| s2-s9 | index of 1st ISP subvector |
+| s10-s17 | index of 2nd ISP subvector |
+| s18-s23 | index of 3rd ISP subvector |
+| s24-s30 | index of 4th ISP subvector |
+| s31-s37 | index of 5th ISP subvector |
+| s38-s42 | index of 6th ISP subvector |
+| s43-s47 | index of 7th ISP subvector |
+| subframe 1 | |
+| s48-s56 | adaptive codebook index |
+| s57 | LTP-filtering-flag |
+| s58-s68 | Codebook Index1 for track 1 |
+| s69-s79 | Codebook Index1 for track 2 |
+| s80-s90 | Codebook Index1 for track 3 |
+| s91-s101 | Codebook Index1 for track 4 |
+| s102-s112 | Codebook Index2 for track 1 |
+| s113-s123 | Codebook Index2 for track 2 |
+| s124-s134 | Codebook Index2 for track 3 |
+| s135-s145 | Codebook Index2 for track 4 |
+| s146-s152 | codebook gains |
+| subframe 2 | |
+| s153-s158 | adaptive codebook index (relative) |
+| s159-s254 | same description as s57-s152 |
+| subframe 3 | |
+| s255-s359 | same description as s48-s152 |
+| subframe 4 | |
+| s360-s461 | same description as s153-s254 |
+
+**Table 12c/G.722.2 – Source encoder output parameters in order of occurrence and bit allocation within the speech frame of 397 bits/20 ms, 19.85-kbit/s mode**
+
+| Bits (MSB-LSB) | Description |
+|----------------|------------------------------------|
+| s1 | VAD-flag |
+| s2-s9 | index of 1st ISP subvector |
+| s10-s17 | index of 2nd ISP subvector |
+| s18-s23 | index of 3rd ISP subvector |
+| s24-s30 | index of 4th ISP subvector |
+| s31-s37 | index of 5th ISP subvector |
+| s38-s42 | index of 6th ISP subvector |
+| s43-s47 | index of 7th ISP subvector |
+| subframe 1 | |
+| s48-s56 | adaptive codebook index |
+| s57 | LTP-filtering-flag |
+| s58-s67 | Codebook Index1 for track 1 |
+| s68-s77 | Codebook Index1 for track 2 |
+| s78-s79 | Pulse Selector for track 3 |
+| s80-s81 | Pulse Selector for track 4 |
+| s82-s91 | Codebook index2 for track 1 |
+| s92-s101 | Codebook index2 for track 2 |
+| s102-s115 | Codebook index for track 3 |
+| s116-s129 | Codebook index for track 4 |
+| s130-s136 | VQ gain |
+| subframe 2 | |
+| s137-s142 | adaptive codebook index (relative) |
+| s143-s222 | same description as s57-s136 |
+| subframe 3 | |
+| s223-s311 | same description as s48-s136 |
+| subframe 4 | |
+| s312-s397 | same description as s137-s222 |
+
+**Table 12d/G.722.2 – Source encoder output parameters in order of occurrence and bit allocation within the speech frame of 365 bits/20 ms, 18.25-kbit/s mode**
+
+| Bits (MSB-LSB) | Description |
+|-----------------------|------------------------------------|
+| s1 | VAD-flag |
+| s2-s9 | index of 1st ISP subvector |
+| s10-s17 | index of 2nd ISP subvector |
+| s18-s23 | index of 3rd ISP subvector |
+| s24-s30 | index of 4th ISP subvector |
+| s31-s37 | index of 5th ISP subvector |
+| s38-s42 | index of 6th ISP subvector |
+| s43-s47 | index of 7th ISP subvector |
+| subframe 1 | |
+| s48-s56 | adaptive codebook index |
+| s57 | LTP-filtering-flag |
+| s58-s59 | Pulse Selector for track 1 |
+| s60-s61 | Pulse Selector for track 2 |
+| s62-s63 | Pulse Selector for track 3 |
+| s64-s65 | Pulse Selector for track 4 |
+| s66-s79 | Codebook index for track 1 |
+| s80-s93 | Codebook index for track 2 |
+| s94-s107 | Codebook index for track 3 |
+| s108-s121 | Codebook index for track 4 |
+| s122-s128 | VQ gain |
+| subframe 2 | |
+| s129-s134 | adaptive codebook index (relative) |
+| s135-s206 | same description as s57-s128 |
+| subframe 3 | |
+| s207-s287 | same description as s48-s128 |
+| subframe 4 | |
+| s288-s365 | same description as s129-s206 |
+
+**Table 12e/G.722.2 – Source encoder output parameters in order of occurrence and bit allocation within the speech frame of 317 bits/20 ms, 15.85-kbit/s mode**
+
+| Bits (MSB-LSB) | Description |
+|-----------------------|------------------------------------|
+| s1 | VAD-flag |
+| s2-s9 | index of 1st ISP subvector |
+| s10-s17 | index of 2nd ISP subvector |
+| s18-s23 | index of 3rd ISP subvector |
+| s24-s30 | index of 4th ISP subvector |
+| s31-s37 | index of 5th ISP subvector |
+| s38-s42 | index of 6th ISP subvector |
+| s43-s47 | index of 7th ISP subvector |
+| subframe 1 | |
+| s48-s56 | adaptive codebook index |
+| s57 | LTP-filtering-flag |
+| s58-s70 | Codebook index for track 1 |
+| s71-s83 | Codebook index for track 2 |
+| s84-s96 | Codebook index for track 3 |
+| s97-s109 | Codebook index for track 4 |
+| s110-s116 | VQ gain |
+| subframe 2 | |
+| s117-s122 | adaptive codebook index (relative) |
+| s123-s182 | same description as s57-s116 |
+| subframe 3 | |
+| s183-s251 | same description as s48-s116 |
+| subframe 4 | |
+| s252-s317 | same description as s117-s182 |
+
+**Table 12f/G.722.2 – Source encoder output parameters in order of occurrence and bit allocation within the speech frame of 285 bits/20 ms, 14.25-kbit/s mode**
+
+| Bits (MSB-LSB) | Description |
+|-----------------------|------------------------------------|
+| s1 | VAD-flag |
+| s2-s9 | index of 1st ISP subvector |
+| s10-s17 | index of 2nd ISP subvector |
+| s18-s23 | index of 3rd ISP subvector |
+| s24-s30 | index of 4th ISP subvector |
+| s31-s37 | index of 5th ISP subvector |
+| s38-s42 | index of 6th ISP subvector |
+| s43-s47 | index of 7th ISP subvector |
+| subframe 1 | |
+| s48-s56 | adaptive codebook index |
+| s57 | LTP-filtering-flag |
+| s58-s70 | Codebook index for track 1 |
+| s71-s83 | Codebook index for track 2 |
+| s84-s92 | Codebook index for track 3 |
+| s93-s101 | Codebook index for track 4 |
+| s102-s108 | VQ gain |
+| subframe 2 | |
+| s109-s114 | adaptive codebook index (relative) |
+| s115-s166 | same description as s57-s108 |
+| subframe 3 | |
+| s167-s227 | same description as s48-s108 |
+| subframe 4 | |
+| s228-s285 | same description as s109-s166 |
+
+**Table 12g/G.722.2 – Source encoder output parameters in order of occurrence and bit allocation within the speech frame of 253 bits/20 ms, 12.65-kbit/s mode**
+
+| Bits (MSB-LSB) | Description |
+|-----------------------|------------------------------------|
+| s1 | VAD-flag |
+| s2-s9 | index of 1st ISP subvector |
+| s10-s17 | index of 2nd ISP subvector |
+| s18-s23 | index of 3rd ISP subvector |
+| s24-s30 | index of 4th ISP subvector |
+| s31-s37 | index of 5th ISP subvector |
+| s38-s42 | index of 6th ISP subvector |
+| s43-s47 | index of 7th ISP subvector |
+| subframe 1 | |
+| s48-s56 | adaptive codebook index |
+| s57 | LTP-filtering-flag |
+| s58-s66 | Codebook index for track 1 |
+| s67-s75 | Codebook index for track 2 |
+| s76-s84 | Codebook index for track 3 |
+| s85-s93 | Codebook index for track 4 |
+| s94-s100 | VQ gain |
+| subframe 2 | |
+| s101-s106 | adaptive codebook index (relative) |
+| s107-s150 | same description as s57-s100 |
+| subframe 3 | |
+| s151-s203 | same description as s48-s100 |
+| subframe 4 | |
+| s204-s253 | same description as s101-s150 |
+
+**Table 12h/G.722.2 – Source encoder output parameters in order of occurrence and bit allocation within the speech frame of 177 bits/20 ms, 8.85-kbit/s mode**
+
+| Bits (MSB-LSB) | Description |
+|-----------------------|------------------------------------|
+| s1 | VAD-flag |
+| s2-s9 | index of 1st ISP subvector |
+| s10-s17 | index of 2nd ISP subvector |
+| s18-s23 | index of 3rd ISP subvector |
+| s24-s30 | index of 4th ISP subvector |
+| s31-s37 | index of 5th ISP subvector |
+| s38-s42 | index of 6th ISP subvector |
+| s43-s47 | index of 7th ISP subvector |
+| subframe 1 | |
+| s48-s55 | adaptive codebook index |
+| s56-s60 | Codebook index for track 1 |
+| s61-s65 | Codebook index for track 2 |
+| s66-s70 | Codebook index for track 3 |
+| s71-s75 | Codebook index for track 4 |
+| s76-s81 | VQ gain |
+| subframe 2 | |
+| s82-s86 | adaptive codebook index (relative) |
+| s87-s112 | same description as s56-s81 |
+| subframe 3 | |
+| s113-s146 | same description as s48-s81 |
+| subframe 4 | |
+| s147-s177 | same description as s82-s112 |
+
+**Table 12i/G.722.2 – Source encoder output parameters in order of occurrence and bit allocation within the speech frame of 132 bits/20 ms, 6.60-kbit/s mode**
+
+| Bits (MSB-LSB) | Description |
+|----------------|------------------------------------|
+| s1 | VAD-flag |
+| s2-s9 | index of 1st ISP subvector |
+| s10-s17 | index of 2nd ISP subvector |
+| s18-s24 | index of 3rd ISP subvector |
+| s25-s31 | index of 4th ISP subvector |
+| s32-s37 | index of 5th ISP subvector |
+| subframe 1 | |
+| s38-s45 | adaptive codebook index |
+| s46-57 | Codebook Index |
+| s58-s63 | VQ gain |
+| subframe 2 | |
+| s64-s68 | adaptive codebook index (relative) |
+| s69-s86 | same description as s46-s63 |
+| subframe 3 | |
+| s87-s109 | same description as s64-s86 |
+| subframe 4 | |
+| s110-s132 | same description as s64-s86 |
+
+# 8 Homing sequences
+
+## 8.1 Functional description
+
+The adaptive multi-rate wideband speech codec is described in a bit-exact arithmetic to allow easy type approval as well as general testing of correct operation of the adaptive multi-rate wideband speech codec.
+
+The response of the codec to a predefined input sequence can only be foreseen if the internal state variables of the codec are in a predefined state at the beginning of the experiment. Therefore, the codec has to be put in a so-called home state before a bit-exact test can be performed. This is usually done by a reset (a procedure in which the internal state variables of the codec are set to their defined initial values). The codec mode of the speech encoder and speech decoder shall be set to the tested codec mode by external means at reset.
+
+To allow a reset of the codec in remote locations, special homing frames have been defined for the encoder and the decoder, thus enabling a codec homing by inband signalling.
+
+The codec homing procedure is defined in such a way that in either direction (encoder or decoder), the homing functions are called after the processing of the homing frame. The output corresponding to the first homing frame is therefore dependent on the used codec mode and the codec state when receiving that frame and hence usually not known. The response of the encoder to any further homing frame is by definition the corresponding decoder homing frame for the used codec mode. The response of the decoder to any further homing frame is by definition the encoder homing frame. This procedure allows homing of both the encoder and decoder from either side, if a loop back configuration is implemented, taking proper framing into account.
+
+## 8.2 Definitions
+
+**8.2.1 Encoder homing frame:** The encoder homing frame consists of 320 identical samples, each 13 bits long, with the least significant bit set to "one" and all other bits set to "zero". When written to 16-bit words with left justification, the samples have a value of 0008 hex. The speech decoder has to produce this frame as a response to the second and any further decoder homing frame if at least two decoder homing frames were input to the decoder consecutively. The encoder homing frame is identical for all codec modes.
+
+**8.2.2 Decoder homing frame:** There exist nine different decoder homing frames, which correspond to the nine AMR-WB codec modes. Using one of these codec modes, the corresponding decoder homing frame is the natural response of the speech encoder to the second and any further encoder homing frame if at least two encoder homing frames were input to the encoder consecutively. In Annex C, for each decoder homing frame, the parameter values are given.
+
+## 8.3 Encoder homing
+
+Whenever the adaptive multi-rate wideband speech encoder receives at its input an encoder homing frame exactly aligned with its internal speech frame segmentation, the following events take place:
+
+### *Step 1*
+
+The speech encoder performs its normal operation including VAD and SCR and produces in accordance with the used codec mode a speech parameter frame at its output which is in general unknown. But if the speech encoder was in its home state at the beginning of that frame, then the resulting speech parameter frame is identical to that decoder homing frame, which corresponds to the used codec mode (this is the way how the decoder homing frames were constructed).
+
+### *Step 2*
+
+After successful termination of that operation, the speech encoder provokes the homing functions for all submodules, including VAD and SCR, and sets all state variables into their home state. On the reception of the next input frame, the speech encoder will start from its home state.
+
+NOTE – Applying a sequence of $N$ encoder homing frames will cause at least $N-1$ decoder homing frames at the output of the speech encoder.
+
+## 8.4 Decoder homing
+
+Whenever the speech decoder receives at its input a decoder homing frame, which corresponds to the used codec mode, then the following events take place:
+
+### *Step 1*
+
+The speech decoder performs its normal operation and produces a speech frame at its output which is, in general, unknown. But if the speech decoder was in its home state at the beginning of that frame, then the resulting speech frame is replaced by the encoder homing frame. This would not naturally be the case but is forced by this definition here.
+
+### *Step 2*
+
+After successful termination of that operation, the speech decoder provokes the homing functions for all submodules, including the comfort noise generator, and sets all state variables into their home state. On the reception of the next input frame, the speech decoder will start from its home state.
+
+NOTE 1 – Applying a sequence of $N$ decoder homing frames will cause at least $N-1$ encoder homing frames at the output of the speech decoder.
+
+NOTE 2 – By definition, the first frame of each decoder test sequence must differ from the decoder homing frame at least in one bit position within the parameters for LPC and first subframe. Therefore, if the decoder
+
+is in its home state, it is sufficient to check only these parameters to detect a subsequent decoder homing frame. This definition is made to support a delay-optimized implementation.
+
+# 9 Voice Activity Detector (VAD)
+
+The function of the VAD algorithm is to indicate whether each 20-ms frame contains signals that should be transmitted, e.g., speech, music or information tones. The output of the VAD algorithm is a Boolean flag (`VAD_flag`) indicating presence of such signals. This flag is used in the AMR-WB speech coder and Annex B.
+
+## 9.1 VAD symbols
+
+For the purposes of this clause, the following symbols apply.
+
+### 9.1.1 VAD variables
+
+| | |
+|---------------------------|---------------------------------------------------------------------------------------------------|
+| bckr_est[n] | background noise estimate at the frequency band "n" |
+| burst_count | counts length of a speech burst, used by VAD hangover addition |
+| hang_count | hangover counter, used by VAD hangover addition |
+| level[n] | signal level at the frequency band "n" |
+| new_speech | pointer of the speech encoder, points a buffer containing last received samples of a speech frame |
+| noise_level | estimated noise level |
+| pow_sum | input power |
+| s(i) | samples of the input frame |
+| snr_sum | measure between input frame and noise estimate |
+| speech_level | estimated speech level |
+| stat_count | stationary counter |
+| stat_rat | measure indicating stationary of the input frame |
+| tone_flag | flag indicating the presence of a tone |
+| vad_thr | VAD threshold |
+| VAD_flag | Boolean VAD flag |
+| vadreg | intermediate VAD decision |
+
+### 9.1.2 VAD constants
+
+| | |
+|--------------------------|------------------------------------------------|
+| ALPHA_UP1 | constant for updating noise estimate |
+| ALPHA_DOWN1 | constant for updating noise estimate |
+| ALPHA_UP2 | constant for updating noise estimate |
+| ALPHA_DOWN2 | constant for updating noise estimate |
+| ALPHA3 | constant for updating noise estimate |
+| ALPHA4 | constant for updating average signal level |
+| ALPHA5 | constant for updating average signal level |
+| BURST_HIGH | constant for controlling VAD hangover addition |
+| BURST_P1 | constant for controlling VAD hangover addition |
+
+| | |
+|-------------------|------------------------------------------------|
+| BURST_SLOPE | constant for controlling VAD hangover addition |
+| COEFF3 | coefficient for the filter bank |
+| COEFF5_1 | coefficient for the filter bank |
+| COEFF5_2 | coefficient for the filter bank |
+| HANG_HIGH | constant for controlling VAD hangover addition |
+| HANG_LOW | constant for controlling VAD hangover addition |
+| HANG_P1 | constant for controlling VAD hangover addition |
+| HANG_SLOPE | constant for controlling VAD hangover addition |
+| FRAME_LEN | size of a speech frame, 256 samples (20 ms) |
+| MIN_SPEECH_LEVEL1 | constant for speech estimation |
+| MIN_SPEECH_LEVEL2 | constant for speech estimation |
+| MIN_SPEECH_SNR | constant for VAD threshold adaptation |
+| NO_P1 | constant for VAD threshold adaptation |
+| NO_SLOPE | constant for VAD threshold adaptation |
+| NOISE_MAX | maximum value for noise estimate |
+| NOISE_MIN | minimum value for noise estimate |
+| POW_TONE_THR | threshold for tone detection |
+| SP_ACTIVITY_COUNT | constant for speech estimation |
+| SP_ALPHA_DOWN | constant for speech estimation |
+| SP_ALPHA_UP | constant for speech estimation |
+| SP_CH_MAX | constant for VAD threshold adaptation |
+| SP_CH_MIN | constant for VAD threshold adaptation |
+| SP_EST_COUNT | constant for speech estimation |
+| SP_P1 | constant for VAD threshold adaptation |
+| SP_SLOPE | constant for VAD threshold adaptation |
+| STAT_COUNT | threshold for stationary detection |
+| STAT_THR | threshold for stationary detection |
+| STAT_THR_LEVEL | threshold for stationary detection |
+| THR_HIGH | constant for VAD threshold adaptation |
+| TONE_THR | threshold for tone detection |
+| VAD_POW_LOW | constant for controlling VAD hangover addition |
+
+### 9.1.3 Functions
+
+| | |
+|---|----------------|
+| + | Addition |
+| - | Subtraction |
+| * | Multiplication |
+| / | Division |
+
+$|x|$ absolute value of $x$
+AND Boolean AND
+OR Boolean OR
+
+$$\sum_{n=a}^b x(n) \quad x(a) + x(a+1) + \dots + x(b-1) + x(b)$$
+
+$$\text{MIN}(x, y) = \begin{cases} x, x \leq y \\ y, y < x \end{cases}$$
+
+$$\text{MAX}(x, y) = \begin{cases} x, x \geq y \\ y, y > x \end{cases}$$
+
+## 9.2 Functional description
+
+The block diagram of the VAD algorithm is depicted in Figure 4. The VAD algorithm uses parameters of the speech encoder to compute the Boolean VAD flag (`VAD_flag`). This input frame for VAD is sampled at the 12.8-kHz frequency and thus it contains 256 samples. Samples of the input frame ( $s(i)$ ) are divided into sub-bands and level of the signal (`level[n]`) in each band is calculated. The normalized open-loop pitch gains are the input for the tone detection function, gains which are calculated by open-loop pitch analysis of the speech encoder. The tone detection function computes a flag (`tone_flag`) which indicates presence of a signalling tone, voiced speech, or other strongly periodic signal. Background noise level (`bckr_est[n]`) is estimated in each band based on the VAD decision, signal stationarity and the tone-flag. Intermediate VAD decision is calculated by comparing input SNR (`level[n]/bckr_est[n]`) to an adaptive threshold. The threshold is adapted based on noise and long-term speech estimates. Finally, the VAD flag is calculated by adding hangover to the intermediate VAD decision.
+
+![Simplified block diagram of the VAD algorithm. The input signal s(i) enters a 'Filter bank and computation of sub-band levels' block, which outputs level[n]. The input ol_gain enters a 'Tone detection' block, which outputs tone_flag. Both level[n] and tone_flag enter a 'VAD decision' block, which outputs the final VAD_flag. The diagram is labeled G.722.2_F04.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg)
+
+```
+
+graph LR
+ s_i["s(i)"] --> FB["Filter bank and computation of sub-band levels"]
+ ol_gain --> TD["Tone detection"]
+ FB -- level[n] --> VD["VAD decision"]
+ TD -- tone_flag --> VD
+ VD --> VAD_flag
+ style FB fill:#fff,stroke:#000
+ style TD fill:#fff,stroke:#000
+ style VD fill:#fff,stroke:#000
+
+```
+
+G.722.2\_F04
+
+Simplified block diagram of the VAD algorithm. The input signal s(i) enters a 'Filter bank and computation of sub-band levels' block, which outputs level[n]. The input ol\_gain enters a 'Tone detection' block, which outputs tone\_flag. Both level[n] and tone\_flag enter a 'VAD decision' block, which outputs the final VAD\_flag. The diagram is labeled G.722.2\_F04.
+
+**Figure 4/G.722.2 – Simplified block diagram of the VAD algorithm**
+
+### 9.2.1 Filter bank and computation of sub-band levels
+
+The input signal is divided into frequency bands using a 12-band filter bank (Figure 5). Cut-off frequencies for the filter bank are shown in Table 13.
+
+**Table 13/G.722.2 – Cut-off frequencies for the filter bank**
+
+| Band number | Frequencies |
+|-------------|--------------|
+| 1 | 0-200 Hz |
+| 2 | 200-400 Hz |
+| 3 | 400-600 Hz |
+| 4 | 600-800 Hz |
+| 5 | 800-1200 Hz |
+| 6 | 1200-1600 Hz |
+| 7 | 1600-2000 Hz |
+| 8 | 2000-2400 Hz |
+| 9 | 2400-3200 Hz |
+| 10 | 3200-4000 Hz |
+| 11 | 4000-4800 Hz |
+| 12 | 4800-6400 Hz |
+
+Input for the filter bank is a speech frame pointed by the new\_speech pointer of the G.722.2 speech encoder. Input values for the filter bank are scaled down by one bit. This ensures safe scaling, i.e., saturation cannot occur during calculation of the filter bank.
+
+
+
+The diagram illustrates the filter bank structure. It begins with an input signal entering a 5th-order filter block. The output of this block is split into two 5th-order filter blocks. The top 5th-order block's output is split into a 3rd-order filter block (producing 4.8-6.4 kHz) and another 5th-order filter block. The bottom 5th-order block's output is split into a 5th-order filter block (producing 2.4-3.2 kHz) and another 5th-order filter block. This hierarchical decomposition continues, using 3rd-order filter blocks to further split the frequency bands. The final output bands, from top to bottom, are: 4.8-6.4 kHz, 4.0-4.8 kHz, 3.2-4.0 kHz, 2.4-3.2 kHz, 2.0-2.4 kHz, 1.6-2.0 kHz, 1.2-1.6 kHz, 0.8-1.2 kHz, 0.6-0.8 kHz, 0.4-0.6 kHz, 0.2-0.4 kHz, and 0.0-0.2 kHz. The label G.722.2\_F05 is present at the bottom right of the diagram.
+
+Block diagram of the G.722.2 filter bank showing a tree structure of 5th-order and 3rd-order filter blocks producing 12 frequency bands from 0.0 to 6.4 kHz.
+
+**Figure 5/G.722.2 – Filter bank**
+
+The filter bank consists of 5th- and 3rd-order filter blocks. Each filter block divides the input into high-pass and low-pass parts and decimates the sampling frequency by 2. The 5th-order filter block is calculated as follows:
+
+$$x_{lp}(i) = 0.5 \times (A_1(x(2 \times i)) + A_2(x(2 \times i + 1))) \quad (84a)$$
+
+$$x_{hp}(i) = 0.5 \times (A_1(x(2 \times i)) - A_2(x(2 \times i + 1))) \quad (84b)$$
+
+where:
+
+$x(i)$ input signal for a filter block
+
+$x_{lp}(i)$ low-pass component
+
+$x_{hp}(i)$ high-pass component
+
+The 3rd-order filter block is calculated as follows:
+
+$$x_{lp}(i) = 0.5 \times (x(2 \times i + 1) + A_3(x(2 \times i))) \quad (85a)$$
+
+$$x_{hp}(i) = 0.5 \times (x(2 \times i + 1) - A_3(x(2 \times i))) \quad (85b)$$
+
+The filters $A_1()$ , $A_2()$ , and $A_3()$ are first-order direct form all-pass filters, whose transfer function is given by:
+
+$$A(z) = \frac{C + z^{-1}}{1 + C \times z^{-1}} \quad (86)$$
+
+where $C$ is the filter coefficient.
+
+Coefficients for the all-pass filters $A_1()$ , $A_2()$ , and $A_3()$ are `COEFF5_1`, `COEFF5_2`, and `COEFF3`, respectively.
+
+Signal level is calculated at the output of the filter bank at each frequency band as follows:
+
+$$level(n) = \sum_{i=START_n}^{END_n} |x_n(i)| \quad (87)$$
+
+where:
+
+$n$ index for the frequency band
+
+$x_n(i)$ sample $i$ at the output of the filter bank at frequency band $n$
+
+$$START_n = \begin{cases} -6, & 1 \leq n \leq 4 \\ -12, & 5 \leq n \leq 8 \\ -24, & 9 \leq n \leq 11 \\ -48, & n = 12 \end{cases}$$
+
+$$END_n = \begin{cases} 7, & 1 \leq n \leq 4 \\ 15, & 5 \leq n \leq 8 \\ 31, & 9 \leq n \leq 11 \\ 63, & n = 12 \end{cases}$$
+
+Negative indices of $x_n(i)$ refer to the previous frame.
+
+### 9.2.2 Tone detection
+
+The purpose of the tone detection function is to detect information tones, vowel sounds and other periodic signals. The tone detection uses normalized open-loop pitch gains (`ol_gain`), which are received from the speech encoder. If the pitch gain is higher than the constant `TONE_THR`, tone is detected and the tone flag is set:
+
+```
+if (ol_gain > TONE_THR)
+ tone_flag = 1
+```
+
+The open-loop pitch search and correspondingly the tone flag is computed twice in each frame, except for mode 6.60 kbit/s, where it is computed only once.
+
+### 9.2.3 VAD decision
+
+The block diagram of the VAD decision algorithm is shown in Figure 6.
+
+![Simplified block diagram of the VAD decision algorithm. The input 'level[n]' is split into three parallel blocks: 'SNR computation', 'Background noise estimation', and 'Speech estimation'. 'SNR computation' outputs 'snr_sum' to a 'Comparison' block. 'Background noise estimation' outputs 'bckr_est[n]' to 'SNR computation', 'noise_level' to 'Threshold adaptation', and receives 'tone_flag' as input. 'Speech estimation' outputs 'speech_level' to 'Threshold adaptation' and receives feedback from the 'Hangover addition' block. 'Comparison' outputs 'vadreg' to 'Hangover addition' and receives 'vad_thr' from 'Threshold adaptation'. 'Hangover addition' outputs the final 'VAD_flag'. A label 'G.722.2_F06' is present near the bottom right of the diagram.](cc542843836eecb036b99cb270b54a1e_img.jpg)
+
+```
+graph TD
+ level_n["level[n]"] --> SNR["SNR computation"]
+ level_n --> BNE["Background noise estimation"]
+ level_n --> SE["Speech estimation"]
+ SNR --> snr_sum["snr_sum"]
+ snr_sum --> Comp["Comparison"]
+ BNE --> bckr_est_n["bckr_est[n]"]
+ bckr_est_n --> SNR
+ BNE --> noise_level["noise_level"]
+ noise_level --> TA["Threshold adaptation"]
+ BNE --> tone_flag["tone_flag"]
+ SE --> speech_level["speech_level"]
+ speech_level --> TA
+ TA --> vad_thr["vad_thr"]
+ vad_thr --> Comp
+ Comp --> vadreg["vadreg"]
+ vadreg --> HA["Hangover addition"]
+ HA --> VAD_flag["VAD_flag"]
+ HA --> SE
+ G722_2_F06["G.722.2_F06"]
+```
+
+Simplified block diagram of the VAD decision algorithm. The input 'level[n]' is split into three parallel blocks: 'SNR computation', 'Background noise estimation', and 'Speech estimation'. 'SNR computation' outputs 'snr\_sum' to a 'Comparison' block. 'Background noise estimation' outputs 'bckr\_est[n]' to 'SNR computation', 'noise\_level' to 'Threshold adaptation', and receives 'tone\_flag' as input. 'Speech estimation' outputs 'speech\_level' to 'Threshold adaptation' and receives feedback from the 'Hangover addition' block. 'Comparison' outputs 'vadreg' to 'Hangover addition' and receives 'vad\_thr' from 'Threshold adaptation'. 'Hangover addition' outputs the final 'VAD\_flag'. A label 'G.722.2\_F06' is present near the bottom right of the diagram.
+
+Figure 6/G.722.2 – Simplified block diagram of the VAD decision algorithm
+
+Power of the input frame is calculated as follows:
+
+$$frame\_pow = \sum_{i=0}^{FRAME\_LEN} s(i) \times s(i) \quad (88)$$
+
+where samples $s(i)$ of the input frame are pointed by the `new_speech` pointer of the speech encoder. Variable `pow_sum` is sum of the powers of the current and previous frames. If `pow_sum` is lower than the constant `POW_TONE_THR`, tone-flag is set to zero.
+
+The difference between the signal levels of the input frame and the background noise estimate is calculated as follows:
+
+$$snr\_sum = \sum_{n=1}^{12} MAX\left(1.0, \frac{level[n]}{bckr\_est[n]}\right)^2 \quad (89)$$
+
+where:
+
+level[n] signal level at band n
+
+bckr\_est[n] level of background noise estimate at band n
+
+VAD decision is made by comparing the variable `snr_sum` to a threshold. The threshold (`vad_thr`) is adapted to get desired sensitivity depending on estimated speech and background noise levels.
+
+Average background noise level is calculated by adding noise estimates at each band except the lowest band:
+
+$$noise\_level = \sum_{n=2}^{12} bckr\_est[n] \quad (90)$$
+
+If SNR is lower than the threshold (`MIN_SPEECH_SNR`), speech level is increased as follows:
+
+```
+If (speech_level/noise_level < MIN_SPEECH_SNR)
+ Speech_level = MIN_SPEECH_SNR × noise_level
+```
+
+Logarithmic value for noise estimate is calculated as follows:
+
+$$ilog2\_noise\_level = \log_2(noise\_level) \quad (91)$$
+
+Before logarithmic value from the speech estimate is calculated, `MIN_SPEECH_SNR × noise_level` is subtracted from the speech level to correct its value in low SNR situations.
+
+$$ilog2\_speech\_level = \log_2(speech\_level - MIN\_SPEECH\_SNR \times noise\_level) \quad (92)$$
+
+Threshold for VAD decision is calculated as follows:
+
+$$\begin{aligned} Vad\_thr = & NO\_SLOPE \times (ilog2\_noise\_level - NO\_P1) + THR\_HIGH + \\ & MIN(SP\_CH\_MAX, MAX(SP\_CH\_MIN, SP\_CH\_MIN \\ & + SP\_SLOPE \times (ilog2\_speech\_level - SP\_P1)))) , \end{aligned} \quad (93)$$
+
+where `NO_SLOPE`, `SP_SLOPE`, `NO_P1`, `SP_P1`, `THR_HIGH`, `SP_CH_MAX` and `SP_CH_MIN` are constants.
+
+The variable `vadreg` indicates intermediate VAD decision and it is calculated as follows:
+
+```
+if (snr_sum > vad_thr)
+ vadreg = 1
+else
+ vadreg = 0
+```
+
+#### 9.2.3.1 Hangover addition
+
+Before the final VAD flag is given, a hangover is added. The hangover addition helps to detect low power endings of speech bursts, which are subjectively important but difficult to detect.
+
+VAD\_flag is set to "1" if less than hang\_len frames with "0" decision have been elapsed since burst\_len consecutive "1" decisions have been detected. The variables hang\_len and burst\_len are computed using vad\_thr as follows:
+
+$$\text{hang\_len} = \text{MAX}(\text{HANG\_LOW}, (\text{HANG\_SLOPE} \times (\text{vad\_thr} - \text{HANG\_P1}) + \text{HANG\_HIGH})) \quad (94)$$
+
+$$\text{burst\_len} = \text{BURST\_SLOPE} \times (\text{vad\_thr} - \text{BURST\_P1}) + \text{BURST\_HIGH} \quad (95)$$
+
+The power of the input frame is compared to a threshold (VAD\_POW\_LOW). If the power is lower, the VAD flag is set to "0" and no hangover is added. The VAD\_flag is calculated as follows:
+
+```
+Vad_flag = 0;
+if (pow_sum < VAD_POW_LOW)
+ burst_count = 0
+ hang_count = 0
+else
+ if (vadreg = 1)
+ burst_count = burst_count + 1
+ if (burst_count ≥ burst_len)
+ hang_count = hang_len
+ VAD_flag = 1
+ else
+ burst_count = 0
+ if (hang_count > 0)
+ hang_count = hang_count - 1
+ VAD_flag = 1
+```
+
+#### 9.2.3.2 Background noise estimation
+
+Background noise estimate (*bckr\_est[n]*) is updated using amplitude levels of the previous frame. Thus, the update is delayed by one frame to avoid undetected start of speech bursts to corrupt the noise estimate. The update speed for the current frame is selected using intermediate VAD decisions (*vadreg*) and stationarity counter (*stat\_count*) as follows:
+
+```
+if (vadreg for the last 4 frames has been zero)
+ alpha_up = ALPHA_UP1
+ alpha_down = ALPHA_DOWN1
+else if (stat_count = 0)
+ alpha_up = ALPHA_UP2
+ alpha_down = ALPHA_DOWN2
+else
+ alpha_up = 0
+ alpha_down = ALPHA3
+```
+
+The variable *stat\_count* indicates stationary and its purpose is explained later in this clause. The variables *alpha\_up* and *alpha\_down* define the update speed for upwards and downwards, respectively. The update speed for each band "n" is selected as follows:
+
+```
+if (bckr_estm[n] < levelm-1[n])
+ alpha[n] = alpha_up
+else
+ alpha[n] = alpha_down
+```
+
+Finally, noise estimate is updated as follows:
+
+$$bckr\_est_{m+1}[n] = (1.0 - \alpha[n]) \times bckr\_est_m[n] + \alpha[n] \times level_{m-1}[n] \quad (96)$$
+
+where:
+
+n index of the frequency band
+
+m index of the frame
+
+Level of the background estimate ( $bckr\_est[n]$ ) is limited between constants $NOISE\_MIN$ and $NOISE\_MAX$ .
+
+If level of background noise increases suddenly, $vadreg$ will be set to "1" and background noise is not normally updated upwards. To recover from this situation, update of the background noise estimate is enabled if the intermediate VAD decision ( $vadreg$ ) is "1" for long enough time and spectrum is stationary. Stationary ( $stat\_rat$ ) is estimated using following equation:
+
+$$stat\_rat = \sum_{n=1}^{12} \frac{MAX(STAT\_THR\_LEVEL, MAX(ave\_level_m[n], level_m[n]))}{MAX(STAT\_THR\_LEVEL, MIN(ave\_level_m[n], level_m[n]))} \quad (97)$$
+
+where:
+
+$STAT\_THR\_LEVEL$ a constant
+
+n index of the frequency band
+
+m index of the frame
+
+$ave\_level$ average level of the input signal
+
+If the stationary estimate ( $stat\_rat$ ) is higher than a threshold, the stationary counter ( $stat\_count$ ) is set to the initial value defined by constant $STAT\_COUNT$ . If the signal is not stationary but speech has been detected (VAD decision is "1"), $stat\_count$ is decreased by one in each frame until it is zero.
+
+```
+if (5 last tone flags have been one)
+ stat_count = STAT_COUNT
+else
+ if (8 last internal VAD decisions have been zero) OR (stat_rat >
+STAT_THR)
+ stat_count = STAT_COUNT
+ else
+ if (vadreg) AND (stat_count ≠ 0)
+ stat_count = stat_count - 1
+```
+
+The average signal levels ( $ave\_level[n]$ ) are calculated as follows:
+
+$$ave\_level_{m+1}[n] = (1.0 - \alpha) \times ave\_level_m[n] + \alpha \times level_m[n] \quad (98)$$
+
+The update speed ( $\alpha$ ) for the previous equation is selected as follows:
+
+```
+if (stat_count = STAT_COUNT)
+ alpha = 1.0
+else if (vadreg = 1)
+ alpha = ALPHA5
+else
+ alpha = ALPHA4
+```
+
+#### 9.2.3.3 Speech level estimation
+
+First, full-band input level is calculated by summing input levels in each band except the lowest band as follows:
+
+$$in\_level = \sum_{n=2}^{12} level[n] \quad (99)$$
+
+A frame is assumed to contain speech if its level is high enough (MIN\_SPEECH\_LEVEL1), and the intermediate VAD flag (vadreg) is set or the input level is higher than the current speech level estimate. Maximum level (sp\_max) from SP\_EST\_COUNT frames is searched. If the SP\_ACTIVITY\_COUNT number of speech frames is located in within SP\_EST\_COUNT number of frames, speech level estimate is updated by the maximum signal level (sp\_max). The pseudo-code for the speech level estimation is as follows:
+
+```
+If (SP_ACTIVITY_COUNT > SP_EST_COUNT - sp_est_cnt + sp_max_cnt)
+ sp_est_cnt = 0
+ sp_max_cnt = 0
+ sp_max = 0
+
+sp_est_cnt = sp_est_cnt + 1
+if (in_level > MIN_SPEECH_LEVEL1) AND ((vadreg = 1) OR (in_level >
+speech_level))
+ sp_max_cnt = sp_max_cnt + 1
+ sp_max = MAX(sp_max, in_level)
+ if (sp_max_cnt > SP_ACTIVITY_COUNT)
+ if (sp_max > MIN_SPEECH_LEVEL2)
+ if (sp_max > speech_level)
+ speech_level = speech_level + SP_ALPHA_UP × (sp_max -
+speech_level)
+ else
+ speech_level = speech_level + SP_ALPHA_DOWN × (sp_max -
+speech_level)
+ sp_max_cnt = 0
+ sp_max = 0
+ sp_est_cnt = 0
+```
+
+# 10 Mandatory AMR-WB codec modes for the speech telephony service in 3GPP
+
+This clause should be observed when interoperability with 3GPP standard-based wireless networks is required.
+
+To facilitate the implementation of AMR-WB for the circuit-switched speech telephony service in 3GPP systems, the number of mandatory AMR-WB codec modes have been reduced to five. This allows for less complexity for the channel coding in terminals and networks. Following modes are used: 23.85, 15.85, 12.65, 8.85 and 6.60 kbit/s. Based on listening test results for the speech telephony service channels, these five modes are considered sufficient for high-quality speech telephony service. For other services and applications in 3GPP, all the 9 modes remain in use. All 9 source codecs are kept in the 3GPP AMR-WB codec, but the number of modes used for the speech telephony service is just limited to five.
+
+In order to improve interoperability, the allowed AMR-WB codec mode configurations within active codec sets (ACS), i.e., which modes can be configured to be used within the mode adaptation
+
+at the same time, were further limited. The following three configurations are allowed: Configuration A (6.60, 8.85, 12.65), Configuration B (6.60, 8.85, 12.65, 15.85) and Configuration C (6.60, 8.85, 12.65, 23.85). This improves Tandem Free Operation/Transcoder Free Operation (TFO/TrFO) interoperability in 3GPP in the various speech service transmission channels because all these configurations are compatible. They contain the same three lower modes. This enables immediate establishment of TFO/TrFO (where double transcoding for calls between mobile terminals is avoided). This restriction for allowed mode configurations also simplifies signalling (e.g., in call set-up and handovers) and also drastically simplifies testing.
+
+Table 14 summarizes the requirements for support of AMR-WB mode configurations in 3GPP speech telephony service.
+
+**Table 14/G.722.2 – Minimum requirements for AMR-WB modes
+in 3GPP speech telephony service**
+
+| Speech telephony service channel | Terminal | Network |
+|---------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|------------------------------------------------------|
+| TCH/F | Configuration A (6.60, 8.85 and 12.65) | Configuration A (6.60, 8.85 and 12.65) |
+| O-TCH/H | Configuration A (6.60, 8.85 and 12.65) | Configuration A (6.60, 8.85 and 12.65) |
+| O-TCH/F | Configurations A (6.60, 8.85, 12.65), B (6.60, 8.85, 12.65, 15.85) and C (6.60, 8.85, 12.65, 23.85) | Configuration A (6.60, 8.85 and 12.65) a) |
+| UTRAN | Configurations A (6.60, 8.85, 12.65), B (6.60, 8.85, 12.65, 15.85) and C (6.60, 8.85, 12.65, 23.85) | Configuration A (6.60, 8.85 and 12.65) a) |
+| a) Support for configurations B and C is optional. | | |
+
+# BIBLIOGRAPHY
+
+- [3] RABINER (L.R.), SCHAFER (R.W.): Digital processing of speech signals, *Prentice-Hall Int.*, 1978.
+- [4] ITAKURA (F.): Line spectral representation of linear predictive coefficients of speech signals, *J. Acoust. Soc. Amer.*, Vol. 57, Supplement No. 1, S35, 1975.
+- [5] BISTRITZ (Y.), PELLERM (S.): Immittance Spectral Pairs (ISP) for speech encoding, *Proc. ICASSP'93*, pp. II-9 to II-12.
+- [6] PALIWAL (K.K.), ATAL (B.S.): Efficient vector quantization of LPC parameters at 24 bits/frame, *IEEE Trans. Speech and Audio Processing*, Vol. 1, No. 1, pp. 3-14, 1993.
+- [7] KABAL (P.), RAMACHANDRAN (R.P.): The computation of line spectral frequencies using Chebyshev polynomials, *IEEE Trans. on ASSP*, Vol. 34, No. 6, pp. 1419-1426, 1986.
+- [8] JÄRVINEN (K.), VAINIO (J.), KAPANEN (P.), HONKANEN (T.), HAAVISTO (P.), SALAMI (R.), LAFLAMME (C.), ADOUL (J.-P.): GSM enhanced full rate speech codec, *Proc. ICASSP'97*, pp. 771-774.
+- [9] HONKANEN (T.), VAINIO (J.), JÄRVINEN (K.), HAAVISTO (P.), SALAMI (R.), LAFLAMME (C.), ADOUL (J.-P.): Enhanced full rate speech codec for IS-136 digital cellular system, *Proc. ICASSP'97*, pp. 731-734.
+- [10] HAGEN (R.), EKUDDEN (E.), JOHANSSON (B.), KLEIJN (W.B.): Removal of sparse-excitation artifacts in CELP, *Proc. ICASSP'98*, pp. I-145 to I-148.
+- [11] 3GPP TS 26.171: AMR Wideband Speech Codec; General description.
+- [12] 3GPP TS 26.190: AMR Wideband Speech Codec; Transcoding functions.
+- [13] 3GPP TS 26.173: AMR Wideband Speech Codec; ANSI-C code.
+- [14] 3GPP TS 26.174: AMR Wideband Speech Codec; Test sequences.
+- [15] 3GPP TS 26.193: AMR Wideband Speech Codec; Source Controlled Rate operation.
+- [16] 3GPP TS 26.194: AMR Wideband Speech Codec; Voice Activity Detector (VAD).
+- [17] 3GPP TS 26.192: AMR Wideband Speech Codec; Comfort Noise Aspects.
+- [18] 3GPP TS 26.191: AMR Wideband Speech Codec; Error Concealment of Lost Frames.
+- [19] 3GPP TS 26.201: AMR Wideband Speech Codec; Frame Structure.
+- [20] 3GPP TR 26.901: AMR Wideband Speech Codec; Feasibility study report.
+- [21] SCHROEDER (M.R.), ATAL (B.S.): Code-Excited Linear Prediction (CELP): High quality speech at very low bit rates, *Proc. ICASSP'85*, pp. 937-940, 1985.
+
+
+
+# SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure, Internet protocol aspects and Next Generation Networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
+
+
+
+A barcode consisting of vertical black lines of varying widths. Below the barcode, the number "26015" is printed, flanked by two asterisks: "\* 2 6 0 1 5 \*".
+
+Barcode with the number 26015 between two asterisks.
\ No newline at end of file
diff --git a/marked/G/T-REC-G.736-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.736-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0b78b9ad33df9b1f824d02a4743f4c7b6346ad12
--- /dev/null
+++ b/marked/G/T-REC-G.736-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bc0726a4e83123da3189bfa26dffd0080e2d16d49d0f5d83886537342f91bf4c
+size 8217
diff --git a/marked/G/T-REC-G.736-199303-I_PDF-E/91be14371a97fb5ce9eeb29ae18d07c3_img.jpg b/marked/G/T-REC-G.736-199303-I_PDF-E/91be14371a97fb5ce9eeb29ae18d07c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..16b7ceb412b7e54a228d2557d6ee5a2cd1302f6d
--- /dev/null
+++ b/marked/G/T-REC-G.736-199303-I_PDF-E/91be14371a97fb5ce9eeb29ae18d07c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:899151a6c0add022fd666cf6157a560d555c64174e09ea348050423664706f36
+size 30811
diff --git a/marked/G/T-REC-G.736-199303-I_PDF-E/e8ff6e66c77a8e96203c9f8db8f0986f_img.jpg b/marked/G/T-REC-G.736-199303-I_PDF-E/e8ff6e66c77a8e96203c9f8db8f0986f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6252e684c4de1bfe91568ff8754fe30564a94318
--- /dev/null
+++ b/marked/G/T-REC-G.736-199303-I_PDF-E/e8ff6e66c77a8e96203c9f8db8f0986f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0e98f42c0071da78b290e82ce5b8f529fa7134ec0948894ff776d2d8b39e97fe
+size 24118
diff --git a/marked/G/T-REC-G.736-199303-I_PDF-E/raw.md b/marked/G/T-REC-G.736-199303-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..2fbee105c22be2fed029f477b2f24e88fc5d3cb8
--- /dev/null
+++ b/marked/G/T-REC-G.736-199303-I_PDF-E/raw.md
@@ -0,0 +1,289 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**G.736**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(03/93)
+
+**GENERAL ASPECTS OF DIGITAL TRANSMISSION**
+
+---
+
+**CHARACTERISTICS OF A SYNCHRONOUS
+DIGITAL MULTIPLEX EQUIPMENT
+OPERATING AT 2048 kbit/s**
+
+**ITU-T Recommendation G.736**
+
+(Previously "CCITT Recommendation")
+
+---
+
+# FOREWORD
+
+The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecommunication Union. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+ITU-T Recommendation G.736 was revised by the ITU-T Study Group XV (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993).
+
+# --- NOTES
+
+1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector.
+
+In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms "CCITT, CCIR or IFRB" or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure.
+
+2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+# CONTENTS
+
+*Page*
+
+| | | |
+|-----|-----------------------------------------------|---|
+| 1 | General characteristics ..... | 1 |
+| 1.1 | Bit rate ..... | 1 |
+| 1.2 | Timing signal ..... | 1 |
+| 2 | Frame structure..... | 1 |
+| 3 | Frame alignment and CRC procedures ..... | 1 |
+| 3.1 | Loss of frame alignment ..... | 1 |
+| 3.2 | Recovery of frame alignment..... | 1 |
+| 3.3 | CRC multiframe alignment in time slot 0..... | 1 |
+| 3.4 | CRC bit monitoring ..... | 1 |
+| 4 | Fault conditions and consequent actions ..... | 2 |
+| 4.1 | Fault conditions ..... | 2 |
+| 4.2 | Consequent actions ..... | 2 |
+| 5 | Interfaces..... | 4 |
+| 6 | Jitter..... | 4 |
+| 6.1 | Jitter at 2048 kbit/s output ..... | 4 |
+| 6.2 | Jitter at tributary outputs ..... | 4 |
+| 6.3 | Jitter transfer functions ..... | 5 |
+
+
+
+# **CHARACTERISTICS OF A SYNCHRONOUS DIGITAL MULTIPLEX EQUIPMENT OPERATING AT 2048 kbit/s**
+
+*(Melbourne, 1988; revised at Helsinki, 1993)*
+
+This Recommendation gives the characteristics of a synchronous digital multiplex equipment, to combine up to 31 tributary channels at 64 kbit/s or $n \times 64$ kbit/s in a 2048 kbit/s digital stream.
+
+## **1 General characteristics**
+
+### **1.1 Bit rate**
+
+The nominal bit rate is 2048 kbit/s. The tolerance on this rate is $\pm 50$ parts per million (ppm).
+
+### **1.2 Timing signal**
+
+It should be possible to derive the transmit timing signal from any of the following:
+
+- a) from the received 2048 kbit/s signal;
+- b) from an external source at 2048 kHz (see 5);
+- c) from an internal oscillator.
+
+# **NOTES**
+
+- 1 The possibility of also deriving the transmit timing signal from a 64 kbit/s or $n \times 64$ kbit/s tributary is under study.
+- 2 The provision of a timing signal output, available for the purpose of synchronizing other equipments, is an option that might be required depending upon national synchronization arrangements.
+
+## **2 Frame structure**
+
+Refer to 2.3 and 5 of Recommendation G.704 for the basic frame structure and characteristics of the frame structure carrying channels at various bit rates in 2048 kbit/s. Bit 1 of the frame should be used in accordance with 2.2.3 of G.704, i.e. for a CRC check bit procedure.
+
+NOTE – In case of interconnection with multiplex equipment using time slot 16 for internal purposes, the use of this time slot for a 64 kbit/s tributary could be excluded. It could also be used for internal purposes according to Recommendation G.704.
+
+## **3 Frame alignment and CRC procedures**
+
+(An illustration of the procedure is given in Figure 2/G.706.)
+
+### **3.1 Loss of frame alignment**
+
+Refer to 4.1.1/G.706.
+
+### **3.2 Recovery of frame alignment**
+
+Refer to 4.1.2/G.706.
+
+### **3.3 CRC multiframe alignment in time slot 0**
+
+Refer to 4.2/G.706.
+
+### **3.4 CRC bit monitoring**
+
+Refer to 4.3/G.706.
+
+## 4 Fault conditions and consequent actions
+
+### 4.1 Fault conditions
+
+The digital muldex should detect the following fault conditions.
+
+#### 4.1.1 Failure of power supply
+
+#### 4.1.2 Failure of the incoming signal at the 64 kbit/s tributary input port
+
+NOTE – This detection is not mandatory when contradirectional interfaces are used.
+
+#### 4.1.3 Loss of the incoming signal at 2048 kbit/s
+
+NOTES
+
+1 The detection of this fault condition is required only when it does not result in an indication of loss of frame alignment.
+
+2 Where separate circuits are used for the digital signal and the timing signal, the loss of either or both should constitute the loss of the incoming signal.
+
+#### 4.1.4 Loss of frame alignment at 2048 kbit/s
+
+#### 4.1.5 Excessive bit error ratio detected by monitoring the frame alignment signal
+
+4.1.5.1 With a random bit error ratio of $\leq 1 \cdot 10^{-4}$ , the probability of activating the indication of fault condition in a few seconds should be less than $10^{-6}$ .
+
+With a random bit error ratio of $\geq 1 \cdot 10^{-3}$ , the probability of activating the indication of fault condition in a few seconds should be higher than 0.95.
+
+4.1.5.2 With a random bit error ratio of $\geq 1 \cdot 10^{-3}$ , the probability of deactivating the indication of fault condition in a few seconds should be almost 0.
+
+With a random bit error ratio $\leq 1 \cdot 10^{-4}$ , the probability of deactivating the indication of fault condition in a few seconds should be higher than 0.95.
+
+NOTE – The activating and deactivating period specified as “a few seconds” is intended to be in the order of 4 to 5 seconds.
+
+#### 4.1.6 Loss of timing signal
+
+The internal oscillator is not locked to the timing signals defined in items a) and b) of 1.2 and in Note 1 of 1.2. The detection criteria for this fault condition are under study.
+
+#### 4.1.7 Alarm condition received from the remote digital muldex
+
+See 4.2.
+
+### 4.2 Consequent actions
+
+Further to the detection of a fault condition, appropriate actions should be taken as specified in Table 1. The consequent actions are as follows.
+
+4.2.1 Prompt maintenance alarm indication generated to signify that performance is below acceptable standards and maintenance attention is required locally. When the AIS (see General Note below to 4.2) at a 2048 kbit/s input is detected, the prompt maintenance alarm indication association with loss of frame alignment (see 4.1.4) and excessive error ratio (see 4.1.5) should be inhibited, while the rest of the consequent actions are in accordance with those associated in Table 1 with the two fault conditions.
+
+NOTE – The location and provision of any visual and/or audible alarm activated by the alarm indications given in 4.2.1 is left to the discretion of each Administration.
+
+4.2.2 Alarm indication to the remote end transmitted by changing bit 3 of channel time slot 0 from the state 0 to the state 1 in those frames not containing the frame alignment signal. This should be effected as soon as possible.
+
+4.2.3 AIS applied to all 64 kbit/s or $n \times 64$ kbit/s outputs and state “1” to corresponding abcd bits in time slot 16 if used (see General Note below to 4.2). This action should be taken as soon as possible and not later than 2 ms after detection of the fault condition.
+
+TABLE 1/G.736
+
+#### **Fault conditions and consequent actions for the 2048 kbit/s synchronous digital multiplex equipment**
+
+| Equipment part | Fault conditions (see 4.1) | Consequent actions (see 4.2) | | | | |
+|----------------------------------|---------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|---------------------------------------------------|-------------------------|-------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|
+| | | Prompt maintenance alarm indication generated | Alarm indication to the remote end transmitted | | AIS applied to all 64 kbit/s and $n \times 64$ kbit/s outputs State 1 in time slot 16 (Note 1) | AIS applied to the relevant time slots of the 2048 kbit/s composite signal State 1 in time slot 16 (Note 1) |
+| | | | Backward alarm | Forward alarm | | |
+| Multiplexer and demultiplexer | Failure of power supply | Yes | Yes (if practicable) | Yes (if practicable) | Yes (if practicable) | Yes (if practicable) |
+| | Loss of timing signal | Yes | Yes (Note 2) | Yes (Note 2) | | |
+| Multiplexer only | Loss of incoming signal at a 64 kbit/s or $n \times 64$ kbit/s input (see Note under 4.1.2) | Yes | | | | Yes |
+| Demultiplexer only | Loss of incoming signal at 2048 kbit/s | Yes | Yes | | Yes | |
+| | Loss of frame alignment (see Note 2 of 4.2 of Rec. G.706) | Yes (see 4.2.1) | Yes | | Yes | |
+| | Error ratio $1 \cdot 10^{-3}$ alignment signal | Yes (see 4.2.1) | Yes | | Yes | |
+| | Alarm indication received from the remote end | | | | | |
+
+# NOTES
+
+- Applicable if time slot 16 is used for channel associated signalling or channel associated supervision/maintenance only.
+
+- In order to enable appropriate actions at the remote end, the indication of loss of timing signal should not be transmitted in bit 3 of time slot 0. The transmission of this indication is under study.
+
+- A Yes in the table signifies that an action should be taken as a consequence of the relevant fault condition. An open space in the table signifies that the relevant action should not be taken as a consequence of the relevant fault condition, if the condition is the only one present. If more than one fault condition is simultaneously present, the relevant action should be taken if, for at least one of the conditions, a Yes is defined in relation to this action.
+
+**4.2.4** AIS applied to relevant time slots in the composite 2048 kbit/s output signal (if supervision of incoming 64 kbit/s signal is provided).
+
+GENERAL NOTE to 4.2 – The equivalent binary content of the alarm indication signal (AIS) is a continuous stream of binary 1s.
+
+The strategy for detecting the presence of the AIS should be such that with a high probability the AIS is detectable even in the presence of random errors having a mean error ratio $\leq 1 \cdot 10^{-3}$ . Nevertheless, a signal in which all the binary elements, with the exception of the frame alignment signal, are in the state 1, should not be taken as an AIS.
+
+NOTE – All timing requirements quoted apply equally to restoration, subsequent to the fault condition clearing.
+
+## **5 Interfaces**
+
+The digital interfaces at 2048 kbit/s should be in accordance with Recommendation G.703. This interface should be used for both $n \times 64$ kbit/s tributaries and 2048 kbit/s multiplexed signal.
+
+The digital interfaces at 64 kbit/s should be of either the codirectional or the contradirectional type specified in Recommendation G.703. The interface for external synchronization of the transmit timing signal should be in accordance with G.703.
+
+NOTE – In the case of the 64 kbit/s codirectional interface, the design of the input ports should take account of the need to provide octet alignment, to allow controlled slips when the tributary timing and that of the multiplexer timing source are plesiochronous, and to absorb jitter and wander up to the limits given in Recommendation G.823. In the case of the $n \times 64$ kbit/s interface, the design of the input ports should similarly take account of the need to provide frame alignment to allow controlled slips.
+
+## **6 Jitter**
+
+### **6.1 Jitter at 2048 kbit/s output**
+
+**6.1.1** In the case where the transmitting timing signal is derived from an internal oscillator, the peak-to-peak jitter at the 2048 kbit/s output should not exceed 0.05 UI when it is measured within the frequency range from $f_1 = 20$ Hz to $f_4 = 100$ kHz. See Figure 2/G.823.
+
+**6.1.2** In the case where the transmitting timing signal is derived from an external source having no jitter, the peak-to-peak jitter at the 2048 kbit/s output should not exceed 0.05 UI when it is measured within the frequency range from $f_1 = 20$ Hz to $f_4 = 100$ kHz.
+
+**6.1.3** In the case where the transmitting timing signal is derived from the incoming 2048 kbit/s signal having no jitter, the peak-to-peak jitter at the 2048 kbit/s output should not exceed 0.10 UI when it is measured within the frequency range from $f_1 = 20$ Hz to $f_4 = 100$ kHz. The equivalent binary content of the test signal applied at the 2048 kbit/s input shall be a pseudo-random bit sequence of length $2^{15} - 1$ as specified in Recommendation O.151.
+
+NOTE – It may be necessary to include a frame alignment signal in the test signal to enable the measurement to be carried out.
+
+### **6.2 Jitter at tributary outputs**
+
+**6.2.1** In the case where the incoming 2048 kbit/s signal has no jitter, the peak-to-peak jitter at the 64 kbit/s output should not exceed 0.025 UI when it is measured within the range from $f_1 = 20$ Hz to $f_4 = 10$ kHz. The equivalent binary content of the test signal applied to the 2048 kbit/s input shall be a pseudo-random bit sequence of length $2^{15} - 1$ as specified in Recommendation O.151.
+
+**6.2.2** The peak-to-peak jitter value for the 2048 kbit/s tributary signal when there is no jitter at the 2048 kbit/s input signal should not exceed 0.10 UI when measured within the range from $f_1 = 20$ Hz to $f_4 = 10$ kHz.
+
+NOTE – In order to carry out these measurements without invoking AIS at the 64 and $n \times 64$ kbit/s outputs it will normally be necessary to include a frame alignment signal in the test signal.
+
+### 6.3 Jitter transfer functions
+
+6.3.1 The jitter transfer function between the 2048 kHz external synchronization signal and the 2048 kbit/s output signal should not exceed the gain/frequency limits given in Figure 1. The 2048 kHz signal shall be modulated with sinusoidal jitter. This may also be applicable to the $n \times 64$ kbit/s tributary output.
+
+
+
+Figure 1/G.736: Jitter transfer function without jitter reduction. The graph plots 20 log (J\_out / J\_in) in dB on the y-axis (from -19.5 to 0.5) against frequency on the x-axis. The curve starts at 0.5 dB from f\_0 to 1.4 kHz, then slopes down at 20 dB/decade to -19.5 dB at 36 kHz, and then slopes up at 20 dB/decade to -8.4 dB at 100 kHz. The area above the curve is shaded. A label '(Note 3)' points to the downward slope. The code T1514170-93/d01 is at the bottom right.
+
+# NOTES
+
+- 1 The frequency $f_0$ should be less than 20 Hz, and as low as possible (e.g. 10 Hz), taking into account the limitations of measuring equipment.
+- 2 To achieve accurate measurements, the use of a selective method is recommended with a bandwidth sufficiently small referred to the relevant measurement frequency but not wider than 40 Hz.
+- 3 For interfaces within national boundaries, this characteristic may be used.
+
+FIGURE 1/G.736
+Jitter transfer function without jitter reduction
+
+Some Administrations require that equipment is fitted with jitter reducers. In this case, the jitter transfer function should not exceed the gain/frequency limits given in Figure 2.
+
+
+
+Figure 2/G.736: Jitter transfer function with jitter reduction. The graph plots 20 log (J\_out / J\_in) in dB on the y-axis (from -19.5 to 0.5) against frequency on the x-axis. The curve starts at 0.5 dB from f\_0 to 40 Hz, then slopes down at 20 dB/decade to -19.5 dB at 400 Hz, and remains at -19.5 dB up to 100 kHz. The area above the curve is shaded. A label '(Note 3)' points to the downward slope. The code T1514180-93/d02 is at the bottom right.
+
+# NOTES
+
+- 1 The frequency $f_0$ should be less than 20 Hz, and as low as possible (e.g. 10 Hz), taking into account the limitations of measuring equipment.
+- 2 To achieve accurate measurements, the use of a selective method is recommended with a bandwidth sufficiently small referred to the relevant measurement frequency but not wider than 40 Hz.
+
+FIGURE 2/G.736
+Jitter transfer function with jitter reduction
+
+**6.3.2** In the case where the transmitting timing is derived from the incoming signal, the jitter transfer function between the 2048 kbit/s input and 2048 kbit/s output or $n \times 64$ kbit/s tributary signal shall be as specified in 6.3.1.
+
+# NOTES
+
+1 The 2048 kbit/s test signal shall be modulated by sinusoidal jitter. The equivalent binary content of the test signal shall be 1000.
+
+2 It may be necessary to include a frame alignment signal in the test signal to enable the measurement to be carried out.
+
+**6.3.3** The jitter transfer function between the 2048 kbit/s input and the 64 kbit/s output should not exceed $-29.6$ dB when measured over the frequency range $f_0$ to 10 kHz. The frequency $f_0$ should be less than 20 Hz and as low as possible (e.g. 10 Hz), taking into account the limitations of measuring equipment.
+
+The jitter transfer function between the 2048 kbit/s input signal and a $n \times 64$ kbit/s tributary output signal shall be as specified in 6.3.1.
+
+# NOTES
+
+1 The 2048 kbit/s test signal shall be modulated by sinusoidal jitter. The equivalent binary content of the test signal shall be 1000.
+
+2 In order to carry out these measurements without invoking AIS at the 64 and $n \times 64$ kbit/s outputs it will normally be necessary to include a frame alignment signal in the test signal.
+
+3 In the case of 64 kbit/s tributaries, the jitter reduction of $1/32$ due to demultiplexing is equivalent to $-30.1$ dB.
\ No newline at end of file
diff --git a/marked/G/T-REC-G.761-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.761-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fd6d37344e1dcb73e876a09f0e28fcc3cc12e0bf
--- /dev/null
+++ b/marked/G/T-REC-G.761-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:473a66f8b6837745a7f32ac1741f274c5a10ec4eec34cbcf59ae9cab1ea41190
+size 7270
diff --git a/marked/G/T-REC-G.761-198811-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/G/T-REC-G.761-198811-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1dc3ae8b2c58114e338124819c1ac0c24e1a6954
--- /dev/null
+++ b/marked/G/T-REC-G.761-198811-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1ab341771b8fcedd06b0a6bf3b93eb755ca9115e89e89f670b91626e0ef08fe3
+size 16997
diff --git a/marked/G/T-REC-G.761-198811-I_PDF-E/f89631cc38aa971e8d15cbffe28f1183_img.jpg b/marked/G/T-REC-G.761-198811-I_PDF-E/f89631cc38aa971e8d15cbffe28f1183_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4d3f3fac80b7f752f22e5d731e2075d3a811d5e0
--- /dev/null
+++ b/marked/G/T-REC-G.761-198811-I_PDF-E/f89631cc38aa971e8d15cbffe28f1183_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cb8c5a375275162ae0e951f7b2379eadc17aa6ce3b888b6c5a4a4ee0286e8688
+size 30540
diff --git a/marked/G/T-REC-G.768-200103-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.768-200103-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f
--- /dev/null
+++ b/marked/G/T-REC-G.768-200103-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2468dfa77e8d32611a5fe8a2ebb904676994eeb54463226fd865698560c960c
+size 8232
diff --git a/marked/G/T-REC-G.768-200103-I_PDF-E/35127fe87029df6f5f0b2ee85f6193f1_img.jpg b/marked/G/T-REC-G.768-200103-I_PDF-E/35127fe87029df6f5f0b2ee85f6193f1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..acde95eea8854a522fb3b6bef26da3aa77ea4f57
--- /dev/null
+++ b/marked/G/T-REC-G.768-200103-I_PDF-E/35127fe87029df6f5f0b2ee85f6193f1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1da157cceb5ece1588e729ccb96bee46822a503666adb44ec9b1f44aa85ea230
+size 22905
diff --git a/marked/G/T-REC-G.768-200103-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/G/T-REC-G.768-200103-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b5974684d0d3741012eaee9735a18943c5aa4eed
--- /dev/null
+++ b/marked/G/T-REC-G.768-200103-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ca055ba65e96ee413df5e1ebe786f1c250988463d51cb4a5381afc84fc1b244d
+size 85947
diff --git a/marked/G/T-REC-G.768-200103-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/G/T-REC-G.768-200103-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7ae057861e5a72c8cd74d89d44b216cf0b7fd43d
--- /dev/null
+++ b/marked/G/T-REC-G.768-200103-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:934bf0af3617ca9a33d585500bde1209df73af482ff0dc3170b327c38beccde3
+size 22743
diff --git a/marked/G/T-REC-G.768-200103-I_PDF-E/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/marked/G/T-REC-G.768-200103-I_PDF-E/e9d825d87c5f85c8dba0664eace96ef4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1125246e906137db02b62de916ee4eb614dfe26f
--- /dev/null
+++ b/marked/G/T-REC-G.768-200103-I_PDF-E/e9d825d87c5f85c8dba0664eace96ef4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8c371286fdf6c659390cafc9aa1dc13302c6dca900440f448822edc8d344bca2
+size 61958
diff --git a/marked/G/T-REC-G.768-200103-I_PDF-E/raw.md b/marked/G/T-REC-G.768-200103-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..59f611fd99f7b3588b20ff6e46fd3a0c0ee480a9
--- /dev/null
+++ b/marked/G/T-REC-G.768-200103-I_PDF-E/raw.md
@@ -0,0 +1,1088 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**G.768**
+
+(03/2001)
+
+SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
+DIGITAL SYSTEMS AND NETWORKS
+
+Digital terminal equipments – Principal characteristics of
+transcoder and digital multiplication equipment
+
+---
+
+**Digital circuit multiplication equipment using
+8 kbit/s CS-ACELP**
+
+ITU-T Recommendation G.768
+
+(Formerly CCITT Recommendation)
+
+---
+
+# ITU-T G-SERIES RECOMMENDATIONS
+
+## TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 |
+| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 |
+| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 |
+| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 |
+| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 |
+| TESTING EQUIPMENTS | G.500–G.599 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.600–G.699 |
+| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 |
+| General | G.700–G.709 |
+| Coding of analogue signals by pulse code modulation | G.710–G.719 |
+| Coding of analogue signals by methods other than PCM | G.720–G.729 |
+| Principal characteristics of primary multiplex equipment | G.730–G.739 |
+| Principal characteristics of second order multiplex equipment | G.740–G.749 |
+| Principal characteristics of higher order multiplex equipment | G.750–G.759 |
+| Principal characteristics of transcoder and digital multiplication equipment | G.760–G.769 |
+| Operations, administration and maintenance features of transmission equipment | G.770–G.779 |
+| Principal characteristics of multiplexing equipment for the synchronous digital hierarchy | G.780–G.789 |
+| Other terminal equipment | G.790–G.799 |
+| DIGITAL NETWORKS | G.800–G.899 |
+| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+# **Digital circuit multiplication equipment using 8 kbit/s CS-ACELP**
+
+## **Summary**
+
+This Recommendation specifies the elements of DCME using 8 kbit/s CS-ACELP, Digital Speech Interpolation (DSI) and facsimile demodulation/remodulation in order to achieve interworking of such equipment. It specifies extensions and deviations for ITU-T G.763, ITU-T G.766 and ITU-T G.767 which specify a 32 kbit/s ADPCM DCME, and facsimile demodulation/remodulation and 16 kbit/s LD-CELP DCME respectively.
+
+## **Source**
+
+ITU-T Recommendation G.768 was prepared by ITU-T Study Group 15 (2001-2004) and approved under the WTSA Resolution 1 procedure on 15 March 2001.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2001
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU.
+
+## CONTENTS
+
+###### Page
+
+| | | |
+|-------|-----------------------------------------------------|---|
+| 1 | Scope..... | 1 |
+| 2 | Reference ..... | 1 |
+| 3 | Terms and definitions ..... | 1 |
+| 4 | Abbreviations..... | 3 |
+| 5 | DCME frame structure..... | 4 |
+| 5.1 | General..... | 4 |
+| 5.1.1 | Supported services..... | 4 |
+| 5.1.2 | PCM frame ..... | 4 |
+| 5.1.3 | DCME frame and subframe..... | 4 |
+| 5.1.4 | DCME multiframe..... | 4 |
+| 5.1.5 | Relationship between the frames..... | 4 |
+| 6 | Trunk interface structure..... | 5 |
+| 6.1 | Type of trunk interface ..... | 5 |
+| 6.2 | Number of trunk interfaces, trunk channels..... | 5 |
+| 6.3 | Type of trunk channels ..... | 5 |
+| 7 | Bearer interface structure..... | 5 |
+| 7.1 | Cliques, destinations and bearers..... | 5 |
+| 7.1.1 | Number of cliques ..... | 5 |
+| 7.1.2 | Number of destinations..... | 6 |
+| 7.1.3 | Multiple outgoing bearers..... | 6 |
+| 7.2 | Assignment message..... | 6 |
+| 7.3 | Bearer Channels (BC)..... | 7 |
+| 7.4 | Control Channel (CC)..... | 7 |
+| 7.5 | BC numbering and the use of the bearer frame ..... | 7 |
+| 7.5.1 | 8 bit (64 kbit/s transparent calls) BCs ..... | 8 |
+| 7.5.2 | 5 bit (VBD optimized 40 kbit/s LD-CELP) BCs..... | 8 |
+| 7.5.3 | 4 bit BCs (bit bank, fax bank)..... | 8 |
+| 7.5.4 | 2 bit (16 kbit/s ADPCM for SS No. 5 tone) BCs ..... | 8 |
+| 7.5.5 | Normal range 1 bit BCs (CS-ACELP voice)..... | 8 |
+| 7.5.6 | Overload BCs ..... | 8 |
+| 7.5.7 | Pre-assigned BCs..... | 8 |
+| 8 | Control channel..... | 8 |
+| 8.1 | General..... | 8 |
+| 8.2 | Number of assignment messages..... | 9 |
+| 8.2.1 | BCC/ECC criterion..... | 9 |
+
+| | Page |
+|------------------------------------------------------------------------------|-------------|
+| 8.2.2 Total number of assignment messages ..... | 9 |
+| 8.3 Control channel content ..... | 9 |
+| 8.3.1 CC synchronization ..... | 9 |
+| 8.3.2 Assignment messages ..... | 10 |
+| 8.3.3 Asynchronous data word ..... | 12 |
+| 8.3.4 Error correction..... | 15 |
+| 8.4 CC message transmission scheme ..... | 16 |
+| 8.4.1 Control channel structure..... | 16 |
+| 8.4.2 CC bit mapping..... | 16 |
+| 9 Low bit-rate codecs..... | 21 |
+| 9.1 Variable bit rate and overload channel creation ..... | 21 |
+| 9.1.1 Principles ..... | 21 |
+| 9.1.2 Overload channel creation..... | 21 |
+| 9.2 Codec to support SS No. 5 tone signals..... | 24 |
+| 9.3 Frame alignment between the different types of codecs..... | 24 |
+| 9.4 Processing delay compensation between the different types of codecs..... | 24 |
+| 9.5 Synchronous reset between encoder and corresponding decoder..... | 24 |
+| 10 Channel check procedure..... | 25 |
+| 11 Facsimile demodulation/remodulation ..... | 25 |
+| 12 System statistics measurement..... | 25 |
+
+# Digital circuit multiplication equipment using 8 kbit/s CS-ACELP
+
+# 1 Scope
+
+This Recommendation specifies the elements of DCME using 8 kbit/s CS-ACELP, Digital Speech Interpolation (DSI) and facsimile demodulation/remodulation in order to achieve interworking of such equipment. It is an extension to ITU-T G.763 (Digital circuit multiplication equipment using 32 kbit/s ADPCM and digital speech interpolation) and ITU-T G.766 (Facsimile demodulation/remodulation for DCME), as it specifies the deviations of the 8 kbit/s DCME from ITU-T G.763.
+
+# 2 Reference
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
+
+- ITU-T G.726 (1990), *40, 32, 24, 16 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM)*.
+- ITU-T G.728 Annex J (1999), *Variable bit-rate operation of LD-CELP mainly for voiceband-data applications in DCME*.
+- ITU-T G.729 (1996), *Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited linear prediction (CS-ACELP)*.
+- ITU-T G.729 Annex D (1998), *6.4 kbit/s CS-ACELP speech coding algorithm*.
+- ITU-T G.763 (1998), *Digital circuit multiplication equipment using G.726 ADPCM and digital speech interpolation*.
+- ITU-T G.766 (1996), *Facsimile demodulation/remodulation for digital circuit multiplication equipment*.
+- ITU-T G.767 (1998), *Digital circuit multiplication equipment using 16 kbit/s LD-CELP, digital speech interpolation and facsimile demodulation/remodulation*.
+
+# 3 Terms and definitions
+
+In addition to the terms and definitions of ITU-T G.763 and ITU-T G.766, the following definitions are listed in this Recommendation:
+
+**3.1 Basic Control Channel (BCC):** A DCME control channel used for a pool with IT numbers less than or equal to 240. It can accommodate four assignment messages/frame.
+
+**3.2 expanded control channel (ECC):** A DCME control channel used for a pool with IT numbers more than 240. It can accommodate eight assignment messages/frame.
+
+**3.3 digital circuit multiplication equipment (DCME):** A general class of equipment which permits concentration of a number of 64 kbit/s PCM encoded input trunk channels on a reduced number of transmission channels (see 3.6).
+
+**3.4 digital speech interpolation (DSI):** A process which, when used in the transmit unit of a DCME, causes a trunk channel to be connected to a bearer channel only when activity is actually present on the trunk channel. This, by exploiting the probability of the speech activity factor of trunk channels being less than 1.0, enables the traffic from a number of trunk channels to be concentrated and carried by a lesser number of time-shared bearer channels. The signals carried by a bearer channel therefore represent interleaved bursts of speech signals derived from a number of different trunk channels.
+
+NOTE – A process complementary to DSI is required in the receive unit of a DCME, i.e. assignment of the interleaved bursts to their appropriate trunk channels.
+
+**3.5 DCME frame:** A time interval, the beginning of which is identified by a unique word in the control channel. The DCME frame need not coincide with the multi-frames defined in Recommendation G.704. The format specification of the DCME frame includes channel boundaries and bit position significance.
+
+**3.6 transmission channel:** A 64 kbit/s time slot within a DCME frame.
+
+**3.7 bearer channel (BC):** A bearer channel is a unidirectional, digital transmission path from the transmit unit of one DCME to the receive unit of a second associated DCME used to carry concentrated traffic between the two DCMEs.
+
+NOTE 1 – A number of bearer channels in each direction of transmission form the both-way link required between two DCMEs. This link may be, for example, a 2048 kbit/s system.
+
+NOTE 2 – A bearer channel may have any of the following instantaneous bit rates: either 64, 40, 16, 8, or 6.4 kbit/s.
+
+**3.8 intermediate trunk (IT):** A channel mapping designation which ranges between 1 and 620 which relates each trunk channel to an internal numbering designation used within the DCME for conveying trunk channel to bearer channel connectivity via the control channel (see 3.10).
+
+**3.9 assignment message:** The message specifying the interconnections required between trunk channels and bearer channels.
+
+**3.10 control channel (CC):** A unidirectional transmission path from the transmit unit of one DCME to the receive unit of one or more associated DCMEs which is dedicated primarily to carrying channel assignment messages. In addition, the control channel transmits other messages such as idle noise levels, dynamic load control, alarm messages and, optionally, line signalling information.
+
+NOTE – An alternative name for control channel is "assignment channel".
+
+**3.11 overload channels:** The additional bearer channel capacity which is generated using VBR encoding to minimize or eliminate DSI competitive clipping.
+
+**3.12 freeze-out:** The condition when a trunk channel becomes active and cannot immediately be assigned to a bearer channel, due to lack of available transmission capacity.
+
+**3.13 freeze-out fraction (FOF):** The ratio of the total time that the individual channels experience the freeze-out condition to the total time of the active intervals and their corresponding hangover times and front end delays, for all trunks over a fixed interval of time.
+
+**3.14 clique:** A set of bearer channels which are associated with a set of trunk channels which are independent in operation and control from other bearer channels. The set of trunk channels is directed to a single destination.
+
+NOTE – An alternative term for clique is "bundle".
+
+**3.15 multi-clique mode:** A DCME operational mode in which more than one clique is used when each clique is associated with a different destination.
+
+**3.16 multi-destination mode:** A DCME operational mode where traffic is exchanged between more than two (2) corresponding DCMEs simultaneously and trunk channel traffic is interpolated over a pool of available bearer channels for all destinations having traffic in the pool. The transmit trunk channels are designated to receive trunk channels at corresponding locations.
+
+**3.17 facsimile demodulation/remodulation:** Processing introduced in a DCME where facsimile traffic is discriminated from voiceband data; subsequently demodulated to recover the baseband digital signal; time-division multiplexed into 32 kbit/s DCME bearers; demultiplexed in the DCME receive unit; and remodulated using the same modulation scheme as used on the original signal received by the DCME transmit unit.
+
+# 4 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|----------|--------------------------------------------------------------|
+| ADPCM | Adaptive Differential Pulse Code Modulation |
+| AM | Assignment Message |
+| BB | Bit Bank |
+| BC | Bearer Channel |
+| BCC | Basic Control Channel |
+| BCH | Base-Chaudhuri-Hocquengheim |
+| CC | Control Channel |
+| CCT | Channel Check Test |
+| CME | Circuit Multiplication Equipment |
+| CS-ACELP | Conjugate Structure Algebraic-Code-Excited Linear-Prediction |
+| DCME | Digital Circuit Multiplication Equipment |
+| DLC | Dynamic Load Control |
+| DSI | Digital Speech Interpolation |
+| ECC | Expanded Control Channel |
+| FB | Fax Bank |
+| FEC | Forward Error Correction |
+| FOF | Freeze-Out Fraction |
+| HL | High Load |
+| IT | Intermediate Trunk |
+| LD-CELP | Low-Delay Code-Excited Linear Prediction |
+| LL | Low Load |
+| LRE | Low Rate Encoding |
+| PCM | Pulse Code Modulation |
+| QB | Quarter Byte |
+| Rx | Receive |
+| STI | Statistic Test Interval |
+| TS | Time Slot |
+
+| | |
+|------|---------------------------------------------------|
+| Tx | Transmit |
+| UCA | Capacity for 64 kbit/s Unrestricted Available |
+| UCNA | Capacity for 64 kbit/s Unrestricted Not Available |
+| USM | User Signalling module |
+| UW | Unique Word |
+| VBD | Voice-Band Data |
+
+# 5 DCME frame structure
+
+## 5.1 General
+
+### 5.1.1 Supported services
+
+The 8 kbit/s DCME frame structure accommodates the following services:
+
+- 8 bit channels to support 64 kbit/s transparent of VBD calls;
+- 1 bit channels to support voice calls at CS-ACELP 8 kbit/s and 6.4 kbit/s according to ITU-T G.729 and its Annex D;
+- 2 bit channels to support SS No. 5 Tone Signals at 16 kbit/s according to ITU-T G.726;
+- 5 bit channels to support VBD calls at 40 kbit/s according to ITU-T G.728 and its Annex J;
+- 4 bit channels to support fax banks (FB) carrying demodulated fax calls in the same manner as in ITU-T G.763 and ITU-T G.766;
+- 4 bit channels to support bit banks (BB) carrying the fifth bits of 40 kbit/s channels for non-demodulated fax calls and voiceband data calls;
+- 8, 5 and 1 bit channels to support 64 kbit/s, 40 kbit/s, 8 kbit/s, and 6.4 kbits pre-assigned channels.
+
+### 5.1.2 PCM frame
+
+As in ITU-T G.763, the bearer structure of the 8 kbit/s DCME retains compatibility with ITU-T G.704, so it contains 24 or 32 consecutively numbered 8 bit time slots, from 1 to 24, for a 1544 kbit/s facility, or from 0 to 31, for a 2048 kbit/s facility.
+
+### 5.1.3 DCME frame and subframe
+
+The low rate encoding algorithm used for speech signals in the 8 kbit/s DCME is CS-ACELP speech encoding algorithm conforming to ITU-T G.729 and its Annex D. The CS-ACELP algorithm has 10 ms of coding frame period, and consequently, the frame period of 8 kbit/s DCME is 10 ms.
+
+### 5.1.4 DCME multiframe
+
+The IT related circuit supervision/alarm condition field of the asynchronous word supports up to 620 ITs, carried over up to 20 primary rate interfaces. The G.768 DCME multiframe of 18 DCME frames is used to accommodate that.
+
+### 5.1.5 Relationship between the frames
+
+A DCME frame is composed of four DCME subframes having a subframe period of 2.5 ms, and each DCME subframe is composed of 20 PCM frames. A DCME multiframe is composed of 18 DCME frames. Figure 1 shows the relationship between DCME multiframe, DCME frame, DCME subframe and PCM frame.
+
+
+
+The diagram illustrates the relationship between associated frames and multiframes in a DCME system. It consists of five horizontal rows of boxes, each representing a different level of the frame hierarchy. The rows are connected by dashed lines that show the grouping of lower-level elements into higher-level elements.
+
+- Top Row:** DCME Multiframe #1, DCME Multiframe #2, [blank], DCME Multiframe #n
+- Second Row:** DCME Frame #0, DCME Frame #1, [blank], DCME Frame #17
+- Third Row:** DCME Subframe #0, DCME Subframe #1, [blank], DCME Subframe #3
+- Fourth Row:** PCM Frame #0, PCM Frame #2, [blank], PCM Frame #19
+- Bottom Row:** TS 0, TS 1, [blank], TS 31
+
+Dashed lines connect the boxes in the following manner:
+
+- From DCME Multiframe #1 to DCME Frame #0 and DCME Frame #1.
+- From DCME Multiframe #2 to DCME Frame #1 and DCME Frame #17.
+- From DCME Frame #0 to DCME Subframe #0 and DCME Subframe #1.
+- From DCME Frame #1 to DCME Subframe #1 and DCME Subframe #3.
+- From DCME Subframe #0 to PCM Frame #0 and PCM Frame #2.
+- From DCME Subframe #1 to PCM Frame #2 and PCM Frame #19.
+- From DCME Subframe #3 to PCM Frame #19.
+- From PCM Frame #0 to TS 0 and TS 1.
+- From PCM Frame #2 to TS 1 and TS 31.
+- From PCM Frame #19 to TS 31.
+
+Diagram showing the hierarchical relationship between DCME Multiframes, DCME Frames, DCME Subframes, PCM Frames, and Time Slots (TS).
+
+T1543430-01
+
+**Figure 1/G.768 – Relationship between associated frames and multiframes**
+
+# 6 Trunk interface structure
+
+## 6.1 Type of trunk interface
+
+Trunk interface shall be either E1 or T1 PRI.
+
+## 6.2 Number of trunk interfaces, trunk channels
+
+Up to 20 E1 or T1 interfaces shall be supported by DCME. The maximum number of ITs shall be 620.
+
+## 6.3 Type of trunk channels
+
+The type of trunk channels shall be 64 kbit/s A-law or $\mu$ -law.
+
+# 7 Bearer interface structure
+
+## 7.1 Cliques, destinations and bearers
+
+### 7.1.1 Number of cliques
+
+The total number of cliques (pools) available over the 2 bearers shall be 4. Each pool starts and ends on TS boundaries (and therefore occupies an integral number of time slots); any single clique shall not be split into different physical interfaces and, consequently, shall not exceed the maximum bearer capacity of 31 time slots.
+
+### 7.1.2 Number of destinations
+
+The maximum number of destinations is 4 including cases of mixed operation between multiclique and multdestination modes.
+
+### 7.1.3 Multiple outgoing bearers
+
+Optionally the equipment can support a maximum of 2 outgoing bearer facilities. A single bearer facility may be able to carry up to 4 cliques, so if a single bearer carries the maximum of 4 cliques, there is no option for a second bearer. The purpose of supporting two outgoing bearer facilities is to utilize the outgoing bearer facilities more efficiently. The DCME is supporting the multdestination operation with up to 4 destinations and consequently four incoming bearer facilities become necessary, whereas one outgoing facility is enough to send out signals resulting in three outgoing bearer facilities which are not in use in typical hardware implementation.
+
+The basic philosophy to support two outgoing bearers is to make more efficient use of hardware resources, with the potential sacrifice of compression gain.
+
+One possibility is to dismiss the necessity of external cross-connect facility at the bearer side. The outgoing bearer channel pools can be assigned to different outgoing facilities.
+
+Another possibility is to make use of more bearer channels to accommodate the traffic including voiceband data signals. Using two outgoing bearer facilities can enable the full use of ITs even in the case where a high compression gain cannot be expected because of the existence of VBD calls.
+
+In this context, using two outgoing bearer facilities does not imply the duplication of DCME capacity. The fundamental design of 8 kbit/s DCME shall be based on the usage of a single outgoing bearer.
+
+## 7.2 Assignment message
+
+Following is the list of assignment messages to be processed in G.768 DCME. The number implies their priorities to be processed at the transmission unit.
+
+- 1) Dummy message.
+- 2) Signalling message via USM.
+- 3) On-demand 64 kbit/s channel disconnection message.
+- 4) Fax-bank disconnection message.
+- 5) Overload BC disconnection message.
+- 6) On-demand 64 kbit/s channel connection message.
+- 7) Fax-bank release message.
+- 8) Data connection message.
+- 9) Speech connection message.
+- 10) Channel check test disconnection message.
+- 11) Refreshment message.
+
+Compared with conventional G.763 DCME and G.767 DCME, a tenth message for channel check test disconnection is added. The reason for adding this new message is to avoid the CCT sequence staying on the same BC in case the channel activity is rather low.
+
+Details of the procedure for generating the channel check test disconnection message is as follows:
+
+When a CCT signal connected to a BC becomes inactive, the connection shall be disconnected. The transmit unit shall execute the disconnection procedure and send out an assignment message being composed of the corresponding BC number and the synchronous data word of "0000". On receiving this message, the receive unit shall disconnect corresponding BC and the special test port. The associated BC encoder and decoder shall become free.
+
+## 7.3 Bearer Channels (BC)
+
+8 kbit/s CS-ACELP encoded voice calls nominally use 1 bit every PCM frame. Therefore the 8 kbit/s DCME bearer channels occupy 1 bit each. These basic Bearer Channels (BCs) shall occupy 80 bits every DCME frame.
+
+## 7.4 Control Channel (CC)
+
+The Basic Control Channel (BCC) of the 8 kbit/s DCME occupies 4 bits every PCM frame, i.e. 2 QBs. BCC holds the synchronization word, four assignment messages (IT and BC numbers and synchronous data word), the asynchronous data word and some error correction bits in every DCME frame. BCC shall be applied to the pool with ITs less than or equal to 240 channels.
+
+If the number of ITs exceeds 240 channels on a specific pool, an Expanded Control Channel (ECC) shall be used for the pool. ECC occupies 6 bits every PCM frame, i.e. 3 QBs, and holds the synchronization word, eight assignment message (IT and BC numbers and synchronous data word), the asynchronous data words and some error correction bits in every DCME frame.
+
+## 7.5 BC numbering and the use of the bearer frame
+
+Each time slot is subdivided into 1 bit slots. The leftmost two or three QBs (four or six 1 bit slots) of each pool carries the control channel (BCC or ECC, respectively). The remaining 1 bit slots of the pool are the Bearer Channels (BCs) and are used to carry traffic.
+
+The normal range BCs are consecutively numbered. When BCC is used, the BC that follows the control channel is BC number one. In the case of ECC, the numbering starts with 3, i.e. BC number 1 and 2 are skipped. In the case of a single pool, the maximum number of normal BCs is 244 for BCC case and 242 for ECC case. The numbering scheme is shown in Figure 2.
+
+
+
+The diagram illustrates the structure of a PCM frame for DCME. The frame is divided into time slots (TS). TS 0 is shown at the beginning. The frame contains multiple pools of channels. Pool 1, starting at TS 1, uses an Expanded Control Channel (ECC) which occupies 3 Quasi-Bits (QBs). This is followed by Bearer Channels (BCs) numbered 3, 4, 5, 6, ..., n-1, n. The last pool, starting at TS 31, uses a Basic Control Channel (BCC) which occupies 2 QBs. This is followed by BCs numbered 1, 2, ..., n-8, n-7, n-6, n-5, n-4, n-3, n-2, n-1, n. A label 'T1543440-01' is present at the bottom right of the diagram.
+
+Diagram illustrating the DCME frame structure. The top part shows 'Pool 1 with ECC' starting at TS 1, containing an ECC (3 QBs) followed by BCs numbered 3, 4, 5, 6, ..., n-1, n. The bottom part shows 'Last Pool with BCC' starting at TS 31, containing a BCC (2 QBs) followed by BCs numbered 1, 2, ..., n-8, n-7, n-6, n-5, n-4, n-3, n-2, n-1, n. A 'TS 0' slot is shown at the beginning of the frame. A label 'T1543440-01' is present at the bottom right.
+
+Figure 2/G.768 – Example of DCME frame structure
+
+### **7.5.1 8 bit (64 kbit/s transparent calls) BCs**
+
+The BC number in the assignment message indicates the BC which carries the first bit of the 8 bit sample (MSB). The rest of the bits are carried by the next seven higher BCs. The same restrictions of G.763 are maintained, so unrestricted 64 kbit/s ITs will occupy one G.704 time slot. 8 kbit/s DCME shall maintain frame integrity of consecutive trunk time slots which are allocated for $N \times 64$ kbit/s calls.
+
+### **7.5.2 5 bit (VBD optimized 40 kbit/s LD-CELP) BCs**
+
+The BC number in the assignment message indicates the BC which carries the first bit (MSB) of the 5 bit sample. The next higher BC carries the next bit (MSB – 1) and so on. The fifth bit (LSB) is obtained from a different 4 bit bearer channel which is independently assigned as a bit bank. Similarly to ITU-T G.763, all 4 bit BCs (data, FB or BB) occupy either the four MSBs or the four LSBs of a G.704 time slot. This implies that the BC number in the assignment message, for such BCs, can be expressed as:
+
+$$4 \times n + 1 \quad (n = 0, 1, 2, 3, \dots)$$
+
+### **7.5.3 4 bit BCs (bit bank, fax bank)**
+
+8 kbit/s DCME fax banks and bit banks are used in the same manner as they are used in ITU-T G.763 and ITU-T G.766. The BC number in the assignment message indicates the BC which carries the first bit of the 4 bit sample. The next higher BC carries the second LSB and so on.
+
+### **7.5.4 2 bit (16 kbit/s ADPCM for SS No. 5 tone) BCs**
+
+The BC number in the assignment message indicates the BC which carries the first bit (MSB) of the 2 bit samples. The 2 bit BC shall occupy QB and the BC number in the assignment message shall be the odd BC number.
+
+### **7.5.5 Normal range 1 bit BCs (CS-ACELP voice)**
+
+The BC number in the assignment message indicates the BC which carries the CS-ACELP encoded IT bits. If high load conditions exist, overload channels will be created.
+
+### **7.5.6 Overload BCs**
+
+The BC number in the assignment message indicates an overload bearer channel which carries the IT bits.
+
+### **7.5.7 Pre-assigned BCs**
+
+8 kbit/s DCME pre-assigned ITs are assigned in the same manner as they are in ITU-T G.763 DCME. 64, 40, 16, 8, and 6.4 kbit/s ITs can be pre-assigned.
+
+# **8 Control channel**
+
+## **8.1 General**
+
+The 8 kbit/s DCME control channel operates with four or eight assignment messages in the 10 ms time-frame. The control channel contains a total of 320 or 480 bits of data in each 10 ms DCME frame, depending on whether four or eight assignment messages (AMs) are used. These bits are transmitted at a rate of 4 or 6 bits every 125 $\mu$ s PCM frame. The control channel, thus, occupies 2 Quarter Bytes (QB) in the case of BCC and 3 QBs in the case of ECC.
+
+Apart from assignment messages, the control channel also conveys the asynchronous data words.
+
+## 8.2 Number of assignment messages
+
+The use of either four messages in a DCME frame period, or eight messages in the DCME frame period, is determined for each clique according to the following rules:
+
+### 8.2.1 BCC/ECC criterion
+
+When the number of ITs belonging to the pool is equal or less than 240, that clique's control channel shall be BCC. When the number of ITs belonging to the pool exceeds 240, that clique's control channel shall be ECC.
+
+### 8.2.2 Total number of assignment messages
+
+The total number of assignment messages per Tx unit is 20.
+
+## 8.3 Control channel content
+
+The contents of the control channel are a synchronization pattern, four or eight assignment messages, an asynchronous data word and error correction code.
+
+### 8.3.1 CC synchronization
+
+The frame synchronization pattern is a unique word of 20 bits, one bit every PCM frame of the DCME frame. The 20 bit unique word also provides a means of identifying the beginning of a 180 ms DCME multiframe (18 DCME frames) for use by the asynchronous data word.
+
+#### 8.3.1.1 Unique word pattern
+
+Four unique words, $UW_0$ , $UW_1$ , $UW_2$ and $UW_3$ , shall be used for DCME synchronization. $UW_0$ , used in the first DCME subframe of the DCME frame will take the following bit sequence except for the first DCME subframe of the DCME multiframe.
+
+$$UW_0 : 0 0 0 1 0 0 0 1 1 1 1 1 0 0 1 0 1 1 0 1$$
+
+In the first DCME subframe of a DCME multiframe (once in 180 ms), the unique word sequence shall be the one which is complementary to normal $UW_0$ mentioned above:
+
+$$\overline{UW_0} : 1 1 1 0 1 1 1 0 0 0 0 0 1 1 0 1 0 0 1 0$$
+
+$UW_1$ , $UW_2$ and $UW_3$ , used in the DCME subframes 1, 2 and 3 respectively, shall take the following bit sequence which is equal to $UW_0$ .
+
+$$UW_1 = UW_2 = UW_3 (= \overline{UW_0}) : 1 1 1 0 1 1 1 0 0 0 0 0 1 1 0 1 0 0 1 0$$
+
+All the information carried by asynchronous data word can maintain the same information interval as they have in G.767 DCME over 620 ITs.
+
+#### 8.3.1.2 Unique word detection
+
+The unique word detection is based on the detection of a correlation match between the accumulated contents of the first bit of the CC and a locally stored unique word pattern on a DCME subframe basis. The resulting correlation matches is used to attain, maintain and regain the synchronization of the CC message.
+
+In the steady state, the erroneous detection threshold of three is used to maintain synchronization, and a 3 bit window centred 20 bits after the previous detection of the correlation match is used to locate the start of the DCME subframe for the proper decoding of the CC message. If the correlation match is not achieved in either DCME subframe of the DCME frame, the CC message bits shall be discarded and a search procedure is initiated over a 20 bit window.
+
+### 8.3.2 Assignment messages
+
+Each assignment message consists of 25 bits that include:
+
+- 10 bits IT identification word;
+- 10 bits BC identification word (1 bit BC type + 9 bits BC number);
+- 5 bits synchronous data word.
+
+#### 8.3.2.1 IT Identification word
+
+The 10 bits of the IT identification word is used to identify the ITs. IT numbering is given in Table 1.
+
+**Table 1/G.768 – IT identification words**
+
+| IT number | IT identification |
+|-----------------|----------------------------------------------------------------------------------------------------------------------------|
+| 0 | Explicit disconnection of BC or used during system start-up and map change. |
+| 1 through 620 | IT used for traffic. |
+| 621 through 624 | Voice order wire to destination number 1 to 4 respectively. |
+| 625 through 628 | CCT to pool 1 to 4 respectively. |
+| 629 through 632 | Local IT number to receive channel check from destination number 1 to 4 respectively. |
+| 637 | BC used as a bit bank. |
+| 638 | BC used as a fax bank. |
+| 1023 | Ineffective CC message when all traffic is pre-assigned. |
+| | – IT field of CC message will be used to carry IT numbers when optional USM is used (see details in CC message structure). |
+
+#### 8.3.2.2 BC identification word
+
+The first (MSB) bit of the 10 bit BC identification word is used to indicate the BC type. For data, this bit will be 1 and for all other BC types it will be 0.
+
+The 9 LSBs in binary code identify the BC number in accordance with the agreed numbering scheme. The normal BC numbering range is 1 through 244. The overload BC numbering range is 256 through 316.
+
+For 4 bit services, the BC number identifies the first 1 bit BC of four consecutive 1 bit BCs, used to create a 4 bit BC and is expressed as follows;
+
+$$4 \times n + 1 \quad (n = 0, 1, 2, 3, \dots)$$
+
+For a 64 kbit/s transparent channel, the BC number identifies the first 1 bit BC of a group of 8 consecutive BCs that occupy exactly one G.704 time slot of the bearer.
+
+BC number 0 in binary code is used for CC messages transmitted during system start-up or during a DCME transmit unit map change.
+
+BC number 1023 in binary code is used to indicate an ineffective CC message if all traffic is pre-assigned.
+
+Table 2 summarizes the BC identification words.
+
+**Table 2/G.768 – BC identification words**
+
+| BC Number | BC identification |
+|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0 | Used during system start-up and map change. |
+| 1 through 244 | Normal BC. |
+| 256 through 316 | Overload BC. |
+| 1023 | Ineffective CC message when all traffic is pre-assigned. |
+| | – BC 1 and 2 will not be used for double AM operation. The normal BC will start from BC3. – BC field of CC message will be used to carry IT numbers when optional USM is used (see details in CC message structure). |
+
+#### **8.3.2.3 Synchronous data word**
+
+The 5 bits synchronous data word supports the following messages:
+
+- Background noise level (16 levels).
+- Indication of 16 kbit/s ADPCM channel assignment.
+- Channel check test procedure.
+- Transparent request.
+- Signalling information when optional USM is used.
+- The ineffective code (transmitted when the IT number indicates a fax bank or a bit bank and when a disconnect message or an ineffective message is sent).
+
+Table 3 shows the synchronous data word encoding. The same criteria shall be applied as that of ITU-T G.767.
+
+**Table 3/G.768 – Synchronous data word encoding**
+
+| Code | Transmit side action: measure noise level | Receive side action: store noise level | Code | Transmit side action: measure noise level | Receive side action: store noise level |
+|-------|----------------------------------------------------------|-------------------------------------------|-------|----------------------------------------------|-------------------------------------------|
+| 00000 | Ineffective | | 10000 | n/u | |
+| 00001 | $\mu$ -law: $n < -72.0$ A-law: not applicable | $\mu$ -law: no noise | 10001 | $-54.0 \leq n < -51.0$ | -52 |
+| 00010 | $\mu$ -law: $-72.0 \leq n < -67.0$ A-law: $n < -67.0$ | $\mu$ -law: -68 A-law: no noise | 10010 | $-51.0 \leq n < -49.0$ | -50 |
+| 00011 | $-67.0 \leq n < -65.5$ | -66.5 | 10011 | $-49.0 \leq n < -47.0$ | -48 |
+| 00100 | $-65.5 \leq n < -64.0$ | -65 | 10100 | $-47.0 \leq n < -45.0$ | -46 |
+| 00101 | $-64.0 \leq n < -61.0$ | -62.5 | 10101 | $-45.0 \leq n < -44.0$ | -44.5 |
+| 00110 | $-61.0 \leq n < -59.0$ | -60 | 10110 | $-44.0 \leq n < -42.8$ | -43 |
+| 00111 | $-59.0 \leq n < -56.0$ | -57.5 | 10111 | $-42.8 \leq n < -42.0$ | -42.5 |
+| 01000 | $-56.0 \leq n < -54.0$ | -55 | 11000 | $-42.0 \leq n$ | -42 |
+| 01001 | n/u | | 11001 | n/u | |
+| 01010 | n/u | | 11010 | n/u | |
+| 01011 | n/u | | 11011 | n/u | |
+
+**Table 3/G.768 – Synchronous data word encoding (concluded)**
+
+| Code | Transmit side action: measure noise level | Receive side action: store noise level | Code | Transmit side action: measure noise level | Receive side action: store noise level |
+|-------|----------------------------------------------|-------------------------------------------|-------|----------------------------------------------|-------------------------------------------|
+| 01100 | n/u | | 11100 | 16 kbit/s ADPCM channel creation | |
+| 01101 | n/u | | 11101 | Transparent | |
+| 01110 | n/u | | 11110 | n/u | |
+| 01111 | n/u | | 11111 | BC is under channel check procedure | |
+
+NOTE 1 – Noise levels in dBm0.
+NOTE 2 – The transmit unit noise measurement should be broadband.
+NOTE 3 – "n/u" means this code is not used – reserved for future use.
+NOTE 4 – It is suggested that because the noise inserted at the receive unit is broadband, the transmit unit noise measurement should also be broadband.
+NOTE 5 – The DCME transmit unit noise intervals are implementation specific, a tolerance of $\pm 2$ dB is suggested.
+NOTE 6 – When the background noise level is high ( $-46$ dBm0 or greater), some Administrations have indicated there may be a subjective benefit in inserting lower values of noise at the receive unit than those measured at the transmit unit. The contrast is most apparent when the noise spectral density at the DCME transmit unit is substantially different from the noise inserted at the receive unit. Since the noise inserted at the receive unit does not affect DCME interoperability, the selection of the noise level is left as an option ( $-50$ dBm0 is being considered).
+
+### 8.3.3 Asynchronous data word
+
+The asynchronous data word consists of 10 bits for each DCME subframe transmitted in a multiframe structure of 18 DCME frames (72 DCME subframes: 180 ms). This results in 720 bits per DCME multiframe for the asynchronous data message. The asynchronous data message holds a net number of 620 bits, including:
+
+- 620 bits IT related circuit supervision/alarm indication.
+- 4 bits DCME bearer backward alarm.
+- 4 bits DLC support message.
+- 5 bits report channel check results.
+- 8 bits report BC related channel check results.
+- 9 bits number of decoder under test.
+
+These bits are transmitted in the asynchronous data word according to Table 4 where bit 0 is transmitted first and bit 9 is transmitted last.
+
+Table 4 shows the encoded messages to be transported by the asynchronous data word.
+
+Table 4/G.768 – Asynchronous data word bit allocation
+
+| DCME Frame No. | DCME Sub frame No. | Bit number (awi) | | | | | | | | | | Remarks |
+|-------------------|-----------------------|------------------|-----|-----|-----|-----|-----|-----|-----|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | |
+| 0 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | Type: IT-related circuit supervision/alarm condition.Designation: The number represents IT number.Content: 0 = normal condition. 1 = alarm condition. (Total 620 ITs). |
+| | 1 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | |
+| | 2 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | |
+| | 3 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | |
+| | . | . | . | . | . | . | . | . | . | . | . | |
+| | . | . | . | . | . | . | . | . | . | . | . | |
+| 14 | 56 | 561 | 562 | 563 | 564 | 565 | 566 | 567 | 568 | 569 | 570 | |
+| | 57 | 571 | 572 | 573 | 574 | 575 | 576 | 577 | 578 | 579 | 580 | |
+| | 58 | 581 | 582 | 583 | 584 | 585 | 586 | 587 | 588 | 589 | 590 | |
+| | 59 | 591 | 592 | 593 | 594 | 595 | 596 | 597 | 598 | 599 | 600 | |
+| 15 | 60 | 601 | 602 | 603 | 604 | 605 | 606 | 607 | 608 | 609 | 610 | |
+| | 61 | 611 | 612 | 613 | 614 | 615 | 616 | 617 | 618 | 619 | 620 | |
+| | 62 | x | x | x | x | x | x | x | x | x | x | |
+| | 63 | x | x | x | x | x | x | x | x | x | x | |
+| 16 | 64 | A1 | A2 | A3 | A4 | x | x | x | x | x | x | Type: DCME bearer backward alarm.Designation: The data word bit number represents Rx bearer number. |
+| | 65 | p | q | r | s | x | x | x | x | x | x | |
+
+Table 4/G.768 – Asynchronous data word bit allocation (concluded)
+
+| DCME Frame No. | DCME Sub frame No. | Bit number (awi) | | | | | | | | | | Remarks |
+|-------------------|-----------------------|------------------|-------------|----|----|----|----|----|----|----|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | |
+| | 66 | b1 | b2 | R | Y | T | x | x | x | x | x | Type: Identification of Rx bearer to which channel check results apply, if channel check is progressing normally.Designation and content: B1, b2: Rx bearer number. R: 1 = channel check disregarded (high BER). 0 = progressing normally. Y: 0 = normal (pass). 1 = alarm (fail). T: Transmit channel check inhibit. 0 = channel check normal. 1 = channel check interrupted. |
+| | 67 | x | BC (MSB) | BC | BC | BC | BC | BC | BC | BC | BC (LSB) | Type: BC related channel check results, transmitted one BC per DCME multiframe. BC: 9 bit code represents the number of the BC for which the results apply. |
+| 17 | 68 | D (MSB) | D | D | D | D | D | D | D | D | D (LSB) | D: 10 bit code represents the number of the decoder for which the results apply. |
+| | 69 | x | x | x | x | x | x | x | x | x | x | |
+| | 70 | x | x | x | x | x | x | x | x | x | x | |
+| | 71 | x | x | x | x | x | x | x | x | x | x | |
+
+NOTE – x means unused, set to zero, reserved for future use.
+
+### 8.3.4 Error correction
+
+#### 8.3.4.1 Bit count
+
+Each assignment message contains 25 bits (10 bit BC, 10 bit IT and 5 bit synchronous data word). The 10 bit asynchronous data word appears once (regardless of the size of CC) in the control channel. A spare of 4 bits is reserved for each DCME subframe. It is therefore required to protect 39 bits in the BCC (25 + 10 + 4) and 64 bits (25 + 25 + 10 + 4) in the ECC.
+
+#### 8.3.4.2 Error correction code
+
+The control channel error correction code to be used is BCH (63,45) which uses the polynomial division remainder of:
+
+$$g(X) = X^{18} + X^{17} + X^{16} + X^{15} + X^9 + X^7 + X^6 + X^3 + X^2 + X^1 + 1$$
+
+This is a triple error correcting code of minimum distance 7. The code is capable of protecting up to 45 bits by adding 18 check bits.
+
+Since the code is capable of protecting 45 bits by adding 18 check bits, and here it is required to protect only 39 data bits in BCC and additional 25 data bits in ECC, it is assumed that the 6 unused most significant bits of data in BCC and 20 unused most significant bits of data in ECC are all zero at both Tx and Rx side, as shown in Figures 3 and 4 respectively.
+
+The information to be protected for BCC is as follows:
+
+| | |
+|------------------------|---------------|
+| Assignment message | 25 bits |
+| Asynchronous data word | 10 bits |
+| Spare bit | 4 bits |
+| | 39 bits |
+
+The information to be protected additionally in ECC case is as follows:
+
+- Additional assignment message 25 bits
+- Each BCH coding sequence shall be applied for each DCME subframe.
+ - FEC sequences shown in Figure 3 shall be repeated 4 times in a DCME frame, corresponding to 4 DCME subframes, in BCC case.
+ - A pair of FEC sequences shown in Figures 3 and 4 shall be repeated 4 times in a DCME frame, corresponding to 4 DCME subframes, in ECC case.
+ - 3 MSBs of check bits for additional message in ECC case will be conveyed in the bit positions next to UW (2nd bit of ECC) in PCM 17, 18 and 19 of each DCME subframe.
+
+
+
+| | | |
+|---------------------------|------------------|---------------|
+| Total number of code bits | | |
+| | Transmitted bits | |
+| 6 unused bits 000000 | 39 data bits | 18 check bits |
+
+T1543450-01
+
+Diagram showing the structure of a BCH (63,45) code block. It is divided into three main sections: '6 unused bits 000000', '39 data bits', and '18 check bits'. Above the '39 data bits' and '18 check bits' sections is a bracket labeled 'Transmitted bits'. Above the entire block is a bracket labeled 'Total number of code bits'. A small code 'T1543450-01' is at the bottom right.
+
+**Figure 3/G.768 – Structure of BCH (63,45) code for first AM channel**
+
+
+
+| | | |
+|----------------------------------------|------------------|---------------|
+| Total number of code bits | | |
+| | Transmitted bits | |
+| 20 unused bits 00000000000000000000 | 25 data bits | 18 check bits |
+
+Diagram showing the structure of a BCH (63,45) code. The total number of code bits (63) is divided into 20 unused bits (00000000000000000000), 25 data bits, and 18 check bits. The transmitted bits (45) consist of the 25 data bits and 18 check bits.
+
+T1543460-01
+
+**Figure 4/G.768 – Structure of BCH (63,45) code for second AM channel in double AM**
+
+## 8.4 CC message transmission scheme
+
+### 8.4.1 Control channel structure
+
+#### 8.4.1.1 Basic Control Channel (BCC) for one subframe
+
+- assignment message: 25 bits
+- asynchronous data word: 10 bits
+- spare: 4 bits
+- error correction: 18 bits
+- dummy: 3 bit
+- synchronization pattern: 20 bits
+- *Total* 80 bits
+
+#### 8.4.1.2 Expanded Control Channel (ECC) for one subframe
+
+- assignment messages: 50 bits ( $25 \times 2$ )
+- asynchronous data word: 10 bits
+- spare: 4 bits
+- error correction: 36 bits ( $18 \times 2$ )
+- synchronization pattern: 20 bits
+- *Total* 120 bits
+
+### 8.4.2 CC bit mapping
+
+Following are the control channel message transmission schemes for BCC and ECC and for USM. The schemes are given in Tables 5 through 10. Each row in the tables lists the bits to be transmitted in one PCM frame within the DCME frame. The left most bit of each row is transmitted first. For each field of the message (BC identification, IT identification, etc.) bit number 0 (e.g. it0, bc0) is the MSB, bit number 1 is MSB – 1 and so on.
+
+**Table 5/G.768 – CC message transmission scheme of a BCC**
+
+| DCME Subframe No. | PCM Frame No. | Control channel bits | | | |
+|----------------------|------------------|----------------------|--------------------|-------|-------|
+| | | UW | Assignment message | | |
+| 0 | PCM frame #0 | UW 0 0 | aw0 | bc1,0 | bc1,1 |
+| | PCM frame #1 | UW 0 1 | aw1 | bc1,2 | bc1,3 |
+| | PCM frame #2 | UW 0 2 | aw2 | bc1,4 | bc1,5 |
+| | PCM frame #3 | UW 0 3 | aw3 | bc1,6 | bc1,7 |
+| | PCM frame #4 | UW 0 4 | aw4 | bc1,8 | bc1,9 |
+| | PCM frame #5 | UW 0 5 | aw5 | it1,0 | it1,1 |
+| | PCM frame #6 | UW 0 6 | aw6 | it1,2 | it1,3 |
+| | PCM frame #7 | UW 0 7 | aw7 | it1,4 | it1,5 |
+| | PCM frame #8 | UW 0 8 | aw8 | it1,6 | it1,7 |
+| | PCM frame #9 | UW 0 9 | aw9 | it1,8 | it1,9 |
+| | PCM frame #10 | UW 0 10 | s0 | sw1,0 | sw1,1 |
+| | PCM frame #11 | UW 0 11 | s1 | sw1,2 | sw1,3 |
+| | PCM frame #12 | UW 0 12 | s2 | sw1,4 | cl,0 |
+| | PCM frame #13 | UW 0 13 | s3 | cl,1 | cl,2 |
+| | PCM frame #14 | UW 0 14 | cl,15 | cl,3 | cl,4 |
+| | PCM frame #15 | UW 0 15 | cl,16 | cl,5 | cl,6 |
+| | PCM frame #16 | UW 0 16 | cl,17 | cl,7 | cl,8 |
+| | PCM frame #17 | UW 0 17 | dummy | cl,9 | cl,10 |
+| | PCM frame #18 | UW 0 18 | dummy | cl,11 | cl,12 |
+| | PCM frame #19 | UW 0 19 | dummy | cl,13 | cl,14 |
+| 1 | (20 PCM frames) | (UW 1 ) | (2nd message) | | |
+| 2 | (20 PCM frames) | (UW 2 ) | (3rd message) | | |
+| 3 | (20 PCM frames) | (UW 3 ) | (4th message) | | |
+
+**Table 6/G.768 – CC message transmission scheme of ECC**
+
+| DCME Subframe No. | PCM Frame No. | Control channel bits | | | | | |
+|-------------------|-----------------|----------------------|--------------------|-------|-------|--------------------|-------|
+| | | UW | Assignment message | | | Assignment message | |
+| 0 | PCM frame #0 | UW 0 0 | aw0 | bc1,0 | bc1,1 | bc2,0 | bc2,1 |
+| | PCM frame #1 | UW 0 1 | aw1 | bc1,2 | bc1,3 | bc2,2 | bc2,3 |
+| | PCM frame #2 | UW 0 2 | aw2 | bc1,4 | bc1,5 | bc2,4 | bc2,5 |
+| | PCM frame #3 | UW 0 3 | aw3 | bc1,6 | bc1,7 | bc2,6 | bc2,7 |
+| | PCM frame #4 | UW 0 4 | aw4 | bc1,8 | bc1,9 | bc2,8 | bc2,9 |
+| | PCM frame #5 | UW 0 5 | aw5 | it1,0 | it1,1 | it2,0 | it2,1 |
+| | PCM frame #6 | UW 0 6 | aw6 | it1,2 | it1,3 | it2,2 | it2,3 |
+| | PCM frame #7 | UW 0 7 | aw7 | it1,4 | it1,5 | it2,4 | it2,5 |
+| | PCM frame #8 | UW 0 8 | aw8 | it1,6 | it1,7 | it2,6 | it2,7 |
+| | PCM frame #9 | UW 0 9 | aw9 | it1,8 | it1,9 | it2,8 | it2,9 |
+| | PCM frame #10 | UW 0 10 | s0 | sw1,0 | sw1,1 | sw2,0 | sw2,1 |
+| | PCM frame #11 | UW 0 11 | s1 | sw1,2 | sw1,3 | sw2,2 | sw2,3 |
+| | PCM frame #12 | UW 0 12 | s2 | sw1,4 | c1,0 | sw2,4 | c2,0 |
+| | PCM frame #13 | UW 0 13 | s3 | c1,1 | c1,2 | c2,1 | c2,2 |
+| | PCM frame #14 | UW 0 14 | C1,15 | c1,3 | c1,4 | c2,3 | c2,4 |
+| | PCM frame #15 | UW 0 15 | C1,16 | c1,5 | c1,6 | c2,5 | c2,6 |
+| | PCM frame #16 | UW 0 16 | C1,17 | c1,7 | c1,8 | c2,7 | c2,8 |
+| | PCM frame #17 | UW 0 17 | C2,15 | c1,9 | c1,10 | c2,9 | c2,10 |
+| | PCM frame #18 | UW 0 18 | C2,16 | c1,11 | c1,12 | c2,11 | c2,12 |
+| | PCM frame #19 | UW 0 19 | C2,17 | c1,13 | c1,14 | c2,13 | c2,14 |
+| 1 | (20 PCM frames) | (UW 1 ) | (3rd message) | | | (4th message) | |
+| 2 | (20 PCM frames) | (UW 2 ) | (5th message) | | | (6th message) | |
+| 3 | (20 PCM frames) | (UW 3 ) | (7th message) | | | (8th message) | |
+
+**Table 7/G.768 – Notes for Tables 5 and 6**
+
+| | |
+|------------------------------|------------------------------------------------------------------------------|
+| UW n (n = 0 to 3) | DCME Unique Words for DCME subframes 0, 1, 2 and 3 respectively (UWi0= MSB). |
+| Itn,0-itn,9 (n = 1 to 8) | T number for messages 1 to 8 respectively (itn0 = MSB). |
+| Bcn,0 (n = 1 to 8) | BC type for messages 1 to 8 respectively. |
+| Bcn,1-bcn,9 (n = 1 to 8) | BC number for messages 1 to 8 respectively (bcn1 = MSB). |
+| swn,0-swn,4 (n = 1 to 8) | Synchronous data word for messages 1 to 8 respectively (swn,0 = MSB). |
+| aw0-aw9 | Asynchronous data word (aw0 = MSB). |
+| s0-s3 | Spare (set to 0 if not used). |
+| Dummy | Dummy bits set to 0. |
+| Cn,0-cn,17 (n = 1 to 8) | Check bits for messages 1 to 8 respectively (cn,0 = MSB). |
+
+**Table 8/G.768 – CC USM message transmission scheme of BCC**
+
+| DCME Subframe No. | PCM Frame No. | Control channel bits | | | |
+|----------------------|------------------|----------------------|-------------------------------------|-------|-------|
+| | | UW | Assignment bits | | |
+| 0 | PCM frame #0 | UW 0 0 | aw0 | it1,0 | it1,1 |
+| | PCM frame #1 | UW 0 1 | aw1 | it1,2 | it1,3 |
+| | PCM frame #2 | UW 0 2 | aw2 | it1,4 | it1,5 |
+| | PCM frame #3 | UW 0 3 | aw3 | it1,6 | it1,7 |
+| | PCM frame #4 | UW 0 4 | aw4 | it1,8 | it1,9 |
+| | PCM frame #5 | UW 0 5 | aw5 | it2,0 | it2,1 |
+| | PCM frame #6 | UW 0 6 | aw6 | it2,2 | it2,3 |
+| | PCM frame #7 | UW 0 7 | aw7 | it2,4 | it2,5 |
+| | PCM frame #8 | UW 0 8 | aw8 | it2,6 | it2,7 |
+| | PCM frame #9 | UW 0 9 | aw9 | it2,8 | it2,9 |
+| | PCM frame #10 | UW 0 10 | s0 | a1 | b1 |
+| | PCM frame #11 | UW 0 11 | s1 | a2 | b2 |
+| | PCM frame #12 | UW 0 12 | s2 | dummy | c1,0 |
+| | PCM frame #13 | UW 0 13 | s3 | c1,1 | c1,2 |
+| | PCM frame #14 | UW 0 14 | c1,15 | c1,3 | c1,4 |
+| | PCM frame #15 | UW 0 15 | c1,16 | c1,5 | c1,6 |
+| | PCM frame #16 | UW 0 16 | c1,17 | c1,7 | c1,8 |
+| | PCM frame #17 | UW 0 17 | dummy | c1,9 | c1,10 |
+| | PCM frame #18 | UW 0 18 | dummy | c1,11 | c1,12 |
+| | PCM frame #19 | UW 0 19 | dummy | c1,13 | c1,14 |
+| 1 | (20 PCM frames) | (UW 1 ) | (2nd message block for IT3 and IT4) | | |
+| 2 | (20 PCM frames) | (UW 2 ) | (3rd message block for IT5 and IT6) | | |
+| 3 | (20 PCM frames) | (UW 3 ) | (4th message block for IT7 and IT8) | | |
+
+**Table 9/G.768 – CC USM message transmission scheme of ECC**
+
+| DCME Subframe No. | PCM Frame No. | Control channel bits | | | | | |
+|-------------------|-----------------|----------------------|---------------------------------------|-------|---------------------------------------|-------|-------|
+| | | UW | Assignment bits | | Assignment bits | | |
+| 0 | PCM frame #0 | UW 0 0 | aw0 | it1,0 | it1,1 | it3,0 | it3,1 |
+| | PCM frame #1 | UW 0 1 | aw1 | it1,2 | it1,3 | it3,2 | it3,3 |
+| | PCM frame #2 | UW 0 2 | aw2 | it1,4 | it1,5 | it3,4 | it3,5 |
+| | PCM frame #3 | UW 0 3 | aw3 | it1,6 | it1,7 | it3,6 | it3,7 |
+| | PCM frame #4 | UW 0 4 | aw4 | it1,8 | it1,9 | it3,8 | it3,9 |
+| | PCM frame #5 | UW 0 5 | aw5 | it2,0 | it2,1 | it4,0 | it4,1 |
+| | PCM frame #6 | UW 0 6 | aw6 | it2,2 | it2,3 | it4,2 | it4,3 |
+| | PCM frame #7 | UW 0 7 | aw7 | it2,4 | it2,5 | it4,4 | it4,5 |
+| | PCM frame #8 | UW 0 8 | aw8 | it2,6 | it2,7 | it4,6 | it4,7 |
+| | PCM frame #9 | UW 0 9 | aw9 | it2,8 | it2,9 | it4,8 | it4,9 |
+| | PCM frame #10 | UW 0 10 | s0 | a1 | b1 | a3 | b3 |
+| | PCM frame #11 | UW 0 11 | s1 | a2 | b2 | a4 | b4 |
+| | PCM frame #12 | UW 0 12 | s2 | dummy | c1,0 | dummy | c2,0 |
+| | PCM frame #13 | UW 0 13 | s3 | c1,1 | c1,2 | c2,1 | c2,2 |
+| | PCM frame #14 | UW 0 14 | c1,15 | c1,3 | c1,4 | c2,3 | c2,4 |
+| | PCM frame #15 | UW 0 15 | c1,16 | c1,5 | c1,6 | c2,5 | c2,6 |
+| | PCM frame #16 | UW 0 16 | c1,17 | c1,7 | c1,8 | c2,7 | c2,8 |
+| | PCM frame #17 | UW 0 17 | c2,15 | c1,9 | c1,10 | c2,9 | c2,10 |
+| | PCM frame #18 | UW 0 18 | c2,16 | c1,11 | c1,12 | c2,11 | c2,12 |
+| | PCM frame #19 | UW 0 19 | c2,17 | c1,13 | c1,14 | c2,13 | c2,14 |
+| 1 | (20 PCM frames) | (UW 1 ) | (2nd message block for IT5 and IT6) | | (2nd message block for IT7 and IT8) | | |
+| 2 | (20 PCM frames) | (UW 2 ) | (2nd message block for IT9 and IT10) | | (2nd message block for IT11 and IT12) | | |
+| 3 | (20 PCM frames) | (UW 3 ) | (2nd message block for IT13 and IT14) | | (2nd message block for IT15 and IT16) | | |
+
+**Table 10/G.768 – Notes for Tables 8 and 9**
+
+| | |
+|------------------------------|-------------------------------------------------------------------------------|
+| UW n (n = 0 to 3) | DCME Unique Words for DCME subframes 0, 1, 2 and 3 respectively (UWi0 = MSB). |
+| Itn,0-itn,9 (n = 1 to 16) | IT number for messages 1 to 8 respectively (itn0 = MSB). |
+| An, bn (n = 1 to 16) | Signalling information associated with itn. |
+| aw0-aw9 | Asynchronous data word (aw0 = MSB). |
+| s0-s3 | Spare (set to 0 if not used). |
+| Dummy | Dummy bits set to 0. |
+| Cn,0-cn,17 (n = 1 to 8) | Check bits for messages 1 to 8 respectively (cn,0 = MSB). |
+
+#### 8.4.2.1 Single IT USM
+
+Optionally, USM will be used to carry signalling information of a single IT and its associated *abcd* bits. In this case, the a2 and b2 fields in Tables 8 and 9 will be used to carry the *c* and *d* bits (respectively) associated with it1, the a3 and b3 fields will carry the *c* and *d* bits of it3, and the it2 and it4 fields will not be used.
+
+# 9 Low bit-rate codecs
+
+## 9.1 Variable bit rate and overload channel creation
+
+### 9.1.1 Principles
+
+The CS-ACELP algorithm produces an 80 bit code word every 80 PCM frames (10 ms) when operating in 8 kbit/s, a 64 bit code word in the same time-frame when operating in 6.4 kbit/s.
+
+The change of rate can be done at the boundary of coding frame (10 ms). The above-mentioned rates are achieved using two basic packaging schemes:
+
+#### 9.1.1.1 Creation of 8 kbit/s channels
+
+To create an 8 kbit/s channel, a 1 bit slot is used to carry one channel.
+
+#### 9.1.1.2 Creation of 6.4 kbit/s channels
+
+For one scheme to create a 6.4 kbit/s channel , four 1 bit slots are used to carry five 6.4 kbit/s-channels. From each 1 bit slot 1 bit is "stolen" every 5 PCM frames therefore leaving 64 bits in each 1 bit slot to carry one normal range 6.4 kbit/s channel. The total amount of "stolen" bits within the algorithmic frame is 64 ( $16 \times 4$ ) bits serving one additional 6.4 kbit/s overload channel.
+
+For another scheme to create a 6.4 kbit/s channel, five 1 bit slots are used to carry five 6.4 kbit/s channels and one 8 kbit/s channel. From each 1 bit slot 1 bit is "stolen" every 5 PCM frames therefore leaving 64 bits in each 1 bit slot to carry one normal range 6.4 kbit/s channel. The total amount of "stolen" bits within the algorithmic frame is 80 ( $16 \times 5$ ) bits serving one additional 8 kbit/s overload channel.
+
+### 9.1.2 Overload channel creation
+
+#### 9.1.2.1 General
+
+The overload channel creation scheme shall basically be the same as that used in ITU-T G.763.
+
+The descriptions in the following subclauses shall supersede corresponding descriptions for overload channel creation and bit bank handling in ITU-T G.763.
+
+The normal BCs range from BC numbers 1 to 244 and the overload BCs can range from BC numbers 256 to 316.
+
+#### 9.1.2.2 Creation of five 6.4 kbit/s channels from four 8 kbit/s channels
+
+Table 11 shows the bearer channel bit-mapping for creating five 6.4 kbit/s channels from four normal range 8 kbit/s channels.
+
+**Table 11/G.768 – Bearer channel bit-mapping for five 6.4 kbit/s channel**
+
+| | | Channel Bit Position | | | |
+|----------------------------------------|------|----------------------|------------|------------|------------|
+| | | M | m+i | m+j | m+k |
+| DCME Frame (10 ms: 125 µs × 80 PCM FR) | FR0 | ch(m)-0 | ch(m+i)-0 | ch(m+j)-0 | ch(m+k)-0 |
+| | FR1 | ch(m)-1 | ch(m+i)-1 | ch(m+j)-1 | ch(m+k)-1 |
+| | FR2 | ch(m)-2 | ch(m+i)-2 | ch(m+j)-2 | ch(m+k)-2 |
+| | FR3 | ch(m)-3 | ch(m+i)-3 | ch(m+j)-3 | ch(m+k)-3 |
+| | FR4 | ovl(n)-0 | ovl(n)-1 | ovl(n)-2 | ovl(n)-3 |
+| | | | | | |
+| | | | | | |
+| | FR75 | ch(m)-60 | ch(m+i)-60 | ch(m+j)-60 | ch(m+k)-60 |
+| | FR76 | ch(m)-61 | ch(m+i)-61 | ch(m+j)-61 | ch(m+k)-61 |
+| | FR77 | ch(m)-62 | ch(m+i)-62 | ch(m+j)-62 | ch(m+k)-62 |
+| | FR78 | ch(m)-63 | ch(m+i)-63 | ch(m+j)-63 | ch(m+k)-63 |
+| | FR79 | ovl(n)-60 | ovl(n)-61 | ovl(n)-62 | ovl(n)-63 |
+
+NOTE – Shaded portions indicate overload channel bits.
+
+#### 9.1.2.3 Creation of five 6.4 kbit/s channels and one 8 kbit/s channels
+
+Table 12 shows the bearer channel bit-mapping for creating five 6.4 kbit/s channels and one 8 kbit/s overload channel from five normal range 8 kbit/s channels.
+
+**Table 12/G.768 – Bearer channel bit-mapping for five 6.4 kbit/s channels and one 8 kbit/s channel**
+
+| | | Channel Bit Position | | | | |
+|----------------------------------------|------|----------------------|------------|------------|------------|------------|
+| | | m | m+i | m+j | m+k | m+l |
+| DCME Frame (10 ms: 125 µs × 80 PCM FR) | FR0 | ch(m)-0 | ch(m+i)-0 | ch(m+j)-0 | ch(m+k)-0 | ch(m+l)-0 |
+| | FR1 | ch(m)-1 | ch(m+i)-1 | ch(m+j)-1 | ch(m+k)-1 | ch(m+l)-1 |
+| | FR2 | ch(m)-2 | ch(m+i)-2 | ch(m+j)-2 | ch(m+k)-2 | ch(m+l)-2 |
+| | FR3 | ch(m)-3 | ch(m+i)-3 | ch(m+j)-3 | ch(m+k)-3 | ch(m+l)-3 |
+| | FR4 | ovl(n)-0 | ovl(n)-1 | ovl(n)-2 | ovl(n)-3 | ovl(n)-4 |
+| | | | | | | |
+| | | | | | | |
+| | FR75 | ch(m)-60 | ch(m+i)-60 | ch(m+j)-60 | ch(m+k)-60 | ch(m+l)-60 |
+| | FR76 | ch(m)-61 | ch(m+i)-61 | ch(m+j)-61 | ch(m+k)-61 | ch(m+l)-61 |
+| | FR77 | ch(m)-62 | ch(m+i)-62 | ch(m+j)-62 | ch(m+k)-62 | ch(m+l)-62 |
+| | FR78 | ch(m)-63 | ch(m+i)-63 | ch(m+j)-63 | ch(m+k)-63 | ch(m+l)-63 |
+| | FR79 | ovl(n)-75 | ovl(n)-76 | ovl(n)-77 | ovl(n)-78 | ovl(n)-79 |
+
+NOTE – Shaded portions indicate overload channel bits.
+
+#### 9.1.2.4 Condition for creating overload channels
+
+The conditions for creating overload channels are as follows:
+
+$$Nov > 0 \quad \text{and} \quad Nv/4 \geq Nov$$
+
+where:
+
+*Nov* (overload list): The number of overload channels (*ov*)
+
+*Nv* (voice list): The number of BCs which are in normal range available for bit-steal
+
+The number of 8 kbit/s channels in the overload range (*No8k *) can be calculated as follows:
+
+$$N_{o8k} = Nov \quad \text{if } \frac{Nv - (Nov \times 4)}{Nov} \geq 1$$
+
+$$N_{o8k} = (Nv - (Nov \times 4)) \text{ modulo } Nov \quad \text{if } \frac{Nv - (Nov \times 4)}{Nov} < 1$$
+
+when *Nov* is greater than 0, the integer variables *Pv* and *Pov* shall be computed as follows:
+
+$$Pv = (IT \text{ modulo } Nv)$$
+
+$$Pov = (IT \text{ modulo } Nov)$$
+
+where:
+
+*IT* is the IT number contained in the assignment message in 2nd subframe of DCME frame.
+
+*Pv* and *Pov* represent voice and overload list positions.
+
+NOTE – Using the assignment message in the first subframe of DCME frame is considered to be inadequate if R1/R2 is used for signalling.
+
+## 9.2 Codec to support SS No. 5 tone signals
+
+To carry SS No. 5 tone signals, 16 kbit/s ADPCM codec conforming to ITU-T G.726 shall be used. For the creation of 16 kbit/s ADPCM channel, the synchronous word of "111100" shall be used in the relevant assignment message.
+
+## 9.3 Frame alignment between the different types of codecs
+
+G.729 CS-ACELP codec, G.728 LD-CELP codec and G.726 ADPCM codec have different coding frame intervals, i.e. 10 ms, 2.5 ms and 125 $\mu$ sec. In 8 kbit/s DCME operation, LD-CELP coding frame boundary and ADPCM coding frame boundary shall be aligned with that of CS-ACELP, composing DCME frame. Any LD-CELP coding frame or ADPCM coding frame shall not be split into two adjacent CS-ACELP frames (i.e. DCME frames).
+
+## 9.4 Processing delay compensation between the different types of codecs
+
+The theoretical processing delay of these three types of codecs are as follows:
+
+| | | |
+|-----------------------|--------------|-----------------------------------------------|
+| – | in encoders: | |
+| 8/6.4 kbit/s CS-ACELP | 15 ms | (5 ms look-ahead delay + 10 ms coding frame). |
+| 40 kbit/s LD-CELP | 0.625 ms | (0.625 ms coding subframe). |
+| 16 kbit/s ADPCM | 125 $\mu$ s | (125 $\mu$ s coding frame). |
+
+Processing delay in decoders will depend on the hardware and/or software design.
+
+When switchover of the codec types should occur, due to the signal classification from voice to data for example, during the active part of input signal, the switchover from 8/6.4 kbit/s CS-ACELP codec to 40 kbit/s LD-CELP should follow. Without absorbing the difference of processing delays, not only the click noise but the duplication (or cut-off) of signal should occur. It should also be noted that such a switchover may occur, although not desired, and not often, in the case where a misclassification of input signal takes place.
+
+It is important to avoid generating such unnecessary noises. To ensure the interoperability between the CME of different manufacturers, the absorption of delay difference shall be independently executed within transmit unit and receive unit. The real implementation of delay difference absorption will depend on the design, and the details are left to the manufacturers.
+
+The equipment design is requested to take notice on the existence of processing delay difference between the different types of speech codecs used in a single equipment, and to absorb the difference of processing delay independently within the transmit unit and receive unit.
+
+## 9.5 Synchronous reset between encoder and corresponding decoder
+
+To obtain better speech quality using low bit-rate codecs, synchronous reset between the encoder and corresponding decoder, to synchronize the internal variables and realize the quicker convergence of the codecs as employed in ITU-T G.763 DCME, shall take place.
+
+The synchronous reset is required for CS-ACELP codecs, LD-CELP codecs and ADPCM codecs. When the codec pair gets the new assignment after the silence period, the synchronous reset shall be performed. The synchronous reset shall also be taken place when the input signal is classified as different as before and gets different type of codec pair to be used.
+
+# 10 Channel check procedure
+
+A means of verifying end-to-end continuity and correct assignment of channels similar to the procedure described in ITU-T G.763 shall be provided.
+
+The use of the control channel for conveying channel check messages as specified in 8.3.3 is the same as specified in ITU-T G.763.
+
+Details of the test procedure are for further study.
+
+# 11 Facsimile demodulation/remodulation
+
+Fax demodulation in the 8 kbit/s DCME shall perform in the same manner as those specified in ITU-T G.767. In each DCME subframe of 2.5 ms, the same procedure as specified in ITU-T G.767 shall be taken.
+
+# 12 System statistics measurement
+
+System statistics measurements in the 8 kbit/s DCME shall basically be performed in the same manner as defined in 15.2.3/G.763 (1998), with the modification that the Statistic Test Interval (STI) is in the range of 10 to 60 minutes (in 5 minute steps).
+
+Additionally, the measurement of a new statistic parameter which directly indicates the dynamic usage of the bearer shall be introduced. The definition of new statistic, bearer occupancy, is as follows:
+
+The new statistic parameter, bearer occupancy, indicates dynamically how many percent of the bearer bits are assigned to active traffics. The definition of the parameter is as follows:
+
+$$\text{Bearer occupancy (\%)} = \frac{\sum_N \frac{N_{nonv} + N_{vact}}{N_{nonv} + (DSI_{pool} - N_{nonv}) \times 1.25}}{N} \times 100$$
+
+where:
+
+| | |
+|---------------------------------------|---------------------------------------------------------------------------------------|
+| $N_{nonv}$ | number of DSI bearer bits used for non-voice traffics. |
+| $N_{vact}$ | number of connected active voice trunks. |
+| $DSI_{pool}$ | size of corresponding DSI pool (in bits, CC not included). |
+| $N$ | number of DCME frames in a single STI. |
+| $N_{nonv} + N_{vact}$ | total of bearer bits assigned for (1) Non-voice traffic and (2) Active voice traffic. |
+| $DSI_{pool} - N_{nonv}$ | number of bearer bits which can be assigned to voice traffic. |
+| $(DSI_{pool} - N_{nonv}) \times 1.25$ | number of maximum voice channels which can be connected. |
+
+# SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure and Internet protocol aspects |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/G/T-REC-G.7712-201908-I_PDF-E/raw.md b/marked/G/T-REC-G.7712-201908-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..ae09bc6f2921cc11198016415802c42ef453e4cd
--- /dev/null
+++ b/marked/G/T-REC-G.7712-201908-I_PDF-E/raw.md
@@ -0,0 +1,3163 @@
+
+
+**ITU-T**
+
+**G.7712/Y.1703**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(08/2019)
+
+SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
+DIGITAL SYSTEMS AND NETWORKS
+
+Data over Transport – Generic aspects – Transport
+network control aspects
+
+SERIES Y: GLOBAL INFORMATION
+INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS,
+NEXT-GENERATION NETWORKS, INTERNET OF
+THINGS AND SMART CITIES
+
+Internet protocol aspects – Operation, administration and
+maintenance
+
+---
+
+**Architecture and specification of data
+communication network**
+
+Recommendation ITU-T G.7712/Y.1703
+
+# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS**
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------|
+| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 |
+| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 |
+| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 |
+| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 |
+| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 |
+| TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS | G.600–G.699 |
+| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 |
+| DIGITAL NETWORKS | G.800–G.899 |
+| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 |
+| MULTIMEDIA QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER-RELATED ASPECTS | G.1000–G.1999 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.6000–G.6999 |
+| DATA OVER TRANSPORT – GENERIC ASPECTS | G.7000–G.7999 |
+| General | G.7000–G.7099 |
+| Transport network control aspects | G.7700–G.7799 |
+| PACKET OVER TRANSPORT ASPECTS | G.8000–G.8999 |
+| ACCESS NETWORKS | G.9000–G.9999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Architecture and specification of data communication network
+
+## Summary
+
+Recommendation ITU-T G.7712/Y.1703 defines the architecture requirements for a data communication network (DCN) which may support distributed management communications related to the telecommunication management network (TMN), distributed control plane communications (e.g., signalling and routing) related to the automatically switched optical network (ASON), distributed control plane communications (e.g., signalling and routing) related to multiprotocol label switching – transport profile (MPLS-TP), control plane communications related to software defined networking (SDN), and other distributed communications (e.g., orderwire or voice communications, software download). The DCN architecture considers networks that are IP-only, open system interface (OSI)-only, and mixed (i.e., support both IP and OSI). The interworking between parts of the DCN supporting IP-only, parts supporting OSI-only, and parts supporting both IP and OSI are also specified – other protocols (other than IP or OSI) are outside the current scope of this Recommendation.
+
+Various applications (e.g., TMN, ASON) require a packet-based communications network to transport information between various components. For example, the TMN requires a communications network, which is referred to as the management communication network (MCN) to transport management messages between TMN components (e.g., network element function (NEF) component and operations system function (OSF) component). ASON and MPLS-TP require communication networks, which are referred to as the signalling communication networks (SCNs) to transport signalling and routing messages between functional control plane components (e.g., connection controller (CC) components and routing controller (RC) components). This Recommendation specifies data communication functions that can be used to support one or more application's communication network.
+
+The data communication functions provided in the 2001 version (version 1) of this Recommendation support connectionless network services. The 2003 revision (version 2) of this Recommendation adds the support of connection-oriented network SCN services by including a specific MPLS-based mechanism.
+
+The 2010 revision (version 4) of this Recommendation provides the requirements for the MPLS transport profile (MPLS-TP) signalling communication channel (SCC) and management communication channel (MCC) data communication functions. The part of this Recommendation that addresses MPLS for transport networks complies with the transport profile of MPLS architecture as defined by Internet Engineering Task Force (IETF). In the event of a difference between this ITU-T Recommendation and any of the normatively referenced request for comments (RFCs) for MPLS-TP, the RFCs will take precedence.
+
+The 2020 version (version 5) provides updates that cover control plane communications related to software defined networking (SDN). A new Appendix V is also added to this version to provide a mapping between clauses here and prior versions due to restructuring.
+
+This Recommendation forms part of a family of Recommendations covering transport networks.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|-----------------------------------|------------|-------------|------------------------------------|
+| 1.0 | ITU-T G.7712/Y.1703 | 2001-11-29 | 15 | 11.1002/1000/5637 |
+| 2.0 | ITU-T G.7712/Y.1703 | 2003-03-16 | 15 | 11.1002/1000/6287 |
+| 3.0 | ITU-T G.7712/Y.1703 | 2008-06-22 | 15 | 11.1002/1000/9390 |
+| 4.0 | ITU-T G.7712/Y.1703 | 2010-09-06 | 15 | 11.1002/1000/10895 |
+| 4.1 | ITU-T G.7712/Y.1703 (2010) Amd. 1 | 2013-10-07 | 15 | 11.1002/1000/12000 |
+| 4.2 | ITU-T G.7712/Y.1703 (2010) Amd. 2 | 2016-02-26 | 15 | 11.1002/1000/12553 |
+| 5.0 | ITU-T G.7712/Y.1703 | 2019-08-29 | 15 | 11.1002/1000/14006 |
+
+## Keywords
+
+Data communication network, Internet protocol (IP), open system interface (OSI).
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2019
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+# Table of Contents
+
+| | | Page |
+|---------|------------------------------------------------------------------|------|
+| 1 | Scope..... | 1 |
+| 2 | References..... | 1 |
+| 3 | Terms and definitions ..... | 4 |
+| 3.1 | Terms defined elsewhere ..... | 4 |
+| 3.2 | Terms defined in this Recommendation ..... | 5 |
+| 4 | Abbreviations and acronyms ..... | 6 |
+| 5 | Conventions ..... | 9 |
+| 6 | DCN applications..... | 10 |
+| 6.1 | TMN application ..... | 12 |
+| 6.2 | ASON application ..... | 19 |
+| 6.3 | SDN application ..... | 27 |
+| 6.4 | Other applications requiring communication networks ..... | 29 |
+| 6.5 | Separation of various applications..... | 30 |
+| 7 | DCN functional architecture..... | 31 |
+| 8 | Data communication function requirements..... | 32 |
+| 8.1 | L1 Physical layer requirements ..... | 32 |
+| 8.2 | L2 Data link layer requirement..... | 32 |
+| 8.3 | L3 Network layer requirements..... | 40 |
+| 8.4 | Other requirements ..... | 46 |
+| 9 | Specific DCN L3 L2 L1 technology requirements ..... | 46 |
+| 9.1 | Ethernet LAN as L1&L2 ..... | 46 |
+| 9.2 | Ethernet WAN as L1&L2..... | 46 |
+| 9.3 | Native MPLS as L3 ..... | 47 |
+| Annex A | – Requirements for three-way handshaking ..... | 50 |
+| A.1 | Point-to-point three-way adjacency TLV ..... | 50 |
+| A.2 | Adjacency three-way state..... | 50 |
+| Annex B | – Requirements for automatic encapsulation..... | 52 |
+| B.1 | Introduction ..... | 52 |
+| B.2 | Scope ..... | 52 |
+| B.3 | Description of the AE-DCF ..... | 52 |
+| B.4 | Requirements and limitations ..... | 54 |
+| Annex C | ..... | 65 |
+| Annex D | – OOB OCh-O and OTSiG-O Protocol specification ..... | 66 |
+| D.1 | Overview ..... | 66 |
+| D.2 | PDU format ..... | 66 |
+| D.3 | OCh_O and OTSiG-O communication channel adaptation function..... | 72 |
+
+| | | |
+|-------------------|------------------------------------------------------------------------------------------------------------------------|----|
+| D.4 | OCh_O [and OTSiG-O] communication channel termination function (OCC_TT) ..... | 72 |
+| Appendix I – | Constraints of the interworking functions in DCN ..... | 73 |
+| I.1 | General assumptions..... | 73 |
+| I.2 | Common to all scenarios ..... | 73 |
+| Appendix II – | Example implementation of automatic encapsulation..... | 76 |
+| II.1 | Introduction ..... | 76 |
+| II.2 | Updates to Dijkstra's algorithm ..... | 77 |
+| Appendix III – | Commissioning guide for SDH NEs in dual [IETF RFC 1195] environment and impact of automatic encapsulation option ..... | 81 |
+| III.1 | Introduction ..... | 81 |
+| III.2 | Integrated IS-IS without automatic encapsulation ..... | 81 |
+| III.3 | Integrated IS-IS with automatic encapsulation..... | 84 |
+| Appendix IV – | Example illustration of packet 1+1 protection..... | 88 |
+| IV.1 | Packet 1+1 protection overview ..... | 88 |
+| IV.2 | Packet 1+1 protection illustration..... | 88 |
+| IV.3 | Operation of selector algorithm under various failure scenarios..... | 90 |
+| Appendix V – | Mapping version 4 and version 5 clause numbers ..... | 95 |
+| Bibliography..... | | 98 |
+
+
+
+# Architecture and specification of data communication network
+
+# 1 Scope
+
+This Recommendation defines the architecture requirements for a data communication network (DCN) which may support distributed management communications related to the telecommunication management network (TMN), distributed control plane communications (e.g., signalling and routing) related to the automatically switched optical network (ASON), distributed control plane communications (e.g., signalling and routing) related to multiprotocol label switching – transport profile (MPLS-TP), control plane communications related to software defined networking (SDN), and other distributed communications (e.g., orderwire or voice communications, software download). The DCN architecture considers networks that are IP-only, open system interface (OSI)-only, and mixed (i.e., support both IP and OSI). The interworking between parts of the DCN supporting IP-only, parts supporting OSI-only, and parts supporting both IP and OSI are also specified – other protocols (other than IP or OSI) are outside the current scope of this Recommendation.
+
+The DCN provides Layer 1 (physical), Layer 2 (data-link) and Layer 3 (network) functionality and consists of routing/switching functionality interconnected via links. These links can be implemented over various interfaces, including wide area network (WAN) interfaces, local area network (LAN) interfaces, and embedded communication channels (ECCs).
+
+Various applications (e.g., TMN, ASON) require a packet-based communication network to transport information between various components. For example, the TMN requires a communication network, which is referred to as the management communication network (MCN) to transport management messages between TMN components (e.g., network element function (NEF) component and operations support function (OSF) component). ASON and MPLS-TP require communication networks, which are referred to as signalling communication networks (SCNs) to transport signalling and routing messages between functional control plane components (e.g., connection controller (CC) components and routing controller (RC) components). This Recommendation specifies data communication functions (DCF) that can be used to support one or more application's communication network.
+
+The DCFs provided in this Recommendation support connectionless network services. Additional functions may be added in future versions of this Recommendation to support connection-oriented network services.
+
+Version 4 of this Recommendation provided the requirements for the MPLS transport profile (MPLS-TP) signalling communication channel (SCC) and management communication channel (MCC) DCFs. The part of this Recommendation that addresses MPLS for transport networks complies with the transport profile of MPLS architecture as defined by Internet Engineering Task Force (IETF). In the event of a difference between this Recommendation and any of the normatively referenced request for comments (RFCs) for MPLS-TP, the RFCs will take precedence.
+
+The 2020 version (version 5) provides updates that cover control plane communications related to software defined networking (SDN). A new Appendix V is also added to this version to provide a mapping between clauses here and prior versions due to restructuring.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision;
+
+users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T G.698.1] Recommendation ITU-T G.698.1 (2009), *Multichannel DWDM applications with single-channel optical interfaces.*
+- [ITU-T G.698.2] Recommendation ITU-T G.698.2 (2009), *Amplified multichannel dense wavelength division multiplexing applications with single channel optical interfaces.*
+- [ITU-T G.707] Recommendation ITU-T G.707/Y.1322 (2007), *Network node interface for the synchronous digital hierarchy (SDH).*
+- [ITU-T G.709] Recommendation ITU-T G.709/Y.1331 (2016), *Interfaces for the Optical Transport Network (OTN).*
+- [ITU-T G.783] Recommendation ITU-T G.783 (2006), *Characteristics of synchronous digital hierarchy (SDH) equipment functional blocks.*
+- [ITU-T G.784] Recommendation ITU-T G.784 (2008), *Management aspects of synchronous digital hierarchy (SDH) transport network elements.*
+- [ITU-T G.798] Recommendation ITU-T G.798 (2012), *Characteristics of optical transport network hierarchy equipment functional blocks.*
+- [ITU-T G.872] Recommendation ITU-T G.872 (2017), *Architecture of optical transport network.*
+- [ITU-T G.874] Recommendation ITU-T G.874 (2017), *Management aspects of optical transport network elements.*
+- [ITU-T G.7702] Recommendation ITU-T G.7702 (2018), *Architecture for SDN control of transport networks.*
+- [ITU-T G.7710] Recommendation ITU-T G.7710/Y.1701 (2012), *Common equipment management function requirements, Amendment 1 (2016).*
+- [ITU-T G.7714] Recommendation ITU-T G.7714 (2005), *Generalized automatic discovery for transport entities.*
+- [ITU-T G.7714.1] Recommendation ITU-T G.7714.1 (2017), *Protocol for automatic discovery in transport networks.*
+- [ITU-T G.8021] Recommendation ITU-T G.8021/Y.1341 (2016), *Characteristics of Ethernet transport network equipment functional blocks.*
+- [ITU-T G.8051] Recommendation ITU-T G.8051/Y.1345 (2015), *Management aspects of the Ethernet-over-Transport (EoT) capable network element.*
+- [ITU-T G.8080] Recommendation ITU-T G.8080/Y.1304 (2012), *Architecture for the automatically switched optical network (ASON), Amendment 1 (2008), Amendment 2 (2010).*
+- [ITU-T G.8081] Recommendation ITU-T G.8081/Y.1353 (2012), *Terms and definitions for Automatically Switched Optical Networks (ASON).*
+- [ITU-T M.3010] Recommendation ITU-T M.3010 (2000), *Principles for a telecommunications management network, Amendment 1 (2003), Amendment 2 (2005).*
+- [ITU-T M.3013] Recommendation ITU-T M.3013 (2000), *Considerations for a telecommunications management network.*
+
+- [ITU-T M.3016.x] Recommendation ITU-T M.3016.x-series (2005), *TMN security overview*.
+- [ITU-T Q.811] Recommendation ITU-T Q.811 (2004), *Lower layer protocol profiles for the Q and X interfaces*.
+- [ITU-T Q.812] Recommendation ITU-T Q.812 (2004), *Upper layer protocol profiles for the Q and X interfaces*.
+- [ITU-T Q.921] Recommendation ITU-T Q.921 (1997), *ISDN user-network interface – Data link layer specification, Amendment 1 (2000)*.
+- [ITU-T X.233] Recommendation ITU-T X.233 (1997) | ISO/IEC 8473-1:1998, *Information technology – Protocol for providing the connectionless-mode network service: Protocol specification*.
+- [ITU-T X.263] Recommendation ITU-T X.263 (1998) | ISO/IEC TR 9577:1999, *Information technology – Protocol identification in the Network Layer*.
+- [ISO 9542] ISO 9542:1988, *Information processing systems – Telecommunications and information exchange between systems – End system to Intermediate system routing exchange protocol for use in conjunction with the Protocol for providing the connectionless-mode network service (ISO 8473)*.
+- [ISO/IEC 10589] ISO/IEC 10589:2002, *Information technology – Telecommunications and information exchange between systems – Intermediate System to Intermediate System intra-domain routing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode network service (ISO 8473)*.
+- [IEEE 802.3] IEEE Std. 802.3-2012, *IEEE Standard for Ethernet*.
+- [IETF RFC 791] IETF RFC 791 (1981), *Internet Protocol DARPA Internet Program Protocol Specification*.
+- [IETF RFC 792] IETF RFC 792 (1981), *Internet Control Message Protocol*.
+- [IETF RFC 826] IETF RFC 826 (1982), *Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware*.
+- [IETF RFC 894] IETF RFC 894 (1984), *A Standard for the Transmission of IP Datagrams over Ethernet Networks*.
+- [IETF RFC 1122] IETF RFC 1122 (1989), *Requirements for Internet Hosts – Communication Layers*.
+- [IETF RFC 1195] IETF RFC 1195 (1990), *Use of OSI IS-IS for Routing in TCP/IP and dual environments*.
+- [IETF RFC 1332] IETF RFC 1332 (1992), *The PPP Internet Protocol Control Protocol (IPCP)*.
+- [IETF RFC 1377] IETF RFC 1377 (1992), *The PPP OSI Network Layer Control Protocol (OSINLCP)*.
+- [IETF RFC 1661] IETF RFC 1661 (1994), *The Point-to-Point Protocol (PPP)*.
+- [IETF RFC 1662] IETF RFC 1662 (1994), *PPP in HDLC-like Framing*.
+- [IETF RFC 1812] IETF RFC 1812 (1995), *Requirements for IP Version 4 Routers*.
+- [IETF RFC 2328] IETF RFC 2328 (1998), *OSPF Version 2*.
+- [IETF RFC 2460] IETF RFC 2460 (1998), *Internet Protocol, Version 6 (IPv6) Specification*.
+- [IETF RFC 2472] IETF RFC 2472 (1998), *IP Version 6 over PPP*.
+
+- [IETF RFC 2740] IETF RFC 2740 (1999), *OSPF for IPv6*.
+- [IETF RFC 2784] IETF RFC 2784 (2000), *Generic Routing Encapsulation (GRE)*.
+- [IETF RFC 2961] IETF RFC 2961 (2001), *RSVP Refresh Overhead Reduction Extensions*.
+- [IETF RFC 3031] IETF RFC 3031 (2001), *Multiprotocol Label Switching Architecture*.
+- [IETF RFC 3032] IETF RFC 3032 (2001), *MPLS Label Stack Encoding*.
+- [IETF RFC 3209] IETF RFC 3209 (2001), *RSVP-TE: Extensions to RSVP for LSP Tunnels*.
+- [IETF RFC 3818] IETF RFC 3818 (2004), *IANA Considerations for the Point-to-Point Protocol (PPP)*.
+- [IETF RFC 4443] IETF RFC 4443 (2006), *Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification*.
+- [IETF RFC 5586] IETF RFC 5586 (2009), *MPLS Generic Associated Channel*.
+- [IETF RFC 5718] IETF RFC 5718 (2010), *An In-Band Data Communication Network For the MPLS Transport Profile*.
+- [IETF RFC 7581] IETF RFC 7581 (2015), *Routing and Wavelength Assignment Information Encoding for Wavelength Switched Optical Networks*.
+
+# 3 Terms and definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+### 3.1.1 Terms defined in [ITU-T G.709]:
+
+- a) optical channel data unit (ODUk)
+- b) optical channel transport unit (OTUk)
+- c) OTM overhead signal (OOS)
+- d) general management communications overhead (COMMS OH)
+- e) optical tributary signal assembly (OTSiA)
+- f) optical tributary signal group (OTSiG)
+- g) optical tributary signal overhead (OTSiG-O)
+
+### 3.1.2 Term defined in [ITU-T G.784]:
+
+- a) data communications channel (DCC)
+
+### 3.1.3 Terms defined in [ITU-T G.8080] and [ITU-T G.8081]:
+
+- a) automatically switched optical network (ASON)
+- b) external network-network interface (E-NNI)
+- c) internal network-network interface (I-NNI)
+- d) user-network interface (UNI)
+- e) call controller (CallC)
+- f) connection controller (CC)
+- g) connection controller interface (CCI)
+- h) subnetwork connection controller (SN-CC)
+
+### 3.1.4 Term defined in [ITU-T G.874]:
+
+- a) general communication channel (GCC)
+
+### 3.1.5 Terms defined in [ITU-T G.7710]:
+
+- a) x.management network
+- b) x.management subnetwork
+
+### 3.1.6 Term defined in [ITU-T G.872]:
+
+- a) optical transport network (OTN)
+
+### 3.1.7 Terms defined in [ITU-T M.3010]:
+
+- a) adaptation device (AD)
+- b) data communications function (DCF)
+- c) mediation device (MD)
+- d) network element (NE)
+- e) network element function (NEF)
+- f) operations system (OS)
+- g) operations system function (OSF)
+- h) Q interface
+- i) transformation function
+- j) workstation function (WSF)
+
+### 3.1.8 Term defined in [ITU-T M.3013]:
+
+- a) message communication function (MCF)
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 automatic encapsulating data communication function (AE-DCF):** An AE-DCF automatically encapsulates packets when necessary so that they may be routed by NEs that would otherwise be unable to forward them. An AE-DCF also features a matching de-encapsulation function to restore the packet back to its original form once it has traversed incompatible NEs.
+
+**3.2.2 control communications network (CCN):** A data communication network (DCN) that is used for control components to communicate with each other is referred to as the control communications network (CCN). The control component could be either SDN control components or ASON control component.
+
+**3.2.3 data communication network (DCN):** The DCN is a network that supports Layer 1 (physical), Layer 2 (data-link), and Layer 3 (network) functionality. A DCN can be designed to support transport of distributed management communications related to the TMN, distributed signalling communications related to the ASON, and other operations communications (e.g., orderwire/voice communications, software downloads).
+
+**3.2.4 embedded communication channel (ECC):** An ECC provides a logical operations channel between NEs that can be utilized by multiple applications (e.g., management applications, control plane applications). The physical channel supporting the ECC is technology specific. Examples of physical channels supporting the ECC are: a DCC channel within SDH, GCC channel within OTN OTUK/ODUK, or the COMMS OH channel within the OTN OOS.
+
+**3.2.5 IP routing interworking function:** An IP routing interworking function allows IP topology or routes to be passed from one IP routing protocol to a different incompatible IP routing protocol. For example, an IP routing interworking function may form a gateway between an integrated IS-IS routed DCN and an OSPF routed DCN.
+
+**3.2.6 management communication channel (MCC):** An MCC provides a dedicated logical operations channel between NEs for management communications. The physical channel supporting the MCC is technology specific.
+
+**3.2.7 network-layer interworking function:** A network-layer interworking function provides interoperability between nodes that support incompatible network-layer protocols. An example of a network-layer interworking function is static GRE tunnels, or an AE-DCF.
+
+**3.2.8 non-MPLS-TP server to MPLS-TP adaptation function (SRV/MT\_A):** The non-MPLS-TP server to MPLS-TP adaptation function is defined as an ITU-T G.805 adaptation function between a non-MPLS server layer network and the MPLS-TP layer network.
+
+**3.2.9 overhead communications channel (OCC):** The overhead communications network (OCN) provides one or more channels for the communication of the overhead. These channels are referred to as the overhead communications channel (OCC).
+
+**3.2.10 overhead communications network (OCN):** A data communication network (DCN) that is used for overhead communication is referred to as the overhead communications network (OCN).
+
+**3.2.11 signalling communication channel (SCC):** An SCC provides a dedicated logical operations channel between NEs for control plane communications. This SCC may not only be used for ASON signalling but may also carry other control plane messages, e.g., routing messages. The physical channel supporting the SCC is technology specific.
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|----------|-----------------------------------------------------|
+| AD | Adaptation Device |
+| AE-DCF | Automatic Encapsulating Data Communication Function |
+| AI | Adapted Information |
+| AP | Access Point |
+| ARP | Address Resolution Protocol |
+| ASON | Automatically Switched Optical Network |
+| ATM | Asynchronous Transfer Mode |
+| BDI | Backward Defect Indication |
+| CallC | Call Controller |
+| CC | Connection Controller |
+| CCI | Connection Controller Interface |
+| CCN | Control Communication Network |
+| CI | Characteristic Information |
+| CLNP | Connectionless Network Layer Protocol |
+| CLNS | Connectionless Network Layer Service |
+| COMMS OH | General Management Communications Overhead |
+| CP | Connection Point |
+| CPI | Control Plane Interface |
+| DCC | Data Communication Channel |
+| DCF | Data Communication Function |
+
+| | |
+|--------|--------------------------------------------|
+| DCN | Data Communication Network |
+| DF | Don't Fragment |
+| ECC | Embedded Communication Channel |
+| EMF | Equipment Management Function |
+| EoT | Ethernet over Transport |
+| ERO | Explicit Route Object |
+| ES | End System |
+| ESH | End System Hello |
+| ES-IS | End System-to-Intermediate System |
+| G-ACh | Generic Associated Channel |
+| GAL | Generic Associated Channel Label |
+| GCC | General Communication Channel |
+| GFP | Generic Framing Procedure |
+| GFP-F | Frame-mapped GFP |
+| GNE | Gateway Network Element |
+| GRE | Generic Routing Encapsulation |
+| HDLC | High-Level Data Link Control |
+| ICMP | Internet Control Message Protocol |
+| ID | Identifier |
+| IIH | IS-IS Hello |
+| IP | Internet Protocol |
+| IPCP | Internet Protocol Control Protocol |
+| IPI | Initial Protocol Identifier |
+| IPv4 | Internet Protocol Version 4 |
+| IPv6 | Internet Protocol Version 6 |
+| IS | Intermediate System |
+| ISDN | Integrated Services Digital Network |
+| ISH | Intermediate System Hello [ISO 9542] |
+| IS-IS | Intermediate System-to-Intermediate System |
+| IWF | Interworking Function |
+| LAN | Local Area Network |
+| LAPD | Link-Access Procedure D-Channel |
+| LCN | Local Communication Network |
+| LER | Label Edge Router |
+| LMP | Link Management Protocol |
+| LSP | Label Switched Path |
+| LS-PDU | Link State Protocol Data Unit |
+
+| | |
+|---------|---------------------------------------------------|
+| LSR | Label Switched Router |
+| MAC | Media Access Control |
+| MCC | Management Communication Channel |
+| MCF | Message Communication Function |
+| MCN | Management Communication Network |
+| MD | Mediation Device |
+| MPLS-TP | Multiprotocol Label Switching – Transport Profile |
+| MTU | Maximum Transmission Unit |
+| NC | Network Connection |
+| NE | Network Element |
+| NEF | Network Element Function |
+| NIM | Non-Intrusive Monitoring |
+| NLPID | Network Layer Protocol Identifier |
+| NNE | Network NE |
+| NNI | Network-to-Network Interface |
+| NSAP | Network Service Access Point |
+| OCC | Overhead Communications Channel |
+| OCh | Optical Channel |
+| OCh-O | Optical Channel Overhead |
+| OCh-P | Optical Channel Payload |
+| OCN | Overhead Communications Network |
+| ODUk | Optical Channel Data Unit |
+| OOB | Out-of-Band |
+| OOS | OTM Overhead Signal |
+| OPS | Optical Physical Section |
+| OS | Operations System |
+| OSC | Optical Supervisory Channel |
+| OSF | Operations System Function |
+| OSI | Open System Interface |
+| OSINLCP | OSI Network Layer Control Protocol |
+| OSPF | Open Shortest Path First |
+| OTM | Optical Transport Module |
+| OTN | Optical Transport Network |
+| OTSi | Optical Tributary Signal |
+| OTSiA | Optical Tributary Signal Assembly |
+| OTSiG | Optical Tributary Signal Group |
+| OTSiG-O | Optical Tributary Signal Group – Overhead |
+
+| | |
+|----------|---------------------------------------------------------------|
+| OTUk | Optical Channel Transport Unit |
+| PDU | Protocol Data Unit |
+| PHOP | Previous HOP |
+| PID | Protocol Identifier |
+| PPP | Point-to-Point Protocol |
+| RC | Routing Controller |
+| RSVP-ORE | Resource Reservation Protocol – Overhead Reduction Extensions |
+| SCC | Signalling Communication Channel |
+| SCN | Signalling Communication Network |
+| SDH | Synchronous Digital Hierarchy |
+| SDN | Software Defined Networking |
+| SID | System Identifier |
+| SN-CC | Subnetwork Connection Controller |
+| S/OMS | SDH/OTN Management Subnetwork |
+| SP | Segmentation Permitted |
+| SPF | Shortest Path First |
+| SRM | Send Routing Message |
+| SSF | Server Signal Fail |
+| TCP | Termination Connection Point |
+| TCP | Transmission Control Protocol |
+| TF | Translation Function |
+| TLV | Type Length Value |
+| TMN | Telecommunication Management Network |
+| TNE | Transport Network Element |
+| TSF | Trail Signal Fail |
+| TT | Trail Termination |
+| UDP | User Datagram Protocol |
+| UNI | User-to-Network Interface |
+| UPI | User Payload Identifier |
+| WAN | Wide Area Network |
+| WS | Work Station |
+| WSF | Work Station Function |
+
+# 5 Conventions
+
+The following conventions are used throughout this Recommendation:
+
+**Mixed DCN:** A mixed DCN supports multiple network layer protocols (e.g., OSI and IPv4). It is possible in a mixed DCN that the path between two communicating entities (e.g., an OS and a managed network element (NE)) will traverse some parts that only support one network layer protocol
+
+(e.g., OSI), and other parts that only support another network layer protocol (e.g., IPv4). To provide communication between such entities, one network layer protocol should be encapsulated into the other network layer protocol at the boundary of those parts supporting different network layer protocols.
+
+**OSI-only DCN:** An OSI-only DCN supports only connectionless network layer protocol (CLNP) as the network layer protocol. Therefore, the end-to-end path between two communicating entities (e.g., an OS and a managed NE) will support CLNP, and encapsulation of one network layer protocol into another network layer protocol is not required to support such communications.
+
+**IPv4-only DCN:** An IPv4-only DCN supports only IPv4 as the network layer protocol. Therefore, the end-to-end path between two communicating entities (e.g., an OS and a managed NE) will support IPv4, and encapsulation of one network layer protocol into another network layer protocol is not required to support such communications.
+
+**IPv6-only DCN:** An IPv6-only DCN supports only IPv6 as the network layer protocol. Therefore, the end-to-end path between two communicating entities (e.g., an OS and a managed NE) will support IPv6, and encapsulation of one network layer protocol into another network layer protocol is not required to support such communications.
+
+# 6 DCN applications
+
+Various applications (e.g., TMN, ASON, MPLS-TP, SDN, overhead communications network (OCN)) require a packet-based communication network to transport information between various components. For example, the TMN requires a communication network, which is referred to as the MCN to transport management messages between TMN components (e.g., network element function (NEF) component and OSF component). ASON and SDN application requires a communication network, which is referred to as the control communication network (CCN) to transport control messages between control components (e.g., CC components, RC components). The control communication network used for ASON signal communication is also referred as signalling communication network (SCN). This Recommendation specifies data communication functions that can be used to support one or more application's communication network.
+
+Figure 6-1 illustrates example applications that can be supported via the DCN. Each application can be supported on separate DCNs or on the same DCN depending on the network design.
+
+
+
+The diagram illustrates the relationship between various network applications and the Data Communication Network (DCN). At the top, five ovals represent different application types: 'Management applications (e.g., TMN)', 'Signalling applications (e.g., ASON)', 'SDN applications', 'OCN applications', and 'Other applications (e.g., software download)'. Lines connect each of these application ovals to a large central oval labeled 'DCN'. Inside the 'DCN' oval, there are five smaller ovals representing the communication functions: 'Management communications', 'Signalling communications', 'Control communications', 'Overhead communications', and 'Other communications'. Each application oval is connected to its corresponding communication function oval within the DCN.
+
+Diagram showing various applications connected to a central DCN. The applications include Management (e.g., TMN), Signalling (e.g., ASON), SDN, OCN, and Other (e.g., software download). These are supported by corresponding communication functions: Management, Signalling, Control, Overhead, and Other communications, all contained within the DCN.
+
+G.7712-Y.1703(19)\_F6-1
+
+**Figure 6-1 – Example applications supported by a DCN**
+
+The conceptual DCN is a collection of resources to support the transfer of information among distributed components. As discussed above, examples of distributed communication that can be supported by the DCN are distributed management communications related to the TMN, distributed control plane communications related to the ASON, and communication related to SDN. In the case of a DCN supporting distributed management communications, the distributed components are TMN components (NEs, adaptation devices (ADs), operations systems (OSs), mediation devices (MDs), and work stations (WSs) containing TMN functions such as OSF, translation function (TF), NEF, work station function (WSF)). [ITU-T M.3010] and [ITU-T M.3013] provide further specifications for the TMN functions. In the case of a DCN supporting distributed signalling communications, the distributed components are ASON components (NEs containing ASON call controller (CallC)/CC functions). [ITU-T G.8080] provides further specifications for the ASON functions. In the case of SDN communications further details are provided in [ITU-T G.7702].
+
+A number of telecommunication technologies can support the DCN functions, such as circuit switching, packet switching, LAN, asynchronous transfer mode (ATM), synchronous digital hierarchy (SDH), optical transport network (OTN), MPLS-TP and Ethernet over transport (EoT). Important aspects of the DCN are the quality of service, information transfer rate, and diversity of routing to support specific operational requirements of the distributed communications supported across the DCN (e.g., distributed management communications, distributed signalling communications).
+
+The goal of an interface specification is to ensure meaningful interchange of data between interconnected devices through a DCN to perform a given function (e.g., TMN function, ASON function, SDN function, OCN function). An interface is designed to ensure independence of the type of device or of the supplier. This requires compatible communication protocols and compatible data representations for the messages, including compatible generic message definitions for TMN management functions, ASON control functions, and SDN control and SDN management functions.
+
+The DCN is responsible for providing compatible communication at the network layer (Layer 3), data-link layer (Layer 2), and physical layer (Layer 1).
+
+Consideration of interfaces should be given to compatibility with the most efficient data transport facilities available to each individual network element (e.g., leased circuits, circuit-switched connections, packet-switched connections, signalling system No. 7, embedded communication channels (ECCs) of the SDH, OTN, MPLS-TP, Ethernet, and integrated services digital network (ISDN) access network D- and B-channels).
+
+This Recommendation specifies the lower three layers for data communication and, therefore, any interworking between protocols within the lower three layers. Such interworking is provided by the DCF. Examples of such interworking are illustrated in Figure 6-2. Note that such interworking does not terminate the Layer 3 protocols. One example is interworking between different physical layers via a common Layer 2 protocol (e.g., bridging media access control (MAC) frames from a LAN interface to an ECC). Another example is interworking between different data-link layer protocols via a common Layer 3 protocol (e.g., routing IP packets from a LAN interface to an ECC). The third example, illustrated in Figure 6-2, shows interworking between different network layer protocols via a Layer 3 tunnelling function (in this example, OSI is encapsulated/tunnelled over IP; however, IP over OSI encapsulation/tunnelling is also possible).
+
+The type of information transported between the distributed components depends on the type of interfaces supported between the components. A DCN supporting distributed management communications related to the TMN needs to support the transport of information associated with the TMN interfaces defined in [ITU-T M.3010]. A DCN supporting distributed control plane communications related to the ASON needs to support the transport of information associated with the ASON interfaces defined in [ITU-T G.8080]. A DCN supporting communications related to SDN needs to support the transport of information associated with the SDN interfaces defined in [ITU-T G.7702].
+
+
+
+Diagram showing three examples of DCN interworking. Each example is a stack of protocol layers. Example 1: Layer 2 (MAC) at the top, with Layer 1 (ECC) and Layer 1 (LAN) below it. Example 2: Layer 3 (IP) at the top, with Layer 2 (PPP) and Layer 2 (MAC) below it, and Layer 1 (ECC) and Layer 1 (LAN) at the bottom. Example 3: Layer 3 (OSI) at the top, with Layer 3 (IP) below it, Layer 2 (LAPD) and Layer 2 (MAC) below that, and Layer 1 (ECC) and Layer 1 (LAN) at the bottom.
+
+G.7712/Y.1703(10)\_F6-2
+
+**Figure 6-2 – Examples of DCN interworking**
+
+## 6.1 TMN application
+
+The TMN requires a communications network, which is referred to as the MCN to transport management messages between TMN components (e.g., NEF component and OSF component). Figure 6-3 illustrates an example relationship of the MCN and the TMN. The interfaces between the various elements (e.g., OS, WS, NE) and the MCN, as illustrated in Figure 6-3, are logical and can be supported over a single physical MCN interface or multiple MCN interfaces.
+
+Figure 6-4 illustrates an example of a physical implementation of an MCN supporting distributed management communications. Depending on the choice of implementation of the MCN, the physical elements may support any combination of ECC interfaces, LAN interfaces, and WAN interfaces. Figure 6-4 also illustrates the types of management plane functional blocks that can be supported in various physical elements. Refer to [ITU-T M.3010] and [ITU-T M.3013] for detailed specifications regarding these management functional blocks. A DCF is part of each physical element and provides data communication functions.
+
+
+
+G.7712/Y.1703(10)\_F6-3
+
+Figure 6-3: Example relationship of TMN interfaces and MCN. The diagram is divided into two main sections: TMN-A on the left and TMN-B on the right, separated by a dashed vertical line. Both sections are symmetrical. At the top of each is an 'Operations system' connected via a 'Q/X/F' interface to a 'Management communication network' (represented as an oval). Below this oval is a 'Q-mediation device' connected via 'Q' interfaces to another 'Management communication network' oval below it. Between the two TMN domains, two 'X-mediation devices' connect the upper and lower 'Management communication network' ovals of TMN-A and TMN-B via 'X' interfaces. On the far left and right, 'Work stations' connect to the network ovals via 'F' interfaces. At the bottom, 'Q adaptor' and 'Network element' blocks connect to the lower network ovals via 'Q' and 'Q/X/F' interfaces respectively. All components are enclosed in dashed boxes representing the TMN domains.
+
+**Figure 6-3 – Example relationship of TMN interfaces and MCN**
+
+
+
+G.7712/Y.1703(10)\_F6-4
+
+Data Communication Function (DCF)
+
+Physical element Function block
+
+Figure 6-4: Example of physical implementation of MCN supporting TMN. This diagram shows physical elements (rectangles) containing function blocks (hatched circles). At the top, two 'OS' (Operations System) elements containing 'OSF' blocks are connected to a central 'WAN' cloud via 'WAN interface' and 'LAN' connections. A 'WS' (Work Station) with a 'WSF' block also connects to this LAN. Below the WAN, an 'MD' (Mediation Device) with a 'TF' block and several 'NE' (Network Element) blocks with 'NEF' blocks are shown. Connections between these include 'ECC' (Embedded Control Channel), 'LAN', and 'q' interfaces. A legend at the bottom defines the rectangle as a 'Physical element' and the hatched circle as a 'Function block'. The text 'Data Communication Function (DCF)' is centered above the legend.
+
+**Figure 6-4 – Example of physical implementation of MCN supporting TMN**
+
+### 6.1.1 X management subnetwork architecture
+
+In Figure 6-5, a number of points should be noted concerning the architecture of a X management subnetwork:
+
+#### – *Multiple NEs at a single site*
+
+Multiple addressable SDH, OTN, or MPLS-TP NEs may appear at a given site. For example, in Figure 6-5, network network element (NNE) and gateway network element (GNE) may be collocated at a single equipment site.
+
+#### – *SDH/OTN/MPLS-TP NEs and their communication functions*
+
+The message communication function (MCF) of an SDH, OTN, or MPLS-TP NE terminates (in the sense of the lower protocol layers) routes, or otherwise processes messages on the ECC or connected via an external interface.
+
+- i) All NEs are required to terminate the ECC. This means that each NE must be able to perform the functions of an OSI end system (ES) or IP host.
+- ii) NEs may also be required to route ECC messages between ports according to routing control information held in the NE. This means that an NE may also be required to perform the functions of an OSI intermediate system or IP router.
+
+#### – *SDH/OTN/MPLS-TP inter-site communications*
+
+The inter-site or inter-office communications link between SDH/OTN/MPLS-TP NEs may be formed from the SDH/OTN/MPLS-TP ECCs.
+
+#### – *SDH/OTN/MPLS-TP intra-site communications*
+
+Within a particular site, SDH/OTN/MPLS-TP NEs may communicate via an intra-site ECC or via a local communication network (LCN). Figure 6-5 illustrates both instances of this interface.
+
+NOTE – A standardized LCN for communicating between collocated network elements has been proposed as an alternative to the use of an ECC. The LCN would potentially be used as a general site communication network serving SDH, OTN, MPLS-TP, and non-SDH/OTN/MPLS-TP NEs (NNEs).
+
+
+
+Telecommunication Management Network (TMN)
+
+G.7712/Y.1703(10)\_F6-5
+
+○ Communication blocks (OS, MD, GNE, NE)
+ ↔ Communication links using standard Q-interface protocol
+ - - - SDH/OTN ECC
+ LCN Local Communication Network
+ GNE Gateway Network Element
+ NNE Network NE
+
+NOTE – The designation "Q" is used in a generic sense.
+
+Diagram of TMN, management network and management subnetwork model. The diagram shows a hierarchy of communication blocks (OS, MD, GNE, NE) connected by Q-interfaces. At the top, OS1 and MD\_A are connected to external systems via F-interfaces. OS1 is connected to MD\_A via a Q-interface. MD\_A is connected to MD\_E via a Q-interface. MD\_E is connected to OS2 via a Q-interface. OS2 is connected to an external system via an F-interface. Below MD\_A are NNE\_A and GNE\_A. NNE\_A is connected to MD\_A via a Q-interface. GNE\_A is connected to MD\_A via a Q-interface. GNE\_A is connected to NE\_B via an ECC link. NE\_B is connected to NNE\_B via an ECC link. NE\_B is also connected to an external system via an F-interface. Below GNE\_A is 'x management subnet-1', which contains NE\_C, NE\_D, and NE\_B. NE\_C is connected to GNE\_A via an ECC link. NE\_D is connected to NE\_C via an ECC link. NE\_B is connected to NE\_C via an ECC link. Below MD\_E are GNE\_E and GNE\_G. GNE\_E is connected to MD\_E via a Q-interface. GNE\_G is connected to MD\_E via a Q-interface. GNE\_E is connected to NE\_F via an ECC link. GNE\_G is connected to NE\_H1 and NE\_H2 via ECC links. NE\_F is connected to NE\_I via an ECC link. NE\_I is connected to NE\_H1 via an LCN Non-ECC link. NE\_H1 is connected to NE\_H2 via an LCN Non-ECC link. Below GNE\_G is 'x management subnet-2', which contains NE\_F, NE\_H1, NE\_H2, and NE\_I. Below OS2 is GNE\_J. GNE\_J is connected to OS2 via a Q-interface. GNE\_J is connected to NE\_K1 and NE\_K2 via ECC links. NE\_K1 is connected to NE\_L via an ECC link. NE\_K1 is also connected to an external system via an F-interface. Below GNE\_J is 'x management subnet-n', which contains NE\_K1, NE\_K2, NE\_L, and NE\_M. NE\_K2 is connected to NE\_M via an ECC link. The diagram also includes a legend for communication blocks, standard Q-interface links, SDH/OTN ECC links, LCN, GNE, and NNE. A note states that 'Q' is used in a generic sense. The diagram is labeled G.7712/Y.1703(10)\_F6-5.
+
+**Figure 6-5 – TMN, management network and management subnetwork model**
+
+#### 6.1.1.1 Topology for management subnetwork
+
+Figure 6-6 illustrates example MCN topologies, such as linear, ring, mesh, and star utilizing ECCs and/or LCN (e.g., [IEEE 802.3] Ethernet LAN) as the physical links interconnecting the network elements. Figure 6-7 illustrates how a management subnetwork could be supported on each topology. Common to each topology are the dual gateways (GNE1 and GNE2 ) which allow reliable access to the NEs within the management subnetwork. Another common aspect to each of the example topologies is that each topology allows multiple diverse paths between any NE within the management subnetwork and the OS.
+
+
+
+The diagram illustrates four example network topologies, each enclosed in a dashed box:
+
+- (Example linear topology):** Nodes NE1 , NEA , NEB , NEC , NED , and NE2 are connected in a linear sequence. An LCN (Logical Connection Network) is shown between NEB and NEC .
+- (Example ring topology):** Nodes NE1 , NEB , NEC , NE2 , NED , NEG , NEF , and NEE are connected in a ring. NE1 is connected to NEA , which is connected to NEE .
+- (Example mesh topology):** Nodes NE1 , NE2 , NEA , NEB , NEC , NED , NEE , NEF , and NEG are fully connected in a mesh. An LCN is shown between NEB and NEC .
+- (Example star topology):** Node NE1 is the central node, connected to NE2 , NEA , NEB , NEC , and NED . NE2 is also connected to NEA , NEB , NEC , and NED .
+
+A legend at the bottom left shows a double-headed arrow labeled ECC.
+
+G.7712/Y.1703(10)\_F6-6
+
+Four diagrams illustrating network topologies: linear, ring, mesh, and star. Each diagram shows nodes (NE1, NE2, NEA, NEB, NEC, NED, NEE, NEF, NEG) connected by double-headed arrows representing ECC links. The linear topology shows a single line of nodes with an LCN connection between NEB and NEC. The ring topology shows a closed loop of nodes. The mesh topology shows a fully connected mesh of nodes with an LCN connection between NEB and NEC. The star topology shows a central node (NE1) connected to multiple other nodes (NE2, NEA, NEB, NEC, NED).
+
+**Figure 6-6 – Example topologies**
+
+
+
+Figure 6-7: Supporting a management subnetwork on various topologies. The diagram shows four examples: linear, ring, mesh, and star topologies. Each example is enclosed in a dashed box labeled 'S/OMS (Example ... topology)'. Each box contains GNE (Gateway Network Element) and NE (Network Element) nodes connected by arrows representing ECC (Element Communication Channel) links. GNE nodes are connected to an external 'to/from OS' (Operating System) via vertical double-headed arrows. In the linear topology, GNE1, NE\_A, NE\_B, NE\_C, NE\_D, and GNE2 are in a line, with an LCN (Local Communication Network) above NE\_B and NE\_C. In the ring topology, GNE1, NE\_B, NE\_C, and GNE2 form a ring, with NE\_A, NE\_E, NE\_F, NE\_G, and NE\_D connected to it. In the mesh topology, all nodes are interconnected. In the star topology, all NE nodes connect to a central GNE1 and GNE2 pair. A legend at the bottom left shows a double-headed arrow labeled 'ECC'. A code 'G.7712/Y.1703(10)\_F6-7' is in the bottom right.
+
+**Figure 6-7 – Supporting a management subnetwork on various topologies**
+
+### 6.1.2 Reliability of MCN
+
+An MCN should be designed to prevent a single fault from making the transfer of critical management messages impossible.
+
+An MCN should be designed to ensure that congestion in the MCN does not cause the blocking or excessive delay of network management messages that are intended to correct a failure or fault.
+
+OSs and NEs that provide an emergency function may require alternate or duplicate access channels to the MCN for redundancy.
+
+### 6.1.3 Security of MCN
+
+See [ITU-T M.3016.x] for MCN security requirements.
+
+### 6.1.4 MCNs
+
+The DCF within the TMN entities shall support the ES (in OSI terms) or host (in IP terms) functionality.
+
+- When the DCF within the TMN entities support ECC interfaces, the following functions are required to be supported:
+ - ECC access function (as specified in clause 8.1);
+ - ECC data-link layer termination function (as specified in clause 8.2);
+
+- "Network layer PDU into ECC data-link layer frame" encapsulation function (as specified in clause 8.3.1);
+- "MPLS PDU into ECC data-link layer" encapsulation function (as specified in clause 9.3.1), if native MPLS is used in the DCN.
+- When the DCF within the TMN entities support Ethernet LAN interfaces, the following functions are required to be supported:
+ - Ethernet LAN physical layer termination function (as specified in clause 9.1);
+ - "Network layer PDU into Ethernet frame" encapsulation function (as specified in clause 8.3.1.5);
+ - "MPLS PDU into Ethernet frame" encapsulation function (as specified in clause 9.3.1.1), if native MPLS is used in the DCN.
+
+The DCF within the TMN entities may operate as an intermediate system (IS) (in OSI terms) or as a router (in IP terms). The DCF within TMN entities that operate as IS/routers must be capable of routing within their Level-1 area and, therefore, must provide the functionality of a Level-1 IS/router. Additionally, the DCF within a TMN entity may be provisioned as a Level-2 IS/router, which provides the capability of routing from one area to another. The functionality of a Level-2 IS/router is not needed in the DCF of all TMN entities. An example of a DCF supporting Level-2 IS/router functionality might be the DCF within a gateway NE.
+
+- When the DCF, within the TMN entities, operates as an IS/router, the following functions are required to be supported:
+ - Network layer protocol data unit (PDU) forwarding function (as specified in clause 8.3.2);
+ - Network layer routing function (as specified in clause 8.3.6).
+
+The DCF within a TMN entity that supports IP may be connected directly to a DCF in a neighbouring TMN entity that supports only OSI.
+
+- When the DCF within a TMN entity that supports IP is connected directly to a DCF in a neighbouring TMN entity that supports only OSI, the following function is required to be supported in the DCF supporting IP:
+ - Network layer PDU interworking function (IWF) (as specified in clause 8.3.3).
+
+The DCF within a TMN entity may have to forward a network layer PDU across a network that does not support the same network layer type.
+
+- When the DCF within a TMN entity must forward a network layer PDU across a network that does not support the same network layer type, the following functions are required to be supported:
+ - Network layer PDU encapsulation function (as specified in clause 8.3.4);
+ - Network layer PDU tunnelling function (as specified in clause 8.3.5).
+
+The DCF within a TMN entity that supports IP using open shortest path first (OSPF) routing may be connected directly to a DCF in a neighbouring TMN entity that supports IP using integrated intermediate system-to-intermediate system (IS-IS).
+
+- When the DCF within a TMN entity that supports IP using OSPF routing is connected directly to a DCF in a neighbouring TMN entity that supports IP using integrated IS-IS, the following function is required to be supported in the DCF supporting OSPF:
+ - IP routing interworking function (as specified in clause 8.3.7).
+
+## 6.2 ASON application
+
+The ASON/MPLS-TP control plane requires a communications network, which is referred to as the signalling communication network (SCN) to transport signalling and routing protocol messages between ASON/MPLS-TP control plane components (e.g., CC components, RC components).
+
+In the following, ASON is used as an example for a control plane application. What is described for the ASON control plane is also applicable to the MPLS-TP control plane.
+
+Figure 6-8 illustrates an example relationship of the SCN and the ASON. The interfaces between the various elements and the SCN, as illustrated in Figure 6-8, are logical and can be supported over a single physical SCN interface, or multiple SCN interfaces.
+
+Figure 6-9 illustrates an example of a physical implementation of a SCN supporting distributed signalling communications. Depending on the choice of implementation of the SCN, the physical elements may support any combination of SCC interfaces, LAN interfaces, and WAN interfaces. Figure 6-9 also illustrates the types of control plane functional blocks that can be supported in various physical elements. Refer to [ITU-T G.8080] for detailed specifications regarding these control functional blocks. A DCF is part of each physical element and provides data communication functionality.
+
+
+
+The diagram shows two ASON domains, A and B, each enclosed in a dashed rectangular box. Inside each domain is an oval labeled 'Signalling communication network'. Below each oval are four rectangular boxes, each labeled 'Network element'. Lines connect each network element to its respective SCN oval. A horizontal line labeled 'UNI/E-NNI' connects the SCN oval in domain A to the SCN oval in domain B. Below the diagram, a legend shows a solid line segment followed by the text 'UNI/ I-NNI/ E-NNI'. In the bottom right corner of the diagram area, the text 'G.7712/Y.1703(10)\_F6-8' is present.
+
+Diagram illustrating the relationship between ASON domains and their Signalling Communication Networks (SCNs).
+
+**Figure 6-8 – Example relationship of ASON interfaces to SCN**
+
+
+
+Diagram of physical implementation of SCN supporting ASON. It shows a WAN at the top connected to several Network Elements (NEs). Each NE contains a Control Plane (CC) and a Data Communication Function (DCF), represented by a circle with a shaded top half. The NEs are interconnected via LANs and ECC (Embedded Control Channel) links. A legend at the bottom identifies a square as a 'Physical element' and a circle with a shaded top half as a 'Function block' (DCF). The diagram is labeled G.7712/Y.1703(10)\_F6-9.
+
+**Figure 6-9 – Example of physical implementation of SCN supporting ASON**
+
+### 6.2.1 Topology of SCN
+
+Figure 6-10 illustrates example topologies, such as linear, ring, mesh, and star utilizing ECCs and/or LCNs (e.g., Ethernet LAN) as the physical links interconnecting the network elements. Figure 6-11 illustrates how an ASON signalling network could be supported on each topology. Common to each topology is that alternate diverse paths exist between the communicating entities (i.e., the ASON capable NEs). Note that to support alternate diverse paths between communicating ASON NEs under a linear topology, an external WAN link could be provided between the edge ASON NEs.
+
+
+
+The diagram illustrates four example network topologies:
+
+- (Example linear topology)**: Nodes are connected in a single line: NE1 ↔ NEA ↔ NEB ↔ NEC ↔ NED ↔ NE2 . An LCN (Logical Connection Network) is shown above NEB and NEC .
+- (Example ring topology)**: Nodes are arranged in a ring: NE1 ↔ NEB ↔ NEC ↔ NE2 ↔ NED ↔ NEG ↔ NEF ↔ NEE ↔ NEA ↔ NE1 .
+- (Example mesh topology)**: Nodes are fully interconnected. NE1 and NE2 are at the top, NEA and NED are below them, and NEE , NEF , and NEG are at the bottom. An LCN is shown above NEB and NEC .
+- (Example star topology)**: Nodes NEA , NEB , NEC , and NED are connected to a central node NE1 . NE2 is also connected to NE1 .
+
+←→ ECC
+
+Four network topology diagrams: linear, ring, mesh, and star. Each diagram shows nodes (NE1, NE2, NEA, NEB, NEC, NED, NEE, NEF, NEG) connected in various configurations. A legend at the bottom left shows a double-headed arrow labeled 'ECC'.
+
+G.7712/Y.1703(10)\_F6-10
+
+**Figure 6-10 – Example topologies**
+
+![Figure 6-11: Supporting an ASON signalling network on various topologies. The diagram shows four examples: linear, ring, mesh, and star topologies. Each example is enclosed in a dashed box and labeled 'ASON signalling network (Example [topology] topology)'. Nodes are labeled ASON NE_1, ASON NE_A, ASON NE_B, ASON NE_C, ASON NE_D, ASON NE_2, ASON NE_E, ASON NE_F, and ASON NE_G. Connections are shown with double-headed arrows. A legend at the bottom left shows a double-headed arrow labeled 'ECC'. A WAN and LCN are shown at the top, connected to ASON NE_1 and ASON NE_2. The mesh topology shows multiple paths between nodes, while the star topology shows all nodes connected to a central node (ASON NE_1).](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg)
+
+WAN
+
+LCN
+
+ASON NE1 ↔ ASON NEA ↔ ASON NEB ↔ ASON NEC ↔ ASON NED ↔ ASON NE2
+
+ASON signalling network (Example linear topology)
+
+ASON NE1 ↔ ASON NEB ↔ ASON NEC ↔ ASON NE2
+
+↑ ↓
+
+ASON NEA ↔ ASON NEE ↔ ASON NEF ↔ ASON NEG ↔ ASON NED
+
+↑ ↓
+
+ASON signalling network (Example ring topology)
+
+ASON NE1 ↔ ASON NEA ↔ ASON NEE ↔ ASON NEF ↔ ASON NEG ↔ ASON NED ↔ ASON NE2
+
+↑ ↓
+
+ASON NEB ↔ ASON NEC
+
+ASON signalling network (Example mesh topology)
+
+ASON NE1 ↔ ASON NE2
+
+↑ ↓
+
+ASON NEA ↔ ASON NEB ↔ ASON NEC ↔ ASON NED
+
+ASON signalling network (Example star topology)
+
+← → ECC
+
+G.7712/Y.1703(10)\_F6-11
+
+Figure 6-11: Supporting an ASON signalling network on various topologies. The diagram shows four examples: linear, ring, mesh, and star topologies. Each example is enclosed in a dashed box and labeled 'ASON signalling network (Example [topology] topology)'. Nodes are labeled ASON NE\_1, ASON NE\_A, ASON NE\_B, ASON NE\_C, ASON NE\_D, ASON NE\_2, ASON NE\_E, ASON NE\_F, and ASON NE\_G. Connections are shown with double-headed arrows. A legend at the bottom left shows a double-headed arrow labeled 'ECC'. A WAN and LCN are shown at the top, connected to ASON NE\_1 and ASON NE\_2. The mesh topology shows multiple paths between nodes, while the star topology shows all nodes connected to a central node (ASON NE\_1).
+
+**Figure 6-11 – Supporting an ASON signalling network on various topologies**
+
+Figure 6-12 illustrates how the ASON signalling network could consist of three different portions: the customer-network portion, the intra-administrative domain portion, and the inter-administrative domain portion. This example shows a mesh topology utilizing ECCs, LCNs (e.g., Ethernet LAN), and leased lines (e.g., DS1/E1, VC-3/4) as the physical links interconnecting the ASON NEs. The topology of the intra-administrative domain portion allows signalling to have alternate diverse paths between two communicating ASON NEs. The topology of the inter-administrative domain portion depends on agreements between administrative domains A and B. This example illustrates dual access points between the administrative domains. The topology of the customer-network portion depends on agreements between the customer and service provider. This example illustrates a single access point between the customer and the network.
+
+
+
+The diagram illustrates the structure of a Signalling Control Network (SCN) across three distinct portions:
+
+
+- Customer-network portion of signalling network:** Contains one ASON NE node connected to the intra-administrative domain via an ECC or LCN link.
+- Intra-administrative domain portion of signalling network:** Part of Administrative domain A, containing four ASON NE nodes interconnected by ECC, LCN, and Leased line links.
+- Inter-administrative domain portion of signalling network:** Connects Administrative domain A to Administrative domain B via a Leased line and an LCN link to another ASON NE node in domain B.
+
+ The bottom of the diagram shows a timeline with markers for 'Customer', 'Administrative domain A', and 'Administrative domain B'. A reference code 'G.7712/Y.1703(10)\_F6-12' is present in the bottom right.
+
+Figure 6-12: Example SCN diagram showing three portions of a signalling network: Customer-network portion, Intra-administrative domain portion, and Inter-administrative domain portion. It illustrates ASON NE nodes and their connections via ECC, LCN, and Leased lines across Administrative domain A and B.
+
+**Figure 6-12 – Example SCN**
+
+### **6.2.2 Reliability of SCN**
+
+Figure 6-13 illustrates ASON control messages being transported over a SCN. It illustrates the following logical interfaces:
+
+- User-to-network interface (UNI);
+- Network-to-network interface (NNI);
+- Connection controller interface (CCI).
+
+
+
+This diagram shows the logical interfaces used for ASON control messages:
+
+
+- UNI (User-to-network interface):** Connects a CallC entity to a CC entity.
+- NNI (Network-to-network interface):** Connects CC entities between different domains or nodes.
+- CCI (Connection controller interface):** Connects a CC entity to a Server entity.
+
+ The sequence of entities from left to right is: Client, Server, Server, Server, Client. Each entity has associated CallC and CC components connected via the specified interfaces. A reference code 'G.7712/Y.1703(10)\_F6-13' is present in the bottom right.
+
+Figure 6-13: ASON interfaces supported on SCN diagram showing CallC, CC, Client, and Server entities connected via UNI, NNI, and CCI interfaces.
+
+**Figure 6-13 – ASON interfaces supported on SCN**
+
+In this example, the messages across the UNI, NNI, and CCI logical interfaces are carried via the SCN network. The SCN may consist of various subnetworks, where logical links in some subnetworks may share common physical routes with the transport network, but such a configuration is neither required nor excluded.
+
+It is possible for the SCN to experience an independent failure from the transport network. Such a scenario is illustrated in Figures 6-14 and 6-15. In this example, which focuses on ASON messages transported over the SCN, an independent failure to the SCN would affect new connection setup and connection tear-down requests.
+
+
+
+Figure 6-14: SCN failure impacting signalling interface. The diagram shows two CallC nodes connected via UNI to CC nodes, which are connected via NNI to Server nodes. The Server nodes are connected via CCI to Client nodes. A failure is indicated by an 'X' on the NNI link between the second and third CC nodes. The text 'G.7712/Y.1703(10)\_F6-14' is in the bottom right corner.
+
+**Figure 6-14 – SCN failure impacting signalling interface**
+
+
+
+Figure 6-15: SCN failure impacting CCI interface. The diagram shows two CallC nodes connected via UNI to CC nodes, which are connected via NNI to Server nodes. The Server nodes are connected via CCI to Client nodes. A failure is indicated by an 'X' on the CCI link between the third Server node and the Client node. The text 'G.7712/Y.1703(10)\_F6-15' is in the bottom right corner.
+
+**Figure 6-15 – SCN failure impacting CCI interface**
+
+As indicated in Figure 6-15, it is also possible for some logical links within the SCN to share common physical routes with the transport network. In this case, it is possible for the SCN to experience a failure that is not independent from the transport network (i.e., failure interrupts both SCN traffic as well as transport traffic), as shown in Figure 6-16. In this example, which focuses on ASON messages transported over the SCN, such a failure may impact restoration when ASON is used to provide restoration of existing connections. It is, therefore, critical for the SCN to provide resiliency when transporting restoration messages.
+
+
+
+Figure 6-16: SCN failure impacting both signalling and data interfaces. The diagram shows two CallC nodes connected via UNI to CC nodes, which are connected via NNI to Server nodes. The Server nodes are connected via CCI to Client nodes. A failure is indicated by an 'X' on the NNI link between the second and third CC nodes, which also affects the CCI link between the third Server node and the Client node. The text 'G.7712/Y.1703(10)\_F6-16' is in the bottom right corner.
+
+**Figure 6-16 – SCN failure impacting both signalling and data interfaces**
+
+If the ASON application is only used to provide connection-setup and teardown, a connectionless SCN may be sufficient. However, if the ASON application is also used to provide restoration, a connection-oriented SCN may be required. A connection-oriented SCN would require specification of additional functions to support connection-oriented network services.
+
+The SCN reliability requirements are as follows:
+
+The SCN shall support various levels of restoration depending on the reliability requirements of the communicating components for which it provides transport (i.e., restoration can be supported between those communicating components requiring highly reliable communications without requiring restoration to be supported among all communicating components).
+
+One way of achieving reliable SCN is through use of packet 1+1 protection for connection-oriented protocols such as MPLS as described in clause 6.2.4.
+
+The SCN may provide transport for restoration messages. In such a case, the SCN should be fast enough to allow proper operation of the connections under control by these restoration messages control.
+
+### 6.2.3 Security of SCN
+
+A SCN supporting ASON messages may provide connectivity between different administrative domains. When a SCN provides connectivity between administrative boundaries, precautions must be taken such that only those messages that are allowed to pass between the two administrative domains are able to cross the interface, while other messages which are not allowed to pass between administrative domains are prevented from crossing the interface. The SCN needs to ensure that only a selected set of messages, which are allowed by the administrative parties on either side of the interface, are actually able to pass across the interface.
+
+[b-IETF RFC 5920] describes the security threats relevant in the context of MPLS and generalized MPLS (GMPLS) (also relevant in the context of MPLS-TP) and the defensive techniques to combat those threats.
+
+### 6.2.4 SCN data communication functions
+
+The DCF within the ASON entities shall support the ES (in OSI terms) or host (in IP terms) functionality.
+
+- When the DCF within the ASON entities support ECC interfaces, the following functions are required to be supported:
+ - ECC access function (as specified in clause 8.1);
+ - ECC data-link layer termination function (as specified in clause 8.2);
+ - "Network layer PDU into ECC data-link layer frame" encapsulation function (as specified in clause 8.3.1).
+- When the DCF within the ASON entities support Ethernet LAN interfaces, the following functions are required to be supported:
+ - Ethernet LAN physical layer termination function (as specified in clause 9.1);
+ - "Network layer PDU into Ethernet frame" encapsulation function (as specified in clause 8.3.1.5).
+
+The DCF within the ASON entities may operate as an intermediate system (IS) (in OSI terms), or as a router (in IP terms). The routing protocol used for DCF determines how to forward SCN messages to their destination. The DCF within ASON entities that operate as IS/routers must be capable of routing within their Level-1 area and, therefore, must provide the functionality of a Level-1 IS/router. Additionally, the DCF within an ASON entity may be provisioned as a Level-2 IS/router, which provides the capability of routing from one area to another. The functionality of a Level-2 IS/router is not needed in the DCF of all ASON entities.
+
+- When the DCF within the ASON entities operate as an IS/router, the following functions are required to be supported:
+ - Network layer PDU forwarding function (as specified in clause 8.3.2);
+ - Network layer routing function (as specified in clause 8.3.6).
+
+The DCF within an ASON entity that supports IP may be connected directly to a DCF in a neighbouring ASON entity that supports only OSI.
+
+- When the DCF within an ASON entity that supports IP is connected directly to a DCF in a neighbouring TMN entity that supports only OSI, the following function is required to be supported in the DCF supporting IP:
+ - Network layer PDU interworking function (as specified in clause 8.3.3).
+
+The DCF within an ASON entity may have to forward a network layer PDU across a network that does not support the same network layer type.
+
+- When the DCF within an ASON entity must forward a network layer PDU across a network that does not support the same network layer type, the following functions are required to be supported:
+ - Network layer PDU encapsulation function (as specified in clause 8.3.4);
+ - Network layer PDU tunnelling function (as specified in clause 8.3.5).
+
+The DCF within an ASON entity that supports IP using OSPF routing may be connected directly to a DCF in a neighbouring ASON entity that supports IP using integrated IS-IS.
+
+- When the DCF within an ASON entity that supports IP using OSPF routing is connected directly to a DCF in a neighbouring ASON entity that supports IP using integrated IS-IS, the following function is required to be supported in the DCF supporting OSPF:
+ - IP routing interworking function (as specified in clause 8.3.7).
+
+The DCF within the ASON entities may operate as a label edge router (LER).
+
+When the DCF within the ASON entities operates as an LER, the following functions are required to be supported:
+
+- If the DCF supports ECC interfaces, the "MPLS PDU into ECC data-link layer" encapsulation function (as specified in clause 9.3.1).
+- If the DCF supports LAN interfaces, the "MPLS PDU into Ethernet frame" encapsulation function (as specified in clause 9.3.1.1).
+- MPLS label switched path (LSP) signalling function (as specified in clause 9.3.2).
+- MPLS LSP forwarding function (as specified in clause 9.3.3).
+- MPLS LSP path computation function (as specified in clause 9.3.4).
+- "Network layer PDU into MPLS" encapsulation function (as specified in clause 9.3.5).
+
+The DCF within the ASON entities may operate as a label switched router (LSR).
+
+When the DCF within the ASON entities operate as an LSR, the following functions are required to be supported:
+
+- If the DCF supports ECC interfaces, the "MPLS PDU into ECC data-link layer" encapsulation function (as specified in clause 9.3.1).
+- If the DCF supports LAN interfaces, the "MPLS PDU into Ethernet frame" encapsulation function (as specified in clause 9.3.1.1).
+- MPLS LSP signalling function (as specified in clause 9.3.2).
+- MPLS LSP forwarding function (as specified in clause 9.3.3).
+
+The DCF within the ASON entities may provide packet 1+1 protection capability.
+
+The minimum requirements to provide packet 1+1 protection service are as follows:
+
+- There is no additional capability required on the interior nodes of the network;
+- The network should support the establishment of diversely routed connections.
+- *Ingress node*
+ - Must be able to associate the two connections that are used to provide packet level 1+1 protection between two end nodes;
+ - Must support the carrying of an identifier in the packet which will be used to identify duplicate copies of a packet at the egress node;
+ - Must be able to dual-feed each packet on these two mated connections.
+
+- *Egress node*
+ - Must be able to associate the two connections that are used to provide packet level 1+1 protection between two end nodes;
+ - Must be able to identify the duplicate copies of a dual-fed packet using the identifier;
+ - Must be able to select and forward one, and only one, copy of a packet.
+
+The mechanism to associate the two diverse connections as well as the format and location of the sequence identifier shall be as described in clause 9.3.6.
+
+## 6.3 SDN application
+
+SDN controllers require a communication network, which is referred to as the control communications network (CCN) to transport SDN control messages between SDN components (e.g., SDN controller to the NEs, SDN controller to SDN controller, SDN controller to SDN applications).
+
+Figure 6-17 illustrates an example relationship of the CCN and the SDN. The interfaces between the various elements, as illustrated in Figure 6-17, are logical and can be supported over a single physical CCN interface, or multiple CCN interfaces.
+
+Figure 6-18 illustrates an example of a physical implementation of a CCN supporting control communications for SDN network. Depending on the choice of implementation of the CCN, the physical elements may support any combination of CCN interfaces, LAN interfaces, and WAN interfaces. Figure 6-18 also illustrates the types of control functional blocks that can be supported in various physical elements. Refer to [ITU-T G.7702] for detailed specifications regarding these control functional blocks. A DCF is part of each physical element and provides data communication functionality.
+
+
+
+The diagram illustrates two SDN networks, SDN network A and SDN network B, connected via their Control communication networks (CCN). Each network contains SDN controllers, SDN applications, and Network elements connected to the CCN via CPI interfaces. The CCNs are represented by ovals, and the interfaces are labeled 'CPI'. The two CCNs are connected by a horizontal line.
+
+```
+
+graph LR
+ subgraph SDN_network_A [SDN network A]
+ CCN_A((Control communication network))
+ SC_A[SDN controllers] -- CPI --> CCN_A
+ SA_A[SDN applications] -- CPI --> CCN_A
+ NE_A1[Network element] -- CPI --> CCN_A
+ NE_A2[Network element] -- CPI --> CCN_A
+ NE_A3[Network element] -- CPI --> CCN_A
+ end
+ subgraph SDN_network_B [SDN network B]
+ CCN_B((Control communication network))
+ SC_B[SDN controllers] -- CPI --> CCN_B
+ SA_B[SDN applications] -- CPI --> CCN_B
+ NE_B1[Network element] -- CPI --> CCN_B
+ NE_B2[Network element] -- CPI --> CCN_B
+ NE_B3[Network element] -- CPI --> CCN_B
+ end
+ CCN_A --- CCN_B
+
+```
+
+Diagram showing two SDN networks, A and B, connected via their Control communication networks (CCN). Each network contains SDN controllers, SDN applications, and Network elements connected to the CCN via CPI interfaces.
+
+G.7712/Y.1703(19)\_F6-17
+
+**Figure 6-17 – Example relationship of SDN interfaces to CCN**
+
+
+
+Diagram illustrating the physical implementation of CCN supporting SDN. At the top, three boxes labeled 'SDN controllers' and one box labeled 'SDN applications' are connected to a central oval labeled 'WAN'. Below the WAN, a box labeled 'LAN' is connected to a 'WAN interface'. The 'LAN' box contains two 'NEF' (Function block) units, each inside an 'NE' (Physical network element) box, connected by an 'ECC' line. The 'WAN interface' box contains three 'NEF' units, each inside an 'NE' box, connected by 'ECC' lines. A legend at the bottom shows a square for 'Physical network element' and a circle with a shaded top half for 'Function block (DCF)'. The text 'G.7712/Y.1703(19)\_F6-18' is in the bottom right.
+
+**Figure 6-18 – Example of physical implementation of CCN supporting SDN**
+
+### 6.3.1 Supported SDN interfaces
+
+SDN controllers can be arranged in multi-levels hierarchy. Each SDN controller instance can be implemented as a centralized SDN controller instance or can be implemented in a distributed way by a federation of functional SDN controller components. The CCN for SDN network need to support both intra-SDN controller communications, i.e., communication between components as defined in [ITU-T G.7702], and also inter-SDN controller communication, i.e., the communication between the high-level controller and low-level controllers. The interworking of components in different levels of SDN controllers are also depicted in [ITU-T G.7702]. Communication between SDN applications and SDN controllers also need to be supported by the CCN.
+
+### 6.3.2 Topology of SDN communications
+
+An SDN controller communicates with others at its adjacent level in the hierarchical arrangement of SDN controllers, SDN controllers may communicate with another SDN controller at an adjacent level, or communicate with SDN applications when there is an SDN application on top of it. The SDN controller has no sense whether it is another SDN controller or SDN application communicating with it. An SDN controller could communicate directly with physical NEs when it has the scope of the resource as transport name space (i.e., the FP name space); this can occur at any level of a hierarchy as any level may have access to a resource view with FP name spaces.
+
+### 6.3.3 Reliability of SDN communications
+
+The control messages crossing the CCN network are critical for operations of the network. It is possible for the CCN to experience failure which could be independent from the transport network or coupled with failure of the transport network. Ways of achieving reliable CCN could be through use of packet 1+1 protection for connection-oriented protocols such as MPLS as described in clause 6.2.4 or any other redundancy technology.
+
+### 6.3.4 Security of SDN communications
+
+A CCN supporting SDN control messages communication may provide connectivity 1) between SDN control components, and 2) between SDN applications and SDN control components. The SDN applications may reside on a customer's network domain and SDN controllers reside on an operator's network domain. The SDN controllers may control the resources of different layer networks which
+
+may be in different MCC domains. When a CCN provides connectivity that crosses the boundary between different MCC domains, precautions must be taken such that only those messages that are allowed to pass between the two MCC domains are permitted to cross the boundary.
+
+[b-ONF TR-530] "Threat analysis for SDN architecture" describes the threats to SDN controllers, SDN NE and SDN applications. [b-ONF TR-529] "Security Foundation Requirements for SDN Controllers" describes defensive techniques to combat these threats.
+
+## 6.4 Other applications requiring communication networks
+
+Besides TMN, ASON and SDN applications, other applications such as overhead communication (e.g., optical channel (OCh) or optical tributary signal group (OTSiG) non-associated overhead), voice communications (e.g., orderwire), software downloads and operator specific communications require a communication network to provide transport of information between components.
+
+A DCN that is used for overhead communication is referred to as the OCN. The OCN provides one or more channels for the communication of the overhead. These channels are referred to as the overhead communications channel (OCC). Described below is an application of the OCN for OCh and OTSiG non-associated layer overhead communication.
+
+### 6.4.1 OTSiG|OCh non-associated overhead communication application
+
+The OTSiG|OCh network uses non-associated overhead (OTSiG|optical channel overhead (OCh-O)), which is normally transported in the OTM-n.m via the optical transport module (OTM) overhead signal (OOS) carried in the optical supervisory channel (OSC). For the case where an OTSiG|OCh signal is transported in a single channel intra-domain interface as described in [ITU-T G.698.1] and [ITU-T G.698.2], the OSC may not be available. To transport this across the interface between the media|OCh subnetwork and the OTSiG|OCh source/sink, an OCC within the overhead communications network (OCN) is used as shown in Figure 6-19. The OTSiG|OCh-O messages must be carried in a PDU that is encapsulated into the OCN packet/frame format for the technology used in the OCN. The OTSiG|OCh-O PDU must contain sufficient information so that the source, sink and intermediate points can verify the connectivity.
+
+In this application, the OCN provides point-to-point connectivity between two OTSiG|OCh-O connection points (OTSiG|OCh-O CP) to transport the OTSiG|OCh-O associated with the OTSiG and OCh payload (OCh-P). See Figure 6-19 (from Figure 12-1 of [ITU-T G.872]). The OCN should be able to support one or more of these point-to-point connections simultaneously.
+
+An OCN should be designed to ensure that a single fault does not prevent the transfer of the OTSiG|OCh-O messages. The OCN should be designed to ensure that the messages are delivered correctly and does not impose blocking or excessive delay.
+
+The protocol used for OTSiG|OCh-O communication is defined in Annex D.
+
+
+
+Diagram of OTSiG overhead transport for single channel IaDI. It shows two OTSiG-O units (Source and Sink) connected via a Network media channel. The Source unit is connected to an OTSi Mod, which is connected to a Media subnetwork. The Sink unit is connected to an OTSi Demod, which is connected to an OTSi-A subnetwork. The Network media channel contains a series of OTSiG-O units, some of which are carried by OSC. The Media subnetworks contain Media channels. Reference points Ss and Rs are indicated on the left and right respectively. The diagram is labeled G.7712-Y.1703(19)\_F6-19.
+
+NOTE 1 – From Figure 12-1 of [ITU-T G.872]
+
+NOTE 2 – $S_s$ and $R_s$ in this figure identify the reference points defined in [ITU-T G.698.1] and [ITU-T G.698.2].
+
+**Figure 6-19 – OTSiG overhead transport for the case of single channel IaDI**
+
+## 6.5 Separation of various applications
+
+Depending on the network design, network size, link capacity, security requirements and performance requirements, various levels of separation between the multiple applications (e.g., TMN, ASON, SDN) are possible. The level of separation that is provided is a choice that is made among operators and vendors when designing the network. The following are examples of various levels of separation.
+
+Option A: The DCN can be designed such that the MCN, SCN, and other applications (e.g., operator-specific communications) are supported on the same Layer 3 network (e.g., share the same IP network).
+
+Option B: The DCN can be designed such that the MCN, SCN, and other applications (e.g., operator-specific communications) are supported on separate Layer 3 networks; however, they may share some of the same physical links.
+
+Option C: The DCN can be designed such that the MCN, SCN, and other applications (e.g., operator-specific communications) are supported on separate physical networks (i.e., separate Layer 3 networks that do not share any of the same physical links).
+
+# 7 DCN functional architecture
+
+The DCN architecture requirements in this clause apply to IP-only domains, OSI-only domains, and mixed IP+OSI domains. The DCN architecture requirements are technology independent. Technology-specific Recommendations such as [ITU-T G.784] for SDH and [ITU-T G.874] for OTN will specify which requirements are applicable for that particular technology.
+
+The DCN is aware of Layer 1, Layer 2, and Layer 3 protocols and is transparent to upper-layer protocols used by the applications for which it transports.
+
+A DCN may be designed such that only IP is supported. A DCN supporting only IP may consist of various subnetworks using different physical and data link layer protocols; however, all subnetworks will support IP as the network layer protocol.
+
+However, since embedded DCN networks support OSI, some DCNs may consist of parts that support IP-only, parts that support OSI-only, and parts that support both IP and OSI.
+
+Those parts of the DCN supporting IP (i.e., either those parts supporting only IP or those parts supporting IP and OSI) may consist of DCFs that support IP-only (i.e., a single stack IP-only DCFs) and/or DCFs supporting IP and OSI (e.g., a dual-stack DCF which is capable of routing both IP and OSI packets). Those parts of the DCN supporting only OSI would consist of DCFs that support OSI-only (i.e., a single stack OSI-only DCF).
+
+Figure 7-1 illustrates the functional architecture of the DCN. As discussed above, the DCN may be composed of parts that only support IP, parts that only support OSI, and parts that support both IP and OSI. An IWF between those parts of the DCN supporting IP-only, OSI-only, and IP and OSI, and mapping functions which map applications to the IP layer are also specified. To provide such transport, the DCN supports Layer 1 (physical), Layer 2 (data-link), and Layer 3 (network) functionality. The architecture requirements for those parts of the DCN supporting IP only, OSI only as well as the requirements for interworking between those parts of the DCN supporting IP-only, OSI-only, and IP and OSI are specified. The cloud in Figure 7-1, representing the IP-only part of the DCN, is an abstract view of the DCN and therefore may also apply to a single IP NE interconnected to OSI NEs via an IWF.
+
+
+
+The diagram illustrates the functional architecture of a DCN. It features two main DCN components connected by an Interworking Function (IWF). The left DCN component is labeled 'IP-only layer 1, 2, 3 functionality' and is connected to four 'Applications' (each represented by an 'OS' circle and an 'm' mapping circle) above it and three subnetworks (SN-CC, EMF, SN-CC) below it via 'm' mapping circles. The right DCN component is labeled 'OSI-only layer 1, 2, 3 functionality' and is connected to four 'Applications' (each represented by an 'OS' circle and an 'm' mapping circle) above it and three subnetworks (EMF, EMF, SN-CC) below it via 'm' mapping circles. The IWF is a rectangular box positioned between the two DCN components. A legend at the bottom left defines the abbreviations: EMF (Equipment Management Function), IWF (Interworking Function), m (Mapping between application and DCN), OS (Operations System), and SN-CC (Subnetwork Connection Controller). The diagram is labeled 'G.7712-Y.1703(10)\_F7-1' in the bottom right corner.
+
+EMF Equipment Management Function.
+IWF Interworking Function.
+m Mapping between application and DCN.
+OS Operations System.
+SN-CC Subnetwork Connection Controller.
+
+G.7712-Y.1703(10)\_F7-1
+
+Functional architecture of DCN diagram
+
+**Figure 7-1 – Functional architecture of DCN**
+
+# 8 Data communication function requirements
+
+This clause provides specifications for various data communication functions related to ECC interfaces, [IEEE 802.3] Ethernet LAN interfaces, and network layer capabilities.
+
+## 8.1 L1 Physical layer requirements
+
+An ECC access function provides access to the ECC bit stream. This function is defined in technology-specific equipment Recommendations (e.g., [ITU-T G.783] (SDH), [ITU-T G.798] (OTH), and [ITU-T G.8021] (Ethernet transport)). The bit rates and definitions of the various ECCs (e.g., data communication channel (DCC), general communication channel (GCC), and general management communications overhead (COMMS OH) in OSC) are provided in the technology-specific Recommendations (e.g., [ITU-T G.784], [ITU-T G.874], and [ITU-T G.8051]).
+
+## 8.2 L2 Data link layer requirement
+
+An ECC data-link layer termination function provides the common data-link layer processing regardless of the network layer PDU encapsulated within the data-link layer frame. The mapping of the data-link layer frame into the ECC is also provided by this function. This function is specified in the technology-specific Recommendations. However, the specification for the SDH ECC data-link layer termination function, the OTN ECC data-link layer termination function, and the MPLS-TP SCC data-link layer termination function is provided below.
+
+### 8.2.1 SDH ECC (DCC)
+
+#### 8.2.1.1 Mapping the data-link layer frame into the SDH ECC
+
+The high-level data link control (HDLC) framed signal is a serial bit stream containing stuffed frames surrounded by one or more flag sequences. The HDLC framed signal format is defined in [ITU-T Q.921] for link-access procedure D-channel (LAPD), and [IETF RFC 1662] for point-to-point protocol (PPP) in HDLC framing. A HDLC frame consists of N octets as presented in Figure 8-1. The HDLC frame is transmitted right to left and top to bottom. A 0 bit is inserted after all sequences of five consecutive 1 bits within the HDLC frame content (octets 2 to N-1) ensuring that a flag or abort sequence is not simulated within a frame.
+
+The mapping of the HDLC framed signal into the DCC channel is bit-synchronous (rather than octet-synchronous) since the stuffed HDLC frame does not necessarily contain an integer number of octets as a consequence of the 0-insertion process. Therefore, there is no direct mapping of a stuffed HDLC frame into bytes within a DCC channel. The HDLC signal generator derives its timing from the ServerLayer/DCC\_A function (i.e., the DCC\_CI\_CK signal) for SDH. The following ServerLayer/DCC\_A functions are defined in [ITU-T G.783]: MSn/DCC\_A function, MS256/DCC\_A function, and RSn/DCC\_A function.
+
+The HDLC framed signal is a serial bit stream and will be inserted into the DCC channel such that the bits will be transmitted on the STM-N in the same order that they were received from the HDLC frame signal generator.
+
+
+
+The diagram shows the structure of an HDLC frame. At the top, there are column headers labeled 8, 7, 6, 5, 4, 3, 2, 1, and Octet. Below this, the first octet is shown with bits 0, 1, 1, 1, 1, 1, 1, 0, and it is labeled 'Flag' and '1'. Subsequent octets are labeled 2, 3, ..., N-2, N-1, and N. Arrows indicate the flow of data from the first flag to the last flag. The last octet (N) is also shown with bits 0, 1, 1, 1, 1, 1, 1, 0, labeled 'Flag' and 'N'. At the bottom, the text 'G.7712-Y.1703(19)\_F8-1' is present.
+
+Figure 8-1: HDLC frame format diagram. It shows a sequence of octets (1 to N) with a Flag at the beginning and end. The Flag is represented by the bit sequence 01111110. The diagram illustrates the framing of data between two flags.
+
+**Figure 8-1 – HDLC frame format**
+
+#### 8.2.1.2 SDH ECC data-link layer protocol specification
+
+The three types of interfaces identified are: IP-only interfaces, OSI-only interfaces, and dual interfaces (dual interfaces are interfaces that can carry both IP and OSI packets). When carrying only IP over the DCC, PPP in HDLC framing shall be used as the data-link layer protocol. Since dual interfaces can carry both IP and OSI, it is possible for a dual interface to be connected to either an IP-only interface, an OSI-only interface, or another dual interface. OSI-only interfaces exist in networks today, and the data-link protocol used on such interfaces is LAPD as defined in [ITU-T G.784]. To allow dual interfaces to connect to either an IP-only interface or an OSI-only interface, the data-link layer protocol supported on a dual interface must be configurable to support either PPP in HDLC or LAPD. An exception is allowed for embedded SDH NEs supporting LAPD in hardware that are upgraded to support dual interfaces. To limit the amount of hardware upgrades, it is allowed for upgraded SDH NEs to support only LAPD.
+
+##### 8.2.1.2.1 IP-only interface
+
+IP-only interfaces are illustrated in Figure 8-2.
+
+
+
+The diagram shows a box labeled 'IP-only interface' connected to a horizontal line. To the right of the line, the protocols 'IP', 'PPP', and 'DCC' are listed vertically. At the bottom, the text 'G.7712-Y.1703(19)\_F8-2' is present.
+
+Figure 8-2: IP-only interface diagram. It shows a box labeled 'IP-only interface' connected to a line. The line is labeled with 'IP', 'PPP', and 'DCC' stacked vertically. At the bottom, the text 'G.7712-Y.1703(19)\_F8-2' is present.
+
+**Figure 8-2 – IP-only interface**
+
+IP-only interfaces shall use PPP as per [IETF RFC 1661] and [IETF RFC 1332].
+
+##### 8.2.1.2.2 OSI-only interface
+
+OSI-only interfaces are illustrated in Figure 8-3.
+
+
+
+Diagram of an OSI-only interface. A box labeled 'OSI-only interface' is connected to a horizontal line. To the right of the line, the protocols 'OSI', 'LAPD', and 'DCC' are listed vertically. Below the diagram is the reference 'G.7712-Y.1703(19)\_F8-3'.
+
+**Figure 8-3 – OSI-only interface**
+
+OSI-only interfaces shall use LAPD as per [ITU-T G.784].
+
+##### 8.2.1.2.3 Dual interface (IP+OSI)
+
+Dual interfaces (dual interfaces are interfaces that can carry OSI and IP packets) can be connected to IP-only interfaces, OSI-only interfaces, or other dual interfaces. To allow dual interfaces to be connected to other IP-only interfaces or other OSI-only interfaces, the data-link protocol on the dual interface must be configurable to switch between PPP in HDLC framing (as per [IETF RFC 1662]) and LAPD (as per [ITU-T G.784]) as illustrated in Figure 8-4. Note that embedded SDH NEs supporting LAPD in hardware that are upgraded to support IP are not required to support PPP in HDLC framing on its dual interfaces. Therefore, its dual interfaces are only required to support LAPD.
+
+
+
+Diagram of a dual interface. Two boxes labeled 'IP + OSI interface' are shown. Each box is connected to a horizontal line. Above each box is an arrow pointing to it from the text 'Dual-stack interface'. To the right of each horizontal line, the protocols 'IP + OSI', 'PPP' or 'LAPD', and 'DCC' are listed vertically. Below the diagram is the reference 'G.7712-Y.1703(19)\_F8-4'.
+
+**Figure 8-4 – Dual interface**
+
+Dual interfaces supporting PPP shall use PPP as per [IETF RFC 1661], [IETF RFC 1332], and [IETF RFC 1377].
+
+Dual interfaces supporting LAPD shall use LAPD as per [ITU-T G.784].
+
+### 8.2.2 OTN ECC (GCC)
+
+#### 8.2.2.1 Mapping the data-link layer frame into the OTN GCC (OTN COMMS channel)
+
+The HDLC framed signal is a serial bit stream containing stuffed frames surrounded by one or more flag sequences. The HDLC framed signal format is defined in [IETF RFC 1662] for PPP in HDLC framing. A HDLC frame consists of N octets as presented in Figure 8-1. The HDLC frame is transmitted right to left and top to bottom. A 0 bit is inserted after all sequences of five consecutive 1 bits within the HDLC frame content (octets 2 to N-1) ensuring that a flag or abort sequence is not simulated within a frame.
+
+The mapping of the HDLC framed signal into the GCC channel (GCC0, GCC1, and GCC2) is bit-synchronous (rather than octet-synchronous) since the stuffed HDLC frame does not necessarily contain an integer number of octets as a consequence of the 0-insertion process. Therefore, there is no direct mapping of a stuffed HDLC frame into bytes within a GCC (COMMS) channel. The HDLC signal generator derives its timing from the ServerLayer/COMMS\_A function (i.e., the COMMS\_CI\_CK signal) for OTN. The following ServerLayer/COMMS\_A functions are defined in [ITU-T G.798]:
+
+- OTUK[V]/COMMS\_A (GCC0);
+- ODUkP/COMMS\_A or optical channel data unit (ODUk)/COMMS\_AC (GCC1 and GCC2).
+
+[ITU-T G.709] also defines the COMMS OH as the general ECC for OTM-N interfaces (OTN OOS). The specific physical frame structure and coding for the COMMS OH is outside the scope of [ITU-T G.709]. Therefore, the corresponding adaptation functions are for further study.
+
+The HDLC framed signal is a serial bit stream and will be inserted into the GCC channel such that the bits will be transmitted on the OTM-N interface in the same order that they were received from the HDLC framed signal generator as depicted in Figure 8-1.
+
+#### 8.2.2.2 OTN ECC data-link layer protocol specification
+
+The three types of interfaces identified are: IP-only interfaces, OSI-only interfaces, and dual interfaces (dual interfaces are interfaces that can carry both IP and OSI packets). When carrying only IP over the GCC, PPP in HDLC framing shall be used as the data-link layer protocol. Since dual interfaces can carry both IP and OSI, it is possible for a dual interface to be connected to either an IP-only interface, an OSI-only interface, or another dual interface.
+
+##### 8.2.2.2.1 IP-only interface
+
+IP-only interfaces are illustrated in Figure 8-5.
+
+
+
+G.7712-Y.1703(19)\_F8-5
+
+Diagram of an IP-only interface showing a box labeled 'IP-only interface' connected to a horizontal line. To the right of the line, the protocols 'IP', 'PPP', and 'GCC' are listed vertically. Below the diagram is the text 'G.7712-Y.1703(19)\_F8-5'.
+
+**Figure 8-5 – IP-only interface**
+
+IP-only interfaces shall use PPP as per [IETF RFC 1661] and [IETF RFC 1332].
+
+##### 8.2.2.2.2 OSI-only interface
+
+OSI-only interfaces are illustrated in Figure 8-6.
+
+
+
+G.7712-Y.1703(19)\_F8-6
+
+Diagram of an OSI-only interface showing a box labeled 'OSI-only interface' connected to a horizontal line. To the right of the line, the protocols 'OSI', 'PPP', and 'GCC' are listed vertically. Below the diagram is the text 'G.7712-Y.1703(19)\_F8-6'.
+
+**Figure 8-6 – OSI-only interface**
+
+OSI-only interfaces shall use PPP as per [IETF RFC 1661] and [IETF RFC 1377].
+
+##### 8.2.2.2.3 Dual interface (IP+OSI)
+
+Dual interfaces (dual interfaces are interfaces that can carry OSI and IP packets) can be connected to IP-only interfaces, OSI-only interfaces, or other dual interfaces.
+
+
+
+G.7712-Y.1703(19)\_F8-7
+
+Diagram of a dual interface showing a box labeled 'IP + OSI interface' connected to a horizontal line. Above the box is the label 'Dual-stack interface' with an arrow pointing to it. To the right of the line, the protocols 'IP + OSI', 'PPP', and 'GCC' are listed vertically. Below the diagram is the text 'G.7712-Y.1703(19)\_F8-7'.
+
+**Figure 8-7 – Dual interface**
+
+Dual interfaces shall use PPP as per [IETF RFC 1661], [IETF RFC 1332], and [IETF RFC 1377].
+
+### 8.2.3 MPLS-TP ECC
+
+For MPLS-TP, the following options define how the control plane (signalling) communication can be carried with respect to the associated user traffic:
+
+- In-band (see clause 8.2.3.1),
+- Out-of-band (OOB), in-fibre (see clauses 8.2.3.1.1, 8.2.3.1.2, 8.2.3.1.5.1 and 8.2.3.1.5.2);
+- Out-of-fibre, aligned topology;
+- Out-of-fibre, independent topology (see clause 8.2.3.1.4).
+
+The DCN architecture, as described in this Recommendation, supports all the options listed above.
+
+The following possibilities are defined for constructing the signalling communication network (SCN):
+
+- SCN link sharing a server layer trail with MPLS-TP user traffic;
+- SCN link utilizing the MPLS-TP SCC as per [IETF RFC 5718];
+- SCN link utilizing a dedicated MPLS-TP LSP;
+- Separate and independent SCN link.
+
+#### 8.2.3.1 MPLS-TP SCN
+
+##### 8.2.3.1.1 SCN link sharing server layer trail with MPLS-TP user traffic
+
+A SCN link sharing a server layer trail with MPLS-TP user traffic is an out-of-band, in-fibre configuration where the server layer trail provides both the SCN link as well as the MPLS-TP link. In this case, the SCN link and MPLS-TP link share the bandwidth provided by the common server layer trail as illustrated in Figure 8-8. Due to the bandwidth sharing, a traffic shaping and conditioning function may be needed to prevent the SCC from exceeding its committed bandwidth in congestion situations.
+
+
+
+The diagram shows two Network Elements, NE-A and NE-B, connected by a shared server trail. Each NE contains an IPv4 SCN, an MPLS-TP, and a Server (SRV) layer. The SCN and MPLS-TP are connected to the SRV layer via an SCC (Service Communication Channel) and IPv4 FwP (Forwarding Plane). The SRV layers are connected to each other via a common server trail. The diagram is labeled G.7712-Y.1703(19)\_F8-8.
+
+Diagram illustrating two Network Elements (NE-A and NE-B) interconnected by a shared server trail. Each NE contains an IPv4 SCN, an MPLS-TP, and a Server (SRV) layer. The SCN and MPLS-TP are connected to the SRV layer via an SCC (Service Communication Channel) and IPv4 FwP (Forwarding Plane). The SRV layers are connected to each other via a common server trail.
+
+**Figure 8-8 – Example of MPLS-TP NEs interconnected by a shared server trail providing an SCN link**
+
+As shown in Figure 8-8, the native SCN packets (e.g., IPv4/IPv6 or OSI CLNP packets) are directly encapsulated into the server layer. The server adaptation function recognizes SCN packets as non-MPLS frames and encapsulates them by using the related payload type identifier (e.g., by using the related user payload identifier (UPI) when generic framing procedure (GFP) encapsulation is used, or by using the related Ethertype when Ethernet encapsulation is used).
+
+It is noted that the server layer payload type identifier may also be used for other data flows across the server layer trail and that the SCN packets may not be distinguishable from these other flows based on the server layer payload type identifier. In such cases, a deeper packet inspection may be needed (e.g., based on the destination address of the packet) to distinguish the SCN packets from the packets belonging to the other flows.
+
+##### 8.2.3.1.2 SCN MPLS-TP SCC as per [IETF RFC 5718]
+
+A SCN link utilizing the MPLS-TP SCC as per [IETF RFC 5718] is an out-of-band, in-fibre configuration which is illustrated in Figure 8-9. In this case, the SCN link is provided by the MPLS-TP trail termination function and shares the bandwidth with the MPLS-TP user traffic (MPLS-TP LSPs) in a similar way as for the previous scenario. Due to the bandwidth sharing, a traffic shaping and conditioning function may be needed to prevent the SCC from exceeding its committed bandwidth in congestion situations.
+
+
+
+The diagram illustrates the architecture of two network elements, NE-A and NE-B, interconnected by a common server layer trail. Each element contains the following components and connections:
+
+- NE-A (Left):**
+ - An **IPv4 SCN** node at the top is connected to an **SCC IPv4 FWP** node.
+ - The **SCC IPv4 FWP** node is connected to an **MT/MT** node.
+ - An **MPLS-TP** node is also connected to the **MT/MT** node.
+ - The **MT/MT** node is connected to an **SRV/MT** node.
+- NE-B (Right):**
+ - An **IPv4 SCN** node at the top is connected to an **SCC IPv4 FWP** node.
+ - The **SCC IPv4 FWP** node is connected to an **MT/MT** node.
+ - An **MPLS-TP** node is also connected to the **MT/MT** node.
+ - The **MT/MT** node is connected to an **SRV/MT** node.
+- Interconnection:** The **SRV/MT** nodes of NE-A and NE-B are connected to each other, forming the common server layer trail.
+
+G.7712-Y.1703(19)\_F8-9
+
+Diagram of two network elements, NE-A and NE-B, connected by a common server layer trail. Each element contains an IPv4 SCN node, an SCC IPv4 FWP node, an MPLS-TP node, an MT/MT node, and an SRV/MT node. The SCN and FWP nodes are connected to the MT/MT node, which is in turn connected to the SRV/MT node. The SRV/MT nodes of NE-A and NE-B are connected to each other, forming the common server layer trail.
+
+**Figure 8-9 – MPLS-TP NEs interconnected by a MPLS-TP trail providing an SCN link**
+
+##### 8.2.3.1.3 SCN link utilizing a dedicated MPLS-TP LSP
+
+A SCN link utilizing a dedicated MPLS-TP LSP is an out-of-band, in-fibre configuration which is illustrated in Figure 8-10. The SCN link is created by establishing this dedicated MPLS-TP LSP. This dedicated MPLS-TP LSP can be multiplexed with the MPLS-TP LSPs carrying user traffic (MPLS-TP user traffic) which are transported over a common server layer trail.
+
+In this case, the native SCN packets (e.g., IPv4/IPv6 or OSI CLNP packets) are encapsulated into a dedicated MPLS-TP trail as defined in [IETF RFC 3032]. This dedicated MPLS-TP trail must not be used for other traffic.
+
+
+
+Diagram of MPLS-TP NEs interconnected by a dedicated MPLS-TP trail providing an SCN link. The diagram shows two network elements, NE-A and NE-B, connected by a red line representing a dedicated MPLS-TP trail. NE-A contains an IPv4 SCN connected to an IPv4 CI, which is connected to an MT/MT block. The MT/MT block is connected to an SRV/MT block, which is connected to an SRV block. The SRV block is connected to the dedicated MPLS-TP trail. NE-B contains an IPv4 SCN connected to an IPv4 CI, which is connected to an MT/MT block. The MT/MT block is connected to an SRV/MT block, which is connected to an SRV block. The SRV block is connected to the dedicated MPLS-TP trail. The diagram is labeled G.7712-Y.1703(19)\_F8-10.
+
+**Figure 8-10 – MPLS-TP NEs interconnected by a dedicated MPLS-TP trail providing an SCN link**
+
+##### 8.2.3.1.4 Separate and independent SCN links
+
+Separate and thus independent SCN links can also be used for MPLS-TP. These are SCN links that do not share link resources carrying MPLS-TP traffic, and are thus independent of the MPLS-TP layer network topology.
+
+The details of independent SCN links for MPLS-TP are outside the scope of this Recommendation.
+
+##### 8.2.3.1.5 MPLS-TP SCC data-link layer termination function
+
+A more detailed description of the shared SCN link option, as defined in clause 8.2.3.1.1, is provided below.
+
+###### 8.2.3.1.5.1 Non-MPLS-TP server layer trail providing an SCN link (SCN link sharing a server layer trail with MPLS-TP user traffic)
+
+Figure 8-11 shows a model of the SRV/MT\_A adaptation function that includes the SCC and MCC forwarding points (FwP) in addition to the MPLS-TP connection points. The diamonds in the figure represent the traffic shaping and conditioning functions that may be needed to prevent the SCC and MCC forwarding points from exceeding their committed bandwidth in congestion situations.
+
+Examples of non-MPLS-TP server layers providing an SCN link are:
+
+- Ethernet PHY;
+- GFP over SDH using virtual concatenation (VCAT);
+- GFP over the OTN (ODUk).
+
+
+
+Diagram of MPLS-TP to server layer adaptation function. At the top, 'SCC' and 'MCC' are grouped, each with 'IP Fwp' and 'OSI Fwp' forwarding points. Below them, 'User traffic MPLS-TP LSPs' and 'MT\_CI' are shown. All these elements connect to a yellow trapezoidal block labeled 'SRV/MT\_A'. Below this block is 'SRV\_AI', which connects to a yellow triangular block labeled 'SRV'.
+
+G.7712-Y.1703(19)\_F8-11
+
+**Figure 8-11 – MPLS-TP to server layer adaptation function providing SCC and MCC forwarding points**
+
+The SCC directly utilizes the IP and OSI forwarding points provided by the server layer.
+
+The layer-2 code points (L2CPs, e.g., the Ethertype field in case of an Ethernet PHY or the UPI field in case of frame-mapped GFP (GFP-F)) are used to distinguish the SCC from the other flows such as the user traffic (MPLS-TP LSPs) and the MCC, unless the SCC and the MCC are sharing the same layer-2 code point (e.g., IPv4).
+
+User traffic MPLS-TP LSPs (shown for the sake of completeness):
+
+| | | |
+|-----------|-----------|----------------|
+| L2 header | L2CP=MPLS | MPLS-TP packet |
+|-----------|-----------|----------------|
+
+SCC IPv4 packets:
+
+| | | |
+|-----------|-----------|-----------------|
+| L2 header | L2CP=IPv4 | SCC IPv4 packet |
+|-----------|-----------|-----------------|
+
+SCC IPv6 packets:
+
+| | | |
+|-----------|-----------|-----------------|
+| L2 header | L2CP=IPv6 | SCC IPv6 packet |
+|-----------|-----------|-----------------|
+
+SCC OSI packets:
+
+| | | |
+|-----------|----------|----------------|
+| L2 header | L2CP=OSI | SCC OSI packet |
+|-----------|----------|----------------|
+
+###### **8.2.3.1.5.2 SCN link utilizing the MPLS-TP SCC as per [IETF RFC 5718]**
+
+[IETF RFC 5718] defines the packet format of the generic associated channel (G-Ach) SCC packet for MPLS-TP, which is based on the generic associated channel label (GAL)/G-ACh definition as per [IETF RFC 5586].
+
+The specification of the MPLS-TP to SCC adaptation function can be found in Annex C.
+
+###### **8.2.3.1.5.3 SCN link utilizing a dedicated MPLS-TP LSP**
+
+IPv4 and IPv6 packets must be encapsulated into MPLS-TP as per [IETF RFC 3032].
+
+The encapsulation of OSI CLNP packets into MPLS-TP is for further study.
+
+#### **8.2.3.2 MPLS-TP MCN**
+
+The same possibilities as described above for the SCN are defined for constructing the MCN:
+
+- MCN link sharing a server layer trail with MPLS-TP user traffic;
+
+- MCN link utilizing the MPLS-TP SCC as per [IETF RFC 5718];
+- MCN link utilizing a dedicated MPLS-TP LSP;
+- Separate and independent MCN links.
+
+A more detailed description of the MCC data-link layer termination function is provided below.
+
+##### **8.2.3.2.1 Non-MPLS-TP server layer trail providing an MCN link (MCN link sharing a server layer trail with MPLS-TP user traffic)**
+
+Refer to clause 8.4.1. It shall be noted that a deeper packet inspection may be needed (e.g., based on the destination address of the packet) to distinguish the MCC packets from the SCC packets in case the same layer-2 code point is used for the MCC and the SCC.
+
+##### **8.2.3.2.2 MCN link utilizing the MPLS-TP MCC as per [IETF RFC 5718]**
+
+[IETF RFC 5718] defines the packet format of the G-ACh MCC packet for MPLS-TP, which is based on the GAL/G-ACh definition, as per [IETF RFC 5586].
+
+The specification of the MPLS-TP to MCC adaptation function can be found in Annex C.
+
+##### **8.2.3.2.3 MCN link utilizing a dedicated MPLS-TP LSP**
+
+IPv4 and IPv6 packets must be encapsulated into MPLS-TP, as per [IETF RFC 3032].
+
+The encapsulation of OSI CLNP packets into MPLS-TP is for further study.
+
+### **8.2.4 EoT ECC**
+
+For further study.
+
+## **8.3 L3 Network layer requirements**
+
+### **8.3.1 L3 into L2 encapsulation function**
+
+A "Network layer PDU into ECC data-link frame" encapsulation function encapsulates and unencapsulates the network layer PDU into the data-link frame. This function also processes the protocol identifier. This function is defined in the technology-specific Recommendations. However, the specification for the "Network layer PDU into SDH ECC data-link frame" encapsulation function is provided below.
+
+#### **8.3.1.1 L3 into SDH ECC data-link frame encapsulation function**
+
+The specification of the "Network layer PDU into SDH ECC data-link frame" encapsulation function for IP-only interfaces, OSI-only interfaces, and dual interfaces is provided below.
+
+##### **8.3.1.1.1 IP-only interface**
+
+IP-only interfaces must use only PPPinHDLCframing/DCC, as per [IETF RFC 1662].
+
+An IP-only interface is defined as follows:
+
+*The transmit end*
+
+- Shall put IS-IS packets directly into PPP information field, as per [IETF RFC 1661], with the OSI protocol value, as per [IETF RFC 1377], into the PPP protocol field;
+- Shall put IPv4 packets directly into PPP information field, as per [IETF RFC 1661], with the IPv4 protocol value, as per [IETF RFC 1332], into the PPP protocol field;
+- Shall put IPv6 packets directly into PPP information field, as per [IETF RFC 1661], with the IPv6 protocol value, as per [IETF RFC 2472], into the PPP protocol field.
+
+###### *The receive end*
+
+- An IS-IS packet is identified if the PPP protocol field has the OSI protocol value as per [IETF RFC 1377], and if the packet has the network layer protocol identifier (NLPID) for IS-IS, as specified in [ITU-T X.263];
+- An IPv4 packet is identified if the PPP protocol field has the IPv4 protocol value, as per [IETF RFC 1332];
+- An IPv6 packet is identified if the PPP protocol field has the IPv6 protocol value, as per [IETF RFC 2472].
+
+##### **8.3.1.1.2 OSI-only interface**
+
+OSI-only interfaces must use only LAPD/DCC, as per [ITU-T G.784].
+
+An OSI-only interface is defined as follows:
+
+###### *The transmit end*
+
+- Shall put CLNP, IS-IS, and end system-to-intermediate system (ES-IS) packets directly into LAPD payload, as per [ITU-T G.784].
+
+###### *The receive end*
+
+- Shall inspect the protocol identifier located in the first octet of the LAPD payload. The value of this identifier is consistent with the values assigned in [ITU-T X.263]. If the PDU received is for a protocol not supported by the receiver, then the PDU shall be discarded.
+
+##### **8.3.1.1.3 Dual (IP+OSI) interface**
+
+A dual interface supporting PPP as the data-link protocol is defined as follows:
+
+###### *The transmit end*
+
+- Shall put CLNP, IS-IS, and ES-IS packets directly into PPP information field, as per [IETF RFC 1661], with the OSI protocol value, as per [IETF RFC 1377], into the PPP protocol field;
+- Shall put IPv4 packets directly into PPP information field, as per [IETF RFC 1661], with the IPv4 protocol value, as per [IETF RFC 1332], into the PPP protocol field;
+- Shall put IPv6 packets directly into PPP information field, as per [IETF RFC 1661], with the IPv6 protocol value, as per [IETF RFC 2472], into the PPP protocol field.
+
+###### *The receive end*
+
+- An OSI packet is identified if the PPP protocol field has the OSI protocol value, as per [IETF RFC 1377];
+- An IPv4 packet is identified if the PPP protocol field has the IPv4 protocol value, as per [IETF RFC 1332];
+- An IPv6 packet is identified if the PPP protocol field has the IPv6 protocol value, as per [IETF RFC 2472].
+
+A dual interface supporting LAPD as the data-link protocol is defined as follows:
+
+###### *The transmit end*
+
+- Shall put CLNP, IS-IS, and ES-IS packets directly into LAPD payload as per [ITU-T G.784];
+- Shall put IP packets directly into LAPD payload, with a one-octet protocol identifier prepended. This identifier will be consistent with [ITU-T X.263] assigned values for IPv4 and IPv6.
+
+###### *The receive end*
+
+- Shall inspect the protocol identifier located in the first octet of the LAPD payload. The value of this identifier is consistent with the values assigned in [ITU-T X.263]. If the PDU received is for a protocol not supported by the receiver, then the PDU shall be discarded.
+
+#### **8.3.1.2 L3 into MPLS-TP SCC data-link frame encapsulation function**
+
+The G-ACh, as defined in [IETF RFC 5586], can be used to carry SCC messages over an MPLS-TP section or a MPLS-TP segment. An SCC message is encapsulated as per [IETF RFC 5718]. The channel type field must be set to 0x0002 indicating that the packet is a G-ACh SCC packet carrying an SCC message. The PPP protocol identifiers, as per [IETF RFC 1661] and [IETF RFC 3818], are used to indicate the PDU type of the SCC message. Examples are provided in Table 8-1 below:
+
+**Table 8-1 – Examples of PID values for G-ACh SCC packets**
+
+| Protocol identifier (PID) value as per [IETF RFC 1661] and [IETF RFC 3818] | Protocol name |
+|-----------------------------------------------------------------------------------|-----------------------------|
+| 0x0021 | Internet protocol version 4 |
+| 0x0023 | OSI network layer |
+| 0x0057 | Internet protocol version 6 |
+
+#### **8.3.1.3 L3 into MPLS-TP MCC data-link frame encapsulation function**
+
+The G-ACh, as defined in [IETF RFC 5586], can be used to carry MCC messages over an MPLS-TP section or a MPLS-TP segment. An MCC message is encapsulated as per [IETF RFC 5718]. The channel type field must be set to 0x0001 indicating that the packet is a G-ACh MCC packet carrying an MCC message. The PPP protocol identifiers, as per [IETF RFC 1661] and [IETF RFC 3818], are used to indicate the PDU type of the MCC message.
+
+#### **8.3.1.4 L3 into EoT MCC data-link frame encapsulation function**
+
+For further study.
+
+#### **8.3.1.5 L3 into Ethernet frame encapsulation function**
+
+This function encapsulates and unencapsulates a network layer PDU into an IEEE 802.3 or Ethernet (version 2) frame.
+
+It shall encapsulate network layer PDUs into IEEE 802.3 or Ethernet (version 2) frames according to the following rules:
+
+- It shall encapsulate and unencapsulate CLNP, IS-IS, and ES-IS PDUs into IEEE 802.3 frames, as per [ITU-T Q.811];
+- It shall encapsulate and unencapsulate IP packets into Ethernet (version 2) frames, as per [IETF RFC 894];
+- IP addresses shall be mapped to Ethernet MAC addresses utilizing the address resolution protocol in [IETF RFC 826].
+
+It shall determine the received frame type (IEEE 802.3 or Ethernet version 2), as per section 2.3.3 in [IETF RFC 1122].
+
+### **8.3.2 L3 forwarding function**
+
+The network layer PDU forwarding function forwards network layer packets.
+
+If this function forwards CLNP packets, it shall forward CLNP packets, as per [ITU-T Q.811].
+
+If this function forwards IPv4 packets, it shall forward IPv4 packets, as per [IETF RFC 791].
+
+If this function forwards IPv6 packets, it shall forward IPv6 packets, as per [IETF RFC 2460].
+
+The preferred addressing format is IPv6. The IP routing protocol should be able to deal with IPv6 and IPv4 addressing.
+
+### 8.3.3 L3 interworking function
+
+The network layer PDU interworking function ensures that neighbouring DCF functions, running different network layer protocols can communicate. The DCF supporting IP is required to support OSI to allow communication to the neighbouring DCF supporting only OSI.
+
+The network layer PDU interworking function between two IP networks is for further study.
+
+### 8.3.4 L3 to L3 encapsulation function
+
+The network layer PDU encapsulation function encapsulates and unencapsulates one network layer PDU into another network layer PDU.
+
+CLNP packets shall be encapsulated over IP using generic routing encapsulation (GRE), as specified in [IETF RFC 2784], as payload in an IP packet using an IP protocol number of 47 (decimal) and with the *Don't Fragment* (DF) bit not set. As per [IETF RFC 2784], the GRE shall contain an Ethertype to indicate what network layer protocol is being encapsulated. The industry standard for OSI Ethertype, which is 00FE (hex) shall be used.
+
+IP packets shall be encapsulated over connectionless network layer service (CLNS) using GRE, as specified in [IETF RFC 2784], as the data payload of a CLNP data type PDU, as specified in [ITU-T X.233], using a network service access point (NSAP) selector value of 47 (decimal) and with the segmentation permitted (SP) flag set. Further information is available in [b-IETF RFC 3147].
+
+IP packets shall be encapsulated over IP using GRE, as specified in [IETF RFC 2784], as payload in an IP packet using an IP protocol number of 47 (decimal) and with the *Don't Fragment* (DF) bit not set.
+
+As an option, the network layer PDU encapsulation function may forward PDUs across incompatible nodes via the automatic encapsulation procedure described in Annex B. Note that a DCF supporting the automatic encapsulation procedure, described in Annex B, is compatible with and can be deployed in the same area as a DCF that does not support the automatic encapsulation procedure.
+
+### 8.3.5 L3 tunnelling function
+
+The network layer PDU tunnelling function provides a static tunnel between two DCFs supporting the same network layer PDU. For a tunnel with a configured maximum transmission unit (MTU) size, any IP packet that cannot be forwarded over the tunnel because it is larger than the MTU size, and has its DF bit set, should be discarded, and an Internet control message protocol (ICMP) unreachable error message (in particular the "fragmentation needed and DF set" code), as per [IETF RFC 792], for IPv4 should be sent back to the originator of the packet. In the case of IPv6, the path MTU discovery procedure ensures that the source node only sends packets that are smaller than the minimum MTU along the path. However, in the unlikely event that an IP packet is received by an intermediate node that is larger than the MTU size of the link towards the next hop, the packet is dropped and an ICMP Packet Too Big message, as per [IETF RFC 4443], should be sent back to the originator of the packet.
+
+### 8.3.6 L3 routing function
+
+The network layer routing function routes network layer packets.
+
+A DCF supporting OSI routing shall support IS-IS, as per [ISO/IEC 10589].
+
+A DCF supporting IP routing shall support integrated IS-IS (see clause 8.3.6.1 for integrated IS-IS requirements) and may also support OSPF, as per [IETF RFC 2328] and [IETF RFC 2740], as well as other IP routing protocols.
+
+#### **8.3.6.1 Integrated IS-IS requirements**
+
+A DCF supporting integrated IS-IS shall support [IETF RFC 1195].
+
+A DCF supporting integrated IS-IS shall support three-way handshaking on all point-to-point links (see Annex A for three-way handshaking requirements). Three-way handshaking modifies the adjacency creation and maintenance behaviour specified in [ISO/IEC 10589].
+
+##### **8.3.6.1.1 Network-layer protocol aware adjacency creation**
+
+The DCF shall include a "protocols supported" type length value (TLV) in all IS-IS hello (IIH) and intermediate system hello (ISH) PDUs on all interfaces, and in all link state protocol data units (LS-PDUs) with LS-PDU number 0, as per [IETF RFC 1195].
+
+On receipt of an IS-IS ISH or IIH PDU, the DCF shall inspect the PDU to see if it contains a "protocols supported" TLV. This shall take place on all interfaces, whether LAN, DCC or other links. If an ISH or IIH PDU does not contain a "protocols supported" TLV, then it shall be treated as if it contains a "protocols supported" TLV containing only the NLPID for CLNP.
+
+The DCF shall compare the NLPIDs listed in the "protocols supported" TLV (assuming only CLNP, if none, is present) with the network layer protocols that the DCF is itself capable of forwarding.
+
+If no adjacency exists with the neighbour that sent the ISH or IIH, and if the DCF is not capable of forwarding any of the network layer protocols listed in the "protocols supported" TLV of the ISH or IIH received from the neighbour, then the DCF shall not form an adjacency with that neighbour.
+
+If an adjacency does exist with the neighbour that sent the ISH or IIH, and if the DCF is not capable of forwarding any of the network layer protocols listed in the "protocols supported" TLV of the ISH or IIH received from the neighbour, then the DCF shall delete the adjacency with that neighbour and generate a ProtocolsSupportedMismatch event.
+
+If the DCF is itself capable of forwarding one or more of the network layer protocols listed in the "protocols supported" TLV of a received ISH or IIH, then the DCF shall process the ISH or IIH as normal.
+
+The DCF shall not consider the value of the "protocols supported" TLV of LS-PDUs during this process.
+
+A DCF that cannot forward CLNP PDUs shall ignore end system hello (ESH) PDUs and consequently shall not advertise reachability to OSI end systems.
+
+##### **8.3.6.1.2 IS-IS domain-wide IP prefix distribution**
+
+DCFs supporting Level-1, Level-2 integrated IS-IS shall support the advertising of configured IP destination prefixes learned via Level-2 into Level-1 LS-PDUs, as well as IP destination prefixes learned via Level-1 into Level-2 LS-PDUs. The default behaviour, when no IP destination prefixes have been configured, shall be to not propagate any Level-2 prefixes into Level-1 LS-PDUs, while all Level-1 learned prefixes shall be propagated into Level-2 LS-PDUs.
+
+###### **8.3.6.1.2.1 Configuration prefixes**
+
+The operator shall provision two tables that control the propagation of prefixes. One table shall control propagation from Level-1 to Level-2, while the other controls propagation from Level-2 to Level-1.
+
+###### **8.3.6.1.2.2 Tagging of propagated prefixes**
+
+Since propagating prefixes from Level-2 into Level-1 and subsequently from Level-1 back into Level-2 can introduce routing loops, a tag is necessary to identify the source of the prefix. This tag, called the
+
+up/down bit, is stored in the previously unused high-order bit (bit 8) of the default metric field in IP reachability TLVs and IP external reachability TLVs. Existing implementations of IS-IS that support [IETF RFC 1195] will not be impacted by the redefinition of this bit, as [IETF RFC 1195] requires it to be set to zero when originating LS-PDUs, and ignored upon receipt. Further information is available in [b-IETF RFC 2966].
+
+IP reachability TLVs and IP external reachability TLVs shall be processed in the same manner. The type of TLV received will be the same type used when the prefix is propagated from the Level-2 to a Level-1 area, as well as from a Level-1 area to the Level-2.
+
+This is different from [IETF RFC 1195], which limited IP external reachability TLVs to appearing only in Level-2 LS-PDUs.
+
+###### **8.3.6.1.2.2.1 Transmission of LS-PDUs with IP reachability TLVs and IP external reachability TLVs**
+
+As with normal [IETF RFC 1195], the value of the up/down bit shall be zero for all IP TLVs in Level-2 LS-PDUs. The value of the up/down bit shall be zero for Level-1 LS-PDUs originated within a Level-1 area.
+
+The up/down bit shall be set to one in an IP TLVs in Level-1 LS-PDU when a Level-1, Level-2 Integrated IS-IS NEs is propagating a configured prefix from Level-2 to Level-1.
+
+###### **8.3.6.1.2.2.2 Reception of LS-PDUs with IP reachability TLVs and IP external reachability TLVs**
+
+A DCF supporting integrated IS-IS shall ignore the value of the up/down bit when developing routes for use within a Level-1 area or for the Level-2.
+
+A DCF supporting Level-1, Level-2 integrated IS-IS that receives an LS-PDU with an IP TLV for a prefix that matches an entry in the Level-1 to Level-2 propagation table shall advertise the appropriate prefix from Level-1 to Level-2.
+
+A DCF supporting Level-1, Level-2 integrated IS-IS that receives an LS-PDU with an IP TLV with the up/down bit set to one shall never use the prefix for propagation of information from Level-1 to Level-2.
+
+###### **8.3.6.1.2.2.3 Use the up/down bit in Level-2 LS-PDUs**
+
+The use of up/down bit in Level-2 LS-PDUs is for further study.
+
+###### **8.3.6.1.2.3 Route preference**
+
+Given that prefixes can now be propagated from Level-2 to Level-1, the route preferences, specified in [IETF RFC 1195], must be updated to take into account this new source. The resulting route preference order is as follows:
+
+- 1) L1 intra-area routes with internal metric;
+L1 external routes with internal metric.
+- 2) L2 intra-area routes with internal metric;
+L2 external routes with internal metric;
+Inter-area routes propagated from L1 into the L2 with internal metric;
+Inter-area external routes propagated from L1 into the L2 with internal metric.
+- 3) Inter-area routes propagated from L2 into an L1 area with internal metric;
+External routes propagated from L2 into an L1 area with internal metric.
+- 4) L1 external routes with external metric.
+- 5) L2 external routes with external metric;
+
+Inter-area external routes propagated from L1 into the L2 with external metric.
+
+- 6) Inter-area external routes propagated from L2 into an L1 area with external metric.
+
+### **8.3.7 L3 IP routing interworking function**
+
+A DCF supporting the IP routing interworking function shall support route-filtering mechanisms, per sections 7.5 and 7.6 of [IETF RFC 1812], so that networks with two routing protocols can be connected via more than one exchange point.
+
+### **8.3.8 Applications to L3 mapping function**
+
+OSI applications running over (a part of) the DCN that only supports IP may be mapped into IP as specified in [ITU-T Q.812] dealing with [b-IETF RFC 2126] transmission control protocol (TCP)/IP protocol profile. Such a mapping is a Layer 4 solution and is therefore outside the scope of this Recommendation. Another option for carrying OSI applications across (a part of) the DCN that only supports IP is to provide OSI over IP Layer 3 encapsulation as specified in clause 8.3.4.
+
+The mapping of IP applications over (a part of) the DCN supporting IP shall be in accordance with IP suite specifications.
+
+## **8.4 Other requirements**
+
+### **8.4.1 Provisioning requirements**
+
+Every NE must support the creation of an interface that does not have any physical manifestation. This interface must be provisionable with an IP address.
+
+The LSP size shall be configurable.
+
+This allows the MTU size within the domain to be set.
+
+Area ID provisioning per interface, including ECC channels and LAN, is required for OSPF.
+
+### **8.4.2 Security requirements**
+
+Care must be taken to avoid unwanted interactions (addresses, etc.) between a public IP network and a DCN supporting IP.
+
+# **9 Specific DCN L3|L2|L1 technology requirements**
+
+## **9.1 Ethernet LAN as L1&L2**
+
+An Ethernet LAN physical termination function terminates the physical Ethernet interface, as defined in [IEEE 802.3].
+
+One or more of the following rates shall be supported: 1 Mbit/s, 10 Mbit/s, 100 Mbit/s, 1Gbit/s or any other higher bitrate as defined in [IEEE 802.3].
+
+Access to terminated ECC channels is allowed by network elements supporting Ethernet LAN interfaces. Not all network elements supporting ECC channels need to support Ethernet LAN ports, as long as there is an ECC path from a network element terminating the ECC channel and another network element providing Ethernet LAN ports.
+
+## **9.2 Ethernet WAN as L1&L2**
+
+Ethernet transport technologies such as Ethernet frames over ODUk can be used to carry DCN messages as an in-band channel. The mapping of Ethernet frames to ODUk refer to [ITU-T G.709]
+
+## 9.3 Native MPLS as L3
+
+This clause describes aspects of using native MPLS as ECC (SCC or MCC). Additional clarification may be provided in a future revision of this Recommendation.
+
+### 9.3.1 MPLS PDU into L2 encapsulation function
+
+This function encapsulates and unencapsulates a MPLS PDU into an ECC data-link layer frame.
+
+If PPP is the supported data link protocol on the ECC interface, the following is required:
+
+- *At transmit end*
+Shall put MPLS packets directly into PPP information field as per [IETF RFC 1661], with the MPLS protocol value of 0281 hex into the PPP protocol field, as per [IETF RFC 3032], section 4.3, for MPLS Unicast.
+- *At receive end*
+An MPLS packet is identified if the PPP protocol field has the MPLS protocol value of 0281 hex, as per [IETF RFC 3032], section 4.3, for MPLS Unicast.
+
+#### 9.3.1.1 "MPLS PDU into Ethernet frame" encapsulation function
+
+This function encapsulates and unencapsulates a MPLS PDU into an Ethernet (version 2) frame.
+
+It shall encapsulate MPLS PDUs into Ethernet (version 2) frames, as per [IETF RFC 894], using an Ethertype value of 8847 hex as per [IETF RFC 3032], section 5, for MPLS Unicast.
+
+### 9.3.2 MPLS LSP signalling function
+
+The MPLS LSP signalling function provides the signalling necessary to set up the MPLS LSP.
+
+A DCF supporting the MPLS LSP signalling function shall support the following reservation model: Explicit Path with a strict route via simple nodes (32 bits IP-address), for point-to-point unicast LSP, via the Reservation Style "FF" over IPv4.
+
+The Path message is forwarded to the destination along a path specified by a list of IP-addresses in the explicit route object (ERO). Each node (LSR) in the path records the ERO. Via the Label Request object, the nodes (LSRs) provide label binding for the session. See [IETF RFC 3209] – RSVP-TE, sections 2.2, 3.1, 4.2 and 4.3.
+
+The destination node responds with a Resv message, which is sent upstream towards the sender, in reverse order of the node-list in the ERO. The Label in the Label object of the Resv message is used in each intermediate LSR to associate outgoing traffic with this LSP. If the node is not the sender, it allocates a new Label and places that in the Label object of the Resv message, which it sends upstream to the previous HOP (PHOP). See [IETF RFC 3209] – RSVP-TE, sections 2.2 and 3.2 and 4.1.
+
+If the node cannot fulfil the request, it sends a PathErr or ResvErr message to the sender node. See [IETF RFC 3209] – RSVP-TE, section 4.5.
+
+The soft-state procedure of RSVP implies periodic sending of a full representation of the LSP state in Resv and Path messages to maintain the LSP. The Srefresh message is used in place of the periodic sending of standard Path and Resv messages. Each MessageID in the Srefresh message represents a full Path or Resv message, for which the state is not changed. See [IETF RFC 2961] – Resource Reservation Protocol – Overhead Reduction Extensions (RSVP-ORE), section 5.5.
+
+A MESSAGE\_ID\_NACK object is used to indicate that a received MessageID does not match, and a full Path or Resv message is needed to restore the LSP. See [IETF RFC 2961] – RSVP-ORE, section 5.4.
+
+A MESSAGE\_ID\_ACK object is used to acknowledge the receipt of messages containing the MESSAGE\_ID object and for which the ACK\_Desired flag is set. It is part of the Srefresh re-transmission algorithm as described in [IETF RFC 2961] – RSVP-ORE, section 6.3.
+
+### **9.3.3 MPLS LSP forwarding function**
+
+The MPLS LSP forwarding function forwards the incoming MPLS packet to an outgoing interface based on its MPLS label and the next hop label forwarding entry (NHLFE), as per [IETF RFC 3031]. The sequence of packets must be maintained within an LSP.
+
+### **9.3.4 MPLS LSP path computation function**
+
+The MPLS LSP path computation function calculates the path for a unidirectional LSP. This function shall be able to calculate paths for two unidirectional LSPs to the same destination such that their paths do not traverse the same node or subnetwork.
+
+### **9.3.5 "Network layer packet into MPLS" encapsulation function**
+
+The "Network layer packet into MPLS" encapsulation function adds/removes the MPLS label stack entry to/from the network layer packet, as per [IETF RFC 3032].
+
+### **9.3.6 MPLS packet 1+1 protection function**
+
+#### **9.3.6.1 Associating two LSPs**
+
+The ingress and egress nodes shall identify and associate the two LSPs providing packet 1+1 service. This association between two LSPs can be established using either network management interface or signalling.
+
+For the case of signalling, an identifier shall be transferred across each of the diverse LSPs. The identifier shall be identical on each of the diverse LSPs and shall be unique amongst LSPs initiated by the ingress node and amongst LSPs terminated by the egress node.
+
+The specific mechanism for assigning the identifier, as well as how the identifier is transported within the signalling protocol, is for further study. The mechanism will be similar to the one required for associating LSPs for other MPLS-based protection mechanisms such as 1+1 or 1:1.
+
+In order to meet the requirement that there are no signalling extensions required at the intermediate nodes, the identifier and the LSP service type (i.e., packet 1+1) shall be carried within opaque objects.
+
+#### **9.3.6.2 Sequence identifier format**
+
+The sequence number shall be used as the identifier for packet 1+1 protection. Each copy of the dual-fed packet is assigned the same unique sequence number by the ingress node. The sequence number of the next packet is generated by adding one to the current sequence number.
+
+The egress node uses the sequence number to make sure that only the first received copy of the packet is selected, whereas the second received copy is discarded. The egress node strips off the sequence number from the packet right after its selection and before passing to the upper layer of the stack. Note that packet 1+1 recovery scheme is independent of the applications/protocols supported above MPLS.
+
+The sequence number shall be carried in every packet as the first four bytes of the MPLS payload of each of the LSP providing packet 1+1 protection. The initial sequence number that is assigned to the first packet by the ingress node shall be agreed between the ingress and egress nodes. The default value of the initial sequence number is zero.
+
+The sequence number is located after the 4-bytes MPLS encapsulation header as illustrated in Figure 9-1.
+
+| | |
+|----------------------|-------------------------|
+| 4-bytes shim header | 4-bytes sequence number |
+| Encapsulation header | Sequence number |
+
+G.7712-Y.1703(19)\_F9-1
+
+**Figure 9-1 – Sequence identifier format**
+
+# Annex A
+
+## Requirements for three-way handshaking
+
+(This annex forms an integral part of this Recommendation.)
+
+The three-way handshaking procedure is based upon and designed to be compatible with the IETF IS-IS Working Group's Three-way Handshaking function ([b-IETF RFC 3373]).
+
+## A.1 Point-to-point three-way adjacency TLV
+
+A DCF supporting integrated IS-IS shall include a TLV in all point-to-point IIH PDUs. The structure of the TLV shall be:
+
+Type = 0xF0 (decimal 240)
+
+Length = 5 to 17 octets
+
+Value:
+
+Adjacency three-way state (one octet):
+
+0 = Up
+
+1 = Initializing
+
+2 = Down
+
+Extended local circuit ID of four octets
+
+Neighbour system ID of zero to eight octets, if known
+
+Neighbour extended local circuit ID of four octets, if known
+
+The extended local circuit ID shall be assigned by the DCF when the circuit is created, and the DCF shall use a different value for each point-to-point circuit that it has.
+
+The adjacency three-way state reported in the TLV shall be as specified in clause A.2.
+
+## A.2 Adjacency three-way state
+
+A DCF supporting integrated IS-IS shall have an adjacency three-way state for each point-to-point circuit. This state is different to the state specified in [ISO/IEC 10589].
+
+If no adjacency exists on a link, then the adjacency three-way state shall be set to "Down".
+
+If a DCF receives an ISH on a point-to-point link and this results in a new adjacency being created with adjacency state "Initializing", then the adjacency three-way state shall be set to "Down".
+
+If a DCF receives a point-to-point IIH that does not contain a three-way adjacency TLV, then the DCF shall behave as per [ISO/IEC 10589], but shall include the TLV in IIH PDUs on that link reporting the adjacency three-way state as "Down".
+
+If a DCF receives a point-to-point IIH PDU that contains a three-way adjacency TLV, then the DCF shall behave differently to [ISO/IEC 10589] IIH PDU processing as follows:
+
+- If the neighbour system ID and the neighbour extended local circuit ID fields of the TLV are present and if either neighbour system ID does not match the ID of the DCF, or the neighbour extended local circuit ID does not match the extended ID of the DCF, then the IIH PDU shall be discarded and shall not be processed;
+- If the IIH PDU results in the [ISO/IEC 10589] state tables producing an "Up" or "Accept", and if the received adjacency three-way state is "Down", then the DCF shall set its adjacency three-way state to "Initializing";
+
+- If the IIH PDU results in the [ISO/IEC 10589] state tables producing an "Up" or "Accept", and if the received adjacency three-way state is "Initializing", then the DCF shall change its adjacency three-way state from "Down" or "Initializing" to "Up" and generate an "AdjacencyChangeState(Up)" event;
+- If the IIH PDU results in the [ISO/IEC 10589] state tables producing an "Up" or "Accept", and if the received adjacency three-way state is "Initializing", then if the DCF already has an adjacency three-way state of "Up", it shall maintain the adjacency three-way state of "Up";
+- If the IIH PDU results in the [ISO/IEC 10589] state tables producing an "Up" or "Accept", and if the received adjacency three-way state is "Up", then if the DCF already has an adjacency three-way state of "Down", it will generate an "AdjacencyStateChange(Down)" event with the reason "Neighbour restarted" and the adjacency shall be deleted with no further IIH PDU processing taking place;
+- If the IIH PDU results in the [ISO/IEC 10589] state tables producing an "Up" or "Accept", and if the received adjacency three-way state is "Up", then if the DCF already has an adjacency three-way state of "Initializing", then it will change its adjacency three-way state to "Up" and generate an "AdjacencyChangeState(Up)" event;
+- If the IIH PDU results in the [ISO/IEC 10589] state tables producing an "Up" or "Accept", and if the received adjacency three-way state is "Up", then if the DCF already has an adjacency three-way state of "Up", it shall maintain the adjacency three-way state of "Up";
+- Following the comparison of source ID from the PDU with the local system, ID and manipulation of the circuit ID shall not be performed.
+
+If the IIH PDU results in the [ISO/IEC 10589] state tables producing an "Up" or "Accept", then the DCF shall:
+
+- 1) copy the adjacency areaAddressOfNeighbour entries from the area addresses field of the PDU;
+- 2) set the holdingTimer value of the holding time field from the PDU; and
+- 3) set the neighbourSystemID to the value of the source ID field from the PDU as per [ISO/IEC 10589].
+
+# Annex B
+
+## Requirements for automatic encapsulation
+
+(This annex forms an integral part of this Recommendation.)
+
+## B.1 Introduction
+
+This annex provides a specification for the optional automatic encapsulating data communication function (AE-DCF) that enables nodes that support routing of differing incompatible network layer protocols, such as CLNS, IPv4 or IPv6 to be present in a single IS-IS Level-1 area or Level-2 subdomain, and which automatically encapsulates one network layer protocol into another as required, provided that all of the nodes support IS-IS or integrated IS-IS routing.
+
+## B.2 Scope
+
+The AE-DCF is an optional function. When it is provided, it shall function as specified in this annex. The requirements in this annex apply only to DCFs that contain the additional functionality of an AE-DCF. The AE-DCF also requires certain behaviours from DCFs that do not include AE-DCF functionality, in order to interwork with them. Requirements for DCFs that do not include AE-DCF functionality are found in clause 8.3.6.1 for IP and dual nodes, and in [ISO/IEC 10589] for OSI nodes.
+
+## B.3 Description of the AE-DCF
+
+### B.3.1 Introduction
+
+Integrated IS-IS, as specified in [IETF RFC 1195], was originally designed to be able to route IP and CLNS using a single routing protocol, and a single shortest path first (SPF) algorithm. For this, it represents IPv4 addresses and subnet masks as a 64-bit number which is then treated by the SPF algorithm as if it were an OSI end system address. Integrated IS-IS nodes are required to have an IS-IS area address and a system identifier, which is treated in the same way as an NSAP address is in an OSI-only node. Integrated IS-IS nodes then form adjacencies and flood system identifiers and metrics throughout their Level-1 area (Level-1 routers) or their Level-2 subdomain (Level-2 routers) in the same way as OSI-only IS-IS nodes.
+
+System identifiers (SIDs) and metrics to other SIDs are flooded throughout a Level-1 area or Level-2 subdomain using LS-PDUs (link state PDUs) that are common to both IS-IS and integrated IS-IS nodes. IP-specific information is then added to these LS-PDUs using TLV extensions that are understood only by IP-capable nodes. OSI-only routers cannot decode these TLVs but still flood them onwards to all of their adjacencies. In this way, an SPF tree can be built by any IS-IS or integrated IS-IS node whether it can route CLNS, IPv4 or IPv6. OSI-capable nodes will calculate the shortest paths to OSI end systems, IPv4-capable nodes will calculate the shortest paths to IPv4 addresses or prefixes, and IPv6-capable nodes will calculate the shortest paths to IPv6 addresses or prefixes.
+
+One consequence of this is that an OSI-only node will calculate a shortest path to an OSI end system that goes through an IP-only node, even though that IP-only node cannot forward CLNS packets. Similarly, an IP-only node will calculate a shortest path to an IP destination that goes through an OSI-only node, even though the OSI-only node cannot forward IP packets. Thus, an OSI-only capable node must not be placed in a part of a network where there is any possibility of it being on the shortest path to IP destinations, and an IP-only node must not be placed in a part of the network where there is any possibility of it being on the shortest path to an OSI end system.
+
+The integrated IS-IS algorithm can only use a single SPF algorithm for two or more network layer protocols due to an assumption that all network-layer protocols have access to the same resources; in other words, the same network with the same topology. Thus, integrated IS-IS requires any node in a Level-1 area or Level-2 subdomain to be able to route any network layer protocol that is present in the area or domain respectively.
+
+For this reason, [IETF RFC 1195] places topological restrictions on networks that are routed by integrated IS-IS, requiring that all of the nodes support both IP and CLNS in an area that have both CLNS traffic and IP traffic present in them.
+
+Consequently, according to [IETF RFC 1195], if one node is upgraded and forwards IP packets, then all of the others in the Level-1 area or Level-2 subdomain must also be upgraded.
+
+The solution proposed here allows this topological restriction to be removed, and it automatically encapsulates CLNS packets inside IP packets for forwarding across IP-only nodes and encapsulates IP packets inside CLNS packets for forwarding across OSI-only nodes. The solution proposed here is fully compatible with existing OSI-only nodes, which will not require any upgrade. It places one requirement upon IPv4-only or IPv6-only nodes above those in [IETF RFC 1195], specifically the network-layer protocol aware adjacency creation function specified in clause 8.3.6.1.1.
+
+### B.3.2 Basic concept
+
+This feature takes advantage of the fact that all integrated IS-IS and IS-IS nodes share basic topology information in the same way, and of the behaviour that OSI-only nodes will attempt to forward a packet across an IP-only node and vice versa, even though that node is incapable of actually forwarding the packet. Normally, this would result in packet loss, but an AE-DCF encapsulates packets before they are forwarded across incompatible nodes so that they are not lost.
+
+When two islands of IP capable integrated IS-IS nodes are connected using a central network that supports only OSI, and if all of the nodes participate in the same area (for Level-1 nodes), then the IP capable nodes will receive the LS-PDUs from all of the other IP capable nodes, even those in the other island, as well as the LS-PDUs from all of the OSI-only nodes in the centre. Thus, they calculate shortest paths across the OSI-only nodes for all of the IP destinations in the island on the far side. It is only when an IP-capable node actually forwards an IP packet to an OSI-only node that things go wrong, and the packet is lost; hence, the topological restrictions in [IETF RFC 1195].
+
+
+
+The diagram illustrates two network topologies. The top topology shows two IP nodes (represented by computer icons) connected to a central OSI NE (Network Element) via Dual OSI/IP NEs. The bottom topology shows two OSI nodes connected to a central IP NE via Dual OSI/IP NEs. A small text 'G.7712-Y.1703(19)\_FB.19' is present below the diagrams.
+
+Figure B.1 shows two network diagrams illustrating illegal topologies. The top diagram shows two IP nodes connected via a central OSI NE through Dual OSI/IP NEs. The bottom diagram shows two OSI nodes connected via a central IP NE through Dual OSI/IP NEs. A small text 'G.7712-Y.1703(19)\_FB.19' is present below the diagrams.
+
+**Figure B.1 – Illegal topologies**
+
+The above simple networks illustrated in Figure B.1 are illegal topologies according to [IETF RFC 1195]. In the top network IP packets will be routed from one side of the network to the other, but on arrival at the OSI-only node they will be discarded. Similarly, in the bottom network CLNS packets will be routed from one side of the network to the other, but on arrival at the IP-only node they will be discarded. An AE-DCF specified here corrects this behaviour.
+
+
+
+The diagram illustrates two network paths for encapsulation 'repair'.
+ Top path: An IP node connects to a Dual OSI/IP NE, which connects to an OSI NE. The OSI NE connects to another Dual OSI/IP NE, which connects to an IP node. A dashed arrow labeled 'IP traffic encapsulated [b-IETF RFC 3147]' shows traffic being encapsulated at the first Dual OSI/IP NE and decapsulated at the second.
+ Bottom path: An OSI node connects to a Dual OSI/IP NE, which connects to an IP NE. The IP NE connects to another Dual OSI/IP NE, which connects to an OSI node. A dashed arrow labeled 'CLNS traffic encapsulated [b-IETF RFC 1702]' shows traffic being encapsulated at the first Dual OSI/IP NE and decapsulated at the second.
+ A small text label 'G.7712-Y.1703(19)\_FB.2' is located at the bottom right of the diagram.
+
+Figure B.2 – Encapsulation 'repair' showing two network paths. The top path shows IP traffic being encapsulated by a Dual OSI/IP NE and then decapsulated by another Dual OSI/IP NE after passing through an OSI NE. The bottom path shows CLNS traffic being encapsulated by a Dual OSI/IP NE and then decapsulated by another Dual OSI/IP NE after passing through an IP NE. Both paths start and end at IP or OSI nodes.
+
+**Figure B.2 – Encapsulation "repair"**
+
+The AE-DCF resides in dual nodes and enables them to recognize that a particular neighbour will discard certain traffic, and so to encapsulate it into a form that will not be discarded (see Figure B.2). This 'repairs' the network so that the part of network between the dual nodes acts as if it is comprised of all dual nodes when, in actual fact, one, or more of the nodes are not dual.
+
+An AE-DCF does not alter the path that a packet will take across the network; any individual packet will still cross the network using the shortest path as calculated by the normal IS-IS SPF algorithm.
+
+The network-layer protocol aware adjacency creation function specified in clause 8.3.6.1.1 forces traffic to go through nodes that support both IP and OSI whenever the shortest path takes traffic across a boundary between IP-capable and OSI-capable parts of an area. The AE-DCF then enables those dual nodes to encapsulate a packet if necessary, so that it can be forwarded by nodes that do not support that network layer protocol. This encapsulation takes place only when necessary, and thus these tunnels are automatically created and are dynamic. The resulting tunnels are not maintained in any way and exist only as entries in forwarding tables. The tunnels do not appear as a circuit or interface as far as the routing protocol is concerned. Thus, packets still cross the network along the shortest path that each node calculates normally, and there is no need for IS-IS packets to be encapsulated, only IP and CLNS traffic is encapsulated.
+
+## **B.4 Requirements and limitations**
+
+### **B.4.1 Requirements for OSI-only nodes**
+
+In order to interwork with the AE-DCF, OSI-only nodes are required to be conformant to [ISO/IEC 10589].
+
+### **B.4.2 Requirements for IP-capable nodes**
+
+In order to interwork with the AE-DCF, IP-only nodes are required to be conformant to [IETF RFC 1195].
+
+In particular, IP-capable nodes are required to ignore the "protocol supported" TLV in LS-PDUs of nodes that they are considering as candidates for shortest paths when running the SPF algorithm.
+
+An IP-capable node that only includes IP-capable nodes in its SPF calculation would not conform to [IETF RFC 1195], where it states:
+
+- From page 26 of [IETF RFC 1195]: "The Dijkstra computation does not take into consideration whether a router is IP-only, OSI-only, or dual. The topological restrictions specified in section 1.4 ensure that IP packets will only be sent via IP-capable routers, and OSI packets will only be sent via OSI-capable routers."
+
+The AE-DCF is compatible with [IETF RFC 1195] implementations that conform to the above statement. An implementation that only includes IP-capable nodes in its SPF calculation would not view paths through OSI-only nodes as being a suitable route, and so will not take advantage of the AE-DCF.
+
+In order to interwork with the AE-DCF, IP nodes are required to conform to clause 8.3.6.1.1. The reason for this is stated below:
+
+- This solution is dependent upon IP packets arriving at an OSI-only node, having first gone through an AE-DCF, and upon CLNS packets arriving at an IP-only node, having first gone through an AE-DCF. The AE-DCF is then responsible for encapsulating these packets so that they can be forwarded;
+- Therefore, an IP-only node must never have an adjacency with an OSI-only node;
+- If this solution is used to mix IPv4 and IPv6 nodes in the same Level-1 area or Level-2 subdomain, then similarly an IPv4-only node must never have an adjacency with an IPv6-only node;
+- This requirement is met if all IP-capable nodes conforming to clause 8.3.6.1.1. Note that this requirement is not present in [IETF RFC 1195].
+
+Alternatively, an operator may manually ensure that nodes that do not support a network layer protocol in common do not have adjacencies.
+
+### **B.4.3 Requirements for automatically encapsulating dual or multilingual nodes**
+
+If this feature is to be used in a Level-1 area or Level-2 subdomain, then nodes that support more than one network layer protocol, but that do not support the AE-DCF, may be used with caution. A safer alternative is either to comply with the topological restrictions of [IETF RFC 1195], or to use only dual or multilingual nodes that contain the AE-DCF.
+
+#### **B.4.3.1 Encapsulation capability TLV**
+
+The AE-DCF will include a new TLV in LS-PDUs with LS-PDU number equal to zero. The new TLV will have the following structure:
+
+Code: 16 (decimal)
+
+Length: The length of the value
+
+Value: A variable length part containing the following:
+
+Sub-TLV type: 1
+
+Sub-TLV length: 3 times the number of encapsulation modes in the sub-TLV
+
+Sub-TLV value:
+
+47 indicating that the next two bytes are a GRE encapsulation;
+
+The NLPID of a packet that may be encapsulated (inner);
+
+The NLPID of a packet that transports the encapsulated packet (outer);
+
+Bytes 4, 5, 6: A second encapsulation mode (if needed);
+
+Bytes 7, 8, 9: A third encapsulation mode (if needed);
+
+etc.
+
+The NLPIDs that are used shall be those as specified in [ITU-T X.263]. Nodes that transmit this TLV shall indicate the formats that a node can both receive and transmit. Nodes must be able to both automatically encapsulate and automatically unencapsulate the formats that are described in the TLV, so that traffic may be received, and so that traffic may return in the reverse direction.
+
+It is recommended that dual nodes supporting an AE-DCF are able to encapsulate/unencapsulate A over B, and B over A (where A and B are the two supported network layer protocols) making two encapsulation modes in a typical dual node.
+
+For example, the contents of the TLV for a typical OSI and IPv4 AE-DCF will be:
+
+- 16: the code;
+- 8: the value length (in this example);
+- 1: sub-TLV type 1;
+- 6: sub-TLV length (in this example);
+- 47: next two bytes are a supported GRE mode;
+- 129: Initial protocol identifier (IPI) for CLNP from [ITU-T X.263];
+- 204: IPI for IPv4 from [ITU-T X.263];
+- 47: next two bytes are a supported GRE mode;
+- 204: IPI for IPv4 from [ITU-T X.263];
+- 129: IPI for CLNP from [ITU-T X.263].
+
+An OSI, IPv4, IPv6 AE-DCF will thus typically use six encapsulation modes to indicate CLNP over IPv4, CLNP over IPv6, IPv4 over CLNS, IPv4 over IPv6, IPv6 over CLNS, and IPv6 over IPv4, giving a value length of 20.
+
+This TLV will not be included in pseudonode LS-PDUs.
+
+An AE-DCF that does not have any IPv4 addresses must not place any encapsulation formats in its TLV of type equal 16 that include IPv4 as an encapsulation transport (outer) NLPID until such time as an IPv4 address is provisioned and advertised.
+
+An AE-DCF that does not have any IPv6 addresses must not place any encapsulation formats in its TLV of type equal 16 that include IPv6 as an encapsulation transport (outer) NLPID until such time as an IPv6 address is provisioned and advertised.
+
+#### **B.4.3.2 Forwarding process**
+
+As the AE-DCF does not modify the path that a packet follows, an AE-DCF may calculate a shortest path for an IP packet that results in the next hop being an OSI-only node.
+
+When this happens, the AE-DCF must not simply forward a packet to an adjacent node that does not support that type of network layer protocol. Instead, the AE-DCF must encapsulate the packet inside a new packet of a type that the next hop does support. The criteria for whether an adjacent node does or does not support a particular network layer protocol is whether that network layer protocol is listed in the "protocols supported" TLV in IS-IS Hello PDUs received from the node on the adjacency which is the next hop for that destination.
+
+This new packet requires a network layer protocol, a destination address, and a source address to encapsulate the original packet:
+
+- The network layer protocol of the new packet must be one that is supported by the next hop, as defined by the "protocols supported" TLV of Hello PDUs received from the next hop;
+- The destination address of the new packet must be equal to the identity of the next node along the shortest path to the original destination that has transmitted an encapsulation mode that has both the type of network layer protocol that the original packet is as the encapsulated (inner) NLPID, and a network layer protocol that is supported by the next hop (as defined by the "protocols supported" TLV of Hello PDUs received from the next hop) as the encapsulation transport (outer) NLPID;
+
+- This must be achieved by inspection of the new TLV of type equal to 16 from LS-PDUs received from each node in the path to the destination, until the first is found that meets the above requirement;
+- When inspecting TLVs of type equal to 16, an AE-DCF shall ignore any sub-TLVs that it does not understand, and shall jump to the next sub-TLV and shall inspect that, either until it finds all of the encapsulation modes that it is looking for, or until it reaches the end of the TLV;
+- The source address of the new packet must be equal to the identity of the AE-DCF that constructs the new encapsulation packet.
+
+If an AE-DCF can forward a packet without encapsulation because the next hop supports that type of packet, then the AE-DCF must forward the packet without encapsulating it.
+
+An AE-DCF might send LS-PDUs containing IP reachability from an IP-only node on to a split stack node, or vice versa, and consequently might then be required to encapsulate packets headed for a split stack node, or unencapsulate packets received from a split stack node.
+
+Thus, an automatically encapsulating split stack node must also follow the same process of inspecting LS-PDUs of nodes between itself and the destination looking for a node that has a suitable encapsulation format.
+
+Note that a split stack node might be capable of receiving an IPv4 packet only encapsulated inside CLNS, for example. In this case, the split stack node will transmit only "CLNS" in the "protocols supported" field of its Hello packets and will only include one encapsulation mode in its TLV of type equal 16 in its LS-PDUs. This single encapsulation mode will specify IPv4 as the encapsulated (inner) packet NLPID and CLNS as the encapsulation transport (outer) packet NLPID.
+
+#### **B.4.3.3 Receipt process**
+
+When an AE-DCF receives a packet that is destined for itself, it must inspect that packet to see if it has another packet encapsulated inside it. The resultant unencapsulated CLNS, IPv4 or IPv6 packet must then be forwarded as normal. If the resultant unencapsulated packet then contains another packet destined for this node, the process is repeated; this is because multiple layers of encapsulation may require unencapsulation at a single AE-DCF.
+
+IS-IS packets are not compatible with IP packets and cannot be forwarded across the public Internet or other IP-only networks. This is a security advantage as it makes it difficult for a malicious entity to remotely launch IS-IS packets at IS-IS or integrated IS-IS nodes across the public Internet. In order not to remove this advantage, then, if an IS-IS or ES-IS packet arrives encapsulated inside another packet destined for an AE-DCF, then the AE-DCF must discard it unless it came from a node with which the AE-DCF has a manually provisioned tunnel with IS-IS provisioned to run across it. Optionally, an error report may be raised informing the network manager of information such that a packet was received and dropped, where it came from, or that it is a potential malicious event.
+
+All packets must be encapsulated using GRE encapsulation as specified in clause 8.3.4.
+
+#### **B.4.3.4 MTU size and fragmentation requirements**
+
+The encapsulation of one packet inside another may result in a new packet that is longer than the MTU size of the link over which this new packet must be forwarded. This new GRE packet must not be discarded; therefore, these packets must not have the Don't Fragment bit set if they are IPv4 packets and must have the SP flag set if they are CLNS packets, as per clause 8.3.4.
+
+The resultant encapsulation packets must then be fragmented before being forwarded if the packet is now longer than the MTU limit of the link.
+
+It is not necessary to fragment a packet before encapsulating it, as the resultant encapsulation packet will be fragmented if necessary.
+
+#### **B.4.3.5 Requirements for AE-DCF with broadcast (LAN) interfaces**
+
+##### **B.4.3.5.1 Pseudo-node election process**
+
+According to clause 8.3.6.1.1, IP-only nodes are not allowed to form an adjacency with OSI-only nodes, and IPv4-only nodes are not allowed to form an adjacency with IPv6-only nodes.
+
+Therefore, when IP-only and OSI-only nodes are connected to the same LAN and in the same Level-1 area or Level-2 subdomain, then the IP-only nodes will form adjacencies with one another and will elect a pseudonode, whilst the OSI-only nodes will form separate adjacencies and will elect a different pseudonode. Therefore, there will be two separate pseudonodes on the LAN, one for the OSI-only nodes, and one for the IP-only nodes.
+
+A similar thing may happen if IPv4-only and IPv6-only nodes are connected to the same LAN.
+
+An AE-DCF must, therefore, take part in these separate pseudonode election processes independently for each network layer that it supports. A Level-1/Level-2 AE-DCF must take part in two pseudonode election processes for each network layer protocol that it supports (one for Level-1 and one for Level-2).
+
+Each pseudonode on the LAN residing on a node of a network layer protocol compatible with the AE-DCF will have an adjacency with the AE-DCF. Thus, on an IP & OSI LAN, the AE-DCF will correctly be the one that has valid adjacencies both with the IP pseudonode and with the OSI pseudonode (if multiple pseudonodes are present on the LAN). The AE-DCF will have an adjacency with the IP pseudonode and with the OSI pseudonode, but the IP pseudonode will not have a direct adjacency with the OSI pseudonode, and vice versa, but will instead gain connectivity only through the AE-DCF, thus guaranteeing that CLNS packets are encapsulated by the AE-DCF before being forwarded to IP-only nodes, and that IP packets are encapsulated by the AE-DCF before being forwarded to OSI-only nodes.
+
+An IP- and OSI-capable AE-DCF may be elected as the designated router by the IP-capable nodes on the LAN, but not by the OSI-capable nodes; in this case, the AE-DCF must create a pseudonode, but the pseudonode must declare adjacencies in its LS-PDUs only with the IP-capable nodes on the LAN.
+
+Similarly, an IP- and OSI-capable AE-DCF may be elected as the designated router by the OSI-capable nodes on the LAN, but not by the IP-capable nodes; in this case, the AE-DCF must create a pseudonode, but the pseudonode must declare adjacencies in its LS-PDUs only with the OSI-capable nodes on the LAN.
+
+An IP- and OSI-capable AE-DCF may be elected as the designated router both by the IP-capable and by the OSI-capable nodes on the LAN; in this case, the AE-DCF must create a pseudonode that declares adjacencies in its LS-PDUs to all of the nodes on the LAN.
+
+In essence, an AE-DCF takes part in a separate election process for each network layer protocol that it supports, and if it wins any of the elections then it creates a pseudonode, but the pseudonode will declare adjacencies in its LS-PDUs only with the set, or sets, of nodes that elected it.
+
+Consequently, OSI-only or IP-only nodes may receive LS-PDUs from a pseudonode that lists adjacencies to nodes on the LAN that they do not have adjacencies with. If a packet should need to be forwarded via such a node, then it should be sent to the designated IS as per [ISO/IEC 10589] section C.2.5 item "h", and as per [IETF RFC 1195] section C.1.4 step 0 clause 8 on page 73. Note that these clauses in [ISO/IEC 10589] and [IETF RFC 1195] are non-normative. It is possible that there are implementations that do not exhibit this behaviour. Such an implementation will drop packets rather than send traffic to an AE-DCF for automatic encapsulation, if the AE-DCF is the designated router, and if non-compatible nodes on the same LAN are on the shortest path.
+
+Implementers and operators, therefore, have a choice to make; the choice is:
+
+- 1) Set the priority of the AE-DCF to a high value. This results in a single pseudonode appearing on the LAN, supported by an AE-DCF. The disadvantage of this approach is that there is a
+
+small chance that a legacy implementation exists on the LAN that does not forward traffic to an AE-DCF if a non-compatible node on the LAN is on the shortest path; or
+
+- 2) Set the priority of the AE-DCF to a low value. This results in one pseudonode appearing on the LAN for every network-layer protocol supported, explicitly sending traffic for non-compatible nodes through an AE-DCF. This improves interoperability but doubles the amount of LS-PDUs transmitted onto the LAN, possibly reducing scalability.
+
+It is recommended that the priority of an AE-DCF is operator configurable.
+
+##### **B.4.3.5.2 LS-PDU update process**
+
+[ISO/IEC 10589] states in section 7.3.15.1 that an LS-PDU received, which does not come from a valid adjacency, must be discarded. A strict OSI-only implementation will therefore reject LS-PDUs that are transmitted onto a LAN interface by an IP-only node, as the IP-only node has rejected the adjacency as per clause 8.3.6.1.1. Thus, the OSI-only node can receive such an LS-PDU only from an AE-DCF. Without modified behaviour, a dual node would only forward such an LS-PDU during periodic LS-PDU database synchronization.
+
+An AE-DCF is, therefore, required to have modified LS-PDU flooding behaviour so that OSI-only or IP-only nodes do not need to wait for the next LS-PDU database synchronization event.
+
+An AE-DCF must check incoming LS-PDUs that arrive on LAN interfaces to see if they come from a neighbour that supports all of the network layer protocols that the AE-DCF does. This must be achieved by inspection of the "protocols supported" TLV in Hello packets received from that neighbour.
+
+If the LS-PDU is received from a neighbour that does support all of the network layer protocols that the AE-DCF supports, then the AE-DCF shall behave as per [ISO/IEC 10589] and unset the send routing message (SRM) flag for that LS-PDU on that LAN interface if it already has the LS-PDU, or shall flood it out of all other interfaces if it does not already have the LS-PDU.
+
+If the LS-PDU is received from a neighbour that does not support all of the network layer protocols that the AE-DCF supports, and if it does not already have the LS-PDU, then the AE-DCF shall set the SRM flag for that LS-PDU on the LAN interface over which the LS-PDU was received, in addition to all other interfaces, resulting in the AE-DCF retransmitting the LS-PDU onto the LAN.
+
+In this way, if an LS-PDU is transmitted onto the LAN by an IP-only node, then an AE-DCF will retransmit the LS-PDU, so that it may be received on a valid adjacency by OSI-only nodes on the LAN and vice versa.
+
+##### **B.4.3.5.3 Redirects**
+
+If an AE-DCF originates an ICMP redirect request, the request must not redirect IPv4 packets from an IPv4-capable node to a non-IPv4-capable node. Likewise, if an AE-DCF originates [ISO 9542] redirect PDUs, the redirect must not redirect CLNS packets from an OSI capable node to a non-OSI-capable node.
+
+##### **B.4.3.5.4 Mixing of dual [IETF RFC 1195] only and automatically encapsulating nodes on a LAN**
+
+A dual node that is conformant to [IETF RFC 1195], but that does not support an AE-DCF, must not reside on a LAN in the same Level-1 area or Level-2 subdomain as both IP-only and OSI-only nodes, as it may forward IP traffic to an OSI-only node, or CLNS traffic to an IP-only node, resulting in packet loss. This is a topological restriction of [IETF RFC 1195].
+
+A dual node that is conformant to [IETF RFC 1195], but that does not support an AE-DCF, may reside on a LAN in the same Level-1 area or Level-2 subdomain as an AE-DCF.
+
+Additionally, it may reside on a LAN with an OSI-only node if it can forward only CLNS traffic to that node, an IPv4-only node if it can forward only IPv4 traffic to that node, or an IPv6-only node if it can forward only IPv6 traffic to that node.
+
+### **B.4.4 Requirements for automatically encapsulating split stack nodes**
+
+A split stack node initiates and terminates packets of a network-layer protocol type that it cannot forward natively in its DCC channels. Therefore, the only way that such a node may initiate or terminate such packets is if they are in an encapsulated form.
+
+This solution is particularly useful for adding an IP card into a predominantly OSI node, or a node that will be installed into an existing OSI network, for example. It may also be easier to upgrade an OSI gateway NE to a split stack node, rather than to a dual AE-DCF, so that IP traffic can get in and out of the network for which the node is a gateway.
+
+The split stack node must be able to internally route any packets that it receives that are of a network-layer protocol equal to one of those listed in the "protocols supported" TLVs of its' IS-IS LS-PDUs.
+
+A split stack node must use the "protocols supported" TLV in IS-IS Hello PDUs to indicate only the network-layer protocols that it can receive and forward natively on any individual interface (or not support this TLV if it is an OSI-only interface).
+
+That is, an IP-over-OSI node can route CLNS natively in its DCC channels, and can route IP traffic that arrives for it in IP-over-OSI GRE encapsulated packets, or possibly an Ethernet interface.
+
+Thus, a split stack node may indicate one network layer protocol in the "protocols supported" TLV of Hello packets on one interface, and a different network layer protocol in the "protocols supported" TLV of Hello packets on another interface. Such a node would be able to route both network layer protocols internally, and so would advertise both in the "protocols supported" TLV of its LS-PDUs.
+
+A split stack node must use IP reachability TLVs in IS-IS LS-PDUs to indicate the address range of encapsulated packets that it is able to terminate.
+
+A split stack node might receive IP reachability extensions from an IP-only node, via a dual AE-DCF. Therefore, the split stack node must be able to send traffic to a destination via an AE-DCF, which it will use to unencapsulate its packets. To achieve this, a split stack node must search for the next node along the path to each destination capable of unencapsulation, or for a split stack destination, in exactly the same way that an AE-DCF does.
+
+An automatically encapsulating split stack node shall advertise the encapsulation modes that it supports using encapsulation capability TLV as per clause B.4.3.1.
+
+When a split stack node receives a packet that is destined for itself, it must inspect that packet to ascertain whether it has another packet encapsulated inside it. If so, then the packet will be processed internally, unless it is an IS-IS or ES-IS packet, in which case it must be discarded (unless a manually provisioned tunnel exists with IS-IS provisioned to run across it) in the same way as it would be by a dual AE-DCF.
+
+In the same way as a dual AE-DCF, a split stack node must support GRE encapsulation as specified in clause 7.1.8.
+
+### **B.4.5 Use of IP nodes that do not conform to clause 8.3.6.1.1 with the AE-DCF**
+
+IPv4-only or IPv6-only nodes that are conformant to [IETF RFC 1195], but that do not support the protocol aware adjacency creation function specified in clause 8.3.6.1.1, may be used in the same mixed Level-1 area or Level-2 subdomain as an AE-DCF, but the network manager must manually ensure that such a node does not have any adjacencies with other nodes that might forward packets to it that it does not support.
+
+### B.4.6 Use of dual nodes with no AE-DCF and dual nodes with AE-DCF in the same IS-IS area
+
+Dual nodes that are conformant to [IETF RFC 1195], but that do not support an AE-DCF, may be used in mixed Level-1 areas or Level-2 subdomains with an AE-DCF with the restrictions below:
+
+Integrated IS-IS nodes (or clusters of nodes) that support more than one network layer protocol but which do not support an AE-DCF are still subject to the topological restrictions of [IETF RFC 1195]. This means that the network manager must ensure that such a node cannot pass packets to a neighbouring node that cannot forward that type of packet.
+
+That is, dual signifies a dual integrated IS-IS node that conforms to [IETF RFC 1195], but that does not contain an AE-DCF.
+
+OSI-AEDCF-dual-AEDCF-IP is a safe combination;
+
+OSI-AEDCF-dual-dual-dual-AEDCF-IP is a safe combination;
+
+IPv4-AEDCF-dual IPv4&IPv6-AEDCF-IPv6 is a safe combination;
+
+dual-AEDCF-OSI-AEDCF-dual is a safe combination;
+
+OSI-IPv4&OSIAEDCF-dual IPv4&OSI-dual IPv4&IPv6-IPv4&IPv6 AEDCF-IPv6 is not a safe combination;
+
+OSI-IPv4&OSIAEDCF-dual IPv4&OSI-IPv4&IPv6&OSI-dual IPv4&IPv6-IPv4&IPv6 AEDCF-IPv6 is not a safe combination.
+
+
+
+Potential autotunnels
+
+Dual OSI/IP NE OSI NE Dual OSI/IP NE Dual OSI/IP NE Dual OSI/IP NE IP NE Dual OSI/IP NE
+
+This node will never initiate or terminate an autotunnel
+
+G.7712-Y.1703(19)\_FB.3
+
+Diagram illustrating topological requirements for IS-IS area dual nodes. A sequence of nodes is shown: Dual OSI/IP NE, OSI NE, Dual OSI/IP NE, Dual OSI/IP NE, Dual OSI/IP NE, IP NE, Dual OSI/IP NE. Dashed arrows labeled 'Potential autotunnels' connect the first Dual OSI/IP NE to the second Dual OSI/IP NE, and the second Dual OSI/IP NE to the third Dual OSI/IP NE. A note with an arrow pointing to the third Dual OSI/IP NE states: 'This node will never initiate or terminate an autotunnel'. The diagram is labeled G.7712-Y.1703(19)\_FB.3.
+
+Figure B.3 – Topological requirements for IS-IS area dual nodes
+
+### B.4.7 Requirements for Level-1 and Level-2 nodes
+
+It is recommended that nodes that support both Level-1 and Level-2 routing and are present in an area in which these AE-DCFs are used provide one of the following functions (mutually exclusive):
+
+- To support all network layer protocols that are present in both the Level-1 and the Level-2 subdomain in which the node participates and support an AE-DCF; or
+- To support all network layer protocols that are present in both the Level-1 and the Level-2 subdomain in which the node participates and be either directly connected to, or connected through, continuous strings of other nodes that support all network layer protocols in the area, to a node that supports an AE-DCF and that supports all of the network layer protocols in the area.
+
+That is, dual signifies an Integrated IS-IS node that conforms to [IETF RFC 1195], but that does not support an AE-DCF:
+
+L2\_subdomain-dual\_L1/L2-non\_dual is safe (as per [IETF RFC 1195]);
+
+L2\_subdomain-dual\_L1/L2-dual-dual-non\_dual is safe (as per [IETF RFC 1195]);
+
+L2\_subdomain-dual\_L1/L2-AE-DCF-mixed\_network is safe;
+
+L2\_subdomain-dual\_L1/L2-dual-dual-AE-DCF-mixed\_network is safe;
+
+L2\_subdomain-dual\_L1/L2-non\_dual-dual is not safe (unless [IETF RFC 1195] restrictions are applied);
+
+L2\_subdomain-dual\_L1/L2-non\_dual-AE-DCF is not safe (unless [IETF RFC 1195] restrictions are applied).
+
+
+
+The diagram illustrates a network architecture with the following components and connections:
+
+- Access DCN:** A top oval containing a **Dual OSI/IP** node.
+- L1, L2 Subdomain:** A dashed oval containing three **Dual OSI/IP NE** nodes. The central node is connected to the **Dual OSI/IP** node in the Access DCN. A note with an arrow pointing to these nodes states: "These nodes will never initiate or terminate an autotunnel".
+- Level-1 area:** A large grey oval containing:
+ - Two **OSI NE** nodes connected to each other.
+ - A **Dual OSI/IP NE** node connected to one of the **OSI NE** nodes.
+ - Another **Dual OSI/IP NE** node connected to the **Dual OSI/IP NE** in the L1, L2 subdomain.
+ - An **IP NE** node connected to the second **Dual OSI/IP NE** node.
+ - A third **Dual OSI/IP NE** node connected to the **IP NE** node.
+- Potential autotunnels:** Indicated by dashed double-headed arrows between the **Dual OSI/IP NE** node (connected to the **OSI NE** nodes) and the **Dual OSI/IP NE** node (connected to the **IP NE** node), and between the **Dual OSI/IP NE** node (connected to the **IP NE** node) and the **Dual OSI/IP NE** node (connected to the **OSI NE** nodes).
+
+G.7712-Y.1703(19)\_FB.4
+
+Diagram illustrating network requirements for Level-1 and Level-2 nodes. It shows an Access DCN connected to a central Dual OSI/IP NE, which is part of an L1, L2 subdomain. This subdomain is connected to a Level-1 area containing various nodes (Dual OSI/IP NE, OSI NE, IP NE). Annotations indicate that nodes in the L1, L2 subdomain will not initiate/terminate autotunnels, and potential autotunnels are shown between Dual OSI/IP NEs in the Level-1 area.
+
+Figure B.4 – Requirements for Level-1, Level-2 nodes
+
+However, it is understood that a gateway NE, and therefore a L1, L2 router, may be an existing OSI-only device. In this case, it is possible to have IP and automatic encapsulation in the area by using the following method, with care:
+
+
+
+The diagram shows a network architecture with two main regions: **Access DCN** (top, white oval) and **Level-1 area = 10.3.x.x** (bottom, grey oval).
+ In the **Access DCN**, there are two **Dual OSI/IP** nodes, each associated with the IP prefix **10.3.0.0/16**.
+ Each **Dual OSI/IP** node is connected via a solid line to an **OSI NE** node labeled **L1, L2** located within the **Level-1 area**.
+ Inside the **Level-1 area**, there is a mesh of nodes: two **OSI NE** nodes, two **Dual OSI/IP NE** nodes, and two **IP NE** nodes. The **Dual OSI/IP NE** nodes are configured with a default route **0.0.0.0**.
+ Dashed lines represent **Manual RFC 3147 tunnel** connections between the **Dual OSI/IP** nodes in the **Access DCN** and the **Dual OSI/IP NE** nodes in the **Level-1 area**.
+ Annotations indicate that the **Static/default route not advertised if tunnel fails** for both the internal and external dual nodes.
+
+Diagram illustrating the use of an OSI-only device as a gateway within an Access DCN and Level-1 area.
+
+**Figure B.5 – Use of an OSI-only device as a gateway**
+
+One or more dual nodes in the area may be chosen as gateways for IP packets. These nodes will be configured to advertise a default route (0.0.0.0) into the area to attract all "out of area" IP traffic to them. These nodes will then forward all "out of area" traffic across a manually provisioned GRE tunnel, which passes through the Level-1, Level-2 OSI-only node to another dual node outside of the area.
+
+The dual node that is outside of the area must have a prefix manually provisioned into it to attract all IP traffic bound for the area to it and send it over the tunnel into the area. Optionally, a mechanism, such as an IP routing protocol, may be provisioned across the tunnel so that each end may see if the other is alive; however, if integrated IS-IS is used, then it must be a different routing instance to that used generally in the area, as it is effectively a different routing domain.
+
+If such a mechanism is used, then if the far end disappears, the dual node inside the area should stop advertising a default route, and the dual node outside of the area should stop advertising the prefix that represents the nodes in the area. In this way, redundant IP gateways can be provisioned.
+
+Note that [IETF RFC 1195] states that default routes should not be advertised within Level-1 LS-PDUs. This solution requires that this rule be broken. Normally a Level-1 [IETF RFC 1195] node would consider a Level-1, Level-2 node to be its default route. This solution requires that this behaviour be overwritten by receipt of a default route advertisement in a Level-1 LS-PDU. If this is not possible, then a work-around is for the IP gateway nodes to be configured with a selection of static routes that cover all possible "out of area" destinations that an IP stack in the area is likely to try to reach.
+
+### **B.4.8 Requirements for the Level-2 subdomain**
+
+It is acceptable to route all protocols present natively in the Level-2 subdomain, as per [IETF RFC 1195], in which case, none of the Level-2 nodes need to support an AE-DCF, but all of them must support all of the network layer protocols present.
+
+Alternatively, it is acceptable to use Level-2 nodes that support less than all of the network layer protocols present in the domain, in which case, the Level-2 dual or multilingual nodes will be required to support an AE-DCF so that packets may be automatically encapsulated in order to pass through such nodes.
+
+# **Annex C**
+
+(This annex has been intentionally left blank.)
+
+# Annex D
+
+## OOB OCh-O and OTSiG-O Protocol specification
+
+(This annex forms an integral part of this Recommendation.)
+
+## D.1 Overview
+
+The OOB OCh-O and optical tributary signal group – overhead (OTSiG-O) protocol supports an OCC carrying the status of OCh and optical tributary signal assembly (OTSiA) connections and signals over an OCN to systems that do not have direct access to the OSC. For deployment flexibility, the OCh-O and OTSiG-O protocol is defined independent of the specific DCN protocol in use (e.g., IPv4, IPv6). The details of how to adapt the characteristic information (CI) of this protocol to an IPv4 based DCN are provided at the end of the protocol definition.
+
+The OOB OCh-O and OTSiG-O protocol requires configuration of a protocol adjacency between two OCh-O or OTSiG-O connection points (OCh-O CP, OTSiG-O\_CP) located on the associated network equipment being connected by one or more optical physical section (OPS). Prior to both ends being configured, the status reporting behaviours driven by the protocol will not be operational. The adjacency is identified by using OPS as well as OCh identifiers and is carried by the DCN network.
+
+The status messages carried by the OOB OCh-O and OTSiG-O protocol provide unidirectional state information for one or more OCh and/or OTSiA connections and signals. The messages include identifiers of the OPS trail and one or more OCh-P and/or OTSiG link connections carried by that trail that identify the OCh-P and/or OTSiG link connections for which status is being reported. The receiving NE correlates the received status message with a local OCh-P CP or OTSiG CP utilizing the configured OPS adjacency.
+
+## D.2 PDU format
+
+The OOB OCh-O and OTSiG-O protocol is derived from the IETF's link management protocol (LMP) [b-IETF RFC 4204]. LMP uses a common format for the PDUs of all protocol messages as shown in Figure D.1.
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------|---|--------------|---|------------|---|---|---|-------|---|----------|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
+| 0 | 1 | | | | | | | | 2 | | | | | | | | 3 | | | | | | | | | | | | | | |
+| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 |
+| Vers | | (Reserved) | | | | | | Flags | | Msg Type | | | | | | | | | | | | | | | | | | | | | |
+| Msg Length | | | | (Reserved) | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| : | | Payload TLVs | | | | | | | | | | : | | | | | | | | | | | | | | | | | | | |
+
+Figure D.1 – OOB OCh-O and OTSiG-O protocol message PDU format
+
+Sub-protocols are used in the design of OOB OCh-O and OTSiG-O protocol. The value in the Msg Type field indicates which of the sub-protocols a PDU belongs to. TLV structure is used for the base PDU and payload TLV structures; in all cases the units of length are octets. The Msg Length provides the overall length of the PDU.
+
+Payload TLVs all follow the format shown in Figure D.2.
+
+
+
+Figure D.2: OOB OCh-O and OTSiG-O protocol payload TLV format diagram. It shows a 32-bit structure with four nibbles (0, 1, 2, 3) at the top. Below are 32 bits grouped into four nibbles. The first 8 bits (0-7) are labeled 'C-Type'. The next 8 bits (8-15) are labeled 'Class'. The next 8 bits (16-23) are labeled 'Length'. The final 8 bits (24-31) are labeled 'Value'.
+
+**Figure D.2 – OOB OCh-O and OTSiG-O protocol payload TLV format**
+
+The C-Type and Class fields are defined by each sub-protocol. The Length field provides the overall length of the TLV inclusive of the C-Type, Class and Length fields.
+
+The OOB OCh-O and OTSiG-O protocol shall exchange Hello PDUs and Status Reporting PDUs.
+
+### **D.2.1 Hello sub-Protocol**
+
+The Hello Sub-protocol uses a message type of 4. Inside the message are Hello Sequence and Validity TLVs. The format of these TLVs is as follows:
+
+#### **D.2.1.1 Hello sequence TLV**
+
+The C-type is 7, Class is 1 and Length is 12. The Value field is formatted as shown in Figure D.3.
+
+
+
+Figure D.3: OOB OCh-O and OTSiG-O protocol Hello sequence format diagram. It shows a 32-bit structure with four nibbles (0, 1, 2, 3) at the top. Below are 32 bits grouped into four nibbles. The first 16 bits (0-15) are labeled 'TxSeqNum'. The next 16 bits (16-31) are labeled 'RcvSeqNum'.
+
+**Figure D.3 – OOB OCh-O and OTSiG-O protocol Hello sequence format**
+
+The TxSeqNum is the sequence number of the Status Reporting message last transmitted by this adjacency endpoint. The RcvSeqNum is the sequence number of the Status Reporting message last received by this adjacency endpoint.
+
+Initially the RcvSeqNum=0 and the TxSeqNum=1. The RcvSeqNum will be replaced with the TxSeqNum received from the peer when the first Hello message is received.
+
+If a Hello message is received with a Hello sequence TLV containing a RcvSeqNum equal to 0, it is an indication that the peer endpoint has restarted and requires state information be sent for all OCh associated with this adjacency. The TxSeqNum may eventually exceed 232 . When this occurs, the TxSeqNum will wrap to the value of 1.
+
+#### **D.2.1.2 Hello validity TLV**
+
+The C-type is 240, Class is 1 and length is 8. The value is formatted as shown in Figure D.4.
+
+
+
+Figure D.4: OOB OCh-O and OTSiG-O protocol Hello validity format diagram. It shows a 32-bit structure with four nibbles (0, 1, 2, 3) at the top. Below are 32 bits grouped into four nibbles. The first 24 bits (0-23) are labeled 'Validity Period'. The last 8 bits (24-31) are empty.
+
+**Figure D.4 – OOB OCh-O and OTSiG-O protocol Hello validity format**
+
+The Validity Period field describes the amount of time (in ms) before another Hello must be received for the adjacency to be considered up. A transmitter should send subsequent Hello messages prior to
+
+the expiration of the validity period. The receiver of the Hello must update the expiration of the adjacency health timer upon receipt of a Hello PDU. If the validity period expires, the adjacency shall raise an alarm to the equipment management function (EMF). This alarm clears when the Hello protocol receives a Hello message from the peer starting a new validity period.
+
+### D.2.2 Status Reporting sub-protocol
+
+Status Reporting PDUs are issued for one or more OCh and/or OTSiA connections and signals as state changes occur or initial state requests are received. These PDUs use message type 17. The PDUs each contains a Message ID TLV, an OPS Trail Identification TLV, along with one or more identifiers for one or more OCh-P and/or OTSiG link connections and one OCh and OTSiA Status TLVs.
+
+It is possible for multiple OCh-P and/or OTSiG Link Connections that change state at the same time to be reported in a single status reporting PDU. In this case, all OCh-Ps and/or OTSiGs identified in the PDU will have the same status.
+
+The format of these TLVs is as follows:
+
+#### D.2.2.1 Message ID TLV
+
+The Message ID TLV contains the TxSeqNum for this specific status reporting PDU. The class number is 5 and the C-Type 1. The TLV length is 8. The format is shown in Figure D.5.
+
+
+
+Figure D.5: OOB OCh and OTSiA status reporting Message ID format. The diagram shows a 32-bit word structure with four nibbles (0, 1, 2, 3) at the top. Below each nibble are 16 bits (0-15). The 'Message\_Id' field is shown in the middle, spanning from bit 0 of nibble 1 to bit 15 of nibble 2.
+
+Figure D.5 – OOB OCh and OTSiA status reporting Message ID format
+
+#### D.2.2.2 OPS Trail Identification TLV
+
+The namespace used for OPS Trail identification is the TCP\_ID namespace used by G.7714 neighbour discovery. Control plane names are not used as it is not guaranteed that a control plane is active on this link.
+
+An OPS Trail Identification TLV has a C-type of 241 and Length of 16. The class uses the Format ID defined for each TCP-ID format in [ITU-T G.7714.1]. The Value field is formatted as shown in Figure D.6, Figure D.7 and Figure D.8 for TCP-ID Name, DCN Address format and DCN Name formats, respectively.
+
+
+
+Figure D.6: OOB OPS Trail and OCh-P and OTSiG Link Connection ID – TCP-ID Name format (Class=1). The diagram shows a 32-bit word structure with four nibbles (0, 1, 2, 3) at the top. Below each nibble are 16 bits (0-15). The 'Reserved' field is in nibble 0 (bits 0-15). The 'TCP Name' field is split across nibbles 1, 2, and 3, with the first part in nibble 1 (bits 0-15), the second part in nibble 2 (bits 0-15), and the third part in nibble 3 (bits 0-15).
+
+Figure D.6 – OOB OPS Trail and OCh-P and OTSiG Link Connection ID – TCP-ID Name format (Class=1)
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------|---------------------|--|--|--|--|--|--|--|--|----------------|---------------------|--|--|--|--|--|--|--|--|--|-----|--|
+| 0 | 1 | | | | | | | | | | 2 | | | | | | | | | | 3 | |
+| 0 1 2 3 4 5 6 7 8 9 | 0 1 2 3 4 5 6 7 8 9 | | | | | | | | | | 0 1 2 3 4 5 6 7 8 9 | | | | | | | | | | 0 1 | |
+| (Reserved) | | | | | | | | | | DCN Context ID | | | | | | | | | | | | |
+| DCN Address | | | | | | | | | | | | | | | | | | | | | | |
+| Local TCP-ID | | | | | | | | | | | | | | | | | | | | | | |
+
+**Figure D.7 – OOB OPS Trail and OCh-P and OTSiG Link Connection ID – DCN Address format (Class=2)**
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------|---------------------|--|--|--|--|--|--|--|--|----------|---------------------|--|--|--|--|--|--|--|--|--|-----|--|
+| 0 | 1 | | | | | | | | | | 2 | | | | | | | | | | 3 | |
+| 0 1 2 3 4 5 6 7 8 9 | 0 1 2 3 4 5 6 7 8 9 | | | | | | | | | | 0 1 2 3 4 5 6 7 8 9 | | | | | | | | | | 0 1 | |
+| (Reserved) | | | | | | | | | | DCN Name | | | | | | | | | | | | |
+| DCN Name | | | | | | | | | | | | | | | | | | | | | | |
+| Local TCP-ID Name | | | | | | | | | | | | | | | | | | | | | | |
+
+**Figure D.8 – OOB OPS Trail and OCh-P and OTSiG Link Connection ID – DCN Name format (Class=3)**
+
+#### **D.2.2.3 OCh-P and OTSiG Link Connection ID TLV**
+
+The OCh-P and OTSiG Link Connection ID TLV identifies an OCh-P or OTSiG instance carried by the OPS trail.
+
+The namespace used for OCh-P and OTSiG Link connection ID is the TCP-ID namespace used by [ITU-T G.7714.1] neighbour discovery. Control plane names are not used as it is not guaranteed that a control plane is active on this link.
+
+The format for the OCh-P and OTSiG Link Connection ID TLV is the same as the format for the OPS Trail ID TLV.
+
+An OCh-P and OTSiG Link Connection ID TLV has a C-type of 244 and length of 16. The class uses the Format ID defined for each TCP-ID format in [ITU-T G.7714.1]. The Value field for the OCh-P and OTSiG Link Connection ID TLV is formatted as shown in Figure D.6, Figure D.7, and Figure D.8 for TCP-ID Name, DCN Address and DCN Name format, respectively.
+
+Multiple Link Connection Identification TLVs may be carried in the same status update message. In this case, all OCh-P and/or OTSiG link connections in the message will have the same status.
+
+#### **D.2.2.4 OCh and OTSiG Status TLV**
+
+The OCh and OTSiG-O Status TLV is a bit vector providing status indication for one or more OCh-P and/or OTSiG link connections identified in the status reporting PDU. The Class number is 242 and the C-Type is 1. The TLV Length is 8. The format is shown in Figure D.9.
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------|---------------------|--|--|--|--|--|--|--|--|--|---------------------|--|--|--|--|--|--|--|--|--|-----|--|
+| 0 | 1 | | | | | | | | | | 2 | | | | | | | | | | 3 | |
+| 0 1 2 3 4 5 6 7 8 9 | 0 1 2 3 4 5 6 7 8 9 | | | | | | | | | | 0 1 2 3 4 5 6 7 8 9 | | | | | | | | | | 0 1 | |
+| Channel Status Flags | | | | | | | | | | | | | | | | | | | | | | |
+
+**Figure D.9 – OCh and OTSiG Status TLV format**
+
+The flags in the Channel Status Flags field are defined as follows:
+
+0x0000.0001: FDI-P
+
+0x0000.0002: FDI-O
+
+0x0000.0004: OCI
+
+All remaining flags are reserved. Reserved flags are transmitted as zero (0) and ignored on reception.
+
+### D.2.3 Protocol adaptation to IPv4 DCN
+
+The OOB OCh-O and OTSiG-O protocol is carried over IPv4 networks using unicast user datagram protocol (UDP) messages.
+
+The OOB OCh-O and OTSiG-O PDUs are carried as payload within adaptation frames with one PDU in each frame. The adaptation uses the format in Figure D.10.
+
+
+
+```
+
+ 0 1 2 3
+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ | ITU-T Enterprise Identifier (xxxx) |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ | ITU-T Protocol Number (yyyy) |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ : Payload :
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+
+```
+
+Figure D.10 – OOB OCh-O and OTSiG-O protocol UDP/IPv4 frame format diagram showing a 4-byte header (ITU-T Enterprise Identifier and ITU-T Protocol Number) followed by a variable-length payload.
+
+**Figure D.10 – OOB OCh-O and OTSiG-O protocol UDP/IPv4 frame format**
+
+While the OOB OCh-O and OTSiG-O protocol does not have a byte-count limit on a PDU, they are to be carried within a single IPv4 PDU to the destination to avoid problems with complete message loss due to message fragmentation and loss of fragments. For this reason, the IPv4 DoNotFragment bit should be set and PDUs should be less than 1500 bytes (inclusive of IPv4, UDP and frame header overheads).
+
+### D.2.4 OTSiG-O TTI TLV
+
+The TTI TLV is a string providing the TTI associated with the end-to-end OTSiA being reported. The class number is 243, the C-Type is 1 and the length is 68. The format is shown in Figure D.11.
+
+
+
+The diagram shows the TTI format for OOB OTSiG Status Reporting. It consists of four frames, labeled 0, 1, 2, and 3, each containing 10 bits (0-9). The fields are distributed as follows:
+
+- Frame 0:** Bits 0-4 are SAPI, bits 5-9 are DAPI.
+- Frame 1:** Bits 0-4 are SAPI, bits 5-9 are DAPI.
+- Frame 2:** Bits 0-4 are SAPI, bits 5-9 are DAPI.
+- Frame 3:** Bits 0-4 are Operator Specific, bits 5-9 are Operator Specific.
+
+Timing diagram for OOB OTSiG Status Reporting protocol TTI format. It shows four frames (0, 1, 2, 3) with 10 bits each. The diagram illustrates the placement of SAPI, DAPI, and Operator Specific fields across the frames. SAPI is present in frames 0, 1, and 2. DAPI is present in frames 0, 1, and 2. Operator Specific fields are present in all four frames, with varying lengths and positions.
+
+**Figure D.11 – OOB OTSiG Status Reporting protocol TTI format**
+
+### **D.2.5 OTSiG-O BDI TLV**
+
+The backward defect indication (BDI) TLV is a string providing the BDI-P and BDI-O associated with the end-to-end OTSiA trail being reported. The class number is 245, the C-Type is 1 and the length is 8. The format is shown in Figure D.12.
+
+
+
+The diagram shows the OTSiA Trail Status TLV format. It consists of four frames, labeled 0, 1, 2, and 3, each containing 10 bits (0-9). The fields are distributed as follows:
+
+- Frame 0:** Bits 0-4 are Trail Status Flags, bits 5-9 are Trail Status Flags.
+- Frame 1:** Bits 0-4 are Trail Status Flags, bits 5-9 are Trail Status Flags.
+- Frame 2:** Bits 0-4 are Trail Status Flags, bits 5-9 are Trail Status Flags.
+- Frame 3:** Bits 0-4 are Trail Status Flags, bits 5-9 are Trail Status Flags.
+
+Timing diagram for OTSiA Trail Status TLV format. It shows four frames (0, 1, 2, 3) with 10 bits each. The diagram illustrates the placement of Trail Status Flags across the frames. Trail Status Flags are present in all four frames, with varying lengths and positions.
+
+**Figure D.12 – OTSiA Trail Status TLV format**
+
+The flags in the Trail Status Flags field are defined as follows:
+
+0x0000.0001: BDI-P
+
+0x0000.0002: BDI-O
+
+All remaining flags are reserved. Reserved flags are transmitted as zero (0) and ignored on reception.
+
+### D.2.6 OTSi TSI TLV
+
+The optical tributary signal (OTSi) TSI TLV is providing the OTSi TSI associated with one of the OTSi instances within the end-to-end OTSiG being reported. An OTSiG consisting of multiple OTSi will have multiple OTSi TLVs, one per OTSi. An OTSi TSI TLV contains a [ITU-T G.698.2] application code plus nominal central frequency. The class number is 246, the C-Type is 1 and the length is 16. The format is shown in Figure D.13. This format is based on the application code format as specified in [IETF RFC 7581] and wavelength ID format as specified in Appendix V of [ITU-T G.697].
+
+
+
+```
+
+ 0 1 2 3
+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ |B| D |S| c | W | y | t | z | v | F |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ | Reserved |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ | g | c | n | m |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+
+```
+
+Figure D.13 – OTSi TSI TLV format diagram showing a 16-byte structure with fields B, D, S, c, W, y, t, z, v, F, Reserved, g, c, n, m.
+
+Figure D.13 – OTSi TSI TLV format
+
+## D.3 OCh\_O and OTSiG-O communication channel adaptation function
+
+### D.3.1 OCh\_O communication channel adaptation function (OCC/OCh-O\_A)
+
+The OCC/OCh-O\_A function aggregates/de-aggregates OCh\_CI\_OH.
+
+The specification of this function is for further study.
+
+### D.3.2 OCh\_O and OTSiG-O communication channel adaptation function (OCC/OCh|OTSiG-O\_A)
+
+The OCC/OCh|OTSiG-O\_A function aggregates/de-aggregates OCh\_CI\_OH and OTSiG\_CI\_OH.
+
+The specification of this function is for further study.
+
+## D.4 OCh\_O [and OTSiG-O] communication channel termination function (OCC\_TT)
+
+The OCC\_TT functions are responsible for the end-to-end supervision of the OCC trail.
+
+The specification of this function is for further study.
+
+# Appendix I
+
+## Constraints of the interworking functions in DCN
+
+(This appendix does not form an integral part of this Recommendation.)
+
+
+
+Figure I.1 – Interworking scenarios. A complex network diagram showing three main routing domains: IntISIS (left), OSPF (middle), and IntISIS (right). The left IntISIS domain contains nodes Y, R, G, S, Z, F, and A. The OSPF domain contains nodes P, M, C, Q, N, and X. The right IntISIS domain contains nodes K, T, L, V, W, and 6. Various nodes are connected to external systems: node 1 (OSI NE), node 2 (OSI NE), node 3 (S2 IP), node 4 (OSI NE), node 5 (OSI NE), node 6 (OSI NE), S4 IP, S5 OSI, S6 IP, S1 OSI, and S3 OSI. A central node B (Dual OSI/IP NE) connects the left IntISIS domain to the OSPF domain. Node A (OSI NE) connects the left IntISIS domain to the right IntISIS domain. Node X (Dual OSI/IP NE) connects the OSPF domain to the right IntISIS domain. Node B (Dual OSI/IP NE) also connects to node 3 (S2 IP). Node A (OSI NE) also connects to node 4 (OSI NE). Node 5 (OSI NE) connects to node 6 (OSI NE). Node 6 (OSI NE) connects to node 5 (OSI NE). Node 5 (OSI NE) connects to node 4 (OSI NE). Node 4 (OSI NE) connects to node 3 (S2 IP). Node 3 (S2 IP) connects to node 2 (OSI NE). Node 2 (OSI NE) connects to node 1 (OSI NE). Node 1 (OSI NE) connects to node 6 (OSI NE). Node 6 (OSI NE) connects to node 5 (OSI NE). Node 5 (OSI NE) connects to node 4 (OSI NE). Node 4 (OSI NE) connects to node 3 (S2 IP). Node 3 (S2 IP) connects to node 2 (OSI NE). Node 2 (OSI NE) connects to node 1 (OSI NE). Node 1 (OSI NE) connects to node 6 (OSI NE).
+
+Figure I.1 – Interworking scenarios
+
+## I.1 General assumptions
+
+DCN covers the IWF for Layer 2-3 of the IP-OSI stacks. Interworking mechanisms that apply to other layers are out of the scope of this Recommendation (i.e., mediation).
+
+See clause 7.1.7 for a definition of interworking.
+
+Tunnels are based on RFCs.
+
+The IP-only NEs support IP routing and may contain redistribution between integrated IS-IS and OSPF.
+
+## I.2 Common to all scenarios
+
+Dynamic routing is accomplished through the use of route redistribution of IP address information between OSPF and IS-IS NEs. Route redistribution is performed on the OSPF nodes between the pairs: (R,P), (S,C), (M,K), (N,L).
+
+### I.2.1 Scenario 1: OSI-based management system connected to node A
+
+There must be at least one tunnel configured from B to one or more of Y or Z.
+
+There must be a tunnel configured from B to X.
+
+There must be a tunnel configured from B to F.
+
+There must be at least one tunnel configured from B to one or more of W, V or T.
+
+The above tunnels will probably have IS-IS running across them (inside the tunnel); however, inter-domain routing techniques is also a possibility. Under some conditions, some tunnels could become congested as a result of routing choices.
+
+An OSI-based management system now has CLNS connectivity to any OSI-only or dual stack NE in the network, but does not have connectivity with IP-only NEs. Although an OSI-based manager will be able to send CLNS packets to a dual stack NE, it will not be able to manage it unless it is OSI manageable.
+
+### **I.2.2 Scenario 2: IP-based management systems connected to node B**
+
+In this particular network, IP traffic can be forwarded from B to all IP NEs without requiring tunnels. OSPF NEs P, C, M, and N must support redistribution of IP routes into integrated IS-IS. Filters will have to be configured on OSPF nodes P, C, M, and N in order to stop routing loops from forming.
+
+An IP-based management system now has IP connectivity to any IP-only or dual stack NE in the network but does not have connectivity with OSI-only NEs. Although an IP-based manager will be able to send IP packets to a dual stack NE, it will not be able to manage it unless it is IP manageable.
+
+### **I.2.3 Scenario 3: OSI-based management systems connected to node C**
+
+NE C cannot provide OSI connectivity, and so CLNS packets cannot be forwarded; therefore, an OSI-based management system cannot function at this location.
+
+### **I.2.4 Scenario 4: IP-based management systems connected to node E**
+
+NE E cannot provide IP connectivity, and so IP packets cannot be forwarded; therefore, an IP-based management system cannot function at this location.
+
+### **I.2.5 Scenario 5: OSI-based management systems connected to node F**
+
+CLNS traffic can pass through NE F to OSI network 2 without requiring tunnels as NE F can forward CLNS packets natively.
+
+There must be a tunnel configured from F to B.
+
+There must be at least one tunnel configured from F to one or more of Z or Y.
+
+There must be a tunnel configured from F to X.
+
+There must be at least one tunnel configured from F to one or more of W, V or T.
+
+The above tunnels will probably have IS-IS running across them (inside the tunnel); however, inter-domain routing techniques are also a possibility. Under some conditions, some tunnels could become congested as a result of routing choices.
+
+An OSI-based management system now has CLNS connectivity to any OSI-only or dual stack NE in the network but does not have connectivity with IP-only NEs. Although an OSI-based manager will be able to send CLNS packets to a dual stack NE, it will not be able to manage it unless it is OSI manageable.
+
+### **I.2.6 Scenario 6: IP-based management systems connected to node G**
+
+In this particular network, IP traffic can be forwarded from G to all IP NEs without requiring tunnels. OSPF NEs P, C, M, and N must support redistribution of IP routes into integrated IS-IS. Filters will have to be configured on each OSPF nodes P, C, M, and N in order to stop routing loops from forming.
+
+An IP-based management system now has IP connectivity to any IP-only or dual stack NE in the network, but does not have connectivity with OSI-only NEs. Although an IP-based manager will be able to send IP packets to a dual stack NE, it will not be able to manage it unless it is IP manageable.
+
+# Appendix II
+
+## Example implementation of automatic encapsulation
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## II.1 Introduction
+
+This appendix is not a requirement but gives brief example details on how a node may be implemented with respect to one aspect of the feature specified in this Recommendation.
+
+The simplest way (but not the only way) for a node to calculate the next node along the shortest path to the final destination of a packet that can unencapsulate is to modify the SPF algorithm to achieve this.
+
+The algorithm can be modified to find the next node along the shortest path to the destination that can accept IP over OSI encapsulated traffic, and the next node along the shortest path to the destination that can accept OSI over IP encapsulated traffic. Note that these two may be the same node, or may be two separate nodes. A modified Dijkstra algorithm is provided below that achieves this.
+
+This additional process only needs to happen when the next hop does not support the network layer protocol of the type that corresponds to the destination address for that path. If the next hop does support that type of network layer protocol (as specified in the "protocols supported" TLV present in IS-IS Hello PDUs received from that node), then packets to that destination may simply be forwarded natively and forgotten, and so the search for a node along the path that can unencapsulate is not necessary.
+
+The algorithm must then identify an IP address for this next unencapsulation node if the destination of the path is an OSI end system and must then identify an OSI address for this next unencapsulation node if the destination of the PATH is an IP address.
+
+Failure to find an IP address for this next unencapsulation node indicates a configuration error in that node (no IP address); this may optionally result in an error message being sent to the network administrator. Packet loss will result if a CLNS packet requires tunnelling to that node over IP as, without an IP destination address, encapsulation may not be possible and the packet will be discarded instead.
+
+Failure to find a node that can unencapsulate indicates a network design error, more specifically, a failure to conform to the topological restrictions stated in this Recommendation. This should result in a "destination unreachable" error report.
+
+For each IP destination that requires encapsulation to get beyond the next hop, the node can then put a marker in the IP forwarding table indicating the OSI destination address that must be used to encapsulate all IP packets destined for that address.
+
+For each OSI destination that requires encapsulation to get beyond the next hop, the node can then put a marker in the OSI forwarding table indicating the IP destination address that must be used to encapsulate all OSI packets destined for that address.
+
+A node that supports IPv4, IPv6 and OSI may find two addresses (for example, an IPv4 address and an IPv6 address) that could be used to encapsulate. In this case, it may choose either as long as it results in a packet that is of a network layer protocol type that the next hop supports (as specified in the "protocols supported" TLV present in IS-IS Hello PDUs received from that node).
+
+## II.2 Updates to Dijkstra's algorithm
+
+The following clauses contain the full Dijkstra's algorithm including extensions to support auto-tunnelling. It is based on the algorithm as specified in [IETF RFC 1195]. The algorithm shown is suitable for a dual IPv4 and CLNS automatically-encapsulating node. Changes to this algorithm are shown in ***Bold Italic***.
+
+The algorithm produces a PATHS database containing, for each destination, the identity of the first node from S to N capable of unencapsulating IP over OSI, and the identity of the first node from S to N capable of unencapsulating OSI over IP.
+
+For each IP destination, the first node from S to N capable of unencapsulating IP over OSI may have its OSI address loaded into the IP forwarding table as the destination address to be used in any CLNP packet used to encapsulate IP over OSI, if the next hop does not support IP.
+
+For each OSI end system, the first node from S to N capable of unencapsulating OSI over IP may have one of its IP addresses loaded into the OSI forwarding table as the destination address to be used in any IP packet used to encapsulate OSI over IP, if the next hop does not support OSI.
+
+### II.2.1 Changes to database
+
+The PATHS and TENTS database should be updated to contain an extension to the {Adj(N)}, element of the triple. The adjacency N element will contain two corresponding dual protocol support (IDP(N)-ODP(N)) entries which will represent the system ID of the first dual router on the path from S to N capable of de-encapsulating IP over OSI tunnelled packets (IDP(N)) and the system ID of the first dual router on that path from S to N capable of de-encapsulating OSI over IP tunnelled packets (ODP(N)). If no \*DP(N) router exists on the PATH, then this value will be set to zero. If multiple Adj(N) entries exist in either the TENTS or the PATHS database, then each adjacency will have corresponding \*DP(N) entries. Thus, each triple will take the format .
+
+If the value of IDP(N) is set to 0, then this means that no dual router exists on the path to the destination capable of de-encapsulating and encapsulating IP over OSI packets.
+
+If the value of ODP(N) is set to 0, then this means that no dual router exists on the path to the destination capable of de-encapsulating and encapsulating OSI over IP packets.
+
+### II.2.2 Changes to algorithm
+
+The SPF algorithm specified in section C.1.4 of [IETF RFC 1195] is amended to appear as follows:
+
+Step 0: Initialize TENT and PATHS to empty. Initialize tentlength to [internalmetric=0, externalmetric=0].
+
+(tentlength is the pathlength of elements in TENT that we are examining.)
+
+- 1) Add to PATHS, where W is a special value indicating traffic to SELF is passed up to internal processes (rather than forwarded).
+- 2) Now pre-load TENT with the local adjacency database (each entry made to TENT must be marked as being either an End System, or a router, to enable the check at the end of Step 2 to be made correctly - Note that each local IP reachability entry is included as an adjacency, and is marked as being an End System). For each adjacency Adj(N) (including level 1 OSI Manual Adjacencies, or Level 2 OSI enabled reachable addresses, and IP reachability entries) on enabled circuits, to system N of SELF in state "Up" compute:
+
+d(N) = cost of the parent circuit of the adjacency (N), obtained from metric.k , where k = one of {default metric, delay metric, monetary metric, error metric}
+
+Adj(N) - **IDP(N)** - **ODP(N)** = the adjacency number of the adjacency to N, *the SID of the next-hop router along the path to the neighbour capable of de-encapsulating IP over OSI packets, and the SID of the next-hop router along the path to the neighbour capable of de-encapsulating OSI over IP packets.*
+
+*In this case, i.e., during initialization, both DP values will be set to 0*
+
+- 3) If a triple $\langle N, x, \{ \text{Adj}(M) - \mathbf{IDP}(N) - \mathbf{ODP}(N) \} \rangle$ is in TENT, then:
+
+If $x = d(N)$ , then $\{ \text{Adj}(M) - \mathbf{IDP}(N) - \mathbf{ODP}(N) \} \leftarrow \{ \text{Adj}(M) - \mathbf{IDP}(M) - \mathbf{ODP}(M) \} \cup \{ \text{Adj}(N) - \mathbf{IDP}(N) - \mathbf{ODP}(N) \}$ .
+
+- 4) If N is a router or an OSI End System entry, and there are now more adjacencies in $\{ \text{Adj}(M) \}$ than maximumPathSplits, then remove excess adjacencies as described in Clause 7.2.7 of ISO/IEC 10589. If N is an IP Reachability Entry, then excess adjacencies may be removed as desired. This will not effect the correctness of routing, but may eliminate the determinism for IP routes (i.e., IP packets still follow optimal routes within an area, but where multiple equally good routes exist, will not necessarily follow precisely the route that any one particular router would have anticipated).
+
+- 5) If $x < d(N)$ , do nothing.
+
+- 6) If $x > d(N)$ , remove $\langle N, x, \{ \text{Adj}(M) - \mathbf{IDP}(M) - \mathbf{ODP}(M) \} \rangle$ from TENT and add the triple $\langle N, d(N), \{ \text{Adj}(N) - \mathbf{IDP}(N) - \mathbf{ODP}(N) \} \rangle$ .
+
+- 7) If no triple $\langle N, x, \{ \text{Adj}(M) - \mathbf{IDP}(M) - \mathbf{ODP}(M) \} \rangle$ is in TENT, then add $\langle N, d(N), \{ \text{Adj}(N) - \mathbf{IDP}(N) - \mathbf{ODP}(N) \} \rangle$ to TENT.
+
+- 8) Now add systems to which the local router does not have adjacencies, but which are mentioned in neighbouring pseudonode LSPs. The adjacency for such systems is set to that of the designated router. Note that this does not include IP reachability entries from neighbouring pseudonode LSPs. In particular, the pseudonode LSPs do not include IP reachability entries.
+
+- 9) For all broadcast circuits in state "On", find the pseudonode LSP for that circuit (specifically, the LSP with number zero and with the first 7 octets of LSPID equal to LnCircuitID for that circuit, where n is 1 (for Level 1 routing) or 2 (Level 2 routing)). If it is present, for all the neighbours N reported in all the LSPs of this pseudonode which do not exist in TENT add an entry $\langle N, d(N), \{ \text{Adj}(N) - \mathbf{IDP}(N) - \mathbf{ODP}(N) \} \rangle$ to TENT, where:
+
+$d(N)$ = metric.k of the circuit.
+
+$\text{Adj}(N)$ = the adjacency number of the adjacency to the DR.
+
+- 10) Go to Step 2.
+
+Step 1: Examine the zeroeth link state PDU of P, the system just placed on PATHS (i.e., the LSP with the same first 7 octets of LSPID as P, and LSP number zero).
+
+- 1) If this LSP is present and the "Infinite Hippity Cost" bit is clear For each $\text{Adj}(\ast) - \text{IDP}(\ast) - \text{ODP}(\ast)$ pair in the PATHS database for P. If this is not a pseudo-node LSP and if $\text{IDP}(\ast)$ is equal to zero then check the unencapsulation capability field of the LSP, if it supports IP over OSI then set the $\text{IDP}(P)$ value for this adjacency to be the system ID of P. if $\text{ODP}(\ast)$ is equal to zero then check the unencapsulation capability field of the LSP, if it supports OSI over IP then set the $\text{IDP}(P)$ value for this adjacency to be the system ID of P
+- 2) If this LSP is present, and the "Infinite Hippity Cost" bit is clear, then for each LSP of P (i.e., all LSPs with the same first 7 octets of LSPID and P, irrespective of the value of SP number) compute:
+
+$\text{dist}(P, N) = d(P) + \text{metric.k}(P, N)$
+
+for each neighbour N (both End System and router) of the system P. If the "Infinite Hippity Cost" bit is set, only consider the End System neighbours of the system P.
+
+Note that the End Systems neighbours of the system P includes IP reachable address entries included in the LSPs from system P. Here, $d(P)$ is the second element of the triple
+
+$\langle P, d(P), \{ \text{Adj}(P) - \mathbf{IDP}(P) - \mathbf{ODP}(P) \} \rangle$
+
+and $\text{metric.k}(P, N)$ is the cost of the link from P to N as reported in P's link state PDU.
+
+3) If $\text{dist}(P, N) > \text{MaxPathMetric}$ , then do nothing.
+
+4) If $\langle N, d(N), \{ \text{Adj}(N) - \mathbf{IDP}(N) - \mathbf{ODP}(N) \} \rangle$ is in PATHS, then do nothing.
+
+NOTE - $d(N)$ must be less than $\text{dist}(P, N)$ , or else N would not have been put into PATHS. An additional sanity check may be done here to ensure that $d(N)$ is in fact less than $\text{dist}(P, N)$
+
+5) If a triple $\langle N, x, \{ \text{Adj}(N) - \mathbf{IDP}(N) - \mathbf{ODP}(N) \} \rangle$ is in TENT, then:
+
+a) If $x = \text{dist}(P, N)$ , then $\{ \text{Adj}(N), \mathbf{IDP}(N) - \mathbf{ODP}(N) \} \leftarrow \{ \text{Adj}(N) - \mathbf{IDP}(N) - \mathbf{ODP}(N) \} \cup \{ \text{Adj}(P) - \mathbf{IDP}(P) - \mathbf{ODP}(P) \}$ .
+
+*Note that even if the value of Adj(N) is equal to the value Adj(P) but the corresponding values of either IDP(P) or ODP(P) and IDP(N) or ODP(N) are different then this should be treated as a different adjacency and will represent a different path to the destination.*
+
+b) If N is a router or an OSI end system, and there are now more adjacencies in $\{ \text{Adj}(N) \}$ than maximumPath Splits, then remove excess adjacencies, as described in clause 7.2.7 of ISO/IEC 10589. For IP Reachability Entries, excess adjacencies may be removed as desired. This will not effect the correctness of routing, but may eliminate the determinism for IP routes (i.e., IP packets will still follow optimal routes within an area, but where multiple equally good routes exist, will not necessarily follow precisely the route that any one particular router would have anticipated).
+
+c) if $x < \text{dist}(P, N)$ , do nothing.
+
+d) if $x > \text{dist}(P, N)$ , remove $\langle N, x, \{ \text{Adj}(N) - \mathbf{IDP}(N) - \mathbf{ODP}(N) \} \rangle$ from TENT, and add $\langle N, \text{dist}(P, N), \{ \text{Adj}(P) - \mathbf{IDP}(P) - \mathbf{ODP}(P) \} \rangle$
+
+6) if no triple $\langle N, x, \{ \text{Adj}(N) \} \rangle$ is in TENT, then add $\langle N, \text{dist}(P, N), \{ \text{Adj}(P) \} \rangle$ to TENT.
+
+Step 2: If TENT is empty, stop. Else:
+
+1) Find the element $\langle P, x, \{ \text{Adj}(P) - \mathbf{IDP}(P) - \mathbf{ODP}(P) \} \rangle$ , with minimal x as follows:
+
+a) If an element $\langle *, \text{tentlength}, * \rangle$ remains in TENT in the list for tentlength, choose that element. If there are more than one elements in the list for tentlength, choose one of the elements (if any) for a system which is a pseudonode in preference to one for a non-pseudonode. If there are no more elements in the list for tentlength, increment tentlength and repeat Step 2.
+
+b) Remove $\langle P, \text{tentlength}, \{ \text{Adj}(P) - \mathbf{IDP}(P) - \mathbf{ODP}(P) \} \rangle$ from TENT.
+
+c) Add $\langle P, d(P), \{ \text{Adj}(P) - \mathbf{IDP}(P) - \mathbf{ODP}(P) \} \rangle$ to PATHS.
+
+d) If this is the Level 2 Decision Process running, and the system just added to PATHS listed itself as Partition Designated Level 2 Intermediate system, then additionally add $\langle \text{AREA.P}, d(P), \{ \text{Adj}(P) \} \rangle$ to PATHS, where AREA.P is the Network Entity Title of the other end of the Virtual Link, obtained by taking the first AREA listed in P's LSP and appending P's ID.
+
+- e) If the system just added to PATHS was an end system, go to step 2. Else go to Step 1.
+
+NOTE - In the Level 2 context, the "End Systems" are the set of Reachable Address Prefixes (for OSI), the set of Area Addresses with zero cost (again, for OSI), plus the set of IP reachability entries (including both internal and external).
+
+# Appendix III
+
+## Commissioning guide for SDH NEs in dual [IETF RFC 1195] environment and impact of automatic encapsulation option
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## III.1 Introduction
+
+This appendix provides guidance on installing Integrated IS-IS nodes in a dual IPv4 and OSI network, and on how to use the optional automatic encapsulation feature described in Annex B.
+
+## III.2 Integrated IS-IS without automatic encapsulation
+
+### III.2.1 Introduction and rules of [IETF RFC 1195]
+
+Integrated IS-IS, as specified in [IETF RFC 1195], was originally written as a dual routing protocol. Specifically, it was written to be able to route both IPv4 and CLNP using a single SPF calculation, a single set of metrics for both IP and CLNP and a single set of Hellos and LS-PDUs.
+
+More specifically, integrated IS-IS routers, conforming to [IETF RFC 1195], calculate shortest paths across a Level-1 area or Level-2 subdomain without considering whether any candidate router can actually forward a specific type of packet.
+
+This is clearly stated in [IETF RFC 1195] in section 3.10:
+
+— "The Dijkstra computation does not take into consideration whether a router is IP-only, OSI-only, or dual. The topological restrictions specified in section 1.4 ensure that IP packets will only be sent via IP-capable routers, and OSI packets will only be sent via OSI-capable routers."
+
+With integrated IS-IS, a router is just a router. The assumption is that any router in the network can handle any type of packet that is thrown at it.
+
+Therefore, integrated IS-IS routers calculate routes, and forward packets based on this assumption, and it is the responsibility of an operator to make sure that the assumption is actually true.
+
+Thus, there are the topological restrictions of [IETF RFC 1195]. Failure to enforce the topological restrictions of [IETF RFC 1195] may result in packet loss, as packets disappear into the black-hole of a router that simply discards packets that it cannot forward, as it does not support them.
+
+In a simple single Level-1 area network, the rules are quite simple. These are:
+
+- 1) If IPv4 packets are to be forwarded in an area, then all of the routers in the area must be able to forward IPv4 packets;
+- 2) If CLNP packets are to be forwarded in an area, then all of the routers in the area must be able to forward CLNP packets;
+- 3) If both IPv4 and CLNP packets are to be forwarded in an area, then all of the routers in the area must be dual, i.e., able to forward both.
+
+Thus, it is fairly easy to classify IS-IS Level-1 areas into the classes "OSI-only area", "IP-only area", and "Dual area". This is shown in Figure III.1.
+
+
+
+**Area 0001**
+**IP-only area**
+
+Within this area, all nodes must be able to forward IPv4.
+CLNP packets will be discarded.
+Dual nodes are allowed but must be IP managed.
+
+**Area 0002**
+**Dual area**
+
+Within this area, all nodes must be able to forward IPv4 and CLNP.
+Nodes can be IP managed or CLNS managed.
+
+**Area 0003**
+**OSI-only area**
+
+Within this area, all nodes must be able to forward CLNP.
+IP packets will be discarded.
+Dual nodes are allowed but must be CLNS managed.
+
+G.7712-Y.1703(19)\_FIII.1
+
+Figure III.1: Classification of IS-IS Level-1 areas. It shows three circular diagrams representing different area types: Area 0001 (IP-only area), Area 0002 (Dual area), and Area 0003 (OSI-only area). Each area contains a set of nodes (IP NE, Dual IP/OSI NE, OSI NE) and specific rules for packet forwarding and management. Area 0001 contains four nodes: two IP NE and two Dual IP/OSI NE. Area 0002 contains three nodes: two Dual IP/OSI NE and one Dual IP/OSI NE. Area 0003 contains four nodes: two OSI NE and two Dual IP/OSI NE. Below each area diagram are text descriptions of the rules for that area type.
+
+**Figure III.1 – Classification of IS-IS Level-1 areas**
+
+### **III.2.2 Level-2 subdomain**
+
+If a larger network is needed, requiring Level-2 routing, then the Level-2 subdomain forwards packets between the Level-1 areas, and thus must support all of the types of packets present in all of those Level-1 area. The rules for the Level-2 subdomain are:
+
+- 1) If IPv4 packets are forwarded in any of the areas (IP-only or dual areas), then all of the routers in the Level-2 subdomain must be able to forward IPv4.
+- 2) If CLNP packets are forwarded in any of the areas (OSI-only or dual areas), then all of the routers in the Level-2 subdomain must be able to forward CLNP.
+
+Therefore, if any of the areas is dual, or if both OSI-only and IP-only areas exist, then the routers in the Level-2 subdomain must be dual. This is illustrated in Figure III.2.
+
+
+
+**Level-2 subdomain**
+
+**Area 0001**
+**IP-only area**
+
+**Area 0002**
+**Dual area**
+
+**Area 0003**
+**OSI-only area**
+
+G.7712-Y.1703(19)\_FIII.2
+
+Figure III.2: Level-2 subdomain. This diagram shows three Level-1 areas (Area 0001, Area 0002, Area 0003) connected to a central Level-2 subdomain. The Level-2 subdomain is represented by a large oval containing four Dual IP/OSI NE nodes. Arrows labeled 'L1, L2' point from the central oval to the Dual IP/OSI NE nodes in Area 0001 and Area 0003. Arrows labeled 'L2' point from the central oval to the Dual IP/OSI NE nodes in Area 0002. Area 0001 (IP-only area) contains four nodes: two IP NE and two Dual IP/OSI NE. Area 0002 (Dual area) contains three nodes: two Dual IP/OSI NE and one Dual IP/OSI NE. Area 0003 (OSI-only area) contains four nodes: two OSI NE and two Dual IP/OSI NE.
+
+**Figure III.2 – Level-2 subdomain**
+
+### III.2.3 Level-2 subdomain with external routers running integrated IS-IS
+
+Many operators currently run Level-1 IS-IS routing in their OSI-only SDH NEs, and then link up multiple areas using Level-2 IS-IS routing in an external router network.
+
+If an operator wishes to use a similar model for a dual network, then they can run Level-1 integrated IS-IS in each area, and Level-2 integrated IS-IS in an external router network. This gives a very similar network to the previous one, as shown in Figure III.3
+
+
+
+The diagram illustrates a network architecture with a central 'Level-2 subdomain' represented by a large horizontal oval. Above this oval, five labels indicate the IS-IS levels supported by the routers below: 'L1, L2', 'L2', 'L1, L2', 'L2', and 'L1, L2'. Below these labels are five boxes representing routers: 'Dual IP/OSI router', 'Dual IP/OSI router', 'Dual IP/OSI router', 'Dual IP/OSI router', and 'Dual IP/OSI router'. The central 'Dual IP/OSI router' is connected to three circular areas: 'Area 0001 IP-only area', 'Area 0002 Dual area', and 'Area 0003 OSI-only area'. Each area contains a set of Network Elements (NEs): 'Area 0001' has four 'IP NE' boxes; 'Area 0002' has two 'Dual IP/OSI NE' boxes and one 'Dual IP/OSI NE' box; 'Area 0003' has two 'OSI NE' boxes and one 'Dual IP/OSI NE' box. All NEs are connected to the central 'Dual IP/OSI router' in the Level-2 subdomain.
+
+Diagram of Level-2 subdomain with external routers running integrated IS-IS
+
+G.7712-Y.1703(19)\_FIII.3
+
+As both IPv4 and CLNP are forwarded within the Level-1 areas, all of the routers in the Level-2 subdomain must be dual, even those present in IP-only or OSI-only areas.
+
+**Figure III.3 – Level-2 IS-IS routing in an external router network**
+
+### III.2.4 External routers running OSPF or other IP routing protocols
+
+Many operators currently run Level-2 IS-IS in their external routers, and OSPF, or other routing protocols, for IP. In this case, the external router must remain as the Level-2 router for the SDH NEs, and so, for a dual area, must be a dual integrated IS-IS router. However, the router may be configured to route all IP packets using OSPF by configuring redistribution of IP routes between IS-IS and OSPF. In this way, all IP packets will be OSPF routed, whilst CLNP packets continue to be Level-2 IS-IS routed. This is shown in Figure III.4.
+
+
+
+These routers must redistribute between OSPF and integrated IS-IS.
+ The default metric distributed into IS-IS must be more attractive than the Level-2 subdomain.
+
+The diagram illustrates three network areas connected to a central backbone (Level-2 subdomain):
+
+- Area 0001 (IP-only area):** Contains an IP router connected to the backbone (L1, L2) and four network elements (NEs): two IP NEs and one Dual IP/OSI NE.
+- Area 0002 (Dual area):** Contains two OSPF IS-IS routers connected to the backbone (L2) and four Dual IP/OSI NEs.
+- Area 0003 (OSI-only area):** Contains an OSI IS-IS router connected to the backbone (L1, L2) and four network elements: three OSI NEs and one Dual IP/OSI NE.
+
+Arrows from the top text point to the OSPF IS-IS routers in Area 0002 and the OSI IS-IS router in Area 0003, indicating they must redistribute between OSPF and integrated IS-IS.
+
+G.7712-Y.1703(19)\_FIII.4
+
+Diagram of external routers running OSPF across three areas: Area 0001 (IP-only), Area 0002 (Dual), and Area 0003 (OSI-only).
+
+**Figure III.4 – External routers running OSPF**
+
+Note that the integrated IS-IS stack in the external routers will not be aware that the Level-2 subdomain is meant only for CLNP packets. The OSPF learned routes must, therefore, be redistributed into integrated IS-IS with a low default metric, to make them more attractive to IP packets than the Level-2 subdomain.
+
+## III.3 Integrated IS-IS with automatic encapsulation
+
+### III.3.1 Introduction and effect on topological restrictions
+
+The automatic encapsulation option allows the topological rules of [IETF RFC 1195] to be broken. Automatic encapsulation effectively makes a node, or group of nodes, appear to be able to forward packets that, intact, they cannot.
+
+This is shown in Figure III.5.
+
+
+
+The diagram shows a sequence of nodes between points A and B:
+
+
+- Point A is connected to an AE (Automatically Encapsulating) IP/OSI NE.
+- This AE node is connected to an OSI NE.
+- This OSI NE is connected to another OSI NE.
+- This second OSI NE is connected to another AE IP/OSI NE.
+- This final AE node is connected to Point B.
+
+G.7712-Y.1703(19)\_FIII.5
+
+AE Automatically Encapsulating
+
+Diagram showing a group of nodes with automatic encapsulation (AE) connected to OSI NEs.
+
+**Figure III.5 – Group of nodes with automatic encapsulation**
+
+This group of nodes will now forward both IPv4 and CLNP packets, as long as the packets enter at point A or B, through one of the automatically encapsulating nodes.
+
+The group of nodes may now safely be put into a dual area, or a dual Level-2 subdomain, as the pair of automatically encapsulating nodes will forward IPv4 packets by encapsulating them inside CLNP packets, so that they will be forwarded by the OSI-only NEs rather than being discarded.
+
+A valid dual area may now appear as shown in Figure III.6.
+
+
+
+The diagram shows a large oval representing 'Area 0004 Dual area'. Inside this area, there are two 'Dual IP/OSI NE' nodes at the top, connected by a horizontal line. Below them, a dashed oval encloses two 'OSI NE' nodes connected to each other. The left 'OSI NE' is connected to an 'AE IP/OSI NE' node, which is in turn connected to the top-left 'Dual IP/OSI NE'. The right 'OSI NE' is connected to another 'AE IP/OSI NE' node, which is connected to the top-right 'Dual IP/OSI NE'. At the bottom, another 'AE IP/OSI NE' node is connected to the bottom-right 'Dual IP/OSI NE'. To the right of the diagram, a bracket groups three text annotations: 'OSI-only subnetwork.', 'Only CLNP packets can be forwarded in this part of the area.', and 'IP packets will be encapsulated into CLNP by AE nodes that surround the subnetwork.' Below the diagram, the text 'G.7712-Y.1703(19)\_FIII.6' is present. At the bottom left, 'AE Automatically Encapsulating' is defined, and 'Area 0004 Dual area' is labeled.
+
+Diagram of a valid dual area (Figure III.6).
+
+**Figure III.6 – Example of a valid dual area**
+
+Note that the OSI-only nodes must not be directly connected to one of the dual nodes that do not have the automatic encapsulation option. It is only the presence of the automatic encapsulating nodes that prevent IPv4 packets from being sent to an OSI-only node.
+
+A dual node may be connected directly to an OSI-only node if it is also treated as an OSI-only node, as shown in Figure III.7.
+
+
+
+The diagram shows a linear sequence of five nodes: 'A' -> 'AE IP/OSI NE' -> 'OSI NE' -> 'Dual IP/OSI NE' -> 'OSI NE' -> 'AE IP/OSI NE' -> 'B'. Below the diagram, the text 'G.7712-Y.1703(19)\_FIII.7' is present. At the bottom left, 'AE Automatically Encapsulating' is defined.
+
+Diagram of a dual node connected to an OSI-only node (Figure III.7).
+
+**Figure III.7 – Connection of a dual node to an OSI-only node**
+
+In this case, the network acts as a dual network for packets going from point A to B, but IPv4 packets cannot reach the central dual node. This dual node is inside an OSI-only subnetwork. This dual node will be able to forward CLNP packets only and must be CLNS managed. There must be no other connections to the central dual node, as, if IPv4 packets were introduced at the central node, then they might be forwarded to an OSI-only node and be discarded.
+
+### III.3.2 Getting IP traffic in and out of the SDH embedded network
+
+#### III.3.2.1 IP capable gateway NE
+
+Both IP and CLNP packets must be able to enter and leave a dual area, whether or not automatic encapsulation is used. Normally traffic enters and leaves an IS-IS area via Level-1, Level-2 routers. These are routers that participate both in the Level-1 area and in the Level-2 subdomain.
+
+The simplest way to build this is to ensure that any Level-1, Level-2 routers are dual, as shown in Figure III.8.
+
+
+
+Diagram of a dual gateway network architecture. A large oval labeled 'Area 0004 Dual area' contains several nodes. At the top, two 'Dual IP/OSI router' nodes are connected by an 'L1, L2 link'. Each of these routers is connected to an 'AE IP/OSI NE' node. These two 'AE IP/OSI NE' nodes are connected to two 'OSI NE' nodes, which are in turn connected to each other. Below the 'OSI NE' nodes, there is another 'AE IP/OSI NE' node connected to one of the 'OSI NE' nodes, and a 'Dual IP/OSI NE' node connected to the other 'OSI NE' node. These two bottom nodes are also connected to each other. Outside the oval, three links are shown: an 'L2 link' pointing to the left 'Dual IP/OSI router', an 'L2 link' pointing to the right 'Dual IP/OSI router', and an 'L2 link' pointing to the top of the oval. The text 'Level-2 subdomain' is at the top left. A reference code 'G.7712-Y.1703(19)\_FIII.8' is at the bottom right. A legend at the bottom left states 'AE Automatically Encapsulating'.
+
+**Figure III.8 – Dual gateway**
+
+#### **III.3.2.2 OSI-only gateway NE**
+
+Occasionally, automatically encapsulating nodes will be used to upgrade an existing OSI-only area to make it effectively into a dual area. In this case, the gateway nodes may have to remain as OSI-only nodes. In such a case, a network can be built as shown in Figure III.9.
+
+
+
+Diagram of an OSI-only gateway network architecture. A large oval labeled 'Area 0004 Dual area' contains a mesh of nodes. At the top, two 'OSPF and L1, L2 OSI router' nodes are connected to an 'OSPF Access DCN' with IP address '10.3.0.0/16'. These routers are connected to 'OSI NE' nodes labeled 'Gateway NE'. Below the gateway nodes, there is a mesh of 'OSI NE' nodes and 'AE IP/OSI NE' nodes. At the bottom, two 'IP NE' nodes are connected to 'AE IP/OSI NE' nodes. The bottom section is labeled 'Level-1 area = 10.3.x.x'. Dashed lines represent 'Manual RFC 3147 tunnel' connections from the 'OSPF Access DCN' to the 'AE IP/OSI NE' nodes at the bottom, with IP address '0.0.0.0'. Text indicates 'Static/default route not advertised if tunnel fails'. A reference code 'G.7712-Y.1703(19)\_FIII.9' is at the bottom right. A legend at the bottom left states 'AE Automatically Encapsulating'.
+
+**Figure III.9 – OSI-only gateway**
+
+In this network, the CLNP packets that need to leave the Level-1 area continue to go to the OSI Level-1, Level-2 router. The nodes that have a manual tunnel leading out of the Level-1 area advertise this as a default route. Consequently, the IP-capable nodes will all add an entry to the bottom of their routing table telling them to send all IPv4 packets to one of the nodes that has the manual tunnel, unless they have a more specific route. In this way, an IPv4 packet is never sent to a Level-1, Level-2 node, but is always sent across one of the manual tunnels.
+
+The router in the access DCN that terminates the manual tunnel does not need to run integrated IS-IS. It may run any IP routing protocol that an operator wishes to use. In this way, an existing network that uses OSPF and Level-2 IS-IS in the access DCN, and Level-1 IS-IS in the SDH NEs, may have the Level-1 areas upgraded to dual areas with little impact on the existing OSI-only SDH NEs, or on the access DCN.
+
+# Appendix IV
+
+## Example illustration of packet 1+1 protection
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## IV.1 Packet 1+1 protection overview
+
+Packet 1+1 path protection provides a packet level protection service similar in some respects to the conventional connection level 1+1 service, with several important distinctions. Packet level 1+1 allows selection of incoming packets from any connection, irrespective of the connection from which the last packet was selected. That is, packet 1+1 protection treats both connections as working connections, as opposed to designating one connection as working, and the other as the protection. In the latter, packets are selected from the working connection until a detection of failure on the working connection causes a switching to the protection connection. In contrast, packet 1+1 does not require explicit failure detection and protection switching. This allows the packet level 1+1 scheme to recover from any failure instantaneously and transparently. Similar to the connection level 1+1 protection, only edge nodes need to be service-aware, which makes interoperability easier.
+
+To provide packet 1+1 protection service between two connection-oriented network edge nodes, a pair of connections is established along disjoint paths. Packets from an application flow subscribing to the service are dual-fed at the ingress node onto the two connections. Disjoint paths, in the simplest case, may be link or node disjoint but, in general, may involve more complicated notion such as shared risk groups. At the egress edge node, one of the two copies of the packets selected and forwarded from the two possible received copies, each traversing a disjoint path. Given this, any single failure in the network, other than the ingress or egress node itself, can affect at most one copy of each packet. This allows the service to withstand a single failure transparently. In terms of restoration time, this can be characterized as an instantaneous recovery from a failure since there is no need to detect, notify and switch to protection path explicitly. The scheme can be easily extended to protect against multiple failures by employing more than two disjoint paths.
+
+## IV.2 Packet 1+1 protection illustration
+
+Figure IV.1 illustrates a realization of the service using sequence numbers as identifiers. After passing through the classifier, each packet that needs to be forwarded on the mated LSPs is assigned a distinct sequence number by the service-aware source edge node. This packet with the distinct identification is then duplicated and forwarded onto the two disjoint LSPs. The egress node shall only select one copy of the duplicated packet. For appropriately selecting the packet exactly once, the destination must be able to identify the duplicate packets and then select one, and handle all possible variations. This selection process at the packet level is non-trivial as the duplicate packets may not arrive at the same time (due to propagation delay and buffering) and also these packets may get lost (due to transmission errors and buffer overflows).
+
+
+
+Diagram of 1+1 protection in a Generic IP/MPLS network. Two Edge nodes are connected to a central network cloud. The left Edge node (ingress) receives packets from Client ports and duplicates them onto two paths: a top path (labeled 7, 6, 5, 4) and a bottom path (labeled 7, 6, 5, 4, 3, 2). The right Edge node (egress) receives packets from both paths. It uses a 'Next sequence #' and a 'Select counter' to determine which packets to accept. The top path is labeled 'Diverse paths (Dual-feed/select)'. The diagram is labeled G.7712-Y.1703(19)\_FIV.1.
+
+**Figure IV.1 – 1+1 protection**
+
+The ingress node inserts the sequence number as defined in clause 7.1.19.2. The packet is then duplicated and transported over diverse LSPs. Due to the diversity of the LSPs, there will be a leading LSP and a trailing LSP. The leading LSP will deliver the packets to the egress node faster than the trailing LSP. Therefore, under non-failure conditions, the egress node will select the packets from the leading LSP. The packets received on the trailing LSP will be duplicate packets and will, therefore, be discarded.
+
+The decision whether to accept or discard a received packet is based on the received packet's sequence number and a counter + sliding window at the egress node. The counter indicates the sequence number of the next packet it is expecting. The counter, plus sliding window, provides a window of acceptable sequence numbers. The sliding window is needed to properly accept and reject packets. If the received packet falls in the window, it is considered legitimate and can be accepted. Otherwise, it is rejected. The size of the window should be larger than the maximum number of consecutive packets a working (an alive) LSP can lose.
+
+The sliding window is used to solve the problem of losing packets on the leading LSP when the leading LSP's sequence number is very close to the wrap around point. Figure IV.2 illustrates a leading LSP (LSP-1) that delivers a packet with sequence number 29. The packet is accepted and the counter is incremented to 30. If we assume that two consecutive packets are lost (i.e., packets with sequence numbers 30 and 31), the next received packet on LSP-1 will be 0. Without a sliding window, the egress node will reject the packet since $0 < 30$ . By implementing a sliding window that is larger than the maximum number of consecutive packets a working (an alive) LSP can lose, this problem can be solved. For example, let us say that the maximum number of consecutive packets that a working LSP can lose is five, then a sliding window of six can be defined. Taking the same example as before, however, now using the sliding window, the egress node will accept packets in the range of {30, 31, 0, 1, 2, 3, 4}. Therefore, even if five packets are lost (i.e., the maximum number of consecutive packets that can be lost on a working LSP), the next packet received will have sequence number 3 and the packet will be accepted.
+
+
+
+Figure IV.2 – Sliding window mechanism. A circular diagram representing a sequence number space from 0 to 31. A yellow dot at the center represents the current position. A blue arrow labeled 'LSP-1' points to position 31, and a red arrow labeled 'LSP-2' points to position 23. A callout box points to position 31 with the text 'Sequence number of the next packet being expected'. A legend indicates that red dots represent 'Lost packets' (at positions 30 and 31) and a green dot represents 'Next packet received' (at position 0). The diagram is labeled 'G.7712-Y.1703(19)\_FIV.2'.
+
+**Figure IV.2 – Sliding window mechanism**
+
+Note that this idea of sliding window only works if the falling behind LSP cannot fall back in the sliding window range. If a packet with a sequence number in the range of the sliding window is received from the falling behind LSP, then it will be mistakenly accepted. A falling behind LSP can only receive a packet with a sequence number in the range of the sliding window if it falls back by more than $(2^N - \text{size of sliding window})$ . Therefore, the number of bits "N" used for the sequence number must support the following equation:
+
+$$2^N > \text{SlidingWindow} + \text{DelayWindow}$$
+
+where:
+
+SlidingWindow > maximum number of consecutive packets that can be lost on a LSP
+
+and:
+
+DelayWindow = maximum number of packets the trailing LSP can fall behind the leading LSP
+
+Note that clause 7.1.19.2 defines a 4-byte field for carrying the sequence number. The 4-byte field provides a sequence of more than four-billion numbers which is large enough to accommodate worst-case consecutive packet losses and delay differentials.
+
+One reasonable way of engineering the size of the sliding and delay windows is to make the size of the sliding window equal to the size of the delay window. (Note that it is assumed that the size of the delay window is generally larger than the size of the sliding window.) This guarantees selection of packets from the leading LSP in all scenarios after a failed LSP gets repaired. This point is further elaborated in the following clause which discusses various failure scenarios.
+
+## IV.3 Operation of selector algorithm under various failure scenarios
+
+One way to view the operation of the selector algorithm is to picture a clock with $2^N$ intervals. Figure IV.3 illustrates an example where $N = 4$ (i.e., 4-bit sequence number) and, therefore, the sequence number ranges from 0 through 15.
+
+In this example, the SlidingWindow is set equal to the DelayWindow, which is 5.
+
+Figure IV.3 shows the leading LSP ahead of the trailing LSP by 3 sequence numbers. The leading LSP delivers a packet with sequence number = 1 and the counter is now set to 2.
+
+
+
+→ Leading LSP
+- - → Trailing LSP
+
+G.7712-Y.1703(19)\_FIV.3
+
+Figure IV.3: Selector algorithm operation. A circular diagram showing sequence numbers 0 to 15. A solid arrow (Leading LSP) points to 1, and a dashed arrow (Trailing LSP) points to 14. A shaded 'SlidingWindow' covers sequence numbers 1 through 6. A 'DelayWindow' arc spans from 12 to 1.
+
+**Figure IV.3 – Selector algorithm operation**
+
+Figure IV.4 shows that, prior to receiving a packet with a sequence number equal to 2 on the leading LSP, the leading LSP fails. Until the packet with sequence number equal to 2 is delivered from the trailing LSP, the egress node will not select any packets and the counter will remain equal to 2.
+
+
+
+→ Leading LSP
+- - → Trailing LSP
+
+G.7712-Y.1703(19)\_FIV.4
+
+Figure IV.4: Leading LSP failure. Similar to Figure IV.3, but the solid arrow (Leading LSP) pointing to 1 is crossed out with an 'X'. The dashed arrow (Trailing LSP) still points to 14, and the shaded 'SlidingWindow' remains from 1 to 6.
+
+**Figure IV.4 – Leading LSP failure**
+
+Figure IV.5 illustrates that, when the packet with a sequence number equal to 2 is received on the trailing LSP, the egress node increments the counter to 3 and the sliding window shifts so that a packet with a sequence number in the range of 3 through 7 can be accepted.
+
+
+
+Figure IV.5: Reception of packet 2 by trailing LSP. A circular diagram representing a sequence number space from 0 to 15. A 'DelayWindow' arc is shown from sequence 0 to 5. A 'SlidingWindow' shaded sector spans from sequence 2 to 5. A dashed arrow labeled 'Trailing LSP' points to sequence 2. A solid arrow labeled 'Leading LSP' points to sequence 4. A legend at the bottom left indicates that a solid arrow represents the Leading LSP and a dashed arrow represents the Trailing LSP. The reference 'G.7712-Y.1703(19)\_FIV.5' is at the bottom right.
+
+**Figure IV.5 – Reception of packet 2 by trailing LSP**
+
+Figure IV.6 illustrates that, prior to receiving a packet with a sequence number equal to 3 from the trailing LSP, the leading LSP is repaired and a packet with a sequence number equal to 6 is received from the Leading LSP. Since 6 is within the sliding window range, the packet is accepted. Note that it is important that, so long as the leading LSP is working, packets are received from the leading LSP. Therefore, to ensure that, when the leading LSP is repaired, it delivers a packet with a sequence number value that is within the sliding window range, the SlidingWindow should be equal to or greater than the DelayWindow, which is the case for this example.
+
+
+
+Figure IV.6: Leading LSP repaired. A circular diagram representing a sequence number space from 0 to 15. A 'DelayWindow' arc spans from 0 to 5. A 'SlidingWindow' shaded sector spans from sequence 10 clockwise to 6. A dashed arrow labeled 'Trailing LSP' points to sequence 3. A solid arrow labeled 'Leading LSP' points to sequence 6. The area between sequence 3 and 6 is labeled 'Lost packets'. A legend at the bottom left indicates that a solid arrow represents the Leading LSP and a dashed arrow represents the Trailing LSP. The reference 'G.7712-Y.1703(19)\_FIV.6' is at the bottom right.
+
+**Figure IV.6 – Leading LSP repaired**
+
+Figures IV.7, IV.8 and IV.9 illustrate a problem if the SlidingWindow is set smaller than the DelayWindow. In this case, it is possible that, when the leading LSP is repaired, it delivers packets with sequence numbers that fall outside the SlidingWindow and, therefore, the egress node continues to accept packets from the trail LSP. If, at a later time, the trailing LSP fails, there is a potential to lose many packets (worst case would be $2^N - \text{size\_of\_sliding\_window}$ , where N is the number of bits used for the sequence number).
+
+Figure IV.7 shows an example where the SlidingWindow is set to 3, while the DelayWindow can be up to 7. In this example, the trailing LSP trails the leading LSP by 4 sequence numbers. Since the leading LSP has failed, the packets are selected from the trailing LSP.
+
+
+
+Figure IV.7: A circular diagram illustrating a sliding window and a delay window. The circle is marked with numbers 0 to 15. A 'DelayWindow' is shown as a shaded arc from 0 to 6. A 'SlidingWindow' is shown as a shaded arc from 2 to 5. A solid arrow labeled 'Leading LSP' points to 6, and a dashed arrow labeled 'Trailing LSP' points to 2. The text 'G.7712-Y.1703(10)\_FIV.7-App-IV' is at the bottom.
+
+**Figure IV.7 – Sliding window too small: packets selected from the trailing LSP**
+
+Figure IV.8 illustrates that, at the time when the leading LSP is repaired, it delivers a packet with a sequence number equal to 7 which is outside the SlidingWindow and, therefore, rejected. The packets continue to be selected from the trailing LSP.
+
+
+
+Figure IV.8: A circular diagram similar to Figure IV.7. The 'DelayWindow' is an arc from 0 to 6. The 'SlidingWindow' is an arc from 3 to 6. A solid arrow labeled 'Leading LSP' points to 7, which is outside the SlidingWindow. A dashed arrow labeled 'Trailing LSP' points to 3. The text 'G.7712-Y.1703(19)\_FIV.8' is at the bottom.
+
+**Figure IV.8 – Sliding window too small: rejection of packets delivered by the repaired leading LSP**
+
+Figure IV.9 illustrates a failure to the trailing LSP. Since the leading LSP delivers packets outside the SlidingWindow and, therefore, those packets are rejected, the egress node will not start accepting packets until the leading LSP comes all the way around and starts to deliver packets with a sequence number that falls within the SlidingWindow. This can result in a significant loss of packets. Therefore, to prevent such an occurrence, it is recommended that this type of selector algorithm set the SlidingWindow equal to the DelayWindow.
+
+
+
+The diagram shows a circular clock face with numbers 0 through 15. A shaded sector labeled 'Sliding Window' spans from position 3 to 6. An arc labeled 'DelayWindow' spans from position 1 to 7. A solid arrow labeled 'Leading LSP' points to position 8. A dashed arrow labeled 'Trailing LSP' points to position 3. The text 'G.7712-Y.1703(19)\_FIV.9' is located at the bottom right of the diagram.
+
+A circular diagram illustrating a sliding window and a delay window for LSPs. The circle is marked with numbers 0 to 15. A shaded 'Sliding Window' covers the range from 3 to 6. A 'DelayWindow' is indicated by an arc from 1 to 7. A solid arrow labeled 'Leading LSP' points to 8, and a dashed arrow labeled 'Trailing LSP' points to 3. The text 'G.7712-Y.1703(19)\_FIV.9' is at the bottom right.
+
+**Figure IV.9 – Sliding window too small: effect of a failure for trailing LSP**
+
+# Appendix V
+
+## Mapping version 4 and version 5 clause numbers
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This appendix provides a mapping between clauses found in this version and those found in prior versions that have been changed due to restructuring.
+
+**Table V.1 – Mapping version 4 and version 5 clause numbers**
+
+| Structure of clauses 6 and 7 in version 4 | Corresponding structure in this version |
+|------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|
+| 6 DCN characteristics | 6 DCN applications |
+| 6.1 TMN application 6.1.1 – 6.1.4 | 6.1 TMN application 6.1.1 – 6.1.4 |
+| 6.2 Control plane application (ASON and MPLS-TP) 6.2.1 – 6.2.4 | 6.2 ASON [1] application 6.2.1 – 6.2.4 |
+| 6.3 SDN application 6.3.1 – 6.3.4 | 6.3 SDN application 6.3.1 – 6.3.4 |
+| 6.4 Other applications requiring communication networks 6.4.1 OTSiG OCh non-association. overhead Comm. application | 6.4 Other applications requiring communication networks 6.4.1 OTSiG OCh non-association overhead Comm. application |
+| 6.5 Separation of various application | 6.5 Separation of various application |
+| 7 DCN functional architecture and requirements | 7 DCN functional architecture |
+| 7.1 Specification of data communication functions | 8 Data communication function requirements |
+| 7.1.1 ECC access function | 8.1 L1 Physical layer requirements |
+| 7.1.2 ECC data-link layer termination function | 8.2 L2 Data Link layer requirements |
+| 7.1.2.1 SDH ECC data-link layer termination function | 8.2.1 SDH ECC (DCC) |
+| 7.1.2.2 OTN ECC data-link layer termination function | 8.2.2 OTN ECC (GCC) |
+
+[1] Possible future study: If there are lots of commonality between DCN for ASON application and DCN for SDN application, it might worth to consolidate the two applications. Furthermore, consolidate the TMN and Control plane applications into Management-Control-Continuum application.
+
+**Table V.1 – Mapping version 4 and version 5 clause numbers**
+
+| Structure of clauses 6 and 7 in version 4 | Corresponding structure in this version |
+|-------------------------------------------------------------------------------------|--------------------------------------------------------------------|
+| | 8.2.3 MPLS-TP ECC |
+| 7.1.2.3 MPLS-TP SCN; 7.1.2.5 MPLS-TP SCC | 8.2.3.1 MPLS-TP SCN |
+| 7.1.2.4 MPLS-TP MCN; 7.1.2.6 MPLS-TP MCC | 8.2.3.2 MPLS-TP MCN |
+| | 8.3 L3 Network layer requirements |
+| 7.1.3 "Network layer PDU into ECC data-link frame" encapsulation function | 8.3.1 L3 into L2 encapsulation functions |
+| 7.1.3.1 "Network layer PDU into SDH ECC data-link frame" encapsulation function | 8.3.1.1 L3 into SDH ECC data-link frame encapsulation function |
+| 7.1.3.2 "Network layer PDU into MPLS-TP SCC data-link frame" encapsulation function | 8.3.1.2 L3 into MPLS-TP SCC data-link frame encapsulation function |
+| 7.1.3.3 "Network layer PDU into MPLS-TP MCC data-link frame" encapsulation function | 8.3.1.3 L3 into MPLS-TP MCC data-link frame encapsulation function |
+| 7.1.3.4 "Network layer PDU into EoT MCC data-link frame" encapsulation function | 8.3.1.4 L3 into EoT MCC data-link frame" encapsulation function |
+| 7.1.4 Ethernet LAN Physical termination function | 9.1 Ethernet LAN as L1&L2 |
+| 7.1.5 Network layer PDU into Ethernet frame | 8.3.1.5 L3 into Ethernet frame encapsulation functions |
+| 7.1.6 Network layer PDU forwarding function | 8.3.2 L3 forwarding function |
+| 7.1.7 Network layer PDU interworking function | 8.3.3 L3 interworking function |
+| 7.1.8 Network layer PDU encapsulation function | 8.3.4 L3 to L3 encapsulation function |
+| 7.1.9 Network layer PDU tunnelling function | 8.3.5 L3 tunnelling function |
+| 7.1.10 Network layer routing function | 8.3.6 L3 routing function |
+| 7.1.11 IP routing interworking function | 8.3.7 L3 IP routing interworking function |
+| 7.1.12 "Applications to network layer" mapping function | 8.3.8 Applications to L3 mapping function |
+
+**Table V.1 – Mapping version 4 and version 5 clause numbers**
+
+| Structure of clauses 6 and 7 in version 4 | Corresponding structure in this version |
+|-------------------------------------------------------------------|-------------------------------------------------------------|
+| | 9 Specific DCN L3 L2 L1 Technology requirements |
+| 7.1.4 Ethernet LAN Physical termination function | 9.1 Ethernet LAN as L1&L2 |
+| | 9.2 Ethernet WAN as L1&L2 |
+| | 9.3 Native MPLS as L3 |
+| 7.1.13 "MPLS PDU into ECC data-link layer" encapsulation function | 9.3.1 MPLS PDU into L2 encapsulation function |
+| 7.1.14 "MPLS PDU into Ethernet frame" encapsulation function | 9.3.1.1 MPLS PDU into Ethernet frame encapsulation function |
+| 7.1.15 – 7.1.19 MPLS .... | 9.3.2 – 9.3.6 .... |
+| 7.2 Provisioning requirements | 8.4.1 Provisioning requirements |
+| 7.3 Security requirements | 8.4.2 Security requirements |
+| NOTE – italicized items are out of order or repeated. | |
+
+# Bibliography
+
+- [b-IETF RFC 1702] IETF RFC 1702 (1994), *Generic Routing Encapsulation over IPv4 networks*.
+- [b-IETF RFC 2126] IETF RFC 2126 (1997), *ISO Transport Service on top of TCP (ITOT)*.
+- [b-IETF RFC 2966] IETF RFC 2966 (2000), *Domain-wide Prefix Distribution with Two-Level IS-IS*.
+- [b-IETF RFC 3147] IETF RFC 3147 (2001), *Generic Routing Encapsulation of CLNS Networks*.
+- [b-IETF RFC 3373] IETF RFC 3373 (2002), *Three-Way Handshake for Intermediate System to Intermediate System (IS-IS) Point-to-Point Adjacencies*.
+- [b-IETF RFC 4204] IETF RFC 4204 (2005), *Link Management Protocol (LMP)*.
+- [b-IETF RFC 5920] IETF RFC 5920 (2010), *Security Framework for MPLS and GMPLS Networks*.
+- [b-IETF RFC 5950] IETF RFC 5950 (2010), *Network Management Framework for MPLS-based Transport Networks*.
+- [b-ONF TR-529] Open Networking Foundation, Technical Recommendation 529 (2016), *Security Foundation Requirements for SDN Controllers*.
+[https://www.opennetworking.org/wp-content/uploads/2013/05/Security\\_Foundation\\_Requirements\\_for\\_SDN\\_Controllers.pdf](https://www.opennetworking.org/wp-content/uploads/2013/05/Security_Foundation_Requirements_for_SDN_Controllers.pdf)
+- [b-ONF TR-530] Open Networking Foundation, Technical Recommendation 530 (2016), *Threat analysis for SDN architecture*.
+[https://www.opennetworking.org/wp-content/uploads/2014/10/Threat\\_Analysis\\_for\\_the\\_SDN\\_Architecture.pdf](https://www.opennetworking.org/wp-content/uploads/2014/10/Threat_Analysis_for_the_SDN_Architecture.pdf)
+
+# ITU-T Y-SERIES RECOMMENDATIONS
+
+## GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES
+
+| | |
+|--------------------------------------------------------------------|----------------------|
+| GLOBAL INFORMATION INFRASTRUCTURE | |
+| General | Y.100–Y.199 |
+| Services, applications and middleware | Y.200–Y.299 |
+| Network aspects | Y.300–Y.399 |
+| Interfaces and protocols | Y.400–Y.499 |
+| Numbering, addressing and naming | Y.500–Y.599 |
+| Operation, administration and maintenance | Y.600–Y.699 |
+| Security | Y.700–Y.799 |
+| Performances | Y.800–Y.899 |
+| INTERNET PROTOCOL ASPECTS | |
+| General | Y.1000–Y.1099 |
+| Services and applications | Y.1100–Y.1199 |
+| Architecture, access, network capabilities and resource management | Y.1200–Y.1299 |
+| Transport | Y.1300–Y.1399 |
+| Interworking | Y.1400–Y.1499 |
+| Quality of service and network performance | Y.1500–Y.1599 |
+| Signalling | Y.1600–Y.1699 |
+| Operation, administration and maintenance | Y.1700–Y.1799 |
+| Charging | Y.1800–Y.1899 |
+| IPTV over NGN | Y.1900–Y.1999 |
+| NEXT GENERATION NETWORKS | |
+| Frameworks and functional architecture models | Y.2000–Y.2099 |
+| Quality of Service and performance | Y.2100–Y.2199 |
+| Service aspects: Service capabilities and service architecture | Y.2200–Y.2249 |
+| Service aspects: Interoperability of services and networks in NGN | Y.2250–Y.2299 |
+| Enhancements to NGN | Y.2300–Y.2399 |
+| Network management | Y.2400–Y.2499 |
+| Network control architectures and protocols | Y.2500–Y.2599 |
+| Packet-based Networks | Y.2600–Y.2699 |
+| Security | Y.2700–Y.2799 |
+| Generalized mobility | Y.2800–Y.2899 |
+| Carrier grade open environment | Y.2900–Y.2999 |
+| FUTURE NETWORKS | Y.3000–Y.3499 |
+| CLOUD COMPUTING | Y.3500–Y.3999 |
+| INTERNET OF THINGS AND SMART CITIES AND COMMUNITIES | |
+| General | Y.4000–Y.4049 |
+| Definitions and terminologies | Y.4050–Y.4099 |
+| Requirements and use cases | Y.4100–Y.4249 |
+| Infrastructure, connectivity and networks | Y.4250–Y.4399 |
+| Frameworks, architectures and protocols | Y.4400–Y.4549 |
+| Services, applications, computation and data processing | Y.4550–Y.4699 |
+| Management, control and performance | Y.4700–Y.4799 |
+| Identification and security | Y.4800–Y.4899 |
+| Evaluation and assessment | Y.4900–Y.4999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/G/T-REC-G.7713.2-200303-I_PDF-E/raw.md b/marked/G/T-REC-G.7713.2-200303-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..1dd7947f4ea1dc0912c86e3673abe68fd29e71c8
--- /dev/null
+++ b/marked/G/T-REC-G.7713.2-200303-I_PDF-E/raw.md
@@ -0,0 +1,1563 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**G.7713.2/Y.1704.2**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(03/2003)
+
+SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
+DIGITAL SYSTEMS AND NETWORKS
+
+Digital terminal equipments – Operations, administration
+and maintenance features of transmission equipment
+
+SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE
+AND INTERNET PROTOCOL ASPECTS
+
+Internet protocol aspects – Operation, administration and
+maintenance
+
+---
+
+**Distributed Call and Connection Management:
+Signalling mechanism using GMPLS RSVP-TE**
+
+ITU-T Recommendation G.7713.2/Y.1704.2
+
+---
+
+# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS**
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------|
+| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 |
+| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 |
+| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 |
+| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 |
+| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 |
+| TESTING EQUIPMENTS | G.500–G.599 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.600–G.699 |
+| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 |
+| DIGITAL NETWORKS | G.800–G.899 |
+| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 |
+| QUALITY OF SERVICE AND PERFORMANCE | G.1000–G.1999 |
+| TRANSMISSION MEDIA CHARACTERISTICS | G.6000–G.6999 |
+| DIGITAL TERMINAL EQUIPMENTS | G.7000–G.7999 |
+| General | G.7000–G.7099 |
+| Coding of analogue signals by pulse code modulation | G.7100–G.7199 |
+| Coding of analogue signals by methods other than PCM | G.7200–G.7299 |
+| Principal characteristics of primary multiplex equipment | G.7300–G.7399 |
+| Principal characteristics of second order multiplex equipment | G.7400–G.7499 |
+| Principal characteristics of higher order multiplex equipment | G.7500–G.7599 |
+| Principal characteristics of transcoder and digital multiplication equipment | G.7600–G.7699 |
+| Operations, administration and maintenance features of transmission equipment | G.7700–G.7799 |
+| Principal characteristics of multiplexing equipment for the synchronous digital hierarchy | G.7800–G.7899 |
+| Other terminal equipment | G.7900–G.7999 |
+| DIGITAL NETWORKS | G.8000–G.8999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# **Distributed Call and Connection Management: Signalling mechanism using GMPLS RSVP-TE**
+
+## **Summary**
+
+This Recommendation meets the requirements of ITU-T Rec. G.7713/Y.1704 and is functionally similar to ITU-T Recs G.7713.1/Y.1704.1 and G.7713.3/Y.1704.3. This Recommendation covers the areas associated with the signalling aspects of automatic switched transport network (ASTN). Specifically it provides the signalling protocol based on the GMPLS RSVP-TE. This Recommendation focuses on the UNI and E-NNI interface specification. While these protocol specifications are generally applicable to the I-NNI as well, the I-NNI interface specification is for further study. This Recommendation encompasses support for Soft Permanent Connection (SPC) services. This version also includes support for Switched Connection (SC) services for intra-carrier application. As such, name translation/directory services and call capability sets are not included. This signalling protocol is used for the communications of call controller, connection controller and link resource manager. Areas covered include:
+
+- message specifications;
+- attribute specifications;
+- signal flows.
+
+This Recommendation does not cover any aspects related to routing, or automatic discovery.
+
+## **Source**
+
+ITU-T Recommendation G.7713.2/Y.1704.2 was prepared by ITU-T Study Group 15 (2001-2004) and approved under the WTSA Resolution 1 procedure on 16 March 2003.
+
+## **History**
+
+This Recommendation forms part of a suite of Recommendations covering the full functionality of the automatic switched transport network (ASTN).
+
+| Document history | |
+|-------------------------|------------------------------------------------------------------------------------------|
+| Issue | Notes |
+| 0.1 | Version 0.1 of G.7713.2/Y.1704.2 |
+| 0.2 | Modifications based on WD40 of 2/02 Q.14/15 meeting |
+| 0.3 | Editorial modifications to provide clarifications in some sections of the Recommendation |
+| 0.4 | Included new text on SPC, Call, Recovery |
+| 0.5 | Modifications to text for call processing |
+| 0.6 | Modification based on comments received at 10/02 Q.14/15 meeting |
+| 0.7 | Accept the revision mark of version 0.6 |
+| 0.8 | Editorial changes to align with IANA codepoint assignments |
+
+## **Keywords**
+
+Automatic switched optical network, Automatic switched transport network, Distributed call and connection management, Exterior network-node interface, GMPLS RSVP-TE, User network interface.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2003
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## CONTENTS
+
+| | Page |
+|---------------------------------------------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References..... | 1 |
+| 3 Terms and definitions ..... | 2 |
+| 4 Abbreviations..... | 3 |
+| 5 Conventions ..... | 3 |
+| 6 Assumptions ..... | 3 |
+| 7 Overview and application of GMPLS RSVP-TE to distributed connection management..... | 4 |
+| 7.1 Overview of GMPLS RSVP-TE ..... | 4 |
+| 7.2 Defect handling of GMPLS RSVP-TE..... | 8 |
+| 7.3 Example signalling flows ..... | 10 |
+| 8 GMPLS RSVP-TE messages..... | 16 |
+| 8.1 Path..... | 17 |
+| 8.2 Resv ..... | 18 |
+| 8.3 ResvConf ..... | 19 |
+| 8.4 PathTear..... | 19 |
+| 8.5 PathErr ..... | 20 |
+| 8.6 Notify..... | 20 |
+| 8.7 Hello ..... | 21 |
+| 8.8 Ack ..... | 21 |
+| 8.9 Srefresh..... | 21 |
+| 9 GMPLS RSVP-TE attributes..... | 22 |
+| 9.1 GMPLS RSVP-TE objects ..... | 22 |
+| 9.2 GMPLS RSVP-TE error/status codes ..... | 25 |
+| Annex A – Summary of GENERALIZED_UNI object..... | 29 |
+| Annex B – Label scope ..... | 30 |
+| B.1 Scope of the label ..... | 30 |
+| B.2 Label association function..... | 31 |
+| Annex C – Technology-specific terminology updates..... | 31 |
+| Appendix I – Mapping of messages..... | 33 |
+| Appendix II – Mapping of attributes..... | 34 |
+| Appendix III – Protocol elements not used..... | 35 |
+| III.1 Messages not used ..... | 35 |
+| III.2 Objects not used ..... | 36 |
+| Appendix IV – Support for call capability..... | 36 |
+| IV.1 Call capability object..... | 36 |
+| Appendix V – Example multiple control plane node failures..... | 37 |
+
+
+
+# **Distributed Call and Connection Management: Signalling mechanism using GMPLS RSVP-TE**
+
+# **1 Scope**
+
+This Recommendation covers the areas associated with the signalling aspects of automatic switched transport network (ASTN). Specifically it provides the signalling protocol based on the GMPLS RSVP-TE. This Recommendation focuses on the UNI and E-NNI interface specification. While these protocol specifications are generally applicable to the I-NNI as well, the I-NNI interface specification is for further study. This Recommendation encompasses support for Soft Permanent Connection (SPC) services. This version also includes support for Switched Connection (SC) services for intra-carrier application. As such, name translation/directory services and call capability sets are not included. This signalling protocol is used for the communications of call controller, connection controller and link resource manager. Areas covered include:
+
+- message specifications;
+- attribute specifications;
+- signal flows.
+
+This Recommendation provides the attribute and message specification, and signalling exchange that allow support for hierarchical, source and step-by-step routing. Other areas of ASTN such as routing mechanism, parameters associated with routing mechanisms, discovery, and naming and addressing are not in the scope of this Recommendation.
+
+This Recommendation uses the control plane architectural requirements in ITU-T Rec. G.8080/Y.1304 and the protocol neutral requirements as outlined in ITU-T Rec. G.7713/Y.1704 as the basis for the specification.
+
+## **2 References**
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- ITU-T Recommendation E.360.1 (2002), *Framework for QoS routing and related traffic engineering methods for IP-, ATM- and TDM-based multiservice networks*.
+- ITU-T Recommendation G.703 (2001), *Physical/electrical characteristics of hierarchical digital interfaces*.
+- ITU-T Recommendation G.707/Y.1322 (2000), *Network node interface for the Synchronous Digital Hierarchy (SDH)*.
+- ITU-T Recommendation G.709/Y.1331 (2003), *Interfaces for the Optical Transport Network (OTN)*.
+- ITU-T Recommendation G.7713/Y.1704 (2001), *Distributed Call and Connection Management (DCM)*.
+- ITU-T Recommendation G.803 (2000), *Architecture of transport networks based on the Synchronous Digital Hierarchy (SDH)*.
+
+- ITU-T Recommendation G.805 (2000), *Generic functional architecture of transport networks*.
+- ITU-T Recommendation G.807/Y.1302 (2001), *Requirements for Automatic Switched Transport Network (ASTN)*.
+- ITU-T Recommendation G.872 (2001), *Architecture of optical transport networks*.
+- ITU-T Recommendation G.8080/Y.1304 (2001), *Architecture for Automatic Switched Optical Network (ASON)*.
+- IETF RFC 2205 (1997), *Resource ReSerVation Protocol (RSVP) – Version 1 Functional Specification*.
+- IETF RFC 2747 (2000), *RSVP Cryptographic Authentication*.
+- IETF RFC 2750 (2000), *RSVP Extensions for Policy Control*.
+- IETF RFC 2961 (2001), *RSVP Refresh Overhead Reduction Extensions*.
+- IETF RFC 3097 (2001), *RSVP Cryptographic Authentication – Updated Message Type Value*.
+- IETF RFC 3209 (2001), *RSVP-TE: Extensions to RSVP for LSP Tunnels*.
+- IETF RFC 3471 (2003), *Generalized Multi-Protocol Label Switching (GMPLS) – Signalling Functional Description*.
+- IETF RFC 3473 (2003), *Generalized Multi-Protocol Label Switching (GMPLS) Signalling – Resource Reservation Protocol – Traffic Engineering (RSVP-TE) Extensions*.
+- OIF UNI-01.0 (2001), *User Network Interface (UNI) 1.0 signalling specification*.
+
+## 3 Terms and definitions
+
+The following terms are defined in ITU-T Rec. G.805:
+
+- administrative domain;
+- layer network;
+- link connection;
+- management domain;
+- subnetwork;
+- subnetwork connection.
+
+The following terms are defined in ITU-T Rec. G.8080/Y.1304:
+
+- agent;
+- component;
+- call controller;
+- connection controller;
+- connection admission control;
+- route controller;
+- neighbour discovery;
+- link resource manager;
+- policy;
+- protocol controller;
+
+- subnetwork point;
+- subnetwork point pool.
+
+The following terms are defined in ITU-T Rec. G.807/Y.1302:
+
+- soft permanent connection;
+- switched connection.
+
+## 4 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|---------|-----------------------------------------------------|
+| ASON | Automatic Switched Optical Network |
+| ASTN | Automatic Switched Transport Network |
+| CallC | Call Controller |
+| CC | Connection Controller |
+| CCC | Calling/Called Party Call Controller |
+| DCM | Distributed Call and Connection Management |
+| E-NNI | Exterior NNI |
+| GMPLS | Generalized Multi-Protocol Label Switching |
+| I-NNI | Interior NNI |
+| LRM | Link Resource Manager |
+| NCC | Network Call Controller |
+| NNI | Network Node Interface |
+| RSVP-TE | Resource reSerVation Protocol – Traffic Engineering |
+| SC | Switched Connection |
+| SNP | Subnetwork Point |
+| SNPP | Subnetwork Point Pool |
+| SPC | Soft Permanent Connection |
+| UNI | User Network Interface |
+
+## 5 Conventions
+
+In this Recommendation, the acronym GMPLS is used to denote the signalling protocol portion of GMPLS based on the GMPLS RSVP-TE and should be read as synonymous to GMPLS RSVP-TE.
+
+## 6 Assumptions
+
+This Recommendation assumes the messages and objects defined by RFC 2205, RFC 2961, RFC 3209, [RFC 3471 GMPLS-SIG], [RFC 3473 GMPLS-RSVP-TE], and OIF UNI-01.0 as the basis for the protocol specification for the ASON network.
+
+ITU-T Rec. G.8080/Y.1304 defines a UNI Transport Resource Addresses for the bearer links at the UNI reference point. For this Recommendation, an instantiation of those addresses will follow the OIF Transport Network Address (TNA) from OIF UNI-01.0 which complies with the G.8080/Y.1304 architecture. Allowable address formats in the OIF TNA are IPv4, IPv6, and NSAP addresses.
+
+Call routing services are assumed to be available that associate a UNI Transport Resource Addresses with internal routable addresses. This is not within the scope of this Recommendation.
+
+Addressing of transport resources in the protocol is done by SNPP identifiers. A pair of these would identify an SNPP link. SNPP names are defined from transport name spaces (see clause 10/G.8080/Y.1304) and it is important to note that control plane names/addresses are not used for these. For example, neither routing controller nor connection manager identifiers are used for bearer link names.
+
+The terms Quality of Service (QoS), Class of Service (CoS), and Grade of Service (GoS) with respect to the transport plane are used in this Recommendation in the sense of ITU-T Rec. E.360.1. It is expected that ASON specific characteristics and parameters will be associated with these terms in later versions of this Recommendation.
+
+# 7 Overview and application of GMPLS RSVP-TE to distributed connection management
+
+Figure 1 shows an overall view of control plane partition.
+
+
+
+```
+
+graph TD
+ subgraph User_Admin_1 [User admin domain]
+ U1[Nodes]
+ end
+ subgraph User_Admin_2 [User admin domain]
+ U2[Nodes]
+ end
+ subgraph Provider_A [Provider A admin domain]
+ subgraph Domain_A1 [Domain A1 I-NNI]
+ end
+ subgraph Domain_A2 [Domain A2 I-NNI]
+ end
+ Domain_A1 -- E-NNI --- Domain_A2
+ end
+ subgraph Provider_B [Provider B admin domain I-NNI]
+ end
+ subgraph Provider_C [Provider C admin domain]
+ end
+
+ U1 -- UNI --- Provider_A
+ Provider_A -- E-NNI --- Provider_B
+ Provider_B -- E-NNI --- Provider_C
+ Provider_C -- UNI --- U2
+
+ Note1[Provider A has divided their network into multiple control domains] -.-> Provider_A
+ Note2[Provider B's network is a single control domain] -.-> Provider_B
+
+```
+
+Figure 1/G.7713.2/Y.1704.2 – Overall view of control plane partition. A network diagram showing User admin domains connected via UNI to Provider admin domains (A, B, and C). Provider A is further divided into Domain A1 and A2 connected via E-NNI. Provider B is a single control domain. Interfaces between provider domains are E-NNI.
+
+**Figure 1/G.7713.2/Y.1704.2 – Overall view of control plane partition**
+
+## 7.1 Overview of GMPLS RSVP-TE
+
+The Resource reSerVation Protocol (RSVP) is an IETF-defined protocol [RFC 2205] for establishing network resources for IP datagram sessions (or "flows"). The definition of RSVP consists of basic procedures, message and object formats for signalling in an IP network. RSVP with Traffic Engineering extensions (RSVP-TE) [RFC 3209] has been defined for establishing connections subject to routing constraints in an MPLS network. The RSVP-TE definition includes
+
+additional procedures, message and object formats over the base RSVP definition. Generalized MPLS (GMPLS) signalling extends basic MPLS signalling procedures and abstract messages to cover different types of switching applications such as time-division-multiplexing (TDM) switching, port switching, wavelength switching, etc. Figure 2 shows the message flow for the relevant messages defined for GMPLS RSVP-TE. See below for a detailed description of these messages.
+
+
+
+Diagram showing GMPLS RSVP-TE message flow directions. A central 'CallC/CC' block is shown. Arrows indicate message flow: Upstream direction (left to right) includes Path, PathTear, ResvConf, Srefresh, Hello, Ack; Downstream direction (right to left) includes Resv, PathErr, Srefresh, Hello, Ack. The diagram is labeled G.7713.2\_F02.
+
+**Figure 2/G.7713.2/Y.1704.2 – GMPLS RSVP-TE message flow directions**
+
+The GMPLS RSVP-TE is extended to support the requirements as specified in ITU-T Rec. G.7713/Y.1704. The GENERALIZED\_UNI object is defined to encapsulate the A-end and Z-end names, as well as the CoS and GoS specifications to support the service requests at the UNI interface. See OIF UNI-01.0 for a definition of the GENERALIZED\_UNI object. This information is also summarized as part of Annex A. In addition to this object, extensions are also made to support the basic call concept and to support the soft permanent connection service.
+
+### 7.1.1 Support for basic call identifier
+
+GMPLS RSVP-TE may be extended to support the basic call model as specified in ITU-T Rec. G.7713/Y.1704. This call model assumes that a request message handles both a call and its associated connections within the same message between the calling party call controller and the network call controller, as well as between the network call controller and the called party call controller. Addition or release of connections from an existing call is considered a call modify procedure, i.e., modification of specific connection attributes. As such, a call session remains constant across call modification operations. An established call may be identified via a call identifier object, CALL\_ID. The format and structure of the CALL\_ID information is:
+
+- CALL\_ID Class = 230, C-Type = 1
+
+| 0 | 1 | 2 | 7 | 8 | 15 | 16 | 23 | 24 | 31 |
+|-------------------------------|---|---|---|---|----|----|-----------|----|--------|
+| Length | | | | | | | Class-Num | | C-type |
+| ... Call identifier ... | | | | | | | | | |
+
+Where the following C-types are defined:
+
+- C-Type = 1 (operator specific): The call identifier contains operator specific identifier.
+- C-Type = 2 (globally unique): The call identifier contains globally unique part plus an operator specific identifier.
+
+The following structures are defined for the call identifier:
+
+- Call identifier: generic [Length\*8-32] bit identifier. The number of bits for call identifier must be multiples of 32 bits, with minimum size of 32 bits.
+
+The structure for the globally unique call identifier (to guarantee global uniqueness) is to concatenate a globally unique fixed ID (composed of country code, carrier code, unique access point code) with an operator specific ID (where the operator specific ID is composed of a source transport network element address – and a local identifier).
+
+Therefore, a generic CALL\_ID with global uniqueness includes (composed of plus plus ) and (composed of plus ). For a CALL\_ID that only requires operator specific uniqueness only the is needed, while for a CALL\_ID that requires to be globally unique both and are needed.
+
+The shall consist of a three-character International Segment (the ) and a twelve-character National Segment (the plus ). These characters shall be coded according to ITU-T Rec. T.50. The International Segment (IS) field provides a 3-character ISO 3166 Geographic/Political Country Code. The country code shall be based on the three-character uppercase alphabetic ISO 3166 Country Code (e.g., USA, FRA).
+
+The National Segment (NS) field consists of two sub-fields: the ITU Carrier Code followed by a Unique Access Point Code. The ITU Carrier Code is a code assigned to a network operator/service provider, maintained by the ITU-T Telecommunication Standardization Bureau in association with ITU-T Rec. M.1400. This code shall consist of 1-6 left-justified characters, alphabetic, or leading alphabetic with trailing numeric. The unique access point code shall be a matter for the organization to which the country code and ITU carrier code have been assigned, provided that uniqueness is guaranteed. This code shall consist of 6-11 characters, with trailing NULL, completing the 12-character National Segment.
+
+The format of the Call identifier field for C-Type = 1:
+
+| 0 | 1 | 2 | 7 | 8 | 15 | 16 | 23 | 24 | 31 | | | | | | | | | | | | |
+|-------------------------------------------------|---|---|----------|---|-----------|----|--------|----|----|--|--|--|--|--|--|--|--|--|--|--|--|
+| Length | | | | | Class-Num | | C-type | | | | | | | | | | | | | | |
+| Type | | | Reserved | | | | | | | | | | | | | | | | | | |
+| Source transport network element address ... | | | | | | | | | | | | | | | | | | | | | |
+| Local Identifier | | | | | | | | | | | | | | | | | | | | | |
+
+The format of the Call identifier field for C-Type = 2:
+
+| 0 | 1 | 2 | 7 | 8 | 15 | 16 | 23 | 24 | 31 | | | | | | | | | | | | |
+|-------------------------------------------------|---|---|--------------|---|-----------|----|--------|----|----|--|--|--|--|--|--|--|--|--|--|--|--|
+| Length | | | | | Class-Num | | C-type | | | | | | | | | | | | | | |
+| Type | | | IS (3 bytes) | | | | | | | | | | | | | | | | | | |
+| NS (12 bytes) | | | | | | | | | | | | | | | | | | | | | |
+| Source transport network element address ... | | | | | | | | | | | | | | | | | | | | | |
+| Local Identifier | | | | | | | | | | | | | | | | | | | | | |
+
+In both cases, a "Type" field is defined to indicate the type of format used for the source transport network element address. The Type field has the following meaning:
+
+- For Type = 0x01, the source transport network element address is 4 bytes;
+- For Type = 0x02, the source transport network element address is 16 bytes;
+- For Type = 0x03, the source transport network element address is 20 bytes;
+- For type = 0x04, the source transport network element address is 6 bytes;
+- For type = 0x7f, the source transport network element address has the length defined by the vendor.
+
+Source transport network element address:
+
+- An address of the transport network element (SSN) controlled by the source network.
+
+Local identifier:
+
+- A 64-bit identifier that remains constant over the life of the call.
+
+Note that if the source transport network element address is assigned from an address space that is globally unique, then the operator-specific CALL\_ID may also be used to represent a globally unique CALL\_ID. However, this is not guaranteed since this address may be assigned from an operator-specific address space.
+
+The following processing rules are applicable to the CALL\_ID object:
+
+- For initial calls, the calling/originating party call controller must set the CALL\_ID's C-Type and call identifier value to all-zeros.
+- For a new call request, the source network call controller (SNCC) sets the appropriate C-type and value for the CALL\_ID.
+- For an existing call (in case CALL\_ID is non-zero) the SNCC verifies existence of the call.
+- The CALL\_ID object on all messages MUST be sent from ingress call controller to egress call controller by all other (intermediate) controllers without altering.
+- The destination user/client receiving the request uses the CALL\_ID value as reference to the requested call between the source user and itself. Subsequent actions related to the call uses the CALL\_ID as the reference identifier.
+
+### 7.1.2 Support for Soft permanent connection
+
+GMPLS RSVP-TE may be extended to support SPC services. An SPC service assumes that both source and destination user-to-network connection segments are provisioned while the network connection segment is set up via the control plane. For example, when an initial request is received from an external source (e.g., from management system), there is an implicit assumption that the control plane has adequate information to determine the specific destination (network-to-user) link connection to use. Support for SPC is provided via the SPC\_LABEL object.
+
+The SPC\_LABEL is a sub-object of the GENERALIZED\_UNI object, and has the same format and structure as the EGRESS\_LABEL sub-object of the GENERALIZED\_UNI object. The SPC\_LABEL information is:
+
+- SPC\_LABEL (Type = 4, Sub-type = 2).
+
+Note that to support the case of SPC, the GENERALIZED\_UNI object is used. This object is used to support the SPC label information as well as service level and diversity specifications that are relevant to the SPC connection request. For a SPC request, the source and destination TNA addresses contain the addresses of the transport network elements controlled by the source the destination network call controllers, respectively. Thus the source TNA contains the address of the transport network element controlled by the source network call controller and the destination
+
+TNA contains the address of the transport network element controlled by the destination network call controller.
+
+## 7.2 Defect handling of GMPLS RSVP-TE
+
+There are different types of defects that may affect the control plane. These defects may range from a simple signalling channel failure to multiple control plane node failures. The control plane needs to support appropriate behaviours to recover from these defects, initially attempting to recover from failures based on local control plane mechanisms, local interaction with the transport plane, and subsequently attempting to recover based on control plane interactions with external components. General guidelines for defect handling include:
+
+- Control plane failures are notified to the management plane. The management plane may direct the control plane to take certain actions due to the failure. These actions may include entering into a self-refresh state, cleaning up of partial connections, release of certain connections, or other protocol-specific actions for state maintenance and recovery.
+- A control plane node may provide a persistent storage of relevant information, such as call and connection state information, configuration information, and control plane neighbour information.
+- After repair if connection/call states cannot be recovered, the control plane node may communicate with an external component to attempt state information recovery. External components may include neighbour control plane nodes or a persistent storage provided by a centralised (e.g., management plane) component. Note that although the restart mechanism allows neighbour control plane nodes to automatically recover (and thus infer) the states of calls/connections, this mechanism can also be used for verification of neighbour states while the persistent storage provides the local recovery of lost state. In this case, if during the Hello synchronization the restarting node determines that a neighbour does not support state recovery (i.e., local state recovery only), and the restarting node maintains its state on a per neighbour basis, the restarting node should immediately consider the Recovery as completed.
+- A control plane node notifies the management plane of the inability to recover (subset of) relevant information (e.g., inability to synchronize state of connections). The management plane may respond with the following actions (the default control plane action should be to retain the connections):
+ - Release the impacted connections.
+ - Retain the impacted connections. In this case, a connection may remain non-synchronized from the control plane perspective; however, the connection may remain valid.
+- A control plane node (after recovering from node failure) may not be able to recover neighbour connection state from its local persistent storage and thus may lose information on connections. In this case the control plane node should request an external controller (e.g., the management system) for information to recover the connections. Similarly call state may be un-recovered and require management intervention to resolve. Specifics of the interactions between the control plane and management plane are beyond the scope of this Recommendation.
+
+Thus, as a general rule:
+
+- A control plane failure must not result in the release of established connections. Setup requests in the process of been completed may be removed (either during the failure or after recovery from failure). Established connections associated with a pending release request must be released (either during the failure or after recovery from failure).
+
+- Additional actions by the control plane may be dependent on provisioned default behaviour for a particular type of connection.
+
+However, a transport plane node failure may result in the release of established connections. This depends on the type of connection and the service level associated with each connection. For example, a "best-effort unprotected" connection may be released during a transport plane node failure while a "protected" connection must be restored (or maintained) based on the service level specification associated with that connection. Note that even in the case of a protected connection, the original connection may be released while a new connection is set up (this also depends on the type of protection used for the particular connection).
+
+In the case of an initial failure to set up the call, an error message is sent upstream towards the source call controller. The source call controller, upon receiving indication of a failure (e.g., information in the ERROR\_SPEC object) to set up a call, may initiate a retry of the call request. Crankback is a mechanism that supports the ability of the control plane to automatically retry the establishment of a connection, using an alternative path, when a connection setup request fails. The route controller may use the information returned in the error message to determine an alternate path. Specification for the crankback mechanism is for further study.
+
+### 7.2.1 Signalling channel failure
+
+In the case of signalling channel failure between control plane nodes A and B, connection #1, #4 and #6 will be affected. As the RSVP-TE state refresh are point-to-point, there will be three Path refresh messages (or a single Srefresh message) between nodes A and B that are disrupted. According to the behaviours described above, both nodes A and B will notify the management plane of the communications failure between nodes A and B. Management plane determines that the failure is a communications channel failure (since it is still receiving notifications from both control plane nodes) and thus instructs both nodes to continue with self-refresh. Figure 3 illustrates the failure scenario.
+
+
+
+Diagram illustrating a signalling channel failure between control plane nodes A and B. The diagram shows four control plane nodes (A, B, C, D) connected in a line. The link between Node A and Node B is marked with an 'X', indicating a failure. Below the nodes, a bracket labeled 'Connections' shows six numbered connections. Connections 1, 4, and 6 are shown as lines between Node A and Node B, which are disrupted by the failure. Connections 2, 3, 5, and 6 are shown as lines between Node B and Node D, which remain active. The text 'G.7713.2\_F03' is visible in the bottom right corner of the diagram area.
+
+**Figure 3/G.7713.2/Y.1704.2 – Signalling channel failure between control plane nodes A and B**
+
+Upon repair of the signalling channel, nodes A and B initiate mechanism (as per GMPLS RSVP-TE restart mechanism – send Srefresh for state verification) for synchronizing the states of the affected connections and calls (e.g., states of connections #1, #4 and #6). If during the synchronization procedure connection states are found out of synchronization, a notification is sent to the management plane according to the behaviour described above.
+
+### 7.2.2 Single control plane node failure
+
+In the case of a control plane node failure, for example failure of node B in Figure 4, both neighbouring nodes A and C will notify the management plane of loss of communication with node B. The management plane then determines whether any connections (and calls) are affected by the control plane node failure. For connections (and calls) that are not affected, it instructs nodes A
+
+and C to enter self-refresh procedures; for connections affected, it may instruct nodes A and C to initiate connection release, e.g., if there is also an associated transport plane failure.
+
+Note that in addition to management plane notification, connections that are disrupted due to the control plane node failure will be detected by nodes A and C (e.g., LOS) and as such the control plane may also initiate release of the connection based on this status for certain types of connections, e.g., "best effort" connections. Figure 4 illustrates this scenario.
+
+
+
+Diagram illustrating control plane node B failure. Four nodes (A, B, C, D) are shown in a line. Node B is crossed out with an 'X'. Below the nodes, connections are shown as horizontal lines with diamond markers. Connection 1 is between A and B. Connection 2 is between B and C. Connection 3 is between C and D. Connection 4 is between A and B. Connection 5 is between B and C. Connection 6 is between A and C. The label 'Connections' is on the left, and the code 'G.7713.2\_F04' is on the right.
+
+**Figure 4/G.7713.2/Y.1704.2 – Control plane node B failure**
+
+In the case of self-refresh, upon node B's recovery, node B restores the connection states based on its "last-known" connection state status via a local persistent storage. Two possible scenarios exist:
+
+- Node B's connections are lost due also to transport plane failure (note that for this case the connections (#1, #2, #4, #5, #6) have already been released by the non-failed control plane node since there would be indications of service interruption from the transport plane to the control plane – via transport plane's OAM mechanism); in this case node B may be instructed by the management system (if it did not already perform this via examining its fabric status) to remove the states of the affected connections.
+- Node B's connections are retained (i.e., connections #1, #2, #4, #5, #6 remain active); in this case, node B initiates recovery procedure with node A and node C.
+
+NOTE – This may be done simultaneously or per-neighbour.
+
+Thus, node B's neighbour may not distinguish the node failure from a signalling channel failure. If status of any active connections is out-of-sync, then the management plane needs to provide information to correct the synchronization as per above behaviours.
+
+## 7.3 Example signalling flows
+
+This clause illustrates basic signal flows for the GMPLS RSVP-TE for Soft Permanent Connections and Switched Connections. The basic signal flows considered within the document are operations associated with supporting Soft Permanent Connections and Switched Connections. A general description of the signalling flow for the setup procedure:
+
+- A Path message is sent from the source to the destination to request a connection.
+- Upon reception of the Path message by the destination node, an RSVP session is set up between the source and destination.
+- The destination node responds to the Path message via one of two messages sent in the upstream direction:
+ - Resv (for normal setup response); or
+ - PathErr (for error in the setup procedure); in this case the connection is not set up. If the Path state is not removed, then an explicit PathTear is needed to remove any extraneous states.
+
+- Upon reception of the Resv message by the source node, an optional ResvConf message may be sent. This is dependent on the RESV\_CONFIRM object within the Resv message.
+
+### 7.3.1 Example SPC signal flow
+
+Figures 5 and 6 show an example signal flow for SPC request. For a SPC connection, it is assumed that the user-to-network link connection is provisioned and information is provided to the control plane regarding the identity of the link connection. Setting up the switched portion of the SPC connection remains the same as that for setting up a switched connection. This is true of the SPC request signal flow as well.
+
+
+
+Figure 5: Basic soft permanent connection setup sequence diagram. The diagram shows vertical lines representing network components: OPCC, SNCC, DNCC, and CPCC. Interfaces I-NNI and E-NNI are marked. A 'Request from MP' arrow points from the Management Plane to the SNCC at the 'A Interface/Label identified by MP'. Signaling between SNCC and DNCC across the E-NNI includes 'Path' (right arrow), 'Ack' (left arrow), 'Resv' (left arrow), and 'ResvConf' (right arrow). The DNCC is associated with 'Z Interface/Label identified by MP'. Cloud shapes represent internal node processing.
+
+Figure 5/G.7713.2/Y.1704.2 – Basic soft permanent connection setup
+
+
+
+a) With Path\_State\_Removed flag.
+
+Figure 6: Basic SPC release sequence diagram. Similar layout to Figure 5. It starts with a 'Teardown "connect X"' request from the MP to the SNCC. Signaling across E-NNI includes 'Path' (right arrow), 'Ack' (left arrow), and 'PathErr' (left arrow) with footnote marker 'a)'. A horizontal dashed line labeled 'Start to release' spans from the OPCC/SNCC area across to the DNCC/CPCC area. Footnote 'a) With Path\_State\_Removed flag.' is at the bottom.
+
+Figure 6/G.7713.2/Y.1704.2 – Basic SPC release
+
+### 7.3.2 Basic SC signal flow
+
+Figure 7 illustrates the setup of the SC. To set up a SC call, a user initiates the request across the UNI interface. The request is propagated across the network to the destination user. Upon verification/acceptance of the request, a positive indication is sent to the source user. Optionally, the source user may also transmit a final response. This third phase message is introduced to support explicit destination notification of completed connection setup.
+
+
+
+The diagram illustrates the basic SC setup process. It shows four main entities: OPCC (Originating Party Call Controller), SNCC (Source Network Call Controller), DNCC (Destination Network Call Controller), and CPCC (Called Party Call Controller). The interfaces between them are UNI (User Network Interface) at the ends and I-NNI (Internal Network Network Interface) and E-NNI (External Network Network Interface) within the network. The SNCC contains three cloud-like shapes representing network nodes. The signal flow is as follows:
+
+
+- Path:** A black arrow from OPCC to SNCC.
+- Ack:** A black arrow from SNCC back to OPCC.
+- Resv:** A black arrow from SNCC to DNCC, then from DNCC to CPCC.
+- ResvConf:** A grey arrow from CPCC back to DNCC, then from DNCC back to SNCC, and finally from SNCC to OPCC.
+
+ The diagram is labeled G.7713.2\_F07.
+
+Figure 7: Basic SC setup diagram showing signal flow between OPCC, SNCC, DNCC, and CPCC across UNI, I-NNI, and E-NNI interfaces.
+
+Figure 7/G.7713.2/Y.1704.2 – Basic SC setup
+
+In the case for SC release, a release request may be initiated by different controllers, e.g., either originating party call controller, called party call controller, or any one of network call controllers may initiate the release. Figure 8a illustrates the originating party initiated release request, Figure 8b illustrates the called party initiated release request, and Figures 8c to 8f illustrate a network call controller initiating a release request.
+
+
+
+The diagram illustrates the basic SC release process initiated by the OPCC. The entities and interfaces are the same as in Figure 7. The signal flow is as follows:
+
+
+- Start to release:** A dashed green line indicates the start of the release process at the OPCC.
+- Path:** A black arrow from OPCC to SNCC (part of the initial setup, shown for context).
+- Ack:** A black arrow from SNCC to OPCC (part of the initial setup, shown for context).
+- PathErra) :** A black arrow from CPCC to DNCC, then from DNCC to SNCC, and finally from SNCC to OPCC. This message indicates the release request.
+
+ A footnote 'a)' indicates that the PathErr message is sent 'With Path\_State\_Removed flag'. The diagram is labeled G.7713.2\_F08a.
+
+Figure 8a: Basic SC release (OPCC initiated) diagram showing signal flow between OPCC, SNCC, DNCC, and CPCC across UNI, I-NNI, and E-NNI interfaces.
+
+Figure 8a/G.7713.2/Y.1704.2 – Basic SC release (OPCC initiated)
+
+
+
+UNI I-NNI E-NNI UNI
+
+Start to release
+
+Resv (D&R)
+
+PathTear
+
+OPCC SNCC DNCC CPCC
+
+G.7713.2\_F08b
+
+Sequence diagram for Figure 8b showing basic SC release initiated by CPCC. The diagram shows four nodes: OPCC, SNCC, DNCC, and CPCC, connected by UNI, I-NNI, and E-NNI interfaces. The release process starts at CPCC, which sends a Resv (D&R) message leftwards through DNCC and SNCC to OPCC. Simultaneously, a PathTear message is sent from SNCC to DNCC and then to CPCC. The OPCC node shows a 'Start to release' state.
+
+**Figure 8b/G.7713.2/Y.1704.2 – Basic SC release (CPCC initiated)**
+
+
+
+UNI I-NNI E-NNI UNI
+
+Start to release
+
+Path (A&R)
+
+Resv (D&R)
+
+PathTear
+
+OPCC SNCC DNCC CPCC
+
+G.7713.2\_F08c
+
+Sequence diagram for Figure 8c showing SC release initiated by an intermediate controller (DNCC) towards the UNI downstream (CPCC). The diagram shows the same nodes and interfaces as Figure 8b. The process begins with DNCC sending a Path (A&R) message to CPCC. CPCC responds with Resv (D&R) back to DNCC, which propagates to SNCC and OPCC. A PathTear message is also sent from SNCC to DNCC and then to CPCC. The OPCC node shows a 'Start to release' state.
+
+**Figure 8c/G.7713.2/Y.1704.2 – SC release: Intermediate controller initiated (towards UNI downstream)**
+
+
+
+UNI I-NNI E-NNI UNI
+
+Resv (A&R)
+
+Start to release
+
+Path (D&R)
+
+PathErra)
+
+OPCC SNCC DNCC CPCC
+
+G.7713.2\_F08d
+
+Sequence diagram for Figure 8d showing SC release initiated by an intermediate controller (SNCC) towards the UNI upstream (OPCC). The process starts with SNCC sending a Resv (A&R) message to OPCC. OPCC enters 'Start to release'. SNCC also sends a Path (D&R) message to DNCC, which propagates to CPCC. A PathErr message with footnote 'a' is sent from CPCC back to DNCC and SNCC.
+
+a) PathErr scenario as above for case of Path\_State\_Removed flag.
+
+**Figure 8d/G.7713.2/Y.1704.2 – SC release: Intermediate controller initiated (towards UNI upstream)**
+
+
+
+UNI I-NNI E-NNI UNI
+
+Start to release
+
+OPCC SNCC DNCC CPCC
+
+Resv (A&R)
+
+Resv (D&R)
+
+PathTear
+
+G.7713.2\_F08e
+
+Sequence diagram for SC release initiated towards E-NNI downstream. The diagram shows a 'Start to release' signal from the OPCC to the SNCC. The SNCC then sends 'Resv (A&R)' and 'Resv (D&R)' messages to the E-NNI. The E-NNI sends a 'PathTear' message to the DNCC, which in turn sends a response to the CPCC. The diagram is labeled G.7713.2\_F08e.
+
+**Figure 8e/G.7713.2/Y.1704.2 – SC release: Intermediate controller initiated (towards E-NNI downstream)**
+
+
+
+UNI I-NNI E-NNI UNI
+
+Start to release
+
+OPCC SNCC DNCC CPCC
+
+Resv (A&R)
+
+Path (D&R)
+
+PathErra)
+
+G.7713.2\_F08f
+
+Sequence diagram for SC release initiated towards E-NNI upstream. The diagram shows a 'Start to release' signal from the OPCC to the SNCC. The SNCC sends a 'Path (D&R)' message to the E-NNI. The E-NNI sends a 'PathErr' message to the DNCC, which in turn sends a response to the CPCC. The diagram is labeled G.7713.2\_F08f.
+
+a) PathErr scenario as above for case of Path\_State\_Removed flag.
+
+**Figure 8f/G.7713.2/Y.1704.2 – SC release: Intermediate controller initiated (towards E-NNI upstream)**
+
+### 7.3.3 Setup rejection signal flow
+
+Figure 9 illustrates the case where a request to set up a connection is immediately rejected by an intermediate node. This may occur due to various reasons as described in ITU-T Rec. G.7713/Y.1704, e.g., during the initial request, no resources were available.
+
+
+
+Figure 9: Setup rejection signal flow diagram. The diagram shows a sequence of nodes: OPCC, SNCC, DNCC, and CPCC, connected by UNI, I-NNI, and E-NNI interfaces. A 'Start to release' message is sent from the OPCC to the SNCC. The SNCC sends a 'Path (D&R)' message to the DNCC. The DNCC immediately responds with a 'PathErr' message (marked with a red starburst) and an 'Ack' message. The SNCC then receives the 'PathErr' message and sends a 'PathErr' message back to the OPCC. The CPCC is shown as a final node but is not reached by the setup path.
+
+a) PathErr with Path\_State\_Removed flag set.
+
+G.7713.2\_F09
+
+**Figure 9/G.7713.2/Y.1704.2 – Setup: Rejection by intermediate node
+(with Path\_State\_Removed set)**
+
+Figure 10 illustrates the case where a request to set up a connection is rejected by an intermediate node after receiving an indication from the destination. For example, this may occur due to inability to complete assignment of a resource to the requested connection due to transport plane error.
+
+
+
+Figure 10: Setup rejection signal flow diagram. The diagram shows a sequence of nodes: OPCC, SNCC, DNCC, and CPCC, connected by UNI, I-NNI, and E-NNI interfaces. A 'Start to release' message is sent from the OPCC to the SNCC. The SNCC sends a 'Path' message to the DNCC. The DNCC receives an 'Ack' message from the CPCC and then sends a 'Resv' message to the SNCC. The SNCC receives the 'Resv' message and then sends a 'PathErr' message (marked with a red starburst) to the OPCC. The DNCC also sends a 'PathTear' message to the SNCC.
+
+a) PathErr scenario as above for case of Path\_State\_Removed flag set.
+
+G.7713.2\_F010
+
+**Figure 10/G.7713.2/Y.1704.2 – Setup: Rejection by intermediate node
+after receiving indication**
+
+Figure 11 illustrates the case where a request to set up a connection is rejected by an intermediate node after receiving a confirmation from the source. For example, this may occur due to loss of message (either loss of the ResvConf message, or the Ack message associated with the ResvConf message). In this case the connection has in fact been established, and connection monitoring (if any) may be in place. As such this defect constitutes a control plane defect, and thus should not be service impacting. A possible action should be to notify the management system of the control plane defect.
+
+
+
+The diagram illustrates a sequence of messages for connection setup across several network domains: UNI, I-NNI, E-NNI, and CPCC.
+
+
+- At the left UNI, a 'Start to release' signal is sent to the SNCC.
+- Messages are exchanged between the UNI and the I-NNI (represented by three cloud-like shapes).
+- From the I-NNI, a 'Path' message is sent to the E-NNI.
+- The E-NNI sends an 'Ack' message back to the I-NNI.
+- The I-NNI sends a 'Resv' message back to the UNI.
+- The UNI sends a 'ResvConf' message back to the I-NNI.
+- Upon receiving 'ResvConf', the E-NNI node generates a defect (indicated by a red starburst) and sends a 'Notify management system of defect' message.
+- A dashed horizontal line labeled 'Start to release' spans across the bottom of the diagram.
+- At the right side, another UNI is shown connected to the DNCC, which is connected to the CPCC.
+
+Sequence diagram showing a connection setup process between UNI and CPCC nodes through intermediate nodes (I-NNI, E-NNI, DNCC). The diagram shows messages Path, Ack, Resv, and ResvConf being exchanged. A red starburst indicates a rejection at the E-NNI node after receiving ResvConf, leading to a 'Notify management system of defect' message. A dashed line indicates the 'Start to release' point.
+
+a) PathErr scenario as above for case of Path\_State\_Removed flag.
+
+G.7713.2\_F11
+
+**Figure 11/G.7713.2/Y.1704.2 – Setup: Rejection by intermediate node after receiving confirmation**
+
+# 8 GMPLS RSVP-TE messages
+
+A GMPLS RSVP-TE message format is based on the basic structure as defined by RFC 2205. An RSVP message is composed of a common header plus a number of objects specific to each message type. The structure of the common header is shown in Table 1:
+
+**Table 1/G.7713.2/Y.1704.2 – Common header**
+
+| 0 | 1 | 2 | 7 | 8 | 15 | 16 | 23 | 24 | 31 |
+|----------|---|-------|------------|----------|----|---------------|----|----|----|
+| Vers | | Flags | | Msg type | | RSVP checksum | | | |
+| Send_TTL | | | (Reserved) | | | RSVP length | | | |
+
+Definitions of the fields may be found in RFC 2205, with specific message type extensions provided by RFC 2961 and RFC 3209. For clarity, the message type field is re-produced below:
+
+Msg Type:
+
+- 1: Path
+- 2: Resv
+- 3: PathErr
+- 5: PathTear
+- 7: ResvConf
+- 13: Ack
+- 15: Srefresh
+
+20: Hello
+21: Notify
+
+## 8.1 Path
+
+This message is modified from definitions in RFC 2205, RFC 2961 and RFC 3209 with further extensions to support distributed connection management.
+
+This message is used to:
+
+- Initiate a connection setup request.
+- Initiate a source-initiated release request (using ADMIN\_STATUS with D and R bit set).
+- Initiate an intermediate-initiated downstream release request (using ADMIN\_STATUS with A and R bit set).
+- Respond to a received Resv (with A and R bit set) connection release request (using ADMIN\_STATUS with D and R bit set).
+
+```
+ ::=
+
+ [ ]
+ [ [ | ] ... ]
+ [ ]
+
+
+
+ [ ]
+
+
+ [ ]
+ [ ... ]
+ [ ]
+ [ ]
+ [ ]
+
+ [ ... ]
+
+```
+
+The format of the sender description for unidirectional LSPs is:
+
+```
+ ::=
+
+
+ [ ]
+ [ ]
+ [ ]
+ [ ]
+```
+
+The format of the sender description for bidirectional LSPs is:
+
+```
+ ::=
+
+
+ [ ]
+ [ ]
+ [ ]
+ [ ]
+
+```
+
+The must come first before any objects. When present, the object must precede all other objects.
+
+## 8.2 Resv
+
+This message is modified from definitions in RFC 2205, RFC 2961 and RFC 3209 with further extensions to support distributed connection management.
+
+This message is used to:
+
+- Respond to a connection setup request indicated by a Path message.
+- Initiate a destination-initiated release request (using ADMIN\_STATUS with D and R bit set).
+- Initiate an intermediate-initiated upstream release request (using ADMIN\_STATUS with A and R bit set).
+- Respond to a received Path (with A and R bit set) connection release request (using ADMIN\_STATUS with D and R bit set).
+
+```
+ ::=
+
+ [ ]
+ [ [ | ] ... ]
+ [ ]
+
+
+
+
+ [ ]
+ [ ]
+ [ ]
+ [ ]
+ [ ... ]
+